In this topic i will talk about integration design between SAP and None-SAP via staging tables. I would like to tell you first, this topic not only talk about SAP Process Orchestration but also tell you general concepts when you decide build integration landscape and consult to your customers.
Continue serial of SAP IDoc articles, in this topic i will show you detail information of SAP IDoc header. It will help you transfer or receive data between SAP PO and SAP ERP | SAP S4 HANA.
In last few years, i faced issue with SAP PO, it took me one month to identify what is root cause of issue. That is very hard time for me. It happened in my customer production system and i have to check data duplication every day. Now i would like to share with you what is really happened in system.
In this topic, i will show you list of roles and permission you need to grant to users who use SAP CAR POS DTA (Point of Sales Data Transfer and Audit) for administration and monitoring.
There are one small note when you do interface data between SAP and None-SAP systems with files adapter scenario. That is “How to design folders structure for Outbound and Inbound Data” then easier for managing partners, permission and archiving files data.
There are two points we need to consider when design folders structure:
This article will show you full flow of sales integration from legacy system to SAP CAR, SAP ERP and SAP BW. This article to help you guys who do SAP PO and SAP POSDM | CAR POSDTA consultant understand full system landscape of objects will be integrated between individuals system.
This article, i will show you overview of SAP IDoc concepts and details of IDoc structure. After this topic, functional and SAP PO consultant can understand how to do Inbound and Outbound interface via IDocs.
Today, i will show you step by step to monitor outbound IDocs from SAP ERP to SAP PO and receiver protocol is File system (FTP / SFTP / Shared Folders).
In the ERP system landscape, SAP ERP is core system where master data, transaction data managed. In some scenarios, we need send master data and transaction data to partners system. Master data can be material master, vendor master, customer master, sales price, promotion etc… all kind of objects SAP had standard message type following EDI standard.
When SAP ERP integrate to partners system, we need to know data flow and where would be check when data wasn’t sent to destination system.
In this topic, i will show you ways to check outbound material master from SAP S/4 Hana to POS system via SAP PO with integration scenario is: SAP S/4 -> SAP PO -> SFTP -> POS (Point Of Sales), base on this example, you can do checking to another outbound IDocs as well.
In this article, i will share you how to make interface webservice with sender is SOAP adapter and Receiver with REST adapter scenario, hope can help you to implement SAP PO.
In this demonstration, i will make simple login function call from SAP ERP to third party using REST and HTTP.
Now i will show you how import IDOC Metada from SAP ERP system. The question is why do we need import metadata and what is metadata ?
Metadata
Metadata is data structure of source or destination system. Example, sales order (SO) object in SAP ERP, there are many group of information in SO like header, items, discount, payment, pricing condition, delivery information etc… all group of information displayed in data structures. And object’s structure of SO, SAP call “Message Type“. Message type content all information of SO. When source system want transfer SO to SAP ERP, SAP PO need read SAP ERP SO “Message Type” and provide values for each mandatory fields.