C_BankAccountReviewTP
Bank Account Review
C_BankAccountReviewTP is a Consumption CDS View that provides data about "Bank Account Review" in SAP S/4HANA. It reads from 1 data source (R_BankAccountReviewTP) and exposes 14 fields with key field BankAccountReviewUUID. It has 1 association to related views. It is exposed through 1 OData service (UI_BANKACCOUNTREVIEW_MNG). It is used in 1 Fiori application: Manage Bank Account Reviews. Part of development package FCLM_BAR_IMPL.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_BankAccountReviewTP | R_BankAccountReviewTP | projection |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | I_UserContactCard | _UserContactCard | $projection.CreatedByUser = _UserContactCard.ContactCardID |
Annotations (9)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Bank Account Review | view | |
| AccessControl.authorizationCheck | #MANDATORY | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| ObjectModel.usageType.dataClass | #MASTER | view | |
| Metadata.allowExtensions | true | view | |
| Search.searchable | true | view | |
| VDM.viewType | #CONSUMPTION | view | |
| Metadata.ignorePropagatedAnnotations | true | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_BANKACCOUNTREVIEW_MNG | UI_BANKACCOUNTREVIEW_MNG | V2 | C1 | NOT_RELEASED |
Fiori Apps (1)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F7510 | Manage Bank Account Reviews | Transactional | With this app, you can create, start and monitor the bank account review process. |
Manage Bank Account Reviews
Business Role: Cash Management Specialist
With this app, you can initiate, monitor, and control your (periodic) bank account reviews to ensure the correctness and completeness of bank account master data. You split the review of the bank accounts for a specific reference date into different review areas tailored to the responsible reviewers. For each review area, you take a snapshot of the bank account master data to be reviewed. This snapshot of bank account data is stored in the app and used during the review. When you start the review for a review area in this app, a workflow assists reviewers in conducting the bank account review for the review area. The reviewers perform the check in their My Inbox - All Items app, but you can monitor the progress of bank account review for the review areas in the Manage Bank Account Reviews app to ensure timely completion and troubleshooting during the review process. When the bank account review is complete, you can set the bank account review to Completed. For more information, see also Advanced Bank Account Review Process.
Key Features: Creation of bank account reviews and the review areas you require. In the review areas, you define the bank account selections and assign the reviewers. For more information, see also Initiate Bank Account Review. Copy bank account reviews Instead of creating a bank account review from scratch, you can also create a bank account review by copying an existing bank account review. The data of the existing bank account review, such as the review areas including the bank account selections and reviewers, are copied. In this way, you only need to enter the header data of the review, such as the review ID, the review description, and the reference date. When the bank account review is created, you can make any necessary changes to the copied data of the bank account review and the review areas. Take a snapshot of the bank account master data to be reviewed for a review area. The snapshot can be deleted all the while the review hasn't been started. Note The snapshot is stored and displayed on the Bank Account Snapshot tab of the review area in the Manage Bank Account Reviews app. When the review is started, the snapshot data is also available in the workflow task of the reviewers in the My Inbox - All Items app (F0862). When the bank account review is completed, the reviewed data is still available, for example, for external auditors. Start and monitor the reviews of the review areas. Note It is possible to stop the review as long as the first reviewer has not yet approved or rejected the bank account data in the My Inbox - All Items app. Set the bank account reviews to Completed when all bank accounts have successfully passed the review process. In this case, the correctness and completeness of the bank account master data is confirmed and the review is completed. Note If reviewers find errors in the master data, they must reject the snapshot data during the review. The review process is stopped, and the review area fails the review. In this case, the errors in the master data need to be corrected. Afterwards, within the bank account review, a new review area is created for these bank accounts, a new snapshot of the corrected bank account master data is taken, and the review process is started again. Overview table of existing bank account reviews SAP delivers a default workflow for the workflow scenario WS48000097 for execution of bank account reviews. The default workflow allows up to five reviewers to be assigned to each review area. The Manage Bank Account Reviews app is updated automatically with the review results, and the Workflow tab in the app allows the initiator to navigate to the status information of the workflow task. The change document object FCLM_BAR is used to log changes to the reviewers in the bank account review areas. The data destruction object allows you to destroy the data of completed bank account reviews after the retention period.
Fields (14)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | BankAccountReviewUUID | BankAccountReviewUUID | ||
| BankAccountReview | BankAccountReview | |||
| BankAccountReviewName | BankAccountReviewName | |||
| BankAccountReviewDate | BankAccountReviewDate | |||
| BankAccountReviewStatus | BankAccountReviewStatus | Review Status | ||
| BkAcctReviewCompletionDateTime | BkAcctReviewCompletionDateTime | Completion Timestamp | ||
| BankAccountReviewStatusNamelocalized | ||||
| LastChangeDateTime | LastChangeDateTime | |||
| CreatedByUser | CreatedByUser | |||
| CreationDateTime | CreationDateTime | |||
| LastChangedByUser | LastChangedByUser | |||
| LocalLastChangeDateTime | LocalLastChangeDateTime | |||
| _BankAccountReviewStatusText | _BankAccountReviewStatusText | |||
| _UserContactCard | _UserContactCard |
@EndUserText.label: 'Bank Account Review'
@AccessControl.authorizationCheck: #MANDATORY
@ObjectModel.usageType:{ serviceQuality: #C,
sizeCategory: #S,
dataClass: #MASTER }
@Metadata.allowExtensions: true
@Search.searchable: true
@VDM : { viewType: #CONSUMPTION,
usage.type: [ #TRANSACTIONAL_PROCESSING_SERVICE ] }
@Metadata.ignorePropagatedAnnotations: true
@AccessControl.privilegedAssociations: [ '_UserContactCard' ]
define root view entity C_BankAccountReviewTP
provider contract transactional_query
as projection on R_BankAccountReviewTP
association [0..1] to I_UserContactCard as _UserContactCard on $projection.CreatedByUser = _UserContactCard.ContactCardID
{
key BankAccountReviewUUID,
@Search.defaultSearchElement: true
@Search.fuzzinessThreshold: 0.8
@Search.ranking: #HIGH
@Consumption.valueHelpDefinition: [{ entity.name: 'I_BankAccountReviewVH',
entity.element: 'BankAccountReview' }]
BankAccountReview,
@Search.defaultSearchElement: true
@Search.fuzzinessThreshold: 0.8
@Search.ranking: #HIGH
// @EndUserText.label: 'Bank Account Review Description'
BankAccountReviewName,
@Search.defaultSearchElement: true
@Search.fuzzinessThreshold: 0.8
@Search.ranking: #HIGH
// @EndUserText.label: 'Bank Account Review Date'
BankAccountReviewDate,
@Search.defaultSearchElement: true
@Search.fuzzinessThreshold: 0.8
@Search.ranking: #MEDIUM
@EndUserText.label: 'Review Status'
@ObjectModel.text.element: ['BankAccountReviewStatusName']
@Consumption.valueHelpDefinition: [{ entity.name: 'I_BankAccountReviewStatus',
entity.element: 'BankAccountReviewStatus' }]
@Consumption.filter.defaultValue: 'IP'
@UI: { textArrangement: #TEXT_ONLY }
BankAccountReviewStatus,
@Search.defaultSearchElement: true
@Search.fuzzinessThreshold: 0.8
@Search.ranking: #HIGH
@EndUserText.label: 'Completion Timestamp'
BkAcctReviewCompletionDateTime,
@Semantics.text:true
@UI.hidden: true
_BankAccountReviewStatusText.BankAccountReviewStatusName : localized,
@Semantics.systemDateTime.lastChangedAt: true
LastChangeDateTime,
@Semantics.user.createdBy: true
CreatedByUser,
@Semantics.systemDateTime.createdAt: true
CreationDateTime,
@Semantics.user.lastChangedBy: true
LastChangedByUser,
@Semantics.systemDateTime.localInstanceLastChangedAt: true
LocalLastChangeDateTime,
@ObjectModel:{virtualElementCalculatedBy: 'ABAP:CL_FCLM_BAR_CALC_EXIT_BAR'}
virtual BkAccountReviewStatusColorCode: fclm_bar_color_code,
_BankAccountReviewArea : redirected to composition child C_BankAccountReviewAreaTP,
_BankAccountReviewStatusText,
@Consumption.filter.hidden: true
_UserContactCard
}
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