Aol Document.pdf 1e3r36

Oracle Applications E-Business Suite

Application Object Library (AOL) AOL is a collection of pre-built application components and facilities and it consists of forms, subroutines, concurrent programs and reports, database tables and objects, messages, menus, responsibilities, flex filed definitions, various guides and library functions.

Objective:     

custom Application components. Understand the security authorization features of Oracle Applications. Run concurrent programs using Standard Report Submission. Design and implement Key and Descriptive Flex fields. Define and modify profile options.

Agenda:   

Setting Up Your Application. Flex fields. Profiles.

Setting Up Your Application:   

Oracle Applications and custom applications that integrate with Oracle Applications need to have a particular directory structure where its Components must be available. Those components are, 1. Forms 2. Menus 3. Programs 4. Reports.

Functions:  

A function is a part of an application functionality that is ed under a unique name for the purpose of asg /excluding it from a responsibility. Application developers functions when they develop forms.

Logical ERP Solutions


Menus:  

A menu is a hierarchical arrangement of application functions that is displayed in the navigator window. A menu consists of menu entries, which could be a submenu or a function.

  

Form functions are selected and navigated to using Navigator window. Each responsibility has a menu associated with it. Note the Menu name associated with a responsibility.



Menus (Contd.):



  

Query the menu name to find the menu entries. Add your functions as menu entries here or create a new menu with your functions and add that as a submenu here. Now you switch the responsibility and check whether your menu entry is appearing in corresponding responsibility.

List of Menus Excluded from a given Responsibility: SELECT FROM

WHERE

frv.responsibility_name ,fmv._menu_name fnd_resp_functions frf ,fnd_menus_vl fmv ,fnd_responsibility_vl frv frf.rule_type =‟M‟ AND frf.action_id = fmv.menu_id AND frf.responsibility_id = frv.responsibility_id AND frv.responsibility_name = „&resp_name‟;

List of Functions Excluded from a given responsibility: SELECT FROM

WHERE

frv.responsibility_name ,fffv._function_name fnd_resp_functions frf ,fnd_form_functions_vl fffv ,fnd_responsibility_vl frv frf.rule_type =‟F‟ AND frf.action_id = fffv.function_id AND frf.responsibility_id = frv.responsibility_id AND frv.responsibility_name = „&resp_name‟;

Concurrent Program Name, Responsibility Name and Name for a concurrent request id?

SELECT

FROM

WHERE

fcr.request_id ,frv.responsibility_name ,fv.concurrent_program_name PROG_SHORT_NAME ,fv._concurrent_program_name CON_PROG_NAME ,fu._name REQUESTED_BY fnd_concurrent_requests fcr ,fnd_concurrent_programs_vl fv ,fnd_ fu ,fnd_responsibility_vl frv fv.concurrent_program_id = fcr.concurrent_program_id AND fu._id = fcr.requested_by AND frv.responsibility_id = fcr.responsibility_id AND fcr.request_id = &req_id;



Concurrent Program:  



A concurrent program is an executable file that runs simultaneously with online operations and with other concurrent programs. We need a concurrent program for .. 1. Any long running data intensive program 2. Operating system script 3. Oracle Reports The various steps to define and a concurrent program are. 4. Define concurrent program executable 5. Define concurrent program 6. Include the concurrent program in a request group 7. Run concurrent program through submit request form.

Concurrent Program Executable:

     1. 2. 3. 4. 5. 6. 7. 8.

Enter a name for executable and short name. Choose the application to which this executable belongs such that the system will Look for this file in that directory structure. Enter the execution method as Flex Rpt The execution file is written using the Flex Report API. Flex Sql The execution file is written using the Flex Sql API. Host The execution file is a host script. Oracle Reports The execution file is an Oracle Reports file. PL/SQL Stored Procedure The execution file is a stored procedure. SQL*Loader the execution file is a SQL script. SQL*Plus the execution file is a SQL*Plus script. SQL*Report the execution file is a SQL*Report script.



9. Spawned The execution file is a C or Pro*C program. 10. Immediate The execution file is a program written to run as a subroutine of the concurrent manager.  Enter the execution file name without the file extension.  For PL/SQL stored procedures enter the <package>.<procedure name> in the execution file name. This procedure must have 2 out parameters of type varchar2 preferably with names errbuf and errout. These two parameters should be added before adding any other parameters.

Concurrent Program:  

Define a concurrent program, Choose an executable created, which will be executed once this concurrent program is scheduled to run.

Define Concurrent Parameters:  

The parameters are the placeholders for the input values to a concurrent program. If the execution method of a concurrent program is Oracle Reports then each parameter is linked to the actual report parameter via the “Token” field in the parameters window  For PL/SQL stored procedures these parameters are ed to the program by position. Output formats of a concurrent program: Logical ERP Solutions


    

HTML. PDF. TEXT. PS (Post Script). PCL (HP‟s Printer Control Language).

Define Request Group: 

Note the Request group name for the responsibility, with which you want to attach the concurrent program.



Define Request Group (Contd.):   

Query the request group and add your concurrent program to the group. A request group is a collection of reports and concurrent programs. A system defines request group in order to control access to reports and concurrent programs.

Concurrent Programs Assigned to a Request Group: SELECT

FROM

WHERE

fv.concurrent_program_name SHORT_NAME ,fv._concurrent_program_name CONC_PROG_NAME ,frg.request_group_name REQ_GROUP_NAME fnd_concurrent_programs_vl fv ,fnd_request_groups frg ,fnd_request_group_units frgu fv.concurrent_program_id = frgu.request_unit_id AND fv.enabled_flag = „Y‟ AND frgu.request_group_id = frg.request_group_id AND frg.request_group_name = „&request_group_name‟;

Check if the concurrent program is assigned to a given responsibility: SELECT

FROM

fv.concurrent_program_name SHORT_NAME ,fv._concurrent_program_name CONC_PROG_NAME ,frg.request_group_name REQ_GROUP_NAME ,frv.responsibility_name fnd_concurrent_programs_vl fv ,fnd_request_groups frg



WHERE

,fnd_request_group_units frgu ,fnd_responsibility_vl frv fv.concurrent_program_id = frgu.request_unit_id AND fv.enabled_flag = „Y‟ AND frgu.request_group_id = frg.request_group_id AND frg.request_group_id = frv.request_group_id AND frv.responsibility_name = „&resp_name‟ AND fv._concurrent_program_name = „&con_prg_name‟;

SRS Form:   

Then use SRS (Standard Report Submission) form for running and monitoring your application‟s reports/concurrent programs at specific time interval. This lets specify run and print options and parameter value for reports and concurrent programs. Use fnd_file.put_line(fnd_file.log, „any message‟) to show message in conc program log file.

A concurrent request proceeds through three, possibly four, life cycle stages or phases:  Pending Request is waiting to be run  Running Request is running  Completed Request has finished  Inactive Request cannot be run. Concurrent Programs Business Events:



In R12 for concurrent programs submission and completion has business events associated with them in the concurrent program definition form there is a business events tab which displays the list of events associated here you specify the points at which business events are enabled. The possible points are: Request Submitted Request On Hold Request Resumed Request Running Program Completed Post Processing Started Post Processing Ended Request Completed. But make sure you set the profile "Concurrent: Business Intelligence Integration Enable". You will need to set "Yes" to enable Business Events from Concurrent Processing System Within each phase, a request‟s condition or status may change. Below appears a listing of each phase and the various states that a concurrent request can go through. Concurrent Request Phase and Status: Phase: PENDING:  Normal: Request is waiting for the next available manager.  Standby: Program to run request is incompatible with other program(s) currently running.  Scheduled: Request is scheduled to start at a future time or date.  Waiting: A child request is waiting for its Parent request to mark it ready to run. Phase: RUNNING:  Normal: Request is running normally.  Paused: Parent request pauses for all its child requests to complete.  Resuming: All requests submitted by the same parent request have completed running. The Parent request is waiting to be restarted.  Terminating: Running request is terminated, by selecting Terminate in the Status field of the Request Details zone. Phase: COMPLETED:  Normal: Request completes normally.  Error: Request failed to complete successfully.  Warning: Request completes with warnings. For example, a report is generated successfully but fails to print.  Cancelled: Pending or Inactive request is cancelled, by selecting Cancel in the Status field of the Request Details zone.  Terminated: Running request is terminated, by selecting Terminate in the Status field of the Request Details zone. Phase: INACTIVE:  Disabled: Program to run request is not enabled. your system .  On Hold: Pending request is placed on hold, by selecting Hold in the Status field of the Request Details zone. Logical ERP Solutions

