indound triggering for material master

[Former Member]

hi abapers ,

iam new to ale technology,

here iam sending material from one system to other system..

here the outbound side is ok.

here inbound side ineed to do some mapping for materials sent by one system to other sytem.

like if material type in sys1 is 'fert'

there in receiving system it should be ''HAWA'

like mapping is required ,so for this where i do coding.

i found one exit EXIT_SAPLMV02_002, here i can put the code?

when this exiot will trigger how can we test in bebugg mode

in my scenario ones material is receicved how this idoc_input_matmas01 is triggerd? and document is posted in appilcation..

can any one explain me..

[Former Member]

i got the sol

[Former Member]

Can u share it with us?

[Former Member]

in my case i want send material from ser1 o ser2.

in ser2 i need to mapping logic for example..

fert material type in sending side,in receiving side it should be hawa type..

this my scenario.

in receiving side u need to do mapping as u r req.

for material (idoc_input_matams01)

this function module is responsibel to process inbound idoc and post it into application.

if u want to put mapping code.

there are some exits & badi's available for this fm.

i hope how to find out the exits or badi's ..

in my case i used badi BADI_MATMAS_ALE_IN

in this badi the corresponding mm table are there ..

do the mapping and pass the values to these table,

here tables are changing parametrs,

one exp:

IF wa_data-segnam EQ 'E1MARAM'.

mara-mandt = sy-mandt.

mara-matnr = wa_data-sdata+3(18). "Material Number

IF wa_data-sdata+77(4) = 'FERT'.

mara-mtart = 'HAWA'. "Material Type

ENDIF.

MODIFY mara_ueb INDEX 1 FROM mara TRANSPORTING mtart .

then the correponding values are moved to mara_ueb..

note:when u modify table mara_ueb pass the values which u want to modify,,

in my case i passed mtart(here i want to modify matart).

why becasue there some ctrl infrmation is there for mara_ueb(idoc inforamatiom)

so,be careful when modifying this .

then after mappig this control comes out from badi.

and execute fm 'material_maintain_dark'.

this fm is responsibe for creating material.

so,after executing this fm check status.

if any errors it will be in MERRDAT.

if any doubts let me know.....

[Former Member]

Hi Ajay ,

I want to Transfer the Data from 4.7 Server to ECC 6 with some Business Updations like Plant from BP01 to 1000 , Storage Locations etc.. I want to send data like Material Master , BOM , Routing , WorkCenter etc... Can you tell me how to do it with the changes like Plant , SLoc in Receiving System .

Regards,

Bintu

[Former Member]

Buddy, the system won't consider the breakpoint in case of Inbound Idoc as it is done automatically in background according to the Message type and process code settings. U can debug it through WE19 only by executing the idoc manually again. Think logically, why would the system stop at ur breakpoint when u didn't intiate a process.

[Former Member]

thanks,

thats clear..

but my issue is stil not cleared..

here i want to add my own code ..so for this i found on exit EXIT_SAPLMV02_002

the importing and exporting parameters are here.

"Lokale Schnittstelle:

*" IMPORTING

*" VALUE(MESSAGE_TYPE) LIKE EDIDC-MESTYP

*" VALUE(F_CUST_SEGMENT) LIKE EDIDD STRUCTURE EDIDD

*" TABLES

*" RES_FIELDS STRUCTURE DELFIELDS

*" CHANGING

*" VALUE(F_MARA_UEB) LIKE MARA_UEB STRUCTURE MARA_UEB

*" OPTIONAL

*" VALUE(F_MAKT_UEB) LIKE MAKT_UEB STRUCTURE MAKT_UEB

*" OPTIONAL

*" VALUE(F_MARC_UEB) LIKE MARC_UEB STRUCTURE MARC_UEB

*" OPTIONAL

*" VALUE(F_MARD_UEB) LIKE MARD_UEB STRUCTURE MARD_UEB

*" OPTIONAL

