Reg : client level data,plant level data,storage location level data

hi
when we enter the data mm01 we select views.these views are based on cleint level,plant level,storage location level .i want the difference between all the three levels.how do we differentiate.

As per our business process there are one company and in which many plants and storage location are available. In which many materials are available in different plant in different storage location.
As per SAP Standard structure: -
Company >> Company code1 & Company code2... >> Plant 1 & Plant 2 & Plant 3 .... >> Storage location 1 & 2 & 3........
And in all plant and storage location have different data.
Suppose in one plant we do quality testing for material and it may be possible in other plant we not perform quality testing for material. So in this case for same material quality data is different for different plants.
Client Level: - Means data is same for all plant level like Basic data
Plant Level: - Means data is based on plant level like Purchasing, Plant data, Quality data, Accounting view.
Storage location level: - Means data is based on storage location level, for different storage location data will be different like Storage location stock data ..
Due to this you can maintain different data on plant level & storage location level.
Regards,
Mahesh Wagh

Similar Messages

Automatic selection of products in a plant but differant storage locations

Hi Gurus
Here is a requierment from our client that is they maintain differant storage locations based on differant prices however they want automatic selection of products during sales order entry, based on manufacturing date like FIFO comparing differant storage locations with in a plant. if you have come across these scenario and other solutions relate to this
please share your experiance
with regards
Baalakrushnan.da

hello, friend.
yes, we have come across this. first, your material should be batch managed specifying FIFO. then, inventory/availability search should be plant level instead of storage location level.
i will try to get back to you with the specifics. but in the meantime, you could probably get your MM consultant to help you with this.
regards.

Regarding how enable plant stock and storage location view

hi all:
   Could you please tell me how enable plant stock and storage location view for MM01?
   couldn't be better if there are detailed steps .
   Thank you very much!

Hi,
The views depend to material type. So you need update in the material type attributes.
SPRO - Logistic General - Material Master - Basic Settings - Material Types - Define Attributes of Material Types
Double click on the material type and update the views in 'User Departments'.
Thanks.

Opening Stock Comapny - Plant - Material - Batch - Storage location Wise

Dear Friends,
I want to do the following report. I will explain the details to you. Pleaes suggest on how to go about it.
1. Since you know that SAP stores stock in a summary form (Plant / Material wise). Our management wants the report on the following hierarchy. (Company - Plant - Material - Batch - Storage). Our management has suggested the following:
a. Create a ZTABLE with the above columns including Quantity (which will contain closing stock quantity).
b. In this calculate and store Closing stock for each month.
c. an insert / update program has to be created for uploading data in the ZTABLE (selection will contain date).
for ex:
When running the program for 31st March 2008. system will take the closing stock stored in the ZTABLE for previous months + March Receipt - March issues. the result will be the closing stock for March 2008.
d. Then a report will be prepared using the ZTABLE and other calculated fields.
Can anyone give me the guideline as to how to go about it. Tables to be used and logic to be followed? Or if any other way the result can be achieved then nothing like it.
The Managements final goal is to have any given date closing stock in the above hierarchy (minimizing the Performance issue... that is why the suggestion of ZTABLE)...
Awaiting for your expert opinions.....
Regards,
Jitesh M Nair

Figured out

Profit centre at storage location level

Hi Experts,
Can we define a profit centre @ storage location level?
My scenario :
The document splitting of FI is activated for the document type of FI and also the profit centre is mandatory entry for any accounting document that will be created so when I am trying to post a MIGO I encounter the error
"Balancing field "Profit Center" in line item 001 not filled"
We have a option of maintaining a profit centre in plant data/storage location but i will be updated in the profit centre field of Costing1 view . But we does not want to upadate in costing view of material master data.
Basically We want the system to determine profit centre based on storage location in Goods reciept transaction .
Helpful Sugestions on this would be helpful & rewarded max .
points.
Regards,
Patil
t

Hi Raju ,
Thanx for the reply.I am Basavarajs Collougues.
Our Enterprise Structure of our Client is as follows
One company code is assigned to one plant and we have treated all the branches across India as Storage locations.Each Branch (Storage Location- MM) is configured as Profit centres in FICO.The goods are procured for a storage location.
By using the functionality of document splitting, the profit center field is made mandatory for all the accounting documents generated in the system. Now we are trying to post a goods receipt against a Purchase Order, the system is giving error "Balancing field "Profit Center" in line item 001 not filled"
The option is there to maintain a profit center at the plant level.But we have several storage locations under the plant and each storage location has to be linked with the particular profit center. So that, while doing goods receipt the system should determine profit centre based on the storage location in purchase orders.
Please suggest on this.
Regards,
SVU123

