Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
Back to Library

Configuring the Maximo Enterprise Adapter for SAP Applications without SAP NetWeaver Process Integration 

Wed March 18, 2020 08:32 AM

The standard implementation of the Maximo Enterprise Adapter for SAP Applications uses SAP NetWeaver Process Integration (PI) for integrating between Maximo Asset Management and SAP ERP. You can configure other middleware, such as WebSphere Application Server, to provide the integration.

To integrate without SAP NetWeaver PI, you must replicate the contents of the SAP NetWeaver PI on the middleware server, specifically the mapping and technical routing content. In addition, you must configure logical ports on SAP ERP and import function module definitions from SAP ERP into the middleware server.

Refer to the following documentation:
SAP NetWeaver Process Integration documentation, available on the SAP NetWeaver website.
Maximo Enterprise Adapter for SAP Applications System Administrator Guide, available on the Maximo Enterprise Adapter for SAP Applications information center

Configuring the processing of transactions from Maximo Asset Management to SAP ERP

There are two options for configuring transaction processing from Maximo Asset Management to SAP ERP.

Maximo Asset Management to SAP ERP - Function modules and RFC

 

Use the import tools provided with the middleware server to import function module definitions. The middleware server can then use the Remote Function Call (RFC) protocol to call the relevant function modules on SAP ERP. This option requires minimal configuration but all mapping and technical routing occurs on the middleware server.		  

Maximo Asset Management to SAP ERP - Function module web services and HTTP

 


Publish each function module as a web service, generate a web services description language (WSDL) file, and import it into the middleware server. The middleware server can then use Hyper Text Transfer Protocol (HTTP) to call relevant web services on SAP ERP. This option requires some configuration but results in less processing activity on the middleware server.

  

Configuring logical ports on SAP ERP to process batch transactions from SAP ERP to Maximo Asset Management

 


ABAP batch reports use client proxy classes to send data from SAP ERP. These proxy classes, by default, point to the corresponding service in SAP NetWeaver Process Integration. To send data to an alternative destination, use the lpconfig transaction to define a default logical port (endpoint) for each client proxy class. SAP ERP can then provide a WSDL file for a service, for example SAP_GLACCOUNTS_TOMX, for import to the middleware server. The middleware server can then use HTTP to send the transaction to Maximo Asset Management.

Logical ports required for services

You must configure the following logical ports to enable processing of batch reports:

ZCO_SAP_COPOSTINGS_TOMX ZBCXIREPR014
ZCO_SAP_DOMAIN_TOMX ZBCXIREPR008, 009, 011
ZCO_SAP_GLACCOUNTS_TOMX ZBCXIREPR001,002,003,006,012
ZCO_SAP_INFORECORD_TOMX ZBCXIREPR013
ZCO_SAP_LABORHOURS_TOMX ZBCXIREPR160
ZCO_SAP_LABOR_TOMX ZBCXIREPR150
ZCO_SAP_MATERIALS_TOMX ZBCXIREPR100
ZCO_SAP_PURCHREQ_TOMX ZBCXIREPR005
ZCO_SAP_VENDORS_TOMX ZBCXIREPR007
ZCO_SAP_ACTIVITY_TOMX ZBCXIREPR170
 

Configuring the processing of real-time transactions from SAP ERP to Maximo Asset Management

Real-time transactions from SAP ERP to Maximo Asset Management use a combination of IDocs and function modules. There are two options for processing real-time transactions from SAP ERP to Maximo Asset Management.

SAP ERP to Maximo Asset Management - IDoc processing with function modules

 

Use the import tools provided with the middleware server to import function module and IDoc definitions. When it receives an IDoc from SAP ERP, the middleware server calls a function module on SAP ERP which extracts the details from the document. The middleware server then calls the function module that filters the details and forwards the filtered information to Maximo Asset Management via HTTP. This option requires minimal configuration but most processing occurs on the middleware server.		  

SAP ERP to Maximo Asset Management - IDoc processing with web services

 

Publish the function modules that extract message information and filter information as web services, generate a WSDL file, and import it into the middleware server. When it receives an IDoc, the middleware server can then use HTTP to call the relevant web services on SAP ERP. This option requires some configuration but results in less processing activity on the middleware server.		  

 




#Maximo
#MaximoIntegrationandScripting
#AssetandFacilitiesManagement

Statistics
0 Favorited
39 Views
0 Files
0 Shares
0 Downloads