quinta-feira, 18 de maio de 2023

SAP Transportation Management in SAP S/4HANA 2022 – Highlights

 It has been a while since SAP S/4HANA 2022 FP0 has been published.

With that release SAP TM delivered a lot of new and great features and innovations,

In release SAP S/4HANA 2022 we have significantly invested into further scenarios regarding integration, planning features and enhancements in charge calculation as well as interoperability and many many more topics in all other areas.

I wanted to mention the most important highlights in this blog to give you a glimpse on the newest and coolest features.

 

Let’s have a look into Advanced Shipping & Receiving first.

As you might already be well aware of SAP has delivered a new kind of integration between TM and EWM with SAP S/4HANA 2020 FPS01 release. The processes are constantly enhanced to support additional scenarios.

With SAP S/4HANA 2022 release we extended the scenarios and now also support

Customer Return Handling in the Advanced Shipping and Receiving (ASR) process

Process%20Overview%20for%20Customer%20Returns%20with%20ASR

Process Overview for Customer Returns with ASR

Based on a returns order in sales you can start the inbound process of a customer return now in TM. The whole process can be handled within ASR.

After planning of the freight unit in a freight order you can handle the physical inbound process the same way as you handle other inbound processes e.g. coming from a purchase order with the advanced shipping and receiving process.

There is much more about integration.
A feature that I really like is the new Incoterm handling.

We have harmonized the handling of Incoterms and Incoterm locations between sales or purchasing documents and TM documents. TM Locations can now consistently be used in master data (like business partners, info records and contracts) and  all succeeding TM processes as all data is using unique master data in an end to end fashion. The huge benefit of doing so is that typos that frequently happened in the freetext Incoterm location fields in the past in MM and SD documents are prevented and followup issues in successor documents and processes in TM are not possible anymore.

Details about this feature are already available here: detailed blog.

 

In the area of Freight Order Management we constantly provide new innovation. One of these great innovations is the

Intelligent processing of faulty data in freight orders:

This is a pretty cool feature and helps a business user tremendously when processing freight orders that he has received by faulty inbound messages in the master data.

With this new feature we do not reject the faulty documents. Instead the business user gets suggestions on how to resolve faulty data as he can access and evaluate the issue based on error history and previous solutions.

 

Planning of freight documents is one of the most important areas withing SAP TM. The list of already existing functionality is endless and breathtaking.

However the stream of new cool features is continuing and also with this release we innovate further. Just too many to mention all of them in this blog. Therefore I want to restrict the list here to the greatest innovations.

Among those is the Creation of Capacity Documents Based on Groups.

So far when creating execution documents, you could manually sort in the Transportation Cockpit or combine manually the requirements that you wanted to plan together or add demands manually based on certain criteria e.g. by filtering when doing manual planning. Now, you can group requirement documents intelligently by grouping according to specific attributes and use this feature to create capacity documents.

The attributes are represented by grouping rules and a set of grouping rules is bundled in a requirement grouping profile

The requirement grouping profile allows to specify attributes by which requirement documents get grouped into capacity documents, e.g.: document type, source location of stage, destination location of stage, earliest start date/latest end date for loading/unloading, material freight group, preferred equipment type, shipping condition, Transportation mode, Carrier or incompatibility settings.

For each of these groups of requirement document stages, the system creates a capacity document.

This kind of grouping really provides a high flexibility.

Creation%20of%20Capacity%20Documents%20Based%20on%20Groups

Creation of Capacity Documents Based on Groups

You can trigger the creation of Capacity Documents based on Groups with a new action in the Transportation Cockpit app. This will improve manual planning efficiency significantly.

 

In the area of planning New layouts for basic shipping in the Transportation Cockpit are delivered. 5 new page layouts that serve as examples are provided to support basic shipping.

This means, that each of the layouts is provided per transportation mode (road, rail, air, ocean) and additionally a layout that include all of those transportation modes.

Additionally SAP delivers new hierarchy types for the basic variants as well.

Transportation%20Cockpit%20with%20Page%20Layout%20for%20All%20Modes%20for%20Basic%20TM

Transportation Cockpit with Page Layout for All Modes for Basic TM

 

There are so many improvements and new features in the are of Package Building. All worth to be listed here, but I want to limit it and specifically mention only some of them. One of it is the support of Mixed Layers within the Package Building Optimizer. With this new enhancement you can now use the Package Building Optimizer to consume and consider layer definitions and to provide detailed results like position information for a layer-based mixed package.

Mixed%20layers%20are%20visualized%20as%20a%20single%20block

Mixed layer visualization

In above picture you can see in the list view how the PBO provides an optimized result using layer definitions providing exact positions on a the layers

 

Furthermore Package Building now also supports Packing Instructions.

This is great news. As you know the Unified Package Building (UPB) already supports TM and EWM. With this new feature now also Logistics General (LO) supports UPB with the Packaging Instructions that are used in LO.

You can create packages using unified package building, a generic packaging layer. Up unit now, automatic packing in Logistics General (LO), Transportation Management (TM), and Extended Warehouse Management (EWM) used differing packing engines based on different packing rules: In LO, based on packing instruction master data, in TM package building based on product master data and package type assignment settings, in EWM based on packaging specification master data. Unified package building enables you to use your preferred packing engine in all three components, for example, to use package building not only in TM but also in LO and EWM.

 

In the area of Freight Collaboration with carriers we deliver a new carrier app to Manage Execution of Freight Orders.

With this feature, you can furnish your carrier with an app to report the execution of freight orders.

Overview%20of%20freight%20orders%20for%20execution

Overview of freight orders in execution

In the overview the carrier gets a list of all freight orders assigned to him for execution.

The carrier can navigate into his worklist, report events directly in the list or access an individual freight order to see all activities he needs to perform with all the required details. In a particullar freight order he or the actual driver can report actual events, delays, or upload documents (like POD documents) during execution.

Freight%20order%20with%20details%20and%20event%20reporting

Freight order with details and event reporting

All the events, further information and documents are instantly visible to you as the shipper and you can react accordingly to exceptions during the execution process.

 

There is also quite some improvements in the area of Charge Calculation. With Advanced Shipping and Receiving a new object called Consignment Order has been introduced. Now you can use Charge Calculation for Consignment orders and calculate charges also for sub-stops.

Charge%20Calculation%20for%20Sub-Stops%20in%20ASR

Charge Calculation for Sub-Stops in ASR

 

Another notable feature is the usage of Charge Calculation for Planned Distance. The planned distance may have been handed over directly from the carrier or it was calculated directly in TM. To enable this new feature a new calculation base for the planned distance has been provided and it can be used on all levels of charge calculation.

 

As you know TM is constantly investing in interoperability to make sure that TM works well with external systems. Here are just some examples where we have extended our Interfaces & APIs.

  • SOAP API: Freight Charges Processing

With this feature, you can update transportation charges in freight orders or freight bookings using an asynchronous business-to-business (B2B) inbound service. You can update the relevant parameters for a particular charge line, for example calculation bases, rate amount and rate currency. The charges are relevant for single or multiple business partners, for example carriers, based on the freight orders or freight bookings.

  • Freight Agreement and Forwarding Agreement Interfaces to Support Agreements with Multiple Purchasing/Sales Organizations and to Support Agreements with Charge Item Hierarchies

The two available interfaces for freight and forwarding agreement interfaces are extended with new features, so that you can now create freight and forwarding agreements with multiple purchasing or sales organizations. The interfaces now support additionally charge items that have a parent-child relationship. You can use the interface as well to send freight or forwarding agreements with multiple purchasing or sales organizations or a hierarchical parent-child relationship to external systems.

 

As I mentioned above, this blog is only about some of the highlights. If you want to get more and additional information about the latest and greatest on the current release, please check the following resources:

Source: https://blogs.sap.com/2023/05/16/sap-transportation-management-in-sap-s-4hana-2022-highlights/

Stock Type Determination of Inbound Delivery in Extended Warehouse Management (EWM)

 Overview:

In this blog, I will attempt to explain how the availability group and ERP storage location are linked, as well as how the stock type is determined in the EWM inbound delivery. And this behavior is same for both S4hana Embedded EWM and Decentralized EWM system.

How does the inbound delivery get the stock type in EWM?

When a purchase order is created, the ERP stock type is displayed in the delivery tab.

Ex: Unrestricted, Quality, and Blocked stock

In the following PO, the stock type of item# 10 is unrestricted, and item# 20 in quality inspection.

When an inbound delivery is created in ERP (VL31N), it is replicated in EWM with the following stock types,

Item 10: Unrestricted in ERP & Stock type F1 in EWM

Item 20: Quality inspection in ERP & Stock type Q3 in EWM

According to the screenshots, it is clear now that system is assigning the stock type as follows,

ItemERP stock typeEWM stock type
10UnrestrictedF1-Unrestricted use in putaway
20Quality inspectionQ3-Stock in QI in putaway

The question here is, how does the system automatically assign these stock types? Check the following configuration,

Case:1 PO item 10 with Unrestricted in ERP,

When the inbound delivery gets transferred to the EWM system, it checks the table below and finds the non-location dependent stock type (NST) that is the ERP stock type in the EWM system.

We can see in the below table that for the warehouse KCWH, NST stock types of FF is there, and it is assigned with availability groups 001,002, and 0003.

But the system took only F1 in the inbound delivery as availably group 001 is assigned to the combination of plant and storage location of the purchase order.

Case:2 PO item 10 with quality inspection in ERP,

When the inbound delivery gets transferred to the EWM system, it checks the table below and finds the non-location dependent stock type (NST) that is the ERP stock type in the EWM system.

We can see in the below table that for the warehouse KCWH, NST stock types of QQ is there, and it is assigned with availability groups 001,002, and 0003.

But the system took only Q3 in the inbound delivery as availably group 001 is assigned to the combination of plant and storage location of the purchase order.

Conclusion:

I hope this blog explains how the EWM inbound delivery get the stock type with the required configuration and test cases.

Please share your comments and feedback in the comment section, I am expecting the comments for improving my knowledge, many thanks. Please follow my profile for upcoming blogs.

Regards,

Kannan Chokkanathan


Source:https://blogs.sap.com/2023/05/16/stock-type-determination-of-inbound-delivery-in-extended-warehouse-management-ewm/

terça-feira, 16 de maio de 2023

Product substitution with advanced Available-to-promise (aATP) with SAP S/4HANA

 Advanced Available-to-promise (aATP) as introduced by SAP in 2016 is the successor of APO- GATP (Refer my blog https://blogs.sap.com/2017/05/22/future-of-apo-and-its-migration/) . aATP has been built from scratch and it took some releases to match the features of APO-GATP. aATP as of S/4HANA 2022 release provides very rich features and one of the major drivers for many of the migrations from ECC to S/4HANA.

Alternative based confirmation (ABC) is the name for location and product substitutions in aATP. Refer my blogs https://blogs.sap.com/2018/10/28/alternative-based-confirmation-abc-of-advanced-atp-in-s4hana-1809-release-for-location-substitution-of-apo-gatp/ , https://blogs.sap.com/2020/02/09/tie-breaker-logic-in-alternative-based-confirmation-abc-of-advanced-atp-aatp-in-s-4hana-1909-release/ for location substitution.

My present blog is on product substitutions and describes some real-life scenarios for some of the customers implementing aATP.Main reasons for substitution of the product are that the product as requested or ordered by the customer is

·       Not available with right quantity at right place (store / warehouse/ plant) at right time

·       Being phased out and replaced by another product (upgraded with new features, better quality or more sustainable etc)

aATP supports real-life complex scenarios and some of scenarios are described below.

Substitution by an upgraded product

The ordered product is not available and hence being substituted by an upgraded product (say iPhone 14 128 GB is being replaced by iPhone 14 256 GB). Below image shows that FG990 is being substituted by FG991 as displayed in fiori app ‘Review availability check result’ RACR.  

No alt text provided for this image

A sub-item is created in the sales order for the substituted product as shown in below image. Originally ordered product ( at a higher level) is also maintained to keep the track for the actual product ordered by the customer. 

No alt text provided for this image

Confirmation first with existing stock and then substitute

One of garden equipment manufacturers want that the existing stock should first be confirmed for the ordered product and then substitute by another product for the remaining quantity. The customer has ordered for 15 pcs of FG990 ,but only 8 pcs are available , then the remaining 7 pcs have been substituted  by product FG991 as shown in below image.

No alt text provided for this image

RACR App also indicates that the availability has been confirmed with multiple products (with 8 ea of FG990 and 7 EA of FG991) as in below image.

No alt text provided for this image

Substitution by multiple products with order unit as Case (CS)

In most case, sales are done at a different unit of measurement than pc (or each ) like case (CS) as shown in below image for 3 products FG995, FG996 and FG997. Each case contains 24 each / pieces of individual products. 

No alt text provided for this image

One of the beverage manufacturing customers wanted to substitute the ordered products by multiple products, but the confirmed quantities were coming in fractions as shown in below image. Obviously this confirmation in fractions was not acceptable to the customer and it was reported as a defect.

No alt text provided for this image

Standard SAP aATP also has solution to confirm the quantities only with full case (or UoM). Delivery unit for the product needs to be set as 1 CS as shown below.

No alt text provided for this image

Sales order then gets confirmed with multiple substituted products with full cases as shown in below image.

No alt text provided for this image

Exclusion of a product from a series of substitution

Normally, the product FG601 can be substituted by series of products FG602, FG603 and FG604 as shown in below product network graph. 

No alt text provided for this image

A sales order with order quantity of 4 ea is confirmed by 1 ea of individual products FG602, FG603, FG604 as only 1 EA is available for individual products FG601, FG602, FG603 and FG604 as shown in below image from RACR app.

No alt text provided for this image

However, it may happen that the product FG603 is not available during 1st to 15th of May’2023 (as one its components are not available) and hence can be excluded as below in Fiori app ‘Manage exclusions’.

No alt text provided for this image

Subsequently the product FG603 is excluded in the sales order confirmation as shown in below image.

No alt text provided for this image

Product substitution is just one of the several useful features in aATP and that is the reason for aATP very demanding module / applications in S/4HANA.

This blog is based on my personal insights, observation, and tests in SAP S/4HANA 2022 release. Will appreciate your views / comment and feedback.


Source: https://www.linkedin.com/pulse/product-substitution-advanced-available-to-promise-aatp-mrinal-k-roy/?utm_source=share&utm_medium=member_ios&utm_campaign=share_via