Difference between Party and Customer

Muhammad Rafi Aamiri Madani on Tuesday, December 15, 2009

PARTY CUSTOMER

Prospective Customer and more relevant for CRM Purposes

A Customer which is used both in CRM as well as in OM, Financials or any other module Example (A Sales Order in OM or Invoice in Receivables cannot be created without creating a Customer record for the Party).

No Business Transactions involved (Sales Order, Sales Invoice, Debit Memo, Credit Memo, Receipt etc.,)

A Business Transaction like a Sales Order, Invoice, Debit Memo, Credit Memo,Receipt can be created.

A Party does not have account but have Sites A Customer will have account and as well as Sites.

A Party can exist without Customer RecordA Party record is must to create a Customer Record linked through party_id.

A Party Record will not have record in following tables

    HZ_CUST_ACCOUNTS    HZ_CUST_ACCT_SITES_ALL    HZ_CUST_SITE_USES_ALL    HZ_CUST_ACCOUNT_ROLES    HZ_CUST_ACCT_RELATE_ALL

A Customer Record will have records in following tables

    HZ_CUST_ACCOUNTS    HZ_CUST_ACCT_SITES_ALL    HZ_CUST_SITE_USES_ALL    HZ_CUST_ACCOUNT_ROLES    HZ_CUST_ACCT_RELATE_ALL

     with reference to party_id column.

Posted by Muhammad Rafi Aamiri Madani

Reina van Ewijk said...

Clear explanation. In addition to this: Some relevant tables for parties:HZ_PARTIES, HZ_LOCATIONS (addresses), HZ_PARTY_SITES (linking the locations with the parties), HZ_PARTY_USG_ASSIGNMENTS.

In R12 Suppliers (and supplier contacts), Banks and Legal Entities are also captured in the Party tables.

September 2, 2011 at 12:08 PM

APPS Interfaces

Muhammad Rafi Aamiri Madani on Tuesday, December 29, 2009

In terms of oracle applications interface is a communication channel that allows the data to move in and out of the

system.

TYPES

INBOUND INTERFACES

    The one which allows data to get into oracle application from outside is called inbound interface.

OUTBOUND INTEFACES

    The one which allows data to get data from oracle applications to other systems is called outbound interface.

TYPES OF INBOUND INTERFACE

Open interfaces  -

API  (Application Program Interface)

EDI (Electronic Data interchange) 

    Mainly used for automation transactions with third party systems

XML GATEWAY

    Mainly used for automation transactions with third party systems

WEBADI

    Used for uploading data from excel with the scope to have some validations mainly used for one time loading.

PLSQL Packages for Reading XML Data

    Use this in case of importing non standard transactions

TYPES OF OUTBOUND INTERFACE

Custom programs where we pull data to a csv file using UTL_FILE in the required format

EDI

XMLGATEWAY

PLSQL Packages for generating XML

DIFFERENCE BETWEEN OPEN INTERFACE & API

OPEN INTERFACE

In case of open interface the data is loaded in to open interface table like GL_INTERFACE or Sales Order

Interface(OE_ORDER_HEADERS_IFACE_ALL).

Run the interface import program.

This will validate the data and put it into oracle applications. All the invalid records are marked as Error.

One thing is there are GUI Screens available for most of these interface where you check the error message correct it

there only and resubmit the interface.

From the technical perspective there are Error tables available for each interface

API

API's are the oracle built packages where the validation logic is wrapped inside a package and the data is passed as

parameters to the API.

Most of these api's use the PLSQL tables as parameters to take the advantage of bulk binding concepts for faster

loading data.

They will have the two OUT parameters to throw back the error code and message in case of data validation failure

APIs are comparatively faster than open interfaces.

If a API's and open interface are available it is better to load through API's.If the records are more...

Posted by Muhammad Rafi Aamiri Madani

FRM-40654: Record has been updated ..... ???

Muhammad Rafi Aamiri Madani on Thursday, January 14, 2010

Very common problem occurs in Forms is  

"FRM-40654: Record has been updated by another user. Re-query to see change"

Cause:  Another user has updated this record since you performed a query and has changed at least one field in the

record. Your actions have not changed the record in memory.

Action:  You can update or delete this record now only if another user has restored the field values back to the way

they were when you performed the query. Otherwise, you must re-query to fetch and display the new record into the

form before you can update or delete it.

This is very common issue after migration or with any external interfaces, If you have taken care by TRIM function ,

then there is nothing to bother, else your end user will report this, which need a proper investigation.

Reason & Resolution

This error is caused because of any of the following

1. FRM-40654 Caused by unnecessary foreign key fields

2. Trapping problem of some sort in Oracle Forms with triggers, execute_query

3. Record locked ie Another user changed the record and saved after you queried the record

4. Some of the columns have trailing spaces, and Forms by default truncates the trailing spaces and hence the

database value and form value will not match and you get the error.

5. Date field stored in database is with time stamp but form showing only Date component and hence Form

value and database value will not match and hence you get the error. 

(you need to remove the time component in DB or show date time in Form)

Bottom line is the value in Database and value in form are not matching, so you have to check for each column and

see where is the difference. 

I know this is going to be painful checking out every field for changes, but there is no other options left.

What you have to do is to investigate the column first and then make a update with TRIM function as

update <table name>

set <column name> = trim(<column name>);

Resolutions Example

Example 1

User reported the problem at suppliers site,

Taking which table hold the supplier data.

Check a column value for a VARCHAR2 column. In this case VENDOR_SITE_CODE. or Address_line1

SELECT '['||vendor_site_code||']'

FROM po_vendor_sites_all

WHERE vendor_id=<VENDOR ID>;

Once you get the column , then use update script, with TRIM function, like

UPDATE po_vendor_sites

SET vendor_site_code = TRIM(vendor_site_code)

WHERE vendor_id = <VENDOR ID>;

Example 2 

Your bank statement Reconcile program ending up with error

In similar way you have to check like

1. select '['||trx_text||']' from ce_statement_lines_interface;

2. select '['||trx_text||']' from ce_statement_lines;

The above mentioned scripts need to be run against all varchar2 columns, not just trx_text, in either

ce_statement_lines or ce_statement_lines_interface.

If trailing spaces are found, run the following scripts to correct them:

update ce_statement_lines_interface

set trx_text=trim(trx_text,' ')

Change the column and table name to those with trailing spaces

Example 3

Invoice Through Auto invoice (External system)

Same way to find the column and apply by this kind of script

update ra_customer_trx_lines_all

set DESCRIPTION = trim(DESCRIPTION) ,

SALES_ORDER = trim(SALES_ORDER)

where customer_trx_id = <customer trx id>;

What if , not have "trailing space" Problem

Confirm with DBA , is table is having any lock or not . If still the problem exists raise SR and apply the script

provided.

Tips of Developing Conversion and Interface

Always use TRIM function in your insert statement of the program

Posted by Muhammad Rafi Aamiri Madani

Create READ ONLY Responsibility

Muhammad Rafi Aamiri Madani on Monday, January 25, 2010

ORACLE RECOMMENDED SOLUTION

AAIdentify the menu that is attached to the GL super user and Payables manager. 

AAIdentify the form functions that are attached to this menu. 

AANow create a new form function exactly similar to the standard one but with the option

aaaaQUERY_ONLY="YES" in the location 

    a Sysadmin  application  function  Form  Parameter. 

     This makes the function read only. 

AANow create a new menu with these read-only functions and attach the menu to a new responsibility which is

aaaaassigned to users who need to have read-only privileges. 

CREATE READ ONLY DATABASE USERS

aaaCreate a Database user apps_readonly 

aaaGrant all the objects/synonyms from apps to apps_readonly 

aaaCreate synonym for all the apps objects in apps_readonly 

aaaIn Oracle apps, register apps_readonly as a user and Datagroup (Similar to apps) 

aaaCreate responsibilities (similar to apps) but attach to apps_readonly datagroup created in Step 4. 

CUSTOM.PLL

aaaCreate read-only responsibilities follow naming convention, all of them should end with same string

aaaae.g. "Read Only". 

aaaExtend custom.pll to prevent save function if user responsibility ends with "Read Only".

Posted by Muhammad Rafi Aamiri Madani

CUSTOM.pll

Muhammad Rafi Aamiri Madani on Wednesday, February 3, 2010

The CUSTOM.pll library is a standard Oracle Forms PL/SQL library that is supplied by Oracle with the Oracle

Applications. This is Oracle's built-in feature that allows the customer to enhance the standard functionality of the

Applications by implementing site-specific business rules. Every Oracle Forms -based eBusiness screen, and any

custom form developed using the Oracle Application development standards, will access the CUSTOM library. This

makes an ideal point of creating business rules that effect the entire organization. This is the only method of forms

enhancement whose functionality is supported by Oracle World Wide Support. Although any enhancements coded by

the customer are not directly supported by Oracle World Wide Support.

Use the CUSTOM Library

Since the CUSTOM library is a typical Forms PL/SQL library, it can include standard PL/SQL logic, Oracle Forms

built-in commands and may have other Forms PL/SQL libraries attached to it. The base CUSTOM library is located in

the $AU_TOP/resource directory on your forms server. Explore the CUSTOM.pll using the Oracle Forms Designer

module to examine the sample code that exists in library. Once any enhancements are made, the library must be

generated into an executable library (CUSTOM.plx) that then can be used by the Oracle Applications Forms runtime

module. Since the CUSTOM library is loaded once for a given session, a user must log out of the application and

sign-on again before any changes will become apparent. It is suggested that you also place a copy of the CUSTOM

library in your customization directory as a safety precaution.

The CUSTOM PL/SQL library does have its limitations. It cannot contain SQL commands. It cannot have certain

Oracle Applications Forms global libraries attached to it (such as APPCORE). The CUSTOM library is designed to be

used solely with the Oracle eBusiness Applications and does not support the Oracle Self-Service Web Applications

(OSSWA). Since the CUSTOM library's standard location is in the $AU_TOP/resource, it can be overwritten during

an upgrade of the Applications.

Once enhancements are implemented, the CUSTOM library is accessed by the Oracle Applications based upon

'events'. The 'events' define the occasions when the Applications will look into the CUSTOM library for additional

code to execute.

Some events are generic:

WHEN-NEW-FORM-INSTANCE Initially entering a formWHEN-NEW-BLOCK-INSTANCE Entering a zone (or block) within a formWHEN-NEW-ITEM-INSTANCE Moving into a new field within the formWHEN-NEW-RECORD-INSTANCE Creating a new recordWHEN-FORM-NAVIGATE Navigating thru a form using the mouseWHEN-VALIDATE-RECORD Saving (committing) the information to the database

EXPORT Triggered by using the Export feature

Some events are field specific

ZOOM – Pre -11 feature for moving to another form and querying up specific records

Some events are form specific

SPECIALn - (where n is a number between 1 and 45) used to generate entries in the 'Special' menu of the tool bar

and the code is triggered by selecting a menu choices

from the 'Special' option on the toolbar

KEY-Fn – (where n is a number between 1 and 8) triggered by pressing the corresponding function key

Some events are application specific

Application Object Library

WHEN-LOGIN-CHANGED Initially entering a form

WHEN-RESPONSIBILITY-CHANGED Entering a zone (or block) within a form

WHEN-PASSWORD-CHANGED Moving into a new field within the form

These are most of the documented events. Discussions from previous OAUG conferences suggest that many more

events are passed to the CUSTOM.pll. The method used to find these events would be to create a generic piece of

code to display the event name as it passes thru the CUSTOM library. The PL/SQL logic within the library can be

organized by these events and then all effected forms or by form and then all effected events. The Oracle

development standard is to group forms logic within a specific event. This is a good solution if many forms are

affected by the same event. Another development standard is to organize the logic by form and then specific events.

This is a good solution if limited forms are affected by several events.

The CUSTOM library can be used to enforce business rules, secure standard features of the Oracle Applications

(eliminate or restrict their use), and enforce naming standards. Business rules can be enforced by adding logic that

will be executed when a user attempts to save a record. The business rules can be as simple as determining that a

user has the authority to perform the actions or that certain data has been entered or as complex as limiting field

access and display based upon a user's security level. All of these items can be coded using PL/SQL logic and

Forms built-in features. Since the CUSTOM library cannot contain SQL commands, that type of logic must be passed

off to stored procedures or functions within the Oracle database.

This section of code looks for the event 'WHEN-NEW-FORM-INSTANCE' when the user is in the PO Supplier form

(APXVDMVD). It then executes a custom stored PL/SQL function (FMS_USER_HAS_RESP) to determine if the user

has the proper authority to update the supplier information. If the user is in the Site portion of the form, then the

custom procedure FMS_WHEN_NEW_ITEM_SITE is executed to allow or disallow changes to the Supplier Site

information.

IF event_name = 'WHEN-NEW -FORM-INSTANCE' THEN

If (form_name = 'APXVDMVD') THEN

v_user_id := fnd_global.user_id;

v_site_maint_ok := FMS_USER_HAS_RESP(v_user_id, 'Purchasing Vendor Site Maint');

If (block_name = 'SITE' ) THEN

FMS_WHEN_NEW_ITEM_SITE(v_site_maint_ok, v_new_record);

End if; -- BLOCK=SITE

End If; -- FORM=APXVDMVD

END IF;

Standard Oracle Application features can be secured or eliminated using standard Oracle Forms built-in features. A

form button can have its logic disabled and even be removed from display by altering the button's characteristics.

This section of code hides the unreserved fields on the Purchase Order form (POXPOEPO) when the user first

accesses the form (WHEN-NEW-FORM-INSTANCE event).

IF event_name = 'WHEN-NEW -FORM-INSTANCE' THEN -- SECURE STANDARD ORACLE FEATURE

