SAP Community - SAP S/4HANA Public Cloud

SAP Named a Leader in the 2024 Gartner® Magic Quadrant™ for Recurring Billing Applications

2024-08-15T09:08:37.514000+02:00

Just yesterday, Martin Barkman announced SAP was named a Leader in the first-ever 2024 Gartner® Magic Quadrant™ for Recurring Billing Applications. Gain access to the full report and read the announcement here.

For our community of developers, partners, and users, we believe this recognition attests to the innovation and collaboration that drives our success. It’s a clear signal that we are on the right path, delivering solutions that not only meet but exceed market expectations.

Why This Recognition Matters

SAP stands out as the only true ERP vendor offering a top-tier recurring billing solution seamlessly integrated with SAP S/4HANA Cloud Public Edition. Our customers seamlessly connect their billing processes with other critical business functions via the end-to-end suite powered by SAP S/4HANA Cloud Public Edition and SAP Subscription Billing.

Being named a Leader in Gartner®’s Magic Quadrant™ is a significant achievement, not just for SAP but for our entire ecosystem of customers, partners, and community members. For our customers, this recognition reaffirms the value of choosing SAP as their trusted partner for subscription billing and recurring revenue management. It signals that SAP is not only capable of meeting current market demands, but is also well-positioned to lead the industry in the years to come.

This recognition is also a call to action. As leaders in the field, we have a responsibility to continue pushing the boundaries of what’s possible in subscription billing and recurring revenue management. We invite our community members to engage with us, explore our solutions, and share their insights and experiences.

For our latest customer success stories and to learn more about our solution, visit our NEW SAP Subscription Billing community page.

How to adopt Group Reporting for existing public cloud accounting customers

2024-08-15T10:16:22.838000+02:00

If you already live for years and you are now looking forward to getting your corporate close supported with S4HC Group Reporting, this article may help you adopt the solution quickly and efficiently. We will explain which general activities needs to be done to be ready using S4HC Group Reporting.

Firstly you need activate the main scope item 1SG(Group Reporting - Financial Consolidation) in your system.

Master Data

You may prepare your master data,

Activity - Description	related area	SSCUI or App	Description of Fiori apps / SSCUI	General Comment
Create Company IDs	Master Data	SSCUI	Create Company	Ensure all companies are prepared. Usually this is done when creating company code, but check if this activity is done.
Assign Company ID to Company Code	Master Data	SSCUI	Assign company code to company	In assumption there is no flexible derivation of consolidation units, ensure 1:1 assignment to company codes.
Assign Company ID to vendor / customer/ GL account	Master Data	App	Maintain Business Partner	Ensure all intercompany customers/vendors/GL accounts with correct company assignment.
Decide which additional data should be released from FI and how is the setup of these master data (e.g. decide for matrix consolidation, master data and hierarchy setup)	Master Data	SSCUI	Define Consolidation Master Data Fields	In case customer want to maintain master data and / or hierarchy for the respective field(s).
Adjust or create a new version	Master Data	SSCUI	Create Version from Reference Version / Define Version	Copy and adjust a version if you cannot use a pre-delivered version.
Create FS items	Master Data	App	Define FS Items	Scope items 1SG deliver appr. 210+ FS items to be used directly. Check if additional FS Items are needed and copy similar FS Items from pre-delivered content. Make sure the correct attributes are assigned.
Create and assign mapping GL accounts to FS items	Master Data	App	Map FS Items with GL Accounts Import FS Item Mappings Assign FS Item Mappings	Ensure all FI accounts are mapped to FS item. There is a recommendation to mapp even secondary cost elements to a clearing FI item.
Define consolidation units for each company with the same technical key Define consolidation units for none integrated company codes	Master Data	App	Define consolidation units	You may consider to prepare this based on the company ID
Assign consolidation units to consolidation group	Master Data	App	Manage Group Structure - Group View	Set the period and year for technical first consolidation
Create subitems based on new transaction types	Master Data	SSCUI	Define Subitem Categories and Subitems	adjust 19 transaction types with respective number of subitems, in case customer define the new transaction type, you need create additional subitem (s). Check if new selection for breakdown category are needed. If yes adjusted breakdown category with copied selection.
Create subitems based on new functional areas	Master Data	SSCUI	Define Subitem Categories and Subitems	adjust 21 function areas with subitems, in case customer create new function areas, then you need create additional subitem.
Specify Account Numbers for Annual Net Income and Balance Carryforward	Master Data	SSCUI	Specify Account Numbers for Annual Net Income and Balance Carryforward	You need this activity if customer does not want to use the predefined GL account and FS item.
Define Group Reporting Preparation Ledgers	Master Data	SSCUI	Define Group Reporting Preparation Ledgers	if not already set

Process adjustments

If best practice setting is not sufficient design task groups(for Data Monitor and Consolidation Monitor), you may

copy existing task group(s) and
adjust based on customer needs
insert new task(s) or exclude tasks which are not needed
assign task group(s) to respective version(s)

