Sales Requirnment in MRP Area

greetings
i have Created Two raw material (trading ) .
In material master MRP views..i used MRP area (Respective Seting Done in SPRO).
Now i created sales order for the Two items......now if i see MD04..i m getting requirenment but not with MRP area..
I m using strategy as 40.
What seting or correction i have to do to see the Sales Order requirenment under MRP area.
Edited by: SAP PP on May 19, 2009 9:39 AM

1) Convert planning file entries - you must first convert the existing planning file entries at plant level to MRP area level in the planning file (OM0F)
2) Activate MRP for MRP areas (Production ->MRP -> Master Data -> MRP areas -> Activate MRP for MRP areas)
3) Define MRP areas
4) Assign material to MRP areas in Material master MRP1 view
The allocation to a storage location MRP area is made using the storage location that the system determines during the planning run. This is determined on the basis of the storage location entered in the BOM (BOM item), in the work center (production supply area), or in the production version or in the material master. This storage location must be included in the MRP area that you have assigned in the material master. In addition, it is necessary that the view "Storage 1" or "Storage 2" exists for this storage location in the material master.
Sales orders are assigned to a MRP area depending on their storage location (the issue storage location in the shipping screen of the item details).

Similar Messages

Sales Plan At MRP area level

Dear All,
is it possible to maintain sales plan on MRP level? if yes How.
or if I will enter sales plan on Plant level can i tranfer to demand management on MRP area level if yes how?
Regards,
Ahmed sobhi

Hi,
Please elaborate your query.
You must have gone to SE37 transaction to check this function module and you must have checked the import parameters on the the import tab.
When we call this fiunction module in Z program, we need to ensure that data is supplied so that import parameters are taken and data is updated in MDMA table.
Regards
Datta

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.

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 Wise Run for Sales Requirenment

Greetings..
I have two raw material (Trading).....in MRP view i defines these material under MRP area ...(Respective setting done in SPRO)
Now i created sales order for these Raw material .
Now in MD04 ...i m getting requirement but under plant....if i choose MRP area i m not getting Requirement...so if i try MD01 ...under MRP i m not getting Result of MRP..
I need two Run MRP only for MRP area which assigned to Raw material in Material Master
i m using Startegy 40..
What else setting i have to do for getting Run with MRP area (MD01)

1) Convert planning file entries - you must first convert the existing planning file entries at plant level to MRP area level in the planning file (OM0F)
2) Activate MRP for MRP areas (Production ->MRP -> Master Data -> MRP areas -> Activate MRP for MRP areas)
3) Define MRP areas
4) Assign material to MRP areas in Material master MRP1 view
The allocation to a storage location MRP area is made using the storage location that the system determines during the planning run. This is determined on the basis of the storage location entered in the BOM (BOM item), in the work center (production supply area), or in the production version or in the material master. This storage location must be included in the MRP area that you have assigned in the material master. In addition, it is necessary that the view "Storage 1" or "Storage 2" exists for this storage location in the material master.
Sales orders are assigned to a MRP area depending on their storage location (the issue storage location in the shipping screen of the item details).

MRP Areas in Flexible Planning?

Hi,
we are in the process of evaluating different planning tools for our long term planning. And I guess we have two options: APO-DP and Flexible Planning in ECC. We are a non manufacturing (government) organisation and want to try to forecast/plan future demand and requirements. We are getting our demands from maintenance orders and cost center consumption. Reqs are in the form of components on maintenance orders and STO's between storage locations in different MRP areas.
Is it possible to do flexible planning and taking mrp areas into account. Will it be possible to forecast future demands on Plant and MRP area level. Mind we are not selling anything through sales order, so we are not actively using SD org structure.
Best regards,
Kenneth

Dear,
APO-DP Vs Flexible Planning in ECC. Yes APO advance but ECC is more user friendly.
The master data is managed in R/3 and transferred to APO using CIF. An issue storage location is maintained in the R/3 production version. This issue storage location is assigned to an MRP area in R/3. This MRP area is contained in the integration model (transaction CFM1). The MRP area is therefore transferred to APO. The APO plan (PPM or PDS) is created in APO in the MRP area. Using this plan, a planned order is created in the MRP area location in APO.
If you want the R/3 behavior, you must not assign the component to the model in the MRP area location. The system will then automatically switch to the plant location, that is, the system then uses the plant location as the issuing location of the component in MRP area.
Hope it will solve your problem. Also refer the OSS Note 628739 - APO 3.x Release restrictions for MRP areas
Regards,
R.Brahmankar

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

MRP Area Setting

Hi, expert
I have the following scenario:
I got a transit sloc 1510 where goods will be backflush to this location first, then use mvt 311 to transfer to 1530 (fg whse) and 1520 (fg whse), and we want to seperate the material planning for 1530 and 1520.
So, we use MRP area to do this:
I set up 2 storage location MRP area: 1530, 1520
sloc 1530 assigned to MRP area 1530, rec loc 1530
sloc 1520 assigned to MRP area 1520, rec loc 1520
Item A MRP4 setting:
Production Version: Issue storage location: 1910, rec sloc: 1510
Already assigned MRP area 1530 to this item A
I created a sales order for ITEM A, in sales order, I specific the sloc 1530. Then I run MD02 using MRP area 1530. When I view the result in MD04, the rec loc for plan order is 1530 instead of 1510 (seems like MRP 4 production version setting is ignored).
I try to add sloc 1510 in MRP area 1530 in SPRO, and then run MD04, the planned order rec loc becomes 1510, and this is what I want. But the problem is when I assign 1510 to MRP area 1520, system prompt error that 1510 already assign to other MRP area, it seems that only 1 sloc can be assigned to 1 MRP area, but based on my scenario, both 1520 and 1530 sharing 1 transit loc 1510, and I want the planning to be diff for 1520 and 1530, how should I proceed? how to configure MRP area?

I only want to have 1 transit sloc 1510, all the goods will backflush to this sloc first, then later distribute to diff sloc. If follow what you said, I need to create multiple dummy storage location for each MRP area, If I have 8 MRP area, means 8 dummy sloc need to be created, this is not very practical and very hard to maintain.
Any better suggestion?

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

No sales orders with MRP-relevant requirements were found MD04

