The following is the list of the conditions and restrictions:
• Buying organizations can specify whether or not the buyer should be involved in the requester change order process. This is regardless of the data (unit price, quantity, amount, need by date, start date and end date) changed by the requester on the requisition or the magnitude of the change. In cases where the buyer is not involved in the change order approval process, the system sends an FYI notification to the buyer when the change request is accepted.
• Administrators can setup upper and lower tolerance
limits with these attributes. So, for any change to these attributes
that lie within its tolerance limits, buyer approval would not be
required.
• The tolerances can be defined by either % amount or absolute amount.
• There is also an option to bypass buyer's approval if the PO was originally auto-created for the requisition. These controls are defined at OU level.
• Administrators can define an Upper Tolerance limit and a Lower Tolerance limit for all these attributes in the Tolerances and Routing for Requester Change Order workflow.
• At any given time, there can be only a single change request pending for each requisition. Until the pending change request is completely acted upon, the requester cannot request any new purchase order (PO) change requests for the requisition.
• Only the preparer of the requisition can request purchase order change requests for the requisition.
• If a purchase order line contains multiple distributions corresponding to the different requisition lines, then the purchase order line is not eligible for change request and none of the Oracle iProcurement requesters who prepared the requisitions can request changes to the purchase order.
• If the purchase order has any approval status other than Approved, then the purchase order is not eligible for a change request and none of the Oracle iProcurement requesters who prepared the requisitions associated with the purchase order can request changes to the purchase order.
• If the purchase order has a control status of Closed, Cancelled, Finally Closed, Freeze or Hold, then the purchase order is not eligible for a change request and none of the Oracle iProcurement user who prepared the requisitions associated with the purchase order can request changes to the purchase order.
• If the purchase order shipment has a control status of Closed, Cancelled, Finally Closed, Freeze or Hold, then the purchase order shipment is not eligible for a change request and none of the Oracle iProcurement requester who prepared the requisition lines associated with the purchase order shipment can request changes to the purchase order shipment.
• Price changes for non-catalog request items are not allowed for Partially Invoiced, Received, or Accrue on Receipt purchase orders, if the profile option PO: Allow Retroactive Pricing of POs is set to NEVER or OPEN RELEASES. If the profile option is set to ALL RELEASES, then the price changes are allowed, even for Partially Invoiced, Received, or Accrue on Receipt purchase orders.
• When the purchase order line contains a non-catalog request item in a foreign currency, the Oracle iProcurement requester can request a price change for that item in both the foreign currency of the item as well as the functional currency for the operating unit. In case of a price change request in the foreign currency of the item, the conversion rate used for the change request is the same as the one used at
the time of purchase order creation.
• While the purchase order change request is being approved in the Oracle iProcurement requester's approval hierarchy, if the purchase order becomes ineligible for change (purchase order goes into a Cancelled control status), then the purchase order change request is automatically rejected. The buyer does not receive the notification to process the change request. The change request does not appear
on the buyer self-service window.
• After the purchase order change request has been approved in the Oracle iProcurement requester's approval hierarchy and before the request is sent to the buyer on the purchase order for processing, a verification compares the requested values for the attributes on the change request and the current values on the purchase order. If these values are same, then the purchase order change request is
automatically accepted. The buyer does not receive the notification to approve the change request, nor does the request appear in the buyer self-service window.
• While the purchase order change request is being approved in the Oracle iProcurement requester's approval hierarchy, if the purchase order goes into an In Process approval status or a Requires Re-approval status, then the purchase order change request is deferred and is not sent to the buyer until the purchase order is in the Approved status.
• Encumbrance support (if enabled) is available for the change request. When the requester is creating the purchase order change request in Oracle iProcurement, the encumbrance funds verification runs for the revised requisition document total if there is a change (increase or decrease) to the document total. The actual funds reservation runs after the buyer responds to the purchase order change request.
• Tax support is available for the change request. While submitting the change request, the estimated tax that applies to the requisition is recomputed based on the revised requisition document total.
• If price breaks apply to the purchase order that are based on the changes that the requester has made, those price breaks apply to the purchase order."
In case the system rejects automatically the change order, verify if any of the conditions above is being violated.
In 11.5.10 the change order tolerances are set in the PO Change Request Tolerance Check workflow directly. In release 12 there is a page to set the tolerances in Purchasing responsibility > Setup > Tolerances and Routings.
• There is also an option to bypass buyer's approval if the PO was originally auto-created for the requisition. These controls are defined at OU level.
• Administrators can define an Upper Tolerance limit and a Lower Tolerance limit for all these attributes in the Tolerances and Routing for Requester Change Order workflow.
• At any given time, there can be only a single change request pending for each requisition. Until the pending change request is completely acted upon, the requester cannot request any new purchase order (PO) change requests for the requisition.
• Only the preparer of the requisition can request purchase order change requests for the requisition.
• If a purchase order line contains multiple distributions corresponding to the different requisition lines, then the purchase order line is not eligible for change request and none of the Oracle iProcurement requesters who prepared the requisitions can request changes to the purchase order.
• If the purchase order has any approval status other than Approved, then the purchase order is not eligible for a change request and none of the Oracle iProcurement requesters who prepared the requisitions associated with the purchase order can request changes to the purchase order.
• If the purchase order has a control status of Closed, Cancelled, Finally Closed, Freeze or Hold, then the purchase order is not eligible for a change request and none of the Oracle iProcurement user who prepared the requisitions associated with the purchase order can request changes to the purchase order.
• If the purchase order shipment has a control status of Closed, Cancelled, Finally Closed, Freeze or Hold, then the purchase order shipment is not eligible for a change request and none of the Oracle iProcurement requester who prepared the requisition lines associated with the purchase order shipment can request changes to the purchase order shipment.
• Price changes for non-catalog request items are not allowed for Partially Invoiced, Received, or Accrue on Receipt purchase orders, if the profile option PO: Allow Retroactive Pricing of POs is set to NEVER or OPEN RELEASES. If the profile option is set to ALL RELEASES, then the price changes are allowed, even for Partially Invoiced, Received, or Accrue on Receipt purchase orders.
• When the purchase order line contains a non-catalog request item in a foreign currency, the Oracle iProcurement requester can request a price change for that item in both the foreign currency of the item as well as the functional currency for the operating unit. In case of a price change request in the foreign currency of the item, the conversion rate used for the change request is the same as the one used at
the time of purchase order creation.
• While the purchase order change request is being approved in the Oracle iProcurement requester's approval hierarchy, if the purchase order becomes ineligible for change (purchase order goes into a Cancelled control status), then the purchase order change request is automatically rejected. The buyer does not receive the notification to process the change request. The change request does not appear
on the buyer self-service window.
• After the purchase order change request has been approved in the Oracle iProcurement requester's approval hierarchy and before the request is sent to the buyer on the purchase order for processing, a verification compares the requested values for the attributes on the change request and the current values on the purchase order. If these values are same, then the purchase order change request is
automatically accepted. The buyer does not receive the notification to approve the change request, nor does the request appear in the buyer self-service window.
• While the purchase order change request is being approved in the Oracle iProcurement requester's approval hierarchy, if the purchase order goes into an In Process approval status or a Requires Re-approval status, then the purchase order change request is deferred and is not sent to the buyer until the purchase order is in the Approved status.
• Encumbrance support (if enabled) is available for the change request. When the requester is creating the purchase order change request in Oracle iProcurement, the encumbrance funds verification runs for the revised requisition document total if there is a change (increase or decrease) to the document total. The actual funds reservation runs after the buyer responds to the purchase order change request.
• Tax support is available for the change request. While submitting the change request, the estimated tax that applies to the requisition is recomputed based on the revised requisition document total.
• If price breaks apply to the purchase order that are based on the changes that the requester has made, those price breaks apply to the purchase order."
In case the system rejects automatically the change order, verify if any of the conditions above is being violated.
In 11.5.10 the change order tolerances are set in the PO Change Request Tolerance Check workflow directly. In release 12 there is a page to set the tolerances in Purchasing responsibility > Setup > Tolerances and Routings.
Comments
Post a Comment