C_CollsHeadOfficeAccountTP
Head Office Receivables
C_CollsHeadOfficeAccountTP is a Consumption CDS View that provides data about "Head Office Receivables" in SAP S/4HANA. It reads from 1 data source (R_CollsHeadOfficeAccountTP) and exposes 11 fields with key fields Customer, CollectionSegment. It is exposed through 1 OData service (UI_HOBRECEIVABLES_DISPLAY). It is used in 1 Fiori application: Display Head Office Receivables.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_CollsHeadOfficeAccountTP | R_CollsHeadOfficeAccountTP | projection |
Annotations (9)
| Name | Value | Level | Field |
|---|---|---|---|
| Metadata.allowExtensions | true | view | |
| VDM.viewType | #CONSUMPTION | view | |
| AccessControl.personalData.blocking | #BLOCKED_DATA_EXCLUDED | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| ObjectModel.usageType.serviceQuality | #X | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.representativeKey | Customer | view | |
| EndUserText.label | Head Office Receivables | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_HOBRECEIVABLES_DISPLAY | UI_HOBRECEIVABLES_DISPLAY | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
Fiori Apps (1)
| App ID | App Name | Type | Description |
|---|---|---|---|
| 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. |
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 (11)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | Customer | Customer | Sold-to Party | |
| KEY | CollectionSegment | CollectionSegment | Segment | |
| BusinessPartner | BusinessPartner | Issuing Authority | ||
| IsHeadOffice | IsHeadOffice | |||
| CustomerName | _Customer | CustomerName | Name of Customer | |
| BusinessPartnerName | _BusinessPartner | BusinessPartnerName | Extracted Customer Name | |
| virtualUICT_CreditAccountboolean | ||||
| virtualUICT_PromiseToPayboolean | ||||
| _BusinessPartner | _BusinessPartner | |||
| _CollectionSegment | _CollectionSegment | |||
| _Customer | _Customer |
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_CollsHeadOfficeAccountTP.
-- 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_CollsHeadOfficeAccountTP AS
SELECT
Customer,
CollectionSegment,
BusinessPartner,
IsHeadOffice,
_Customer.CustomerName AS CustomerName,
_BusinessPartner.BusinessPartnerName AS BusinessPartnerName,
virtual UICT_CreditAccount : boolean AS virtualUICT_CreditAccountboolean,
virtual UICT_PromiseToPay : boolean AS virtualUICT_PromiseToPayboolean
FROM R_CollsHeadOfficeAccountTP
;
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