*" VALUE(F_MFHM_UEB) LIKE MFHM_UEB STRUCTURE MFHM_UEB

*" OPTIONAL

*" VALUE(F_MPGD_UEB) LIKE MPGD_UEB STRUCTURE MPGD_UEB

*" OPTIONAL

*" VALUE(F_MPOP_UEB) LIKE MPOP_UEB STRUCTURE MPOP_UEB

*" OPTIONAL

*" VALUE(F_MPRW_UEB) LIKE MPRW_UEB STRUCTURE MPRW_UEB

*" OPTIONAL

*" VALUE(F_MVEG_UEB) LIKE MVEG_UEB STRUCTURE MVEG_UEB

*" OPTIONAL

*" VALUE(F_MVEU_UEB) LIKE MVEU_UEB STRUCTURE MVEU_UEB

*" OPTIONAL

*" VALUE(F_MARM_UEB) LIKE MARM_UEB STRUCTURE MARM_UEB

*" OPTIONAL

*" VALUE(F_MEAN_UEB) LIKE MEA1_UEB STRUCTURE MEA1_UEB

*" OPTIONAL

*" VALUE(F_MBEW_UEB) LIKE MBEW_UEB STRUCTURE MBEW_UEB

*" OPTIONAL

*" VALUE(F_MLGN_UEB) LIKE MLGN_UEB STRUCTURE MLGN_UEB

*" OPTIONAL

*" VALUE(F_MVKE_UEB) LIKE MVKE_UEB STRUCTURE MVKE_UEB

*" OPTIONAL

*" VALUE(F_MLGT_UEB) LIKE MLGT_UEB STRUCTURE MLGT_UEB

*" OPTIONAL

*" EXCEPTIONS

*" APPLICATION_ERROR

*"----

---

INCLUDE ZXMGVU04.

when iam executing function module idoc_input_matmas01.and putiing break point in that exit

but for importing parameters F_CUST_SEGMENT it is showing empty..

here iam not passing any values to F_CUST_SEGMENT,because the function module idoc_input_matms01 should call this exit and pass importing parameters..

[Former Member]

Hi Ajay,

how this idoc_input_matmas01 is triggerd?

there are 3 steps to assign the Inbound func module

1. BD51- ale attributes( attaching the fm here )

2. WE57- attaching the Message type, Idoc type to the fm

3. WE42- assigning the 4 letter Process code to the fm (the process code points to this fm )

While maintaining partner profiles WE20 add the Inbound parameters ,

here the Process code refering to the fm is assigned and so the Inbound FM gets triggered..

Regards,

Mdi.Deeba

[Former Member]

means,

here when ever material is received this will trigger,

iam putting break point in that funtion module(idoc_input_matmas01)

iam uing tcode bd11 but iam not going to debugg mode.

[Former Member]

Have you created inbound parameters(Message Type) for partner profile(WE20) and assigned a process code to that Message type. With that process code you have to attach an FM which will process your inbound IDoc.

[Former Member]

yes,

here inbound process code in MATM

and function module attact to it is 'IDOC_INPUT_MATMAS01'.

there are standard ones .

[Former Member]

run WE19 in ur receiving system, put your received IDoc No. and press execute. then select the idoc and press button "Inbound Function module", enter ur FM name, and select "Foreground processing" and it will start debugging for the given FM.

[Former Member]

ok,i understood ,

here in receiveing receiving system i want to add some custom code ,

im my case in SENDING SYS material type is FERT and IN RECEIVING SYSTEM material type i HAWA.

i want to do such mapping in receiving side..

i found one exit for it EXIT_SAPLMV02_002.

till now i didn't write any code ,but put a break point in it and i want to test it,but this break point is not triggering,

is that exit is correct ,if than how can we test that exit.

[GauthamV]

Use WE19 or BD87 transaction.

[Former Member]

thanks for u r reply,

but can u explain me how the idoc is received in inbound and when this function module idoc_input_matmas01 is triggered ,,

here we have to execute tcode bd11 ?

or it automatically updates..