CL_COND_DATACONTAINER - Conditions: Generic Data Container

Addresses (Business Address Services)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Functionality

The CL_COND_DATACONTAINER class enables you to put the data part of a condition technique usage in a uniform format. Each table of the data part is represented by its owndata object.Each data object has properties such as a superior data object and cardinality. This defines the relationships of the data objects to each other, so that they form a hierarchy.

To generate an instance, there are two static methods available:

• CREATE_BY_USAGE

This method generates the appropriate instance for a usage. Make sure that the IF_COND_USAGE_BADI_MAINTENANCE~GET_DATAPART_DESCRIPTIONmethod of the BAdI COND_USAGE_BADI is implemented for this usage. Without this implementation the instance cannot be generated and the BADI_NOT_IMPLEMENTED exception is triggered.

• GET_INSTANCE

This method generates an instance using the transferred meta data for the data part description. This method is intended for internal usage, and therefore the CREATE_BY_USAGE method should preferably be used.

The following instance methods are available:

• Methods for working with a data object

• SET_DATA

Transfers the data records of the IT_DATA table to the data object whose name has been specified withI_NAME. The I_OVERWRITE parameter is used to control whether the previous data records of the data object are to be completely overwritten. The line type of IT_DATA must be suitable for the respective data object.

• SET_DATA_REF

This method functions like SET_DATA, but the table data must be transferred for each reference (parameter I_DATAREF).

• GET_DATA

Gets the data records from the data object whose name has been specified with I_NAME. The data is put in the ET_DATA table that must have a suitable line type.

• GET_DATA_REF

This method functions like GET_DATA, but the data is returned as a reference to a copy. The copy is generated dynamically for this purpose and is a standard table.

• RESET_DATAOBJECT

Removes all data records from a data object. The data object is "empty" afterwards.

In addition, the GET_DATAOBJECT method is available which you can use to directly access thedata object to carry out more specialized operations.

• Methods for the hierarchy of the data objects

• GET_SUPERORDINATED_DATAOBJECT

Like GET_DATAOBJECT, but it returns the superior data object.

• GET_SUBORDINATED_DATAOBJECTS

Returns all lower-level data objects for the specified data object, either as a table of object references or as a table of data object names.

• IS_DATAOBJECT_MANDATORY

Returns a truth value as to whether the data object is mandatory. That means at least one data record must exist for each data record of the preceding (superior) data object.

• IS_DATAOBJECT_MULTIPLE

Returns a truth value as to whether the data object is multiple. That means several data records can exist for each data record of the preceding (superior) data object.

• GET_CONTAINER_STRUCTURE

Returns the structure of the data objects contained in the data container. The following information is determined for each data object:

object_level,,,,,,Level of data object (ROOT = 0)

object_name,,,,,,Name of data object

parent_object,,,,,,Name of preceding (superior) data object

is_mandatory,,,,,,Data object is mandatory

is_multiple,,,,,,Data object is multiple

• GET_ALL_DATA_REF

Returns a table with the names and data references of all data objects. The data references point to standard tables that contain the copies of all data records.

• Additional Methods

• CHANGE_RECORD_NUMBER

Changes the condition record number (from old to new) if it is in the data record key.

• ENABLE_AUTOMATIC_NUMBER_CHANGE

Relationships

Example

Notes

Further information

BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.


Length: 5432 Date: 20120526 Time: 103155     triton ( 153 ms )