| Status | Revision in progress |
|---|---|
| Owner | TATARU-ext, Eugenia |
| Stakeholders | |
| Jira Request ID | ERP-59 - Getting issue details... STATUS |
| Jira Development ID | ERP-843 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | GTS |
| Business Process Reference | 12.03.04.01 Manage Intrastat Inbound |
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).
Step | Description | Comment |
|---|---|---|
| 1 | Send PO from S/4HANA | |
| 2 | Send Return PO from S/4HANA | |
| 3 | Receive data feeder system in Intrastat Declaration | |
| 4 | Manage Intrastat Declarations Fiori App | Enhancement related |
Assumptions
- SAP GTS & S/4HANA interface connection available.
- SAP GTS configuration settings performed.
Dependencies
N/A
Security, Integrity and Controls
N/A
Configuration Requirements
In GTS:
- Create Business Partner with BP Role as: SLLFTO, SLLPOI, General and Financial Services.
- Create Provider of Information for the respective BP.
- Define the necessary Business Transaction types.
- Activate Legal Regulation
- Define Partner Countries
- Assign Partner Countries to Countries of Declaration
- Define Country of Origin
- Assign Country of Origin to Countries of Declaration
- Define Movement Codes
- Define Modes of Transport at the Border
- 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:
EKPO-MATKL for material group (description)
EKPO-LIFNR for Supplier (number and description)
Data Source Considerations
N/A
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
N/A
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
N/A
Master Data
N/A
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
N/A
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
N/A
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
BADI /SAPSLL/INTRASTAT_SELECTION
Method CHANGE_DATA use parameter CT_DECL_ITEMS_FS
Within component types: /SAPSLL/ADDF1, /SAPSLL/ADDF2/, /SAPSLL/ADDF3 link it to the below EKPO technical fields and send it to GTS within ADDA1, ADDA2, ADDA3 fields. Ensure the length is matching between S/4 - GTS additional data fields (20, 40 CHAR).
- EKPO-MATKL for material group (description)
- EKPO-LIFNR for Supplier (number and description)
Volumetrics
N/A
Performance Considerations
N/A
Error Handling
N/A
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
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 |
