jco.metadata.html

SAP ERP的二次开发

<A NAME="getNumFields()"><!-- --></A><H3>
getNumFields</H3>
<PRE>
public int <B>getNumFields</B>()</PRE>
<DL>
<DD>Returns the number of fields.
  This is just a convenience function and returns
  the same value as <tt>getFieldCount()</tt>.<DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Returns:</B><DD>the number of entries in the record.</DL>
</DD>
</DL>
<HR>

<A NAME="getCapacity()"><!-- --></A><H3>
getCapacity</H3>
<PRE>
public int <B>getCapacity</B>()</PRE>
<DL>
<DD>Returns the capacity of the internal buffers<DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Returns:</B><DD>the current capacity of the internal buffers</DL>
</DD>
</DL>
<HR>

<A NAME="getMetaData()"><!-- --></A><H3>
getMetaData</H3>
<PRE>
public <A HREF="../../../../com/sap/mw/jco/IMetaData.html">IMetaData</A> <B>getMetaData</B>()</PRE>
<DL>
<DD>Returns the copy of MetaData object<DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Returns:</B><DD>the meta data object</DL>
</DD>
</DL>
<HR>

<A NAME="addInfo(java.lang.String, int, int)"><!-- --></A><H3>
addInfo</H3>
<PRE>
public void <B>addInfo</B>(java.lang.String&nbsp;name,
                    int&nbsp;type,
                    int&nbsp;length)</PRE>
<DL>
<DD>Adds a new field descriptor to the meta data object.<br>

 <em>Note:</em> if the backend is an unicode enabled system
 use <br>
 <tt>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags, Object tab_meta, IExtendedFieldMetaData extended)</tt><br>
 Otherwise the parameters based on character data types
 cannot be interpreted correctly.
 <em>Note:</em> The preffered way to create meta data 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<DT><B>See Also: </B><DD><A HREF="../../../../com/sap/mw/jco/JCO.MetaData.html#addInfo(java.lang.String, int, int, int, int, int, java.lang.String, java.lang.String, int, java.lang.Object, com.sap.mw.jco.IExtendedFieldMetaData)"><CODE>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags,Object tab_meta, IExtendedFieldMetaData extended)</CODE></A>, 
<A HREF="../../../../com/sap/mw/jco/JCO.Repository.html"><CODE>JCO.Repository</CODE></A></DL>
</DD>
</DL>
<HR>

<A NAME="addInfo(java.lang.String, int, int, int)"><!-- --></A><H3>
addInfo</H3>
<PRE>
public void <B>addInfo</B>(java.lang.String&nbsp;name,
                    int&nbsp;type,
                    int&nbsp;length,
                    int&nbsp;offset)</PRE>
<DL>
<DD>Adds a new field descriptor to the meta data object.<br>

 <em>Note:</em> if the backend is an unicode enabled system
 use <br>
 <tt>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags, Object tab_meta, IExtendedFieldMetaData extended)</tt><br>
 Otherwise the parameters based on character data types
 cannot be interpreted correctly.
 <em>Note:</em> The preffered way to create meta data 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>offset</CODE> - Data field offset in the internal JCO data buffer<DT><B>See Also: </B><DD><A HREF="../../../../com/sap/mw/jco/JCO.MetaData.html#addInfo(java.lang.String, int, int, int, int, int, java.lang.String, java.lang.String, int, java.lang.Object, com.sap.mw.jco.IExtendedFieldMetaData)"><CODE>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags,Object tab_meta, IExtendedFieldMetaData extended)</CODE></A>, 
<A HREF="../../../../com/sap/mw/jco/JCO.Repository.html"><CODE>JCO.Repository</CODE></A></DL>
</DD>
</DL>
<HR>

<A NAME="addInfo(java.lang.String, int, int, int, int)"><!-- --></A><H3>
addInfo</H3>
<PRE>
public void <B>addInfo</B>(java.lang.String&nbsp;name,
                    int&nbsp;type,
                    int&nbsp;length,
                    int&nbsp;offset,
                    int&nbsp;decimals)</PRE>
<DL>
<DD>Adds a new field descriptor to the meta data object.<br>

 <em>Note:</em> if the backend is an unicode enabled system
 use <br>
 <tt>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags, Object tab_meta, IExtendedFieldMetaData extended)</tt><br>
 Otherwise the parameters based on character data types
 cannot be interpreted correctly.
 <em>Note:</em> The preffered way to create meta data 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>offset</CODE> - Data field offset in the internal JCO data buffer<DD><CODE>decimals</CODE> - Data field number of decimals (only necessary for the data types JCO.TYPE_BCD and JCO.TYPE_FLOAT)<DT><B>See Also: </B><DD><A HREF="../../../../com/sap/mw/jco/JCO.MetaData.html#addInfo(java.lang.String, int, int, int, int, int, java.lang.String, java.lang.String, int, java.lang.Object, com.sap.mw.jco.IExtendedFieldMetaData)"><CODE>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags,Object tab_meta, IExtendedFieldMetaData extended)</CODE></A>, 
<A HREF="../../../../com/sap/mw/jco/JCO.Repository.html"><CODE>JCO.Repository</CODE></A></DL>
</DD>
</DL>
<HR>

<A NAME="addInfo(java.lang.String, int, int, int, int, int, java.lang.Object)"><!-- --></A><H3>
addInfo</H3>
<PRE>
public void <B>addInfo</B>(java.lang.String&nbsp;name,
                    int&nbsp;type,
                    int&nbsp;length,
                    int&nbsp;offset,
                    int&nbsp;decimals,
                    int&nbsp;flags,
                    java.lang.Object&nbsp;tab_meta)</PRE>
<DL>
<DD>Adds a new field descriptor to the meta data object.<br>

 <em>Note:</em> if the backend is an unicode enabled system
 use <br>
 <tt>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags, Object tab_meta, IExtendedFieldMetaData extended)</tt><br>
 Otherwise the parameters based on character data types
 cannot be interpreted correctly.
 <em>Note:</em> The preffered way to create meta data 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>
<DT><B>Specified by: </B><DD><CODE><A HREF="../../../../com/sap/mw/jco/IMetaData.html#addInfo(java.lang.String, int, int, int, int, int, java.lang.Object)">addInfo</A></CODE> in interface <CODE><A HREF="../../../../com/sap/mw/jco/IMetaData.html">IMetaData</A></CODE></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>offset</CODE> - Data field offset in the internal JCO data buffer<DD><CODE>decimals</CODE> - Data field number of decimals (only necessary for the data types JCO.TYPE_BCD and JCO.TYPE_FLOAT)<DD><CODE>flags</CODE> - Bit-vector for additional attributes of the field. The vector can be ORed together from<BR>
 <table border=1>
 <tr><th>Flag                </th><th>Description                     </th></tr>
 <tr><td>IMPORT_PARAMETER    </td><td>The field is an import parameter</td></tr>
 <tr><td>EXPORT_PARAMETER    </td><td>The field is an export parameter</td></tr>
 <tr><td>OPTIONAL_PARAMETER  </td><td>The field is optional parameter </td></tr>
 <tr><td>INACTIVATE_PARAMETER</td><td>Only used for table parameter,<BR>
                                      indicating that the content of the table will not be sent to the server</td></tr>
 </table><DD><CODE>tab_meta</CODE> - Meta-data if the field is a complex field, i.e. structure or table, <tt>null</tt> otherwise
        If this field is a structure or table object only the meta data of those objects will we copied
        not reference to the objects ! Use <tt>setValue(...)</tt> to actually set the container object.<DT><B>See Also: </B><DD><A HREF="../../../../com/sap/mw/jco/JCO.MetaData.html#addInfo(java.lang.String, int, int, int, int, int, java.lang.String, java.lang.String, int, java.lang.Object, com.sap.mw.jco.IExtendedFieldMetaData)"><CODE>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags,Object tab_meta, IExtendedFieldMetaData extended)</CODE></A>, 
<A HREF="../../../../com/sap/mw/jco/JCO.Repository.html"><CODE>JCO.Repository</CODE></A></DL>
</DD>
</DL>
<HR>

<A NAME="addInfo(java.lang.String, int, int, int, int, java.lang.String, java.lang.String, int, java.lang.Object, com.sap.mw.jco.IExtendedFieldMetaData)"><!-- --></A><H3>
addInfo</H3>
<PRE>
public void <B>addInfo</B>(java.lang.String&nbsp;name,
                    int&nbsp;type,
                    int&nbsp;length,
                    int&nbsp;offset,
                    int&nbsp;decimals,
                    java.lang.String&nbsp;sdefault,
                    java.lang.String&nbsp;description,
                    int&nbsp;flags,
                    java.lang.Object&nbsp;tab_meta,
                    com.sap.mw.jco.IExtendedFieldMetaData&nbsp;extended)</PRE>
<DL>
<DD>Adds a new field descriptor to the meta data object.<br>

 <em>Note:</em> if the backend is an unicode enabled system
 use <br>
 <tt>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags, Object tab_meta, IExtendedFieldMetaData extended)</tt><br>
 Otherwise the parameters based on character data types
 cannot be interpreted correctly.
 <em>Note:</em> The preffered way to create meta data 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>
<DT><B>Specified by: </B><DD><CODE><A HREF="../../../../com/sap/mw/jco/IMetaData.html#addInfo(java.lang.String, int, int, int, int, java.lang.String, java.lang.String, int, java.lang.Object, com.sap.mw.jco.IExtendedFieldMetaData)">addInfo</A></CODE> in interface <CODE><A HREF="../../../../com/sap/mw/jco/IMetaData.html">IMetaData</A></CODE></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>offset</CODE> - Data field offset in the internal JCO data buffer<DD><CODE>decimals</CODE> - Data field number of decimals (only necessary for the data types JCO.TYPE_BCD and JCO.TYPE_FLOAT)<DD><CODE>sdefault</CODE> - Data Field default value<DD><CODE>description</CODE> - Description of data field<DD><CODE>flags</CODE> - Bit-vector for additional attributes of the field. The vector can be ORed together from<BR>
 <table border=1>
 <tr><th>Flag                </th><th>Description                     </th></tr>
 <tr><td>IMPORT_PARAMETER    </td><td>The field is an import parameter</td></tr>
 <tr><td>EXPORT_PARAMETER    </td><td>The field is an export parameter</td></tr>
 <tr><td>OPTIONAL_PARAMETER  </td><td>The field is optional parameter </td></tr>
 <tr><td>INACTIVATE_PARAMETER</td><td>Only used for table parameter,<BR>
                                      indicating that the content of the table will not be sent to the server</td></tr>
 </table><DD><CODE>tab_meta</CODE> - Meta-data if the field is a complex field, i.e. structure or table, <tt>null</tt> otherwise.
        If this field is a structure or table object only the meta data of those objects will we copied
        not reference to the objects ! Use <tt>setValue(...)</tt> to actually set the container object.<DD><CODE>extended</CODE> - extended meta data for this field or <tt>null</tt> if none available.<DT><B>See Also: </B><DD><A HREF="../../../../com/sap/mw/jco/JCO.MetaData.html#addInfo(java.lang.String, int, int, int, int, int, java.lang.String, java.lang.String, int, java.lang.Object, com.sap.mw.jco.IExtendedFieldMetaData)"><CODE>addInfo(String name, int type, int charlength, int length, int offset, int decimals, String sdefault, String description, int flags,Object tab_meta, IExtendedFieldMetaData extended)</CODE></A>, 
<A HREF="../../../../com/sap/mw/jco/JCO.Repository.html"><CODE>JCO.Repository</CODE></A></DL>
</DD>
</DL>
<HR>

<A NAME="addInfo(java.lang.String, int, int, int, int, int, java.lang.String, java.lang.String, int, java.lang.Object, com.sap.mw.jco.IExtendedFieldMetaData)"><!-- --></A><H3>
addInfo</H3>
<PRE>
public void <B>addInfo</B>(java.lang.String&nbsp;name,
                    int&nbsp;type,
                    int&nbsp;charlength,
                    int&nbsp;length,
                    int&nbsp;offset,
                    int&nbsp;decimals,
                    java.lang.String&nbsp;sdefault,
                    java.lang.String&nbsp;description,
                    int&nbsp;flags,
                    java.lang.Object&nbsp;tab_meta,
                    com.sap.mw.jco.IExtendedFieldMetaData&nbsp;extended)</PRE>
<DL>
<DD>Adds a new field descriptor to the meta data object<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>charlength</CODE> - Data field length in character units<DD><CODE>length</CODE> - Data field internal length in bytes<DD><CODE>offset</CODE> - Data field offset in the internal JCO data buffer<DD><CODE>decimals</CODE> - Data field number of decimals (only necessary for the data types JCO.TYPE_BCD and JCO.TYPE_FLOAT)<DD><CODE>sdefault</CODE> - Data Field default value<DD><CODE>description</CODE> - Description of data field<DD><CODE>flags</CODE> - Bit-vector for additional attributes of the field. The vector can be ORed together from<BR>
 <table border=1>
 <tr><th>Flag                </th><th>Description                     </th></tr>
 <tr><td>IMPORT_PARAMETER    </td><td>The field is an import parameter</td></tr>
 <tr><td>EXPORT_PARAMETER    </td><td>The field is an export parameter</td></tr>
 <tr><td>OPTIONAL_PARAMETER  </td><td>The field is optional parameter </td></tr>
 <tr><td>INACTIVATE_PARAMETER</td><td>Only used for table parameter,<BR>
                                      indicating that the content of the table will not be sent to the server</td></tr>
 </table><DD><CODE>tab_meta</CODE> - Meta-data if the field is a complex field, i.e. structure or table, <tt>null</tt> otherwise.
        If this field is a structure or table object only the meta data of those objects will we copied
        not reference to the objects ! Use <tt>setValue(...)</tt> to actually set the container object.<DD><CODE>extended</CODE> - extended meta data for this field or <tt>null</tt> if none available.</DL>
</DD>
</DL>
<HR>

<A NAME="addInfo(java.lang.String, char, int, int)"><!-- --></A><H3>
addInfo</H3>
<PRE>
public void <B>a