C_AllocationCycleVH

DDL: C_ALLOCATIONCYCLEVH SQL: CALOCYCLEVH Type: view CONSUMPTION

Allocation Cycle Value Help

C_AllocationCycleVH is a Consumption CDS View that provides data about "Allocation Cycle Value Help" in SAP S/4HANA. It reads from 2 data sources (C_AllocationContextVH, P_AllocationCycle) and exposes 12 fields with key fields AllocationCycle, AllocationType, AllocationCycleStartDate. It has 2 associations to related views. It is exposed through 2 OData services (FCO_ALLOCATION_RUN_GROUP, FCO_ALLOCATION_TAG_V3). It is used in 2 Fiori applications: Manage Allocation Tags, Manage Cycle Run Groups.

Data Sources (2)

SourceAliasJoin Type
C_AllocationContextVH _context inner
P_AllocationCycle P_AllocationCycle from

Associations (2)

CardinalityTargetAliasCondition
[1..1] P_AllocationCycle _AllocationCycleCalc $projection.AllocationType = _AllocationCycleCalc.AllocationType and $projection.AllocationCycle = _AllocationCycleCalc.AllocationCycle and $projection.AllocationCycleStartDate = _AllocationCycleCalc.AllocationCycleStartDate
[1..1] I_UserContactCard _CreatedByUserContactCard $projection.CreatedByUser = _CreatedByUserContactCard.ContactCardID

Annotations (11)

NameValueLevelField
AbapCatalog.sqlViewName CALOCYCLEVH view
AccessControl.authorizationCheck #CHECK view
EndUserText.label Allocation Cycle Value Help view
VDM.viewType #CONSUMPTION view
ObjectModel.usageType.sizeCategory #S view
ObjectModel.usageType.serviceQuality #C view
ObjectModel.usageType.dataClass #MASTER view
ClientHandling.algorithm #SESSION_VARIABLE view
ObjectModel.dataCategory #VALUE_HELP view
ObjectModel.representativeKey AllocationCycle view
Search.searchable true view

OData Services (2)

ServiceBindingVersionContractRelease
FCO_ALLOCATION_RUN_GROUP FCO_ALLOCATION_RUN_GROUP V2 C1 NOT_RELEASED
FCO_ALLOCATION_TAG_V3 FCO_ALLOCATION_TAG_V3 V2 C1 NOT_RELEASED

Fiori Apps (2)

App IDApp NameTypeDescription
F4523 Manage Allocation Tags Transactional This app provides tagging functionality for Universal Allocation data
F4935 Manage Cycle Run Groups Transactional You use this app to manage your allocation cycle run groups. With this Fiori application, user can maintain cycle run groups and assign allocation cycles into the run groups. With grouping provided, parallel processing of allocation cycles is possible.

Manage Allocation Tags

Business Role: Cost Accountant - Overhead

With this app, you can create and assign allocation tags. Allocation tags are semantic tags you can assign to allocation cycles and segments that allow you to group and identify those cycles and segments. The tags can be used across allocation contexts and types, allowing you to track and label all elements of an allocation process.

Manage Cycle Run Groups

Business Role: Cost Accountant - Overhead

With this app, you can organize allocation cycles into groups to enable parallel processing. If you don't organize your allocation cycles into groups, the cycles are always processed sequentially. This can be time consuming. A cycle run group is always processed in parallel with other cycle run groups, so you can significantly reduce the processing time if you organize your allocation cycles into groups. The allocation cycles within a single group are processed sequentially, but in parallel with other groups.

Fields (12)

KeyFieldSource TableSource FieldDescription
KEY AllocationCycle AllocationCycle Cycle
KEY AllocationType P_AllocationCycle AllocationType Table
KEY AllocationCycleStartDate AllocationCycleStartDate Valid From
AllocationContextTypeText C_AllocationContextVH AllocationContextTypeText
AllocationCycleName _AllocationCycleCalc AllocationCycleName Allocation Cycle
AllocationCycleNameText _AllocationCycleCalc AllocationCycleNameText Cycle Description
FullName _CreatedByUserContactCard FullName Name
CreatedByUser CreatedByUser User Name
Ledger Ledger Ledger
AllocationPostingType AllocationPostingType Posting Type
AllocationActualPlanVariant AllocationActualPlanVariant Actual/Plan
_CreatedByUserContactCard _CreatedByUserContactCard

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_AllocationCycleVH.
-- 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: CALOCYCLEVH

CREATE VIEW C_AllocationCycleVH AS
SELECT
  AllocationCycle,
  P_AllocationCycle.AllocationType AS AllocationType,
  AllocationCycleStartDate,
  _context.AllocationContextTypeText AS AllocationContextTypeText,
  _AllocationCycleCalc.AllocationCycleName AS AllocationCycleName,
  _AllocationCycleCalc.AllocationCycleNameText AS AllocationCycleNameText,
  _CreatedByUserContactCard.FullName AS FullName,
  CreatedByUser,
  Ledger,
  AllocationPostingType,
  AllocationActualPlanVariant
FROM P_AllocationCycle
INNER JOIN C_AllocationContextVH AS _context ON /* join condition not captured in parsed metadata */
LEFT OUTER JOIN P_AllocationCycle AS _AllocationCycleCalc ON AllocationType = _AllocationCycleCalc.AllocationType AND AllocationCycle = _AllocationCycleCalc.AllocationCycle AND AllocationCycleStartDate = _AllocationCycleCalc.AllocationCycleStartDate  -- association [1..1]
LEFT OUTER JOIN I_UserContactCard AS _CreatedByUserContactCard ON CreatedByUser = _CreatedByUserContactCard.ContactCardID  -- association [1..1]
;