SAP GTS-Common Issues/Fixes/Requirements

Introduction: Here in this blog, we will see a few of the common issues/requirements which I've seen in some projects and the steps to resolve/address them. We will see based on the modules/topics.

General:

·       Error - Error during consistency check for numbering scheme: No. of special UoMs (during HS content upload) 

Solution- This error is due to the mismatch in the numbering scheme settings. Select the number scheme in SPRO and check the timezone and No.of spl units matching as per XML upload file (for ex -Timezone-CST; No.of spl units- 3 Customs Tariff System has 3 Special Units of Measure). Change the config as required by the XML upload file and continue with the upload.

·       Issue - /SAPSLL/CTSNUM table has no entries for any numbering scheme even if the content files are loaded in the SAP GTS system.

Reason- Check the numbering scheme configuration and the xml file loaded for the numbering scheme. If the country dependent is active/true for the numbering scheme in the xml file loaded, then the classification numbers are saved in /SAPSLL/CTSNUMC tables (Country Specific Customs Tariff No. Table). This is mainly noted for Germany / DE imports, for the numbering scheme DEEZT with 11 digits structure.

·       Requirement - How to disable the prompt when accessing the file for any uploads in SAP system. "The system is attempting to access the following file"

Solution- To disable the prompt every time we see when we try to upload any content file to SAP GTS. Goto SAP GUI Configuration - click on security - security settings - open security configuration - choose the required SAP rule for the required folder path and change the Default action from Ask to Allow. Click on apply to save the settings. Then we will not see the prompt for allowing permission to access the file.

·       Error - Error during Classification content load  - Consistency error: Two overlapping instances exist for number

Solution- The issue can occur if file versions have not been uploaded to the system in sequential order by excluding the nomenclature check in the standard program. Another possibility it that the data in the file that was obtained from a data provider is not correct. Check the relevant notes: 1470356 - How To Resolve The Error "Number cannot be updated twice " In GTS.1) Run the Correction report SE38 program to remove the inconsistencies - "/SAPSLL/CTS_WN_REPAIR". 2) If the correction program does not work then create a new numbering schem and transfer the product classification. 3)Tcode for classification migration from source old numbering scheme to new numbering scheme - /n/SAPSLL/PR_CL_CPY

·      Error - Error during BOM transfer from SAP ECC/S4 to SAP GTS. “Status of BOM Explosion: Bill of Material Does not Exist.

Solution- The issue is due to BOM settings 1) Check the BOM Validity & Status in BOM Header. (Tcode - CS03). BOM Status should be active "1". If its inactive "2" / valid to date is expired, then BOM cannot be transferred to SAP GTS. 2) Check all other standard configurations for BOM transfer at plant/country level from SAP ECC/S4 to SAP GTS.

·      Error - Fiori launchpad not opening in the Web browser. "This Site can't be reached".

Solution- Check whether the Ip address details maintained in the host file. Host file path is required for opening the Fiori launchpad in the browser. Go to folder path C:\Windows\System32\drivers\etc\hosts. Format to be maintained: "192.XX.X.X sapgts  sapgts.xxxx.com". Actual IP address can be checked from SAP logon pad if ipaddress is maintained / using OS01 transaction-change view. Host name can be checked from the web browser error details.

Compliance Management:

·       Requirement – Transfer the license from the preceding document even if the license has been applied manually using legal control data option. 

Solution- This requirement can be met with the standard configuration. Step 1) Adoption of Control Data from Preceding Item can be set for the relevant item category: Transaction path - SPRO:IMG: Global Trade Services > General Settings > Document Structure > Activate Item Categories for Application Area. Select Activation for Legal Control Item cat: Select relevant item category (EXDLV1) and Flag “Copy legal control from preceding item”  Step 2) config at the Legal Regulation level. SPRO> Global Trade Services > Compliance Management > Legal Control > Control Settings for Legal Control. Select Relevant Legal Regulation, Field: Transfer of legal control data and choose “Transfer license data with limited check”. Relevant SAP Note: 2467936- Transfer License from preceding compliance document.           

·       Requirement – Apply a license to any document only when there are no other compliance blocks like SPL/Embargo/client specific ones. 

Solution- This requirement can be met by activating the ‘Block legal control” option in the Activate item categories for legal control. With this option, the license will be applied only when there is no other compliance blocks in the document and even we could not manually assign a license through legal control data option.

·       Error - Unable to find a value for depreciation on license determination. 

Solution- This error is for the document check for the value-based license check in Compliance. The net value of the controlled item in the Sales/purchase order might be zero. If the order has free charge item, then only option is to create a new license type without value assignment and have the check based on the quantity, if required. Item value cannot be zero for value-based license (Validated license) check. However manual license assignment is possible through Maintain Legal control data option.

