This module helps in creating set of attributes for a given application in an abstract way, so that frameworks like PMF and other modules can leverage to retrieve application attributes and its values.
Each application is identified using an application package ID. For configuring package IDs, see Application Package section.
Against each package id, the set of attributes needs to be seeded in the “AAI_AOM_APP_COMP_ATTR_MAPPING” table.
AAI_AOM_APP_COMP_ATTR_MAPPING Table
Column Name |
Description |
APP_COMP_ATTR_MAP_ID |
Enter a unique ID for the attribute. You need to enter Attribute name and description for each attribute ID entered here in the AAI_AOM_APP_COMP_ATTR_TL table. See AAI_AOM_APP_COMP_ATTR_TL Table section. |
V_ATTR_CODE |
Name of the attribute. |
N_ATTR_TYPE_ID |
ID of the attribute type. The values of the attributes are fetched based on attribute type. 1001- Static 1002- SQL Query 1003- JavaAPI 1004- Hierarchy 1005- Multi Select Hierarchy 103- Date field 102- Textbox field For more information, see Attribute Types. |
V_ATTRIBUTE_VALUE1 V_ATTRIBUTE_VALUE2 |
Values to be fetched for the attribute. Based on the attribute type, you need to pass the values. |
N_APP_ID |
Application code for which the current attribute is configured. For example, if you are configuring Run execution parameters for IFRS application, enter the application ID of IFRS here. |
N_COMP_ID |
Component code for which the attribute is configured. |
V_UDP_CODE |
Special property used by applications (user defined). For example, ‘GET_STATUS’ –to get the status for the workflow. |
V_ATTR_CONTROL_TYPE |
Enter the Control type ID to be used for the attribute. For example, 3 is used for drop-down list, 7 for textbox, 11 for date control, 41 is for hierarchy and 42 for Multi Select hierarchy |
Example for Run Pipeline
Following figure shows an example of entries in AAI_AOM_APP_COMP_ATTR_MAPPING table for Run Pipeline:
The values of attributes are fetched based on the attribute types. Following are the attribute types with their IDs:
· 1001 (Static) - Store attribute values in the AAI_AOM_STATIC table as V_STATIC_ID and V_STATIC_VAL.
· 1002 (Query) - Enter the SQL query in V_ATTRIBUTE_VALUE1 in the AAI_AOM_APP_COMP_ATTR_MAPPING table, which has to be fired to fetch the attribute values.
· 1003 (JavaAPI) – Enter the method that is configured for V_ATTRIBUTE_VALUE1 for the required attribute. The configured method in the class path is invoked to get the attribute values in this case.
· 1004 (Hierarchy) – Specify the Hierarchy code to be fetched in V_ATTRIBUTE_VALUE1 in the AAI_AOM_APP_COMP_ATTR_MAPPING table.
· 1005 (Multi Select Hierarchy) – Specify the Multi Select Hierarchy entries in the AAI_AOM_APP_COMP_ATTR_TL table.
· 103 (DATE) - This is used for configuring FIC_MIS_DATE. The V_ATTR_CONTROL_TYPE value should be 11.
· 102 (Text Box) - This is used for Description field. The V_ATTR_CONTROL_TYPE value should be 7.
In this table, for each APP_COMP_ATTR_MAP_ID table, enter the locale specific Attribute Name, Description as shown:
While executing Run pipeline, the Select Run Params window displays the AOM fields which are marked as mandatory.
For example, for the attributes stored in APP_COMP_ATTR_MAP_ID table as shown in the previous figure, the Select Run Params window will be displayed as shown:
