Storage Unit Date

Dear Experts
Please advice which exit / badi / enhancement can be used to derive the same / orginal storage unit date in case when we transfer stocks from one storage location to other.
when the stocks are transfered from one Sloc - WM location to other Sloc WM location, the system consumes the orginal storage unit in the source location and creates new storage unit in the destination location. due to this the ageing of the item in the destination storage bin becomes new and the system does not consider the orginal storage unit number
Can you please help me find a solution for this since the ageing report is being developed and derived from BI
Thanks

closed

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

Mixing materials with different Goods Receipt date in the same Storage Unit

Hello everybody,
I´d like to know how FIFO strategy would affect to this example:
Adding boxes from one storage unit (pallet) to another storage unit (pallet). Both storage units have different goods receipt dates, so there is a pallet which has boxes with different GR dates.
Would FIFO make difference among boxes inside the storage unit?. As far as I know, when adding stock (boxes) to a handling unit (pallet), the system keeps the oldest GR date and does not create new quant number for the incoming boxes
Thanks in advance for your help

Hi Nagesh,
Thank you for the input. I am receiving Stock from vendor and while creating Inbound delivery i created the Handling Unit and also packed it and i could also post it (PG Receipt). Now when i am creating TO i have that error message. The Storage Location where i am receiving is 9001and i have also maintained the partner Storage location,,, its like this Plant(1000)-SLoc(9001)-Partner SLoc(9002).... now the Storage Location 9002 is not HU managed,, the reason i gave this Storage location is, initially i gave 9001, but system said "Storage Location 9001 and 9001 must have different management systems". So now kindly tell me what is the purpose of the partner Storage location and which storage location should i give, as my partner Storage location across "1000-9001-????" thank you again for ur inputs.
Regards,
Samuel

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

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

Function module which changes the Storage Unit (SU) Block Data like LS32

Hi,
Is there any Function module which changes the Storage Unit (SU) Block Data as done in LS32.
Thank you,
Prashanth A.

Hello Pablo.
Yes we did run LT04 and it does encounter that same error message after clicking the Stock Removal button. But eventually error msg will be removed by entering the value at the Storage Unit Type field because it directly fills in LTAP-LETYP.
We have resolved that the function module will not really fill the desired Storage unit type therefore TO background creation is not feasible in our scenario (non-SU managed transfer to SU-managed storage type). And I found this thread too: http://scn.sap.com/thread/1947358
So issue is still open but we have considered of changing the process since this is still just a new scenario for us.
Thanks a lot for your inputs!

Storage location Data is not saving in table MARD using BAPI method.

Hi Experts,
TABLES: T001L, "Storage Locations
        MARA, "General Material Data
        MAKT, "Material Descriptions
        MBEW, "Material Valuation
        MARC, "Plant Data for Material
        MARD. "Storage Location Data for Mate
DATA: BAPI_HEAD   LIKE BAPIMATHEAD, "MATERIAL
      BAPI_MAKT   LIKE BAPI_MAKT,    "Material Description
      BAPI_MARA1 LIKE BAPI_MARA,    "Client Data
      BAPI_MARAX LIKE BAPI_MARAX,
      BAPI_MARC1 LIKE BAPI_MARC,    "Plant View
      BAPI_MARCX LIKE BAPI_MARCX,
      BAPI_MBEW1 LIKE BAPI_MBEW,    "Accounting View
      BAPI_MBEWX LIKE BAPI_MBEWX,
      BAPI_MARD1 LIKE BAPI_MARD,    "Storage location
      BAPI_MARDX LIKE BAPI_MARDX,
      BAPI_RETURN LIKE BAPIRET2.
DATA: BEGIN OF INT_MAKT OCCURS 100.
        INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF INT_MAKT.
DATA: BEGIN OF INT_MAT OCCURS 100,
         WERKS(4),     "Plant
         LGORT(4),     "Storage location
         MTART(4),     "Material type
         MATNR(18),    "Material number
         MAKTX(40),     "Material description
         MATKL(9) ,    "Material group
         MBRSH(1),     "Industry sector
         MEINS(3),     "Base unit of measure
         GEWEI(3),     "Weight Unit
         SPART(2),     "Division
         EKGRP(3),     "Purchasing group
         VPRSV(1),     "Price control indicator
         STPRS(12),    "Standard price
         PEINH(3),     "Price unit
         SPRAS(2),     "Language key
         BKLAS(4),     "VALUATION CLASS
         VERPR TYPE VERPR_BAPI,    "MOVING PRICE
         BWTTY(1),     "Valuation Catogory
         MLAST(1),     "Price determination
         MLMAA(1),     "Material Ledger
         EKLAS(4),     "Valuation Class for sales order stock
         QKLAS(4),     "Valuation Class for Project Stock
         ZKPRS TYPE DZKPRS, "Future price
         ZKDAT TYPE DZKDAT, "Valid From Date
         BWPRS TYPE BWPRS, "Tax price 1
         BWPS1 TYPE BWPS1, "Tax price 2
         VJBWS TYPE VJBWS, "Tax price 3
         ABWKZ TYPE ABWKZ, "Devaluatin indicator
         BWPRH TYPE BWPRH, "Commercial price 1
         BWPH1 TYPE BWPH1, "Commercial price 2
         VJBWH TYPE VJBWH, "Commercial Price 3
         XLIFO(1),          "LIFO/FIFO revelant
         MYPOL(4),          "Pool no for LIFO
         MMSTA(2),          "Plant specific material status
         AUSME TYPE AUSME, "Unit of issue
         QMATA(6),          "Material Authorization group
         RBNRM(9),          "Catalog Profile
         WEBAZ TYPE WEBAZ, "Goods reciept processing time in days
         PRFRQ TYPE PRFRQ, "Recurring Insepction
         SSQSS(8),          "QM Control key
         QZGTP(4),          "Certificate Type
         QSSYS(4),          "Required QM system for vendor
       END OF INT_MAT.
DATA: V_MATNR TYPE MARA-MATNR.
SELECT-OPTIONS:
            PLANT    FOR MARC-WERKS OBLIGATORY MEMORY ID PLT,
            S_LGORT FOR MARD-LGORT MEMORY ID STL,
            MATERIAL FOR MARA-MATNR MEMORY ID MAT,
            MATLTYPE FOR MARA-MTART MEMORY ID MTY,
            DIVISION FOR MARA-SPART MEMORY ID DIV.
PARAMETERS: F_FILE LIKE RLGRAP-FILENAME
             DEFAULT 'C:\DATA\ZMATERIAL.XLS' MEMORY ID F_FILE,
GETDATA AS CHECKBOX, "Tick to download materials data to local harddisk
         UPDDATA AS CHECKBOX. "Tick to update date to Materials Master
IF GETDATA = 'X'.
   PERFORM DOWNLOAD_DATA.
   PERFORM DOWNLOAD_FILE.
ENDIF.
IF UPDDATA = 'X'.
   PERFORM UPLOAD_FILE.
   PERFORM UPDATE_MM.
