C_CollectionsInvoiceTP

DDL: C_COLLECTIONSINVOICETP Type: view_entity CONSUMPTION
75 Fields 1 Data Sources 4 OData Services 3 Fiori Apps

Collections Invoice

C_CollectionsInvoiceTP is a Consumption CDS View that provides data about "Collections Invoice" in SAP S/4HANA. It reads from 1 data source (R_CollectionsInvoiceTP) and exposes 75 fields with key fields CollectionSegment, CompanyCode, FiscalYear, AccountingDocument, AccountingDocumentItem. It is exposed through 4 OData services (UI_DISPUTECASE_MANAGE, UI_HOBRECEIVABLES_DISPLAY, UI_INVOICEPRIOZNRULE_MAN, ...). It is used in 3 Fiori applications: Manage Dispute Cases (Version 2), Display Head Office Receivables, Manage Invoice Prioritization Rules.

Data Sources (1)

SourceAliasJoin Type
R_CollectionsInvoiceTP R_CollectionsInvoiceTP 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 AccountingDocumentItem view
ObjectModel.query.implementedBy ABAP:CL_COLL_PR_INV_QUERY view
EndUserText.label Collections Invoice view

OData Services (4)

ServiceBindingVersionContractRelease
UI_DISPUTECASE_MANAGE UI_DISPUTECASE_MANAGE V2 C1 NOT_TO_BE_RELEASED_STABLE
UI_HOBRECEIVABLES_DISPLAY UI_HOBRECEIVABLES_DISPLAY V2 C1 NOT_TO_BE_RELEASED_STABLE
UI_INVOICEPRIOZNRULE_MAN UI_INVOICEPRIOZNRULE_MAN V2 C1 NOT_TO_BE_RELEASED_STABLE
UI_PROCESSRECEIVABLES_MANAGE UI_PROCESSRECEIVABLES_MAN V2 C1 NOT_TO_BE_RELEASED_STABLE

Fiori Apps (3)

App IDApp NameTypeDescription
F0702A Manage Dispute Cases (Version 2) Transactional Use this app to analyze and further process existing dispute cases. This involves dispute cases that are related to open receivables for your customers.
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.
F5470 Manage Invoice Prioritization Rules Transactional You use this app in order to define rules based on which the invoices that are displayed in the Fiori app Process Receivables are prioritized. This helps the collection specialist to focus on the most important invoices during his collection call with the customer, in particular if there are many of them.

Manage Dispute Cases (Version 2)

Business Role: Accounts Receivable Accountant

Use this app to analyze and further process existing dispute cases. This involves dispute cases that are related to open receivables for your customers.

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.

Manage Invoice Prioritization Rules

Business Role: Accounts Receivable Manager

Use this app to define rules to proritize invoices displayed in the Invoices section of the Process Receivables Fiori app.You can add rule and define criteria for the invoice priritization evaluation, and define Priority tresholds to group invoices in the Process Receivables.

Fields (75)

KeyFieldSource TableSource FieldDescription
KEY CollectionSegment CollectionSegment Segment
KEY CompanyCode CompanyCode Receiver Company Code
KEY FiscalYear FiscalYear G/L Fiscal Year
KEY AccountingDocument AccountingDocument Journal Entry
KEY AccountingDocumentItem AccountingDocumentItem Posting View Item
Customer Customer Sold-to Party
BranchAccount BranchAccount Branch Account No.
DocumentDate DocumentDate Journal Entry Date
PostingDate PostingDate Posting Date for GR
DunningLevel DunningLevel Dunning Level
LastDunningDate LastDunningDate Last Dunned
NetDueDate NetDueDate Net Due Date
Reference1InDocumentHeader Reference1InDocumentHeader Reference 1
Reference2InDocumentHeader Reference2InDocumentHeader Reference 2
PaymentMethod PaymentMethod Pymt Meth.
FinancialAccountType FinancialAccountType Fin. Account Type
OverdueDays OverdueDays
CashDiscount1Days CashDiscount1Days Days from Baseline Date for Payment
AmountInTransactionCurrency AmountInTransactionCurrency Pt Crcy Amt
PaidAmount PaidAmount Paid Amount
DunnedAmount DunnedAmount
OpenAmountInDocumentCurrency OpenAmountInDocumentCurrency
CashDiscountAmtInTransacCrcy CashDiscountAmtInTransacCrcy
TransactionCurrency TransactionCurrency Transaction Currency
PaymentDate PaymentDate Payment Date
DunningBlockingReason DunningBlockingReason Set Dunning Block
SpecialGLCode SpecialGLCode Special G/L Ind
OperationalGLAccount OperationalGLAccount Operational G/L Acct
FiscalPeriod FiscalPeriod Tax period
BillingDocument BillingDocument SD Document
PostingKey PostingKey Posting Key
DocumentItemText DocumentItemText Text
ReferenceDocumentLogicalSystem ReferenceDocumentLogicalSystem Ref. Doc. Lgcl Syst.
CaseStatus CaseStatus Status
CaseStatusName CaseStatusName
CaseReason CaseReason Reason
ReasonCodeName ReasonCodeName
PromiseToPayStatus PromiseToPayStatus State
DisputeCase DisputeCase Case ID
PromiseToPay PromiseToPay
NumberOfResubmissions NumberOfResubmissions
ArrangedAmount ArrangedAmount
PromisedAmount PromisedAmount Promised Amount
PromiseToPayLevel PromiseToPayLevel Level
PromiseToPayDueDate PromiseToPayDueDate
DisputedAmount DisputedAmount Disputed Amount
CreditedAmount CreditedAmount Credited
DocumentReferenceID DocumentReferenceID Reference
LastDunningDurationInDays LastDunningDurationInDays
ObjectKey ObjectKey Object Key
Country Country Venue: Ctry/Reg
ResubmissionUUID ResubmissionUUID Resubmission Key
ResubmissionDueDate ResubmissionDueDate Resubmission Date
ResubmissionReason ResubmissionReason Reason
NumberOfDaysSinceResubmission NumberOfDaysSinceResubmission
CaseUniqueID CaseUniqueID
LatePaymentRisk LatePaymentRisk
PostingKeyNameasPostingKeyNamelocalized
CompanyCodeName _CompanyCode CompanyCodeName Company Name
CustomerName _Customer CustomerName Name of Customer
BranchAccountName _BranchAccount CustomerName Name of Customer
virtualUICT_OverdueDayschar1
virtualCriticalitychar1
virtualUICT_CollectionSegmentboolean
virtualUICT_BillingDocumentIconboolean
_CollectionSegment _CollectionSegment
_CompanyCode _CompanyCode
_Customer _Customer
_BranchAccount _BranchAccount
_BillingDocument _BillingDocument
_DunningBlockingReasonCode _DunningBlockingReasonCode
_SpecialGLCode _SpecialGLCode
_PostingKey _PostingKey
_PromiseToPayStatus _PromiseToPayStatus
_OperationalAcctgDocItem _OperationalAcctgDocItem

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_CollectionsInvoiceTP.
-- 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_CollectionsInvoiceTP AS
SELECT
  CollectionSegment,
  CompanyCode,
  FiscalYear,
  AccountingDocument,
  AccountingDocumentItem,
  Customer,
  BranchAccount,
  DocumentDate,
  PostingDate,
  DunningLevel,
  LastDunningDate,
  NetDueDate,
  Reference1InDocumentHeader,
  Reference2InDocumentHeader,
  PaymentMethod,
  FinancialAccountType,
  OverdueDays,
  CashDiscount1Days,
  AmountInTransactionCurrency,
  PaidAmount,
  DunnedAmount,
  OpenAmountInDocumentCurrency,
  CashDiscountAmtInTransacCrcy,
  TransactionCurrency,
  PaymentDate,
  DunningBlockingReason,
  SpecialGLCode,
  OperationalGLAccount,
  FiscalPeriod,
  BillingDocument,
  PostingKey,
  DocumentItemText,
  ReferenceDocumentLogicalSystem,
  CaseStatus,
  CaseStatusName,
  CaseReason,
  ReasonCodeName,
  PromiseToPayStatus,
  DisputeCase,
  PromiseToPay,
  NumberOfResubmissions,
  ArrangedAmount,
  PromisedAmount,
  PromiseToPayLevel,
  PromiseToPayDueDate,
  DisputedAmount,
  CreditedAmount,
  DocumentReferenceID,
  LastDunningDurationInDays,
  ObjectKey,
  Country,
  ResubmissionUUID,
  ResubmissionDueDate,
  ResubmissionReason,
  NumberOfDaysSinceResubmission,
  CaseUniqueID,
  LatePaymentRisk,
  _PostingKey._PostingKeyText.PostingKeyName as PostingKeyName : localized AS PostingKeyNameasPostingKeyNamelocalized,
  _CompanyCode.CompanyCodeName AS CompanyCodeName,
  _Customer.CustomerName AS CustomerName,
  _BranchAccount.CustomerName AS BranchAccountName,
  virtual UICT_OverdueDays : char1 AS virtualUICT_OverdueDayschar1,
  virtual Criticality : char1 AS virtualCriticalitychar1,
  virtual UICT_CollectionSegment : boolean AS virtualUICT_CollectionSegmentboolean,
  virtual UICT_BillingDocumentIcon : boolean AS virtualUICT_BillingDocumentIconboolean
FROM R_CollectionsInvoiceTP
;

Learn More