Idoc status error 37 in sender and 51 in recieving system

i m new to ale idoc n created 2 clients 910(sender system) and 800(reciever system)
all connections are well i got status message 03 and 30 and 01 but along with it i m getting one more idoc genersted and status as 37 . idoc no. 50 as 03 30 and 01 and idoc 51 as 37 . in sender system n inreciever system i m not getting idoc.after sumtim i m getting them n error status as 51 .two idocs are generated simultanously.
does the port name we21 should be same i m using same port name currently .
clnt910 --rfc800 destination client 800 (sender system).
clnt800 --rfc800 destination client 910 (reciever system).
when i m changing the port name i m getting error status as 29 .
we20 both the partner profile are active

Hi,
You Outbound IDOC is not correctly formatted I think, check the segments whether they are correctly added or not.
Thanks,
Mahesh.

Similar Messages

Real Time Clock Error - Check Date and Time settings, System CMOS Checksum bad

Hello everybody,
Can help anyone to resolve my problem.
I have an Thinkpad W520 (42823FG), BIOS 8BET60WW 1.4 When I disconect AC power and remove battery and connect again, I see this message on screen:
"Real Time Clock Error - Check Date and Time settings, System CMOS Checksum bad
Press Esc to continue or F1 to enter Setup"
Is this a system board problem or CMOS battery problem ?
Thank you

Hello and welcome,
It's probably (hopefully) just the CMOS battery. The easiest way to find out is to just replace that battery.
Page 85 of the Hardware Maintenance Manual:
Hardware Maintenance Manual
Here's an example of the battery. I'm not recommending (or not) this vendor:
http://www.ebay.com/itm/New-Lenovo-ThinkPad-W500-W510-W520-W530-W700-W701-W701ds-CMOS-RTC-Backup-BAT...
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

IDOC: Status (Error/Success/information)report to Sender system

How would one send a message(error/success/information) to the sending(external) system to inform them of the statuses of the messages they've sent to our SAP system?

Hi Baumann,
you have an option called Audit reporting in which you can have the status of idoc at sender side.read the following.
Setting Up Audit Reporting
In the default behavior, after an IDoc is dispatched to a destination system, the sender does not know the state of the process on the destination system. You can configure the system, however, for cross-system reporting. You must model the ALEAUD message between the systems.
Two programs enable cross-system reporting.
1)RBDSTATE. This program is scheduled to run periodically on the destination system. It reports the status of incoming IDocs to the sending system, using the ALEAUD message and ALEAUD01 IDoc. This status information is recorded separately from IDoc status information in the audit logs.
2)RBDAUD01. This program is executed on the sending system. It analyzes the audit log and displays the output as a report.
The RBDSTATE program returns the following statuses, from the receiving to the sending system.
RBDSTATE Is Run on the Receiving System
Status of IDoc in receiving system     Status reported to sending system via ALEAUD
53 (Application document posted.)     41 (Application document created in receiving system.)
51 (Error: Application document not posted.)     Status 39 (IDoc is in the receiving system.) This status is repeated each time RBDSTATE is run, as long as the IDoc remains in status 51.
68 (Error: No further processing.)     40 (Application document not created in receiving system.)
reward points if helpful,

IDoc status error 51 : A company code cannot be determined for LS

Hi,
We are trying to post an Idoc into R/3 but getting the IDoc status code 51 : A company code cannot be determined for LS
What could be the possible reason?
Should we use Party in Receiver IDoc scenarios?

Hi,
I have quite the same problem. I built an IDOC with WE19 and I have the message "A company code cannot be determined for LI 0000031004".
As explained in note OSS 117808, the partner number (31004) and partner type (LI) are read from the control record of the IDOC. I enter this values in OBCA and OBCE customizing points, to determine the company code 'LC'. It doesn't work.
PT Rao, what do you call "activate partner profile" ?
Thanks in advance.
Regards,
Arnaud

Error while sending mail from SAP system

