MRP Area Error

Hi all
I am uploading material master mrp area data using LSMW direct input method. The standard prog RMDATIND not showing the BERID field in the step field mapping. IEven table name MDMA is not sowing in structure step also. So that i am not able to mapp BERID field.
Can u suggest right solution.
Thanks
Ganesh

Hi prabu
yes, that is fine. But i have load file only one and i want to update MRP area, MRP group through Standard program RMMDDIBE.
If u said like i want to create onother program for MRP group only. But i dont want like that, i want to update both at a time.
Please suggest me..
Thanks
GAnesh

Similar Messages

MRP Areas error message

Hi
In implementing MRP areas, we created and assigned MRP area to material and later on deleted the config for the MRP area definition without deleting it from material master. We get an error message MD318 - MRP area has not been defined, which is an internal error, there is no oss note fixes for this issue but OSS note exists for MD319...can anyone please suggest me any options to resolve this error.

Dear Sender,
I was checking answer for the same error. and I saw this note. the answer may not be useful as it was in 2011, could be helpful for other checking current and in future.
I resolved by configuring the MRP area in MDLV table along with the MRP Parameters for the plant.
The Products created already without the MRP area were updated as MRP area at plant level for our scenario.
Thanks
Muthu

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

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

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

Creation of new MRP Areas.

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

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

BDC for MM02 - MRP area

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

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

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.

Change vendor in MRP area - SC Direct delivery

Hi,
I need to change the vendor in my MPR area for subcontractor. I receive the following error:
"Vendor 1234 is being used by material ZZZ, therefore cannot be changed"
The material has of course already been assigned to the MRP area as the was requered for the flow using the previous vendor.
br,
anders

Hi,
Try this. First remove the vendor assigned to the material. Then assign new vendor.
Regards,
Prashant Kolhatkar

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?

RIMODINI for CIF Object: [MRP Area Matl, MRP Areas]

Hi Experts,
We have Material maintained at MRP areas in R/3. Integration model is maintained with CIF object : [MRP Area Matl, MRP Areas] to bring the new material master at MRP Area changes through Delta mode(CFM3), but the changes to existing material in Integration model at MRP Area does not come over immediately to APO and not through DELTA mode.
We have to execute Report: RIMODINI to bring the changes of existing material master changes at MRP Area level to APO. Since its a performance intensive it takes too long to execute to bring changes over to APO.
Is there alternative method of bringing the existing material master changes at MRP area level for CIF object : [MRP Area Matl, MRP Areas] to APO without executing RIMODINI.
Additional Information: R/3: SAP_APPL     470     0030     SAPKH47030
                                 R/3: PI                2004_1_470     0015     SAPKIPZI5F
                                APO:SCM                    500     0012     SAPKY50012
Thanks,
K Sendil Kumar
Thanks,
K sendil Kumar

Hi Sendil,
Are you getting this error only for Material or other master data also?
Please can you quickly check below mentioned checks:-
https://www.sdn.sap.com/irj/scn/wiki?path=/display/scm/cif
Regards
Samir

Rounding value at MRP area level

Hi All,
We are using MRP areas at storage location level. Also we have maintained rounding value , one at plant level in mRP1 view and one at MRP area level for that particular storage location.
Now when we run MRP for that storage location specific MRP area one would assume that it picks up the rounding value maintained in that MRp area,but it is picking up the value maintained at plant level.
Am I missing some setting or is it std. system behaviour..pl. advise.
Tks..kiran

Hi Inguva
Can you give more detail of your solution? I have the same problem, MRP is creating requisitions using the lot size parameters from the MRP area but when converting to an STO using ME21N the lot size parameters from the plant are applied.
This usually increases the PO quantity beyond the PR quantity and I get an error message "06076 - Materials of requisition & item & alr. ordered in full"
It's driving me crazy so any help you can offer would be greatly appreciated.
Thanks
Robyn

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

Define new MRP Area

Hi,
I have four plant under one company code. Recently, one more created under the same company code. The Storage loacations are same in SAP across the five plants. While defining MRP area for the new plant Receiving storage location is used what is has used for the other four plant but system is giving error message " Error in Customizing. Storage location ST01 used by MRP area 55555"
Please suggest how to resolve this error.
Regards,
Vs

Dear ,
Couple of checks for you in this issue :
How come Four plants has same common Recieveing Storage Location ? PP Oreg structure is Plant-Storage loaction ( 1:n) but not N:1 .I feel you should have four dirent storage location .However , in MRP area Org sequence is MRP Area -Plant -Storage Loactions .Even you have new plant and u want to create MRP Area for that , you should have Storage Loaction ( any kind) assinged to that plant , then it will allow you to include .If you are trying to use Other plants storage loaction , system will flag this message.
Basically , Receiving storage location is the default sloc that will be in PR that was created by MRP if you run the MRP Area level.So ,
1.Did you Convert planning file entries (SE38 program RMDBVM00)
2.MRP area actvation is at Client level .Check wether u have activated the MRP area or not
43As One plant can be entered for each MRP area and there could be multiple storage location under the plant in one MRP area .But , did you check wether recieveing same storage location can be assinged to multiple plant under diffierent MRP area .
Check this and come bakc
Regards
JH
Edited by: Jiaul Haque on Jul 19, 2010 3:50 PM

I charged my phone and now I can't get it to turn on again. What do I do? I can't find a solution here. All I get are error messages.

I charged my phone and now I can't get it to turn on again. What do I do? I can't find a solution here. All I get are error messages.

Try pulling the battery for 10 minutes and putting it back in. Try pressing and holding the power button for a while 15-30 seconds to see if it will respond. Did anything happen to it, drop, submersion, etc. Was it functioning before you charged, When did it last work. Are you sure it charged up and the charger is working.

Replenishment delivery for material with MRP areas and Avl Check

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

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

MRP Area Error

Similar Messages

Maybe you are looking for