Short dump error DBIF_RSQL_TABLE_UNKNOWN

Hi Experts,
We are using a job having program "ATPBD001" to Refresh the buffer. Yesterday this job failed with the short dump error
DBIF_RSQL_TABLE_UNKNOWN.
The message is coming like " One of the tables in the statement accessing table "ATP_RESB " is unknown ".
Today the same job run successfully. what could be the possible root cause of the error ?
Here is the source code for reference :
004370                     atp_resb-sobkz = sobkzk
004380   *}   INSERT
004390               CLEAR atp_resb-sobkz.
004400   *           checks
004410               resb_check atp_resb
004420                          p_atpmex.
004430             ENDSELECT.
004440           ENDIF. " IF NOT g_t441v-skbdp IS
004450
004460         ENDIF. " IF s_index_flg = swoff.
004470       ELSE.
004480         SELECT *
004490         FROM   atp_resb
004500         INTO   atp_resb
004510         WHERE matnr = atpmat-matnr
004520         AND    werks = atpmat-werks
004530         AND    xloek = space
004540         AND    kzear = space
004550   *{   REPLACE        PA8K040916
004560   *\      AND    sobkz IN (space, sobkzk)
004570   *XFO 16.12.2005 H908220 wrong ATP for spe
004580   *(del)      AND    sobkz IN (space, sobkz
004590   *}   REPLACE
004600         AND    bdmng > atp_resb~enmng
004610         AND    txtps = space
004620         AND    schgt = space
004630         AND    dbskz = space
004640         AND ( vorab IS NULL
>             OR vorab = space ).
004660   *{   INSERT         PA8K040916

Check noe 950317.
rob

Similar Messages

Short dump error report

What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani

Short Dump Error

Hi Everyone,
I'm loading 690k odd records to cube
I am facing short dump error while data request is processed to cube.
In ST22 i'm getting Timeout Error.
Buffer time is set for 10mins to process
Can anyone guide me in this issue.
Thanks in advance

Hi,
Due to data volume your load took more than 7hrs. in general time out time is 7hrs. so in your case its may exceeded.
Try to increase time out time for your info package.
Go to your info pack--> menu scheduler --> time out time--> increase 7 hrs to 14hrs and trigger your load again. if its full load delete failed load and retrigger.
Thanks

Short dump error when using count(*)

Hi Experts
I am getting a short dump error when selecting the records >= current date - 30 see the coding and comment please correct the coding I want to know the ztable records it is important for command interface.
I have 1402345 records available after deleting the records but as the memory is not enough it is giving short dump error
select count(*) from ZINT_TABLE
select count(*) from ZINT_MSGS
   select * from zint_data
             nto table izint_d2 . "PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.**
report z_eslp_command_records.
data: cnt type i.
data: cnt2 type i.
data: cnt3 type i.
data: cnt4 type i.
DATA:
     w_date1 like sy-datum .
DATA:
     w_date2 like sy-datum.
data: izint_msgs type table of zint_msgs.
data: izint_data type table of zint_data.
data: izint_m2 type table of zint_msgs.
data: izint_d2 type table of zint_data.
INITIALIZATION.
w_date1 = sy-datum - 30.
w_date2 = sy-datum - 30.
select * from zint_data
             into table izint_data PACKAGE SIZE 3000
             where STATUS = 'OK' AND CREATED_ON <= w_date1.   " ZERO
endselect.
select * from zint_msgs
             into table izint_msgs PACKAGE SIZE 3000
              where CREATED_ON <= w_date2.              " ZERO
endselect.
select * from zint_data
             into table izint_d2 PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.
select * from zint_msgs
             into table izint_m2 PACKAGE SIZE 20000
where CREATED_ON >= w_date2.                            " VALUE
endselect.
select * from zint_data
            into table izint_data2
where STATUS = 'OK' AND CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
select * from zint_msgs
            into table izint_msgs2
where CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
sort izint_data by created_on ascending.
sort izint_msgs by created_on ascending.
sort izint_d2 by created_on ascending.
sort izint_m2 by created_on ascending.
describe table izint_data lines cnt.
describe table izint_msgs lines cnt2.
describe table izint_d2 lines cnt3.
describe table izint_m2 lines cnt4.
write:/ ' Note: THE RECORDS COUNTED SHOULD SHOW ZERO ELSE THE SCRIPT FAILED TO RUN' color 3.
skip.
write:/ '1. Records counted in ZINT_DATA   <=current date - 30                   :' color 2,                        cnt color 4.
write:/ '2. Records available in ZINT_DATA >=current date - 30                   'color 4,                   cnt3 color 4 .
skip.
write:/ '2. Records counted in ZINT_MSGS   <=current date - 30                   :' color 2                 ,                      cnt2 color 4.
write:/ '4. Records available in ZINT_MSGS >=current date - 30                   'color 4 ,            cnt4 color 4 .
TOP-OF-PAGE.
WRITE:/55(60) ' WAGNERS INVESTMENT LIMITED '.
WRITE:/50(40) ' Command Interface Data' CENTERED .
WRITE:/50(40) '----
' CENTERED .
FORMAT INTENSIFIED ON.
SKIP.
"FORMAT COLOR COL_HEADING.
ULINE.
FORMAT COLOR 1.
END-OF-PAGE.

Answer

Short Dump error while loading data from R/3 to ODS

Hello,
while trying to load data into the ODS from R/3 I get the following short dump error message. How do I carry out step 1 in the below procedure. Where do i find the Activate Function. And idea?
Thanks,
SD
                                                                                Diagnosis
Form routine CONVERT_ITAB_RFC is incorrect in transfer program
     GP4C0LOLZ6OQ70V8JR365GWNW3K .
System Response
The IDoc processing was terminated and indicated as incorrect. The IDoc
     can be reimported at any time.
Procedure
1. Go to the transfer rule maintenance for your InfoSource
         ZFIN_TR_FLQITEM_FI and the source system DA_M_10 and regenerate the
         transfer program using the function Activate. Remove possible syntax
         errors on the basis of your conversion routines.
2. Restart the processing of this IDoc.
3. If the error occurs again search for SAPNet R/3 notes, and create a
        problem message if necessary.
Edited by: Sebastian D'Souza on Jan 13, 2009 3:22 PM

Hi.......
Goto RSA1>> then to source system tab (on left side) >> double click on the desired source system...........Then on the right side you have the Datasource tree..........there search the datasource and activate.......Also u can Replicate the datasource again.......and activate the Transfer rules using the program : RS_TRANSTRU_ACTIVATE_ALL
After this operation when come back to source system (R/3).........I think the error log line will be disappeared from SM58......... Then repeat the load.........
Also u can try to Activate the infosource once...........in RSA1.........before repeating the load....
Hope this helps......
Regards,
Debjani....

Short dump Error in BAPI_BUS2054_SET_STATUS

I am trying to set status of wbs element and have the following sequence of calls based on the
Error in BAPI_BUS2054_SET_STATUS
CALL FUNCTION 'BAPI_PS_INITIALIZATION' .
CALL FUNCTION 'BAPI_PS_PRECOMMIT'
TABLES
et_return = it_bapiret.
CALL FUNCTION 'BAPI_BUS2054_SET_STATUS'
IMPORTING
return = l_return
TABLES
i_wbs_user_status = it_wbs_user_status
e_result = lt_e_result.
IF l_return-type EQ 'E'.
gv_flg_error = 'X'.
ENDIF.
CALL FUNCTION 'BAPI_PS_PRECOMMIT'
TABLES
et_return = it_bapiret.
READ TABLE it_bapiret INTO it_bapiret WITH KEY type = 'E'.
IF sy-subrc = 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
ENDIF.
I am still getting the short dump :
Error analysis
    Short text of error message:
    Precommit did not run successfully
Information on where terminated
    Termination occurred in the ABAP program "SAPLPS_BAPI" - in "CHK_PRECOMMIT".
    The main program was "RS_TESTFRAME_CALL ".
In the source code you have the termination point in line 24
    of the (Include) program "LPS_BAPIF01".
Any help to make this work is appreciated.

suzzie
you are always calling precommit after set_status.you should call only if set_status is successfull.
This is how we are calling for network status.
        call function 'BAPI_PS_INITIALIZATION'.
        call function 'BAPI_BUS2002_SET_STATUS'
          exporting
            number                   = network
          tables
            i_activity_system_status = it
            e_result                 = itet.
        read table itet into wa_itet with key message_type = 'E'.
        if sy-subrc ne 0.
          call function 'BAPI_PS_PRECOMMIT'
            tables
              et_return = etit.
          call function 'BAPI_TRANSACTION_COMMIT'
            exporting
              wait = 'X'.
        else.
         MOVE wa_itet-message_text TO wa_error_tab-message_text.
         wa_error_tab-key1 = network.
         wa_error_tab-key2 = wa_itet-objectkey+12(4).
         wa_error_tab-object_type = c_activity.
         APPEND wa_error_tab TO e_error_tab.
        endif.

Short dump error when extracting delta records from R/3

I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
Below is the error message
Kindly do the needful ASAP.
Job started
Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0ISCM_PAYMENT_01
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 2000000000                              *
abap/heap_area_total.......... 2000000000                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled

Hi,
I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
Another option is to look at OSS notes, because the error is giving you a standard extractor.
Greetings,

Short Dump Error While Data load

Hi Experts,
Data load to an ODS in production server has been failed because of Short dump error. The error message shows " OBJECTS_OBJREF_NOT_ASSIGNED ".
Request you to please help me out with a solution ..
Regards,
Vijay

Hi Vijay,
follow the steps below (May Help you)
Goto Monitor screen>Status Tab> using the wizard or the menu path >Environment -> Short dump> In the warehouse
Select the Error and double click
Analyse the error from the message.
1.-->Go to Monitor
-->Transactional RFC
-->In the Warehouse
-->Execute
-->EDIT
-->Execute LUW
Refresh the Transactional RFC screen and go to the Data Target(s) which have failed and see the status of the Request-->Now it should be green.
2.In some cases the above process will not work (where the Bad requests still exists after the above procedure).
In that case we need to go to the Data Targets and need to delete the bad requests and do the update again
Regards,
BH

Short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow

hi all,
i am getting short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow.
not able to figure out the actual issue and how to solve it.
can anyone suggest?
below is the details of the short dump
Short text
    Exception condition "UNKNOWN_TRANSCAT" raised.
What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
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
    A RAISE statement in the program "CL_SERVICE_TRG================CP" raised the
     exception
    condition "UNKNOWN_TRANSCAT".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
How to correct the error
    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:
    "RAISE_EXCEPTION" " "
    "CL_SERVICE_TRG================CP" or "CL_SERVICE_TRG================CM003"
    "SORT_TRANSACTIONS"
    or
    "CL_SERVICE_TRG================CP" "UNKNOWN_TRANSCAT"
    or
    "SBIE0001 " "UNKNOWN_TRANSCAT"
    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.

Hi,
It seems like some routine are there and check your rotines , transformation etc.
Regards
sivaraju

Short Dump Error DBIF_DSQL2_SQL_ERROR

Hi All,
I am getting a Short dump error DBIF_DSQL2_SQL_ERROR when I try to selectively delete the contents of an infocube. Now, we have a custom program that does this selective deletion. I had no problem when I ran this program in Development system. But when I try to do the same in Testing system, I get a short dump error.
Additional info: We have DB2 for database.
Thanks,
Ashmith Roy

Hi All,
Thanks for your input. The exact error I am getting is in as follows:
Runtime Error          DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
An SQL error occurred when executing Native SQL.
Error "-199" occurred in the current database connection "DEFAULT".
How to correct the error
     Database error text........: "[IBM][CLI Driver][DB2] DSNT408I SQLCODE = -199,
      ERROR: ILLEGAL USE OF KEYWORD FETCH. TOKEN WAS EXPECTED DSNT418I SQLSTATE =
      42601 SQLSTATE RETURN CODE "
     Database error code .......: "-199"
     Triggering SQL statement...: "FETCH NEXT "
     Internal call code.........: "[DBDS/NEW DSQL]"
     Please check the entries in the system log (Transaction SM21).
Information on where terminated
The termination occurred in the ABAP program "GP41YKV36E6C2VFC36AKSJQXCD3" in
      "COUNT".
The termination occurred in line 0 of the source code of the (Include)
program " "
of the source code of program " " (when calling the editor 00).
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "COUNT" "(FORM)" but was not handled locally, not declared in the
RAISING clause of the procedure.
The procedure is in the program "GP41YKV36E6C2VFC36AKSJQXCD3 ". Its source code
starts in line 0
of the (Include) program "???".
So could you please advise as to how to correct the error?
Ashmith Roy

Short dump error with InfoSource

Hi All,
When i try to open Accounts Payable Infosource in BW production, It is returning with the short dump error ' Assertion was violated'.
R_AWBOBJ ->. may I know what is this error.
I created generic datasource in ECC DEV and replicated into BW DEV system, After that I created necessary infoobjects, infosource, transformations, ODS, DTP, InfoPackage and loaded data into it under Accounte Payable in BW DEV. Everything was fine, So I released every object into production successfully.
I asked our network guy to move them into production, When he try to move them they are returning with the errors. Which doesn't happen before. Is this anything effected with the existed AP infosource in production as i explained above error? But still these are not moved into production.I released generic datasource from ECC DEV to ECC PRD.
Data loading was stopped for Line Items DSO under Accounts Payable, Because of these process chains were failed.
Please let me know where i did wrong or what steps i have to follow further. We are on BI7.0 systems.
We recently installed our BI systems.
Please help me anyone ASAP, I appreciated any help.
Thanks,
Aparna.

HI,
If I can understand properly the infosource is the generated object from DSO begnining with 8*? updating AP DSO?
Or it is the self created infsource updating the AP DSO??
What I can understand is you already had a flow in production which was working fine.
Then you did some development inculding a new DSO...this new DSO contained some infoobject fields common with the already live AP DSO in production.
new DSO transport failed in production and becasue of which the data loads to the old AP DSO in production has stopped.
The issue could be that since the transport failed... these infoobjects are into incosistent state.
check these common infoobjects in prodution first.
All I can suggest is transport the DSO again production for AP DSO so that its in consistent state along with the infoobjects.
The infoobjects must be consistent for the DSO, generated data source and infosource to work properly.
Eeen if the infosource is generated one( 8*XXXXXX) transport the respective DSO again in production along with required infoobjects.
Transport the cutomized infosource as well if created.
Thanks
Ajeet

ABAP short dump error while creating an invoice

Hi All,
We are creating a delivery(Unit is EA) for the material for which the Unit Conversion is maintained as 1CS = 48 EA. So while creating a delivery If I maintain the delivered quantity is less than 24, I am not able to create an invoice.It's throwing an ABAP short dump error BCD zerodivide run time error.
If I deliver greater than or equal to 24, then the invoice is created without any issue
I have checked if there is any CMIR record but no record is maintained.
Can anyone help me out on this?
Regards,
Manjunath

Hi Manju,
Can you post the dump screen shot, which should contain the source code for that dump.
Regards,
Krishna

Short dump errors desc--how to resolve

I would like to know the short dump errors meaning and how to resolve it. i have the following errors
1. TSV_TNEW_PAGE_ALLOC_FAILE----
for this the description for ERROR ANALYSIS is : The internal table "IT_24" could not be enlarged further. To allow error handling, the table has to be deleted before this log was created.HOW TO CORRECT THE ERROR is : the amount of storage space was (in bytes) filled at termination time was:
Roll area..........1708928
Extended memory (EM).........440057520
Assigned memory (HEAP).......465813648
short area.........." "
Paging area.....33857536
Maximum address space....." "
2. DBIF_DSQL2_SQL_ERROR----
HOW TO CORRECT THE ERROR is:
Database error text......."ORA-01555: snapshot too old: rollback segment number 2 with name "PRS_0" too small"
Database error code - 1555
Triggering SQL statement......."FETCH NEXT"
Internal call code................"[DBDS / NEW DSQL]"
Please check the entries in the system log (Trasaction SM21)
3. TSV_LIN_ALLOC_FAILED----
this error analysis which also gives HOW TO CORRECT THE ERROR is almost the same like the first error description which i have written like memory space and so on
i would appreciate if u could clarify these errors and how to resolve it. Thanks in advance.

Hi,
TSV_TNEW_* error are the memory problems in BI, you need to wait untill the system load is reduced...check the TA: SM37 and then repeat the failed steps, it will be successful.
DBIF_* are database releated errors....oracle backend error, u need to find out where the error has occured in the SQL statement and fix the error.
Usually these errors will the locks.
Oracle 8i error message says:
<u><b>ORA-01555</b></u>
snapshot too old: rollback segment number string with name "string"
too small
Cause: Rollback records needed by a reader for consistent read are overwritten
by other writers.
Action: Use larger rollback segments.
Regards,
Vijay
Message was edited by:
Vijaya Kumar Malyavantham

Short dump error DBIF_RSQL_INVALID_CURSOR

Hi
From Past few days, I am facing a peculiar issue
I am getting a short dump when the batch run to load to the Infocubes(Full Load). The load runs fine ones I deletes the failed request and load again.
The short dump and the exception are as below
Name of runtime error DBIF_RSQL_INVALID_CURSOR
Exception CX_SY_OPEN_SQL_DB
I have also checked with the basis team and no indication of a failure within SAP (no errors suggesting time-outs, buffers filling, tables filling etc)
Kindly let me know what could be root cause

Hi Pavan,
Are you trying to load the infocube from a DSO.We had the same issue whlle loading a cube from DSO and OSS note 339080 solved our issue.In case you are not able to access the note,find below the cause and solution provided in the note for this issue.
Cause and prerequisites
Customizing: the number of parallel processes for sending data was set to 0 in the ROIDOCPRMS table. For this reason, the system uses the process, in which the extraction takes place, for sending the data. A 'commit work' is performed in the sending process which causes an interruption of the running database selection in the extraction process.
Solution
Set the parameter 'maximum processes' in the ROIDOCPRMS table (or of the ROIDOCPRMS maintenance view) to a value> 0 for its connection with the BW.
Regards,
Bhagyarekha.

Short dump error while filling setup tables for 2LIS_06_INV

Hi All,
I am trying to fill the setup table.While filling the stup table for 2lis_06_inv datasource, i got the Dump error after some time.
Error
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
    SQL error in the database when accessing a table.
plz can anyone help me out...

Dear friends,
I tried it by giving the selection on fiscal year,but again same problem.If i give 1 0r 2 document numbers in selection then extractor works fine.
error:in detail.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
    SQL error in the database when accessing a table.
Information on where terminated
    Termination occurred in the ABAP program "SAPLMRMBW" - in "BW_RETRIEVE_DB_CO".
    The main program was "RMCENEUR ".
    In the source code you have the termination point in line 827
    of the (Include) program "LMRMBWF01".
    The program "SAPLMRMBW" was started as a background job.
    Job Name....... "RMCENEUR"
    Job Number..... 10524100
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "BW_RETRIEVE_DB_CO" "(FORM)", but it was neither handled locally nor
     declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLMRMBW "; its source code begins in line
    806 of the (Include program "LMRMBWF01 ".
806 FORM bw_retrieve_db_co USING    t_mcrbkey_bv    TYPE mcrbkey_t
807                                  t_mcrbkey_nbv   TYPE mcrbkey_t
808                                  t_ekbe_acc      TYPE t_ekbe
809                         CHANGING t_mcrbco        TYPE mcrbco_t.
810
811   TYPES: BEGIN OF s_target.
812   TYPES: table_left LIKE rbco.
813   TYPES: table_right TYPE rbex.
814   TYPES: END OF s_target.
815   TYPES: t_target TYPE TABLE OF s_target.
816
817
818   DATA: t_rbco_nbv TYPE t_target,
819         t_rbco_bv   TYPE t_target,
820         s_rbco      TYPE s_target,
821         s_ekbe      LIKE ekbe,
822         s_mcrbco    TYPE mcrbco,
823         l_index     LIKE sy-tabix.
824
   825 * Data source: invoice item non-background
826   IF NOT t_mcrbkey_nbv[] IS INITIAL.
*>>>>>     SELECT * FROM rbco AS r LEFT OUTER JOIN rbex AS i*
828        ON   ( rmandt = imandt AND
829               rbelnr = ibelnr AND
830               rbuzei = ibuzei AND
831               rcobl_nr = icobl_nr )
832        INTO TABLE t_rbco_nbv
833        FOR ALL ENTRIES IN t_mcrbkey_nbv
834        WHERE r~gjahr = t_mcrbkey_nbv-gjahr AND
835              r~belnr = t_mcrbkey_nbv-belnr.
836   ENDIF.
837 * Data source: invoice item background
838   IF NOT t_mcrbkey_bv[] IS INITIAL.
839     SELECT * FROM rbco AS r LEFT OUTER JOIN rbex AS i
840        ON   ( rmandt = imandt AND
841               rbelnr = ibelnr AND
842               rbuzei = ibuzei AND
843               rcobl_nr = icobl_nr )
844        INTO TABLE t_rbco_bv
845        FOR ALL ENTRIES IN t_mcrbkey_bv
846        WHERE r~gjahr = t_mcrbkey_bv-gjahr AND
Thnks in advance

Short dump error DBIF_RSQL_TABLE_UNKNOWN

Similar Messages

Maybe you are looking for