Problem statement

When a purchase order line is split using delivery schedules, the resulting lines are renumbered as new whole-number purchase order lines. This removes the clear relationship back to the original purchase order line and creates traceability issues for users and downstream processes.

Current behaviour

As confirmed under LCS Issue 1152082, purchase order delivery schedule line numbers are renumbered as whole integers rather than cascading from the original line number as decimal sub-lines, unlike the equivalent sales order behaviour.

Microsoft has confirmed this behaviour is by design. This submission is raised following our related support case, TrackingID#2606110030008534.

Business impact

The loss of a stable purchase order line reference impacts traceability, reporting, reconciliation, integrations, and supplier communication. It creates ambiguity when users need to understand which split delivery schedule line relates back to the original purchase order line.

This is particularly impactful for ASN, EDI, and Landed Cost processes. In our scenario, the lack of a consistent line reference prevents reliable ASN integration and automated voyage creation, as shipment and voyage records need to link back to the correct purchase order line. As a result, shipment and voyage handling requires manual intervention, tracking, and validation.

The issue affects procurement, supply planning, and external integration processes where consistent purchase order line references are required.

Proposed solution

Provide a standard enhancement to preserve the original purchase order line reference when purchase order lines are split.

Ideally, this would support a system-generated decimal sub-line structure, for example:

- Original line: 10

- Split lines: 10.1, 10.2, 10.3

Alternatively, Microsoft could provide an equivalent parent-child reference structure that maintains a clear and stable link between the original purchase order line and all related split lines.

The key requirement is to retain the original line relationship and make it consistently available across delivery schedules, ASN/EDI, supplier communication, Landed Cost, voyage creation, and partial receipt scenarios.

Customer value

This enhancement would improve traceability, usability, reporting, and downstream automation for customers using purchase order delivery schedules and integrated inbound logistics processes.

It would reduce manual intervention, lower the risk of mismatched shipment or ASN references, and reduce the need for customers to build custom solutions to maintain purchase order line relationships.

References

- Customer support reference: TrackingID#2606110030008534

- Microsoft product reference: LCS Issue 1152082 - Purchase order delivery schedule line numbers are renumbered as whole integers, not decimals like sales orders