Each BAPI Bean information class is based on a class in the Java Class Library. The Java Class Library implements Java so that each business object's proxy class has a corresponding JavaBeans information class. For example, the proxy class for the business object SalesOrder is jboSales Order , and the corresponding JavaBeans information class is jboSalesOrderBeanInfo (the jboSalesOrderBeanInfo class is derived from the com.sap.bapi.jboBeanInfo class). The SAP R/3 System uses the information class as the gateway to obtain detailed information about a BAPI Bean, including its properties, methods, and features.

Unlike classes in the Java Class Library, BAPI Beans have no explicit properties. SAP has implemented BAPI Beans so that a key consisting of several keyfields identifies each business object instance, and the methods required are the BAPI methods themselves. SAP also has implemented factory methods, such as those responsible for creating new instances of business objects, as BAPI Beans. In addition, all of the simple, structure, import, export, and table parameters associated with BAPI methods are implemented as BAPI Bean features, and all of the constructors, keyfields, methods and parameters are described by JavaBean feature descriptor classes. These classes are described below:

The jboBAPIDescriptor Class

The jboParameterContainerDescriptor Class

The jboConstructorDescriptor Class

The jboParameterDescriptor Class

The jboSimpleParameterDescriptor Class

The jboStructureParameterDescriptor Class

The jboTableParameterDescriptor Class

The jboKeyfieldDescriptor Class

• getBAPIDescriptors
• getBeanDescriptor
• GetConstructorDescriptors
• GetKeyfieldDescriptors
• GetMethodDescriptors