PRC:PO: 23C Bug Fix Is Not Working - Bypass Location Validation On Changes To Fulfilled Purchase Orders
(Doc ID 2967184.1)
Last updated on AUGUST 15, 2023
Applies to:
Oracle Fusion Purchasing Cloud Service - Version 11.13.23.07.0 and laterOracle Fusion Purchasing - Version 11.1.9.2.0 and later
Information in this document applies to any platform.
Symptoms
23C Bug fix is not working - Bypass Location Validation on Changes to Fulfilled Purchase Orders
Acceptance Criteria
- Applicable to default ship-to location at the header, ship-to location at line and deliver-to location at schedule/distribution level on a change order
- If the default ship to location is inactive, then we should not validate it irrespective if the field is read only or editable as long as there is downstream activity on the purchase order
- For location on the children,
- current behavior is such that location is validated everytime user makes a change to need-by-date/price/amount at the schedule or requester at the distribution level. If the location is read-only, it means po either has an invoice or receipt. New behavior is such that if the location is inactivated and read only, then it should not be validated since it can not be updated anyway
- If location is no longer valid and is not read only, then allow user to update it and continue with validating it.
- No differentiation for expense or inventory destination type
Acceptance Tests
1.
Scenario: Default Ship-to location at the header level is no longer active
Given a CO with an inactive ship-to location
And there exists an invoice on the PO
When the buyer updates the requester on the CO distribution and submits the CO for approval
Then the submission check validation on header location does not appear
And buyer can submit the change order
2.
Scenario: Ship-to location at the line level is read only and it is no longer active
Given a CO with an inactive read only ship-to location
And there exists an invoice on the PO
When the buyer updates the requester on the CO distribution and submits the CO for approval
Then the submission check validation on location does not appear
And buyer can submit the change order
3.
Scenario: Ship-to location at the schedule level is read only and it is no longer active
Given a CO with an inactive read only ship-to location
And there exists a receipt on the PO
When the buyer updates the line amount on the CO and submits the CO for approval
Then the submission check validation on location does not appear
And buyer can submit the change order
4.
Scenario: Deliver-to location at the distribution level is read only and it is no longer active
Given a CO with an inactive read only deliver-to location
And there exists a receipt on the PO
When the buyer updates the need-by date on the CO and submits the CO for approval
Then the submission check validation on location does not appear
And buyer can submit the change order
5.
Scenario: Buyer should be able to update the price on PO even if the location is inactive and field is read-only
Given a CO with an inactive read only location
When the buyer updates the price on the CO and submits the CO for approval
Then the submission check validation on location does not appear
And buyer can submit the change order
6.
Scenario: Perform submission check validation if buyer is updating the inactive ship-to location on CO
Given a CO with an inactive ship-to location at the line level
When the buyer updates the location on the CO and submits the CO for approval
Then the ship-to location on the line gets validated through submission check
And buyer can or can not submit the change order based on the submission check error
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Acceptance Criteria |
Acceptance Tests |
Changes |
Cause |
Solution |