Planned Release of SAP HANA 2.0 SPS 06

Ten years ago, when we launched SAP HANA as the first in memory database, it raised the bar for enterprise-class data processing. SAP HANA continues to provide the data management foundation needed to deliver the Intelligent Enterprise, and, now, more than 33,000 customers run their most mission critical workloads on SAP HANA. Today, I am pleased to share the planned release of SAP HANA 2.0 SPS 06 in December 2021.

As SAP HANA continues to grow and change, we remain committed to supporting our customers in maximizing and safeguarding their existing investments as their chart their path into the future. This is why several improvements in TCO and usability, as well as a continued focus on stability and quality, are planned for SAP HANA 2.0 SPS 06. This includes extensions for backup and recovery, online DDL, and capture and replay.

We have also planned improvements to SAP HANA smart data access, including support for new versions of Oracle and Microsoft SQL, as well as improved SAP HANA machine learning capabilities thanks to new PAL algorithms coming with support for Python 3. There are also further updates to SAP HANA native storage extension, which complete the big data capabilities of SAP HANA and enable reduced TCO for larger database instances. In addition, SAP HANA cockpit SPS 13 is planned for Q2/2021.

Since SAP HANA 2.0 SPS 05 is our long-term maintenance release, SAP HANA 2.0 SPS 06 is planned for a standard, two-year maintenance window.

As you can see, we have many exciting features and updates for SAP HANA 2.0 SPS 06, and we’re looking forward to seeing how our customers continue to use SAP HANA to gain business value from their data!

If you have any questions, please make sure to visit the SAP Community Q&A for SAP HANA or submit your question directly.

Remote Working: 3 Steps to Maintain Company Culture for Small to Medium Size Businesses

You’ve seen the headline 1000 times and in one way or another, it’s probably something you’re trying to navigate yourself. Ready or not, Covid-19 has forced us to reevaluate how we work and where we work. Remote working is the new normal, but what does this mean for small to medium size businesses and how are you ensuring that your company culture doesn’t fall apart in the process?

After some research, I came across an article by Susan M. Heathfield titled, How to Maintain Company Culture While Remote Working. According to the article, in a study conducted by Hinge Research Institute, it was found that over half of respondents believe culture is just as important as pay when seeking new employment. I personally would argue that this is even more important when talking about SMBs. SMB’s tend not to have the same amount of resources as larger enterprises, so maintaining a strong company culture is paramount in keeping your employees motivated and moving forward. With this in mind, I thought it might be interesting to share the 3 steps which I think are most crucial for SMBs to think about in this “new normal”.

Focus on and Define the Culture

 If you find yourself asking, “what exactly is my company’s culture?”, then you might want to take some time to concretely define the aspects of your company that differentiate it from others. These could be traditions, norms, daily meetings, how you approach employee development, or even the weekly lunch your employees share together. Involve your fellow employees and ask them what parts of the company they find most important.

You might be saying, “Okay, I’ve defined my company culture, but how do I translate that to remote working?”. You might be surprised but it’s simpler than you think. Whatever you do in-person at the office, do online too. Bring those weekly team meetings online. Share lunch together (virtually of course). If your company supports a collaborative culture, utilizing a software such as Microsoft Teams will enable your employees to continue working together in an efficient and safe manner. One of the many benefits of working for an SMB is that you generally will know if not all of, a large portion of your coworkers. Giving your employees the tools for them to continue communicating with each other and building relationships is critical to maintaining and strengthening your company culture.

Something that’s often overlooked when talking about remote work is the physical aspect of it. The office also plays a central role in company culture and this part can be easily lost in remote work. The atmosphere surrounding your workspace is pertinent to worker efficiency and staying focused. For example, allowing your employees to take their office chairs home with them might help make their environment feel a bit more like the office.

Trust your Employees

 Trusting your employees is the cornerstone to remote working. You might be concerned that your workers won’t do what they are supposed to without someone watching them. Multiple studies have shown that remote workers are as productive, if not more productive in remote settings. At the end of the day, you wouldn’t have hired these people if you didn’t believe in their abilities to succeed in their role.

At the end of the day you wouldn’t have hired these people if you didn’t believe in their abilities to succeed in their role.

Despite that, there are ways to support your employees without micromanaging their every move. Some of the tools that the article mentioned to support remote work are:

  • Trello: workflow automation tool with collaborative “boards”
  • Slack: Collaboration tool for communication and file sharing
  • Cisco Jabber: Communication tool for messaging, calling, and conferencing

Take a look at different tools and find out which tool best supports the needs of your workers and company. It’s key to understand that your employees are competent and able to work on their own accord. By sharing and allowing collaboration on the day-to-day tasks of your employees, their motivation will increase as well.

Work-Life Balance

Remote work has the negative tendency to blend home-life and work-life into one. It can be quite a daunting task to stay focused while your bed and work desk are in the same room. You must also consider those who must look after little ones who might be a little bit more restless than normal without school and extracurricular activities. The article suggested that childcare support, flexible hours, and establishing a concrete schedule for important meetings and events are a few of the ways you can support your workers in the new normal.

Conclusion

 Although the idea of remote working has existed for a few years now, 2020 has forced us to adapt and learn quickly on how to shift to remote working. We’ve learned that employees can work from home and be just as efficient as their in-office colleagues. This is great for businesses, especially SMBs. Companies can now source talent on a global scale, finding the best fit for their company culture and the individual role. No one has remote working completely figured out but knowing how to maintain and build your company culture in the remote age will give you an advantage above your competitors.

Please share your experiences, tips, and thoughts on remote working below! If you’re interested in reading more about topics related to small to medium size businesses, check out our community page here: https://community.sap.com/topics/smb

We are building a great community where those involved with SMBs can ask questions, find answers, and share their thoughts and ideas! Join the community today!

Questions related to small to medium size businesses? Don’t hesitate to ask anything (Directly related to SAP or not) here: https://answers.sap.com/tags/2521823005136277121291

P.S. My name is Justin and I’m the new SMB community advocate. You will probably be seeing a bit more of me in this community so don’t hesitate to connect and reach out, I’m always open for a discussion!

SAP is One of the Best Companies to Work by Glassdoor in 2021

Glassdoor revealed its annual list of Best Places to work in 2021. The ranking is decided based on employee reviews and ratings, conducted by Glassdoor’s awards team.

For the past consecutive 5 years, SAP has been honored to be recognized as a ‘Best Places to Work’ recipient in multiple markets. We are one of only 3 employers who are being recognized in 4 out of 5 markets.

SAP France #3
SAP Germany #7
SAP Canada #8
SAP UK #9

SAP’s unique culture is valued by our employees around the world. While it’s natural that rankings may fluctuate, SAP has held a consistent place on the Glassdoor Employees’ Choice Award, recognizing the Best Places to Work in 2021.
The Employees’ Choice Awards program, is based on the input of employees, who elect to provide feedback on their jobs, work environments and companies on Glassdoor, the worldwide leader on insights about jobs and companies

On Glassdoor, current and former employees voluntarily and anonymously share insights and opinions about their work environments by sharing a company review, designed to capture an authentic inside look at what a specific job may be like at a particular company.
When sharing a company review on Glassdoor, employees are asked to rate their satisfaction with the company overall, and key workplace factors like career opportunities, compensation and benefits, culture and values, senior management and work/life balance.

We remain committed to creating an amazing experience for our employees to foster a workplace of excellence Thank you to all employees who took the time to share their perspective on what it’s like to work here. We appreciate the valuable feedback and insights. And will continue to listen and act on feedback.

We want to amplify and encourage everyone to share this great news on Social. Therefore, we want to provide the following links:

Update: Future SAPUI5 versions will no longer support Microsoft’s legacy browsers

This blog highlights the end of support for Microsoft legacy browsers by future SAPUI5 versions and the recommended activities for our customers and partners.

What?

SAPUI5 supports a range of browsers and platforms. Microsoft Internet Explorer 11 and Microsoft Edge Legacy (EdgeHTML) are legacy products with limited maintenance from Microsoft. Both will not be supported by future SAPUI5 versions. Specifically, this means

SAPUI5 will no longer support IE11 starting with SAPUI5 1.88 (2104)

This does not affect any support statements for the new Microsoft Edge (Chromium) browser, see SAP Note 2884143.

Why?

Microsoft IE11 and Microsoft Edge Legacy (EdgeHTML) are legacy products, which do not fulfil the requirements of a modern browser regarding features, security, performance, etc. Microsoft has limited the support for both products:

To ensure a secure environment for running business-critical solutions, SAP recommends using the latest version of a modern and secure browser.

When?

The SAPUI5 end of support for Microsoft IE 11 was announced earlier in the SAPUI5 documentation. Looking at the SAPUI5 versions and their maintenance status, this now means SAPUI5 will no longer support IE11 starting with SAPUI5 1.88 (2104).

  • SAPUI5 1.84 (2011) is the last long term maintenance version supporting Microsoft IE11 and Microsoft Edge Legacy.
  • SAPUI5 1.87 (2103) will be the last SAPUI5 version supporting Microsoft IE11. All SAPUI5 versions up to and including SAPUI5 1.87 will continue to support IE11 as long as they are in maintenance. (Please note: no Microsoft Edge Legacy support due to the announced end of life date.)

Depending on the SAP products used and the respective SAPUI5 version consumed by these products, different product releases are affected with different timelines.

Recommended Action

SAP always recommends using the latest version of a modern, supported browser according to SAPUI5 Browser and Platform Support. Microsoft recommends transitioning to the new Microsoft Edge browser.

For SAP solutions using SAPUI5, keep an eye out for announcements concerning the respective products. If you are using Microsoft IE11, it can be helpful to temporarily stay on SAPUI5 1.84 – 1.87 (see above) until your environment is updated to a supported browser.

More Information

Business Application Studio & Launchpad Services in Cloud Foundry

Hello All

These days, we have seen many blogs explaining in & arounds of SAP Business Application Studio (BAS). I blogged out few experiences I came across while using BAS & Launchpad Services.

Below are the ways in getting the templates for applications creation in BAS.

  1. View > Find Command > SAP Business Application Studio: Create Project from Template
  2. View > Find Command > Yeoman UI Generators

     3.Help > Welcome

I have created an SAPUI5 application using SAP Fiori Freestyle Project template.

To run the application, goto Run Configurations from left pane.

Click on + icon and choose the application we wish to run. Follow the below steps based on our requirements.

Create%20a%20new%20service%20instance

Create a new service instance

Select%20CF%20space

Select CF space

If we have multiple applications exposed, there is an option available to unexpose the active ports

Output

Output

Build & Deploy mta.yaml file. Replace the instance with subaccount

We should be able to view below details after deployment in CF.

To configure our application in Launchpad service, use below object in manifest.json under sap.app

We can set the “hideLauncher”: true for SAP Fiori Launchpad plugins

Build and Deploy again. Now open launchpad service. My application is available in the content manager.

Title > appTitle in manifest.json

Description > appDescription in manifest.json

ID > Combination of HTMLModuleName and Namespace provided during creation of application

Finally configure Group, Catalog & Role. Go to site.

Please do comment if any.

Thank you!!
#EnhanceLearning
BR// Dhanasupriya Sidagam

bgRFC use case – Asynchronous event publishing


Introduction:

Have you ever wondered how you can decouple your event publishing/streaming from the actual transaction SAP Netweaver for ABAP? This can be achieved asynchronously by utilizing the bgRFC mechanism.

What is this blog post about?

  1. This blog post is not a technical introduction to bgRFC concept. You can always refer it in the SAP Help.
  2. This blog post is not a formal or official recommendation but to share the idea, individual learning and project experience of decoupling event publishing/streaming from the actual transaction using bgRFC.

What do I want to achieve?

  1. To decouple/separate the LUW of event publishing from the LUW of the actual transaction. Thus, any uncaught exception in the event publishing will not interrupt the successful commit of the actual transaction.
  2. To improve performance by decoupling/splitting the execution to different work processes. The event publishing is considered less critical and can be executed asynchronously.
  3. To provide manage the system allocations used to process the event publishing based settings in logon/server group used in the inbound destination as well as bgRFC specific settings at system, application or destination level, thus, preventing it from occupying all available work processes in the system which could result in deterioration of user experience or other critical business processes in your system.

What is bgRFC?

You can use your favourite search engine to look for “sap bgRFC“. Please check your system support patch level of your SAP Netweaver for ABAP environment to match the documentation that you will be referring to. Instead of redefining using my own words, below are the explanation extracted from SAP Help.

The bgRFC allows applications to record data that is received later by a called application. When the data is received, you must ensure that the data was transferred to the receiver either once only in any order ( transactional) or once only in the order of creation ( queued).

bgRFC is the successor to tRFC and qRFC, with significant improvements in terms of performance and functionality.”

The SAP Help provides quite a comprehensive explanation on the following areas of the bgRFC.

  • bgRFC: Architecture
  • bgRFC: Configuration
  • bgRFC: Administration
  • bgRFC: Programming

Also a very good introduction about bgRFC can be found in the following page,

https://support.sap.com/en/alm/solution-manager/expert-portal/monitoring-of-integration-scenarios/bgrfc-channel.html

And, lastly don’t forget to check on the SAP Support websites for the SAP notes related to your support level to eliminate already known issues that hinder the usage in your application.

The high-level design of my use case:

[Payment Posting] -> [BADI] -> [bgRFC] -> [ABAP proxy] -> [SAP PO] -> [JMS topic]

I have tested on the following environment.

  • SAP_BASIS 750 SP0015
  • SAP_ABA 750 SP0015

In my Proof of Concept scenario, i would like to publish an event for every payment posting in SAP Banking Services 9.0. During the payment posting, a standard BAdI will be called to generate the payment correspondence. I have implemented the BAdI to the bgRFC, instead of calling the ABAP proxy directly. This allows me to decouple the logical unit of work (LUW) and processing of the event publishing (mapping, formatting and calling the ABAP proxy) asynchronously.

 DATA: lx_bgrfc_error TYPE REF TO cx_bgrfc_error. DATA: my_destination TYPE REF TO if_bgrfc_destination_inbound. DATA: my_unit TYPE REF TO if_trfc_unit_inbound. DATA: dest_name TYPE bgrfc_dest_name_inbound. TRY. dest_name = 'WS_BGRFC_INBOUND_PY_POST_NOTF'. "change this according to yr inbound dest name my_destination = cl_bgrfc_destination_inbound=>create( dest_name ). my_unit = my_destination->create_trfc_unit( ). my_unit->disable_commit_checks( ). CALL FUNCTION 'Z_PY_POST_NOTF_OUT' IN BACKGROUND UNIT my_unit EXPORTING i_internal_outbound = i_tab_int_data. CATCH cx_bgrfc_invalid_destination cx_bgrfc_invalid_context INTO lx_bgrfc_error. " log the error inside the application log
... ENDTRY.

As in my scenario, i do not need the publishing of the event in EOIO (exactly once in order) but just need it to be EO (exactly once) thus, I am utilising the transactional RFC (tRFC) unit.

In the RFC function module, implement your custom logic. In my case here, I am triggering an ABAP proxy that calls to a SAP PO to publish the message into a JMS topic.

The configurations:

You will require the following authorizations for the setup.

  • For bgRFC configuration, you need authorization object S_BGRFC.
  • For bgRFC Supervisor User, you need authorization object S_RFC.

For the setup:

1. Creating a Supervisor Destination

Supervisor destination is used to get the configuration settings for the bgRFC scheduler and starts or stops the schedulers as required on each application server.

Using the transaction SBGRFCCONF, you can define a supervisor destination.

  1. Choose the Create symbol on the Define Supervisor Dest tab page.
  2. Enter the name of the destination to be created.
  3. Enter the supervisor user name and a password.
  4. Choose Copy.

2. Maintaining Inbound Destinations

As my use case is to enable the asynchronies between the caller and the called application within the same system (same SID and same client). The Inbound destination and queue prefixes help in compartmentalizing different applications and avoid conflict for applications using the same queue name in the same system.

Using the transaction SBGRFCCONF, you can define an inbound destination.

  1. Choose the Create symbol on the Define Inbound Dest tab page.
  2. Enter the name of the inbound destination to be created.
  3. Select a logon/server group
  4. Add a queue prefix.
  5. Choose Save.

3. System, Application and Destination – Specific Settings

Well, referring to the recommendations in SAP 2309399 – How to use SBGRFCCONF effectively?, I have pretty much use the default values for my use case. I would suggest that you do a performance test if you expect huge volume on your end to determine which settings work best for your use case.

How to monitor the bgRFC?

Use the transaction SBGRFCMON to monitor the bgRFC.

For testing purpose, I have inserted a temporary local programmatically after the call so that I will be able to monitor my tRFC unit in the bgRFC monitoring tool. This is required for the initial run or if your inbound destination is empty. You can also opt to lock and unlock the destination inside the bgRFC monitoring tool.

... CALL FUNCTION 'Z_PY_POST_NOTF_OUT' IN BACKGROUND UNIT my_unit EXPORTING i_internal_outbound = i_tab_int_data. " for testing only lock_id = my_unit->delay( 300 ). ...

Summary:

This my first blog post, thus, apologize for any shortcomings or inaccuracy in the terminology that I might have used. I just hope that this blog post will help anyone who faces the same requirements/scenario/use case and would like to reap the benefits mentioned, you may evaluate the option shared in this blog post. And lastly, I welcome your kind feedback.

I am also planning to put up another blog post for another use case of bgRFC on how to prevent the error due to locking issue when receiving by using the queue mechanism of the bgRFC framework. Stay tuned.

How SAP Data Warehouse Cloud strategy aligns with SAP Analytics Cloud

Introduction

This blog post provides an overview about how SAP Data Warehouse Cloud’s strategy aligns with SAP Analytics Cloud’s strategy. In fact, the tight integration of SAP Data Warehouse Cloud and SAP Analytics Cloud unleashes synergies.

short exceprt of SAP Data Warehouse Cloud’s strategy

SAP Data Warehouse Cloud serves as a business data warehouse and can be used for data wrangling, data preparation and data modelling. SAP Data Warehouse Cloud is a complete end-to-end self-service data management solution in the cloud. It serves as a business data warehouse enabling SAP Analytics Cloud to create visualizations and slice-and-dice data cubes. Furthermore, multiple user groups benefit from SAP Data Warehouse Cloud. Users from IT can pre-process & clean data sets using common modelling techniques such as SQL, Cube Builders and even Python to transform unstructured raw data to high quality structured data. Business users can unleash full value through SAP Data Warehouse Cloud’s innovative business layer. It enables them to discover relationships between data elements and enrich data fields with business information. This allows users across business departments to instantly understand data in a self-service fashion. Consequently, SAP Data Warehouse Cloud customers benefit from data democratization – making information accessible and understandable to the average business user and not only to IT professionals.

short exceprt of SAP Analytics Cloud’s strategy

SAP Analytics Cloud’s Augmented BI strategy envisions intelligent algorithms automatically generating insights for end-users. This saves end-users from having to create visualizations and dashboards by hand and automates the creation of meaningful content. Even though SAP Analytics Cloud follows a self-service strategy for dashboarding, visualizations created by end-users usually take into consideration only a small subset of the available data. Users may choose their own filters, their own data dimensions and eventually their own chart types to visualize data.

This leads to users showing a certain extract of data by showing a few selected numbers of dimensions. The end-user is limited to the selected dimensions in his perception. Meanwhile, the explanation of certain values may be hidden due to the reduced scope of dimensions available. As a result, consumers of the visualization may develop biases or derive incorrect conclusions.

In turn, companies develop biased dashboards and hence biased decision making. Additionally, many organizations follow agenda driven BI journeys leading to the implementation of rigid organizational business processes.

SAP Analytics Cloud’s Augmented Analytics strategy challenges end-user bias by enabling exploratory BI journeys. SAP Analytics Cloud includes various smart features enabling end-users to automatically generate dashboards, charts and insights. SAP Analytics Cloud’s smart features allow end-users to break rigid analytics processes through assisted data exploration & visualization. This disrupts the status-quo of rigid organizational processes by providing agile BI journeys and ad-hoc analysis capabilities. Because of this differentiation in the market, SAP Analytics Cloud ranks as a visionary tool in the Gartner Magic Quadrants.

To sum up, SAP Analytics Cloud’s Augmented Analytics strategy resulted in smart features within SAP Analytics Cloud. This effectively creates more value of your data by avoiding end-user bias. Additionally, it enables exploratory BI journeys in an agile manner rather than static agenda-driven BI processes.

Alignment of SAP Data Warehouse Cloud’s and SAP Analytics Cloud’s strategy

SAP Data Warehouse Cloud & SAP Analytics Cloud emphasize their fully-fledged self-service interaction with business end-users. Both tools embody ease of use and user-centricity. SAP Data Warehouse Cloud’s provisioning of a business layer and data democratization is key to Augmented Analytics. Data democratization leads to high quality structured data. Furthermore, data sets used for business users differ from data sets used by purely technical users. Business user focused data sets do not contain technical information and illegible characteristics. Every data cell should be understandable by business users. Consequently, data democratization guarantees high quality data sets with business user focus.

SAP Data Warehouse Cloud’s data democratization capabilities simplify analytics.

In fact, smart BI features benefit from higher quality data sets as results are more tangible and easier to understand. More importantly: insights themselves are of higher quality. The higher the quality of the data, the better the insights generated by smart features are. Augmented Analytics requires clean and especially business-user focused data sets. Otherwise, insights generated by intelligent algorithms happen on a technical level which results in hard to understand insights – this is avoidable by using business user focused data sets provided by SAP Data Warehouse Cloud.

State of the art BI practices often happen in silos. Different departments create their own reports based on their relevant data sources. However, data democratization leads to unified data structures across data sources within the company. This enables analytics to create more value from available data. For instance, it allows analytics to discover correlations or causality across business departments rather than only within one department’s data silo.

Outlook

SAP Data Warehouse Cloud and SAP Analytics Cloud are becoming more and more user centered. End-users utilize self-service abilities daily. In fact, there is a lot of potential for service delivery to get the maximum value for customers. Consultants must proactively emphasize the tools’ work mode. It starts with conveying an agnostic attitude towards data. Beneficially, consultants set an example for customers to live exploratory BI journeys, as agile as reporting requirements change more and more frequently.

Income Tax Declaration Web Dynpro ABAP Configuration Guide

SAP provides the self-service options for Income Tax solutions for India with its Web Dynpro ABAP applications. This blog post mentions the steps which will guide you to configure the same and also mentions the troubleshooting methods for the roadblocks which can be faced during the implementation.

  1. Activate the following services from transaction SICF
    • HRESS_ITDL_EE_IN
    • HRESS_ITDL_AP_IN
    • HRESS_CLMS_AP_EMCR
    • HRESS_A_REP_IN_FORM12BB
  1. Activate the below business functions through transaction SFW5 to enable the WDA SPRO nodes
    • HCM_ESS_WDA_1
    • HCM_ESS_WDA_2
    • HCM_ESS_WDA_3
    • HCM_MSS_WDA_1
    • HCM_MSS_WDA_2
    • HCM_LOC_CI_12
    • HCM_LOC_CI_21
    • HCM_LOC_CI_32
    • HCM_LOC_CI_33
    • HCM_LOC_CI_48
  1. Activate the income tax related info types required using the view V_T77WWW_GATSR

  1. Assign the workflow for IT declaration (India) using view V_T77WWW_GADEF

  1. Activate the workflow WS18900052 and set the task as General Task (Note – Workflow customizing settings in transaction SWU3 should be activated)

  1. Maintain the privilege groups and approver groups and their assignment using the path – SPRO -> Personnel Management -> Employee Self-Service (Web Dynpro ABAP) -> Service-Specific Settings-> Settings for Country-Specific Services -> India -> Benefits and Payment -> Advanced Claims -> Basic Settings

  1. Activate the BAdI for determining approver and approver group

METHOD if_ac_next_approver~get_next_approver.
DATA: ls_p0001 TYPE p0001.
DATA: lt_grp TYPE TABLE OF t77www_clagapa,
ls_grp TYPE t77www_clagapa.
DATA: lv_name TYPE char12.
SELECT * FROM t77www_clagapa
INTO TABLE lt_grp WHERE molga = 40.
SORT lt_grp BY apgrp.
ls_p0001 = ist_p0001.
SELECT SINGLE usrid
FROM pa0105
INTO lv_name
WHERE pernr = ls_p0001-pernr
AND subty = '0001'
AND endda >= sy-datum.
IF ifd_aplvl = 1.
IF ( ist_trnhe-retyp = 'S80C' OR ist_trnhe-retyp = 'SC80'
OR ist_trnhe-retyp = 'HRAC' OR ist_trnhe-retyp = 'IOS'
OR ist_trnhe-retyp = 'PETD' ).
READ TABLE lt_grp INTO ls_grp WITH KEY apgrp = 'APPGRP1'.
IF ls_grp-apuid = lv_name.
READ TABLE lt_grp INTO ls_grp INDEX 2.
efd_apgrp = ls_grp-apgrp .
ELSE.
efd_apgrp = ls_grp-apgrp .
ENDIF.
ENDIF.
IF ( ist_trnhe-retyp = 'S80C' OR ist_trnhe-retyp ='SC80'
OR ist_trnhe-retyp = 'HRAC' OR ist_trnhe-retyp = 'IOS'
OR ist_trnhe-retyp = 'PETD' ).
READ TABLE lt_grp INTO ls_grp WITH KEY apgrp = 'APPGRP2'.
IF ls_grp-apuid = lv_name.
READ TABLE lt_grp INTO ls_grp INDEX 4.
efd_apgrp = ls_grp-apgrp .
ELSE.
efd_apgrp = ls_grp-apgrp .
ENDIF.
ENDIF.
IF ( ist_trnhe-retyp = 'S80C' OR ist_trnhe-retyp ='SC80'
OR ist_trnhe-retyp = 'HRAC' OR ist_trnhe-retyp = 'IOS'
OR ist_trnhe-retyp = 'PETD' ).
READ TABLE lt_grp INTO ls_grp WITH KEY apgrp = 'APPGRP2'.
IF ls_grp-apuid = lv_name.
READ TABLE lt_grp INTO ls_grp INDEX 3.
efd_apgrp = ls_grp-apgrp .
ELSE.
efd_apgrp = ls_grp-apgrp .
ENDIF.
ENDIF.
IF ( ist_trnhe-retyp = 'S80C' OR ist_trnhe-retyp ='SC80'
OR ist_trnhe-retyp = 'HRAC' OR ist_trnhe-retyp = 'IOS'
OR ist_trnhe-retyp = 'PETD' ).
READ TABLE lt_grp INTO ls_grp WITH KEY apgrp = 'APPGRP1'.
IF ls_grp-apuid = lv_name.
READ TABLE lt_grp INTO ls_grp INDEX 1.
efd_apgrp = ls_grp-apgrp .
ELSE.
efd_apgrp = ls_grp-apgrp .
ENDIF.
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDMETHOD.
  1. Maintain the view: V_T7XSSPERSUBTYP with the info types needed to be updated.

40 0585 A1

40 0586 B2

Implement the BAdI “HRXSS_PER_BEGDA” and maintain any date in the previous year as default start date.

Configuration Method:

SPRO -> Personnel Management -> Employee Self-Service (Web Dynpro ABAP) -> Service-Specific Settings -> Personal Information -> Personal Profile -> BAdI: Change Default Start Date

method IF_EX_HRXSS_PER_BEGDA~DEFAULT_DATE.
if INFTY = '0006'.
begda = '20064001'.
endif.
endmethod.
  1. Configure the header level fields and multiple line level fields in the application for each declaration type from the nodes ‘Define Fields and its Attributes at Header Level’ (View – V_T77WWW_GAHLC) and ‘Define Fields and its Attributes at Multiple Line Level’ (View – V_T77WWW_GAMLC).
  1. Editability of proposed and actual values can be controlled through ‘Control Visibility & Editing of Proposed and Actual Value Columns’

Value ‘1’ means Proposed column will be editable and Actual column will be non-editable for the employees.

Value ‘2’ means Proposed column will be non-editable and Actual column will be editable for the employees.

Value ‘3’ means both Proposed column and Actual column will be non-editable for the employees.

  1. For configuring the tax regime option introduced with the Union Budget 2020-21, implement the SAP KBAs 2895046 and 2919107 and also perform the manual instructions attached with these KBAs.
  2. Implement the ‘BAdI: Determine Process Completion Date’ under Income Tax Declaration in Payroll: India in SPRO to change the status of the request from ‘To be Processed’ to ‘Processing Complete’.
  3. Run the applications by executing corresponding application configurations for employee and approver applications

Employee application screen-

Approver application screen-

Additional Information-

  • For configuring any validation checks during the application request, implement the BAdI available in the node ‘BAdI: Validate Request Data’ under Income Tax Declaration in Payroll: India in SPRO.
  • Attachments uploaded through the IT declaration application are stored in cluster tables in SAP as mentioned in the SAP KBA 1685478 and 2682711. In case in the future the database space of the ECC server becomes less, there is a provision of a ‘BAdI: Process Attachments’ (available under Advanced Claims in Payroll: India) so that attachments can be stored in any third-party server.
  • Troubleshooting SAP KBAs:
    • 2312421 – ESS: HINUINFU Error while Infotype/Database Updation. Solution Type:00002 PBAS_SERVICE 9
    • 2729718 – Attachment option not visible in IT Declaration
    • 2312412 – ‘Only one record can exist between Jan. 1800 to Dec. 9999’ error when employee tries to create IT580 from ESS portal
    • 2307748 – ESS: Values updated in Infotypes 585 and 586 not in same order as filled in ESS IT declaration screen
    • 2303705 – Approver is not able to download the attachment in Approver application of IT Declaration (Webdynpro ABAP)
    • 2212336– Maximum limit not coming correctly in ESS IT declaration application with Section 80C details
    • 2021059 – While raising ESS Tax Declaration Application, system throws errror “Mandatory field “Actual Ded-Interest u/s 24″ not filled”

Following the above-mentioned instructions, you would be able to implement Income Tax declaration for India using Web Dynpro ABAP. In case of any improvements or feedbacks, please comment on this blog post, or you may ask questions in the HCM Employee Self-Service Q&A tag area here: https://answers.sap.com/tags/399814863717995876203615023559515. I hope this blog post helps you.

Thanks and Regards

Udit Khera

Part 2: Why a Resilient Business Recovery Begins with an Application Extension

By Anthony Leaper, Senior Vice President, SAP Cloud Platform Extension Suite Go-to-Market Strategy, SAP 

When businesses experience radical shifts in customer demand and expectations, a domino effect of exposed weaknesses and fragilities inevitably arise across all operations and interactions. But I also have seen many companies display incredible resilience by adapting to the current situation faster with greater agility, higher productivity, and stronger customer connections.

According to McKinsey, businesses that stay competitive in a disruptive environment often identify weaknesses and opportunities better than their competitors. This sense of clairvoyance empowers companies to quickly adapt existing processes and create new ones while resolving a long-standing trade-off between flexibility, efficiency, and resilience.

Most organizations find such an achievement easier said than done. They are often missing a flexible foundation that deploys agile processes and extends them quickly across the entire user experience for employees, customers, and partners. But it is possible to change their business resilience game with an application extension by using SAP Cloud Platform Extension Suite, as part of the SAP Business Technology Platform.

