MDGF Data Modelling for Funds Management Part 2
Tags:
Introduction
SAP Master Data Governance (MDG) is used for embedded MDM, that is, out-of-the-box, domain specific master data governance to centrally create, change and distribute master data with a focus on SAP Business Suite.
Domain specific content (data models, user interfaces, workflows) is provided as part of the standard for several application areas. SAP Master Data Governance for Financials at present does not include support for governing master data objects for the Funds Management module.
This document is sequel of the earlier document MDGF Data Modelling for Funds Management Part 1 which provided an overview of modelling 2 standard objects in Funds Management using SAP Master Data Governance:
- Fund
- Funds Center with Hierarchy
In this document the following 2 standard objects in Funds Management are covered from data modeling perspective:
- Functional Area
- Commitment Item with Hierarchy
SAP MDG-F includes standard delivered data model 0G which can be extended as described in this document Extend Data Model by New Fields
Overview MDG-F data modeling
Data Modelling in MDG-F on a high level involves following steps:
- Extend standard delivered data model 0G
- Model entities
- Model entity specific attributes
- Model relationships between entities
This document assumes expertise of the user to do each of the above steps. The entities, attributes and the relationships that are required to be modeled to support master data governance of the 3 standard entities is covered next.
Functional Area
Quick facts
ECC table: TFKB
ECC text table: TFKBT
Data element: FKBER
The data modelling of the Functional Area entity is based on the following ER diagram.
Figure 1: ER Diagram of Functional Area
The ER diagram above is designed to capture the following information for Functional Area master data:
Table 1.1: Functional Area master data
Name of the Field | Type | Length | Entity SU type |
|---|---|---|---|
Functional Area | CHAR | 16 | Type 1 – Main Entity |
FM: Authorization Group of Functional Area | CHAR | 10 | Attribute |
Expiration Date | DATS | 8 | Attribute |
Appropriation Text Part 1 | CHAR | 60 | Attribute |
Appropriation Text Part 2 | CHAR | 60 | Attribute |
Operating Flag | CHAR | 1 | Attribute |
Appropriation Bill Schedule | CHAR | 40 | Attribute |
Appropriation Category | CHAR | 10 | Attribute |
Appropriation Type | CHAR | 3 | Attribute |
FM: Valid from date | DATS | 8 | Attribute |
FM: Valid to date | DATS | 8 | Attribute |
Control Type | CHAR | 4 | Attribute |
Approp Type PreRoyal Assent Name 1 | CHAR | 60 | Attribute |
Approp Type PreRoyal Assent Name 2 | CHAR | 60 | Attribute |
Appropriation Item | CHAR | 4 | Attribute |
Active Flag | CHAR | 1 | Attribute |
Transaction Data Check | CHAR | 1 | Attribute |
Functional Area Long Text | CHAR | 420 | Attribute |
Availability Control Specification | CHAR | 1 | Attribute |
Name | CHAR | 20 | Text table attribute |
Medium text | CHAR | 40 | Text table attribute |
Long text | CHAR | 60 | Text table attribute |
The attributes of the Functional Area entity are tabulated below.
Table 1.2: Functional Area attributes
Attribute | Data Element | Required Field | Description |
|---|---|---|---|
ZZFAAUTHG | FM_AUTHGR_FAREA | No | FM: Authorization Group of Functional Area |
ZZFAVLDFR | FM_DATAB | Yes | FM: Valid from date |
ZZFAVLDTO | FM_DATBIS | Yes | FM: Valid to date |
ZZFAXPDAT | FM_DATE_EXP | No | Expiration Date |
ZZFAATXT1 | ZAPPTXT1 | No | Appropriation Text Part 1 |
ZZFAATXT2 | ZAPPTXT2 | No | Appropriation Text Part 2 |
ZZFAOFLG | ZOPERATE | No | Operating Flag |
ZZFAAPBIL | ZBILLSCH | No | Appropriation Bill Schedule |
ZZFAAPCT | ZAPP_CAT | No | Appropriation Category |
ZZFAAPTP | ZAPP_TYPE | No | Appropriation Type |
ZZFACTTP | ZCT_TYP | No | Control Type |
ZZFAAPPR1 | ZROYALTX1 | No | Approp Type PreRoyal Assent Name 1 |
ZZFAAPPR2 | ZROYALTX2 | No | Approp Type PreRoyal Assent Name 2 |
ZZFAAPPIT | ZAPP_ITEM | No | Appropriation Item |
ZZFAACFLG | ZACTIVE | No | Active Flag |
ZZAVAILCT | ZDEAVAILCTRL | No | Availability Control Specification |
ZZFALGTXT | ZDELONGTEXT | No | Functional Area Long Text |
ZZFATRCHK | WDY_BOOLEAN | No | Functional Area Transaction Data check |
The attributes of the Functional Area entity tabulated below are language dependent.
Table 1.3: Functional Area attributes (language dependent)
Field Name | Type | Length | Required Field | Description |
|---|---|---|---|---|
TXTSH | CHAR | 20 | Name | |
TXTMI | CHAR | 40 | Description | |
TXTLG | CHAR | 60 | Long Description |
The Functional Area entity has the below related entities which need to be modelled in MDG-F.
Table 1.4: Related entities for Functional Area
Entity Type | Z_FUNCARE | ACCOUNT | CCTR | CELEM |
|---|---|---|---|---|
Description | Functional Area | Account | Cost Center | Cost Element |
Definition | Functional Area | Account | Cost Center | Cost Element |
Storage/Use Type | 1 - Changeable via Change Request; Generated Database Tables | 1 - Changeable via Change Request; Generated Database Tables | 1 - Changeable via Change Request; Generated Database Tables | 1 - Changeable via Change Request; Generated Database Tables |
Validity of Entity | Edition | Edition | Edition | Edition |
Data Element | FKBER | USMDZ1_ACCOUNT | USMDZ1_CCTR | USMDZ1_CELEM |
Hierarchy | No Hierarchy | No Hierarchy | No Hierarchy | No Hierarchy |
Validity / Hierarchy | not relevant | not relevant | not relevant | not relevant |
Key Assignment | Key Cannot Be Changed; No Internal Key Assignment | Key Cannot Be Changed; No Internal Key Assignment | Key Cannot Be Changed; No Internal Key Assignment | Key Cannot Be Changed; No Internal Key Assignment |
Language-Dependent Texts | yes | yes | yes | yes |
Long Text: Length | 60 | 50 | 0 | 0 |
Medium Text: Length | 40 | 0 | 40 | 40 |
Short Text: Length | 20 | 20 | 20 | 20 |
Attachments | yes | yes | yes | yes |
Search Help (when not available from data element) | not relevant | not relevant | not relevant | not relevant |
The Functional Area entity has the following relationship types that need to be maintained in MDG-F.
Table 1.5: Functional Area relationships
Field Name | Field Type | Relationship type | From entity type | To-entity | Cardinality | No Existence Check |
|---|---|---|---|---|---|---|
Z_FUNCACC | Relationship | Referencing | FUNCAREA | ACCOUNT | 0:N | |
Z_FNCCCTR | Relationship | Referencing | FUNCAREA | CCTR | 0:N | |
Z_FNCCELM | Relationship | Referencing | FUNCAREA | CELEM | 0:N |
Commitment item
Quick facts
ECC table: FMCI
ECC text table: FMCIT
ECC hierarchy table: FMHICI
Data element: FM_FIPEX
The data modeling of the Commitment Item entity is based on the following ER diagram.
Figure 2: ER Diagram of Commitment Item
The data modeling of the Commitment Item Hierarchy entity is based on the following ER diagram.
Figure 3: ER Diagram of Commitment Item Hierarchy
The ER diagram above is designed to capture the following information for Commitment Item master data:
Table 2.1: Commitment Item master data
Name of the Field | Type | Length | Entity SU type |
|---|---|---|---|
Financial Management Area | CHAR | 4 | Type 3 |
Commitment Item | CHAR | 24 | Type 1 – Main entity |
Name | CHAR | 20 | Text table attribute |
Description 1 | CHAR | 50 | Text table attribute |
Description 2 | CHAR | 50 | Text table attribute |
Description 3 | CHAR | 50 | Text table attribute |
FM: Valid from date | DATS | 8 | Attribute |
FM: Valid to date | DATS | 8 | Attribute |
Attribute: Can be Posted To | NUMC | 1 | Attribute |
Financial transaction | NUMC | 2 | Attribute |
Commitment Item Category | NUMC | 1 | Attribute |
Commitment Item Type | CHAR | 3 | Attribute |
Standard Variant | Char | 1 | Attribute |
Superior Commitment Item (standard Hierarchy) | CHAR | 24 | Type 1 – Referencing relationship |
Statistical commitment item | CHAR | 1 | Attribute |
Authorization Groups of the Commitment Item | CHAR | 10 | Attribute |
Funds Centre (Default Value in a Commitment Item) | CHAR | 16 | Type 1 – Referencing relationship |
Fiscal Year | NUMC | 4 | Type 3 - Leading |
Commitment item criterion category | CHAR | 5 | Attribute |
Carry forward item category for commitment item | CHAR | 2 | Type 3 - Referencing |
No Budget for Future Years | CHAR | 1 | Attribute |
Relevant to total costs | CHAR | 1 | Attribute |
Not relevant for budget print | CHAR | 1 | Attribute |
Able to carry forward at fiscal year change | CHAR | 1 | Attribute |
(Negative) clearing item | CHAR | 1 | Attribute |
Negative Budget Permitted | CHAR | 1 | Attribute |
District | CHAR | 4 | Attribute |
Local authorities: Budget execution account | CHAR | 1 | Attribute |
Budget balancing concept | CHAR | 1 | Attribute |
Indicator: NDA Budget | CHAR | 1 | Attribute |
Indicator: Accrued Budget | CHAR | 1 | Attribute |
Expiration Date | DATS | 8 | Attribute |
Commitment Item Long Text | CHAR | 420 | Attribute |
Account Category | CHAR | 2 | Attribute |
PBF Account Category | NUMC | 2 | Attribute |
Account Chart Type | CHAR | 10 | Attribute |
Account Natural Sign | CHAR | 2 | Attribute |
Account Used on Actuals | CHAR | 1 | Attribute |
Account Related Entity Enabled | CHAR | 1 | Attribute |
Account Related Entity Required | CHAR | 1 | Attribute |
Account SPP Required | CHAR | 1 | Attribute |
Account Jurisdiction Required | CHAR | 1 | Attribute |
Account Impacts Underlying Cash | CHAR | 1 | Attribute |
Account Fiscal Balance Impact | CHAR | 1 | Attribute |
Account Assumed Related Entity | CHAR | 24 | Attribute |
Account Control Type Restriction | CHAR | 4 | Attribute |
Account Used in Adjustments | CHAR | 1 | Attribute |
Account Movement Account Required | CHAR | 1 | Attribute |
Account Administered Approp Req | CHAR | 1 | Attribute |
Account Cash Flow Sign | CHAR | 2 | Attribute |
Account Cash Flow Mapping | CHAR | 24 | Attribute |
Account Cash REC Sign | CHAR | 2 | Attribute |
Account RECON Mapping | CHAR | 24 | Attribute |
Account Impacts GFS Revenue | CHAR | 1 | Attribute |
Account Impacts GFS Expense | CHAR | 1 | Attribute |
Account Impacts GFS Capital | CHAR | 1 | Attribute |
Postable | CHAR | 1 | Attribute |
BO Flag 01 | CHAR | 2 | Attribute |
Account EQ-Accumulated Results | CHAR | 1 | Attribute |
Account EQ - Total Capital | CHAR | 1 | Attribute |
Account EQ – Asset Revaluation Reserve | CHAR | 1 | Attribute |
Account EQ – Foreign Currency Translation Reserve | CHAR | 1 | Attribute |
Account EQ – Administered Investments Reserve | CHAR | 1 | Attribute |
Account EQ – Statutory Funds | CHAR | 1 | Attribute |
Account EQ – Other Reserve | CHAR | 1 | Attribute |
Account – Non Financial Assets | CHAR | 1 | Attribute |
Account - Contingencies | CHAR | 1 | Attribute |
Account – Financial Instruments | CHAR | 1 | Attribute |
Movement Account – Future 1 | CHAR | 1 | Attribute |
Movement Account – Future 2 | CHAR | 1 | Attribute |
IsMvtAct | CHAR | 1 | Attribute |
Account – Future A | CHAR | 1 | Attribute |
Account – Future B | CHAR | 1 | Attribute |
Commitment Item Transaction Data check | CHAR | 1 | Attribute |
The following information for Commitment Item Hierarchy master data is captured in the data modeling:
Table 2.2: Commitment Item Hierarchy master data
Name of the Field | Type | Length | Entity type |
|---|---|---|---|
Financial Management Area | CHAR | 4 | Type 3 |
Commitment Item | CHAR | 24 | Type 1 |
Commitment Item Hierarchy Variant | CHAR | 3 | Type 3 |
The attributes of the Commitment Item entity are tabulated below.
Table 2.3: Commitment Item attributes
Attribute | Data Element | Required Field | Description |
|---|---|---|---|
ZZCITRCHK | WDY_BOOLEAN | No | Commitment Item Transaction Data check |
ZZCIVLDFR | FM_DATAB | Yes | FM: Valid from date |
ZZCIVLDTO | FM_DATBIS | Yes | FM: Valid to date |
ZZKATEG | FM_KATEG | No | Attribute: Can be Posted To |
ZZFIVOR | FM_FIVOR | Yes | Financial transaction |
ZZPOTYP | FM_POTYP | Yes | Commitment Item Category |
ZZFPART | FM_FPART | No | Commitment Item Type |
ZZSTVAR | FM_STVAR | No | Standard Variant |
ZZSTATS | FM_STATPOS | No | Statistical commitment item |
ZZCIAUTHG | FM_AUTHGRP | No | Authorization Groups of the Commitment Item |
ZZNCBUD | FM_NCBUD | No | No Budget for Future Years |
ZZKRTYP | FM_KRTYP | No | Commitment item criterion category |
ZZGKFLG | FM_GKFLG | No | Relevant to total costs |
ZZDRUCK | FM_DRUCK | No | Not relevant for budget print |
ZZCFFLG | FM_CFFLG | No | Able to carry forward at fiscal year change |
ZZCVFLG | FM_CVFLG | No | (Negative) clearing item |
ZZNEGBUD | FM_NEG_BUDGET_FLG | No | Negative Budget Permitted |
ZZBEZIRK | FM_BEZIRK | No | District |
ZZUBFLG | FM_UBFLG | No | Local authorities: Budget execution account |
ZZHSFLG | FM_HSFLG | No | Budget balancing concept |
ZZNDAKZ | FM_NDAB | No | Indicator: NDA Budget |
ZZAZPKZ | FM_AZPB | No | Indicator: Accrued Budget |
ZZDATEXP | FM_DATE_EXP | No | Expiration Date |
ZZCILGTXT | ZDELONGTEXT | No | Commitment Item Long Text |
ZZACTCAG | ZACTCAG | No | Account Category |
ZZPBFACCT | ZDEACCAT | No | PBF Account Category |
ZZCHARTYP | ZCHARTTYP | No | Account Chart Type |
ZZACTSIGN | ZACTSIGN | No | Account Natural Sign |
ZZACTUSE | ZACTUSE | No | Account Used on Actuals |
ZZRELNEED | ZRELNEED | No | Account Related Entity Enabled |
ZZRELREQ | ZRELREQ | No | Account Related Entity Required |
ZZSPPREQ | ZSPPREQ | No | Account SPP Required |
ZZJURREQ | ZJURREQ | No | Account Jurisdiction Required |
ZZCASHIMP | ZCASHIMP | No | Account Impacts Underlying Cash |
ZZFBALIMP | ZFBALIMP | No | Account Fiscal Balance Impact |
ZZRELUSE | ZRELUSE | No | Account Assumed Related Entity |
ZZCT_TYP | ZCT_TYP | No | Account Control Type Restriction |
ZZADJUSE | ZADJUSE | No | Account Used in Adjustments |
ZZMOVEREQ | ZMOVEREQ | No | Account Movement Account Required |
ZZADMAPP | ZADMAPP | No | Account Administered Approp Req |
ZZCFLSIGN | ZCFLSIGN | No | Account Cash Flow Sign |
ZZFLOWMAP | ZFLOWMAP | No | Account Cash Flow Mapping |
ZZRECSIGN | ZRECSIGN | No | Account Cash REC Sign |
ZZRECMAP | ZRECMAP | No | Account RECON Mapping |
ZZGFSREV | ZGFSREV | No | Account Impacts GFS Revenue |
ZZGFSEXP | ZGFSEXP | No | Account Impacts GFS Expense |
ZZGFSCAP | ZGFSCAP | No | Account Impacts GFS Capital |
ZZPSTABLE | ZPOSTABLE | No | Postable |
ZZBORPT01 | ZBORPT_01 | No | BO Flag 01 |
ZZACCNT01 | ZACCNT_01 | No | Account EQ-Accumulated Results |
ZZACCNT02 | ZACCNT_02 | No | Account EQ - Total Capital |
ZZACCNT03 | ZACCNT_03 | No | Account EQ – Asset Revaluation Reserve |
ZZACCNT04 | ZACCNT_04 | No | Account EQ – Foreign Currency Translation Reserve |
ZZACCNT05 | ZACCNT_05 | No | Account EQ – Administered Investments Reserve |
ZZACCNT06 | ZACCNT_06 | No | Account EQ – Statutory Funds |
ZZACCNT07 | ZACCNT_07 | No | Account EQ – Other Reserve |
ZZACCNT08 | ZACCNT_08 | No | Account – Non Financial Assets |
ZZACCNT09 | ZACCNT_09 | No | Account - Contingencies |
ZZACCNT10 | ZACCNT_10 | No | Account – Financial Instruments |
ZZACCNT11 | ZACCNT_11 | No | Movement Account – Future 1 |
ZZACCNT12 | ZACCNT_12 | No | Movement Account – Future 2 |
ZZTBA | TBA | No | IsMvtAct |
ZZFUTRA | ZFUTRA | No | Account – Future A |
ZZFUTRB | ZFUTRB | No | Account – Future B |
The attributes of the Commitment Item Text (Z_CMMTXT) entity tabulated below are language dependent.
Table 2.4: Commitment Item attributes (language dependent)
Field Name | Type | Length | Required Field | Description |
|---|---|---|---|---|
ZZCINAME | CHAR | 20 | Name | |
ZZCIDESC1 | CHAR | 50 | Description 1 | |
ZZCIDESC2 | CHAR | 50 | Description 2 | |
ZZCIDESC3 | CHAR | 50 | Description 3 |
The Commitment Item entity has the below given related entities which need to be modeled in MDG-F.
Table 2.5: Related entities for Commitment Item
Entity | Z_FUNDCTR | Z_FMAREA | Z_CMMTXT | Z_VPTYP |
|---|---|---|---|---|
Description | Fund Center | Financial Management Area | Commitment Item Language dependent texts | Carry forward item category for commitment item |
Storage/Use Type | 1 - Changeable via Change Request; Generated Database Tables | 3 - Not Changeable via MDG; No Generated tables | 4 - Changeable via Other Entity Type; Generated Database Tables | 3 - Not Changeable via MDG; No Generated tables |
Validity of entity | Edition | No edition | Edition | No edition |
Data element | FISTL | FIKRS | FM_VPTYP | |
Hierarchies | Not Version-dependent / Not Cross-name | No Hierarchy | No Hierarchy | No Hierarchy |
Validity / Hierarchy | Hierarchy is Edition Dependent | not relevant | not relevant | not relevant |
Key assignment | Key cannot be changed; No internal key assignment | Key cannot be changed; No internal key assignment | Key cannot be changed; No internal key assignment | Key cannot be changed; No internal key assignment |
Language Dependent Texts | yes | not relevant | not relevant | not relevant |
Long text: Length | 60 | not relevant | not relevant | not relevant |
Medium text: Length | 40 | not relevant | not relevant | not relevant |
Short Text: Length | 20 | not relevant | not relevant | not relevant |
Deletion Allowed | yes | yes | yes | yes |
The Commitment Item Hierarchy entity has the below related entities which need to be modeled in MDG-F.
Table 2.6: Related entities for Commitment Item Hierarchy
Entity | Z_COMMIT | Z_FMAREA | Z_COMMITH |
|---|---|---|---|
Description | Commitment Item | Financial Management Area | Commitment Item Hierarchy |
Storage/Use Type | 1 - Changeable via Change Request; Generated Database Tables | 3 - Not Changeable via MDG; No Generated tables | 3 - Cannot be changed by MDG; no generated tables |
Validity of entity | Edition | No edition | No Edition |
Data element | FM_FIPEX | FIKRS | ZDE_CI_VARNT |
Hierarchies | Not Version-dependent / Not Cross-name | No Hierarchy | No Hierarchy |
Validity / Hierarchy | Hierarchy is Edition Dependent | not relevant | Hierarchy is Not Edition Dependent |
Key assignment | Key cannot be changed; No internal key assignment | Key cannot be changed; No internal key assignment | Key Cannot Be Changed; No Internal Key Assignment |
Language Dependent Texts | not relevant | not relevant | not relevant |
Long text: Length | not relevant | not relevant | not relevant |
Medium text: Length | not relevant | not relevant | not relevant |
Short Text: Length | not relevant | not relevant | not relevant |
Deletion Allowed | yes | yes | yes |
Search help (unless there are data elements available) | not relevant | not relevant | not relevant |
Additional Entity Types in Hierarchies
The following table illustrates the entity types used in Commitment Item entity type for hierarchy modeling:
Table 2.7: Additional Entity Types for Commitment Item
Entity Type of Node | Use |
|---|---|
Z_COMMIT | No Special Use |
Z_COMMITH | Hierarchy Name |
The Commitment Item Hierarchy entity has the following relationship types maintained in MDG-F.
Table 2.8: Commitment Item Hierarchy relationships
Field Name | Field Type | Relationship type | From entity type | To-entity | Cardinality | Data element | No Existence Check |
|---|---|---|---|---|---|---|---|
Z_FMACMHY | Relationship | leading | Z_FMAREA | Z_COMMITH | 1: N |
Summary
In this document, the following MDG-Financials master data objects have been covered from the data modeling perspective:
- Functional Area
- Commitment Item with Hierarchy
Additional Information
How-to Guides
MDGF Data Modelling for Funds Management Part 1
Extend Data Model by New Fields | SCN
In order to replicate active master data from MDG-F to the back end ECC tables refer the below guide on SAP SCN
How to Guide | Description |
|---|---|
ALE Replication from MDG Hub to ERP Using the Same Client in MDG-F | This guide provides you with the knowledge you need to setup an ALE scenario for replication of MDG-F entities into the same physical client system (MDG hub and ERP system share the same client). |
Follow me onGoogle+
