Material master/Output type IDOC /MATMAS

[Former Member]

Hello ,

I want to generate Idoc(MATMAS) whenever a material is created or changed. I could do the same for ME21N/ME22N for PO with PO idoc. Would like to know whether there is output types for material master or anything else so that i can generate Idoc for my senario.

Thanks for ur time.

Jeeva.

[rainer_hbenthal]

Activate Change Pointer in general in SALE, then activate particular change pointer in BD50. If you want to transport changes goto BD21 and release the changes creating idocs.

Hopefully the rfc connection is done... SM59, WE20, WE21, BD64

[former_member404244]

Hi,

the configurations which we do for material master is below...we don't give any output for material master,becoz its a master data not transactional data..

For distributing master data like material master, vendor master, customer master we have standard transaction codes that are provided by sap.

Bd10(send material master)

Bd12(send customer master)

Bd14(send vendor master)

Bd30(bom’s)

The order of Tcodes are:

Bd54 (creating logical systems)

Scc4 (assigning logical systems )

Sm59 (rfc destination)

We81 ( message type)

We30 ( idoc type)

We31 ( segment type)

We82 (linking message type and idoc type)

We21 (creating port)

We20 (partner profiles)

Bd64 (Distribution model)

Bd10 (material master)

Ex: material master.

Message type: matmas.

Idoc type: matmas05.

Rewrad if helpful.

Regards,

Nagaraj

[Former Member]

Thanks a lot for ur replies .

I do understand the BD10 and other tcodes for master's and other general ALE /IDoc configurations. The senario im working on is , the volume of material creation and change is very high daily and i would like to go for a automatic trigger of IDOC from MM01 or MM02 .

Would like to know how i can achieve this ??

Sure points for right solutions....

Thanks,

Jeeva.

[Former Member]

Hi,

Schedule (job using SM36) the program RBDMIDOC with a variant (Message type 'MATMAS'). The frequency depends on your requirement (daily/hourly).

Thanks,

Amit Jain