Query related to RM maintained for two MRP areas.

Hi PP Gurus,
The scenario is we modeled two Storage location MRP Areas say 1001 and 2001. There are two FG getting manufactured at them, say FG-1 at 1001 and FG-2 at 2001. Say there are three RMs viz. RM-1, RM-2, and RM-3. RM-1 and RM-2 included in FG-1 BOM and RM-3 and RM-2 in FG-2 BOM. Means RM-2 is common in both MRP areas.
Now I've extended FG-1 and FG-2 for respected MRP areas. RM-1 extended to MRP area 1001, and in MRP views of material master, Production storage location and Storage location for EP is maintained as 1001. Same is maintained for RM-3 except MRP area as 1001, it's 2001.
The concern is about RM-2, though I extended RM-2 for both MRP areas i.e. 1001 and 2001 but I can maintain Production storage location and Storage location for EP either as 1001 or 2001. So whenever I'm taking MRP run, for RM-2 it's either proposing 1001 or 2001 as Storage location for withdrawl or EP.
My requirement is when I run MRP for FG-1 system should show me Sloc for RM-2 as 1001 and in case of FG-2 as 2001.
As a try I tried to remove Production and Issue Sloc from MRP views and maintained Issue Sloc/Receive Sloc in PV of FG-1 and FG-2 but still unable to get the requirement fulfil.
Please make prompt comments
Thanks & Regards,
Abu Arbab

Dear ALL
my requirement is exactly same as above that i need my component to be issued from different slocs depending on diffreent MRP areas in which they are being planned.
But in my case FG is same and is being planned in 2 different MRP areas. So my BOM is same in both cases.
For eaxmple--2000 is MRP area 1 and 3000 is MRP area 2
Requirement is components should be issued from 2000 when panned in 2000 and from 3000 when planned in FG is planned in 3000.
Kindly let me know what settings are required at components level to do this
thanks

Similar Messages

Creating Planned Independent Requirements for an MRP Area.

Hi All,
I am trying to enter Planned Independent Requirements for an MRP Area, with requirement type VSE and I get the following error;
"Only stock requirements are allowed when planning at MRP area level".
I can enter at the Plant level with no problems.
Any guidance is greatly appreciated.
Kevin.

