This Blog is mainly on SAP Exam Questions and Selected "How-to" SAP processes

Tuesday, June 17, 2025

SAP SD - Business Partner Customer via Fiori HTML and UX App

CLICK here to view the Presentation

at No comments:
Labels:

S/4 FI - Old and new General Ledger

 
CLICK here to view the Presentation

at No comments:
Labels:

Monday, June 16, 2025

Q&A in Class (2025-06-16) S4H02

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is the difference between the "Classic Service Management" vs the "Cloud Service" 

Answer: The Classic SAP CS (Customer Service) module (sometimes referred to as "Service Management" is an on-premise solution primarily focused on managing service processes within an SAP ERP system, which was introduced in the 1990s when SAP released its R/3 system. While SAP  Service Cloud, is a Cloud-based Solution offering a broader range of customer service capabilities and integration across various channels. It is important to note that the Classic CS module is nearing the end of its lifecycle and is being replaced by the new S/4HANA Service module, which is more closely aligned with the cloud-based SAP Service Cloud. 

Some pointers when considering Classic SAP CS or the new Cloud CS:
• Replacement: SAP reported that the S/4HANA Cloud Service is the successor the the Classic CS module.  
• Data Model: SAP claims that both the Classic CS module and S/4HANA Service Cloud  
are leveraging on the same data model and infrastructure. (However, after using it, there are some differences). 
• Functionality: The Classic CS module primarily handles service order management, warranty claims, service contracts, and field service within an SAP ECC or S/4HANA environment. While the new Service Cloud provides a comprehensive suite of tools for managing customer service interactions across various channels, including phone, email, chat, social media, and self-service portals; offering seamless integration with other SAP solutions like SAP Sales Cloud and SAP Marketing Cloud, as well as third-party systems. 
• Lifecycle: It is important to understand the Classic CS module is part of R/3 and ECC system but carried over the the S/4HANA system but is now reaching the end of its Maintenance Period in 2025 (From 2026 until the end of 2030, you can still use the SAP CS module in compatibility mode and for an additional charge in Extended Maintenance). It can be concluded that the S/4HANA Service Cloud as a Cloud solution, it benefits from continuous updates and enhancements by SAP.
• New Names: SAP now also calls their "Service Cloud" as "Service Management in SAP S/4HANA Cloud" as there is now a confusion between "Cloud Service" and "Service Cloud"! Therefore, because of what is refer to it today. 

See the following official links to 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Show the navigations to Find Fiori App in the fiorilibrary in the Web. 



Answer: See the following Demo: 
https://docs.google.com/presentation/DiscoverS/4FIORIApps/

Here are some SAP Official Resources for FIORI: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: SAP introduced the "Space and Pages" FIORI Front-end Presentation as an alternative to the "Fiori Tile Groups", what are some difference and how to setup "Spaces and Pages"?


Answer: The new "Spaces and Pages" DEMO: 
https://froggysap.blogspot.com/2024/12/sap-s4hana-fiori-2023-space-pages.html

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: FIORI Setting explore.


Answer: Here some a Blog Posts or some FIORI Settings; 
https://froggysap.blogspot.com/2022/04/s4-fiori-some-settings.html

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: How to for an Analytics (Report) FIORI App/Tile to be "SAVE as Tile"?


Answer: "SAVE as a TILE" steps as below: 
https://froggysap.blogspot.com/2025/06/find-technical-object-1-filter-settings.html

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Show an example of an Accounting User's FIORI Group and FIORI Tile Assignment and how it is related to the SAP User Role ? 


Answer: SAP Provide the Standard FIORI Catalogs, and FIORI Roles for direct assignment to the User. However the FIORI Admin can also use /n/UI2/FLPD_CUST in the command box in the FIORI Admin login to check and/or re-group (define new ones) of the FIORI Tile Group and FIORI Catalogs. 
See the Blog Post:
https://froggysap.blogspot.com/2025/06/q-in-class-2025-06-16-s4h02.html

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

at No comments:
Labels:

Find Technical Object (1) Filter, Settings, save as EXCEL and new FIORI TILE

 

click "here" to view Presentation

at No comments:
Labels:

SAP FIORI - Fiori App for FI User PFCG and /n/UI2/FLPD_CUST


at No comments:
Labels:

Question no 4053 : Create Storage Location Automatically

In Material Management as at S/4 1909, "Create Storage Location Automatically" can be set in which of the following Parameters ?

(only one answer)

A. Plant and Movement Type
B. Movement Type only
C. Plant and MIGO variant
D. Material Type and Movement Type.
E. Plant, Material Type and Movement Type.
.

Answer: A

Check IMG t-code OMB3



at No comments:
Labels: ,

Friday, June 13, 2025

SAP FI-MM - Currency Type "10" and "30" (Understanding for Non-Accounting people)

CLICK here to view the Presentation

at No comments:
Labels: ,

SAP MM - Exchange Rate Difference and Trx Event Key KDM

at No comments:
Labels: ,

Tuesday, June 10, 2025

Q&A in Class (2025-06-12) S4H00

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review some of the FIORI Navigations and Settings.


Answer: SAP Fiori is a user experience (UX) and design system that SAP uses to build business applications. It's designed to create a more intuitive and user-friendly interface for SAP software, especially for mobile devices and web applications. Fiori provides a simplified, role-based experience with role-based tiles that encapsulate common processes, such as viewing sales orders or approving timesheets. It's used across various SAP products, including S/4HANA and C/4HANA suites, SAP Analytics Cloud, and others. 

Here's a more detailed breakdown:
• Simplicity and Usability: SAP Fiori is a web-based user experience platform. It provides a modern and user-friendly interface for SAP applications that can be accessed through a web browser. The new interface to SAP prioritises a clean, easy-to-use interface, making it easier for users to navigate and interact with SAP applications. 
• Role-Based Access: The system is designed to provide users with access to the specific information and functionalities they need for their role, streamlining their workflow. 
• Mobile-First Design: Fiori (some of it) is built with mobile devices in mind, ensuring a responsive and user-friendly experience on various devices. SAP Fiori can be used on both Android and iOS devices. SAP provides native applications for both platforms, allowing users to experience Fiori applications on their mobile devices with features optimized for each operating system. 
• Design System: Fiori provides a design language, templates, tools, and guidelines for developers to create visually appealing and consistent applications. 
• Integration: Fiori integrates well with existing SAP systems and applications, including S/4HANA, C/4HANA, and other products TechTarget (eg: IBP or Integrated Business Planning, SuccessFactors, SAP Concur, SAP FieldGlass, Ariba etc) 
• Development Framework: Fiori includes a framework and tools for developers to create and deploy new applications, such as the ABAP Programming Model for SAP Fiori. 

Here are some Blog Posts that illustration the Navigations and Settings for FIORI Usage: 

Here are some SAP Official Resources for FIORI: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review some of the Enterprise Structure Relationships in SAP.


Answer: In SAP, the enterprise structure defines how a company's organization is represented within the system. It's a hierarchical framework that reflects the real-world company's structure, encompassing legal, organizational, and operational aspects. This structure is crucial for setting up master data and configuring business processes.

Key Components of SAP Enterprise Structure:
• Client: The highest level, representing a self-contained system with its own data. 
• (CO) Operating Concern: is a key organizational unit within Profitability Analysis (CO-PA) and usually recommend to have one Operating Concern for a Controlling Area.
• (CO) Controlling Area: is an organizational unit used for managing costs and profits within a company or a group of companies. Each Controlling Area can be assigned with Multiple Company Codes. 
• (FI) Company Code: Represents a legal entity, a separate legal and accounting unit. 
• (SD) Sales Organization: Responsible for the overall sales strategy and processes and usually mapped to the way the Company manage sales via Georgrahical definitions like North Region Sales Organization, South Region Sales Organizations. The Sales Organization is assigned to the Company Code. 
• (SD) Distribution Channel: Defines how goods or services are sold (e.g., Online, Retail, Wholesale etc). Distribution Channels(s) are assigned to the Sales Organization. 
• (LO&SD) Division: A logical grouping of products or services. Assigning Division(s) to Sales Organization(s) is a fundamental configuration step in SAP SD. It facilitates product categorization, sales focus, reporting, and the development of efficient sales strategies. The Division is also assigned to the Material Master (Products or Services Material) to declare Products or Services "belong" to which Division of the Company. 
• (SD) Sales Area: is a combination of three key elements: Sales Organization, Distribution Channel, and Division. This combination defines how a company conducts its sales activities, influencing pricing, order types, and other aspects of the sales process. Sales Area is Mandatory when creating a Sales Document. 
• (SD) Sales Group: a Sales Group is a grouping of salespeople or organizational units within a sales office, responsible for a specific set of products or customer segments. Sales Group(s) are assigned to Sales Office(s). 
• (SD) Sales Office: represents a specific physical location or geographical region within a company that manages sales activities. It's essentially a local hub for sales operations, often representing a branch office or a dedicated sales team within a larger organization. Sales Office(s) are assigned to the Sales Area.
• (MM) Purchasing Organization: Responsible for procurement and supplier relationships. The Purchasing Organization is assigned to the Company Code and Plant. Purchasing Organization is Mandatory when creating a Purchasing Document. 
• (MM) Purchasing Group: a unit within an organization responsible for procuring specific materials or services. It represents a buyer or group of buyers who handle the procurement process for a particular material or class of materials. The Purchasing Group is NOT assigned to any Enterprise Structure in the Configuration BUT it is assigned in the Material Master Purchasing view AND assigned in the Business Partner Vendor. Purchasing Group is mandatory in the Purchase Requisition Line Item AND in the Header of the Purchase Order. 
• (LO) Plant: A physical location where goods are produced or stored, this is where all logistics activities takes place and that is why it is mandatory when creating a PP Production Order, MM Puchase Order, SD Sales Order, PS Network Order, PM Maintenance Order, CS Service Order, and QM Inspection Lot. The Plant is assigned to the Company Code. 
• (MM) Storage Location: A specific location within a plant where materials are stored. But this is considered a Rough Storage where detail storage up to Rack, Bin levels must then consider implementation of LE-WM or LE-EWM functionality. 
• (SD) Shipping Point: a designated location from which goods are shipped to customers. The Shipping Point(s) are assigned to the Plant. Shipping Point is mandatory when creating an Outbound Delivery in LE-Delivery. 
• (LE) Transportation Planning Point: An organizational unit in Logistics, responsible for planning and processing transportation activities. The Transportation Planning Point (TPP) is assigned to a Company Code. TPP is mandatory when creating a Shipping Document in Transportation. 
• (LE) Classic Warehouse: Provides warehouse management functionality for smaller warehouses. LE-WM module is now revamped as Stock Room Management in S/4HANA. The Classic Warehouse number is assigned to Plant + Storage Location combination. 
• (LE) EWM Warehouse: Provides warehouse management functionality for complex or larger warehouses. EWM or Extended Warehouse Management is now the recommended solution for complex Warehouse Structuring and Activities. The EWM Warehouse is assigned to the LE-Warehouse. 
• (HR) Personnel Area: key element in SAP's Human Capital Management (HCM) module, used for personnel administration, time management, and payroll processing. The Personnel Area is assigned to a Company Code. 
• (HR) Personnel Subarea: is a subdivision of a personnel area, used for more granular control and organization of employee data, particularly regarding pay, work schedules, and payroll.

Answer: See the Blog Posts for illustration of MM, SD, and EWM Enterprise Structure explanations in more details: 

You can also review about SAP Enterprise Structure using the following SAP official Resources:
https://learning.sap.com/learning-journeys/explore-integrated-business-processes-in-sap-s-4hana-/explain-the-organizational-structures/

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: A structural presentation of the above Question

Answer: The above "lines" linking between Enterprise objects are necessary for FI, CO, HR, MM, PP, SD, PS, QM, PM, CS, E&HS, TM, LE, and PDM except there is no direct assignment (dotted lines) from Purchasing Group to the Purchasing Organisation in the Enterprise Structure IMG configuration.

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. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Is COPA obsolete in S/4HANA, if ECC is using COPA when migration to S/4HANA should COPA be also activated as part of the migration step?

Answer: Yes, SAP Costing-based COPA (CO-PA) is still valid in SAP S/4HANA, although SAP recommends Account-based CO-PA as the default solution according to a blog post. You can still use Costing-based CO-PA alongside Account-based CO-PA if desired.

• SAP's Recommendation:
SAP's approach is to transition towards Account-based CO-PA, also known as Margin Analysis, within S/4HANA.
• Costing-based CO-PA Availability:
SAP continues to support Costing-based CO-PA in S/4HANA, even though they are not actively developing it further.
• Parallel Use:
You can run both Costing-based and Account-based CO-PA in S/4HANA simultaneously if your business needs require it or in transition from the "Classic Costing-based CO-PA" to the "Account-based CO-PA". 
• Business Case:
The choice between the two COPA versions depends on your specific business requirements and how you want to analyze profitability. 
• Account-based CO-PA Advantages:
Account-based CO-PA provides real-time integration with General Ledger and streamlined reporting. 
• Costing-based CO-PA Advantages:
Costing-based CO-PA offers a more granular view of costs and revenues, particularly useful for industries like automotive servicing where cost objects like sales orders or projects are 
commonly used.
• Between Simplicity to Complexity:
Account-based CO-PA in SAP uses general ledger accounts for posting cost of goods sold (COGS), while costing-based CO-PA uses value fields to allocate and trace costs. Account-based CO-PA is easier to configure and maintain, while costing-based CO-PA allows for more granular cost analysis.

Migration Considerations: (According to a SAP Expert on the Web)
  1. The migration process to SAP S/4HANA as well as to SAP in general does not offer any tools to migrate the historical information in costing-based CO-PA to account-based CO-PA. You must consider if the historical data from costing-based CO-PA is needed for future analyses. If yes, then how much of that is needed (for example, historical data of three previous years)? Accordingly, this must be undertaken as a separate project to migrate the historical information into account-based CO-PA.
  2. While it would be an ideal situation to migrate the historical data to account-based CO-PA in the same timelines as SAP S/4HANA migration, it is quite unlikely to happen. Considering the criticality of the SAP S/4HANA migration and the complexity of the historical data migration from costing-based CO-PA to account-based CO-PA, it is advisable to keep both the projects separate.
  3. Hence, there might be a transition period post migration to SAP S/4HANA, in which both account-based CO-PA and costing-based CO-PA are active simultaneously. Once the historical data is migrated, the plug on costing-based CO-PA can be pulled (by deactivating the costing-based CO-PA in the operating concern using transaction code KEA0).
  4. There could be another option to handle the historical data in costing-based CO-PA, which is to make use of data warehousing tools to store the historical information. This can then be used for future analyses. However, this also needs to be taken up as a separate project.
See the following for Expert views:
https://www.pikon.com/en/blog/co-pa-in-s4hana/
https://community.sap.com/is-account-based-copa-going-to-replace-costing-based-copa-in-s4/d  

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Questions: Explain the SAP Scenario Processing setup from Enterprise Structure to Primary Master Data to Secondary Master Data to Scenario Processing.

Answer: The following link to diagrams of "linked lines" of each level (details already explained in class): 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: When a Company uses Local Currency Type "10" EUR, and no other operations overseas, why is it recommended to also setup Global Currency Type "30" as EUR again with a conversion of 1:1?


Answer: Before begin, let's understand (assume a LOCAL Company in Malaysia):
• Local Currency: This is the Company Code Currency MYR.
• Global Currency: Example if the Company in Malaysia (MYR) is only a Branch of a Singapore Company (SGD) then the Malaysia Company should have the Global Currency set (SGD).
• Transaction Currency: So, a Purchase Order from a Vendor in Germany may require to be in (EUR), this EUR will be the Transaction Currency which will be converted to the Local Currency (MYR). 
• Document Currency: This Currency is also usually the Transaction Currency. 
Let's assume a Local Company which do not have any branches of entities outside a country; and except for "Transaction Currencies" which could be different from the Local/Company Code Currency (of Let's say MYR); then it is still necessary to setup the Global Currency with MYR as perhaps seems to be a redundant setting. 

Note that according to SAP FI Experts, the Global Currency can still be opted out (EMPTY) and not defined for a new Company (meaning only Local Currency); BUT if there is a future need to assign a Global Currency to this Company, it will be an Impossible Task. In order to TRY to make such a change, it will be new PROJECT !!!!
That said, SAP HIGHLY RECOMMEND to setup the Local Currency as the Global Currency for any Company Code in S/4HANA. AND that's why to avoid confusion, it is SAVE to say that the "Global Currency" is Mandatory in S/4HANA for any Company Code regardless of the Business Case. 

When time permit will posts an example of a 2 Companies (soon):
                            Country        Local Currency            Group Currency
                                                 (Currency Type 10)    (Currency Type 30)
Headquarters       Germany         EUR                             EUR
Subsidiary            US                   USD                             EUR

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review Purchase-to-Pay (MM) steps example in S/4HANA.


Answer: See the following Presentations for a Basic flow of MM Purchase Requisition to Invoice Verification: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review Sales and Distribution (SD) steps example in S/4HANA.


Answer: See the following Presentations for a Basic flow of SD Sales Order to Incoming Payment: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review Production Planning (PP) steps example in S/4HANA.

Answer: Here are 2 Blog Post of using FIORI App to perform PP Planning and PP Execution: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: The FI "New GL" ACDOCA Table and the Classic Tables review.

Answer: The Universal Journal in SAP S/4HANA is a single, unified table (ACDOCA) that consolidates financial and controlling data from both Financial Accounting (FI) and Controlling (CO). It replaces the separate tables used in previous SAP ERP systems, simplifying data integration and reporting while providing a comprehensive view of transactional data. The ACDOCA as a singular table combines four specific components in FICO which are the General Ledger, Material Ledger, Controlling, and Profitability Analysis Data.

Previously was misinformed by some Experts that the ACDOCA table combines 40/50 tables to become one table called the ACDOCA tables but I think maybe is maybe is only a single digit number of 10+tables; however, the new table does contain 500 over fields (the exact number can vary depending on the specific S/4HANA release and customizations). AND the combined new table of ACDOCA does make at least the following tables below Obsolete in S/4HANA. 

The following are obsolete tables including index tables due to the ADOCA table.
BSIS
BSAS
GLT0
BSID
BSAD
KNC1
KNC3
BSIK
BSAK
LFC1
LFC3
FAGLFLEXT
FAGLFLEXA

ACDOCA Advantages:
• Data Model Simplification: ACDOCA consolidates financial data from various SAP modules into a single table, reducing complexity and redundancy compared to the traditional SAP ECC system. ACDOCA, SAP's Universal Journal, is generally considered relatively easy to learn and train for, especially compared to older SAP financial accounting systems. Its simplified structure, single source of truth, and streamlined reporting features make it more user-friendly for both technical and business users.
• Real-Time Reporting: The consolidated data in ACDOCA allows for real-time financial reporting and analysis, enabling faster decision-making.
• Improved Data Accuracy: ACDOCA's centralized data model improves the consistency and accuracy of financial data, leading to more reliable reporting. SAP (in help.sap.com) claims that the Integrity of financial data in ACDOCA is guaranteed by design. 
• Enhanced Reporting Capabilities: ACDOCA provides a foundation for more flexible and detailed reporting, allowing for deeper analysis of financial data.
• Simplified Reporting Process: ACDOCA simplifies the process of creating financial reports and makes it easier to communicate financial information.
• Faster Data Retrieval: The streamlined data structure in ACDOCA facilitates faster data retrieval, allowing for quicker analysis and reporting.
• Improved Organizational Performance: By simplifying data management and improving reporting, ACDOCA can contribute to better organizational performance and decision-making.
• No 999 Line Item Limitation: Unlike the BSEG table, ACDOCA does not have the 999 line item posting restriction, allowing for more detailed and accurate recording of financial transactions. 

