topic Re: one problem with IDOC. in Application Development and Automation Discussions

one problem with IDOC.

Former Member — Wed, 06 Aug 2008 02:27:51 GMT

Hi All,

I am sending data between 2 clients.

Client 800 is sending system and client 850 is receiving system.

When i send the data in Client 800, it seems all the things are ok.

I check this within T-code BD10 in client 800.

It gives below message:

-1 master IDocs set up for message type MATMAS

-1 communication IDoc(s) generated for message type MATMAS.

Then I checked this IDOC within T-code WE05 in client.

The status of this IDOC is 03.

It seems all the things are ok in client 800.

But a problem occours in client 850.

I checked this idoc within T-code WE05 in client 850.

The status of this IDOC is 51.

Anyone can tell me why?

Thanks in advance!

Re: one problem with IDOC.

Former Member — Wed, 06 Aug 2008 02:50:23 GMT

Hi Yijie,

IDOC Status 51 means an error.

see this links which explains how the idoc proceeds, both inbound and outbound idocs are shown.

Are you using IDES?

Status 51 just means there's "something wrong".

There are very many different types of idocs, but even for one type this

status can have many causes.

You've got just one option, go into the idoc and see the more detailed

error information you'll find there.

There are many kinds of errors.Example: It could be a syntax issue or the master table may not containeither the material or partner in the idoc.Depending on the idoc if youedit and correct the same and reprocess the edited idoc it should createthe necessary Doc.

Check the log linked to the status 51, it will tell you exactly what itis.

For sure, there is a field defined in the field status account group as

required that is not in your IDOC. Other possibilities are that somefield

value that you want to assign is not defined in customizing (industrycodes,

transportation zone, ...).

Using WE19 or BD87 tcodes, you can reprocess them in foreground or even

foreground / all screens, such as for BDCs. This way, you will see ifthere is

a field missing or a wrong value.

Please check your partner profile and the port definitions.... SAPsystem is

not able to call the binary on your subsystem...using rfcexec...

Check outbound parameter of sender system and Inbound parameter of target system and process code for matmas.

Process code should be matm for matmas.

Please check if you have proper write permissions on the subsystem inthe

particular directory where u are trying to write the file or Idoc...

Try with someone's login who has the authority of SAP_ALL.

Just have a look on the possible causes.

Use BD87 tcode or report RBD00.

We19 for testing do it in the foreground.

also check the status record what does it says..

Mohinder

Re: one problem with IDOC.

Former Member — Wed, 06 Aug 2008 05:59:21 GMT

HI,

Just take the IDOC number from WE05 ( client 850 ) and process the IDOC in WE19.

Thanks,

Re: one problem with IDOC.

Former Member — Thu, 07 Aug 2008 07:16:32 GMT

Hi,

Idocs Status 51 means Application document not posted.

First try to find the error which idocs has been failed.You can find the error through application log.

Goto Status records -> double click the status 51 -> Application log (Shift+f8)..

There is no problem with the client (850)..

Regards,

Karthik..

Re: one problem with IDOC.

Former Member — Thu, 07 Aug 2008 08:53:07 GMT

Hi ALL,

Thanks for your suggestions.

I checked the status record of my IDOC.

The error message is as below.

Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT

Any good idea from all of you?

Best regards,

Yijie

Re: one problem with IDOC.

Former Member — Thu, 07 Aug 2008 08:57:42 GMT

You can create custom function module to process the Inbound IDoc and post data in Client 850.

Re: one problem with IDOC.

Former Member — Thu, 07 Aug 2008 09:29:13 GMT

hi,

do you using "MATMAS" or "ARTMAS" ? Industry or Retail ?

Settings for ARTMAS:

please be sure that the sender system is configured for RetailMaterial.Clone as BAPI in the Sender Distributionmodel (Tcode: BD64)

The Receiving System should use the ProcessCode "BAPI" in the Partnerprofiles (Tcode: WE20)

please check this first !

Settings for MATMAS

please be sure that the sender system is configured for MessageType "MATMAS" in the Sender Distributionmodel (Tcode: BD64)

The Receiving System should use the ProcessCode "MATM" in the Partnerprofiles (Tcode: WE20)

Edited by: Gordon Breuer on Aug 7, 2008 11:30 AM