# Oracle Fusion Procurement: approved requisition not creating a purchase order > Source: https://netray.co/erp-help/fusion-process-requisitions-not-creating-purchase-orders > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer An approved requisition becomes a purchase order only if its lines are processable: a supplier and site can be sourced, a buyer is assigned or derived, the procurement business unit is configured as a service provider for the requisitioning unit, and the Process Requisitions job picks the lines up. Check line status and the job log in that order. ## Kind how-to ## System oracle-fusion ## Erp Oracle Fusion Cloud ERP ## Module Procurement / Requisitions and Purchase Orders ## Query Oracle Fusion approved requisition not converting to purchase order Process Requisitions ## Alternate Queries - Fusion requisition stuck pending processing - Process Requisitions scheduled process no purchase order created - Fusion requisition line not picked up buyer procurement agent - Manage Requisition Lines Fusion create orders ## Applies To Oracle Fusion Cloud Procurement, current quarterly releases ## Steps ### Trace a requisition line to a purchase order **Items:** - Open Purchase Requisitions > Manage Requisitions and confirm the status is Approved, not Pending Approval or Incomplete. - Open Procurement > Purchase Orders > Manage Requisition Lines (or the Process Requisitions area) and find the line; note its processing status and any rejection reason. - Confirm a supplier and supplier site are on the line or can be sourced from a blanket agreement, a negotiation or a sourcing rule. - Verify that the line has a buyer assigned, or that the procurement agent for the procurement business unit and the item category exists in Manage Procurement Agents. - Check the business unit setup: the procurement business unit must be a service provider for the requisitioning business unit in Manage Business Unit configurations. - Run the Process Requisitions scheduled process with the right parameters, or enable auto-create so lines are processed by schedule. - Read the process log for lines it skipped and why, then fix the cause and run it again. - Open the created PO from Manage Orders and confirm the requisition line link, then submit it for approval. ## Sections ### The path a requisition line takes **Body:** After approval, a requisition line enters the procurement pipeline. If it references a blanket agreement or a supplier and site, it can be grouped into a purchase order by the Process Requisitions job (also called Create Orders in some flows). If sourcing cannot resolve a supplier, the line waits in Manage Requisition Lines for a buyer to source it manually, or for a negotiation to be created. This is why users report that a requisition is approved and then nothing happens. Nothing is broken in most cases: the line is waiting for a decision that the system cannot make by itself, such as which supplier to use, or it lacks an agent to own it. ### Setup gaps that block conversion **Body:** Procurement agent. A buyer must be authorised for the procurement business unit, with access to the relevant item categories and document types. Without an agent, lines cannot be assigned or processed, and users see them in no worklist. Set up agents and their access actions in Manage Procurement Agents. Service provider relationship. When the requisitioning and procurement business units differ, the procurement unit must be set up as a service provider to the requisitioning unit, with the Procurement and related services enabled. A missing assignment keeps lines from being processable. Sourcing. Without a purchase agreement that matches the item, category and supplier, the system has no supplier. Check blanket agreement effective dates, the status of the agreement and whether Use Agreements for sourcing is enabled for the requisitioning unit. Document style and approval. The purchase order document style must be active, and the approval rules must resolve an approver, otherwise the PO will remain Incomplete or Pending Approval after creation. ### Process Requisitions job parameters **Body:** The job takes parameters such as procurement business unit, requisitioning business unit, buyer, supplier, category and a grouping choice. A narrow parameter set can quietly exclude lines, so rerun with the parameters widened if you cannot find why a specific line is ignored. The job log lists the lines it considered and the ones it left for manual action. Grouping rules decide how many POs result. Lines with different suppliers, sites, bill-to or ship-to locations, currencies or payment terms end up on separate orders. Users are sometimes surprised by many small POs, and the cause is differing line attributes rather than a defect. **Code:** Navigator > Purchasing > Purchase Orders > Manage Requisition Lines Scheduled Processes > Process Requisitions Parameters: Procurement BU, Requisitioning BU, Buyer, Supplier, Group Requisitions Setup and Maintenance > Manage Procurement Agents Setup and Maintenance > Manage Business Unit Service Provider Relationships ### Special cases **Body:** Supply chain driven requisitions, such as those created by planning, behave like others but also depend on the item being purchasable and having a valid purchasing category. Drop ship or back-to-back orders from sales have their own processing status and are handled through the order management flow rather than a manual job. Punchout and catalog requisitions arrive with a supplier and price already attached, so they usually convert automatically when auto-create is on. If they do not, the first thing to check is the agent and the document style, not the catalog. ## Pitfalls - Assuming approval equals a PO; unsourced lines wait for a buyer by design. - Missing a procurement agent for the item category, so no one owns the line. - Running Process Requisitions with narrow parameters and concluding the job is broken. - Not defining the service provider relationship between requisitioning and procurement business units. - Expecting one PO per requisition when line attributes force several. ## Ai Angle A grounded assistant such as ERPray can list approved requisition lines that have been waiting for more than a few days, grouped by the reason they are not processable, such as no supplier, no buyer or no agent for the category. It reads the data without writing and shows the query. Creating orders and assigning buyers remain with the procurement team. ## Faq ### Why is my approved requisition not a purchase order? **Answer:** Most often the line has no resolvable supplier, no buyer or procurement agent, or the business unit service provider setup is missing. Check the line in Manage Requisition Lines for its status, then review agents, agreements and the Process Requisitions log. ### Do I need to run Process Requisitions manually? **Answer:** Not necessarily. You can schedule it or rely on auto-create for sourced lines. Run it manually when troubleshooting, or when you want to control timing. Unsourced lines still need a buyer to select a supplier. ### Why did one requisition create several purchase orders? **Answer:** Lines are grouped by supplier, site, currency, bill-to, ship-to and terms. Differing attributes split them into separate orders. This is expected behaviour, and the grouping choice in the job parameters influences it. ### Who can see unprocessed requisition lines? **Answer:** Buyers with access to the procurement business unit and the relevant categories through their procurement agent setup. If nobody sees the line, the agent setup is usually the gap. ## Search terms Process Requisitions Fusion, Manage Requisition Lines, Fusion requisition not converting to PO, Manage Procurement Agents, Oracle Fusion Procurement setup, service provider business unit Fusion, Fusion purchase order creation, requisition pending processing --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json