jco.parameterlist.html

SAP ERP的二次开发

</DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>name</CODE> - Field name for identifying this data field<DD><CODE>type</CODE> - Data field type<DD><CODE>length</CODE> - Data field internal length in bytes<DD><CODE>value</CODE> - Data field value<DT><B>Throws:</B><DD><CODE><A HREF="../../../../com/sap/mw/jco/JCO.ConversionException.html">JCO.ConversionException</A></CODE> - thrown if the value could not be converted to its internal representation</DL>
</DD>
</DL>
<HR>

<A NAME="appendValue(java.lang.String, int, int, int)"><!-- --></A><H3>
appendValue</H3>
<PRE>
public void <B>appendValue</B>(java.lang.String&nbsp;name,
                        int&nbsp;type,
                        int&nbsp;length,
                        int&nbsp;value)</PRE>
<DL>
<DD><B>Deprecated.</B>&nbsp;<I>Internal use only. This method will be removed in the next release.</I>
<P>
<DD>Adds a value to the parameter list

  The preffered way to create parameter list should be
  to use <tt>JCO.Repository</tt>. In this case the meta data fetched by
  repository is correct independent on having unicode and non unicode backend.<br>
  In cases where this way is not possible create first a
  <tt>MetaData</tt> object, fill it using suitable <tt>addInfo</tt> APIs and
  then create a <tt>ParameterList</tt>.<br><DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>name</CODE> - Field name for identifying this data field<DD><CODE>type</CODE> - Data field type<DD><CODE>length</CODE> - Data field internal length in bytes<DD><CODE>value</CODE> - Data field value<DT><B>Throws:</B><DD><CODE><A HREF="../../../../com/sap/mw/jco/JCO.ConversionException.html">JCO.ConversionException</A></CODE> - thrown if the value could not be converted to its internal representation</DL>
</DD>
</DL>
<HR>

<A NAME="appendValue(java.lang.String, int, int, double)"><!-- --></A><H3>
appendValue</H3>
<PRE>
public void <B>appendValue</B>(java.lang.String&nbsp;name,
                        int&nbsp;type,
                        int&nbsp;length,
                        double&nbsp;value)</PRE>
<DL>
<DD><B>Deprecated.</B>&nbsp;<I>Internal use only. This method will be removed in the next release.</I>
<P>
<DD>Adds a value to the parameter list

  The preffered way to create parameter list should be
  to use <tt>JCO.Repository</tt>. In this case the meta data fetched by
  repository is correct independent on having unicode and non unicode backend.<br>
  In cases where this way is not possible create first a
  <tt>MetaData</tt> object, fill it using suitable <tt>addInfo</tt> APIs and
  then create a <tt>ParameterList</tt>.<br><DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>name</CODE> - Field name for identifying this data field<DD><CODE>type</CODE> - Data field type<DD><CODE>length</CODE> - Data field internal length in bytes<DD><CODE>value</CODE> - Data field value<DT><B>Throws:</B><DD><CODE><A HREF="../../../../com/sap/mw/jco/JCO.ConversionException.html">JCO.ConversionException</A></CODE> - thrown if the value could not be converted to its internal representation</DL>
</DD>
</DL>
<HR>

<A NAME="appendValue(java.lang.String, int, int, byte[])"><!-- --></A><H3>
appendValue</H3>
<PRE>
public void <B>appendValue</B>(java.lang.String&nbsp;name,
                        int&nbsp;type,
                        int&nbsp;length,
                        byte[]&nbsp;value)</PRE>
<DL>
<DD><B>Deprecated.</B>&nbsp;<I>Internal use only. This method will be removed in the next release.</I>
<P>
<DD>Adds a ByteArray value to the parameter list

  The preffered way to create parameter list should be
  to use <tt>JCO.Repository</tt>. In this case the meta data fetched by
  repository is correct independent on having unicode and non unicode backend.<br>
  In cases where this way is not possible create first a
  <tt>MetaData</tt> object, fill it using suitable <tt>addInfo</tt> APIs and
  then create a <tt>ParameterList</tt>.<br><DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>name</CODE> - Field name for identifying this data field<DD><CODE>type</CODE> - Data field type<DD><CODE>length</CODE> - Data field internal length in bytes<DD><CODE>value</CODE> - Data field value<DT><B>Throws:</B><DD><CODE><A HREF="../../../../com/sap/mw/jco/JCO.ConversionException.html">JCO.ConversionException</A></CODE> - thrown if the value could not be converted to its internal representation</DL>
</DD>
</DL>
<HR>

<A NAME="appendValue(java.lang.String, int, int, java.lang.Object)"><!-- --></A><H3>
appendValue</H3>
<PRE>
public void <B>appendValue</B>(java.lang.String&nbsp;name,
                        int&nbsp;type,
                        int&nbsp;length,
                        java.lang.Object&nbsp;value)</PRE>
