ESH_L_KNB1_CUST-TOGRU SAP table Field - Tolerance Group for Business Partner/G/L Account values
TOGRU is a standard field within SAP Table view ESH_L_KNB1_CUST that stores Tolerance Group for Business Partner/G/L Account information.
Below is the list of attribute values for the TOGRU field including its length, data type, description text, associated data element, search help etc... You could also view this information on your SAP system if you enter the table name ESH_L_KNB1_CUST or data type TOGRU into the relevant SAP transactions such as SE11 or SE80 etc.
Also check out the example ABAP code to select data contained in this field along with useful hints, tips and screen shots specific to this SAP table field.
Summery for field ESH_L_KNB1_CUST-TOGRU
SAP togru-ESH_L_KNB1_CUST field is a none Key Field of table ESH_L_KNB1_CUST that it stores Tolerance Group for Business Partner/G/L Account
Attributes of ESH_L_KNB1_CUST SAP Table field TOGRU
Example ABAP code to select data from table ESH_L_KNB1_CUST field TOGRU
DATA: LD_TOGRU TYPE ESH_L_KNB1_CUST-TOGRU.SELECT single TOGRU
FROM ESH_L_KNB1_CUST
INTO LD_TOGRU
WHERE...
Attributes of SAP Data Element
Data element (semantic domain): More details... | TOGRU |
Language Key: More details... | |
Activation State of Repository Object: More details... | Entry activated or generated in this form |
Version of the entry (not used): More details... | |
Domain name: More details... | TOGRU |
Short Description of Repository Objects: More details... | |
Length (No. of Characters): More details... | |
Heading: More details... | |
Get/Set parameter ID: More details... | |
No parameter ID is assigned to this data element so the ABAP statements GET PARAMETER ID and SET PARAMETER ID can't be used to store and retrieve values from memory | |
Short Field Label: More details... | |
Flag for writing change documents: More details... | No |
Change document history is not recorded for this FIELD and no entries will be made in tables CDHDR and CDPOS.
| |
Maximum length of heading: More details... | |
Medium Field Label: More details... | |
Long Field Label: More details... | |
Max. length for short field label: More details... | |
Max. length for medium field label: More details... | |
Max. length for long field label: More details... | |
Activation flag: More details... | Start of activation or activation successful |
Application class for DD objects (not used): More details... | FB |
Activation type: More details... | |
Original Language in Repository objects: More details... | |
SDIC: Reserve for data elements (not used): More details... | |
Flag for private DD objects (not used): More details... | |
Name of a Search Help: More details... | |
Name of a search help parameter: More details... | |
Default name for components using the data element: More details... | |
Data Type in ABAP Dictionary: More details... | CHAR |
Length (No. of Characters): More details... | 4 |
Number of Decimal Places: More details... | |
Output Length: More details... | |
Allow lowercase letters or NOT: More details... | No |
As this is set to No all text stored within a field associated with domain will be converted to uppercase irrespective of case entered by the user. | |
Field contains negative values: More details... | Yes |
Basically saves the first position of the field so that a + or -sign can be displayed when output. Only valid for floating point,Quantity, Decimal and Currency data types | |
Conversion Routine: More details... | |
Converts the field value between the display and internally stored format. The 5 char ID (i.e. ) associates this field with the underlying ABAP function modules that perform the conversion. | |
Domain contains fixed values: More details... | No |
Value table: More details... | |
Category of Dictionary Type: More details... | |
Type of Object Referenced: More details... | |
Not relevant as this field is an Elementary Domain Type rather than a reference type. | |
DD: Is a generated proxy object: More details... | |
Force write direction to be LTR: More details... | |
If this flag is set the field content is always displayed using the left to right writing direction, even if the write direction of the screen/user is right to left. Maybe useful for digit based data such as phone numbers which may be un-readable using RTL direction. See OSS note 1291845 | |
DD: No Filtering of BIDI Formatting Characters: More details... | |
DD: Flag for Deactivating Input History in Dynpro Field: More details... | |
ABAP Language Version: More details... |
Other SAP tables containing same field/data element
SAP tables containing data element TOGRUSearch for further information about these or an SAP related objects