Setting up the Integration into Outbound Processes

You issue export declarations in SAP GTS based on customs declarations. If required, you can change or complete data in the customs declaration before sending the electronic message to the responsible customs office.

The transfer of inbound deliveries, material documents, and billing documents to SAP GTS always takes place asynchronously. This means that the documents are first created in the database of the feeder system and then transferred to SAP GTS via RFC. If mapping settings are missing or other serious deficiencies exist, the replication fails.

However, failed replication attempts are logged. If a customs declaration or customs shipment is missing for a feeder system document, check the transfer log for this document in SAP GTS. To track billing document replication, use the Display Transfer Log for Export transaction (transaction code /SAPSLL/EXPORT_TLOG). For the tracking of inbound delivery and material document replication, you can use the transactions Display Transfer Logs for Inbound Deliveries (transaction code /SAPSLL/APITIBD_TLOG) and Display Transfer Logs for Material Documents (transaction code /SAPSLL/APICUWL_TLOG).

If you have corrected the cause for the document replication to fail in Customizing or at master data level, you can trigger the transfer of document data in the feeder system again. To do this, start the Transactional RFC transaction (transaction code SM58). Specify a display period and execute the selection. In the results display, select the entry for the RFC with errors and choose Edit → Execute LUW.

SAP GTS replicates each billing document separately as a customs declaration. It is not possible to group several customs declarations for a new document in SAP GTS. If goods from several outbound deliveries are transported together for the same consignee in a third country, it usually makes sense to create a collective billing document for these outbound deliveries for transfer to SAP GTS.

In the SAP ECC or SAP S/4HANA feeder system, you can find a suitable transaction in the area menu for communication with SAP GTS on the Documents tab (Shipment Consolidation: Generate Customs Declarations from Sales Docs, transaction code /SAPSLL/CUS_INV_R3). Alternatively, you can use the Maintain Billing Due List transaction (transaction code VF04).

When the billing document is replicated, SAP GTS always decides on the variant of the export procedure and creates the customs declaration either for a normal procedure or for a simplified procedure, where applicable. Users cannot influence or revise this system decision. If the other procedure variant is to be processed, the billing document must first be canceled in the feeder system or, in the case of a pro forma invoice, completed.

SAP GTS always opts for the simplified procedure during billing document replication if the legal prerequisites for processing this procedure variant are met, that is, a suitable authorization for the simplification exists in the system.

If the data entered in the authorization for the simplified procedure (foreign trade organization, legal unit with authorized location of goods, commodity codes) do not match the document data, or if the authorization is not yet valid or is no longer valid, the system automatically chooses the normal procedure during billing document replication.

The decision for the normal procedure or the simplified procedure is the result of the activity sequence determination that SAP GTS performs when replicating the billing document. An activity sequence usually represents a procedure variant in the configuration of communication with the customs authorities. The activity sequence defines the substeps (activities) of a process – that is, the transfer to a customs procedure – and the sequence in which these activities must be executed.