Using JTF_RS_ROLE_RELATE_PUB API to Assign Roles to Resource always commits (Doc ID 420969.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

Oracle Incentive Compensation - Version 11.5.10.2 and later
Information in this document applies to any platform.

Symptoms

Using the Paygroup to Role Role API JTF_RS_ROLE_RELATE_PUB.create_resource_role_relate to convert over 70000 resources.  Even though the parameter for P_COMMIT is entered as FND_API.G_FALSE, the API commits the transaction. This will be a huge problem when running conversions, if they need to roll back a specific transaction.

The issue can be reproduced at will with the following steps:
1. Create the sql script.
2. In the script call the API JTF_RS_ROLE_RELATE_PUB.create_resource_role_relate.
3. Here's a snippet of the code that will be used to assign roles to resources:

jtf_rs_role_relate_pub.create_resource_role_relate(p_api_version => 1.0,
p_init_msg_list => FND_API.G_TRUE,
p_commit =>
FND_API.G_FALSE,
p_role_resource_type =>
'RS_INDIVIDUAL',
p_role_resource_id => x_resource_id,
p_role_id => 10082 -- MGI
AGENT 13
,
p_role_code => 'MT SEND FLAT
AMOUNT',
p_start_date_active => sysdate,
p_end_date_active => null,
x_return_status =>
x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
x_role_relate_id =>
x_role_relate_id);

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms