C_CollectionsPaymentTrend

DDL: C_COLLECTIONSPAYMENTTREND Type: view_entity CONSUMPTION
7 Fields 1 Data Sources 3 OData Services 2 Fiori Apps

Collections Payment Trend

C_CollectionsPaymentTrend is a Consumption CDS View that provides data about "Collections Payment Trend" in SAP S/4HANA. It reads from 1 data source (I_CollectionsPaymentTrend) and exposes 7 fields with key fields Customer, CollectionSegment, FiscalPeriod. 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.

Data Sources (1)

SourceAliasJoin Type
I_CollectionsPaymentTrend I_CollectionsPaymentTrend projection

Annotations (10)

NameValueLevelField
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
ObjectModel.query.implementedBy ABAP:CL_COLL_PR_TREND_QUERY view
EndUserText.label Collections Payment Trend view

OData Services (3)

ServiceBindingVersionContractRelease
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 IDApp NameTypeDescription
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 (7)

KeyFieldSource TableSource FieldDescription
KEY Customer Customer Sold-to Party
KEY CollectionSegment CollectionSegment Segment
KEY FiscalPeriod FiscalPeriod Tax period
NetDueArrearsDays NetDueArrearsDays
IsHeadOffice IsHeadOffice
_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_CollectionsPaymentTrend.
-- 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_CollectionsPaymentTrend AS
SELECT
  Customer,
  CollectionSegment,
  FiscalPeriod,
  NetDueArrearsDays,
  IsHeadOffice
FROM I_CollectionsPaymentTrend
;

Learn More