PO_HEADER_ID numbering in Oracle Fusion Purchasing
in Purchasing
Hello,
I need to ask about the logic used by Oracle Fusion Purchasing to assign values in the PO_HEADER_ID column, corresponding to PO_HEADERS_ALL table.
After creating several Purchase Orders in Oracle Fusion, we can see jumps in the PO_HEADER_ID numbering, for example:
1, 2, 1001, ..., 1004, 2001, 4001, ..., 12002, 300000002961782, 300000002974696
There is a way to force the PO_HEADER_ID numbering to follow always the secuence of the largest values (i.e. higher than 300000000000000) when creating a purchase order (whether via GUI, FBDI, SOAP or Rest API) ?
Thanks,
Ricardo
Tagged:
0