Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
jogeswararao_kavala
Active Contributor

Introduction

The way several features including coding in Extras of Infoset takes the work closer to an ABAP development, another function Alias in the Table-join screen also increases the versatility of an Infoset (SQ02) or a  Quick View (SQVI)


Objective:

To understand the concept of Alias Tables in Infosets and Quick Views, through a Demo application.

Demo Situation:

We have a task of developing, a report through Infoset or a Quick View, to display Notification details and corresponding Object part and Damage Codes details.

So the ALV we need will have these columns:




Let’s see how we do it.

Obviously the two tables we need are:

  1. VIQMEL  - For Notification Details
  2. VIQMFE - For Object Part, Damage Details.

But

In VIQMFE table, we do not have the Code texts (field name kurztext). These fields are shown in Red in the 1st picture.  QPCT is the table we need to join to get this field value. Let’s take this into our join.

Then, What’s the problem ?

As per the join shown above we are getting kurztext (Damage Code Text) for Damage Code (FECOD) only.

What about the kurztext for Object Part Code (oteil).

To get this too, we need to have one more QPCT table into the join. But system does not allow this.


So what do we do?

Here comes  the use of the Alias Table.

We now need to create an alias table identical to QPCT (say QPCT1)

Follow the steps shown in the picture.

Now you have the desired table for you. Take this table too into the join.

Remember, system can not propose the right links for the join. You need to know this and Join Manually.

All done regarding the Alias Table.

Now you have your Selection-screen and List fields in QuickView (in case of Infoset make the Query through SQ01).

The Result is:

We find here the desired output with Code Texts also filled.

NOTE:

This is a simple case to demo the Alias tables. This feature has a big advantage during complex works of Infoset / Quick View.

The absence of Extras  facility in SQVI, makes this Alias feature more relevant to a Quick View work.

In infoset, this Alias feature can be substituted by Extras Add Table, Add field and Code functionalities.

Hope Infoset / Quick Viewer users find this useful.

The environment of this document is ECC6.0 no EHPs.

Readers might be interested in these posts also:

10 Useful Tips on Infoset Queries

Infoset Queries: Collection of important posts

Thank you

Jogeswara Rao K

27 Comments
Labels in this area