Need to send Material Class type 001 Characteristics to GBT System

[Former Member]

Hi,

We need to send Material Class 001 Characteristics from ERP to GBT System. We do not have any Material Class type 001 in GBT System, or any mapping for this Class type with any other Class Type in GBT as we have for ERP Batch Class type 023 to GBT Class type 223.

Is there any way that we can create a new Class type or any other method to send these Characteristics to GBT System.

Thanks & Regards,

Randeep Singh

+41.779931004

[martin_wolff]

Hi Randeep,

In SAP GBT, classification is only possible for batches. These classes are of class type 223 (mapped from the original class types 022 and 023 in SAP ERP).
Other class types are not used in SAP GBT.

So unfortunately, it is currently not possible to transfer characteristics for material classes to SAP GBT.

If you could provide more details of how you want to use these characteristics in SAP GBT, we could possibly find a workaround.

Best regards,
Martin Wolff

[Former Member]

Hi Martin,

We want to use this Material Characteristics as search criteria in Web UI and for various reports to be developed on SAP UI.

This characteristics should be stored based on material & logical system combination in GBT.

Based on material characteristics it should find the respective Material, Logical System. Further based on Material, Logical System its should find the respective Batch GUID, and thus we will be able to use in various search criteria, and also in output of these reports.

Many Thanks!

Best Regards,

Randeep Singh

[martin_wolff]

Hi Randeep,

There are roughly 3 alternatives to store the material classification in GBT and use them for selection.

In any case the classification is send with IDOC CLFMAS and will be processed in GBT by function module (FM) /GBT/IL_IDOC_IN_CLFMAS.

To accept also class type 001 and to perform the mapping described in the following solutions this FM needs to be substituted in ALE (Transaction BD51 & WE57) by an enhanced copy.

1. Store the characteristics as customer attributes in the GBT material master.
   The characteristics are stored in customer fields in the material master (Hint: You can create customer fields for GBT material master using transaction COMM_ATTRSET).
   The characteristics have to be added to the GBT search and the material query needs to be enhanced.
   Instead of storing the characteristics as material attributes, the material class and the characteristics could be transferred to a GBT material class.
   
   Advantages:
   - No redundant storage of the characteristics
   Disadvantages:
   - GBT search has to be enhanced
   
2. Store the characteristics in the batch customer include.
   The characteristics are stored in the existing batch customer include.
   In GBT, the new attributes have to be added as batch search criteria to the GBT search.
   No enhancement is necessary in the coding for these additional search criteria.
   
   Advantages:
   - Less effort in GBT search
   Disadvantages:
   - Redundant storage of material characteristics
   - No usage in material search possible
   - Difficult to enrich newly created batches in GBT
   
3. Model the material characteristics as a product group.
   Depending on the number of characteristics needed for the search in GBT (e.g. up to3 if they are used together as search parameters), the material characteristics could be mapped to a product group.
   Product groups are already integrated in the GBT search.
   
   Advantages:
   - Low effort as most functionality already exists
   Disadvantages:
   - Only practical for a very small number of characteristics

Which of these alternatives is practical for your use case and the details should be discussed with a consultant.

Best regards,

Martin