Synchronizing Material Master revision level across multiple plants

Hello,
If an organization uses material master revision level to maintain the details of material's validity across different plants then we see a material master with different revisions in that organization. Now I would like to understand the impact of this practice in big organizations , is it advisable to have a material master with different revisions in different plants? , if not then which is the best way to synchronize these material masters ( with different revision level ), which are already in use?
Bets Regards,
Avinash
Message was edited by: Ulf Petzel

Hello Ulf,
Thanks for your reply, the actual issue is..
There are two companies; both are using the same material.
We are building a central system and synchronizing the materials from all companies.
While synchronization, we found that revision level are different across companies.
1.      Should we avoid using revision level in our organization?
2.      If I can find the validity of a material with change no + material + plant, then what is the purpose
         of the revision level?
3.     What will be the impact, if we remove the entire revision level across all companies?
4.     In real world, across different organizations, how revision level is synchronized across companies or at least in the central system.
Please let me know your valuable inputs.
Thanks
Sridhar

Similar Messages

Open PR Material Master Revision Level

Hi,
I am working on upgrade from 4.5b to ecc6.0.In this Project Material Revision Level and Change Number is assigned with Z Program.
The Requirement is the Program has to check the Open PR 's and that particular Material needs to be updated with Change Number and Revision Level.
Now the Functional Specification to be prepared for the Technical Team -Based on the Open PR condition -Now what are the fields to be specified in EBAN table in order to fullfill the open PR.
As per my understanding Open PR means PO is not created and PO is created means that PR is closed.
Or any other fields are to taken into consideration for preparing Functional Specification
Please reply me ..
Thanks for the reply.

It is very much possible. You can try this use case. It's pretty simple. But Vice-versa is not possible.
~ Guru

Create Material Master Revision Level using CC02

Dear oss ,
Using CC02 for a change number I can view object material and I can insert a new material. The revision level field is greyed.
Can I have a chance to create revision level for a material directly using CC02 ?
Thanks.

If you want to create revision level of Material then use t-code CC11. I hope it would help you.
Thanks!!!

MRP across multiple plants

Hello everyone,
I have a scenario where I have multiple plants. During Production of some finished products, I have to procure some material from anothere plant. For this I have used Special procurement key in MRP 2 to throw requirement to corresponding plant.
As Per MRP run, I Hope to use NEUPL run once a week for the corresponding plant. Do I Have to run MRP seperately for each plant so that MRP requirement for semi finished products are also raised in corresponding plant. Will in that case help to group together multiple plants under scope of planning or an MRP area.
My second question is that if we run MRP with processing Key: NETCH what can be the corresponding impact. I was hoping to run it daily so as to capture changes in requirements, if any.
Please do give your suggestions.
Sincerely,
Aji Kurian Mani

Brian,
I am looking for a way to run MRP across multiple plants as if it was one plant.
Well, that phrase can mean different things to different people. In general, though, SAP ERP does not support this requirement.
I guess you overlooked the rules of engagement for this forum, which state that you should first search the forums for answers before posting a question. There are lots of workarounds, using Special Procurement and/or MRP Areas. Just search the ERP PP and ERP MM forums. This topic has been discussed extensively.
There are also several third party products available that can probably meet your requirements as well. Be advised that the purchase price of these products are substantial, and the implementations are not trivial. Many shops are unwilling to invest the money and effort into advanced planning systems, and end up just working with ERP planning, using workarounds, enhancements, and business process changes.
SAP is also marketing one of these advanced planning products as a 'solution extension', that they are calling Supply Chain Response Management (SCRM). This software was developed by the third party software company ICON, and SAP now has established a relationship with ICON. You can see info on the software at
http://www.sap.com/solutions/solutionextensions/supply-chain-response-management/index.epx
and also on the ICON website at
http://www.icon-scm.com/en/products/sap-supply-chain-response-management-by-icon-scm/
Best Regards,
DB49

APO gATP vs R/3 ATP - To check sales order ATP across multiple plants

Hi There,
I am trying to evaluate gATP functionality for SD sales orders.
The primary requirement is to have sales order ATP checking take place across multiple plants.
E.G.
Sales order line is entered for qty 100
60 is available in plant A, 40 is available in plant B
System checks both plants and creates 2 lines - one for delivery from plant A and one for delivery from plant B
(we are currently heading down the road of writing ABAP to do this 'multi-plant' check in R/3 but the more complex the requirements get the more interested I am in understanding more about APO/gATP)
I would like to understand the benefit of implementing APO / gATP as opposed to using standard R/3 ATP and perhaps writing custom ABAP code to search for inventory across multiple plants.
I would appreciate any insight regarding what is required to setp gATP to perform such checking and any other feedback regarding this issue - especially if you have had to implement something similar at your company.
I have looked here but not much clear help:
http://help.sap.com/saphelp_scm50/helpdata/en/26/c2d63b18bc7e7fe10000000a114084/frameset.htm
Thanks,
Niall