ENDIF.
FORM DOWNLOAD_DATA.
SELECT * FROM MARC WHERE LVORM EQ ' '
                      AND WERKS IN PLANT
                      AND MATNR IN MATERIAL.
    CLEAR MARA.
    SELECT SINGLE * FROM MARA WHERE MATNR = MARC-MATNR.
    CHECK MATLTYPE.
    CHECK DIVISION.
    CLEAR MBEW.
    SELECT SINGLE * FROM MBEW WHERE MATNR = MARC-MATNR
                                AND BWKEY = MARC-WERKS.
    CLEAR MAKT.
    SELECT SINGLE * FROM MAKT WHERE SPRAS = 'EN'
                                AND MATNR = MARC-MATNR.
    CLEAR MARD.
    SELECT SINGLE * FROM MARD WHERE WERKS IN PLANT
                              AND   LGORT IN S_LGORT.
    WRITE:/ MARC-WERKS,    "Plant
            MARD-LGORT,    "Storage location
            MARA-MTART,    "Material type
            MARA-MATNR,    "Material number
            MARA-MATKL,    "Material group
            MARA-MBRSH,    "Industry sector
            MARA-MEINS,    "Base unit of measure
            MARA-GEWEI,    "Weight Unit
            MARA-SPART,    "Division
            MARC-EKGRP,    "Purchasing group
            MBEW-VPRSV,    "Price control indicator
            MBEW-STPRS,    "Standard price
            MBEW-PEINH,    "Price unit
            MBEW-BKLAS,    "VALUE CLASS
            MAKT-SPRAS,    "Language key
            MBEW-BKLAS,    "Valuation Class
            MBEW-VERPR,    "Moving price
            MAKT-MAKTX,    "Material description
            MBEW-BWTTY,    "Valutaion Catogorey
            MBEW-MLAST,    "Price Determination
            MBEW-MLMAA,    "Material Ledger
            MBEW-EKLAS,    "Valuation class for Sales order stock
            MBEW-QKLAS,    "Valutaion Class for Project Stock
            MBEW-ZKPRS,    "Future Price
            MBEW-ZKDAT,    "Valid From Date
            MBEW-BWPRS,    "Tax price 1
            MBEW-BWPS1,    "Tax price 2
            MBEW-VJBWS,    "Tax price 3
            MBEW-ABWKZ,    "Devaluatin indicator
            MBEW-BWPRH,    "Commercial price 1
            MBEW-BWPH1,    "Commercial price 2
            MBEW-VJBWH,    "Commercial Price 3
            MBEW-XLIFO,    "LIFO/FIFO revelant
            MBEW-MYPOL,    "Pool no for LIFO
            MARC-MMSTA,    "Plant specific material status
            MARC-AUSME,    "Unit of issue
            MARC-QMATA,    "Material Authorization group
            MARA-RBNRM,    "Catalog Profile
            MARC-WEBAZ,    "Goods reciept processing time in days
            MARC-PRFRQ,    "Recurring Insepction
            MARC-SSQSS,    "QM Control key
            MARC-QZGTP,    "Certificate Type
            MARC-QSSYS.    "Required QM system for vendor
            INT_MAT-WERKS = MARC-WERKS.    "Plant
            INT_MAT-LGORT = MARD-LGORT.    "Storage Location
            INT_MAT-MTART = MARA-MTART.    "Material type
            INT_MAT-MATNR = MARA-MATNR.    "Material number
            INT_MAT-MAKTX = MAKT-MAKTX.    "Material description
            INT_MAT-MATKL = MARA-MATKL.    "Material group
            INT_MAT-MBRSH = MARA-MBRSH.    "Industry sector
            INT_MAT-MEINS = MARA-MEINS.    "Base unit of measure
            INT_MAT-GEWEI = MARA-GEWEI.    "Weight Unit
            INT_MAT-SPART = MARA-SPART.    "Division
            INT_MAT-EKGRP = MARC-EKGRP.    "Purchasing group
            INT_MAT-VPRSV = MBEW-VPRSV.    "Price control indicator
            INT_MAT-STPRS = MBEW-STPRS.    "Standard price
            INT_MAT-PEINH = MBEW-PEINH.    "Price unit
            INT_MAT-SPRAS = MAKT-SPRAS.    "Language key
            INT_MAT-BKLAS = MBEW-BKLAS.    "VALVATION CLASS
            INT_MAT-VERPR = MBEW-VERPR.    "MOVING price
            INT_MAT-BWTTY = MBEW-BWTTY.    "Valutaion Catogorey
            INT_MAT-MLAST = MBEW-MLAST.    "Price Determination
            INT_MAT-MLMAA = MBEW-MLMAA.    "Material Ledger
            INT_MAT-EKLAS = MBEW-EKLAS.    "Valuation class forS.O Stock
            INT_MAT-QKLAS = MBEW-QKLAS.    "Valutaion Class for Project
            INT_MAT-ZKPRS = MBEW-ZKPRS.    "Future Price
            INT_MAT-ZKDAT = MBEW-ZKDAT.    "Valid From Date
            INT_MAT-BWPRS = MBEW-BWPRS.    "Tax price 1
            INT_MAT-BWPS1 = MBEW-BWPS1.    "Tax price 2
            INT_MAT-VJBWS = MBEW-VJBWS.    "Tax price 3
            INT_MAT-ABWKZ = MBEW-ABWKZ.    "Devaluatin indicator
            INT_MAT-BWPRH = MBEW-BWPRH.    "Commercial price 1
            INT_MAT-BWPH1 = MBEW-BWPH1.    "Commercial price 2
            INT_MAT-VJBWH = MBEW-VJBWH.    "Commercial Price 3
            INT_MAT-XLIFO = MBEW-XLIFO.    "LIFO/FIFO revelant
            INT_MAT-MYPOL = MBEW-MYPOL.    "Pool no for LIFO
            INT_MAT-MMSTA = MARC-MMSTA.    "Plant specific material
            INT_MAT-AUSME = MARC-AUSME.    "Unit of issue
            INT_MAT-QMATA = MARC-QMATA.    "Material Authorization group
            INT_MAT-RBNRM = MARA-RBNRM.    "Catalog Profile
            INT_MAT-WEBAZ = MARC-WEBAZ.    "Goods reciept processing
            INT_MAT-PRFRQ = MARC-PRFRQ.    "Recurring Insepction
            INT_MAT-SSQSS = MARC-SSQSS.    "QM Control key
            INT_MAT-QZGTP = MARC-QZGTP.    "Certificate Type
            INT_MAT-QSSYS = MARC-QSSYS.    "Required QM system for
            APPEND INT_MAT.
            CLEAR INT_MAT.
