Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | TTYPE |
| Short Description | Table type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TTYPE | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | Tab. type |
| Medium | 15 | Table type |
| Long | 20 | Table type |
| Heading | 3 | Typ |
Documentation
Definition
Since all tables used by General Ledger have to be entered in table T800A, they have to be classified by table type.
Possible values:
TT General Ledger summary table
SI General Ledger line items. Object tables must store a line item
table.
SP Plan line items. If you store plan line items, you must enter this
table with table type SP. The assigned summary record entry and
line item entry must also store the plan line item table.
ST General Ledger line item structures (without database)
Here you have to specify the assigned summary table under
'Corr.Tab.'. You enter this using table type TT, but you must not
enter any assigned line item table under 'Corr.Tab.' because this
is only a line item structure.
VL External tables that use G/L
For example, for direct posting, ledger selection, validation
CM G/L master data
CT G/L master data texts
AL Tables for assessment/distribution (storing fixed portions)
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
