Available to promise using SAP GATP. What HCL did for the customer. To address the need for an application that could perform availability check across the. SAPVITS is best SAP APO Online Training Portal available in Hyderabad. Our SAP APO Course are interactive live video and live person. In a system (for example, SAP R/3 or SAP CRM) that is connected to SAP APO, you create sales orders for which an ATP check should be carried out in SAP.
|Language:||English, Spanish, Indonesian|
|Genre:||Business & Career|
|ePub File Size:||16.54 MB|
|PDF File Size:||9.78 MB|
|Distribution:||Free* [*Regsitration Required]|
The SAP APO Core Interface (APO CIF) is a standardized interface solution that enables you to integrate SAP APO with the SAP R/3. Define and activate one of the following integration models for the SAP APO Core Interface (SAP APO CIF): ¡ An integration model to schedule VMI sales orders. 3 How SAP APO Global ATP Technology Works .. 69 12 Integrating the SAP Customer Relationship GATP - rules-based multilevel,
The second time I populated the quantity field with a value of , and now the ATP has been performed for Show related SlideShares at end. Click here to sign up. One item may be ordered in units of 50, but if units are desired, and the current inventory is less than 35, then must be ordered to meet this demand. The integration model has a name and is related to a target system. This not only holds true for safety stock but also for many other attributes that only come into play at the product location master. Of these alternatives, Multilevel ATP Check is the most complicated, and best suited for assemble to order operations.
But in reality, supply chains are not perfectly linear prob- lems. For example, the lot size is a discrete value that limits the flex- ibility of the order quantity. One item may be ordered in units of 50, but if units are desired, and the current inventory is less than 35, then must be ordered to meet this demand. SAP SCM has a num- ber of techniques, such as lot size, that alter the problem being solved from perfectly linear to discrete, or what is known as a step function.
This is very important for making the resulting recommendation re- alistic Figure 1. This was because the plan- ning was primarily being performed by heuristics that had been custom coded with scripts, and the solution was not using the optimizer at all.
Whether the client knew the optimizer was not being used is unknown. This is more common than reading press releases and industry periodicals in the area would make you think. Implementing and maintaining optimization methods requires much effort and long-term investment. Secondly, optimization requires a great deal of discipline and knowledge on the part of the implement- ing company.
Many companies want the benefit of advanced plan- ning but are not culturally, financially, or skills-wise prepared to make the sacrifices required to get the outcomes they desire. More often than not, companies want simple solutions that deliver value quickly. And this is partly because the software has historically been designed to be more com- plex than is necessary Figure 1.
As with other planning software, the best successes typically come from companies that are already good at planning. Part of this is content knowledge of planning, but another component is open mindedness to new approaches. Focused on Transaction processing systems such as SAP improvement ERP are a necessity, but a business can still run without a planning system.
Some applications request the estimation of a cost of a lost sale, so those successful with SAP SCM are effective at asking these questions and getting answers. However, more generally, SAP SCM is most beneficial to companies that are dedicated to improving their planning processes and that already have good planning processes to begin with.
Being effective at planning helps the company know how to design the system and also allows the company to better le- verage what it ends up implementing. Cross Application Components As mentioned earlier, this book is broken into a format of one chap- ter per application. However, there are some important concepts and components that cut across the applications, so even though all of the components will be addressed in the same form in individual chap- ters, they may also be covered in other chapters.
The product master contains the information and attributes that relate to the product across all locations. Data elements such as the product number, the material group, and the gross weight and volume are all attributes of the product master. The product mas- ter is set up once per product.
The location master deals with the attributes of the location. The product location master is essentially the product master with added fields and added tabs to hold these fields that modify the product per location.
This not only holds true for safety stock but also for many other attributes that only come into play at the product location master. Planning Areas and Planning Object Structures Planning areas are Planning areas and planning object structures are important cross ap- containers for plication items.
They have a central administration that al- lows the areas and structures to be copied, maintained, and deleted. A planning area is a container for key figures. Planning areas feed an interface object called a planning book, which is a spreadsheet view with a number of aggregation and macro capabilities. At the most basic level, key figures are the numerical values in the spreadsheet.
Planning Object Structure Just as a planning area is a container for key figures, a planning object structure POS is a container for characteristics. The combination of characteristics is called characteristic value combinations CVCs. The POS stores every unique combination of CVCs, which is then used to help control disaggregation when data is manipulated at summary levels. In the previous analogy, we stated that key figures are the nu- merical values in the planning book spreadsheet.
Characteristics are like the textural column and row headings, with the time characteris- tic on the horizontal axis, and the product characteristics on the verti- cal axis. A Planning versions model with the same supply network can have slight alterations in are variations of the planning models terms of control fields on, say, the product location master, making the version create different planning results than a different version of the same model that has the original product location master set- tings.
Multiple versions can be kept over time and run to see how the results change. Because only the active version planning results are communicated back to SAP ERP, multiple versions can be run in per- petuity along with a live active version, without ever impacting the active version.
These time series are displayed with the transaction category. Notice that I have to declare the areas listed above. If not a future date can be entered and the availability check will be run for that date. These two are important fields to call out.
Check Mode: This is explained at this link.
Business Event: The operations of a business. The Business Event is made up of the following characteristics: However, because the real logic is maintained within the Check Mode, while the Business Event is necessary to populate, it is essentially an information field.
After the green checkbox button is selected, we then are taken to the ATP screen, which in this case shows a very large quantity of stock which can be committed against any potential sales order. Notice below: The second time I populated the quantity field with a value of , and now the ATP has been performed for This is because I also changed the date of the ATP check. By double clicking this line item, one can be brought back into the setup of the ATP check. Next, we will view what is referred to as the check instructions, by selecting the button at the top of the screen.
Next, this screenshot comes up. These are all the options that appear for the Check Instructions. Notice that the Check Mode and the Business Event are right at the top of the screen. Next is when the check is to be performed, that is the Product Check, the Product Allocation that is against an allocation, or during Planning.
They are described as follows:. Below this is the Rules Based Avail Check section. I found this definition from a link I provided in the references:. In branched supply chain networks, rules-based ATP allows companies to take full advantage of multiple shipping assets to ship goods from alternative sites to customers.
In addition, it permits certain products to be substituted as required to successfully satisfy customer demands.
This is a functionality available in GATP. This is where the complexity of GATP really ratchets up, because there are so many options. Rules based AC has a number of configuration settings which include:.
There are so many areas to focus on, however, the Third Party Order Processing is of note. This allows processing to be performed against Contracts and Scheduling Agreements. There are many more…. The Check Mode is apparent when selecting to perform a GATP availability check as can be seen in the following screenshot. The Check Mode comes from the Product Master, and therefore definable per product, and is the scope of the check that is performed combined with the consumption of the forecast.
The Check Modes are made up of four characteristics, although in most cases it is really three characteristics as rounding profiles are rarely used. The final characteristic is really more of the name or description of the Check Mode — that is what the Check Mode is used for. For example, SAP gave up documenting fields and therefore many of the fields within one of the most important areas of GATP, called the Check Instructions, are simply copied over and over.
As far as the published material shortage, this surprising because GATP is one of the original SCM modules, so there has been plenty of time to document it. While not implemented as broadly as SNP or PPDS, we can not think of a very good reason why so little is written on the module as it is a constant module of interest among clients. However, it describes many areas of functionality in GATP that I know very well are never implemented — for instance it describes how GATP supports transportation and shipment scheduling to determine material availability — that simply does not happen, and the SAP GATP will most often go off of lead times.
Furthermore, the number of options are so numerous in GATP. However the actual implementation of the options is much different, and this leads to the next point. There are some supply chain experts who dispute the implementability of SAP GATP because some of the data, such as the shipping lead time accuracy.
The complexity of looking out across many locations and other dependent variables are not which relate to future inventory are typically of insufficient quality to make GATP a worthwhile endeavor.
One complicating factor with GATP is its product-location planning, as well as production scheduling along with an order commitment and inventory allocation system all in one.