C_IHBMstrDataObjChangeDocument
IHB MD Object Change Document
C_IHBMstrDataObjChangeDocument is a Consumption CDS View that provides data about "IHB MD Object Change Document" in SAP S/4HANA. It reads from 1 data source (I_IHBMstrDataObjChangeDocument) and exposes 18 fields with key fields IHBObjectUUID, ChangeDocObject, ChangeDocObjectClass, ChangeDocument, DatabaseTable. It has 1 association to related views. It is exposed through 8 OData services (UI_IHBACCOUNTFEETP, UI_IHBACCOUNTLIMITWORKFLOW, UI_IHBACCTINTRSTCOMPNOBJTP, ...). It is used in 6 Fiori applications: Manage In-House Bank Limits, Manage In-House Bank Limits, Manage In-House Bank Conditions, ....
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_IHBMstrDataObjChangeDocument | I_IHBMstrDataObjChangeDocument | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | C_APMUserContactCard | _APMUserContactCard | $projection.CreatedByUser = _APMUserContactCard.ContactCardID |
Annotations (9)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #MANDATORY | view | |
| EndUserText.label | IHB MD Object Change Document | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #XXL | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| VDM.viewType | #CONSUMPTION | view | |
| VDM.lifecycle.contract.type | #NONE | view | |
| Metadata.allowExtensions | true | view |
OData Services (8)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_IHBACCOUNTFEETP | UI_IHBACCOUNTFEETP | V2 | C1 | NOT_RELEASED |
| UI_IHBACCOUNTLIMITWORKFLOW | UI_IHBACCOUNTLIMITWORKFLOW | V2 | C1 | NOT_RELEASED |
| UI_IHBACCTINTRSTCOMPNOBJTP | UI_IHBACCTINTRSTCOMPNOBJTP | V2 | C1 | NOT_RELEASED |
| UI_IHBACCTLIMITOBJECTTP | UI_IHBACCTLIMITOBJECTTP | V2 | C1 | NOT_RELEASED |
| UI_IHBCONDITIONOBJECTTP | UI_IHBCONDITIONOBJECTTP | V2 | C1 | NOT_RELEASED |
| UI_IHBCONDITIONWORKFLOW | UI_IHBCONDITIONWORKFLOW | V2 | C1 | NOT_RELEASED |
| UI_IHBFEEWORKFLOW | UI_IHBFEEWORKFLOW | V2 | C1 | NOT_RELEASED |
| UI_IHBINTRSTCOMPNWORKFLOW | UI_IHBINTRSTCOMPNWORKFLOW | V2 | C1 | NOT_RELEASED |
Fiori Apps (6)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F5940 | Manage In-House Bank Limits | Transactional | This app manage internal limits for in-house bank accounts |
| F5940 | Manage In-House Bank Limits | Transactional | This app manage internal limits for in-house bank accounts |
| F5941 | Manage In-House Bank Conditions | Transactional | Manage in-house bank financial conditions for internal house bank accounts |
| F5941 | Manage In-House Bank Conditions | Transactional | Manage in-house bank financial conditions for internal house bank accounts |
| F6335 | Manage In-House Bank Fees | Transactional | Manage in-house bank interest compensation hierarchies. |
| F6652 | Manage In-House Bank Interest Compensation | Transactional | Manage in-house bank interest compensation hierarchies. |
Manage In-House Bank Limits
Business Role: Payment Specialist
With this app, you can monitor payments that are relevant for in-house bank accounts.
Manage In-House Bank Limits
Business Role: Payment Specialist
With this app, you can monitor payments that are relevant for in-house bank accounts.
Manage In-House Bank Conditions
Business Role: Payment Specialist
With this app, you can manage account balances by setting the lower limits. A limit can be set at a single account level or a group of accounts level together with the value and the validity. You can set either a positive value (for example, 1000 EUR) or a negative value (for example, -1000 EUR).
Manage In-House Bank Conditions
Business Role: Payment Specialist
With this app, you can manage account balances by setting the lower limits. A limit can be set at a single account level or a group of accounts level together with the value and the validity. You can set either a positive value (for example, 1000 EUR) or a negative value (for example, -1000 EUR).
Manage In-House Bank Fees
Business Role: Payment Specialist
With this app, you can define fees for your monthly account maintenance and for processing transactions. The account maintenance fee is a monthly fee that will be charged when you set up an account. Transaction fees are calculated on a monthly basis and you can define them in three different levels.
Fields (18)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | IHBObjectUUID | IHBObjectUUID | UUID | |
| KEY | ChangeDocObject | ChangeDocObject | Object Value | |
| KEY | ChangeDocObjectClass | ChangeDocObjectClass | Change Doc. Object | |
| KEY | ChangeDocument | ChangeDocument | Document Number | |
| KEY | DatabaseTable | DatabaseTable | Table Name | |
| KEY | ChangeDocTableKey | ChangeDocTableKey | ||
| KEY | ChangeDocDatabaseTableField | ChangeDocDatabaseTableField | Field Name | |
| KEY | ChangeDocItemChangeType | ChangeDocItemChangeType | ||
| CreatedByUser | CreatedByUser | Modified by | ||
| CreationDate | CreationDate | Date Modified | ||
| CreationTime | CreationTime | Time Modified | ||
| ChangeDocPreviousFieldValue | ChangeDocPreviousFieldValue | |||
| ChangeDocNewFieldValue | ChangeDocNewFieldValue | |||
| ChangeDocPrevFieldValueText | ||||
| ChangeDocNewFieldValueText | ||||
| _IHBMstrDataObjFieldLabel | _IHBMstrDataObjFieldLabel | |||
| _IHBMasterDataObjectTP | _IHBMasterDataObjectTP | |||
| _APMUserContactCard | _APMUserContactCard |
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_IHBMstrDataObjChangeDocument.
-- 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_IHBMstrDataObjChangeDocument AS
SELECT
IHBObjectUUID,
ChangeDocObject,
ChangeDocObjectClass,
ChangeDocument,
DatabaseTable,
ChangeDocTableKey,
ChangeDocDatabaseTableField,
ChangeDocItemChangeType,
CreatedByUser,
CreationDate,
CreationTime,
ChangeDocPreviousFieldValue,
ChangeDocNewFieldValue,
cast( '' as cdfldvaln ) AS ChangeDocPrevFieldValueText,
cast( '' as cdfldvaln ) AS ChangeDocNewFieldValueText
FROM I_IHBMstrDataObjChangeDocument
LEFT OUTER JOIN C_APMUserContactCard AS _APMUserContactCard ON CreatedByUser = _APMUserContactCard.ContactCardID -- association [0..1]
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- OData Services in SAP S/4HANA Explained
- Service Bindings and Service Definitions in SAP S/4HANA
- SAP Fiori Apps Architecture — How Fiori Apps Connect to Data
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- 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
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA