SAP SD SUPORTE

segunda-feira, 23 de janeiro de 2023

Quality Inspection of Nested HUs with follow up task for Top & Sub HU level

Objective:

To establish a flow how nested HU can be relevant for Quality inspection for Inbound receiving process considering a shipment is arriving in Pre-Packed form at Pallet level and at box level.
Figure out how Usage decision can be conducted at Top HU level and at Sub HU level.
Address the core issues of Warehouse task creation at Top HU level or Sub HU level or Product WT creation with Top & Sub HU.
Address why Top HU is getting deleted in Non POSC scenarios and explore all the possibilities of top HU retention in system.

In below example, a nested HU is depicted which is relevant for quality inspection. The main objective of the blog is to figure out different behaviours of Warehouse task creation with Direct Putaway and with complex putaway including Unload, Quality Inspection & Putaway.

Scenario I: Direct Putaway: Product WT with Sub HU after UD:

Nested HU is received in staging area, posted GR and relevant for quality activity.( Process 2 in flow).Product is packed into Top( Pallet level) and Sub( Box) level HU and posted GR at staging area.

Perform QI UD from Staging area( Only Embedded EWM allows Partial UD, EWM inspection from Staging area). UD is performed at top level HU ending with 469.

Once UD is completed & saved, partial UD set can be seen how it is fetched.

On completion of UD, Product Warehouse task is created with Sub HU

The top HU ending with 469 is deleted once UD is performed. This process leaves business with no option of having flexibility of HU WT at top HU.

In the final Bin, stock is updated at Sub HU level ending with 452.

Case II: Introduce a POSC with QIS step.( Process 1 as depicted in above diagram). HU wt with Top HU

For the below example, POSC has been set up as Unload+ QIS+Putaway. Once UD is performed for Top level HU having QIS step wired into it, it cancelled a previous Task and created Top HU WT.

The Top HU is retained in system as depicted below and allows Pallet level ending with 438 & Box level ending with 445 inventory in warehouse stock.

Case III: Product WT with Top HU( Process 2 shown in diagram)

Change the Internal action as blank in follow up action. This will trigger only posting change when UD is completed. Then the product WTs can be created automatically after the HU is closed on the workcenter.

Fore this process, created a Unloading WT from Door to staging area and confirmed all relevant activity task required.

Before UD, a Product WT is created with Top HU with waiting status( Process number 2 in diagram)

Top HU ending with 476 and Sub HU ending with 483 is shown as below

Perform UD at top level HU.

Product WT is created with Top level HU as below( Process 2 diagram) with open status.

Inventory is updated at pallet level and box level as shown below.

It would be noteworthy to evaluate in business process whether the subHUs are required at all in this process. If complete stock is put into the topHU, and requirement is to only enter one usage decision for the complete stock then the follow up action will create one WT for this topHU. If necessary, the stock could also be repacked after the usage decision has been made.

This completes all the necessary permutation and combination of conducting QI for Nested HUs. Thanks for reading. Your feedback is highly valued.

All tests have been performed in S/4 HANA 2021 Embedded EWM and content is based purely on by research & insight.

Reference:

3154679 – Complete HU (storage control) after completion of the quality inspection

3217735 – Follow-up putaway WT is not created for top HU

https://answers.sap.com/questions/12979561/quality-inspection-usage-decision-for-top-level-hu.html

Source: https://blogs.sap.com/2023/01/21/quality-inspection-of-nested-hus-with-follow-up-task-for-top-sub-hu-level/

Activity Area in Extended Warehouse Management

Hi Everyone,

Introduction:

This is my first SAP blog here I try to give some insights into the activity area, activities, and sort sequence which is used in the warehouse process.

Activity:

Before talking about the activity area, let’s discuss “activity” first.

An activity is a kind of goods movement inside the warehouse.

Below are the examples of activities that generally occur in the warehouse

Perform putaway
Perform picking
Perform physical inventory
Perform replenishment