Activity - Description	related area	SSCUI or App	Description of Fiori apps / SSCUI	General Comment
Import Foreign Exchange Rates	Process Preparation	App	Import Foreign Exchange Rates
Adjust task group or task group assignment for Data Monitor if needed	Process Adjustment	SSCUI	copy task group, assign task group, assign new task, delete not used task => several SSCUI's
Adjust task group or task group assignment for Consolidation Monitor if needed	Process Adjustment	SSCUI	copy task group, assign task group, assign new task, delete not used task => several SSCUI's
Adjust selections if customer specific selections are needed.	Process Preparation	App	Define Selections	Copy already existing selections to customer namespaces (refer to note 2326112 for Namespace restriction in SSCUI. • S, Q, R, X, P, Y for alphanumeric fields • 5, 6, 7, 8, 9, 0 for numeric fields

Reporting

Activity - Description	related area	SSCUI or App	Description of Fiori apps / SSCUI	General Comment
Adjust Reporting capabilities	Reporting	App	Manage Global Hierarchies	Adjust the hierarchies for : - Type FS Items (if new FS Items are created) - Type Transaction Type - Type document Type
Adjust Reporting Rule	Reporting	App	Define Reporting Rules / Assign Reporting Rules to Versions	Adopt the reporting rule

Initial Load of Reported Financial Data

After all setting is prepared, you may need consider to prepare your initial reported data. In this article, we introduce the technical first consolidation starting point that can be different from your cutoff date. The starting point is the time(period/year) for the initial technical consolidation of the capital and the investment values. After starting point onwards, the correct consolidated financial statements including all consolidation entries should be carried out and posted in a correct period ranking in S4HCGR.

There is no migration of already posted consolidation financial statements. If consolidation results needs to be available(for comparison purpose) in your S4 system, that have already been completed in the past, these closing must be processed/executed and posted again in the Group Reporting environment.

Here is an example,

Go live is 004/2024, and starting point is 012/2023, periods 012/2023, 001/2024, 002/2024, 003/2024 need to be processed and finished in Group Reporting. And we need to provide as of the starting point the initial load of reported financial data in 012/2023 based on YTD(year to date) value.

There are several customer situations together with examples we would like to explain.

Customer Case 1

Customer Case 2

Customer Case 3

Customer Case 4

Customer Case 5(initial load via flexible upload of reported financial data)

Customer Case 6(initial load via flexible upload of reported financial data)

This will not cover each every customer situation, and your feedback or best practice is warmly welcome!

Extensibility Approaches in SAP S/4HANA Cloud Public Edition

2024-08-15T11:07:30.967000+02:00

In the context of SAP S/4HANA Public Cloud Edition, Clean Core principles emphasize minimizing customizations to maintain system integrity and simplify upgrades. Extensibility approaches are designed to enhance functionality while preserving the core system’s stability. By adhering to Clean Core principles, organizations can achieve greater agility, lower total cost of ownership, and a smoother transition during system upgrades. SAP S/4HANA Cloud Public Edition offers various extensibility options to adapt and extend its functionalities according to business needs. These options ensure flexibility while maintaining the integrity and upgrade stability of the system. Below, we explore the different types of extensibilities and provide best practices for implementation.

SAP S/4HANA Cloud Public Edition offers support for the following three main extensibility options:

Key User Extensibility
Developer Extensibility
Side-by-Side Extensibility

Extensibility Comparison Table

Parameter	Key User Extensibility	Developer Extensibility	Side-by-Side Extensibility
Use Case	Low-code/no-code adaptations and extensions	Professional ABAP development	Sophisticated development projects and custom UIs
Persona	Business expert, implementation consultant, citizen developer, key user	Professional ABAP developer	Developers with knowledge of Java, Node.js, ABAP
Tools/Platform Used	Key user tools (low-code/no-code tools)	ABAP Development Tools (ADT), SAP S/4HANA Cloud ABAP Environment	SAP Business Technology Platform (BTP)
Skills Required	Minimal coding skills	Professional ABAP development skills	Programming skills in Java, Node.js, ABAP
Proximity to Core SAP S/4HANA	Tightly coupled	Tightly coupled	Loosely coupled
Example Scenario	Adding custom fields to business objects	Developing custom SAP Fiori apps	Creating custom applications on SAP BTP
APIs Used	Local public APIs and extension points	Local public APIs and extension points	Remote SAP APIs (e.g., OData services)
Lifecycle Management	Managed by key users	Managed by ABAP development lifecycle (ADT, ATC)	Managed separately on SAP BTP

Key User Extensibility

Key user extensibility allows business experts to extend SAP S/4HANA Cloud without deep technical knowledge. It focuses on "last mile" extensions using low-code/no-code tools.

Types of Key User Extensibility are detailed as below:

S.I No	Key User Extensibility Applications	Description
1	Adapt UI	Adapt UI allows users to customize Fiori Apps by hiding or renaming fields, groups, and areas; adding fields from the field repository; and reorganizing UI elements. Users can combine or split fields, create new groups, and define custom filter and table variants. Note that Adapt UI is for Fiori Apps, whereas SAP Screen Personas is used for Web GUI screens.
2	Custom Fields	Enable users to create, edit, and manage fields by extending SAP tables, applications, CDS views, and OData services. Users can also delete custom fields, though this is restricted if the field has been transported. Custom fields can be used across various UIs, reports, forms, service interfaces, processes, and searches. Additionally, users can define associations to custom or standard SAP business objects and extend CDS views and OData services with SAP fields from lower layers of the virtual data mode.
3	Custom Logic	Custom Logic offers a streamlined development experience with features like API exploration, syntax checking, and code completion. It includes a sandbox environment for testing before publishing, ensuring secure and robust implementations. To maintain system integrity, ABAP capabilities are restricted, prohibiting direct database changes (except for selects), task alterations, dynamic programming, and code generation.
4	Custom Business Objects	You can create and manage business objects and their database tables, add, or delete fields and objects, and develop CDS views and OData services for data entry or integration with other systems. Define sub-nodes and associations with both custom and standard SAP business objects. Implement custom logic at the node level, manage custom business objects by publishing, editing, resetting, copying, or deleting them, and perform tracing as needed.
5	Manage KPI’s and Report	In the Manage KPIs and Reports application in SAP S/4HANA Public Edition, you can copy and modify SAP-delivered KPIs to fit your business needs. Define drilldowns for in-depth KPI analysis and apply filters to focus on specific areas. Save filtered analyses for future use and set up associations between KPIs for runtime analysis. Additionally, you can navigate to transactional apps to act on your analysis results.
6	Create Custom Analytical Queries	The Create Custom Analytical Queries application in SAP S/4HANA Public Edition allows you to create queries based on released SAP analytical data sources (CDS views of type cube) or custom sources. You can copy standard SAP queries, customize fields (such as labels and data display), and adjust filters (fixed or user-defined). Additionally, you can create parameters for user input and define calculated, restricted, or converted measures. The application includes testing capabilities to preview results in Design Studio.
7	Create Custom CDS Views	The Create Custom CDS Views application in SAP S/4HANA Public Edition lets you view a list of pre-delivered public data sources (VDM CDS views) and existing custom CDS views, as well as preview available data sources. You can create new custom CDS views by selecting a primary data source, adding associated data sources, and modifying field properties (annotations). You can also create calculated fields with arithmetic calculations, case statements, and conversions, and display parameters for the selected data sources if applicable.
8	Custom Reusable Elements	The Custom Reusable Elements application in SAP S/4HANA Public Edition allows you to modularize and organize your custom code. You can create and manage Custom Libraries, add methods, and provide details for each method. Key features include creating new libraries, adding and detailing methods, testing, saving, and publishing your custom code.
9	Custom Logic Tracing	Custom Logic Tracing allows you to monitor the processing order of determinations, validations, and actions for custom business objects and nodes. You can trace input, output, and changing parameter values, as well as execution durations. When creating a trace, you can set a name, retention date, and activation lifetime. Tracing can be started and stopped as needed, and the trace overview will display the status and results of the trace.
10	Custom Catalog Extensions	With the Create Custom Catalog Extensions application in SAP S/4HANA Public Edition, you can extend SAP Fiori catalogs by adding various elements such as custom business object UIs, Smart Business KPIs, reports, Analytical Design Studio applications, custom tiles, and Analytic Cloud Stories. You can also configure a custom inbound service app via OAuth. Extended catalog items will appear in the Fiori Launchpad, where you can use the "Personalize Home Page" feature to add custom tiles to one or more launchpad groups.
11	Custom Communication Scenario	Create Custom Business Objects and Custom CDS Views using their respective Fiori apps, ensuring to select the OData Service flag during creation. Combine multiple OData services into a single scenario with the Custom Communication Scenarios Fiori app. Then, set up a communication arrangement in the Custom Arrangement Fiori app, where you configure the technical user and activate the service endpoint for the services included.
12	Extensibility Inventory Application	You can view an overview of your extensibility items, including their associations and dependencies. This allows you to understand the impact of importing or exporting items on others. The system provides details such as the name, type, date, last change, and status (e.g., deleted, imported, exported) of each item, as well as information on what other items are used by or use the current item. Additionally, it includes a full change history for each extensibility item.

Best Practices:

- Use key user extensibility for quick, simple extensions.

- Ensure key users are familiar with the business processes to maximize efficiency.

On-Stack/Developer Extensibility

On-stack/developer extensibility is designed for professional ABAP developers who need to create extensions closely integrated with the SAP S/4HANA Cloud public edition. Utilizing the SAP S/4HANA Cloud ABAP Environment and standard ADT tools, it allows for the development of cloud-ready, upgrade-stable custom ABAP code. This method combines the benefits of custom ABAP code with the necessary constraints for Cloud readiness and follows the SAP S/4HANA programming model for building SAP Fiori apps.

Category	Details
Key Features
1. RAP Model	ABAP RESTful Application Programming model for creating custom services and SAP Fiori apps.
2. Eclipse-based IDE	ABAP Development Tools with debugging, troubleshooting, and testing support.
3. Software Lifecycle Management	ABAP software lifecycle management.
4. SAP Business Application Studio	SAP Business Application Studio with SAP Fiori tools for developing custom Fiori apps.
Best Practices
1. Cloud-Optimized ABAP	Use a cloud-optimized subset of the ABAP language.
2. SAP APIs and Objects, Business Object Interface	Utilize released SAP APIs and objects in custom code.
3. Extension Points, Business Add-Ins	Employ predefined extension points to extend SAP objects.
4. Controlled Access Guidelines	Follow controlled access guidelines for admin, user, authorization, monitoring tools, and services.
5. Custom Table Security	Custom table creation lacks default security measures and cannot use ILM (Information Lifecycle Management) or IRF (Information Retrieval Framework).
6. Security and Compliance Tools	No tool support for ensuring security and compliance of custom code when developing SAP Fiori apps through SAP Business Application Studio and SAP Fiori tools.

Side-by-Side Extensibility

Side-by-side extensibility lets you build custom applications or extend existing ones, using the SAP Business Technology Platform (BTP). This approach enables loosely coupled, seamlessly integrated extensions that operate independently of SAP S/4HANA Cloud's lifecycle. On SAP BTP, you can develop using your preferred runtime or language, such as ABAP, Java, or Node.js.

SAP Business Application Studio is a development environment that supports the creation and management of custom applications on SAP Business Technology Platform (BTP). It is designed to streamline the development of extensions and applications, offering a user-friendly interface and integrated tools for building, and deploying solutions.

The SAP Cloud Application Programming Model (CAP) is a comprehensive framework designed to simplify the development of cloud-native applications within SAP Business Technology Platform (BTP). SAP CAP streamlines the development of sophisticated cloud applications, enabling developers to build robust, scalable, and secure solutions that integrate seamlessly with SAP S/4HANA and other SAP systems (https://cap.cloud.sap/docs/).

You can connect your extensions to SAP S/4HANA Cloud data using remote APIs or events, which are available on the SAP Business Accelerator Hub. For more details, see the APIs and Events sections on the SAP Business Accelerator Hub.

You can extend existing processes or create new processes while easily combining SAP S/4HANA Cloud data with data from other systems. Here are a few typical extension archetypes:

Proxy Applications: These are intermediary applications designed to facilitate communication between SAP S/4HANA and other external systems. For example, a proxy application might be used to sync data between SAP S/4HANA and a third-party CRM system, ensuring that customer information is consistent across platforms. By acting as a bridge, proxy applications enable seamless integration without modifying the core ERP system.

Convenience Applications: These applications enhance the user experience by providing additional features or functionalities that are not available in the standard SAP S/4HANA Cloud environment. For instance, a convenience application might offer specialized dashboards or widgets that simplify complex workflows or provide quick access to frequently used tools, improving productivity and user satisfaction.

Substitute Applications: Substitute applications replace existing standard processes with customized versions that better meet specific business needs. For example, if the standard SAP S/4HANA process for order management does not fully align with a company’s unique requirements, a substitute application can be developed to introduce alternative workflows or functionalities, ensuring that the solution fits the business's exact needs.

Preprocessing Applications: These applications handle data before it is processed by SAP S/4HANA. They might be used to clean, transform, or enrich data coming from various sources before it enters the core system. For instance, a preprocessing application could validate and standardize data from external suppliers before it is imported into the SAP system, ensuring data quality and consistency.

Postprocessing Applications: After data has been processed by SAP S/4HANA, postprocessing applications perform additional tasks such as generating reports, conducting analysis, or integrating processed data with other systems. For example, a postprocessing application might create custom analytics reports based on transaction data processed by SAP S/4HANA, providing insights that are not available through standard reporting tools.

Analytical Applications: These applications are used to perform advanced data analysis and generate insights from SAP S/4HANA data. They leverage tools like SAP Analytics Cloud to provide in-depth reporting, predictive analytics, and data visualizations. For instance, an analytical application might analyse sales data to identify trends and forecast future performance, helping businesses make informed decisions.

Build Applications: These are custom applications developed using SAP’s development tools and platforms, such as SAP Business Technology Platform (BTP). Build applications are tailored to specific business requirements and can interact with SAP S/4HANA data and processes. For example, a build application might be developed to manage a unique business process that is not covered by the standard SAP S/4HANA functionalities.

Custom Forms: These are personalized forms designed to collect and present data in a way that meets specific business requirements. Custom forms can be used for various purposes, such as generating tailored invoices, creating specialized order forms, or capturing unique data fields. By customizing forms, organizations can ensure that all necessary information is collected and processed according to their specific needs.

Gate Entry Applications: These applications manage the entry and exit of goods or personnel through designated checkpoints. For instance, a gate entry application might be used to track the arrival and departure of inventory at a warehouse, ensuring accurate records of goods movement and facilitating efficient logistics operations. These applications help in maintaining operational efficiency and compliance with inventory management practices.

These use cases illustrate the flexibility and adaptability of side-by-side extensibility in SAP S/4HANA Public Cloud Edition, allowing organizations to tailor their ERP system to meet unique business needs while maintaining a clean and stable core. Below are few more of the possible use cases via side-by-side extensibility:

Use Case	Description	Technologies & Tools	Integration Points	Deployment
Custom UI on SAP Business Technology Platform	Custom Fiori UI built with SAP Business Application Studio (BAS) or SAP Web IDE, running on SAP Business Technology Platform. Uses SAP predefined OData service.	UI5 technology, UI5 templates, editors, and testing capabilities.	Integrates using SAP predefined OData service.	Deploy to SAP Business Technology Platform account or SAPUI5 ABAP repository.
SAP Business Technology Platform Application	Application (Java, JavaScript, HANA) running on SAP Business Technology Platform with SAP predefined OData service.	Open standards, partner ecosystem contributions.	Integration scenarios with cloud integration; use SAP prepackaged integration content as reference templates.	Deploy and integrate within SAP Business Technology Platform.
Custom UI on SAP Business Technology Platform or SAP Business Technology Platform App with Custom OData Service	Custom UI or app with custom OData service built with In-App extensibility tools.	UI5 technology or custom development tools; In-App extensibility tools for custom OData services.	Integrates using custom OData service.	Deploy to SAP Business Technology Platform.
New SAP Business Technology Platform Service Called from SAP S/4 Extension	SAP S/4HANA, Success Factors, and SAP C/4HANA can fire business events to call apps on SAP Business Technology Platform.	Business event framework for SAP S/4HANA, Success Factors, SAP C/4HANA.	Uses business events to trigger actions on SAP Business Technology Platform.	The service is called from SAP S/4HANA or related SAP products.
Analytics on SAP Business Technology Platform (Replication)	Data replication from SAP S/4HANA, Success Factors, and SAP C/4HANA for analytics purposes on SAP Business Technology Platform.	Data replication tools, SAP Business Technology Platform analytics capabilities.	Data replication for analytics; integrates with SAP Business Technology Platform.	Data is replicated for analysis and reporting within SAP Business Technology Platform.

Best Practices:

- Use side-by-side extensibility for loosely coupled scenarios.

- Ensure seamless integration using SAP API Business Hub.

The below table details out the best practice for approaching extensibility in reference to SAP S/4 HANA, Public Cloud edition.

Best Practice	Explanation
Core Clean	Avoid modifying the core system to ensure smooth upgrades and maintain system integrity, hence using the extensibility points and approached detailed by SAP ensures they are always cloud ready and upgrade stable.
Use Standard APIs	Leverage SAP's provided APIs to ensure compatibility and reduce future maintenance efforts. Use SAP Business Accelerator Hub to explore and identify the best suited API for your use case.
Scenario based approach to Extensibility	Primary preference to be given to Key User and Development Extensibility within the SAP S/4HANA Cloud Public and opt for Opt for side-by-side extensions to separate custom logic from core processes, enhancing flexibility.
Consider User Needs	Always keep the end-user in mind to ensure customizations add real value and improve usability.
Documentation and Governance	Maintain thorough documentation and follow governance processes to ensure transparency and control.

Selecting the appropriate extensibility approach for SAP S/4HANA Cloud Public Edition, hinges on the specific use case, the expertise of the team involved, and the extent of integration needed with the core system. By adhering to best practices and utilizing the right tools, businesses can attain flexibility while preserving the integrity of their SAP environment.

References:

Extensibility https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/533228e1e854433ab16d013f161ca509.html?&version=2402.503
SAP S/4HANA Extensibility – Simplified Guide for Beginners SAP S/4HANA Extensibility – Simplified Guide for B... - SAP Community
SAP Extensibility Explorer for SAP S/4HANA Cloud (ondemand.com)
Extend SAP S/4HANA in the cloud and on premise with ABAP based extensions

Research & Development Engineering in SAP S/4HANA Cloud Public Edition 2408

2024-08-15T15:24:11.397000+02:00

I am happy to share the Research & Development Engineering innovations for SAP S/4HANA Cloud Public Edition 2408 release. Let's start with the highlight overview video:

Now let's shift to the details and start with an important innovation in SAP Product Lifecycle Management integration with SAP S/4HANA Cloud.

SAP Product Lifecycle Management Solution Integration with SAP S/4HANA Cloud

Before we go into the details, let's look at the overall strategy:

From a strategic point of view, we simplified into two scope items 6U3 (integration through SAP PLM) and 6U2 (Integration external PLM systems). With 2408 we enhanced the 6U3 process with the SAP Product Lifecycle Management Solution Integration with SAP S/4HANA Cloud Public Edition.

With SAP Product Lifecycle Management solution, you can seamlessly transfer engineering bills of material (EBOMs) from the SAP Product Lifecycle Management solution and continue to work on them as manufacturing bills of material (MBOMs) in the relevant Maintain Bill of Material (Version 2) app. To allow you to transfer the BOMs and monitor the process, the following apps are now available on the SAP S/4HANA Cloud Launchpad:

Configure Handovers

In the Configure Handovers app the following attributes are defined. First the BOM Usages are configured for the handover process:

Then the Item Categories are defined:

In SAP S/4HANA Cloud, Public Edition we have already standard defined item categories.

Last, but not least, the plants are configured for the handover process. The plant is configured to define at which plant you want to manufacture your product or how the target BOM is to be used:

Hand Over Engineering Bills of Material (EBOM)

In the Hand Over Engineering Bills of Material (EBOM) the magic happens. In the main screen of the Fiori app the SAP S/4HANA BOMs are visible as well as the SAP PLM BOMs:

When going into the details (object page), you may see the Source BOM and the Target BOM:

Interesting for you is that the Routing has been integrated:

By selecting the component in the BOM you can view the routing:

A new routing can also be assigned:

Actions can be taken on the Source BOM side:

As well as on the Target BOM side:

You may also add 3D models and pictures as well:

Changes can be seen in the Log:

Messages or Monitoring can be seen here:

By clicking on the Show Details, you will jump into the Task Monitoring for Handovers app. This will be explained next.

Task Monitoring for Handovers

The Task Monitoring for Handovers app monitors the handover process from SAP PLM to SAP S/4HANA Cloud Public Edition:

In the object page, you may monitor further details:

SAP PLM Integration to SAP S/4HANA Cloud Public Edition Demo

The following shows a short demo for the SAP PLM to SAP S/4HANA Cloud Public Edition integration process:

Click on this link for further onboarding and also check out this user guide.

New App in BOM Management: Maintain Bills of Material (Version 2)

With this new app (F1813A), you can create, update, or delete BOMs.

This app is a successor to the Maintain Bill of Material (F1813) app. In this old app, the copy from EBOM to MBOM happened with the button "Handover to Manufacturing".

This can be done in the new app with the "Copy BOM" button:

The real "Handover" process may be done via SAP PLM as described above in this blog post, or also with external PLM systems via scope item 6U2

Maintain Subitems in Manage Order Bill of Material (Version 2) App

This feature enables you to create, update, or delete subitems for a BOM.

The maintenance of the subitems quantity is integrated with the BOM components.

New App in BOM Management: Maintain WBS Bills of Material

With this app, you can create, update, or delete work breakdown structure (WBS) BOM.

You may work on an engineer-to-order scenario with projects. A project can have several work breakdown structure (WBS) elements that are nothing, but steps or different requirements involved in conceptualizing a finished product. Several activities that belong together can be grouped into WBS elements. You can create WBS BOMs for each of these WBS elements and carry out project-specific modifications.

Usability Feature in Manage Multilevel Bill of Material App

This feature enables you to copy and paste BOM item data from one BOM assembly to another thus reducing the tedious task of recreating the same BOM item data.

Manage Change Record (Version 2) App

Manage Change Record (Version 2) app is the successor of the Manage Change Record app.

It provides continuous enhancement opportunities, improved performance, better usability, and supports Flexible Workflow only.

It is recommended to use Manage Change Records (Version 2), as it is the successor of Manage Change Records. It is more simplified and supports the following objects:

Bill of Material (BOM)
Document (DOC)
Materials (MAT)
Production Routings (PRG)
Class (CLS)
Characteristic (CHR)
Sales Order Bill of Material (OBM)

Flexible Workflow

Flexible workflow allows businesses to run the Change Management process with transparency while taking appropriate decisions as you may check and approve process changes in a Change Record.

A new workflow can be created, or an existing one can be copied and edited to create a new one with the Workflows for Change Record app.

Don’t hesitate to leave a comment and check out our community page to ask your questions and engage with the experts. Follow the PSCC_Enablement tag to stay up to date with our latest blog posts.

📽️ Watch the Replays of Our SAP S/4HANA Cloud Public Edition 2408 Early Release Series!

From July 8 to July 12, we hosted a series of 20 compelling live sessions to highlight the exciting innovations shipped with the SAP S/4HANA Cloud Public Edition 2408 release. Missed the live sessions? We've got you covered! Don't miss this chance and watch them on demand–anywhere, anytime.

🔎Find All of Our Assets

SAP S/4HANA Cloud is the foundation of the intelligent, sustainable enterprise and is an innovative, robust, and scalable ERP. We at Cloud ERP Product Success and Cloud Co-Innovation offer a service as versatile as our product itself. Check out the numerous offerings our team has created for you below:

Transportation Management for SAP S/4HANA Cloud Public Edition 2408

2024-08-15T15:27:40.087000+02:00

Exciting product updates coming your way for Transportation Management in SAP S/4HANA Cloud Public Edition 2408.

Integration of Returns Purchase Orders with
Transportation Management

With this feature you can integrate returns purchase orders with Transportation Management. This allows you to perform transportation planning, monitor the execution, and settle the freight costs for a returns purchase order as part of the Return to Supplier process (scope item BMK).

Configuration

You need to configure the integration of returns purchase orders with Transportation Management using the following configuration activities:

Define Logistics Integration Profile
For returns purchase orders, you must create a logistics integration profile. To do this, you can copy an existing logistics integration profile, such as S003 (manual planning) or S004 (external planning), and adapt it as required.
Define Transportation-Relevance of Purchasing Documents
You activate the integration of returns purchase orders into TM by assigning the control key 0058 and the logistics integration profile that you created in the Define Logistics Integration Profile activity to a combination of the required purchasing organization, and purchasing group.

Currently Transportation management for returns purchase orders is not integrated with Warehouse Management.

Integration of Returns Purchase Orders with
Transportation Management - Demo

Check out this short demo featuring the configuration steps and the process from our Early Release Webinar 2408:

Delivery Deletion Initiated from Transportation Management

You can delete inbound, outbound, and customer returns deliveries in Logistics Execution (LE) from the Manage Freight Units app in Transportation Management (TM).

If a freight unit has been assigned to a freight order or freight booking, you must remove this assignment before you can delete the delivery.

Enhancements for Consignment Orders in the
Outbound Process

With this feature, you can benefit from an improved handling of consignment orders and consignment order documents in the outbound process.

In particular, the following improvements have been made:

Execution status as an indicator for creating and deleting consignment order documents

The execution status of a freight order now clearly indicates if a consignment order document is created or has been created for the local consignment items of the freight order:

When the execution status of the freight order is set to Ready for Transportation Execution, the system automatically creates a corresponding consignment order document for each of the local consignment orders. These business documents can be accessed from the Document Flow tab or the Items tab of the freight order.
When you add freight units to the freight order after the execution status Ready for Transportation Execution has been reached, a consignment order document is created by the system for these freight units.
When you change back the execution status of the freight order from Ready for Transportation Execution to Not Ready for Transportation Execution, the system deletes the consignment order document, and the consignment order exists again only locally in the freight order.

No further changes allowed after sending of ASN or checkout of freight order

When an advanced shipping notification (ASN) has been sent or when the freight order has been checked out at the source location (checkout status value of handling execution status has been set), you can't unassign freight units from the consignment order or cancel the consignment order document anymore. To be able to do so, you must first undo the goods issue for the corresponding delivery and revoke the checkout.

Deletion of the consignment order after removal of assignment to freight order

If you unassign a consignment order from a freight order, the freight units are automatically unassigned from the consignment order and the consignment order is deleted. If the freight units are replanned to the freight order later, the system creates a new consignment order document for them.

Freight Cost Calculation based on Material Freight Group and Transportation Group

With this feature, you can calculate transportation charges in a freight order or freight booking based on a material freight group and transportation group.

Maintain freight rates based on the material freight group and transportation group in the freight agreement during negotiations with the carrier. Also, consider the material freight group and transportation group for the respective freight documents in the freight cost calculation after creation of freight agreement.

Billing of Freight Cost for Batch-Managed Material

For transportation management scenarios that are initiated from a sales document, the freight cost of the freight document can be taken into account when the corresponding billing document is created. This functionality is also available for batch-managed materials now.

Refinement of Freight Settlement Initiation for Advanced Intercompany Processes

Freight order does not contain an "own" location [e.g. in advanced intercompany sales scenario with (internal) incoterm CIF, where the freight order of the selling organization relates to the transport from port of destination to the customer location].

Freight orders automatically qualify for freight cost confirmation and settlement process as soon as the departure from the source location of relevant stage is reported.

Enhancement of the Form Data Provider for the WAYBILL Output Type

The Form Data Provider of the Output Type ‘WAYBILL’ was extended with details on the Shipper’s Contact and Container Number.

Form Data provider for the WayBill Output Type is extended with the following attributes:

Container Details:
Container Number
Container Country/Region
Shipper Contact Number
Shipper’s E-mail
Shipper’s Phone
Shipper’s Mobile Phone
Shipper’s Fax

Third-Party Warehouse Management with Transportation Management - Advanced Integration Scenario

Support integrated logistics processes with a third-party warehouse management system (Scope Item 1ZQ) and transportation planning and execution (Scope Items 6W1, 6W2, 6W3).

The improvements:

Ability to distribute outbound or inbound deliveries that are integrated with transportation management to a connected, third-party warehouse management system.
Subsequent changes to deliveries after they were distributed to the third-party warehouse management system.

Warehouse Outbound Processing with External Transportation Planning - Advanced Integration Scenario

Support integrated logistics processes with Warehouse Management (Scope Item 3BS) and transportation planning in an external Transportation Management System (Scope Item 6W1).

The following was enhanced:

Enable integration with Warehouse Management, if freight units are distributed and planned in a connected external transportation management system.

Task Tutorials + Learning Content for Transportation Management with 2408 Release

New task tutorials and updated learnings to showcase an end-to-end scenario in Transportation Management for SAP S/4HANA Cloud Public Edition. Check them out:

Don’t hesitate to leave a comment and check out our community page to ask your questions and engage with the experts. Follow the PSCC_Enablement tag to stay up to date with our latest blog posts.

📽️ Watch the Replays of Our SAP S/4HANA Cloud Public Edition 2408 Early Release Series!

🔎Find All of Our Assets

Key User Extensibility and Developer Extensibility for Carbon Footprint Category Breakdown

2024-08-16T13:29:39.951000+02:00

#saveThePlanet requires drilling into the details: Carbon Footprint Category Breakdown is released. Read my Blog article on how to extend your applications easily with Key User and Developer Extensibility for #SAPS4HANA

Introduction

SAP S/4HANA provides features that allow to extend existing applications with carbon footprint data. Our team’s previous Blog post described how to extend existing applications with carbon footprints, on the example of Manage Purchase Order. This is meanwhile standard functionality of Purchase Requisition and Purchase Order in current SAP S/4HANA releases. Nevertheless, the Blog post is still relevant for on premises installations not yet on the newest release and furthermore also for applications not yet enabled with footprints.

Today we bring it to the next level with our latest SAP S/4HANA Cloud 2408 release which includes the latest Sustainability Integration Component. It is enabled by Scope Item 5IM “Product Footprint Management” since several years, specifically since SAP S/4HANA Cloud 2108 and SAP S/4HANA 2021. We introduced new CDS views as listed here including:

List of greenhouse gas scopes I_GHGScope.
A GHG scope defines where emissions come from, e.g. from your own factory, your suppliers, or your consumers to name some examples from Scope 1, 2 and 3.
List of greenhouse gas categories I_GHGCategory.
A GHG category further subdivides the greenhouse gas scopes, for example Scope 3 into category 3.06 “business travel”, 3.12 “end-of-life treatment of sold products” etc.
Master Data Footprint Breakdown by GHG Category I_CO2eqFprntAvgGHGCat.
This one is best explained stepwise:
- SAP S/4HANA contains master data records, specifying for example a product from a plant, or a product from a plant delivered by a specific supplier.
- The master data footprint is a record that relates to an existing master data record. It adds footprint information to this master data record.
- The Breakdown by GHG Category splits the master data footprint into quantity components per GHG category.
Transactional Data Footprint Breakdown by GHG Category I_PFMTransDataCO2eqFprntGHGCat. The transactional data footprint is related to a transactional data record. For example, it computes the overall CO2e sum for a given purchase order for the sum of the list of items ordered.

Prerequisites

Learning Recommendation

For an introduction into the topic of footprints, see the training Climate Action with SAP Sustainability Footprint Management. It starts with an overview of Climate Action offerings by SAP and then focuses on SAP Sustainability Footprint Management hands-on and explains master data, transactional data, footprint computation etc.

Before you continue with the content below, I recommend making yourself familiar with Key User Extensibility and Developer Extensibility if you are not familiar already. I recommend Learning Journey “Practicing Clean Core Extensibility For SAP S/4HANA Cloud”, especially the chapters

User Roles

Make sure you have the following business roles assigned in your system:

SAP_UI_FLEX_KEY_USER
SAP_BR_PURCHASER
SAP_BR_EXTENSIBILITY_SPEC
SAP_BR_ADMIN_SUS_PFM

Key User Extensibility

Create Custom Field to Display the CO2e Category Breakdown in Your Purchase Requisition Item

Custom Fields is a tool for Key User Extensibility. Using this tool, a key user can create and edit custom fields for SAP tables, Core Data Service (CDS) views or OData services and expose them to the UI.

I now extend Purchase Requisition Item. It already shows the CO2e footprint, and I additionally insert GHG category breakdown by adding a Custom Field. The steps required are:

Select Adapt UI from your profile icon menu top right.
Select Create Custom Fields
The list of Custom Fields is pre-filtered with the Business Context for Purchase Requisition Item, as you can see below. Create your new field here of Field Type: Text. Select something meaningful for label and identifier. The Business Context is prefilled with: Procurement: Purchase Requisition Item (MM_PURREQN_ITEM). The result should look like the screenshot below.
Position the newly created field to the place you want it to be. In the screenshot below I dragged it into the General Information section.

Create Custom Logic

As you saw in step 3 in the screenshot above, the category breakdown is placed now in the UI, but it does not yet show any value. Now I add the logic to define the text value. Go to application Custom Logic, add a new implementation in the Business Context and Extension Point as shown in the screenshot below.

For the code, you can take the example below as a first draft. It composes the text for the GHG breakdown by calling our Calculation API, looping through the returned components, and doing basic error handling. It is good practice to limit the code to your user at first to try things out without interfering with others, adapt this in line 1 before you proceed.

IF purchaserequisitionitem-createdbyuser = 'CB9980004180'. "Martin Knechtel
    " get footprint calculation API
    TRY.
        purchaserequisitionitemchange-yy1_mk_pr_co2category_pri = 'CO2e category breakdown coming from my Key User Extensibility'. "our custom field receives a first initial assignment, helps you debugging
        CATCH cx_sy_conversion_overflow.
            INSERT VALUE #(
                messageid        = 'MEPO'
                messagetype      = 'E'
                messagenumber    = 250
                messagevariable1 = 'CO2e category breakdown exceeds size of Custom Field.'
            ) INTO TABLE messages.
    ENDTRY.
    TRY.
        DATA(lo_calculation_api) = cl_supfm_tdfp_calc_api_factory=>get_factory( )->get_calculation_api( ).
        CATCH cx_supfm_tdfp_calc_api_factory INTO DATA(lx_supfm_tdfp_calc_api_factory).
            INSERT VALUE #(
              messageid        = 'MEPO'
              messagetype      = 'E'
              messagenumber    = 250
              messagevariable1 = lx_supfm_tdfp_calc_api_factory->get_text( )
            ) INTO TABLE messages.
            RETURN.
    ENDTRY.
    TRY.
        " calculate the CO2e Footprint for the purchase requisition item
        DATA(ls_calculation_result_ghg) = lo_calculation_api->calculate_ghg_with_log(
                      VALUE #( ( 
Product       = purchaserequisitionitem-material "e.g. 'BUTTER100'
Plant         = purchaserequisitionitem-plant    "e.g. '1010' 
Quantity      = purchaserequisitionitem-orderedquantity "e.g. '3'
UnitOfMeasure = purchaserequisitionitem-purchaseorderquantityunit "e.g. 'KG'
                               ) ) ).

      " in case a footprint for the item was successfully calculated, loop over the components
      DATA responseString TYPE string.
      IF ls_calculation_result_ghg-has_result = abap_true.
          LOOP AT ls_calculation_result_ghg-pfmfootprintcomponents REFERENCE INTO DATA(component).
            DATA(quantityRounded) = round( val = component->pfmfootprintquantity
                                           dec = 3 ).
            responsestring = |{ responsestring }{ component->pfmfootprintqtycomponenttype }: { quantityRounded } { component->pfmfootprintunit } /  |.
          ENDLOOP.
      ELSE.
        responsestring = |No CO2e scope categories found. Log: { ls_calculation_result_ghg-calculation_log->get_calculation_log_json(  ) } Input: | &&
            |{ purchaserequisitionitem-material },{ purchaserequisitionitem-plant },{ purchaserequisitionitem-orderedquantity },{ purchaserequisitionitem-purchaseorderquantityunit }|.
      ENDIF.
      responsestring = |{ responsestring } at { cl_abap_context_info=>get_system_date(  ) }{ cl_abap_context_info=>get_system_time(  ) }|.
      purchaserequisitionitemchange-yy1_mk_pr_co2category_pri = responsestring.
    CATCH cx_supfm_tdfp_calc_api INTO DATA(lx_supfm_tdfp_calc_api).
      INSERT VALUE #(
        messageid        = 'MEPO'
        messagetype      = 'E'
        messagenumber    = 250
        messagevariable1 = lx_supfm_tdfp_calc_api->get_text( )
      ) INTO TABLE messages.
    ENDTRY.
ENDIF.

Returning to your Purchase Requisition Item you should now see the CO2e category breakdown similarly to the screenshot below.

Developer Extensibility

Above I introduced Custom Logic for the ABAP code to prepare your text to be shown in the UI. This was done with Key User Extensibility tools. Now I switch into Developer Extensibilty. Preparing code with ADT is more comfortable if the Custom Logic above gets extensive. Debugging is possible. You can also encapsulate part of the logic and call it from the extension point Custom Logic above. An example is shown in the screenshot below. Similarly to the code example above, it calculates a transaction data footprint from a master data footprint and prepares the calculated GHG component breakdown to a string. Here it prints it to the console, but I could also assign it to some custom field, as shown above.

In case there is no master data footprint found for the given product “BUTTER100”, an error with message number 4 is returned. As shown in the screenshot, the CM_SUPFM_TDFP_LOGGER message class was opened to retrieve the message text from the message number. This might indicate to the developer that no test data was created yet on the system and afterwards he can proceed debugging and developing. With that, I walked you through an end to end example for extending your application with sustainability features with Key User Extensibility and Developer Extensibility.

Disclaimer: I describe the work of many here and I am only one of the contributors in a great and dedicated team. We keep on rocking to deliver you the latest and greatest sustainability integration into SAP S/4HANA.

使用Availability Check Horizon来管理ATP

2024-08-19T08:11:18.493000+02:00

业务需求

客户每日通过集成创建销售订单，但这些销售订单并不急着创建交货单，客户希望这些订单不要占用ATP库存。

我们可以启用Availability Check Horizon来实现。

系统配置

1.配置SSCUI：Configure Scope of Availability Check, ID:101099，选择对应的配置Availible Check + Checking Rule

选择Full Confirmation

配置里的Availale Check SR对应的是产品主数据MRP3视图里的配置

2.APP：Manage Product Master Data（注意：必须是Fiori APP并不是MM02），工厂视图下添加Availibility Check Horizon的天数

设置200天

系统实现

产品ZFC105库存100件，对订单1741，订单数量200件设置交货日期晚于200天后，比如：

对后续新销售订单需求70件，可以看到ATP可以被完全满足，并不受上一张订单数量200件占用库存。

感谢观看

ビジネスコンテンツ「 Finance Foundation for SAP S/4HANA and S/4HANA Cloud」を実装してみよう！

2024-08-19T08:14:32.018000+02:00

はじめに

こちらのブログでは「Finance Foundation for SAP S/4HANA and S/4HANA Cloud」のビジネスコンテンツの実装手順を解説します。ビジネスコンテンツの概要に関しては「SAP Datashere ビジネスコンテンツ概要とインストール手順」をご確認ください。

「Finance Foundation for SAP S/4HANA and S/4HANA Cloud」のビジネスコンテンツではSAP S/4HANA あるいはSAP S/4HANA Cloud をデータソースとした財務報告・分析のベースとして利用できるデータモデル、およびサンプルダッシュボードを併せて提供しています。データモデルにはG/L勘定科目、実績/計画仕訳項目、会計伝票や仕訳明細のオペレーショナルデータ、および対応するマスターデータが含まれており、テンプレートとしてそのまま使うだけでなく、独自にカスタマイズを行いテンプレートの拡張を行うことも可能です。

以下は本ビジネスコンテンツの構成図です。

ビジネスコンテンツはSAPのモデリングベストプラクティスに則って、項目の絞り込みを行ったうえで集計や結合、階層の追加などの処理がされ、それらを基にSAP Analytics Cloudで使用するモデルが作成される構成をとっています。これらが以下のように３つのレイヤーに分けられ、テーブルやビュー、分析モデルとしてSAP Datasphereのビジネスコンテンツに含まれています。

本ブログではSAP S/4HANA Cloudをデータソースとした実装方法をご紹介します。　

リモートテーブルの作成が必要なため、DP Agentをお客様環境にインストールをする必要があります。DP Agentの設定方法に関しては「SAP S/4HANAとSAP Datasphereのデータ連携 : DP Agentの設定」をご確認ください。
SAP S/4HANA Cloudとの接続作成が必要となり、2つの通信シナリオ（SAP_COM_0531およびSAP_COM_0532）を割り当てた通信契約の作成が必要です。詳細は「SAP S/4HANA CloudとSAP Datasphereのデータ連携」をご確認ください。

本ブログでは以下を前提としています。バージョンの相違にご注意ください。

バージョン情報：

SAP S/4HANA Cloud:2402
SAP Datasphere: 2024.14.48
DP Agent: 2.7.3.3

手順

以下が主な手順です。本ブログではSAP S/4HANA Cloud, SAP Datasphere, SAP Analytics Cloudと手順を分けてご紹介いたします。

SAP S/4HANA Cloudでの手順

こちらでは以下を行います。

通信ユーザ作成
通信システム作成
通信契約作成
セマンティックタグの割り当て

本ビジネスコンテンツではSAP S/4HANA Cloudの接続タイプを指定されているため、接続作成のためにSAP_COM_0531およびSAP_COM_0532の２つの通信シナリオを有効にする必要があります。

手順１～３の詳細の手順は「SAP S/4HANA CloudとSAP Datasphereのデータ連携」ブログで紹介されていますのでご確認ください。

4. セマンティックタグの割り当て

本ブログでは「グローバル階層管理」アプリを用いたセマンティックタグの割り当て方法を解説します。こちらのSAP Note「3219638 - セマンティックタグの割当方法」も併せてご確認ください。

まずはじめに「グローバル階層管理」アプリより有効な既存の財務諸表バージョンの検索およびセマンティックタグの割り当てをおこないます。

セマンティックタグの割り当てを行うには、はじめに階層の「無効化」をしてから「編集」をおこなう必要があります。

割り当てが必要なセマンティックタグはこちらのSAP Help Portalに記載されており、該当するものを対応するノードに割り当てます。

グローバル階層管理アプリでセマンティックタグの割り当てを行う際は、適切な階層のノードを開き、タグのアイコンを選択すると「選択：セマンティックタグ入力ヘルプ」メニューが新たなウィンドウで表示されます。

検索あるいはスクロールダウンで使用するものを選択し、「OK」で割り当てを行うことができます。

必要なセマンティックタグの割り当てが終了すると右下の「保存」を選択します。

分析レポートなどの実行時アプリケーションでは、有効な階層バージョンのみ使用することができるため、セマンティックの割り当て終了後は財務諸表バージョンの「有効化」を行う必要があります。

詳細は「グローバル階層管理」のSAP Help Portalをご確認ください。

SAP Datasphereの手順

こちらでは以下を行います。

ビジネスコンテンツのインポート
SAP S/4HANA Cloudとの接続作成
ローカルテーブルのデータ型変更
複製フロー・データフローの作成・実行
ビュー・分析モデルのデプロイ

ビジネスコンテンツのインポート

SAP Datasphereにログイン後、「セマンティックオンボーディング」メニューよりビジネスコンテンツのインポートを行います。

ソースシステムとの接続名はビジネスコンテンツ毎に指定されており、本ビジネスコンテンツで定められている名称は以下の通りです。

ビジネス名：　SAP S/4HANA Cloud
技術名：　SAP_S4HC

SAP S/4HANA Cloudとの接続作成

「接続」メニューよりSAP S/4HANA Cloudとの接続の「作成」を行います。

接続タイプは「SAP S/4HANA Cloud」を選択します。

接続プロパティや接続名称を設定し、「接続を作成」します。

作成した接続が有効かどうかは以下のように確認ができます。

ローカルテーブルのデータ型変更

SAP S/4HANA Cloudのデータをビジネスコンテンツに含まれるローカルテーブルに挿入する前に以下の3つのローカルテーブルの日付のデータ型を確認してください。

CDS View	Local Table
I_FISCALYEARFORCOMPANYCODE	SAP_FI_IL_I_FISCALYEARFORCOMPANYCODE
I_OPERATIONALACCTGDOCITEM	SAP_FI_IL_I_OPERATIONALACCTGDOCITEM
I_SemTagGLAccount	SAP_FI_IL_I_SemTagGLAccount

ターゲットテーブルの該当する日付のデータ型がStringになっている場合はDateへと変更し、テーブルのデプロイを実行します。

↑データ型の変更前↑データ型の変更後

複製フローの作成

「ビジネスコンテンツのインポート」の際に作成されたローカルテーブルをターゲットとする複製フローを作成し、データの挿入をします。こちらのSAP Help Portalを参考に、CDS viewの選択およびターゲットオブジェクトの選択を行います。

この際の注意点として、ターゲットシステムの選択をするとターゲットオブジェクトが自動で選択されますが、SAP Help Portalで指定されているローカルテーブルをターゲットとして変更する必要があります。

作成した複製フローのデプロイおよび実行を「一般」メニューより行います。

データフローの作成

ビジネスコンテンツで使用するCDS viewの１つであるI_SemTagGLAccountは１次キーが設定されておらず、複製フローの作成が2024年7月時点ではサポートされていません。（ロードマップはこちらからご確認いただけ、2024年Q3での実装が予定されています。）

まずはじめにリモートテーブルを作成します。後続の手順は以下の2つの方法から１つを選択します。こちらのSAP Help Portalを確認ください。

選択肢①　リモートテーブルをソーステーブル、SAP_FI_IL_I_SemTagGLAccountをターゲットテーブルとしたデータフローの作成
選択肢②　SAP_FI_IL_ SemTagGLAccountをデータビルダで開き、ソーステーブルをリモートテーブルへと置換

選択肢①を選んだ場合は、作成したデータフローのデプロイおよび実行を「一般」メニューより行います。

ビュー・分析モデルのデプロイ

複製フロー・データフローのデプロイ・実行後にデータソース側からInbound Layer → Harmonization Layer→Reporting Layerの順でローカルテーブル、ビュー、分析モデルのデプロイをします。

SAP Analytics Cloudでの手順

ビジネスコンテンツのインポート
SAP Analytics Cloudとの接続作成
ストーリーの確認

ビジネスコンテンツのインポート

SAP Analytics Cloudにアクセス後、「コンテンツネットワーク」よりビジネスコンテンツのインポートを行います。

SAP Datasphereとの接続を作成します。

