<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_Implementing_SAP_Order_Management_Sourcing_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2024-12-16T07:30:56.000Z

Explaining Data Ingestion Objects

<div id="content"><div class="parentsection"><div class="section"><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_vh4at6r6"></div></div><p tabindex="0">To use the features of&nbsp;SAP Order Management for sourcing and availability, you must upload data into the system using Data ingestion for industry cloud Solutions.</p><p tabindex="0">Data ingestion for industry cloud solutions enables secure and reliable data integration with SAP and non-SAP systems. It allows supported industry cloud solutions to consume data from a shared data foundation instead of integrating with the source systems individually.</p><p tabindex="0">Data is replicated from SAP and non-SAP source systems to data ingestion for industry cloud solutions with or without passing through the Cloud Integration capability within&nbsp;SAP Integration Suite&nbsp;for data mapping. The communication is secured using the HTTPS protocol. Data is then consumed by the supported industry cloud solutions.</p><ul style="list-style-type:disc"><li tabindex="0">If you use&nbsp;SAP S/4HANA&nbsp;as the source system with which we provide out-of-the-box integration, you can use the Data Replication Framework (DRF) to generate data that can be readily used by the APIs.</li><li tabindex="0">If you use some other SAP source system or a non-SAP one, you need to convert your data to the JSON format so that it can then be used by the data ingestion APIs.</li></ul><p tabindex="0">In either case, you can optionally use the&nbsp;SAP Integration Suite&nbsp;to map the data to the desired structure before sending it to the data ingestion capability.</p><p tabindex="0">Further Technical details are provided in Module 4: <i>ICOMF4 - SAP Order Management Foundation and SAP Order Management Sourcing and Availability - Technical Baseline</i>.</p><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Flowchart illustrating data ingestion from SAP and non-SAP systems, highlighting SAP Order Management for sourcing and availability." alt="Flowchart illustrating data ingestion from SAP and non-SAP systems, highlighting SAP Order Management for sourcing and availability." src="/service/media/ICOMF3_02_en-US_media/ICOMF3_02_en-US_images/ICOMF3-01-U2L1O1T1_001.png" tabindex="0"><div class="imageCaption"></div></div></div><div class="parentsection"><div class="section"><div tabindex="0"><h3>APIs</h3></div><p tabindex="0">Data ingestion for industry cloud solutions provides you with a set of APIs to ingest data from source systems to your industry cloud solutions.</p><p tabindex="0">These APIs are available on the SAP Business Accelerator Hub and come with sample JSON files, schemas, and a try-out tool. You must ensure that data is sent to the APIs in the correct format.</p><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Dashboard showing various REST APIs for data ingestion, including product plants and inventory snapshots, with active status indicated." alt="Dashboard showing various REST APIs for data ingestion, including product plants and inventory snapshots, with active status indicated." src="/service/media/ICOMF3_02_en-US_media/ICOMF3_02_en-US_images/ICOMF3-01-U2L1O1T1_002.png" tabindex="0"><div class="imageCaption"></div></div></div><div class="parentsection"><div class="section"><div tabindex="0"><h3>Data Entities</h3></div><p tabindex="0">Data entities for data ingestion to SAP Order Management for sourcing and availability:</p><div tabindex="0"><h4>SAP S/4HANA ERP</h4></div><ol><li tabindex="0">Product details (Product ID, Description, and so on)</li><li tabindex="0">Site Basic details (Name, Address, and so on)</li><li tabindex="0">Inventory Snapshot (Store Inventory)</li><li tabindex="0">ATP Snapshot Time series (DC Inventory)</li><li tabindex="0">Product/Site Details (Safety Stock)<div tabindex="0"><h4>Transportation Aspects (For example: Third party TM System)</h4></div></li><li tabindex="0">Transportation Zones</li><li tabindex="0">Transportation Lanes</li><li tabindex="0">Transportation Service Codes (for example, Express, Normal)<div tabindex="0"><h4>Other Site Data (For example: Third party External WMS)</h4></div></li><li tabindex="0">Site Transportation Zone</li><li tabindex="0">Site Maximum Capacity or Maximum Consignment Capacity (Max number of orders per day)</li><li tabindex="0">Site Pick Pack Cost</li></ol><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Diagram showing the flow of commerce availability and sourcing requests between OMSA, SAP S/4HANA, and third-party systems." alt="Diagram showing the flow of commerce availability and sourcing requests between OMSA, SAP S/4HANA, and third-party systems." src="/service/media/ICOMF3_02_en-US_media/ICOMF3_02_en-US_images/ICOMF3-01-U2L1O1T1_003.png" tabindex="0"><div class="imageCaption"></div><div tabindex="0"><h3>Data Ingestion App</h3></div><div class="formalblock"><p tabindex="0">Data ingestion for industry cloud solutions provides you with a set of APIs to ingest data from source systems to your industry cloud solutions.</p><p tabindex="0">These APIs are available on the SAP Business Accelerator Hub&nbsp;and come with sample JSON files, schemas, and a try-out tool. You mustsure that data is sent to the APIs in the correct format.</p></div></div></div></div>

Data Ingestion Overview

Implementing SAP Order Management Sourcing and Availability

<div>This video provides an overview of the data ingestion unit in the industry cloud. It explains how data entities are ingested and consumed by various industry cloud solutions, with a focus on OMSA. The video also discusses the available APIs for data ingestion and showcases the data entities required by OMSA. If you're interested in data ingestion and industry cloud solutions, this video is for you.<br><br># This description was auto-generated #</div>

Giving an Overview of Data Ingestion

This is the data ingestion unit. So I'll give an overview and then I will go data entity by data entity, right, product, side, inventory, and hopefully some of the questions that you will see answer some of the questions that you raised already. So this is just the, is the second unit overview of data ingestion overview. Let me put that presentation mode, and she'll present to you. Yeah, hopefully you can see my screen now. Yeah. Yeah? Yeah. OK, good. Now, what I'm going to discuss now, or I'm going to go through that, is this layer, data ingestion layer, inside the industry cloud. It's a separate application, and data ingestion is used not only for OMSA, but data ingestion also provides data to other industry cloud solutions. And for example, the product details is not only consumed by OMSA. It is also used and consumed by other industry cloud solutions, also the side details. So what is different is that what is similar to all the different industry cloud solutions from this data ingestion perspective, And tomorrow, you will see technical details about data ingestion. But what is different is that what is similar is that from the ERP, master data product site are feed equally in one way only into the data ingestion layer. But then OMSA will pick up only three or four attributes that are required from the product and three or four attributes from the site. Other industry solutions, maybe Osta, or OMF, or any other, they might consume more attributes from this data ingestion. But for you to understand, data ingestion is a common layer across multiple industry cloud solutions. And it's the industry cloud solution which basically consumes only a part of the product attributes and a part of the site attributes that are available in the data ingestion layer. And then when you replicate, for example, a product or a site from the ERP, from S4HANA into data ingestion, this is just one process, only one process, and replicates all the product attributes that are going to be stored in industry clouds in data ingestion. And there might be a hundred attributes for the product replicated into data ingestion. But then only four of them will be consumed by OMSA. We are going to focus now on this area, data ingestion. And it is important. So OMSA use only a few objects of data. So it use, from a master data perspective, use product details. And mainly, it's just the product ID and the unit of measures. It uses site details, so the site address, for example, and the site ID. And so every new product created in the ERP has to be feed to OMSA through the master data so that OMSA knows the product and knows the site. And then this is from master data perspective. And then inventory figures, they require, And there are two objects to replicate. One is named ATP Snapshot, which is considered the time series and is typically used by distribution centers. And the inventory snapshot, which is the store inventory. And then in addition to these four, we have also other site details, for example, the site pick and pack cost. There was a question there. So through this, there will be a third party system. And using an API, you can feed the site peak impact cost, the site capacity. So those site details that are not available in the ERP. And the same with transportation lanes, right? OK, good. So those are the major six objects, right? Transportation lanes, and there are three of them within transportation lanes. site capacity attributes, and then site address attributes, product details, and inventory. Now, the way we ingest data into OMSA is you might have an SAP system, ERP, or a non-SAP source system. Another ERP, or a transportation manager, or a warehouse manager, or a store system. Now, that's your source of information, right? And if it is an S4HANA system, you can use data replication framework, which is a process available in S4HANA to replicate the data. And if it is not an S4HANA system, then you have available APIs for each of the objects. There is available APIs so that from an external system, you can feed or ingest data into OMSA. We are not using S4HANA. There is an API by which you can ingest product details into OMSA or site details. So there is a choice. And if you are using, depending on your architecture, and I didn't cover those details in the initial architecture slide, there is a choice of use directly the API to ingest data into data ingestion solutions. Or you could have in the middle SAP, for example, an integration suite or your own suite, integration suite. So this is optional, right? So if you want to do mappings from the source into the structuring data ingestion, you might need, if you are using SAP BTP, you might use SAP CPI or SAP integration suite to map data from your ERP or non-ERP system into data ingestion, right? Or there is a possibility also some of the objects if you do not require mapping, for example, for product and site and inventory, there is an out-of-the-box integration using DRF which do not require any mapping. But that might suit some of our customers and then some of our other customers might require a mapping in the middle. So there is an optional component from the source system. You could use a mapping layer or an integration layer. And then data arrives into data ingestion for industry cloud. And this is a common layer for a number of industry cloud solutions. And then is ONSA who will consume some of the data available in data ingestion layer. What you control and when you are doing an implementation, what can be controlled by the project or by the user, by a particular customer is how do you ingest into data ingestion. But then the way that we ingest from the data ingestion to the solutions, this is something which there is no controls. So it's usually replicated every few minutes, and that is defined in your setup. But there is no control about. So OMSA already knows that they need to pick up three or four product attributes from the data ingestion product entity. That is already not configurable, if you like. What you can configure is what arrives into data ingestion. Now, as I explained, so there is a number of available APIs for ingesting data to OBSA. In the SAP API hub, if you search by data ingestion for industry cloud solutions, you will see a lot of a number of APIs to ingest a number of data entities. And for example, plans is one, right? So this is the API that you will need to use to ingest sites into OMSA. If you are not doing so, directly from an S4, replicating from an S4 HANA system. If you have a vendor stock, for example, or a warehouse which is not owned by your company, it's a third party stock and you want to ingest ATP inventory from that external warehouse into OMSA, you will need to use this ATP snapshot API. If that stock of a particular warehouse is available in your ERP, then you will be able to use the ERP stock replication process, and you will not need to use the API. But APIs are available for each and every of the data objects that needs to be ingested into OMSA. And you can find them, you just access the Business Affiliator Hub or the former API Hub in SAP. You put in the search, put on data ingestion for industry cloud solutions. And then you will see all of them available here. But OMSA only use a few of them. Those are the data entities that you need to ingest into OMSA. And it's 11 data entities. Sorry, it's not 11. It's actually nine, because the last three ones are just considered as a one entity. Let me try to explain. So the first data entity is product, details. You can use the RF process, or you can use an API to ingest these two, to OMSA. Sorry, this slide is not correct. It should say di, right, data ingestion, right? Yeah, but anyway. So product is one. The second one is site-based basic details. It's a second entity. So this can be used. There is an object in S for HANA where you can feed site details into data ingestion and then into OMSA. For example, an address, a site description, a site name, a site ID. Yeah. The third object is product site details. So there is a way of feeding also product site attributes or details into OMSA. For example, a safety stock is feed using the product site details from S4HANA. Sorry, that was the number five. Yep. Number three is inventory snapshot. So this is store, store inventory. Number four is ATP snapshot, time series. So those are the five data entities that you could feed from an S4HANA system. Now, data which is not maintaining S4HANA and needs to be feed into data ingestion and then into, and later we'll arrive into OMSA. You can use APIs for that And there are transportation aspects, right? And there are three transportation aspects. There are transportation service codes, for example, express delivery or standard delivery. So there are, yeah. You need to feed that to OMSA so that OMSA knows what are the available shipping methods or service codes, right? And then you can, in the sort of thing request we will see later, you can filter some of the sites based on, sorry, or you can use that information in the surfing engine, in the surfing algorithms. So transportation service codes, transportation zones, and transportation lanes. So those are three transportation aspects, three objects that you need to feed into data ingestion into OMSA. And then you have, let's say, from S4HANA, you feed basic site details, address, ID. But there are a number of aspects, like for example, pick and pack cost, or the site maximum capacity, or the transportation phone, which basically the site is assigned to, is not in the diagram, but you're required to use the API to feed that, right? So to complete the entire picture of the site information in OMSA, you need to use two feeds, one from S4HANA, giving the address, giving the site ID. And then you need to enrich that site record with site capacity, peak impact cost, all the attributes that are using the sorting engine and that are not sitting in the S4HANA. And so you need two sources to feed site details into OMSC. And these other site data is the site transportation zone. So in which transportation zone is this site sitting? The maximum number of orders, the maximum capacity, maximum consignment capacity, there are different names for the same object, especially the maximum number of orders. and the pick and pack cost. Those are the data entities that OMSA requires. So does OMSA requires any other? I mean, there will be multiple data entities in data ingestion, but they will not be consumed by OMSA. Only those 11 will be consumed by OMSA. And let me just do a demo, and then we can do a break. And I need to share now my screen, right? Yeah, let me then do this. Oops, sorry, my mistake. Share my screen. Now I'm going to share my screen directly. Yeah, okay. I have completed this. Let me remove this. And let me go into Yeah, so But in terms of data ingestion, as I said, right, so if you go to the SAP Business Accelerator, can you see my screen? Sorry. Can you see my screen, website, SAP Business Hub? Yes, SAP Business Hub. So you need to search for industry cloud, for example, right? And then you will find data ingestion for industry cloud solutions. And then those are all the data entities available in industry cloud solution. In that layer within the industry cloud, which is named data ingestion, right? For example, that is ABC indicator code. So that is consumed not by OMSA, consumed by another. So there are only some of them are applicable, right? Which is what I have summarized in the slide, right? For example, transportations. If I look now within industry cloud solution transportation aspects. Then I can see transportation aspects, right? And then this is the API, which basically is used to feed, to ingest service codes, transportation lanes, and transportation zones into... So this is the API, right? You could see the reference and there are three web services or three APIs, right? There is one for transportation phones, there is one for transportation service codes, and one for lanes. And then you can see like any other API, right? So you could see also the details, right? What is the details of the API? What is the schema of the API? There are some information. So you can yourself understand the API, how to use them, what are the entities required, what is the body you need to use, and so on and so forth. And this is only one, transportations. If you want to use, for example, ATP, you want to load external inventory because if you have an S4HANA system with your own distribution tenders, then you are Usually, you replicate that from the S4 HANA party. You need to replicate or you need to feed inventory positions from external warehouses. Then you use this ATP snapshot API. And again, so you access and then you can see the reference, the body, everything. This is the API that can be used and so on and so forth. That's what I meant. So data ingestion for industry cloud solutions. And then, finally, the DI app. So how do we control the data which is ingested or goes into every of the industry cloud solutions? So there is a data ingested. Yeah, OK, I need to indicate. Oh, sorry, no. I'm accessing now a testing BTP account. Now, in this DI application, I define, first, what are your systems that are feeding data into OMSA? Well, sorry, not into OMSA because this is, as I say, is a common layer for all of the industry cloud solutions, not only OMSA, also it will be used by OMF and the other, and all the industry cloud solutions. So those are the systems that you could use. And for example, for S4HANA, I'm using this system ID 111A2 to feed data using data replication framework. And then you have data entities. You define that when you set up, when you're doing an implementation, you need to define, first you need to define what are industry solutions you want. You need to subscribe them, but tomorrow you'll receive details about that. And then you need to also configure your data ingestion. And there is a number of entities, right? And for example, if we look into the ATP snapshot, this is consumed, you can see that this ATP Snapchat will be feed from this source system, right? And then in the ATP Snapchat, you will see that the only entity, the only industry cloud solution, which in this testing system is consuming ATP Snapchat is OMSC. But if we look into plants, for example, science, data entity, right? Oh, for example, transportation lanes again, right? So the data entity, again, is only OMSA who is consuming these transportation lanes. But if you go back to plant or product, give you an example, plant object is consumed by OMSA but also by other industry cloud solutions. So this is the common layer. You have source systems, You have data entities and you need to enable the data entities so that OMSA can connect to data ingestion and then replicate data from data ingestion into OMSA.