In EWM, this activity is uniquely assigned to a warehouse process category.

Warehouse process category:

The warehouse process category is used to classify activities. The following are permitted values for the warehouse process category for activities, we cannot edit or create a new warehouse process category.

Putaway
Stock removal
Internal stock transfer
Physical Inventory
Posting change
Cross-line stock putaway

We can define the activities as per the business requirement, again it could be just a name change since only standard warehouse process categories are available.

IMG-SCM Extended warehouse management-Master Data-Activity areas- Activities- Define Activities

Define%20Activity

Define Activity

Activity Area:

Activity area is the logical area that is used to separate our warehouse into logical subdivision units. Warehouse workers operate different kinds of activities in these logical units such as putaway and picking.

Activity area containing one or multiple storage bins from the same storage type or different storage types. We can define the assigned storage bins using the following attributes:

Aisle
Stack
Level
Bin subdivision
Depth
Information about the storage type
Any assigned deconsolidation groups

Activity-dependent storage bin sorting can be maintained in the activity area (like Put away, picking ) this storage bin sorting helps to optimize the warehouse task execution.

Storage bin sorting allows us to customize our own path through the different storage types in order to set up the fastest and most efficient way to process warehouse tasks.

Example:1

If the business wants to have some sort of crisscross route through the different aisles of the storage types

crisscross%20route

crisscross route

Example: 2

If the business wants to have the serpentine route,

serpentine%20route

serpentine route

We can set up the different storage bins sorting for different activities such as,

Put away – Crisscross route
Picking – Serpentine route
Physical inventory – some other paths as per business

Activity%20Area%20based%20Bin%20sorting

Activity Area-based Bin sorting

Structure of activity area:

The activity area can be a single storage type, a combination of multiple storage types, or multiple storage bins from different storage types.

If the business requires, each storage type as an activity area based on the activities (picking, putaway,.) then we have the following report that helps to create.

/SCWM/R_AREA_LGTYP_CREATE – Generate Activity Area from Storage Type

Report%20to%20create%20Activity%20area%20based%20on%20storage%20type

Report to create Activity area based on storage type

And we can create an activity area based on the combination of storage bins, ex: For the picking activity, we can use the serpentine route (which is used for fast-moving materials) that will get when we assign the multiple bins from the different storage types.

IMG-SCM EWM- Master Data- Activity Areas- Define Activity Area

Define%20Activity%20Area

Define Activity Area

Fast%20moving%20activity%20area

Fast-moving activity area

Assign storage bins to the Activity area:

If the business wants the activity area based on the storage bins from the same or different storage type, then assign the storage bins against the activity area.

IMG-SCM EWM-Master data- Activity Areas- Assign Storage Bins to Activity Areas

Create%20Activity%20Area%20with%20bins

Create Activity Area with bins

Define Sort Sequence for Activity Area

We can sort these storage bins into any sequence we want and assign as many activities to them as we require.

Storage bin sorting can be carried out based on the activity (picking, putaway…) and storage type in the activity area.

Below is the configuration to set up the sort sequence method for the activity area.

IMG- Extended Warehouse Management – Master Data – Activity Areas- Define Sort Sequence for Activity Area

Sort%20sequence%20for%20storage%20bins

Sort sequence for storage bins

And the following screen, we can see how the sorting can be executed,

T code: /SCWM/SBST (cannot captured in TR)

Create%20Bin%20sorting

Create Bin sorting

Simulation%20of%20Bin%20sorting

Simulation of Bin sorting

Success%20message

Success message

To check the sorted storage bin in the table, go to /SCWM/LAGPS

Bin%20sorting%20table

Bin sorting table

When activity areas are used and storage bins are sorted, we need to re-execute if the storage bins are,

Added
Deleted
Changed

Conclusion:

I hope this blog explains the activity area concept in EWM clearly with the required configuration and business process.

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/2022/08/19/activity-area-in-extended-warehouse-management/?utm_campaign=meetedgar&utm_medium=social&utm_source=meetedgar.com

