Results for “batch_job_num”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ICX_CAT_CATEGORIES_TL is the translation table for the Oracle iProcurement (ICX) category catalog. It stores the language-specific, user-facing text associated with each category record, enabling multilingual display of category names, descriptions, and titles across the iProcurement requisitioning and catalog browsing interfaces. In Oracle EBS 12.1.1 and 12.2.2, this table works in conjunction with the base ICX_CAT_CATEGORIES_B table, which holds language-independent attributes, while the "_TL" table supplies the translatable columns keyed by LANGUAGE.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. It is neither a hub, link, nor satellite by the mined foreign-key structure, meaning it has no documented outward FK dependencies and functions as an independent descriptive entity within the iProcurement schema. The 25-column schema and its two unique indexes clearly identify it as a business-data carrier rather than a pure junction table.

Key Information Stored

The table's primary key is ICX_CAT_CATEGORIES_TL_PK, defined on the composite of LANGUAGE and RT_CATEGORY_ID. RT_CATEGORY_ID serves as both part of the surrogate primary key and the linkage back to the parent category, while LANGUAGE identifies the translation locale.

• RT_CATEGORY_ID – Identifies the parent category record; the primary join key to the base category table.
• LANGUAGE – The language code for the translated row; part of the primary key.
• SOURCE_LANG – The source language from which the translation was derived, used in the translation workflow.
• CATEGORY_NAME – The translated, user-visible category name, the most frequently queried attribute.
• UPPER_CATEGORY_NAME – An uppercase form of the category name used for case-insensitive search.
• DESCRIPTION – The translated long description of the category.
• TITLE – An alternate display title for the category entry.
• TYPE – Classifies the category record; participates in the U2 unique index.
• KEY – A business key value used for category identification and lookup; participates in the U2 unique index.
• UPPER_KEY – Uppercase form of the business key for case-insensitive matching.
• ITEM_COUNT – The number of items associated with the category, useful for catalog reporting.
• SECTION_MAP – Stores the section mapping configuration associated with the category display.
• ZD_EDITION_NAME – Editioning column supported in 12.2.x, participates in both unique indexes and is not present in the 12.1.1 schema.
• Audit and concurrency columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, PROGRAM_LOGIN_ID, BATCH_JOB_NUM, REBUILD_FLAG track who changed the translation and which concurrent program performed any rebuild or refresh.

Two unique indexes serve as business-key candidates: ICX_CAT_CATEGORIES_TL_U1 (RT_CATEGORY_ID, LANGUAGE, ZD_EDITION_NAME) confirms a single translation per category per language, and ICX_CAT_CATEGORIES_TL_U2 (KEY, TYPE, LANGUAGE, ZD_EDITION_NAME) enforces uniqueness of the business key by type and locale.

Common Use Cases and Queries

Typical uses include multilingual category display, translation completeness reporting, and catalog maintenance validation. A common pattern retrieves the translated category name for a given language:

• SELECT rt_category_id, category_name, description FROM icx_cat_categories_tl WHERE language = USERENV('LANG') AND rt_category_id = :id;
• Joining to the base table to detect missing translations: SELECT b.rt_category_id FROM icx_cat_categories_b b, icx_cat_categories_tl tl WHERE b.rt_category_id = tl.rt_category_id(+);
• Reporting on catalog size by category via ITEM_COUNT aggregates.
• Case-insensitive search using UPPER_CATEGORY_NAME or UPPER_KEY.
• Auditing translation load jobs through REQUEST_ID, BATCH_JOB_NUM, and REBUILD_FLAG.

Related Objects

The table is closely tied to the following iProcurement and shared schema objects:

• ICX_CAT_CATEGORIES_B – The base category table joined on RT_CATEGORY_ID.
• ICX_CAT_CATEGORIES_VL – The translated view layer that presents both base and TL columns.
• ICX_CAT_ITEMS – Catalog items linked to categories via the category identifier.
• ICX_CAT_ITEM_VAL_EXTRACT – Extraction objects that surface category names.
• PO_CATEGORIES / PO_CATEGORIES_TL – Purchasing category definitions frequently synchronized with iProcurement categories.
• ICX_CAT_CATEGORIES_TL_S – Sequence used to generate RT_CATEGORY_ID values.
• FND_LANGUAGES – Provides valid LANGUAGE codes referenced by translated rows.
• FND_CONCURRENT_REQUESTS – Join on REQUEST_ID to trace translation batch programs.