To view the properties of the Verify Req Line Information process, select the process in the navigator tree, then choose Properties from the Edit menu. The Verify Req Line Information process has a result type of PO Req Line AutoCreatable?, indicating that when the process completes, it has a result of Automatic Creation Not Allowed, Automatic Creation Not Done Through Workflow, Not Enough Information For Autocreation, or Req Line Can Be Automatically Created. These results correspond to the lookup codes in the PO Req Line AutoCreatable? lookup type in the PO Create Documents item type.
This process activity is also runnable, indicating that it can be initiated as a top-level process to run by making calls to the Workflow Engine CreateProcess and StartProcess APIs.
The Verify Req Line Information process is initiated by the activity Launch Process To Verify Req Line Information.
The process begins at node 1.
Node 2 retrieves information from the requisition line. Node 3 checks how the profile option PO: Warn if RFQ Required before AutoCreate is set. If it is set to Yes, the requisition line is not on an RFQ, and RFQ Required is checked for the requisition line, the workflow stops automatic document creation because it is unable to issue the warning. This requisition line will be available in the AutoCreate Documents window. Otherwise, even if an RFQ is required for the requisition line, as long as the profile option PO: Warn if RFQ Required before AutoCreate is set to No, the workflow continues creating the document.
Node 5 checks if the requisition line has enough information from which to create a purchase order or release.
Node 7 checks if the requisition is an emergency requisition created in iProcurement, and node 8 checks if a procurement (credit) card number is associated with the requisition. Emergency and procurement card requisitions can be created in iProcurement only.
If the requisition line comes from an emergency or procurement card requisition, none of the activities related to node 12 are performed. Since the workflow does not require an emergency or procurement card requisition to have a source document associated with it, the workflow skips node 12, moves directly to node 9, and continues.
Note: Although a procurement card requisition line doesn't require a source document, if it is associated with a source document such as a blanket purchase agreement, the workflow (through the activity Group Requisition Lines, in a later subprocess) does create a release.
For all other requisition lines, the workflow uses node 12 to retrieve the source document type. If the source document is a quotation, or if the source document is a blanket purchase agreement but the requisition line is for a one-time item, node 9 inserts the requisition line into a temporary table as a candidate for automatic document creation, and the workflow continues.
For a requisition line that has a blanket purchase agreement as a source document (as determined by node 12) and that is not for a one-time time (as determined by node 13), the workflow at node 14 gives different results depending on the release generation method:
If there is no release generation method, the workflow ends at Node 15.
If the release generation method is Automatic Release/Review or Automatic Release, the workflow ends at node 16 or 17 respectively; instead the document will be created automatically through the Create Releases process.
If the release generation method is Release Using AutoCreate, node 19 checks the item attribute Should Workflow Create the Release? to see how you set up Purchasing. If you left this item attribute set to Y for Yes, the workflow creates the release. Otherwise, it ends at node 18, and you can create the release through the AutoCreate Documents window.
Note: No release generation method is retrieved for one-time items at node 14 since the Approved Supplier List does not support one-time items and the release generation method is specified in the Approved Supplier List. If the requisition line is for a one-item item but also associated with a blanket purchase agreement, the workflow does create a release from it later, using the activity Group Requisition Lines. The workflow in this case does not need to retrieve a release generation method from the Approved Supplier List.