JMS to JDBC scenario

Hi All:
I need to create one JMS to JDBC Scenario. For Sender side i.e JMS what I need to do.
Like I dont have any messaging System like MQ series etc. I have JMS client and I know how to use JMS adapter, but where should I create Queue? In there any way like we can
create Test queue in XI and can send the data from JMS client to that Queue?
Also if the and Messaging Sysytem that I can download as a trial version please let me know with the required setting in XI.
Thanks & Regards,
Farooq.

Hello Farooq,
Instead of creating a queue in visual admin, I would suggest you to use the default queue provided by XI.
Please have a look at the parameters(Sender/Receiver):
Select the Transport Protocol as 'Access JMS Provider with JNDI'
JNDI Lookup Name of QueueConnectionFactory: jmsfactory/default/QueueConnectionFactory
JNDI Lookup name of JMS Queue: jmsqueues/default/sapDemoQueue
Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
JNDI Server Address: <Host Name of your XI server>:<J2EE Port>
JNDI Logon User and Password are not mandatory.
Please note that you will not be able to monitor the sapDemoQueue. However you can test your scenario by doing a File to JMS scenario first and then a JMS to File scenario.
Before granting points please let me know if this helped you out.
Thanks,
Pritish

Similar Messages

Error comming in File to JDBC scenario.

Hi Frnds,
I am trying to do the File to JDBC scenario and is using the SQLServer.
After processing the message, it is showing executed successfully in moni but for the receciver communication channel i am getting the error like---->
Error during database connection to the database URL 'jdbc:sqlserver://10.112.132.211:1433;databaseName=DemoDB' using the JDBC driver 'com.microsoft.jdbc.sqlserver.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:sqlserver://10.112.132.211:1433;databaseName=DemoDB': SAPClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver'
What could be the possible solution for it.
Thnx
Raj.

Hi Raj,
As Prateek mentioned, the error you are getting is because of an improper installation of a driver.
Check out the doc for the driver installtion steps : [How To Install and Configure External Drivers for the JDBC & JMS Adapters|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f]
Also, the following thread contains some more useful links : Re: What's necessary to connect SQL server to XI?
Thanks,
Pooja Pandey

Need information regarding IDOC to JDBC Scenarios.

Hi,
Kindly help me with the pre-requisites inorder to start with a scenario of IDOC to JDBC and also the scenario of JDBC to IDOC.
Regards,
Sreedhar, Av

Hello Sreedhar,
While we working in JDBC or JMS Adapters we should deploy the Drivers..
Go through this links,
/people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
To install JDBC driver follow the how to guide.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
Configuration of JDBC Adapter for SQL Server
JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
UserID and Password.
If the connection is not working find the correct port number.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
JDBC- X I - R/3 Scenario
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Please check the driver path as mentioned below.
JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
No JDBC driver required.
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
follow this thread
Re: Problem when connecting to MS Access through JDBC Adapter.
SAP Note 850116 has details
2) While we working in IDOC Adapters we should do ALE Config of IDOC Settings .
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Here in IDOC to JDBC interface we need not to config sender Adapter..
1) The main usage of a sender adapter is to convert the input format into the XI supported XML format.
Once the conversion is completed the sender agreement appends the header with the sender details.
In case of these adapters we wont require sender agreement and sender communicationchannel for the
following reasons.
Sender agreement is associated with a namespace when we shoot an idoc frm r/3 if already contains its standard sap namespace. so those is need of sender agreement
The sender communication channel use is to identify the sending system and adapter, as the idoc header contains the details there is no need to sender.
These adapters resides on ABAP stack here the integration server takes care of IDOC/HTTP to XML conversion without requirement of adapter.
The business system that is sending the adapter has already been assigned to a techinical system which normally acts as an integration server...
IDOC to xi links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Hope this explanation is useful to u..
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on Jun 3, 2008 9:57 AM

Sample scienario on JMS to JDBC/File

Hi,
Can any one send me the sample scenario on JMS to JDBC or FILE. Any suggestions for how to configure JMS with MQ will be helpful for me .
Thanking you with anticipation
Regards
Ramesh.

Hi Ramesh,
Go thru these links :
http://help.sap.com/saphelp_nw04/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/e6fb40f17af66fe10000000a1550b0/frameset.htm
And these threads
JMS and MQ Series (sender and receiver)
SAP XI and JMS for WebSphere MQ
JMS - MQ Series
Hope these will be helpful.
Regards
Suraj

JMS to JDBC

Hi Friends,
This is Bhavya.Right now I am working with the interface i.e. JMS to JDBC.
Can anybody send me the sample scenario?
Thanks,
Bhavya...

Hi Bhavya,
First you need to install the external drivers for JMS and JDBC adpater.
You can check the following link for that.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bf4b1055-0d01-0010-32a3-b3848d77a6b9">How to Install and Configure External Drivers for JDBC JMS</a>
Now your sender service is an JMS server, the details of which you must have..which you will provide it in the channel...it is not that complicated....
For JDBC side..
Check the following blog for the same.
<a href="/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30">FILE to JDBC Adapter using SAP XI</a>
*Reward points if helpful*
Regards,
Sushil

XI idoc-jdbc scenario in details

Hi Experts,
Please provide me this scenario pn detail.
Cheers
Aman

Hi,
For IDOC to JDBC scenario:
Refer the below weblog for help:
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 --> for jdbc receiver: file -JDBC
1) First you need to install the JDBC drivers on XI server refer the below link for installation process.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
2) You need to do the IDOC configuration at R3 as well as at Xi end:
Refer the below configuration steps:
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
Configuration required at Xi side:
Go to IDX2: load the DOC metadata.
3) For updating the table you need to write the stored procedure:
Refer the below link for stored prcedure.
JDBC:
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
Stored Procedures-
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
http://www.ics.com/support/docs/dx/1.5/tut6.html
/people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
http://www.ics.com/support/docs/dx/1.5/tut6.html
http://java.sun.com/docs/books/tutorial/jdbc/basics/sql.html
http://www.sqlteam.com/article/stored-procedures-an-overview
Thnx
Chirag
Reward points if it helps and close the threads.

Pass system ack of JDBC adapter to ERP in IDoc - XI - JDBC scenario

Dear all,
i have an IDoc -> XI -> JDBC scenario (without using ccBPM). In the standard way the ERP system, sending the IDoc waits for an application acknowledgement. However the JDBC adapter is only capeable to send system acknowledgements.
Is there a way to pass these acknowledgements to the IDoc status record?
In help.sap.com (http://help.sap.com/saphelp_nwpi71/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm) under "IDoc Processing with the IDoc Adapter " there is a table that maps XI system/applic acknowledgement to IDoc status. So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
Can anyone tell, if this is really working? What if I deactivate the acknowledgement request in the NOALE programm?
In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
Many thanks and best regards
Florian

Is there a way to pass these acknowledgements to the IDoc status record?
Without BPM, No.
So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
The ack referred here is related to idoc status whether it is properly reached till XI or not and not related to the JDBC ack.
What if I deactivate the acknowledgement request in the NOALE programm?
Then u won't have any ALEAUD message at sender R3.
In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
No
Regards,
Prateek

Problem in JDBC to JDBC scenario

Hello all,
I am working on a JDBC 2 JDBC Scenario.
Everything gone fine, data is picked from source, but it is not updated in the destination.
I could not see any message related to this in SXMB_MONI it shows only messages related to IDOC, on search I fould, we need to add trace level,etc in SXMB_ADM but still couldnot found any message (I restarted the system, cleared cache also).
In RWB(communication channel monitoring) I could find that sender is sucessful, but no message for receiver.
In RWB (message monitoring) I checked my business system, i could see sender entries but no receiver entries, there is only one error message as :
 transmitting the message to endpoint http://xisystem:50100/sap/xi/engine?type=entry using connectio
For which I found we need to change XI businesssystem's pipeline port no from some 54+++ to 4+++ (but I could see only 50100 in the pipeline so i did'nt)
we are using R/3, was7.0 sp11,XI3.0,
Can any body help me in this regard
Thanks,
Sai.k.k

Hi,
Error in SXMB_MONI :
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_JDBC2JDBC_MM_: RuntimeException in Message-Mapping transformatio~
Error in Integration repository when I test with the payload :
<pre>
13:01:52 Start of test
Document start
Start tag [ns0:Receiver_JDBC_MT]
Add raw attribute [ xmlns:ns0="http://xyz.com/JDBC2JDBC_NMSP"]
Start tag [Statement]
Start tag [dbTable]
Add attribute: [action]=[INSERT]
Start tag [table]
Put value [Example]
Close tag [table]
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)com.sap.aii.utilxi.misc.api.
BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException:Fatal
Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) ->
com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
13:01:52 End of test
</pre>
Query : Select * from Employee fetches all the fields
Payload :
<pre> <?xml version="1.0" encoding="utf-8" ?>
- <resultset>
- <row>
<PerNer>t</PerNer>
<Initials>t</Initials>
<Name>t</Name>
<DOB>t</DOB>
<State>t</State>
<Country>t</Country>
</row>
</resultset>
</pre>
Regards,
Sai.k.k

Error"SYSTEM Failure" while testing the RFC in SE37 : RFC to JDBC Scenario

Hi All,
I am doing RFC to JDBC scenario. When I am testing the RFC in SE37 using the RFC destination created in SM59, I get an error "SYSTEM FAILURE".
Please suggest.
Thanks,
Shyam
Edited by: Shyam Sreepada on Dec 18, 2007 5:46 PM

Hi,
You must run RFC with RFC destination in background mode, I suggest to read following post in order to understand it better.
Syntax would be:
CALL FUNCTION func IN BACKGROUND TASK
[DESTINATION <your RFC destination>]
parameter list
http://help.sap.com/saphelp_nw04/helpdata/en/8f/53b67ad30be445b0ccc968d69bc6ff/frameset.htm
If you read it you will find that you can't test it directly from SE37, for this either you need to create dummy ABAP program or another RFC where you will call this RFC with background syntax.
Regards,
Gourav
Reward points if it helps you
Edited by: Gourav Khare on Dec 18, 2007 6:07 PM

IDOC to JDBC scenario in case of Cost Element Group IDOC.

This is an IDOC to JDBC scenario.
The Cost Element Group IDOC is having different segments. The main segment E1COGH (1...unbound) is consisting of different subsegment like E1OGS (0...unbound) & E1COGV (0...unbound). The main segment (E1COGH) along with subsegments E1OGS & E1COGV) is occuring more that 1 times. I have to insert data into the table, which we can do in single rows (no hierarchy is possible in tables). I have used "use one as many" in message mapping. Now if E1OGS or E1COGV is repeating in a single E1COGH segment then we dont get any error. But if I duplicate the main segment then I am getting runtime exception.
Please suggest about how to map in this case.

In my scenario:
     E1COGH
     |
      -> E1COGS
         E1COGV
where     E1CGH -> Main segment
     E1COGS & E1COGV -> sub segment
E1COGH -> 1..unbound
E1COGS -> 1..unbound
E1COGV -> 1..unbound
At the target side I have created two Statement Structure (ie.Statement & Statement_1) . One for E1COGS (ie. Statement) & the other for E1COGV (ie. Statement_1).
Case 1 -> If E1COGS is present in the main segment E1COGH then it is mapped AS IS.
Case 2 -> If E1COGS is not present in the main segment E1COGH then it is mapped as blank.
This will be mapped with Statement & in the absence of E1COGS this Statement structure is SUPPRESSED.
Similarly,
Case 1 -> If E1COGV is present in the main segment E1COGH then it is mapped AS IS.
Case 2 -> If E1COGV is not present in the main segment E1COGH then it is mapped as blank.
This will be mapped with Statement_1 & in the absence of E1COGV this Statement_1 structure is SUPPRESSED.
All the elements of the segment E1COGH, E1COGHT & E1COGHR are replicated in all the rows for X (no. of occurance of E1COGS) + Y (no. of occurance of E1COGV).
While testing in Message Mapping, I am able to get the output as for multiple occurence of E1COGS & E1COGV in a single E1COGH.
But if I increse the occurence of E1COGH the it is giving the following error :
Runtime exception during processing target field mapping /ns0:MT_Cost_Element_Group_Response/Statement/DBtablename/access/GROUPNAME. The message is: Exception:[com.sap.aii.mappingtool.tf3.IllegalInstanceException: Too few values in first queue in function useOneAsMany. It must have the same number of contexts as second queue.] in class com.sap.aii.mappingtool.flib3.NodeFunctions method useOneAsMany[com.sap.aii.mappingtool.flib3.CollapseContexts@51197231, , ]
Please suggest how to map the occurence of E1COGH simultaneously with the occurence of E1COGS & E1COGV.

Sender side Synchoronous jdbc scenario

Hii experts,
Can we do Sender side synchronous jdbc scenario?? if yes give me an example how the scenario will look like??
and what are the steps has to be done?
Regards,
Balaji

Hi,
Can you pls clear your requirement?
In your case, do sender JDBC will fetch the data and give it to the target, and again target will give some resonse and that
response you have to insert into the database at sender side?
If this is the case for you, then it can be achieved.
Pls exactly tell what you are looking for.
-Tanaya.

Test cases for File to JDBC scenario?

Hi Experts,
I would like to know what are the things needs to be tested to ensure that the File to JDBC scenario holds good in the PI box. Your valuable inputs are required to verify /check my scenario configuration is free of errors.
Thanks & Regards,
Pcv.

Hi,
You can try the following:
1) If the end systems require authentication and the same is not provided in PI then it should throw an error.
2) Check what happens when you dont give a mandatory field.
3) check what result you will get when you give a wrong input.
4) Check whether all your restrictions (in mapping and/or in receiver determination) are working properly.
5) Check what you need to do when the target system is down.
6) If using any FCC then check whether the conversion is done properly.....
7) See to it that you have defined a proper DB structure when you are communication with JDBC
8) Check with the end system whether your statement (Insert/Update/Delete etc) is performed properly
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 4, 2008 9:58 AM

File-Jdbc scenario

Dear Friends,
I am performing Simple File to JDBC scenario. For this I am using MySql. I have designed and configured all the required steps and activated. Now I went to Runtime Work Bench monitoring.. Here in Message monitoring status is "waiting". Here it has thrown one exception like this, Exception caught : Jdbc Receiver Channel:Configuration not initialized due to loading Jdbc receiver
"com.microsoft.sqlserver.SQLServerDriver" Failed :java.lang.ClassNotFound - Exception : com.microsoft.jdbc.sqlserver.SQLServerdriver.
Please help me,Now what i have to perform.
thanks in advance.

check this
http://help.sap.com/saphelp_nwce10/helpdata/en/45/08546ff5200486e10000000a155369/content.htm
and
https://wiki.sdn.sap.com/wiki/x/sAA7AQ
Regards,
Ravi

Mapping issue in idoc to JDBC scenario

mapping issue in idoc to JDBC scenario
source structure
E1KNB1M
BUKRS = 1000
E1KNB1M
BUKRS= 9000
E1KNB1M
BUKRS= 2000
THE NODE E1KNB1M is repeated many times and the field BUKRS is also repeated with E1KNB1M as above
TARGET field : ISFRANCHISE
if any where value of BUKRS =9000 we have to pass Y to the target filed, else N
if BUKRS = 9000   THEN ISFRANCHISE= Y
               ELSE
            ISFRANCHISE=N
I've done the mapping as below
BUKRS = 9000--> IF THEN Y ELSE N--
> ISFRANCHISE
BUT everry time the target value is N only
pl suggest
rgds
mojib

mapped like this
BUKRS--->SORT---->
                                             EQUALS --------IF---THEN    Y
9000------------------------>                                               ----------------->ISFRANCHISE
                                                              ELSE   N
context of BUKRS set to parent node
its worked
thanks to all for valuable suggestions
rgds
mojib

SOAP TO JDBC scenario: calling stored procedure which will return the value

Hi
I have Soap To Jdbc scenario in which I am going to call the Stored Procedure at target side which will be executed and it is going to return the result set .
Result contains following values.
return code as ( 0 Or 1) and also specific exception message if its return code as 1.
Could you suggest me the way by which I can handled this return code and send it back to the Sap PI system then the same thing is directed the to SMTP server for sending mail to consern person.
Regards
Kumar

The OUT parameters of stored procedure will be returned as response. Where exactly are you facing the proble? Here is a complete walkthourgh
/people/luis.melgar/blog/2008/05/13/synchronous-soap-to-jdbc--end-to-end-walkthrough
In your case, you don't want response at sender. Instead you want to mail it. For this you may use BPM to design your scenario with following steps
Receive (to receive data from sender)
Send Sync (to stored procedure and get response)
Send Async (to mail receiver)
Regards,
Prateek

JMS to JDBC scenario

Similar Messages

Maybe you are looking for