Portal Administration

HR-PORTAL_ System Maintenance and Technical Documentation
PORTAL ADMINISTRATION
SYSTEM MAINTENANCE AND TECHNICAL DOCUMENT

Release Notices
The present document is extremely confidential and is subject to distribution control. This document
belongs to Wipro Technologies, India. The number and version on the document are allocated to the
person notified in the document distribution list. The person(s) to whom this document is issued will be
responsible for any changes/ reviews to this document. Every copy of this document is subject to Quality
control.
If the document distribution list does not contain the number of copies then it would be an uncontrolled
copy. Uncontrolled copies are outside the scope of the quality control or any QA or QC activity. Persons
who are having such copies should clearly mention with two parallel lines the term “UNCONTROLLED” to
abdicate themselves from any responsibility.
Document Control
Document Distribution Name Approval Date
Prepared by Reviewed by Approved by
Namrata Mohapatra
Version Name Date Change Remarks
Version 1.0 Portal Administration 1st 1st Draft

Cut
Table of Contents
1 Introduction........................................................................................................................................... 6
2 Portal Administration............................................................................................................................ 7
2.1 CREATE A TEST USER ON IGA.........................................................................................7
2.2 CHANGE THE SEQUENCE INTO A DETAILED NAVIGATION MENU......................................8
2.3 CREATE A NEW SGA HR ROLE........................................................................................9
2.4 CREATE A TRAINING USER ON FGA...............................................................................10
Assign a user into a group.................................................................................................................. 11
Links between roles and groups......................................................................................................... 13

2.5 INSTALL A NEW XGA SYSTEM:.....................................................................................13
Transport of the HR content............................................................................................................... 13
Export content from PGA.................................................................................................................... 14
Import content into FGA..................................................................................................................... 15
Users creation.................................................................................................................................... 17
Export users list (HRTRxxxx) from IGA.............................................................................................. 17
Group creation and assignation of users............................................................................................17
Rename groups to reach naming convention.....................................................................................18
Create groups and import users into groups.......................................................................................18
Assignation of role to the groups........................................................................................................ 18
Configuration of SSO:......................................................................................................................... 19
2.6 LAUNCH THE JAVA API................................................................................................24
2.7 MAINTAINING THE DEPLOYMENT TABLE........................................................................28
The transaction................................................................................................................................... 28
2.8 MAINTAINING THE INFORMATION PAGE........................................................................30
Upload of the html file......................................................................................................................... 30
Storage of a picture file....................................................................................................................... 31
Create a new designation................................................................................................................... 32

2.9 TRANSLATE THE PORTAL OBJECT...................................................................................33
Create the translation worklist............................................................................................................ 33
Set up the translation.......................................................................................................................... 35
Publish the translation........................................................................................................................ 36

Transport of the translation................................................................................................................. 36

2.10 TRANSPORT A SGA OBJECT...........................................................................................36
Create the transport package............................................................................................................. 37
Create the transport file...................................................................................................................... 38
Import the transport file....................................................................................................................... 39
Note 1:................................................................................................................................................ 40
Note 2:................................................................................................................................................ 41
2.11 UNLOCKING A SGA OBJECT..........................................................................................41
2.12 INSTALLATION OF PORTAL CERTIFICATE.......................................................................42
2.13 CHECK ACCESS RIGHTS FOR A END USER.......................................................................46
2.14 MAINTAIN STATIC HTML PAGES ON SGA....................................................................56
Prerequisites:...................................................................................................................................... 56
Page Define designation.................................................................................................................... 56

THE CSS FILE..............................................................................................................................58
2.15 MANAGE SYSTEM MESSAGE INFORMATION ON SGA....................................................62
IVIEW “DATA SECURITY POLICY”..............................................................................................62
IVIEW “SYSTEM INFORMATION”.................................................................................................62
IVIEW “WELCOME”.....................................................................................................................63
BSP ZBHHR_XX_C_DSP........................................................................................................63
IVIEW “QUICK INFO ADMINISTRATION”......................................................................................64
CREATION...................................................................................................................................65
MODIFICATION...........................................................................................................................66
COPYING.....................................................................................................................................67
DELETION...................................................................................................................................67
3. Appendix A - Acronyms.......................................................................................................68
1 Introduction
The purpose of this document is to capture information gathered during the knowledge transfer and
structure it for proper system understanding.
2 Portal Administration
Here we provide an insight into the portal administration activities.
2.1 Create a test user on IGA
Pre-requisites for this activity:
You are SGA administrator for HR. You have an access to the test system of SGA called IGA.
You are aware of the complete landscape of SGA and the different roles and responsibilities.
You are used to work with roles, folders, permissions and users on SGA.
You received a request from an IS package leader working on an ESS/MSS scenario. You have:
process and status (employee or manager) of test user to create or logon and group of user to give
authorization.
Creating a user:
The test users are “anonymous”, theirs logons are shaped by the prefix “HR” followed by the process
name (MACO, PD, TEM, ESSMSS for example) and a number on 3 digits.
If you have to create only one or some users, you can use the User Administration tab then Users
link.
Mass creation of user:
For a mass creation of user, you have to use a text file giving the user ID, the password, the e mail
(HRIS SGA e mail for test user), the first and the last name with this design:
[User]
UID=HRTEM121
Password=training121
Email Address=administration.hris-sga@airbus.com
First Name=TEM test user
Last Name=HRTEM121
On the User Administration tab, choose the link Import / Export. Fill in the file parameter and tick the
radio button Overwrite Existing Data. Then click on Import button.
Assign a user into a group:
On the User Administration tab, choose the link Groups. At this step, you can search or key in the
group name. From the proposed list, select the good one and click on the icon “Assign users to ”.
On the screen after, you have the list of already assigned users and a button “plus” to assign a new
user.
Mass assignment:
To assign several users to a group, you can use a file giving the group id, group description and the
list of users using this design:
[Group]
Gid = HR_IGAMACO_XX_EMPLOYEE_GENERIC
Gdesc = Group for training user HR, management of competencies, for employees of all entities.
user=HRTEM002;HRTEM004;HRTEM006;HRTEM008;HRTEM010;HRTEM012;HRTEM014;HRTEM0
16;HRTEM018;HRTEM020;HRTEM022
Use the link Import/ Export as for the mass user creation. The file name should be the group name.
Note that the case (upper or minor) is important. If there is an error in the spelling or in the case, a new
group is created. The file should contain all users already assigned to the group plus the new ones if
the option Overwrite is ticked.
2.2 Change the sequence into a detailed navigation menu
You are SGA administrator for HR. You have an access to the necessary systems of SGA.
You are aware of the complete landscape of SGA and the different roles and responsibilities.
You received a request from an IS package leader working on an ESS/MSS scenario.
In the role or work set directory of the process, choose the page to move and use the buttons up or
down at the bottom of the Iview. The horizontal navigation links (e-HR Services, Manager’s Area for
example) have the parameter Entry point set to yes.
You can also organise pages under a common folder like People Development, using the merge ID.
2.3 Create a new SGA HR role
In the PCD, you create a new role inside the project repertory. This role has to be named using the
naming convention:
hr_<project code>_<XX or entity code>_<employee or manager>_<free text>
In the role, you must use the merge ID field in order to respect the classification convention. All hr role
must be included inside the e-HR Services tab and placed into the Employee’s area or the Manager’s
area. Via the merge id, you can create a new classification in order to group some i-views under a
common folder.
Roles Groups association on PGA:

