Ansicht
Dokumentation

RHIQ_SPLIT_OLD_CA - Conversion Program for CM Infotype 1750 (Time Limits/Sequences)

BAL Application Log Documentation   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Title

Purpose

The structure of the infotype Time Limits/Sequences (1750) in the object academic calendar (CA) was changed in release CM 463. The header of this infotype (database table HRP1750) contains the new field PERYR (academic year). The time constraint of this infotype was changed from 0 (only one record may exist) to 3 (any number of records may exist). You can now create an infotype record for each academic year.

In release CM 462, an academic calendar contained only one infotype 1750 record. In this record, you maintained the dates of several academic years.

Since you now require one infotype record per academic year, you must convert existing data records. This report creates one infotype record per academic year for each academic calendar, enters the dates of this academic year in the infotype record, and writes the academic year in the field PERYR of the infotype record header.

If the existing infotype 1750 record contains no dates, the report writes the value 9999 in the field PERYR. After conversion, you can access the infotype record to assign it an academic year by choosing Campus Management -> Curriculum -> Academic Calendar (transaction PIQCAA) from the SAP menu.

Integration

Prerequisites

You have created academic calendars in the system in release 4.62.

Features

Selection

The report selection screen contains the indicator test mode. This indicator is set by default.

Output

If the indicator test mode is set, the report outputs a list of the infotype 1750 records to be converted in the new data structure. If no infotype records exist, no data is output. We recommend that you run the report in the test mode first to check the consistency of the output.

If the indicator test mode is not set, the report converts the existing infotype records and writes the converted records to the database. The error messages, warnings, and information messages are collected in an application log and output after conversion has been completed. You can evaluate the log with transaction SLG1 (object CM_ACAD_CAL) and delete it with transaction SLG2.

Activities

Start report RHIQ_SPLIT_OLD_CA manually once in each client using transaction SA38 or SE38.

Example

CL_GUI_FRONTEND_SERVICES - Frontend Services   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 2836 Date: 20240601 Time: 114914     sap01-206 ( 64 ms )