on 11-29-2010 3:08 PM
Hi Guys
On my Scenario Jdbc to Idoc (Asynch) I am using FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01
as a Receiver Interface, now when testing on the sxmb_moni I get two flags the Black and While and the Red the one the is Back and While shows that the Sender is my JDBC Adapter which is right
but now the Red flag show that the Sender is IDoc(FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01) is also Sender of which I used it as a Receiver Interface, I dont know how to stop this IDoc Adapter not to send but to receiver.
Basical my scenario is meant to create an IDoc but is is not doing it when going to TCode WE02/WE05 I get message : "No IDocs selected"
Thanks
Yonela
Hi,
Can you shed more information like how you created your Integration directory configuration. There might be some error in that.
Also, try checking idx5 in sxmb_moni whether you were able to see the idoc.
Please also post the error message you are getting in SXMB_MONI.
Regards
Krish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like there are issues while posting IDOCs to Backend-SAP system, which is causing the idocs not to be posted
For the other message, seems like Idoc Acknowledgments are coming back from back-end sap to PI and since there is no configuration to capture Acknowledgments, you are seeing them in Red.
You can disable IDOC acknowledgments from back end by using report: IDX_NOALE or table IDXNOALE from SE16 in SAP XI/PI
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thanks I manage to disable the Acknowledgement, but now my JDBC to IDoc scenario is giving the below error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Receiver Identification
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
My IDOC is a reciever not a sender interface I cant figger out why is it sending a message
Any idea will be appreciated
Thanks
Yonela
Hi Yonela,
Check if there are any conditions to send to receiver. If so check if the condition is satisfied.
Check the below link : Page 43,44 &45 regarding IDOC related errors.
Thanks,
Hi
I don't have any conditions, to Send and Receive, by the way I went to TCode IDX5 my Outbnd is right but Inbound thats where I get the below error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Identification
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error
I have done these:
SM59- To Create RFC Destinations
WE21- To Create IDoc Ports
SALE- To Create Logical System
WE20- To Create Partner Profiles
IDX1- Port Maintenance in IDoc Adapter
IDX2- Metadata Overview for IDoc
On the ID I created the the IDoc Receiver:
RFC Destinatin: IDOC_RECEIVER
Interface Version: SAP Release 4.0 or Higher
Port: SAPPI1
SAP Release: 701
What could be the problem
Thanks,
Yonela
In the configuration part enter sender business sytem ( for JDBC ) Enter receiver business system for IDoc ( SAP ECC )
Under sender interface select your sender interface for JDBC , Under receiver interface directly select the IDoc you will see in the display list while you select from drop down menu
Using the Above two now create your sender agreement , receiver agreement , interface determination , receiver determination
Now go to test tab in configuratio where in you can test your configuration
enter your scenario details paste a valid payload and execute and see theresults
if there is red signal in any of the steps you will come to know the error
regards
Ninad
Hi ALL
After testing the Configuratiion on the Integration Directory I got the below error:
Receiver Determination
Internal Error
HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://saptrain1:8000/sap/xi/simulation?sap-client=001 User: PIDIRUSER
Can you advice on this
Thanks
Yonela
> Hi ALL
>
> After testing the Configuratiion on the Integration Directory I got the below error:
>
>
> Receiver Determination <Not found>
>
> Internal Error
> HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://saptrain1:8000/sap/xi/simulation?sap-client=001 User: PIDIRUSER
>
> Can you advice on this
>
> Thanks
> Yonela
in your XI system in SM59 transaction, just check whether the rfc destinations INTEGRATION_DIRECTORY_HMI, AI_RUNTIME_JCOSERVER and AI_VALIDATION_JCOSERVER are running by testing using the connection test button.............
Go to transaction SICF and navigate to Path sap/xi/engine and make sure this service is active (should be in dark black) otherwise right click on engine and activate it.
regards
Ninad
Hi Guys
Thanks for your assistence I manage to resolve the below error:
This error is because some services in SICF transaction are not activated. Try activating them first
HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://saptrain1:8000/sap/xi/simulation?sap-client=001 User: PIDIRUSER
Execute the SICF transaction for SERVICES and then expand the tree default host> sap> xi > simulation. Then right click and select Activate service. (Also see SAP Note 517484)
Regards
Yonela
Hi all
Though when testing on the Test Configuration everything is work right (Sender Agreement, Receiver Determination, Interface Determination & Mapping and Receiver Agreement) but still getting the error below:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Identification
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
And on TCode WE05 still getting the error below:
No IDocs selected
What am I not doing right
Thanks,
Yonela
refresh your CPA cache
Error code NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC
Inspect receiver determination area in SXI_CACHE
If necessary, adjust the routing information in the Integration Directory
If the message is asynchronous, it can be restarted manually, and manual
changes in the SOAP header are permitted
Common causes of error are discrepancies between the configuration
and the SOAP header of the incoming message
Sender service does not match (case-sensitive!)
Sender interface name or namespace does not match (case-sensitive!)
Condition for content-based routing has not been met
Double-check message content
Double-check condition (XPath expression or context object)
For the no IDocs selected issue
The very first setting you need to check is in distribution
model if the message type is configured for given sending
recieving system combination.if this is correct and partner
profile is wrong, you will get an IDoc stuc in 56 status on
inbound.
check inbound partner profile(WE20) in the receiver
side.give the correct partner number,message type and
process code.i
http://www.allinterview.com/showanswers/85337.html
regards
Ninad
Edited by: Ninad Sane on Dec 3, 2010 8:48 AM
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.