offdataai
SAP · data model template

SAP FSCM Credit Management Analytics data model

Kimball warehouse for SAP FSCM Credit Management: a periodic exposure-snapshot fact (UKM_ITEM aggregated per business partner, credit segment, and snapshot date) carrying credit limit, exposure liability categories, available credit, utilization percentage, overdue amount, and credit score for utilization-vs-limit and overdue trending; plus an event-grain credit-decision fact for individual credit checks and blocked/released documents with degenerate sales-document and credit-check identifiers. Conformed dimensions include an SCD2 business partner (UKMBP_CMS) preserving as-was risk class and credit group, credit segment, credit control area, risk class (UKM_LIMIT_RULES), company code, and date.

SAP Financial Supply Chain Management Credit Management (FIN-FSCM-CR) analytics migrated from S/4HANA / FSCM into Snowflake. Credit master data lives on the business partner (UKMBP_CMS, UKMBP_CMS_SGM) and credit exposure line items in UKM_ITEM — the modern source that replaced the legacy SD info structures S066/S067. Models a periodic exposure-snapshot fact at business partner × credit segment × snapshot date grain for utilization-vs-limit, overdue, and risk-class distribution reporting, plus an event-grain credit-decision fact for credit checks and blocked/released documents, over conformed business partner (SCD2), credit segment, credit control area, risk class, company code, and date dimensions. It is a Kimball dimensional model: fact tables at a declared grain surrounded by conformed dimensions, ready for BI tools and a semantic layer.

KimballSAPSOXGDPR
8
tables
80
columns
11
relationships
2
PII columns

Opening the template creates a project with the ERD, platform-native DDL, a dbt project and documentation already generated (recommended platform: Snowflake). Edit it in plain English or on the canvas, then ship it to any supported warehouse.

Subject areas

credit_exposurecredit_decisionsconformed_dimensions

Design decisions

  • Periodic exposure-snapshot fact at partner × segment × date grain

    FSCM tracks credit exposure as UKM_ITEM liability categories that change continuously; a periodic snapshot aggregating UKM_ITEM per business partner and credit segment each snapshot date gives stable, semi-additive balances for utilization-vs-limit, available-credit, and overdue trending without re-deriving exposure from transactions.

  • Separate event-grain credit-decision fact

    Credit checks and blocked/released documents are discrete events with their own measures (document value, exposure/limit/available at check) and a different grain than the daily balance snapshot; a transaction fact with degenerate sales-document and credit-check identifiers keeps blocked-order and decision analysis clean and additive.

  • SCD2 business partner for as-was risk class and credit group

    FSCM credit master attributes (risk class, credit group, credit limits) are re-rated over time; type-2 history on the business partner preserves the as-was risk-class and group assignment required for comparable, SOX-auditable credit-risk trend reporting.

  • Dedicated risk-class and credit-segment dimensions

    Risk-class score bands (UKM_LIMIT_RULES) and credit segments (UKMBP_CMS_SGM) are reused conformed across both facts; modelling them as their own dimensions enables risk-class distribution and per-segment limit reporting without duplicating score-band logic.

  • UKM_ITEM as the exposure source over legacy S066/S067

    FSCM consolidates credit exposure into UKM_ITEM, superseding the legacy SD info structures S066/S067; sourcing the snapshot from UKM_ITEM captures all liability categories (open order, delivery, billing, receivable) in one consistent, segment-aware exposure model.

Tables in the SAP FSCM Credit Management Analytics model

Every table with its grain, columns, types and keys. PK marks a primary key, BK a business key and PII a column classified as personal data, which gets a masking strategy by default.

Fact tables (2)

fct_credit_exposure_snapshot

Grain: one row per business partner per credit segment per snapshot date (UKM_ITEM aggregated)

Periodic snapshot fact — UKM_ITEM exposure aggregated for utilization-vs-limit trending.

