Use of report RMMDDIBE for MRP area creation

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

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

Similar Messages

Change consumption for MRP Area

how I can change the consumption for MRP Area recorded in the table DVER without using MM02 ?
Thanks,
Edited by: BEKKARI Mohamed on Feb 9, 2009 5:49 PM

Hi,
write one report get the data from the table dver.
Change the value and use update database.
then commit.
>Thanks

Creating a file to be used by report ROIUH_LOAD_JEINTF for journal entry

Hello everyone,
My doubt is related to the PRA module -
I have to create a file to be used by program ROiUH_LOAD_JEINTF for journal entry creation. There are other programs also creating a similar file to what I am expected to create.
When I observe the existing programs, they have not used OPEN DATASET statement, instead directly used the TRANSFER dataset and then CLOSE DATASET.
What that does is it creates a file on the app server in a different format with only 1 line even if there may be like 10 lines of journal entry. The file mainly contains # which seems like some internal coding by the system.
When I tried using the OPEN DATASET statement, it wrote all the lines to the app server that were there in my internal table.
However, when I do not use the OPEN DATASET statement, it creates a file with just one line and maily # instead of the actual data from internal table.
Can any one explain what difference does it make to the system when we do not use the OPEN DATASET statement.
You help would be highly appreciated.
Thanks and Regards,
Shipra.

Hello Satish,
Thank you for your response.
I think I was not clear enough about my doubt. I do not have any confusion about what OPEN DATASET would do.
In my case, there is a file being written to the app server without using an OPEN DATASET for OUTPUT statement. The Z program directly calls a TRANSFER statement.
The file that is created on the app server looks like:
7042008-11-01 000200100840 ######RD##################203 #### #####10012888 #####RI01 MC3
This file is used by the program ROIUH_LOAD_JEINTF. There are several lines in the internal table for Journal Entry creation but only 1 line shows in the file. However, when you debug the program ROIUH_LOAD_JEINTF with the above filename, you would see that it takes up all the JE lines that were passed from the previous program (the Z program) which created this file.
However, when I changed the Z program to have an OPEN DATASET statement, it had all the lines displayed in the file, the file was very readable.
I just wanted to know how does the system write to app server when no OPEN DATASET statement is written in the program.
Hope I am clear this time. Thanks again.
Regards,
Shipra.

BOM Explosion for MRP Area

Dear Expert,
I have doubt regarding BOM explosion for MRP Area. This doubt is triggered when performing MD01, as result I do not find the dependent requirement in MD04 for my FG. I have maintained the BOM through CS61 and MRP area for all component, I understand that only component level system is taking into account MRP area (storage location). FYI before maintaining all components to MRP area, the BOM explosion was successful exploded. Your advice is appreciated.
Best regards,
Mahnansa

Dear,
Please check the Explosion control in Customizing, Transaction OMIW.
Try to explode the BOM in CS11 , CS12 or CS13 if it is working there in curret date then chack the planning file entry in MD21.
You need to convert the planning file entery at MRP area in OM0F.
Also note the dependent requirement is not generated in the corresponding MRP area to which the production storage location in the material master has been not assigned for the data of the MRP area.
Regards,
R.Brahmankar

Program or exit/BAdi for table DVER (Material Consumption for MRP Area)

Hi,
I want to update table DVER (Material Consumption for MRP Area).
Please suggest if any program or exit/BAdi.

Check these function modules:
CONSUMPTION_EXI_MAT_PLA_PE_DB
CONSUMPTION_READ_FOR_MM_DB
CONSUMPTION_REF_MAT_PLA_PE_DB
DVER_GENERIC_EXIS_MATNR
DVER_GENERIC_EXIS_MATNR_DB_PER
DVER_GENERIC_READ_MATNR_PLA_PE
DVER_GET_BILD
DVER_SET_DATA
DVER_SET_SUB
A badi/user exit is triggerred when a standard transaction is run.Let me know if you want to update the table when a std. transaction is executed and the transaction code.

Planning file entry for MRP Area

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

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

Use of Planning Calender in MRP Area

Hi ,
Can any body tell me the possible way to use Planning Calender in MRP Area for Vendor direct Orders
Thanks & Regards,
Nirmalya

Hi
i have tried above link ..........But still not able to get the desired results.
Need your help on this.
Thanks,
Nirmalya

