on 12-15-2006 8:31 AM
Hi folks,
I have a weird problem:
I map IDOCs to a JDBC structure. I use the JDBC to Insert_Update changes that are transmitted in the IDOC.
Now we discovered that the absence of fields in the IDOC leads to these fields missing as well in the JDBC (of course).
A missing field means that the entry needs to be set to "" in the DB though.
My solution approach is that I duplicated the table-subelement and that I want to have a DELETE message first and then the INSERT_UPDATE I already did.
Anyway - when I dupliate the subtree the new subtree is below the old one. But I need the DELETE first.
Does anyone know how to change the order of the sub-trees?
I also tried to copy the mapping down using a mapping template. But mapping templates never work here. They solely map the first element and everything else is not mapped.
Please help. I don't dare to re-do my some 100 elements mapping...
Cheers,
Helge
Helge,
Is your problem:
After suplicate subtree in mapping it is coming below the existing one?
Then why don;t you just copy the mapping of the first node and paste for the second...?
If you right click and copy any function from mapping editor the whole mapping to the left of the functions will be copied and can be pasted for any other node.....
Thanks,
Himadri
Message was edited by:
Himadri Chakraborty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Helge,
I have a crude and very bad idea ... )
The node you are duplicating say A .. the next duplicated node will be represented as A[1] ..
Now in the dataflow editor you click CNTL + SHIFT _ Rt. Click and can export the whole mapping as MTE file..
Open the file in notepad... replace all the As with A[1] and A[1] with A.... and reimport....
You can try this once.. to check if it works or not...
Cheers,
Himadri
Hi,
One option is that you can use a second mapping in the 'Interface Mapping' request side.
Dont duplicate the subtree in the first mapping.
In the second mapping create mapping for Delete statement first, then one to one mapping for the insert_update statement.
If i get any further simpler technique will post you that.
Regards,
P.Venkat
Message was edited by:
Venkataramanan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the suggestion.Anyway - it's not really an option since that would required to touch every mapping.
an I have really a lot of fields here...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Helge,
>>Now we discovered that the absence of fields in the IDOC leads to these fields missing as well in the JDBC (of course).
A missing field means that the entry needs to be set to "" in the DB though.
You can map only for the input fields which can be empty during run time..
Your mapping would be like this
Source node -- mapWithDefault -- Target node
Am not sure, if there is annother easy work around to this...
Regards,
Jai Shankar
Have you tried "mapWithDeafault" available in node functions?
Regards,
Jai Shankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.