Bdc running in foreground not in background.

My BDC is working in foreground mode but not running in background mode.What can be the possible reasons..

hi renu,
Do check for ur flat file from which u r picking the data to be in application server.
Because in background processing the data cannot be picked from presentation server.
Also if u r using Gui_upload FM, that would give an error.
Use open dataset, read dataset statements to read from application server.
<b>Hope this is helpful, Do reward.</b>

Similar Messages

Air 3.4 iOS Push Notification is not fired when app is not running and is not in background

Hello,
I'm making an Air iOS application which uses the iOS Push Notification from Air 3.4.
All is working perfectly except when I receive notifications when the app is not running and is not in background (The app is killed).
I suppose the RemoteNotificationEvent.NOTIFICATION must be dispatched when I receive a notification even if my app is not currently running or in background ?
Do you have already get the same issue ? Do you know what can prevent the notification to be handled ?
Thanks,
Loïc

issue has been fixed in the build available at http://labs.adobe.com/downloads/air3-5.html.
You would now have to attach listener to InvokeEvent. For cases, when application is killed, InvokeEventReason will be InvokeEventReason.NOTIFICATION. The notification payload can be accessed by the following code
protected function onInvokeEvent(event:InvokeEvent):void
     trace("Invokehandler called .... \n");
     trace("reason: " + event.reason + "\n");
     if( event.reason == InvokeEventReason.NOTIFICATION)
                    var payload:Object = Object(event.arguments[0]);
          for (var i:String in payload)
                trace("Key:value pair " + i + ":" + payload[i] + "\n");
          // TODO: DO THE NEEDFUL ON RECIEVING A NOTIFICATION HERE

BDC running in foreground in ECC 6.0

hi all,
we have the system upgraded to ECC 6 and there was a BDC which was working fine in earlier version 4.7.
But now after the upgrade BDC runs in the foreground instead of background.
Can any one help me on this issue.
Regards,
Tcode

Hi
I guess the BDC is using 'Call transaction' not 'Session method'.
The 'MODE' in 'Call transaction' decides whether it is run in background or foreground. Please do check the code to ensure the value passed to MODE.
mode Effect
"A" Processing with display of screens
"E" Display of screens only if an error occurs
"N" Processing without display of screens. If a breakpoint is reached in one of the called transactions, processing is terminated with sy-subrc same as 1001. The field sy-msgty contains "S", sy-msgid contains "00", sy-msgno contains "344", sy-msgv1 contains "SAPMSSY3", and sy-msgv2 contains "0131".
"P" Processing without display of the screens. If a breakpoint is reached in one of the called transactions, the system branches to the ABAP Debugger.
Others Like "A".
Cheers!
Sam Kandas...

BDC Error:- Runs OK in foreground but NOT in background.

Hi All,
I am trying to do a BDC for stock putaway using LT01.
When I run this BDC in foreground
it runs successfully and transfers the stock OK with the following message:-
Field RL03T-ANFME. input value is longer than screen field (this is not an error message)
but when
I try to run it in background it gives me the following errors :-
Field RL03T-ANFME. input value is longer than screen field (this is not an error message in foreground)
Transaction error.
I know that a potential solution would be to write the LT01 using a BAPI or direct input etc but I would rather not go down this route.
Amny ideas?
I am using ECC5.0
Thanks,
N.

Hi Niall,
I have seen BDC behaving the way you have mentioned. This is because in Foreground the error is taken as soft error/warning(Green light flashes) and it allows you to continue. Even though the data upload is sucessful, you will have problems when you go into the actual transaction. An error pops up saying 'Please enter all the required fields' etc.
But at the same time when it runs in background, the same error is taken as hard error(red status light) and it will not allow further process.
Try to debug this BDC program in foreground and when it comes to this stage make the system field SY-BATCH = 'X'. Then you will understand what exactly happens.
The background process should be taken as the way to go and you need to correct the data.
I think this is helpful.
Kannan

Difference: Job run in foreground, job run in background and batch job

Hi Gurus,
Can you please help me to know what are the differences between job run in foreground, job run in background and batch job? Do jobs in foreground run in presentation server? Do jobs in background or batch jobs run in application server?
Thanks,
Kumar

foreground job running may cause job running crash or failed if it is too big or server is busy and it take too long time. meantime it will take one sap session.
background job will run base on request server status. and it will not take your sap session. and it will not failed normally.
and you can get the result by SM37.
my experience show that big report run in background normally faster than in foreground.
Edited by: JiQing Zhao on Sep 3, 2010 4:13 AM

Task working in foreground, not working in background

Hi Experts,
I am facing one strange problem.
I have created one Z BOR where i have written one method to fetch data from database.
I have added one task in workflow which calls this method.
When the task runs in foreground its perfectly fetches data.
But when i make the task background it does not fetch 2-3 particular fields.
I am not getting why this is happening.
Can anybody give me solution for this,
Thanks
Sameer

Hi,
Check the method of BO, double click on it and check the general tab, make sure if Dialog check box is not checked.
Regards
Dev.

BDC NOT WORKING BACKGROUND

Hi all
           I did a bdc for the tcode mira. It works fine in the foreground and displays
a status message "INVOICE DOCUMENT 411523 POSTED" is raised by SAP itself.
But in backgroud the program gets finished,but no documents is posted.
I want to run the program only in background .How to handle the message in background?
Thanks all.

ru using Call Transaction or session method.
If u r using Call transaction then pass the messages into one more internal table and display the messages.
Ex.
DATA: I_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
CALL TRANSACTION 'MIR7' USING I_BDCDATA
                     MODE   G_MODE
                     UPDATE 'S'
                     MESSAGES INTO I_MESSTAB.
loop at i_messtab and display the messages.

BDC to run in foreground using session method.

Hi,
Can you please let me know how to run the BDC session in foreground using RSBDCSUB.
Presently i am using the following code for RSBDCSUB.
submit rsbdcsub with mappe eq gc_bdcname
                         with Z_VERARB EQ 'X'
                         with FEHLER EQ ' '
                         and return.
Thanks,

SM35 submits the Session created to RSBDCSUB
To create session from program we use...
SUBMIT RFBIBL00 WITH DS_NAME = VA_FILE
WITH CALLMODE = CALLMODE AND RETURN.
run session.... there isnt any option to run it in foreground as far as I know, this will process it automatically, award points if found helpful
SUBMIT RSBDCSUB WITH MAPPE = P_NAME
WITH VON = SY-DATUM
WITH BIS = SY-DATUM
WITH FEHLER = ' '
TO SAP-SPOOL
LIST NAME P_NAME
LIST DATASET P_NAME
COVER TEXT P_NAME
NEW LIST IDENTIFICATION ' '
EXPORTING LIST TO MEMORY
AND RETURN.

Run the Report as a Background job and Get the Output in Excel in Local PC

Hello Gurus,
I have one following requirement.
One should be able to run the report as a background job and it should be possible to get the report in Excel format, also when running the report in background. The excel report should have the same information and look as the current SAPreport.
Please provide some solution.
Any helpful answer get surely awarded.
Thanks a lot,
Varlanir

GUI_* WS_* Function In Background, CSV Upload
GUI_* and WS_* function modules do not work in background
When scheduling a job in the background the appropriate statement to read in your file is OPEN DATASET, and the file must be on the file system that the SAP server can see.
At anytime, a user can switch of the Personal Computers even though the job is still running in the background. Therefore GUI_* and WS_* function modules are not designed to work in that way, as they need to access your personal computer file.
To choose the correct download method to used, you can check the value of SY-BATCH in your code,
if it is 'X' use OPEN DATASET and if it is ' ' use WS_UPLOAD.
*-- Open dataset for reading
DATA:
dsn(20) VALUE '/usr/test.dat',
rec(80).
OPEN DATASET dsn FOR INPUT IN TEXT MODE.
IF sy-subrc = 0.
DO.
    READ DATASET dsn INTO rec.
    IF sy-subrc <> 0.
      EXIT.
    ELSE.
      WRITE / rec.
    ENDIF.
ENDDO.
ENDIF.
CLOSE DATASET dsn.
*-- Open dataset for writing
DATA rec(80).
OPEN DATASET dsn FOR OUTPUT IN TEXT MODE.
TRANSFER rec TO '/usr/test.dat'.
CLOSE DATASET dsn.
What is the difference when we use upload, ws_upload, gui_upload function modules?
UPLOAD, WS_UPLOAD, GUI_UPLOAD, are used in BDC concepts. ie., Batch Data Communication.
Batch Data Conversion is a concept where user can transfer the Data from non SAP to SAP R/3. So , in these various Function Modules are used.
UPLOAD--- upload a file to the presentation server (PC)
WS_UPLOAD----    Load Files from the Presentation Server to Internal ABAP Tables.
WS means Work Station.
This is used upto SAP 4.6 version.
GUI_UPLOAD-------    Replaces WS_UPLOAD. Upoad file from presentation server to the app server. From 4.7 SAP version it is replaced.
How to Upload csv file to SAP?
Common File Download Upload Questions:
How you upload the data from text file to sap internal table? From my knowledge its by upload or gui_upload.
How you download the data from sap internal table to text file?
How you upload the data from xls (excel) file to sap internal table how you download the data from sap internal table to xls(excel) file.
You can upload data from presentation server to an internal table using gui_upload. Use gui_download to download from internal table to flat file.
Use fm ALSM_EXCEL_TO_INTERNAL_TABLE to upload data frm excel.
Use function module GUI_UPLOAD
The FILETYPE refer to the type of file format you need: For e.g 'WK1' - Excel format , 'ASC' - Text Format etc.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    FILENAME                      = 'C:\test.csv'
   FILETYPE                      = 'ASC'
TABLES
    DATA_TAB                      = itab
EXCEPTIONS
   FILE_OPEN_ERROR               = 1
   FILE_READ_ERROR               = 2
   NO_BATCH                      = 3
   GUI_REFUSE_FILETRANSFER       = 4
   INVALID_TYPE                  = 5
   NO_AUTHORITY                  = 6
   UNKNOWN_ERROR                 = 7
   BAD_DATA_FORMAT               = 8
   HEADER_NOT_ALLOWED            = 9
   SEPARATOR_NOT_ALLOWED         = 10
   HEADER_TOO_LONG               = 11
   UNKNOWN_DP_ERROR              = 12
   ACCESS_DENIED                 = 13
   DP_OUT_OF_MEMORY              = 14
   DISK_FULL                     = 15
   DP_TIMEOUT                    = 16
   OTHERS                        = 17.

BDC Error - Codepage could not be determined

Hello Gurus,
We are having a problem with BDC in transaction VF01.
The return message is FES-025 "Codepage could not be determined".
First of all the details and what have been done so far:
- The funcion module with BDC is called by an EDI message that is send on the creation of the SD Invoice.
- In Online mode, no errors are raised;
- The errors are only raised when the program runs in background - Manual processing of EDI message via T-Code WE19 (online mode) runs with no problems;
- In DEV enviroment, everything runs smoothly (both online and background modes) and we achieve the required result;
- In QAS enviroment, with exacly the same versions of code, the background process fails;
- Both DEV and QAS work on the same physical machine, on different instances.
I've searched quite a lot about this error and most results talk about the usage/call of GUI_UPLOAD or GUI_DOWNLOAD. We are NOT using this type of funcions in our code (or something that would connect to the client).
Any ideias?
Thanks in advance, best regards,
João Argêncio

Some additional informations:
- The sistem is non-unicode;
- The EDI message source and destination are the same machine (inter-company process);
- The user assiciated in IDoc Config has SAP_ALL privileges;
- Both systems are in the same release levels (ECC 5);
- All IDoc configuration is equal in both DEV and QAS instances.
If you need any additional information just let me know.
Thanks oin advance, best regards,
João Argêncio

Running the alv report in background and sending it thro email

hi,
      i have to run the alv report in background and send the output through email

Hi
Many a times there is a requirement to display ALV Grid (not ALV List) in the background Job. I have checked the SDN Forum for the same and it has been mentioned that ALV Grid cannot be displayed in Background, but the list output of ALV is possible. So user wont have the actual Grid interface but the List interface.
There is a workaround to display ALV Grid in Background Job. The only restriction is you cant schedule the job through SM36. You need to execute the transaction of the report program, fill in the selection screen data and hit Execute.
The job would be executed in background. User will be able to see the Job Log and Job Status after executing the program. User doesnt have to go to SM37 to view the job status/log. Once the Job Status is changed to COMPLETED, user can click on DISPLAY SPOOL to view the ALV Grid.
Limitations:
Cant schedulea background job
The session should be active until the background job is completed. If the session is closed, then user wont be able to check the output in ALV Grid. User would be able to check the output through spool or SM37
Advantages:
If the spool width is greater than 255 characters, then the entire width could be seen in the output because the output is directed to an ALV Grid and not to spool
Interface of ALV Grid is available instead of ALV List even though its a background job.
Program wont give the TIME OUT error
Steps Required:
1. Once you execute the program, the following screen would be displayed
2. Click Display Job Status to check the Status of the Background Job
3. Click on Display the Job Log to check the Log
4. Click on Display Job Status to check the Job Status
5. Click on DISPLAY SPOOL to check the spool content once the Job Status is changed to COMPLETED. Output is displayed in ALV Grid
Programs:
1. Two different programs needs to be created
ZPROGRAM_ONE: This is the 1st program, where the selection screen and all the data validations would be done. Error handling for invalid data should be done in this program.
Once the data validation is done, this program would call the 2nd program ZPROGEAM_TWO. Build the logic to display ALV Grid in this program. The logic will only display ALV in foreground and it wont be reflected in the spool.
ZPROGRAM_TWO: This program would fetch all the data and do all the processing. If you want the spool output along with ALV Grid output, then build the logic in this program to display ALV Grid.
*& Report ZPROGRAM_ONE                                                *
REPORT zprogram_one                            .
PRASHANT PATIL
TABLES : mara,
         tsp01.
type-pools:slis.
TYPES : BEGIN OF t_mara,
          matnr   TYPE mara-matnr,
          ersda   TYPE mara-ersda,
          ernam   TYPE mara-ernam,
          laeda   TYPE mara-laeda,
        END OF t_mara.
DATA : i_mara       TYPE STANDARD TABLE OF t_mara,
       wa_mara      TYPE t_mara,
       wa_index     TYPE indx,        " For Index details
       wa_index_key TYPE indx-srtfd VALUE 'PRG_ONE',
       i_jobsteplist     TYPE STANDARD TABLE OF tbtcstep, " For spool number
       wa_params         TYPE pri_params, " To Get Print Parameters
       wa_jobhead        TYPE tbtcjob,     " To know the status of job
       wa_jobsteplist    TYPE tbtcstep,    " To know the spool
       w_jobname         TYPE tbtco-jobname, " Job name for bckgrnd job
       w_jobcount        TYPE tbtco-jobcount, " Unique id for bckgrd job
       w_path            TYPE string,         " Upload path
       w_lsind           TYPE sy-lsind,       " Index
       wa_seltab         TYPE rsparams,
       i_seltab          TYPE STANDARD TABLE OF rsparams,
       wa_index1         TYPE indx,        " For Index details
       wa_index_key1     TYPE indx-srtfd VALUE 'PRG_TWO',
       i_fieldcat        TYPE slis_t_fieldcat_alv,
       wa_fieldcat       LIKE LINE OF i_fieldcat.
        CONSTANTS DECLARATION                                        *
CONSTANTS :
         c_a(1) TYPE c VALUE 'A',
         c_m(1) TYPE c VALUE 'M',
         c_l(1) TYPE c VALUE 'L',
         c_c(1) TYPE c VALUE 'C',
         c_zfdr(4) TYPE c VALUE 'ZFDR',
         c_x(1)    TYPE c VALUE 'X',
         c_locl(4) TYPE c VALUE 'LOCL', " Destination is LOCAL
         c_f(1)    TYPE c VALUE 'F',   " Job Status - Failed
         c_s(1)    TYPE c VALUE 'S',
         c_p(1)    TYPE c VALUE 'P'.
SELECTION SCREEN PARAMETERS
SELECT-OPTIONS : s_matnr FOR mara-matnr.
START-OF-SELECTION.
Before the export, fill the data fields before CLUSTR
wa_index-aedat = sy-datum.
wa_index-usera = sy-uname.
EXPORT s_matnr
       TO DATABASE indx(st) FROM wa_index ID wa_index_key.
To Open the Job for background processing
PERFORM open_job.
To get the print parameters
PERFORM get_print_parameters.
Submit the job in background
PERFORM job_submit.
Close the background job
PERFORM job_close.
This is the output screen with the buttons ********
Create 3 buttons DISPLAY SPOOL, STATUS, JOBLOG
SET PF-STATUS 'ZS001'.
WRITE: / 'The program is submitted in Background'.
WRITE: / 'Press DISPLAY SPOOL to see the spool'.
WRITE: / 'Press STATUS to see the status of the background'.
AT USER-COMMAND.
If user presses the 'BACK' button
IF sy-ucomm = 'BAK'.
    IF wa_jobhead-status = c_f OR
        wa_jobhead-status = c_a.
      LEAVE TO SCREEN 0.
    ENDIF.
ENDIF.
If the user presses the 'DISPLAY SPOOL' Button
IF sy-ucomm = 'DISPLAY'.
    PERFORM display_spool.
ENDIF.
If the user presses the 'JOB STATUS' Button
IF sy-ucomm = 'STATUS'.
    PERFORM display_status.
ENDIF.
If the user presses the 'JOB LOG' Button
IF sy-ucomm = 'JOBLOG'.
    PERFORM display_job_log.
ENDIF.
*&      Form open_job
      text
--> p1        text
<-- p2        text
FORM open_job .
This is to Create a new job which is to be submitted in background to
process sales order/delivery/invoice
Here we would get a unique id ( Jobcount ) which identifies our job
along with the job name which we have assigned to our job
CONCATENATE sy-uname
              sy-datum
              sy-uzeit
                      INTO w_jobname . " Assign unique jobname
CALL FUNCTION 'JOB_OPEN'
   EXPORTING
DELANFREP              = ' '
JOBGROUP               = ' '
    jobname                = w_jobname
SDLSTRTDT              = NO_DATE
SDLSTRTTM              = NO_TIME
JOBCLASS               =
IMPORTING
   jobcount                = w_jobcount
CHANGING
RET                    =
EXCEPTIONS
   cant_create_job        = 1
   invalid_job_data       = 2
   jobname_missing        = 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.
ENDIF.
ENDFORM.                    " open_job
*&      Form get_print_parameters
      text
--> p1        text
<-- p2        text
FORM get_print_parameters .
DATA : l_valid TYPE c.
This is to get the Print Parameters for the job which is to be
submitted in background to process sales order/delivery/invoice
CALL FUNCTION 'GET_PRINT_PARAMETERS'
   EXPORTING
ARCHIVE_ID                   = C_CHAR_UNKNOWN
ARCHIVE_INFO                 = C_CHAR_UNKNOWN
ARCHIVE_MODE                 = C_CHAR_UNKNOWN
ARCHIVE_TEXT                 = C_CHAR_UNKNOWN
AR_OBJECT                    = C_CHAR_UNKNOWN
ARCHIVE_REPORT               = C_CHAR_UNKNOWN
AUTHORITY                    = C_CHAR_UNKNOWN
COPIES                       = C_NUM3_UNKNOWN
COVER_PAGE                   = C_CHAR_UNKNOWN
DATA_SET                     = C_CHAR_UNKNOWN
DEPARTMENT                   = C_CHAR_UNKNOWN
      destination                  = c_locl " LOCL
EXPIRATION                   = C_NUM1_UNKNOWN
      immediately                  = space
IN_ARCHIVE_PARAMETERS        = ' '
IN_PARAMETERS                = ' '
LAYOUT                       = C_CHAR_UNKNOWN
LINE_COUNT                   = C_INT_UNKNOWN
LINE_SIZE                    = C_INT_UNKNOWN
LIST_NAME                    = C_CHAR_UNKNOWN
LIST_TEXT                    = C_CHAR_UNKNOWN
MODE                         = ' '
      new_list_id                  = c_x
PROTECT_LIST                 = C_CHAR_UNKNOWN
      no_dialog                    = c_x
RECEIVER                     = C_CHAR_UNKNOWN
RELEASE                      = C_CHAR_UNKNOWN
REPORT                       = C_CHAR_UNKNOWN
SAP_COVER_PAGE               = C_CHAR_UNKNOWN
HOST_COVER_PAGE              = C_CHAR_UNKNOWN
PRIORITY                     = C_NUM1_UNKNOWN
SAP_OBJECT                   = C_CHAR_UNKNOWN
TYPE                         = C_CHAR_UNKNOWN
      user                         = sy-uname
USE_OLD_LAYOUT               = ' '
UC_DISPLAY_MODE              = C_CHAR_UNKNOWN
DRAFT                        = C_CHAR_UNKNOWN
ABAP_LIST                    = ' '
USE_ARCHIVENAME_DEF          = ' '
DEFAULT_SPOOL_SIZE           = C_CHAR_UNKNOWN
PO_FAX_STORE                 = ' '
NO_FRAMES                    = C_CHAR_UNKNOWN
   IMPORTING
OUT_ARCHIVE_PARAMETERS       =
      out_parameters               = wa_params
   valid                        = l_valid
   EXCEPTIONS
     archive_info_not_found       = 1
     invalid_print_params         = 2
     invalid_archive_params       = 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.
ENDIF.
ENDFORM.                    " get_print_parameters
*&      Form job_submit
      text
--> p1        text
<-- p2        text
FORM job_submit .
The job which we have created & the unique id ( jobcount ) which we
have got identifies our job. Hence those parameters are passed along
with the name of the background program "ZPROGRAM_TWO"
The job is submitted in background.
CALL FUNCTION 'JOB_SUBMIT'
    EXPORTING
ARCPARAMS                         =
    authcknam                         = sy-uname
COMMANDNAME                       = ' '
OPERATINGSYSTEM                   = ' '
EXTPGM_NAME                       = ' '
EXTPGM_PARAM                      = ' '
EXTPGM_SET_TRACE_ON               = ' '
EXTPGM_STDERR_IN_JOBLOG           = 'X'
EXTPGM_STDOUT_IN_JOBLOG           = 'X'
EXTPGM_SYSTEM                     = ' '
EXTPGM_RFCDEST                    = ' '
EXTPGM_WAIT_FOR_TERMINATION       = 'X'
    jobcount                          = w_jobcount
    jobname                           = w_jobname
LANGUAGE                          = SY-LANGU
    priparams                         = wa_params
    report                            = 'ZPROGRAM_TWO'
VARIANT                           = ' '
IMPORTING
STEP_NUMBER                       =
   EXCEPTIONS
     bad_priparams                     = 1
     bad_xpgflags                      = 2
     invalid_jobdata                   = 3
     jobname_missing                   = 4
     job_notex                         = 5
     job_submit_failed                 = 6
     lock_failed                       = 7
     program_missing                   = 8
     prog_abap_and_extpg_set           = 9
     OTHERS                            = 10
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " job_submit
*&      Form job_close
      text
--> p1        text
<-- p2        text
FORM job_close .
Once the job is submitted in background then the job is closed
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
AT_OPMODE                         = ' '
AT_OPMODE_PERIODIC                = ' '
CALENDAR_ID                       = ' '
EVENT_ID                          = ' '
EVENT_PARAM                       = ' '
EVENT_PERIODIC                    = ' '
    jobcount                          = w_jobcount
    jobname                           = w_jobname
LASTSTRTDT                        = NO_DATE
LASTSTRTTM                        = NO_TIME
PRDDAYS                           = 0
PRDHOURS                          = 0
PRDMINS                           = 0
PRDMONTHS                         = 0
PRDWEEKS                          = 0
PREDJOB_CHECKSTAT                 = ' '
PRED_JOBCOUNT                     = ' '
PRED_JOBNAME                      = ' '
SDLSTRTDT                         = NO_DATE
SDLSTRTTM                         = NO_TIME
STARTDATE_RESTRICTION             = BTC_PROCESS_ALWAYS
    strtimmed                         = c_x
TARGETSYSTEM                      = ' '
START_ON_WORKDAY_NOT_BEFORE       = SY-DATUM
START_ON_WORKDAY_NR               = 0
WORKDAY_COUNT_DIRECTION           = 0
RECIPIENT_OBJ                     =
TARGETSERVER                      = ' '
DONT_RELEASE                      = ' '
TARGETGROUP                       = ' '
DIRECT_START                      =
IMPORTING
JOB_WAS_RELEASED                  =
CHANGING
RET                               =
   EXCEPTIONS
     cant_start_immediate              = 1
     invalid_startdate                 = 2
     jobname_missing                   = 3
     job_close_failed                  = 4
     job_nosteps                       = 5
     job_notex                         = 6
     lock_failed                       = 7
     invalid_target                    = 8
     OTHERS                            = 9
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " job_close
*&      Form display_spool
      text
--> p1        text
<-- p2        text
FORM display_spool .
To Read the Job to get the spool details
DATA : l_rqident TYPE tsp01-rqident, " Spool Number
         l_spoolno TYPE tsp01_sp0r-rqid_char.
CLEAR : l_rqident,
          w_lsind,
          wa_jobsteplist.
REFRESH : i_jobsteplist.
SET PF-STATUS 'ZAR02'.
Get the Spool Number
CALL FUNCTION 'BP_JOB_READ'
    EXPORTING
      job_read_jobcount           = w_jobcount
      job_read_jobname            = w_jobname
      job_read_opcode             = '20'
    JOB_STEP_NUMBER             =
   IMPORTING
     job_read_jobhead            = wa_jobhead
   TABLES
     job_read_steplist           = i_jobsteplist
CHANGING
   RET                         =
   EXCEPTIONS
     invalid_opcode              = 1
     job_doesnt_exist            = 2
     job_doesnt_have_steps       = 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.
ENDIF.
Read the Job Step list to get the spool number
READ TABLE i_jobsteplist INTO wa_jobsteplist INDEX 1.
CHECK wa_jobsteplist-listident <> space.
Spool Number
l_rqident = wa_jobsteplist-listident.
MOVE l_rqident TO l_spoolno.
Check the spool in TSP01
SELECT SINGLE * FROM tsp01 WHERE rqident = l_rqident.
IF sy-subrc = 0.
    LEAVE TO LIST-PROCESSING.
    CALL FUNCTION 'RSPO_R_RDELETE_SPOOLREQ'
      EXPORTING
        spoolid       = l_spoolno
    IMPORTING
      RC            =
      STATUS        =
    PERFORM show_alv.
ENDIF.
w_lsind = sy-lsind.
IF sy-lsind GE 19.
    sy-lsind = 1.
ENDIF.
ENDFORM.                    " display_spool
*&      Form show_alv
      text
--> p1        text
<-- p2        text
FORM show_alv .
Before the import, fill the data fields before CLUSTR.
wa_index1-aedat = sy-datum.
wa_index1-usera = sy-uname.
To Import the selection screen data from Calling Program
IMPORT i_mara
FROM DATABASE indx(st) ID wa_index_key1 TO wa_index1.
FREE MEMORY ID wa_index_key1.
This prepares the field-catalog for ALV.
PERFORM prepare_fieldcatalog.
This displays the output in ALV format .
PERFORM display_alv.
ENDFORM.                    " show_alv
*&      Form display_status
      text
--> p1        text
<-- p2        text
FORM display_status .
To Display the STATUS of the JOB which is exectued in background
CLEAR : wa_jobsteplist.
REFRESH : i_jobsteplist.
WRITE:/ 'DISPLAYING JOB STATUS'.
CALL FUNCTION 'BP_JOB_READ'
    EXPORTING
      job_read_jobcount           = w_jobcount
      job_read_jobname            = w_jobname
      job_read_opcode             = '20'
    JOB_STEP_NUMBER             =
   IMPORTING
     job_read_jobhead            = wa_jobhead
   TABLES
     job_read_steplist           = i_jobsteplist
CHANGING
   RET                         =
   EXCEPTIONS
     invalid_opcode              = 1
     job_doesnt_exist            = 2
     job_doesnt_have_steps       = 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.
ENDIF.
To Display the status text as per the status type
CASE wa_jobhead-status.
    WHEN 'S'. WRITE: / 'Scheduled'.
    WHEN 'R'. WRITE: / 'Released'.
    WHEN 'F'. WRITE: / 'Completed'.
    WHEN 'A'. WRITE: / 'Cancelled'.
    WHEN OTHERS.
ENDCASE.
IF sy-lsind GE 19.
    sy-lsind = 1.
ENDIF.
ENDFORM.                    " display_status
*&      Form display_job_log
      text
--> p1        text
<-- p2        text
FORM display_job_log .
To display the log of the background program
LEAVE TO LIST-PROCESSING.
CALL FUNCTION 'BP_JOBLOG_SHOW_SM37B'
    EXPORTING
      client                    = sy-mandt
      jobcount                  = w_jobcount
      joblogid                  = ' '
      jobname                   = w_jobname
    EXCEPTIONS
      error_reading_jobdata     = 1
      error_reading_joblog_data = 2
      jobcount_missing          = 3
      joblog_does_not_exist     = 4
      joblog_is_empty           = 5
      joblog_show_canceled      = 6
      jobname_missing           = 7
      job_does_not_exist        = 8
      no_joblog_there_yet       = 9
      no_show_privilege_given   = 10
      OTHERS                    = 11.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " display_job_log
*&      Form prepare_fieldcatalog
      text
--> p1        text
<-- p2        text
FORM prepare_fieldcatalog .
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'MATNR'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = 'Material no.'.
wa_fieldcat-outputlen    = '18'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERSDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = 'Creation date'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERNAM'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = 'Name of Person'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'LAEDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = ' Last Change'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
ENDFORM.                    " prepare_fieldcatalog
*&      Form display_alv
      text
--> p1        text
<-- p2        text
FORM display_alv .
Call ABAP List Viewer (ALV)
call function 'REUSE_ALV_GRID_DISPLAY'
    exporting
      it_fieldcat = i_fieldcat
    tables
      t_outtab     = i_mara.
ENDFORM.                    " display_alv
     ZPROGRAM_TWO: This is the 2nd program which would be called from program ZPROGRAM_ONE.
*& Report ZPROGRAM_TWO                                                *
REPORT zprogram_two                            .
PRASHANT PATIL
TABLES : mara.
TYPE-POOLS:slis.
TYPES : BEGIN OF t_mara,
          matnr   TYPE mara-matnr,
          ersda   TYPE mara-ersda,
          ernam   TYPE mara-ernam,
          laeda   TYPE mara-laeda,
        END OF t_mara.
DATA : i_mara        TYPE STANDARD TABLE OF t_mara,
       wa_mara       TYPE t_mara,
       wa_index      TYPE indx,        " For Index details
       wa_index_key TYPE indx-srtfd VALUE 'PRG_ONE',
       wa_index1     TYPE indx,        " For Index details
       wa_index_key1 TYPE indx-srtfd VALUE 'PRG_TWO',
       i_fieldcat        TYPE slis_t_fieldcat_alv,
       wa_fieldcat       LIKE LINE OF i_fieldcat.
SELECT-OPTIONS : s_matnr FOR mara-matnr.
Before the import, fill the data fields before CLUSTR.
wa_index-aedat = sy-datum.
wa_index-usera = sy-uname.
To Import the selection screen data from Calling Program
IMPORT s_matnr
FROM DATABASE indx(st) ID wa_index_key TO wa_index.
FREE MEMORY ID wa_index_key.
SELECT matnr
       ersda
       ernam
       laeda
       FROM mara
       INTO TABLE i_mara
       WHERE matnr IN s_matnr.
PERFORM prepare_fieldcatalog.
PERFORM display_alv.
Before the export, fill the data fields before CLUSTR
wa_index1-aedat = sy-datum.
wa_index1-usera = sy-uname.
EXPORT i_mara
TO DATABASE indx(st) FROM wa_index1 ID wa_index_key1.
*&      Form prepare_fieldcatalog
      text
--> p1        text
<-- p2        text
FORM prepare_fieldcatalog .
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'MATNR'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '18'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERSDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERNAM'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'LAEDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
ENDFORM.                    " prepare_fieldcatalog
*&      Form display_alv
      text
--> p1        text
<-- p2        text
FORM display_alv .
Call ABAP List Viewer (ALV)
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      it_fieldcat = i_fieldcat
    TABLES
      t_outtab    = i_mara.
ENDFORM.                    " display_alv
its possible to display ALV Grid using OO ALV. Following code can be used instead of FM.
In the PBO, add following code
SET PF-STATUS 'ZSTAT'.
If program is executed in background
CALL METHOD cl_gui_alv_grid=>offline
RECEIVING
e_offline = off.
IF off IS INITIAL.
IF container1 IS INITIAL.
CREATE OBJECT container1
EXPORTING
container_name = 'CC_ALV1' .
ENDIF.
ENDIF.
CREATE OBJECT g_grid1
EXPORTING
i_parent = container1.
CALL METHOD g_grid1->set_table_for_first_display
EXPORTING
I_BUFFER_ACTIVE =
I_BYPASSING_BUFFER =
I_CONSISTENCY_CHECK =
I_STRUCTURE_NAME =
IS_VARIANT =
i_save = 'A'
i_default = ' '
is_layout =
is_print =
IT_SPECIAL_GROUPS =
it_toolbar_excluding =
IT_HYPERLINK =
IT_ALV_GRAPHICS =
IT_EXCEPT_QINFO =
CHANGING
it_outtab = i_output
it_fieldcatalog = i_fieldcatalog
IT_SORT =
IT_FILTER =
EXCEPTIONS
invalid_parameter_combination = 1
program_error = 2
too_many_lines = 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.
ENDIF.
Reward points if useful
Regards
Anji

How to run the basic list in background to generate secondary.

How to run the basic list in background to generate secondary and spool for the secondary.Please note that Basic list will run in foreground.

Problem solved.

Calling Spool while running in Foreground

Hi,
If I run a classical report in background, the output of this automatically goes to the Spool, which I can see using SP01/SP02.
But, the user wants to send the output of the report while running in Foreground too.
Customer's Says: "in the foreground, the user must be prompted to send the output to the spool".
Please help me with the logic.
Thanks in advance,
Ishaq.

Hi,
I have tried your code for generating spool in foreground(below). The spool no gets generated but I am not getting the data in spool.
NEW-PAGE PRINT ON
        LINE-SIZE 220
        IMMEDIATELY 'X'
        KEEP IN SPOOL 'X'
        NEW LIST IDENTIFICATION 'X'
        NO DIALOG.
        PERFORM header.
        PERFORM output USING wa_final.
        NEW-PAGE PRINT OFF.
Then after I have to send mail with a PDF attachment.
Please suggest.
Regards,
Binay.

BDC for KE51 is not working

Hi all,
BDC for KE51 is not working.I did recording with my Func Consultant and I created the program,all the data is coming correctly in th structure RECORD.But when Iam running the transaction,in foreground mode(Display all screens) the data is not getting entered into the fields of the screen,few got entred and few are blank.When I tried to reprocess the recording,then also data is not getting entered into the fields.Data is there in the recording.
What might be the problem?

Hello Techies,
i m having the same problem but in my program i have to extract the data from SAP server and again have to upload in other table on SAP so please help me how would i extract the data and after that upload it using BDC.
Thanks

No result /report when weu00B4re running a risk analysis in background

Dear forum,
We are running several risk analysis in background (from configuration tab) and we cannot see any result
in the column called "result". However, when we run a offline analysis (from informer tab) we can see that the column "result" is containing a file.
Hope you can help us.
Thanks in advance.

Running risk analysis in background from the configuration tab does not produce a report by design. This background job is really just performing a system maintenence activity and is not intended for report generation. This background job preps data for performing offline analysis as well as the underlying data that supports the management reports in the informer tab (among other things). Generally, anything in the configuration tab is system maintenance related.
It sounds like you're attempting to perform typical analysis of end user access, not system maintenance activities. The informer tab is what you need to be using to perform the analysis.
Within the informer tab, whether you choose to perform online analysis or offline analysis, a report result is always generated. In my experience, there has not been a compelling reason to use offline analysis capabilities within the informer tab. Online analysis (real-time analysis of the SAP system rather than the offline data from the last configuration tab background risk analysis) is naturally always current, which is a plus.

Bdc running in foreground not in background.

Similar Messages

Maybe you are looking for