Oracle applications Products short name list in R12:

Oracle applications Products short name list in R12:

ABM - Activity Based Management (Obsolete)
AD - Applications DBA
AHL - Complex Maintenance Repair and Overhaul
AHM - Hosting Manager(Obsolete)
AK - Common Modules-AK
ALR - Alert
AME - Approvals Management
AMF - Fulfillment Services (Obsolete)
AMS - Marketing
AMV - Marketing Encyclopedia System
AMW - Internal Controls Manager
AN - Sales Analysis
AP - Payables
AR - Receivables
AS - Sales Foundation
ASF - Sales Online
ASG - CRM Gateway for Mobile Devices
ASL - Sales Offline
ASN - Sales
ASO - Order Capture
ASP - Oracle Sales for Handhelds
AST - TeleSales
AU - Application Utilities
AX - Global Accounting Engine
AZ - Application Implementation
BEN - Advanced Benefits
BIC - Customer Intelligence (obsolete)
BIE - eCommerce Intelligence
BIL - Sales Intelligence
BIM - Marketing Intelligence
BIN - Communications Intelligence
BIS - Applications BIS
BIV - Service Intelligence
BIX - Interaction Center Intelligence
BIY - Systems Intelligence
BLC - Utility Billing
BNE - Web Applications Desktop Integrator
BOM - Bills of Material
BSC - Balanced Scorecard
CCT - Telephony Manager
CDR - Oracle Clinical Data Repository
CE - Cash Management
CHV - Supplier Scheduling
CLA - APAC Consulting Localizations
CLE - EMEA Consulting Localizations
CLJ - Japan Consulting Localizations
CLL - LAD Consulting Localizations
CLN - Supply Chain Trading Connector for RosettaNet
CN - Incentive Compensation
CPGC - CPG - CDOA
CRP - Capacity
CS - Service
CSC - Customer Care
CSD - Depot Repair
CSE - Asset Tracking
CSF - Field Service
CSI - Install Base
CSL - Field Service/Laptop
CSM - Field Service/Palm
CSN - Call Center
CSP - Spares Management
CSR - Scheduler
CSS - Support (obsolete)
CST - Cost Management
CTB - Clinical Transaction Base
CUA - Capital Resource Logistics - Assets
CUC - Revenue Accounting
CUE - Billing Connect (obsolete)
CUF - Capital Resource Logistics - Financials
CUG - Citizen Interaction Center
CUI - Network Logistics - Inventory
CUN - Network Logistics - NATS (obsolete)
CUP - Network Logistics - Purchasing
CUR - Mass Market Receivables for Comms
CUS - Network Logistics
CZ - Configurator
DDD - CADView-3D
DDR - Demand Signal Repository
DEM01 - Team 01 Order Entry Demo
DNA - Development
DOM - Document Managment and Collaboration
DPP - Oracle Price Protection
DT - DateTrack
DUMMY_GMO - Obsolete Process Operations
EAA - SEM Exchange (obsolete)
EAM - Enterprise Asset Management
EC - e-Commerce Gateway
ECX - XML Gateway
EDR - E-Records
EGO - Advanced Product Catalog
EMS - Environment Management System
ENG - Engineering
ENI - Product Intelligence
EVM - Value Based Management
FEM - Enterprise Performance Foundation
FF - FastFormula
FII - Financial Intelligence
FLM - Flow Manufacturing
FND - Application Object Library
FPA - Project Portfolio Analysis
FPT - Banking Center (obsolete)
FRM - Report Manager
FTE - Transportation Execution
FTP - Transfer Pricing
FUN - Financials Common Modules
FV - Federal Financials
GCS - Financial Consolidation Hub
GHR - US Federal Human Resources
GL - General Ledger
GMA - Process Manufacturing Systems
GMD - Process Manufacturing Product Development
GME - Process Manufacturing Process Execution
GMF - Process Manufacturing Financials
GMI - Process Manufacturing Inventory
GML - Process Manufacturing Logistics
GMO - Manufacturing Execution System for Process Manufacturing
GMP - Process Manufacturing Process Planning
GMS - Grants Accounting
GMW - Process Manufacturing Portal
GNI - Genealogy Intelligence
GR - Process Manufacturing Regulatory Management
HCA - Healthcare
HCC - iHCConnect
HCN - iHCIntegrate
HCP - Healthcare Intelligence
HCT - Healthcare Terminology Server
HRI - Human Resources Intelligence
HXC - Time and Labor Engine
HXT - Time and Labor
IA - iAssets
IAM - Digital Asset Management
IBA - iMarketing (Obsolete)
IBC - Content Manager
IBE - iStore
IBP - Bill Presentment & Payment
IBT - iAuction
IBU - iSupport
IBW - Oracle Web Analytics
IBY - Payments
ICX - Oracle iProcurement
IEB - Interaction Blending
IEC - Advanced Outbound Telephony
IEM - Email Center
IEO - Interaction Center Technology
IEP - Predictive
IES - Scripting
IET - Call Center Connectors
IEU - Universal Work Queue
IEV - IVR Integrator
IEX - Collections
IGC - Contract Commitment
IGF - Financial Aid
IGI - Public Sector Financials International
IGS - Student System
IGW - Grants Proposal
IMC - Customers Online
IMT - iMeeting (obsolete)
INL - Oracle Landed Cost Management
INV - Inventory
IPA - Capital Resource Logistics - Projects
IPD - Product Development (obsolete)
IPM - Oracle Imaging Process Management
IRC - iRecruitment
ISC - Supply Chain Intelligence
ISX - iSettlement
ITA - Information Technology Audit
ITG - Internet Procurement Enterprise Connector
IZU - Oracle E-Business Suite Diagnostics
JA - Asia/Pacific Localizations
JE - European Localizations
JG - Regional Localizations
JL - Latin America Localizations
JMF - Supply Chain Localizations
JTF - CRM Foundation
JTM - Mobile Application Foundation
JTS - CRM Self Service Administration
LNS - Loans
ME - Controlled Availability Product(Obsolete)
MFG - Manufacturing
MIA - Mobile Applications for Inventory Management
MIV - Media Interactive
MQA - Mobile Quality Applications
MRP - Master Scheduling/MRP
MSC - Advanced Supply Chain Planning
MSD - Demand Planning
MSO - Constraint Based Optimization
MSR - Inventory Optimization
MST - Transportation Planning
MTH - Oracle Manufacturing Operations Center
MWA - Mobile Applications
OAM - Oracle Applications Manager
ODQ - Data Query
OE - Order Entry
OFA - Assets
OKB - Contracts for Subscriptions (Obsolete)
OKC - Contracts Core
OKC_REP_TXT_INDEX_OPTIMIZE - Optimize Contracts Repository Text index
OKC_REP_TXT_INDEX_SYNC - Build/syncronize Contracts Repository Text index
OKE - Project Contracts
OKI - Contracts Intelligence
OKL - Leasing and Finance Management
OKO - Contracts for Sales (Obsolete)
OKP - Contracts for Procurement (Obsolete)
OKR - Contracts for Rights (Obsolete)
OKS - Service Contracts
OKT - Royalty Management
OKX - Contracts Integration
ONT - Order Management
OPI - Operations Intelligence
OTA - Learning Management
OUC - University Curriculum
OZF - Trade Management
OZP - Trade Planning (Obsolete)
OZS - iClaims (Obsolete)
PA - Projects
PAY - Payroll
PBR - Budgeting and Planning
PER - Human Resources
PFT - Oracle Profitability Manager
PJI - Project Intelligence
PJM - Project Manufacturing
PMI - Process Manufacturing Intelligence
PN - Property Manager
PO - Purchasing
POA - Purchasing Intelligence
POM - Exchange
PON - Sourcing
POS - iSupplier Portal
PQH - Public Sector HR
PQP - Public Sector Payroll
PRP - Proposals
PSA - Public Sector Financials
PSB - Public Sector Budgeting
PSP - Labor Distribution
PSR - Public Sector Receivables
PTX - Patch Tracking System
PV - Partner Management
QA - Quality
QOT - Quoting
QP - Advanced Pricing
QPR - Oracle Deal Management
QRM - Risk Management
RCM - Regulatory Capital Manager (obsolete)
RG - Application Report Generator
RHX - Advanced Planning Foundation(obsolete)
RLA - Release Management Integration Kit (Obsolete)
RLM - Release Management
RMG - Risk Manager
RRC - Retail Core
RRS - Site Management
SHT - Applications Shared Technology
SSP - SSP
SYSADMIN - System Administration
TEST - test
VEA - Automotive
VEH - Automotive Integration Kit (Obsolete)
WIP - Work in Process
WMA - Manufacturing Mobile Applications
WMS - Warehouse Management
WPS - Manufacturing Scheduling
WSH - Shipping Execution
WSM - Shop Floor Management
XDO - XML Publisher
XDP - Provisioning
XLA - Subledger Accounting
XLE - Legal Entity Configurator
XNA - Service Assurance for Communications
XNB - Oracle Telecommunications Billing Integrator
XNC - Sales for Communications (Obsolete)
XNI - Install Base Intelligence (Obsolete)
XNM - Marketing for Communications (Obsolete)
XNP - Number Portability
XNS - Service for Communications (obsolete)
XNT - TeleBusiness for Telecom/Utilities
XTR - Treasury
ZFA - Financial Analyzer
ZPB - Enterprise Planning and Budgeting
ZSA - Sales Analyzer
ZX - E-Business Tax

