C_DisputeCaseProtocol
Dispute Case Protocol
C_DisputeCaseProtocol is a Consumption CDS View that provides data about "Dispute Case Protocol" in SAP S/4HANA. It reads from 1 data source (R_DisputeCaseProtocol) and exposes 20 fields with key fields DisputeCaseUUID, TableChangeLogKey. It is exposed through 1 OData service (UI_DISPUTECASE_MANAGE). It is used in 1 Fiori application: Manage Dispute Cases (Version 2). Part of development package ODATA_DISPUTE.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_DisputeCaseProtocol | R_DisputeCaseProtocol | projection |
Annotations (10)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Dispute Case Protocol | view | |
| ObjectModel.representativeKey | DisputeCaseUUID | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.serviceQuality | #X | view | |
| ObjectModel.query.implementedBy | ABAP:CL_DISPUTE_LOG_QUERY | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| AccessControl.personalData.blocking | #BLOCKED_DATA_EXCLUDED | view | |
| VDM.viewType | #CONSUMPTION | view | |
| Metadata.allowExtensions | true | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_DISPUTECASE_MANAGE | UI_DISPUTECASE_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
Fiori Apps (1)
| 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. |
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.
Fields (20)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | DisputeCaseUUID | DisputeCaseUUID | ||
| KEY | TableChangeLogKey | TableChangeLogKey | ||
| TableChangeLogUser | TableChangeLogUser | |||
| LastChangedByUserName | LastChangedByUserName | |||
| CaseLastChangedOn | CaseLastChangedOn | |||
| TableChangeLogFieldOldValue | TableChangeLogFieldOldValue | |||
| ChangeDocNewFieldValueText | ChangeDocNewFieldValueText | |||
| TableChangeLogFieldNewValue | TableChangeLogFieldNewValue | |||
| ChangeDocOldFieldValueText | ChangeDocOldFieldValueText | |||
| ParameterValue | ParameterValue | |||
| ParameterName | ParameterName | |||
| ObjectName | ObjectName | |||
| Department | _ContactCard | Department | ||
| EmailAddress | _ContactCard | EmailAddress | ||
| FaxNumber | _ContactCard | FaxNumber | ||
| FunctionalTitleName | _ContactCard | FunctionalTitleName | ||
| MobilePhoneNumber | _ContactCard | MobilePhoneNumber | ||
| PhoneNumber | _ContactCard | PhoneNumber | ||
| UserDescription | _ContactCard | UserDescription | ||
| _DisputeCase | _DisputeCase |
@EndUserText: { label: 'Dispute Case Protocol' }
@ObjectModel: { representativeKey: 'DisputeCaseUUID',
usageType: { dataClass: #TRANSACTIONAL,
sizeCategory: #L,
serviceQuality: #X },
query: { implementedBy: 'ABAP:CL_DISPUTE_LOG_QUERY' } }
@AccessControl: { authorizationCheck: #CHECK,
personalData: { blocking: #BLOCKED_DATA_EXCLUDED },
privilegedAssociations: [ '_ContactCard' ] }
@VDM: { viewType: #CONSUMPTION,
usage: { type: [ #TRANSACTIONAL_PROCESSING_SERVICE ] } }
@Metadata: { allowExtensions: true }
define root view entity C_DisputeCaseProtocol
as projection on R_DisputeCaseProtocol
{
//R_DisputeCaseProtocol
key DisputeCaseUUID,
key TableChangeLogKey,
@ObjectModel: { text: { element: [ 'LastChangedByUserName' ] } }
@Semantics: { contact: { type: #PERSON },
user: { id: true } }
TableChangeLogUser,
LastChangedByUserName,
CaseLastChangedOn,
@ObjectModel: { text: { element: [ 'ChangeDocOldFieldValueText' ] } }
TableChangeLogFieldOldValue,
ChangeDocNewFieldValueText,
@ObjectModel: { text: { element: [ 'ChangeDocNewFieldValueText' ] } }
TableChangeLogFieldNewValue,
ChangeDocOldFieldValueText,
@ObjectModel: { text: { element: [ 'ParameterName' ] },
sort: { enabled: false },
filter: { enabled: false } }
ParameterValue,
@ObjectModel: { sort: { enabled: false },
filter: { enabled: false } }
ParameterName,
ObjectName,
@Semantics: { organization: { name: true } }
_ContactCard.Department,
@Semantics: { eMail: { type: [ #WORK ],
address: true } }
_ContactCard.EmailAddress,
@Semantics: { telephone: { type: [ #FAX ] } }
_ContactCard.FaxNumber,
@Semantics: { organization: { role: true } }
_ContactCard.FunctionalTitleName,
@Semantics: { telephone: { type: [ #CELL ] } }
_ContactCard.MobilePhoneNumber,
@Semantics: { telephone: { type: [ #WORK ] } }
_ContactCard.PhoneNumber,
@Semantics: { name: { fullName: true } }
_ContactCard.UserDescription,
// Exposed Associations
@ObjectModel: { sort: { enabled: false },
filter: { enabled: false } }
_ContactCard : redirected to C_RblsMgmtUserContactCard,
@ObjectModel: { sort: { enabled: false },
filter: { enabled: false } }
_DisputeCase
}
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