SAP Community - SAP S/4HANA Public Cloud

Return to Supplier in SAP S4HANA Cloud Public Edition

2024-05-02T09:00:09.508000+02:00

Hope this blog can address most return / reversal goods movement scenarios in Procurement. Different movement type representing the following 3 reversal scenarios respectfully and we will also talk about the advanced return management.

Return Delivery

Cancellation of material document

Basic Return to Supplier

Advanced Returns Management

Return Delivery

Movement type 122 with the reason for return movement specified referencing original material document.

After posting the return delivery, we can see the material document with movement type 122 (Return delivery to vendor).

Cancellation of material document

Movement type 102 representing the reversal of original material document movement type 101.

Re-order 10 PCs of material 94 and cancel the material document, here is the history review. Movement type 102 (Goods receipt for purchase order into warehouse - reversal) is shown as below.

Basic Return to Supplier

Material document with movement type 161 (Returns for purchase order)

To create a return purchase order with the order type Standard PO (NB), we need to manually set the Returns Item indicator at item level to create a return item. Return items can coexist with other order items in the same purchase order.

Step 1: Standard purchase order creation with the ‘Return’ field ticked.

Step 2: APP ‘Post Goods Receipt for Purchasing Document’ to post goods receipt on the return item.

Material document with movement type 161 (Returns for purchase order) was created as per the PO history.

Step 3: APP Create Supplier Invoice to create a Credit Memo

After posting, let’s check the accounting document.

Advanced Returns Management

Material document with movement type 161.

An advanced return purchase order should leverage the order type as Enh.Ret.to Supplier (NB2). The Returns Item indicator at item level is set automatically and cannot be removed. In this scenario, return items cannot coexist with other order items in the same purchase order. The use of a delivery is mandatory.

Step 1: Create a return order with APP ‘Create Purchase Order -Advanced.’

We will find the Return tab appear in the item details

Step 2: Transfer the quantity to be returned to the dedicated storage location (optional)

APP ‘Transfer Stock - In-Plant’

In this case, we suppose storage location 131C as the physical location to deal with return items.

Step 3: Create an outbound delivery for the return order

APP ‘My Purchase Orders - Due for Delivery (VL10B)’

We can see the outbound delivery 80000103 has been created from PO history.

Step 4: Pick and post the goods issue

APP Manage Outbound Deliveries (F0867A)

After Picking and Posting Goods Issue, the PO history was updated with movement type 161.

Step 5: Create a credit memo

APP Create Supplier Invoice (F0859)

We can see the GR/IR account was positive instead.

Step 6: Order a replacement material (Optional)

APP: Receive Replacement Materials - From Vendor

To activate this function, step 5 should be eliminated so that you can type the replacement quantity in this APP.

Let’s check the return PO overview first.

Then type in the replacement quantity, 10 PC here and click save. Replacement Purchase order 4500000435 has been created.

Step 7: Post Goods Receipt (Optional)

APP Change Inbound Delivery (VL32N)

Input the put away quantity, post goods receipt.

Step 8: Follow-Up Activities For Replacement Material (Optional)

APP: My Follow-Up Activities - For Replacement Materials (MSR_VRM_LFU)

In the ‘Logistical Follow-Up’ session, enter Follow-Up Activity: <0011 Transfer to Free Available Stock >

In the replacement purchase order history, we can see GR IR has been automatically created.

Go to the original purchase order, Return tab on the header, open the return overview:

You can see the full historical view of the return PO

More to explore:

SAP S4HANA Cloud Public Edition Logistics FAQ - SAP Community

The features covered in this article are based on SAP S/4HANA Cloud, Public Edition 2402, please refer to the latest information for changes in subsequent versions.

Hope you LIKE it if it addresses your issue. After that, please feel free to comment after following my account and I will reply ASAP.

Preliminary What’s New Information for SAP S/4HANA Cloud Public Edition 2402.3

2024-05-02T10:07:26.959000+02:00

Preliminary versions of What’s New information and of the Product Assistance are now available for customers and partners to get a preview on the upcoming new and changed features of SAP S/4HANA Cloud Public Edition 2402.3.

You can find this preview on the current Help Portal page SAP S/4HANA Cloud (see What’s New section “Preview of SAP S/4HANA Cloud 2402.3”). To access the Preliminary What’s New information, please use the What’s New Viewer or the Release Assessment and Scope Dependency (RASD) tool.

The RASD tool provides you with a personalized and tailored view on What’s New information based on the activated and used scope within your system. The preliminary information for SAP S/4HANA Cloud 2402.3 will be available in RASD within the next few days. We recommend using RASD to prepare for upgrades and updates of your system and to focus on the new and changed features that are relevant for you.

A valid S-User ID is needed to use the RASD tool and to view all the preliminary content stated above.

INFLUENCE THE DEVELOPMENT OF SAP ENTERPRISE THREAT DETECTION, CLOUD EDITION

2024-05-03T06:40:10.948000+02:00

Introducing influence page for SAP Enterprise Threat Detection, cloud edition.

The SAP Enterprise Threat Detection product team are inviting customers and partners to share their feedback and ideas to enhance our solution.

On SAP Enterprise Threat Detection, cloud edition Influence page you can see all submitted requests, submit your improvement requests, vote and comment on other ideas.

The rationale and advantages of a customer influence page include:

Augmenting customers engagement and influence on product features.
Improving product/services using meaningful customer insights.
Cultivating an engaged community.
Serving as a central platform for customer suggestions and fueling innovation.

The product team regularly evaluates the ideas and considers them for roadmap planning. Votes help to priorities ideas along with other important selection criteria such as:

DESIRABILITY: How many customers voted for this? How many customers will benefit from it?
VIABILITY: Is this Improvement Request globally relevant? Is this in alignment with SAP’s strategy for the product?
FEASIBILITY: Is the development effort realistic? Is this request achievable within the product’s architecture?

While this page is mainly for the public cloud edition, for private cloud and on-premise versions feel free to propose integration-related ideas.

Follow the steps below to get access and start sharing your enhancement ideas:

Go to SAP Enterprise Threat Detection, cloud edition Influence page.
- In case you are a new user, create a user account using S-User-ID and accept the Terms of Use. Once the user is created you activate SSO and can access without any interruption.

Follow the session to get notified of new Improvement Requests and blogs.
Vote and comment on Improvement Requests posted by other customers/ partners.
Submit new Improvement Requests.

You can also check out the videos\link below, if you wish to learn more about SAP Continuous Influence and how to submit and manage improvement requests:

Please reach us at SAP-ETD@sap.com in case of any issue.

We look forward to seeing your ideas and further improve our software as we move forward.

Assign Accounting Principles to Ledgers and Company Code: SAP Public Cloud

2024-05-03T07:50:02.826000+02:00

Leading Ledger

SAP delivers the leading ledger 0L. This ledger is updated in all company codes, that is, it's assigned to all company codes. The document numbers assigned in this ledger apply to all dependent ledgers. In each company code, the leading ledger receives exactly the same settings that apply to that company code: the currencies, the fiscal year variant, and the variant of the posting periods. For these reasons, the leading ledger can act as the global ledger for the whole entity (that is, with the valuation done according to legal reporting requirements).

Non-Leading Ledgers

Along with the leading ledger, you can have another, non-leading ledger or extension ledger. The non-leading ledger is a parallel ledger to the leading ledger. It can be based on a local accounting principle, for example. You can either use ledger 2L (by default, for IFRS) or ledger 3L (by default, for US GAAP) as the non-leading ledger. You have to activate the non-leading ledger for the individual company codes.

If there is a mismatch in the ledger assignment as per the standard expectation, Addressing this issue will require you (Customer),

To reset the data (refer to documentation) for all company codes in both DEV and TEST systems and then
reassign* the local accounting principle as recommended below.

Current Settings / As is situation. (This will be the default configuration when partner receives the initial system access to CBC from SAP). FI consultant should check the configuration and do the needful.

Ledger	Corporate Accounting Principle	Local Accounting Principle
0L	IFRS
2L	LKAP

Recommended Customizing / To be situation.

Ledger	Corporate Accounting Principle	Local Accounting Principle
0L	IFRS
2L		LKAP

*Important: Please do not create/post any fixed assets in your Production System before the recommended changes are effective in your production system. As soon as you have a transactional posting in Fixed Assets in your Production system, it will not be possible to change the Accounting Principle to Ledger settings at Company Code in your landscape.

Adding Custom Fields to Migration Objects in SAP S/4HANA Cloud Public Edition

2024-05-03T07:51:35.354000+02:00

Introduction

SAP S/4HANA Cloud Public Edition is a cloud-based Enterprise Resource Planning (ERP) system that is built on the SAP HANA in-memory database platform. It is designed to provide businesses of all sizes with a comprehensive suite of enterprise management applications for their core business processes, such as finance, procurement, manufacturing, sales, and supply chain management, among others.

The need of custom fields in Data Migration

SAP S/4HANA Cloud Public Edition offers powerful tools for data migration, enabling businesses to seamlessly transition their data to the cloud. However, organizations often require additional custom fields to capture unique information critical to their operations. In this blog post, we'll explore the process of adding custom fields to data migration in S/4HANA Cloud Public Edition. From understanding the data model to configuring custom fields in the migration templates, we'll provide insights and best practices to streamline the migration process and ensure that your business's specific requirements are met. With the flexibility of custom fields, businesses can unlock the full potential of S/4HANA Cloud Public Edition and drive innovation in their digital transformation journey.

