In the background process field tcode is clean

Executing a transaction in the background field tcode is clean.
For example the transaction mir11 run in the background does not fill the field BKPG-TCODE as it happens running online.
there 'a solution?
thanks

Hi Prashant,
I know that the value is empty.
I need for example, because there are rules that check the TCODE to control (user exit), replacements and / or validation.
These work online while in the background is not.
Moreover, in the transaction MR11, sap record documents setting the transaction who created (BKPF-TCODE) and there is a check for the transfer (MR11SHOW) which controls the TCODE to do other things.
However I would also like to know if there is a rule or SAP note clarifying that the TCODE is never set in the background and that can not be used so as to seek other solutions.
thanks and excuse my English!
Caterina

Similar Messages

The background process

how can i get the handler of processes of oracle on WINNT?
what can i get now is only the oracle8i.exe process, but not the ora_dbw0_ORCL,ora_lgwr_ORCL,ora_ckpt_ORCL
as we get in unix ps command.
thanks.
null

Hi Prashant,
I know that the value is empty.
I need for example, because there are rules that check the TCODE to control (user exit), replacements and / or validation.
These work online while in the background is not.
Moreover, in the transaction MR11, sap record documents setting the transaction who created (BKPF-TCODE) and there is a check for the transfer (MR11SHOW) which controls the TCODE to do other things.
However I would also like to know if there is a rule or SAP note clarifying that the TCODE is never set in the background and that can not be used so as to seek other solutions.
thanks and excuse my English!
Caterina

How to trap warning messages generated from the background processing?

Hi all,
Following is my requirement, i want to know whether it can be done and how?
The credit management (CM) warning messages generated as a result of the CM background processes, where do the messages go? Can you trap them and include them in an interface control report?
Thanks

Hi
If it's created a job for that process, you can try to read the log: here you should find all triggered messages, so the warning ones too.
U can try to use fm like BP_JOBLOG_READ or BP_JOBLOG_SHOW in order to get the log.
Max

URGENT CAN U PLEASE TELL ME THE BACKGROUND PROCESSING

i developed one BDC program with session method
when i go to sm36 and i have gone through all the steps
but it is failing
the errors are:
1.session name is not given
2.user name not given
please tell me the STEP BY STEP CORRECT PROCEDURE

Hello,
Please read this: [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/edab9790-0201-0010-479a-98fcc7ebc7bd].
Regards.

The request could not be submitted for background processing.

Post Author: Chriss
CA Forum: Administration
It's an BOE XI SR2, on Win2k3 server, with a print cluster with two print spools, handling 3000+ printers. I discovered this error to be intermittent and only on one of the spools. It turned out that the only common factor was an HP4250 print driver. I backed all the 4250s down to 4200 drivers and the intermitent error ("Error in File. The request could not be submitted for background processing.") went from about 100 a day to zero. The other spool had a different version of the HP4250 driver and would on rare occassion cause this error, "Error in File ... Page header or footer longer than a page." but never the background processing error.
For reference, when I got this error in XI R1, this was the solution for 'the error with one name and many causes':The error "The request could not be submitted for background processing" can be related to a corrupt or wrong versioned crpe32.dll in the Crystal bin folder. Renaming to crpe32.dll_bak and using the repair command in the the "Add/Remove Programs" tool in the "Control Panel" will reinstall the correct dll. Then restart the Crystal services.

Post Author: krishna.moorthi
CA Forum: Administration
For Crystal reports :
Error : "The request could not be submitted for background processing"
I think,this was not related to a corrupt or wrong versioned crpe32.dll.
but the below mentioned is one of the reason for getting this error.
I got the error when the main report(crystalreports10) having more than 2 subreports not assigned proper tables for the subreports.
Example: (this code raise the abone mentioned error.)
rpt.SetDataSource(Exdataset);
rpt.Subreports["subreportname1"].SetDataSource(Exdataset); // Exdatatset.Tables[1]
rpt.Subreports["subreportname2"].SetDataSource(Exdataset);// Exdatatset.Tables[2]

Background processes while starting the R/3 system

hi all
I have IDES R/3 4.7 installed in my hard disk,
and when i start the background processes normally the status has to be Wait , yes.
But these days when i started the processes, i'm getting the statuses as "Ended" with all the 12 background processes,
and i can't be able to get into the login screen.
can anyone tell how to get the processes states to wait and yes state.
Thanks

Have a look at the dev_-traces located in /usr/sap/work directory. You should pay special attention to dev_w0 and dev_ms, and then look through the other dev_w files.
I guess, there you will find a hint leading you to the cuase of the issue

Regarding the Mandatory BackGround Processes

Hi,
I wanna to know the information abt the BackGround processes like(PMON,SMON,CKPT,LGWR,DBWR).Can u pls explain abt all these processes and can i able to visualise these processes practically?
Regards,
sudhir

To fully outline these processes and what they do, would take a book. In fact, books have been written on the subject.
Go to http://tahiti.oracle.com/ and start with the Concepts manual.
-Mark

EAS background processes status window is not listing the processes

Hi All,
When I choose to run a calc/report script at the background in EAS i dont see that process in the background process status window, it is just blank. but when i goto the session window to check, the process is still running. So background process status window is not list any processes that are chose to run at the background. Did anybody have this issue? Really appreciate your help to solve this problem.
We are using Essbase 11.1.2.1. The issue is in the nonprod environment but it works fine in the prod environment which is running the same version.
Thanks for you help..
MD

Hi Shiva,
When I run a calc from EAS and If I choose to run at the background, I should see that process and all previous processes that were run at the background in "Background Process Status" window but i don't see anything there. What do I need to do in ESSVR?
Hi Celvin,
This is the JRE version and same in prod too.
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Oracle JRockit(R) (build R28.0.2-11-135406-1.6.0_20-20100624-2119-linux-x86_64, compiled mode)
Thanks

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

ABAP Custom Report (ALV Format) in Background Processing

Hi
I am not the hardcore ABAP Person. But want to know about the detail fact of the ABAP Custome Reports. The question is can we do the background processing for the ABAP Custome Report in ALV Format.
If Yes ..do we require to have any additional Function/code to get the spool in ALV Format. I saw the comments that the output will look like the mess.
Please share your comment or any useful documenation on this. We are in ECC 6.0
Thanks in advance..and yes it will be rewared by points.
Navin

You can use alv's in background using docking containers, but the display wont be interactive. If you search the forum you will see tons of threads which talk about running ALV's in background.
For the output to be interactive, you can run the report in foreground and do the data processing in background.
Refer this link:
Displaying ALV Grid in Background Job

Background Processing, Selection Screens and Variants

Hi All,
I am having a little trouble Background Processing with Selection Screens and Variants.
When a user runs my report and selects the option of background processing, then they select a checkbox. Once this is checked, they should go and fill in details, press Execute and voila a background process is created. However what is happening is that when i execute it then it asks for a variant. I do not want this to happen. I want the values in the selection screens to be used as default. Here is my code for background processing
FORM START_BACKGROUND_PROCESSING.
CALL FUNCTION 'BP_JOBVARIANT_SCHEDULE'
    EXPORTING
      TITLE_NAME            = 'End Customer Report '
      JOB_NAME              = 'customer_report'
      PROG_NAME             = 'ZSE_SD_SALES'
EXCEPTIONS
    NO_SUCH_PROGRAM       = 1
    OTHERS                = 2
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.                    "START_BACKGROUND_PROCESSING
After the background process is started, all teh data is collated then written to the app server. this is the order
ELSEIF R2 EQ 'X' AND SY-BATCH EQ 'X'.
    PERFORM INITIALIZE_DATA.
    PERFORM SELECT_DATA.
    PERFORM PROCESS_DATA.
    PERFORM GET_END_CUSTOMER_DATA.
    PERFORM WRITE_TO_APP_SERVER.
Any ideas? Points given to those who are helpful

done myeslf

SAP BI 7 - Background process performance Issue

This question is about efficiency of dialog process compared to inefficiency of the background process and I want suggestions from SAP Basis/BI experts on this.
We have observed that our background processes on BI server are not running as efficiently as we would like them to run.
For example
DSO activation:
When I use Dialog mode for DSO Activation with 3 parallel processes, I can activate a certain DSO with in 15 seconds. But the same DSO and the same data package when activated using background mode with 3 parallel process takes about 15 minutes.(there are plenty of background processes available on the system when this activation is running). So dialog process runs 60 times faster than background process.
In BI 7 most of the operations can be executed only in the background parallel mode. And from the activation example we know that our background processes are not as efficient as dialog processes. It
is understood that in general the background processes will not be as efficient as dialog processes, but in our case the difference is a factor of 60. We want help to identify, why the background processes are not as efficient as dialog processes. What SAP Basis settings need to be changed to make them as efficient as we can. Any suggestion or help will be highly appreciated.

Hello Eswaran
Generally a dialog process is not faster by any means than a background workprocess. Nevertheless i trust you on your observations, so there must be some difference. I just did a small test, i ran SE16 chose a big table and selected 10000 rows, i did 3 tries in dialog and 3 in background. The results:
dialog: 10.2s, 9.4s, 9.6s
background: 26s, 24s, 24s
So even in my simple example the background execution took more time. The issue here is, that the resulting output (which is pretty large) had to be saved additionally in a spool (a total of 167 pages) when executed in background. The selection of the data certainly did not take more time in either case.
The most important difference between dialog and batch processes is the memory management. Dialog processes work with a shared memory segment (extended memory). Background processes have their private heap memory.
Nevertheless, background processes are not "slower" in general, not at all. You will need to observe closer, what your processes are doing. Maybe watching SM50 while running the DSO activation is enough to see it, maybe you need to trace a process. If you see large spools generated, or huge amounts of memory consumed, we might already have an answer.
Regards
Michael

Adding a Variable name to a filename in background processing

Hi All, Currently when I run a background process I am giving it a file name of
file_name = '/tmp/END_CUST'.
CONCATENATE file_name '_' v_dat '_' v_tim '.txt' INTO file_name.
This works and shows the filename correctly. However before running the background processing, I choose a variant and would like to concatenate that name in to it as well. I am not having luck with this.
Rewards for helpful answers

Hi dipesh,
1. The current variant name is stored in system variable
<b>SY-SLSET</b>
2. Hence, you can concatenate it like this for eg.
file_name = '/tmp/END_CUST'.
CONCATENATE file_name '_' v_dat '_' v_tim '.txt' INTO file_name.
<b>concatenate file_name sy-slset into file_name.</b>
regards,
amit m.

No background processing active on TargetServr BWTCLNT400

Hi There
I am currently working on a landscape where we have had a copy-back on our CRM system, plus the BW system was moved onto new hardware etc etc. the net result is that I am having a nightmare re-establishing the comminications CRM --> BW (which is now sorted) but especially BW --> BW.
I have sorted out all the usual stuff (SM59, WE20, WE21 etc etc) but when I run an update from an DSO in BW to another InfoProvider using the 3.x data flows, I get the following error in SM21:
BP_JOB_MODIFY: Job cannot be modified. Reason:
> Job BIREQU_62ZSSTFTQ5AI5RW1Y429235SE contains invalid data
BP_JOB_MODIFY: Job cannot be modified. Reason:
> No background processing active on TargetServr BWTCLNT400
I suspect this has definitely something to do with me trying to sort out the process chains and de-scheduling the background job for BI_PROCESS_LOADING on the BW system.
When I try to re-shedule this job using SM37, where you define a step for the ABAP Program RSPROCESS the system insist that I should enter a variant (which does not exist). So obviously I am being a muppet.
Does anybody know how I can re-start the Background Processing (I suspect there is a program that needs to be run or something)?
Any help would be MUCH appreciated.
Cheers - Daneel

Hi
I m facing the same error .. please check this note 147104 might be helpful in your issue..
check the entry in table ROIDOCPRMS for target system.. for the current source system.
Thanks
Sonal....
Edited by: Sonal Patel on Aug 28, 2009 12:08 PM

Workflow not working in Background Processing

Hi All,
I am relatively new to Workflow. Currently, I am creating Deliveries (preferably in background) once a Sales Order is created. I am using an ABAP Class as the object method to submit the sales order number to the delivery processing method (which just submits basic information to standard SAP transaction VL04). I found that if the execution of the delivery creation task is not in Background Processing (the user manually kicks off the Delivery creation in SBWP) the workflow works as expected and creates the deliveries. However, if the Background Processing is checked, the workflow does not process and does not create a delivery. Is there any specific reason as to why the workflow will not work in background?
Any help you can give would be greatly appreciated. Thanks.
John

Hi,
John
See to process a Back ground task, there should be a proper parameter flow.
Please look at the import parameters in the method you are using to process the back ground task..
If proper import parameters are passed then the task will work
This should help..
Thanks,
Shanky

In the background process field tcode is clean

Similar Messages

Maybe you are looking for