Configuration Guide OASM 2 0 SP6

SAP Custom Development
Online Application
Submission Management
Configuration Guide
Version Status Date
1.4 Final July 09, 2012
Confidential
2012 SAP AG
Dietmar-Hopp-Allee 16
D-69190 Walldorf
Configuration Guide
Confidential
Typographic Conventions Icons
Type Style Description Icon Meaning

Example Text Words or characters quoted Caution
from the screen. These
include field names, screen Example
titles, pushbuttons labels, Note
menu names, menu paths,
and menu options. Recommendation
Cross-references to other Syntax
documentation
Example text Emphasized words or Additional icons are used in SAP Library
phrases in body text, graphic documentation to help you identify different
titles, and table titles types of information at a glance. For more
EXAMPLE TEXT Technical names of system information, see Help on Help General
objects. These include report Information Classes and Information
names, program names, Classes for Business Information
transaction codes, table Warehouse on the first page of any version
names, and key concepts of of SAP Library.
a programming language
when they are surrounded by
body text, for example,
SELECT and INCLUDE.
Example text Output on the screen. This
includes file and directory
names and their paths,
messages, names of
variables and parameters,
source text, and names of
installation, upgrade and
database tools.
Example text Exact user entry. These are
words or characters that you
enter in the system exactly
as they appear in the
documentation.
<Example Variable user entry. Angle
text> brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE TEXT Keys on the keyboard, for
example, F2 or ENTER.
2012 SAP AG Title: Online Application Submission Management Page 2 of 111

Dietmar-Hopp-Allee 16 Version: 1.4
D-69190 Walldorf Date: July 09, 2012
Configuration Guide
Confidential
Table of Contents
1 Organization .................................................................................................. 5
1.1 Document Administration.................................................................................................... 5
1.1.1 Authors ................................................................................................................................. 5
1.1.2 History .................................................................................................................................. 5
1.2 Intended Group of Readers ................................................................................................ 5
1.3 Glossary ............................................................................................................................... 5
2 Getting Started .............................................................................................. 7

2.1 Related Information ............................................................................................................. 7
2.2 Important Notes ................................................................................................................... 7
3 Solution Overview......................................................................................... 9
3.1 System Landscape.............................................................................................................. 9
3.2 Software Component Matrix ............................................................................................. 10
3.3 Implementation General Description ............................................................................ 10
4 Configuration Details.................................................................................. 12
4.1 SAP User Management Engine (UME) ........................................................................... 12
4.1.1 User Types ........................................................................................................................ 12
4.1.2 Groups ............................................................................................................................... 16
4.1.3 Roles .................................................................................................................................. 19
4.1.4 Actions ............................................................................................................................... 27
4.2 Connecting Online Application Submission Management to Other Systems ............... 40
4.2.1 SAP Portal and Document Management System (DMS) ............................................... 40
4.2.2 Adobe Document Services ............................................................................................... 46
4.2.3 Destinations for Forms ...................................................................................................... 47
4.2.4 Address Validation Service............................................................................................... 50
4.2.5 Implement Virus Scanning in SAP NetWeaver CE 7.1 .................................................. 55
4.2.6 Integration of CAPTCHA (Completely Automated Public Turing test to tell
Computers and Humans Apart) ....................................................................................... 63
4.3 Specific Customizing for Online Application Submission Management ........................ 66
4.3.1 Customisable E-Mail Notification Templates................................................................... 66
4.3.2 Status Actions.................................................................................................................... 71
4.3.3 Message Customizing....................................................................................................... 72
4.3.4 Application Properties ....................................................................................................... 73
4.3.5 Running a Notification Job................................................................................................ 83

Configuration Guide
Confidential
4.4 Additional Functionality ..................................................................................................... 86

4.4.1 Employee Data Mapping for Forms and Messages ....................................................... 86
4.4.2 HTML Forms...................................................................................................................... 88
4.4.3 New Categories added for Questions.............................................................................. 92
4.5 Register Master Data Maintenance for Online Application Submission........................ 93
4.5.1 Manual Register Master Data Maintenance .................................................................... 93
4.5.2 Register Dependencies .................................................................................................... 97
4.5.3 Register Master Data Transport ....................................................................................... 97
4.5.4 Register Post Checks ..................................................................................................... 101
4.6 Security ............................................................................................................................ 102
4.7 User Interface .................................................................................................................. 103
4.7.1 Web Dynpro Applications ............................................................................................... 103
4.7.2 SAP Portal Configuration ................................................................................................ 108

Configuration Guide
Confidential
1 Organization
1.1 Document Administration
1.1.1 Authors
Name Company Project Role/Comment
Team SAP AG Author
1.1.2 History
Date Version Release Name Change/Enhancement
Note
30/11/2010 Release 2.0 All

17/12/2010 Release 2.0 SP1 1539224 All
28/01/2011 Release 2.0 SP2 1548169 All
12/05/2011 Release 2.0 SP3, 1562462 Manish Sethi Section 4.3.3.1 Restrictions while
Document Version 1.1 Customizing Message Types added
14/06/2011 Release 2.0 SP4, 1570651 Florian Speth Changed upper and lower case of email
Document Version 1.2 template placeholders in section 4.3.5.2
30/04/2012 Release 2.0 SP5, 1589441 Florian Speth, Section 4.4 Additional Functionality
Document Version 1.3 Manish Sethi added.
09/07/2012 Release 2.0 SP6, 1722743 Florian Speth Section 4.4.1: Added new mappable
Document Version 1.4 parameters for department text, institution
and institution text.
Section 4.3.4.2: Added new application
property for HTML forms
1.2 Intended Group of Readers

This document is intended for use by the following user groups:
Customers
Consultants
Partners
1.3 Glossary
For more information about project-specific terminology, see the glossary on SAP Service Marketplace at
http://service.sap.com/swdc Software Downloads Installations and Upgrades Browse our

Configuration Guide
Confidential
Download Catalog SAP Development Projects ONLINE APP SUBMISSION MGMT ONLINE APP
SUBMISSION MGMT 2.0 Technical Documentation Glossar.

Configuration Guide
Confidential
2 Getting Started
2.1 Related Information
Links to SAP Service Marketplace
For more information about other documentation, see SAP Service Marketplace at
http://service.sap.com/swdc Software Downloads Installations and Upgrades Browse our
Download Catalog SAP Development Projects ONLINE APP SUBMISSION MGMT
ONLINE APP SUBMISSION MGMT 2.0 Technical Documentation.
SAP Solution Manager
2.2 Important Notes

You must ensure that the required software is installed before you start the implementation. You can find
the information about installation in the SAP notes listed in the table below. The SAP notes contain the
most recent information about the installation and the corrections to the installation documentation. You
must therefore ensure that you have the up-to-date version of each SAP Note.
We recommend that you read the SAP Installation Notes before proceeding with installation and
implementation of the solution.
List of Related SAP Notes
SAP Note Title Description

Number
1527526 Online Application Installation Note for Online Application Submission

Submission Management Management 2.0
2.0
984006 Remote Support for an For remote access, you need to make use of the
Enterprise Portal Remote Support Service. In order to get Remote
Support, a remote connection to SAP is needed. This
note helps you to find further information on remote
connectivity and the required software.
736902 Adobe Credentials This note provides information about how you can
install the credentials and complete the configuration
for Adobe Interactive Forms.
Example Adobe Forms do not work Adobe Interactive Forms do not work with Mozilla
1393511 with FF3 FireFox 3.x. This note provides instructions on how to
deploy a NetWeaver patch to fix the problem.
1527542 Online application Contains the register transport XML Schema. For more
submission management: information about register transport, see Register
Master Data Master Data Transport.
1539224 Release Note for SP1 Contains release-specific information for support
package 1 (SP1) of online application submission
management

Configuration Guide
Confidential
management
management
management
management

Configuration Guide
Confidential
3 Solution Overview
3.1 System Landscape
Browser
Web User Interface
SAP NetWeaver Composition

Environment 7.1
Portal
Web Adobe
Application Document
Server Java Services
SAP NetWeaver Portal 7.0
Knowledge Management
Figure 1: System Landscape

Configuration Guide
Confidential
3.2 Software Component Matrix

The following table provides a consolidated view of the described scenarios and processes, and identifies
the associated SAP software component:
Scenario/Business Software Components Implementation and Configuration

Processes Process
Register Data SAP NetWeaver Register Data Maintenance

Maintenance Composition Environment
(CE) 7.1 Enhancement
Application Management Pack 01 SP05 Configurations for the SAP NetWeaver CE
System 7.1 EhP 1 System
Specific customizing for the online
application submission management solution
Adobe Document Adobe Document Services

Services Configuration
SAP User Management SAP User Management Engine
Engine
Document Management SAP NetWeaver 7.0 SAP Portal and Document Management
System Enterprise Portal 6.0 System
SP16 Configurations for the SAP Enterprise Portal
7.0
You can connect a different portal system to

this SAP solution. This needs to be specified
in a separate project.
3.3 Implementation General Description

The following table provides an overview of the main installation steps for the online application
submission management application:
Software to Be Installed and the Related Configuration
1 Install Java Software Development Kit (JSDK) version 1.5_x

2 Install Database Server Software.
3 Install SAP NetWeaver CE 7.1 EhP 1 (SP05 or higher).
4 Deploy the online application submission management application.
5 Install SAP NetWeaver 7.00 SP16 (or higher) including Enterprise Portal and
Knowledge Management.
6 Deploy the latest patch of CDPEUDLR_DMS_KM from the SAP Service
Marketplace to the SAP NetWeaver 7.00 system.
5 Create business roles in the User Management Engine (UME) on the CE server.

Configuration Guide
Confidential
Software to Be Installed and the Related Configuration
6 Configure your portal software.

7 Connect the solution to other systems.
8 Implement online application submission management specific customizing
9 Maintain register data in an XML file for upload or maintain register data
manually.
After performing the installation steps, configure the business processes.
For more information about the installation of the software components, see SAP Note 1527526.

Configuration Guide
Confidential
4 Configuration Details
4.1 SAP User Management Engine (UME)
The SAP User Management Engine (UME) is an integral component of the SAP NetWeaver Composition
Environment (CE) platform and of the online application submission management system architecture. It
is used for user authentication and authorisation purposes. Business roles, role groups, assignments of
actions and implicitly of application permissions as well, user groups and the system users for the online
application submission management system are maintained in this component.
Users acting as applicants in the online application submission management system are created in the
UME by the registration process of the online application submission management system for applicant
individuals or for primary users of applicant organisations, respectively. These primary users can further
create and manage other users for their organisations. In addition, they can also grant them necessary
authorisations. For this so-called delegated user administration the online application submission
management system provides user interfaces (UIs) as enhancement of the standard Identity
Management functionality to ensure that a primary user can administrate users within their own
organisation.
Users acting as front office employees or authority employees are created in the UME during register
maintenance of institutions. The initial setup of these users with respect to passwords and role
assignments has to be carried out using the standard SAP Identity Management administration console
(UI). Once the initial setup is done, the delegated user administration concept can be applied on front
offices and authorities as well as on applicants. However, master data changes are not possible.
It is essential that the system is properly configured in accordance with the configuration options
described in the following sections.
Authorisations are enforced using permissions, actions, and roles. Permissions are used on application
code level for access control. They are grouped into actions by developers. Contrariwise, an action is a
collection of permissions. Every application like the online application submission management also
defines its own set of actions and specifies the permissions assigned to the actions internally, either in an
XML file or dynamically in the code. However, the actions appear in the Identity Management
administration console where you can group them into roles.
UME roles group actions from one or more applications. You assign roles to users directly or indirectly by
using groups in the Identity Management administration console. By assigning roles to users, you define
the users authorisations.
The following sections describe various user types of online application submission management
explaining how roles are related to them and which roles have to be assigned to the different users to
accomplish their tasks. In addition, the creation of groups and roles is described step by step. Finally, the
actions section gives you an overview about all available actions after the deployment of the online
application submission management software.
4.1.1 User Types

This section summarizes the various business user types for online application submission management
system and their related roles. Among these user types are applicant individuals, applicant organisation
employees, front office employees, authority employees, register maintenance users and anonymous
users, for example those who have not carried out the self-registration or start an application process in
simulation mode. The required standard roles of the online application submission management system
are highlighted per user type. However, in addition to these standard roles, you can also maintain custom
roles for specific system processes, as required. For example, you can create specific roles as required
for a consulting project.

Configuration Guide
Confidential
4.1.1.1 Applicant Individuals

Two prerequisites have to be fulfilled to act as an individual applicant in the system. First, an applicant
needs to be registered as an individual applicant. This way the required master data is stored in the
system. Secondly, the role OAM_APPLICANT_INDIVIDUAL has to be assigned to the corresponding
user.
4.1.1.2 Applicant Organisation Employees
The master data for an applicant organisation as well as for the first employee of this organisation is
gathered in the registration process. The essential role to act as an employee of the applicant
organisation is OAM_APPLICANT_ORGANISATION_EMPLOYEE.
In addition, the following roles are available in the applicant organisation scenario to provide additional
privileges:
OAM_APPLICANT_ORGANISATION_EMPLOYEE_PROFILE_MAINTENANCE
Privileges to maintain the own employee profile data, this includes master data changes,
password changes and security question or answer changes
OAM_APPLICANT_ORGANISATION_MAINTENANCE
Privileges to maintain the applicant organisation master data
OAM_APPLICANT_ORGANISATION_DISPATCH
Privileges to dispatch applications to other employees of the same applicant organisation
OAM_APPLICANT_ORGANISATION_USER_ADMINISTRATION
Privileges to administrate users of the own applicant organisation, this includes creating new
organisation employees, updating master data and user management for example password
changes, role assignments, locking and unlocking users.
4.1.1.3 Front Office Employees
The master data for front office employees are maintained in the institution registers. The essential role to
act as a contact person of the front office is OAM_FRONT_OFFICE_EMPLOYEE.
Additional privileges can be granted to front office employees by assigning the following roles:
OAM_FRONT_OFFICE_APPLICATION_DISPATCH_GLOBAL
Privileges to dispatch applications to another front office employee within the same front office
institution
OAM_FRONT_OFFICE_APPLICATION_DISPATCH_HIERARCHY
Privileges to dispatch applications to another front office employee of the same department and
its sub-departments
OAM_FRONT_OFFICE_APPLICATION_DISPATCH_LOCAL
Privileges to dispatch applications to another front office employee of the same department
OAM_INSTITUTION_USER_ADMINISTRATOR_GLOBAL
Privileges to administrate users within the institution, including user management for example
changing passwords, assigning roles, locking and unlocking users

Configuration Guide
Confidential
Updating master data is not possible; these changes are only allowed in register maintenance
OAM_INSTITUTION_USER_ADMINISTRATOR_HIERARCHY
Privileges to administrate users within the department and its sub-departments of the institution,
including user management for example changing passwords, assigning roles, locking and
unlocking users
OAM_INSTITUTION_USER_ADMINISTRATOR_LOCAL
Privileges to administrate users of the department of the institution, including user management
for example changing passwords, assigning roles, locking and unlocking users
4.1.1.4 Authority Employees
The master data for authority employees are maintained in the institution registers. The essential role
required to act as an employee of the authority is OAM_AUTHORITY_EMPLOYEE.
Additional privileges can be granted to authority employees by assigning the following roles:
OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_GLOBAL
Privileges to dispatch partial applications as an authority employee to another employee of the
same authority institution
OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_HIERARCHY
Privileges to dispatch partial applications as an authority employee to another employee of the
same department and its sub-departments
OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_LOCAL
Privileges to dispatch partial applications as authority employee to another employee of the same
department
OAM_INSTITUTION_USER_ADMINISTRATOR_GLOBAL
Privileges to administrate users of the own institution, including user management, for example
changing passwords, assigning roles, locking and unlocking users
OAM_INSTITUTION_USER_ADMINISTRATOR_HIERARCHY
Privileges to administrate users of the same department and its sub-departments, this includes
user management for example changing passwords, assigning roles, locking and unlocking
users.

Configuration Guide
Confidential
OAM_INSTITUTION_USER_ADMINISTRATOR_LOCAL
Privileges to administrate users of the same department, including user management, for
example changing passwords, assigning roles, locking and unlocking users
4.1.1.5 Register Maintenance Users
The essential roles to maintain register data for the online application submission management system
are OAM_REGISTER_VIEW_UI and OAM_REGISTER_MANAGE_QUERY_API. The first one grants
access to the register maintenance dialogs and the second one in combination with one of the following
roles described below provides privileges to create, update, delete, read and find register data.
Additional roles are required to grant specific maintenance privileges. They have to be assigned to the
user and are described as follows:
OAM_REGISTER_GLOBAL_ADMIN
Privileges to maintain the domain of local administrators; this includes access to the admin
register and assignment of entities and institutions to local administrators
OAM_REGISTER_LOCAL_ADMIN
Privileges to maintain the domain of local users; this includes providing access to the admin
register and assignment of entities and institutions to the local users belonging to the local
administrators domain
OAM_REGISTER_LOCAL_USER
Privileges to read and change only specific register data as a local user; this includes
maintenance of periods and charges for public service types, maintenance of institution data, its
departments and employees and their communication and payment data. It also includes
maintenance of form fields and form variants for forms belonging to the local users domain.
This does not include administrator and import/export privileges.

OAM_REGISTER_GLOBAL_READ_WRITE_USER
Privileges to read and change all register data; note: this does not include administrator and
import/export privileges
OAM_REGISTER_TRANSPORT
Privileges to import and export register data
4.1.1.6 Everyone
Some features shall be available without the necessity to be logged on to the online application
submission management system. For this purpose, the following roles have to be managed to make them
applicable:
OAM_EVERYONE_APPLICANT_REGISTRATION
Privileges to register as applicant (individual or organisation) on the Online Application
Submission Management platform

Configuration Guide
Confidential
OAM_EVERYONE_APPLICATION_SIMULATION
Privileges to run the application process as an application enterer in simulation mode for demo
purposes
OAM_EVERYONE_USER_CREDENTIALS_RECOVERING
Privileges to retrieve (forgotten) user IDs and request (forgotten) passwords
Retrieving user IDs can be applied to all user types in the online application submission
management system. However, the process for resetting passwords is only applicable for
applicant users due to the fact that security questions/ answers have to be provided and defined.
The online application submission management system supports this feature currently for
applicants only.
Besides the roles described above the following technical role is required for every user type mentioned
above:
OAM_REGISTER_QUERY_API
Privileges to read and find register data
4.1.1.7 Other
There are two additional roles, one for system administrators and one to publish search queries to
specific users:
OAM_MISC_PARTIAL_APPLICATION_NOTIFICATION_JOB
Additional privileges for administrator users of the SAP NetWeaver Administrator which are
required to run scheduled notification jobs informing other users about the status of partial
applications (see Running a Notification Job)
OAM_MISC_SEARCH_QUERY_VARIANT_PUBLISHING
Privileges to store search query variants publicly to enable other users of the same search query
dialog to reuse them. The concrete search dialogs in the online application submission
management system, used by the user of this role, are determined by further roles or the user
types
4.1.2 Groups
The online application submission management system requires the availability of some groups for users
and roles. Role groups are used for delegated user administration and user groups to provide particular
initial privileges for the user types they are meant for. This is why these groups have to be created.
The assignments below constitute the recommended basic configuration; they can be enhanced or
restricted according to your specific needs. In any case the groups described in this section have to be
created with their given IDs in the UME.
OAM_USER_GROUP_APPLICANT_INDIVIDUAL
Users who are created during the registration process as applicant individuals are automatically
assigned to this user group.
Required role:
o OAM_APPLICANT_INDIVIDUAL

Configuration Guide
Confidential
OAM_USER_GROUP_APPLICANT_ORGANISATION_ADMINISTRATOR
Users who are created during the registration process as applicant organisation employees are
automatically assigned to this user group.
Required roles:
o OAM_APPLICANT_ORGANISATION_EMPLOYEE
o OAM_APPLICANT_ORGANISATION_DISPATCH
o OAM_APPLICANT_ORGANISATION_EMPLOYEE_PROFILE_MAINTENANCE
o OAM_APPLICANT_ORGANISATION_MAINTENANCE
o OAM_APPLICANT_ORGANISATION_USER_ADMINISTRATION
OAM_USER_GROUP_APPLICANT_ORGANISATION
Users who are created my means of the delegated user administration as applicant organisation
employees are automatically assigned to this user group.
Required role:
o OAM_APPLICANT_ORGANISATION_EMPLOYEE
OAM_USER_GROUP_INSTITUTION
Users who are created during register maintenance as employees are automatically assigned to
this user group.
Required role: None
Technically it cannot be distinguished at the time of user creation whether the user is acting as
front office employee or authority employee. That is why no online application submission
management role is required although the group may help to assign common custom privileges.
The following user groups may be helpful during your implementation project, although they are
currently not considered directly in the online application submission management system:
OAM_USER_GROUP_AUTHORITY, OAM_USER_GROUP_FRONT_OFFICE and
OAM_USER_GROUP_REGISTER_ADMINISTRATOR
The following role groups are used to configure the assignable roles for delegated user administration of
different user types.
Roles assigned to users implicitly by (user) groups cannot be unassigned by the delegated user
administration. For example, if you assign the user group
OAM_USER_GROUP_APPLICANT_ORGANISATION to an employee user of an applicant organisation,
the role OAM_APPLICANT_ORGANISATION_EMPLOYEE is assigned implicitly to the corresponding
user. Even if this role would be part of the role OAM_ROLE_GROUP_APPLICANT, is not possible to
unassign it using the delegated user administration because the delegated user administration can
manage direct role assignments only.
OAM_ROLE_GROUP_APPLICANT
Grouping of available or assignable roles for the delegated user administration of an applicant
organisation

Configuration Guide
Confidential
The role OAM_APPLICANT_ORGANISATION_EMPLOYEE is implicitly assigned to users by the

user group mechanism.
Required system roles:
o OAM_APPLICANT_ORGANISATION_DISPATCH
o OAM_APPLICANT_ORGANISATION_EMPLOYEE_PROFILE_MAINTENANCE
o OAM_APPLICANT_ORGANISATION_MAINTENANCE
o OAM_APPLICANT_ORGANISATION_USER_ADMINISTRATION
OAM_ROLE_GROUP_FRONT_OFFICE
Grouping of available or assignable roles for the delegated user administration of the front office
o OAM_FRONT_OFFICE_EMPLOYEE
o OAM_FRONT_OFFICE_APPLICATION_DISPATCH_GLOBAL
o OAM_FRONT_OFFICE_APPLICATION_DISPATCH_HIERARCHY
o OAM_FRONT_OFFICE_APPLICATION_DISPATCH_LOCAL
o OAM_INSTITUTION_USER_ADMINISTRATOR_GLOBAL
o OAM_INSTITUTION_USER_ADMINISTRATOR_HIERARCHY
o OAM_INSTITUTION_USER_ADMINISTRATOR_LOCAL
OAM_ROLE_GROUP_AUTHORITY
Grouping of available or assignable roles for the delegated user administration of the authority
o OAM_AUTHORITY_EMPLOYEE
o OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_GLOBAL
o OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_HIERARCHY
o OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_LOCAL
OAM_ROLE_GROUP_INSTITUTION
Grouping of available or assignable roles for the delegated user administration of the institution;
This role group is applied in the delegated user administration only if the roles
OAM_FRONT_OFFICE_EMPLOYEE and OAM_AUTHORITY_EMPLOYEE are assigned to the
delegated user administrator. This is designed for the special case where an authority acts as a
front office as well.
o OAM_FRONT_OFFICE_EMPLOYEE
o OAM_FRONT_OFFICE_APPLICATION_DISPATCH_GLOBAL
o OAM_FRONT_OFFICE_APPLICATION_DISPATCH_HIERARCHY
o OAM_FRONT_OFFICE_APPLICATION_DISPATCH_LOCAL

Configuration Guide
Confidential
o OAM_AUTHORITY_EMPLOYEE
o OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_GLOBAL
o OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_HIERARCHY
o OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_LOCAL
4.1.3 Roles
After the above descriptions of the online application submission management user types and groups and
their relationship to the required roles, the focus of the following sections lie on these roles in more detail.
You have to create them in the UME with the unique names given in this section. To make them
operational, you have to assign the described actions.
These actions are automatically available in the UME after the online application submission
management software is deployed on the SAP NetWeaver CE 7.1 system. Technically, the actions are
contained in the permission development component of the online application submission management
delivery.
4.1.3.1 OAM_APPLICANT_INDIVIDUAL
Unique name: OAM_APPLICANT_INDIVIDUAL
Description: Privileges for applicant individuals
Assigned actions:
OAMApplicationApplicantAdmin
OAMManageApplicantUpdateApplicant
OAMManageIndividualReadIndividualByUserID
OAMManageIndividualUpdateIndividual
OAMUserTypeApplicantIndividual
4.1.3.2 OAM_APPLICANT_ORGANISATION_DISPATCH
Unique name: OAM_APPLICANT_ORGANISATION_DISPATCH
Description: Privileges to dispatch applications in applicant organisations
Assigned action:
OAMApplicationApplicantDispatcher
4.1.3.3 OAM_APPLICANT_ORGANISATION_EMPLOYEE
Unique name: OAM_APPLICANT_ORGANISATION_EMPLOYEE
Description: Privileges for applicant organisation employees
Assigned actions:
OAMApplicationApplicantAdmin
OAMUserTypeApplicantOrganisationEmployee
4.1.3.4 OAM_APPLICANT_ORGANISATION_EMPLOYEE_PROFILE_MAINTENANCE
Unique name: OAM_APPLICANT_ORGANISATION_EMPLOYEE_PROFILE_MAINTENANCE
Description: Privileges for employees to manage their own profile

Configuration Guide
Confidential
Assigned actions:
OAMManageOrganisationEmployeeReadOrganisationEmployeeByUserID
OAMManageOrganisationEmployeeUpdateOrganisationEmployee
4.1.3.5 OAM_APPLICANT_ORGANISATION_MAINTENANCE
Unique name: OAM_APPLICANT_ORGANISATION_MAINTENANCE
Description: Maintain applicant organisation master data
Assigned actions:
OAMManageOrganisationReadOrganisationByEmployeeUserID
OAMManageOrganisationUpdateOrganisation
4.1.3.6 OAM_APPLICANT_ORGANISATION_USER_ADMINISTRATION
Unique name: OAM_APPLICANT_ORGANISATION_USER_ADMINISTRATION
Description: Administrate users of applicant organisations
Assigned actions:
OAMAdministrateUserCreateOrganisationUser
OAMAdministrateUserFindOrganisationUserByElements
OAMAdministrateUserFindRolesByGroupUniqueName
OAMAdministrateUserGeneratePassword
OAMAdministrateUserLockUser
OAMAdministrateUserReadOrganisationUser
OAMAdministrateUserUnLockUser
OAMAdministrateUserUpdateOrganisationUser
4.1.3.7 OAM_AUTHORITY_EMPLOYEE
Unique name: OAM_AUTHORITY_EMPLOYEE
Description: Privileges for authority employees
Assigned actions:
OAMApplicationAuthorityAdmin
OAMApplicationChargesAdmin
OAMUserTypeAuthorityEmployee
4.1.3.8 OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_GLOBAL
Unique name: OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_GLOBAL
Description: Dispatch partial applications in your institution
Assigned action:
OAMApplicationAuthorityGlobalDispatcher
4.1.3.9 OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_HIERARCHY
Unique name: OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_HIERARCHY
Description: Dispatch partial application in your department and associated sub-departments

Configuration Guide
Confidential
Assigned action:
OAMApplicationAuthorityHierarchicalDispatcher
4.1.3.10 OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_LOCAL
Unique name: OAM_AUTHORITY_PARTIAL_APPLICATION_DISPATCH_LOCAL
Description: Dispatch partial application in your department
Assigned action:
OAMApplicationAuthorityLocalDispatcher
4.1.3.11 OAM_EVERYONE_APPLICANT_REGISTRATION
Unique name: OAM_EVERYONE_APPLICANT_REGISTRATION
Description: Register on the online application submission management platform
Assigned action:
OAMManagePrincipalRegisterPrincipal
4.1.3.12 OAM_EVERYONE_APPLICATION_SIMULATION
Unique name: OAM_EVERYONE_APPLICATION_SIMULATION
Description: Run online applications in simulation mode
Assigned actions:
OAMSimulationUser
4.1.3.13 OAM_EVERYONE_USER_CREDENTIALS_RECOVERING
Unique name: OAM_EVERYONE_USER_CREDENTIALS_RECOVERING
Description: Recover your user credentials
Assigned action:
OAMRecoverCredentialsReadSecurityQuestion
OAMRecoverCredentialsResetPassword
OAMRecoverCredentialsSubmitUserIDsByEmail
4.1.3.14 OAM_FRONT_OFFICE_APPLICATION_DISPATCH_GLOBAL
Unique name: OAM_FRONT_OFFICE_APPLICATION_DISPATCH_GLOBAL
Description: Dispatch applications in your institution
Assigned action:
OAMApplicationFrontOfficeGlobalDispatcher
4.1.3.15 OAM_FRONT_OFFICE_APPLICATION_DISPATCH_HIERARCHY
Unique name: OAM_FRONT_OFFICE_APPLICATION_DISPATCH_HIERARCHY
Description: Dispatch applications in your department and associated sub-department
Assigned action:
OAMApplicationFrontOfficeHierarchicalDispatcher

Configuration Guide
Confidential
4.1.3.16 OAM_FRONT_OFFICE_APPLICATION_DISPATCH_LOCAL
Unique name: OAM_FRONT_OFFICE_APPLICATION_DISPATCH_LOCAL
Description: Dispatch applications in your department
Assigned action:
OAMApplicationFrontOfficeLocalDispatcher
4.1.3.17 OAM_FRONT_OFFICE_EMPLOYEE
Unique name: OAM_FRONT_OFFICE_EMPLOYEE
Description: Privileges for front office employees
Assigned actions:
OAMApplicationChargesAdmin
OAMApplicationFrontOfficeAdmin
OAMUserTypeFrontOfficeEmployee
4.1.3.18 OAM_INSTITUTION_USER_ADMINISTRATOR_GLOBAL
Unique name: OAM_INSTITUTION_USER_ADMINISTRATOR_GLOBAL
Description: Administrate users in your institution
Assigned actions:
OAMAdministrateUserFindInstitutionUserByElements
OAMAdministrateUserReadInstitutionUser
OAMAdministrateUserUpdateInstitutionUser
OAMUserTypeInstitutionUserAdministrator
4.1.3.19 OAM_INSTITUTION_USER_ADMINISTRATOR_HIERARCHY
Unique name: OAM_INSTITUTION_USER_ADMINISTRATOR_HIERARCHY
Description: Administrate users in your department and associated sub-department
Assigned actions:
OAMUserTypeDepartmentHierarchyUserAdministrator
4.1.3.20 OAM_INSTITUTION_USER_ADMINISTRATOR_LOCAL
Unique name: OAM_INSTITUTION_USER_ADMINISTRATOR_LOCAL
Description: Administrate users in your department

Configuration Guide
Confidential
Assigned actions:
OAMUserTypeDepartmentUserAdministrator
4.1.3.21 OAM_MISC_PARTIAL_APPLICATION_NOTIFICATION_JOB
Unique name: OAM_MISC_PARTIAL_APPLICATION_NOTIFICATION_JOB
Description: Privileges to run partial application notification jobs (see Running a Notification Job)
Assigned action:
OAMNotificationJobAction
4.1.3.22 OAM_MISC_SEARCH_QUERY_VARIANT_PUBLISHING
Unique name: OAM_MISC_SEARCH_QUERY_VARIANT_PUBLISHING
Description: Privileges to maintain and publish default query variants
Assigned action:
OAMUserTypeQueryVariantAdministrator
4.1.3.23 OAM_REGISTER_GLOBAL_ADMIN
Unique name: OAM_REGISTER_GLOBAL_ADMIN
Description: Privileges to maintain the domain of local administrators
Assigned action:
OAMRegisterGlobalAdmin
4.1.3.24 OAM_REGISTER_GLOBAL_READ_WRITE_USER
Unique name: OAM_REGISTER_GLOBAL_READ_WRITE_USER
Description: Privileges to read and change register data domain-independent
Assigned action:
OAMRegisterGlobalUser
4.1.3.25 OAM_REGISTER_LOCAL_ADMIN
Unique name: OAM_REGISTER_LOCAL_ADMIN
Description: Privileges to maintain the domain of local users
Assigned action:
OAMRegisterLocalAdmin
4.1.3.26 OAM_REGISTER_LOCAL_USER
Unique name: OAM_REGISTER_LOCAL_USER

Configuration Guide
Confidential
Description: Privileges to read and change only specific register data that are allowed to be maintained by
local users
Assigned action:
OAMRegisterLocalUser
4.1.3.27 OAM_REGISTER_MANAGE_QUERY_API
Unique name: OAM_REGISTER_MANAGE_QUERY_API
Description: Run permission for all registers' create, update, delete, read and find operations (= technical
role)
Assigned actions:
OAMManageUserProfileDMSAddUserToGroup
OAMManageUserProfileDMSCreateUser
OAMManageUserProfileDMSUpdateUser
OAMManageUserProfileUMEAddUserToGroup
OAMManageUserProfileUMECreateUser
OAMManageUserProfileUMEFindUsersByElements
OAMManageUserProfileUMEUpdateUser
OAMRegisterGlobalUIUser
OAMRegisterManage
OAMRegisterManageClassification
OAMRegisterManageClassificationType
OAMRegisterManageCommunication,
OAMRegisterManageCustomizing
OAMRegisterManageDocumentType,
OAMRegisterManageEmployee
OAMRegisterManageEntity
OAMRegisterManageEntityCategory
OAMRegisterManageEntityCategoryAppParam
OAMRegisterManageEntityInstitution
OAMRegisterManageEntityReference
OAMRegisterManageEntityType
OAMRegisterManageExternalCode
OAMRegisterManageForm
OAMRegisterManageFormField
OAMRegisterManageFormVariant,
OAMRegisterManageInstitution
OAMRegisterManageNamespace
OAMRegisterManageOrgUnit
OAMRegisterManagePayment,
OAMRegisterManagePublicServiceAuthority
OAMRegisterManagePublicServiceType
OAMRegisterManagePublicServiceTypeCharge
OAMRegisterManagePublicServiceTypeDocument
OAMRegisterManagePublicServiceTypePeriod
OAMRegisterManageQuestion,
OAMRegisterManageQuestionGroup
OAMRegisterManageRule
OAMRegisterManageSelectionList

Configuration Guide
Confidential
OAMRegisterManageSelectionValue
OAMRegisterManageSmc
OAMRegisterManageUserLocalization
OAMRegisterQuery
OAMRegisterQueryClassification
OAMRegisterQueryClassificationType
OAMRegisterQueryCommunication
OAMRegisterQueryCustomizing
OAMRegisterQueryDocumentType
OAMRegisterQueryEmployee
OAMRegisterQueryEntity
OAMRegisterQueryEntityCategory
OAMRegisterQueryEntityCategoryAppParam
OAMRegisterQueryEntityInstitution
OAMRegisterQueryEntityReference
OAMRegisterQueryEntityType
OAMRegisterQueryExternalCode
OAMRegisterQueryForm
OAMRegisterQueryFormField
OAMRegisterQueryFormVariant
OAMRegisterQueryInstitution,
OAMRegisterQueryNamespace
OAMRegisterQueryOrgUnit
OAMRegisterQueryPayment
OAMRegisterQueryPublicServiceAuthority
OAMRegisterQueryPublicServiceType
OAMRegisterQueryPublicServiceTypeCharge
OAMRegisterQueryPublicServiceTypeDocument
OAMRegisterQueryPublicServiceTypePeriod
OAMRegisterQueryQuestion,
OAMRegisterQueryQuestionGroup
OAMRegisterQueryRule
OAMRegisterQuerySelectionList,
OAMRegisterQuerySelectionValue
OAMRegisterQuerySmc
OAMRegisterQueryTypedRule,
OAMRegisterQueryUserLocalization
OAMRegisterManageQuestionGroupFormAssignment
OAMRegisterQueryQuestionGroupFormAssignment
4.1.3.28 OAM_REGISTER_QUERY_API
Unique name: OAM_REGISTER_QUERY_API
Description: Run permission to all registers' read and find operations (= technical role)
Assigned actions:
OAMRegisterQuery
OAMRegisterQueryClassification
OAMRegisterQueryClassificationType
OAMRegisterQueryCommunication

Configuration Guide
Confidential
OAMRegisterQueryCustomizing
OAMRegisterQueryDocumentType
OAMRegisterQueryEmployee
OAMRegisterQueryEntity
OAMRegisterQueryEntityCategory
OAMRegisterQueryEntityCategoryAppParam
OAMRegisterQueryEntityInstitution
OAMRegisterQueryEntityReference
OAMRegisterQueryEntityType
OAMRegisterQueryExternalCode
OAMRegisterQueryForm
OAMRegisterQueryFormField
OAMRegisterQueryFormVariant
OAMRegisterQueryInstitution
OAMRegisterQueryNamespace
OAMRegisterQueryOrgUnit
OAMRegisterQueryPayment
OAMRegisterQueryPublicServiceAuthority
OAMRegisterQueryPublicServiceType
OAMRegisterQueryPublicServiceTypeCharge
OAMRegisterQueryPublicServiceTypeDocument
OAMRegisterQueryPublicServiceTypePeriod
OAMRegisterQueryQuestion
OAMRegisterQueryQuestionGroup
OAMRegisterQueryRule
OAMRegisterQuerySelectionList
OAMRegisterQuerySelectionValue
OAMRegisterQuerySmc
OAMRegisterQueryTypedRule
OAMRegisterQueryUserLocalization
OAMRegisterQueryQuestionGroupFormAssignment
4.1.3.29 OAM_REGISTER_TRANSPORT
Unique name: OAM_REGISTER_TRANSPORT
Description: Privileges to import and export register data
Assigned actions:
OAMRegisterExport
OAMRegisterExportApi
OAMRegisterImport
OAMRegisterImportApi
OAMRegisterImportViewLog
4.1.3.30 OAM_REGISTER_VIEW_UI
Unique name: OAM_REGISTER_VIEW_UI
Description: Privileges to access register maintenance dialogs
Assigned action:
OAMRegisterGlobalUIUser

Configuration Guide
Confidential
4.1.4 Actions
This section lists all available online application submission management actions assignable to roles.
These actions are deployed into the UME automatically during software deployment.
4.1.4.1 OAMAdministrateUserCreateOrganisationUser
Name: OAMAdministrateUserCreateOrganisationUser
Description: This action allows the user to create organisation users belonging to his company.
4.1.4.2 OAMAdministrateUserFindInstitutionUserByElements
Name: OAMAdministrateUserFindInstitutionUserByElements
Description: This action allows the user to find institution users.
4.1.4.3 OAMAdministrateUserFindOrganisationUserByElements
Name: OAMAdministrateUserFindOrganisationUserByElements
Description: This action allows the user to find organisation users belonging to the own company.
4.1.4.4 OAMAdministrateUserFindRolesByGroupUniqueName
Name: OAMAdministrateUserFindRolesByGroupUniqueName
Description: This action allows the user to find available roles for organisation users of his company.
4.1.4.5 OAMAdministrateUserGeneratePassword
Name: OAMAdministrateUserGeneratePassword
Description: This action allows the user to generate passwords for organisation users belonging to his
company.
4.1.4.6 OAMAdministrateUserLockUser
Name: OAMAdministrateUserLockUser
Description: This action allows the user to lock organisation users belonging to the own company.
4.1.4.7 OAMAdministrateUserReadInstitutionUser
Name: OAMAdministrateUserReadInstitutionUser
Description: This action allows the user to read institution users.
4.1.4.8 OAMAdministrateUserReadOrganisationUser
Name: OAMAdministrateUserReadOrganisationUser
Description: This action allows the user to read organisation users belonging to his company.
4.1.4.9 OAMAdministrateUserUnLockUser
Name: OAMAdministrateUserUnLockUser
Description: This action allows the user to unlock organisation users of his company.
4.1.4.10 OAMAdministrateUserUpdateInstitutionUser
Name: OAMAdministrateUserUpdateInstitutionUser
Description: This action allows the user to update institution users.

Configuration Guide
Confidential
4.1.4.11 OAMAdministrateUserUpdateOrganisationUser
Name: OAMAdministrateUserUpdateOrganisationUser
Description: This action allows the user to update organisation users of his company.
4.1.4.12 OAMApplicationApplicantAdmin
Name: OAMApplicationApplicantAdmin
Description: This action allows the user to read, save, create, submit applications and set them as
obsolete.
4.1.4.13 OAMApplicationApplicantDispatcher
Name: OAMApplicationApplicantDispatcher
Description: This action allows the applicant to dispatch and read applications.
4.1.4.14 OAMApplicationAuthorityAdmin
Name: OAMApplicationAuthorityAdmin
Description: This action allows the authority user to read, approve, reject and remove partial applications.
4.1.4.15 OAMApplicationAuthorityGlobalDispatcher
Name: OAMApplicationAuthorityGlobalDispatcher
Description: This action allows the user to read and dispatch partial applications.
4.1.4.16 OAMApplicationAuthorityHierarchicalDispatcher
Name: OAMApplicationAuthorityHierarchicalDispatcher
Description: This action allows the Authority to read and hierarchically dispatch partial applications.
4.1.4.17 OAMApplicationAuthorityLocalDispatcher
Name: OAMApplicationAuthorityLocalDispatcher
Description: This action allows the user to read and locally dispatch partial applications.
4.1.4.18 OAMApplicationFrontOfficeAdmin
Name: OAMApplicationFrontOfficeAdmin
Description: This action allows the user to read, approve, cancel, reject, create, update applications and
set them as obsolete and to add, update, delete partial applications.
4.1.4.19 OAMApplicationFrontOfficeGlobalDispatcher
Name: OAMApplicationFrontOfficeGlobalDispatcher
Description: This action allows the front office employee to read and globally dispatch applications.
4.1.4.20 OAMApplicationFrontOfficeHierarchicalDispatcher
Name: OAMApplicationFrontOfficeHierarchicalDispatcher
Description: This action allows the user to read and hierarchical dispatch applications.
4.1.4.21 OAMApplicationFrontOfficeLocalDispatcher
Name: OAMApplicationFrontOfficeLocalDispatcher
Description: This action allows the front office user to read and locally dispatch applications.

Configuration Guide
Confidential
4.1.4.22 OAMManageApplicantFindApplicantByOrganisationData
Name: OAMManageApplicantFindApplicantByOrganisationData
Description: This action allows the user to find applicants by organisation data.
4.1.4.23 OAMManageApplicantFindApplicantByPersonData
Name: OAMManageApplicantFindApplicantByPersonData
Description: This action allows the user to find applicants by person data.
4.1.4.24 OAMManageApplicantFindApplicantsByKey
Name: OAMManageApplicantFindApplicantsByKey
Description: This action allows the user to find applicants by key.
4.1.4.25 OAMManageApplicantFindApplicationEntererByPersonData
Name: OAMManageApplicantFindApplicationEntererByPersonData
Description: This action allows the user to find application enterers by person data.
4.1.4.26 OAMManageApplicantFindApplicationEntererByUserID
Name: OAMManageApplicantFindApplicationEntererByUserID
Description: This action allows the user to find applicantion enterers by user ID.
4.1.4.27 OAMManageApplicantReadApplicantByKey
Name: OAMManageApplicantReadApplicantByKey
Description: This action allows the user to read applicants by key.
4.1.4.28 OAMManageApplicantReadApplicantByUserID
Name: OAMManageApplicantReadApplicantByUserID
Description: This action allows the user to read applicanta by user ID.
4.1.4.29 OAMManageApplicantUpdateApplicant
Name: OAMManageApplicantUpdateApplicant
Description: This action allows the user to update applicants.
4.1.4.30 OAMManageIndividualReadIndividualByUserID
Name: OAMManageIndividualReadIndividualByUserID
Description: This action allows the user to read individuals by user ID.
4.1.4.31 OAMManageIndividualUpdateIndividual
Name: OAMManageIndividualUpdateIndividual
Description: This action allows the user to update individuals.
4.1.4.32 OAMManageOrganisationEmployeeReadOrganisationEmployeeByUserID
Name: OAMManageOrganisationEmployeeReadOrganisationEmployeeByUserID
Description: This action allows the user to read organisation employees by user ID.

Configuration Guide
Confidential
4.1.4.33 OAMManageOrganisationEmployeeUpdateOrganisationEmployee
Name: OAMManageOrganisationEmployeeUpdateOrganisationEmployee
Description: This action allows the user to update organisation employees.
4.1.4.34 OAMManageOrganisationReadOrganisationByEmployeeUserID
Name: OAMManageOrganisationReadOrganisationByEmployeeUserID
Description: This action allows the user to read organisations by the employee user ID.
4.1.4.35 OAMManageOrganisationUpdateOrganisation
Name: OAMManageOrganisationUpdateOrganisation
Description: This action allows the user to update organisations.
4.1.4.36 OAMManagePrincipalImportPrincipalVCard
Name: OAMManagePrincipalImportPrincipalVCard
Description: This action allows the user to import vCards.
The functionality to import vCards must be provided by a custom implementation.

4.1.4.37 OAMManagePrincipalRegisterPrincipal
Name: OAMManagePrincipalRegisterPrincipal
Description: This action allows the user to register principals.
4.1.4.38 OAMManageUserProfileDMSAddUserToGroup
Name: OAMManageUserProfileDMSAddUserToGroup
Description: This action allows the user to add users to group in the document management system.
4.1.4.39 OAMManageUserProfileDMSCreateUser
Name: OAMManageUserProfileDMSCreateUser
Description: This action allows the user to create users in the document management system.
4.1.4.40 OAMManageUserProfileDMSUpdateUser
Name: OAMManageUserProfileDMSUpdateUser
Description: This action allows the user to update users in the document management system.
4.1.4.41 OAMManageUserProfileUMEAddUserToGroup
Name: OAMManageUserProfileUMEAddUserToGroup
Description: This action allows the user to add users to a group in the UME.
4.1.4.42 OAMManageUserProfileUMECreateUser
Name: OAMManageUserProfileUMECreateUser
Description: This action allows the user to create users in the UME.
4.1.4.43 OAMManageUserProfileUMEFindUsersByElements
Name: OAMManageUserProfileUMEFindUsersByElements
Description: This action allows the user to search users in the UME.

Configuration Guide
Confidential
4.1.4.44 OAMManageUserProfileUMEReadSecurityQuestion
Name: OAMManageUserProfileUMEReadSecurityQuestion
Description: This action allows the user to read security questions in the UME.
4.1.4.45 OAMManageUserProfileUMEUpdateUser
Name: OAMManageUserProfileUMEUpdateUser
Description: This action allows the user to update users in the UME.
4.1.4.46 OAMNotificationJobAction
Name: OAMNotificationJobAction
Description: This action allows a job to read partial application data to send period notifications.
4.1.4.47 OAMProcessLogAction
Name: OAMProcessLogAction
Description: This action allows a user to view the process log and upload or download the questionnaire.
4.1.4.48 OAMRecoverCredentialsReadSecurityQuestion
Name: OAMRecoverCredentialsReadSecurityQuestion
Description: This action allows reading the security question of the user.
4.1.4.49 OAMRecoverCredentialsResetPassword
Name: OAMRecoverCredentialsResetPassword
Description: This action allows the user to reset passwords.
4.1.4.50 OAMRecoverCredentialsSubmitUserIDsByEmail
Name: OAMRecoverCredentialsSubmitUserIDsByEmail
Description: This action allows submitting user IDs by e-mail.
4.1.4.51 OAMRegisterExport
Name: OAMRegisterExport
Description: This action allows the user to export register data
4.1.4.52 OAMRegisterExportApi
Name: OAMRegisterExportApi
Description: This role allows the user to create and download register exports.
4.1.4.53 OAMRegisterGlobalAdmin
Name: OAMRegisterGlobalAdmin
Description: This action allows the user to administrate the local administrators and users.
4.1.4.54 OAMRegisterGlobalReadLocalWriteUser
Name: OAMRegisterGlobalReadLocalWriteUser
Description: This action allows the user to read global register data. However, he can modify register data
only in his specific domain.
4.1.4.55 OAMRegisterGlobalReadUser

Configuration Guide
Confidential
Name: OAMRegisterGlobalReadUser
Description: This action allows the user to read all register data.
4.1.4.56 OAMRegisterGlobalUIUser
Name: OAMRegisterGlobalUIUser
Description: This action allows the user to access register maintenance and customizing UIs.
4.1.4.57 OAMRegisterGlobalUser
Name: OAMRegisterGlobalUser
Description: This action allows the user to read and modify all register data.
4.1.4.58 OAMRegisterImport
Name: OAMRegisterImport
Description: This action allows the user to import register data.
4.1.4.59 OAMRegisterImportApi
Name: OAMRegisterImportApi
Description: This action allows the user to import register data.
4.1.4.60 OAMRegisterImportViewLog
Name: OAMRegisterImportViewLog
Description: This action allows the user to display the import log.
4.1.4.61 OAMRegisterLocalAdmin
Name: OAMRegisterLocalAdmin
Description: This action allows the user to administrate local users.
4.1.4.62 OAMRegisterLocalUser
Name: OAMRegisterLocalUser
Description: This action allows user to read and modify register data only to his specific domain.
4.1.4.63 OAMRegisterManage
Name: OAMRegisterManage
Description: This action allows the user to create, update or delete register data.
4.1.4.64 OAMRegisterManageClassification
Name: OAMRegisterManageClassification
Description: This action allows the user to create, update or delete classifications.
4.1.4.65 OAMRegisterManageClassificationType
Name: OAMRegisterManageClassificationType
Description: This action allows the user to create, update or delete classification types.
4.1.4.66 OAMRegisterManageCommunication
Name: OAMRegisterManageCommunication
Description: This action allows the user to create, update or delete communication data.

Configuration Guide
Confidential
4.1.4.67 OAMRegisterManageCustomizing
Name: OAMRegisterManageCustomizing
Description: This action allows the user to create, update or delete customizing data.
4.1.4.68 OAMRegisterManageDocumentType
Name: OAMRegisterManageDocumentType
Description: This action allows the user to create, update or delete document types.
4.1.4.69 OAMRegisterManageEmployee
Name: OAMRegisterManageEmployee
Description: This action allows the user to create, update or delete employee data.
4.1.4.70 OAMRegisterManageEntity
Name: OAMRegisterManageEntity
Description: This action allows the user to create, update or delete entities.
4.1.4.71 OAMRegisterManageEntityCategory
Name: OAMRegisterManageEntityCategory
Description: This action allows the user to create, update or delete entity categories.
4.1.4.72 OAMRegisterManageEntityCategoryAppParam
Name: OAMRegisterManageEntityCategoryAppParam
Description: This action allows the user to create, update or delete application parameters for the entity
category.
4.1.4.73 OAMRegisterManageEntityInstitution
Name: OAMRegisterManageEntityInstitution
Description: This action allows the user to create, update or delete an entity institution.
4.1.4.74 OAMRegisterManageEntityReference
Name: OAMRegisterManageEntityReference
Description: This action allows the user to create, update or delete entity references.
4.1.4.75 OAMRegisterManageEntityType
Name: OAMRegisterManageEntityType
Description: This action allows the user to create, update or delete entity types.
4.1.4.76 OAMRegisterManageExternalCode
Name: OAMRegisterManageExternalCode
Description: This action allows the user to create, update or delete external codes.
4.1.4.77 OAMRegisterManageForm
Name: OAMRegisterManageForm
Description: This action allows the user to create, update or delete forms.
4.1.4.78 OAMRegisterManageFormField

Configuration Guide
Confidential
Name: OAMRegisterManageFormField
Description: This action allows the user to create, update or delete form fields.
4.1.4.79 OAMRegisterManageFormVariant
Name: OAMRegisterManageFormVariant
Description: This action allows the user to create, update or delete form variants.
4.1.4.80 OAMRegisterManageQuestionGroupFormAssignment
Name: OAMRegisterManageQuestionGroupFormAssignment
Description: This action allows the user to create, update or delete question group form assignments.
4.1.4.81 OAMRegisterManageInstitution
Name: OAMRegisterManageInstitution
Description: This action allows the user to create, update or delete institutions.
4.1.4.82 OAMRegisterManageNamespace
Name: OAMRegisterManageNamespace
Description: This action allows the user to create, update or delete namespaces.
4.1.4.83 OAMRegisterManageOrgUnit
Name: OAMRegisterManageOrgUnit
Description: This action allows the user to create, update or delete organisational units.
4.1.4.84 OAMRegisterManagePayment
Name: OAMRegisterManagePayment
Description: This action allows the user to create, update or delete payment data.
4.1.4.85 OAMRegisterManagePublicServiceAuthority
Name: OAMRegisterManagePublicServiceAuthority
Description: This action allows the user to create, update or delete public service authorities.
4.1.4.86 OAMRegisterManagePublicServiceType
Name: OAMRegisterManagePublicServiceType
Description: This action allows the user to create, update or delete public service types.
4.1.4.87 OAMRegisterManagePublicServiceTypeCharge
Name: OAMRegisterManagePublicServiceTypeCharge
Description: This action allows the user to create, update or delete charges for public service types.
4.1.4.88 OAMRegisterManagePublicServiceTypeDocument
Name: OAMRegisterManagePublicServiceTypeDocument
Description: This action allows the user to create, update or delete documents of public service types.
4.1.4.89 OAMRegisterManagePublicServiceTypePeriod
Name: OAMRegisterManagePublicServiceTypePeriod
Description: This action allows the user to create, update or delete periods for public service types.

Configuration Guide
Confidential
4.1.4.90 OAMRegisterManageQuestion
Name: OAMRegisterManageQuestion
Description: This action allows the user to create, update or delete questions.
4.1.4.91 OAMRegisterManageQuestionGroup
Name: OAMRegisterManageQuestionGroup
Description: This action allows the user to create, update or delete question groups.
4.1.4.92 OAMRegisterManageRule
Name: OAMRegisterManageRule
Description: This action allows the user to create, update or delete rules.
4.1.4.93 OAMRegisterManageSelectionList
Name: OAMRegisterManageSelectionList
Description: This action allows the user to create, update or delete selection lists.
4.1.4.94 OAMRegisterManageSelectionValue
Name: OAMRegisterManageSelectionValue
Description: This action allows the user to create, update or delete selection values.
4.1.4.95 OAMRegisterManageSmc
Name: OAMRegisterManageSmc
Description: This action allows the user to create, update or delete subject-matter competences.
4.1.4.96 OAMRegisterManageUserLocalization
Name: OAMRegisterManageUserLocalization
Description: This action allows the user to create, update or delete a user localisation.
4.1.4.97 OAMRegisterQuery
Name: OAMRegisterQuery
Description: This action allows the user to read or find register data.
4.1.4.98 OAMRegisterQueryClassification
Name: OAMRegisterQueryClassification
Description: This action allows the user to read or find classifications.
4.1.4.99 OAMRegisterQueryClassificationType
Name: OAMRegisterQueryClassificationType
Description: This action allows the user to read or find classification types.
4.1.4.100 OAMRegisterQueryCommunication
Name: OAMRegisterQueryCommunication
Description: This action allows the user to read or find communication data.

Configuration Guide
Confidential
4.1.4.101 OAMRegisterQueryCustomizing
Name: OAMRegisterQueryCustomizing
Description: This action allows the user to read or find customizing data.
4.1.4.102 OAMRegisterQueryDocumentType
Name: OAMRegisterQueryDocumentType
Description: This action allows the user to read or find document types.
4.1.4.103 OAMRegisterQueryEmployee
Name: OAMRegisterQueryEmployee
Description: This action allows the user to read or find employees.
4.1.4.104 OAMRegisterQueryEntity
Name: OAMRegisterQueryEntity
Description: This action allows the user to read or find entities.
4.1.4.105 OAMRegisterQueryEntityCategory
Name: OAMRegisterQueryEntityCategory
Description: This action allows the user to read or find entity categories.
4.1.4.106 OAMRegisterQueryEntityCategoryAppParam
Name: OAMRegisterQueryEntityCategoryAppParam
Description: This action allows the user to read or find application parameters of entity categories.
4.1.4.107 OAMRegisterQueryEntityInstitution
Name: OAMRegisterQueryEntityInstitution
Description: This action allows the user to read or find entity institutions.
4.1.4.108 OAMRegisterQueryEntityReference
Name: OAMRegisterQueryEntityReference
Description: This action allows the user to read or find entity references.
4.1.4.109 OAMRegisterQueryEntityType
Name: OAMRegisterQueryEntityType
Description: This action allows the user to read or find entity types.
4.1.4.110 OAMRegisterQueryExternalCode
Name: OAMRegisterQueryExternalCode
Description: This action allows the user to read or find external codes.
4.1.4.111 OAMRegisterQueryForm
Name: OAMRegisterQueryForm
Description: This action allows the user to read or find forms.

Configuration Guide
Confidential
4.1.4.112 OAMRegisterQueryFormField
Name: OAMRegisterQueryFormField
Description: This action allows the user to read or find form fields.
4.1.4.113 OAMRegisterQueryFormVariant
Name: OAMRegisterQueryFormVariant
Description: This action allows the user to read or find form variant.
4.1.4.114 OAMRegisterQueryQuestionGroupFormAssignment
Name: OAMRegisterQueryQuestionGroupFormAssignment
Description: This action allows the user to read or find Question Group Form Assignment.
4.1.4.115 OAMRegisterQueryInstitution
Name: OAMRegisterQueryInstitution
Description: This action allows the user to read or find institutions.
4.1.4.116 OAMRegisterQueryNamespace
Name: OAMRegisterQueryNamespace
Description: This action allows the user to read or find namespaces.
4.1.4.117 OAMRegisterQueryOrgUnit
Name: OAMRegisterQueryOrgUnit
Description: This action allows the user to read or find organisational units.
4.1.4.118 OAMRegisterQueryPayment
Name: OAMRegisterQueryPayment
Description: This action allows the user to read or find payment data.
4.1.4.119 OAMRegisterQueryPublicServiceAuthority
Name: OAMRegisterQueryPublicServiceAuthority
Description: This action allows the user to read or find public service authorities.
4.1.4.120 OAMRegisterQueryPublicServiceType
Name: OAMRegisterQueryPublicServiceType
Description: This action allows the user to read or find public service types.
4.1.4.121 OAMRegisterQueryPublicServiceTypeCharge
Name: OAMRegisterQueryPublicServiceTypeCharge
Description: This action allows the user to read or find charges for public service types.
4.1.4.122 OAMRegisterQueryPublicServiceTypeDocument
Name: OAMRegisterQueryPublicServiceTypeDocument
Description: This action allows the user to read or find documents of public service types.

Configuration Guide
Confidential
4.1.4.123 OAMRegisterQueryPublicServiceTypePeriod
Name: OAMRegisterQueryPublicServiceTypePeriod
Description: This action allows the user to read or find periods of public service types.
4.1.4.124 OAMRegisterQueryQuestion
Name: OAMRegisterQueryQuestion
Description: This action allows the user to read or find questions.
4.1.4.125 OAMRegisterQueryQuestionGroup
Name: OAMRegisterQueryQuestionGroup
Description: This action allows the user to read or find question groups.
4.1.4.126 OAMRegisterQueryRule
Name: OAMRegisterQueryRule
Description: This action allows the user to read or find rules.
4.1.4.127 OAMRegisterQuerySelectionList
Name: OAMRegisterQuerySelectionList
Description: This action allows the user to read or find selection lists.
4.1.4.128 OAMRegisterQuerySelectionValue
Name: OAMRegisterQuerySelectionValue
Description: This action allows the user to read or find selection values.
4.1.4.129 OAMRegisterQuerySmc
Name: OAMRegisterQuerySmc
Description: This action allows the user to read or find subject-matter competences.
4.1.4.130 OAMRegisterQueryTypedRule
Name: OAMRegisterQueryTypedRule
Description: This action allows the user to read or find typed rules.
4.1.4.131 OAMRegisterQueryUserLocalization
Name: OAMRegisterQueryUserLocalization
Description: This action allows the user to read or find a user localisation.
4.1.4.132 OAMSimulationUser
Name: OAMSimulationUser
Description: This action allows the user to simulate an application process.
4.1.4.133 OAMUserTypeApplicantIndividual
Name: OAMUserTypeApplicantIndividual
Description: This action identifies the user as an individual applicant.

Configuration Guide
Confidential
4.1.4.134 OAMUserTypeApplicantOrganisationEmployee
Name: OAMUserTypeApplicantOrganisationEmployee
Description: This action identifies the user as an applicant organisation employee.
4.1.4.135 OAMUserTypeAuthorityEmployee
Name: OAMUserTypeAuthorityEmployee
Description: This action identifies the user as an authority employee.
4.1.4.136 OAMUserTypeDepartmentHierarchyUserAdministrator
Name: OAMUserTypeDepartmentHierarchyUserAdministrator
Description: This action identifies the user as delegated user administrator of an department within the
hierarchy of an institution.
4.1.4.137 OAMUserTypeDepartmentUserAdministrator
Name: OAMUserTypeDepartmentUserAdministrator
Description: This action identifies the user as delegated user administrator of a department of an
institution.
4.1.4.138 OAMUserTypeFrontOfficeEmployee
Name: OAMUserTypeFrontOfficeEmployee
Description: This action identifies the user as front office employee.
4.1.4.139 OAMUserTypeInstitutionUserAdministrator
Name: OAMUserTypeInstitutionUserAdministrator
Description: This action identifies the user as delegated user administrator of an institution.
4.1.4.140 OAMUserTypeQueryVariantAdministrator
Name: OAMUserTypeQueryVariantAdministrator
Description: This action identifies the user as a query variant administrator.

Configuration Guide
Confidential
4.2 Connecting Online Application Submission Management to Other

Systems
This chapter describes all necessary configuration steps to connect online application submission
management to other systems.
4.2.1 SAP Portal and Document Management System (DMS)

The system architecture of the solution consists of the application management and document
management.
All application documents of the application parties such as attachments, forms, certificates, message
forms and notices are stored in the document management system.
To facilitate the integration of the document storage, we recommend that you use the Knowledge
Management component of the SAP Enterprise Portal based on the SAP NetWeaver 7.0 component.
You can also use an already available document management system (for example a file system) that
supports the following features:
Folder Structures: The DMS must be able to support necessary folder structure creation.
Document Versions: The DMS must have the ability to track versions of all stored documents. This
feature allows you to track application or document versions.
User-Specific Authorisations: The DMS must have the ability to restrict system access using
predefined roles to ensure the necessary security.
To enable an already available document management system to be used with online application
submission management, and to support the predefined web service interface, additional development is
required.
The standard delivery of the online application submission management solution contains an
implementation of the above document management interface based on the component SAP NetWeaver
7.0 Enterprise Portal with Knowledge Management & Collaboration. The implementation consists of the
following:
A defined interface for the external systems, provided as a web service on the SAP NetWeaver 7.0
platform. Within the delivered solution, the existing Application Programming Interfaces (APIs) of the
Knowledge Management component are used to implement the functionalities.
Within the online application submission management solution, the functionality of the interface is used by
a web service client proxy.
The above mentioned web service client proxy works through a technical user.
Web Service Setup Knowledge Management
To set up the system, your user must belong to the Administrators group.
Creating Logical Ports for the DMS Web Service
Create the Logical ports as described below:
1. Open the NetWeaver Administrator of SAP NetWeaver CE 7.1 system using the link
http://<HostName>:<Port>/nwa.
2. Log on using your user name and password.
3. Choose SOA Management Application and Scenario Communication Single Service
Administration Consumer Proxies.

Configuration Guide
Confidential
4. Select the WSDL Porttype Name from the dropdown list and find Multi*; then choose Go.
5. Select the following table entry:
Proxy definition : MultiClientKMVi_Document
Internal Name:
sap.com/cdev~acs~eusd~bc~app_sap.com~cdev~acs~eusd~bc~dao_EJB/ManageDMSInDAOB
ean/MultiClientKM_Config1Binding_MultiClientKMVi_Document
6. Choose the Configuration tab page.
7. A Logical Port is already present; by default the port points to the server used for generating the
client.
8. Select the default port Config1Port_Document and change the settings to use the available SAP
EP KM 7.0 server.
9. Choose the Edit pushbutton.
10. Select the General tab page.
11. In the field WS Endpoint URL, enter the required URL for the DMS Web Service:
http://<Host Name>:<Port No>/ MultiClientKM/Config1?style=document.
12. Choose the Security tab page.
13. Select the UserID/Password (Basic) radio button and enter the User ID and Password of a user
having admin rights on the KM root folder. For more information, see the section on Main Folders
for Solution Documents for Online Application Submission Management.
14. In case the documents to be uploaded are bigger in size, increase the time out for the Web
Service.
15. Choose the Transport Settings tab page.
16. Increase the value of the field Max wait-time for http response (in milliseconds): 960000.
The value depends on the size of the documents being uploaded. However, this value will
support a maximum document size of 20 Mb.
17. In case you do not want to use the default port then create a new Logical Port.
18. Choose the New pushbutton.
19. Select the Enter Manually radio button.
20. Then choose Next.
21. In the field Logical Port Name, enter any port name, for example, DMS_TECH_USER and check
the Set as default check box (if this needs to be the default port for this web service).
22. In the field WS Endpoint URL, enter the required URL for the DMS Web Service:
http://<Host Name>:<Port No>/MultiClientKM/Config1?style=document
24. Select HTTP Authentication from the dropdown list Authentication.
25. Select the UserID/ Password (Basic) radio button and enter the User ID and Password of a user
having admin rights on the KM root folder (user who belongs to the OAM _ADMIN_USERS
group). For more information, see section Main Folders for Solution Documents for Online
Application Submission Management.
26. Choose Next. No changes are required.

Configuration Guide
Confidential
27. Choose Next again. No changes are required.

29. Change the value of the field Max wait-time for http response (in milliseconds), if required.
30. Choose the Finish pushbutton.
4.2.1.1 User Management Support of DMS and Portal UME
The SAP Identity Management is an integral component of the online application submission
management solution. It manages users as described above (see section SAP User Management Engine
(UME)). This section focuses on special scenarios where the document management system (DMS) and
the portal navigation for online application submission management is running on different systems linked
to a SAP User Management Engine (UME); in short, scenarios where the user storage is different for
online application submission management as opposed to the user storage in the DMS or the Portal.
Online application submission management supports rudimentarily the integration of another DMS user
store by updating this user store upon user changes in the user store of online application submission
management. The following operations are supported and realised by Service Provisioning Markup
Language (SPML) message exchanges:
user creation
user update
user group assignments
password synchronizations
By default, nothing happens. To enable the desired functionality, the following application properties
have to be set to true:
eusd.common.dms.ume.userCreationEnabled
eusd.common.dms.ume.userUpdateEnabled
eusd.common.dms.ume.userGroupAssignmentEnabled
eusd.common.dms.ume.userAccountChangeEnabled
An Service Provisioning Markup Language (SPML) message is generated and sent to the DMS UME in
case of corresponding UME data changes in online application submission management for each
enabled functionality. These changes can be triggered in various occasions such as during registration,
profile maintenance or delegated user administration.
As a prerequisite for successfully transmitting data in the DMS UME, the Service Provisioning Markup
Language (SPML) service must be installed and active on this system. This can be quickly verified using
the following URL: http<s>://<host>:<port>/spml/spmlservice
To connect to the DMS for the purpose described above, the following application properties have to be
set:
eusd.common.dms.url
eusd.common.ume.spmlService
eusd.common.ume.dmsUser
eusd.common.ume.dmsPassword
For more information, see Application Properties.

Configuration Guide
Confidential
The following user data are transferred to the DMS UME in the following cases:
Case Transferred User Data

User Creation Unique name, first name, last name, e-mail address, locale and
password
User Update Unique name, first name, last name, e-mail address and locale
User Group Assignment Unique name of user and unique name of group
As prerequisite the following groups with corresponding unique names have to exist in the DMS UME:
OAM_USER_GROUP_APPLICANT_INDIVIDUAL
Assignable at registration as applicant individual
OAM_USER_GROUP_APPLICANT_ORGANISATION_ADMINISTRATOR
Assignable at registration as applicant organisation employee
OAM_USER_GROUP_APPLICANT_ORGANISATION
Assignable at user creation via delegated user administration for applicant organisations
OAM_USER_GROUP_INSTITUTION
Assignable at user creation in registers
The user group assignment functionality allows customers to have more flexibility in handling the users in
the DMS UME regarding the roles by assigning them accordingly to user groups instead of users directly.
The following user data are transferred to the DMS UME in case of user account change:
Case Transferred User Data

User Account Change Unique name, password and flag for required password change
4.2.1.2 Setup Knowledge Management in SAP Portal 7.0

Get familiar with the Knowledge Management Security Guide available in the SAP Help Portal at
http://help.sap.com SAP Net Weaver SAP NetWeaver 7.0 (2004s) Knowledge Center System
Administration Security Guide SAP NetWeaver Security Guide Security Guides for SAP
NetWeaver According to Usage Types Security Guides for Usage Types EPC and EP Knowledge
Management Security Guide.
For more information about restricting unauthorised access to the document folders and documents, see
SAP Note 599425.
To set up the system, you must belong to the Administrators role group.
After deployment of the implementation of the document management system (in this case the default
implementation for SAP Enterprise Portal Knowledge Management) on the SAP Enterprise Portal 7.0
server, you must make the following configurations.
4.2.1.2.1 Settings for the URL Generator Service

Set up the basis URL of the host system in the URL Generator Service (part of the standard customizing).
To set up the basis URL of the host system, proceed as follows:

Configuration Guide
Confidential
1. Log on to the SAP Portal using your administrator user name and password.
2. Choose System Administration System Configuration Knowledge Management Content
Management Global Services URL Generator Service (visible in the extended mode).
The system displays a list of entry fields.
3. Choose the Edit pushbutton.
4. Enter the basis URL of the host system in the Host field name according to the following scheme:
http://<your host number>:<your port number>
4.2.1.2.2 Create a Repository Manager for Solution Documents

To provide maximum security, it is required to create an own repository manager for the documents for
the Online application submission management solution. Do not store them in the default documents
folder.
1. Log on to the SAP Portal using your administrator user name and password.
2. Choose System Administration System Configuration Knowledge Management Content
Management Repository Managers CM Repository.
3. Create a new CM Repository Manager with a suitable name, for example OAM.
4.2.1.2.3 Main Folders for Solution Documents for Online Application Submission Management
Create the main folders for the solution documents as follows:
1. Choose Content Administration KM Content Root Documents.
Locate the folder that represents the newly created repository manager, for example OAM. In the
following steps, it is called <OAM_ROOT>.
2. Restrict the access to the root folder by allowing access only to administrative users and roles.
3. Create a new group (for example, OAM _ADMIN_USERS); then manually assign all users you
want to allow administrative access (for example, a front office employee).
4. Create a subfolder using a name of your choice (for example DocumentSafe) in the
<OAM_ROOT> folder.
For each application, the system creates a new folder (using the application ID name) in the
folder created above; and all the application related documents are stored in this folder.
5. Activate KM versioning for the subfolders.
4.2.1.2.4 Maintain Document Folder Paths

Maintain the path to the new root folder and its subfolders in the application properties of the KM proxy
implementation of online application submission management. These properties are maintained using the
Visual Administrator (standard administration tool) of the SAP NetWeaver System 7.0.
Maintain the required paths as follows:
1. On the system where the portal installation exists, navigate to the following location:
<Installation Drive>/usr/sap/<SID>/JC<InstanceNo>/j2ee/admin
The above is an example of a path in a system based on Microsoft Windows; the path can
change with respect to the operating system.

Configuration Guide
Confidential
2. Execute go.bat.
3. Navigate to Server <Instance>/services/Configuration Adapter.
4. Choose Runtime Display Configuration Window; then choose to apps sap.com
cdev~acs~eusd~dms~km~ear appcfg Propertysheet application.global.properties.
5. Maintain values for the following two given properties as described below:
o For the property eusd.dms.km.repository.documentsafe, maintain the same value as the
one maintained for the property eusd.common.dms.repository_name in the SAP
NetWeaver CE 7.1 EhP1 system, where application folders must be created to store the
application documents.
o For the property eusd.dms.km.repository.root, maintain the value for the location where
the root folder for all applications is created. For example, if the value of the property
eusd.dms.km.repository.documentsafe is maintained as /OAM, which is the location of
the application root folder, then the value of the property eusd.dms.km.root must be "/".
The following screenshot illustrates the property settings described above:
Figure 2: Visual Administrator
4.2.1.3 KM-Specific Customizing in Online Application Submission Management

In order to integrate the document management system (DMS) with the online application submission
management system, certain properties need to be maintained.
Make the following configuration:

Configuration Guide
Confidential
1. Open the SAP NetWeaver Administrator of the SAP NetWeaver CE 7.1 EhP1 system using the
link http://<host>:<port>/nwa.
2. Log on using your SAP NetWeaver Administrator user name and password.
3. Choose Configuration Management Infrastructure Java System Properties.
4. Select the activated CE template
5. In the Details section, choose the Applications tab page.
6. In the table, select the application cdev~acs~eusd~common~app
In the view Extended Details, all application parameters for online application submission
management are displayed and can be maintained.
You must maintain at least the following main parameters:
o KM system root repository for application documents:
(eusd.common.dms.repository_name= /documents/OAM/DocumentSafe
For more information, see the section on Main Folders for Solution Documents for
Online Application Submission Management.
o Logical Port to be used for the KM Web Service with Basic (User ID/ Password)
Authentication: eusd.common.dms.techuser.binding_port
(Use the configured logical port name. See Settings for the URL Generator Service.)
4.2.2 Adobe Document Services

To work with Adobe forms, you must ensure that Adobe Document Services (ADS) is configured on the
SAP NetWeaver Composition Environment (CE) server.
For more information about ADS setup and installation of the ReaderRights Credentials, see the SAP
Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver CE SAP NetWeaver
Composition Environment 7.1 Including Enhancement Package 1 SAP NetWeaver Composition
Environment 7.1 EHP 1 Library Administrator's Guide Configuration of SAP NetWeaver CE
Configuration for CE Additional Components Configuring Adobe Document Services for CE (SAP
Library - Administrator's Guide).
Download the ADS credentials from SAP Note 736902. To install the credentials, you also require access
to the directory of the system that hosts the Adobe document services.
For more information about relevant steps to configure ADS, see the SAP Help Portal at
http://help.sap.com SAP NetWeaver SAP NetWeaver CE SAP NetWeaver Composition
Environment 7.1 Including Enhancement Package 1 SAP NetWeaver Composition Environment 7.1
EHP 1 Library Administrator's Guide Configuration of SAP NetWeaver CE Configuration for CE
Additional Components Configuring Adobe Document Services for CE (SAP Library - Administrator's
Guide).

Configuration Guide
Confidential
4.2.3 Destinations for Forms

To define form variants in the form register, you must use a specific URL containing the destination
identifier the in following format:
dest: <http-destination-name>/<alias>/<formular-template-name.xdp>
dest:
FORM_DEST_ID_REG_DATAMODEL_1/FORMS_ALIAS_REG_DATA_MODEL_1/Address_Template1.x
dp.
You must maintain the destination identifier, for example FORM_DEST_ID_REG_DATAMODEL_1, under
the SAP NetWeaver Administrator, as follows:
1. Open the SAP NetWeaver Administrator using the link http://<host>:<port>/nwa.
2. Log on using the SAP NetWeaver Administrator user name and password.
3. Navigate to Configuration Management Security Destinations.
4. Create a new HTTP destination and enter the root URL of the server where the forms reside.
See the following screenshot:
Figure 3: HTTP Destination for Form Folder
To configure the access to the folder in which the forms reside, proceed as follows:
2. Log on using the SAP NetWeaver Administrator user name and password.
3. Choose Configuration Management Connectivity Java HTTP Provider Configuration.

Configuration Guide
Confidential
4. On the Virtual Hosts tab, check the following:
Figure 4: Clearing Cache
To display an Adobe Form in the online application submission management application, you must first
create the template in Adobe LiveCycle Designer (ALD) 8.1 or above. For more information about the
installation of ALD 8.1 and SAP NetWeaver release compatibility, see SAP Note 1176858.
To display and execute an interactive form on the browser in a platform and browser independent
manner, use Zero Client Installation (ZCI) style forms. The templates created on ALD 8.1 will contain the
latest ZCI scripts. However, if you created templates and used with SAP NetWeaver CE 7.1 EhP 1
before, the scripts would be automatically updated from the Adobe Document Service (ADS) server.
If a new template is added to the folder or the existing one is modified and changes are not being
reflected in the application, you can choose the Clear Cache pushbutton highlighted in the screenshot
(see below).
Adobe Reader 8.1 or higher version must be installed on client side for displaying and editing the forms in
the application. For more information about interactive forms, Web Dynpro Java limitations and
recommendations, see SAP note 1090464.
The physical path of the folder which is used to store the XDP and XML templates should be provided in
in the Aliases tab. The name given as alias, for example FORMS_ALIAS_REG_DATA_MODEL_1, shall
be used to specify a destination URL of the template later.

Configuration Guide
Confidential
Figure 5: Alias
If you use Adobe forms for message communication, use the following field names during creation of
XML Data Package (XDP) templates.
Field Name Preferred Type Required Type/Values
_APPLICATIONID String
_PARTIALAPPLICATIONID String
If an XML template mapping is being used, the data node under which the fields specified above are
created should be named DataNode.
If HTML Forms are being used, the fields for the application ID and partial application ID must be children
of the root node. The root node name can by any name in that case.
The application ID and the partial application ID are prefilled automatically in the form used for message
creation or filling the application form, if they are created as specified above.
For prefilling other fields of the template, make the necessary configuration in the form register. For more
information about creating forms in the registers, see the application help documentation on SAP Service
Marketplace at http://service.sap.com/swdc Software Downloads Installations and Upgrades
Browse our Download Catalog SAP Development Projects ONLINE APP SUBMISSION MGMT
ONLINE APP SUBMISSION MGMT 2.0 Technical Documentation Anwendungshilfe.

Configuration Guide
Confidential
4.2.4 Address Validation Service

An interface has been provided for validating the address of users during registration and modification of
personal data. This interface can be used to plug in concrete implementation for validating addresses.
SAP Note 1527526 delivers the Web Services Description Language (WSDL) file for address validation.
A consumer proxy using the same WSDL has been created in online application submission management
which can be configured for multiple logical ports. Validation service loops over all logical ports to call the
service implementations of various provider systems and collective error messages are returned to the
user.
To configure logical ports for a consumer proxy, proceed as follows:
1. Open the SAP NetWeaver Administrator.
2. Choose Configuration Management Connectivity Single Services Administration
Consumer Proxies Browse.
3. Select Software Components from dropdown menu.
4. Navigate to your application development component for example sap.com/CDPEUSD_BC
sap.com/ cdev~acs~eusd~bc~app and expand the node.
5. Select the consumer proxy named AddressValidation.
Figure 6: Consumer Proxies
6. Choose the Configuration tab in the details section.

Configuration Guide
Confidential
Figure 7: Configuration Tab
7. You can either modify the existing default logical port or create a new one.
8. To create or edit a logical port, the following information is required:
a. Service end point URL
b. User name and password to access the provider system
The web service endpoint URL can be found in the WSDL document, if the end point has already been
created for the web service. If a web service has no end points, create the end point and generate the
WSDL again. This is displayed in the location property of the port as shown in the following code
excerpt:
<service xmlns="http://schemas.xmlsoap.org/wsdl/" name="service name">
<port name="<endpoint name>" xmlns:bref="http://ip.test/"
binding="bref:DefaultService_">
<address xmlns="http://schemas.xmlsoap.org/wsdl/soap/"
location="<endpoint URL>" />
</port>
</service>
9. If you are editing the existing one, provide details as shown below.

Configuration Guide
Confidential
Figure 8: Logical Port
10. For creating a new logical port, choose the New pushbutton.
Figure 9: Address Validation Proxy Definition
11. Select the Enter Manually radio button.

Configuration Guide
Confidential
Figure 10: Enter Manually Radio Button
12. Provide the logical port name and web service end point URL.
13. Choose the Next pushbutton.
Figure 11: Logical Port Name
14. Provide the user ID and password details.

15. Choose the Finish pushbutton.

Configuration Guide
Confidential
Figure 12: User ID and Password
The logical ports created above should be specified as comma separated values in the application
property eusd.common.address.validation.logicalPorts. Define the sequence in which the system calls the
web service, for example AddressValidation_Port and AddressValidation1.

Configuration Guide
Confidential
4.2.5 Implement Virus Scanning in SAP NetWeaver CE 7.1

To implement virus scanning in SAP NetWeaver CE 7.1 EhP1, proceed as follows:
1. Download the virus scan adapter based on your antivirus product.
See SAP note 1494278 to check the Virus Scan Adapter. The adapter which is named in the
present document is used for testing purposes to test the eicar file.
To download the test adapter check the following location:
ftp://ftp.sap.com/pub/icc/nw-vsi/VSA-SDK-1.0.zip
2. Unzip the virus scan adapter file.
3. This directory contains the dll file for various operating systems. Check your operating system
version and copy the dll file from the directory to your local drive.
Use NTAMD64 dll.
If the configuration on your machine is is AMD 64 bit, copy the dll file from
VSA-SDK-1.0/vssap/opt/NTAMD64/vssap.dll to your local drive for ex
C:\vssap\
Figure 13: Downloading the Virus Scan Adapter
4. Select one of the following installation types for the virus scan provider, depending on your
system prerequisites:
Virus scan adapter
This procedure describes the normal case in which you are using a local virus scan adapter.
The virus scan adapter is a native dynamic library from a third-party vendor, which can be

Configuration Guide
Confidential
loaded directly into the process environment of the J2EE Engine. It allows you to check
memory contents directly for viruses, and thus help in achieving a higher performance.
Virus scan server
This procedure describes the special case, in which the platform or process architecture does
not allow the direct inclusion of a virus scan adapter. This is the case, for example, if the
required operating system for SAP NetWeaver is not compatible with the external anti-virus
product. In this case, use a virus scan server. The virus scan server communicates with the
J2EE Engine using TCP/IP (SAP RFC protocol) and accesses the external anti-virus product
using a virus scan adapter.
4.2.5.1 Configure the Virus Scan Adapter
To configure the virus scan adapter, open the link http://<Server>:<port>/nwa. Then choose Go
To Configuration Management Security Virus Scan Provider.
4.2.5.2 Create a Virus Scan Group
To create the virus scan group, perform the following steps:
1. Switch to the Edit mode by choosing the Edit pushbutton, as shown in the following screenshot.
2. Choose the Groups tab page.
3. Choose Add to create a scanner group.
Figure 14: Create a Virus Scan Group
4. Choose a name of the group and enter it in the in Group Name field and choose Continue.
A new row is added in the Virus Scan Groups group box.
5. Choose the Settings tab page.
In the Description field on the Virus Scan Group Details group box, enter a description for the
group.
6. Select the Default scan group checkbox to set the group as the default virus scan group.
7. Choose Save.

Configuration Guide
Confidential
Figure 15: Create a Virus Scan Group

4.2.5.3 Create a Virus Scan Adapter
You can create the virus scan provider either as a virus scan adapter on the Adapters tab or as a virus
scan server on the Servers tab as follows:
1. Switch to the edit mode by choosing the Edit pushbutton.
2. Choose the Adapters tab page or the Servers tab page, as required; then choose Add to create a
scanner group.
3. Enter the Adapter Name. The adapter name should start with the prefix VSA_.
Figure 16: Create a Virus Scan Adapter
4. Choose Continue.
A new row is added in the Virus Scan Adapters group box.
You can enter the following data in the Virus Scan Adapter Details group box on the Settings tab
page.

Configuration Guide
Confidential
Settings for the Virus Scan Adapter
Field Entry
Checkbox indicating that this Virus Scan Provider is the default provider.
Default Scan You can select this checkbox only for one Virus Scan Provider. This Virus Scan
Provider Provider is used, if an application requests a virus scanner without specifying a
Virus Scan Provider.
Adapter The name of the virus scan adapter is displayed. The name entered is
Name automatically saved with the prefix VSA_.
Adapter
Description of the current adapter
Description
The input help provides a list of the available groups to which you can assign the
Scan Group
current adapter.
Default =0
Reinitialisation interval of the Virus Scan Adapter in hours. This specifies the
Init. Interval number of hours after which the Virus Scan Adapter is to be reinitialised.
(hours) If you receive new virus definitions at regular intervals which the Virus Scan
Adapter has to load, a reinitialisation is required.
If you enter the value 0, the virus scan adapter is not automatically reinitialised.
Default =20
Max. Specifies the maximum number of scan instances provided by the Virus Scan
Instances Server, with which you define how many of these instances are provided. If this
number is exceeded, the virus scanner is no longer available for scan requests.
VSA Library Enter the path where you have saved vssap.dll on your local hard disk, for
Path example C:\vssap\vssap.dll
5. To activate a trace output for the Virus Scan Provider, select the desired checkbox on the Trace
tab page.
6. Save your configuration.
7. Select the Virus Scan Adapter.
8. Choose the Activate pushbutton to activate the virus scan adapter.

Configuration Guide
Confidential
Figure 17: Create a Virus Scan Adapter
4.2.5.4 Set Up the Virus Scan Profile

To set up the virus scan profile, proceed as follows:
1. Choose the Profiles tab page.
2. Create a virus scan profile by choosing the Add pushbutton in the edit mode.
3. In the Profile Name field, enter the appropriate name after the predefined prefix.
4. Choose Continue.
A new row is added in the Virus Scan Profiles group box.
5. In the Virus Scan Profile Details group box, enter the Profile Description.
6. Choose the Add pushbutton.
7. Select the Group from the dropdown list in the first column.
8. Select the Group name from the dropdown list in the second column.
9. Save and activate the profile.

Configuration Guide
Confidential
Figure 18: Create a Virus Scan Profile
10. Select the profile webdynpro_fileupload from the available profiles and edit it.
11. Select the reference profile on the Settings tab page.

Configuration Guide
Confidential
Figure 19: Reference Profile Setting

12. Set the following parameters for the profile webdynpro_fileupload:
o CUST_NO_SCANINFO: Type as BOOL; Value as FALSE
o SCANALLFILES: Type as BOOL; Value as TRUE
o SCANBESTEFFORT: Type as BOOL; Value as TRUE
o CUST_NOT_SCANNED_AS_WARNING: Type as BOOL; Value as TRUE
Figure 20: Reference Parameter Settings

Configuration Guide
Confidential
13. Activate the profile.
4.2.5.5 Test Virus Scan Interface
4.2.5.5.1 Check Configuration

Follow the steps below to check correctness of configuration you have just finished above.
1. Start the test application under the path /vscantest.
2. Specify the object to be checked, using either the test data provided or your own local file.
a. Select the virus scan profile, scanner group, or the virus scan provider to be tested.
b. Select an action.
The following two checks are possible:
o Check Only: scans the data for viruses and then display the results
o Check and Clean: scans the data for viruses and then cleans the virus infected data,
then displays the results
3. Start the test by choosing Execute the action.
4.2.5.5.2 Test Using eicar

You can also test the virus scanning functionality in the online application submission management
solution by downloading the eicar virus test file from the www.eicar.org website.
When you upload the file as attachment to an application, an error message appears.
The information provided in this document is based on the adapter provided by SAP for testing purposes.
This adapter will only test the eicar test file. To implement the real time virus scanning, ask your security
provider for an appropriate adapter.
Further configuration might be necessary based on the specific adapter. For more information, contact
your security provider.

Configuration Guide
Confidential
4.2.6 Integration of CAPTCHA (Completely Automated Public Turing

test to tell Computers and Humans Apart)
It is possible to have an additional sub screen on the self-registration screen. You can add the CAPTCHA
validation to avoid fake computer-generated user registrations. You can also add some extra options to
validate the input provided by the user on the screen as almost all of the data is exposed on the interface.
There is a predefined interface which you can implement. Besides, you can add your own screen and
validate input from the user accordingly. The details of the interface are as follows:
Figure 21: Interface Details for Validation

All the data on the self-registration screen is exposed in the Web Dynpro Context where you can add
additional validations. Besides, an interface view is defined which you can implement and by making
more configurations it will be displayed in the bottom of the second step on the self-registration screen.

Configuration Guide
Confidential
Figure 22: Interface Details for Validation

By using this validation data method, which must be implemented by a custom implementation, you can
provide the input back to the application using logGDT. All messages added to it, will be displayed on the
screen.
In order to implement this interface, you need to maintain some dependencies in the development
component in which the implementing component resides as shown below. Then create a new
component in your own development component to implement the above mentioned interface.
Figure 23: Development Component

Configuration Guide
Confidential
After implementing the above mentioned interface, maintain the configuration. Choose SAP NetWeaver
Administrator Configuration Management Infrastructure Java System Properties and then choose
the Applications Tab in the Details screen in order to activate the implementation (see below).
Figure 24: Configuration for Implementation

The default values are for the default implementation provided with a blank screen. In order to activate
the implementation, you need to provide the component and development component details.
Provide the web dynpro component details which implement the interface:
eusd.cust.SelfRegSubScreenComponent.compname
Provide the development component name belonging to the web dynpro component:
eusd.cust.SelfRegSubScreenComponent.dcname

Configuration Guide
Confidential
4.3 Specific Customizing for Online Application Submission

Management
4.3.1 Customisable E-Mail Notification Templates
Within the Online application submission management system, certain actions in the application process
result in e-mail notifications to inform an application party about the action, for example a status update.
The e-mail can be configured as follows:
The e-mail subject and text are completely customisable. You can provide a language-dependent
text and content for the e-mail subject line and body.
The template is assigned with specific dynamic content, which can be used within the subject line
as well as in the body text.
The customisable e-mail notification templates are simple text files or HTML files in case you use an
HTML e-mail template having specific format rules. They can be placed on any web server. The only
prerequisite with regard to the web server folder, where the customisable e-mail notification templates are
placed, is that they must be accessible (using HTTP) by the Online application submission management
system.
The e-mail template files must generally be named as follows (whether simple text files or HTML files are
used): <email template name>_<language>.txt
The e-mail template names for the supported e-mail notification cases are listed in the table below. The
<language> place holder must be replaced by the ISO language code of the language you want to use in
the e-mail content.
The ISO language code, which is formed by using two lowercase letters, is defined by ISO-639.
The type for Multipurpose Internet Mail Extensions (MIME) of the e-mails is determined by the following
application property: eusd.common.emailNotification.mimeType
Examples of possible e-mail template file names are:
RegistrationConfirmation_de.txt for German e-mail notifications sent after successful
completion of the registration
MessageNotification_en.txt for English e-mail notifications informing about received
messages in the inbox
The contents of the e-mail template file must be stored using the UTF-8 character encoding. The online
application submission management treats the e-mail sections as follows:
First line of the e-mail template text file as the e-mail subject
Second and subsequent lines as the e-mail body
In addition, the customisable e-mail notification templates support dynamic content defined by using place
holders. The following self-explanatory place holders are available: {appellation}, {nameaffix}, {firstname},
{lastname}, {userID}, {password}, {url}, {applicationID}, {partialApplicationID},
{partialApplicationDescription} and {daysToDueDate}.
The following place holders are supported in certain context:
{ObjectType}
Type of the object considered for status change
{ObjectState}

Configuration Guide
Confidential
New state of the object considered for status change

{ObjectId}
ID of the object considered for status change
The place holder values are determined by the online application submission management solution at the
time of sending the e-mail notification.
The following table lists the customisable e-mail notification templates along with the supported place
holders for each template:
E-Mail Template Name Supported Place Description

holders
GenericStateChangeEMailTemplate {appellation} Sent to the respective parties (application

{nameaffix} enterer, contact person of the front office or
authority employee) when the application
{firstname}
changes to a specific status.
{lastname}
Configure the e-mail related status actions in
{ObjectType} the status action customizing and maintain the
{ObjectId} template.
{ObjectState}
{applicationID}
{partialApplicatio
nDescription}
{url}
<OBJECTTYPE>_<OBJECTOLDSTA {appellation} Customized e-mail template which can be
TUS>_<OBJECTNEWSTATUS> {nameaffix} sent to the respective parties. The format of
the template is for example:
{firstname}
APPLICATION_NEW_APPSUBMIT
{lastname}
This e-mail template is used to send an e-mail
{ObjectType} to the applicant when he or she submitted the
{ObjectId} application, if you defined the status
{ObjectState} Customizing.
{applicationID} Possible object type values:
{partialApplicatio APPLICATION, PARTIAL_APPLICATION,
nDescription} DOCUMENT
{url} Possible status values for APPLICATION:
NEW, SHARED, APPSUBMIT, UCHKSPC,
UAPP, OBS, CANCEL, COMP
Possible status values for
PARTIAL_APPLICATION:
NEW, FORCHKAUTH, UAPP, APP, REJ,
OBS, UCHKSPC, UCHKAUT, APPDEEMCLR
Possible Status values for DOCUMENT :

NEW, SPCCHKD, COMP, OBS, PROC,
UCHKSPC, UCHKAUT, AUTHCHKD

Configuration Guide
Confidential

holders
For more information about the description of

the values, see the table below.
You have to maintain the names of these

Customized templates (along with the
language code and extension for example
PARTIAL_APPLICATION_UAPP) in the
application properties. Otherwise it will not be
possible to use them.
The relevant application property for these
custom e-mail templates and status changes
is:
eusd.common.emailNotification.cust
omerTemplates
MessageNotification {url} Sent to the application enterer, front office
{applicationID} employees and/or authority employees to
inform them about new messages in their
respective message inboxes
PasswordGeneration {appellation} Sent to the user after the user's password is
{nameaffix} generated or changed by the (delegated) user
administrator
{firstname}
{lastname}
{password}
RegistrationConfirmation {appellation} Sent to the user after successfully completing
{nameaffix} the (self) registration process
{firstname}
{lastname}
{userID}
{password}
UserCreation {appellation} Sent to the user after the (delegated) user
{nameaffix} administrator created the user
{firstname}
{lastname}
{userID}
{password}
UserIDRequest {firstname} Sent to the user after retrieving the requested

Configuration Guide
Confidential

holders
{lastname} (forgotten) user ID
{userID}
UserLocking {appellation} Sent to the user when his or her user account
{nameaffix} is locked by the (delegated) user administrator
{firstname}
{lastname}
{userID}
UserUnlocking {appellation} Sent to the user when his or her user account
{nameaffix} is unlocked by the (delegated) user
administrator
{firstname}
{lastname}
{userID}
Table for status values to be used in the e-mail templates for status actions:
Object type Status code Status description
APPLICATION, NEW New

PARTIAL_APPLICATION,
DOCUMENT
APPLICATION SHARED Application shared
APPLICATION APPSUBMIT Application submitted
APPLICATION, UCHKSPC Under check by front office
DOCUMENT
APPLICATION, UAPP Under approval
PARTIAL_APPLICATION
APPLICATION, OBS Obsolete
DOCUMENT
APPLICATION CANCEL Cancelled
APPLICATION, DOCUMENT COMP Completed
PARTIAL_APPLICATION FORCHKAUTH For check by authority
PARTIAL_APPLICATION APP Approved
PARTIAL_APPLICATION REJ Rejected
PARTIAL_APPLICATION, UCHKAUT Under check by authority
DOCUMENT

Configuration Guide
Confidential
Object type Status code Status description
PARTIAL_APPLICATION APPDEEMCLR Approved trough deemed

clearance
DOCUMENT SPCCHKD Checked by front office
DOCUMENT PROC In process
DOCUMENT AUTHCHKD Checked by authority
The message notification e-mail template supports embedded links to the message inbox by
means of an {url} place holder.
For more informaiton about configuration steps required to maintain the value for the {url}
placeholder, see section
The e-mail notification template used for status update supports embedded links to the
application by means of the {url} place holder.
For more information about configuration steps required to maintain the value for the {url}
placeholder, see section Application Properties.
The following table summarises the application properties that must be properly configured for the
seamless usage of e-mail notifications in the online application submission management system:
ID pf Application Property Description Default Example

eusd.common.mail.from.syst E-mail ID used for sending e-mails donotreply@xyz.com
em across the system, in case all
application parties in the system will
receive e-mails from this e-mail upon
any change, for example a status
change, new message, user
creation.
eusd.common.emailNotificati To use the customised e-mail PARTIAL_APPLICAT
on.customerTemplates templates (along with the language ION_UAPP_APP
code and extension) used across the
application, their names have to be
maintained in this separate property
variable.
In addition to the application properties described above, the customisable e-mail notification functionality
depends on various other mail application property values. It is mandatory to maintain them. For more
information, see section Application Properties.

Configuration Guide
Confidential
4.3.2 Status Actions

It is possible to trigger a selection of pre-defined actions whenever an application, partial application or
document changes it status. This selection is done using a granular customizing which is described in the
next sections.
4.3.2.1 Defining Status Actions
In the status customizing you can set the status actions and the point in time when they are called. To
make the status settings, proceed as follows:
1. Navigate to the Customizing register.
2. Open the Status Customizing link. The Status Customizing screen appears.
3. Choose the Add button.
Figure 25: Status Customizing
4. A new line is added to the table. To make it visible, scroll down the table.
5. Select the Object (application, partial application or document) for which the action should be
valid upon status change.
6. Select the desired Action that should be invoked upon a specific status change.
7. Select the statuses for the status change:
o Select a From Status.
o Select a To Status.
8. Choose the Save pushbutton.

Configuration Guide
Confidential
9. Repeat steps 3-8 for further status actions.
4.3.2.2 Payment-Specific Status Actions

There is a specific requirement that an applicant should not be charged for a partial application, if it is
obsolete and has never reached an authority. This requirement is realized by a status action and can be
activated as follows:
1. Follow the instructions of the previous section, see Defining Status Actions.
2. Select Partial Application in the Object column.
3. Select Set Partial Application Charges To Zero in the Action column.
4. Select New in the From Status column.
5. Select Obsolete in the To Status column.
6. Choose the Save pushbutton.
Repeat the steps 2-6 with the same values, but select Under Check by contact person of the front office
as From Status value.
4.3.3 Message Customizing

For the message customizing, direct communication between the authority and the applicant is
dependent on the following parameter:
eusd.reg.customizing.isDirectCommunicationwithAuthorityAllowed
You can set the parameter to true or false:
o False
Direct communication is not permitted
o True
Direct communication is permitted
To maintain the parameter, proceed as follows:
2. Log on using your SAP NetWeaver Administrator user name and password.
4. In the Details section, choose the Applications tab page.
5. In the table, select the application cdev~acs~eusd~common~app.
6. In the Extended Details view, all application parameters specific to online application submission
management are displayed and can be maintained.
7. Maintain the parameter
eusd.reg.customizing.isDirectCommunicationwithAuthorityAllowed as required.
For Example:
eusd.reg.customizing.isDirectCommunicationwithAuthorityAllowed = false.
8. Save your settings.

Configuration Guide
Confidential
4.3.3.1 Restrictions while Customizing Message Types

The messages can be used for triggering status changes for the respective objects, so uttermost care
should be taken while configuring Message Types through Message Customizing.
No such messages should be configured which can sent back an object viz. Application, Partial
Application or Document to its previous state after attaining specific final state for a party.
Some of the status changes not allowed are :

A document cant be sent back to SPC(by the Authority) once it has been accepted by the
Authority i.e.the current status of the document is Checked by Authority.
A completed Application cant be reprocessed i.e. it status shouldnt be changed.
The status of an Approved Partial Application cant be changed.
A Completed Document cant be sent for reprocess or its status cant be changed to any other
value.
4.3.4 Application Properties

The application properties can be maintained as follows:
1. Go to SAP NetWeaver Administrator (http://<host>:<port>/nwa ).
3. In the Templates table select the template you are using on your system
Figure 28: Java System Properties
4. In the the Details area choose the Applications tab.

5. Use the filter to search for common~app.
6. Select cdev~acs~eusd~common~app.

Configuration Guide
Confidential
Figure 29: Application Properties
7. In the Extended Details area all available properties are displayed with their default properties on
the Properties tab page.
Figure 30: Application Property Value
8. To change a property value, select the table line for the property which has to be changed.
9. Choose the Modify pushbutton. A popup appears where you can enter the new value.
10. Choose the Set pushbutton to finish.

Configuration Guide
Confidential
Figure 31: Property Value
11. After setting all values, choose the Save pushbutton.
4.3.4.1 Common Properties

eusd.common.default_spc
Contains the readable text (=unique ID) of the front office department. In case a proper value is
provided, all new applications will be assigned to this department initially. Therefore, this
department can be addressed by applicants in case they have trouble in the first steps of the
application creation. This assignment will be deleted once another department is determined by the
process composition.
eusd.common.default_locale
Default locale should be maintained here, for example DE.
eusd.common.supported.languages
Supported languages should be maintained as comma separated values (for example DE, EN).
Ensure that this list also contains the default language for the solution. These languages will also
be available in the register maintenance in the description and help text section. This means that it
will be possible to maintain descriptions and help texts in only these languages.
Note: It has to be made sure that for all supported languages resource bundles (which contain the
UI texts among others) are available. If the resource bundles for a certain language are not
available, configuring the support of this language is a misconfiguration.
eusd.common.default_timezone
Default time zone should be maintained here, for example GMT.
eusd.common.uppercase_native_search
If this property is set to true, the system uses native SQL queries to enable case insensitive search.
eusd.query.max.results
All queries (for example the application searches for applicants, front-office or authority users,
register advanced searches) are normally restricted to a maximum number of results. This is done
in order to improve the performance of these searches. This application property contains the
default value for the maximum number of results. Use a negative value to select all results by
default.
eusd.common.forbidden.filetype
File types that should be restricted in upload should be maintained as comma separated values (for
example exe).
4.3.4.2 User Interface Properties

eusd.am.ui.roadmap.show_step_3

Configuration Guide
Confidential
This property influences the applicants application process. You can choose one of the following
values:
o HIDE means that step 3 of the road map, the selection of available documents, will never be
shown
o DEPENDENT means that step 3 of the road map, the selection of available documents, will
only be shown, if the application contains partial applications that have a predecessor/
successor relationship. Then this step is only displayed for those documents that are the
output of a partial application and a necessary input for another partial application
o ALWAYS means that step 3 of the road map, the selection of available documents, is always
shown. It displays all output documents of all partial applications.
eusd.principal.management.registration.closeWindowSupport
This property specifies the behaviour of the pushbutton to close the registration window. This
pushbutton enables the user to cancel the registration process for cases where the self-registration
runs in an own (separate) browser window.
Example Text: false

eusd.htmlforms.download.preview.directly
This property is relevant for the HTML forms functionality. It determines whether a click on Show
PDF in a form or message popup should result in a download of the PDF or in an inline display of
the PDF. You can chose the following values:
o True means that the PDF preview will be downloaded
o False means that the PDF preview will be shown in the popup
Example Text: true
4.3.4.3 Register Properties

eusd.reg.publicservicetype.spc
Readable text (=name) of front office service as public service type defined in the public service
register, for example FO for front office
eusd.reg.customizing.isDirectComunicationwithAuthorityAllowed
Determines, if direct communication of messages is allowed between an applicant and an authority.
Possible values are true and false.
eusd.locking.timeout.in.ms
When any register object is modified, a logical lock will be set to prevent that any depending object
is, for instance, deleted at the same time. This property is used to define the default timeout period
in milliseconds when acquiring a lock on register objects. This means that the system will try to
acquire a lock in the defined number of milliseconds, if it is already acquired by some other
process.
eusd.locking.set.global.register.lock.at.import
Set this flag to true, if all the registers should be locked for editing during a register import.

Configuration Guide
Confidential
We recommend setting it to true, to prevent data inconsistencies.

eusd.locking.set.global.register.lock.at.export
Set this flag to true, if all the registers should be locked for editing during a register export.
We recommend setting it to true, to prevent data inconsistencies.

eusd.register.import.log.stylesheetURL
Path to the location of the style-sheet that shall be used for rendering the import XML log file into a
text file. The format should be http://<server>:<port>/<public directory>. It should be
possible to access this link through http.
http://localhost:50000/public.
For more information, see SAP Note 1527542.

eusd.register.import.transport.file.schema
URL for the XSD schema file used for the transport file. The schema must correspond to the
following format: http://<server>:<port>/<path>/<filename>.
http://localhost:50000/public/oam_register_transport_schema.xsd.
For more information, see SAP Note 1527542.

eusd.reg.timedependent.query.speed.offset
Offset in milliseconds to allow a delay between the creation and subsequent read of time
dependent object. This is required because different databases use different levels of accuracy for
timestamp fields. In some environments, it might be the case that two depending time-dependent
objects are created subsequently in an import run (for example, a question and a rule that uses this
question in a condition). The second object does not find the corresponding depending object. The
value of this application property will be added to the read timestamp in the validation routines. It
has no affect on actual persisted timestamps.
4.3.4.4 Period Properties

eusd.period.includeweekend
Determines, if the period calculation includes weekends.
eusd.period.periodupdatemessage
Message notification upon period update that is the message which is sent when the period of a
partial application is changed manually. Here, the key from a message customizing entry needs to
be entered.
4.3.4.5 Document Management System (DMS) Properties:

eusd.common.dms.url

Configuration Guide
Confidential
URL for the DMS system in the following format:

http<s>://<DMS host>:<port>/
eusd.common.dms.repository_name
Repository structure (folder structure) in the DMS system to be used for storing application
documents.
eusd.common.dms.SSO.binding_port
Binding port to be used in the future in case of Single Sign-On seamless access to the backend
DMS.
You cannot use this value in the current application.

eusd.common.dms.techuser.binding_port
Binding port to be used, if a technical user, that is a user having administrative access to the
repository folder used for storing application documents, exists, to enable a seamless access to the
DMS.
4.3.4.6 User Management Engine (UME) Properties:
eusd.common.ume.invalidCharactersInUserPassword
This property specifies the invalid characters in the user password. User passwords in the online
application submission management system must not contain these characters. Already existing
user passwords are not affected, if the property value changes.
Example text: <>&

eusd.common.ume.validCharactersInUserID
This property specifies the allowed characters in user ID. User IDs in the online application
submission management system are only allowed to contain these characters that are defined by
this property at creation time. Already existing user IDs are not affected if the property value
changes.
Example text:
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_-+.@,
eusd.common.ume.userIDMaxLength
This property determines the supported maximum length of the user ID. Already existing user IDs
are not affected, if the property value changes.
eusd.common.ume.spmlService
This property stores the path to access the Service Provisioning Markup Language (SPML)
service. The path specified in this property is concatenated with the server URL specified in the
property eusd.common.dms.url to create and modify users in the DMS system.
Example text: spml/spmlservice

eusd.common.ume.dmsUser

Configuration Guide
Confidential
This property stores the user ID of the administrator user of the DMS system.
eusd.common.ume.dmsPassword
This property stores the password of the administrator user of the DMS system.
4.3.4.7 Properties of Domument Management System (DMS) and User Management

Engine(UME):
eusd.common.dms.url
This property stores the URL to access the system used for document storage in the Document
Management System (DMS).
It should be specified in the following format:
http<s>://<DMS host>:<port>/
eusd.common.dms.ume.userCreationEnabled
If the value is true, DMS users are created aligned with users of the online application submission
management, otherwise not.
eusd.common.dms.ume.userUpdateEnabled
If the value is true, DMS users are updated aligned with users the online application submission
management, otherwise not.
eusd.common.dms.ume.userGroupAssignmentEnabled
If the value is true, DMS users are assigned to specified user groups of the online application
submission management, otherwise not.
eusd.common.dms.ume.userAccountChangeEnabled
If the value is true, DMS user accounts are updated in case of password changes in the online
application submission management, otherwise not.
eusd.common.dms.ume.sendSystemAdministratorEmailNotification
If the value is true, an e-mail is sent to the DMS system administrator in case of issues.
eusd.common.dms.ume.systemAdministratorEmailAddress
This property specifies the e-mail address of the DMS system administrator who shall be informed
in case of issues during user creation or modification.
eusd.common.dms.ume.systemAdministratorEmailLanguage
This property specifies the language to be used to select the e-mail notification template of the
DMS system administrator.
Example text: en
4.3.4.8 Address Validation Properties:

eusd.common.address.validation.enabled
If this property is set to true, the address validation is executed on user creation or modification in
online application submission management. For more information about the implementation of
address validation, see section Address Validation Service.
eusd.common.address.validation.logicalPorts

Configuration Guide
Confidential
This property stores the logical port names (as comma separated list) configured for the address
validation consumer proxy. These port names are looped over in sequence to determine web
service proxies which are called to validate addresses.
Example text: AddressValidation_default, AddressValidationCustom
4.3.4.9 Payment Properties:

eusd.payment.currency
This property defines the currency. There is only one system wide currency. By default Euro
(EUR) is used.
eusd.payment.currency.symbol
This property defines the matching currency symbol for the system wide currency, for example .
4.3.4.10 E-Mail Notifications Properties:

eusd.common.emailNotification.templatesURL
This property stores the URL of the location where e-mail templates are stored.
Example text: http://<host>:<port>/email

eusd.common.emailNotification.customerTemplates
This property stores the template names of the custom e-mail notification templates (as comma
separated list).
eusd.common.emailNotification.mimeType
This property stores the MIME type of the e-mail notification template, for example text/plain,
text/html.
Example text: text/plain

eusd.common.emailNotification.enabled
If the value is true, e-mail notifications are generally enabled.
eusd.common.emailNotification.registration
If the value is true, a confirmation e-mail is sent after successful user registration. Otherwise, no e-
mail is sent.
eusd.common.emailNotification.userCreation
If the value is true, a confirmation e-mail is sent after successful user creation. Otherwise, no e-
mail is sent.
eusd.common.emailNotification.userLocking
If the value is true, a confirmation e-mail is sent after locking the user ID. Otherwise, no e-mail is
sent.
eusd.common.emailNotification.userUnlocking
If the value is true, a confirmation e-mail is sent after successful unlocking the user ID. Otherwise,
no e-mail is sent.

Configuration Guide
Confidential
eusd.common.emailNotification.newPassword
If the value is true, an e-mail containing a new password is sent to the user. Otherwise, no e-mail
is sent.
eusd.common.mail.smtp.host
This property specifies the SMTP mail host server name.
eusd.common.mail.smtp.user
This property specifies the SMTP mail user ID.
eusd.common.mail.smtp.password
This property specifies the password for the e-mail sender account used for sending e-mails.
eusd.common.mail.smtp.port
This property specifies the SMTP port.
Example text: 25
eusd.common.mail.from.system
E-mail ID used for sending e-mails across the system, that is all application parties in the system
will receive an e-mail from this e-mail address upon a change , for example a status change, new
message or user creation.
4.3.4.11 Application Link Properties for E-Mail Notifications:

The following properties are used in order to build the right application links that is for the message inbox
or for online application maintenance, which has to be used within the E-Mail notifications.
eusd.common.host.url
The URL of the server on which the Web Dynpro applications are deployed.
It should be specified in the following format: http<s>://<host>:<port>/
eusd.ui.link.isportalused
This property determines, if the portal has to be used to access the application or if the Web
Dynpro application has to be accessed via the direct link.
Possible values: true or false
eusd.ui.link.portal.isquicklink
If the application has to be accessed via the portal (eusd.ui.link.isportalused = true) either a portal
quick link can be used or the entire path to access the right portal page.
Possible values: true or false
The following properties define the access URLs for the Web Dynpro applications. The syntax to be used
depends on the settings for the application properties eusd.ui.link.isportalused and
eusd.ui.link.portal.isquicklink.
If the portal is not used (eusd.ui.link.isportalused = false) the direct link to the Web Dynpro
application has to be entered as follows:
Syntax:
sap.com/<DCName>/<ApplicationName>

Configuration Guide
Confidential
or (if URL Parameter are needed)
sap.com/<DCName>/<ApplicationName>?<parameter1>=<value1>&<parameter2>=<
value2>
Example:
sap.com/cdev~acs~eusd~ui~common~owl/OWLApp?objectType=MessageAE&searchA
reaMode=Disabled
If the portal is used (eusd.ui.link.isportalused = true) and the link is not a quick link
(eusd.ui.link.portal.isquicklink = false) the path to the portal page has to be entered as follows:
Syntax:
ROLES://portal_content/<Path to Portal Page>/<Page Name>
Example:
ROLES://portal_content/EU-
DLR_Refactoring/OAM_PORTAL_APPLICANT_INDIVIDUAL/EU-
DLR_Refactoring_WS/EU-DLR_Cockpit_WS/INBOX_AE
If the portal is used (eusd.ui.link.isportalused = true) and the link is a quick link
(eusd.ui.link.portal.isquicklink = true) just the quick link name has to be entered as follows:
Syntax: <Quicklink Name>
Example: InboxAE
eusd.ui.link.inboxae
This property defines the access URL of the message inbox UI of the application enterer.
eusd.ui.link.inboxfo
This property defines the access URL of the message inbox UI of the front office employee.
eusd.ui.link. inboxauth
This property defines the access URL of the message inbox UI of the authority employee.
eusd.ui.link.applicationae
This property defines the access URL of the online application UI of the application enterer.
eusd.ui.link. applicationfo
This property defines the access URL of the online application maintenance UI of the front office
employee.
eusd.ui.link. partialappauth
This property defines the access URL of the partial application maintenance UI of the authority
employee.

Configuration Guide
Confidential
4.3.5 Running a Notification Job

There is a special job that sends notification e-mails to authorities and/ or the front office for partial
applications.
Make the following settings:
Configure an administrative user who will start the job.
Maintain e-mail templates for the e-mail to the authority and front office.
Configure and run the job.
4.3.5.1 Configuring the Administrative User
Either create a new or use your existing administrative user of the J2EE engine. Supply this user with the
UME action OAMNotificationJobAction.
4.3.5.2 Maintain E-Mail Templates
Make the general e-mail template configuration as described in section Customizable E-Mail Notification
Templates.
Add one template for the authorities and one for the front office notification in the desired languages.
The following place holders are supported:
{firstname} {lastname}{daysToDueDate}{partialApplicationID} {url}.
The following is a sample template text (named FrontOfficeDueDateWarning_en.txt):

------
Period notification
Dear {firstname} {lastname},
The following partial application is due in {daysToDueDate} day(s):

{partialApplicationID} {url}
Kind regards,
Your System Administrator
------
4.3.5.3 Run the job

To run the job, proceed as follows:
1. Log on to the Java Scheduler of the J2EE. Choose SAP NetWeaver Administrator using the link
http://<HostName>:<Port>/nwa and then choose Operation Management Jobs Java
Scheduler.
2. Choose the Tasks tab.

Configuration Guide
Confidential
Figure 32: Tasks Tab
3. Choose the Add pushbutton.
Figure 33: Add Pushbutton
4. Select the Deadline Notification Job.

5. Choose Next.
Figure 34: Select the Job
6. The system displays a description. Choose Next.

Configuration Guide
Confidential
Figure 35: Job Description
7. Fill in the parameters of the job as follows:
o daysToDueDate
The number of dates until the partial application ends
o authoritiesMailTemplate
E-mail template used for authority due date warning
o frontOfficeMailTemplate
E-mail template used for Front Office due date warning
o partialApplicationStatusValues
A comma separated list of partial application statuses. Only partial applications with a
status included in this list will be considered.
Figure 36: Job Parameters
8. Select the execution time (Recurring, Cron or Simple)

9. Choose Add.
10. Choose Finish.
You configured the notification job.

Configuration Guide
Confidential
4.4 Additional Functionality

4.4.1 Employee Data Mapping for Forms and Messages
As of SP 5, the personal data and the communication data of employees (both SPC and authority) can
now be mapped to the corresponding forms or messages. Therefore, a list of constants for each field like
employee name and the communication data fields has been defined. These constants can be used in
the form field mapping maintenance in a similar fashion as is currently done for applicant data mapping.
In order to use the constants, they need to be defined as question of category Principal. Afterwards the
constants are available in the corresponding value help in the form register.
Employee Fields Question IDs for Employee Specific Data

employee id /ORGANISATION/EMPLOYEE/ID
employee firstname /ORGANISATION/EMPLOYEE/FIRSTNAME
employee last name /ORGANISATION/EMPLOYEE/LASTNAME
employee no. /ORGANISATION/EMPLOYEE/EMPLOYEE_NO
employee logon id /ORGANISATION/EMPLOYEE/LOGON_ID
employee institution id /ORGANISATION/EMPLOYEE/INSTITUTION
employee institution short text /ORGANISATION/EMPLOYEE/INSTITUTION_TEXT
employee department id /ORGANISATION/EMPLOYEE/DEPARTMENT
employee department short text /ORGANISATION/EMPLOYEE/DEPARTMENT_TEXT
employee communication dvdvid /ORGANISATION/COMMUNICATION/DVDVID

employee communication email /ORGANISATION/COMMUNICATION/EMAIL
employee communication language /ORGANISATION/COMMUNICATION/LANGUAGE
employee communication mode /ORGANISATION/COMMUNICATION/MODE
employee communication start hours /ORGANISATION/COMMUNICATION/START_HOURS
employee communication end hours /ORGANISATION/COMMUNICATION/END_HOURS
employee address care of name /ORGANISATION/ADDRESS/CAREOFNAME

employee address floor number /ORGANISATION/ADDRESS/FLOOR_NUMBER
employee address room /ORGANISATION/ADDRESS/ROOM
employee address street /ORGANISATION/ADDRESS/STREET
employee address house number /ORGANISATION/ADDRESS/HOUSE_NUMBER
employee address zipcode /ORGANISATION/ADDRESS/ZIPCODE
employee address county /ORGANISATION/ADDRESS/COUNTY
employee address city /ORGANISATION/ADDRESS/CITY
employee address country /ORGANISATION/ADDRESS/COUNTRY
employee address street number /ORGANISATION/ADDRESS/STREET_NUMBER
employee address additional info /ORGANISATION/ADDRESS/ADDITIONAL_INFO
employee address building /ORGANISATION/ADDRESS/BUILDING
employee address region code /ORGANISATION/ADDRESS/REGION_CODE
employee address region name /ORGANISATION/ADDRESS/REGION_NAME
employee fax country code /ORGANISATION/TELEPHONE/FAX/COUNTRY_CODE

employee fax country dial code /ORGANISATION/TELEPHONE/FAX/COUNTRY_DIAL_CODE
employee fax area code /ORGANISATION/TELEPHONE/FAX/AREA_CODE
employee fax subscriber code /ORGANISATION/TELEPHONE/FAX/SUBSCRIBER_CODE
employee fax extension /ORGANISATION/TELEPHONE/FAX/EXTENSION

Configuration Guide
Confidential

Employee fax type /ORGANISATION/TELEPHONE/FAX/TYPE
employee home landline country code /ORGANISATION/TELEPHONE/HOME_LANDLINE/COUNTRY_C

ODE
employee home landline country dial /ORGANISATION/TELEPHONE/HOME_LANDLINE/COUNTRY_DI
code AL_CODE
employee home landline area code /ORGANISATION/TELEPHONE/HOME_LANDLINE/AREA_CODE
employee home landline subscriber /ORGANISATION/TELEPHONE/HOME_LANDLINE/SUBSCRIBER
code _CODE
employee home landline extension /ORGANISATION/TELEPHONE/HOME_LANDLINE/EXTENSION
Employee home landline type /ORGANISATION/TELEPHONE/HOME_LANDLINE/TYPE
employee mobile country code /ORGANISATION/TELEPHONE/MOBILE/COUNTRY_CODE

employee mobile country dial code /ORGANISATION/TELEPHONE/MOBILE/COUNTRY_DIAL_CODE
employee mobile area code /ORGANISATION/TELEPHONE/MOBILE/AREA_CODE
employee mobile subscriber code /ORGANISATION/TELEPHONE/MOBILE/SUBSCRIBER_CODE
employee mobile extension /ORGANISATION/TELEPHONE/MOBILE/EXTENSION
Employee mobile type /ORGANISATION/TELEPHONE/MOBILE/TYPE
employee phone country code /ORGANISATION/TELEPHONE/PHONE/COUNTRY_CODE

employee phone country dial code /ORGANISATION/TELEPHONE/PHONE/COUNTRY_DIAL_CODE
employee phone area code /ORGANISATION/TELEPHONE/PHONE/AREA_CODE
employee phone subscriber code /ORGANISATION/TELEPHONE/PHONE/SUBSCRIBER_CODE
employee phone extension /ORGANISATION/TELEPHONE/PHONE/EXTENSION
employee phone type /ORGANISATION/TELEPHONE/PHONE/TYPE
employee office landline one country /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_ONE/COUN

code TRY_CODE
employee office landline one country /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_ONE/COUN
dial code TRY_DIAL_CODE
employee office landline one area code /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_ONE/AREA_
CODE
employee office landline one /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_ONE/SUBSC
subscriber code RIBER_CODE
employee office landline one extension /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_ONE/EXTEN
SION
employee office landline one type /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_ONE/TYPE
employee office landline two country /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_TWO/COUN

code TRY_CODE
employee office landline two country /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_TWO/COUN
dial code TRY_DIAL_CODE
employee office landline two area code /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_TWO/AREA_
CODE
employee office landline two subscriber /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_TWO/SUBS
code CRIBER_CODE

Configuration Guide
Confidential

employee office landline two extension /ORGANISATION/TELEPHONE/OFFICE_LANDLINE_TWO/EXTE
NSION
4.4.2 HTML Forms

With SP5 it is possible to use HTML forms instead of Interactive PDF Forms. This applies to forms to
be uploaded, e.g. by the applicant, as well as messages.
4.4.2.1 Maintaining Question Group
A new field Category is added to the question group object. The possible values for this type are:
Principal To be used when defining mandatory fields on the applicant data step (current
question group /SYSTEM/PERSON).
Questionnaire To be used for question groups that shall appear in the questionnaire (Step 2).
Form To be used for question groups that shall appear in the questionnaire of forms and
messages
The searches on the question group user interfaces have been enhanced so that it is possible to show
only objects of a particular type (category) and also belonging to a particular form id.

Configuration Guide
Confidential
The following screenshot shows how to select a category using a drop down while creating or modifying a
Question Group:
Figure 37: Question Group Category

If you are using the OASM 2.0 software also in a release prior to SP5, make sure to run the migration job
as described in note 1589441 because the data model has changed slightly.
4.4.2.2 Maintaining the Form
The register users can define on form level:
If the form is a classical Interactive Form, which means the Interactive Form UI Element will
appear so that the user has to fill the data directly into the PDFform or
If the form is an HTML form, which means that the user will see a HTML form like in the
questionnaire when filling the form.
The searches on the form user interfaces has been enhanced so that it is possible to
show only objects of a particular type(form type) and also containing certain question groups.
The below screenshot displays creating a Form of a specific Form Type :
Figure 38: Form Type

Configuration Guide
Confidential
The moment a new form of Form Type HTML Form is created a new tab Question Group Assignment
becomes visible in the Form Register view because it has to be defined which question groups shall be
shown for the HTML form.
The screenshot below displays the new tab added to the Form Register:
Figure 39: Question Group Assignment Tab
In order to add question groups to the HTML form, proceed as follows:

In the tab Question Group Assignment, use the Add button to add a new Question Group to the
form.
Select the Question Group using a Value Help, the value help will only provide the Question
Groups which are of category HTML Form.
Provide the sort index at which this question group has to be displayed in the form. One Question
Group can only be assigned to the Form once.

Configuration Guide
Confidential
The screenshot displays how to assign a new Question Group to an HTML Form:
Figure 40: Assigning Question Group to Form
4.4.2.3 Additional settings
Please refer to section 4.3.4.2 User Interface Properties in order to see how to configure application
property eusd.htmlforms.download.preview.directly.

Configuration Guide
Confidential
4.4.3 New Categories added for Questions

As part of SP5, the following two new question categories are added:
Hint:
The purpose is to dynamically show help texts in the questionnaire or in HTML forms.
When creating Questions of category Hint just provide the values as mentioned in below. Maintain the
Hint Text in the Description & Help Text section and this will then be displayed in the Questionaire or
Form Questionnaire.
The screenshot displays how to create a Question of type Hint:
Figure 41: Question of type Hint
Radio Button:
Radio-buttons can always be selected for questions having selection lists. In this case, all selection
values will be shown in one radio button group and the user can select exactly one of these values.
Questions of type radiobutton can be used in the questionnaire and in HTML forms.
When creating Questions of category Radio Button just provide the values as mentioned in the figure
below. The Selection List element gets enabled when the category Radio Button is selected so that the
required Selection list can be selected. In the length field provide the no which defines the no of values or
radio buttons to be displayed in a single row. If no value is defiend then all will be displayed in a single
row. The screenshot displays the process of creating a Question of type Radio Button:

Configuration Guide
Confidential
Figure 42: Question of type Radio Button
4.5 Register Master Data Maintenance for Online Application

Submission
The solution is designed in a manner that all required master data is maintained in sets of registers such
as the question register, document register, public service register, and so on.
You can maintain the master data manually or by using the import functionality in the registers. The
following sections provide more information about the registers.
4.5.1 Manual Register Master Data Maintenance

4.5.1.1 Question Register: Mandatory and Process Relevant Applicant Fields
In the online application submission management system all data fields of applicants can be configured to
be mandatory and/ or process relevant. This section describes how to do this under Register
Maintenance.
Independent of the configuration, the following fields are considered to be mandatory by default in the
system:
First Name (of individual applicant / applicant organisation employee)
Last Name (of individual applicant / applicant organisation employee)
E-Mail Address (of individual applicant / applicant organisation employee)
Language (of individual applicant / applicant organisation employee)

Configuration Guide
Confidential
Name (of applicant organisation)

You can set the other fields related to individual applicants and applicant organisations as mandatory, if
required. For example, you can set the phone number field as mandatory. As a result, the applicant can
only navigate to the next application process step, if he entered the phone number.
In addition to this, you can set fields as process relevant. The system uses data entered for process-
relevant fields to correctly compose an application during the process composition.
The customizing for mandatory and/ or process relevant fields is made in the question registers. All
affected fields are maintained as corresponding questions, also called application parameters, with
determined IDs. Application parameters set as process relevant are used to calculate the application
elements.
Furthermore, you must maintain the questions about the applicant fields associated with the special
question group: /SYSTEM/PRINCIPAL
The group does not exist by default. You must create the special group by specifying the following
attribute details:
Name: /SYSTEM/PRINCIPAL
Sort Index: -1
Category: Principal
The question group /SYSTEM/PRINCIPAL is not displayed in the questionnaire.

The following table show the mapping between applicant fields and the question IDs maintained in
question register. In the question maintenance dialog, the question origin type is Principal in all cases.
You can choose Single line text with length 1 as category and length information. You can choose any
sort index unless it is unique. There are no further restrictions for the other values. However, they are
mandatory in the question dialog (see the example below).
Applicant Field Question IDs for Individual Applicants

person appellation /APPLICANT/INDIVIDUAL/APPELLATION
person name affix /APPLICANT/INDIVIDUAL/NAMEAFFIX
person first name /APPLICANT/INDIVIDUAL/FIRSTNAME
person last name /APPLICANT/INDIVIDUAL/LASTNAME
person language /APPLICANT/INDIVIDUAL/EMAIL
person phone /APPLICANT/INDIVIDUAL/LANGUAGE
person mobile /APPLICANT/INDIVIDUAL/TELEPHONE
person email /APPLICANT/INDIVIDUAL/MOBILE
person fax /APPLICANT/INDIVIDUAL/FAX
person street /APPLICANT/INDIVIDUAL/STREET
person house number /APPLICANT/INDIVIDUAL/HOUSENUMBER
person zip code /APPLICANT/INDIVIDUAL/ZIPCODE
person city /APPLICANT/INDIVIDUAL/CITY
person country /APPLICANT/INDIVIDUAL/COUNTRY

Configuration Guide
Confidential
Applicant Field Question IDs for Applicant Organisation

employee appellation /APPLICANT/ORGANISATION/EMPLOYEE/APPELLATION
employee name affix /APPLICANT/ORGANISATION/EMPLOYEE/NAMEAFFIX
employee first name /APPLICANT/ORGANISATION/EMPLOYEE/FIRSTNAME
employee last name /APPLICANT/ORGANISATION/EMPLOYEE/LASTNAME
employee language /APPLICANT/ORGANISATION/EMPLOYEE/EMAIL
employee phone /APPLICANT/ORGANISATION/EMPLOYEE/LANGUAGE
employee mobile /APPLICANT/ORGANISATION/EMPLOYEE/TELEPHONE
employee email /APPLICANT/ORGANISATION/EMPLOYEE/MOBILE
employee fax /APPLICANT/ORGANISATION/EMPLOYEE/FAX
employee organisation unit /APPLICANT/ORGANISATION/EMPLOYEE/ORGANISATIONUNIT
employee department /APPLICANT/ORGANISATION/EMPLOYEE/DEPARTMENT
employee position /APPLICANT/ORGANISATION/EMPLOYEE/POSITION
organisation name /APPLICANT/ORGANISATION/NAME
organisation name 2 /APPLICANT/ORGANISATION/NAME2
organisation email /APPLICANT/ORGANISATION/EMAIL
organisation street /APPLICANT/ORGANISATION/STREET
organisation house number /APPLICANT/ORGANISATION/HOUSENUMBER
organisation zip code /APPLICANT/ORGANISATION/ZIPCODE
organisation city /APPLICANT/ORGANISATION/CITY
organisation country /APPLICANT/ORGANISATION/COUNTRY
main contact appellation /APPLICANT/ORGANISATION/MAINCONTACT/APPELLATION
main contact name affix /APPLICANT/ORGANISATION/MAINCONTACT/NAMEAFFIX
main contact first name /APPLICANT/ORGANISATION/MAINCONTACT/FIRSTNAME
main contact last name /APPLICANT/ORGANISATION/MAINCONTACT/LASTNAME
main contact email /APPLICANT/ORGANISATION/MAINCONTACT/EMAIL
main contact language /APPLICANT/ORGANISATION/MAINCONTACT/LANGUAGE
main contact phone /APPLICANT/ORGANISATION/MAINCONTACT/TELEPHONE
main contact mobile /APPLICANT/ORGANISATION/MAINCONTACT/MOBILE
main contact fax /APPLICANT/ORGANISATION/MAINCONTACT/FAX
main contact organisation /APPLICANT/ORGANISATION/MAINCONTACT/ORGANISATIONUNIT
unit
main contact department /APPLICANT/ORGANISATION/MAINCONTACT/DEPARTMENT
main contact position /APPLICANT/ORGANISATION/MAINCONTACT/POSITION
The following is an example of how you can categorise the Country field of the applicant individual as
mandatory:
1. Create a new question group /SYSTEM/PRINCIPAL, if it does not already exist.
2. Create a new question for the above question group.
3. Enter the question ID /APPLICANT/INDIVIDUAL/COUNTRY into the question field.
4. Specify the origin as Principal.
5. Provide a sort index.
6. Provide any category and length information.
7. Select the Mandatory checkbox.

Configuration Guide
Confidential
8. Enter the validity.

9. Choose Save.
Figure 43: Example: Maintenance of a Mandatory Field for the Applicant
The settings described above, result in Country as a mandatory field. The application enterer must enter
the country of the applicant before proceeding.
4.5.1.2 Mandatory Public Service Type for Front Office

To define the public service type for the front office, proceed as follows:
1. Maintain a value for the application property eusd.reg.publicservicetype.spc. The values
are restricted to the set of allowed values for readable texts (=unique IDs) in registers, for
example FO.
2. Now maintain a public service type in the public service register with the same readable text
(=unique IDs) as maintained for the value in the application property.
In the definition of subject-matter competencies, this public service type must be used for front office
responsibilities.

Configuration Guide
Confidential
4.5.2 Register Dependencies

Read and follow the instructions of SAP Note 1527542. It contains a list of all register dependencies, for
example which object can only be deleted if children objects are deleted.
4.5.3 Register Master Data Transport

4.5.3.1 General
SAP Note 1527542 contains the latest information with regard to register data transport. The following
chapter provides additional information.
4.5.3.2 File Format
The file format for the transport of register data is based on the following XML criteria:
The transport file has to be encoded in UTF-8 with Byte Order Mark (BOM). Files that do not fulfil
this requirement cannot be imported.
The root element to be used is TransportFile. It will contain a list of TransportObjects. Each
TransportObject contains the operation (create, update or delete operations) and it wraps any
register object a question.
Figure 38 Example 1 for Transport File shows a sample transport file:

Configuration Guide
Confidential
Example Transport File

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<TransportFile version="v100">
<TransportObjects>
<TransportObject operation="CREATE" objectChangedAt="2010-07- 15T09:46:22.283+02:00">
<Namespace>
<namespaceID>ANY_NAMESPACE</namespaceID>
<description>standard namespace</description>
<defaultFlag>true</defaultFlag>
<lockingID>0</lockingID>
<deleted>false</deleted>
</Namespace>
</TransportObject>
<TransportObject operation="CREATE" objectChangedAt="2010-07-15T09:46:24.377+02:00">
<DocumentType>
<readableText>ATTACHMENT_01</readableText>
<signature>NO</signature>
<type>ATTACHMENT</type>
</DocumentType>
</TransportObject>
<TransportObject operation="CREATE" objectChangedAt="2010-07-15T09:46:30.737+02:00">
<EntityCategory>
<readableText>EC_ANY</readableText>
<dependent>false</dependent>
</EntityCategory>
</TransportObject>
</TransportObjects>
</TransportFile>
Figure 44: Example 1 for Transport File
The complete schema is available as an attachment of SAP Note 1527542.

If you want to import the register data, compress the XML file into a ZIP file.
For importing rules, there are two options:

o Generic rule type
o Concrete rule types (for example QuestionRule)
It is recommended to use the concrete rule types as they contain the corresponding fields
for the particular type.
4.5.3.3 Import
4.5.3.3.1 General
The import interface can only accept a ZIP file containing only the XML transport file. If the ZIP file
contains more than one entry, the import will fail.
The import interface processes the objects imported from top to bottom. For example if any object such
as a question group occurs before a question in the transport file, the question group will be imported
before the question.

Configuration Guide
Confidential
Importing an object does not only mean to create it. It is also possible to update an existing object and to
delete an object. This is controlled by the operation attribute of type TransportObject. As a consequence,
consider the following aspects with regard to the order of the TransportObjects:
For objects that depend on each other (question depends on the question group, entity depends
on entity category etc.) it is important that the parent object already exists when the dependent
object is created. If a question group and a question are created, the question group needs to be
listed before the question in the transport file.
If an object that has children should be deleted, the transport file needs to list the deletion of all
child objects first. If an entity category having three child entities (World, Europe, Germany)
should be deleted, the transport file needs the delete commands in the following order: Entities
Germany, Europe, World and only then the entity category can be listed.
There is no definite order for the sequence of creation first, then deletion or updates.
For more information, see SAP Note 1527542, which contains a list of all dependencies.
Generally, each import has a unique name, which is provided by the user and which is used in order to
refer to it in the web services (for example for reading the status).
4.5.3.3.2 Web Service
The following web service can be used to import files:
Interface
TransportInService
Name
Service Name TransportInService
Namespace http://sap.com/cdev/acs/eusd/bl/srv/reg/transport/beans/
WSDL http://<host>:<port>/TransportInService/TransportInService?wsdl
This web service provides the following relevant operations:

uploadImportFile
can be used to upload a new import file
startImport
can be used to trigger a simulation or import
checkImportCompleted
can be used to check if the import is completed
downloadImportLog
can be used to download the log once the import is completed. For more information about the
available log renderers, see section Creating Log Renderers.
4.5.3.3.3 User Interface
For more information about the transport user interface, see Register Management and Customizing
4.5.3.4 Export
4.5.3.4.1 General
In order to export register data, it is required to create a register group. A register group bundles a set of
exports. Generally, different groups can be used to transport from one system to multiple other systems at
different points in time, since always other delta exports will be required. In a productive environment,
only one group might exist in the register maintenance system.

Configuration Guide
Confidential
The advantage of export groups is to export different delta exports. For example a register data
maintenance system can have two export groups. One group can be used to export the data into a test
system and one for exporting the data into the production system.
Whenever a new export is triggered in a group, all data changes are exported that were done after the
time of the last export that was marked as successfully imported.
In general, each export has a unique name, which needs to be provided by the user. This name is used
for instance to reference an export in a web service call.
4.5.3.4.2 Web Service
The following web service can be used to import files:
Interface
TransportInService
Name
Service Name TransportInService
Namespace http://sap.com/cdev/acs/eusd/bl/srv/reg/transport/beans/
WSDL http://<host>:<port>/TransportInService/TransportInService?wsdl
This web service provides the following relevant operations:

createExportGroup Creates a new Export Group
startNextExport Starts the next Export in the corresponding Group.
checkExportCreationCompleted Checks if the Export is complete
downloadExportFile Downloads a completed ExportFile
setExportSuccessfullyImported - Marks an Export as Successfully Imported into the Target
System.
4.5.3.4.3 User Interface
For more information about the transport user interface, see Register Management and Customizing.
4.5.3.5 Creating Log Renderers
The system provides the following two types of log files:
XML Log File (grouped by severity, errors first), renderer name = XmlBySeverityErrorFirst
Text Log File (grouped by severity, errors first), renderer name = TextBySeverityErrorFirst
You can create a concrete log file by using a so-called log file renderer. There is at the moment one
renderer for the XML and one for the Text Log File.
To create a new log renderer, proceed as follows:
1. Create a session bean.
2. The bean needs to implement the local interface
com.sap.cdev.acs.eusd.interfaces.reg.transport.log.ImportLogRendererInL
ocal
3. Implement the Render method.
4. Register the bean by using or enhancing a post enhancement for the available log file renderer
directory. For more information, see section Transport.
The log renderer will then be part of the drop down box of the import user interface as shown below.
Alternatively, it can also be used in the log file web service by providing the key as chosen in your
enhancement.
Configuration Guide
Confidential
Figure 45: Import Log Renderer
4.5.4 Register Post Checks

It is possible to carry out post checks in the register maintenance after importing register data. Using this
functionality, you can create own checks, for example you can check, if all question groups contain valid
questions or if all public service types have correct charges.
To create a custom register check, proceed as follows:
1. Create a session bean.
2. The bean needs to implement the local interface
com.sap.cdev.acs.eusd.interfaces.reg.checks.RegisterCheckInLocal
3. Implement the Check method.
We recommended implementing only one check per bean.

4. Register the bean by using or enhancing a post enhancement for the register check directory. For
more information, see Register Checks).
All registered checks will be executed at the end of each register import. This also applies for the
simulation of an import. In addition, there is a user interface available, which can be used to trigger these
checks. The URL to access this user interface is
http://<host>:<port>/webdynpro/dispatcher/sap.com/cdev~acs~eusd~ui~reg~admin/
RegisterCheckApp
http://localhost:50000/webdynpro/dispatcher/sap.com/cdev~acs~eusd~ui~reg~admi
n/RegisterCheckApp.
In order to setup the required roles for executing these checks, see section SAP User Management
Engine (UME).
Configuration Guide
Confidential
4.6 Security
In order to prevent the user from seeing any stack traces or dumps on the user interface, all logging and
tracing has to be disabled in the production environment. Otherwise, the user might see technical details
that he or she is not supposed to see such as code lines, SQL queries etc.
To switch off the logging, proceed as follows:
1. Open the SAP NetWeaver Administrator using the link http://<HostName>:<Port>/nwa.
2. Choose Problem Management Logs and Traces Log Viewer.
3. Choose Related Links Log Configuration.
4. Open the following nodes :
a. Root Category
b. Applications
c. OAM
5. Select the line OAM.
6. Select Error in the the Severity column.
7. Choose Copy To Sub-Tree.
8. Choose the Save Configuration pushbutton.
Figure 46: Logging Categories
For more information about general security, see SAP Help Portal at http://help.sap.com SAP
NetWeaver SAP NetWeaver CE SAP NetWeaver Composition Environment 7.1 Including
Enhancement Package 1 Knowledge Center Security Guide.
Configuration Guide
Confidential
4.7 User Interface

There are several Web Dynpro applications available for the three main application areas principal (user)
management, register management and application management. This chapter describes the purpose of
each of these applications and how they can be accessed.
Each application can be accessed either via a direct Web Dynpro link or via the SAP Enterprise Portal.
4.7.1 Web Dynpro Applications

Build each direct link for the Web Dynpro application as follows:
Web Dynpro Application URL:
http(s)://<host>:<port>/webdynpro/dispatcher/sap.com/<Development Component
Name>/<Application Name>
http://<host>:<port>/webdynpro/dispatcher/sap.com/cdev~acs~eusd~ui~principalmgmt/SelfRegistration
If URL parameters are needed, add them to the URL as follows:

<Web Dynpro Application URL>?<parameter1>=<value1>&<parameter2>=<value2>&
http://<host>:<port>/webdynpro/dispatcher/sap.com/cdev~acs~eusd~ui~am~root/PartialApplicationDetail
s?partialApplicationID=10026
4.7.1.1 Common Web Dynpro Applications

Within the online application submission management application several objects can be displayed and
maintained using a common UI pattern.
The so called Object Worklist (OWL) is the entry point for this maintenance and provides search, filter,
and export functionalities. From here you can start to create new objects and display, delete or change
existing objects.
The object itself is maintained within the so called Object Instance Floorplan (OIF). This application is only
used from OWL UIs, if the user wants to maintain or create an object.
For the OWL and OIF UIs the following two Web Dynpro applications where created:
Object Worklist OWL:
Development Component Name: cdev~acs~eusd~ui~common~owl
Application Name: OWLApp
Parameter:
objectType (mandatory)
This parameter is used to identify the object, for which the OWL should be shown.
Possible values for the Register Management & Customizing Area are:
o QuestionGroup (Question Group Register Object)

o Question (Question Register Object)
o SelectionList (Selection Register Object)
Configuration Guide
Confidential
o Namespace (Namespace Register Object)

o DocumentType (Document Type Register Object)
o Form (Form Register Object)
o EntityCategory (Entity Category Register Object)
o PublicServiceType (Public Service Type Register Object)
o Export (Export UI)
o Import (Import UI)
o Institution (Institution Register Object)
o SMC (Subject Matter Competence Register Object)
o PeriodRules (Period Rules Register Object)
o RuleTemplates (Rule Templates Register Object)
o ApprovalRules (Public Service Determination Rules Register Object)
o Admin (Register User Administration UI)
o Extensibility (Extension Point Customizing)
o MessageCustomizing (Message Customizing UI)
Possible values for the Principal Management Area are:
o OrgUserManagement (Maintenance of existing or new user of an Applicant Organisation)
o InstitutionUserManagement (Maintenance of the system user for maintained Employees
within the Institution Register)
Possible values for the Application Management Area are:
o MessageAE (Message Inbox for Application Enterer)
o MessageFO (Message Inbox for Front Office Employee)
o MessageAuthority (Message Inbox for Authority Employee)
o ApplicationOverviewForApplicant (Application Overview for Application Enterer My
Applications)
o ApplicationOverviewForFrontOffice (Application Overview for Front Office Employee
My Work)
o ApplicationOverviewForAuthority(Partial Application Overview for Authority Employee
My Work)
searchAreaMode
This parameter is used to hide the advanced search area to the user. In this case this parameter
has to be used with the value Disabled.
dontDisplayQueryVariants
This parameter is used to hide the drop down box with the saved query variants to the user. In
this case this parameter has to be used with the value X.
Authentication needed: Yes
Object Instance Floorplan (OIF):
As this application is only used from OWL UIs, if the user wants to maintain or create an object, do not
call it as a direct link.
Development Component Name: cdev~acs~eusd~ui~common~oif
Application Name: OIFApp
Parameter:
Several parameters depending on the object which has to be shown and on the UI from which the OIF is
called. These parameters are handled automatically by the caller. As this application should not be called
as direct link, no more details will be described here.
Configuration Guide
Confidential
4.7.1.2 Principal Management
Self-Registration:
With this application a new applicant can register a new user.
Development Component Name: cdev~acs~eusd~ui~principalmgmt
Application Name: SelfRegistration
Parameter: None
Authentication needed: No
Organisational Data Maintenance

With this application an applicant organisation user can maintain the organisation data.
Application Name: OrgDataMaintenance
Parameter: None
User Profile Maintenance

With this application an applicant can maintain his user profile data.
Application Name: ProfileMaintenance
Parameter: None
Password Reset
With this application an applicant can reset the password when he forgot his password.
Application Name: PasswordReset
Parameter: None
User ID Request
With this application an applicant can request the user ID when he forgot his use ID.
Application Name: UserIDRequest
Parameter: None
Organisation User Maintenance

With this application an applicant organisation user can maintain additional users within the organisation.
Configuration Guide
Confidential
This is an Object Worklist UI with the OrgUserManagement object type.
Institution User Administration

With this application an institution employee can maintain users for all employees within the same
institution or department (this depends on the user permissions).
This is an Object Worklist UI with the InstitutionUserManagement object type.
4.7.1.3 Register Management and Customizing

Within the register management for each register object the OWL UI is used. See chapter Common Web
Dynpro Applications.
Status Customizing:
Within this application the status actions and status changes can be maintained.
Development Component Name: cdev~acs~eusd~ui~customization
Application Name: StatusCustomizing
Parameter: None
4.7.1.4 Application Management

Online Application Simulation
Within this application the application creation can be simulated without a registered user.
Development Component Name: sap.com/cdev~acs~eusd~ui~am~root
Application Name: OnlineApplicationSimulation
Parameter:
simulation=X
This parameter has to be used, if the application creation should be started in simulation mode
Application Enterer
Online Application (Creation and Display)

Within this application a registered user can create, maintain and display his applications. In addition, this
application can run in simulation mode.
This application is also used by the front office employee for simulation or for creation of an application for
a certain applicant. The front office employee can also use it, if the applicant shares an application which
makes it visible to him without submitting the application.
Application Name: OnlineApplicationAE
Parameter:
applicationID=<Application ID>
This parameter needs to be used to display an already created application
simulation=X
Configuration Guide
Confidential
This parameter can be used if application creation should be started in simulation mode
applicantKey=<GUID of Applicant>
This parameter is only used internally if Front Office Employee creates an application for a certain
applicant
Inbox
Within this application all received and sent messages are displayed.
This is an Object Worklist UI with the MessageAE object Type.
The advanced search area should be disabled (searchAreaMode=Disabled).
My Applications
Within this application all created applications are shown.
This is an Object Worklist UI with the ApplicationOverviewForApplican object type.
The advanced search area should be disabled (searchAreaMode=Disabled).
The search queries should be hidden (dontDisplayQueryVariants=X).
Front Office Employee:
Create Application for Applicant:

Within this application the front office employee can select an applicant user for which he wants to create
a new application.
Application Name: ApplicantSelectorFO
Parameter: None
Online Application Maintenance

Within this application the front office employee can maintain an application and forward it to the
authorities.
Development Component Name Name: sap.com/cdev~acs~eusd~ui~am~root
Application Name: OnlineApplicationDetailsFO
Parameter:
applicationID=<Application ID>
Inbox
This is an Object Worklist UI with the MessageFO object type.
Configuration Guide
Confidential
My Work
This application shows all applications, the front office employee has to work on.
This is an Object Worklist UI with the ApplicationOverviewForFrontOffice object type.
Authority Employee:
Partial Application Maintenance

Within this application the front office employee can check a partial application, create notices and
approve or reject the partial application.
Application Name: PartialApplicationDetails
Parameter:
partialApplicationID=<Partial Application ID>
Inbox
This is an Object Worklist UI with the MessageAuthority object type.
My Work
This application shows all partial applications, an authority employee has to work on.
This is an Object Worklist UI with the ApplicationOverviewForAuthority object type.
4.7.2 SAP Portal Configuration

Using the SAP Enterprise Portal is optional. All Web Dynpro Applications can run in the SAP Enterprise
Portal. If you want to use the portal you have to create portal roles, worksets and iViews. Use the Web
Dynpro applications mentioned above for the iViews.
To ensure that the navigation between the Web Dynpro applications is realised within the SAP Portal and
the navigation targets are the own created iViews, a navigation configuration needs to be done:
1. Go to SAP NetWeaver Administrator using the link http://<HostName>:<Port>/nwa.
2. Choose Configuration Management Infrastructure Application Modules.
3. Within the Module List filter for ui~common.
4. Select webdynpro/resources/sap.com/cdev~acs~eusd~ui~common.
Configuration Guide
Confidential
Figure 47: Module List
5. Within the Web Module Details area choose the on the Web Dynpro Properties tab.
6. Select the following entry:
Components/com.sap.cdev.acs.eusd.ui.common.navigationcomp.NavigationCom
pNavigation
Figure 48: Web Module Details
7. Within the Full Details area you get a list of properties which must be maintained for using the
online application submission management application in the SAP Enterprise Portal.
Figure 49: Property Details
Configuration Guide
Confidential
Navigation Properties:
a. OpenObjectDetailsExternal
This property determines, if the object details that is the Object Instance Floorplan (OIF)
application is always opened in a complete new window or inplace. For more information
about the OIF application, see Common Web Dynpro Applications.
Values: true or false
b. ObjectDetails
Portal link to the OIF application
c. UserRegistration
Portal link to the self-registration application
d. UserIDRequest
Portal link to the Request User ID application
e. PasswordReset
Portal link to Password Reset application
f. ApplicationCreationAE
Portal link to the Online Application Creation application for the applicant
g. ApplicationCreationFO
Portal link to the Online Application Creation application for the front office employee
h. OnlineApplicationMaintenanceFO
Portal link to the Application Maintenance application for the front office employee
i. OnlinePartialApplicationMaintenanceAuth
Portal link to the Partial Application Maintenance application for the authority employee
j. ApplicationOverviewAE
Portal link to the Application Overview application for the application enterer (displayed as My
Applications)
k. ApplicationOverviewFO
Portal link to the Application Overview application for the front office employee (displayed as
My Work)
l. PartialApplicationOverviewAuth
Portal link to the Partial Application Overview application for the authority employee
(displayed as My Work)
m. InboxAE
Portal link to the Inbox application for the application enterer
n. InboxFO
Portal link to the Inbox application for the front office employee
o. InboxAuth
Portal link to the Inbox application for the authority employee
Configuration Guide
Confidential
Example for a portal link:

ROLES://portal_content/EU-DLR_Refactoring/OAM_PORTAL_FRONT_OFFICE_EMPLOYEE/EU-
DLR_Refactoring_WS/EU-DLR_Cockpit_WS/Online_Application_Maintenance
The following figure shows the navigtion between the many Web Dynpro applications. The number
bubbles match the numbers of the navigation properties.
Figure 50: Overview of Web Dynpro Applications

Configuration Guide OASM 2 0 SP6

Uploaded by

Document Information

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

Configuration Guide OASM 2 0 SP6

Uploaded by

Copyright:

Available Formats

SAP Custom Development

Version Status Date

1.4 Final July 09, 2012

Typographic Conventions Icons

Type Style Description Icon Meaning

2012 SAP AG Title: Online Application Submission Management Page 2 of 111

2 Getting Started .............................................................................................. 7

2012 SAP AG Title: Online Application Submission Management Page 3 of 111

4.4 Additional Functionality ..................................................................................................... 86

2012 SAP AG Title: Online Application Submission Management Page 4 of 111

Team SAP AG Author

30/11/2010 Release 2.0 All

1.2 Intended Group of Readers

2012 SAP AG Title: Online Application Submission Management Page 5 of 111

2012 SAP AG Title: Online Application Submission Management Page 6 of 111

2.2 Important Notes

List of Related SAP Notes

SAP Note Title Description

1527526 Online Application Installation Note for Online Application Submission

2012 SAP AG Title: Online Application Submission Management Page 7 of 111

2012 SAP AG Title: Online Application Submission Management Page 8 of 111

Web User Interface

SAP NetWeaver Composition

SAP NetWeaver Portal 7.0

Figure 1: System Landscape

2012 SAP AG Title: Online Application Submission Management Page 9 of 111

3.2 Software Component Matrix

Scenario/Business Software Components Implementation and Configuration

Register Data SAP NetWeaver Register Data Maintenance

Adobe Document Adobe Document Services

You can connect a different portal system to

3.3 Implementation General Description

Software to Be Installed and the Related Configuration

1 Install Java Software Development Kit (JSDK) version 1.5_x

2012 SAP AG Title: Online Application Submission Management Page 10 of 111

Software to Be Installed and the Related Configuration

6 Configure your portal software.

After performing the installation steps, configure the business processes.

2012 SAP AG Title: Online Application Submission Management Page 11 of 111

4.1.1 User Types

2012 SAP AG Title: Online Application Submission Management Page 12 of 111

4.1.1.1 Applicant Individuals

2012 SAP AG Title: Online Application Submission Management Page 13 of 111

2012 SAP AG Title: Online Application Submission Management Page 14 of 111

This does not include administrator and import/export privileges.

2012 SAP AG Title: Online Application Submission Management Page 15 of 111

2012 SAP AG Title: Online Application Submission Management Page 16 of 111

2012 SAP AG Title: Online Application Submission Management Page 17 of 111

The role OAM_APPLICANT_ORGANISATION_EMPLOYEE is implicitly assigned to users by the

2012 SAP AG Title: Online Application Submission Management Page 18 of 111

2012 SAP AG Title: Online Application Submission Management Page 19 of 111

2012 SAP AG Title: Online Application Submission Management Page 20 of 111

2012 SAP AG Title: Online Application Submission Management Page 21 of 111

2012 SAP AG Title: Online Application Submission Management Page 22 of 111

2012 SAP AG Title: Online Application Submission Management Page 23 of 111

2012 SAP AG Title: Online Application Submission Management Page 24 of 111

2012 SAP AG Title: Online Application Submission Management Page 25 of 111

2012 SAP AG Title: Online Application Submission Management Page 26 of 111

2012 SAP AG Title: Online Application Submission Management Page 27 of 111

2012 SAP AG Title: Online Application Submission Management Page 28 of 111

2012 SAP AG Title: Online Application Submission Management Page 29 of 111

The functionality to import vCards must be provided by a custom implementation.

2012 SAP AG Title: Online Application Submission Management Page 30 of 111

2012 SAP AG Title: Online Application Submission Management Page 31 of 111