PI7.11- Configuration in the Sender ABAP System: RFC destination

I'm trying to create Destination for AAE in SM59
on the Path Prefix row, I'm entering below as advised in the SAP document and I'm getting error, Query string not allowed. can you help?
/XISOAPAdapter/MessageServlet?ximessage=true

It is just a warning. Press 'enter' and you will be able to save you changes.
rgds
arun

Similar Messages

How to determine the sender business system for ABAP client proxy

Hi All,
I have one doubt: when the client proxy sends the message to XI, how could i know what is the sender business system name for it?
Is it the logical system which is reflected in Technical System?
let's say if i have the ABAP system, the technical system is ECC, which has three clients: 001, 066 and 000.
And the client 001's logical system in ECCCLNT001 (all the client proxy is created in this client). In this case, the sender business system name is ECCCLNT001, am i right?
If no, please correct me.
Thanks in advance
Leo

Hi lawrence
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: <System-ID>CLNT<Client>.
Regards
sandeep

How does ABAP client proxy determine the sender business system

When we use ABAP client proxy to send a message in XI-SOAP format to the integration engine, how does the client proxy determine what is the sender business system, i.e. how does it know what value it should insert in the sender service field in the SOAP envelop.
For example, at first, the business system X8A_105 corresponds to the technical system X8A_105, so when the client proxy sends out a message, the sender service is X8A_105. Then I delete the business system X8A_105 in the SLD, and create a new business system that is associated with the technical system X8A_105.when the client proxy sends out a message, the sender_service is still X8A_105, why?

Hi Annie,
Execute the following function module in your business system and see what name it returns..
LCR_GET_OWN_BUSINESS_SYSTEM.
You can always debug the code inside the above FM to find out how it gets the business system name...
I think the issue should be related to cache. I would also suggest you to logoff from your business system and then login again.
Regards,
Sumit
Message was edited by:
Sumit Khetawat

Connect one JAVA ADS instance to multiple clients from the same ABAP system

Hi,
Does anyone know whether it is possible to connect multplie clients from the same ABAP system to a JAVA instance running ADS?
If so how do you setup the java destinations in Visual Admin and SM59 RFC connections?
Any help is appreciated,
Sander

Dear Sander,
this is always the case if you arrange the ADS connection.
You have to set up the RFC connection 'ADS' in ABAP side and this connection/destination is client independent. So you can use this from all clients of your abap system.
On Java side you have to arrange the already mentioned FP_ICF_DATA_<SID> destination. On the ABAP system and client (you specify in this destination) you have to maintain the user ADS_AGENT and your templates should also exist on this client. If there is no client defined, the default client will be used.
Regards
Istvan

Error in Local Message System: RFC destination MB3AP1039 does not exist.

Error in Local Message System: RFC destination MB3AP1039 does not exist. Message was Not Created
Message no. BCOS088
Hi,
When iam creating a message from any system from HELP-CREATE SUPPORT MESSAGE it is throwing the above error message. Actually i need to send this message to SAP solution Manager Service Desk.
Can anyone help me in resolving the above issue.
Thanks & Regards,
Mirza Kaleemulla Baig.

Dear friend
You have to of following option
1.Define Service Desk destination in the R/3 systems:
Note: for this you need to log in the R/3 system.
Create the RFC between the Solution manager and R/3 system (Login to the R/3 system)
2.a. Go to transaction SM30.
b. In table/view field, enter BCOS_CUST. Then press the Maintain Button. See example below:
c. Press the Continue button in the following screen:
d. You should see the following screen, no entries should be seen in the table. Press the New Entries button:
e. In the next screen, enter the following information:
In the RFC Destination you should point to your Solution Manager destination RFC.
0ss_msg w sm_bsmclnt_back cust620 1.0
shailesh

Error in Local Message System: RFC destination 10.189.98.10 does not exist.

Error in Local Message System: RFC destination 10.189.98.10 does not exist. Message was Not Created
Message no. BCOS088
Hi,
When iam going inside the tcode SM30 in the satellite system and entering the destination ip of solution manager system and after that when iam creating a message from HELP-CREATE SUPPORT MESSAGE, then it is throwing the following error.
Can anyone please help me in the above issue.
Regards,
Mirza Kaleemulla Baig.

Hi Mirza,
For the RFC destination don't enter the IP address,enter the RFC name,somthing like SM_SP1CLNT200_BACK which is maintained in sm59.
Revert for any clarifications.
Thanks and Regards,
Avinash.

Configuring EWA for non Abap System

Hello to everybody.
I am configuring EWA in Portal System 7.01and SOLMAN 7.01 too. It's a new installation and i have a question:
- Which is the order to start to configure SMD?
- Is Necessary configure the CCMSR agent?
I configured EWA in a old system that had installed the agents, but they could not to connect to SMD Server.
I Fixed this problem, but now I need configure the SMD since start.
By the way, I'm new configuring EWA for Java
Thanks.
Esteban G.-
Edited by: Esteban Gutierrez E. on Jan 11, 2010 8:48 PM

Hi Sailesh
Here is related blog fr your issue. Hope this will help you.
setup EWA for portal
Thanks
Jignesh

Help with RFC sender, Program And RFC Destination

Hi!!
my scenary is asynchronous
     RFC Sender -> SAP-XI -> Oracle reciever
I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI receive the message but the message is empty.
1. In my program on the line
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
2. I rewrite my program, that line to
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
3. I rewrite my program, that line to
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
What is my Error?
Where am i making a mistake?
RFC
FUNCTION zbapi_sd_ped_ord_servic.
*"Interfase local
*" TABLES
*"      PED_ORDEN STRUCTURE ZSD_RFC_T04
*"      RETURN STRUCTURE ZSD_RFC_R06
TABLES: zsd_ped_orden, zsd_rfc_r01.
DATA: tb_ped_orden LIKE zsd_ped_orden OCCURS 0 WITH HEADER LINE,
               tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
*Get Pedido by Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
          FROM zsd_ped_orden
          WHERE estatus EQ space.
LOOP AT tb_ped_orden.
    MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
    APPEND ped_orden.
    tb_ped_orden-estatus = 'X'.
    tb_ped_orden-fecha_actualiz = sy-datum.
    tb_ped_orden-hora_actualiz = sy-uzeit.
    MODIFY tb_ped_orden.
ENDLOOP.
MODIFY zsd_ped_orden FROM TABLE tb_ped_orden.
COMMIT WORK.
*Errors in Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
          FROM zsd_rfc_r01
          WHERE estatus EQ space.
LOOP AT tb_rfc_orden_error.
    MOVE-CORRESPONDING tb_rfc_orden_error TO return.
    APPEND return.
    tb_rfc_orden_error-estatus = 'X'.
    tb_rfc_orden_error-fecha_actualiz = sy-datum.
    tb_rfc_orden_error-hora_actualiz = sy-uzeit.
    MODIFY tb_rfc_orden_error.
ENDLOOP.
MODIFY zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
COMMIT WORK.
ENDFUNCTION.
PROGRAM
REPORT ZBAPI_SD_PED_ORD_SERVIC.
DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
      return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
     TABLES
          ped_orden             = ped_orden
          return                = return
EXCEPTIONS
    communication_failure = 1
    system_failure        = 2
    OTHERS                = 3.
IF sy-subrc <> 0.
MESSAGE 'error' type 'I'.
ENDIF.
COMMIT WORK.
RFC DESTINATION
RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
Connection TYpe: TCP/IP Connection
Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
Gateway host: host00
Gateway service: sapgw00

hi
For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
a) RFC destination
b) RFC channel in the XI directory
This weblog is a response to a few question about the basic configuration of the RFC sender adapter
that were posted on the XI forum (and also on my e-mail)
So here we go, basically we have to configure 2 things:
a) RFC destination
b) RFC channel in the XI directory
RFC destination:
1. To create the RFC go to TCODE: SM59
2. Create new destination of type T (TCP/IP)
3. Make sure you select Registered Server Program option before writing your program ID
4. Write you program ID (remember it's case-sensitive)
5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
7. No configuration in the J2EE administrator nessecary
Now we can proceed to RFC channel configuration:
1. Enter your Application Server
2. Your Application Server Service
3. Enter your Program ID from the RFC destination
And we're done:)
Now you can test the RFC destination in SM59 to see if it works.
Please chk this following link.
1. RFC Processing with the RFC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
2. Configuring the Sender RFC Adapter -
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
3. /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
regards
Manas

How to send data to RFC Destination(RFC SENDER Adapter)

Hi ,
Scenario: R/3 Backendà RFC Sender Adapterà XIàsome other system.
I have configured the RFC destination (of the type TCP/IP) at R/3 System and have registered the Program ID (specified in the RFC destination) in the XI server and using it in the configuration parameters of the RFC Sender Adapter.
Problem: I do not know how I can send data to the RFC destination. (Should I use a report program/ ABAP Function Module?) Can anybody provide me with a sample code of Report Program/Function module (whichever is required), how to send data to the RFC Destination, so that it may be picked up by my RFC Sender Adapter.
Thanks and Regards,
Siva Maranani

I have one query for you that
I am trying to develop a scenario in SAP XI
SAP R/3 ( RFC function module) sends a synchronous request to the XI and SAP XI will send this request to a third party web application using HTTP receiver adapter.
I am able to send the data/message and it is successfully received at the third party web application.
But I am facing one issue that I am unable to receive any message/data in my RFC module back.i have seen in sxmb_moni that the two messages are displayed in successfuly processed but in SAP R/3 side nothing get happedned
Can you tell me how to use some waiting mechanism in function module to wait for the response from SAP XI.
Regards
Gopesh

** Seeburger AS2 Configuration in the Sender Side

Hi friends,
We are trying to receive Purchase Order from the Customer using Seeburger AS2 adapter. The customer is sending the PO to Inovis a solution provider and we need to receive this documents from Inovis. We need to configure AS2 adapter to receive the PO from Inovis.
How to configure AS2 adapter ?
Kindly reply friends.
Thanking you

hi
I will give you the normal flow how the things works.
You need to deployee the seeburger conversion module on XI. Now in the AS2 adapter this module wil be called and which will does the conversion of EDI to XML.
In the AS2 module parameter tab you need to write the below entry.
Process Sequence :
localejbs/callBicXIRaBean bic
Module Configuration :
bic mappingName See_E2X_ORDERS_UN_D96A
AS2 adapter is used for B2B scenario so for this case you need to use the party concept and you need to maintain the identifier information of Partner which will going to send the EDI file to XI.
please look in to this links u will come to know about seeburger adapter.
HI,
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
Reward points if helpful
Vishal

Unable to convert the sender service to an ALE logical system... Urgent..!!

Hi,
Im DOing File to Idoc scenario.
Firstly i check LS name exist or not in BS.. then i found its not maintained.
I edited the BS and provided the required LS name.
and the same has been tested in ID
Business System -> Service -> Adapter Specific Identifiers .
Now i got logical system name in "Adapter Specific Identifiers".
Pressed Apply, save and activate the changes.
But still it is showing the same error.
1. Any idea what might have gone wrong??
2. I need to maintain the
   LS name of R/3 in XI system? and
   LS name of XI in R/3 system?
    Is it necessary?
Waiting for your answers.
Regards
Seema.
Edited by: reddy seema on Dec 27, 2007 1:37 AM

Hi Reddy,
        just mention the logical system name in the Sender Business system or Service ( click on sender business service> Service(menu)> Adapter Specific Identifiers--> specify the logical system name which you configured in R/3 WE20 ..) in R/3 side WE20 you need to configure the Inbound parameters of your Idoc ..
Here sender business system and Reciver Business system logical system names are different.. for checking just go to Services and check the adapater specific identifiers..--> then you   can find the name of logical system.. like that you need to check for both systems.. and both should be different..
try with this option..
Regards
@jay

Service Desk Configuration (Raising message from R3 system)

Hi,
I want to configure my R3 system, so that when I create a support Message it is reflected in Solution Manager.
I have done the following steps, in R3 system
1) Use transaction SM30 and modify BCOS_CUST table.
Entries in this table are
Col 1: OSS_MSG
Col 2: W
Col 3: SOLUTION_MANAGER (Not sure, what is the right entry for this column)
Col 4: CUST620
Col 5: 1.0
I am confused over the entry for Col 3:
In some postings I have seen that the value is SM_<sysid>CLNT<client>_TRUSTED, so assuming my Solution Manager SID is SL3 and Client is 100, the value for Col3 must be
SM_SL3_CLNT100_TRUSTED
Is the above assumption right?
2) Is it necessary to make entries for RFC destination in my R3 system using transaction SM59.
Also while creating the RFC Connection using transaction SM59 in the R3 system, it asks about the type of connection.
Which type of the connection, should be chosed.
Type :: Short text
I :: Connection to application server with same database
3 :: Connection to R/3 System
2 :: Connection to R/2 System
T :: Start an external program via TCP/IP
L :: Reference entry (refers to another destination)
S :: Start an external program via SNA or APPC
X :: RFC via special ABAP/4 driver routines
M :: CMC connection
H :: HTTP Connection to R/3 System
G :: HTTP Connection to External Server
Hope you can help..
Regards,
Vikas

