domingo, 4 de abril de 2021

Replication of products to a TM embedded in SAP S/4HANA

 Dear friends of SAP TM,

Let’s assume you run a TM embedded in SAP S/4HANA in a sidecar scenario with SAP S/4HANA. When you replicate your master data into the TM embedded in SAP S/4HANA, the master data in the source system often has much more information than actually needed for SAP TM in the target system. Therefore, when replicating the master data, the somewhat ‘unnecessary’ data often requires additional settings and data in the target system which you obviously don’t want to maintain.

In the following, there’s a hint how to handle this regarding the replication of products.

Basically, a product in SAP S/4HANA can have a ridiculous amount of different data.

The multi-million dollar question is, which of those is actually relevant for SAP TM. Quite frankly…the answer is not given anywhere in this blog post. But it’s safe to say, that data from the following tables are required for SAP TM:

  • MARA (General Material Data)
  • MAKT (Material Descriptions)
  • MARM (Units of Measure for Material)

On the other hand, data which you don’t require in SAP TM (except any rare or special cases) is for instance those from tables MARD (Storage Location Data for Material), MARC (Plant Data for Material) and many others.

Now, master data replication to an SAP S/4HANA system needs to be done by DRF (Data Replication Framework). What you really want to do is to replicate only the data actually required for SAP TM (at least for your scenarios). And to do so, DRF has so-called segment filters that can be used to transfer a subset of the data of a master data object.

In our example, we have a product in SAP S/4HANA which has plant / storage location data in table MARD that we don’t want to replicate:

If we would now replicate this product with DRF, its whole data is transferred to the TM embedded in SAP S/4HANA, creating an equivalent copy. With that, it might be, we receive errors that additional settings are needed in the target system.

Therefore, we use DRF with those segment filters (in transaction DRFOUT) by excluding any plant and any storage location:

As a result, data from table MARD hasn’t been transferred to the target system. You can check this in the target system on the database or see the following try to display the view ‘General Plant Data / Storage’ in transaction MM03:

The same can be done for other types of product specific data. I.e. the sales data (stored in table MVKE) can be eliminated from replication by excluding all sales organizations in the segment filter.

I hope this makes your life a bit easier when it comes to the replication of products in a sidecar scenario.

Feel free to share any comments, I appreciate!

SAP Fiori 3: How to put intelligence into your user experience

 In this post, I will give you an overview of how you can help your users get more done, with better results than before, by adding intelligence to your business applications – leveraging design patterns for AI (artificial intelligence) provided by SAP Fiori and its supporting technologies.

Introduction

What does AI actually mean for a user? When does a user think that they are using an intelligent system? Essentially: when the system helps him or her get more done, with better results than before.

How can a business system do this?

  • By automating routine tasks, so that the user doesn’t have to do them.
  • By augmenting and guiding the user, in other words providing insights, by notifying of issues needing attention, providing relevant contextual information for making a decision, making suggestions on how to proceed and providing explanations about why it is making these suggestions.
  • Allowing the user to interact using natural language will make the system appear intelligent to the user, and helps the user interact faster and more easily with the system – for example it is much quicker to simply ask the system “show me overdue orders for product ABCD” than first navigating to the app and searching there.

In other words: automation is not the only way to provide an intelligent enterprise system (see also). Where automation is possible it should be done; where it cannot be done, proactive information, recommendations and decision support along with explanations can often be provided. The figure shows this, with the arrows indicating that over time the amount of automation and proactive support should increase based on feedback and learnings, and as more AI is built into the system.

Blue: Automated, users configure and monitor

Green: Proactive, recommendations (smart)

Red: unique human value-adding activities

Figure 1: Increasing automation and system support allows users to get more done, and focus on value adding work.

Users benefit from automation because they are freed up to do more valuable and enjoyable activities. For these activities, augmenting and guiding the user makes the user more effective – in other words they can get better results with less effort, and with a more enjoyable experience. And natural language interaction gives the user a faster, more natural and even more enjoyable way to interact with the system.

What does this mean for developers?

First and foremost, it is essential that developers understand the needs of the user:

  • which routine tasks could be automated, and how?
  • where and how could the system augment the user? For example, which decisions do users have to take, what contextual information do they need for that, could the system provide suggestions or recommendations along with explanations?

Also, it is important to surface intelligence consistently across all applications: if a user gets contextual information and suggestions for a certain kind of task in one application, then they expect to get the same experience when getting guidance for similar tasks from other applications.

This is where SAP Fiori comes in to play, with design patterns to ensure consistency – for the user interactions themselves as well as for user feedback on the AI outcomes, which simplifies learning.

SAP Fiori design patterns for putting AI in your UX

We follow a human centered AI approach, meaning that we look at the users’ needs holistically, which includes aspects like building trust in addition to functional insights and guidance.

User guidance can be provided both by a graphical UI, a GUI, as well as using a conversational UI – both allow the user to interact with the system and receive guidance. This guidance can be

  • Predictive: the system can analyze historical data and make predictions or forecasts.
  • Proactive: providing insights relevant for the activity the user is doing in the system – in other words analyzing the data in the system and giving the user guidance or suggestions on how to best proceed with the activity.
  • Reactive: helping users react to external triggers or events, such as a machine breaking down or a supplier informing about a delivery issue, by guiding the user and suggesting options for dealing with the situation.

We have identified a number of UX patterns for guiding the user, which are described below. SAPUI5 controls, SAP Fiori elements and the Situation Handling framework in SAP S/4HANA support developing these patterns.

Figure 2: SAP Fiori design patterns for AI support augmentation (user guidance) as well as automation

 

Notifications

Notifications proactively inform the user that there is something which needs their attention – this could be proactively triggered by some insights, or reactive based on an external trigger. Notifications can be via the SAP Fiori notification center, but also indicators on lists or object pages, indicating that a certain object has an issue or needs attention.

Suggestions

Suggestions are the patterns for actually guiding the user on how to best act on a given task or situation. We have identified these three patterns for suggestions:

  • Recommendations for how to proceed, for example recommended actions;
  • Ranking, which means suggesting which items are the most important ones to look at or to take action on, and which ones are less important. For example, you could provide a list of customer opportunities, with the most likely customers at the top, so that users don’t waste their time following up on unlikely customers.
  • Matching, which means that the system suggests that certain items are best matches for other items – for example which payments match to which invoices. This can be automated, but if there are discrepancies, the system can propose which matches are most likely, hence guiding the user. This can be seen as a special kind of recommendation.

Predictions

This pattern covers predictions and forecasts. Forecasts could be visualized in a chart with a forecast for the future months. Predictions could be used to inform a user about when something will run out or fail and need replacing. Both of these are also powerful ways of providing user guidance.

Explanations

Explanations are key to building trust with the user: the system explains why it is notifying you about an issue, and in particular explains the suggestions it is making. This is important because many decisions have high stakes for users, so they need to feel confident that they are making the right decision when following the guidance provided by the system – they don’t want to get into trouble for doing the wrong thing simply because they took the advice provided by the system.

Feedback

Feedback allows users to feel that they are contributing to the AI insights, by indicating how useful the guidance was – allowing the system to learn about which guidance was followed and which not, and hence improve future guidance. This also ensures that users’ trust level remains high.

Situation Handling

Situation Handling is an approach which brings together many of these patterns into one overarching pattern for dealing with business situations – in other words, dealing with issues which need attention. A situation needing attention might be a broken machine, a supplier being unable to deliver on time or contract which will soon expire.

Situation Handling includes notifying the user about the situation proactively, providing suggestions and recommendations on how to deal with it, along with explanations of the situation itself as well as explaining its recommendations.

Situations could be triggered by predictions, by proactive insights or in reaction to external triggers. Situation Handling also foresees a feedback mechanism for users to indicate how helpful the recommendations were, and also monitoring which of the recommendations were actually chosen.

Automation and Augmentation are inter-related

Augmentation and Automation look quite separate, but in fact they are related to one another:

  • Notifications can be used to inform users if errors occurred during automation.
  • Suggestions can also lead to recommendations for automation: if users regularly accept the main recommendation, or regularly accept the proposed matching result, then the system could recommend that these decisions be automated going forward.
  • Explanations are also important for automation – explaining the automation outcome, so that users trust that it is working as expected, or if errors occur, explaining what went wrong.
  • Finally, feedback can be used to confirm the automation rules, or as input for adjusting them.

Learn more

To learn more about how to put AI into your UX using the above patterns, have a look at the section on how to design intelligent systems in the SAP Fiori design guidelines. For supporting natural language interaction, have a look at the Conversational UX design guidelines, which are supported by the SAP Conversational AI technology.

These blog posts give you an overview of the Intelligent Design System:

Keep an eye out on future blog posts, also from my co-author Joachim Sander, design lead for the „Intelligent System“ topic within the SAP Fiori design system.

Situation Handling

These blog posts are a good way to get a comprehensive overview of Situation Handling:

Selected use cases explained in short videos (1 – 2 minutes, plus configuration time for two of them):

Advanced insights, troubleshooting blog posts:

Do also have a look at the documentation:

To get more insights on the design of Situation Handling, have a look at these blog posts:

Source: https://blogs.sap.com/2021/03/25/sap-fiori-3-how-to-put-intelligence-into-your-user-experience/

New Customer Vendor Integration Analysis (CVIA) Check in SAP Readiness Check is Now Live

 Dear All,

We are very happy to announce the go live of a new version of the check for Customer Vendor Integration (CVI) in SAP Readiness Check for SAP S/4HANA.

The mapping of customers and vendors to Business Partners is one of the main preparation steps for a system conversion to SAP S/4HANA and can be a showstopper for the conversion when there are unresolved synchronization issues. This topic has already been addressed in SAP Readiness Check by means of the Business Partners (Business Partner/CVI) check since May 2020. The new Customer Vendor Integration Analysis is the successor of the former Business Partners check, incorporating existing functionality of the prior version, while also offering new capabilities. The new check reports on synchronization status, indicates the implementation effort for the customer vendor integration, and provides information about the integration of master data to and from other SAP systems (such as SAP CRM or SAP Master Data Governance).

 

What’s Included in the New Customer Vendor Integration Analysis:

1. Overview on the Dashboard

 

An overview on the dashboard summarizes the key findings of the check, such as the implementation status of CVI at the time of the analysis. The following scenarios can be displayed:

  • Business Partner not used and CVI inactive:
    No Business Partner records were found in your system. CVI is inactive.
  • Business Partner used and CVI inactive:
    There are Business Partner records in your system, but CVI is inactive.
  • Business Partner used, CVI active, and synchronization issues found:
    CVI is activated in your system. All links between customers, vendors, contact persons, and Business Partner entities are established. However, there are synchronization issues for customers, vendors, and/or contact persons with the corresponding Business Partner entities.
  • Business Partner used, CVI active, and no synchronization issues:
    CVI is activated in your system. All links between customers, vendors, contact persons, and Business Partner entities are established. No synchronization issues have been identified.

In the graphic above, CVI is activated in the SAP ERP system. Not all links between customers, vendors, contact persons, and Business Partner entities are established. There are synchronization issues for some of the customers, vendors, and/or contact persons with the corresponding Business Partner entities. By clicking the tile, you can open the detail view of the check.

 

2. Detail View

Customers

On the Customers tab, information on data volume, data quality and custom fields is presented.

  • The Data Volume section displays the following findings:

The number of customer master data records is compared to the number of records that are already synchronized to a Business Partner. If there is a delta, this indicates that the other customer records still need to be synchronized to Business Partner entities or have to be deleted. The same applies to the count of contact persons.

To resolve identified issues, use the tasks “Post-Processing” and “Completeness Check” in transaction CVI_COCKPIT in your SAP ERP system.

 

The subsequent rows do not show issues but an option for data cleansing – the identified customer and vendor entries can be merged to the same Business Partner:

 

  • The Data Quality section provides an overview of the most common issues, lists the number of data quality issues found per check type, and provides a description of each check type (for example, in which table and field the identified issues appear):

 

 

  • The Custom Fields section provides an overview of append structures and custom fields: If the customer or vendor data tables contain custom fields or append structures, it is necessary to integrate these additional fields in the Business Partner and CVI using the business data toolset (BDT).

 

The SAP Note 2309153 provides a document that explains how to make customer enhancements to the Customer/Vendor integration in order to integrate additional Customer/Vendor fields in the Business Partner and to use CVI synchronization to update them in the Customer/Vendor.

 

Vendors

The Vendors tab shows the same kind of information as the Customers tab, with the respective data sources.

 

Integration

On the Integration tab, the replication of master data to and from the SAP ERP system is shown:

  • Integration with SAP CRM
  • Bi-directional integration with SAP Master Data Governance
  • IDocs
  • SOAP Service

The SAP ERP system shows an integration with an SAP CRM system if data records have been replicated from an SAP CRM system in the past. If you still use SAP CRM for the customer master creation, follow the guidance in SAP Notes 2285062 and 2283695. Otherwise follow the instructions in SAP Notes 2933528 and 2304337 to delete the records.

 

Customers and Vendors: Implementation Effort

If the Customer Vendor Integration has not been performed yet (indicated by CVI inactive in the overview on the dashboard), an additional section on the implementation effort is displayed on both the Customers and the Vendors tabs, depicting factors that usually influence the effort and duration of the customer vendor conversion process.

Typical effort indicators are:

  • The number of account groups
  • The count of customer and/or vendor master records
  • The percentage of records with data quality issues

 

This section shows which indicators were measured in the SAP ERP system and the related results. In addition, it provides visibility into the effort associated with the indicator, for example, “if you have more than 20 account groups in your system, this may result in high effort for the customer vendor integration.”

 

Activating the CVIA Check:

To use the new Customer Vendor Integration Analysis in SAP Readiness Check, proceed as follows:

  1. Refer to SAP Note 2913617 – SAP Readiness Check 2.0. Then refer to the new entry to enable the CVIA check and implement the new SAP Note 3010669.

  2. Execute the program RC_COLLECT_ANALYSIS_DATA.
    The Customer Vendor Integration Analysis has now replaced the former Business Partners check in the program:

  3.  Upload the results of the CVIA check on the SAP Readiness Check launch page. Upon successful upload of the data, the new check is available on the dashboard, in parallel the old Business Partners check tile will then be removed.

 

In the Learn More side panel available in the detail view of the new check, you can find additional information about the customer vendor integration and next steps. For detailed information about performing the customer vendor integration and resolving issues, see the  SAP S/4HANA Cookbook CVI.

 

SAP Readiness Check Team

Source: https://blogs.sap.com/2021/03/29/new-customer-vendor-integration-analysis-cvia-check-in-sap-readiness-check-is-now-live/

domingo, 28 de março de 2021

SAP: Posting Cost Of Goods Sold at Billing (Technical Steps)

 When should COGS (Cost of Goods Sold) be recognized?

Is it okay if we post COGS during Goods Issue although Sales Revenue is posted in another transaction (Billing)?

What if we post Goods Issue then the period ended before we do Billing?! Do we have to do manual adjustments?


Answer

According to the Matching

Principle, COGS and related Revenue must be posted in the same period

SAP standard setup is to post

COGS at Goods Issue BUT it can be changed

If your business cycle can

include Goods Issue without Billing in one period then change SAP setup to post

COGS at Billing instead of at Goods Issue


Technical Steps to Post COGS at Billing:

1) Transaction OBYC > GBB > VAX > Goods in transit account:

Switch the COGS account with a Goods in Transit Account, the goods issue entry will change to below


2) Transaction V/08 > Pricing Procedure > VPRS > Accrual Account Key:

Maintain a new account key and assign to VPRS


3) Transaction VKOA > Assign GL Accounts to the new Account Key:

Assign COGS account in the provision column and Goods in Transit in GL column


4) Change VPRS condition to accept accruals:

This tells SAP to post the VPRS value to the 2 accounts maintained in VKOA

The billing document will be posted as below

Source: https://www.linkedin.com/pulse/sap-posting-cost-goods-sold-billing-technical-steps-abdullah-galal/