Hierarchy

⤷

⤷

IMG Activity
ID | /SAPSLL/CUS_COM_PROC | Define Control Settings for Communication Processes |
Transaction Code | /SAPSLL/33000097 | (empty) |
Created on | 20030805 | |
Customizing Attributes | /SAPSLL/CUS_COM_PROC | Define Control Settings for Communication Processes |
Customizing Activity | /SAPSLL/CUS_COM_PROC | Define Control Settings for Communication Processes |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /SAPSLL/CUS_COM_PROC |
Use
In this Customizing activity, you define your communication processes with the customs authorities. When you are defining communication processes, you structure them and put each of the process steps into a logical sequence. You can also assign messages to each of the process steps. Furthermore, you prepare the system in such a way that users are only provided with process-relevant messages.
Requirements
You have completed the Customizing activity Define Messages for Communication Processes.
Standard settings
In the standard configuration of this activity, process flows for communication processes have been defined at the following levels: Process Template - Process - Activity - Messages and Process Template - Process - Activity Sequence - Subsequent Activities.
For example, process TRSO Open Transit Procedure in process template TRSDE Transit/Presentation - Germany (NCTS, SumD) already contains the following standard settings:
- Process template:
- TRSDE Transit/Presentation - Germany (NCTS, SumD)
- Processes:
- TRSC Complete Transit Procedure
- TRSO Open Transit Procedure
- TRSSU ePresentation / Safekeeping (SumD)
- Activities under TRSO Open Transit Procedure:
- TRDCV Simplified Procedure (CP)
- TRDEC Standard Procedure
- TRDOK Transit Procedure Completed
- TRDOV Transit Procedure Completed (CP)
- Messages for TRDCV Simplified Procedure (CP):
- I1110 Automatic Release (DE)
- I1120 Error Message (DE)
- I1130 Manual Release (DE)
- I1140 EDI Syntax Error (DE)
- M0110 Transit Declaration (DE)
- Activity sequence:
- TRDCV Simplified Procedure (CP)
- TRSO Standard Procedure
- Subsequent activities:
- TRDCV Simplified Procedure (CP)
- TRDOV Transit Procedure Completed (CP)
Activities
Perform the following activities:
- Assign an output determination procedure to a process template.
In the application, you determine a legal regulation using the appropriate service and the specified organizational unit. The legal code is assigned according to the service (for example, "7" for Transit/NCTS) and the country is assigned according to the foreign trade organization. The combination of country and legal code shows the active legal regulation that is applicable. In the application, you also choose the customs document type.
The process template, and thus the output determination procedure, for the legal regulation can be accessed from the data basis of the legal regulation and the customs document type. The direction of the goods movement is predefined by the customs document type. - Split the process template into processes
Splitting the process template into processes allows the application to offer only the processes that are of any relevance, based on the data entered.
- Split the processes into activities.
Activities can be used alone or in combination with other activities. For each activity, you can define the following details:
- Advance entry desired
- Participation in simplified procedure
- Required authorization type, if you have chosen the simplified procedure
- Declaration type
- Define an activity sequence
You can define an activity sequence to map the interdependencies between activities. The system then processes the activities within a process in the given sequence. You can define the following for each activity sequence:
- Document type and necessity of a supplementary customs declaration for an activity sequence
- Control settings for time of release and calculation of closing portions
- Manual processing or processing via the worklist
- Configure Determination Procedure for Dynamic Field Labels
- Procedure transitions within the activity sequence and the exact time at which these can occur, for example, when a message is received or when a customs declaration or customs shipment is created
- Visibility of the activity sequence in the individual processes in the application, for example, to transfer products from the customs warehouse to free circulation or for customs declarations prior to goods receipts.
- Assign messages to the activities
In this step, you can only assign messages from the output determination procedure if these messages have been assigned to the process template. Messages can be either outbound or inbound messages. Only one active electronic message is possible for each activity.
- Define a fallback activity sequence
If technical problems cause the customs authorities to instruct the company to process customs declarations in the fallback procedure for certain customs procedures or for a certain period, you have to submit printed SADs for the customs declaration, for example, instead of electronic messages. You assign the relevant messages to a fallback activity sequence, for example, for printing.
Then assign the necessary fallback activity sequence to the activity sequence for normal operations.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | 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_PROC | 0 | /SAPSLL/SLL0000003 | Global Trade Services |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
/SAPSLL/VC_TLEPS | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20050510 |
SAP Release Created in | 200 |