Oracle Applications E-Business Suite 

No Manager: No manager is defined to run the request. Check with your system .

Request Set:     

Request Sets are a method of grouping multiple reports and/or concurrent programs by business function with common run and print options. The various tasks of the request set are linked together to determine the execution order, whether the tasks execute sequentially or in parallel. Stage is a component of a request set used to group requests within the set. All requests in a stage are run in parallel, while stages themselves are run sequentially in the set. Tasks that must operate separately are created in different stages. After defining the initial stage for execution, all subsequent stages are defined under the three completion status codes for the previous stage.

Useful FND Queries: 1. Concurrent Program Info SELECT ft._concurrent_program_name Concurrent_Program ,fdfcu.column_seq_num Sequence_number ,fdfcu.DEFAULT_VALUE default_value ,fdfcut.form_left_prompt prompt ,fdfcut.description description ,ffvs.flex_value_set_name ,fl.meaning ,fe.executable_name FROM apps.fnd_concurrent_programs f ,apps.fnd_concurrent_programs_tl ft ,apps.fnd_concurrent_programs_tl fd ,apps.fnd_descr_flex_col_usage_tl fdfcut ,apps.fnd_descr_flex_column_usages fdfcu ,apps.fnd_descr_flex_col_usage_tl fdfcud ,apps.fnd_application fa , apps.fnd_flex_value_sets ffvs , apps.fnd_lookups fl , apps.fnd_executables fe WHERE ft._concurrent_program_name='Payables Open Interface Import' AND f.concurrent_program_id = ft.concurrent_program_id AND ft.concurrent_program_id = fd.concurrent_program_id AND fdfcut.application_id = fa.application_id AND fdfcut.descriptive_flex_context_code = 'Global Data Elements' AND fdfcut.descriptive_flexfield_name = '$SRS$.'||f.concurrent_program_name AND fdfcut.application_id = fdfcu.application_id AND fdfcut.descriptive_flex_context_code = fdfcu.descriptive_flex_context_code AND fdfcut.descriptive_flexfield_name = fdfcu.descriptive_flexfield_name AND fdfcut.application_column_name = fdfcu.application_column_name Logical ERP Solutions


AND fdfcut.application_id = fdfcud.application_id AND fdfcut.descriptive_flex_context_code = fdfcud.descriptive_flex_context_code AND fdfcut.descriptive_flexfield_name = fdfcud.descriptive_flexfield_name AND fdfcut.application_column_name = fdfcud.application_column_name AND fdfcu.flex_value_set_id = ffvs.flex_value_set_id AND f.EXECUTION_METHOD_CODE = fl.lookup_code AND fl.lookup_type = '_EXECUTION_METHOD_CODE' AND f.executable_id = fe.executable_id ORDER BY 1, 2 ,3

SELECT t._CONCURRENT_PROGRAM_NAME, t.DESCRIPTION, .CONCURRENT_PROGRAM_NAME, a.APPLICATION_SHORT_NAME, e.EXECUTABLE_NAME, .CREATION_DATE, uc._NAME CREATOR, .LAST_UPDATE_DATE, ulu._NAME UPDATER, .ENABLED_FLAG, .RUN_ALONE_FLAG, .SRS_FLAG, .PRINT_FLAG, .SAVE_OUTPUT_FLAG, .REQUIRED_STYLE, .OUTPUT_PRINT_STYLE, .PRINTER_NAME, .MINIMUM_WIDTH, .MINIMUM_LENGTH, .OUTPUT_FILE_TYPE, .ENABLE_TRACE, .RESTART, .NLS_COMPLIANT, .REQUEST_SET_FLAG FROM applsys.fnd_concurrent_programs , applsys.fnd_concurrent_programs_tl t, applsys.fnd_application a, applsys.fnd_executables e, applsys.fnd_ uc, applsys.fnd_ ulu WHERE .CREATION_DATE > to_date('17-MAY-1995')-- Enter Creation Date AND .APPLICATION_ID = t.APPLICATION_ID Logical ERP Solutions


AND .CONCURRENT_PROGRAM_ID = t.CONCURRENT_PROGRAM_ID AND t.LANGUAGE = sys_context('ENV', 'LANG') AND .APPLICATION_ID = a.APPLICATION_ID AND .EXECUTABLE_APPLICATION_ID = e.APPLICATION_ID AND .EXECUTABLE_ID = e.EXECUTABLE_ID AND .CREATED_BY = uc._ID AND .LAST_UPDATED_BY = ulu._ID AND t._concurrent_program_name='Payables Open Interface Import' order by .CONCURRENT_PROGRAM_NAME

2. Concurrent Program parameters SELECT

.CONCURRENT_PROGRAM_NAME, cu.*, vs.FLEX_VALUE_SET_NAME FROM applsys.fnd_concurrent_programs , applsys.fnd_descr_flex_column_usages cu, applsys.fnd_flex_value_sets vs WHERE .CREATION_DATE > to_date('17-MAY-1995') --Enter Creation Date AND cu.application_id = .application_id AND cu.descriptive_flexfield_name = '$SRS$.' || .concurrent_program_name AND cu.FLEX_VALUE_SET_ID = vs.FLEX_VALUE_SET_ID AND .CONCURRENT_PROGRAM_ID=:CONCURRENT_PROGRAM_ID -(Enter CONCURRENT_PROGRAM_ID of CONCURRENT_PROGRAM) order by .CONCURRENT_PROGRAM_NAME, cu.COLUMN_SEQ_NUM 3. Concurrent Request Details SELECT

FROM

WHERE AND AND AND AND AND AND AND

p.concurrent_program_name, pt._concurrent_program_name, rt.responsibility_name, r.* applsys.fnd_concurrent_requests r, applsys.fnd_concurrent_programs p, applsys.fnd_concurrent_programs_tl pt, applsys.fnd_responsibility rsp, applsys.fnd_responsibility_tl rt r.request_id = &Request_ID -- Enter Request ID r.program_application_id = p.application_id r.concurrent_program_id = p.concurrent_program_id p.application_id = pt.application_id p.concurrent_program_id = pt.concurrent_program_id pt.language = sys_context('ENV', 'LANG') r.responsibility_application_id = rsp.application_id r.responsibility_id = rsp.responsibility_id



AND rsp.application_id = rt.application_id AND rsp.responsibility_id = rt.responsibility_id AND rt.language = sys_context('ENV', 'LANG') 4. Request Group Details SELECT

FROM

WHERE AND AND AND AND AND AND AND AND AND AND AND

rga.application_short_name "Req Grp App", rg.request_group_name "Request Group Name", rg.request_group_code "Request Group Code", rg.description "Request Group Desc", .concurrent_program_name "Concurrent Program", ea.application_short_name "Exec App", e.executable_name "Executable", rga.application_id "Req Grp App ID", rg.request_group_id "Req Grp ID", e.application_id "Exec App ID" applsys.fnd_executables e, applsys.fnd_concurrent_programs , applsys.fnd_request_group_units rgu, applsys.fnd_request_groups rg, applsys.fnd_application rga, applsys.fnd_application ea e.application_id like '%' -- Enter Application ID e.executable_name like '%' -- Enter Executable Name .executable_application_id = e.application_id .executable_id = e.executable_id .enabled_flag = 'Y' rgu.request_unit_id = .concurrent_program_id rgu.unit_application_id = .application_id rgu.request_unit_type = 'P' rg.application_id = rgu.application_id rg.request_group_id = rgu.request_group_id rga.application_id = rgu.application_id ea.application_id = e.application_id