One of our key priorities within the PSA is to empower partners with proficiency in new technologies. As part of this initiative, we provide a training program known as the Go Live Experience (GLX). This training simulates a rapid implementation scenario for a distribution company. It encompasses various aspects including configuration settings, data migration, and testing scenarios, focusing on critical areas such as procurement, sales, and finance.

During recent GLX training sessions, participants frequently inquired about managing custom fields within standard migration objects during SAP implementation projects. In response to this demand, I have created this blog to offer a detailed, step-by-step solution. It is our hope that this resource will help you achieve your migration objectives.

Business Case

This simulated scenario requires to add a custom field to the sales order. This field will be included as part of the sales order header, is required to appeared in reporting, will be needed also in the sales order confirmation printout form as well as appear in the billing document. there might be the need to use this field in a potential integration so it will be also available for API usage while working with sales orders.

For more details see images below:

Sales order analytics enabled

Sales order API enabled

Sales order confirmation print form enabled

The custom field is enabled for billing documents

Once these changes are published into SAP S/4HANA Cloud Public Edition the field is created and extended into the corresponding places. Now we go into the UI Adaptation mode to select my available field and capture it during the execution of the business transaction. e.g. in this case the sales order creation.

As a result the field appears in the main screen

The expectation is to migrate existing sales orders; we proceed to create a migration project using local staging tables

To avoid mistakes during migration you need to "Check for Custom Fields" once this operation is run the system will add the custom field to the standard migration template.

You can see under the History Tab the executed actions/status; as well as the predecessors if any.

Proceed to Download this fresh template. Under the title Key user Extensibility Fields you will find the recently created field, in this case ZCustom_Field_DLEON

Continue with the standard steps to Upload File, Review Data, Mapping Tasks, Simulation and Migration.

See the migrated info for a particular order if you to the sales document header and then look into the Custom Fields tab.

We hope this is useful for your implementation. Please leave your feedback below

Thanks,

David Leon

Partner Solution Adoption

SAP Recommendation: Assignment of Corporate Accounting Principle to Ledger

2024-05-03T15:21:16.933000+02:00

This blog aims to guide the SAP Recommendation for assigning Corporate Accounting Principles to the Ledgers for SAP S/4HANA Cloud, public edition (Public Cloud), explain each scenario, the future impacts if the recommendation is not followed, and when it is possible to change the Corporate Accounting Principal assignment.

In the blog SAP S/4HANA Cloud, public edition: Options for Accounting Principles and Ledgers, you can find all the details to define how many ledgers you need to enable in your system and the available scenarios.

However, when the customer and partners activate a non-leading ledger to assign the Corporate Accounting Principle (scope item 1GA for IFRS or/and 2VA for USGP), it is essential to follow the SAP Recommendations in the SAP Help portal's Ledger scenarios: Choosing the right combination for your business needs.

Below, I am going to mention the scenarios available with Corporate Accounting Principles (Accounting Principles):

Scenario: IFRS and Local Accounting

Scope item activated: J58 - Local Accounting and 1GA - IFRS
SAP Recommendation:

Ledger 0L (leading ledger) is assigned with the local accounting principle by default. Please change the assignment to the corporate accounting principle IFRS for this ledger.
Ledger 2L (non-leading ledger) is assigned by default to the corporate accounting principle IFRS. Please assign the local accounting principle to this ledger instead to correct this.

Example:

Scenario: US-GAAP and Local Accounting

Scope item activated: J58 - Local Accounting and 2VA - US-GAAP (USGP)
SAP Recommendation:

Ledger 0L (leading ledger) is assigned with the local accounting principle by default. Please change the assignment to the corporate accounting principle USGP for this ledger.
Ledger 3L (non-leading ledger) is assigned by default to the corporate accounting principle USGP. Please assign the local accounting principle to this ledger instead to correct this.

Example:

Scenario: IFRS, US-GAAP and Local Accounting

Scope item activated: J58 - Local Accounting, 1GA - IFRS and 2VA - US-GAAP
SAP Recommendation:

Ledger 0L (leading ledger) is assigned with the local accounting principle by default. Please change the assignment to the corporate accounting principle IFRS for this ledger.
Ledger 2L (non-leading ledger) is assigned by default to the corporate accounting principle IFRS. Please assign the local accounting principle to this ledger instead to correct this.
Ledger 3L (non-leading ledger) is assigned by default to the corporate accounting principle USGP.

Example:

Future impacts:

If the configuration does not follow the recommended settings for their assignment of the Accounting Principles to Ledgers:

The future impacts when don't have one ledger at the Company Code Level (any ledger in blank), they could:

Not able to assign a different Accounting Principle to Company Codes in New countries
Nor able to enable the Tax Depreciation area 15 for Fixed Assets
If the customer is not planning to use Fixed Assets or expand to additional countries, the update is (still recommended but) not strictly necessary.
Not able to use deviating Fiscal Year Variant in the future.
Example of this case:

The future impact when the leading ledger does not have assigned the Accounting Principle:

Not able to use deviating Fiscal Year Variant in the future.
Example of this case:

It is possible to change the Accounting Principle when:

No postings have been made using any company code in General Ledger Accounting.
If postings were made in a system other than your production (P) system, you can delete these by using the Reset Transaction Data job from the Schedule Accounting Data Changes app.

Please read the information in the following links before executing the Reset Transaction Data job:

Blog:

Reset Transaction Data" Functionality... And when/how to use it...

SAP Help Portal:

SAP S/4HANA Cloud Public Edition Integration Extensibility FAQ-1

2024-05-06T05:42:24.676000+02:00

In this article, we provide a summary of common integration and extensibility questions collected on SAP S/4HANA Cloud Public Edition to reflect the latest developments and changes to frequently asked questions on SAP S/4HANA Cloud Public Edition. In this way, we would like to provide you with a comprehensive and timely resource to help you better understand and take advantage of the functionality of your SAP products.

Common Errors

Problem 1: "TOO_LARGE_BODY" error returned during API call.

Answer: The error "TOO_LARGE_BODY" is returned because the HTTP response is too large, the relevant parameter is (icm/HTTP/max_request size MB), it is recommended to add a parameter $top to limit the number returned, for example, A_PurchaseRequisitionItem? $format=json&$top=100. You can find this in note https://me.sap.com/notes/0003366726 .

Question 2: You cannot create a custom field with the same ID, even if the previous field has been deleted

Answer: This is a known limitation that even if a previously created duplicate custom field has been deleted, you cannot create a new custom field with the same ID as the previously transferred field. It is recommended that customers create new fields with new identifiers and then only use the same description. Details can be found at KBA: https://me.sap.com/notes/3073680 .

Question 3: Postman tests SOAP API reports 500 errors

Answer: The following blog can be referenced: https://blogs.sap.com/2019/09/10/guidelines-for-testing-journal-entry-api-with-soapui-and-checking-r... Part 3, how to test asynchronous APIs.

Question 4: Error "Project of type Custom CDS view must not be edited in this tenant"

Answer: Custom CDS views are part of key user extensions and are therefore only allowed to be changed in the quality/development system, not in the production/test system. Key user extension changes need to be transported together with the Export Soft Collection app and the Import Software Collection app.

Question 5: Change of requested delivery date via Odata API API_SALES_ORDER_SRV but update failed

Answer: This is a known issue, Deep insert of schedule lines is not supported in the sales order creation through the OData API Sales Order (A2X), specifically you can view the KBA https://launchpad.support.sap.com/#/notes/3036121 .

Question 6: Call the OData API of sales order to get all the data, there are about 30000 pieces of data in the system. The return error message is "Error: Maximum response size reached"

Answer: The solution is to change the "Max response size in MB" setting in Postman's settings from 50 to 5000, and then get all the data successfully. The KBA documentation can be found in detail: https://itsm.services.sap/now/nav/ui/classic/params/target/kb_view.do%3Fsysparm_article%3DKB0546967

Question 7: An error is raised when a one-time customer calls the sales order Odata API

Answer: If the customer is a one-time customer, the necessary address information needs to be provided in the payload request, otherwise an error will be reported. You can refer to SAP Note https://me.sap.com/notes/3085492 .

Question 8: Checking CDS for errors: "Data type CURR is not supported at this position"

Answer: To be able to use these fields, one of the following functions needs to be applied to convert the value of the CURR element:
CURR_TO_DECFLOAT_AMOUNT (converts CURR fields to DECFLOAT34 fields,)
GET_NUMERIC_VALUE (Remove the reference information from the DDIC metadata, including the shift of the CURR element.)

Guide Relevant

Question 1: How do I add and subtract dates?

Answer: the function DATS_ADD_DAYS adds days to a specified date.
If the number of days is positive, add the number of days to the date. In other cases, the number of days is subtracted. If the calculation produces an invalid date, the error is handled as specified in on_error.

Question 2: Cannot use APPCustom CDS Views in Starter system

Answer: In the SAP S/4HANA Cloud system (Starter or partner demo system), extensibility for key users is not activated by default. Extensibility for key users can be activated. You can activate extensibility yourself. Open the Fiori app Extensibility Settings and follow the activation process. For more information, see 2283716 - Key User Apps Not Configured https://launchpad.support.sap.com/#/notes/2283716 .

Question 3: Add a new custom field to the app “Post General Journal Entries” which business context should be selected

Answer: You can refer to the SAP Help documentation: https://help.sap.com/docs/SAP_S4HANA_CLOUD/0fa84c9d9c634132b7c4abb9ffdd8f06/e5defe0a850948d1bd7a2834...

Consulting-Relevant

Question 1: What is the effective time for CSRF Token?

