SAP IS-HER-CM Campus Management

Release 4.64

Release Notes
© Copyright 2002 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of
Microsoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and
OS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

TM
INFORMIX®-OnLine for SAP and Informix® Dynamic Server are registered trademarks of Informix Software
Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other
Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,
SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG
in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered
trademarks of their respective companies.

Design: SAP Communications Media

SAP AG Table of Contents SAP System
________________________________________________________________

1 IS-HER-CM Campus
Management 1
1.1 Student Business Partner Roles (Changed) 1
1.2 IS-HER-CM-AD Administration 1
1.2.1 Data Model Adjustments Resulting From
Changes to the Study O 1
1.2.2 Data Model for Module Booking (Changed) 2
1.2.3 Module Booking Data Structure (Changed
and Enhanced) 2
1.2.4 Student Address and Communication Data
(Changed and Enhanced 3
1.2.5 BAPIs and Remote-Enabled Function
Modules for Student Master 7
1.2.6 Registration and De-registration
(Changed and Enhanced) 9
1.2.7 Student Search and Duplicate Checks
(Changed) 10
1.2.8 Student Status Management (New) 11
1.2.9 Terminology in Student Administration
(Changed) 11
1.3 IS-HER-CM-AC Student
Accounting 12
1.3.1 Student Address and Communication Data
(Changed and Enhanced 12

________________________________________________________________
SAP AG iii
 SAP System
________________________________________________________________

1 IS-HER-CM Campus Management

1.1 Student Business Partner Roles (Changed)

Use
As of this release, the system automatically assigns only the following two business partner roles when you
create a student master record:
o Student (PSCM10)
o Contract partner (MKK)
It no longer assigns the citizen (PSCI10) and HR payee (HR1000) roles which were required for technical
reasons up until this release.

Effects on Existing Data

During the upgrade, the system automatically deletes the roles which it no longer requires using the
RHIQU464_DELETE_ROLE conversion program.

1.2 IS-HER-CM-AD Administration

1.2.1 Data Model Adjustments Resulting From Changes to the Study O

Use
The data model for storage of registration data has been changed and enhanced in this release following
enhancement of registration and de-registration functions and addition of the change of program function.
Study Object (CS) and Relationships ST-517-CS and CS-514-SC
The system creates only one study object (CS) for each program (SC) in which a student (ST) is registered.
The study object is linked to the student via the new relationship 517 and to the program via relationship 514.
The Object (1000) record and the ST-517-CS and CS-514-SC relationship records of the study object have
the plan status active and the same validity period.
The study object (CS) is a technical object which contains the student data that is linked to a program via
relationship 514. The study objects (CS) you create may not be deleted.
Infotype Study Segments (1769) and Relationship ST-513-CS (New)
The study segment concept is new in release CM 4.64. The system contains one Study Segments (1769)
record for each study segment. This record contains data on the start and end of a study segment.
The system also contains at least one study segment record with relationship 513. Relationship 513 contains
redundant information, with the exception of priority, on the new infotype Study Segments (1769). This
relationship enables you to create structural evaluations with evaluation paths via relationship 513, and
ensures the compatibility of existing programs. Please note that if you change the priority of a program, for

________________________________________________________________
SAP AG 1
 SAP System
________________________________________________________________

example from main program to additional program, the system contains several records with relationship
513. However, existing de-registration data is stored only as additional data in the last record. Therefore,
when evaluating data on the start or end of a study segment, you should not read the additional data of
relationship 513.
Sessional Registration (1771)
The sessional registration status (PR_STATUS field) is new. You can evaluate this field in customer reports
to distinguish between active sessional registrations and leaves of absence. However, when you edit a leave
of absence, the system still writes the value 0003 in the APPTYPE field for reasons of compatibility.
The status specification (PRS_STATE) field is new. You can use this field to distinguish between active and
cancelled records.
The system writes the value 0001 in the SUBTY field of the infotype Sessional Registration (1771).

Effects on Existing Data

Existing registration data is automatically converted during the upgrade with RHIQU464_REGISTRATION
(XPRA: Conversion Program for Registration Data CM 4.63 -> CM 4.64).

Effects on System Administration

Before you evaluate the infotype Sessional Registration (1771) in customer reports, you must determine
whether or not you want to include cancelled registration records. If the infotype contains cancelled
registration records, the PRS_STATE> status specification field contains the value I.

1.2.2 Data Model for Module Booking (Changed)

Use
As of this release, module booking relationships are no longer created between the study (CS) and module
(SM) objects but between the student (ST) and module (SM) objects.

Effects on Existing Data

o The system automatically converts existing module booking data during the upgrade using conversion
program RHIQU464_MODULEREG.
o When the module booking data has been successfully converted, you can delete the old data
(CS-506-SM relationships).

1.2.3 Module Booking Data Structure (Changed and Enhanced)

Use
The following fields have been added to the module booking data structure in this release:
o Module booking reason (BOOKREASON)

________________________________________________________________
SAP AG 2
 SAP System
________________________________________________________________

o Cancellation indicator (ANNULMENT)

o Identification (ID)
The following fields have been moved from the module booking data structure to the appraisal data structure:
o Earned credits (CPGAINED)
o Standard value (NORM_VAL)

Effects on Existing Data

The system automatically converts the existing data with conversion program RHIQU464_MODULEREG.

1.2.4 Student Address and Communication Data (Changed and Enhanced

Use
Up to release CM 4.63, the address data (postal address, phone and fax numbers) and e-mail address of
students was stored in the infotypes Address (1028) and Mail Address (1032) respectively. This
communication data was duplicated in the business partner master record.
As of release CM 4.64, address data is only stored in the business partner record in central address
management. The infotypes Address (1028) and Mail Address (1032) are no longer used for students. You
can now use all the business partner address management functions for students. These functions enable you
to:
o Store an unlimited number of addresses
o Create a sufficient number of address fields of appropriate length
o Store several phone numbers, fax numbers, and e-mail addresses for a single address
o Use a uniform address format for students and related persons
o Improve address checks and input help using a regional structure
o Assign several address types to one address
o Maintain address data in the business partner maintenance transaction
o Define a user-specific address format in the user parameter ADDRESS_SCREEN
The following restrictions apply to this functionality:
o You cannot create an e-mail address without specifying a country for the postal address. (This
restriction only applies in release CM 4.64. It will no longer apply in the next release at which time
address-independent communication data will be implemented.)
o It is no longer possible to change address data retroactively.
o You can only change address data for future dates in the maintenance dialog. The BAPIs for address
data maintenance enable you to access current address data only.

Effects on Customizing
Up to release CM 4.63, you were able to store one address for each address subtype. Now you can store as

________________________________________________________________
SAP AG 3
 SAP System
________________________________________________________________

many addresses as you want. You can define one of these as the standard address, and assign several address
types to each address to designate the address usage.
You may have to create additional address types for students if you have not already done so in a previous
release. As the assignment of address types to addresses represents a different approach, it will not always be
necessary to create an address type for each address subtype.
You can set up address usages in the Customizing activity Define Address Types.
If your system contains student address data, you must maintain or check table T7PIQADRKIND before
starting the conversion report. Detailed instructions on how to use the program are given at the end of this
release note.

Changes to the Interface

Deactivating Maintenance Dialogs for the Infotypes Address (1028) and Mail Address (1032)
As of release CM 4.64, you can no longer maintain the infotypes Address (1028) and Mail Address (1032)
using student master data maintenance (PIQSTM) or transaction PP01.
The tab page that contains this infotype data (PIQADDRM or PIQADDRN) was deactivated in the standard
system.
If you want to display existing records before you convert them, you can use transaction PP01 or activate tab
page PIQADDRM or PIQADDRN in Customizing as described in the activity Change Display and Sequence
of Tab Pages for the duration of the conversion. However, you must make sure to deactivate this tab page
before you start production operation. If you do not, the data will not be updated and obsolete address data
will be displayed.
Activating the New Maintenance Dialogs
As of release CM 4.64, the system has two new tab pages for maintenance of address data in student master
data maintenance:
o PIQBPADD: Direct maintenance of standard address
o PIQBPADO: Address overview (with navigation to address usage maintenance)
The two tab pages are activated in the standard system and therefore visible in master data maintenance
directly after the upgrade. You can make required changes in the activity Change Display and Sequence of
Tab Pages.
The system prevents loss of data through overwriting of new address data with old address data by blocking
student address maintenance until data the end of conversion.

Effects on Existing Data

Existing student address data must be converted with the program RHIQU464_STUDENTADDRESS
(Conversion of Student Address Data from Rel. 4.63 -> Rel. 4.64). You must run this program in each client
that contains student data. When address data has been successfully converted, the system sets the relevant
status in a system table. The system blocks address data maintenance for student master records until
conversion of the current address data has been completed.
The program does not automatically convert future address changes, that is, records of the infotypes
Address (1028) and Mail Address (1032) with a future start date. (This was agreed upon with Campus
Management pilot customers.) However, the conversion program does enable you to create a list of future
address changes which serves as a basis for manual updating of addresses.

________________________________________________________________
SAP AG 4
 SAP System
________________________________________________________________

Detailed instructions on how to convert address data are given at the end of this release note.

Effects on Data Transfer

You must adjust existing programs for transfer of student address data. Detailed information on new and
changed function modules is found in the release note BAPIs and Remote-Enabled Function Modules for
Student Master Data.
You can determine whether you need to make adjustments by generating a where-used list for the function
modules BAPI_STUDENT_CREATEFROMDATA2, BAPI_STUDENT_GETDETAIL2, and
BAPI_STUDENT_CHANGE2. If either of these function modules is used in user-defined programs and this
function module uses the STUDENTEMAIL or STUDENTADDRESS parameter, you must make the
necessary adjustments.

Request for Admission (Internet Service Request)

You must also make a few slight changes to the Internet service request for admission.
To ensure that you can display and edit requests which were submitted with a scenario that uses the old
address structures, you must create a new scenario with the following changes:
o Use the new structures for central address management (piqapp_addresszav, piqapp_adtel,
piqapp_adfax, piqapp_adpag, piqapp_adsmtp, and piqapp_addressusage) as characteristics instead of
the old structures (piqapp_address and piqapp_email).
o Adapt your HTML form to the new structures.
o Use the function module HRIQ_ISR_STUDENT_CREATE_CAM to create a student instead of the
function module HRIQ_ISR_STUDENT_CREATE.
o Replace the function module HRIQ_ISR_CONTFILL_AFTER_SAVE with the function module
HRIQ_ISR_WFCFIL_AFTER_SAVE_CAM.
The function modules from release CM 4.63 have been adjusted so that the data in the old structures is
transferred to the new central address management structures. You therefore do not need to define a new
scenario immediately after the release upgrade, and can still display and edit the requests that were submitted
with the old scenario. You must use the new function modules (see above) in the new scenario.
We strongly recommend that you define a new scenario and keep your old scenario when you convert to
central address management. Only then can you display and edit the requests that were submitted with the
old scenario.

Procedure for Converting Address Data

When you call the selection screen of conversion program RHIQU464_STUDENTADDRESS, you see
whether or not conversion has been run.
Preparing the Conversion
1. Familiarize yourself with the concept of address types and address usages. Decide which address types
you require for students, and create these (Define Address Types). You may already have set up the
address types for address data duplication in release CM 4.63. You should therefore first check the
system settings.
2. During conversion of student address data, the program creates a business partner address for each
existing student address (but only if a business partner address is not already available).
If a student has several addresses, you must designate one of these as the standard address. You can

________________________________________________________________
SAP AG 5
 SAP System
________________________________________________________________

then assign an address type to each address. The assignment of address types is not mandatory.
a) Determine which address subtypes you require for students.
b) If several addresses exist, define which of the address subtypes should be designated as the
standard address during conversion.
c) Specify whether you want to create an address usage for the addresses maintained for an address
subtype.
3. Check the entries in table T7PIQADRKIND, and create any new entries you require (Table
Maintenance):
- Create a table entry for each address subtype including the main address.
- If you want to create an address usage for the address of an address subtype, enter the address type
in the field Address type. Leave the field blank if you do not want the program to create an
address usage during conversion.
- Select one address subtype as the standard address. (This is usually the main address subtype.
- Save your entries.
4. Check the consistency of Customizing settings by choosing Check Customizing on the selection
screen of conversion program RHIQU464_STUDENTADDRESS. (This function is located at the
bottom of the selection screen). Keep adding entries to table T7PIQADRKIND until the check is
performed successfully.
5. Read the conversion program documentation .
6. Run the conversion program for students with address data in the simulation mode. (You can display
the student object ID in the Student File by choosing Utilities -> Technical information.)
a) Examine the error log, and analyze all termination and error messages. For example, a warning
message might indicate that the system was unable to distinguish the area code from the telephone
number.
b) Using the interactive output list, check whether the displayed address list is correct and contains
all the addresses which are not yet in the business partner master record (address overview in
student master data maintenance).
c) If your system contains address data with a future start date, you must also run the conversion
program for one of these students, and check the output.
Testing the Conversion Program
7. Run the conversion program in the simulation mode for all students in the background. You can use
variant SAP &SIMUL_ALL.
- Examine the error log.
- Check the output list for records that were not converted.
- The result statistics provides information on the number of addresses to be converted, and on the
incorrect addresses and future address changes that have to converted manually.
When you have remedied the errors, start the conversion program.
Converting Current Address Data
Run the conversion program in the background for all students with the option process data for today