The following is the excerpt from SAP [Help|http://help.sap.com/saphelp_470/helpdata/en/81/470a58ddab11d1b55b0000e82de178/frameset.htm] I think you maintained a planning strategy in the MRP view (for the plant) which doesn't support VSE.
You can delete PIRs from an MRP area by deleting the MRP area number from the Creating Planned Independent Requirements screen and recompiling.
When you define the planning strategies and parameters in the material master, these parameters apply to the whole plant, including all the MRP areas within the plant: You cannot maintain the MRP areas separately.
The integration of the MRP area and the assignment of the MRP area in the sales order is supported only by a user exit in the sales and distribution user exit pool.
Sales orders with MRP areas are created irrespective of the availability check control group in the material master.
Customer order processing of production sales orders with the item category (account assignment Step E Single) is only maintained in the MRP area of the plant.
In Customizing and in the MRP area user exit, make sure that when transferring individual sales orders, only requirements types KE, KEK, KEKS, KET, KELV, KEV, KEVV, VSEF, and VSE are generated.
The following requirements types are valid for the MRP area: KE, KEK, KEKS, KET, KELV, KEV, KEVV, VSEF, and VSE.
You cannot plan with preliminary planning materials in the MRP area.
There is no planning strategy for the material segment of the MRP area.
The planning strategy for the material master segment of the plant is assigned to the material segment of the MRP area.
The consumption mode and the periods of adjustment are derived from the plant in the MRP area of the material master.
Only consumption customer requirements with planned independent requirements are allowed: VSF requirements with KSV and VSFB with KSV.

Any Prerequisite for adding MRP Area?

Hi Gurus,
I need to add MRP area data to a large number of materials. I tried testing for some material . For some materials I am able to add the data. For other I am not able to add.
Is there any prerequisite for adding MRP area to a material?
Can some suggest any BAPI to add/ update MRP area for a material?
I am basically a ABAPer and don't have much Idea about MRP area. Please suggest any link where I can learn overview about MRP area.
Thanks in Advance,
KG

hi,
the prerequisities for MRP area are
1> ACTIVATE MRP AREA
2> DEFINE MRP AREAS.u will find the settings under the menu path:
SPRO > IMG > MATERIAL MANAGEMENT > CONSUMPTION BASED PLANNING > MASTER DATA > MRP AREAS
or u can find it under the menu path:
SPRO > IMG > PRODUCTION > MATERIAL REQUIREMENT PLANNING > MASTER DATA > MRP AREAS.
regards
jash
Edited by: diptasya jash on Apr 30, 2009 11:35 AM

MRP areas--Component To be issues for different MRP areas

Dear All
I have this scenario for MRP areas--- MRP area 2000 and 3000..these areas are basically 2 separate physical production facitilties...One is main production plant and other is lab for making samples.... But they store the raw material stock seprately..stock for raw material for main production is in main warehouse 2000 and stock for samples lab in in their mini warehosuese 3000.
Busniess wants to consume stock from main production warehosue when doing main production and to consume stock from samples warehosue when doing samples production. BUT header item is same and raw materials are also same. Means the same BOM.
Example-- FG1 and it has RM1 and RM2 in BOM
Kindly help to do settings\configuration somehow that when we do production in 2000, compoenent are comsumed from 2000 and when we do production in 3000, components from 3000.
I extended FG on both MRP areas. even for RM1 anf RM2, i extended it on both MRP areas. So in MRP2 view prodcution stprage location is 2000 and with MRP area MRP 2 view production storage location is 3000.
It did not work.
Kindlt sugget

Hi,
What you need is a way to determine the proper issue storage location for the two cases.
Since, as you say, the BOM is the same, you need to use production versions. In the definition of the production version you can control the issue storage location for the components of the order.
All you need then is to choose the right production version for each case when you create the order.
Regards,
Mario

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

Reports for two costing Area With one operating concern

Hi,
What are the reports I can get if I am having two different costing area for my comapnies with same operating concern
Thanks in advance for your input
CHEERS

Thanks Sreekanth ,
I want to what are the reports that will be generated. And what cannot be done if we have two controlling area instead of one.
CHEERS

Single Invoice for two sales areas

Hello SAP Gurus,
I have a scenario that Iu2019ll appreciate if a solution could be proffered
Contractually, a customer requires materials from a company (company code), and these materials will be sold from 2 or more sales areas within the company code. However, a single invoice, which will list the items and their individual prices, is what is required to be given the customer. What solution can I use to resolve this?
Thanks

Hi luqmon
Say you have material - MAT1 ; Customer - 1000 ; 1st sales area is - 1000/10/10 ; 2nd sales area - 2000/20/20
So make sure that the material MAT1 is available in both sales areas
Even customer (KUNNR) is also available in both sales areas . If you have created in 1st sales area then extended it to 2nd sales area.
Maintain same pricing procedure for both sales areas in OVKK
Maintain a access sequence with the key combination Sales orgn / material . and assign the access sequnece to the Pricing (PR00) condition type
Now Maintain the condition record for the material MAT1 in VK11 , with the key combination of sales orgn / material
Now when you create the sales order and do delivery , PGI and when you do billing then you can see the price of the material maintained in that VK11 based on sales orgn
But yours can be solved either with a LIS report also
Regards
Srinath

Creating a Production Order for a MRP area

Hi All
I have activated MRP area and has created 2 MRP area's. When I create a production order, always the first MRP area is assigned in the production Order.
Please help me to understand how do we create a Production order for a particular MRP area.
Thanks
Tom

Sorry guys, the question was not correct.

A query related to creating Indexes for a table

Hi ,
I am in a J2EE Banking Project using Oracle 10g as our Database .
We have created Indexes on some tables .
But this this is not called by any of our Java class .
Could anybody please let me know how these Indexes will actually improve the Performance .
Waiting for your replies .
Thanks in advance .

But in our safety database (huge & ofcourse Oracle), we use indexes just because to avoid duplicates, improve data retrieval and so on.As you pointed out indexes can do 2 things for you: enforce uniqueness and (hopefully) improve data retrieval. Enforcing uniqueness is pretty basic, but indexes don't always improve performance. Under the wrong condtions indexes can hurt performance. The ideas below refer to B-TREE indexes; other kinds of indexes have other considerations
Indexes add overhead to insert, delete, and (hopefully not - updating index columns is a Bad Idea), enough so that if you're inserting a lot of rows into a large table it is sometimes helpful to drop the indexes, load the data, and recreate the indexes when done to help performance. The more indexes a table has the more overhead DML statements need to maintain them.
Indexes help query performance under a couple of conditions. When using them as join keys to retrieve a small percentage of rows in a table (< 20% maybe; there is no firm number) indexes can help. When a query can read its columns from an index only (such as counts against a primary key index) index access can be faster than table access.
Indexes can hurt performance by adding overhead for maintenance if the index is never actually used or if used to read most of the rows in a table when a full table scan would be more efficient (why go through the extra effort to read the index and then table when you'll have to read most of the rows in the table anyway?).

In scope of planning ( md01), How to maintain MRP areas in scope of plg?

Hello PP members,
In scope of planning ( md01), How to maintain plant or MRP areas in scope of planning ?
What is the transaction code for maintaining plants or MRP areas in the scope of planning
I tried transaction code SAMP, Also went to SE93( Maintain transaction) for any related transaction codes for maintaining plants in scope of planning, it wasn't much help
Thanks for your time,
Thanks Again,
Suren R

Hi,
we can use Total planning(MD01) for a single plant or use scope of planning to control whether total planning is to be carried out for single plant/sevaral plant/ for one MRP Area/sevaral MRP areas/ combination of plant and MRP Areas.
Steps :
1.Group together the plants which are to be planned in spro in --->Define scope of planning.(OM0E)
2. Define the scope of planning as 999 for ex and give description.
2. Now select that and Specify the sequence in which Plants and MRP Areas are to be planned,
3.Goto new entries and enter the plant as 1000/MRP Area as 1000 with counter 1 and plant as 1100 with counter 2 and save.
4.Execute the total planning either as online job or as background job.
5.The planning run has to be always started with paralle processing.
In SPRO in define parallel processing in MRP enter the destination for parallel processing for ex your server name and enter the no .of sessions as 1 and save.
6.Tcode MD01 enter the scope of planning group and selet the parallel processing and enter.
7. All the materials to be planned in the plant / mrp area will be planned now.
Regards,
nandha

MRP Area query

Dear All
Client is having a trading plant which has almost 50000 materials approximately or more. Each Material has two MRP Areas already present in the system but due to some issue client wants to remove or delete one MRP Area and keep other MRP Area only for all materials .However but if MRP Area is deleted Client doesn't want stocks,Sales order, Purchase order of the deleted area to be affected they should be closed in that area only and Other MRP Area is to be used effectively?
Please suggest

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

How to run MRP only for MRP area ?

Dear Gurus,
I am going to run collective MRP only for one MRP area, not for whole plant. How to do it?
MD03----is only for one material.
MD01----is at plant level
Thanks in anticipation.
Jason
Edited by: Jason Ma on May 6, 2008 4:44 PM

Can you be more specific?
MD21 - Display Planning File Entries? Is this related to MRP run and how?

Mass change of Reorder point on MRP areas for materials

Hi,
Is there any process to upload mass change of reorder point on MRP areas for materials.
Please suggest.
Thanks in advance.

Hi Pavithra,
I know this is an old thread and my answer may not be relevant to you anymore but maybe it will help others. Are you trying to do a mass change for the reorder points of the MRP Areas? If so, go to tcode SA38, then run program RMMDDIBE. Then go to create/change with Data tab. Select change MRP area and there you can change the reorder points for your MRP areas.
Regards,
Chester

Sap pp -MRP-area

Hello SAP-Guruu2019s
Pls tell me the Procedure/steps/Details to maintain MRP-area for a Vendor & also for a Sub-Contractor.
Any comments welcome & Thanks in advanc

Hi,
Pls. find the following details regarding MRP Area :
MRP Area
Definition
The MRP area represents an organizational unit for which material requirements planning is carried out independently.
Basically, there are three types of MRP area:
Plant MRP Area
The plant MRP area initially contains the plant together with all its storage locations and stock with subcontractors.
When you have defined MRP areas for storage locations and for subcontractors and you have assigned the materials, the plant MRP area is reduced by exactly this number of subcontractors and storage locations. This is because they are now to be planned separately.
MRP Areas for Storage Locations
You can define an MRP area that consists of a particular storage location, by creating an MRP area and assigning the storage location to it. Material requirements for this storage location are then planned separately from the rest of the plant.
You can also group several storage locations into one MRP area, by creating an MRP area and assigning the storage locations to it. These storage locations are then planned together.
A storage location of a plant may be assigned to only one MRP area.
MRP Areas for Subcontractors
You can also define an MRP area for each subcontractor.
A subcontractor may be assigned to only one MRP area. An MRP area of the subcontractor type may also only contain one subcontractor.
Use
You can carry out MRP specifically for the determined MRP areas. This enables you to carry out differentiated material requirements planning. The requester can be, for example, the production on a particular assembly line or a subcontract order.
The MRP area allows you to have specific control over the staging and procurement of important parts produced in-house and purchased parts for each shop floor area. You can, however, also plan the provision of components for the individual subcontractors.
MRP areas of the storage location or subcontractor type are only suitable for:
components that are planned and produced for stock
finished products that are planned and produced for stock. By assigning a storage location in a sales order or by entering an MRP area when creating the planned independent requirements, you can define whether a material is planned in the plant MRP area or in the MRP area of the storage location.
Finished products and important assemblies intended for make-to-order or engineer-to-order production are always planned in the plant MRP area.
The planning run takes into account the planning with MRP areas as follows:
If you do not enter a separate scope of planning, the system plans the whole plant, that is, all MRP areas in the plant, during the total planning run. If you want to carry out a total planning run for a particular MRP area only, you must specify the required MRP area in the scope of planning.
During single-item, multi-level planning, the system plans the selected material in the MRP area entered. In addition, the system takes into account planning file entries from other MRP areas, for example, if the material is to be procured using stock transfer.
During single-item, single-level planning, the system plans the selected material in the MRP area entered only.
Structure
You define the MRP areas in Customizing for MRP. You can thereby assign the following to an MRP area:
one or more storage locations (example: you want to carry out planning for a particular assembly line and therefore assign a production storage location to the MRP area)
a subcontractor.
You assign the various MRP areas to the materials in the material master. For this, you create an MRP area segment for a material for every MRP area, in which it is used. In this MRP area segment, you can define MRP parameters such as, for example, the lot size or MRP type. This allows you to plan the material differently in the MRP area from how you plan it in the plant MRP area.
MRP with MRP areas for the material is not activated until the material has been assigned to an MRP area. If you have not assigned a material to an MRP area, that is, you have not created an MRP area segment in the material master, the material will continue to be planned in the plant MRP area only. If you have assigned an MRP area to it, the system can plan it in the plant MRP area and in the assigned MRP area.
Integration
You can carry out material requirements planning for MRP areas using all MRP procedures and all lot-sizing procedures.
You can also carry out an independent material forecast for MRP areas using your own parameters.
The material consumption values are updated separately for each MRP area.
A separate ATP check is carried out for each MRP area.
If several storage locations belong to an MRP area, the system can also carry out a check at two levels, that is, at storage location level and at MRP area level.
Example: Subcontractor
You can also carry out planning for components to be provided in subcontracting using an MRP area by defining an MRP area for every subcontractor and assigning the components to be provided to the MRP area of the subcontractor. You therefore plan the requirements to be provided for these components for one subcontractor separately from all other requirements (see Planning for Components to be Provided in Subcontracting).
Depending on the requirements situation, the system creates either stock transfer reservations from the plant to the stock of material provided of the subcontractor or it creates purchase requisitions within subcontracting/third-party order processing, according to the special procurement key settings.
Implementing MRP Areas
Implementation Options
The main reason for you to implement MRP areas is if you would like to plan materials, which are required in different shop floor areas, storage locations or by subcontractors, separately from one another.
As soon as you have activated materials requirements planning with MRP areas, this type of MRP is active at client level, that is, MRP will be carried out in this way in all plants.
Material requirements planning with MRP areas cannot be reversed.
Process Flow
You can implement material requirements planning with MRP areas in three steps:
You convert the existing planning file entries at plant level to planning file entries at MRP area level.
During the conversion, the system creates a plant MRP area for every plant as a background job. This, however, will not affect your planning. The processes in material requirements planning and the planning results remain unaffected.
The conversion is also useful even if you do not work with MRP areas, but still have to plan for several plants, as the new planning file improves system performance during the planning run.
You activate MRP with MRP areas in Customizing for MRP. This causes the MRP area field to appear in the applications of MRP and in related areas. When you enter the plant number, the system automatically fills the field with the number of the plant MRP area. The number of the plant MRP area is the same as the plant number.
This does not affect the planning run as the plant MRP area still corresponds to the present plant.
You define an MRP area, for example, for a storage location. You then assign the materials that are to be planned for this storage location, by creating an MRP area segment in the material master.
Materials requirement planning for this storage location is then carried out separately. The storage location stock is no longer included in the available stock of the plant MRP area. The receipt and issue elements of this storage location (MRP area) are also not taken into account in the plant MRP area. They are only taken into account in the MRP area of the storage location.
If you have already worked with storage location MRP the system still carries out storage location MRP even after the activation of MRP areas. You need to decide in principle whether you want to continue using storage location MRP or whether you want to create MRP areas for the storage locations that are planned separately. It is not possible to simultaneously plan a material using storage location MRP and an MRP area for the same storage location.
If you decide to use MRP areas, you should then try to convert all storage locations that are planned separately to MRP areas in one step. Before you assign the material to an MRP area, you must remove the MRP indicator, which is located in the material master at the storage location organizational level (view MRP 4) in the screen area Storage location MRP.
Even if you have defined MRP areas in Customizing, the system plans the materials in the plant MRP area until you assign the MRP areas to the materials.
Only the assignment of one or more MRP areas to a material, by creating MRP area segments in the material master, actually cause changes in the material requirements planning.
Hope this helps.
Regards,
Tejas

Subcontract MRP Area with quota usage - urgent

We have a subcontractor supplying assembly X which in turn require us to supply component Y to the subcontractor. We have two vendor for supplying component Y to subcontractor. Scheduling agreement with component vendors are set up for direct delivery to subcontractor. Both the scheduling agreements are included in the source list with MRP indicator 2. Quota arrangement is set up for the component.
We have set subcontractor MRP area and assigned the same to component Y material master. Special procurement key 20 is assigned in subcontractor MRP area. Quota usage and source list are duly enabled. Quota usage indicator is 3 which provides for MRP, PR, schedule line etc.,
When we run MRP ffor component Y for subcontract MRP area, system is generating schedule line for but without update quota file. Further, the scheduling agreement picked up is not of the correct vendor as per Quota logic.
Does SAP support quota usage with subcontract MRP area. If not, is there a work around.
Shall appreciate urgent response

Dear Ravi,
you will get a seperate location product for your material. MRP areas in apo are represented by a seperate location (type 1007 = storage location mrp area). You can transfer your ecc mrp areas via cif (CFM1). The master data you maintain in mrp section of the material master in R/3 will be trasfered to that location product. Furthermore you can maintain it manually in apo MAT1 (location = name of your mrp area). That technique provides you the possibility to maintain different parameters for the plant and the mrp area.
Kind regards,
Christian

Query related to RM maintained for two MRP areas.

Similar Messages

Maybe you are looking for