2.4 Create a training user on FGA
You are SGA administrator for HR. You have an access to the training system of SGA called FGA.
You are used to work with roles, folders, permissions and users on SGA.
You received a request from an IS package leader working on an ESS/MSS scenario. You have:
process and status (employee or manager) of training user to create or logon and group of user to give
authorization.
Create a user
The training users are “anonymous”, theirs logons are shaped by the prefix “HRTR” and a number on
4 digits. If you have to create only one or some users, you can use the User Administration tab then
Users link.
Mass creation of user
For a mass creation of user, you have to use a text file giving the user ID, the password, the e mail
(HRIS SGA e mail for training user), the first and the last name with this design:
[User]
UID=HRTR0121
Password=training0121
Email_Address=administration.hris-sga@airbus.com
First_Name=TRAINING USER
Last_Name=HRTR0121
On the User Administration tab, choose the link Import / Export. Fill in the file parameter and tick the
radio button Overwrite Existing Data. Then click on Import button.
Assign a user into a group
On the User Administration tab, choose the link Groups. At this step, you can search or key in the
group name. From the proposed list, select the good one and click on the icon “Assign users to”.
On the screen after, you have the list of already assigned users and a button to assign a new
user.
2.4.1.1 Tip:
One other solution is to use a “reference” user. Search this user and look the group assigned.
Mass assignment:
To assign several users to a group, you can use a file giving the group id, group description and the
list of users using this design:
[Group]
Gid=HR_FGAMACO_XX_EMPLOYEE_GENERIC
Gdesc=Group for training user HR, management of competencies, for employees of all entities.
user=HRTR0002;HRTR0004;HRTR0006;HRTR0008;HRTR0010;HRTR0012;HRTR0014;HRTR0016;
HRTR0018;HRTR0020;HRTR0022
Use the link Import/ Export as for the mass user creation. The file name should be the group name.
Note that the case (upper or minor) is important. If there is an error in the spelling or in the case, a new
group is created.
The option Overwrite has to be ticked for a creation or a recycling. Be careful because of erase risk.
If the group does not exist: it is created and the logon is assigned.
If the group already exists with one or more logon and if you use a file with the already assigned
logon(s) plus some new ones, without the option overwrite: no change of the group. If the options
overwrite is ticked: the group is updated.
Links between roles and groups
The users are put into a group to be identified by a common feature (entity, process) but it is common
that several groups are linked to the same role. Here after, you can find a document with role(s) and
associated group(s) by process.
2.5 Install a New XGA system:
Pre-requisites of this activity:
You are SGA administrator for HR. You have an access to necessary system of SGA.
Transport of the HR content
Before any transport, the PCD contain not any HR object:

Export content from PGA
On PGA, we have to create a new transport package and insert the whole content of HR directory.
Import content into FGA
On FGA, we have to import the transport file.

After the import, the PCD contain all objects like on PGA.
Users creation
Export users list (HRTRxxxx) from IGA
The export function doesn’t work for huge group. So the users (HRTR001 to HRTR999 and HRPD001
to HRPD099) are mass created using a text file.
Modify e-mail address with HRIS-SGA administration address
Not needed, the e mail address was set up at the mass creation.
Group creation and assignation of users
Export groups (FGA*) from IGA
Select the group called FGA*GENERIC on IGA:

And select for each one the export function. Create a new text file for each one.
Rename groups to reach naming convention
Create groups and import users into groups
Assignation of role to the groups
On the old FGA, for each role of the PCD we have to search which group(s) is (are) linked via the user
administration tab. This produce an excel file.
For example in old FGA user administration tab for role menu, we choose the role which has to be
reassigned in new FGA portal.
We select the role which target on old FGA folder.

Then we do an explain tab in the .xls file which represent group(s) and user(s) assignment for the
selected role (hr_ess_xx_employee in the example).
Then it will be easier to assigned appropriate group(s) and user(s) for each role in the new FGA portal from the xls file.
Configuration of SSO:
Request of certificate to Olivier Rodriguez and Pierre Melan
They will send the certificate by mail:

Configure STRUSTSSO2 transaction in all SHM clients
Import the certificate into SAP R/3 using strustsso2 transaction:
Create "SAP_R3_Human_Ressources" alias for SHM009
Create the alias in FGA portal for SHM009 system:

Transport of the eu_role for Personalize option
Create a transport package named “eu_role” for example in the PGA portal to export the role “eu_role”
for personalizes option.
Then in new FGA portal, import the client transport package file created for eu_role transport package.
Assign eu_role to HR groups
Assign the new eu_role, which stems form PGA eu_role transport package, to all groups in new FGA.
2.6 Launch the JAVA API
On PGA:
Daily portal deployment:
On PHM, the tables ZDTHAU_XX_IN_US and ZDTHAU_XX_OUT_US must be field in by the

deployment program.
The custom table ZDTHAU_XX_API_MO must be flag to “classic”.
Exceptional portal deployment:
On PHM, the tables ZDTHAU_XX_IN_M and ZDTHAU_XX_OUT_M must be field in via SM30.
The custom table ZDTHAU_XX_API_MO must be flag to “cleaning”.
Remark:
The function module used by API is ZFHAU_XX_SGA_GROUP_USER.
In our server, go to Deployment folder to click on MSTSC.exe

To connect on server tosap172 using our generic logon HRISSGA (password HRISSGA14).
Open the scheduled tasks :
We can only touch hr_ume_xx_project_PGA
For a exceptional run, right-click and choose run.
To change the daily run hour, double click.

Once finish, make a logoff hrissga, never, never a shutdown!!!! If not, you can call immediately Pierre
Melan, Olivier Rodriguez, Sebastien Viau and go to security local to leave your badge.
On PGA, check the run
If the run is complete, at the end of log there is « end of task »

On PPC
Daily portal deployment:
On PHA, the tables ZDTHAU_XX_IN_US and ZDTHAU_XX_OUT_US must be field in by the

deployment program.
The custom table ZDTHAU_XX_API_MO must be flag to “classic”.
Exceptional portal deployment:
On PHA, the tables ZDTHAU_XX_IN_M and ZDTHAU_XX_OUT_M must be field in via SM30.
The custom table ZDTHAU_XX_API_MO must be flag to “cleaning”.
Remark:
The function module used by API is ZFHAU_XX_SGA_GROUP_USER
In our server, go to Deployment folder / PPC, Double click on .bat file
If the run is complete, at the end of log there is « end of task »

2.7 Maintaining the deployment table
You are SGA administrator for HR. You have an access to the production system PHM.
You are used to work with roles, folders, permissions and users on SGA.
You received a request from an IS package leader working on an ESS/MSS scenario. You have the
precise description of the involved population.
The transaction
All settings for the deployment program can be done by the transaction ZTHHR_XXMAINTDEPLOY.
In this case, we have to choose the option 3

A new screen is displayed:

For any change, we have to click on export button. So we work on an excel sheet. After updating the
excel sheet, close it before click on import button. Then save to confirm your changes.
This action has to be done directly on the needed system. For each process, we can set many lines to
give the process role for a restricted population.
This population could be restricted by org unit, by link type (NAT, OPE or FUN), by company code
(bukrs), by personnel area (Persa), by personnel Subarea (btrtl), by employee group (persg) and by
employee subgroup (persk). Each of these potential combinations could be restricted also using a
function (zform). The complete line is applied for employee (link 000) or for manager (link 012). But
other links on position can be managed also by the program.
The population described by the line is deployed if the case is ticked.
2.8 Maintaining the Information Page
Pre-requisites of this activity:
You are SGA administrator for HR. You have an access to the necessary system of SGA.
You received a request from the change team to create a new designation or to store a picture file.
Upload of the html file
The online training and documentation is under the responsibility of the Change management team,
they manage the content themselves using html files.
A group has been created especially for this task: TECH_HR_XX_HTMLUPLOAD
So the members of Change team can themselves upload theirs html file on the portal. In fact a BSP is
called to store this file as a binary file into SAP R/3 server. The necessary keys are the designation
title and the language. This action has to be done on each SGA system.
Storage of a picture file
If a picture is included into an information page, this picture has to be store into the folder mime
repository of the BSP application ZBHHR_XX_C_DSP. This action has to be done on DHM and
included into a transport order to be effective on others systems.
The tag in the html file should refer to the file without any path.
Tip: If there is a problem about display, you can make a right click on a page, show the source code,
save it on your hard disk. Then you can change the HTML code and make an upload of this new
version.
Create a new designation
To create a new designation, found the next free number, fill in the 2 fields and click on update.
This number will be used in I view Application parameter

2.9 Translate the portal object
You are SGA administrator for HR. You have now an access to the necessary system of SGA.
You received a request from an IS package leader working on an ESS/MSS scenario.
Create the translation worklist
On DGA system, go through Content Administration and Portal Content Translation tabs to the menu
link Translation Worklist Coordination. Then, in the PCD, choose or create the directory dedicated to
the project into the global directory Translation to create a new translation worklist.
Inside this worklist, you have to put all necessary objects, a good way is to put the whole content of
the project directory for each object type ( Iview, page, role and workset).
After that, you can click on button Generate Translation Data, then on the button Release for
Translation.
And finally, close this i view.

Set up the translation
In the menu, click on link Worklist Translation. Then you can search your worklist (this value is case
sensitive).
The worklist appears only if the status is “released for translation“.
You have to tick the good one and to select the source and target language before click on button
Load for translation.
On the new Iview, you can tick the object to translate and to set the translation, repeat this action for
all necessary objects and click on Save All button. Then you can close the i view.
Back on the first Iview, you have to click on button Mark as Translated to complete the action. The
status is changed to Translated.
Publish the translation
From the menu, go back to the Translation Worklist Coordination console to open again your worklist
and click on Publish translation button.
Transport of the translation
In order to diffuse the translation on others xGA system, you have to perform a classic transport. As
for worklist, a good way is to transport the whole content of the project.
2.10 Transport a SGA Object
You are SGA administrator for HR. You have an access to the necessary systems of SGA.
You received a request from an IS package leader working on an ESS/MSS. You have: name and ID
of the objects to transport and the source and the target systems.
Create the transport package
From the source system (DGA in this example)
In the System Administration tab, choose the link Transport.
In the detailed navigation menu, select Transport Packages, then Export.
Search the folder Transport / HR in the PCD. In it, you will find a folder dedicated to each project.
Make a right click on the dedicated folder to create a new transport package.
The package name and Id should be the same (without space in the ID) and contain the source
system, the project name, the transported objects names and the target system (ex:
DGA_UGO_IVIEW_MyAlert_IGA). After key in the name and ID, you should click on Next then Finish
buttons.
Create the transport file
In this package, you should include all needed objects.
To reach this goal, you will search in the PCD (still in the System Administration tab with the transport
package opened in the overview page), the transportable objects. In the PCD, choose the folders HR,
then A690, then the folder by object type and finally the project dedicated folder. In this last folder,
make a right click on the object and choose the option Add object to transport package.
The template called Static Package content is filled in.
When all needed objects are selected, you have to click on Export button.
Please note that when you want to transport a role or a page, you have also to transport the included
objects like the Iview.
Note : You can ask to xGA to include all needed objects by the radio button Include all objects on
which the exported objects depend after identify the object in the template, BUT THIS OPTION IS
RISKY.
After click on Export button the SAP Web Dynpro is added:
Then you click on Start export button to access to another screen where you could download the
export file on your hard disk.
Import the transport file
From the target system (IGA in this example)

In the System Administration tab, choose the link Transport.
In the detailed navigation menu, select Transport Packages, then Import.
It is important to choose the value client to the parameter Source for Package Files to search the file
on your hard disk.
Then you have to click on upload then on import buttons. At this step, you can choose to overwrite or
not the object. If you keep the default value “all” all objects included in the file are overwritten, if you
choose the value “None”, only the new objects are imported. Be aware that the existing objects are not
updated even if the versions are different between the source and target system.
The transport is done, you can now check the new version of the objects.
Note 1:
On the portal, a transport can not be used to delete an object. So, if you want to delete an object, you
have to delete it manually on each system.
To delete an object, it has to be released, so you have to delete before all transport packages where
the object is included.
Note 2:
Before the transport of existing objects, you can check the system alias. It is usually set to
“SAP_R3_HUMAN_RESSOURCES”. But in some cases, a portal system linked with several R/3
systems like IGA or on PGA, the information pages are linked to RHM and not PHM in order to have
valid information even if PHM is unavailable, the parameter system alias has to be set to the correct
alias like RHM001. This has to be checked before transport.
2.11 Unlocking a SGA Object
Before a transport or in order to move an object from the DEV to the project repertory you may need to
unlock the object.
The tool is in the System Administration tab, Monitoring link, Portal workset: Object locking
2.12 Installation of Portal Certificate
Type in Transaction
STRUSTSSO2
Click on Import
certificate
Click on Add to PSE,

and then Add to ACL
Type in the name of the system and the client 001 and click enter:
Click on Save:
Verify the installation:
Exit the STRUSTSSO2 transaction, verify the new certificates are present in the two lists (the old one
too).
2.13 Check access rights for a end user
General access to the tool:
Link : e-HR Services / Administration / Users Administration
Process:
Ask to HRIS-SGA team to be included into the group TECH_HR_XX_HRISSUPPORT
Check the logon exists on xGA
PGA is linked to AEDS database.
Check the status of logon, whether is it locked.
Check the log exists with which role.

Check the logon status on R3.
Check the deployment action on the logon

Logon searched and linked employee information
Check the person’s authentication
The employee belongs to the deployed population.
This person should be in groups listed in these 2 tables. (Tables ZDTHAU_XX_HISTO &
ZDTHAU_XX_HISTO2)
The assignment date depends on calculation date and update parameter.

The JAVA API has included this logon into these groups at the noticed date stamp. (Table
ZDTHAU_XX_TRACE).
Check the IT0105 consistency on Airbus Population
Population involved:
Airbus , all entities except Spain

Employees included in at least one deployed population
In case of data un-consistency, the IT 0105/0001 is delimited.
The List of employees modified during the last run:
People who already have a 0105 infotype:

List of employees delimited during the last run:
Employee with no logon in CUA:

Exclusion of one
or several pernr
for future run
Employees with logon locked in CUA
Employee locked in CUA :
Locked Globally By Administrator
Locked Locally By Administrator
Employees with multiple logon valid in CUA (Need data cleaning in LDAP)
Employees with logon already used (Data Inconsistency)
Search for a SGA Group:

Last run log message for a logon:
Employees with problems of excluded from selection:

Put this PERNR back in valid list for

future run
Employees Locked excluded from selection:
Put this PERNR back in

valid list for future run
2.14 Maintain Static HTML pages on SGA
Once logged on PGA, enter in the menu .
You will get access to the Static Html File, where you can find three pages:
Prerequisites:
A page has been defined for static content. We have created a page with 4 Iviews called Welcome.
Page Define designation.
You don’t see the first page (Define Designation) because administrator does it. With this page you
configures in which Iview the static html page will be display.
Example:
3 4
2
1
This page is composed by 4 Iview, Iview 1, 2, 3 containing html static page:
In the page “define designation” we defined names to Iviews:
Welcome
DSP Summary
Image
This Iview is not a static Html page; it’s a BSP and don’t need a designation.
If you want change the text displayed in the “DSP Summary Iview” (Iview 2) you need to upload a new
html page for the designation DSP Summary, and automatically the new text will be displayed in the
Iview of the page “Welcome”. The last page uploaded for a designation will be displayed in the
Iview.
Page Upload.
This page is made for upload html page that you have created before. In the selected area designation
you can choice the Iview (the zone of the page) where the upload html file will be displayed. You need
to upload the page for all the languages.
HTLM Page Development constraint:
You can only make static html file.
If you want to include image who are not in the kit of development, you will have to ask to the
administrator portal for upload the image.
For display image in your html file you need to write him directly without path. Ex: <img src="ESS.jpg">
You must develop using the css HtmlStyle.css, this css is like the look and field of the portal. If in this
css it misses a class, you need to recreate the css including it and ask the administrator for uploading
the new file.
The css file.