·       Error – “No import/export license types found for determination procedure <CD05>” in the error logs of the compliance check

Solution- This error is for the document check for license check in Compliance. Here, Determination strategy for the procedure <CD05 – Country level> is missing. Maintain license determination Strategy in GTS Cockpit for the legal regulation for any missing procedures from CD01 to CD21.

·       Error – “Values were not written off (deducted) in value/quantity-based license.”

Solution- This can be due to incorrect/missing configs. 1) check whether the license type is activated for value/quantity-based check. 2)check whether the depreciation group is assigned, if its an agreement. 3) check whether the depreciation setting is applied for the item category-legal control 4) Uncheck the low value check in define license type. This setting is for threshold value check (Threshold value license) and not for depreciation. For ex: With low value check enabled, if a license value is 1000USD, then any order/delivery with above 1000USD will be blocked, and this license will not get depreciated, so it can hold as many as orders/deliveries within 1000USD.

·       Terms - Soft block in the SPL screening

Explanation - Soft block is due to "Asynchronous screening" enabled in the configuration for the business partner and the SPL screening is not yet performed on the transferred BP & the document. We can run A1/A2 Asynchronous screening to perform the screening and update the actual screening result (Released/Hard block). Or change the config to Synchronous screening to have the immediate screening results when the partner/document is transferred to GTS. We usually use ‘Asynchronous screening’ for the initial mass transfer of partners from SAP ECC to SAP GTS for system performance. After transfer of all the master data (BP’s) it can be changed to Synchronous.

·      Requirement - Certain Partner function to be excluded from transfer from feeder (ECC / S4) to GTS and to skip incompletion blocks due to some partner functions which are not required in GTS document for SPL/Embargo Screening (like sales people / Contact persons / Employee responsible)

Solution – This can be achieved through standard config. Path: SPRO- General Settings-Partner Structure- Assign Partner Function at Feeder System/Group Level-Manually assign-Then Select the checkbox "Do not Copy Partner Role/Function from Backend System. This indicator excludes individual partner functions from the transfer. If this indicator is not set, then the partner function is transferred.

·    Issue – License type Codes not visible in default data for customs management in define license types for EAR legal regulation.

Solution- This is due to missing customs code list to the US EAR legal regulation. Assign customs procedure 'CUSUS' for the legal regulation 'EAR' in SPRO- Customs - Customs Code lists - Assign Customs Code Lists Procedure to Legal Regulations.

Add customs code list for PAPTY (License code), PAPOF (Issuing Authority of Document), QUALD (Qualifier of the document). Then the licensing types like C30 (IVL) / C33 (NLR) etc which are applied at the compliance level can be automatically defaulted/transferred from the compliance document to the customs declaration at the item level.

·      Issue – Compliance screening log shows as: “This item is not relevant for Checking” / ” Document not relevant for check” .

Reason- This could be due to several reasons. 1) The item could be marked for cancellation/rejection. 2) Delivery date of the order could be in the past and its delivery/PGI is completed already. For sales order log, the delivery status is checked and for delivery log, the PGI status is checked. For PO, the deletion indicator is set at PO item level. /SAPSLL/CUIT-ITREC field indicates whether item is relevant for checking or not in SAP GTS. The value for this ITREC field comes from the Feeder System. If ITREC = " ", then the item is not relevant for new check and it could be due to any of the above two reasons. If ITREC field = "X" then the item is relevant for new check and any changes to the order / recheck transaction will update the log for that line item.

Customs Management:

·       Error – Customs export declaration not created in SAP GTS for the required export billing document / Customs document type cannot be determined for external document type  

Solution- This error could be due to several factors like 1) Customs export declaration can be created only for export, not for domestic. So, check the exporting plant country and ship-to-party/end user country to make sure its an export transaction / check the export indicator in VBRK table. 2) Check the configuration in SAP GTS to make sure there is an active legal regulation for the company code country and activity sequence is correctly maintained with GTS document type CULOEX. 3) Check the billing type is activated for customs and badi is on for the SDOC transfer from ECC to GTS. 4)Check the RFC connection between ECC to GTS 5) Check the SM58 logs in ECC / check the export logs in SAP GTS to find any other issues. (like packaging type not mapped) 6)Try creating manual export declaration in SAP GTS to rule out the issue in SAP GTS/in the transfer from ECC to GTS.

·       Error - Invalid identification type (0) / (4) in the DE customs declaration incompletion check.

Solution: If the filing involves EU countries, then check the "EU Member" flag in the country specific settings (T005 table). The partners like declarant, representative, Message sender should be EU countries when EU countries are involved in the customs filing. For ex: For DE export filing, Poland (PL) can be the consignor, declarant with the PL EORI & branch number. for this PL should be marked as EU member in the T005-XEGLD. So this EU member activation is missing here to proceed further.

·       Issue - Customs Invoice is not getting created in SAP GTS. 

Solution: Customs invoice can be used for creating import declaration prior to GR. 1) Check the Config in GTS - SPRO: Define Document types should have CUIN doc type with number range and partner groups. Assign the required duty types. 2)Then check in GTS SPRO - "Assign Customs Invoice to a Business Document Category" - Assign it for Intercompany / Customer invoice. 3)Check the Payer (RG) & Bill to party (RE) partner number in GTS billing on ECC side. Both the partners should have Plant table customer number value (T001W-KUNNR). If not, then development is required to flip the partners. 4) Check the Customs document (Compliance) created and available in GTS. Without IMPORD customs document the customs invoice cannot be used for creating the import declaration. 5) Also check whether the intercompany invoice types in SAP ECC is activated for Customs invoice (Can be verified for the invoice type in table - /SAPSLL/TLER3B for SD0C application level)

·       Error - No Customs duty rates getting loaded in upload option / Customs duty calculation determination failed in import declaration/simulation.

Solution: 1) Check the external duty rates mapping. 2) Check the Duty rate types assignment in the Calculation procedure config for imports for the required customs legal regulation. 3) Country groups from the DTR file should be captured in a TR and moved to subsequent systems (like test/prd) before loading the files / change the settings as “Non-Transportable” for /SAPSLL/V_CTYGP in SOBJ transaction to load the CD rates & country groups together in test/production clients without any transport request.

·       Error - Packaging type assignment not getting transferred to GTS

Solution: 1) Check whether the standard packaging process followed in SAP ECC with the handling units for the standard to work. 2) Assign the packaging types from ECC to GTS. 3) Check the Package category in the maintain custom code list for Package type (PGETY). Package type should be "Transport Packaging". Freight Container & Sales Packaging/Not Packed values won’t be transferred to GTS using packaging type assignment.

·     Error - "Filer not authorized" as error message during US AES export declaration filing. This could be due to multiple US company codes/FTO having multiple USPPI/EIN for filing, but only one used with Seeburger for filing/connecting with the US Customs.

Solution: To meet this requirement, we need changes to be done only for one Partner value, (i.e) Decentralized communication partner in customs declaration. ISA02 is the Transmitter ID, that will need to stay the same for all transmissions with fixed EIN value which is used by Seeburger for connection with the US Customs. (This can be set as fixed value by changing/setting DEZCOM (Partner function type) - Decentralized/local communication partner in default value). ISA06 and GS02 are Filer IDs and that can be with different. (Rest all partner functions like message sender, Consignor, declarant can represent the actual company code/FTO in the declaration). 1) Transmitter ID = Decentralized / local communication parter/Periph.Comm. (Partner Function - CUSDCC, PF type - DEZCOM) - Fixed value. 2) Filer ID - Message Sender, Consignor, Declarant (PF Type - CUSMES, CUSVER) – This can be the actual USPPI of the Filing company code.

·      Error - Error in Print/print preview of adobe pdf forms in Customs declaration “CX_SY_CONVERSION_NO_NUMBER.”

Solution: 1) Check the user profile in SU01 - Decimal notation settings - It could be X format (1,234,56.00) 2) Check the data type for the number fields used in form. There could be some limitation on the field length. Change the data type as required (for ex: from integer to characters) / remove the variable which is not required to pass the values in the form.

·      Error – Incompletion error in DE Atlas customs declaration. “Partn. Constellation has an incorrect value (X000)”

Solution: Check the partner functions maintained in the declaration. Consignor, Declarant, Message Sender Partner function to be added in the declaration - Partner data.

·      Error – Incompletion error in DE Atlas customs declaration. “Address data for Representative (Person) - Customs Agent is incomplete: Position at the Company”

Solution: Remarks column is required for the representative person. Logon in SAP GTS in German language and maintain the comment/remark field for the Representative contact person (DE -Bemerkungen). Expand the + icon to see the "Bemerkungen/Remarks" column.

·      Error – Incompletion error in US Customs import declaration. “Specify a consignee with identification (Sender/receiver ID Code)"

Solution: Maintain the US Filer Code (three characters) to the FTO BP-ID type "SLLTEC" - Technical Identification in Messages in the BP transaction - Identification tab.

·      Error – Incompletion error in US Customs import declaration. “"Customs Number Consignee has an incorrect value"

Solution:  Maintain the US Filer Code (three characters) to the FTO BP - TIN "GTS Area Menu-Customs-Master data-Organizations-Maintain TIN". (TIN will be the filer code)

Risk Management:

·       Requirement - Request Vendor LTVD for products where there is no PO / GR in the VLTVD worklist. 

