1. Implementing Procurement
  2. Configure Approval Rules for Purchasing Documents and Requisitions Using Mapping Sets

Configure Approval Rules for Purchasing Documents and Requisitions Using Mapping Sets

Use mapping sets to configure the approval authority matrix and route purchasing documents and requisitions for approval against the approval authority by creating a single approval rule. This significantly reduces the maintenance overhead associated with managing many rules.

For example, you can create a rule for conditions listed in this table.
Category Deliver-to Location Department Requisition Amount Range (USD) Approver
Miscellaneous Ashburn Neurology 100 1000 Terry Smith
Miscellaneous Bloomington Neurology 100 1000 Terry Smith
Medical Supplies Ashburn Neurology 1000 10000 Terry Smith
Medical Supplies Bloomington Neurology 1000 10000 Terry Smith
Medical Supplies Ashburn Cardiology 10000 100000 Terry Smith
Medical Supplies Bloomington Cardiology 10000 100000 Terry Smith
To model this requirement, you must perform these steps:
  1. Create PO_APPROVAL_MAPPING_SET_X and PO_APPROVAL_DATA_SET_X mapping sets for purchasing documents or create REQ_APPROVAL_MAPPING_SET_X and REQ_APPROVAL_DATA_SET_X mapping sets for requisitions.
  2. Create an approval rule using the appropriate mapped approval attribute X.

In the mapping sets you created, X is the number of mapping set approval configurations. You can't create more than 5 mapping set approval configurations.

The mapped approval attribute 1-5 are associate with a pair of mapping sets such that the approval configurations from the respective mapping sets are executed when the attribute is used in an approval rule.

Attributes Executes Approval Configuration from Mapping Sets with a Short Name
For Purchasing Documents For Requisitions
Mapped Approval Attribute 1 PO_APPROVAL_MAPPING_SET_1 and PO_APPROVAL_DATA_SET_1 REQ_APPROVAL_MAPPING_SET_1 and REQ_APPROVAL_DATA_SET_1
Mapped Approval Attribute 2 PO_APPROVAL_MAPPING_SET_2 and PO_APPROVAL_DATA_SET_2 REQ_APPROVAL_MAPPING_SET_2 and REQ_APPROVAL_DATA_SET_2
Mapped Approval Attribute 3 PO_APPROVAL_MAPPING_SET_3 and PO_APPROVAL_DATA_SET_3 REQ_APPROVAL_MAPPING_SET_3 and REQ_APPROVAL_DATA_SET_3
Mapped Approval Attribute 4 PO_APPROVAL_MAPPING_SET_4 and PO_APPROVAL_DATA_SET_4 REQ_APPROVAL_MAPPING_SET_4 and REQ_APPROVAL_DATA_SET_4
Mapped Approval Attribute 5 PO_APPROVAL_MAPPING_SET_5 and PO_APPROVAL_DATA_SET_5 REQ_APPROVAL_MAPPING_SET_5 and REQ_APPROVAL_DATA_SET_5
To configure an approval rule for requisitions using mapping sets, you must perform these steps:
  1. Create Mapping Sets
  2. Configure the Approval Rule

Create Mapping Sets

REQ_APPROVAL_MAPPING_SET_1

To define this mapping set, select 4 input sources from the list of available input sources.

  • PO Header Attribute 1: Indicates the sequence in which the attributes specified in this mapping will be mapped with the corresponding data values are specified in the REQ_APPROVAL_DATA_SET_X mapping set.
  • PO Header Attribute2: Indicates the attribute's technical alias name in the TableAlias.Column_Name format. You can use attributes only from these tables:
    Product Table Table Alias Example Attribute Name Approval Document
    Procurement POR_REQUISITION_HEADERS_ALL ReqHeader ReqHeader.REQUISIITON_TOTAL Requisitions
    Procurement POR_REQUISITION_LINES_ALL ReqLine ReqLine.CATEGORY_ID Requisitions
    Procurement POR_REQ_DISTRIBUTIONS_ALL ReqDist ReqDist.REWQ_BU_ID Requisitions
    Financials GL_CODE_COMBINATIONS ChargeAccount ChargeAccount.SEGMENT3 Requisitions
    Project Management PJF_PROJECT_PARTIES ProjectParty ProjectParty.PROJECT_ID Requisitions
    Procurement PO_HEADERS_ALL PoHeader PoHeader.PRC_BU_ID Purchasing Documents
    Procurement PO_LINES_ALL PoLine PoLine.CATEGORY_ID Purchasing Documents
    Procurement PO_LINE_LOCATIONS_ALL PoSchedule PoSchedule.SHIP_TO_LOCATION_ID Purchasing Documents
    Procurement PO_DISTRIBUTIONS_ALL PoDistribution PoDistribution.DELIVER_TO_LOCATION_ID Purchasing Documents
    Financials GL_CODE_COMBINATIONS ChargeAccount ChargAccount.SEGMENT1 Purchasing Documents
  • PO Header Attribute 3: Indicates if the attribute is an input or an output variable for rule evaluation.
  • PO Header Attribute 4: Indicates the operator used to validate the rule. Here's the list of supported operators.
    Data Type Operator Meaning
    String, Number = Equals
    <> Not equal
    Number, Date > Greater than
    >= Greater than and equal to
    < Less than
    <= Less than and equall to
