SAP Financial Consolidation Database Schema Guide

Administration Guide | CONFIDENTIALSAP Financial ConsolidationDocument Version: 10.1 Support Package 09 – 2021-12-14

SAP Financial Consolidation Database Schema Guide

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.1 Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

ct_datasource: data sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13ct_datasource_dim: dimensions associated with data sources. . . . . . . . . . . . . . . . . . . . . . . . . . 14ct_datasource_indexes: indexes associated with data sources. . . . . . . . . . . . . . . . . . . . . . . . . . 15ct_datasource_prop: properties associated with data sources. . . . . . . . . . . . . . . . . . . . . . . . . . 16ct_dimension: data source dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16ct_ds_property: data source properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.2 Reference tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18ct_reftable: reference tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18ct_charac: reference table characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19ct_charac_path: path of characteristics (level > 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20ct_charac_dim_visibility: characteristics displayed depending on dimensions (not used). . . . . . . 21ct_rt_property: reference table properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1.3 Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22ct_filter: reference table filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22ct_filter_expr: filter definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23ct_filter_dim_visibility: filters displayed depending on dimensions (not used). . . . . . . . . . . . . . . 23ct_filter_result: filters displayed results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1.4 Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24ct_icon: icons associated with structural items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24ct_period_month: table of translatable period descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 24ct_property:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2 Product reference tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272.1 Associated with amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

ct_phase: category reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27ct_variant: consolidation variant reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27ct_scope_code: scope reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28ct_entity: reporting unit reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28ct_curncy: currency reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29ct_account: account reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29ct_flow: flow reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30ct_nature: audit ID reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30ct_techorig: technical origin reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31ct_mu : reference table for Management Unit dimension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31ct_scope_entity_custom_prop: custom property for the scope. . . . . . . . . . . . . . . . . . . . . . . . . .32

2 CONFIDENTIALSAP Financial Consolidation Database Schema Guide

Content

2.2 Associated with other data sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32ct_scope_version: scope version reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32ct_portfl_code: investment code reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32ct_exrate_version: conversion rate version reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . .34ct_exrate_type: conversion rate type reference table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34ct_taxrate_type: tax rate type reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35ct_country: country reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35ct_var_interco: intercompany variant reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35ct_action_context: Package amount trace context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.3 Associated with characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36ct_sign: account sign reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36ct_class: account class reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37ct_nat_level: audit ID level reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37ct_curncynat: currency audit ID type reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37ct_consonat: audit ID loading restriction reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38ct_techtype: technical origin type reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38ct_techoriglvl: technical origin level reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3 Amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.1 Package amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

ct_pkref: partitioning of package amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40ct_pkPPPP: package amounts data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40ct_pbref : partitioning of published packages amouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41ct_pbPPPP: published package amounts data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41ct_pbdref : partitioning of historical published packages amouts . . . . . . . . . . . . . . . . . . . . . . . . 42ct_pb_deltaPPPP: historical published package amounts data source. . . . . . . . . . . . . . . . . . . . .42

3.2 Preconsolidated amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43ct_pcref: partitioning of preconsolidated amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43ct_pcPPPP: preconsolidated amounts data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44ct_pcdref : partitioning of preconsolidated packages amouts delta data source. . . . . . . . . . . . . . 45ct_pc_deltaPPPP: preconsolidated packages amouts delta data source. . . . . . . . . . . . . . . . . . . 45

3.3 Consolidated amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46ct_coref: partitioning of consolidated amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46ct_coPPPP: consolidated amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.4 Intercompany amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48ct_intercos: intercompany data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.5 Opening balances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49ct_opbalref: partitioning of opening balance data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49ct_opbalPPPP: opening balance data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4 Operation objects associated with amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.1 Package amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

SAP Financial Consolidation Database Schema GuideContent CONFIDENTIAL 3

ct_pack: packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51ct_pack_workflow: list of users authorized to use the package. . . . . . . . . . . . . . . . . . . . . . . . . . 58ct_pack_embedded_file: package attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59ct_pack_period_trans: settings for package periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59ct_pack_protect_period: settings for protecting package periods. . . . . . . . . . . . . . . . . . . . . . . . 59ct_pack_protect_flow: settings for protecting package flows. . . . . . . . . . . . . . . . . . . . . . . . . . . 60ct_pack_lock: package lock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60ct_journal_pack: journal entry ledgers associated with packages (technical table). . . . . . . . . . . . 61ct_pk_entry: package journal entry headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.2 Preconsolidated amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64ct_preconsopack: preconsolidated package headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64ct_preconsopack_period_trans: settings for package periods (preconsolidated level). . . . . . . . . .70ct_preconsopack_protect_flow: settings for protecting package flows (preconsolidated). . . . . . . 70ct_preconsopack_protect_period: settings for protecting package periods (pc). . . . . . . . . . . . . . 70ct_preconsopack_histo : history of preconsolidated package headers. . . . . . . . . . . . . . . . . . . . . 71ct_publishedpack : published packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72ct_publishedpack_histo: history of published packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73ct_pc_entry: preconsolidated journal entry header table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74ct_mje_wrkflw_notif_reg : definition of entries notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

4.3 Consolidated amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77ct_conso_def: consolidation definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77ct_conso_def_per: consolidation periods definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81ct_consopack: consolidated package headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82ct_conso_def_embedded_file: attachment for consolidation definition. . . . . . . . . . . . . . . . . . . . 83ct_co_entry: consolidated journal entry header table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83ct_tbl_scope: consolidation scopes associated with consolidations. . . . . . . . . . . . . . . . . . . . . . 86ct__tblglobal_scope: full consolidation scope associated with consolidations. . . . . . . . . . . . . . . 90ct_tbl_shares: stockholdings associated with consolidations. . . . . . . . . . . . . . . . . . . . . . . . . . . 94ct_tbl_scope2: secondary consolidation scopes associated with consolidations. . . . . . . . . . . . . 96ct_tbl_global_scope2: full secondary consolidation scopes associated with consolidations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100ct_tbl_shares2: secondary stockholdings associated with consolidations. . . . . . . . . . . . . . . . . 104

4.4 Intercompany amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107ct_interco_def: intercompany reconciliations processing definition. . . . . . . . . . . . . . . . . . . . . . 107

4.5 Opening balance amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108ct_pack_model: opening balance package (or generated package) headers. . . . . . . . . . . . . . . . 108ct_pack_model_period_trans: settings for generated package periods. . . . . . . . . . . . . . . . . . . . 114ct_pack_model_protect_flow: settings for protecting generated package flows. . . . . . . . . . . . . . 114ct_pack_model_protect_period: settings for protecting generated package periods. . . . . . . . . . 115

5 Other data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165.1 Investments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116


Content

ct_portfl: investment data source headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116ct_portfl_lines: investment data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117ct_portfl_graph_props: display properties of charts in investment occurrences. . . . . . . . . . . . . .118

5.2 Scopes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118ct_scope: scope data source headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118ct_scope_lines: scope data source (reporting units). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120ct_scope_portfl_lines: scope data source (stockholdings). . . . . . . . . . . . . . . . . . . . . . . . . . . . 123ct_scope_graph_props: display properties of charts in scope occurrences. . . . . . . . . . . . . . . . . 124

5.3 Conversion and tax rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125ct_exchange_rate_header: conversion rate table headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125ct_exrate: conversion rate data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125ct_taxrate_header: tax rate headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126ct_taxrate: tax rate data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

6 Operation definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1276.1 Reporting ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

ct_reporting: reporting ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127ct_reporting_period_trans: settings for reporting periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131ct_reporting_protect_flow: settings for protecting reporting flows. . . . . . . . . . . . . . . . . . . . . . . 131ct_reporting_protect_period: settings for protecting reporting periods. . . . . . . . . . . . . . . . . . . 132ct_journal_reporting_site: journal entries associated with reporting IDs (technical table). . . . . . .132ct_hierarchy: information about the whole hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133ct_hierarchy_content: hierachy content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

6.2 Reporting set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134ct_entity_reporting: reporting sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134ct_entity_rep_period_trans: settings for reporting set periods. . . . . . . . . . . . . . . . . . . . . . . . . 139ct_entity_rep_protect_flow: settings for protecting reporting set flows. . . . . . . . . . . . . . . . . . . 139ct_entity_rep_protect_period: settings for protecting reporting set periods. . . . . . . . . . . . . . . . 139ct_input_restriction: data entry restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140ct_ser_input_restr: data entry restrictions definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140ct_pack_group_comment: group comment for packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140ct_pack_user: list of users authorized to access the package (workflow). . . . . . . . . . . . . . . . . . 141

6.3 Ledgers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141ct_journal: journal entry ledger reference table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141ct_journal_to_nature: audit IDs associated with journal entry ledgers. . . . . . . . . . . . . . . . . . . . 142ct_journal_to_phase: categories associated with journal entry ledgers. . . . . . . . . . . . . . . . . . . .142

6.4 Journal entry templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142ct_entry_model: journal entry template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142ct_entry_model_rows: journal entry template rows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143ct_entry_model_to_entity: restrictions by reporting unit in the journal entry template. . . . . . . . . 143ct_entry_model_to_framework: restrictions by category scenario in the journal entry template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144


ct_entry_model_to_phase: restrictions by category in the journal entry template. . . . . . . . . . . . 144ct_entry_embedded_file: central journal entry attachment. . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

7 Report Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467.1 Schedules and schedule items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

ct_document: schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146ct_document_serial_doc: schedule definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147ct_document_input_comment: schedule data entry guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147ct_docuser: most recently used schedule values by user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147ct_doc_template: style book (automatic presentation). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148ct_doc_template_serial: style book definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148ct_headerfooter: schedule headers and footers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148ct_headerfooter_serial: schedule header and footer definition. . . . . . . . . . . . . . . . . . . . . . . . . 149ct_doc_formula: schedule initialization formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149ct_doc_form_to_dim: dimensions associated with schedule formulas. . . . . . . . . . . . . . . . . . . . 149ct_doc_scheduleenhancement: enhancements to schedules for planning. . . . . . . . . . . . . . . . . 150ct_doc_scheduleenhancementdata: enhancements made to schedules for planning. . . . . . . . . . 151

7.2 Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151ct_folder: folders for schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151ct_folder_to_phase: folders displayed according to the category. . . . . . . . . . . . . . . . . . . . . . . . 152ct_book: schedule books. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152ct_baf_tree_link: relationships in the folder/book/schedule hierarchy. . . . . . . . . . . . . . . . . . . . 152

7.3 Report bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153ct_state: schedule settings for report bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153ct_state_to_define_data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153ct_statesgroup: report bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154ct_statesgroup_to_phase: report bundles assigned by category. . . . . . . . . . . . . . . . . . . . . . . . 154ct_statesgroup_to_define_data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

8 Category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558.1 Definition and general settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

ct_framework: category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155ct_framework_version: category scenario version reference table. . . . . . . . . . . . . . . . . . . . . . . 164ct_framework_period_trans: settings for category scenario periods (for opening balances). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164ct_framework_protect_flow: settings for protecting category scenario flows (opening balances). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164ct_framework_protect_period: settings for protecting category scenario periods (opening balances). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

8.2 Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165ct_period: periods defined in category scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165ct_cumul_def: definition of totals accumulated periodically in the category scenario. . . . . . . . . .165ct_source: initialization sources in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166


Content

ct_source_def: definition of initialization sources in the category scenario by period. . . . . . . . . . 1668.3 Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

ct_acc_family: sets of indicators in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . .166ct_frmwrk_acc: sets of indicator accounts in the category scenario. . . . . . . . . . . . . . . . . . . . . .168ct_frmwrk_calculaccumul_filter: calculation accumulation filters. . . . . . . . . . . . . . . . . . . . . . . 169ct_frmwrk_calculperiod_filter: calculation period filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169ct_frmwrk_flow: sets of indicator flows in the category scenario (and flow template). . . . . . . . . .169ct_comment_family: set of indicators with comments in the category scenario. . . . . . . . . . . . . 170ct_comment_indicator: indicators with comments in the category scenario. . . . . . . . . . . . . . . . 171ct_indicators: details about the category scenario indicators. . . . . . . . . . . . . . . . . . . . . . . . . . .171

8.4 Dimensional Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172ct_analyse: dimensional analysis in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . 172ct_indic: indicators broken down in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . .173ct_det_anal: analysis dimensions used by dimensional analysis in the category scenario. . . . . . . 174ct_form_auto: category scenario automatic formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175ct_cont_auto: analysis hierarchy automatic controls in the category scenario. . . . . . . . . . . . . . .176ct_control_auto_to_document: schedules associated with automatic controls. . . . . . . . . . . . . . 176ct_set_to_contauto: automatic controls associated with sets of controls. . . . . . . . . . . . . . . . . . 176ct_fam_to_contauto: automatic controls associated with sets of controls in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

8.5 Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177ct_formula: category scenario manual formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177ct_formula_condition: conditions for running category scenario formulas. . . . . . . . . . . . . . . . . 178ct_formula_expression: expression of category scenario formulas. . . . . . . . . . . . . . . . . . . . . . .178ct_form_family: subsets of formulas in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 178

8.6 Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179ct_control: category scenario controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179ct_control_factor: control factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180ct_control_expression: expression of controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180ct_control_to_document: schedules associated with controls. . . . . . . . . . . . . . . . . . . . . . . . . .180ct_level: control levels in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180ct_ctrl_set: sets of controls in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181ct_ctrl_family: subsets of controls in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . 181ct_set_to_family: subsets of controls associated with sets of controls. . . . . . . . . . . . . . . . . . . . 182ct_set_to_control: manual controls associated with sets of controls. . . . . . . . . . . . . . . . . . . . . 182ct_family_to_control: manual controls associated with subsets of controls in the category scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

8.7 Compiled category scenario form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182ct_refupdateflag: updating category scenarios in the structure. . . . . . . . . . . . . . . . . . . . . . . . . 182ct_valid_frmwrk: compiled category scenario form (indicators and analyses). . . . . . . . . . . . . . . 183ct_valid_frmwrk_input_data: compiled category scenario form (data which can be entered). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183


ct_valid_frmwrk_init_form: compiled category scenario form (initialization formulas). . . . . . . . . 183ct_valid_frmwrk_pack_form: complied form of the category scenario (schedule context formulas). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184ct_valid_frmwrk_entry_form: compiled category scenario form (journal entry context formulas). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184ct_valid_frmwrk_control: compiled category scenario form (controls). . . . . . . . . . . . . . . . . . . . 184ct_valid_frmwrk_report: compiled category scenario form (carry-over formulas). . . . . . . . . . . . 184ct_valid_frmwrk_info: compiled category scenario form (information). . . . . . . . . . . . . . . . . . . . 185

9 Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1869.1 Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

ct_ruleset: sets and subsets of rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186ct_ruleset_to_phase: sets of rules associated with categories. . . . . . . . . . . . . . . . . . . . . . . . . . 186ct_ruleset_to_ruleset: subsets of rules associated with sets of rules. . . . . . . . . . . . . . . . . . . . . 187ct_ruleset_to_consrule: consolidation rules associated with sets or subsets of rules. . . . . . . . . . 187ct_ruleset_to_preconsrule: preconsolidation rules associated with sets or subsets of rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187ct_ruleset_to_packrule: package rules associated with sets or subsets of rules. . . . . . . . . . . . . 188ct_ruleset_to_interrule: intercompany rules associated with sets or subsets of rules. . . . . . . . . .188ct_ruleset_to_sqlrule: SQL rules associated with sets or subsets of rules. . . . . . . . . . . . . . . . . . 188ct_ruleset_to_ent_rolluprule: entity rules associated with sets or subsets of rules. . . . . . . . . . . .189ct_ruleset_to_accnt_rolluprule: account rules associated with sets or subsets of rules. . . . . . . . 189

9.2 Consolidation rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189ct_consrule: consolidation rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189ct_consrule_serial_selection: consolidation rules - selection. . . . . . . . . . . . . . . . . . . . . . . . . . . 191ct_consrule_serial_scope: consolidation rules - scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191ct_consrule_serial_processing: consolidation rules - processing. . . . . . . . . . . . . . . . . . . . . . . . 192

9.3 Preconsolidation rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192ct_preconsrule: preconsolidation rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192ct_preconsrule_ser_selection: preconsolidation rule selection. . . . . . . . . . . . . . . . . . . . . . . . . 193ct_preconsrule_ser_processing: preconsolidation rule processing definition. . . . . . . . . . . . . . . 193

9.4 Package rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193ct_packrule: package rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193ct_packrule_serial_selection: package rule selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194ct_packrule_serial_processing: package rule processing definition. . . . . . . . . . . . . . . . . . . . . . 194

9.5 Intercompany rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195ct_interrule: intercompany reconciliation rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195ct_interrule_serial_scope: scope restrictions for intercompany rules. . . . . . . . . . . . . . . . . . . . . 197ct_interrule_serial_inter: intercompany rules processing definition. . . . . . . . . . . . . . . . . . . . . . 197

9.6 SQL rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197ct_sqlrule: SQL rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197ct_sqlrule_serial_sql: SQL rule processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198


Content

9.7 Coefficients and functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198ct_rulecoeff: coefficients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198ct_rulefunction: functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201ct_rulefunction_serial_sql: SQL function processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

9.8 Entity Rollup Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202ct_entity_rollup_rule: rules for entity rollup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202ct_entrolluprule_serial: entity rollup serialized data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202ct_ruleset_to_ent_rolluprule: entity rules associated with sets or subsets of rules. . . . . . . . . . . 203

9.9 Account Rollup Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203ct_account_rollup_rule: account rollup rule table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203ct_accnt_rollup_rule_to_dim: account rollup rule to dimension table. . . . . . . . . . . . . . . . . . . . .203

10 Sites and databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20410.1 Site management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

ct_recipient: correspondents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204ct_site: profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

10.2 General settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206ct_config: configuration of the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206ct_language: working languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206ct_active_server: contains items saved corresponding to the servers running concurrently on the same data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207ct_active_session: contains items saved corresponding to the sessions open for the data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207ct_md_lock: table that stores the locks for multi-dimensional data sources. . . . . . . . . . . . . . . . 207ct_mutex: synchronization of access to resource shared by several ctserver instances. . . . . . . . 208ct_pack_mutex :. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208ct_identifier_mutex: synchronization of identifier allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . 208ct_identifier_pool: persisted identifier pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208ct_object_lock:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209ct_recycled_identifier: unknown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209ct_scheduler: unknown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209wctversion: database schema version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209ct_message: manage notifications between every instances of ctserver. . . . . . . . . . . . . . . . . . .210

10.3 Local items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210ct_user_config: user personal settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210ct_viewpoint: Web user viewpoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211ct_pivot_table: MS Excel pivot table queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211ct_pivot_table_serial_pivot: pivot table query definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212ct_allocate_identifier: IDs used and fixed for certain objects (e.g. users, functional profiles, owner groups, etc.). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212

11 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21311.1 Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213


ct_user: users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213ct_user_password: user passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214ct_user_workgroup: workgroups associated with users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214ct_user_profile: functional profiles associated with users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215ct_user_serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

11.2 Workgroups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215ct_workgroup: workgroups (user groups). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

11.3 Functional profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216ct_fnprofile: functional profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216ct_fnprofile_detail: details of functional profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

11.4 Data access groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216ct_datarights: data access groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216ct_datarights_phase: data access rights by category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217ct_access_restriction: access restrictions (obsolete V9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218ct_accessdef_conso: consolidation access definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218ct_accessdef_entry: central manual journal entry access definition. . . . . . . . . . . . . . . . . . . . . . 219ct_accessdef_inputanalysis: data entry analysis access definition . . . . . . . . . . . . . . . . . . . . . . 219ct_ser_access_restr: access restriction definitions (obsolete V9). . . . . . . . . . . . . . . . . . . . . . . 220ct_ser_accessdef_conso: serialized fields in an access definition. . . . . . . . . . . . . . . . . . . . . . . 220ct_ser_accessdef_entry: serialized fields in an access definition. . . . . . . . . . . . . . . . . . . . . . . . 220ct_ser_accessdef_inputanalysis : serialized fields in an access definition. . . . . . . . . . . . . . . . . . 221

11.5 Security V2 – not used by SAP Financial Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221ct_ace: Control for access to work groups for objects (not used by SAP Financial Consolidation). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221ct_acl: list of secure objects (not used by SAP Financial Consolidation). . . . . . . . . . . . . . . . . . . 221ct_compiled_ace: compiled form of access controls for objetcs (not used by SAP Financial Consolidation). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222ct_compiled_acl: compiled form of lists of secure objects (not used by SAP Financial Consolidation). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222ct_right: dynamic definition of access rights (not used by SAP Financial Consolidation). . . . . . . 222

12 Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22412.1 Common item. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

ct_runnableobjects: tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224ct_schedulings: task planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224ct_executions: settings for running tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225ct_history: log for tasks run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225ct_history_detail: detail of log of tasks run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226ct_execresults: results of tasks run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

12.2 Specific items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226ct_filter_restriction: filtering consolidated and preconsolidated data to be sent. . . . . . . . . . . . . 226ct_ser_filter_restr: definition of filters for data to be sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227


Content

12.3 Audit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227ct_auditdef: audit definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227ct_auditdef_serial_searcharea: area used to search for items in an audit. . . . . . . . . . . . . . . . . . 228ct_auditdef_serial_searchedid: objects searched for in an audit. . . . . . . . . . . . . . . . . . . . . . . . 229

12.4 Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229ct_interface_def: datalink definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229ct_interface_def_detail: detail of datalink definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

12.5 Trace reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230ct_log: actions performed by users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

13 Common columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23113.1 ID Columns (id, owner_site, name). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23113.2 Short description columns in 6 languages (sdesc1-6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23113.3 Long description columns in 6 languages (ldesc1-6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23113.4 Extra long description columns in 6 languages (xdesc1-6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23213.5 Security management columns (security columns). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23213.6 HTML comments columns in 6 languages (cdesc). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

14 Appendix 1: Utilities for SQL processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23414.1 Variables available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

14.2 Temporary tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236[TBL_SCOPE]: top consolidation scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236[TBL_GLOBAL_SCOPE]: full consolidation scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236[TBL_SHARES]: stockholding of scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236[TBL_SCOPE2]: top secondary consolidation scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237[TBL_GLOBAL_SCOPE2]: full secondary consolidation scope. . . . . . . . . . . . . . . . . . . . . . . . . 237[TBL_SHARES2]: stockholding of secondary scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237[WORKTABLE]: consolidation worktable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237[USER_TABLE]: consolidation worktable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237[FUNCTION_TABLE]: function result table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

14.3 List of Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23814.4 Meaning of Period IDs in SAP Financial Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23914.5 Utility: Periods in SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24014.6 Extraction of an ID Profile in SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241

15 Appendix 2: Schema of Tables in the Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242


15.1 Storing Data: Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24215.2 Specific Case: Amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24215.3 Dimension Values: Reference Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24315.4 Multi-Dimensional Index Customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24415.5 Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245


Content

1 Structure

1.1 Data Sources

1.1.1 ct_datasource: data sources

Column Type Len. Null Comment

ct_entry_document int 4 yes data entry schedule (for rates and client data source tables)

[=ct_document.id]

ct_flags int 4 yes header options:

1 → Comment available

2 → long description available

ct_icon int 4 yes icon (none = default icon)

[*=ct_icon.id]

ct_retrieval_book int 4 yes data retrieval book (for rates and client data source tables)

[=ct_book.id]

id int 4 no idx

ldesc1-6 nvarchar 120 yes

name nvarchar 12 yes

opobject_man_id int 4 yes ID of the reporting object Manager when there is data associated with a reporting object

owner_site smallint 2 yes

phys_name nvarchar 30 yes SQL name of the associated data table, or root of the data tables names when they are partitioned

SAP Financial Consolidation Database Schema GuideStructure CONFIDENTIAL 13


progid_client nvarchar 80 yes COM client manager for non-partitioned tables: CtCore.CtGenericDataSourceClient.1

progid_server nvarchar 80 yes COM server manager for non-partitioned tables: CtCore.CtGenericDataSourceClient.1

sdesc1-6 nvarchar 30 yes

security columns

1.1.2 ct_datasource_dim: dimensions associated with data sources


aggregatable bit 1 yes true = data that can be totaled depending on the dimension

ct_order int 4 yes order of the dimension in the user interface

datasource int 4 yes data source using the dimension

[=ct_datasource.id]

detail int 4 yes

dimension int 4 yes dimension used

[=ct_dimension.id]

header bit 1 yes true = header dimension

header_rank int 4 yes rank of header dimensions

hidden bit 1 yes hidden dimension

interlace_with int 4 yes

nullable bit 1 yes true = accepts the null value

optional bit 1 yes true = analysis dimension

particular bit 1 yes true = differentiation dimension


Structure


phys_name nvarchar 30 yes column name in the data table (null for dimensions in the partition table for partitioned data sources)

1.1.3 ct_datasource_indexes: indexes associated with data sources

Column Type Len. Null. Comment

base_name nvarchar 13 yes base index name used for index name + 4 character unique identifyer

columns nvarchar 100 yes Comma delimited list of indexed columns

datasource int 4 yes uidx1

data source using the index

[=ct_datasource.id]

is_ascending bit 1 yes true = ascending index values

is_clustered bit 1 yes true = clustered index

is_custom bit 1 yes true = client created index

is_unique bit 1 yes true = unique index

partition int 4 yes uidx1

null = all partitions

not null = specific paritions

rank int 4 yes uidx1

index number of datasource

table_scope int 4 yes future use


1.1.4 ct_datasource_prop: properties associated with data sources


ct_order int 4 yes order of the property in the user interface

datasource int 4 yes data source using the property [=ct_datasource.id]

phys_name nvarchar 30 yes column name in the data table

property int 4 yes property used [=ct_ds_property.id]

1.1.5 ct_dimension: data source dimensions


ct_icon int 4 yes icon (none = default icon) [*=ct_icon.id]

id int 4 no uidx




rank int 4 yes not used

reftable int 4 yes reference able from which the dimension takes its values [=ct_reftable.id]


security columns

1.1.6 ct_ds_property: data source properties


ct_default_value nvarchar 600 yes default value


Structure


ct_flags int 4 yes property option

1 → compulsory

2 → sensitive

ct_format nvarchar 100 yes default format (not used)


ct_length int 4 yes length for strings

id int 4 no uidx




prop_type int 4 yes type of property

0 → integer

1 → real

2 → string

3 → date

4 → period

5 → reference table value

6 → binary

7 → boolean

8 → text

9 → rate


security columns


1.2 Reference tables

1.2.1 ct_reftable: reference tables


ct_flags int 4 yes reference table option:

1 → values with an extra long description

2 → values with comments

4 → the table is hidden

8 → the table cannot be filtered

16 → the table cannot be changed or completed in the structure


ct_type int 4 no type of reference table

0 → integer

4 → period

5 → values table

id int 4 no uidx

lastdatainsertdate datetime 8 yes

lastdataremovedate datetime 8 yes

lastdataupdatedate datetime 8 yes


man_callback_progid_client

nvarchar 80 yes not used in 7.4

man_callback_progid_server

nvarchar 80 yes not used in 7.4

manager int 4 no ID of the associated reference values manager which is identical to the ID of the table for customized tables

manager_progid_client nvarchar 80 yes COM client manager


Structure


manager_progid_server

nvarchar 80 yes COM server manager



phys_name nvarchar 30 yes SQL name of the reference table (for values tables)


security columns

1.2.2 ct_charac: reference table characteristics


available_hierarchy int 4 yes Indicates if the characteristic is available in hierarchies or not: 0 not available, 1 available

ct_default_value int 4 yes default value (only for direct characteristics) [*=dst_reftable.physname.id]

ct_flags int 4 yes characteristic option (only for direct characteristics):

1 → automatic generation of the OLAP pivot (not used)

2 → compulsory

4 → sensitive


ct_order int 4 yes order of the characteristic in the user interface



dst_reftable int 4 yes reference table for which the link is targeted and in which the characteristic takes its values (only for direct characteristics) [*=ct_reftable.id]

entry_filter int 4 yes filter for entering values (only for direct characteristics) [*=ct_filter.id]

id int 4 no uidx




phys_name nvarchar 30 yes column name of the reference table for which a characteristic has been defined (only for direct or first level characteristics)


security columns

src_reftable int 4 yes reference table from which the link originates and for which the characteristic has been defined (only for direct characteristics) [*=ct_reftable.id]

1.2.3 ct_charac_path: path of characteristics (level > 1)


ct_direct_charac int 4 yes ID of the direct characteristic used [ct_charac.id]

ct_order int 4 yes order of the path

ct_sub_charac int 4 yes ID of the indirect characteristic for which the path has been defined [ct_charac.id]


Structure

1.2.4 ct_charac_dim_visibility: characteristics displayed depending on dimensions (not used)


charac int 4 yes ID of the characteristic [=ct_charac.id]

dimension int 4 yes ID of the dimension [=ct_dimension.id]

1.2.5 ct_rt_property: reference table properties


ct_default_value nvarchar 600 yes default value

ct_flags int 4 yes property option

1 → compulsory

2 → sensitive

ct_format nvarchar 100 yes default format (not used)


ct_length int 4 yes length for strings

ct_order int 4 yes order of the column in the user interface

id int 4 no uidx




phys_name nvarchar 30 yes column name in the table



prop_type int 4 yes type of property

0 → integer

1 → real

2 → character string (from 1 to 4000)

3 → date

7 → boolean

reftable int 4 yes reference table of the property (not used)


security columns -- -- --

1.3 Filters

1.3.1 ct_filter: reference table filters


cdesc image 16 yes

context int 4 yes filter application context

1 → schedule

2 → category scenario

4 → administration

8 → operation

id int 4 no uidx




reftable int 4 yes reference table where the filter is applied [=ct_reftable.id]



Structure



1.3.2 ct_filter_expr: filter definition


id int 4 no uidx filter defined [=ct_filter.id]

param_expr image 16 yes expression of the filter (serialized)

1.3.3 ct_filter_dim_visibility: filters displayed depending on dimensions (not used)


dimension int 4 yes dimension where the filter is visible

filter int 4 yes filter displayed for all dimensions

1.3.4 ct_filter_result: filters displayed results


filter_id int 4 yes cidx idx1

value_id int 4 yes idx1


1.4 Miscellaneous

1.4.1 ct_icon: icons associated with structural items


icon image 16 no icon (serialized)

id int 4 no uidx

1.4.2 ct_period_month: table of translatable period descriptions

Column Type Len Null Comment

ct_ldesc_format int 4 yes date format for the long description:

1 → month preceding year

2 → year preceding month

ct_ldesc_separator nvarchar 120 yes date separator for the long description

ct_month01_ldesc nvarchar 120 yes

ct_month01_sdesc nvarchar 30 yes














Structure












ct_sdesc_format int 4 yes date format for the short description:

1 → month preceding year

2 → year preceding month

ct_sdesc_separator nvarchar 120 yes date separator for the short description

id int 4 no uidx

reftable int 4 yes period reference table [=ct_raftable.id]

1.4.3 ct_property:


ct_default_value nvarchar 100 yes

ct_format nvarchar 100 yes

ct_icon int 4 yes

ct_length int 4 yes

ct_optional int 4 yes

id int 4 no






prop_type int 4 yes

security_columns -- -- yes


Structure

2 Product reference tables

2.1 Associated with amounts

2.1.1 ct_phase: category reference table


cdesc image 16 yes

id int 4 no ucidx


name nvarchar 12 no idx

owner_site smallint 2 no

planning_fn bit 1 yes

planning_use bit 1 yes Indicates if the category supports Excel Web schedules



xdesc1-6 nvarchar 253 yes

2.1.2 ct_variant: consolidation variant reference table


cdesc image 16 yes

id int 4 no ucidx


name nvarchar 12 yes idx





SAP Financial Consolidation Database Schema GuideProduct reference tables CONFIDENTIAL 27

2.1.3 ct_scope_code: scope reference table


cdesc image 16 yes

global_integr_threshold

int 4 yes full consolidation threshold (default)

id int 4 no uidx

integr_rate_computed_as_max

int 4 yes consolidation rate calculation mode (default):

0 → total ownership interest

1 → maximum total ownership interest and share of profits

integr_threshold int 4 yes consolidation threshold (default)


management_scope int 4 yes type of scope (default):

0 → statutory

1 → reporting

mother_id int 4 yes main parent company (default) [*=ct_entity.id]



proportional_integr_threshold

int 4 yes proportional consolidation threshold (default)



2.1.4 ct_entity: reporting unit reference table


cdesc image 16 yes

company int 4 yes company characteristic [=ct_entity.id]


Product reference tables


country int 4 yes country characteristic [=ct_country.id]

curncy int 4 yes currency characteristic [=ct_curncy.id]

id int 4 no ucidx







2.1.5 ct_curncy: currency reference table


cdesc image 16 yes

decimals int 4 yes number of digits after the decimal property

id int 4 no uidx







2.1.6 ct_account: account reference table


2.1.7 ct_flow: flow reference table


balanced int 4 yes balanced flow property

cdesc image 16 yes

id int 4 no ucidx







2.1.8 ct_nature: audit ID reference table


cdesc image 16 yes

consonat int 4 yes type of data entry level characteristic [=ct_consonat.id]

curncynat int 4 yes type of data entry currency characteristic [=ct_curncynat.id]

docrestat int 4 yes adjustments via schedules

entryallwd int 4 yes authorized journal entries property

id int 4 no ucidx



natlvl int 4 yes audit ID level characteristic [=ct_nat_level.id]

opbalnat int 4 yes opening balance audit ID characteristic [=ct_nature.id]


scoperate int 4 yes apply consolidation rate property







2.1.9 ct_techorig: technical origin reference table


cdesc image 16 yes

id int 4 no ucidx






techoriglvl int 4 yes level of technical origin characteristic [=ct_techoriglvl.id]

techtype int 4 yes type of technical origin characteristic [=ct_techtype.id]


2.1.10 ct_mu : reference table for Management Unit dimension


cdesc image 16 yes

id int 4 no ucidx








2.1.11 ct_scope_entity_custom_prop: custom property for the scope


cdesc image 16 yes

id int 4 no ucidx







2.2 Associated with other data sources

2.2.1 ct_scope_version: scope version reference table


cdesc image 16 yes

id int 4 no ucidx







2.2.2 ct_portfl_code: investment code reference table


cdesc image 16 yes

closure_flow_id int 4 yes source data flow (default)




control_threshold int 4 yes control threshold (default)

direct_auto_holding int 4 yes management of direct self-held stock (default)

held_cap_dim_id int 4 yes capital dimension for subsidiary (df)

held_portfl_dim_id int 4 yes investment dimension for subsidiary (df)

id int 4 no uidx



natures_id int 4 yes source data audit ID filter (default)

outer_entity_id int 4 yes non-group company (default)

owner_cap_dim_id int 4 yes capital dimension for parent (df)

owner_portfl_dim_id int 4 yes investment dimension for parent (df)


phase_id int 4 yes source data category (default)



shares_cap_accnts_id int 4 yes capital account in number of stocks (df)

shares_hld_accnts_id int 4 yes investment account in number of stocks (d)

votes_cap_accnts_id int 4 yes capital account in number of voting rights (default)

votes_hld_accnts_id int 4 yes investment account in number of voting rights (df)



votes_prop_with_shares

int 4 yes manages voting rights (default):

0 → voting rights are not proportionate to stocks

1 → voting rights are proportionate to stocks

2.2.3 ct_exrate_version: conversion rate version reference table


cdesc image 16 yes

id int 4 no uidx







2.2.4 ct_exrate_type: conversion rate type reference table


cdesc image 16 yes

id int 4 no uidx









2.2.5 ct_taxrate_type: tax rate type reference table


cdesc image 16 yes

id int 4 no uidx







2.2.6 ct_country: country reference table


cdesc image 16 yes

id int 4 no cuidx







2.2.7 ct_var_interco: intercompany variant reference table


cdesc image 16 yes

id int 4 no ucidx









2.2.8 ct_action_context: Package amount trace context


cdesc image 16 yes

id int 4 no ucidx







2.3 Associated with characteristics

2.3.1 ct_sign: account sign reference table


cdesc image 16 yes

id int 4 no uidx









2.3.2 ct_class: account class reference table


cdesc image 16 yes

id int 4 no ucidx







2.3.3 ct_nat_level: audit ID level reference table


cdesc image 16 yes

id int 4 no ucidx







2.3.4 ct_curncynat: currency audit ID type reference table


cdesc image 16 yes

id int 4 no uidx









2.3.5 ct_consonat: audit ID loading restriction reference table


cdesc image 16 yes

id int 4 no







2.3.6 ct_techtype: technical origin type reference table


cdesc image 16 yes

id int 4 no ucidx









2.3.7 ct_techoriglvl: technical origin level reference table


cdesc image 16 yes

id int 4 no ucidx








3 Amounts

3.1 Package amounts

3.1.1 ct_pkref: partitioning of package amounts


id int 4 no uidx ID of the corresponding partitioned table

phase int 4 yes category dimension [=ct_phase.id]

updper int 4 yes data entry period dimension

3.1.2 ct_pkPPPP: package amounts data source


accnt int 4 no account dimension [=ct_account.id]

amount float 8 yes package amount property

ctshare int 4 no share dimension [*=ct_entity.id]

curncy int 4 no currency dimension [=ct_curncy.id]

data_comment nvarchar 2000 yes comments on data property

entity int 4 no reporting unit dimension [=ct_entity.id]

entorig int 4 no original reporting unit dimension [=ct_entity.id]

enumber int 4 no journal entry number dimension

flow int 4 no flow dimension [=ct_flow.id]


Amounts


globorig int 4 no geographical origin dimension [=ct_site.id]

journal int 4 no ledger dimension [*=ct_journal.id]

nature int 4 no audit ID dimension [=ct_nature.id]

partner int 4 no partner dimension [*=ct_entity.id]

period int 4 no period dimension

techorig int 4 no technical origin dimension [=ct_techorig.id]

version int 4 yes package version

3.1.3 ct_pbref : partitioning of published packages amouts


id int 4 no uidx1 Identifier



3.1.4 ct_pbPPPP: published package amounts data source








SAP Financial Consolidation Database Schema GuideAmounts CONFIDENTIAL 41











3.1.5 ct_pbdref : partitioning of historical published packages amouts





3.1.6 ct_pb_deltaPPPP: historical published package amounts data source





Amounts




delta float 8 yes








newamount float 8 yes package amount property




vernumber int 4 no

3.2 Preconsolidated amounts

3.2.1 ct_pcref: partitioning of preconsolidated amounts







3.2.2 ct_pcPPPP: preconsolidated amounts data source


accnt int 4 account dimension [=ct_account.id]


ctshare int 4 share dimension [*=ct_entity.id]

curncy int 4 currency dimension [=ct_curncy.id]


entity int 4 reporting unit dimension [=ct_entity.id]

entorig int 4 original reporting unit dimension [=ct_entity.id]

enumber int 4 journal entry number dimension

flow int 4 flow dimension [=ct_flow.id]

globorig int 4 geographical origin dimension [=ct_site.id]

journal int 4 ledger dimension [*=ct_journal.id]

nature int 4 audit ID dimension [=ct_nature.id]

partner int 4 partner dimension [*=ct_entity.id]

period int 4 period dimension

techorig int 4 technical origin dimension [=ct_techorig.id]


Amounts

3.2.3 ct_pcdref : partitioning of preconsolidated packages amouts delta data source





3.2.4 ct_pc_deltaPPPP: preconsolidated packages amouts delta data source






delta float 8 yes








newamount float 8 yes






vernumber int 4 no

3.3 Consolidated amounts

3.3.1 ct_coref: partitioning of consolidated amounts


curncy int 4 yes consolidation currency dimension [=ct_curncy.id]

id int 4 no idx ID of the corresponding partitioned table


scope int 4 yes scope dimension [=ct_scope_code.id]


variant int 4 yes variant dimension [=ct_variant.id]

3.3.2 ct_coPPPP: consolidated amounts




consamount float 8 yes consolidated amount property


Amounts


convamount float 8 yes converted amount property













rollup int 4 no ID of the rollup refrenced in ct_hierarchy_content

rollup_partner int 4 no detail of partner


mu int 4 no management unit dimension [=ct_mu.id]

pmu int 4 no partner management unit dimension [=ct_mu.id]

rollup2 int 4 no ID of the secondary rollup refrenced in ct_hierarchy_content

rollup_partner2 int 4 no detail of partner for secondary rollup


3.4 Intercompany amounts

3.4.1 ct_intercos: intercompany data source


accnt int 4 yes account dimension [=ct_account.id]

buyer int 4 yes buyer dimension [=ct_entity.id]

buyer_amount float 8 yes amount in original buyer currency property

buyer_convamount float 8 yes converted buyer amount property

conscur int 4 yes consolidation currency dimension [=ct_curncy.id]

ctshare int 4 yes share dimension [*=ct_entity.id]

curncy int 4 yes currency dimension [=ct_curncy.id]

differential float 8 yes converted amount difference property

entity int 4 yes reporting unit dimension [=ct_entity.id]

entorig int 4 yes original reporting unit dimension [=ct_entity.id]

enumber int 4 yes journal entry number dimension

flow int 4 yes flow dimension [=ct_flow.id]

globorig int 4 yes geographical origin dimension [=ct_site.id]

inter_rule int 4 yes reconciliation rule dimension [=ct_interrule.id]

inter_subrule int 4 yes reconciliation block dimension

journal int 4 yes ledger dimension [*=ct_journal.id]

mu int 4 no management unit dimension [=ct_mu.id]


Amounts


nature int 4 yes audit ID dimension [=ct_nature.id]

partner int 4 yes partner dimension [*=ct_entity.id]

period int 4 yes period dimension


pmu int 4 no Partner management unit dimension [=ct_mu.id]

reconciliation int 4 yes reconciliation variant dimension [=ct_var_interco.id]

scope int 4 yes scope dimension [=ct_scope_code.id]

seller int 4 yes seller dimension [=ct_entity.id]

seller_amount float 8 yes amount in original seller currency property

seller_convamount float 8 yes converted seller amount property

techorig int 4 yes technical origin dimension [=ct_techorig.id]


variant int 4 yes variant dimension [=ct_variant.id]

3.5 Opening balances

3.5.1 ct_opbalref: partitioning of opening balance data







3.5.2 ct_opbalPPPP: opening balance data source


accnt int 4 yes account dimension [=ct_account.id]


ctshare int 4 yes share dimension [*=ct_entity.id]

curncy int 4 yes currency dimension [=ct_curncy.id]

entity int 4 yes reporting unit dimension [=ct_entity.id]

entorig int 4 yes original reporting unit dimension [=ct_entity.id]

enumber int 4 yes journal entry number dimension

flow int 4 yes flow dimension [=ct_flow.id]

globorig int 4 yes geographical origin dimension [=ct_site.id]

journal int 4 yes ledger dimension [*=ct_journal.id]

nature int 4 yes audit ID dimension [=ct_nature.id]

partner int 4 yes partner dimension [*=ct_entity.id]

period int 4 yes period dimension

techorig int 4 yes technical origin dimension [=ct_techorig.id]

type_entry int 4 yes type of journal entry property (technical)


Amounts

4 Operation objects associated with amounts

4.1 Package amounts

4.1.1 ct_pack: packages


allow_early_publishing smallint 2 yes advanced publication authorized

approbation_level int 4 yes current approval level of the package in the workflow. It indicates the users who are authorized to access the package at this stage of the workflow.

canhave_changereport bit 1 yes Is package change report available for this package? 0 means false, otherwise true.

cdesc image 16 yes

commented bit 1 yes comments available

control_execution_author_id

int 4 yes user who ran the controls [*=ct_user.id]

control_execution_date

datetime 8 yes date the controls were run

control_execution_recipient_id

int 4 yes site where the controls were run [*=ct_recipient.id]

control_level_id int 4 yes validating control level [*=ct_level.id]

control_level_inhibit_valid

smallint 2 yes blocking controls

control_level_reached_id

int 4 yes control level reached [*=ct_level.id]

control_set_id int 4 yes set of controls applied [*=ct_ctrl_set.id]

SAP Financial Consolidation Database Schema GuideOperation objects associated with amounts CONFIDENTIAL 51


ctrl_level_reached_pub int 4 yes Control level that packages published in advance must pass in order to be integrated automatically after publication

ctrl_level_reached_transfer

int 4 yes Control level that packages published in advance must pass in order to be integrated automatically after publication

data_commented bit 1 yes at least one comment on data available

effective_lock smallint 2 yes

effective_lock_author_id

int 4 yes

effective_lock_date datetime 8 yes

effective_lock_recipient_id

int 4 yes

entity_id int 4 yes cidx1 reporting unit [=ct_entity.id]

entry_save_version int 4 yes Backup version of journal entries

exist_emb_files bit 1 yes Attachments exist

first_publishing_author_id

int 4 yes Author of the first publication of the package.

first_publishing_date datetime 8 yes Date of the first publication of the package.

first_publishing_recipient_id

int 4 yes Site of the first publication of the package.

framework_broadcast_date

datetime 8 yes publication date of category scenario used

framework_version_id int 4 yes version of category scenario used [=ct_framework_version.id]

group_comment_id int 4 yes group comment [*=ct_pack_group_comment.id]

group_commented bit 1 yes group comment available

id int 4 no uidx


Operation objects associated with amounts


import_date datetime 8 yes date of the import

import_author_id int 4 yes user performing the import

input_currency_id int 4 yes data entry currency [=ct_curncy.id]

input_recipient_id int 4 yes data entry site [*=ct_recipient.id]

input_restriction_id int 4 yes data entry restrictions [*=ct_input_restriction.id]

input_start_author_id int 4 yes user who started data entry [*=ct_user.id]

input_start_date datetime 8 yes data entry start date

input_start_recipient_id

int 4 yes site where data entry was started [*=ct_recipient.id]

input_techorig_restriction_id

int 4 yes [=ct_techorig.id]

integrate_after_publication

int 4 yes Automatic integration after publication

integrate_after_transfer

int 4 yes Automatic integration after receipt of the package

integration_author_id int 4 yes user who integrated [*=ct_user.id]

integration_date datetime 8 yes integration date

integration_recipient_id

int 4 yes integration site [*=ct_recipient.id]

internet_input_folder_id

int 4 yes specific internet folder [*=ct_folder.id]

last_protecting_author_id

int 4 yes user who protected the package

last_protecting_date datetime 8 yes date of protection

last_protecting_recipient_id

int 4 yes site where the protection was performed

late bit 1 yes late

op_bal_amount_count int 4 yes number of opening data loaded

op_bal_conso_currency

int 4 yes consolidation currency of opening balance data [*=ct_curncy.id]



op_bal_manager_id int 4 yes manages opening balance data

-523588 à preconsolidated data

-523538 à consolidated data

op_bal_phase_id int 4 yes category of opening balance data [*=ct_phase.id]

op_bal_scope_code_id int 4 yes scope of opening balance data [*=ct_scope_code.id]

op_bal_update_period_id

int 4 yes data entry period of opening balance data

op_bal_version_id int 4 yes variant of opening balance data [*=ct_variant.id]

opening_balances smallint 2 yes opening balance data available


pack_approbation_author

int 4 yes the authorized user who approved the package in the workflow [=ct_user.id]

pack_availability_recipient

int 4 yes the package is not available for this user at this stage of the workflow [=ct_user.id]

pack_control_status smallint 2 yes control status:

1 → not run

2 → no data

3 → valid

4 → warning

5 → non-blocking

6 → blocking

pack_model_date datetime 8 yes date the opening package was generated

pack_model_indicator bit 1 yes

pack_model_load_author_id

int 4 yes user who initialized the package [*=ct_user.id]




pack_model_load_date datetime 8 yes date the package was initialized

pack_model_load_recipient_id

int 4 yes site where the package was initialized [*=ct_recipient.id]

pack_model_reception_author_id

int 4 yes user who received the opening package [*=ct_user.id]

pack_model_reception_rcpt_id

int 4 yes site where the opening package was received [*=ct_recipient.id]

pack_model_recipient_id

int 4 yes site where the opening package was created [*=ct_recipient.id]

pack_model_send_date

datetime 8 yes date the opening package was sent

pack_publishing_cutoff_date

datetime 8 yes advanced publication deadline

pack_reception_author_id

int 4 yes user who received the package [*=ct_user.id]

pack_reception_date datetime 8 yes date the package was received

pack_reception_recipient_id

int 4 yes site where the package was received [*=ct_recipient.id]

pack_rule_status smallint 2 yes

pack_user_list_id int 4 yes reference ID of the package in the table listing the authorized users [=ct_pack_user.pack_id]

pack_users_restriction bit 1 yes equal to 1 if the package has a list of users authorized to access it

package_security int 4 yes

phase_id int 4 yes cidx1 category [=ct_phase.id]

protect_flow_filter_id int 4 yes filter of read-only flows [*=ct_filter.id]

protect_flow_filter_method

int 4 yes flow selection method:

4 à several values

8 à filter



protect_flow_if_op_bal smallint 2 yes flows read-only if opening balances

protect_period_filter_id

int 4 yes filter of read-only periods [*=ct_filter.id]

protect_period_filter_method

int 4 yes period selection method:

4 → several values

8 → filter

publishing_author_id int 4 yes user who published [*=ct_user.id]

publishing_comment nvarchar 8000 yes Comment on the publication.

publishing_date datetime 8 yes publication date

publishing_lock int 4 yes locked on publication:

0 → none

1 → full

2 → locked integration

publishing_mode int 4 yes publication mode:

0 → none

65536 → standard

131072 → special permission

262144 → advance

publishing_recipient_id int 4 yes publication site [*=ct_recipient.id]

reporting_hierarchy_date

datetime 8 yes

restr_on_document smallint 2 yes data entry restrictions applied to schedules

restr_on_local_man_entry

smallint 2 yes data entry restrictions applied to local journal entries

restr_on_precons_manual_entry

smallint 2 yes data entry restrictions applied to central journal entries

rule_execution_author_id

int 4 yes user who ran the package rules [*=ct_user.id]




rule_execution_date datetime 8 yes date the package rules were run

rule_execution_recipient_id

int 4 yes site where the package rules were run [*=ct_recipient.id]

rule_set_id int 4 yes set of package rules [*=ct_ruleset.id]

save_version int 4 yes Backup version


status int 4 yes package status:

0 → n.a.

1 → empty

2 → changed

4 → published

8 → integrated

s4h_timestamp datetime 8 yes max timestamp of data imported from S/4HANA source

sh4_datalink_def int 4 yes ID of the Data Link definition used to import data from S/4HANA

transaction_mutex int 4 yes Technical column used to manage the package backup in multi-user mode

transfer_recipient_id int 4 yes transfer site [*=ct_recipient.id]

update_data_author_id

int 4 yes last user who changed the data [*=ct_user.id]

update_data_date datetime 8 yes date the data was last changed

update_data_recipient_id

int 4 yes site where the data was last changed [*=ct_recipient.id]

update_period_id int 4 yes cidx1 data entry period

update_recipient_id int 4 yes site where the package was last changed [*=ct_recipient.id]

user_control_level int 4 yes



validity_check smallint 2 yes validity:

0 → not run

1 → valid

2 → invalid

windows_input_folder_id

int 4 yes windows and internet folder [=ct_folder.id]

workflow bit 1 yes equal to 1 if the authorized users are organized in workflow hierarchies

workflow_levels_count int 4 yes Number of workflow user levels configured for working in the package

4.1.2 ct_pack_workflow: list of users authorized to use the package


id int 4 no uidx1


pack_lnk_id int 4 yes uidx2 package or Reporting Set ID related to the users defined in the Workflow

reportingset_id int 4 yes uidx2 The reporting unit owner of the workflow

user_id int 4 yes uidx2 ID of users authorized to work in a package or defined in a Reporting Set

user_level int 4 yes uidx2 user hierarchy level



4.1.3 ct_pack_embedded_file: package attachments


file_name nchar 253 yes Attachment name

file_serial image 16 yes Attachment contents

file_size int 4 yes Size in KB of attachment

file_type nchar 120 yes Attachment file extension

id int 4 no uidx ID given to the package attachment

ownerobject_id int 4 yes idx Package that owns attachment

4.1.4 ct_pack_period_trans: settings for package periods


id int 4 no uidx corresponding package [=ct_pack.id]

period_translations image 16 yes definition for converting the opening balance period (serialized)

4.1.5 ct_pack_protect_period: settings for protecting package periods



protect_period_filter image 16 yes list of protected periods (serialized)


4.1.6 ct_pack_protect_flow: settings for protecting package flows


id int 4 yes uidx corresponding package [=ct_pack.id]

protect_flow_filter image 16 yes list of protected flows (serialized)

4.1.7 ct_pack_lock: package lock


entity_id int 4 yes cidx2 package reporting unit [=ct_entity.id]

id int 4 no uidx1

key_hole nvarchar 60 yes package lock


phase_id int 4 yes cidx2 package category [=ct_phase.id]

publishing_key nvarchar 60 yes key enabling the package to be published by special permission if the user does not have the relevant access right. The key is valid until the next publication.

update_period_id int 4 yes cidx2 package data entry period



4.1.8 ct_journal_pack: journal entry ledgers associated with packages (technical table)


control_status int 4 yes ledger status:

1 → empty

2 → automatic journal entry ledger

4 → run automatic journal entry ledger

8 → opening balance ledger

16 → controls not run

32 → no data

64 → valid controls

128 → warning

256 → non-blocking

512 → blocking

1024 → imbalanced

2048 → n.a.

empty int 4 yes empty

entity_id int 4 yes cidx1 package reporting unit [=ct_entity.id]

id int 4 no uidx

journal_id int 4 yes ledger [=ct_journal.id]

last_entry_number int 4 yes last journal entry number assigned

pack_id int 4 yes obsolete

phase_id int 4 yes cidx1 package category [=ct_phase.id]

updper_id int 4 yes cidx1 package data entry period


4.1.9 ct_pk_entry: package journal entry headers


control_status int 4 yes journal entry control status:

1 → valid

2 → invalid

3 → category scenario changed

4 → no validity

curncy_id int 4 yes currency [=ct_curncy.id]


entry_comment nvarchar 253 yes journal entry short comments

entry_label nvarchar 120 yes description

frmwk_ver_id int 4 yes version of category scenario used [=ct_framework_version.id]

globorig int 4 yes geographical origin [=ct_site.id]

id int 4 no uidx

journal_id int 4 yes cidx2 ledger [=ct_journal.id]

model_attached int 4 yes uses the journal entry template

model_id int 4 yes journal entry template

nature_id int 4 yes audit ID [=ct_nature.id]


pack_rule_id int 4 yes generating package rule [*=ct_packrule.id]

pack_sql_rule_id int 4 yes generating SQL rule [*=ct_sqlrule.id]

period_id int 4 yes period


reversing_entry_id int 4 yes reversing journal entry




revert_entry_id int 4 yes reversed journal entry

rule_name nvarchar 12 yes generating rule code (automatic journal entry)

rule_type nvarchar 12 yes type of generating rule (automatic journal entry)

save_version int 4 yes cidx2journal entry backup version


serial_entry_data image 16 yes data display settings (serialized)

subscribe_id int 4 yes recurring journal entry

type_entry int 4 yes type of journal entry:

1 → single-sided

2 → double-sided

3 → not authorized


user_entry_number int 4 yes cidx2 journal entry number (ó«amounts ».enumber)

valid_entry_date datetime 8 yes journal entry validity date

validity_status Int 4 yes journal entry validity:


32 → no data


128 → warning


512 → blocking

1024 → imbalanced

2048 → n.a.


4.2 Preconsolidated amounts

4.2.1 ct_preconsopack: preconsolidated package headers



cdesc image 16 yes

commented bit 1 yes comment available



















int 4 yes






int 4 yes







id int 4 no uidx











int 4 yes automatic integration after publication


int 4 yes automatic integration after receipt of the package





integration_version int 4 yes version number of the last integration





late bit 1 yes late





-523588 → preconsolidated data

-523538 → consolidated data






opening_balances smallint 2 yes opening balance available



1 → not run

2 →à no data

3 → valid

4 → warning

5 → non-blocking

6 → blocking





































8 → filter







8 → filter




0 → none

1 → full



0 → none

65536 → standard


262144 → advance



date 8 yes

















0 → n.a.

1 → empty

2 → published

4 → changed

8 → integrated










0 → not run

1 → valid

2 → invalid





4.2.2 ct_preconsopack_period_trans: settings for package periods (preconsolidated level)


id int 4 no uidx corresponding integrated package [=ct_preconsopack.id]


4.2.3 ct_preconsopack_protect_flow: settings for protecting package flows (preconsolidated)




4.2.4 ct_preconsopack_protect_period: settings for protecting package periods (pc)






4.2.5 ct_preconsopack_histo : history of preconsolidated package headers


action_context int 4 yes Action context: Receiving, Publication, Integration.

entity_id int 4 yes cidx2 reporting unit dimension [=ct_entity.id]


integration_author_id int 4 yes Author of the package integration.

integration_date datetime 8 yes Date of the package integration when you publish the package.


int 4 yes Site of the package integration.

integration_version int 4 yes cidx2 version number of the last integration


phase_id int 4 yes cidx2 category dimension [=ct_phase.id]

publishing_author_id int 4 yes Author of the last publication of the package when you perform a package integration of this version.

publishing_date datetime 8 yes date of the last publication of the package when you perform a package integration of this version.

publishing_recipient_id int 4 yes Site of the last publication of the package when you perform a package integration of this version.

received_date datetime 8 yes Received on: The date you receive the preconsolidated data.

received_from_recipient_id

int 4 yes Received from: The Site that sent the preconsolidated data.

update_period_id int 4 yes cidx2 data entry period dimension


4.2.6 ct_publishedpack : published packages



entity_id int 4 yes cidx2 reporting unit dimension [=ct_entity.id]







phase_id int 4 yes cidx2 category dimension [=ct_phase.id]

publishing_author_id int 4 yes Author of the last publication of the package.

publishing_comment nvarchar 8000 yes Comment on the package publication.

publishing_date datetime 8 yes Date of the last publication of the package.

publishing_recipient_id int 4 yes Site of the last publication of the package.

publishing_version int 4 yes cidx2 Version number of the last publication.

received_date datetime 8 yes Received on: The date you receive the preconsolidated data.


int 4 yes Received from: The Site that sent the published or integrated data.

update_period_id int 4 yes cidx2 data entry period dimension



4.2.7 ct_publishedpack_histo: history of published packages



entity_id int 4 yes cuidx2 reporting unit dimension [=ct_entity.id]







phase_id int 4 yes cuidx2 category dimension [=ct_phase.id]

publishing_author_id int 4 yes Author of the last publication of the package.

publishing_comment nvarchar 8000 yes Comment on the publication action.

publishing_date datetime 8 yes Date of the last publication of the package.

publishing_recipient_id int 4 yes Site of the last publication of the package.

publishing_version int 4 yes cuidx2 Version number of the last publication.

received_date datetime 8 yes Received on: The date you receive preconsolidated data.


int 4 yes Received from: The Site that sent the published or integrated data.

saving_date datetime 8 yes Saving package date

update_period_id int 4 yes cuidx2 data entry period dimension


4.2.8 ct_pc_entry: preconsolidated journal entry header table


amount_level int 4 yes amount level

control_status int 4 yes journal entry control status:

1 → valid

2 → invalid


4 → no validity


curncyconso_id int 4 yes consolidation currency




exist_emb_files int 4 yes Existence of attachments (1: attachment(s) exist, 0: no journal entry attachments)


globorig int 4 yes cidx1 geographical origin [=ct_site.id]

id int 4 no uidx

journal_id int 4 yes cidx1 ledger [=ct_journal.id]

model_attached int 1 yes uses the journal entry template











posting_date datetime 8 yes Date of posting

preconso_rule_id int 4 yes generating preconsolidation rule [*=ct_preconsrule.id]

preconso_sql_rule_id int 4 yes generating SQL rule [*=ct_sqlrule.id]






serial_entry_data image 16 yes data display settings and validity depending on scope and variant (serialized)

status Int 4 yes Status of entry. Types are:

0 → modified

1 → posted

2 → protected


techorig int 4 yes cidx1 technical origin [=ct_techorig.id]

type_entry int 4 yes type of journal entry:

1 → single-sided

2 → double-sided




under_scope_mother_entity_id

int 4 yes linked parent company [*=ct_entity.id]


user_entry_number int 4 yes cidx1 journal entry number (ó« amounts ».enumber)


validity_status int 4 yes journal entry validity:

0 → valid

1 → valid but with some incomplete lines

2 → valid but with some invalid lines

4 → not equilibrated

8 → not equilibrated on flow

16 → not valid against framework controls

24 → 8 and 16

32 → no data


128 → warning


512 → blocking

1024 → imbalanced

2048 → n.a.



4.2.9 ct_mje_wrkflw_notif_reg : definition of entries notifications


action int 4 yes Actions registered:

1:create

2:modify

4:post

8:unpost

16:protect

32:unprotect

64:delete

id int 4 no uidx

journal_id int 4 yes cidxuidx2 ledger [=ct_journal.id]

phase_id int 4 yes cidxuidx2 category dimension [=ct_phase.id]

site_id int 4 yes cidxuidx2 site [=ct_site.id]

updper_id int 4 yes cidxuidx2 data entry period dimension

user_id int 4 yes uidx2 ID of user who have subscribed to the notification

4.3 Consolidated amounts

4.3.1 ct_conso_def: consolidation definition


archive_date datetime 8 yes Archive date

cdesc image 16 yes

coeff float 8 yes coefficient for multiplying thresholds



context int 4 yes indicates that the following elements are defined:

1 → opening balances

2 → restricta data by period according to the dimensions

4 → process period after period

8 → carry forwared one period to another

16 → different category scenario than the one used in the reporting ID

32 → different opening category scenario

64 → different variant for sub-consolidations

128 → data restriction differenciated by period

256 → category scenario differenciated by period

512 → consolidation locked

curncy int 4 yes currency [=ct_curncy.id]


framework_phase int 4 yes category of category scenario used [=ct_phase.id]

framework_version int 4 yes version of category scenario used [=ct_framework_version.id]

id int 4 no uidx





linked_props smallint 2 yes indicates that the following elements exist:

1 → source period for opening balances

2 → conversion rate period

4 → conversion rate version

8 → use replacement data

16 → replacement data category

32 → replacement data entry period

64 → replacement data period

128 → forced Audit ID for replacement data

256 → scope code

512 → scope period

1024 → scope version

2048 → use secondary scope

4096 → secondary scope code

8192 → secondary scope period

16384 → secondary scope version

locked smallint 2 yes bitmap:

1 → consolidation locked

2 → consolidation and reporting locked

4 → consolidation and scope locked



main_period int 4 yes default period settings [=ct_conso_def_per.id]

opbal_curncy int 4 yes currency of opening balance data [*=ct_curncy.id]

opbal_dst_period int 4 yes source period of opening balance data

opbal_phase int 4 yes category of opening balance data [*=ct_phase.id]

opbal_scope_code int 4 yes scope of opening balance data [*=ct_scope_code.id]

opbal_updper int 4 yes data entry period of opening balance data

opbal_variant int 4 yes variant of opening balance data [*=ct_variant.id]


phase int 4 yes category [=ct_phase.id]

readentry_lastdate datetime 8 yes date the last journal entry was loaded

rollup_state smallint 2 yes Binary mask :

consolidation has run

0: without any rollup

1 : with primary rollup on Reporting Unit

2 : with primary rollup on Original Reporting Unit

4: with secondary rollup on Management Unit

8: with secondary rollup on Original Reporting Unit

rules_set int 4 yes sets of rules applied [=ct_ruleset.id]





subconso_variant int 4 yes alternative subconsolidation variant [*=ct_variant.id]

task_author int 4 yes user who performed the corresponding task [=ct_user.id]

task_date datetime 8 yes date the corresponding task was performed

task_status int 4 yes status of the corresponding task performed

0 → error

1 → task performed

2 → full processing - error

3 → full processing -success

4 → incremental processing - error

5 → incremental processing - success

updper int 4 yes data entry period

variante int 4 yes variant [=ct_variant.id]

4.3.2 ct_conso_def_per: consolidation periods definition


consodef_id int 4 yes consolidation definition to which the period is linked [=ct_conso_def.id] or 0 if default period

context int 4 yes indicates that the following are defined:

1 → replacement data

2 → secondary scope

4 → process the period



conv_period int 4 yes conversion rate period

conv_version int 4 yes conversion rate version [*=ct_exrate_version.id]

id int 4 no uidx

opbal_src_period int 4 yes source period for opening balance data


period int 4 yes period defined

replacing_nature int 4 yes audit ID forced for replacement data [*=ct_nature.id]

replacing_period int 4 yes period for replacement data

replacing_phase int 4 yes category for replacement data [*=ct_phase.id]

replacing_updper int 4 yes data entry period for replacement data

restriction image 16 yes period restrictions (serialized)

scope_code int 4 yes scope code [*=ct_scope_code.id]

scope_period int 4 yes scope period

scope_version int 4 yes scope version [*=ct_scope_version]

secondary_scope_code

int 4 yes secondary scope code [*=ct_scope_code.id]

secondary_scope_period

int 4 yes secondary scope period

secondary_scope_version

int 4 yes secondary scope version [*=ct_scope_version.id]

4.3.3 ct_consopack: consolidated package headers


curncy int 4 yes cuidx1 consolidation currency [=ct_curncy.id]




entity_id int 4 yes cuidx1 reporting unit [=ct_entity.id]

phase_id int 4 yes cuidx1 category [=ct_phase.id]

scope int 4 yes cuidx1 scope [=ct_scope_code.id]

update_period_id int 4 yes cuidx1 data entry period

variant int 4 yes cuidx1 variant [=ct_variant.id]

version int 4 yes

4.3.4 ct_conso_def_embedded_file: attachment for consolidation definition


file_name int 4 Yes Attachment name

file_serial image 16 yes Content of attachment

file_size int 4 yes Size in KB of attachment

file_type int 4 yes Attachment contents

id int 4 no uidx ID given to the consolidation attachment

ownerobject_id int 4 Yes idx Consolidation that owns attachment

4.3.5 ct_co_entry: consolidated journal entry header table


account_rollup_rule_id int 4 yes

adjust_rule_id int 4 yes generating reconciliation rule [*=ct_interrule.id]

amount_level int 4 yes amount level



conso_rule_id int 4 yes generating consolidation rule [*=ct_consrule.id]

conso_sql_rule_id int 4 yes generating SQL rule [*=ct_sqlrule.id]

control_status smallint 2 yes journal entry control status:

1 → valid

2 → invalid


4 → no validity


curncyconso_id int 4 yes cidx1 consolidation currency

entity_id int 4 yes reporting unit [=ct_entity.id]

entity_rollup_rule_id int 4 yes





globorig smallint 2 yes geographical origin [=ct_site.id]

id int 4 no uidx


model_attached bit 1 no uses the journal entry template











preconso_rule_id int 4 yes generating preconsolidation rule [*=ct_preconsrule.id]

preconso_sql_rule_id int 4 yes generating SQL rule [*=ct_sqlrule.id]





scope_id int 4 yes cidx1 scope [*=ct_scope_code.id]


serial_entry_data image 16 yes data display settings and validity depending on scope and variant (serialized)


techorig int 4 yes technical origin [=ct_techorig.id]

type_entry smallint 2 yes type of journal entry:

1 → single-sided

2 → double-sided


under_scope_mother_entity_id

int 4 yes linked parent company [*=ct_entity.id]


user_entry_number int 4 yes journal entry number (ó« amounts ».enumber)




validity_status smallint 2 yes journal entry validity:


32 → no data


128 → warning


512 → blocking

1024 → imbalanced

2048 → n.a.

variant_id int 4 yes cidx1 variant [*=ct_variant.id]

4.3.6 ct_tbl_scope: consolidation scopes associated with consolidations


absorbing_entity_id int 4 yes reporting unit acquired (outgoing acquired) [*=ct_entity.id]

cl_behaviour int 4 yes scope status at closing:

0 → not integrated

1 → parent company

2 → subsidiary

3 → sub-parent company

4 → sub-subsidiary

cl_control_rate float 8 yes group total ownership interest at closing




cl_integr_method int 4 yes consolidation method at closing:


1 → full consolidation

2 → proportional consolidation

3 → equity method

4 → sub-parent equity method

cl_integr_rate float 8 yes consolidation rate at closing

cl_interest_rate float 8 yes group share of profits at closing

cl_intermed_control_rate

float 8 yes intermediate total ownership interest

cl_intermed_integr_rate

float 8 yes intermediate consolidation rate

cl_intermed_interest_rate

float 8 yes intermediate share of profits

cl_subconso_currency_id

int 4 yes sub-consolidation currency [*=ct_curncy.id]

cl_subscope_code_id int 4 yes subscope code (sub-parent) [*=ct_scope_code.id]

cl_subscope_period_id int 4 yes subscope period (sub-parent)

cl_subscope_version_id

int 4 yes subscope version (sub-parent) [*=ct_scope_version.id]

conscur int 4 yes cidx consolidation currency dimension [=ct_curncy.id]

entity_id int 4 yes consolidated reporting unit dimension [=ct_entity.id]

loaded int 4 yes reporting unit data loaded



op_behaviour int 4 yes scope status at opening



2 → subsidiary



op_control_rate float 8 yes group total ownership interest at opening

op_integr_method int 4 yes consolidation method at opening




3 → equity method


op_integr_rate float 8 yes consolidation rate at opening

op_interest_rate float 8 yes group share of profits at opening

op_intermed_control_rate

float 8 yes intermediate total ownership interest (from scope at opening)

op_intermed_integr_rate

float 8 yes intermediate consolidation rate (from scope at opening)

op_intermed_interest_rate

float 8 yes intermediate share of profits (from scope at opening)

op_subscope_code_id int 4 yes subscope code (sub-parent) [*=ct_scope_code.id]

op_subscope_period_id

int 4 yes subscope period (sub-parent)




op_subscope_version_id


out_updper_id int 4 yes outgoing period (outgoing during period)

period_id int 4 yes period dimension processed (0 if multi-period)

phase int 4 yes cidx category dimension [=ct_phase.id]

rl_behaviour int 4 yes average scope status for rules:



2 → subsidiary



rl_integr_method int 4 yes average consolidation method for rules:




3 → equity method


scope int 4 yes cidx scope dimension [=ct_scope_code.id]

updper int 4 yes cidx data entry period dimension

variant int 4 yes cidx variant dimension [=ct_variant.id]



variation int 4 yes variation between opening and closing:

0 → no variation

1 → incoming

2 → outgoing at opening

3 → outgoing during period

4 → outgoing acquired at opening

5 → outgoing acquired during period

6 → EM/SEM to FC/PC

7 → FC/PC to EM/SEM

scope_custom_prop Int 4 yes custom property for the scope [=ct_scope_entity_custom_prop.id]

4.3.7 ct__tblglobal_scope: full consolidation scope associated with consolidations



cl_behaviour int 4 yes scope status at closing



2 → subsidiary







cl_entity_id int 4 yes linked consolidated reporting unit at closing [ct_entity.id]

cl_integr_method int 4 yes consolidation method at closing




3 → equity method










cl_level int 4 yes minimum level for original reporting unit at closing

cl_subsid_scope_code_id

int 4 yes main scope for original reporting unit at closing [=ct_scope_code.id]

cl_subsid_scope_period_id

int 4 yes main scope period for original reporting unit at closing

cl_subsid_scope_version_id

int 4 yes main scope version for original reporting unit at closing [=ct_scope_version.id]






1 → parent company 2 à subsidiary




op_entity_id int 4 yes linked consolidated reporting unit at opening [ct_entity.id]





3 → equity method










op_level int 4 yes minimum level for original reporting unit at opening




op_subsid_scope_code_id

int 4 yes main scope for original reporting unit at opening [=ct_scope_code.id]

op_subsid_scope_period_id

int 4 yes main scope period for original reporting unit at opening

op_subsid_scope_version_id

int 4 yes main scope version for original reporting unit at opening [=ct_scope_version.id]




rl_behaviour int 4 yes average scope status for rules



2 → subsidiary



rl_integr_method int 4 yes average consolidation method for rules




3 → equity method



subsid_id int 4 yes original reporting unit dimension [=ct_entity.id]





variation int 4 yes variation between opening and closing

0 → no variation

1 → incoming







scope_custom_prop int 4 yes custom property for the scope [=ct_scope_entity_custom_prop.id]

4.3.8 ct_tbl_shares: stockholdings associated with consolidations


cl_control_rate float 8 yes total ownership interest (closing)

cl_forced_control int 4 yes forced control (closing)

cl_geographic_origin int 4 yes site from where the information originates (closing) [ct_site.id]

cl_interest_rate float 8 yes transitive share of profits (closing)




cl_origin_scope_code_id

int 4 yes scope code (statutory) from where the information originates (closing) [ct_scope_code.id]

cl_origin_scope_period_id

int 4 yes scope period (statutory) from where the information originates (closing)

cl_origin_scope_version_id

int 4 yes scope version (statutory) from where the information originates (closing) [ct_scope_version.id]

cl_share_direct_rate float 8 yes direct investments in number of stocks (closing)

cl_shares float 8 yes number of stocks held (closing)

cl_vote_direct_rate float 8 yes direct investments in number of voting rights (closing)

cl_votes float 8 yes number of voting rights held (closing)


held_id int 4 yes subsidiary [=ct_entity.id]

op_control_rate float 8 yes total ownership interest (opening)

op_forced_control int 4 yes forced control (opening)

op_geographic_origin int 4 yes site from where the information originates (opening) [ct_site.id]

op_interest_rate float 8 yes transitive share of profits (opening)

op_origin_scope_code_id

int 4 yes scope code (statutory) from where the information originates (opening) [ct_scope_code.id]



op_origin_scope_period_id

int 4 yes scope period (statutory) from where the information originates (opening)

op_origin_scope_version_id

int 4 yes scope version (statutory) from where the information originates (opening) [ct_scope_version.id]

op_share_direct_rate float 8 yes direct investments in number of stocks (opening)

op_shares float 8 yes number of stocks held (opening)

op_vote_direct_rate float 8 yes direct investments in number of voting rights (opening)

op_votes float 8 yes number of voting rights held (opening)

owner_id int 4 yes parent (0 for the capital row) [*=ct_entity.id]






4.3.9 ct_tbl_scope2: secondary consolidation scopes associated with consolidations









2 → subsidiary








3 → equity method










cl_subconso_currency_id

int 4 yes sub-consolidation currency [*=ct_curncy.id]

cl_subscope_code_id int 4 yes subscope code (sub-parent) [*=ct_scope_code.id]

cl_subscope_period_id int 4 yes subscope period (sub-parent)

cl_subscope_version_id






loaded int 4 yes reporting unit data loaded




2 → subsidiary








3 → equity method













op_subscope_code_id int 4 yes subscope code (sub-parent) [*=ct_scope_code.id]

op_subscope_period_id

int 4 yes subscope period (sub-parent)

op_subscope_version_id




phase int 4 no cidx category dimension [=ct_phase.id]




2 → subsidiary







3 → equity method








0 → no variation

1 → incoming 2 à outgoing at opening







4.3.10 ct_tbl_global_scope2: full secondary consolidation scopes associated with consolidations






2 → subsidiary







cl_entity_id int 4 yes linked consolidated reporting unit at closing [ct_entity.id]





3 → equity method










cl_level int 4 yes minimum level for original reporting unit at closing

cl_subsid_scope_code_id

int 4 yes main scope for original reporting unit at closing [=ct_scope_code.id]

cl_subsid_scope_period_id

int 4 yes main scope period for original reporting unit at closing

cl_subsid_scope_version_id

int 4 yes main scope version for original reporting unit at closing [=ct_scope_version.id]







2 → subsidiary




op_entity_id int 4 yes linked consolidated reporting unit at opening [ct_entity.id]





3 → equity method










op_level int 4 yes minimum level for original reporting unit at opening




op_subsid_scope_code_id

int 4 yes main scope for original reporting unit at opening [=ct_scope_code.id]

op_subsid_scope_period_id

int 4 yes main scope period for original reporting unit at opening

op_subsid_scope_version_id

int 4 yes main scope version for original reporting unit at opening [=ct_scope_version.id]







2 → subsidiary







3 → equity method



subsid_id int 4 yes original reporting unit dimension [=ct_entity.id]






0 → no variation

1 → incoming








4.3.11 ct_tbl_shares2: secondary stockholdings associated with consolidations


cl_control_rate float 8 yes total ownership interest (closing)

cl_forced_control int 4 yes forced control (closing)

cl_geographic_origin int 4 yes site from where the information originates (closing) [ct_site.id]

cl_interest_rate float 8 yes transitive share of profits (closing)




cl_origin_scope_code_id

int 4 yes scope code (statutory) from where the information originates (closing) [ct_scope_code.id]

cl_origin_scope_period_id

int 4 yes scope period (statutory) from where the information originates (closing)

cl_origin_scope_version_id

int 4 yes scope version (statutory) from where the information originates (closing) [ct_scope_version.id]

cl_share_direct_rate float 8 yes direct investments in number of stocks (closing)

cl_shares float 8 yes number of stocks held (closing)

cl_vote_direct_rate float 8 yes direct investments in number of voting rights (closing)

cl_votes float 8 yes number of voting rights held (closing)


held_id int 4 yes subsidiary [=ct_entity.id]

op_control_rate float 8 yes total ownership interest (opening)

op_forced_control int 4 yes forced control (opening)

op_geographic_origin int 4 yes site from where the information originates (opening) [ct_site.id]

op_interest_rate float 8 yes transitive share of profits (opening)

op_origin_scope_code_id

int 4 yes scope code (statutory) from where the information originates (opening) [ct_scope_code.id]



op_origin_scope_period_id

int 4 yes scope period (statutory) from where the information originates (opening)

op_origin_scope_version_id

int 4 yes scope version (statutory) from where the information originates (opening) [ct_scope_version.id]

op_share_direct_rate float 8 yes direct investments in number of stocks (opening)

op_shares float 8 yes number of stocks held (opening)

op_vote_direct_rate float 8 yes direct investments in number of voting rights (opening)

op_votes float 8 yes number of voting rights held (opening)

owner_id int 4 yes parent (0 for the capital row) [*=ct_entity.id]








4.4 Intercompany amounts

4.4.1 ct_interco_def: intercompany reconciliations processing definition


all_entities int 4 yes type of reporting units processed:

0 → with package data only

1 → all reporting units

cdesc image 16 yes

conso_ruleset int 4 yes sets of rules [*=ct_ruleset.id]

curncy int 4 yes currency [=ct_curncy.id]

id int 4 no uidx

interrule int 4 yes reconciliation rule [*=ct_interrule.id]


locked int 4 yes status of intercompany data

0 → unlocked

1 → locked


phase int 4 yes category [=ct_phase.id]

reconciliation_variante int 4 yes intercompany reconciliation variant [=ct_var_interco.id]

rules_set int 4 yes subset of rules [*=ct_ruleset.id]

scope_code int 4 yes scope [=ct_scope_code.id]


task_author int 4 yes user who performed the corresponding task [=ct_user.id]



task_date datetime 8 yes date the corresponding task was performed

task_status int 4 yes status of the corresponding task performed

0 → error

1 → task performed

2 → task archived

updper int 4 yes data entry period

variante int 4 yes variant [=ct_variant.id]

4.5 Opening balance amounts

4.5.1 ct_pack_model: opening balance package (or generated package) headers



cdesc image 16 yes

commented bit 1 yes comment available






















int 4 yes



int 4 yes







id int 4 no uidx1






















late bit 1 yes late


















1 → not run

2 → no data

3 → valid

4 → warning

5 → non-blocking 6 → blocking


































8 → filter







8 → filter




0 → none

1 → full






0 → none

65536 → standard


262144 → advance



datetime 8 yes














0 → n.a.

1 → empty

2 → published

4 → changed

8 → integrated












0 → not run

1 → valid

2 → invalid




4.5.2 ct_pack_model_period_trans: settings for generated package periods




4.5.3 ct_pack_model_protect_flow: settings for protecting generated package flows







4.5.4 ct_pack_model_protect_period: settings for protecting generated package periods





5 Other data

5.1 Investments

5.1.1 ct_portfl: investment data source headers


cdesc image 16 yes

closure_flow_id int 4 yes source data flow

control_threshold smallint 2 yes control threshold

direct_auto_holding smallint 2 yes management of direct self-held stock

GUI_props int 4 yes

held_cap_dim_id int 4 yes capital dimension for subsidiary

held_portfl_dim_id int 4 yes investment dimension for subsidiary

id int 4 no uidx

natures_id int 4 yes source data audit ID filter

outer_entity_id int 4 yes non-group company

owner_cap_dim_id int 4 yes capital dimension for parent

owner_portfl_dim_id int 4 yes investment dimension for parent


period_id int 4 yes source data period

phase_id int 4 yes source data category

portfl_code_id int 4 yes investment code dimension [=ct_portfl_code]

portfl_period_id int 4 no investment period dimension


shares_cap_accnts_id int 4 yes capital account in number of stocks


Other data


shares_hld_accnts_id int 4 yes investment account in number of stocks

updper_id int 4 yes source data data entry period

votes_cap_accnts_id int 4 yes capital account in number of voting rights

votes_hld_accnts_id int 4 yes investment account in number of voting rights


smallint 2 yes manages voting rights:



5.1.2 ct_portfl_lines: investment data source


geographic_origin int 4 yes site from where the information originates [ct_site.id]

held_id int 4 yes subsidiary dimension [=ct_entity.id]

initial_shares float 8 yes number of stocks after initialization

initial_votes float 8 yes number of voting rights after initialization

keep_modified_shares int 4 yes keeps value of revised number of stocks after reinitialization

keep_modified_votes int 4 yes keeps value of revised number of voting rights after reinitialization

modified_forced_control

int 4 yes forced control

SAP Financial Consolidation Database Schema GuideOther data CONFIDENTIAL 117


modified_shares float 8 yes number of stocks revised

modified_votes float 8 yes number of voting rights revised

owner_id int 4 yes parent dimension (0 for one capital row) [*=ct_entity.id]

portfl_code_id int 4 yes investment code dimension [=ct_portfl_code]

portfl_period_id int 4 yes investment period dimension

5.1.3 ct_portfl_graph_props: display properties of charts in investment occurrences


graph_props image 16 yes chart properties

id int 4 no uidx investment occurence [=ct_portfl.id]

5.2 Scopes

5.2.1 ct_scope: scope data source headers


cdesc image 16 yes

control_threshold smallint 2 yes control threshold

direct_auto_holding smallint 2 yes management of direct self-held stock

entities_id int 4 yes reporting unit filter [*=ct_filter.id]


Other data


exclude_all_helds_by_equity

smallint 2 yes propagating reporting units using the equity method:

0 → including stockholdings

1 → excluding stockholdings

global_integr_threshold

smallint 2 yes full consolidation threshold

GUI_props int 4 yes

hierarchy_id int 4 yes

hierarchy_status int 4 yes

id int 4 no uidx

init_from_portfolio int 4 yes

initialization_in_steps smallint 2 yes initializing in steps

integr_rate_computed_as_max

smallint 2 yes consolidation rate calculation mode:

0 → total ownership interest

1 → maximum total ownership interest and share of profits

integr_threshold smallint 2 yes consolidation threshold

management_scope smallint 2 yes type of scope:

0 → statutory

1 → reporting

mother_id int 4 yes main parent company [*=ct_entity.id]

opening_scope_code_id

int 4 yes opening scope code [*=ct_scope_code.id]

opening_scope_period_id

int 4 yes opening scope period

opening_scope_version_id

int 4 yes opening scope version [*=ct_scope_version.id]

origin_portfl_code_id int 4 yes original investment code [*=ct_portfl_code.id]



origin_portfl_period_id int 4 yes original investment period


proportional_integr_threshold

smallint 2 yes proportional consolidation threshold

reporting_id int 4 yes

scope_code_id int 4 yes scope code dimension [*=ct_scope_code.id]

scope_locked int 4 yes

scope_period_id int 4 no scope period dimension

scope_version_id int 4 yes scope version dimension [*=ct_scope_version.id]

secondary_hierarchy_id

int 4 yes Secondary hierarchy



smallint 2 yes manages voting rights:



5.2.2 ct_scope_lines: scope data source (reporting units)




Other data


behaviour int 4 yes scope status:



2 → subsidiary




initial_control_rate float 8 yes group total ownership interest after initialization

initial_forced_control int 4 yes forced control after initialization

initial_integr_method int 4 yes consolidation method after initialization:




3 → equity method


initial_integr_rate float 8 yes consolidation rate after initialization

initial_interest_rate float 8 yes group share of profits after initialization

intermed_control_rate float 8 yes intermediate total ownership interest

intermed_integr_rate float 8 yes intermediate consolidation rate

intermed_interest_rate float 8 yes intermediate share of profits

intermed_rates int 4 yes intermediate rates available



keep_mod_control_rate

int 4 yes keeps the value of the revised group total ownership interests after reinitialization

keep_mod_integration int 4 yes keeps the value of the revised consolidation rate after reinitialization

keep_mod_interest_rate

int 4 yes keeps the value of the revised group share of profits after reinitialization

modified_control_rate float 8 yes revised group total ownership interests

modified_integr_method

int 4 yes revised consolidation method:




3 → equity method


modified_integr_rate float 8 yes revised consolidation rate

modified_interest_rate float 8 yes revised group share of profits



scope_custom_prop int 4 yes [=ct_scope_entity_custom_prop.id]

scope_period_id int 4 yes scope period dimension


subscope_code_id int 4 yes subscope code (sub-parent) [*=ct_scope_code.id]


Other data


subscope_period_id int 4 yes subscope period (sub-parent)

subscope_period_same

int 4 yes subscope period identical to current scope period

subscope_version_id int 4 yes subscope version (sub-parent) [*=ct_scope_version.id]

subscope_version_same

int 4 yes subscope version identical to current scope version

5.2.3 ct_scope_portfl_lines: scope data source (stockholdings)


geographic_origin int 4 yes site from where the information originates [ct_site.id]

held_id int 4 yes subsidiary dimension [=ct_entity.id]

initial_forced_control int 4 yes forced control after initialization

initial_shares float 8 yes number of stocks after initialization

initial_votes float 8 yes number of voting rights after initialization

keep_mod_forced_control

int 4 yes keeps the value of the forced control after reinitialization

keep_modified_shares int 4 yes keeps value of revised number of stocks after reinitialization

keep_modified_votes int 4 yes keeps value of revised number of voting rights after reinitialization

modified_forced_control

int 4 yes forced control



modified_shares float 8 yes number of stocks revised

modified_votes float 8 yes number of voting rights revised

origin_scope_code_id int 4 yes original subscope code for the stockholdings [=ct_scope_code.id]

origin_scope_period_id

int 4 yes original subscope period for the stockholdings

origin_scope_version_id

int 4 yes original subscope version for the stockholdings [=ct_scope_version.id]

owner_id int 4 yes parent dimension (0 for the capital row) [*=ct_entity.id]


scope_period_id int 4 yes scope period dimension


5.2.4 ct_scope_graph_props: display properties of charts in scope occurrences


graph_props image 16 yes chart properties

id int 4 no uidx scope occurence [=ct_scope.id]


Other data

5.3 Conversion and tax rates

5.3.1 ct_exchange_rate_header: conversion rate table headers


cdesc image 16 yes

ct_truecot int 4 yes type of quotation:

0 → uncertain for certain

1 → certain for uncertain

id int 4 no uidx



update_period_id int 4 yes conversion rate period dimension

version_id int 4 yes conversion rate version dimension [=ct_exrate_version.id]

5.3.2 ct_exrate: conversion rate data source


ct_currency int 4 yes currency dimension [=ct_curncy.id]

ct_entity int 4 yes reporting unit dimension [*=ct_entity.id]

ct_exrate float 8 yes conversion rate property

ct_period int 4 yes conversion rate period dimension

ct_type int 4 yes rate type dimension [*=ct_exrate_type.id]

ct_version int 4 yes conversion rate version dimension [=ct_exrate_version.id]


5.3.3 ct_taxrate_header: tax rate headers


cdesc image 16 yes

id int 4 no uidx



update_period_id int 4 yes tax rate period dimension

5.3.4 ct_taxrate: tax rate data source


ct_country int 4 yes tax rate country dimension [=ct_country.id]

ct_entity int 4 yes reporting unit dimension [*=ct_entity.id]

ct_period int 4 yes tax rate period dimension

ct_taxrate float 8 yes tax rate property

ct_type int 4 yes rate type dimension [=ct_taxrate_type.id]


Other data

6 Operation definition

6.1 Reporting ID

6.1.1 ct_reporting: reporting ID



cdesc image 16 yes

conso_data_security int 4 yes consolidated data protection





ct_modify_comment int 4 yes indicates whether or not the Group comment of the reporting set has been changed. If it has not been changed, the value is -1.

ct_reporting_hierarchy int 4 yes




exchange_rate_type_id int 4 yes conversion rate type used for converting opening balance data [=ct_exrate_type.id]

SAP Financial Consolidation Database Schema GuideOperation definition CONFIDENTIAL 127


exchange_rate_update_period_id

int 4 yes conversion rate period used for converting opening balance data

exchange_rate_version_id

int 4 yes conversion rate version used for converting opening balance data [=ct_exrate_version.id]


id int 4 no uidx











locked int 4 yes

manual_entry_security int 4 yes central manual journal entry protection



op_bal_manager_id int 4 yes manages opening balance data –

523588 → preconsolidated data –

523538 → consolidated data




Operation definition










package_security int 4 yes package protection


pre_conso_data_security

int 4 yes preconsolidated data protection





8 → filter







8 → filter


0 → none

1 → full


reporting_end_date datetime 8 yes reporting end date


datetime 8 yes



reporting_security int 4 yes reporting ID protection

reporting_start_date datetime 8 yes reporting start date









status int 4 yes reporting ID status

0 → prepared

1 → in progress

2 → complete

3 → archived


use_dft_control_level smallint 2 yes uses the default control level for validating packages

use_dft_control_set smallint 2 yes uses the default set of controls

use_dft_input_restriction

smallint 2 yes uses the default data entry restrictions

use_dft_internet_input_folder

smallint 2 yes uses the default internet data entry folder

use_dft_opening_balances

smallint 2 yes uses the default settings for opening balance data

use_dft_protect_flow_condition

smallint 2 yes uses the default flow protection conditions

use_dft_protect_flow_filter

smallint 2 yes uses the default flow protection

use_dft_protect_period_filter

smallint 2 yes uses the default period protection

use_dft_publishing_lock

smallint 2 yes uses the default lock when publishing




use_dft_rule_set smallint 2 yes uses the default set of rules

use_dft_techorig_restriction

smallint 2 yes If yes use ct_framework. input_techorig_restriction_id

use_dft_windows_input_folder

smallint 2 yes uses the default data entry folder




6.1.2 ct_reporting_period_trans: settings for reporting periods


id int 4 no uidx corresponding reporting ID [=ct_pack.id]


6.1.3 ct_reporting_protect_flow: settings for protecting reporting flows





6.1.4 ct_reporting_protect_period: settings for protecting reporting periods




6.1.5 ct_journal_reporting_site: journal entries associated with reporting IDs (technical table)


control_status int 4 yes ledger status:

1 → empty

2 → automatic journal entry ledger

4 → run automatic journal entry ledger

8 → opening balance ledger


32 → no data


128 → warning


512 → blocking

1024 → imbalanced

2048 → n.a.

empty int 4 yes empty

id int 4 no uidx


last_entry_number int 4 yes last journal entry number assigned




phase_id int 4 yes reporting ID category [=ct_phase.id]

reporting_id int 4 yes obsolete

site_id int 4 yes site [=ct_site.id]

status int 4 yes

transaction_mutex int 4 yes "technical" column

updper_id int 4 yes reporting ID data entry period

6.1.6 ct_hierarchy: information about the whole hierarchy


dimension_id int 4 no Identifier of the dimension (usually reporting unit or account) the hierarchy is based on

id int 4 no uidx

init_charac_id int 4 no Identifier of the characteristic the hierarchy is initialized from

init_elim int 4 no 1 (=the user initialized the hierarchy with “elimination” leaves) or 0


type int 4 no 0 (= the dimension is not aggregatable) or 1 (=the dimension is aggregatable)

6.1.7 ct_hierarchy_content: hierachy content


charac_id int 4 yes

datatype int 4 no

globorig int 4 yes Identifier of the site where the hierarchy item was created



hierarchy_id int 4 yes cidx2 Identifier of the hierarchy the item belongs to

id int 4 no uidx1


parent_elim_id int 4 yes

parent_id int 4 yes

position int 4 no

reftable_id int 4 yes cidx2 Identifier of the reference table for the reference value

refvalue_id int 4 yes cidx2 Identifier of the reference value of the item

type int 4 no

update_date datetime 8 yes

6.2 Reporting set

6.2.1 ct_entity_reporting: reporting sets


allow_early_publishing int 4 yes advanced publication authorized

cdesc image 16 yes



int 4 yes blocking controls


ct_modify_comment int 4 yes indicates whether or not the Group comment of the reporting set has been changed. If it has not been changed, the value is -1.




ct_reporting_desc nvarchar 255 yes description of the associated reporting ID




definition_change_date

datetime 8 yes date the data entry definition was last changed

definition_change_user_id

int 4 yes user who changed the data entry definition [=ct_user.id]

derogation_pack_qty int 4 yes number of publications by special permission

early_pack_qty int 4 yes number of advance publications

entity_id int 4 yes cuidx2 reporting unit [=ct_entity.id]

environment_change_date

datetime 8 yes date the data entry environment was last changed

environment_change_user_id

int 4 yes user who changed the data entry environment [=ct_user.id]

id int 4 no uidx1














manual_entry_security int 4 yes central manual journal entry protection




-523588 → reconsolidated data







opening_balances int 4 yes opening balance available

opening_generation_date

datetime 8 yes date the opening package was generated

opening_generation_user_id

int 4 yes user who generated the opening package [=ct_user.id]

opening_send_date datetime 8 yes date the opening package was sent

opening_send_user_id int 4 yes user who sent the opening package [=ct_user.id]







pack_users_restriction int 4 yes equal to 1 if the package has a list of users authorized to access it

package_security int 4 yes package protection

phase_id int 4 yes cuidx2 category [=ct_phase.id]





8 → filter

protect_flow_if_op_bal int 4 yes flows read-only if opening balances






8 → filter


0 → none

1 → full



related_pack_id int 4 yes associated package [*=ct_pack.id]

restr_on_document int 4 yes data entry restrictions applied to schedules


int 4 yes data entry restrictions applied to local journal entries


int 4 yes data entry restrictions applied to central journal entries






update_period_id int 4 yes cuidx2 data entry period

use_default_delivery_props

int 4 yes uses the default reporting settings

use_default_integration_props

int 4 yes uses the default integration settings

use_default_publishing_props

int 4 yes uses the default publication settings

use_dft_control_level int 4 yes uses the default control level for validating packages

use_dft_control_set int 4 yes uses the default set of controls

use_dft_input_restriction

int 4 yes uses the default data entry restrictions

use_dft_internet_input_folder

int 4 yes uses the default internet data entry folder

use_dft_opening_balances

int 4 yes uses the default settings for opening balance data

use_dft_protect_flow_condition

int 4 yes uses the default flow protection conditions

use_dft_protect_flow_filter

int 4 yes uses the default flow protection

use_dft_protect_period_filter

int 4 yes uses the default period protection

use_dft_publishing_lock

int 4 yes uses the default lock when publishing

use_dft_rule_set int 4 yes uses the default set of rules

use_dft_techorig_restriction

smallint 2 yes If yes use ct_framework. input_techorig_restriction_id

use_dft_windows_input_folder

int 4 yes uses the default data entry folder

valid_or_locked_pack_qty

int 4 yes number of standard publications






workflow int 4 yes equal to 1 if the authorized users are organized in workflow hierarchies

6.2.2 ct_entity_rep_period_trans: settings for reporting set periods


id int 4 no uidx corresponding reporting set [=ct_entity_reporting.id]


6.2.3 ct_entity_rep_protect_flow: settings for protecting reporting set flows




6.2.4 ct_entity_rep_protect_period: settings for protecting reporting set periods





6.2.5 ct_input_restriction: data entry restrictions


cdesc image 16 yes

id int 4 no uidx






6.2.6 ct_ser_input_restr: data entry restrictions definition


id int 4 no uidx data entry description defined [=ct_input_restriction.id]

serial_dimension image 16 yes definition of data entry restrictions (serialized)

6.2.7 ct_pack_group_comment: group comment for packages


cdesc image 16 yes group comment (serialized)

id int 4 no uidx




6.2.8 ct_pack_user: list of users authorized to access the package (workflow)


pack_id int 4 yes uidx1 corresponding reporting set [=ct_entity_reporting.id]

rank int 4 yes uidx1 rank of the user in the workflow hierarchy

user_id int 4 yes uidx1 user [=ct_user.id]

6.3 Ledgers

6.3.1 ct_journal: journal entry ledger reference table


all_phases int 4 yes used for all categories

environment int 4 yes ledger environment: 1 → local 2 → central 3 → local and central

id int 4 no uidx



nature_charac_id int 4 yes audit ID characteristic [*=ct_charac.id]

nature_charac_value_id

int 4 yes value of characteristic [*=ct_charac.dst_reftable.physname.id]

nature_filter_id int 4 yes audit ID filter [*=ct_filter.id]

nature_init_method int 4 yes audit ID selection method: 0 → by value 1 → by filter 2 → by characteristic





6.3.2 ct_journal_to_nature: audit IDs associated with journal entry ledgers


journal_id int 4 yes corresponding ledger [=ct_journal.id] with ct_journal.nature_init_method = 0

nature_id int 4 yes audit ID defined [=ct_nature.id]

6.3.3 ct_journal_to_phase: categories associated with journal entry ledgers


journal_id int 4 yes corresponding ledger [=ct_journal] with ct_journal.all_phases = 0

phase_id int 4 yes category defined [=ct_phase.id]

6.4 Journal entry templates

6.4.1 ct_entry_model: journal entry template


build_framework_id int 4 yes category scenario on which the template rows are based [=ct_framework.id]

cdesc image 16 yes

currency_id int 4 yes currency of the template [=ct_curncy.id]

id int 4 no uidx






nature_id int 4 yes audit ID of the template [=ct_nature.id]


pack_mode_allowed int 4 yes template authorized or not in the package

restriction_entity_charact_id

int 4 yes characteristic if initialization method is "Characteristic" [=ct_charac.id]

restriction_entity_method

int 4 yes initialization method for restrictions to Reporting Unit (ID of the "List of values", "Filter" or "Characteristic" methods)

restriction_entity_value

int 4 yes filter or characteristic values if the initialization method is "Filter" or "Characteristic" [=ct_filter.id or {reference_table}.id]



6.4.2 ct_entry_model_rows: journal entry template rows


id int 4 no corresponding journal entry template [=ct_entry_model.id]

model_rows image 16 yes journal entry template rows (serialized)

6.4.3 ct_entry_model_to_entity: restrictions by reporting unit in the journal entry template


entity_id int 4 yes reporting unit [=ct_entity.id]



entry_model_id int 4 yes journal entry template [=ct_entry_model.id]

6.4.4 ct_entry_model_to_framework: restrictions by category scenario in the journal entry template



framework_id int 4 yes category scenario [=ct_framework.id]

6.4.5 ct_entry_model_to_phase: restrictions by category in the journal entry template



phase_id int 4 yes category [=ct_phase.id]

6.4.6 ct_entry_embedded_file: central journal entry attachment


file_name nvarchar 253 yes Attachment name

file_serial image 16 yes Attachment contents

file_size Int 4 yes Size in KB of attachment

file_type nvarchar 120 yes Attachment file extension

id int 4 no uidx ID for the central jounal entry attachment




ownerobject_id int 4 yes idx Package that owns attachment


7 Report Designer

7.1 Schedules and schedule items

7.1.1 ct_document: schedules


cdesc image 16 yes

expansion_analyse bit 1 yes

expansion_analyse bit 1 yes

expansion_input bit 1 yes

expansion_input bit 1 yes

id int 4 no uidx

id_doc_headerfooter int 4 yes header and footer templates [=ct_headerfooter.id]

id_doc_owned_headerfooter

int 4 yes header and footer [=ct_headerfooter.id]

id_doc_template int 4 yes style book [=ct_doc_template.id]

id_inputcomment int 4 yes data entry guide [=ct_document_input_comment.id]

id_tech_userdoc int 4 yes Identifier of the associated technical docuser






show_headerfooter bit 1 yes indicates whether or not the header and footer should be displayed by default in the scheudle run.

show_headerfooter bit 1 yes


Report Designer

7.1.2 ct_document_serial_doc: schedule definition


id int 4 no uidx corresponding schedule [=ct_document.id]

serial_doc image 16 yes schedule definition (serialized)

7.1.3 ct_document_input_comment: schedule data entry guide


cdesc image 16 yes data entry guide (serialized)

id int 4 no uidx


7.1.4 ct_docuser: most recently used schedule values by user


doc_id int 4 yes idx schedule [=ct_document.id]

id int 4 no uidx

last_execution_date datetime yes Date of the last execution of the document by this user

last_launcher_id int 4 yes Identifier of the user who last run this document - useful only for the technical user, when user_id = 0

Executions_counter int 4 yes Number of executions for the current user or for all users when user_id = 0


serial_docuser image 16 yes user settings (serialized)

SAP Financial Consolidation Database Schema GuideReport Designer CONFIDENTIAL 147


user_id int 4 yes idx user [=ct_user.id]

7.1.5 ct_doc_template: style book (automatic presentation)


cdesc image 16 yes comments

id int 4 no uidx


level_col int 4 yes

level_row int 4 yes





7.1.6 ct_doc_template_serial: style book definition


id int 4 no uidx corresponding style book [=ct_doc_template.id]

serial_template image 16 yes style book definition (serialized)

7.1.7 ct_headerfooter: schedule headers and footers


cdesc image 16 yes comments

id int 4 no uidx

is_template int 4 no template shared by a given number of schedules



Report Designer






7.1.8 ct_headerfooter_serial: schedule header and footer definition


id int 4 no uidx corresponding header and footer [=ct_headerfooter.id]

serial_headerfooter image 16 yes header and footer definition (serialized)

7.1.9 ct_doc_formula: schedule initialization formulas


ct_expression varchar 4000 yes expression of the formula

id int 4 no uidx






7.1.10 ct_doc_form_to_dim: dimensions associated with schedule formulas


dimension_id int 4 yes dimension [=ct_dimension.id]



doc_formula_id int 4 yes initialization formula [=ct_doc_formula.id]

7.1.11 ct_doc_scheduleenhancement: enhancements to schedules for planning

These enhancements are saved by user/schedule/category/data entry period/reporting unit/variables to be set.


doc_id int 4 yes cidx1 ID of the schedule in which the enhancement was saved

entity_id int 4 yes cidx1 ID of the reporting unit for which the enhancement was saved

id int 4 no uidx enhancement ID

period_id int 4 yes cidx1 ID of the data entry period for which the enhancement was saved

phase_id int 4 yes cidx1 ID of the category for which the enhancement was saved

todefine_stream image 16 yes stream of variables to be set for which the enhancement was saved

user_id int 4 yes cidx1 ID of user who saved the enhancement

Notethe ct_doc_scheduleenhancement and ct_doc_scheduleenhancementdata tables are linked in order to have 2 streams of enhancements.


Report Designer

7.1.12 ct_doc_scheduleenhancementdata: enhancements made to schedules for planning

These enhancements are saved by user/schedule/category/data entry period/reporting unit/variables to be set.


data_stream image 16 yes stream containing the enhancement to be saved

data_stream_version int 4 yes

id int 4 no uidx ID for enhancement data (the tables are linked => same ID as the ct_doc_scheduleenhancement table

7.2 Hierarchies

7.2.1 ct_folder: folders for schedules


all_phases int 4 yes active for the whole category

cdesc image 16 yes

for_input int 4 yes active for data entry

for_internet_analysis int 4 yes active for Web analysis

for_windows_analysis int 4 yes active for Windows analysis

id int 4 no uidx






welcome_doc int 4 yes has a home page


7.2.2 ct_folder_to_phase: folders displayed according to the category


folder_id int 4 yes folder [=ct_folder.id]


7.2.3 ct_book: schedule books


cdesc image 16 yes

id int 4 no uidx






7.2.4 ct_baf_tree_link: relationships in the folder/book/schedule hierarchy


child_id int 4 yes id of child [=ct_book.id or ct_document.id]

child_type int 4 yes type of child

-524088 à book

-524087 à schedule

id int 4 no uidx

index_in_parent int 4 yes hierarchy for organizing the parent [=ct_baf_tree_link.id]



Report Designer


parent_id int 4 yes id of parent [=ct_folder.id or ct_book.id]

parent_type int 4 yes type of parent:

-524086 à folder

-524088 à book


user_id int 4 yes user [*=ct_user.id]

7.3 Report bundles

7.3.1 ct_state: schedule settings for report bundles


cdesc image 16 yes

document_id int 4 yes

id int 4 no uidx

next_state_id int 4 yes


previous_state_id int 4 yes


statesgroup_id int 4 yes

status int 4 yes

state_comment nvarchar 253 yes corresponds to the "description supplement" column in the Report Bundles

7.3.2 ct_state_to_define_data


id int 4 no uidx

to_define_data image 16 yes


7.3.3 ct_statesgroup: report bundles


all_phases int 4 yes

cdesc image 16 yes

id int 4 no uidx






status int 4 yes

exe_start_date datetime -- yes Last run start date of a report bundle

exe_end_date datetime -- yes Last run end date of a report bundle

nb_gen_pages int -- yes Number of generated pages during the last run

7.3.4 ct_statesgroup_to_phase: report bundles assigned by category


phase_id int 4 yes

statesgroup_id int 4 yes

7.3.5 ct_statesgroup_to_define_data


id int 4 no uidx

to_define_data image 16 yes


Report Designer

8 Category scenario

8.1 Definition and general settings

8.1.1 ct_framework: category scenario


acc_calculaccumul_fltmethod

int 4 yes

acc_calculperiod_fltmethod

int 4 yes

ana_charac int 4 yes characteristic which can be used for creating dimensional analysis [=ct_charac.id]

cdesc image 16 yes

comment_charac int 4 yes characteristic which can be used for creating sets of indicators with comments [=ct_charac.id]





convert_dim_curncy int 4 yes conversion currency dimension [=ct_dimension.id]

convert_flow_filter int 4 yes flow filter converted using transaction currency [=ct_filter.id]

cumul_filter_id int 4 yes filter for accounts calculated cumulatively [=ct_filter.id]

cumul_flow_id int 4 yes cumulative flow [=ct_flow.id]

dfirst smallint 2 yes data entry period start month: from 1 to 12 for January to December

SAP Financial Consolidation Database Schema GuideCategory scenario CONFIDENTIAL 155


entry_round_diff_account

int 4 yes

entry_round_diff_flow int 4 yes

fam_charac int 4 yes characteristic which can be used for creating subsets [=ct_charac.id]

flags smallint 2 yes category scenario options:

1 → reversal required

2 → manage conversions

4 → manage carry-overs and opening balances

8 → apply data entry restrictions

32 → convert amounts using transaction currency 64 → apply package rules

128 → process periods consecutively

256 → carry forward one period to another


Category scenario


formcumul_context smallint 2 yes cumulative formula context:

1 → initializing packages – original package audit ID

2 → initializing packages – other package audit IDs

4 → package – original package audit ID

8 → package – other package audit IDs

16 → journal entries – original package audit ID

32 → journal entries – other package audit IDs

64 → journal entries – central audit IDs

128 → breakdown



formreport_context_dft

smallint 2 yes default settings for carry-over flow context:








128 → breakdown


Category scenario


formula_context_dft smallint 2 yes default settings for formula context:








128 → breakdown

hierarchy_calculation_id

int 4 yes

id int 4 no uidx






isinsimplemode bit 1 yes


month_filter_id int 4 yes filter for accounts calculated monthly [=ct_filter.id]

month_flow_id int 4 yes monthly flow [=ct_flow.id]





















8 → filter







8 → filter


Category scenario


pub_ref_id int 4 yes published category scenario form [=ct_valid_frmwrk.id]


0 → none

1 → full


rate_flow_filter int 4 yes flow filter integrated with opening rate

report_def_cumul smallint 2 yes

report_def_source smallint 2 yes






rollupform_context smalling 2 yes


scope_closing_flow int 4 yes closing flow [=ct_flow.id]

scope_diff_account_filter

int 4 yes account filter managed by consolidation difference [=ct_filter.id]

scope_diff_flow int 4 yes consolidation difference flow [=ct_flow.id]

scope_entry_account_filter

int 4 yes account filter managed by incoming scope [=ct_filter.id]

scope_entry_flow int 4 yes incoming flow [=ct_flow.id]

scope_eq_pack_acc_filter

int 4 yes account filter managed by keeping equity method packages [=ct_filter.id]

scope_exit_flow int 4 yes outgoing flow [=ct_flow.id]



scope_exiting_account_filter

int 4 yes account filter managed by outgoing scope [=ct_filter.id]

scope_merger_acc_filter

int 4 yes account filter managed by mergers [=ct_filter.id]

scope_merger_flow int 4 yes merger flow [=ct_flow.id]

scope_new_entry_account_filter

int 4 yes account filter managed by mode change [=ct_filter.id]

scope_new_entry_flow int 4 yes new mode flow [=ct_flow.id]

scope_old_close_flow int 4 yes old mode flow [=ct_flow.id]

scope_old_closing_acc_filter

int 4 yes old mode account filter managed by mode change [=ct_filter.id]

scope_opening_flow int 4 yes opening flow [=ct_flow.id]




Category scenario


states smallint 2 yes category scenario options:

1 → adjustments in packages

2 → local adjustments by journal entry (otherwise schedule)

4 → central manual journal entries

8 → distinguish central journal entries from local ones

16 → authorized comments

32 → comments for all indicators

64 → integrate zero amounts

128 → integrate headers at central site

update_ref_id int 4 yes update indicator in structure [=ct_refupdateflag.id]

valid_ref_id int 4 yes validated category scenario form (ócompiled) [=ct_valid_frmwrk.id]

version smallint 2 yes Serialization version of the validated category scenario

version_id int 4 yes version [=ct_framework_version.id]





8.1.2 ct_framework_version: category scenario version reference table


cdesc image 16 yes

id int 4 no ucidx







8.1.3 ct_framework_period_trans: settings for category scenario periods (for opening balances)


id int 4 no uidx corresponding category scenario [=ct_framework.id]


8.1.4 ct_framework_protect_flow: settings for protecting category scenario flows (opening balances)





Category scenario

8.1.5 ct_framework_protect_period: settings for protecting category scenario periods (opening balances)




8.2 Periods

8.2.1 ct_period: periods defined in category scenarios


expression text 16 yes definition of periods

framework_id int 4 yes idx corresponding category scenario [=ct_framework.id]

id int 4 no uidx

8.2.2 ct_cumul_def: definition of totals accumulated periodically in the category scenario


expression text 16 yes previous monthly/cumulative


id int 4 no uidx

period_id int 4 yes period [=ct_period.id]

report smallint 2 yes reporting ID [from 1 to 12, 1 = data entry period start month]


8.2.3 ct_source: initialization sources in the category scenario



id int 4 no uidx



8.2.4 ct_source_def: definition of initialization sources in the category scenario by period


expression text 16 yes definition

id int 4 no uidx

period_id int 4 yes period [=ct_period.id]

report int 4 yes reporting ID [from 1 to 12, 1 = data entry period start month]

source_id int 4 yes initialization source [=ct_source.id]

8.3 Indicators

8.3.1 ct_acc_family: sets of indicators in the category scenario


cdesc image 16 yes

charac_value int 4 yes value of the characteristic defining the set, if not defined by a list of values


Category scenario


flags smallint 4 yes type of account definition:

0 → list of values

1 → characteristic

formula_context smallint 4 yes carry-over flow application context:





16 → journal entries – automatic



128 → breakdown


id int 4 no uidx




8.3.2 ct_frmwrk_acc: sets of indicator accounts in the category scenario


accnt int 4 yes account [=ct_account.id]

author_id int 4 yes

classofaccount int 4 yes

creation_date datetime 8 yes

dataentrysign int 4 yes

family_id int 4 yes set of indicators [=ct_acc_family.id]

framework_id int 4 yes corresponding category scenario [=ct_framework.id]

hasauthorizecomments

bit 1 yes

hasauthorizedcommentsondetail

bit 1 yes

hascommentsallflows bit 1 yes

hasdimensionalanalysis

bit 1 yes

id int 4 no idx

isapplyondetails bit 1 yes

isuseparentcomment bit 1 yes

isuseparentdimensionanalysis

bit 1 yes

isuseparentflowanalysis

bit 1 yes

isuseparentroolup bit 1 yes

journalsign int 4 yes

op_bal_account int 4 yes opening balance account [=ct_account.id]


rollupsign int 4 yes

update_author_id int 4 yes



Category scenario

8.3.3 ct_frmwrk_calculaccumul_filter: calculation accumulation filters


acc_calculaccumul_filter

image 16 yes

id int 4 no uidx

8.3.4 ct_frmwrk_calculperiod_filter: calculation period filters


acc_calculperiod_filter image 16 yes

id int 4 no uidx

8.3.5 ct_frmwrk_flow: sets of indicator flows in the category scenario (and flow template)


context smallint 2 yes application properties

1 → default for flow

2 → schedule environment

4 → single-sided local manual journal entry environment

8 → double-sided local manual journal entry environment

16 → single-sided central manual journal entry environment

32 → double-sided central manual journal entry environment

64 → consolidation at central site



diff_flow int 4 yes consolidation difference flow [*=ct_flow.id]

ex_rate_id int 4 yes type of conversion rate applied [*=ct_exrate_type.id]

family_id int 4 yes set of indicator [=ct_acc_family.id]

flow int 4 yes flow [=ct_flow.id]

framework_dft_id int 4 yes idx2 corresponding category scenario [=ct_framework.id] if default flow (odd number in "context"), otherwise 0

framework_id int 4 yes idx1 corresponding category scenario [=ct_framework.id] if flow assigned to a set (even number in "context"), otherwise 0

hasauthorizedcomments

bit 1 yes has authorized comments

id int 4 no uidx

op_bal_flow int 4 yes opening flow [*=ct_flow.id]


post_flow int 4 yes carry-over flow [*=ct_flow.id]

8.3.6 ct_comment_family: set of indicators with comments in the category scenario


cdesc image 16 yes

charac_value int 4 yes value of characteristic

flags smallint 2 yes definition properties: 1 → defined by characteristic 2 → indicators broken down


Category scenario



id int 4 no uidx



8.3.7 ct_comment_indicator: indicators with comments in the category scenario


account_id int 4 yes category scenario account [=ct_frmwrk_acc .id]

comment_family_id int 4 yes set of indicators with comments [=ct_comment_family.id]

flow_id int 4 yes flow [=ct_flow.id]


id int 4 no uidx


8.3.8 ct_indicators: details about the category scenario indicators


accnt int 4 no account

analysis_dim_pos int 4 yes position of indicator in the analysis dimension

convrate int 4 yes conversion rate

diff_flow int 4 yes conversion difference flow

docmode int 4 yes schedule environment mode



flow int 4 no flow

isloaded int 4 yes Integration of the context:

-1 if the integration context is checked, if not 0

locentrymode int 4 yes local journal entry environment mode

opbalaccnt int 4 yes opening balances account

opbalflow int 4 yes opening balances flow

phase int 4 no cidx1 category scenario category

postconvrate int 4 yes carry over flow conversion rate

postflow int 4 yes carry over flow

scheme int 4 yes analysis hierarchy

version_ref int 4 no cidx1 category scenario version

analysis_dim_branches

ntext 16 yes XML serialization of the dimensional analysis associated to the indicator

all_auditids int 4 yes Returns the value of option All audit IDs to the dimensional analysis

je_scheme int 8 yes

8.4 Dimensional Analysis

8.4.1 ct_analyse: dimensional analysis in the category scenario


Cdesc image 16 yes

charac_value int 4 yes value of characteristic


Category scenario


control_context int 4 yes

flags int 4 yes type of selection:

1 → by characteristic

formula_context int 4 yes

framework_id int 4 yes idx1 corresponding category scenario [=ct_framework.id]

id int 4 no uidx


nat_filter_id int 4 yes audit ID filter [=ct_filter.id]


topnode_id int 4 yes idx2 highest node in the analysis dimension hierarchy [=ct_det_anal.id]

8.4.2 ct_indic: indicators broken down in the category scenario


account_id int 4 yes category scenario account [=ct_frmwrk_acc .id]

analyse_id int 4 yes analysis hierarchy [=ct_analyse.id]

flow_id int 4 yes flow [=ct_flow.id]


id int 4 yes uidx



8.4.3 ct_det_anal: analysis dimensions used by dimensional analysis in the category scenario


code int 4 yes code of filter or reference value

ctrl_type smallint 2 yes type of automatic control:

0 → less than

1 → less than or equal to

2 → equal to

3 → greater than or equal to

4 → greater than

5 → less than in absolute value

6 → less than or equal to in absolute value

7 → equal to in absolute value

8 → greater than or equal to in absolute value

9 → greater than in absolute value

dimension_id int 4 yes dimension [=ct_dimension.id]

fathernode_id int 4 yes idx parent node [=ct_det_anal.id]


Category scenario


flags smallint 2 yes definition properties:

1 → totals at this level

2 → by filter

4 → check breakdown total against higher level total

8 → carry breakdown total to higher level

12 → carry higher level total – breakdown total to balancing figure

16 → carry breakdown total to cumulative node

32 → balancing figure node 64 → cumulative node

id int 4 no uidx


plugnode_id int 4 yes balancing figure node [=ct_det_anal.id]

upnode_id int 4 yes carry-over node [=ct_det_anal.id]

8.4.4 ct_form_auto: category scenario automatic formulas


id int 4 no uidx


node_id int 4 yes idx



8.4.5 ct_cont_auto: analysis hierarchy automatic controls in the category scenario


accuracy float 8 yes

cdesc image 16 yes

context smallint 2 yes

id int 4 no uidx

level_id int 4 yes


node_id int 4 yes idx



8.4.6 ct_control_auto_to_document: schedules associated with automatic controls


control_auto_id int 4 yes idx1

document_id int 4 yes idx1

8.4.7 ct_set_to_contauto: automatic controls associated with sets of controls


contauto_id int 4 yes

rank int 4 yes

set_id int 4 yes


Category scenario

8.4.8 ct_fam_to_contauto: automatic controls associated with sets of controls in the category scenario


contauto_id int 4 yes idx1

family_id int 4 yes idx1

rank int 4 yes

8.5 Formulas

8.5.1 ct_formula: category scenario manual formulas


cdesc image 16 yes

context int 4 yes formula context:








128 → breakdown

family_id int 4 yes




id int 4 no uidx



8.5.2 ct_formula_condition: conditions for running category scenario formulas


condition text 16 yes

id int 4 no uidx

8.5.3 ct_formula_expression: expression of category scenario formulas


expression text 16 yes

id int 4 no uidx

8.5.4 ct_form_family: subsets of formulas in the category scenario


cdesc image 16 yes


id int 4 no uidx




Category scenario

8.6 Controls

8.6.1 ct_control: category scenario controls


accuracy float 8 yes

cdesc image 16 yes

context smallint 2 yes control application context:

1 → default

2 → package environment

4 → preconsolidation (not used)

8 → consolidation (not used)

16 → opening balance environment

32 → manual journal entry environment 64 → original package audit ID

128 → aggregated audit IDs 256 → error

512 → period defined (not used)

1024 → forced (not used)

framework_dft_id int 4 yes idx2 corresponding category scenario [=ct_framework.id] if default control (odd number in "context")

framework_id int 4 yes idx1 corresponding category scenario [=ct_framework.id] if existing control (even number in "context")

id int 4 no uidx

level_id int 4 yes




nat_filter_id int 4 yes filter for adjustment audit IDs

nat_filter_id int 4 yes



8.6.2 ct_control_factor: control factors


factor text 16 yes

id int 4 no uidx

8.6.3 ct_control_expression: expression of controls


expression text 16 yes

id int 4 no uidx

8.6.4 ct_control_to_document: schedules associated with controls


control_id int 4 yes idx1

document_id int 4 yes idx1

8.6.5 ct_level: control levels in the category scenario


cdesc image 16 yes


Category scenario



id int 4 yes uidx




rank int 4 yes

8.6.6 ct_ctrl_set: sets of controls in the category scenario


cdesc image 16 yes


id int 4 no uidx




8.6.7 ct_ctrl_family: subsets of controls in the category scenario


cdesc image 16 yes

framework_id int 4 yes idx1 corresponding category scenario [=ct_framework.id]

id int 4 no uidx





8.6.8 ct_set_to_family: subsets of controls associated with sets of controls


family_id int 4 yes idx1

rank int 4 yes

set_id int 4 yes idx1

8.6.9 ct_set_to_control: manual controls associated with sets of controls



rank int 4 yes

set_id int 4 yes idx1

8.6.10 ct_family_to_control: manual controls associated with subsets of controls in the category scenario



family_id int 4 yes idx1 idx2

rank int 4 yes

8.7 Compiled category scenario form

8.7.1 ct_refupdateflag: updating category scenarios in the structure


flag smallint 2 yes updating in the structure: 0 → no 1 → yes


Category scenario



8.7.2 ct_valid_frmwrk: compiled category scenario form (indicators and analyses)


flags smallint 2 yes

id int 4 no uidx

serial_tree image 16 yes

update_author_id int 4 yes


8.7.3 ct_valid_frmwrk_input_data: compiled category scenario form (data which can be entered)


id int 4 no uidx corresponding compiled form [=ct_valid_frmwrk.id]

serial_input_data image 16 yes

8.7.4 ct_valid_frmwrk_init_form: compiled category scenario form (initialization formulas)



serial_init_form image 16 yes


8.7.5 ct_valid_frmwrk_pack_form: complied form of the category scenario (schedule context formulas)



serial_pack_form image 16 yes

8.7.6 ct_valid_frmwrk_entry_form: compiled category scenario form (journal entry context formulas)



serial_entry_form image 16 yes

8.7.7 ct_valid_frmwrk_control: compiled category scenario form (controls)



serial_control image 16 yes

8.7.8 ct_valid_frmwrk_report: compiled category scenario form (carry-over formulas)



serial_report image 16 yes


Category scenario

8.7.9 ct_valid_frmwrk_info: compiled category scenario form (information)



serial_info image 16 yes


9 Rules

9.1 Hierarchy

9.1.1 ct_ruleset: sets and subsets of rules


all_phases int 4 yes active for all categories

cdesc image 16 yes

id int 4 no uidx






type int 4 yes type of set of rules:

0 → consolidation

1 → preconsolidation

2 → package

8 → set of rules (otherwise subset)

9.1.2 ct_ruleset_to_phase: sets of rules associated with categories


phase_id int 4 no category for which the set is active [=ct_phase.id]

ruleset_id int 4 no corresponding set of rules [=ct_ruleset.id]


Rules

9.1.3 ct_ruleset_to_ruleset: subsets of rules associated with sets of rules


child_id int 4 yes child subset [=ct_ruleset.id]

parent_id int 4 yes parent set [=ct_ruleset.id]

rank int 4 yes order of subsets in the set

9.1.4 ct_ruleset_to_consrule: consolidation rules associated with sets or subsets of rules


rank int 4 yes order of rules in the set or subset

rule_id int 4 yes child rule [=ct_consrule.id]

ruleset_id int 4 yes parent set or subset [=ct_ruleset.id]

9.1.5 ct_ruleset_to_preconsrule: preconsolidation rules associated with sets or subsets of rules



rule_id int 4 yes child rule [=ct_preconsrule.id]


SAP Financial Consolidation Database Schema GuideRules CONFIDENTIAL 187

9.1.6 ct_ruleset_to_packrule: package rules associated with sets or subsets of rules



rule_id int 4 yes child rule [=ct_packrule.id]


9.1.7 ct_ruleset_to_interrule: intercompany rules associated with sets or subsets of rules



rule_id int 4 yes child rule [=ct_interrule.id]


9.1.8 ct_ruleset_to_sqlrule: SQL rules associated with sets or subsets of rules


rank int 4 yes

rule_id int 4 yes



Rules

9.1.9 ct_ruleset_to_ent_rolluprule: entity rules associated with sets or subsets of rules



rule_id int 4 yes


9.1.10 ct_ruleset_to_accnt_rolluprule: account rules associated with sets or subsets of rules



rule_id int 4 yes


9.2 Consolidation rules

9.2.1 ct_consrule: consolidation rules


amount_type int 4 yes type of amounts processed:

0 → in original currency

1 → converted

2 → consolidated

cdesc image 16 yes



condition smallint 2 yes trigger condition:

0 → none

1 → consolidation without opening balances

2 → consolidation with opening balances

3 → no effect on opening if opening balance

id int 4 no uidx



options smallint 2 yes options:


2 → incremental consolidation

4 → load data at all amount levels

8 → deactivate carry-over flow calculations

16 → deactivate analysis hierarchy calculations

32 → apply processing at each level

64 → only process reporting units without package data

128 → only process amounts in a different currency from the consolidation currency

256 → outgoing reporting unit: do not reverse closing flow





Rules


sub_scope_crit smallint 2 yes criteria for selecting intra subscope data:

0 → exclude data from original reporting unit, partner or stock in the same subscope

1 → include data from the original reporting unit and partner in the same subscope

2 → include data from original reporting unit and stock in the same subscope

4 → include data from partner and stock in the same subscope

9.2.2 ct_consrule_serial_selection: consolidation rules - selection


id int 4 no uidx corresponding consolidation rule [=ct_consrule.id]

serial_selection image 16 yes selection (serialized)

9.2.3 ct_consrule_serial_scope: consolidation rules - scope



serial_scope image 16 yes scope restrictions (serialized)


9.2.4 ct_consrule_serial_processing: consolidation rules - processing



serial_processing image 16 yes processing (serialized)

9.3 Preconsolidation rules

9.3.1 ct_preconsrule: preconsolidation rules


amount_type int 4 yes (always 0)

cdesc image 16 yes

condition int 4 yes (always 0)

id int 4 no uidx



options int 4 yes options:

1 → always run

2 → (always active)

8 → deactivate carry-over flow calculation

16 → deactivate analysis hierarchy calculation





Rules

9.3.2 ct_preconsrule_ser_selection: preconsolidation rule selection


id int 4 no uidx corresponding preconsolidation rule [=ct_preconsrule.id]


9.3.3 ct_preconsrule_ser_processing: preconsolidation rule processing definition


id int 4 no uidx corresponding preconsolidation rule [=ct_preconsrule.id]


9.4 Package rules

9.4.1 ct_packrule: package rules


amount_type int 4 yes (always 0)

cdesc image 16 yes

condition int 4 yes trigger condition:

0 → none

1 → package without opening balances

2 → package with opening balances

id int 4 no uidx






1 → always run

2 → (always active)




9.4.2 ct_packrule_serial_selection: package rule selection


id int 4 no uidx corresponding package rule [=ct_packrule.id]


9.4.3 ct_packrule_serial_processing: package rule processing definition


id int 4 no uidx corresponding package rule [=ct_packrule.id]



Rules

9.5 Intercompany rules

9.5.1 ct_interrule: intercompany reconciliation rules


ajust int 4 yes mode:

0 → reconciliation only

1 → automatic adjustment

buyer_sign int 4 yes calculation mode:

1 → Seller + Buyer

-1 → Seller - Buyer

cdesc image 16 yes


0 → none



3 → no effect on opening if opening balance

id int 4 no uidx






8 → deactivate carry-over flow calculation

16 → deactivate analysis hierarchy calculation

256 → outgoing reporting unit: do not reverse closing flow




priority int 4 yes adjustment priority:

0 → seller

1 → buyer

2 → lesser amount

3 → greater amount



signed int 4 yes type of reversal for Seller + Buyer calculation:

0 → do not reverse

1 → reverse accounts on credit side

2 → reverse accounts on debit side

sub_scope_crit int 4 yes criteria for selecting intra subscope data:

0 → exclude data from original reporting unit, partner or stock in the same subscope

1 → include data from the original reporting unit and partner in the same subscope

2 → include data from original reporting unit and stock in the same subscope

4 → include data from partner and stock in the same subscope

threshold float 8 yes automatic adjustment threshold


Rules

9.5.2 ct_interrule_serial_scope: scope restrictions for intercompany rules


id int 4 no uidx corresponding intercompany rule [=ct_interrule.id]

serial_scope image 16 yes scope restrictions (serialized)

9.5.3 ct_interrule_serial_inter: intercompany rules processing definition


id int 4 no uidx corresponding intercompany rule [=ct_interrule.id]

serial_inter image 16 yes processing (serialized)

9.6 SQL rules

9.6.1 ct_sqlrule: SQL rules


cdesc image 16 yes


0 → none



id int 4 no uidx











9.6.2 ct_sqlrule_serial_sql: SQL rule processing


id int 4 yes uidx corresponding SQL rule [=ct_sqlrule.id]

serial_sql image 16 yes SQL processing (serialized)

9.7 Coefficients and functions

9.7.1 ct_rulecoeff: coefficients


cdesc image 16 yes

func1_dim1_id int 4 yes dimension used as 1st argument of the 1st function [=ct_dimension.id]

func1_dim2_id int 4 yes dimension used as 2nd argument of the 1st function [=ct_dimension.id]

func1_dim3_id int 4 yes dimension used as 3rd argument of the 1st function [=ct_dimension.id]


Rules


func1_dim4_id int 4 yes dimension used as 4th argument of the 1st function [=ct_dimension.id]

func1_id int 4 yes function used [=ct_rulefunction.id]

func2_dim1_id int 4 yes dimension used as 1st argument of the 2nd function [=ct_dimension.id]

func2_dim2_id int 4 yes dimension used as 2nd argument of the 2nd function [=ct_dimension.id]

func2_dim3_id int 4 yes dimension used as 3rd argument of the 2nd function [=ct_dimension.id]

func2_dim4_id int 4 yes dimension used as 4th argument of the 2nd function [=ct_dimension.id]

func2_id int 4 yes second function used if compound coefficient [=ct_rulefunction.id]

Generator1 smallint 2 yes generating dimensions among 1st function arguments:

0 → no generating dimension

1 → generating dimension for 1st argument

2 → generating dimension for 2nd argument

4 → generating dimension for 3rd argument

8 → generating dimension for 4th argument



Generator2 smallint 2 yes generating dimensions among 2nd function arguments:

0 → no generating dimension

1 → generating dimension for 1st argument

2 → generating dimension for 2nd argument

4 → generating dimension for 3rd argument

8 → generating dimension for 4th argument

id int 4 no uidx



oper smallint 2 yes compound coefficient operator:

1 → addition

2 → subtraction

3 → division

4 → multiplication

5 → minimum

6 → maximum




type smallint 2 yes type of coefficient:

1 → simple

2 → compound


Rules

9.7.2 ct_rulefunction: functions


cdesc image 16 yes

id int 4 no uidx

LabelArg1 nvarchar 60 yes 1st argument description

LabelArg2 nvarchar 60 yes 2nd argument description

LabelArg3 nvarchar 60 yes 3rd argument description

LabelArg4 nvarchar 60 yes 4th argument description




RefTableArg1 int 4 yes reference table with the 1st argument [=ct_reftable.id]

RefTableArg2 int 4 yes reference table with the 2nd argument [=ct_reftable.id]

RefTableArg3 int 4 yes reference table with the 3rd argument [=ct_reftable.id]

RefTableArg4 int 4 yes reference table with the 4th argument [=ct_reftable.id]



type smallint 2 yes number of arguments (from 1 to 4)

9.7.3 ct_rulefunction_serial_sql: SQL function processing


id int 4 no uidx corresponding SQL function [=ct_rulefunction.id]



serial_sql image 16 yes SQL processing (serialized)

9.8 Entity Rollup Rules

9.8.1 ct_entity_rollup_rule: rules for entity rollup


cdesc image yes

condition smallint 2 yes

elim_leaf_level bit 1 yes Is true if elimination is performed at the hierarchy nodes and at leaf level. Default value is false (0).

id int 4 no uidx



options smallint 2 yes


primary_hier_enabled bit 1 yes Primary hierarchy enabled


secondary_hier_enabled

bit 1 yes Secondary hierarchy enabled


9.8.2 ct_entrolluprule_serial: entity rollup serialized data


id int 4 no uidx

serial_selection image 16 yes


Rules

9.8.3 ct_ruleset_to_ent_rolluprule: entity rules associated with sets or subsets of rules



rule_id int 4 yes


9.9 Account Rollup Rules

9.9.1 ct_account_rollup_rule: account rollup rule table


all_detailed_dim bit 1 no

cdesc image 16 yes

condition smallint 2 yes

id int 4 no uidx



options smallint 2 yes




9.9.2 ct_accnt_rollup_rule_to_dim: account rollup rule to dimension table


accnt_rule_id int 4 no

dim_id int 4 no dimension [=ct_dimension.id]


10 Sites and databases

10.1 Site management

10.1.1 ct_recipient: correspondents


address_desc nvarchar 255 yes address description

address_type lint 4 yes type of address:

1 à email (MAPI)

2 à network

3 à email (Internet)

4 à diskette

5 à database

6 à customized

id int 4 no uidx

initialized bit 1 yes is the site already initialized?

lang int 4 yes working language for sending objects run


name nvarchar 17 yes alphanumeric code of the site preceded by its parent’s profile




type int 4 yes type of correspondent:

1 à SAP Financial Consolidation site

2 à referring to an existing SAP Financial Consolidation site

3 à individual


Sites and databases

10.1.2 ct_site: profiles


allow_udv_creation int 4 yes user dimension value creator site (not used in 7.3)

aux_signatures nvarchar 4000 yes list of additional sub-pools for extended identifier allocation

father int 4 yes profile of parent site [=ct_site.signature]

id int 4 no uidx

initial_range nvarchar 4000 yes initial signature attribution for the site (covers main signature, extended identifier allocation signatures, child sites signatures)




signature int 4 yes site profile [=id-1]

signatures_range text 16 yes profile range assigned

type int 4 yes type of site:

1 → user dimension value simple site (not used in 7.3)

2 → central (or data collection) site

3 → consolidation site

4 → setup site

udv_owner int 4 yes user dimension value owner site (not used in 7.3)

SAP Financial Consolidation Database Schema GuideSites and databases CONFIDENTIAL 205

10.2 General settings

10.2.1 ct_config: configuration of the database


id int 4 no uidx number of the configuration item

ldesc1 nvarchar 40 yes description of configuration item

name nvarchar 255 yes idx value of configuration item


serial image 16 yes serialized value

type number 3 yes type of configuration item value:

1 → integer

2 → real

3 → text

4 → object

10.2.2 ct_language: working languages


ct_locale int 4 yes standard language ID (not used)

id int 4 no uidx number of the working language (from 1 to 5, and 6 for the local language)

is_active int 4 yes 1 → displayed

0 → hidden

ldesc1-6 nvarchar 120 yes description of the working language in the 6 languages




Sites and databases

10.2.3 ct_active_server: contains items saved corresponding to the servers running concurrently on the same data source


expiration_date datetime 8 no

server_certificate nvarchar 38 yes uidx

server_computer_name

nvarchar 255 yes

10.2.4 ct_active_session: contains items saved corresponding to the sessions open for the data source


server_certificate nvarchar 38 yes idx

session_certificate nvarchar 38 yes uidx

user_id int 4 yes

10.2.5 ct_md_lock: table that stores the locks for multi-dimensional data sources


datasource_id int 4 Yes idx1 ID of the multi-dimensional data source

header_dim_values nvarchar 255 yes idx1 concatenation of dimension codes that identify the lock, in hexadecimal form

locking_date datetime 8 no date locked

locking_mode nchar 1 yes type of lock. 'S': share. 'E': exclusive.



session_certificate nvarchar 38 yes certificate of the user session that locked the data. This is a key for the session_certificate column in the ct_active_session table.

10.2.6 ct_mutex: synchronization of access to resource shared by several ctserver instances


ct_lock int 4 yes

ct_name nvarchar 255 yes uidx

10.2.7 ct_pack_mutex :


id int 4 no

mutex int 4 yes

10.2.8 ct_identifier_mutex: synchronization of identifier allocation


manager_id int 4 no object type

mutex int 4 yes technical column

10.2.9 ct_identifier_pool: persisted identifier pool


last_object_id int 4 no

manager_id int 4 no idx


Sites and databases


range_id int 4 no sub-pool signature

10.2.10 ct_object_lock:


locking_date datetime 8 no

locking_mode nchar 1 no

manager_id int 4 no uidx1

object_id int 4 no uidx1

process_id int 4 no

session_certificate nvarchar 38 no

10.2.11 ct_recycled_identifier: unknown


manager_id int 4 no uidx1

object_id int 4 no uidx1

release_date float 8 no timestamp of object deletion

10.2.12 ct_scheduler: unknown


server_certificate_id char 38 no

10.2.13 wctversion: database schema version


base1 int 4 yes major release

base2 int 4 yes minor release



base3 int 4 yes schema number

base4 int 4 yes build number

lastupdate datetime 8 yes date of last update

schname nchar 8 yes cuidx1, code of the database schema

status smallint 2 yes schema status

updateuser nvarchar 32 yes windows user who updated the schema

10.2.14 ct_message: manage notifications between every instances of ctserver


body image 16 yes

last_forwarder nvarchar 200 yes

local_sender_order int 4 yes

ls_timestamp datetime 8 yes cidx2

message_id nvarchar 100 no uidx1

message_type nvarchar 510 no

recipient_address nvarchar 200 no cidx2

sender_address nvarchar 200 no

transaction_id int 4 yes

10.3 Local items

10.3.1 ct_user_config: user personal settings


definition image 16 yes preferences and settings (serialized)

id int 4 no uidx1


Sites and databases


substitution_language int 4 yes substitute working language

0 → none

1 to 6 → number of language


user_language int 4 yes last working language used

0 → none

1 to 6 → number of the language

last_connection_date datetime 8 yes last connection date of the user

10.3.2 ct_viewpoint: Web user viewpoint


id int 4 no uidx





serial_viewpoint image 16 yes definition of viewpoint (serialized)

10.3.3 ct_pivot_table: MS Excel pivot table queries


cdesc image 16 yes

id int 4 no uidx








10.3.4 ct_pivot_table_serial_pivot: pivot table query definition


id int 4 no uidx pivot table query [=ct_pivot_table.id]

serial_pivot image 16 yes definition of the query (serialized)

10.3.5 ct_allocate_identifier: IDs used and fixed for certain objects (e.g. users, functional profiles, owner groups, etc.)


manager_id int 4 yes uidx1 ID of the type of object

object_id int 4 yes uidx1 ID of the object


Sites and databases

11 Security

11.1 Users

11.1.1 ct_user: users


cdesc image 16 yes

count_docexe bit yes Do we count the number of document executions for this user:

● 0 => don't count● 1 => count

cstmdata1 nvarchar 255 yes User free text 1





datarights_id int 4 yes data access group [=ct_datarights.id]

email Nvarchar 255 yes

fnprofile_id int 4 yes functional profile [=ct_fnprofile.id]

id int 4 no uidx1


login_name nvarchar 255 yes uidx3

name nvarchar 12 yes uidx2




user_active Bit 1 yes

user_alias Nvarchar 510 yes alias in Business Object Enterprise platform (e.g. “secEnterprise:MYUSER”)

SAP Financial Consolidation Database Schema GuideSecurity CONFIDENTIAL 213


user_power Int 4 yes user privileges: 1 → guest user 2 → normal user 3 → super user 4 → kernel

user_pwd_key Nvarchar 254 yes

user_type smallint 2 yes type of user: 1 → SAP Financial Consolidation 2 → NT account 3 → External Authentication

defined_restriction bit 1 yes reserved for future use. Available since SP15 only

last_connection_date datetime 8 yes Available since SP15 only

11.1.2 ct_user_password: user passwords


id Int 4 no uidx user [=ct_user.id]

last_change_date datetime 8 yes date password was last changed

user_pwd nvarchar 512 yes password (serialised)

11.1.3 ct_user_workgroup: workgroups associated with users



workgroup_id int 4 yes uidx1 workgroup [=ct_workgroup.id]


Security

11.1.4 ct_user_profile: functional profiles associated with users


profile_id int 4 yes uidx1 funtional profile [=ct_fnprofile.id]


11.1.5 ct_user_serial

Reserved for future use. Available since SP15 only.


id int 4 yes user id [=ct_user.id]

user_serial blob 16 yes

11.2 Workgroups

11.2.1 ct_workgroup: workgroups (user groups)


cdesc image 16 yes

id int 4 no uidx






security_ctx int 4 yes context in which the functional profile will be applied (not used by SAP Financial Consolidation)


11.3 Functional profiles

11.3.1 ct_fnprofile: functional profiles


cdesc image 16 yes

id int 4 no uidx1


name nvarchar 12 yes uidx2




security_ctx int 4 yes context in which the functional profile will be applied (not used by SAP Financial Consolidation)

11.3.2 ct_fnprofile_detail: details of functional profiles


id int 4 no uidx corresponding functional profile [=ct_fnprofil.id]

wdetail image 16 yes definition of profile (serialized)

11.4 Data access groups

11.4.1 ct_datarights: data access groups


cdesc image 16 yes


Security


default_accessible smallint 2 yes access to default categories: 0 → cannot be accessed 1 → can be accessed

default_cs_restriction_id

int 4 yes default consolidation access definition [=ct_accessdef_conso.id]

default_et_restriction_id

int 4 yes default central manual journal entry access definition [=ct_accessdef_entry.id]

default_op_restriction_id

int 4 yes default write access definition [=ct_accessdef_inputanalysis.id]

default_ro_restriction_id

int 4 yes default read access definition [=ct_accessdef_inputanalysis.id]

id int 4 no uidx






11.4.2 ct_datarights_phase: data access rights by category


accessible smallint 2 yes category which can be accessed

conso_restriction int 4 yes default consolidation access definition for phase_id [=ct_accessdef_conso.id]

datarights_id int 4 yes data access group [=ct_datarights.id]

entry_restriction int 4 yes default central manual journal entry access definition for phase_id [=ct_accessdef_entry.id]



operation_restriction int 4 yes default write access definition for phase_id [=ct_accessdef_inputanalysis.id]


readonly_restriction int 4 yes default read access definition for phase_id [=ct_accessdef_inputanalysis.id]

use_default smallint 2 yes uses default values

11.4.3 ct_access_restriction: access restrictions (obsolete V9)


cdesc image 16 yes

id int 4 no uidx






11.4.4 ct_accessdef_conso: consolidation access definition

ColumnType Len. Null. Comment

cdesc image 16 yes

id int 4 no uidx







Security

11.4.5 ct_accessdef_entry: central manual journal entry access definition


cdesc image 16 yes

id int 4 no uidx






11.4.6 ct_accessdef_inputanalysis: data entry analysis access definition


cdesc image 16 yes

datasrc int 4 yes data source to which DA is applied (not used)

datasrc_prop int 4 yes data source property to which DA is applied (not used)

id int 4 no uidx







11.4.7 ct_ser_access_restr: access restriction definitions (obsolete V9)


id int 4 no uidx ID of the access definition [=ct_access_restriction .id]

serial_dimension image 16 yes list of restrictions for each dimension (serialized)

11.4.8 ct_ser_accessdef_conso: serialized fields in an access definition


id int 4 no uidx ID of the access definition [=ct_accessdef_conso.id]


11.4.9 ct_ser_accessdef_entry: serialized fields in an access definition


id int 4 no uidx ID of the access definition [=ct_accessdef_entry.id]



Security

11.4.10 ct_ser_accessdef_inputanalysis : serialized fields in an access definition


id int 4 no uidx ID of the access definition [=ct_accessdef_inputanalysis.id]


11.5 Security V2 – not used by SAP Financial Consolidation

11.5.1 ct_ace: Control for access to work groups for objects (not used by SAP Financial Consolidation)


ct_acl_id int 4 yes

ct_delete_access bit 1 yes

ct_deny bit 1 no

ct_read_body_access bit 1 yes

ct_read_header_access

bit 1 yes

ct_trustee_creation datetime 8 yes

ct_trustee_id int 4 no

ct_trustee_type int 4 no

ct_write_access bit 1 yes

id int 4 no idx

11.5.2 ct_acl: list of secure objects (not used by SAP Financial Consolidation)


ct_type int 4 yes



id int 4 no uidx

11.5.3 ct_compiled_ace: compiled form of access controls for objetcs (not used by SAP Financial Consolidation)


ct_acl_id int 4 yes idx

ct_delete_access bit 1 yes

ct_deny bit 1 yes

ct_read_body_access bit 1 yes

ct_read_header_access

bit 1 yes

ct_trustee_creation datetime 8 yes

ct_trustee_id int 4 yes

ct_trustee_type int 4 yes

ct_write_access bit 1 yes

id int 4 no uidx

11.5.4 ct_compiled_acl: compiled form of lists of secure objects (not used by SAP Financial Consolidation)


ct_type int 4 yes

id int 4 no uidx

11.5.5 ct_right: dynamic definition of access rights (not used by SAP Financial Consolidation)


ct_context int 4 yes

ct_deleted int 4 yes


Security


ct_dlldescprefix nvarchar 255 yes

ct_iddesc int 4 yes

ct_name nvarchar 255 yes

ct_parent int 4 yes

ct_rank int 4 yes

id int 4 no uidx


12 Tasks

12.1 Common item

12.1.1 ct_runnableobjects: tasks


id int 4 no uidx






wactivation int 4 yes

wdefaultpriority int 4 yes

wdetail image 16 yes

wobjtype nvarchar 80 yes

wtype int 4 yes

12.1.2 ct_schedulings: task planning


ctclosingdate datetime 8 yes

ctclosingtime int 4 yes

ctdatemask int 4 yes

ctdateunit int 4 yes

ctenddate datetime 8 yes

ctlocked int 4 yes

ctopeningdate datetime 8 no

ctopeningtime int 4 yes

ctperiodicity int 4 yes

ctprocessid int 4 yes idx1


Tasks


ctsettings image 16 yes

ctstartingdate datetime 8 yes

cttimemask int 4 yes

id int 4 no uidx


name nvarchar 12 yes idx2




12.1.3 ct_executions: settings for running tasks


id int 4 no uidx

wbeginningdate datetime 8 no

wenddate datetime 8 no

whistoryid int 4 yes

wrequestinguserid int 4 yes

wroid int 4 yes

wstatus int 4 yes

12.1.4 ct_history: log for tasks run


id int 4 no uidx



wcategory int 4 yes

wdesc image 16 yes

wendlogdate datetime 8 no

wlogdate datetime 8 no

wparenthistory int 4 yes

SAP Financial Consolidation Database Schema GuideTasks CONFIDENTIAL 225


wrootvisible int 4 yes

wsource nvarchar 32 yes

wstatus int 4 no

12.1.5 ct_history_detail: detail of log of tasks run


id int 4 no uidx


12.1.6 ct_execresults: results of tasks run


id int 4 no uidx

wdesc nvarchar 80 yes


wexecutionid int 4 yes

wobjtype nvarchar 80 yes

wresultdate datetime 8 no

12.2 Specific items

12.2.1 ct_filter_restriction: filtering consolidated and preconsolidated data to be sent


cdesc image 16 yes

id int 4 no uidx




Tasks





12.2.2 ct_ser_filter_restr: definition of filters for data to be sent


id int 4 no uidx

serial_dimension image 16 yes filtering data (serialized)

12.3 Audit

12.3.1 ct_auditdef: audit definition


cdesc image 16 yes

dimension int 4 yes dimension being searched for

id int 4 no ucidx





operator smallint 2 yes operator between ID of object being searched for and its values:

0 → none

1 → equal to

2 → like

3 → Null

4 → different

5 → not like

6 → not Null

7 → filter

8 → object



searchedmanagerid int 4 yes ID of manager of object being searched for

searchedobjectid int 4 yes ID of object being searched for

searchkind smallint 2 yes search type:

0 → object used

1 → object not used


12.3.2 ct_auditdef_serial_searcharea: area used to search for items in an audit


id int 4 no audit [=ct_auditdef.id]

searcharea image 16 yes search area: all of the objects included in the search


Tasks

12.3.3 ct_auditdef_serial_searchedid: objects searched for in an audit


id int 4 no audit [=ct_auditdef.id]

searchedvalueid image 16 yes IDs of objects to be searched for

12.4 Interface

12.4.1 ct_interface_def: datalink definition


cdesc image 16 yes

id int 4 no uidx






type int 4 yes

s4h_status int 4 yes Status of the deployment:

● non_s4h_definition = 0

● s4h_never_deployed = 1

● s4h_saved_after_deploy = 2

● s4h_deployed = 3● s4h_need_de

ployement = 4

s4h_user int 4 yes For S/4HANA definition, ID of the user that performed the deployment



s4h_date datetime 8 yes For S/4HANA definition deployment date

12.4.2 ct_interface_def_detail: detail of datalink definitions


id int 4 no uidx


12.5 Trace reports

12.5.1 ct_log: actions performed by users


action_date nvarchar 20 yes date action performed (format: yyyy/mm/dd)

action_id int 4 yes ID of action

action_time nvarchar 16 yes time action performed (format: hh:mm:ss)

comment_id int 4 yes ID of the comments

details_id nvarchar 500 yes the resource ID of the details and other IDs for other objects affected by the action

id int 4 yes unique ID for an action

main_obj_code nvarchar 300 yes code of the object affected by the action

main_obj_mgr nvarchar 100 yes type of the object affected by the action

object1 nvarchar 100 yes code of the first object in detail

object2 nvarchar 500 yes code of the second object in detail

user_name nvarchar 24 yes code of user who performed the action


Tasks

13 Common columns

13.1 ID Columns (id, owner_site, name)


id int 4 no when the object has a “name” column, the ID is in the range of creation site IDs.

name nvarchar 12 yes unique alphanumeric code for a given creation site

owner_site smallint 2 yes creation site

13.2 Short description columns in 6 languages (sdesc1-6)


sdesc1 nvarchar 30 yes short description in language 1

sdesc2 nvarchar 30 yes





13.3 Long description columns in 6 languages (ldesc1-6)


ldesc1 nvarchar 120 yes long description in language 1

ldesc2 nvarchar 120 yes


SAP Financial Consolidation Database Schema GuideCommon columns CONFIDENTIAL 231





13.4 Extra long description columns in 6 languages (xdesc1-6)


xdesc1 nvarchar 253 yes extra long description in language 1

xdesc2 nvarchar 253 yes





13.5 Security management columns (security columns)


access_mode smallint 2 yes access mode:

0 à none

1 à read

2 à write

3 à new

author_id int 4 yes user who created the object

creation_date datetime 8 yes creation date

owner_workgroup_id int 4 yes owner group

update_author_id int 4 yes user who made the last change

update_date datetime 8 yes date last changed


Common columns

13.6 HTML comments columns in 6 languages (cdesc)


cdesc image 16 yes HTML comments in six languages (binary field)

SAP Financial Consolidation Database Schema GuideCommon columns CONFIDENTIAL 233

14 Appendix 1: Utilities for SQL processing

14.1 Variables available

Key:

The variable is applied:

● for package processing (L)● for preconsolidated processing (P)● for consolidated processing (C)

The variable is available:

● in a function (F)● in an SQL rule (R)

14.1.1 Definition

[SCOPE_PERIOD] __C FR internal scope period value

[SCOPE_VERSION] __C FR internal scope version code

[RATEPERIOD] __C FR internal value for exchange rate period

[RATEVERSION] __C FR internal exchange rate version code

14.1.2 Function

[INSERT_FUNCTION] LPC F_ insert command for the function result table

[FUNCTION_TABLE] LPC FR function result table

[FUNCTION_CODE] LPC F_ internal code for function currently being run


Appendix 1: Utilities for SQL processing

14.1.3 ID

[PHASE] LPC FR internal category code

[UPDPER] LPC FR internal data entry period value

[SCOPE] __C FR internal scope code

[VARIANT] __C FR internal variant code

[CURNCY] __C FR internal consolidation currency code

[ENTITY] L__ FR reporting unit code during processing

14.1.4 Rule

[DAYBOOK] LPC _R internal code for automatic journal entry ledger

[ENUMBER] LPC _R automatic journal entry number of rule

[TECH_ORIG] LPC _R technical origin corresponding to rule

14.1.5 Table

[WORKTABLE] LPC FR data table currently being produced

[USER_TABLE] LPC FR empty table available to user

[TBL_SCOPE] __C FR top consolidation scope

[TBL_GLOBAL_SCOPE] __C FR full consolidation scope

[TBL_SHARES] __C FR stockholding of scope

[TBL_SCOPE2] __C FR top secondary consolidation scope

[TBL_GLOBAL_SCOPE2] __C FR full secondary consolidation scope

[TBL_SHARES2] __C FR stockholding of secondary scope

SAP Financial Consolidation Database Schema GuideAppendix 1: Utilities for SQL processing CONFIDENTIAL 235

14.1.6 Utility

[MARGIN] __C FR variable equal to 1 in incremental consolidation

[PERIODS] __C FR list of internal values for periods being processed

[PROCESS_ITERATION] __C FR rank of period being processed

[PERIOD] __C FR period currently being processed (including mono-period) – 0 if simultaneous multi-period processing

[SIGNATURE] LPC FR current site profile

[COLUMNS] LPC FR list of [WORKTABLE] columns

14.2 Temporary tables

Temporary tables which are linked to consolidation scopes and which can be accessed using variables during consolidation are now stored once consolidation is complete. They have the same structure as the corresponding storage tables.

The other temporary tables are not stored once consolidation is complete.

14.2.1 [TBL_SCOPE]: top consolidation scope

Structure identical to the ct_tbl_scope table

14.2.2 [TBL_GLOBAL_SCOPE]: full consolidation scope

Structure identical to the ct_tbl_global_scope table

14.2.3 [TBL_SHARES]: stockholding of scope

Structure identical to the ct_tbl_shares table



14.2.4 [TBL_SCOPE2]: top secondary consolidation scope

Structure identical to the ct_tbl_scope2 table

14.2.5 [TBL_GLOBAL_SCOPE2]: full secondary consolidation scope

Structure identical to the ct_tbl_global_scope2 table

14.2.6 [TBL_SHARES2]: stockholding of secondary scope

Structure identical to the ct_tbl_shares2 table

14.2.7 [WORKTABLE]: consolidation worktable


convamount2 float 8 no conversion difference amount property

Structure identical to the ct_coPPPP table and the column:

14.2.8 [USER_TABLE]: consolidation worktable

Structure identical to the [WORKTABLE] table

14.2.9 [FUNCTION_TABLE]: function result table


fncode int 4 no function producing the result [=ct_rulefunction.id] when a function is run, its value is given by the [FUNCTION_CODE] variable



fnarg1 int 4 no 1st argument of the function [={reftable}.id]

fnarg2 int 4 no 2nd argument of the function [*={reftable}.id]

fnarg3 int 4 no 3rd argument of the function [*={reftable}.id]

fnarg4 int 4 no 4th argument of the function [*={reftable}.id]

fnvalue float 8 no value of the function for the set of 4 arguments

14.3 List of Values

Value Options

Variations 0 → no change in scope

1 → incoming







Scope status 0 → not integrated


2 → subsidiary





Value Options

Consolidation methods 0 → not integrated



3 → equity method


14.4 Meaning of Period IDs in SAP Financial Consolidation

In SAP Financial Consolidation, there are no period tables. The ID is linked directly to the period. The ID is stored in 32 bits, which can be broken down into sub-groups used for storing the information described below:

Start End Size Sign Description Description

0 6 7 yes reserved2 not used - can be used for the week [-64: +63]

7 12 6 yes reserved1 not used - can be used for the day [-32: +31]

13 17 5 yes month month of the year [-16: +15]

18 28 11 yes year year [-1024: +1023] based on 1900

29 30 2 no type period type (0 → absolute ; 1 → relative ; 2 → mixed)

31 31 1 no reserved engine bit (not used)

To retrieve the month from a period ID, you should perform the binary comparison between the ID and the integer so that bits 13 to 17 are equal to 1 and the others are equal to 0, or 253952, and delete all of the bits from 0 to 12. This means that you should divide by 2^13, or 8192.

To retrieve the year from a period ID, you should perform the binary comparison between the ID and the integer so that bits 18 to 28 are equal to 1 and the others are equal to 0, or 536608768, and delete all of the bits from 0 to 17. This means that you should divide by 2^18, or 262144, and add 1900 to the result.


14.5 Utility: Periods in SQL

Convert a year with 4 digits and a month number to a SAP Financial Consolidation period ID:

period_id = (year_4_digits – 1900) * 262144 + month_number * 8192

Convert an alphanumeric period code in YYYY.MM format to a SAP Financial Consolidation period ID:

period_id = (convert(int,LEFT(ltrim(period_alpha),CHARINDEX('.', ltrim(period_alpha))-1)) - 1900) * 262144 + convert(int,RIGHT(rtrim(period_alpha),LEN(rtrim(period_alpha)) - CHARINDEX('.', rtrim(period_alpha)))) * 8192

Retrieve the year and month from a SAP Financial Consolidation period ID:

month_number = (period_id & 253952) / 8192

year_4_digit = 1900 + (period_id & 536608768) / 262144

Convert a SAP Financial Consolidation period ID to an alphanumeric period code:

period_alpha = ltrim(str(1900+(period_id&536608768)/262144)) + '.' + right('00'+ltrim(str((period_id&253952)/8192)),2)

or similarly:

period_alpha = convert(varchar(5),1900 + (period_id & 536608768) / 262144) + '.' + case when ((period_id & 253952) / 8192) < 10 then '0' else '' end + convert(varchar(3),(period_id & 253952) / 8192)

In Oracle:

period_alpha := to_char(1900+round(updper/262144))||'.'||lpad(to_char(round(mod(updper,262144)/8192)),2,'0')

Example 1: You want to retrieve the tax rate for the country of a reporting unit from the tax rate table in which rates are entered yearly in December. You will therefore run an SQL function applied to all of the consolidations in the year by entering the following script in the WHERE clause:

ct_taxrate.ct_period = (1900 + ([UPDPER] & 536608768) / 262144 – 1900) * 262144 + 12 * 8192

… or simply:

ct_taxrate.ct_period = ([UPDPER] & 536608768) + 12 * 8192

Example 2: You want to apply a disparity between two periods (shifting of the period depending on the source and target data entry periods) to a period:

period_dest = period_orig + (updper_dest & 536608768) - (updper_orig & 536608768) + (updper_dest & 253952) - (updper_orig & 253952) + case when (((period_orig & 253952) + (updper_dest & 253952) - (updper_orig & 253952)) / 8192) > 11 then -12 * 8192 + 262144 when (((period_orig & 253952) + (updper_dest & 253952) - (updper_orig & 253952)) / 8192) < 0 then 12 * 8192 – 262144 else 0 end



14.6 Extraction of an ID Profile in SQL

site = cast(cast(left(cast(cast(id as binary(4))&cast(0xFFF80000 as int) as binary(4)),2) as binary(2)) as int)/8

or

site = cast(cast(left(cast(id as binary(4)),2) as binary(2)) as int)/8

and the local part of the ID is (between 1 and 524287)

loc_id = cast(cast(cast(id as binary(4))&cast(0x0007FFFF as int) as binary(4)) as int)


15 Appendix 2: Schema of Tables in the Structure

15.1 Storing Data: Data Sources

Depending on its origin, data is grouped into different data sources. For example, you can have data sources for "package amounts", "conversion rates" or "scopes".

An item of data is identified in a data source in a unique way using a unique set of identification values from the data source dimensions. For certain dimensions in the data source, the identification value can be null. An item of data contains a set of values from the data source properties.

You can see an example of a data source in the following table:

Dim1 Dim2 Dim3 Prop1 Prop2

Data1 A E Null 100 10

Data2 A E H 40 0

Data3 B E Null 150 40

Data3 B E Null 150 40

In SAP Financial Consolidation, the 6 tables below provide the description of the data source:

● • The ct_datasource table provides the general properties of the data source as well as the physical name of the table containing the data.

● • The ct_datasource_dim table provides all of the dimensions identifying the data source by joining ct_datasource_dim.datasource ↔ ct_datasource.id. Each item includes the physical column name in the table containing the data, the dimension type for the data source, and the reference to the description of the dimension.

● • The ct_dimension table provides the description of a dimension and the definition of its values by joining ct_datasource_dim.dimension ↔ ct_dimension.id

● • The ct_datasource_prop table provides all of the properties belonging to an item of data in the data source by joining ct_datasource_prop.datasource ↔ ct_datasource.id. Each item includes the physical column name in the table containing the data and the reference to the description of the property.

● • The ct_ds_property table provides the description of a property and the definition of its values by joining ct_datasource_prop.property ↔ ct_ds_property.id.

15.2 Specific Case: Amounts

Because of the data load implied, data from amount data sources are not stored in a single table but in a set of tables where each item of data has its subset of identical dimensions. Its data sources are partitioned based on this subset of dimensions.


Appendix 2: Schema of Tables in the Structure

For a given partitioned data source, there is a partition table named ct_datasource.physname+’ref’, made up of an ID column and a number of columns corresponding to the subset of dimensions.

Each sub-data table will be named ct_datasource.physname+’XXXX’, XXXX being the ID in the partition table converted to a 4-character string. The structure of the sub-data table is identical to the general one without the subset of dimensions contained in the partition table.

The partitioned data sources are as follows (with the definition of the associated partition tables):

● Opening balance amounts: ct_opbalref (id, phase, updper)● Package amounts: ct_pkref (id, phase, updper)● Preconsolidated amounts: ct_pcref (id, phase, updper)

For consolidated amounts:

● If these amounts use the Financial Consolidation multi-table mode: ct_coref (id, phase, updper, scope, variant, curncy)

● If these amounts use the SAP HANA single-table mode: ct_co (in that case, ct_co contains: phase, updper, scope, variant, conscur and all other dimensions and properties)

15.3 Dimension Values: Reference Tables

The possible identification values for a dimension are grouped in a reference table. A reference table is usually a database table containing a finite set of reference values. It can also be a virtual table containing an infinite set of values, as in the case of the "period" and "journal entry number" reference tables.

In a normal reference table, each reference value can take on characteristics from another reference table and properties, besides its own ID and description. The three tables below provide the description of a reference table:

● The ct_reftable table provides the general properties of the reference table, its type (physical or virtual), and the physical name of the associated table (if physical).

● The ct_charac table provides all of the direct characteristics in a reference table by joining ct_charac.src_reftable ↔ ct_reftable.id. It indicates in which reference table the characteristic takes its values by joining ct_charac.dst_reftable ↔ ct_reftable.id. It also displays the corresponding column name in the reference table.

● The ct_rt_property table provides all of the available properties for a reference table by joining ct_rt_property.reftable ↔ ct_reftable.id. It also displays the corresponding column name in the reference table.

Characteristics are used to group reference values from a reference table based on similar subsets depending on the value of the characteristic. Because this characteristic value is a reference value from another reference table, it can also have a characteristic. This second characteristic is a sub-characteristic of the first reference table and can also be used to group its values together.

The two tables below provide the description of the sub-characteristic:

● The ct_charac table provides the description of the sub-characteristic (the fields used to define a first level characteristic are null).

● • The ct_charac_path table provides an ordered set of direct characteristics to which a given sub-characteristic is associated by joining ct_charac_path.ct_sub_charac ↔ ct_charac.id. For each segment of

SAP Financial Consolidation Database Schema GuideAppendix 2: Schema of Tables in the Structure CONFIDENTIAL 243

the direct characteristics path, the direct characteristic is displayed by joining ct_charac_path.ct_direct_charac ↔ ct_charac.id.

15.4 Multi-Dimensional Index Customization

Starting with version 9.5 of Magnitude, it is possible to configure the product to create and maintain indexes on the multi-dimensional schema. The new table ct_datasource_indexes can be modified to achieve this. After an indexing need has been determined, a row can be inserted into this table and when CtServer is restarted, it will create the new index. The exception to this is on partitioned data. Indexes on partitioned data are only created when a new partition is generated. The index customization supports composite indexes.

To create a new MD index, determine the datasource ID, partition number (null if data is not partitioned or the index should apply to all partitions) and columns (dimensions). For example, if you would like to index the INVEST-RATE datasource on the INVEST-CODE and PTFL-SUBS dimensions, you would do the following:

select idfrom ct_datasourcewhere name = 'INVEST-RATE'

This would yield: -524284

Then to obtain Columns:

select id from ct_dimensionwhere name in ('INVEST-CODE', 'PTFL-SUBS')

This would yield:

-524269 -524266

And finally, depending on the specific index options you were interested in:

insert into ct_datasource_indexes values (1, -524284, null, '-524269, -524266', 0, 0, 0, 1, 7, null)

When CtServer is next restarted, it will detect the change and create a non-clustered, decending, custom index on the data table associated with the INVEST-RATE datasource on the columns associated with the INVEST-CODE and PTFL-SUBS dimensions. Also, by assigning 7 to the table_scope value, indexes in this manner will be used for permanent, work and temporary tables on this combination of this datasource and dimensions.


Appendix 2: Schema of Tables in the Structure

15.5 Diagram

SAP Financial Consolidation Database Schema GuideAppendix 2: Schema of Tables in the Structure CONFIDENTIAL 245

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free LanguageSAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders, and abilities.


Important Disclaimers and Legal Information

SAP Financial Consolidation Database Schema GuideImportant Disclaimers and Legal Information CONFIDENTIAL 247

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

Date post:	18-Jan-2022
Category:	Documents
Upload:	others
View:	8 times
Download:	0 times

SAP Financial Consolidation Database Schema Guide

Documents