Known SAP notes

The following table describes known SAP Notes that may resolve problems which can occur when using Control-M for SAP. For more information, access either the SAPNet - R/3 Frontend or the SAP Service Marketplace, at http://support.sap.com/notes.

NOTE: You may need to install later support packages on your SAP system.

SAP Note number

Description

2340467

Correction in BAPI_XBP_VARIANT_CHANGE: Multiselection (select-options) is not handled correctly.

2369968

BAPI_XBP_VARIANT_CHANGE and protected

Variants: The 'Protected' variant attribute remains unchanged.

2422103

A variant is changed with the function BAPI_XBP_VARIANT_CHANGE. A no-display field that should not be

changed, is incomplete following the change.

1003941

SAP BW, Process Chain: On the agent tracker process, an error occurs that the chain is not continued despite the fact that the process was completed successfully.

1005481

SAP BW, Process Chain: On the agent tracker process, In very quick parallel asynchronous processes, even though one or more processes may be successful, the process chain log may not contain any instances.

As a result, the chain does not continue after the successful process.

1723482

When the same process chain is started in parallel via the FM RSPC_API_CHAIN_START, the chain is not executed and it results in an endless loop.

706292

DB2 database system. A function that checks or reads the status of a job report, and understands that the job does not exist, even though it clearly does.

888681

As 706292, for the DB6 database system.

756201

As 706292, for the SQL Server Microsoft database.

792850

903329

Kernel corrections.

1030158

The FKJO_SCHEDULE report prepares jobs for a mass activity run for external job schedulers. Jobs should be created in "Scheduled" status.

However, these jobs exist in 'Released' status for a short time during the report runtime before their status is changed to Scheduled. This can be a problem for some external job schedulers.

1048051

When an external job scheduler reads child jobs of the FKJO_SCHEDULE report, no results are shown, because scheduled jobs are not child jobs. In this situation, the jobs must have Released status, released and the external job scheduler must intercept these jobs.

(This is a continuation of the note 1030158)

1004083

This SAP note relates to the Restart from Point of Failure option in the SAP panel of Control-M active jobs. Process Chain jobs do not restart.

1059049

Control-M for SAP reports that Process Chain jobs ended NOTOK, when they have actually completed successfully. This is due to an internal SAP problem.

1016441

Control-M for SAP reports that R/3 jobs ended NOTOK, when they have actually completed successfully. This is due to an internal SAP problem.

856780

790615

Load ABAP fails with error 101, Call back function with events called.

839526

When you activate the process chain using the RSPC_API_CHAIN_START function, the E_LOGID parameter is empty but no exception is triggered.

835846

BP_JOB_SELECT: Optimizing the job selection (See also SAP Note 715355; After you import SAP Note 715355, jobs may not be selected correctly.) See the following Flash BMPM009945 Jobs in Copy mode end in failure after updating the SAP Basis SP level

833777

If you want to create jobs with the After Event start condition, this note must be installed in your SAP system.

782127

Due to an internal SAP problem, jobs intercepted by SAP fail to start running and are assigned a status of NOTOK in Control-M. See the following Flash Control-M fails to start Intercepted jobs, and displays an error message.

756901

Intercepted jobs are released and started by SAP just after being intercepted. As a result, the Interception functionality is unusable. See the following Flash Intercepted jobs are released by SAP.

732350

BAPI_XBP_REPORT_SEARCH: Empty report names in output In XBP 2.0, Load ABAP does not provide the full list of ABAP programs. This is an SAP problem.

728947

Job count cannot be created.

699144

When restarting a Process Chain from point of failure using Control-M, irrelevant processes are also started.

677081

Data Archiving: Delete and Store jobs may not be recognized as children of the Write job. This SAP Note must be implemented when working with the Control-M solution for Data Archiving with XBP 2.0 functionality.

664830

Severe problems when working with Business Information Warehouse. This SAP Note must be applied to your SAP system when working with Control-M solution for Business Information Warehouse.

654802

Jobs become stuck in Released status instead of being executed.

641175

When copying a job, the Spool List Recipient is not copied.

635095

Short dump with BAPI_XBP_REPORT_SEARCH

628917

This SAP Note relates to bug number BMPM008968 (No support of comma as decimal point in numeric fields). For more information, see the Control-M for SAP Release Notes, FD5311.

612564

Jobs are created with the wrong job class.

610480

Slow reaction of certain BAPI functions can affect the Extractor Management performance, and the loading of job names in the Job Editing form.

609462

Incorrect print parameters for XBP (Version 2.0) In XBP 2.0, the Use ABAP Program default does not work properly. This is an SAP problem.

605483

Authorization checks are not performed when releasing intercepted jobs.

604496

A composite SAP Note on XBP 2.0.

602683

When a parent job name contains a period ("."), the child job is not always registered as such, causing the parent job to finish without waiting until the child job has finished.

487374

Spool list recipient is lost when you use XBP.

458670

Data Archiving: This SAP Note should be implemented when using XBP 1.0 on SAP 4.6C.

330267

Importing Control-M Function Modules to Unicode SAP systems. See Installing the Control-M Function Modules in a Unicode SAP system.

182963

Due to Control-M usage, the SAP table TXMILOGRAW rapidly increases in size. To resolve this problem:

  • Follow general instructions for configuring Standard Jobs, as described in SAP Note 16083.
  • If this does not resolve the problem, configure SAP_REORG_XMILOG to delete XMI logs more frequently.
  • When using SAP releases earlier than 4.6C, follow the instructions in SAP Note 182963.

101146

Problems with background processing authorizations

16083

A review of Standard Jobs and Reorganization jobs. See also SAP Note 182963.

1721035

XBP 3.0: The function BAPI_XBP_VARIANT_CHANGE does not change the description of a Variant.

Parent Topic

Control-M for SAP overview