--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Introduction to the FIORI in S/4HANA.There are 2 main interfaces of FIORI as of today:
- Introduced in 2013 - Classic FIORI by Tile Groups and Tiles
- Introduced in 2020 - Fiori Spaces and Pages with Sections
Answer: SAP Fiori version 1.0, was released in 2013. The main interface was called the Fiori Groups which contain a logical grouping of Fiori Tiles. It introduced a mobile-first design approach with a focus on simplifying business tasks and providing a responsive user experience across different devices. Initially, focused on a mobile-first approach, providing a simplified, user-friendly interface for common business tasks within the existing SAP ECC environment. It initially offered a limited set of 25 transactional apps, like those for approving requests or viewing sales orders, specifically designed to improve the user experience for frequently used functions.
SAP Fiori apps are primarily built using SAPUI5, which is a UI development toolkit for HTML5. SAPUI5 utilizes a combination of web technologies, including:
• HTML5: For structuring the content and defining the layout of the user interface.
• JavaScript: The core programming language for implementing application logic, handling user interactions, and manipulating the UI.
• XML: Often used for defining views and structuring the UI components within SAPUI5 applications.
• CSS: For styling the appearance of the Fiori apps and ensuring a consistent look and feel according to the Fiori design guidelines.
• Notes: While SAPUI5 is the foundation for most web-based Fiori apps, native Fiori apps can also be developed for specific platforms using their respective native languages, such as Swift for iOS or Java for Android. However, the majority of standard SAP Fiori apps are built with SAPUI5.
SAP introduced the next generation Fiori interface called Spaces and Pages in the SAP Fiori Launchpad which was release in S/4HANA 2020 to improve user experience by enhancing organization, personalization, and flexibility in accessing and managing applications. Spaces and pages offer a more structured and intuitive way to navigate the Fiori Launchpad, making it easier for users to find the apps they need for their specific roles and tasks.
To help you to understand SAP Fiori, here are some official links:
To help you to understand SAP Fiori, here are Blog Posts to show the step by steps guides:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: A structural presentation of an example SAP Enterprise Structure for the above Question
As for the PP (Production for Discrete and Process), QM (Quality Management), PM (Plant Maintenance), CS (Customer Service), PS (Project System) module, the Logistics Plant (Apple Green above) is used. In PM and CS, the Plant is used as the Maintenance Plant and the Maintenance Planning Plant. AND in PP-DI or PP-PI, the Plant is referred to as either a Planning Plant or Production Plant. BUT regardless of how the individuals give names to the Plant for its declared usages (this case Planning or Execution), it is the same Plant object.
PLANT is part of LO (Logistics) Enterprise Structure and not specifically for MM, PP or SD, use of Plant is necessary in the following:
Materials Management (MM-PUR): for creating Purchasing DocumentsMaterials Management (MM-IM): for managing Material with Stock scenarioSales & Distribution (SD-DLV): as Delivery Plant for creating Outbound Delivery for Stock scenarioProduction Planning & Execution (PP): as Planning Plant and Production PlantProject System (PS): for Network Activities and Component AssignmentPlant Maintenance (PM): for Maintenance Order ProcessingCustomer Service (CS): for Service Order ProcessingQuality Management (QM): for Inspection Lot Processing
When attempting the TS410 certification, it is important to have some understanding of the Enterprise Structure Relationships like below:
Operating Concern: Each Client must have at least ONE Operating Concern, SAP do not recommend to have more than ONE Operation Concern for each installed Client. Reason is for for simplicity and efficient data management, particularly when all controlling areas within the client share the same fiscal calendar. This approach reduces complexity and simplifies reporting, especially when dealing with a single, global business structure.
Controlling Area: An Operating Concern can be assigned with ONE or MORE Controlling Areas, a Controlling Area can only be assigned to ONE Operating Concern because the Operating Concern is the highest level in the Profitability Analysis (CO-PA) organizational structure, and it defines the scope for analyzing profitability. The assignment links the cost accounting information from controlling areas (which manage cost and revenue) to the profitability analysis performed within the operating concern.Company Code: A Controlling Area can be assigned with ONE or MORE Company Code where the Company Codes need not necessarily be in the same Country. It is Mandatory to assign a Company Code to only ONE Company Code. This assignment is crucial for transferring financial data from FI (Financial Accounting) to CO (Controlling) for internal reporting and management decision-making. Without this assignment, cost and revenue information cannot be tracked and analyzed within the controlling module.Plant: A Company Code can be assigned with ONE or MORE Plants BUT each Plant can be assigned to only ONE Company Code, because a plant represents an operational unit within a company, and the company code is the smallest organizational unit for financial accounting. This assignment ensures that all operational activities within a plant are properly reflected in the company's financial records. Specifically, it allows for accurate valuation of materials, inventory, and other operational aspects within the plant's context, which are then rolled up into the company code's financial statements.Purchasing Organization: In order to be able to create Procurement Orders (like PR or PO), the Purchasing Organization must be assigned to a PLANT. However the SAME Purchasing Organization can be assigned to MORE than ONE Plant. However, assigning a purchasing organization to a company code in SAP is optional because it allows for different purchasing strategies. A purchasing organization can be configured to be company-specific (procuring only for one company code) or cross-company (procuring for multiple company codes). If a purchasing organization is not assigned to a specific company code, it can procure for any plant within the enterprise, regardless of its assigned company code.Sales Organization: Assigning a Sales Organization to a company code is mandatory in SAP's Sales and Distribution (SD) module. Each Sales Organization must be assigned to exactly ONE Company Code, though a company code can have multiple Sales Organizations. However, one DO NOT assign the Sales Organization to the Plant.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review the Business Partner for Vendor (Supplier) BP T-code or BP Fiori App.
Answer: In SAP, the Business Partner (BP) is the central object for managing vendor data, replacing the traditional vendor master in SAP S/4HANA. To designate a BP as a vendor, you assign the "Vendor" BP role to the business partner record, which integrates their data with purchasing and financial functions. This approach provides a single, unified platform for managing all business partner interactions, including vendors, customers, and other parties, streamlining master data maintenance and improving data accuracy.
BP Role "000000" - Business Partner General Role (Address etc)
BP Role "FLVN00" - Business Partner FI Vendor Role (Company Code Reconciliation account)
BP Role "FLVN01" - Business Partner Supplier Role (Purchasing Organization data)See the following Blog Posts on step-by-step to Create or Manage Business Partner for Vendor in S/4HANA:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review on Purchase-to-Pay or Materials Management (MM) Process.
SAP MM Components:
• MM-PUR (Purchasing) - PR, RFQ, Quotation, PO, Contract, Scheduling Agreement• MM-IM (Inventory Management) - Goods Receipt, Stock Transfers, Goods Issues• MM-IV-LIV (Logistics Invoice Verification) - 3-way Matching of Supplier Invoice to GR Material Document and PO Price• MM-MRP-CBP (Consumption Based Planning) - ReOrder Point Planning, Forecasting, Consumption Based Planning
SAP introduced the Material Management (MM) Module in 1972 at the time of the Release of R2, the MM module initially was introduced with the above MM components from PUR, IM, LIV to CBP. It is not until sometime before mid 2000s coincide with transition to ECC that SAP change the MM name to Procurement.
SAP's Procure-To-Pay (P2P) or Purchase-To-Pay (P2P) process is not a specific product or release date but rather a comprehensive approach to integrating purchasing and accounts payable systems. It's a business process framework within SAP, not a single product launch date. This framework encompasses the entire cycle from identifying needs to making payments. SAP's focus on P2P has been a gradual evolution, with different aspects being addressed through various solutions and modules over time.
The latest buzz word is now Source-to-Pay (S2P)! While P2P is more operational, dealing with ordering, receiving, invoicing, and paying for goods and services, S2P extends even further to include involves strategic activities like market analysis, supplier evaluation, and contract negotiation. The new Source-to-Pay (S2P) name likely coincides with SAP introduction of Central Procurement with the release of SAP S/4HANA 1809 (2018) or maybe around 2000. This release included the Central Procurement hub and features like central contracts, purchase orders, requisitioning, and source of supply assignment. It also provided centralized analytics for procurement processes.
See the following Presentations for a Basic flow of MM Purchase Requisition to Invoice Verification:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review on Design-to-Operate or Production Planning & Execution (PP) Process.
Answer: SAP PP or Production Planning and Execution which was likely introduced some time around 1979 when SAP R2 was Released (remember that R1 was mostly Financial functionality which was released in 1972)! Early versions of SAP, like SAP R/2, included capabilities for manufacturing, sales, and distribution, which formed the foundation for what later became the PP module.
Some Milestone of major PP module development timeline:
• 1998: SAP's Advanced Planning and Optimization (APO) module was launched, which included Demand Planning (DP), Supply Network Planning (SNP), PP/DS (Production Planning and Detailed Scheduling) functionality, and Global ATP (GATP) etc.
• 2015: SAP Integrated Business Planning (IBP) was introduced, and in later years, PP/DS was integrated into S/4HANA. SAP Integrated Business Planning (IBP) is a cloud-based solution that helps companies streamline and optimize their supply chain planning processes. It provides a unified platform for demand planning, supply planning, sales and operations planning (S&OP), and inventory management, enabling better decision-making and improved supply chain performance.• 2018: PP/DS was launched as an embedded version within SAP S/4HANA.
The remaining PP component in S/4HANA 2023 are:
Planning: Sales.& Operations Planning (SOP)Planning: Long Term Planning (LTP) - SimulationsPlanning: Master Production Scheduling (MPS) - Planning for Finished GoodsPlanning: Material Requirement Planning (MRP) - Planning for Raw MaterialsPlanning: Embedded Production Planning & Detailed Scheduling (PPDS) - Advanced PlanningExecution: PPDI Discrete Manufacturing Execution using Production OrdersExecution: PPDI Discrete Manufacturing Execution using Repetitive ManufacturingExecution: PPPI Process Manufacturing Execution using Processn OrdersExecution: PPDI or PI using Kanban
Here are 2 Blog Post of using FIORI App to perform PP Planning and PP Execution:
https://docs.google.com/Production Planning/
https://docs.google.com/Production Execution/
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review on Order-to-Cash or Sales & Distribution (SD) Process.
Answer: The Sales & Distribution (SD) Module was introduced alongside the MM Module in 1978 when SAP R2 was Released, it is now called Order-to-Cash (O2C).
The Operation Components of SD are:
• SD-SLS refers to Sales Order Processing• SD-DLV refers to the Delivery within the SD module• SD-BIL refers to the Billing step within the SD module
See the following Presentations for a Basic flow of SD Sales Order to Incoming Payment:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
_U03_040_ExecuteStagingForProduction_Blogged.jpg)