-- Turn off the Reserve/Unreserve functionality

If form_name = 'POXPOEPO'

And block_name = 'PO_APPROVE' then

SET_ITEM_PROPERTY('PO_APPROVE.UNRESERVE',DISPLAYED,PROPERTY_FALSE);

SET_ITEM_PROPERTY('PO_APPROVE.UNRESERVE_DATE',DISPLAYED,PROPERTY_FALSE);

End If;

END IF;

Since the event logic can be limited specifically to a given form and even a specific zone within a form, it is possible

to create validation logic that can enforce naming standards and data entry standards for a type of transaction. One

of the samples in the CUSTOM library provides logic to force a supplier's name to be uppercase. This code changes

the properties of several columns on the Purchase Order form to force uppercase data entry when the purchase

order type is 'CONTRACT'. Notice that logic is required to reset the column properties for other purchase order types.

IF event_name = 'WHEN-NEW -FORM-INSTANCE' THEN

If form_name = 'POXPOEPO' THEN

-- Code to set the item properties for contract documents to Uppercase and Required.

If (block_name = 'PO_HEADERS'

And name_in('PO_HEADERS.TYPE_LOOKUP_CODE') = 'CONTRACT') THEN

SET_ITEM_PROPERTY('PO_HEADERS.COMMENTS',CASE_RESTRICTION,UPPERCASE);

SET_ITEM_PROPERTY('PO_HEADERS.START_DATE',REQUIRED,PROPERTY_TRUE);

SET_ITEM_PROPERTY('PO_HEADERS.END_DATE',REQUIRED,PROPERTY_TRUE);

SET_ITEM_PROPERTY('PO_HEADERS.AMT_LIMIT_DSP',REQUIRED,PROPERTY_TRUE);

Else

-- Code to set the item properties for NON contract documents to Uppercase and NON Required.

SET_ITEM_PROPERTY('PO_HEADERS.COMMENTS',CASE_RESTRICTION,UPPERCASE);

SET_ITEM_PROPERTY('PO_HEADERS.START_DATE',REQUIRED,PROPERTY_FALSE);

SET_ITEM_PROPERTY('PO_HEADERS.END_DATE',REQUIRED,PROPERTY_FALSE);

SET_ITEM_PROPERTY('PO_HEADERS.AMT_LIMIT_DSP',REQUIRED,PROPERTY_FALSE);

v_doc_type := name_in('PO_HEADERS.TYPE_LOOKUP_CODE');

END IF;

END IF; -- Form = 'POXPOEPO'

END IF;-- EVENT=NEW –FORM

During the conference presentation, these examples and others will be discussed in more detail and shown in the

entire context of the CUSTOM.pll library.

Suggestions and Tips

To safeguard against accidental loss of your personalized CUSTOM library, place a copy in your customizations

directory forms subdirectory. If you wish to execute the CUSTOM library from within your customization directory, you

will need to add your customization forms directory path to the beginning of the FORMS60_PATH o/s variable. This

method will find your personalized version first and execute it instead of the standard version located in the

$AU_TOP/resource directory. To discover any hidden events that may be passed into the CUSTOM library, you could

add a section of code to display the event name. Caution: since everyone that accesses the Applications will use the

CUSTOM library, limit this experiment to off-hours or to limited use instances.

Posted by Muhammad Rafi Aamiri Madani

R12 Table Naming Convention

Muhammad Rafi Aamiri Madani on Monday, February 8, 2010

  _ALLTable holds all the information about different operating units. Multi-Org environment. You can also set the client_info to specific operating unit to see the data specific to that operating unit only.

  _TLTables corresponding to another table with the same name minus the _TL. These tables provide multiple language support. For each item in the table without _TL there can be many rows in the _TL table, but all with different values in the LANGUAGE column.

  _BThese are the CORE BASE tables. They are very important and the data is stored in the table with all validations. It is supposed that these table will always contain the perfect format data. If anything happens to the BASE table data, then it is a data corruption issue.

  _F

These are date tracked tables, which occur in HR and Payroll. For these there are two date columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE which together with the PK identifies a row uniquely. The date intervals cannot overlap. Many think they are Secured data. Guess someone from Oracle confirms.

  _V Tables are the views created on base tables

  _VLViews for multi language tables which combines the row of the base table with the corresponding row of the _TL table where the LANGUAGE = USERENV('LANG').

  _S Sequences, used for finding new values for the primary key of a table.

  _A Audit Shadow Tables

  _AVN Audit Shadow Views

  _ACN Audit Shadow Views

  _MRC_VMRC (Multiple Reporting Currency) is supported by the following Oracle Applications - Oracle Assets,Oracle Cash Management, Oracle Cost Management,  Oracle General Ledger, Oracle Global Accounting Engine, Oracle Payables, Oracle Receivables, Oracle Purchasing, Oracle Projects

Posted by Muhammad Rafi Aamiri Madani

Discoverer Plus not opening

Muhammad Rafi Aamiri Madani on Saturday, February 20, 2010

If you find that Discoverer Plus won't start (or the Discoverer Plus windows doesn't appear) after downloading the

Java Applet, or if you're having issues with JInitiator with Oracle Applications, then it could be that you have multiple

versions of Java required. For your Oracle Discoverer Plus, Oracle JInitiator Java Plugin (JVM), or other Java based

software multiple versions of Java can cause conflicts, so try the following steps. Actually I'd recommend any rollout

of the Disco Plus or EBS client include the below steps!

1. Allow multiple concurrent versions of Java to run by enabling Secure Static Versioning.

Update or Create the following Windows registry entry on your desktop client as follows;

1. If the 'Java Deployment' and 'Policy' folders do not exist under your HKEY LOCAL MACHINE ->

SOFTWARE -> JavaSoft entry in your registry you will first need to create these folders as follows;

2. Right mouse click on the JavaSoft folder in your registry and from the menu select 'New -> Key'. Name the

new folder 'Java Deployment'. Open this folder and create another folder named 'Policy' underneath it, then

follow the rest of the steps below.

3. Go to 'HKEY LOCAL MACHINE -> SOFTWARE -> JavaSoft -> Java Deployment -> Policy' in your Windows

registry

4. Right mouse click on the Policy folder and from the menu select 'New -> DWORD Value'

5. Right click on the newly created value and rename it to - 'EnableSecureStaticVersioning'

6. The Data value should remain at the default of '0x00000000 (0)'

2. Switch off automatic updates of Java.

It is advisable to turn off the automatic upgrade facility for the desktop client JRE. This will ensure that newer versions

of the JRE plug-in are not installed, and used with Oracle E-Business Suite / Oracle Discoverer unknowingly. This

feature can be turned off as follows;

1 From the 'Start Menu', select 'Control Panel'

2 Double click the 'Java' icon

3 Select the 'Update' tab

4 Uncheck the 'Check for Updates Automatically' box

5 Click the 'Never Check' button on the 'Java Update -Warning' pop up window

6 Click 'OK' to close the 'Java Control Panel'

Posted by Muhammad Rafi Aamiri Madani

APPS Data Model

Muhammad Rafi Aamiri Madani on Wednesday, February 24, 2010

APPS Schema

When we install Oracle Database by default system will creates SYS and SYSTEM schemas. These consist of all

Data Dictionary Tables. Like this if we install Oracle Applications System will automatically creates schemas of all

Modules (i.e. GL, AR, AP, etc.) with the respective module name as User and Password. Along with these schemas

some special Schemas i.e. APPS, APPLSYS, APPLSYSPUB will be created for special purpose.

APPS Schema

It is Public Schema. It consists of a collection of public synonym of all the objects of all the schemas in the Application

database.

All the Procedures, Functions and Packages created must be stored in this Schema.

APPLSYS Schema

This is a special Schema consists of the files starts with FND, ALR, WF and AD.

APPLSYSPUB Schema

This schema is a collection of public synonyms of all FND Tables, which are used for User verification. This is the

Gate Way User ID of Oracle Applications.

Note:

1. When we are changing the APPS Schema password, first we have to change in the backend for both APPS and

APPLSYS Schemas.

2. Password for both APPS and APPLSYS should be same.

3. Change the password of both the Schemas in Front‐End and Back‐End.

4. Drop the Concurrent Manager Services and re‐create the Concurrent Manager Service with the Password as

APPS Password.

Posted by Muhammad Rafi Aamiri Madani

Open Interfaces for Data Migration

Muhammad Rafi Aamiri Madani on Wednesday, February 24, 2010

Oracle General Ledger

• Budget Upload 

• Importing Journals 

• Loading Daily Rates 

Oracle Payables

    • Credit Card Transaction Interface Table 

    • Invoice Import Interface. This interface is no longer supported for importing invoices.

……..Use the Payables Open Interface instead. 

    • Payables Open Interface 

    • Purchase Order Matching 

Oracle Receivables

    • AutoInvoice 

    • AutoLockbox 

    • Customer Interface 

    • Sales Tax Rate Interface 

    • Tax Vendor Extension 

Oracle Assets

    • ACE Interface 

    • Budget Open Interface 

    • Mass Additions Interface 

    • Production Interface 

    • Physical Inventory 

Oracle Cash Management

    • Bank Statement Open Interface 

    • Forecasting Open Interface 

    • Reconciliation Open Interface 

Oracle Purchasing

    • Requisitions Open Interface 

    • Purchasing Documents Open Interface 

    • Receiving Open Interface 

Oracle Inventory

    • Customer Item Interface 

    • Open Item Interface 

    • Open Replenishment Interface 

    • Open Transaction Interface 

    • Cycle Count Open Interface 

    • Reservations Open Interface 

    • Move Orders Open Interface 

Oracle Projects

    • Activity Mangement Gateway 

    • Client Extensions 

    • Transaction Import

Posted by Muhammad Rafi Aamiri Madani

Overview of Oracle Inventory

Muhammad Rafi Aamiri Madani on Monday, March 1, 2010

Oracle Inventory is core module of entire Oracle e-business suite, this module shares the information with almost

every other module. Oracle Inventory let you define the Items and it is backbone of all inventory transactions.

Functionality provided by Oracle Inventory

Item Master

Item setup is critical part of Oracle ERP implementation. Item setup is required to place purchase orders, receive &

transact inventory, to enter sales orders, ship goods/services to customer. Items are first setup in master inventory

organization and same can enabled in every other inventory organization where it needs to transact. Item attributes

are different flags that determine the characteristics of items. Item attributes determine whether item is procured item,

saleable item, service item etc. 

Inventory transactions

Inventory holds the onhand quantities and transactions that can cause onhand changes. Transactions originated from

other modules (Shipping - customer shipments, Purchasing - Receiving goods into stock etc) are finally transferred to

Inventory. Every transaction is associated with a transaction type, source, Item, quantity, unit of measure and

additional attributes. Oracle provides many seeded transaction types and you can add custom transaction types as

needed for accurate reporting.

Examples of Inventory transactions

       Subinventory transfers

       Miscellaneous issue/receive

       Account Alias issue/receive

       Move order issue

       Sales order shipment

Serial & Lot control Its provides detail tracking of onhand and related inventory transactions. Lot number and serial

number are critical requirements in a regulated environment like pharmacuetical, food processing industries. In case

of any recalls lot/serial control provides tracing the current location of goods.

Inventory Planning

Oracle Inventory planning provides good planning methodoligies for indirect item purchases, MRO kinds of items

while MRP (Material Requirements Planning) as planning method is still preferred for direct material. MRP

functionality is delivered through Oracle MRP/SCP module. Widely known inventory planning methods are Reorder

planning & Min-max planning, lets understand little bit more about these methods.

Reorder Point Planning (ROP) ROP uses Supply (onhand + expected receipts) and safety stock information to plan

the re-order quantity. When supply falls below safestock a replenishment order is created considering the lead time

and economic order quantity.

Min-Max Planning This planning method is bit different from ROP, The replenishment order is created when onhands

falls below the minimum level set at the item. 

Periodic Inventory verification methods

It is very important to have systematic onhand match with actual physical onhands for data accuracy and efficient

planning purpose. Oracle Inventory provides two onhands verification and rconcialiation methods called Physcial

Inventory and Cycle counting.

Physical Inventory It is an activity where 100% of onhand is physically verified and reconciled with system onhand.

Typically this is done once a year or twice based on business needs. When physical inventory in progress typically all

other operations will be on hold. Any differences in physical and systematic onhands are adjusted and approved in

system and matched with physical onhand quantity.

Cycle counting It is a periodic counting process instead of onetime process like physical inventory. In cycle couting

items are classified into ABC classes (high, medium, low value items). High value items are verified more frequent

than low low value items. System generates the schedule of items that need to be counted and verified.

Posted by Muhammad Rafi Aamiri Madani

Preference in APPS Start Page

Muhammad Rafi Aamiri Madani on Friday, December 18, 2009

"Applications Start Page" feature provides a user an option to set a particular page as his/her preferred start. The

user will be taken to this page at login. 

A user can choose from the set of functions available under his/her responsibilities. The value is recorded in a profile

option named "Applications Start Page (APPLICATIONS_START_PAGE)" as

"functionId$$$respId$$$appId".

Usage of the Feature

žMake sure the profile "Self Service Personal Home Page Mode" is set to "Framework only" at site level or at user level for which user you intend to provide "Applications Start Page" feature

   ž Login to Applications as the End user   ž Navigate to Preferences link on top of the page.

   

žYou can find a section "Start Page" under General Preferences page.  Select the Responsibility from which you would like to choose the Function (For e.g. Payables Super User). It then lists the functions available for this user under this responsibility.  Choose the Function as Start page (e.g, Invoices). Apply the changes.

   ž Logout and Log back in. Your Start Page is now effective.

