IDOC Scenario Not Working

Dear All,
Yesterday I deleted the entry from SMQR transaction, I have SOAP->RFC->SOAP scenario it is working fine, but SOAP->XI->IDOC scenario is giving me the error , Please let me know how do I solve this issue.
Thanks in advance.
Raghavendra

Hi Ragava,
are u expecting the IDOC acknowledgments as RFC responds if so try to follow this links it may help you
setting up Audit Response.
Configuration Tips for a Business Service/Integration Process to send back ALE audit IDOC
Just set this parameter in SXMB_ADM >integration engine configuration>specific configuration--> choose RUNTIME --> ACK_SYSTEM_FAILURE.
It will send a acknowledgment in SXMB_MONI
regards,
Kishore

Similar Messages

File to IDOC scenario not working

I have configured a file to idoc scenario and kept the XMl file in a shared location on XI server.
I have also created and checked the communication channels correctly.
Once Everything is done my xml file does not get picked up at all. Also the SXMB_MONI does not show any messages for my service.
How do I find out what is the error ??

Hi Kapil,
Just check the File path that was in shared location once and the file name is properly mentioned or not..
And also one thing after activating all IR and ID just goto SXI_CACHE and press F6 to update cache refresh
And also in RWB --> Message Monitoring --> Adapter monitoring --> check the status of the sender
Regards,
Sridhar

Web Service Scenario Not Working

Hi Sdners,
I am working on Support project where I have web Service to RFC Scenario which is synchronus scenario. when the user sending the WSDL request to XI it's woking fine in for Devlopment but it is not working QA .In QA i am gettings error below
<?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="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="urn:sap-com:document:sap:rfc:functions">ZCA_RATE_INTF.Exception</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When I asking user to send the message from their they are coming to QA syetm insted of DEV.........for this where I have to check........
Edited by: gangadhar kh on Mar 3, 2010 12:29 PM

HI All,
Can anyone help me on this?
there is no communication is going between the sender system(Web Service) to PI . When user is sending the data through URL he is not able to send the data and when he is sending the data . I am getting the message in PI/XI(MONI) messsage coming (with system Error with balls sign)

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="urn:sap-com:document:sap:rfc:functions">ZCA_PRICE_F_EX_RATE_INTF.Exception</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and IN payload of This message
RFC_ERROR_SYSTEM_FAILURE</ID><Attributes><V1>CALL_FUNCTION_NO_DEST</V1>
Please suggest on this Problem
Regards
Edited by: gangadhar kh on Mar 8, 2010 6:00 AM

File to IDOC Scenario Not able get Metadata (IDX2)

Hi,
I am doing File to IDOC scenario. I have done all configurations in IR and in ID. But it is throwing error like ATTRIBUTE_IDOC_METADATA-Basic type ZOIDOC does not exist.
Where as my custom idoc is a not exit in metadata (IDX2). Also I am trying to reload same manually but I am not able to reload it. I have all required configuration in SAP R/3 side like partner profile.
I would appreciate yours inputs.

Hi Sunil,
You are saying that you are unable to load the Metadata even manually.
There could be a problem with the RFC destination defined within the IDX1 port. So first test the RFC destination using SM59.
Also ensure that you have used the right naming conventions for the PORTS and RFC destinations as below:
<SID>CL<ClientNo> e.g DXXCL055 where DXX is the SID and 055 is the Client No.
Rgds
RC

IDOC is not working

Hi,
We have 2 company codes and for the intercompany trade we are using IDOC to send invoices between the companies - it works perfect. Now we have added a third company code and the IDOC functionality does not work for intercompany trade involving the new company. All about pricing, requirements, PO, delivery etc. works without problems but the IDOC process does not start when we create the invoice - so i don't even have error to trace. I have created OBCA, OBCB, OBCD and OBCE and of course WE20.
A tip for the missing link will be really appreciated - thanks in advance
yu

With reference to this issue, please review note 106142 which has good
information on this behaviour.
Transaction OBCA is not really a customizing function since the table
as the partner numbers in the key, and these are master data, at
east in case of vendors (partner type LI). Thus, table T076B should not
ransport relevant. But there's been a couple of bugs in the lower
releases (note 106142) and they're fixed in release 4.70 and higher.
Similarly the tables like T076S as well as view V_T076S depend on master
data (like vendor master data), the standard settings of these tables
do not implicate transport requests.
Within note 106142 incorrect table settings in lower releases were
corrected to avoid the transport of these tables.
If you nevertheless want to transport changes of these tables you have
to undo the change of the recording routine in transaction se54.
For these tables change it back to Standard Recording Routine and save
the changes. Please do NOT generate the view.
But please keep in mind that this setting represents a modification
and possible problems due to this setting are not supported by SAP.
tr. SE54 ->
Table/View: T076M
select the radio-button 'Generated objects' ->
select the button 'Create/change' ->
frame 'Dialog data transport details' ->
'Recording routing' -> please, select option 'Standard recording
routing' and save your settings.
PLEASE, DO NOT REGENERATE THE VIEW !!!!
Further details which may be helpful:
You have to change
the view T076M for the transaction OBCD
the view V_T076S for the transaction OBCE,
the view V_T076K for the transaction OBCC,
the view V_T076B for the transaction OBCA,
the view V_T076I for the transaction OBCB.
Please also review the SAP notes.
356483     Customizing: Current settings in the test system
135028     Transfer IMG activity to current setting
106142     EDI: Customizing tables T076B, T076I,...
Regards
Vijayesh V V

Multiple IDOCs pattern not working

Hello, When I tried Multiple IDOC to single file pattern, it is not working as expected. Everytime when a idoc reaches XI, it is going to a seperate BPM queue and not collecting the IDOCs, any idea??

Yes, I have refered. I have done exaclty the same thing as in SAP Pattern for collecting multiple idocs to single file. Everything is working fine in BPM too. But the problem is whenever the idoc hits XI, it is going to a seperate BPM queue instead of a same queue. So single message for each BPM and BPM waits for 3 minutes (mentioned in BPM) and times out. But my need is all the IDOCs should come to a single BPM queue and BPM needs to collect all the IDOCs and send it as a single file.

BPM Scenarios not working

Hi All
I have done a simple file_2_file and SOAP_RFC scenario. Both of them are perfectly working fine.
Now I did a simple file_2_file scenario using BPM and this doesn't work. When I go the transaction SXI_CACHE, it shows as "Cache contents are obsolete". Also, in SXMB_MONI, when I see the messages, only sender interface is there and no part of the BPM messages are shown.
I am sure that my BPM configuration is perfect as its a simple example which I implemented from one of blogs.
Do I have make any settings for a BPM scenario to work? Please help.
Thanks,
Vijay

Hi Moorthy,
I already implemented your blog. After activating all the objects, I just tried SXI_CACHE, it says the "Cache contents are obsolete". Also, my previous scenarios doesn't work. Now If I take out the BPM scenario, I mean if I delete the scenario, then the previous scenarios start working fine.
Any solution please?
Thanks,
Vijay

WE20 - Pack size not working/IDOC packaging not working - PI 7.1

Hi all,
My requirement is to collect idocs and send to PI at one point of time in a day.
I kept Pack.Size = 100 in partner profile (WE20), in PI 7.1 - Sender Communication channel I assigned the same value 100 to pack size.
Now the problem is when I create more than 10 idocs and trigger manually by rseout00. for example
15 idocs are pushed to PI by executing RSEOUT00. In PI when I check IDX5 or SXMB_MONI, 2 message ID's are generated one with 10 idocs and the other with 5 idocs.
It works fine meaning creates only one message id if the total count of IDOC's are 10 or <10.
Any ideas/suggestions appreciated.
Thanks,
Krishna

Yes Prateek,
In Sender Communication channel - IDOC package size is assigned as '100' and only 10 idocs are collecting for one message id.
I checked the assignment and it was correct. I changed the description, saved and activated Sender agreement & Sender Communication Channel.
No luck.
Regards,
Krishna

Idoc to file Scenario not working

Hi ALL,
I have created one Idoc -XI-File scenario.I have done all the preconfiguartion in Backend and XI.
Now when i am testing in we19, it is showing that Idoc is sent and saved in the database but when i am going to sm58, there it is showing Status field "No service for system SAPSAI, client 800 in Integration directory
Can anybody tell where i am going wrong???
Thanks in Advance
Regards
Vikas

Hi,
Now i am able to see the message in sxmb_moni , it is showing Green status, but still am not getting the file in reciever side.
In communication channel monitoring it is showing green status,but not giving any messages theres
Any suggestions what do to next to get the file??
Thanks
Regards
Vikas
Message was edited by:
Vikas Agarwal

IDOC Acks not working

Hi All,
I have spent hours searching SDN for this specific problem, and can see some similar threads but none with a successful answer, so I will ask again.
I have the following scenario:
R/3 system sending an IDOC to XI, then XI mapping that to a custom XML message and sending it via the HTTP Adapter to an external business partner.
We have no issues with the above and get a chequered flag in SXMB_MONI.
But we want an Acknowledgement of that transmission to go back to the initiating IDOC in the R/3 system and update the status. e.g. If there was a HTTP comms failure and the message ended up in error in SXMB_MONI then we want that status sent back as an Acknowledgement to the original IDOC so that the R/3 system is aware of the failure.
We can see that XI tries to send the Ack back, but in SXMB_MONI in the "Ack Status" column there is an error associated with the Ack which says either "Acknowledgement not possible" or "Acknowledgement contains system errors". When we look into the error message contained within the Acknowledgement it says:
Unable to convert the sender service XXXXX to an ALE logical system
The Sender Service listed in the error message is the original Receiver Service which passed on the HTTP message to the 3rd party receiver. But in this case it is the sender because it is trying to send an Ack back to the R/3 system that is now the Reveiver. Note that it is a Business Service (not in SLD), it is NOT a Business System.
My question is - where is XI looking for an ALE Logical System name? My Business Service is not in the SLD (doesn't need to be, it's a 3rd party external system and I can send to it fine). I even tried populating the Adapter Specific Identifers for this Business Service with the IDOC Logical System name and R/3 System ID and Client, but that did nothing becasue this isn't using the IDOC Adapter, it's using the HTTP Adapter.
And note that we have SXMB_ADM param RUNTIME-ACK_SYSTEM_FAILURE = 1.
And please dont post a bunch of links, I've looked at every message in SDN that refers to the above. Please only reply if you can type the exact answer and it refers to the Acks only.
Thanks,
Brendan.

Hi,
Open(Double click) the Receiver Business service in ID and goto Change mode
goto Adapter Specific Identifiers---just give the LS name as HTTP and click on Apply and save Activate.
Do SXI_Cache also
Now try to post the Idoc Again from R/3
Regards
Seshagiri

Idoc Filtering not working

Hi All,
Requirement is to send an idoc to XI only if it satisfies the filter condition. Currently, the idoc is getting triggered even if the filter conditions are not satisfied. However the segment with the relevant filter fields does not appear in the idoc.
The config is complete in BD59, BD64, BD52 (for change pointers).
Does the filter in BD64 work at the idoc level or segment level? If at segment level, then what is the way to stop the idoc from getting triggered if it does not satisfy the filter conditions?
Thanks,
Shivali

hi
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
regards
ravish
plz dont forget to reward points if helpful

User eixt for modifying inbound idoc (delins) not working

hi all,
Inbound IDoc DELINS.DELFOR02 is sent from customer to vendor to create forecast delivery schedule lines (VA32). E1EDP16-WMENG has the delivery quantity and it is mapped to VBEP-WMENG.
I need modify E1EDP16-WMENG accordingly (based on some business rules) and this change should also be reflected to VBEP_WMENG.
I tried to modify the idoc_data in user exits: EXIT_SAPLVED4_002, userexit_zuordnen_idocs. During debug, I can see the idoc is modified, but the final forecast delivery is not updated (VA33).
Anyone can help?
Thanks!
Regards
Hui

Hi Sandip,
Inside userexit_zuordnen_idocs, i updated the table idoc_data_1 (I changed the delivery quantities of the schedule lines), but it dosen't work. In Va33, the delivery quantities are not changed.
Any other input?
Thanks!
Regards,
Hui

Sender RFC scenario not working

Hi All,
I'm trying to configure a scenario where the sender is an RFC. I have done the following configuration steps:
1. Created an RFC destination in the R/3 system.
 Program ID: SAPSLDAPI_X3A
 Gateway Host: hostname of the XI system
 Gateway Service: Gateway service of the XI system
2. In the RFC Sender channel
 App Server Gateway: R/3 system's hostname
 App Server Service: of the R/3 system
 Program ID: SAPSLDAPI_X3A
3. In the RFC Metadata Repository Parameter, the details of the R/3 system is provided.
4. The RFC is triggered by calling a report program specifying the RFC destination.
But no messages are coming to the message monitor. Is anything wrong here or is something missing? Is there any way to see what happened in the R/3 system?
Could you please help?
Thanks,
Priya

Hi,
1. Created an RFC destination in the R/3 system.
Program ID: SAPSLDAPI_X3A
Gateway Host: hostname of the XI system
Gateway Service: Gateway service of the XI system
This is fine.. I would recommend you to use different name coz SAPSLDAPI is a RFC destination name for SLD communication purpose. Its better to avoid using some system names. But this is not a problem.
2. In the RFC Sender channel
App Server Gateway: R/3 system's hostname
App Server Service: of the R/3 system
Program ID: SAPSLDAPI_X3A
The App Server Gateway, App Server Service & Program ID should match with what you have given in the RFC destination of R/3 system.
After this try doing a test connection from the RFC destination sm59. Your test should be succesful.
3. In the RFC Metadata Repository Parameter, the details of the R/3 system is provided.
This is fine
4. The RFC is triggered by calling a report program specifying the RFC destination.
This is also fine.
Also in order to see any messages in SXMB_MONI you need to enable Logging. Trace level = 3 will not capture the Sync message. RFC is by default Sync. If your sender is not expecting any response then you will get an error in the response message, in this case you need Async.
For Async you need to add this addition while doing the call function "IN BACKGROUND TASK". Also make sure you re mentioning the destination while doing the call function.
Check you have mentioned
DESTINATION <rfc destname>.
Thanks,
Prakash

File to RFC Scenario - Not working with AAE

I have a File to RFC Scenario (calling RFC /POSDW/CREATE_TRANSACTIONS_EXT) using AAE but it is failing with following error in PI .
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
But When I run the same scenario using IE instead of AAE, it is successful from PI. So probably there is nothing wrong in RFC channel configuration.
There's an OSS note-730870 on this error ,it says the XML document sent to RFC Adapter may not be RFC-XML but as I am using AAE, payload generated after technical routing cannot be viewed.
Could you all please suggest why this error is coming and solution for the same?
Thanks,
Ankit

Hi Debashish,Monica,
Thanks for your help, I checked this SAP note its question 16 do describe my problem but do not provide solution and as I am using AAE it does not allows me to see the target structure generated whereas if I use IE the target structure generated is sucessfully getting posted.
Also, the functional module is present in target system. I have reimported the RFC also.
Is there some AAE related configuration required to enable AAE with RFC which could be missing?
This is what I get in log as the RFC reciever is called..
06.09.2011 14:15:31 Information MP: entering1
06.09.2011 14:15:31 Information MP: processing local module localejbs/RfcAFBean
06.09.2011 14:15:31 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
06.09.2011 14:15:31 Error Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
06.09.2011 14:15:31 Error Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
Thanks,
Ankit

Notifications from IDoc processing not working right

I am having a problem where the IDoc error notifications are appearing in everyone's inboxes. I followed the instructions in SAP notes 44416 & 116610. If the tasks are set as general tasks, they go to everyone. If they are not general tasks, they go to no one. I checked the rule resolution for the tasks and they are resolving to the proper organization unit. Any ideas?

The changes only apply to new errors.

IDOC Scenario Not Working

Similar Messages

Maybe you are looking for