topic Re: Inbound IDoc Error in Application Development and Automation Discussions

Inbound IDoc Error

Former Member — Mon, 31 Jan 2011 20:36:58 GMT

The Inbound IDoc reaches SAP system successfully. But it does not get posted successfully. Below given are the details of my IDoc in WE57:

BAPI_IDOC_INPUT1 - Function module (Standard)

ACC_GL_POSTING01 IDoc Type

ZACC_GL_POSTING - Msg Type

Process Code - BAPI

Also assigned Logical Message to Process Code BAPI in WE57. I made all possible needed entries correctly from my knowledge.

But still I get the below error: Inbound IDoc Error 51: The IDoc interface is not complete for message type ZACC_GL_POSTING.

Do I have to maintain some entry in WE27 - Proposal for Inbound Partner Profiles?

For my partner type, the WE27 gives the below 6 entries ONLY:

DEBMAS Customer master data distribution

FTDABA Foreign trade: Data service basic data

FTDACO Foreign trade: Data service customs conditions

FTDACU Foreign trade: Data service customs data

MATMAS Material master

WHSCON Delivery: Stock confirmation

Any suggestions?

Cheers........

Re: Inbound IDoc Error

former_member186741 — Tue, 01 Feb 2011 01:57:52 GMT

have you got an inbound process code entry via WE42?

Re: Inbound IDoc Error

Former Member — Tue, 01 Feb 2011 04:57:01 GMT

There are few table entries required for the Inbound FM and process code, Custom Message and Basic Types mapping etc.

Follow the steps and all the transactions:

http://www saptechnical com/Tutorials/ALE/DataDistributeCustomIDOC/page1.htm

Re: Inbound IDoc Error

Former Member — Tue, 01 Feb 2011 14:26:05 GMT

Hello Neil

I have not got Process Code in WE42. My understanding was that we can use the std process code BAPI as we are calling the std BAPI.

So, I made an entry in WE57 with below values and in Partner Profile, I assigned the Process Code BAPI only.

BAPI_IDOC_INPUT1 - Function module (Standard)

ACC_GL_POSTING01 IDoc Type

ZACC_GL_POSTING - Msg Type

Process Code - BAPI

Was I wrong? Do I have to create a new Process Code for this as well?

Cheers

Re: Inbound IDoc Error

Former Member — Tue, 01 Feb 2011 14:41:19 GMT

Why don't you try it with a 'Z' process code (something like ZBAPI) in WE42... You do have a custom message type and you can see that process code BAPI is linked to multitude of logical messages like ACC_BILLING , ACC_INVOICE_POST... I am not sure if this plays a role, but you can try with a new process code and see if it gets called or link your Z message type to the process code in WE42

Re: Inbound IDoc Error

Former Member — Tue, 01 Feb 2011 15:33:13 GMT

I tried creating custom process code ZBAPI and assigning logical message ZACC_GL_POSTING to it. Still I get the message: The IDoc interface is not complete for message type ZACC_GL_POSTING.

While debugging, I could find that an entry against my custom message type is missing in TBDBE / TBDBA tables.

Could anyone guide me how to have an entry in TBDBE/TBDBA table for my custom message type?

Cheers!!

Re: Inbound IDoc Error

Former Member — Tue, 01 Feb 2011 20:05:37 GMT

Did you generate the BDBG entry for your Business object? Please check out the following entries..

http://help.sap.com/saphelp_40b/helpdata/en/78/21740f51ce11d189570000e829fbbd/content.htm

Re: Inbound IDoc Error

Former Member — Tue, 01 Feb 2011 20:18:04 GMT

Hi Kris

Thanks for reply. But, in BDBG, I tried to create the ALE interface already. I had faced the below issues:

BDBG asks for 2 inputs: 1) Object / Interface Type and 2) Method.

I could not find the correct Object / Interface Type for BAPI_IDOC_INPUT1.

Where can I find the same? is it from Process Code?

Or, should I create ZBAPI_IDOC_INPUT1?

Below is my object details:

BAPI_IDOC_INPUT1 - Function module (Standard)

ACC_GL_POSTING01 IDoc Type

ZACC_GL_POSTING - Msg Type

Process Code - ZBAPI

I already have created the message type. Can I use it?

Cheers!

Re: Inbound IDoc Error

Former Member — Tue, 01 Feb 2011 20:42:25 GMT

BDBG entry already exist for BAPI BAPI_ACC_GL_POSTING_POST. Is there a reason, you want to use custom message type?

For IDOC type ACC_GL_POSTING01, Message type already exist ACC_GL_POSTING and IDOC FM IDOC_INPUT_ACC_GL_POSTING... I don't know if you need to create a new message type...

As long as you are maintaining WE57 entry for the combination of IDOC_INPUT_ACC_GL_POSTING to the message type ACC_GL_POSTING and create WE42 entry for custom process code (you could use some thing ZGL_POST) and also the BD51 entry, it should work.

Re: Inbound IDoc Error

Former Member — Tue, 01 Feb 2011 21:01:51 GMT

One small correction. My WE57 entry is:

BAPI_IDOC_INPUT1 - Function module (Standard)

ACC_GL_POSTING01 IDoc Type

ZACC_GL_POSTING - Msg Type

And, using WE19, I created an inbound IDoc based on my custom message type ZACC_GL_POSTING and I could see in debugging that it checks TBDBE and TBDBA tables to see if there is an entry against it.

Having no records found, it failed to:

Error 51 - The IDoc interface is not complete for message type ZACC_GL_POSTING.

Message no. B1500

What is the way that I can have an entry in TBDBE or TBDBA with the following:

MESTYPE              METHOD              IDOCTYPE                  FNAME_INB

ZACC_GL_POSTING        POST            ACC_GL_POSTING01       BAPI_IDOC_INPUT1

Cheers!

Re: Inbound IDoc Error

Former Member — Tue, 01 Feb 2011 21:23:11 GMT


> One small correction. My WE57 entry is:
> 
> BAPI_IDOC_INPUT1 - Function module (Standard)
> ACC_GL_POSTING01 IDoc Type
> ZACC_GL_POSTING - Msg Type
> 
> Cheers!

I don't think you can have entry for the Same method of the object unless you are going to copy the Business object BUS6030 to a Z Object... Further why do you need a custom message type?

Please note that BAPI_IDOC_INPUT1 just calls another FM, which has to be maintained in TBDBE/TBDBA table... You will also notice that message type ACC_GL_POSTING does exist in table TBDBE/TBDBA... Unless there is a specific reason, I don't see the need to maintain a custom message type...

Since ACC_GL_POSTING does not appear to be tied to the BAPI process code, I would create a new process code to link IDOC_INPUT_ACC_GL_POSTING to message type ACC_GL_POSTING01 and see if it would work out.. You can always tie the message type ACC_GL_POSTING01 to the BAPI_IDOC_INPUT1 FM (and I would guess that it would also work)..

Re: Inbound IDoc Error

Former Member — Thu, 03 Feb 2011 16:53:51 GMT

Thank you all!