High- Level Specification

Functional Overview

The functional design of the enhancements describes the scenario(s) where enhancements to existing SAP programs are required.

Scope and Objectives

1. Organizational Context: GBUs and Legal Entities

Syensqo operates through several Global Business Units (GBUs). Each GBU has its own sales processes and revenue recognition procedure and serves as a commercial representation of the Syensqo organization.

These GBUs are active across multiple countries, which requires the use of legal entities (Company Codes) to manage local operations and ensure regulatory compliance - this represents the operational view of Syensco. 

• In some cases, a legal entity is dedicated to a single GBU.
• In other cases, one legal entity may serve multiple GBUs, resulting in a shared use of financial systems and transactional data across different units.

2. Current Situation in GTS 

In the current Global Trade Services (GTS) system, product- level segregation by GBU is missing, with the exception of Composite Materials (CM). This lack of segmentation makes it difficult to: 

• Identify the responsible business contact for classification questions
• Process license requests accurately
• Link the right Customer Service Representative (CSR) to specific products in compliance scenarios

3. Objective

The goal is to extend GBU identification to all product types in the new GTS e4H system, not just Composite Materials

To support this, the system must be enhanced to assign a GBU tag to each product during material replication from S/4HANA to GTS. 

4. Proposed Solution and Logic

A new logic will be introduced to ensure proper GBU tagging: 

• When a product is extended to a plat in S/4HANA, it will be replicated to GTS.
• At the time of replication, the product will be tagged with its corresponding GBU.
• This tag will be stored as an Additional Characteristic in the GTS Product Master to allow for GBU-level filtering and reporting.
• The GBU value will be derived from the Profit Center assigned in the Material Master in S/4HANA.

5. Business Benefits of GBU Segregation

Introducing the GBU field in GTS will: 

• Help Customer Service and Compliance teams find the correct point of contact for product classification or supplier-related questions. 
• Support license management, where identifying the GBU responsible is often required.

Process Flow Diagram

Assumptions

Dependencies

None.

Security, Integrity and Controls

There is no specific security required for this enhancement

Configuration Requirements

The following configuration will be completed in GTS, based on this enhancement:

1) Define Product Characteristics from the feeder system →  define the attribute technical name.

2) Assign Field attributes to the product characteristics from the feeder system → assign field length to the attributes defined at step 1.

3) Define Attributes of Product Characteristics with Length 01 → define possible values for the attribute.

Below is the list of relevant tables for this functionality:

• /SAPSLL/PRGEN - Product attributes in GTS
• /SAPSLL/TCOATR - Definition of characteristics from feeder system
• /SAPSLL/TCOATC - Generic settings for general attributes maintenance
• /SAPSLL/TCOATA - Control of general attribute maintenance - assignment of attributes

Language Requirements

TBC

Special Requirements

Design Rationale

Functional Requirements

Current functionality: The Composites business has export controlled products under EAR and ITAR Regulations, and Composition data is considered export controlled technology. The Composition data of ITAR and Certain EAR items must be secured and limited to only US citizens. For that reason, the SBS-CCT-CTC organization in the US will manage the HTS classification for Composites in all countries. At the moment, the SBS-CCT-CTC Team is located in Lisbon supporting all other GBU’s by managing the HTS Classification in GTS for all countries. The Composites structure creates the requirement to segregate the products to be classified by Lisbon from the products to be classified by the US Team. 

To-be functionality: Sends GBU(Profit Center) for all material types across all S/4HANA systems available based on logical system and plants maintained. Use table material/plant combination on S/4HANA side and send the profit center/GBU via standard user exit of the GTS S/4HANA plugin. Simple data mapping needed to update master data in GTS client.

Proposed Technology to Use

S4 user exit: EXIT_SAPLSLL_LEG_PRR3_004

Data Source Considerations

N/A

Data Validation Considerations

N/A

Custom Tables

N/A

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

1 GBU =1 Profit Center. 

Reference table = MARC -PRCTR

Scenarios:

1. If 1:1 material/plant → sends '1' GBU available under that combination and take it from MARC-PRCTR.
2. If 1:n material/plant → sends 'n' GBU available for same material by taking it from MARC-PRCTR to GTS under the configured field. If more than one Business unit was found to the product, Business unit should be separated by a “,”.

Volumetrics

Performance Considerations

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

In case of a change in the GBU/Profit Center value of the Product inside master data, this change will reflect to GTS, only if a dedicated user will collect all impact products and send them via GTS area menu in an S/4HANA system, as /SAPSLL/MENU_LEGALR3.

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