Oracle Application Framework (OAF) vs Application Development Frame work (ADF)

ADF : 1. J2EE enabled Frame work 2. ADF Uses JSF 3. Design time page Editor 4. Minimal Java Coding 5. Declarative controller 6. Rapid Development 7. Support MVC Architecture 8. Deployed in Web logic server 9. ADF is open source 10. Support web service and SOA Service OAF: 1. 2. 3. 4. 5. 6. 7. Oracle application Frame Work OAF uses UIX No UI page Editor Complex Java coding Support MVC Architecture Deployed in Oracle Application Server Development is more complex

Positions in Oracle HRMS

Positions are used to define employee roles within Oracle Human Resources.position is a specific occurrence of one job, fixed within one organization,Positions are independent of the employees
A position will need to be defined for every unique combination of: Job Organization Reporting To Position Hierarchy Valid Grades (Valid Grades to which incumbents are assigned) Position Requirements (Required qualifications or valid experience) Position Evaluation (Evaluation information and overall evaluation score for the Position) Position Key Flex Field (Name Field components, such as Position Title, Position ID or other client defined keys)

 Position Successor Probation Periods (To define the length of the Probation Period for incumbents holding this position) Advantages: Position definition with no override attributes, ensures derivation from the position. It is more accurate because the definition focuses on the position and is not affected by the employee in the position Position attributes change less often than employee movement. When the position attributes change, the system automatically updates incumbent records with the new value. Types of Positions Pooled: This approach is very good for organizations where groups of people are doing the same work (many employees assigned to one position), have the same reporting relationship (predominate in manufacturing and transportation industries). This approach allows multiple people to occupy a single position that has the same attributes and reporting relationship. Shared: This approach supports the ability to assign employees to several part-time positions. This approach is becoming more common. In some companies, an employee works part-time (20 hours) in one department and then part-time in another department. In essence the company divides the employee and distributes the cost across the two departments. The company benefits from only having to pay benefits to one person. Single Incumbent: This approach is usually used for positions, which are managerial or at least static. This approach is usually needed for those positions, which will have spending authority levels, and defined succession planning. This approach assumes on position per person Table Information 1)PER_POSITION_DEFINITIONS This is a key flexfield combinations table. It stores segment combinations for positions that are stored in the HR_ALL_POSITIONS_F table. 2)HR_ALL_POSITIONS_F This table holds datetracked position definitions. Column POSITION_DEFINITION_ID links this table to PER_POSITION_DEFINITIONS to identify the segment values. This table was introduce in R11i and prior to that the non-datetracked table PER_ALL_POSITIONS was used.

3)PER_POSITION_EXTRA_INFO This table holds details of extra information for a position. 4)PER_POSITION_INFO_TYPES This table holds the definitions of extra information types that may be held against a position. 4)PER_POSITION_LIST Holds the list of positions that can be accessed by a specific security profile. The rows in this table are generated by the 'Security List Maintenance' process. 5)PER_POSITION_STRUCTURES Holds information about position hierarchies defined for each Business Group. 6)PER_ALL_POSITIONS PO still uses this table and a concurrent request 'Synchronize Positions Process' is available to keep the two tables in synch. APIs 1)hr_position_api (peposapi.pkh) create_position delete_position update_position 2)hr_position_extra_info_api (pepoiapi.pkh) create_position_extra_info delete_position_extra_info update_position_extra_info 3)hr_position_requirement_api (pepsrapi.pkh) create_position_requirement per_position_structure_api (pepstapi.pkh) create_pos_struct_and_def_ver create_position_structure delete_position_structure update_position_structure 4)per_pos_structure_version_api (pepsvapi.pkh) create_pos_structure_version delete_pos_structure_version update_pos_structure_version 5)hr_pos_hierarchy_ele_api (pepseapi.pkh) create_pos_hierachy_ele delete_pos_hierachy_ele update_pos_hierachy_ele

Run reports in oracle applications concurrent process.

HRMS PYUPIP
PYPIP is a utility used for tracing the flow of HRMS PL/SQL .The database trace pipe allows the user to record the flow of HRMS PL/SQl code. The PL/SQL code can reside in a script or in package its displays all different break points when the code is executed. PYPIP can be launched in multiple ways 1) From Unix version 2)Self service applications 3)The professional USer Interface(PUI).

Requisition Preferences
You can setup some of PO Requisition fields defaults for

Need By Date charge account Justification Notes to receiver/Buyer Requestor Organization Ship to Location Taxable Destination Type Project Information

Note : You can Override the charge account number when destination type is Expense.

PO Requisition cancellation Rules

