MANUALS > Requisition > Requisition Switches > REQSEQ - Next Sequential Number for a Requisition and Requisition Authorization

REQSEQ - Next Sequential Number for a Requisition and Requisition Authorization

Next Sequential Number for a Requisition and Requisition Authorization

Affected windows: w_customer_orders_reservation_eu, w_pn_planning_requisition, w_pn_planning_requisition_multi, w_wo_reservation_eu, w_wo_reservation_eu_sub_wo_loop, w_requisition_detail_eu, w_requisition_header_eu, w_requisition_management_eu

Note: When Switch REQSEQ is set to Yes, Switch REQNOTIF becomes accessible/viewable.

The number specified in the Config Number field will determine the next sequential number for a Requisition when generated. Start number is set at implementation.

The following Config Number is set.

The next Requisition number is sequentially generated.

Additional Functionality: Authorization

Switch Set to Yes:

When set to Yes, and Switch REQATHREL is set to Yes, regardless of whether the user is configured for authorization, the Requisition will not be authorized.

When Switch REQSEQ is set to Yes and Switch REQATHREL is set to No, the user must be configured with sufficient authorization, before the Requisition is authorized.

Example 1: Switch REQATHREL is set to Yes.

The following User is configured with authorization.

The following Requisition Header is created.

The Requisition Detail is created, saved, and exited. The Requisition Release For Authorization pop-up window appears. Select 'Yes' to release the Requisition for Authorization.

The Requisition was not authorized.

Example 2: Switch REQATHREL is set to No.

The following User is not configured for authorization.

The Requisition Detail is created, saved, and exited. The following error appears informing the user that a higher level of authorization is required to release the Requisition.

The Requisition is not authorized.

Example 3:

The following User is configured for authorization.

The following Requisition is created.

The Requisition has been removed from the header because it has been authorized.

Switch Set to No:

When set to No, and Switch REQATHREL is set to Yes, regardless of whether the user is configured for authorization, the Requisition will not be authorized.

When Switch REQSEQ and REQATHREL are both set to No, regardless of whether the user is configured for authorization, the Requisition will be automatically authorized when the user exits the Requisition Detail.

Example 1: Switch REQATHREL is set to Yes.

The following User is configured for authorization.

The following Requisition Header is created.

The Requisition Detail is created, saved, and exited. The Requisition Release For Authorization pop-up window appears. Select 'Yes' to release the Requisition for Authorization.

The Requisition was not authorized.

Example 2: Switch REQATHREL is set to No.

The following User is not configured for Requisition Authorization.

The following Requisition Header is created.

The Requisition Detail is created, saved, and exited.

The Requisition has been removed from the header because it has been authorized.