High- Level Specification

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.

Assumptions

1. Company code must be available in S/4 HANA Feeder system.
2. Plants must be available in S/4 HANA system.
3. SAP GTS system should be available during transfer. 
4. 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

N/A

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

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.

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

On entering company code details in the select option and run the program , the program should validate the entries are company codes. Error should be shown if the details entered in selection screen are not valid company codes. 

And then fetch the relevant business partner master data from feeder including Name , Street/House number, Postal Code/City, Country, Time zone. If communication relevant details are present in the bp master data including language, telephone, email etc. 

And in GTS system , corresponding to this company code, BP master data should be created and available in transaction BP with all the fields populated. 

Three roles are to be created for the FTO(Foreign Trade Organization ) in GTS - 000000 Business Partner (General), SLLFTO(Foreign Trade Org) and FS0000(Financial Services BP).

Similarly on entering plants in the select option and run the program, prgoram should validate the entries are plants. Error should be shown if the details entered in selection screen are not valid plants. 

And then fetch the relevant business partner master data from feeder including Name , Street/House number, Postal Code/City, Country, Time zone. If communication relevant details are present in the bp master data including language, telephone, email etc. 

And in GTS system , corresponding to this plant, BP master data should be created and available in transaction BP with all the fields populated. 

Three roles are to be created for the Legak Unit(LU) in GTS -000000 Business Partner (General), SLLSIT(Legal Unit) and FS0000(Financial Services BP).

There should be option to run this program in simulation mode and check the details. 

A log should be generated with the details of transfer  and also record any errors duirng transfer. 

It should be possible to execute this report in background as well. 

Volumetrics

This program should be run as part of cutover task to have all the company code and plants to be created in GTS same as the feeder system S/4. Also after go-live , if any new company codes/plants  are created/changed, it should be possible to transfer them as well.  

Performance Considerations

As part of Syensqo,we have more than 3000 + company codes and plants and the number may vary. So the program should be able to handle this transfer. 

Error Handling

Any failures in the report 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

Test Considerations/Dependencies

For this report to work, company codes and plants are to be available in S/4 HANA. 

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

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.

See also

Change log