ColumnTypeKeys
credit_exposure_keybigintPK
snapshot_date_keybigint
business_partner_keybigint
credit_segment_keybigint
credit_control_area_keybigint
risk_class_keybigint
company_code_keybigint
credit_limitdecimal
total_exposuredecimal
open_order_exposuredecimal
open_delivery_exposuredecimal
open_billing_exposuredecimal
open_receivable_exposuredecimal
available_creditdecimal
exposure_utilization_pctdecimal
overdue_amountdecimal
oldest_open_item_daysinteger
credit_scoreinteger
currencyvarchar
is_over_limitboolean
is_blockedboolean
is_payment_blockboolean

fct_credit_decision

Grain: one row per FSCM credit check / blocked-document event

Event-grain fact — individual credit checks and blocked/released documents.

ColumnTypeKeys
credit_decision_keybigintPK
decision_date_keybigint
business_partner_keybigint
credit_segment_keybigint
risk_class_keybigint
company_code_keybigint
sales_documentvarchar
credit_check_idvarchar
document_valuedecimal
exposure_at_checkdecimal
limit_at_checkdecimal
available_at_checkdecimal
currencyvarchar
check_resultvarchar
block_reasonvarchar
check_typevarchar
released_byvarcharPII
is_auto_releasedboolean

Dimension tables (6)

dim_date

Grain: one row per calendar day

ColumnTypeKeys
date_keybigintPK
full_datedateBK
day_of_monthsmallint
month_numbersmallint
month_namevarchar
quartersmallint
yearsmallint
is_period_endboolean

dim_business_partner

Grain: one row per business partner per SCD2 version (FSCM credit account UKMBP_CMS)

SCD type 2

ColumnTypeKeys
business_partner_keybigintPK
partner_numbervarcharBK
partner_namevarcharPII
countryvarchar
regionvarchar
industryvarchar
customer_groupvarchar
credit_groupvarchar
is_activeboolean

dim_credit_segment

Grain: one row per FSCM credit segment (UKM_ITEM segment / UKMBP_CMS_SGM)

ColumnTypeKeys
credit_segment_keybigintPK
credit_segmentvarcharBK
descriptionvarchar
segment_currencyvarchar
default_credit_limitdecimal
is_default_segmentboolean

dim_credit_control_area

Grain: one row per credit control area mapped to FSCM credit segments

ColumnTypeKeys
credit_control_area_keybigintPK
credit_control_areavarcharBK
descriptionvarchar
currencyvarchar
risk_categoryvarchar

dim_risk_class

Grain: one row per FSCM credit risk class / score band (UKM_LIMIT_RULES)

ColumnTypeKeys
risk_class_keybigintPK
risk_classvarcharBK
descriptionvarchar
score_range_lowsmallint
score_range_highsmallint
check_rulevarchar
is_high_riskboolean

dim_company_code

Grain: one row per SAP company code

ColumnTypeKeys
company_code_keybigintPK
company_codevarcharBK
company_namevarchar
countryvarchar
currencyvarchar

Relationships

Each relationship is a foreign key on the first table referencing the second.

  • fct_credit_exposure_snapshot.snapshot_date_key → dim_date (many-to-one)
  • fct_credit_exposure_snapshot.business_partner_key → dim_business_partner (many-to-one)
  • fct_credit_exposure_snapshot.credit_segment_key → dim_credit_segment (many-to-one)
  • fct_credit_exposure_snapshot.credit_control_area_key → dim_credit_control_area (many-to-one)
  • fct_credit_exposure_snapshot.risk_class_key → dim_risk_class (many-to-one)
  • fct_credit_exposure_snapshot.company_code_key → dim_company_code (many-to-one)
  • fct_credit_decision.decision_date_key → dim_date (many-to-one)
  • fct_credit_decision.business_partner_key → dim_business_partner (many-to-one)
  • fct_credit_decision.credit_segment_key → dim_credit_segment (many-to-one)
  • fct_credit_decision.risk_class_key → dim_risk_class (many-to-one)
  • fct_credit_decision.company_code_key → dim_company_code (many-to-one)

Related templates

All templates →
Start for $1

From requirements to AI-ready context, in one platform.

Describe your business in a conversation, start from a template or connect your own database. Your first model is ready in minutes.

Get startedBook a demo

Plans from $1/month · cancel any time