IRDB Table Architecture
autoextractor_control Table
The purpose of the auto extractor control table is to specify the conditions and data extracted by the APM Connect interfaces. The structure of the table is outlined below, indicating the fields that should be updated during customization.
| Field Name | Description | Configurable |
|---|---|---|
| autoextract_id | Auto-generated index | Do Not Modify |
| batch_name | Interface Batch Name | Do Not Modify |
| active |
| Yes |
| job_name | APM Connect sub-process name | Do Not Modify |
| filename | Filename returned by SAP | Do Not Modify |
| run_in_background |
True - Run in SAP background False - Run in foreground | Yes |
| default_date_value | Date used when SAP returns a null date | Do Not Modify |
| field_separator | Indicates file delimiter in file returned by SAP | Do Not Modify |
| abap_cursor_fetch_size | Invokes SAP to read large data sets as a batch of the size indicated | Do Not Modify |
| extract_schema_definition |
An array utilized in SAP select statements when retrieving data. Structure: “SAP Table Name | SAP Field Name” Delimiter: “;” | Yes |
| join_condition | Join condition used when querying the data in SAP | Yes |
| where_condition | Where condition used when querying the data in SAP | Yes |
| for_all_entries_field_name | Field name used in SAP where a “For All Entries” statement is in use in the SAP Query | Do Not Modify |
| for_all_entries_field_type | SAP Field data type used in SAP where a “For All Entries” statement is in use in the SAP Query | Do Not Modify |
| for_all_entries_condition | Condition used in SAP where a “For All Entries” statement is in use in the SAP Query | Do Not Modify |
| object_list_type | Object to create a list of objects when utilizing the object_list_control table | Do Not Modify |
| object_type | Refers to SAP object, interface name, SAP Table name when utilizing the object_list_control table | Do Not Modify |
| sap_background_job_name | When running in SAP background, this is the job name passed to SAP. | Yes |
| step_seq | Not in use | Do Not Modify |
| cmms_id | SAP System ID | Yes |
autoloader_control Table
The purpose of the auto loader control table is to specify the condition under which the data extracted in active entries in the autoextractor_control is staged in temporary tables in the IRDB. The structure of the table is outlined below, indicating the fields that should be updated during customization.
| Field Name | Description | Configurable |
|---|---|---|
| autoloader_id | Auto-generated index | Do Not Modify |
| batch_name | Interface Batch Name | Do Not Modify |
| active |
Note: Must match active status for same batch_name in autoextracor_control table | Yes |
| job_name | APM Connect sub-process name | Do Not Modify |
| filename | Filename returned by SAP that will load into IRDB temporary table. | Do Not Modify |
| table_name | IRDB temporary Table Name | Do Not Modify |
| null_string | Default Date String | Do Not Modify |
| field_separator | Indicates file delimiter in file returned by SAP | Do Not Modify |
| row_separator | Indicates new line indicator in file returned by SAP | Do Not Modify |
| delete_where_clause | Utilized in multiple EAM system configurations to clear entries in temporary table for the EAM system that is being updated. | Do Not Modify |
| object_type | Refers to SAP object, interface name, SAP Table name when utilizing the object_list_control table | Do Not Modify |
| transform_job_name |
APM Connect transformation sub-process name
| Do Not Modify |
| cmms_id | SAP System ID | Yes |
autojoin_control Table
The purpose of the auto join control table is to fetch the data loaded into the IRDB temporary tables and create the data payloads to be loaded into APM. The structure of the table is outlined below indicating the fields that should be updated during customization.
| Field Name | Description | Configurable |
|---|---|---|
| autojoin_id | Auto-generated index | Do Not Modify |
| batch_name | Interface Name | Do Not Modify |
| table_name | The data table name to identify the data sheet when loading into APM. | Do Not Modify |
| sql_execution_order | Specifies the order of the data load for each batch_name | Do Not Modify |
| sql | The query to extract data from the temporary table in the IRDB. | Yes |
| site_reference | Site reference in APM can be an APM Family Field or a constant | Yes |
| apm_site_reference_column | Field name for Site Reference in APM | Do Not Modify |
| apm_site_reference_family | APM Family to fetch the site reference in which site_reference field resides. | Do Not Modify |
| use_relationship_lookup |
Null – ignored
| Do Not Modify |
| default_site_reference | Default Site is no site is configured | Yes |
| primary_family_id | APM Family ID | Do Not Modify |
| cmms_id | SAP System ID | Yes |
southbound_mapping_control Table
The purpose of this table is to provide a dynamic mapping capability from APM fields (including custom fields) in the Recommendation to SAP fields supported by the baseline interface for notification creation. The request from APM has the following details:
- Entity (EQ/FL) on which the request is being generated
- Connection information of the EAM system
- APM Family Fields (including custom fields) from the Recommendation
The structure of the table is outlined below, indicating the fields that should be updated during customization.
| Field Name | Description | Configurable |
|---|---|---|
| southbound_mapping_control_id | Auto-generated index | Do Not Modify |
| apm_field_name | APM Field Name | Yes |
| target_field_name | SAP Field Name | Do Not Modify |
| target_field_map_name | SAP RFC Parameter Name | Do Not Modify |
| mapping_enabled |
True – Will be pushed to SAP False – Will not be pushed to SAP | Yes |
| target_default_value | Default value in case data is not provided in the payload | Yes |
| cmms_id | SAP System ID | Yes |