MC.9 drill down at storage location level

In mc.9 report stock against plant xxxx at storage location drilldown
I see
In total valuated stock is 0
But
at storage location 0040 I see 423.686 as valuated stock
and at storage location 5M06 I see minus 423.686 as valuated stock
Client need to have not stock at plant level.
In total I see 0
But client is bothering about valuate stock he is getting at storage location level.
Thanks,
Kiran

Hi Jurgen,
For plant xxxx there is nil stock in mc.9 report. only I see sloc to sloc transfer of qty. for example sloc 0001 has qty + 100 & sloc 0002 has qty -100.
Finance is asking to user that this + - qty should not show in mc.9 and asking him to get it removed.
What should I suggest to user and finance.
Thanks,
Kiran

Availablity check at storage location level in STO

Hi,
There is an unique requirement from my client with respect to the Availability check at storage location level in STO
Process:
Based on the inputs from APO we are creating STR for moving the material from one plant to another plant. These STR’s will be converted into STO through ME59N batch job. During STO creation process system will do the availability check and only if stock is available in the issuing plant then only STO will be generated.
During this availability check the stock will be considered at plant level and not at storage location level.
Requirement/Scenario:
Issuing plant contains two storage location ( location A & B).FG stock exists in both the locations.
Our requirement is system should create separate line items in the STO based on the availability of the stock in the respective storage locations.
Example
Total required qty: 1000 of material X
material X - Stock in Storage location A : 600
material X - Stock in Storage location B : 400
Two separate line item needs to be created in the STO
Sl no
Material
qty
Issuing storage location
1
X
600
A
2
X
400
B
Is there any function module available for doing Availability check at storage location level so that it can be called in ME59N with the enhancement.
Please suggest how to achieve this. If any enhancements needs to be done we will do it.
Thanks & regards,
Prashanth

Hi Nilesh,
in SAP standard the system is always checking on plant level first and then on the storage location level, there is no possibility to change this behaviour.
I'm also not sure if the process is correct, because if you have also requirements on plant level only then you would create negative ATP if you confirm on storage location level even though there is no ATP on plant level.
I'm also not aware of a user-exit that would suite your requirement, additionally according to the IMG documentation the user-exits in the availability check area should only be carried out in agreement with SAP.
Regards,
Markus

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 valuation level

Hello all,
We are using moving average price (MAP) at plant level valuation. We have several Storage Locations assigned to the same plant. We have several Client non-valuated goods-receipt at Storage location. That increases the quantity, but not the value. Therefore, of course those actions
changes the MAP. We are not using batches or WM module.
How can we not change the MAP without using batches? Is that possible to put a valuation level at storage location?
Can anyone help us to solve this problem?
Thank you in advance very much!
Best regards,
Pedro Grabulho.

No you do not have to change OU which is plants in your case.
1. The procedure is to activate split valaution using OMW0(zero) t-code, which is active in your case, I guess.
2. Define Global Valuation Type. You can define Storage locations here or it can be any thing else. Use T-code OMWC. (BTW, every time you add one storage location, you have to make appropriate changes here also, It is not like your storage location becomes valuation type)
3. Define Global Valuation Categories.
4. Attach Categories to OU. (OU can either be Plant or Company code, there is no 3rd option). You can atttach in one or more OU(plant)where you want it active. 3rd & 4th steps are in the same T-code OMCW.
5. Using the MM01 now extend the material to the newly created Valuation Types. (Accounting 1 view)
Thanks,
Ashish

Storage Location level ATP check with CRM

Hi:
I am on an implemenation where the integration is between CRM, EWM and GATP. So, consider the situation where the sales order check is done through CRM and a call to GATP is made.
Some background on supply
EWM would like to receive the goods into storage location ROD (Received On Dock) and then do a movement type to move it to storage location AFS (Available For Sale). The sales orders should consider only the supply from storage location AFS and not ROD.
First question is, is it possible to do a storage location level determination in CRM? I don't think so but wanted to confirm. The reason is because even a plant determination is not possible in CRM when you integrate with GATP (the plant is determined through Rules).
Now, suppose that we have determined the storage location called AFS (in gATP through enhancement) and will do an ATP only at that level in GATP. Suppose that the first plant that will be checked is Plant A and then based on the location determination procedure, the next plant that will be checked is Plant B. When the system checks supply at Plant B, then the question is this: will it still check only at storage location AFS in Plant B or will it check at the plant level? The requirement will be to check at the same storage location level (which means that whatever process we used to determine the storage location at Plant A has to be followed for Plant B also).
One option that can be considered is to check at the Storage Location MRP Area level (there seems to be better support for RBA and Storage Location MRP Area than just storage location). See SAP Note 412314. But this is also complicated.
Another option is to not check at the storage location level but represent the various stocks with stock types (stock type ROD and stock type AFS) and only the stock type AFS will be used in the list of ATP categories.
Please share any experience that you may have in this.
Thanks,

Hi Satish,
In my project also we had this requirement to determine the correct Storage location after plant has been determined by using rules.
What we did is as follows:
- We created a Z table which had entries for all plants and preferred storage locations for those plant (only one entry per plant) in your case it will be like:
Plant A - AFC
Plant B - AFC
Plant C - AFC
- We used a ATP user exit in APO to get the storage location of source plant ( which was determined in APO via rules) from the Z table.
I hope this helps.
Please let me know if you have any questions.
Thanks,
Anupam
Edited by: Anupam Sengar on Dec 20, 2011 12:03 AM

Storage Location Level ATP check through CRM

Hi:
I am on an implemenation where the integration is between CRM, EWM and GATP. So, consider the situation where the sales order check is done through CRM and a call to GATP is made.
Some background on supply
EWM would like to receive the goods into storage location ROD (Received On Dock) and then do a movement type to move it to storage location AFS (Available For Sale). The sales orders should consider only the supply from storage location AFS and not ROD.
First question is, is it possible to do a storage location level determination in CRM? I don't think so but wanted to confirm. The reason is because even a plant determination is not possible in CRM when you integrate with GATP (the plant is determined through Rules).
Now, suppose that we have determined the storage location called AFS (in gATP through enhancement) and will do an ATP only at that level in GATP. Suppose that the first plant that will be checked is Plant A and then based on the location determination procedure, the next plant that will be checked is Plant B. When the system checks supply at Plant B, then the question is this: will it still check only at storage location AFS in Plant B or will it check at the plant level? The requirement will be to check at the same storage location level (which means that whatever process we used to determine the storage location at Plant A has to be followed for Plant B also).
One option that can be considered is to check at the Storage Location MRP Area level (there seems to be better support for RBA and Storage Location MRP Area than just storage location). See SAP Note 412314. But this is also complicated.
Another option is to not check at the storage location level but represent the various stocks with stock types (stock type ROD and stock type AFS) and only the stock type AFS will be used in the list of ATP categories.
Please share any experience that you may have in this.
Thanks,
Satish

Hi Satish,
In my project also we had this requirement to determine the correct Storage location after plant has been determined by using rules.
What we did is as follows:
- We created a Z table which had entries for all plants and preferred storage locations for those plant (only one entry per plant) in your case it will be like:
Plant A - AFC
Plant B - AFC
Plant C - AFC
- We used a ATP user exit in APO to get the storage location of source plant ( which was determined in APO via rules) from the Z table.
I hope this helps.
Please let me know if you have any questions.
Thanks,
Anupam
Edited by: Anupam Sengar on Dec 20, 2011 12:03 AM

Link material to profit center at storage location level

Hello,
I have one plant 0001, two storage location assigned to this plant (MAG1, MAG2).
In " MAG1", I am keeping the consignment stock (stock blongs to my vendor), hence when I create the material at the storage location I need that profit center be set to PF1
"MAG2" is my own stock location, so when I create material at MAG2 level, I need that profit center be set as PF2.
Does standard SAP allows such scenario.
Is there any possibility to map this scenario
Many thanks for your help
Meher Souayeh

Dear,
Basically GUIXT script work mainly from Technical point of view..
Here they can write codes accordinly so that if you want to make any sort of changes in the application or if you want to put some restriction parameters then by writing codes, it is very much possible to get the desired output.
Hope this clears your doubt.
Utsav

Number range purchase requisitions at storage location level

How can I define a number range for purchase requisitions at storage location level? I have one plant with several storage locations and I want a number range for purchase requisitions per storage location.

what is the background to this request?
I guess that the requestor can easily identify their own requisitions among many.
I dont think that this is necessary with SAP, do not put to much importance in numbers, there are many other options to meet the users requirements.

Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help the client in Data Mapping activity.

Hello All,
Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help in Data Mapping activity.
Thanks,
Mownesh

There are standard templates in HCI data sources.
e.g. 1) Customer Master data template is SOP_MD_CustomerMaster for extracting master data from SAP ECC and load it to S&OP
KNVP is the table for customer in ECC from that you can select the fields as required
KUNNR for customer Number
ADRNR for Address
List of a few commonly used table names of ECC:
Product Related:
MARA – Material Master (MATNR)
MARC – Material Master with Plant Data (MATNR, WERKS)
MARD – Material Master with Storage Location Data (MATNR, LGORT, WERKS)
MAKT – Material Master Material Descriptions (MATNR, MATKL)
MBEW – Material Valuation Data (MATNR, BWTAR)
MVKE – Material Master : Sales related Data
MDKP, MDTB – MRP related Data( Header, Item)
MCHA, MCHB – Material Batches (Header, Item) (MATNR, WERKS, LGORT, CHARG)
Vendor/Supplier related:
LFA1 – vendor data (LIFNR)
LFB1 -- Company Code Segment : Vendor Data(LIFNR, BUKRS)
LFC1 -- FI Related Vendor Data (LIFNR, BELNR)
LFM1 – Pur. Orgn. Related Vendor Data (LIFNR, EKORG)
PReq/PO, BOM Related:
EBAN – Pur. Req. Data( BANFN, BNFPO, BADAT, MATNR)
EINA – Purchase Info. Record(General Data)(INFNR, MATNR, LIFNR)
EINE – Purchase Info. Record (pur. Orgn. Data) (INFNR, EKORG)
ELBK, ELBN, ELBP – Vendor Evaluation Related Data
EKKO – PO Data (Header) (EBELN, BSTYP, BSART)
EKPO – PO Data (Item) (EBELN, EBELP, MATNR)
Pur. Req., RFQ and PO are differentiated by Doc Type (BSTYP) in EKKO table.
For RFQ it is ‘A’ and for PO it is ‘F’
MKPF – GRN Data (Header) (EBELN, BLDAT, BUDAT, XBLNR, BKTXT)
MSEG – GRN Data(Item) MBLNR, BWART, LIFNR, MATNR, EBELN)
Apart from this there are lot of tables which begin with ‘M’ & ‘E’, but we
use the following very often.
EQUK – Quota (Header)(QUNUM, MATNR)
EQUP – Quota (Item) (QUNUM, QUPOS, LIFNR)
EKBE – PO History Data (EBELN, EBELP, BELNR, BLDAT, MATNR, VGABE)
EKBZ – PO History with Delivery Costs(EBELN, BELNR, LIFNR, XBLNR)
EKET – Schedule lines data of a PO(EBELN, EINDT, SLFDT)
EKES – Vendor Confirmations Data (EBELN, EBTYP, EINDT, XBLNR)
T163F – Confirmation Texts (EBTYP, EBTXT)
T156 – Movement Types (BWARE)
T024 – Purchasing Groups
T024E – Purchase Organizations
T163 – Item Category’s in Purchasing Documents(PSTYP)
T149D – Valuation Types
T134 – Material Types
FVLK – Delivery Types
STKO, STPO – BOM(Bill Of Material) related Data (Header & Item)
STPU, STPN, STST, STZU – BOM Related Tables
RKPF, RBKP, RSEG (Header & Item) – MM – FI Related Data
KONO, KONH – Pricing data
T006 – Basic Unit Of Measurements
Customer/Sales Order Related:
VBAK : Sales Document(Header Data) (VBELN)
VBAP : Sales Document(Item Data) (VBELN, POSNR, MATNR, ARKTX, CHARG)
Enquiry, Quotation, Sales Order are differentiated based on Doc.
Type(VBTYP Field) in VBAK, VBAP Tables for Enquiry VBTYP = A, for Quotation ‘B’ & for Order it is ‘C’.)
LIKP : Delivery Table(Header Data) (VBELN, LFART, KUNNR, WADAT, INCOL)
LIPS : Delivery Table(Item Data)(VBELN, POSNR, WERKS, LGORT, MATNR, VGBEL)
(LIPS – VBGELN = VBAK- VBELN, LIPS-VGPOS = VBAP-POSNR)
VTTK : Shipment Table(Header Data) (TKNUM)
VTTP : Shipment Table (Item Data)(TKNUM, TPNUM, VBELN)
(VTTP – VBELN = LIKP – VBELN)
VBRK : Billing Table(Header Data) (VBELN, FKART, BELNF)
VBRP : Billing Table(Item Data) (VBELN, POSNR, FKIMG, NEWR, VGBEL, VGPOS)
(VERP – AUBEL = VBAK- VBELN, VBRP – VBEL = LIKP – VBELN)
Apart from these tables there are lot of other tables which starts with ‘V’, but we use the
following tables frequently.
VBUK: All Sales Documents status & Admn. Data(Header) (VBELN, VBTYP)
VBTYP = ‘C’ (Sales Order) VBTYP = ‘L’(Delivery) VBTYP = ‘M’(Invoice)
VBUP: Sales Documents status & Admin. Data(Item) (VBELN, POSNR)
VBEP : Sales Document Schedule Lines Data (VBELN, POSNR, EDATU, WMENG)
VBKD: To get sales related Business data like Payment terms etc.(VBELN, ZTERM)
VBFA: Sales Document flow data(VBELV, VBELN, POSNV, VBTYP)
VBPA: Partner functions Data(VBELN, PARVW, KUNNR, LIFNR)
TVLKT: Delivery Type: Texts(LFART, VTEXT)
KNA1, KNB1, KNC1 : Customer Master Data and Other Partner’s Data(KUNNR,
NAME1,LAND1)
KNVK: Customer Master Contact Person(PARNR, KUNNR)
KNVV: Customer Master Sales Data.
LFA1, LFB1, LFC1: Vendor Master Data(To get Transporter data)(LIFNR, NAME1, ORT01)
MARA, MARC, MARD : Material Master Data(Basic, Plant, St. Location Views)
TVKO: Sales Organizations(VKORG)
TVKOV: Distribution Channels(VTWEG)
TVTA: Divisions(SPART)
TVKBZ: Sales Office(VKBUR)
TVBVK: Sales Group(VKGRP)
T077D: Customer Account Group(KTOKD)
T001W: Plants(WERKS)
T001L: Storage Locations(LGORT)
TWLAD: To get address of Storage Location and Plant(LGORT, ADRNR)
TVAU: Sales Document (Order) Types
KONV: Condition Types (pricing) (KNUMV, KSCHL, KWETR)
T685T: Condition Types Texts.
ADRC: To get Addresses of Partners
VBBE, VBBS: Sales Requirements Data
VBKA: Sales Activities Data
VBPV: Sales Document Product Proposal
Based on the functionality you can search ECC table names and fields
Hope this information is helpful for you.
Thanks and Regards,
Anjali

Create Plant or just separate Storage Location

I am trying to determine where the magical line is to decide whether to establish a separate address location as a different plant or location. My example is not very complex. It is a satellite production location that produces products for use as raw materials for another production facility that assembles and sells the final product. The satellite location will have a separate cost center and will use activity rates and costing sheets for overhead recovery. My inclination is to set the satellite facility as a plant but supply Chain team sees this as overkill and would rather make it simply a storage locations.
Can someone provide a white paper or list of positives and negatives to storage location versus plant? I know some things might involve the following:
1-If valuation of products are different or may at some point involve different values by location, a plant is needed.
2-If products are sold directly from location, plant would make more sense.
3-If inventroy is transferred between locations with differing addresses, various tax and bank reporting could necessitate the use of separate plants.
4-When manufacturing activities exist, a plant is logical.
5-If all purchasing is performed at a central location, a separate plant may not be required for this purpose.
My existing dilemma relates to the fact that we use costing sheets by plant. Without a separate plant, using different storage locations forces me to use the Material Origin Group to dileneate the extra location if I don't want to use the plant based overhead rates. This seems like a violation of best practice and proper use of SAP.

Hi
If you define satellite production location as Storage location you can not do profitable analysis at this unit. My suggestion is activate MRP area at storage location level. So that satellite production unit is treated as separate entity under the same Plant. This will just help you to do the Supply chain activities (purchasing, Sale, Prod and STO) at MRP area level. But Profitability analysis still can be done at Plant level only.
This will solve your point numbers 2, 3, and 4.For material valuation (Point number -1) I think you have to go for split valuation.
Regards,
Velmurugan S

Reg : client level data,plant level data,storage location level data

Similar Messages

Maybe you are looking for