ENDSELECT.
ENDFORM.
FORM DOWNLOAD_FILE.
call function 'WS_DOWNLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Download Successfully to your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPLOAD_FILE.
call function 'WS_UPLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Upload Successfully from your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPDATE_MM.
LOOP AT INT_MAT.
CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'
EXPORTING
    INPUT              = INT_MAT-MATNR
IMPORTING
   OUTPUT             = INT_MAT-MATNR
EXCEPTIONS
LENGTH_ERROR       = 1
OTHERS             = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Header
    BAPI_HEAD-MATERIAL        = INT_MAT-MATNR.
    BAPI_HEAD-IND_SECTOR      = INT_MAT-MBRSH.
    BAPI_HEAD-MATL_TYPE       = INT_MAT-MTART.
    BAPI_HEAD-BASIC_VIEW      = 'X'.
    BAPI_HEAD-PURCHASE_VIEW   = 'X'.
    BAPI_HEAD-ACCOUNT_VIEW    = 'X'.
Material Description
    REFRESH INT_MAKT.
    INT_MAKT-LANGU           = INT_MAT-SPRAS.
    INT_MAKT-MATL_DESC       = INT_MAT-MAKTX.
    APPEND INT_MAKT.
Client Data - Basic
    BAPI_MARA1-MATL_GROUP     = INT_MAT-MATKL.
    BAPI_MARA1-BASE_UOM       = INT_MAT-MEINS.
    BAPI_MARA1-UNIT_OF_WT     = INT_MAT-GEWEI.
    BAPI_MARA1-DIVISION       = INT_MAT-SPART.
    BAPI_MARAX-MATL_GROUP = 'X'.
    BAPI_MARAX-BASE_UOM   = 'X'.
    BAPI_MARAX-UNIT_OF_WT = 'X'.
    BAPI_MARAX-DIVISION   = 'X'.
Plant - Purchasing
    BAPI_MARC1-PLANT      = INT_MAT-WERKS.
    BAPI_MARC1-PUR_GROUP = INT_MAT-EKGRP.
    BAPI_MARC1-PUR_STATUS = INT_MAT-MMSTA.
    BAPI_MARC1-ISSUE_UNIT = INT_MAT-AUSME.
    BAPI_MARC1-QM_AUTHGRP = INT_MAT-QMATA.
    BAPI_MARC1-GR_PR_TIME = INT_MAT-WEBAZ.
    BAPI_MARC1-INSP_INT   = INT_MAT-PRFRQ.
    BAPI_MARC1-CTRL_KEY   = INT_MAT-SSQSS.
    BAPI_MARC1-CERT_TYPE = INT_MAT-QZGTP.
    BAPI_MARC1-QM_RGMTS   = INT_MAT-QSSYS.
    BAPI_MARCX-PLANT      = INT_MAT-WERKS.
    BAPI_MARCX-PUR_GROUP = 'X'.
    BAPI_MARCX-PUR_STATUS = 'X'.
    BAPI_MARCX-ISSUE_UNIT = 'X'.
    BAPI_MARCX-QM_AUTHGRP = 'X'.
    BAPI_MARCX-GR_PR_TIME = 'X'.
    BAPI_MARCX-INSP_INT   = 'X'.
    BAPI_MARCX-CTRL_KEY   = 'X'.
    BAPI_MARCX-CERT_TYPE = 'X'.
    BAPI_MARCX-QM_RGMTS   = 'X'.
Accounting 1
    BAPI_MBEW1-VAL_AREA      = INT_MAT-WERKS.
    BAPI_MBEW1-PRICE_CTRL    = INT_MAT-VPRSV.
    BAPI_MBEW1-STD_PRICE     = INT_MAT-STPRS.
    BAPI_MBEW1-PRICE_UNIT    = INT_MAT-PEINH.
    BAPI_MBEW1-MOVING_PR     = INT_MAT-VERPR.
    BAPI_MBEW1-VAL_CLASS     = INT_MAT-BKLAS.
    BAPI_MBEW1-VAL_CAT       = INT_MAT-BWTTY.
    BAPI_MBEW1-ML_SETTLE     = INT_MAT-MLAST.
    BAPI_MBEW1-ML_ACTIVE     = INT_MAT-MLMAA.
    BAPI_MBEW1-VM_SO_STK     = INT_MAT-EKLAS.
    BAPI_MBEW1-VM_P_STOCK    = INT_MAT-QKLAS.
    BAPI_MBEW1-FUTURE_PR     = INT_MAT-ZKPRS.
    BAPI_MBEW1-VALID_FROM    = INT_MAT-ZKDAT.
*ACCOUNTING 2
   BAPI_MBEW1-TAXPRICE_1    = INT_MAT-BWPRS.
   BAPI_MBEW1-TAXPRICE_2    = INT_MAT-BWPS1.
   BAPI_MBEW1-TAXPRICE_3    = INT_MAT-VJBWS.
   BAPI_MBEW1-DEVAL_IND     = INT_MAT-ABWKZ.
   BAPI_MBEW1-COMMPRICE1    = INT_MAT-BWPRH.
   BAPI_MBEW1-COMMPRICE2    = INT_MAT-BWPH1.
   BAPI_MBEW1-COMMPRICE3    = INT_MAT-VJBWH.
   BAPI_MBEW1-LIFO_FIFO     = INT_MAT-XLIFO.
   BAPI_MBEW1-POOLNUMBER    = INT_MAT-MYPOL.
    BAPI_MBEWX-VAL_AREA   = INT_MAT-WERKS.
    BAPI_MBEWX-PRICE_CTRL = 'X'.
    BAPI_MBEWX-STD_PRICE = 'X'.
    BAPI_MBEWX-PRICE_UNIT = 'X'.
    BAPI_MBEWX-MOVING_PR = 'X'.
    BAPI_MBEWX-VAL_CLASS = 'X'.
    BAPI_MBEWX-VAL_CAT       = 'x'.
    BAPI_MBEWX-ML_SETTLE     = 'X'.
    BAPI_MBEWX-ML_ACTIVE     = 'X'.
    BAPI_MBEWX-VM_SO_STK     = 'X'.
    BAPI_MBEWX-VM_P_STOCK    = 'X'.
    BAPI_MBEWX-FUTURE_PR     = 'X'.
    BAPI_MBEWX-VALID_FROM    = 'X'.
   BAPI_MBEWX-TAXPRICE_1    = 'X'.
   BAPI_MBEWX-TAXPRICE_2    = 'X'.
   BAPI_MBEWX-TAXPRICE_3    = 'X'.
   BAPI_MBEWX-DEVAL_IND     = 'X'.
   BAPI_MBEWX-COMMPRICE1    = 'X'.
   BAPI_MBEWX-COMMPRICE2    = 'X'.
   BAPI_MBEWX-COMMPRICE3    = 'X'.
   BAPI_MBEWX-LIFO_FIFO     = 'X'.
   BAPI_MBEWX-POOLNUMBER    = 'X'.
*Storage Locations
    BAPI_MARD1-PLANT      = INT_MAT-WERKS.
    BAPI_MARD1-STGE_LOC   = INT_MAT-LGORT.
    BAPI_MARDX-PLANT      = INT_MAT-WERKS.
    BAPI_MARDX-STGE_LOC   = INT_MAT-LGORT.
   WRITE:/ BAPI_HEAD-MATERIAL, BAPI_MARC1-PLANT ,BAPI_MARD1-STGE_LOC.
    call function 'BAPI_MATERIAL_SAVEDATA'
      exporting
        HEADDATA                   = BAPI_HEAD
        CLIENTDATA                 = BAPI_MARA1
        CLIENTDATAX                = BAPI_MARAX
        PLANTDATA                  = BAPI_MARC1
        PLANTDATAX                 = BAPI_MARCX
      FORECASTPARAMETERS         =
      FORECASTPARAMETERSX        =
      PLANNINGDATA               =
      PLANNINGDATAX              =
<b>      STORAGELOCATIONDATA        = BAPI_MARD1
       STORAGELOCATIONDATAX       = BAPI_MARDX</b>
        VALUATIONDATA              = BAPI_MBEW1
        VALUATIONDATAX             = BAPI_MBEWX
      WAREHOUSENUMBERDATA        =
      WAREHOUSENUMBERDATAX       =
      SALESDATA                  = BAPI_MVKE1
      SALESDATAX                 = BAPI_MVKEX
      STORAGETYPEDATA            =
      STORAGETYPEDATAX           =
      IMPORTING
        RETURN                     = BAPI_RETURN
      TABLES
        MATERIALDESCRIPTION        = INT_MAKT
      UNITSOFMEASURE             =
      UNITSOFMEASUREX            =
      INTERNATIONALARTNOS        =
      MATERIALLONGTEXT           =
      TAXCLASSIFICATIONS         =
      RETURNMESSAGES             =
      PRTDATA                    =
      PRTDATAX                   =
      EXTENSIONIN                =
      EXTENSIONINX               =
IF BAPI_RETURN-TYPE = 'E'.
   WRITE:/ 'Error Message ', BAPI_RETURN-MESSAGE.
ENDIF.
ENDLOOP.
ENDFORM.
<b>i am using this bapi method to copy materials from one plant to another plant using storage location so here what happenig is everyting is going correct but only the storage location data is not saving in table mard so any body faced this kind of problem please tell me.... and one more dbt
bapi_marcx-pur_status = 'x' what is 'X' here??? is that mandatory field or required field ???
points wil be rewarded.
reagrds,
sunil k airam.

In the HEADDATA structure, STORAGE_VIEW should also be set as 'X' , in order to update storage location data
for example
BAPI_HEAD-STORAGE_VIEW = 'X'.
Also, PUR_STATUS corresponds to field MARA-MSTAE whose domain has value table T141, therefore values in the field are checked against T141
Edited by: Harris Veziris on May 12, 2008 12:37 PM

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 TOs 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 TOs 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!

Serial Numbers in WM Storage Units

Hi all:
My client needs to manage serial numbers in WM. I am planning to propose to use the storage unit as storage for serial numbers. This WM will not have HUM, no batch management. Plant will use valution type.
Can anyone tell me what are the pros and cons for storing serial numbers in Storage Units in a non HUM WM?
We are implanting WM in SAP ECC 6.0
Thanks in advance for any help.

Hi Juan
Are you talking about managing serial numbers with storage unit management? When we use serial number management every material within the storage unit number will have a serial number. For ex:- if a storage unit number has 10 pcs in it then system would generate 10 serial numbers. You will need a BADI 'LE_WM_INV_WM_IM' and add data serial number in the class to control serial number function in WM. Check OSS 559531 for more info.
Thanks
Anandha

Storage Unit & Storage Bin

Dear All,
How to make that one storage bin can have serveral storage unit?
Such as we want one storage bin can contain three pallets.
regards
Gang

Hi,
There is no restriction on using any no. of storage unit types for a storage bin. Storage unit types are defined at warehouse level. The path is Logistics Execution -> Warehouse Management -> Master Data -> Material -> Define Storage unit types.
You can define any no. of SUT for a warehouse. Now these SUTs are assigned to materials in material master WM view 2. And materials are linked to bins. SO, whatever materails you have for a bin the SUTs for those materials are all valid for that bin...
Hope this is of some help for you..
Regards,
Noopur

WM Storage Unit Type Capacity

Hi,
I have the following situation:
In our warehouse, materials are received in kilograms and stored and transferred in barrels or containers.
For this reason we are using storage unit types "barrel" and "container".
For the barrels, we have a defined bin structure. Containers are stored in one large area with no restrictions to the number of containers.
For barrel storage we use placement strategy P (palletization). This because a maximum of 4 barrels can be placed in a bin. We created 4 bin sections per bin to hold the maximum of 4 storage units.
My question is this:
To check if a storage unit can be placed in a bin works fine. A maximum of 4 barrels is allowed in a barrel bin.
However, when converting a TR to a TO i want to check the entered quantity PER storage unit type.
For a barrel, a maximum of 250 kilograms is allowed. For containers, a maximum of 1500 kilograms is allowed. Material can be stored in barrels, as well as in containers.
How do i let the system check the allowed maximum quantity per storage unit type?
Thanks in advance,
Paul

Hi Paul
I can see why it is failing now.
For a storage type with Palletization strategy, it considers the capacity per bin and not per section. Therefore it will allow you to putaway 750KG in a single section of the bin (250 used by SUT totaling 1000 for the bin).
Your requirement is capacity check per SUT with a set maximum material quantity.
A different way of handling this is using capacity check method 2 for the storage type.
Then update your material master data (WM2 view) with Palletization data.
250 KG <Barrel SUT>
No update to storage bin masters is required.
A drawback of this strategy is you can work only with the one SUT for a material. System will not take in to consideration any data given in line 2 or 3 in Palletization Data. In other words you cannot restrict the max quantity for Containers for the same material.
Perhaps depending on the storage type characteristics of your container store, we may make some work around.
Let me know if you wish to discuss more.
Regards
Baseer

How much storage units can be added in the single bin.

Hi all,
Can anybody tell me how much storage units can be added in the single bin.
Dev

Hi Dev,
AS Prashant & Abhijit mentioned above the maximum storage units in a single bin is based on various factors such the putaway strategy & capacity check you have set for your storage type as well as palletization data.
Now in case of Bulk Storage which you have mentioned above, please go through the below F1 help for the block structure.
In bulk storage, you need to define for each block (or row) how many
storage units fit into the block. For this purpose, you must define
both the number of columns as well as the maximum stack height. *The*
product of these factors usually gives the maximum number of storage
+units and is determined automatically by the system. However, it is+
possible to change the maximum number of storage units to a lower number
if the storage bin or the material features require this.
Hope it helps.
Thanks & Regards,

Storage unit type not found automatically on LT01

Hi,
We have just only one kind of storage unit type in the settings. I want it to be determined automatically on TO creation(LT01) , so that the user is not required to enter it everytime he creates a TO
I couldnt find a way to do it via custimizing. Appreciate any tips about it.
Thanks
Cihan Polat

Hi,
I dont have a problem with storage type determination.
Acctually what is missing on LT01 is storage type indicator LTAP-LETYP (EXP for my example).
This is the field on the second screen of LT01 (SAPML03T- 102).
It is located under quantity, which is just second line on the screen.
Requested qty    1                 PC   5SQ2 370-0KA06 /N-OTM.C6 3pol
Stor. unit type      EXP                   Material        5SQ23700KA06
Certificate no.                         Plant/Stor.loc. 1000   1550
Confirm
Printer                                 Stock category
GR date          12.04.2010             Special stock
                                        TO item         0
Tpe Sec Stor.bin    Target quantity   AUn
Src                                         0 PC
Dest                                        0 PC
Ret.                                        0 PC
Goods recipient                         Weight                   0,000

How many storage unit type per Material code

Dear ERP Expert
we are running SAP ECC 6.0 with decentralized Warehouse Management System (WHP).
In material master data of WHP, view Warehouse Mgmt 2, there is the "Palletization data" box, with the following column:
Loading equipment quantity 1
Unit of measure for loading equipment quantity 1
1st storage unit type
In this way it is possible to define, per material code, 3 different pallet type, isnt'it?
I would like to know: To define different pallet types what kind of the impact could have?
I mean, someone tell us that the main impact to define different pallet types, in WH material master data is:
1 - When receiving the goods the TOu2019s will have to be created manually. The system cannot define the used pallet by itself and this is very important for the placement.
2 - The issuing of the goods is not possible via RF (radio frequency). This will have to be done manually as this is not supported.
is this scenario relalistic or is it possible to do something in order to avoid this scenario?
regards
marco

1)Storage unit type is assigned to the eacj warehouse number.
2)It is activated for each storage type in the warehouse.
3)Goto SPRO->LE->Warehouse mangmt->Mater Data->Material->Define storage unit type.
4)Here you assign storage unit type to warehouse number
5)You can activate SU mngmt at warehouse level here:
SPRO->LE->Warehouse mangmt->Storage Unit->Master Data->Activate SU mngmt per warehouse number
6)You can also activate SU mngmt at storage type level
SPRO->LE->Warehouse mangmt->Master Data->Define storage type.
Reward if helpful

L_TO_CREATE_SINGLE - new storage unit is not created by SAP

Hello Friends,
I am using a FM L_TO_CREATE_SINGLE to create transfer order.
But, When I am not passing Destination SU as import parameter, it gives me following error.
"Storage unit XXXXXXX is not consistent with other transfer order data"
This is happening in ECC 6.0. Earlier i was using ECC 5.0 and there was no problem.
How can I get rid out of this problem?
Regards,
RH

Hi,
Check the long text of the message.
It clearly says that
"Data in the transfer order item (such as the quant number, storage bin or storage type) does not belong to the storage unit number that you entered."
So check to see if the storage unit number you entered is correct.
This seems to be a data issue.
Regards,
Ankur Parab

Storage Unit Date

Similar Messages

Maybe you are looking for