|Home • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Implementation of Bridge without using BPM (Using JAVA mapping)
By Sabyasachi Masanta
is often found that the scenario like bridge is usually implemented with BPM
technique in exchanged infrastructure (XI). But BPM has some performance issue.
For that reason many clients want to by pass the BPM.
document enables the developer to implement a scenario of bridge without using
BPM. This scenario is developed with the help of java mapping.
2.0 Business Requirements
need to create the following bridge scenario.
we need to send a file (contain company code) to the SAP XI. In XI we have used
java mapping. This java mapping is calling the RFM (BAPI_COMPANYCODE_GETDETAIL)
from ECC. We are sending company code and getting company name and city from ECC.
And this company name and city are sending to the output file server.
STEP 1 Create
the outbound and inbound data type. For outbound data type we are using
COMPANYCODEID and for the inbound data type we are using COMP_NAME and CITY.
2 Create outbound (using
data type “Outbound_DT”) and inbound (using data type “Inbound_DT”)
4 Create the java mapping.
First of all get the company code from the “COMPANYCODEID” tag.
NodeList n1 = document.getElementsByTagName("COMPANYCODEID");
Now call the BAPI (BAPI_COMPANYCODE_GETDETAIL)
for the company code.
Get the company name and
city in a variable.
returnStructure.getString("COMP_NAME") + "," +
Create the company name
node and city node with their respective values.
+ st.nextToken() + "</COMP_NAME>");
+ st.nextToken() + "</CITY>");
For the Java Mapping, click here.
Export the java mapping
into a .jar file. Now create imported
archives and import the .jar file.
STEP 4 Create
Operation Mapping and use the above imported archives (java mapping).
go to the “Test” tab and test the Operation Mapping with the valid company
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