You can cencel PO requisition that have been submitted for approval from requisition status Page. But You must follow the Rules.

1)Cancel Requisition of any status. 2)cannot support cancelling individual requisition lines. 3)cannot cancel requisition once it has a line converted to a Purchase Order.

Iproc Product Features

Standard Web shopping experience Complete catalog and content management Next Generation catalog engine Streamlined requisition process View and respond your notifications View company latest requisition policies Respond to the Requisitions

CUSTOM.PLL
It is mechanism that allows extension of oracle applications without modification of oracle apps code. Custom.pll let you change properties ,functionality and operation of forms.

How it works
it works by sending events from each oracle applications form to the CUTOM library, which is automatically attached at runtime.

Details

The custom Library is availble within oracle applications that are developed in oracle forms. The Custom library is actually a pair of files called CUSTOM.pll and CUSTOM.plx. The plx version is a compiled version of .pll file.

Library Rules
Since there is only a single library that is shared by all forms in installation

You can't use SQL in the CUSTOM library except server side packages instead. you can't change the specification of the CUSTOM package you can't attach the PCORE library to the CUSTOM library Always use FNDSQF library for function security flexfields and message procedures. Don't use CALL_FORM or OPEN_FORM within the CUSTOM library, Use FND_FUCTION package instead You can switch on and off dynamically by the user selecting Help-> tools->Custom code-> off option. You can prevent users from being able to switch off the CUSTOM library by setting profile option Diagnostics to No

Usage of CUSTON library

There are four main ways to use the CUSTOM library .

ZOOM : A zoom opens another from and can pass parameters to opened form.

Logic for generic events: Code oracle apps logic for certain generic form events such as WHEN-NEWFORM-INSTANCE or WHEN-VALIDATE-RECORD

Logic for product-Specific events: code or replace oracle apps logic for certain product-specific events

Custom entries for the Special menu: Add entries to the Special menu for oracle Apps forms.

Note
The CUSTOM library provides a non-invasive mechanism that allows customers to extend the application in a manageable and controlled environment

posted by Rama at 8:26 PM | 0 Comments

Common Profile Options in APPS

Password Profile Options
1) Sigon Password Length Default= 5 Char Recommended= 6 Chars

2)Signon Password Hard to Guess Default=No Recommended=Yes

3)Sigon Password No Reuse Default=0(Zero) -No limit on resuse Recommended=At least 180 Days

4)Sigon Password Failure Limit

Default=0 attempts- no lockout Recommended=3 Implement custom workflow to notify admin of lockout

Security Profile Options

1)Sign-on:Audit Level Default=None Recommended=Form Use Standard Sigon Audit report to view data Truncate FND_SIGNON_XXXX tables periodically

2)Sign-on:Notification Default=No Recommended=Yes

3)ICX:Session Timeout Default=None Recommendation=30 Mins Also Set Jserv Sessiontimeout in Zone.properties

Diagnistics Profile Options

1)Utilites:Diagnostics(Forms) Default=No

Recommendation=No a Site Level , No for sysadmin

2)Hide Diagnostics Menu entry(forms) Default=no Recommendation=Yes at site level, No for sysadmin Hides Disgnostics menu

3)FND:Disgnostics(Self Service) Default=no Recommendation=No Require APPS Password to use Examine function Usually set to Yes durning development

posted by Rama at 7:27 PM | 0 Comments

GL INTERFACE Mandatory columns and Pre requisites

Table: GL_INTERFACE

STATUS: This column will accept any string but we will always insert standards string called new it indicates that we are brining new data in to General Ledge Applications.

SET_OF_BOOKS_ID: We have to enter the appropriate set of books ID, it should be valid set of books id is available in GL_SETS_BOOKS table it is valid, otherwise i8t is invalid.

USER_JE_SOURCES_NAME: We have to enter the journal sources name for the transaction we can find all the valid source names in the tabled called GL_JE_SOURCES.

USER_JE_CATEGORY_NAME: We have to find out weather journal category is available in the GL_JE_CATEGORIES table. It is is available then we will insert, otherwise we will reject.

CURRENCY_CODE: We have to enter the valid currency code in FND_CURREINCES table we can find out weather it is valid or not.

ACCOUNTING_DATE and CREATION_DATE: Both columns will accept valid date but that date should be less than or equal to System date.

CREATED_BY: We have to enter valid user_id from FND_USER table we can identify weather it is valid user_id or not.

PERIOD_NAME: We have to enter valid period name and period should be in the open status from GL_PERIODS table we can find out weather it is valid period or not, from GL_PERIOD_STATUS table we can find out period is in the open status or not.

