You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Responsive Self-Service Procurement: Unexpected Behavior while Selecting Charge Account

in Self Service Procurement 6 comments

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):

  1. When a Non-Catalog Request is initiated, the system automatically assigns the requestor's default expense account as the charge account.
  2. 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."
  3. 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.
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!