Co-author: anil.kumar.k.r
Welcome to the Two-Tier ERP innovation updates with SAP S/4HANA Cloud 2111 Release.
SAP’s vision is to enable customers transform their business into “Intelligent” and “Sustainable” Enterprises. With this vision we see some interesting scenario innovations in Two-Tier ERP with SAP S/4HANA Cloud 2111 release.
SAP Intelligent Real Estate supports all key future focus topics including space management, remote work, sustainability, cloud & analytics. With SAP Intelligent Real Estate, we get centralized master data model in the cloud which enables end-to-end real estate business processes between headquarter & subsidiary companies for commercial & corporate requirements.
Customers can make intelligent leasing decisions with embedded analytics and best in class contract & lease management solution from SAP S/4HANA Cloud & on-premise systems. We get real estate-based controlling and profit-center accounting, integration with asset accounting, new SAP Fiori apps for usage and occupancy management to support different business scenarios (such as external lease-out, internal occupancy, and intercompany lease out of spaces). New Fiori apps makes leasing more transparent and helps make intelligent lease decisions. We get embedded analytics with Dashboards for Contract & Lease management.
Next scenario innovation is about managing the “green line” to address climate change. Sustainable, intelligent enterprises manage their "green line" to reduce their carbon footprint. SAP Product Footprint Management is SAP Cloud-native application to calculate product footprints periodically and at scale considering the entire product lifecycle. Now, business users can replicate business-activity and master data from subsidiary company on SAP S/4HANA Cloud and Headquarter company on SAP S/4HANA on premise to SAP Product Footprint Management as a primary source for product footprint calculation based on a specified set of plants and a time range. After the footprint calculations, we get inbuild integration back to SAP S/4HANA Cloud and on-premise systems.
Within SAP S/4HANA Cloud system - Fiori application “View Product Footprints” allows you to search for product footprints and provides highlight of product footprints in other Fiori applications also.
For the product deep dive, you can read the blog post here. You can find a detailed video with a system demo here.
Next, we get innovations in Financial planning with integration of SAP IBP (Integrated Business Planning) with Finance data from SAP S/4HANA Cloud and on Premise on SAP Analytics Cloud. This improves the quality of sales and profitability planning in SAP Analytics Cloud for Headquarter and Subsidiary companies.
To learn more on what's new with Integrated Financial Planning click here.
In this scenario you get direct delivery of service from subsidiary to customer against a purchase order in headquarter in Two-Tier Model.
The process starts with customer walking into the Retailer stores or reaching out to Service Provided/Reseller with product complaint. Subsidiary receive the customer material through post good receipt and places it under customer stock. Customer Service Representative creates an In-House Repair to add the repair product and the serial number received from the customer.
Perform Pre-check is performed to assess the repair. As an optional process, additional products are required or out of warranty service, Repair quotation is generated for customer’s approval.
Repair Order is created with addition of part to be procured. Post confirmation of the Repair Order – Purchase requisition is created and automatically converted to Purchase order through background schedule purchase order creation job.
Purchase order is created with vendor as Headquarters. EDI output type in the purchase order send the details to Cloud integration. Integration flow created using standard artefacts help create a Sales order in OEM system with reference document as purchase order.
Similarly, EDI output from Sales Order triggers another Integration Flow for updating the purchase order, in the confirmations tab, with Sales order details. Subsequent Delivery creation – Post Good Issue from headquarters is done. Inbound delivery is created against the purchase order in subsidiary.
Repair confirmation is done against the repair order created. Goods issue is done to the end customer and Invoice created from the subsidiary. For more details, read the blog post here.
The process starts with customer walking into the Retailer stores or reaching out to Service Provided/Reseller for requirement of product along with installation at the location. Subsidiary receive the customer’s order and creates a Solution Order with Sales and Service Material.
Upon release of the Sales line item, Sales Order is created, based on the orchestration, with Purchase requisition and is automatically converted to Purchase order through background schedule purchase order creation job.
Purchase order is created with vendor as Headquarters. EDI output type in the purchase order send the details to Cloud integration. Integration flow created using standard artefacts help create a Sales order in OEM system with reference document as purchase order.
Similarly, EDI output from Sales Order triggers another Integration Flow for updating the purchase order, in the confirmations tab, with Sales order details. Subsequent Delivery creation – Post Good Issue from headquarters is done. Inbound delivery is created against the purchase order in subsidiary.
Sales Invoice is created in the Subsidiary for the end customer. Subsidiary release the Service line item which creates the service order. The service order is replicated to Field Service Management wherein an agent is assigned. Installation of the product is done and service confirmation sent back to the subsidiary for invoicing, if necessary.
Billing document is created at headquarters and bill to subsidiary, corresponding Supplier invoice will be created automatically at subsidiary.
Learn more here.
Two-Tier ERP Accelerators can be downloaded from Best Practice Explorer as shown in below screenshot.
Apart from the above scenario highlights, you can find several APIs to facilitate Two-Tier ERP deployment here.
You can learn more about our innovation scenarios with detailed videos and demos with our new Two-Tier ERP Microlearning channel.
Do stay tuned with the latest release updates, stay safe and stay healthy.
Welcome to the Two-Tier ERP innovation updates with SAP S/4HANA Cloud 2111 Release.
SAP’s vision is to enable customers transform their business into “Intelligent” and “Sustainable” Enterprises. With this vision we see some interesting scenario innovations in Two-Tier ERP with SAP S/4HANA Cloud 2111 release.
Intelligent Real Estate
SAP Intelligent Real Estate supports all key future focus topics including space management, remote work, sustainability, cloud & analytics. With SAP Intelligent Real Estate, we get centralized master data model in the cloud which enables end-to-end real estate business processes between headquarter & subsidiary companies for commercial & corporate requirements.
Customers can make intelligent leasing decisions with embedded analytics and best in class contract & lease management solution from SAP S/4HANA Cloud & on-premise systems. We get real estate-based controlling and profit-center accounting, integration with asset accounting, new SAP Fiori apps for usage and occupancy management to support different business scenarios (such as external lease-out, internal occupancy, and intercompany lease out of spaces). New Fiori apps makes leasing more transparent and helps make intelligent lease decisions. We get embedded analytics with Dashboards for Contract & Lease management.
Product Footprint Management
Next scenario innovation is about managing the “green line” to address climate change. Sustainable, intelligent enterprises manage their "green line" to reduce their carbon footprint. SAP Product Footprint Management is SAP Cloud-native application to calculate product footprints periodically and at scale considering the entire product lifecycle. Now, business users can replicate business-activity and master data from subsidiary company on SAP S/4HANA Cloud and Headquarter company on SAP S/4HANA on premise to SAP Product Footprint Management as a primary source for product footprint calculation based on a specified set of plants and a time range. After the footprint calculations, we get inbuild integration back to SAP S/4HANA Cloud and on-premise systems.
Within SAP S/4HANA Cloud system - Fiori application “View Product Footprints” allows you to search for product footprints and provides highlight of product footprints in other Fiori applications also.
For the product deep dive, you can read the blog post here. You can find a detailed video with a system demo here.
Financial Planning with SAP IBP Integration
Next, we get innovations in Financial planning with integration of SAP IBP (Integrated Business Planning) with Finance data from SAP S/4HANA Cloud and on Premise on SAP Analytics Cloud. This improves the quality of sales and profitability planning in SAP Analytics Cloud for Headquarter and Subsidiary companies.
To learn more on what's new with Integrated Financial Planning click here.
Repair Order Integration
In this scenario you get direct delivery of service from subsidiary to customer against a purchase order in headquarter in Two-Tier Model.
The process starts with customer walking into the Retailer stores or reaching out to Service Provided/Reseller with product complaint. Subsidiary receive the customer material through post good receipt and places it under customer stock. Customer Service Representative creates an In-House Repair to add the repair product and the serial number received from the customer.Perform Pre-check is performed to assess the repair. As an optional process, additional products are required or out of warranty service, Repair quotation is generated for customer’s approval.
Repair Order is created with addition of part to be procured. Post confirmation of the Repair Order – Purchase requisition is created and automatically converted to Purchase order through background schedule purchase order creation job.
Purchase order is created with vendor as Headquarters. EDI output type in the purchase order send the details to Cloud integration. Integration flow created using standard artefacts help create a Sales order in OEM system with reference document as purchase order.
Similarly, EDI output from Sales Order triggers another Integration Flow for updating the purchase order, in the confirmations tab, with Sales order details. Subsequent Delivery creation – Post Good Issue from headquarters is done. Inbound delivery is created against the purchase order in subsidiary.
Repair confirmation is done against the repair order created. Goods issue is done to the end customer and Invoice created from the subsidiary. For more details, read the blog post here.
Sales and Installation process
In this scenario, you get direct delivery of service from subsidiary to customer against a purchase order in headquarter in Two-Tier Model.
The process starts with customer walking into the Retailer stores or reaching out to Service Provided/Reseller for requirement of product along with installation at the location. Subsidiary receive the customer’s order and creates a Solution Order with Sales and Service Material.
Upon release of the Sales line item, Sales Order is created, based on the orchestration, with Purchase requisition and is automatically converted to Purchase order through background schedule purchase order creation job.
Purchase order is created with vendor as Headquarters. EDI output type in the purchase order send the details to Cloud integration. Integration flow created using standard artefacts help create a Sales order in OEM system with reference document as purchase order.
Similarly, EDI output from Sales Order triggers another Integration Flow for updating the purchase order, in the confirmations tab, with Sales order details. Subsequent Delivery creation – Post Good Issue from headquarters is done. Inbound delivery is created against the purchase order in subsidiary.
Sales Invoice is created in the Subsidiary for the end customer. Subsidiary release the Service line item which creates the service order. The service order is replicated to Field Service Management wherein an agent is assigned. Installation of the product is done and service confirmation sent back to the subsidiary for invoicing, if necessary.
Billing document is created at headquarters and bill to subsidiary, corresponding Supplier invoice will be created automatically at subsidiary.
Learn more here.
Scope items
Accelerators
Two-Tier ERP Accelerators can be downloaded from Best Practice Explorer as shown in below screenshot.
Whitelisted APIs
Apart from the above scenario highlights, you can find several APIs to facilitate Two-Tier ERP deployment here.
Two Tier ERP Microlearning
You can learn more about our innovation scenarios with detailed videos and demos with our new Two-Tier ERP Microlearning channel.
Do stay tuned with the latest release updates, stay safe and stay healthy.
More Information on SAP S/4HANA Cloud:
- SAP S/4HANA Cloud release info here
- jan.gilg SAP News article here
- Latest SAP S/4HANA Cloud Release Blog Posts here and previous release highlights here
- Product videos on our SAP S/4HANA Cloud and SAP S/4HANA YouTube playlist
- SAP S/4HANA PSCC Digital Enablement Wheel here
- Early Release Webinar Series here
- Inside SAP S/4HANA Podcast here
- openSAP Microlearnings for SAP S/4HANA here
- Best practices for SAP S/4HANA Cloud here
- SAP S/4HANA Cloud Community: here
- Feature Scope Description here
- What’s New here
- Help Portal Product Page here
- Implementation Portal here
- Two-Tier ERP with SAP S/4HANA Cloud 2108 Release here
- SAP Managed Tags:
