SAP Community - SAP NetWeaver

saptune 3.1 on the Horizon

2023-09-01T14:33:03+02:00

In a few weeks saptune 3.1 will reach the public repositories of SLES for SAP Applications. Time to talk about the changes and new features.

As always saptune 3.1 will be released for all Service Packs still in support, namely:

SUSE Linux Enterprise Server for SAP Applications 12 SP5

SUSE Linux Enterprise Server for SAP Applications 15 SP1

SUSE Linux Enterprise Server for SAP Applications 15 SP2

SUSE Linux Enterprise Server for SAP Applications 15 SP3

SUSE Linux Enterprise Server for SAP Applications 15 SP4

SUSE Linux Enterprise Server for SAP Applications 15 SP5

Machine-readable Output

This might be the biggest new feature: optional JSON output

With --format json the first set of commands

saptune [daemon|service] status

saptune note list|verify|enabled|applied

saptune solution list|verify|enabled|applied

saptune status

saptune version

will print the output as a JSON string. Further commands will follow.

This does not only paves the way for the upcoming Trento integration, but also simplifies the usage in scripts or configuration management solutions.

Output of: saptune --format json note applied | jq

Do not use --format json blindly! A command that does not support JSON output yet, will fail if called with the option, even if it would work otherwise!

New Commands, Deprecated Commands

As requested by a customer, we added a new command: saptune solution change

With only one solution allowed at a time, switching to another was a two step process. First reverting the current solution and afterwards applying the new one. Now this is possible with a single command.

This is not only more convenient, but also minimizes the time when the system is not tuned, since revert and apply are done internally much faster.

With the change being simply a revert followed by an apply, the order is not preserved in case you have additional Notes applied to a Solution.

Output of: saptune solution change HANA

Refurbished Status Command

The command saptune status got a face-lift and some new additions.

The Solution shows now the list of contained Notes. In all cases Note lists are ordered in the way they are applied.

Newly added are the type of virtualization and, I believe the most welcomed addition, the state of the tuning!
You don't have to run an additional `saptune verify` anymore, to check if the tuning is in order. This is displayed by the status command already.
For those who don't want that, the old behavior can be restored by using --non-compliance-check.

Output of : saptune status

New Solutions and SAP Notes

The MAXDB solution has not been just de-deprecated, we also introduced a new Solution `NETWEAVER+MAXDB` for running both SAP application servers and MAXDB on the same host.

SAP Note "1868829 - Startup Issues Because Number of Active I/O Requests to Queue Exceeds aio-max-nr Limit" is now available and part of the solutions:

- HANA
- NETWEAVER+HANA
- S4HANA-APP+DB
- S4HANA-DBSERVER

Zebras are here!

The tables of saptune verify can become very long. The one for the SAP HANA Solution contain over 50 parameters, depending on the environment. Spotting non-compliant entries can be cumbersome.

With 3.1 you now can either limit the table to non-compliant parameters only:

Output of: saptune note verify --show-non-compliant

or colorize the output:

Output of: saptune note verify --colorscheme full-red-noncmpl

That's where the zebras come into the play. You can choose between different color styles:

cmpl-blue-zebra

full-blue-zebra

full-red-noncmpl

red-noncmpl

cmpl-green-zebra

full-green-zebra

full-yellow-noncmpl

yellow-noncmpl

Play around and choose which zebra you like best!

About sysctl

Since 3.0 saptune reports possible conflicts with sysctl files. One file almost always caused a debate: /boot/sysctl.conf-*. Amongst others it sets the defaults of kernel.shmmax and kernel.shmall for SLES and therefore always got reported by saptune as possible conflict.

The feedback told us, that part of the users liked it, but a slight majority didn't.

With 3.1 saptune will no longer report both files per default. But those of you who still want it, can simply change the variable SKIP_SYSCTL_FILE in /etc/sysconfig/saptune.

Anything Else?

Without being complete, we also have reworked the version definition in the configuration files, which will be interesting for those who use custom Notes and Solutions. We went from the (still supported, but deprecated) comment format to a more clear section format:



[version]

VERSION=28

DATE=29.07.2021

DESCRIPTION=VMware vSphere configuration guidelines

REFERENCES=https://launchpad.support.sap.com/#/notes/2161991

Also it is now possible to use inline comments throughout the Note and Solution files and finally we deprecated the custom Note format from saptune v1, which should not be around anymore.

I think, that covers most of the changes.

Enjoy!

SAP Security Patch Day – September 2023

2023-09-12T10:14:29+02:00

SAP Security Patch Day – September 2023

On September 12, 2023, SAP has once again released a crucial set of security patches to address a myriad of vulnerabilities across its product line. This month's SAP Security Patch Day primarily focuses on rectifying Program errors. Below is a comprehensive rundown of the security notes, sorted by their Common Vulnerability Scoring System (CVSS) scores:

HotNews

BI-BIP-CMC [CVE-2023-25616]: Code Injection vulnerability in SAP Business Objects Business Intelligence Platform (CMC) with a CVSS score of 9.9. First released on 14.03.2023, updated on 12.09.2023.

BI-BIP-LCM [CVE-2023-40622]: Information Disclosure vulnerability in SAP BusinessObjects Business Intelligence Platform (Promotion Management) with a CVSS score of 9.9. Released on 12.09.2023.

BC-IAM-SSO-CCL [CVE-2023-40309]: Missing Authorization check in SAP CommonCryptoLib with a CVSS score of 9.8. Released on 12.09.2023.

BC-FES-BUS-DSK [CVE-2023-40624]: Security updates for the browser control Google Chromium delivered with SAP Business Client with a CVSS score of 10.0. First released on 10.04.2018, updated on 12.09.2023.

BC-XI-CON-UDS [CVE-2022-41272]: Improper access control in SAP NetWeaver AS Java (User Defined Search) with a CVSS score of 9.9. First released on 13.12.2022, updated on 12.09.2023.

High Priority

BI-RA-WBI-FE [CVE-2023-42472]: Insufficient File type validation in SAP BusinessObjects Business Intelligence Platform (Web Intelligence HTML interface) with a CVSS score of 8.7. Released on 12.09.2023.

BC-CCM-HAG [CVE-2023-40308]: Memory Corruption vulnerability in SAP CommonCryptoLib with a CVSS score of 7.5. Released on 12.09.2023.

Medium Priority

BC-SYB-PD [CVE-2023-40621]: Code Injection vulnerability in SAP PowerDesigner Client with a CVSS score of 6.3. Released on 12.09.2023.

MM-FIO-PUR-SQ-CON [CVE-2023-40625]: Missing Authorization check in Manage Purchase Contracts App with a CVSS score of 5.4. Released on 12.09.2023.

BC-GP [CVE-2023-41367]: Missing Authentication check in SAP NetWeaver (Guided Procedures) with a CVSS score of 5.3. Released on 12.09.2023.

BI-BIP-LCM [CVE-2023-37489]: Information Disclosure vulnerability in SAP BusinessObjects Business Intelligence Platform (Version Management System) with a CVSS score of 5.3. Released on 12.09.2023.

FS-QUO [CVE-2023-40308]: Denial of service (DOS) vulnerability due to the usage of vulnerable version of Commons FileUpload in SAP Quotation Management Insurance (FS-QUO) with a CVSS score of 5.7. Released on 12.09.2023.

BC-WD-UR [CVE-2023-40624]: Code Injection vulnerability in SAP NetWeaver AS ABAP (applications based on Unified Rendering) with a CVSS score of 5.5. Released on 12.09.2023.

BI-BIP-INS [CVE-2023-40623]: Arbitrary File Delete via Directory Junction in SAP BusinessObjects Suite(installer) with a CVSS score of 6.2. Released on 12.09.2023.

Low Priority

FI-FIO-AP-CHK [CVE-2023-41368]: Insecure Direct Object Reference (IDOR) vulnerability in SAP S/4HANA (Manage checkbook apps) with a CVSS score of 2.7. Released on 12.09.2023.

FI-FIO-AP [CVE-2023-41369]: External Entity Loop vulnerability in SAP S/4HANA (Create Single Payment application) with a CVSS score of 3.5. Released on 12.09.2023.

Statistics:

Total new SAP notes: 16

Total vulnerabilities addressed: 16

Highest CVSS Score: 10.0 (HotNews) – Security updates for the browser control Google Chromium delivered with SAP Business Client – [CVE-2023-40624]

Description: This HotNews-rated note addresses security updates for the browser control Google Chromium delivered with SAP Business Client, with a critical CVSS score of 10.0.

Top 2 Critical Bugs:

BI-BIP-CMC [CVE-2023-25616]
- CVSS Score: 9.9 (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H)
- Description: This high-priority note resolves a Code Injection vulnerability in SAP Business Objects Business Intelligence Platform (CMC) with a CVSS score of 9.9. As this vulnerability allows attackers to compromise system integrity and confidentiality, prompt action is advised to mitigate potential risks.

BC-XI-CON-UDS [CVE-2022-41272]
- CVSS Score: 9.9 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L)
- Description: This high-priority note addresses an Improper access control in SAP NetWeaver AS Java (User Defined Search) with a CVSS score of 9.9. As this vulnerability allows unauthorized access, immediate patching is essential to protect the application and its users.

saptune 3.1 is out

2023-10-02T13:03:03+02:00

Last week saptune 3.1 was made available in all official repositories for:

SUSE Linux Enterprise Server for SAP Applications 12 SP5
(saptune-3.1.0-4.15.1)

SUSE Linux Enterprise Server for SAP Applications 15 SP1
(saptune-3.1.0-150100.8.27.1)

SUSE Linux Enterprise Server for SAP Applications 15 SP2
(saptune-3.1.0-150100.8.27.1)

SUSE Linux Enterprise Server for SAP Applications 15 SP3
(saptune-3.1.0-150100.8.27.1)

SUSE Linux Enterprise Server for SAP Applications 15 SP4
(saptune-3.1.0-150100.8.27.1)

SUSE Linux Enterprise Server for SAP Applications 15 SP5
(saptune-3.1.0-150100.8.27.1)

To see, what is new and what has changed, please read my announcement blog post.

As always, after a release is before a release. If you have wishes for the next version, let us know!

Have a lot of fun!

Single Sign On - SAML Configuration for Fiori Application using Azure Enterprise

2023-10-11T07:47:45+02:00

Step-by-step configuration instructions of single sign on for SAP Fiori application with Azure AD

Pre-requisite:

SSL need to be configured first before configuring for SAML2 authentication.

Configuration Steps:

Activating the Services

1. Goto Transaction SICF, enable below services

/sap/bc/saml2/cdc_ext_service

   /sap/bc/webdynpro/sap/saml2

   /sap/public/bc/icf/logoff

   /sap/public/bc/sec/saml2

   /sap/public/myssocntl

2. On the Maintain Services page, enter one of the service name from the list.

3. Right-click the service in the tree menu view, select Activate Service.

4. Prompt to activate the service, click Yes with tree option.

Enable SAML2 Local Provider Setting

1. Run the transaction SAML2 or open the URL

https://<FQDN>:<ICM_HTTPS_PORT>/sap/bc/webdynpro/sap/saml2?sap-client=100&sap-language=EN

Note : If you want to use webdispatcher then open the SAML2 URL through webdispatcher Url

https://<WEBDISPATCHER_FQDN>:<WEBDISPATCHER_ICM_HTTPS_PORT>/sap/bc/webdynpro/sap/saml2?sap-client=100&sap-language=EN

2. Click on Enable SAML2.0 Support and Select "Create SAML 2.0 Local provider".

3. Enter the Provider Name https://<SID>CLNT<CLIENT_NO>; on Initial setting screen. Click Next.

4. Choose Automatic in Selection Mode on Service Provider Settings and Select Finish.

5. After Click on Finish, it will be redirect you to Configuration Page.

6. Click on Metadata button to get pop-up for the metadata download, then select Download Metadata.Make sure browser pop-up is allowed.

7. Now the RPT can be performed at Azure Enterprise Application, by either directly uploading the metadata.xml file or providing the details manually in enterprise application of fiori.

8. You can provide the identifier same as it has been created in step 3 in transaction SAML2

9. Provide the fiori sign-on url in the configuration and Click on save.

8. Configure the following user attributes & claims for application. To manage these attribute values, select Edit and set the Name identifier as Unspecified & source attribute as user.onpremisesamaccountname.

9. Now the signed certificate and federation can be downloaded from the section SAML Certificates

10. As a next step, open the SAML2 and click on Trusted Providers tab.

11. Select the the Upload Metadata File.

12. Upload the federation metadata xml which was downloaded in step 9

13. In the Next Step Metadata Verification, Upload the federation certificate downloaded in Step 9 and Click Next

14. In Signature and Encryption Step Choose the Digest Algorithm

15. In Authentication Requirements, Choose the shown and Click Finish.

16. First Click on Edit and then Add then select the Unspecified and then Save the setting as shown.

17. Then Click on Enable to activate the configuration.

18. Goto Transaction SICF , enter the service name or external alias example /sap/bc/ui2/flp and open the service

19. Select Logon Data Tab. Choose the Alternative Logon Procedure and set SAML Logon at 1 and Save.

20 . Test the Service by openeinf the fiori URL in the browser.

