| Author |
Message
|
| Qadeer_824 |
 Posted: Tue Feb 05, 2008 8:39 am Post subject: Information on a scenario.. |
 |
|
Acolyte
Joined: 04 Oct 2007
Posts: 59
|
Hi,
I'm trying to execute the following scenario:
InputFile -> JavaCode -> Queue(TEST1) -> MsgFlow (Transform to idoc XML) -> WBIA SAP Connector -> SAP
An input file is picked up by java code and it copies the data to a Queue. This data is received by a message flow which constructs an xml structure of idoc, passed to WBIA SAP Connector to push data into sap.
for this, i'm done with creating the java code and data now reaches the message flow. The input data is csv values, and i've happily created a message set to parse it.
Now, i have to transform this csv data to idoc using some mapping rules.
Can someone please tell me how do i create the messageset to convert it to idoc xml (ACC_BILLING02 idoc) and send to SAP connector?
Even pointers to such scenario's can help me out.
Thnx,
Qadeer |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Tue Feb 05, 2008 9:11 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| If you use MB v6.1, the message set is automatically generated for you (the MBToolkit queries the SAP business objects directly). |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 05, 2008 11:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And if you are not using 6.1 you need to ask you SAP team to provide you with the C type structure for the IDOC.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kirankinnu |
| Posted: Tue Feb 05, 2008 11:35 am Post subject: |
|
|
Centurion
Joined: 12 Jun 2004
Posts: 128
Location: Chicago, IL
|
You need to import the IDOC's by using the Object discovery Agent(mySAP Adapter). IDOC's will be imported as xsd files. Later you can import the xsd's into your workspace as Message definition files.
If you have the latest version of Broker, I think you can import the IDOC structure from the toolkit itself.
Thanks,
Kiran |
|
| Back to top |
|
|
| Qadeer_824 |
| Posted: Wed Feb 06, 2008 12:18 am Post subject: |
|
|
Acolyte
Joined: 04 Oct 2007
Posts: 59
|
Thnx for the replies.
Yes, i do have access to SAP server and connected to it using BO Designer and SAP ODA. Got the BO's and saved them as xsd's.
Now when i create message set with these xsd's (selecting XML Schema as source), i'll need to create one "mxsd" for each "xsd" file. Is it not possible to have a single mxsd which includes all xsd's ? |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Feb 06, 2008 1:21 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Is it not possible to have a single mxsd which includes all xsd's ? |
Why would you want that? It is usually a good idea to separate a large schema into a group of xsds ( modularity, reduced build times if changes are made etc ). |
|
| Back to top |
|
|
| Qadeer_824 |
| Posted: Wed Feb 06, 2008 5:18 am Post subject: |
|
|
Acolyte
Joined: 04 Oct 2007
Posts: 59
|
Well yes, it doesnt' really make sense in pulling everything to single definition. I asked that bocz i already have a few idoc related msg sets which have everything in a single mxsd.
I've never used V2.1 of MB. Was there any restriction on creation of msgsets / parsers in it?
And yeah, thnx a lot for ur replies. I've complete the scenario successfully.  ..
Just to complete the thread with a solution,
Once you're done with importing of xsd's into toolkit, create mxsd's for each xsd and make sure that you have set the XML Rendering options correctly (if not using namespaces for SAP Connector).
After the transformation esql is written, deploy and u get hte transformed output which passes to the SAP Connector and hence to SAP 
Many Thnx,
Qadeer. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 06, 2008 5:27 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Qadeer_824 wrote: |
| I've never used V2.1 of MB. Was there any restriction on creation of msgsets / parsers in it? |
Yes. It's entirely out of support, and shouldn't be used for anything, including the creation of msgsets or custom parsers.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 06, 2008 5:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Qadeer_824 wrote: |
I've never used V2.1 of MB. Was there any restriction on creation of msgsets / parsers in it?
|
The product was one giant restriction, starting with the GUI and ending with the broker.
It's long gone and I do not mourn it's passing. While there may well still be a few instances out there, the sooner they're humanly shot the better for all of us.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
