When it comes to using Pending Status mode, it is using direct table insert. Unfortunately, there isn't Oracle API available for this mode, so users will need to be extra diligent in testing before making the move to the production environment.
You are able to apply future item statuses to items.
Requirements:
Set the profile ‘More4Apps: IEW Activate Pending Item Status Mode’ to "Yes". Note that this is using a direct table insert to insert into the Oracle tables and is not supported by Oracle.
Rules and Exceptions:
Create/insert can only occur if an item exists in Oracle.
If item status control is at master level, then only master org level status changes are supported.
Only future dated pending statuses are allowed.
Duplicate pending statuses on the same date are not allowed.
For the pending statuses you can process an add transaction at the same time as a delete transaction.
Functionality Type:
This load type uses a custom API not supported by Oracle.
User Form Layout:
Spreadsheet Data Columns:
•Organization Code.
•Item Number - If Item Status is Master Org Controlled then any pending status validation will fail if the load is against a child org (same as catalog functionality).
•Pending Status – This uses the same list of values as the Item Status column used in Oracle.
•Status Effective Date - Must be greater to or equal to today’s date. Only one pending status for the item can have this date. Duplicate pending statuses on the same date are not allowed.
•Delete Pending Status –A Pending Status can only be deleted if it is in a pending state and not Implemented.
•Implemented Date – A read only field and is populated when using the download option.
