Find Concurrent Programs Incompatible with a program

Use the below query to find out all the incompatible programs with the program in question :-


 SELECT fat.APPLICATION_NAME,
         fctl.user_concurrent_program_name,
         DECODE (TO_RUN_TYPE, 'S', 'Set', 'Program') TYPE,
         DECODE (INCOMPATIBILITY_TYPE, 'G', 'Global', 'Domain')
            "Incompatibilty Type"
            FROM FND_CONCURRENT_PROGRAM_SERIAL fcrs,
         FND_CONCURRENT_PROGRAMS_TL fctl,
         FND_APPLICATION_TL fat
   WHERE     fcrs.RUNNING_APPLICATION_ID = fat.application_id
         AND (RUNNING_CONCURRENT_PROGRAM_ID = :p_cp_id) -- CP id of the program in question
         AND fctl.CONCURRENT_PROGRAM_ID = fcrs.TO_RUN_CONCURRENT_PROGRAM_ID
         AND fctl.LANGUAGE = 'US'
         AND fat.LANGUAGE = 'US'
ORDER BY to_run_application_id, to_run_concurrent_program_id;

Spawn Multiple Autoinvoice Import Programs with Single Autoinvoice Master Program

If you want to spawn multiple autoinvoice import programs with only one Autoinvoice Master program then You need to setup the below profile.Spawn Multiple Autoinvoice Import Programs with Single Autoinvoice Master Program.


Profile name :- AR:Maximum lines per AutoInvoice worker

The value for this profile will be maximum number of lines will be processed by single import program. If the number goes beyond the profile value then new child request(Import) will be fired.

i.e.

No of lines in interface table :-  1000
Value setup for the Profile    :-    100

In the above case 10 Autoinvoice Import program will be triggered.

each will process 100 records from interface table.

MVC Architecture

The architecture of the portal UI is based on the Model-View-Control (MVC) design pattern. The MVC paradigm allows you to separate the code that handles business logic from the code that controls presentation and event handling. Each page in the portal is made up of a combination of at least one Model and View, and one or more Controls.

• Model classes store the data for a page or page section. A single page might use one or more Model classes, depending on how much of the page data can be shared by other types of pages. A Model defines how data is accessed and set for a given page, including any functions necessary for security or data validation and modification. Models encapsulate calls to the portal server API and also store UI-specific data. Data that is globally accessed by the UI is available from the ActivitySpace object (discussed on the next page). All other data should be stored in a Model.

• View classes contain HTMLElements and HTMLConstructs that describe how the data from the Model should be displayed to the user. In the portal UI design, DisplayPage objects are used to aggregate View objects to encapsulate all the information needed to render a particular page. Some Views are common throughout the portal and some are specific to certain pages. For example, the banner that makes up the majority of the portal is a common View that defines the color scheme and where the search section will be displayed. In contrast, the View used to create and modify data within a User Profile is specific to the User Profile function and is seen only on that page.

• Control are actions or sets of actions that are executed when a specific event is triggered. Multiple Controls can be defined within a page, each with its own functional specification. For example, one Control might produce a popup window that allows the user to browse for a specific object and places the selection within the View, and another could save the new data to the Model.

What is a Ref Cursor?

- Oracle server uses unnamed memory spaces to store data used in implicit cursors.
- Ref cursors are used to define a cursor variable, which will point to that memory space and can be used like pointers in SQL ‘S’.

Difference between a function and a procedure in Oracle

               Functions                                                                   Procedures

* Invoke as a part of an expression.                             Execute as a PL/SQL statement.
* Must contain a RETURN clause in the header.         Do not contain a RETURN
                                                                                     Clause in the header.
* Must return a single value.                                        Can return none, one or many
                                                                                     values.
* Must contain at fast one RETURN                            Can contain a RETURN
Statement.                                                                   Statement.
* Do not contain OUT and INOUT                               Can contain IN, Out and
IN OUT parameters.                                                    IN OUT Parameters.

Types of Triggers in Reports: -

* Report Triggers * Data Triggers * Layout Triggers

Report Triggers: -

After Parameter form Trigger.
After Report Trigger
Before parameter form Trigger
Before Report Trigger.
Between Pages Trigger
+ Firing Sequence
* Before Parameter form Trigger
- Fires before the runtime parameter form is displayed.
- The parameter values can be accessed and changed.
* After Parameter form Trigger.
- Fires after the runtime parameter form is displayed.
- The parameters can be accessed and their values can be checked.
* Before Report Trigger
- Fires before the reports is executed but after the queries are passed and data is fetched.
* Between Pages Trigger.
- Fires between each page of the report are formatted, except the very first pages.
- This is used for customized page formatting.
* After Report Trigger
- Fires after exiting from the run time premier or after report output is sent to a specified
destination. (File, Printer, Mail id etc….)
- This is used to clean up any initial processing that was done such as deleting the tables.
- This Trigger always fires irrespective of success or failure of the report.

DATA TRIGGERS:-

* Ref Cursor Query.
- This uses PL/SQL to fetch data for the report.
- In this a PL/SQL function need to be specified to return a cursor value from a cursor variable.
-
* Group Filter:
This is PL/SQL function that determines which records to be included in a group in the
property are PL/SQL.
- The function must return a BOOLEAN value.
True ……. Includes the current record in the report.
False ……. Excludes the current record from the report.
* Formula
- These are PL/SQL functions that populate formula or place holder columns.
* Validation Trigger
- These are also PL/SQL functions that are executed when parameter values are specified on the
command line and when the runtime parameter form is accepted.
- Are also used to validate the initial value property of the parameter.

 Layout Triggers :- 

* Format Trigger.
- These are PL/SQL functions executed before the object is formatted.
- Used to dynamically change the formatting attributes of the object.
* Action Trigger
- These are PL/SQL procedures executed when a button is selected in the run time
Pre-viewer.
- This can be used to dynamically call another report or execute any other PL/SQL.

What is NOCOPY?

By default the IN parameter is passed by reference and the OUT and IN OUT parameters
are passed by value.
NOCOPY : is a compiles hint that can be used with OUT and IN OUT parameter to
request to pass by reference. This improves the performance with OUT and INOUT
parameters.