PO Template population

Moving your legacy data to Oracle Cloud can be a daunting task. However, there are many benefits to moving to the Cloud. Savings related to infrastructure purchases and maintenance which are no longer needed, training your staff and keeping up with software updates regularly. When it comes to moving your Purchase Orders (PO) to the Cloud, we can help make sure that the process is accurate and as smooth as possible.

One of the most common processes that we go through when we implement Oracle Cloud is to migrate existing Purchase Orders from the client’s legacy system to the new system. Oracle has a template in order to help with this exercise. The template is invaluable in aiding both the client and the implementer get legacy data into Oracle. There are a few things that should be known about this process. The PO template has a tab for each of the PO components – Header, Lines, Line Locations (Schedules) and Distributions. Here are some tips for completing the template:

• All of the “Key” columns throughout the various template tabs need to contain a unique identifier. I always have the client use the PO Number for both the Interface Header Key and Order columns in the Header tab. It makes it easier when following the flow within the other components. Example – 12345

• For the Lines tab, there is a column “Interface Header Key”, which should contain the PO number for each of the PO Lines. The “Interface Line Key” should contain the PO number and the line number from the PO, with a delimiter (“.”) between. Example – 12345.1

• For the Line Locations tab, there is a column “Interface Line Key”, which should contain the PO and Line combination for each of the PO Shipment Lines. The “Interface Line Location Key” should contain the PO number, the line number and the shipment number for the PO line with a delimiter (“.”) between. Example – 12345.1.1

• For the Distributions tab, there is a column “Interface Line Location Key”, which should contain the PO, Line and Shipment combination for each of the PO Distribution Lines. The “Interface Distribution Key” should contain the PO number, the line number, the shipment number and the distribution number for the PO line location with a delimiter (“.”) between. Example – 12345.1.1.1

• For migrated POs, a Requester name is put on the PO at the line level, however, because there is no originating requisition, the Requester does not have the same visibility to downstream activity they have on a PO created from a requisition. This can only be handled via BI reports or search screen exports with the proper role assignment.

The Oracle template is key to executing your legacy data to Oracle and we have more tips and tricks we can share to make this transfer seamless.  For more information or a step by step process, feel free to reach out to our team at [email protected] or check out our website at www.appsassociates.com