Skip to main content

[HU] Physical Inventory process for Handling Units

The physical inventory process plays a vital role in the warehouse as it is part of statuary requirements that all materials should be counted at least once a year.

Physical inventory process can be carried out at Inventory Management level, Warehouse Management Level and Handling Unit level.

This article will talk about the physical inventory process at Handling Unit level .

Below are the HU physical inventory process steps :

Create Physical inventory document - HUINV01
Change or delete physical inventory - HUINV02
Perform Stock Count - HUINV03
Perform Stock Recount - HUINV04
Post HU stock differences - HUINV05
Inventorize HU - HUINV06

Different status of HU's during Inventory:

Before creation of physical inventory document - HU status will be PHEX and WHSE Ideally ( Available to use)

  • Upon creation of physical inventory document - HU status will be INIV,PHEX and WHSE
  • If Physical inventory document is deleted then system will remove INIV status again
  • Perform Stock Count - INIV,PHEX and WHSE
  • Perform Stock Recount - INIV,PHEX and WHSE
  • Post HU stock differences - INVE,PHEX and WHSE ( In case of differences of stock between physical and Book value then system will adjust stock at IM and WM level as well once differences are posted)
  • Inventorise HU - INVE status will be removed and HU will be available again with PHEX and WHSE status

Thank you.

Comments

  1. Learned a lot of new things from your post!Good creation ,It's amazing blog Other wise if any one who want to learn software testing contact us on 9311002620 or visit our further website https://www.htsindia.com/software-testing-training-course

    ReplyDelete
  2. Very nice blog post. Thanks for sharing.

    Dynode Software established in 2004, it is one of the leading website development company in Patna started as a small software Development firm to make a mark in the IT Industry, which gradually went on web developing and exploring its dimensions with International Clients & has built a solid reputation amongst the most competitive market in order to match fulfill requirements as per client estimated.

    ReplyDelete
  3. Thanks for sharing such a great article with us. This surely helps me in my work.Thanks a lot if you are required any TAX and GSTR related information to visit our website click on :Tax Return Filing in bangalore


    ReplyDelete
  4. Learn SAP EWM Online Training by SAP Industry Expert. SAP S4 HANA EWM Online Training

    ReplyDelete
  5. Good to find this informative blog post.Its extremely good and very helpful for me.

    ERP Software for Manufacturing

    ReplyDelete
  6. Nice information thank you,if you want more information please visit our link
    ewm training
    sap ewm training in hyderabad

    ReplyDelete

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...