Skip to main content

Handling Unit Management Basics - 1

We normally come across warehouses which is handled in Cases/Boxes or Pallets. Handling goods in this manner will make life of the warehouse clerk easy.

Warehouse activities is broadly divided into three categories :

1. Inbound
2. Outbound
3. Internal

Inbound activity

Receiving department of the warehouse will be responsible for this, Where they deals with receiving of goods from the vendors.

Whenever we receive stock into a storage location which is HU Managed then delivery will be created automatically based one the settings in the LG-HU view.

In delivery will be do packing and put the stock the respective location.

Outbound Activity

Dispatching the goods to the customer will be done through this process. Ideally shipping department is responsible for this.

During dispatch to customer stock from a HU managed storage location stock need to be packed and only then goods issue will be allowed to be performed

Internal Activity

Movement of goods within the warehouse will be treated as an internal activity. Even in this situation, If the receiving storage location is HU managed then delivery will be created for this as well.

Movement of goods from unrestricted to quality inspection or to any other stock categories.

Movement of goods between storage types or bins come under this category.

Comments

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...