MRP Area Clarification

Hi Friends
I have a Plant with only one storage location and I assign an MRP area with plant type and Storage location type MRP area, when I run MRP for the plant only the plant level requirements are taken into account and the stock is not considered right?? And when I run MRP at MRP area level for storage location the stock is considered and the requirements at plant level are not considered correct?
Please clarify the above
Jade

Hi,
You have a plant with only one str location. Plant is assigned with MRP area & str location also assigned to str loc MRP area.
So in the plant no str location.
When run MRP at str location level, system will not consider plant level.
MRP run at Plant level will not consider str loc MRP area.
Regards,
Dharma

Similar Messages

MC74 : how transfer SOP to PIR for a specific mrp area

Dear guru ,
i want to transfer Planning Data of a SOP Version for a single material to Demand Management.
The copy to Demand is run directly into the plant of the SOP Version.
I manage MRP Area.
How can I transfer directly SOP to PIR for a specific mrp area ?
Thanks in advance

Hi..
In MC87 you have to first create planning data.. SOP.
Then if you go to MC74 your planning data will be transferred..
Ii.e you will get the PIRs automatically from Demand management..
Hope the above clarifies..
karthick

MRP Areas Activation

Is there an option for one to only activate MRP Areas for a specific plant instead of activating for all plants in client?
Thanks.

MRP area activation is must if you would to carry out planning using "scope of planning"...in scope of planning you can group the plants or storage location or sub-contractors and run the MRP at one time. This you can do from MDBT/MD01 transaction in backgorund/online. This option for carry out plannning for MRP areas is not available with other transaction like MD02/MD03.
If you are working with plant level MRP from MD01/MDBT and not using the MRP area then you just have activate the MRP for plant from OMDU transaction. For this MRP area activation is not neccesary.
"MRP area Activation will not effect to the plant which are enabled for plant level MRP from OMDU transaction" Both are having different significance and importance.
Hope the above clarifications is clear.
If satisfy please close this thread or please inform for any more doubts.
Regards
TAJUDDIN

Replenishment delivery for material with MRP areas and Avl Check

HI We have MRP area at storage location level maintained for materials. Stock exists in the plant in the storage location which is part of the MRP area.
Now when I create STO and try to create delivery for the same, system is giving message 0 stock available and not creating delivery. Material has 02 Avl Chck group.If I deactivate the MRP area in the material master, it allows creation of delivery.
How can I ensure that system creates delivery even though stocks exist in MRP area relevant sloc only in the plant?
Sriram

1) According to SAP when inbound deliveries are used and your delivery item category is set up for mvt type 101, these should be received with transaction VL32N. If you use MIGO/MB0A instead the GR status in the delivery will not be updated. If you then report on open deliveries you'll notice that nothing is received in the course of time. Amazing. Now if you set up the delivery item category without the movement type your inbound will not even be GR relevant. Just one of these things that's nice to be aware of.
Check note 199703.
may b it helps...

Can PIR created at wbs element and MRP area of storage location level

Hi,
I tried to create an planned independent requirement at MRP area and WBS element level, but failed. The MRP area is not plant level, but storage location level.
*When trying to create account assignment category Q for it, then there is an error message saying:*
**only stock requirements are allowed when planning at MRP area level.**
Does it mean it is not possible to create planned independent requirement for this case?
Thanks!

Select the "Issue storage location" as '2' here:
spro -> production -> material requirement planning -> mrp groups -> overall maintenance of mrp groups -> overview -> mrp control parameters at material level -> (field) Issue storage location selection
& make sure:
1. In the BOM issue storage location is blank for the components
2. For the FG products , in mrp area prod.storage loc is maintained
3. Components are extended to the mrp area.
Pl. revert with the results

MRP area for running a sale order MRP

Hello PP experts,
I come across a scenario where , I need to do the MRP run for sale order in a MRP area. I have checked , I can put PIR with respect to MRP AREA , but when I open MD50 screen for running MRP for sale order. I did not found the MRP AREA
field in the screen.
In short , my question is , How the sale order MRP run , system will do in a MRP
area defined for the material ?
Here , I have already defined the material is MRP AREA and also I have created
MRP area segment in the material master.
I have also configured the MRP area in SPRO.
Waiting for your reply.
Regards,

