How to Remove Discrepancies Related to the Sale orders and Deliveries from MD04

 Hello Everyone,

The following process will shed light on how to remove discrepancies related to sale orders and deliveries.

Problem Statement:

The issue is that when a sale order or delivery has been rejected, blocked, or deleted, the quantity of material related to that sale order or delivery is displayed in MD04. Due to these discrepancies in quantity of a material, the planning/procurement department of an organization is not getting the correct demand for the material, and it causes excess procurement or production of that material, and ATP of that material is not triggered correctly.

Solution:

To overcome the above problem, the following solution is as below to remove discrepancies from MD04 transaction related to Sale Orders and Deliveries.

Step-1:   Run the standard program SDRQCR21 in T code-SE38 and place the sale order/delivery number in the field of Document Number as per the below screenshot and check mark the below options and execute the transaction.

This program can be run for Material/Plant/Creation Date/Sale Orders and Deliveries. It can also be run for a single value or multiple values by selecting multiple options on the screen.

Note: When executing this program, do not select the “Planning Entry” option on the screen.

 

Step-2:        Now check in MD04 that the discrepancies related to Sale Order and Delivery have been removed for which the above program ran.

To Conclude:

Once the above steps will be executed successfully, the business will get the correct demand/planning quantity of the material either to procure or produce that material.

Suggestion:

To avoid any risk in the Production system, instead of running this program-SDRQCR21 directly in SE38, business can make Z T-codes to run this program in the production system and give authorization to the respective user for that T-code to run this program.

Please follow Neeraj Jain for more content on issues & topics related to SAP Sales & Distribution, Material Management and Production Planning.

If any questions, please click here

Thanks for your interest! Please share feedback, comments, or suggestions below.

Best Regards,

Neeraj Jain

SAP Lead Consultant in HCL Technologies Limited

Source: https://blogs.sap.com/2022/09/21/how-to-remove-discrepancies-related-to-the-sale-orders-and-deliveries-from-md04/

Update on EWM – Quality Management Integration

 In the past SAP S/4HANA releases, a couple of new functionalities have been released in the area of Quality Management in EWM. To reflect these, we have reworked our Quality Management in EWM slide deck which is now available in version five.

New in SAP S/4HANA 2022

One functionality which is new with SAP S/4HANA 2022 is the inspection lot summary per delivery item which allows to create one inspection lot per delivery item in case of multiple items with the same material / batch combination. The functionality can be activated in the EWM IMG Activity “Define and Activate Warehouse-Independent IOTs”. Before 2022 and in case of multiple items with the same material / batch combination in one inbound delivery, the system automatically summarized the complete quantity into one inspection lot.

IMG Activity – Define and Activate Warehouse-Independent IOTs

Also new with SAP S/4HANA 2022 is the support of the QM process when using synchronous goods receipt from external and manufacturing (available due to system boundaries for embedded EWM only). In case MIGO or PP transactions are used in order to post the goods receipt into an EWM managed storage location, as of SAP S/4HANA 2022 inspection lots are created and also the inspection lot summary, skip lots as well as cancellations are supported. The following transactions are supported:

Manufacturing Process​	Transaction​	Description​
Repetitive (PP-REM)​	MFBF​	Backflushing in Repetitive Mfg.​
Repetitive (PP-REM)​ ​	MFHU​	Goods Receipt of HUs​
Discrete (PP-SFC)​	CO15​	Enter Production Order Confirmation​
Discrete​	CO11N​	Single Screen Entry of Confirmations​
Process (PP-PI)​	CORK​	Process Order Confirmations (Total)​
Process Man. (PP-PI)​	COR6N​	Single Screen Entry of Confirmations​
Process Man. (PP-PI)​	COWBHUWE​	Goods Receipt for Handling Units​
Universal (REM/SFC/PI)​	MIGO​	Goods Movement​

The quality certificates in the goods receipt process are also new with SAP S/4HANA 2022. In order to ensure compliance, it is now possible to capture the existence of external certificates during the goods receipt posting in EWM. The EWM inbound delivery contains the information that a certificated needs to be captures and passes this to SAP ERP QM in order to prevent the usage decision taking before the certificate receipt is recorded (e.g. via app QC51). This functionality is only available for delivery based goods receipt postings.

IMG Activity – Define and Activate Warehouse-Dependent IOTs

Last but not least, as of SAP S/4HANA 2022 the quality inspection can be skipped according to the quality level and goods receipt can be posted in EWM directly to unrestricted use stock. This means that it is now possible to create the putaway warehouse tasks directly to the final storage bin for skipped stock. This functionality is new for decentral EWM on SAP S/4HANA as it has been available in embedded EWM already. For more information see SAP note 2810763.

New QM relevant notes

In the course of reworking our QM slide deck, we have also created two new notes with FAQs / additional information:

• SAP note 3284686 – Stock Transfer with EWM and Quality Management: this note provides some insights and answers frequently asked questions with regards to stock transfers with EWM and QM. It covers the process of stock transfers within one plant and to another plant where the receiving storage location is EWM managed.
• SAP note 2545012 – EWM-QM integration – inspection lots of origin 17: Unsupported processes: this note is a collection of the restrictions in the EWM-QM integration

ADDITIONAL INFORMATION

SAP note 2775887 – How to set up Quality Management (QM) in decentralized EWM​

SAP note 2973050 – How to set up Quality Management (QM) in embedded EWM

AP EWM Community:

https://community.sap.com/topics/extended-warehouse-management

SAP Digital Supply Chain Channel:

https://www.youtube.com/channel/UCELmE2CEAkcwqpBLnuZHufA

EWM LinkedIn Community:

https://www.linkedin.com/groups/1952257/

For a complete list of Q&A from the SAP EWM community, please access this link:

https://answers.sap.com/tags/01200615320800000705

Source: https://blogs.sap.com/2023/02/16/update-on-ewm-quality-management-integration/

Integration of Sales Scheduling Agreements with TM embedded in SAP S/4HANA – Use Cases and Document Flow

 

Dear friends of SAP TM,

In this blog post we already announced the integration of sales scheduling agreements with TM embedded in SAP S/4HANA.

With this blog post here, I want to provide a few more details how freight units are built according to the transport requirements from the delivery schedules of the sales scheduling agreement.

The basic paradigm for building the freight units is to consider the delivery relevance of the schedule lines. This is similar with the integration of other sales documents as sales orders and customer returns.

Settings regarding delivery relevance

The delivery relevance of the schedule lines is determined by the indicator ‘MRP for DS Type’ at header level of the sales scheduling agreements. Here, you determine whether forecast delivery schedules or JIT delivery schedules or both of them are delivery relevant.

For the case of forecast and JIT delivery schedules supposed to be delivery relevant, this means that the JIT horizon is decisive. Means, for forecast schedules, only schedule lines after the JIT horizon are delivery relevant. And for JIT delivery schedules, only schedule lines before the JIT horizon are delivery relevant.

Building Freight Units and Deliveries

As mentioned, the basic paradigm for building freight units is similar to other sales documents as sales orders and customer returns. Means, only delivery relevant schedule lines are considered for building freight units according to the freight unit building rule in the logistics integration profile. And those freight units then have a reference to the respective schedule line.

When the delivery is created for the schedule line, the freight unit is reassigned from the schedule line of the sales scheduling agreement to the delivery. This again is similar to other sales documents.

Examples with different settings for delivery relevance

We now take a closer look at the different settings for the delivery relevance of the delivery schedules.

In the first example, no JIT delivery schedules are used and only forecast delivery schedules are delivery relevant.

See here, the forecast delivery schedules and the document flow:

Here you also see the mentioned reassignment of freight units to the delivery.

Similarly, when only JIT delivery schedules are delivery relevant, for this scheduling agreement, the following document flow exists:

For the last case, where forecast and JIT delivery schedules are used and the JIT horizon determines the delivery relevance, the document flow looks like this:

Integration of existing sales scheduling agreements

As scheduling agreements are covering long term business relations, they need to be integrated with TM seamlessly.

For customers, this means that the customizing of the TM integration needs to be adjusted. To be precise, for the combination of order type, sales org., distribution channel and the division, a logistics integration profile has to be assigned. Then with the next change of the sales scheduling agreement (e.g. the next release from the customer is sent), the integration with TM happens along with the freight unit building for all delivery relevant schedules not being delivered yet.

Fiscal year change

In a sales scheduling agreement, the cumulative quantities are always stored for the current fiscal year. If the system detects a fiscal year change, the cumulative quantities of the sales scheduling agreement are adjusted respectively and the open quantities (including the quantities in transit) are taken over to the next fiscal year. In regards to TM integration, no additional effort is necessary. Freight units are retained and can be used in the next fiscal year.

Transaction SACO

As a scheduling agreement covers a long term business relation, the number of assigned documents (e.g. deliveries, freight units) will grow. Therefore, transaction SACO can be used to copy a sales scheduling agreement to another one, thereby taking over the data necessary for the future handling as open quantities to be delivered. With that, you can somehow start with a ‘new’ sales scheduling agreement.

For TM integration this means that freight units are reassigned from the ‘old’ to the ‘new’ sales scheduling agreement and execution can continue seamlessly.

Correction deliveries

In the context of sales scheduling agreements, correction deliveries are used to adjust the open quantity of a delivery schedule. E.g. delivered goods turn out to be faulty at the recipient and another delivery is expected. Those correction deliveries are a special type of outbound deliveries.

With TM integration, correction deliveries are not integrated as they don’t have any logistical relevance. Nevertheless, their quantity is considered in the open quantity calculation of TM and thus in freight unit building to enable a transport of the complaint goods.

Conclusion

Having explained those details about different use cases, you see that sales scheduling agreements are seamlessly integrated with TM and can be used with its various use cases.

Don’t hesitate to ask or give feedback, I appreciate!

Best regards,

Michael

Source: https://blogs.sap.com/2023/02/24/integration-of-sales-scheduling-agreements-with-tm-embedded-in-sap-s-4hana-use-cases-and-document-flow/

Integration of Sales Scheduling Agreements with TM embedded in SAP S/4HANA

 Dear friends of SAP TM,

Scheduling agreements are commonly used by supplier and customers when there’s a supply relationship over a longer period in time. So, this type of business document is essential for e.g. car manufacturers and their component suppliers (but also other industries) when running the supply chain. SAP TM comes into play when it’s about building the freight units according to the transport requirements of the scheduling agreement.

In a sidecar scenario with SAP TM, purchase and sales scheduling agreements are already integrated. Also, in TM embedded in SAP S/4HANA, purchasing scheduling agreements are already integrated. But here, the integration of sales scheduling agreements was still the missing part, which we now also achieved.

Description of the scenario

In the following, the usage of sales scheduling agreements in a scenario with supplier and customer is shown together with the integration with SAP TM:

(1) Material Requirements Planning creates, changes or deletes schedule lines of a purchasing scheduling agreement.

(2) The delivery schedules for FRC / JIT are sent to the supplier where respective delivery schedules are created, changed or deleted in a corresponding sales scheduling agreement.

(3) Based on the delivery schedule lines, respective freight units are created in TM.

(4) Transportation planning in TM is executed and freight units are planned on existing or newly created capacity documents, as e.g. freight orders.

(5) Outbound deliveries are created based on the TM planning result.

(6) When an outbound delivery is posted goods issue at the supplier, a service message is sent to the customer and a respective inbound delivery is created based on that message.

(7) Goods receipt is posted with the inbound delivery at the customer. This is considered when the next material requirements planning is executed by detecting that the respective requirements are fulfilled.

Document flow of a sales scheduling agreement

This leads then to the following document flow of an exemplary sales scheduling agreement.

The scenario is as follows:

• A customer purchases 100 PCE of a product each month at a supplier.
• Forecast and JIT schedule lines are transport relevant

And the document flow as shown in above figure is explained next:

• Schedule lines for January are deleted from sales scheduling agreement at the supplier as their delivery has been confirmed by the customer -> Respective outbound deliveries with freight units are still assigned
• JIT horizon is at 15.2., schedule lines for JIT releases are transport relevant -> respective freight units are assigned
• Schedules lines for forecast releases for March and April are transport relevant -> respective freight units are assigned

Relevant use cases

With the new integration of sales scheduling agreements with TM embedded in SAP S/4HANA, the following use cases are covered:

Update of Releases from purchasing scheduling agreement

This is the ‘common’ use case as described in the scenario above.​

Planning Delivery Schedule

The planning delivery schedule is an internal delivery schedule of the supplier to plan requirements for future periods not covered by forecast and JIT delivery schedules.

Fiscal Year Change​

Cumulated quantities are captured on sales scheduling agreements only for the current fiscal year whereas open quantities have to be taken over to the next fiscal year. And those transport requirements reflect then in assigned freight units.

Correction Delivery​

Quantity differences in the inbound processing can be captured in correction deliveries, adjusting the open quantity of a sales scheduling agreement.

Transaction SACO​

With transaction SACO, sales scheduling agreements can be copied. Thereby, open quantities are taken over but the document flow of already delivered and confirmed schedule lines is not, thus improving manageability of the sales scheduling agreement.

Furthermore, it’s possible to continue using existing sales scheduling agreements by just setting up their TM relevance in customizing and freight units will then be built according to the transport requirements.

Conclusion

So, now that we have integrated the full scenario of scheduling agreements on supplier and customer side, this is surely another huge step for SAP TM.

This enhancement is available with note 3299820 and is planned to be published with SAP S/4HANA oP2022 FPS02.

Please see also the second part where we talk in detail about the supported use cases and how the document flow with the freight units looks like.

I appreciate your comments and feedback!

Best regards,

Michael

Source: https://blogs.sap.com/2023/02/20/integration-of-sales-scheduling-agreements-with-tm-embedded-in-sap-s-4hana/

Integration of Sales Scheduling Agreements with TM embedded in SAP S/4HANA

 Dear friends of SAP TM,

Scheduling agreements are commonly used by supplier and customers when there’s a supply relationship over a longer period in time. So, this type of business document is essential for e.g. car manufacturers and their component suppliers (but also other industries) when running the supply chain. SAP TM comes into play when it’s about building the freight units according to the transport requirements of the scheduling agreement.

In a sidecar scenario with SAP TM, purchase and sales scheduling agreements are already integrated. Also, in TM embedded in SAP S/4HANA, purchasing scheduling agreements are already integrated. But here, the integration of sales scheduling agreements was still the missing part, which we now also achieved.

Description of the scenario

In the following, the usage of sales scheduling agreements in a scenario with supplier and customer is shown together with the integration with SAP TM:

(1) Material Requirements Planning creates, changes or deletes schedule lines of a purchasing scheduling agreement.

(2) The delivery schedules for FRC / JIT are sent to the supplier where respective delivery schedules are created, changed or deleted in a corresponding sales scheduling agreement.

(3) Based on the delivery schedule lines, respective freight units are created in TM.

(4) Transportation planning in TM is executed and freight units are planned on existing or newly created capacity documents, as e.g. freight orders.

(5) Outbound deliveries are created based on the TM planning result.

(6) When an outbound delivery is posted goods issue at the supplier, a service message is sent to the customer and a respective inbound delivery is created based on that message.

(7) Goods receipt is posted with the inbound delivery at the customer. This is considered when the next material requirements planning is executed by detecting that the respective requirements are fulfilled.

Document flow of a sales scheduling agreement

This leads then to the following document flow of an exemplary sales scheduling agreement.

The scenario is as follows:

• A customer purchases 100 PCE of a product each month at a supplier.
• Forecast and JIT schedule lines are transport relevant

And the document flow as shown in above figure is explained next:

• Schedule lines for January are deleted from sales scheduling agreement at the supplier as their delivery has been confirmed by the customer -> Respective outbound deliveries with freight units are still assigned
• JIT horizon is at 15.2., schedule lines for JIT releases are transport relevant -> respective freight units are assigned
• Schedules lines for forecast releases for March and April are transport relevant -> respective freight units are assigned

Relevant use cases

With the new integration of sales scheduling agreements with TM embedded in SAP S/4HANA, the following use cases are covered:

Update of Releases from purchasing scheduling agreement

This is the ‘common’ use case as described in the scenario above.​

Planning Delivery Schedule

The planning delivery schedule is an internal delivery schedule of the supplier to plan requirements for future periods not covered by forecast and JIT delivery schedules.

Fiscal Year Change​

Cumulated quantities are captured on sales scheduling agreements only for the current fiscal year whereas open quantities have to be taken over to the next fiscal year. And those transport requirements reflect then in assigned freight units.

Correction Delivery​

Quantity differences in the inbound processing can be captured in correction deliveries, adjusting the open quantity of a sales scheduling agreement.

Transaction SACO​

With transaction SACO, sales scheduling agreements can be copied. Thereby, open quantities are taken over but the document flow of already delivered and confirmed schedule lines is not, thus improving manageability of the sales scheduling agreement.

Furthermore, it’s possible to continue using existing sales scheduling agreements by just setting up their TM relevance in customizing and freight units will then be built according to the transport requirements.

Conclusion

So, now that we have integrated the full scenario of scheduling agreements on supplier and customer side, this is surely another huge step for SAP TM.

This enhancement is available with note 3299820 and is planned to be published with SAP S/4HANA oP2022 FPS02.

I appreciate your comments and feedback!

And I can already put in promising that there will be another blog post where I will go into details regarding freight unit building for different scenarios.

Best regards,

Michael

Source: https://blogs.sap.com/2023/02/20/integration-of-sales-scheduling-agreements-with-tm-embedded-in-sap-s-4hana/

Compare Bill of Material apps and Tcodes

 The purpose of this blog post is to document the differences between various BOM apps.

Although it is well documented in SAP, based on various queries in my previous blog post, I am putting the comparison chart here between various BOM Fiori apps and Tcodes. Please take a look at the link for the latest changes using the link.

 

Again, please refer to the standard SAP link for the latest changes.

 Source:https://blogs.sap.com/2023/01/01/compare-bill-of-material-apps-and-tcodes/

Stock transfer of Quality and Blocked stocks with EWM

 In some cases, it is necessary to transfer the stock from one plant to another even though stock is not cleared by quality (quality stock) or even if the stock is rejected by quality (blocked stock).

Best example for this kind of requirement is, if a manufacturing plant has limited warehouse space, business may decide to move the stock to a distribution center and store the inventory in DC with quality or blocked or unrestricted use.

While this is not a new functionality of EWM, Intention of the blog is to explain the process of stock transfer of quality and blocked stocks from one plant to another.

To work with this kind of process, it is must to enable the source stock type for STO.

This will enable the field source stock type in delivery tab of the STO.

Quality stock transfer: During creation of STO, if we decide to transfer the quality stock, we should choose source stock type manually.

When delivery is created, stock type will be carried to delivery document in ERP and same will be distributed to EWM.

ERP Delivery:

EWM Document:

Inventory position before creating the pick list.

Warehouse task for the delivery:

After Goods Issue:

Upon GI, SPED output triggers to generate Inbound delivery in receiving plant.

Stock type is quality inspection as per inspection set up of material master.

Inbound delivery in EWM

After the goods receipt, stock will be posted in quality inspection in receiving plant.

Even though only quality stock to quality stock transfer executed in this test case, it is possible to transfer quality stock to unrestricted or quality stock to blocked stock.

Block stock transfer: Just like quality stock, we can also transfer blocked stock from source plant to destination.

In this example, blocked stock transferred from source plant and received as unrestricted stock in destination plant.

Delivery created in ERP with block stock.

Same distributed to EWM and creates a document with block stock as source stock.

After completing the picking and goods issue, inbound delivery generated in receiving plant with unrestricted use.

ERP Delivery:

EWM Delivery:

Upon goods receipt, stock will be posted in unrestricted use.

This is out of the box configuration and no development involved.

PS: This is my personal observation based on requirements that I worked, and this blog is based on S4 HANA 2022 version sandbox. Functionality available in older versions also.

Thank you for reading the post, please share thoughts and feedback.

Follw https://community.sap.com/topics/extended-warehouse-management for more content.

Follow Narsimha Namburi for more updates.

References

https://help.sap.com

Source: https://blogs.sap.com/2023/02/11/stock-transfer-of-quality-and-blocked-stocks-with-ewm/