5. Request Set Details SELECT

rst._REQUEST_SET_NAME, rs.REQUEST_SET_NAME, rsst_start._STAGE_NAME start_stage, rss.DISPLAY_SEQUENCE stage_sequence, rss.STAGE_NAME, rss.REQUEST_SET_STAGE_ID, rss.SUCCESS_LINK, rss.WARNING_LINK, rss.ERROR_LINK,



rsst._STAGE_NAME, rsst.DESCRIPTION stage_description, rsp.sequence program_sequence, ._concurrent_program_name, pa.* FROM applsys.fnd_request_sets_tl rst, applsys.fnd_request_sets rs, applsys.fnd_request_set_stages_tl rsst_start, applsys.fnd_request_set_stages rss, applsys.fnd_request_set_stages_tl rsst, applsys.fnd_request_set_programs rsp, applsys.fnd_concurrent_programs_tl , applsys.fnd_request_set_program_args pa where rs.REQUEST_SET_NAME like '%' -- Enter Request Set Name AND rs.application_id = rst.application_id AND rs.REQUEST_SET_ID = rst.REQUEST_SET_ID AND rst.language = sys_context('ENV', 'LANG') AND rsst_start.SET_APPLICATION_ID = rs.application_id AND rsst_start.REQUEST_SET_ID = rs.REQUEST_SET_ID AND rsst_start.REQUEST_SET_STAGE_ID = rs.START_STAGE AND rsst_start.language = 'US' AND rss.SET_APPLICATION_ID = rs.application_id AND rss.REQUEST_SET_ID = rs.REQUEST_SET_ID AND rsst.SET_APPLICATION_ID = rss.SET_APPLICATION_ID AND rsst.REQUEST_SET_ID = rss.REQUEST_SET_ID AND rsst.REQUEST_SET_STAGE_ID = rss.REQUEST_SET_STAGE_ID AND rsst.language = 'US' AND rsp.SET_APPLICATION_ID = rss.SET_APPLICATION_ID AND rsp.REQUEST_SET_ID = rss.REQUEST_SET_ID AND rsp.REQUEST_SET_STAGE_ID = rss.REQUEST_SET_STAGE_ID AND rsp.program_application_id = .application_id AND rsp.concurrent_program_id = .concurrent_program_id AND .language = 'US' AND pa.application_id (+) = rsp.SET_APPLICATION_ID AND pa.REQUEST_SET_ID (+) = rsp.REQUEST_SET_ID AND pa.REQUEST_SET_PROGRAM_ID (+) = rsp.REQUEST_SET_PROGRAM_ID ORDER BY rst._REQUEST_SET_NAME, rss.DISPLAY_SEQUENCE, rsp.sequence, pa.DESCRIPTIVE_FLEX_APPL_ID, pa.DESCRIPTIVE_FLEXFIELD_NAME, pa.APPLICATION_COLUMN_NAME



1.Find Locks Info SELECT sid, id1, id2, lmode, request, block FROM v$lock WHERE sid = &sid 2.Find Session Info SELECT module, action, sid, serial# FROM v$session WHERE action like '%%' 3.Find Lock Mode SELECT a.sid, b.name, a.id1, a.lmode, a.request FROM v$lock a, sys.obj$ b WHERE b.obj# = a.id1 4.Find Locked Objects SELECT oracle_name, os__name, session_id, process, locked_mode, o.owner, o.object_type, o.object_name FROM v$locked_object l, sys.dba_objects o WHERE l.object_id = o.object_id order by o.owner, o.object_name, session_id 5.Control File Query SELECT * FROM v$controlfile 6.Folder Info Query SELECT b.application_short_name, d.responsibility_name, a.OBJECT, c.NAME Folder_Name FROM apps.fnd_default_folders a, apps.fnd_application b, apps.fnd_folders c, apps.fnd_responsibility_vl d WHERE a.application_id = b.application_id AND a.folder_id = c.folder_id AND d.responsibility_id = - (a._id) AND d.responsibility_name LIKE '%%' ORDER BY b.application_short_name, d.responsibility_name; Logical ERP Solutions


