Question no 4158 : Material Variants Production Version setup

In S/4 1909, Material Variants (Configured Material) required Production Version for a Make-to-Stock scenario, what are the necessary setups ?

(more than one answers)

A) Create a BOM for the Configured Material (Material Variants) via CS01.
B) Assign the Configured Material to the Configurable Material  .
C) Create a Routing for the Configured Material (Material Variants) via CA01.
D) Assign the Configurable Material Routing to the Configured Material (Material Variants) via CA02.
E) Production Version is not required to Planning or Execution in S/4 1909.
.

Answer: B, D

Steps required:

Step 1

Assign the Configured Material to the Configurable Material 

Step 2

    LINK the Material Variant to the Super BOM

Step 3

Assign the Configurable Material Routing to the Configured Material (Material Variants) via CA02.

Step 4

Create the Production Version via C223 and assign the Alternative and Usage number of the Configurable Material plus assign the Configurable Material's Routing Group number and Counter.

SAP HANA - VDM CDS Views vs BW Info Cubes

The Classic OLTP (ECC) to OLAP (BW) data flow scenario:

Transfer structures, transfer rules, and update rules are legacy 3.x data flow components in SAP Business Warehouse (BW) used to map, transform, and load data from a source system into persistent data targets. SAP NetWeaver 7.0 and Later) uses Transformations method that replaced both transfer rules and update rules as of SAP NetWeaver 7.0. 

Extraction from ECC (OLTP)

ECC Extractors: Business content or custom extractors (such as function modules, views, or tables) gather operational data in ECC.
Delta Mechanisms: Updates use timestamps, delta queues, or numeric pointers to pull only changed records during scheduled runs.

Staging and Processing in BW (OLAP)

PSA (Persistent Staging Area): Acts as the first flat-structure receiving table in SAP BW where raw data lands unmodified from ECC.
Transformations & DTPs: Data Transfer Processes (DTP) move data out of the PSA, applying clean-up rules and logic defined in transformations.
DataStore Objects (DSOs): Standard or write-optimized DSOs serve as clean repository layers for consolidated records before they feed reporting cubes.

SAP Virtual Data Model (VDM) built on Core Data Services (CDS) views enables real-time, online operational reporting directly on live transactional data. Because it functions entirely as a virtual abstraction layer over the database, it eliminates data duplication, physical data loads, and reporting latency. This is significant advantage compared to the previous ECC (OLTP) to BW (OLAP) being the foundational architecture for SAP Enterprise Reporting.

  
SAP ABAP CDS Views (CDS) models and structures data using "Dimensions", specifically through analytical annotations that define master data and attributes. AND this is similar to the way Business Warehouse (BW) Info Cubes are structured; except that SAP Core Data Services (CDS) views do not store data physically while BEW InfoCubes stores data physically. 

SAP BW InfoCube Dimensions

1) Hard limit of 16: “There are 16 dimensions available in an Info Cube because the fact table can accommodate this number of dimensions in a star schema.”.
2) Pre-defined structure: Includes 3 system dimensions (Time, Unit, and Data Packet) and up to 13 user-defined dimension tables.
3) Characteristic limits: Each dimension can hold up to 248 characteristics due to database constraints.
4) Similarity: BW InfoCube & S/4 CDS are both data modeling tools.
5) Physical Data Store: is a persistent, physical multi-dimentsional data store in SAP Business Warehouse. The InfoCube storesdata in dedicated fact and dimension tabels (star schema).
6) OLTP to OLAP: Standard InfoCubes in SAP BW physically store data in tables and use scheduled data loads from OLTP database tables to OLAP infocube rather than live online access. As such, BW InfoCube is used in classic SAP BW for enterprise data warehousing, historical analysis, and heavy data aggregation.

SAP ABAP CDS Views (S/4HANA Analytics)

1) No rigid dimension count: CDS views use a flexible virtual data model (VDM) and associations rather than physical dimension tables.  
2) Flat or flexible modeling: Instead of grouping fields into rigid dimension buckets, a CDS view of type #CUBE can expose as many fields (attributes/characteristics) and measures as needed, linked dynamically via associations to separate #DIMENSION CDS views.
3) Field limits: Limited only by underlying SQL view and database column constraints (which allow hundreds of columns), rather than a strict 16-dimension container model. 
4) Similarity: BW InfoCube & S/4 CDS are both data modeling tools.
5) Virtual Data Model: it is code-based Virtual Data Model (VDM) defined in the ABAP/HANA layer. It is vitual and generally non-persistent and do not store any data (compared to BW cubes); they act as virtual data models that fetch, calculate, and structure data dynamically from underlying database tables at runtime.
6) On-line Real time: SAP S/4HANA Core Data Services (CDS) views operate directly on the underlying database without the need for traditional data staging. As such, SAP CDS is used heavily in SAP S/4HANA for Embedded Analytics and real-time operational reporting.

******************************************************************************************************************************************************************

Question no 4157 : Classic and Advanced Configuration Profile

In S/4 1909, the following are characteristics of the Configuration Profile ?

(more than one answers)

A. Classic Configuration Profile can add only classic object dependencies and the advanced object dependencies are ignore.
B. Classic Configuration Profile can add both classic object dependencies and also advanced object dependencies.
C. Advanced Configuration Profile can add only advanced object dependencies and the classic object dependencies are ignore.
D. Advanced Configuration Profile can add both classic object dependencies and also advanced object dependencies.
E. The Classic Configuration Profile are no longer active.
.

Answer: A, C

SAP HANA - VDM, CDS, and Database Tables

Core Data Services (CDS) and the standard Virtual Data Model (VDM) do not exist natively or fully in SAP ECC. SAP ECC reads data directly from physical database tables using ABAP Open SQL statements (like SELECT etc), rather than using Core Data Services (CDS) views.

Core Data Services (CDS) were introduced later by SAP with the advent of SAP S/4HANA and modern ABAP platforms to build a Virtual Data Model (VDM). Classic ECC architecture predates widespread CDS usage.

It is important to note that Core Data Services (CDS) and the Virtual Data Model (VDM) in SAP are strictly virtual definitions that fetch data dynamically at runtime rather than persisting or storing it physically. Physical records reside exclusively in underlying database tables. CDS and VDM do not store any data. 

A VDM is not a single file or a lone view; rather, it is a structured network or framework of multiple stacked and layered CDS views designed to work together, a single Virtual Data Model (VDM) in SAP S/4HANA always contains multiple Core Data Services (CDS) views. SAP builds the VDM using a hierarchical network of CDS views.

At the database runtime level, both VDM and non-VDM CDS views execute identical SQL statements against the actual database tables. The database engine does not change its reading behavior. Both Virtual Data Models (VDM) and Core Data Services (CDS) views ultimately rely on SQL to read data from underlying physical database tables. 

The SAP Virtual Data Model (VDM) is a structured architectural framework used to build reusable, high-performance data models using ABAP Core Data Services (CDS) views. It enforces a multi-layer design to separate raw database interaction from final application delivery.

The SAP Virtual Data Model (VDM) uses three primary user-facing and reuse layers built with Core Data Services (CDS) views: Basic/Interface, Composite, and Consumption.

1. Basic Views (@VDM.viewType: #BASIC)

• Basic views represent the foundation of the VDM stack. They are the only views allowed to interact directly with physical database tables.

2. Composite Views (@VDM.viewType: #COMPOSITE)

• Composite views live in the middle layer, serving as the reusability engine of the VDM. They cannot access the physical database directly.
• Virtual Data Model (VDM) consumption view can include aggregations and calculations, typically built on top of composite cube views to serve analytical queries and UI applications.

3. Consumption Views (@VDM.viewType: #CONSUMPTION)

• Consumption views act as the definitive top layer of the VDM stack, customized for specific business applications.

• In SAP ABAP Core Data Services (CDS), the Consumption View is the top-most layer designed specifically to interact with frontend applications and external programs.

In the SAP S/4HANA architecture, CDS (Core Data Services) views and the VDM (Virtual Data Model) represent a purely logical semantic layer and do not physically store or replicate data. They act as blueprints or definitions that read real-time data from actual, physical tables down in the database. 

(note: the above represents summary view of VDM and CDS in the S/4HANA system by a non-Technical person, the written notes are based on research material reading from SAP help.sap.com. Pleaes refer to the right technical expertise for precise information about the subject matter).

******************************************************************************************************************************************************************

References:

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/Virtual Data Model and CDS Views/
https://blog.sap-press.com/an-overview-of-the-sap-s4hana-vdm
https://help.sap.com/docs/SAP_S4HANA_CLOUD/Virtual Data Model and CDS Views in SAP S/4HANA Cloud Public Edition/

https://blog.sap-press.com/how-to-create-a-basic-interface-core-data-services-view-with-abap

https://www.cnblogs.com/虚拟数据模型/

 
Videos:

SAP Press: How Does CDS Relate to the SAP S/4HANA Virtual Data Model?

SAP Press: How Is Analytics Implemented in CDS?

******************************************************************************************************************************************************************

The fundamental difference between VDM and CDS in SAP is that CDS (Core Data Services) is the underlying technology and language, while VDM (Virtual Data Model) is the architectural blueprint, semantic design, and rule book built using that technology.

Think of the difference between CDS and VDM as:

CDS are the BRICKs.
VDM are the WALLs.

CDS (Core Data Services) = The BRICKs

• Definition: CDS is the foundational technology used to define and consume semantic data models. It is a technical infrastructure, DDL syntax, and data modeling framework.
• Analogy: They are the individual, raw building blocks. A single brick (a basic CDS view) contains data but does not represent a complete structural feature on its own. You need many of them to build something meaningful.
• Purpose: Pushes heavy data processing down to the HANA database layer (Code-to-Data paradigm).
• Scope: Generic tool; anyone can build any arbitrary query or view using CDS.

VDM (Virtual Data Model) = The WALLs

• Definition: VDM is the structured, layered framework built on top of database tables using CDS views. It organizes data into reusable, business-oriented layers (like Interface, Composite, and Consumption views). It is a structured semantic layer and architectural guidelines.
• Analogy: The wall is the final structure. It is built by systematically arranging the bricks (CDS views) according to an architectural blueprint. The wall serves a specific purpose, like supporting a room or acting as a boundary.
• Purpose: Abstracts raw, complex SAP database tables into understandable business entities.
• Scope: Specific design standard used by SAP to model all standard business processes.

******************************************************************************************************************************************************************

SAP GUI Transaction Codes:

• SE11 (ABAP Dictionary): Enter the SQL view name of the CDS view to display its structure, then double-click the DDL name to open the data definition.
• SDDLAR (CDS Repository): Used to display CDS view definitions and run consistency checks directly in the SAP GUI.
• SE80 (Object Navigator): Select Repository Info System or edit object by entering the DDL (Data Definition Language) name to view the data definition.
• RSRTS_ODP_DIS: Used to check and preview analytical or cube-based CDS views.

Fiori and Developer Tools:

• View Browser (Fiori App ID F2170): The official app to search, explore, and analyze CDS-based Virtual Data Models and their cross-references.
• ABAP Development Tools (ADT): The Eclipse-based environment used by developers for advanced dependency analysis and viewing complete VDM hierarchies.

******************************************************************************************************************************************************************

OData Service: An SAP OData service bridges raw database tables and front-end UIs by turning business data into a web-ready API. It acts as the delivery mechanism, while Core Data Services (CDS) structure the data, the Virtual Data Model (VDM) organizes it into meaningful business concepts, and the Database stores the physical records.

How the Components Work Together:

SAP Fiori application + SAP Business Object BI Tools + 3rd Party UI/Client + Cloud Reporting Tools

↑↑↑↑

OData Service: The final communication protocol (REST-based API) generated on top of the VDM consumption views, allowing tools like SAP Fiori or external clients to query and modify the data.

↑↑↑↑

VDM (Virtual Data Model): A structured, layered collection of CDS views (Basic, Composite, and Consumption) that translates technical database fields into clear business objects like SalesOrder or Product.

↑↑↑↑

CDS (Core Data Services): SQL-like data definitions written in code that read from the database, add calculations, and define joins or associations.

↑↑↑↑

Database: The foundation layer holding physical tables (like VBAK or VBAP) with technical column names

******************************************************************************************************************************************************************

Question 4156 : PP Planning Strategy

In S/4 1909, consider the following characteristics

• The Dependent Requirement from the Finished Product Consumes the Sub-assembly Forecast
• The Strategy need not necessary have a Requirement Type for Customer Requirement
• Forecast is created at the Sub-assembly level
• The Finished Product can be MTO or MTS
• Mixed MRP indicator "1" is to be set to the Sub-Assembly's MRP3 view
• Goods Issue of the Sub-assembly to the Finished Goods Prod Order will reduce the Sub-assembly Forecast

which of the following Strategy fits the above descriptions ?

(only one answer)

A) Strategy 10
B) Strategy 20
C) Strategy 40
D) Strategy 50
E) Strategy 70

