C_CollectionsPaymentTrend

DDL: C_COLLECTIONSPAYMENTTREND Type: view_entity CONSUMPTION

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.

1 data source(s) Exposed by 3 service(s) Used in 2 Fiori app(s) 7 fields

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
KEY CollectionSegment CollectionSegment
KEY FiscalPeriod FiscalPeriod
NetDueArrearsDays NetDueArrearsDays
IsHeadOffice IsHeadOffice
_CollectionSegment _CollectionSegment
_Customer _Customer 
@Metadata: { allowExtensions: true }
@VDM: { usage: { type:     [ #TRANSACTIONAL_PROCESSING_SERVICE ] },
                 viewType: #CONSUMPTION }
@AccessControl: { personalData:       { blocking: #BLOCKED_DATA_EXCLUDED },
                  authorizationCheck: #CHECK }
@ObjectModel: { usageType: { serviceQuality: #X,
                             sizeCategory:   #L,
                             dataClass:      #TRANSACTIONAL },
                representativeKey: 'Customer',
                semanticKey: [ 'Customer',
                               'CollectionSegment',
                               'FiscalPeriod' ],
                query: { implementedBy: 'ABAP:CL_COLL_PR_TREND_QUERY' } }
@EndUserText: { label: 'Collections Payment Trend' }

define root view entity C_CollectionsPaymentTrend
  as projection on I_CollectionsPaymentTrend
{

      // VDM Fields

  key Customer,
  key CollectionSegment,
  key FiscalPeriod,
      NetDueArrearsDays,
      IsHeadOffice,

      // Exposed Associations

      @ObjectModel: { sort: { enabled: false },
                      filter: { enabled: false } }
      _CollectionSegment,

      @ObjectModel: { sort: { enabled: false },
                      filter: { enabled: false } }
      _Customer

}

Learn More