ACDOCA Disadvantages:
• Initial Transition: Migrating data from SAP ECC to S/4HANA, including data related to the universal journal (ACDOCA), is generally not easy and requires careful planning and execution. While S/4HANA offers many benefits and simplifies data management compared to ECC, the migration process itself presents several challenges. 
• Potential for Performance Impact: With very large datasets (500+fields in a Single Table), ACDOCA's performance might be affected due to large datasets and complex queries, requiring optimization strategies or careful design choices even on a S/4 HANA Database platform. 
• Complexity for Some Users: Some users may find the initial learning curve of ACDOCA challenging, especially those accustomed to traditional SAP reporting methods. 
• Dependency on SAP S/4HANA: ACDOCA is a feature of SAP S/4HANA, and its functionality is dependent on the SAP S/4HANA system BUT regardless, use of ACDOCA in Mandatory in S/4HANA.  

Conclusion, the advantages of ACDOCA typically outweigh the disadvantages, particularly within the context of SAP S/4HANA. ACDOCA, or the Universal Journal, offers significant improvements in data management, reporting, and overall system performance. 

Link to:
https://www.sap.com/assetdetail/2024/11/GeneralLedgerTOUniversalJoournal/
https://community.sap.com/all-you-need-to-know-about-universal-journal-acdoca-s4hana/
https://www.youtube.com/UniversalJournal(ACDOCA)inS/4HANA FinanceExplained/

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: "My Sales Overview" Analytics App review.


Answer: The "My Sales Overview" SAP Fiori app provides a centralized dashboard or Hub for sales representatives to quickly access and view key sales data. It allows users to see a variety of "Cards" like "Open Sales Quotations", "Open Sales Orders", "Customer Returns", "Blocked Credit Memo", "Incoming Sales Orders", and other sales-related information at a glance. This app enables users to identify areas that need attention to improve sales volume and track the overall sales performance. The SAP Fiori app also allow access to "Sales Order Fulfillment - Analyze and Resolve Issues" that helps the businesses Users address impediments to sales order fulfillment. It provides a central point for identifying, analyzing, and resolving issues that arise during the sales order fulfillment process, ensuring orders can be completed efficiently. 
See link to a Blog Posts to the App: 

See also links to "My Sales Overview" Fiori App official links:
https://drive.google.com/file/mySAPOverviewVideo/

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: SAP Signavio.

Answer: SAP Signavio Process Navigator is a cloud-based tool that provides access to SAP's predefined business process content, including solution scenarios, process flows, and related information.
Benefits of using SAP Signavio Process Navigator:
• Improved Understanding of SAP Processes: Helps users understand the pre-configured processes within SAP systems. 
• Faster Implementation: Facilitates faster and more efficient implementation of SAP solutions. 
Reduced Implementation Costs: Can help reduce implementation costs by providing access to pre-built processes and implementation accelerators. 
• Enhanced Collaboration: Enables teams to collaborate effectively on process design and implementation. 
• Increased Agility: Allows businesses to adapt to changing needs more quickly by leveraging pre-configured processes. 

Key Features and Functionality:
• Access to SAP Solution Scenarios: Offers insights into SAP's pre-built processes, like "Lead to Cash" or "Plan to Fulfill," for various SAP solutions. 
• Process Details: Provides detailed information about solution processes, including process flows, applications, integrations, and solution capabilities. 
• Implementation Accelerators: Offers resources like test scripts, tutorials, and setup instructions to facilitate process implementation. 
• Contextual Information: Displays process-related context data such as roles, integration automation, and applications. 
• Country and Industry Specifics: Includes information tailored to specific countries and industries. 
• Deployment Model Support: Supports various deployment models, including SAP S/4HANA Cloud, on-premise, and hybrid environments. 
• Search and Filtering: Allows users to search and filter processes based on various criteria, such as solution scenarios, applications, and roles. 

See the following link to illustration step navigation in the web link to SAP Signavio:
https://froggysap.blogspot.com/2025/02/sap-best-practice-activation-and-sap.html

See also official SAP links to SAP Signavio: 
https://www.signavio.com/products/process-explorer/
https://www.signavio.com/Gardner/
https://help.sap.com/docs/signavio-process-collaboration-hub/user-guide/login

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

at No comments:
Labels:

SAP SD - Enterprise Structure Configuration

click "here" to view the Presentation

at No comments:
Labels:

Question no 4052 : Quality Management data at the Plant level

In SAP Quality Management, which of the following QM Master data need to be created at the Plant level ?

(more than one answers)

A. Master Inspection Characteristics.
B. Sampling Procedure.
C. Inspection Methods.
D. Sampling Scheme.
E. Inspection Plan.
.

Answer: A, C, E

The following QM Master data are Plant dependent:
. Master Inspection Characteristics
. Inspection Method
. Inspection Plan
. Material Specification


The following QM Master data are not Plant dependent:
. Sampling Procedure
. Sampling Scheme
. Dynamic Modification Rule
. Sample Drawing Procedure

at No comments:
Labels: ,

Saturday, June 7, 2025

SAP PP - Dispatched Repetitive Manufacturing Planned Orders

at No comments:
Labels:

Q&A in Class (2025-06-06) S43400

 Question: What is the "Claim" button in the Inbox for Maintenance Order Approval ?


Answer: The "Claim" button in the SAP Fiori My Inbox app reserves a task for the user who clicks it. Essentially, it allows the user to take ownership of a task, preventing other users from seeing or processing it until it is released. 
Here's a more detailed explanation:
• Reserved Task: When a task is claimed, the user becomes its processor, and the task is marked as "Reserved".
• Private Visibility: Only the user who claimed the task will see it in their My Inbox.
• Multiple Recipient Scenarios: The Claim feature is particularly useful when multiple users are assigned to a task and it's important to avoid overlapping work.
• Releasing the Task: After claiming a task, the user can later release it, making it visible to other recipients again. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Is there an equivalent FIORI App for Report "S_ALR_87013015" or best Excel Download feature for this Report ?


Answer: Although not too sure if there is an equivalent FIORI.App for this but the SAP CO t-code "S_ALR_87013015" Report allows to Activate Output Type to "Excel".
Goto the section 4 of the Blog Posts to see How to Integrate to Excel from the Report:
https://froggysap.blogspot.com/2025/06/sap-pm-finding-balances-in-maintenance.html

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Phase-based Maintenance scenario step-by-step review.


Answer: Phase-based maintenance is a structured approach to managing maintenance activities, dividing the process into distinct phases to improve organization, tracking, and overall efficiency. This method is often used with systems like SAP S/4HANA to streamline maintenance workflows.

