Technical Tasks Guideline

Contents
APIs: ................................................................................................................................... 2
Prerequisites: ................................................................................................................ 2
Technical Considerations:........................................................................................... 2
Delivered Files: ............................................................................................................. 2
Reports............................................................................................................................... 2
Prerequisites: ................................................................................................................ 2
Technical Considerations:........................................................................................... 2
For HCM Reports ..................................................................................................... 3
For Financial & SCM Reports ................................................................................ 4
Delivered Files: ............................................................................................................. 6
Forms ................................................................................................................................. 7
Customized Form: ............................................................................................................ 7
Prerequisites: ................................................................................................................ 7
Technical Considerations:........................................................................................... 7
Delivered Files: ............................................................................................................. 7
New Form .......................................................................................................................... 7
Prerequisites: ................................................................................................................ 7
Technical Considerations:........................................................................................... 8
Delivered Files: ........................................................................................................... 10
AME .................................................................................................................................. 11
Work Flow........................................................................................................................ 11
Prerequisites: .............................................................................................................. 11
Technical Considerations:......................................................................................... 11
Delivered Files: ........................................................................................................... 11
Alert .................................................................................................................................. 12
Prerequisites: .............................................................................................................. 12
Technical Considerations:......................................................................................... 12
Delivered Files: ........................................................................................................... 12
Account Generator Workflow ....................................................................................... 13
Brief Description : ....................................................................................................... 13
Account generator Processes : ................................................................................ 13
You should know about workflow account generator: .......................................... 13
Customizations : ............................................................................................................. 14
Prerequisites: .............................................................................................................. 14
Customization Steps: .................................................................................................... 14
Naming Convention: .................................................................................................. 15
Delivered Files: ........................................................................................................... 15
APIs:
For any Data Upload Scripts, the Task must contain the following:

Prerequisites:
 A Sample of DCS that is generic enough prepared by Functional Consultant

Technical Considerations:
 It’s recommended to use R12 APIs as all future Projects will be on it.
 Each API Procedure contains a Flag for Validating Data or Uploading it as
Validation Process must be done by Technical Consultant to insure all the Data
is correct before Upload Process
 No Hard Code in the API & detailed Comments for each sub-block of code
 For Translatable Data, Translation API must be considered in the Script.

Delivered Files:
 A Sample of DCS File
 Intermediate Tables’ Structures that are used for Data Upload
 A Package containing all needed APIs Procedures (Create, Update or Delete) for
Each Module.

Reports
For any Offshore Report, the delivered Report must contain the following:

Prerequisites:
 MD050 Document should be prepared by Functional Consultant with the
following Considerations:
o Detailed Description for the Report Purpose.
o Mandatory & Optional Parameters
o Each Field’s Path on the Application
o Technical Notes for the Technical Consultant such as Master-Detail
Relations, if the Master Exist with no detail, what the expected results to
be considered in the development
o The Required Layout (Header , Footer & Body)
o Concurrent Program Name

Technical Considerations:
 A Package containing all needed Program Units for Report Development with
Detailed comments & reference uses.
 Following the Naming Convention for all Report Objects to be as following:
 o Executable Name, Concurrent Program Code, RDF File & RTF File will
be XX<CUSTOMER_SHORTNAME>_<APPL SHORT
NAME>_<REPORT NAME>
o Value Set Name will be XX<CUSTOMER_SHORTNAME>_<APPL
SHORT NAME>_<RETURN FILED NAME>
o Package Name will be XX<CUSTOMER_SHORTNAME>_<APPL
SHORT NAME>_REPROTS
 The RDF must contain One Formula Column & as much as I need Place Holders
to encapsulate all the Codes in one Place & for Performance Wise.
 Registered Concurrent Program, Executable & Value Sets must be created by
SYSADMIN User not OPERATIONS User to be easily transferred between
Instances as CREATED BY User is mention in FNDLOAD Files.
 Templates will be translatable (Arabic & English)
 BR120 Document should be prepared by Technical Consultant with detailed
