EXPORT obj1 ... objn TO DATABASE dbtab(ar) ID key
Hi all,
I have searched the entire SAP Fans forum, but did not get the answer to my query.
There is something called "Month End Trial Balance Report", (module FI) at our client site. This is a SE38 report. This report is run online and this makes a call to another report.
Datas/Internal tables are passed to another report by using statement "EXPORT obj1 ... objn TO DATABASE dbtab(ar) ID key". I guess this statment is used because of very big size of internal table.
As far as my knowledge is concerned abt this statment is that when this statement is executed SAP locks the INDX table(Exclusive Lock). So that database table INDX can't be accessed by another user.
Now my problem is that since it a monthend report and concurrent user starts running this report on monthed. Except for one user every other user running this report "Wait for DB Lock" to be released, resulting in short dump for them, as allowed time exceeds for them.
I am wondering is there any way we can control this, meaning can we control it from giving short dump, like performance tunning kind of thing.
I also thought to use "DELETE FROM DATABASE INDX(YT) ID GS_EXPORT_ID" after import statment because next time ABAP processor simply writes the new set of binary data into INDX table rather then deleting and writing for the same set of primary key .
To avoid dump, one thing can be done. Before the EXPORT/IMPORT statement, explicit check can be incorporated to see if the database is free (using the lock object ESINDX function module). If not free then program might be scheduled to run after some time. But user wanted to run the report online always.
Thanks a lot.
Jazz2
Still waiting to hear from you guys.
Regards,
Jazz2
Still waiting for answer
I also want to know.
I also have a question. I use the EXPORT to DATABASE statement, if the internal table is small, the program is OK. But if the IT is big, it will lost some records when IMPORT statement was executed.
I don't know why, who can tell me the reason.