C_CollsAcctCreditMgmtSummary
Collectoins Account Credit Summary
C_CollsAcctCreditMgmtSummary is a Consumption CDS View that provides data about "Collectoins Account Credit Summary" in SAP S/4HANA. It reads from 1 data source (R_CollsAcctCreditMgmtSummary) and exposes 8 fields with key fields BusinessPartner, CollectionSegment. It is exposed through 3 OData services (UI_COLL_MD_MANAGE, UI_HOBRECEIVABLES_DISPLAY, UI_PROCESSRECEIVABLES_MANAGE). It is used in 2 Fiori applications: Manage Collections Master Data, Display Head Office Receivables. Part of development package ODATA_PROCESS_RECEIVABLES.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_CollsAcctCreditMgmtSummary | R_CollsAcctCreditMgmtSummary | projection |
Annotations (9)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Collectoins Account Credit Summary | view | |
| ObjectModel.representativeKey | CollectionSegment | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| AccessControl.personalData.blocking | #BLOCKED_DATA_EXCLUDED | view | |
| VDM.viewType | #CONSUMPTION | view | |
| Metadata.allowExtensions | true | view |
OData Services (3)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_COLL_MD_MANAGE | UI_COLL_MD_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_HOBRECEIVABLES_DISPLAY | UI_HOBRECEIVABLES_DISPLAY | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_PROCESSRECEIVABLES_MANAGE | UI_PROCESSRECEIVABLES_MAN | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
Fiori Apps (2)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F5400 | Manage Collections Master Data | Transactional | Use this app to activate customers for Collections Management processes. For activated accounts, you can maintain Collection Groups per Collection Segments as well as assign Specialists on Collection Segment level. |
| F5401 | Display Head Office Receivables | Transactional | If head office / branch relationships are used in SAP FI-AR, the work list entries in SAP Collections Management can be created on the branch level. Accordingly, only the branch related FI line items are shown on the Invoices list in the Process Receivables app. The app Head Office Receivables can be called via the button Display Head Office Receivables in the Process Receivables app. The button is only available, if such a relationship is maintained for the customer. The app provides the information on customer recevievables and related objects (dispute cases, promises to pay, resubmissions, company relationships, notes) from the perspective of the head office. Unlike the Process Receivables, the creation of new objects is not possible in this app. |
Manage Collections Master Data
Business Role: Accounts Receivable Accountant
Use this app to activate customers for Collections Management processes. For activated accounts, you can maintain Collection Groups per Collection Segments as well as assign Specialists on Collection Segment level.
Display Head Office Receivables
Business Role: Accounts Receivable Accountant
If head office / branch relationships are used in SAP FI-AR, the work list entries in SAP Collections Management can be created on the branch level. Accordingly, only the branch related FI line items are shown on the Invoices list in the Process Receivables app. The app Head Office Receivables can be called via the button Display Head Office Receivables in the Process Receivables app. The button is only available, if such a relationship is maintained for the customer.The app provides the information on customer recevievables and related objects (dispute cases, promises to pay, resubmissions, company relationships, notes) from the perspective of the head office. Unlike the Process Receivables, the creation of new objects is not possible in this app.
Fields (8)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | BusinessPartner | BusinessPartner | ||
| KEY | CollectionSegment | CollectionSegment | ||
| CreditRiskClass | CreditRiskClass | |||
| virtualCreditLimitAmountukm_credit_limit | ||||
| virtualCrdtLimitUtilznCriticalitychar1 | ||||
| _BusinessPartner | _BusinessPartner | |||
| _CollectionSegment | _CollectionSegment | |||
| _CreditManagementBP | _CreditManagementBP |
@EndUserText: { label: 'Collectoins Account Credit Summary' }
@ObjectModel: { representativeKey: 'CollectionSegment',
semanticKey: [ 'CollectionSegment' ],
usageType: { dataClass: #TRANSACTIONAL,
sizeCategory: #L,
serviceQuality: #C } }
@AccessControl: { authorizationCheck: #CHECK,
personalData: { blocking: #BLOCKED_DATA_EXCLUDED } }
@VDM: { viewType: #CONSUMPTION,
usage: { type: [ #TRANSACTIONAL_PROCESSING_SERVICE ] } }
@Metadata: { allowExtensions: true }
@Consumption: { dbHints: [ 'USE_HEX_PLAN' ] }
define root view entity C_CollsAcctCreditMgmtSummary
as projection on R_CollsAcctCreditMgmtSummary
{
// VDM Fields
key BusinessPartner,
key CollectionSegment,
@ObjectModel: { text: { element: [ 'CreditRiskClassName' ] } }
CreditRiskClass,
// Text Elements
_CreditManagementBP._CreditRiskClass._Text.CreditRiskClassName as CreditRiskClassName : localized,
// Virtual Fields
@Semantics: { amount: { currencyCode: 'CreditSegmentCurrency' } }
@ObjectModel: { virtualElement: true,
virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_CREDIT_VE' }
virtual CreditLimitAmount : ukm_credit_limit,
@ObjectModel: { virtualElement: true,
virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_CREDIT_VE' }
virtual CreditLimitUtilizationPct : ukm_credlimit_used,
@Semantics: { currencyCode: true }
@ObjectModel: { virtualElement: true,
virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_CREDIT_VE' }
virtual CreditSegmentCurrency : ukm_sgm_currency,
@Semantics: { amount: { currencyCode: 'CreditSegmentCurrency' } }
@ObjectModel: { virtualElement: true,
virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_CREDIT_VE' }
virtual CustomerCreditExposureAmount : ukm_sgm_amount,
@ObjectModel: { virtualElement: true,
virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_CREDIT_VE' }
virtual CrdtLimitUtilznCriticality : char1,
// Exposed Associations
_BusinessPartner,
_CollectionSegment,
_CreditManagementBP
}
Learn More
- What Is a CDS View in SAP S/4HANA?
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- CDS View Annotations — A Complete Guide
- CDS View Field Mapping and Associations
- Understanding the SAP S/4HANA Data Model
- CDS View Extensions and Custom Fields in SAP S/4HANA
- Released APIs and Stability Contracts in SAP S/4HANA