How to Preserve Parent-Child LPN Hierarchy When Receiving ASN via API?
Summary:
While receiving an ASN that contains a parent License Plate Number (LPN), the receivingReceiptRequests API does not accept the ParentLicensePlateNumber attribute. As a result, after the ASN is received, only the child LPN is moved to Receiving, while the parent LPN remains in the Defined but Not Used status.
Has anyone encountered this issue? How can this be addressed? Is there a supported way to receive an ASN while preserving the parent-child LPN hierarchy?
Content (please ensure you mask any confidential information):
Version (include the version you are using, if applicable):
26.c
Code Snippet (add any code snippets that support your topic, if applicable):
Tagged:
0