Beruflich Dokumente
Kultur Dokumente
Copyright
Copyright 2013 SAP AG. All rights reserved.
SAP Library document classification: PUBLIC
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies (SAP Group) for
informational purposes only, without representation or warranty of any kind, and SAP Group
shall not be liable for errors or omissions with respect to the materials. The only warranties for
SAP Group products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.
Meaning
Caution
Example
Note
Recommendation
Syntax
Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help General Information Classes and
Information Classes for Business Information Warehouse on the first page of any version of SAP Library.
Typographic Conventions
Type Style
Description
Example text
Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT
Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of 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 text>
Variable user entry. Angle brackets indicate that you replace these words and
characters with appropriate entries to make entries in the system.
EXAMPLE TEXT
Contents
1
1.1.1
Prerequisites ............................................................................................................................. 6
1.1.2
1.1.3
Constraints ................................................................................................................................ 6
1.2
1.3
Glossary ............................................................................................................................................. 7
1.4
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
Configuration ..........................................................................................................................................11
2.1
2.1.1
2.2
2.3
2.3.1
Procedure: Activate.................................................................................................................20
2.3.2
Procedure:Test ........................................................................................................................20
2.3.3
Result ......................................................................................................................................21
3.2
3.3
3.4
3.5
3.5.1
3.6
3.6.1
4
Procedure ................................................................................................................................11
5 Get URL to Access SAP Screen Personas from the Installed System ......................................................37
SAP Screen Personas Configuration Guide Addendum
1/2015
6.1
6.1
6.2
Troubleshooting ......................................................................................................................................43
7.1
Notes .......................................................................................................................................................57
Prerequisites
SAP Kernel with release 721 or release 740 or higher installation basis
Install the latest version of Silverlight version 5.0 UI technology (browser plug-in) from
Microsoft in the client machines to render rich internet content.
Please see SAP Screen Personas Configuration Guide (https://websmp106.sapag.de/instguides) for a full list of pre-requisites.
1.1.2
Deliver screen modifications in a fast and cost-effective way, without any programming
Align user interfaces to business user needs and personal work styles
Reduce screen clutter for business users, allowing them to access only the data they need to
transact business
Add extra information to screens through labels, tooltips, and sticky notes
Add images, web content, or shortcut buttons that start transactions from the screen
1.1.3 Constraints
This component supports solutions using SAP GUI screens and no other screens.
Consultants
Partners
Customers
System Administrators
Support Specialists
1.3
Glossary
Term
SAP application
Business
Scenario
Component
Flavor
User
Admin User
Definition
An SAP software solution that serves a specific business area, for example, ERP,
CRM, PLM, SRM, SCM
From a microeconomic perspective, a business scenario is a cycle that consists of
several interconnected logical processes in time. Typically, a business scenario
includes several company departments and involves other business partners.
From a technical point of view, a business scenario needs at least one SAP
application (SAP ERP, SAP SCM, or others) for each cycle and possibly other
third-party systems.
A business scenario is a unit that can be implemented separately and reflects the
customers prospective course of business.
The smallest individual unit considered within the Solution Development
Lifecycle.
Components are separately produced, delivered, installed and maintained.
Flavor in SAP Screen Personas identifies a specific personalization for a particular
SAP transaction. So a Personas Flavor is always linked to a specific SAP transaction
(example VA01). On the other hand, one particular SAP transaction can have
infinite number of flavors.
Business user who uses any SAP transaction with Personas personalization.
A user who does and supports configuration and other system activities to
support business users.
http://service.sap.com/instguides
Focused Business Solutions
SAP Screen Personas
SAP Screen Personas 2.0
http://help.sap.com/personas
http://service.sap.com/
http://service.sap.com/quicksizer
http://service.sap.com/platforms
To access the Platform Availability Matrix directly, enter
http://service.sap.com/pam
http://service.sap.com/securityguide
http://scn.sap.com/docs/DOC-7848
http://service.sap.com/performance
http://service.sap.com/sp-stacks
http://scn.sap.com/community/internationalization-andunicode
1.4.1
Further Useful Links
The following table lists further useful links on SAP Service Marketplace:
Content
Information about creating error messages
SAP Notes search
SAP Software Distribution Center (software
download and ordering of software)
SAP Online Knowledge Products (OKPs) rolespecific Learning Maps
1.4.2
This Master Guide is based on Master Guides for cross-industry applications. You can find more
information about the relevant applications in the following documents:
Title
Master Guide - SAP ERP 6.0
SAP NetWeaver
Location
http://service.sap.com/instguides
SAP Business Suite Applications
SAP ERP
SAP ERP 6.0
Planning
http://service.sap.com/instguides
SAP NetWeaver
SAP NetWeaver 7.4
Planning
Latest Notes that are released can be found on this SCN Blog:
http://scn.sap.com/community/gui/blog/2013/08/28/sap-screen-personas--how-to-configure-thesystem-troubleshooting-faq
1848339
1885334
1869640
Title
Installation Note for SAP
Screen Personas 2.0
Description
The note contains information about planning the
installation of upgrades of the ABAP add on PERSOS.
https://service.sap.com/sap/support/notes/1776739
Installation and Upgrade note This note contains information on the steps for
for SAP Screen Personas
installing and getting started for both new and
(Silverlight)
existing customers.
https://service.sap.com/sap/support/notes/1848339
Feature List for Silverlight
Feature list for SAP Screen Personas Release 2.0
Silverlight
https://service.sap.com/sap/support/notes/1885334
Client copy of Personas
After Personas installation, all the SAP delivered
delivered customizing
customizing is present in client 000.
https://service.sap.com/sap/support/notes/1869640
1.4.4
The following documentation will allow you to obtain the most value from your investment in
SAP Screen Personas.
Name
Configuration
Document
2.0_SP2
Location
https://websmp106.sa
p-ag.de/instguides
Audience
SAP basis
team
https://websmp106.sa
p-ag.de/instguides
SAP Screen
Personas Users
Guide
Purpose
This document provides configuration
information for the Silverlight and HTML
components of SAP Screen Personas 2.0 and
includes additional information of the
Support Pack SP02.
It also describes all activities necessary for
the implementation and configuration of
SAP Screen Personas.
This Master Guide is the central starting
point for the technical implementation of
the SAP Screen Personas solution. You can
find cross-scenario implementation
information as well as scenario-specific
information in this guide.
The user guide is a central starting point for
Personas. The documenting is regularly
updated with new information.
SAP Screen
Personas
Optimization
Guide
http://scn.sap.com/doc
s/DOC-54574
Under: Technical
Documentation
SAP Screen
Personas
Configuration
Guide
Addendum
http://scn.sap.com/doc
s/DOC-54574
Under: Technical
Documentation
SAP Screen
Personas
administrators
, enterprise
application
team
Enterprise
application
team, key
users, screen
designers,
business
analysts
Enterprise
application
team, key
users, screen
designers,
application
developers
Enterprise
application
team, key
users, screen
designers,
application
developers
Master Guide
2.0_SP02
http://scn.sap.com/doc
s/DOC-54574
Under: Technical
Documentation
1.4.5
Useful Links
Name
Purpose
Location
http://help.sap.com/saphelp_persona
s200_silverlight/helpdata/en/33/30f
15101d9445ee10000000a423f68/fra
meset.htm
http://scn.sap.com/docs/DOC-54574
http://www.sap.com/bin/sapcom/e
n_us/downloadasset.2014-04-apr29-17.sap-screen-personas-mythsversus-truth-about-usability-andthe-user-experiencepdf.bypassReg.html
http://experience.sap.com/fioriguidelines/#FioriDesign
2 Configuration
Once the SAP Screen Personas is installed, the following procedures need to be competed in order to
be able perform the administration tasks.
Please make sure you have all the need pre-requisites including the SAP Kernel 7.21.
Procedure
Transaction: RZ10
1. Create the clientaccesspolicy.xml and crossdomain.xml
2. Locate key icm/HTTP/file_access_<n> in your system profile.
Ex: http://nvpal774.pal.sap.corp:8074/clientaccesspolicy.xml
<access-policy>
<cross-domain-access>
<policy>
<allow-from http-methods="*" http-request-headers="*">
<domain uri="http://*"/>
<domain uri="https://*"/>
</allow-from>
<!--<allow-from http-methods="*">
<domain uri="http://*"/>
<domain uri="https://*"/>
</allow-from>-->
crossdomain.xml
</access-policy>
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<site-control permitted-cross-domain-policies="all"/>
<allow-access-from domain="*" secure="false"/>
<allow-http-request-headers-from domain="*" headers="*"
secure="false"/>
</cross-domain-policy>
Results:
If the service is not available, configure restgui service by following the steps given below:
.
The service data dialog is displayed. Once you have the restgui service in place do the
following:
1. Change Compression to Yes.
Modify parameters.
1. Add or set parameter ~XSRFCHECK with value 0. (This is optional but makes potential
debugging easy).
2. Add or set parameter ~WEBGUI with value 1.
3. Remove all other parameters.
4.
5.
6.
7.
Procedure: Activate
As the initial page to launch SAP Screen Personas in a BSP, the following services need to be
activated in the SICF transaction:
Transaction: SICF
/sap/persos_app
/sap/bc/bsp/persos/mainapp
/sap/bc/bsp/sap/system
/sap/bc/bsp/sap/public/bc
/sap/public/bsp/sap/public/bc
/sap/public/bsp/sap/system
/sap/public/bsp/sap/htmlb
/sap/public/bc
/sap/public/bc/ur
/sap/restgui
/sap/bc/gui/sap/its/webgui (this should be already active, make sure it is
/sap/bc/bsp/persos/mainapp (this should be already active, make sure it is)
Please follow the steps given below to activate each service:
2.3.2
Procedure:Test
Result
3 SPRO Transaction
You can access SAP Screen Personas SPRO Transaction under Cross Applications Component:
The following are all the configuration steps that need to be completed in the SPRO Transaction.
Rendering, visual editing and sharing of flavors (Bits 0-5, and 8-13)(16191)
oUser is able to create private flavors and edit them
In addition, Admin can come up with new roles. The steps for this are mentioned in the IMG
configuration help. The following table lists down the different User Permissions per bit position.
Permission Bit Name
AccessToProfileFlavors
Permission
Bit Number
0
Permission
Bit Mask
0x1
AccessToSharedFlavors
0x2
AllowEdit
0x4
AllowGroup
0x8
AllowMove
0x10
AllowResize
0x20
AllowHide
0x40
AllowMandatory
0x80
AllowBackgroundImages
0x100
AllowRecolor
0x200
AllowCreatePostItNote
10
0x400
AllowCreateImage
11
0x800
AllowCreateGroupBox
12
0x1000
AllowCreateLabel
13
0x2000
AllowCreateLauchButton
14
0x4000
AllowCreateScriptButton
15
0x8000
AllowCreateHtmlControl
16
0x10000
Description
Allows switching
between flavors
that are part of the
profile
Allows searching for
flavors and adding
them to the profile,
as well as setting a
default
Allows user to enter
edit mode and copy
flavors
Allows user to
group controls and
change Z-Index
Requires
AccessToSharedFlavors
17
0x20000
AllowConvertInput
18
0x40000
AllowConditionalFormatting
19
0x80000
AllowEditComboBoxes
20
0x100000
AllowEditLabels
21
0x200000
AllowAdvancedScripting
22
0x400000
AllowCreateCheckBox
23
0x800000
AllowEditButtons
24
0x1000000
ShowBasicView
25
0x2000000
HTML controls
Allows creating text
box controls
Allows converting
inputs
Allows setting
conditional
formatting
Allows editing
combo boxes
Allows editing label
controls
Allows using
WebRFC and
JavaScript actions
as part of the Script
Button
Allows creating
Check Boxes
Allows changing
labels and icons of
buttons
Show basic view for
user.
AllowResize
Requires AllowMove &
AllowResize
Requires
AllowCreateScriptButton
Roles can be created using transaction PFCG and then assigned to the user. It has to be ensured
that the authorization object /PERS/AOBJ is attached to the role and maintained. This
authorization object uses three parameters described below.
Parameter Description
Transaction Code: This limits/filters activities to a specific transaction. Wild cards are allowed, for
example * to indicate all transactions. You can specify multiple transaction codes separated by a
comma.
Flavor ID: This limits an activity to one flavor, or a pattern of flavor identifiers. Multiple flavor
patterns are separated using comma.
Note
It is mandatory to grant authorization rights to the static flavor ID SAP_PERSONAS.
Activity: The activity for which a specific authorization check is done.
There are seven activities that are allowed for a role. These activities have an increasing level of
privilege. Given below is a table consisting of different roles.
Note
It is mandatory to assign all lower privilege level activities also to the role.
Role
USE
Privilege
1
Activity
16/Execute
SWITCH
03/Display
RESHARE
78/Assign
THEMING
EDIT
4
5
A3/Change Status
02/Change
SHARE
59/Distribute
ADMIN
70/Administrate
Description
The user is allowed to see and use the
specific flavor.
The user is allowed to switch between a set
of available flavors.
If the user has a number of predefined
flavors (shared with this user). Then the
user can re-share his flavors with other
users.
The user is allowed to update the theme.
The user is allowed to create and maintain
flavors.
The user is allowed to share own flavors with
other users.
The user is allowed to administer flavors.
Note
In addition to the role, ensure that while accessing the SAP GUI for HTML, the URL parameter
sapie=edge is included in the URL. Without this parameter, the solution will not be enabled on
the UI even if the necessary authorizations are provided.
For example:...webgui?sap-ie=edge&
SAP Screen Personas can be installed in a central system (termed as Main system) and be connected
to be used with other systems (Target systems). Both the Main and theTarget Systems need SAP
Kernel 7.21 or higher and the System settings mentioned in Section 2.
In the SPRO Node, maintain the system Details like System ID, Client, Description, Connector to
SAPSystem. The Value for Connector to SAP System is always ITS. Once the user enters all values and
clickon enter, a GUID is generated in the System Config ID which will be used as the unique ID for any
SystemClient configuration.
Value (Example)
System (ID)
CNS
Client
800
Group
Test System
Description
Once the System Details are maintained, select the row and double click on the System Settings on
theleft side navigation. This takes you to the Parameter Maintenance screen for each system.
Maintain the following parameters under System settings:
Service.Uri Please maintain the service name for accessing SAP Screen Personas here. The
defaultservice is /restgui.
Server.Url Please maintain the server link for the system here. For example:
https://ldfss600.pal.ess.corp:50015
Property Value
Service.Uri
/restgui
Server.Url
http(s)://target_system_host:Port
Sap.Language (optional)
EN
Note: Ensure you are using Server.Url and Service.Uri (pay attention to server vs. service and Url
vs. Uri).
3.6.1
RFC Destination
Transaction: SM59
Maintain the RFC Destination in the HTTP Connection to ABAP System
Make sure the Logon with User is: SAP RFC Logon or SAP Standard
Language: Preferred Language
Client: Should be the same as the one mentioned in SPRO> Maintain Systems
User: UserID of the target system to authenticate the connection
PW Status: Password of the target system to authenticate the connection
If you dont have the role you can use transaction PFCG to create it. See Section 3.6.1
Here is an example of how the /PERSOS/ADMIN_UI transaction is assigned to a higher role:
Get URL to Access SAP Screen Personas from the Installed System
SAP Screen Personas can be accessed from the users PC using a shortcut URL. This URL can be generated
by following the below steps:
1. Goto transaction SICF.
2. Select the following filters and press execute.
a. Hierarchy Type - SERVICE
ob. Service Path - /sap/bc/bsp/persos/mainapp/
3.Select"mainapp" service, right click and click on test service.
4. A GUI Security dialog pops up. Select "Allow this one time" and click ok.
5.You would be taken to the personas application in the default browser window.
This URL can be used as a shortcut to access Personas.
Appendix
restgui
: Service for communicating with ITS
/persos_app : Service for communicating with ABAP Storage
Classes
BSP Applications
/PERSOS/MAIN_APP : The main BSP application that hosts the Silver Light island
Programs
Transactions
In this example you would use Screen ID Overwrite in the SPRO transaction.
Why do we need Control Id Overwrite Rules?
For certain transactions, the Control Ids gets changed dynamically when you do something in that
Screen.
E.g. For ME21N, check the dropdown. Go into Edit mode, and copy its control ID from the Properties
window.
Go into Edit mode, and copy its control ID from the Properties window.
Expand/Collapse the Header Panel and then go back into edit mode and check the control id
You will notice that there is difference between the Control IDs BEFORE and AFTER
ses[0]/wnd[0]/usrUSRAREA/subcntSUB0SAPLMEGUI0016/subcntSUB3SAPLMEVIEWS1100/subc
ntSUB2SAPLMEVIEWS1200/subcntSUB1SAPLMEGUI1301/subcntSUB1SAPLMEGUI6000/cmbDYN
_6000LIST
ses[0]/wnd[0]/usrUSRAREA/subcntSUB0SAPLMEGUI0013/subcntSUB3SAPLMEVIEWS1100/subc
ntSUB2SAPLMEVIEWS1200/subcntSUB1SAPLMEGUI1301/subcntSUB1SAPLMEGUI6000/cmbDYN
_6000LIST
First line is before and 2nd line is after. You will see that the control Ids have changed.
So for Personas to have a consistent Control ID, we overwrite in this scenario which you would use the
/persos/ADMIN_UI transaction
Flavor Maintenance
Transport Objects
User Management
Profile Wide Settings
Group Management
Translation
Tools
User Maintenance
Mass User Maintenance
Control Specific Profile Settings
Type Specific Profile Settings
Global Text Replacement
Group Maintenance
Mass Group Maintenance
Prepare for Translation
Cleanup Redundant Translation
Export Flavors
Import Flavors
Configuration Check
Troubleshooting
I do not see any Personas Roles OR Screen Id Overwrite entries OR Controld ID Overwrite
entries?
SAP Screen Personas is shipped with some pre-configured values which can be found in client 000 of
your system. Follow the Implementation and Configuration Guide or note 1869640 to get these values
from client 000 to client XXX of your system.
Which kernel patch level shall I be on?
If your kernel patch is very old (120 or below), then you should upgrade your kernel patch first before
reporting any issue for unusual Personas behavior.
SAP Screen Personas Configuration Guide Addendum
7/2014
At this point, start clicking the all the tabs. For any tab, if the Screen Number changes, then we need
screen id overwrite entry for that particular transaction. For any transaction, if you are not able to figure
out the overwrite entries, please create an OSS message.
Where do I find the latest notes which are being released?
Usual support channel is the preferred way.
Silverlight is stuck on Cross Domain Setup, where do we put files clientaccesspolicy.xml
and crossdomian.xml Silverlight application for SAP web services?
OS
Parameter Value
Windows
PREFIX=/sap/public/icmandir/,DOCROOT=$(DIR_ICMAN_ROOT),ARCHIVE=$(DIR_EX
ECUTABLE)\ITS.SAR,CACHECTRL=+28800
Linux,AIX etc.
PREFIX=/sap/public/icmandir/,DOCROOT=$(DIR_ICMAN_ROOT),ARCHIVE=$(DIR_EX
ECUTABLE)/ITS.SAR,CACHECTRL=+28800
2. Locate the parameter icm/HTTP/file_access_1 in your system profile. If not found, create one and
change the parameter value as mentioned below.
OS
Parameter Value
PREFIX=/clientaccesspolicy.xml,DOCROOT=$(DIR_ICMAN_ROOT)\clientaccesspolicy.
xml,CACHECTRL=0
PREFIX=/clientaccesspolicy.xml,DOCROOT=$(DIR_ICMAN_ROOT)/clientaccesspolicy.
xml,CACHECTRL=0
3. Locate the parameter icm/HTTP/file_access_2 in your system profile. If not found, create one and
change the parameter value as mentioned below.
OS
Windows
Parameter Value
PREFIX=/crossdomain.xml,DOCROOT=$(DIR_ICMAN_ROOT)\crossdomain.xml,CACHECTRL=0
Linux,AIX
etc.
PREFIX=/crossdomain.xml,DOCROOT=$(DIR_ICMAN_ROOT)/crossdomain.xml,CACHECTRL=0
service makes sure that restgui is configured correctly if it has 200 then it was configured correctly
2nd call makes sure that the url is on the whitelist and is configured correctly if it has 200 then it was
configured correctly this is only done once
3rd call is the rest gui call also seemed successful (200) this call returns and renders the screen definition
If you dont see the screen definition you want to explore more the 3rd call
Double click on that call
SAP Screen Personas Configuration Guide Addendum
7/2014
Value
~RESTGUI
~XSRFCHECK
~WEBGUI
While checking the restgui service , and trying to Setup URL Handler facing a pop up
below
Make sure when you are creating the restgui (See Section 2.2: Setup URL Hander) that you are
either Specify a new package or choosing the Local Object button.
The service path name in the SPRO transaction needs to equal the service name in the SICF
transaction.
Restgui service is saved into /persos/mainapp package with SAP as owner. So it is not letting you delete
it. It should have been saved into own package or as local object as specified in Section 2.2
/persos/mainapp package will be restricted package because it will contain Personas code. You can try
the following options:
Option 1 (make package modifiable)
Go to SE06 -> System change options -> in the System Components list, scroll down to Personas
and set it to Modifiable
Come back to SICF, delete restgui service and rename restgui1 to restgui
Reset package back to unmodifiable to avoid misuse of package in future.
Go to SPRO -> Cross-Application Components -> SAP Screen Personas -> Maintain Systems
Select the target system and double click on System Settings
8 Configuration Checklist
The latest patch of personas allows you to view a Config Checklist
Transaction
Check that you have Personas System setup correctly
/n/persos/admin_ui
Transaction
/n/persos/admin_ui
Transaction RZ10
Transaction SICF
Transaction
SE80
Make sure the following files exist under the Main App
ScreenMode.js,
- Silverlight.js,
- SilverlightBrowserIntegration.js
- Utilities.js
Transaction SPRO
Transaction SPRO
Transaction SPRO
Menu >System
>Status
For the selected system, check that the parameter Service.Uri exists with
correct spelling and case. The value for this parameter should be maintained
as /restui.
For the selected system, check that the parameter Server.Url exists with
correct spelling and case. The value for this parameter should be maintained
in the following format.
http://<hostname>:<port> or https://<hostname>:<port>
(Some customers, face problems with https:// In such case, try using http://)
Check Basis Version, Kernel Version and Kernel Patch
- Click looking glass under the Component Version
Transaction SICF
If you get a different response, check whether your service is activated and
whether you have the right authorizations.
Example:
Also restgui settings (the following example URL assumes you have configured
restgui service at /sap/restgui):
Put following URL into your browser:
https://DOMAINNAME:PORT/sap/restgui/state/text
Control Tree
--> [_][E][R][_] : CONTROL_TREE
--> [_][E][R][A] ses[0] : SESSION
--> [V][E][R][A] ses[0]/wnd[0] : SAP Easy Access :
PRIMARY_WINDOW
.
If you get different response, check whether your service is activated
Sectio
n 3.7
Transaction SICF
Transaction SICF
Transaction SICF
Sectio
n 2.3
Sectio
n
2.2.1.1
Sectio
n
2.2.1.1
Transaction SICF
Transaction SICF
Sectio
n
2.2.1.1
Transaction SU01
/PERSOS/ADMIN_UI
> General Actions >
Maintain Control ID
Overwrite Logic
/PERSOS/ADMIN_UI
Sectio
n 3.5
Sectio
n
4.1
Personas Role.
9 Notes
Kernel Notes
You have implemented the below mentioned important kernel notes
a. 1787341 - Personas:ABAP Interface Restgui
b. 1885506 - Personas:Turn off Control (amodal) based F4 help
c. 1913055 - ABAP interface does not work correctly inside RFC calls (Only applicable for kernel patch 200
onwards)
ITS sizing
You have considered sizing your ITS memory based on note 1888428 and number of expected users.
(For a start, it is recommended to put value of em/global_area_MB as 2048 MB)
To find the current value, go to transaction RZ11 and display the parameter em/global_area_MB.
Contact your system admin if you dont have authorizations to increase this parameter.
ITS Configuration Notes
892442
885580
755726
742048