SAP ABAP IMG Activity /SAPSLL/GTS_BADI_RFC (BAdI to Change RFC Destination for Calling SAP GTS)
Hierarchy
☛ SLL_PI (Software Component) GTS Plug-In
   ⤷ SD-FT (Application Component) Foreign Trade
     ⤷ /SAPSLL/PLUG_IN_R3 (Package) Legal Services: PI Functions and PI Services
IMG Activity
ID /SAPSLL/GTS_BADI_RFC BAdI to Change RFC Destination for Calling SAP GTS  
Transaction Code /SAPSLL/91000076   (empty) 
Created on 20050407    
Customizing Attributes /SAPSLL/GTS_BADI_RFC   Change to RFC Destination for Calling SAP Global Trade Services 
Customizing Activity /SAPSLL/GTS_BADI_RFC   Change to RFC Destination for Calling SAP Global Trade Services 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /SAPSLL/GTS_CMOD_EN    

Use

SAP Global Trade Services (SAP GTS) is supplied with logistics data such as sales, delivery and purchasing document data, from feeder systems. The feeder systems may be mySAP ERP or mySAP CRM, for example, or it may be a third-party system. Remote Function Calls (RFCs) are required to facilitate the communication between separate systems. You have to define RFC destinations in the Plug-In (transaction /SAPSLL/MENU_LEGALR3) and you dalso efine here which document data you want to have replicated in SAP GTS.

This Business Add-In (BAdI) enables you to override the standard settings you made for transferring document data in the plug-in for the following feeder system documents:

  • Sales orders
  • Outbound deliveries
  • Billing documents
  • Purchase orders
  • Inbound deliveries
  • Inbound deliveries (temporary storage)
  • Goods movements

For more information, see Help --> Application Help.

Requirements

You have installed and configured SAP GTS in accordance with the sections on System Communication and Data Replication in the Business Scenario Configuration Guide in SAP Service Marketplace at http://service.sap.com/instguides -> SAP Components -> SAP Global Trade Services -> Using SAP GTS 7.0.

Standard settings

Activities

The BAdI consists of the following methods:

  • CHANGE_RFC_DEST_SD0A
    This method allows you to overwrite the standard logic for RFC destinations for sales orders. You can use the following parameters to do this:

    Importing:
    - IS_HEADER
    Sales order: header data
    - IT_PARTNER
    Table for structure VBPAVB
    - IT_BUSINESS_DATA
    Table for structure VBKDVB
    - IT_ITEM
    Table for structure VBAPVB

    Changing:
    - CV_RFC_DEST
    Logical destination (provided in function call)
  • CHANGE_RFC_DEST_SD0B
    This method allows you to overwrite the standard logic for RFC destinations for outbound deliveries. You can use the following parameters to do this:

    Importing:
    - IS_HEADER
    S&D inbound delivery document: header data
    - IT_PARTNER
    Table type for partner (structureVBPAVB, standard key)
    - IT_ITEM
    Inbound deliver item (upward compatibility)

    Changing:
    - CV_RFC_DEST
    Logical destination (provided in function call)
  • CHANGE_RFC_DEST_SD0C
    This method allows you to overwrite the standard logic for RFC destinations for billing documents. You can use the following parameters to do this:

    Importing:
    - IS_HEADER
    Billing document: header data
    - IT_PARTNER
    Table for structure VBPAVB
    - IT_ITEM
    Billing document: item data

    Changing:
    - CV_RFC_DEST
    Logical destination (provided in function call)
  • CHANGE_RFC_DEST_MM0A
    This method allows you to overwrite the standard logic for RFC destinations for purchase orders. You can use the following parameters to do this:

    Importing:
    - IS_HEADER
    Purchasing document: header data
    - IT_ITEM
    Table type BEKPO

    Changing:
    - CV_RFC_DEST
    Logical destination (provided in function call)
  • CHANGE_RFC_DEST _MM0B
    This method allows you to overwrite the standard logic for RFC destinations for inbound deliveries. You can use the following parameters to do this:

    Importing:
    - IS_HEADER
    S&D document: Outbound delivery: header data
    - IT_ITEM
    Outbound delivery item (upward compatability)

    Changing:
    - CV_RFC_DEST
    Logical destination (provided in function call)
  • CHANGE_RFC_DEST_MM0B_SK
    This method allows you to overwrite the standard logic for RFC destinations for inbound deliveries (temporary storage). You can use the following parameters to do this:

    Importing:
    - IS_HEADER
    S&D document: Inbound delivery: header data
    - IT_LIPS
    Inbound delivery item (upward compatability)
    - IT_MSEG
    Inbound delivery interface structure for material document

    Changing:
    - CV_RFC_DEST
    Logical destination (provided in function call)
  • CHANGE_RFC_DEST_MM0C
    This method allows you to overwrite the standard logic for RFC destinations for goods movements. You can use the following parameters to do this:

    Importing:
    - IT_XMKPF
    - IT_XMSEG
    - IT_XVM07M

    Changing:
    - CV_RFC_DEST
    Logical destination (provided in function call)

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on POLLOCZEK  20060516 
SAP Release Created in 600