REPM_DepSalesOrderV3

DDL: REPM_DEPSALESORDERV3 SQL: REPM_DEPSOV3 Type: view
15 Fields 1 Data Sources 2 Associations

Department Sales Order

REPM_DepSalesOrderV3 is a CDS View of category Cube that provides data about "Department Sales Order" in SAP S/4HANA. It reads from 1 data source (REPM_SalesOrderV3) and exposes 15 fields. It has 2 associations to related views.

Data Sources (1)

SourceAliasJoin Type
REPM_SalesOrderV3 SalesOrder from

Associations (2)

CardinalityTargetAliasCondition
[1] SEPM_I_SlsOrdLifeCycleStatusT _LifeCycleText $projection.LifeCycleStatus = _LifeCycleText.SalesOrderLifeCycleStatus
[1] Repm_DepartmentV3 _Department $projection.DepartmentUUID = _Department.DepartmentUUID

Annotations (4)

NameValueLevelField
AbapCatalog.sqlViewName REPM_DEPSOV3 view
AccessControl.authorizationCheck #NOT_REQUIRED view
EndUserText.label Department Sales Order view
Analytics.dataCategory #CUBE view

Fields (15)

KeyFieldSource TableSource FieldDescription
CreatedByUser REPM_SalesOrderV3 CreatedByUser User Name
SalesOrderID REPM_SalesOrderV3 SalesOrder SD Document
EmployeeName REPM_SalesOrderV3 EmployeeName Employee Name
DepartmentName REPM_SalesOrderV3 DepartmentName
DepartmentUUID REPM_SalesOrderV3 DepartmentUUID
TotalGrossAmount Total Revenue
TransactionCurrency REPM_SalesOrderV3 TransactionCurrency Transaction Currency
LifeCycleStatus REPM_SalesOrderV3 LifeCycleStatus Life Cycle Status
CustomerName REPM_SalesOrderV3 CompanyName Text
CustomerEmailID REPM_SalesOrderV3 CustomerEmailID
EmployeeEmailID REPM_SalesOrderV3 EmployeeEmailID
EmployeePhoneNo REPM_SalesOrderV3 EmployeePhoneNo
EmployeeCity REPM_SalesOrderV3 EmployeeCity
_LifeCycleText _LifeCycleText
_Department _Department

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 REPM_DepSalesOrderV3.
-- 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: REPM_DEPSOV3

CREATE VIEW REPM_DepSalesOrderV3 AS
SELECT
  SalesOrder.CreatedByUser AS CreatedByUser,
  SalesOrder.SalesOrder AS SalesOrderID,
  SalesOrder.EmployeeName AS EmployeeName,
  SalesOrder.DepartmentName AS DepartmentName,
  SalesOrder.DepartmentUUID AS DepartmentUUID,
  sum(SalesOrder.GrossAmount) AS TotalGrossAmount,
  SalesOrder.TransactionCurrency AS TransactionCurrency,
  SalesOrder.LifeCycleStatus AS LifeCycleStatus,
  SalesOrder.CompanyName AS CustomerName,
  SalesOrder.CustomerEmailID AS CustomerEmailID,
  SalesOrder.EmployeeEmailID AS EmployeeEmailID,
  SalesOrder.EmployeePhoneNo AS EmployeePhoneNo,
  SalesOrder.EmployeeCity AS EmployeeCity
FROM REPM_SalesOrderV3 AS SalesOrder
LEFT OUTER JOIN SEPM_I_SlsOrdLifeCycleStatusT AS _LifeCycleText ON LifeCycleStatus = _LifeCycleText.SalesOrderLifeCycleStatus  -- association [1]
LEFT OUTER JOIN Repm_DepartmentV3 AS _Department ON DepartmentUUID = _Department.DepartmentUUID  -- association [1]
;

Learn More