Saturday, January 4, 2025
_0406&07_aATP&BOP_Blogged.jpg)
Friday, January 3, 2025
Q&A in Class (2025-01-03) S4SD1
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: a Concise view of the Table Structure and Relationship for SD in S/4HANA as at S/4HANA2023
The link below are slides to the SD tables relationships and tables changes in S/4HAN2023
https://froggysap.blogspot.com/2025/01/sap-sd-sd-tables-relationships-and.html
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of "Space and Pages" in SAP FIORI 2023 (as at January 02.2025 testing)
_0102_Space_Blogged.jpg)
"Spaces and Pages" is the new Layout Design of Fiori Launchpad which is available from S4H4HANA 2020 or maybe 2021 (if remember correctly) and onward on both cloud and on Premise environment. When creating new User and access the FIORI Web environment, the "Spaces and Pages" is now a Standard Default of the the currently login on January 2.2025. Do note that the previous "Group Tile" Layout is still available when the User switch off the "Spaces and Pages" in the User Settings.
Clink the link below to demo slides on Space and Pages
https://froggysap.blogspot.com/2024/12/sap-navigation-new-user-roles-space.html
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
S/4HANA Amount field lengths AFLE)
In ECC, while posting any journal entry or any entry posted through any other modules eg. Logistics, Sales etc. there was a limitation of 13 digits i.e. 11 digits and 2 decimals (13,2). Therefore maximum possible amount which could be posted was 999,999,999,99.99.
One of the key changes in SAP S/4 HANA, on-premise edition 1809 and higher releases is that Amount Field Length Extension which is AFLE. This was release for S/4HANA.
ALFE on or after 1809, it has been extended to 23 digits (including 2 decimals). Therefore maximum possible amount which could be posted was 999,999,999,999,999,999,999.99.
The ALFE or Amount Field Length Extension is not activated in customizing by default. But once activated, it no longer can be deactivated.
_AFLE.jpg)
_AFLE%20(1).jpg)
_AFLE%20(2).jpg)
_AFLE%20(3).jpg)
Before implementing AFLE, you should read the following SAP Notes:
- SAP Notes 2628654 (link to OSS notes) depending user accessibility
- SAP Notes 2628040 (link to OSS notes) depending user accessibility
Also see the following link:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review aATP functionality "Advanced BOP"
SAP introduced Advanced Backorder Processing (BOP) ((CA-ATP-BOP)) as part of the advanced Available-to-Promise (aATP) functionally in September 2022. BOP is a feature that allows users to adjust ATP quantities and dates based on changing inventory positions.
Advanced Available-to-Promise (aATP) "Advanced Backorder Processing" (Adv. BOP) is a process that involves batch processing orders to accommodate business priorities and changes in demand and supply. Instead of the classic Order by Order Backorder Processing in ECC via transaction codes like (CO06, V_V2, and V_R2); the S/4 "Adv. BOP" uses ONLY FIORI Apps to setup something called "BOP Segment" and the "BOP Variant" with strategies like "WIN", "GAIN", "LOSS" which then runs selected Sales Order in a Batch Processing Model to perform the "Strategy based BOP". One of the popular criteria is the "Priority of the Customer" as a basis for the Advanced BOP but other criteria can also be deployed via the "BOP Segment and BOP Variant".
3 Configurations required:
- S/4 Backend SPRO via t-code OVZ2 to activate aATP for Availability Check Group
- BOP Segment (App ID F2158)
- BOP Variant (App ID F2160)
_04_BOP2_Blogged.jpg)
Click for step by step Adv.BOP example in the following link:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of S/4HANA Credit Management process and Structural relationship of Main Credit Segment and Sub Credit Segment Level.
_0410_S_4CreditMgmtOverview_Blogged.jpg)
SAP Credit Management (FIN-FSCM-CR) in SAP S/4HANA was introduced in ECC as an alternative to the Classic Credit Management (FI-AR-CR, SD-BF-CM) in SAP ECC. BUT there is some news that the new FIN_FSCM-CR Credit Management will replace the Classic Credit Management in the S/4HANA system (this has to be reconfirm).
The new FIN-FSCM-CR Credit Management Solution offers:
- Setup of credit limit via a standard BP Role "UKM-000" at the Credit Segment level.
- Credit Segment is a new "Org Unit" which is still assigned to the Classic Credit Control Area.
As far as Main Credit Segment and Sub-level Credit Segment is concerned:
- It is possible to set-up Credit Segments as Main or Sub-level when defining them.
- When defining Sub-level Credit Segments, user can select an indicate to cumulate the credit limit at the Sub-level to the Main Credit Segment level.
- The relationship between the Main and Sub-level Credit Segments is done via maintain relationships between sub-segments and main segments in Transaction Code “BP” and open the “Relationships” tab (according to recent review of SAP documentation, but this certainly has to be simulated first). ((ie when the main credit segment is is used along with sub-segments; the sub-levels of credit segment can be flagged to "Add contribution to main segment". This means that the liabilities of the sub-segments are collected at the main segment level.))
For Main Credit Segment and Sub-Level Credit Segment, the following OSS Notes could be useful (but I will have to investigate "how to"):
KBA 2706299 - Parent-child relationship of business partners for credit check in SAP Credit Management (FSCM)
Answer: see link below:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review Condition Contract Management Order creation and Settlement process.
_0413_(14)ConditionContract_Blogged.jpg)
Condition Contract Management provides a Central, Standardized solution for the administration of supplier and customer Rebates. The ECC classic Rebate processes for MM and SD is not obsolete in S/4HANA system.
Answer: see link below:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of Advanced Return Management for SD with internal Inspection via ARM.
_0415_CustomerReturn_Blogged.jpg)
SAP released Advanced Returns Management (SAP ARM) to integrate and manage the entire returns process (if not mistaken, it can be used in ECC EhP8). BUT from S/4 HANA 1709 with Embedded EWM, for Customer return process, SAP has introduced for all customer return process has to be mapped through "Advanced Return Management( ARM)". ARM is an extremely powerful tool for all reverse logistics to capture nearly all the complex return process with a complete document flow within existing SD and PO.
SAP Advanced Returns Management (ARM) is a component of SAP ERP and SAP S/4HANA that manages the entire process of customer and supplier returns. For SD application, it involves the creation of the customer returns order. recording material inspection results, and deciding the logistical follow-up activity.
Answer: see link below:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review an example scenario of "Preliminary Billing".
_0517_PreliminaryBilling(ServicesLeanSale)_Blogged%20(1).jpg)
"Preliminary Billing", sometimes also referred as "Pre-Billing" (or "intermediary document for Billing"), is a business practice where the customer is invoiced for goods or services before they are fully delivered or completed (in SAP it can be used for either "Order-based Billing" or "Delivery-based Billing). The feature is often used in industries where there are significant upfront costs or when products or services are delivered over a long period of time AND the agreed price in the Sales Order is the "Best initial Agreed Estimate" BUT the "Preliminary Billing Document" is used as the final price with the customer before the "Final Billing" is generated to the Customer.
see below for a demonstration example:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question : Review of the new "Flexi-Workflow".
_04_Team&WorkFlow(CreditMemo)1_.jpg)
The flexible workflow is a new workflow framework available in SAP S/4HANA in all versions of the system: on-premise, private cloud, public cloud. It enables easy execution of decision-making processes in different areas of the system (for both MM and SD). The setup for flexi workflow is done in general using 2 FIORI Apps for Credit Memo Workflow:
- "Teams and Responsibilities" App ID F2412
- "Manage Credit Memo Request Workflow" App ID F3014
The advantages of S/4HANA Flexi-workflow are:
- Can be used as a cloud edition or on-premise.
- Notifications to users via Fiori "My Inbox" in Mobile Devices.
- Notifications process to recipient's are seamless and instant.
- The Workflow can have multiple start conditions and a variety of options for determining approvers.
- The Workflow can define workflows for approval processes based on conditions.
- The Workflow can have validity period.
- The Workflow can be activated or deactivated easily.
Answer: see link below:
https://docs.google.com/presentation/d/1oJJdt57Wg6GkmQOjRUx4JwZTR6nxJF4gaM7vgO8ga3w/edit?usp=sharing
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of the "Track Sales Order" FIORI App.
_0621_TrackSalesOrder_Blogged.jpg)
Track Sales Order for ECC and S/4HANA:
- "Track Sales Order (ERP)" App ID F0020 (introduced in 2013 for ECC)
- "Track Sales Orders (S/4HANA)" App ID F2577 (introduced in 1709 for S/4HANA)
The "Track Sales Order" FIORI App is a useful App to show Fulfillment issues of list of Sales Orders. With this app, the user can check whether selected sales order's fulfillments are on track. The user can then immediately recognize whether a sales order contains any issues, if it is complete, or still in process. Not just sales but also delivery, or invoiced issues or whether the corresponding journal entry in accounting has been created (cleared).
see an example of a demo and online help of the "Track Sales Order" FIORI App:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: an Overview of the "Customer - 360° View" FIORI App.
"Customer - 360° View" Fiori App ID F2187.
Customer 360 is the concept of having a unified view of all the customer data across all touchpoints encompassing a holistic 360 degree view of your customers including all interactions across various channels like:
- Sales area for the Customer BP
- Open Quotations
- Sales Orders
- Sales Contracts
- Customer Return
- Credit Memo Request
- Debit Memo Request
- Sales Scheduling Agreement
- Service Orders
- Service Quotations
- Fulfillment issues
- etc. depending of the Version
See link below for the demonstration:
https://docs.google.com/presentation/d/14th5NiueEjNCAdvagnJQYnpuzjtN22Um9TTXY8fVLfI/edit?usp=sharing
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is an example of "Smart Business KPI"?
_0620_SmartBusinessEVAL_Blogged.jpg)
The SAP Smart Business KPI Fiori app is a tool (Modeling App) that allows users to monitor and manage key performance indicators (KPIs) and operating performance indicators (OPIs) in real time:
App ID F2814 "Manage KPIs and Reports" was released in 2019: The App is a single platform for creating all analytical applications using KPIs, reports, and stories. The user can create KPI Anlalytical FIORI Apps that can be launched directly from SAP Fiori launchpad or "Space and Pages". Some of the features in the KPI App creation are metrics configuration in the KPI, data visualization either in chart or table format, etc.
_0723_PredictiveDelay_.jpg)
SAP Intelligent Technologies facilitate the following:
see below link for an overview of the "Smart Business KPI" FIORI App is created using OData Source:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: SAP and "Intelligence" directions:
_0723_PredictiveDelay_.jpg)
SAP Intelligent Technologies facilitate the following:
- SAP IoT and Edge (formerly SAP Leonardo IoT) offers a guided approach to digital transformation that combines intelligent technologies and services.
- Technologies such as artificial intelligence, machine learning, Big Data, IoT, Analytics, and blockchain across the Suite to drive ongoing innovation.
In Analytics, "SAP Intelligence Analytics" is a collection of data management and analytics tools that help businesses make better decisions by using data to gain insights. One of the initiatives is the the SAP Predictive Analytics Library (PAL) and the Automated Predictive Library (APL) that offer a range of algorithms for predictive modeling. The SAP Business Technology Platform (BTP) also integrates machine learning services, making it easier to build and deploy models. Several FIORI Apps have been released (pending more simulation and testing) based on these initiatives and in SD are:
_0723_PredictiveDelay_%20(3).jpg)
In order to perform "Predictive Calculations" results for any of the Apps above, the pre-requisite are "Predative Scenarios" that uses:
- Classification
- Regression (the above SAP predictive Apps uses this method)
- Time Series
The above are NOT "Advanced Mathematics or Statistics" comparing to the use of "Genetic Algorithms (GA)" that is used in SAP PPDS or "Mixed Integer Linear Programming (MLP)" used in SAP SNP.
However, the "Predictive Scenario" FIORI App is required to create "Scenario Model" which using historical data and Mathematics (eg: Regression) to perform "Machine Learning" and applying the "Learning Results" through specific periods before there can be used to perform Predictions eg: the Prediction of Outbound Deliveries. (when these "Predictive Scenario" Apps can be accessible in the near future then further simulations can be done to see if there "really work").
See link below for a brief aspect of the "Intelligence Analytics" initiative:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Subscribe to:
Posts (Atom)