Copyright (c) 2024, Oracle. All rights reserved. Oracle Confidential.

How to Set Up Service Contracts Approval Using Oracle Approvals Management in R12 (Doc
ID 1456324.1)

In this Document

Goal
Solution
Part A - check the AME responsibilities and grants
Part B - set up the Service Contracts Internal Approval transaction type
References

APPLIES TO:

Oracle Service Contracts - Version 12.1.3 and later

Information in this document applies to any platform.

GOAL

In R12 the Service Contracts approval process requires Oracle Approvals Management (AME) to be set up. If the required
setup is not done, then the approval notification will not be sent and the contract will be stuck in 'Pending Internal
Approval' negotiation status. An error notification may be sent with the error below:

Details: A valid approver was not found for the contract

Please check AME setup.

ORA-20102: No rules are applicable to this transaction. At least one rule must apply to this transaction when the value
of the attribute AT_LEAST_ONE_RULE_MUST_APPLY is true. in Package OKS_WF_K_APPROVE Procedure select_next.

This note explains how to do the AME setup to define the approval rule for service contracts approval.

Note: for Repository Contracts approval setup see Doc ID 980703.1: How to Define Approval Rules for Repository
Contracts

SOLUTION

NOTE: In the images below, user details / company name / address / email / telephone number represent a fictitious
sample (based upon made up data used in the Oracle Demo Vision instance).
Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Part A - check the AME responsibilities and grants

The steps here will give access to AME Transaction Types which is a prerequisite to allow the required setup for the Service
Contracts Internal Approval transaction type to be done.

In AME.B the following two responsibilities are used for AME:

Approvals Management Business Analyst

Approvals Management Administrator

Assigning these responsibilities directly to a user will NOT work. From AME.B onwards RBAC (Role Based Access Control) is
used. So, for the responsibilities to work, AME roles should be assigned and data grant has to be provided to the users.
This is explained in detail below.
For the Existing users, the ‘Approvals management Post Upgrade Process’ concurrent process should be run and this will
attach the new responsibilities to the existing AME Users. Using the System Administrator Responsibility, the concurrent
program can be assigned to the System Administrator Reports Request Group.

See also 'HRMS Approvals Management (AME) Responsibilities and Setups in AME.B / Oracle Approvals Management Not
Enabled? What Does It Take To Enable It ?' (Doc ID 434567.1)

This section gives a step-by-step illustration of adding the two AME responsibilities to a new user.

1. Login as SYSADMIN user (or a user that has full User Management functionality – Review Note 378262.1 for the steps to
update an existing user to full user management capabilities).

2. Create a New user account and give an appropriate effective date. Do NOT add any Approval responsibility.

3. Save the record.

4. Switch the responsibility to User Management and Navigate to the Users function.

5. Query for the newly created user.

6. Click on the update action from the result table.

7. In the Update User page, click on the Assign Roles button

8. Change the “Search By” field from “Roles and Responsibilities” to “Roles”

9. In the search window, query for Approval%

10. Following five roles will be displayed.

11. Select only the “Approvals Management Administrator” and “Approvals Management Business Analyst” roles.
12. After selecting the Roles, provide the Justification for the role and the effective date.

13. After completing the action, you can query back the same user and verify the list of roles being attached to the user.

14. Now switch the responsibility to Functional Administrator.

15. Click on create grants under the grants sub-tab.

16. Enter a Grant Name and provide an effective date.

17. Navigate to the security Context region and select the Grantee Type as ‘Specific User’

18. In the Grantee field select the newly created User

19. In the Data Security region select ‘AME Transaction Types’ as the Object.
20. Clicking Next will take you to the ‘Select Object Data Context’ page’.

21. You have a default value of ‘All Rows’ in the Data Context Type, leave it as it is, and navigate further.

22. In the ‘Object parameter and Select Set’ page, enter ‘AME calling applications’ as the value in the Set field.

23. Clicking Next will take you to the Review page.

