Worklist for Imports declaration not getting generated upon posting GR in S4H on an Inbound Delivery

[prashant75]

Hello Experts,

I am facing problem while attempting to generate an Import declaration via the worklist after posting GR in S4H against an IBD. Can someone help based on what I have stated below?

The process for Import declaration goes as follows:

1. Create purchase order

2. Create Inbound delivery

3. Update inbound delivery with MRN and T1 doc type ( Header => Intl. Trade) for following fields: Prev Doc Type:  T1 transit document / Prelim. doc. no.: MRN number

4. inbound delivery creates a customs document in E4H

5. Post Goods receipt in S4H against the IBD

6. Create Import declaration via worklist in E4H (This is not working or I don't know how to make it work in E4H).

Configuration for Transit Procedure (Import Declaration) – S4H:

1. Technical activation of document transfer for Purchasing Doc(MM0A), IBD(MM0B), and Material Doc(MM0C)

2. Control settings for Document transfer:

2.a. For MM0A, chose PO type NB with Doc cat F for Compliance, Customs, and Risk Management at Doc type level only

2.b. For MM0B, chose IBD type EL for Compliance, and Customs at Doc type level only and option checked for Transfer of Proc. Traffic (IP/PUCC)

2.c. For MM0C, chose 101B movement type for Customs at Doc type level only and option checked for placement into Customs status before GR

3. Define Preliminary Document type “T1” for Transit MRN

Configuration for Transit Procedure (Import Declaration) – E4H:

1. Check Std Legal regulation definition for TRSUS with Legal code: 07

2. Check Std determination Procedure for Active Legal Regulation (Determination procedure: LETRS w/Partner Group Assignment)

3. Activate Legal regulation (TRSUS) at country level

4. Check Std Document type at Application area level: TRLOIM (Customs Shipment – Inbound) with no changes to the standard settings

5. Check Std Document Type activation for Transit/Presentation/Excise Duty: Doc type-TRLOIM

6. Check Std Control Settings definition for Process scheme TRSUS for US transit and ensure Processes, Activity, Activity sequence, and messages are good to be used As-Is.

7. Retain Action Profile, Partner Group, Text Det Proc., Calc Profile, etc. from the Std setup

8. Assign Document type at feeder system or feeder system group level. Application Level MM0B  FS Doc type: EL to Doc type DTAVI

9. Assign Std Item Category at feeder system or feeder system group level. Application Level MM0B

10. Define Determination of Prev. Doc. Type from Feeder System at the receipt (T1- Transit Proc.- MRN)

11. Define Determination of Target Procedure from Prev Doc type for Collection (LECTPR- Transit Proc- Duty Unpaid -Transit)

12.Assign Determination Procedure for Active Legal Reg LECTR

Configuration for Customs Processing (Import Declaration) – E4H:

1. Check Std Legal regulation definition for ACE with Legal code: 01

2. Check Std determination Procedure for Active Legal Regulation (Determination procedure: LECUS w/Partner Group Assignment)

3. Activate Legal regulation (ACE) at country level

4. Check Std Document type at Application area level: CULOIM (Customs Declaration) with no changes to the standard settings

5. Check Std Document Type activation for Customs Processing/Pre-Declaration: Doc type- CULOIM

6. Check Std Control Settings definition for Process scheme CUSUS for US Customs Processing, Activity, Activity sequence, and messages are good to be used As-Is.

7. Retain Action Profile, Partner Group, Text Det Proc., Calc Profile, etc. from the Std setup

8. Check determination of Activity Sequence for LR ACE and inherit the Std setup

9. Assign Determination Procedure for Active Legal Reg LECTR

10. Setup Default data per reqmt. (Define Default Data fields, Partner, Messages, Emails, etc.) 

Thanks in advance...

~Prashant