DECODE FUNCTION VS CASE:

Decode Function and Case Statement in Oracle: Decode Function and Case Statement are used to transform data values at retrieval time. DECODE and CASE are both analogous to the "IF THEN ELSE" conditional statement.

History of DECODE and CASE:

Before version 8.1, the DECODE was the only thing providing IF-THEN-ELSE functionality in Oracle SQL. Because DECODE can only compare discrete values (not ranges), continuous data had to be contorted into discreet values using functions like FLOOR and SIGN. In version 8.1, Oracle introduced the searched CASE statement, which allowed the use of operators like > and BETWEEN (eliminating most of the contortions) and allowing different values to be compared in different branches of the statement (eliminating most nesting). In version 9.0, Oracle introduced the simple CASE statement, that reduces some of the verbosity of the CASE statement, but reduces its power to that of DECODE.

Decode Function and Case Statement Example: 

Example with DECODE function

Say we have a column named REGION, with values of N, S, W and E. When we run SQL queries, we want to transform these values into North, South, East and West. Here is how we do this with the decode function:

select
decode (
region,
‘N’,’North’,
‘S’,’South’,
‘E’,’East’,
‘W’,’West’,
‘UNKNOWN’
)
from
customer;

Note that Oracle decode starts by specifying the column name, followed by set of matched-pairs of transformation values. At the end of the decode statement we find a default value. The default value tells decode what to display if a column values is not in the paired list.

