Setting Profile SLA: Alternate Application ID
(Doc ID 1365422.1)
Last updated on JUNE 23, 2017
Applies to:Oracle Assets - Version 12.1 and later
Information in this document applies to any platform.
Is it possible to set the profile SLA: Alternate Application ID at a responsibility level instead of at the application level?
Setting up at the application level may cause issues with other modules as the customer application covers multiple modules (AP, FA, AR, etc.)
From Forum Thread: SLA: Alternate Application ID for different applications same custom app
Customers are using custom responsibilities, which are attached to custom applications. They want to use SLA functionality for that responsibility / application similar to EBS application / subledger.
Let's say customer is having two responsibilities and applications.
1. Custom ABC resp for the application Custom ABC app.
2. Custom DEF resp for the application Custom DEF app.
And they want to treat Custom ABC app as EBS Payables and Custom DEF app as EBS Receivables.
They can set the profile 'SLA: Alternate Application ID' for Custom ABC app as 'Payables'. From then on, the responsibilities attached to that application Custom ABC app will work similar to Payables responsibilities.
The scope of this profile is defined in the <Note 833986.1>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Still Have Questions?|