「接続」メニューより＋（接続の追加）を選択し、ライブデータに接続のドロップダウンメニューを開け「SAP Datasphere」を選択します。

ビジネスコンテンツにおけるSAP Datasphere - SAP Analytics Cloud間の連携は以下の接続名で固定されており、どのコンテンツでも使用することが出来ます。詳細はこちらのSAP Help Portalをご確認ください。

接続名：SAPDWC

ストーリーの確認

ビジネスコンテンツは「公開」フォルダ内に以下の名称でインポートされています。

SAP Finance: P&L Statement (based on SAP Datasphere)

また、ストーリーを表示する際にはプロンプトが表示されます。以下の３つの変数を入力する必要があります。

さいごに

最後までお読みいただきありがとうございました！

以下に参考としてSAP Help Portalや関連ブログのリンクを掲載しておりますので、併せてご確認ください。

ABAP Cloud Sessions at SAP TechEd in 2024

2024-08-20T20:42:55.415000+02:00

Hey Everyone!

That time of year is here again, SAP TechEd 2024 is just around the corner!

SAP TechEd is the leading tech conference for all developers, IT professionals, business experts, tech visionaries, innovators, and leaders eager to gain in-depth knowledge of SAP’s solutions, platforms, and technologies, along with insights into their future direction. It also offer an opportunity to network and connect with peers and SAP experts.

SAP TechEd in 2024 will kick off with a free, engaging virtual event accessible to everyone, followed by SAP TechEd on Tour stops all around the world for a unique opportunity for more in-depth, in-person learning experiences. The series of local on-site events will be organized in partnership with and hosted by SAP User Groups and SAPinsider. Learn more about the virtual experience here.

The choice is yours: Join us virtually for the first event in the series, SAP TechEd Virtual 2024!

📌Save the date and register now!
📅October 8 - 9, 2024

At this year's SAP TechEd, you will have the opportunity to attend a variety of sessions and formats - such as lectures, jumpstarts, and roadmaps - organized into six (6) content tracks that are aligned with your business needs, covering SAP technologies, products, and solutions:

Digital Transformation with Cloud ERP (DT)
SAP Business Technology Platform – General (XP)
Application Development and Automation (AD)
Data and Analytics (DA)
Integration (IN)
Artificial Intelligence (AI)

The ABAP sessions at this year's SAP TechEd event will be centered around "Clean Core Extensibility powered by ABAP Cloud and Generative AI". Attendees can look forward to a range of lectures (incl. roadmaps) and jump-starts on clean core development and transformation with ABAP Cloud and GenAI for all SAP S/4HANA editions, both cloud and on-premise. Below is an overview of the SAP TechEd Virtual 2024 sessions related to clean core extensibility and ABAP Cloud.

📚Access the full session catalog of SAP TechEd Virtual 2024

Keynotes

KEY100CEST & KEY100EDT | SAP TechEd in 2024 Launch - Where ideas get real
[Executive Keynote] At SAP TechEd, experts, developers, IT leaders, and our SAP Community gather to learn, share, and build together. Hear firsthand from SAP Board Members Juergen Mueller and Muhammad Alam how innovations in SAP Build solutions, SAP Business AI, SAP BTP, and other solutions across our end-to-end portfolio are revolutionizing the tech world.´
Speakers:
• Juergen Mueller, Chief Technology Officer, SAP
• Muhammad Alam, SAP Product Engineering, SAP
Schedule:
• 📅 Tuesday, Oct 8 | 🕛 9:00 AM - 10:30 AM CEST [KEY100CEST]
• 📅 Tuesday, Oct 8 | 🕛 4:00 PM - 5:30 PM CEST [KEY100EDT]

DEV101A & DEV101B | Keynote recap + Community welcome
[Developer Keynote] Join the Developer Advocates as they welcome the SAP Community to SAP TechEd, provide a short recap of the key announcements, and share insights into what it means for developers.
Speakers: Developer Advocates, SAP
Schedule:
• 📅Tuesday, Oct 8 | 🕛 10:30 AM - 10:55 AM CEST [DEV101A]
• 📅Tuesday, Oct 8 | 🕛 5:30 PM - 5:55 PM CEST [DEV101B]

DEV100A & DEV100B | Developer keynote [deconstructed]: Keeping the promise
[Developer Keynote Deconstructed] Hear from the developer advocates for a quick injection of news, recaps, and deep-dive demos covering various announcements from the event as well as other fun stuff.
Speakers: Developer Advocates, SAP
Schedule:
• 📅Tuesday, Oct 8 | 🕛3:30 PM - 3:55 PM CEST [DEV100A]
• 📅Tuesday, Oct 8 | 🕛9:00 PM - 9:25 PM CEST [DEV100B]

Track Overviews

AD100 – Unlock SAP Build and ABAP Cloud interoperability to elevate your extensions
[Track Overview, 45 min] Discover a new approach to building extensions while keeping your core clean. Learn how SAP Build and ABAP Cloud interoperability work together to foster fusion development. Whether you prefer pro-code or low-code tools, discover how to seamlessly integrate them to build extensions tailored to your needs. Learn from experts about best practices, innovative solutions, and practical applications that can enhance your development processes and drive business growth.
Speakers: Dr Alexander Rother (SAP), Thomas Volmering (SAP), Björn Schulz (REWE digital GmbH)
Schedule: 📅 Tuesday, Oct 8 | 🕛 6:00 PM - 6:45 PM CEST

DT100 – Unlocking the intelligent enterprise: Cloud ERP innovations for the future
[Track Overview, 45 min] Explore the future of cloud ERP, focusing on the latest innovations and strategies driving digital transformation. Delve into the technological backbone of SAP's vision for cloud ERP, covering in-app extensibility, integration with SAP Business Technology Platform, AI-powered automation, and the "suite-first" approach. Learn the benefits of a clean core and its role in enabling composability, empowering businesses to adapt and evolve, and get insights into this year’s cloud ERP track sessions.
Speakers: Jan Gilg (SAP)
Schedule: 📅 Tuesday, Oct 8 | 🕛 10:30 AM - 11:15 AM CEST

Lectures

📅Tuesday, Oct 8

AD105 – Enhance your fusion team collaboration with ABAP Cloud and SAP Build
[Lecture, 25 min] Learn how to take advantage of interoperability between SAP’s low-code and pro-code solutions. Discover how you can use the graphical modeler in the development environment of SAP Build Code for the ABAP Cloud development model and how your ABAP Cloud projects can be integrated into the lobby of SAP Build solutions.
Speakers: Dr. Anne Keller (SAP), Tim Back (SAP)
Schedule: 📅 Tuesday, Oct 8 | 🕛 7:00 PM - 7:25 PM CEST

AD107 – Boost your coding efficiency: Explore Joule’s ABAP Developer capabilities
[Lecture, 25 min] Discover Joule's ABAP developer capabilities. Hear about detailed use cases, the generative AI road map, and insights on how these advancements can boost your productivity as a developer in your daily tasks.
Speakers: Dr. Jasmin Gruschke (SAP), Sebastian Baskovich (SAP)
Schedule: 📅 Tuesday, Oct 8 | 🕛 7:30 PM - 7:55 PM CEST

📅Wednesday, Oct 9

AD106 – Clean core extension of SAP S/4HANA with the latest ABAP Cloud features
[Lecture, 25 min] ABAP Cloud is the comprehensive development model for building cloud-ready business applications, services, and extensions on both SAP Business Technology Platform, SAP S/4HANA Cloud, and SAP S/4HANA, helping ensure clean core compliance by definition. Learn about the latest features offered in ABAP Cloud and how generative AI can boost the development efficiency.
Speaker: Volker Drees (SAP)
Schedule: 📅 Wednesday, Oct 9 | 🕛 7:00 PM - 7:25 PM CEST

DT201 – Extensibility for SAP S/4HANA Cloud Public Edition
[Lecture, 25 min] The extensibility portfolio for SAP S/4HANA Cloud Public Edition consist both on-stack and side-by-side extension techniques. In this lecture you will learn how on-stack key user extensibility can be used to develop a custom business object together with an application in SAP Build Apps.
Speaker: Dr. Thomas Schneider (SAP), Alda Dollani (SAP)
Schedule: 📅 Wednesday, Oct 9 | 🕛 2:30 PM - 2:55 PM CEST

DT200 – Clean Core Extensibility for SAP S/4HANA Cloud Private Edition
[Lecture, 25 min] Learn how to manage your custom, on-stack extensions in SAP S/4HANA Cloud Private Edition with the ABAP Cloud development model following clean core principles. Find out about the new guidelines for clean core ABAP development in a well-known, three-tier extensibility model and how to handle transformation options for existing custom code to ABAP Cloud. Get an outlook of upcoming generative AI support and hear our plans for ABAP test cockpit to support governance of your clean core developments.
Speaker: Olga Dolinskaja (SAP), Thomas Fiedler (SAP)
Schedule: 📅 Wednesday, Oct 9 | 🕛 3:00 PM - 3:25 PM CEST

Jump-Starts

AD180 – Build SAP Fiori Apps with ABAP Cloud powered by Joule's ABAP Developer capabilities
[Jump-Start, 25 min] Learn how to develop transactional SAP Fiori apps in ABAP Cloud using the ABAP RESTful Application Programming Model supported by generative AI. You will also learn about features such as business events for loosely coupled integration scenarios and read-only treeviews for displaying hierarchical data.
ABAP Cloud is the comprehensive development model for building clean core compliant apps, services, and extensions on SAP Business Technology Platform and SAP S/4HANA, in the cloud and on-premise.
Speaker: Carine Tchoutouo Djomo (SAP)
Schedule: 📅 Tuesday, Oct 8 | 🕛 7:30 PM - 7:55 PM CEST

DT280 – Building Clean Core Extensions with ABAP Cloud for SAP S/4HANA Cloud
[Jump-Start, 25 min] Learn how to speed up the implementation of SAP S/4HANA Cloud extensions with ABAP Cloud using two new ABAP Development Tools (ADT) based generators for adding extension fields and for building custom UI services on top of business objects that have been released by SAP.
Speaker: Andre Fischer (SAP)
Schedule: 📅 Wednesday, Oct 9 | 🕛 3:30 PM - 3:55 PM CEST

I hope this overview gives you a few more reasons to join us at SAP TechEd 2024.

We look forward to meeting and interacting with you virtually at SAP TechEd Virtual and in person at the local events in West Palm Beach (US), Melbourne (AUS), Copenhagen (DK), Birmingham (UK), and Wiesbaden (DE).

In the meantime, you can check out Devtoberfest by SAP TechEd 2024 and watch the replays of last year's events, SAP TechEd Virtual in 2023 and SAP's Devtoberfest in 2023.

Stay tuned - and see you there!

SAP Field Service Management 2408: Generative AI, Enhanced User Experience, and Improved Integration

2024-08-21T15:16:08.492000+02:00

SAP Field Service Management 2408 advances our strategic investment in generative AI for field service organizations. In addition, we introduced several new features designed to simplify user workflows, strengthen integration, and increase functionality. In this blog, you can find an overview of the most notable features, along with a demo video showcasing key highlights. For a complete list of all the features in the 2408 release, click here. In this blog, I will highlight the key features that will significantly enhance how you manage field services, including:

Generative AI: Activity Summary, Equipment Insights, and Natural Language Filtering.
User Experience enhancements: Dispatching board, service contracts, filtering improvements, and more.
Service Map: Enhanced filtering and object visualization improvements.
Integration with SAP S/4HANA Cloud Public Edition: Business object replication across multiple companies.
AI-based Scheduling improvements: New and enhanced rules/objectives; service regions; and supporting technicians.

Note: The Activity Summary, Equipment Insights, and Natural Language Filtering features require a customer to be licensed for SAP AI Units. For more information about licensing, please contact your SAP Account Executive.

Generative AI

In addition to simplifying workflows, generative AI in SAP Field Service Management makes it easier to unlock and benefit from valuable insights that were previously difficult to access. These enhanced workflows and actionable insights provide substantial value to field service organizations. According to SAP customer benchmarking, by utilizing these features, field service organizations can achieve (on average):

12.5% increase in dispatcher productivity.
5% improvement in first-time fix rates.
15% reduction in time to review and plan service requests.

Take a look at the demo video below showcasing our Generative AI highlights in 2408:

Activity Summary

Activity Summary is an advanced AI feature that generates a detailed summary of previously performed activities. This summary offers dispatchers and technicians essential information, such as used spare parts, activity duration, completed checklists, and their outcomes. By leveraging this enhanced intelligence, technicians can achieve faster resolution times and improve first-time fix rates. Additionally, dispatchers can use these insights to make more informed decisions when assigning new tasks. Upon activity close, field service staff can also utilize the information in the activity summary to expedite the time to resolution and closing of work orders. For more information, click here.

Generating an Activity Summary

Natural Language Filtering: save and display used queries

Natural Language Filtering now offers prompts for suggesting previously used queries when a user begins typing related searches. This boosts dispatcher productivity by allowing them to search and retrieve relevant activities more quickly. Additionally, reusing these prompted queries does not consume AI units, helping reduce costs for customers. For more information, see here.

Save and display used queries in Natural Language Filtering

Equipment Insights: additional information with relevant links

With the latest enhancements to Equipment Insights, users can now quickly navigate to linked detail pages about activities, personnel, and spare parts involved. This improvement boosts efficiency by centralizing all relevant information, simplifying workflows, and making it easier to retrieve additional details. For more information, see here.

Equipment Insights with additional information and relevant links included

User Experience Enhancements

SAP Field Service Management also features several key user experience highlights which are summarized below and in the demo video:

Dispatching Board

Skill levels in best matching technician UI

Now, within the best matching technician UI, dispatchers can easily visualize skill levels for specific tasks. This enhancement enables dispatchers to make more informed decisions when assigning jobs that require varying levels of skill proficiency. See more here.

Skill levels visible within the best matching technician UI

Automatic calculation of travel time on plan or replan

Travel time calculation is now automated when planning or replanning activities from the planning list to the board. Planners can also manually trigger travel time calculations for specific activities. This enhancement provides accurate travel time information based on the technician's or last activity location, improving planning accuracy and overall efficiency in managing a technician's day. Find out more here.

Manually trigger calculation of travel time

Ability to zoom in and out on the dispatching board

When working within specific timeframes, it can be difficult to view all the relevant details for certain activities on the schedule. To address this, we introduced the ability to zoom in and out on the planning board without losing sight of the broader schedule context. This enhancement provides planners with greater visibility to manage detailed information about specific activities, and increased flexibility when managing the planning horizon. More info here.

Ability to zoom in and out on the dispatching board

Unassign multiple activities at once

When there is a need to unassign multiple activities, especially those within a specific timeframe for a particular technician, planners currently must unassign each activity individually. To streamline workflows, we've implemented a bulk unassign feature. This enhancement simplifies the unassign process, and reduces time spent on unassigning multiple activities. See more here.

Unassign multiple activities at once

New Activity Sidebar: Tools & Smartforms

Enhanced capabilities in the Activity Sidebar now allow planners to manage tools and Smartforms directly. We also added the ability to configure the order and visibility of tabs, making it easier to manage key information within the sidebar. This enhancement provides an improved user experience by harmonizing planning processes and offering greater flexibility when using the activity sidebar. For more information, see here.

New Activity Sidebar: Tools and Smartforms Tab

Ability to select all matching filter results

We improved the filtering functionality, allowing planners to select all matching results with a single click, instead of selecting them one by one. Additionally, a new setting lets you adjust the number of shown filter results. This enhancement increases productivity by supporting end-users in various situations, and reduces the time spent selecting matching filter results. Learn more here.

Ability to select all matching filter results

Master Data

Improved UX with Service Contracts

Service Contracts in Master Data have been improved to create a more user-friendly and intuitive experience. The enhanced layout improves readability and simplifies the management and organization of contract information, including custom fields. Explore more information here.

Improved user experience with service contracts

Partner Portal

Better access to activity information with Modal UI

Access to activity information has been improved in the Partner Portal. Partner Managers can now view work order data through the Modal UI view, with Crowd Owners ultimately controlling access via screen configuration. This enhancement allows Crowd Owners to enable features like viewing skills, attachments, extensions, and custom fields, according to business needs, offering improved consistency and greater flexibility in how partners access data. Discover more details here.

Modal View of Activity – In Preview

Service Map

2408 brings several enhancements to the Service Map, including the ability to save and configure default views, and control object visibility at different zoom levels. Check out the demo video below for more details:

Save filters as views on the Service Map

When a large volume of objects is shown on the map, finding the right information without a saved view can be time-consuming and inefficient. To address this, dispatchers can now save selected filter sets as views, with an auto-save feature creating a last autosaved view. Views can also be set as default, enhancing usability by allowing dispatchers to quickly choose the appropriate view See more here.

Service Map - save filter as view

Control object visibility with different zoom levels

Now dispatchers can adjust the precision of objects by selecting the number of objects displayed at different zoom levels. This improvement boosts performance by optimizing the map display and helps provide flexibility to meet each customer's unique visualization needs. Check out more details here.

Service Map - adjust number of objects

Integration with SAP S/4HANA Cloud Public Edition

Enable business object replication across multiple companies from SAP S/4HANA Cloud, Public Edition

