Ansicht
Dokumentation

RCF_CORRECT_ATTACHMENT_PROP - Sychronization of Attachment Attributes Between Table HRP5134 and KPro

ABAP Short Reference   General Material Data  
This documentation is copyright by SAP AG.

Purpose

You can use this report to correct specific attributes of the attachments stored in Knowledge Provider (KPro).

These attributes are:

• Language (= KPro attribute LANGUAGE)

• Attachment Type (= KPro attribute HR_ATTRIBUTE1)

In SAP E-Recruiting, you can save unstructured data for objects (such as Candidate or Requisition) in the form of attachments within Knowledge Provider (KPro). There is a corresponding entry in the table HRP5134 for each of these attachments. Attachments have specific attributes. Users can change some of these attributes via the user interface. These include the language and attachment type of an attachment.

In the past, changing the attachment attributes via the user interface could lead to inconsistencies: although the change was contained in the table HRP5134, the attachment attributes of the corresponding attachment were not updated in KPro.

To determine if there are any inconsistencies, you must compare the entries for the attachments in table HRP5134 with the corresponding entries for the attachments in KPro. You can then remove any inconsistencies.

Integration

Prerequisites

Features

Selection

The following selection fields are available:

• Object Type

Object type for which you want to determine/remove inconsistencies

• Object ID

IDs of the objects for which you want to determine/remove inconsistencies

• Date of Change

Period containing the change date of the selected attachments

Note

If you do not restrict the object IDs or the change period, the report performs a search of all objects of the specified object type.

Processing modes

The following processing modes are available:

• Change: Determine/Remove Inconsistencies

The report determines the list of object IDs with inconsistent data records for a selected object type and displays this list in the List of Inconsistencies Found view. You can use the Remove Inconsistencies function to correct the inconsistent data records for these object IDs.

Note

When the report is run in the background, it corrects the inconsistent data records directly. In this case, the report does not display an output view.

• Plan: Determine Object IDs for Package

In the Package Size field, you enter the maximum number of objects for which you want to correct the inconsistent data records in one report cycle. The report determines the start and end object IDs of the individual packages for the selected package size, where each object ID pair defines a package of inconsistent data records.

Note

If you want to run the report in the background, you have to select at least the object type.

We recommend you run the report first in planning mode. You can use the start and end object IDs delivered by the report in this case to correct the inconsistent data records for the objects for each package. To do this, you enter as a selection criterion the object IDs that define a package and then choose the processing mode Change: Determine/Remove Inconsistencies.

Standard Variants

Output

The output of the report depends on the processing mode and the type of execution.

Running the report in the foreground

• Processing mode: Change: Determine/Remove Inconsistencies

For the selected object type, the report displays a list of the IDs of the objects with inconsistent data records. The report displays the corresponding number in the header of the output.

Once you have performed the Remove Inconsistencies activity, the report displays for the selected object type a list of the object IDs for which the inconsistent data records could not be corrected. The report displays the corresponding number in the header of the output.

• Processing mode: Plan: Determine Object IDs for Package

For a specified object type, the report displays a list of the start and end object IDs for the selected package size. The output header contains the number of inconsistent data records determined.

Running the report in the background

You can also execute both processing modes in the background. You can then use transaction SM37 to view the relevant output lists.

Activities

1. Enter the selection criteria.
2. Select a processing mode.
3. Run the report.
4. If necessary, choose the Remove Inconsistencies function in the List of Inconsistencies Found view. This step is only necessary if you do not run the report in the background.

Note

If the report determined errors when correcting the inconsistent data records, you can view these errors using the transaction SLG1.

Example

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 6455 Date: 20240520 Time: 110625     sap01-206 ( 98 ms )