Skip to main content

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12?







Definition of Lookup in Oracle Apps R12

Or

What is Lookup in Oracle Apps R12?

Or

What is the main purpose of lookups in Oracle Apps R12?


















The main purpose of a lookup is to keep programs flexible and easier to configure. Lookups are an approach of creating a configurable “list of values” in E-Business Suite. One of the simplest examples of a lookup type is gender. A “gender lookup” will have definitions as shown next:

Code       Meaning
M             Male
F              Female
U             Unknown


Suppose that there is a table for employees named PER_ALL_PEOPLE_F and it has the following columns:

FIRST_NAME
LAST_NAME
DATE_OF_BIRTH
GENDER


The screen that displays an employee’s gender will display a value of Male, Female, or Unknown. However, the database column PER_ALL_PEOPLE_F table. GENDER will store a value of M, F, or U. Hence, the screen displays the meaning, whereas the database columns reference the lookup via a lookup code.
If in the future your organization wants the users to see “Undisclosed” instead of “Unknown,” you will have to make a change to just one record in the lookups table via the lookup screen. By doing so, you will avoid having to update thousands of records in PER_ALL_PEOPLE_F. Your new lookup will look like the following:

Code       Meaning
M             Male
F             Female
U             Unknown


Here lies the power of the lookups; you do not need to modify thousands of records in a transactional table. A simple change via the lookup screen will suffice. Using the lookup screen, you can either create new custom lookups or modify existing lookups.


What are the differences between system, extensible, and user lookup types in Oracle Apps R12?

OR

Type of Lookups in Oracle Apps R12



User
  • Insertion of new codes is allowed
  • Updating of the start date, end date, and enabled fields are allowed
  • Deletion of codes is allowed
  • Updating of the tag is allowed
Extensible
  • Deletion of lookup type is not allowed
  • Insertion of new codes is allowed
  • Updating of the start date, end date, enabled fields, and the tag is allowed only if the code is not 'seed data'
  • Deletion of codes is allowed only if the code is not 'seed data'
  • Updating of the module is not allowed
System
  • Deletion of lookup type is not allowed
  • Insertion of new codes is not allowed
  • Updating of the start date, end date, and enabled fields are not allowed
  • Deletion of codes is not allowed
  • Updating of the tag is not allowed
  • Updating of the module is not allowed
The following table shows the differences between system, extensible, and user lookup types:





Brief, some pre-seeded lookups given by Oracle cannot be modified. For example, Oracle has a lookup type called a termination type as shown in the above figure. Oracle has some rules defined within the Payroll Engine program that read the value of a termination type code for employees before calculating their final salaries. Such lookup codes, if changed, can affect the logic within the Payroll Engine. For this reason, Oracle flags some lookups as system lookups, and the Lookup Entry screen will not let you modify those lookup codes.


How can a lookup type be directly attached to a flexfield segment to do validations in Oracle Apps R12?


To do this, create a value set of Table type that validates against FND_LOOKUP_VALUES using the desired lookup. In this manner, you can validate flexfield segments against lookup values.

The point here is that a lookup type cannot be directly attached to a flexfield segment to do validations; however, it is indirectly possible to do so.


Examples and use cases where we use lookups in Oracle Apps R12.

Example: Interfacing Data to Third-Party Systems

Sometimes there is a need to create a database view that becomes the source of information for data transfer to other third-party systems. You might have to put filtration rules in place; for example, for HRMS Extract, people with person types Employee and Applicant should be extracted. To achieve this, instead of hard-coding Employee and Applicant in the database view, you can do the following:

1-Create a lookup type XX_EXTRACT_EMPLOYEE_TYPES.
2-Add lookup codes Employee and Applicant to this lookup type.
3-In the database view, join the HR Person Types from HR Tables with FND_LOOKUP_VALUES for this lookup type.

So through this manner, Lookup also gives you the flexibility to change hard-code Value in Code.






“A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide 




Comments

Popular posts from this blog

AP, AR, GL, INV, PA, FA, PO, TCA, Workflow - Interface and Base table in Oracle Apps R12

Main Interface and Base table in Oracle Apps R12 GL Module (General Ledger Module tables in Oracle Apps R12) Interface Table Base Table gl_interface gl_budget_interface gl_je_batches gl_je_headers gl_je_lines gl_je_sources gl_je_categories gl_sets_of_books gl_daily_rates gl_balances gl_periods gl_period_sets gl_code_conbinations AR Module (Account Receivable Module  tables  in Oracle Apps R12) Interface Table Base Table ra_customers_interface_all   ra_contact_phones_int_all ra_customer_profiles_int_all hz_parties hz_cust_accounts hz_cust_acct_sites_all hz_cust_sit_use_all hz_party_sites hz_locations hz_party_site_uses hz_customer_profiles hz_organization_profiles hz_person_profiles ra_interface_lines_all ra_interface_distributions_all ra_interface_salescredits_all ra_customer_trx_all ra_customer_trx_lines_all ra_cust_trx_line_gl_dist_all ra_cust_trx_types_all ar_payment_schedules_all ra_batch_sources_All ar_vat_tax_all ra_terms ar_periods ar_perio

Error: - APP-PER-50022: Oracle Human Resource Could Not Retrieve a Value For The User Type Profile Option. Please ensure it is set property for your responsibility

Error: - APP-PER-50022: Oracle Human Resource Could Not Retrieve a Value For The User Type Profile Option. Please ensure it is set the property for your responsibility. Solution-:      (1)  Go to System administrator > Profile > System       (2) Now Search “ HR: User Type ” Profile option at Responsibility level with Respective Responsibility. And Click On FIND Button. Now Select HR: User Type Value “HR with Payroll User” (you can choose another option as well accordingly). And SAVE. Now check your responsibility, error removed. Go ahead with your next step and enjoy Oracle Apps. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide.

APP-PO-14624: Source organization is missing or invalid

APP-PO-14624: Source organization is missing or invalid. At the time of creating an internal requisition with Source name Inventory and entering the Organization name that time this error occurs. Firstly check whether used Item should be ‘Transactable’, ‘Stockable’ & ‘Internal order enabled’ at both level Source and destination Organizations. Go to Inventory > Items > Master Items > Find the Item. Now go to Inventory tab and check attribute ‘Stockable’ and ‘Transactable’ are checked or not (It should be).And In Order Management tab, check ‘Internal Orders enabled’ attribute is available. Careful –: If Item attribute ‘Internal ordered’ is enabled then we cannot enable “Internal Orders enabled” attribute. Unless all the above three attributes are enabled we cannot Proceed with the Internal Requisition. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide