C_BPCollectionsSgmtQuickView
Business Partner Quick View
C_BPCollectionsSgmtQuickView is a Consumption CDS View that provides data about "Business Partner Quick View" in SAP S/4HANA. It reads from 1 data source (R_BPCollectionsSgmtQuickView) and exposes 10 fields with key fields BusinessPartner, CollectionSegment. It is exposed through 5 OData services (UI_COLL_MD_MANAGE, UI_COLLECTION_CONTACT_MANAGE, UI_CUSTOMER_CONTACT_MANAGE, ...). It is used in 4 Fiori applications: Manage Customer Contacts, Manage Resubmissions, Manage Collections Master Data, .... Part of development package ODATA_PROCESS_RECEIVABLES.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_BPCollectionsSgmtQuickView | R_BPCollectionsSgmtQuickView | projection |
Annotations (9)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Business Partner Quick View | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.representativeKey | BusinessPartner | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| AccessControl.personalData.blocking | #BLOCKED_DATA_EXCLUDED | view | |
| VDM.viewType | #CONSUMPTION | view | |
| Metadata.allowExtensions | true | view |
OData Services (5)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_COLL_MD_MANAGE | UI_COLL_MD_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_COLLECTION_CONTACT_MANAGE | UI_COLL_CONTACT_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_CUSTOMER_CONTACT_MANAGE | UI_CUSTOMER_CONTACT_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_HOBRECEIVABLES_DISPLAY | UI_HOBRECEIVABLES_DISPLAY | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_RESUBMISSIONS_MANAGE | UI_RESUBMISSIONS_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
Fiori Apps (4)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F4707 | Manage Customer Contacts | Transactional | Use this app to manage the customer contacts for your business partners, which are created by collections specialists as result of a customer contact. You use these contacts in the collection process with the Process Receivables app. |
| F4709 | Manage Resubmissions | Transactional | Use this app to manage resubmissions for business partners that were created for outstanding receivables. You use these resubmissions in the collection process with the Process Receivables app. |
| 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 Customer Contacts
Business Role: Accounts Receivable Accountant
Use this app to manage the customer contacts for your business partners, which are created by collections specialists as result of a customer contact. You use these contacts in the collection process with the Process Receivables app.
Manage Resubmissions
Business Role: Accounts Receivable Accountant
Use this app to manage resubmissions for business partners that were created for outstanding receivables. You use these resubmissions in the collection process with the Process Receivables 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 (10)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | BusinessPartner | BusinessPartner | ||
| KEY | CollectionSegment | CollectionSegment | ||
| BusinessPartnerCategory | BusinessPartnerCategory | |||
| BusinessPartnerPerson | BusinessPartnerPerson | |||
| virtualCompleteAddresstext100 | ||||
| virtualWebsiteURLtext1000 | ||||
| virtualContactCardPictureURLtext60 | ||||
| virtualUICT_MainContactboolean | ||||
| virtualUICT_WebsiteURLboolean | ||||
| _BusinessPartner | _BusinessPartner |
@EndUserText: { label: 'Business Partner Quick View' }
@ObjectModel: { usageType: { dataClass: #TRANSACTIONAL,
sizeCategory: #L,
serviceQuality: #C },
representativeKey: 'BusinessPartner',
semanticKey: [ 'BusinessPartner',
'CollectionSegment' ] }
@AccessControl: { authorizationCheck: #CHECK,
personalData: { blocking: #BLOCKED_DATA_EXCLUDED } }
@VDM: { viewType: #CONSUMPTION }
@Metadata: { allowExtensions: true }
@Consumption: { dbHints: [ 'USE_HEX_PLAN' ] }
define root view entity C_BPCollectionsSgmtQuickView
as projection on R_BPCollectionsSgmtQuickView
{
// VDM Fields
key BusinessPartner,
key CollectionSegment,
BusinessPartnerCategory,
BusinessPartnerPerson,
@ObjectModel: { virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_BP_POPOVER_VE' }
virtual CompleteAddress : text100,
@ObjectModel: { virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_BP_POPOVER_VE' }
virtual WebsiteURL : text1000,
@ObjectModel: { virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_BP_POPOVER_VE' }
virtual ContactCardPictureURL : text60,
@ObjectModel: { virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_BP_POPOVER_VE' }
virtual UICT_MainContact : boolean,
@ObjectModel: { virtualElementCalculatedBy: 'ABAP:CL_COLL_PR_BP_POPOVER_VE' }
virtual UICT_WebsiteURL : boolean,
// Exposed associations
_BusinessPartner,
_CollectionsMainContact : redirected to C_CollectionsMainContact
}
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