Hello MM Enthusiast,
We are in process of EHP upgradation and I need to replicate the following error message,
No sales orders with MRP-relevant requirements were found
Error message MF 336
Please let me know how to get the above message in S environment.
I have gone through the already discussed thread (http://scn.sap.com/thread/3460655) but couldn't able to get the message MF 336.
Based on your response I can replicate and apply the causing / resolving note given by SAP AG.
Looking forward to your valuable input to proceed further on this issue
Cheers,
Kumar S

This issue was solved using a different availability checking rule in MRP3 of the material master.
the old checking rule had a requirements summary, while the new was for individual requirements, this setting is defined in OVZ2 customizing transaction.
Hence you need to enter a checking rule in your material master which has a A as sales requirement in OVZ2.
then create 2 or more new sales orders for this item for the same delivery date.
After that you should get the error in MD04

PIR' s are consuming in Stock transfer between slocs under same MRP area

We are using Sloc to Sloc with PO /delivery/asn/pgr route These SLOCS belong to same MRP area
Materials that are having strategy group 40
PIR's are conumed once PGI is done .
How to restrict this
Please throw me some light

i am not saying to stop the consumption by sales order.
try to map a different delivery type in case of such stock transfer as you explained process at your end. and for that try to wrok that way. i think you i have done misttake by saying requirement class as that comes in SO not delivery. in your case the PIR reudction is due to movement type. please movement type config in OMJJ (it might have PIR reduction active.
go thorugh not 896518
please check the movement type getting called in this GI case, and try to create a new mvmt type map this inplace of standard one with config and on that movement type remove the indicator "indepenet requirement reduction"
Regards,
Pravin Mukkawar
TCS canada
Edited by: pravin mukkawar on Mar 25, 2010 7:06 PM

MRP Area issue

Hi Experts,
I have the following business scenario. My sales order are created based on contracts. After I activate my MRP area functionality, notice that my MRP run was not working anymore. After making some analysis I noitce that my Sales Order are being created with some MRP area that can be checked on the availability check on the sales order VA03 transaction.
It seems that this MRP area is coming now from the contract, the fact is that I cannot understand why this kind of behavior, since the material is not activated by MRP area and since the MRP area is different from the plant, then the MRP run did not work.
Please, could anyone help me on that?
Kind regards
Oliver F

Hi
Kindly check your settings from the following link
http://www.sap123.com/showthread.php?t=57
Thanks

BAPI   for    MRP AREA

I create material using bapi BAPI_MATERIAL_SAVEDATA
in VIEW MRP1    it need to use the button 'mrp area' to inut the mrp area
double click and inout mrp type , mrp controller .....
is there anyone konw   the bapi to do it ?
many thanks!!

BAPI_MATERIAL_SAVEDATA field MARA-KZKFG not in ClientData
if its not in BAPI_MARA then you have to use ExtensionIn table to populate this field.
In Extensionin Table you have to enter the following two fields
structure name "BAPI_TE_MARA" and
the values for all the fields in this structure in valuepart1 field.
matnr (18), zfield1(10), zfield2(10)
Then it_extensionin-valuepart1 should have matnr in the first 18 char's and then zfield1 in the next 10 chars and zfield2 in the next 10 chars. so you should have filled the first 38 chars of valuepart1. In your case you dont need is_bapi_te_mara
you can just say
it_extensionin-valuepart1+0(18) = matnr.
it_extensionin_valuepart1+18(10) = zfield1
it_extensionin_valuepart1+28(10) = zfield2
append.
it should be something like this. Please try this and let me know if you still face any problems. Let me know the structure of bapi_te_mara.
BAPI_TE_MARA looks like the following;
MATERIAL MATNR CHAR 18 0
.APPEND ZABAPI_TE_MARA 0 0 Missing fields fo
EXTWG EXTWG CHAR 18 0 Ext
ZZLSTATION1 ZLSTATION1 CHAR 13 0 Line
ZZLFEEDER1 ZLFEEDER1 CHAR 12 0 Line
FUNCTION z_mmc_local_material_create.
""Local interface:
*" IMPORTING
*" VALUE(SINGLE) TYPE CHAR1
*" VALUE(IV_UNAME) TYPE SYUNAME OPTIONAL
*" EXPORTING
*" VALUE(MESSAGE) TYPE ZCHAR150
*" TABLES
*" MATDATA STRUCTURE ZMMCLOCMM
*" EXCEPTIONS
*" ERROR
TABLES: zmmcuser. "DG28347E
TYPE-POOLS shlp.
Tables
TABLES: t9mmclocmm,
t9mmcuser,
t100,
z19ppl_mm_dat,
t134t,
t9mmclocmt,
z19sloccon.
Strutures and internal tables
DATA: is_headdata LIKE bapimathead,
is_clientdata LIKE bapi_mara,
is_clientdatax LIKE bapi_marax,
is_plantdata LIKE bapi_marc,
is_plantdatax LIKE bapi_marcx,
is_forecastparameters LIKE bapi_mpop,
is_forecastparametersx LIKE bapi_mpopx,
is_planningdata LIKE bapi_mpgd,
is_planningdatax LIKE bapi_mpgdx,
is_storagelocationdata LIKE bapi_mard,
is_storagelocationdatax LIKE bapi_mardx,
is_valuationdata LIKE bapi_mbew,
is_valuationdatax LIKE bapi_mbewx,
is_warehousenumberdata LIKE bapi_mlgn,
is_warehousenumberdatax LIKE bapi_mlgnx,
is_salesdata LIKE bapi_mvke,
is_salesdatax LIKE bapi_mvkex,
is_storagetypedata LIKE bapi_mlgt,
is_storagetypedatax LIKE bapi_mlgtx,
is_return LIKE bapiret2,
is_bapi_te_mara LIKE bapi_te_mara,
is_bapi_te_marax LIKE bapi_te_marax,
it_materialdescription LIKE bapi_makt
OCCURS 0
WITH HEADER LINE,
it_unitsofmeasure LIKE bapi_marm
OCCURS 0
WITH HEADER LINE,
it_unitsofmeasurex LIKE bapi_marmx
OCCURS 0
WITH HEADER LINE,
it_internationalartnos LIKE bapi_mean
OCCURS 0
WITH HEADER LINE,
it_materiallongtext LIKE bapi_mltx
OCCURS 0
WITH HEADER LINE,
it_taxclassifications LIKE bapi_mlan
OCCURS 0
WITH HEADER LINE,
it_returnmessages LIKE bapi_matreturn2
OCCURS 0
WITH HEADER LINE,
it_prtdata LIKE bapi_mfhm
OCCURS 0
WITH HEADER LINE,
it_prtdatax LIKE bapi_mfhmx
OCCURS 0
WITH HEADER LINE,
it_extensionin LIKE bapiparex
OCCURS 0
WITH HEADER LINE,
it_extensioninx LIKE bapiparexx
OCCURS 0
WITH HEADER LINE.
DATA: BEGIN OF it_error OCCURS 0,
uname LIKE t9mmcuser-uname,
cltprt LIKE z19ppl_mm_dat-cltprt,
prttx LIKE z19ppl_mm_dat-prttx,
message(150),
msgno(23),
END OF it_error.
DATA: BEGIN OF it_class OCCURS 0,
mtart LIKE t9mmclocmm-mtart,
traw LIKE t9mmclocmm-traw,
cltprt LIKE z19ppl_mm_dat-cltprt,
prttx LIKE z19ppl_mm_dat-prttx,
END OF it_class.
DATA: BEGIN OF it_mmflag OCCURS 0,
cltprt LIKE z19ppl_mm_dat-cltprt,
mmflag LIKE z19ppl_mm_dat-mmflag,
END OF it_mmflag.
DATA: BEGIN OF it_extend OCCURS 0.
INCLUDE STRUCTURE zmmclocmm.
DATA: END OF it_extend.
BDC Data
DATA: BEGIN OF it_bdctab OCCURS 30.
INCLUDE STRUCTURE bdcdata.
DATA: END OF it_bdctab.
Data returned from transaction
DATA: BEGIN OF it_trn_ret OCCURS 10.
INCLUDE STRUCTURE bdcmsgcoll.
DATA: END OF it_trn_ret.
Email
DATA: BEGIN OF it_mail_text OCCURS 0.
INCLUDE STRUCTURE solisti1.
DATA: END OF it_mail_text.
Storage location and warehouse data
DATA: BEGIN OF it_whse OCCURS 0,
cltprt LIKE zmmclocmm-cltprt,
lgnum LIKE z19sloccon-lgnum,
END OF it_whse.
DATA: BEGIN OF it_sloc OCCURS 0,
cltprt LIKE zmmclocmm-cltprt,
lgort LIKE z19sloccon-lgort,
END OF it_sloc.
DATA: BEGIN OF it_lgnum OCCURS 0,
lgnum LIKE z19sloccon-lgnum,
END OF it_lgnum.
DATA: BEGIN OF it_lgort OCCURS 0,
lgort LIKE z19sloccon-lgort,
END OF it_lgort.
DATA: BEGIN OF it_sloc_extend OCCURS 0.
INCLUDE STRUCTURE zmmclocmm.
DATA: END OF it_sloc_extend.
Start of Insert TT67507
DATA: BEGIN OF it_qm OCCURS 0,
matnr LIKE mara-matnr,
werks LIKE marc-werks,
END OF it_qm.
End of Insert TT67507
DATA: v_slin TYPE i,
v_wlin TYPE i,
v_index TYPE i,
v_lgort LIKE z19sloccon-lgort,
v_lgnum LIKE z19sloccon-lgnum.
Work fields
DATA: v_ermsg(500),
v_subrc LIKE sy-subrc,
v_mode,
v_mail_subject LIKE sodocchgi1-obj_descr,
v_email LIKE sadrud,
v_single,
v_message TYPE zchar150,
v_mtart LIKE t9mmclocmt-mtart,
v_traw LIKE t9mmclocmt-traw,
v_skip,
v_hold_cltprt LIKE z19ppl_mm_dat-cltprt.
Constants
CONSTANTS: co_mark VALUE 'X',
co_klart LIKE rmclf-klart VALUE '001',
co_class1 LIKE rmclf-class VALUE 'PARTNUM', "DK69475E
co_class2 LIKE rmclf-class VALUE 'L/STATION', "DK69475E
co_ssqss(4) VALUE '0001', "TT67505
co_insp1(2) VALUE '01', "TT67505
co_insp2(2) VALUE '08'. "TT67505
CHECK NOT matdata[] IS INITIAL.
v_single = single.
CLEAR: it_class,
it_error,
message,
v_message,
it_extend,
v_hold_cltprt.
REFRESH: it_class,
it_error,
it_extend,
it_sloc,
it_whse,
it_sloc_extend.
LOOP AT matdata.
Get default data
SELECT SINGLE * FROM t9mmclocmm
WHERE mtart = matdata-mtart
AND traw = matdata-traw.
IF sy-subrc NE 0.
IF v_single = space.
SELECT uname INTO t9mmcuser-uname
FROM t9mmcuser WHERE mtart = matdata-mtart
AND traw = matdata-traw.
CLEAR it_error.
it_error-uname = t9mmcuser-uname.
it_error-cltprt = matdata-cltprt.
it_error-prttx = matdata-prttx.
CONCATENATE 'Table T9MMCLOCMM not maintained for'
matdata-mtart
matdata-traw
INTO it_error-message SEPARATED BY space.
APPEND it_error.
ENDSELECT.
ELSE.
CONCATENATE 'Table T9MMCLOCMM not maintained for'
matdata-mtart
matdata-traw
INTO v_message SEPARATED BY space.
ENDIF.
CONTINUE.
ENDIF.
Extract storage location and warehouse data
CLEAR: v_lgort,
v_lgnum.
PERFORM fm_sloc_whse_data USING matdata-cltprt
matdata-prttx.
IF t9mmclocmm-lgort NE space.
v_lgort = t9mmclocmm-lgort.
ENDIF.
Initialise
CLEAR: is_headdata,
is_clientdata,
is_clientdatax,
it_materialdescription,
it_taxclassifications,
is_plantdata,
is_plantdatax,
is_forecastparameters,
is_forecastparametersx,
is_storagelocationdata,
is_storagelocationdatax,
is_valuationdata,
is_valuationdatax,
is_warehousenumberdata,
is_warehousenumberdatax,
is_salesdata,
is_salesdatax,
is_bapi_te_mara,
is_bapi_te_marax,
it_extensionin,
it_extensioninx,
is_return,
it_mail_text.
REFRESH: it_materialdescription,
it_taxclassifications,
it_extensionin,
it_extensioninx,
it_mail_text.
Fill BAPI structures
is_headdata-material_external = matdata-cltprt.
is_headdata-ind_sector = t9mmclocmm-mbrsh.
is_headdata-matl_type = t9mmclocmm-mtart.
is_headdata-basic_view = co_mark.
is_headdata-sales_view = co_mark.
is_headdata-purchase_view = co_mark.
is_headdata-mrp_view = co_mark.
is_headdata-storage_view = co_mark.
is_headdata-warehouse_view = co_mark.
is_headdata-quality_view = co_mark.
is_headdata-account_view = co_mark.
is_headdata-cost_view = co_mark.
IF t9mmclocmm-prmod NE space.
is_headdata-forecast_view = co_mark.
ENDIF.
Basic data
IF t9mmclocmm-meins = space.
is_clientdata-base_uom = matdata-meins.
ELSE.
is_clientdata-base_uom = t9mmclocmm-meins.
ENDIF.
is_clientdata-matl_group = t9mmclocmm-matkl.
is_clientdata-division = t9mmclocmm-spart.
is_clientdatax-base_uom = co_mark.
is_clientdatax-matl_group = co_mark.
is_clientdatax-division = co_mark.
PANDA
IF t9mmclocmm-traw = 'P1'.
is_clientdata-trans_grp = t9mmclocmm-tragr.
is_clientdatax-trans_grp = co_mark.
ENDIF.
Quality
is_clientdata-qm_procmnt = co_mark. "TT67507
is_clientdatax-qm_procmnt = co_mark. "TT67505
is_plantdata-ctrl_key = co_ssqss. "TT67507
is_plantdatax-ctrl_key = co_mark. "TT67507
Description data
it_materialdescription-langu = 'E'.
it_materialdescription-matl_desc = matdata-prttx.
APPEND it_materialdescription.
Tax classifications for PANDA
IF t9mmclocmm-traw = 'P1'.
CLEAR it_taxclassifications.
it_taxclassifications-depcountry = t9mmclocmm-aland.
it_taxclassifications-tax_type_1 = t9mmclocmm-tatyp.
it_taxclassifications-taxclass_1 = t9mmclocmm-taxkm.
APPEND it_taxclassifications.
ENDIF.
Country of origin for XP via ZMMCM
IF v_single NE space
AND t9mmclocmm-traw = 'XP'
AND t9mmclocmm-herkl = space.
t9mmclocmm-herkl = matdata-herkl.
ENDIF.
Plant data
is_plantdata-plant = t9mmclocmm-werks.
is_plantdata-profit_ctr = t9mmclocmm-prctr.
is_plantdata-pur_group = t9mmclocmm-ekgrp.
is_plantdata-pur_status = t9mmclocmm-mmsta.
is_plantdata-comm_code = t9mmclocmm-stawn.
is_plantdata-countryori = t9mmclocmm-herkl.
is_plantdata-pvalidfrom = sy-datum. "mmstd
is_plantdata-sloc_exprc = t9mmclocmm-lgfsb.
is_plantdata-mrpprofile = t9mmclocmm-dispr.
is_plantdata-mrp_ctrler = t9mmclocmm-dispo.
is_plantdata-lotsizekey = t9mmclocmm-disls.
is_plantdatax-plant = t9mmclocmm-werks.
is_plantdatax-profit_ctr = co_mark.
is_plantdatax-pur_group = co_mark.
is_plantdatax-pur_status = co_mark.
is_plantdatax-comm_code = co_mark.
is_plantdatax-countryori = co_mark.
is_plantdatax-pvalidfrom = co_mark.
is_plantdatax-sloc_exprc = co_mark.
is_plantdatax-mrpprofile = co_mark.
is_plantdatax-mrp_ctrler = co_mark.
is_plantdatax-lotsizekey = co_mark.
PANDA
IF t9mmclocmm-traw = 'P1'.
is_plantdata-loadinggrp = t9mmclocmm-ladgr.
is_plantdata-gr_pr_time = t9mmclocmm-webaz.
is_plantdata-specprocty = t9mmclocmm-sobsk.
is_plantdata-dep_req_id = t9mmclocmm-sbdkz.
is_plantdatax-loadinggrp = co_mark.
is_plantdatax-gr_pr_time = co_mark.
is_plantdatax-specprocty = co_mark.
is_plantdatax-dep_req_id = co_mark.
ENDIF.
Forecast data
IF t9mmclocmm-prmod NE space.
is_forecastparameters-plant = t9mmclocmm-werks.
is_forecastparameters-fore_model = t9mmclocmm-prmod.
is_forecastparametersx-plant = t9mmclocmm-werks.
is_forecastparametersx-fore_model = co_mark.
ENDIF.
Storage location data
IF t9mmclocmm-traw = 'P1' " PANDA
OR v_lgort NE space.
is_storagelocationdata-plant = t9mmclocmm-werks.
is_storagelocationdata-stge_loc = v_lgort.
is_storagelocationdatax-plant = t9mmclocmm-werks.
is_storagelocationdatax-stge_loc = v_lgort.
ENDIF.
Valuation data
is_valuationdata-val_area = t9mmclocmm-werks.
is_valuationdata-val_type = space.
is_valuationdata-val_class = t9mmclocmm-bklas.
is_valuationdata-orig_group = t9mmclocmm-hrkft.
is_valuationdatax-val_area = t9mmclocmm-werks.
is_valuationdatax-val_type = space.
is_valuationdatax-val_class = co_mark.
is_valuationdatax-orig_group = co_mark.
Warehouse data
IF v_lgnum NE space.
is_warehousenumberdata-whse_no = v_lgnum.
is_warehousenumberdatax-whse_no = v_lgnum.
ENDIF.
Sales data for PANDA
IF t9mmclocmm-traw = 'P1'.
is_salesdata-sales_org = t9mmclocmm-vkorg.
is_salesdata-distr_chan = t9mmclocmm-vtweg.
is_salesdata-delyg_plnt = t9mmclocmm-dwerk.
is_salesdata-item_cat = t9mmclocmm-mtpos.
is_salesdatax-sales_org = t9mmclocmm-vkorg.
is_salesdatax-distr_chan = t9mmclocmm-vtweg.
is_salesdatax-delyg_plnt = co_mark.
is_salesdatax-item_cat = co_mark.
ENDIF.
Additional data
is_bapi_te_mara-material = matdata-cltprt.
is_clientdata-extmatlgrp = t9mmclocmm-extwg.
is_bapi_te_mara-kzkfg = t9mmclocmm-kzkfg.
is_bapi_te_marax-material = matdata-cltprt.
is_clientdatax-extmatlgrp = co_mark.
is_bapi_te_marax-kzkfg = co_mark.
it_extensionin-structure = 'BAPI_TE_MARA'.
it_extensionin-valuepart1+0(18) = matdata-cltprt.
it_extensionin-valuepart1+18(18) = 'NEW TEST'.
APPEND it_extensionin.
it_extensioninx-structure = 'BAPI_TE_MARAX'.
it_extensioninx-valuepart1+0(18) = matdata-cltprt.
it_extensioninx-valuepart1+18(1) = 'X'.
APPEND it_extensioninx.
Call BAPI
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
headdata = is_headdata
clientdata = is_clientdata
clientdatax = is_clientdatax
plantdata = is_plantdata
plantdatax = is_plantdatax
forecastparameters = is_forecastparameters
forecastparametersx = is_forecastparametersx
planningdata = is_planningdata
planningdatax = is_planningdatax
storagelocationdata = is_storagelocationdata
storagelocationdatax = is_storagelocationdatax
valuationdata = is_valuationdata
valuationdatax = is_valuationdatax
warehousenumberdata = is_warehousenumberdata
warehousenumberdatax = is_warehousenumberdatax
salesdata = is_salesdata
salesdatax = is_salesdatax
storagetypedata = is_storagetypedata
storagetypedatax = is_storagetypedatax
IMPORTING
return = is_return
TABLES
materialdescription = it_materialdescription
unitsofmeasure = it_unitsofmeasure
unitsofmeasurex = it_unitsofmeasurex
internationalartnos = it_internationalartnos
materiallongtext = it_materiallongtext
taxclassifications = it_taxclassifications
returnmessages = it_returnmessages
prtdata = it_prtdata
prtdatax = it_prtdatax
extensionin = it_extensionin
extensioninx = it_extensioninx.

Mrp area not determined

Hi experts,
I ahve created a sale order while creating it show the error mrp area is not determined.
pls guide me how to resolve it.
I enter and save it .
the material is in stock and i created outbound delivery it is showing 0 st.
I have checked all stock is available.
pls guide me why this mrp area not maintaing message is coming while creating so
regards
arun

Dear Arun
Give us Message ID and Message number
Take help of PP guy
Please refer following for some help
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.
http://www.sap-img.com/pp010.htm
Regards
Jitesh

MRP AREA CONFIG & PROCESS

Hi PP Gurus,
I want to know about the complete process of MRP Areas.
1) Complete step by step process in terms of config. & front end in SAP.
2) How to activae it for Plant, Storage location & vendor.
3) Difference between above three & where they are exactly used.
The person who helps will be awarded points = 10.Sure.
Regards

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
Edited by: Tejas Pujara on Nov 7, 2008 12:02 PM

Sales Requirnment in MRP Area

Similar Messages

Maybe you are looking for