I found some discrepancies in several batches in SAP. Where do I go to update the Expiration date of a batch? Tcode please..

Thanks

Ilsa

Dear GBT Experts,

I'm currently looking for information how GBT on Hana would improve reporting performance.

Based on the official SAP communication, the core application reporting can be improved by 60%.

Is there any benchmark or information available especially for GBT?

thank you in advance for your help

In this short video, you get some tips where to find information about SAP GBT 2.0. Furthermore, you find some quicklinks or URLs, which you can use to display different kinds of information or documentation.

For example, you get the information were to find the administrator’s guide or the quicklink to access the application help for SAP GBT 2.0.

Use this link: https://www.youtube.com/watch?v=PTEtvFIWrL8.

On April 22nd we released the first content package for HANA Live for SAP Global Batch Traceability. It is available for download on SAP Service Marketplace.

HANA Live content for SAP Global Batch Traceability enables customers to do very flexible reporting on batch-where used information. Without any programming knowledge users can adopt available query views by adding columns, filtering data, defining the type of output (maps, bar charts, heat maps and more). This is possible by the use of SAP analytics tools like SAP Lumira, SAP BusinessObjects Analysis, SAP BusinessObjects Explorer or any other analytics tool that can connect to a SAP HANA database.

General Information on SAP HANA Live are available in the following blog post: SAP HANA Live - Real-Time operational reporting

The current delivery consists of several database procedures which allow to traverse the batch network held in SAP Global Batch Traceability. On top of these procedures query views can be built by the customer. As an example the "Batch Distribution List Query View" is delivered with the package and can be used right out of the box.

A summary of the delivered package is shown on the following slide:

HANA Live Content 1.0 for SAP GBT can be deployed in two different ways. If you have a HANA side car approach running already - just deploy the content in your landscape and start data replication from SAP GBT to your HANA side car. You can also install SAP GBT directly on a HANA database and deploy the content on top of this server:

Most value is delivered from this content if you combine it with data from other applications.

Imagine, for example, having the batch genealogy data as a starting point and combining it with information from a SAP Transportation Management System. Starting off with a raw material batch that should be recalled, you can now not only tell which deliveries and which customers are affected. In addition you can exactly show on which trucks, ships, containers the affected goods are at the moment. Just one example of many possible use cases!

Find additional information on HANA based analytics at http://help.sap.com/hba

In case of questions you can also contact us directly!

This article describes how to add a navigation button to the batch details screen to jump to the inspection lot worklist in ERP for the displayed batch.

GBT offers the functionality to navigate to the original system of the data record displayed. This is possible on every details screen within the UI of GBT.
Details screens can be customized by the customer to show additional fields or remove some of the fields displayed in standard GBT. In addition to this it is possible to customize navigation buttons on the details screens. For the navigation Launchpads are used which needs to be customized.

The following describes the steps which need to be executed to add the navigation to the inspection lot worklist in the source system.

1. Define Navigation Targets
   SPRO: Cross-Application Components -> Processes and Tools for Enterprise Applications -> Settings for BO Framework and Navigation -> Navigation, Parameter Mapping, and Services -> Define Navigation Targets (cross-client customizing).
   
   To create additional navigation functionality for a details screen you define a navigation target which will be used to determine the action you want to execute on the screen. Each Navigation Target will result in a separate FPM Event in the customizing of the details screens.
   
   Create a new navigation target called “LOT_DISPLAY” with Description “Display Inspection Lots”.
   
   
   
2. Create a new Launchpad application
   SPRO: Cross-Application Components -> SAP Global Batch Traceability -> Analysis of Global Batch Traceability Network -> Navigate to External Systems Using Launchpad.
   
   A Launchpad application defines the application you want to include in your existing UI.
   Within the Launchpad application you define the parameters used for navigation and the target application itself.
   
   Create a new Launchpad application by copying an existing application (for example “Display Batch in SAP ERP”). Enter a new name e.g. “Display Inspection Lots in SAP ERP” and change the transaction code to QA33.
   Set the Application Alias to a new value e.g. “LPD_LOT_DISP”. This value will be used in the next step to link this Launchpad application to a navigation target.
   In section Target App. Parameters you have to define the mapping of parameters to the target transaction parameters. Click on the Parameter Mapping Button and maintain the following:
   

   Program	RQEEAL10
   Dynpro  Number	1000
   OK Code	<space>
   Forward only the following parameters	<checked>
   Not completed by COMMIT	<checked>
   No Batch Input for CALL Trans.	<checked>

   
   In the table for parameters enter the following three parameters and their target parameters:
   

   Source Parameter	Target Parameter
   MATNR	QL_MATNR-LOW
   BATNR	QL_CHARG-LOW
   PLANT	QL_WERKS-LOW

   
   The Parameter Mapping should look like this:
   
   
   Set field Entries Once Started to ‘R Skip Initial Screen if Possible’.
   Save the Launchpad application.
   
   The new Launchpad application should look like this:
   
   
   
3. Assign the Navigation Target
   SPRO: Cross-Application Components -> Processes and Tools for Enterprise Applications -> Settings for BO Framework and Navigation -> Navigation, Parameter Mapping, and Services -> Assign the Navigation Target.
   
   In this step you create the link of the internal GBT data and navigation structure to the external navigation using Launchpad technology.
   
   Create a new entry in this table with the following data:
   
   
   
4. Add button to Batch Details Screen
   As described above, GBT screens can be customized using the standard Floorplan Manager (FPM) functionality.
   To provide the new navigation target defined in the Launchpad, a button for the navigation to inspection lots has to be added to the batch details screen:
   
   Start transaction FPM_WB (FPM Workbench) and choose ‘Edit FPM Customizing (FLUID)’.
   Enter FPM_FORM_UIBB_GL2 as Component Name and /GBT/WDC_BATCH_DETAILS_CFG  as Configuration ID and choose ‘New’ (or Continue in Change Mode if the customizing already exists).
   In the Form UIBB Schema choose ‘Element’ -> ‘Add Button at Next Level’.
   In the following popup choose action ‘LOT_DISPLAY’ and then define a button text e.g. ‘Inspection Lots’ and an explanation text e.g. ‘Display Inspection Lots in Source System’.
   The button attributes should look like this:
   
   Save the customizing.
   
   Now the button 'Inspection Lots' is available on the Batch Details screen.

This article describes how to add batches with the shelf life date within a certain time frame to a worklist.

GBT 2.0 offers the functionality of worklists which enables you to group tracked objects for further checking, and to trigger actions or run reports. You can share a worklist to solve an issue together with other colleagues.

Worklist items can either be read from the standard database tables (stored manually or using a period report) or they can be selected dynamically when displaying a worklist by executing a specific programmed determination.

To select worklist items dynamically, interface /GBT/IF_WORKLIST_ITEM_READ, which has two methods, needs to be implemented:

• Method GET_NAME to define a name for the dynamical determination of worklist items
• Method GET_ITEM_BY_WORKLIST_ID which has the worklist item determination logic

In this example, a worklist is implemented to display all batches which will expire in the next 30 days. This worklist should always display the current result for the date it is displayed.

The implementation of interface /GBT/IF_WORKLIST_ITEM_READ has to be created using transaction SE24.

1. Double click on method GET_NAME, copy the following coding into this method, and choose Save (Ctrl+S):
   
     rv_name = 'Batches expiring next 30 days'(001).
   
   
2. Go back to the class header (F3), and double click on method GET_ITEM_BY_WORKLIST_ID.
3. Copy the following coding into this method and choose Save (Ctrl+S):
   
     DATA:
       lv_expiring_date TYPE /gbt/bat_expiry_date,
       lt_bat_itm_guid  TYPE /gbt/t_obj_guid.
   
     FIELD-SYMBOLS:
       <ls_worklist_itm_key> LIKE LINE OFet_worklist_itm_key,
       <lv_bat_itm_guid>     LIKE LINE OFlt_bat_itm_guid.
   
     CLEAR et_worklist_itm_key.
   
     lv_expiring_date = sy-datum + 30.  "Expiring in 30 days
   
   * Perform selection to return items with real batches
     SELECT obj_guid FROM /gbt/v_bat_itm INTO TABLElt_bat_itm_guid
       WHERE expiry_date >= sy-datum
         AND expiry_date <= lv_expiring_date.
   
     LOOP AT lt_bat_itm_guid ASSIGNING <lv_bat_itm_guid>.
       APPEND INITIAL LINE TO et_worklist_itm_key
              ASSIGNING <ls_worklist_itm_key>.
       <ls_worklist_itm_key>-worklist_id = iv_worklist_id.
       <ls_worklist_itm_key>-obj_guid    = <lv_bat_itm_guid>.
       <ls_worklist_itm_key>-obj_type    = 'BAT'.
     ENDLOOP.
   
4. Activate all objects of the new class (Ctrl+F3).
5. Add the new class to the GBT customizing Analysis of Global Batch Traceability Network ->Maintain Available Classes for Dynamic Worklist Items.
6. Create a worklist with dynamic items:
   1. In the SAP NetWeaver Business Client (transaction NWBC) select a role and navigate to the Process Worklists screen.
   2. Choose Create and enter a name and a description for the new dynamic worklist to show all batches which will expire in the next 30 days.
   3. From the dropdown menu for column Item Selection choose the class name created before ('Batches expiring next 30 days').
   4. Choose Save to save your changes.

Hi,

We have following queries regarding Installation of GBT within same logical system & Client as of SAP ERP System. (We know this is very much possible for same logical system, different Clients.)

1. Is this possible.

2. To make it possible are there any prerequisites.

3. We want to know if there will be any issue during transfer of Event/Transaction Data.

4. For Master Data can we bypass distribution of idocs through BD64 as it does not accept same sending and receiving logical system/Client,

Here we can use exit during distribution to idocs while sending idocs through custom program. Looking for better solution.

Thanks & Regards,

Randeep Singh

+41.779931004

We recently released the following support packages:

• support package 03 for component GBTR 200
• support package 11 for component GBTR 100
• support package 11 for component GBTRINT 100 (integration component on SAP ECC)

The support packages are available for download on SAP Support Portal.

Did you ask yourself how the posting of a goods receipt for partial deliveries of a purchase order is displayed in SAP Global Batch Traceability (SAP GBT)? And what other example processes are described for SAP GBT?

Have a look in the documentation of SAP GBT under Example Processes.

This document describes how to create new search criteria in the Batch Search using fields from batch, handling unit, delivery, and material document.

Standard search criteria

On the Batch Search Screen, Global Batch Traceability 2.0 provides the following search criteria in the standard:

• Batch

  • Batch Number (BATNR)
  • Material Number (MATNR)
  • Plant (PLANT)
  • Logical System (LOGSYS)
  • Vendor Batch Number (PRT_BATNR)

• Material

  • Material Description (MATERIAL_DESCR)

• Product Group

  • Filled dynamically

• Handling Unit

  • Handling Unit (HUMNR)
  • Packaging Material (PACK_MAT)
  • Warehouse (WHSENUMBER)
  • WM Transfer Order (WMTONR)

• Delivery

  • Ship-To Party (SHIP_TO)
  • Sold-To Party (SOLD_TO)
  • Actual Goods Issue Date (GI_DATE)

• Material Document

  • Posting Date (PSTNG_DATE)
  • Movement Type (MOVE_TYPE)

• Characteristics

  • Filled dynamically (can be defined by creating batch class GBT_SEL_CRITERIA as described in SAP note 1870447)

It is easily possible to add fields (standard or customer fields) from the objects Batch, Handling Unit, Delivery, Material Document, and Purchase Order as new search criteria to the batch search.

Add new search criteria using BAdI/PLMB/EX_SPI_METADATA_DYN

The search criteria can be modified by implementing method GET_NEW_NODE_DEFINITION of the BAdI /PLMB/EX_SPI_METADATA_DYN (part of Enhancement Spot /PLMB/ES_SPI).

Create a new BAdI implementation for /PLMB/EX_SPI_METADATA_DYN and implement method /PLMB/IF_EX_SPI_METADATA_DYN~GET_NEW_NODE_DEFINITION to add or delete search criteria.

The following example adds the field PROD_DATE (Date of Manufacture) from the batch master:

  DATA:
    ls_component        TYPE /plmb/s_spi_component_descr,
    ls_component_detail TYPE /plmb/s_spi_criteria_details.

  FIELD-SYMBOLS:
    <ls_query_def> LIKE LINE OF cs_metadata_node-queries-sp.


  READ TABLE cs_metadata_node-queries-sp ASSIGNING <ls_query_def>
    WITH KEY query_name = /gbt/cl_nw_mp=>gc_query_name-batch_by_char.
  CHECK sy-subrc = 0.

* Batch: 'Date of Manufacture'
  CLEAR ls_component.
  CLEAR ls_component_detail.
  ls_component-name = 'SAP%PROD_DATE'.
  ls_component-type = '/GBT/BAT_PROD_DATE'.
  APPEND ls_component TO <ls_query_def>-definition-criteria-components.
  ls_component_detail-name          = ls_component-name.
  ls_component_detail-description_s = '009'.
  ls_component_detail-description_l = /gbt/cl_spi_util=>get_data_element_description( ls_component-type ).
  CONCATENATE 'BAT:' ls_component_detail-description_l INTO ls_component_detail-description_l SEPARATED BY space.
  ls_component_detail-options = /gbt/cl_spi_util=>fill_char_select_options( ).
  INSERT ls_component_detail INTO TABLE <ls_query_def>-definition-criteria-component_details.

To delete search criteria you do not want to provide to the users, add the coding similar to the following example in the same method:

* Remove Material Documents Posting Date
  DELETE <ls_query_def>-definition-criteria-components WHERE name = 'MDI%PSTNG_DATE'.
  DELETE TABLE <ls_query_def>-definition-criteria-component_details WITH TABLE KEY name = 'MDI%PSTNG_DATE'.

Add new search criteria via implicit enhancement

As an alternative, you can create an implicit enhancement at the end of method /GBT/CL_NW_MP->ADD_SEL_CRIT_COMPLEX_SEARCH and add some coding to define the additional search criteria.

The following example describes how to add the field PROD_DATE (Date of Manufacture) to the batch search:

1. Start transaction SE24 or SE80 to display class /GBT/CL_NW_MP. Open method ADD_SEL_CRIT_COMPLEX_SEARCH.
2. Choose 'Edit' -> 'Enhancement Operations' -> 'Show Implicit Enhancement Options' from the menu.
   Choose 'Method' -> 'Enhance' from the menu or press Ctrl+F4 to switch to enhancement mode.
3. Place the cursor at the line before the ENDMETHOD statement and choose 'Edit' -> 'Enhancement Operations' -> 'Create Implementation' from the menu or press Shift+Ctrl+F8.
4. On the following popup 'Choose Enhancement Mode' choose button 'Code'.
5. On the following popup 'Create Enhancement Implementation' enter a name and a short description, e.g. Z_ADD_SEL_CRITERIA and 'Add search criteria to batch search' and press Enter.
6. Enter the following coding in the enhancement:
   
   * Batch: 'Date of Manufacture'
     CLEAR ls_component.
     CLEAR ls_component_detail.
     ls_component-name = 'SAP%PROD_DATE'.
     ls_component-type = '/GBT/BAT_PROD_DATE'.
     APPEND ls_component TO cs_criteria_def-components.
     ls_component_detail-name          = ls_component-name.
     ls_component_detail-description_s = '007'.  "First sort field
     ls_component_detail-description_l = /gbt/cl_spi_util=>get_data_element_description( ls_component-type ).
     ls_component_detail-options = /gbt/cl_spi_util=>fill_char_select_options( ).
     INSERT ls_component_detail INTO TABLE cs_criteria_def-component_details.
   
7. Check and activate the enhancement (Ctrl+F2 and Ctrl+F3).

In the same way you can also remove standard selection criteria which you do not want to provide to the users.
For example to remove the field 'Posting Date' from the selection, add the following lines to the implicit enhancement:

* Remove Material Documents Posting Date
  DELETE cs_criteria_def-components WHERE name = 'MDI%PSTNG_DATE'.
  DELETE TABLE cs_criteria_def-component_details WITH TABLE KEY name = 'MDI%PSTNG_DATE'.

Prefix for object type

To enable the query to identify the object to which the field belongs to, a prefix is used in the technical name of the new search criterion.

In the example above, the prefix 'SAP%' is used for the batch field PROD_DATE in variable ls_component-name.

The following prefixes have to be used for the different object types in the batch search:

• Batch: SAP%
• Handling Unit: HUX%
• Delivery: DLV%
• Material Document: MDI%
• Purchase Order: PUI%

Sorting of search criteria

The sequence of the search criteria is defined first by the number in field ls_component_detail-description_s and then by the text in field ls_component_detail-description_l.

Each object type like batch or delivery has a number range for the first sort field ls_component_detail-description_s to group the search criteria:

• Batch: 001 - 009
• Product Group: 010
• Handling Unit: 021 - 030
• Deliveries: 031 - 040
• Material Documents: 041 - 050
• Characteristics: 999

You can define the sequence of the search criteria either by assigning specific numbers, or by using the same number to sort alphabetically by field ls_component_detail-description_l.

Dear GBT Experts,

on the Home screen of GBT Version 2.0 SP03 we are getting following message:

Delete customizing "/GBT/WDC_GCO_HOME_CFG"

Warning 

Customizing "/GBT/WDC_GCO_HOME_CFG" based on a configuration last changed on 2014-02-11 13:26:56.

Warning 

Configuration "/GBT/WDC_GCO_HOME_CFG" last changed on 2014-09-01 15:21:07

Could you please provide instruction how to proceed with such warning?

Thank you in advance

Hi All,

Just want to share a video that we created, showing the multi angle batch search capabilities of SAP GBT.

Hope you like it

SAP Global Batch Traceability - Multi Angle Batch Search - YouTube

Regs,

Ruud

Hi,

In CLFMAS idocs in SAP GBT System we have received some idocs with field OBJEK with only material (no batch or plant), When we are trying to process these idocs it is giving dump with Error 'ASSERTION_FAILED' in ABAP program - /GBT/CL_BAT_BO================CP.

- These idocs are getting generated when we are creating material master and adding batch class in classification view in source system, without creating any batch for the material.

- We would like to know if someone has faced similar issue.

I am not sure if we have some way that we can stop CLFMAS idocs generation for those materials for which batch is not created, so that CLFMAS idoc with field OBJEK does not created with only material field in source system or if we have some solution on GBT side to avoid dump even if we receive CLFMAS idocs with OBJEK field as only material.

Will appreciate your early response.

Thanks & Regards,

Randeep Singh

+41.779931004

In contrast to other search screens, the search criteria of the GBT Batch Search cannot be configured via component customizing.This is due to the dynamic creation of search criteria for the product group and the characteristics.

As of Service Package 3 for Netweaver 7.40, personalization is offered for the FPM search component:

http://help.sap.com/erp_hcm_ias2_2015_02/helpdata/de/d2/d1bb7afb0f49fc90fcf66e0d595ff6/content.htm

Using this personalization, the user can choose a search variant containing the search criteria in the desired sequence that should be displayed when opening the GBT Batch Search.

This search (called Default Search) is not run automatically unless requested.

In case the symbol for the personalization (marked in yellow above) is not visible, personalization has to switched on first for the search component.

To do so, create a component customizing for the batch search configuration /GBT/WDC_BATCH_SEARCH_CHAR_CFG and set the value for the field 'Personalization' to 'Enabled'.

Traceability software maps complex supply chains in Life Science industry

Please check the link for my blog

Dear gurus,

Maybe you could help. Below a short summary of my current concern:

We receive raw material 1 that we send to QM for inspection. The specifications are defined but may vary per customer. Ie: herbicide acceptance level < 10 mg/kg for customer A, B,C and D but only < 5 for customer E.

Scenario 1: At inspection time, material 1 ( batch 11) passed with 7 mg/kg because accepted by many of our customers. This raw material batch is totally handled manually when starting the production to avoid to use it for finish good to customer E.

Scenario 2: At inspection time, material 1 (batch 12) passed with 4 mg/kg because accepted by all our customers. This raw material batch is totally handles manually when starting the production to have it used only for production of finish good to customer E.

How could we avoid this manual practice and have the correct batch selection at production level automatically? Is there any function we can use in SAP?

I read about active ingredient but not sure this is the solution for the described issue.

Thank you.

Sandra.

Did you experience the following?

In SAP ERP, neither a message of typeCREMASnor of typeDEBMASis generated by change pointer although you have changed customer or vendor address data.

Certain fields belong to message type ADRMASonly, for example, fieldEmailor Search Term 2.

• If you change only these fields, no message of typeCREMASorDEBMASis generated by change pointer.
• You must create a change pointer for the related message typeCREMASorDEBMAS.

To do so, implement Business Add-InBDCP_BEFORE_WRITE (Filter Change Pointers per Message Type Before Writing).

For further information, see SAP Note 2280557.

All,

Am new to GBT. As I am in the process of completing the basic settings; have a query related to the output display.

Understand that SAP NetWeaver Business Client (NWBC) is required.

Questions.

1. Is this a portal where the users are supposed to log on and hence query the data?

2. Does it get 'connected' from the SAP ECC menu itself?

My scope

SAP ECC to GBT; no other third party system.

Requesting inputs.

Regards