Oracle E-Business Suite Custom Library New Look

Presentator : Donald Ferreira Email : donaldferreira@gmail.com Location : BuZa Date : 19th December 2005 Oracle E-Business Suite 11i Custom Library giving a New Look

Agenda

Introduction

Structure

Advantages (BuZa and Team)

Q & A

Overall Picture

Unix

Forms

Libraries Logic Code example

Custom  

Connector  

Module  

Introduction What is Custom Library? Allows extensions and enforce business rules to Oracle Application without modifying the standard code. This is done using the Oracle development tool Oracle Forms 6i What is this presentation about? Re-engineering and transforming the existing business rules & process opportunities(Custom Library) into more structured and simplified solutions. A part of thi solution is already being implemented in production environment(PIRP) Who are the key players and benefiaries? ECC-Maatwerk Team, will play a key role in Re-engineering/ structuring of the Custom library. All the departments of EC i.e. Maatwerk, Kennisbeheer, Test team, TM, etc will benefit from this simplified solution.

Donald Structure (Overall picture)- I CC.pll OKC.pll FND.pll COMMON.pll AP.pll AR.pll GL.pll PA.pll HR.pll CUSTOM.pll ( Custom Library) CONNECTOR.pll

Untouchable Library New Module Libraries Structure ( UNIX ) - II

Structure ( Forms 6 i ) - III $AU_TOP/resource $XXX_TOP/forms/US

Structure (Custom.pll Logic) - IV CUSTOM.pll ( Custom Library)

Declaration of Global Variables which can be used across all libraries

Application Short Name (ASN) fnd_global.application_short_name

From Name (FRM) system.curremt_name

Block Name (BLK) system.cursor_block

Field Name (FLD) system.cursor_block

Triggering the call to objects of xxbz_connector_custom.pll

FUNCTION zoom  xxbz_connector_custom.zoom;

FUNCTION style  xxbz_connector_custom.style;

PROCEDURE event  xxbz_connector_custom.event;

Declaring all global variables app_short_name VARCHAR2(2000) DEFAULT fnd_global.application_short_name; form_name VARCHAR2(2000) DEFAULT name_in('SYSTEM.CURRENT_FORM'); block_name VARCHAR2(2000) DEFAULT name_in('SYSTEM.CURSOR_BLOCK'); field_name VARCHAR2(2000) DEFAULT name_in(‘SYSTEM.CURSOR_FIELD’); Structure (Custom.pll – code example) CUSTOM.pll ( Custom Library) FUNCTION style(event_name) xxbz_connector_custom.style(event_name) END event; FUNCTION zoom xxbz_connector_custom.zoom END event; PROCEDURE event(event_name) RETURN BOOLEAN IS vapp_short_name VARCHAR2(2000) DEFAULT fnd_global.application_short_name; BEGIN default_value(‘1’, ‘global.capp_short_name’); default_value(‘1’, ‘global.cform_name’); default_value(‘1’, ‘global.cblock_name’); default_value(‘1’, ‘global.cfield_name’); copy(vapp_short_name, ‘global.capp_short_name’); copy(vform_name , ‘global.cform_name’); copy(vblock_name , ‘global.cblock_name’); copy(vfield_name , ‘global.cfield_name’); xxbz_connector_custom.event(event_name); END event;

XXBZ_CONNECTOR_CUSTOM.pll Structure (XXBZ_CONNECTOR_CUSTOM.pll Logic) - V Calling extended libraries based on Modules Each Oracle Applications Form is linked to an Application(Module). When a form is opened by the user/system/zoom/special menu, the global variable ASN will get it’s application short name that is attached to the form. Based on this value, the related module library will be called : For example: Form Invoked  Application Short Name(ASN)  Extended Library called IGCCENTR IGC xxbz_igc_custom.pll ARXTWMAI AR xxbz_ar_custom.pll PAXBUEBU PAX xxbz_pa_custom.pll

Calling extended libraries ONLY when it is needed

Firing forms and block level triggers

(eg. When-New-Block-Instance, When-New-Record-Instance, When-New-Item-Instance, WVR, etc…)

Other standard events like : Special triggers, Zoom, etc..

This can either be controlled at CUSTOM library or in the XXBZ_CONNECTOR_CUSTOM library

Structure (XXBZ_CONNECTOR_CUSTOM.pll - code example) No PROCEDURE event(event_name) RETURN BOOLEAN IS --Declare variables BEGIN -- 1. Oracle Receivables IF name_in(‘global.capp_short_name’) = 'AR' THEN xxbz_ar_custom.event(event_name); -- 2. Oracle Payables ELSIF name_in(‘global.capp_short_name’) = 'SQLAP' THEN xxbz_ap_custom.event(event_name); -- 3. General Ledger ELSIF name_in(‘global.capp_short_name’) = ‘GL' THEN xxbz_gl_custom.event(event_name); ELSIF ………… THEN ……… ……… END IF; END event; END IF; IF event_name IN (WNFI, WNBI, WNRI, WVR, SPECIAL n, etc…) THEN Enter BuZa Library, and call the related module library Oracle Forms Is firing trigger a standard Custom library trigger? Yes Exit

CC.pll OKC.pll FND.pll COMMON.pll AP.pll AR.pll GL.pll PA.pll HR.pll Structure (Module Libraries Logic) - VI

Basic structure of the module library

Seperate program unit for every Oracle Apps. FORM

Each program unit will be further divided into following activities:

Form level activities

Event and Block level activities

Quick and easy creation of new extended libraries by using pre-built templates

XXBZ_ <modulename> _CUSTOM.pll

Re-usable library, for all module libraries

Creation of a common re-usable library called XXBZ_COMMON_CUSTOM.pll

All re-usable code will be placed in this library which can be called from the extended libraries.

Some of the few reusable objects are for eg. :

Setting up LOV’s

Creation of record groups

etc….

Structure (Extended Libraries - code example) PROCEDURE event(event_name) BEGIN IF name_in( 'global.cform_name' ) = 'ARXTWMAI' THEN --Form level activities z_ARXTWMAI.form_level; --Start Block level activities IF name_in( 'global.cblock_name' ) = ‘TGW_HEADER' THEN z_ARXTWMAI.tgw_header; ELSIF name_in('global.cblock_name') = ‘TACC_ACC_ASSGN' THEN z_ARXTWMAI.tacc_acc_assgn; END IF; --End Block level activities ELSIF name_in( 'global.cform_name' ) = 'ARXCWMAI' THEN ……… . ……… . END IF; END event; PROCEDURE form_level BEGIN IF event_name = ‘WHEN-NEW-FORM-INSTANCE' THEN Perform Code for WNFI at form level; ELSIF event_name = ‘WHEN-NEW-BLOCK-INSTANCE' THEN Perform Code WNBI at form level; END IF; END; PROCEDURE TGW_HEADER BEGIN IF event_name = ‘WHEN-NEW-BLOCK-INSTANCE' THEN Perform Code for WNFI for the block; ELSIF event_name = ‘WHEN-NEW-ITEM-INSTANCE' THEN Perform Code WNBI for the block; END IF; END TGW_HEADER;

The Module Library’s Release Version Number from PVCS could be easily checked at a quick glance in Oracle Appication by using Help-About Oracle Applications Adding & Viewing Version history

Advantages