Ansicht
Dokumentation
Conversion of Data in the Infotype Time Limits/Sequences (1750) (Changed) ( RELNCM_463_PQ_IT1750 )
BAL Application Log Documentation ABAP Short ReferenceThis documentation is copyright by SAP AG.
Short text
Conversion of Data in the Infotype Time Limits/Sequences (1750) (Changed)
Use
The object academic calendar in the infotype Time Limits/Sequences (1750) must be converted.
- The time constraint of infotype 1750 has been changed from 0 (only one record may exist) to 3 (any number of records may exist). The field academic year has been added to the header of this infotype. In this field, you can specify the year for which time limits and time limit sequences are to be displayed. In release CM 462, you could create only one infotype record for each calendar object containing the time limits and time limit sequences of all academic years. You must therefore convert the existing infotype records by running a conversion report.
- The language dependency of infotype 1750 no longer applies in the current release. If you have maintained time limits and time limit sequences in more than one language, database inconsistencies may occur when you convert database table HRP1750 (for example, only one infotype record may remain after conversion and the language of this record cannot be determined beforehand).
- The required functions will be included in one of the upcoming CRTs. Up until this time, you must use transaction PP01 to maintain the academic calendar.
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
Start the report RHIQ_SPLIT_OLD_CA manually once in each client.
Effects on Customizing
Further Information
Addresses (Business Address Services) PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 2025 Date: 20240603 Time: 114941 sap01-206 ( 45 ms )