Example with CASE statement

select
case
region
when ‘N’ then ’North’
when ‘S’ then ’South’
when ‘E’ then ’East’,
when ‘W’ then ’West’
else ‘UNKNOWN’
end
from
customer;

Difference between DECODE and CASE:

Everything DECODE can do, CASE can. There is a lot more that you can do with CASE, though, which DECODE cannot. Differences between them are listed below:

1. DECODE can work with only scaler values but CASE can work with logical oprators, predicates and searchable subqueries.
2. CASE can work as a PL/SQL construct but DECODE is used only in SQL statement.CASE can be used as parameter of a function/procedure.
3. CASE expects datatype consistency, DECODE does not.
4. CASE complies with ANSI SQL. DECODE is proprietary to Oracle.
5. CASE executes faster in the optimizer than does DECODE.
6. CASE is a statement while DECODE is a fucntion.

CASE can work with logical operators other than ‘=’

DECODE performs an equality check only. CASE is capable of other logical comparisons such as < > etc. It takes some complex coding – forcing ranges of data into discrete form – to achieve the same effect with DECODE.

An example of putting employees in grade brackets based on their salaries. This can be done elegantly with CASE.

SQL> select ename
  2       , case
  3           when sal < 1000
  4                then 'Grade I'
  5           when (sal >=1000 and sal < 2000)
  6                then 'Grade II'
  7           when (sal >= 2000 and sal < 3000)
  8                then 'Grade III'
  9           else 'Grade IV'
 10         end sal_grade
 11  from emp
 12  where rownum < 4;

ENAME      SAL_GRADE
---------- ---------
SMITH      Grade I
ALLEN      Grade II
WARD       Grade II

CASE can work with predicates and searchable subqueries

DECODE works with expressions that are scalar values only. CASE can work with predicates and subqueries in searchable form.

An example of categorizing employees based on reporting relationship, showing these two uses of CASE.

SQL> select e.ename,
  2         case
  3           -- predicate with "in"
  4           -- mark the category based on ename list
  5           when e.ename in ('KING','SMITH','WARD')
  6                then 'Top Bosses'
  7           -- searchable subquery
  8           -- identify if this emp has a reportee
  9           when exists (select 1 from emp emp1
 10                        where emp1.mgr = e.empno)
 11                then 'Managers'
 12           else
 13               'General Employees'
 14         end emp_category
 15  from emp e
 16  where rownum < 5;

ENAME      EMP_CATEGORY
---------- -----------------
SMITH      Top Bosses
ALLEN      General Employees
WARD       Top Bosses
JONES      Managers

CASE can work as a PL/SQL construct

DECODE can work as a function inside SQL only. CASE can be an efficient substitute for IF-THEN-ELSE in PL/SQL.

SQL> declare
  2    grade char(1);
  3  begin
  4    grade := 'b';
  5    case grade
  6      when 'a' then dbms_output.put_line('excellent');
  7      when 'b' then dbms_output.put_line('very good');
  8      when 'c' then dbms_output.put_line('good');
  9      when 'd' then dbms_output.put_line('fair');
 10      when 'f' then dbms_output.put_line('poor');
 11      else dbms_output.put_line('no such grade');
 12    end case;
 13  end;
 14  /

PL/SQL procedure successfully completed.

CASE can even work as a parameter to a procedure call, while DECODE cannot.

SQL> var a varchar2(5);
SQL> exec :a := 'THREE';

PL/SQL procedure successfully completed.

SQL>
SQL> create or replace procedure proc_test (i number)
  2  as
  3  begin
  4    dbms_output.put_line('output = '||i);
  5  end;
  6  /

Procedure created.

SQL> exec proc_test(decode(:a,'THREE',3,0));
BEGIN proc_test(decode(:a,'THREE',3,0)); END;

                *
ERROR at line 1:
ORA-06550: line 1, column 17:
PLS-00204: function or pseudo-column 'DECODE' may be used inside a SQL
statement only
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored


SQL> exec proc_test(case :a when 'THREE' then 3 else 0 end);
output = 3

PL/SQL procedure successfully completed.

Careful! CASE handles NULL differently

Check out the different results with DECODE vs NULL.

SQL> select decode(null
  2              , null, 'NULL'
  3                    , 'NOT NULL'
  4               ) null_test
  5  from dual;

NULL
----
NULL

SQL> select case null
  2         when null
  3         then 'NULL'
  4         else 'NOT NULL'
  5         end null_test
  6  from dual;

NULL_TES
--------
NOT NULL
The “searched CASE” works as does DECODE.

SQL>  select case
  2         when null is null
  3         then 'NULL'
  4         else 'NOT NULL'
  5         end null_test
  6* from dual
SQL> /

NULL_TES
--------
NULL

CASE expects datatype consistency, DECODE does not

Compare the two examples below- DECODE gives you a result, CASE gives a datatype mismatch error.

SQL> select decode(2,1,1,
  2                 '2','2',
  3                 '3') t
  4  from dual; 

         T
----------
         2 

SQL> select case 2 when 1 then '1'
  2              when '2' then '2'
  3              else '3'
  4         end
  5  from dual;
            when '2' then '2'
                 *
ERROR at line 2:
ORA-00932: inconsistent datatypes: expected NUMBER got CHAR

CASE is ANSI SQL-compliant

CASE complies with ANSI SQL. DECODE is proprietary to Oracle.

7. The difference in readability

In very simple situations, DECODE is shorter and easier to understand than CASE.

SQL> -- An example where DECODE and CASE
SQL> -- can work equally well, and 
SQL> -- DECODE is cleaner

SQL> select ename
  2       , decode (deptno, 10, 'Accounting',
  3                         20, 'Research',
  4                         30, 'Sales',
  5                             'Unknown') as department
  6  from   emp
  7  where rownum < 4;

ENAME      DEPARTMENT
---------- ----------
SMITH      Research
ALLEN      Sales
WARD       Sales

SQL> select ename
  2       , case deptno
  3           when 10 then 'Accounting'
  4           when 20 then 'Research'
  5           when 30 then 'Sales'
  6           else         'Unknown'
  7           end as department
  8  from emp
  9  where rownum < 4;

ENAME      DEPARTMENT
---------- ----------
SMITH      Research
ALLEN      Sales
WARD       Sales