Hello ,
Thanks for reply.
I am using plant MRP area. For FERT , I am using make to order strategy 20.
I want to specify the real problem. It is like below.
Suppose 'A ' is sumassembly goes to a variant configured MTO KMAT say 'V'.
The same 'A' subassembly is a child for a make to stock FERT say ' S'.
Presently using strtegy 11 for MTS fert 'S' and 10 for the subassembly ---'A'.
Now the planner want to plan for the subassembly.
He is putting the PIR for the subassembly as sales order is not availble and he is putting the PIR for FERT 'S'.
When sales order is coming then additinal quantity planning is happening.
So I suggested to use the strategy 70 for subassembly 'A' , so the sales order (of 'V') OF quantity will be offset for the PIR of the SUBASSEMBLY 'A'.
But the consumption of PIR of 'A' will be apllicable to MTS FERT that is 'S'.
So how can we prevent the system from offsetting the dependent requiremet triggered from the PIR of 'A'.
That means the consumption (that is the usage of stategy 70) of the FERT requirement should only work for ' A' and sales order based KMAT 'V'.
The same offseting should not work for subassembly 'A' and MTS FERT 'S'.
For for Make to order KAMT 'V' , if I use MRP area and do the sales order planning in MRP area. Will I get the desired result ?
Waiting for reply.
Regards,
Ravindra

MRP Area and SA Schedule Lines

Hello All,
We are looking at using MRP Areas and noticed it can not be turned off once on (ECC 5.0). Given that, is the following true with reference to schedule agreements:
- Will seperate schedule lines be created for each MRP Area (same material)?
- Does the receiving storage location come from the material master or the MRP Area (Does it matter if it is a type 01 or type 02 MRP Area)?
- Is it possible to define differen't receiving slocs in a schedule line for a Plant MRP Area?
Thank you,
Jerry

Thank you Charlie,
The link is helpful however it doesn't come straight out and answer the questions - meaning there is a bit of ambiguity there.
It would be appreciated if you or anybody that is using MRP areas with schedule agreements is doing the above.
Regards,
Jerry

Availability check with MRP area at Sloc level

HI We have MRP area at storage location level maintained for materials. Stock exists in the plant in the storage location which is part of the MRP area.
Now when I create STO and try to create delivery for the same, system is giving message 0 stock available and not creating delivery. Material has 02 Avl Chck group.If I deactivate the MRP area in the material master, it allows creation of delivery.
How can I ensure that system creates delivery even though stocks exist in MRP area relevant sloc only in the plant?
Sriram

I am sure you have already moved on from this issue, but what you mention is a limitation prior to ECC 6. You can not identify on the purchasing document the source sloc of the supplying plant. This is why you can not create the STO between sloc MRP areas. I was told this was resolved in ECC 6.
Jon

MRP AREA NETCH indicator missing in planning file entry

Hi,
MRP has been activated at MRP area level storage location level and there were no planning file entries for some materials because we were using the LSMW program RMDATIND for uploading the materials and there was no update flag for Planning File entries. Later we have updated the Direct input session with update Flag.
I already ran the MDAB and MDRE so by the missing planning file entries.
We are running the background job RMMRP000 for the MRP. There are some materials which are not being planned in the background job. When i run the MRP for the same materials in MD02/MD03, the procurement proposals are being created using MD02/MD03.
I checked in MD21, we can see the Planning file entries then there no indicator for NETCH.
What could be the reason?
Regards,
Kumar

hi
take t code-md20
flag required field
regards
gyana

Planning file entry for MRP Area

Hi,
To create planning file entry in the background at plant level we use Transaction MDAB. I would like to know that if MRP area is active than whats the T-code for planning file entry in the background at mrp area level?? To create manualy in the Trx md20 we have that option to select mrp area & plant. So please let me know yours view on this.
Thanks & Regards
Kundan Kumar

Dear,
If planning file entry are there on plant level then system will convert same on MRp area level. Have you check that tables? (DBVM)
For planning file entry at MRP area lvel , use report RMDBVM00 (transaction OM0F) to convert the existing table MDVM with the planning file entries into table DBVM. The conversion is also described in MRP Customizing: TA OPP1 -> Planning File Entries.
There is no need of MDAB just check your entry in MD21 take a MRP run at MRP area lvel and come back if any problem.
If you want to schedule it on MRP area lvel then use the MDRE or use program RMMDVM10 and in variant here select the MRP Area redio button.
Regards,
R.Brahmankar
Edited by: R Brahmankar on Oct 26, 2009 6:25 PM

Creation of new MRP Areas.

Hi All,
While creating new MRP areas am facing problem like "ERROR IN CUSTOMIZING:MRP AREA 1002 IN PLANT 1002 DOES NOT EXIST.
But I am creating MRP areas for another plant-1003.
I didnt understand thatwhy this error is coming and unable to save.
Can any body tell me how to slove this problem.
Thanks
Chindam

dear 2009,
frist create MRP area using SPRO->Prod>MRP>MRP areas-->Define MRP area(SM34)
then come back and activate MRP for created MRP area
sree

Use of report RMMDDIBE for MRP area creation

Dear All
I have this requirement where i have to extend already created materials to storage location MRP areas. In SAP documentation i found that, standard report RMMDDIBE can be used for this.
If anyone has worked with this earlier, kindly let me few things abt this report
1- Exact fucntionality of this report
2. How to run this report
3. Is it a configuration or just front end report which has to be run everytime
4. can we make front end batch job
Any help on this would be great
thanks
bals

Hi Murugesan,
1. Exact fucntionality of this report
The mass create & change MRP Area data instead of manually doing via material master MRP1 view
2. How to run this report
Select the materials and plant that you want to create or change the MRP areas, then select where to copy the MRP area data from, i.e. copy from material master MRP views, copy from other MRP area data.
For example you can copy the material master data when creating, then use "create/change the data" to update some of the fields.
3. Is it a configuration or just front end report which has to be run every time
Yes, you must have configured MRP area and assigned storage locations in the IMG. RMMDDIBE is a mass master data update program, it is not configuration.
4. can we make front end batch job
No real need, this is a mass create/change program.
James

MRP Area tables for MD06 information access like SQ01, DBM logical database

We currently use SQ01 DBM logical database to access MD06 information (tables MDKP and MDTB). The MRP results from the MRP Area are not showing in this query. This implies that the MRP area, MRP results are stored in other tables.
I have reviewed tables (MDLV, MDMA, MDLG, DVER, MDIP) from a similiar thread. However, they do not contain the MRP data (planned orders, stock, production orders ect) like in the DBM logical database.   This data access is very powerfull for exporting planning data for more robust analysis.
Any help is much appreciated.
Thank you

Hi,
       Please try FM: 'AUFBAUEN_MDPSX_ANZEIGEN'.
    MD06 dame come many table.
Example:
(Plant level)
icm61w-fabkl = wk_fabkl.                  :Factory calender
imt61d-matnr = p_matnr.                    : Materials
imt61d-werks = it_tbl-werks.            : Plant
AUFBAUEN_MDPSX_ANZEIGEN 呼出
CALL FUNCTION 'AUFBAUEN_MDPSX_ANZEIGEN'
    EXPORTING
      ecm61w      = icm61w
      ecm61x      = icm61x
      emt61d      = imt61d
      et399d      = it399d
      ECM61B      =
      ESFILT      =
    IMPORTING
      icm61m      = wa_e_cm61m
      imdkp       = wa_e_mdkp
      imdsta      = wa_e_mdsta
    TABLES
      mdpsx       = it_mdps
regards,
   Gaito

BDC for MM02 - MRP area

Hello everyone!
I have developed a BDC program to batch input data into MM02 / MRP area.
It's working perfectly fine when I use mode 'A' in CALL TRANSACTION statement, but when I change it to 'N', so I can give this for the customer to test, it stops working, giving me an error in one of the screens, saying the "MRP area is not assigned to plant CH01" (when running with mode "E" it also gives me the error).
Here's my coding:
REPORT zload_mrp_areas.
Data and variables definition
DATA: bdcdata    LIKE bdcdata OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF t_header OCCURS 0,
        link      LIKE mara-matnr,
        matnr     LIKE mara-matnr,
        werks     LIKE marc-werks,
        mstae(2) TYPE c,
        perkz(2) TYPE c,
      END OF t_header.
DATA: BEGIN OF t_details OCCURS 0,
        muvbr(5) TYPE c,
        unvbr(5) TYPE c,
        matnr     LIKE mara-matnr,
        priod(6) TYPE c,
        gsvbr(5) TYPE c,
      END OF t_details.
DATA: v_count(3) TYPE n,
      v_week      LIKE scal-week,
      v_week1(6) TYPE n,
      v_week2(6) TYPE n,
      v_page(5)   TYPE p DECIMALS 2,
      v_index(3) TYPE n,
      v_field(19) TYPE c,
      v_mode      TYPE c,
      v_date1     LIKE sy-datum,
      v_date2     LIKE sy-datum,
      v_date3     TYPE i.
Screen definition
SELECTION-SCREEN BEGIN OF BLOCK 1 WITH FRAME TITLE text-001.
PARAMETERS: headfile     LIKE rfpdo1-febauszf OBLIGATORY,
            detsfile     LIKE rfpdo1-febauszf OBLIGATORY.
SELECTION-SCREEN END OF BLOCK 1.
File selection
AT SELECTION-SCREEN ON VALUE-REQUEST FOR headfile.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
    EXPORTING
      mask      = ',Multicash,*.txt'
      static    = 'X'
    CHANGING
      file_name = headfile.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR detsfile.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
    EXPORTING
      mask      = ',Multicash,*.txt'
      static    = 'X'
    CHANGING
      file_name = detsfile.
