Search Results worflow notification




The FND_FUNCTION_PARAMETER_MAP table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical repository table that stores parameter mappings for functions defined within the Oracle Applications Framework (OAF) and other functional modules. This table plays a pivotal role in ensuring seamless parameter passing between different components of the EBS system, particularly in the context of function security, navigation, and integration with custom or standard forms, reports, and concurrent programs. Below is a detailed breakdown of its structure, purpose, and significance. ### **Table Structure and Key Columns** The FND_FUNCTION_PARAMETER_MAP table contains the following key columns: 1. **FUNCTION_ID** – A foreign key reference to FND_FORM_FUNCTIONS.FUNCTION_ID, linking the parameter mapping to a specific function. 2. **PARAMETER_NAME** – The name of the parameter being mapped (e.g., ORG_ID, P_CONCURRENT_REQUEST_ID). 3. **PARAMETER_VALUE** – The static or dynamic value assigned to the parameter (may reference profile options, session variables, or literal values). 4. **CREATED_BY**, **CREATION_DATE**, **LAST_UPDATED_BY**, **LAST_UPDATE_DATE** – Standard Oracle EBS audit columns tracking record creation and modification. ### **Purpose and Functionality** The primary purpose of FND_FUNCTION_PARAMETER_MAP is to define how parameters are passed when a function is invoked, either through: - **Menu Navigation** (e.g., passing an ORG_ID when launching a form). - **Concurrent Program Submissions** (e.g., setting default values for report parameters). - **OA Framework Pages** (e.g., pre-populating fields based on user context). This table works in conjunction with FND_FORM_FUNCTIONS and FND_MENU_ENTRIES to ensure that runtime parameters are correctly resolved before execution. ### **Parameter Value Resolution** The PARAMETER_VALUE column supports dynamic resolution via special syntax: - **Profile Options**: ${PROFILE.<PROFILE_NAME>} (e.g., ${PROFILE.ORG_ID}). - **Session Variables**: ${<VARIABLE_NAME>} (e.g., ${USER_ID}). - **Literal Values**: Hardcoded values (e.g., Y for a flag). ### **Integration with Oracle EBS Security** The table is integral to Oracle’s function security model. When a user accesses a function (via a menu or responsibility), the mapped parameters are evaluated and passed to the target application, ensuring data-level security (e.g., restricting access by ORG_ID). ### **Example Use Case** Consider a custom concurrent program that requires the ORG_ID parameter. By defining a mapping in FND_FUNCTION_PARAMETER_MAP with PARAMETER_NAME='ORG_ID' and PARAMETER_VALUE='${PROFILE.ORG_ID}', the system automatically passes the user’s current operating unit. ### **Maintenance and Best Practices** - **Audit Regularly**: Review parameter mappings to avoid conflicts or obsolete values. - **Use Dynamic Values**: Leverage profile options for flexibility. - **Avoid Hardcoding**: Minimize static values to ensure adaptability across environments. ### **Conclusion** The FND_FUNCTION_PARAMETER_MAP table is a cornerstone of parameter management in Oracle EBS, enabling dynamic, secure, and context-aware parameter passing. Proper utilization of this table enhances system integration, user experience, and compliance with data security policies. Understanding its structure and behavior is essential for developers and administrators working with Oracle EBS 12.1.1 or 12.2.2.