After personalizing the 'start page' to directly open a Form, how do I reset the User Preferences and the start page?

Disabling the Feature

žWhen you are on Self-service Framework page, you can Navigate to Preferences Link and de-select the values (choose blank) for Responsibility and Page drop down lists.

   ž When you are in Forms based Applications, navigate to menu  Edit => Preferences => Profile   ž Search for "Applications Start Page", remove the value from User Value field and Save.   ž Next time when you login to Applications, you get Self-service Framework Homepage.

OR

After logging in, replace the login link with:

http://<initial part of path>/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE

This should get you to the Personal Home Page.

OR

Either use the Responsibility Hat to change to the System Administrator responsibility or Login as another user

and have them use the System Administrator responsibility.

Then do a find for the Start Page profile option: Profile > System  for the User Name that is needing to reset their

'Start Page' profile.

Delete the start page for the user, save the changes. This will allow the user to get back to the Personal Home Page,

and then they can reset their 'Start Page'.

Posted by Muhammad Rafi Aamiri Madani

Definition of AIM Methodology

Muhammad Rafi Aamiri Madani on Tuesday, December 22, 2009

Application Implementation Method is a proven approach for all the activities required to implement oracle ERP

applications.

The scope of the AIM is focused on an enterprise as a whole. There are eleven processes of implementation.

1. Business Process Architecture [BP]

This phase outlines:

ž Existing business practicesž Catalog change practicesž Leading practicesž Future practices

2. Business Requirement Definition[RD]

This phase explains about the initial baseline questionnaire and gathering of requirements.

3. Business Requirement Mapping[BR]

In this phase the requirements of business are matched with the standard functionality of the oracle applications.

4. Application and Technical Architecture [TA]

This outlines the infrastructure requirements to implement oracle applications.

5. Build and Module Design [MD]

This phase emphasizes the development of new functionality (customization) required by the client. It mainly details

how to design the required forms, database and reports.

6. Data Conversion [CV]

Data Conversion is the process of converting or transferring the data from legacy system to oracle applications.

Ex. Transferring customer records from the legacy to the Customer Master.

7. Documentation [DO]

Documentation prepared per module that includes user guides and implementation manuals.

8. Business System Testing [TE]

A process of validating the setup's and functionality by QA(functional consultant) to certify status.

9. Performance Testing [PT]

Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background

process, database performance, etc…

10. Adoption and Learning [AP]

This phase explains the removal of the legacy system and oracle application roll out enterprise wide.

11. Production Migration [PM]

The process of "decommissioning" of legacy system and the usage(adoption) of oracle application system.

Posted by Muhammad Rafi Aamiri Madani

Payroll Table Name and Description

Muhammad Rafi Aamiri Madani on Friday, November 13, 2009

Table Name Description

PAY_ACCRUAL_BANDS Length of service bands used in calculating accrual of paid time off.

PAY_ACCRUAL_PLANS PTO accrual plan definitions, (Paid time off).

PAY_ACTION_CLASSIFICATIONS Payroll Action Type classifications.

PAY_ACTION_CONTEXTS Assignment Action Contexts.

PAY_ACTION_INFORMATION Archived data stored by legislation

PAY_ACTION_INTERLOCKS Assignment action interlock definitions to control rollback processing.

PAY_ACTION_PARAMETERS Global parameters to control process execution.

PAY_ACTION_PARAMETER_GROUPS Groups of Pay Action Parameters

PAY_ACTION_PARAMETER_VALUES Values for the specified action parameters

PAY_AC_VENDOR_MAPPINGSNorth American Table to control the mapping of internal Values to External Vendor Values

PAY_ALL_PAYROLLS_F Payroll group definitions.

PAY_ASSIGNMENT_ACTIONSAction or process results, showing which assignments have been processed by a specific payroll action, or process.

PAY_ASSIGNMENT_LATEST_BALANCES Denormalised assignment level latest balances.

PAY_ASSIGNMENT_LINK_USAGES_FIntersection between PAY_ELEMENT_LINKS_F and PER_ALL_ASSIGNMENTS_F.

PAY_AU_MODULESDefines the processes that can be executed by the generic code caller.

PAY_AU_MODULE_PARAMETERSDefines the parameters associated with the module used in the generic code

PAY_AU_MODULE_TYPES Defines the module types used in the generic code caller

PAY_AU_PROCESSESThis table defines the processes that can be executed by the generic code caller.

PAY_AU_PROCESS_MODULESDefines the intersection between processes and modules used by the generic code caller.

PAY_AU_PROCESS_PARAMETERS Defines the parameters for a process.

PAY_BACKPAY_RULES Balances to be recalculated by a RetroPay process.

PAY_BACKPAY_SETS Identifies backpay, or RetroPay sets.

PAY_BALANCE_ATTRIBUTES Holds mappings between attributes and defined balances.

PAY_BALANCE_BATCH_HEADERS Batch header information for balance upload batch.

PAY_BALANCE_BATCH_LINES Individual batch lines for the balance upload process.

PAY_BALANCE_CATEGORIES_F Holds seeded categories for balances.

PAY_BALANCE_CLASSIFICATIONS Information on which element classifications feed a balance.

PAY_BALANCE_CONTEXT_VALUES Localization balance contexts.

PAY_BALANCE_DIMENSIONS Information allowing the summation of a balance.

PAY_BALANCE_FEEDS_F Controls which input values can feed a balance type.

PAY_BALANCE_SETS Allows related balances to be grouped for reporting purposes.

PAY_BALANCE_SET_MEMBERS Individual members of the balance set

PAY_BALANCE_TYPES Balance information.

PAY_BALANCE_TYPES_EFCThis is a copy of the PAY_BALANCE_TYPES table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_BALANCE_TYPES_TL Translated balance type definitions

PAY_BALANCE_VALIDATION Balance Validity information

PAY_BAL_ATTRIBUTE_DEFAULTS Balance attribution defaulted according to values in this table.

PAY_BAL_ATTRIBUTE_DEFINITIONSBalance attributes help to identify which balances should be usedin which reports.

PAY_BANK_BRANCHES Stores bank branch information to enable entry of bank account

details with the correct branch information (e.g. GB bank, sort code, branch).

PAY_BATCH_CONTROL_TOTALSHolds user defined control totals for the Batch Element Entry process.

PAY_BATCH_HEADERS Header information for a Batch Element Entry batch.

PAY_BATCH_LINES Batch lines for a Batch Element Entry batch.

PAY_CALENDARS Details of user defined budgetary calendars.

PAY_CA_EMP_FED_TAX_INFO_F Canadian federal tax information

PAY_CA_EMP_PROV_TAX_INFO_F Canadian provincial tax information

PAY_CA_FILE_CREATION_NUMBERS Used by Canadian direct deposit

PAY_CA_LEGISLATION_INFO Canadian legislation specific data

PAY_CA_PMED_ACCOUNTS Canadian Provincial Medical account information

PAY_CE_RECONCILED_PAYMENTSHolds reconciliation information for payments processed through Oracle Cash Management.

