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:
- When oDATA and SOAP APIs not available to integrate S/4HANA Cloud with 3rd party solutions on-Premise and Cloud. Based on individual customer requests, SAP allow customers/partners to usage of BAPIs and IDocs on a temporary basis to integrate your solution wherever the currently available OData and SOAP APIs are not available. Such APIs are Blue listed API’s
- Such requests are restricted to individual customers means, if another customer has similar requirements to consume such APIs they have to request SAP to consume. Such API’s ( BAPIs or IDOCs) have been technically enabled by SAP for this purpose. To get this approval please follow the process described in the Note 2653671
Process Steps:
- Create, schedule, and release production order in the SAP S/4HANA system
- Create and release production order in a Manufacturing Execution System (MES) or shop floor system
- Update production order in an MES and send information back to the SAP S/4HANA system
- Confirm production order in the SAP S/4HANA system
Process Flow:
- Integration of Manufacturing Execution System to Production Operation
- Integration of Manufacturing Execution System to Production Operation
- Integration of Manufacturing Execution System to Production Operation
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:
- SAML Local identity provider certificate of Jam instance.
- SAML Local identity provider issuer of certificate of Jam instance
- Communication user ID
- SAP S4HANA Cloud System
Prerequisites:
- Scope Item 1Y5 should be active. ( The 1BM, BJ5or BJE scope item is a prerequisite for running the 1Y5scope item)
- Configure SAP Cloud connector (integration scenario SAP_COM_0200 (SAP Cloud Connector Integration).
- Implement Communication arrangement SAP_COM_0156
- Before implementing the communication arrangement for SAP_COM_0156, the following interface scenarios need
to be implemented:
- Product Integration (SAP_COM_0009) Additionally, the following scenarios can be implemented:
- Product Life cycle Management – Core Master Data Integration (SAP_COM_0150)
- Product Life cycle Management – Master Data Integration (SAP_COM_0105)
- Classification Systems Integration (SAP_COM_0160)
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:
- A JDK 7 or 8 needs to be installed. Due to problems with expired root CA certificates contained in older patch levels of JDK 7, we recommend that you install the most recent patch level. An up-to-date SAP JVM can be downloaded from the SAP Development Tools for Eclipse page as well. The most recent version is at https://tools.hana.ondemand.com/additional/sapjvm-8.1.028-windows-x64.zip
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.
- The installer informs you that you are now guided through the installation process. Choose Next>.
- Navigate to the desired installation directory for your cloud connector and choose Next>. When doing the installation in the context of an upgrade, make sure that you choose the previous installation directory again.
- You can choose the port on which the administration UI is reachable. Either leave the default 8443 or choose a different port if needed. Then choose Next>.
- Select the JDK to be used for running the cloud connector. The installer will display a list of all JDKs of version 7 that are installed on your machine. If the needed JDK is not listed in the drop down box (for example, if it’s an SAP JVM that is not registered in the Windows Registry upon installation), you can browse to its installation directory and select it. We recommend that you use an up-to-date Java 7 installation to run the cloud connector.
- On this step, decide whether the cloud connector should be started immediately after finishing the setup. If you do not want this now, remove the check from the checkbox. Then choose Next>.
- After all installation options, have been fulfilled, if you want to install, press again the Next> button.
- In up to a few seconds, the installation has been done. To finish the installer, choose the Close button.
- Go to the installed SAP cloud connector folder. Run go.bat file. Run SCCHost.exe
- Continue with the Next Steps section.
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
- On the login screen, enter Administrator / manage (case sensitive) for User Name / Password.
- When you first log in, you must change the password before you continue forwards, regardless of the installation type you have chosen.
- Choose between master and shadow installation. Use Master if you are installing a single cloud connector instance or a main instance from a pair of cloud connector instances.
- You can edit the password for the Administrator user from Configuration in the main menu, tab section Authentication: User Interface
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:
- Usage of BAPIs & IDOCs technically needs to be enabled by SAP for this purpose. To get this approval, please follow the process described in SAP Note 2653671.
- These BAPIs and IDocs are available as is and will not be functionally extended. They will be maintained for a limited period of time. Maintenance of a BAPI/IDoc will end 12 months after availability of an equivalent OData or SOAP Webservices
- The call of BAPIs in S/4HANA Cloud shall be triggered on-Premise via the SAP Cloud Connector installed on-premise.
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.
- BAPI CO_MES_PRODORDERCONF_CREATE_TT
- BAPI_PRODORDCONF_CREATE_TT
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…
- SAP Managed Tags:
2 Comments