________________________________________________________________
SAP AG 6
 SAP System
________________________________________________________________

only, or use the variantSAP&CONVTODAY

You need a special authorization to run the conversion program (see program documentation).
During conversion, the system locks all business partners. You must therefore make sure that no users are
editing business partner master records before your start the program.
The system generates a log if conversion was performed successfully for all students. If conversion was not
performed successfully, determine which addresses could not be converted and run the program again.
If the system still contains addresses without business partner records and you have decided to either ignore
them or transfer them manually, you can end conversion by running the program with the Set Status
'completed' indicator set.
Create List of Future Address Changes
If the system contains future address changes, transfer these changes manually. You can create a list of future
address data by running the conversion report with the variant SAP&LISTFUTURE.
Concluding Address Conversion
When address conversion has been completed successfully and the system table is designated as completed,
you can maintain student address data.
Now you can transfers the future address changes to master data. To do so, choose the student in the maintain
student master data transaction by entering the student number. Set the key date to the date of the address
change, enter the address data for this key date, and save your entries.
If the tab page that contains the address data in the infotypes Address (1028) and >LS>Mail Address (1032)
is still activated, deactivate it.

1.2.5 BAPIs and Remote-Enabled Function Modules for Student Master (Changed)

Use
This release contains changes which affect the BAPIs and remote-enabled function modules used in Campus
Management.

BAPIs for Student Master Data:

The existing BAPIs for address data maintenance have been replaced by new BAPIs because of the
changeover from student address to business partner address. For technical reasons, the system no longer
supports the existing BAPIs. Continued use of these BAPIs will lead to data inconsistencies. With the
exception of address data, no other incompatible changes have been made in the interface.
This change means that you may no longer use the following function modules:
o BAPI_STUDENT_GETDETAIL2
o BAPI_STUDENT_CHANGE2
o BAPI_STUDENT_CREATEFROMDATA2
You can replace calls to these function modules by calls to function modules
BAPI_STUDENT_GETDETAIL3, etc. New modules (see below) are now available for reading and editing

________________________________________________________________
SAP AG 7
 SAP System
________________________________________________________________

address data.
As of this release, the following BAPIs are provided for student master data:
o BAPI_STUDENT_GETDETAIL3: Read student master data
You can no longer read student address and communication data with this BAPI. However, this BAPI
now enables you to read the death data of students in addition to its other functions. You may no longer
use the old BAPI_STUDENT_GETDETAIL2 BAPI as of this release.
o BAPI_STUDENT_CHANGE3: Edit student master data
You can no longer change student address and communication data with this BAPI. However, this
BAPI now enables you to process the death data of students in addition to its other functions.
o BAPI_STUDENT_CREATEFROMDATA3: Create student master data
You can no longer create student address and communication data with this BAPI. However, this BAPI
now enables you to process the death data of students in addition to its other functions.
o HRIQ_STUDENT_SEARCH_RFC: Remote-enabled function module that enables you to search by
student and includes a status-dependent student search function
o HRIQ_STUDENT_SIMILAR_GET_RFC: Student duplicate check
For more information, read the release note Student Search and Duplicate Check.

BAPIS for Processing Student Addresses:

o BAPI_STUDENT_ADDRESSES_GET: Read address GUIDs of student

o BAPI_STUDENT_ADDRESS_GETDETAIL: Read detailed student address data for specified address
GUID
o BAPI_STUDENT_ADDRESS_ADD: Create new addresses
o BAPI_STUDENT_ADDRESS_CHANGE: Change existing addresses
o BAPI_STUDENT_ADDRESS_REMOVE: Delete addresses
o BAPI_STUDENT_ADDRESS_GET_NUMB: Read address numbers
SAP facilitates the conversion of address data from infotype 1028 ( Address) to the business partner address
(central address management) by providing the following function modules for value assignment:
o HRIQ_CONVERT_FON_1028_ZAV: Assign CAM phone number to infotype 1028 phone number
o HRIQ_CONVERT_FON_ZAV_1028: Assign phone number to CAM phone number in infotype 1028
o HRIQ_CONVERT_FAX_ZAV_1028: Assign fax number to CAM fax number in infotype 1028
o HRIQ_MAP_BAPIADR_TO_ZAV: Assign address of the 4.63 BAPI address structure to central
address management structure
o HRIQ_MAP_ZAV_TO_BAPIADR: Assign address of CAM address structure to the CM 4.63 BAPI
structure

