| Status | Approved |
|---|---|
| Owner | Divya Nair |
| Stakeholders | Massimo Lietaert |
| Jira Request ID | https://syensqo.atlassian.net/browse/ERP-102 |
| Jira Development ID | ERP-172 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | S/4HANA |
| Business Process Reference |
Functional Overview
Foreign Trade Organization(FTO) and Legal Units(LU) are the organizational elements in GTS. These organizational elements are required to comply with the legal and customs requirements to allow execution of the respective country's import and export processes. Foreign Trade Organization (FTO) is the top level organizational unit in SAP GTS and it corresponds to the company code in the feeder system. Legal unit(LU) corresponds to the plant in the feeder system. FTO and LU are created as business partner in SAP GTS system with different roles. The objective of this application job is to automate the creation of the FTO and LU business partner in GTS by executing the report in the feeder S/4 HANA system.
Scope and Objectives
Foreign Trade Organization and Legal unit business partners are created manually in SAP GTS. Due to the huge volume of these organizational elements in Syensqo, creation of FTO and LU
business partner data is to be automated. Mapping of company code is 1: 1 and mapping of plants is also 1: 1. For every company code in feeder, only one FTO will be created in GTS. Similarly for every plant in feeder, only one legal unit will be created.
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
| 1. | Company codes are created in feeder system as a business partner | |
| 2 | Plants are created in feeder systems as a business partner | |
| 3 | Company codes to be replicated in GTS system as a business partner | |
| 4 | Plants to be replicated in GTS system as a business partner | |
| 5 | Map FTO to company code in GTS | |
| 6 | Map Legal Units to plants in GTS | |
| 7 | Assign LU to FTO | |
| 8 | Assign combination of plant and storage location to FTO |
Assumptions
- Company code must be available in S/4 HANA Feeder system.
- Plants must be available in S/4 HANA system.
- SAP GTS system should be available during transfer.
- Address elements like name, street, city , country etc are available in the feeder business partner.
Dependencies
Finance team will be responsible for the creation of company codes.
Supply Chain team will be responsible for the creation of plants and storage locations.
These are mandatory for the bp creation in GTS.
Security, Integrity and Controls
Master Data Specialist - Business Partner Data is the role for the BP transaction and it should be available for the application job to create bp.
Configuration Requirements
RFC connection should be established between the S/4 HANA and GTS E4H system.
Language Requirements
Special Requirements
Design Rationale
Functional Requirements
Existing process of creating the organizational elements FTO and LU is manual. In BP transaction , FTO and LU will be created one by one by referring to the data from the S/4 feeder.
Going forward, as part of this enhancement execution, company codes and plants will be replicated as business partners in GTS. For FTOs, the naming convention will be FTO_XXXX where XXXX will be the company code from S/4 feeder. For LUs, the naming convention will be LU_XXXX where XXXX is the plant from S/4 feeder.
For FTO, it should be created in 3 different BP roles -000000 Business Partner (General), SLLFTO(Foreign Trade Org) and FS0000(Financial Services BP).
For LU, it should be created in 3 different BP roles- 000000 Business Partner (General), SLLSIT(Legal Unit) and FS0000(Financial Services BP).
The BP fields which are usually populated for FTO and LU are : Name, Street/House number, Postal Code/City, Country, Region, Timezone. Communication details if available in feeder can also be copied including email, telephone etc.
Proposed Technology to Use
Data Source Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
| T001 | BUKRS | |
| T001W | WERKS | |
Data Validation Considerations
Only one to one mapping should exist between company code from feeder and FTO in GTS.
Similary one to one mapping for plants and legal units from feeder to GTS.
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
| T001 | BUKRS | Validate the company code using this table |
| T001W | PLANT | Validate the plant using this table |
Custom Tables
Master Data
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
| Company Code | Option | CHAR 4 | |||
| Plant | Option | CHAR 4 |
Processing Logic
Volumetrics
Performance Considerations
Error Handling
Any failures in the job must be logged for further review.
Testing
How to Test
Run the application job and validate in GTS system , the corresponding org units are created.
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
| 1 | Replicate a company code XXXX transfer via the application job | FTO_XXXX created in GTS with 3 different roles - BP General(0000000), SLLFTO, FS00000 |
| 2 | Replicate a plant YYYY transfer via the application job | LU_YYYY created in GTS with 3 different roles-BP General(0000000), SLLSIT, FS00000 |
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
Appendix
Custom Authorization Group Naming Convention
This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.
ABAP | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|---|---|---|---|---|---|---|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |