topic Problem with RBDMANI2 in Application Development and Automation Discussions

Problem with RBDMANI2

Former Member — Fri, 09 Oct 2009 05:40:29 GMT

Hi,

We have scheduled RBDMANI2 (1 hr) for posting error idocs,but the problem is with the custom inbound function module which actually creates BDC session for posting .

So each time when RBDMANI2 tries to re process the error idocs which have status 51,it creates that much session as well.

We would like to avoid the creation of sessions each time when RBDMANI2 tries to re process the same error IDOCS.

Please suggest some ways.

Re: Problem with RBDMANI2

Former Member — Fri, 09 Oct 2009 09:31:03 GMT

I'd say this is more a design issue of the custom function module. I.e. why is the custom function module creating BDC sessions and leaving the IDoc in status 51? As you mention, it seems wrong to create a BDC each time you'd reprocess the IDoc. So if the IDoc should remain in status 51, then the function module doing the IDoc processing should at least not create a new BDC each time (unless for example some data changed). So I'd say it's time to take another look at the requirements for the IDoc processing...

Maybe you should just change the function module for the IDoc processing to simply use CALL TRANSACTION instead of creating new BDC's.

Re: Problem with RBDMANI2

Former Member — Fri, 09 Oct 2009 10:11:02 GMT

Thanks for the reply ...Ok ,if the IDOC is not posted and is in status '51' with reason "Some 0000 plant not exist"

then what should be done.

Whether the master data should be maintaned and then error idoc to be processed ,then we can avoid the sessions which are getting creatd when error idocs are re processed.?

As currently no actions are being taken to maintain it is what I have got answer from our functional contact.Please advise

Re: Problem with RBDMANI2

Former Member — Fri, 09 Oct 2009 13:00:55 GMT

Not sure I understand the question, so I apologize for probably stating the obvious: If the business doesn't require creation of BDC's in case of errors, then most likely the function module should be changed to use CALL TRANSACTION and not to produce any BDC's. You'll have to discuss such options with the functional consultant though.

Also, it's clear that somebody has to be responsible for monitoring and correcting errors...