A basic explanation of the Evolution of SAP Platform from Basis, NetWeaver to SAP BTP

 

CLICK here to view the Presentation

SAP MM - Supplier Evaluation Scores, Q&A and Purchasing Category (S/4)

CLICK here to view the Presentation

SAP TM - Calculate Transportation Charges Integrations

 

ICK here to view the Presentation

SAP PM - AV Check at CRTD status when a Reservation is created in the Maintenance Order

CLICK here to view Presentation

SAP Best Practices Activation and SAP Signavio Process Navigator

CLICK here to view the Presentation

Question no 4033 : PDS Transfer via CURTOADV_CREATE

In SAP Advanced Planning S/4 1909, which of the following are TRUE for PDS Transfer via CURTOADV_CREATE ?

(more than one answers)

A. A Production Version must be created for the Materials concerned.
B. The Production Version must have a valid Routing and a valid BOM.
C. The Production Version can be with a valid BOM and without Routing.
D. The Assembly must have an Advanced Planning view but MRP views are not necessary in the Material Master.
E. Only Target Version "000" Active Version can be transferred.
.

Answer: A, C

A) If a valid BOM with its components were to be transferred to Advanced Planning, not just just assembly but the components must have been activated for Advanced Planning before executing CURTOADV_CREATE.
B, C) As at 1909, A Production Version must exist but only a BOM is necessary and Routing is not mandatory for a successful PDS Transfer.
D) When activating a Material for Advanced Planning, MRP view becomes Mandatory.
E) Target Version other than "000" can be transferred.

SAP SD - Outbound Delivery More Functions 7 - Controllable Error Messages

CLICK here to view the Presentation

Q&A in Class (2025-01-24) S4520

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

Question: Review of 2-step Plant to Plant transfer (S4510). 

Stock Transfers between Plants within the same company:

1-step transfer uses Movement type "301"

2-step transfer uses Movement type "303" then "305". 

The results of step 1 in a 2-step transfer via "303" is:

• Accounting document posted in Step 1 (Credit Stock account in Supply Plant AND Debit Stock accounting Receiving Plant).
• The Transit Stock type is a the Plant level of the Receiving Plant.

Answer: See Blog Post link below

https://froggysap.blogspot.com/2016/09/material-management-one-or-two-steps.html

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/StockTransferBetweenPlants/

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

Question: Review of UNBW Material Type and Processing (S4510). 

Materials created with "UNBW" Material Type is characterized as Materials "With Quantity Update" but "Without Value Updating" and it is also called scenario for "Non-Valuated Materials". Purchase Order for such Materials will required Account Assignment as Goods Receipt will have to "Expense-off" (Debit Expenses G/L Account) BUT due to "With Quantity Update", the Stock Quantity will be registered in the Warehouse with Quantity but without Stock Values. This means that such Materials will be tracked with Quantity in the Warehouse and subsequent Goods Issue or Adjustments of these Materials will not have any impact to the Balance Sheet. 

Answer: See Blog Post link below

https://froggysap.blogspot.com/2014/05/material-type-unbw-non-valuted-material.html

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

Question: Review the SAP steps for Manual PI Doc creation with Posting Block processing (S4510). 

The Physical Inventory Processes is different for the 3 choices of stock management system in SAP:

1. MM-IM Physical Inventory
2. LE-WM Warehouse Management
3. EWM Extended Warehouse Management

Within MM-IM Physical Inventory, there are 3 options:

• Classic Physical Inventory - is a business process in which physical stock is to be matched with book (system) stock. It is legal requirement to carry out physical inventory at least once in a year (the accounting year).  Physical inventory can be carried out both for a company’s own stock (Unrestricted, Quality, Blocked Stock) and for special stocks (Customer Consignment stock, Vendor consignment stock from vendor, Returnable packaging). 
• Cycle Counting - is a method of physical inventory whereby inventory is counted at regular intervals within a fiscal year. These intervals depend on the cycle counting indicator set for the material. Cycle Counting allows you to count fast-moving items more frequently than slow-moving items, for example.
• Sampling Procedure - involves randomly selecting a sample of stock management units for counting. The sample size depends on the desired level of confidence for the count results.

The MM-IM Physical Inventory process step basically are:

1. Create the Physical Inventory Document (manual or batch input).
2. Print the PI Docs to prepare for the Physical Inventory exercise. 
3. Set Posting Block or Freeze Inventory before the Count process.
4. Enter the Count Results. 
5. Check the Difference Report to determine if Re-Count is required. 
6. Post the Difference Report to adjust the Qty and Post the necessary FICO documents for the adjustment. 

Answer: see the following link to the steps in SAP and SAP documentation:

https://froggysap.blogspot.com/2019/08/material-management-physical-inventory.html

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/PhysicalInventory/

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

Question: Review of Invoicing Plan process (S4520).

"Invoicing Plan" is part of the Consumable Scenario with Account Assignment Mandatory using Consumable Purchase Order with Document type "FO" (Framework Order), without Goods Receipts but with Automatic Invoicing Plan Settlement for Schedule Payments. The "Invoicing Plan Type" assign to the PO item will determine if it is a Periodic Invoicing Plan (fixed amount and regular intervals) or Partial Invoicing Plan (irregular amount and manually decided payment dates). Transaction code MRIS is used to setup background job to generate SAP invoice to Accounts Payable when the scheduled payment dates in the Invoicing Plan are due.

Answer: see the following link to process steps and SAP help:
https://froggysap.blogspot.com/2016/04/mm-purchasing-invoicing-plan-periodic.html

https://froggysap.blogspot.com/2024/05/sap-mm-purchasing-doc-type-fo-with.html

https://help.sap.com/docs/SAP_ERP/InvoicingPlan/

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

Question: Review the Subcontracting Process flow (S4510).

SAP Subcontracting involves transferring components to a vendor (subcontractor) to manufacture an assembly. The vendor use the components to assembly the assembly product and returns the completed assembly, and during goods receipt GR, the components are issued from subcontract inventory.

Answer: see the following link to process steps and SAP help:
https://froggysap.blogspot.com/2024/09/sap-mm-special-stock-o-subcontracting.html

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/Subcontracting/

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

Question: Review on MPN Materials (S4520).

SAP MPN materials are materials that have a Manufacturer Part Number (MPN) in the SAP system, it is linked to an "Internal SAP Material". The "Internal SAP Material" is used in the company for Inventory Management (stocks), Bills of Materials and ALL other internal processing of the Material. MPN material numbers can usually recognized by the vendor as it is often the Vendor system's material number to be mapped in our system. Therefore when using MPN material in the Purchase Order for the vendor, it is easily recognized by the Vendor. Via the MPN Profile in the Internal Material, 1 or more MPN material number can be created using Material Type "HERS" for each vendor. The MPN Profile can also be configured to determine if MPN material is allowed in Purchasing Info Record, whether AMPL (Approved Manufacturer Parts List) is mandatory etc. 

Answer: see link below on setup and process steps for MPN Materials:

https://froggysap.blogspot.com/2016/04/material-management-purchasing.html

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/MPN/

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/MPN_functions/

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

Question no 4032 : Time-dependent Conditions in Materials Management

In SAP Material Management, Time-dependent Condition Records can be found in which of the following ? 

(more than one answers)

A. Purchase Requisitions.

B. Purchasing Info Records.

C. Quotation.

D. Purchase Order.

E. Scheduling Agreements.

.

Answer: B, C, D, E

A) PR does not have Condition Records, there is an "Estimated Price" that defaults from the Material Master Accounting data view or Manually entered and it is for Release Strategy Activation.

B, C, E) Info Records, Condition Records and Outline Agreements (Contract and Scheduling Agreements) all are with Time-dependent Conditions.

D) The Prices or Conditions in a Purchase Order are for a specific date.

SAP QM - Inspection Type "01" Multiple Specifications

CLICK here to view the Presentation

SAP MM - MMCC Mass Copy Control Changes & Overwrites

CLICK here to view Presentation

SAP Distributed EWM - Setup for Quality Inspection

CLICK here to view Presentation

Q&A in Class (2025-01-17) S4H00

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

Question: Review a Concise History of SAP.

Source: https://community.sap.com/ (Hasso Plattner, Klaus Tschira, Claus Wellenreuther, Dietmar Hopp and Hans-Werner Hector).   

SAP = "System, Applications, and Products in Data Processing". 

The Germany-based Company was founded in 1972 with the purpose to provide a standard software solution for managing business processes in real time. The company's mission was and still is to help businesses around the world to work more efficiently and use business insights more effectively.

Answer: A Brief History or Milestone of the SAP software company:

