Organization-Enabled LOV: Column specified by Owner Organization Specifier must be accessible to the BC (using a join if necessary)
Last updated on SEPTEMBER 17, 2016
Applies to:Siebel Sales - Version 220.127.116.11 SIA and later
Information in this document applies to any platform.
""Checked for relevance on 13-AUG-2014""
A custom BC was created based on S_OPTY_XM. One of the fields in this BC uses an Organization-enabled picklist.
To enable Organization LOV's, the originating business component needs to supply an Organization Id. For this purpose, the table property "Owner Organization Specifier" can be used to specify a column on the BC's table, or a column joined in from another table, that supplies the Organization ID. In the customer's scenario, this property was set to:
[PAR_ROW_ID] is a foreign key column pointing to S_OPTY, so this Owner Organization Specifier value would advise the system to pick the Organization ID from S_OPTY.BU_ID.
However, this setup did not work. For new records, the Organization ID was successfully retrieved from the current user's position; however, for existing records, where the Organization ID should get picked from S_OPTY.BU_ID, the system was unable to retrieve the Organization Id.
As a result, the picklist query filtered for "BU_ID IS NULL" which was not the desired behavior.
The session log file revealed an error message related to the Owner Organization Specifier:
EventContext EvtCtxApplet 4 000000024ffd1628:0 2012-07-11 11:52:28 <custom MVG applet> (GetQuickPickInfo)
ObjMgrBusCompLog Warning 2 000000024ffd1628:0 2012-07-11 11:52:28 Field "OrgSpecializedLOV.Internal_OwnerOrgSpecifierBU_ID" is not activated in BusComp "<custom MVG BusComp name>".
which indicated an issue with resolving the reference in Owner Organization Specifier.
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