Hi all,
I configured SAP connect in ecc6.0 ehp7 while sending mail using tx sost i am error
Message cannot be transferred to node SMTP due to connection error (final) , below is the icm log.
ERROR => IcmPlAllocBuf: MpiGetOutbuf failed (rc = 14(MPI_ESTALE: outdated MPI handle)) [icxxplugin.c 1222]
ERROR => SMTP SmtpClientClose: alloc failed, rc = -3 [smtp_plg.c 3738]
ERROR => IcmBufFree(id=0/32): MpiFreeBuf failed (rc=14), MPI_ESTALE: outdated MPI handle [icxxplugin.c 165
ERROR => IcmConnClose: PlugInStopConn failed (rc=701) [icxxconn.c 3433]
can any one please help on this
Thanks,
Narendar.

Hello Priyanka,
Actually, I performed the following two steps in order to solve the issue:
- In transaction SICF, the node for SAPConnect must be active. In our system, this node was in inactive state. Hence I activated it.
- Then In transaction SCOT-> Settings menu--> default domain should be 'xyz.com' if the email addresses in your company are maintained with a suffix xyz.com.
But for me the problem didnt get solved here..
The problem that i am facing now is that if in my user profile, I have the email address maintained, then i get an error saying 'Sender address rejected'. However, if i goto transaction SU01 and clear the email id, the mail is successfully sent to outer world.
You can try the above mentioned two steps using SICF and SCOT. If the problem does not get solved then try clearing the mail id in ur user profile.
Hope this helps. If you find an answer to the problem of the mail id getting cleared, then please let me know..
Regards,
Himanshu

Idoc Status error 29 for Out bound Idoc( Receiver of IDoc is its own logic)

I try to create the Out bound Idoc with messag type WMMBXY ( basic Idoc type - WMMBID02 ).
which is configured with the out put type XXXX in VT01N( shippment creation). But I am getting the error status 29 in the Idoc.
Only I am passing the sender, receiver port , partner type and partner function to the communication structure.
Could you please tell me , what is the issue with the partner type configuration .

Hi,
Error 29 occurs when there is an incomplete or no partner profile maintained.
Check whether you have done the correct partner profile settings in WE20 outbound parameters.
For the partner no defined in Idoc check whether there is an entry(under partner type LI, KU or LS)
with correct message type WMMBXY and Idoc type WMMBID02. Also check for message function code.
Regards,
Savitha

IDoc outbound errors - mail send step in WF to send info-mail to enduser

Hello specialists
I searched quite a lot in the forums now. I found lot of info but nothing regarding my issue.
I need to send an info-mail to the end user creating purchase orders. But only if the idoc (outbound ORDERS) could not be sent (failing for some reason, i.e. if rfc connection fails). This is what I've done to achieve this:
- in WE40 I linked my WF to process code EDIO
- the WF-BATCH user has an email address assigned to it (in SU01)
- the mail sending step in my WF is configured like this:
recipient type = G (organizational object)
Expression = &_WORKITEM.CREATEDBYUSER.ID& (this contains the enduser id)
subject = Test for &WORKITEM.CREATEDBYUSER.ID&
When testing the mail can not be delivered (error SO23).
When setting recipient type to U (E-Mail address) and giving a valid e-mail address, then it works fine (SCOT, etc. is configured and mailing to external systems works). But setting the e-mail address hard coded style in the mail send step is not an option here!
It seems that the send mail step (SELFITEM.SENDTASKDESCRIPTION) always requires a valid e-mail address. Is it not able to handle SAP user id's ?
Thanks in advance for some guideance on this one.
Renaud
Edited by: Renaud Desarzens on Feb 11, 2010 3:00 PM

Hello and thanks for your help.
I was able to solve it like this:
- don't use mail send step
- instead, add new activity with a new task (SELFITEM.SENDTASKDESCRIPTION)
- in the bindings (workflow -> step) set:
B --> &TYPEID&
&_WORKITEM.CREATEDBYUSER.ID& --> &ADDRESSSTRINGS&
Seems that the mail send step doesn't allow TYPEID to be "B" because each time I tried to tweak the generated bindings that way it messed up the recipient type and expression I set before.
Regards
Renaud

Idoc/ALE error handling, send to external email

Hi all,
I'm developing an IDoc inbound interface for purchase order create using PORDCR1. For the error handling functionality, I need to send an external email describing all of the validation error happened in user-exit EXIT_SAPFKCIM_002. Please kindly tell me how to cater the functionality. I won't use workflow because the error handling can't describe all the error, it just displaying the first error encountered. I also don't want to create any custom object since message type PORDCR1 is available. I think creating a custom FM is a possible way, but if there is another way, please tell me how.
Thanks,
Teddy

Hi Teddy,
A custom FM is the easiest and simple way.There may be other ways.
Regards,
Atish

Idoc status error 66 - IDoc must be processed later; 000006 , IDoc no. 0000

Hi,
The following error appears when a particular Idoc is trying to get posted
Status 66 - IDoc is waiting for predecessor IDoc (serialization)
Message - "IDoc must be processed later; 000006 , IDoc no. 000002 required."
What is this error all about? How do I find out which is the predecessor Idoc which has to be posted first. I can not find any other idoc numbers mentioned here.
Thanks in advance

Rhea,
What you have mentioned is clear for me too. But the question is how do I trace the predecessor idoc? 0002 or 0006 are not Idoc numbers. They are Idoc types.
Any way in which I can trace out the predecessor idoc?
Regards

Mds: (Error) Import over and over in system.log?

I am currently watching my system.log file fill up with stuff like this:
Feb 26 09:43:54 Zeus mds[47]: (Error) Import: importer:0x861800 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Feb 26 09:44:24: --- last message repeated 7 times ---
Feb 26 09:44:26 Zeus mds[47]: (Error) Import: importer:0x861800 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Feb 26 09:44:56: --- last message repeated 7 times ---
Feb 26 09:44:58 Zeus mds[47]: (Error) Import: importer:0x861800 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Feb 26 09:45:28: --- last message repeated 7 times ---
As you can see from the time intervals, it's happening a lot, over and over. I found some references to an error like this supposedly being caused by Time Machine, but I have Time Machine turned off. (Don't like it.)
Anyone know what this is? Looking back through the log, I'm seeing that it has happened multiple times in the past, for anywhere from 15 minutes at a time to over an hour.