PAY_COIN_ANAL_ELEMENTS Monetary unit quantities for automatic make-up of cash payments.

PAY_COMPARISON_ROWS  

PAY_CONSOLIDATION_SETS Consolidation set of results of payroll processing.

PAY_COSTS Cost details and values for run results.

PAY_COSTS_EFCThis is a copy of the PAY_COSTS table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_COST_ALLOCATIONS_F Cost allocation details for an assignment.

PAY_COST_ALLOCATION_KEYFLEX Cost Allocation key flexfield combinations table.

PAY_CUSTOMIZED_RESTRICTIONS CustomForm restrictions for specific forms.

PAY_CUSTOM_RESTRICTIONS_TL Translated data for the table PAY_CUSTOMIZED_RESTRICTIONS

PAY_DATED_TABLES Holds details of datetracked columns

PAY_DATETRACKED_EVENTS Stores details of events to track on HRMS Datetrack tables

PAY_DEFINED_BALANCESIntersection between PAY_BALANCE_TYPES and PAY_BALANCE_DIMENSIONS.

PAY_DIMENSION_ROUTES Stores balance dimension relationships.

PAY_ELEMENT_CLASSIFICATIONS Element classifications for legislation and information needs.

PAY_ELEMENT_CLASSIFICATIONS_TL Translated element classification definitions

PAY_ELEMENT_ENTRIES_F Element entry list for each assignment.

PAY_ELEMENT_ENTRY_VALUES_F Actual input values for specific element entries.

PAY_ELEMENT_ENTRY_VALUES_F_EFCThis is a copy of the PAY_ELEMENT_ENTRY_VALUES_F table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_ELEMENT_LINKS_F Eligibility rules for an element type.

PAY_ELEMENT_SETSElement sets.  Used to restrict payroll runs, customize windows, or as a distribution set for costs.

PAY_ELEMENT_SPAN_USAGES  

PAY_ELEMENT_TEMPLATES Element Templates

PAY_ELEMENT_TYPES_F Element definitions.

PAY_ELEMENT_TYPES_F_EFCThis is a copy of the PAY_ELEMENT_TYPES_F table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_ELEMENT_TYPES_F_TL Translated element definitions

PAY_ELEMENT_TYPE_EXTRA_INFO Stores extra information for an element

PAY_ELEMENT_TYPE_INFO_TYPES Types of extra information that may be held against an element.

PAY_ELEMENT_TYPE_RULES Include and exclude rules for specific elements in an element set.

PAY_ELEMENT_TYPE_USAGES_F Used to store elements included or excluded from a defined run type.

PAY_ELE_CLASSIFICATION_RULES Intersection table for PAY_ELEMENT_SETS and

PAY_ELEMENT_CLASSIFICATIONS.

PAY_ELE_PAYROLL_FREQ_RULES Frequency rules for a deduction/payroll combination.

PAY_ENTRY_PROCESS_DETAILS Internal processing details for certain element entries

PAY_EVENT_GROUPS Provides grouping for user control of event monitoring

PAY_EVENT_PROCEDURES Code to execute if event detected.

PAY_EVENT_QUALIFIERS_F Event Qualification definitions

PAY_EVENT_UPDATES Process event update transactions

PAY_EVENT_VALUE_CHANGES_F Values changes that cause an event

PAY_EXTERNAL_ACCOUNTS Bank account details that enable payments to be made.

PAY_FILE_DETAILS Report file details that have been saved in the system

PAY_FORMULA_RESULT_RULES_F Rules for specific formula results.

PAY_FREQ_RULE_PERIODS Stores frequency rule for a deduction/payroll combination.

PAY_FR_CONTRIBUTION_USAGESPAY_FR_CONTRIBUTION_USAGES holds the definition of statutory payroll contributions in the French legislation.

PAY_FUNCTIONAL_AREAS Holds definitions of functional areas

PAY_FUNCTIONAL_TRIGGERS Defines the triggers contained in a functional area

PAY_FUNCTIONAL_USAGESEnables functional areas for specific legislations, business groups and payrolls

PAY_GB_SOY_OUTPUTS Temporary table for GB Start of Year process outputs.

PAY_GB_TAX_CODE_INTERFACE Interface table for the UK Start of Year process.

PAY_GB_YEAR_END_ASSIGNMENTSExtraction table for UK End of Year processing, which holds information about assignments.

PAY_GB_YEAR_END_PAYROLLS Payroll information for the UK EOY process.

PAY_GB_YEAR_END_VALUESExtraction table for the UK End of Year process that holds information about the NI balances at the year end.

PAY_GL_INTERFACE Costed details to be passed to the General Ledger

PAY_GRADE_RULES_F Stores the values for grade or progression point rates.

PAY_GRADE_RULES_F_EFCThis is a copy of the PAY_GRADE_RULES_F table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_GROSSUP_BAL_EXCLUSIONSStores balances which will be excluded for gross up by the net to gross process

PAY_IE_PAYE_DETAILS_FPAY_IE_PAYE_DETAILS_F holds the PAYE Tax  Details for an assignment. It is a Date Tracked table.

PAY_IE_PRSI_DETAILS_FPAY_IE_PRSI_DETAILS_F holds the PRSI Details for an assignment. It is a Date Tracked table.

PAY_IE_SOCIAL_BENEFITS_FPAY_IE_SOCIAL_BENEFITS_F holds the social benefit details for an assignment.This is a date tracked table

PAY_IE_TAX_BODY_INTERFACEPAY_IE_TAX_BODY_INTERFACE,Interface table used for uploading data into PAYE tables from a flat file.

PAY_IE_TAX_ERRORPAY_IE_TAX_ERROR,Table used  to populate errors occured during uploading PAYE details.

PAY_IE_TAX_HEADER_INTERFACEPAY_IE_TAX_HEADER_INTERFACE,Interface table used for uploading data into PAYE tables from a flat file.

PAY_IE_TAX_TRAILER_INTERFACEPAY_IE_TAX_TRAILER_INTERFACE,Interface table used for uploading data into PAYE tables from a flat file.

PAY_INPUT_VALUES_F Input value definitions for specific elements.

PAY_INPUT_VALUES_F_EFCThis is a copy of the PAY_INPUT_VALUES_F table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_INPUT_VALUES_F_TL Translated input value definitions

PAY_ITERATIVE_RULES_F Holds the processing rules of iterative elements.

PAY_JOB_WC_CODE_USAGESWorkers Compensation codes for specific job and state combinations.

PAY_JP_BANKS This table is used for Japanese bank information.

PAY_JP_BANK_BRANCHES This table is used for Japanese bank branch information.

PAY_JP_PRE_TAX This table is a temporary table for Japanese legislative reports.

PAY_JP_SWOT_NUMBERSHolds Japanese Tax Special Withholding Obligation Taxpayer Numbers.

PAY_LEGISLATION_CONTEXTS Maps core contexts to legislative names

