Mapping FlatStructure from FileAdapter to Hierarchical IDOC
We want to map the following FLAT-Structure to an Hierarchical IDOC-Structure
ZUECH_0210
recordset
H1
H2
H6
D1 (1 to unbounded)
D2 (1 to unbounded)
Meterno1
D3 (1 to unbounded)
Q1
D3
Q2
D2
Meterno2
D3
Q1
D3
Q2
D3
Q3
/recordset
IDOC_ZUECH_210
IDOC
HEADER
H1
H2
H6
/HEADER
D1 (1:1)
D2 (1:99)
D3 (1:99)
/IDOC
We tried D3 splitbyvalue to D3 => below D2 there is only one D3 mapped?
Any ideas how to keep the values from D3 below the according D2?
We went through
http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm.
It didn't help us very much
Here the <b>source structure</b>
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2007 (http://www.altova.com) by d2k (-) -->
<!--W3C Schema generated by XMLSpy v2007 (http://www.altova.com)-->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:rwe-nl:xi:interfaces_ext:global">
<xs:element name="ZUECH_0210">
<xs:complexType>
<xs:sequence>
<xs:element name="recordset" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="H1">
<xs:complexType>
<xs:sequence>
<xs:element name="KH1" type="xs:string"/>
<xs:element name="H1" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="H2">
<xs:complexType>
<xs:sequence>
<xs:element name="KH2" type="xs:string"/>
<xs:element name="H2" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="H3">
<xs:complexType>
<xs:sequence>
<xs:element name="KH3" type="xs:string"/>
<xs:element name="H3" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="H4">
<xs:complexType>
<xs:sequence>
<xs:element name="KH4" type="xs:string"/>
<xs:element name="H4" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="H5">
<xs:complexType>
<xs:sequence>
<xs:element name="KH5" type="xs:string"/>
<xs:element name="H5" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="H6">
<xs:complexType>
<xs:sequence>
<xs:element name="KH6" type="xs:string"/>
<xs:element name="H6" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="MEDTD1" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="KMEDTD1" type="xs:string"/>
<xs:element name="REQUEST_ID" type="xs:string"/>
<xs:element name="TRANSACTION_ID" type="xs:string"/>
<xs:element name="CONNECT_EAN" type="xs:string"/>
<xs:element name="REASON_ID" type="xs:string"/>
<xs:element name="PERIOD_STARTDATE" type="xs:string"/>
<xs:element name="PERIOD_ENDDATE" type="xs:string"/>
<xs:element name="SUBMITTED_DATE" type="xs:string"/>
<xs:element name="MARKET_SEGMENT" type="xs:string"/>
<xs:element name="NETOP_EAN" type="xs:string"/>
<xs:element name="REQUEST_REFERENCE" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="MEDTD2" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="KMEDTD2" type="xs:string"/>
<xs:element name="METERNO" type="xs:string"/>
<xs:element name="NO_DIALS" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="MEDTD3" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="KMEDTD3" type="xs:string"/>
<xs:element name="QUANTITY" type="xs:string"/>
<xs:element name="QUANTITY_TYPE_ID" type="xs:string"/>
<xs:element name="QUANTITY_DATE" type="xs:string"/>
<xs:element name="QUANTITY_DATE_TYPE" type="xs:string"/>
<xs:element name="MEASURE_UNIT_ID" type="xs:string"/>
<xs:element name="TIMEFRAME_ID" type="xs:string"/>
<xs:element name="QUALIFICATION" type="xs:string"/>
<xs:element name="NO_DIGITS" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="F1">
<xs:complexType>
<xs:sequence>
<xs:element name="KF1" type="xs:string"/>
<xs:element name="F1" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
And here the <b>Target Structure</b> of the IDOC
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="ZUECH_0210">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="IDOC" type="ZUECH_0210.ZUECH_0210" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="EDI_DC40.ZUECH_0210.ZUECH_0210">
<xsd:sequence>
<xsd:element name="TABNAM" type="xsd:string" fixed="EDI_DC40">
<xsd:annotation>
<xsd:documentation>Table Structure Name</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MANDT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Client</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DOCNUM" minOccurs="0">
<xsd:annotation>
<xsd:documentation>IDoc Number</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="16"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DOCREL" minOccurs="0">
<xsd:annotation>
<xsd:documentation>SAP IDoc Release</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STATUS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>IDoc Status</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DIRECT">
<xsd:annotation>
<xsd:documentation>Direction</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="1">
<xsd:annotation>
<xsd:documentation>Outbound</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="2">
<xsd:annotation>
<xsd:documentation>Inbound</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OUTMOD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Output Mode</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EXPRSS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Overriding in Inbound Processing</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TEST" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Test Flag</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="IDOCTYP" type="xsd:string" fixed="ZUECH_0210">
<xsd:annotation>
<xsd:documentation>Basic Type Name</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CIMTYP" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Enhancement (Customer-Defined)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MESTYP" type="xsd:string" fixed="ZUECH_0210">
<xsd:annotation>
<xsd:documentation>Message Type</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MESCOD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Message Variant</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MESFCT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Message Function</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>EDI Standard, Flag</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STDVRS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>EDI Standard, Version, and Release</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="6"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STDMES" minOccurs="0">
<xsd:annotation>
<xsd:documentation>EDI Message Type</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="6"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SNDPOR">
<xsd:annotation>
<xsd:documentation>Sender Port (SAP System, External Subsystem)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SNDPRT">
<xsd:annotation>
<xsd:documentation>Sender Partner Type</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SNDPFC" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Sender Partner Function</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SNDPRN">
<xsd:annotation>
<xsd:documentation>Sender Partner Number</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SNDSAD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Sender Address (SADR)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="21"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SNDLAD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Logical Sender Address</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="70"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="RCVPOR">
<xsd:annotation>
<xsd:documentation>Receiver Port</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="RCVPRT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Receiver Partner Type</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="RCVPFC" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Receiver Partner Function</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="RCVPRN">
<xsd:annotation>
<xsd:documentation>Receiver Partner Number</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="RCVSAD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Receiver Address (SADR)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="21"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="RCVLAD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Logical Receiver Address</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="70"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CREDAT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Creation Date</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CRETIM" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Creation Time</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="6"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="REFINT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Interchange File (EDI Interchange)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="14"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="REFGRP" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Message Group (EDI Message Group)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="14"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="REFMES" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Message (EDI Message)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="14"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ARCKEY" minOccurs="0">
<xsd:annotation>
<xsd:documentation>External Message Archive Key</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="70"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SERIAL" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Serialization</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="SEGMENT" type="xsd:string" use="required" fixed="1"/>
</xsd:complexType>
<xsd:complexType name="ZUECH_0210._-RWENL_-U_MEDTD2">
<xsd:annotation>
<xsd:documentation>MEDTD2</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="METERNO" minOccurs="0">
<xsd:annotation>
<xsd:documentation>MeterNo</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="18"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NO_DIALS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>No_Dials</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="_-RWENL_-U_MEDTD3" type="ZUECH_0210._-RWENL_-U_MEDTD3" maxOccurs="99"/>
</xsd:sequence>
<xsd:attribute name="SEGMENT" type="xsd:string" use="required" fixed="1"/>
</xsd:complexType>
<xsd:complexType name="ZUECH_0210._-RWENL_-U_EDSN_HEADER">
<xsd:annotation>
<xsd:documentation>EDSN Header information</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="H1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Not More Closely Defined Area, Possibly Used for Patchlevels</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="H2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Character 100</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="H3" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Character field 13 digits</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="13"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="H4" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Character Field Length = 10</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="H5" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Supplier_EAN</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="13"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="H6" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Supplier_EAN</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="13"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="SEGMENT" type="xsd:string" use="required" fixed="1"/>
</xsd:complexType>
<xsd:complexType name="ZUECH_0210.ZUECH_0210">
<xsd:annotation>
<xsd:documentation>Received Metered data E</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="EDI_DC40" type="EDI_DC40.ZUECH_0210.ZUECH_0210"/>
<xsd:element name="_-RWENL_-U_EDSN_HEADER" type="ZUECH_0210._-RWENL_-U_EDSN_HEADER"/>
<xsd:element name="_-RWENL_-U_MEDTD1" type="ZUECH_0210._-RWENL_-U_MEDTD1"/>
</xsd:sequence>
<xsd:attribute name="BEGIN" type="xsd:string" use="required" fixed="1"/>
</xsd:complexType>
<xsd:complexType name="ZUECH_0210._-RWENL_-U_MEDTD3">
<xsd:annotation>
<xsd:documentation>MEDTD3</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="QUANTITY" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Quantity</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="QUANTITY_TYPE_ID" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Quantity_Type_ID</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="QUANTITY_DATE" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Quantity_Date</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="QUANTITY_DATE_TYPE" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Quantity_Date_Type</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MEASURE_UNIT_ID" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Measure_Unit_ID</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TIMEFRAME_ID" minOccurs="0">
<xsd:annotation>
<xsd:documentation>TimeFrame_ID</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="QUALIFICATION" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Qualification</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NO_DIGITS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>No_Digits</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="SEGMENT" type="xsd:string" use="required" fixed="1"/>
</xsd:complexType>
<xsd:complexType name="ZUECH_0210._-RWENL_-U_MEDTD1">
<xsd:annotation>
<xsd:documentation>MEDTD1</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="REQUEST_ID" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Request_ID</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TRANSACTION_ID" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Transaction_ID</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CONNECT_EAN" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Connect_EAN</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="18"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="REASON_ID" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Reason_ID</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PERIOD_STARTDATE" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Period Startdate</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PERIOD_ENDDATE" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Requested_MR_End_Date</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SUBMITTED_DATE" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Submitted_date</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MARKET_SEGMENT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Market_Segment</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NETOP_EAN" minOccurs="0">
<xsd:annotation>
<xsd:documentation>NetOp EAN</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="13"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="REQUEST_REFERENCE" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Request_Reference</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="_-RWENL_-U_MEDTD2" type="ZUECH_0210._-RWENL_-U_MEDTD2" maxOccurs="99"/>
</xsd:sequence>
<xsd:attribute name="SEGMENT" type="xsd:string" use="required" fixed="1"/>
</xsd:complexType>
</xsd:schema>
Similar Messages
-
Mapping problem:from E1EDK14-ORGID to PORDCR102-PUR_GROUP
Mapping problem:from E1EDK14-ORGID to PORDCR102-PUR_GROUP
E1EDK14 occurs 4 times in the source sys:
1 E1EDK14-QUALF = '014'
E1EDK14-ORGID = 'YP01' <= purchase organization
2 E1EDK14-QUALF = '009'
E1EDK14-ORGID = '001' <= purchase group
3 E1EDK14-QUALF = '013'
E1EDK14-ORGID = 'NB' <= document type
4 E1EDK14-QUALF = '011'
E1EDK14-ORGID = 'C999' <= company code
I always want to copy "E1EDK14-ORGID = '001'" to PORDCR102-PUR_GROUP.
I have a solution which works but not perfect:
E1EDK14-ORGID=>copyvalue[1]=>PORDCR102-PUR_GROUP
I want to have the perfect mapping as follow:
IF E1EDK14-QUALF = '009'.
E1EDK14-ORGID = '001' => PORDCR102-PUR_GROUP
ENDIF.
I did it in the data flow editor as follow:
/PORDCR102/IDOC/E1PORDCR1/E1BPMEPOHEADER/PUR_GROUP=
ifWithoutElse([keepss=false]stringEquals
(removeContexts(/ORDERS05/IDOC/E1EDK14/QUALF=),
const([value=009])), /ORDERS05/IDOC/E1EDK14/ORGID=)
But the result in the target sys is always 'YP0'(The first E1EDK14-ORGID)
How to solve this problem?
Thanks
ming yuHi,
Try like this.
E1EDK14-QUALF --------
Constant(009) ---------------- EqualsS ---------------
And(Boolean Function) ------ IfWithoutElse -- PORDCR102-PUR_GROUP
E1EDK14-ORGID ------- E1EDK14-ORGID ----------------
Constant(001) -------------- EqualsS ------------------
Regards,
P.Venkat -
Mapping problem on different levels. (IDOC) to SQL
I am having a mapping issue with a multi segment IDOC. It seems that it should be pretty straight forward but I am struggling. I have looked at some pretty good documentation but it still doesn't seem to help. The IDOC segments deal with text lines in SAP. The text identifier is at a higher level and the text lines are a level below the text identifier. I am writing these records to a SQL database table and the table will just contain the text identifier and then the text line. Both of these are at the same level. I need to combine the text identifier from the higher level to to each text line in the database table.
Here is my source file. It contains two different types of text identifiers (TDID)
<E1TXTH8 SEGMENT="1">
<TDID>0012</TDID>
<TDSPRAS>E</TDSPRAS>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 1 of TDID 0012</TDLINE>
</E1TXTP8>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 2 of TDID 0012</TDLINE>
</E1TXTP8>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 3 of TDID 0012</TDLINE>
</E1TXTP8>
</E1TXTH8>
<E1TXTH8 SEGMENT="1">
<TDID>Z110</TDID>
<TDSPRAS>E</TDSPRAS>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 1 of TDID Z110</TDLINE>
</E1TXTP8>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 2 of TDID Z110.</TDLINE>
</E1TXTP8>
</E1TXTH8>
I wand this to map so that I see the following results:
<InsertStatement_ShippingText>
<MDB_tblshippingtext action="INSERT">
<access>
<TDID>0012</TDID>
<TDLINE>This is line 1 of TDID 0012</TDLINE>
</access>
<access>
<TDID>0012</TDID>
<TDLINE>This is line 2 of TDID 0012</TDLINE>
</access>
<access>
<TDID>0012</TDID>
<TDLINE>This is line 3 of TDID 0012</TDLINE>
</access>
<access>
<TDID>Z110</TDID>
<TDLINE>This is line 1 of TDID Z110</TDLINE>
</access>
<access>
<TDID>Z110</TDID>
<TDLINE>This is line 2 of TDID Z110</TDLINE>
</access>
</MDB_tblshippingtext>
</InsertStatement_ShippingText>
So far I have been unsuccessful. I am mapping the access element to the lower level segment E1TXTP8. This gives me all of the text lines but the TDID is not filled in properly.
If I map the access element to the highler level E1TXTH8 then I do not get all of my text lines from the lower level. I have looked at the document "Replication of Nodes using the graphical tool mapper" but I still don't seem to understand my problem.
Any help is appreciated.
Thanks,
JimHi Jim,
there are a couple of things to look at:
1. If you always have at least one E1TXTP8 segment under each E1TXTH8 segment, you can use the function useOneAsMany. Jin Chin gave you all the pointers to look at (remember to check the context for the mapping of your element "access")
2. If you test with samples that have a E1TXTH8 segment without a segment E1TXTP8 underneath, the function useOneAsMany will give you the error you encounter. In that case you need to use one of the different mappings described in the <a href="/people/claus.wallacher/blog/2006/04/17/replication-of-nodes-using-the-graphical-mapping-tool">weblog</a> you mentioned.
3. If it still doesn't work, can you give us the sample XML that causes the error?
Regards,
Claus -
Mapping problem on different levels. (IDOC) to XML
I am having a mapping issue with a multi segment IDOC. It seems that it should be pretty straight forward but I am struggling. I have looked at some pretty good documentation but it still doesn't seem to help. The IDOC segments deal with text lines in SAP. The text identifier is at a higher level and the text lines are a level below the text identifier. I am writing these records to XML . Both of these are at the same level. I need to combine the text identifier from the higher level to to each text line in the XML.
Here is my source file. It contains two different types of text identifiers (TDID)
<E1TXTH8 SEGMENT="1">
<TDID>0012</TDID>
<TDSPRAS>E</TDSPRAS>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 1 of TDID 0012</TDLINE>
</E1TXTP8>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 2 of TDID 0012</TDLINE>
</E1TXTP8>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 3 of TDID 0012</TDLINE>
</E1TXTP8>
</E1TXTH8>
<E1TXTH8 SEGMENT="1">
<TDID>Z110</TDID>
<TDSPRAS>E</TDSPRAS>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 1 of TDID Z110</TDLINE>
</E1TXTP8>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 2 of TDID Z110.</TDLINE>
</E1TXTP8>
</E1TXTH8>
I wand this to map so that I see the following results:
<TDID>0012</TDID>
<TDLINE>This is line 1 of TDID 0012</TDLINE>
</access>
<access>
<TDID>0012</TDID>
<TDLINE>This is line 2 of TDID 0012</TDLINE>
</access>
<access>
<TDID>0012</TDID>
<TDLINE>This is line 3 of TDID 0012</TDLINE>
</access>
<access>
<TDID>Z110</TDID>
<TDLINE>This is line 1 of TDID Z110</TDLINE>
</access>
<access>
<TDID>Z110</TDID>
<TDLINE>This is line 2 of TDID Z110</TDLINE>
</access>
</MDB_tblshippingtext>
</InsertStatement_ShippingText>
So far I have been unsuccessful. I am mapping the access element to the lower level segment E1TXTP8. This gives me all of the text lines but the TDID is not filled in properly.
If I map the access element to the highler level E1TXTH8 then I do not get all of my text lines from the lower level. I have looked at the document "Replication of Nodes using the graphical tool mapper" but I still don't seem to understand my problem.
Any help is appreciated.
Thanks,Hi Neela,
I have uploaded Mapping pictures(Access node Mapping,TDID field Mapping,TDLINE Field Mapping).
http://www.flickr.com/photos/14144840@N02
In Access node Mapping You can use removeContexts node function as shown in Pic or without using removeContexts function Change Context to parent of E1TXTH8 node (How to Change Context: Right click on TDLINE in Data flow editor Context->select parent of E1TXTH8 node)
In TDID field Mapping useOneAsMany node function and change contexts of 2nd and 3rd inputs of this function to E1TXTH8 as shown in Pic.
Please let me know if you have any issues.
Thanks,
Jag -
Mapping not sufficiently defined FILE TO IDOC(HRMD_A.HRMD_A06) scenerio
Hello friends,
In message mapping part from File to IDOC. I am doing mapping of infotype 14 message type with the corresponding idoc. But when I activate it I am getting the following error:
Activation of the change list canceled Check result for Message Mapping MM_INF14_LS | urn:tcs:test: Mapping not sufficiently defined
As far as I know I have properly mapped the fields which I am picking from the file. But I am not very sure what to do woth few fields in the IDOC which appear to be red in message mapping
Kindly give me the solution.
Regards,
LokeshThanx guys...I tried changing the description of other mappings whch were already activated. And thn I tried activating I got the same error:
Activation of the change list canceled Check result for Message Mapping MM_02IT | urn:tcs:payroll: Starting compilation Source code has syntax error: java.lang.NoClassDefFoundError: com/sun/tools/javac/Main Exception in thread "main"
what possibly can go wrong? Is there any way to activate it.
Looking forward for ur reply.
Regards,
Lokesh -
How can I map SSH from an outside network range to an internal host (ASA 5505)
Cisco Adaptive Security Appliance Software Version 7.2(4)
Device Manager Version 5.2(4)
- External network range that needs SSH access: 8.8.8.0/24
- Outside interface: 10.1.10.2 (NAT'd from 7.7.7.7)
- Inside Network: 192.168.100.0/24
- Inside host to redirect external SSH to: 192.168.100.98
Hi All,
I have a Cisco ASA 5505 (version above) and I have someone that needs to SSH into a box behind the ASA. I'm having a few issues trying to configure this access-list and NAT. I've tried many combinations and clearly my IOS is not as good as I thought.
Can anyone help with this? What commands should I enter to accomplish mapping SSH from an outside network range to an internal host?
Many thanks,
TarranThis may or may not work depending on how your modem handles the natting. On your firewall try this -
static (inside,outside) tcp interface 22 192.168.100.98 22
then add this to your acl on the outside interface of your ASA -
access-list outside_in permit tcp 8.8.8.0 255.255.255.0 host 10.1.10.2 eq 22
if you don't have an acl applied then add this extra step -
access-group outside_in in interface outside
Jon -
How do I import gradient map settings from one computer to another?
Quick Question,
How do I import my gradient map settings from CS3 on my old I mac into my new Mac that uses CS6? Is there a folder somewhere that I can just copy and paste?
Thanks,
Mike1
Start Adobe Photoshop CS3 and open an image from your files to which you want to apply a gradient map.
2
Select the "Image" menu, point to "Adjustments" and click on "Gradient Map" to open the "Gradient Map" dialog box.
3
Choose the gradient you want to use for the gradient map by clicking on the "Gradient Picker" drop-down box. Click on the gradient preset you want to use for the gradient mapping. You will see that in the background the gradient has been applied to your open image.
4
Click on the gradient fill that you have chosen to open the "Gradient Editor" if you want to edit the gradient preset. Make any changes in this dialog box and click the "OK" button to close the box and return to your gradient map.
5
Set any final options to apply to your gradient map. Check "Dither" under "Gradient Options" to add noise to smooth the bands of your gradient and/or "Reverse" to switch the direction of the gradient map.
6
Use the "OK" button to close the "Gradient Map" dialog box and return your image to which the gradient map is now applied.
Is that what you were asking?
Hope it helps. -
Mapping - Checking 3 fields to change IDOC
Hello,
I am triggering a new IDOC whenever the source field1 changes as below.
field1 -> removecontext -> splitbyvalue [value change] -> collapsecontext -> IDOC
If i need to check for 2 more fields field2 & field3 and if any one of these 3 field changes trigger the creation of new IDOC field?
How do I map the other two fields to IDOC?
Thanks,
HariHi,
Since we can not map the target IDOC when any of the field changes using nodefunctions , you can write UDF and check the same i.e if field1 changes or field2 changes or field3 changes then trigger new IDoc. This is one of the options that you can try...please try it once.
Regards
Priyanka -
I want to create an HTML table of img maps dynamically from DB retrieves...
Hi,
How do I build dynamic HTML code in a function and then populate a HTML region to render it.. (did I say that right?)
I want to create an HTML table of img maps dynamically from DB retrieves...
Thank you, BillVikas and Andy,
Using Andy's code I'll go further...
I want to create a function that returns HTML code that has been built dynamically.
create or replace function "GET_CH_TABLE"
return VARCHAR2
is
HTML_STRING VARCHAR2(2000); -- Create a string variable
BEGIN
HTML_STRING:= '<table align="center">' ||chr(10)||
' <tr>' ||chr(10)||
' <td> TEST ' ||chr(10)||
' /td>' ||chr(10)||
' /tr>' ||chr(10)||
' tr>' ||chr(10)||
' td>' ||chr(10)||
' a href=https:// ............etc. etc.. building the <TABLE> and <TD> cells having whatever I want... example.. changing the name of an image dependant on something else..
return HTML_STRING; -- output the string to the region
--also tried htp.p(HTML_STRING);
END;
=====================================
Building the dynamic HTML is not my problem. It is how to get it into a region and to be read as HTML from a function call...
I'd like the source of the region to be the returned HTML from a function call to GET_CH_TABLE();
but it gives error:
ORA-06550: line 1, column 7: PLS-00221: 'GET_CH_TABLE' is not a procedure or is undefined
ORA-06550: line 1, column 7: PL/SQL: Statement ignored
Debug:
1: begin
2: GET_CH_TABLE();
3: end;
I -
Mapping Styles from Word 2010 to RoboHelp HTML 10
Hello all,
I have created customized styles for myself and my team to use for authoring content, which I then import to RoboHelp, as I am the only individual who understands RoboHelp and HTML/CSS. I created a corresponding CSS style sheet in RoboHelp to correspond with the names of the Word styles. When I go to import the files in RoboHelp, I am running in to an issue with paragraph tags and heading tags.
When I import a file from a Word document, I have not found a way to map a <p> tag that is parsed from a Word document to an <h> tag, as heading tags do not appear as a selectable item in the Conversion Settings window when importing Word files. I would be able to keep the formatting if I left the headings as <p> tags; however, it is my understanding that RoboHelp 10 search relies heavily on the heading tags for weighting search results. I have about 400 topics, and search is used heavily by those using my documentation. I would prefer to keep the <h> tags in place in the RoboHelp files and retain the search functionality, if at all possible, while finding an easier import option from Word files.
At this point, I have to manually change the HTML for each <p> tag to match the correct heading style. While Find and Replace works well for this, I would prefer to have a seamless import from Word (which bloats an HTML file horrendously, I know) by mapping from one style to the next. Has anyone found a way to map a <p> tag to an <h> tag so that the search functionality does not suffer? Or am I just approaching this the wrong way?You are correct in your assumption that I am referring to paragraph styles when speaking of <p> tags. The paragraph styles come over as <p> tags, and I was just thinking of my style sheet. Sorry for the confusion.
Speaking of my workflow, I'm attempting to map the styles for one topic at a time when importing a new Word file. I set up a test project to test out my style sheet, as I am upgrading from RoboHelp 7 right now. .I need to get one document to map correctly to save the settings for future imports.
From the Import window, I click the Edit... button in the Word Document section. After RoboHelp scans the Word file, a list of all the styles from the Word document display. When I attempt to select from the available styles I want to map to from my RoboHelp style sheet, I don't have the option to select the heading styles I created in my RoboHelp CSS file. Does this provide you enough information to give you context on how I am attempting to map the styles?
I found this article that leads me to belive that RoboHelp does not support mapping to a customized heading style from a CSS file. I realize that this is around the printed output, but it states the following:
If custom heading styles aren’t named in the format Heading <number>, they are not treated as headings.
If it doesn't work going from HTML to printed output, I'm guessing that there is not support going from Word to HTML. Am I wrong in this assumption? Do I just need to alter my style sheet to only use the standard <h> tags to fix this issue? -
Dequeuing a Map message from AQ using Java/JMS
I have a queue in Oracle AQ, created from a queue table with queue_payload_type of SYS.AQ$_JMS_MAP_MESSAGE. I can successfully enqueue a Map message using PL/SQL, but when I try to read a message from the queue using the JMS API (with the Oracle AQ JMS provider JARs) in a standalone Java program, the message is not successfully read. However, the RETRY_COUNT in the queue table is incremented each time I try to read from the queue. I do not receive any error messages on the client side.
If I change the queue_payload_type of the queue table to SYS.AQ$_JMS_TEXT_MESSAGE instead and enqueue a text message using PL/SQL, I can read the text message successfully in the standalone Java program using JMS. The message is removed from the queue and everything works fine.
Most Oracle AQ/JMS examples I've found on the web involve text messages. Has anyone been able to read a Map message from an Oracle AQ queue using JMS, or is there a known issue with Map messages?
I'm running Oracle 10g Standard Edition version 10.2.0.1.0 on Windows XP.
Thanks for your help,
MartyWhile you are awaiting an answer you might want to consider applying the 10.2.0.4 patch. Your version is several years old and patches are free.
-
No mapping exists from object type Telerik.Web.UI.RadMaskedTextBox to a known
hi for all i got this problem when i try to update record in a database actually it's first
time happining with me
No mapping exists from object type Telerik.Web.UI.RadMaskedTextBox to a known
managed provider native type
and this is my code
SqlCommand cmd = new SqlCommand("update RealEstate set DestinationEntity=@speechDirect,FULLName=@name,Individual_Iqama_NR=@egamhNo,Individual_Passport_NR_ID=@passport,Individual_Gender=@six,Individual_Sociall_Status=@martialstate,Individual_Passport_Issue_Date=@passportdate,Individual_Nationality_ID=@nationality,IqamaIssued_From=@egamhsource,Total_Staying_Time_KSA=@stayduration,Individual_Work_Address=@workdisc,Possess_Type=@omntype,Apartment_No=@estateno,Apartment_Floor_No=@storyno,Possess_City_ID=@city,QuarterID=@area,Deed_No=@InstrumentNo,Deed_Date_HijriAfter=@Instrumentdate,Deed_Issue_City_ID=@Instrumentsource,Request_Status=@orderstate,Real_Estate_Area=@estatespace,[notes]=@notes,Incomming_No=@waredno,Incomming_Date_HijriAfter=@wareddate,Qaied_No=@ghaidno,Qaied_Date_HijriAfter=@ghaiddate,ExportNumber=@jihtsdor, ExportDateHijriAfter=@job where Possess_ID=@id", _con);
cmd.CommandType = CommandType.Text;
_con.Open();
cmd.Parameters.AddWithValue("@id", int.Parse(Request.QueryString["Serial"].ToString()));
cmd.Parameters.AddWithValue("@speechDirect", RadComboBox1.SelectedValue);
cmd.Parameters.AddWithValue("@name", txtname.Text);
cmd.Parameters.AddWithValue("@egamhNo",txtegamhno.Text);
cmd.Parameters.AddWithValue("@passport", txtpassportno.Text);
cmd.Parameters.AddWithValue("@six",RDSix.SelectedValue);
cmd.Parameters.AddWithValue("@martialstate", Rdstatus.SelectedValue);
cmd.Parameters.AddWithValue("@passportdate", DateTime.Now);
cmd.Parameters.AddWithValue("@nationality", RdNationality.SelectedValue);
cmd.Parameters.AddWithValue("@egamhsource", txtegamhsou.Text);
cmd.Parameters.AddWithValue("@stayduration", txtstayduration.Text);
cmd.Parameters.AddWithValue("@workdisc", txtjobdirec.Text);
cmd.Parameters.AddWithValue("@omntype", RdownType.SelectedValue);
cmd.Parameters.AddWithValue("@estateno",txtflatNo.Text);
cmd.Parameters.AddWithValue("@storyno", txtstoryNo.Text);
cmd.Parameters.AddWithValue("@city", RDcity.SelectedValue);
cmd.Parameters.AddWithValue("@area", RadComboBox2.SelectedValue);
cmd.Parameters.AddWithValue("@InstrumentNo",txtskno.Text);
cmd.Parameters.AddWithValue("@Instrumentdate", txtskdate.Text);
cmd.Parameters.AddWithValue("@Instrumentsource", Rdsksource.SelectedValue);
cmd.Parameters.AddWithValue("@orderstate", Rdordercase.SelectedValue);
cmd.Parameters.AddWithValue("@estatespace",txtspace.Text);
cmd.Parameters.AddWithValue("@notes", txtcomments.Text);
cmd.Parameters.AddWithValue("@waredno",txtwaredno.Text);
cmd.Parameters.AddWithValue("@wareddate", txtkitabno.Text);
cmd.Parameters.AddWithValue("@ghaidno", txtgaidno.Text);
cmd.Parameters.AddWithValue("@ghaiddate",txtghaiddate.Text);
cmd.Parameters.AddWithValue("@jihtsdor",Rdsksource.SelectedValue);
cmd.Parameters.AddWithValue("@job", txtsaderdate);
int x =cmd.ExecuteNonQuery();
any one could provide suggestion to solve this problem
thanksHello,
I would like suggest you posting it to:
http://www.telerik.com/support
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
How to... fetch SeeBurger Mapping Variables from a BPM
Hi,
I am currently having a problem in fetching some values on the Seeburger Mapping Variables from an BPM. What I currently do is the normal way of fetching the value using an UDF in my message mapping: below is the sample code that I did on my function:
import seeburger.functions.permstore.impl.;com.seeburger.functions.permstore.;
try {
VariableBeanServlet vbs;
vbs = (VariableBeanServlet)VariableFactory.getVariableInstance(VariableFactory.PROPERTY_CLASSNAME_DEFAULT);
return vbs.getStringVariable(a);
}catch(PermstoreException e){
return "";
did i missed something on my code?
best regards,
mikeThe values are written on the Seeburger --> MappingVariables under Variables section. These has been predefined by me beforehand. I've checked the code without passing thru the BPM and it works but when it was used with the BPM the values doesn't turn up..
best regards,
Mike -
Value Mapping replication from SAP
Hi
I have gone thru the Blogs and threads related to value mapping replication from SAP.
Inmy observervation http://sap.com/xi/XI/System of SAP BASIS 7.00
still I have some doubts...
1)what is the differnce between ValueMappingReplication(Asynchronous) and ValueMappingReplicationSynchronous .
when we will use them.
2) Message type ValueMappingReplication contains Operation ,GroupId,Context,scheme,agency.
what is the meaning of Operation??
what is the use of group ID??
is this necessary to maintain all these values in Ztable and also source and target values ?? and use them in Abap aproxy logic??
3) is there any Message Mapping Needed.?? and Interface Mapping Needed to implement value Mapping replication??
but in this blog
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1301i [original link is broken] [original link is broken] [original link is broken] didnt find any interface mapping .
4)what is the Sender Adapter type ??
5) if I did replication from SAP..can I see the details in ID
please guide me
regards
munnahi
1)what is the differnce between ValueMappingReplication(Asynchronous) and ValueMappingReplicationSynchronous .
In sync you will get the value mapping replication status back and in async you won't. In sync based on the response u can update again in case of any failure. If data size is large use async.
2) Message type ValueMappingReplication contains Operation ,GroupId,Context,scheme,agency.
what is the meaning of Operation??
The operation that you are going to perform. Below is the operations list and the contents to be set in the message for the same
Insert = all fields must be set;
Delete =all fields must be set;
DeleteGroup = fields GroupID and context must be set;
DeleteContext = field Context must be set;
DeleteContextGeneric = Context contains the starting part for the context to be deleted
what is the use of group ID??
Displays the different representations of an object.
A value mapping group is identified uniquely by a GUID.
You can also assign a name to a value mapping group.
is this necessary to maintain all these values in Ztable and also source and target values ?? and use them in Abap aproxy logic??
no. system creates the value mapping table. you can take it frm there. no need of any ztables.
3) is there any Message Mapping Needed.?? and Interface Mapping Needed to implement value Mapping replication??
You will be sending the value mapping data from a sender system. If it can sent in the same format not required, otherwise you will have to.
4)what is the Sender Adapter type ??
Any adapter...depends on the sender system.
5) if I did replication from SAP..can I see the details in ID
You can see it in Cache monitoring in RWB.
for more details refer
http://help.sap.com/saphelp_nw70/helpdata/EN/13/ba20dd7beb14438bc7b04b5b6ca300/content.htm
rgds
Arun -
Value mapping access from XI module adapter
Hi,
is it possible to access a value mapping from an XI module adapter?
Thanks
Yannhi
1)what is the differnce between ValueMappingReplication(Asynchronous) and ValueMappingReplicationSynchronous .
In sync you will get the value mapping replication status back and in async you won't. In sync based on the response u can update again in case of any failure. If data size is large use async.
2) Message type ValueMappingReplication contains Operation ,GroupId,Context,scheme,agency.
what is the meaning of Operation??
The operation that you are going to perform. Below is the operations list and the contents to be set in the message for the same
Insert = all fields must be set;
Delete =all fields must be set;
DeleteGroup = fields GroupID and context must be set;
DeleteContext = field Context must be set;
DeleteContextGeneric = Context contains the starting part for the context to be deleted
what is the use of group ID??
Displays the different representations of an object.
A value mapping group is identified uniquely by a GUID.
You can also assign a name to a value mapping group.
is this necessary to maintain all these values in Ztable and also source and target values ?? and use them in Abap aproxy logic??
no. system creates the value mapping table. you can take it frm there. no need of any ztables.
3) is there any Message Mapping Needed.?? and Interface Mapping Needed to implement value Mapping replication??
You will be sending the value mapping data from a sender system. If it can sent in the same format not required, otherwise you will have to.
4)what is the Sender Adapter type ??
Any adapter...depends on the sender system.
5) if I did replication from SAP..can I see the details in ID
You can see it in Cache monitoring in RWB.
for more details refer
http://help.sap.com/saphelp_nw70/helpdata/EN/13/ba20dd7beb14438bc7b04b5b6ca300/content.htm
rgds
Arun
Maybe you are looking for
-
Recently took my iPad to Apple store, had a bug from IOS7.4, so they re did it, lost all my pics in iCloud, I even paid extra $ for more storage,,they then tried to restore it, but still no pics. All they could say is I'm sorry but this is what happe
-
Indesign CS6 saves my PDF in Negative
Ive been having this issue for a few weeks now and Ive hunted online and found nothing. I use Indesign CS6 to create ads. The Images in these ads are .psd saved as CMYK or Grey Scale. I save them as PDF's, and in Preview randomly the PDF preview wont
-
Windows server 2003 connect to SQl server 2000 problem
my problem D:\Myjava>java connect java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establis hing socket. at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source at com.microsoft.jdbc.base.BaseExceptions.getExce
-
How to present a link to job (I want to bypass job output cycle wizard)
Dear firends How to present a link to job (I want to bypass job output cycle wizard to open MyExample.BQY) http://MyServer:45000/workspace/browse/get/KursHYP2008/siyavus/MyExample?jobOutput=true&user=admin&pass=password this link shows wizard to open
-
Is it possible to lock the Asset after capitalization - GR Posting done
Hi, The Fund Reservation configuration containing with Fund, Fund Centre & Commitment Item is linked with Asset at the time of creation of PR. If we change the asset in PR, the new Commitment Item is showing after GR posting. At the same time old com