WBS element 0000 does not exist ; Message no. ABPS021

[former_member191434]

Dear Guru,

I have encountered an issue.

The Issue is like this : I have an ALV report in which I have used 'REUSE_ALV_LIST_DISPLAY' to display the lists .

Usin this report we are finding out lists of WBS elements with respect to Material Doc. Year, Material Doc Number , Posting Date, Movement Type etc in the selection screen field.

Now in the list o/p when i am trying to sort WBS element in ascending or descending order i am not facing any issue .

But in the list o/p when I am trying to search/filtrate a perticular WBS element Using "Set Filter (Ctrl + F5) " button it is giving the following error.

WBS element                     0000 does not exist
Message no. ABPS021

Note: In case of trying to search/filtrate a perticular Material doc num Using "Set Filter (Ctrl + F5) " button in the same report o/p i am not getting any error.

The things I want to know:

1. why this kind of error is coming only for WBS element ??

2. how I should approach to resolve this issue ??

[SuhaSaha]

I will suggest run an ALV consistency check once to check if you have any errors in it. Further details on ALV consistency check read Rainer's blog on the same subject.

BR,

Suhas

PS: I have a notion this has got something to do with the conversion exit associated with WBS element.

[raymond_giuseppi]

To perform [The Consistency Check|http://help.sap.com/saphelp_nw70/helpdata/EN/d6/23253963143e6ae10000000a11402f/content.htm] you will have to use a GRID ALV.

Regards,

Raymond

[former_member191434]

Dear Suhas Da,

I agree with Raymond Giuseppi - that ALV consitency check only possible with ALV grid diplay.

If this error can be sort out using conversion exit then which function module I have to use the convert . Internal and external format for WBS element.

Now How I will Identify whether the WBS elemnt is in internal or External Format..

With addition to this i would like to give some sort of information that for displaying WBS Element I have used MSEG-PS_PSP_PNR (which is N 8 )field to populate it into field catalogue ...

so what might be the issue where we are getting stuck...

please give a guideline to resolve this

Thanks & Regards

Saifur Rahaman

[raymond_giuseppi]

MSEG-PS_PSP_PNR is internal format (Numeric 😎

- Keep this field and insure that fieldcat is correct (eg. EDIT_MASK = "==ABPSN", OUTPUTLEN = 24)

- Use the external format (fill the field with PRPS-POSID or using FM CONVERSION_EXIT_ABPSN_OUTPUT or use a WRITE) (Using this second option will enable use of filter, wildcard, etc.)

Regards,

Raymond

[SuhaSaha]

>

> To perform [The Consistency Check|http://help.sap.com/saphelp_nw70/helpdata/EN/d6/23253963143e6ae10000000a11402f/content.htm] you will have to use a GRID ALV.
> 
> Regards,
> Raymond

I dont think so. If you are using ALV List you can:

1. During the testing phase pass I_CONSISTENCY_CHECK = 'X' to the REUSELISTDISPLAY to check of your field catalog is populated correctly.

2. Else you can initiate a consistency check by typing &SOS in the the command field of the menu bar

Check this blog by Rainer for further details: [/people/rainer.hbenthal/blog/2009/09/25/sos--my-alv-report-is-not-working|/people/rainer.hbenthal/blog/2009/09/25/sos--my-alv-report-is-not-working]

BR,

Suhas

Edited by: Suhas Saha on Mar 29, 2010 7:39 PM

[raymond_giuseppi]

Okay, i learn something today

Regards,

Raymond

[former_member191434]

Dear Suhas Da,

I tried and found we can perform consitency check in ALV list also....

But the thing which Raymond Giuseppi have suggested that we have to perform

- Keep this field and insure that fieldcat is correct (eg. EDIT_MASK = "==ABPSN", OUTPUTLEN = 24)
- Use the external format (fill the field with PRPS-POSID or using FM CONVERSION_EXIT_ABPSN_OUTPUT or use a WRITE) (Using this second option will enable use of filter, wildcard, etc.)

But the thing is like this : I am populating my field catalogue by below way

CALL FUNCTION 'GET_FIELDTAB'
    EXPORTING
      langu               = sy-langu
      tabname             = 'MSEG'
      withtext            = space
    TABLES
      fieldtab            = nametab
    EXCEPTIONS
      internal_error      = 1
      no_texts_found      = 2
      table_has_no_fields = 3
      table_not_activ     = 4
      OTHERS              = 5.

  teller1 = 0.
  LOOP AT nametab.
    teller1 = teller1 + 1.
    CHECK nametab-fieldname <> 'MANDT'.

    PERFORM build_fieldcat USING 'TABELL1' 'MSEG' 1 teller1
                                 nametab-fieldname ' ' 'X' 'X' ' ' ' '.

  ENDLOOP.

Then I am builing layout & then event catlogue and displaying the list by below :

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
      i_callback_program      = repid
      i_callback_user_command = 'USER_COMMAND'
      is_layout               = is_layout
      it_fieldcat             = fieldcat
      it_sort                 = sortcat
      i_save                  = 'A'
    TABLES
      t_outtab                = tabell1
    EXCEPTIONS
      program_error           = 1
      OTHERS                  = 2.

Now my question is if I have to use EDIT_MASK/conversion exit then How and where I will use can you give me a guideline ....

Thanks & Regards

Saifur Rahaman

Edited by: Saifur Rahaman on Mar 29, 2010 8:05 PM

[SuhaSaha]

Well why are you populating the fieldcat this way? You can try creating it using REUSE_ALV_FIELDCATALOG_MERGE to create the fieldcat directly from a DDIC structure.

BR,

Suhas

[raymond_giuseppi]

I agree, use REUSE_ALV_FIELDCATALOG_MERGE which will generate a full correct field catalog.

- Read the documentation of field IT_FIELDCAT which mentions this FM.

- Also check with SE37, GET_FIELDTAB is obsolete, use DDIF_FIELDINFO_GET.

Regards,

Raymond

[former_member191434]

Dear Suhas Da,

Its little difficult to understand the reason why the earlier programmer have used this way rathar than using REUSE_ALV_FIELDCATALOG_MERGE and this coding is running since 2001.

In my point of view the fields we are populating into the o/p of the report not belongs to not only from MSEG, The other fields which is associated to the internal table tabell1 , belongs to from MKPF , LIPS ,LIKP, T001L. and populating the field catalog like above way like what he did for MSEG..

So the concern is now cant we rectify this without using REUSE_ALV_FIELDCATALOG_MERGE.

I have come accross a suggestion there is something i have to do with no_convext in the slis_t_fieldcat_alv rather than using REUSE_ALV_FIELDCATALOG_MERGE.

So can you please give me some guideline how...it will be possible..

Thanks & Regards

Saifur Rahaman

[SuhaSaha]

If you use NO_CONVEXT i think the conversion exit on the field will be suppressed. As already discussed the error may be becuase of the conversion exit associated with the WBS element.

During debug can you check what is the value in the fieldcatalog for the WBS element & post it here ?

BR,

Suhas

[former_member191434]

Dear Suhas Da,

With ref to your previous suggestion i would like add my some more finding....

I am getting this error in only Quality & Development Server not in the sandbox server....

In sandbox server this wbs element is getting filtrate properly without any error....

Can you put some lights on this issue ...

Thanks & regards

Saifur Rahaman

[former_member191434]

Hi ,,

Is there any possibility that due to upgradation of system landscape from 4.7 to ecc6...this kind of situation is arising ??

Thanks & regards

Saifur Rahaman

[raymond_giuseppi]

Try to run report BALVBUFDEL and execute your report once again.

Regards,

Raymond

[former_member191434]

Dear Raymond Giuseppi

I have executed the report u have suggested then I executed my report...

the issue is still arising.....

Is there any other way of resolving this issue ...

Thanks & regards

Saifur

[raymond_giuseppi]

Did you execute the refresh ALV buffer in every system, if yes did you now get the problem in all systems or only some ?

Regards,

Raymond

[former_member191434]

Dear Raymond ,

I executed refresh ALV Buffer in only quality system....where the issue i am facing....

then i logged off and again logged in in Quality then I executed the ALV report....

Thanks & Regards

Saifur Rahaman

Edited by: Saifur Rahaman on Mar 31, 2010 5:08 PM

[raymond_giuseppi]

Did you use the internal or external format of WBS in your internal table, there seems to be a conversion problem. If internal format is stored, did you fill correctly the field catalog ?

Regards,

Raymond

[former_member191434]

Dear Raymond Giuseppi ,

While in dubbing this ALV list report I found that the WBS elementes are coming only numeric with compare to those WBS which are all coming alpha numeric in the o/p of the report...

some WBS are 20 chr long some are 16 and some are 14.... but all are alpha numeric in the o/p

[former_member191434]

still not got the soln