topic Re: program standard terminate RFBIBL00 in Application Development and Automation Discussions

program standard terminate RFBIBL00

Former Member — Wed, 05 Nov 2008 11:28:12 GMT

hiii

i am doing a requirement as follows:



loop at list of directory
    SUBMIT RFBIBL00 WITH  DS_NAME     = G_DIRECTORY "file path name
                    WITH  FL_CHECK    = SPACE 
                    WITH  OS_XON      = SPACE 
                    WITH  XNONUNIC    =  SPACE 
                    WITH  CALLMODE    = 'B'    "batch session
                    WITH  MAX_COMM    = '9999' "no of docs per commit work
                    WITH  PA_XPROT    = SPACE  "extended log
                    WITH  XLOG        = 'ON'   "radio button log on
                     EXPORTING LIST TO MEMORY
                    AND RETURN.

  CALL FUNCTION 'LIST_FROM_MEMORY'
    TABLES
      listobject = t_list
    EXCEPTIONS
      not_found     = 1
      ERROR_MESSAGE = 2
      OTHERS        = 3.
endloop

suppose i have 3 files in and the second file have some error such as

posting key not determine in table etc...

the submit program terminate and the 3rd file is not being process how can prevent that

note the my program is being run in background.

i have use exporting list to memory as shown above but it's not working

Re: program standard terminate RFBIBL00

Former Member — Wed, 05 Nov 2008 12:24:09 GMT

Hi,

I assume that the program is getting terminated due to the errors occured during runtime. We need to some how capture/track these errors. So it would be best if you use call mode as CALL TRANSACTION instead of session. So that it will captuer the errors and returns the msgcoll table.

Try this.

Venkat.

Re: program standard terminate RFBIBL00

Former Member — Thu, 06 Nov 2008 04:00:09 GMT

In the standard program there is a piece of code like this


select * in a database table
if sy-subrc NE 0.
  if sy-batch EQ X
      message ID 'A' with xxxx
  ENDIF.
ENDIF.

so in this case whether through call transaction or batch session . if the program is executed in background then the message abort will always be trigger is the select statement is not satisfy