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 / Master data:

1)  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.

2)  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.

3)  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.

4)  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

5)  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.

6)  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.

7) Error -  Transfer error while transferring materials from the feeder system to GTS: "Conversion error in module AP16850_TXT_PROD_MAP, field AP16850_TXT-LANGU_ISO, value 3F."

Solution- Check the SAP notes; 3058365-KBA: Error message Conversion error in module AP16850 TXT PROD MAP raised when transferring product. 3553621-Adding New Languages to T002 Table. As mentioned in the note, add the missing language in the transaction code 118N and activate it to appear in T002 table. then transfer the material to have material transfer successfully to SAP GTS with this new language text value updated in GTS product master.

8) Error - Transfer Error while transferring customers/vendors from the feeder system to GTS. "Form of address 0002 not designated for organizations."

Solution- We need to check and maintain the form of address in Customizing - Maintain form of address. (Transaction code - SA03 then mark the title '0002' as Organization too. Related SAP Note : 2549000 (BP transfer error R1231: Form of address &1 not designated for Organizations)

Compliance Management:

1)  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.           

2)  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.

3)  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.

4)  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.

5)  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.

6)  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.

7)  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.

8)  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.

9)  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:

1)  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.

2)  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.

3)  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)

4)  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.

5)  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.

6)  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.

7)  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.

8)  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.

9)  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.

10) 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.

11) 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)

12) Error - Error in simulation of US tax assessment statement from SPROXY transaction / from the broker with the duty type values. Broker integration US Tax statement XML simulation error: "fault text - Code XXXX is not a valid value of code list 'Duty Definition', id - 204 (/SAPSLL/PROXY). 

Solution - This error is due to the Duty role code USMP, USHM not available in the customs code list of Duty Definition (AADEF - code list) in ACE. Go to Maintain customs code list - Enter Legal regulation - choose duty definition. Match the same duty definition value from the code list in the inbound tax assessment XML for the required duty types. For ex: US0100 - Estimated duty amount; USF499 - Merchandise processing fee (MPF); USF501 - Harbor Maintenance Fee (Waterways), USTOTA  - Amount Due.

13) Error- Broker integration - Import/export notification xml simulation error message: "Fault text: Standard message fault. text: The message is obsolete and is no longer maintained. id: 170 (/SAPSLL/PROXY)

Solution - The issue could be the xml is already triggered and inbound notification updated in the import declaration. To repeat trigger then change the <ImportDeclaration changeOrdinalNumberValue = "Next number"> and execute to update as new version of inbound message. Change ordinal number value should reflects the count of occurrence / update in the import declaration inbound message.

14) Requirement - Broker Integration XML simulation testing in SPROXY transaction. Testing XML inbound message to the declaration. For ex; simulation of inbound notification from the customs brokers to SAP GTS system

Solution- 1) Go to tcode - SPROXY. Open the required notification message ( export, import / tax assessment notification). 2) Select the required XML notification message on the left and Click on execute icon on the top. 3) Keep the same “Generate Request template” input and click execute. 4) We see the standard XML scheme for the inbound xml in the TEST Service provider: Display request. 5) Maintain the required field entries and prepare the XML inbound file outside GTS. 6) Make sure to maintain the correct entries like partner number, function, declaration number, Registration number (ZREGNR) to be used once for each declaration testing. Make sure the same ZREGNR not used on other simulation file for other declaration. 7)Click on the load file and select the file from the system to import the XML test file from the system matching with any existing declaration in the GTS system (declaration number and item details).  8) Then execute the file to simulation the notification update in the declaration. 9) The declaration will be updated with the response message (IB001…) and the ZREGNR and other details can be updated in the declaration using the standard BADi's for the inbound notification update.

15) Requirement - Antidumping (AD) /Countervailing duty (CVD) to populate in the US import declaration.

Solution - We need to purchase the duty rate files with AD/CVD rates from the data provider ( for ex: Descartes). AD/CVD rates is a separate subscription to be procured from the data provider. Then follow the below steps 

1)  Define external customs duty rate types for Data upload in config for US HTS numbering scheme content. (B080 = B501; anti dumping & B081 = B502; CVD) 2 ) Define calculation procedure for customs duties for US imports (ACE Legal regulation) and add B501 & B502 for the US imports. 3) Add the additional tariff numbers (USADD) & duty rate conditions (USECCC) in the Define numbering scheme content config for the US HTS numbering scheme content USHTS_CT. 4) Upload the TXT & NOM classification files 5) Upload any additional tariff number NOM files , for ex US HTS additional tariff number for chapter 98 and 99 with 8 digits 6) Then upload the DTR files for the HTS and additional tariff numbering scheme content along with cd rates and country group settings. 7) Classify the product and choose the customs duty rate conditions in the product master to have the customs duty rates populated automatically or we need to manually select one in the import declaration, if the product classification got multiple conditions 8) Maintain the products documents at the product master authorities tab for the document type PDOC-ADDL (Anti dumping Case number) to auto populate the case number directly in the import declaration 9) Then create the import declaration for the US with the required HTS, Customs duty rate conditions, PDOC-ADDL at the declaration item level and with the right country of origin. With the right values the anti dumping value will be calculated and displayed in the import declaration at the item level customs value tab. For ex: US HTS - 3906905000, Customs duty rate condition/ ADDL case number - A580914000 & COO = KR, then Anti dumping duty rate will be 26.05 percent.  Antidumping duty rates using case number, HTS, product country can be searched in ITA (International Trade Administration) - https://access.trade.gov/ADCVD_Search.aspx 

16) Requirement - US PGA Codes setup for the US import declaration.

Solution - Configurable PGA (From GTS E4H) If configurable PGA record maintenance is checked in the Display numbering scheme for tariff number then maintain the separate config for PGA under the numbering schemes and then the product master classification tab will have the button for PGA relevance code setup below the supplementary UOM and a separate tab for PGA in the product master. then we can use the "Create PGA records for the products app" to mass maintain the PGA records / go to the PGA tab in the product master to manually maintain for single product. PGA tab is visible only when configurable PGA record maintenance is active.  PGA relevance code will be updated automatically from the classification content if the content is uploaded after the PGA config setup.

Non-configurable PGA (GTS 11 / E4H) If configurable PGA record maintenance NOT checked in the Display numbering scheme for tariff number then maintain the authority & program codes in the numbering scheme content and then product master will have the authority code to maintain it in the classification tab. Authority code will be updated automatically from the classification content if the content is uploaded after the authority code setup in the config / master data setup in Define authority code..

17) Issue - Printer Determination not enabled or greyed out in Define Conditions/ Output Parameters for actions PPF.

Solution - Check whether the printer dynamic Determination BADi is activated for the customs management  or preference management with the required action definition as filter values. Check the BADI - PRINTER_DETERM_PPF.  If the Action definition is a Z* one then we need to maintain the filter values with Z* in the BADI implementation and then the printer determination checkbox will be enabled for that action definition in the config for Define Conditions/output parameters for the communication. Then the required printers can be maintained in the transaction /SAPSLL/PRNDT2 for the customs management and in the transaction /SAPSLL/PRE_LTSD_PRI for the preference management.

Risk Management:

1) 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. 

2) 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.·        

3)  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.

4)  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.

5)  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.

6)  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.

Special Customs Procedure: (BWH/ IPR / FTZ)

 1)   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.

 2)  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.

3) Requirement – Distribute special customs procedure flagging in SAP GTS product master through transfer the flagging from SAP ECC/S4 to SAP GTS product master.

Solution- Standard Program in SAP ECC/ S4 can be used. /SAP SLL/PRECIP_DISTRIBUTE_R3 – distribute flagging from ECC/S4 to GTS. Customs procedure product flagging can be distributed from feeder to GTS system only when the products are maintained for that particular plant & sloc activated for the customs id in the feeder system and the stock details are maintained. Choose the required customs id, material selection & product attributes (like CWH, IPR, OPR, FTZ, Processing trade) and execute the program to activate the flagging in SAP GTS. This standard program “/SAP SLL/PRECIP_DISTRIBUTE_R3” can be used only when the below conditions are met. 1) Materials extended for customs id plant and storage locations. (as per BWH activated locations in /SAP SLL/TECOR3 table). MRP setup done and stock details available in MARD & MCHB tables. PRECIP flagging can be deleted in SAP GTS for any customs id using the function module /SAPSLL/PRODUCT_PRECIP_DELETE function module, if required. 

4) Requirement – Flagging products directly in SAP GTS for special customs procedure flagging in SAP GTS product master. This is non- standard but can be required for some clients where the materials are not extended for required plant & sloc and customs procedure logic is handled directly in SAP GTS.

Solution- Standard Program /SAP SLL/PRECIP_DISTRIBUTE_R3 used the FM "/SAPSLL/API_6850_PRECIP_SYNCH" which can be called directly in SAP GTS for product flagging. 

1) FM - /SAPSLL/API_6850_PRECIP_SYNCH . In this function module pass the logical system name in iv_logsys and iv_commit = x and fill the internal table it_precip with the product number and flagging as x for the required fields and customs id in "ecp_stge_id".  for ex for bwh " mat_bwh_rel = x" and ipr "mat_ipr_rel =x" and additional stock id "ivm_stock_sep_id= x". With this logic the product flagging can be done directly through a program in SAP GTS with some similar selection screen used in the standard program.

2) FM - /SAPSLL/API_IVMS_STOCK_SYNCH . This function module to activate BWH in GTS directly after the flagging which by standard will get activated when the initial transfer of Duty paid stock program is executed in SAP ECC/S4. With this FM we can have development to activate the product for BWH and create an entry in /SAPSLL/PRBWH table. 

5) Requirement – Standard Scrapping process in SAP ECC/S4 & SAP GTS using material document.

Solution- 1) Create the "scrapping request" using the "Scrapping" button in the CWH Stock Overview. A new Customs Declaration Document is created by the system, and sits in the Export "Outbound Activities" work-list. In the Stock Overview, you should be able to see that the corresponding stock is transferred to "reserved" stock.

2) In the ERP Material Document (assuming you have activated the scrapping number in the IMG ECC-SPRO-Control Doc settings-Activate the 551/any scrapping movement type and choose only the "Transfer to Customs Management" and the Goods movement category as '1-Scrapping' and don't select any other settings), a new tab should appear, and the user should enter the "scrapping number" that the Customs administrator provides - that number corresponds to the Export Declaration Document Number and Year of the Declaration Document (for example, '14123456782020'). GTS Customs reference number(Scrapping ref number) is required for the scrapping to get updated in GTS. Keep a BP in this program before CALL BADI - "MM07MFS0_SLL_DOCUMENT_TRANSFER" program and structure and field is "XMKPF[] - GTS_CUSREF_NO, if any issues in transferring the scrapping ref number to GTS. If no number provided then SAP should send the scrapping ref number as $1.

3) Posting the Material Document should cause the transferred data to create an entry in the "Scrapping" work-list in GTS. (it will be updated in /SAPSLL/CUSWLO table with IBLIS field = 5 for Scrapping) Processing the entry in Process scrapping operations transaction should automatically close/complete the Customs Document and remove the stock from the system. The "pop-up" dialog should only appear if the system cannot match the "scrapping number" with an open Customs Document and we can enter the matching export declaration number for the update.

Other topics:

1)  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.

--------------------------------

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