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

You've completed

cleanFiles/bookmap_SAP_Order_Management_-_Technical_Baseline_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2024-12-17T10:36:30.000Z

Explaining Filter & Jobs

<div id="content"><div class="parentsection"><div class="section"><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_phr5pszq"></div></div></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Diagram of a replication model showing Plant and Product sections with various filters for ProductPlant, CustomerOrder, and others." alt="Diagram of a replication model showing Plant and Product sections with various filters for ProductPlant, CustomerOrder, and others." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_001.png" tabindex="0"><div class="imageCaption"></div><p tabindex="0">Filter that are set for an object are evaluated across entities</p></div></div><div class="parentsection"><div class="section"><div tabindex="0"><h3>Three Different Filter Types</h3></div><ul style="list-style-type:disc"><li tabindex="0">Simple explicit filter</li><li tabindex="0"><p tabindex="0">Filter on main table with selected fields</p></li><li tabindex="0">Complex explicit filter</li><li tabindex="0"><p tabindex="0">Filter implemented with filter class</p></li><li tabindex="0">Custom filter (as simple or complex filter)</li><li tabindex="0"><p tabindex="0">Own implementation of a filter class / filter structure</p></li></ul></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Screenshot of SAP's Define Filter Objects overview, showcasing filter definitions and assigned filters for product management." alt="Screenshot of SAP's Define Filter Objects overview, showcasing filter definitions and assigned filters for product management." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_003.png" tabindex="0"><div class="imageCaption"></div></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Screenshot of SAP display structure showing filter criteria for product with attributes and components listed." alt="Screenshot of SAP display structure showing filter criteria for product with attributes and components listed." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_004.png" tabindex="0"><div class="imageCaption"></div><p tabindex="0">The selection fields are configured/chosen through the structure</p></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="SAP interface displaying active queries with filter criteria and replication models. Various business objects are listed with filter statuses." alt="SAP interface displaying active queries with filter criteria and replication models. Various business objects are listed with filter statuses." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_005.png" tabindex="0"><div class="imageCaption"></div><p tabindex="0">Filter values are maintained via transaction <code>DRFF</code> for background or initial loads</p></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Screenshot of SAP interface displaying filter criteria for data ingestion; includes fields for including and excluding business objects by material type." alt="Screenshot of SAP interface displaying filter criteria for data ingestion; includes fields for including and excluding business objects by material type." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_006.png" tabindex="0"><div class="imageCaption"></div><p tabindex="0">Filter values are maintained via transaction <code>DRFF</code> for background or initial loads</p></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Interface screenshot showing the Source of Supply filter object with attributes like supplier, product, and validity dates." alt="Interface screenshot showing the Source of Supply filter object with attributes like supplier, product, and validity dates." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_007.png" tabindex="0"><div class="imageCaption"></div><p tabindex="0">In complex filters the structure might deviate from the main table</p></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Screenshot of SAP Class Builder displaying filter settings and method implementation for data replication framework. Code and parameters are visible." alt="Screenshot of SAP Class Builder displaying filter settings and method implementation for data replication framework. Code and parameters are visible." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_008.png" tabindex="0"><div class="imageCaption"></div><p tabindex="0">And the select is developed and not automatically derived from table and fields</p></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Table displaying methods in the class ZCL_CIC_PRODUCT_FILTER_W_SITE, including method names, levels, visibility, and descriptions." alt="Table displaying methods in the class ZCL_CIC_PRODUCT_FILTER_W_SITE, including method names, levels, visibility, and descriptions." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_009.png" tabindex="0"><div class="imageCaption"></div><p tabindex="0">Custom filters work exactly like standard filters</p><ul style="list-style-type:disc"><li tabindex="0">Create a structure if required</li><li tabindex="0">Check whether criteria are relevant for manual selection or generic</li><li tabindex="0">Implement filter class for complex filters</li></ul></div></div><div class="parentsection"><div class="section"><p tabindex="0">Simple filter - 1,000,000 records</p><p tabindex="0">Complex filter - 200,000 records</p><p tabindex="0">Custom filter - 50,000 records</p><ul style="list-style-type:disc"><li tabindex="0">Handed over as unfiltered -&gt; filtered tables</li><li tabindex="0">Records can be reduced not extended</li><li tabindex="0">Filters might apply on depending objects (for prod and plant)</li></ul></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Screenshot of SAP data replication settings, including options for replication model, outbound implementation, and report control." alt="Screenshot of SAP data replication settings, including options for replication model, outbound implementation, and report control." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_011.png" tabindex="0"><div class="imageCaption"></div><p tabindex="0">TA <code>DRFOUT</code></p></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Interface for SAP Manual Replication Filter Criteria with fields for product and plant material categories and types." alt="Interface for SAP Manual Replication Filter Criteria with fields for product and plant material categories and types." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_012.png" tabindex="0"><div class="imageCaption"></div><p tabindex="0">TA <code>DRFOUT</code></p></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="SAP data replication interface showing replication model settings and time interval options for data creation limits." alt="SAP data replication interface showing replication model settings and time interval options for data creation limits." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U3_L3_T1_013.png" tabindex="0"><div class="imageCaption"></div></div></div></div>

Filter & Jobs

Customizing technical baseline of SAP OMF and SAP OMSA

<div>The video explains the concept of filter handling with cloud integration, discussing cross-object filters and different filter types such as simple explicit, complex explicit, and custom filters.<br><br># This description was auto-generated #</div>

Understanding the Concept of Standard Filter, Complex Filter and Custom Filter Across Data Entities

Then we already come to the topic of filter. Like I said, the filter handling with cloud integration is a little bit different than the filter handling that we had with car. The big change is that now these filters are cross-object, meaning you have the possibility if you send data out, I don't know who of you have worked with DRF already, but pretty much the data replication framework, if you send data out, you select data, you can restrict data, and then you send this data out and then to industry cloud, for example. And if you set a filter, there are possibilities. You can either do it in a kind of saved way. We'll see that in a minute, or you can do it when manually replicating data. So if you set a filter for a product, let's say we don't need service articles in industry cloud. We only need hava articles or the certain article type. Then we can set a filter for product. This filter will be automatically applied to all entities and object that use the product inside of their entity. Right? So if we have, for example, a purchase order and we filter products to certain product types, we will only replicate purchase orders or customer orders that contain at least one article out of the filtered articles. Right? And that's something that for customers that have used with car is a little bit strange that they don't have to set the same filter in every object sending out, but that the filter that you set, and there's a transaction with it, we would see that, that you said that they automatically apply also to other objects, right, to make sure that we send out a consistent set of data. Also for plant, if we say for the moment we do replenishment for disease, we only need disease and don't need stores for now. If we restrict the object plant with these filters, Also, product plan data will only be sent out for those plans chosen, right? So this is important to know and it has to be explained to customers that have worked with car before. And also this is something that you have to know and also if you're talking about extensibility again if we want to influence that I will explain now how that works and what different filter types are. Right so we have basically three different filter types even if technically there are only two. So one is simple explicit filter what is called means that for every we will see this in a minute, that for every object, for example, if we send products out, who's familiar with S4 knows that there's a table called Mara where product data is on. So that's the main table for the object product, for example. And if we want to simply filter the data that we send out, we could say that we search for certain article types or for something that is available as a restriction or a selection field or a table field in MARA we can use that as a simple filter and just say okay only send out where the article type is something like this. In complex explicit filter the difference is that somebody an SAP or yourself implemented a filter class so this this is not only like, okay, Mara field filter. So you don't have to program anything that can be automatically generated or used by the code or by S4. It means that in some class, somebody defined, okay, we have that and that and that restriction and we use this and this view, whatever, to look for the data and to assemble the data. And that's the complex filter means that you, in a programmed kind of way, that you select on data and that you use restrictions, maybe even across tables, right? You have like a join or anything where you say, OK, I look into an info record and stuff like that. So this is the example of complex explicit filters. And the third dimension is that you as a customer or somebody working for a customer can create a custom filter. So you can do the same stuff that SAP does in standard, also in your system, that you can create a filter. If it's a structure for a simple filter or if it's a class for a complex filter, we will see. I will show one example. Right. So a simple filter means the main table, the simple filter is, like I said, so we have a structure. And the structure in the object is defined. And there's also the same dRF EMG again. You can see here for a filter object, to see what I mentioned earlier, that this object here is CIC prod, which is not the same product that we use to send out articles to car. So just as a reminder. So here we have our CRC prod, and we see here the main table is Mara. And if we go to this assign filters, we see here that we have here in this system, in your system, you will only find the first two entries. The third one is one that we created here for testing out what we did for a customer, is here that we see we have a simple filter with this product generic filter. So here, for example, for this project product generic filter, we see here that in this structure we have two fields available, right? The material category. So it's a simple article or a display or a sales set, if you are familiar with these article types in in S4, and the material type, which means this is a service article or this is a normal selling good, right. So these are basic filters that are set for this product. And in DRFF, this is a transaction. If you open it, this will similar as the oauth profile open Web GUI. And here you can use for this filter values, you can set some some filter, right. So here in DRFF, if we set this filter criteria, then we say here, okay, where the material type is HAVA or set HAW, right. So we want to restrict to this article types. And this is important if you send data out as initialization or as full-blown or considering change pointers. And yeah, and the, I shouldn't read, sorry. Right, so here we set these values. And if you send initialization or change pointer, whatever this filter values that you set this transactions are always applied. Only if you send manual filter we will see that in a minute then you can put something else but here this stored criteria is available if you send data like a full send over or something these filter here apply. Right so this is the simple filter we see that we have two fields that are defined in the structure and we can set values for these two fields in this transaction here. You can then choose here material type. If you would be here in edit mode, you could also see that it's not only material type. You would only see the article type that you can restrict here. Right. And you can put multiple values like here, of course. So, if we move to complex filters, you see here, I chose the example here of source of supply. This is not relevant for OMSA, but for PRP, for example, and for ODS. So we have here the source of supply and you see here already that the structure does not only contain fields that is available in this table but some additional fields that you can set as a value that has some effect when selecting the data. You also see in the configuration if we go back here that you see that for simple filters we only have the structure right, to filter data. And for complex filters, we have a structure, two structures, and a filter class. So the filter class here implements what data and how the data is selected. We have here two structures, might be the same, but different, meaning that if you use manual sending over of objects to industry cloud, then these fields apply. If you send over initialization or in change mode, then these filter apply. Like I said, they could be the same, but for example, if you select articles and you do it manually, you might want to select an article number, which is pretty unlikely that you restrict an article number if you want to to send over articles with change pointers, right? That's why here in the manual filter parameters, you would find an article number and here you would find something more generic like article type and so forth. But here in this filter class here, a product filter, this is then what is implemented for a selection. And in the example, again, of source of supply, you see here that here there is a method called apply filter. And in this applied filter, there is then coded. I didn't put all the codes here. Of course, you can look it up in every S4 system. You see here that we filter on plant. This is what we showed earlier. We take over what is filtered for the plant, because source or supply also uses plant. So we don't do a different kind of filtering. We make sure that the filters are in sync. Right. So here, in this here, this is coded. This is select. This is some joins. So we can write how we select the data and how we assemble the data that we want to send over. For custom filter, this works now exactly in the same way. We create a structure if required or if available in standard. So we might choose two different fields from Mara. We created a set field of Mara, or we use the new possibilities to add fields. We want to add this field to a structure. Then we could create just a structure, and then we are fine. We already have a custom simple filter. If we say we need more specific stuff, what I said, we have to check if it's relevant for manual selection or generic. So in this structure, we saw that we have two structure options. If we need two different structures to say, that set field is not relevant if you run it manually, only if mass processing or the other way around. If we want to implement filter class for complex filters, we always have to implement this interface. So we always have this apply filter in our class. Of course, we can create additional selects or additional under methods or methods that we need to make the code more readable and more modular. For example, here, the customer said, for now, I only want to have data for one DC. So when I replicate products, I cannot use filter on product to know which 50,000 articles I need out of my 2 million, right? So what we did here is that we created like an own filter where we said, okay, we want to restrict products for just the products that exist in a certain site. And then we implemented here this class to say, okay, we add a selection criteria plant, which is of course not part of MARA. And we implemented an own filter class to be able to risk to already when we risk to select products that we select products that are only available or listed in a certain site. And once we have implemented this filter and have set this for product also in generic filter, this filter was applied to all objects that use the product. So out of 2 million, we just send 50,000 articles and only for this 50,000 articles we have sent ATP, snapshots, source of supply, whatever. So that's then automatic. We don't have to do that again and again for every entity. If we filter the product, this product, and that's the new filter concept, is used automatically in all the objects that use the filter, or the object product for example. Right. So this is how this works. Just PowerPoint doesn't work. No, it works. Yeah. One thing that is important for this filter logic, like we've seen here in the customizing, we have like three levels, right? We have the simple filter, we have a standard complex filter, and we have our custom complex filter. We could have removed the standard filter, but we left it in. What is important is that with a filter and the filter logic, you can only restrict values, right, you cannot go bigger again. So if the first the initial simple filter returns 1 million records, our next filter level can only reduce the number. So there's a check in the code and after a filter, it's always like you have an unfiltered list and you have a filtered list and it checks for integrity reasons that the filtered table does not contain a value which was not available and unfiltered. I think you even get an error if you try to do so. So we can restrict, we can reduce the number of records, we cannot grow the number. one. That is just important to know. Yeah. And of course, that you have to keep in mind if we apply a filter for product that this automatically applied for product and plan. It's I think a feature, but you have to bear that in mind. If you design your filters and you only would like to filter on whatever, yeah, info records or something that you don't do it on product already if there you want to use products to be sent with other artifacts, more or more entities. Right. OK. So if we manually send out data with transaction DRF out, we enter here our replication model. We choose our object. We can also choose multiple. If we say that here manual, then we see our manual filters. Here in our system, you won't find that in yours. We allow the possibility to restrict by plant, which is normally not available just for product. We have the material category, material type, and this material number, as we saw, is only available for the manual replication. If we want to send data by job, for example, with initialization mode, then we can send this data out. And then we don't restrict just with the filters that has been set with this drff transaction. So there we said, OK, only certain article types, and if we send initialization. One thing that we have to consider is that for some objects, it might make more sense to send initialization rather than changes, right? For some, it might be the other way around. So if we have very few records with billion of changes, it might make more sense to always send the full data initialization mode for articles where we have millions of records and very few changes, like maybe articles, Um, I guess they change, uh, not as often as, as they are initially sent. Um, then it makes more sense. Of course, do you go by changes? Right. Um, yeah, one thing, because I saw a question in that regard, maybe we just continue and then we take the questions. Um, it's a very short lesson. there is this application integration framework. And the DRF framework, especially for industry cloud is also connected to this framework. So yes, there was one question in that regard, if I saw correctly. So the link or the documentation for AIF is pretty simple. And we can maybe open that here. no use to put these few lines. It's very simple, right? You just have to go to S4, use a transaction, enter this deployment scenario, execute it, and that's it. And then you enable this industry cloud DRF objects for the application integration framework. What you get then is that here, for example, you see the log here of an object sending out here, I just sent one article. But you see here, for example, the count of elements that have survived each filter. So we see here that we had already in the first filter, one entry, one entry, one entry. In our example with the products filtered by plant, you would maybe see see that we have 2 million here, that we have 50,000 here, and again, or 260,000 if we restrict to article type or whatever, and that we see 50,000 here if we restrict with a third filter. You would see that here. But here I send to two different systems. That's why I see here that I receive two codes, one for this direct and one for this iFlow way and one for the direct connection, right? And if I go to the application integration framework to this error monitoring here, I see more data here, I see okay, that I successfully if I restrict so that I successfully submitted value, and you would be even able to see the data that has been sent out.