Learn about Redwood and be one of the first to join the conversation

Visit Redwood Community
Requisition number is consumed when incomplete req is deleted causing req number skipping — Cloud Customer Connect
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

Requisition number is consumed when incomplete req is deleted causing req number skipping

Accepted answer
2
Views
2
Comments

Summary:


Content (required):

When a user creates a requisition through enter requisition line and click on Save and Close or 'Shop', requisition gets saved in incomplete status and a requisition number gets generated to it. Now if a user delete this requisition and creates a new one, new number will be the next number in sequence as per Procurement Document Numbering setup. There is no gapless logic here.

This is a serious concern for a client and this may cause audit issue as well.

How to tackle this situation?

Version (include the version you are using, if applicable):

22C (11.13.22.07.0)

Code Snippet (add any code snippets that support your topic, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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