Hi Niall
you are probably looking at RBATP (Rule based ATP). Look at transaction /sapapo/rba04 in APO where you develop your own location and product substitution rules. Going down an ABAP road in R/3 may work short-term but not long-term as the requirements may get more complex.
Regards
Srinivas

Availability check across multiple plants

Can anyone tell me how to do availability check across multiple plants belonging to same Company Code on First Expiry First Out basis. The Sales Order should Pick up plant which has product(batch) which is near to expiry .

Dear Kalpkothari ,
Your requirement can be fulfilled using the following user exit.
USEREXIT_SOURCE_DETERMINATION
OR
USER EXITS AVAILABLE FOR AVAILABILITY CHECK
User exits in program FV45VFZZ
o   USEREXIT_ADD_FIELD_TO_HEADER
o   USEREXIT_ADD_FIELD_TO_LINE
User exits in program FV45VFZY
o   USEREXIT_DELIVERY_GROUPS
o   USEREXIT_MVERF_INIT
o   USEREXIT_QUOTA_KEY_VALUE
User exits in program RV03VFZZ
o   USEREXIT_AVAILABILITY_IN
o   USEREXIT_AVAILABILITY_OUT
o   USEREXIT_DARA_REFRESH
o   USEREXIT_PLANT_SELECTION
Thanks & Regards,
Hegal Charles

Material Master in more than one plant /purchasing group/Valuation Class

Hi All,
How to maintain a Material Master in more than one plant /purchasing group/Valuation Class......
Points shall be awarded accordingly,
Regards,
Rounak

in mm01 u can extent the material for new plant
first creat all the views say purchasing accounting basic view etc for one plant
the go to MM01 put same materal code and select the views purchasing and accounting
now put the other plant number
enter
and put the purchasing and valuation class etc asd save
thuis u can extend the material to other plant
reward if usefull
Message was edited by:
Umakant Bhangale

Extending material master for different sales org/plant combination

hi ,
1 ) a material can be sold from one plant by many sales organisations. so we map this scenario in enterprise structure by the config step "assign sales org--dist channel--
plant ". (let's say sales org A and B selling from plant 1 and also sales org A selling from plant 2)
when we have defined the above config step, then why we need to have material master extended for different combination of sales org and plant as in stpe 1 ?. we can just create one material master with one plant and sales org combination and based on config as in step one, we can sell material from any sales org from a plant ?
2) we can extend material master for any combination of sales org/plant .....is it also possible to extend material master to different storage locations !
regds
pamela
Edited by: Pamela79 on Feb 15, 2011 11:02 AM

There are several reasons why you should extend the materails to different sales organizations and plants.
a. The materials are normally valuated at the plant level. So, you can have different valuations at different plants.
b. You can have different quantity stored in different plants. How do you know which plant has what quantity.
c. You can have materail not to be sold from one plant, but you can have the same materail sold from the other, how do you block it? at the plant and materail combination, you can do it.
d. For different sales organizations, you may want the cost and the price to be posted to different GL accounts. You can control it at sales org level of the materail.
e. You may just want the material to be purchased but not sold, then you may not even create a sales org view for the material. But say, in future you will like to only purchase a materail from a plant and consume it for some other purpose but not sales (which u did previously), then you can block it at sales org and dbr level.
So, these are a few reasons. But there could be many. You can have a look at the fields in the material master at sales org level and plant level and you can find it for yourself howmany parameters are there to control...
Hope this helps...
Regards,
Mukund S

How to deleate material master in basic data corss-plant cm

in material master fert in basic data cross-plant cm how to delete

Hi Gopal,
its not possible to delete entry from "cross-plant cm" baisc data 2 view.
once you made a entry in this field , it will greyed out and its not possible to delete it.
its a important field related to variant configuration, and one should be careful before making any entry in this field. same is applicable to MARC-STDPD in MRP 3 view.
Regards
Ritesh
Edited by: R S D on Jun 2, 2009 12:22 PM

Material Master Extension to all the plants of same type

Hi
In the given scenario, we have almost 200 plants where same materials are required , now when we create material master using Tcode MM01 we want to extend this material master to all the plants of same type in one go .Is it possible , if yes , how to go about it ?? please help, this is the specific customer requirment .
ans will be rewarded
rgds
mojib

Hi,
Just go through the code
report ZMM_FERT_CREATE_EXT_PLANT
       no standard page heading line-size 255.
*include bdcrecx1.
DATA : it_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE,
       it_bdcmsgcoll LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
data : p_filex type string .
types: BEGIN OF t_mm01,
        matnr(018),
        MAKTX(040),
        mtart(004),
        matkl(009),
        WGBEZ(020),
        bklas(004),
        vprsv(001),
        werks(004),
        vkorg(004),
        vtweg(002),
        sktof(001),
        versg(001),
        kondm(002),
        ktgrm(002),
        meins(003),
        gewei(003),
        j_1ichid(012),
        j_1isubind(001),
        j_1icapind(001),
        j_1igrxref(001),
        tragr(004),
        ladgr(004),
        mtvfp(002),
        xchpf(001),
        mtpos_mara(004),
        mtpos(004),
        ekgrp(003),
        BWTTY(010),
        meins1(003),
        meins2(003),
        meins3(003),
        sales_txt(040),
        purc_txt(040),
        mbrsh(001),
        verpr(015),
        peinh(006),
        stprs(015),
        brgew(017),
        ntgew(017),
        j_1ivalass(018),
        umrez1(006),
        umren1(006),
        umrez2(006),
        umren2(006),
        umrez3(006),
        umren3(006),
        lgort(004),
        TAXKM1(001),
        TAXKM2(001),
        HERKL(003),
        HERKR(003),
        J_1IMOOM(018),
      end of t_mm01.
DATA : it_mm01 type table of t_mm01 with header line initial size 0.
*Selection Screen                                              *
SELECTION-SCREEN BEGIN OF BLOCK B WITH FRAME TITLE text-001.
            PARAMETERS: p_file like IBIPPARMS-PATH obligatory.
SELECTION-SCREEN:END OF BLOCK B.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file .
PERFORM get_filename.
*START-OF-SELECTION
START-OF-SELECTION.
   PERFORM upload_data.
   PERFORM fill_data.
*&      Form upload_data
*       text
* --> p1        text
* <-- p2        text
form upload_data .
p_filex = p_file.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    filename                      = p_filex
    FILETYPE                      = 'ASC'
    HAS_FIELD_SEPARATOR           = '#'
*   HEADER_LENGTH                 = 0
*   READ_BY_LINE                  = 'X'
*   DAT_MODE                      = ' '
*   CODEPAGE                      = ' '
*   IGNORE_CERR                   = ABAP_TRUE
*   REPLACEMENT                   = '#'
*   CHECK_BOM                     = ' '
*   NO_AUTH_CHECK                 = ' '
* IMPORTING
*   FILELENGTH                    =
*   HEADER                        =
tables
    data_tab                      = it_mm01
EXCEPTIONS
   FILE_OPEN_ERROR               = 1
   FILE_READ_ERROR               = 2
   NO_BATCH                      = 3
   GUI_REFUSE_FILETRANSFER       = 4
   INVALID_TYPE                  = 5
   NO_AUTHORITY                  = 6
   UNKNOWN_ERROR                 = 7
   BAD_DATA_FORMAT               = 8
   HEADER_NOT_ALLOWED            = 9
   SEPARATOR_NOT_ALLOWED         = 10
   HEADER_TOO_LONG               = 11
   UNKNOWN_DP_ERROR              = 12
   ACCESS_DENIED                 = 13
   DP_OUT_OF_MEMORY              = 14
   DISK_FULL                     = 15
   DP_TIMEOUT                    = 16
   OTHERS                        = 17
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.                    " upload_data
*&      Form get_filename
*       text
* --> p1        text
* <-- p2        text
form get_filename .
CALL FUNCTION 'F4_FILENAME'
               EXPORTING
                 PROGRAM_NAME        = SYST-CPROG
                 DYNPRO_NUMBER       = SYST-DYNNR
*                 FIELD_NAME          = p_file
               IMPORTING
                 FILE_NAME           = p_file .
               if sy-subrc NE 0 .
                  write : / 'Enter File Name'.
               endif.
endform.                    " get_filename
*&      Form fill_data
*       text
* --> p1        text
* <-- p2        text
form fill_data .
*perform open_group.
loop at it_mm01.
clear it_bdcdata.
refresh it_bdcdata.
perform bdc_dynpro      using 'SAPLMGMM' '0060'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-MTART'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'RMMG1-MATNR'
                               it_mm01-matnr.
*                              '116100'.
perform bdc_field       using 'RMMG1-MBRSH'
                              'C'.
perform bdc_field       using 'RMMG1-MTART'
                              'FERT'.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(16)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(03)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(05)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(06)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(07)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(09)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(10)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(13)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(16)'
                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '0080'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-VTWEG'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'RMMG1-WERKS'
                               it_mm01-werks.
*                              '9010'.
perform bdc_field       using 'RMMG1-LGORT'
                               it_mm01-lgort.
*                              'F901'.
perform bdc_field       using 'RMMG1-VKORG'
                               it_mm01-vkorg.
*                              '1000'.
perform bdc_field       using 'RMMG1-VTWEG'
                               it_mm01-vtweg.
*                              '03'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'BDC_CURSOR'
                              'MVKE-MTPOS'.
perform bdc_field       using 'MVKE-VERSG'
                                it_mm01-versg.
*                              '1'.
perform bdc_field       using 'MVKE-KONDM'
                                it_mm01-kondm.
*                              '03'.
perform bdc_field       using 'MVKE-KTGRM'
                               it_mm01-ktgrm.
*                              '01'.
perform bdc_field       using 'MVKE-MTPOS'
                                it_mm01-mtpos.
*                              'NORM'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-MTVFP'
                               it_mm01-mtvfp.
*                              '01'.
perform bdc_field       using 'MARC-XCHPF'
                               it_mm01-xchpf.
*                              'X'.
perform bdc_field       using 'BDC_CURSOR'
                              'MARC-LADGR'.
perform bdc_field       using 'MARC-LADGR'
                               it_mm01-ladgr.
*                              '0003'.
perform bdc_dynpro      using 'SAPLMGMM' '4004'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-HERKL'
                               it_mm01-HERKL.
*                              'IN'.
perform bdc_field       using 'MARC-HERKR'
                               it_mm01-HERKR.
*                              '01'.
perform bdc_field       using 'BDC_CURSOR'
                              'J_1IASSVAL-J_1IVALASS'.
perform bdc_field       using 'J_1IMTCHID-J_1ICHID'
                               it_mm01-J_1ICHID.
*                              '2913 00 90'.
perform bdc_field       using 'J_1IMTCHID-J_1ISUBIND'
                                it_mm01-J_1ISUBIND .
*                              'X'.
perform bdc_field       using 'J_1IMTCHID-J_1ICAPIND'
                                it_mm01-J_1ICAPIND.
*                              'F'.
perform bdc_field       using 'J_1IMTCHID-J_1IGRXREF'
                                 it_mm01-J_1IGRXREF .
*                              '2'.
if it_mm01-J_1IVALASS <> '0'.
perform bdc_field       using 'J_1IASSVAL-J_1IVALASS'
                                it_mm01-J_1IVALASS.
*                              '0'.
endif.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                               it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'BDC_CURSOR'
                              'MARC-EKGRP'.
perform bdc_field       using 'MARC-EKGRP'
                               it_mm01-ekgrp.
*                              '002'.
perform bdc_field       using 'MARC-XCHPF'
                               it_mm01-xchpf.
*                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'BDC_CURSOR'
                              'MAKT-MAKTX'.
perform bdc_field       using 'MAKT-MAKTX'
                               it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-STEUC'
                               it_mm01-J_1ICHID.
*                              '2913 00 90'.
perform bdc_field       using 'MARC-HERKL'
                                it_mm01-HERKL.
*                              'IN'.
perform bdc_field       using 'MARC-HERKR'
                               it_mm01-HERKR.
*                              '01'.
perform bdc_field       using 'J_1IMTCHID-J_1ICHID'
                               it_mm01-J_1ICHID.
*                              '2913 00 90'.
perform bdc_field       using 'J_1IMTCHID-J_1ISUBIND'
                                it_mm01-J_1ISUBIND.
*                              'X'.
perform bdc_field       using 'J_1IMTCHID-J_1ICAPIND'
                               it_mm01-J_1ICAPIND.
*                              'F'.
perform bdc_field       using 'J_1IMTCHID-J_1IGRXREF'
                                it_mm01-J_1IGRXREF.
*                              '2'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'BDC_CURSOR'
                              'MAKT-MAKTX'.
perform bdc_field       using 'MAKT-MAKTX'
                               it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-XCHPF'
                                it_mm01-xchpf.
*                              'X'.
*perform bdc_field       using 'MARA-IPRKZ'
*                              'D'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'BDC_CURSOR'
                              'MBEW-STPRS'.
perform bdc_field       using 'MBEW-BKLAS'
                                it_mm01-bklas.
