/SAPSLL/SCD_PROCESS_AUTO - Process Supplementary Customs Declarations AutomaticallyROGBILLS - Synchronize billing plans ABAP Short Reference
This documentation is copyright by SAP AG.
You can use this report for the automatic processing of supplementary customs declarations to automate the transmission of changed data by using a change SCD.
At the present time, this scenario is only supported for the supplementary customs declaration for release to free circulation under ATLAS.
In the overview list, press the "Supplementary Customs Declaration" button to go to the corresponding SCD document. If the focus is on the column with the item number of the SCD, this item is accessed directly.
In the overview list, press the "Customs Declaration" button to go to the corresponding customs declaration document. If the focus is on the column with the item number of the customs declaration, this item is accessed directly.
You can restrict the selection for the overview list using the following document data in the supplementary customs declaration: Foreign trade organization, document number, year, settlement period, registration number, authorization number, and processor.
The creation date of the supplementary customs declaration is also available as a selection criterion.
You can also restrict selection by the document number and year of the customs declarations referenced in the SCD documents.
The processing type determines which actions can be executed in the overview list.
Set the "Save Log" indicator if you want to save the processing log in the database. You can then display the log in transaction SLG1 (object /SAPSLL/CUPED, subobject /SAPSLL/CUPED_LOG).
The overview list only selects the SCD items that meet the following conditions:
- The transmission status is not "Sent"
- The status for manual postprocessing is not "Required".
In addition, only those SCD items that meet the following criteria are selected:
- The "Control of Periodic SCD" flag has value "E" (entered in periodic SCD – changed after registration)
Or the following criteria:
- The supplementary customs declaration contains a deadline that has expired, and
- The transmission status of the item is "Processed Positive" or "Processed with Warnings", and
- No tax statement (interim or final) exists for the item
When you select at least one line and execute the action chosen in the selection screen, the processing log is displayed.
Possible processing types:
1. Simulation Run
The system checks for each selected item whether a change has taken place in the corresponding customs declaration, compared to the last sent message, that means the updated data has to be declared in a change SCD.
2. Remove Obsolete Entries
Processing runs as in item 1, plus all SCD items that are identified as not relevant for a change SCD are removed from the worklist for automatic processing.
3. Generate Change Messages
Processing runs as in item 2, plus all SCD items that are identified as relevant for a change SCD are sent to the customs system.
If all the items of a change SCD to be sent are identified as incorrect due to the incompleteness check, no message is sent to the customs system. If only some of the items are incomplete, the complete items are sent to the customs system in a change SCD. In either case, you can display the result of the automatic incompleteness check on the message tab of the SCD document.
The following example involves an SCD with four items, split into two customs declarations of two items each.
All four items were transmitted and processed positively in an initial SCD (IDoc 1001). After a reply message (IDoc1002) was received, a change SCD (IDoc 1003) was used to transmit the first three items again, where they were all processed positively.
The following changes were then made to the customs declaration data:
- Document number changed for SCD item 1
- Country of origin changed for SCD item 2
- Incoterms in customs declaration header changed in SCD items 3 and 4
Due to these changes, all the corresponding customs declaration items are assigned the value "E" in field "Control of Periodic SCD" (entered in periodic SCD - changed after registration) and therefore can be selected for automatic processing in the report.
During the simulation run, all four SCD items are checked for relevance for a changed SCD. To do so, the processing report reads the data of the most recent outbound message (IDoc 1003), which was used to transfer SCD items 1, 2, and 3, as well as the data of the second-most recent outbound message (IDoc 1001), which was used to transfer SCD item 4.
In the most recent outbound message (IDoc 1003), no relevant changes are identified for the header data of the first customs declaration, but relevant changes are identified for the first item (SCD item 1) and the second item (SCD item 2). A relevant change is identified for the header data of the second customs declaration, but no change for the first item (SCD item 3).
The result after this first step:
Customs declaration 1 / header --> Not relevant for change ECD
Customs declaration 1 / item 1 --> Relevant for change ECD
Customs declaration 1 / item 2 --> Relevant for change ECD
Customs declaration 2 / header --> Relevant for change ECD
Customs declaration 2 / item 1 --> Not relevant for change ECD
Customs declaration 2 / item 2 --> Not decided yet
The second-most recent outbound message (IDoc 1001) is the initial SCD. In this case, all SCD items sent with this message are generally considered relevant for a change SCD. (The reason for this is the ATLAS logic, which only allows the transmission of certain item data in an initial SCD if it differs from the data in the corresponding customs declaration. Since the affected IDoc fields for the initial SCD were not filled as a result of this "delta" logic, a comparison of certain item data between the current SCD document and the initial SCD based on the IDoc data of the outbound messages is not possible.)
The header data and item data from the affected customs declarations and customs declaration items that have been determined as relevant are not are no longer taken into account, which means only SCD item 4, which was not considered yet, has to be checked. Based on the special logic for the initial SCD described above, this item is considered automatically relevant for a change SCD.
The result after this second step:
Customs declaration 1 / header --> Already decided
Customs declaration 1 / item 1 --> Already decided
Customs declaration 1 / item 2 --> Already decided
Customs declaration 2 / header --> Already decided
Customs declaration 2 / item 1 --> Already decided
Customs declaration 2 / item 2 --> Relevant for change ECD
Accordingly, the result of the simulation run is that SCD items 1, 2, and 4 must be sent to the customs system in a change SCD. In contrast, SCD item 3 is not relevant for a change SCD and would be removed from the worklist for automatic processing under processing type "Remove Obsolete Entries" and "Generate Change Messages".
The data at header level of a customs declaration can only be transmitted to the customs system if at least one item from that customs declaration is transmitted in a change SCD. If only the header of a customs declaration is relevant for a change SCD, but none of the corresponding customs declaration items, the first items of the customs declaration (that is contained in the SCD) is made relevant for a change SCD.
Vendor Master (General Section) ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 8910 Date: 20200217 Time: 194558 sap01-206 ( 54 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.