Your problem is that X3 has the capability to combine lines from different requisitions onto a PO, and that the requisition itself is not limited to a single supplier. All  of those functions would need to be controlled. If you are just needing it for reporting purposes there will be data in the PO lines that will link back to a requisition and I would think that the traceability functionality would also allow that.

Your problem is that X3 has the capability to combine lines from different requisitions onto a PO, and that the requisition itself is not limited to a single supplier. All  of those functions would need to be controlled. If you are just needing it for reporting purposes there will be data in the PO lines that will link back to a requisition and I would think that the traceability functionality would also allow that.

I spoke with Sage Support and they referred me to this KB article (https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=94234&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=2192&cmd=displayKC&dialogID=87238&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true). Apparently the system automatically sorts the lines by the item number in alphabetical order during the PO creation process. The article explains what needs to be done to fix the issue. It needs an entry point added to the code for the function by a certified developer. It is not considered a customization but a tweak according to Sage.

Let me know if you are able to locate and run this...you definitely got farther than I did!

I'll keep you posted. Apparently you have to request the entry point from Sage.

Morning!  

Just wondering if you were able to successfully get this working?

Good morning Carl,

As this will require a code change, and we are in the process of an upgrade, it is on the back burner. I will likely address it after the upgrade or have the partner do it during the upgrade.

Dave