Project-Stock Handling units using HUPAST
Hi folks,
we want to use handling units with project stock (SOBKZ = Q). While it's easy to create handling units on project stock with HU02 it does not seem to be possible with HUPAST. System does not allow the edit the field SOBKZ in HUPAST.
Does anybody know how to create handling units with batches from project stock using the transaction HUPAST?
Thanks BR
MAtthias
Hi
You cann't do GR wid mvtType 101 for HU
you can do it through only vl01n
VLMOVE you can do .
Regards
Aryan
Don't forget to give points
Similar Messages
-
How to create Handling Unit using Process Order no. & Packing Instruction
Hi experts,
Please guide me how to create Handling Unit using Process Order number & Packing Instruction reference?Noramlly this is done using standard transaction 'COWBPACK'.
ANY FUNCTION MODULE OR BAPI TO DO THIS.
if any solution please explain with proper example..
Thanks In advance
Thanks,
YogeshHi experts,
Please guide me how to create Handling Unit using Process Order number & Packing Instruction reference?Noramlly this is done using standard transaction 'COWBPACK'.
ANY FUNCTION MODULE OR BAPI TO DO THIS.
if any solution please explain with proper example..
Thanks In advance
Thanks,
Yogesh -
How to fetch external handling unit# using delivery#
Hi Gurus,
Please tell me relationship how to fetch the VBEP-EXIDV(external handling unit) Using LIKP-VBELN(Outbound Delivery no) .
Any suggestions welcome.
Thanks in advance,Table vekp has a field SPE_DELDEC.
Also if field STATUS = 60, its deleted. -
Problem while unpacking an handling unit using FM HU_PACKING_AND_UNPACKING
Hi ,
I want to unpack an HU from an outbound delivery and transfer to other storage location using FM 'HU_PACKING_AND_UNPACKING'.I could find out that only quantities are transferred but unpacking HU is not done.
Below is the code i am using for unpacking.
CALL FUNCTION 'HU_GET_HUS'
EXPORTING
if_lock_hus = 'X'
it_venum = it_hu1
IMPORTING
et_header = it_hdr1
et_items = it_item1
EXCEPTIONS
hus_locked = 1
no_hu_found = 2
fatal_error = 3
OTHERS = 4.
IF sy-subrc <> 0.
l_error = 'X'.
CLEAR: g_msgid, g_msgno, g_msgv1,g_msgv2, g_msgv3, g_msgv4.
g_msgid = sy-msgid.
g_msgno = sy-msgno.
g_msgv1 = sy-msgv1.
g_msgv2 = sy-msgv2.
g_msgv3 = sy-msgv3.
g_msgv4 = sy-msgv4.
PERFORM message_scr USING g_msgid g_msgno g_msgv1 g_msgv2 g_msgv3 g_msgv4.
EXIT.
ENDIF.
LOOP AT it_hu1 INTO wa_hu.
CLEAR: wa_item1,l_error,l_post.
READ TABLE it_hdr1 INTO wa_hdr1 WITH KEY venum = wa_hu-venum.
CLEAR : g_venum, g_plant, g_sloc, g_whno, g_stype, g_sbin.
* get the warehouse details
SELECT SINGLE lgnum lgtyp lgpla FROM lein INTO (g_whno,g_stype,g_sbin)
WHERE lenum = wa_hdr1-exidv.
IF sy-subrc EQ 0.
* Get the plant and storage location for WM managed
SELECT SINGLE werks lgort FROM lqua INTO (g_plant, g_sloc)
WHERE lgnum = g_whno
AND lgtyp = g_stype
AND lgpla = g_sbin
AND lenum = wa_hdr1-exidv.
ELSE.
* Get the Venum (Internal HU Number)
SELECT SINGLE venum FROM vekp INTO g_venum
WHERE exidv = wa_hdr1-exidv.
IF sy-subrc EQ 0.
* Get the plant and storage location for Non-WM managed
SELECT SINGLE werks lgort FROM vepo INTO (g_plant, g_sloc)
WHERE venum = wa_hu-venum.
ENDIF.
ENDIF.
READ TABLE it_item1 INTO wa_item1 WITH KEY venum = wa_hu-venum.
IF sy-subrc = 0.
CLEAR :wa_pack_unpack.
MOVE-CORRESPONDING wa_item1 TO wa_pack_unpack.
wa_pack_unpack-venum = wa_item1-venum.
wa_pack_unpack-vepos = wa_item1-vepos.
wa_pack_unpack-velin = wa_item1-velin.
wa_pack_unpack-belnr = wa_item1-vbeln.
wa_pack_unpack-posnr = wa_item1-posnr.
MOVE wa_item1-vemng TO l_vemng.
CONCATENATE l_vemng '-' INTO l_vemng.
CONDENSE l_vemng NO-GAPS.
MOVE l_vemng TO wa_pack_unpack-quantity.
wa_pack_unpack-altme = wa_item1-altme.
wa_pack_unpack-matnr = wa_item1-matnr.
wa_pack_unpack-charg = wa_item1-charg.
wa_pack_unpack-werks = g_plant.
wa_pack_unpack-lgort = g_sloc.
wa_pack_unpack-wdatu = wa_item1-wdatu.
wa_pack_unpack-vfdat = wa_item1-vfdat.
ENDIF.
* *Find the partner location
CLEAR: g_hu_managed, g_partner_sloc.
CALL FUNCTION 'V51S_HU_LGORT'
EXPORTING
if_lgort = g_sloc
if_werks = g_plant
IMPORTING
ef_hu_managed = g_hu_managed
ef_partner_lgort = g_partner_sloc
EXCEPTIONS
lgort_not_exist = 1
OTHERS = 2.
IF sy-subrc <> 0.
ENDIF.
IF g_hu_managed = 'X'.
wa_pack_unpack-umlgo = g_partner_sloc.
ENDIF.
CALL FUNCTION 'HU_PACKING_AND_UNPACKING'
EXPORTING
is_packing_request = wa_pack_unpack
IMPORTING
es_p_request = wa_pack_unpack
EXCEPTIONS
missing_data = 1
hu_not_changeable = 2
not_possible = 3
customizing = 4
weight = 5
volume = 6
serial_nr = 7
fatal_error = 8
OTHERS = 9.
IF sy-subrc <> 0.
l_error = 'X'.
ELSE.
l_post = 'X'.
ENDIF.
IF l_error IS INITIAL AND l_post EQ 'X'.
CALL FUNCTION 'HU_POST'
EXPORTING
if_synchron = 'X'
if_commit = 'X'
IMPORTING
et_messages = it_messages.
ENDLOOP.
Please help if any parameter need to be set for unpacking of HU.
Please suggest.
Thanks in advance.Hi Sailaja,
I have similar requirements like this before with HU_PACKING_AND_UNPACKING FM. It was a tough debugging before I came up with the right solution. Unfortunately, I was not able to document that code..
But here is what I have been doing.
Youre on track with the solution below, never use BDC as it will only limit the Handling units that you wish to put into.
The function modules that starts with V5_ plays important role as you need to initialize the global variables and table of this function group with values before calling HU_PACKING_AND_UNPACKING FM
Debug inside the Function module, and look for the FM that returns SY-SUBRC <> 0 then set a breakpoint.
Restart the program then debug inside that FM again (and I do not want to go further on the details, I give you the presumption of literacy)
You will find some items that has no value, try to initialize everything by utilizing the FM for this function group V51S.
Happy Debugging. -
Goods Receipt for Handling Unit using RF
Hello,
The customer requirement is to do Goods Receipt for HU in RF. In RF the standard transaction is LM76 for GR for HU.
The scenario is Multiple handling units are there for each inbound delivery. the client wants to do GR for each HU. where as in
standard TC: LM76, if one HU is entered GR is done for the entire inbound delivery.
Can i go for customized transaction (is it possible to develop) in RF where GR is done for each handling unit ( i.e. multiple HU's
are there in the inbound delivery)
Regards,
NeethaHi,
I've done something similar on RF for a retailer in Holland and used enhancement MWMRFDLV/INCLUDE ZXLHUU31.
I've added an example of the code that is implemented.
This enhancement is called by transaction LM61 op to LM66 en LM71 up to LM76.
Transaction LM76 is initially intended to select the delivery by scanning the HU.
What I did is reducing the information on the sceen to the HU that has been scanned
Secondly yo need to assure that when the user is creating a TO or posting the GR it is performed for the HU only.
For this you need to do additional development mwmrf631 (= Delivery Header / in the PAI define your own logic that post the GR for a single HU) What I used is an outputtype in application V6 (HU) that is triggerred from include ZXLHUU21 and will post the GR with BAPI_GOODSMVT_CREATE' . See 2nd example include ZXLHuu21
I hope my comment are usefull for you.
Kind regards
Ronald
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INCLUDE ZXLHUU31
case sy-tcode.
WHEN con_lm76.
inperken OP HU als de levering meerdere Handling Units heeft
alleen dan inperken op HU informatie
LOOP AT et_postab WHERE posnr = '000000'.
SELECT SINGLE anzpk FROM likp INTO et_postab-anzpk
WHERE vbeln = et_postab-vbeln.
MODIFY et_postab.
IF et_postab-anzpk > 1.
EXIT.
ENDIF.
ENDLOOP.
CHECK et_postab-anzpk > 1.
GET PARAMETER ID 'INP_100' FIELD inp_100.
i_exidv = inp_100.
IF i_exidv NA sy-abcde.
et_postab-exidv = i_exidv.
et_postab-anzpk = 1.
LOOP AT et_postab WHERE posnr <> '000000'.
SELECT SINGLE aexidv abrgew b~vemng
INTO (et_postab-exidv, et_postab-brgew, et_postab-lfimg)
FROM vekp AS a INNER JOIN vepo AS b
ON avenum = bvenum
WHERE a~exidv = i_exidv
AND bvenum = avenum
AND b~vbeln = et_postab-vbeln
AND b~posnr = et_postab-posnr.
MODIFY et_postab.
ENDLOOP.
et_postab-anzpk = 1.
MODIFY et_postab TRANSPORTING exidv brgew anzpk WHERE posnr = '000000'.
DELETE et_postab WHERE exidv IS INITIAL.
SORT et_postab BY posnr.
ENDIF.
ENDCASE.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
EXIT_SAPLLMOB_084 INCLUDE ZXLHUU21 .
*& Include ZXLHUU21 *
Initial development by Perfect for People - Ronald Westdijk
o_current_field = current_field.
o_verification_errors[] = verification_errors[].
SET PARAMETER ID 'BYDLVRY' FIELD LIKP-VBELN.
CASE sy-tcode.
WHEN con_lm76.
CASE sy-ucomm.
WHEN fcode_save.
melding alleen geven als meerdere Handling Units bestaan
en als deze nog moeten worden geboekt.
SELECT SINGLE anzpk FROM likp INTO i_anzpk
WHERE vbeln = likp-vbeln.
CHECK i_anzpk > '1'.
check output messages in tabel NAST of deze nog moet worden geboekt.
melding alleen geven als er nog meerdere HU open staan.
eerst de HU's ophalen
daarna de nast records inlezen in i_nast (output ZMCR) en checken
REFRESH i_nast.
CLEAR vbco3.
vbco3-vbeln = likp-vbeln.
CALL FUNCTION 'SD_PACKING_PRINT_VIEW'
EXPORTING
comwa = vbco3
auftrag_nicht_lesen = 'X'
exportdaten_nicht_lesen = 'X'
TABLES
vbplk_tab = xvbplk
vbplp_tab = xvbplp
vbpls_tab = xvbpls.
LOOP AT xvbplk.
SELECT SINGLE * FROM nast INTO i_nast
WHERE vstat = '0'
AND kappl = 'V6'
AND objky = xvbplk-venum
AND kschl = 'ZMCR'.
IF sy-subrc = 0.
APPEND i_nast.
ENDIF.
ENDLOOP.
DESCRIBE TABLE i_nast LINES n.
CHECK n > 1.
message lf317 Het systeem zal de boeking uitvoeren, verder?
sy-msgid = 'LF'.
sy-msgno = '317'.
PERFORM warning_message(rlmob001).
GET PARAMETER ID 'POX' FIELD msg_answ.
SET PARAMETER ID 'POX' FIELD ''.
CASE msg_answ.
WHEN ver_on.
output ZMCR after HU to post Goods receipt is executed.
REFRESH bapihukey.
bapihukey-hu_exid = i_exidv.
APPEND bapihukey.
REFRESH bapioutptype.
bapioutptype-trans_medium = '8'.
bapioutptype-output_type = 'ZMCR'.
APPEND bapioutptype.
CALL FUNCTION 'BAPI_HU_PROCESS_MSG_DIRECT'
TABLES
hukey = bapihukey
outputtype = bapioutptype
return = bapiret2.
LEAVE TO TRANSACTION con_lm01.
ENDCASE.
ENDCASE.
ENDCASE. -
Problem in 301 Stock transfer via VLMOVE for Handling Unit movement
Hi Gurus
I am having one issue, where handling unit is active. So user facing one issues that user has posted the stock around 10 qty , after some material movements , stock showing as 9 in MMBE , where as checking the handling units showing 10 In HUMO . Now user wants to do the stock transfer 301 via VLMOVE. But system is giving error message like u201Cdeficit of stock, handling units can't be movedu201D, anybody advise is there anyway how user can do this transaction.
Regards
Edited by: venkat g on Aug 19, 2010 1:03 PMHi,
The solution for creating inbound delivery that you people have suggested is already in place. The problem is not with creation of inbound delivery but with assigning the material HUs to the inbound delivery. As material HUs are having status assigned to Shipment Document which is created after outbound delivery is processed. How should I go about it? Even after status of shipment document is made complete, assignment of HUs to inbound delivery is not possible. Please help to resolve this issue.
Thanks and regards,
Sudhir Dahake -
Hi All.
I have a material docuement which was created by HUPAST transaction code. How to trace the HU number? I have checked in HUMSEG table, but their is no HU assigned to the matertial document.
Also checked in HUMO transaction with matl and batch number?
Please help me to trace the Handling Unit number HU
Regards,
Prasadyes, the stock was moved using HUPAST, transaction code,
Please guide me how to trace the handling unit
regards,
satyaprasad -
SAP table for finding Quant from the Handling unit
Hi All,
I would like to know the SAP table name - from the handling unit (where the stock received in the Warehouse), i would like to corresponding Quant ?
PSSHi,
To know the QUANT for handling unit, use the table LQUA. -
can anybody explain handling units
-what is it's use
-how material are kept in W/H
i have gone thru help.sap but unable to understand concept
Nikhil
Edited by: nniikkhhiill on Feb 8, 2010 11:22 AMHi
Handling Unit Management
Purpose
You can use Handling Unit Management (HUM) to reflect packing-based logistics structures in the SAP System. Using this method, you track the movements of entire handling units and the materials they contain rather than tracking each material individually.
When you base logistics processes on handling units, goods movements processing is made easier, which in turn optimizes all logistics operations. This simplified processing includes the existing packing function in shipping and warehouse processing in the Warehouse Management system, which is expanded here.
Features
In the system, the handling unit (HU) expands on the shipping unit. Handling units can be nested, which means that you can create new handling units from several handling units as often as you like. At the material item level, HUs contain the complete material identification, the quantity, and, in the case of serial numbers, the respective object list. Handling units have unique, scannable identification numbers that can be developed according to standards such as EAN 128 or SSCC.
Handling units contain all inventory management information of the materials they contain that are maintained in Inventory Management. There are also status messages that you can call up at any time that indicate whether a handling unit is only planned or if the ship-to party has been notified of the arrival of this handling unit, or whether it is in the warehouse or has already been posted to goods issue. The integrated history function also records each business process in the life cycle of each handling unit, meaning that you can track the handling unitu2019s path and development at any time.
In HU-managed storage locations, all goods movements are executed through the specification of the respective HUs, and Inventory Management is performed through the handling units. If you are not working with HU-managed storage locations, you can use handling units (without stock information) as before in the delivery and in the shipment.
In HU-managed storage locations, materials can be managed in HUs only. Mixed stock (stock made up of packed and non-packed materials within the same storage location) is not supported. HUs can also be managed in interim storage types. Unpacking a material from an HU means that the stock of the material is posted to a storage location that is not HU-managed.
If you call up normal material movements in connection with an HU-managed storage location, a delivery is created, rather than a direct material posting, which has been the procedure up to this point.
Handling units are unique at client level in at least one system. Using an indicator at client level (see Unique Identification of Handling Units), you can control whether you are going to work with the HU functions. Since the handling unit is a physical unit, the central logistics processes are controlled through the input of the handling unit identification. These processes include putaway, picking, and stock transfers, as well as goods receipts and goods issues.
A handling unitu2019s mobility can be limited if quality checks are active. Changes in the stock category caused by a quality inspection are made using a posting change in the handling unit.
There is also a report available that you can use to find and display handling units using different selection criteria such as material, packing instruction, or storage location.
Although the handling unit is basically a unit that remains constant in the system, you can change it by repacking the materials it contains. All the packing functions, such as packing, repacking, and unpacking, are completely supported by the handling unit function. In this way, handling units can be created in production, during goods receipt, or in the packing areas of the warehouse. If you have automatic packing, the handling unit is created from the packing proposals defined in the system (from the packing instructions, for example).
Pl.go thorugh link
http://help.sap.com/erp2005_ehp_04/helpdata/EN/19/7f6d36f74c7505e10000009b38f839/frameset.htm
Edited by: Sanjay Shah on Feb 8, 2010 11:32 AM -
Hi folks,
I very urgently need some documents about SAP HUM.
Can any one help me.
LaxmananSAP HU - SAP Handling Unit Management (HUM)
The SAP HU is used for tracking the handling units used by the materials. Some common handling units are packagings materials like cartons, pallets etc.
In the SAP system, the handling unit (HU) expands on the shipping unit. Handling units can be nested and you can also create new handling units from several handling units as often as you like. At the material item level, HUs contain the complete material identification, the quantity, and, in the case of serial numbers, the respective object list. Handling units have unique,
scannable identification numbers that can be developed according to standards such as EAN 128 or SSCC.
Handling units contain all inventory management information of the materials they contain that are maintained in Inventory Management. There are also status messages that you can call up at any time that indicate whether a handling unit is only planned or if the ship-to party has been notified of the arrival of this handling unit, or whether it is in the warehouse or has already been posted to goods issue. The integrated history function also records each business process in
the life cycle of each handling unit, meaning that you can track the handling units path and development at any time.
Refer to : Logistics -> Central Functions -> Handling Unit Management
In HU-managed storage locations, all goods movements are executed through the specification of the respective HUs, and Inventory Management is performed through the handling units. If you are working without HU-managed storage locations, you can work with handling units (without stock information) as before in the delivery and in the shipment.
In HU-managed storage locations, materials can be managed in HUs only. Mixed stock made up of packed and non-packed materials within the same storage location are not supported. HUs can also be managed in interim storage types. Unpacking a material from a HU means that the stock of the material is posted to a storage location that is not HU-managed.
If you call up normal material movements in connection with an HU-managed storage location, a delivery is created, rather than a direct material posting, which has been the procedure up to now.
Please note that if you want to use 311 to move the material already in stock, but in a non HUM Storage Location and you want to transfer those materials into a HUM Storage Location 304. If this is the case you can use the transaction VLMOVE with the destination plant and storage location. Before that you have to create the HU with the transaction code HU02 Storage location: where the material is and the status: in stock.
Handling units are unique at client level in at least one system. Using an indicator at client level, you can control whether you are going to work with the HU functions. Since the handling unit is a physical unit, the central logistics processes are controlled through the input of the handling unit identification. These processes include putaway, picking, and stock transfers, as well as goods receipts and goods issues.
A handling units mobility can be limited if quality checks are active. Changes in the stock category caused by a quality inspection are made using a posting change in the handling unit.
There is also a report available that you can use to find and display handling units using different selection criteria such as material, packing instruction, or storage location.
Although the handling unit is basically a unit that remains constant in the system, you can change it by repacking the materials it contains. All the packing functions, such as packing, repacking, and unpacking, are completely supported by the handling unit functionality. In this way, handling units can be created in production, during goods receipt, or in the packing areas of the warehouse. If you have automatic packing, the handling unit is created from the packaging proposals defined in the system (from the packing instructions, for example).
Regards,
Rajesh Banka
Reward points if helpful. -
Hi Gurus,
How handling unit number selection happens in delivery document?
Does system determines this number automatically? If so from which table?
Thank you
ANilHi Anil,
Handling Unit Management
The SAP HU is used for tracking the handling units used by the materials. Some common handling units are packagings materials like cartons, pallets etc.
In the SAP system, the handling unit (HU) expands on the shipping unit. Handling units can be nested and you can also create new handling units from several handling units as often as you like. At the material item level, HUs contain the complete material identification, the quantity, and, in the case of serial numbers, the respective object list. Handling units have unique,
scannable identification numbers that can be developed according to standards such as EAN 128 or SSCC.
Handling units contain all inventory management information of the materials they contain that are maintained in Inventory Management. There are also status messages that you can call up at any time that indicate whether a handling unit is only planned or if the ship-to party has been notified of the arrival of this handling unit, or whether it is in the warehouse or has already been posted to goods issue. The integrated history function also records each business process in
the life cycle of each handling unit, meaning that you can track the handling unit's path and development at any time.
Refer to : Logistics -> Central Functions -> Handling Unit Management
In HU-managed storage locations, all goods movements are executed through the specification of the respective HUs, and Inventory Management is performed through the handling units. If you are working without HU-managed storage locations, you can work with handling units (without stock information) as before in the delivery and in the shipment.
In HU-managed storage locations, materials can be managed in HUs only. Mixed stock made up of packed and non-packed materials within the same storage location are not supported. HUs can also be managed in interim storage types. Unpacking a material from a HU means that the stock of the material is posted to a storage location that is not HU-managed.
If you call up normal material movements in connection with an HU-managed storage location, a delivery is created, rather than a direct material posting, which has been the procedure up to now.
Please note that if you want to use 311 to move the material already in stock, but in a non HUM Storage Location and you want to transfer those materials into a HUM Storage Location 304. If this is the case you can use the transaction VLMOVE with the destination plant and storage location. Before that you have to create the HU with the transaction code HU02 Storage location: where the material is and the status: in stock.
Handling units are unique at client level in at least one system. Using an indicator at client level, you can control whether you are going to work with the HU functions. Since the handling unit is a physical unit, the central logistics processes are controlled through the input of the handling unit identification. These processes include putaway, picking, and stock transfers, as well as goods receipts and goods issues.
A handling unit's mobility can be limited if quality checks are active. Changes in the stock category caused by a quality inspection are made using a posting change in the handling unit.
There is also a report available that you can use to find and display handling units using different selection criteria such as material, packing instruction, or storage location.
Although the handling unit is basically a unit that remains constant in the system, you can change it by repacking the materials it contains. All the packing functions, such as packing, repacking, and unpacking, are completely supported by the handling unit functionality. In this way, handling units can be created in production, during goods receipt, or in the packing areas of the warehouse. If you have automatic packing, the handling unit is created from the packaging proposals defined in the system (from the packing instructions, for example).
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula -
Provide information about handling units
Plz provide information about handling units. Explain all the paths and information about HU.
Hi,
Purpose
You can use Handling Unit Management (HUM) to reflect packing-based logistics structures in the SAP System. Using this method, you track the movements of entire handling units and the materials they contain rather than tracking each material individually.
When you base logistics processes on handling units, goods movements processing is made easier, which in turn optimizes all logistics operations. This simplified processing includes the existing packing function in shipping and warehouse processing in the Warehouse Management system, which is expanded here.
Features
In the system, the handling unit (HU) expands on the shipping unit. Handling units can be nested, which means that you can create new handling units from several handling units as often as you like. At the material item level, HUs contain the complete material identification, the quantity, and, in the case of serial numbers, the respective object list. Handling units have unique, scannable identification numbers that can be developed according to standards such as EAN 128 or SSCC.
Handling units contain all inventory management information of the materials they contain that are maintained in Inventory Management. There are also status messages that you can call up at any time that indicate whether a handling unit is only planned or if the ship-to party has been notified of the arrival of this handling unit, or whether it is in the warehouse or has already been posted to goods issue. The integrated history function also records each business process in the life cycle of each handling unit, meaning that you can track the handling units path and development at any time.
In HU-managed storage locations, all goods movements are executed through the specification of the respective HUs, and Inventory Management is performed through the handling units. If you are not working with HU-managed storage locations, you can use handling units (without stock information) as before in the delivery and in the shipment.
In HU-managed storage locations, materials can be managed in HUs only. Mixed stock (stock made up of packed and non-packed materials within the same storage location) is not supported. HUs can also be managed in interim storage types. Unpacking a material from an HU means that the stock of the material is posted to a storage location that is not HU-managed.
If you call up normal material movements in connection with an HU-managed storage location, a delivery is created, rather than a direct material posting, which has been the procedure up to this point.
Handling units are unique at client level in at least one system. Using an indicator at client level (see Unique Identification of Handling Units), you can control whether you are going to work with the HU functions. Since the handling unit is a physical unit, the central logistics processes are controlled through the input of the handling unit identification. These processes include putaway, picking, and stock transfers, as well as goods receipts and goods issues.
A handling units mobility can be limited if quality checks are active. Changes in the stock category caused by a quality inspection are made using a posting change in the handling unit.
There is also a report available that you can use to find and display handling units using different selection criteria such as material, packing instruction, or storage location.
Although the handling unit is basically a unit that remains constant in the system, you can change it by repacking the materials it contains. All the packing functions, such as packing, repacking, and unpacking, are completely supported by the handling unit function. In this way, handling units can be created in production, during goods receipt, or in the packing areas of the warehouse. If you have automatic packing, the handling unit is created from the packing proposals defined in the system (from the packing instructions, for example).
Regards
Adarsh Mathur -
hi,
i am going to my new implementation project WM & Handling Unit management...
I am frm MM side..I don't have any idea abt Handling unit mgmt
what r the pre requisites & what r the implementation steps ???
kindly help me
thanks
raj
Edited by: raj rajan on May 4, 2009 10:27 AMHi Raj,
sorry for late reply...
Please find a list of important wm transaction codes
LB01
Create Transfer Requirement
LB02
Change transfer requirement
LB03
Display Transfer Requirement
LB10
TRs for Storage Type
LB11
TRs for Material
LB12
TRs and Posting Change for MLEat.Doc.
LB13
TRs for Requirement
LD10
Clear decentralized inventory diff.
LD11
Clear differences for decentral.sys.
LI01
Create System Inventory Record
LI02
Change System Inventory Record
LI03
Display System Inventory Record
LI04
Print System Inventory Record
LI05
Inventory History for Storage Bin
LI06
Block stor.types for annual invent.
LI11
Enter Inventory Count
LI12
Change inventory count
LI13
Display Inventory Count
LI14
Start Inventory Recount
LI20
Clear Inventory Differences WM ?
LI21
Clear Inventory Differences in MM-IM
LL01
Warehouse Activity Monitor
LLVS
WM Menu
LN01
Number Ranges for Transfer Requirem.
LN02
Number Ranges for Transfer Orders
LN03
Number Ranges for Quants
LN04
Number Ranges for Posting Changes
LN05
Number Ranges for Inventory
LN06
Number Ranges for Reference Number
LN08
Number Range Maintenance:
LP10
Direct picking for PO
LP11
WM staging of crate parts WM
LP12
Staging release order parts (WM-PP)
LP21
WM replenishment for fixed bins WM
LP22
Replenishm. Planning for Fixed Bins
LQ01
Transfer Posting in Invent. Mgmt
LQ02
Transfer Posting in Invent. Mgmt
LS01
Create Warehouse Master Record
Also few tables that u must know:
T3001 Warehouse number
T320 Assignment MM Storage Location to WM Warehouse
MLGN Material / Warehouse number
Transfer requirement
LTBK Transfer requirement - header
LTBP Transfer requirement - item
Transfer order
LTAK Transfer order - header
LTAP Transfer order - item
Master data - stock positions
LQUA Quants
8.4 Inventory documents in WM
LINK Inventory document header
LINP Inventory document item
LINV Inventory data per quant
More info is available in this thread....
New to Materials Management / Warehouse Management?
Regards,
Swapnil -
Batch management & Handling unit management?
Dear Expert,
could you explain Batch management & Handling unit management?
thanks
saravanakumar.<b>HU:</b>
The SAP HU is used for tracking the handling units used by the materials. Some common handling units are packagings materials like cartons, pallets etc.
In the SAP system, the handling unit (HU) expands on the shipping unit. Handling units can be nested and you can also create new handling units from several handling units as often as you like. At the material item level, HUs contain the complete material identification, the quantity, and, in the case of serial numbers, the respective object list. Handling units have unique,
scannable identification numbers that can be developed according to standards such as EAN 128 or SSCC.
Handling units contain all inventory management information of the materials they contain that are maintained in Inventory Management. There are also status messages that you can call up at any time that indicate whether a handling unit is only planned or if the ship-to party has been notified of the arrival of this handling unit, or whether it is in the warehouse or has already been posted to goods issue. The integrated history function also records each business process in
the life cycle of each handling unit, meaning that you can track the handling units path and development at any time.
Refer to : Logistics -> Central Functions -> Handling Unit Management
In HU-managed storage locations, all goods movements are executed through the specification of the respective HUs, and Inventory Management is performed through the handling units. If you are working without HU-managed storage locations, you can work with handling units (without stock information) as before in the delivery and in the shipment.
In HU-managed storage locations, materials can be managed in HUs only. Mixed stock made up of packed and non-packed materials within the same storage location are not supported. HUs can also be managed in interim storage types. Unpacking a material from a HU means that the stock of the material is posted to a storage location that is not HU-managed.
If you call up normal material movements in connection with an HU-managed storage location, a delivery is created, rather than a direct material posting, which has been the procedure up to now.
Please note that if you want to use 311 to move the material already in stock, but in a non HUM Storage Location and you want to transfer those materials into a HUM Storage Location 304. If this is the case you can use the transaction VLMOVE with the destination plant and storage location. Before that you have to create the HU with the transaction code HU02 Storage location: where the material is and the status: in stock.
Handling units are unique at client level in at least one system. Using an indicator at client level, you can control whether you are going to work with the HU functions. Since the handling unit is a physical unit, the central logistics processes are controlled through the input of the handling unit identification. These processes include putaway, picking, and stock transfers, as well as goods receipts and goods issues.
A handling units mobility can be limited if quality checks are active. Changes in the stock category caused by a quality inspection are made using a posting change in the handling unit.
There is also a report available that you can use to find and display handling units using different selection criteria such as material, packing instruction, or storage location.
Although the handling unit is basically a unit that remains constant in the system, you can change it by repacking the materials it contains. All the packing functions, such as packing, repacking, and unpacking, are completely supported by the handling unit functionality. In this way, handling units can be created in production, during goods receipt, or in the packing areas of the warehouse. If you have automatic packing, the handling unit is created from the packaging proposals defined in the system (from the packing instructions, for example).
For more help follow the link
http://www.sap-img.com/shop/sap-handling-unit-management-configurations.htm
Batch:
In various industries particularly the process industry you have to work with homogenous partial quantities of a material or product throughout the logistics quantity and value chain.
There are various reasons for this:
Legal requirements (for example, the guidelines set out by GMP (Good Manufacturing Practice) or regulations on hazardous material
Defect tracing, callback activities, and regression requirement
The need for differentiated quantity-and value-based Inventory Management (for example, due to heterogeneous yield/result qualities or varying constituents in Production.
Differences in usage and the monitoring thereof in materials planning in SD and Production.
Production or procedural requirements (for example, settlement of material quantities on the basis of different batch specifications).
For more help you have to refer the SAP help -
Dear Friends,
I am able to create the Handling Units using BAPI_HU_CREATE but not able to assign the HU to delivery.
I can see the HUs are created in VEKP tables correctly.
I am using the FM 'HU_ASSIGN_HUS_TO_OBJECT' to assign this to delivery ( LIKP-VBELN ).
See the code below, in debugging all the values gets filled correctly including lt_hu_units but HUs are not assigned.
I can not see those later on in VL02 & then clicking on Pack from menu bar.
Not sure why the below FM not working correctly?
Pls. see portion of code below for your referance:
ls_hu_units-top_hu_external = lv_hukey.
ls_hu_units-venum = ls_huheader-hu_id.
ls_hu_units-rfbel = gs_header_details-vbeln.
ls_hu_units-rfpos = 10.
APPEND ls_hu_units TO lt_hu_units.
ls_object-object = 01.
ls_object-objkey = gs_header_details-vbeln.
CALL FUNCTION 'HU_ASSIGN_HUS_TO_OBJECT'
EXPORTING
is_object = ls_object
it_handling_units = lt_hu_units
IT_HUM_QM =
IMPORTING
et_messages = lt_messages
My Regards,
PrashantHi David.
There are two areas for creating packing instructions
Packing instructions and then packing instruction determination
Transaction POF1 and POP1 (Cannot remember which is which)
You will need materials set up to represent packing items such as pallets etc, and these are then included in the packing instruction.
Config in HUM will allow you change the level of determination, plant etc
Good luck
Maybe you are looking for
-
Is Adobe Acrobat 7.0 Professional compatible with Windows 7?
I've ordered Acrobat XI Pro, but it may be a week or two before I receive it. I need to make some pdf files from WordPerfect files and I already have Acrobat 7.0 Pro. I was hoping to be able to use the 7.0 until I receive the version XI.
-
Create hyperlink for reply to in mail body while sending email.
Hi All, We have a requirement where we need to create an hyperlink for reply to in the mail body. We have implemented entire functionality using CL_BCS classes and everything is working fine. Only problem we have is when we give document type as HTM
-
Photoshop CC (not a trial) is asking for my Adobe ID, saying it's trial software
Hi all, I've been using Photoshop CC since last August. Suddenly, this morning, opening Photoshop CC requires my Adobe ID; it's telling me that this is required for trial software. Huh? I've been paying every month to get... a trial? This is news to
-
Keeping my applications from closing after an hour
Sometimes I want to keep an application running, like an Internet radio station. But no matter how I try to disable shutdown and sleep functions, my Mac still shuts all applications after about 1 hour, and on my screen I find the login box against th
-
Low pass filter in LabVIEW Base Development System
Hello, I've got a problem for several days and I haven't find even a hint to fix it so it's driving me crazy. I'm developing an application on LabVIEW Base Development System for automatical aquisition and exploitation of five signals. These signals