IDOC INBOUND Error !

[Former Member]

Actually I received a test IDOC ( FIDCCP02) from middleware see beyond, when it was dropped in our R/3 Box. it has a status 51 - Application Document not posted ( the application failed to return a status record to the ALE layer )

I tried to reprocess with prog. RBDMANIN it didn’t worked and I tried BD87 but it says: this is due to an error in the application function module which processed the inbound IDOC.

Then, I tried to post the IDOC through WE19 with particular IDOC number, the test IDOC has been created and it is surprisingly posing data to custom segment ( user exit developed for particular IDOC extension ), Actually this custom segment has diverted to custom table. But it is not posting standard segments data to standard tables.

As per my understanding it is posting the data for the user exit which I developed in FM. But the FM is not triggered properly for the standard segments. May be FM executing only user exit developed for IDOC extension .

can some one pls tell me what is the problem behind this ? Appropriate suggestions would be appreciated.

[Former Member]

check with partner profile - whether you are maintaing correct one like process code ,if you get 51 status then it will be problem at WE20 Transaction

[Former Member]

Hello Sridhar,

i got same issue for sales order inbound ,when you fill the data wrongly in partner profile or in we19 transaction ( EDIT->control records) ,try to look these areas ,if not then Function module problem

[Former Member]

Seshu,

Thank you.

yes checked it with partner profiles, in WE19 by giving the existing idoc number and click on standard inbound option on the menu, it indicates green light, that means partner profiles or correct right ? or do you think it may show like that ?

if problem with the function module, what could be the problem ? whether the user exit which i developed interpreting the triggering of FM ?

actually i receiving IDOC from see beyond, so created RFC destination for See beyond with TCP/IP Connection, with connection type: T & i used same Program ID which they used at Outbound R/3 system .

Pls suggested me accordingly

Regards,

Sridhar

[Former Member]

just comment ur user exit code and see the results ,still if you get 51 then partner profile or we19

[Former Member]

Thanks seshu. Points awarded.

will try in that way by commenting user exit.

But my concern is, if pratner profiles are wrong , it should not be populated in custom segment also right ? my custom segment is populated only when tried to post throught WE19 only .

apart from it, what could be the problem do you think with FM ?

Regards,

Sridhar

[Former Member]

in my practise! I knew that ..some user exits will be triggered after database(std segments) updation others b4 db updation. urs is triggered b4 database updation. so your custom segment updates custom table first. then cntrl goes to std segments.

i think problem with data. edit it in we19.

(am new to ale/idoc...correct me if am wrong)

[Former Member]

Seshu,

I tried by commenting user exit, now the control goes to standard segments, but is it not posting due to some data mismatch problem.

Now I am wondering why the control moving to main segmeants after commenting user exit. it this exit interpreting the main FM functionality ? what should be the ideal case, updating custom table first ? or updating the DB table ?

Regards,

Sridhar

[Former Member]

Venkat,

thank you.

whether this functionality of updating DB table first before updating Custom table and other way around, depends on user exit we are using ? it is standard by SAP ?

IDOC as follows:

FIDCC2 / FIDCCP02, FM :IDOC_INPUT_FIDCC2, EXIT: EXIT_SAPLF050_006 (exit 005/006)

Regards,

Sridhar

[Former Member]

we can't change the time of triggering user exit(customer exits). it's standard.

as per ARAVIND NAGPAL,book, for customer master the exit (provided by sap) will be triggered after db updation (stnadrd segments ). but it's reverse for material master.