PAY_LEGISLATION_RULES Legislation specific rules and structure identifiers.

PAY_LEGISLATIVE_FIELD_INFO Controls legislative rules on individual form fields

PAY_LINK_INPUT_VALUES_F Input value overrides for a specific element link.

PAY_LINK_INPUT_VALUES_F_EFCThis is a copy of the PAY_LINK_INPUT_VALUES_F table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_MAGNETIC_BLOCKS Driving table for fixed format version of the magnetic tape process.

PAY_MAGNETIC_RECORDSControls the detailed formatting of the fixed format version of the magnetic tape process.

PAY_MESSAGE_LINES Error messages from running a process.

PAY_MONETARY_UNITS Valid denominations for currencies.

PAY_MONETARY_UNITS_TL Translated data for the table PAY_MONETARY_UNITS_TL

PAY_MONITOR_BALANCE_RETRIEVALS Monitors the source of balance retrievals

PAY_MX_EARN_EXEMPTION_RULES_F Used to hold the Earnings exemption rules for Mexico

PAY_MX_LEGISLATION_INFO_F Mexican legislation specific data

PAY_NET_CALCULATION_RULESElement entry values which contribute to the net value of Paid Time Off.

PAY_NL_IZA_UPLD_STATUS Holds the Status of the Data Records in the Processed IZA File

PAY_ORG_PAYMENT_METHODS_F Payment methods used by a Business Group.

PAY_ORG_PAYMENT_METHODS_F_EFCThis is a copy of the PAY_ORG_PAYMENT_METHODS_F table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_ORG_PAYMENT_METHODS_F_TL Translated payment method information

PAY_ORG_PAY_METHOD_USAGES_F Payment methods available to assignments on a specific payroll.

PAY_PATCH_STATUS Used to track the application of patches.

PAY_PAYMENT_TYPES Types of payment that can be processed by the system.

PAY_PAYMENT_TYPES_TL Translated payment type details

PAY_PAYROLL_ACTIONS Holds information about a payroll process.

PAY_PAYROLL_ACTIONS_EFCThis is a copy of the PAY_PAYROLL_ACTIONS table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_PAYROLL_GL_FLEX_MAPS Payroll to GL key flexfield segment mappings.

PAY_PAYROLL_LIST List of payrolls that a secure user can access.

PAY_PEOPLE_GROUPS People group flexfield information.

PAY_PERSONAL_PAYMENT_METHODS_F Personal payment method details for an employee.

PAY_PERSONAL_PAYMENT_METHO_EFCThis is a copy of the PAY_PERSONAL_PAYMENT_METHODS_F table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_PERSON_LATEST_BALANCES Latest balance values for a person.

PAY_POPULATION_RANGES PERSON_ID ranges for parallel processing.

PAY_PRE_PAYMENTSPre-Payment details for an assignment, including the currency, the amount and the specific payment method.

PAY_PRE_PAYMENTS_EFCThis is a copy of the PAY_PRE_PAYMENTS table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_PROCESS_EVENTS Process event capture table.

PAY_PROCESS_GROUPS Defines groups of processes

PAY_PROCESS_GROUP_ACTIONS Processes within the Process Group

PAY_PSS_TRANSACTION_STEPSTable holding (denormalised) work-in-progress for Payroll Payments self-service.

PAY_PURGE_ACTION_TYPES Details of the processing order required to purge action types.

PAY_PURGE_ROLLUP_BALANCESPopulated during Purge.  Stores details of the balance values being removed.

PAY_QUICKPAY_EXCLUSIONS List of element entries that are to be excluded from a QuickPay run.

PAY_QUICKPAY_INCLUSIONS List of element entries that can be included in a QuickPay run.

PAY_RATES Definitions of pay rates, or pay scales that may be applied to grades.

PAY_RECORDED_REQUESTS Dated process information.

PAY_REPORT_FORMAT_ITEMS_F Individual items for the report mapping.

PAY_REPORT_FORMAT_MAPPINGS_FMaps a report for a given jurisdiction to the fixed format defined for the magnetic tape.

PAY_REPORT_TOTALS  

PAY_RESTRICTION_PARAMETERS Restrictions to the rows retrieved by a customized form.

PAY_RESTRICTION_VALUES The specific values to be used to customize a form.

PAY_RETRO_ASSIGNMENTS Identifies assignment for reprocessing

PAY_RETRO_COMPONENTS  

PAY_RETRO_COMPONENT_USAGES  

PAY_RETRO_DEFINITIONS  

PAY_RETRO_DEFN_COMPONENTS  

PAY_RETRO_ENTRIES Identifies the Entries required for re-processing.

PAY_RETRO_NOTIF_REPORTS Populated and used in the RetroNotification Report

PAY_ROUTE_TO_DESCR_FLEXS Store of routes to Descriptive Flexfields

PAY_RUN_BALANCES Store of run level balances.

PAY_RUN_RESULTS Result of processing a single element entry.

PAY_RUN_RESULT_VALUES Result values from processing a single element entry.

PAY_RUN_RESULT_VALUES_EFCThis is a copy of the PAY_RUN_RESULT_VALUES table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_RUN_TYPES_F The different types of Payroll Run processing

PAY_RUN_TYPES_F_TL Translated run type descriptions

PAY_RUN_TYPE_ORG_METHODS_FOrganisation level payment methods associated with a particular run type.

PAY_RUN_TYPE_ORG_METHODS_F_EFCThis is a copy of the PAY_RUN_TYPE_ORG_METHODS_F table which is populated by the EFC (Euro as a Functional Currency) process.

PAY_RUN_TYPE_USAGES_FHolds child run types where the run type parent is of type Cumulative.

PAY_SECURITY_PAYROLLS List of payrolls and security profile access rules.

PAY_SHADOW_BALANCE_CLASSI Element Template Shadow Balance Classifications

PAY_SHADOW_BALANCE_FEEDS Element Template Shadow Balance Feeds

PAY_SHADOW_BALANCE_TYPES Element Template Shadow Balance Types

PAY_SHADOW_BAL_ATTRIBUTES  

PAY_SHADOW_DEFINED_BALANCES Element Template Shadow Defined Balances

PAY_SHADOW_ELEMENT_TYPES Element Template Shadow Element Type

PAY_SHADOW_ELE_TYPE_USAGES Element Template Shadow Element Type Usages

PAY_SHADOW_FORMULAS Element Template Shadow Formulas

PAY_SHADOW_FORMULA_RULES Element Template Shadow Formula Result Rules

PAY_SHADOW_GU_BAL_EXCLUSIONS Element Template Grossup Balance Exclusions

PAY_SHADOW_INPUT_VALUES Element Template Shadow Input Values

PAY_SHADOW_ITERATIVE_RULES Element Template Shadow Iterative Rules

PAY_SHADOW_SUB_CLASSI_RULES Element Template Shadow Sub-Classification Rules

PAY_STATE_RULES US state tax information.

