Problem in MRP Area

Hi
one problem which i s related to MRP Area
how to creat MRP area and how to assign Storage locations to that MRP area
i tried but it is created for plants , not created for Storage locations.
regards
sesidhar

Hi Sesidhar
Try this Path in IMG
Production-> Material Requirement Planning-> Master Data-> MRP Area-> Define MRP Area-> New Entry
Enter Storage Location, In MRP Type select 2 (Storage Location), Rec storage Location.
Hope this will help
Regards
Samarth

Similar Messages

Problem with MRP area

Gurus,
I had activated MRP area for exisitng client.
The scenario is,
Within a plant i have two MRP area. One is plant level (A) and the other one is storage location level (B)
A finished good and its components belongs to both the MRP areas. (A and B) I created a Planned Independent Requirement for finished good at storage location MRP area (B) and run MRP via MD02 for MRP area B, i got a planned order at MRP area B. But the dependent requirements for the components are created at MRP area (A) plant level.
My requirement is to get the dependent requirements at MRP area B for pegged requirements of MRP area B.
Suggestion to this isue is highly appreciated.
Thanks,
Aravind

Hi pravin,
Thank you for the reply.
Initially my client was not activated for MRP area. So when i activated MRP area, throughout my client for each of the existing plants an MRP area is created by default. So, all the materials that belongs to the plant, by default belongs to the plant MRP area.(A)
I created one more Storage location level MRP area (B) and assigned that to MRP 1 view of the finished good and all of its components. I also created a planned independent requirement for the finished good at MRP Area B. that is i can see the requirement in MD04 screen only with the MRP area B and not in MRP area A.
Then i ran MRP for the finished thru MD02 for MRP Area B. I got a planned order in MD04 of MRP area B.
As you are aware MD04 screen is specific for particular MRP area.
This planned order is not displayed in MD04 screen of MRP Area A. But the dependent requirements for the components are not displayed in MD04 screen of B. But the dependent requirements are seen in MD04 Screen of MRP area A.
As per my understanding the dependent requirements of components should be displayed in MD04 screen of B as my pegged requirements are from MRP area B.
Kindly suggest and please let me know if any thing is not clear.
Regards,
Aravind

MRP area for running a sale order MRP

Hello PP experts,
I come across a scenario where , I need to do the MRP run for sale order in a MRP area. I have checked , I can put PIR with respect to MRP AREA , but when I open MD50 screen for running MRP for sale order. I did not found the MRP AREA
field in the screen.
In short , my question is , How the sale order MRP run , system will do in a MRP
area defined for the material ?
Here , I have already defined the material is MRP AREA and also I have created
MRP area segment in the material master.
I have also configured the MRP area in SPRO.
Waiting for your reply.
Regards,

Hello ,
Thanks for reply.
I am using plant MRP area. For FERT , I am using make to order strategy 20.
I want to specify the real problem. It is like below.
Suppose 'A ' is sumassembly goes to a variant configured MTO KMAT say 'V'.
The same 'A' subassembly is a child for a make to stock FERT say ' S'.
Presently using strtegy 11 for MTS fert 'S' and 10 for the subassembly ---'A'.
Now the planner want to plan for the subassembly.
He is putting the PIR for the subassembly as sales order is not availble and he is putting the PIR for FERT 'S'.
When sales order is coming then additinal quantity planning is happening.
So I suggested to use the strategy 70 for subassembly 'A' , so the sales order (of 'V') OF quantity will be offset for the PIR of the SUBASSEMBLY 'A'.
But the consumption of PIR of 'A' will be apllicable to MTS FERT that is 'S'.
So how can we prevent the system from offsetting the dependent requiremet triggered from the PIR of 'A'.
That means the consumption (that is the usage of stategy 70) of the FERT requirement should only work for ' A' and sales order based KMAT 'V'.
The same offseting should not work for subassembly 'A' and MTS FERT 'S'.
For for Make to order KAMT 'V' , if I use MRP area and do the sales order planning in MRP area. Will I get the desired result ?
Waiting for reply.
Regards,
Ravindra

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

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

MD04 - Subreq - Storage location MRP area

Hi all,
I have an issue of Subreq in MD04 which is not assigned to the the good MRP area.
I'm explaining :
Business process
   -> I work with a subcontractor
        case 1 : either I buy raw material to be processed and delivered it directly to my subcontractor
        case 2 : either I send raw material from my physical stock to my subcontractor
   -> I create subcontracting purchase order with indication as components, the raw material.
   -> In case of the components are already in my subcontractor (case 1), the reservation (Subreq) should not consume my physical stock.
   -> In case of the components are in my physical stock (case 2), the reservation (Subreq) should consume the physical stock.
Solution choosen
Then I decided to create a storage location MRP area : "EXTERN" as External.
I assigned a storage location "EXT" to this MRP area.
I assigned this MRP area to the material in MRP1 / MRP Area.
In the purchase order, in the components popup,
For case 1 : I assigned "EXT" as Prod.Stor.Loc and Supply area
For case 2 : nothing special is filled
Issue
For the case 1, althought I assigned the storage location "EXT", the Subcontractor Requirement is not attached to the good MRP area.
WHY?
Remark : I didn't use the subcontracting MRP area because I would like to have 2 cases : case 1 & case 2.
Thank you in advance for your help about this problem which make me nervous !

Hello Catherine
Your system is working as designed. The following note explains the system design in more detail:
503497 - Subcontracting and MRP areas
Take a look on the relevant information provided by this note below:
Reason and Prerequisites
The most important point to understand the system behavior is the fact that the withdrawal of the (subcontracting) component is generally carried out during the goods receipt for an SC procurement proposalfrom the subcontractor stock that is managed at plant level from an inventory management point of view and that has no reference to a storage location at all.
This causes that subcontractor requirements can never enter a storage location MRP area, since you can later not post the withdrawal from this MRP area.
Thus SC-requirements always enter the SC segment of the plant MRP area or the SC-MRP area.
The SC MRP area in turn is supplied by stock transfer reservations from the plant MRP area or via third-party order processing through procurement proposals with goods receipt directly to the subcontractor. A supply through the materials planning from a storage location MRP area is not possible.
For the above reason, SC-requirements do also not carry any storage location, since the storage location does not have any control function at all for SC-requirements:
You cannot and you should not determine a storage location MRP area (see above), and the subcontractor MRP area is determined via the vendor of the procurement proposal, thus it is independent of the storage location.
See also Note 376050 on this topic that makes a modification available which prevents the deletion of the storage location in the subcontractor requirements, so that you can use, for example, customer-specific reports to analyze the storage location.
Please observe that the mentioned modification note 376050 only makes the storage location available on table RESB, so that you can use it on custom report. This modification will not make the storage location to be considered by MRP or on MD04.
BR
Caetano

Problem With MRP

Hi Friends,
I am facing a problem with MRP. In my Implementation, my Client is a Automobile Gasket Manufacturer.
One major product line is Gaskets which is high volume and low price
We will use Make to stock with streategy 40.
Now the queries are as follows-
1) What should be the frequency of MRP Run for the plant (weekly , monthly of daily)
2) If after one MRP Run- some Planned Orders and some Purchase Req are converted to Production Orders and Purchase Orders. My Prod Orders- 100 Pieces and PO is 1000 Kgs.
Now subsequently , due to change in schedule,(PIR is maintained by Sales Department and it changes often) lets say, my PIR is Changed from 100 to 10 Pieces ,
How can a PPC person come to know of this and inform the Buyer to foreclose the PO or amend the PO and as well change the Prod order also.
Thanks in Advance
Waiting for your Reply,
Praveen

Hi Praveen
1) What should be the frequency of MRP Run for the plant (weekly , monthly of daily) : Daily Basis as your demand changes frequently.
2) PPC will understand from MD04 screen where all the result of MRP as Stock Requirement List available.U cant change Production Order while running MRP as your demand changes from 100 to 10 pecies because Prodction Orders are firmed recipept.In that case you can change quantiy , do the availablity check and scheduled again or set TECO so that it will not show up in the MD04 screen also.
Any changes to demand and subsequent effect can be viewed through the exception messeges column in MD04/MD05
Hope this will help you to figure it out.
Regards
Jia

Creating Planned Independent Requirements for an MRP Area.

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

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

MRP Areas in Flexible Planning?

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

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

MRP Area 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?

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

Subcontracting with MRP area

Hi,
we have a FERT material that is in the MRP area by storage location.
This material was produced internally. When we ran MRP the requirements and planed orders for FERT material and its components were showed in MRP area. It was ok
Nowadays this FERT material was changed to subcontracted.
We don't have a defined supplier for FERT material.
When I run MRP the requirements and planed orders for FERT material are still in MRP area.
When we run MRP for components, the requirements and planned orders go to MRP plant.
This way if we have in MRP area documents placed to cover the requirements from FERT material, MRP will suggest to cancel them. In MRP plant the MRP will suggest to create another documents to cover. How can We avoid this problem?
Thanks and best regards,
Elaine

Hi Elaine,
If your FERT material is set to F , 30 then your MRP run in MRp Area will not create any dependent requirement.
Assuming the setting is X in Material Master,
Given an option please remove the MRP Area planning and the PIR related to that and shift PIR for you FERT material to Plant level in mD61,MD62. This should avoid Planned order getting created in MRP Ara and Plant.
in my past experience unlesss you want to do Planning run with Scope as planning as Vendor th euse of MRP Area for planning for PIR leads to confusion for End users.
Hope this helps.
Thx
MJ

MRP area configure but vendor is diffrent between client

May I know if have configure MRP area before?
I faced the following problem. Hope you can help.
I configure one MRP area with MRP area type as 03 (i.e. vendor) in DEV-100
However, I cannot put in the subcon-vendor number at DEV-100 because the vendor is internal numbering and it is different between the production and devleopment.
Thus, how to put in the vendor number in DEV-100?
and How to change it in Production system on this vendor?
thanks
Tuff

Hi,
you have to do this configuration directly in production...
Kuber

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.

Problem in MRP Area

Similar Messages

Maybe you are looking for