Enterprise Resource Planning Blog Posts by Members
cancel
Showing results for 
Search instead for 
Did you mean: 
135,854


As you know, SAP HANA comes with many enhancements and features. The new transaction SE16H comes with new features which enables rapid tables check and small queries.

SAP Consultants used to use the transactions code SE16/SE16N/SQVI to check table’s value and/or extract data.

The transaction code SE16H enables:

  • Tables check (consult and extract) like a classical SE16 or SE16N

  • Joint creation for small query

  • Rapid check of number of entries


Here are two cases where this new features are explained

1- Complete accounting document query


Imagine a scenario where you want to check entries for complete accounting document. We can combine many finance tables, but for this example, we will only use two tables:

  • BKPF: Header data of accounting segment

  • BSEG: Accounting document segment


Launch SE16H with BSEG and create a join

Enter the criteria for your join

As described below, to have a complete finance document informations, we will add the table BKPF as a join. Then, we will click on the yellow arrow to add the fields we want to add to the output.

Please note that, as it is shown in this figure, you can apply filters on the fields you need. In this example, we have put filter on fiscal year, company code and posting month. For these filters, we have putted a constant value. But SE16H offers also other methods as displayed below.

After executing the SE16H with the joint we have created, your financial data are displayed as below.

Please note that a layout have been used for the displayed result

The fields displayed contain data from the header table BKPF and data from accounting document segment. For example, here are some field’s detail.

2- Rapid check of entries number


Group feature

In case we want to have a quick view of the number of accounting entries by company code, we have to tick the field group as indicated below and execute.

Group and sort feature

In case we want to have a quick view of number of document type used in the system for a single company code
20 Comments
thangarajthomas
Participant
Hi abdellah khebbari,

Excellent overview information. Thank you for sharing.

Thanks

Thangaraj Thomas

 

 
Good information
Micheal_Mathews
Participant
Thank you, very well explained
surykumar158
Explorer
Thank you so much for sharing knowledge ☺️
gianluca_taccone
Product and Topic Expert
Product and Topic Expert
Hi Adbellah.

Well written, elegant and illustrative, thanks a lot for that.

Since it it so huge, people are frequently searching for a way to compare fields in S/4HANA ACDOCA and ECC tables (e.g  BSEG ,COEP, FAGLFLEXA ) a very useful note on that argument is this one https://launchpad.support.sap.com/#/notes/2156822

I know yours was just an example but I wonder whether it would be possible to find the entire example's result in ACDOCA.  😉

Thanks a lot!

Best

Gianluca

 
pranav_gupata
Participant
Hi Sir,

Very useful article first time i have heard about SE16H

Thq So much !!
tejas_shelke
Discoverer
Very useful transaction details, sharing on LinkedIn.
Yasin
Active Participant
Very good explanation. Thanks for your efforts Abdullah.
0 Kudos
I would like to ask if there is a way to get this joined report in the background and send it via email?
I was looking for it on internet but no luck.
Good information shared that can be used for table counts, reports etc. Thanks for sharing.

Regards, Casimer Quadros
My favorite transaction ! 🙏
Sandra_Rossi
Active Contributor
0 Kudos

Note that the join between BSEG and BUKRS works only in S/4HANA, or in ECC if BSEG has been converted into a transparent table, because BSEG used to be a pooled table in ECC.

An important thing missing here, is how to define the join conditions:

Sandra_Rossi_0-1724936210926.png

 

Sandra_Rossi
Active Contributor

EDIT January 2025: the author has just replied (comment right after mine) that he was the author of the original blog post in 2016, published elsewhere, so all blog posts from other people (after 2016) are those who did copy his work (with or without authorization).

----

I see that you have reused screenshots (at least) from this blog post by Dharmesh Desai in 2017: SAP S/4 HANA offering SE16H versus SE11/SE16N/SQV... - SAP Community.

It's minimum to ask the author if you can copy the screenshots, and also inform the audience.

Thank you.

Sandra_Rossi
Active Contributor

Thanks for the clarification!

abo
Active Contributor
0 Kudos

Why am I being tagged here?

mwn
Participant
0 Kudos

@abdellah_khebbari sadly, platforms like LinkedIn allow blatant plagiarism, such as you're seeing. Some people even add a watermark with their name. 


soch5584
Explorer
0 Kudos

Hello, 

Thanks for this great post.

A small question please, we realized that when we create a join, it is public, avalable for all the users having access to the SE16H transaction, is there any way to limit the joins by users ?

Thanks & Regards

 

PIERRE_COULLIARD
Newcomer

Thank you Abdellah for this insightful post

0 Kudos

Thank you @PIERRE_COULLIARD for your support !