Skip to Content
author's profile photo Former Member
Former Member


Dear Friends,

Is there a difference between BTC & BGD?



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Jun 14, 2007 at 03:52 PM

    Hi Praveen

    There is no much diffrence between BTC and BGD. Both are backround proccessing techniques.

    <b> 1. BTC </b>

    Background Processing


    In background processing, the SAP System automatically runs any report or program that you can start interactively.

    When you schedule a job in the background processing system, you must specify:

    The ABAP report or external program that should be started

    The start time

    The printing specifications

    The background processing system starts your job and runs the program(s) that you specify. Afterwards, you can check whether your job was executed successfully and display a log of any system messages.

    Suppose you need to run a report of customers whose bills are overdue.You can:

    Start the report yourself from the ABAP Editor. If you do this, the system runs the report interactively, in a session at your PC or workstation. While the report is being processed, your computer response time may be slower.

    Or, you can have the background processing system run the report. To do this, you must create a background job that tells the system what you want it to do.

    The background processing system runs your "late bills" report according to your instructions. The list generated by the report is either printed directly or is waiting for you in the SAP output controller (see Using the Output Controller).You can also check in the background processing system whether the report ran correctly.


    Running a report in the background does not tie up the SAP sessions you are currently working with.

    When you start a report interactively, your current SAP session is blocked for further input for as long as the report runs.

    When you start the report in the background, running the report does not influence your interactive work with the SAP System.

    You can shift the execution of reports to the evening or other periods of low load on the SAP System.

    You can schedule a report or external program to run at any time that the SAP System is active. You can also set up reports to run automatically on a regular basis (for example, on the last day of each month).

    Background processing is the only way you can execute long-running jobs.

    To prevent tying up system resources with interactive sessions for long reports, the SAP System has a built-in time limit on interactive sessions. If a single ABAP report runs for more than 5 minutes continuously in an interactive session, the SAP System terminates the report automatically.

    The background processing system executes long-running ABAP reports more efficiently. Often, such reports are automatically scheduled for execution in the background. In this case, you do not need to schedule them for background processing yourself.

    <b> 2. BGD </b>

    BI Background Management


    The BI background management provides you with a number of functions:

    &#9679; Functions for managing background and parallel processes in BI

    &#9679; Various reports for BI system management

    &#9679; Functions for finding and analyzing errors in BI

    These functions support SAP Support during the error analysis.

    The BI background management functions are available in the Administration functional area of the Data Warehousing Workbench under Batch Manager (transaction RSBATCH).


    Make sure that there are sufficient background processes (type BTC or BGD) available to process the processes in the system in parallel. Approximately 50% more background work processes are required than before.


    You make settings for the parallel processing of processes that are managed in BI background management. BI background management allows you to process BI processes in parallel in the background, as long as the processes support parallel processing. For example, you can use BI background management to activate the data in a DataStore object in parallel in the background. As well as being able to run processes in parallel, using background processes also has other advantages, such as the generation of logs, making it easier to monitor processes. You can also define deletion selections for messages generated by BI background management and internal parameters for the background processes and execute check and conversion programs for request information. BI background management also offers functions for displaying job and process information.

    You can execute check and conversion reports. With the BI background management, you can start conversion of the management of request information. During conversion, the request information is stored in tables that permit fast access to the request information, for example when displaying from within the administration of the InfoProvider.

    Perform this conversion after an upgrade.

    You can search logs and protocols for the BI processes and also debug BI processes that are managed by the BI background management.


    Tab Page: Background and Parallel Processes

    &#9679; Displaying background jobs in BI background management

    Choose the list of Batch Manager Jobs. You can display or delete messages for individual jobs and delete the internal parameters of background processes.

    &#9679; Displaying background processes

    Choose Display Batch Processes. In the overview, the system displays different information about the background process; the number of jobs in a work process, the number of jobs in a work process that contain errors, the load of the work processes over the time.

    &#9679; Settings for parallel processing

    Select the process type for which you want to make settings. The system displays in detail the process chain variants for which settings have already been made. Select Parallel Settings. On the next screen, select the process for which you want to change the settings. Specify whether you want to process the process serially or in parallel in the background. For parallel processing, define the number of processes that you want to use in parallel. Define the server or server group on which you want to execute the processes. If you do not specify a server or server group, the system selects an available server and distributes the load evenly across all servers that have free background work processes.

    You can change settings for process variants here. These settings are made initially in variant maintenance for the relevant process. The settings are valid globally for processes that are not executed via process chains.

    For more information about parallel processing for several aggregates, see Loading Data into Aggregates Efficiently.

    &#9679; Determining selections for deleting messages output by BI background management and internal parameters for background processes

    Choose Deletion Selections. Specify the number of days after which you want the system to delete internal messages output by BI background management and the internal parameters of background processes that are executed in background management. We recommend that you delete messages and parameters that are older than 30 days. This setting should normally prevent table RSBATCHDATA from being overfilled. When defining the deletion selections, make sure that you keep the data as long as necessary in order to track any problems that might occur. With Schedule, define the start conditions. We recommend that you run the job on a daily basis. Save the start conditions. On the next screen, enter the server on which the job should run and choose Copy to schedule the deletion job. You can display the deletion jobs and stop a scheduled deletion job.

    Tab Page: Reports

    &#9679; Jump to transaction SE38 to execute the check and conversion programs for request information

    To improve performance when displaying requests (in InfoProvider administration, for example) and loading data, in SAP NetWeaver 2004s, the administration information for requests is stored in special tables (RSSTATMANPART and RSSTATMANPARTT for InfoProviders and RSstatmanpsa and RSstatmanpsaT for PSA tables). This allows quicker access to the information.

    After upgrading to SAP Net Weaver 2004s, execute the two reports RSSTATMAN_CHECK_CONVERT_DTA and RSSTATMAN_CHECK_CONVERT_PSA for all objects (InfoProvider and PSA tables) at least once in the background. This ensures that the available request information for existing objects is written to the new tables to enable quicker access. It also fills the new status management tool with the existing data. The request information for newly loaded requests and objects created after the upgrade is automatically written to the new table. These functions and reports primarily serve to transfer existing data to the new administration tables. We recommend that you execute the reports again if there are inconsistencies between the contents of table RSSTATMANPART or RSSTATMANPSA and the correct status or information for the request.

    When you execute check and conversion programs, the system checks the status of all requests for the selected objects, changes or includes entries as required, and deletes the entries for deleted requests.

    Choose Edit Loadable InfoProviders to execute report RSSTATMAN_CHECK_CONVERT_DTA and Edit PSA Tables to execute report RSSTATMAN_CHECK_CONVERT_PSA. Select the objects for which you want to execute the reports. Specify whether you want to check status management at execution. This check is only recommended if the reports have already been executed. It is also useful later if you find inconsistencies in status management for the requests, for example if the system continues to display deleted requests in InfoProvider administration or displays the incorrect request status even after the reports have been executed. Make the settings for parallel processing (see above) and execute the reports in the background.

    Tab Page: Support Tools

    &#9679; Search for logs in different areas

    Choose Search Logs in BW. You can use different criteria to search for logs and messages. Searches supported include: Search for logs for ABAP runtime errors (ST22), SysLogs (SM21), application logs (SLG1), monitor logs, job logs (SM37), traces for SM50, logs for BI background management, and transport logs and activation search results.

    &#9679; Debugging BI background management processes

    You can specify selections for debugging a process that is managed in BI background management (Debug Selections) and debug this process directly (Perform Debugging).

    This function is primarily intended for SAP Support to find errors.

    Also go through this links for more detailed info.

    <b> Helpfull: Reward Points </b>

    Thanks and Kind Regards



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 14, 2007 at 03:58 PM


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 22, 2016 at 09:04 AM

    Dear All,

    there is any way to trace BTC connection. For example when I run a Bex Query I have a DIA connection and this kind of connection are traced on RSDDSTAT_OLAP but unfortunately BTC connection are not traced. Which kind of table is used by SAP BW to trace BTC connections ?

    Best Regards,


    😊 😊 😊

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.