Skip to main content
Question

Customs Declaration Number in Part Lot Batch

  • August 3, 2026
  • 1 reply
  • 38 views
J
Do Gooder (Partner)
Forum|alt.badge.img+2

I am receiving an item on a purchase order in the Register Arrivals window and assigning a Customs Declaration Number and Date. This information is stored on the Part Lot Batch record under the Customs Declaration tab. However, if the part is moved via Shipment Order/Shipment the Customer Declaration information must be re-entered. It is not inherited to the Shipment. (Issue #1)

 

I am moving the items via Shipment Order from an Arrival location to a Remote Warehouse. When I receive the items via Incoming Dispatch Advice, I am not seeing the Customs Declaration Information that was entered at either the original time of receipt or when the shipment was created. (Issue #2)

 

If I add the Customs Declaration No and Date when performing the receipt at the remote warehouse via Incoming Dispatch advice, the Part Lot Batch record is not updated with the Customs Declaration details. (issue 3)

 

Why does it appear the Part Lot Batch window only stores one Customs Declaration No and Date?

    1 reply

    Piyal Perera
    Hero (Partner)
    Forum|alt.badge.img+12
    • Piyal Perera
    • Hero (Partner)
    • August 4, 2026

    Hi ​@Jwsc0964,

    Sharing my findings from a Cursor-assisted code/functional search. I hope these insights are beneficial.

    Why only one Customs Declaration No and Date?

    By design:

    • Storage is one row per Part + Lot/Batch + Site (LotBatchCustomsDeclar).
    • Product documentation states you cannot assign different CDNs to the same lot/batch.
    • Later receipts with a different CDN get a warning and do not update the lot record (DIFFCUSTDECLNO).
    • Shipment header CDN (export/tax) is a different attribute from import lot CDN.

    Workarounds (no code change)

    1. Keep using the original Part Lot Batch CDN on the supply/receiving site — inventory move does not clear it; re-entry is only needed if you expect it on Shipment/IDA documents.
    2. Enter CDN manually on IDA lines before receive (CloudDocs-supported). Prefer line-level CDN so Create_Customs_Declaration gets values.
    3. If Part Lot Batch must be corrected after receive: open the Receipt and change CDN there — that calls Modify_Customs_Declaration and overwrites the lot record; or edit Part Lot Batch Customs Declaration tab directly (CRUD Update allowed).
    4. Avoid conflicting CDNs for the same lot on the same site; if a second import CDN is truly different, use a new lot/batch (per CloudDocs split-receipt guidance).
    5. Do not rely on Shipment header Customs Declaration fields for this import scenario — those are for export customs/tax flows.

    It also suggests that Issue 1 and 2 as a product enhancement and Issue 2 can treat as working as designed.

    regards,

    Piyal

    Piyal
    Terms & ConditionsAccessibility statement