For the moment, the css file is like that:
 
Example of the result:
 
 
Page Versioning.
It’s very important that you keep in mind that the last html page for a designation will be displayed in
your portal.
Example: For the Iview DSP Summary (like the screenshot) in the portal you will see the last page
name dsp02.htm in the language of your connection.
You can see by designation (the Iview where the page is displayed) and by language. You can see all
pages you have uploaded. You can delete or have a preview of these pages.
Example: You have uploaded a page for the Iview DSP SUMMARY. This page will be automatically
the last page, so this page will be displayed in the portal. But this is a wrong page… you have just to
delete this page and automatically the most recent page will be displayed in the portal.
Also, think to clean the database avoiding a lot of version.

Summary
After developing your html pages you want to include it in a new page of the portal.
1 - Ask to the administrator for create the new page in the portal.
The administrator will create the page with the number of Iview you want.
After the administrator creates the designation for each Iview.
1 - Welcome
Administrator part.
2 - DSP Summary
When the page, Iviews and designation are created by the administrator go to step 2
2 - Upload the html page in the database.
The page uploaded will be displayed automatically in the portal
3 - After you can manage version of your html Page

Your part.
- Have a preview of your different Page
- Delete a page
2.15 Manage System Message Information on SGA
The Welcome page
This page is visible for all the users and it is composed of 4 Iviews:
Image
Data Security Policy
System information
Welcome
Iview “Data Security Policy”

BSP: ZBHHR_XX_C_DSP
This Iview show an HTML page with information for Airbus data security. A link exist on this page witch
open a new window with additional information on HR data security.
This page is stored in a specific table by the administrator.

Iview “System information”
BSP: ZBHHR_XX_J_QNF
This Iview retrieve the quick info available for the current period.
The period for displaying the quick info is entered by the administrator when he create (or modify or
copy) the quick info (see the manage page).
Iview “welcome”
BSP: ZBHHR_XX_C_DSP
Display of an HTML file. (see BSP ZBHHR_XX_C_DSP).
This page is stored in a specific table by the administrator (see Access to the Administration of the
static HTML PAGE.doc)
BSP ZBHHR_XX_C_DSP
The BSP ZBHHR_XX_C_DSP is used to display information.
For the Welcome page, these information are in fact HTML pages stored in the specific table
ZDTHHR_XXDSPTAB (Table contains Xstring that can be display in bsp) in hexadecimal type.
Parameters passed to the BSP:
Designation is a number witch define an Iview (defined in specific table ZDTHHR_XXDESIGN)
The values for designation number for the welcome page are defined as follow with their description
(see table ZDTHHR_XXDESIGN).
 Welcome
 Data Security Policy
 DSP Summary
 Image
We can have only one value for an Iview.
This parameter is passed in the portal content. Only an administrator can modify this content.
For example the Iview “welcome” have designation=1.

The others parameters are the language, the date and the time. They are sent by an other BSP witch
aim is to upload the HTML file or image (see doc).
The manage page
Iview “quick info administration”

This page is composed of one Iview (Quick info administration).
This page is only accessible for an administrator and is used to create, modify, copy or delete quick
info.
Screenshot: portal content

