Ansicht
Dokumentation

/PM0/ABX_UPDATE_JOB - Check Task Table

Vendor Master (General Section)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Purpose

The program /PM0/ABX_UPDATE_JOB is used to update the task table /PM0/ABDUPPJOB.

Integration

The task table /PM0/ABDUPPJOB provides a simplified selection for the update (Update Policies/Contracts mass activity). The data is redundant for the most part, and it can be derived from other data or it must be synchronized.

Prerequisites

Usually the task table /PM0/ABDUPPJOB is synchronized when the underlying data is changed. Due to the loose coupling, in other words the synchronization must be explicitly triggered by the program, errors in program enhancements may result in the task table not being synchronized.

Features

The three major functions can only be executed separately, which means for each execution or scheduling of the program only one of the three options can be chosen:

• Search for missing tasks

Data records are missing in the task table and they are created. Missing data records cause policies/contracts not to be selected by the update, although they should be.

• Search for unnecessary tasks

Data records are unnecessary in the task table and they are deleted. Unnecessary data records cause policies/contracts to be selected by the update, although they do not need to be, or cannot be, processed. This results in unnecessary error message or warnings in the application log of the update run.

• Find tasks to be adjusted

Data records are required in the task table but they are not completely correct. Data records to be adjusted cause policies/contracts to be incorrectly selected by the update (timespot, loading mode, and so on). This results in unnecessary error message or warnings in the application log of the update run.

The program has a test mode which allows you to determine and display the changes of the synchronization.

The program uses simple parallel processing, where you can specify the required number of parallel processes (jobs).

You can also have the option of debugging the parallel processes.

CAUTION: If you select the option to debug the batch jobs, these run in an endless loop. You can use transaction SM50/SM51 to place the processes in the debugger. All the jobs must be removed from the endless loop with the debugger, or they must be cancelled with transaction SM37.

Selection

You can restrict the selection set by:

• Policy number

• Contract number

• Line of business
  
  

Standard Variants

There are no standard variants.

Output

The output consists of:

• Number of data records checked

• Number of data records changed (or to be changed if you are using the test mode)

• List of all data records changed (ALV for direct execution in dialog or list/spool in batch)

• On execution with parallel processing, the jobs created are displayed.
  
  

Activities

You determine that the task table for a policy or contract contains incorrect data. For example, you recognize this because the scheduling processing activities that are displayed in the Inquiry (highest version) show a different activity as the next processing activity from the task table (correspondence dates are not taken into account).

The comparison of task table and scheduled processing activity is a possible way of tracking error messages/warnings of the application log of the update.

CAUTION: The program can be scheduled periodically and executed automatically. Howevever, we do not recommend this since the purpose of the program is the postprocessing of incorrect processes. If it is necessary to execute the program regularly, this would suggest that an error situation exists constantly. If the program is to be used in this form nevertheless, then the result of every execution should be checked in detail.

The periodic execution in test mode may be beneficial if you are concerned about or aware of error situations and it is necessary to monitor them. Data should only be adjusted manually after careful checking.

Example

Example 1:

The task table shows the effective date of March 1, 2018 as the first processing activity.

The next scheduled processing activity has an earlier date, for example February 1, 2018.

In this case, you execute the program with the option "Find Tasks to Be Adjustment" in test mode for the respective policy and check the result. If the result is correct, you execute the program again without test mode.

Example 2:

The task table shows the effective date of January 1, 2019 as the first processing activity.

There is no next processing activity because the contract was reversed.

In this case, you execute the program with the option "Search for unnecessary tasks" in test mode for the respective policy and check the result. If the result is correct, you execute the program again without test mode.

Example 3:

A contract was included in an existing policy.

The next processing activity displayed for the new contract is November 1, 2018.

The task table does not display any next processing activity (no data record).

In this case, you execute the program with the option "Search for missing tasks" in test mode for the respective policy and check the result. If the result is correct, you execute the program again without test mode.

CPI1466 during Backup   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 6101 Date: 20240416 Time: 224318     sap01-206 ( 103 ms )