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 8 OData services (ASQL_F4707, ASQL_F4708, ASQL_F4709, ...). 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 (8)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| ASQL_F4707 | ASQL_F4707 | C2 | NOT_RELEASED | |
| ASQL_F4708 | ASQL_F4708 | C2 | NOT_RELEASED | |
| ASQL_F4709 | ASQL_F4709 | C2 | NOT_RELEASED | |
| 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 | Issuing Authority | |
| KEY | CollectionSegment | CollectionSegment | Segment | |
| BusinessPartnerCategory | BusinessPartnerCategory | Partner Cat. | ||
| BusinessPartnerPerson | BusinessPartnerPerson | Busn. Partner | ||
| virtualCompleteAddresstext100 | ||||
| virtualWebsiteURLtext1000 | ||||
| virtualContactCardPictureURLtext60 | ||||
| virtualUICT_MainContactboolean | ||||
| virtualUICT_WebsiteURLboolean | ||||
| _BusinessPartner | _BusinessPartner |
Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.
-- Derived SQL interpretation of CDS view C_BPCollectionsSgmtQuickView.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
CREATE VIEW C_BPCollectionsSgmtQuickView AS
SELECT
BusinessPartner,
CollectionSegment,
BusinessPartnerCategory,
BusinessPartnerPerson,
virtual CompleteAddress : text100 AS virtualCompleteAddresstext100,
virtual WebsiteURL : text1000 AS virtualWebsiteURLtext1000,
virtual ContactCardPictureURL : text60 AS virtualContactCardPictureURLtext60,
virtual UICT_MainContact : boolean AS virtualUICT_MainContactboolean,
virtual UICT_WebsiteURL : boolean AS virtualUICT_WebsiteURLboolean
FROM R_BPCollectionsSgmtQuickView
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- OData Services in SAP S/4HANA Explained
- Service Bindings and Service Definitions in SAP S/4HANA
- SAP Fiori Apps Architecture — How Fiori Apps Connect to Data
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- 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
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA