General Reference

APM Connect Version Compatibility Table

This topic provides the installation files that are required for an APM Connect installation, and the version structure for APM Connect.

Version Structure

Example:EAMSAPV152
Description:Area of APM Connect

(that is, Data Loaders, EAM)

EAM System released against

(that is, SAP, SAP PI, Maximo)

Architecture ReleaseMajor ReleaseMaintenance or Patch Release

The following are examples of how to interpret the versions.

  • EAM SAP V1.5.0 is the fifth major release on the APM Connect V1.x architecture; it can be applied to the EAM system SAP.
  • EAM SAP V1.5.1 is a maintenance release that can be applied to EAM SAP V1.5.0.
  • DL V1.4.0 is the fourth major release on the APM Connect V1.x architecture.
  • Since V4.3.0.2, all the APM Connect Integration options are merged to a common framework, UDLP – Unified Data Loader Process for Dataloaders and EAMs.

APM Compatibility Table

This table includes only the APM versions for which a corresponding APM Connect version was released.

Note: GE Vernova will only support APM Connect Services Version 5.1, Integration Pack (IP) Version 5.1 from the current release. As per the new Technology Replacement notice, the below versions will cease operation upon the Talend license expiration.
  • APM Connect Base version 3.X
APM Framework VersionAPM Connect BaseIntegrated Pack VersionSAP ABAP Version
V5.0.6.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_3)V7.X
V5.0.5.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V5.0.4.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V5.0.3.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V5.0.2.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V5.0.1.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V5.0.0.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V4.6.6.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V4.6.5.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V4.6.4.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V4.6.3.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V4.6.2.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2) V7.X
V4.6.1.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V4.6.0.0.0APM Connect Services V5.1.2.0.0Integration Pack (IP-Release_5_1_2)V7.X
V4.5.0.0APM Connect Base V2.0.0UDLP Version:

UDLP V2.9.0 or V2.8.0 or v2.9.0.1 (with ABAP V7.X)

V4.X
Table 1. SAP ABAP Package Certification Matrix
SAP Certificate NumberCertificate Issue DateCertificate Expiration DateSAP VersionABAP Interface Version (as displayed on the certificate)APM Versions
16649June 26, 2020June 25, 2023S4/HANA 1909V4.X4.4.x, 4.5.x, 4.6.x, (UDLP 3.3.0)
13857October 6, 2020October 5, 2023ERP (ECC) 6 EHP8V7.X4.6.x, 5.x
16864January 21, 2021January 20, 2024S4/HANA Cloud Extended Edition 1909V7.X4.5.x*, 4.6.x, 5.x
17051January 21, 2021January 20, 2024S4/HANA 1909V7.X4.5.x*, 4.6.x, 5.x
17336January 21, 2021January 20, 2024S4/HANA Cloud Extended Edition 2020V7.X4.5.x*, 4.6.x, 5.x
17337January 21, 2021January 20, 2024S4/HANA 2020V7.X4.5.x*, 4.6.x, 5.x
20873October 12, 2022October 11, 2025S4/HANA Cloud Extended Edition 2021V7.X4.5.x*, 4.6.x, 5.x
20874October 12, 2022October 11, 2025S4/HANA 2021V7.X4.5.x*, 4.6.x, 5.x
21395July 20, 2023July 20, 2026S4/HANA 2022V7.X4.5.x*, 4.6.x, 5.x
S4/HANA 2023V7.X5.x
Note: *You must have UDLP 2.9.0.1 or later to use APM V4.5.0.0.0 with SAP ABAP packages of certificate numbers 16864, 17051, 17336, 17337, 20873, and 20874.

Attributes Available for Adding to Notification Creation from APM to SAP

