Search Results init_ame_installation_level

Overview

AME_SEED_UTILITY is a supporting PL/SQL package body in the Oracle Approvals Management (AME) module. AME provides the rules engine that determines approval chains, approvers, and routing behavior for many Oracle E-Business Suite transactions, including iProcurement requisitions, Purchasing documents, and Human Resources workflows. The AME_SEED_UTILITY package exists to service the seed, load, and upgrade infrastructure used to deploy and maintain AME configuration data. Its routines operate as thin helper wrappers around the FND_LOAD_UTIL seed-data loader, translating between owner identifiers, user identifiers, and date representations so that other AME packages can perform consistent comparisons during data merges and upgrades.

The package is classified as OTHER in the documented API metadata, meaning it is not a public business API. It is an internally consumed utility that is referenced by 28 other packages, which underscores its role as a foundational dependency of the AME seed-data framework.

Key Procedures and Functions

The documented routines fall into several functional groups.

• INIT_AME_INSTALLATION_LEVEL — Initializes the AME installation level package variable by reading the AME_INSTALLATION_LEVEL profile option.
• OWNER_AS_STRING and OWNER_AS_INTEGER — Convert between the numeric last-updated-by identifier and its string owner name using FND_LOAD_UTIL.
• DATE_AS_STRING and DATE_AS_DATE — Convert last update date values between DATE and VARCHAR2 using the canonical format YYYY/MM/DD HH24:MI:SS. DATE_AS_DATE performs the string-to-date conversion used when comparing uploaded seed rows.
• IS_SEED_USER, SEED_USER_ID, and SEED_USER_NAME — Identify and return the canonical seed user; IS_SEED_USER checks whether a given user resolves to a known seed owner identifier.
• MERGE_ROW_TEST and TL_MERGE_ROW_TEST — Determine whether a seed row should be inserted or updated during a merge, honoring a FORCE custom mode and otherwise delegating to FND_LOAD_UTIL.UPLOAD_TEST.
• GET_DEFAULT_END_DATE, MLS_ENABLED, CALCULATE_USE_COUNT, USER_ID_OF_SEED_USER, CREATE_PARALLEL_CONFIG, and CHANGE_ATTRIBUTE_USAGES_COUNT — Provide ancillary services including default end-date derivation, multi-lingual support detection, use-count calculation, seed user resolution, parallel configuration creation, and attribute usage counting.

Tables Accessed

The package reads and writes AME configuration tables through APPS synonyms. AME_ATTRIBUTE_USAGES, AME_CONDITIONS, and AME_CONDITION_USAGES are consulted when calculating use counts and attribute usage changes. AME_RULES and AME_RULE_USAGES support rule-level configuration checks. The action-related tables — AME_ACTIONS, AME_ACTION_TYPES, AME_ACTION_TYPE_CONFIG, AME_ACTION_TYPE_USAGES, and AME_ACTION_USAGES — are referenced when validating action configuration. AME_APPROVAL_GROUP_CONFIG, AME_MANDATORY_ATTRIBUTES, and AME_CALLING_APPS complete the AME object set. DBMS_LOCK supports serialized processing, and DUAL provides single-row select targets.

Usage Notes

AME_SEED_UTILITY is not intended for direct invocation by end users or custom forms. It is invoked during AME seed-data loading and patching, typically through the standard Oracle Applications seed loader infrastructure and during upgrades between 12.1.1 and 12.2.2. The DATE_AS_DATE and DATE_AS_STRING functions are the mechanism of interest for the search term "date_as_date": DATE_AS_DATE converts the stored VARCHAR2 date representation into a native DATE so that FND_LOAD_UTIL.UPLOAD_TEST can compare upload timestamps against database timestamps. Any custom code that manipulates AME seed data should reuse these helpers rather than reprocessing the timestamp format independently, since the YYYY/MM/DD HH24:MI:SS format is the agreed contract across the seed framework.