Ansicht
Dokumentation

/GBT/EX_PARTY_ID - BAdI: B2B SOA Integration Sender Party Identification

BAL Application Log Documentation   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Global Batch Traceability (CA-GBT) component. You can use this BAdI to identify the sender party, and map this party in SAP Global Batch Traceability to the appropriate logical system.

This BAdI is called in the following service interfaces:

• TrackedGoodsMaterialBulkReplicateNotification_In

• TrackedGoodsPartyBulkReplicateNotification_In

• TrackedGoodsLocationBulkReplicateNotification_In

• TrackedGoodsMovementNotification_In

For more information about the standard settings (filter, single or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).

You can use the /GBT/EX_IL_B2B_PARTY_IDENTIFNT default implementation to identify the sender party, and map this sender party to the appropriate logical system. The following information must be available in the message header, to enable the identification and mapping:

• CreationDateTime

• SenderBusinessSystemID or the standard ID in field SenderParty, for example, a D-U-N-S number, GLN, or SCAC

If you deactivate the default implementation, you must activate your own BAdI implementation.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

GET_MAPPED_LS_FROM_MSG_HDR:
This BAdI method gets the logical system that is mapped to the appropriate sender party. The logical system is needed to determine which data belongs to which sender party.

General Material Data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 2749 Date: 20240607 Time: 092231     sap01-206 ( 101 ms )