Idoc Error in sm58

Hello All,
My Idoc for any Data load is failing in sm58 with "No authorization to send IDocs with message type R SRQST (Message no. SR053)". I have Sap_ALL and All New in both ECC and BID.
Thank you,
Rakesh.

Hi
Please check the SAP Note 150315.
Check whether SAP_ALL is provided for user ALEREMOTE and also cross check whether these two S_BI-WX_RFC and S_BI-WHM_RFC authorizations. are provided.
Thanks

Similar Messages

IDOC Error in SM58 and Management Console

Hi Guys,
Good day!
I am currently having issues on sending IDOCs to BODS.
There are instances that an IDOC gets stuck or ends up with an error in transaction code SM58. In transaction WE02, the IDOC is
successfully processed with status 03. In a set of IDOCs (10 or more), one IDOC is in error in SM58, usually the first IDOC gets the error and the next IDOCs are successfully processed. The error received in SM58 displays the following:
Error 1: R3RfcClient(DI_CLIENT)ActaIDocFunc::Process()...
Error 2: CPIC-CALL ThSAPCMRCV no data received
However, the client interface is active/running.
In the management console, the error Logs-History displays the following:
(14.0) 04-08-14 23:32:51 (E) (8060:3868) Unknown: SP(INVOICE_001, ABC:1234)::flowThread() Flow became
invalid during waiting for request (BODI-300137)
(14.0) 04-08-14 23:32:51 (E) (8060:9356) Unknown: R3RfcClient(RFC_CLIENT_INTERFACE) ActaIDocFunc::Process()
encountered processing error for Requeste(15149) (Communication Error. See real time job log for details.) (IDOC 0000001234567890/ABCDE). (BODI-300129)
For the Real-Time Services log, the following is displayed:
(14.0) 04-08-14 23:32:39 (E) (70684:47620) RUN-051005: |Session REALTIME_INVOICE|Data flow DATAFLOW_INVOICE|Loader query_IDOC_DETAILS Execution of <Regular Load Operations> for target <IDOC_DETAILS> failed. Possible causes: (1) Error in the SQL syntax; (2) Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for regular load operation and load triggers are defined, check the SQL. Otherwise, for (3) and (4), contact your local DBA.
(14.0) 04-08-14 23:32:50 (E) (70684:68856) DBS-070401: |Session REALTIME_INVOICE|Data flow DATAFLOW_INVOICE|Loader query_IDOC_DETAILS ODBC data source <ABC\ABC,12345> error message for operation <SQLExecute>: <[Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host. >.|<Regular Load Operations>|<IDOC_DETAILS>
Given this, I would like to ask on how to eliminate this issue.
Thanks,

Reg Sender IDoc error in PI7.3

Hi All,
I am facing the below error while triggering an IDoc from ECC to PI. I could see the error in SM58 and PI log as below:
[JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT, Managed_Application_Thread|XI_IDOC_DEFAULT Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO) Exception raised from invocation of public void com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(java.lang.String) method on bean instance com.sap.aii.af.idoc.inbound.IDocReceiverBean@24a49d74 for bean sap.com/com.sap.aii.adapter.idoc.app*xml|com.sap.aii.adapter.idoc.ejb.jar*xml|IDocReceiverBean in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is: com.sap.conn.idoc.IDocRuntimeException (raised by system |PI_AAE_IDOC)
Can anyone please help me on the same.
The resource adapter configurations are deleted and created again. Also the RFC destination is working fine.
Cheers,
Neethu

Neethu,
Can you check if you are able to ping PI from the TCP Ip rfc destination in ECC.
Also the program id in the RFC destination created in SAP should match program id in InboundRA
Also the gateway parameters in the inboundRA in PI should be set properly. If you are setting the Gateway to be PI gateway then enable Local to true. If you are using SAP Gateway then set Local to false.

IDoc_AAE Synchronous error in SM58

Dear friends,
I configured IDoc_AAE sender and receiver side. I tested this with success. The next step was to configure an Async-Sync scenario. I configured my scenario according the following Blog:
Request/Response Bean for IDOC_AAE adapter
My scenario is that I want to take an IDOC from ECC and send it to SOAP which is synchronous one and I map the response data to a ALEAUD and send it back to ECC.
My configuration looks like following:
I use the following Beans and parameters in the sender Idoc communication channel:
Now when I want to send an Idoc from ECC I get the following error in SM58:
Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad
And I get the following error in NWA:
Error in look up for binding. Reason: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=BS_******;TS=;AN=IDOC Name;ANS=urn:sap-com:document:sap:idoc:messages;
So If I test this idoc asynchronous it works fine and if I put this Idoc in an Outbound Sync SI it doesn't work and I get an error in SM58.
Do you have any suggestion why it doesn't work and can you please tell me If I can achieve my scenario with this configuration? As I read in the following thread (it was mentioned by Indrajit that we cannot use an Idoc adapter in the ResponseOneWayBean)
ResponseOneWay Bean unable to find the receiver channel
If its true so what do I can do to achieve this scenario? I also can use an asynchronous ABAP Proxy back to ECC instead of an ALEAUD.
You help would greatly appreciated,
Thank you in advanced,
Kind regards,
John

Hi
Unfortunately the way you are trying to get the acknowledgement idoc will not work.The request response bean in the sender idoc adapter only work for
Adapter Namespace: http://sap.com/xi/XI/System.
Adapter Type: File
The same is clearly mentioned in the document you have referred. But there is another alternative approach which you can use to get the acknowledgment back.
You have to use the request response bean in the receiver adapter( say SOAP). In that case the receiver application will trigger an response message with the interface name you have provided in the response bean.
You have to create one more ICO or scenario for that interface triggered by receiver adapter and use the mapping in PI which will convert that in ALEAUD idoc.
Following things needs to keep in mind
You have to use virtual receiver for the second scenario.

IDoc error in PI

I am unable to see in PI theIDoc triggered from SRM system to PI. What settings should be done to trigger IDoc from SRM to PI? Is this the same as that of ECC to PI?

Hi Radhika,
For sending IDOC from any SAP system to SAP PI, following things should be in place in SRM system -
1. There should be a RFC connection type 3 in the sender system.
2. In sender system you must have maintained the partner profiles and port.
Then after triggering Idoc from SRM system you can check in transaction we02 about the Idoc status.
Then you can also check IDOC in BD87 if the IDOC has failed.If failed , you can reprocess the failed IDOC.
In SM58 you can check for any rfc related errors or any authorisation errors in both SAP PI and SAP SRM.
In SAP PI system check for following things -
Ports
You can also check in IDX5 the idocs that has been received by SAP PI.
Regards
Somil

Error in SM58 on XI box

Hi,
While trying to post IDocs to an R3 system, getting the following error in sm58 - 'Transactional RFC' transaction 'PASSWORD LOGON NO LONGER POSSIBLE'.
But when I do a connection test from SM59, to the corresponding RFC destination listed in the receiver IDoc adapter there is no issue. The test is successfull.
Anything I'am missing here?
Thanks,
Anand

>>>> did try a remote logon from the RFC destination...on doing this I get a dialog box requesting username/password entry. And the user that appears here is my user ID, not the user that is in the RFC destination.Is this standard behaviour?
No. This means your RFC destination is not working properly. Just fill the user Id, pwd with a valid user Id that has sufficient auth., then try. You should be directly logging into SAP on using the Remote logon option.
Regards,
Jai Shankar

Error in sm58

Hi all,
I am trying to send a IDOC from SAP system to XI and I getting the following error in sm58
Transaction IDX1: Port SAPEN5, Client 800, RFC Destination contian error.
BTW what is the difference between maintaing the port in we21 or idx1?

>>what is the difference between maintaing the port in we21 or idx1?
WE21 is mainted in R3.
IDX1 is maintained in XI.
<a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> By Swaroopa Vishwanath
Regards
San
<a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
Where There is a <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/weblogs?blog=/weblogs/topic/16">blog</a> there is a Way.

Receiver IDOC error - using TCP/IP

Hi All,
I have a scnario where I am sending an IDOC to BCOMM ERP system via IDOC adapter from SAP PI using TCP/IP RFC program but while sending it is giving me an error in SM58 as IDocException occurred and there isn't much info in SM21 or ST22 or any other transaction.
Error log in SM21 says
Name of the partner program where an error has occurred. Check the
preceding system log entries.
Use the gateway monitor (transaction SMGW) to monitor the functions
of the gateway.
If someone has ever worked on such a scneario please let me knw and any pointers would be great.
Cheers
Abhi

Hi Michael,
I know that this is not the conventional way but we cannot use RFC of type 3 as it is not a ECC system , it can handle IDOC communication via Idoc adapter through a SAP connector at there end which can be handled only via TCP/IP.
I am able to do it for another system with similar scenario but Not able to do for this particular system.
Can you tell me about your scenario and how you did it?
Thanks for your reply.
Cheers
Abhi

IDOC error while load balancing

Folks,
I am facing an issue when I am switching on Load balancing button in RFC destination while sending IDOC in sender system . The sender system shows this error in SM58
IDoc adapter inbound channel: Error Error when rea
Thanks,
Manish

Hi,
cud u please precise about the problem. So that we can help u in solving ur problem.
Regards
Sanjeev.

T rfc error in SM58

I m getting " :: 000 " error in SM58 while sending ORDERS
I have tried everything, even recreated all ALE configuration settings.
What could be the reason?
With the same settings, I could transfer MATMAS but its comign only for ORDERS
regards,
Nikhil.

To track the IDOC in SAP XI you need some authorizations to execute IDX5
To start the XI message monitor in the remote system
SXMB_MONI with ACTVT = 03
To start the IDoc monitor in the remote system
SXMB_MONI with ACTVT = 03
Authorization for function groups:
BDMON
BDMT
IDOC_TRACING
SXMB_MONI
Trigger the IDOC in the R/3 system like do the scenario like IDOC to file or File to IDOC.
/people/kamalkumar.ramakrishnan/blog/2008/02/13/monitoring-the-idoc-adapter-in-xipi-using-idx5

IDoc error In case of ERS procedure, please enter terms of payment

Hi,
I tried to use BAPI_PO_CREATE1 to post purchase order. However, I encountered this error.
IDoc error In case of ERS procedure, please enter terms of payment
I passed the payment term in IDOC PORDCH. Segment E1BPMEPOHEADER-PMTTRMS has value filled out. This value is passed into the BAPI correctly but for some reasons, it got cleared out in the BAPI. Any ideas or suggestions would be greatly appreciated.
Thanks

Check
BAPI_PO_CREATE1 - E 06 436 In case of account assignment

IDoc Errors in ECC

Hi Experts,
what kind of IDoc Errors can occur in ECC for the scenario :
ECC sending PO to Ariba(E-commerce hub, using third party adapter) and in receiving back Order confirmation from it.
Thank you,
MK

Hi,
This depends on the design and landscape and also Disaster Recovery or High Availability Plan.
some hints:
1. Connection Problem: Because of timeout , unavailability of the Receiver system.
2. Data Problem may cause you the error in IDoC posting [ probably functional/Business Team should look into this]
3. User ID and Password Maintenance - it may hit sometimes
4. If any pre-requisite process is required to process this IDoC, then problem in the pre-requisite process will lead the problem
these all kind of problems you may face..
Rgds , Moorthy

RFC destination error in SM58

Hi,
We are getting an error in SM58 "P85040 does not exist".
What could be the reason for this error in PI system?
When I checked, there is no RFC destination configured with the name P85040. Also there is no communication channel configured with the RFC destination parameter P85040.
Kindlly help.
Thanks,
John

Hi John,
The reason can be the host name you are assigning is not existing.
In RFC destination the host name is for that particular client which is pointing to IP address not to the logical system. You can choose name of RFC destination same as of your logical system.
You can get the host name by login to SAP system and the using MENU ... System->Status and in lower right corner you can find it.
Sachin
Edited by: Sachin Dhingra on Dec 18, 2008 1:18 PM

IDoc Error 51 - Make Entry in All Required Fields

hi,
I am using a scenario where an idoc is being posted into an R/3 system from a legacy application. For some reason I keep getting Idoc error 51 (Document not posted).
Once I drill down further, the specific error states "Make entry in all required fields". Have checked to make sure all mandatory fields have been mapped and proper constant values have been specified.
But cannot seem to get rid of the problem. Could anybody help out in determining how else to troubleshoot this and identify the possible cause?
thx,
Manpreet

Manpreet,
What IDoc Type you are trying to post ? One way is debugging the inbound function module using WE19. The second option is talking to a functional consultantor who worked, what fields are needed for that particular IDoc.
I wouldn't care much about whether the IDoc is posted or not because, it is the ABAP ALE/EDI consultant's job to do that. The only way XI Developer is concerned is when it is not posting, ABAPer would tell what's missing.
Hope this info helps.
regards
SKM

File to IDOC - Error Inbound -56

Hi,
I am doing file to Idoc. (CREMAS01).. My scenario in
RWB is successful. But in R/3 it is shwoing IDOC
error :"EDI: Partner profile inbound not available".
I created Partner Profile in R/3(logical name of BS-
sender file). Still is shwoing Error.
Regards,
Mukharji
Message was edited by: Mukharji T

Hi Mukharji,
I hereunder give you the step by step procedure for File to IDOC scenario. Cross check whether you have done all these:-
SLD
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Hope this helps you.
Regards.
Praveen

Idoc Error in sm58

Similar Messages

Maybe you are looking for