PO Acceptance Upload records buyer-side acceptances (acknowledgments) against existing approved Oracle Purchasing documents – Standard, Blanket, Contract and Planned POs and Blanket Releases – from Excel, via the standard Oracle Purchasing public API. It captures whether the buyer accepts the document, the acceptance type, date, accepting employee and an optional note.
When to use it
- Record buyer acknowledgment/acceptance of one or many approved POs or Blanket Releases in bulk.
- Capture supplier-order acknowledgments back into EBS where the buyer confirms acceptance on behalf of the organization.
- Backfill acceptance history with a specific acceptance date and acceptance type per document.
- Set the accepting employee and role on each acceptance.
- Attach acceptance descriptive flexfield values at the time of recording.
Before you start
- Blitz Report is installed and you are signed in to a responsibility with access to the operating unit.
- An existing purchase document exists for the operating unit – not cancelled, not finally closed, in status Approved, Requires Reapproval, or Incomplete.
- If you enter a revision, it must be the document’s current revision.
Step 1 – Set the parameters and download
In Blitz Report, open PO Acceptance Upload and set the parameters:
| Parameter | Purpose |
|---|---|
| Operating Unit | The operating unit the documents belong to. |
| Default Action | The acceptance Action used when the Action column is left blank (default New). |
| Default Action Date | The acceptance Action Date used when the column is blank; if that’s also blank, the current date is used. |
Run the upload to download and open the Excel file. This upload records new buyer acceptances – the template opens empty.
Step 2 – Enter the acceptances
On each row enter the Operating Unit and PO Number (and Release for a Blanket Release), set Accepted (Yes/No) and the Acceptance Type, and optionally the Action, Action Date, Accepted By Employee, Role and Comments. Supplier columns are optional – they only help narrow the PO Number list.
Step 3 – Validate and Save
Click Validate and Save. This checks for missing required values and runs the upload’s validation, then saves the file. Correct anything it flags before continuing.
Step 4 – Upload and view the result
Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which records each acceptance. When it finishes, a result report opens showing each row as success or error.
What’s produced
- Recorded buyer acceptances against the selected purchase documents.
- A result report listing every row with a status (success or error) and a message.
Common questions
Can I update or delete existing acceptances with this upload?
No. It only records new buyer acceptances; the template always opens empty and there is no update or delete capability.
Can I record supplier acceptances?
No. Only buyer acceptances are supported.
Do I have to fill in the supplier columns?
No. They are optional and exist only to narrow the PO Number list; you can type the PO Number directly.
What happens if I leave Action or Action Date blank?
Action falls back to the Default Action parameter (default New); Action Date falls back to the Default Action Date parameter, and if that’s also blank, the current date is used.
What if I don’t specify an accepting employee?
The PO/Release buyer is used as the accepted-by. If the employee name isn’t unique, also supply the employee number.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| PO Number is not valid / not unique | No PO matches that number in the operating unit, or more than one does. | Choose the PO Number from the dropdown; verify the operating unit; narrow by supplier if duplicated. |
| Release Number is not valid | The release number doesn’t exist for that PO. | Select a valid Release for the chosen Blanket PO. |
| Revision does not match the document’s current revision | The Revision entered isn’t the document’s current revision. | Leave Revision blank or enter the current revision number shown in the message. |
| Accepted By is not a valid current employee / not unique | The employee name/number doesn’t resolve to one current buyer-agent employee. | Use the dropdown; add the employee number to disambiguate, or leave blank to default to the buyer. |
| Flexfield validation error | An attribute value failed validation for the acceptance flexfield. | Correct the attribute category and values against the flexfield’s allowed values. |