Guidelines SLcM BW

Guideline – BW Content 3.53 and 7.03 for Student Lifecycle Management

Applies to: This document describes how to do reporting with BW extractors for 3.53 and 7.0.3 BW content and Student Lifecycle Management EHP 3 and EHP 4.

Summary This document provides a guideline to install and configure the delivered BW content for SAP Student Lifecycle Management, both BW 3.5 and 7.0.

Author: Marco Gruenthaler

Company: SAP AG

Updated on: 6 March 2009

Author Bio Marco Gruenthaler works as an intern at SAP’ IBU for Higher Education and Research.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com © 2009 SAP AG 1


Table of Contents Definition / Basics ...............................................................................................................................................6

Data Warehousing ..........................................................................................................................................6 Flow of Data ....................................................................................................................................................6 Persistent Staging Area (PSA)........................................................................................................................7 Info Package ...................................................................................................................................................7 DataSource .....................................................................................................................................................7 Data Transfer Process (DTP) .........................................................................................................................7 Transformation ................................................................................................................................................7 InfoSource.......................................................................................................................................................7 Info Objects .....................................................................................................................................................7 Info Provider....................................................................................................................................................7 Data Storage Object (DSO) ............................................................................................................................8 Transfer Rules.................................................................................................................................................8 Update Rules ..................................................................................................................................................8

Content Activation...............................................................................................................................................9 Replication of DataSources ............................................................................................................................9 Activation of the Content ...............................................................................................................................10

3.5 Content Configuration.................................................................................................................................13 7.0 Content Configuration.................................................................................................................................14

Activate DataSources....................................................................................................................................14 Transformation ..............................................................................................................................................14 DTP ...............................................................................................................................................................15 InfoPackage ..................................................................................................................................................16

Data Loading ....................................................................................................................................................17 Manual data load...........................................................................................................................................17

3.5 Content ................................................................................................................................................................17 7.0 Content ................................................................................................................................................................17

Process chain................................................................................................................................................18 Building a process chain ............................................................................................................................................18 Scheduling the process chain ....................................................................................................................................21

Queries .............................................................................................................................................................22 Queries for Admissions.................................................................................................................................22 Queries for Registrations ..............................................................................................................................22 Queries for Specialization .............................................................................................................................22 Queries for Module Booking .........................................................................................................................22 Queries for Event Offering ............................................................................................................................22 Queries for Program Completions ................................................................................................................22 Queries for Stage Completions.....................................................................................................................22 Queries for Program Type Progression ........................................................................................................22



Appendix...........................................................................................................................................................23 3.5 Content....................................................................................................................................................23

Academic Structure....................................................................................................................................................23 Academic Period..................................................................................................................................................23 Academic Session................................................................................................................................................23 Campus................................................................................................................................................................23 Module Group ......................................................................................................................................................24 Program ...............................................................................................................................................................24 Qualification .........................................................................................................................................................24

Student Master Data ..................................................................................................................................................25 Academic Standing ..............................................................................................................................................25 Admission Category .............................................................................................................................................25 Admission Status .................................................................................................................................................25 Admission Status Supplement .............................................................................................................................25 Campus (Text) .....................................................................................................................................................26 Cancellation Reason ............................................................................................................................................26 Challenge Group..................................................................................................................................................26 Challenge Type....................................................................................................................................................26 County of Residence............................................................................................................................................27 Data Privacy Level ...............................................................................................................................................27 Degree Level........................................................................................................................................................27 Degree Type ........................................................................................................................................................27 Discipline..............................................................................................................................................................28 Ethnic Origin ........................................................................................................................................................28 Leave of Absence Reason ...................................................................................................................................28 Main Module Group Category ..............................................................................................................................28 Module Group (Text) ............................................................................................................................................29 Part-Time Study (Indicator) ..................................................................................................................................29 Program (Text) .....................................................................................................................................................29 Program Choice ...................................................................................................................................................30 Program Type ......................................................................................................................................................30 Program/Specialization ........................................................................................................................................30 Progress Classification.........................................................................................................................................30 Qualification (Text) ...............................................................................................................................................31 Qualification Group ..............................................................................................................................................31 Registration Classification....................................................................................................................................31 Registration Status...............................................................................................................................................31 Registration Type.................................................................................................................................................32 Religious Denomination .......................................................................................................................................32 Residence Status .................................................................................................................................................32 Sessional Registration Status Specification .........................................................................................................32 Social Class .........................................................................................................................................................33 Stage....................................................................................................................................................................33 Student Fee Category ..........................................................................................................................................33 Student Group......................................................................................................................................................33



Student Administration...............................................................................................................................................34 Admissions...........................................................................................................................................................34 Registrations ........................................................................................................................................................35 Specializations .....................................................................................................................................................35 Student.................................................................................................................................................................36 Student (Text) ......................................................................................................................................................37 Study....................................................................................................................................................................37 Study (Text) .........................................................................................................................................................38 Business Partner..................................................................................................................................................38 Organizational Unit...............................................................................................................................................38 Default academic session ....................................................................................................................................38

7.0 Content (for Student Lifecycle Management release EHP 3) .................................................................39 Academic Structure....................................................................................................................................................39

Academic Period Unit (Text) ................................................................................................................................39 Event....................................................................................................................................................................39 Event Package.....................................................................................................................................................39 Event Package Texts ...........................................................................................................................................40 Event Texts ..........................................................................................................................................................40 Event Type...........................................................................................................................................................40 Event Type Texts .................................................................................................................................................40 Module .................................................................................................................................................................41 Module Texts .......................................................................................................................................................41 Object Type..........................................................................................................................................................41 Module Offering....................................................................................................................................................42

Student Master Data ..................................................................................................................................................42 Academic Scale Identification ..............................................................................................................................42 Academic Level....................................................................................................................................................42 Alternative assessment method ...........................................................................................................................43 Alternative assessment method Texts .................................................................................................................43 Appraisal remark..................................................................................................................................................43 Appraisal Type .....................................................................................................................................................43 Appraisal completed.............................................................................................................................................43 Appraisal status....................................................................................................................................................44 Appraisal type ......................................................................................................................................................44 Booking reason ....................................................................................................................................................44 Calculation point...................................................................................................................................................44 Cancellation reason .............................................................................................................................................44 Ceremony category..............................................................................................................................................45 Conditional Booking .............................................................................................................................................45 Delivery Mode ......................................................................................................................................................45 Due date schedule ...............................................................................................................................................45 Event Package Category .....................................................................................................................................45 Exclusion Indicator for Module Bookings .............................................................................................................46 Exclusion Indicator for Module Bookings text.......................................................................................................46 External Academic Work or Qualification Transferred..........................................................................................46 Grade Assignment Category................................................................................................................................46 Graduation reason ...............................................................................................................................................46



Graduation status.................................................................................................................................................47 Module Booking Status ........................................................................................................................................47 Module Category..................................................................................................................................................47 Module Fee Category...........................................................................................................................................47 No credit assignment ...........................................................................................................................................47 Performance index ...............................................................................................................................................48 Processing Status for Academic Events Planning ...............................................................................................48 Progression Category ..........................................................................................................................................48 Progression Result Status....................................................................................................................................48 Qualification not achieved ....................................................................................................................................48 Repetition type .....................................................................................................................................................49 Session pattern ....................................................................................................................................................49 Special Fee Category...........................................................................................................................................49 Teaching method .................................................................................................................................................49 Waitlist Booking....................................................................................................................................................49

Student Administration...............................................................................................................................................50 Module Booking ...................................................................................................................................................50 Program Completions ..........................................................................................................................................52 Stage Completions...............................................................................................................................................53 Program Type Progression ..................................................................................................................................54

7.0 Content (for Student Lifecycle Management release EHP 4) .................................................................55 Performance Indices ............................................................................................................................................55

How to extract customer fields......................................................................................................................56 Enhance the DataSource...........................................................................................................................................56 Implement the BAdI RSU5_SAPI_BADI ....................................................................................................................57 Modify the DSO object 0HE_DS06 and the InfoSource 0HE_SLC_MBK_1 ..............................................................59

Unit of Measurement.....................................................................................................................................59 Copyright...........................................................................................................................................................60



Definition / Basics

Data Warehousing

The reporting, analysis, and interpretation of business data is of central importance to a company in guaranteeing its competitive edge, optimizing processes, and enabling it to react quickly and in line with the market.

Company data is usually spread across several applications that are used for entering data. Analyzing this data is not only difficult because it is spread across several systems but because the data is saved in a form that is optimized for processing, not analysis.

Data analysis represents additional system load which affects operative data processing. Furthermore, the data has come from heterogeneous applications and is therefore only available in heterogeneous formats which must first be standardized. The applications also only save historic data to a limited extent. This historic data can be important in analysis.

Therefore separate systems are required for storing data and supporting data analysis requirements. This type of system is called a data warehouse.

A data warehouse serves to integrate data from heterogeneous sources, transform, consolidate, clean up and store this data, and stage it efficiently for analysis and interpretation purposes.

Flow of Data

The data flow in the Data Warehouse describes which objects are needed at design time and which objects are needed at runtime to transfer data from a source to BI and cleanse, consolidate and integrate the data so that it can be used for analysis, reporting and possibly for planning. You can use any data sources that transfer the data to BI or access the source data directly, apply simple or complex cleansing and consolidating methods, and define data repositories that correspond to the requirements of your layer architecture.

The data flow begins with the transfer of data from the source system to the Persistent Staging Area (PSA) using InfoPackages. The data is stored in the PSA using tables, which are based on prior defined DataSources. After that the Data Transfer Process (DTP) transfers the data via transformation into an InfoSource and then to a Data Storage Object (DSO), which is the base for the following queries.



Persistent Staging Area (PSA)

The PSA is the inbound storage area for data from the source systems in the BI system. The requested data is saved, unchanged from the source system. Request data is stored in the transfer structure format in transparent, relational database tables of the BI system in which the request data is stored in the format of the DataSource. The data format remains unchanged, meaning that no summarization or transformations take place, as is the case with InfoCubes.

For further Information lock at SAP Help

Info Package

Before data can be processed in BI, it has to be loaded into the PSA using an InfoPackage. In the InfoPackage, you specify the selection parameters for transferring data into the PSA.

DataSource

In BI, the metadata description of the source data is modeled with DataSources. A DataSource is a set of fields that are used to extract data of a business unit from a source system and transfer it to the entry layer of the BI system or provide it for direct access.


Data Transfer Process (DTP)

You use the data transfer process (DTP) to transfer the data within BI from one persistent object to another object, in accordance with certain transformations and filters. Possible sources for the data transfer include DataSources and InfoProviders; possible targets include InfoProviders and open hub destinations.


Transformation

Using the transformation, data is copied from a source format to a target format in BI. The transformation process thus allows you to consolidate, cleanse, and integrate data. In the transformation, the fields of a DataSource are also assigned to the InfoObjects of the BI system.


InfoSource

An InfoSource is a non-persistent structure consisting of InfoObjects.

You use InfoSources if you want to run two (or more) sequential transformations in the data flow, without storing the data again or if you want to assign two different DataSources to one InfoSource.

If you do not have transformations that run sequentially, you can model the data flow without InfoSources. In this case, the data is written straight to the target from the source using a transformation.


Info Objects

InfoObjects are the smallest units of BI. They are known as business evaluation objects. You map the information in a structured form that is required for constructing InfoProviders. InfoObjects are divided in characteristics, key figures, time characteristics and technical characteristics.


Info Provider

InfoProviders are persistent data repositories that are used in the layer architecture of the Data Warehouse or in views on data. They can provide the data for analysis, reporting and planning. Typical InfoProviders are InfoCubes and Data Storage Objects (DSO).