label
MI_GENRECOM_ALERT_GUIDMI_REC_DAYS_BEF_DUE_DT_NOT_NBRMI_REC_ASSET_TYPE_CHRMI_REC_ASSET_ID_CHR
MI_GENRECOM_ALERT_ID_CMI_REC_STATU_CHANG_BY_CHRMI_REC_LAST_CHANG_DATE_DTMI_SM_STATE_OWNER_ID_C
MI_GENRECOM_CASE_GUIDMI_REC_STATU_CHG_BY_NM_CHRMI_REC_CLOSE_COMME_TXMI_SM_STATE_ENTERED_D
MI_GENRECOM_CASE_ID_CMI_REC_WO_INTERFACE_FLAG_FMI_REC_CLOSE_DATE_DTMI_REC_ANALY_ID_CHR
MI_GENRECOM_EQUIP_KEY_NMI_REC_MERIDIUM_TASK_ID_CMI_REC_COMPL_DATE_DTMI_REC_CREATE_SAP_NOTIF_FLG
MI_GENRECOM_FUNCT_LOCAT_KEY_NMI_REC_TYPE_CHRMI_REC_COMPL_FLGMI_REC_WK_REQ_REF_CHR
MI_GENRECOM_SOURCE_KEYMI_REC_WORK_ORDER_NUMB_CHRMI_REC_CREAT_DATE_DTMI_REC_WR_EQUIP_C
MI_REC_CAUSE_ID_NBRMI_REC_LOC_ID_CHRMI_REC_STATU_CHRMI_REC_WR_LOC_C
MI_REC_ERP_01_CD_CHRMI_REC_GENERATE_MERID_TASK_FMI_REC_SHORT_DESCR_CHRMI_REC_NOTIF_TYPE_C
MI_REC_ERP_02_CD_CHRMI_REC_FINAL_STATE_LOCK_FMI_REC_LONG_DESCR_TXMI_REC_TECHNICAL_NUM_C
MI_REC_ERP_03_CD_CHRMI_REC_FINAL_APPRO_ID_CMI_REC_LAST_CHANG_BY_CHRMI_REC_ASSET_DESCR_C
MI_REC_ERP_04_CD_CHRMI_REC_FINAL_APPROVE_NAME_CMI_REC_LAST_CHG_BY_NM_CHREVNT_START_DT
MI_REC_ERP_05_CD_CHRMI_REC_REVIEWER_KEY_NBRMI_REC_RECOR_NM_CHRMI_OPR_REC_CRT_OF_MEAS_LOC_F
MI_REC_ERP_06_CD_CHRMI_REC_ORIG_ENTY_KEY_NMI_REC_PRIORITY_CMI_OPR_REC_SOURCE_ML_DESC_C
MI_REC_ERP_07_CD_CHRMI_REC_PUB_FLAG_FMI_REC_FINAL_APPROVER_KEY_NMI_OPR_REC_ASSET_KEY_N
MI_REC_ERP_08_CD_CHRMI_REC_REVIE_NM_CHRMI_REC_ASST_CL_CHRMI_OPR_REC_SOURCE_ML_KEY_N
MI_REC_ERP_01_DESC_CHRMI_REC_REVIE_CHRMI_REC_ASST_CTGRY_CHRMI_SM_STATE_KEY_N
MI_REC_ERP_02_DESC_CHRMI_REC_REQUI_EQUIP_STATU_CHRMI_REC_BASISMI_REC_SITE_C
MI_REC_ERP_03_DESC_CHRMI_REC_REEVAL_EMAIL_TXMI_REC_AUTHOR_LOCK_FMI_REC_EAM_REF_CHANGE_DATE_C
MI_REC_ERP_04_DESC_CHRMI_REC_IDMI_REC_AUTH_KEY_NBRMI_REC_EAM_REF_CREATE_DATE_C
MI_REC_ERP_05_DESC_CHRMI_REC_EVNTREF_CHRMI_REC_ASSIGNEE_KEY_NBR
MI_REC_ERP_06_DESC_CHRMI_REC_NOTIF_EMAIL_TEXT_CHRMI_SM_STATE_ID_C
MI_REC_ERP_07_DESC_CHRMI_REC_NOTIFY_RP_FLGMI_REC_ASSIG_NM_CHR
MI_REC_ERP_08_DESC_CHRMI_REC_REEVAL_DTMI_REC_ASSIG_TO_CHR
MI_REC_FINAL_ACTIO_TAKEN_TXMI_REC_EAM_SERVICE_REQ_ID_CMI_REC_ANALY_KEY_NBR
MI_REC_STATU_CHANG_DATE_DTMI_REC_IMPAC_CHRMI_REC_AUTHO_CHR
MI_REC_DATE_REVIE_DTMI_REC_RECOR_CHRMI_REC_AUTHO_NM_CHR
MI_REC_REEVAL_FLGMI_REC_NOTIF_AFTER_DD_CHRMI_REC_TARGE_COMPL_DATE_DT
MI_REC_REEVAL_NOTIF_LIST_CHRMI_REC_LOC_SHRT_DESC_CHRMI_REC_MANDA_DATE_DT

About Time Zone Data

APM stores the dates and times of transactions in Universal Coordinated Time (UTC) format. This enables the data to flow through the system in a single time zone format. APM Connect supports the time zones defined in https://docs.microsoft.com/en-us/previous-versions/windows/embedded/gg154758(v=winembedded.80).

To provide information with the time stamp relevant to your operations, the system converts UTC to your time zone by using the time zone information configured in your user definition.

Important: If you change the time zone information configured in your user definition, all the records will reflect the new time zone.

The following sections contain the time zone considerations relevant to specific systems.

Maximo

APM stores the time stamp associated with the data extracted from Maximo in UTC and displays the time stamp based on your configured time zone.

SAP

SAP provides a set of baseline time zone codes, which contain most of the standard time zones across the world. SAP also provides the ability for administrators to define their own custom time zone, as needed. Before you use a customized time zone, you must configure the timezone_control table in APM Connect to include the customized time zone.

SAP defines two types of time zones:

  • System: This time zone is based on SAP Application Server Operating System and is derived from the context file. You cannot modify this type of time zone.
  • User: This time zone is based on the user who created the SAP record. You can modify and store this type of time zone in the SAP user interface.

APM stores the time stamp associated with the data extracted from SAP in UTC and displays the time stamp based on the time zone configured for the user who created the SAP record.

Note: If the data extracted from SAP contains only the date, then APM will assign the time 00:00:00 and adjust the assigned time with the SAP system or user time zone. This may lead to a date mismatch when you choose to display the data in APM. To prevent this, APM stores the assigned reference time stamp as a string within the data, which is hidden by default. If you need this information, you can configure APM to display the data.

Support for Multiple Source Systems

Whether in a cloud environment or an on-premise installation, APM Connect enables you to connect multiple source systems to a single APM system.

There are occasions when you need to connect multiple source systems to a single APM system. For example, when your company acquires another company, rather than immediately attempting to merge two systems together, you need to keep the systems running separately but want to implement strategies centrally. The two systems might be the same type or of different types. You can configure APM Connect to handle either scenario.

The steps to configure these scenarios is similar to configuring a single system; you repeat the steps that define the EAM system records and, after creating the intermediate repository for the first system, run a job that adds the other systems to the intermediate repository with any required extraction filters.

Multiple Source Systems of the Same Type

This scenario is most useful when you all systems you need to support are the same type. The context file configuration for each source system will look the same for the target APM and APM Connect system for all the source systems. The unique parts of the context file are those that describe the particulars of the source system, for example, the system ID and filters used.

Multiple Source Systems of Different Types

Use this scenario if you need to support multiple disparate systems, for example, an SAP and a Maximo system. In this case, you will need to configure context files for each different type of source system, each pointing to the same target APM and APM Connect system. This does not preclude having multiple systems of a specific type (for example, one SAP, one ServiceMax, and two Maximo).

Considerations

There are some things to consider when connecting multiple source systems to a single APM with APM Connect:

  • You must make sure that each source system has a unique system ID.
  • The logs will contain the messages from all of the source systems. Each message will identify the source system using the system ID.
  • Some source system types have unique requirements that must be performed for each source system. For example, you must run the Static Data job for all SAP systems.
  • Each source system in a cloud environment will need an intermediate repository, even though they are communicating with a single tenant.
  • Do not schedule running the same adapter job types (for example, functional location extractions) simultaneously from different source systems.

Support for Multiple Culture Settings from a Single Source System

APM Connect enables you to send data to APM from a single source system that supports plants using different language or extraction requirements.

Important: This feature is not supported for Technical Characteristics, Work Management, Asset Criticality Analysis, Asset Strategy Management, or Asset Strategy Implementation.

Globalization has increased the need to improve management of assets in different culture settings. Your solution may involve including these new plants in a single source system that communicates with APM but requires the data to be presented to the user in their native language. You can accomplish this by configuring APM Connect so that the plants that require specific languages or extractions appear to be different source systems, one for each language or extraction requirement. This capability provides a better user experience for all users of APM regardless of their location.

A key advantage of this support is that you can combine your source systems and then configure APM Connect to extract the data correctly.

Considerations

  • The user defined in the source system that communicates with APM must use the same decimal notation.
  • You must have unique system IDs and the correct language parameter value or extraction requirements for each plant.
  • You must configure filters to make sure that the data is routed correctly to the specific location.