The administration of the quick info is a table display with 4 buttons.
The user can create a new quick info or delete, modify, copy existing one.
The data saved are stored in specifics tables ZDTHHR_XXQIUI and ZDTHHR_XXQIUM.
Creation
A new page is opened when the user click on the create button.
The user can define start date and time, end date and time and those of display, The urgency of the
message and the message in the different languages. Then he choose Create to save the information
of the quick info in the specifics tables.
These information are displayed for all the users in the System information’s Iview of the welcome
page.
Clear button is used to refresh the messages.
Back button is used to return to precedent page(the main administration menu).
Modification
The user select a line and click on the modify button.
The following page is displayed.
The user can modify the message, the dates or times and then pressed Update to save.
He can delete the quick info or go to the main administration menu with the others buttons.
Copying
The line selected is copied and the user can modify data.
Deletion
It is used to delete the quick info selected.
The user has to select a line and then press the delete button.
3. Appendix A - Acronyms
Acronyms Description
AMS Application Management Services
BR Baseline Record
CA Change Authorization
CAB Change Advisory Board
CCR Change Control Register
CR Change Request
CMDB Configuration Management Database
CMM Capability Maturity Model
CMP Configuration Management Plan
COE Center of Excellence
CI Configuration Items
DPR Development Project Plan
EPD Execution Process Document
GSC Global Support Center
ITIL IT Infrastructure Library
ITSM IT Service Management
KAP Knowledge Acquisition Phase
MSA Master Service Agreement
ODC Offshore Development Center
PCR Program Change Request
PIR Post-Implementation Review
PM Project Manager
PR Problem Request
RFC Request For Change

RICEF Reports, Interfaces, Conversions, Enhancements and Forms
SACC SAP Application Competency Center
SCAR Software Configuration Audit Report
SLA Service Level Agreement
SME Subject Mater Expert
SMTD System Maintenance Technical Document
SOW Statement of Work
SOX Sarbanes-Oxley
SQA Software Quality Assurance
TCO Total Cost of Ownership
VPN Virtual Private Network
WSR Weekly Status Report

Portal Administration

Uploaded by

Copyright:

Available Formats

Portal Administration

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Portal Administration

Uploaded by

Copyright:

Available Formats

HR-PORTAL_ System Maintenance and Technical Documentation

SYSTEM MAINTENANCE AND TECHNICAL DOCUMENT

Document Distribution Name Approval Date

Prepared by Reviewed by Approved by

Version Name Date Change Remarks

Version 1.0 Portal Administration 1st 1st Draft

Links between roles and groups......................................................................................................... 13

Export content from PGA.................................................................................................................... 14

Import content into FGA..................................................................................................................... 15

Export users list (HRTRxxxx) from IGA.............................................................................................. 17

Group creation and assignation of users............................................................................................17

Rename groups to reach naming convention.....................................................................................18

Create groups and import users into groups.......................................................................................18

Assignation of role to the groups........................................................................................................ 18

Storage of a picture file....................................................................................................................... 31

Create a new designation................................................................................................................... 32

Set up the translation.......................................................................................................................... 35

Publish the translation........................................................................................................................ 36

Transport of the translation................................................................................................................. 36

Create the transport file...................................................................................................................... 38

Import the transport file....................................................................................................................... 39

Page Define designation.................................................................................................................... 56

2.1 Create a test user on IGA

Pre-requisites for this activity:

Mass creation of user:

First Name=TEM test user

Assign a user into a group:

2.2 Change the sequence into a detailed navigation menu

Pre-requisites for this activity:

You received a request from an IS package leader working on an ESS/MSS scenario.

2.3 Create a new SGA HR role

hr_<project code>_<XX or entity code>_<employee or manager>_<free text>

Roles Groups association on PGA:

2.4 Create a training user on FGA

Pre-requisites for this activity:

Mass creation of user

Assign a user into a group

Links between roles and groups

2.5 Install a New XGA system:

Pre-requisites of this activity:

Transport of the HR content

Before any transport, the PCD contain not any HR object:

Export content from PGA

Import content into FGA

On FGA, we have to import the transport file.

Export users list (HRTRxxxx) from IGA

Modify e-mail address with HRIS-SGA administration address

Group creation and assignation of users

Export groups (FGA*) from IGA

Select the group called FGA*GENERIC on IGA:

Rename groups to reach naming convention

Create groups and import users into groups

Assignation of role to the groups

We select the role which target on old FGA folder.

Request of certificate to Olivier Rodriguez and Pierre Melan

They will send the certificate by mail:

Configure STRUSTSSO2 transaction in all SHM clients

Import the certificate into SAP R/3 using strustsso2 transaction: