Hierarchy
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation⤷
SLL-LEG (Application Component) Global Trade Services⤷
/SAPSLL/CORE_LEGAL (Package) Legal Services: Core Functions
IMG Activity
| ID | /SAPSLL/CUS_COM_EXPL | Required Steps for Setting up Communication Processes |
| Transaction Code | /SAPSLL/33000110 | (empty) |
| Created on | 20030805 | |
| Customizing Attributes | /SAPSLL/CUS_COM_EXPL | Steps Required to Set Up Communication Processes |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPSLL/CUS_COM_EXPL |
Use
To use printed or electronic communication with the customs authorities, you have to fulfill the technical prerequisites for the communications processes in addition to the process-specific settings. This IMG activity describes the various settings in SAP NetWeaver that you need to configure to meet the technical requirements, with a brief explanation of each. The described settings are part of the standard SAP applications IDoc Interface / Electronic Data Interchange and Activate HTTP Services
Requirements
Standard settings
Activities
- System connection to EDI converter
In addition to system communication between your feeder system and GTS, you also have to configure the system connection between SAP GTS and your converter. This converter encodes the data formats of the messages to exchange between SAP GTS and the customs authorities and then forwards the messages. SAP GTS uses inbound and outbound IDocs for this communication, with the IDoc types assigned to namespace /SAPSLL/*.
You have to configure the following settings for the system connection to the EDI converter:
- Configure RFC connection to converter
- Define your converter's RFC destination.
- Define ports for IDoc processing
- Define a and assign it the RFC destination for the converter call.
- Define partner agreements
- For the converter to recognize the message destinations, you have to define partner agreements for all communication partners (usually the customs offices with which you exchange data). You define the message destinations for IDocs in partner agreements, which tells the system how to process the IDocs. For outbound IDocs, the system assigns the appropriate port for the customs office based on the customs office information. It can post inbound IDocs correctly based on the information from the partner agreement. You have to define partner agreements for both the customs offices and the converter for inbound IDocs.
- To enter partner agreements completely, you have to meet the following prerequisites:
- - The customs offices and the converter must be defined as master data
- - You maintain the business partner number of the of the customs office for communication with the customs offices, and assign this number in the partner agreement
- - You have to enter the partners as Business Partners (partner type BP) within the partner agreement
- Activate the content service
To enable the sending and receipt of attachments in electronic messages, you have to activate the HTTP services on the content server. The system then uses this content server to store export accompanying documents and export endorsements, for example, that the customs authorities send you as e-mail attachments. The system also uses this server to store attachments for authorizations and securities, as well as upload files.
To activate this service, you have to do the following:
- Create a user with type Service in user management. For more information about user types, see User Type.
- Activate the content server.
- Assign the content server to the Service type user.
For more information about HTTP services, see the SAP Library at help.sap.com -> SAP NetWeaver -> SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> Platform-Wide Services -> Connectivity -> Components of SAP Communication Technology -> Internet Communication Framework.
Example
You can use the following message types for transit processing, for example, and assign them in the partner agreement:
Legal area Activity Message Type Direction
Transit Open transit /SAPSLL/TRS_DEC (GTS Out: Customs: Transit: Open) Outbound message
/SAPSLL/TRS_INBOUND (GTS In: Customs: Transit: Reply Messages) Inbound message
Dispatch transit /SAPSLL/TRS_AN (GTS Out: Customs: Transit: Closing Notification of Receipt) Outbound message
/SAPSLL/TRS_UR (GTS Out: Customs: Transit: Closing Conformity) Outbound message
/SAPSLL/TRS_INBOUND (GTS In: Customs: Transit: Reply Messages) Inbound message
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /SAPSLL/CUS_COM_EXPL | 0 | /SAPSLL/SLL0000003 | Global Trade Services |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20030808 |
| SAP Release Created in | 200 |
