SAP ABAP Data Element FELDM (IS-H: Field Attribute String)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ NBAS (Package) Appl. development Hospital System master data, catalogs

Basic Data

Data Element	FELDM
Short Description	IS-H: Field Attribute String

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	FELDM
Data Type	CHAR	Character String
Length	255
Decimal Places	0
Output Length	255
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	AttrString
Medium	14	Attrib.String
Long	20	AttributeString
Heading	50	AttributeString

Documentation

Definition

The screen attributes of a field can be controlled using the following symbols:
. The field is ready for input ('optional entry')
* The field is only displayed, it is not ready for input
+ The field requires an entry ('required entry')
- The field is not displayed on the screen
(Blank) There is no field with the corresponding modification group

Supplementary Documentation - FELDMODIF 1000

Use

Procedure

Examples

Dependencies

The following is possible in rollup field movements:

• Summarization by omitting fields
  When you execute the rollup, only those fields that have been entered in the field movement (in addition to those defined in table T800M) are transferred to the rollup ledger. The summarization of data occurs by omitting dimensions.
  
• Summarization using substitution
  During the field movement, you can also substitute fields (for example, products are assigned to a product group) using substitution activities; this also results in a summarization of data. You must enter these substitution activities in the field movement.
  
• Rolling up between local and global tables
  If you want to roll up between local and global tables, the field movement must contain a fixed company code or a fixed global company into which data is to be summarized.
  
• User exits
  Using user exits that are entered in the field movement or in substitution activities, you can influence the processing of the individual records at three different points in time when you execute the rollup:
• directly after reading the summary record
• when transferring a specific field
• directly before writing the rollup record

Note

In addition to transferring fields to the receiver table when you roll up using line items, you can also transfer fields to the relevant line item table for documentation purposes. You must make sure that the receiver field exists in table 'GLU1' and in the line item table, but not in the summary table.

Supplementary Documentation - FELDMODIF 2000

Use

Test

Procedure

Examples

Dependencies

Test

History

Last changed by/on	SAP	20050224
SAP Release Created in