automatic IDOC generation !

[Former Member]

How to automate an idoc generation when the credit memo is created !

Can any one tell me the approach and the steps !

[Former Member]

Hi,

Check this IDOC type : GSVERF01.(TCODE: WE60 or WE30)

IDOC for credit memo can be created by this.

Reward if helpful.

Regards,

Ramya

[Former Member]

Can I automate the process of creation of IDOC...

i mean when the credit memo is created an IDOC will be generated !

[Former Member]

Any one can tell me the steps for automation ?

[shivhare]

Hi Jyotirmoy Deb

Go to transaction code MRM1 put output devices ERS6 vin key combination select select company code /invoice invoicing Party put vendor or other party number that you want to generate invoice

In partner function select your partner type in case of vendor select VN

In medumof transaction select 6 for EDI

In date time select 4 for Send immediately (when saving the application)

Thanks

Amit Shivhare

PS: Reward point

[Former Member]

Hi,

You dont need to write a code in userexit, just check this IDOC type : GSVERF01.(TCODE: WE60 or WE30)

Thru this you can create an IDOC for Credit memo.

Thru message control option we can achieve that.

Read this.. it will help u.

Message Control

The objective of Message Control is the exchange of information between various partners and the launching of subsequent processing that is partner-independent. Message Control provides interfaces to make this possible.

You can use the Message Control interfaces to describe various data combinations along with the required processing. If one of these data combinations is found to be applicable during the processing of an application object, the appropriate processing is started (synchronously or asynchronously).

Message Control is a "service program" for other applications. It is initiated via ABAP function modules. Information about which programs carry out the subsequent processing is managed in tables . The conditions determining when programs are called are often very complex and also depend on the individual customer situation. Message Control offers the flexibility needed to represent these various situations .

Purpose

The output or follow up processing of partner-dependent messages is automated via Message Control. The application then calls the Message Control via the specified interfaces.

You can use these interfaces to describe various data combinations along with the required processing. If one of these data combinations appears during processing, the appropriate processing is started (synchronously or asynchronously). You can define processing with several different methods, for example as a workflow, print output or as an IDoc dispatch for EDI.

Implementation considerations

SD and MM applications always use Message Control for message output. You carry out Customizing of the Message Control in the application’s Customizing. The Message Control is also sometimes described here as "output control".

Integration

Message Control is a "service program" for other applications. It is initiated via ABAP function modules. An application that uses Message Control must

Call the Message Control

Transfer files which should be compared with the combinations defined in Customizing.

Provide a processed program, that is called from the Message Control, if the transferred data corresponds with the combinations defined in Customizing

Features

The condition technique in the R/3 System is used to formulate the data combinations required. If the current application data corresponds to the conditions defined in Customizing, message determination was successful and created a message default. If the application supports it, the proposal can be changed (processed).

As a result the message is processed immediately or at a defined time. The processing status of the message is stored in a status record. If the application supports it, a processing log is written as well.

Message Control scenarios:

1. The credit limit has been exceeded in a sales order, whereupon the block indicator is assigned. The Message Control should respond to the block indicator by printing out this customer’s account history.

2. A document is released and receives a corresponding status in its data record. The Message Control should thereupon issue a release message.

There are also applications which can "switch off" message determination and directly generate the message default.

Structure

Condition Components and Condition Records

The individual objects of the Message Control which are relevant in the message determination process and can be configured in Customizing or the application transaction are explained.

Message determination

This section describes how the condition component hierarchy is evaluated and how the condition tables are accessed. Different scenarios, which can be realized by special strategies when Customizing the condition component, are used as examples.

Message Default and Message Editing

The result of message determination is a message default that can be edited manually in the application, if this function is available in the application. If not, any messages found are forwarded directly for automatic processing.

Message processing

This explains how the message found can be processed.

Regards.