Technical Considerations & Related Registration Steps.(Optional)
 Apply Security Profile Rules

For HCM Reports

o Reports’ Queries will read their data from Security Views instead of
Tables and any Formula Columns Queries as well.

 Security Profiles are applied on HCM Tables that contain “ALL” in

its name & the relevant Security view in the same table name
without “ALL”. i.e.: PER _PEOPLE_F Security View for
PER_ALL_PEOPLE_F Table
o Table Values Sets shall read their data from Security Views instead of
Tables.
o Add 5 extra Parameters in RDF with type Number
 USER_ID
 RESP_ID
 RESP_APPL_ID
 SECURITY_GROUP_ID
 SERVER_ID
o In the Concurrent Program Parameters, add the same 5 Parameters with
default values from Profile Options of their exact names and not
Displayed
o In the RDF, Before Report Trigger, add the following:
function BeforeReport return boolean is
begin
FND_GLOBAL.APPS_INITIALIZE(:P_USER_ID,
:P_RESP_ID,
:P_RESP_APPL_ID,
:P_SECURITY_GROUP_ID,
:P_SERVER_ID);

return (TRUE);
end;
For Financial & SCM Reports
 Reports’ Queries will read their data from Security Views instead of Tables and
any Formula Columns Queries as well.
o Security Profiles are applied on Tables that contain “ALL” in its name & the
relevant Security view is the same table name without “ALL”. i.e.:
PO_REQUISITION_HEADERS is Security View for
PO_REQUISITION_HEADERS_ALL Table
 Table Value sets shall read their data from Security Views instead of Tables.

 Reports’ Queries will read their data from Security Views instead of Tables and
any Formula Columns Queries as well.
o Security Profiles are applied on Tables that contain “ALL” in its name &
the relevant Security view is the same table name without “ALL”. i.e.:
AP_INVOICES_ALL Security View for AP_INVOICES Table
 Table Values Sets shall read their data from Security Views instead of Tables.
 Add extra Parameter in RDF for ORG_ID nor in Concurrent Program
Parameters.
o Set its default Value as SQL statement:
SELECT mo_global.get_current_org_id FROM DUAL
 Add this code in RDF’s BeforeReport triggers

function BeforeReport return boolean is

begin
MO_GLOBAL.set_policy_context('S',:ORG_ID);
RETURN (TRUE);
end;

 Oracle has implemented a new parameter on the System Administration

(Responsibility) è Concurrent Program (Page)è Request (Tab) to control how
to handle Operating Units, change “Operating Unit Mode” value from NULL to
Single. Please note that this setting is not existing in System Administrator
(Responsibility) è Concurrent Program (Form). Check below screenshot:
 Submit Request Form will contain an Operating Unit Parameter that will be
selected initially & report parameters will be based on its value.
Delivered Files:
 RDF File
 RTF Files (Arabic & English)
 FNDLOAD File of the Registered Concurrent Program.
 MD050-120 Techno-Functional Document(Optional)
 Sample XML File
 Sample PDF Output
 The Package File of the Program Units needed for Reports Purposes.
Forms
For Forms Development, there are two sections that will be considered separately:

Customized Form:

Prerequisites:
 MD050 Document should be prepared by Functional Consultant with the
following Considerations:
o Detailed Description for the Form Customization Purpose.
o Prerequisite Functional Setup.

Technical Considerations:
 Detailed Description of the Personalization.
 Detailed Comments for each sub-block of Code in CUSTOM.pll
 Following the Naming Convention of the Package Name that contains Program
Units needed for Customization Purposes to be
XX<CUSTOMER_SHORTNAME>_<APPL SHORT NAME>_UTILS
 BR120 Document should be prepared by Technical Consultant with detailed
Technical Considerations, Related Personalization Steps & the Code of Custom
Library.(Optional)

Delivered Files:
 MD050-120 Techno-Functional Document(Optional)
 FNDLOAD File of Form Personalization.
 CUSTOM.pll File
 The Package File of the Program Units needed for Form Customization
Purposes.

New Form

Prerequisites:
 MD050 Document should be prepared by Functional Consultant with the
following Considerations:
o Detailed Description for the Form Purpose.
o Prerequisite Functional Setup.
o Initial Form Design
o Description of each Form Field such Field Type & Required Flag
 XXRAYA Schema must be designed first & registered on the Application.
 All Tables and Sequences should be created using schema owner XXRAYA
 All Tables and Sequences should have synonyms created for public on APPS
schema
 All Tables and SEQUENCES access should be granted to APPS user
 All Views and Packages should be created using schema owner APPS
Technical Considerations:

 Tables needed for the Developed Forms must contain the following Columns:
o WHO Columns (Created_By, Creation_Date, Last_Updated_By &
Last_Creation_Date) to keep the history of each record.
o Object_Version_Number to manage Record Lock behavior.
o Extra Column (Attribute1 … Attribute30) as Descriptive Flex Fields for any
further changes required from Customer Site.
o ORG_ID Column containing the Operating Unite ID for Financial & Supply
Chain Related Data & BUSINESS_GROUP_ID Column for Human
Resources Related Data must be considered in Table Structure.
o All Forms’ Block should be based on Data Base Views not directly on its
Tables.
o Primary Key Constraint must be defined on its Column.
o Ignore Not Null Constraint on Table level as it can be handled by Form
Field Properties.
o Tables Naming Convention will be
XX<CUSTOMER_SHORTNAME>_<APPL SHORT NAME>_<TABLE
NAME>_ALL.
o
 Multi Org Views will be based on any transaction table and will be used instead
of _ALL tables, these views will transparently enable multi-org security without
any extra coding in referencing objects.
o This view will be a simple query from the based table with all fields and
the condition that ORG_ID field is equal to the organization id assigned
to the user session, This will always keep data secured between different
operating units
o Where statement will be as the following:
Where NVL(ORG_ID,
NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1),
' ',
NULL,
SUBSTRB(USERENV('CLIENT_INFO'), 1,
10))),
-99)) =
NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1),
' ',
NULL,
SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))),
-99)

o Multi Org Views Naming Convention will be the same base Table Name
without _All
 Lookup Views will be based on defined lookups on the system, for seeded
lookups no need to define a view for this lookup, we will just use it, but for
transaction lookups which may be changed by the user at any time, a view will be
created with a name similar to the lookup name, and will query on lookups table
for all fields
o This will be useful incase a lookup structure is changed; the only change
will be done to the lookup view.
o View create statement will be as the following (Note: Replace
<LOOKUP_TYPE_NAME> with lookup type name created on the
application):
 Create or Replace View XXRAYA_<Appl Short Name>_<LOOKUP_TYPE_NAME> As
Select LOOKUP_CODE,
MEANING,
DESCRIPTION,
ENABLED_FLAG,
START_DATE_ACTIVE,
END_DATE_ACTIVE,
ATTRIBUTE_CATEGORY,
ATTRIBUTE1,
ATTRIBUTE2,
ATTRIBUTE3,
ATTRIBUTE4,
ATTRIBUTE5,
ATTRIBUTE6,
ATTRIBUTE7,
ATTRIBUTE8,
ATTRIBUTE9,
ATTRIBUTE10,
ATTRIBUTE11,
ATTRIBUTE12,
ATTRIBUTE13,
ATTRIBUTE14,
ATTRIBUTE15
FROM FND_LOOKUP_VALUES
WHERE LOOKUP_TYPE = '<LOOKUP_TYPE_NAME>'
AND LANGUAGE = USERENV('LANG')
AND APPLICATION_ID = <APPLICATION_ID>
o Lookup Views Naming Convention will be
XX<CUSTOMER_SHORTNAME>_<APPL SHORT NAME>_<LOOKUP
TYPE NAME>.
o
 Form Views will be based on base table (for non multi org table) or multi org
views of the base table joined with all related lookup views, foreign key
tables/multi org views to get the data(names, description, meanings) from the
foreign key table to be shown as fields on the form.
o Form Views Naming Convention will be <Multi Org View Name>_V.

 List of Values Views will be base for non straight forward with conditions list of
values assigned to specific form fields
o The benefit from these views is reusing the same LOV view more than
one time in more than one field, and maintaining LOV view structure
outside the form so that changes in LOV conditions could be maintained
from out side and applied to all referenced form field LOV’s with one
change on database and no changes on related forms.
o List of Values Views Naming Convention will be
XX<CUSTOMER_SHORTNAME>_<APPL SHORT NAME>_<LIST
NAME>_LOV.
 Sequences will be for all tables with ID key Column to populate the primary key
of the table
o Sequence Naming Convention will be <Table_Name>_S.
 Packages of all table handlers that will be created for normal insert, update, lock
and delete procedures. Any other Utility Functions & Procedures used in Forms
will be held on other Package.
o Table Handler Packages Naming Convention will be
XX<CUSTOMER_SHORTNAME>_<TABLE NAME without _ALL>_PKG.
o Utility Packages Naming Convention will be
XX<CUSTOMER_SHORTNAME>_<APPL SHORT NAME>_UTIL.
 Forms Development must be based on the following guidelines:
 o Form Development must be based on Oracle Standard Template.
o Data Block Name is the same name of its based View without _V.
o All Data Block must contain DFF & its related definition Triggers.
o All Form Objects (Fields, Data Blocks, Windows …) Properties must be
based on Standard Sub-Class.
o All Data Manipulation Triggers will be overridden on Data Block Level to
handle Insert, Update, Lock and Delete Triggers.
o No Direct Calling to any DB Procedure Directly through Triggers. All DB
Procedures will be encapsulated in Form Program Unit & the calling of
the Program Units will be in triggers to follow the Same Oracle Standards.
 Application Form Registration: All the registered Objects on the Application
must be created with SYSADMIN User not OPERATIONS User to be easily
transferred between Instances as CREATED BY User is mention in FNDLOAD
Files. All Objects named as unique code & only Data that is displayed to the
users has a Friendly User Name.
o Form Name, Form Function Name, Function User Name will be the same
as XX<CUSTOMER_SHORTNAME>_<APPL SHORT NAME>_<FORM
NAME>. The Prompt of the function in its related Menu will be a Friendly
User Name as it’s only displayed for the User
o All the Tables & there Columns must be registered on the Application
before referencing it in DFF Definition.
o Descriptive Flex Field Definition Name is the same as its Base Table.
 MD060 Document should be prepared by Technical Consultant with detailed
Data Base Extensions’ Schema & Consideration.
 BR120 Document should be prepared by Technical Consultant with detailed
Technical Considerations & Related Registration Steps.

Delivered Files:
 All DB Objects Files (Tables Structures, Views, Sequences, Synonyms &
Packages).
 FMB Form File.
 FMX Executable File.
 FNDLOAD Files for all required Application Registrations (Forms, DFF
Definitions, Lookups and Messages).
 MD050-120 Techno-Functional Document(Optional)
 MD060 Database Extension Technical Document.
AME
For AME Tasks, It’s hard to create reusable Components for this field as there is no
common requirement for the Approval Rule. We can only make a referenced library for a
Common Dynamic Attributes & Approver Groups Definitions.

Work Flow
Prerequisites:
 MD050 Document should be prepared by Functional Consultant with the
following Considerations:
o Detailed Description for the Customization Purpose.
o Prerequisite Functional Setup.

Technical Considerations:
 As much as we can all the Customized Activities is consolidated in Sub-Process
to be easy for updates.
 BR120 Document should be prepared by Technical Consultant with detailed
Technical Considerations.

Delivered Files:
 WFT File
 BR120 Technical Document
Alert
Prerequisites:
 MD050 Document should be prepared by Functional Consultant with the
following Considerations:
o Detailed Description for the Customization Purpose.
o Prerequisite Functional Setup.

Technical Considerations:
 BR120 Document should be prepared by Technical Consultant with detailed
Technical Considerations and Alert Definition as there is no Tools to Backup
Alert Definition.

Delivered Files:
 BR120 Technical Document
Account Generator Workflow

Brief Description :
Applications need to construct Accounting Flexfield combinations automatically.
The Account Generator feature uses Oracle Workflow technology to provide
applications with the ability to construct key flexfield combinations automatically
using customized construction criteria. Each site can customize how they want to
build key flexfield combinations.

Account generator Processes :

Generate Default Accrual Account
Generate Default Budget Account
Generate Default Charge Account
Generate Default Variance Account

You should know about workflow account generator:

Access Level in Workflow:
 Is a property in workflow help you protect your workflow customizations from
workflow definition upgrade.
 All workflow objects except lookup codes, function attributes, and message
attributes contain an Access tab in their property pages so you can change it
to your level of access.
 You can set your access level to 1000 to be public for any type of changes
 You can check the access level table in workflow document to set your
access level
 To change in any process your access level should be the same as the
access level of the target object.
Standard Functions of account generator workflow:
 Start Generating Code Combination (the functions used to start the activity
that generates the code combinations . It should not be used as a start activity of any
sub-process).
 Assign Value to Segment (this function a value to a specific segment of the
combination.)
 Copy Segment Value from Code Combination (This function copies a segment
value from a given code combination to the combination that is being generated. )
 Copy Values from Code Combination (This function copies all the values from a
given code combination to the combination that is being generated )
 Is Code Combination Complete? (This function checks to see if values have been
assigned to all segments in the code combination.)
 Validate Code Combination (This function validates the code combination that has
been generated)
 Abort Generating Code Combination (This function is used to end the Account
Generator process when a fatal error occurs).
 End Generating Code Combination (This function ends the top level process of the
account generation)
 Note Every account generator (accrual, charge, budget etc..) have a sub process
that have the same main activities you will customize at

Customizations :

Prerequisites:
o MD050 Document should be prepared by Functional Consultant with the
following Considerations:
 Detailed Description for the Customization Purpose including :
 Behavior before and after customization .
 Any flexfields must be created .
 Test Cases or how to create test cases
o All functional Setup mentioned in MD050 Should be done on apps

Customization Steps:
1. Determine which account generator you should customize
(accrual , charge or budget etc.)
2. Run the original process of account generator, watch the workflow
monitor to know which process fires the default account generator.
3. Download WTF file :
 Use concurrent program to download or force WTF file
(Workflow Definitions Loader concurrent program) with the
parameter :
1. Must use SYSADMIN.
2. Parameters :
a. Mode : Download/Force
b. File : workflow path (Server Side)
c. Item type
4. Determine how the flexfield combination should be populated(from
MD050).
5. Work backwards from your desired Accounting Flexfield
combination to determine what values you need and how to obtain
them.
6. If the standard Account Generator functions are insufficient to
meet your requirements, specify additional attributes or functions
and their properties, within the Oracle Workflow Navigator
window.
7. If you find it necessary to modify the default Account Generator
processes in the Oracle Workflow Process window. you should
create a new process entirely. Which approach you take depends
on the extent of your modifications. If you need major
customizations and name it
(XX_CustomerName_DefaultProcessName), such as adding or
deleting function activities, you may want to create a new process.
If you are modifying a process that Oracle sup-plies, you should
make a backup of the .WTF file.
Naming Convention:
 (XX) before internal name
 (project name) before display name for process
 Package name xx_project-name_account generator

Delivered Files:
 WFT File
 BR120 Technical Document