topic Re: Trigger condition for IDOC in Application Development and Automation Discussions

Trigger condition for IDOC

Former Member — Wed, 05 Aug 2009 11:20:30 GMT

Hi,

I have trigger condition for IDOC

All materials where:

"Finished Goods" Technical Names MARA-MTART = "Z001", and the Plants are "Granollers" MARC-WERKS="ES11", MARC-WERKS="ES12", goods that are "ready" or "ready for manufacturing", MARC-MMSTA = "02" or "03".

All the materials which satisfy this criteria will need to be triggered whenever a new material is created in SAP which meets the above criteria, or if any materials are modified which meet the above criteria in SAP.

How do I trigger my IDOC based on these conditions.

Regards,

Subhashini

Re: Trigger condition for IDOC

Former Member — Wed, 05 Aug 2009 11:25:21 GMT

Hi,

you can add the filter condition to idoc in BD64 transaction to control the trigger.

Thanks

kamath

Re: Trigger condition for IDOC

Former Member — Wed, 05 Aug 2009 11:28:44 GMT

Hi,

First you have to fill the your data into a table which is like the structure of EDIDD.Here you have to fill the all segmetns in the sequence which defined in the idoc type only other wise you will get error 26.

Then pass the control record data in the structure like EDIDC here you have to fill the sender,receiver,partner profile,idoc type message type like stuff.

Then pass these table and structure to the function module MASTER_IDOC_DISTRIBUTE.

Then idoc will created by above funciton module.

If you want pass data in xml format then you have to create xml port in we21 and pass this port name in the EDIDC structure.

Thanks & regards,

ShreeMohan

Re: Trigger condition for IDOC

Former Member — Wed, 05 Aug 2009 12:39:36 GMT

Hi,

Please create the Idoc type / segments , create message type and link Idoc and message.

Steps to customize a new IDoc >>>

1. Define IDoc Segment (WE31)

2. Convert Segments into an IDoc type (WE30)

3. Create a Message Type (WE81)

4. Create valid Combination of Message & IDoc type(WE82)

5. Define Processing Code(WE41 for OUT / WE42 for IN)

6. Define Partner Profile(WE20)

2. Yes, you need LS & Partner profile

3. Yes use MASTER_IDOC_DISTRIBUTE

4. Can use IDOC_CREATE_ON_DATABASE instead of MASTER_IDOC_DISTRIBUTE and then process the Idoc.

Message Type :: The message type defines the semantic context of an IDoc. The message type tells the processing routines, how the message has to be interpreted. The same IDoc data can be sent with different message types.

IDoc Type :: An IDoc type defines the syntax of the IDoc data. It tells which segments are found in an Idoc and what fields the segments are made of.

Processing Code :: The processing code is a logical name that determines the processing routine. This points usually to a function module, but the processing routine can also be a workflow or an event.

The use of a logical processing code makes it easy to modify the processing routine for a series of partner profiles at once.

Partner profile :: Every sender-receiver relationship needs a profile defined. This one determines

The processing code
The processing times and conditions
In the case of outbound IDoc 1. The media port used to send the IDoc and 2. Triggers used to send the IDoc

Partner Type :: The IDoc partners are classified in logical groups. Such as : LS, KU, LI.

LS - Logical Systems : It is meant to be a different computer and was primarily introduced for use with the ALE functionality.

KU - Customer : The partner type customer is used in classical EDI transmission to designate a partner, that requires a service from your company or is in the role of a debtor with respect to your company, e.g. the payer, sold-to-party, ship-to-party.

LI - Supplier : The partner type supplier is used in classical EDI transmission to designate a partner, that delivers a service to your company.

thanks & Regards,

ShreeMohan

Re: Trigger condition for IDOC

Former Member — Tue, 11 Aug 2009 06:10:30 GMT

Self answered.Thanks evryone.