Error in background job while running FTP_CONNECT

Dear Friends,
When I try to run the FTP_CONNECT  FM in background,
the ftp server is not connected throwing an error message ''Attempt to set up connection to <ftpserver> failed''.
I am using the RFC destination SAPFTPA and still it is not working!
My program was successfully executing in fore ground with SAPFTP.
Please help.
Thanks and Regards,
Vidya Sagar.

Hi,
The below program is to create file on FTP server by taking the data from internal table
To see whether the file is created on the FTP server
use the function module FTP_SERVER_TO_R3.
Check the below code.
You write a same program with the function module FTP_SERVER_TO_R3 instead of
FTP_R3_TO_SERVER to check the existence of the file which is already created.
tables: t777a.                        "Building Addresses
Internal Table for  Building table.
data: begin of it_t777a occurs 0,
        build like t777a-build,       "Building
        stext like t777a-stext,       "Object Name
        cname like t777a-cname,       "Address Supplement (c/o)
        ort01 like t777a-ort01,       "City
        pstlz like t777a-pstlz,       "Postal Code
        regio like t777a-regio,       "Region (State, Province, County)
      end of it_t777a.
Internal Table for taking all fields of the above table in one line
separated by u2018|u2019(pipe).
data: begin of it_text occurs 0,
      text(131),
      end of it_text.
Constants: c_key  type i value 26101957,
           c_dest   type rfcdes-rfcdest value 'SAPFTPA'.
data: g_dhdl type i,      "Handle
      g_dlen type i,      "pass word length
      g_dpwd(30).         "For storing password
Selection Screen Starts
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME TITLE TEXT-001.
parameters: p_user(30) default 't777a'          obligatory,
            p_pwd(30)  default 't777a'          obligatory,
            p_host(64) default 'XXX.XXX.XX.XXX' obligatory.
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN BEGIN OF BLOCK blk2 WITH FRAME TITLE TEXT-002.
parameters: p_file like rlgrap-filename default 't777a_feed.txt'.
SELECTION-SCREEN END OF BLOCK blk2.
Password not visible.
at Selection-screen output.
  loop at screen.
    if screen-name = 'P_PWD'.
      screen-invisible = '1'.
      modify screen.
    endif.
  endloop.
g_dpwd  = p_pwd.
Start of selection
start-of-selection.
To fetch the data records from the table T777A.
  select build stext cname ort01 pstlz regio
         from t777a
         into table it_t777a.
Sort the internal table by build.
  if not it_t777a[] is initial.
    sort it_t777a by build.
  endif.
Concatenate all the fields of above internal table records in one line
separated by u2018|u2019(pipe).
  loop at it_t777a.
    concatenate it_t777a-build it_t777a-stext it_t777a-cname
                it_t777a-ort01 it_t777a-pstlz it_t777a-regio
                into it_text-text separated by '|'.
    append it_text.
    clear it_text.
  endloop.
To get the length of the password.
  g_dlen = strlen( g_dpwd ).
Below Function module is used to Encrypt the Password.
  CALL FUNCTION 'HTTP_SCRAMBLE'
    EXPORTING
      SOURCE      = g_dpwd          "Actual password
      SOURCELEN   = g_dlen
      KEY         = c_key
    IMPORTING
      DESTINATION = g_dpwd.         "Encyrpted Password
*Connects to the FTP Server as specified by user.
  Call function 'SAPGUI_PROGRESS_INDICATOR'
    EXPORTING
      text = 'Connecting to FTP Server'.
Below function module is used to connect the FTP Server.
It Accepts only Encrypted Passwords.
This Function module will provide a handle to perform different
operations on the FTP Server via FTP Commands.
  call function 'FTP_CONNECT'
    EXPORTING
      user            = p_user
      password        = g_dpwd
      host            = p_host
      rfc_destination = c_dest
    IMPORTING
      handle          = g_dhdl
     EXCEPTIONS
        NOT_CONNECTED.
  if sy-subrc ne 0.
    format color col_negative.
    write:/ 'Error in Connection'.
  else.
    write:/ 'FTP Connection is opened '.
  endif.
**Transferring the data from internal table to FTP Server.
  CALL FUNCTION 'FTP_R3_TO_SERVER'
    EXPORTING
      HANDLE         = g_dhdl
      FNAME          = p_file
      CHARACTER_MODE = 'X'
    TABLES
      TEXT           = it_text
    EXCEPTIONS
      TCPIP_ERROR    = 1
      COMMAND_ERROR  = 2
      DATA_ERROR     = 3
      OTHERS         = 4.
  IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  ELSE.
    write:/ 'File has created on FTP Server'.
  ENDIF.
