Create Limitations

File-based data import doesn’t support the creation or update of purchasing documents with more than 10,000 distributions. E.g. 1 Purchase order, 1 line, 1 schedule each, 10,000 distributions each OR 1 Purchase order, 10,000 lines, 1 schedule each, 1 distribution each

Currently, Oracle only allows the download of 500 Agreements headers at one time.

Only support document type of Standard Blanket Purchase Agreements. E.g. Consignment is excluded

The download web service returns only the code, not its meaning, so the Integrator will only display the code.

The download web service provides only the code itself, so the Integrator will display only the code. This issue will be resolved when Oracle fixes it.

The download web service does not return priority information. We are unable to download the priority to the sheet. This issue will be resolved when Oracle fixes it.

The Change Order Details (Description, Status, Line change reason) are not currently available in the download web service. As a result, the integrator will not display these details when downloading. This issue is with Oracle to resolve.

Due to performance implications of Oracle’s Web Service, More4apps recommends uploading no more than 500 lines per agreement.

The Web Service also has a limitation for downloading records. More4apps recommends only downloading records with 1000 lines or less.

These limits may improve over time as Oracle enhances these gateways.

The web service currently supports only the creation and upload of DFFs. Download functionality will be available once Oracle provides an enhancement.

Header attachments are supported with the following Oracle imposed restrictions. The operation works only for purchasing documents created by import or web service. Documents must be in Incomplete or Open status. If documents are in Open status, they must have bypassed human approvals and must not have been communicated, acknowledged, or signed. They must also not have a change document open or a change implemented.

While the line start date field exists within the template, its visibility within the user interface is conditional: it requires the instance to be running version 25A or a more recent version, and the field must be specifically opted into.