My Oracle Support Banner

When the ShipTo is not Defined in the Default Hierarchy, the Requisition Cannot be Saved After Adding New Items to an Existing Requisition. (Doc ID 2632410.1)

Last updated on JANUARY 24, 2020

Applies to:

PeopleSoft Enterprise SCM eProcurement - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When the ShipTo is not defined in the default hierarchy, the requisition cannot be saved after adding new items to an existing requisition.
 
The issue can be reproduced at will with the following steps:

1. Navigate : Setup Financials/Supply Chain > Common Definitions > User Preferences > Define User Preferences > VP1
2. Set Blank valuye to Ship To Location
3. Navigate : Setup Financials/Supply Chain > Product Related > Procurement Options > Purchasing > Requester Setup > VP1
4. Set Blank valuye to Ship To Location
5. Click Create Requisition
6. Add Special Request Item
7. Click Checkout
8. Click Submit
9. Getting warning message to enter Ship To
10. Navigate to schedule page and enter Ship To valule
11. Click Submit (Requisition # 180 created)
12. My Requisitions
13. Edit Requisition # 180
14. Click Continue Shopping
15. Add an item from Item History
16. Add Special Item
17. Click Checkout
18. Click Save
Issue 1 : Nothing Happened
19. Click Save Again
Getting Error

Changes

 Not Applicable

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.