Answer: The default CSRF token is 24 hours (86400 seconds), but this validity period is related to security session and depends on the value of system parameter http/security_session_timeout. Inside S4HC, the value of http/security_session_timeout is 30 minutes, so CSRF token is valid for 30 minutes in S4HC.

Question 2: Want to read fixed asset master data via API, but found that CDS View I_FixedAsset cannot be used as a data source for custom cds view

Answer: I_FixedAsset can be used by in-app extensions, except that the data sources in the custom cds view are automatically filtered. If you want to see other data sources, on the select primary data source page, select show filter and set recommended data source to No. Details can be found in the KBA https://me.sap.com/notes/3148426 .

Question 3: Whether the SAP interface has a limit on the amount of data and the number of times it has been acquired, the data is not returned, and no error is reported. There is no return of interface data in successive attempts

Answer: The External API scenario is not available for one-time mass data extraction. For optimal performance, the client needs to use appropriate filters and/or paging to limit the requested data. For more information, check out the following link:
https://launchpad.support.sap.com/#/notes/2692128

Question 4: I want to read the field "RequirementTracking" on the API API_PURCHASEORDER_PROCESS_SRV for purchase orders and found that it is not possible to find it

Answer: There is no such field on the OData V2 API. However, the field is available on the API CE_PURCHASEORDER_0001 for OData V4. If the customer needs to read the field, they can consider using the API of V4.

Question 5: Using the OData API (SAP_COM_0057) to create supplier invoices, but found that there is no duplicate check in the API

Answer: To do the duplicate check in the API, you need to specifically activate it in the configuration of invoice verification. Message class M8 message 804,805 needs to be set to error, see Note https://me.sap.com/notes/2721713 .

Question 6: Create sales order from a third-party system by calling the Sales order Odata API, and find that the performance is not good. It takes 60-70 seconds to create a data

Answer: The user gets the full amount of data when taking the token, but in order to get the token only need to take a piece of data, I suggest adding it at the end of the URL? $top=1&$inlinecount=non.

EPPM-项目经理权限控制ⅠⅠ

2024-05-06T08:55:02.702000+02:00

系统现状

当使用权限企业项目-项目经理角色（SAP_PROJECT_MANAGER），同时又需要项目分析报表权限在角色业务目录里增加业务目录企业项目-项目财务分析(SAP_PS_BC_PROJ_FIN_ANLYTC_MC)

会使APP：我的项目-项目经理中，项目概要显示所有项目经理的项目

Workaround：通过以下设置可以恢复只显示项目经理为自己的项目

1.APP：维护业务角色，对角色Z_BR_PROJECTMANAGER维护限制

设置写入访问和读取访问为受限制
对页签S4PPM_PR1设置公司代码为9999（任何非真实公司存在代码都可以）
对其他所有页签和字段设置为无限制

2.再次打开APP：我的项目-项目经理，项目概要只显示项目经理为自己的项目

感谢观看

SAP S/4HANA Cloud Public Edition: Product Expert Training 2024 上半年度 5 月 10 日至 5 月 16 日

2024-05-07T06:03:58.079000+02:00

为您提供卓越的产品支持

尊敬的客户和 SAP 同事：

我们很荣幸邀请您参加 2024 年 SAP S/4HANA Cloud 产品专家培训！很高兴您能加入我们，全面掌握 SAP S/4HANA Cloud ERP。从 5 月 10 日至 16 日，我们将分享有关 SAP S/4HANA Cloud 公有云的最新洞察。作为产品专家，您的知识和经验是推动产品成功以及帮助我们为 SAP S/4HANA Cloud 客户提供卓越产品和服务的关键。

注册和议程

立即注册，在线参加会议。

话题	标题	日期	时间	注册链接
技术话题	Cross Topic & UX用户体验更新	10/05/2024	2:00 PM - 4:00 PM	注册
项目实施	项目避坑指南	13/05/2024	2:00 PM – 2:30 PM	注册
寻源到支付	端到端采购供应商退货	13/05/2024	3:00 PM – 4:00 PM	注册
本地化	大中华区本地化	14/05/2024	10:30 AM – 12:00 PM	注册
计划到履行	计划到履行端到端供应链	14/05/2024	2:00 PM – 3:30 PM	注册
记录到报告	财务总览	15/05/2024	10:00 AM – 10:45 AM	注册
技术话题	可扩展性	15/05/2024	11:00 AM – 11:30 AM	注册
技术话题	公有云与人工智能同行	15/05/2024	2:00 PM – 2:45 PM	注册
技术话题	自动化测试和Process Navigator	15/05/2024	3:00 PM – 3:30 PM	注册
线索到现金	端到端销售和EPPM	16/05/2024	10:30 AM – 11:30 AM	注册
计划到履行	计划到履行端到端制造	16/05/2024	2:00 PM – 3:30 PM	注册

您可以在登录页面上找到关于注册的更多信息：

Workzone 登录页面

*SAP 客户可能需要联系您的 SAP 联系人将您添加至 Workzone。
*SAP 合作伙伴可以联系您的 SAP 联系人寻找相关注册和参会链接。

概念

通过本次线上分享，您将获得宝贵的洞察和专业知识，使您能够为内部团队和重要客户提供支持、指导和尖端的最佳实践。从了解产品特性和功能到解决常见查询和解决复杂问题，本培训将为您提供职位所需的工具和知识。我们对产品卓越性的承诺是坚定不移的，

在接下来的六天中，您将了解有关可扩展性与人工智能等交叉主题的详细信息，与行业专家进行实践练习，并与云客户服务的其他参与者协作。此外，我们的业务线功能也包含在端到端业务流程中。您对此学习之旅的方法为目的地增加了高度的品质：我们鼓励您以好奇心、热情和愿意与自己以及我们的专家交流和提出问题的意愿来参加每个会议。把握机会，扩展你的技能、专业知识，并在企业内发挥有意义的影响。

我们已经涵盖了产品专家培训课程，这些课程将被录制并上传到Workzone。

在“线上”阶段见！还有问题或反馈？请联系 s4hana.pscc.gcr@sap.com，我们将尽快与您联系！

Shared Trouble is security doubled: the shared responsibility model for SAP S/4HANA Cloud

2024-05-07T09:21:45.077000+02:00

One of the advantages of cloud applications is that you don’t have to take care of security. Which is true – mostly. In reality, while most of the security responsibilities and tasks are taken over by the cloud service provider, there are some things which the customer still holds responsible for. And that also goes for the security responsibilities in SAP S/4HANA Cloud.

Now, the title of this article specifically mentions SAP S/4HANA Cloud, without specifying whether it refers to private or public cloud. This is intentional as the focus is on the customer's responsibilities in the S/4HANA Cloud responsibility model – and in the following I’d like to highlight the responsibilities of the customer in general, while detailing the differences between SAP S/4HANA Cloud Privat Edition versus SAP S/4HANA Cloud Public Edition.

Responsibilities in General

In terms of security, responsibilities are relatively clearly split between the Cloud Service Provider (CSP) and the customer. On a high level, the CSP’s responsibility includes security operations, network application, database management, operating system management, and the bare metal, unless partnering with a hyperscaler.

The customer, on the other hand, is responsible for the application's access and security. However, there's a significant distinction depending on whether we're discussing SAP S/4HANA public or private cloud.

Looking at it from another perspective, as the cloud service provider, we don't have access to your customer data, user identities, authentication, and business processes. The responsibility for these aspects lies with the customer. Conversely, security for the application server, database, operating systems, physical security, and bare metal security falls under our, SAP's, jurisdiction as a cloud service provider.

Understanding the difference is crucial, not just for security, but for adjacent topics as well.

Auditing cloud applications

In order to get an overview, let’s begin with how auditing is approached in different cloud deployment options. This will help elucidate why it's critical to clearly distinguish responsibilities between you as a customer and SAP as the cloud service provider.

When examining IT general controls, one should consider business processes, applications, and infrastructure. These elements require auditing by your auditor. IT application controls relate to business transactions and processes. The software, such as SAP S/4HANA, handles this. However, as the customer, you define the business processes and are therefore accountable to the auditor to ensure these processes function as designed.

Secondly, there are application-related controls. These involve access management, change management, security configuration, and monitoring of application jobs and integration scenarios. The goal here is to ensure the application is implemented securely and correctly to meet the requirements of the business processes.

The same principle applies to IT infrastructure, which must be implemented correctly to support business processes without negative impacts. This includes operating system and database security, but also physical data center security.

Customer Audits

When considering various cloud service models, the scope of the auditor's role varies significantly between on-premise installations and software as a service. In an on-premise model, the customer’s auditor must assess everything from physical security to business process controls.

Different Cloud Deployment Models

In an Infrastructure as a Service (IaaS) model, the auditor would need to rely on the cloud service provider for physical data center security and hardware matters. However, everything else, including service operating systems and databases, remains the customer's responsibility and must be audited accordingly.

With Platform as a Service (PaaS), like S/4HANA private cloud, responsibilities for the security of operating systems and databases shift to the cloud service provider.

Software as a Service (SaaS) extends this concept further, in cases like the SAP S/4HANA public cloud, where standardized software is used by all customers.

To manage these varying responsibilities, the SOC (Service Organization Control) report, specifically the SOC 2 report has been established as an industry standard. This report is an attestation from auditors that all controls regarding IT infrastructure and application responsibility are functioning as designed.

The SOC report's purpose is to prevent each customer's auditor from having to verify that a CSP is maintaining their controls correctly.

However, it's crucial to note that customers must request the SOC 2 report regularly from the CSP, review it, and ensure it aligns with their security requirements. Subsequently, the company and its IT auditors need to review the controls within the SOC 2 report to verify everything is in order.

