The standard implementation of Celonis SAP Extractor assumes direct communication between the Extractor service and the RFC Module. However, some customers use PI/PO as mediator between all external parties and SAP systems, and therefore direct communication between the Extractor service and RFC Module is impossible.
To make this happen Celonis also supports extraction via PI/PO. In this scenario, the Extractor service will conduct all communications with the RFC module via PI/PO. We can communicate via RFC Adapters, or SOAP endpoints.
For the integration via SOAP Adapter, the customer should create adapters/endpoints in PI/PO and map them to the RFC Functions of our RFC package. Then they should generate WSDL files for these endpoints, which will later be used when setting up the connection between Celonis Platform and SAP.
The following Function Modules should be mapped:
/CELONIS/FM_NEW_EXTRACT
/CELONIS/FM_CANCEL_EXTRACT
/CELONIS/FM_CLEANUP_FILES
/CELONIS/FM_GET_JOB_STATUS
/CELONIS/FM_CONFIG_TEST
/CELONIS/FM_GET_EXTR_FILE_LIST
/CELONIS/FM_GET_EXTRACT_FILE
/CELONIS/FM_DELETE_JOB_LOG
/CELONIS/FM_GET_JOB_LOG
/CELONIS/FM_GET_SYS_INFO
/CELONIS/FM_GET_TABLE_LIST
/CELONIS/FM_GET_CHECKED_TABLES
/CELONIS/FM_GET_TABLE_METADATA
/CELONIS/FM_CL_NEW_EXTRACT (required only for real-time extractions)
/CELONIS/FM_CL_RM_EXTRACT (required only for real-time extractions)
/CELONIS/FM_CL_GET_TABLE_NAME (required only for real-time extractions)
These are part of the Function Groups: /CELONIS/EXTRACTION and /CELONIS/CL_EXTRACTION.
Note
RFC Module should be setup as usual on SAP side for PI/PO connection to work.
The diagrams below describe how the systems communicate with each other.
 |