Time-Dependent Stock Levels in SAP S/4HANA

SAP S/4HANA 2022 introduced the new Fiori App Maintain Time-Dependent Stock Levels (F5726), which allows the maintenance of Time-Dependent Stock Levels, that are relevant to MRP.

Using this app, planner can define a Time-Dependent Safety-Stock and Time-Dependent Days of Supply, that means, a safety stock or days of supply that is considered by MRP only within a specific time window.

This blog will explain how to set up this functionality and how to use this app to maintain time-dependent stock levels. We will also see an example of how the time-dependent safety stock is considered by MRP during net requirements calculation.

Note: The concept of time-dependent stock levels was introduced in SAP S/4HANA 2021 but the maintenance of the stock levels was only possible with the API API_PROD_TIMEDPDNTSTCK_SRV.

Definition of the MRP Safety Stock Method

The first step if we want to define a time-dependent stock level for a product is to choose the MRP Safety Stock Method, and we can choose a value for this field in the app Manage Product Master (F1602).

We will be able choose one of the following values for this field:

Static Safety Stock: A fixed safety stock that will not change over time.
Time-Dependent Safety Stock (MB): Allows the user to create custom time intervals and define a different value for the safety stock in each interval.
Time-Dependent Days of Supply (MZ): With this setting in the material master, instead of defining a fixed value for the safety stock within a time-interval, we will define how many days of requirements should be covered by the safety stock.

In our example we will choose the option Time-Dependent Safety Stock, as shown in the Figure below, because we want to use a different value for the safety stock in each time-interval.

Maintaining Time-Dependent Stock Levels

After we define the safety stock method in the material master, we need to use the app Maintain Time-Dependent Stock Levels, highlighted in the following figure, to create our intervals and choose the desired quantity that will be used as a safety stock.

When we open this app, it will show a list of materials within the user Area of Responsibility for which an MRP Safety Stock Method has been defined. If we select one of those materials, we will jump into the details screen, where we can see all the intervals defined for a material.

As we can see in the Figure above, we already have intervals a safety stock defined for our material, but we can click the button Add Interval to create a new one.

We will add a new interval from February 1^st to February 28^th, where the safety stock will 15 PCs, as shown in the following Figure.

Existing intervals are automatically adapted to fit the newly created interval. As we can see in the Figure below, we have two intervals in the past, one interval from January first to January 31^st, where the safety stock is 20, another interval from February 1^st to February 28^th with a safety stock of 15 and on interval from March 1^st onwards with a safety stock of 20.

Checking the Safety Stock in the Stock/Requirements List

Now that the intervals were created, we can check the Stock/Requirements List either in the MRP Fiori Apps or directly in transaction MD04.

The Figure above shows the results in Fiori Manage Material Coverage (F0251), and we can see there are three lines representing the Time-Dependent Safety Stock:

The first line is shown in the current date, and it is represented with a negative quantity of 20 PC.
The second line, on February 1^st, shows a positive quantity of 5 PCs, because it shows the difference between the safety stock in the previous period and the safety stock in the new period, and the safety stock decreased from 20 PCs to 15 PCs.
The third line, on March 1^st, shows a negative quantity of 5 PCs, because again it is showing the difference between the safety stock in the previous period and in the new period, but now the safety stock increased from 15 PCs to 20 PCs.

After MRP is executed for this material, we will observe that purchase requisitions are created to cover the shortages caused by the safety stock and that the available quantity is zero at the end of the Stock/Requirements List.

Now that you know how this Fiori App works and you have seen an example of a material using the Time-Dependent Safety Stock Method, you can explore this functionality and also create an example with Time-Dependent Days of Supply.

Additional Information:

SAP Help – Maintain Time-Dependent Stock Levels

openSAP Microlearning – MRP Time-dependent Safety Stock Levels

Source: https://blogs.sap.com/2023/01/04/time-dependent-stock-levels-in-sap-s-4hana/