C_CollsMgmtBusinessPartnerTP
Collections Management: Business Partner
C_CollsMgmtBusinessPartnerTP is a Consumption CDS View that provides data about "Collections Management: Business Partner" in SAP S/4HANA. It reads from 1 data source (R_CollsMgmtBusinessPartnerTP) and exposes 11 fields with key field BusinessPartner. It is exposed through 1 OData service (UI_COLL_MD_MANAGE). It is used in 1 Fiori application: Manage Collections Master Data. Part of development package ODATA_COLLECTIONS_MASTER_DATA.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_CollsMgmtBusinessPartnerTP | R_CollsMgmtBusinessPartnerTP | projection |
Annotations (9)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Collections Management: Business Partner | view | |
| ObjectModel.representativeKey | BusinessPartner | 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 (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_COLL_MD_MANAGE | UI_COLL_MD_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
Fiori Apps (1)
| 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. |
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.
Fields (11)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | BusinessPartner | BusinessPartner | ||
| Customer | Customer | |||
| CollectionProfile | _BusPartCollsProfileAssgmtTP | CollectionProfile | ||
| LastChangeDateTime | LastChangeDateTime | |||
| BusinessPartnerName | _BusinessPartner | BusinessPartnerName | ||
| CustomerName | _Customer | CustomerName | ||
| CollectionsProfileNamelocalized | ||||
| OrganizationBPName1 | _BusinessPartner | OrganizationBPName1 | ||
| OrganizationBPName2 | _BusinessPartner | OrganizationBPName2 | ||
| _BusinessPartner | _BusinessPartner | |||
| _Customer | _Customer |
@EndUserText: { label: 'Collections Management: Business Partner' }
@ObjectModel: { representativeKey: 'BusinessPartner',
semanticKey: [ 'BusinessPartner' ],
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_CollsMgmtBusinessPartnerTP
provider contract transactional_query
as projection on R_CollsMgmtBusinessPartnerTP
{
// VDM Fields
@ObjectModel: { text: { element: [ 'BusinessPartnerName' ] } }
key BusinessPartner,
@ObjectModel: { text: { element: [ 'CustomerName' ] } }
Customer,
@ObjectModel: { text: { element: [ 'CollectionsProfileName' ] } }
_BusPartCollsProfileAssgmtTP.CollectionProfile,
LastChangeDateTime,
// Text Fields
_BusinessPartner.BusinessPartnerName,
_Customer.CustomerName,
_BusPartCollsProfileAssgmtTP._CollectionsProfile._Text.CollectionsProfileName : localized,
// Elements for search
_BusinessPartner.OrganizationBPName1,
_BusinessPartner.OrganizationBPName2,
// Exposed Associations
_BusinessPartner,
_Customer,
// BO Compositions
_BusPartCollsProfileAssgmtTP : redirected to composition child C_BusPartCollsProfileAssgmtTP,
_BPCollsSegmentAssignmentTP : redirected to composition child C_BPCollsSegmentAssignmentTP
}
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