GL Hist Padrao Application Technical Documentation
GL Hist Padrao Application Technical Documentation
GL Historico Padrao
1 of 14
Table of content
2. ERD.................................................................................................................................................2
3. SYSTEM ARCHITECTURE...............................................................2
4. APPLICATION DESCRIPTION..................................................2
5. SETUP / INSTALLATION......................................................................2
8. External Interfaces....................................................................................2
2 of 14
1.Application Block Diagram
a. Triggers (CNS_GL_HIST_PADRAO_AP) methods call flow diagram
3 of 14
FA_OPS_MASS_ADDITIONS_CREATE MTL_TRANSACTION_ACCOUNTS Table
CNS_OM_TRANS_TO_ASSET_TRG
User Initiated Trigger Initiated
GET_FA_MA_UPDATE_VALUE
S
FA INTERFACE
CNS_OM_ERROR_HANDLER_MULTI CNS_TRX_ERROR_HANDLER_MULTI
SEND_MAIL
4 of 14
b. Concurrent Call flow diagram
CNS Manufactured Assets Create CNS Manufactured Asset Add CNS Manufactured Asset Delete
OM79OPS - Sales Order Cogs Temp Table OM79OPS - Sales Order Cogs Temp Table
Legend:
CNS_OM_MANUFACTURED_ASSETS_CREATE CNS_OM_INIT_MAN_ASSET_ADD
Concurrent Program
Request Set
2.ERD
5 of 14
CNS_OM_MANUFACTURED_ASSETS
6 of 14
b. Table Creation DDL statement
-- Create table
create table CNS_CUST.CNS_OM_MANUFACTURED_ASSETS
(
UNIT_CODE VARCHAR2(150) not null,
ASSET_TYPE_CODE VARCHAR2(150) not null,
TRANSACTION_ID NUMBER,
SALES_ORDER_HEADER_ID NUMBER,
SALES_ORDER_NUMBER NUMBER,
SALES_ORDER_LINE_ID NUMBER,
SALES_ORDER_LINE_NUMBER NUMBER,
INVENTORY_ITEM_ID NUMBER,
ITEM_PART_NUMBER VARCHAR2(40),
ITEM_ORGANIZATION_ID NUMBER,
ITEM_DESCRIPTION VARCHAR2(240),
QUANTITY NUMBER,
PRS_NUMBER VARCHAR2(150),
ITEM_COST NUMBER,
DELTA_CABINET_COST_FM NUMBER,
DELTA_CABINET_COST_FA NUMBER,
TOTAL_COST_OH2_FM NUMBER,
TOTAL_COST_OH1_FA NUMBER,
DELTA_CALCULATED VARCHAR2(2),
BUDGET_CODE_CCID NUMBER,
BUDGET_CODE VARCHAR2(200),
CABINET_CATEGORY_L1 VARCHAR2(204),
BOOK_TYPE_CODE VARCHAR2(15),
ASSET_KEY VARCHAR2(150),
SO_TYPE_DESCRIPTION VARCHAR2(30),
SO_CIR VARCHAR2(150),
SO_LOGICAL_UNITS VARCHAR2(150),
SO_IS_LOANED VARCHAR2(2) not null,
MODIFICATION_ACTION_TYPE_CODE VARCHAR2(150) not null,
MODIFICATION_DATE DATE,
CREATION_DATE DATE,
CREATED_BY NUMBER,
LAST_UPDATE_DATE DATE,
LAST_UPDATED_BY NUMBER,
FA_REQUIRED VARCHAR2(2),
FM_REQUIRED VARCHAR2(2),
FA_IMPORTED VARCHAR2(2),
FA_IMPORT_DATE DATE,
FM_IMPORTED VARCHAR2(2),
FM_IMPORT_DATE DATE
)
tablespace CNSD
pctfree 10
pctused 40
initrans 1
maxtrans 255
storage
(
7 of 14
initial 40K
next 40K
minextents 1
maxextents 505
pctincrease 0
);
-- Create/Recreate primary, unique and foreign key constraints
alter table CNS_CUST.CNS_OM_MANUFACTURED_ASSETS
add constraint COMA_PK primary key (UNIT_CODE, SO_IS_LOANED, MODIFICATION_ACTION_TYPE_CODE)
using index
tablespace CNSD
pctfree 10
initrans 2
maxtrans 255
storage
(
initial 40K
next 40K
minextents 1
maxextents 505
pctincrease 0
);
8 of 14
so_cir,
so_logical_units,
so_is_loaned,
modification_action_type_code,
modification_date,
creation_date,
created_by,
last_update_date,
last_updated_by,
fa_required,
fm_required,
fa_imported,
fa_import_date,
fm_imported,
fm_import_date
FROM cns_cust.cns_om_manufactured_assets
WHERE fm_required = 'Y'
AND fm_imported = 'N';
3.System Architecture
FA OPS Manufactured Assets is a mostly PL/SQL based Oracle Applications customization.
It binds concurrent programs and sets with various PL/SQL procedures packed together on a consolidated package over the database.
Two systems are interfacing with the Manufactured Assets information, both of them collect their interface data from the same database on
which the Manufactured Assets interface lies.
The system has a single application form customization which applies a quantity of one (‘1’) to each item row of a MISC issue/receipt
transaction, for more information about this customization please refer to 4. d. INV MISC transaction form customization.
All of the system error management is done through e-mail notifications. The concurrent processes that across this application DOES NOT
report errors to logs, for more information refer to 4. e. Error Handling.
4.Application Description
All of the generated manufactured assets are inserted to a special table ( CNS_OM_MANUFACTURED_ASSETS) which holds them
logged until its imported through at least one of the interfaces.
9 of 14
The main creation mechanism (CNS Manufactured Assets Create concurrent) is scheduled to work daily and generates
manufactured assets out of the new Sales Orders added over the past 24 hours
Application created MISC transactions are automatically added as manufactured assets via a database trigger
(CNS_OM_TRANS_TO_ASSET_TRG) which resides on the MTL_TRANSACTION_ACCOUNTS table.
Creation of Manufactured Assets from a specific Sales Order is done by activating the CNS Manufactured Assets Add
concurrent.
Deletion of a specific Sales Order / MISC transaction manufactured assets is done via the CNS Manufactured Asset Delete
concurrent.
Oracle Applications’ FA module uses the OPS Manufactured Assets data in order of converting it onto official organization
fixed assets.
It does so by using the CNS OPS Mass Additions Create concurrent, this program scans all of the not yet fixed, manufactured
assets, identified by FA_IMPORTED field equals ‘N’ and processing them using the FA_OPS_MASS_MASS ADDITIONS_CREATE
procedure.
The File Maker user (CNS_FILEMAKER) is granted this view alone and can update only it’s FM_IMPORTED flag to indicate that
the specific manufactured asset was imported.
10 of 14
e. Error Handling
All of the application errors are reported via e-mails sent to distribution lists maintained on several value sets as listed below:
When refreshing environments from prod, one must use the CNS_OM_DISABLE_ERROR_VALUE_SETS.sql in order of disabling the
operational users that receive e-mail notifications from the process and do not want to be informed from any environment other than
PRODUCTION.
5.Setup / Installations
All files mentioned here are located over the “/Users/development11i/FA/OPS/” directory.
11 of 14
While creating new objects (not via epack) please refer to TESTCRM as source to implement from.
1. Database:
2. Application:
CUSTOM.pll instructions:
/*********************************************************************************************************************/
IF (p_event = 'WHEN-VALIDATE-RECORD') THEN
IF (p_form = 'INVTTMTX') THEN
12 of 14
-- Begin: Avi Kalvo 24/7/2005 - Set Quantity to 1
IF (name_in('MTL_TRX_HEADER.TRANSACTION_TYPE_NAME') IN ('CNS TA Misc. Issue to Capital', 'CNS TA Misc. Receipt Capital')
AND (name_in('MTL_TRX_LINE.TRANSACTION_QUANTITY') <> 1)) THEN
3. Save Unit
4. Compile Unit
5. Close Unit
6. Compile All Incremental using Ctrl+Shift+K
7. Link using ctrl + T
8. Check in CNS_INV.pll, CNS_INV.plx
7.External Interfaces
Here’s a diagram to describe how exactly does the Fixed Assets module and the File maker application are interfacing with the
Manufactured Assets data, for more information about Manufactured Assets interfaces please refer to 4. Application Description.
13 of 14
14 of 14