How to Configure SAP FIORI Launchpad Automatic Sign-Out

 

How to Configure SAP FIORI Launchpad Automatic Sign-Out:

The SAP FIORI users access the system via a web browser. For security reasons, it's important to set a limited session lifetime for the browser. However, this can be frustrating for end users, as they may encounter a server error when attempting to interact with the system after a long period of inactivity. This error is often difficult to understand and resolve.

This blog will explain how to configure a more user-friendly session timeout and warning for SAP FIORI pages.

The following questions will be addressed:

1. How can I set a session timeout for my FIORI tiles?
2. How can I configure a warning to notify end users that their FIORI session is about to expire?
3. Is it possible to limit the number of concurrent FIORI sessions?

Time-Out Settings for SAP FIORI.

To configure session timeout settings for Fiori, follow these steps:

1. Open the SAP GUI and enter transaction code /UI2/FLP_SYS_CONF.

In the system configuration screen, set the values for the following two parameters:

      2.    SESSION_TIMEOUT_INTERVAL_IN_MINUTES: This parameter defines the total session lifetime (in minutes). Once this time is reached, the session will automatically expire.

      3. SESSION_TIMEOUT_REMINDER_IN_MINUTES: This parameter defines how far in advance (in minutes) a warning will be shown to users before their session expires.

Set these values according to your company’s needs. Once you've decided on the appropriate times, press Save to apply the changes.

Note: This parameter will be available from SAP_UI 754.

Time-out warning for End User:

The result for the end user is a more user-friendly warning, giving them the option to either continue or log out.

Limiting amount of sessions:

Limiting the number of browser and SAP FIORI sessions per user is not possible. SNOTE:3248472

SAP tp import options and unconditional modes

SAP tp import options and unconditional modes.

Unconditional Modes (umode)

These modes are intended for special cases where you want to bypass certain rules of the Transport Organizer and Transport Management System. An unconditional mode is represented by a digit between 0 and 9. To use an unconditional mode when you call the tp program, enter a 'U' in the command line followed by the required digits.

Reference from help.sap.com

Domain activation Upgrade or transport stops in phase ACTUPG

Domain activation: Upgrade or transport stops in phase ACTUPG

During the SUM tool execution phase, the shadow system upgrade or transport (importing Support Packages or EHP Installer) stops due to activation errors. A domain cannot be activated because it contains duplicate fixed values, resulting in the following error message:

DO197 "Fixed value / lower limit & reoccurs"

The relevant fixed value was maintained in a domain append in the customer system. However, this fixed value is now provided by SAP.

As with all appends in the Data Dictionary, domain appends are the unmodified option for changes in the customer system.

Appends are therefore not handled during the comparison. This issue very rarely occurs during an upgrade since there are no customer namespaces or techniques for obscuring duplicate values for domain appends (unlike other objects).

Solution:

Call transaction SE11 and branch to the maintenance screen of the relevant domain. On the tab page for fixed values, adjust or delete the customer append that contains the new value provided by SAP.

Education purpose Reference: 1467826

 

SWU3 workflow jobs not scheduled in S/4HANA system - yellow lightning symbol on the workflow system job nodes

 

SWU3 workflow jobs not scheduled in S/4HANA system - yellow lightning symbol on the workflow system job nodes

In an S/4 HANA system when executing transaction SWU3 users get a yellow lightning symbol and can't activate the Workflow jobs.

Workflow jobs are not scheduled automatically from SJOBREPO

In case of upgrade from an older release to S/4 Hana OnPremise 1709 or higher and make sure that user SAP_WFRT exists in the system and has role SAP_BC_BMT_WFM_SERV_USER_PLV01 assigned.

Create a user DDIC or SAP_SYSTEM and give it SAP_ALL authorization (SAP S/4HANA 1709) As per SAP Note 2731999.

If the jobs "R_JR_BTCJOBS_GENERATOR" have status "Released/Susp." in SM37. TRy to reschedule

Wait for the next run of system job "R_JR_BTCJOBS_GENERATOR" for the Technical Job Repository. It is scheduled automatically by the Job Repository and it runs by default every hour and schedules all new workflow system jobs starting with SAP_WORKFLOW. After the workflow jobs are scheduled, user will see green lights in transaction SWU3. If R_JR_BTCJOBS_GENERATOR is not scheduled.

Thanks to read a blog!!!

SUM fails in PREP_INPUT/ASCS_CHK: No ASCS instance detected

SAP SUM Tool Error : SUM fails in PREP_INPUT/ASCS_CHK: No ASCS instance detected

No ASCS instance detected at SUM instance list

During the SAP S/4HANA or  ECC Upgrade/migration using SUM Tool.

SUM does not recognize ASCS/ERS instance:

SUM log shows below error

ASCS_CHK.LOG:

1 ETQ201 Entering upgrade-phase "PREP_INPUT/ASCS_CHK" ("20240805200335")

2 ETQ367 Connect variables are set for standard instance access: System-nr = '02', GwService = 'sapgw02' Client = '000'

1 ETQ200 Executing actual phase 'PREP_INPUT/ASCS_CHK'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[ALPFile] = ''

2 ETQ399 Arg[Options] = 'CHECK'

1 ETQ000 ==================================================

1 ETQ399 Standalone enqueue server detected.

2 ETQ011 --------------------------------------------------

2 ETQ399 SYSTEM MANAGER: Get all instances with type 'ASCS':

1 ETQ399 No ASCS instance detected at SUM instancelist.

1 ETQ399 ASCS Instance is detected at SAP profiles (ASCS host 'techrelam' and ASCS sysnum '01').

1 ETQ399 Standalone enqueue server is detected at profiles (ASCS host '' and ASCS sysnum ''), but no valid ASCS instance is found at SUM instancelist. Better reinit the SUM instancelist.

1 ETQ399 SAPCONTROL MANAGER: getSystemInstanceList with dumpfile: /usr/sap/TRP/SUM/SUM/abap/log/SAPCONTROL_INSTANCELIST.OUT

3 ETQ120 20240805200335: PID 30656 execute '/usr/sap/TRP/D02/exe/sapcontrol -prot NI_HTTP -nr 02 -function GetSystemInstanceList', output written to '/usr/sap/TRP/SUM/abap/log/SAPCONTROL_INSTANCELIST.OUT'.

3 ETQ122 20240805200335: PID 30656 exited with status 0 '' (time:     0.0/    0.0/    0.0/93MB real/usr/sys/maxmem)

1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: 02, Instance Host: hec53v031439

2 ETQ011 --------------------------------------------------

2 ETQ399 SYSTEM MANAGER: Get all instances with type 'ASCS':

1 ETQ399 No ASCS instance detected at SUM instancelist.

1EETQ399 Last generated error message is: The SUM instancelist has been rebuilt but no valid ASCS instance

1EETQ399Xcan be found! Check your system settings.

1EETQ204 Upgrade phase "ASCS_CHK" terminated with severe errors ("20240813200335")

When you check the status of the instances (sapcontrol -nr <inst no> -function GetSystemInstanceList), you get the following result:

  GetSystemInstanceList

  OK

  hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus

  <hostname>, <inst no>, ..., ... , ..., ABAP|GATEWAY|ICMAN|IGS, GREEN

It does not list ASCS instance in the output.

Resolution

1. Stop the System.
2. Fix permission issue of folder $(DIR_GLOBAL)/sapcontrol                                                  Observation: If you are using cluster for (A)SCS / ERS instance, this folder could be a NFS share. This folder must be accessible by all instances of same system / SID.
3. You can rectify the permission of this folder with the help of your OS / File system / Storage team.
4. Once it is rectified, you can test by creating a test file in the same location i.e $(DIR_GLOBAL)/sapcontrol. 
5. The command "sapcontrol -nr <inst no> -function GetSystemInstanceList" will now list (A)SCS instance.
6. Once the above steps are successful, Start the system, then repeat the phase in SUM.

Workaround Solution:

Scenario : If you are using a heterogeneous system migration where PAS and ASCS are running in a Windows environment and AAS is running in a Linux environment (such as in a RISE migration/conversion scenario), RISE will not provide a Windows system for migration. Consequently, the RISE team will not provide a Windows system for migration. As a result, we cannot share the /sapmnt folder from Windows to Linux, which means that the SUM tool cannot detect the ASCS instance from Linux. Therefore, we need to move the ASCS sapcontrol file from the Windows server to the Linux server.

The highlighted sapcontrol file for the ASCS instance can be identified by the instance number in the file name. This file contains the ASCS instance hostname and the PID (Process ID) for the operating system.

Note: The sapcontrol file is update every minute.

When you encounter an error with the SUM tool, copy the highlighted file from source windows system to the RISE system (Linux) folder location: /sapmnt/TRP/global/sapcontrol or /usr/sap/TRP/SYS/global/sapcontrol.

Once the file is moved from the source system to the target system, repeat the SUM phase. SUM will detect the ASCS instance and proceed to the next phase.

This all activity should executed within one minute and if you missed again replace the file from source to target.

Thank you for reading the blog!

 

How to define the maximum file size in SAP Content Server 7.5

How to define the maximum file size in SAP Content Server 7.5

"There is a need to adjust the maximum file size in SAP Content Server 7.5 (and above) to a desired higher or lower limit."

"The maximum file size is determined by the profile parameter icm/HTTP/max_request_size_KB."

The profile configuration file can be found in the DIR_PROFILE of the new installation, for example, /usr/sap/<SID>/SYS/profile.

The parameter can also be used to set a smaller limit if desired.

Important Note:

Please be aware that adjusting the upload limit for file size will impact all applications.

Any files uploaded prior to the limit adjustment, which exceed the new limit, will become inaccessible.

For instance, if the limit is set at 150MB and a 200MB file was uploaded before the adjustment, it will no longer be accessible.

Reference :

SAP Snote

SAP help