BAPIS for Processing Visa and Identification Data:

o BAPI_STUDENT_IDENTIFIC_ADD: Create visa and identification data

o BAPI_STUDENT_IDENTIFIC_CHANGE: Change visa and identification data

________________________________________________________________
SAP AG 8
 SAP System
________________________________________________________________

o BAPI_STUDENT_IDENTIFIC_GET: Read all visa and identification data of student

o BAPI_STUDENT_IDENTIFIC_GETDETL: Read visa detailed data
o BAPI_STUDENT_IDENTIFIC_REMOVE: Delete visa and identification data

Student/Related Person Relationships

o You can use the remote-enabled function module HRIQ_STRELPERSON_CREATE to create

relationships between students and related persons. The existing function module
HRIQ_STRELPREL_CREATE may no longer be used as of this release.
o The remote-enabled function module HRIQ_STRELPERSON_CHANGE enables you to change
student/related person relationship data.
o The remote-enabled function module HRIQ_STRELPERSON_DELETE enables you to delete
student/related person relationship data.
o The remote-enabled function module HRIQ_STRELPERSON_DELIMIT enables you to delimit
student/related person relationship data.
o The remote-enabled function module HRIQ_STRELPERSON_GETLISTFROMRP reads the
relationships for a related person.
o The remote-enabled function module HRIQ_STRELPERSON_GETLISTOFRP reads the relationships
for a student.

1.2.6 Registration and De-registration (Changed and Enhanced)

Use
As of release CM 4.64, you can maintain the following attributes for registrations:
o Registration classification
o Completed length of study
The following functions have been added:
o The system creates an activity document for registration and de-registration activities. In this release, an
activity document contains a header but no detailed data.
o You can assign activity-related authorizations.
o The change of program function is new.
The following functions have been changed:
o The layout of the student file and Registration tab page have been changed.
o The system now contains a separate activity for registration and leave of absence. It also contains two
de-registration activities: withdrawal and dismissal. You must choose the required de-registration
activity when you call the de-registration dialog in the student file.
o Up to now, the system deleted the sessional registration (1771) record when you cancelled a
registration for an academic year or academic session. As of this release, the system no longer deletes

________________________________________________________________
SAP AG 9
 SAP System
________________________________________________________________

the sessional registration record but marks it as inactive. If you perform a re-registration at some future
time, the system overwrites the inacative data record as only one record may exist in a given period.
You can determine the registration history from the activity documents.
o The progress classification stage field has been removed from the registration dialogs. The
progression result is now stored in a separate infotype.
o Campus Management terminology has been changed. For more information, see the Terminology
Changes release note.

Effects on Existing Data

Existing registration data is automatically converted during the upgrade. For more information, see the Data
Model Adjustments Resulting From Changes to the Study Object (CS) release note.

Effects on Customizing
You can make the following system settings for the changed functions:
o Set Up Registration Classifications
o Set Up Default Values for Registration
o Assign leave of absence and de-registration reasons to new activities:

Several activities have been created for the new activity-specific authorizations and activity documents.
The old leave of absence (0003) and de-registration (0004) activites have been replaced by the leave
of absence (RL01) and the dismissal (RV01) and withdrawal (RW01) activities. If your system
contains leave of absence reasons and de-registration reasons for the old activities, you must assign
these reasons to the new activities in Customizing. They will not be converted automatically. You can
create the new assignments in the view V_T7PIQPROCRSN01 of table mainteance which is provided
especially for the purpose of reassigning reasons.

You can simply transfer the leave of absence reasons to the new activities. However when assigning
de-registration reasons, you must make sure to distinguish between withdrawal and dismissal.

1.2.7 Student Search and Duplicate Checks (Changed)

Use
The student search function has been improved in this release so that it is now easier to conduct specific and
fuzzy searches.
You can now search for specific students based on their status using the dialog transaction or the new
remote-enabled function module HRIQ_STUDENT_SEARCH_RFC. You can personalize the statuses and
the validity of these statuses. The system then uses these personalized values as defaults in the search help. In
addition, the search help function now allows you search by middle name and birth name.
A new remote-enabled function module has been implemented for duplicate checks. In duplicate checks, the
system now also checks whether the last names of existing students match the birth name of new students.

Effects on Existing Data

If your system contains student master records, you must run the RHIQU464_FILL1702MC conversion

________________________________________________________________
SAP AG 10
 SAP System
________________________________________________________________

program. To facilitate conversion, you can define the following transaction calls:
Program Selection Screen for Building Search Fields
Start Program for Building Search Fields in the Background

See also
Also read the following release notes on new functions:
o BAPIs and Remote-Enabled Function Modules for Student Master Data
o Student Status Management

1.2.8 Student Status Management (New)

Use
Status management functions have been implemented in this Campus Management release. These include
functions for customer and system statuses. The system status is defined by SAP, the customer status by the
customer. The customer status is set in the activities in the dialog or background mode. You can also use
statuses to block activities.
A student status can be program-independent or dependent on a specific program (that is, on the study object
- CS). You can display the customer-specific status in the student header data.
The status has been integrated in the search help. You can therefore use the status as a selection criterion in
search help.
The system status merely represents a duplication of original information from status-relevant infotypes.

Effects on Existing Data

When you have upgraded your system to release CM 4.64, you must run the
RHIQU464_STATUSDUPLICATION conversion program with the SAP&UPGRADE variant to initialize
the status. You can display the results of status duplication using the RHIQU464_LOGDISPLAY program.
To simplify conversion, you can create the following transaction calls:
o Execute Program for Status Duplication
o Display Results

See also
For more information, see Student Search and Duplicate Checks.

1.2.9 Terminology in Student Administration (Changed)

Use
The following terminology was changed in this release:

________________________________________________________________
SAP AG 11
 SAP System
________________________________________________________________

Old term New term

Progression type Program type
Progress classification stage Progress classification
Progress classification category/stage assignment Progress assignment
Registration status Registration type

1.3 IS-HER-CM-AC Student Accounting

1.3.1 Student Address and Communication Data (Changed and Enhanced

Use
Up to release CM 4.63, the address data (postal address, phone and fax numbers) and e-mail address of
students was stored in the infotypes Address (1028) and Mail Address (1032) respectively. This
communication data was duplicated in the business partner master record.
As of release CM 4.64, address data is only stored in the business partner record in central address
management. The infotypes Address (1028) and Mail Address (1032) are no longer used for students. You
can now use all the business partner address management functions for students. These functions enable you
to:
o Store an unlimited number of addresses
o Create a sufficient number of address fields of appropriate length
o Store several phone numbers, fax numbers, and e-mail addresses for a single address
o Use a uniform address format for students and related persons
o Improve address checks and input help using a regional structure
o Assign several address types to one address
o Maintain address data in the business partner maintenance transaction
o Define a user-specific address format in the user parameter ADDRESS_SCREEN
The following restrictions apply to this functionality:
o You cannot create an e-mail address without specifying a country for the postal address. (This
restriction only applies in release CM 4.64. It will no longer apply in the next release at which time
address-independent communication data will be implemented.)
o It is no longer possible to change address data retroactively.
o You can only change address data for future dates in the maintenance dialog. The BAPIs for address
data maintenance enable you to access current address data only.

Effects on Customizing
Up to release CM 4.63, you were able to store one address for each address subtype. Now you can store as

________________________________________________________________
SAP AG 12
 SAP System
________________________________________________________________

many addresses as you want. You can define one of these as the standard address, and assign several address
types to each address to designate the address usage.
You may have to create additional address types for students if you have not already done so in a previous
release. As the assignment of address types to addresses represents a different approach, it will not always be
necessary to create an address type for each address subtype.
You can set up address usages in the Customizing activity Define Address Types.
If your system contains student address data, you must maintain or check table T7PIQADRKIND before
starting the conversion report. Detailed instructions on how to use the program are given at the end of this
release note.

Changes to the Interface

Deactivating Maintenance Dialogs for the Infotypes Address (1028) and Mail Address (1032)
As of release CM 4.64, you can no longer maintain the infotypes Address (1028) and Mail Address (1032)
using student master data maintenance (PIQSTM) or transaction PP01.
The tab page that contains this infotype data (PIQADDRM or PIQADDRN) was deactivated in the standard
system.
If you want to display existing records before you convert them, you can use transaction PP01 or activate tab
page PIQADDRM or PIQADDRN in Customizing as described in the activity Change Display and Sequence
of Tab Pages for the duration of the conversion. However, you must make sure to deactivate this tab page
before you start production operation. If you do not, the data will not be updated and obsolete address data
will be displayed.
Activating the New Maintenance Dialogs
As of release CM 4.64, the system has two new tab pages for maintenance of address data in student master
data maintenance:
o PIQBPADD: Direct maintenance of standard address
o PIQBPADO: Address overview (with navigation to address usage maintenance)
The two tab pages are activated in the standard system and therefore visible in master data maintenance
directly after the upgrade. You can make required changes in the activity Change Display and Sequence of
Tab Pages.
The system prevents loss of data through overwriting of new address data with old address data by blocking
student address maintenance until data the end of conversion.

Effects on Existing Data

Existing student address data must be converted with the program RHIQU464_STUDENTADDRESS
(Conversion of Student Address Data from Rel. 4.63 -> Rel. 4.64). You must run this program in each client
that contains student data. When address data has been successfully converted, the system sets the relevant
status in a system table. The system blocks address data maintenance for student master records until
conversion of the current address data has been completed.
The program does not automatically convert future address changes, that is, records of the infotypes
Address (1028) and Mail Address (1032) with a future start date. (This was agreed upon with Campus
Management pilot customers.) However, the conversion program does enable you to create a list of future
address changes which serves as a basis for manual updating of addresses.

________________________________________________________________
SAP AG 13
 SAP System
________________________________________________________________

Detailed instructions on how to convert address data are given at the end of this release note.

Effects on Data Transfer

You must adjust existing programs for transfer of student address data. Detailed information on new and
changed function modules is found in the release note BAPIs and Remote-Enabled Function Modules for
Student Master Data.
You can determine whether you need to make adjustments by generating a where-used list for the function
modules BAPI_STUDENT_CREATEFROMDATA2, BAPI_STUDENT_GETDETAIL2, and
BAPI_STUDENT_CHANGE2. If either of these function modules is used in user-defined programs and this
function module uses the STUDENTEMAIL or STUDENTADDRESS parameter, you must make the
necessary adjustments.

Request for Admission (Internet Service Request)

You must also make a few slight changes to the Internet service request for admission.
To ensure that you can display and edit requests which were submitted with a scenario that uses the old
address structures, you must create a new scenario with the following changes:
o Use the new structures for central address management (piqapp_addresszav, piqapp_adtel,
piqapp_adfax, piqapp_adpag, piqapp_adsmtp, and piqapp_addressusage) as characteristics instead of
the old structures (piqapp_address and piqapp_email).
o Adapt your HTML form to the new structures.
o Use the function module HRIQ_ISR_STUDENT_CREATE_CAM to create a student instead of the
function module HRIQ_ISR_STUDENT_CREATE.
o Replace the function module HRIQ_ISR_CONTFILL_AFTER_SAVE with the function module
HRIQ_ISR_WFCFIL_AFTER_SAVE_CAM.
The function modules from release CM 4.63 have been adjusted so that the data in the old structures is
transferred to the new central address management structures. You therefore do not need to define a new
scenario immediately after the release upgrade, and can still display and edit the requests that were submitted
with the old scenario. You must use the new function modules (see above) in the new scenario.
We strongly recommend that you define a new scenario and keep your old scenario when you convert to
central address management. Only then can you display and edit the requests that were submitted with the
old scenario.

Procedure for Converting Address Data

When you call the selection screen of conversion program RHIQU464_STUDENTADDRESS, you see
whether or not conversion has been run.
Preparing the Conversion
1. Familiarize yourself with the concept of address types and address usages. Decide which address types
you require for students, and create these (Define Address Types). You may already have set up the
address types for address data duplication in release CM 4.63. You should therefore first check the
system settings.
2. During conversion of student address data, the program creates a business partner address for each
existing student address (but only if a business partner address is not already available).
If a student has several addresses, you must designate one of these as the standard address. You can

________________________________________________________________
SAP AG 14
 SAP System
________________________________________________________________

then assign an address type to each address. The assignment of address types is not mandatory.
a) Determine which address subtypes you require for students.
b) If several addresses exist, define which of the address subtypes should be designated as the
standard address during conversion.
c) Specify whether you want to create an address usage for the addresses maintained for an address
subtype.
3. Check the entries in table T7PIQADRKIND, and create any new entries you require (Table
Maintenance):
- Create a table entry for each address subtype including the main address.
- If you want to create an address usage for the address of an address subtype, enter the address type
in the field Address type. Leave the field blank if you do not want the program to create an
address usage during conversion.
- Select one address subtype as the standard address. (This is usually the main address subtype.
- Save your entries.
4. Check the consistency of Customizing settings by choosing Check Customizing on the selection
screen of conversion program RHIQU464_STUDENTADDRESS. (This function is located at the
bottom of the selection screen). Keep adding entries to table T7PIQADRKIND until the check is
performed successfully.
5. Read the conversion program documentation .
6. Run the conversion program for students with address data in the simulation mode. (You can display
the student object ID in the Student File by choosing Utilities -> Technical information.)
a) Examine the error log, and analyze all termination and error messages. For example, a warning
message might indicate that the system was unable to distinguish the area code from the telephone
number.
b) Using the interactive output list, check whether the displayed address list is correct and contains
all the addresses which are not yet in the business partner master record (address overview in
student master data maintenance).
c) If your system contains address data with a future start date, you must also run the conversion
program for one of these students, and check the output.
Testing the Conversion Program
7. Run the conversion program in the simulation mode for all students in the background. You can use
variant SAP &SIMUL_ALL.
- Examine the error log.
- Check the output list for records that were not converted.
- The result statistics provides information on the number of addresses to be converted, and on the
incorrect addresses and future address changes that have to converted manually.
When you have remedied the errors, start the conversion program.
Converting Current Address Data
Run the conversion program in the background for all students with the option process data for today

________________________________________________________________
SAP AG 15
 SAP System
________________________________________________________________

only, or use the variantSAP&CONVTODAY

You need a special authorization to run the conversion program (see program documentation).
During conversion, the system locks all business partners. You must therefore make sure that no users are
editing business partner master records before your start the program.
The system generates a log if conversion was performed successfully for all students. If conversion was not
performed successfully, determine which addresses could not be converted and run the program again.
If the system still contains addresses without business partner records and you have decided to either ignore
them or transfer them manually, you can end conversion by running the program with the Set Status
'completed' indicator set.
Create List of Future Address Changes
If the system contains future address changes, transfer these changes manually. You can create a list of future
address data by running the conversion report with the variant SAP&LISTFUTURE.
Concluding Address Conversion
When address conversion has been completed successfully and the system table is designated as completed,
you can maintain student address data.
Now you can transfers the future address changes to master data. To do so, choose the student in the maintain
student master data transaction by entering the student number. Set the key date to the date of the address
change, enter the address data for this key date, and save your entries.
If the tab page that contains the address data in the infotypes Address (1028) and >LS>Mail Address (1032)
is still activated, deactivate it.

________________________________________________________________
SAP AG 16