Call function 'SAPGUI_PROGRESS_INDICATOR'
    EXPORTING
      text = 'File has created on FTP Server'.
To Disconnect the FTP Server.
  CALL FUNCTION 'FTP_DISCONNECT'
    EXPORTING
      HANDLE = g_dhdl.
To Disconnect the Destination.
  CALL FUNCTION 'RFC_CONNECTION_CLOSE'
    EXPORTING
      destination = c_dest
    EXCEPTIONS
      others      = 1.
Regards,
Kumar Bandanadham

Similar Messages

  • Background job is running for long tome in source system (ECC)

    Hi All,
    Background job is running for long tome in source system (ECC) while extracting data to PSA.
    I checked in ECC system SM66,SM50 the job is still running
    in SM37 the job is Active
    There are only maximum 7000 records the extractor is 2LIS_02_ITM but it is taking 11 to 13 hours to load to PSA daily
    I had checked enhancements every thing is correct.
    Please help me on this how can I solve this issue.
    Regards
    Supraja K

    Hi sudhi,
    The difference between Call customer enhancement...  and  Result of customer enhancement:... is very less we can say this as a second.
    The difference is between LUWs confirmed and 1 LUWs -
       and Call customer enhancement -
    Please find the job log details below, and give me the solution to ressolve this
    01:06:43 ***01:06:43 * ztta/roll_extension........... 2000000000                              *                 R8           050
                     R8           048
    01:06:43 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA     RSQU          036
    06:56:31 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 5.208 records                  R3           407
    06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
    06:56:31 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 5.208 records                      R3           407
    06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
    06:56:31 PSA=1 USING SMQS SCHEDULER / IF [tRFC=ON] STARTING qRFC ELSE STARTING SAPI                 R3           299
    06:56:31 Synchronous send of data package 1 (0 parallel tasks)                                      R3           410
    06:56:32 tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =                           R3           038
    06:56:32 tRFC: Start = 00.00.0000 00:00:00, End = 00.00.0000 00:00:00                               R3           039
    06:56:32 Synchronized transmission of info IDoc 3 (0 parallel tasks)                                R3           414
    06:56:32 IDOC: Info IDoc 3, IDoc No. 1549822, Duration 00:00:00                                     R3           088
    06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
    06:56:32 Altogether, 0 records were filtered out through selection conditions                      RSQU          037
    06:56:32 Synchronized transmission of info IDoc 4 (0 parallel tasks)                                R3           414
    06:56:32 IDOC: Info IDoc 4, IDoc No. 1549823, Duration 00:00:00                                     R3           088
    06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
    06:56:32 Job finished                                                                               00           517
    Regards
    Supraja

  • Background Job Still Running - Data Can Be Displayed Only Msg Populated in Maintain Versions (OKEQ) Screen

    Hi,
    I try to create 2013 FY in "Setting for Each FY" in OKEQ - Maintain Versions unfortunately I have created Null FY, try to delete Null FY on the time it will ask Job schedule, I have cancelled the job & reopen Maintain Versions (OKEQ) screen on the time system populated the msg "Background Job still running - Data can be displayed only"
    In Settings for Each FY screen there is no New Entries button, all FY are blocked status, changes was not allowed.
    How can I resolve it.
    Waiting for your valuable suggestions.
    Regards,
    Nageswar.

    Dear Rajneesh Saxena
    Thanks for your prompt reply.
    Yes you are correct, on the time of deletion it will ask Background Job Process, for immediate deletion must & should select "NO".
    While "Settings for Each FY" screen populates message "Background Job Still Running - Data Can Be Displayed Only" open  screen in display mode enter the command "=KILL" in command bar press enter, then you will allow to changes get New Entries button also.
    Problem is solved
    Regards,
    Nageswar.

  • Error in background job for program RSGET_SMSY error message No active job

    Hello!
    I would like to set up the Change Request Management functionality in SAP Solution Manager.
    The only red warning by executing Test-button in Tcode “SOLAR_ADMIN_PROJECT” is:
    <b>Error in background job for program RSGET_SMSY error message No active job found</b>
    Can someone please tell me how to solve this problem?
    (tcodes, technical steps)
    Thank you very much!
    regards
    Thom

    Thank you very much!
    Can you also help me with the warning "Errors occurred during synchronization of the system landscape" in tcode SOLAR_PROJECT_ADMIN" --> System landscape --> Change requests --> "Refresh"?
    The second issue I cannot see any projects in Tcode "/TMWFLOW/CMSCONF"
    according to the SPRO-step "Set Project Assignment of Requests as Mandatory"
    Thank you!
    regards

  • MGX-8850 DIAG: slot 8, error = 0xffffffff: Reset occurred while running Offline diag.

    Need help with resolving this error message. 
    From what I can tell the card seems find when doing a dspcd 8 it does not show any alarms.
    AGNODE-331-1.7.PXM.a > dspcd 8
    AGNODE-331-1                     System Rev: 05.06   May. 02, 2014 15:51:28 GMT
    MGX8850/B                                            Node Alarm: CRITICAL
    Slot Number    8    Redundant Slot:  7
                        Front Card          Upper Card          Lower Card
    Inserted Card:      PXM45C              UI Stratum3/B       PXM HardDiskDrive  
    Reserved Card:      PXM45               UI Stratum3         PXM HardDiskDrive  
    State:              Standby             Active              Active         
    Serial Number:      SAD100509GD         SAD1032004C         SAD102509L4 
    Prim SW Rev:        5.6(10.200)         ---                 ---
    Sec SW Rev:         5.6(10.200)         ---                 ---
    Cur SW Rev:         5.6(10.200)         ---                 ---
    Boot FW Rev:        5.6(10.200)         ---                 ---
    800-level Rev:      E0                  B0                  A0   
    800-level Part#:    800-20217-06        800-25728-01        800-05052-06
    CLEI Code:          BA7AURPDAA          BA6ATU0FAB          BA7IADYAAB 
    Version ID (VID):   ---                 ---                 ---        
    Reset Reason:       On Reset From Shell
    Card Alarm:         NONE                
    Failed Reason:      None                
    Type <CR> to continue, Q<CR> to stop: 
    AGNODE-331-1                     System Rev: 05.06   May. 02, 2014 15:51:28 GMT
    MGX8850/B                                            Node Alarm: CRITICAL
    Miscellaneous Information:
    Crossbar Slot Status:      Present
    Alarm Causes
        NO ALARMS                 
    Backcard Mismatch/Failed Reasons
    Upper Card 
        NO MISMATCH               
    Lower Card 
        NO MISMATCH               
    Type <CR> to continue, Q<CR> to stop: 
    AGNODE-331-1                     System Rev: 05.06   May. 02, 2014 15:51:28 GMT
    MGX8850/B                                            Node Alarm: CRITICAL
    Front Card Mismatch Reason
    NO MISMATCH
    AGNODE-331-1.7.PXM.a > 
    but when I run the dsplog command the following is shown.
    07A00454 05/02/2014-14:13:31 DIAG-4-ERR           
            SysDiag    SysDiagReportError
    DIAG: slot 8, error = 0xffffffff: Reset occurred while running Offline diag.
    07A00455 05/02/2014-12:40:41 DIAG-4-ERR           
            SysDiag    SysDiagReportError
    DIAG: slot 8, error = 0xffffffff: Reset occurred while running Offline diag.
    07A00602 05/02/2014-12:53:54 DIAG-4-ERR           
            SysDiag    SysDiagReportError
    DIAG: slot 8, error = 0xffffffff: Reset occurred while running Offline diag.
    Anyone know why the log is showing this and how do I get past it?

    Need help with resolving this error message. 
    From what I can tell the card seems find when doing a dspcd 8 it does not show any alarms.
    AGNODE-331-1.7.PXM.a > dspcd 8
    AGNODE-331-1                     System Rev: 05.06   May. 02, 2014 15:51:28 GMT
    MGX8850/B                                            Node Alarm: CRITICAL
    Slot Number    8    Redundant Slot:  7
                        Front Card          Upper Card          Lower Card
    Inserted Card:      PXM45C              UI Stratum3/B       PXM HardDiskDrive  
    Reserved Card:      PXM45               UI Stratum3         PXM HardDiskDrive  
    State:              Standby             Active              Active         
    Serial Number:      SAD100509GD         SAD1032004C         SAD102509L4 
    Prim SW Rev:        5.6(10.200)         ---                 ---
    Sec SW Rev:         5.6(10.200)         ---                 ---
    Cur SW Rev:         5.6(10.200)         ---                 ---
    Boot FW Rev:        5.6(10.200)         ---                 ---
    800-level Rev:      E0                  B0                  A0   
    800-level Part#:    800-20217-06        800-25728-01        800-05052-06
    CLEI Code:          BA7AURPDAA          BA6ATU0FAB          BA7IADYAAB 
    Version ID (VID):   ---                 ---                 ---        
    Reset Reason:       On Reset From Shell
    Card Alarm:         NONE                
    Failed Reason:      None                
    Type <CR> to continue, Q<CR> to stop: 
    AGNODE-331-1                     System Rev: 05.06   May. 02, 2014 15:51:28 GMT
    MGX8850/B                                            Node Alarm: CRITICAL
    Miscellaneous Information:
    Crossbar Slot Status:      Present
    Alarm Causes
        NO ALARMS                 
    Backcard Mismatch/Failed Reasons
    Upper Card 
        NO MISMATCH               
    Lower Card 
        NO MISMATCH               
    Type <CR> to continue, Q<CR> to stop: 
    AGNODE-331-1                     System Rev: 05.06   May. 02, 2014 15:51:28 GMT
    MGX8850/B                                            Node Alarm: CRITICAL
    Front Card Mismatch Reason
    NO MISMATCH
    AGNODE-331-1.7.PXM.a > 
    but when I run the dsplog command the following is shown.
    07A00454 05/02/2014-14:13:31 DIAG-4-ERR           
            SysDiag    SysDiagReportError
    DIAG: slot 8, error = 0xffffffff: Reset occurred while running Offline diag.
    07A00455 05/02/2014-12:40:41 DIAG-4-ERR           
            SysDiag    SysDiagReportError
    DIAG: slot 8, error = 0xffffffff: Reset occurred while running Offline diag.
    07A00602 05/02/2014-12:53:54 DIAG-4-ERR           
            SysDiag    SysDiagReportError
    DIAG: slot 8, error = 0xffffffff: Reset occurred while running Offline diag.
    Anyone know why the log is showing this and how do I get past it?

  • Error DBIF_RSQL_SQL_ERROR and DBIF_REPO_SQL_ERROR while running DTP

    Hi to all,
    I am loading the data from PSA to DSO, while running DTP, after some records load a run time error coming DBIF_RSQL_SQL_ERROR or DBIF_REPO_SQL_ERROR .
    Also i tried the Number of Processes reduce from 3 to 1 in DTP, but still same error .
    i have searched the SDN and found that it is due to table space problem.
    if it is due to table space , how i will find it and how to correct it.
    Please can any one tell we why it is coming and what is the solution for that.
    i shall be thankful to you for this.
    Regards
    Pavneet Rana

    Thanks for reply,
    i have checked ST22 . and found the error text for 2 runtime error .
    first for DBIF_RSQL_SQL_ERROR
    second for  DBIF_REPO_SQL_ERROR
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          14.03.2011 22:00:21
    Short text
         SQL error in the database when accessing a table.
    What can you do?
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrator
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    How to correct the error
        Database error text........: "SQL30081N A communication error has been
         detected. Communication protocol being used: "TCP/IP". Communication API being
         used: "SOCKETS". Location where the error was detected: "200.1.1.66".
         Communication function detecting the error: "recv". Protoco"
        Internal call code.........: "[RSQL/FTCH/RSBMONMESS ]"
        Please check the entries in the system log (Transaction SM21).
        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:
        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
        "CL_RSBM_LOG_REQUEST_ROOT======CP" or "CL_RSBM_LOG_REQUEST_ROOT======CM00F"
        "GET_STATIC_BUFFER"
        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
       "GET_STATIC_BUFFER" "(METHOD)", or its possible occurrence must be declared in
        the
       RAISING clause of the procedure.
       To prevent the exception, note the following:
    Information on where terminated
        Termination occurred in the ABAP program "CL_RSBM_LOG_REQUEST_ROOT======CP" -
         in "GET_STATIC_BUFFER".
        The main program was "RSBATCH_EXECUTE_PROZESS ".
        In the source code you have the termination point in line 29
        of the (Include) program "CL_RSBM_LOG_REQUEST_ROOT======CM00F".
        The program "CL_RSBM_LOG_REQUEST_ROOT======CP" was started as a background job.
        Job Name....... "BIDTPR_2256_1"
        Job Initiator.. " a"
        Job Number..... 18254200
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "GET_STATIC_BUFFER" "(METHOD)", but it was neither handled locally
         nor declared
        in the RAISING clause of its signature.
        The procedure is in program "CL_RSBM_LOG_REQUEST_ROOT======CP "; its source
         code begins in line
        1 of the (Include program "CL_RSBM_LOG_REQUEST_ROOT======CM00F ".
    Source Code Extract
    Line  SourceCde
        1 method get_static_buffer.
        2   data l_s_storage type rsbm_s_storage.
        3   l_s_storage = get_s_storage( ).
        4   check l_s_storage-type = rsbm_c_storagetype-database..
        5   delete o_th_nodes_static where logid = n_logid.
        6   delete o_t_msg_static where logid = n_logid.
        7   delete o_t_logpar_static where logid = n_logid.
        8   select *
        9     from rsbmnodes connection (l_s_storage-id)
       10     appending corresponding fields of table o_th_nodes_static
       11     where logid = n_logid.
       12
       13   data l_count_monmess type sytabix.
       14   select count( * ) from rsbmonmess
       15     into l_count_monmess
       16     where logid = n_logid.
       17   if l_count_monmess > 50000.
       18     select * from rsbmonmess up to 50000 rows connection (l_s
       19       appending corresponding fields of table o_t_msg_static
       20       where logid = n_logid
       21       and   posit < 50
       22       order by node posit.
       23   else.
       24     select * from rsbmonmess connection (l_s_storage-id)
       25       appending corresponding fields of table o_t_msg_static
       26       where logid = n_logid
       27       order by node posit.
       28   endif.
    >>>>>   select * from rsbmlogpar
       30     appending corresponding fields of table o_t_logpar_static
       31     where logid = n_logid.
       32   field-symbols: <l_s_nodes> type rsbmnodes,
       33                  <l_s_log> type s_log.
       34   read table o_th_log assigning <l_s_log>
       35     with table key logid = n_logid.
       36   if sy-subrc <> 0.
       37     break hoeferf.                                          "
       38   endif.
       39   loop at o_th_nodes_static assigning <l_s_nodes>.
       40     if <l_s_nodes>-node  > <l_s_log>-maxnode.
       41       <l_s_log>-maxnode = <l_s_nodes>-node.
       42     endif.
    43   endloop.
    44 * --- set datapackage buffer
    45   cl_rsbk_dp_state=>free_buffer( n_requid ).
    46   cl_rsbk_dp_state=>fill_buffer( n_requid ).
    47 endmethod. 
    Runtime Errors         DBIF_REPO_SQL_ERROR
    Date and Time          14.03.2011 15:34:32
    Short text
         SQL error "-99999" occurred when accessing program
    What can you do?
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrato
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    How to correct the error
         Database error text........: "CLI0108E Communication link failure.
          SQLSTATE=40003"
         Triggering SQL statement...: "CX_SY_NATIVE_SQL_ERROR========CP "
         Internal call code.........: "[REPO/*/43/LOAD/CX_SY_NATIVE_SQL_ERROR===
         Please check the entries in the system log (Transaction SM21).
         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:
         "DBIF_REPO_SQL_ERROR" " "
         "SAPLSYDB" or "LSYDBU27"
         "DB_COMMIT"
         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.
    Information on where terminated
        Termination occurred in the ABAP program "SAPLSYDB" - in "DB_COMMIT".
        The main program was "RSBATCH_EXECUTE_PROZESS ".
        In the source code you have the termination point in line 7
        of the (Include) program "LSYDBU27".
        The program "SAPLSYDB" was started as a background job.
        Job Name....... "BIDTPR_2252_1"
        Job Initiator.. "A"
        Job Number..... 12541100
    Source Code Extract
    Line  SourceCde
        1 FUNCTION DB_COMMIT.
        2 *"----------------------------------------------------------------------
        3 *"*"Lokale Schnittstelle:
        4 *"----------------------------------------------------------------------
        5
        6   EXEC SQL.
    >>>>>     COMMIT WORK
        8   ENDEXEC.
        9
       10 ENDFUNCTION 
    please  can any one tell me cause for runtime error.
    i shall be thankful to you for this.
    regards
    pavneet rana
    Edited by: pavneet rana on Mar 15, 2011 1:29 PM

  • Error in Background Job Processing.

    Dear All,
             I am using a background job for processing the outbound delivery.
             In the user exit in delivery program I am checking for the combination of
             ship to party, Material & Batch of outbound delivery in a ztable. If the combination exists in
             Ztable I do not want to save & ignore this delivery creation and continue with the next
             delivery order creation thru the batch job.
             However I need to give an error / warning message for the delivery orders
             which are not created so I am giving the error message as success message
             in  the below format :-
              IF L_RETURN-TYPE = 'E'.
                MESSAGE S000(Z64_I) WITH L_RETURN-MESSAGE_V1
                                         L_RETURN-MESSAGE_V2
                                         L_RETURN-MESSAGE_V3
                                         L_RETURN-MESSAGE_V4
                                         DISPLAY LIKE 'E'.
                PERFORM FOLGE_GLEICHSETZEN(SAPLV00F).
                FCODE = 'ENT1'.
                SET SCREEN SYST-DYNNR.
                LEAVE SCREEN.
              ENDIF.
            But my job is finished as soon as the above message is encountered and the
            rest of the outbound deliveries are not created.
            However if I execute the progarm in foreground the execution is working fine.
            Could you please let me know what do I need to code / do corrections to make
            the program run successfully in background.
    Thanks & Regards
    Jitendra Gujarathi

    Hello,
    Check system log and also check work process trace, to know the error.
    I feel that it could be Authorization issue, you don't have sufficient authorization to do.
    Hope this helps.
    Regards
    venkata
    Edited by: venkata emandi on Sep 12, 2011 8:13 AM

  • Spool error for background job

    Hi All,
    I have scheduled one job in sap for a report.I have made a distribution list via tcode SO01.
    I have given this distribution list to the SPOOL RECEPIENT section in SM 36.
    The job is running successfully but is giving the following error and not sending emails to the distribution list.
    The error is :-
    "Spool list of step 1 could not be sent due to error 7".
    Does anybody has any idea about this error?
    Please help its a production issue.
    Thanks in advance
    Vivekanand Meghmala

    Look at SAP note : 760838
    Symptom
    Background job spool lists are not sent.
    Other terms
    RSBTCRTE, RSPO_SPOOLJOB_TO_OFFICE, SO_DOCUMENT_SEND_API1
    Reason and Prerequisites
    1. The jobs in question have recipient references in table TBTCO but these have no equivalent in the Business Object Repository.
    2. An error occurs when sending in the spool or in the Sapconnect layer.
    Solution
    This note does not provide a direct solution to the problem but it does provide a source code enhancement that you can use to create more trace information about the cause of the error. When you copy and execute a job with spool list recipients, trace messages are output when errors occur.
    After implementing the correction instructions, use transaction SE91 to create the following message:
    Message class: BT
    Number: 347
    Text: Spool list of step &1 could not be sent due to error &2.
    In detail, the error numbers mean:
    1 = Spool request does not exist (or no longer exists)
    2 = Spool request does not contain any data
    3 = Empty page area selected
    4 = No authorization to send the request
    5 = Access to the spool request is not possible
    6 = Read error in the Temse layer
    7 = Spool request could not be sent (sending problem)
    8 = Incorrect request type
    9 = Other

  • How to select server in which background job should run

    Hi,
    I want to run my program as background job. I want the user to select the server, in which background job should be run, in the selection screen of my program. When it is sheduled in background the job should run in the selected server.
    How to do this?
    Regards,
    Sriram

    Hi,
    please write the code like as below.
    DATA : D_GROUP like TBTCJOB-JOBGROUP.
    use the function moulde JOB_OPEN.
      D_JOBNAME = SY-REPID.
      D_GROUP- BTCSYSREAX =  " pass the target server name Here
         CALL FUNCTION 'JOB_OPEN'
            EXPORTING
                 JOBNAME          = D_JOBNAME
                 JOBGROUP       =  D_GROUP
            IMPORTING
                 JOBCOUNT         = D_JOBNO
            EXCEPTIONS
                 CANT_CREATE_JOB  = 1
                 INVALID_JOB_DATA = 2
                 JOBNAME_MISSING  = 3
                 OTHERS           = 4.
    submit   <Program name>
                  USER SY-UNAME VIA JOB D_JOBNAME NUMBER D_JOBNO
                  USING SELECTION-SET '  var1 '   " Give varient name
                  AND RETURN.
    CALL FUNCTION 'JOB_CLOSE'
               EXPORTING
                    JOBCOUNT             = D_JOBNO
                    JOBNAME              = D_JOBNAME
                    STRTIMMED            = 'X'
               IMPORTING
                   JOB_WAS_RELEASED     = D_REL
               EXCEPTIONS
                   CANT_START_IMMEDIATE = 1
                   INVALID_STARTDATE    = 2
                   JOBNAME_MISSING      = 3
                   JOB_CLOSE_FAILED     = 4
                   JOB_NOSTEPS          = 5
                   JOB_NOTEX            = 6
                   LOCK_FAILED          = 7
                   OTHERS               = 8.
    Hope this will helps you
    Regards
    Kiran

  • Background Job not running

    Hi All,
    A background job has been scheduled to run every minute.It was working fine but a few days back it did not get scheduled for 2 hours . Any suggestions as to why this might have happened.
    TIA.
    Vartika

    Hi Manik,
    The job started working fine after 2 hours. It was only for 2 hrs that it did not work. How to check if the userid was locked or not during that period.
    Thanks
    Vartika

  • Error in background job scheduling in Solman 7.0

    Hi Experts,
    I am working with Solman 7.0 configuration. In the IMG node for Scheduling background jobs (Solution manager-> General Settings), while following the documentation to schedule the jobs, I am facing issues with the following jobs:
    1. *SEND_SYSTEM_RELATIONSHIP_TO_SUPPORT *
    This job got cancelled on immediate scheduling, however has been scheduled for next day. What could be the reason by which it got cancelled?
    2. AI_SDK_FILL_FILE_TYPE_TABLE
    I cant find a job of this name in the system (while all other jobs are already available in the system by default). But, there is a program with the same name. Should I schedule the same in SM36?
    Regards,
    Arun.

    Hi,
    Yes schedule a job with program AI_SDK_FILL_FILE_TYPE_TABLE. Hope this solves your problem.
    Feel free to revert back.
    --Ragu

  • Error in Source System while running the Full Load

    HI Experts,
    We are using 0CRM_UT_SRV_CONT_I datasource from CRM to extract data.
    It is giving error while running the full load as 'Error Occured in Source system' with messaage Number : RSM340.
    I  want to mention certain points here:
    1) In RSA3 its running fine.
    2) Connection between BW and CRM system is OK.
    3) We have replicated datasource and send active veriosn from Dev system.
    4) When I run Init without data, Init set sucessful with entry in RSA7 in CRM.
    5) Delta run fine with green status.
    6) As source system is static client, hence do data for delta.
    The Main issue happens when we run either the Full load or Init With Data transfer.
    Kindly suggest.
    Thanks
    Mayank

    Hi Mayank,
    see in source system (CRM) with transaction SM21 and ST22 the error log and and then you let us know.
    Charly

  • Error in background job for VT04 - RV56TRGN

    Hello!
    The selection criteria is fine - we want every shipping point to be used to create every variant. We also have TPPs mirroring the plant codes. The job log sepects some deliveries which are good and tries to process them - the endlogue is it found X no. of deliveries, processed them but did not write the shipment to the data base. Digging further, it shows the error - <u>the system cound not determine the TPP for the plant in the delivery line item.</u>
    When I look at the variant, it doesn't talk of the TPP at all - only the shipping point and all the other criteria mainly associated with the deliveries and their statuses. I am wondering how the system knows which TPP to use for each shipping point when no TPP is assiged in the variant? Is this a default configuration I am missing? Or something else? Appreciate any leads...
    Thanks a lot.

    PS: In addition to creating the shipments, we also need to make their status to 'complete' in the background job as it is a purely non value added activity for us but we need the shipments for the cost documents. Any ideas how I can go about that?
    Thanks.

  • Error with data source while running hybernate program

    Hi,
      An error has occured while running the hybernate example.I have deployed the application using the net weaver.
    The Error is :
      500   Internal Server Error
      SAP J2EE Engine/6.40 
      Application error occurs during processing the request.
    Details: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method addDepartment.
         at com.sap.j2ee.examples.ejb.HibernateFacadeLocalLocalObjectImpl0.addDepartment(HibernateFacadeLocalLocalObjectImpl0.java:163)
         at com.sap.j2ee.examples.Control.addDepartment(Control.java:126)
         at com.sap.j2ee.examples.Control.doPost(Control.java:73)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.engine.services.ejb.exceptions.BaseRuntimeException: Cannot create an instance of the stateless bean.
         at com.sap.engine.services.ejb.session.stateless_sp5.BeanFactory.getActiveBean(BeanFactory.java:192)
         at com.sap.engine.services.ejb.session.stateless_sp5.StatelessContainerFP.getActiveBean(StatelessContainerFP.java:183)
         at com.sap.j2ee.examples.ejb.HibernateFacadeLocalLocalObjectImpl0.addDepartment(HibernateFacadeLocalLocalObjectImpl0.java:154)
         ... 18 more
    Caused by: java.lang.NoClassDefFoundError
         at com.sap.j2ee.examples.ejb.HibernateFacadeBean.setSessionContext(HibernateFacadeBean.java:44)
         at com.sap.engine.services.ejb.session.stateless_sp5.BeanFactory.createObject(BeanFactory.java:111)
         at com.sap.engine.services.ejb.util.pool.ContainerPoolImpl.doResizeOneStepUp(ContainerPoolImpl.java:368)
         at com.sap.engine.services.ejb.util.pool.ContainerPoolImpl.ensureNotEmpty(ContainerPoolImpl.java:337)
         at com.sap.engine.services.ejb.util.pool.ContainerPoolImpl.pop(ContainerPoolImpl.java:291)
         at com.sap.engine.services.ejb.session.stateless_sp5.BeanFactory.getActiveBean(BeanFactory.java:188)
         ... 20 more
    com.sap.engine.services.ejb.exceptions.BaseRuntimeException: Cannot create an instance of the stateless bean.
         at com.sap.engine.services.ejb.session.stateless_sp5.BeanFactory.getActiveBean(BeanFactory.java:192)
         at com.sap.engine.services.ejb.session.stateless_sp5.StatelessContainerFP.getActiveBean(StatelessContainerFP.java:183)
         at com.sap.j2ee.examples.ejb.HibernateFacadeLocalLocalObjectImpl0.addDepartment(HibernateFacadeLocalLocalObjectImpl0.java:154)
         at com.sap.j2ee.examples.Control.addDepartment(Control.java:126)
         at com.sap.j2ee.examples.Control.doPost(Control.java:73)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: java.lang.NoClassDefFoundError
         at com.sap.j2ee.examples.ejb.HibernateFacadeBean.setSessionContext(HibernateFacadeBean.java:44)
         at com.sap.engine.services.ejb.session.stateless_sp5.BeanFactory.createObject(BeanFactory.java:111)
         at com.sap.engine.services.ejb.util.pool.ContainerPoolImpl.doResizeOneStepUp(ContainerPoolImpl.java:368)
         at com.sap.engine.services.ejb.util.pool.ContainerPoolImpl.ensureNotEmpty(ContainerPoolImpl.java:337)
         at com.sap.engine.services.ejb.util.pool.ContainerPoolImpl.pop(ContainerPoolImpl.java:291)
         at com.sap.engine.services.ejb.session.stateless_sp5.BeanFactory.getActiveBean(BeanFactory.java:188)
         ... 20 more

    we are getting the same error in 11.5.10 oracle apps!
    Current system time is 19-MAR-2013 11:41:33
    +-----------------------------
    | Starting concurrent program execution...
    +-----------------------------
    Arguments
    p_order_by='TRX_NUMBER'
    p_cust_trx_class='CM'
    p_trx_number_low='1'
    p_trx_number_high='1'
    p_project_number='2160610'
    p_report_fmt='Y'
    p_open_invoice='N'
    p_check_for_taxyn='N'
    p_choice='SEL'
    p_header_pages='1'
    p_debug_flag='N'
    p_message_level='10'
    p_pmt_advice='Y'
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.US7ASCII
    Spawned Process 5484
    X Error of failed request: BadWindow (invalid Window parameter)
    Major opcode of failed request: 15 (X_QueryTree)
    Resource id in failed request: 0xa400001
    Serial number of failed request: 518
    Current serial number in output stream: 518
    Database version: 10.2.0.4

  • ERROR: InDbCtxFile.uploadCtx() : Exception  While Running Autoconfig

    While running autoconfig, we are getting this error.
    Attempting upload of Context file and templates to database...ERROR: InDbCtxFile.uploadCtx() : Exception : Error executng BEGIN fnd_gsm_util.upload_context_file(:1,:2,:3,:4,:5); END;: 1; The element reports_port is missing from the context file /u01/R12/inst/apps/upg_peabody/appl/admin/upg_peabody.xml. The context file upload will not continue.
    oracle.apps.ad.autoconfig.oam.InDbCtxFileException: Error executng BEGIN fnd_gsm_util.upload_context_file(:1,:2,:3,:4,:5); END;: 1; The element reports_port is missing from the context file /u01/R12/inst/apps/upg_peabody/appl/admin/upg_peabody.xml. The context file upload will not continue.
    at oracle.apps.ad.autoconfig.oam.InDbCtxFile.uploadCtx(InDbCtxFile.java:281)
    at oracle.apps.ad.autoconfig.oam.CtxSynchronizer.uploadToDb(CtxSynchronizer.java:328)
    at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBCtx(FileSysDBCtxMerge.java:678)
    at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBFiles(FileSysDBCtxMerge.java:222)
    at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:1583)
    at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:684)

    If this is part of the upgrade,
    yes< we are doing Upgrade 11i to R12
    please note that Rapid Install (as it runs AutoConfig) records errors in the AutoConfig log file. These errors occur because the database has not yet been upgraded. They can be safely ignored. The errors will be resolved when you run Rapid Install (and AutoConfig) in Step 2 of the Finish the Upgrade section of Chapter 3.
    Sawwan, We already upgraded database to 10g (10.2.0.4)

Maybe you are looking for