HL segments in a schema and the mapper

Tech-Archive recommends: Fix windows errors by optimizing your registry

Everyone,

I have a destination schema that contains the following segment:

the node is:

<xs:element maxOccurs="unbounded" name="HL_Hierarchical_Level_S4"
type="Hierarchical_Level_S4_type" />

and the underlying type is:

<xs:complexType name="Hierarchical_Level_S4_type">
- <xs:sequence>
- <xs:element name="_628_Hierarchical_ID_Number_E1"
type="Hierarchical_ID_Number__003__040">
- <xs:annotation>
- <xs:appinfo>
<fieldInfo implied_decimals="No" />
</xs:appinfo>
</xs:annotation>
</xs:element>
- <xs:element minOccurs="0" maxOccurs="1"
name="_734_Hierarchical_Parent_ID_Number_E2"
type="Hierarchical_Parent_ID_Number__003__040">
- <xs:annotation>
- <xs:appinfo>
<fieldInfo implied_decimals="No" />
</xs:appinfo>
</xs:annotation>
</xs:element>
- <xs:element name="_735_Hierarchical_Level_Code_E3"
type="Hierarchical_Level_Code__003__040">
- <xs:annotation>
- <xs:appinfo>
<fieldInfo implied_decimals="No" />
</xs:appinfo>
</xs:annotation>
</xs:element>
- <xs:element minOccurs="0" maxOccurs="1"
name="_736_Hierarchical_Child_Code_E4"
type="Hierarchical_Child_Code__003__040">
- <xs:annotation>
- <xs:appinfo>
<fieldInfo implied_decimals="No" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="LIN_Item_Identification_S5"
type="Item_Identification_S5_type" />
<xs:element minOccurs="0" maxOccurs="unbounded"
name="SN1_Item_Detail__Shipment__S6" type="Item_Detail__Shipment__S6_type" />
<xs:element minOccurs="0" maxOccurs="100"
name="SLN_Subline_Item_Detail_S7" type="Subline_Item_Detail_S7_type" />
<xs:element minOccurs="0" name="PRF_Purchase_Order_Reference_S8"
type="Purchase_Order_Reference_S8_type" />
<xs:element minOccurs="0" maxOccurs="unbounded"
name="PO4_Item_Physical_Details_S9" type="Item_Physical_Details_S9_type" />
<xs:element minOccurs="0" maxOccurs="200"
name="PID_Product_Item_Description_S10"
type="Product_Item_Description_S10_type" />
<xs:element minOccurs="0" maxOccurs="40" name="MEA_Measurements_S11"
type="Measurements_S11_type" />
<xs:element minOccurs="0" maxOccurs="25" name="PWK_Paperwork_S12"
type="Paperwork_S12_type" />
<xs:element minOccurs="0" maxOccurs="25"
name="PKG_Marking__Packaging__Loading_S13"
type="Marking__Packaging__Loading_S13_type" />
<xs:element minOccurs="0" maxOccurs="20"
name="TD1_Carrier_Details__Quantity_and_Weigh_S14"
type="Carrier_Details__Quantity_and_Weigh_S14_type" />
<xs:element minOccurs="0" maxOccurs="12"
name="TD5_Carrier_Details__Routing_Sequence_T_S15"
type="Carrier_Details__Routing_Sequence_T_S15_type" />
<xs:element minOccurs="0" maxOccurs="12"
name="TD3_Carrier_Details__Equipment__S16"
type="Carrier_Details__Equipment__S16_type" />
<xs:element minOccurs="0" maxOccurs="5"
name="TD4_Carrier_Details__Special_Handling__S17"
type="Carrier_Details__Special_Handling__S17_type" />
<xs:element minOccurs="0" maxOccurs="unbounded"
name="REF_Reference_Numbers_S18" type="Reference_Numbers_S18_type" />
<xs:element minOccurs="0" maxOccurs="3"
name="PER_Administrative_Communications_Conta_S19"
type="Administrative_Communications_Conta_S19_type" />
<xs:element minOccurs="0" maxOccurs="200" name="CLD_Load_Detail_S20"
type="Load_Detail_S20_type" />
<xs:element minOccurs="0" maxOccurs="unbounded"
name="MAN_Marks_and_Numbers_S22" type="Marks_and_Numbers_S22_type" />
<xs:element minOccurs="0" maxOccurs="10" name="DTM_Date_Time_Period_S23"
type="Date_Time_Period_S23_type" />
<xs:element minOccurs="0" name="FOB_F.O.B._Related_Instructions_S24"
type="F.O.B._Related_Instructions_S24_type" />
<xs:element minOccurs="0" name="PAL_Pallet_Information__PAL__S25"
type="Pallet_Information__PAL__S25_type" />
<xs:element minOccurs="0" maxOccurs="200" name="N1_Name_S26"
type="Name_S26_type" />
<xs:element minOccurs="0" maxOccurs="50"
name="SDQ_Destination_Quantity_S33" type="Destination_Quantity_S33_type" />
<xs:element minOccurs="0" name="ETD_Excess_Transportation_Detail_S34"
type="Excess_Transportation_Detail_S34_type" />
<xs:element minOccurs="0" maxOccurs="unbounded"
name="CUR_Currency__CUR__S35" type="Currency__CUR__S35_type" />
<xs:element minOccurs="0" maxOccurs="10"
name="ITA_Allowance__Charge_or_Service_S36"
type="Allowance__Charge_or_Service_S36_type" />
<xs:element minOccurs="0" name="GF_Furnished_Goods_and_Services_S37"
type="Furnished_Goods_and_Services_S37_type" />
<xs:element minOccurs="0" maxOccurs="10"
name="LM_Code_Source_Information_S38" type="Code_Source_Information_S38_type"
/>
</xs:sequence>
</xs:complexType>




I need to be able to map to this segment from a source document and I am
having trouble forcing the parent/child IDs. I am always ending up with one
flat version of the HL segment with 4 IDs for the node IDs (1,2,3,4) four IDs
for the parent segment (0,1,2,3) and four identifier IDs.

How can I map multiple loops to this record? I cannot get it and I've tried
everything the mapper has to offer.
.

Relevant Pages

  • Re: HL segments in a schema and the mapper
    ... Use the Xslt code in the Xslt Script functoid. ... BizTalk Solution Developer ... I need to be able to map to this segment from a source document and I am ... having trouble forcing the parent/child IDs. ...
    (microsoft.public.biztalk.general)
  • Re: x-forwarded-for an IDS capability
    ... spyware-infected PCs phoning home through our proxies - and so the IDS ... snort onto all our proxies :-) Now snort can see the clients. ... In my opinion would it not be easier to simply place and IDS on each segment and have it send the logs to a parent IDS system on a secured segment of the network? ... I'm considering this at my current place of employment to simply allow me to see our VPN sites as well. ...
    (Focus-IDS)
  • Re: distance approximation in 3D
    ... On a big 3D map with many actors this function will be ... You can divide the dungeon into "segments" (each room a segment; ... You can cache A* results for monsters in the same origin segment ... Or you can do effective pathfinding without A*. ...
    (rec.games.roguelike.development)
  • Re: [PATCH] [request for inclusion] Realtime LSM
    ... > segment and move your stack pointer into a second segment. ... > Or, going the other way, the client app can pass map handles to the ... look at the realtime LSM patch, ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Nets on a Sphere
    ... Lee Rudolph wrote: ... consider S^2 with its riemannian geometry. ... say of f that "its restriction to each segment of Z" ... should be "a C^1 map which preserves distances", ...
    (sci.math)