SAP Interface Modules
The OGM/Capstone SAP Interface Module implements a number of distinct Interfaces between the RBMI application and SAP® R/3®:
- Create Malfunction Reports in SAP R/3
The user creates Non Conformance records in RBMI for a particular asset. Each Non Conformance record created will also have an entry inserted into the RBMI Interface table, referencing the Non Conformance ID. On a scheduled basis, records in the RBMI interface table will be processed into SAP as malfunction reports (notification type M2). Should any errors occur that prevent successful posting into SAP, the Interface Module writes the error to an error log located on the Interface Module machine and/or alerts users via e-mail. The referenced RBMI Interface table record will be updated to reflect that posting was not successful. If the Interface Module successfully processes the record(s) into SAP, the notification number from SAP will be retrieved and updated into RBMI. The referenced record in the RBMI Interface table will be deleted.
- Create Maintenance Request in SAP R/3
The user creates Inspection Task records in RBMI for a particular asset. Each Inspection Task record created will also have an entry inserted into the RBMI Interface table, referencing the Asset ID and Task ID. On a scheduled basis, records in the RBMI interface table will be processed into SAP as Maintenance Requests (notification type M1). Should any errors occur that prevent successful posting into SAP, the Interface Module writes the error to an error log located on the Interface Module machine and/or alerts users via e-mail. The referenced RBMI Interface table record will be updated to reflect that the posting was not successful. If the Interface Module successfully processes the record(s) into SAP, the referenced record in the RBMI Interface table will be deleted.
- Update Notification Statuses from SAP R/3
On a scheduled basis, and/or on demand, the Interface Module queries a list of Notifications updated since the last query date from SAP, and checks to see if any of the notifications corresponds to a RBMI Non Conformance record. If a match exists, the Interface Module checks to see if the notification status has changed, and/or if a work order has been created in SAP. If either is True, the Interface Module will update RBMI with the updated information.
- Update Work Order Statuses from SAP R/3
On a scheduled basis, and/or on demand, the Interface Module queries a list of Work Orders updated since the last query date from SAP, and checks to see if any of the work orders corresponds to a RBMI Non Conformance record. If a match exists, the Interface Module checks to see if the work order is closed or completed. If either is True, the Interface Module will update RBMI with the updated information.
- Asset Synchronization between SAP and RBMI
On a scheduled basis, and/or on demand, the Interface Module queries a list of Functional Location Assets and Equipment created in SAP since the last queried date. The Interface Module will check to see if these assets already exist in the RBMI system. If these assets do not already exist, the Interface Module will insert these assets into RBMI as either Fixed Equipment, or Relief Devices. For every record created in RBMI, the Interface Module will also alert the user via e-mail. Should any errors occur that prevent successful posting into RBMI, the Interface Module writes the error to an error log located on the Interface Module machine and/or alerts users via e-mail. The referenced error record will also be dumped locally for reprocessing on the next event.
- Asset Synchronization Updates from SAP
On a scheduled basis, and/or on demand, the Interface Module queries a list of Functional Location Assets and Equipment updated in SAP since the last queried date. The Interface Module will check to see if these assets have been de-activated in SAP, and that they exist in the RBMI system. If this is True, the Interface Module will alert the user via e-mail that the referenced assets have been de-activated.
- Retrieve Master Data from SAP R/3
On a user-defined scheduled basis, the Interface Module queries the latest Equipment Type List and Task Code list information from SAP and sends this information to the RBMI Interface tables. The Equipment Type list and Task Code list are data necessary for Interface cross-reference processing between RBMI and SAP.
Functional Highlights of the RBMI Interface Module
The Interface Module contains a variety of features that make it superior to other methods of connecting RBMI to SAP R/3.
- Fast to implement and easy to change, the Interface Module can be quickly and easily modified to support customer-specific requirements since those elements of the Interfaces are separate and easily changed.
- The Interface Module has been deployed against SAP 4.6C but can be quickly and easily modified to support all other major versions of SAP R/3 since the version-specific elements of the Interfaces are separate and easily changed.
- The Interface Module uses the optimal combination of a proprietary SAP Query technology and SAP-provided RFC connectivity technology to provide superior Flexibility, Performance and Reliability.
- Flexibility. In SAP R/3 4.6C there is no BAPI available to retrieve the Notification detail list for the SAP R/3 PM module. The Interface Module SAP Query technology was able to support the required functionality nonetheless.
- Flexibility. Where applicable, SAP supported function modules are used in conjunction with the Interface Module SAP Query technology to retrieve the various required data elements from SAP R/3.
- Performance. The Interface Module is fully multi-threaded and operates as an in-memory process. This combination of design techniques yields an impressive runtime performance that is hard to match.
- Reliability. In order to provide enhanced business process validation the SAP Query technology is used to read data from additional SAP tables that are not supported by any SAP published BAPI.
- Reliability. Notification posting into SAP R/3 using existing Function Modules ensures that the record will be created in SAP regardless of the differences in SAP configuration between various deployments. The Interface Module uses Interface tables to ensure that any records that fail to post can be read and re-processed on the next interface run.
- The Interface Module supports a flexible and sophisticated Error Handling facility. The Interface Module uses a set of re-usable components to handle common functions. Its Error Logging and Audit Trail capability can be activated or de-activated simply and easily. Furthermore, all error messages can be optionally e-mailed to designated administration personnel. Finally, the actual format of the e-mails and log messages can be configured to suit the individual needs of each end customer.
- The Interface Module uses field-proven technology that is patented and SAP certified.
- The Interface Module requires no end-user coding to be deployed.
Glossary of Terms
SAP R/3 RFC
An SAP R/3 Remote Function Call (RFC) is a synchronous communication process method used to call and execute predefined functions within SAP R/3. RFCs are written in the SAP proprietary programming language, ABAPTM (Advanced Business Application Programming), and can be custom written to execute a variety of functions within SAP R/3. RFCs are typically not documented or supported by SAP.
SAP R/3 BAPI
A Business Application Programming Interface (BAPI) is an RFC-enabled function module. It allows transactions to be performed on specific business objects located in the SAP Business Object Repository. A Business Object represents a central real world business object (such as a Purchase Order). BAPIs do not cover all transactions available in SAP R/3, but they are supported by SAP.
