We can utilize the Fiori application – Manage Substitution and Validation Rules to create the rules which will be applied to all the standard processes such as standard interfaces, GUI T-codes and managing standard processes in custom program.

In this blog, we will create a custom-defined function in the validation rule on asset creation or modification done through the Fiori app – ‘Manage Fixed Assets’. The rule will validate against the supplier assigned to the asset master record.

Note that the same validation will work through any means of creating or modifying asset master data as mentioned earlier.

Steps to create a custom validation rule

1. Open the Fiori app – “Manage Substitution and Validation Rules” and click on ‘Create Rule’.

2. Enter Business Context, Event, select Rule Type and click on Create.

3. Enter the Rule Name and Description. Decide what should happen post validation in control level. You could give a warning or an error, along with a message defined in the message class assigned here.

4. If there are preconditions, you can assign them. But in this blog, we will create only a validation by clicking on F4 help.

5. Upon clicking the help, we get all the CDS entities list with respect to the business context chosen when we created the rule in step 2. But we also get a list of functions which we can utilize to create our validation rule. Based on our requirement, we can also extend the CDS views from the list through the Fiori app – “Custom Fields and Logic” and we can also create a custom function rather than relying on the four functions we see in the list above.

6. In this demonstration, we will create a customer-defined function and use it for our validation. For that, we will create a class by implementing the interface – IF_FIN_RE_CUSTOM_FUNCTION.
When we implement this interface, it allows us to integrate custom ABAP logic into the Manage Substitution/Validation Rules app. Once the implementing ABAP class is activated, the implementation is made available as a function inside the Manage Substitution/Validation Rules app in the functions list.

To implement the required methods, you can take help from the SAP provided reference class – CL_SUBVAL_WEEKDAY. The class documents the functionality of each method with logic.

Below is the brief explanation of each method –

• IS_DISABLED: Remove the method for visibility in all events or use IV_EVENT_ID for specific event visibility in Manage Substitution and Validation Rules app.
  
• GET_NAME: Returns the name of the customer-defined function
  
• GET_RETURNTYPE: Define the ABAP type for the return value of IF_FIN_RE_CUSTOM_FUNCTION~EXECUTE method. Update the return type based on your needs.
  
• GET_RETURN_VALUEHELP: Returning a CDS view for value help and a field for the function’s return value.
  
• GET_PARAMETERS: Returns a list of function parameters with unique names, specifying technical ABAP types.
  
• GET_DESCRIPTION: Return a message ID/No. for the text description of customer-defined function that is to be displayed in the functions list.
  
• CHECK_AT_RULE_ACTIVATION: Implement this method to enforce checks on parameters passed to a substitution/validation rule, ensuring only specified types or values are accepted for activation.
  
• EXECUTE: Method to actually implement the logic of the function at hand.

Below is the code for the class defined –

CLASS zcl_test_asset_val DEFINITION
  PUBLIC
  FINAL
  CREATE PUBLIC .
  PUBLIC SECTION.
    INTERFACES if_fin_re_custom_function .
  PROTECTED SECTION.
  PRIVATE SECTION.
    TYPES:    gty_country TYPE c LENGTH 2.

ENDCLASS.

CLASS zcl_test_asset_val IMPLEMENTATION.

  METHOD if_fin_re_custom_function~execute.

*   Data declaration
    DATA lv_supplier TYPE c LENGTH 10.

*   Get supplier from parameters
    lv_supplier = is_runtime-parameters[ 1 ]-value->*.

*   Get supplier's country
    SELECT SINGLE FROM i_supplier WITH PRIVILEGED ACCESS
      FIELDS Country WHERE Supplier = _supplier INTO (lv_country).

*   Pass space if country is DE, else 'X'
    IF lv_country EQ 'DE'.
      ev_result = REF #( abap_false ).
    ELSE.
      ev_result = REF #( abap_true ).
    ENDIF.
  ENDMETHOD.

  METHOD if_fin_re_custom_function~get_description.

    rs_msg = VALUE symsg( msgid = 'ZTEST' msgno = '000' ).

  ENDMETHOD.

  METHOD if_fin_re_custom_function~get_name.

    rv_name = 'ZCHECK_ASSET'.

  ENDMETHOD.

  METHOD if_fin_re_custom_function~get_parameters.

    rt_parameters = VALUE #( ( name = 'SUPPLIER' ) ).

  ENDMETHOD.

  METHOD if_fin_re_custom_function~get_returntype.

    ro_type = CAST cl_abap_elemdescr( cl_abap_typedescr=>describe_by_name( 'ZCL_TEST_ASSET_VAL=>GTY_COUNTRY' ) ).

  ENDMETHOD.
ENDCLASS.​​

7. Once the implementing class is activated, we can see the custom function appearing in the list.

8. Once the function is selected, it will pop-up the importing parameters that we have specified in the implementing class’s method GET_PARAMETERS. We can assign the value of parameter as a constant, a field from available CDS views, or another function.

9. We will select supplier from the CDS view – C_ASSETTP and click on save.

10. In our logic we would validate the supplier country. If it is ‘DE’, we pass nothing and the validation is passed, else we pass ABAP_TRUE and its failed.

Now, save the rule and activate it with customizing TR. That’s it. Now, we can go to the Fiori app – “Manage Fixed Assets” and test the validation. Upon saving asset, we get below error if country of supplier is not DE.

The post How to Create a Custom Validation from Fiori App Manage Substitution and Validation Rules appeared first on ERP Q&A.

As the user sets the Validation rule, it checks the validation rule defined on specific fields data. When user is trying to post the transaction and enters data in that specific field, which violates the validation rule, system throws an error message for the user and it will not allow the transaction to post.

It will succeed to post the transaction only when the data is posted in that specific field as defined in the validation rule. It helps to avoid wrong entry at initial stage of posting the transaction.

Whereas Substitution rule is set up to substitute the data immediately upon the entry made. As the user enters the value, system validates according to the prerequisite defined by the user. If the prerequisite rule is met, the system replaces the value entered with other values.

With SAP S/4HANA Cloud 2005, The Manage Substitution/Validation Rules app for JVA is enhanced with the new comparison operator Matches and the new substitution type Table Lookup.

The Matches operator can be used to match a string-type field value against a regular expression.

The Table Lookup substitution type allows user to choose a source field from a custom business object and uses its value to fill in the target field.

Let’s see how it looks and how to configure in the Cloud System with 2005 upgrade:

Apps involved:

• Manage Substitution/Validation Rules
  
• Post General Journal Entries

Business Roles:

Unrestricted read/write for:

• Configuration Expert – Business Process Configuration: BR_BPC_EXPERT
  
• General Ledger Accountant: BR_GL_ACCOUNTANT

Example:

1. Define Validation Rule

Login with the role Configuration Expert – BPC_EXPERT

Go to “Manage Substitution/Validation Rules”

Click on “Create Rule”.

Enter the following:

Context: Coding Block

Event: Coding Block

Rule Type: Validation Rule

Click on “Create”

Under General Information enter the following:

Under Precondition, enter the following:

Under Validation, enter the following:

Click on “Save”.

Click on “Activate”.

2. Post Journal Entry

Login with the role General Leder Accountant: GL_ACCOUNTANT

Enter the following Header details.

Line Item 1: Enter the following details

Line Item 2: Enter the following details

Click on “Post”.

You should receive the below error message.

Click on OK and go to Line Item 1.

Change the Cost Center to CC_CON

Click on “Post”

3. Create Substitution Rule

Login with the role Configuration Expert – BPC_EXPERT

Go to “Manage Substitution/Validation Rules”

Click on “Create Rule”

Enter the following

Context: Coding Block

Event: Coding Block

Rule Type: Substitution Rule

Click on “Create”

Under General Information, enter the following:

Under Precondition, Enter the following:

Under Substitution, Enter the following:

Substitute Type: Substitute with Constant

Click on Save.

Click on Activate.

4. Post Journal Entry

Login with the role General Ledger Accountant: GL_ACCOUNTANT

Enter the following Header details.

Line Item 1: Enter the following details

Line Item 2: Enter the following details

Click on Post.

Click on Display.

Click on Settings

Select Functional area and click on OK.

Functional Area is YB20 which proves Substitution Rule has been triggered correctly.

With this the user can successfully create and validate the rules as per business requirements.

The post SAP S/4HANA Cloud Validation and Substitution rules appeared first on ERP Q&A.

Withholding Tax is a tax that is deducted at the source of income before the recipient receives the payment. It is a legal requirement imposed by governments to ensure that taxes are collected efficiently and timely. The payer of the income withholds or deducts the tax amount and deposits it with the government on behalf of the payee.

We develop functionalities in SAP ERP systems (like SAP S/4HANA) to manage withholding tax effectively. These functionalities include:

• Classic Withholding Tax: Used for simpler tax scenarios where tax is deducted directly during invoice processing.
  
• Extended Withholding Tax: Provides advanced capabilities such as multiple withholding tax types, exemption handling, and reporting requirements.

Localization and Compliance

We ensure the withholding tax functionality adheres to specific country legal and compliance requirements:

• Country-Specific Solutions: Support withholding tax laws in multiple jurisdictions, incorporating local tax rules and thresholds.
  
• Updates for Legal Changes: Continuously update systems to reflect changes in tax laws, ensuring compliance.

Reporting and Documentation

We develop tools and templates for reporting withholding tax:

• Tax Certificates: Generate certificates for tax deducted, which the payer provides to the payee.
  
• Statutory Reporting: Support local reporting formats (e.g., Form 26Q in India).
  
• Audit and Reconciliation: Provide detailed records to help businesses reconcile tax payments with statutory filings.

DRC / ACR Reports:

Digital Reporting Compliance (DRC) is an SAP cloud-based solution designed to help businesses meet statutory reporting requirements by digitally submitting reports to tax authorities. It is part of SAP’s strategy to address real-time compliance needs, driven by governments globally mandating electronic submissions for various tax-related transactions.

Basically the implementation is on SEGW Project(ODATA). So , we would change the method _prepare_entity inside the project ‘FDP_FIWTTH_50BIS’

We should go DPC_EXT class now

Go inside _prepare_entity method

We should add the code inside that method.

WHEN '3500' OR '3600' OR '3700' OR '3800' OR '3900' OR '35A'. 

            IF is_entityset-amountsect405 IS INITIAL AND 
               is_entityset-datesection405 IS INITIAL AND 
               is_entityset-taxsect405 IS INITIAL. 
                      is_entityset-amountsect405 = <ls_consumq>-calcdtxbaseamtincocodecrcy. 
                      is_entityset-datesection405 = <ls_consumq>-postingdate. 
                      is_entityset-taxsect405 = <ls_consumq>-calculatedtxamtincocodecrcy. 
                      is_entityset-withholdingtaxcodename51 = <ls_consumq>-whldgtaxcodename. 
            ELSEIF is_entityset-amountsect4052 IS INITIAL AND 
                   is_entityset-datesection4052 IS INITIAL AND 
                   is_entityset-taxsect4052 IS INITIAL. 
                      is_entityset-amountsect4052 = <ls_consumq>-calcdtxbaseamtincocodecrcy. 
                      is_entityset-datesection4052 = <ls_consumq>-postingdate. 
                      is_entityset-taxsect4052 = <ls_consumq>-calculatedtxamtincocodecrcy. 
                      is_entityset-withholdingtaxcodename52 = <ls_consumq>-whldgtaxcodename. 
            ELSEIF is_entityset-amountsect4053 IS INITIAL AND 
                   is_entityset-datesection4053 IS INITIAL AND 
                   is_entityset-taxsect4053 IS INITIAL. 
                      is_entityset-amountsect4053 = <ls_consumq>-calcdtxbaseamtincocodecrcy. 
                      is_entityset-datesection4053 = <ls_consumq>-postingdate. 
                      is_entityset-taxsect4053 = <ls_consumq>-calculatedtxamtincocodecrcy. 
                      is_entityset-withholdingtaxcodename53 = <ls_consumq>-whldgtaxcodename. 
            ELSE. "If more than 3 income type related to ths (item5) then later will be ignored as max 3 is allowed. 
               lv_linefive_count = 1. 
            ENDIF.

The above code we should add instead of below code.

WHEN '3500' OR '3600' OR '3700' OR '3800' OR '3900' OR '35A'. 

     IF lv_linefive_count IS INITIAL. 

              is_entityset-totalwithholdingtax = is_entityset-totalwithholdingtax + <ls_consumq>-calculatedtxamtincocodecrcy. 
              is_entityset-totalwithholdingbase = is_entityset-totalwithholdingbase + <ls_consumq>-calcdtxbaseamtincocodecrcy. 
            
    ENDIF. 

Here what we have did is, changed the Entity type and written three conditions to store three line items in different lines. For that we should go entity type and add extra 6 fields to store another 6 fields data(Previously, It has only 3 fields to store only one line item, Now, along with that we have added another 6 fields. So that, It can store 3 line items with 3 fields each)

Those 6 fields we have added.

Now, If we add extra fields to the entity type, definitely we should change our form(Adobe form) as well

Now we should go to that form and map the fields to extra fields.

The form name would be ‘FIWTTH_50BIS’

Go inside the form.

Go to layout

Here, we should map the below fields to which we have added the fields in Entity type.

For output, We should post one Invoice and Payment for the Tax type and code which would have income type as ‘3500’ OR ‘3600’ OR ‘3700’ OR ‘3800’ OR ‘3900’ OR ’35A’.

Before that we will see the Tax codes and types in SPRO configuration.

After Mapping done, we should go to the Frond end app and should run our report through AP_MANAGER_TH user.

Now, search for Run statutory reports

Give report name as TH_WHT_50BIS and Reporting Entity name would be ‘TH_WHT_ENT’

Click on Go

Select that report

Now, we will get our desired out put If we run this report and see the PDF file.

Previously It was different form that would give us only one line item.

But now, It would show 3 line items for the 5th line i.e., If the income type is ‘3500’ OR ‘3600’ OR ‘3700’ OR ‘3800’ OR ‘3900’ OR ’35A’.

The post New Implementation for TH_WHT_50BIS(DRC) Report appeared first on ERP Q&A.

This blog is structured to understand the following:

• Cloud ALM Vs Solution Manager
  
• Overview of Cloud ALM
  
• SAP Integrated Tools Overview
  
• SAP Readiness Check to move to SAP S/4HANA
  
• Project Management Approach using SAP Activate Phase
  
• Change Management in Cloud ALM
  
• Manual Testing Use Case Sample

Read More: SAP Solution Transformation Consultant with SAP Cloud ALM Certification Preparation Guide

Cloud ALM Vs Solution Manager

• SAP Cloud ALM is a good choice for organizations that needs an Agile, cloud-based solution that integrates easily with other SAP solutions.
  
• SAP Solution Manager is a better fit for organizations that need a highly customizable tool with a proven track record.

Ultimately, the decision between these two tools will depend on the organization specific needs.

• Solution Manager: Mainstream support for the Solution Manager will end in 2027, and Extended Support will end in 2030.
  
• CALM: Usage rights are included in SAP Cloud Service subscriptions containing Enterprise Support, cloud editions, in SAP Enterprise Support and in Product Support for Large Enterprises
  
• SAP Cloud ALM includes a baseline of 8 GB SAP HANA Memory.

Overview of Cloud ALM

• SAP Cloud ALM enables you to build, run, and optimize your intelligent enterprise.
  
• SAP Activate methodologies with CALM makes it easier to adapt in phases as we along in the CALM usage journey.

SAP Integrated Tools Overview

• SAP has partnered with tools which helps in Business Process Mining, Project Management and Test Automation to make the transition journey easier.
  
• These tools can be used at different phases of the transition journey.

SAP Readiness Check to move to SAP S/4HANA

• SAP Cloud ALM enables to set up references between SAP Readiness Check findings and SAP Cloud ALM project.
  
• With this functionality, we can create new and assign existing follow-ups to the findings within SAP Readiness Check analysis and manage them in SAP Cloud ALM project.
  
• This allows to administrate SAP Cloud ALM project and prepare for a Brownfield conversion or Greenfield Implementation

The integration is available for the following check scenarios:

• SAP highly recommend running SAP Readiness Check tools in the production system to get an accurate picture of actual system usage.

Check analysis information such as the following is available:

How to utilize Cloud ALM Readiness Check Feature:

• Role required to access the readiness check feature:

You might see the below screen when you login initially on CALM Instance.

• SAP Readiness Check analyzes existing system using built-in APIs, which may need to be updated to ensure data is pushed to Cloud ALM to the readiness check analysis.
  
• Each supported scenario provides its own central SAP Note, which guides through the preparation steps required for the specific scenario.
  
• To start a new analysis, input the readiness report as below:

• We can then start reviewing the results of the Readiness Check

Dashboard Analysis as per the sample readiness check report:

We can use the readiness check report to create all the tasks i.e., user stories and subtask and do the follow-ups.

We are now ready to implement a project using SAP Activate Methodology (Phases) and roadmaps.

Project Management Approach using SAP Activate Phases

Project Management contains:

• Definition of teams and roles.
  
• Timeboxes and releases.
  
• Agile methodology using sprints.

Project Creation

Managing Scope

Managing Requirements

Managing User story

Managing Feature and Q-Gates

Change Management in Cloud ALM

• Change Management comes with straight forward flow for changes in SAP Cloud ALM.
  
• SAP is planning to integrate APIs as well with change management process to bring in more automation. With this we can easily embed sub-workflows created via SAP Workflow Management.

Change Management Workflow

Creating and deploying a transport on Cloud ALM

Manual Testing Use Case Sample

Overall steps for Manual testing

Cloud ALM screen for test management

Test Preparation

• Create to create a new test case

• Add the test steps as required and change the status to Prepared. SAVE.

Test Plan

• Create to create a new test plan.
  
• Assign Test Cases to add one or more test cases to the plan
  
• Assign the person responsible for completing the tests and the start/end dates
  
• Change the Status to In Testing when finished, then save.

Test Execution

• Execute the test cases that have been prepared in the Test Preparation
  
• Select the test results as applicable

Defect Management

• Raise a defect if test results are not as expected

Overall Cloud ALM dashboard overview for the Project deliverables summary:

The post All the buzz about SAP CLOUD ALM appeared first on ERP Q&A.

This short overview of abstract entities concept in the context of non-standard RAP business object operations. It outlines their purpose, advantages, and implementation strategies, emphasizing their role in enhancing modularity and flexibility in data modeling.

Purpose

Abstract entities are Core Data Services (CDS) constructs specifically designed to model complex input parameters for non-standard RAP BO operations(actions and functions).

Database Independence

One of the key features of abstract entities is their independence from database persistence. They are particularly suited for parameter modeling and give possibility to redefine parameters on next modelling level.

Reusability

Abstract entities promote reusability across multiple operations. This characteristic enables developers to adopt a more modular approach, allowing the same abstract entity to be utilized in different contexts without the need for redundant definitions.

Parameter Flexibility

These entities support complex structures, including multi-level nested components. This flexibility allows for more sophisticated data representations and enhances the capability to handle intricate business logic.

Binding

Unlike traditional entities, abstract entities are not bound to specific BO nodes. They provides greater adaptability in how they are integrated into various operations.

Improved Separation of Concerns

By decoupling input parameter modeling from the actual business logic, abstract entities facilitate a clearer separation of concerns. This simplification in design leads to more maintainable and understandable code, as the focus can be placed on each aspect of the application independently.

In conclusion, abstract entities serve as a powerful tool for modeling complex input parameters in non-standard RAP BO operations.

2. Implementation details.

I want to highlight how to effectively use abstract entities in ABAP development. One of their key applications is for typing, particularly for action parameters in RAP actions. Let’s begin with a straightforward example.

We make a simple abstract entity with four fields.

@EndUserText.label: 'ABSTRACT ENTITY'
define root abstract entity ZPRU_ABS_ENTITY
{
    ABSTRACTENTITYNAME : char40;
    SURNAME : char40;
    AGE : int4;
    EMAIL : char40;
    
    CHILD : composition [ * ] of ZPRU_ABS_CHILD;
    CHILD_2: composition [ * ] of ZPRU_ABS_CHILD_2;
}

Next, I created a RAP business object with a root entity view (the specifics of which aren’t important for this example) and defined the ‘sendEntity’ action with an input parameter of type ZPRU_ABS_ENTITY.

Let’s have a look at action definition:

managed implementation in class zbp_pru_root_entity unique;
strict ( 2 );

define behavior for ZPRU_ROOT_ENTITY alias ROOT
persistent table zpru_dn
lock master
authorization master ( instance )
{
  create;
  update;
  delete;
  field ( readonly ) dn_no, freq, prod;

  //Flat
  action sendEntity parameter ZPRU_ABS_ENTITY;
  // Deep
  action sendEntity2 deep parameter ZPRU_ABS_ENTITY;
  // Deep Table
  action sendEntity3 deep table parameter ZPRU_ABS_ENTITY;

}

Right now, let’s check RAP business object implementation class.

CLASS lhc_root DEFINITION INHERITING FROM cl_abap_behavior_handler.
  PRIVATE SECTION.

    METHODS get_instance_authorizations FOR INSTANCE AUTHORIZATION
      IMPORTING keys REQUEST requested_authorizations FOR root RESULT result.

    METHODS sendentity2 FOR MODIFY
      IMPORTING keys FOR ACTION root~sendentity2.

    METHODS sendentity FOR MODIFY
      IMPORTING keys FOR ACTION root~sendentity.

    METHODS sendentity3 FOR MODIFY
      IMPORTING keys FOR ACTION root~sendentity3.

ENDCLASS.

CLASS lhc_root IMPLEMENTATION.

  METHOD get_instance_authorizations.
  ENDMETHOD.

  METHOD sendentity2.
    DATA(lv_deep_field_from_abs_entity) = keys[ 1 ]-%param-child[ 1 ]-abstractchildname.
  ENDMETHOD.

  METHOD sendentity.
    DATA(lv_field_from_abs_entity) = keys[ 1 ]-%param-abstractentityname.
  ENDMETHOD.

  METHOD sendentity3.
    DATA(lv_deep_table_field) = keys[ 1 ]-%param[ 1 ]-child[ 1 ]-abstractchildname.
  ENDMETHOD.

ENDCLASS.

Derived type:

As a result, you’ll see the KEYS table, where each row contains a %PARAM component. This component is typed as the structure ZPRU_ABS_ENTITY.

The next step is to demonstrate the use of the ‘deep parameter AbstractBDEF’ and the ‘deep table parameter AbstractBDEF’ in defining a BDEF action parameter.

To do this, we need to extend the abstract entity by adding a BDEF of type Abstract with a hierarchy.

First, I added the ‘root’ keyword to the abstract entity:

One important note: when adding a BDEF to an abstract entity, we initiate the creation of an abstract business object. As a result, we need to construct this business object in a way that’s quite similar to how we build standard RAP business objects. This is why we use keywords like ‘root’, ‘composition’, and ‘association to parent.’

I also created a new abstract entity, ZPRU_ABS_CHILD. Then, I added mutual associations between ZPRU_ABS_ENTITY as the root and ZPRU_ABS_CHILD as the child.

Then, I’ve created BDEF with ZPRU_ABS_ENITY as root entity and Abstract implementation type:

Let’s overview new abstract BDEF:

abstract;
strict ( 2 );
with hierarchy;

define behavior for ZPRU_ABS_ENTITY alias ABS
{
  association CHILD;
  association CHILD_2;
}

define behavior for ZPRU_ABS_CHILD alias CHILD
{

  association ROOT;

}

define behavior for zpru_abs_child_2 {

association third_level;

}

There are 3 main points:

1. add keyword ‘with hierarchy’ to make BDEF opt to deep expanding.
   
2. recreate RAP BO composition tree, add root entity and child entity.
   
3. explicitly mark association to ZPRU_ABS_CHILD.

Finally, I’ve added addition keyword ‘deep’ to action definition to expand action parameter type.

Let’s have a look into typing:

%PARAM typing:

You can notice that to component %PARAM a new nested table with the name CHILD has been added. It’s an effect of keyword ‘deep’ in action parameter definition. Component CHILD has type of table due to cardinality [ * ] in definition of composition in abstract root entity ZPRU_ABS_ENTITY.

Last topic is about addition ‘deep table’ to action parameter definition.

Let’s add it:

Hence, let’s check what has been changed in typing:

As you can see component %PARAM became table, before it was a structure. This is the effect of keyword ‘table’ in action parameter definition.

Lastly, the same principles apply to typing action output parameters. However, one key difference is that we can’t use the ‘deep’ addition when defining output parameters. As a result, the %PARAM component will be incorporated into the output’s derived type as a structure.

A table with summarizing:

The post CDS Abstract Entity and ABAP RESTful Application Programming Model: Input parameter modelling appeared first on ERP Q&A.

1. Register an app for SharePoint API Access in Azure Active Directory

• Logon to your Azure Portal using your SharePoint online credentials
  
• Navigate to Azure Active Directory and select App Registrations
  
• Click New Registration to create an OAuth application

• In the application registration prompt, enter an application name e.g. SharePointOAuthApp
  
• Select the supported account types

Enter the redirect URL for SAP Cloud Platform Open Connectors:  https://auth.cloudelements.io/oauth

2. Configure the registered application’s SharePoint API permissions

The registered application by default has only User.Read permission from Microsoft Graph APIs, so you need to add in permission to access SharePoint REST APIs.

• Select API permissions tab and then click on Add a permission to add permissions for SharePoint REST APIs.

• Select SharePoint to add in the API permissions for SharePoint

In SAP Cloud Platform Open Connectors, access to the API is via the signed-in user.

• Select Delegated Permissions for accessing APIs as signed-in user

• Select permissions shown below, then click Add permissions

Some of the selected permissions require administrator consent 

• After the permission is selected, click on Grant admin access 

The permission may take some time to updated as shown in the warning, so wait for few minutes before selecting the Grant admin consent option.

• Select Yes if you are prompted to confirm the administrator consent

When successful, the status will change to Granted for your user.

3. Generate certificates and secrets for your registered app

For connecting to your SharePoint Online account from SAP Cloud Platform Open Connectors, an OAuth secret and client ID are required.

• Select Certificates & secrets tab, click on New client secret.

• Enter a description for your OAuth secret and add

• Note! Copy and save the generated client secret. You need to provide the secret in order to create the SharePoint connector instance from SAP Open Connectors, and it cannot be retrieved later.

• To get your OAuth Client ID , select Overview tab, copy the Application (client) ID value.

4. Create a SharePoint Open Connector instance in SAP BTP Integration Suite

• In the SAP BTP navigate to Integration Suite
  
• Select Extend Non-SAP Connectivity. If this option is not visible, click  Manage Capabilities and enable Open Connectors capability.

• Select the Connectors tab
  
• Hover over the SharePoint connector and select Authenticate to connect to your own SharePoint account.

• In the connection wizard, enter a name for your connector instance
  
• Enter your SharePoint Site Address in the format {your_sharepoint_domain}.sharepoint.com
  
• In API Key enter your copied OAuth Client ID
  
• In the API Secret dialog enter your copied OAuth secret
  
• Select Show Optional Fields.

• Enable graph authentication to prompt user authentication (this corresponds with the delegated scoped defined on Azure)
  
• Select Create Instance

You may be prompted to enter your SharePoint user credentials if you are not already logged into your SharePoint account

• Trust your app

After successfully creating your authenticated connection to your SharePoint account, you can test it

• Choose Test in the API docs

• Select GET /files to read files from your SharePoint sites

• Click on Try it Out

• Insert the file path for a valid file in the folder (no sub folders) and choose execute

(Note:- If your site contains spaces, then in the Subsite field enter the site name without spaces.)

Once the test has run successfully, the updated file should be available for download.

5. Establish a connection to your SharePoint Open Connector in Datasphere

• Enter your SAP BTP Subaccount Region

The BTP region can be found within the Account Explorer page in the BTP Cockpit

• Enter your Organization Secret
  
• Enter your User Secret

For the Organizational and User secrets, after creating the instance to the app you need, make any type of API request, for example “GET”

The authorization String will contain the necessary detail as well.

6. In Datasphere, create a dataflow to read your SharePoint directory

• Create a dataflow to read your SharePoint directory and post the data into a local table
  
• Create a fact view to transform your data as required
  
• Create an analytical model for external consumption

7. In SAC create your story using your SharePoint-based Datasphere model

The post Accessing SharePoint files from Datasphere using BTP Open Connectors appeared first on ERP Q&A.

Key topics include:

• Export from HANA On-Prem DB and Import to HANA Datalake Filesystem in CSV and PARQUET Formats using HANA Cloud.
  
• Export from HANA On-Prem DB and import to the HANA Datalake Filesystem in CSV and PARQUET formats using HANA Datalake Relational Engine.

Export from HANA On-Prem DB and import to the HANA Datalake Filesystem in CSV and PARQUET formats using HANA Datalake Relational Engine

1. Creation of HANA On-Prem Remote Server in HANA Datalake Relational Engine

Step 1: Open SQL Console

From the Database Explorer of SAP HANA Datalake Relational Engine, open the SQL Console.

Step 2: Create HANA On-Prem Remote Server

Execute the following SQL query to create the remote server for the HANA On-Prem system

CREATE SERVER REMOTE_SERVER CLASS 'HANAODBC' USING
'Driver=libodbcHDB.so;
ConnectTimeout=0;
CommunicationTimeout=15000;
RECONNECT=0;
ServerNode= hanahdb.onprem.sap.server:30241;
ENCRYPT=TRUE;
sslValidateCertificate=False;
UID=USERNAME;
PWD=PaSsWoRd;
UseCloudConnector=ON;
LocationID=SCC-LOC-01';

Please note the following

• REMOTE_SERVER: This is an example name. Replace it with the actual source name
  
• hanahdb.onprem.sap.server and 30241: These are the example server name and port. Replace them with the required HANA On-Prem server details
  
• USERNAME and PaSsWoRd: Replace these with valid credentials
  
• SCC-LOC-01: Replace it with the valid Cloud Connector Location name

Step 3: Verify the Remote Server Connection

Run the following SQL query to check if the newly created remote source is functioning correctly

CALL sp_remote_tables('REMOTE_SERVER');

If the output lists all the tables of the HANA On-Prem database, the remote server has been created successfully

Step 4: Check the Remote Server Details

To view the details of the newly created remote server, execute the following query:

SELECT * FROM SYSSERVER;

2. Create a Virtual Table in HANA Datalake Relational Engine for HANA On-Prem Table

Create a Existing (Virtual) Table

To create a existing table (virtual table) that points to a table in the HANA On-Prem database, execute the following SQL query

CREATE EXISTING TABLE VT_TESTMYTABLE AT 'REMOTE_SERVER..SCHEMA_NAME.TABLE_NAME';

Please note the following

• VT_TESTMYTABLE: This is an example virtual table name. Replace it with the required name
  
• REMOTE_SERVER: Replace this with the name of the newly created remote server
  
• SCHEMA_NAME: Replace it with the schema name of the table in the HANA On-Prem database
  
• TABLE_NAME: Replace this with the actual table name in the HANA On-Prem database

3. Export / Import Operations from HANA Datalake Relational Engine to HANA Datalake Filesystem

Export Virtual Table Data

• Once the virtual table is created in HANA Datalake Relational Engine, you can use SQL commands or tools to export its data

Export from HANA On-Prem and Import to HANA Datalake Filesystem in CSV and PARQUET Formats using HANA Cloud

1. Creation of HANA On-Prem Remote Source in HANA Cloud

Step 1: Login to the HANA Cloud Database

• Open Database Explorer of your SAP HANA Cloud Database
  
• Login to your HANA Cloud Database Instance and expand the Catalog to locate Remote Sources

Step 2: Add a Remote Source

• Right-click on Remote Sources and select Add Remote Source
  
• Provide the necessary details
  
  • Source Name: REMOTE_SOURCE_NAME (This is an example, replace it with the appropriate name).
    
  • Adapter Name: HANA (ODBC).
    
  • Source Location: indexserver.

Step 3: Adapter Properties Configuration

• Default driver libodbcHDB.so will be selected automatically
  
• Provide:
  
  • Server: hanahdb.onprem.sap.server (example, replace with your required server).
    
  • Port: 30241 (example, replace with the correct port number).

Step 4: Extra Adapter Properties

• Enter the configuration: useHaasSocksProxy=true;sccLocationId=SCC-LOC-01;encrypt=yes;sslValidateCertificate=False

Note: SCC-LOC-01 is an example Cloud Connector name. Replace it with the correct one

Step 5: Credentials Setup

• Select Technical User as the credentials mode
  
• Provide valid Username and Password

Step 6: Save the Remote Source

• After entering all the details, click Save
  
• Alternatively, you can use the SQL query below to create the remote source:

CREATE REMOTE SOURCE REMOTE_SOURCE_NAME
ADAPTER "hanaodbc"
CONFIGURATION 'ServerNode=hanahdb.onprem.sap.server:30241;useHaasSocksProxy=true;sccLocationId=SCC-LOC-01;encrypt=yes;sslValidateCertificate=False;'
WITH CREDENTIAL TYPE 'PASSWORD'
USING 'user=Username;password=Password';

Step 7: Verify the Remote Source

• Run the following SQL command to check if the newly created remote source is working

CALL PUBLIC.CHECK_REMOTE_SOURCE('REMOTE_SOURCE_NAME');

• If the command executes successfully without errors, the remote source is functional.

Step 8: View the Remote Source

• Expand the Catalog of the HANA Cloud Database Instance
  
• Right-click on Remote Sources and select Show Remote Sources to confirm your connection

2. Create a Virtual Table in HANA Cloud for HANA On-Prem Table

Step 9: Open Remote Source

• Right-click on the newly created Remote Source (REMOTE_SOURCE_NAME) and select Open

Step 10: Search for On-Prem Table (Remote Objects)

• Use the Schema and Object filters to search for the required On-Prem table
  
• Click Search to display the list of available remote objects (tables)

Step 11: Create Virtual Object

• Select the desired table from the list
  
• Click on Create Virtual Object(s)

Step 12: Define Virtual Table Details

• Provide a name for the virtual table
  
• Select the target schema in your HANA Cloud Database
  
• Click Create to finish the process

The newly created virtual table in HANA Cloud can now be used for operations, including exporting data to the HANA Datalake Filesystem.

3. Export / Import Operations from HANA Cloud to HANA Datalake Filesystem

Export Virtual Table Data

• Once the virtual table is created in HANA Datalake Relational Engine, you can use SQL commands or tools to export its data

The post Read \ Write Data between HANA Datalake and HANA On-Prem DB appeared first on ERP Q&A.

This blog breaks down the key differences in simple, practical terms to help you understand what sets SAP Cloud ERP Private apart and how it can benefit your business.

Why Move from On-Premise to the Cloud in general?

With today’s rapid pace of innovations, organizations are facing new opportunities along with new challenges, including the need to scale and adapt at extraordinary speed. However, legacy applications, including on-prem ERP systems, that once were the backbone of business operations, are holding back companies from taking advantage of these innovations due to outdated processes, disconnected data, and disparate systems.

With the transformation to the cloud, organizations benefit from:

• Faster Innovation: Get immediate access to the latest capabilities as they are released, including core application updates and embedded AI with Joule.
  
• Better Productivity: Modernize the user experience with Fiori apps and the conversational AI assistant, Joule, helping teams work faster and more intuitively than with the traditional SAP GUI.
  
• Connected Insights: Simplify cross-company analytics with prebuilt, SAP-managed data products and ready-to-use intelligent applications.
  
• Lower Total Cost of Ownership (TCO): Let SAP operate your environment for enhanced security, resilience, and scalability, freeing up your team to focus on strategic business initiatives.

You may ask yourself, what does this mean in detail, what are the benefits of moving to SAP Cloud ERP Private?

Here’s a closer look at the specific advantages you gain by moving to SAP Cloud ERP Private.

The 4 Pillars of Differentiation

To begin with, SAP Cloud ERP Private is an essential part of SAP’s corporate strategy and delivers innovations in each of its domains: AI, Data and Apps, which is not the case with on premise products.

There are four main key pillars that set SAP Cloud ERP Private apart from on-premise:

Let’s go into the details of each pillar.

1. Functionalities in and around the core

The SAP Cloud ERP Private Edition unlocks new and exclusive capabilities that strengthen your core processes. These include:

Existing Add-Ons:

Powerful solutions like Central Procurement, Central Finance and Extended Service Parts Planning are available for new customers only with the transformation to SAP Cloud ERP Private. A new add-on, available since release 2025 FPS0, Integrated Business Communications, is available only for SAP Cloud ERP Private customers. It allows users to send communications to customers and suppliers using business partners directly from within SAP Cloud ERP Private, to design the communication and to track responses. In the upcoming Feature Pack Stack 1, it is planned to even initiate conversations from within business documents like a sales or purchase order.

Planned Innovations:

Look forward to SAP ERP Cloud Private only innovations such as multi-stage intercompany sales and stock transfer.

This feature is designed to streamline logistics and finance across a complex corporate group with multiple entities, improving efficiency and transparency, and is planned with Feature Pack Stack 1 of 2025. It eliminates the limitation of Advanced Intercompany Sales, which enables business between two affiliates within one group only.

Sustainability Solutions:

In case of being on a transformation journey to SAP Cloud ERP Private, benefit from solutions like SAP Sustainability Control Tower, Sustainability Footprint Management, and Green Ledger to embed ESG data directly into your core business processes.

Packaged Applications:

The Cloud ERP Private package includes additional entitlements for business applications (like SAP Signavio and SAP Business Network), transformation tools, and extensibility with the SAP Business Technology Platform (BTP), accelerating your time to value.

In general, we recommend going to SAP Road Map Explorer to find innovations that are delivered with SAP Cloud ERP Private and only with SAP Cloud ERP Private.

2. Joule and Business AI

This is where the future of ERP becomes tangible. SAP Cloud ERP Private delivers AI capabilities that are not available to on-premise customers.

Joule, Your AI Copilot:

Role-based AI assistants in Joule help your employees work faster and smarter. With providing a conversational interface, Joule performs four basic basic patterns: navigate to business context related transactions, information about how to do a specific action by consuming user assistance content, perform transactions on business documents and get analytical insights (requires SAP Analytics Cloud). These base skills are available across the lines of business in SAP Cloud ERP Private:

Business AI:

Business AI in SAP Cloud ERP Private comes in two forms: AI features and AI agents, delivered across the lines of business:

AI features use generative AI or AI services such as document extraction and personalized recommendations. These premium AI features go beyond simple commands, automating, accelerating and predicting business processes in SAP Cloud ERP Private.

Examples are:

The automatic creation of in-house repairs and repair objects by scanning incoming paper documents like purchase orders or packing lists:

The planning of resources and predictions of workload for picking and packing using historical and real-time data:

Monitoring and resolving sales order fulfillment issues by using generative AI:

AI Agents (currently in Beta): These agents take AI a step further by proactively managing complex tasks and solving business challenges. Role-based AI assistants in Joule orchestrate agents, accelerate workflows, and drive connected business outcomes at scale.

Examples are:

The Accounts Receivable Agent helps resolve overdue payments by analyzing balances and recommending actions:

The Maintenance Planner Agent continuously analyzes real-time data and suggests maintenance schedule adjustments, reprioritizing tasks and improving asset health:

3. Unmatched Data Insights

Instant access to structured and harmonized data in real-time is a prerequisite for faster decision-making, which is critical to staying competitive in today’s business climate. At the same time, organizations struggle with scattered data lakes and various data sources that lack common semantic data integration, making it difficult for businesses to extract meaningful insights.

With SAP Business Data Cloud we will step on this opportunity and deliver a unified data platform that centralizes and seamlessly integrates data from SAP and non-SAP sources all by persevering in its critical business context.

How does this relate to SAP Cloud ERP Private?

SAP Cloud ERP Private users benefit from SAP-managed data products, which are ready-to-use building blocks for analytics and reporting. These data products are delivered and maintained by SAP, saving time and effort compared to building custom solutions in on-premise environments. Prebuilt and curated data products turn raw sources into ready-to-run, semantically consistent building blocks you can trust, whereas on-premise users would have to create their data products on their own.

SAP-Managed Data Products:

Gain access to a growing library of over 140 pre-built, semantically aligned data products for SAP Cloud ERP Private. These are maintained by SAP and ready to use, significantly simplifying cross-solution analytics.

Intelligent Applications:

Data products are the basis for intelligent applications, which are pre-configured, ready-to-use and SAP-managed dashboards and analytics. These apps leverage SAP Analytics Cloud as the key front-end solution for visualization, simplifying the process of creating interactive reports and dashboards. Intelligent Applications reduce complexity, requiring only installation and role assignment for consumption.

Example:

Working Capital Insights: An established SAP Analytics Cloud story, now embedded in the BDC data product concept to help finance teams optimize cash, DSO/DPO and working capital levers.

4. Excellence in cloud operations

With SAP Cloud ERP Private, SAP manages the system infrastructure, security, and lifecycle management. This means your team is freed from routine maintenance and can focus on driving business value, all while benefiting from the scalability and security of a modern cloud environment operated by SAP.

• Streamlined operations and support, enabling the handover of technical operations for your mission-critical system to SAP
  
• High availability of your mission-critical systems based on a standard service level agreement (SLA) of 99.7% for your SAP Cloud ERP Private
  
• Lower total cost of ownership (TCO) through a subscription-based model and the increased cost efficiency of shifting upfront capital expenses to operating expenses

Summary

For organizations on SAP ERP or SAP S/4HANA on-premise, SAP Cloud ERP Private offers a clear path to modernization. It delivers faster innovation, real-time analytics and data insights, superior user experience with Joule and Fiori, powerful embedded AI features, and the operational simplicity of a managed service. With upcoming highlights like multi-stage intercompany processes and a rapidly expanding catalog of AI use cases and data products, it represents the next step in intelligent ERP.

Which of these differentiating features, such as the AI Agents or the pre-built data products, seems most relevant to your business needs right now?

The post Key differences between SAP S/4HANA and SAP Cloud ERP Private appeared first on ERP Q&A.

This mini blog post demonstrates how to check backend data in S/4HANA Cloud,Public Edition as compared to traditional approach of using SE16N

Here in this context we will discuss about two Fiori applications –

1. View Browser
Role needed - SAP_BR_ANALYTICS_SPECIALIST
Catalogs - SAP_CORE_BC_EXT_AQA_PC

2. Customer Data Browser
Role Needed - SAP_BR_ADMINISTRATOR_DANA
Catalog - SAP_CORE_BC_CDB_PC

View Browser –

You use this app to view the structure of the CDS views and two other important information “Key User Release state” and “Cloud Development release state”

Lets take the example of the CDS view for Product master data – I_PRODUCT

When you open I_PRODUCT from this application as shown in the image, it shows you the data types and also the underlying tables and other views that are used for association.

The backend referenced tables can be seen from the tab “Cross Reference”

If you want to check the underlying table for I_PRODUCTTEXT you go inside that view.

Customer Data Browser –

With this app you get to see the actual backend data. Here also we take the reference of standard CDS view – I_PRODUCT.

The basic landing page of the app looks like the one in below image. There are two tabs one for “Tables” and one for “CDS Views”. We only have access to the tab “CDS Views”

Enter the name I_PRODUCT in the search box

Click on the CDS view to see the data.

You can switch between technical names and functional names of the fields

The post View/Access backend data in S/4HANA Cloud, Public Edition appeared first on ERP Q&A.

It’s time to look beyond the traditional and explore the powerful, modern alternatives that offer enhanced flexibility, blazing speed, and a better alignment with contemporary architectural demands. The shift isn’t just about new technology; it’s about enabling a truly connected enterprise.

Why Move Beyond Traditional IDocs?

While IDocs still have their place, especially in legacy scenarios, modern business requirements often call for more:

• Faster and More Efficient Data Exchange: In today’s real-time world, batch processing might not be enough. New integration methods enable instant data flow.
  
• Better Alignment with Modern Integration Standards: APIs, for instance, are the lingua franca of modern application development, making it easier to connect diverse systems.
  
• Enhanced Flexibility and Scalability: Cloud-native solutions offer the ability to scale integration capabilities up or down as needed, without massive upfront infrastructure investments.
  
• Improved Real-time Capabilities: Critical for scenarios like e-commerce, real-time inventory updates, or immediate financial postings.

The Key Players in Modern SAP S/4HANA Integration

So, what are the alternatives you should be exploring in the SAP S/4HANA era?

1. APIs (OData, REST, SOAP): The Real-time Connectors APIs are the backbone of modern, agile integration. They allow for standardized, performant, and often real-time communication between systems.

• OData: A standardized protocol for building and consuming RESTful APIs, heavily used in SAP Fiori apps and often preferred for exposing SAP data.
  
• REST (Representational State Transfer): A widely adopted architectural style for networked applications, offering lightweight and flexible communication.
  
• SOAP (Simple Object Access Protocol): While considered more traditional than REST, SOAP is still robust and used for complex enterprise integrations requiring strong typing and strict contracts.

2. SAP Ariba Cloud Integration Gateway (CIG): Streamlining Procurement For businesses leveraging the Ariba Network for procurement (think buying, invoicing, catalogs), CIG is a game-changer. It provides a seamless, standardized, and pre-packaged way to connect your SAP S/4HANA system to the Ariba Network. This eliminates much of the custom development typically required for buyer-supplier integration, leading to faster implementation and reduced operational costs.

3. SAP Business Technology Platform (BTP) Integration Suite: Your Cloud-Native Integration Hub The BTP Integration Suite is a comprehensive, cloud-native integration platform-as-a-service (iPaaS) offering. It’s designed to handle a wide array of integration scenarios, from simple point-to-point connections to complex orchestration.

• Capabilities: Includes capabilities for API management, enterprise messaging, open connectors, data intelligence, and process orchestration.
  
• Flexibility: It’s a powerhouse for integrating SAP with non-SAP systems, cloud-to-cloud, and on-premise-to-cloud scenarios.
  
• Scalability: Being cloud-native, it offers inherent scalability and resilience, adapting to fluctuating business demands.

4. SAP S/4HANA Output Management: Modern Document Handling This isn’t just about data exchange between systems, but about how your SAP S/4HANA system communicates outward with documents like invoices, purchase orders, or shipping notifications. The new Output Management framework offers a flexible and modern way to handle these outputs, supporting various channels (print, email, EDI) and formats, moving away from older SAPscript or Smart Forms methods.

5. File-Based Integration: Still Relevant for Specific Scenarios While the focus is on real-time APIs, file-based integration still holds value for certain use cases, especially with large data volumes or where real-time updates aren’t critical. Modern file-based approaches often involve secure file transfer protocols and intelligent parsing mechanisms, sometimes orchestrated via BTP Integration Suite.

The Integration Evolution

The move away from IDoc-centric integration in SAP S/4HANA is a testament to the broader digital transformation happening across enterprises. These new integration technologies empower businesses to:

• Respond to market changes more swiftly.
  
• Automate end-to-end processes more effectively.
  
• Gain real-time visibility across their operations.
  
• Build more resilient and agile IT landscapes.

Understanding these modern integration paradigms is crucial for anyone working with or planning to implement SAP S/4HANA. It’s not just about technical knowledge, but about envisioning a more connected and efficient future for your business.

The post Navigating Modern Integration in SAP S/4HANA appeared first on ERP Q&A.