Define Request Set:

ing Custom Application:      

your custom application with the Application Object Library. Switch to System responsibility and open „Applications‟ form. a custom application with name, short name and Base path. In UNIX, create a custom directory tree for your custom schema under APPL_TOP. First create a directory XXCUS which will serve as the base path then create other subdirectories as.. Modify the applications environment file to include the custom schema base path as XXCUS_TOP="/u02/oracle/visappl/XXCUS" export XXCUS_TOP.



ing Custom Schema: 

First create a in the database using SQL*Plus under the system . o For example:  $ sqlplus system/system .  SQL> create XXCUS identified by CUST default table space _DATA temporary table space TEMP quota unlimited on _DATA quota unlimited on TEMP;  SQL> grant connect to XXCUS identified by CUST;  Then the with the Application Object Library. to Oracle Apps as the System and navigate to Security -> ORACLE -> .



Add custom schema to data group:     

to Applications as the System and navigate to Security -> ORACLE-> Data Group. It is recommend that you use the STANDARD data group and associate the custom schema with APPS. Now you can create your custom tables, indexes and sequences in custom schema. Then Grant ALL access to APPS. Create Synonyms, views, triggers and Packages in APPS schema.

Responsibility:    

A responsibility is a set of authority in Oracle Applications that lets s access only that functionality of the application appropriate to their role. How much of an application‟s functionality a can use What reports and concurrent program a can access Which application data these reports and concurrent programs can access.



Create s and assign Responsibilities:    

Switch to System responsibility Navigate to Security-->-->Define Add or query a . Add responsibility to as required.

Key Flex fields: 

  

Most businesses use codes made up of meaningful segments to identify Number, Part number and other business entities, eg: a company might have a part number ”PAD–NR–YEL–8 1/2x14” indicating a notepad, narrow–ruled, yellow, and 14” by 8 1/2”. A Flex field is a field which is made up of segments. Each segment has a name and a set of valid values. A Key flex field identifies an entity.



Key Flex fields: 

your key flex field with Oracle Application Object Library.  Each key flex field has one corresponding table, known as the combinations table, where the flex field stores a list of the complete codes, with one column for each segment of the code.  There is a corresponding unique ID number (a code combination ID number or CCID) for that code which is also stored in the combination table.  A flex field structure is a specific configuration of segments. Same flex field can have multiple segment structure.

Customize Key Flex field Segments:    

A segment is a single sub–field within a flex field. You define the appearance and meaning of individual segments when customizing a flex field. A segment is represented in your database as a single table column. Flex field validates each segment against a set of valid values, which are mostly predefined A flex field qualifier identifies a particular segment of a key flex field.



Key Flex field Feature:  

Dynamic Insertion: The insertion of a new valid combination into a combinations table from a form other than the combinations form.

Key Flex field Cross validation: Cross–Validation:  Cross–validation rules prevent s from creating new key flex field combinations that contain values that should not coexist in the same combination.



Descriptive Flex fields:     

Descriptive flex fields provide customizable "expansion space" on your forms. You can use descriptive flex fields to have additional information, important and unique to your business that would not otherwise be captured by the form. A descriptive flex field appears on a form as a single-character, unnamed field enclosed in brackets. Descriptive flex fields have two different types of segments, global and context-sensitive. A global segment is a segment that always appears in the descriptive flex field pop-up window. A context-sensitive segment is a segment that may or may not appear depending upon what other information is present in your form.

Global Segments:   

In Order management, if you want to add some extra Order line information, then query the DFF for “Additional Line Attribute information” Go to Global Data Elements context field. Click segments to view the DFF segments.



Global Segments (Contd.):   

Already used segments for the DFF will appear here You can create a new record and use a previously unused attribute and make it enabled and displayed Save and compile the flex field definition.

   

Navigate to Order Management, Enter orders screen. Enter or query an order and go to line DFF You can see the additional information you enabled now The DFF data gets stored in attribute columns of the base table.