PAY_STATUS_PROCESSING_RULES_F Assignment status rules for processing specific elements.

PAY_STAT_TRANS_AUDIT  

PAY_SUB_CLASSIFICATION_RULES_FRules to determine the inclusion of an element in a secondary element classification.

PAY_TAXABILITY_RULES Taxability rules for categories of earnings and deductions.

PAY_TAXABILITY_RULES_DATESMaintains taxability rules date-effectively, to allow for end-of-year updates.

PAY_TEMPLATE_CORE_OBJECTSKeeps track of  the core schema objects generated from an element template.

PAY_TEMPLATE_EXCLUSION_RULES Controls the exclusion of an object from an Element Template

PAY_TEMPLATE_FF_USAGES Allows multiple formulas to be associated with a shadow object.

PAY_TEMP_BALANCE_ADJUSTMENTS Holds temporary data used by the balance initialization process.

PAY_TEST_CONTEXTS  

PAY_TEST_EXPIRY_INFO  

PAY_TEST_FEED_INFO  

PAY_TEST_PARAMETERS  

PAY_TEST_PARAMETER_USAGES  

PAY_TEST_RUNS  

PAY_TEST_STAGES  

PAY_TEST_STEPS  

PAY_TEST_SUITE_USAGES  

PAY_TRIGGER_COMPONENTS Stored procedures that are executed from dynamic triggers

PAY_TRIGGER_DECLARATIONS Variables declared in dynamic triggers

PAY_TRIGGER_EVENTS Definitions of triggers that are dynamically generated

PAY_TRIGGER_INITIALISATIONS How dynamically generated triggers initialise their local variables

PAY_TRIGGER_PARAMETERSParameter mappings for dynamically generated procedure and function calls

PAY_TRIGGER_SUPPORTAllows support package for dynamically generated trigger to be linked to the trigger

PAY_USER_COLUMNS Column definitions for user defined tables.

PAY_USER_COLUMN_INSTANCES_FActual values for each row and column combination in a user defined table.

PAY_USER_ROWS_F Row definitions for user defined tables.

PAY_USER_TABLES Table definitions for user defined tables.

PAY_US_ASG_REPORTING Denormalised performance table for accessing balances.

PAY_US_CITY_GEOCODESHolds all distinct combinations of state code, county code and city code.

PAY_US_CITY_NAMESUS cities and their VERTEX geocodes, used to validate US addresses.

PAY_US_CITY_SCHOOL_DSTS VERTEX geocodes for school districts within a city.

PAY_US_CITY_TAX_INFO_F Holds city tax information.

PAY_US_CONTRIBUTION_HISTORYContribution History stores yearly consolidated contribution data for a Person per GRE per contribution type

PAY_US_COUNTIESUS counties and their VERTEX geocodes, used to validate US addresses.

PAY_US_COUNTY_SCHOOL_DSTS VERTEX geocodes for school districts that span counties.

PAY_US_COUNTY_TAX_INFO_F Holds county tax information.

PAY_US_EMP_CITY_TAX_RULES_F City level tax details for employee assignments.

PAY_US_EMP_COUNTY_TAX_RULES_F County level tax details for employee assignments.

PAY_US_EMP_FED_TAX_RULES_F Federal level tax details for employee assignments.

PAY_US_EMP_STATE_TAX_RULES_F State level tax details for employee assignments.

PAY_US_FEDERAL_TAX_INFO_F Holds federal tax information.

PAY_US_GARN_ARREARS_RULES_F Used for holding the Garnishment Arrears Rules

PAY_US_GARN_EXEMPTION_RULES_F Used for holding the Garnishment Exemption Rules

PAY_US_GARN_FEE_RULES_F Used for holding the Garnishment Fee rules

PAY_US_GARN_LIMIT_RULES_F Used for holding the Garnishment Limit Rules.

PAY_US_GEO_UPDATETo keep track of changes made to the user data by the geocode patch.

PAY_US_MODIFIED_GEOCODESUS cities and their VERTEX geocodes, used for showing modified geocodes.

PAY_US_RPT_TOTALS A temporary table to be used in Payroll and Paper W2 Reports.

PAY_US_SCHOOL_DSTS_TAX_INFO_FThe Federal Liaison Services ( FLS ) agency codes have been mapped to the School District Jurisdiction Information  Codes

PAY_US_STATESUS states and their VERTEX geocodes, used to validate US addresses.

PAY_US_STATE_TAX_INFO_F Holds the state tax information.

PAY_US_TAX_BALANCES Tax balances used by US Payroll Tax balance reporting.

PAY_US_TAX_REPORT_BALANCES Identifies tax balances for US Payroll Tax Summary Listing report.

PAY_US_TAX_REPORT_DIMENSIONSBalance dimensions used by the US Payroll Tax Summary Listing report.

PAY_US_TAX_TYPES US Tax Types used by US Payroll Tax Balance reporting.

PAY_US_ZIP_CODESValid zip code ranges for VERTEX cities, used to validate US addresses.

PAY_WCI_ACCOUNTS Workers Compensation Accounts table.

PAY_WCI_OCCUPATIONS Workers Compensation occupations table.

PAY_WCI_RATESWorkers Compensation rates table. NB. This table is currently used for Canadian workers compensation, but is designed to be used globally.

PAY_WC_FUNDS Workers Compensation Funds table.

PAY_WC_RATES Workers Compensation Rates table.

PAY_WC_STATE_SURCHARGES Workers Compensation Surcharges table.

PAY_ZA_ACB_USER_GEN_NOSPAY_ZA_ACB_USER_GEN_NOS holds the ACB generation number information needed when submitting magnetic tapes to ACB.

PAY_ZA_BRANCH_CDV_DETAILSPAY_ZA_BRANCH_CDV_DETAILS stores Bank and Branch information used to verify Bank account numbers.

PAY_ZA_CDV_PARAMETERSPAY_ZA_CDV_PARAMETERS holds information needed to perform the CDV on bank account numbers.

PAY_ZA_IRP5_BAL_CODES Table holds codes for IRP5 balances

PAY_ZA_TAXREG_BAL_TEMP Table holds balance types for specific assignments

PAY_ZA_TAX_REGISTERSPAY_ZA_TAX_REGISTERS is used for the South African Tax Register Report.

PAY_ZA_TAX_TRACES PAY_ZA_TAX_TRACES holds tax trace data calculated during the

payroll run. Only the most recent run's data will be stored.

PAY_ZA_TEMP_BRANCH_DETAILSPAY_ZA_TEMP_BRANCH_DETAILS is a temporary table that holds Bank and Branch information used to verify Bank account numbers, used in the population of PAY_ZA_BRANCH_CDV_DETAILS.

PAY_ZA_TYS_PROCESSES

PAY_ZA_TYS_PROCESSES stored information about each Tax Year Start Process that was run to ensure that the process will not be run for the same payroll and tax year, and to ensure that a rollback on the process will not occur if the specific

Posted by Muhammad Rafi Aamiri Madani