Storage unit is without appendant HU

When doing a goods receipt for an inbound delivery into an HU-managed storage location, I get this error: "Storage unit 00000000001000000111 is without appendant HU".
Can some one help what this error is...........?
Much appreciated!
Edited by: Sylvia Hernandez on Mar 5, 2010 3:32 AM

HU is created while packing the inbound delivery....SU is also create as part of TO confirmation...........when i try to come back and post PGR, the system gives the appendant error.
Sylvia

Similar Messages

  • Need Ideas For Storage Units Data Storage Capabilities - Special Attributes? History? 2 Ind-UMs

    Hello experts,
    The company I'm working for is looking into permanently-storing pallet level information (keep a history of the pallet movements) and use RF-scanners to move product in the warehouse. They have made a decision to implement Warehouse Management's Storage Unit Management functionality. They looked into Handling Units as well, but they don't want to use HUs for many reasons.
    They would also like to store 2 units of measure at the Storage Unit level without activating "Catch Weight Management" because that would require them to run parallel systems for a while and also deal with CWM functionality restrictions. Keep in mind that most of the products they handle are catch-weight products, so UM conversions don't work for them.
    Solutions I have in mind:
    For storing 2 independent UMs: Store the quantity of the 2nd unit of measure in a custom table at the Storage Unit level and use custom RF-scanner programs to "receive, issue, scrap, and move" goods in the warehouse. These custom RF-scanner programs would update SAP standard table with 1st (base) UM and also custom table with 2nd UM.
    For permanenlty-storing SU history: Use custom table to to store Storage Unit History. The custom programs created to handle the SUs would update this custom table.
    Last time I checked, the history of a Storage Unit is not recorded in SAP, correct? ONLY in Handling Units, correct?
    OR are there any documents/tables that permanently store the Storage Unit number so they can be queried after the Storage Unit is consumed/issued?
    I know SAP keeps improving its applications with every release, so I'm just looking at my options here.
    Does anyone else have any other ideas on how to approach this other than Using Handling Units & Catch Weight Management?
    Thanks in advance!
    -Mr. Bello
    Message was edited by: Jürgen L

    For storing 2 independent UMs
    Can you please explore the LS26 option there also system is allowing you to change the parameter"Unit of measure" and displays the stock on different UoM, hopefully this will solve your problem and you need not design a custom table to store the value at different UoM level
    For permanenlty-storing SU history:
    System store the storage unit related value in table : LEIN however the moment you do any consumption or movement to non SU the entries goes off from this table hence i think the approach taken by you seems the only one approach  to store the historical data. (Make sure you are taking into consideration of the archiving activity as you proceed further the size of database will get bigger and time to generate any report will take longer then expected

  • Reprint Storage Unit Label

    How can I reprint a storage unit label (without having to create a new TO)? Assume that the label is damaged and I have to print a new one and replace the damaged one.
    Thanks.

    LT32 prints SU label according to open transfer orders that contain the SU. This is not what I need. I need to reprint the label for an existing SU without having to use a TO. The material is not moved at all.

  • Issue with Storage Unit Type (LETYP) in L_TO_CREATE_TR

    Hi Experts,
    I need help in the function module "L_TO_CREATE_TR". using in Warehouse Management(WM) module.
    In theis function module I am passing LETYP(Storage Unit Type) value in IT_TRITE parameter, but this is not considering my value instead of this it is considering the value which is coming based on Source Storage type.
    Can any one aware of this issue ?
    Please let me know.
    Thanks & Regards,
    Chandu

    Hi,
    Pass the Storage type details to NLTYP/ VLTYP. For destination storage details NLTYP and NLPLA. For Souce storage details VLTYP and VLPLA.
    No need to pass to LETYP value.
    " Pass these values
                ls_trite-tbpos      =     "Transfer Requirement
                ls_trite-nltyp      =      "Destination storage type
                ls_trite-nlpla      =      "Destination storage bin
                ls_trite-anfme      =     "Quantity
                ls_trite-vltyp      =     "Source storage type
                ls_trite-vlpla      =    "Source storage bin
                ls_trite-altme      =    "Unit of measurement
                APPEND ls_trite TO lt_trite.
    CALL FUNCTION 'L_TO_CREATE_TR'
                EXPORTING
                  i_lgnum                  =  "Warehouse
                  i_tbnum                  =  "Transfer Requirement
                  i_update_task            = 'X'
                  i_commit_work            = 'X'
                  it_trite                = lt_trite
    This will create a TO w.r.t TR
    Regards,
    Karuna

  • Storage unit types and storage bin types  - Need

    Hi,
    i want to know what is the use of the storage unit type and storage bin type.
    thanks,
    Maxx

    Dear Maxx,
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/c6/f844694afa11d182b90000e829fbfe/frameset.htm
    Storage Bin:
    A storage type generally contains several storage spaces or slots. These are called storage bins in Warehouse Management (WM). The storage bin is the smallest available unit of space in a warehouse. The storage bin therefore describes the position in the warehouse where the goods are or can be stored.
    Since the address of a storage bin is frequently derived from a coordinate system, a storage bin is often referred to as a coordinate. The coordinate 01-02-03 for example, can refer to a storage bin in row 1, stack 2, and level 3.
    You assign each storage bin to a specific warehouse number and storage type according to its location. You must also assign each storage bin to a storage section.
    You can also define the following additional characteristics of a storage bin:
    Maximum weight
    Total capacity
    Fire containment section
    Storage bin type (for example, for small or large pallets)
    With certain stock placement strategies, the storage bin type plays a significant role in optimizing the automatic search for a storage bin in connection with the pallet type. For example, you can define the WM putaway strategy to place large industrial pallets into a specific large bin type and smaller pallets into small bins.
    Storage Unit:
    In the system, a storage unit record consists of a header and at least one material data record (quant data record).
    The header contains information which is relevant for the entire storage unit and includes the:
    Storage unit number
    Storage unit type (SUT) of the storage unit
    Storage bin in which the storage unit is currently located
    Status, which provides current information about the storage unit
    Specific information about the stock contained in a storage unit is found in the material data record. The material record is already familiar to you in the existing system as a quant data record. For SU management, this information can be managed at the storage unit level.
    The following graphics illustrate how WM handles storage bins with and without the use of storage unit management. For these examples, storage bins are displayed in which 200 boxes of red pencils and 50 boxes of blue pencils are stored. The stock is distributed on two pallets.
    Hope this will help.
    Regards,
    Naveen.

  • Storage Unit stays after L_TO_CREATE_DN

    Hi,
    I use L_TO_CREATE_DN to pick SUs (Storage Unit) and post goods movements. I give the parameter "KOMIM = 2".
    The WM Stock (LQUA table) lines disappear as expected, but the SU header data (LEIN table) stays without any change. It causes many problems.
    Any ideas ?
    Regards,

    Hi.
    By using L_TO_CREATE_DN, you are creating and confirming TO?
    When you create a TO you should get your SU assigned to it (if your storage type is not bulk or open storage etc.)... I gues that works for you since you have automated the process... So after confirming the TO, this SU should disappear (check in LS33 for your SU if it exists), but it doesn't necessarily have to disappear - e.g. if your SU has 100 cs and you picked 50 cs from it. It should still exist with qty of 50 cs.
    Instead of looking at table LEIN, check if your SU is showing in LS33.
    Regards,
    Mihailo

  • When to introduce Storage Unit into a warehouse business

    Hi all,
    I am new in storage unit and I did read up a couple website about the storage unit and know how it work.
    However, I am wondering if you can share your experience with regards to following questions.
    In what kind of warehouse operation setting best suit to use SAP storage unit functionality? Does the warehouse business process require to meet some basic pre-requisites before a storage unit process of SAP is consider feasible and not overkill or will provide value added to the whole warehouse operation?
    Is there any concern or remification of introducing SAP SU into a warehouse operation (both from system and business perspective). In another word, impact to other module as a result of SU.
    Looking forward to your feedback.
    Regards,
    Daniel

    Hello Daniel, there are a number of reasons and scenarios for introduction of storage units.
    I assume you want to use / are using - RF devices for WM...
    From the aspect of warehouse operations if your products don't have printed material bar codes, then you would need to print them at some point in order to be able to scan your materials during transfer order confirmation. When you have batch management too, in bulk storage types everything gets more complicated since if you don't have storage unit management, and have batch managed materials, you also need to scan batch number in addition to scanning your material bar code. Ok, now you need to have that batch number bar-coded too. This gets a bit tricky, scanning two bar codes, printing 2 bar codes... Then why not introduce storage unit management and kill a couple of flies with one hit?
    What storage unit does, is keep all the info stored in itself.
    SU keeps track of material inside it, batch number, etc. So when you are picking from bulk storage type, by simply scanning SU you want to pick, you are actually specifying all the info from that SU, like material, batch, etc.
    Someone will argue that material bar-code isn't mandatory to be scanned and yes it can be switched off, but it leaves you with a lot of room for mistakes, so if you don't have SU management, you need to scan the material + batch.
    Also, it is easier to perform physical inventory with RF and storage unit managed warehouse. If you are having batch management that is.
    From business point of view first we can think of traceability (not in the meaning of standard batch traceability) => like having the information of which exact pallet went to which customer.
    When you scan storage unit for picking to customer 1234, you will have the information where did the exact pallet go, if you need that kind of info.
    You can also have some sort of functionality like that without SU management, because you can actually store more information in one bar code, like scanning once and having all the info in one long number (by parsing the number you can assign that info to the appropriate fields in RF transactions).
    And that's one good approach too if you don't want storage unit management but want to scan only once, but this requires some modifications to RF programs to be able to parse the scanned data into multiple data fields. Storage unit does something like that with just a bit of customizing.
    Actually there are a lot of good things SU introduces in your warehouse, but sometimes it is overkill indeed, if you don't really need it then don't implement it, sometimes things are good to be kept simple, although I seem to thing about SU management to be the simplest way of operating WH.
    If you need any further clarification or question about SU, feel free...
    Regards,
    Mihailo

  • R/3 request storage unit during TO confirmation

    Dear all,
    I bump into an obstacle while perform TO confirmation.
    During TO confirnmation, there is one screen requesting me to key in the storage unit.
    I tried to put in some of the storage unit from the the search screen (i.e. the little round shape next to the field), but system don't allow.
    May I know how to handle this?
    Do I need to create a new storage unit and put in to this field during TO confirmation?
    thanks
    tuff

    Dear Sinéad, and other,
    Ok this is how I bump into the error (in between, my WM knowledge has not reach the Storage Unit yet).
    I have created a TO for picking from a delivery order via VL02N's menu screen (i.e. movement type 601). Next, I perform a TO confirmation in LT12, and when I click the "Confirm Internally" button, R/3 jumps to this screen requesting the following two data:
    1- Storage unit
    << I tried to assign some randomly existing SU unit to this field but R/3 complaint "Storage unit 00157032650003548391 does not exist Message no. L3209">>
    2- Destination Storage Unit
    << I tried to assign some randomly existing SU unit to this field but R/3 complaint "Target handling unit 157032650000046104 is not assigned to TO 0000353991 Message no. L3822">>
    I just don't know how to proceed now as without the confirmation there is no picking (i.e. as the actual quantity field in the LT12 screen still empty) and there is a problem on PGI later on my delivery.
    Please teach me how to proceed when encounter above obstacles.
    thanks
    tuff

  • Simple Storage unit management by using of 'real' handling unit data

    Hi all,
    actually we have a WM setup to use the full handling unit management in Warehouse. After some years we detected that the HU managed
    Warehouse is not the best solution for our business.
    Inside of WM we do no more want to have the Handling units. The assigned storage location is not HU managed.
    Now to my question:
    We receive from other plants finished goods via inbound delivery. All goods are packed on Handling Units.
    When doing the good receipt, Is it possible to use the HU data (vekp, vepo) and create according to it the WM storage units? So one Handling unit
    from the inbound delivery will become one storage unit.
    thanks in advance for your answers.
    Michael

    Hi Patrick,
    we actually have SAP WM with HU management running. but we want to go back to WM without HU management - only with the storage unit management.
    when getting an inbound delivery from another plant (in the same client) goods are batch managed and packed on HU´s. i am searching for a possibility to use the HU data from the inbound delivery to create the WM storage units. So one HU should become one WM storage unit.
    so i will post to an ERP comuity.
    thanks
    Michael

  • External number range for storage units

    I have been trying to set this up without success.
    1. If I set up an external number range and assign it, then the system tells me to set up an internal number range.
    2. If I set up an internal number range the system does not allow manual input (external assignment from internal number range not allowed).
    I have allowed internal and external assignment for the warehouse.
    This is the error that I get when trying scenario 2.
    "External assignment of numbers from an internal number range not allowed
    Message no. L3212
    Diagnosis
    The external storage unit number to be issued is in an internal number range.
    Procedure
    Unlike other applications, external number ranges in the WM system are not explicitly defined.  Instead, they are taken from the unused numbers in the internal number ranges when the "Issue type" switch in the Customizing application allows external numbers to be issued for the warehouse number."
    So does this saying that external number assignment is not possible? Or is it saying that I have to use internal range even for external numbering? What is the solution?

    Please have a look at OSS note no. 14881.
    Best regards,
    Christiane Schnellenbach

  • Process of Clearing WM Data at Storage Unit Level

    Dear All,
    I have an issue where our client has decide to temporaryly halt the WM function which was implemented for past three weeks. Now i have stocks in the new warehouse storage locations both in IM & WM. Presently the users are executing the IM Function but not the WM (Storage Unit ) part. They do not want to execute storage unit level process due to practical concerns. How do i go about clearing the WM part of the stock, since the storage unit level information is wrong at present.
    I might have asked this question before this, i would appreciate if you could provide me a detailed procedure, on how i have to go about clearing the WM Data, and enable the user to procedure with the IM Process as before.
    Thanks & Regards
    Shabeen Buhary

    Dear Frenchy,
    Thanks for your response. That is exactly what i am doing at the moment. Transfer the stocks at roll level to 999 storage type.
    I am also looking into the possible of using LI21. But my concern is at the present moment i do not want to maintain any stocks at storage unit level (since the users have stopped using the WM Module due to technical & practical reasons). So storage unit level info is not important for them they want to only execute the IM Part, is there a possibility where i could just remove the storage unit level stocks without affecting the IM portion (since the IM Portion is correct). Any standard transaction, movement type to exexute this.
    And alternative option i presume is to transfer the stocks from the warehouse storage location to non warehouse storage location.
    Regards
    Shabeen Buhary

  • Apple set my iCloud storage at $40 without asking or telling me. They won't let me contact them to fix that unless I pay for support. Nor will they let me downgrade. How do I talk to Apple?

    Apple set my iCloud storage at $40 without asking or telling me. They won't let me contact them to fix that unless I pay for support. Nor will they let me downgrade. How do I talk to Apple?

    Have you actually been charged? Did you convert from MobileMe?  If so, you'll be automatically put on that plan, but revert to the free one when your current one expires.

  • Problems when creating a  transfer order for moving storage units

    Hi,
    When creating a TO for moving storage units with FM FU L_TO_CREATE_MOVE_SU i got problems when the storage unit consist of 2 items. The message 'Warehouse number does not exist (new selection required)'
    is displayed. When i use the FM again after this message then the TO is created correctly.
    When i debug the FM for 2 items is see that LEIN-LGNUM is empy en when performing:
    PERFORM T300_LESEN(SAPML03T) USING LEIN-LGNUM. and the message E080 is raised.
    The perform before this is determining the lein-lgnum (PERFORM LENUM_EINL_CHECK(SAPML03T) USING I_LENUM) but this value isnt passed to the calling program the first time (memory or something????)
    Does anyone have a solution for this problem?
    Thx in advance.
    Kind regards,
    John Nijburg

    Hello,
    I had the same problem today and I've fixed it by calling the FM in a different task (asychronous) .. this way the fugr/internal variables will be loaded again and you won't get this stupid error anymore. 
    CALL FUNCTION 'L_TO_CREATE_MOVE_SU' STARTING NEW TASK lv_task
    In case you need it syncronous use PERFORMING clause together with WAIT UNITL
    Hope this helps!
    Cristian

  • Unable to confirm transfer order due to error message "enter a storage unit

    Hi guys:
    I am unable to confirm transfer order due to error message popping up and saying "enter a storage unit", and I tried to search it in whole thread in the forum,it was suggestion to pick up destination storage unit via ls24, but I did went to ls24 and trying to click that line(transfer order) but unable to find the storage unit, so is there another way to fix it?

    Hi Allen...
    Pls check if your Storage Type is SU Active. If yes, then system will create a storage unit according to the setting done for the storage unit management, perhaps in your case you are confirmin TO for the putaway.
    Pls confirm and revert
    Regards
    Shiva

  • Split transfer order on the basis of Storage Unit type(SUT)

    Hi,
    I got one problem and want the solution for that immediately.the problem is as follows:-
    The transfer Order needs to be split by quantity according to the quantity per Storage Unit Type.
    I have to do this making chages in the SAP standard user Exit EXIT_SAPLL03A_12 in the program SAPML03T.
    Eg.One scenario is provided
    •Scenario 1:     Perform transaction MIGO with a movement type ‘101’ for Outbound Delivery 80000201. Enter a quantity of 15 kgs.
    the result should be as follows:
    •Scenario 1: Check TO’s created by going to transaction LT22. Enter Warehouse number 200; Storage type 902. Select the Dynamic Selections button and select ‘Transfer order Item’. Double click on Material and enter the material number (W075006). The SUT is 5kg so the expected result is for 3 TO’s to have been created.
    Means one TO got splitted in 3 TOs.
    Please provide me the help.

    Hi Vinay,
    This can be done purely through customizing. Please check IMG -> Logistics Execution -> Warehouse Management -> Activities -> Transfers -> Processing Performance Data/Split. You will need to define a sorting profile for TO split in where LETYP (storage unit type) can be used as sorting condition. The sorting profile should then be assigned to defined TO split.
    Hope it helps.
    Have a nice weekend!

Maybe you are looking for