START-OF-SELECTION                                           *
START-OF-SELECTION.
Load files
PERFORM load_files.
PERFORM process_file.
*&      Form LOAD_FILES
      Load files from network to SAP
FORM load_files .
File upload
DATA: l_filename TYPE string.
l_filename = headfile.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename            = l_filename
      filetype            = 'ASC'
    TABLES
      data_tab            = t_header.
IF sy-subrc <> 0.
ENDIF.
l_filename = detsfile.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename            = l_filename
      filetype            = 'ASC'
    TABLES
      data_tab            = t_details.
IF sy-subrc <> 0.
ENDIF.
ENDFORM.                    " LOAD_FILES
*&      Form process_file
      Load files into Material Master
FORM process_file .
LOOP AT t_header.
    REFRESH bdcdata.
    PERFORM bdc_dynpro USING 'SAPLMGMM'        '0060'.
    PERFORM bdc_field   USING 'RMMG1-MATNR'     t_header-matnr.
    PERFORM bdc_field   USING 'BDC_OKCODE'      '/00'.
    PERFORM bdc_dynpro USING 'SAPLMGMM'        '0070'.
    PERFORM bdc_field   USING 'BDC_OKCODE'       '=SELA'.
    PERFORM bdc_dynpro USING 'SAPLMGMM'        '0070'.
    PERFORM bdc_field   USING 'BDC_OKCODE'       '=ENTR'.
    PERFORM bdc_dynpro USING 'SAPLMGMM'        '0080'.
    PERFORM bdc_field   USING 'RMMG1-WERKS'     t_header-werks.
    PERFORM bdc_field   USING 'BDC_OKCODE'      '=ENTR'.
    PERFORM bdc_dynpro USING 'SAPLMGMM'        '4004'.
    PERFORM bdc_field   USING 'BDC_OKCODE'      '=SP12'.
    PERFORM bdc_dynpro USING 'SAPLMGMM'        '4000'.
    PERFORM bdc_field   USING 'BDC_OKCODE'      '=PB42'.
    PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0010'.
   PERFORM bdc_field   USING 'SMDMA-BERID(01)' 'X'.
    PERFORM bdc_field   USING 'BDC_OKCODE'      '=AEND'.
    PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0020'.
    PERFORM bdc_field   USING 'BDC_OKCODE'      '=SP04'.
    CLEAR v_week.
    CALL FUNCTION 'GET_WEEK_INFO_BASED_ON_DATE'
      EXPORTING
        date = sy-datum
      IMPORTING
        week = v_week.
    CALL FUNCTION 'WEEK_GET_FIRST_DAY'
      EXPORTING
        week = v_week
      IMPORTING
        date = v_date1.
    LOOP AT t_details WHERE matnr = t_header-matnr.
      CLEAR: v_week1, v_week2.
      v_week1 = v_week.
      v_week = t_details-priod.
      CALL FUNCTION 'WEEK_GET_FIRST_DAY'
        EXPORTING
          week = v_week
        IMPORTING
          date = v_date2.
      v_date3 = v_date1 - v_date2.
      v_page = v_date3 / 7.
      IF v_page > 11.
        v_index = v_page MOD 11.
        v_page = v_page / 11.
        COMPUTE v_count = TRUNC( v_page ).
      ELSE.
        v_index = v_page.
      ENDIF.
      IF v_index IS INITIAL.
        v_index = 11.
        v_count = v_count - 1.
      ELSE.
        v_index = v_index + 1.
      ENDIF.
