Skip to Content

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.

/wp-content/uploads/2014/02/0_382874.jpg

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.

1.JPG

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.

3a.JPG


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.

2.JPG

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

3.JPG

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:

4.JPG

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

To report this post you need to login first.

27 Comments

You must be Logged on to comment or reply to a post.

  1. Sorin Camner

    Dear Jogeswara,

    You are of great help and you deserve a big thanks. I don’t know how to congratulate you. Thank you very much for all your work.

    Sorin

    (0) 
    1. K Jogeswara Rao Post author

      Dear Sorin,

      These words of yours itself, are big rewards for these works.

      These are real inspirations which make me contribute more and more like this.

      Regards

      Jogeswara Rao K

      (0) 
  2. Patrick S.

    Dear Jogeswara,

    WOW.. very nice workaround to overcome the SQVI boundaries with unallowed joins!

    I was not aware about the option of “alias-tables” and work with a duplicate.

    Thanks for sharing your knowledge – very useful guideline!

    Regards,

    Patrick

    (0) 
  3. Akhilesh Singh

    Hi Jogeswara,

                            This very useful functionalities for functional guy’s.

    Lot’s of thanks for sharing this such kind of documents. 

    (0) 
  4. SAP WARRIOR

    Hi Jogeshwar

    Nice Document as it give me a way to come out of problem as We are pulling BOM Data with the help of SQVI. Header material description we are not able to pull as MAKT table is being used to pull components material description.

    (0) 
  5. Astrid Gambill

    Hi Jogeswara Rao K

    I’m trying to use this ALIAS functionality and I can create an entry in the pop-up per your guidelines, but then that 2nd version of the table isn’t displaying in the Join screen.

    We just upgraded to ERP 6.0 Ehp7 SP3.  Did something get broken?

    Thanks

    Astrid

    (0) 
    1. K Jogeswara Rao Post author

      Is it the case? Can you detail which tables you are trying? Also you may try with above example to confirm whether it is due to Enhanced version. Mine is ECC6.0 no EHPs.

      (0) 
    2. K Jogeswara Rao Post author

      Hi Astrid,

      Sorry, I did not understand your first post properly, I’ve just re-read and understood. Looks something to do with Enhanced version.  You may contact SAP (OSS),  after confirming that it is so.

      Regards

      Jogeswara Rao K

      (0) 

Comments are closed.