Skip to main content
Question

Purchase Req Lines sequence in PO

  • February 13, 2026
  • 3 replies
  • 44 views

PRODQ
Superhero (Customer)
Forum|alt.badge.img+18
  • Superhero (Customer)

Has anyone come across this situation?

 

  • Non-stock Purchase req raised with four lines.  
  • Change the sort order of the lines (either by accident or design...)
     

 

Convert Req to PO and PO line numbers reversed…

 

We’re on 24R1 SU16.

Thanks

Linda

3 replies

Forum|alt.badge.img+12

Hi ​@PRODQ

I checked the same in our 25R1 reference environment and observed the same result. This seems a bug in the application. Please send us a Support Ticket so we can report this to RnD and get fixed.

Thank you. 


Forum|alt.badge.img+7
  • Hero (Partner)
  • April 1, 2026

Hi ​@Ravinatha Ariyarathna  - Has a fix been developed for this bug? or is it in progress?

 

Thanks

James


PRODQ
Superhero (Customer)
Forum|alt.badge.img+18
  • Author
  • Superhero (Customer)
  • April 1, 2026

“Not a bug” apparently, ​@Ravinatha Ariyarathna ​@WyrJamesG 
Linda

 

2026-03-05 17:37:07

As explained by RND below, the line numbers in the Purchase Order are generated independently because they belong to a separate object. However, the Purchase Order includes a specific attribute that stores the original Requisition Line Number (Req Line No) for reference.
*Please refer to the attached screenshot "Screenshot of Requisition Line No CS0483828".

Since the requisition lines are sorted before generating the Purchase Order, the PO lines are created independently according to that sorted order.

Therefore, the comparison should not be based on the Purchase Order line numbers. Instead, users should refer to the "Req Line No" field, which contains the original reference from the requisition.
Using this field will provide the correct information for users and address the issue raised. Hope this clarifies your issue.

 

2026-02-25 16:59:04  Additional comments

Dear Linda,
I would like to inform you that our RND team has conducted a thorough investigation regarding the issue you reported and pleased find following update from RND.

The issue arises after the creation of a Purchase Requisition, during which several non-part lines are added. The customer then sorts the line numbers in descending order and subsequently converts the Purchase Requisition into a Purchase Order. It has been observed that the line numbers in the Purchase Order do not align with the order of the lines in the Purchase Requisition, which has been raised as a concern.

However, RND has clarified that this behavior is expected. The line numbers in the Purchase Order are generated independently, as they pertain to a distinct object. Furthermore, the Purchase Order contains a specific attribute designed to store the original "Requisition Line Number" (Req Line No) for reference purposes.
The customer's comparison is based solely on the Purchase Order line numbers, without taking into account this separate reference field (Req Line No).

Therefore, please note that the RND team has confirmed that this does not signify a system defect and cannot be classified as a bug.
You may consider the original Requisition Line Number (Req Line No) in the Purchase Order line instead of the Purchase Order line number. I hope this explanation addresses your concern.

CS0483828