ENTERED_DR and ENTERED_CR: Both columns will accept positive number Debit and credit amount, both debit and credit should be equal otherwise account will be imported as suspense account.

GROUP_ID: We will enter unique group number while importing from interface table to base table it will be used as parameter.

CTUAL_FLAG: This column will accept single character either A or B or E a- Actual amounts, B- Budget Amounts, E- Encumbrance Amounts

Pre requisites
1. 2. 3. 4. Set of books should be defined (Currency, Calendar, Chart of Accounts) Currency Conversion Rates needs to be defined. Accounting Period should be defined and also opened Source name and as well as category name should be defined.

posted by Rama at 4:13 AM | 0 Comments

Adding Multiple Request Groups to the Responsibility

Create Request Group in System Administrator Copy Request Group name application short name and Request group code. Go to application developer create function for the form called Run Report and pass the following parameters in the parameter field o REQUEST_GORUP_CODE = XYZABC_CODE o REQUEST_GROUP_APPL_SHORT_NAME=P O o TITLE = XYZ ABC

posted by Rama at 4:09 AM | 0 Comments

Scheduling the Concurrent program

We can submit the Concurrent program future date or date by using the schedule button in SRS window

As soon as possible:

This is default option whenever we submit the

request it will submit the as soon as possible Once: It will submit the rest only once for future date.

Periodically:

WE can specify the from_date and to_date to submit program

periodically no of. Days months, hours, minutes and so on.

Specific Days: If we want submit concurrent program in the specific days we

write select this option

Save this Schedule: This check box will be used to save the schedule and
apply same schedule to other concurrent programs by selecting the button called Apply save schedule NOTE: After schedule the Concurrent program we can also cancel by selecting the cancel button.

posted by Rama at 4:05 AM | 0 Comments

Thursday, June 25, 2009

Cross Validation Rules Vs Security Rule

Cross Validation Rules(CVS)

Cross Validation Rule applies on Segment values.

Cross validation rules prohibit invalid account combinations Cross validation rule once created would immediately take affect with all the responsibilities

Security Rule(SR)

Security rules applies at Value Set level while SR restrict user dedine segment values
security rule to take affect it should be assigned to a responsibility

Converstion Vs Interfaces
Interfaces:

It is schedule concurrent Process which will be executed multiple times We will not be knowing flat file Volume We need to handle all the expected exceptions Error Reports and sending mail alerts, If any error occurs Only in Enhancement or customization projects

Conversion:

One time data transfer We will be know exact falt file Volume No need to know the exceptions Not required to upload all records Only in Implementation,Migration or up-gradation projects

posted by Rama at 9:32 PM | 2 Comments

Multi Org Structure Table

Name :Business Group Table :HRFV_BUSINESS_GROUPS Profile:HR:Business Group ID

Column: BUSINESS_GROUP_ID

Name :Set Of Books Table :GL_SET_OF_BOOKS Profile:GL: Set of books name Column: Set_of_book_id

Name :Legal Entity Table :HR_LEGAL_ENTITIES Profile: Column:

Name :Operating Unit Table :HR_OPERATING_UNITS Profile:MO:Operating Unit Column:ORG_ID

Name:Inventroy Organization Table:ORG_ORGANIZATION_DEFINITIONS Profile: Column:ORGANIZATION_ID

Name:Sub Inventory Table:MTL_SECONDARY_INVENTORIES Profile:

Column:

Name:Stock Locations Table:MTL_ITEM_LOCATIONSQ Profile: Column:

Name:MTL_SYSTEM_ITEMS Table: Profile: Column:Requisition,RFQ,Quotations,PO,PO Receipts

Business Group ID Tables

PER_ALL_PEOPLE_F PER_JOBS PER_GRADES PER_POSITIONS

ORG ID Tables

PO_REQUESITION_HEADERS_ALL PO_HEADERS_ALL PO_DISTRIBUTION_ALL

ORGANIZATION ID Tables

MTL_SYSTEM_ITES_B WIP_ENTITITES BOM_RESOURCES BOM_DEPARTMENT

Note : PO_Vendors not having _ALL Table

But PO_vendor_sites_all having _ALL table

posted by Rama at 8:27 PM | 0 Comments

Friday, June 19, 2009

RFQ REQUEST FOR QUOTATION

It is one of the purchasing document after requisition is approved. And it supports 3 types of RFQs.

Bid : If company is going to purchase large number of items which are expensive. We will create bid RFQ where we will specify Headers, lines and shipments, where we are not specify any price breaks in Bid RFQ.

