SAP ABAP Data Element GENIL_TEXT_ACCESS_SUPPORTED (Tells if Text Access via GenIL Object Model is Supported)
Hierarchy
☛ WEBCUIF (Software Component) SAP Web UI Framework
   ⤷ CA-WUI-GOL-GIL (Application Component) Generic Interaction Layer
     ⤷ CRM_GENIL (Package) Generic Interaction Layer for Access to CRM Objects
Basic Data
Data Element GENIL_TEXT_ACCESS_SUPPORTED
Short Description Tells if Text Access via GenIL Object Model is Supported  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type GENIL_TEXT_ACCESS_SUPPORTED    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Txt Access 
Medium 11 Text Access 
Long 21 Text Access Supported 
Heading 21 Text Access Supported 
Documentation

Definition

In this setting you specify if and how text access for the value of an object attribute is supported.

Note that your selection may require an implementation in the underlying component of the generic Interaction Layer (genIL).

The text of an object attribute is retrieved programmatically using method GET_TEXT of the BOL entity class CL_CRM_BOL_ENTITY. All possible values for an attribute may be retrieved via method GET_TEXTS if supported as pointed out below.

Use

You have the following options:

  • Not Defined
    indicates that a text access strategy has not yet been modeled for an attribute.

    Since it helps to reduce effort in the application development, it is strongly recommended to avoid this setting. Indicate explicily if a call of the methods GET_TEXT and GET_TEXTS is supported.

    Note: With this setting the flooplan manager cannot offer the attribute text for UI configuration.
  • Text Access by Attribute Value
    indicates that text access is done by attribute value.

    Here the text does not depend on the value of other attributes of the object instance the text is to be determined for. In contrast to the option "Access to all Texts by Object Type" the retrieval of all possible attribute values at once - e.g. to populate a pick list - is not supported.

    For faster access the texts are buffered in the business object layer BOL.
  • Text Access by Object Instance
    indicates that text access is done by attribute instance.

    Here the text of an attribute value may depend on any other attribute of the object instance.

    In contrast to the option "Access to all Texts by Object Instance" the retrieval of all possible attribute values at once is not supported.

    Texts are not buffered in the BOL.
  • Access to all Texts by Object Type
    indicates that access to the texts of all possible attribute values is supported by object type.

    Texts depend on the attribute value and are the same for all object instances. You may request the entries of a picklist. Attribute texts are buffered in the BOL.

    Attention: Do not use this setting in the case the number of possible entries is high - e.g. greater than 100.
  • Access to all Texts by Object Instance
    indicates that access to the texts for all attribute values is supported by object instance.

    Text may depend on various attribute values of the object instance and hence may differ for the same attribute value by instance. Attribute texts are not buffered in the BOL.

    Use this setting in case you would like to retrieve a list of all possible attribute values with texts progammatically and in case you would not like to get it buffered in the BOL.
  • Not Supported

    Use this setting in case no text is determined for the attribute.

Dependencies

A default implementation for text access is provided by the genIL core for the following common use cases:

  • The underlying domain in the data dictionary specifies fixed values for the object attribute

    You typically use setting Access to all Texts by Object Type in this case.
  • The domain has a value table which itself has a text table. The value table is linked with a foreign key definition to the attribute in the attribute structure of the object.

    You typically use setting Text Access by Object Instance in this case.

You may implement a custom logic in method IF_GENIL_APPL_INTLAY~GET_TEXT of your GenIL component.

In order to activate the default implementation the GenIL component needs to raise exception CX_CRM_GENIL_NOT_IMPLEMENTED in case the text for the attribute in question has been requested.

Example

The text for the value "US" of attribute "NATION" is "United States Of America".

History
Last changed by/on SAP  20110908 
SAP Release Created in 731