Defining Authorization Stages

Authorization Stage Setup (AUS) is used to define the separate levels of authorization a set of transactions may require to be fully authorized for processing. Several different authorization stages can be configured for a particular process, although not all of these may apply to a particular set of transactions. This is one of the Steps Required to Configure Authorization.

An authorization stage can be suspended by selecting the Suspend action, and re-opened by selecting the Re-Open action.

Authorization Stage Setup (AUS)

Stage Number
The number that uniquely identifies an authorization stage. Authorization can be required for several different Financials processes, as identified in the . The form contains the following fields: Stage Type field below. An authorization stage is linked to a stage type. The stage number determines the order in which these authorization stages are requested, if more than one authorization stage is required for a set of transactions.
Note: When numbering the authorization stages, you may want to group together stages within each authorization process. For example, Stage Numbers 1 to 100 may be reserved for payment authorization stages and 200 to 300 for ledger entry / import authorization stages. Leave gaps between stage numbers, so that any subsequently required additional stages can be easily inserted without having to rearrange the stage numbering.
Status
The status.
Lookup Code
The lookup code.
Description
The description.
Short Heading
The short heading.
Comment
Any additional text describing this stage in the authorization process.
Filter Definition Control Id
The filter to be used to identify the transactions requiring this stage of authorization. For example, this stage of authorization may only be required if the transactions reference a particular account code. The filter must have been defined using Filter Designer (FLD).
Note: When creating Authorization filters, the Filter Type must be Authorization Inquiry SAAUTH. The filter condition Authorization Set Reference must be included as a Runtime Entry at least once and the Blanks check box should normally not be checked. These check boxes are displayed on the Edit Condition dialog. No other data items must be defined as Runtime Entries.
User Team Code
The group of operators able to authorize the transactions at this authorization stage. User teams are defined using User Team Setup (UTS).
Authorizer
The default operator, within the user team, who is asked to authorize the transactions.
Stage Type
This is the type of Financials processing for the authorization stage. The authorization stages are carried out in stage number order, within this stage type. For example, this might be the first authorization stage for payment processing. The following types are available:
  • Payments
  • Matching/Allocations
  • Ledger Entry/Import.
Related topics