General Reference

SAP Transactions-Quick Reference

The following table provides a list of SAP transactions and their functions.

This transaction:...Lets you:
/n/MIAPM/MIPROView a list of Predix Essentials-specific steps that can be performed in SAP.
/n/MIAPM/MANAGE_PARAMSAccess and manage the /MIAPM/PARAMS table.
/n/MIAPM/MANAGE_TSKCNFAccess the /MIAPM/TASK_CNF table.
SM37Check the status of a background process.
IW43Validate SAP Confirmations against that data in Predix Essentials 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)
  • 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)
  • 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 ObjectDescription
C_TCLA_BKAAuthorization for Class Types
I_AUARTPM: Order Type
I_BEGRPPM: Authorization Group
I_BETRVORGPM: Business Operation
I_INGRPPM: Maintenance Planner Group
I_KOSTLPM: Cost Centers
I_QMELPM/QM: Notification Types
I_SWERKPM: Maintenance Plant
I_WERKPM: Maintenance Planning Plant
S_BTCH_JOBBackground Processing: Operations
S_DATASETAuthorization for File Access
S_LOG_COMRequired if file transfer is SFTP/SCP. For server mode this authorization is not required.
S_RFCAuthorization Check for RFC Access
S_TABU_NAMTable Access with Generic Standard

RFCs Required

APM Connect must have access to the RFCs listed in the following table.

/MIAPM/*RFC_GET_FUNCTION_INTERFACESYSTEM_RESET_RFC_SERVER
CLAF_CLASSIFICATION_OF_OBJECTSRFCPINGRFC_PING
DDIF_FIELDINFO_GETSYSTEM_RESET_RFC_CONNECTION

SAP Tables Required

APM Connect must have access to the tables listed in the following table.

/MIAPM/*CRHDJESTPRPST353I_TTGSBT
AFVVCRTXJSTOQMELT356_PTJ02
AFKOCSKTKLAHQMFET356_TTJ02T
AFRUCVERSKSMLQMMAT357TJ30
AFVCEAPLKSSKQMURT357A_TTJ30T
AFVVEQBSMAKTQPCTT357M_TTKA01
AUSPEQKTMHISSWORT370C_TTQ80
BGMKOBJEQUIMHIOT001T370F_TTQ80_T
CABNEQUZMMPTT001WT370K_TVIAUFKST
CABNTIFLOMPLAT003PT370UVIQMEL
CAWNIFLOSOBJKT006TAPLVIMPLA
CAWNTIFLOTPLAST006ATCLAVIMPOS
COBKIFLOTXPLKOT024ITCURC
COEPILOAPLPOT350TCURR
COVPINOBPMCOT352B_TT499S

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 Predix Essentials Predix Essentials, Roles are assigned to Security Users through permission sets.

Important: Assigning a Security User to a Role grants that user the privileges associated with all of the Security Groups that are assigned to that Role. To avoid granting a Security User unintended privileges, before assigning a Security User to a Role, be sure to review all of the privileges associated with the Security Groups assigned to that Role.
Security GroupRoles
MI SAP Interface AdministratorNone
MI SAP Interface UserNone
The baseline family-level privileges that exist for these Security Groups are summarized in the following table.
FamilyMI SAP Interface AdministratorMI SAP Interface User
Entity Family  
ConfirmationView, Update, Insert, DeleteView, Update, Insert
EquipmentView, Update, Insert, DeleteView, Update, Insert
Functional LocationView, Update, Insert, DeleteView, Update, Insert
SAP SystemView, Update, Insert, DeleteView
Site ReferenceViewView
Work HistoryView, Update, Insert, DeleteView, Update, Insert
Work History DetailView, Update, Insert, DeleteView, Update, Insert
Relationship Families  
Equipment Has EquipmentView, Update, Insert, DeleteView, Update, Insert, Delete
Functional Location Has EquipmentView, Update, Insert, DeleteView, Update, Insert, Delete
Functional Location Has Functional Location(s)View, Update, Insert, DeleteView, Update, Insert, Delete
Has ConfirmationView, Update, Insert, DeleteView, Update, Insert, Delete
Has Event DetailView, Update, Insert, DeleteView, Update, Insert, Delete
Has SAP SystemView, Update, Insert, DeleteView, Update, Insert, Delete
Has Work HistoryView, Update, Insert, DeleteView, Update, Insert, Delete
User AssignmentView, Update, Insert, DeleteView, 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 Predix Essentials, 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.

Important: A Site Reference record corresponding to your SAP System(s) must exist in Predix Essentials before you can transfer records.

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.

ColumnDescription
AUTOJOIN_IDSurrogate ID used to uniquely identify a row; i.e., the primary key.
BATCH_NAMEWhen 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_NAMEThe name of the temporary table that will be created for this row. This name will be concatenated by the load UUID.
SQL_EXECUTION_ORDERWithin a batch, the value in this column defines the order in which the SQL statements will be executed. Lower numbers will be executed first.
SQLThe 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 Predix Essentials 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 the topic 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 Predix Essentials column used to store Site Reference values. Unless you have customized the Predix Essentials database, this value should be MI_SITE_NAME.

APM_SITE_REFERENCE_FAMILYThe Predix Essentials 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 Predix Essentials 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.

  • Enter *Global* to assign the site as global
  • Enter the name of a site to assign records to that site.

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.
Note: The SAP PI Adapters determine if SAP PI server will be used via the FILE_MOVE_USE_PI parameter in the context file. If the parameter is true, then SAP PI will be used to copy files from your SAP server to your APM Connect server. If it is false, SAP PI will not be used to copy files from your SAP server to your APM Connect sever. In both configurations however, the SAP PI server will be used to proxy RFC calls.

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.

Note: Using active directory to manage the service account is recommended.

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:

Tip: When the shares are created and permissions configured correctly, run the equipment job for a single equipment ID. This is a quick and easy way to check that permissions are set up correctly. After you run the job, a file will be created using the SAP service account, then opened and read by the APM Connect system.
Volume (Disk, Share, LUN)Access Control
NAS/SANVendor specific user mapping (i.e. NetApp), or active directory integrations.
Windows Users/Groups permissions are defined in Active Directory.
UnixActive 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 Predix Essentials 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.

Note: If you using SAP PI, Classification and Characteristic synchronization are not supported.

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 Predix Essentials 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.

Note: The System ID field is available on the baseline EAM System datasheet, but the CMMS System ID field is not available on the baseline CMMS Classification Type, CMMS Classification, or CMMS Characteristic datasheets.

When you run the Equipment Characteristic Extraction Interface or the Functional Location Characteristic Extraction Interface, Predix Essentials needs to determine which specific characteristics to extract from that system. To do so, it evaluates the CMMS Characteristic records that exist in your Predix Essentials 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 Predix Essentials.

Note: This site filtering configuration applies only to SAP PI deployment. If you are deploying the SAP Adapters, site filtering is handled by modifying the autojoin_control table.
Important:
  • Site Reference records must exist in your Predix Essentials 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 Predix Essentials, 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 Predix Essentials. 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 Predix Essentials. 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 Predix Essentials. 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.

  1. Site Name: You can enter the site name directly as defined on the preexisting Site Reference record (i.e., Site 100).
  2. 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 Predix Essentials site reference, you would enter #MI_EQUIP000_MAINT_PLANT_C#.

  3. 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 Predix Essentials 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 Predix Essentials 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.
Note: If you are using multiple SAP Systems, you must set up a context file for each system, and then designate the appropriate site(s) for each EAM Systems.