Answer : E

Question 4155 : Period Specific Consumption (MRP3 view in the Material Master)

In SAP S/4 1909, the MRP3 data view (Material Master), which of the correct are correct about the features of the Consumption Mode "5" (Period Specific Consumption) ?

(more than one answers)

A) The Period indicator in the Planned Independent Requirement plays a role in deciding if a Sales Order of a certain date will consumed the PIR.
B) The Planning Horizon now at the MRP Group Parameter or Plant Parameter in sequence of Priority will now play a role in deciding if a Sales Order of a certain date will consumed the PIR.
C) The Time Fence in the MRP1 data view will now play a role in deciding if a Sales Order of a certain date will consumed the PIR.
D) The Forward and Backward Consumption Period in MRP3 view must be set as "X" to avoid wrong Consumption.
E) The Forward and Backward Consumption Period in MRP3 view should be set to "0" (zero).
.

click "1 comment" to view the suggested solution

Answer: A, E

The 2 main criteria's of Period Specific Consumption
A) The PIR's Period indicator is important
E) The Forward/Backward periods can now be zero

Question 4154 : Primary Objective of DDMRP

In SAP S/4 1909, the Primary Objective of DDMRP is to enable ______________________ .

(only one answer)

A) Material FLOW.
B) Balance COST and Investment.
C) Kanban EXECUTION more effectively.
D) Combine KANBAN and MRP.
E) Optimization of the Production Scheduling.
.

click "1 comment" to view Possible Solution
Answer: A

DDMRP is a multi-echelon planning and execution approach to protect and promote the flow of information through the supply chain by establishing and managing strategically placed decoupling point stock buffers.

Question 4153 : Calibration Planning characteristics

In SAP S/4 1909, which of the following are TRUE about Calibration Planning for Equipment's using the QM module's assistance ?

(more than one answers)

A) Measuring Points in the Equipment Master are necessary for Calibration Planning.
B) Option to use either use Inspection Plan or Maintenance Task List for Calibration Planning.
C) Inspection Point assignment in the Maintenance Task List header is Mandatory for Calibration Planning.
D) Both Functional Locations and Equipment can be assigned in the Calibration Plans
E) Cycle Modification Factor can be entered during Results Recording or Usage Decision.

.
Answer: C, D

A) No. Measuring Point either in EQ or FL is not mandatory for Calibration Planning, meaning the calibration results can be recorded in the Inspection Lot without updating the measuring document to the measuring points. 
B) No. not in the Inspection Plan, but the Plant Maintenance's Task List is used to define setup the Inspection Characteristics required for the Calibration. 
C) Yes, An appropriate Inspection Point must be assigned to the Maintenance Task List Header.
D) Yes, In SAP, both FL and EQ can be assigned in the Calibration Plans.
E) No, Only at UD that the Cycle Modification Factor can be changed.