|Home • Trainings • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Usage of SOAP Lookup and RFC Lookup in a single Mapping Program
adding the outbound message type and inbound message types perform the mapping
between the fields as shown below
above screen the input fields FromCurrency
and ToCurrency are mapped to the
target field ForexRate which is under
message type MT_IB_SoapLookup using
the UDF SoapLookUp.
the two receiver communication channels in the ID, one is for the SOAP
adapter and the other is for the RFC
adapter. Since we are using the soaplook and the rfclookup in our mapping we
need to maintain the business system name and the respective communication
channel names in the UDF.These
communication channels will help to get the output from the RFC and web service
based on the values given in the input fields in the message mapping.
the message mapping. If you observe the below screen based on the input values
the output got generated from the RFC and Web service. The Field ForexRate which
has the value 79.4937 is coming from
the web service (of course it may vary from day to day) and the ForexRate which
is having the value 80 is coming from
interface mapping between the outbound interface and the two inbound interfaces
as shown below. In the inbound side add the two interfaces by using the add
in the Integration Directory:
sender communication channel with adapter type FILE and two receiver
communication channels with adapter types FILE and two more receiver
communication channels for RFC and SOAP as discussed above.
Business systems for sender communication channel and receiver communication
channels. For RFC and SOAP receiver channels use business service and for the
RFC business service maintain the adapter specific identifiers.
File sender communication channel and maintain the required parameters like
source directory and file name, FTP parameters and the processing mode.
two File receiver communication channels and maintain the required parameters
which were not showed here.
SOAP receiver communication channel and maintain the target URL and soap action.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards