Concurrent Program: phase_code, status_code meanings

Very old but still useful stuff...

status_code and phase_code in FND_CONCURRENT_REQUESTS table

PHASE_CODE column
C - Completed
I - Inactive
P - Pending
R - Running

 

STATUS_CODE Column:

A - Waiting
B - Resuming
C - Normal
D - Cancelled
E - Error
F - Scheduled
G - Warning
H - On Hold
I - Normal
M - No Manager
Q - Standby
R - Normal
S - Suspended
T - Terminating
U - Disabled
W - Paused
X - Terminated
Z - Waiting

OBIEE and ODI

OBIEE: The Oracle Business Intelligence Suite Enterprise Edition Plus (EE) is a comprehensive suite of enterprise BI products, delivering the full range of BI capabilities including interactive dashboards, full ad hoc, proactive intelligence and alerts, enterprise and financial reporting, real-time predictive intelligence, disconnected analytics, and more. It is featuring a unified, highly scalable, modern architecture, Oracle BI EE Plus provides intelligence and analytics from data spanning enterprise sources and applications—empowering the largest communities with complete and relevant insight.

In addition to providing the full gamut of BI functionality, the Oracle Business Intelligence Suite EE Plus platform is based on a proven, modern Web Services-Oriented Architecture that delivers true next-generation BI capabilities.

ODI: Oracle Data Integrator Enterprise Edition delivers unique next-generation, Extract Load and Transform (E-LT) technology that improves performance, reduces data integration costs, even across heterogeneous systems. Unlike conventional ETL tools, Oracle Data Integrator EE offers the productivity of a declarative design approach, as well as the benefits of an active integration platform for seamless batch and real-time integration. In addition, hot-pluggable Knowledge Modules provide modularity, flexibility, and extensibility.

 

http://www.scribd.com/doc/33730571/ODI-Integration-With-OBIEE

http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/overview/index.html

http://www.oracle.com/technetwork/testcontent/obiee-plm-bi-128330.pdf

OLE DB - Microsoft API to access non-RDBMS sources

The title already summarizes what OLE DB is about. Let's have a look what Wikipedia has written about it.

OLE DB (Object Linking and Embedding, Database, sometimes written as OLEDB or OLE-DB), an API designed by Microsoft, allows accessing data from a variety of sources in a uniform manner. The API provides a set of interfaces implemented using the Component Object Model (COM); it is otherwise unrelated to OLE. Microsoft originally intended OLE DB as a higher-level replacement for, and successor to, ODBC, extending its feature set to support a wider variety of non-relational databases, such as object databases and spreadsheets that do not necessarily implement SQL.

http://en.wikipedia.org/wiki/OLE_DB

Data Mart vs OLAP Cubes (Traditional DB vs Multidimentional DB)

Data Mart and Cubes - In Short:
Data mart is a collection of data of a specific business process. It is irrelevant how the data is stored.

A cube stores data in a special way, multiple-dimension, unlike a table with row and column. A cube in an OLAP database is like a table in a traditional database.

A data mart can have tables or cubes. Cubes make the analysis faster because it pre-calculates aggregations ahead of time.


In Detail:
Cube is an OLAP artifact. OLAP cubes can use a different API to a standard relational database. Typically OLAP servers maintain their own optimized data structures (known as MOLAP), although they can be implemented as a front-end to a relational data source (known as ROLAP) or in various hybrid modes (known as HOLAP).

'Data Mart' is also a fairly loosely used term and can mean any user-facing data access medium for a data warehouse system. The definition MAY or MAY NOT include the reporting tools and metadata layers, reporting layer tables or other items such as Cubes or other analytic systems.

Traditionally Data Mart is considered as the database from which the reporting is done, particularly if it is a easily definable subsystem of the overall data warehouse architecture. However it is quite reasonable to think of it as the user facing reporting layer, particularly if there are ad-hoc reporting tools such as Business Objects or OLAP systems that allow end-users to get at the data directly.

http://stackoverflow.com/questions/360900/datamart-vs-reporting-cube-what-are-the-differences

How to examine OPP logs

From the application:

- Login to System Administrator Responsibility
- Navigate to: Concurrent > Manager > Administer
- Select the Output Post Processor
- Click on the Processes button
- Select the process that was active when the request ran
- Click on the Manager Log button to open the OPP log file

From the file system:

SQL> SELECT fcpp.concurrent_request_id req_id, fcp.node_name, fcp.logfile_name
FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp
WHERE fcpp.processor_id = fcp.concurrent_process_id
AND fcpp.action_type = 6
AND fcpp.concurrent_request_id = <request_id>;

Credit goes to

Hussein Sawwan. Copied from his OTN post

https://kr.forums.oracle.com/forums/thread.jspa?threadID=646563

EBS CP Parameters - small but useful stuff :)

Let's say you have 2 parameters in a EBS concurrent program (CP).

1 p_ledger_name
2. p_ledger_id

You want to set the value for the p_ledger_id based on the value choosen for p_ledger_name. You can do it this way.

SETP 1
=====
Set the p_ledger_name default parameter type = SQL Statement
SQL statement can be this which ensures the users get to choose only the ledgers they have access to.
select name from gl_ledgers where ledger_id = gl_access_set_security_pkg.get_default_ledger_id(:$PROFILES$.GL_ACCESS_SET_ID, 'R')

STEP 2
=====
p_ledger_id parameter should also be set as SQL Type and SQL can be as follows,
select gl_ledger_utils_pkg.get_ledger_id_of_short_name(:$FLEX$.GL_SRS_LEDGER_WITH_SETS_AND_ALCS_STORE_SHORT_NAME) FROM DUAL

Here GL_SRS_LEDGER_WITH_SETS_AND_ALCS_STORE_SHORT_NAME is the value set name of the p_ledger_name parameter (my first parameter). Now lets have a look at this Value Set.

This value set is a character type value set. Validation Type = Table. You can check the value set details by clicking Edit Information button.

STEP 3
=====
Save your CP and Test it. When you choose the ledger name in the first parameter, you will get the ledger id in the second parameter automatically. Cool!!