COFIT_K SAP (Key structure for reconciliation ledger totals) Structure details
Description: Key structure for reconciliation ledger totals
Structure field list including key, data, relationships and ABAP select examples
COFIT_K is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Key structure for reconciliation ledger totals" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_COFIT_K TYPE COFIT_K.
The COFIT_K table consists of various fields, each holding specific information or linking keys about Key structure for reconciliation ledger totals data available in SAP. These include RLDNR (Ledger), RRCTY (Record Type), RVERS (Version), RYEAR (Fiscal Year).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified
SAP COFIT_K structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| RCLNT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| RLDNR | Ledger | RLDNR | CHAR | 2 | T881 | ALPHA | RLDNR | GLN | H_T881 |
| RRCTY | Record Type | RRCTY | CHAR | 1 | RRCTY | ||||
| RVERS | Version | VERSN | CHAR | 3 | TKA09 | ALPHA | COVERSI | KVS | |
| RYEAR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| ROBJNR | Object number for FI-SL tables | GOBJNR | CHAR | 18 | OBJNR | ||||
| COBJNR | Object number for FI-SL tables | GOBJNR | CHAR | 18 | OBJNR | ||||
| SOBJNR | Object number for FI-SL tables | GOBJNR | CHAR | 18 | OBJNR | ||||
| RTCUR | Currency Key | RTCUR | CUKY | 5 | TCURC | WAERS | FWS | ||
| RUNIT | Base Unit of Measure | MEINS | UNIT | 3 | T006 | CUNIT | MEINS | ||
| DRCRK | Debit/Credit Indicator | SHKZG | CHAR | 1 | SHKZG | ||||
| RPMAX | Period | RPMAX | NUMC | 3 | RPMAX | ||||
| RBUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
| RACCT | Cost Element | KSTAR | CHAR | 10 | CSKA | ALPHA | KSTAR | KAT | |
| RHRKFT | Origin Group as Subdivision of Cost Element | HRKFT | CHAR | 4 | TKKH1 | HRKFT | |||
| ROBART | Reconciliation ledger object type (technical) | COFI_OB_CV | CHAR | 2 | OBART | J_OBART_LD | |||
| RSCOPE | Object Class | SCOPE_CV | CHAR | 2 | SCOPE | SCOPE_CV | PCO | ||
| RBUSA | Business Area | GSBER | CHAR | 4 | TGSB | GSBER | GSB | ||
| SBUKRS | Company code of partner | PBUKRS | CHAR | 4 | T001 | BUKRS | BUK | ||
| SACCT | Cost element of partner | PKSTAR | CHAR | 10 | CSKA | ALPHA | KSTAR | KAT | |
| SHRKFT | Origin of partner (subdivision of cost element) | PHRKFT | CHAR | 4 | TKKH1 | HRKFT | |||
| SOBART | Partner object type (for reconciliation ledger) | COFI_PO_CV | CHAR | 2 | OBART | J_OBART_LD | |||
| SSCOPE | Partner object class | PSCOPE_CV | CHAR | 2 | SCOPE | SCOPE_CV | |||
| SBUSA | Trading partner's business area | PARGB | CHAR | 4 | TGSB | GSBER | GSB | ||
| VRGNG | CO Business Transaction | CO_VORGANG | CHAR | 4 | TJ01 | J_VORGANG | |||
| KOKRS | Controlling Area | KOKRS | CHAR | 4 | TKA01 | CACCD | CAC | ||
| OCLNT | Original client | OCLNT | NUMC | 3 | NUM3 | ||||
| WRTTP | Value Type | CO_WRTTP | CHAR | 2 | CO_WRTTP |
| Key field | Non-key field |
How do I retrieve data from SAP structure COFIT_K using ABAP code?
As COFIT_K is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on COFIT_K as there is no data to select.How to access SAP table COFIT_K
Within an ECC or HANA version of SAP you can also view further information about COFIT_K and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects