Most of the business objects use a generic approach to fetch their main data. As the business objects often provide their data in structures using readable field names (external view), two structures exist (external and internal view). These structure have exactly the same fields in the same order with the data elements. The only difference are the field names:
/PCH/BO_<OBJECT_TYPE>_MAIN_DATA - is representing the main data structure which is provided by the business object. Its field names are normally more descriptive.
/PCH/BO_<OBJECT_TYPE>_DB_MAIN_DATA - is representing the main data structure which is used to select data from the database. Its field names correspond to the database table field names.
/PCH/BO_<OBJECT_TYPE>_EXT_DATA - is representing the data structure for all additional fields (e.g for edit) normally with more descriptive field names.
/PCH/BO_<OBJECT_TYPE>_DB_EXT_DATA - is representing the corresponding structure for database selection.
The main select of data only reads a subset of the database to increase the performance. Customers may extend the field set by extending both of the structures without any code implementation. You'll find all structure names within the maintenance view /PCH/OBJ_V01.
...
Info |
---|
Only some Business Objects (MARA, MARC and MVKE) provide, the EXT data (extended data) additionally to the MAIN data. |
...
Note |
---|
Like in the delivered version of the structure, the customer specific fields must be appended in both structures (normal and DB) with the same fields in the same order using the same data elements. It is possible to use the same field names in both structures as well as rename the field in the external structure. Customer specific fields have to respect the namespace rules. |
...
Info |
---|
If you plan to use the same names in the external view as the field is named in the database, it is suggested to use one single common include for both structures (normal and DB). |