--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Are there OSS Notes for FIORI App ?
.jpg)
Answer: Key points about finding OSS notes for Fiori apps:
- Accessing the Fiori App Support: When experiencing an issue within a Fiori app, navigate to the system information section (usually accessible through a gear icon or similar) and look for an option related to "App Support" or "Technical Information."
- Searching by Fiori App ID: Once you access the App Support feature, you can input the Fiori app ID (which can be found in the application details) to retrieve a list of relevant SAP Notes.
- Transaction Code Search: If the Fiori app is linked to a specific transaction code, you can also use that code to search for relevant SAP Notes.
- Interpreting the Notes: The returned SAP Notes will provide detailed information about the issue, potential causes, and recommended solutions, including any necessary system adjustments or configuration changes.
- Important Considerations: System Version: Always ensure you are checking SAP Notes relevant to your specific SAP system version as fixes may vary across releases.
- Backend System: If your Fiori app interacts with multiple backend systems, you may need to search for notes related to each backend system involved.
To patch OSS notes for a Fiori app, access the SAP Support Portal, find the relevant SAP note for the specific issue affecting your Fiori app, download the patch, and then implement it in your system using the appropriate transaction depending on the type of fix required (e.g., using transaction SNOTE to apply the patch directly to your system) - always consult your system administrator before applying any patches; ensure you understand the implications of the patch and back up your system before implementation.
However, applying OSS notes for FIORI App is often not as straight forward as a simple patch step above as the example FIORI OSS note below:
Example: OSS Note 1 Error Description and Resolution:
#### **OSS Note example from Repository: Authorization Errors in Fiori App**
- **Version:** 001
- **Priority:** Critical
- **Status:** Released
- **Component:** FIORI-AUTH
- **Affected Releases:** SAP S/4HANA 2020+, SAP BTP
**Symptoms:**
- Users receive "No Authorization" errors despite correct role assignments.
- App-specific permissions not recognized.
**Cause:**
- Missing PFCG role inheritance for the Fiori app’s catalog.
- Incorrect scope in OAuth 2.0 configuration (BTP).
**Resolution:**
1. Add catalog `/APPNAME` to PFCG role via transaction PFCG.
2. For BTP, update XSUAA scope in `manifest.json` to include `$XSAPPNAME.Display`.
3. Redeploy app and refresh user tokens.
Example: OSS Note 2 Error Description and Resolution:
#### **OSS Note example from Repository: Fiori Launchpad Tiles Not Loading**
- **Version:** 001
- **Priority:** High
- **Status:** Released
- **Component:** FIORI-UL-LAUNCH
- **Affected Releases:** SAP S/4HANA 2021, SAP BTP CF 2105
**Symptoms:**
- Tiles in the Fiori Launchpad fail to load, showing "Loading..." indefinitely.
- Error message "Failed to load tile configuration" in browser console.
**Cause:**
- Incorrect caching of tile metadata due to corrupted browser storage.
- Missing backend OData service activation.
**Resolution:**
1. Clear browser cache or launch the app in an incognito window.
2. Activate OData service `/IWFND/MAINT_SERVICE` in transaction SICF.
3. Apply SAPK-12345 patch for UI5 version 1.96.1.
4. Regenerate Launchpad content via transaction `/UI5/APP_INDEX_CALCULATE`.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Is it possible to use 3rd Party Scenario for LEAN Service, meaning Sales Order generating PR for LEAN Service and subsequent SES then LIV to LEAN Service Vendor and Billing to the Customer requesting the LEAN Service ?
*** Pending ****
Answer: Yes, it is possible to use the LEAN Service in the Sales Order to generate a PR for LEAN Service to be done by Vendor to a Customer (in a 3rd Party Sales Process), and when time permit; a BLOG Post will be posted to illustrate the scenario in question:
*** Pending Blog Posts ***
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: How to setup InCO term Location treatment in S/4HANA in preparation for S/4 TM module in the future ?
.jpg)
Answer: Here is a simple blog posts to setup the INCOterm Location in S/4HANA.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review how to Display Business Partner ?
Answer: Below is blog posting steps for Display Business Partner FIORI App:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Selected relevant summary of changes in the Material Master in S/4HANA ?
- Material Type introduction Product Type Group "2" for LEAN Service Material Master.
- Material Master code field length increase from 18 to 40.
- MRP2 Quota Arrangement Usage field remove due to simplification.
- MRP3 Consumption Mode "5" (Consume in Period).
- MRP4 BOM Selection Method field removed as Production Version is Mandatory.
- MRP4 Storage Location segment is removed forcing use of MRP Area for SLoc Planning Control.
- Advanced Planning view for Embedded PPDS.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: S/4HANA SLoc segment in MRP4 view no long possible, what method to use to Ignore Storage Location stock for MRP Planning in the S/4 system ?
Answer: pending
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Self-Service Procurement Scenario step-by-step ?
Answer: Self-service procurement in SAP S/4HANA is a process that allows employees to request goods and services without needing direct involvement from a purchaser. The process is designed to be faster, easier, and smoother using FIORI UX Apps and Internet Catalog.
See the following Blog Posts illustrating the process step for Self-Service Procurement for S/4HANA:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: LEAN Service setup and processing review in S/4HANA /
_Blogged.jpg)
Answer: Lean Service PRs are identified by "product type group" as Service (2). Purchase orders for lean service are identified with "product type group" 2 and can be created without purchase requisition. There are now 3 options for Services Procurement:
- Classic Simple Service using Material type DIEN with PO-GR-LIV (ECC + S/4)
- External Service using Service Master with PO-SES-Approval-LIV (ECC + S/4)
- LEAN Service using Material type SERV with PO-Fiori SES-Approval -LIV (S/4)
Refer to the following Blog Posts for an example of the LEAN Service in SAP in S/4HANA 2024.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: How to address the issue of the following no longer possible in S/4HANA:
- Material Master MRP 4 SLoc data segment.
- IMG t-code OMIR (refers to the transaction "Define Storage Location MRP per Plant," which allows users to customize Material Requirements Planning (MRP) settings for specific storage locations within a plant, essentially defining whether a storage location should be included in MRP calculations or not.)
_Blogged.jpg)
Answer: The Blog Posts show the difference between Storage Location MRP/Planning Control in ECC Ehp8 vs S/4HANA setup:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Compare the difference between Classic MRP and MRP Live ?
Answer: SAP S/4HANA as of 1511 (November 2015) introduced a new MRP functionality called MRP Live, which was basically the same concept and the same logic, but improved for better performance on an SAP HANA database. Since then, the previously existing MRP and its transactions have become known as classic MRP to help differentiate between the versions. From a planner's perspective, it is important to note that MRP Live offers advantages as well as disadvantages:
Advantage:
- When SAP created the SAP HANA database, there was a huge opportunity to improve MRP performance using the power of SAP HANA’s in-memory parallelization. Therefore, SAP decided to improve classic MRP, pushing the MRP logic into the database layer and creating MRP Live.
- Instead of using User Exit for Selected Materials if used MD01 or MDBT, MRP Live via MD01N uses Multiple Material Section, Selection by Product Group, Selection by MRP Controllers.
- In Classic MRP, execution of MPS Materials and MRP Materials uses different t-codes; however, MRP Live can have choice to execution both MPS and MRP Material or either one.
- For Materials activated for Advanced Planning, MRP Live can also include in the same planning run but will use the PPDS Heuristics.
- App ID F1339 (Schedule MRP Run) Fiori App combines MD01 and MDBT as the FIORI App can be used to create Background or Online Jobs as desired by the Planner.
Disadvantage:
- NETPL Planning File Entry feature is not supported (ie: only NETCH and NEUPL).
- MRP List will not be created.
- For Procurement type "F", the system always create Purchase Requisition as Planning Horizon is no longer available in OPPQ (Plant Parameter) and SMK (Scheduling Margin Key) in MRP 2 view is no longer Mandatory.
- Production Version is Mandatory for Procurement type "X" and "E".
The new MRP Live has been defined by SAP as the future architecture, which means that all the innovation in this area will be focused on MRP Live, rather than classic MRP. Therefore, it is highly recommended that new SAP S/4HANA implementations use MRP Live as their default planning tool.
Note: To switch from MRP Live to classic MRP in SAP, you can use the transaction code MD_MRP_FORCE_CLASSIC which allows you to explicitly force specific materials to be planned using the classic MRP logic within an MRP Live run; you can also set this option directly in the material master record for individual materials to always use classic MRP planning instead of MRP Live.
See the following Blog Post for an illustration of the difference between Classic MRP and MRP Live:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.