Problem in sending IDOC

Hi experts,
i am trying to send customer number to other system..i am not getting no errors...but status 30 is coming in outbound idoc like "receiver exits,field conversion,filter exits....." this is warning...
can any body tell me how can i acheive this?
Thanks,
Praveena.

Hi ,
try to use the EQUEUE & DEQUEUE
for Outbound you need to trigger the program RSEOUT00 by passing the idoc number.
See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes
IDoc Statuses:
Successful Transmission:
                               03 - Successful outbound transmission
                               12 - Dispatch OK
IDoc being processed:
                               01 - IDoc created
                               30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)
ALE Error Messages:
                               02 - Error passing data to port
                               04 - Error within control information on EDI subsystem
                               05 - Error during translation
                               25 - Processing despite syntax errors (outbound)
                               29 - Error in ALE service
                               32 - Resubmit edited intermediate document (DO NOT USE)
Syntax Error Messages:
                               26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes
IDoc Processed Successfully:
                               50 - IDoc added
                               53 - Successful posting
IDoc ready for processing:
                               64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Errors in IDoc Processing:
                               51 - Error - application document not posted
                               56 - IDoc with errors added (You should never see this error code)
                               60 - Error during syntax check of IDoc (inbound)
                               61 - Processing despite syntax error (inbound)
                               63 - Error passing IDoc to application
                               65 - Error in ALE service - indicates partner profiles are incorrect
                               69 - IDoc was edited
Prabhudas

Similar Messages

Problems with sending IDocs into R/3 using BPM

Hi Vishnu,
as I have read the forum, you have experience with sending IDocs into R/3 from XI using the BPM.
Did you have problem, that this sending takes very long time?
My BPM splits the xml, sends IDoc into R/3 immediately, but the processing of the 2nd IDoc takes 6-10 minutes!
Do you have any idea, what could be wrong?
Thanx 4 answer, Peter

Vishnu, I was discussing this problem in another thread, but no helpful answer was sent, and I have read, that you have experience, so - just for explanation
Well,
yes, this situation is really strange.. New facts are:
when I send into XI XML, which is splitted in the BPM only into 1 IDoc, it is processed immediately. When I send there XML for 2 IDocs, the first is processed immediately, the 2nd starts immediately, but end of process is after 6-10 minutes, it depends... Then I tried to send there XML for 10 IDocs - and now attention please! 5 of them have been processed almost immediately, 5 of them after 8 minutes... The last test was with 16 items - 6 processed immediately, 10 after 10 minutes... And all these 10 minutes was my 4 processor XI box unavailable, with over 60% load... But finally the IDocs arrive!!
Any explanation???
This is really unbelievable situation!
Port name is SAPDEV, rfc destination DEVCLNT100
Actually, when I was creating the scenarion using the wizard and trying to add my communication channel(IDoc type) to receiver agreement, I got error - communication channel is not configured correctly, use another one. But somewhere I read, that I should create the receiver agreement manually. So I did.
To my BPM:
-receive MSG
-switch (but I'm testing only one branch now) - and the MSG message is always passed here, it's ok
-then I have transformation to MultiMSG (message with multiple DATA for multiple IDOCS)
-then comes the split mapping Multi2SingleMSG
-then ForEach Block with sending the Single MSG
this is the end of the BPM, and outside the BPM comes the mapping Single2IdocMSG and sending the IDoc into R/3
before I had the Single2Idoc mapping in the BPM, but thought, that this could be the bottleneck, so moved the mapping after the BPM... It didn't help...
So, what do you say?
Peter

Problem while sending IDOC to File Senario

Hi Experts
    I am having problem while sending the Idoc from SAP R/3 to File
   I have done all the setting in SAP as well in XI but while pushing IDOC
   I am getting error in the transaction sm58 in SAP R/3
" <b>The service for the client 300(My SAP R/3 client) is not present in Integration
Directory</b>"
I can any one explain me what to done on this....all the connections are fine
Waiting for Response
Adv points and thanx
Rakesh

Reason and Prerequisites
You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
This note proposes solutions for the following error messages:
a) No service for system SAPABC client 123 in the integration directory
b) Transaction IDX1: Port SAPABC, client 123, RFC destination
c) ::000
d) NO_EXEC_PERMISSION: "USER" "Business_System"
e) IDoc adapter inbound: Error error ...
Solution
a) Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client.
For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with TransactionSLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
Solution:
The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
Activities in the central XI system:
In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
Activities in sender system ABC:
Transaction SM21 contains entries for failed logons.
Activities in the central XI system:
Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
In Transaction SM21, you will find entries relating to authorization problems and more exact details.
Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
The most common errors are:
- IDoc type or segments not released
- Segments that no longer exist are listed in the IDoc type
- Data elements that do not exist in the DDIC are assigned to fields
in the segment.
Contact your system administrator and correct these errors in the IDoc type.
d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
Solution:
You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
e) Error message: IDoc adapter inbound: Error error
Solution:
You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
Regard's
Prabhakar.....