For this example, these are the created mapping sets.
Input
PO Header Attribute 1 PO Header Attribute 2 PO Header Attribute 3 PO Header Attribute 4
1 ReqLine.CATEGORY_ID IN =
2 ReqLine. DELIVER_TO_LOCATION_ID IN =
3 ChargeAccount.SEGMENT2 IN =
4 ReqHeader. REQUISITION_TOTAL IN >=
5 ReqHeader. REQUISITION_TOTAL IN <=
6 PROJECT_ROLES OUT =

REQ_APPROVAL_DATA_SET_1

To define this mapping set, you must select the same number of input sources as the number of approval attributes you configured in the REQ_APPROVAL_MAPPING_SET_1 mapping set. In this case, you must select 6 input sources because the REQ_APPROVAL_MAPPING_SET_1 has 6 approval attributes. You can enter the attribute values in terms of an ID (unique identifier), alternatively, you can configure value sets to enter data using user-friendly values (business keys).

Here are the input sources for the mapping set.
Number Input Source Value Set
1 PO Header Attribute1 REQ_CATEGORY
2 PO Header Attribute2 REQ_DELIVER_TO_LOCATION
3 PO Header Attribute3 N/A
4 PO Header Attribute4 N/A
5 PO Header Attribute5 N/A
Here's the mapping set data.
Input
PO Header Attribute1 PO Header Attribute2 PO Header Attribute3 PO Header Attribute4 PO Header Attribute5 PO Header Attribute6
Medical Supplies Ashburn 120 10000 100000 Scott.Campbell
Medical Supplies Ashburn 720 1000 10000 Anne.Balmer
Medical Supplies Bloomington 120 10000 100000 Bob.Boyle
Medical Supplies Bloomington 720 1000 10000 Alister.Cook
Miscellaneous Ashburn 720 100 1000 Terry.Smith
When using PROJECT_ROLES as the output, you must specify the project role name in the REQ_APPROVAL_DATA_SET_1. The requisition is routed to all users assigned to the project role.
Input
PO Header Attribute1 PO Header Attribute2 PO Header Attribute3 PO Header Attribute4 PO Header Attribute5 PO Header Attribute6
Medical Supplies Ashburn 120 10000 100000 Project Manager
Medical Supplies Ashburn 720 1000 10000 Team Manager
Medical Supplies Bloomington 120 10000 100000 Project Participant
Medical Supplies Bloomington 720 1000 10000 Project Participant
Miscellaneous Ashburn 720 100 1000 Team Member

Configure the Approval Rule

After creating the mapping sets, configure an approval rule using the Mapped Approval Attribute 1 attribute.

Here's the rule setup scenario.

CONDITION
Requisitioning BU Equals Vision Operations
AND Mapped Approval Attribute 1 ls not blank
AND Functional Currency Code equals USD
ACTION
Action Type: Approval Required
Route Using: Single Approver
User Type: Mapped Approval Attribute 1

To use the Mapped Approval Attribute X in supervisory hierarchy and job-level routing, configure the approval rules using the Oracle BPM Worklist application. For instance, for a supervisory hierarchy approval for a requisition, use this BPM rule setup scenario:

THEN
List Builder: Supervisory
Response Type: Required
Number of levels: 3
Starting Participant: HierarchyBuilder.getManager("supervisory",ReqHeaderDimension.mappedApprovalAttribute1,-1,"","")
Top Participant: HierarchyBuilder.getPrincipal("CVRQST06",-1,"","")
Auto Action Enabled: False
Auto Action: null
Rule Name: "MappingSetRuleReferencingApprovers"