Context sensitive Segments:     

A context-sensitive descriptive flex field can gather context information from either a field on the form, or from a special field (a context field) inside the descriptive flex field pop-up window. If the descriptive flex field derives the context information from a form field, that field is called a reference field for the descriptive flex field. In DFF Segments form check Displayed for the context. Optionally change the prompt of context Choose the reference field from LOV, which should be initially defined in DFF form.



 

The reference field is same as a normal form field. Reference fields provide a way to map the context-sensitivity of descriptive flex field information that has been captured to existing conditions in your business data.

   

Descriptive flex field segments... Multiple Structure Reference field Structure Column



 

If you use a reference field, the value of that field populates its own column. For example, if the reference field on the form is the "Country" field, it populates the "country" column in the table. However, the reference field value also populates the structure (context) column in the table, since that value specifies which structure the flex field displays.



Benefits of Flex fields: 

Flex fields provides features that are required to satisfy the following business needs: 1. Customize your applications to conform to your current business practice for ing codes, product codes, and other codes. 2. Customize your applications to capture data that would not otherwise be tracked by your application. 3. Have “intelligent fields” that are fields comprised of one or more segments, where each segment has both a value and a meaning. 4. Rely upon your application to validate the values and the combination of values that you enter in intelligent fields (Cross Validation Rules). 5. Have the structure of an intelligent field change depending on data in your form or application data. 6. Customize data fields to your meet your business needs without programming. 7. Query intelligent fields for very specific information.

Value Sets:  Use value set to:  

Determine which values s can enter into flex field segments and concurrent program parameters. Provide a list of valid values using list of values feature

 Validation Type for Value Set:    

None (not validated at all) Table Independent Dependent

Table validated Value Sets:     

Create a validation table in your database your table with Oracle Application Object Library (as a table) Create the necessary grants and synonyms Define a value set that uses your validation table Define your flex field structure to use that value set for a segment.



      

Create a value set with a name, format type and length. Specify validation type as Table and click on details button Enter the Application name (optional), table name. Enter the column names which you want to display as value and meaning (optional) Enter the column name which need to be stored in the database in ID field Mention the data type of these columns Enter where and order by clause as appropriate.

Independent/Dependent Value Sets: • • • •

Create your independent value set first Create your dependent value set, specifying a default value Define your independent values Define your dependent values.



Validation Type for Value Set… 

Dependent

Relationship between Value Sets:



This Query gives details of value sets that are based on a oracle application tables:

Profiles: Profile:  





A profile is a set of changeable options that affects the way your application runs System Profile Options 1. Set by the System 2. cannot change 3. Any change in the system profile becomes effective only when the logs on again or change responsibility Personal Profile Options 1. Set by the System 2. can change the option values 3. Any changes become effective immediately You need to create a profile in Application Developer responsibility and then assign its system and personal values.



Profile Forms:

  

Define new profile option at the time of developing a new application Profile names must be unique A profile option cannot be deleted.



Setting Profile Values: Setting System Profile Values • Navigate to Sys  Profiles

Setting Personal Profile Values: •

Click on Menu Edit -> Preferences -> Profile.



Profile:  Profile Levels  A value set at the higher level overrides the one set at the lower level. “” is the highest level.  After implementation System sets the default profile values at the site level  Option values are dynamically set at the run time.

Profile Routines:  • • 

Profile routines that helps in retrieving option values are, FND_PROFILE.GET (name IN varchar2, value OUT varchar2) is a procedure. FND_PROFILE.VALUE (name IN varchar2) return varchar2 is a function. Syntax of referring a profile option value in value sets or concurrent program parameters is :$PROFILES$.option_name  Seeded profiles are – NAME – _ID – RESP_ID


Aol Document.pdf 1e3r36

Overview 26281t

More details 6y5l6z

Related Documents 3h463d

Aol 3w4x11

Aol Document.pdf 1e3r36

Aol 1413 15iv

Aol 10k 2h5hy

Aol 9.1 Manual 40183p

Aol Time Warner Merger 2uz3x