<DL>
<DD><B>Deprecated.</B>&nbsp;<I>Internal use only. This method will be removed in the next release.</I>
<P>
<DD>Adds an Object value to the parameter list

  <em>Note:</em> This API cannot be used for communication with
  unicode enabled backend system.

  The preffered way to create parameter list should be
  to use <tt>JCO.Repository</tt>. In this case the meta data fetched by
  repository is correct independent on having unicode and non unicode backend.<br>
  In cases where this way is not possible create first a
  <tt>MetaData</tt> object, fill it using suitable <tt>addInfo</tt> APIs and
  then create a <tt>ParameterList</tt>.<br><DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>name</CODE> - Field name for identifying this data field<DD><CODE>type</CODE> - Data field type<DD><CODE>length</CODE> - Data field internal length in bytes<DD><CODE>value</CODE> - Data field value<DT><B>Throws:</B><DD><CODE><A HREF="../../../../com/sap/mw/jco/JCO.ConversionException.html">JCO.ConversionException</A></CODE> - thrown if the value could not be converted to its internal representation</DL>
</DD>
</DL>
<HR>

<A NAME="appendValue(java.lang.String, com.sap.mw.jco.JCO.Table)"><!-- --></A><H3>
appendValue</H3>
<PRE>
public void <B>appendValue</B>(java.lang.String&nbsp;name,
                        <A HREF="../../../../com/sap/mw/jco/JCO.Table.html">JCO.Table</A>&nbsp;value)</PRE>
<DL>
<DD><B>Deprecated.</B>&nbsp;<I>Internal use only. This method will be removed in the next release.</I>
<P>
<DD>Adds a Table value to the parameter list

  <em>Note:</em> This API cannot be used for communication with
  unicode enabled backend system.

  The preffered way to create parameter list should be
  to use <tt>JCO.Repository</tt>. In this case the meta data fetched by
  repository is correct independent on having unicode and non unicode backend.<br>
  In cases where this way is not possible create first a
  <tt>MetaData</tt> object, fill it using suitable <tt>addInfo</tt> APIs and
  then create a <tt>ParameterList</tt>.<br><DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>name</CODE> - Field name for identifying this data field<DD><CODE>value</CODE> - Data field value<DT><B>Throws:</B><DD><CODE><A HREF="../../../../com/sap/mw/jco/JCO.ConversionException.html">JCO.ConversionException</A></CODE> - thrown if the value could not be converted to its internal representation</DL>
</DD>
</DL>
<HR>

<A NAME="appendValue(java.lang.String, com.sap.mw.jco.JCO.Structure)"><!-- --></A><H3>
appendValue</H3>
<PRE>
public void <B>appendValue</B>(java.lang.String&nbsp;name,
                        <A HREF="../../../../com/sap/mw/jco/JCO.Structure.html">JCO.Structure</A>&nbsp;value)</PRE>
<DL>
<DD><B>Deprecated.</B>&nbsp;<I>Internal use only. This method will be removed in the next release.</I>
<P>
<DD>Adds a structure value to the parameter list

  <em>Note:</em> This API cannot be used for communication with
  unicode enabled backend system.

  The preffered way to create parameter list should be
  to use <tt>JCO.Repository</tt>. In this case the meta data fetched by
  repository is correct independent on having unicode and non unicode backend.<br>
  In cases where this way is not possible create first a
  <tt>MetaData</tt> object, fill it using suitable <tt>addInfo</tt> APIs and
  then create a <tt>ParameterList</tt>.<br><DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>name</CODE> - Field name for identifying this data field<DD><CODE>value</CODE> - Data field value<DT><B>Throws:</B><DD><CODE><A HREF="../../../../com/sap/mw/jco/JCO.ConversionException.html">JCO.ConversionException</A></CODE> - thrown if the value could not be converted to its internal representation</DL>
</DD>
</DL>
<HR>

<A NAME="appendValue(java.lang.String, int, int, int, java.lang.String)"><!-- --></A><H3>
appendValue</H3>
<PRE>
public void <B>appendValue</B>(java.lang.String&nbsp;name,
                        int&nbsp;type,
                        int&nbsp;length,
                        int&nbsp;decimals,
                        java.lang.String&nbsp;value)</PRE>
<DL>
<DD><B>Deprecated.</B>&nbsp;<I>Internal use only. This method will be removed in the next release.</I>
<P>
<DD>Adds a string value to the parameter list

  <em>Note:</em> This API cannot be used for communication with
  unicode enabled backend system. Please create first a
  <tt>MetaData</tt> object and then a <tt>ParameterList</tt>.<br>
  The preffered way to create parameter list should be
  to use <tt>JCO.Repository</tt>. In this case the meta data fetched by
  repository is correct independent on having unicode and non unicode backend.<DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>name</CODE> - Field name for identifying this data field<DD><CODE>type</CODE> - Data field type<DD><CODE>length</CODE> - Data field internal length in bytes<DD><CODE>decimals</CODE> - Data field number of decimals (only necessary for the data types JCO.TYPE_BCD and JCO.TYPE_FLOAT)<DD><CODE>value</CODE> - Data field value<DT><B>Throws:</B><DD><CODE><A HREF="../../../../com/sap/mw/jco/JCO.ConversionException.html">JCO.ConversionException</A></CODE> - thrown if the value could not be converted to its internal representation</DL>
</DD>
</DL>
<HR>

<A NAME="appendValue(java.lang.String, int, int, int, int)"><!-- --></A><H3>