Nw70ehp2 en 48

Download as pdf or txt
Download as pdf or txt
You are on page 1of 4

User-specific Changes

PDF download from SAP Help Portal:


http://help.sap.com/saphelp_nw70ehp2/helpdata/en/48/3a061a902131c3e10000000a42189d/frameset.htm
Created on September 20, 2016

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 4

Table of content
1 User-specific Changes
1.1 Example

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 4

1 User-specific Changes
To change the layout and the logon process according to your special requirements, you can make user-specific changes in addition to the settings that are
possible on the configuration screen.

Process
Create a new class that is a subclass of CL_ICF_SYSTEM_LOGIN.
You change the layout of the logon screen by overwriting the htm_login method in the new class.
To modify the screen for the password change, overwrite the htm_change_passwd method.

Note
To ensure that the entries made are forwarded to the relevant screens and to trigger the corresponding events for the transfer of the results, it is
necessary for you to use default constants and attributes for form names, input field names, event names and script functions. The constants and
attributes that should be used depend on the logon functionality to be implemented.

Constants
Below is a list of all constants used by the system, which are necessary for changes to the process and layout of logging on and changing passwords:
Logon
Constant

Description

CO_SAP_USER

Name and ID of the input field for the user name

CO_SAP_PASSWORD

Name and ID of the input field for the password

CO_SAP_CLIENT

Name and ID of the input field for the client

CO_SAP_LANGUAGE

Name and ID of the input field for the language

CO_FORM_LOGIN

Form name

CO_JS_SUBMIT_LOGIN

Name of the JavaScript function to be called when a pushbutton is pressed on the


logon screen

CO_EVENT_LOGIN

Event to be triggered when the logon pushbutton is pressed

CO_EVENT_CHANGE_PASSWORD

Event to be triggered when the Change password pushbutton is pressed

CO_EVENT_BASIC_AUTHENTICATION

Event to be triggered when the Basic Authentication pushbutton is pressed

M_SAP_APPLICATION

Value of the action form attribute

Password change
Constant

Description

CO_PASSWORD

Name and ID of the input field for the current password

CO_PASSWORD_NEW

Name and ID of the input field for the new password

CO_PASSWORD_REPEAT

Name and ID of the input field for repeating the new password

CO_FORM_CHANGE_PASSWORD

Form name

CO_JS_SUBMIT_CHANGE_PASSWORD

Name of the JavaScript function to be called when a pushbutton is pressed on the


change password screen

CO_EVENT_DO_CHANGE_PASSWORD

Event to be triggered when the Change pushbutton is pressed

CO_EVENT_CANCEL_PASSWORD

Event to be triggered when the Cancel pushbutton is pressed

CO_EVENT_CONTINUE_PASSWORD

Event to be triggered when the Continue pushbutton is pressed after successfully


changing the password

M_SAP_APPLICATION

Value of the action form attribute

You can use the following classes as a reference to implementation additional functions:
CL_ICF_BASIC_LOGIN
CL_ICF_IDES_LOGIN
CL_ICF_NW04_LOGIN

Example
You can find a sample implementation in the system in the CL_ICF_EXAMPLE01_LOGIN class and in the following simple example.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 4

Example
This example shows which attributes you have to change and which methods you have to overwrite in order to implement your own logon screen that should
have the following elements:
User names
Password
Logon pushbutton

Prerequisites
Your class is a subclass of CL_ICF_SYSTEM_LOGIN.

Attributes
You need the following attributes in your class for your changes:
Attributes
Attribute

Description

CO_FORM_LOGIN

Form name

M_SAP_APPLICATION

Value of the action form attribute

CO_SAP_USER

Name and ID of the input field for the user name

CO_SAP_PASSWORD

Name and ID of the input field for the password

CO_JS_SUBMIT_LOGIN

Name of the JavaScript function to be called when a pushbutton is pressed on the


logon screen

CO_EVENT_LOGIN

Event to be triggered when the logon pushbutton is pressed

Methods
In addition to the attributes, you need the htm_login method, which you overwrite in your class.
The interface of the htm_login method is used to transfer the JavaScript functions that are necessary and provided by the system and a series of form field
value pairs of type HIDDEN, which are required to control the logon. The JavaScript functions are transferred as a string in the iv_javascript parameter;
the form fields are transferred in the iv_hidden_fields parameter
The HTTP body that is necessary for the HTTP response is summarized in the htm_login method and returned as a string to the caller.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 4

You might also like