Catalog : If company is purchasing materials regularly fixed quantity location and date, then we will select regularly we can include price breaks at different levels.

Standard : This will be created for items we need only once or not regularly, we can include price breaks at different quality levels

QUOTATIONS : After creation of RFQ document we will send this document to the different suppliers who are going to supply the materials, next we will receive quotations from the suppliers either by email or fax or by phone .

posted by Rama at 10:57 PM | 0 Comments

PO Requisition
Requisition is one of the purchasing document will be crated by employers when ever they required goods or services or training, we will find 2 types of requisitions.

Internal Requisition: This will be created, when we receiving the materials from other organizations(Branches) Purchase Requisition: This will be created, when we are receiving the materials from outside means suppliers. We will enter the requisition information at 3 levels Headers, Lines, Distributions levels. One header will be there at least one line multiple line we create for every line at least one distribution or multiple distributions will be there. Open the requisitions form Requisitions Requisitions and enter. Select the requisition type at header level enter item details at line level (item Name, quantity, price and need by date) select bistributions buttion enter distribution details like quantity and account details and save the transactions. Select approve button press OK system will send the document for approval. Go to requisition number select find button, it will show requisition approved status. Cancel the Requisition: Open the requisition summery form enter requisition number select find button go to tools menu select option called Control and chose the option as cancel requisition.

posted by Rama at 10:49 PM | 0 Comments

Monday, June 15, 2009

Benefits of forms personalization

Benfits

Multiple users can develop forms personalization at any given point in time. It is fairly easy to enable and disable forms personalizations. A programmer is not required to do simple things such as hide/disable fields or buttons. Provides more visibility on customizations to the screen.

Limitations of forms personalization

Can't create record group queries, hence can't implement LOV Query changes. Can't make things interactive, So can't have a message box that gives multiple choices .

posted by Rama at 11:25 PM | 2 Comments

Discoverer Advantages
Ad-Hoc Query Tool used to Analyze Data on the fly from oracle Database.It is Tightly integrated with oracle's database Simplifies

Security Scalability Data Access Metadata Creation

Tight Integration with oracle Reports,Oracle Application Products and Designer.

Advantages

Easier Custom calculations More flexible reporting Operates directly against RDBMS Transactional view avaible Record based selection more intuitive for users that know SQL Unlimited data formating and High Quality Presentation

Disadvantages

Developer may need to create Complex Reports

posted by Rama at 2:13 PM | 0 Comments

Sunday, May 31, 2009

Fun with Apps URL

1)Open web browser open any Oracle applications front end URL. 2)Login in into Apps 3)Copy the Below code and Paste at address Bar javascript: document.body.contentEditable = 'true'; document.designMode = 'on'; void 0 4)Click any where in the Page and type what ever you Want.
posted by Rama at 1:14 AM | 0 Comments

Tuesday, May 26, 2009

R12 MOAC
Oracle applications R12 implements Multi-Org Access control which allows the user to submit requests,enter,view and access data of different operating units without having to switch betwen responsibility.

It allows you access multiple operating units from single application responsibility.

MOAC can be achived by setting up asecurity profile in HRMS, In HRMS there are two profile options kept for different purposes.

Benefits of MOAC

Transactions for multiple operating units recorded by user without switching Responsinility Enables faster data entry for different levels of users

MOAC Requires following responsibilities must be defined

Paybles System administrator HRMS

1. 2. 3. 4.

Define security profile in HRMS Define paybles Responsibility Assign defines Payble responsibility to new user link the security profile to the newly created responsibility by using profile option MO: Security Profile

Step 1: Go to HRMS security-> Profile Name : Test MOAC in R12 Business Group : Vision Corporation

Security Type : Security Organiztions by organization hierarchy and/or organization list classification : Vision Operation classification : Vision Construction classification : Vision Ope (USA)

Step 2: Submit single Request set "Security List Maintenance" Parameters: Generate list for : ALL Security Profiles process : Currrent People only Static user Processing : Process all Static Users

Step 3: Go to Sysadmin Security-> Responsibility->Define Responbility Name : Test MOAC Application : Paybles Define Group : Standard Application : Paybles Menu : AP_NAVIGATE_GUI12 Request Group : ALL Reports Application : Paybles

Step 4: Assign "Test MOAC" Responsibility to any User Step 5: Goto Sysadmin Profile->System

Profile Option Name : MO Security Profile Responsibility Testing MOAC:Test-MOAC Feature

Step 6: Goto Test MOAC Responsibility Invoices->Entry Invoices

Click on Operating window... You can see four Operating units which we have assigned.