For customers operating in multiple countries, integrating data from SAP S/4HANA Cloud Public Edition with SAP Field Service Management is now more efficient. Data can be mapped to specific companies in SAP Field Service Management using organizational assignments like Sales Area, Company Code, Purchasing Group, and Plants. Master and transactional data from SAP S/4HANA Cloud Public Edition, can be integrated into the respective SAP Field Service Management company based on assigned replication rules, with the ability to extend these mapping rules to custom fields. This enhancement simplifies data management in SAP Field Service Management, ensuring users have access to the correct data. See the complete details here.

AI-based Scheduling

Service Regions in Auto-Scheduling

Service regions are now fully supported in custom policies with the introduction of three new rules:

Enforce Service Region: Restricts technicians to activities within their designated service region.
Job Has Service Region: Confirms if a job is associated with a service region.
Resource Has Service Region: Confirms if a technician is assigned to a service region.

Service regions have also been added to the existing rule UDF - compare values. These enhancements reduce implementation effort by leveraging familiar concepts from manual scheduling and closing key feature gaps. More information here.

Service Regions in auto-scheduling

Support for multiple technicians in auto-scheduling

In this release, we have introduced functionality that ensures a supporting technician's time is considered blocked during the auto-scheduling process, and it also allows for the re-optimization of assigned activities requiring one or more supporting technicians. These enhancements safeguard manually created schedules from being disrupted by automatic scheduling and enable seamless re-optimization of schedules involving supporting technicians. Read more here.

Supporting Technicians in auto-scheduling

Final Thoughts

SAP Field Service Management 2408 strengthens the entire field service value chain. These enhancements enable field service organizations to unlock value through generative AI, simplify workflows with new feature functionality, and enhance company-wide integration. We invite you to explore these new capabilities, share your feedback, and help us shape the future of SAP Field Service Management by submitting your influence requests here. Stay tuned for the 2411 release, where even more innovations are on the way!

Get in touch!

Thoughts or questions? Feel free to share any feedback in a comment. It would also be great to hear directly from you which AI innovations you think could be the most impactful for future releases. For related posts and more information, please join our SAP Field Service Management Community page and explore our SAP Field Service Management Website. You can also watch the SAP Field Service Management 2408 Release Demo here, and I encourage you to register for our upcoming webinars for the most up to date information by registering here.

How to perform mass upload from an Excel file in a FIORI App in SAP BTP ABAP Environment - Part 2

2024-08-21T16:06:02.643000+02:00

Introduction

In continuation to my previous blog post (How to perform mass upload from an Excel file in a FIORI App in SAP BTP ABAP Environment - Part 1), in this blog post, I will showcase an easy way to extend a FIORI Elements-based OData V4 application in Business Application Studio (BAS) to add a custom action on the responsive table header of the list report page. This custom action will allow the user to open a dialog to browse local files and upload an Excel file.

In this blog post, I will be creating a Fiori Elements-based application using the tools provided in SAP Business Application Studio (BAS) and will be extending generated apps using App Extensions to trigger OData V4 operations (in this example, RAP Static Action 'fileUpload' to upload an Excel file and RAP Static Function 'downloadFile' to download an Excel template).

Prerequisites

SAP Business Application Studio (BAS) subscription and developer role in your respective BTP Subaccount.
Basic knowledge of performing App Extensions to extend generated FIORI Elements based apps.
Basic UI5 skill.
Use of File Uploader control.

Basic of OData V4 Operation

Function - Functions are operations exposed by an OData service that don't have side effects. Functions must return data and can include additional path segments. Functions are invoked using HTTP method GET.

Action - Actions are operation exposed by an OData service that can have side effects. Actions can return data but must not be composed with additional path segments. Actions are invoked using HTTP method POST.

Operation - Both Functions and Actions are operations that can return data. Operations are either bound to a resource (for example, an entity type), that makes them members of that instance type. Operations can also be unbound. Unbound operations are called as static operations (using “action imports” or “function imports”) since a static (unbound) operation can't be called directly.

The OData V4 model supports OData operations (Action Import, Function Import, Bound Actions and Bound Functions).

RAP - Non-Standard Operations

Non-standard operations are RAP BO Operations that provide transactional behavior and that are user defined and implemented. There are two kinds of non-standard operations.

Action: User-implemented operations that change the data of a BO instance. They are self-implemented operations. Two main categories of actions can be implemented in RAP:
1. Non-factory actions: Defines a RAP action which offers non-standard behavior. The custom logic must be implemented in the RAP handler method FOR MODIFY. An action per default relates to a RAP BO entity instance and changes the state of the instance. An action is related to an instance by default. If the optional keyword static is used, the action is defined as static action. Static actions are not bound to any instance of a RAP BO entity but relate to the complete entity.
2. Factory actions: Factory actions are used to create RAP BO entity instances. Factory actions can be instance-bound (default) or static. Instance-bound factory actions can copy specific values of an instance. Static factory actions can be used to create instances with prefilled default values.
Function: User-implemented operations that return data without any side effects.
1. Instance Function: Bound to an instance of a RAP BO Entity which can have input parameters.
2. Static Function: Not bound to any instance of a RAP BO Entity but relate to the complete entity. It can also have input parameters.

Can we create unbound OData V4 operations "Action Import" or "Function Import" in RAP?

At this moment, we cannot implement unbound function and action in RAP. Both the static action and functions are related to the complete entity. But it is supported in CAP.

Code sample:

How RAP Static Action and Functions are related to the complete entity?

Let's understand from the metadata itself.

It is bound to the complete entity and with the collection of the entity.

Let's begin

For the interest of time and topic, I am not showing all the basic steps to create a FIORI Elements based application in BAS. There are multiple blog posts and SAP Learning materials available to refer. I will directly jump to perform app extension.

We will be using the Fiori Guided Development tool to add a custom action to a page using extension and will be using the page map to perform List Report page controller extension.

Note: When you use the Fiori Guided Development tool to add a custom action in OData V4 based app, the framework automatically adds a custom action handler function in JavaScript creating a new custom JS file but does not perform controller extension. This is the way OData V4 app extension behaves which adds a "controlConfiguration" in the target page.

Custom Action in the Table toolbar for the list report in OData V2 vs OData V4:

OData V2:

OData V4:

Further Reference: Adding Custom Actions Using Extension Points

But why do we need a controller extension? Can't we use the custom action handler function created automatically by the Guided Development tool in an OData V4 app?

We need to create a controller extension in an OData V4 app explicitly to use the SAP FIORI Elements extension API to open a dialog using the 'loadFragement' function; to perform OData operations and to use Edit Flow (A controller extension offering hooks into the edit flow of the application) to invoke action and perform secured execution. Otherwise, within the custom JS file, we won't get the model reference to trigger the OData operation (here RAP Static Action and Static Function).

So, we will start by adding a custom action to the table toolbar using the FIORI Guided Development tool.

Step 1: Right click on the 'webapp' folder and select 'Open Guided Development'

Step 2: Select 'Add a custom action to a page using extensions'.

Step 3: Follow the guide and select the page and choose a custom controller and function name.

Following code snippets to be inserted.

Go ahead and insert snippets. This will modify the manifest settings and create custom JS file.

Step 4: But we need to perform controller extension. So, the custom JS file can be deleted.

Step 5: Now, we will perform the List report controller extension using the page map. So, right click on 'webapp' folder and select 'Show Page Map'.

Step 6: From the page map, select the List Report page and click on 'Show controller extension'. After that, click on 'Add Controller Extension' to create controller extension on the list report page.

Note: It is advisable to perform controller extensions for the concerned page rather than performing a generic extension for all the list report pages. Here, 'VendorEmailList' is the target list report page. So, I selected that option.

Step 7: Now, we can navigate to the controller extension using 'Edit in source code' button and add custom logic.

This the way the controller extension looks.

Let us add a custom handler function 'uploadMailDialog' to handle the custom action.

After the controller extension, the following changes applied to the manifest.json file. It signifies a controller extension added to the list report controller.

Step 8: Now, we need to tweak the manifest settings in such a way that the custom action triggers the custom handler function 'uploadMailDialog' added to the controller extension.

We need to add the custom action path adding '.extension' as a prefix. '.extension' refers to the controller extension.

Step 9: Now, if we preview the application and click on the custom action button, it will trigger the controller extension.

Step 10: Let us now add a fragment to open the file dialog. So, we will use 'fileUploader' control. I created a fragment folder inside the 'ext' folder and added a new xml file 'uploadFileDialog.fragement.xml'.

Following is the sample code snippet.

<core:FragmentDefinition xmlns:core="sap.ui.core" xmlns:f="sap.ui.layout.form" xmlns:u="sap.ui.unified" xmlns="sap.m"
	xmlns:layout="sap.ui.layout">
	<Dialog id="idFileDialog" title="{i18n>uploadVendorMailDialogTitle}" >
		
		<VBox id="idVBox" width="100%">
			<core:InvisibleText id="idInvisibleText" text="{i18n>uploadVendorMailDialogTitle}"/>
			<f:SimpleForm id="idSimpleForm" editable="true" layout="ResponsiveGridLayout" maxContainerCols="2">
				<f:content>
					<Label id="idFileUploadlabel" required="true" text="{i18n>uploadVendorMailFile}"/>
					<u:FileUploader id="idFileUpload" name="internalMailFileUpload" change="onFileChange" width="100%" 
                    uploadComplete="onUploadComplete" style="Emphasized" fileType="xls,xlsx" placeholder="{i18n>uploadVendorMailPlaceholder}"
                    tooltip="{i18n>uploadVendorMailTooolTip}" sendXHR="false" />
				</f:content>
			</f:SimpleForm>
		</VBox>
		<footer>
			<Toolbar id="idFooterToolbar">
				<content>
					<Button id="idDownloadTempButton" text="{i18n>downloadTempButtonTxt}" press="onTempDownload" icon= "sap-icon://download-from-cloud" />
					<Button id="idUploadButton" text="{i18n>uploadButtonTxt}" type="Emphasized" press="onUploadPress" icon="sap-icon://upload-to-cloud" />
					<Button id="idCancelButton" text="{i18n>cancelButtonTxt}" press="onCancelPress" icon="sap-icon://cancel"/>
				</content>
			</Toolbar>
		</footer>
	</Dialog>
</core:FragmentDefinition>

Now, add the logic to open the dialog on click of the action similar to the code snippet mentioned below.

		uploadMailDialog: function (oEvent) {
			this.base.getExtensionAPI().loadFragment({
				name: Constants.fragmentName,
				type: "XML",
				controller: this
			}).then(function (oDialogResult) {
				oDialog = oDialogResult;
				oDialogResult.open();
			})
		},

Now, in application preview the app looks like below.

Step 11: So, till now, on click of the action 'Upload', a dialog will open up asking the user to upload a file. The button 'Template' will allow users to download an Excel template, and the button 'Upload' will allow users to upload the given file.

Let us add logic to read the file content, mimetype and filename of the given file. I used 'onFileChange' event of the File uploader control as highlighted below.

		// On File Change
		onFileChange: function (oEvent) {
			// Read file
			var file = oEvent.getParameter("files")[0];
			if (file === undefined) {
				return;
			}
			fileType = file.type;  //mimetype or file type
			fileName = file.name;
			//Instantiate JavaScript FileReader API
			var fileReader = new FileReader();
			//Read file content using JavaScript FileReader API
			var readFile = function onReadFile(file) {
				return new Promise(function (resolve) {
					fileReader.onload = function (loadEvent) {
						resolve(loadEvent.target.result.match(/,(.*)$/)[1]);
					};
					fileReader.readAsDataURL(file);
				});
			};

			new Action(readFile(file)).executeWithBusyIndicator().then(function (result) {
				fileContent = result;
			})
		},

Here, I used JS FileReader API to read the file content as data URL and later used RegEx to clean the base64 encoded file content.

Step 12: Now, implement the logic to upload a file once the 'upload' button is clicked.

		//perform upload
		onUploadPress: function (oEvent) {
			var oResourceBundle = this.base.getView().getModel("i18n").getResourceBundle();
			//check file has been entered
			if (fileContent === undefined || fileContent === "") {
				MessageToast.show(oResourceBundle.getText("uploadFileErrMsg"));
				return;
			}

			var oModel = this.base.getExtensionAPI().getModel();

			var oOperation = oModel.bindContext("/VendorEmail" + Constants.serviceNamespace + "fileUpload(...)");

			var fnSuccess = function () {
				oModel.refresh();
				MessageToast.show(oResourceBundle.getText("uploadFileSuccMsg"));
				oDialog.close();
				//Clear the file name from file uploader
				sap.ui.getCore().byId("idFileUpload").clear();
				oDialog.destroy();
				fileContent = undefined;
			}.bind(this);

			var fnError = function (oError) {
				this.base.editFlow.securedExecution(
					function () {
						Messaging.addMessages(
							new sap.ui.core.message.Message({
								message: oError.message,
								target: "",
								persistent: true,
								type: sap.ui.core.MessageType.Error,
								code: oError.error.code
							})
						);
						var aErrorDetail = oError.error.details;
						aErrorDetail.forEach((error) => {
							Messaging.addMessages(
								new sap.ui.core.message.Message({
									message: error.message,
									target: "",
									persistent: true,
									type: sap.ui.core.MessageType.Error,
									code: error.code
								})
							);
						})
					}
				);
				oDialog.close();
				//Clear the file name from file uploader
				sap.ui.getCore().byId("idFileUpload").clear();
				oDialog.destroy();
				fileContent = undefined;
			}.bind(this);

			oOperation.setParameter("mimeType", fileType);
			oOperation.setParameter("fileName", fileName);
			oOperation.setParameter("fileContent", fileContent);
			oOperation.setParameter("process", sProcess);
			oOperation.execute().then(fnSuccess, fnError);
		},

Here, I triggered OData V4 operation a bound action (RAP 'fileUpload' Static Action) passing File Type, File Name and File Content as parameters.

Earlier, I already explained that a RAP Static Action or Function is bound to a collection specified by an OData entity set. So, to call such actions or functions, you can create a context binding with an absolute path, or with a relative path for the operation (for example odata.srv.name.space.staticMyAction(...)") and the header context of a list binding as parent context. The following sample shows a button press event handler which calls the static MyAction action on the MyEntity entity set.

var oModel = this.getView().getModel();
 
oModel.bindContext("/MyEntity/odata.srv.name.space.staticMyAction(...)").invoke();

The same example with a relative binding and the header context of the list binding as parent context:

var oModel = this.getView().getModel(),
    // assume there is a table with ID "idMyEntityTab" and its items aggregation bound to "/MyEntity"
    oListBinding = this.byId("idMyEntityTab").getBinding("items"),
    oHeaderContext = oListBinding.getHeaderContext();

oModel.bindContext("name.space.staticMyAction(...)", oHeaderContext).invoke();

Note: In my code sample, I am using "execute" function of the OData V4 Context binding. But, from UI5 version 1.123.0 onwards, "execute" function is deprecated. So, use "invoke" function instead as shown in the example. Simply, replace "execute' function with "invoke".

			oOperation.setParameter("mimeType", fileType);
			oOperation.setParameter("fileName", fileName);
			oOperation.setParameter("fileContent", fileContent);
			oOperation.setParameter("process", sProcess);
			oOperation.invoke().then(fnSuccess, fnError);

Reference: Execute function of OData V4 Context Binding API

Alternatively, you can also use the "invokeAction" method of the Edit Flow API ( Edit Flow API ). However, I found the above approach to be the preferred choice.

Reference: How to call RAP static action from elements FPM extension with EditFlow.invokeAction()?

After this step when you will execute the 'upload' action selecting an Excel file to upload, the RAP static action 'fileUpload' will trigger and the XCO XLSX module will do the rest to parse the file content and create/update BO entity instances as explained in my previous blog post.

Step 13: Similar to the file upload, the excel template can also be downloaded invoking RAP static function 'downloadFile'.

Sample code snippet:

onTempDownload: function (oEvent) {
			var oModel = this.base.getExtensionAPI().getModel(),
				oResourceBundle = this.base.getView().getModel("i18n").getResourceBundle();

			var oModel = this.base.getExtensionAPI().getModel(),
				oResourceBundle = this.base.getView().getModel("i18n").getResourceBundle();

			var oOperation = oModel.bindContext("/VendorEmail" + Constants.serviceNamespace + "downloadFile(...)");

			//Success function to display success messages from OData Operation
			var fnSuccess = function () {
				var oResults = oOperation.getBoundContext().getObject();

				var aUint8Array = Uint8Array.from(atob(oResults.fileContent), c => c.charCodeAt(0)),
					oblob = new Blob([aUint8Array], { type: oResults.mimeType });

				File.save(oblob, oResults.fileName, oResults.fileExtension, oResults.mimeType);
				MessageToast.show(oResourceBundle.getText("downloadTempSuccMsg"));
			}.bind(this);

			//Error function to display error messages from OData Operation
			var fnError = function () {
				this.base.editFlow.securedExecution(
					function () {
						Messaging.addMessages(
							new sap.ui.core.message.Message({
								message: oError.message,
								target: "",
								persistent: true,
								type: sap.ui.core.MessageType.Error,
								code: oError.error.code
							})
						);
						var aErrorDetail = oError.error.details;
						aErrorDetail.forEach((error) => {
							Messaging.addMessages(
								new sap.ui.core.message.Message({
									message: error.message,
									target: "",
									persistent: true,
									type: sap.ui.core.MessageType.Error,
									code: error.code
								})
							);
						})
					}
				);
			}.bind(this);

			// Execute OData V4 operation i.e a static function 'downloadFile' to download the excel template
			oOperation.execute().then(fnSuccess, fnError)
                        // From UI5 version 1.123.0 onwards use invoke function
			//oOperation.invoke().then(fnSuccess, fnError);

Please stay tuned for the next blog post where I will explain how I used the XCO XLSX module to create an Excel template and dynamically handled the column names based on the template structure defined in the backend and populated the text maintained in the data elements. This will enable them to read the translated texts as well. The translation process is different in ABAP Cloud; hence, the traditional approach does not work.

Electronic Invoices for Malaysia: A Guide for Communication Settings

2024-08-22T07:23:21.554000+02:00

You are in the process of implementing electronic invoices for Malaysia. One of the key implementation activities is to integrate your business system (for example, SAP S/4HANA Cloud) with SAP Document and Reporting Compliance, cloud edition. The cloud edition acts as a bridge between your business system and the Inland Revenue Board of Malaysia (IRBM), the tax authorities in Malaysia. Among other settings, you must configure communication settings in the Manage Communication Settings - External Parties app in the cloud edition to connect to the IRBM. This blog guides you through configuring these communication settings.

Getting Started

Start your journey by reading the following documentation, which describes how to configure communication settings:

SAP S/4HANA Cloud: Managing Communication Settings | SAP Help Portal
SAP S/4HANA: Managing Communication Settings | SAP Help Portal
SAP ERP: Managing Communication Settings | SAP Help Portal

The communication settings primarily involve maintaining the credentials that you've obtained from the IRBM or another authority, including a pair of client ID and client secret as well as a digital certificate. You should get these credentials ready for use before proceeding to configure communication settings in the cloud edition. You can find out the Malaysia-specific settings from the Process-Specific Settings page:

Product Guide: Process Specific Settings

Step 1: Create a New Communication Type

You need to first retrieve your taxpayer identification number (TIN) as described at How to retrieve and verify company TIN number? and then create a new communication type using this TIN.

Create communication type

Step 2: Add an Authentication Setting for Consuming the IRBM APIs

For the communication type created in step 1, add an authentication setting that is used to consume the IRBM APIs, as follows:

Select the Basic type.
Enter your client ID as the username and your client secret as the password.
See How to obtain Client ID and Client Secret?.

Add basic authentication type

Step 3: Add an Authentication Setting for Signing Electronic Invoices

For the communication type created in step 1, add another authentication setting that is used to sign electronic invoices, as follows:

Select the Key Pair X.509 type.
Upload the certificate you generated from one of the certified service providers.
Enter the password for your digital certificate.
You need to purchase a digital certificate from a certificate authority (CA) in Malaysia. See How to acquire Digital Signature?.

Note: SAP supports soft certificates only, roaming certificates are not supported. The digital certificate extensions supported are PFX and P12.

Add Keypair

More Information

Suppose that your company has several company codes representing headquarters and subsidiary units. In this case, you can choose to use only one digital certificate, which is registered with the TIN of headquarters or a leading subsidiary. The TIN associated with the common certificate is referred to as intermediary or intermediary representative. See For companies that have subsidiaries, does digital certificate need to be registered for each subsidiary?.

If you use different SAP systems at the same time, such as SAP ERP and SAP S/4HANA, you can still use the same digital certificate.

Also remember that a digital certificate has an expiration date. You must renew your certificate when it's expiring soon. See Do I need to renew a digital certificate?. Otherwise, you'll encounter the following errors:

Certificate is not valid according to the chain of trust validation or has been issued by an untrusted certificate authority.
Signing time is not within validity period.

We hope that you find this information useful. Feel free to leave a comment on this blog or follow SAP Document and Reporting Compliance | SAP Community.

SAP Document and Reporting Compliance

Reduce project cycle time using collaboration capabilities in SAP Project and Resource Management

2024-08-23T08:40:49.947000+02:00

In today’s digital, fast paced, and interconnected world, it becomes imperative that projects need to be run at speed and efficiency. Project lifecycles have condensed and focus on collaboration between project stakeholders has never been more critical. Success clearly lies in cooperation, trust, reducing risk and increasing efficiency between intra and inter organizational members.

The complexity of modern projects demands a seamless integration between various stakeholders - owners, contractors, subcontractors, engineers, architects, facility managers, and authorities.

This challenge posits a question: “How can project managers increase project efficiency, transparency and reduce the complexity of information exchange - between internal and external project stakeholders - while maintaining their individual objectives and incentives”?

Project Collaboration Management as part of SAP Project and Resource Management addresses this specific whitespace.

Need for Project Collaboration Management

Project activity Interdependency: Stakeholders in cross company projects sometimes cut across different geographies and organizations. Coordinating with these diverse members requires a robust collaboration framework to ensure that all parties are on the same page.

Inefficiency in Traditional Methods: Traditional methods of collaboration, such as emails and phone calls, are not only time-consuming but also error prone. Information shared through different systems can lead to miscommunication and delays.

Compliance to Standards: In industries such as Engineering and Construction, adhering to standards like building information modelling (BIM) and maintaining a common data environment is crucial for project success. Projects also have their templates to comply with and adhered by all members.

Capabilities of Project Collaboration Management

Share Project Information: This centralized and integrated toolset provides a single source of truth to enhance project transparency and collaboration to also to track and control both management and execution processes. Features such as GANTT chart and KANBAN board provide visibility to activities and enable agile decision making. Project Managers can share project plans with external partners and import project timelines from 3rd party scheduling tools using various file formats such as .mpp, .mpx, .mpd, .xer. This enables Project Managers to manage multiple versions of project plans e.g., from tools like Oracle Primavera or MS Project and use these versions to compare against initial timeline.

Native integration with Enterprise Projects in SAP S/4HANA Cloud, public edition allows users to import project WBS elements from underlying system and use them as the basis for project structure. In addition, one can also import the projects WBS structure from Project System in SAP S/4HANA by using the SAP Integration suite. For integration with EPPM (Portfolio and Project Management) in SAP S/4HANA, a consulting service is offered to define the corresponding iFlows in the SAP Integration Suite. This approach utilizes APIs for custom integrations which enables users to bring-in project timeline information from any kind of project scheduling tools.

Support for Digital Twin: SAP Project Collaboration Management is an open, flexible, and expandable solution that supports digital twin lifecycle from as-designed to as-built. Project Managers can share digital models in a central repository to connect cross company and organizational processes. Distributed project information can be visualized and connected using a digital twin that complies with local and international standards and actions on the digital twin can be monitored by assigning issues, changes, and tasks.

Issue and Change management: The tool helps Project Managers simplify Task, Risk, Issue and Change Request by providing option to classify and document project problems with detailed information such as notes, member responsible, related objects and photos. It provides flexibility to manage authorizations at both individual and team level. Project Managers can use the automated review and approval process to collaborate across internal and external stakeholders on topics that impact project cost, scope, quality, and schedule.

Risks, Issues and Change Requests

Risk Heat chart

Benefits of Using Project Collaboration Management

Streamlined Processes: The tool provides a digitized and automated information flow between all internal and external project stakeholders. This helps avoid manual steps, reduce errors, and decrease waste of time and materials. Collaborative project management ensures that all stakeholders are aligned, leading to faster project completion times and adherence to higher quality standards.

Enhanced Efficiency: Features like document management, cross-company project master plans, risk, task and issue management, and visual budget control significantly improve process efficiency. Automation of manual tasks leads to a more productive workforce.

Increased transparency: An integrated toolset for project management and work management results in a single source of truth for project information. It provides users visibility to upstream and downstream processes and the right information leading to fewer claims disputes, resulting in better customer relationships.

Reduced Rework and Cycle time: By improving collaboration, companies can reduce rework and waste by up to 50%*. This not only saves time but also reduces costs associated with time and material wastage. Collaborative project management can also reduce cycle times for approvals and workflows by up to 60%*, ensuring that projects move forward without unnecessary delays.

*Source: SAP experts estimate based on co-innovation customer engagements

Conclusion

A study by PMI states that collaborative project management tools can increase the success rate of projects by 71%. With its numerous benefits, SAP Project Collaboration can help Project managers deliver real business value. Thus, by leveraging Project Collaboration Management within SAP Project and Resource Management, companies can increase efficiency, build trust and transparency, and meet the complexity and demands of new-age projects.

You can learn more about SAP Project and Resource Management at the following pages:

SAP Product Page: SAP Project and Resource Management
SAP Help portal: SAP Project and Resource Management | SAP Help Portal
SAP Community Page: SAP S/4HANA Cloud Public Edition and Project Control

4 Step semi-sequential payment approval

2024-08-26T13:48:34.425000+02:00

In this blog, we will discuss How to configure a semi-sequential payment approval. The idea is to restrict the same approvers from approving payment batches in the 2nd and 3rd approval steps.

Image/data in this blog is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Follow the steps to configure a semi-sequential payment approval.

Configure new Approval Groups, Approval Patterns in configuration activity / SSC-UI ID 102336 - Define Settings for Bank Account Master Data.
Add new Approval Groups for 4 Steps Semi-Sequential Approval
Approval pattern for 4 Steps Semi-Sequential Approval with limits on the 4th Step.
Assign the approval pattern to the company code and account type.
Maintain the payment approvers and assign the approvers group in the App Manage Bank Accounts for the bank account.
Press the button Show Approval Steps to Display the Approval steps for the bank account payment approval.

SAP Fiori for SAP S/4HANA - Extend FIORI App "Manage Customer Master" with Z-field

2024-08-26T16:14:17.317000+02:00

Introduction

Utilize the FIOR app "Custom Fields" (F1481) from the SAP Fiori Apps Reference Library (ondemand.com) to easily add a Z-field to your FIORI app. This allows for custom field extension without the need for programming, thanks to the Key User Extensibility functionality. For more information on this topic, check out the blog post "SAP Fiori for SAP S/4HANA – What is Key User Extensibility and Who are your Key Users."

Key User Extensibility is part of Clean Core approach to keep your system/landscape clean as described at blog post Clean Core demystified: What does it mean and how to achieve it with SAP BTP?

More information about Key User Extensibility, including required roles and initial steps, can be found on the SAP Help website.

In the example outlined in this blog, I will demonstrate the addition of a custom field (Z-field) to the "Manage Customer Master" FIORI app (F0850A) at the Sales Area level. The custom field, "Last Phone Contact," will be added as an example. This information can be found in the SAP Fiori Apps Reference Library.

This extension will be done in 2 steps:
1. Z-field definition
2. Z-field assignment at FIORI app

Target audience: Functional expert, Development expert

Starting point

In the FIORI app "Manage Customer Master," a new Z-field should be added to the Sales Area level to store the last phone contact date specific to the Sales Area. This field should be located in the "General Data" section (highlighted in red).

Z-field definition

To define a custom Z-field run FIORI app "Custom Fields".

At this app you will see all so far created custom fields. To add a new field push "Create" button.

Field properties

At appearing pop-up you have to define your field properties like:
1. Business Context
2. Label
3. Identifier
4. Tooltip
5. Type

Business Context

With setting the Business Context you tell the system to which objects the Z-field is related to.

Following Business Contexts are relevant for Business Partner, Customer or Supplier:

BP_CUSTVEND1 - Master Data: Business Partner BUT000
CUSTOMER_GENERAL - Customer Core View KNA1
CUSTOMER_GEN_ADDR - Customer General Address Dependent Context KNA1_ADDR
CUSTOMER_SALES_ADDR - Customer Sales Address Dependent Context KNVV_ADDR
CUST_COMPANYCODE - Customer company code core KNB1
CUST_SALES - Partner Sales area core view KNVV
SUPLR_PURORG_ADDR - Supplier Purchasing Organisation Address Dependent Context -> Listed but not available
SUPPLIER_GENERAL - Supplier Core View LFA1
SUPPLIER_GEN_ADDR - Supplier General Address Dependent Context -> Listed but not available
SUP_COMPANYCODE - Supplier Company Code Core LFB1
SUP_PURORG - Supplier Purchasing Org Core LFM1

The SCFD_REGISTRY transaction allows you to determine the objects associated with the business context, such as CDS Views, OData Models, and BAdIs, through the Custom Fields: Registry UI.

You can locate CDS View MD_CUSTOMER_MASTER_SRV_01 in the FIORI Library for the FIORI app "Manage Customer Master" (F0850A) by referring to the Implementation Information section of the SAP Fiori Apps Reference Library (ondemand.com).

Label

This field description is displayed on screens and includes technical details.

Identifier

This is the technical name of this field starting with a predefined prefix.

Tooltip

This is the description which is shown if you hoover over this field with your mouse.

Type

This field is the technical type that can be found in the SE11 transaction. The screenshot shows the data I entered.

I recommend adjusting or at least checking the predefined usages of this new field. To do this, press the "Create and Edit" button.

You can view additional field descriptions such as Medium Label and different tabs like "User Interface" at the detail screen. These tabs display potential technical objects. The number within the tab description indicates how many, for example, User Interfaces are assigned to your selected Business Context.

You may choose to establish or leave unused a new field on each technical object. In order to publish the new field for the FIORI app "Manage Customer Master", you must enable it for the User Interface Manage Customer Master, which is based on the Data Source MD_CUSTOMER_MASTER_SRV_01.

Please note that it is not possible to enable this field for any GUI transaction. If you wish to add this new field to a BP transaction, please refer to the blog post "SAP S/4HANA Business Partner - Field Enhancement" on SAP Community for instructions. You can find the relevant information under the "Implementation" topic.

To make this field available for SOAP APIs and/or IDOCs, you should enable it in these areas.

After defining technical usages, you can add field description translations by navigating to the "General Information" tab.

Select target language(s) and enter texts in target language.

All preparations are complete, and you can now save your work. Saving the setup allows you to preserve your work in a temporary state, enabling you to make further refinements and save again. When you click the "Publish" button, the system will initiate the generation process, automatically creating or adjusting all technical objects in the background.

The app will automatically navigate to the view of custom fields overview. You will need to scroll all the way down to the end of the field list to see your Z-field with the status "Publishing…"

Keep in mind that it will take some time to publish the new field. The more data you have in your database, the longer it will take. This is due to the column store storage type of the HANA database, which requires complex restructuring during extensions. Additionally, the decompression and recompression of data for compression prolong the process, and indexes need to be recreated or reorganized for new columns, adding to the time it takes. After the publishing is finalized, the screen will be refreshed and you will see the new field:

Now your new field is ready to use.

Technical field check

Check with field Viewer

Run Transaction SCFD_FIELDVIEWER to check your new field.

Check with SE11

To check the usage of this new field navigate to tab "Usages". Here you can see all objects which has been enhanced by this field.

For example let's have a look at enhanced objects like table KNVV - Customer Sales Area Data
Run transaction SE11 and display table KNVV.

There are important structures which has been enhanced automatically. I will stick to 2 examples:
1. Migration structure for customer master data
2. Main CVI structure CVIS_EI_EXTERN

Run transaction SE11 and display structure MIG_CMDS_EI_CUST_SALES_EXT_S which is part of migration structure MIG_CMDS_EI_CUST_SALES_EXT_T which is used at function module CMD_MIG_BP_CVI_CREATE.
(Navigation path from function module import parameter: IT_EXT_CUST_SALES -> MIG_CMDS_EI_CUST_SALES_EXT_T -> MIG_CMDS_EI_CUST_SALES_EXT_S)

Run transaction SE11 and display structure CMDS_EI_SALES_DATA.

This structure is part APIs, WebServices, ….
(Navigation path from Maintain Business Partner class CL_MD_BP_MAINTAIN parameter: I_DATA -> CVIS_EI_EXTERN -> CUSTOMER -> SALES_DATA -> SALES -> DATA)

Add Z-field to FIORI app

Add new field to your FIORI app "Manage Customer Master" (F0850A) (SAP Fiori Apps Reference Library (ondemand.com)) at Sales Area level.

Start FIORI app from FIORI Launchpad and navigate into customer sales area data.

Switch into "Adapt UI" mode via your profile.

To add a new Field Group use right mouse-click at your target area and "Create: Group" option appears.

Enter a text for your new group and use right mouse-click at your group name to add a new field.

At appearing pop-up you can find your new field. It might be that you are forced to scroll a bit. In my example my new field is available without scrolling.

Mark this field and press OK button. By using the mouse you can place the field group.
Don't forget to save and activate you changes. By activation system is asking you for a version name. Enter a name and confirm.

By pressing button "Publish Version" you can take over your changes into a transport request to publish your changes to your landscape.

Testing

Leave the "Adapt UI" mode and test your new field.

Using calendar button you can select a date out of the calendar pup-up to take over a specific date.

Apply and save you changes and navigate into Sales Area data in display mode to check your changes.

As a last technical check navigate into transaction SE16N and use table KNVV. Don't forget to remember customer number and used Sales Area.

Optional: Add field to BP transaction

Now you have done technical prerequisites to add the new field to BP transaction which is not done via field extensibility automatically.

If you want to implement this new field into BP transaction, follow instructions at blog post SAP S/4HANA Business Partner - Field Enhancement. You can directly step into topic "Implementation".

How to perform modifications in Standard Migration Object with Migration Object Modeler App

2024-08-26T16:47:23.404000+02:00

Introduction:

Let’s explore the options for adapting delivered content of the SAP S/4HANA migration cockpit to meet our customer-specific circumstances.

The SAP S/4HANA migration object modeler is name of the modelling environment in the migration cockpit. Available in the on-premises version of SAP/4HANA, you can call it using Transaction LTMOM. In SAP S/4HANA Cloud Public Edition, the migration object modeler is called via the SAP Fiori tile Model Migration Objects - Migration Object Modeler.

Prerequisite:
Before proceeding with adding any field, it is necessary to verify if the specific Migration Object allows the addition of the required field. The business role SAP_BR_ADMINISTRATOR is required to use the SAP S/4HANA Migration Object Modeler.

To check which Migration Object support field additions, refer to SAP Note 2999428 - Collective Note for extensions via Model Your Migration Objects - Migration Object Modeler App in SAP S/4HANA Cloud, public edition (Migrate Data Using Staging Tables), this specific KBA outlines the objects that permit fields to be added.

Use Case:
The field "Document Number" is not present in the Migration Object “Product” template. Downloaded template is not having any field “Document Number” in the Basic Data Tab as shown below.

Image/data in this blog is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Standard Template:

Steps to follow:

Create a Migration Project from “Migrate Your Data” App, here as an example I have created the Migration Project “Test_Sap”.
Open the Project (Test_Sap) in the Object Modeler App and go to the Migration Object “Product” and open the Source Structure in Edit mode.
Then click on the create button.
Once clicked you will see a new row got added with the prefix “ZZ”. Create the field as per your requirement and then click on Save.
Now the field is created. We can see the field ZZ_ ZEINR in the Source Structure of the Migration Object. We need to map the newly added field to the Target Structure of the underlying API.
To perform the Field Mapping, double-click on the Field Mapping node.
Now as mentioned in the Prerequisite section the newly created field needs to be mapped to the underlying API Structure. Here the mapping is done with the field ZZ_ZEINR with the API field Document number (without document management system).
To map it drag and drop the Source Structure to the Target Structure. Once mapped it will turn the Document Number sign in Green. By default, the Rule MOVE is used to map the Source and Target Structure, you can change the rule as per your business requirement.
In the Object Modeler app regenerate the Migration Object using the Reset Migration Object option.
Now download the Template from the app Migrate Your Data app.
The required field will be added in the template.

To add fields in a Migration Object within the S/4 HANA Private Edition using LTMOM, refer to this specific blog.

To add custom fields using the App "Custom Fields" refer to the help portal Overview | SAP Help Portal.

Automatic Loss Handling with Event-Based Revenue Recognition for Projects

2024-08-28T11:45:14.774000+02:00

Relevant for SAP S/4HANA Cloud Public Edition 2408.

Co-authored by Volkmar Zahn, Frank Hennrich, Gerold Wellenhofer and Chenchu Zhong.

In this blog post, we would like to share with you the new automatic loss handling feature with Event-Based Revenue Recognition (EBRR) for project-based service and project-based sales scenarios. This exciting innovation has been made available with the release 2408.

Scope Introduction

Companies aim to make profit from contracts. However, in some cases, the costs associated with a contract can surpass the potential revenue from the contract, leading to a loss. International accounting standards, such as IFRS, provide specific guidance for such scenarios. In principle, the imminent loss reserves for a loss-making contract must be built as soon as it is foreseen that estimated costs exceed the estimated revenue that will be earned under the contract.

What we offer in EBRR since years to address this requirement is a manual processing of imminent loss handling. In the Event-Based Revenue Recognition – Projects app, you can use the Enter Manual Contract Accruals feature to post Reserves for Imminent Loss manually. As seen in the screenshot below, 100 EUR of Manual Reserves for Imminent Loss Reserves have been posted to the project using the Enter Manual Contract Accruals feature.Figure 1: Manual Imminent Loss Reserves entered using Enter Manual Contract Accruals

The field Manual Contract Accruals (Balance Sheet) in the section Manual Contract Accruals on the Balance Sheet tab shows 100 EUR of Manual Imminent Loss Reserves, representing the contract liability. The field Manual Contract Accruals (Income Stmnt.) in the Adjustments section on the Income Statement tab displays -100 EUR of Manual Adjustment of Reserves for Imminent Loss.

Figure 2: Manual Imminent Loss Reserves in the Event-Based Revenue Recognition-Projects app

After the project is completed, the balance of Manual Imminent Loss Reserves will be cleared during the next period-end closing.

With the release CE2408, the automatic loss handling process feature has been released for revenue recognition scenarios: Project-Bases Services (1IL, 1P0, 33O) and Project-Based Sales (4GQ, 4GR, 4GS). This particularly applies to the revenue recognition key SPFC for project-based services, and the revenue recognition keys EPMFC & EPMFR for project-based sales. The underlying revenue recognition methods which support automatic loss handling are the cost-based POC method and the revenue-based POC method. The posting logics for each method are illustrated with the following T-account examples: Figure 3: T-Account Example for Automatic Loss Handling with Cost-Based POC Method

Figure 4: T-Account Example for Automatic Loss Handling with Revenue-Based POC Method

System Walkthrough – Automatic Loss Handling in Project-Based Sales

Now let’s delve deeper into the functionality using the example of a revenue-carrying enterprise project with an anticipated loss. The project is created to collect costs and revenues for selling project-based solutions with sales orders. The project uses the revenue recognition key EPMFC, which is utilizing a cost-based PoC revenue recognition method.

Figure 5: Project Control - Enterprise Projects app

Due to unforeseen events, the costs of materials and labor have risen significantly, and the newly estimated contract costs exceed the contract revenue, and the contract turns to a loss making one.

In this example, we use the Import Financial Plan Data app to bring in the most up-to-date plan data for the project. Once the data has been successfully imported, we then proceed to review the Financial Data for the project. The project has 1500 EUR of planned revenue and 2000 EUR of planned costs. Therefore, the project is identified as a loss-making project.

Figure 6: Financial Plan Data for Project

During the EBRR period-end closing, initial reserves for the imminent loss are calculated and created. In this example, we use the Revalue feature in the Event-Based Revenue Recognition – Projects app to re-evaluate the project. The system calculates the imminent loss reserves according to the plan values in the leading ledger. In the Revalue screen, we see 500 EUR of Imminent Loss Reserves under Liabilities and corresponding -500 EUR of Adjustment Imminent Loss Reserves under Adjustments.

Figure 7: EBRR Simulation Results for Creation of Imminent Loss Reserves

The simulation results have been posted to the project and the values have been refreshed in the Event-Based Revenue Recognition – Projects app.Figure 8: Imminent Loss Reserves in the Event-Based Revenue Recognition - Projects app

In the execution phase, EBRR adjusts the imminent loss reserves based on the percentage of completion of the project.

In this example, the goods are delivered to the client.

Figure 9: Posting of Goods Issue

Upon posting the goods issue, 250.11 EUR of actual costs have been posted. In real-time, Event-Based Revenue Recognition calculates the recognized revenue according to the revenue recognition key EPMFC, which recognizes revenue on cost-based POC:

Percentage of Completion (POC) = actual costs / planned costs = 250.11 EUR / 2000 EUR = 12.5055%

Recognized revenue = POC × planned revenue = 12.5055% × 1500 EUR = 187.58 EUR

The screenshot shows the updated values of actual costs, accrued revenue and recognized revenue in the Event-Based Revenue Recognition – Projects app.

Figure 10: Recognized Revenue upon Posting of Goods Issue

During period-end closing, EBRR calculates the consumption of the imminent loss reserves based on the percentage of completion. In this example, we use the Revalue function to re-evaluate the project.

Consumption of Imminent Loss Reserves = POC × Imminent Loss Reserves = 12.5055% × 500 EUR = 62.53 EUR

Remaining Balance of Imminent Loss Reserves = 500 EUR – 62.53 EUR = 437.47 EURFigure 11: EBRR Simulation Results for Consumption of Imminent Loss Reserves

The values of Imminent Loss Reserves and Adjustment of Imminent Loss Reserves are updated in the Event-Based Revenue Recognition – Projects app.Figure 12: Imminent Loss Reserves in the Event-Based Revenue Recognition - Projects app

Now, a billing document is sent to the client, with the billing amount of 1500 EUR.Figure 13: Billing Document

Upon posting of the billing document, EBRR creates an invoice correction posting in real-time. The screenshot shows the updated values of Billed Revenue, Deferred Revenue and Revenue Adjustment.Figure 14: Deferred Revenue upon Posting of Invoice

The project has now been set to completed.Figure 15: Project in Completed Status

A period-end closing has been scheduled for the project in the Run Revenue Recognition – Projects app.

Figure 16: Run Revenue Recognition - Projects app

The results of the Output show that revenues and costs have been recognized for the project. Imminent loss Reserves and Adjustment of Imminent Loss Reserves are balanced to zero.Figure 17: Output Results of EBRR Period-End Closing

Let’s review the journal entries that have been recorded for the project in this example.

Figure 18: Journal Entries of Imminent Loss Reserves

The journal entries are grouped by the reference documents. The business transaction type TBRR indicates the journal entries are posted by Event-Based Revenue Recognition.

The journal entry 100191845 is recoded during the first period-end closing (using the Revalue feature). It creates the initial imminent loss reserves of 500 EUR for the project. The SLA line item type 8300 indicates that this is the creation of the imminent loss reserves.

The journal entry 100191868 is recorded during the second period-end closing (using the Revalue feature). It is for the consumption of imminent loss reserves after the posting of goods issue. The SLA line item type 8301 shows that this is the consumption of the imminent loss reserves.

The journal entry 10019883 is recorded during the third period-end closing (using the Run Revenue Recognition – Projects app) after the project has been completed. The remaining balance of imminent loss reserves is zeroed out as revenues and costs are fully recognized.

Activation of Automatic Loss Handling in Event-Based Revenue Recognition

To activate automatic loss handling, a few customizing settings must be configured.

First, go to the SSCUI Maintain Settings for Event-Based Revenue Recognition (ID 102530)

In the step Assignment Rules, choose the pre-delivered assignment rule for automatic loss handling processing. In case you require the functionality of automatic loss handling for customer projects, select the assignment rule COSTPOCL. In case the automatic loss handling for revenue-carrying enterprise projects is needed, select the assignment rule EPMCCCL. Next, proceed to the Assign Sources and Posting Rules step. Here, set up the G/L accounts for the line with the usage 300: Loss processing to capture the automatic imminent loss reserves. Specific G/L accounts should be utilized for the usage 300 to prevent any impact on the manual loss processing using the usage 301, if applicable.Figure 19: Maintain G/L for Automatic Loss Handling

Please note, it is necessary to update Financial Statement Version (FSV) YPS2 and assign the G/L account Adjustment of Imminent Loss Reserves to the tag ADJ_COS. Assignment of the B/S account for imminent loss reserves is not required to the Financial Statement Version YPS2, as reporting is taken care by SAP.

In the Recognition Keys step, choose the supported revenue recognition key for automatic loss handling and assign the assignment rule for automatic loss handling to the selected revenue recognition key. For example, in the screenshot, the recognition key EPMFC is selected. Then, you click Company Code and Accounting Principle Settings, and assign the assignment rule EPMCCCL to the company code 1010 with the accounting principles DEAP and IFRS.Figure 20: Maintain Assignment Rules of Automatic Loss Handling for Recognition Keys

In the Document Types step, change the Loss Handling from Manual loss handling to 3-Automatic creation and usage (closing).Figure 21: Maintain Loss Handling Function

If you require to deactivate automatic loss handling, you must first clear the balances of the imminent loss reserves for ongoing projects before reverting the configuration to manual loss handling. Please follow these steps:

Set the project status to completed.
Run the period-end closing, which can be done in the Run Revenue Recognition – Projects app, to clear the open balances in Event-Based Revenue Recognition.
Change the assignment rule back from EPMCCCL to EPMCCC for the revenue recognition key EPMFC. To avoid issues, make sure that the balances for the values in Event-Based Revenue Recognition have been cleared during the period-end closing.
In the Document Types step, change the Loss Handling setting back from 3 Automatic creation and usage (closing) to Manual loss handling for the corresponding company codes and accounting principles.
Set the project status back to released.

In summary, the automatic imminent loss handling feature offers you a streamlined way to identify the projects with anticipated loss and immediately reflects this in your financials, supporting you in compliance with the requirements from international accounting principles.

SAP S/4HANA Cloud for group reporting - Release 2408 is generally available

2024-08-28T11:53:02.121000+02:00

We're glad to announce the release of SAP S/4HANA for group reporting 2408 on July 24, 2024, with new and improved features to help you run your corporate close process. Key innovations in release 2408 include:

Group financial statement review booklet improved with commenting and calculated measures
Group-level Green Ledger - managing greenhouse gas emissions for group reporting
Industry scenario fields for public sector and financial services
New Fiori app to define consolidation groups
Improved data mapping including dashboard view of jobs by status and user notifications
UX improvement of the Release Universal Journal task
Multiple line-validation tasks on group reporting and unreleased accounting data
Support different amounts with the same key in local and group currency

--
Group financial statement review booklet improved with commenting and calculated measures

The group financial statement review booklet is a reporting app designed to help you validate your closing process. With the release 2408, we improve the review booklet with two new features.

You can now manage comments in your reports:

Use the new commenting side panel
Add comments on a single data-cell or see "all loaded cell-comments" for a page
Classify, tag, and filter comments

Also, you can create ratios and calculations: calculate important measures and structures, and add them to the layout of your page.

In the release 2408, we also improve the group financial statement review booklet with the following features:

Share public variants of your booklet using Microsoft Teams
Full page mode
Accessibility
Review booklet designer to create and adapt your review booklets

More information on Group Financial Statement Review Booklet - Highlighted Features in S/4HANA CE2408 and Review Booklet Designer (Concept and Adaptability) - CE2408.

--
Group-level Green Ledger: managing greenhouse gas emissions for group reporting

Source: WRI/WBCSD Corporate Value Chain (Scope 3) Accounting and Reporting Standard (PDF), page 5

In the 2408 release, we've introduced new features to help you follow sustainability standards. These updates will improve your ability to manage greenhouse gas emissions at a group level. The main additions include:

Business function that you can enable to add greenhouse gas–specific standard fields to group reporting
New fields such as greenhouse gas category, mode of transport, or calculation method
New column structure in group financial statement review booklet showing emission quantity numbers
Elimination rules to remove double accounting for greenhouse gas emissions
Configuration of document types that only allow posting quantities for pairwise eliminations and consolidation postings, as is already possible for the other posting levels
Use both quantitative and financial data on the same financial statement item, with the support of an optional breakdown (breakdown 1)

New greenhouse gas fields in group reporting's master data

You can enable a new business function to activate standard fields for greenhouse gas (GHG). Five new greenhouse gas fields are then activated in group reporting's master data:

GHG Scope
GHG Category
Scope 2 Calculation Method
Scope 2 Contractual Instrument
Mode of Transport

These five greenhouse gas fields are dedicated to the consolidation process. They behave as any other master data field. You can manage them in the Define Master Data for Consolidation Fields app.

These new fields are defined according to the GHG Protocol Corporate Standard, which classifies a company’s greenhouse gas emissions into three ‘scopes’:

Scope 1 emissions are direct greenhouse emissions that occur from sources that are controlled or owned by an organization (for example, emissions associated with fuel combustion in boilers, furnaces, vehicles).
Scope 2 emissions are indirect GHG emissions associated with the purchase of electricity, steam, heat, or cooling.
Scope 3 emissions are the result of activities from assets not owned or controlled by the reporting organization, but that the organization indirectly affects in its value chain. An organization's value chain includes both its upstream and downstream activities.

New greenhouse gas fields in Flexible Upload and Data Mapping

To upload greenhouse gas data in SAP S/4HANA for group reporting, you can use the Flexible Upload of Reported Data app as well as the Data Mapping app in SAP Group Reporting Data collection. Both apps have been enhanced with greenhouse gas specific columns.

You can now generate data for additional greenhouse gas fields with the Flexible Upload. These fields are automatically included in the mapping template files. Use the Flexible Upload app if you have simple import requirements, with no transformation needed from source to data.

Also, you can map and generate data for additional greenhouse gas fields with Data Mapping. These fields are automatically included in the mapping template files. Use the Data Mapping app if you have more complex requirements, and need to transform source data before populating SAP S/4HANA for group reporting.

New configuration of document types that only allow posting quantities for pairwise eliminations and consolidation postings

Document types identify the type and source of data. For example, reported data is stored on different document types than elimination data. Document types are used in posting journal entries as well as other consolidation settings, tasks, and reports. For manual group journal entries as well as for automatic consolidation rules, the greenhouse gas processing requires that some document types should only allow posting in quantities.

In addition to document types that allow postings in both amounts/currency and quantity, with release 2408 you can now also configure document types that will only allow postings in quantity, both for pairwise eliminations (posting level 20) and consolidation (posting level 30).

Elimination rules to remove double accounting for greenhouse gas emissions

Automated intercompany elimination rules remove all double accounting of greenhouse gas emissions at group level. Below is an example of a simplified greenhouse gas value chain of two subsidiaries part of the same consolidation group. The example encompasses the following:

Scope 1 Direct greenhouse emissions from the two subsidiaries in the example
Scope 2 Indirect emissions from energy suppliers of the subsidiaries
Scope 3 Result of activities from assets not owned by the subsidiaries
Carbon handover activities from the subsidiaries
One subsidiary has an intercompany of 80t CO2e with the other, which should be eliminated at group level

From a group reporting perspective, the value chain including the intercompany to be eliminated at consolidated level can be summarized as follow:

Below is an example of how intercompany consolidation rules automatically eliminate amounts in currency and in quantity for the greenhouse gas value chain. Both intercompany amounts in group currency and the quantity of greenhouse gas are eliminated at group level.

From an amount perspective, intercompany sales (1) and costs of sales (2) are eliminated in (3); unrealized profits of the same inter-company transaction are eliminated in (4).

From a greenhouse gas quantity perspective, CO2 emissions (1 and 2) of the intercompany sales are eliminated along with the GHG information in (3).

More information on our Help Portal here: Fields for Greenhouse Gas Emissions.

--
Industry scenario fields for public sector and financial services

With release 2408, we deliver on better integration with industry solutions by enhancing the data model of SAP S/4HANA for group reporting with standard fields from accounting for the banking and public sector industries. This integration provides you with the following benefits:

Integrate accounting and group reporting better by supporting more standard fields and avoiding the need to create customer fields instead
Help you, as an industry solution customer, simplify the process of consolidation by providing tools and ability to automate interorganizational currency conversions, adjustments, and eliminations entries
Provide real-time data access, allowing industry solution customer's organizations to consolidate actual data more efficiently
Provide ability to generate consolidated financial statements such as balance sheet, P&L, and cash-flow reports by industry solution–specific fields such as fund, grant, and cash origin account assignments in the case of the public sector industry solution

You can enable a new business function to activate banking/financial services and public standard fields to group reporting. The new fields are then activated in group reporting's master data.

For public sector five additional industry specific fields are supported in group reporting:

Financial Management Area
Fund
Grant
Cash Origin Chart of Accounts
Cash Origin Account

More information: Maintaining additional Public Sector fields in group reporting.

For financial services three additional industry specific fields are supported in group reporting:

Financial Services Product Group
Financial Services Branch
Financial Data Source

More information: Maintaining additional Banking Sector fields in group reporting.

--
New Fiori app to define consolidation groups

Part of our strategy of UX modernization, in 2408 you can now use the new “Define Consolidation Groups” Fiori app, which replaces the old Web GUI-based applications “Consolidation Groups – Create and Change” and “Consolidation Groups – Display” (see screenshot above).

Already existing consolidation groups created with the old apps can directly be maintained using the new “Define Consolidation Groups” Fiori app, as the persistence of the cons groups is still the same. You can still use the old apps, but they're marked as “Deprecated”, and will be removed in a later release according to our deprecation process.

More information:

--
Improved data mapping including dashboard view of jobs by status and user notifications

In release 2408, we enhance data mapping capabilities of the SAP Group Reporting Data Collection app:

Last run information in the list of jobs
User notification
New "add" option when importing data
New "OData Custom Connection" source

Last run information in the list of jobs

We improved the list of jobs in the Run Data Mapping app. Today, you have more visibility on the status of your jobs, and you can use the Data Mapping Jobs page of jobs as a dashboard (see screenshot below). The Data Mapping Jobs page contains the list of data mapping jobs, including information about job runs, such as run status, mapping status, and import status of the last run, or last successful import on, meaning the date of the last successful run which wasn't a test run. Additional columns related to the last run are the following:

Date and time of the last job run
Date and time of the last update run that was successful
Run (overall) status
Mapping status
Import status

Default sorting by date and time, with the most recently run job at the top of the list.

User notification

With the new user notification feature, your users are notified when an import job is finished. When you run an import using the Run Data Mapping app, just select the new "Notify Users" tab, choose the users to be notified, and what type of information they should receive (success, error, warning). In the example below:

tester_grdc_34 is notified of errors to be solved
tester_grdc_35 is made aware of warnings and errors to be solved
tester_grdc_37 is notified when data has been imported successfully

You can receive user notifications by mail and/or in the data mapping app itself. In addition, you can define users to be notified for multiple jobs from the list of jobs:

New "add" option when importing data

In addition to the Delete All FS Items and Sub-assignments and Overwrite update modes, you can now choose the Add update mode when importing data. In Add mode, the uploaded records are added to the existing records. In Add mode, you can upload data for multiple consolidation units and fiscal periods (of the same year), but only for one version at a time.

Use of OData (Open Data Protocol) as a source in your data mapping definition

With release 2408, we increase Data Mapping flexibility by using OData source instances to access and extract source data from a wide range of OData services. We improve user effectiveness by enabling users to read data, for example, from the ACDOCP table for planning data, and import it into the ACDOCU group reporting table. With Data Mapping you can now:

Create OData source instances in the SAP BTP Cockpit identifying OData services
Use OData service fields as input columns in mapping rules
Create OData custom connection data mapping definitions
Read source data from OData services, map it and import it into the ACDOCU group reporting table

OData is a standard web protocol used for querying and updating data. A new OData based source type OData Custom Connection can be selected in mapping definitions. You can connect to and read data from any source systems through an OData based API and process this data using the Data Mapping apps.

--
UX improvement of the Release Universal Journal

With the Release Universal Journal app, you release the reported / non consolidated financial data from the universal journal in accounting for consolidation purposes. By executing this task, data is transferred from accounting to group reporting.

Part of our UX improvement strategy, we deliver further simplification, usability enhancement, and harmonization of the release universal journal task. The UX improvement was available in release 2402 if you activated the improved feature. Today, with 2408, the feature is now activated for all customers.

With the improved UX, instead of having to go through multiple screens to release data, you can now perform "one click actions" for release options such as:

Test
Update
Test with original list
Start with selection

With the revised UX, each release universal journal task execution leads to a single task log only, even when executed for multiple consolidation units in one go. The tree display on the left hand side can be used to filter the task log entries by particular consolidation units (see screenshot below).

--
Multiple line-validation tasks on group reporting and unreleased accounting data

With release 2408.2, we help you improve efficiency in controlling data quality in different scenarios such as:

Smooth and fast group closing process by running quality checks on unreleased accounting data early, right after the accounting posting becomes available, and applying the group reporting quality definitions
Loading of remote system data into group reporting, running validations as separate tasks, and deciding to correct errors either at the source or in group reporting
Staggered data collection process, with submission and validation of different data sets at different dates (such as profit and loss first, balance sheet later)

You can validate line items in multiple tasks:

Sources: Group reporting data selected from posting level blank and 0C; Unreleased accounting data
Validation scopes: Existing breakdown checks; Existing line-item validation rules from the business context "group reporting journal entry"
Other abilities: Define multiple tasks; Define the data source per task; Assign a data selection object to the task

--
Support different amounts with the same key in local and group currency

In group reporting it is now possible to release data from accounting with different amounts in the local currency and group currency fields, even though the local currency key equals the group currency key. This is because, for example, the translation from the transaction currency to the local currency and to the group currency can use different exchange rates.

Before the 2408 release these value differences caused issues during the calculation of the net income in the next year. Hence, you had to correct the group currency value by posting a manual correction. As of release 2408, these differences can be reconciled automatically. For this purpose, the following features have been enhanced:

Calculation of the Net Income: The net income is calculated in local currency and in group currency. If the reported data shows differences, this will result in differences in the calculated net income
Currency translation: The option Reconcile LC with GC in standard version is available now in the currency translation method.
Reclassification: When a reclassification triggers the calculation of the net income, the net income is calculated in local currency and in group currency.

More information: Supporting Different Amounts with Same Key in Local Currency and Group Currency.

--
More information

Find Release Information & Content with the Release Navigator for SAP S/4HANA Cloud Public Edition

2024-08-29T16:49:44.261000+02:00

If you’re a customer using SAP S/4HANA Cloud Public Edition, you won’t want to miss our upcoming virtual session on the Release Navigator offered by the SAP Enterprise Support Academy. This powerful tool is designed to simplify the process of finding release information and content, allowing you to stay informed and prepared for upcoming updates.

Join us for an interactive virtual live session where we’ll walk you through the features and benefits of the Release Navigator. Discover how this tool provides a comprehensive view of upcoming releases, allowing you to easily plan and prepare for updates. You’ll also learn how to find release scheduling and maintenance windows within the release navigator, enabling you to better plan for and manage the deployment of updates.

But that’s not all – we’ll also show you how to simplify the release process by utilizing consolidated content from SAP experts found inside the release navigator. This means you can access all the information you need in one centralized platform, saving you time and effort when it comes to staying on top of the latest updates and enhancements.

Whether you’re new to the release navigator or looking to enhance your existing knowledge, this virtual session is for you. Our experienced presenters will provide valuable insights and practical tips that you can immediately apply to your daily operations.

Don’t miss out on this opportunity to take your release management to the next level. Register now to secure your spot in the upcoming virtual session and unlock the full potential of the Release Navigator for SAP S/4HANA Cloud Public Edition. We look forward to seeing you there!

Please note:
Before you can access the link to the Meet-the-Expert session, a one-time registration in SAP Learning Hub, edition for SAP Enterprise Support, is required. A detailed step-by step guide to registration can be found here.

Find Release Information & Content with the Release Navigator for SAP S/4HANA Cloud Public Edition

SAP Maintenance Assistant 2408 Now Available – What’s New?

2024-08-29T22:35:17.561000+02:00

The SAP Mobile Service and Asset Management team is pleased to share details of the latest release of SAP Maintenance Assistant, version 2408, the mobile maintenance execution solution for SAP S/4HANA Cloud.

Our latest update update enhances efficiency for plant maintenance technicians with improved time reporting, streamlined equipment management, and intuitive data input. For backend administrators, it offers better monitoring tools, faster data synchronization, and advanced reporting capabilities.

Features delivered in the 2408 release

Install and dismantle equipment

Installing and dismantling equipment is a common part of asset maintenance as some equipment requires periodic overhauls, which involve dismantling and replacing significant components. Using the mobile application during configuration and replacement processes helps ensure the equipment hierarchy is recorded properly in the master data

Installation and dismantling may be initiated in the mobile app from any functional location or equipment detail page. The technician can then verify the parent/child relationship of newly installed or dismantled equipment using the hierarchy view.

Operation page improvements

Continuing our work toward modernizing the SAP Maintenance Assistant user experience, operation details pages have been updated to improve efficiency. Sections have been reorganized to prioritize the most relevant information for the technician.

Common objects are represented by new colorful icons to easily differentiate the type, e.g., maintenance order, technical object, etc.

Documents are now shown individually in a dedicated section on the detail page accompanied by a document preview. The attachment may be opened and viewed, and new attachments added without navigating to a separate page.

Measurement readings with editable data table

The new editable data table functionality transforms data input by enabling direct value entry and swift handling of multiple records. Users now can seamlessly input measurement point values directly into the table, significantly expediting workflows, especially when dealing with tasks involving multiple records, such as recording results for inspections.

This table supports various input controls — text, lists, numbers, switches, and buttons — providing a versatile toolkit for efficient data handling, and the option to designate a sticky column facilitates smooth horizontal and vertical scrolling while ensuring crucial data remains visible regardless of navigation.

Fiori applications

Two new Fiori applications are now available to provide greater visibility for administrators into activities on the mobile device.

Monitor Communication Session History enables investigations into the length of initial and delta synchronizations. An administrator can monitor the communication sessions between the mobile client and the backend system and filter for user communication sessions.

Monitor Data Object Mobile Status History can be used app to monitor business objects that were changed in the mobile app.

Optimized delta synchronization

The latest release introduces updates designed to streamline the synchronization process. This enhancement refines the delta synchronization workflow by identifying and targeting only entities that have undergone changes since the last synchronization.

By default, when users trigger delta synchronization, the application initiates an upload of locally created transactions. Subsequently, an interactive call efficiently identifies entities requiring updates or modifications since the previous synchronization. Delta synchronization then exclusively targets these altered entities, eliminating redundant sync actions and significantly optimizing the duration required for the synchronization process.

This optimization ensures that only pertinent data is synchronized, enhancing efficiency, and minimizing the time and resources required for delta synchronization.

Support for CDS Views

CDS (Core Data Services) views are standardized and reusable data models that can be leveraged across various SAP applications. With support in this release, customers may generate a report of mobile transaction history for a set of business object types, mobile users, or mobile applications.

Data points from the mobile application can be used to build intelligent operational dashboards. For example, understanding the meantime to repair and meantime to complete the work can provide valuable insights into technician productivity.

For customers using SAP Analytics Cloud, the SAP Maintenance Assistant CDS view is available as a data source.

Learn more about Integration with SAP Analytics Cloud using MAIF data sources

Release available now

SAP Maintenance Assistant is available now. The application is publicly available and includes an offline demo mode for viewing and testing the functionality. The application may be downloaded from the Apple App Store and Google Play Store.

Submit innovation requests

We encourage you to visit the SAP Mobile Service and Asset Management Customer Influence portal to submit improvement requests. Use the "SAP Maintenance Assistant for S/4HANA Public Cloud" category to properly direct your request.

Explore other SAP mobile applications

SAP has a powerful suite of SAP native mobile applications. Visit the SAP Mobile Experience community for the latest updates.

SAP Community - SAP S/4HANA Public Cloud

SAP Named a Leader in the 2024 Gartner® Magic Quadrant™ for Recurring Billing Applications

How to adopt Group Reporting for existing public cloud accounting customers

Extensibility Approaches in SAP S/4HANA Cloud Public Edition

Key User Extensibility

On-Stack/Developer Extensibility

Side-by-Side Extensibility

Research & Development Engineering in SAP S/4HANA Cloud Public Edition 2408

SAP Product Lifecycle Management Solution Integration with SAP S/4HANA Cloud

Configure Handovers

Hand Over Engineering Bills of Material (EBOM)

Task Monitoring for Handovers

SAP PLM Integration to SAP S/4HANA Cloud Public Edition Demo

New App in BOM Management: Maintain Bills of Material (Version 2)

Maintain Subitems in Manage Order Bill of Material (Version 2) App

New App in BOM Management: Maintain WBS Bills of Material

Usability Feature in Manage Multilevel Bill of Material App

Manage Change Record (Version 2) App

Flexible Workflow

Transportation Management for SAP S/4HANA Cloud Public Edition 2408

Integration of Returns Purchase Orders withTransportation Management

Configuration

Integration of Returns Purchase Orders withTransportation Management - Demo

Delivery Deletion Initiated from Transportation Management

Enhancements for Consignment Orders in theOutbound Process

Execution status as an indicator for creating and deleting consignment order documents

No further changes allowed after sending of ASN or checkout of freight order

Deletion of the consignment order after removal of assignment to freight order

Freight Cost Calculation based on Material Freight Group and Transportation Group

Billing of Freight Cost for Batch-Managed Material

Refinement of Freight Settlement Initiation for Advanced Intercompany Processes

Enhancement of the Form Data Provider for the WAYBILL Output Type

Third-Party Warehouse Management with Transportation Management - Advanced Integration Scenario

Warehouse Outbound Processing with External Transportation Planning - Advanced Integration Scenario

Task Tutorials + Learning Content for Transportation Management with 2408 Release

Key User Extensibility and Developer Extensibility for Carbon Footprint Category Breakdown

Introduction

Prerequisites

Learning Recommendation

User Roles

Key User Extensibility

Create Custom Field to Display the CO2e Category Breakdown in Your Purchase Requisition Item

Create Custom Logic

Developer Extensibility

使用Availability Check Horizon来管理ATP

ビジネスコンテンツ「 Finance Foundation for SAP S/4HANA and S/4HANA Cloud」を実装してみよう！

はじめに

手順

SAP S/4HANA Cloudでの手順

4. セマンティックタグの割り当て

SAP Datasphereの手順

ビジネスコンテンツのインポート

SAP S/4HANA Cloudとの接続作成

ローカルテーブルのデータ型変更

複製フローの作成

データフローの作成

ビュー・分析モデルのデプロイ

SAP Analytics Cloudでの手順

ビジネスコンテンツのインポート​

ストーリーの確認

さいごに

ABAP Cloud Sessions at SAP TechEd in 2024

Keynotes

Track Overviews

Lectures

Jump-Starts

SAP Field Service Management 2408: Generative AI, Enhanced User Experience, and Improved Integration

How to perform mass upload from an Excel file in a FIORI App in SAP BTP ABAP Environment - Part 2

Introduction

Prerequisites

Basic of OData V4 Operation

RAP - Non-Standard Operations

Can we create unbound OData V4 operations "Action Import" or "Function Import" in RAP?

How RAP Static Action and Functions are related to the complete entity?

Let's begin

Custom Action in the Table toolbar for the list report in OData V2 vs OData V4:

Further Reference: Adding Custom Actions Using Extension Points

But why do we need a controller extension? Can't we use the custom action handler function created automatically by the Guided Development tool in an OData V4 app?

Electronic Invoices for Malaysia: A Guide for Communication Settings

Getting Started

Integration of Returns Purchase Orders with
Transportation Management

Integration of Returns Purchase Orders with
Transportation Management - Demo

Enhancements for Consignment Orders in the
Outbound Process

ビジネスコンテンツのインポート

--
Group financial statement review booklet improved with commenting and calculated measures

--
Group-level Green Ledger: managing greenhouse gas emissions for group reporting

--
Industry scenario fields for public sector and financial services

--
New Fiori app to define consolidation groups

--
Improved data mapping including dashboard view of jobs by status and user notifications

--
UX improvement of the Release Universal Journal

--
Multiple line-validation tasks on group reporting and unreleased accounting data

--
Support different amounts with the same key in local and group currency

--
More information

Please note:
Before you can access the link to the Meet-the-Expert session, a one-time registration in SAP Learning Hub, edition for SAP Enterprise Support, is required. A detailed step-by step guide to registration can be found here.