Skip to Content

Issue with displaying a view table V_T352R

Hi,

I try to see the contents of a view table V_T352R, its dumping.

I try to implement SAP note 653597, which needs a line to be added in this view.

How to solve this.

Cheers

Senthil

Edited by: Senthil on May 14, 2008 10:20 AM

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on May 14, 2008 at 09:01 AM

    Hi,

    What does the dump say. I am able to view the contents of this view we are on 4.6C

    Rgds,

    HR

    Add a comment
    10|10000 characters needed characters exceeded

    • Here is the dump message.

      Runtime Errors PERFORM_NOT_FOUND

      Except. CX_SY_DYN_CALL_ILLEGAL_FORM

      Date and Time 14.05.2008 16:41:39

      -


      -


      Short text

      Call (PERFORM) to a non-existent routine.

      -


      -


      What happened?

      There exist various options:

      Error in the ABAP Application Program

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

      come across a statement that unfortunately cannot be executed.

      or

      Error in the SAP kernel.

      The current ABAP "SAPL0I05" program had to be terminated because the

      ABAP processor detected an internal system error.

      -


      -


      What can you do?

      Note down which actions and inputs caused the error.

      To process the problem further, contact you SAP system

      administrator.

      Using Transaction ST22 for ABAP Dump Analysis, you can look

      at and manage termination messages, and you can also

      keep them for a long time.

      -


      -


      Error analysis

      An exception occurred that is explained in detail below.

      The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FORM', was

      not caught in

      procedure "VIEWPROC_V_T352R" "(FUNCTION)", nor was it propagated by a RAISING

      clause.

      Since the caller of the procedure could not have anticipated that the

      exception would occur, the current program is terminated.

      The reason for the exception is:

      The program "SAPL0I05" is meant to execute an external PERFORM,

      namely the routine "DIWPS_MEB_CHECK " of the program "SAPL0I05", but

      this routine does not exist.

      This may be due to any of the following reasons:

      1. One of the programs "SAPL0I05" or "SAPL0I05" is currently being developed.

      The name "DIWPS_MEB_CHECK " of the called routine may be incorrect, or

      the routine "DIWPS_MEB_CHECK " is not yet implemented in the program

      "SAPL0I05".

      -

      2. If the program SAPMSSY1 is involved in the runtime error, one of

      the function modules called via RFC is not flagged as remote-capable.

      (see Transaction SE37 Goto -> Administration -> RFC flag)

      3. There is an inconsistency in the system. The versions of the

      programs "SAPL0I05" and "SAPL0I05" do not match.

      -


      -


      How to correct the error

      - Check that transports to the system are complete.

      - Conclude any developments already begun ("SAPL0I05" and/or "SAPL0I05").

      - Check routine names

      If the error occures in a non-modified SAP program, you may be able to

      find an interim solution in an SAP Note.

      If you have access to SAP Notes, carry out a search with the following

      keywords:

      "PERFORM_NOT_FOUND" "CX_SY_DYN_CALL_ILLEGAL_FORM"

      "SAPL0I05" or "L0I05U10"

      "VIEWPROC_V_T352R"

      If you cannot solve the problem yourself and want to send an error

      notification to SAP, include the following information:

      1. The description of the current problem (short dump)

      To save the description, choose "System->List->Save->Local File

      (Unconverted)".

      2. Corresponding system log

      Display the system log by calling transaction SM21.

      Restrict the time interval to 10 minutes before and five minutes

      after the short dump. Then choose "System->List->Save->Local File

      (Unconverted)".

      3. If the problem occurs in a problem of your own or a modified SAP

      program: The source code of the program

      In the editor, choose "Utilities->More

      Utilities->Upload/Download->Download".

      4. Details about the conditions under which the error occurred or which

      actions and input led to the error.

      The exception must either be prevented, caught within proedure

      "VIEWPROC_V_T352R" "(FUNCTION)", or its possible occurrence must be declared in

      the

      RAISING clause of the procedure.

      To prevent the exception, note the following:

      -


      -


      System environment

      SAP-Release 700

      Application server... "dcrntsp021"

      Network address...... "10.254.1.21"

      Operating system..... "Windows NT"

      Release.............. "5.2"

      Hardware type........ "16x AMD64 Level"

      Character length.... 8 Bits

      Pointer length....... 64 Bits

      Work process number.. 3

      Shortdump setting.... "full"

      Database server... "DCRNTSP022\DEV"

      Database type..... "MSSQL"

      Database name..... "DEV"

      Database user ID.. "dev"

      Char.set.... "English_United State"

      SAP kernel....... 700

      created (date)... "Mar 19 2008 22:07:01"

      create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

      Database version. "SQL_Server_8.00 "

      Patch level. 152

      Patch text.. " "

      Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

      SAP database version. 700

      Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

      NT 6.0"

      Memory consumption

      Roll.... 16128

      EM...... 8379808

      Heap.... 0

      Page.... 32768

      MM Used. 1486992

      MM Free. 2700352

      -


      -


      User and Transaction

      Client.............. 500

      User................ "SKUMAR"

      Language key........ "E"

      Transaction......... "SM30 "

      Transactions ID..... "7E8E21DD68C1F1459A8E00145E7A9718"

      Program............. "SAPL0I05"

      Screen.............. "SAPMSVMA 0100"

      Screen line......... 19

      -


      -


      Information on where terminated

      Termination occurred in the ABAP program "SAPL0I05" - in "VIEWPROC_V_T352R".

      The main program was "SAPMSVMA ".

      In the source code you have the termination point in line 26

      of the (Include) program "L0I05U10".

      The termination is caused because exception "CX_SY_DYN_CALL_ILLEGAL_FORM"

      occurred in

      procedure "VIEWPROC_V_T352R" "(FUNCTION)", but it was neither handled locally

      nor declared

      in the RAISING clause of its signature.

      The procedure is in program "SAPL0I05 "; its source code begins in line

      5 of the (Include program "L0I05U10 ".

      -


      -


      Source Code Extract

      -


      Line

      SourceCde

      -


      1

      ----


      2

      • program for: VIEWPROC_V_T352R

      3

      • generation date: 21.02.1995 at 09:39:54 by user SKIERA

      4

      ----


      5

      FUNCTION VIEWPROC_V_T352R .

      6

      ----


      7

      • Initialization: set field-symbols etc. *

      8

      ----


      9

      IF LAST_VIEW_INFO NE VIEW_NAME.

      10

      ASSIGN V_T352R TO <TABLE1>.

      11

      ASSIGN *V_T352R TO <INITIAL>.

      12

      ASSIGN STATUS_V_T352R TO <STATUS>.

      13

      PERFORM INITIALISIEREN.

      14

      ENDIF.

      15

      PERFORM JUSTIFY_ACTION_MODE.

      16

      MOVE: VIEW_ACTION TO MAINT_MODE,

      17

      CORR_NUMBER TO CORR_NBR.

      18

      19

      ----


      20

      • Get data from database *

      21

      ----


      22

      IF FCODE EQ READ OR FCODE EQ READ_AND_EDIT.

      23

      PERFORM PREPARE_READ_REQUEST.

      24

      IF X_HEADER-FRM_RP_GET NE SPACE.

      25

      PERFORM (X_HEADER-FRM_RP_GET) IN PROGRAM SAPL0I05.

      >>>>>

      ELSE.

      27

      PERFORM GET_DATA_V_T352R.

      28

      ENDIF.

      29

      IF FCODE EQ READ_AND_EDIT. FCODE = EDIT. ENDIF.

      30

      ENDIF.

      31

      32

      CASE FCODE.

      33

      WHEN EDIT. " Edit read data

      34

      PERFORM CALL_DYNPRO.

      35

      PERFORM CHECK_UPD.

      36

      ....................................................................

      37

      38

      WHEN SAVE. " Write data into database

      39

      PERFORM PREPARE_SAVING.

      40

      IF <STATUS>-UPD_FLAG NE SPACE.

      41

      IF X_HEADER-FRM_RP_UPD NE SPACE.

      42

      PERFORM (X_HEADER-FRM_RP_UPD) IN PROGRAM.

      43

      ELSE.

      44

      IF SY-SUBRC EQ 0.

      45

      PERFORM DB_UPD_V_T352R.

      -


  • author's profile photo Former Member
    Former Member
    Posted on Oct 22, 2009 at 03:35 PM

    How did you solve your issue ?

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 10, 2010 at 07:55 AM

    Hi Senthil,

    I am facing same issue. Can you please let me know how did you resolve this issue.

    Thanks in advance for your respnose.

    Regards,

    Magadi

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 25, 2013 at 03:55 AM

    Hi

    Any one know solution of OIOB dump problem as mention by senthil

    thanks

    Ajay

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.