http://help.sap.com/saphelp_nw04s/helpdata/en/42/fc4ff863aa3255e10000000a1553f7/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/fd/5b725f617ddc40b760cf5396bfcb5d/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/42/f98e07cc483255e10000000a1553f7/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/f8/7913426e48db2ce10000000a1550b0/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/7e/001342743eda2ce10000000a1550b0/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/23/054e3ce0f9fe3fe10000000a114084/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/4d/c3cd3a9ac2cc6ce10000000a114084/content.htm


Data Storage Object (DSO)

A DSO serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level.

A Data Store Object contains key fields (for example, document number/item) and data fields that can also contain character fields (for example, order status, customer) as key figures. Unlike multidimensional data storage using Info Cubes, the data in DataStore objects is stored in transparent, flat database tables. The system does not create fact tables or dimension tables.

This data can be evaluated using a query.


Transfer Rules

When you have maintained the transfer structure and the communication structure, you use the transfer rules to determine how you want the transfer structure fields to be assigned to the communication structure InfoObjects. You can arrange for a 1:1 assignment. You can also fill InfoObjects using routines, formulas, or constants.


Update Rules

Update rules specify how the data (key figures, time characteristics, characteristics) is updated to data targets from the communication structure of an InfoSource. You are therefore connecting an InfoSource with a data target.



http://help.sap.com/saphelp_nw04s/helpdata/en/f9/45503c242b4a67e10000000a114084/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62bfe07211d2acb80000e829fbfe/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/3f/0e503c3c0d563de10000000a114084/content.htm


Content Activation To be able to use the Student Lifecycle Management Business Content as delivered by SAP, it first has to be activated. A pre-requisite of this is that the source system from which you want to load the data is connected to the BW system. Only then you will be able to replicate the DataSources and to load the data.

Replication of DataSources

To replicate the DataSources that are delivered for Student Lifecycle Management, proceed with the steps given below:

Activate the DataSources in the Source System

In the Student Lifecycle Management System run transaction RSA5 and find the node 0IS_HER.

If you can’t find the node you have to run transaction RSA9 (Transfer Application Components) and confirm the security check: “Do you want the content application Transfer Component Hierarchy?” with “Yes”.

If you get the following window, please click on “Create Request” and give it a short description, hit “Save” and then “Continue” (the green check mark).

After that you should see node 0IS_HER in transaction RSA5. Choose it, mark it with F9 and activate the DataSources by hitting the Button ‘Activate DataSources’.

If you get the request-window as shown above again, hit ‘Continue’ (the green check mark) and in the next window too. By now the DataSources should be activated.



Replicate the DataSources in the BW System • Start the BW Administrator Workbench (RSA1). • In the left navigation panel, choose DataSources. • Select the source system from which you want to replicate the DataSources.

• Reload the entire tree containing the DataSources from this source system.

• To find the DataSources for Student Lifecycle Management, navigate as follows: SAP → Higher Education and Research.

• If you cannot find the node in the tree, make sure that you show the empty folders as well.

• Right click on the entry for Higher Education and Research. Choose ‘Replicate Metadata’ to replicate the DataSources. All DataSources delivered by SAP for SLCM will now be replicated. This will take a few minutes.

Beware! If you right click on SAP and choose ‘Replicate Metadata’, all DataSources delivered by SAP will be replicated. This will take a long time! Be careful when you choose.

• If there are popup windows asking how to create a DataSource that does not exists, confirm them with the green checkmark.

Activation of the Content

To activate the Content that is delivered for Student Lifecycle Management, proceed with the steps given below:

• Start the BW Administrator Workbench (RSA1). • In the left panel, choose ‘BI Content’.



• Now choose ‘InfoProviders by InfoAreas`and than ‘Industry Sectors’→ ‘Higher Education and Research’ → ‘Academic Structure’ and ‘Student Management’.

• In the right panel choose ‘Grouping’ and select ‘In Dataflow Before and Aftrwds’ • Next, choose ‘Collection Mode’ and select ‘Collect Automatically’ and then choose ‘Display’ and

select ‘Hierarchy’ • To install the DataStoreObjects drag them from the left to the right. The following ODS are available:

o 0HE_DS01, 0HE_DS02, 0HE_DS03, 0HE_DS04, 0HE_DS05 are on 3.5 basis o 0HE_DS06, 0HE_DS07, 0HE_DS08, 0HE_DS09, 0HE_DS10 are on 7.0 basis and available

with EHP 3 o 0HE_DS11 is available with EHP 4 and is also on 7.0 basis

If a popup window appears, make sure that only your source system is marked. If necessary, unmark the other systems.

• When activating it is useful to do it in the background. Sometimes you may get a time-out when you

activate it in foreground. To activate the content choose ‘Install’ → ‘Install in background’ • If necessary create a ‘Workbench request’ as shown in the source system

When activating the content, it is possible that you get an error message that a certain object is not known/active. Since a lot of objects are activated, it could be that an InfoObject has an attribute that has not been activated yet. This will result in an error since the InfoObject cannot be activated due to depending



objects. This is not a problem. The depending object will be activated somewhere along the line. When it is active, the InfoObject with the error can be activated as well.



3.5 Content Configuration This chapter describes how to create and activate the needed items for the 3.5 content.

At first, we have to create the transfer rules. Right click on a DataSource and choose ‘Create Transfer Rules’.

The DataSource and InfoSource assignment can be found in the BW Content. By confirming this window the assignment will be used. A customer can also define his own InfoSource assignment by creating a new one and selecting the “Other” option.

Confirm this window and in the next screen choose ‘Install in Background’ to install and activate the transfer rule.

After that, the transfer rule is installed and active. Go back to the DataSource tree and refresh it. If the InfoPackage is not created, right click on a DataSource and choose ‘Create InfoPackage’. Give it a name and confirm it. For some DataSources delta loading is available for that look at the appendix.

If the BW Content has been activated correctly, the update rules should be available already. After the activation of the Transfer Rule, refresh the tree and the Update Rule should be listed. If it is not, check the installation of the BW Content or create the rule manually. Update Rules are required for Student, Study, Specializations, Registrations and Admissions.

An overview about the mapping of the fields in the transfer rules is in the appendix.



7.0 Content Configuration This is an example procedure to create the needed items. All necessary items for each DataSource are listed in the appropriate section in this guideline.

Now it is time to create the transformations, the data transfer process (DTP) and the InfoPackage. These things are required to transfer the data from the source to the BW.

Activate DataSources

Go to the Administrator Workbench (RSA1) and open the DataSources for Student Lifecycle Management (Modelling → DataSources → SAP → Higher Education & Research).

All replicated DataSources should be displayed there. Make sure that all DataSources are activated, because they can not be used if they are not active. To activate one, double click on it, choose ‘Display/Change’ and then ‘Activate’.

Transformation

You have to create a transformation at first. Right click on a DataSource and choose ‘Create Transformation’. In the next step choose the target as it is mentioned in the appendix for each DataSource (e.g. the DataSource 0HE_SLC_PCP_1 is assigned to the InfoSource 0HE_SLC_PCP_1). Confirm this.

Note: The use of an InfoSources for transactional data is not required. You can transfer directly from the DataSource to the DSO, but you have to do the mapping by your own. There is no template available. With the use of an InfoSource two transformations are required. The use of an InfoSource is reasonable if you have more than one DataSource. For further information look at SAP Help

After that you have to map the fields. Look at the appropriate section in the appendix in section B for each DataSource. To map the fields, click on one field and move the cursor to the corresponding filed on the right and release. To delete an arrow, right-click on the arrow and select ‘delete’. If you finished mapping, activate this transformation by hitting ‘Activate’. Now refresh your entire tree by hitting the refresh button.


http://help.sap.com/saphelp_nw04s/helpdata/en/44/0243dd8ae1603ae10000000a1553f6/content.htm


Your DataSource should look like this

DTP

Now we have to create the DTP. Right click on the DataSource and choose ‘Create data transfer process’.

Confirm the following window and activate the DTP by hitting ‘Activate’.

Refresh the tree. Your Data Source should look like this.



InfoPackage

At last we have to create the InfoPackage which is needed to start the ETL process.

Right click on the DataSource and choose ‘Create InfoPackage’. Give it a name and confirm.

When creating InfoPackages for the transactional data you have to option to use the delta mechanism. The advantage is that once an initial load has been done, only changed records will be loaded to BW. The DataSources which have this functionality will be mentioned in the appropriate section in this guideline for the DataSource. Change it only form ‘Full Update’ to ‘Initialize Delta Process’ if it is mentioned in the DataSource section in the guideline.

Now hit the ‘Save’ to save the InfoPackage. Refresh your tree. Your DataSource should look like this.



Data Loading There are two ways to load the date. The first one is the manual execution of all InfoPackages and DTPs every time you want to load the data into the data warehouse.

The second way is to build up a process chain which will do the same as we did in the first way, but the advantage is that we have to start the process chain and the rest will be done automatically. The second advantage is that we can schedule this process chain. But building a process chain is a big one time work which needs a little bit of time.

Manual data load

3.5 Content

After creating all necessary items for each DataSources it is now time to load the data. You can do this during the creation of the InfoPackage or at the end.

To load the data double-click on the InfoPackage of a DataSource and choose the tab ‘Schedule’ and then ‘Start’.

The data in the DataStore Objects has to be activated. For this choose the DataStore Object and right click on it, then choose ‘Activate Data’.

This step is necessary for Admission, Registration, Specialization, Student and Study.

7.0 Content

After creating all necessary items for each DataSources it is now time to load the data. You can do this during the creation of the InfoPackage or at the end.

To load the data double-click on the InfoPackage and choose the tab ‘Schedule’ and hit the ‘Start’ Button.

Once the loading is finished you have to start the data transfer process (DTP) (this is valid for all objects).

Double-click on a DTP and hit ‘Execute’.

If this is finished, you might have to activate the data. This can be done via the context menu on the DSO (can be found under the DTP). This step is necessary for Module Booking, Module Offering, Program Completions, Stage Completion, Program Type Progression and Performance Indices.



Process chain

Building a process chain

To build up a process chain go to transaction ‘RSPC’.

To create a new process chain click ‘Create’.

In the following popup window you have to enter a technical name and a description for your process chain.

The technical name can be as long as up to 20 characters. For the start of the technical name beware of the name convention (e.g. it has to start with Z).

After confirming this window a new popup window will appear. You are asked to define a start variant.

That’s the first step in your process chain! Every process chain does have one and only one starting step. A new step of type “Start process” will be added. To be able to define unique start processes for your chain you have to create a start variant. So press on the “create” button, a new pop-up appears:

Here you define a technical name for the start variant and a description. In the next step you define when the process chain will start. You can choose from direct scheduling or start using meta chain or API. With direct scheduling you can define either to start immediately upon activating and scheduling or to a defined point in time like you know it from the job scheduling in any SAP system. With “start using meta chain or API” you are able to start this chain as a sub chain or from an external application via a function module “RSPC_API_CHAIN_START”. Hit the ‘Save’ button and go one step back to the previous window.

Your window should look like this.



If you have defined the starting point for your chain you can add now a loading step for loading master data or transaction data. For all of this data choose “Execute infopackage” from all available process types. See picture below:

You can easily move this step with drag & drop from the left on the right side into your design window. A new pop-up window appears. Here you can choose which InfoPackage you want to use. You can’t create a new one here. Press F4 help and a new window will pop-up with all available InfoPackages sorted by use. At the top are InfoPackages used in this process chain, followed by all other available InfoPackages not used in the process chain. Choose one and confirm. This step will now be added to your process chain. Your chain should look like this:

To connect these to items you can right click on the start and choose ‘Connect with’ → ‘Load Data’ and then the InfoPackage you want to be the successor. The other way is to click on the starting point and keep the mouse pressed. Move down to the next step and resale the mouse. A new connection is created.

In the next step drag and drop a DTP in your process chain. In the following window choose the right DTP and confirm.

Now connect the InfoPackage and the DTP. You now get a new popup window.



Here you can choose if this successor step shall be executed only if the predecessor was successful, ended with errors or anyhow if successful or not always execute. With this connection type you can control the behaviour of your chain in case of errors. Whether a step ends successful or with errors is defined in the process step itself. To see the settings for each step you can go to Settings -> Maintain Process Types in the menu. In this window you see all defined (standard and custom) process types.

Your process chain can now look like this.

You can now add all other steps necessary. By default the process chain itself suggests successors and predecessors for each step. For loading transaction data with an InfoPackage it usually adds steps for deleting and creating indexes on a cube. You can switch off this behaviour in the menu under “Settings -> Default Chains". In the pop-up choose “Do not suggest Process” and confirm.

If you finished your process chain you can check your chain with menu “Goto -> Checking View” or press the button “Check”. Your chain will now be checked if all steps are connected, have at least one predecessor. Logical errors are not detected. That’s your responsibility. If the chain checking returns with warnings or is ok you can activate it. If check carries out errors you have to remove the errors first.

After successful checking you can activate your process chain. You can activate your chain with menu “Process chain -> Activate” or press on the activation button in the symbol bar. You will find your new chain under application component "Not assigned". To assign it to another application component you have to change it. Choose "application component" button in change mode of the chain, save and reactivate it. Then refresh the application component hierarchy. Your process chain will now appear under new application component.



Scheduling the process chain

After successful activation you can now schedule your chain. Press button “Schedule” or menu “Execution -> schedule”. The chain will be scheduled as background job. You can see it in SM37. You will find a job named “BI_PROCESS_TRIGGER”. Unfortunately every process chain is scheduled with a job with this name. In the job variant you will find which process chain will be executed. During execution the steps defined in RSPCPROCESSCHAIN will be executed one after each other. The execution of the next event is triggered by events defined in the table. You can watch SM37 for new executed jobs starting with “BI_” or look at the protocol view of the chain.

If there is an error while scheduling the process chain, double click at the start of the chain and select ‘Change Selections’. In the following window choose ‘Immediate’ if you want to start the process chain right now. Hit the ‘Save’ Button and go back to the process chain view.

You can check chain execution for errors in the protocol or process chain log. Choose in the menu “Go to -> Log View”. You will be asked for the time interval for which you want to check chain execution. Possible options are today, yesterday and today, one week ago, this month and last month or free date. For us option “today” is sufficient.

Here is an example of another chain that ended incorrect:

On the left side you see when the chain was executed and how it ended. On the right side you see for every step if it ended successfully or not. As you can see the two first steps were successful and step “Load Data” of an InfoPackage failed. You can now check the reason with context menu “display messages” or “Process monitor”. “Display messages” displays the job log of the background job and messages created by the request monitor. With “Process monitor” you get to the request monitor and see detailed information why the loading failed.



Queries With the delivery of the Business Content, Student Lifecycle Management delivers a number of queries. The queries are split up over each of the DataStore Object (DSO) that they analyze. These queries serve as an example / implementation accelerator.

Queries for Admissions • Admission by Admission Attributes, Hierarchical 0HE_DS01_Q0001 • Admission by Admission Attributes, Non-Hierarchical 0HE_DS01_Q0002 • Admission, Mid-cycle Analysis, Comparison List 0HE_DS01_Q0003 • Admission by Student Demographics Attributes, Hierarchical 0HE_DS01_Q0004

Queries for Registrations • Registration, Hierarchical, O-O-SC 0HE_DS02_Q0001 • Registration by faculty (Principal Org Unit of Student) 0HE_DS02_Q0002 • Registration Hierarchical, by Student Demographics Data 0HE_DS02_Q0003 • Registration, Hierarchical, O-O_SC, Multi-year 0HE_DS02_Q0004 • Registration by Day of Registration 0HE_DS02_Q0005 • Registration Geographical (Based on Main Address) 0HE_DS02_Q0006

Queries for Specialization • Specialization by Module Group Attributes, Hierarchical 0HE_DS03_Q0001 • Specialization by Student Attributes, Hierarchical 0HE_DS03_Q0002

Queries for Module Booking • Module Bookings by Booking Status 0HE_DS06_Q0001 • Module Bookings by Student & Period 0HE_DS06_Q0002 • Student Course Report 0HE_DS06_Q0003

Queries for Event Offering • Event Offers 0HE_DS07_Q0001

Queries for Program Completions • Program Completions by Qualification and Status 0HE_DS08_Q0001

Queries for Stage Completions • Stage Completions by Program, Student and Grade 0HE_DS09_Q0001

Queries for Program Type Progression • Progression Results by Program Type, Category and Result 0HE_DS10_Q0001



Appendix

3.5 Content

Academic Structure

In the navigation tree open ‘Academic Structure’. Activate all DataSources if necessary.

Academic Period

Assign the DataSource 0HE_YRSES_ATTR to the InfoSource 0HE_YRSES. Map the fields and create an InfoPackage to load the data.

Academic Session

Assign the DataSource 0HE_PERID_TEXT to the InfoSource 0HE_PERID. Map the fields and create an InfoPackage to load the data.

Campus

Assign the DataSource 0HE_CAMPUS_ATTR to the InfoSource 0HE_STCAMP. Map the fields and create an InfoPackage to load the data.



Module Group

Assign the DataSource 0HE_MODGRP_ATTR to the InfoSource 0HE_MODGRP. Map the fields and create an InfoPackage to load the data.

Program

Assign the DataSource 0HE_PRGRM_ATTR to the InfoSource 0HE_PRGRM. Map the fields and create an InfoPackage to load the data.

Qualification

Assign the DataSource 0HE_CQUAL_ATTR to the InfoSource 0HE_CQUAL. Map the fields and create an InfoPackage to load the data.



Student Master Data

In the navigation tree open ‘Student Master Data’. Activate all DataSources if necessary.

Academic Standing

Assign the DataSource 0HE_ACSTND_TEXT to the InfoSource 0HE_ACSTND. Map the fields and create an InfoPackage to load the data.

Admission Category

Assign the DataSource 0HE_ADMCTG_TEXT to the InfoSource 0HE_ADMCTG. Map the fields and create an InfoPackage to load the data.

Admission Status

Assign the DataSource 0HE_ADMST_TEXT to the InfoSource 0HE_ADMST. Map the fields and create an InfoPackage to load the data.

Admission Status Supplement

Assign the DataSource 0HE_STSUPL_TEXT to the InfoSource 0HE_STSUPL. Map the fields and create an InfoPackage to load the data.



Campus (Text)

Assign the DataSource 0HE_CAMPUS_TEXT to the InfoSource 0HE_CAMPUS. Map the fields and create an InfoPackage to load the data.

When loading texts for this object, you have to specify the object type F.

Cancellation Reason

Assign the DataSource 0HE_CNCRSN_TEXT to the InfoSource 0HE_CNCRSN. Map the fields and create an InfoPackage to load the data.

Challenge Group

Assign the DataSource 0HE_CHGRP_TEXT to the InfoSource 0HE_CHGRP. Map the fields and create an InfoPackage to load the data.

Challenge Type

Assign the DataSource 0HE_CHTYP_TEXT to the InfoSource 0HE_CHTYP. Map the fields and create an InfoPackage to load the data.



County of Residence

Assign the DataSource 0HE_RCNTRY_TEXT to the InfoSource 0HE_RCNTRY. Map the fields and create an InfoPackage to load the data.

Data Privacy Level

Assign the DataSource 0HE_CONFID_TEXT to the InfoSource 0HE_CONFID. Map the fields and create an InfoPackage to load the data.

Degree Level

Assign the DataSource 0HE_DEGLVL_TEXT to the InfoSource 0HE_DEGLVL. Map the fields and create an InfoPackage to load the data.

Degree Type

Assign the DataSource 0HE_DEGTYP_TEXT to the InfoSource 0HE_DEGTYP. Map the fields and create an InfoPackage to load the data.



Discipline

Assign the DataSource 0HE_MDISC_TEXT to the InfoSource 0HE_MDISC. Map the fields and create an InfoPackage to load the data.

Ethnic Origin

Assign the DataSource 0HE_ETHNIC_TEXT to the InfoSource 0HE_ETHNIC. Map the fields and create an InfoPackage to load the data.

Leave of Absence Reason

Assign the DataSource 0HE_LVRSN_TEXT to the InfoSource 0HE_LVRSN. Map the fields and create an InfoPackage to load the data.

Main Module Group Category

Assign the DataSource 0HE_CATGRY_TEXT to the InfoSource 0HE_CATGRY. Map the fields and create an InfoPackage to load the data.



Module Group (Text)

Assign the DataSource 0HE_MODGRP_TEXT to the InfoSource 0HE_MODGRP. Map the fields and create an InfoPackage to load the data.

When loading texts for this object, you have to specify the object type CG.

Part-Time Study (Indicator)

Assign the DataSource 0HE_PARTT_TEXT to the InfoSource 0HE_PARTT. Map the fields and create an InfoPackage to load the data.

Program (Text)

Assign the DataSource 0HE_PRGRM_TEXT to the InfoSource 0HE_PRGRM. Map the fields and create an InfoPackage to load the data.

When loading texts for this object, you have to specify the object type SC.



Program Choice

Assign the DataSource 0HE_CHOICE_TEXT to the InfoSource 0HE_CHOICE. Map the fields and create an InfoPackage to load the data.

Program Type

Assign the DataSource 0HE_PRTYPE_TEXT to the InfoSource 0HE_PRTYPE. Map the fields and create an InfoPackage to load the data.

Program/Specialization

Assign the DataSource 0HE_LDOBJ_TEXT to the InfoSource 0HE_LDOBJ. Map the fields and create an InfoPackage to load the data.

Progress Classification

Assign the DataSource 0HE_PRGCLS_TEXT to the InfoSource 0HE_PRGCLS. Map the fields and create an InfoPackage to load the data.



Qualification (Text)

Assign the DataSource 0HE_CQUAL_TEXT to the InfoSource 0HE_CQUAL. Map the fields and create an InfoPackage to load the data.

When loading texts for this object, you have to specify the object type CQ.

Qualification Group

Assign the DataSource 0HE_CQGRP_TEXT to the InfoSource 0HE_CQGRP. Map the fields and create an InfoPackage to load the data.

Registration Classification

Assign the DataSource 0HE_REGCLS_TEXT to the InfoSource 0HE_REGCLS. Map the fields and create an InfoPackage to load the data.

Registration Status

Assign the DataSource 0HE_REGST_TEXT to the InfoSource 0HE_REGST. Map the fields and create an InfoPackage to load the data.



Registration Type

Assign the DataSource 0HE_REGTY_TEXT to the InfoSource 0HE_REGTY. Map the fields and create an InfoPackage to load the data.

Religious Denomination

Assign the DataSource 0HE_KONFE_TEXT to the InfoSource 0HE_KONFE. Map the fields and create an InfoPackage to load the data.

Residence Status

Assign the DataSource 0HE_RESST_TEXT to the InfoSource 0HE_RESST. Map the fields and create an InfoPackage to load the data.

Sessional Registration Status Specification

Assign the DataSource 0HE_REGSTE_TEXT to the InfoSource 0HE_REGSTE. Map the fields and create an InfoPackage to load the data.



Social Class

Assign the DataSource 0HE_SOCIAL_TEXT to the InfoSource 0HE_SOCIAL. Map the fields and create an InfoPackage to load the data.

Stage

Assign the DataSource 0HE_STAGE_TEXT to the InfoSource 0HE_STAGE. Map the fields and create an InfoPackage to load the data.

Student Fee Category

Assign the DataSource 0HE_FEECAT_TEXT to the InfoSource 0HE_FEECAT. Map the fields and create an InfoPackage to load the data.

Student Group

Assign the DataSource 0HE_STGRP_TEXT to the InfoSource 0HE_STGRP. Map the fields and create an InfoPackage to load the data.



Student Administration

In the navigation tree open ‘Student Administration’. Activate all DataSources if necessary.

Admissions

Assign the DataSource 0HE_SLC_ADM_1 to the InfoSource 0HE_SLC_ADM_1. Map the fields and create an InfoPackage to load the data. For this InfoSource delta loading is available. Have this in mind by creating the InfoPackage.



Registrations

Assign the DataSource 0HE_SLC_REG_1 to the InfoSource 0HE_SLC_REG_1. Map the fields and create an InfoPackage to load the data. For this InfoSource delta loading is available. Have this in mind by creating the InfoPackage.

Specializations

Assign the DataSource 0HE_SLC_SPC_1 to the InfoSource 0HE_SLC_SPC_1. Map the fields and create an InfoPackage to load the data. For this InfoSource delta loading is available. Have this in mind by creating the InfoPackage.



Student

The Student objects needs special handling. The data should be loaded from the DataSource, to the InfoSource, to the DataStore Object (ODS) and then in the InfoObject (instead of from DataSource, to the InfoSource and directly in the InfoObject). The reason is that if you change the Student Data more than once during the days, the complete Student image is loaded into BW multiple times. To ensure data consistency, a DataStore Object is used to consolidate this data. The same holds for the Study data.

Assign the DataSource 0HE_STUDNT_ATTR to the InfoSource 0HE_SLC_ST_1. Map the fields and create an InfoPackage to load the data. For this InfoSource delta loading is available. Have this in mind by creating the InfoPackage.

The update rules should be created automatically. If not please create them.

InfoSource to DataStore Object

Right click on the DataStore Object (ODS) for Student and Create Update Rules. For the DataSource you select to InfoSource 0HE_SLC_ST_1. After that, the mapping should be defaulted. Activate it.

DataStore Object to InfoObject

Right click on the InfoObject Student and Create Update Rules. For the DataSource you select the DataStore Object (ODS) Object 0HE_DS04. After that, the mapping should be defaulted. Activate it.



Student (Text)

Assign the DataSource 0HE_STUDNT_TEXT to the InfoSource 0HE_SLC_ST_1. Map the fields and create an InfoPackage to load the data. As target for the InfoPackage choose ‘Student (Texts)’.

Study

Assign the DataSource 0HE_STUDY_ATTR to the InfoSource 0HE_SLC_CS_1. Map the fields and create an InfoPackage to load the data. For this InfoSource delta loading is available. Have this in mind by creating the InfoPackage.

The update rules should be created automatically. If not please create them.

InfoSource to DataStore Object

Right click on the DataStore Object (ODS) for Student and Create Update Rules. For the DataSource you select to InfoSource 0HE_SLC_CS_1. After that, the mapping should be defaulted. Activate it.

DataStore Object to InfoObject

Right click on the InfoObject Student and Create Update Rules. For the DataSource you select the DataStore Object (ODS) Object 0HE_DS05. After that, the mapping should be defaulted. Activate it.



Study (Text)

Assign the DataSource 0HE_STUDY_TEXT to the InfoSource 0HE_SLC_CS_1. Map the fields and create an InfoPackage to load the data. As target for the InfoPackage choose ‘Study (Texts)’.

Business Partner

In the BW Administrator Workbench, open the DataSources for your source system (DataSources → PI Basis → Business Partner → Business Partner Master Data).

Assign the InfoSource BP: Master Record (0BPARTNER_ATTR) to the DataSource 0BPARTNER_ATTR of your Source System and map the corresponding fields.

For this InfoSource delta loading is available. Have this in mind by creating the InfoPackage.

Organizational Unit

In the BW Administrator Workbench, open the DataSources for your source system (DataSources → SAP Application Components → Personnel Management → Organizational Management → Organizational Management Master Data).

Assign the InfoSource Organizational Unit (0ORGUNIT) to the DataSource 0ORGUNIT_ATTR of your Source System.

Map the corresponding fields. Create an InfoPackage to load the data.

Default academic session

When an admission or registration record has no academic session maintained (this can be the case for a full year registration), it is useful to replace this empty session with a different value so that you can report on it in BW. To make a query stating: Show all admission where the session is empty is difficult to make.

Therefore you can use your own defined number to derive this records.

The table T7PIQSWITCH has been extended with the values GROUP → BW and SETTING → DEFSESSION.

When you maintain a value for this switch via the view V_T7PIQSWITCHVAL, this is the value that will be loaded into BW. If you don’t maintain it, the session will remain empty.

Example: Student registers for the whole year 2005. DEFSESSION in V_T7PIQSWITCHVAL = 99. The InfoObject 0HE_YRSES will have the value 2005099 in BW.



7.0 Content (for Student Lifecycle Management release EHP 3)

Academic Structure

In the navigation tree open ‘Academic Structure’. Activate all DataSources.

Academic Period Unit (Text)

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_YSUINT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Event

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_EVENT and ‘ATTRIBUTES’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Event Package

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_EVPACK and ‘ATTRIBUTES’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Event Package Texts

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_EVPACK and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Event Texts

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_EVENT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Event Type

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_EVTYPE and ‘ATTRIBUTES’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Event Type Texts

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_EVTYPE and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Module

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_MODULE and ‘ATTRIBUTES’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Module Texts

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_MODULE and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Object Type

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_OTYPE and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Module Offering

Create the transformation and choose ‘InfoSource’ as Object Type for the InfoSource 0HE_ACO_MOF1. Map the fields and then create the DTP and the InfoPackage.

Here is the mapping for the assignment of the InfoSource to the DSO. This transformation will be created automatically.

Student Master Data

In the navigation tree open ‘Student Master Data’. Activate all DataSources.

Academic Scale Identification

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_GRADSC and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Academic Level

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_ACLEVL and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Alternative assessment method

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_AWRAT and ‘ATTRIBUTES’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Alternative assessment method Texts

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_AWRAT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Appraisal remark

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_APRMRK and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Appraisal Type

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_ARGTYP and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Appraisal completed

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_APCOMP and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Appraisal status

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_APSTAT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Appraisal type

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_APTYPE and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Booking reason

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_MBKRSN and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Calculation point

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_CLCPNT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Cancellation reason

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_MBKCRS and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Ceremony category

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_CRMCAT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Conditional Booking

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_COBOK and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Delivery Mode

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_DELMOD and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Due date schedule

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_DDSCHD and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Event Package Category

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_SECAT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Exclusion Indicator for Module Bookings

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_ANNULM and ‘ATTRIBUTES’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Exclusion Indicator for Module Bookings text

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_ANNULM and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

External Academic Work or Qualification Transferred

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_TRNSFW and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Grade Assignment Category

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_NOGRD1 and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Graduation reason

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_GRDRSN and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Graduation status

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_GRDST and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Module Booking Status

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_MBKST and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Module Category

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_SMCAT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Module Fee Category

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_SMFCAT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

No credit assignment

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_NOCRD and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Performance index

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_PINDEX and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Processing Status for Academic Events Planning

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_EVPRST and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Progression Category

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_PGCAT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Progression Result Status

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_PGSTAT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Qualification not achieved

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_CQFAIL and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Repetition type

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_REPTYP and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Session pattern

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_OFFPAT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Special Fee Category

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_SMLVCT and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.

Teaching method

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_TCHMTH and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage

Waitlist Booking

Create the transformation and choose ‘InfoObject’ as Object Type for the InfoObject 0HE_WTLBK and ‘TEXTS’ as Subtype for Object. Map the fields and then create the DTP and the InfoPackage.



Student Administration

In the navigation tree open ‘Student Master Data’. Activate all DataSources.

Module Booking

Create the transformation and choose ‘InfoSource’ as Object Type for the InfoSource 0HE_SLC_MBK_1. Map the fields and then create the data transfer process. When creating the InfoPackage go to the tab ‘Update’ and choose ‘Initialize Delta Process’.






Program Completions

Create the transformation and choose ‘InfoSource’ as Object Type for the InfoSource 0HE_SLC_PCP_1. Map the fields and then create the data transfer process. When creating the InfoPackage go to the tab ‘Update’ and choose ‘Initialize Delta Process’.




Stage Completions

Create the transformation and choose ‘InfoSource’ as Object Type for the InfoSource 0HE_SLC_SCP_1. Map the fields and then create the data transfer process. When creating the InfoPackage go to the tab ‘Update’ and choose ‘Initialize Delta Process’.




Program Type Progression

Create the transformation and choose ‘InfoSource’ as Object Type for the InfoSource 0HE_SLC_PTP_1. Map the fields and then create the data transfer process. When creating the InfoPackage go to the tab ‘Update’ and choose ‘Initialize Delta Process’.




7.0 Content (for Student Lifecycle Management release EHP 4)

Performance Indices

Create the transformation and choose ‘InfoSource’ as Object Type for the InfoSource 0HE_SLC_PI_1. Map the fields and then create the data transfer process and then the InfoPackage.

Define the formula “CONCATENATE( ACAD_YEAR, ACAD_SESSION )” to concatenate the year and session into one field.




How to extract customer fields

If you want to extract extra/missing fields for a given extractor, a BAdI exists that you can use for this. As example we will enhance the extractor for Module Booking. It currently has only one Program for the Program Usage. In case there is a need to have more than one Program there, following needs to be done.

Enhance the DataSource

Start transaction RSA6 and mark the DataSource you want to extend. Choose ‘Enhance Extraction Structure’.

Enter a name for the DDIC structure you want to create.

In the following screen, define the fields you want to extract additionally and activate the structure.

Activate the structure. The DataSource has now been enhanced with the customer field.



Implement the BAdI RSU5_SAPI_BADI

Start transaction SE18. Enter the BAdI name and choose from the pull-down menu → Implementation Create:

Give a name for the implementation.

The method DATA_TRANSFORM should be implemented in case you want to extract extra fields for master and transactional data.

This BAdI is called after the load of the data has been done. The table C_T_DATA contains all the extracted data. Via a loop over that table you can easily enhance the data. Here is the example coding for the implementation:





Modify the DSO object 0HE_DS06 and the InfoSource 0HE_SLC_MBK_1

The last step is to modify the DataStore Object, the InfoSource and the Transformations. Create an InfoObject (RSD1) ZHE_PRUS2 (Program Usage 2). Via RSA1, goto the InfoProvider view, look up 0HE_DS06 and change it.

Add the ZHE_PRUS2 as a data field. Activate.

Goto the InfoSource view. Look up the InfoSource 0HE_SLC_MBK_1 and add the field ZHE_PRUS2 to the InfoSource. Activate.

Goto the DataSource view and replicate the DataSource 0HE_SLC_MBK_1. Activate it.

Goto the InfoProvider view. You might have to delete the existing Transformation. You can create them with the mapping as given previously. Additionally, map your created field.

That should be it.

Unit of Measurement

Make sure that if you extract data that uses the unit CRH that this is available in the BW system. If not, you might get errors when processing the DTP.




Copyright © Copyright 2009 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C 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, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Documents

Guidelines SLcM BW