Category: Database

Database and dictionary inconsistencies

During an S4HANA upgrade (for example with table PRCD_ELEMENTS) or during normal development work, you might end up in database and ABAP dictionary inconsistencies.

Questions that will be answered in this blog are:

  • How to detect database and ABAP dictionary inconsistencies?
  • How to repair database and ABAP dictionary inconsistencies?

Detection of database inconsistencies

In transaction DB02 you can get an overview of the missing database objects and inconsistencies:

Solving database and ABAP dictionary inconsistencies

The main procedure is explained in OSS note 1248769 – Inconsistency between database and ABAP Dictionary.

Start with transaction SE14 (database utility):

In the main screen click the Check button:

Result:

Pending on the check results, you need to Activate and Adjust the database.

Table reconstruction with DDIC user

Worst case you need to reconstruct the table. Be very sure this is needed before you execute it! Procedure for reconstruct: log on with user DDIC. Start transaction SE14. Select the menu option Table/Reconstruct (this option is only available for user DDIC).

Never use the database utilities in Shadow phase of an upgrade. In case of issues there: raise support message to SAP and only execute after instructions of SAP.

Table conversion issues

SE14 table conversion issues can happen. To roll back the changes, follow the instructions in OSS note 1925322 – How to roll back table conversion?.

In general a key field change that is increasing the length should go ok. Shortening key will can go dramatically wrong in the conversion due to duplicate entries.

Oss note 2465903 – Error DT064 “Structure change at field level (convert table …)” is suggesting to run program RUTATCHK before actual execution.

And read the FAQ note on table conversions: 2428810 – Frequently asked questions about table conversion.

Activating embedded BI in S4HANA

This blog will explain how to activate embedded BI in S4HANA.

Questions that will be answered are:

  • How to activate embedded BI in S4HANA?
  • Where to find more background information about embedded BI activation in S4HANA?

Setting up embedded BI in S4HANA

To start setup of embedded BI in S4HANA go to transaction STC01 and start task list SAP_BW_SETUP_INITIAL_S4HANA:

The task list will ask you to confirm that you have read OSS note 2303900 – Latest Information about BW Setup in S/4HANA Systems. You should really read the note before and apply the known issue notes listed in this note.

Then you need to set the BI client: best to use the same client as your data client. Withe BW content option, just choose all.

Now run the task list and be patient. If the task list finishes correctly you are done. You can use transaction RSA5 to check the content activation.

OSS note 2636754 – Configuration steps for embedded Analytics in ABAP based Applications contains detailed explanation of all the steps in this task list.

Bug fix OSS notes:

Full list is in OSS note 2303900 – Latest Information about BW Setup in S/4HANA Systems.

Known issues

EQ_RS_AUTOSETUP: you might run into an issue with this program.

First apply OSS notes 2704713 – Report EQ_RS_AUTOSETUP: improvements and enhancements and 3005612 – Report EQ_RS_AUTOSETUP: improvements and enhancements (2) to get the latest patches for this program. Then run the program EQ_RS_AUTOSETUP manually:

Transaction RSTCO_ADMIN: this one might not have gone right.

Re-install the content if required.

In case of issues with BGRFC supervisor destination: Use transaction code SBGRFCCONF and check the last tab that the supervisor destination is assigned. In systems with CUA there might be an issue with creating the supervisor destination. In this case follow the steps of OSS note 2775490 – Error in customizing while creating supervisor destination.

Other bug notes:

3283169 – Virtual time hierarchy 0YEA_QUA_MON is not activated when running task list SAP_BW_SETUP_INITIAL_S4HANA

Background information

Good background information can be found at:

The configuration of embedded analytics is also part of the SAP best practices:

Download the full configuration guide.

DB01 Oracle Lock monitor

This blog will answer the following questions:

  • How does a deadlock look like in DB01 Oracle lock monitor?
  • How can I solve the issue?

Deadlocks

A database deadlock can occur when 2 or more processes are trying to update each other and are also waiting for each other. This process will lead to infinite waiting.

DB01 Oracle lock monitor

With the use of transaction DB01 you can get overview of Oracle locks. A deadlock is observed when the status is on HOLD and more processes are in status WAIT.

Solving the deadlock can be done by the Oracle DBA on database level.

Background: 745639 – FAQ: Oracle enqueues.