Supercharge SAP workload on IBM Cloud with PowerVS

2023-10-11T18:46:41+02:00

Few month ago, I released a blog about running SAP workload on VMware in IBM Cloud as a unique offer, well today I will talk about another major offer which is the IBM Power Virtual Server as an IaaS (Infrastructure-as-a-Service) offering.

Known as least hidden secret, running IBM Power system for SAP workload is the ideal platform due to their robustness, scalability, and ability to handle high workloads. IBM Power Server is specifically designed for high-performance computing, data-intensive workloads, and mission-critical applications.

Overall, as a powerful virtualization solution, IBM PowerVS can help businesses to run their SAP workloads more efficiently, securely, and cost-effectively.

In this article, I will provide detail around the PowerVS offer on IBM Cloud, design & architecture for SAP workload.

Best practice: Before to start anything make sure to read all necessary note relevant to your deployment, read the product guide for each component that you intend to deploy and make sure that you have done the sizing exercise properly.

Be careful on restriction and what is supported or not, this will avoid unnecessary hiccup.

Again, and always, before to start any action and to guaranty the success of the exercise, it is important to do some reading on our subject. Here is a collection of guides, references and SAP Notes to be reviewed.
These references differ from the previous article, so take the time to review it

SAP Notes

2855850 - SAP Applications on IBM Power Virtual Servers
2947579 - SAP HANA on IBM Power Virtual Servers
2923984 - SAP on IBM Power Virtual Servers: Support prerequisites
2414820 - SAP on IBM Cloud: Support prerequisites
2932766 - SAP on IBM Power Virtual Servers: Key Monitoring Metrics

Guides

IBM Product Guide Power System Virtual Servers

Knowledge Base

Run Critical SAP Hana workload using RHEL in Power Virtual Server
SAP Fast Path of IBM Power Virtual Servers
IBM Storage FlashSystem
Shared Processor Performance Compare to Dedicated Processors

SAP workload on IBM PowerVS, what does it mean for customers?

Running IBM PowerVS for customers as mentioned in my first paragraph bring significant value for all reasons highlighted, existing customers familiarized with IBM Power on-premise already know how powerful and robust this infrastructure is, but for new customers it’s like traveling on a first-class Rocketship.

Remember the PowerVS is an IaaS offering, so in a context of hybrid architecture, customers can extend their existing on-premise or private DC SAP workload to the cloud without changing anything in terms of tools or operations, which save time and money.

Beyond the fact that customers run their operation as usual, they also can consume and integrate native cloud services with PowerVS.

Let’s get started

Hold on !!! not yet 😉 … before to put your system on a different solar system you must be informed of few things to clear out nuances with the classic approach of native cloud virtual machine like VPC.

PowerVS Responsibility Assignment Matrix
The first point is the RACI, once your PowerVS is provisioned you must manage the OS, software and data.

PowerVS Matrix

The second thing is the “PowerVS Workspace“, this is the first thing that you need to understand. Consider the Power Systems Virtual Server workspace as a centralized hub that encompasses all Power Systems Virtual Server instances within a designated geographic region

PowerVS Workspace

You can access the Power Systems Virtual Server workspace from the Resource list within the user interface. This workspace has the capacity to accommodate numerous Power Systems Virtual Server instances simultaneously.

Cloud Workspace

Ok now that you understand this 2 (two) aspect, let’s review the core of this unique infrastructure that makes SAP so special to run on.

Design for the best and even better

IBM PowerVS architecture is purposely built to support heavy SAP workload which requires tremendous performance, scalability and uptime.
The core components below that I will walk you through are designed specially to meet these expectations.

IBM Power Server

Let’s get started with the servers, to operate SAP workload on PowerVS in IBM Cloud two server type will be available

Power Server Option

IBM Power E980

To run SAP Hana, only this server will be supported operating SLES or RHEL. It brings massive throughput, performance and scalability in a modular high-end system with up to 192 POWER9 cores processor. It can go up to 64TB memory and is the fastest POWER9 processors in the Power Systems portfolio.

IBM Power S922

On the other side, this server can be used to run SAP NetWeaver and SAP AnyDB workloads on AIX or Linux operating system. At the glance the IBM Power Systems S922 is a mid-range server featuring the POWER9 core processor also, featuring a flexible core configuration ranging from 4 to 20 cores, making it a robust solution for resource-intensive applications and enterprise workloads.

IBM Processor

Let’s continue with the processor, of course, IBM Power will not be named as such without running Power processor 😊. IBM Power processor permit to run with dedicated and shared configurations, the great thing with IBM PowerVS instance is the ability to resize virtual servers dynamically !!! feature that is fully supported by SAP NetWeaver.

Power Processor

IBM Storage

The other major point in terms of hardware is the storage, both servers are attached with Block Storage powered by IBM Storage FlashSystem families such 5200/7300/9500. They are connected through fiber channel protocols and provide performance, cyber resiliency, scalability and power efficiency.

IBM Storage FlashSystem

Within IBM Power Systems Infrastructure, there are two types of storage available:
Block Storage Tier 1 for mission critical application, e.g. NVMe flash storage. For SAP HANA workloads, Tier 1 of block storage is supported only.
Block Storage Tier 3 default storage type with optimized price/performance, e.g. SSD flash storage.

IBM PowerVS design for SAP

Now that we see what it consists of from a pure hardware, let’s dive on the specifics to understand how to articulate your choice around the virtual server instance.

Few lines above it talked about the Power Server E980 and S922 usage for SAP Hana or SAP Netweaver with AnyDB, well to make things simple here is a matrix of usage between server, processor core type, and SAP usage.

Matrix of usage

I’m sure that some of you are wondering what the meaning of the profile or core type is … Let me give you more explanation around this.

Profiles

Let me start with SAP Hana, when you create your instance from the PowerVS portal, you need to start by selecting the OS and the image associated.

Operating system

You will have the option to check the box “Use a custom SAP (Hana) profile” or leave it empty, if you leave the default box unchecked the instance profiles to be used will be based on predefine configuration regarding to fix core/memory ratio for production usage

Default Profile

Note the because of SAP Hana OS usage, E980 server and dedicated core type is selected and can’t be changed, you will find the list of profile available for SAP Hana on the link below.
SAP Hana PowerVS Profile Offering

Now, what if you select the check box for the boot image?

Custom profile

For a non-production system, it is acceptable to run custom profile which will allow you to customize the number to core and memory to your server instance. You will notice that E980 server and dedicated core types are selected and can’t be changed also.

Core / Memory Ratio

Ok now that we understand the SAP Hana matrix let’s talk about Netweaver and AnyDB. As previously mentioned you will need to select your OS combination and image, but unlike SAP Hana the choice of OS has much broader options.

Netweaver and AnyDB OS option

However, here there is no specific instance profile to select. The same rule as custom profile will apply but with a choice given for the machine and core type.

Netweaver and AnyDB - Core / Memory Ratio

Core Types

When you run SAP workload on PowerVS obviously you need to be very precise to get maximum benefit from the environment, here the core type allows you to operate the core processor Dedicated or Shared (capped/uncapped).

Core types selection

What does it mean? First, there is a correlation between the processor core type and the OS chosen. Indeed, if you want to run SAP Hana, as mentioned previously you will select Linux for SAP (Hana) and de facto because of that the core type processor will be dedicated so as the machine type (E980).

SAP Hana dedicated core

If you chose any other OS, then you will have the ability to go with dedicated or shared, ok I see you with “ok, so what ? and ?” … I got you, in other words:

Dedicated

With dedicated core type, you have the SAPS value per cores guaranteed based on the system type (E980/S922) with resources allocated specifically for you.

Shared (Uncapped)

With shared core type the same rule will apply, however you will share the resource with others 😊 Note that If you are using shared processor configurations for SAP NetWeaver, it is recommended using uncapped mode.

What about integration with cloud service and native components?

Running SAP in IBM cloud native VMs (VPC) is nice because you can consume and integrate cloud native service and components easily.
Running SAP on IBM PowerVS is awesome for many reasons and I already talked about it above, so for customers who want to leverage this unique offer here is a classic simplified architecture view.

PowerVS Integration

One of the main elements in this picture for the integration with IBM Cloud native service or components is the transit gateway. This specific network component is commonly used in hybrid scenario to interconnect multiple layers in IBM Cloud, here the TG will provide connectivity between IBM PowerVS and the VPC layer to interact with native VM.
On top of it because of the interaction with the VPC layer, the Cloud Service can be consumed from Virtual Private Endpoint for VPC.

Conclusion

Running SAP on IBM PowerVS as mentioned previously has many advantages, to me one of the major benefits is also the fact that customer who runs on-premise Power, can make the move PowerVS seamlessly, and leverage the full power of the technology.
Moreover, that customers can push to more innovations and transformations by integrating IBM cloud extended native features and specific platform offers for SAP like VPC and more.

In my IBM Cloud PowerVS blog, I will talk how PowerVS help to increase ROI for SAP workload, followed by detail technical migration and automation.

SAP NetWeaver 7.5メンテナンス方針のSAP Business Suite 7への同期と SAP BW/4HANAの製品戦略のSAP S/4HANAへの同期について

2023-10-13T09:37:24+02:00

＊このブログは、2020年4月15日にSAPジャパンブログに投稿したものです。弊社プラットフォーム変更により、内容をSAP Community Blogに再投稿しております。

SAPは2020年2月にSAP S/4HANAとSAP Business Suite 7のメンテナンス方針の更新の発表を行いました。それに引続きSAPでは下記関連製品のメンテナンス・製品方針についても2020年4月付けで更新を行いました。

1）SAP S/4HANAへの安全な移行のためSAP NetWeaver 7.5のメンテナンス方針のSAP Business Suite 7への同期化　　⇒　SAP NetWeaver 7.5はメインストリームメンテナンスを2027年末まで、延長保守を2030年末までとします

2）SAP BW/4HANAの製品拡張方針をSAP S/4HANAシリーズに同期させます

詳細にはSAP Platform開発部門のKarl Kesslerによるブログとそのブログで示されている各リンクをご覧いただきたいと思います。ここでは日本のお客様向けに、我々の言葉にて解説・紹介させていただきます。

SAP NetWeaver 使用パターン別メンテナンス方針解説

図1：SAP ERP 6.0の同一システム・インスタンスに埋め込まれたSAP NetWeaverのサポート

SAP NetWeaver ASが代表的です。これは2020年2月のアナウンス時と変更なくSAP Note1648480に記述されている通りになります。SAP NetWeaver 7.03, 7.31（以上SAP ERP 6.0 EhP6のベース）、SAP NetWeaver 7.4 （SAP ERP 6.0 EhP7のベース）、SAP NetWeaver 7.5（SAP ERP 6.0 EhP8のベース）のSAP NetWeaver ABAP StackはSAP ERP 6.0などのSAP Business Suite 7のメンテナンス方針と同期を取ります。つまり2027年末までのメインストリームメンテナンス、その後2030年までのOptionとしての延長保守です。

図2：BW,　EP（Enterprise Portal）, PI / PO(Process Integration / Process Orchestration)など、単独システム・インスタンスとしてSAP NetWeaverを使う場合

SAP NetWeaver 7.5のメインストリームメンテナンスは従来2024年末でしたが、これが完全にSAP Business Suite 7（SAP ERP 6.0 EhP6~8）と同様になって2027年末となりました。またオプションとしての2030年までの延長保守も提供されます。これは、SAP ERP 6.0などと同期を合わせて、次世代プラットフォームへの移行ロードマップ策定をいただく時間を十分に取って頂くためでもあります。

ちなみにSAP NetWeaver 7.5のJava StackはJava8がベース、SAP NetWeaver 7.4のJava StackはJava6がベースです。単独システム・インスタンスで使うSAP NetWeaver 7.4とそれ以前については、メインストリームメンテナンス期間の変更はありません。

次世代プラットフォームへの移行について

進化の早いインフラ、DB、UX、UI、セキュリティ技術、機械学習の組込など特にIT基盤系では、一般的に最新の技術の恩恵を得て、ITに関わる自社従業員のより付加価値分野へのリソース配分を図るために、ますますクラウドサービスの活用が浸透してきていると思います。SAPでもSAP Datasphereなどにて次世代のIT基盤の提供は既に早くから始まっています。

BI(Business Intelligence)・Business Warehouse(BW)の分野では、SAP Analytics Cloud, SAP BW/4HANA, SAP S/4HANAデータのリアルタイム分析を可能にするCDS Viewや、SAP Fioriの技術も相当浸透してきました。

また、現在のSAP NetWeaver Application Serverに当たるコンポーネントは、オンプレミス・Cloud両方のSAP S/4HANAなどの組込部品ABAP Platformとして今後も進化を続けます。

このように、Cloud化などを切欠に技術革新の速度が速い従来のSAP NetWeaverの領域では、利用シナリオ、目指すプラットフォームにより選択肢も増えより間違いの無い選択・設計が求められていると思います。SAP NetWeaver 7.5のメンテナンス方針修正により、SAP ERP 6.0などと同期を合わせて、あるべき次世代プラットフォームへの移行ロードマップ策定をいただく時間を十分に取って頂くことができればと思います。推奨移行情報については前出のSAP Platform開発部門のKarl Kesslerによるブログ　にもございますので是非ご覧ください。

SAP Note,Captured in which TR Request in SAP using TCODE SE03

2023-10-23T18:33:23+02:00

Hi All,

Hope Every one is well! 🙂

Introduction:

SAP Notes is a set of instructions to remove known errors from the SAP systems. Using the Note Assistant tool, SAP Notes can be applied to the system. You can access the Note Assistant tool using transaction SNOTE.

As we all know, how to implement a note in an SAP system After implementation of OSS Notes, from which Transport the note has been captured and how to identify it I will explain the below steps further.

Step 1.

I implemented an OSS Note a Few Days ago and have to know from which Transport it has been captured.

Step 2:

Go to SE03,click on Find objects in Request/Tasks.

Step 2:Click on Find Objects in Request/Task it will navigate into the below screen.

Step 3:After provided the details as per above and execute it.

After providing the details as per the above and pressing execute, we will navigate to the next screen, where we can observe from which transport the note has been captured.

Conclusion:

I hope this blog will help you find the released Oss Notes and from which transport they have been captured, which we can identify as per the above steps.

Ready for LaMa 3.0 SP29?

2023-11-07T04:19:28+01:00

This year we’re a little bit earlier than the years before – so let me introduce you to our latest Support Package 29 of SAP Landscape Management 3.0.

As usual in my feature blog posts, I would like to highlight 3 new capabilities that were released with this feature support pack. All other innovations and improvements can be found in the “What’s New” section on our SAP Help Portal for SAP Landscape Management.

Let me start with the SAP Kernel Update. We continue our end-2-end story for this topic. Now you’re able to restore a backup of a previous release version in case you need to do so (e.g. if the recent update of the SAP Kernel fails). This was requested by several customers and now we’re proud to make this available to you.

Another new topic is the SPAM/SAINT Update that can now directly be executed via LaMa. We also made this available via REST API in case you need to perform it remotely.

Additionally, we optimized the Database Refresh Operations. Let me highlight the following:

We removed the “User” step where not needed

For SNC enabled systems we added more steps to the refresh procedure

It is also possible now to skip the SWPM step if required

You can pre-import system users into the target system

I hope this little intro to SP29 encourages you to update your LaMa installation.

BTW: If you’re attending ASUG Tech Connect 2023 in New Orleans, LA (Nov 7-9, 2023) and want to hear more about the latest and the future of LaMa as well as are interested to have a meeting with the team => just reach out to my colleague naeem.maqsud#about for more details).

Further information

What’s New in 3.0 SP29 Enterprise Edition
SAP Note 3316859 - SAP Landscape Management 3.0 SP29

Calling custom ABAP function modules with custom startrfc C/C++ file

2023-11-17T23:27:59+01:00

Recently we had a requirement to call a custom function module in SAP ECC system from a 3rd party non SAP application using SAP NW RFC SDK. Earlier it was pretty much simple process to call any function module in SAP via the startrfc kernel executable i.e. you can start any SAP function module, that is RFC-enabled. This program is part of SAP application server and of any SAP RFC SDK.

startrfc worked as follows:

startrfc -3 -h <host> -s <instance number> -c <client> -l <language> -u <user> -p <password> -F <function module> -E <parameter=value>

RFC Clients calling Server FM

However in the last few years whenever you tried to call the startrfc to start a function module in backend system, you faced error like "Missing or invalid -F option" and the function module could not be started. This is due to new SAP Security limitations that now only allowed EDI_DATA_INCOMING and EDI_STATUS_INCOMING to be started by default. More information in the SAP Note 2010749 - Startrfc -F option restriction in NW RFC SDK

Our requirement was such that we had to call the custom FM so we decided on create a custom version of SAP Kernel file STARTRFC so that the original SAP Kernel file is not broken along with calls to standard SAP EDI FM EDI_DATA_INCOMING & EDI_STATUS_INCOMING. The standard STARTRFC program is designed to handle input parameter PATHNAME & PORT where as the custom FM was designed to accept 3 other parameters (routename, filename, uniqueid) so a copy of the STARTRFC C++ program was modified and recompiled and was placed into the kernel directory with name ZSTASRTRFC.

One challenge which arises from following this approach is that we need to ensure that in future when upgrades (Kernel upgrade, EHP upgrades, S/4 Migration etc.) happens, this custom Z file should not be deleted. Additionally customizing the original STARTRFC program itself was more complicated, error prone plus with every update (Kernel upgrade etc.), this file would be overwritten. So this approach was not taken.

Scenario:

Our custom Function module Z_*_UTILITY accepted 3 import parameters - IP_ROUTENAME, IP_FILENAME & IP_UNIQUEID. This FM was remote enabled

Custom FM

Modification of the startrfc C++ Program

The standard startrfc c++ program was modified where the import parameters' were added in place of the standard parameters. In addition to this the custom FM module (Z_*_UTILITY) was added to the program. One thing we noted is that the sequence of adding the import parameters in the c++ file should match the import parameter sequence in the function module.

#include "zstartrfc.h"



int mainU (int argc, SAP_UC ** argv)

{

    OPTIONS options = {};

    if(!parseCommand(argc, argv, &options))

        return 0;

    if(!checkOptions(&options))

    {

        showHelp();

        return 1;

    }

    options->path = "/sapmnt/<SID>/exe/uc/linuxx86_64";

    RFC_RC SAP_API RfcSetIniPath(options->path,errorInfo);

    RFC_RC rc = startRfc(&options);

    return rc;

}



bool parseCommand(int argc, SAP_UC ** argv, OPTIONS* options)

{

    if( argc < 2 || !strcmpU(argv[1], cU("-help")) || !strcmpU(argv[1], cU("-?")))

    {

        showHelp();

        return false;

    }

    else if(!strcmpU(argv[1], cU("-v")))

    {

        showVersion();

        return false;

    }

    int i = 1;

    const SAP_UC * const IP_FILENAME = cU("IP_FILENAME=");

    const SAP_UC * const IP_ROUTENAME = cU("IP_ROUTENAME=");

    const SAP_UC * const IP_UNIQUEID = cU("IP_UNIQUEID=");

    const size_t   FILENAME_LEN = 12;

    const size_t   ROUTENAME_LEN = 13;

    const size_t   UNIQUEID_LEN = 12;



    while(i < argc)

    {

        const SAP_UC ch1 = argv[i][0];

        const SAP_UC ch2 = argv[i++][1];

        if(ch1 == cU('-') && ch2) // we found an option

        {

            if(ch2 == cU('i'))

            {

                options->showSysInfo = true;

                continue;

            }

            if(i > argc - 1 || argv[i][0] == cU('-'))

            {

                continue;

            }

            switch (ch2)

            {

            case cU('h'):

                options->ashost = argv[i++];

                break;

            case cU('s'):

                options->sysnr = argv[i++];

                break;

            case cU('u'):

                options->user = argv[i++];

                break;

            case cU('p'):

                options->passwd = argv[i++];

                break;

            case cU('c'):

                options->client = argv[i++];

                break;

            case cU('l'):

                options->language = argv[i++];

                break;

            case cU('D'):

                options->dest = argv[i++];

                break;

            case cU('F'):

                options->function = argv[i++];

                break;

            case cU('E'):

                {

                    const SAP_UC *param = argv[i++];

                    if(!strncmpU(param, IP_FILENAME, FILENAME_LEN))

                    {

                        options->filename = param + FILENAME_LEN;

                    }

                    else if(!strncmpU(param, IP_ROUTENAME, ROUTENAME_LEN))

                    {

                        options->routename = param + ROUTENAME_LEN;

                    }

                    else if(!strncmpU(param, IP_UNIQUEID, UNIQUEID_LEN))

                    {

                        options->uniqueid = param + UNIQUEID_LEN;

                    }

                }

                break;

			case cU('t'):

                options->trace = argv[i++];

                break;

            default:

                i++;

                break;

            }

        }

    }

    return true;

}



bool checkOptions(OPTIONS *options)

{

    SAP_UC ch = cU('\0');

    const SAP_UC * const EDI_DATA_INCOMING = cU("EDI_DATA_INCOMING");

    const SAP_UC * const Z_*_UTILITY = cU("Z_*_UTILITY");

    const SAP_UC * const EDI_STATUS_INCOMING = cU("EDI_STATUS_INCOMING");

    const unsigned MAX_FILENAME_LEN = 255;

    const unsigned MAX_ROUTENAME_LEN = 50;

    const unsigned MAX_UNIQUEID_LEN = 50;



    if(!options->dest)

    {

        if(!options->ashost )

            ch = cU('h');

        else if(!options->sysnr)

            ch = cU('s');

        else if(!options->user)

            ch = cU('u');

        else if(!options->passwd)

            ch = cU('p');

        else if(!options->client)

            ch = cU('c');

        if(ch)

        {

            printfU(cU("Missing or invalid -%c option.\n"), ch);

            return false;

        }

    }

    if(!options->showSysInfo)

    {

        if((!options->function) ||

            (strcmpU(options->function,EDI_DATA_INCOMING) && 

            strcmpU(options->function,EDI_STATUS_INCOMING) &&

            strcmpU(options->function,Z_*_UTILITY)))

        {

            printfU(cU("Missing or invalid -F option.\n"));

            return false;

        }



        if(!options->filename || !options->filename[0])

        {

            printfU(cU("Missing or invalid -E IP_FILENAME=  option.\n"));

            return false;

        }

        else if(strlenU(options->filename) > MAX_FILENAME_LEN)

        {

            printfU(cU("Filename specified by -E IP_FILENAME= excceeds the maximum length of 255. \n"));

            return false;

        }

        if(!options->routename ||!options->routename[0] )

        {

            printfU(cU("Missing or invalid -E IP_ROUTENAME=  option.\n"));

            return false;

        }

        else if(strlenU(options->routename) > MAX_ROUTENAME_LEN)

        {

            printfU(cU("Route name specified by -E IP_ROUTENAME= excceeds the maximum length of 50. \n"));

            return false;

        }

	if(!options->uniqueid ||!options->uniqueid[0] )

        {

            printfU(cU("Missing or invalid -E IP_UNIQUEID=  option.\n"));

            return false;

        }

        else if(strlenU(options->uniqueid) > MAX_UNIQUEID_LEN)

        {

            printfU(cU("UNIQUEID name specified by -E IP_UNIQUEID= excceeds the maximum length of 50. \n"));

            return false;

        }

   }

   return true;

}



RFC_RC startRfc(OPTIONS *options)

{

    RFC_RC rc = RFC_OK;

    RFC_ERROR_INFO error;

    memsetR(&error, 0, sizeofR(RFC_ERROR_INFO));

    RFC_CONNECTION_PARAMETER connParams[] = {

                                {cU("ashost"), options->ashost},

                                {cU("sysnr"), options->sysnr},

                                {cU("client"), options->client},

                                {cU("lang"), options->language ? options->language : cU("E")},

                                {cU("user"), options->user},

                                {cU("passwd"), options->passwd},

                                {cU("dest"), options->dest ? options->dest : cU("")},

								{cU("trace"), options->trace}};

    RFC_CONNECTION_HANDLE connHandle = RfcOpenConnection(connParams, 

                                        sizeofR(connParams) / sizeofR(RFC_CONNECTION_PARAMETER),

                                        &error);

    if(connHandle)

    {

        if(options->showSysInfo)

        {

            RFC_ATTRIBUTES attr;

            rc = RfcGetConnectionAttributes(connHandle, &attr, &error);

            showConnAttr(&attr);



        }

        else if(options->function)

        {

            RFC_FUNCTION_DESC_HANDLE funcDesc = getFunctionHandle(options->function);

      	    RFC_FUNCTION_HANDLE funcHandle = RfcCreateFunction(funcDesc, 0);



            RfcSetChars(funcHandle, cU("IP_ROUTENAME"), options->routename, (unsigned)strlenU(options->routename), 0);

            RfcSetChars(funcHandle, cU("IP_FILENAME"), options->filename, (unsigned)strlenU(options->filename), 0);

            RfcSetChars(funcHandle, cU("IP_UNIQUEID"), options->uniqueid, (unsigned)strlenU(options->uniqueid), 0);

            rc = RfcInvoke(connHandle, funcHandle, &error);

        }

        if(RFC_OK == rc)

        {

            RfcCloseConnection(connHandle, &error);

            return rc;

        }

    }

    printfU(cU("Error: %s\n"), error.message);

    return error.code;

}



RFC_FUNCTION_DESC_HANDLE getFunctionHandle(const SAP_UC* functionName)

{

    RFC_PARAMETER_DESC parDescRoutename = { iU("IP_ROUTENAME"),     RFCTYPE_CHAR, RFC_IMPORT,   50,   100,   0, 0, 0, 0, 0};

    RFC_PARAMETER_DESC parDescFilename  = { iU("IP_FILENAME"), RFCTYPE_CHAR, RFC_IMPORT,   255,  510,   0, 0, 0, 0, 0};

    RFC_PARAMETER_DESC parDescUniqueid  = { iU("IP_UNIQUEID"),     RFCTYPE_CHAR, RFC_IMPORT,   50,   100,   0, 0, 0, 0, 0};

    RFC_FUNCTION_DESC_HANDLE funcDesc = RfcCreateFunctionDesc(functionName, 0);

    RfcAddParameter(funcDesc, &parDescRoutename, 0);

    RfcAddParameter(funcDesc, &parDescFilename, 0);

    RfcAddParameter(funcDesc, &parDescUniqueid, 0);

    return funcDesc;

}





void showHelp( )

{

    const SAP_UC * const programName = cU("startrfc");

    printfU( cU("\nUsage: %s [options]\n"), programName );

    printfU( cU("Options:\n") );

    printfU( cU("  -h <ashost>          SAP application server to connect to\n") );

    printfU( cU("  -s <sysnr>           system number of the target SAP system\n") );

    printfU( cU("  -u <user>            user\n") );

    printfU( cU("  -p <passwd>          password\n") );

    printfU( cU("  -c <client>          client \n") );

    printfU( cU("  -l <language>        logon language\n") );

    printfU( cU("  -D <destination>     destination defined in RFC config file sapnwrfc.ini\n") );

    printfU( cU("  -F <function>        function module to be called, only EDI_DATA_INCOMING\n") );

    printfU( cU("                       or EDI_STATUS_INCOMING or Z_MCA_MFT_UTILITY is supported\n") );

    printfU( cU("  -E PATHNAME=<path>   path, including file name, to EDI data file or status \n") );

    printfU( cU("                       file, with maximum length of 100 charachters\n") );

    printfU( cU("  -E PORT=<port name>  port name of the ALE/EDI interface with maximum   \n") );

    printfU( cU("                       length of 10 charachters\n") );

    printfU( cU("  -t <level>           set RFC tracelevel 0(off), 1(brief), 2(verbose) or 3(full)\n") );

    printfU( cU("  -help  or -?         display this help page\n") );

    printfU( cU("  -v                   display the version of the NWRFC library, the version\n") );

    printfU( cU("                       of the compiler used by SAP to build this program and\n") );

	printfU( cU("                       the version of startrfc\n") );

    printfU( cU("  -i                   connect to the target system and display the system info\n") );



}



void showConnAttr(RFC_ATTRIBUTES *attr)

{

    if(!attr)

        return;

    printfU(cU("SAP System ID: %s\n"),attr->sysId);

    printfU(cU("SAP System Number: %s\n"),attr->sysNumber);

    printfU(cU("Partner Host: %s\n"),attr->partnerHost);

    printfU(cU("Own Host: %s\n"),attr->host);

    printfU(cU("Partner System Release: %s\n"),attr->partnerRel);

    printfU(cU("Partner Kernel Release: %s\n"),attr->kernelRel);

    printfU(cU("Own Release: %s\n"),attr->rel);

    printfU(cU("Partner Codepage: %s\n"),attr->partnerCodepage);

    printfU(cU("Own Codepage: %s\n"),attr->codepage);

    printfU(cU("User: %s\n"),attr->user);

    printfU(cU("Client: %s\n"),attr->client);

    printfU(cU("Language: %s\n"),attr->language);

}







void showVersion()

{

    printfU (cU("NW RFC Library Version: %s\n"), RfcGetVersion(NULL, NULL, NULL));

    printfU (cU("Compiler Version:\n")

#if defined SAPonAIX

		cU("%04X (VVRR)\n"), __xlC__

#elif defined SAPonHP_UX

		cU("%06d (VVRRPP. %s Compiler)\n"),	/*yes, decimal here!*/

	#if defined __HP_cc

			__HP_cc, cU("C")

	#elif defined __HP_aCC

			__HP_aCC, cU("C++")

	#else

			0, cU("Unknown Version")

	#endif

#elif defined SAPonLINUX

		cU("%s\n"), cU(__VERSION__)

#elif defined SAPonNT

		cU("%09d (VVRRPPPPP. Microsoft (R) C/C++ Compiler)\n"), _MSC_FULL_VER		/*decimal!*/

#elif defined SAPonSUN

		cU("%03X (VRP. %s Compiler)\n"),

	#if defined __SUNPRO_C

			__SUNPRO_C, cU("C")

	#elif defined __SUNPRO_CC

			__SUNPRO_CC, cU("C++")

	#else

			0, cU("Unknown Version")

	#endif

#elif defined SAPonOS390

        cU("%08X (PVRRMMMM)\n"), __COMPILER_VER__

#else

		cU("%s\n"), cU("Version not available.")

#endif

	);

    printfU (cU("Startrfc Version: 2018-08-15\n"));

}

Compiling & Binding:

Before compiling the custom c++ program, ensure that NW RFC SDK is in kernel folder & GCC rpm is installed for recompiling a new version of the STARTRFC program. Once the pre-requisites were in place, we proceeded with compiling and binding the file with SDK & Kernel with the below commands.

Bind with NW RFC SDK

g++ -o zstartrfc zstartrfc.o nwrfcsdk/lib/libsapnwrfc.so nwrfcsdk/lib/libsapucum.so

g++ -std=c++0x -DSAPwithUNICODE -I nwrfcsdk/include -c -o zstartrfc.o zstartrfc.cpp

Bind with Kernel

g++ -std=c++0x -DSAPwithUNICODE -I /sapmnt/SID/exe/uc/linuxx86_64/nwrfcsdk/include -c -o zstartrfc.o zstartrfc.cpp

g++ -o zstartrfc zstartrfc.o /sapmnt/SID/exe/uc/linuxx86_64/libsapnwrfc.so /sapmnt/SID/exe/uc/linuxx86_64/libsapucum.so

The above commands created the zstartrfc program which can be now placed in the kernel directory. Finally updated the custom application Java file to call ZSTARTRFC instead of STARTRFC

This process of creating the custom kernel executable now allowed to call the custom function module and bypass the restriction with startrfc.

Reference SAP Notes

2010749 - Startrfc -F option restriction in NW RFC SDK

2573953 - Compiling and Linking RFC Programs with the SAP NetWeaver RFC SDK 7.50

Where can I learn to create business processes and integration scenarios using the required tools?

2023-11-28T16:38:49.712000+01:00

You can build the skills you need, for free and at your own pace with our Digital Learning Journey.
on our SAP Learning Site

I recommend to access our Developing Business Processes with SAP Process Orchestration learning jo...

Overview
This learning journey is designed for integration designers and developers with responsibilities for building business processes and integration scenarios with SAP Process Orchestration.

Learning objectives

After completing this learning journey, developers will be able to create business processes and integration scenarios using the required tools. You will understand how to work with SAP NetWeaver Developer Studio, to create iFlows and business processes and connect iFlows with your business processes.

Prerequisites
Discovering SAP Process Orchestration

I hope this is helpful

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

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

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

Kind regards
Margit

SAP Security Patch Day December 2023

2023-12-13T23:03:18+01:00

On December 12, 2023, SAP once again demonstrated its commitment to cybersecurity by releasing a crucial set of security patches. These patches are designed to fix various vulnerabilities identified across various SAP products. The focus of this month's SAP Security Patch Day is primarily on fixing program errors that have the potential to pose security risks. We have provided a detailed overview of the security notes released below, organized according to their severity as determined by the Common Vulnerability Scoring System (CVSS) scores:

Vulnerability ID	CVE Number	Description	CVSS Score	Release Date	Update Date
BI-BIP-CMC	CVE-2023-25616	Code Injection vulnerability in SAP Business Objects Business Intelligence Platform (CMC)	9.9	14.03.2023	12.09.2023
BI-BIP-LCM	CVE-2023-40622	Information Disclosure vulnerability in SAP BusinessObjects Business Intelligence Platform (Promotion Management)	9.9	12.09.2023	-
BC-IAM-SSO-CCL	CVE-2023-40309	Missing Authorization check in SAP CommonCryptoLib	9.8	12.09.2023	-
BC-FES-BUS-DSK	CVE-2023-40624	Security updates for the browser control Google Chromium delivered with SAP Business Client	10.0	10.04.2018	12.09.2023
BC-XI-CON-UDS	CVE-2022-41272	Improper access control in SAP NetWeaver AS Java (User Defined Search)	9.9	13.12.2022	12.09.2023
BI-RA-WBI-FE	CVE-2023-42472	Insufficient File type validation in SAP BusinessObjects Business Intelligence Platform (Web Intelligence HTML interface)	8.7	12.09.2023	-
BC-CCM-HAG	CVE-2023-40308	Memory Corruption vulnerability in SAP CommonCryptoLib	7.5	12.09.2023	-
BC-SYB-PD	CVE-2023-40621	Code Injection vulnerability in SAP PowerDesigner Client	6.3	12.09.2023	-
MM-FIO-PUR-SQ-CON	CVE-2023-40625	Missing Authorization check in Manage Purchase Contracts App	5.4	12.09.2023	-
BC-GP	CVE-2023-41367	Missing Authentication check in SAP NetWeaver (Guided Procedures)	5.3	12.09.2023	-
BI-BIP-LCM	CVE-2023-37489	Information Disclosure vulnerability in SAP BusinessObjects Business Intelligence Platform (Version Management System)	5.3	12.09.2023	-
FS-QUO	CVE-2023-40308	Denial of service (DOS) vulnerability in SAP Quotation Management Insurance (FS-QUO)	5.7	12.09.2023	-
BC-WD-UR	CVE-2023-40624	Code Injection vulnerability in SAP NetWeaver AS ABAP (applications based on Unified Rendering)	5.5	12.09.2023	-
BI-BIP-INS	CVE-2023-40623	Arbitrary File Delete via Directory Junction in SAP BusinessObjects Suite(installer)	6.2	12.09.2023	-
FI-FIO-AP-CHK	CVE-2023-41368	Insecure Direct Object Reference (IDOR) vulnerability in SAP S/4HANA (Manage checkbook apps)	2.7	12.09.2023	-
FI-FIO-AP	CVE-2023-41369	External Entity Loop vulnerability in SAP S/4HANA (Create Single Payment application)	3.5	12.09.2023	-

Statistics:

Total new SAP notes released: 16

Total vulnerabilities addressed: 16

Highest CVSS Score: 10.0 (HotNews)

Security updates for the browser control Google Chromium delivered with SAP Business Client – [CVE-2023-40624]

Top 3 Critical Issues:

1. BC-FES-BUS-DSK [CVE-2023-40624]: Security updates for the browser control Google Chromium delivered with SAP Business Client (CVSS Score: 10.0)

This vulnerability could compromise the integrity and confidentiality of the SAP Business Client through the browser control.

2. BC-CP-CF-SEC-LIB [Multiple CVEs]: Escalation of Privileges in SAP Business Technology Platform (BTP) Security Services Integration Libraries (CVSS Score: 9.1)

This issue allows unauthorized escalation of privileges, potentially compromising system security.

3. IS-OIL-DS-HPM [CVE-2023-36922]: OS command injection vulnerability in SAP ECC and SAP S/4HANA (IS-OIL) (CVSS Score: 9.1)

This vulnerability allows attackers to execute arbitrary OS commands, posing a significant threat to the integrity and availability of the system.

Customize the ABAP Editor Theme in SAP NetWeaver

2024-02-23T09:38:43.214000+01:00

ABAPers are you tired of the default appearance of the ABAP Editor in SAP NetWeaver? Do you wish to add a personal touch to your coding environment? With just a few steps, you can customize the theme of your ABAP Editor to suit your taste and make coding sessions more enjoyable.

ABAP Editor Dark Theme

Step 1: Open ABAP Editor Directory

Begin by navigating to the ABAP Editor directory. You can do this by opening the Command Prompt and running the following command:

start "" "%APPDATA%\SAP\SAP GUI\ABAP Editor"

Alternatively, you can directly open the folder \AppData\Roaming\SAP\SAP GUI\ABAP Editor.

Step -2 Replace abap_spec.xml File

Once you have accessed the ABAP Editor folder, locate the abap_spec.xml file. This file contains the specifications for the editor's theme. Note: Before making any changes, it's advisable to create a backup of the original abap_spec.xml file.

Now Replace the source code of abap_spec.xml with your below code.

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="lang_spec.xslt"?>
<XMLConfigSettings>
	<FILEINFO>
		<Author>Alex Arseniev</Author>
		<Type>LangSpec</Type>
		<Language>ABAP4</Language>
		<Desc>Language specification for ABAP4</Desc>
	</FILEINFO>
	<SPECIFICATION>
		<FilePattern>*.ecatt</FilePattern>
		<CaseSensitive>0</CaseSensitive>
		<OpenClose>()[]''``</OpenClose>
		<Delimiters>,.:</Delimiters>
		<WrapBy>(),</WrapBy>
		<EscapeChar></EscapeChar>
		<LineEnd>.</LineEnd>
		<Operators>?-+/&amp;*=&lt;&gt;~</Operators>
		<Words>0-9a-Z_/-&lt;&gt;</Words>
		<Numbers>-+0-9a-fA-F.xXUL</Numbers>
		<HierarchySeparator>
			<Separator id="1" text="-"/>
			<Separator id="2" text="-&gt;"/>
			<Separator id="3" text="=&gt;"/>
		</HierarchySeparator>
	</SPECIFICATION>
	<COMPLEX_USING>
		<Word text="at"/>
		<Word text="where"/>
		<Word text="key"/>
	</COMPLEX_USING>
	<STRUCTURES>
		<Structure open="region" close="endregion" header="0" has_name="1" sent_start="1"/>
		<Structure open="if" middle="else" close="endif" header="1" sent_start="1">
			<Middle name="elseif"/>
		</Structure>
		<Structure open="case" middle="when" close="endcase" header="1" sent_start="1">
			<Middle name="others"/>
		</Structure>
		<Structure open="loop" close="endloop" header="1" sent_start="1"/>
		<Structure open="form" close="endform" has_name="1" separator="1" header="1" sent_start="1"/>
		<Structure open="while" close="endwhile" header="1" sent_start="1"/>
		<Structure open="do" close="enddo" header="1" sent_start="1"/>
		<Structure open="try" middle="catch" close="endtry" header="1" sent_start="1">
			<Middle name="cleanup"/>
		</Structure>
		<Structure open="class" close="endclass" has_name="1" separator="1" header="1" sent_start="1"/>
		<Structure open="method" close="endmethod" has_name="1" separator="1" header="1" sent_start="1"/>
		<Structure open="function" close="endfunction" has_name="1" separator="1" header="1" sent_start="1"/>
		<Structure open="module" close="endmodule" has_name="1" separator="1" header="1" sent_start="1"/>
		<Structure open="interface" close="endinterface" header="1" sent_start="1"/>
		<Structure open="at" close="endat" header="1" sent_start="1"/>
		<Structure open="exec" close="endexec" header="0" sent_start="1"/>
		<Structure open="define" close="end-of-definition" has_name="1" separator="1" header="0" sent_start="1"/>
		<Structure open="provide" close="endprovide" header="1" sent_start="1"/>
		<Structure open="select" close="endselect" header="1" sent_start="1"/>
		<Structure open="begin" close="end" header="0"/>
		<Structure open="enhancement" close="endenhancement" header="0" has_name="1" separator="1" sent_start="1"/>
		<Structure open="enhancement-section" close="end-enhancement-section" header="0" has_name="1" separator="1" sent_start="1"/>
	</STRUCTURES>
	<FORMAT>
		<DefaultIndent>2</DefaultIndent>
		<ResetFormatSymbols>,</ResetFormatSymbols>
		<FormatWords>
			<FormatWord word="data" indent="6" next_line="1"/>
			<FormatWord word="field-symbols" indent="15" next_line="1"/>
			<FormatWord word="importing" indent="2" next_line="1"/>
			<FormatWord word="exporting" indent="2" next_line="1"/>
			<FormatWord word="changing" indent="2" next_line="1"/>
			<FormatWord word="exceptions" indent="2" next_line="1"/>
			<FormatWord word="tables" indent="2" next_line="1"/>
			<FormatWord word="using" indent="6" next_line="1"/>
			<FormatWord word="elseif" indent="-2"/>
		</FormatWords>
	</FORMAT>
	<SYNTAXINFO>
		<InfoType id="1" name="Compiler error" clr="-1"/>
		<InfoType id="2" name="Performance tip" clr="-1"/>
		<InfoType id="3" name="Syntax tip" clr="-1"/>
		<InfoType id="4" name="Spelling error" clr="-1"/>
	</SYNTAXINFO>
	<COLORSYNTAX>
		<TextType id="8" name="Breakpoint" dstyle="1" dbkclr="0" clr="16777215" bkclr="139"/>
		<TextType id="10" name="Changed indicator" dstyle="1" dbkclr="1" clr="139"/>
		<TextType id="11" name="Changed and saved indicator" dstyle="1" dbkclr="1" clr="12895487"/>
		<TextType id="5" name="Current line" dstyle="1" dbkclr="0" clr="-1" bkclr="15918553"/>
		<TextType id="6" name="Erroneous line" dstyle="1" dbkclr="0" clr="65535" bkclr="255"/>
		<TextType id="7" name="Execution" dstyle="1" dbkclr="0" clr="16777215" bkclr="3329330"/>
		<TextType id="3" name="Inactive selected text" dstyle="1" dbkclr="0" clr="-1" bkclr="-1"/>
		<TextType id="4" name="Line number" dstyle="1" dbkclr="1" clr="9342520"/>
      	<TextType id="13" name="Maximum line length" dstyle="1" dbkclr="1" clr="255"/>
		<TextType id="2" name="Selected text" dstyle="1" dbkclr="0" clr="16777215" bkclr="9922608"/>
		<TextType id="1" name="Selection margin" dstyle="1" dbkclr="1" clr="14281970"/>
		<TextType id="21" name="Text highlights" bold="1" italic="0" underline="0" clr="0" bkclr="-1"/>
		<TextType id="22" name="Text highlights error" bold="1" italic="0" underline="0" clr="255" bkclr="-1"/>

		<TextType id="30" name="Normal" dstyle="0" dbkclr="0" bold="0" italic="0" underline="0" clr="-1" bkclr="-1"/>
		<TextType id="9" name="Read-only mode" dstyle="1" dbkclr="1" clr="15789798"/>

		<TextType id="31" name="Comments" dstyle="0" dbkclr="0" text="1" bold="0" italic="1" underline="0" clr="8421504" bkclr="-1">
			<FirstChar>*</FirstChar>
			<Conditions>
				<Condition start="&quot;" end="\n"/>
			</Conditions>
		</TextType>
		<TextType id="52" name="Keywords" ImageIdx="13" bold="0" italic="0" underline="0" clr="16711680" bkclr="-1" CaseDisplayMode="0">
			<Keywords>
				<Keyword text="Class-pool"/>
				<Keyword text="Function-pool"/>
				<Keyword text="Include"/>
				<Keyword text="Interface-pool"/>
				<Keyword text="Program"/>
				<Keyword text="Report"/>
				<Keyword text="Type-pool"/>

                		<Keyword text="bound"/>
				<Keyword text="Class"/>
				<Keyword text="Class-data"/>
				<Keyword text="Class-events"/>
				<Keyword text="Class-methods"/>
				<Keyword text="Constants"/>
				<Keyword text="Contexts"/>
				<Keyword text="Data"/>
				<Keyword text="Definition"/>
				<Keyword text="Endclass"/>
				<Keyword text="Endinterface"/>
				<Keyword text="Enhancement"/>
				<Keyword text="Endenhancement"/>
				<Keyword text="Enhancement-section"/>
				<Keyword text="End-enhancement-section"/>
				<Keyword text="Events"/>
				<Keyword text="Field-groups"/>
				<Keyword text="Field-symbols"/>
				<Keyword text="Implementation"/>
				<Keyword text="Interface"/>
				<Keyword text="Interfaces"/>
				<Keyword text="Local"/>
				<Keyword text="Methods"/>
				<Keyword text="Parameters"/>
				<Keyword text="Private"/>
				<Keyword text="Protected"/>
				<Keyword text="Public"/>
				<Keyword text="Ranges"/>
				<Keyword text="Section"/>
				<Keyword text="Selection-screen"/>
				<Keyword text="Select-options"/>
				<Keyword text="Static"/>
				<Keyword text="Statics"/>
				<Keyword text="spots"/>
				<Keyword text="Type-pools"/>
				<Keyword text="Types"/>
		                <Keyword text="During "/>
				<Keyword text="End-of-page"/>
				<Keyword text="End-of-selection"/>
				<Keyword text="Initialization"/>
				<Keyword text="Line-selection"/>
				<Keyword text="Line-selection"/>
				<Keyword text="Load-of-program"/>
				<Keyword text="Selection-screen"/>
				<Keyword text="Start-of-selection"/>
				<Keyword text="Top-of-page"/>
				<Keyword text="User-command"/>

				<Keyword text="and"/>
				<Keyword text="assigned"/>
				<Keyword text="At"/>
				<Keyword text="Begin"/>
				<Keyword text="between"/>
				<Keyword text="block"/>
				<Keyword text="byte-ca"/>
				<Keyword text="byte-cn"/>
				<Keyword text="byte-co"/>
				<Keyword text="byte-cs"/>
				<Keyword text="byte-na"/>
				<Keyword text="byte-ns"/>
				<Keyword text="Ca"/>
				<Keyword text="Call"/>
				<Keyword text="Case"/>
				<Keyword text="Catch"/>
				<Keyword text="Change"/>
				<Keyword text="Check"/>
				<Keyword text="Cleanup"/>
				<Keyword text="cn"/>
				<Keyword text="co"/>
				<Keyword text="Continue"/>
				<Keyword text="cp"/>
				<Keyword text="cs"/>
				<Keyword text="Define"/>
				<Keyword text="Do"/>
				<Keyword text="Else"/>
				<Keyword text="Elseif"/>
				<Keyword text="End"/>
				<Keyword text="Endat"/>
				<Keyword text="Endcase"/>
				<Keyword text="Enddo"/>
				<Keyword text="Endexec"/>
				<Keyword text="Endform"/>
				<Keyword text="Endfunction"/>
				<Keyword text="Endif"/>
				<Keyword text="Endloop"/>
				<Keyword text="Endmethod"/>
				<Keyword text="Endmodule"/>
				<Keyword text="End-of-definition"/>
				<Keyword text="Endon"/>
				<Keyword text="Endprovide"/>
				<Keyword text="Endselect"/>
				<Keyword text="Endtry"/>
				<Keyword text="Endwhile"/>
				<Keyword text="eq"/>
				<Keyword text="Exec"/>
				<Keyword text="Exit"/>
				<Keyword text="first"/>
				<Keyword text="Form"/>
				<Keyword text="Function"/>
				<Keyword text="ge"/>
				<Keyword text="gt"/>
				<Keyword text="If"/>
				<Keyword text="in"/>
				<Keyword text="initial"/>
				<Keyword text="is"/>
				<Keyword text="last"/>
				<Keyword text="le"/>
				<Keyword text="Leave"/>
				<Keyword text="Loop"/>
				<Keyword text="lt"/>
				<Keyword text="M"/>
				<Keyword text="Method"/>
				<Keyword text="Module"/>
				<Keyword text="na"/>
				<Keyword text="ne"/>
				<Keyword text="new"/>
				<Keyword text="not"/>
				<Keyword text="np"/>
				<Keyword text="ns"/>
				<Keyword text="o"/>
				<Keyword text="of"/>
				<Keyword text="On"/>
				<Keyword text="or"/>
				<Keyword text="Perform"/>
				<Keyword text="Provide"/>
				<Keyword text="requested"/>
				<Keyword text="Return"/>
				<Keyword text="screen"/>
				<Keyword text="Select"/>
				<Keyword text="Sql"/>
				<Keyword text="Stop"/>
				<Keyword text="supplied"/>
				<Keyword text="transaction"/>
				<Keyword text="Try"/>
				<Keyword text="When"/>
				<Keyword text="While"/>
				<Keyword text="z"/>

				<Keyword text="Abs"/>
				<Keyword text="Abs"/>
				<Keyword text="Abs"/>
				<Keyword text="Acos"/>
				<Keyword text="Add"/>
				<Keyword text="Add-corresponding"/>
				<Keyword text="Adjacent"/>
				<Keyword text="Aliases"/>
				<Keyword text="all"/>
				<Keyword text="Analyzer"/>
				<Keyword text="Any"/>
				<Keyword text="Append"/>
				<Keyword text="appending"/>
				<Keyword text="as"/>
				<Keyword text="ascending"/>
				<Keyword text="Asin"/>
				<Keyword text="Assign"/>
				<Keyword text="assigning"/>
				<Keyword text="Assert"/>
				<Keyword text="Atan"/>
				<Keyword text="Authority-check"/>
				<Keyword text="Avg"/>
				<Keyword text="Back"/>
				<Keyword text="BAdi"/>
				<Keyword text="binary"/>
				<Keyword text="Bit"/>
				<Keyword text="Bit-and"/>
				<Keyword text="Bit-not"/>
				<Keyword text="Bit-or"/>
				<Keyword text="Bit-xor"/>
				<Keyword text="Blank"/>
				<Keyword text="Bound"/>
				<Keyword text="Break-point"/>
				<Keyword text="buffer"/>
				<Keyword text="by"/>
				<Keyword text="c"/>
				<Keyword text="case"/>
				<Keyword text="Ceil"/>
				<Keyword text="Centered"/>
				<Keyword text="changing"/>
				<Keyword text="Charlen"/>
				<Keyword text="Checkbox"/>
				<Keyword text="Clear"/>
				<Keyword text="client"/>
				<Keyword text="Close"/>
				<Keyword text="Cnt"/>
				<Keyword text="Code"/>
				<Keyword text="Collect"/>
				<Keyword text="color"/>
				<Keyword text="col_negative"/>
				<Keyword text="col_normal"/>
				<Keyword text="Comment"/>
				<Keyword text="Commit"/>
				<Keyword text="Communication"/>
				<Keyword text="comparing"/>
				<Keyword text="component"/>
				<Keyword text="Compute"/>
				<Keyword text="Concatenate"/>
				<Keyword text="Condense"/>
				<Keyword text="Control"/>
				<Keyword text="Controls"/>
				<Keyword text="Convert"/>
				<Keyword text="Copy"/>
				<Keyword text="Cos"/>
				<Keyword text="Cosh"/>
				<Keyword text="Count"/>
				<Keyword text="Country"/>
				<Keyword text="Create"/>
				<Keyword text="Currency"/>
				<Keyword text="Cursor"/>
				<Keyword text="Customer-function"/>
				<Keyword text="Database"/>
				<Keyword text="Dataset"/>
				<Keyword text="date"/>
				<Keyword text="Dbmaxlen"/>
				<Keyword text="Decimals"/>
				<Keyword text="default"/>
				<Keyword text="Delete"/>
				<Keyword text="Demand"/>
				<Keyword text="descending"/>
				<Keyword text="Describe"/>
				<Keyword text="Detail"/>
				<Keyword text="Dialog"/>
				<Keyword text="Distinct"/>
				<Keyword text="Div"/>
				<Keyword text="Divide"/>
				<Keyword text="Divide-corresponding"/>
				<Keyword text="duplicates"/>
				<Keyword text="Dynpro"/>
				<Keyword text="Edit"/>
				<Keyword text="Editor-call"/>
				<Keyword text="encoding"/>
				<Keyword text="equal"/>
				<Keyword text="Event"/>
				<Keyword text="Exceptions"/>
				<Keyword text="excluding"/>
				<Keyword text="Exp"/>
				<Keyword text="Exponent"/>
				<Keyword text="Export"/>
				<Keyword text="exporting"/>
				<Keyword text="Extended"/>
				<Keyword text="Extract"/>
				<Keyword text="Fetch"/>
				<Keyword text="Field"/>
				<Keyword text="Fields"/>
				<Keyword text="Find"/>
				<Keyword text="Floor"/>
				<Keyword text="for"/>
				<Keyword text="Format"/>
				<Keyword text="Frac"/>
				<Keyword text="frame"/>
				<Keyword text="Free"/>
				<Keyword text="from"/>
				<Keyword text="Generate"/>
				<Keyword text="Get"/>
				<Keyword text="greater"/>
				<Keyword text="Group"/>
				<Keyword text="handler"/>
				<Keyword text="hashed"/>
				<Keyword text="header"/>
				<Keyword text="help-id"/>
				<Keyword text="Help-request"/>
				<Keyword text="Hide"/>
				<Keyword text="Hotspot"/>
				<Keyword text="i"/>
				<Keyword text="Icon"/>
				<Keyword text="id"/>
				<Keyword text="Import"/>
				<Keyword text="importing"/>
				<Keyword text="index"/>
				<Keyword text="Infotypes"/>
				<Keyword text="Inheriting"/>
				<Keyword text="Input"/>
				<Keyword text="Insert"/>
				<Keyword text="intensified"/>
				<Keyword text="into"/>
				<Keyword text="Inverse"/>
				<Keyword text="Join"/>
				<Keyword text="key"/>
				<Keyword text="Language"/>
				<Keyword text="Leading"/>
				<Keyword text="left"/>
				<Keyword text="left-justified"/>
				<Keyword text="less"/>
				<Keyword text="Like"/>
				<Keyword text="Line"/>
				<Keyword text="Line-count"/>
				<Keyword text="Lines"/>
				<Keyword text="Line-size"/>
				<Keyword text="List-processing"/>
				<Keyword text="Load"/>
				<Keyword text="lower"/>
				<Keyword text="Locale"/>
				<Keyword text="Log"/>
				<Keyword text="Log10"/>
				<Keyword text="Margin"/>
				<Keyword text="Mask"/>
				<Keyword text="Matchcode"/>
				<Keyword text="Max"/>
				<Keyword text="memory"/>
				<Keyword text="Message"/>
				<Keyword text="Message-id"/>
				<Keyword text="Min"/>
				<Keyword text="Mod"/>
				<Keyword text="mode"/>
				<Keyword text="Modify"/>
				<Keyword text="Move"/>
				<Keyword text="Move-corresponding"/>
				<Keyword text="Multiply"/>
				<Keyword text="Multiply-corresponding"/>
				<Keyword text="New-line"/>
				<Keyword text="New-page"/>
				<Keyword text="Next"/>
				<Keyword text="no "/>
				<Keyword text="nodes"/>
				<Keyword text="No-gap"/>
				<Keyword text="No-heading"/>
				<Keyword text="Non-unique"/>
				<Keyword text="No-scrolling"/>
				<Keyword text="No-sign"/>
				<Keyword text="No-title"/>
				<Keyword text="No-zero"/>
				<Keyword text="number"/>
				<Keyword text="Numofchar"/>
				<Keyword text="Object"/>
				<Keyword text="occurs"/>
				<Keyword text="occurrences"/>
				<Keyword text="Open"/>
				<Keyword text="optional"/>
				<Keyword text="order"/>
				<Keyword text="others"/>
				<Keyword text="Output"/>
				<Keyword text="Overlay"/>
				<Keyword text="Pack"/>
				<Keyword text="Page"/>
				<Keyword text="Parameter"/>
				<Keyword text="Pf-status"/>
				<Keyword text="places"/>
				<Keyword text="position"/>
				<Keyword text="Print"/>
				<Keyword text="Print-control"/>
				<Keyword text="Property"/>
				<Keyword text="Put"/>
				<Keyword text="Radiobutton"/>
				<Keyword text="Raise"/>
				<Keyword text="Raising"/>
				<Keyword text="Read"/>
				<Keyword text="Receive"/>
				<Keyword text="redefinition"/>
				<Keyword text="ref"/>
				<Keyword text="reference"/>
				<Keyword text="Refresh"/>
				<Keyword text="Reject"/>
				<Keyword text="Replace"/>
				<Keyword text="Reserve"/>
				<Keyword text="Reset"/>
				<Keyword text="right-justified"/>
				<Keyword text="Rollback"/>
				<Keyword text="Round"/>
				<Keyword text="rows"/>
				<Keyword text="Rtti"/>
				<Keyword text="Run"/>
				<Keyword text="Scan"/>
				<Keyword text="Scroll"/>
				<Keyword text="Scroll-boundary"/>
				<Keyword text="Search"/>
				<Keyword text="Selection-table"/>
				<Keyword text="separated"/>
				<Keyword text="Set"/>
				<Keyword text="shared"/>
				<Keyword text="Shift"/>
				<Keyword text="Sign"/>
				<Keyword text="Sin"/>
				<Keyword text="single"/>
				<Keyword text="Sinh"/>
				<Keyword text="Size"/>
				<Keyword text="Skip"/>
				<Keyword text="Sort"/>
				<Keyword text="sorted"/>
				<Keyword text="Specified"/>
				<Keyword text="Split"/>
				<Keyword text="Sqrt"/>
				<Keyword text="Stamp"/>
				<Keyword text="standard"/>
				<Keyword text="starting"/>
				<Keyword text="string"/>
				<Keyword text="Strlen"/>
				<Keyword text="Structure"/>
				<Keyword text="Submit"/>
				<Keyword text="Subtract"/>
				<Keyword text="Subtract-corresponding"/>
				<Keyword text="Sum"/>
				<Keyword text="Summary"/>
				<Keyword text="Supply"/>
				<Keyword text="Suppress"/>
				<Keyword text="Symbol"/>
				<Keyword text="Syntax-check"/>
				<Keyword text="Syntax-trace"/>
				<Keyword text="System-call"/>
				<Keyword text="System-exceptions"/>
				<Keyword text="table"/>
				<Keyword text="Tables"/>
				<Keyword text="Tan"/>
				<Keyword text="Tanh"/>
				<Keyword text="task"/>
				<Keyword text="Text"/>
				<Keyword text="Textpool"/>
				<Keyword text="Time"/>
				<Keyword text="times"/>
				<Keyword text="title"/>
				<Keyword text="Titlebar"/>
				<Keyword text="to"/>
				<Keyword text="Transfer"/>
				<Keyword text="Translate"/>
				<Keyword text="transporting"/>
				<Keyword text="Trunc"/>
				<Keyword text="type"/>
				<Keyword text="Uline"/>
				<Keyword text="under"/>
				<Keyword text="unique"/>
				<Keyword text="Unit"/>
				<Keyword text="Unpack"/>
				<Keyword text="up"/>
				<Keyword text="Update"/>
				<Keyword text="upper"/>
				<Keyword text="using"/>
				<Keyword text="value"/>
				<Keyword text="Value-request"/>
				<Keyword text="Wait"/>
				<Keyword text="Where"/>
				<Keyword text="Window"/>
				<Keyword text="with"/>
				<Keyword text="With-title"/>
				<Keyword text="Work"/>
				<Keyword text="Write"/>
				<Keyword text="x"/>
				<Keyword text="xor"/>
				<Keyword text="xstring"/>
				<Keyword text="Xstrlen"/>
				<Keyword text="zone"/>
			</Keywords>
		</TextType>
		<TextType id="32" name="Numbers" dstyle="0" dbkclr="0" bold="0" italic="0" underline="0" clr="16750899" bkclr="-1"/>
		<TextType id="33" name="Strings" dstyle="0" dbkclr="0" text="1" bold="0" italic="0" underline="0" clr="1680973" bkclr="-1">
			<FirstChar/>
			<Conditions>
				<Condition start="'" end="'"/>
				<Condition start="`" end="`"/>
			</Conditions>
		</TextType>
		<TextType id="40" name="Syntactical error" dstyle="1" dbkclr="0" clr="255" bkclr="-1"/>
		<TextType id="70" name="Token operator" bold="0" italic="0" underline="0" clr="8421504" bkclr="-1"/>
	</COLORSYNTAX>
</XMLConfigSettings>

By following these simple steps, you can transform the appearance of your ABAP Editor and create a more personalized coding environment. Enjoy coding with a fresh new look that reflects your style and enhances your productivity.

If you wish to create your own theme, you can easily do so by navigating to the options menu and selecting "Fonts and Colors." This feature allows you to customize the visual aspects of the ABAP Editor to your liking, empowering you to create a personalized coding environment tailored to your preferences.

Customize the ABAP Editor theme in SAP NetWeaver for a personalized coding environment. Follow simple steps to create a workspace that enhances creativity and productivity in your ABAP development journey.

I am writing this blog inspired by the following blog authored by @alexey_arseniev . It's an amazing piece of work that provides valuable insights into the ABAP Editor.

https://community.sap.com/t5/application-development-blog-posts/old-new-abap-editor/bc-p/13328531

Thank you for reading! I hope you enjoy your newly customized ABAP Editor.

Hamad

Broadcom (Automic) Agent Installation and configuration for SAP Batch Jobs

2024-02-23T09:39:56.186000+01:00

Purpose of the Document: The purpose is to show the Automic (Brodcom) Agent installation on Linux Server, it’s integration with SAP System and Automic Portal web UI to trigger automatic SAP Jobs and central controlling for the Jobs.

This Document will Show:

Agent Media download.
Required media for Agent Setup
Service Manager installation
Configuration of Agent
Configuration of Service Manager

Automic Tool:

Automic Automation for SAP allows business processes to be created with workflows that include jobs from SAP systems.
Automation Engine and its functions can be used in various ways in order to support processing in SAP.

In below example we will installing the Automic Agent and Service Manager for version 12.3.6 in Linux environment

Step 1: Download Media from Broadcom Portal

By Using Link- Automic Download Center - Component Downloads

Once the media is downloaded we need to extract the files and unzip and untar the same

For Agent below shown files will be used

For Service manager below shown files will be used

Step 2: Download SAP JCO
https://me.sap.com/softwarecenter

Goto Path -->SUPPORT PACKAGES & PATCHES -> By Category -> SAP Connectors ->

Step 3: Automic Agent and Service Manager media Untar and unzip

Unpack the .tar file:

gzip -d UCXJR3X.tar.gz

tar xvfo UCXJR3X.tar

Before making changes in service manager files take backup of original files

Rename file ucybsmgr.ori.ini to ucybsmgr.ini

Step 4: Make changes in Service Manager and Agent file

uc4.smd and uc4.smc file will be used to initiate service manager process and agent process.

Rename uc4.ori.smd to uc4.smd and define Agent Path, JAVA Path to start the agent Process and Agent name (same name will be used in ucxjr3x.ini (Agent file))

Create uc4.smc and define agent name (same name will be used in ucxjr3x.ini (Agent file)) to trigger the start of Agent process.

Now go to Agent Path
/usr/automic/agents/SAP_SID/bin

Make changes to ucxjr3x.ori.ini as per the required environment ( Define Agent Name, Automic Application and Web Server details where Automic Engine is running)

And rename it to ucxjr3x.ini

Provide Agent Name in the ucxjr3x.ini- This name will also be used in UC4.smc file for triggering Agent process using service manager and with same name agent connection will be created in Automic UI.

Provide Automic server details and port- This is the server for Automic application where your automic engine is running.

AETEST is the name of the Automic Web UI Connection and ucxjr3x.ini file will contain details about automic web UI Application and port.

Step 5: Starting Service Manager and Agent Process

Command to start Agent directly ---> java -jar ucxjr3x.jar

We need to have Java- installed (this Java Path will be defined in uc4.smd file) and it will be used to start the agent process

Command to start Service Manager and agent through Service Manager using file uc4.smc and uc4.smd

nohup ./ucybsmgr AETEST >/dev/null 2>&1 &

Automic agent And Service Manager Process will be running on Linux Server.

Next We need to Configure Agent on Automic Web UI, Create a R3 connection to login on SAP System and Job Object needs to be created which will trigger the Job in Backend SAP System via connection through this Agent.

Creation of Agent in Automic Web UI, Template, R3 Connection and Job Object for SAP we will cover under other blog.

Conclusion:-
In this Blog we have covered installation and configuration of Automic Broadcom Agent on a Linux Platform to Cater Automation of SAP Jobs for a central controlling Tool for Batch Jobs scheduling, monitoring and Modification.

References Link:-

New Installation (automic.com)

Installing the Agent for SAP - Details (automic.com)

Automic Download Center - Component Downloads

https://me.sap.com/softwarecenter

Domain name migration for SAP ABAP system.

2024-03-01T10:53:22.079000+01:00

Hello readers,

Migrating the SAP instances from one domain to another domain is always tedious task for administrators.

To overcome these challenges, I'm going to explain how we can successfully migrate our SAP ECC system from old domain (example.com) to new domain (example2.xyz).

Before we start, we need to make sure couple of things.

Just to be sure, see if DNS server is reachable from the application server (on which SAP is hosted on):

If it is not reachable, you'll need to get help from network support team.

Make an entry of new FQDN (server.example2.xyz) into DNS server to enable the forward lookup.
Add the entry of new domain into hosts file on the application server. ( eg. <ip> <sub domain> <FQDN>)

Activity:

Open transaction - RZ10 and edit Instance profile:

put FQDN in 'icm/host_name_full' parameter then save and activate.

Edit the DEFAULT profile:

put 2nd-level and top-level domain in 'SAPFQDN' parameter (note that 'SAPLOCALHOSTFULL' is made up of 'SAPLOCALHOST' and 'SAPFQDN' values)

* The Subdomain in my case remained unchanged, so I did not change the value of 'SAPLOCALHOST' parameter.

Since this change is permanent, we need to take a restart of SAP system.

Once the SAP starts, go to transaction code - SMICM -> Services, to verify the changes:

This completes the part of actual migration.

Other points to note:

You will also need to generate and apply new certificates using transaction - STRUST according to the new domain if NWBC and/or other portals are being used.
Email node can be changed as well, using transaction code SCOT:

Set default domain to the updated one (like example2.xyz).

Email functionality can be tested using transaction SBWP -> New Message

Few other things to consider:

This blog only covers the SAP part of the migration, not for the different DBs and OS changes. You'll need to look further into OS/DB related transactions and/or parameters to realize the full impact on the SAP system in that case.
You will also need to check if there are any other services, ABAP reports or programs have the old domain configured into them which are being used in the SAP system and make changes accordingly.

Below notes/documents can be referred for more information:

611361 - Hostnames of SAP ABAP Platform servers

Fully Qualified Domain Names (FQDN)

3220752 - NWBC error : The URL contains no complete domain specification\

2148070 - Configuration of e-mail using SMTP (outbound)

How to create a CSR and import the certificate response in STRUST

Detailed information about domains can be found in this article.

Thanks,

Nikhil Kumar.

SAP NetWeaver SAP NetWeaver Application Server for ABAP

E4H Conversion Error in Phase MAIN_NEWBAS/XPRAS_AIMMRG

2024-03-13T11:25:12.382000+01:00

If you are trying to do a E4H Conversion from SAP GTS 11.0 to SAP GTS Edition for HANA 2023 with S/4 HANA Foundation 2022 then you may come across below error.

Issue:

During the execution phase below error is reported

Sql command that runs

INSERT INTO "/SAPSLL/TEDTM" ( "MANDT", "STCCS", "RTYPE", "TLC_AART" ) SELECT DISTINCT

"/SAPSLL/LC_CUSM"."MANDT", "/SAPSLL/TLEGSU"."CTSIM" as "STCCS", "/SAPSLL/LC_CUSM"."RTYPE",

"/SAPSLL/LC_CUSM"."TLC_AART" FROM "/SAPSLL/LC_CUSM" INNER JOIN "/SAPSLL/TLEGSU" ON

"/SAPSLL/LC_CUSM"."MANDT" = "/SAPSLL/TLEGSU"."MANDT" AND "/SAPSLL/LC_CUSM"."LGREG" =

"/SAPSLL/TLEGSU"."LGREG" WHERE "/SAPSLL/TLEGSU"."LGREG" = "/SAPSLL/LC_CUSM"."LGREG" AND

"/SAPSLL/TLEGSU"."SRVLL" = 'LECCUS' AND "/SAPSLL/TLEGSU"."CTSTY" = '101' AND NOT (

"/SAPSLL/LC_CUSM"."MANDT" = '000' )

Solution:

Old table: /SAPSLL/LC_CUSM

New table after conversion: /SAPSLL/TEDTM

The reason for the above error is that there are some duplicate entries that exists in /SAPSLL/TEDTM table so the XPRA report is not able to insert the content into the table and it throws an error.

While you can find similar kind of 301 error for different type of schema and table but there is no specific steps for this table which comes during the conversion.

Option1:

Try to login to the clients and see if you can get help from functional consultant to identify the duplicate entries from the table and repeat the phase. (Take a backup before you do this)

Option 2:

Accept the error at this stage and complete the conversion.

Once the conversion is done do below steps.

Check if the index exists.Most likely it will because its a ~0 index and its reserved index which means you can only see that in se14.It wnt even show in hana studio.

- Drop the index from below command from hana studio

ALTER TABLE "SAPABAP1"."/SAPSLL/TEDTM" DROP CONSTRAINT "/SAPSLL/TEDTM~0";

- For HANA databases, use the HANA scripts HANA_Data_DuplicateKeys_CommandGenerator_1.00.100+ and HANA_Data_DuplicateKeys_columnStore_Deletion_CommandGenerator attached in SAP Note 1969700 to remove duplicates

below the command that i used

**************************************

DELETE FROM
"SAPABAP1"."/SAPSLL/TEDTM"
WHERE
"$rowid$" IN
( SELECT
ROW_ID
FROM
( SELECT
"$rowid$" ROW_ID,
ROW_NUMBER() OVER (PARTITION BY "MANDT", "STCCS", "RTYPE") DUP_NO
FROM
"SAPABAP1"."/SAPSLL/TEDTM"
)
WHERE
DUP_NO > 1
)
WITH HINT (NO_AGGR_SIMPLIFICATION, NO_GROUPING_SIMPLIFICATION)

*******************************

@note: Please be double sure when you run this command.Have it verified with the functional consultant as its going to delete duplicate entries from the table.

- Once duplicates are removed, try to create the index again

ALTER TABLE "SAPABAP1"."/SAPSLL/TEDTM" ADD CONSTRAINT "/SAPSLL/TEDTM~0" PRIMARY KEY ( "MANDT", "STCCS", "RTYPE" )

- Run the XPRA again /SAPSLL/XPRA_V8000 (this is the same XPRA which ran during the execution phase)

and this time it should typically work without giving issues.

Hope this help.

Thanks

Sid

How to use Transaction BD87 to reprocess failed IDocs

2024-03-21T15:15:03.463000+01:00

Dear readers.

In this blog we'll look into the functionality of transaction code BD87, It is used to monitor and process the IDocs in SAP:

Let's look at what IDoc is first

IDoc (or intermediate document) is used by SAP applications to transport data between applications and external systems. Businesses using SAP ERP systems, for instance, can exchange data with partners or customers by using IDocs.
While transferring information from a SAP system to an external system takes place through electronic data interchange (EDI), the transfer between SAP systems is handled by SAP's ALE solution. This eliminates the need to transform data across formats in order to exchange data between the various systems.

Process:

Open the transaction BD87 – Go to Basic Transactions-> IDoc Status Monitoring for ALE Messages.

Once we go to transaction screen you will find the option to select the required filters in Initial screen based on the actual need.

In the same screen we get multiple filters to search the IDoc

After providing the required information on the IDoc screen, we can see multiple options (explained below)

Refresh IDoc Display Button- This can be used to refresh the detailed view and when we change the status of any IDoc or reprocess the IDoc.
Expand Subtree:- To expand the subtree of the view component(node) that is presently chosen.
Collapse subtree:- Compresses the subtree of the view's presently chosen component(node).
Display Partner systems:- groups the partner systems, IDoc status, and message type in the IDoc tree view.
Highlight message type:- Groups the IDoc tree view according to the message type and IDoc status.
Select IDocs:- Restricts the IDocs that are now being shown in a pop-up window. The pre-filled parameters match those chosen in the before selection mask.
Display IDocs:- After select the node an ALV list of all IDocs is open, and you can twice click the node and you will achieve the same result.
Trace IDocs:- When you want see trace of Displayed an IDoc status its alternatively clicking the twice on the IDoc this will achieve the same result.
Process:- All of the IDocs of the chosen node are processed by this function. This feature should be utilized carefully because a mistaken click could possibly send thousands of IDocs for re-processing, which could have unintended consequences.

Let's have a look how to process the failed IDoc’s:- When we found the the initial screen of IDoc monitoring then we need to process it, then we there is Process button on Status bar, then select the node then hit the process button and the mentioned IDoc is processed.

These are some major characteristics of BD87 T-code:

Reprocessing Failed IDocs: It is solely used to handle Failed IDocs. We can reprocess the IDoc by using the error number, IDoc number, and necessary message type.

Retains Original IDoc Number: With this option the original IDoc number is kept when processing a failed IDoc in BD87 is restarted. By ensuring the preservation of the IDoc history and references, it is possible to more easily follow the processing timeline.

Processing Several IDocs at Once: This transaction also helps users to process multiple of IDocs at once. Since this allows us to manage multiple IDocs at once, this can be very helpful.

Processes unsuccessful IDocs: We cannot reprocess the IDocs which are already successful.

Hope you enjoyed reading.

Conclusion-

We discussed how to re-process the failed IDoc's.

Related information's-

https://userapps.support.sap.com/sap/support/knowledge/en/2658803

https://userapps.support.sap.com/sap/support/knowledge/en/2514304

https://userapps.support.sap.com/sap/support/knowledge/en/2324075

Please share your feedback and your thoughts. Looking forward to questions and queries.

Thank you.

STMS Reconfiguration for SAP System after Refresh.

2024-03-21T15:16:50.106000+01:00

Hi everyone,

In this blog we'll cover the reconfiguration of Transport Management for SAP ABAP system.

Before we start, let's look at below points to understand about STMS:

STMS stands for SAP Transport Management System, a tool that helps to organize, perform, and monitor transports between SAP Systems.
STMS is used for central management of all transport functions, such as defining the transport domain controller, configuring the SAP system landscape, defining the transport routes, and distributing the configuration.
STMS eliminates the need for user actions at the operating system level, since all the information and functions are mapped in the SAP System

There are times when we need to reconfigure STMS in SAP system after system refresh, system copy and implementation.

Prerequisites: - Access of DDIC user in client 000

TMSADM user password must be maintained.

Process:

First, we need to login to the domain controller system from client 000 with DDIC user.

Goto system overview:

Select the system on which refresh has been performed then go to SAP system and delete the system.

In our case Quality system has been refreshed.

Once we click on delete a pop up will be shown in which we need to confirm by clicking “Yes”

After deleting Q system from transport route, it will ask to distribute configuration change immediately.

Click on “NO”

TMS configuration has been deleted.

Now login to the system on which refresh has been completed (i.e. Quality system)

Goto SE06 TCode

Click on “Perform Post Installation Actions”

It will ask you to reinstall the CTS.

Click on “Yes”

It will ask for source system database copy.

Put Production SID in that box and click on continue.

It will ask for changes from Production to Quality.

Click on “Yes”

You will see a pop-up Change and Transport system not configured.

Click on green tick.

It will ask for change originals from production to quality.

Click on “Yes”

A prompt box for delete TMS configuration.

Click on “Yes”

Click “Yes” to delete old versions of transport.

Post installation steps have been completed.

Now go to TCode – STMS

Click on “Save”

It will ask for TMSADM user’s password.

Make sure that password should be correct otherwise it will create inconsistency.

Select Quality system and click on approve.

Once we have approved the system a pop up will appear click on “Yes”

We will distribute the configuration change immediately.

Click on “Yes” on below pop up.

Quality system included in the Transport Domain.

Now we will click on Overview --> Transport Routes --> Adjust with controller.

Click on “Yes”

We will check connection test it should be ok.

Check transport directory everything should be in green.

Now check Transport tool everything needs to be in green.

TMS has been reconfigured.

Troubleshooting Issues:

There can be some issues while setting up the transport route.

1. Sometimes while configuring TMS "system - number" is not populated when system is included in the domain controller.

The TMS RFCs hence created , they do not have system number and so it will not work.

Solution:

Update following RFCs to include system number.

"TMSADM@"

"TMSSUP@

2. Sometimes TMS distribution from Domain controller do not work because TMSADM is not sufficiently authorized. Error thrown however shows that the user or password is not correct.

Solution:

In the RFC below maintain DDIC and password until TMS distribution.

Maintain ‘TMSADM’ back after the distribution is ok.

"TMSADM@"

Documentation below can be referred for more information.

1536753 - Configuration of the Transport Management System

1568362 - TMSADM password change

2861552 - Transport request settings after system copy/upgrade

2751569 - 'Target System not Reachable' Message in Transport Management

How to receive and invoice bitcoin in SAP - Proof of Concept

2024-03-21T15:23:14.914000+01:00

Integrating Bitcoin Transactions into SAP with BTCpayserver

In this post, we'll explore how to receive and invoice your customers in Bitcoin using the open-source software, BTCpayserver.

A key advantage of BTCpayserver is that it allows you to maintain complete control, eliminating the need for a third-party custodian to manage your Bitcoin wallet.

For a clearer picture of where this solution stands on the self-sovereignty spectrum in terms of counterparty risk, refer to Andrew Lunde's insightful visualization:

This visualization is taken from @andrew_lunde blog post.

On the self-sovereignty spectrum, this solution is located on the two right spots.

You can secure your own keys (you are your own custodian).
You can take care of channel management yourself.
You can use the bitcoin blockchain for final settlement.
You are also able to use the Lightning Network for the invoicing (instant and low fee settlement).

Below is a glimpse of the working interface (note: values have been modified for privacy):

When you enter an email address in the invoice creator, it automatically sends an invoice to your customer. Here’s a preview of what your customers will see upon opening the email:

One standout feature is the highly customizable checkout screen. Customers can make payments on-chain or through a lightning wallet, as the QR codes support both protocols.

Main use case

Picture this: You're an accountant at a multinational company, operating across several sales organizations. The CEO has decided to embrace Bitcoin as a payment method, aiming to attract a forward-thinking customer base (envision a strategy akin to Tesla's). Traditional payment providers are off the table due to high costs, and adding another third-party service would only compound compliance complexities.

In your diverse locations, tech expertise varies; not everyone is adept at setting up a wallet or managing Bitcoin transactions. What you need is a streamlined solution allowing your team to invoice in Bitcoin effortlessly, without getting bogged down in exchange rate calculations, Lightning Network channel management, or accessing the company's Bitcoin wallet.

Seamless integration with SAP is key for a smooth and rapid deployment.

Our goal? Simplicity. Customers should receive an aesthetically pleasing invoice that's easy to interact with. Moreover, every aspect of the payment process, including documentation, needs to be meticulously handled.

The ultimate aim is to empower various sales organizations within your company to invoice their customers in Bitcoin, all funneling into a singular, centralized wallet for ease of management.

Outlook

There are more functionalities and possibilities to be excited about. A few I can think of that are cool:

Customer Bitcoin Refunds
Tax Deductions with Split Payments
Automated bitcoin payments

Want to discuss Bitcoin further? Feel free to send me a message!

Or would you like to try it out yourself in your SAP environment? Follow me on my github below, will post more there soon.

Sources:

Andrew Lunde´s blog post:
https://community.sap.com/t5/technology-blogs-by-sap/thoughts-on-bitcoin-etfs-and-the-sovereign-enterprise/ba-p/13574575

My github:

https://github.com/konigra99

Top of page and end of page using SAP List Viewer (SALV)

2024-03-27T10:03:10.471000+01:00

Top of page and end of page using SALV

I am happy to share my very first blog post on SAP OABAP Programming using SALV. In this blog post you will learn how to Create a Top of page and end of page using SALV.

Introduction: -

In SAP, the System Application and Products, 'SALV' stands for SAP List Viewer. It's a framework used to simplify the display of data in a user-friendly format within SAP applications.

Timesaving: Implementing SALV can save developers time as it provides pre-defined functionalities for handling data. Developers can focus on business logic rather than building data display functionalities from scratch.
Standardization: SALV follows SAP's standard programming guidelines, promoting uniformity in coding practices across applications, making maintenance and updates more manageable.

Before writing code, we need to know what and all classes we need to use.

Class names: CL_SALV_TABLE,

CL_SALV_FORM_LAYOUT_GRID,

CL_SALV_FORM_LABEL,

CL_SALV_FORM_LAYOUT_FLOW.

How to create a program to display the top of page and end of page using SALV

Step 1. Go to ABAP editor transaction (SE38) provide a program name and type of the program.

Step 2. Declare class and methods.

Step 3. In this step am implementing the build_salesorder method.

Step 4. Implementing disp_salesorder method to display the data in SALV.

Call factory method to display the data.

Step 5. Top_of_page method takes some variable with a different class; we can see the classes.

Step 6. End_of_page method also declare some classes whatever we did in top of page we need to do in end of page Method also.

Step 9. create a object for main class, using object call the methods and display the records in SALV.

Refer the code below for the whole program.

CLASS sales_order_disp DEFINITION. 
   PUBLIC SECTION. 
    DATA : o_salv TYPE REF TO cl_salv_table. 
    METHODS : build_salesorder, 
              disp_salesorder. 
  PRIVATE SECTION. 
    DATA : lt_vbak TYPE TABLE OF vbak. 
     METHODS : build_top_of_page CHANGING obj_salv TYPE REF TO 
               cl_salv_table, 
               build_end_of_page CHANGING obj_salv TYPE REF TO 
               cl_salv_table. 
ENDCLASS. 
 
CLASS sales_order_disp IMPLEMENTATION. 
    METHOD build_salesorder. 
     SELECT * FROM vbak INTO TABLE lt_vbak . 
    ENDMETHOD. 
    METHOD disp_salesorder. 
 "========THIS METHOD FOR TO DISPLAYING  SALV DISPLAY 
     TRY. 
         cl_salv_table=>factory( 
           IMPORTING 
             r_salv_table   =      o_salv  " Basis Class Simple ALV Tables 
           CHANGING 
             t_table        = lt_vbak 
         ). 
       CATCH cx_salv_msg. " ALV: General Error Class with Message 
     ENDTRY. 
"USING ME KEYWORD CALLING TOP OF PAGE  METHOD THIS IS IN PRIVATE SECTION" 
     me->build_top_of_page( 
       CHANGING 
         obj_salv = o_salv 
     ). 
"USING ME KEYWORD CALLING END OF PAGE  METHOD THIS IS IN PRIVATE SECTION"
     me->build_end_of_page( 
       CHANGING 
         obj_salv = o_salv 
     ). 
"=============TO DISPLAY=============== 
     o_salv->display( ). 
   ENDMETHOD. 
 
"============TO DISPLAY THE TOP LINES=============== 
   METHOD build_top_of_page. 
     DATA: o_label TYPE REF TO cl_salv_form_label, 
           o_flow  TYPE REF TO cl_salv_form_layout_flow.
 
"======creating object for CL_SALV_FORM_LAYOUT_GRID=============== 
     DATA(o_layout) = NEW cl_salv_form_layout_grid( ). 
 
"====using layout objcet am calling isntance method name as CREATE_LABEL 
     o_layout->create_label( 
       EXPORTING 
         row         =   1               " Natural Number 
         column      =   1               " Natural Number 
       RECEIVING 
         r_value     =   o_label               " Label 
     ). 
"=========CL_SALV_FROM_LABEL using this class refernce am calling the 
 SET_TEXT method to write something in top========" 

     o_label->set_text( value = 'Sales order details' ). 
    o_layout->create_flow( 
       EXPORTING 
         row     =    2              " Natural Number 
         column  =     1             " Natural Number 
       RECEIVING 
         r_value = o_flow 
     ). 
"==========cl_salv_form_layout_flow using this class we can add one more row and we can write a information of Top ========="
     o_flow->create_text( 
       EXPORTING 
         text     =  sy-uname 
     ). 
   obj_salv->set_top_of_list( value = o_layout ). 
    o_layout->create_flow( 
       EXPORTING 
         row     =    3             " Natural Number 
         column  =     1             " Natural Number 
       RECEIVING 
         r_value = o_flow 
     ). 
     o_flow->create_text( 
       EXPORTING 
         text     = sy-datum 
     ). 
     obj_salv->set_top_of_list( value = o_layout ). 
   ENDMETHOD. 

  METHOD build_end_of_page. 
     DATA: o_label TYPE REF TO cl_salv_form_label, 
           o_flow  TYPE REF TO cl_salv_form_layout_flow. 
     DATA(o_end) = NEW cl_salv_form_layout_grid( ). 
 
    o_end->create_label( 
       EXPORTING 
         row         =    1              " Natural Number 
         column      =     1             " Natural Number 
       RECEIVING 
         r_value     =     o_label             " Label 
     ). 
 
    o_label->set_text( value =  'SAP Labs India'). 
 
    o_end->create_flow( 
       EXPORTING 
         row     =    2              " Natural Number 
         column  =     1             " Natural Number 
       RECEIVING 
         r_value = o_flow 
     ). 
 
    o_flow->create_text( 
       EXPORTING 
         text     = 'End of page' 
        ). 
 
    obj_salv->set_end_of_list( value =  o_end ). 
  ENDMETHOD. 
ENDCLASS. 
 
START-OF-SELECTION. 
"creating the object for SALES_ORDER_DISP class and calling the method 

 DATA(o_sales) =  NEW sales_order_disp( ). 
  o_sales->build_salesorder( ). 
  o_sales->disp_salesorder( ).

OUTPUT:

How do we adapt the PATCH method in SAP PO

2024-05-13T12:54:11.101000+02:00

Hello everyone,

I will explain how to adapt a REST service called with the PATCH method for use in SAP PO.

In an integration scenario triggered from SAP, if we have a REST link on the receiver side and this link is called with the PATCH method in Postman, we can easily adapt it in PO. This is because not all methods may be available in every PO system. If the PATCH method is not available in your PO system, you can follow the steps below.

1- When configuring, first, we create a Rest receiver adapter.

If there is no authorization in our Rest link, we do not select Basic Authentication. However, if our service authenticates with a username and password, we must specify it in this section.

2- We use our link in the Target URL section in the REST URL tab.

3- We should select POST as the Static Value for our Rest Operation.

To send a service from SAP using the PATCH method through the adapter, we need to add two module configurations in the Module section of the adapter.

4- Module Configuration:

overrideHttpMethod - PATCH

useSAPHttpLibrary - apache

After adding these modules, we can complete the Integrated Configuration steps of the service and trigger it from SAP.

We can easily adapt a REST service triggered as PATCH in Postman to be used in the adapter with the POST method in SAP PO.

SAP Community - SAP NetWeaver

saptune 3.1 on the Horizon

Machine-readable Output

New Commands, Deprecated Commands

Refurbished Status Command

New Solutions and SAP Notes

Zebras are here!

About sysctl

Anything Else?

SAP Security Patch Day – September 2023

SAP Security Patch Day – September 2023

HotNews

High Priority

Medium Priority

Low Priority

Statistics:

Total new SAP notes: 16

Total vulnerabilities addressed: 16

Highest CVSS Score: 10.0 (HotNews) – Security updates for the browser control Google Chromium delivered with SAP Business Client – [CVE-2023-40624]

Top 2 Critical Bugs:

saptune 3.1 is out

Single Sign On - SAML Configuration for Fiori Application using Azure Enterprise

Supercharge SAP workload on IBM Cloud with PowerVS

SAP Notes

Guides

Knowledge Base

SAP workload on IBM PowerVS, what does it mean for customers?

Let’s get started

Design for the best and even better

IBM Power Server

IBM Power E980

IBM Power S922

IBM Processor

IBM Storage

IBM PowerVS design for SAP

Profiles

Core Types

Dedicated

Shared (Uncapped)

What about integration with cloud service and native components?

Conclusion

SAP NetWeaver 7.5メンテナンス方針のSAP Business Suite 7への同期と SAP BW/4HANAの製品戦略のSAP S/4HANAへの同期について

SAP NetWeaver 使用パターン別メンテナンス方針解説

図1：SAP ERP 6.0の同一システム・インスタンスに埋め込まれたSAP NetWeaverのサポート

図2：BW, EP（Enterprise Portal）, PI / PO(Process Integration / Process Orchestration)など、単独システム・インスタンスとしてSAP NetWeaverを使う場合

次世代プラットフォームへの移行について

SAP Note,Captured in which TR Request in SAP using TCODE SE03

Ready for LaMa 3.0 SP29?

Calling custom ABAP function modules with custom startrfc C/C++ file

startrfc worked as follows:

Scenario:

Modification of the startrfc C++ Program

Compiling & Binding:

Where can I learn to create business processes and integration scenarios using the required tools?

SAP Security Patch Day December 2023

Statistics:

Top 3 Critical Issues:

Customize the ABAP Editor Theme in SAP NetWeaver

Broadcom (Automic) Agent Installation and configuration for SAP Batch Jobs

Domain name migration for SAP ABAP system.

E4H Conversion Error in Phase MAIN_NEWBAS/XPRAS_AIMMRG

How to use Transaction BD87 to reprocess failed IDocs

STMS Reconfiguration for SAP System after Refresh.

How to receive and invoice bitcoin in SAP - Proof of Concept

Integrating Bitcoin Transactions into SAP with BTCpayserver

Main use case

Outlook

Top of page and end of page using SAP List Viewer (SALV)

How do we adapt the PATCH method in SAP PO

図2：BW,　EP（Enterprise Portal）, PI / PO(Process Integration / Process Orchestration)など、単独システム・インスタンスとしてSAP NetWeaverを使う場合