Source List for MRP Area

Is there a possibility to maintain source list for MRP purposes
at storage Location level? We receive requirements from a couple
of our subsidaries and we were consolidating this to be a single
requirement for our suppliers, however this has changed we have
to now show each subsidary's requirements individually. We
currently only use a single plant, previously we created
additional plants for this and maintained a separate source list
for each. Is this the best way to represent and run MRP for each
subsidary? Thanks.

Dear Kennedy,
Source list for Storage Location level not possible!!
An MRP area represents an organizational unit for which you can perform material requirements planning separately.
An MRP area can include one or several storage locations of a plant or a subcontractor. You can define MRP areas in a plant.
By defining MRP areas, you can perform MRP for each area. This means the right quantity of materials can be provided on time for each area, such as a production line, a storage location for spare parts, or subcontractor stock.
Bye,
Muralidhara

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.

How to run MRP only for MRP area ?

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

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

Tables used in f.08 for business area value

Hi ,
thanks Dzed & raju .
structure also given you but,
now i want from which table business area(GSBER) , debit & credit values are taken.
Regards,
Jyotsna

Hi Jyotsna ,
It's Fetching the business area from FAGLFREESEL-RBUSA. . (Field for Business area) .
Also you can fidn the smae in BSEG-GSBER as well.
Regards,
rajesh Kumar

Report name for Export are not correct

Hello,
When I'm doing an export on PDF or XLS, the file name is wared, it's not taking the name of the report or in the TOP of the tree navigation in the PDF
- Is it possible to have the rigth name ?
- Is it possible to have the name depending on some values of the report, like date of extraction ?
Thanks in advance
Alex
Edited by: Alexandre VANNIER on Oct 15, 2008 11:47 AM

Hi Alexandre,
You can insert a report title in FileSummary Info..This will help you.
You can insert report execution data and time in the report and it is not possible to use as report name.
Thanks,
Sastry

Using a report value for a where clause in other report

Hi All,
i'm getting kinda nuts here. I created a page with three reports.
First report show the name of the user who logged in with his/her whole name. Second report shows the year, week, begin/end date of the week for the user in the first report. The third report show the hours the user worked in the week selected in the second report.
The link between first and second report is on column report. Somehow i managed it to work with second_report.mdw_code = :P3_ACRONIEM. I have no idea were this P3_ACRONIEM item is coming from, while i have no items in my page whatsoever. Now i need to link the second report to the third report. I have to use the second_report.mdw_code, second_report.year and second_report.week but i have no idea how to link these together. Any idea's? (Like making items, but then i have no idea how to link that item to the value in the second report). Please help.
Kind regards,
Dave
The link between the first and the second i could get it to work with :P3_ACRONIEM. I have no idea where this ITEM is coming from, because i have no items in my page (and it's the only page in the application). Then

Hi Dave,
If I understand you correctly, you have a one report that lists users, a second report that lists dates and a final report that shows hours worked?
If so, you may find it easiest to have hidden fields on your page and base the second and third reports on these using appropriate WHERE clauses. (I generally put hidden fields in a region in the "After Header" position)
So, if the first report contains a USER_ID field, have a hidden field called P1_USER_ID. The link on the first report will branch back to the same page and set the value of P1_USER_ID to #USER_ID# The second report can then use WHERE USER_ID = :P1_USER_ID. When the page reloads, the second report redisplays and is filtered to show only those records relating to the selected USER_ID in the first report.
To extend this, if the second report contains WEEK_NUMBER, it should have a link that branches back to the same page and sets a hidden P1_WEEK_NUMBER field with #WEEK_NUMBER#. The third report should when have WHERE WEEK_NUMBER = :P1_WEEK_NUMBER AND USER_ID = :P1_USER_ID. You can, if need be, have and set more than one hidden field during each link.
Regards
Andy

No Request Prompt for Info Area Creation

Hello Gurus,
When i create an infoarea , it does'nt ask for a request. any clue. then how do we transport it to production. or do we have to create the same in production too.
thanks in advance.
TR PRADEEP

Hi,
another option is to goto the transport connection and switch 'standard on'. Then you will always be asked for a request. But normally, follow Robertos suggestion. In my experience I had only one customer who switched standard on in the last six years.
regards
Siggi

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

Use of report RMMDDIBE for MRP area creation

Similar Messages

Maybe you are looking for