DP forecast release on MRP area

Hi Experts,
We are having multiple MRP areas within a distribution center. The sales history is available in R3 with the associated sloc as the delivering sloc.
Can i get this history in DP , do a forecast & release it on MRP areas in APO? What are the precautions to take care in this cycle.
Regards,
Vinay

Hi Vinay,
If you want to do forecast in MRP area level in DP, than follow the below steps:
1. CIF MRP area to APO using integration model.( MRP area will be appeared in APO as Location)
2. Create a characteristic with MRP Area.
3. Do forecasting at MRP area level or dis-aggregate to MRP area level.
4. Release the forecast to ECC.
Hope this answer your query.
Thanks
kishor

Similar Messages

Upload Forecasting parameters on MRP area level

Hi there,
Is there a way I can automate via Bapi or Idoc, the upload of the forecasting parameters on MRP area level.
The MRP area data is uploaded via IDOC /ISDFPS/MDMA but there is nothing foreseen for the forecast parameters.
Parameters that should be uploaded are DPOP-KZINI and DPOP-PRMOD.
Anyone an idea?

Dear Essam,
Please try the following procedure.
1. Create Plan in flexible planning --> MC93 (In this step you create Sales plan in flexible planning )
2.Sales plan verification transfer to active version--> MC8V (In this step you verify and transfer to active version)
3.Transfer sales plan to production plan -->MC8Q (In this step you transfer to sales plan to production plan)
4.Create Inactive Demand in Demand Management -->MD61 (In this step you create Independent Requirement which can be
simulative requirements. These requirements are set after analyzing sales forecast and production requirements together)
I hope it may help you out..
Feel free to ask.
Thanks,
Mohit

Scheduling agreement between mrp areas.

Hi all! I have a question.
Can i create scheduling agreement between two storage location whitin one plant for stock transfers? (storage locations - mrp areas).
where can i read about this?
Thanks.

Hi Mildar,
Following OSS notes will be useful to you.
1402298 Purchase order handling release with MRP area
1067960 Stock trasnfer reservation not created for MRP area
Following URL will help for the functionlity of MRP areas within APO
http://help.sap.com/saphelp_scm70/helpdata/en/c1/147a375f0dbc7fe10000009b38f8cf/frameset.htm
Please check and confirm.
Regards
Datta

MRP Areas & shipments out of

Once I create an MRP area what is the best practice around making shipments in SD "from" the MRP area and not the plant it resides in itself?
Also if product is made within the plant iself the MRP area resides in vs outside STO ... what is the best practice on "transfering" the product from the plant to the MRP area (MRP area resides within the same plant).
Tim

Thankyou.
One last quesiton ... we are concerned about consuming "forecast" against the MRP area stock .... management is still asking how are sales orders to be entered "against" the MRP area so that forecast in demand plan is consumed?
As it sounds the order entry is as normal eg by sold to, material, date, etc. and only real difference is that when you create your delivery and pick you retrieve stock from the MRP area location eg 1002 which decrements stock from it.
As far as movements, it sounds like you can use location to location transfer postings to move stock between the plant locations and the MRP area location inside the plant and special procurement keys to move UB or NB Stock transports to the plant and then transfer to the MRP area.
Your thoughts or guidance are appreciated as we've never used MRP areas and can't find much info on these areas anywhere.
Tim

Mandatory/Default field for mrp/forecast profile mrp area

Dear guru,
In MM01/MM02 when i create a new mrp area for a material I want Mrp profile field and forecast profile field as mandatory field. Or as alternative solution purposed with a default.
How can I do that ?

Dear Murugesan ,
in OMSR i make the mrp profile (MDMA-DISPR) and forecast profile (MDMA-PROPR)
as required entries in the screen sequence.
But when I create/change mrp area fields the system dont consider as required these fields.
Are you sure that the field selection for data screen is concerning also for mrp area fields ?
Thanks.

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

Creating a New Forecasting profile for MRP

Hi there,
Please can somebody let me know how do I create a new Forecasting profile for MRP.
I want to see this in table MRPR once created. (field PROPR).
Kind Regards,

Dear marelizen
Use transactio code MP80.
Creating a Profile
The information contained in this info object is relevant to the material master for industry and to the article master for retail. Retail customers are requested to substitute:
article for material
requirements planning for material requirements planning or MRP
1. In the Material Master menu, choose Profile ® MRP profile or Forecast profile ® Create.
The initial screen appears.
2. Enter the name you want to give the profile.
If you want to use an existing profile as a reference, enter its name under Copy from so that the system can copy its values to the new profile.
3. Choose Selection screen.
The selection screen appears. It shows all the fields that can be copied to the MRP or Forecasting screen in the material master record.
4. Enter a profile description and select the fields you want the profile to contain, specifying whether each field is to be copied to the material master record as a fixed value or as a default value.
It is not possible to select Fixed lot size and Maximum stock level in a single MRP profile. However, if you select Maximum stock level, you must also select Lot size (materials planning).5. Choose Data screen.
MRP profile data is spread over two screens. To switch from one screen to the other, choose Data screen 1 or Data screen 2.
When you access the data screen from the selection screen, the system checks whether the fields selected are allowed to appear in the same profile.
The data screen appears, containing only the fields you selected on the selection screen. The fixed values and default values are displayed in different colors. All fixed values are required fields except where the field can also be left blank.
If, in the forecast profile, you enter N or 0 as the forecast model, no forecast is made.
Like forecast model N, if you enter forecast model 0 when maintaining a forecast profile, you will be unable to maintain any other field in the profile.
Unlike forecast model N, forecast model 0 deletes any existing forecast values when you change the material. This ensures that these values are no longer included in materials planning.
6. Enter the corresponding values and save the profile.
If the system detects inconsistencies or errors, it asks you to change the fields selected on the selection screen and/or to correct the values. Otherwise, the initial screen appears, where you can begin to create another profile.
warm regards
Ramakrishna

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

Linking SLoc and MRP Areas in Supply Area

Hi All,
I recently moved one production line from one plant to an other one. This new line is feeded with Water from a separated tank. I would like to be able to see the requirement of water coming from the new line and stock in this tank separatelely from the "other" Water to be able to know how much water we have to supply to this separated tank.
Based on, what we are asking for is a new storage location equivalent to the separated tank (for stock and consumption) and a new MRP are (to be able to differentiate between demand).
this is the situation am going on right now, i think the above subject is what am i thinking the best solution on this situation, can anyone help me guide to work on this. thank you!

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

Distribution Profile / Customer Specific Forecast Release

Hello All,
I have a small question about the distribution profiles in Demand Planning. We use MRP and VMI scenarios.
1. While using VMI, we release forecast from DP to SNP using a distribution profile for each location. We get the percentages based on the quarterly reports on what was actually shipped to the customer and we manually enter the percentage every three months.
Our planners do this manually for the locations today since we only have a bunch of customers through VMI.
2. For the rest of the customers, we use DP and MRP. We release the forecast to ECC using a distribution function that would equally divide the PIR by the total number of days and we see that in MDO4.
The concern now is that instead of dividing the forecast equally by the day, can we divide it by the percentages of forecast consumed by the customer like we do for VMI?
If so, rather than the planner entering the numbers in the distribution profile manually, is there an automated way such as an exit that would actomatically calcuate the percentage consumed by a specific location and update them in the distribution profile automatically. Thank you for your time.
Regards,
Rohit.

Hello Rohit,
You will need these BAdis -
BAdi Name : /SAPAPO/SDP_RELSPLIT
Description: Change period split profile when DP released to SNP.
BAdi Name - /SAPAPO/SDP_RELDATA
Description - Modification of Data During Release from DP to SNP - Orders
You can fetch Period Split Profile value from Freely-Definable Attribute(like AT101) Product-Location Master (Table Name : /SAPAPO/MATLOC) to use during Forecast Release process. is added in /SAPAPO/MATLOC table.
You can create commonly used pattern using distribution functions and mapped those to different Period Split profiles. Also you can map these PSPs to some kind of numeric digits/text to easily identify/remember period split profile names uniquely. These numeric digits can be set into Product-Location Master by either users or by using custom program.
This is just an idea, please think, you may improvise further to make it more purposeful for your scenario.
Example : Common distribution functions -
Month - 4 X 4 - 25% split into 4 Week on the Month
Month - 1F X 1 - 100% on 1st day of the Month
Month - 1L X 1 - 100% on last day of the month
Month - 2 X 4 - 50% split into 2nd and 3rd week of the Month and so on and so forth
Hope this will help.
Thank you
Satish Waghmare

Transaction data in MRP areas in APO

Hi,
We are using storage location MRP areas in APO.In ECC we have a storage location 5000 under plant 1000. We have defined storage location as MRP area and transferred to APO. Now we have two locations in APO one is 1000 and another location 5000 (with location type 1007).one material is existing in both these locations. We have a forecast in location 5000 and a Pur requisition is created for this material in 5000 after SNP heuristics. We are able to see the Pur Requisition in 5000 location in the product view.But when we are looking in 1000 location in the product view,we are not able to see the same purchase requisition.Is this standard functionality or am i missing any setting?
In ECC we can see the same purchase requisition in both the MRP areas in 5000 and 1000 in MD04. But the same is not in APO? we are not able to see in 1000 plant in product view but could see in 5000 location in product view.
Any one has this issue?
Thanks
Chandrakanth

Hello Chandrakanth,
Check if the storage MRP area is not been transfered to APO as Plant.
Take a look on note 896482, perhaps it can helps in analyze how you are CIFing the MRP areas to APO.
Hope it helps.
Regards,
Michel Bohn

Unable to create a new MRP area type 3 for subcontractor?

In golden client for defining the MRP area type 3, its not accepting the vendor number in the subcontractor field ( since there wont be any master data) saying doest not exist in LFA1 table.
But there are certain similar data already available in the golden client, I dont know how those have been created long back for company.
we are using ECC 6.0,
Can i move the TR without subcontractor number to Quality and Production clients and maintain the subcontractor in Material master.
Please suggest me how to do that experts
Thanks
Srini

Hello David,
We are having S&OP 3.0 SP1 patch 1 on premise with HANA version 1.00.69.385057. We have old golden demo files imported.
Could you please let us know...
1) is it right combination..?
2) Is it necessary to upgrade to patch 2.
3) in case, we upgrade to patch 2, do we need to import golden demo file again for patch 2
4) Do we have any release note for patch 2.
Your quick response is highly appreciated. Thanks!!
Regards,
Dinesh Goyal

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

How Forecast Release and Consumption for Variant Configuration

Hi experts,
we are planning in our project how to Forecast Release and Consumption for Variant Configuration
can you explain me
Regards,
babu

Hi Sivaramakrishna,
We tried the same but what is complicating is having "market" attribute of customer in R/3 and planning forecast in DP at the "market" level. There is no customer as such in DP. THere is only market. We could release forecast at market leve using "consumption group". But I am trying to figure out how to have the sales orders consume forecast at the location, product and market level in SNP.
Today we have our sales orders to consume forecast in SNP at location-product level. we are trying to take this to "location-product-market" level in SNP.
I think we need to use some settings for characteristic based or variable consumption I think...but not clear.
Any help is appreciated.
Thanks for taking time to reply.

DP forecast release on MRP area

Similar Messages

Maybe you are looking for