Background:
When there are no white listed APIs available that can be consumed by the customer to integrate S/4HANA Cloud system to integrate with an existing on-premise non-SAP(MES) legacy system.
In such cases, customer advised to use existing Blue listed API’s to develop an interim solution for an integration with legacy system.
How to Guide:
To start with, SAP has provided following scope item which should be activated to have an integration.
IY5 – Integration of Manufacturing Execution System to Production Operation – https://rapid.sap.com/bp/scopeitems/1Y5
This scope item provides an integration of SAP S/4HANA Cloud with an on-premise third-party Manufacturing Execution Systems (MES) to production operation.
This scope item provides how to integrate a MES system directly into SAP S/4HANA, giving manufacturing staff a clear overview of production operations and improving analytical capability for the management team. SAP S/4HANA is the system of record for all master data. An MES or a shop floor system is the system of record for all work in progress (WIP) data.
What are Blue Listed API:
Process Steps:
Process Flow:
Configuration
Additional configuration steps that have to be carried out by customers in order to activate the Integration of Manufacturing Execution System to Production Operation (SAP_COM_0156). As these configuration steps are customer-specific, they cannot be delivered by SAP, and must be carried out by the customer.
This communication scenario provides end points (inbound and outbound), which are needed to integrate an on-premise third party MES solution (Manufacturing Execution System) to production operation through ALE IDocs, BAPI and OData call
Required Information:
Prerequisites:
to be implemented:
Communication Arrangement:
A communication arrangement needs to be activated in SAP S/4HANA for communication with web services.
SAP_COM_0156- Integration with Manufacturing Execution System to Production Operation
Communication User :
A business user with a business role must exist. The business role must contain the business catalog
SAP_CORE_BC_COM (Communication Management).
Communication System:
Prerequisite: Before implementing the communication arrangement for SAP_COM_0156 the SAP Cloud Connector (integration scenario SAP_COM_0200 (SAP Cloud Connector Integration)) needs to be configured.
Steps for Installation and Configuration of SAP Cloud Connector
SAP Cloud Connector:
SAP Cloud connector, connects the cloud applications in SAP HANA Cloud Platform and existing on-premise systems. The Cloud connector can be installed and runs as on-premise agent in a secured network and acts as a reverse invoke proxy between the on-premise network and SAP HANA Cloud Platform.
For more understanding of the SAP Cloud connector, please refer to
https://blogs.sap.com/2015/07/13/cloud-connector-a-brief-guide-for-beginners/
Prerequisites:
Download the SAP cloud connector from the following link. https://tools.hana.ondemand.com/additional/sapcc-2.10.0.1-windows-x64.msi
Installer Scenario
Start the <sapcc-<version>-windows-x64.msi> installer by double-clicking it.
Next Steps
In a browser, enter: https://<hostname>:8443, where <hostname> is the host name of the machine on which you have installed the cloud
connector. If you access the cloud connector locally from the same machine, you can just enter localhost. https://localhost:8443
Configure a Service Channel for RFC(Cloud Connector)
Communication Arrangement:
The administrator user has the catalog role ID SAP_BCR_CORE_COM. In this step you will create new communication arrangement by selecting SAP_COM_0. Here you will provide Communication system and technical Communication user created earlier for the integration.
In the Additional Properties section, in the Replication Model field, enter a name for the replication model that you wish to create for this IDoc. If you have enabled job execution, choose a Replication Model (I for initial replication or C for change replication)
Define Filter criteria:
In the SAP S/4HANA Cloud solution, the delivered order types are set by default to ME distribution. Therefore, by activating this integration scenario all orders will automatically be distributed to your ME system if you do not define special filter criteria. Consequently, order confirmation can no longer be carried out within the SAP S/4HANA system, but needs to be done in your ME system and sent back to the SAPS/4HANA Cloud system
To define filter criteria, your user needs to include the business role SAP_BR_ADMINISTRATOR_DATA_REPL
Integrate SAP S4HANA Cloud with 3rd Party Application:
oDATA and SOAP Web Services are offered as a means to integrate S/4HANA Cloud with 3rd party solutions on-Premise and Cloud. However, for exceptional cases and based on individual customer requests, SAP admit usage of BAPIs and IDOCs on a temporary basis to integrate your solution wherever the currently available OData and SOAP Web Services are not sufficient. This admittance is restricted to individual customers and to a well-defined set of BAPIs and IDOCs, which have been technically enabled by SAP for this purpose.
By using traditional APIs:
OData and SOAP web services are offered to integrate SAP S/4HANA Cloud with on-premise and cloud third party solutions.
For exceptional cases, usage of BAPIs and IDocs on a temporary basis to integrate your solution wherever the currently available OData and SOAP web services are not sufficient.
IMPORTANT NOTE:
Business Applications Programming Interfaces(BAPIs):
By giving the current situation, SAP has provided two BAPI’s for MES integration. Below are the blue listed APIs from SAP.
The BAPI : BAPI CO_MES_PRODORDERCONF_CREATE_TT, is special API, which can be used if the other MES system is SAP MES(On premise).
The BAPI: BAPI_PRODORDCONF_CREATE_TT, this Blue API can be used if the other system in non-SAP (3rd Party) MES system with limited usage and the customer has to open a ticket by note 2653671 as pointed out earlier. This is absolutely necessary because of legal aspects.
Conclusion:
It’s always recommended to check for White listed/Public APIs available in SAP API HUB for S4HANA Cloud. If there are no such APIs to utilize for your customer needs then on condition basis check for IDOCs or BAPIs as described above.
Hope this blog helps you with required information…
Wish You Happy learning…
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
7 | |
5 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |