General Reference
SAP Transactions-Quick Reference
The following table provides a list of SAP transactions and their functions.
This transaction: | ...Lets you: |
---|---|
/n/MIAPM/MIPRO | View a list of APM-specific steps that can be performed in SAP. |
/n/MIAPM/MANAGE_PARAMS | Access and manage the /MIAPM/PARAMS table. |
/n/MIAPM/MANAGE_TSKCNF | Access the /MIAPM/TASK_CNF table. |
SM37 | Check the status of a background process. |
IW43 | Validate SAP Confirmations against that data in APM Confirmation records. |
Requirements
SAP System Requirements
- SAP Backend System: The following versions are supported:
- SAP ECC 6.0 (Enhancement Packs [EhP] 1 and above)
- SAP S/4 HANA on-premises (1509, 1610, 1709, 1809, 1909, 2020, 2021, 2022)
- SAP Database: A database that contains the SAP data model and data.
- SAP Internet Transaction Server (ITS): Version 6.20 or higher.
- SAP Java Connector Files (SAP JCO) downloaded from the SAP marketplace, which contains the following files:
- sapjco.dll
- sapjco3.dll
- sapjco3.jar
SAP PI System Requirements
- SAP Backend System: The following versions are supported:
- SAP ECC 6.0 (Enhancement Packs [EhP] 1 and above)
- SAP S/4 HANA on-premises (1509, 1610, 1709, 1809, 1909, 2020, 2021, 2022)
- SAP PI: An SAP PI system 7.00 and above, up to SAP PI/PO 7.50.
APM Connect User Profile Requirements
To successfully extract data from SAP, APM Connect needs authority objects, access to RFCs, and access to SAP Tables.
Authority Objects Required
APM Connect must have the authority objects listed.
Authorization Object | Description |
---|---|
C_TCLA_BKA | Authorization for Class Types |
I_AUART | PM: Order Type |
I_BEGRP | PM: Authorization Group |
I_BETRVORG | PM: Business Operation |
I_INGRP | PM: Maintenance Planner Group |
I_KOSTL | PM: Cost Centers |
I_QMEL | PM/QM: Notification Types |
I_SWERK | PM: Maintenance Plant |
I_WERK | PM: Maintenance Planning Plant |
S_BTCH_JOB | Background Processing: Operations |
S_DATASET | Authorization for File Access |
S_LOG_COM | Required if file transfer is SFTP/SCP. For server mode this authorization is not required. |
S_RFC | Authorization Check for RFC Access |
S_TABU_NAM | Table Access with Generic Standard |
RFCs Required
APM Connect must have access to the RFCs listed in the following table.
/MIAPM/* | RFC_GET_FUNCTION_INTERFACE | SYSTEM_RESET_RFC_SERVER |
CLAF_CLASSIFICATION_OF_OBJECTS | RFCPING | RFC_PING |
DDIF_FIELDINFO_GET | SYSTEM_RESET_RFC_CONNECTION |
SAP Tables Required
APM Connect must have access to the tables listed in the following table.
/MIAPM/* | CRHD | JEST | PRPS | T353I_T | TGSBT |
AFVV | CRTX | JSTO | QMEL | T356_P | TJ02 |
AFKO | CSKT | KLAH | QMFE | T356_T | TJ02T |
AFRU | CVERS | KSML | QMMA | T357 | TJ30 |
AFVC | EAPL | KSSK | QMUR | T357A_T | TJ30T |
AFVV | EQBS | MAKT | QPCT | T357M_T | TKA01 |
AUSP | EQKT | MHIS | SWOR | T370C_T | TQ80 |
BGMKOBJ | EQUI | MHIO | T001 | T370F_T | TQ80_T |
CABN | EQUZ | MMPT | T001W | T370K_T | VIAUFKST |
CABNT | IFLO | MPLA | T003P | T370U | VIQMEL |
CAWN | IFLOS | OBJK | T006 | TAPL | VIMPLA |
CAWNT | IFLOT | PLAS | T006A | TCLA | VIMPOS |
COBK | IFLOTX | PLKO | T024I | TCURC | T399G_T |
COEP | ILOA | PLPO | T350 | TCURR | T356_T |
COVP | INOB | PMCO | T352B_T | T499S | TGSBT |
CRHD | CRTX | TCN00 | TCN01 | TCURC | TCURT |
T399I | T001W | T411 | T411T | t003o | t003p |
T351X | T351P | TCF10 | TCF11 | DRAW | DRAT |
T399W | T024I | T351 | T351T | T024E | CSSL |
CSLT | T006 | T006A | T412 | T412T | T024A |
T024 | TQ80 | TQ80_T | T023 | T023T | |
T430 | T430T | TDWA | TDWAT | TFACD | TFACT |
T006D | T006T | T370B_T | T357M_T | t353i | t353i_t |
t350i | T435 | T435T | T399W_T | CSKA | CSKU |
SAP Interfaces Security Groups
The following table lists the baseline Security Groups available for users within this module, as well as the baseline Roles to which those Security Groups are assigned. In APM APM, Roles are assigned to Security Users through permission sets.
Security Group | Roles |
---|---|
MI SAP Interface Administrator | None |
MI SAP Interface User | None |
Family | MI SAP Interface Administrator | MI SAP Interface User |
---|---|---|
Entity Family | ||
Confirmation | View, Update, Insert, Delete | View, Update, Insert |
Equipment | View, Update, Insert, Delete | View, Update, Insert |
Functional Location | View, Update, Insert, Delete | View, Update, Insert |
SAP System | View, Update, Insert, Delete | View |
Site Reference | View | View |
Work History | View, Update, Insert, Delete | View, Update, Insert |
Work History Detail | View, Update, Insert, Delete | View, Update, Insert |
Relationship Families | ||
Equipment Has Equipment | View, Update, Insert, Delete | View, Update, Insert, Delete |
Functional Location Has Equipment | View, Update, Insert, Delete | View, Update, Insert, Delete |
Functional Location Has Functional Location(s) | View, Update, Insert, Delete | View, Update, Insert, Delete |
Has Confirmation | View, Update, Insert, Delete | View, Update, Insert, Delete |
Has Event Detail | View, Update, Insert, Delete | View, Update, Insert, Delete |
Has SAP System | View, Update, Insert, Delete | View, Update, Insert, Delete |
Has Work History | View, Update, Insert, Delete | View, Update, Insert, Delete |
User Assignment | View, Update, Insert, Delete | View, Update, Insert, Delete |
About Site Filtering Configuration via the autojoin_control Table
Site Reference values are managed in the Intermediate Repository, specifically in the autojoin_control table as shown in the following image.
About the Baseline Site Reference Configuration
The baseline configuration of the SAP Adapters uses the SAP System to determine the site to which a record should be assigned. More specifically, the value in the site_reference column in the autojoin_control table is #MI_FNCLOCOO_SAP_SYSTEM_C#
for Functional Location records and #MI_EQUIPOO_SAP_SYSTEM_C#
for Equipment records.
Additionally, if SAP System value is null or empty on a record in SAP, once transferred into APM, it will be assign the site reference defined in the defaut_site_reference column in the autojoin_control table. The default value is *Global*
.
If you want to use your SAP System as the site for all records transferred from SAP to APM then no additional configuration is needed. However, if necessary, you can configure different site reference values.
About the autojoin_control Table
You can specify site references using the autojoin_control table. The columns in this table are described in the following table.
Column | Description |
---|---|
AUTOJOIN_ID | Surrogate ID used to uniquely identify a row; i.e., the primary key. |
BATCH_NAME | When a load is processed, queries defined in this table are run together in batches. All queries with the same BATCH_NAME are executed together. |
TABLE_NAME | The name of the temporary table that will be created for this row. This name will be concatenated by the load UUID. |
SQL_EXECUTION_ORDER | Within a batch, the value in this column defines the order in which the SQL statements will be executed. Lower numbers will be executed first. |
SQL | The SQL SELECT statement to be executed. The results of this statement will be copied to the temporary table defined by the load UUID and the TABLE_NAME column. Columns defined in the SELECT statement should match exactly the column names in the APM family for which data is being loaded. |
SITE_REFERENCE |
This column specifies the value to use for the corresponding record's Site Reference Key. This can be a direct site reference (i.e., a specific site reference name) or it can contain an indirect site reference (i.e., a field that contains the site reference name to use). See Configure Site Reference Values for details. Note: The baseline value is
#MI_FNCLOCOO_SAP_SYSTEM_C# for Functional Location records and #MI_EQUIPOO_SAP_SYSTEM_C# for Equipment records. This means the SAP System will determine to which site records are assigned. |
APM_SITE_REFERENCE_COLUMN |
The APM column used to store Site Reference values. Unless you have customized the APM database, this value should be |
APM_SITE_REFERENCE_FAMILY | The APM family to which the site reference will be applied. When the relationship is being built within the records of the same entity, the value is <PRED_FAMILY_ID>. Unless you have customized the APM database, you do not need to modify this value. |
USE_RELATIONSHIP_LOOKUP |
This column specifies whether the row is for an entity or relationship. If this row is populating a relationship, the value should be 1. If not, the value should be 0. This affects the way relationship references are defined in the resulting SQL statements. |
DEFAULT_SITE_REFERENCE |
If an indirect site reference is specified, this value defines the Site Reference Key that should be used if the value in the specified indirect site reference column is NULL.
|
About File Shares and APM Connect
File shares mounted in the APM Connect architecture allow you to read and write files between servers within your architecture configuration.
File Mount Configurations
If you are using SAP PI, create a file share on your APM Connect server, and then mount it to your SAP PI server. Then, create a share on your SAP server, and then mount to your SAP PI Server. Similarly, if you are not using SAP PI, or you are bypassing your SAP PI server, you must create a file share on your APM Connect server, and then mount it to your SAP Server.Additionally, in the most common architecture, the APM Connect server is hosted on a Windows Sever with the SAP server and the SAP PI server hosed on a Linux server. The following diagrams details the recommended configurations.
User’s Permissions for File Shares
When using a shared file system to facilitate data extraction from SAP to APM Connect, you will need to grant the service account user(s) the appropriate permissions to access both systems.
The volume to be mounted can be in three configurations: NAS/SAN, Windows, or Unix. Additionally, access control could be different for each configuration, as shown in the following table:
Volume (Disk, Share, LUN) | Access Control |
---|---|
NAS/SAN | Vendor specific user mapping (i.e. NetApp), or active directory integrations. |
Windows | Users/Groups permissions are defined in Active Directory. |
Unix | Active Directory integration, or user maps (i.e. Samba or Config). |
About Classification Hierarchies
In SAP, for any given class, multiple characteristics can be inherited from another class.
For example, consider the following SAP classes:
- EQ_CLASS_0001
- Fasteners
- Bolts
- Hexagonal Bolt
As shown in the following image, EQ_CLASS_0001 has four unique characteristics:
As shown in the following image, Fasteners also has four sets of unique characteristics:
Bolts, however, inherits all of the characteristics from EQ_CLASS_0001 and FASTENERS. In addition, Bolts has two unique characteristics of its own: HEAD_SHAPE and BOLT_TYPE:
Finally, Hexagonal Bolt also inherits all of the characteristics from EQ_CLASS_0001, FASTENERS, and BOLTS. It also has one unique characteristic of its own: TOLERANCE:
Using these SAP classes, in APM system, if you were to select the Extract From CMMS System check box for the HEXAGONALBOLT class, after selecting the Synchronize Characteristics link while viewing the HEXAGONALBOLT CMMS Classification record, the following CMMS Characteristic records would be created automatically:
As you can see from the Classification column, some of the characteristics are inherited from other classes:
Specifically, you can see that:
- The following characteristics are inherited from the class EQ_CLASS_0001:
- COLOR
- LOCAL_REG_NUM
- OPH
- SAP_EHS_1017_003_TEST_TYPE
- The following characteristics are inherited from the class FASTENERS:
- FASTENER_DIAMETER
- LENGTH
- NUMBEROFTHREADS
- THREAD_TYPE
- The following characteristics are inherited from the class BOLTS:
- HEAD_SHAPE
- BOLT_TYPE
- The characteristic TOLERANCE is assigned directly to the class HEXAGONALBOLT (no highlighting).
If you selected the Extract From CMMS System check boxes for all of these characteristics, if you were to run the Equipment Characteristics Extraction Interface without filters, all of these characteristics would be extracted.
If, however, you were to filter the report to extract only characteristics belonging to the HEXAGONALBOLT class, only characteristics that are assigned directly at the HEXAGONALBOLT level would be extracted. In other words, because only TOLERANCE is assigned directly to HEXAGONALBOLT, only the TOLERANCE characteristic would be extracted.
About Extracting Characteristics
When you create CMMS Classification Type records using the CMMS System list, you must select the SAP system from which you want to extract characteristics belonging to that classification type.
The CMMS System list displays the values in the Name field in all existing EAM System records. When you save the CMMS Classification Type record, the APM system finds the EAM System record whose Name field contains the selected value, and the value in the System ID field in that EAM System record is copied to the CMMS System ID field in the CMMS Classification Type record.
Then, when you create CMMS Classification or CMMS Characteristic records that are associated with that CMMS Classification Type record, the value in the CMMS System ID field in the CMMS Classification Type record is copied automatically to the CMMS System ID field in those records.
CMMS Characteristic records are created automatically and linked to the CMMS Classification record. Each CMMS Characteristic record is created from a characteristic that currently exists in the specified SAP system (using the CMMS System field in the CMMS Classification record). The CMMS Characteristic records are displayed in a grid on the CMMS Classification datasheet.
When you run the Equipment Characteristic Extraction Interface or the Functional Location Characteristic Extraction Interface, APM needs to determine which specific characteristics to extract from that system. To do so, it evaluates the CMMS Characteristic records that exist in your APM database. If it finds any CMMS Characteristic records whose CMMS System ID field value identifies the SAP system from which you are running the interface, it will extract only those characteristics from that SAP system (assuming that the Extract from CMMS System check box is selected in the CMMS Characteristic record).
About Site Filtering Configuration in the Context File
The EAM Adapters are used to populate the Site Reference on Equipment, Functional Location, and Work History records in APM.
- Site Reference records must exist in your APM system, before you can use the EAM Adapters to populate the Site Reference Key. Additionally, the site entered into the context file must match the exact value in the corresponding Site Reference record.
- The user who is running the EAM Adapters jobs must be assigned, in APM, to the site to which the records being loaded will be assigned. Additionally, the credentials for that user must be entered into the context file. If the user is not a member of the appropriate site, then the data load will fail, and an error message will appear.
The adapters populate the MI_SITE_KEY system field with the ENTY_KEY system field associated with the Site Reference value to be populated. On asset records, the Site Reference is stored in the MI_SITE_KEY field, a system field in APM. The EAM Adapters use the Site Name (MI_SITE_NAME) to translate the value to the corresponding Site Reference Key and populate the MI_SITE_KEY field; therefore, you do not need to know the key to be able to populate the site reference. This functionality is important because this value can change from one database to another.
When records are loaded using the Equipment, Function Location, and Work History Adapters, the system will assign the Site Reference Key (MI_SITE_KEY) to the assets using the value designated in the applicable context file (that is, the file for SAP or for Maximo ). The following parameters are used to designate the Site Reference Key value:
- SITE_REFERENCE_EQUIP: Used to populate the Site Reference Key on Equipment records being loaded into APM. The Site Reference Key determines the Site to which the Equipment record(s) will be assigned.
- SITE_REFERENCE_FLOC: Used to populate the Site Reference Key on Functional Location records loaded into APM. The Site Reference Key determines Site to which the Functional Location record(s) will be assigned.Note: The values entered into these parameters should match, because Equipment records are linked to Functional Location records. Therefore, they should have the same site.
These parameters accept two types of values to determine the site reference value.
- Site Name: You can enter the site name directly as defined on the preexisting Site Reference record (i.e., Site 100).
- Column Name: You can enter a column value between two pound symbols (#) to set the site reference. The following columns can be used:
- SAP columns:
- MI_EQUIP000_SAP_SYSTEM_C
- MI_EQUIP000_MAINT_PLANT_C
- MI_FNCLOC00_MAINT_PLNT_C
- MI_FNCLOC00_SAP_SYSTEM_C
For example, if you wanted to use your SAP maintenance plant field as your APM site reference, you would enter #MI_EQUIP000_MAINT_PLANT_C#.
- SAP columns:
- Null: You can leave the value as null. The record will be a global record if a Site Reference value is not mapped in between the tags.
If the assets being loaded into APM are global records, meaning they will not be filtered according to site, then the Site Reference parameters can be left blank. When records are loaded with a null values in their Site Reference parameters, those created asset records will be designated as Global.
After the adapters are run, records designated to be transferred into APM will be assigned to the site defined in the Site Reference parameters.
In addition to Equipment and Functional Location records loaded by the EAM adapters, Work History records and shell records are impacted by site reference functionality as detailed in the following table.
Action | Result |
---|---|
If the Work History Adapter is run after the Equipment or Functional Location Adapter... | The Work History records will inherit the Site Reference Key of their parent Functional Location or Equipment records. |
If the Work History Adapter is run before the Equipment or Functional Location Adapter... | The Site Reference Key will be inherited from the shell record that will be created for Equipment and Functional Location. |
If a shell record is created while loading data... | The Site Reference Key will be the value set in the context parameters. |