|Home • Trainings • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Multiple occurrence of file to single occurrence of RFC
the structure conversion need to be done. Define the Interface mapping which we
will be needed in Directory.
up the source Message interface & target message interface as shown
the Occurrences in target Message interfaces to 0.unbounded as this is
the occurrences of target interfaces to 0—unbounded as shown
message mapping need to be defined between the Source Message Type & target
mapping for the corresponding Interface mapping
objects & activate all the design time objects.
change list and expand the SWCE right click on standard change list and click on
activate by selecting the objects.
We are now
going to create A2A scenario manually.
scenario & name it then save it.
Scenario is created & saved, it is displayed in Left panel
following steps need to be performed
Business Systems: Import the Business systems from SLD. Select the appropriate
the systems & click on import, make sure the option “create communication
channel automatically is unchecked”. Because we would like to create them
the sender is file system, choose the Adapter type as File.
configure the Adapter dependent & independent properties
RFC Receiver adapter with server specific properties.
Integration Process: import the BPM from IR into
step is to be done in order to import the BPM from IR to ID
the Appropriate receiver for this message.
contains 2 steps.
BPM to R/3 System
the Appropriate inbound message interface & the interface mapping created in
IR for this message.
contains 2 steps.
To R/3 System:
the Inbound interface (outbound) for BPM and Inbound For RFC.
the Sender Agreement. This makes the binding between the sender system &
sender message interface & communication channel
the receiver Agreement. This makes the binding between the sender system &
receiver system, receiver message interface & communication channel
XML file into the folder on FTP server, as mentioned in the properties of sender
uses Pull mechanism to pick up the file as per pool interval, And depending on
the mode (delete in this case) the file is deleted from the sender folder
the Transaction code SXMB_MONI, to check the incoming messages.
log on to the R/3 system (backend) and check the data base table for entries.
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