What is an application extension?

The concept of application extensions is centred around enabling customers to rapidly adapt and differentiate their business by extending the solutions they already use, building new ones, and scaling them in the same deployment environment. From the deployment environment to the application and consulting services, each element of the extension strategy is acquired to fulfil a determined purpose. And in most cases, the goal is focused on achieving a more-competitive future for the business.

IT organizations often view application extensions as enhancements to solutions that are developed and implemented without impairing existing system functions – or, what we call, “keeping the core clean.” But non-IT business functions take a different view, where extension provide the customizations needed to fulfil their needs for innovation and competitive advantage.

On their own, each solution implemented offers tremendous benefits; however, developers dedicate considerable time and effort to design, train, and retrain algorithms to support accurate decision-making and drive expected outcomes. To minimize wasted time, businesses can integrate an application extension of pretrained conversational AI bots with existing solutions, which sets a rapid, continuous cycle of updating capabilities, creating new ones, and ensuring timely delivery.

How an application extension changes business operations?

The key to a successful application extension is the delivery of innovation that creates competitive differentiation – without disrupting core applications. Using proven methodologies, enterprise-grade tools and services, ready-to-be-used business content, and an accessible deployment environment, companies can quickly implement the application extension and run it seamlessly with existing software.

Take, for example, Delivery Hero. The online food delivery service built a fast-growing operation with the assistance of a cloud platform supporting the creation and deployment of application extensions that protect and improve business performance. In return, the company keeps pace with explosive growth by leveraging standardized technologies and processes to accelerate the fulfilment of consumer requests with high satisfaction and augment the efficiency and flexibility of procurement and finance activities.

Delivery Hero’s experience is one of a portfolio of use cases that application extensions are well-suited to support. I recently discovered three scenarios that are helping SAP customers gain the edge they need to recover from today’s economic volatility.

  1. Simplification of user experiences
  • Application extensions are boosting workforce productivity and engagement by delivering harmonized and contextualized user experiences. They are jumpstarting development efforts with prebuilt components and comprehensive mobile services, supported by low-code and cloud-native development options.
  1. Agile process automation
  • ROI is realized faster by using application extensions to embed digital process automation technologies into existing software. Automating and optimizing processes and tasks help build greater operational resilience and flexibility, adapting and customizing business processes, managing process performance, and identifying improvements with data-based insights.
  1. Digital workplaces
  • By enabling rapid innovation without disruption, application extensions allow organizations to become more agile and resilient to change. Business productivity can be enhanced with intuitive tools, collaborative access to existing expertise, and personalized workplace experiences that connect people, data, and processes.

Where managing change is flexible, prompt, and resilient

Surviving and thriving in a rapidly changing economy calls for a limitless ability to adapt. Through that drive comes the flexibility and agility to mitigate risk, capture new opportunities, and reimagine the way business is done.

Cloud-based application extensions developed through SAP Cloud Platform Extension Suite extend the power of intelligent operations by delivering consistent, personalized, and unified experiences across business processes and interaction channels. In return, businesses can automate, enhance, and adapt processes beyond the capabilities of their standard solutions.

Explore the value that SAP Cloud Platform Extension Suite can bring to your business.

NEW TUTORIAL: Debug Your SAP Conversational AI Chatbot

I’ve been using SAP Conversational AI for a while, and learned as I went along about the Test panel and the Chat Preview (previously known as the Chat With Your Bot panel). While using them I came across the JSON preview, and then the relatively new Debug panel.

But I hadn’t gotten a complete explanation of when to use each, and what each part of these “debugging” tools do.

So, of course, I decided to write a tutorial to let people really learn what they do and what they are for, while playing with them and having a good time. The tutorial is called Debug Your SAP Conversational AI Chatbot.

Among the things it explains:

  • What is the true purpose of the Test Panel?
  • What can learn from the JSON behind a conversation?
  • How does the Debug panel behave during different events in the conversation?
  • How can you find problems in the chatbot from the Debug Panel?

And finally, it explains the inner workings of an SAP Conversational AI chatbot. You know, how skills are selected, like I’ve written in my 2 previous blogs: How the heck does a chatbot work? and How the heck does a chatbot work? Now with disambiguation.

I won’t reprint the graphic — I am tempted, because I like it so much — but here’s the link.


See all SAP Conversational AI tutorials
See all tutorial in the SAP Tutorial Navigator


Follow me: Daniel Wroblewski
Follow all tutorial updates to keep up to date on tutorial news blogs