Size limit of 500 rows
We have recently received confirmation from Oracle that the User Interface is designed with a limit of 500 rows for requisitions. As a result, we now advise against creating requisitions with more than 500 rows. If you do create larger requisitions, you will not be able to view or submit them for approval, either through our integrator or manually within the cloud application. In this case, you will need to delete the requisitions.
You should not create requisitions with 500+ rows (lines or distributions). You should split large requisitions into 500 rows or less.
The limitations mentioned may be subject to change as Oracle continues to enhance and improve their gateways.
Batching
The Integrator employs the Oracle batch service to upload data in batches of a predefined size (currently 50) for each section. In case of an error in a batch, the entire batch will be rejected. For instance, if there are no errors in the header section but a line or distribution is rejected, the header batch will be created, but not the lines or distributions. You will need to correct and re-upload the problematic line or distribution.
Currency
It's important to note that the creation of purchase requisitions using the Oracle REST service is only supported for the same currency as the ledger currency.
Sourcing Agreements
The current version of the integrator does not provide an option to specify the source agreement, whether it is a Blanket Purchase Agreement (BPA) or Contract Purchase Agreement (CPA). However, if Touchless PO creation is configured, then the read-only sourcing agreement columns will be automatically populated upon download. It is important to note that this behavior is determined by your configuration settings and not by the integrator itself.
Project Information
Project information can be validated and uploaded as expected.
Note: If the destination type is Inventory, then the inventory organization must have the “Inventory Tracking by Project flag” enabled.
The REST service does not download the Project Name and Task Name fields, only the Project Number and Task Number. However, the Project Name and Task Name can be derived from the number upon validation or upload.
Descriptive Flexfields (Fixed in release 13.4.9.0)
Descriptive flexfields can be uploaded in the Integrator with the following limitations:
● The Supported Oracle ERP Cloud web service does not detect the required list of values. If a DFF segment is mandatory the web service still allows a null value. We are currently working on resolving this, and present the following workaround:
Enter an invalid value, such as ‘XXXX’, into the Default Row (Row 10) attribute field. The web service will error as expected which will signify to the user that the attribute is a required field:
This will only work for lists of values in DFFs that are required. For text fields we suggest entering notes on rows 7 or above in the sheet:
Descriptive Flexfields List of Values
Dependent and independent descriptive flex fields have list of value support. Table based lists of values are not supported (validation still is supported)
The list of values is limited to the first 500 values to ensure the integrator does not freeze or time out on large data sets. This does not affect validation. If the value is in the list below 500 it is still a valid value.
Attachments
Attachments can only be created or added to requisitions with a status of INCOMPLETE. To achieve this, you must set “Submit for Approval” to No or leave it blank.
We currently cannot support download or update of attachments.
Refer to the Attachment documentation for more information on these limitations.