Problems with sending IDOC in tRFC.

Hi All,
I am sending IDOC to websphere from SAP.
Problem is very weird. All the IDOCs have status 03, but some of them never reach webshpere.
I checked SM58 and there are some tRFC entries for the same.
Following is the error there:
Check SAP Connector log. Error in BO Handler.
I think problem is after the data has been sent to ALE layer.
Can anyone suggest what can be the issue? And how can this be resolved.
Regards
Anuj

Hi Anuj,
As it seems like from the error message there is some problem with the way BO handler is responding to request BOs .
The base class to initialize the connector has been set properly though.
Check the log in SM21 on this and it might give you the detailed information.
Also check if you are passing the large objects, which might require some additional config.
Hope these pointers help in solving the issue.
Cheerio,
Disha

Problem when sending IDOC from ECC to MII 12.0

Hi all,
   I have followed the document "[How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50775783-6cb1-2b10-90b0-e6bc2c0b8563]" to configure the scenario to send IDOC from SAP ECC 6.0 to MII 12.0.
   But when sending 53 IDOCs by Tcode POIT to MII, I have problem as below:
   - 53 IDOCS were successfully outbounded (list in WE02).
   - 8 IDOCs were successfully sent to MII IDOC listener (these 8 IDOCs messages exist in list of Message Monitor).
   - 45 IDOCS were error with message in SM58: "Bean IDOC_INBOUND_ASYNCHRONOUS not found on host xxx, ProgId=yyy".
   I'm wonder why some IDOCs were successful while some others were error. If the bean IDOC_INBOUND_ASYNCHRONOUS don't exist in EJB, why some IDOCs successful found this bean?
   I have another wonder: in this scenario document, all IDOC message type (SYNCH, LOIPRO) is configured in outbound parameters of RECEIVER (receiver logical system), why they weren't configured them in outbound parameters of SENDER (sender logical system)?
   If some have the same problem and know how to resolve it, could you please help me?
Thank a lot in advance,
Vinh Vo

Hi Vinh,
Please read the following document:
[IDOC Listener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
If you explicitly defined a Prog ID in NW, then you have done an extra step and are confusing NW with the real destination.
In basic terms, you set up an RFC destination (with an assigned ProgID) in ERP, then configure MII to point to it.
I suggest that you follow the document completely and do nothing else to set up a new listener.
If you are not using ECC 6.0, you may find the paths are different, but the transactions codes are generally the same. However, you may want to check with some of the older installation instructions regarding specific modifications. Look in the Wiki for MII under Connectivity.
Good luck,
Mike

Problem while sending idoc over xml http

Hello all,
We have developed a scenario to send the idocs from SAP to Java(Tomcat) web server. Its was working fine. But SOMETIMES the idoc status will be set to 03(Data passede to port OK) on the SAP side, but no data(no xml string) received in the web server. is this depends on the size of the idoc? or due to some JVM settings of webserver??Could someone suggest us a way to identify the problem.
Thanks in advance
Regards,
Vishu.

Asit Purbey,
i have send 2 idocs with different number of segments. idoc with 2 segments is successfully received in the webserver, but the idoc with 100 segments didnt received in the webserver. Then i processed RBDMOIND but both the idocs remain in status 03.. Please help me to figure out the problem......
Regards,
Vishu.

Problems at sending IDOC from XI to R/3

Hello everybody, I have a problem sending an IDOC (WPUUMS) from XI to R/3. Everytime the ERP system presents overflow problems at the locked table, the IDOC, send by the XI, is not created. The type of the sending message is asynchronous. I tried to use the ALE configuration but it doesn´t seem to work.
I hope anyone can help me to figure out this issue.
Thank you.

Julio
Please try this...
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
http://help.sap.com/saphelp_nw70/helpdata/en/44/a1b46c4c686341e10000000a114a6b/content.htm
Check the Queue [SMQ2] & if the message got struck in queues clear the queues
Then goto SMQR - De-register & register the queues.
I hope it helps you ...
Thanks,
Vasanth.

Problems with sending IDOC via RFC from Unicode to NonUnic

Hello
I have following problem, sending an IDOC via RFC from Unicode to Non Unicode System. IDoc is not sent with error: codepage of receiver system cant determined. receiver destination was: Message no. B1999
I have tried different options in sm59, but it didnt help.
Any ideas? The recipient system is rather old, version 4.0

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

Problems with sender IDoc scenario

hi experts..,
when i create message Interface for a Outbound Idoc my scenario is not working.
if i use idoc directly instead of message interface its working properly
And in Interface Determination if i gv interface mapping we are gting errors and without mentioning interface mapping in Configuration its is working fine
can any one explain me what is the reason for my two questions
thx in advance
john wesly

Hi,
I will explain one example by taking one IDOC
we have ORDERS05 Idoc and we are using the same Idoc for two scenarios
Scenario1 -
IDOC---File( FTP Server)
Scenario2----IDOC-JDBC
Now let us assume that we have configured two scenarios.
If we trigger the IDOC Orders05 from SAP R/3 means
1) The Idoc will be triggered and it will reach to XI.
Now your doubt is which Receiver will be take place and to be executed.
This time the problem my come or may not come, let it be like that.
If your requirement is like the above mentioned thing means
1) We can develop a single scenario like
IDOC-------File( FTP Server)
JDBC
Here what we have to do is when the idoc comes to xi we have route the Idoc to the particular receiver based on some condition in Receiver Determination
And one more thing is in mapping also if we have two mappings then we can use Interface determination based on condition which interface mapping to be execute.
I hope this clears yor doubt
Regards
Seshagiri

Problem in sending IDOC to XI: status 30 in R/3

in a IDOC to file scenario, i m sending a MATMAS idoc from R/3 to XI,
i m triggering it form we19, it shows a status 30 (IDOC ready for dispath(ALE service)), what shall i do to sent it to the target XI system

U will find the solution here
http://help.sap.com/saphelp_sm32/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm
An add on
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Regards,
Prateek

Problem to send idoc for a Good Receipt created

Hello all,
I have a problem when a good receipt has been created in EBP system the idoc has been generated with a message type MBGMCR.Why a idoc has not been generated with a message type WMMBXY in our system ?
I verify in a transaction WE20 and we have a correct message WMMBXY between a system EBQ and system back end.
Please help me for this problem.

Ok Mady,
then just reward this good response
PS: for IDOC exchange, this is the only message type changed by switching < 4.5B to >= 4.5B.
New message types can be added for contract distribution (BLAORD, COND_A, BLAREL).
Rgds
Christophe

Assignment IDX1 port to sender idoc adapter ...

Hi gurus,
I have a big problem and I don't have any idea how to solve it. Please, help me.
I have a non-SAP system, regular SAP ERP and SAP XI and I need to transfer IDocs between them.
There is no problem to send IDoc from ERP to XI and forward it to non-SAP system. Unfortunatelly communication in opposite direction doesn't work. XI is not able to receive IDoc sent from non-SAP system because appropriate metadata can not be found in IDX2 cache.
In configuration of communication channel for sending IDocs to non-SAP (receiver idoc adapter) I selected IDX1 port that is directed to the ERP and it's worknig fine. I can send IDoc from XI to non-SAP.
But in configuration of communication channel for receiving IDocs from non-SAP (sender idoc adapter) is not possibility to determine any port. Does exist a way how to force sender idoc adapter to use some specific IDX1 port?
Thank you in advance for every reply!
Regards,
Zbynek

The IDocs are sent from non-SAP system by means of tRFC. Connection type of the RFC destination is type T (TCP/IP) and activation type is Registered Server Program.
If we sent the IDoc directly into SAP ERP (where the IDoc Type is known) everything is fine
Edited by: Zbynek Kabrt on May 19, 2009 8:59 PM

Problem in sendinfg Idoc's

Hi All,
I am facing problem in sending idoc's form one SAP sys to another. I had written a outbound program for sending IDOC's. When i execute the program the idoc is generated in the sending system ( With status 03 ) but no idocs were posted on the target system. But if i manually try to send the IDOC ( WE19 ) the idocs are posted to the target system.
Can any one give me an idea where the exact problem lies in...
Regards,
Swamy Mantha.

Hi,
Ru close the master idoc with a commit .
<b>*Reward points</b>
Regards

Problem sending IDOC DESADV /AFS/DELVRY03 to XI

Hi Gurus,
I have problems sending IDOCs DESADV (basic type /AFS/DELVRY03) created by function LSEND_IDOC to XI system. IDOC is correctly created by R3 system (AFS ECC 5.0) and correctly sent on the XI port (Status: Data passed to port OK - 03), but XI system doesn't receive IDOC.
If I resend the same IDOC by WE19 tcode goes ok!!
In R3 sending system nothing warnings/errors in syslog or sm58.
Any suggests? Thanks in advance.

Issue solved! It is necessary close the master idoc with a commit

Problems while sending/receiving IDOCs

Hi,
I am trying to store IDOC data to MS access database. I created a scenario and able to activate that successfully, but after sending IDOC from SAP, in SXMB_MONI I can see status as "Message Processed succesfully" flag, and acknowledgement status as "Still awaiting acknowledgement" and data is not stored in database. Anybody having any idea about this problem.
Another problem what I am facing is, when sending an XML file from a file server to SAP(through XI), I am getting status as " Scheduled for outbound processing". Receiver determination, Interface determination, Sender & receiver agreements all are present and correct. Any help?

Hi,
Check what chris has said....Also in SXMB_MONI check the status of the message on the outbound side(by scrolling to the right)...This will say whether it has been transferred to the Adapter Engine....
For the second problem, pls check whether all your queues are registered. All queues can be registed from transaction SXMB_ADM...then doublwe click on "Manage Queues"...and choose the register queues and execute...
Thanks,
Renjith

Problem in sending IDOC

Similar Messages

Maybe you are looking for