24. Verify the information and submit the transaction.

25. Now Switch the responsibility to System Adminstrator and Navigate to System Profiles.

26. Query for the profile ‘AME:Installed’ at the required level and set the value to ‘Yes’.

27. Save the data.

Now you can login as the newly created user.

29. You should be able to see the following responsibilities:

a. Approvals Management Administrator

b. Approvals Management Business Analyst

Part B - set up the Service Contracts Internal Approval transaction type

1. Navigate to The Business Analyst Dashboard using the Approvals Management Business Analyst responsibility.

2. The Approval Process Setup lov appears on the right-hand side of the page.

3. Enter, or select from the LOV, the transaction type 'Service Contracts Internal Approval', (Transaction Type Key =
OKS_INTERNAL_APPROVAL).

4. Beneath this entry is a section entitled '2. Define the components'. Select the link for 'Approver
Groups'.

Note: If the 'Service Contracts Internal Approval' transaction type cannot be found, see Note 1148943.1: Unable To
Find Transaction Type 'Service Contracts Internal Approval' In Approval Management Administrator Responsibility.
CREATE APPROVER GROUPS

1. Press the Create button.

2. Enter the following values:

Name = Desired Name

Description = Desired Description
Order Number = 1
Voting Method = Serial (in this example a single approver is designated).

3. Select the Add Another Row button in the 'Approver Type' section of the page.

4. Enter the following values:

Approver Type = HR People

Approver = Select desired entry from the list of values.

CREATE APPROVER CONDITIONS:

At this point the Setup: Approver Group page is open. There are four subtabs; Attributes, Conditions, Action Types and
Approver Groups.

1. Open the Conditions tab and then select the Regular subtab.

2. Press the Create button.

3. The Condition Type defaults to Ordinary. Click on the Attribute list of values.
Select an attribute and enter the corresponding condition

An example is provided.

Example : Attribute = CONTRACT_AMOUNT.

Expression: CONTRACT AMOUNT is greater than or equal to 9999

CREATE APPROVAL RULES

After the Conditions are saved, control should return to the main Setup page. This set of actions will define rules for the
workflow.

1. Select the Rules tab.

2. Press the Create button.

3. Enter these values:

Name = Desired Rule Name. Make the name easily identifiable.

Rule Type = List Creation
Item Class = Header
Start Date / End Date = Enter desired dates.

4. Press the Next Button.

5. Press the Add Condition button.

6. Select the Condition that you just created and then select the Continue button.

7. Press the Next Button.

8. The Action Type has a single entry in the pull-down list, approval-group chain of authority.

9. Select the Action from the list of values. The list consists of approval group name that was just created. Select the
approval group name you created.
10. Press the Next button.

11. Then press the Finish button to complete the creation of the Rule.

At this point the Transaction Type 'Service Contracts Internal Approval' should have at least one Rule.

The Rule(s) should have a condition that must be met to "fire" that rule.

Each Rule should have an Action, one that specifies the Contract Approver.

Complete these steps to complete the approval definition.

APPROVALS MANAGEMENT DEFINITION (SETUP CHANGE):

This step is necessary only if someone has disabled the AME, in which case the first notification is
one asking the user to Sign the contract.

1. Navigate to 'Transaction Types' using the Approvals Management Administrator responsibility.

(There is no menu entry, the page opens when the link for the responsibility is selected).
2. Use the Search Filter to fine Transaction Type = Service Contracts Internal Approval.

3. Press the Update icon.

The seeded definition appears.

4. Press the 'Next' button until page 3 of 4 is reached.

5. Set the value for AT_LEAST_ONE_RULE_MUST_APPLY to 'True'.

This will turn ON service contracts approval and will use the AME approval setup done in the previous sections to
determine how to handle the approval and who should receive the approval notification.

6. Press the Next button and then the Finish button to save the change.

REFERENCES
NOTE:980703.1 - How to Define Approval Rules for Repository Contracts
Didn't find what you are looking for?