Paging
      IF v_count NE 0.
        v_count = v_count + 1.
        DO v_count TIMES.
          PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0020'.
          PERFORM bdc_field   USING 'BDC_OKCODE'      '=P-'.
        ENDDO.
        PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0020'.
        PERFORM bdc_field   USING 'BDC_OKCODE'      '=P++'.
        v_count = v_count - 1.
        DO v_count TIMES.
          PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0020'.
          PERFORM bdc_field   USING 'BDC_OKCODE'      '=P-'.
        ENDDO.
      ENDIF.
      PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0020'.
      v_field = 'RM03M_DB-KOVBW(*)'.
      REPLACE '*' WITH v_index INTO v_field.
      PERFORM bdc_field   USING v_field     t_details-muvbr.
      v_field = 'RM03M_DB-VBWRT(*)'.
      REPLACE '*' WITH v_index INTO v_field.
      PERFORM bdc_field   USING v_field     t_details-unvbr.
     PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0020'.
      PERFORM bdc_field   USING 'BDC_OKCODE'      '=WEIT'.
      PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0020'.
      PERFORM bdc_field   USING 'BDC_OKCODE'      '/00'.
      PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0020'.
      PERFORM bdc_field   USING 'BDC_OKCODE'      '=P++'.
    ENDLOOP.
    PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0020'.
    PERFORM bdc_field   USING 'BDC_OKCODE'      '=UEBE'.
    PERFORM bdc_dynpro USING 'SAPLMD_MGD1'     '0010'.
    PERFORM bdc_field   USING 'BDC_OKCODE'      '=UEBE'.
    PERFORM bdc_dynpro USING 'SAPLMGMM'        '4000'.
    PERFORM bdc_field   USING 'BDC_OKCODE'      '=BU'.
    DATA: ITAB TYPE TABLE OF BDCMSGCOLL.
    v_mode = 'N'.
    CALL TRANSACTION 'MM02' USING bdcdata
                   MODE   v_mode
                   UPDATE 'S'
                   MESSAGES INTO ITAB.
    if sy-subrc is initial.
    endif.
ENDLOOP.
ENDFORM.                    " process_file
*&      Form BDC_DYNPRO
      text
FORM bdc_dynpro USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro   = dynpro.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
ENDFORM.                    "BDC_DYNPRO
*&      Form BDC_FIELD
FORM bdc_field USING fnam fval.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDFORM.                    "BDC_FIELD
Can anyone help? Please!
Thanks and regards,
Fernanda

You are trying to access one of the MRP area which is not yet assigned to CH01 plant. You need to make sure wheather the MRP view was already created for that material for CH01 plant.
So, first check your data against the MARC for material and plant. If you don't fine any material for that plant than don't run BDC for that plant.
Regards,
Naimesh Patel

MD04 - Subreq - Storage location MRP area

Hi all,
I have an issue of Subreq in MD04 which is not assigned to the the good MRP area.
I'm explaining :
Business process
   -> I work with a subcontractor
        case 1 : either I buy raw material to be processed and delivered it directly to my subcontractor
        case 2 : either I send raw material from my physical stock to my subcontractor
   -> I create subcontracting purchase order with indication as components, the raw material.
   -> In case of the components are already in my subcontractor (case 1), the reservation (Subreq) should not consume my physical stock.
   -> In case of the components are in my physical stock (case 2), the reservation (Subreq) should consume the physical stock.
Solution choosen
Then I decided to create a storage location MRP area : "EXTERN" as External.
I assigned a storage location "EXT" to this MRP area.
I assigned this MRP area to the material in MRP1 / MRP Area.
In the purchase order, in the components popup,
For case 1 : I assigned "EXT" as Prod.Stor.Loc and Supply area
For case 2 : nothing special is filled
Issue
For the case 1, althought I assigned the storage location "EXT", the Subcontractor Requirement is not attached to the good MRP area.
WHY?
Remark : I didn't use the subcontracting MRP area because I would like to have 2 cases : case 1 & case 2.
Thank you in advance for your help about this problem which make me nervous !

Hello Catherine
Your system is working as designed. The following note explains the system design in more detail:
503497 - Subcontracting and MRP areas
Take a look on the relevant information provided by this note below:
Reason and Prerequisites
The most important point to understand the system behavior is the fact that the withdrawal of the (subcontracting) component is generally carried out during the goods receipt for an SC procurement proposalfrom the subcontractor stock that is managed at plant level from an inventory management point of view and that has no reference to a storage location at all.
This causes that subcontractor requirements can never enter a storage location MRP area, since you can later not post the withdrawal from this MRP area.
Thus SC-requirements always enter the SC segment of the plant MRP area or the SC-MRP area.
The SC MRP area in turn is supplied by stock transfer reservations from the plant MRP area or via third-party order processing through procurement proposals with goods receipt directly to the subcontractor. A supply through the materials planning from a storage location MRP area is not possible.
For the above reason, SC-requirements do also not carry any storage location, since the storage location does not have any control function at all for SC-requirements:
You cannot and you should not determine a storage location MRP area (see above), and the subcontractor MRP area is determined via the vendor of the procurement proposal, thus it is independent of the storage location.
See also Note 376050 on this topic that makes a modification available which prevents the deletion of the storage location in the subcontractor requirements, so that you can use, for example, customer-specific reports to analyze the storage location.
Please observe that the mentioned modification note 376050 only makes the storage location available on table RESB, so that you can use it on custom report. This modification will not make the storage location to be considered by MRP or on MD04.
BR
Caetano

MRP Area Clarification

Similar Messages

Maybe you are looking for