--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Classic vs S/4 FIORI Technical Object creation for SAP Plant Maintenance.
Part1_FLEQ_Blogged.jpg)
Answer: The FIORI "UX" App "Create Technical Object" is a combined "UX" App to Create either Functional Location or Equipment and therefore combining the classic transaction code of IL01 and IE01. Besides layout changes of the look and feel in the FIORI interface via "Create Technical Object" FIORI App, there is really not much difference comparing this App to IL01 or IE01.
See link
Another FIORI App for Technical Objects perhaps worth reviewing is the "Find Technical Object" FIORI App ID "F2072"
See the link below for a demonstration of this App:
https://docs.google.com/presentation/FindTechnicalObjectFIORIApp/
.jpg)
.jpg)
.jpg)
Answer: The above transaction codes are still valid in S/4HANA2023 similar to its availability in ECC EhP8. One can conclude that in a technical upgrade, the transaction codes for Technical Object creation, change, or display and reporting (list display) are the same in ECC to S/4HANA. AND although there are some FIORI Apps available for some (not all) of the Technical Objects above, the "UX" (User Experience) may not be as impressive as other modules (like in MM and SD).
Some of the key features this App are:
- List Display FL and EQ plus download to Excel.
- Display Installation information for the Technical Object in the Hierarchy.
- Perform Installation and Dismantling.
- Shows details of related Notification and Order for the Technical Object of FL an EQ.
- etc.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Advanced features of "AI" (Artificial Intelligence) in S/4HANA 2023 Plant Maintenance ?
.jpg)
Answer: Predictive maintenance continually assesses equipment health in real time, helping the maintenance organization to maximize uptime and therefore equipment and/or functional location performance. There is a "Predictive Modeling" tool announce by SAP recently (only via FIORI App) but unfortunately we do not have access to activate it for simulation. Nevertheless, to be really able to use such a "Modeling" tool, the Equipment or FL must be IOT-powered; meaning sensors embedded in equipment to collect data and predict potential failures, allowing for proactive maintenance and minimizing downtime. Hopefully, SAP soon will provide a course content and access to this kind of advanced App to provide knowledge transfer to consultants and the customer.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Option for EAM Deployment from ECC to S/4HANA ?
.jpg)
Answer: The ways in which how the PM module will be deployed from ECC to S/4HANA system is of the following:
- On-Premise : On-premise solutions involve resources being deployed within the organization's own infrastructure. The Organization will need both IT (BTS team) as well as Software support teams internally as the SAP software is installed and maintenance within the premises of the Organization. The organization can then flexibly customize the SAP system to their process requirement either using internal teams or SAP partners.
- Cloud (Private) : Private Cloud service is still managed by a 3rd party but it is dedicated for a single Organization. The SAP software is access via Cloud, while some Customization is still possible but depending on licensing agreement with SAP.
- Cloud (Public) : using Cloud service whereby it is shared by multiple organizations, often time this kind of license are for organizations with "super lean" IT and support whereby most if not all SAP support is by the Cloud service organization. Usually standard use of the SAP system is expected with limited or no Customizations. This approach is generally acceptable for organizations with lean IT and smaller organizations which prefer to use "Standard" SAP. Implementation time line is usually the shortest for such as approach.
- Mobile: Setting up of Mobile infrastructure is desirable if there is an intention to use tablet devices for Job Card deployment from Maintenance Orders to the Technicians via FIORI login via Mobile Devices. The "Simplification Maintenance" Scenario for Mobile solutioning allows Technician to perform confirmation via their Mobile Devices.
It is important to note that as the PM or EAM module is not the only SAP component implemented in a S/4HANA migration from ECC, for a mid size to large organization, it is likely for a Deployment with either On-Premise with Mobile or even Hybrid with On-Premise, Private Cloud and Mobile architecture as a Deployment option.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is SAP BTP in S/4HANA ?
Answer: There are always 2 sides of SAP ie: the Application side and the Technical side. While the Application side (often where Application Consultants works are associated with) are the SAP software areas like FICO, MM, SD, PP, HR etc.
- Basis: The Technical side of SAP ensure that everything should work the way it should, and during the R2 and R3 SAP versions are usually referred to as Basis (often the job function of Basis Consultants). SAP Basis is technological foundation and system administration component for running SAP
- Netweaver: SAP NetWeaver, originally developed by TopTier Software in 1997 and acquired by SAP in 2001, was first released in 2004. The TopTier Software develops the portal technology that would become the foundation of SAP NetWeaver. SAP Basis is the foundation of SAP NetWeaver, with Basis evolving into the Web Application Server (WAS) and becoming a mandatory requirement for installing any NetWeaver component. NetWeaver encompasses various functionalities, including Portal, Business Intelligence, and Process Integration, building upon the capabilities of the previous Basis. I'd like to call Netweaver the Basis++ as Netweaver builds on top of the SAP Basis.
- BTP: Perhaps the one of the best differentiating statement on Netweaver vs BTP is that SAP NetWeaver is the on-premise foundation for SAP applications, while SAP Business Technology Platform (BTP), formerly SAP Cloud Platform, is its cloud counterpart. SAP Business Technology Platform (SAP BTP) was introduced in January 2021. SAP BTP was introduced as part of the SAP strategy to unify its portfolio and cloud offerings under a single platform. I'd like to call BTP as NetWeaver++ as BTP enhanced on top of SAP NetWeaver.
- SAP BTP for Data Management offers a wide range of data management options (previously the BI component of NetWeaver) are offered by SAP BTP, including:
- Data Warehousing: Storage and analysis of vast amounts of data are made possible by the cloud-based data warehouse offered by SAP BTP.
- Data lakes: Regardless of the type or structure of your data, SAP BTP offers a cloud-based data lake that can be used to store it all.
- Data Visualization: Dashboards, reports, and charts are just a few of the tools available in SAP BTP for visualizing data.
- SAP BTP for Application Development is for the creation of applications, SAP BTP offers a range of tools and services, including:
- Cloud based IDE: SAP BTP offers an IDE in the cloud that may be used to create apps in a number of different programming languages.
- Code Repository: SAP BTP offers a repository for managing and storing code.
- CI/CD Pipeline : The build, test, and deployment of apps can all be automated using the CI/CD pipeline offered by SAP BTP.
- SAP BTP for Application Integration offers several integration capabilities are offered by SAP BTP, including:
- API management: SAP BTP offers a platform for the creation, administration, and security of APIs. In the context of SAP systems, APIs (Application Programming Interfaces) like RESTful APIs using OData are generally considered more modern and flexible than BAPIs (Business Application Programming Interfaces) which use RFC (Remote Function Call).
- Event-driven architecture: SAP BTP offers an event-driven architecture that can be used to integrate apps without a shared data model.
- Microservices: To help developers create scalable, loosely linked systems, SAP BTP offers a microservices architecture.
- SAP BTP and Intelligent Technologies uses a range of clever technologies, such as:
- Artificial intelligence (AI): SAP BTP offers a range of AI features, such as computer vision, natural language processing, and machine learning.
- Machine learning (ML): SAP BTP offers a range of ML features, such as fraud detection, predictive analytics, and consumer segmentation.
- Internet Of Things(IoT): Data collecting, data analysis, and predictive maintenance are just a few of the Internet of Things (IoT) features offered by SAP BTP.
- SAP BTP and Analytics offers a number of analytics features, such as:
- Data Mining: Finding patterns and insights in data is a process known as data mining. To extract insights from your data, SAP BTP offers a range of data mining tools and methods.
- Predictive analytics: Utilizing data to make predictions about the future is known as predictive analytics. To predict consumer behavior, fraud, and other outcomes, SAP BTP offers a number of predictive analytics tools and approaches.
- Business intelligence: Business intelligence (BI) is the process of using data to enhance decision-making. To visualize data, produce reports, and build dashboards, SAP BTP offers a number of BI tools and methodologies.
- While not strictly mandatory for all S/4HANA implementations, SAP Business Technology Platform (BTP) is highly recommended and often essential for extending and integrating S/4HANA Cloud solutions, especially for side-by-side extensions and connecting to other systems.
- SAP BTP is a key platform for building and deploying applications that extend the functionality of S/4HANA Cloud, allowing for customization and integration without altering the core S/4HANA system.
See the following links:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: The Classic Technical Objects transaction code in S/4HANA (similar to ECC)
.jpg)
Answer: The above transaction codes are still valid in S/4HANA2023 similar to its availability in ECC EhP8. One can conclude that in a technical upgrade, the transaction codes for Technical Object creation, change, or display and reporting (list display) are the same in ECC to S/4HANA. AND although there are some FIORI Apps available for some (not all) of the Technical Objects above, the "UX" (User Experience) may not be as impressive as other modules (like in MM and SD).
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What are difference in Enterprise Structure of the Plant Maintenance module comparing ECC and S/4AHANA ?
- Maintenance Planning Plant
- Maintenance Plant
The functionality is the same from ECC to S/4 where the Logistics Plant (for MM, PP, SD) can immediately be used as a Maintenance Plant primarily as the (1) Location for the Technical Object of FL and EQ, (2) Maintenance Work Center, and (3) Spare Parts Storage. In this respect, usually this Enterprise Structure mapping for ECC to S/4HANA upgrade is "easy" unless there is a need to "revamp" the Enterprise Structure when implementing S/4HANA.
The Maintenance Planning Plant (ECC and S/4 the same) will have to be explicitly assigned (see blog post link below), The use of the Planning Plant is for Maintenance Task List header, Maintenance Plan as well as the Header of the Maintenance Order. In this respect, Planning Plant is for "Planning" along with the Planner Group" and the Maintenance Plant is for "Execution" for assignment of the Work Center, representing as "Main Work Center" and Spare Parts issuance.
Answer: See link
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: the IBAU BOM, what is it ?
The IBAU Material Type (ECC and S./4HANA the same functionality) is often used to represent the Header of the Material BOM to assign with Spare Parts, where the Header (IBAU BOM) is then assigned as a Construction Type to the FL or EQ. This is especially true when the Header BOM is not to be procured or inventoried; it is to be used like a "Phantom" to link the Spare parts to the Functional Location and Equipment master. Creation of the IBAU Material is easy as it only need the Basic data view with the Material code, Description, and UOM.
Answer: see link for configuration of IBAU material type and application demo for IBAU Material BOM.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.