topic Re: IDoc Problem. in Application Development and Automation Discussions

IDoc Problem.

Former Member — Tue, 18 Dec 2007 11:19:39 GMT

i am trying to update invoice throught a z function via idoc. This works good if i try to post it through we19. but when the idocs are directly inbound from external system this fails. and give the below error.

“Entry too long (please enter in the format ____.__.__ ) “

but if process the same idoc using we19 it gets posted.

Further to add on if try to re post this with program rdbinput then i also gets posted but if i try to use the same program in background job the again gets the same error.

so a bit confused. can anybody help here.

Re: IDoc Problem.

former_member404244 — Tue, 18 Dec 2007 11:28:15 GMT

Hi,

what i feel is when the idoc is coming directly from external system,the date format is different and when u r using in WE19,it might be different...kindly check the same...try to use the same format and check..

Regards,

Nagaraj

Re: IDoc Problem.

Former Member — Tue, 18 Dec 2007 11:50:08 GMT

thanks for reply.

but if try to re´post the same external idoc via we19 it gets posted... so the data in both the case is same ... then why it only fails when it directly inbound or when these are executed in background.

Re: IDoc Problem.

Former Member — Tue, 18 Dec 2007 12:56:31 GMT

Hi Hema ,

Please check the Partner Profile in WE20 .Check process code and Function module .

Re: IDoc Problem.

Former Member — Tue, 18 Dec 2007 13:30:30 GMT

thanks!! they are perfect ... in dont think there is any problem ....

Re: IDoc Problem.

Former Member — Thu, 14 Feb 2008 09:49:12 GMT

After looking in sap notes found that this is standard bug in 4.7. and all our exploration to resolve this leaded us to only one solution and that was to service pack upgrade. This was not a wise acitvity so i had to scrap by bdc in idoc and wrote a bapi to accomplish my task.

So if bdc is failling in background mode (i had this probelm in sap 4.7) or via inerface from external system then better write a BAPI or direct table update (not recommended).