How to setup the Required/Mandatory field in BP based on BP role in SAP S/4HANA

Generally, when you do changes to BP field settings as per the above note things will work fine. But, for some cases the results will not be positive! Example, you have made a field as mandatory in customization but when you check in the BP transaction still the field is optional. In this case, follow the below steps.

What to do when a vendor field is displaying as optional though the field has been set to mandatory?

Reproducing the Issue

There could be multiple ways of reproducing the error which might be based on different fields, but I am taking a specific example here:

How to compare an APL model to a non-APL model ─ Part 2

After completing the first part of the blog you should have a hold-out dataset in HANA dedicated to test, for both the Census case, and the California Housing case. In this second part we will build an APL model and a non-APL model on the same training data. Predictions will be made against the hold-out dataset to ensure a fair comparison between the two models. We will use standard metrics to measure the accuracy of our classification models and our regression models.

Regression Use Case

We define the HANA dataframes for training and for test using the tables prepared during part 1:

How to compare an APL model to a non-APL model ─ Part 1

You need to compare an APL classification or regression model to a non-APL model, and you want to make sure the evaluation process is not flawed. This blog should help you run this comparison in a fair manner; it includes code snippets you can copy and paste in your own Python notebook.

The importance of using a Hold-out dataset

To compare the accuracy obtained by an APL model and the accuracy obtained by a non-APL model, the use of the same input dataset for model training and model testing, as shown in the following diagram, can be tempting because it is quick and easy to do:

Creating Reports using SAP Analysis for office: Basics

First we will discuss about why analysis for office is useful for Business intelligence reporting and what are the advantages and the steps to create a report, scheduling it to specific users.

SAP Analysis for Office is a plugin from Microsoft which can be used with excel and power point.

When Excel plugin with SAP Analysis for office we can use the OLAP connection from different data sources (like SAP HANA, SAP BW etc.) and build different kind of dashboard and Dynamic reports. In Finance and COPA arear SAP Analysis for office widely used –

BASIC Concepts in CDS VIEWS

This blog would give basic idea on different concepts which are  used in the  S4HANA CDS view.

It will be helpful for new beginners on basic concepts which we can use while creating a CDS views

@AbapCatalog.sqlViewName:It is mandatory annotation and which is created in  SE11 (16 Characters length) after activating and it will not be same as  view name/entity name.

@AbapCatalog.compiler.compareFilter: It defines the evaluation of filter  condition in path expression. 

True: If they match, the associated join expression is evaluated only once.

False: A separate join expression is created and evaluated for each filter condition.

Add additional Fields in BMBC – New User Group in S/4HANA

How to define the new fields in the BMBC selection screen and Report?

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

Batch information Cockpit:  T-code: BMBC

SPRO -> Batch Management -> Batch Information Cockpit -> Define User-Group-Specific Selection

We can see all the standard SAP templates

SAP Datasphere: Seamless extraction of business insights in multi-cloud environments with HANA Machine Learning and FedML

This blog post describes how SAP Datasphere can be used to provide a seamless data science experience by facilitating the training of machine learning (ML) models on different platforms (e.g. using hana_ml in SAP HANA and using FedML on hypercaler landscapes). Furthermore, it shows how those ML models can work hand-in-hand to provide data-driven insights to business users without the need of expensive data replication and fully preserving the business context of the data. To illustrate the point, a real-life use case is reviewed and the selection of an ML runtime is discussed in the context of data gravity, availability of the required ML tools on the platform and business criticality of the data. The objective of this blog post is to provide a high level concept and consideration guidelines for data scientists and architects when working on similar multi-cloud cases.

SAP Commissions – Data Anonymization @ Database side

Data Anonymization in SAP HANA

Anonymization methods available in the SAP HANA database allow you to gain statistically valid insights from your data while protecting the privacy of individuals.

Why Anonymize?

In a data-driven world, a growing amount of business data contains personal or sensitive information. If this data is to be used by applications for statistical analysis, it must be protected to ensure privacy. Trivial modifications to the data like replacing information that directly identifies an individual such as name or social security number (pseudonymization) or simply removing the information is not enough. Re-identification is still possible, for example if additional information is obtained (referred to as a linkage attack).

RISE Migration with Tenant Copy Strategy

The most particular case about migration is the downtime, estimate the windows that customers need to achieve and perform a good project, but this not always happen and with the native HANA methodology of HANA System replication (HSR) we can mitigate some risk about Downtime, but as you well know to execute HSR is necessary to have the same SID in both HANA Nodes (and others prerequisites – help.sap.com – General prerequisites for HANA System replication),  when the customer already have the same SID of HEC/RISE is good because we review the others prerequisites and we can move forward but when the it cannot be completed we will face issues and the downtime is impacted.

One of this common scenarios is when a customer has already on HEC all infrastructure and wants to move on RISE Contract, if the SID of BD HANA for example is D01 On premise and RISE is D10 and 10TB of size in HANA DB and the Business windows is just 24hrs, in this scenario we cannot move with HSR and is when enter Tenant Replication (Copy / Move) , with this new feature in HANA DB we can move or copy a tenant in few hours (Depend of the bandwidth), for this case mentioned above is possible with good VPN of 100MB/s transfer the tenant to RISE in just 4 hours and later perform the finalize replica and startup the HANA DB in the new target (RISE), then we will proceed with the next steps in app server, post migration and deliver to RISE for post activities migration, we can explain in more details but first we need to fill the prerequisites:

S/4HANA 2022 What’s New – Target PSA in EWM with Automatic WT creation

Definition

The target production supply area (PSA) defines the production supply area of the next production step. It is used if a semifinished product remains in production and is needed for a subsequent production step.

Dependencies --> If the storage location, where the semifinished product is placed upon order confirmation or goods receipt, is not managed by the warehouse, the field is only for information character.

ssl connection from hana studio to sap hana DB

After activating the sslenforce parameter in the hanadatabase, our attempts to connect to the hana database via hana studio were unsuccessful due to an “only secured connections are allowed” error. Here is one of the methods we employed to establish a secure connection with the hana database.

Here are the steps we followed to establish a connection from SAP Hana Studio to the HANA DB.

1. Export the Hana server certificate using sapgenpse as per note 2475246.

Advanced Foreign Currency Valuation in S/4HANA Cloud (Cloud ERP)

Advanced Foreign Currency Valuation

Advanced Foreign Currency Valuation is part of Advanced Valuation in Financial Accounting. Advanced Valuations support you in following accounting standards, for example, IFRS9. The following processes are part of advanced valuation and are realized as job templates in the Schedule General Ledger Jobs app.

1. Post Discounting of Long-Term Assets and Liabilities

2. Advanced Foreign Currency Valuation

3. Post Credit-Risk Based Impairment

4. Post B/S Reclassification

Event Based Revenue Recognition – Sell from Stock (1K2)

The concept of this scope item is to help speeding the revenue recognition process in SAP S/4HANA Public Cloud.

The classic problem is that the revenue is not always recognised at the same time as COGS as the COGS is posted during Goods Issue to customer and then the revenue will be posted during the billing.

With this new feature of Event Based Revenue Recognition – Sell from Stock, system automatically posted the revenue adjustment at the time of Goods Issue (depends on the EBRR Key that you have selected but in this example, I will focus on the Revenue Recognition Key – SFS.

Field Status Variant in SAP

The purpose of this blogs to explain about the field status variant in SAP.

What is Field Status Variant?