Hi,
The third one is RFC destination which is a way of linking two systems providing there ip and login credentials.
When you create RFC in sm59 tcode you have to provide ip address and login credentials and a name,This name you have to provide in se11 bcos_cust table third field.
You have to create an R/3 or abap connection.check this for creating rfc connection.
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f62cfa8911d386e70000e82011b8/content.htm
Check the following .
/people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
in short first of all go to tcode sm59 create a r/3 connection to your server and provide a name to it.
secondly go to bcos_cust table and provide this name in the third field.
Please reward points if it helps.
Message was edited by:
Prakhar Saxena

EWA on Non-ABAP System with Solution Manager EHP 1

Hi Experts,
We have recently updated our solution manager from SP Stack 16 to EHP1 (sp 18). we are now planning to set up EWA for non-abap components (EP 7.0). however, the only SAP note that i have been able to find is "976054 - Availability of EWA for Non ABAP components" but this is only limited up to SP 17. I have not been able to find any guides relating to EWA thru Solution Manager EHP1.
I would greatly appreciate if anyone can refer any documents or SAP notes that would enable setting up EWA for non-abap components thru Solution Manager EHP1.
We have also gone through the note 1332428, but we have'nt found it useful. We are still struggling to generate EWA report on Non-ABAP system.
Looking forward to your kind help.
Thanks and Regards,
Sarthak Syal

Hi Sarthak,
Good!!
Please do the following:
1) include the system in the Solution and scheduled the EWA session.Logical component should refer to the Non-ABAP System with no ABAP instance as relevant under the SID definition in SMSY-systems.
2) Is the Non -ABAP ( assuming its java) has the Software component defined and is mentioned as relevant under the SID with the component name and type.
3) Having said that SMD - Root cause Analysis functionality is configured-> check whether you are getting the Details for the Non-ABAP systems in the analysis Tabs of Root Cause Analysis.
This should be good to go. Wait for the session to get completed.
Thanks,
Jagan

Error: Unable to convert the sender service SC_PO_fileidoc to an ALE logica

Hi,
I'm currently creating an Idoc adapter receiver with BPM. However I've received an error at the second stage from BPM - IDOC. It gives the error "Unable to convert the sender service SC_PO_fileidoc to an ALE logical system". Appreciate if anybody can help me.
Cheers
Zubair

Hi,
This weblog will help you resolve this issue.
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
under the section "Intgeration Process as the receiver system"
Check whether you have assigned the Logical system (LS) name to the integration process in the adapter specific identifiers (Integration Directory). Also check whether an entry for the LS is available in the SLD for the sender Business system.
Regards,
Sridhar

Problem while connecting to external ABAP system (on 4.6C rel)

Hi All,
I've created WebDynpro application that is supposed to fetch info about users from several ABAP systems. J2EE engine that runs this WebDynpro is directly connected to one of the ABAP systems. I've successfully created identical Adaptive RFC models, maintained SLD entries for my ABAP systems and configured JCO connections for my WebDynpro through WebDynpro Content Manager (http://<host>:port/webdynpro/welcome). I was able to reach all ABAP systems testing my JCO connections from WebDynpro Content Manager.
The problem I am experiencing is the following:
the application is working fine for the ABAP system that J2EE (where it's executed) is connected to, but failed to reach the remote ABAP system issuing the following message:
"Accessing System <Remote ABAP system> is not possible because RFC Metadata was retrieved using System <ABAP system that J2EE is connected>. Please assure you have configured the RFC Connections properly. A Server restart may be necessary!"
Where else should I have define JCO settings ?
This remote ABAP system is running on 4.6C so I have no options to install J2EE on it or fully configure SLD for that system.
It may seem like a dummy question since I am new to WebDynpro programming.
Thanks in advance,
Mike

Hi Rich,
Thank you for a quick reply,
Here is what I've done to connect to the remote ABAP system:
1. Configured this remote system in the SLD as a Technical System (SLD=> Technical Landscape).
2. Opened WebDynpro Content Administrator and created two JCO's for my application pointed to that remote ABAP system (defined in SLD). I was able to test them successfully reaching that remote system.
But when I run my application the same error occured.
What did I miss ?
Thanks & Regards,
Mike
Message was edited by: Mykhaylo Puzankev

PI7.11- Configuration in the Sender ABAP System: RFC destination

Similar Messages

Maybe you are looking for