Skip to main content


Showing posts from April, 2009

India Localization

India Localization is a major part of any Indian company using Oracle ERP. What is this India Localization(IL). Why is it so important.? This is the module for Payrol/payables/receiving or for any transaction which comes under Local Indian taxasion rules. This is the module through which TDS (Tax Deduction at source) is collected wrt Indian taxation rules. This module belongs to JA_TOP for which the development work is done in India and it has its own library stack and its own way of applying patches. Since taxasion comes under India Regulatory act which makes it important to manage/implement this module without any flaws which makes it very hard on the client to test each and every scenario. In 11i most of the readers would know that the patch details are kept in ad_applied_patches and ad_bugs but for IL it is kept under JAI_APPLIED_PATCHES. India Localization patches are applied to IL Patch application tool which comes with the patch, "6491231 REF : 6059025 - MULTINODE

What are Flexfields

Flexfields are a major part of Oracle Applications. Rather than knowing what a flexfield is, it is better to start with different types of flexfields and know what each type of flexfield mean. There are 2 types of flex fields Key Flexfield Descriptive Flexfield Key Flexfield: A Key Flexfield looks like a normal text field on a form. Descriptive Flexfield: A descriptive flexfield appears on the form within 2 brackets [] with a character length 2. When opened both types appear as a pop up window that contains sub fields. So a flex field is a field made of sub fields(segments, values, valuesets). Each segment has an unique name and a set of valid values and their descriptsion. A segment is represented as a single table column in a table.

Concurrent Requests Purge Program -- What happens?

The following tables will be purged: . FND_CONCURRENT_REQUESTS This table contains a complete history of all concurrent requests. . FND_RUN_REQUESTS When a user submits a report set, this table stores information about the reports in the report set and the parameter values for each report. . FND_CONC_REQUEST_ARGUMENTS This table records arguments passed by the concurrent manager to each program it starts running. . FND_DUAL This table records when requests do not update database tables. . FND_CONCURRENT_PROCESSES This table records information about Oracle Applications and operating system processes. . FND_CONC_STAT_LIST This table collects runtime performance statistics for concurrent requests. . FND_CONC_STAT_SUMMARY This table contains the concurrent program performance statistics generated by the Purge Concurrent Request and/or Manager Data program. The Purge Concurrent Request and/or Manager Data program uses the data in FND_CONC_STAT_LIST to compute these statistics. FND_CONC_PP

eMail Center -- What is it?

Oracle eMail Center is a comprehensive solution for managing high volumes of inbound and outbound e-mails. Oracle eMail Center reduces the cost per email interaction by automatically replying to certain email inquiries as well as routing others to a skilled set of agents and providing them with a full featured console with cross application functionality. Oracle eMail Center increases customer satisfaction and reduces customer attrition by providing quick, accurate and consistent responses. It also increases agent’s efficiency through the use of a full featured, eMail Center agent console thereby reducing agent turnover. Oracle Email Center provides agents with the ability to create business objects such as a service request and at the same time provides message composing/viewing capabilities to the business users such that every email interaction is recorded and archived. Email Center provides its agents the ability to create a service request from within the Message Component, wh

Did you know --- Oracle Database 9i

1. Oracle 9i can have maximum of 256 column for a row. 2. For a partitioned table, each partition has a data segment. Each cluster has a data segment. The data of every table in the cluster is stored in the cluster's data segment. 3. A tablespace can be online (accessible) or offline (not accessible). A tablespace is taken offline to make a portion of the database unavailable while allowing normal access to the remainder of the database.