Ansicht
Dokumentation

Handling of incorrect data records (enhanced) ( RELNBW_30A_WHM_MONERROR )

rdisp/max_wprun_time - Maximum work process run time   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Short text

Handling of incorrect data records (enhanced)

Use

1. The error handling options in the scheduler as already seen in BW 2.0A (Tab page Update Parameter-> Error handling)

• No update, no reporting

• Valid records updated, no reporting (red request)

• Valid records updated, reporting possible (green request)

Records previously only relevant for tests in the transfer rules, can now also apply for tests in the following processing steps:

• Update rules

• master data-, text- and hierarchy update

• InfoCube update

• referential integrity of InfoObjects against master data tables or ODS objects on the communications structure level.

1. You can now set how the system is to react when the number of received data records differs from the number of updated records in the BW. You can do this in error handlingon the tab page update parameters in the Scheduler.

A difference between the number of received records and the number of updated records can arise when records are sorted, aggregated or added in the following:

• transfer rules

• update rules

• updating

When you set the indicator No aggregation permitted, the system will view the request as incorrect if the number of received records does not match the number of updated records.

Note:

In the case where the number of selected records does not match the number of received records in the BW, this will be considered incorrect, independent of this indicator.

1. While updating in a data target, the system marks the incorrect records and returns them to the error handler which locates the original PSA records and writes the log accordingly.
   This function has still not been implemented for load processes involving ODS objects.
2. An error can occur while updating master data and texts, for example due to characteristic attributes appearing more than once, due to time overlaps, invalid dates or invalid characteristic attributes. When this happens, this is logged with an error message and record number.
   When handling double records, you can set the Scheduler to only update the last data record to a key in a request (compare Release information handling double data records).
3. If errors arise when updating InfoCubes, the system generates new requests for incorrect records in each InfoCube combination amongst which incorrect records are updated in the PSA. The InfoCube, for which records were incorrect, entered these new requests as data targets. For example, if a record is incorrectly updated in two InfoCubes , the system generates a request for this record which contains both InfoCubes as a data target. The requests appear as correctly updated in the PSA tree. These new requests can then be updated in InfoCubes again.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

CPI1466 during Backup   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4233 Date: 20240520 Time: 213650     sap01-206 ( 63 ms )