CL_AXT_CUSTOMER_TABLES_UTIL - Utility Class for customers to simplify stable data retrieva

General Material Data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Functionality

To modify table enhancements and rapid applications, you need to know a few basic terms.

At runtime, both use structures that have the following format:

| RECORD_ID | PARENT_ID | OBJECT_ID | [logical key fields] | [other fields] |

Such a structure is called "work structure". If you have a look into transaction AXTSHOW, you can seethat such a structure has been generated there. If you implement a BAdI for a specific table, you canuse the specific structure type listed in AXTSHOW. Make sure that you activate the BAdI with the correctfilter set. Otherwise, the system might produce syntax errors at runtime, because the BAdI is called for all table enhancements and rapid applications.

If a database table is generated, it has the same structure, and an additional CLIENT field.

The work structure contains the following fields:

• RECORD_ID: unique key of an entry in the database

In general, it is a GUID, but it can also be the position correct concatenated database key in caseof existing tables in rapid applications. The constant defining this field name is CL_AXT_TABLES_METADATA=>GC_RECORD_ID_FIELDNAME. In general, you can use the data type STRING for it.

• PARENT_ID: ID of the parent object

For root objects of rapid applications, this field is empty. For table enhancements, it could be, forexample, the order header. The constant defining this field name is CL_AXT_TABLES_METADATA=>GC_PARENT_ID_FIELDNAME. In general, you can use the data type STRING for it.

• OBJECT_ID: ID of the object that the current record is part of

This object can be the rapid application or the object that the table enhancement is part of (for example,an order). The constant defining this field name is CL_AXT_TABLES_METADATA=>GC_OBJECT_ID_FIELDNAME. In general, you can use the data type STRING for it.

• Logical key fields are mostly optional (not for rapid application header tables). The uniquenessof keys is ensured by the internal API. If there is a logical key, there is also a logical key structure with all fields of the logical key.

This class also provides the following methods, which you can use to retrieve additional data for BAdI implementations:

• GET_DATA_BY_RECORD_ID returns the work structure of a record identified by the RECORD_ID and the database table name.

• GET_CHILD_DATA_BY_RECORD_ID can only be used for rapid applications. It returns a table with data in the work structure format from a specific child table, which points to the current record.

Relationships

Example

Notes

Further information

ROGBILLS - Synchronize billing plans   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.


Length: 2871 Date: 20120526 Time: 085132     triton ( 130 ms )