Here's a breakdown of how phase-based maintenance works:
Phases in Phase-Based Maintenance:
• 1. Initiation: The process begins with the generation of a maintenance request or order, often triggered by a fault, failure, or scheduled maintenance task. 
• 2. Screening: A designated individual or team reviews the maintenance request to determine its validity and urgency. 
• 3. Planning: Detailed planning, including resource allocation, material requirements, and execution • strategy, takes place. 
• 4. Approval: Necessary approvals are obtained before the maintenance order can proceed to the next phase. 
• 5. Preparation: This phase involves preparing the necessary resources, tools, and materials for the maintenance task. 
• 7. Scheduling: The maintenance task is scheduled, taking into account availability of resources, time constraints, and other factors. 
• 8. Execution: The maintenance work is performed by the assigned personnel. 
• 9. Post-Execution: Once the work is completed, post-execution activities such as confirmation of work performed, recording of failure data, and updating the system with relevant information are carried out. 
• 10. Completion: The maintenance order is officially closed after all necessary steps have been completed. 
 
See the following Blog Post on the steps of Phased-baesd Maintenance Scenario:  
https://froggysap.blogspot.com/2025/06/plant-maintenance-maintenance-request.html

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Inspection Checklist scenario step-by-step review.


Answer: In SAP, an inspection checklist is a structured form used to document inspections during maintenance operations. It helps ensure that all necessary checks are performed, and results are recorded accurately. This process, which is part of SAP's Plant Maintenance module (PM), is automated within SAP S/4HANA to generate checklists based on defined criteria and master data. 
Example applications:
•  A maintenance order for a machine might trigger an inspection checklist to verify its condition, including checking for wear and tear, lubrication levels, and operational performance.
•  An inspection checklist could be used for a building's electrical system to ensure compliance with safety standards and identify potential issues. 

Here's a breakdown of how inspection checklist works:
Steps in Inspection-Checklist Maintenance:
•  1. Trigger: A maintenance order triggers the process, creating a list of technical objects for inspection.
•  2. Automatic Checklist Generation: Based on the order, the system automatically generates inspection checklists for the identified objects.
•  3. Inspection and Recording: Inspection characteristics are defined and results are recorded in the checklist.
•  4. Usage Decision: Based on the results and defined tolerances, a usage decision (e.g., equipment usable, needs repair) is made.
•  5. Follow-up Actions: Depending on the usage decision, subsequent actions like repairs or maintenance can be initiated.
 
See the following Blog Post on the steps of Inspection Checklist Scenario:
https://docs.google.com/presentation/Inspection-Checklist/

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Is there a t-code steps recording tool to generate documentation of screens ? 



Answer: SAP Enable Now offers a suite of tools to support various aspects of learning and knowledge management, including creating and delivering learning content, managing user access, and providing in-application support. Key tools include Manager (LMS capabilities), Producer (extended authoring), Instant Producer (recording tool), and SAP Companion (in-system assistance). 

SAP Enable Now was previously known as SAP Workforce Performance Builder. The latest release is 2406, which was released in June 2024. SAP is also preparing for the 2311 release in November 2023. The 2406 release includes new features like AI-powered text editing in the web editor, web-based camera recording, and support for the SCIM API. 

Here's a more detailed breakdown of the tools and features:
Content Creation and Management:
• Producer: This tool allows for web-based content creation, course design, and editing, enabling the creation of various learning materials. 
• Instant Producer: A user-friendly tool for recording system processes, which can be used to create videos, simulations, and other learning assets. 
• Learning Centre: A repository for storing and accessing learning content, including processes, tutorials, documents, simulations, and videos. 
User Assistance and Support:
• SAP Companion: Provides assistance within the live SAP system, helping users navigate and understand processes. 
• SAP Desktop Assistant: Offers a toolbar with access to onscreen help, LMS content, and contacts. 
• SAP Enable Now Web Assistant: Provides in-application support, including guided tours and context-sensitive help. 
Additional Features: 
• Workflow Feature: Facilitates collaboration and tracking of training document progress.
Integration with SAP Signavio: Enables synchronized access to critical content.
• Text-to-speech: Converts text into audio for accessibility.
Media Management: Supports various media formats, including videos and audio. 

Here to links to resources on SAP Enable Now:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
at No comments:
Labels:
Subscribe to: Posts (Atom)