Solution- This can be achieved by selecting "Select Document-Independent Products" in the Request Long term vendor declaration. Also choose the mandatory- "Vendor & Material" combination for request VLTVD. Then inside the output select Vendor-Based Vendor declaration on the top menu and click on "Add Products". Now select the required products and click on copy data and then we can request Vendor LTVD for the selected vendor & material combination. 

·       Error - Saleability / Not Saleable status for the products not updated correctly in GTS.

Solution - Saleability details is transferred from ECC along with the procurement indicator transfer. If the material in ECC has the maintenance for sales view, then its saleable. It’s captured on the MARC-PSTAT value.  For Ex: if a product XYZ in plant A has MARC-PSTAT="GBDQA" then "V" which is sales view is missing then its not saleable, if a product XYZ in plant B has MARC-PSTAT= "DELBVGQA" then V is part of the value then sales view is available and its saleable.

Maintenance Status of material is updated in the table MARC against the field PSTAT with the below indicators: A- Work scheduling; B-Accounting; C-Classification; D-MRP; E-Purchasing; F- Production resources/tools; G-Costing; K-Basic data; L-Storage; P- Forecasting; Q- Quality management; S- Warehouse management; V-Sales; X- Plant stocks; Z- Storage location stocks.·        

.        Issue – No spool logs available for Check Spool error log / print error log for printing V-LTVD / C-LTVD

Reason- If "delete after output" is enabled while printing then the spool log won't be saved / available. Uncheck the "delete after output" to view the Spool log.

 ·       Issue – Error during Preference - Customer LTVD form print/preview: At least one LTVD cannot be issued. Do you still want to continue?

Reason- Check the "Set Up Inconsistency Check for Customer LTVD". There should be an incompletion check activated for any agreement and the field values (like product description and HTS) can be blank. Maintain the mandatory field values and retry.

·       Issue – Error dump during Preference - Customer LTVD form print/preview: ABAP Dump - "CALL_FUNCTION_CONFLICT_TYPE".

Reason- Customs Forms (/SAPSLL/PF_NAFTA_COO) that are assigned to Interfaces of the area "Customs Management" have 1 optional and 1 relevant Import Parameters. So, for Preference (Risk Management) we should use the copy of the Risk management form (/SAPSLL/PF_NAFTA_VD_1) which got required import parameters. So don’t use the customs declaration forms for risk management. Relevant SAP note 2146243. SAP Note 2149633 is the other way round of using the preference form interface in the customs declaration.

·      Issue – No documents found in LTVD's worklist in Preference Processing

To Check- 1) Check whether the vendor country & Delivery address country are activated for Preference Agreement. (EX: For NAFTA, Vendor & delivery address to be in US, CA / MX, if only these countries are activated in country group / country group level. 2) Check the vendor is assigned to administration unit if specific activation is enabled in control settings. 3) Check whether the procurement indicators are sent to GTS from ECC through initial transfer of master data. 4) Check whether you have maintained preference/LTVD status in product master for that product, if we've already (manually/thru preference) maintained it's status, then the PO is not needed in GTS for that year. 5) Check whether the PO types / Material document types are activated for transfer to GTS for vendor LTVD worklist in ECC config. 6) Also check whether the preference agreements are transferred from GTS to ECC and in sync in both the systems.

·      Requirement – To Skip Letter of Credit check based on Payment terms in Sales order / OBD.

Solution- This can be achieved through standard config. Path: SPRO-GTS-General Settings-Define Terms of Payment. Select the Terms of payment that are not relevant for LOC and check ‘NOT LOC’ checkbox against the payment terms.

 ·      Requirement – To pull the stock from particular import declaration for Customs Warehouse (CWH) / Inward Processing Relief (IPR) closing portions in the CWH/IP Re-exports/Scrapping/Free Circulation.

Solution- SAP Standard will always follow the FIFO (First In First Out) for the discharge procedure from the CWH/IP Special customs procedure. But to have the particular stock to be pulled we can make use of the additional stock identifier logic (Field - IDGDS) to store the stock in the CWH/IP inward process. Then the particular stock id can be used for the pulling the stock for any discharge.

 ·      Requirement – To create one customs declaration with multiple line items for the Free Circulation / Scrapping from the CWH/IP.

Solution- SAP Standard allows to create one declaration with one item using the standard process for "Create FC from CWH" / "Process scrapping operations". Only 5 items can be selected in the Stock overview which is a limitation and one product can be selected in the stock output layout to create FC / Scrapping declaration. But through development we can create one declaration with multiple line items using excel upload option. FM "/SAPSLL/API_IVMS_IDUP_SYNCH" can be used with the required changes for the development.

For any suggestions/corrections/need to discuss on any other GTS issues, please drop a message. Happy Learning...