A Forum for Oracle E-business suite, Fusion professionals. It is an effort to make my blog a Knowledge repository and Solution Center which provides unique technical and functional solutions for EBS professionals.
Thursday, December 19, 2013
FND_MESSAGE Displaying only message code and not message text
--Application: The short name of the application this message is associated with. This short name references the application
--you associate with your message when
--you define it using the Messages form.
--
--Name: The message name that identifies your message. This name is identical to the name you use when you define your message
--using the Messages form. Message Dictionary names are not case sensitive (for example, MESSAGE_NAME is the same name as message_name).
--
--Procedure FND_MESSAGE.SET_NAME(application IN varchar2,
-- name IN varchar2);
DECLARE
l_message VARCHAR2 (4000);
BEGIN
FND_MESSAGE.SET_NAME ('XXTST', 'XX_TEST_MSG_NAME');
l_message := FND_MESSAGE.GET; DBMS_OUTPUT.put_line(l_message);
END;
--Note:-IF FND_MESSAGE.GET displays only the message code whatever
--is passed in the 2nd parameter and not message text, then, it
--means either the "Application Short Name" or the "Message Name" is
--incorrect
--Also, make sure the "Generate Messages" Concurrent Program is run
--from "Application Developer" responsibility
SELECT Statement to retrieve Oracle AOL Descriptive Flexfield Segment(DFF) Details
SELECT Statement to retrieve Oracle AOL Descriptive Flexfield Segment(DFF) Details
-- Application Developer > Navigate > Flexfields > Descriptive > Segments-- Search for relevant Title, second half of the screen, under "Context Field Values"
-- lists the main parts of the Flexfield
-- Click into a name on the "Context Field Values" section in the lower part of the
-- screen, and click "Segments"
-- This lists the bits users see in Core Applications when they click into the DFF
-- plus shows if there is a LOV linked to the field
-- Following SELECT statement retrieves DFF details related to an application,DFF
-- title, DFF Context or
-- the entire application if no parameter is passed
-- Optional Parameters:-
-- P_TITLE -- DFF Title
-- P_APPLICATION -- Application Name
-- P_DESC_FLEX_CD, DFF Context
SELECT fat.application_name
, fdfv.title
, fdfcv.descriptive_flex_context_code context
, fdfcuv.column_seq_num num
, fdfcuv.end_user_column_name name
, fdfcuv.application_column_name column_
, ffvs.flex_value_set_name value_set
, ffvs.description value_set_description
, fdfcuv.required_flag
, fdfcuv.display_flag
, fdfcuv.enabled_flag
, fdfcuv.security_enabled_flag
, fdfcuv.default_value
FROM apps.fnd_descriptive_flexs_vl fdfv
, applsys.fnd_application_tl fat
, apps.fnd_descr_flex_contexts_vl fdfcv
, apps.fnd_descr_flex_col_usage_vl fdfcuv
, applsys.fnd_flex_value_sets ffvs
WHERE fdfv.application_id = fat.application_id
AND fdfcv.descriptive_flexfield_name = fdfv.descriptive_flexfield_name
AND fdfcv.descriptive_flexfield_name = fdfcuv.descriptive_flexfield_name
AND fdfcv.descriptive_flex_context_code =
fdfcuv.descriptive_flex_context_code
AND fdfcuv.flex_value_set_id = ffvs.flex_value_set_id(+)
AND fdfv.title = NVL(:P_TITLE,fdfv.title)
AND fat.application_name = NVL(:P_APPLICATION,fat.application_name)
AND fdfcv.descriptive_flex_context_code =
NVL(:P_DESC_FLEX_CD,fdfcv.descriptive_flex_context_code)
ORDER BY fat.application_name
, fdfv.title
, fdfcv.descriptive_flex_context_code
, fdfcuv.column_seq_num;
Tuesday, December 10, 2013
How to enable the MOAC parameter “Operating Unit” for a Concurrent Program in Oracle EBS R12
You can notice that the new field “Operating Unit” which
is new field in R12 and by default is in disabled mode:-
With the introduction of multi-org access control in release
12, an applications responsibility
can access multiple operating units. Some concurrent programs have been enhanced to process multiple operating units simultaneously, while for other requests the operating unit must be specified when you run the program.
can access multiple operating units. Some concurrent programs have been enhanced to process multiple operating units simultaneously, while for other requests the operating unit must be specified when you run the program.
To support this, concurrent programs are defined with an
operating unit mode of 'S' for single operating unit or 'M'(concurrent program
will be in this mode by default) for multiple operating units. If the
'Operating Unit Mode' is not set for the concurrent program it will fail.
The “Operating Unit” field/parameter is known as “Reporting
Context” in MOAC(Multi Org Access Control) terminology.
For a concurrent program though there may be a need to only
run for Single Operating Unit, though the Responsibility has access to Multiple
Operating Units’ data based on the “MO: Security Profile” profile option.
Running a particular concurrent program for only a Single
Operating Unit can be achieved by a simple update statement or from the
front-end application:-
--Execute
the following update statement in the database for the particular concurrent
program you want set to run for "Single Operating Unit"
UPDATE fnd_concurrent_programs
SET
multi_org_category = 'S'
WHERE concurrent_program_name =
'<your program
name>';
Now we will see how we can achieve from the Oracle Applications
front-end.
1. Login into application with System
Administration responsibility (NOT System
Administrator)
2. Navigate: Concurrent -> Programs
Administrator)
2. Navigate: Concurrent -> Programs
3. Query for
short name of the concurrent program
4. Click on
Update pencil icon of your program
5. Under 'Update Concurrent Program' region, select Request
tab
6. Under 'Request Setting' region, select 'Single' from the drop down of 'Operating Unit
Mode' field
7. Save changes by clicking on 'Apply' button
6. Under 'Request Setting' region, select 'Single' from the drop down of 'Operating Unit
Mode' field
7. Save changes by clicking on 'Apply' button
8. Change
responsibility to the responsibility where the “Concurrent Program” can be run,
in
this example
“TESTOU” is assigned to “AR Super User” responsibility
9. Select the “Concurrent Program” from the “SRS Window”, now
you can see that “Operating
Unit” field is enabled and you can see the
Operating Units in the LOV
10. This particular selected Operating Unit value can be
accessed using the standard MOAC API: MO_GLOBAL.get_current_org_id
Note:- The return value for the “Operating Unit” reporting
context is corresponding “ORG_ID” for the selected “Operating Unit Name”
Subscribe to:
Posts (Atom)