C_CollsInvoiceRelatedResubmsn
Resubmission Related to Invoice
C_CollsInvoiceRelatedResubmsn is a Consumption CDS View that provides data about "Resubmission Related to Invoice" in SAP S/4HANA. It reads from 1 data source (I_CollsInvoiceRelatedResubmsn) and exposes 29 fields with key fields LogicalSystem, ObjectType, ObjectKey, RelationToLinkedObject, ResubmissionUUID. It is exposed through 3 OData services (UI_DISPUTECASE_MANAGE, UI_HOBRECEIVABLES_DISPLAY, UI_PROCESSRECEIVABLES_MANAGE). It is used in 2 Fiori applications: Manage Dispute Cases (Version 2), Display Head Office Receivables.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_CollsInvoiceRelatedResubmsn | I_CollsInvoiceRelatedResubmsn | projection |
Annotations (8)
| Name | Value | Level | Field |
|---|---|---|---|
| Metadata.allowExtensions | true | view | |
| VDM.viewType | #CONSUMPTION | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| ObjectModel.usageType.serviceQuality | #X | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.representativeKey | ResubmissionUUID | view | |
| EndUserText.label | Resubmission Related to Invoice | view |
OData Services (3)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| 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_PROCESSRECEIVABLES_MANAGE | UI_PROCESSRECEIVABLES_MAN | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
Fiori Apps (2)
| App ID | App Name | Type | Description |
|---|---|---|---|
| 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. |
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.
Fields (29)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | LogicalSystem | LogicalSystem | ||
| KEY | ObjectType | ObjectType | ||
| KEY | ObjectKey | ObjectKey | ||
| KEY | RelationToLinkedObject | RelationToLinkedObject | ||
| KEY | ResubmissionUUID | ResubmissionUUID | ||
| ObjectClassification | ObjectClassification | |||
| ObjectIsConfirmed | ObjectIsConfirmed | |||
| ObjectIsVoided | ObjectIsVoided | |||
| CompanyCode | CompanyCode | |||
| AccountingDocument | AccountingDocument | |||
| FiscalYear | FiscalYear | |||
| AccountingDocumentItem | AccountingDocumentItem | |||
| CaseID | CaseID | |||
| BusinessPartner | _CollectionsResubmission | BusinessPartner | ||
| CollectionSegment | _CollectionsResubmission | CollectionSegment | ||
| ResubmissionDueDate | _CollectionsResubmission | ResubmissionDueDate | ||
| CollResubmissionDateTime | _CollectionsResubmission | CollResubmissionDateTime | ||
| NoCntctUntilResubmsnDateIsReq | _CollectionsResubmission | NoCntctUntilResubmsnDateIsReq | ||
| ResubmissionReason | _CollectionsResubmission | ResubmissionReason | ||
| ResubmissionStatus | _CollectionsResubmission | ResubmissionStatus | ||
| CreatedByUser | CreatedByUser | |||
| CreationDateTime | _CollectionsResubmission | CreationDateTime | ||
| ChangedBy | ChangedBy | |||
| ChangedOnDateTime | _CollectionsResubmission | ChangedOnDateTime | ||
| BusinessPartnerName | ||||
| CreatedByUserName | ||||
| ChangedByUserName | ||||
| _CaseAttribute | _CaseAttribute | |||
| _CollectionsResubmission | _CollectionsResubmission |
@Metadata: { allowExtensions: true }
@VDM: { usage: { type: [ #TRANSACTIONAL_PROCESSING_SERVICE ] },
viewType: #CONSUMPTION }
@AccessControl: { authorizationCheck: #CHECK }
@ObjectModel: { usageType: { serviceQuality: #X,
sizeCategory: #L,
dataClass: #TRANSACTIONAL },
representativeKey: 'ResubmissionUUID',
semanticKey: [ 'ResubmissionUUID' ] }
@EndUserText: { label: 'Resubmission Related to Invoice' }
define root view entity C_CollsInvoiceRelatedResubmsn
as projection on I_CollsInvoiceRelatedResubmsn
{
//I_CollsInvoiceRelatedObject
key LogicalSystem,
key ObjectType,
key ObjectKey,
key RelationToLinkedObject,
key ResubmissionUUID,
ObjectClassification,
ObjectIsConfirmed,
ObjectIsVoided,
CompanyCode,
AccountingDocument,
FiscalYear,
AccountingDocumentItem,
CaseID,
// Resubmission Data
@ObjectModel: { text: { element: [ 'BusinessPartnerName' ] } }
_CollectionsResubmission.BusinessPartner,
@ObjectModel: { text: { element: ['CollectionSegmentName'] } }
_CollectionsResubmission.CollectionSegment,
_CollectionsResubmission.ResubmissionDueDate,
_CollectionsResubmission.CollResubmissionDateTime,
_CollectionsResubmission.NoCntctUntilResubmsnDateIsReq,
@ObjectModel: { text: { element: ['ResubmissionReasonName'] } }
_CollectionsResubmission.ResubmissionReason,
@ObjectModel: { text: { element: ['ResubmissionStatusName'] } }
_CollectionsResubmission.ResubmissionStatus,
@ObjectModel: { text: { element: ['CreatedByUserName'] } }
CreatedByUser,
_CollectionsResubmission.CreationDateTime,
@ObjectModel: { text: { element: ['ChangedByUserName'] } }
ChangedBy,
_CollectionsResubmission.ChangedOnDateTime,
// Text Elements
_CollectionsResubmission._BusinessPartner.BusinessPartnerName as BusinessPartnerName,
_CollectionsResubmission._CollectionSegment._Text.CollectionSegmentName as CollectionSegmentName : localized,
_CollectionsResubmission._ResubmissionReason._Text.ResubmissionReasonName as ResubmissionReasonName : localized,
_CollectionsResubmission._ResubmissionStatus._Text.ResubmissionStatusName as ResubmissionStatusName : localized,
_CollectionsResubmission._CreatedBy.UserDescription as CreatedByUserName,
_CollectionsResubmission._ChangedBy.UserDescription as ChangedByUserName,
// Exposed Associations
_CaseAttribute,
_CollectionsResubmission,
_CreatedByContactCard : redirected to C_RblsMgmtUserContactCard,
_ChangedByContactCard : redirected to C_RblsMgmtUserContactCard
}
Learn More
- What Is a CDS View in SAP S/4HANA?
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- CDS View Annotations — A Complete Guide
- 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