SAP S/4HANA 2021 – Feature Pack Stack 1 (FPS01) – Part 2
In a 2021 survey, 55% of European companies stated the COVID-19 pandemic has increased the demand for digitalization, and 46% of companies reported that they have grown more digital. For more information, see the report here. This digital transformation provides the industry with unparalleled opportunities for value creation. For example, Last-Mile Deliveries has changed forever and is going to be one of the biggest challenges as new technologies must be introduced to save time, reduce operational costs, and enhance the customer experience.
In this blog, learning about how the new innovations shipped with SAP S/4HANA 2021 FPS01 can help here concerning the Consumers Products Industry.
The blog is built as a series of 2 parts and present the key highlights for:
- Part 1: Lines of business
- Part 2: Industries
In the following second part, I will go into details for selected innovations for industries that are new with the latest release SAP S/4HANA 2021 FPS01.
Last Mile Distribution for Direct Distribution: Support of bank deposits for collected payments during route execution.
Last Mile Distribution supports the distribution of ordered goods directly to the final points of sale. Manufacturers and suppliers of different consumer goods industries can coordinate all phases of the distribution process centrally.
Last Mile Distribution enables manufacturers and suppliers of different consumer goods to coordinate the distribution of goods to the final point of sale (POS), such as retail stores or mom-and-pop stores: from route preparation to route execution through to route settlement. It represents an alternative approach to central retail deliveries for delivering goods to stores. Last Mile Distribution is most suitable for supporting the needs of consumer goods companies involved in the production of food and beverages, as well as the needs of tobacco and oil and gas companies.
Now with SAP S/4HANA 2021 FPS01, we bring innovations in four areas to support bank deposits for collected payments during route execution.
Capture and Settle Bank Deposits:
This feature enables settlement clerks to capture collected payments and bank deposits. During the settlement run, bank deposits are posted from driver clearing accounts to bank clearing accounts.
To minimize the necessity of transporting large amounts of cash, during route execution, delivery drivers and van sellers deposit collected payments at banks. After each bank deposit stop, drivers can upload the bank deposit information from a mobile device or record the information on printed documents. Any remaining payments are handed over at check-in.
If an intermediate settlement is enabled, the settlement of individual stops takes place directly after the completion of the respective stops during route execution. If bank deposit documents have been uploaded with route data, they are mapped to freight order documents and updated in the back-end system.
Manage Bank Deposit Postings Through Configuration
With this feature, you can activate and/or deactivate bank deposit postings and define appropriate reconciliation accounts.
During route execution, drivers can deposit collected payments at one or more banks to avoid carrying large sums of money.
Upload Bank Deposit Information
With this feature, bank deposit information can be recorded on mobile devices and uploaded during route execution or on completion of a route.
The OData (V2) service Mobile Data for Last Mile Distribution (LMD_MA) is used to send information to mobile devices that are required for route execution and to return information about delivery and van sales route activities. Furthermore, this service is used to download configuration data that is required to record activities on mobile devices.
This API is available on the SAP API Business Hub (https://api.sap.com/Information published on the SAP site).
To minimize the necessity of transporting large amounts of cash, during route execution, delivery drivers and van sellers deposit collected payments at banks. It is now possible for delivery drivers and van sellers to record information related to bank deposits on a mobile device and to upload this information during route execution or on completion of a route.
If an intermediate settlement is enabled, the bank deposit stops can be settled before completion of a route, which speeds up revenue postings and reduces work peaks in the system.
Furthermore, this feature supports the download of deposit account references, which are configured in the back-end system and can be chosen by delivery drivers and van sellers when they record bank deposit information.
Manage Driver Accounts for Manual or Automatic Clearing of all Collected Payments
With this feature, during settlement, all collected payments that are posted contain a reference to the corresponding route or document, for example, a deposit slip. This information is used to support account clearing in SAP S/4HANA Finance.
When payments are posted to driver accounts, a reference number, such as a route ID or a bank deposit number, is added to the driver account. Customers can use this reference to clear payments in SAP S/4HANA Finance. Payments can be cleared both manually or automatically:
- When payments are cleared manually, an accountant verifies if payment receipts on customer accounts correspond to invoices by taking into account the reference number.
- When payments are cleared automatically, a report such as the Automatic Clearing report (transaction F.13) is used to go through customer accounts, for example, by using the reference number.
Last Mile Distribution for Direct Distribution: Truck-to-truck transfer of products on delivery and van sales routes
A delivery transfer is a movement of ordered goods from one vehicle to another vehicle during the execution of a delivery route because the first vehicle is not able to carry out the delivery. The delivery is added to the route of the second vehicle and removed from the initial route. The driver of the first vehicle might also deposit deliveries at a temporary storage location where another driver can later load the deliveries onto a second vehicle.
With the new SAP S/4HANA 2021 FPS01, we have now:
Drivers can transfer route stock and deliveries from one route to another route during route execution.
Delivery drivers can transfer deliveries between two routes to ensure the timely delivery of goods, for example, when vehicles are delayed (delivery transfers). Van sellers can transfer stock between two routes to ensure stock availability on van sales routes, for example, when there is a high demand for specific products (stock transfers).
The transfers are modeled as stops and can be recorded on the issuing and the receiving route under the stop type TRANSFER, or VISIT for delivery transfers in offline mode. Issuing and receiving documents must be created for the routes. Optionally, the issuing and receiving route ID can be specified in the issuing/receiving route stock transfer document.
Execution of Van Sales Routes
Van sellers sell products on van sales routes based on the information collected during route preparation. All activities related to the execution of a van sales route are recorded on mobile devices, and this information is used to settle routes.
Route stock management capabilities provide full visibility of stock during each step of a van sales route, from the completion of loading activities at a warehouse, stock transfer at check-out, customer visits, stock transfer at check-in, up to final route settlement.
Fashion and Vertical Business
This solution enables fashion retailers and vertical fashion companies to manage their business processes across one large data system landscape. It also enables the companies in the fashion industry to use the power of in-memory computing to analyze large data volumes for a fast and accurate overview of products. This results in greater efficiency, quicker time to market, and better inventory control.
Manage Master Planned Orders app – enabling users to create, manage, and monitor master-planned orders
With this new SAP Fiori app, you can view the details of planned orders at master, individual, and combined production order levels. In addition, you can use this app to create master-planned orders from individual planned orders and combined planned orders from master-planned orders.
Picture 1: Improve planning and decision-making through enhanced visibility into the overall progress of master-planned orders.
You can use this app to do the following:
- View details of planned orders at master, individual, and combined planned orders levels.
- View the overall conversion status at the master-planned orders or combined planned orders level.
- Create master-planned orders from individual planned orders and combined planned orders from master-planned orders.
- Notify about the completion of background jobs scheduled for the creation of master-planned orders and combined planned orders.
In addition, the app supports the following technical features and options:
- View the logs and the details corresponding to each scheduled job run using the Job Overview app.
For more information, see App Implementation: Manage Master Planned Orders – Fashion.
Purchase-order management and consolidation updates
With the “Manage Purchase Orders” SAP Fiori app, you can display the selected open purchase order details at header, generic product, and item levels, so you can get a complete view of different items in these orders before you can edit these items or consolidate them into a new or existing purchase order.
Now with the new release, you can define consolidation rules to flexibly control whether the consolidated items are to be created in an existing purchase order or in a new purchase order.
For more information, see App Implementation: Configure Purchase Order Consolidation Rule.
Option to ignore a batch split for inbound deliveries
You can enable the system to check whether the batch entered in the inbound delivery document already exists in the system. A batch split describes the situation where more than one batch is used to cover a particular delivery item. The batch split function in the delivery includes a batch selection screen and an availability check.
Now with this new release, you can Ignore Batch Split.
This means, during inbound delivery creation, you can enable the system to ignore the batch split for documents with segmented materials or articles of segmentation scope 1. This only applies to delivery documents with document category 7 (Delivery/Shipping Notification).
For more information, see Batch Determination for Inbound Deliveries.
Retail for Merchandise Management
SAP S/4HANA Retail for merchandise management is an end-to-end solution that supports companies with retail processes across the entire retail value chain.
Integration for merchandise categories and merchandise category hierarchies
OData API: Merchandise Category (A2X)
You can use this OData service to integrate external applications to create and maintain merchandise category data. This service enables you to create, read, update, and delete merchandise category data. It includes merchandise category description, assignment of characteristics to merchandise category, assignment of merchandise category to merchandise category hierarchy node, and characteristic value restriction.
This API is available on the SAP API Business Hub (https://api.sap.com/Information published on the SAP site).
OData API: Merchandise Category Hierarchy Node (A2X)
You can use this OData service to integrate external applications to create and maintain merchandise category hierarchy node data. This service enables you to create, read, update, and delete merchandise category hierarchy node data. It includes merchandise category hierarchy node description, assignment of characteristic to merchandise category hierarchy node, assignment of merchandise category hierarchy node to merchandise category hierarchy node, and characteristic value restriction.
For more information, see Merchandise Category Hierarchy Node (A2X).
App Extensibility for Count Stock Ad hoc
With this feature, you can enhance the print form in the Count Stock Ad hoc application depending on your store requirement. You can add more fields in the print form header and product details to provide more information on count stock documents to store associates.
For more information, see App Extensibility: Count Stock Ad hoc (Key User).
Insurance provides advanced claims, policy, and billing management capabilities insurers need to improve efficiency, profitability, and customer loyalty. It enables insurers to implement best-in-class business processes.
SAP Fiori apps for maintaining claim items and participants in claims management
Support for changes to claims by insurance agents or claims clerks through a set of SAP Fiori apps:
One central cockpit for changing claims in the SAP Fiori app (variant) “Claims Inquiry and Update Claim” with improved and extended functionality.
Two new SAP Fiori apps for maintaining additional subjects of a claim:
- Maintain Claim Items: You can use the new Maintain Claim Items app to create, search for, edit and delete claim items at the claim header and sub claim level on an SAP Fiori interface. Furthermore, you can create a payment for a claim item
- Maintain Participants: You can use the new Maintain Participants app to quickly create, edit and delete participants for a claim subobject on an SAP Fiori interface. You can search for and display existing participants. If you do not save the data during creating or editing a participant the system automatically saves the entered data in a draft version. You can search for existing participants (including draft versions) using several search criteria (such as business partner name, participant role, claim number).
Improvements to existing SAP Fiori apps for changing claims:
- Maintain Payments: You can now park a payment in the existing Maintain Payments app if you want to enter a payment, but not post it and pay it out until some time later. The payment will then be parked in Claims Management and not be posted in the Collections and Disbursements system. You can still edit the payment details of the parked payments, such as the payment amount or the payee
Apps based on SAP Fiori elements using the ABAP RESTful application programming model to access claims management in back-end systems.
Picture 2: Improved usability while maintaining insurance claims.
First Notice of Loss SAP Fiori app extended by draft number and coverage-referral logic in claims management in SAP S/4HANA
The First Notice of Loss app has been enhanced with the following additional features:
- Draft claims will now be saved with a temporary unique ID. Furthermore, you can search for these draft claim IDs using search criteria.
- You can use the new Final Payment checkbox in the Payment Details section to mark your payment as final during straight-through payments. However, a parked payment request will be created if the system encounters a coverage referral during the claim processing.
- If you enter a payment amount during the claim creation which exceeds the payment limit configured in Customizing, no straight-through payment is possible. The system creates a parked payment request for the claim instead.
Picture 3: Capture data in a flexible sequence that accommodates the order in which the reporter provides the claim information.
Integration from the financial services accelerator to claims management extended by participant information
With the SAP S/4HANA 2021 FPS01 release, we made an update on existing integration functionality. It is now possible to also replicate participant data for an insurance claim from Claims Management to customer portals such as SAP Commerce. This allows the customer to view various participants in the claim, their roles, and other data, such as the participant’s full name, address, and contact details in SAP Commerce, Financial Services Accelerator (FSA).
The Public Sector industry provides solutions for activities and services provided by public authorities at the federal, state, and municipal level. Solutions are provided for the financial management of services, incomes, taxes, and applications in conjunction with citizens and commercial organizations. The Public Sector Management (PSM) solutions are designed to manage the government income and expenditure budget.
Communication between SAP S/4HANA and SAP Analytics Cloud through standard OData services for public sector management
This feature enables you to use the standard OData service for PSM Funds Management master data (funds management area, funded program, commitment item, funds center, fund, budget period, grant, functional area, and the master data hierarchies).
For more information, see APIs for Funds Management.
Risk score integration to SAP Marketing Cloud
The risk score values for the corresponding customers in each Behavioral Insights scenario can be exported to and updated in SAP Marketing Cloud. This information can then be used for segmentation and target group building in SAP Marketing Cloud.
- Intuitively push machine-learning–generated risk scores to the SAP Marketing Cloud solution as marketing attributes
- Use these and other marketing attributes to segment customers into target groups
- Use target groups to build personalized omnichannel campaigns
- Leverage this integration layer, which uses open APIs and is easy to set up and administer
SAP S/4HANA for behavioral insights (abbreviated to Behavioral Insights) allows organizations, such as government agencies and companies to analyze the behavior of customers and to generate risk scores and insights for multiple scenarios. It provides an expanded overview of events, which enables the organization to perform efficient and reliable analysis of the customer so that they can make informed decisions and take appropriate action.
For information about setting up Behavioral Insights integration with SAP Marketing Cloud, see Integration with SAP Marketing Cloud.
Loading of planning data (stored in central planning ACDOCP) into public sector management budgeting (BCS)
Ability to load data from central planning (stored in ACDOCP) into public sector management budgeting in funds management, which can be done by:
- Planning category
- Financial ledger
- Account assignments
The transaction FMCYCOPI_CO (Transfer of CO Planning Data to BCS) has been enhanced, and you can now use it to read the plan data line items in the table ACDOCP.
The screen is updated as follows:
- If the ledger and planning category have been entered, the program reads from ACDOCP, otherwise, it reads from COSS/CSOP (controlling planning data).
See also the pilot note 3100868 Information published on the SAP site, which is valid for S4H OP 2020 and 2021.
See also the blog from Ekaterina Ivanova with more details about the recent innovations concerning SAP Public Sector Budget Planning & Analytics here.
Thanks for reading this blog post. Stay tuned!
If you are also interested in the innovations delivered with SAP S/4HANA 2021, I would like to draw your attention to my link collection blog – The Link Collection
If you want to learn more and actively engage with SAP subject matter experts on SAP S/4HANA Cloud, join our SAP S/4HANA Cloud Customer Community. This platform which is available to SAP S/4HANA Cloud customers and partners has a clear mission: deliver an interactive community to engage with one another about best practices and product solutions.
For more information on SAP S/4HANA Cloud and SAP S/4HANA 2021, check out the following links:
- SAP S/4HANA release info: sap.com/s4hana
- SAP S/4HANA Community here
- The Link Collection for Product Compliance here
- SAP S/4HANA PSCC Digital Enablement Wheel here
- Inside SAP S/4HANA Podcast here
- Join the SAP S/4HANA Movement
- Best practices for SAP S/4HANA here
- Help Portal Product Page here
- Feature Scope Description here
- What’s New here
Follow us via @SAP and #S4HANA, or myself via @VoglerChrist and LinkedIn