ABAP program error in the standard ABAP program

[Former Member]

Hello, the Guru!!!

Help to solve the incorrect situation connected to a ABAP program error in system SAP BW (the Version of components of system SAP_BASIS and SAP_BW - 702).

The incorrect situation consists in the following. I needed to analyse contents PSA of the table of a Datasource "2LIS_02_SCL".

In transactions "RSA1" has gone to a bookmark "DataSources", has selected a datasource "2LIS_02_SCL" and has chosen from the contextual menu "Manage".

I has chosen required request and has pressed button "PSA-Maintenance".

In a window "PSA-Maintenance" I have selected a required data package and have pressed button "Continue".

Usually on pressing button "Continue" the system showed contents of the chosen data package in format ALV.

In my case I have received ABAP Dump:

Category               ABAP Programming Error

Runtime Errors         GETWA_NOT_ASSIGNED

ABAP Program           SAPLSLVC

Application Component  BC-SRV-ALV

Date and Time          30.05.2012 09:10:24

Short text

    Field symbol has not yet been assigned.

What happened?

    Error in the ABAP Application Program

    The current ABAP program "SAPLSLVC" had to be terminated because it has

    come across a statement that unfortunately cannot be executed.

Trigger Location of Runtime Error

    Program                                 SAPLSLVC

    Include                                 LSLVCF36

    Row                                     3.273

    Module type                             (FORM)

    Module Name                             FILL_DATA_TABLE

I have tried to look for notes on elimination above specified ABAP Programming Error.

I have found some notes, but all of them refer to support packages which are already installed in our system BW.

Now at us following last packages of support in system BW are installed:

SAP_BASIS: SAPKB70211;

SAP_BW: SAPKW70211.

Please state your ideas on higher to the described situation for reception of the decision. May be somebody already has the same situation and you have already found the decision, have found the note.

In a case if who that has already found the note then write me please the note.

Best regards,

Sergey.

[former_member188080 · Accepted solution]

Hi,

Just go to RSRV transaction and carry out PSA table checks..

try to repair it if there is any error..

also check for replication of datasource and try to reactivate it one more time..

RSDS_DATASOURCE_ACTIVATE_ALL ..TRY this and then try continuing ur activity..

Thanks and regards

Kiran

[Former Member · Accepted solution]

Hi,Kiran.

I have executed repeated replication of datasource and reactivate it

with help RSDS_DATASOURCE_ACTIVATE_ALL. All became good.

Many thanks, Kiran.

[former_member545416]

guys i`m trying to run fbl3n std t-code but it says the below error, so what i`m suppose to do ?

plz help.THANK YOU !!!

-------------------------------------------------------------------------------------------------------------------------------

Short text

    Time limit exceeded.

What happened?

    The program "SAPDBSDF" has exceeded the maximum permitted runtime without

    interruption and has therefore been terminated.

Error analysis

    After a specific time, the program is terminated to make the work area

    available to other users who may be waiting.

    This is to prevent a work area being blocked unnecessarily long by, for

    example:

    - Endless loops (DO, WHILE, ...),

    - Database accesses with a large result set

    - Database accesses without a suitable index (full table scan)

    The maximum runtime of a program is limited by the system profile

    parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this

     time limit is

    exceeded, the system attempts to cancel any running SQL statement or

    signals the ABAP processor to stop the running program. Then the system

    waits another 60 seconds maximum. If the program is then still active,

    the work process is restarted.

Trigger Location of Runtime Error

    Program                                 SAPDBSDF

    Include                                 SAPDBSDF

    Row                                     1,675

    Module type                             (FORM)

    Module Name                             PUT_BSIS

Source Code Extract

Line  SourceCde

1645 EXIT.

1646 ENDIF.

1647

1648 if sd_usear is initial and sd_usedb is initial.

1649 sd_usedb = 'X'.

1650 endif.

1651 if sd_usear = 'X'.

1652 IF gd_arch_done EQ 'N'.

1653 PERFORM read_archive.

1654 gd_arch_done = 'Y'.

1655 gd_read_memo_done = 'N'.

1656 ENDIF.

1657 IF NOT ybsas[] IS INITIAL.

