Ansicht
Dokumentation

Academic Sessions, Years and Session Variants ( RELNCM_462_PQ_PERIODE )

BAL_S_LOG - Application Log: Log header data   General Material Data  
This documentation is copyright by SAP AG.

Short text

Academic Sessions, Years and Session Variants

Use

A new academic year concept has been implemented in this release. This new concept affects the definition of session data (start and end dates).

Up to this release, the start and end dates of academic sessions were stored in tables T7PIQYEARPRD and T7PIQSTDYEARPRD. The start and end dates of the academic sessions were stored there for the relevant session/year/session variant combinations.

As of this release, the start and end dates of academic sessions are maintained in the academic calendar (transaction PIQCAA).

The academic calendar now contains the time limit 0100 (start and end of session) which defines the start and end dates of the academic session. Date information stored in the academic calendar is inherited by all lower-level objects. For example, if the top organizational unit has set dates for time limit 0100, these are inherited by all lower-level programs and organizational units.

You can also set up a separate academic calendar with dates that deviate from those maintained in time limit 0100 for individual objects. These dates override those stored in the inherited time limit.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

You must check the settings in the Campus Management Implementation Guide in Master Data -> Academic Years. You must also maintain the required session data in the academic calendar.

Further Information

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

Length: 1829 Date: 20240603 Time: 073619     sap01-206 ( 43 ms )