Lesson: Mapping Settings in SAP ERP
Lesson Overview
In the SAP ERP feeder system, you need to maintain settings for the transfer of master data and documents to SAP GTS. This lesson explains these settings.
Lesson Objectives
After completing this lesson, you will be able to:
• Explain the use of change pointers in master data distribution and set them up in the system
• Set up the transfer of documents to SAP GTS
Business Example
IDES AG intends to use SAP GTS in some of its branch offices. The company needs to check the required system settings.
Master Data Transfer Using Change Pointers
To be able to use SAP GTS in your foreign trade processes, you need to forward all relevant business partner records and material master records from your SAP ERP feeder system to the SAP GTS system. As your users may create or change master data at any time, you need to ensure that any changes relevant to SAP GTS are promptly transferred. Although the SAP ERP system does not generate Intermediate Documents (IDocs) for data distribution to SAP GTS, certain settings from the IDoc Interface can be used for regular master data transfer: message types and change pointers.
Many application programs create change documents for each change made to their objects (master data and documents). These change documents record changes to the application objects and usually specify the person who made the change and the time of the change. These change documents can be used in ALE and EDI scenarios but can also be used for SAP GTS to set what are known as change pointers, which allow the sending system to select all changed data records and send only these to the target systems.
For internal use by CSC only For internal use by CSC only
Figure 13: Change Pointers
You can specify in Customizing whether a message type works with the change pointer function. Message types are keys that indicate data that can be exchanged between systems in ALE or EDI scenarios, for example, MATMAS for material masters, CREMAS for vendor masters, and DEBMAS for customer masters.
They are linked to IDoc basic types defining the formatting structure of the data records that are to be sent. The change pointer creates a connection between change documents and the corresponding message type, for example the change document for the creation or change of a material master and the message type MATMAS. When it creates or changes a master record, the application program queries whether the change pointer mechanism is activated or not. If the function is active, a change pointer is saved to the database together with the application document and the change document.
You can evaluate change pointers by using program RBDMIDOC. This program is usually scheduled as a periodic background job but can also be executed directly using transaction code BD21. You can call this transaction from the ALE area menu via Tools → ALE → ALE Administration → Services → Change Pointers
→ Evaluate. In ALE and EDI scenarios, the program creates IDocs for new and changed master records. For data transfer from SAP ERP to SAP GTS, it generates RFCs instead.
Hint: Change pointers are stored in the data base of the SAP ERP system.
You should delete processed and obsolete change pointers at regular intervals using program RBDCPCLR. You can execute this program from the ALE area menu via Tools → ALE → ALE Administration →
For internal use by CSC only For internal use by CSC only
Unit 2: Basic Mapping Settings GTS200
Some applications have such flexible programs for inbound and outbound processing that you can choose whether or not each optional segment field of the relevant IDoc basis type is to be transferred. To do this, you create what is known as a reduced message type as a copy of a standard message type. Then you select the fields from the IDoc basis type linked to this message type whose content you want to be transferred to a particular target system.
Figure 14: Reduced Message Types for Master Data Transfer
You can create, change and display reduced message types from the SAP GTS area menu in the SAP ERP feeder system. Choose Activate Change Pointers for Reduced Messages on the Basic Settings tab page, enter the reduced message type, and select Create , Change or Display . The menu path in SAP NetWeaver Customizing is SAP NetWeaver Application Server → IDoc Interface / Application Link Enabling (ALE) → Modelling and Implementing Business Processes → Master Data Distribution → Scope of Data for Distribution → Message Reduction → Create Reduced Message Type (transaction code BD53).
When you create a new reduced message type, it is based on the most current IDoc basis type. First the required segments are selected and then only the fields in these segments that are marked in a standard SAP system as required fields.
These segments and fields are marked with a green background. Select a segment by highlighting it and clicking on the Select button.
Note: When you select a segment, only fields that are defined in a standard SAP system as required fields will be selected.
For internal use by CSC only For internal use by CSC only
To select additional fields for a selected segment, navigate to the detail view.
In the detail view, first select the additional fields, then click on Select again.
Optional segments or fields that have not yet been selected are marked with a red background. Optional segments or fields that have already been selected are colored white.
Caution: You have to click on the Select button before you can exit the detail screen by selecting Enter. If you select fields and then click on Enter immediately, your selection is not saved.
If the change pointer function is used for a reduced message type, only changes made to selected fields generate change pointers. You could thus create your own reduced message type(s) containing only the fields whose content is transferred to SAP GTS in addition to the required fields of the IDoc basis type. Thus only changes relevant for SAP GTS result in a re-transfer of a material, a vendor, or a customer master record from the SAP ERP feeder system.
Figure 15: Re-Transfer of Changed Master Data
By scheduling program RBDMIDOC as a periodic background job, you can ensure that new master records as well as changes to existing ones are promptly available in SAP GTS.
Note: In your SAP ERP feeder system, you will find three reduced message types for master data transfer to SAP GTS (/SAPSLL/CREMAS_SLL, /SAPSLL/DEBMAS_SLL and /SAPSLL/MATMAS_SLL).
For internal use by CSC only For internal use by CSC only
Unit 2: Basic Mapping Settings GTS200
Settings on Document Type Level
Before you can use SAP GTS functions, the logistics documents that are created in the SAP ERP feeder system needed for an import or an export process (for example, purchase orders, orders, and billing documents) require counterparts in the SAP GTS system.
Figure 16: Document Types: Settings (Example)
To ensure that relevant documents are replicated for all your processes, you have to flag the corresponding document types as relevant to SAP GTS in the SAP ERP feeder system. To do so, choose Sales and Distribution → Foreign Trade/Customs
→ SAP Global Trade Services - Plug-In → Control Data for to Transfer SAP Global Trade Services → Configure Control Settings for Document Transfer in the IMG.
You will find three so-called application levels for each basic process: MM0A, MM0B, and MM0C for goods receipts; and SD0A, SD0B, and SD0C for goods issues. Each application level groups together document types or goods movements according to their respective function in the process. For example, MM0A is the application level of purchase orders, and SD0C the application level of billing documents.
The details of each application level indicate for which groups of services it can be used. For example, sales orders (application level SD0A) can be transferred to SAP GTS for the use of the services of SAP Compliance Management and SAP Risk Management; billing documents (application level SD0C) can be transferred
For internal use by CSC only For internal use by CSC only
Exercise 1: Mapping of Document Types -Feeder System
Exercise Objectives
After completing this exercise, you will be able to:
• Link document types in the SAP ERP feeder system to document types in the SAP GTS system to use SAP GTS functions in import and export processes.
Business Example
Some goods receipt and goods issue processes in the model company are to undergo a foreign trade law audit.
Task:
Make sure that all orders entered using sales document type ZA## in your SAP ERP feeder system are transferred to the SAP GTS system for screening in SAP Compliance Management and for preference calculation in SAP Risk Management.
1. In Customizing, assign sales document type ZA## to application level SD0A (Dispatch / Export: Sales Document).
2. Flag the document type as being relevant to SAP Compliance Management and SAP Customs Management. The system should display a message if a document is blocked. You also want SAP GTS to set a preference indicator in sales documents of document type ZA##, where applicable.
For internal use by CSC only For internal use by CSC only
Unit 2: Basic Mapping Settings GTS200
Solution 1: Mapping of Document Types -Feeder System
Task:
Make sure that all orders entered using sales document type ZA## in your SAP ERP feeder system are transferred to the SAP GTS system for screening in SAP Compliance Management and for preference calculation in SAP Risk Management.
1. In Customizing, assign sales document type ZA## to application level SD0A (Dispatch / Export: Sales Document).
a) In the IMG, choose Sales and Distribution → Foreign Trade/Customs
→ SAP Global Trade Services - Plug-In → Control Data for Transfer to SAP Global Trade Services→ Configure Control Settings for Document Transfer.
b) Select the application level SD0A (Dispatch/Export: Sales Document) and double-click Document Types in the dialog structure.
c) Choose New Entries and enter document type ZA## in the DT fr.
Backend Syst. field.
2. Flag the document type as being relevant to SAP Compliance Management and SAP Customs Management. The system should display a message if a document is blocked. You also want SAP GTS to set a preference indicator in sales documents of document type ZA##, where applicable.
a) Set the indicators for Call Up SAP Compliance Management Services, Call Up SAP Risk Management Services, Output Dialog in SAP Global Trade Services and Set Preference Indicator in Feeder System.
b) To create the new entry, choose Save and exit the table.
For internal use by CSC only For internal use by CSC only
Lesson Summary
You should now be able to:
• Explain the use of change pointers in master data distribution and set them up in the system
• Set up the transfer of documents to SAP GTS
For internal use by CSC only For internal use by CSC only
Unit 2: Basic Mapping Settings GTS200
Lesson: Mapping Settings in SAP GTS
Lesson Overview
In the SAP GTS system, you need to maintain settings for the mapping of documents transferred from the SAP ERP feeder system. This lesson deals with these settings.
Lesson Objectives
After completing this lesson, you will be able to:
• Customize settings needed to map documents transferred from SAP ERP
Business Example
IDES AG intends to use SAP GTS in some of its branch offices. The company needs to check the required system settings.
Document Types and Item Categories
In Customizing for SAP GTS, you define document types as corresponding documents for the document types flagged in the SAP ERP feeder system (a set of model document types is supplied by SAP in client 000). You then need to assign these SAP-GTS-specific document types to the corresponding feeder system document types.
For internal use by CSC only For internal use by CSC only
SAP Compliance Management and SAP Customs Management each have to have their own sets of document types defined for them. SAP Risk Management uses the document types from the other two subsolutions (menu path in
the IMG: SAP Global Trade Services → SAP Compliance Management → General Settings → Document Structure → Define Document Types and SAP Global Trade Services → SAP Customs Management → General Settings
→ Document Structure → Define Document Types respectively). The SAP GTS-specific document type is assigned the control parameters that are essential for foreign trade processes (for example, number range keys, text determination procedures, and action profiles for communication with the authorities).
To assign document types from the feeder system to their equivalents in SAP GTS, choose SAP Global Trade Services → SAP Compliance Management → General Settings → Document Structure → Assignment of Document Types from Feeder Systems and SAP Global Trade Services → SAP Customs Management → General Settings → Document Structure → Assignment of Document Types from Feeder Systems respectively.
For some of the application levels, the same procedure is also necessary at item category level. First, you have to define SAP-GTS-specific item categories. You then assign these to the corresponding item categories from the SAP ERP feeder system. In SAP GTS, you usually need a smaller selection of item categories than those available in the feeder system.
Figure 18: Assign Item Categories
If there is no SAP GTS-specific item category for the item category transferred from the SAP ERP feeder system, the SAP GTS system creates the document for the feeder system document without the corresponding item data. The document
For internal use by CSC only For internal use by CSC only
Unit 2: Basic Mapping Settings GTS200
The user in the feeder system receives a message (“Item Type Mapping not Maintained”). To avoid this, opt for the function Automatically Transfer Item Category when maintaining the table for the assignment of item categories from the feeder system. Enter the logical system of the feeder system (or the system group, if there are several similar feeder systems), the application level, and the SAP-GTS-specific item category you want to use to “summarize” the item categories of the feeder system. The SAP GTS system will then retrieve all item categories from the feeder system and automatically assign the default SAP GTS-specific item category.
Organizational Units
In SAP GTS, you map your own company using the organizational units foreign trade organization and legal unit. These organizational units represent your company in regard to customs and foreign trade law. They are required to enable you to transfer documents from the SAP ERP system and to determine the legal regulation on which the functions of the services to be used are based.
Figure 19: Organizational Units
You define foreign trade organization and legal units as SAP business partners in SAP GTS (transaction code BP). It is imperative that you assign the correct business partner roles of Foreign Trade Organization (SLLFTO) and Legal Unit (SLLSIT), respectively. For the preference processing service in SAP Risk
For internal use by CSC only For internal use by CSC only
The foreign trade organization is assigned to at least one company code in the SAP ERP feeder system. If the foreign trade organization represents more than one company code to the authorities, you can also make multiple assignments.
A company code, on the other hand, can be linked to only one foreign trade organization. Likewise, a legal unit can be assigned to multiple plants, but a plant can be linked to only one legal unit. A foreign trade organization and legal unit(s) are linked to each other in Customizing for SAP GTS (SAP Global Trade Services
→ General Settings → Organizational Structure → Assign Legal Unit to the Foreign Trade Organization).
Note: If you want to use the “Preference Processing” service in SAP Risk Management, SAP recommends that you assign a legal unit in your SAP GTS system to each plant of your SAP ERP feeder system (see SAP Note 891338).
The two organizational units are required to enable you to transfer documents from the feeder system, among other things. If a foreign trade organization or legal unit or both cannot be identified in SAP GTS when you are attempting to transfer a document, you can create the document or save your changes in the feeder system.
However, the document will either not be replicated at all (services of SAP Customs Management) or replicated incompletely (services of SAP Compliance Management and SAP Risk Management). You will find incomplete replicates in SAP GTS calling transaction Display Technically Incomplete Documents (transaction codes /SAPSLL/CUHD_IC_EXP and /SAPSLL/CUHD_C_IMP respectively).
Partner Functions and Partner Groupings
You must define all the partner roles in the SAP ERP feeder system that are relevant for SAP GTS as partner functions in SAP GTS. When creating a partner function, you have to specify whether this function is to be used for goods receipts, goods issues, or both.
For internal use by CSC only For internal use by CSC only
Unit 2: Basic Mapping Settings GTS200
Figure 20: Partner Functions
In the Customizing of the SAP GTS system, choose SAP Global Trade Services
→ General Settings → Partner Structure → Define Partner Functions (the keys of the delivered partner functions correspond in part to the German partner roles in SAP ERP). Then choose Assignment of Partner Roles from Feeder Systems → Assign Partner Function at Feeder System Level → Manually Assign Partner Function. In this table, the SAP ERP feeder system partner roles are linked to the SAP GTS-specific partner functions.
To ensure that all partner roles used in inbound and outbound processes in the SAP ERP feeder system are known in the SAP GTS system, it is advisable to choose Automatically Transfer Partner Function when maintaining the assignment table. Set the Excl. Partn. Role indicator for all partner roles that should not be transferred from the SAP ERP feeder system at the time of document replication.
Not all partner functions in SAP GTS need to be linked to partner roles in the SAP ERP feeder system. In client 000, you will find a few partner functions for the purpose of customs processing that do not require an equivalent in the feeder system, for example, customs offices.
You then assign the partner functions to partner groupings, which are subsequently linked to individual services in SAP GTS. For example, if you intend to use the “Embargo Check” service, you define a partner grouping for each direction of goods movement (receipt/issue) and assign to it the partner functions
For internal use by CSC only For internal use by CSC only
Figure 21: Groups of Partner Functions
In Customizing, choose SAP Global Trade Services → General Settings → Partner Structure → Define Groups of Partner Functions. The system displays a list of preconfigured partner groupings for each of the SAP GTS services. For
In Customizing, choose SAP Global Trade Services → General Settings → Partner Structure → Define Groups of Partner Functions. The system displays a list of preconfigured partner groupings for each of the SAP GTS services. For