1658       LOOP AT ybsas  INTO bsis                              "#EC ENHOK

1659                     WHERE hkont = save_saknr

1660                       AND bukrs = save_bukrs.

1661 ld_arch = 'X'.

1662 PERFORM process_bsis USING ld_arch.

1663 ENDLOOP.

1664 ENDIF.

1665 ENDIF.

1666

1667 IF NOT sd_usedb IS INITIAL.

1668 if B0SG-XSTAN = 'X' or B0SG-XSTAS = 'X'. ">>>> normal documents >>>>>

1669 SAVE_BSTAT = ' '.

1670 *----------------------------------------------------------------------*

1671 * 1 Variante: Es sind offene Posten zu einem bestimmten Stichtag      *

1672 *              gewuenscht.                                             *

1673 *----------------------------------------------------------------------*

1674 if SD_OPOPT eq 'X' and SD_APOPT ne 'X'.

>>>>>         select (BSIS_FIELDS) from BSIS into corresponding fields of BSIS

1676                           where BUKRS eq SAVE_BUKRS

1677                           and   HKONT eq SAVE_SAKNR

1678 *                     AND   GJAHR IN SD_GJAHR

1679                           and   BUDAT in SD_BUDAT

1680                           and   BUDAT le SD_STIDA

1681                           and   ZUONR in SD_ZUONR

1682                           and   GSBER in SD_GSBER

1683 *                     and   blart in sd_blart            "<<<< au40

1684                           and   VBUND in SD_VBUND

1685                           and   BSCHL in SD_BSCHL

1686                           and   KOSTL in SD_KOSTL

1687                           and   WERKS in SD_WERKS

1688                           and   SHKZG in SD_SHKZG

1689                           and   (BSIS_WHERE).

1690

1691 CLEAR ld_arch.

1692 PERFORM process_bsis USING ld_arch.

1693

1694 endselect.

[shalaka_golde]

Hi,

Please do a st05 trace of fbl3n and then find out which statement is taking a long time to execute and performance tune it.Some indexes may have got deleted or deactivated.

Regards,

Shalaka

[former_member545416]

Thank you so much shalaka,

i later got to know that there were no entries in any of the G/L accounts..

[shanthi_bhaskar]

Upgrade your GUI to latest version and some times rebooting system might work.

[former_member186491]

Hi Sergey,

Error "Runtime Errors         GETWA_NOT_ASSIGNED " comes when Fieldcatalog to display the ALV has not been defined correctly or not defined at all.

Please check -

  1.) whether Fieldcatalog is defined or not,

  2.) If Defined, check if all Field-Names are passed correctly to the fieldcatalog - mind spellings of field-names to avoid typo-error.

This way you can correct your problem.

Thanks.

Kumar Saurav.

[Former Member]

Hi Kumar Saurav,

I am confused with that Fieldcatalog is defined not in mine ABAP program. Fieldcatalog is defined in standard ABAP program which has been generated SAP. ABAP error arises, when I try to execute standard function «PSA-Maintenance» (Viewing of contents PSA of the table).

To me it is not clear, that will give me the analysis of definition Fieldcatalog in standard ABAPprogram. I did not develop standard function « PSA-Maintenance ». If I shall find a error in definition Fieldcatalog in standard ABAP program then as I can correct error in standard ABAP program. I think this incorrect situation it is possible to remove only installation SAP note.

Or I am mistaken? If I am mistaken please specify, what I should do if I shall find a mistake in definition Fieldcatalog in standard ABAP program?

Best regards,

Sergey.

[former_member186491]

Hi Sergey,

I believe that there won't be such things required because, you have written that you have already checked the relevent SAP Notes are applied in the system -

I have found some notes, but all of them refer to support packages which are already installed in our system BW.

At this point of time, can you please see if Data Source is Activated or not?

I'd suggest to do activate the DataSource and then run it again.

I'd insist that this is simple Fieldcatalog error and this can again happen if the data is not getting passed to the Fieldcatalog.

As you are saying that this is being done in Standard Part of the codes, you can then check the DataSource Activation itself.

Thanks.

[Former Member]

Thank you Saurav.

Reagrds,

Raju K. Rao