| Author |
Message
|
| marko.pitkanen |
 Posted: Mon Sep 10, 2012 4:10 am Post subject: WMB 7 IDocs with short segement names? |
 |
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
I'm sorry I did only a quick search with Google and found no confirmation if I can set properties at the Toolkit's Wizard so that also segment names would use SAP's short way (like SapOrders05Zeorders05E2edl37005 would be E2EDL37005 ). Can anyone point me to the documentation I can study this?
Metadata seems to contain the required information:
| Quote: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="SapOrders05Zeorders05E2edl37005" nillable="true" type="saporders05zeorders05e2edl37005:SapOrders05Zeorders05E2edl37005">
<xsd:annotation xml:space="preserve">
<xsd:appinfo source="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata">
<sapasi:sapALEPropertyTypeMetadata>
<sapasi:FieldName>E2EDL37005</sapasi:FieldName>
|
--
Marko |
|
| Back to top |
|
 |
| mapa |
| Posted: Mon Sep 10, 2012 5:28 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
I am pretty sure this is only possible for the actual field names, not the segments themselves.
I normally check both "Use SAP field names to generate attribute names for ..." and "Use SAP-original casing for ..."
I guess this is the most relevant link as you've surely found already:
Naming conventions for ALE business objects |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Mon Sep 10, 2012 10:57 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Thanks mapa,
I tried to find this functionality from the InfoCenter and by trying several setting with Wizard with no luck. It seems that tool doesn't support this.
Luckily I can make a script that walks through all mxsd -files in exported message set and sets segment names from metadata to shorter version. (I tested this and edited message set seems to be valid for the Toolkit and can be compiled into bar and deployed to runtime and it produces a message tree with short names.)
I don't recommend this unofficial approach to anyone else.
Hopefully some one can show a official way to do this or I can convince SAP and third party people that long --broker's generated- segment names are good enough.
--
Marko |
|
| Back to top |
|
|
| mapa |
| Posted: Mon Sep 10, 2012 11:11 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
A classic 
Might get you into trouble though if you will do iterative discovery later on.
Unless you keep the orginal, update it and then do your procedure again, or? |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Mon Sep 10, 2012 11:36 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Good point mapa!
A lot of troubles can arrise and I have to handle them with my own support only if I choose to go on with this script approach. I think it would be wise to export message definition with Wizard and then copy message set project to another name, do modifications and experiments only to this copied project. Then I can use official supported functions to original message set.
--
Marko |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Mon Sep 10, 2012 9:26 pm Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
We decided to use message definitions in the form they are produced by the tool.
--
Marko |
|
| Back to top |
|
|
|
|
