Skip to Content

This document detail how we can connect  SAP Feeder system to SAP GTS system  for Master Data and Transaction Data transfer.:


Data Exchange Between SAP Feeder and SAP GTS system

/wp-content/uploads/2014/10/15_555853.png

ERP and GTS system are more often separate system with respective software installed onseparate  machine, One Client will be ERP and other Client will be GTS. ERP System which connects to GTS is called Feeder System.

This is the basic GTS architecture how it talk to Feeder System ,  all the  master  data like Material ,customer vendor and all the transaction data like sales  order  delivery  billing  doc get  pushed to GTS through RFC ( Remote Function Calls) . And any message back to Feeder system flows through RFC call.

For above mentioned Data exchange to happen, RFC connection has to be established in between two systems.



SAP Global Trade Services (SAP GTS) uses a feeder system to provide  the logistics  data. SAP GTS  uses feeder system data to perform certain activities or start processes within SAP GTS.

You need the following data, for example, to use the services in SAP GTS:

Master data records for

  • Customers
  • Vendors
  • Employees (if integrated SAP HCM is used)
  • Materials
  • Bank data (if financial and insurance systems are integrated)

Document data

  • Sales orders
  • Purchase orders
  • Billing documents

To transfer data from the feeder system to SAP GTS, you need to set  up the  system communication between the feeder system and SAP GTS. You must specify certain communication prerequisites, for example:

  • Logical system
  • RFC destination
  • ALE distribution model


Setting in ERP (Feeder system)

/wp-content/uploads/2014/10/16_555855.png

Use Transaction code /n/SAPSLL/MENU_LEGALR3 to go to GTS Area menu of Feeder system —>Tab Basic settings—>System Connection to SAP GTS

  a.  Define Logical System:

Need to define Logical system for both ERP and GTS system. The logical system name uniquely identifies the client of an SAP system or non-SAP system in the system landscape.

You can also use Tcode BD54 to define the logical system

/wp-content/uploads/2014/10/17_555856.png

Here you have to define both ERP logical system (FED510) as well as GTS logical system (GTS500)

For logical system  name  to  be  unique  and  to  simplify  the assignment, it is recommended  of  using  the naming convention <System name><Client key>. Eg. FED (system name) 100(client), GTS500

b. Assign Logical System:

Here actually when u get in you will see the physical system detail on which you are logged in, suppose you are on ECC you will find detail of Feeder system with different clients. Some client will come as default like 00 which is Waldrof client the SAP client and other are those which are created at the time of installation. Here you have to assign the logical system of Feeder to the physical system client combination on which you logged in. You will find a field of logical system on the top once you get in detail of the client system combination. Now here you have assigned the Logical system of Feeder this is required as when GTS will communicate with Feeder it will try to look  for Feeder  logical system  as  for RFC connection you always define logical system to which the system will talk.

/wp-content/uploads/2014/10/18_555857.png

Tcode SCC4 can also be used to Assign Logical System.

c. Define RFC Destination:

Here you define the Target host, IP address and logon detail like language, client, user password. You need to define the detail for GTS for RFC connection and so you need the logical system name of GTS here. Basically it contains all the Technical Detail for system call. Tcode SM59

/wp-content/uploads/2014/10/19_555858.png

d.  Maintain RFC Destination for Method Call:

To enable calls of cross-‚Äźsystem function modules, you need to define the standard connection for method calls. You do this by assigning the Remote Function Call (RFC) destination you defined in the preceding step for SAP GTS .Tcode BD97

If your SAP GTS logical system is GTS500 and RFC Destination is also defined with same name GTS500, then the assignment happens as follows. (The Detail of this assignment you can find in table TBLSYSDEST if for some reason we get an error that RFC destination for GTS is not maintained then first place is to check is this table to confirm whether for the defined GTS logical system entry has been maintained or not which get populated from following settings.)

Feeder System: FED100

SAP GTS: GTS500

Standard RFC Destination for BAPI Calls: GTS500

/wp-content/uploads/2014/10/20_555859.png

e. Maintain ALE Distribution Model:

You need to create a model view of an Application Link Enabling (ALE) model. In addition to defining the sender and recipient for the data exchange information, you also need  to  select  an  interface  and an object. The object type contains methods that ensure that all necessary data is transferred. Tcode BD64

Step to create ALE Model:

  • Choose Create Model View to create a new distribution model.
  • Select the model view and choose Add BAPI.
  • Enter the name of your feeder system (sender).
  • Enter the name of SAP GTS (recipient).
  • Assign CustomsDocumentIF as the object/interface
  • Assign SynchronizeR3 as the method

    

Suppose you Create Dist model called TEST_LEG. So you will assign CustomsDocumentIF as object/interface and SynchronizeR3 as method to the sender FED100 and receiver GTS500.  Where FED100 and GTS500 are defined Logical System

/wp-content/uploads/2014/10/21_555860.png

Suppose a sales order is created in the SAP ERP feeder system FEEDER in order to transfer its data to the SAP GTS system, the application program in FEEDER checks the local distribution model, identifies SAPGTS as the receiver, and searches for a suitable RFC destination thus the purpose of the BAPI CustomsDocumentIF.SynchronizefR3 is  to use the distribution model for determination of the  RFC receiver.

Setting in SAP GTS

Similar steps as of Feeder system has to be repeated in GTS fro RFC connection.

a.       Define Logical System : SPRO Path:

SAP Global Trade Services–>System Communication–> Define Logical System

  You can also use Tcode BD54 to define the logical system. 

          Feeder system: FED100

          GTS system:     GTS500

    /wp-content/uploads/2014/10/22_555861.png

b.    Assign Logical System  :

Assign GTS Logical system to GTS Client

SPRO Path: SAP Global Trade Services–> System Communication –> Assign Logical System
/wp-content/uploads/2014/10/23_555862.png

Tcode SCC4 can also be used to Assign Logical System.

 
      c.       Define RFC Destination :

Define the Target host, IP address and logon detail like language, client, and user password. You need to define the detail for Feeder for RFC connection and so you need the logical system name of Feeder here. Basically it contains all the Technical Detail for system call. Tcode SM59.

You  can find  the relevant  transaction in the  SAP GTS  menu  in  the SAP  GTS system (transaction

/SAPSLL/MENU_LEGAL). In the System  Administration  area,  choose System Communication/Workflow and, in the next screen, choose Maintain Target System for RFC Calls

/wp-content/uploads/2014/10/24_555863.png

d.       Maintain RFC Destination for Method Call:

You do this by assigning the Remote Function Call (RFC) destination you defined in the preceding step for Feeder System .Tcode BD97.

You  can  find the  relevant transaction  in  the SAP  GTS menu in the  SAP GTS  system  (transaction

/SAPSLL/MENU_LEGAL).    In  the System Administration area, choose  System  Communication/Workflow and, in the next screen, choose Maintain RFC Destination

If you’re SAP Feeder logical system is FED100 and RFC Destination is also defined with same name FED100, then the assignment happens as follows:

SAP GTS: GTS500

Feeder System: FED100

Standard RFC Destination for BAPI Calls: FED100

/wp-content/uploads/2014/10/25_555864.png

. e.    In addition to above mentioned steps you need to define “group of logical systems.” This   Group comprises feeder systems with similar properties, for example, identical material or   Partner data. Such a system group is also required to connect only one feeder system to the SAP GTS   system. If you assign several feeder systems to a system group, you need to transfer a Material or   a partner master record only from one of these feeder systems. The master record in SAP GTS will always be created on the system group level, for example, one product master per System group.

Define the Logical System Group

         SPRO Path: SAP Global Trade Services–> System Communication-> Define Group of Logical System

/wp-content/uploads/2014/10/26_555866.png

GTSFEDGRP for Feeder System and GTSGTSGRP for GTS system.

  Assign the Logical System to Group of Logical System

SPRO Path: SAP Global Trade Services–>System Communication –>Assign the Logical System to Group of Logical System

Note:

Here you have to assign logical systems to a group of logical systems.  You have to  assign  each  logical system to a group of logical systems, regardless of whether you want  to  connect  one or  more feeder systems to your SAP GTS. A logical system group can contain only your feeder systems or the SAP GTS system.

/wp-content/uploads/2014/10/27_555867.png

Both Feeder and GTS logical system has to be assigned to Logical system group even if there are only one Feeder and one GTS system.  And it is advisable to assign them to separate Logical System group.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply