Validation on storage location

Dera Experts ,
I have the following queries:
1. Is it possible to have a particular user to have authorizations for a few selected storage locations? That is , the user should be able 2 carry out the transaction for only a few stores & the rest , he should not . If yes how .
2. Is it possible to ahve the validation of the storage loaction for a material > Eg if a material is being wrongly posted thye wrong store , is it possible to validate it ? If yes How ?
Regards
Anis

You wil first have to activate "Authorization checks for storage location" , goto SPRO->MAterials mgmt->Inventory Management and physical inventory->Authorization Management->Authorisation checks for storage location , here you need to select the storage locations for which you want to enable the authorization checks.
Then you will have to ask yor Basis person to assign relevant storage locations to the user roles.
Regards
Raviraj

Similar Messages

Validation for storage location

Greetings to Experts!!
I am looking for following two validations;
1- stock outward movement from a particular storage location (say ABC ) could only be possible via 351.
2- 351 movement type could only be used for storage location ABC
Plz Help,
Regards,
M. Tayyab Aslam

For the first one, IN OMJJ, for the movement type , tick The storage location automatic option. If the stor loc in maintained in the material master, then that will be picked automatically..
For the second , I don find any possiblilty
karthick

Storage location validation in ME21n

Dear Experts,
While creating a PO in ME21N, there is no validation for a storage location for checking whether the material record created for storage location or not.
How to set a warning or error messgae in such cases?
Please post your valuable inputs
regards,
Shetty

>
shetty123s wrote:
> Dear Experts,
>
> While creating a PO in ME21N, there is no validation for a storage location for checking whether the material record created for storage location or not.
>
> How to set a warning or error messgae in such cases?
>
> Please post your valuable inputs
>
> regards,
> Shetty
Check for BAdI ME_PURCHDOC_POSTED...here you can write a code with help of your ABAP person that the system will first check the material code (MATNR) & storage location (LGORT) from each PO line item...then with the same combination will check if there is any entry in table MARD...if no entry found then system will throw a customized error...
Regards,
Indranil

Material deletion flag at storage location level is not working

I have a material that is created in some plants and also in some storage locations within each plant. If I mark the deletion flag at plant level I am not able to create a PO -> Me051 error message appears. Whereas if I mark the deletion flag at storage location level nothing appens. I am able to create a PO and also to create to goods receipt. Is there any customization that I should do in order to get the error message?
Thanks in advance.

storage location level deletion flag is not checked at order creation.
it is assumed that you can change the storage location when you do the receipt.
MRP run is at plant level, so the requirement is valid even the storage location view is flagged for deletion.

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

Default SC Plant Company code and Storage location Based on Position

Hi All,
We are on version SRM 7.02.
We are using SAP ECC R/3 EHP7 based system as a back end FI and HR system.
Org structure in SRM is replicated fromm HR system.
We have case of concurrent employment in the HR org structure , which means one USER can be assigned to multiple Positions in an org structure.
We have a user A , who is created in Two different org units say O1 , O2 occupying positions P1 and P2, belonging to company code C1 and C2.
Whenever a SC is created a custom enhancement shows all the user positions to him and he has to choose one from the list of positions.
Now based on the selected position(P1) , i have to default plant(PL1), storage location(SL1) and Company code(C1).
Even after defaulting attributes based on the position, user gets an error "company code C1 is not valid for user"
This error (Message class : /SAPSRM/CLL ; # 135) is thrown from method : /SAPSRM/CL_CH_WD_DODM_SC_I_BD /SAPSRM/IF_CLL_MAPPER~UPDATE
after getting user's Company code using following method.
/sapsrm/cl_pdo_shared_user=>/sapsrm/if_pdo_shared_user~get_company_code
This gets Company code as C2 ; Based on Users Attributes and not based on User Position attributes.
If i overwrite values fetched by this method in Implicit enhancement, then plant(PL1), storage location(SL1) are not getting fetched.
Does anyone have any solution for this problem?
Regards,
Ashish Shah

Hi MURUGESAN !
      Can you give me some information more in Special Procument Configure in plant 2000 like:
          - Procurement type (maybe F)
          - Special procurement (Maybe U)
          - Plant (Maybe 1000).
          - Issuing plant (maybe 2000)
       We will check together.
       Regards,
      Tony

Storage location list during Confirmation

Hi! I discovered during confirmation of the goods in SRM (SRM 4, extended classic) that when I choose to list the storage location for selection, although only the relevant storage locations are listed, there are gaps in between the storage locations. I suspect that it is taking the sequence of the order in the user attributes.
For example, if I maintain the attributes in the following fashion:
Plant   SLoc
0001   0010
0001   0020
0002   0010
0002   0020
0002   0030
On saving the attributes, it will be sorted and shown like this:
Plant   SLoc
0001   0010
0002   0010
0001   0020
0002   0020
0002   0030
If my order is for plant 0002, on listing the SLoc for the item during confirmation, I get the sloc listed like this
<blank>
0010
<blank>
0020
0030
What I would like to achieve is for the system to show the storage location valid for the plant and as per maintained in the attributes
0010
0020
0030
Does anyone have similar problem as described? What should be the standard behavior?
Cheers!
SF

Hi! I found this note 632616 but it is about listed the details of the plants and logical system so that the user knows which storage location to pick. It did not specially talk about the blanks/gaps.

MRP storage location

to check for all materials in a given plant if 'Storage location MRP' details is maintained or not in MRP-4 view of material master.

Hi Rajesh
Whatever soln. i suggested is still valid for ur prob. now to extend it little bit follow below said.
If u follow above said steps from previous post..u will get MRP indi. Tab...double click in open space against that tab....U will get list of selection options...select not equal to 1..and execute report ..
It will give u List of Items for which Storage Location MRP is not maintained
Hope this will silve ur prob
Vishal...

WM Storage Location control problem - no TR created in receiving warehouse

Hi all,
I have configured the system to perform a 311 mvt from sloc 4002 to sloc 0010. Both Slocs have different warehouse numbers assigned.
The transfer is working fine, however in the receiving warehouse no TR is being generated even though I am using the standard *** 311 movement type which has create TR flag set.
If I disable the config and perform the 311 in MIGO after confirming the TR in the sending warehouse, the stock is moved to the new warehouse and a TR is created.
Has anyone experienced this before?
Mark

2nd entry in storage location control is ZF2 501 DE01 0010 311
1st case:The entry.e. ZF2 501 DE01 0010 311 seems to be wrong.
Your warehouse storage location 0010 is managed with ZF4 and not ZF2.
But in this case, the way you created entries concludes that you want to transfer the stock from one Sloc to other Sloc which have separate warehouses.
i feel your approach to excute this scenario seems to be not a valid one. I don't understand why you are running this process as WM transaction followed by IM document. You said that you are creating the transfer order first.. must be with wm mvt 311 in LT01. Standard WM mvt 311 doesn't allows manual TO creation.Your both storage locations are assigned to different warehouses. You should post the movement in IM first, then follow the WM activities.
2nd case:If you say that ZF2 is correct, then your storage location is wrong, it should be 4002 instead of 0010 and you are transferring stock from one storage type to other storage within same warehouse.
If you want to do this scenarion as WM followed by IM, then please change the Wm mvt 311 in ZF2 to allow manual TO creation.
In movement type properties, set the destination storage type as 501.
Strorage location control should be ZF2 501 DE01 4002 311
Please let me know your thoughts on this.
Regards,
Santosh

Material block for sale in plant-storage location level

Dear experts,
Please help me how to block a material to sale in plant-storage location level.
Thank you.
Regards,
Badruddoza

The standard sales block (MVKE-VMSTA) in material master is valid for sales organisation / distribution channel combination (VKORG, VTWEG) - this means you cannot do it for Plant / SLoc combination,
What does it mean to block it at plant / sloc level? Generally in SO you do not specify the storage location. Or you are speaking about MRP also? In this case you could use SLoc-MRP (with proper availability check in delivery) for your material but the problem is that a plant might be assigned to several sales area and this SLoc would be hidden for them also.
Could you please specify what would you like to achieve, what sales block means according to you?
Regards,
Csaba

MRP4 view exclude storage location & material provided by vendor/customer..

Hi
Could anyone please tell me in MRP4 view for a material,where is the option so that i can exclude or include the storage location stock from MRP?
and also in which T code i should indicate the material is provided by vendor/material provided by customer?In CS01wher's this option?
Please help me
Thanks & regards
Raj

Hi Karthik,
MRP area is nothing to do with storage locations settings in MRP4 view. If you want to activate MRP area and use the MRP run at MRP area level then you have to customized MRP area either at storage location level or sub-contractor level (in MRP master data settings )... then you need to assign this MRP1 view of the material and with valid MRP type. Now when you run the MRP then planning will be carried out at this MRP area for this part.
With storage location indicators in MRP4 view (must enter with putting the stoarge location values from MM02/MM03) you can exclude the stock of this storage location (indicator 1) in the palnning run or you can plan seperately with indicator2 with using re-order level. Here no need of MRP area.
If helps rewards points.
Regards
TAJUDDIN

Storage location-determination of return-deliveries (delivery type RL)

Is there a difference between picking storage location-determination of return-deliveries (delivery type u201CRL Returns (pur.ord.)u201D/return to vendor) on 4.6C compared to ECC6.0? Is there a SAP-note?
Within 4.6C-system the storage location is determined based on the customizing settings (Logistics Execution \ Shipping \ Picking \ Determine Picking Location \Assign Picking Locations).
Within ECC6.0-system the storage location in the return-delivery is always the storage location that is entered in the Return-Purchase Order. It seems like the customizing-settings are no longer beeing taken into account.

This storace location-determination of return-deliveries (delivery type RL) in customozing that you mention is only true within the 4.6C-system. Within the ECC6.0-system the storage lcoation is always the one that is entered in the return-purchase order. In ECC6.0 the customizing settings you are refering to a no longer valid for deliveries with delivery type RL.
The questions is why/ and is there an OSS note.

Storage location to be excluded from MRP Run

Dear Gurus ,
We are trying to exclude perticular Storage location from MRP Run with the Configuration setting
IMG >>> Production >>>.MRP >>>.Planning >>>>.Define Storage Location MRP per plant >>>> Indicator 1 is set
Still the Stock is being considered
As I know this can be done thr' MRP4 view , but we don't want to go Part No wise ,
Suggest better sloution
Thanx in advance

Vasu,
Above IMG path is only used for defulting the storage location exclusion in material master.
Whenever materials are extended to this storage nlocation in mm01 or mmsc, this defult value would be proposed automatically .
However this does not mean setting it in IMG would change existing materia storage location extensions automatically. Also MRP will not pick from above IMG settings.
Once again above setting is only valid from defulting the values while extending the Materials to storage locations.
Hope it helps.

Updation of Replenishment storage location in MF60 ( reservation creation )

Hello,
In REM, we are using MF60 for two step material staging.
We have gone for two stage staging process.
First shop person will create reservation and then the store person will issue the material against the reservation.
Here when the resrvation is getting created , user
do not want to give the replenishment storage location on the sap screen.
User considers this as a pain.
Is there any way to bring the replenishment storage location
automatically updated in the reservation?
Please let me know in both scenarios,
scenario one --- by using inventory management
scenario two --- by using warehouse management.
Waiting for reply from Experts.
Regrads,
Ravindra Deokule

Hello Mahesh,
Thanks for your reply.
Your suggestion was valid if we were working with single step stock transfer process.
But as stated in the question , we are working with two stage process.
Here the stock determination button itself is not appearing on the SAP screen in MF60.
So I think your answer is not right Or may be let me know how
to bring the stock determination button on the SAP screen when you are creating the reservation.
Waiting for your reply.
Regards
Ravindra Deokule

Turn off ATP for a Storage Location

Hi,
I want to turn off ATP for a Storage Location.
I am aware of a setting on IMG where we can have this done but not able to find the right node.
Can someone help me with it?
availability check NOT TO CHECK the stock at the storage location level
Thanks,
Mike

Availability checks can be triggered either automatically or manually:
The availability of components in an order can be checked automatically during order creation and/or order release. You specify in CustomizingOPJK per order type and plant whether the availability should be checked automatically. In addition, an automatic availability check can be carried out when the order is saved.
You can always trigger a manual availability check
The checking scope is defined via the Checking Group (in the material master) and the valid Checking Rule (in Customizing).
They define:
Which MRP elements are taken into account in the check
Which inventory categories are taken into account
Whether the replenishment lead time is taken into account
Whether the check is also to be carried out at storage location level
In Customizing (checking control) you specify which quantity is used to check the availability of a material. You can choose between the following:
Availability Check Against Planned Independent Requirements
In the check against planned independent requirements, the system only checks the open planned independent requirement quantities created for the components. This means that the ATP quantity is not included in this availability check nor are receipts or stocks.
This type of availability check is most useful:
if assembly planning or phantom assembly planning is used to plan the components
if quick statements about the availability situation are required and the results from this check are precise enough
The system uses the open planned independent requirements quantity at component level to determine a committed quantity and this quantity is copied to the planned order header in the Committed quantity field. As opposed to the availability check according to ATP logic, however, the committed quantity is not recorded in the dependent requirements. The planned independent requirements of the components are not consumed by the committed quantity but by the complete dependent requirements quantity. In availability checks that follow, the system can only commit quantities for the amount of planned independent requirements that have not yet been consumed.
In the availability check against planned independent requirements, the following dates/quantities are not calculated:
overall commitment date
partial commitment date/quantity
ATP quantity
In the check according to ATP logic, the system checks whether the dependent requirements of each component are covered by specific receipt and issue elements or by stock. This check is carried out dynamically, that is, each time you carry out the check, the system recalculates the current situation. If a quantity can be committed for the requirement date, the system enters precisely this quantity as the committed quantity in the dependent requirements and the ATP quantity for the components is reduced by the committed quantity. Therefore, in the next availability check, dependent requirements can only be committed for the amount of the remaining ATP quantity.

Validation on storage location

Similar Messages

Maybe you are looking for