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

 In SAP GTS, an Intrastat Inbound flow involves capturing data from an IBD or GR in an ERP system and transferring it to GTS for Intrastat Declaration processing.

There are cases when for indirect materials coming from Ariba Guided Buying, goods without material master data such as: laptop, supplies or even services to be having missing classification and free text mentioned on the PO. At the time of the PO creation in S/4 and send it to GTS, the information received will be incomplete; the Intrastat Specialist User will require additional data on the declaration in GTS in order to make a better idea of the item used; for this the Intrastat Inbound Declaration will have to be enhanced with other data coming from S/4 like: Vendor and Material Group description (PO source).

Process Flow Diagram

Assumptions

1. SAP GTS & S/4HANA interface connection available.
2. SAP GTS configuration settings performed.

Dependencies

N/A

Security, Integrity and Controls

N/A

Configuration Requirements

In GTS

Mandatory:

1. Create Business Partner with BP Role as: SLLFTO, SLLPOI, General and Financial Services.
2. Create Provider of Information for the respective BP.
3. Define the necessary Business Transaction types.
4. Activate Legal Regulation
5. Define Country of Origin
6. Assign Country of Origin to Countries of Declaration

Optional:

1. Define Partner Countries
2. Assign Partner Countries to Countries of Declaration
3. Define Movement Codes
4. Define Modes of Transport at the Border
5. Define Incoterms

In S/4: ensure Intrastat-relevant data is maintained such as: commodity codes, country of origin and vendor/material master data.

Language Requirements

EN only.

Special Requirements

N/A

Design Rationale

Functional Requirements

For Intrastat Inbound flows, the POs from S/4HANA will trigger the creation of the declaration in GTS. For cases when POs are missing its master data (free text only), or when classification missing, it required to enhance the declaration in GTS with other data in order to provide a better clarity on the item used.

Therefore, following data must be added to the standard Fiori App “Manage Intrastat Declarations” ,under Additional data Tab for those whose length is 20 and 40.

• Material group description → assign it to CHAR 40

• Supplier name → assign it to CHAR 40

• Supplier number → assign it to CHAR 20

Proposed Technology to Use

BADI /SAPSLL/INTRASTAT_SELECTION in SAP S/4HANA.

The fields on a PO transactional level can be found as:

• T023T-MATKL-WGBEZ for Material group's description
• EKKO-LIFNR for Supplier number
• LFA1- LIFNR-NAME1 for Supplier description

See Processing Logic for more details.

Data Source Considerations

N/A

Data Validation Considerations

N/A

Custom Tables

N/A

Master Data

N/A

Configuration Table

N/A

Selection Screen Enhancement

N/A

Processing Logic

Note: Trigger this logic only when material number (MATNR) is missing on the Purchase Order (EKPO-EBELN = RDNUM inside the BADI).

BADI /SAPSLL/INTRASTAT_SELECTION

Method CHANGE_DATA use parameter CT_DECL_ITEMS_FS

Within component types: /SAPSLL/ADDF4, /SAPSLL/ADDF5/, /SAPSLL/ADDF2 link it to the below EKPO & dependencies technical fields and send it to GTS within ADDA* fields. Ensure the length is matching between S/4 - GTS additional data fields (20, 40 CHAR).

Based on the PO number (EKPO-EBELN = RDNUM inside the BADI):

• Take MATKL (material group) from EKPO and pass it into T023T (as MATKL key) to retrieve WGBEZ. Eventually link it to the ADDF4 of the BADI parameter → sends to GTS
• Take LIFNR (Supplier number) from EKKO and link it to the ADDF2 of the BADI parameter → sends to GTS
• For supplier's name see below options to pick it up:
  • Option 1: Take LIFNR from EKKO and pass it into LFA1 (as LIFNR key) to retrieve NAME1 (Supplier description). Eventually link it to the ADDF5 of the BADI parameter → sends to GTS
  • Option 2: Once the PO arrives to GTS is automatically linked to the Provider of Information App (as part of Intrastat process) which contains the Business Partner/Vendor. The name of the Vendor will be therefore automatically assigned by the system.

Volumetrics

N/A

Performance Considerations

N/A

Error Handling

N/A

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Purchase Orders must be first created in S/4HANA. 

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