Search Results mls_enabled

Overview

AME_SEED_UTILITY is a public PL/SQL package owned by APPS within the Oracle E-Business Suite Approval Management Engine (AME) module. It provides the foundational utilities used by AME seed data routines to load, compare, and reconcile seeded configuration rows against the data already present in the AME schema. Seeded AME data includes approval rule definitions, action types, action type configurations, conditions, conditions usages, and mandatory attribute definitions. These rows are delivered by Oracle and identified by a reserved seed user, allowing the merge logic in this package to distinguish Oracle-owned records from customer-maintained records and to determine whether a given row should be inserted, updated, or left untouched.

The package also encapsulates environment detection and date-handling helpers used across the AME seed data loader, plus usage-count calculations that maintain denormalized usage statistics for attributes and rules. Its header comment identifies it as a non-shipped (noship) package, indicating it is internal infrastructure invoked by AME seed loading code rather than by end users directly.

Key Procedures and Functions

• INIT_AME_INSTALLATION_LEVEL — Initializes the package-level AME_INSTALLATION_LEVEL variable, establishing the installation context used by subsequent seed operations.
• OWNER_AS_STRING — Converts a numeric LAST_UPDATED_BY value into its string representation, typically for comparison against seed metadata.
• OWNER_AS_INTEGER — Converts a string owner value back into a number, the inverse of OWNER_AS_STRING. This is the function matching the query "owner_as_integer."
• DATE_AS_STRING — Formats a LAST_UPDATE_DATE value as a string for seed comparison purposes.
• DATE_AS_DATE — Parses a string LAST_UPDATE_DATE back into a date, complementing DATE_AS_STRING.
• IS_SEED_USER — Returns a boolean indicating whether the supplied user is the AME seed user.
• SEED_USER_ID and SEED_USER_NAME — Return the identifier and name of the reserved AME seed user.
• USER_ID_OF_SEED_USER — Returns the numeric user identifier of the seed user, used when populating owner columns.
• MERGE_ROW_TEST and TL_MERGE_ROW_TEST — Determine whether a seeded row should be merged (inserted or updated) based on current owner, current last update date, incoming owner, incoming last update date, and the custom mode flag. The TL variant applies to translatable (MLS) rows.
• GET_DEFAULT_END_DATE — Returns the default end date, based on the END_OF_TIME constant.
• MLS_ENABLED — Indicates whether Multi-Language Support is enabled in the current environment.
• CALCULATE_USE_COUNT — Calculates usage counts for a given attribute and application from attribute usage data.
• CREATE_PARALLEL_CONFIG — Creates parallel configuration entries linking action types, actions, and approval groups.
• CHANGE_ATTRIBUTE_USAGES_COUNT — Adjusts the usage count recorded for a rule and application within rule usage data.

Tables Accessed

The package reads and writes AME configuration and usage tables through APPS synonyms. AME_ATTRIBUTE_USAGES and AME_RULE_USAGES supply and store usage counts. AME_ACTIONS, AME_ACTION_TYPES, AME_ACTION_TYPE_CONFIG, AME_ACTION_TYPE_USAGES, and AME_ACTION_USAGES support parallel configuration creation. AME_APPROVAL_GROUP_CONFIG links approval groups to configuration rows. AME_CALLING_APPS identifies registered calling applications, while AME_CONDITIONS, AME_CONDITION_USAGES, AME_MANDATORY_ATTRIBUTES, and AME_RULES hold rule and condition seed data subject to the merge tests. DBMS_LOCK provides locking during seed operations, and DUAL supports simple value retrieval.

Usage Notes

AME_SEED_UTILITY is invoked indirectly by AME seed data loading routines rather than directly by end users. It is referenced by 28 other packages, reflecting its role as shared infrastructure. The MERGE_ROW_TEST and TL_MERGE_ROW_TEST functions are called during seed data application to determine row disposition. Custom code should not call this internal package directly; AME configuration should be managed through supported AME setup forms and concurrent programs.