*                              '7930'.
perform bdc_field       using 'MBEW-VPRSV'
                                it_mm01-vprsv.
*                              'S'.
perform bdc_field       using 'MBEW-PEINH'
                                it_mm01-peinh.
*                              '1'.
perform bdc_field       using 'MBEW-VERPR'
                                it_mm01-verpr.
*                              '273.75'.
perform bdc_field       using 'MBEW-STPRS'
                               it_mm01-stprs.
*                              '207'.
perform bdc_dynpro      using 'SAPLSPO1' '0300'.
perform bdc_field       using 'BDC_OKCODE'
                              '=YES'.
CALL TRANSACTION 'MM01' USING it_bdcdata
                                MODE 'A'
                                UPDATE 'A'
                                MESSAGES INTO it_bdcmsgcoll.
CLEAR it_mm01.
endloop.
*perform bdc_transaction using 'MM01'.
*perform close_group.
endform.                    " fill_data
*&      Form bdc_dynpro
*       text
*      -->P_0297   text
*      -->P_0298   text
form bdc_dynpro USING prog scr.
CLEAR it_bdcdata.
it_bdcdata-program = prog.
it_bdcdata-dynpro = scr.
it_bdcdata-dynbegin = 'X'.
APPEND it_bdcdata.
endform.                    " bdc_dynpro
*&      Form bdc_field
*       text
*      -->P_0687   text
*      -->P_IT_MM01_VPRSV text
form bdc_field USING fnam fval.
CLEAR it_bdcdata.
it_bdcdata-fnam = fnam.
it_bdcdata-fval = fval.
APPEND it_bdcdata.
endform.                    " bdc_field
Regards,
Madhu.

Single BOM across multiple plants in sub-contracting

We have a single purchasing organisation managing sub-contracting for around 17 plants. This organisaiton purchases sub-contracted items for all the plants.
The problem we are facing is having to maintain the same BOM for all the 17 plants.
The central purchasing org is going to create the PO with multiple lines - requesting delivery from the vendor to the different plants.
How can we avoid having to create the same BOM in every plant?
Regards,
Praveen.

hi
u can avoid by choosing the recurrcive allowed for BOM can avoid it
kishore reddy

Rescheduling across multiple plants

Hi,
When the rescheduling runs, is it possible via the standard system to look for inventory in mulitple plants and change the plant (where the inventory is available) on the sales order item accordingly?
Any thoughts would be highly appreciated.
Thanks,
Prayarna

Not in standard SAP.
You need to write a progrma to do that (I would limit to unconfirmed items only).
But it's not an easy task as material may have different availability control settings in different plants and you in fact may select not the best option...
I believe tools like i2 can do that. Try to check if APO can help here as well.
By writing your own program you may just spend time trying to re-invent the weel (re-create tool like APO or i2) and it's not an easy task

Materia Master field mandatory for specfic plant for a specfic mat type

HI,
I want to make one MARA-XCHPF field mandatory for a specific plant and specfic material type,If I Give Plant specfic Field referance and check the fiield as mandatory in OMSR for the field referance I have created If I mark it mandatory it become mandatory for all the material type,I want to make mandatory for some materials type only that too plant specfic
How to acheive this? kindly guide me
Kantha

Dear Kantha,
check this link may be useful to you.
Mandatory field per material type
Regards,
PK.

CS15 for multiple plants

Hi
Please inform, How to get report similar to CS15 output for multiple plants?

Hi Bhurke,
If you want to search Material Where-used list for multiple plants, then in CS15 first screen enter where used material number and in second screen under Plant give * ( Star symbol) and execute. System will display the Material where used details across multiple plants.
Thanks & Regards,
Ramagiri

Stock of material at different revision levels

Hi,
We are planning to have revision levels (from Engineering Change Management) for a material. There will be different revision levels of the material (for each minor enhancement) and there can be stocks of the material at each of these levels. Can I get the stock of the material for each revision level?
Please note that I will not create new material for each minor enhancement.
Regards,
Lakshman

Thanks for the replies.
Workarounds are fine... (I have already considered these workarounds) but my question was whether I can see the stock at different revision levels.
To rephrase with an example, I have a material 1001 with the current revision level 03. Can a standard report show me the following:
material 1001, revision level 01 stock 100 ea
material 1001, revision level 02 stock 300 ea
material 1001, revision level 03 stock 700 ea
I am looking for an answer to this specific question.
Thanks
Lakshman

Synchronizing Material Master revision level across multiple plants

Similar Messages

Maybe you are looking for