I_JointVentureRecovery
Joint Venture Recovery
I_JointVentureRecovery (Basic)
Package: Explore, extend and adapt the SAP S/4HANA Public Edition with built-in and side-by-side extension capabilities.
Accounting and Financial Close
I_JointVentureRecovery is a Basic CDS View (Dimension) that provides data about "Joint Venture Recovery" in SAP S/4HANA. It reads from 1 data source (t8jj) and exposes 4 fields with key fields CompanyCode, JointVentureRecoveryCode. It has 2 associations to related views. It is exposed through 2 OData services (ASQL_F0731A, ASQL_F3516). Part of development package FINS_FIS_FICO.
SAP API Hub
| Category | Basic |
|---|---|
| State | C1 |
| Line of Business | Accounting and Financial Close |
| Application Component | FI-GL-IS-2CL |
| Capabilities | Data Source for Defining CDS Entities |
| Extensible (Key User) | No |
| Extensible (Developer) | No |
| Release State (Key User) | Released |
| Release State (Developer) | Not Released |
| Package | Accounting and Financial Close for SAP S/4HANA Cloud Public Edition |
| Description | <p>This CDS view provides the prerequisites for answering the following business questions:</p> <ul> <li> <p>How many joint venture recovery codes are defined?</p> </li> </ul> |
Documentation
- Analytics with CDS Views — Build Analytics for S/4HANA Cloud Public Edition ABAP CDS views replicated to SAP Cloud Platform
- CDS Views on SAP Business Accelerator Hub — Explore SAP S/4HANA Cloud Public Edition CDS Views on SAP Business Accelerator Hub
- Create CDS View as API — Create CDS views in SAP S/4HANA Cloud Public Edition and consume them as APIs
- Custom CDS Views — Access data using a Custom Core Data Service view (Custom CDS view)
- Custom Communication Scenarios — Create custom communication scenarios to configure custom communication arrangement
- Key User Extensibility Tools — The Key User Extensibility Tools of S/4HANA
- SAP S/4HANA Extensibility — SAP S/4HANA Extensibility Tutorial
- VDM View Types — The Virtual Data Model in SAP S/4HANA Cloud Public Edition
- View Browser — Search, browse and tag CDS Views
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| t8jj | t8jj | from |
Associations (2)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | I_CompanyCode | _CompanyCode | $projection.CompanyCode = _CompanyCode.CompanyCode |
| [0..*] | I_JointVentureRecoveryText | _Text | $projection.CompanyCode = _Text.CompanyCode and $projection.JointVentureRecoveryCode = _Text.JointVentureRecoveryCode |
Annotations (15)
| Name | Value | Level | Field |
|---|---|---|---|
| Analytics.dataCategory | #DIMENSION | view | |
| VDM.viewType | #BASIC | view | |
| Metadata.allowExtensions | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| AbapCatalog.sqlViewName | IFIJVR | view | |
| ObjectModel.representativeKey | JointVentureRecoveryCode | view | |
| EndUserText.label | Joint Venture Recovery | view | |
| AbapCatalog.buffering.status | #ACTIVE | view | |
| AbapCatalog.buffering.type | #GENERIC | view | |
| AbapCatalog.buffering.numberOfKeyFields | 1 | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| ObjectModel.usageType.dataClass | #CUSTOMIZING | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| Metadata.ignorePropagatedAnnotations | true | view |
OData Services (2)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| ASQL_F0731A | ASQL_F0731A | C2 | NOT_RELEASED | |
| ASQL_F3516 | ASQL_F3516 | C2 | NOT_RELEASED |
Fields (4)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | CompanyCode | bukrs | Company Code | |
| KEY | JointVentureRecoveryCode | recid | Statistical Key Figure Item | |
| _CompanyCode | _CompanyCode | |||
| _Text | _Text |
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 I_JointVentureRecovery.
-- 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.
-- SQL view name: IFIJVR
CREATE VIEW I_JointVentureRecovery AS
SELECT
bukrs AS CompanyCode,
recid AS JointVentureRecoveryCode
FROM t8jj
LEFT OUTER JOIN I_CompanyCode AS _CompanyCode ON CompanyCode = _CompanyCode.CompanyCode -- association [0..1]
LEFT OUTER JOIN I_JointVentureRecoveryText AS _Text ON CompanyCode = _Text.CompanyCode AND JointVentureRecoveryCode = _Text.JointVentureRecoveryCode -- association [0..*]
;
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
- 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