Hi Dave,
This is my requirement ...
**************************
- I. OVERVIEW
A. Business Driver
RMA (Returns, Replacement and Repair) specific fields are not part of standard interface during transfer of Document from ECC to GTS. Annex A in PDD identifies Fields are that are required to be transferred to SAP GTS. Certain fields are available when RMA specific Order is created in ECC.
B. Key business requirements
Compliance Team during review of Blocked Documents, require visibility to additional data to make informed decision whether Document under GTS Block can be released or not. Certain documents have to be released on priority and priority can be determined by SLA, Region, Customer etc.
C. High level Process overview
Documents (Sales Order Types and Delivery Order Types) are created in ECC. Upon creation, they are replicated in GTS as Customs Sales Order and Customs Delivery Order. The documents upon replication undergo various Compliance checks such as Sanction Party List Screening, Embargo Screening and Export License Screening.
The Documents can fail to pass such checks and will be blocked in GTS. Subsequent functions such as Delivery Creation with Reference to such Blocked Sales Orders or PGI (Post Goods Issue) with Reference to Blocked Delivery Orders cannot be performed in ECC till the referenced Blocked Documents are released in GTS.
- II. DETAILS
A. Detail Processing Logic:
To transfer additional Data during Sales Order creation (RMA specific Documents), SAP provides required user exits to influence Data Transfer.
Additional Data Field Mapping in ECC created specifically for RMA Orders
Required Data | Data Source | Source System |
Refurbished Indicator | Sales Order - Item Level | ECC |
Defective/Returns Indicator | Sales Order - Item Level | ECC |
| Sales Order - Item Level | ECC |
| Sales Order - Item Level | ECC |
Agreement / Contract No. | Sales Order - Item Level | ECC (Conditional) |
Service Level Agreement - SLA | Sales Order - Item Level | ECC |
Address Change Flag | Sales Order - Header Level Sales Order - Item Level | GTS (Partner Address Change) |
This user exit is available in the plug-in to to influence Sales & Distribution document data you transfer to SAP Global Trade Services(SAP GTS).
- /SAPSLL/GTS_CMOD_DOC - Transfer of MM and SD Documents (Enhancement Project SLLLEG01)
- Multiple user exists are available under this enhancement Project
- User Exits - EXIT_SAPLSLL_LEG_CDPIR3_001
- User Exits - EXIT_SAPLSLL_LEG_CDPIR3_002
- User Exits - EXIT_SAPLSLL_LEG_CDPIR3_003
This Data in GTS will be mapped in Additional Data Tab. Both Header and Item Level has includes that will hold the Data transferred.
- Header Table - /SAPSLL/CUHD
- Include - /SAPSLL/CUHD_CUST_S
- Item Table - /SAPSLL/CUIT
- Include - /SAPSLL/CUIT_CUST_S
There are limitations to how many Data Elements can be stored in the structures mentioned above. Before writing the TDD, the ABAP Team should investigate the possibility of implementation. The other alternative can be storing the Data in Z Table in GTS.
Address Change Flag (Additional Processing Logic)
This flag will be determined based on presence of New and Old Installed at site Address Partner Function in RMA Sales Order. A Z Field will capture the Flag if the Address changes occur and will be blank if the Address hasn’t changed.
B. Business Logic and Rules Definition
- By utilizing standard delivered enhancement spots, the interface that is responsible for replicating Orders in GTS.
- Restrict the replication of Data for specific Order Types. This would require a Z Table to be created in ECC to store the relevant Document Types.
- Original Installed at Site and Requested Installed at Site Address will be defined as Partner Functions and will be part of FS created to address Partner Function address changes at Transaction Level.
***************************
Regards,
Pratibha Aggarwal