The differences in SAP S/4HANA deployment models

Let's delve into the S/4HANA application, specifically focusing on the differences between private and public cloud options.

To do this, we could proceed alphabetically by topic, but the most effective approach would be through the lens of the SAP Secure Operations Map. This tool, although developed before the advent of cloud technology, remains relevant as it comprehensively covers all tasks required for running applications like S/4HANA.

SAP Secure Operations Map

As a brief overview, the map starts at the top with the organization, which isn't directly related to IT. It emphasizes the need for security governance awareness and risk management - an area that's often overlooked. In essence, it's crucial to identify potential risks, prepare responses, and manage them appropriately.

Next, the secure operations map addresses the application itself, highlighting aspects like access management, authentication, authorizations, and custom code security. It considers all customizations made in your SAP S/4HANA system.

On the system level, the map focuses on security hardening, secure SAP code, our secure development process, and security monitoring.

At the bottom of the map, mirroring the cloud responsibilities we've discussed, there’s the environment. This includes network security, operating system, database security, and client security.

Taking a closer look at this, and returning to the cloud deployment models we discussed earlier, we see that the Secure Operations Map's five topics (environment, system, application, process, and organization) are all the customer's responsibility in an on-premise environment.

In a private environment, the responsibility transitions between SAP and the customer around the application area. In a public environment, we, as the service provider, shoulder a larger share of the responsibility compared to the customer.

Network security is a shared responsibility between customers and SAP, regardless of whether the environment is private or public. As a customer, you must ensure that the network you use to access applications is secure. For instance, in a private environment, you may use SAP GUI via a VPN tunnel to our network. In contrast, in the public cloud, you can only access the software through a web browser over the internet. In both cases, you as the customer need to ensure that the network on your end is secured.

The operating system database security is our responsibility, again, regardless of whether it's a private or public cloud. Client security, on the other hand, such as ensuring the SAP GUI or web browser is set up securely, falls under the customer's domain in both cases.

When it comes to system security hardening, it's our responsibility, fully. Secure SAP code, from a development perspective, is our responsibility in both private and public cloud scenarios. However, there's a key difference when it comes to patch management in the private cloud. Here, updates are individual per customer and may affect business processes or require system restarts. Therefore, we coordinate with you before initiating any updates, unlike in the public cloud, where updates affect all customers.

Security monitoring and forensics represent another shared responsibility, but there are differences between Rise and Grow. In Rise, due to access to most of the ABAP stack, similar to an on-premise environment, you receive more information, including infrastructure logs provided by our private cloud operations team, a service called LogServe.

In a public cloud scenario, we provide a limited number of logs for security monitoring. Some information, technically, is shared among all customers; hence, we can't share it with individual customers.

The application

Let's delve into the application, specifically User and Identity Management.

When we discuss roles and authorizations, we see a distinction between private and public cloud environments. In a private cloud, customers retain access to the PFCG, the SAP system transaction where roles and authorizations are defined and implemented. It's important to note that while you do have PFCG access in the private cloud, it's not usually full access. You typically can't assign authorizations or access the roles and authorizations definition, PFCG, as an admin, particularly when it comes to technical security topics.

In the public cloud, we implement a different strategy. We use what we call business catalogues, the smallest units of roles and authorizations. These catalogues are combined to create roles within the application, aligning with your business processes.

Regarding Custom Code Security, your code is generally your responsibility. However, there's a slight difference between private and public clouds. In the private cloud, you have more opportunities to program additional applications on top of S/4HANA. In contrast, in the public cloud, we provide Developer Extensibility that allows business application extensions but limits access to low level functionality.

The last main topic from within the Secure Operations Map is Processes and Organizations. This is primarily the customer's responsibility, which is why we won’t discuss it here.

Conclusion: Lots and less to think about

As mentioned in the opening of this article: moving to the cloud gives you a lot less to think and worry about, especially when it comes to security. However, it does not relieve customers from all responsibility - something to keep in mind. On the other hand, we at SAP will support now and in the future by guiding customers through those settings they are responsible for. And by making S/4HANA Cloud the most secure ERP system.

New features in SAP Warehouse Operator Version 2.3

2024-05-07T09:29:20.767000+02:00

The latest release of SAP Warehouse Operator comes with several exciting new features. One of the most interesting ones is the support for product putaway.

After the release of SAP Warehouse Operator Version 2.2 last December, we have worked on the next version of SAP Warehouse Operator, which has just been released with the following key capabilities:

Support for product putaway
Putaway by purchase order and inbound delivery number
Splitting of warehouse tasks
Support for different destination bins inside a warehouse order
Improved handling for scanning serial numbers
Audio playback for positive scanning feedback
Translation into additional standard languages (Spanish, French, Portuguese/Brazil, Japanese)

Support for product putaway

Putaway in a warehouse is the process, when goods that have been received from vendors are brought to their storage area in the warehouse. This allows for easy tracking of items and helps to prevent the loss of goods.

We have added support for product putaway on top of putting away handling units. This means that individual products can now be scanned and put away based on the product warehouse tasks created in Warehouse Management SAP S/4HANA Public Edition before.

The warehouse operator may choose between two different selection strategies, when working on warehouse tasks. The “Product” strategy allows the user to take a products from a handling unit, scan it and then start the related product warehouse task for putaway. As an alternative, the “Sorting” strategy can be used to put away products based on the sequence of warehouse tasks defined by the app.

Putaway by purchase order and inbound delivery number

The putaway of goods can now also be initiated by scanning or typing in the handling unit ID, purchase order number or inbound delivery number. Different entry points have been added accordingly.

Splitting of warehouse tasks

To improve the handling of quantity differences for picking warehouse tasks, you can now also split warehouse tasks in the app. This is for example helpful, when a pick handling unit is full and not all items can be picked into it. The warehouse task may be splitted and a new task gets created for the remaining quantity. A new Pick-HU can then be created in the app to be used to pick the remaining quantity of items for the new warehouse task.

More improvements

Also, different destination bins inside a warehouse order are now supported.

Additionally, we have improved scanning of serial numbers, which is now also possible from a list view, to get a better overview of the serial numbers that have and have not been scanned.

Furthermore, audio playback for positive scanning feedback has been added and the app is now also available in Spanish, French, Portuguese/Brazil and Japanese, when you preferer one of those languages.

Try the app and engage with us

Please download the new version of the app and try it out yourself.

Please leave a comment below if you have questions or feedback and we’ll get back to you.

You may also contact us at SAP_Warehouse_Operator@sap.com if you have questions on the configuration to use the app, the setup process or have specific requirements.

We also encourage you to visit our SAP Mobile Applications community page and click “follow”. We’ll be publishing more informative blog posts. Please post questions in the SAP Extended Warehouse Management area.

Behavior of Advanced Foreign Currency Valuation after Clearing

2024-05-07T10:09:51.800000+02:00

The clearing will not change any existing valuation adjustments posted from Advanced Foreign Currency Valuation. The next valuation run after the clearing will correct existing valuation adjustments. To which account these corrections will be posted depends on the account determination configuration of Advanced Foreign Currency Valuation.

The following sample process incorporates a few valuations runs generating gain and loss FX effects. It shows how the delta posting logic is working.

The clearing is done as part of the Incoming payment (line 10). The last two lines (11 and 12) are generated by the valuation run after the clearing. The accounts used by the different steps are depending on the account configuration. The following chapters explain the configuration and the influence on the result.

Account configuration for exchange rate differences

There are two different configurations for accounts used to post exchange rate differences:

1. Define Rules for Advanced Foreign Currency Valuation (SSCUI ID 105450)
The sub-view ‘Assign G/L Accounts for FCV’ provides the account configuration.

It provides the following four accounts: (1) FX Gain Realized Account, (2) FX Loss Realized Account, (3) FX Gain Unrealized Account and (4) FX Loss Unrealized Account.

In general, there are two accounts for unrealized exchange rate differences and two accounts for realized excchange rate differences: The unrealized accounts are used to post value adjustments from Advanced Foreign Currency Valuation before an open item is cleared. The realized accounts are used to reset existing value adjustments from Advanced Foreign Currency Valuation after an open item is cleared.

2. Automatic Account Determination (SSCUI ID 100297)
Area = Financial Accounting
Subarea = General Ledger Accounting
Process = Define Accounts for Exchange Rate Differences
Transaction Key = KDF (Exchange Rate Dif.: Open Items/GL Acct)

The accounts for ‘Exchange Rate Difference Realized’ are used to post exchange rate differences as a part of clearing. They are not related to Advanced Foreign Currency Valuation. Hence, the account determination needs to be maintained in both SSCUIs.

Influence of account configuration on reporting results

In the following, the posting behavior and methodology of the Advanced Foreign Currency Valuation Run with clearing will be described.

Configuration scenarios

Different account determination settings can lead to different effects on the P&L accounts. With the flexible account determination different business and even country-specific requirements can be met. This, as well as the delta posting methodology will be described with the help of the four following scenarios:

Note: Please be aware, the examples below are only focusing on the gain accounts. The same is applicable to the loss accounts.

Scenario 1: The ‘Realized FX Gain’ account (customizing of the Advanced Foreign Currency Valuation) and the ‘Exchange Rate Difference Realized Gain’ account (customizing for Automatic Account Determination) are identical, but the ‘Unrealized FX Gain’ account (customizing of the Advanced Foreign Currency Valuation) is different.
Scenario 2: The ‘Realized FX Gain’ and the ‘Unrealized FX Gain’ account (customizing of the Advanced Foreign Currency Valuation) are identical, but the ‘Exchange Rate Difference Realized Gain’ account (customizing for Automatic Account Determination) is different.
Scenario 3: The ‘Realized FX Gain’ account, the ‘Unrealized FX Gain’ account (customizing of the Advanced Foreign Currency Valuation) and the ‘Exchange Rate Difference Realized Gain’ account (customizing for Automatic Account Determination) are all identical.
Scenario 4: The ‘Realized FX Gain’ account, the ‘Unrealized FX Gain’ account (customizing of the Advanced Foreign Currency Valuation) and the ‘Exchange Rate Difference Realized Gain’ account (customizing for Automatic Account Determination) are all different.

Explanation of the sample process:

The sample process starts with an outgoing invoice of $ 1.000 (line 1). Because of the exchange rate at posting date (0.7 EUR/USD), EUR 700 were posted onto Receivables 12100000 (dr.) and revenue (cr.).
The Advanced Foreign Currency Valuation run in January 2024 has posted value adjustments for exchange rate differences using the account ‘Unrealized FX Gain’ (line 2). The account ‘Unrealized FX Gain’ was used because the item is still open (not yet cleared).
The clearing was done as part of the Incoming Payment in February 2024 (line 3). The clearing has posted exchange rate differences using the account ‘Exchange Rate Difference Realized Gain’ of Automatic Account Determination.
The Advanced Foreign Currency Valuation run in February 2024 has corrected the existing value adjustments using the account ‘Realized FX Gain’ (line 4). The account ‘Realized FX Gain’ was used because the item is cleared.
In addition this valuation has generated a statistical posting to enable the reporting of the realized exchange rate differences from clearing (line 5).

Reporting results for different configuration scenarios

Scenario 1: The configuration is as follows

FX Gain Unrealized Account: 70200000
FX Gain Realized Account: 72510000
Exchange Rate Difference Realized – Gain: 72510000

The result shows that:

The valuation in January has posted unrealized FX effects on account 70200000.
Exchange Rate Differences from clearing are posted onto account 72510000 (line 3).
The valuation in February has posted the corrections for FX effects from valuation on account 72510000 (line 4).
On account 72510000 the amount of EUR 200 (line 3) will be reduced by EUR – 100 (line 4) to correct the unrealized FX effects that had been posted before (line 2).
The balance on account 70200000 is not zero at the end of the process.

Attention: Evaluate if the change of realized exchange rate differences from clearing by corrections from Advanced Foreign Currency Valuation is meeting the business and acounting requirements. If not, this configuration scenario should not be used.

Scenario 2: The configuration is as follows

FX Gain Unrealized Account: ‘Unrealized FX Gain’ 70200000
FX Gain Realized Account: ‘Unrealized FX Gain’ 70200000
Exchange Rate Difference Realized – Gain: ‘Valuation Gain Exchange Rate Differences’ 72510000

The result shows that:

The valuation in January has posted unrealized FX effects on account 70200000.
The incoming payment has posted realized FX effects on account 72510000 (line 3).
The valuation in February has posted the corrections for FX effects from valuation on account 70200000 (line 4).
On account 72510000 the amount of EUR 200 (line 3) is not changed.
The balance on account 70200000 is zero at the end of the process.

Scenario 3:

Configuration: The configuration is as follows

FX Gain Unrealized Account: 72510000
FX Gain Realized Account: 72510000
Exchange Rate Difference Realized – Gain: 72510000

The result shows that:

The valuation in January has posted unrealized FX effects on account 72510000 (line 2).
The incoming payment has posted realized FX effects on account 72510000 (line 3).
The valuation in February has posted the corrections for FX effects from valuation on account 72510000 (line 4).
The balance on account 72510000 is EUR 200, the same as the realized FX effects from clearing.

Scenario 4:

Configuration:

FX Gain Unrealized Account: 70200000
FX Gain Realized Account: 70100000
Exchange Rate Difference Realized – Gain: 72510000

The result shows that:

The valuation in January has posted unrealized FX effects on account 70200000.
The incoming payment has posted realized FX effects on account 72510000 (line 3).
The valuation in February has posted the corrections for FX effects from valuation on account 70100000 (line 4).
On account 72510000 the amount of EUR 200 (line 3) is not changed.
The balance on account 70200000 is not zero at the end of the process.
The balance on account 70100000 is not zero at the end of the process.

Where can I start learning how to design business processes in SAP S/4HANA Cloud Public Edition?

2024-05-07T13:59:22.649000+02:00

We recommend to access our Designing the Asset Accounting Process learning journey.

Overview
This learning journey provides business users and application consultants the necessary skills to configure Asset Accounting in SAP S/4HANA. This knowledge is particularly beneficial when defining and designing business processes in SAP S/4HANA Cloud Public Edition.

Learning objectives

Improve the structure of the fixed assets
Manage asset account determinations
Define low-value assets
Use validations and substitutions for asset master record fields
Procure fixed assets with valuated and non-valuated goods receipts
Explore down payments for assets under construction

Prerequisites

Performing Asset Accounting Processes in SAP S/4HANA

Please ask a question related to the digital learning Journey in the Q&A area.

Our SAP Learning Experts will get back to you as soon as possible! We are here to support you.

We appreciate your feedback and we will make sure to continue sharing interesting topics.

A free training bootcamp & certification opportunity for women in tech

2024-05-07T17:22:46.026000+02:00

Hi everyone,

I’m David Chaviano from the SAP Community growth & adoption programs team. I am responsible for our digital skills initiative.

The digital skills initiative is a learn-to-earn program intended to get people generally considered to be underrepresented in tech into the SAP ecosystem. Participating organizations/instructors will be partnering with SAP in giving people from a disadvantaged/ unconventional /underrepresented background a chance to break into the tech sector and prove themselves while adding fresh talent to our ecosystem.

One subset of the initiative is getting a cohort of potential candidates and guiding them through a learning pipeline and linking them up with a customer, partner or SAP org willing to give these new folks a chance at a job/internship. This is sometimes done via virtual live bootcamp with an instructor.

Here is the registration information for one of these free bootcamps – it includes the registration details for candidates who are interested to sign up. Be sure to sign up via the link or QR code in the PDF.

For a full deep dive on what this certification is training you for, read this blog.

Feel free to pass it along to peers who may also be a good fit!

Regards,

David

Quantity Distribution

2024-05-08T14:11:28.972000+02:00

Hello there!

If you're new to the world of SAP S/4HANA Cloud, Public Edition and Bill of Materials (BOM), one concept that may sound a bit complex initially, but could be tremendously beneficial to your business, is Equal Quantity Distribution. Though it might seem like a mouthful at first, understanding this principle could be the key to unlocking greater efficiency and potential in your production process.

What is Equal Quantity Distribution?

Imagine you're planning to host a big party. You have a list (your BOM) of all the ingredients you need for your menu. Now, would it make sense to buy all of your supplies weeks in advance? Probably not. Some ingredients are perishable, others might only be needed at the time of cooking. So, you plan your shopping trips, distributing your purchases over time.

Similarly, Equal Quantity Distribution can be seen as a "smart shopping" strategy for your production process. In the context of dependent requirements and BOM, Equal Quantity Distribution is a method of scheduling the procurement or production of materials exactly when it's required during the production cycle. The demand is equally dispersed along with your chosen timeline or specific stages of your production process.

But not only production processes can benefit from Equal Quantity Distribution, also the Product Availability Check (PAC) can incorporate it when determining on which date and in which quantity a requirement (for example, a sales order item) can be fulfilled.

What does this mean for the supply and demand?

In a production order the demand for the components is on start date of the operation. With quantity distribution, these demands are distributed across the production runtime. Similarly, the whole supply that is created with the production order is planned at the end of the order. Following diagram depicts this:

Equal Quantity Distribution changes this by distributing supply and demand, like depicted in following diagram:

How can businesses benefit from equal quantity distribution?

Optimized Production Process: Equally distributing the quantity of materials required at each stage ensures a smoother, more streamlined production process. It avoids bottlenecks or unnecessary delays due to waiting for materials to arrive or be produced.
Reduced Inventory Costs: By planning and managing your materials to be available just when needed, you effectively reduce storage and handling costs. This is because you won't need to hold excess inventory for extended periods.
Enhanced Quality Control: With the right quantity provisioned when needed, there's a lower risk of errors in production. Hence, overall product quality is likely to improve.
Greater Customer Satisfaction: Efficient production often leads to timely order fulfillment, which can significantly boost customer satisfaction and loyalty.
Support for JIT Production: Equal Quantity Distribution aligns well with Just-In-Time (JIT) production, a methodology aimed at reducing waste and enhancing productivity by receiving goods only as they are needed.

How to set it up?

The equal distribution function is available in discrete manufacturing, process manufacturing and repetitive manufacturing. You can set it basically at two places:

On header level of the production version material level or,
at component level in the bill of material (BOM)

In addition the Equal Quantity Distribution can be set to be respected in the Available-to-Promise (ATP) by setting it in the Scope of Check. Let us have a look to a simple example in the system:

Conclusion

The principle of Equal Quantity Distribution in SAP S/4HANA Cloud, Public Edition can significantly improve your production process, especially when working with continuous component feed. It can also improve your order fulfillment as supplies can be considered earlier than only at the end of production.

Implementing Equal Quantity Distribution might require a shift in mindset, but the payoffs could be substantial - from reduced inventory costs to improved product quality and customer satisfaction.

So don't shy away from exploring this concept further.

More Information

Product Assistance
Questions? Ask here

Customer Usage Dashboard 2nd Edition for SAP S/4HANA Cloud Public Edition

2024-05-08T15:00:00.076000+02:00

In January 2023, we delivered the first version of the Customer Usage Dashboard for SAP S/4HANA Public Cloud Edition on SAP for Me. As mentioned in my previous blog, our goal is to help customers monitor their usage and adoption in order to better understand how their end-users are using SAP S/4HANA Cloud Public Edition. This, in turn, helps customers to take data-driven decisions based on their own usage, and to better understand how their investment generates value.

What’s new in the second edition of Customer Usage Dashboard?

In the Most Used Apps table, instead of only showing the top 25 most used applications, we now have the full list of used applications from the past 12 months.

You can choose any monthly time interval from the past 12 months to see how many times each application was started by the end-users within this period. You can also compare the usage of different apps using the Application Name filter. The name of the application is also linked to SAP Fiori Apps Reference Library.

In the Feature Usage (Scope Item Usage) table, we added a new column showing the DDA (Digital Discovery Assessment) selection status. In case you used the DDA tool during the sales cycle to identify the scopes required to fulfill your business needs, this column shows which scope items were “Selected” or “Not Selected”. With this additional information, you can now monitor which of those selected items are activated, as well as monitoring the usage in the last 6 and 12 months. What’s more, the Scope Items are linked to the respective Scope Item definition on the SAP for Me Process Navigator page with information on process documentation, underlying software components, applications, application roles, test scripts along process flows diagrams, integration information, and more.

These changes are all based on your direct feedback. Please continue to share your feedback and experiences with us so we can improve future versions to help you leverage maximum value.

As always, you can also reach out to your Customer Success Manager (CSM) to have a discussion.

An Uber for Engineering?

Your feedback helps to improve SAP S/4HANA Cloud Public Edition

Learn More:

Celebrating the Success of the Product Expert Training H1 2024

2024-05-08T16:05:49.126000+02:00

Celebrating the Success of the Product Expert Training H1 2024

In the dynamic market environment, staying ahead of the curve requires more than just great products – it demands product experts who can effectively showcase their value and meet our customers´ needs. At the SAP PSCC organization, we understand the role that product expertise plays in driving success, which is why we embark on a transformative journey with the SAP S/4HANA Cloud Product Expert Training.

We are thrilled to share the remarkable success story and the positive impact it has on the partner ecosystem for SAP S/4HANA Cloud Public Edition and SAP colleagues.

Empowering Excellence

We have the goal to empower our colleagues and partners with the knowledge and skills needed to represent our products, recognising that expertise is a continuous journey. Our organization is happy to be part of this journey by providing a learning environment full of effective communication and interaction.

Over 230 SAP engineering product experts presented in 63 webinars the lates product features and insights of SAP S/4HANA Cloud Public Edition. Our participants gained a deeper understanding of our products, and had the ability to engage with product experts and address their needs. This prodcut expertise contributes to the overall knowledage and curriculum needed to successfully mannager a customer project.

The next Chapter of Success

We have achieved a total registration of 3.7k, meaning compared to the Training in April 2023, we could increase the overall registration by 20%. With +2.5k registered partners, we have achieved the highest partner share ever with 68%. We have improved communication and could lift not only the registration, but also the live participation to a new level.

During the 7 days of training, we had a total live participation of +12600. Additionally, we had an even higher partner share of 66%.

Throughout the training, we noticed remarkable dedication and commitment from our speakers. With their product expertise, our colleagues and partners gain the knowledge and insights they need to succeed in their roles. The numbers reflect the exceptional standards our experts have delivered in the last two weeks. Our speakers achieved a total satisfaction score of 93%.

But don't just take our word for it—here's what some of our participants had to say about their experience with the Product Expert Training program:

“Very insightful training as always. Thanks for organizing it.”
“Well done, nice flow and right level in detail for the audience.”
“These sessions are extraordinary. Anytime we can talk about Methodology is awesome.”

Join Us on the Journey

As we celebrate the success of our Product Expert Training, we are also mindful of the journey that lies ahead. We invite you on this journey. Join the SAP S/4HANA community and explore the culture of learning and growth at the Product Expert Training. We will share the recordings, as well as the latest information on the upcoming Product Expert Training on our landing pages:

Internal landing page

Partner landing page

See you at the next training!

4 Expert Tips for Setting Up the Organizational Structure in SAP Central Business Configuration

2024-05-08T16:21:55.205000+02:00

Setting up your organizational structure is a crucial part of any implementation project. If you’re implementing SAP S/4HANA Cloud Public Edition, then SAP Central Business Configuration with its Set Up Organizational Structure app is used to perform this task. Here are a few tips on how to make the most of the offered capabilities.

1. Switch Between Graphic View and Table View

Based on your personal preference, there are two options for displaying your organizational structure: The graphic view, which represents your organizational structure as a tree diagram, or the table view, which organizes the units in a tabular format. Although the graphic view is generally the default, we advise using the table view for large organizational structures to enhance performance and usability. If the size of your organizational structure is near the threshold that the application can support in terms of rendering, the organizational structure even opens in the table view by default to ensure best performance.

Screenshot of the table view

2. Swiftly Navigate in Full-Screen Mode

For those working with larger organizational structures who prefer the graphic view, full-screen mode offers an enhanced user experience. This mode does not only enlarge the view but also introduces an alternative way of navigation: The cursor transforms into a hand for easy click-and-drag navigation, eliminating the need to use the scroll bars. This allows you to navigate your organizational structure smoothly.

Screenshot of the full-screen mode

3. Change the Focus of Your View

In the graphic view, you have the option to focus your view on specific segments of the organizational structure. This is applicable to organizational units which typically encompass numerous subordinate units, such as plants or sales organizations. By clicking on the desired unit, the view automatically adjusts to display only the selected unit and its subordinate units. This gives you a better overview of the individual segments of the organizational structure. To go back to the full structure, simply click Back to Overview.

Screenshot of the graphic view focusing on a specific plant and its subordinate units

4. Intentionally Select Subtypes

Depending on your scope, different subtypes for storage locations are available for selection. It's crucial to select the subtype of your storage locations deliberately, based on your specific needs, as this cannot be modified later. For instance, in a Logistics with Third-Party Warehouse Management scenario, make sure to select a suitable subtype, for example, 3rd Party WMS, to ensure proper setup of your storage locations. Note that once you’ve confirmed an organizational unit, you can no longer delete it or change its subtype.

Screenshot of the Subtype dropdown list

If you ever encounter difficulties while setting up the organizational structure, the in-app help is readily available. Simply click on the question mark icon at the top right. For a more thorough understanding and a comprehensive overview, refer to the Organizational Structure Management documentation on the SAP Help Portal. To learn more about future capabilities that we’ve planned for the Set Up Organizational Structure app and other applications, visit the SAP Central Business Configuration road map on SAP Road Map Explorer.

Do you have an idea on how to further enhance SAP Central Business Configuration? Go to the SAP Customer Influence portal to submit an improvement request or vote for the ideas of others. This helps us understand your requirements even better and prioritize our work accordingly. We’re looking forward to your improvement requests.

Co-authors: Amit Gupta, @FabianAckermann

Understand Upgrading and Patching Processes of SAP S/4HANA Cloud Public Edition

2024-05-08T19:42:19.359000+02:00

Introduction

For the SAP S/4HANA Cloud Public Edition solution, the upgrade happens every six months and patches are applied every other week. To the customers and consultants new to this solution, I’d like to explain this process in an easy-to-understand way in this blog. Separately, I have written three other upgrade related blogs to give you a full picture of the topic (see reference section).

Notes:

All times shown in this blog are for North America for the convenience of our discussion.
No discussion on the upgrade of Partner Demo System, Starter System, and Test System, as they usually are not critical or impactful to the customer users from the upgrade perspective.
Our discussion will focus on CBC based 2 System Landscape and 3 System Landscape, Dev and Production Systems in particular.

Terminologies for High Level Schedule of Upgrade and Patches

When we talk about upgrades and patches, understanding some terminologies is critical. Let me list them here:

Major Upgrades or Release Upgrades or Upgrades – They are major software upgrades happening every February and August. They are applied to different systems in different weekends in a period of several weeks. A numeric software release version is assigned, for example, 2402 is for February 2024 release.
Updates or Patches – They are conducted every other weekend. Two weeks after the Major Upgrade, a Hotfix Collection (HFC) with corrections is applied. Two weeks later, another HFC with both corrections and new innovations (called Continuous Delivery Service, CDS) is applied. The cycle continues until next Major Upgrade. The HFC deployments are performed on the same dates to all systems. The Hotfix is labeled like HFC03, standing for the third hotfix collection.
HANA Database Upgrades – About four weeks before the Major Upgrade, a mandatory HANA Database Upgrade is applied, so that the Major Upgrade of the S/4HANA Cloud Public Edition solution can be performed.
Global Infrastructure Maintenance – They are conducted in the maintenance windows no other activities are present to change the hardware, router, operating systems, network, etc.

With above definitions in mind, we can easily navigate the Upgrade and Patch Schedule published by SAP in the SAP S/4HANA Cloud - Software Lifecycle Management for Customers (9/18/2023). Let’s take the 3-System Landscape (3SL) systems as an example in Figure 1.

Figure 1. High Level Schedule of Upgrades and Patches for 3SL Systems

On January 26-28, Release 2402 and HFC02 was applied to Test Systems. This marks the beginning of the 2402 Upgrade cycle.
On February 2-4, Release 2402 and HFC02 was applied to Starter Systems, Partner Demo System, etc.
On February 16-18, Release 2402 and HFC03 was applied to both Development and Production Systems. In the same weekend, HFC03 was applied to previously upgraded Test Systems and Starter Systems. This marks the end of the 2402 Upgrade cycle, and all the systems are at the same level: 2402 HFC03.
On March 1-3, two weeks after D/P System Upgrade, HFC04 (green box) was applied to all systems. This HFC04 is for corrections (bug fixes) only.
On March 15-17, another two weeks later, HFC05 (brown box) was applied to all systems. This HFC05 is for corrections (bug fixes) as well as new innovations (features).
This HFC Patch application cycle repeats every two weeks until Release 2408 Upgrade cycle starting on July 26-28 to the Test Systems.
Every month there is one weekend reserved for Global Infrastructure Maintenance (blue boxes).

Blue Green Deployment Method

To shorten the downtime of an upgrade process, SAP S/4HANA Cloud Public Edition takes the advantage of available virtual machines to do the software upgrade (ABAP code in particular). This model reduces productive system downtime drastically. In average, the downtime for production systems is reduced from 2-3 hours to 1 hour.

As Figure 2 illustrated, Blue Version 1 schema is the old set of ABAP codes. Persistency is the customer business data stored in the SAP HANA Database. While old version of the software is running, we create a Green Version 1 schema by copying from the Blue Version 1 schema. While users are still using the Blue Version 1 schema, the Green Version 1 schema is upgraded to the Green Version 2. After all the procedures are done on the Green Version 2 schema, we now connect the Green Version 2 schema to the Persistency and switch the user connections to the Green Version 2 schema. Now the system is running on the latest release. Finally, we drop the Blue Version 1 schema. The blue-green term is from the color of the illustration.

To avoid ABAP code and data structure changes to Version 1 schema (both blue and green schema) during copying and upgrading period, no transports and configurations are allowed. This includes the data migration, as it could alter the table structure. The transports are allowed only after the upgrade, and to the Green Version 2 schema directly. This is the root cause of all the restrictions applied during the upgrade.

Figure 2. High-level Walkthrough of the Blue-Green Deployment

Roughly speaking, above Steps 1- 4 are in uptime phase (business users can still run transactions), and Steps 5 - 6 are in downtime phase (no users are allowed in the system).

From Release 2105 HFC04, we introduced the Blue Green Software Deployment model for all 3-System Landscape system types and 2-System Landscape production systems, in applying patches/HFCs.

From Release 2202, we introduced the Blue Green Software Deployment model for the Major Upgrades.

The concept of the Blue Green Deployment Model was used in on-premises solution in the past (called near zero downtime maintenance, or NZDM) to a limited number of customers, due to the high cost of using the 2nd production scale server ($$$) for a short period of time. With widely available virtual machines for a short period of time in the cloud data center, this approach has been accepted as a normal process in upgrade operations.

The Blue Green Deployment Method applies to ABAP code upgrade, not Business Content activation. It works well in the Central Business Configuration (CBC) based 3SL systems, as Business Content is decoupled from the ABAP code.

Why the Blue Green Deployment Method applies to all system types (D, T and P systems) in 3-System Landscape, and only the production systems in 2-System Landscape?

The Blue Green Deployment Method applies to ABAP code upgrade, not Business Content activation. In 3SL Dev System, the CBC Business Content and the ABAP Code are decoupled. So, we upgrade ABAP code using the Blue Green Method first, then the CBC Business Content subsequently (upgrading and activation).
For 3SL Test and Production Systems and 2SL Production system, there is no involvement of the CBC Business Content upgrade, so we use the Blue Green Method for ABAP code upgrade. The activated CBC Business Content are imported to them via transports.
For the Quality and non-productive systems in 2-System Landscape, since majority of them are Solution Builder based, they are coupled with the ABAP codes. The Business Content activation is the main driver of the downtime. We use the standard SPAM deployment model (see SAP Note 3042314 - Hotfix Collection deployment for RISE with SAP S/4HANA Cloud). The consequence is a longer downtime. This is not obvious in Production System upgrade, but during patch/HFC application for the Quality system, it becomes obvious:

For the Quality and Starter systems in 2SL: 12 hours - from 02:00 to 14:00 UTC on Saturday
For the Development systems in 3SL: 2 hours - from 04:00 to 08:00 UTC on Sunday

Upgrade a CBC Based System

Figure 3 illustrates the timeline of upgrading a development or a production system based on the CBC. The entire upgrade process is divided into two primary phases: the Uptime Phase and the Downtime Phase. During the Uptime Phase, the business users are still using the system for business transactions. It is about 34 hours (2+18+14). Only during the Downtime Phase, no business users are allowed on the system. The Downtime Phase is also called the Major Upgrade Window (MUW). It is about 24 hours.

Figure 3. Detailed Upgrade Timeline for SAP S/4HANA Cloud Development and Production Systems

Let’s focus on the line Milestones. The milestone Start of upgrade preparation marks the beginning of the Uptime Phase. It starts at 0:00 UTC on Friday, or 19:00 EST on Thursday. Thirty-four hours later, it reaches the milestone Start of SAP S/4HANA Cloud downtime processing which marks the end of the Uptime Phase and the beginning of the Downtime Phase. After system switch, we start CBC Business Content upgrade at the milestone End of S/4HANA Cloud downtime processing & start of content upgrade. This process lasts about three hours until next milestone End of content upgrade. The entire upgrade wraps up at the milestone End of Major Upgrade Window, or 10:00 UTC, or 5:00 EST on Sunday.

Let me do a one-to-one match with the Green Blue Deployment Method I just discussed, as in Figure 4.

Figure 4. One-to-One Match between Upgrade Timeline and Blue Green Deployment Method

At the milestone Start of upgrade preparation, the system is still running in the Blue Version 1 schema. Two hours later, we are entering Green Version 1 copying phase for about 18 hours. This is also called Uptime Phase 1. According to SAP Note 3097708 - Release upgrade for RISE with SAP S/4HANA Cloud 2-System and 3-System Landscape and SAP Note 3042314 - Hotfix Collection deployment for RISE with SAP S/4HANA Cloud, there are limitations during this uptime phase. We want Blue Version 1 schema to be stable in terms of ABAP codes and database table structure; otherwise, Blue Version 1 and Green Version 1 schemas are inconsistent.

For 2SL Quality, Starter and Partner Demo Systems, and 3SL Test, Starter, Partner Demo and Dev Systems
- No release of Transports Requests
- No In-App Extensibility (Extensibility Explorer)
- No Data migration ("Migrate your data" app is in read-only mode)
- Or activities such as Scope Extension, Add New Country, Expert Configuration
For 2SL and 3SL Production Systems
- No Imports
- No Data Migration (“Migrate your data" app is in read-only mode)

The next 14 hours are reserved for upgrading the Green Version 1 to the Green Version 2 to the new release. It is called Uptime Phase 2. All restrictions in Uptime Phase 1 still apply.

At the milestone Start of SAP S/4HANA cloud downtime phase, we are officially entering the downtime phase. The first task (about 2 hours) is to switch user connections and Persistency from the Blue Version 1 to the Green Version 2 schema. This will enable users to use the upgraded ABAP codes to conduct business transactions. It is the sole purpose of an upgrade.

For a CBC based system, we not only upgrade the ABAP codes, but also upgrade and activate the Business Content. This task takes about three hours. It is not part of the Blue Green Deployment Method.

The entire MUW reserves 24 hours, but we only used 5 hours so far, because we built-in 19 hours reserve to deal with possible issues. Good news is that our past upgrade experiences show that this MUW can be further reduced. You will see an official announcement on reduced Downtime Phase starting from 2408 upgrade. This is a win-win case for both customers and SAP.

Impact to the CBC/SB System Usage during an Upgrade

Now let me change our perspective: how the Central Business Configuration (CBC) or Solution Builder (SB) system usage is impacted during an upgrade? I put CBC/SB related restrictions into the upgrade timeline for the ease of discussion (Figure 5).

Figure 5. Impact to the CBC/SB System during an Upgrade

The SAP Central Business Configuration (CBC) System allows users to configure business processes. The configuration conducted on the CBC system is deployed to the Development System, and subsequently a relevant transport is created to deliver the same configuration to the Test and Production Systems.

With the introduction of the CBC system, we decoupled the business content from ABAP codes. That is one step forward from the Solution Builder based system. However, we still need to pay attention to the possible impact to the CBC system or the S/4HANA ABAP system during an upgrade.

As illustrated in Figure 5, up until 02:00 UTC on Friday, there is no limitation on the CBC System usage. It is a solid green except we advise our customers don’t run large CBC deployments. The reason is that it is hard to estimate how long it would take for a large deployment, for example deploying 50 scopes from 20 countries. We cannot stop a deployment if it slips into the light green zone (after 02:00 UTC on Friday).

From 02:00 UTC on Friday, we are entering Uptime Phase 1 (copying the Blue Version 1 schema to the Green Version 1 schema). A stable Blue Version 1 schema is a must. Therefore, we don’t want any deployments from the CBC system to the Development System, as the configuration could change the table structure in the Blue Version 1 schema.

For the Solution Builder based system, locking starts earlier than the CBC based system, at 20:00 UTC on Friday. The reason is that Business Content and ABAP codes are coupled together. The importing and activating are executed along with ABAP code upgrade.

For CBC based system, before complete locking at 12:00 UTC on Saturday, you can still work on org structure enhancement, new scope or country addition. This gives users more time to work on the CBC system.

Impact to the ABAP System Usage during an Upgrade

Figure 6 illustrates the impact to the ABAP Systems, namely the Development System and the Production System, during an upgrade.

Figure 6. Impact to the ABAP Systems during an Upgrade

Before Uptime Phase 1 at 02:00 UTC on Friday, although it is solid green, we need to limit the imports from large Git-Enabled Change and Transport System (gCTS). The reason is similar as CBC content deployments as we don’t know how long it could last.

From 02:00 UTC on Friday, to safeguarding the consistency between the Blue Version 1 schema and the Green Version 1 schema, we put the following limitations:

For Production System
- No importing transports
- No data migration
For Non-Production System, like Development System
- No release of transports
- No in-app extensibility
- No data migration
- No customization

From 10:00 UTC on Saturday and on, the system is completely locked up for business users to execute following tasks:

Switch user connections from the Blue Version 1 schema to the Green Version 2 schema and connect the persistency to the Green Version 2 schema.
For the Development System, we import and activate Business Content, and create activated business content transports. This takes about 3 hours.
For the Production System, we only import the activated Business Content. It only takes about one hour.

As discussed above, there might be potential issues need to deal with. We have a 19-hour window built-in for that. Users are not advised to logon to the system until an official email from SAP operations team arrives. At that time, the upgrade is officially completed.

General Process of a Major Upgrade Cycle

Based on the above discussions, I hope it becomes easy for you to understand the overall process of a major upgrade cycle for the SAP S/4HANA Cloud Public Edition. We take the 3-System Landscape as an example (Figure 7), and you can adapt it to the 2-System Landscape systems accordingly.

Figure 7. General Process of a Major Upgrade in a 3-System Landscape

If we take the Test System upgrade as time Week 0, we need to start upgrade preparation work four weeks before Week 0.

Review new innovations/features, new/deprecated Apps, new/deprecated Business Roles in the Preliminary What’s New Doc
Release transports
Initiate an upgrade project

During the Test System upgrade, customers don’t get involved too much most of the time. The job is after the upgrade:

Review the final What’s New Doc
Conduct Regression Tests
Report issues and resolve them before Production System Upgrade
No transports from D to T possible until D/P upgrade is done

The Development and Production Systems upgrade is the heavyweight of the upgrade cycle. You need to plan carefully, especially when you have activities overlapping with the upgrade week as we discussed above, not just the weekend activities.

Watch the restrictions during Uptime and Downtime Phases
If a go-live is scheduled around a major upgrade period, plan the overlap activities carefully

There are still a few more tasks after the Dev/Prod system upgrade:

Sync transports in all 3 systems
Revise Business Roles and Business Catalogs
Deploy updated Business Content to T and P systems

Conclusion

This blog explained the overall process of a major upgrade in the SAP S/4HANA Cloud Public Edition, especially the constraints you might experience due to the upgrade method we use in the ABAP system and the Business Content upgrade in parallel. The overall system downtime has been reduced due to the adoption of the Green Blue Deployment Method. We can see further reduction of the Major Upgrade Window due to the process optimization by the SAP cloud operations team in the coming upgrades.

References

Be a Cockroach: A Simple Guide to AI and SAP Full-Stack Development - Part I

2024-05-09T19:14:30.935000+02:00

Disclaimer: This blog delves into SAP full-stack development, incorporating SAP RAP for both front-end and back-end functionalities, Integration Suite for middleware tasks, TensorFlow for AI/ML modeling, and crafting a personalized system dashboard. Geared towards simplifying complex business systems through engaging stories, it's for those wanting to understand these concepts. If you're already well-versed, feel free to just stop here and explore other content.

I) Introduction (Story):

Most people came here to see what he has to say about cockroaches and their connection to SAP development. Some might be curious to learn about it. Few of you could feel grossed out and think cockroaches are yucky and ugly! But after reading this section, I hope you'll respect these special creatures called “COCKROACH”.

The world is more than 200,000 years old. Lots of animals have lived and expired over time. One of them was dinosaurs—they were huge and strong. Due to changes in the tectonic plates and environment, the Dinosaurs couldn't survive and disappeared. Now, you can see it in movies using computer-generated effects. However, cockroaches have been around for over 1,00,000 years and you can still come across them in your kitchen, living room, bathroom, trash can, and everywhere else. Cockroaches have adjusted to changes in their surroundings, which is why they still exist on the planet.

Even though companies produce items like HIT and Baygon to kill them, cockroaches survive by figuring out how to deal with those products. A study found that certain products cause some cockroaches to behave as if they're intoxicated. Their bodies adapt to these substances. This ability to change is known as adaptation.

There aren't any charities or groups dedicated to protecting cockroaches like there are for elephants and dolphins. Everyone wants to kill cockroach, yet these humble cockroaches keep on living and undefeated by human, and their existence is inevitable. Now that you understand, I trust you hold a greater appreciation for the modest cockroach. Similarly, Consultants must also adjust to shifts in market trends.

The IT market is going through changes like "Artificial Intelligence" and a higher demand for “SAP Full-Stack developers” and so on. In this blog we are go-through about SAP Full-Stack development.

(The story about cockroaches was inspired by a book called "11 Rules for Life" written by Chetan Bhagat)

II) Agenda:

Getting to Know SAP FullStack: Understanding the Full Stack
Background Insights: Delving into the Story Behind
System Design Visualization: Seeing the Technical Architecture
Practical Implementation: Learning the Practical Details Step-by-Step
Wrapping Up: Summarizing Key Points and Looking Ahead
Further Reading: Offering Links to More Research Materials

III) Getting to Know SAP Full-Stack: Understanding the SAP Full-Stack development

Many of our consultants believe that full stack development involves only front-end and back-end development. However, when it comes to SAP development, there's a third component: middleware.

In today's market, relying on just one system isn't enough. Data comes from various sources, and we need to consolidate it to generate reports. So, if you're interested in becoming an SAP full-stack developer, this blog will help you understand the basics of all three elements: front-end, middleware, and back-end, and explain them practically.

Fig1: Basic diagram for Full-Stack development

IV) Background Insights: Delving into the Story Behind

Sundhara Pandian is a big part of Kotravai Coffee Group in Queenstown, New Zealand. He makes really good coffee. His trick? He gets top-notch coffee beans by following a careful process.

Instead of just buying beans whenever he wants, Sundhara Pandian sends a request called a Purchase Order (PO) to a big coffee supplier in Bremen, Germany. But it's not as simple as filling out a form. The PO has to go through a smart system with AI and automation. This system checks the beans in the supplier's stock and confirms the order.

But Sundhara Pandian's job doesn't stop there. The results from the system are put into SAP S/4HANA Cloud. This helps keep track of orders and how much coffee is left.

Basically, Sundhara Pandian does more than just make coffee. He's good at handling complicated systems to make sure Queenstown always has enough beans for coffee lovers.

Let's dive into SAP full-stack development through Sundara Pandian's story as we build the SAP RAP App for PO cockpit, iFlows and AI/ML model.

V) Technical Architecture Diagram: Visualizing the System Design

Fig2: Architecture diagram for E2E – Full Stack development with SAP applications

VI) Technical Implementation: Step-by-Step Integration Details

AIM: (Custom Cockpit and Integrated Goods Receipts):

We're making a simple app for custom Purchase Orders (PO) with basic fields.
Obtaining the GR information electronically, then utilizing a machine learning algorithm to automatically update the GR within our application system (GR automation).
We're getting details about Goods Receipts (GR) from GR automation system and showing them in the custom PO form.

Target Audience:

Individuals with 0 to 4 years of experience in SAP.
Enthusiastic learners eager to explore new concepts and expand their knowledge base.

Before proceeding, please ensure the following prerequisites are met:

Familiarity with basic concepts of SAP S/4HANA Cloud and SAP RAP.
Activation of the ADT-Eclipse, Postman, Integration Suite API plan in your SAP BTP entitlement.
Understanding of fundamental AI and Automation concepts.
Knowledge related to Python, Javascript, System landscape and UI

Step 1: Install the ADT package in the Eclipse. You can refer the below link to download the ADT package in the eclipse.

ADT Link: https://tools.hana.ondemand.com/#abap

Step 2:

Step two has been divided into two sections, each detailed below:

Section-A: Connect to the S/4 HANA Cloud system.
Section-B: Create the modelling with SAP RAP

Go to help-> About Eclipse IDE -> Double check the below highlighted icon from your system.

Section-A: Connect to the S/4 HANA Cloud system

To connect the S/4 HANA Cloud system, please use the below steps.

Type the S/4 HANA Cloud web address: https://<Host>.s4hana.cloud.sap. Remember, select client 80. This client is used for making changes to the system.

Click the "Copy Logon URL to Clipboard" button. Then, open your web browser and paste the URL there. Enter your login details and press enter. After successful login, you'll see the screen below.

Click "Finish" and create your own package name. I've used "ZDEMO" here.

Part 1: Key Takeaway:

Gaining foundational knowledge of systems and landscapes through story-based learning.
Grasping the fundamentals of full-stack development with diagrams
Setting up Eclipse for SAP ADT and establishing a connection to the S/4 HANA Public Cloud system.

Part 2: Coming soon - Keep an eye out for an exciting story-based learning journey as we delve into creating SAP RAP applications.

Part 3: Coming soon - Embark on an exploration of AI and ML with our forthcoming model, create system with a dashboard for ( GR Automation )

Part 4: Coming soon - Learn how to connect the circuit using Integration Suite in our upcoming installment.

Author: If you find this information helpful, please consider clicking the "Like" button on this blog and sharing your thoughts in the comments section below. You can also connect with the author on their LinkedIn profile: [Author's LinkedIn Profile]