• 1972 to 1980s - Five former IBM engineers started SAP in April 1, 1972 in Mannheim, Germany. In 1973, founders released SAP R/1, which was an integrated financial accounting system (FI). This software was revolutionary for its time, allowing companies to process data in real-time and share information across departments. 
• 1980s - ABAP or Advanced Business Application Programming which is the proprietary language of programming for the SAP system until today was released in this period and also where SAP release SAP R/2. In R/2, SAP expanded its capabilities to support manufacturing (PP), sales, and distribution processes (SD). The foundation of the SAP system that includes FI, MM, PP, SD as an integrated system between Accounting and Logistics became the initial backbone of the SAP software system. At this time, SAP is still running only on Mainframe-based system. 
• 1990s - The era where Client-Server Architecture flourished is also where SAP introduced its R/3 System in 1992. The R/3 (or Release 3) provided a "more flexible and user-friendly interface", allowing further integration of Financials and Cost Accounting (FICO) with Logistics (MM, PP, SD), and Human Resources (HR). It is also a time where supporting modules like Warehousing (WM), Plant Maintenance (PM), Quality Management (QM) etc was introduced as SAP takes the lead from MRPII system to ERP system (Enterprise Resource Planning). So far, SAP is still a "ONE Software" company from R/1 to R/3. 
• 2000s - The internet bloom sees SAP introduced "MORE software" for Advanced Solution option as well as Connecting to other Software.  In 2004, SAP introduced ECC 5.0 (Enterprise Centric Component) that replaced R/3 where the "Backend Software of FICO, MM, PP, SD, WM, PM, QM, etc) will be integrated to the "NEW software" solutions where some of them can also be sold separately. These "NEW Software" solutions include SRM (Supplier Relationship Management), APO (Advanced Planner & Optimizer), CRM (Customer Relationship Management), SEM (Strategic Enterprise Management) etc. AND in 2006, SAP released ECC6.0 which became the SAP Backend Solution until 2015 and even today. It is important to note that it is in the early 2000 that SAP introduced Life-Cache Technology (LCT) which is the SAP proprietary memory-resident object management technology that enables higher levels of performance in business processing and initial intention is for the APO (Advanced Planner and Optimizer) Solution (or Advanced PP that is to use Optimization Engines for Planning and Scheduling). 
• 2010s - This is the era where software companies began the shift to "Cloud Computing". The more than 10 years of Life-Cache Technology (LCT) experience consolidated into SAP HANA which was released in 2012. (HANA = Hyper Performance Analytical Application) is and improved in-memory database platform that allows for real-time advanced analytics and higher speed transactions in a software system. AND in February 2015, SAP released S/4HANA (interestingly instead of R/4HANA), and the "S" of S/4 is consistently being referred as abbreviated letter of the word "Simplification". SAP S/4HANA can be scaled UP or scaled OUT (all the way to 48TB as of today by using multiple servers in a cluster, or by using cloud storage. AND because such advanced storage capabilities, SAP then included some of the Advanced Solutions Embedded into the single S/4HANA instance which include part of the APO system called Production Planning and Detailed Scheduling (PPDS), Extended Warehouse Management (EWM), or Transportation Management (TM). AND not just that, Industry solutions like IS-Automotive etc have also becoming Embedded into the S/4HANA system. The "sudden" rapid shift from Traditional IT management to Cloud Computing (which originally dates back to the 1940s and 50s) is now no longer a "Technology gimmick" but achieved mainstream adoption to organizations world wide since the early 2010s. So, besides the S/4HANA solution, SAP embark on its next journey to create Cloud Solution like the "Integrated Business Planning" (IBP) which is a Cloud solution for Demand Planning and Forecasting (previously the Demand Planning (DP) component of the APO system) which was release in mid 2014. 
• 2020s - The increased use of smartphones in the workplace has prompted SAP to further introduce Fiori with "User Experience (UX)" capabilities. BUT this is the ear where SAP is leading the charge for "Industry 4.0" in helping organizations to leverage the latest technologies to transform into Intelligent Enterprises. One of the next focal point of software direction is to use "Cloud Computing", "Artificial Intelligence (AI) and "Machine Learning (ML) to create Solutions that perform Predictive Analytics and "Generative AI Co-Pilot" that will revolutionizes how users interact with the SAP business systems etc.

The future of SAP will be an ever more "Connected" systems and a "Smarter" system that help businesses work faster and more efficiently. This can be send by SAP's focus on Cloud-based solutions and AI-driven technologies to more towards that vision. 

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

Question: What are the official web resources on SAP. 

https://store.sap.com/dcp/en/news-blogs/announcements

Answer: Official SAP references:

https://www.sap.com/sea/about/company/history.html

https://news.sap.com/

https://www.sap.com/topics/

https://www.linkedin.com/showcase/sap-news/

https://learning.sap.com/

https://help.sap.com/docs/

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

Question: A basic illustration of the SAP User Interface screens in SAP for 50 over years since 1972: 

The history of SAP's user interface (UI) Milestones worth mentioning are the following:

• 2000s - onwards : Graphical user interfaces (GUIs) with colors and push buttons
• 2015s - onwards : Evolution of the SAPUI5 framework into FIORI Apps

Answer: Some blog posts related to SAP Fiori Apps:
https://froggysap.blogspot.com/2022/04/s4-discover-fiori-applications.html

https://froggysap.blogspot.com/2022/04/s4-fiori-some-settings.html

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

Question: The following is a depiction of the Enterprise Structure used to support the Standard Material Management Process.

CO, FI, MM, LO are module names in SAP:

Finance

• CO is Controlling module (Basically for Cost or Management Accounting processes)
• FI is Financials module (Basically for Financials Transactions and Reporting)

Logistics (LO is Logistics module) which contains many other "sub" modules

• MM is Material Management module (for managing processes of purchasing for stock and services etc, plus stock management and capture supplier invoices for goods delivered to us)
• PP is Production Planning module (for planning and production of sub assembly and final assembly to be sold to the customers)
• SD is Sales & Distribution module (for captures customer orders in both products and services to be sold, then work with LE (Logistics Execution module) for delivery of the products to the customer and finally created Billing Document for the Customers. 

Human Resource

• HR is Human Resource module (for 

Enterprise Structure relevant to support the MM Process:

• Controlling Area - In SAP, a controlling area is an organizational unit that is used for cost accounting and managing costs and profits. In the academic representation, it can be called Cost Accounting or Management Accounting which is for Internal Accounting. The Controlling Area is the Enterprise Structure in the SAP Controlling module (CO module).  
• Company Code - Since CO is for Internal Accounting, the Financials module (FI module) is for External Accounting. The components of the FI modules contains but not limited to the following of General Ledger (GL), Accounts Payable (AP), and Accounts Receivables (AR). While AP is to track all Invoices to-be-paid to the Supplier, AR is to track all billing documents to customer and managed the payment from the Customers. 
• Purchasing Organization - In SAP, a Purchasing Organization is an Enterprise Structure that handles a company's purchasing transaction processing. It's responsible for procuring of materials and services, and negotiating purchase conditions with supplier (or vendors). 
• Plant - In SAP, a Plant is a branch or operating area within a company. It's a logistics-based Enterprise Structure that's used to manage procurement, production, warehouse, maintenance, and materials planning. In this case, a Plant can be a Ship, a Warehouse, a Port, a Service Center, a Production Facility etc. 
• Storage Location - In SAP, a Storage Location is a physical location within a plant where stock or inventories are kept.

Answer: See the following links to SAP screens for the introduction to the MM Enterprise Structure:

(1) Controlling Area

(2) Company Code

(3) Purchasing Organization

(4) Plant

(5) Storage Location

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

Question: Review of the Material Management (MM) basic steps. 

Answer: See the following links to SAP screens for the introduction to the MM Basic Process from Master Data to an example MM Process:

(1) Create Material Master

(2) Create Vendor Master

(3) Create Purchase Order

(4) Create Goods Receipt

(5) Create Logistics Invoice Verification

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

SAP MM - Advanced Return STO issues (Missing Output Types LD00 and SPED)

 

CLICK here to view the Presentation

Question no 4031 : Maintenance Status for Stock Procurement Scenario

In SAP Material Management, which of the following Minimum Maintenance Status a "Valuated" Material Master must have in order for execution of Procurement to Stock scenario ?

(more than one answers)

A. Basic Data ("K")
B. Purchasing ("E")
C. MRP ("D")
D. Accounting ("B")
E. Costing ("G")
.

Answer: B, D

SAP QM - "Manage Defects" App ID F2649 Overview

 

CLICK here to view the Presentation

SAP PM - Maintenance Planning Overview FIORI App (Overdue Orders and Orders for Completion CARDS)

CLICK here to view Presentation

SAP SD - Outbound Delivery More Functions 6 - Delivery Split by Warehouse

 

CLICK here to view the Presentation

Q&A in Class (2025-01-10) S4PR1

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

Question: BP creation using FIORI UX App.

Answer: See the following BP creation step using FIORI App:

https://froggysap.blogspot.com/2018/12/business-partner-vendor-fiori-app.html

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/GuidelinesforConvertingBusinessPartner/

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

Question: We have customized report that pull Vendor Data (ECC) from Standard Table (LF* or LM*).  Using BP Vendor Creation (S4 Hana), is this vendor info will be flow to Standard Table (LF* or LM*) also or need to use different Table (for BP Vendor creation).

In S4, the LFA1 table still exists and it is not being replaced to BUT000. 

All LFA1 data is in BUT000 and it can be considered that LFA1 is a subset of BUT000. 

BUT000 contain more data which are S/4 relevant data. 

Answer: See the following Blog Posts that include both Process flow and MM Tables
https://froggysap.blogspot.com/2023/03/S4MMProcess&Table.html

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

Question: Review the S/4 "Self-Service Procurement Scenario".

In SAP S/4HANA, "Self-Service Procurement" is a streamlined process that allows employees to request goods (consumables) and services directly. The process is similar to shopping in the B2C on-line shipping and is designed empower the user to make request and perform confirm of goods receipt via simplified FIORI Apps. 

Answer: See the following Blog Posts and online help for the Self-Service Procurement Scenario introduced in S/4HANA:
https://froggysap.blogspot.com/2025/01/mm-pur-employee-self-service-with-lean.html

https://help.sap.com/docs/SelfServiceProcurementScenario/

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

Question: Review the S/4 "LEAN Service Procurement Scenario".

Lean services is newly introduced process in SAP S/4HANA to simplify service procurement. For this scenario: 

• SAP introduced Product Type Group "2" in the Material Type "SERV" that can be used to create a LEAN Service Material Master (instead of using the Service Master via AC03). 
• Instead of using Service Condition, the Purchasing Info Record can be use for the LEAN Service Material. 
• MIGO and ML81N is not relevant AND SAP introduce a FIORI App for the Service Entry of LEAN Service PO, but it still will create a SES (Service Entry Sheet) similar to the Service Master scenario. 
• The Result the Approval of the LEAN Service will create Material Document with FICO postings. 
• Invoice entry is the same for the LEAN Service PO (via MIRO). 

Answer: See below Blog Posts for step by step:
https://froggysap.blogspot.com/2024/11/sap-mm-material-type-serv-lean-service.html

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

Exercise for Stock and Lean Service Scenario (use the following Data Set)

Answer: We shall use the above data to run through the FIORI Apps for Stocks and Service Entry Scenarios via the FIORI Apps suggested in the Steps. 

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

Question: The workings of "Classification and Segmentation" feature in FIORI App

I was able to access the FIORI App for "Classification and Segmentation" as per the screen shot above in the previous Login to SAP via an FIORI App called "Display Supplier Procurement" (App ID F3371) see link below. (However, need to do testing again to see if this App will still allow access to the Score Card screen for the supplier). 

Answer: Basically the "Classification and Segmentation" is a FIORI screen that allows the User to Enter the Score Card for the Supplier in relation to Supplier Risk, Labor Policy, Social Responsibility, and Environmental Responsibility. At present, there are no documentation that states the Overall Score is interactable to Supplier Evaluation as a Main and Sub-Criterion Score. 

When there is an opportunity to access the FIORI app for "Classification and Segmentation" will definitely create another Blog Posts to show case the Supplier Score Card capabilities. 

See the following link: 
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F3371')/S29PCE

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

Question: What is the difference between Flexi workflow vs the Classic Release Strategy ?

Answer: The flexible workflow allows SAP user to define approval processes for documents in Sourcing and Procurement introduced in SAP S/4HANA as a set of enhancements for the SAP Business Workflow. By using the flexible workflow, you can simplify your configuration as compared to the Classic Release Strategy (as at S/4HANA2023, the Classic Release Strategy is still available and no news of any intention to remove the functionality). 

The activation of flexible workflow (or Flexi-Workflow) is at the Purchasing Document type. Hence, any Purchasing Document Type not activated for Flexi-Worfklow can continue to use the Classic Release Strategy. In this case, customer can use both approval methods depending on Purchasing Document Types. 

Features of Flexi-Workflow includes but not limited to the following:

• Configure Start Conditions and Activation criteria
• Email notification via "My Inbox" App
• Approval, Rejections via FIORI mobile/tablet devices 
• Model one-step or multi- step approval processes. 
• Deadline overdue monitoring
• Exception handling during approval

SAP claims that it is possible to define custom conditions, custom agent rules, and a list of possible recipients when forwarding tasks. You can define logic to set the task priority, the list of excluded processors, and the values of custom attributes provided in the My Inbox app. One of the difference between the Flexi-Workflow vs Classic Release Strategy is that it seems (at present) that the Flexi-Workflow do not have any Field Selection Control when each step is approve by a recipient. BUT let's see if SAP make any improvements on this issues and several other limitations as I can see today in the Flexi-Workflow method. 

Please check the following documentation from SAP and an example of Flexi-Workflow: 

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/FlexibleWorkflow/

https://froggysap.blogspot.com/2021/03/material-management-classic-release.html

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

Question: List of analytics Apps for Materials Management in S/4HANA 2023.

Answer: To find the latest FIORI Apps offered; for example Reporting and Analytics Apps for Purchasing, you can try the "Line of Business" folder in the web fiori library and use key words like "Overview", "Analytics", "Reporting" etc to find the latest Analytics/Reporting Apps for MM and any other modules. 

click the following link to SAP Fiori Library (any web browser)

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/

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

Question: If S/4HANA system already go life with only using the GUI backend, what are considerations for start to use selected FIORI Apps ? 

Resource reference: SAP Press and help.sap.com

Answer: Please refer to NetWeaver Consultants for the accurate depiction of the Infrastructures Installation requirements. 

https://help.sap.com/docs/SAP_FIORI_OVERVIEW/FioriInfrastructure/
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/ConfigurationofFIORI_Infrastructure/

https://amazonaws.com/reading_sample_sap_press_configuring_sap_fiori_launchpad.pdf

https://www.tutorialspoint.com/sap_fiori/index.htm

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

SAP MM - Employee Self-Service with LEAN Catalog (S/4)

 

CLICK here to view the Presentation

Question no 4030 : Overall Release Strategy for Purchasing Documents

In SAP Material Management, which of the following Release strategy is possible in SAP MM Purchasing Document ? 

(only one answer)

A. Overall Release Strategy allowed in Purchase Requisition. 
B. Item level Release Strategy allowed in Purchase Requisition. 
C. Release Strategy is possible Header and Item level in the Purchase Order.
D. Only Release Strategy in the Header level is allowed for Purchase Orders. 
E. All of the above.
.

Answer: A, B. D
Overall Release Strategy for PR means all PR item must be approve before the PR can be converted to PO (or next follow-up document). 

For PO, RFQ, Contract, Scheduling Agreements, the Release Strategy is only at the Header Level. 

SAP TM - Cost Distribution with FSD and FCDD (FCAD or ABD) (S/4HANA2023)

 

CLICK here to view the Presentation

SAP TM - Tax indicator at the Charge Type level

 

Q&A in Class (2025-01-07) S4611 (Part 2)

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

Question: References on TM Configuration Guide ?

The following book is highly recommended by SAP community. 

Answer: Books you can purchase on SAP S/4HANA TM as below by "SAP Press" and SAP help

https://www.sap-press.com/introducing-transportation-management-in-sap-s4hana_5945/

https://www.sap-press.com/transportation-management-with-sap-s4hana_5575/

https://help.sap.com/en-US/IG_91_TM_BASIC_SETTINGS_FINAL.pdf

https://help.sap.com/doc/PRODUCTION/MasterGuideTM7.5.pdf

https://help.sap.com/doc/ConfigurationGuideForInternalInboundDelivery.pdf

https://help.sap.com/doc/ConfiGuideBulk TransportationExtension.pdf

https://help.sap.com/doc/ConfigGuideDomesticInboundTM.pdf

https://help.sap.com/doc/SettingUptheTMCollaborationPortal.pdf

FYI: another one with 880+pages already send to your mail box

Also see these from SAP: 

https://www.sap.com/products/scm/transportation-logistics/videos.html

https://www.sap.com/assetdetail/2022/06/SomeoneTalkingAboutTM.html

https://www.sap.com/germany/documents/2021/08/Oct2024TMstatus.html

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

Question: What are the settings for Split and Consolidation of Freight Unit ?

The "Control" section and the "Planning Quantities" section in the "Freight Unit Building Rule" FIORI App are parameters used for "Consolidate" and/or "Split" Inbound/Outbound Deliveries into the desired Freight Units, for both HU and non HU scenarios.

Answer: Here are some simulation scenarios on the "Consolidate" and "Split" examples: 

https://froggysap.blogspot.com/2024/07/sap-tm-freight-unit-building-rule_9.html

https://froggysap.blogspot.com/2024/07/sap-tm-freight-unit-building-rule_82.html

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

Question: Inconsistency in Slide 133 "Stock Room Management" functionality ?

Answer: In many SAP documentations and SAP forums or OSS notes, SAP and many "experts" now often mention is there are now in S/4HANA (maybe 2023) have 3 storage choice: 

• Inventory Management with Storage Location
• Stock Room Management (= ECC Warehouse Management or ECC WM)
• Extended Warehouse Management (or EWM)

AND the following should be correct: 

Functionalities of LE-WM that are not part of stock room management are:

(LE-WM means the classic Warehouse)

• Task & Resource Management (WM-TRM)
• Warehouse Control Unit interface (WM-LSR)
• Value Added Service (WM-VAS)
• Yard Management (WM-YM)
• Cross-Docking (WM-CD)
• Wave Management (WM-TFM-CP)
• Decentral WM (WM-DWM)

Very likely these functionality will be further enhanced in the S/4 Embedded EWM system and seized development in the classic LE-WM in S/4HANA system. 

AND if you login to S/4HANA 2023, in the Logistics Execution folder, you can still find Cross-Docking (WW-CD) as well as Value Added Service (WM-VAS) as below screen shot under the folder Logistics Execution. (but not the Yard Management and VAS). From the historical perspective when SAP release the early days of EWM in 2000s: there are 4 features (as I remember) ie: WM-VAS (I think), WM-YM, WM-CD, WM-TRM, and since SAP decided to move the entire EWM in mid 2000s to the APO system; I don't think there were any more development of the initial rolled out features of the EWM in LE for maybe over 20 years. 

There are many posting in SAP Community that repeatedly "highly recommended" customers who have the need for LE-WM like the above WW-TRM, WM-LSR, WM-VAS, WM-YM, WW-CD, WM-TFM-CP, WM-DEM to migrate to the Embedded EWM system by December 2025. AND "maybe" in 2026 (or later or earlier or no idea) that even the available t-codes of Wave Pick, CD will even be removed from the LE module folder in the S//4 System. AND "maybe" then they will introduce the "NEW folder name" called "Stock Room Management" in the S/4HANA system Login (all maybe as we don't know whether Stock Room Management is a concept word for marketing or a definition one can see in SAP system login. 

I suspect SAP's intention is to retain the most basic functionality of the classic WM that is meant for stock management up to Storage Bins with TR-TO, and Posting change features (beyond MM-IM) but no intention to use WW-TRM, WM-LSR, WM-VAS, WM-YM, WW-CD, WM-TFM-CP, WM-DEM. (according to the Strategic Road Map explained in SAP Note 2881166). 

(the following update on January 09.2025 5:30am)

I highly suspect changing the name of "ECC Warehouse Management" to "Stock Room Management" in S/4HANA is both a "Direction Move" and "Marketing Move" in SAP to try to differentiate the "Light Weight Warehouse Management (ie: ECC WM in S/4) to the Embedded Warehouse Management system. AND the following names actually refer to the same thing: 

• ECC WM in S/4
• Stock Room Management in S/4
• Light Weight WM in S/4

As at S/4HANAN2023, the "ECC WM in S/4" can still be found in the folder Logistics - Logistics Execution ...., let's see if SAP will change the folder name to Stock Room Management in future SAP Release OR the name of "Stock Room Management" is a Marketing Term. 

The typo error slides in the book perhaps is trying to convey a message that in case you want to use any of these features below, you should just consider the Embedded EWM system as SAP will seize any development efforts for their use in the "Stock Room Management" or at least I think so: 

• Task & Resource Management (WM-TRM)
• Warehouse Control Unit interface (WM-LSR)
• Value Added Service (WM-VAS)
• Yard Management (WM-YM)
• Cross-Docking (WM-CD)
• Wave Management (WM-TFM-CP)
• Decentral WM (WM-DWM)

... the above features (some of them looks still can be found in the Logistics - Logistics Execution folder) (in the last Login to SAP on S/4HANA 2023). 

The S/4HANA Stock Room Management functionality should include the following as of the current findings:

• Warehouse Structure of Storage Type, Storage Section, and Storage Bin
• Processing Inbound with Putaway Strategies using TR and TO (with or without RF). 
• Processing Inbound with Removal Strategies TR and TO (with or without RF). 
• Supports Batch Management. 
• Internal Posting via Posting Change Notice. 
• Cycle Counting and Physical Inventory. 
• Stock Replenishment.
• Likely with integration to MM, SD, PP, QM modules (similar to ECC WM). 
• No integration to S/4HANA Transportation Management at the moment. 
• Last test in S/4HANA2022 the Wave Picking can still be used in the ECC WM in S/4 but whether SAP will remove this transaction code entirely or just stop development for its use in the Lightweight WM will depend on SAP in future SAP versions. 

We should think of Stock Room Management offers much more visibility of the Warehouse compared to MM Inventory Management via Storage Location. AND the purpose of Stock Room Management is only for organizations that require higher visibility of materials in the Warehouse in terms of Movement and Storage Controls. 

As at S/4HANA2022, there are FIORI Apps for the "ECC WM" in the S/4 System BUT the FIORI Apps are HTML of the backend transaction codes. Whether SAP will release any "UX" FIORI App for the "Stock Room Management" remains to be seen. 

Although the Embedded EWM seems to be more relevant for Complex Warehouse scenario; BUT I do think that in a "Simplified" implementation of EWM in S/4 can perform the SAME as the "Stock Room Management" while at the same time allows that flexibility to use any of the EWM functionalities. 

As of to-date, it does look like the focus of Stocks Storage Management for SAP is to focus its resources on the Development of the S/4HANA Embedded EWM system. 

See the following link and SAP Notes will be helpful:

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/StockRoomManagement/

https://www.sap-press.com/introducing-stock-room-management-with-sap-s4hana_5156/

SAP Note 2577428 - Road map for LE-WM in SAP S/4HANA
SAP Note 2270211- S4TWL - Warehouse Management (WM)
SAP Note 2881166 - FAQ Stock Room Management

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

Question: What is the purpose of Tax Indicator in the Charge Type ? 

Looks like the Charge Type "Tax activation" may allow Tax code determination via the Charge Type level (preliminary conclusion which will have to be verified in the future). 

latest update (January 9.2025 4:30am)

• Findings as at January 9.2025 4:30am
• TM-Basic Function-Charge Calculation-Basic Setting-Define Charge Type (an indicator that looks like perhaps to activate Tax relevancy at the Charge Type level). 
• TM-Settlement-Freight Settlement-Integration for Settlement Posting-Tax-Assign Tax indicator for Charges (Set Tax indicator to Charge Type). 
• I think another configuration step is via the standard Access Sequence for Tax Code Determination in MM+FI Configuration (or something else). 
• Or more steps. 
• Level of Activation is likely at Country + Charge type possibility. 

Of course describing the possible configuration is not enough, Looking forward to more findings and application level actual application level simulation on this issue when time and SAP access is possible. 

Answer: See the following:

https://help.sap.com/docs/SAP_TRANSPORTATION_MANAGEMENT/TaxDeterminationinTM/

https://froggysap.blogspot.com/2025/01/sap-tm-tax-indicator-at-charge-type.html

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

Question: How does the Agency Business Document (ABD) with respect to "Cost Distribution" works ?

Answer: The above Accounting to send FSD settlement document as an "Agency Business Document (ABD)" to the another module called "Settlement" to perform the GR/IR reversal so as to switch the posting for Material distribution involves settings beyond TM module, should be involving FI and the Settlement module; when TIME and accessible to SAP is available, I will try to at least show the above FI posting for Outbound Delivery scenario. 

latest update (January 9.2025 3:00am)

• I have reason to believe that the word written by someone in SAP Community (or whatever source) for the Document/Term "Agency Business Document (ABD)" may have also other SAP names "Freight Cost Distribution Document (FCDD)" ie:
• "Agency Business Document (ABD)" 
• "Freight Cost Distribution Document (FCDD)"
• "Freight Cost Allocation Document (FCAD)"
• I have high suspicion to think that they all mean the same thing (still I could be wrong)
• The above Accounting Posting (tried to simulate in below Blog Post) which result in the following:
• Create a PO and SES: The PO and SES are created in the document flow. (Done) (Step 9 in the Blog).
• Debit a temporary freight expense account: The system debits a temporary freight expense account and credits the GR/IR account for the vendor. (Done) (Step 10 in the Blog).
• Post the cost distribution financial entry: The cost distribution financial entry is posted in the Settlement Management module. (Done) (Step 11 in the Blog).
• Clear the temporary expense account: The system clears the temporary expense account and posts to the material. (To be Simulated as this Step I high suspect in under the umbrella of S/4HANA "Settlement Management" Module (the re-engineered Rebate Module)). 
• The next challenge is to work on this Final Step, the above steps is my Simulation and Thought results in the past 24 hours which could be the right direction or maybe TOTALLY WRONG, and therefore let me work on it. 

FYI: in the past 24+ hours from 08.Jan 2025 5am, research on web findings are many bloggers or "SAP Experts" talks (describing) or writes about it BUT no actual step by step with SAP Screen shots demonstration are published SO nothing said by others can be verified until there are actually simulated in an SAP login. 

Looking forward to more findings and application level simulation on this issue when time and SAP access is possible. 

See the following blog posts (Pending last step of Material Distribution):
https://froggysap.blogspot.com/2025/01/SAP TM - Cost Distribution with FSD and FCDD (FCAD or ABD) (S/4HANA2023)

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