Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOracle E-Business Suite R12 has no single “automate requisitions” switch. Reliable automation is a chain: the requester submits a requisition, accounting and funds checks run, approval rules select approvers, sourcing identifies an eligible supplier or agreement, the PO Create Documents workflow creates a purchase order or release, and separate approval, receiving, matching, and closure processes finish the transaction. Approval automation and purchase-order automation are distinct stages, so an approved requisition can still require buyer action.
This guide applies to Oracle E-Business Suite R12 Purchasing and iProcurement, not Oracle Fusion Cloud Procurement. Labels and defaults can differ between R12.1, R12.2, patch levels, responsibilities, and customizations; verify every setting in the target instance.
The end-to-end requisition lifecycle
The normal automated path is:
- Create: A requester enters a catalog or noncatalog requisition in iProcurement or Purchasing.
- Validate: Account generation, charge-account validation, funds checking, encumbrance, inventory and receiving controls, and required-field checks run.
- Source: Sourcing rules, approved supplier information, quotations, blanket purchase agreements, or contract purchase agreements identify a purchasing source.
- Approve: The PO Requisition Approval workflow routes notifications through either standard Purchasing approval logic or Oracle Approvals Management (AME).
- AutoCreate: If permitted and eligible, the PO Create Documents workflow creates a standard PO or a release against a blanket agreement.
- Approve the PO: A separate PO approval workflow may approve the resulting document; creation does not imply approval.
- Execute: The buyer and supplier fulfill the order, receiving records the delivery, Payables matches invoices, and the document closes under normal controls.
The delivered requisition approval workflow is PO Requisition Approval (seeded file poxwfrqa.wft). Automatic document creation uses PO Create Documents (seeded file poxwfatc.wft). Related seeded processes include the PO Account Generator, PO Send Notifications for Purchasing Documents, Confirm Receipts, PO Change Request Tolerance Check, Requester Change Order Approval, and PO Change Approval for Requester. Oracle describes the requisition approval start and handoff to document creation in its Purchasing workflow documentation and the workflow attributes in its iProcurement implementation documentation.
What can be automated—and what remains optional
Define the desired scope before changing configuration. These are separate decisions:
- Approval routing and approver selection.
- Accounting-distribution generation.
- Supplier and agreement sourcing.
- Automatic creation of POs or blanket-agreement releases.
- Automatic approval of the resulting PO.
- Buyer assignment and notification delivery.
- Receipt confirmations and receipt-related notifications.
Agreement-backed catalog lines are usually the safest candidates for unattended processing. Free-text and other noncatalog lines often need buyer review because supplier, price, unit of measure, account, delivery, and agreement data may be incomplete.
Which R12 products own each stage
| Stage | Primary product or setup | Typical dependency |
|---|---|---|
| Requester entry | iProcurement and Purchasing | Items, categories, units of measure, organizations, locations, and requester security |
| Accounting and funds | General Ledger and Financials | Valid chart-of-accounts combinations, budgetary control, and encumbrance settings |
| Approval orchestration | Oracle Workflow | PO Requisition Approval, notifications, deferred processing, and workflow monitoring |
| Approval decisions | Purchasing hierarchy or AME | Jobs, positions, supervisors, approval groups, limits, or AME rules |
| Sourcing and documents | Purchasing | Quotations, agreements, sourcing rules, approved suppliers, buyers, and document types |
| Supplier and invoice execution | Payables and Purchasing | Supplier sites, matching controls, receiving options, and payment policies |
| Technical processing | System Administration | Concurrent managers, Workflow Background Engine, Document Approval Manager, and notification mailer |
Prerequisites before enabling automation
Organizational and master data
- Legal entities, ledgers, operating units, and inventory organizations.
- Financials, Purchasing, and Receiving Options, plus valid ship-to locations.
- Active employees, assignments, requesters, buyers, supervisors, jobs, and positions.
- Suppliers and valid supplier sites for the operating organization.
- Items, categories, purchasing attributes, units of measure, and inventory controls.
- Valid charge accounts and account combinations.
- Effective quotations, blanket purchase agreements, contract purchase agreements, or other approved sources where unattended creation is expected.
Workflow and system services
- Oracle Workflow item types and seeded processes are installed and valid.
- The Workflow Background Engine runs if deferred or background processing is selected.
- The Document Approval Manager is active; Oracle identifies it as required for approval document checks.
- Concurrent managers are available for relevant Purchasing programs.
- The Workflow Notification Mailer and outbound email requirements are configured if email is part of the process.
- Administrators can view workflow status, notifications, deferred activities, and errors.
Oracle’s implementation sequence also calls for organizations, units of measure, categories, personnel, Workflow, line types, Financials Options, receiving, suppliers, workflow-related processes, and automatic sourcing. See the Oracle Purchasing implementation guide.
Choose the approval model
| Model | How it works | Best fit | Main risks |
|---|---|---|---|
| Standard Purchasing approval | Uses employee/supervisor relationships or position hierarchies, approval groups, jobs, positions, authorization limits, and document types. | Organizationally based, stable rules. | Routing can change when HR or position data changes; complex conditions are difficult to express. |
| AME | Evaluates transaction attributes and applies conditions, actions, approver groups, and hierarchy rules through the Purchasing workflow. | Rules based on amount, category, cost center, project, organization, supplier, requester, preparer, or distribution data. | More governance is required; overlapping rules, precedence, and distribution behavior need testing. |
AME does not replace the requisition workflow. Oracle states that Purchasing still handles routing, notifications, and completion, while the workflow invokes AME when the document type is configured for it. See Oracle’s requisition approval and AME documentation and AME terminology and capabilities.
Configure standard Purchasing approvals
- Choose employee/supervisor routing or position-hierarchy routing. Oracle requires this choice; position routing requires positions as well as jobs.
- Define jobs and, when applicable, positions.
- Maintain employees, assignments, supervisors, and active user accounts.
- Create approval groups and define authorization limits, currencies, and control rules.
- Assign approval groups to the relevant jobs or positions.
- Associate the approval setup with the requisition document type.
- Test normal approval, insufficient authority, no approver, delegation, forwarding, rejection, and resubmission.
For the hierarchy requirements and setup concepts, use Oracle’s standard Purchasing approval documentation. “No Approver Available” is a workflow result, not a rejection; the seeded process distinguishes Approved, Invalid Action, No Approver Available, and Rejected outcomes.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteConfigure AME approvals
- Identify the requisition approval transaction type used by the implementation.
- List the required routing conditions before creating rules: amount, requester or preparer, item or category, cost center, project, organization, supplier, and distribution information.
- Define conditions, approval rules, action types, approver groups, and any serial or parallel behavior supported by the release.
- Associate the AME transaction type with the requisition document type.
- Test rule precedence, overlapping rules, missing approvers, and changes to employee or supervisor data.
A requisition has headers, lines, and distributions, but AME does not evaluate three independent levels. Oracle explains that a line with two distributions is treated as two lines for AME approval purposes. Also check whether document-style AME setup overrides document-type setup; Oracle documents that precedence in document-type workflow setup.
Set the requisition document type
The requisition document type is the central handoff point. In the relevant Purchasing setup, verify:
- Approval Workflow: normally the seeded PO Requisition Approval workflow.
- Workflow Startup Process: normally Main Requisition Approval Process.
- Approval Transaction Type: select the AME transaction type when AME is used; leave it blank for standard Purchasing approval logic.
- Autocreate Workflow: normally PO Create Documents.
- Autocreate Workflow Startup Process: normally Overall Document Creation / Launch Approval Process.
- Owner Can Approve: decide whether the document owner may approve within authority.
- Approval limits and controls: align them with policy, currency, hierarchy, and segregation-of-duties requirements.
Configure sourcing and agreement-backed creation
Automatic creation starts only when automatic creation is allowed, the requisition lines have eligible source documents, and sourcing is correctly configured. A quotation can result in a standard PO; a blanket purchase agreement generally results in a release rather than a new standard PO. A contract purchase agreement may be referenced when the workflow attributes and agreement setup permit it.
Validate all of the following:
- Sourcing rules and approved supplier lists, where used.
- Supplier and supplier-site status for the operating organization.
- Agreement effective dates, item or category coverage, price, currency, unit of measure, and organization compatibility.
- Buyer assignment, purchasing controls, line type, and document type.
- Whether each requisition line is eligible for unattended creation.
Configure PO Create Documents attributes
Review the seeded workflow item attributes in the target release rather than assuming a generic default. Oracle’s documentation presents differing default descriptions for automatic creation, so document type, workflow version, patch level, and implementation history matter.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Attribute | Function | Implementation question |
|---|---|---|
AUTOCREATE_DOC |
Determines whether automatic document creation is permitted for approved requisition lines. | Is unattended creation enabled for this document type and line population? |
AUTO_APPROVE_DOC |
Controls whether PO approval starts automatically after creation. | Should every eligible PO bypass a separate buyer or approver decision? |
CONT_WF_FOR_AC_REL_GEN |
Controls whether workflow creates the release or leaves release creation to the buyer through AutoCreate. | Should blanket-agreement demand become releases without buyer intervention? |
USE_CONTRACT_FLAG |
Controls whether an available contract purchase agreement is referenced when creating a standard PO. | May the workflow use a contract, and is the contract compatible? |
CONTRACT_REQUIRED_FLAG |
Requires a contract purchase agreement on the requisition line for automatic creation to succeed. | What should happen when no valid contract exists? |
See the detailed attribute descriptions in Oracle’s workflow documentation. Do not infer that automatic creation is enabled everywhere: verify the actual item attribute and document-type behavior in the instance.
Background versus online processing
Two controls are easy to confuse:
- PO: Workflow Processing Mode governs general Purchasing approval processing. Online processing completes an activity before the user continues; background processing defers eligible work to the Workflow Background Engine.
- Send PO Autocreation to Background specifically controls post-approval automatic document creation.
Background processing can keep high-volume checkout responsive, but it introduces a delay between approval and PO creation. It also requires a healthy Workflow Background Engine, concurrent managers, Document Approval Manager, and notification processing. Use it in production only after confirming frequent engine runs and monitoring deferred activity. Online processing is useful for controlled testing or low-volume paths, but it can make users wait.
Buyer AutoCreate versus workflow creation
| Path | Who controls the conversion | What it allows |
|---|---|---|
| Buyer AutoCreate | Buyer in Purchasing | Select and group lines, choose supplier or agreement, assign buyer, choose document type, and resolve exceptions manually. |
| Workflow-driven creation | PO Create Documents workflow | Create an eligible PO or release automatically after approval when attributes and sourcing permit it. |
| Create Standard Purchase Orders process | Concurrent program | Group multiple requisitions into standard POs using supplier or agreement information. |
Automatic conversion does not mean one requisition always produces one PO. Grouping rules may combine multiple requisitions or lines, while a blanket agreement may produce a release. Oracle documents both workflow creation and grouping behavior in Purchasing workflow guidance and document-creation setup.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A controlled implementation sequence
- Define policy: Identify eligible requisition types, thresholds, approvers, agreement requirements, noncatalog treatment, change-order rules, and no-approver or no-source outcomes.
- Prepare data: Validate HR, supplier, item, category, accounting, organization, agreement, buyer, and location records.
- Select approval: Use standard Purchasing hierarchy for simple organizational rules or AME for attribute-driven rules. Document precedence if both are present.
- Configure the document type: Set approval and autocreate workflows, startup processes, AME transaction type where applicable, owner approval, and limits.
- Configure sourcing: Establish agreements, quotations, sourcing rules, approved suppliers, buyer assignments, and effective dates.
- Set creation behavior: Decide PO creation, release creation, contract use, contract requirement, PO auto-approval, and online/background mode independently.
- Start services: Confirm Workflow Background Engine, Document Approval Manager, notification processing, concurrent managers, and relevant Purchasing programs.
- Test end to end: Use the matrix below before expanding automation by category or organization.
Test matrix
| Scenario | Expected approval result | Expected document result | First diagnostic location |
|---|---|---|---|
| Low-value catalog line with valid blanket agreement | Approver(s) selected and requisition approved | Release created if release creation is enabled | Requisition workflow status and agreement eligibility |
| High-value line over one limit | Multiple or escalated approvals | PO waits for its own approval unless auto-approval is enabled | Approval history, limits, and PO workflow |
| Multiple distributions | AME evaluates distribution behavior as documented | Creation depends on every required distribution and source | AME transaction details and distributions |
| Noncatalog line without agreement | Approval may succeed | Usually remains available for buyer AutoCreate | Source-document and autocreate eligibility |
| Expired or incompatible agreement | Approval may succeed | No automatic PO or release | Agreement dates, organization, supplier site, UOM, and currency |
| No approver returned | No Approver Available | No creation | Hierarchy or AME rule evaluation |
| Requester changes during approval | Current process is withdrawn and restarted after resubmission | Creation waits for the new approval cycle | Workflow history and change-order status |
| Background engine stopped | Deferred activities accumulate | Approval or creation is delayed | Workflow queues, engine schedule, and concurrent-manager log |
| Several eligible requisitions for one supplier | Each requisition is approved | Grouping process may create one standard PO | Grouping criteria and Create Standard Purchase Orders request |
Troubleshooting by symptom
“In Process” or no approval notification
- Check for a missing approver, invalid hierarchy, or AME rule returning no approver.
- Verify employee, user, supervisor, job, position, and assignment records.
- Check the Workflow Background Engine, notification mailer, Document Approval Manager, and deferred activities.
- Review the requisition workflow error and notification history rather than resubmitting blindly.
Approved requisition, no PO
- Confirm automatic creation is permitted for the document type and workflow instance.
- Check for a valid quotation, blanket agreement, contract, sourcing rule, supplier site, buyer, and purchasing assignment.
- Check contract-required and contract-use attributes, agreement dates, item or category coverage, organization, currency, price, and unit of measure.
- Review the PO Create Documents workflow for deferred or error activities.
PO created but not approved
- Check
AUTO_APPROVE_DOC. - Verify the PO approval workflow, hierarchy or AME rules, limits, and Document Approval Manager.
- Remember that a created PO can legitimately await a separate approval decision.
Wrong approver
- Confirm whether AME is enabled for this document type and whether the intended transaction type is selected.
- Check whether document-style AME setup overrides document-type setup.
- Verify the routing subject: requester, preparer, employee, supervisor, position, or another configured attribute.
- Check current HR records, approval limits, currency, overlapping rules, and distribution-level behavior.
Automatic creation is slow
- Check the two background controls separately.
- Verify Workflow Background Engine frequency, concurrent-manager workload, Document Approval Manager availability, and queue backlog.
- Review workflow errors and deferred activities before changing business rules.
Requester changes a requisition
Oracle’s workflow can withdraw the requisition from the current approval process when the requester changes it, then restart approval after resubmission. Approvers who had not acted may not receive the old notification. See Oracle’s requisition approval documentation.
Production governance
- Separate requester, approver, buyer, and supplier-maintenance duties.
- Use change control for AME rules, approval limits, seeded workflow customizations, and profile options.
- Monitor deferred activities, workflow errors, notification failures, concurrent requests, and inactive employees.
- Review approval limits, agreements, supplier sites, sourcing rules, and buyer assignments after organizational or supplier changes.
- Roll out by category, agreement type, or operating organization instead of enabling unattended creation for every requisition at once.
- Do not use undocumented direct database updates to change workflow attributes or approval setup; use supported application forms and governed customizations.
- Retest after R12.2 online patches, upgrades, workflow changes, and major HR or chart-of-accounts changes.
Go-live checklist
- R12.1 or R12.2 release and patch level documented.
- Organizations, locations, employees, jobs, positions, supervisors, requesters, and buyers validated.
- Items, categories, units of measure, accounts, suppliers, supplier sites, and receiving controls validated.
- Standard Purchasing hierarchy or AME selected, documented, and tested.
- Requisition document type points to the correct approval and autocreate workflows and startup processes.
- AME transaction-type precedence is understood where document-style and document-type setup both exist.
- Agreements, quotations, sourcing rules, approved suppliers, effective dates, and buyer assignments tested.
AUTOCREATE_DOC,AUTO_APPROVE_DOC,CONT_WF_FOR_AC_REL_GEN,USE_CONTRACT_FLAG, andCONTRACT_REQUIRED_FLAGreviewed in the target workflow.- Online/background choices made separately for approval and autocreation.
- Workflow Background Engine, Document Approval Manager, notification mailer, concurrent managers, and monitoring access confirmed.
- Tests completed for approval, rejection, no approver, changed requisition, invalid source, delayed background work, PO approval, grouping, receiving, and invoice matching.
The Bottom Line
Automate Oracle R12 requisitions as a controlled chain, not a single switch: establish clean master data, choose one approval model, configure the requisition and PO workflows, provide valid sourcing documents, and operate the background services that move deferred work. The decisive test is not whether a requisition reaches “Approved,” but whether each eligible line can safely become the intended PO or agreement release under the organization’s approval and financial controls.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
