topic Idoc extension in Application Development and Automation Discussions

Idoc extension

Former Member — Tue, 22 May 2007 06:49:41 GMT

Hi all,

I have to do payment run so that the output is in the form of Idoc (PEXR2002).

I need to enhance the idoc as well to include few customr specific fields.

I dont know what is the procedure for finally getting a output as Idoc in We02.

Please help

Re: Idoc extension

Former Member — Tue, 22 May 2007 07:18:03 GMT

HI Srinivas,

YOu need to identify the application which is going to trigger your idoc. (Payment run in this case).

Determine what method will you use for triggering the idoc: Change pointer activation or Output Control.

The above two points would be helpful in triggering the idoc and gettign the output in we02.

As far as enhancing the idoc is concerned, you need to add Z segments to your idoc.

Go to transaction WE31. Give your segment name and say create. Add the customer specific fields and then activate the segment. After activating the segment, go to menu, Edit-> SEt Release. This would release your segment so that its ready to get attached to idoc.

Then add this z segment to your basic idoc type . (tcode we30).

Next, you need to search application specific exit (specific to your idoc type), wherein you can populate data in the customer fields.

You try and go ahead with developement and revert as an when required.

Hope this helps.

Pls reward some points if helpful.

Regards,

Karan

Re: Idoc extension

Former Member — Tue, 22 May 2007 07:18:15 GMT

Revert if any issues

null

Re: Idoc extension

Former Member — Tue, 22 May 2007 09:26:29 GMT

Hi karan,

It is said that 3 std report programs populate the Idoc. i am not sure that the idoc will be filled only after running the payment run.If it is so,letme know.

If any of the report fills the idoc then how will the customer specific fields be filled?

Re: Idoc extension

Former Member — Tue, 22 May 2007 09:42:14 GMT

Hi,

If its triggering of idoc through "Change Pointers Activation", then the report RBDMIDOC populates the data and triggers the same. If it is through "Output type", then the report RSNAST00 popultes and triggers the idoc.

The two reports i just mentioned are generic for all the idoc types. However, for each application, there are application specific reports to trigger the specif idoc.

And all the idocs are triggered only when the application to which they are attached, does some functionality. For example, when you create a vendor, then idoc cosmas gets triggered. When you create a material , then idoc type MATMAS gets triggered. In the same way, the idoc type which you are extending ( or enhancing) has an application attached to it, which will populate the idoc. The triggering can either be immediate or by running the above mentioned reports. (The triggering methods also depend upon the partner profile configurations)

Now, when these idocs are triggered through the reports (generic or application specific), they call standard customer exits. YOu need to find out the exits specific to the application. Every application, which has an idoc type attached to it, has a customer exit, which allows user to fill in the extra fields added as an extension. If you want, then i can send you the list of all the idoc types and the corresponding exits.

Hope this cleared your understanding.

Pls reward if useful.

Revert in case of issues.

Regards,

Karan

Re: Idoc extension

Former Member — Tue, 22 May 2007 09:50:20 GMT

Hi Karan,

It would be nice if i get the list of idoctypes and their exits.

It would clear my doubt in a more better way.Points have already been rewarded.

Thank you,

Will get back to you when required.

Re: Idoc extension

Former Member — Tue, 22 May 2007 09:52:05 GMT

Hi karan,

Plz send th elist on srinivas1984@gmail.com ASAP.

Thank you.

Re: Idoc extension

Former Member — Tue, 22 May 2007 09:56:03 GMT

Check your mail,

Have sent you the document

Regards,

Karan