Acknowledgement message for RFC

Hello Everyone,
I am having a scenario where my ABAP transaction invoke a async RFC on XI and sends message to a legacy system using a File Adapter and then updates one Z-table in SAP with appropriate status.XI processes the RFC Sender message and puts file in a target system's configured directory.
The process is working fine.But now I want to have an acknowledgement to SAP system.For that I setted Transport acknowledgement in Send step and in XML monitor I got acknowledgement message.
But how to process this message? I wanted to change the status in the Z-table? Should I create another interface for acknowledgement message and then update Z-table using another RFC? I checked Processing of Acknowledgement on help.sap.com but it says that its automatically send back to the sending system.But if the sending system is sending message asynchronously how it will get the acknowledgement message?
Thanks in advance.
Regards
Rajeev

Hi Rajeev,
If you want to use you scenario I believe you don't have to do any correlation at all:
- if you're using "Transport Acknowledgement" then your process can look like this:
Reveive(RFC) Step -> Send(file)+ ack -> Send(RFC for Z-table) Step
- the send step <b>will wait</b> for the transport acknowledgement
in order to proceed
- so only after it receives the transport acknowledgement it will go to the Send(RFC for Z-table) step.
take a look at Siva's useful weblog:
Usage of Transport level Acknowledgements
/people/siva.maranani/blog/2005/03/01/usage-of-transport-level-acknowledgements
also take a look at: Transport Acknowledgement section
http://help.sap.com/saphelp_nw04/helpdata/en/86/80163f6b5baa09e10000000a114084/content.htm
>>>>For that I setted Transport acknowledgement in Send step and in XML monitor <b>I got acknowledgement message.</b>
if you set everything try to lock the file folder then the File adapter will fail and you shouldn't get the acknowledgement and the process will stop before the Send step (RFC Z-table) - try this test to make sure everything works:)
Regards,
michal

Similar Messages

CCB-MDM Integration | Acknowledgement Message for Initial Sync Reqeust

Hi All,
We are intergrating the CCB-MDM and loaded the contact information to MDM env, but there is no acknowledgement message fired from the MDM. And verified that the +ve, -ve Acknowledgement algorithms are not plugged in to "*D1-InitialSyncRequestContact*" BO lifecycle.
But these algorithms are plugged in to ongoing sync request BO's.
Is there any configuration/installation wrong/missing in the env?
Regards,
Guru

At my previous project we ran into the same 'issue'. The response from Oracle Support:
Because of the volumes involved during initial synchronization, and because the nature of initial synchronization is iterative and closely monitored, no acknowledgements are going to be sent back from MDM. Implementations may choose to delete the initial sync records after they have been produced, or introduce a standard Transition To Next Default State monitor on the Awaiting Acknowledgement state of the parent BO when initial sync requests are being produced. This way, the sync request transitions straight through to Synchronized without waiting for a response from MDM.

Acknowledgement message for Async scenario...

Hello All,
I am working on Asynchronous scenario (IDOC -> File). I have confirgured all the things properly. My problem is when i execute the idoc everything is working fine file got created at FTP. But in sxmb_moni i am getting success message with still wating for acknowledgement "?".... Where i have did the mistake.. as this is async scenario this message is not expected.
Is there anyone who had faced such problem... Please let me know..
Thanks for all your help in advance...

Hi Siddhesh,
By default, Sender IDOC adapter requests IDOC acknowledgement from receiver adapter, when we send IDOC to XI. In your case, System acknowledgement sent by File adapter is converted in to ALE audit message and sent to sender system.
If you want to receive acknowledgement then you need to configure IDOC receiver communication channel.
Refer to this good blog
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
From the above blog....
At times, there could be a scenario where in we do not need the ALEAUD IDOCs to be got back.
To acheive this add the PORT,CLIENT and MESSAGETYPE to the table IDXNOALE.Use transaction SE16 -> specify the table name "IDXNOALE" and then choose create new entries.Specify the values for PORT, CLIENT and MESTYPE fields, save the entry.This procedure helps switch off ALEAUD IDOCs from being sent back to the sender SAP system.
Best Regards,
Divyesh

Idoc acknowledgement message to web service

I am trying to set up the scenario SOAP sender>XI>IDoc Receiver.
I have exposed the outbound, synchronous message interface as a web service, and I'm planning to use sync-async bridge in BPM.
My problem is: I need a response message from SAP. Can I use an iDoc acknowledgement message for this purpose? If this is the case, how do I set up SAP to send this acknowledgement message to XI, and do I have to configure an iDoc sender channel for this purpose?
Any comment is appreciated!
Thanks,
Håvard

One option - not a ABAP expert but this is what I understood with my discussions with my ABAP team when we were coveringt he same issue -
In the Idoc Inbound Processing Code - write a ABAP Exit that after processing the Idoc will trigger the RBDSTATE report to trigger the AleAudit back to XI and XI will send it back to R3.
It is surely possible, as the Aleaudits are triggered by RBDSTATE report instead, you can manually makde the Idoc procesing code to trigger this report immdeitaly and so on.
An Abap , Ale_Idoc specialist will have the answer to this in seconds - on how to do this - but am not one
Regards
Bhavesh

Define fault message type for RFC

Hi,
How can I define the fault message type for RFC so that when I import RFC from another server to XI, I can view this Fault type.
So far I could only see Request and Response type .
Thanks

Hi Rokie,
Acc. to me by default we are having only request and response mesages for RFC and in case some exception/fault is there the RFC will through this in the response under the Return parameter having msg,id number as sub fields which you can map to fault message type.
Sachin

PI 7.11 - Alert creation for RFC Exceptions does not work

Hi folks!
In our PI 7.11 SP04 system we have created an Alert Category as well as an Alert Rule to be informed about errorneous messages in the Integration Engine (ABAP).
The scenario is synchronous SOAP Axis to sRFC, where the RFC answers with an exception that is transferred to a SOAP Fault response message.
Now we see messages with Application Errors in the Integration Engine, but no alert is created. Having a look at the alert creation log using report SXMSALERT_LOGREADER shows us that the system even does not try to create an alert for these messages. Alerts are only created for errors in the Adapter Engine.
Question:
Why does the system not create alerts in this case and how can we achieve this?
Thanx for any hint!
Kind Regards,
Volker

Hi!
Additional information for all:
When forcing an error like "receiver not found" both kinds of alerts are created: AE Alert and IE Alert. Thus in general the alert configuration and the alert rule for IE errors are correct and working - only not for RFC exceptions ....
Regards,
Volker

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.

Processing acknowledgement messages in PI

Hello Experts,
I am having a Mainframe to ABAP proxy scenario where I am updating mainframe data into SAP. Mainframe application expects the acknowledgement after successful update into SAP. I have created another Proxy to Mainframe interface for the same.
But I also found that, the target ECCsystem generates acknowledgement message and sends it back to PI server (I could see the same in SXMB_MONI udner Request message).
I was planning to make use of this message to send acknowledgement back to mainframe system but couldn't find how to acheive this. I tried creating receiver determination for the same but was not of any help.
I had a look at help.sap.com but it talks about processing acknowledgements in Sender ABAP proxy or incase of IDocs but it discusses about querying the acknowledgement messages.
Can we make use to acknowledgement message where senders of the message are not capable of querying this message?
Thanks in advance.
Regards
Rajeev

i don't think this is possible

Problems at receiving messages at RFC-Sender

Hi all,
i have configured the following scenario in NWDS for testing a message flow in PO:
SOAP request comes into PI -> map Request to RFC -> send request to ERP Test System -> wait for RFC Response -> send to PI -> map Response to SOAP -> send to File
Therefore i have, amongst others, created a RFC Channel for sending the RFC response to the mapping operation.When i run the scenario for the first time everything worked pretty well without any error messages. But after testing it the second time the message got stuck in the ERP Test System and couln't be forwarded anymore. It turned out that whenever i deployed the channel with some config changes, the message flow worked for the first time, but crashed after every following.
In the error log i get the following message:
java.lang.RuntimeException: Bean Z_PP_PDES_RESPONSE not found on host xxx, ProgId =RFC_HMC100_POD: Object not found in lookup of Z_PP_PDES_RESPONSE.
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:121)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:267)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Object not found in lookup of Z_PP_PDES_RESPONSE.
When i look in the message log at the same position of a successful message, the log says...
MP: processing local module localejbs/RfcAFBean
... which is actually the module defined in the channel.
So for me it looks like that after the first run something in the module config crashes and the channel tries to use Z_PP_PDES_RESPONSE instead of the RfcAFBean.
Any help very much appreciated!!!
Thanks,
Maurice

Issue has been solved! There has been a running jco server with same program id as the one of the scenario. This led to complications. After stopping the server it worked perfectly...

** Sender Agreement is required for RFC but not IDoc, XI, & HTTP.. Why ?

Hi Friends,
All we know that since IDoc, XI adapters running on Integration Engine (SAP WAS 6.40), Sender Agreement is need not required.
Since RFC is proprietary document for SAP like IDoc, why we are creating Sender Agreement for RFC adpater ? (We know that RFC adpater is running on Adapter Engine, so that ...). Some of our guys asking me this question.
Why is this difference (IDoc adapter running on Integration Engine & RFC adapter is running on Adapter Engine) ? Anyboday can clarify the exact reason on this ...
Kind regards,
Jegathees P.

Hi,
RFC Adapter:
RFC adapter can abe to manage metadata while using the Jco call.This turns the RFC data to RFC xml message.
IDOC Adapter:
But Loading the metadata for IDOC we should create a port and rfc destination.IDOC adapter and metadata container placed in integration server before and after the pipeline step.metadata container converts the IDOC to IDOCxml.IDOC adapter converts the IDOC xml to native xml format.Using idx2 we uploaded the IDOC metadata with the help of RFC destination and port.
Regards,
Prakasu.M

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

No jcoMetadata found for RFC function '/RPM/GET_GEN_LAUNCHER

Hi,
We get initial exception when we click on "portfolio management" tab in the portal while accessing xrpm. The details of error given in the below. We have done the integration as per master guide for xrpm 4.5
I have Integrated the Portal (EP 7.0 EHP1) with backend R/3 ECC6.0(EHP3) with xRPM4.5.
We have installed business packages CPRXRPMUI08_0-10003793.SCA,
BPPPMDC08_0-10003980.SCA.in the portal server.
Please let me the solution
*Error message:*
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function '/RPM/GET_GEN_LAUNCHER_PARAMS'! Please verify, that your model is consistent with the ABAP backend: 'EID'.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to create or init instance of model 'com.sap.xapps.cprxrpm.model.RPMModel' in scope APPLICATION_SCOPE with instanceId 'null'
at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getOrCreateModelInstanceFromScopeMaintainer(WDModelFactory.java:341)
Regards
Madhu

Madhu-
Did you ever find a solution to this error? I am having the same problem.
Thanks,
Jeremy

Password for RFC USer

Hi experts,
We need to set the password for RFC User in small letters.But we are not able to do it ,because of our 'login/*' parameter values.
Is there is any other method to create the password for User ID with small letters(Ex:welcome,hello)?
Thanks in Advance,
Karthika

> > Login rules are not specific to user types. It is same for all type of users.
> Sorry, this is not correct. The password validity rules are a good example which don't apply to SYSTEM and SERVICE type users. Other examples are the idle time rules and compliance to policy rules and the logon ticket rules and remote login via debugging rules and...
>
I tried to talk about is as per the ongoing discussion topic i.e. Case sensitiveness of Passwords and not other attributes. So from this point of view there is no such separate rule applies during admin imposed password or during a change (the cases where system prompts for changing password).
> > From NAS 7 there is a change in the password rules.
> There were major changes in 46B, and 6.10 and 6.40 as well, and Karthika still has not told us which release she is on.
>
Agreed totally.
> > [Note 750390 - USR02: various problems with password attributes|https://service.sap.com/sap/support/notes/750390]
> > [Note 624635 - Error messages with password change using RFC function|https://service.sap.com/sap/support/notes/624635]
> I cannot see how these notes are related to this silly requirement of setting a lower-case only password.
>
I didn't went through in details fully but seen it contains a considerable error details.... may be of any help to OP.
> I think either Karthika is playing a joke on us, or the person interviewing Karthika is playing a joke on her... These would be the only logical explanations left which I can see for for such a requirement.
>
May be.. but of course need more information and purpose of such strictness for setting such password. Also the FM PASSWORD_FORMAL_CHECK can be used with required customizations but you are the best person to tell this properly.
regards,
Dipanjan

Any more configureation needed for RFC -File Syncronous scenario?

HI Experts,
I am working on File to RFC syncronous scenario.
I imported RFC which has Mess, Res and Excep
I have ED which has only Mess
Now I need to send file using File Adaptor to ECC using RFC and ECC has to send resp back to File using File Adaptor.
I created:
MI
MI_File_Meg_os (File Message Output Syncronous) ---> Mess ED
> MT_Res -
> DT_Res
MI_RFC_Meg_is (Input RFC Message ) ---> Mess
> Resp
I cretaed MM for (Message and Response), IM (mapped for both mess and respose) and activated.
I created 3 Communicaiton Channel (File_Sender, File_Receiver and RFC_Receiver), Rec Determination, Sender Aggrement and Receiver Aggrement.
Do I need to create any more objects or configure ?
Thanks in Advance,
Rajeev

You need RFC CC and Filereceiver CC too
Sender Agreement
Do I need to make sender CC for RFC or File receiver CC?
both
Interface determination,
for mapping File request to RFC and RFC response to File
Sender or receiver Aggrements
sender agreements with FileSender CC and receiver agreement for File receiver CC
For getting back Ack from ECC?
RFC is synchronous and can return response
goto wiki and check for pi there is exact scenario
rajesh

Acknowledgement message for RFC

Similar Messages

Maybe you are looking for