Requisition Attributes

The table lists all the attributes within the three requisition dimensions that are available for you to create approval routing rules for requisitions. Attributes marked with asterisk (*) when used in approval rules need an explicit mention that it isn't a blank rule.

These are header level attributes.

Attribute	Notes
Change in Approval Amount of Modified Lines	Amount of the difference between Original Approval Amount of Modified Lines and New Approval Amount of Modified Lines (includes nonrecoverable taxes).
Change in Requisition Amount of Modified Lines	Amount of the difference between Original Requisition Amount of Modified Lines and New Requisition Amount of Modified Lines.
Document Fiscal Classification	Tax attribute
Emergency Requisition	Indicates if the requisition is an emergency requisition.
Functional Currency	Currency code of the requisitioning BU
Funds Check Failure or Warning	Identifies that funds check upon requisition submission has warnings.
Funds Override Approver	User who can approve the request for funds override.
Funds Override Approver User Name	Name of the user who can approve the request for funds override.
Header Attribute Category	Attribute category for Requisition Header
* Header Number Attribute 1 - 20	Numeric Descriptive Flexfield attributes
Header Text Attribute 1 20	Text Descriptive Flexfield attributes
Insufficient Funds	Indicates whether the requisition was submitted with funds override request.
Interface Source Code	Used in requisition import to identify import source.
Internal Transfer Requisition	A requisition containing items which are internal to the company.
Ledger	Ledger used for the requisitioning BU.
New Approval Amount of Modified Lines	Sum of the amount for the new lines added during an update from catalog or split operation plus including nonrecoverable taxes.
New Requisition Amount of Modified Lines	Sum of the amount for the new lines added during an update from catalog or split operation.
Original Approval Amount of Modified Lines	Amount for the replaced or split line, including nonrecoverable taxes.
Original Requisition Amount of Modified Lines	Amount for the replaced or split line, excluding taxes.
* Overriding Approver	Approver specified to override the application generated approver.
* Overriding Approver Position ID	Attribute used in position hierarchy routing when the Position Chain Of or the Approval Chain Of is Overriding Approver (only supported from BPM).
Percentage Change in Approval Amount of Modified Lines	Difference as a percentage between Original Approval Amount of Modified Lines and New Approval Amount of Modified Lines (includes nonrecoverable taxes).
Percentage Change in Requisition Amount of Modified Lines	Difference as a percentage between Original Requisition Amount of Modified Lines and New Requisition Amount of Modified Lines.
Preparer	Person who submitted the requisition.
Preparer Department Id	Department ID of the person who submitted the requisition.
Preparer Department Name	Department name of the person who submitted the requisition.
* Preparer Grade Code	Grade code of the person who submitted the requisition.
Preparer Job	Job code of the person who submitted the requisition.
Preparer Job Level	Job level of the person who submitted the requisition.
* Preparer's Position	Position ID of the person who submitted the requisition.
Preparer Username	User name of the person who submitted the requisition.
Requisition Amount	Total amount of the requisition.
Requisition Approval Amount	Requisition amount with nonrecoverable taxes.
Requisition DFF Context	Descriptive flexfield context on the requisition header(only supported from BPM).
Requisitioning BU	BU in which the requisition is created.
Taxation Country	The country in which the transaction is deemed to have taken place for taxation purpose.
Requisition Description	Displays free-form text to enter a value.
Requisition BU Name	Displays free-form text to enter a value.

This table lists the requisitions line level attributes.

