Tuesday, July 12, 2016

Touch less buying - Automatic PO creation

Yes it is possible to create PO Automatically without Agreements from Release 11, refer to first seven conditions below:
Requisition line's are eligible for Automatic PO Creation based on following conditions in order:

Condition 1:
(a)IF this Requisition line does not have a buyer assigned, THEN it does not qualify for automatic creation.
(b)IF the buyer assigned to the requisition line is not valid, THEN it does not qualify for automatic creation.

Condition 2:
IF this req line requires a negotiation, THEN it does not qualify for automatic creation.

Condition 3:
IF this req line does not have optimum supplier/supplier site, THEN it does not qualify for automatic creation.

Condition 4:
IF this req line has an item that is not purchasable in the default inventory organization of the assigned procurement BU, then it does not qualify for automatic creation.

Condition 5: IF this req line references a Procurement Card,
(a) IF SFO is implemented, and an active financial orchestration flow exists, then this req line does not qualify for automation.
(b) Verify the Procurement Card is active. If the validation fails then this req line does not qualify for automation.
(c) Verify that the optimum supplier site accepts the Procurement Card. If the validation fails then this req line does not qualify for automation.
(d) If the req line passes all the above checks, it qualifies for automatic creation without having to run through the rest of the Conditions.

Condition 6:
IF this req line is an emergency request and the emergency PO already exists, THEN the req line does not qualify for automatic creation.
ELSE it qualifies for automatic creation without having to run through the rest of the Conditions.

Condition 7:
IF this req line does not have a source agreement (agreement reference is null AND 'Determine Optimum Source' phase did not return any agreement reference), THEN check if following conditions are true :-
a) Requisition line has the ‘Negotiated’ flag checked AND
b) Procurement business function configuration allows automatic order generation for negotiated requisition lines.
If both these conditions are satisfied then this requisition line qualifies for automatic creation without having to run through the rest of the Conditions.

Condition 8:
IF this req line does not have a valid source agreement, THEN it does not qualify for automatic creation.

Condition 9:
IF the requisition line is sourced to a valid Contract Purchase Agreement and the 'Negotiated' flag is not checked on the requisition line, THEN this requisition line does not qualify for automatic creation.

Condition 10:
IF the 'Automatically Generate Orders' checkbox on the source agreement is not checked, THEN this requisition line does not qualify for automatic creation.

If a req line passes the Conditions, it is then considered eligible for automatic order creation, else:

1) The Req line is sait to be 'Failed Automation' if the requisition line references:

  • a procurement card and there is a financial orchestration flow applicable as returned by SFO
  • an emergency PO/flagged as an emergency requisition, or
  • an agreement with the control 'Automatically generate Orders' set to Yes.
2) The automation failure reason will be shown in Process Requisitons UI.

Yes behavior is confined to Procurement BU whose Confugraiton has flag 'Autogenerate orders from requester-negotiated requisition lines' checked.

4 comments:

  1. Interesting article about Puncout cXML.
    CXML Punchout

    ReplyDelete
  2. Thanks for sharing such a great blog about cXML Punchout.
    CXML Punchout




    ReplyDelete
  3. Thanks for sharing artile about OCI Punchout
    cXML PunchOut

    ReplyDelete
  4. cXML PunchOut - Commerce extensible markup language application who is a protocol created by Ariba used to communicate between sessions across the internet.
    Commerce Extensible Markup Language Punchout

    ReplyDelete