Storage Location Authorization

Hello,
I want to authorize user A to make material movements in     Plant 1001  Storage 1000, 1001, 1002...9000
                                                                                Plant 1002   Storage 9000
                                                                                Plant 1003   Storage 9000  etc.
So,  first I followed path SPRO - MM - Inventory Management and Physical Inventory - Authorization Management - Authorization check for storage management   and enabled storage authorization.
Then In PFCG under Goods Movement: Storage Location I selected related storage locations and plants as above but it still allowed user A to make movements to storage 1001, 1002 of plant 1002 and 1003.
In our system every plant has storage locations called 1000,1001,1002...9000. Does the system recognize the storage locations selected in PFCG according to the plants selected. To be more precise, ıf I select, 1001, 1002 and 1003 for plants, and
(plant-storage loc) (1001-1000, 1001-1001, 1001-1002, 1002-9000) does the system recognize it as if I want to be authorized for 1002-1000, 1002-1001,1002-1002  ?

Hi
You can do it additive, for instance.
Only can create movement 101 and 102, others only view them:
ACTVT = 01,02
BWART = 101, 102
LGORT =  *
WERKS = *
and add newly the object M_MSEG_LGO with other parameters.
ACTVT = 03
BWART = *
LGORT = *
WERKS = *
Of course, you have other auth.objects (eg: M_MSEG_BWF, M_MSEG_WMB,...). If other object avoid that the user can do it, run tcode SU53, it will tell you what object avoid that user can do it.
I hope this helps you
Regards
Eduardo

Similar Messages

  • Storage Location Authorizations

    Dear Gurus
    We have recently implemented SAP in our Organization and have activated Storage Locations' authorizations. Our requirement is to limit the authorization to issue and receive material from individual storage locations but at the same time the users should be allowed to dispatch material for other storage locations (through 2 step transfer posting by posting "Remove from Storage" transactions). The problem is that at present the users are not able to select Destination Storage locations (in 2 step transfer posting - remove from storage) which are not authorized to them. On the contrary authorizing them for those Storage locations will authorize them to issue / receive material in other's storage locations.
    I will appreciate if any of you may guide how to resolve this problem.
    Regards
    Muhammad Asif Nakhuda
    Edited by: Asif Nakhuda on Jul 31, 2010 10:34 PM

    Hello Ahsan,
    Addition in SU22 in not for introducing authorization checks. It is misconception. All it does is the following:
    For example you add auth object X for as transaction Y in Su22/SU24 . Now if you add transaction Y to a role in PFCG then authorization object X will be added by default in the role. For standard transactions SAP has maintained Su22/SU24 customizing on basis of ABAP code so that whenever you add a transaction to a role its correspnding authorization checks are added automatically to a role and you dont to take pains of finding them out. In case of custom built transactions also you can follow the approach used by SAP. SU22/SU24 is for easing role adminsitration ands not introducing authority checks !!
    Regards.
    Ruchit.

  • Storage Location Authorization Object

    Dear all,
    I am trying to restrict a user on some particular Storage Locations , but when we apply the restriction , the user can still access all other St Loc.. Could u pls help..
    Wants to do the same for Movement Type as well..
    Thanks in advance..

    Hi,
    Go to SPRO > MM > Inventory Management and Physical Inventory > Authorization Management > Authorization Check for Storage Locations > Here activate the authorization for storage location under plant
    And use authorization object as "M_MSEG_LGO"
    Note: - In this step, you activate storage location authorization for individual storage locations.
    Storage location authorization means that a user has to have authorization for authorization object M_MSEG_LGO in order to enter a goods movement in the storage location, using a particular movement type. In the list of material documents, only the document items for which the user has a display authorization are displayed.

  • Material Type Movement type and Storage location Authorization Object

    Dear All,
    My client wants that  certain type of material i.e. SFG should not be GR Mvt. type 101 at the FG storage location, they want to restrict to some  user ID .
    Is there any authorization object or the enhancement to control all three parameter to restrict to particular USER ID?
    Thanks in advance.
    regards
    ALOK Shrivastava

    Hi,
            Please check as follows.
            IMG > Material Management > Inv. management and Physical Inventory  > Authorization Management
                   > Authorization Check for Storage Locations (Indicator on)
    Regards,
        Gaito

  • Storage Location check during 101

    Hi folks,
    I am facing a problem and need ur help...
    Though this is a security related issues but it requires Functional help...
    A user who does not have authorization for Storage Location ABC (M_MSEG_LGO) is executing MIGO and is being able to do GR(101) against STPO for ABC...
    The system trace shows that only 2 objects are getting checked viz M_MSEG_BWE (Goods Receipt for Purchase Order: Movement Type) and M_MSEG_WWE (Goods Receipt for Purchase Order: Plant). There is no check for Storage Location in Purchase Order...
    The S Loc is defined in the PO and during MIGO it is getting picked from there..
    How can i restrict this guy from posting 101 for ABC??...
    Pls help before i am thrown out...
    PS: The Storage Location authorization (M_MSEG_LGO) is available to the user BUT for a different location. Also the storage location ABC is authorization relevant in SPRO...
    thankx in advance
    Sachin

    hi sachin,
    pls check the user roles defined. From what you have written, it seems that the object M_MSEG_LGO is getting bypassed for some reason. Pls check all the other roles that this particular user is assigned to. And pls don't worry. There's no way you are going to be thrown out with so many experts around to help you out with a solution. I'm sure everyone will echo my view. Be patient and check out the roles. Revert back.
    - Rahul

  • User Authorisation - storage location

    Hi,
    we have three storeage location under one plant, can we restrict user to access only on UM1 storage location not to access balance two storage location.
    Plant :    X70
    Storage Location  :  UM1
                                    UN1
                                    UN2
    Is it possibile to create a role only on storage location, please advice.
    Regards,
    Muthu

    You will need to activate " Authorization Check for Storage Locations "
    Storage location authorization means that a user has to have authorization for authorization object M_MSEG_LGO in order to enter a goods movement in the storage location, using a particular movement type. In the list of material documents, only the document items for which the user has a display authorization are displayed
    Go to  SPRO->Materials management ->Inventory management ->Authorisation management->Authorisation check for storage locations,

  • Movement type authorisation for different storage locations

    Hi sdners
    can we make the movement type restricted to any storage location
    Ex: i have 2 storage locations 1110 and 1114 in plant 1100
    and i have two end user mst1 mst2
    if so i want to make sure that mst1 is responsible only for issue goods from 111o
    and he should not able to issue goods from 1114 vice versa to mst2
    is there any possible configuration please let me know.
    With regards
    S.K.chaitanya

    Hi
    u can achive this through authorization
    First
    You need to activate the storage location authorization check for goods movements in config
    SPRO->Materials Management->Inventory Management and Physical Inventory->Authorization Management->Authoization check for storage locations.
    Then required  control is achieved via authorization object M_MSEG_LGO.
    Get in touch with Basis and ask him to remove required storage location from user ID so that that user will not able to pass any movement to that storage location
    Vishal...

  • Authorization Control for Transfer Posting's Storage Location

    Dear Gurus,
    Hi ! May I know is that SAP has any Authorization Object to control Transfer Posting (SAP R3 4.0B) ?
    Let say in MB1B I only allow certain user to do transfer posting with P230 storage location, how should I control it ? With Authorization Profile?
    I had tried remove all storage location P230 authorization M_MSEG_LGO from those user who are not allow to use, but sad to say that most of the user who allow to use transaction MB1B also able to do good receipt or transfer posting with storage location P230.
    I had check those user's profile, actually in their authorization, there could not get P230 in their M_MSEG_LGO authorization  object.
    Thank you!
    Warm regards

    Hi,
    I did not tried OLMB before, but I couldn't get  the option you ask me to click.
    Please refer to the screen, is it the Basis Administration is what you mention lately?
    [http://www.pikipimp.com/pp/pimped_photo/s/image/40/552/543/OLMB-compiled.JPG?ts=1232093107390]
    I had assign the storage location P230 to the authorize users, but the problem now was those unauthorized users also can use the storage location P230 to do Transfer Posting (MB1B) although I did not assign to them in PFCG.
    Thank you.
    Warm regards.

  • Purchase Requisition Authorization based on Storage Location

    Hi MM Gurus,
    Our client has got a specific requirement to control the security of purchase requsition creation, change and release based on the storage locations. We have found the authorization object M_BANF_LGO which is to restrict the access of PR based on storage location in purchase requsitions.
    The issue is the purchase requsition BAPI does not check this authorization object as per standard SAP.
    Does anyone know how to handle the security of purchase requsition based on storage location?
    FYI - Our PR release strategy is at item level and not at document level.
    Thanks,
    Shekhar

    Thank you for the reply. In case of purchase requsition for cost center, you can still enter the value of storage location. The storage location comes into picture when the goods receipts are posted against this purchase. However, the storage location value can be entered at PR level.
    We have storage location field as "Required" field in all purchase requsitions as there is only one plant and each storage location represents the division.

  • Authorization removal for storage location.

    we want to remove authorization for certain users for accessing specific storage location for transfer posting,let say 0002 is not supposed to access by user AABBCC.
      to control this my basis team member had removed this storage location in master role of this user where storage location is added(Inventory management/physical inventory) even though system is allowing for processing transactions in this 0002 storage location.
    plz suggest the way for restriction of this storage location access to user.

    Please share with us how you resolved this. That may help others in the future.

  • Authorization Check for Storage Location

    Hi Experts,
    I have the following requirement :-
    I have Plant : P081 created under Company Code : P110.
    I have got various Storage Locations under this Plant for example
    KT01 - Main Stores
    KT24 - Remote Store.
    The KT24 store is basically a remote location store. I have activated the Authorization for the Storage Location KT24 in the SPRO Settings
    Material Management --> Inventory Management and Physical Inventory --> Authorization Management --> Authorization check for storage location.
    I have maintain the following authorizations for the Object M_MSEG_LGO as follows :-
    1. OBJECT : M_MSEG_LGO.
    >> 2. USER ID : 081Store
    >> 3. PLANT : P081
    >> 4. STORAGE LOCATION : Kt24
    >> 5. ACTIVITY : 01-03
    >> 6. MOVEMENT : 101, 102, 201, 221, 261
    and authorization for T_code MIGO_GR and MIGO_GI . I want to restrict the user for transaction only for this storage location but the system is allowing the user to post GR document for KT01 stores also.
    Can any one suggest a solution or settings that need to be done for the user to be restricted to prepared GR for Storage Location KT24 only.
    Thanks in advance.
    AJ

    Hi,
    You set the authorizations to users with tcode PFCG. To know the reason of deny some access run tcode SU53 after SAP denies the access to some documents / objects.
    Regards,
    Eduardo

  • Restricting Authorization for movement types for Storage Location

    Hi Xperts
    I have a requirement that 313 & 315 material movements should not have any BBD/SLED check.However , 314 & 316 should have BBD/SLED check.
    Suppose there are two storage locations : A(Good Stock) & B(Blocked Stock).
    I want one User-ID should be authorized to perform 313 & 315 from A to B.However the same USER-ID should not be authorized to perform 313 & 315 from B to A.They should be authorized only to perform 314 & 316 from B to A.
    All the above trasnactions will be performed either via MIGO or via MB1B.
    How to achieve this.Pls suggest.
    Regards,
    Soumick

    Hi Soumick,
    You can try by creating 2 roles as given below.
    Role A - Tcode Migo
    BWART - 313 and 315
    for object M_MSEG_LGO field LGORT - give only A
    Role B - Tcode Migo
    BWART - 314 and 316
    for object M_MSEG_LGO field LGORT - give only B
    Try assigning both the roles to user and see... Not 100% sure...but u can try out.... You need to have such scenarios tested very thoroughly.
    With Regards
    Nishad Showkath

  • 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

  • Storage location missing in purchase order

    Hi all, I'm struggling to find why the storage location is not copied from purchase requisition to purchase order using ME21n.
    Further this happens only for one buyer, the same PR's if converted in PO by other buyers, move correctly storage locations to PO.
    Only for one buyer the storage location comes up blank and he has to populate manually the field.
    I've checked his SAP profile and it's perfectly the same of all other buyers. Also he hasn't any particular personal settings in his ME21n.
    Apparently there aren't reason why it should happen but it does.
    Also searching on the web I haven't found any documentation or any other SAPer with the same issue
    Can someone give me some suggestion?
    thanks
    Luca

    There are 3 reasons for this issue...
    1. Authorization
    You have said that, all authorizations are same for this buyer compare with other.
    2. Personal settings in me21n.
    You have also said that there are no issues with the personal settings..
    3. User parameter..
    Check user parameter from su01 tcode. Is it showing same as other users..
    Also check again the personal settings, is there tick the option "Always propose" for storage location in me21n..

  • How to restrict Stock posting in Specific Storage Location

    We Want to restrict posting of cenvet creadit taken material to specific storage loacation at time of GRN (MVT 105)

    HI
    IMaterial master view in mrp-2 view there is option to procurement for EP. here you specify the storage location so while posting the GR system pick the same sto location.
    which material you want to post just make the changes in mmr.
    creation of user wise authorization  also you can reach this with help of basis.
    laxman

Maybe you are looking for

  • I purchased a song, and it won't play. How do I fix it?

    How do I go about getting a song I payed for to actually play?????  I use the same computer or phone to make my purchases, and this has never happened, every other song I downloaded the same night dowloaded correctly, but this one I guess didn't. How

  • Organization View for Succesion Planning-My Org. Units!

    Hi, We are in process of implementing Nakisa (Release: 301_701) with EHP4 for few components including Succession Planning. We have completed Admin settings for Succession Planning. When we log in to End User section for succession planning & go to M

  • Data loading with 1:N & M:N relationship

    Hi, Which data (master or transaction) we can load with 1 : N relationship and M : N relationship. Can anyone give me the idea. Thx

  • Is there any Documentation frame work for OAF development

    hi Is there any Documentation frame work for OAF development like AIM Documentation for RICE components ? Hence , it is very clear that, MD50 and MD70 template is not for the OAF java development. Is there any need to document the oaf development, he

  • Blur face again...I know have read previous but can't do it...help

    ok am using fcp5.1 on g5 and am very new to fcp...used to use another program but this is different... placed the original file on v1 and a copy on v2. have hidden v1 so i don't get confused. just need to block out a small piece of video i dropped a