E1: 43: Change JP430000 processpurchaseorder To Validate Transaction Originator (Torg)
(Doc ID 2978495.1)
Last updated on OCTOBER 05, 2023
Applies to:
JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Currently processPurchaseOrder does not validate transaction Originator (TORG). The BSSV calls the purchase order entry MBF which copies the user profile data to populate transaction Originator (TORG). Currently one can populate detail tag <transactionOriginator> with any value and it will be written to the F4311 without any validation against a specific user.
The customer wants to have 2 user IDs used when creating the PO. One user ID populated in the header tag <wsse:Username>DN=TJ5903946,ENV=JPD920,ROLE=*ALL</wsse:Username> which will populate "Ordered By" and "User ID" in the F4301 and "User ID" in the F4311 and another user ID populated in the detail tag <transactionOriginator> to populate "Transaction Originator" in the F4311 that will be different than the User ID in F4311 and "Ordered By" and "User ID" in the F4301.
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 |
| Changes |
| Cause |
| Solution |
| References |