This looks like a permission problem to me.
Can you execute the following commands in a terminal and post them?
(Only the actual 'ls -al xxx' lines, the rest is shell prompt and result)
Regards
Patrick
[18:31 root@pm1] ls -lad /var/tmp
drwxrwxrwt 5 root wheel 204 Feb 26 18:26 /var/tmp
[18:31 root@pm1] ls -lad /var/tmp/mds
drwxrwxrwt 6 root wheel 204 Feb 26 18:20 /var/tmp/mds
[18:31 root@pm1] ls -lad /var/tmp/mds/
502/ 65/ messages/ system/
[18:31 root@pm1] ls -lad /var/tmp/mds/502
drwx------ 2 mau wheel 170 Feb 26 18:20 /var/tmp/mds/502

How to get the status idoc from recieveing system

Hi All,
In our requirement we will be sending an idoc to the recieveing system. we are planning to get the staus of the idoc.
How can you recieve the status of the idoc that idoc has been is saftly reached to target server.
Can any one share the solution if you have confirgured the same before.
We are planning to use : Middleware.

Hi Anil,
If get the status 03 means your idoc successfully send to receiving system port. But in the receiving system if there any issue in processing you can't get these updated status automatically from receiving system. You know Idoc works in asynchronous mode. To get the status you need send one idoc with status (error , success ot warning) from receiving system to sending system.
Thanks
Subhankar.

How to find Correct IDoc Status in SAP

Hi All,
I need some help on IDoc scenario, I have custom program to create Idoc and as well it will send IDoc to XI. I want to know idoc staus in the program to update custom table whether idoc sent successfully or not but idoc giving status as 03 (Data passed to port OK) irrespective of idoc send or not, actually idoc not sent to xi when I check SM58 showing error.
Please advice me how to find correct idoc status inside program itself.
**-----Create IDoc
CALL FUNCTION 'IDOC_OUTBOUND_WRITE_TO_DB'
    TABLES
      int_edidd      = i_edidd
    CHANGING
      int_edidc      = wa_int_edidc
    EXCEPTIONS
      idoc_not_saved = 1
      OTHERS         = 2.
COMMIT WORK.
i_edidc = wa_int_edidc.
APPEND i_edidc.
REFRESH i_edidd.
**-----Send Idoc
CLEAR i_edidd.
**-------Send Idoc to XI
CALL FUNCTION 'EDI_OUTPUT_NEW'
    EXPORTING
      onl_option = 'B'
      error_flag = ' '
    TABLES
      i_edidc    = i_edidc
      i_edidd    = i_edidd.
COMMIT WORK.
READ TABLE i_edidc INDEX 1.
**-----Update Dispatch order status based on Idoc status.
IF sy-subrc = 0 AND i_edidc-status ='03'.
    znxi01_update c_03 i_edidc-docnum.
    gw_success_record = gw_success_record + 1.
ELSE.               " Error in Data Transfer
    znxi01_update c_02 i_edidc-docnum.
    gw_fail_record = gw_fail_record + 1.
ENDIF.

Hi Anil,
for setting IDOC Status you can send back a IDOC of type <i>ALEAUD01</i>.
The function IDOC_INPUT_ALEAUD takes automatically this IDOC and writes the status to the origin IDOC.
Regards Mario

Error when sending data request

Hi All,
   i have scheduled info package for different type data sources in bi 7.0, for this i am getting the data from ecc 6.0 . all of this schedule's showing the status "error when sending data request" with the following details.
status
diagnosis
the request idoc could not be sent to the source system using rfc
system response
there is an idoc in the warehouse outbox that did not arrive in the ale inbox of the source system
in step by step analysis it is showing
   rfc to source system successful showing with ash status
   data selection successfully stated and finished ? show with red status
in that details tab
request : showing with green status
everything ok
extraction :showing with red status
missing messages
transfer(idocs and trfc) : missing messeges
processing(data packet) : no data
    it is showing technical status with red as processing overdue
                       processing step call to source system
   so it is showing error with 0 from 0 records.
please any body could help me for solving this error.
regards,
naveen.

Hi
Seems you have connectivity issues between the Source system and Bi system.
You need to check whether you have data on R/3 side via RSA3 with Full / Delta Update Modes with Target System as your BI system.
RSA13--Source System -- Right click Connection parameters/check/Restore/Activate again Say Replicate All Data Sources (If Possible , provided if you have time because it consumes lot of time )
You need to check the tRFC Queue SM58/59 for any Stucks and WE19/20 for IDocs.
Much of BASIS Issue .
Hope it helps and clear

File to IDOC scenario error...

Hi all,
we hhave created an File to Idoc scenario .
we are getting the following error in SXMB_MONI t-code.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BUS_SENDER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can any one plz say wat this error might be..
TIA
Regards,
Raj

Hi,
The problem occurs when sender and receiver business system or business service does not have a logical system name.
ID - Integration Directory
Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
If business system type = Third-Party, then add the logical system in business system level and Save.
If the business service does not have the logical system name in ID, it needs to be configured as follows.
Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
Apply and activate.
hope this will help you.
regards
Aashish Sinha
PS : reward points if helpful

IDOC Acknowledgement Error

Hi All,
I am getting "Receiver exists , No filters , No conversion , No version change" message in IDOC Status of ALEAUD. And IDOC has not been sent to XI System.
I have done the settign for Idoc acknowledgement.
What is the reason of this message.?

this is inbound message that i am getting..
<?xml version="1.0" encoding="UTF-8" ?>
- <ALEAUD01>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>900</MANDT>
<DOCNUM>0000000002416250</DOCNUM>
<DOCREL>620</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>ALEAUD01</IDOCTYP>
<MESTYP>ALEAUD</MESTYP>
<STDMES>ALEAUD</STDMES>
<SNDPOR>SAPEIT</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>EITCLNT900</SNDPRN>
<RCVPOR>SAPXID</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>XIDCLNT300</RCVPRN>
<CREDAT>20071105</CREDAT>
<CRETIM>190225</CRETIM>
<ARCKEY>A05D0C308BBB11DC8598001A4BA967D2 0000000000573053</ARCKEY>
<SERIAL>20071105171956</SERIAL>
</EDI_DC40>
- <E1ADHDR SEGMENT="1">
<MESTYP_LNG>Z_MLS_INBOUND_RECEIPT</MESTYP_LNG>
- <E1STATE SEGMENT="1">
<DOCNUM>0000000000573053</DOCNUM>
<STATUS>64</STATUS>
<STACOD>SAPB1999</STACOD>
<STATXT>& & & &</STATXT>
<STAPA1>Immediately processi</STAPA1>
<STAPA2>Unable to interpret</STAPA2>
<STAMQU>SAP</STAMQU>
<STAMID>B1</STAMID>
<STAMNO>999</STAMNO>
<STAPA1_LNG>Immediately processing not possible:</STAPA1_LNG>
<b><STAPA2_LNG>Unable to interpret EGOD3 as a number.</STAPA2_LNG></b> - <E1PRTOB SEGMENT="1">
<DOCNUM>0000000002416235</DOCNUM>
</E1PRTOB>
</E1STATE>
</E1ADHDR>
</IDOC>
</ALEAUD01>
In 'Ack' i am getting this message.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Status>Error</SAP:Status>
<SAP:Category>transient</SAP:Category>
</SAP:Ack>

Idoc status error 37 in sender and 51 in recieving system

Similar Messages

Maybe you are looking for