Attribute	Notes
* Agreement	Agreement Number on the requisition line.
* Agreement Buyer	Buyer of the agreement on the requisition line.
* Agreement Header Amount Released	Released amount on the header of the agreement on the requisition line.
* Agreement Line	Line number of the agreement on the requisition line.
* Agreement Line Amount	Agreement line amount of the agreement on the requisition line.
Agreement Line Amount Exceeded Indicator	True if requisition line amount exceeds agreement line amount limit.
* Agreement Line Amount Overage	Amount that the requisition line amount exceeds agreement line amount limit.
* Assessable Value	The deemed price at which a product is valued, by a tax authority, for tax calculation purposes.
Assigned Buyer	Buyer assigned to process requisition line.
Assigned Buyer User Name	User name of the assigned buyer.
Category Name	Name of the category on the requisition line.
Deliver-to Location	Location to which the request should be delivered.
Deliver-to Organization	Organization of the location to which the request should be delivered.
Destination Type	Type of the destination, either Expense or Inventory.
Hazard Class	Hazard classification for the requisition line.
* Intended Use	A tax classification based on the purpose for which a product is used.
Item	Item number
Item Revision	Revision number of the item on the requisition line.
Item Source	Identifies the source from which item is added, such as noncatalog request, punchout catalog, local catalog, and so on.
Line Amount	Total amount of the requisition line.
Line Approval Amount	Line amount with nonrecoverable taxes.
Line DFF Context	Descriptive Flexfield context on the requisition line(only supported from BPM).
Line Attribute Category	Attribute category on the requisition line.
* Line Number Attribute 1 - 20	Numeric Descriptive Flexfield attributes
Line Text Attribute 1 - 20	Text Descriptive Flexfield attributes
Line Type	Line type, such as Goods or Amount Based
Manufacturer	Manufacturer of the request.
Manufacturer Part Number	Manufacturer Part number of the request.
Negotiation Required	Indicates if negotiation is required for the requisition line.
New Supplier	Indicates if a new supplier is specified on the requisition line.
* Price	Price of the requisition line in functional currency.
Procurement Card	Indicates if a procurement card is used.
Procurement Category Hierarchy (Level 1 - 10)	Category hierarchy used to classify products that the organization purchases.
Product Category	A tax classification based on category of items entered at transaction time.
^ Product Fiscal Classification	A tax classification used to categorize a product for a tax and which are applicable.
Product Type	A tax classification based on type of products (for example, goods).
* Quantity	Quantity requested
Requester	Person for which the line was requested.
Requester Department Id	Department Id of the person for whom the line was requested.
Requester Department Name	Department name of the person for whom the line was requested
* Requester Grade Code	Grade code of the person for whom the line was requested.
Requester Job	Job code of person for which the line was requested.
Requester Job Level	Job Level of person for which the line was requested.
Requester Level 1 - 10 Supervisor User Name	User name of the top 10 worker in the supervisory hierarchy of the requester. Requester Level 1 Supervisor User Name being the user name of the topmost worker.
Requester Level 1 -10 Supervisor	Supervisor in the supervisory hierarchy chain of the requester. Requester Level 1 Supervisor being the topmost worker on the supervisory chain.
*Requester's Position	Position ID of the person for which the line was requested.
Requester Username	User name of the person for which the line was requested.
* Smart Form	Name of the smart form on the requisition line.
Source Organization	Inventory organization which will supply the item to the destination inventory in internal material transfer.
Source Type	Indicates the type of source of supply for the requisition line, for example, source type is internal for inventory organization and external for suppliers.
* Subinventory	Subinventory to which the request should be delivered, if destination type is Inventory.
* Suggested Buyer	Suggested buyer on the requisition line.
* Supplier	Supplier of the line requested.
Supplier Configuration ID	ID used to identify a configurable item.
Supplier D-U-N-S	Identifier for the supplier.
Supplier Item	Supplier item number of the line requested.
* Supplier Site	Site from which the supplier will process the request.
Tax Classification	Tax classification code entered on the transaction for tax determination purpose.
Transaction Business Category	A tax classification used to classify a transaction line to define the type of transaction (for example, Purchase Transaction).
UN Number	Hazardous substance identifier
UNSPSC	United Nations Standard Products and Services Code used to classify a request
UOM	Unit of measure of the line requested.
Urgent	Indicates if the line is an urgent request.
User Defined Fiscal Classification	User defined tax classification used to classify transactions to drive tax determination and reporting.
Category Name	Displays free-form text to enter a value.
Supplier Organization Type	Displays free-form text to enter a value.
Negotiated by Preparer	Displays free-form text to enter a value.
Available Blanket Amount	Displays free-form text to enter a value.
Deliver-to Location Code	Displays free-form text to enter a value.

This table includes requisition distribution level attributes.

Attributes	Notes
Award Owning Business Unit	The business unit that manages and owns the grant award.
Award Purpose	Description of an activity that the award is funding. For example, research or clinical trials.
Award Type	Classification of an award. For example, federal grant or private grant.
Balancing Segment Value	Balancing segment of the chart of accounts.
Contract	The display name of the award contract.
Charge Account	Account to which the requested item should be charged.
Chart of Accounts	Name of the chart of accounts associated with the business unit.
Cost Center	A unit within an organization to which costs may be charged for accounting purposes.
* Cost Center Manager	The manager of a unit within an organization to whom the costs may be charged for accounting purposes.
Cost Center Manager User Name	The user name of the manager of a unit within an organization to which costs may be charged for accounting purposes.
Distribution Amount	Total amount on the distribution.
Distribution Approval Amount	Distribution amount including nonrecoverable tax.
Distribution Attribute Category	Attribute category for requisition distribution.
Distribution DFF Context	Descriptive flexfield context on the requisition distribution(only supported from BPM).
* Distribution Number Attribute 1 - 20	Numeric Descriptive Flexfield attributes
Distribution Text Attribute 1 - 20	Text Descriptive Flexfield attributes
* Expenditure Organization	An organization that incurs expenditures and holds financial plans for projects.
* Expenditure Type	A classification of cost assigned to each expenditure item, such as calculating raw costs, to plan, budget, forecast, and report on projects.
Funding Source	Display name of the source of the funding that's associated to the award.
Natural Account	Natural Account segment of the chart of accounts.
Principal Investigator	Person responsible for the performance of the award.
Principal Investigator User Name	The User Name of person responsible for the performance of the award.
* Project	Name of the project business manages
Project Billable	Indicates whether the project is billable or not. Available in Release 13 Update C.
Project Capitalizable	Indicates whether the project is capitalizable or not. Available in Release 13 Update C.
Project Funding Source	Party that's funding the project, for example, external customer or internal organization. Available in Release 13 Update C.
Project Manager	Project Manager of the project.
Project Manager Username	User name of the project manager.
Project Owning Business Unit	Display name of the business unit that owns the project.
Project Reserved Attribute 1 - 10	Reserved for future use in the project cost collection flexfield. Available in Release 13 Update C.
Project Type	Primary classification for the projects business manages.
Project User Defined Attribute 1 - 10	User-defined segment of the project cost collection flexfield. Available in Release 13 Update C.
Project Work Type	A classification of the work associated with a project task. Available in Release 13 Update C.
Task	Name of the task associated with a project.
Project Owning BU Name	Displays free-form text to enter a value.
Project Type Name	Displays free-form text to enter a value.

Considerations

Consider these requisition related considerations.

For amount-specific approval rules you should do either or these:
- Either include the requisitioning business unit in the condition along with specifying the approval amount in the functional currency of the requisitioning business unit (optionally include the functional currency) if approval policies differ across business units.
  
  If Requisition Approval Amount less than or equals 500 and Functional Currency equals USD and Sold-to BU is Vision USA.
- Or use the currency conversion rate function if approval limits are enforced in a standard currency. Create a user-defined attribute with currency based type to convert the amount currency in documents to the currency of the approval rule.
For each participant that's in use (that's, not disabled), at least one rule must apply when a document is submitted for approvals. AMX doesn't auto approve if the document attributes don't meet the conditions of any of the existing rules within a participant.
- Example 1: You use the Header Hierarchy participant to set up rules based on requisition amounts with the following conditions:
  - Requisitions more than 500 USD and under 1000 USD requires 1 level.
  - Requisitions more than or equal to 1000 USD and under 2000 USD requires 2 levels.
  - Requisitions more than or equal to 2000 USD requires 3 levels.
    
    This means that requisitions under or equal to 500 USD don't require approvals. In this case, you will need to create a rule to automatically approve the requisition.
  - Example 2: You use the Preapproval Header Consensus participant to set up rules based on categories on the requisition line. You need additional approvals routed for the following two categories:
    - IT Equipment
    - Office Furniture
      
      You must add a rule to automatically approve the remaining categories in this participant.
  - Example 3: You use the Preapproval Header Consensus participant to set up rules based on smart forms on the requisition line. You need additional approvals routed for the following smart form:
    
    Work Visa Request
    
    Condition: If Smart Form Is Not blank and Smart Form Equals Work Visa Request.
    - Make sure to add a condition to check that the attribute isn't empty. This applies to all rules using attributes in a document that may contain no value.
      
      Since not every requisition line will have a smart form associated, you must add an autoapproval rule for the following:
      
      If (Smart Form Is Not blank and Doesn't equal Work Visa Request) or Smart Form Is blank.
    - Example 4: You use the Serial Approval participant in First Stage Approvals to set up rules based on Tax Organization Type for supplier registration requests.
      
      Condition: If Tax Organization Type equals Individual.
      
      To ensure that approvals are generated successfully, you can:
      1. Create multiple rule conditions using an OR separator where you expect at least one condition to be true.
      2. Add another rule in the same participant to ensure that it covers the supplier registration requests where Tax Organization Type doesn't equal Individual, since not all registrations will have this value.
    - Example 5: You use the Serial Approval participant in First Stage Approvals to set up an approval rule with the following condition in supplier registration:
      
      Condition: If Bank Account Country equals United States.
      
      For this condition to evaluate to true, the registration request must have bank account details entered and the bank account country is United States. If the registration request doesn't contain any bank account information, this rule won't apply.
      
      To ensure that approvals are generated successfully, the participant must contain another rule with a condition that will apply if bank account information doesn't exist, using If Bank Account Entered Is No.
      
      This applies to approval rules created using attributes from these dimensions: Contacts, Addresses, Business Classifications, Bank Accounts and Products and Services Category. The following attributes should be used to handle cases where no information is provided for registrations for the respective children entities if attributes on these dimensions are used in rule evaluation.
      1. For Contacts, use Contact Entered.
      2. For Addresses, use Address Entered.
      3. For Business Classifications, use Business Classification Entered.
      4. For Bank Accounts, use Bank Account Entered.
      5. For Product and Services Category, use Product and Services Category Entered.
    - All approvers returned within a participant that's routed in serial are ordered and notified in sequence.
      
      For example, the following rules are evaluated to true in the Header Hierarchy participant for a requisition with 2 lines:
      
      Line 1 satisfies rule 1: If requisition line belongs to the IT category and amount is less than 500 USD, then approval is required from the IT Manager and IT Director.
      
      Line 2 satisfies rule 2: If requisition line belongs to the Facilities category and amount is greater than 1500 USD, then approval is required from the Facilities Manager and Facilities Director.
      
      In this case, within the Header Hierarchy participant, approvals will be routed in the following order:
      - IT Manager
      - IT Director
      - Facilities Manager
      - Facilities Director
      If your organization has a need to route a document for approvals to more than one hierarchical path concurrently, you should use more than one serial based participant. You can use Header Hierarchy, Header Hierarchy 2 and Header Hierarchy 3 participants in the Header Stage to maintain your rules based on your organization's requirements.
  - Only one rule within a participant with first responder wins voting regime should evaluate to true for a given document.
    
    If more than one rule applies within a first responder wins participant, the approvers returned by each rule will be grouped together where only one response from this group will determine the approval outcome.
    1. For example, within the Header First Responder Wins participant:
      1. These rules are defined:
        
        Rule 1 includes approvers from the IT Approval Group if a requisition contains a line from the IT category.
        
        Rule 2 includes approvers from the Legal Approval Group if a requisition contains a line from the Legal category.
      2. If both conditions are met and the two rules are triggered, then approvers from both the IT Approval Group and the Legal Approval Group are returned. However, if an approver from the IT Approval Group approves the requisition, this participant is considered approved, and no actions would be required from the Legal Approval Group.
    2. To satisfy the requirement where at least one rule must apply within a participant, you can set up a rule to use an empty approval group rule for the conditions where no approvals are required in a first responder wins participant. This option will ensure that the participant doesn't get auto-approved in the event where the document contains objects that satisfy both rules that require approvals and rules that don't require approvals. Using the supervisory hierarchy based autoapproval option would be treated as an approval response for the participant, hence bypassing the other rules that actually would require approvals.
      
      Autoapproval rule using an empty approval group
      - Select Rule always applies when creating a rule
      - Action Type = Approval required
      - Route Using = Approval group
      - Approval Group = No Approvals
      - This group has to be created in the Approval Groups tab in BPM Worklist application without any participants specified.
      - Automatically approve if group returns no approvers = Checked
    You can the first responder wins based participants across the different stages if your organization requires different groups of approvers to provide approvals independently.
    
    Using the same preceding example.
    1. Rule 1 can be added to the Preapproval Header First Responder Wins participant, along with an autoapproval rule to satisfy the requirement where at least one rule must evaluate to true.
    2. Rule 2 can be added to the Header Stage First Responder Wins participant, along with an autoapproval rule to satisfy the requirement where at least one rule must evaluate to true.
    3. A response from Preapproval Header First Responder Wins participant will be required from the IT Approval Group. And a separate response from the Header Stage First Responder Wins participant will be required from the Legal Approval Group.
Line level withdrawal from approved requisition is supported.

Example: An approved requisition (not in PO) has 4 lines. You, as a preparer, select line 2 and withdraw that line. You then modify line 2 and resubmit for approval. Only line 2 will now be routed for reapproval based on the approval rules defined. All other lines will remain in its current state.
On the Configure Requisitioning Business Function page, there are three approval related controls a user can define:
- Reapproval required for changes made during an active approval process: This controls whether a requisition must be sent back for reapproval whenever an approver makes a modification to the requisition. It is unchecked by default.
  
  Example: When an approver modifies a requisition line and submits the requisition AND if this checkbox is checked, a new approval process is started.
- Approval required for buyer modified lines: This controls if lines modified by buyer will be submitted for approval. It is unchecked by default.
  
  Example: When requisition is approved and before PO is created, buyer can modify the lines. If this checkbox is checked, and the sum of the amount from the new lines doesn't equal the amount on the original line, the modified lines will be routed for reapproval based on the requisition approval rules.
- Enable Approver Override: This controls if the Overriding Approver field is displayed on the requisition creation flow.
Cost center manager based approvals can be set up using the following condition if all requisitions in your organization needs to be routed to the cost center manager for approvals:

If Cost Center Manager Is not Blank, route using Single User with User Type = Cost center manager

The cost center manager is set up on Manage Department page from the setup manager.
For autoapproval rules, transaction is approved using the internal APPID user (Application Development Framework Application) instead of the task creator (preparer).
Approval rule priority: Manage Requisitions Approval UI has been enhanced to support approval rule priority. Approvers from the higher priority rule will be notified before the approvers from the lower priority rule. The following values are supported priority: Highest, Higher, High, Medium, Low, Lower, Lowest. Medium is the default priority.

How rule is priority applied?
- The Approval Engine will determine the list of approvers based on the rules with conditions that evaluate to true for a transaction.
- The list of approvers will be arranged by priority, so the approver with the highest priority receives the notification first and so forth.
- Approvers from the rules having same priority will be notified in a random sequence.
To prevent self approval of transactions when the submitter (task creator) is part of an approval list, the following task configuration property should be set in BPM:

Skip creator for Approval List = Y When this option is set to Y and the requisition preparer/buyer is one of the approvers, the task will be routed to the next approver in the chain skipping the task assignment for the creator. For a single approver scenario, skipping task assignment for creator would mean the task outcome is set to reject unless there is another approver in the chain (or an auto approval rule) that approves the transaction. Alternatively, you can set the flag Assign to Creator's Manager = Y to replace the creator with his manager set in HCM.

Note: Task assignment for creator won't be skipped when using application role or position hierarchy based routing.