Responsive Self-Service Procurement: Unexpected Behavior while Selecting Charge Account
Dear Oracle Community Experts,
We've encountered an issue with creating Non-Catalog Requests in the Responsive Self-Service Procurement application following the recent 24A upgrade.
Current Behavior (Please see the attached file for the screenshots below):
- When a Non-Catalog Request is initiated, the system automatically assigns the requestor's default expense account as the charge account.
- If the requisitioning Business Unit (BU) requires a different company code than the one associated with the default expense account (e.g.,Company Code 102 in this case), an error message appears upon submission: "The charge account isn't valid."
- Clicking "Edit" on the line and using the "Search for combination" option does not highlight the problematic code, unlike the Classic Self-Service Procurement (SSP) experience.
0