I_FundStdVH

DDL: I_FUNDSTDVH SQL: IFU_VH4 Type: view COMPOSITE Package: PSM_S4C_BASIS

Fund

I_FundStdVH (Composite)

Package: Explore, extend and adapt the SAP S/4HANA Cloud Public Edition with built-in and side-by-side extension capabilities.

Cross Applications

I_FundStdVH is a Composite CDS View that provides data about "Fund" in SAP S/4HANA. It reads from 1 data source (I_Fund) and exposes 14 fields with key fields Fund, FinancialManagementArea. It is exposed through 65 OData services (ASQL_F0735, ASQL_F1443B, ASQL_F1665, ...). It is used in 2 Fiori applications: Manage RIB Rules, Manage RIB Rules for Grants. Part of development package PSM_S4C_BASIS.

SAP API Hub

CategoryComposite
StateC1
Line of BusinessCross Applications
Application ComponentPSM
CapabilitiesAnalytical Dimension,Data Provider for Value Help
Extensible (Key User)No
Extensible (Developer)No
Release State (Key User)Released
Release State (Developer)Released
PackageCross Applications for SAP S/4HANA Cloud Public Edition

Documentation

Data Sources (1)

SourceAliasJoin Type
I_Fund I_Fund from

Annotations (14)

NameValueLevelField
AbapCatalog.sqlViewName IFU_VH4 view
AbapCatalog.compiler.compareFilter true view
VDM.viewType #COMPOSITE view
ObjectModel.dataCategory #VALUE_HELP view
ObjectModel.representativeKey Fund view
ObjectModel.usageType.dataClass #MASTER view
ObjectModel.usageType.serviceQuality #B view
ObjectModel.usageType.sizeCategory #M view
Search.searchable true view
Consumption.ranked true view
AccessControl.authorizationCheck #CHECK view
ClientHandling.algorithm #SESSION_VARIABLE view
Metadata.ignorePropagatedAnnotations true view
EndUserText.label Fund view

OData Services (65)

ServiceBindingVersionContractRelease
ASQL_F0735 ASQL_F0735 C2 NOT_RELEASED
ASQL_F1443B ASQL_F1443B C2 NOT_RELEASED
ASQL_F1665 ASQL_F1665 C2 NOT_RELEASED
ASQL_F1754 ASQL_F1754 C2 NOT_RELEASED
ASQL_F1755 ASQL_F1755 C2 NOT_RELEASED
ASQL_F1867 ASQL_F1867 C2 NOT_RELEASED
ASQL_F2009 ASQL_F2009 C2 NOT_RELEASED
ASQL_F2009A ASQL_F2009A C2 NOT_RELEASED
ASQL_F2218 ASQL_F2218 C2 NOT_RELEASED
ASQL_F2332 ASQL_F2332 C2 NOT_RELEASED
ASQL_F2420 ASQL_F2420 C2 NOT_RELEASED
ASQL_F2421 ASQL_F2421 C2 NOT_RELEASED
ASQL_F2422 ASQL_F2422 C2 NOT_RELEASED
ASQL_F2691 ASQL_F2691 C2 NOT_RELEASED
ASQL_F2986 ASQL_F2986 C2 NOT_RELEASED
ASQL_F2986A ASQL_F2986A C2 NOT_RELEASED
ASQL_F3029 ASQL_F3029 C2 NOT_RELEASED
ASQL_F3215 ASQL_F3215 C2 NOT_RELEASED
ASQL_F3338A ASQL_F3338A C2 NOT_RELEASED
ASQL_F3398 ASQL_F3398 C2 NOT_RELEASED
ASQL_F3555 ASQL_F3555 C2 NOT_RELEASED
ASQL_F3664 ASQL_F3664 C2 NOT_RELEASED
ASQL_F3697 ASQL_F3697 C2 NOT_RELEASED
ASQL_F3697A ASQL_F3697A C2 NOT_RELEASED
ASQL_F3799 ASQL_F3799 C2 NOT_RELEASED
ASQL_F3915 ASQL_F3915 C2 NOT_RELEASED
ASQL_F3915A ASQL_F3915A C2 NOT_RELEASED
ASQL_F3966 ASQL_F3966 C2 NOT_RELEASED
ASQL_F4001 ASQL_F4001 C2 NOT_RELEASED
ASQL_F4022 ASQL_F4022 C2 NOT_RELEASED
ASQL_F4173 ASQL_F4173 C2 NOT_RELEASED
ASQL_F4173A ASQL_F4173A C2 NOT_RELEASED
ASQL_F4174 ASQL_F4174 C2 NOT_RELEASED
ASQL_F4175 ASQL_F4175 C2 NOT_RELEASED
ASQL_F4307 ASQL_F4307 C2 NOT_RELEASED
ASQL_F4345 ASQL_F4345 C2 NOT_RELEASED
ASQL_F4366 ASQL_F4366 C2 NOT_RELEASED
ASQL_F4367 ASQL_F4367 C2 NOT_RELEASED
ASQL_F4597 ASQL_F4597 C2 NOT_RELEASED
ASQL_F4657 ASQL_F4657 C2 NOT_RELEASED
ASQL_F5293 ASQL_F5293 C2 NOT_RELEASED
ASQL_F5342 ASQL_F5342 C2 NOT_RELEASED
ASQL_F5370 ASQL_F5370 C2 NOT_RELEASED
ASQL_F5371 ASQL_F5371 C2 NOT_RELEASED
ASQL_F5512 ASQL_F5512 C2 NOT_RELEASED
ASQL_F5549 ASQL_F5549 C2 NOT_RELEASED
ASQL_F5600 ASQL_F5600 C2 NOT_RELEASED
ASQL_F6097A ASQL_F6097A C2 NOT_RELEASED
ASQL_F6621 ASQL_F6621 C2 NOT_RELEASED
ASQL_F6622 ASQL_F6622 C2 NOT_RELEASED
ASQL_F6785 ASQL_F6785 C2 NOT_RELEASED
ASQL_F6951 ASQL_F6951 C2 NOT_RELEASED
ASQL_F7308 ASQL_F7308 C2 NOT_RELEASED
ASQL_F7321 ASQL_F7321 C2 NOT_RELEASED
ASQL_F7334 ASQL_F7334 C2 NOT_RELEASED
ASQL_F7343 ASQL_F7343 C2 NOT_RELEASED
ASQL_F7344 ASQL_F7344 C2 NOT_RELEASED
ASQL_F7411 ASQL_F7411 C2 NOT_RELEASED
ASQL_F7738 ASQL_F7738 C2 NOT_RELEASED
ASQL_F7739 ASQL_F7739 C2 NOT_RELEASED
ASQL_F7740 ASQL_F7740 C2 NOT_RELEASED
ASQL_F7741 ASQL_F7741 C2 NOT_RELEASED
ASQL_F8134 ASQL_F8134 C2 NOT_RELEASED
UI_REVNINCRBDGTRULE_MANAGE UI_REVNINCRBDGTRULE_MANAGE V2 C1 NOT_RELEASED
UI_RIBRULEGRANTS_MANAGE UI_RIBRULEGRANTS_MANAGE V2 C1 NOT_RELEASED

Fiori Apps (2)

App IDApp NameTypeDescription
F6621 Manage RIB Rules Transactional Manage RIB Rules Fiori app enables you to define your rules relevant for revenue increasing the budget process.
F7411 Manage RIB Rules for Grants Transactional Manage RIB Rules for Grants Fiori app enables you to define your rules relevant for revenue increasing the budget process once the budget is available via sponsors.

Manage RIB Rules

Business Role: Budget Specialist - Funds Management

You can use this app to define rules for when and how budget increases based on revenues should be performed. A revenues increasing the budget (RIB) rule contains all of the definitions required to increase the budget for specific expenditure budget addresses from specific revenues. It is defined by a unique combination of the fields “Valid from Fiscal Year”, “Company Code” and “Plan Category” with a RIB control object and includes the RIB calculation scheme and the receiving budget addresses. You cannot create a new RIB rule with the same value combination (for the fields Valid from Fiscal Year, Company Code and Plan Category with the same RIB control object) that already exists for a current RIB rule. Note In the RIB profile, you define the fields that are required to define the RIB control object. Once you have done so, only these fields are available as input fields for the RIB control object definition in the Manage RIB Rules app for the related fiscal year, company code and plan category.

Key Features: List existing RIB rules using filter and search options. Create a new RIB rule from scratch or as a copy of an existing RIB rule. Revise existing RIB rules. Delete any RIB rule that is not used and is no longer required. Please note that it is not possible to delete a rule in the following cases: If amounts (from RIB budget documents) are available for a RIB rule for the current fiscal year and if the amount is greater than zero. If amounts (from budget documents) are available for a RIB rule for previous fiscal years. Note If RIB budget documents only exist for the current fiscal you can set the rule to inactive and start the RIB run to distribute the amounts back to zero. Afterwards it is possible to delete the rule. You can use the draft function to interrupt creation or revision until you save the draft to the database. A RIB rule is defined by the valid from fiscal year, company code and plan category in combination with a RIB control object. The RIB rule includes attributes such as the Activation Status, Filter Profile, Calculation Scheme, sender revenue budget address (one) and receiving expenditure budget addresses (one or more). In addition to this, the surplus address (one) is also added to the RIB rule if the Use Surplus Amount indicator is set to Yes in the General Information section of the app. The app allows you to add attachments (documents or URLs). You can also rename, delete or download the uploaded file as required. The change history is displayed to document previous values.

Manage RIB Rules for Grants

Business Role: Grant Specialist

You can use this app to define rules for when and how amounts received from the sponsor increase Grant external budget. A revenues increasing the budget (RIB) for Grants rule contains all definitions required to increase the Grant external budget from revenues received from the sponsor. . It is defined by a unique combination of the field Plan Category with a RIB control object and includes among others the RIB calculation scheme and the receiving budget addresses. You cannot create a new RIB rule with the same value combination Plan Category and RIB control object) that already exists for a current RIB rule. Note In the RIB profile, you define the fields that are required to define the RIB control object. Mandatory fields for the scenario Grantee Management (External) are Grant and Fund. You can include sponsored class and sponsored program to the RIB profile, too. Once you have done so, these fields are available as input fields for the RIB control object definition in the Manage RIB Rules for Grants app.

Fields (14)

KeyFieldSource TableSource FieldDescription
KEY Fund Fund Sender Fund
KEY FinancialManagementArea FinancialManagementArea Financial Management Area
FundName Fund Name
FundDescription Fund Description
FundAuthznGrp FundAuthznGrp Fund Authorization Group
FundFinMgmtAreaForAuthzn FundFinMgmtAreaForAuthzn FM Area for Auth Grp for Fund
ValidityStartDate ValidityStartDate Validity Start Date
ValidityEndDate ValidityEndDate Fund Valid To
FundPeriodicity FundPeriodicity Fund Frequency
GranteeMgmtFundTypeName Fund Type Name in Grantee Management
GrnteMgmtFundTypeNameSearchTxt Short Text for Fixed Values
FundPeriodicityText Frequency Description
_FinMgmtArea _FinMgmtArea
_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_FundStdVH.
-- 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: IFU_VH4

CREATE VIEW I_FundStdVH AS
SELECT
  Fund,
  FinancialManagementArea,
  _Text[1:Language = $session.system_language].FundName AS FundName,
  _Text[1:Language = $session.system_language].FundDescription AS FundDescription,
  FundAuthznGrp,
  FundFinMgmtAreaForAuthzn,
  ValidityStartDate,
  ValidityEndDate,
  FundPeriodicity,
  _FundType._GranteeMgmtFundType._Text[1:Language = $session.system_language].GranteeMgmtFundTypeName AS GranteeMgmtFundTypeName,
  _FundType._GranteeMgmtFundType._Text[1:Language = $session.system_language].GrnteMgmtFundTypeNameSearchTxt AS GrnteMgmtFundTypeNameSearchTxt,
  _FundPeriodicity._Text[1:Language = $session.system_language].FundPeriodicityText AS FundPeriodicityText
FROM I_Fund
;