Hello,

I'm trying to export Solution Manager database instance installed on Windows\SQL server.

The export is performed with Sapinst.

Solution Manager is installed in distributed environment:

Host 1 - Host_DB (no SAP software/users - only SQL server executables)

Host 2 - Host_ASCS_SCS

Host 3 - Host_APP

From which host should I actually perform database export? I want to export only database instance - without CI.

When I start the export on Host_APP or Host_ASCS_SCS no database export is performed - only Java executables and SDM is exported.

Sapinst even don't ask me about database parameters. When i start export on Host_DB everything seems to be OK, but during database export I have the following error:

=======================================

sapparam: sapargv(argc, argv) has not been called!

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

\\mih-vssmpci2\sapmnt\SMP\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130330215539

\\mih-vssmpci2\sapmnt\SMP\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#17 $ SAP

\\mih-vssmpci2\sapmnt\SMP\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Jan 26 2013 03:12:24

patchinfo (patches.h): (0.413) SAP HANA: Corrupt database after R3load import (note 1806935)

process id 6936

\\mih-vssmpci2\sapmnt\SMP\SYS\exe\uc\NTAMD64\R3load.exe -testconnect

(DB) ERROR: DbSlControl(DBSL_CMD_IMP_FUNS_SET) rc = 20

(DB) ERROR: DbSlErrorMsg rc = 20

\\mih-vssmpci2\sapmnt\SMP\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

\\mih-vssmpci2\sapmnt\SMP\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130330215539

=======================================

It is interesting, how Sapinst is going to perform the export, if there are no SAP executables on the database host?

SAP kernel, R3load,R3trans - upgraded to the latest versions.

Any advices will be appreciated.

Thank You.

In this document you will find the latest information about the SAP kernel such as

• Announcements of SP stack kernel deliveries
• Other news related to the development, maintenance and usage of the SAP kernel versions 72X (720, 720_EXT, 721, 721_EXT, 722, 722_EXT) and 74X (741, 742, 745)

If you are interested in getting notifications when this document is updated, please activate the "Receive email notifications" feature. To unsubscribe from receiving notifications, click on "Stop email notifications".

News

13.10.2015: SP Stack Kernel 721 PL#600 Released

SP stack kernel 721 PL #600 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2214191.

Information on known issues in the stack kernel 721 PL #600 can be found in SAP Note 2214680. This note will be updated on a regular basis.

02.10.2015: issue with Oracle lib_DBSL 722 PL 13

Please do not use patch 13 for the 722 Oracle lib_DBSL

Further details can be found in note 2220724. A fix is expected early next week.

14.09.2015: SP Stack Kernel 741 PL#300 Released

The last SP stack kernel for the 741 kernel version has been released today. Kernel 741 PL #300 can be downloaded from the archive area of SAP Support Portal. Refer to release note 2207362 for information on fixes included in this stack kernel.

As announced previously, kernel 741 has reached its end of maintenance, see note 1969546 for more detail. Future 74* kernel corrections will be delivered through 742 kernel patches.

08.07.2015: SP Stack Kernel 742 PL#200 Released

SP stack kernel 742 PL #200 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2178917.

Information on known issues in the stack kernel 742 PL #200 can be found in Note 2176515. This note will be updated on a regular basis.

07.07.2015 SAP Kernel 741 maintenance

The SAP Kernel 741 reached its end of maintenance, see note 1969546. We will continue to deliver regression fixes during July and a final stack kernel 741 PL#300 in August. After that corrections will be delivered through kernel 742 patches.

12.06.2015 SAP Kernel Archive

SAP Kernels which are out of maintenance like SAP Kernel 720 can be found in the archive https://support.sap.com/software/patches/archive.html

For SAP Kernel 720 the last version is patch level 800. Please read the release note 2158874  - SAP Support Package Stack Kernel 7.20 (EXT) Patch Level 800. Corresponding note for regression found in the future is 2138737.

20.05.2015 SAP Kernel 722 Released

SAP kernel 722 has been released for customers today. The first shipment (Kernel 722 PL#4) can now be downloaded from SAP Support Portal. With this a new release cycle has been established for 72X kernel versions that can be used with all SAP NetWeaver releases 7.00-7.31:

• Kernel 720 reached its end of maintenance, no further corrections will be provided for this kernel version
• Kernel 721 becomes the standard kernel containing only corrections/bug fixes
• Kernel 722 replaces Kernel 721 in its role as Innovation Kernel. Besides regular corrections, new features/enhancements/improvements will be delivered with Kernel 722.

Refer to SAP Note 2133909 for general information on Kernel 722 including new features and current limitations. This note will be updated on regular basis.

Kernel 722 can be applied manually as a kernel patch, see Note 2115344 - Installation of Kernel 722 (EXT) for detailed instructions. Options to apply Kernel 722 during upgrade/update are outlined in Note 2133909.

04.05.2015: SP Stack Kernel 721 PL#500 Released

A new SP stack kernel 721 PL #500 is now available on SAP Support Portal.

SAP Note 2158856 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #402.

All regressions known in the PL #402 have been fixed.

Review SAP Note 2155366 for known issues in the stack kernel 721 PL #500. This note will be continuously updated.

14.04.2015: Kernel 742 Released as DCK to Kernels 740 and 741

After an extended validation phase kernel 742 PL#101 has been released as a downward compatible kernel (DCK) to kernels 741 and 740 and can be used instead of these with SAP NetWeaver 7.4. Refer to Note 2128122 for details on installation and usage of kernel 742 as DCK. The release roadmap for 74* kernels is presented in Note 1969546.

31.03.2015: SP Stack Kernels 741 PL#201 and 742 PL#101 are delivered

As announced previously, SP Stack kernels for 741 and 742 kernel versions have been updated. 741 PL#201 replaces 741 PL#200 and 742 PL#101 replaces 742 PL#100. New SP stack kernels can be now downloaded from SAP Support Portal, following fixes are included:

• Regression in the Oracle DBSL Library (Note 2118448, Point 2 - Termination during secondary database connection; LRAW length error) is removed.
• CommonCryptoLib has been updated to the version 8.4.35 (see Note 2134460.)

For more details on 741 PL#201 refer to Notes 2150081 - SAP Support Package Stack Kernel 7.41 Patch Level 201 and 2100429 - Known regressions in kernel 7.41 patch level 201.

Fixes and enhancements in the SP stack kernel 742 PL#101 are listed in the note 2145156. Information on known issues with this stack kernel can be found in the Note 2134238.

19.03.2015: Update on SP Stack Kernels 741 PL#200 and 742 PL#100

The latest SP stack kernels 741 (PL#200) and 742 (PL#100) contain a regression in the Oracle DBSL Library, see Note 2118448 -Termination during secondary database connection; LRAW length error, Point 2.

As a solution you may use the latest ORA lib_dbsl available on SAP Support portal. For kernel 741 on Windows, please be aware of the issue 2142073 - Application server in Windows NT with Oracle does not start.

Updated stack kernels will be provided as soon as possible.

11.03.2015: SP Stack Kernel 721 PL#402 Released

SP Stack kernel 721 PL #402 has been released and can be downloaded from SAP Support Portal. The issues from PL#400 (Note 2118382) and PL#401 (Note 2138260) are fixed.

Refer to Note 2138680 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 402 for overview of new features, enhancements and improvements added since PL#300. Known regressions are documented in Note 2138678.

09.03.2015: SP Stack Kernel 742 PL#100 Released

SP stack kernel 742 PL #100 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2136550.

Information on known issues in the stack kernel 742 PL #100 can be found in Note 2129327. This note will be updated on regular basis.

04.03.2015: SP Stack Kernel 721 PL#401 Revoked

SP Stack kernel 721 PL #401 has been revoked from SAP Support Portal for all platforms except for MS Windows because the kernel archives contained some files with wrong versions.

In most cases it is not necessary to replace the kernel in a system running with PL#401 because the issue has a limited impact and does not affect the kernel itself. Details are outlined in Note 2138260.

SP stack kernel PL#402 will be released as soon as possible; this document will be updated accordingly.

06.02.2015: SP Stack Kernel 741 PL#200 Released

A new SP stack kernel 741 PL #200 has been released today and can be downloaded from SAP Support Portal.

For a summary of enhancements and improvements included into this stack kernel, see SAP Note 2101802 - SAP Support Package Stack Kernel 7.41 Patch Level 200.

30.01.2015: SP Stack Kernel 721 PL#401 Replaces PL#400

Current SP stack kernel 721 PL#400 has been replaced with PL#401, see Note 2121693 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 401.

It fixes a file permission issue that has a very limited impact:

• It occurs with 721_EXT kernel on Windows platforms only
• It has no effect at runtime, only for future system maintenance
• Workaround is easy.

This means: even if above criteria apply, it is not always necessary to replace already installed 721 kernel PL#400. Refer to Note 2118382 for more information.

Note 2084437 contains the list of known regressions in the stack kernel 721 PL #401. This note will be continuously updated.

16.12.2014: SP Stack Kernel 721 PL#400 Released

A new SP stack kernel 721 PL #400 is now available on SAP Service Marketplace.

SAP Note 2101779 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #300.

All regressions known in the PL #300 have been fixed.

Review SAP Note 2084436 for known issues in the stack kernel 721 PL #400. This note will be continuously updated.

Hi Experts,

Am raising this question for a SOX compliance issue in our ECC production system.

As per SOX compliance guideline we should not use DDIC user except transport and we are not using DDIC anywhere in our production environment.

Recently in transaction ST03N we have found that report/program sapstartsrv has been called out with user DDIC via RFC calls which includes function modules RFCPING & TH_GET_PARAMETER

Kindly give your suggestions on the below

1. Why program sapstartsrv has been called out with DDIC user with internal RFC destination?

2. How do we prevent this?

Thanks,

Preetha Balan

Hi, How can I trace where the create date and update date of the data for tables A065 and KNOP? Thanks!

Dear Experts,

I have noticed, that SAP has released EHP 3 for NetWeaver AS Java 7.0:

I wanted to make a test installation of it, but unfortunately no SWPM supports it! In the normal SWPM

it is not listed at all and in the 70SWPM... there is an option to install an ABAP system ONLY:

And this is the LATEST SWPM available on the marketplace...

Please kindly advise what is the trick in order to get this installed :-) Thanks a lot in advance!

Hello everybody,

we have a small license issiue with our JAVA-Stack (AS Java). We installed a dual-stack System and now the temporary license is invald. We installed a new license in the ABAP-Part via the SLICENCE TA but for the JAVA Part we don't find any option to get a license from SAP. In the license request application there is no option "J2EE-Engine" as mentioned in the relevant notes. Can anybody assist in this case or give us a hint?

Many thanks...

Moritz

At previous companies I've worked at, a user (e.g. SAP_BATCH) has been used to create batch jobs, which would then be read and processed by Tivoli.

The SAP_BATCH user would be of type System.

When a batch job was required, this process would be followed:

• A user would log on as themselves (e.g. JohnSmith) and change the SAP_BATCH user from type Systemto Dialogue.
• They would then log on as the user SAP_BATCH and create/edit the batch jobs
• They would then log off of the user SAP_BATCH
• They would then log on again as themselves (e.g. JohnSmith) and change the SAP_BATCH user from type Dialogue to System

Where I am currently working, the process is for the staff to log on as user SAP_BATCH. This user is of type Dialogue and has a restricted role-set, allowing them to only create new batch jobs.

Please can you tell me which process is valid. Are both valid? Is there a better way to do this?

Thanks.

Paul

Hello,

we migrate our PI System to PO 7.40. Now we want to connect our PO System with our Acitve Directory. For the authentication we want use the LDAP conenction. The Problem is our Active Directory runs on a Windows Server 2008 and in note 983808 stand that the highest certified Windows Server for JAVA is Windows Server 2003. In the configurations from the usermanagemt I can also only take SUN ONE LDAP Server, Novell LDAP Server or Siemens LDAP Server at the data source. Exist an note from SAP which include Windows Server 2008 as Data Source? And maybe also Windows Server 2012 already? I don´t find a note.

Have anybody an example config file to configurat PO to Active Directory with LDAP?

Best regards.

Dennis Wißkirchen

Good Day,

Since Yesterday i have had problems starting the application server where by it hangs on sapcontrol as seen below

startsap r3
Checking sid Database
-------------------------------------------
setTrace: false
J2EE Database is running
See logfile /home/sidadm/JdbcCon.log
Starting Startup Agent sapstartsrv
OK
Instance Service on host hostname started
-------------------------------------------
starting SAP Instance J30
Startup-Log is written to /home/sidadm/startsap_J30.log
-------------------------------------------
/usr/sap/sid/J30/exe/sapcontrol -prot NI_HTTP -nr 30 -function Start

The kernel has been replaced and the enviroment had been double checked, sapcontrol does not generate any log files

-rw-r--r-- 1 sidadm sapsys     342 2013-09-10 14:21 INSTSTAT

-rw-r--r-- 1 sidadm sapsys   31563 2013-09-11 09:29 class_prefetch.lst

-rw-r--r-- 1 sidadm sapsys     850 2013-09-11 10:50 sapstartsrv.old

-rw-r--r-- 1 sidadm sapsys    2106 2013-09-11 11:04 available.log

-rw-r--r-- 1 sidadm sapsys       8 2013-09-11 11:04 logsave.bin

-rw-r--r-- 1 sidadm sapsys     851 2013-09-11 11:04 sapstartsrv.log

hostname:sidadm 65>

the contents of the log file startsap_J30.log can be found below

hostname:sidadm 68> cat startsap_J30.log
Trace of system startup/check of SAP System sid on Wed Sep 11 11:04:03 CEST 2013

Called command: /usr/sap/SID/SYS/exe/uc/linuxx86_64/startsap start

-------------------------------------------
11:04:05
Starting Startup Agent sapstartsrv

-------------------------------------------
11:04:16
Instance Service on host hostname started

-------------------------------------------
11:04:16
starting SAP Instance J30

-------------------------------------------
11:04:16
Startup-Log is written to /home/sidadm/startsap_J30.log

-------------------------------------------
11:04:16
/usr/sap/SID/J30/exe/sapcontrol -prot NI_HTTP -nr 30 -function Start

running sapcontrol from the command line does the same where by no feedback is supplied.

any help would be appreciated

Best Regards

Marius

Dear Experts

we have query spro tcode in Quality server with only one module access

we have done with SPRO_ADMIN command but when we have created role and add that customization it works fine

but there is a tab we need to hide that tab bcaz once some body click on that whole spro comes into picture

i have tried with SHD0 to hide that tab it didn't work

we need to remove SAP Reference IMG tab

i need some suggestion so i could able to disable or hide that

Regards

Hi All,

we did refresh of BW DEV system to BW Sandbox HANA system. the dev bw is connected to dev ecc and sandbox was connected to quality ecc.

we have some doubts about post steps after this refresh. as per note 886102 - System Landscape Copy for SAP NetWeaver BW, scenario B3 suits our case. the note says deletion source system connection of ecc which was copied over from source bw system. we did not refresh ecc system. but this link Post processing steps for SAP BW system copy or db copy says just do bdls, create partner port, profiles and restore source system. which one to follow now? should we delete development ecc source system from sandbox bw(transfer rules and psa tables will be deleted) or follow the blog and just restore after bdls, etc.

thanks,
Ranjith

Hello experts,

I am facing issues during the deployment of web-dynpro java application on the application based on NW740.

The deployment is getting finished with the warning message:

===== PROGRESS START =====

Deploying [sap.com_tc~mdm~srmcat~redirect (sda)] ...

Deployment of [sap.com_tc~mdm~srmcat~redirect (sda)] finished.

===== PROGRESS END =====

===== DEPLOY RESULT =====

sdu id: [sap.com_tc~mdm~srmcat~redirect]

sdu file path: [/usr/sap/EIW/J33/j2ee/cluster/server0/temp/tc~bl~deploy_controll

er/archives/289/1523603713845137/tc~mdm~srmcat~redirect.sda]

version status: [NEW]

deployment status: [Success]

description: [

1. Warning occurred on server 336793750 during deploy of sap.com

/tc~mdm~srmcat~redirect : References Test: There are no matching deploy time ref

erences (described in META-INF/SAP_MANIFEST.MF) for the following runtime refere

nces [sap.com/tc~conn~connectorframework, sap.com/com.sap.mdm.tech.mdm4j] (descr

ibed in the META-INF/application-j2ee-engine.xml), file: tc~mdm~srmcat~redirect.

sda, severity: warning

Warning occurred on server 336793750 during deploy of sap.com/tc~mdm~srmcat~redi

rect : Mapping Test: com.sap.ASJ.webjlin.000021 Invalid servlet mapping. servlet

with name "action" cannot be found in the web application. Value of "<servlet-n

ame>" sub-tag of "<servlet-mapping>" tag does not match any value of "<servlet-n

ame>" sub-tag of "<servlet>" tag., file: sap.com~tc~mdm~srmcat~ociredir.war#WEB-

INF/web.xml, severity: warning

CSN component of deployment item is not available]

The same application when deployed on application server based on NW730 it works without any issues.

When we try accessing application deployed on NW740 server, nothing comes up. We suspect the warning during deployment to be the issue, but we are not sure. Could you please guide us.

Thanks,

Rakesh

Dear all

we have requirement in spro to disable SAP Reference IMG  node

Could any body give some suggestions

we have prepared SPRO_ADMIN role but when we run command SPRO it shows  that particular module only and when we click on SAP Reference IMG it show whole SPRO which we need to restrict

Regards

In this document you will find the latest information about the SAP kernel such as

• Announcements of SP stack kernel deliveries
• Other news related to the development, maintenance and usage of the SAP kernel versions 72X (720, 720_EXT, 721, 721_EXT, 722, 722_EXT) and 74X (741, 742, 745)

If you are interested in getting notifications when this document is updated, please activate the "Receive email notifications" feature. To unsubscribe from receiving notifications, click on "Stop email notifications".

News

16.10.2015: Kernel 722 PL14, PL15 and enserver PL 14 revoked

As a precaution Enqueue Server 722 PL 14 (enserver.sar) and Kernel (dw.sar) 722 PL 14 and PL 15 have been revoked from the SAP Support Portal.
The new patch of the Enqueue Server might not be 100% compatible to older clients (e.g. disp+work PL 13) and the newer disp+work starting PL 14 might not be 100% compatible with old Enqueue Servers (prior patch 14). Standard operations Enque, Dequeue and DequeueAll are NOT affected. Investigation is ongoing.

13.10.2015: SP Stack Kernel 721 PL#600 Released

SP stack kernel 721 PL #600 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2214191.

Information on known issues in the stack kernel 721 PL #600 can be found in SAP Note 2214680. This note will be updated on a regular basis.

02.10.2015: issue with Oracle lib_DBSL 722 PL 13

Please do not use patch 13 for the 722 Oracle lib_DBSL

Further details can be found in note 2220724. A fix is expected early next week.

14.09.2015: SP Stack Kernel 741 PL#300 Released

The last SP stack kernel for the 741 kernel version has been released today. Kernel 741 PL #300 can be downloaded from the archive area of SAP Support Portal. Refer to release note 2207362 for information on fixes included in this stack kernel.

As announced previously, kernel 741 has reached its end of maintenance, see note 1969546 for more detail. Future 74* kernel corrections will be delivered through 742 kernel patches.

08.07.2015: SP Stack Kernel 742 PL#200 Released

SP stack kernel 742 PL #200 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2178917.

Information on known issues in the stack kernel 742 PL #200 can be found in Note 2176515. This note will be updated on a regular basis.

07.07.2015 SAP Kernel 741 maintenance

The SAP Kernel 741 reached its end of maintenance, see note 1969546. We will continue to deliver regression fixes during July and a final stack kernel 741 PL#300 in August. After that corrections will be delivered through kernel 742 patches.

12.06.2015 SAP Kernel Archive

SAP Kernels which are out of maintenance like SAP Kernel 720 can be found in the archive https://support.sap.com/software/patches/archive.html

For SAP Kernel 720 the last version is patch level 800. Please read the release note 2158874  - SAP Support Package Stack Kernel 7.20 (EXT) Patch Level 800. Corresponding note for regression found in the future is 2138737.

20.05.2015 SAP Kernel 722 Released

SAP kernel 722 has been released for customers today. The first shipment (Kernel 722 PL#4) can now be downloaded from SAP Support Portal. With this a new release cycle has been established for 72X kernel versions that can be used with all SAP NetWeaver releases 7.00-7.31:

• Kernel 720 reached its end of maintenance, no further corrections will be provided for this kernel version
• Kernel 721 becomes the standard kernel containing only corrections/bug fixes
• Kernel 722 replaces Kernel 721 in its role as Innovation Kernel. Besides regular corrections, new features/enhancements/improvements will be delivered with Kernel 722.

Refer to SAP Note 2133909 for general information on Kernel 722 including new features and current limitations. This note will be updated on regular basis.

Kernel 722 can be applied manually as a kernel patch, see Note 2115344 - Installation of Kernel 722 (EXT) for detailed instructions. Options to apply Kernel 722 during upgrade/update are outlined in Note 2133909.

04.05.2015: SP Stack Kernel 721 PL#500 Released

A new SP stack kernel 721 PL #500 is now available on SAP Support Portal.

SAP Note 2158856 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #402.

All regressions known in the PL #402 have been fixed.

Review SAP Note 2155366 for known issues in the stack kernel 721 PL #500. This note will be continuously updated.

14.04.2015: Kernel 742 Released as DCK to Kernels 740 and 741

After an extended validation phase kernel 742 PL#101 has been released as a downward compatible kernel (DCK) to kernels 741 and 740 and can be used instead of these with SAP NetWeaver 7.4. Refer to Note 2128122 for details on installation and usage of kernel 742 as DCK. The release roadmap for 74* kernels is presented in Note 1969546.

31.03.2015: SP Stack Kernels 741 PL#201 and 742 PL#101 are delivered

As announced previously, SP Stack kernels for 741 and 742 kernel versions have been updated. 741 PL#201 replaces 741 PL#200 and 742 PL#101 replaces 742 PL#100. New SP stack kernels can be now downloaded from SAP Support Portal, following fixes are included:

• Regression in the Oracle DBSL Library (Note 2118448, Point 2 - Termination during secondary database connection; LRAW length error) is removed.
• CommonCryptoLib has been updated to the version 8.4.35 (see Note 2134460.)

For more details on 741 PL#201 refer to Notes 2150081 - SAP Support Package Stack Kernel 7.41 Patch Level 201 and 2100429 - Known regressions in kernel 7.41 patch level 201.

Fixes and enhancements in the SP stack kernel 742 PL#101 are listed in the note 2145156. Information on known issues with this stack kernel can be found in the Note 2134238.

19.03.2015: Update on SP Stack Kernels 741 PL#200 and 742 PL#100

The latest SP stack kernels 741 (PL#200) and 742 (PL#100) contain a regression in the Oracle DBSL Library, see Note 2118448 -Termination during secondary database connection; LRAW length error, Point 2.

As a solution you may use the latest ORA lib_dbsl available on SAP Support portal. For kernel 741 on Windows, please be aware of the issue 2142073 - Application server in Windows NT with Oracle does not start.

Updated stack kernels will be provided as soon as possible.

11.03.2015: SP Stack Kernel 721 PL#402 Released

SP Stack kernel 721 PL #402 has been released and can be downloaded from SAP Support Portal. The issues from PL#400 (Note 2118382) and PL#401 (Note 2138260) are fixed.

Refer to Note 2138680 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 402 for overview of new features, enhancements and improvements added since PL#300. Known regressions are documented in Note 2138678.

09.03.2015: SP Stack Kernel 742 PL#100 Released

SP stack kernel 742 PL #100 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2136550.

Information on known issues in the stack kernel 742 PL #100 can be found in Note 2129327. This note will be updated on regular basis.

04.03.2015: SP Stack Kernel 721 PL#401 Revoked

SP Stack kernel 721 PL #401 has been revoked from SAP Support Portal for all platforms except for MS Windows because the kernel archives contained some files with wrong versions.

In most cases it is not necessary to replace the kernel in a system running with PL#401 because the issue has a limited impact and does not affect the kernel itself. Details are outlined in Note 2138260.

SP stack kernel PL#402 will be released as soon as possible; this document will be updated accordingly.

06.02.2015: SP Stack Kernel 741 PL#200 Released

A new SP stack kernel 741 PL #200 has been released today and can be downloaded from SAP Support Portal.

For a summary of enhancements and improvements included into this stack kernel, see SAP Note 2101802 - SAP Support Package Stack Kernel 7.41 Patch Level 200.

30.01.2015: SP Stack Kernel 721 PL#401 Replaces PL#400

Current SP stack kernel 721 PL#400 has been replaced with PL#401, see Note 2121693 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 401.

It fixes a file permission issue that has a very limited impact:

• It occurs with 721_EXT kernel on Windows platforms only
• It has no effect at runtime, only for future system maintenance
• Workaround is easy.

This means: even if above criteria apply, it is not always necessary to replace already installed 721 kernel PL#400. Refer to Note 2118382 for more information.

Note 2084437 contains the list of known regressions in the stack kernel 721 PL #401. This note will be continuously updated.

16.12.2014: SP Stack Kernel 721 PL#400 Released

A new SP stack kernel 721 PL #400 is now available on SAP Service Marketplace.

SAP Note 2101779 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #300.

All regressions known in the PL #300 have been fixed.

Review SAP Note 2084436 for known issues in the stack kernel 721 PL #400. This note will be continuously updated.

HI,

I have a few questions regarding memory management in SAP system.

I read about it a lot butI still confused

My question is:

1. How I know how much memory all the WPs is used? (How much memory all the WPtakesfrom the OS)

2. How I know how much memory all the DIA's is used? (How much memory all the DIAtakesfrom the OS)

Idontwantseperateit to extend memory roll areaetc, I want to know percentage of memory all the WP takes from the OS.

I asked it becauseineed to increase the number of DIA in the APO system, but before the change I want to know how much memory the WP and the DIA used now, I want to avoid frommemory problemin the OS afteriincrease the number of DIA.

My server is always around 80% memory used, but I limit the memory used bySAP systemwith the parameter PHYS_MEMSIZE, and Idontthink the SAP takes all the PHYS_MEMSIZE parameter value.

And it'stakeme to the 3 question:

3.howI know how much memory the SAP system takes fromOS? I limit the memory used by SAP with PHYS_MEMSIZE, but I want to know exactly how much memory the SAP takes and if he used all the valueigive in the PHYS_MEMSIZE.

Maybe Idontneed to increase memory in the server just to increase the number of DIA

Thanks for your help my freinds

Naor

Dear Experts,

we have ADS configured from ABAP to Java system but

"fp_test_00" is giving com.adobe.ProcessingException(200101) error for any selected OUTPUTDEVICE.

     A.  HTTP RFC is giving error 403 FORBIDDEN

     B. In VISUAL ADMINISTRATOR ->  destination ->  HTTP service FP_ICF_DATA_<SID>  giving HTTP Ping Error 404.

Any help much appreciated.

Kind Regards,

Domnic.

Hi Guys,

I am facing an issue with certain background users.

when these users try to send email to some recipient, sender email address comes as SAPUSER@default-domain.

I am facing this issue in 2 scenario. one while send email notification during PO release strategy using workflow. In this case sender email id shown is

WF-BATCH@default-domain. where in it has to be the one maintained in SU01.

In second scenario I have scheduled few background jobs. On execution of these jobs I send Email to few recipient. In this case the sender ID shown in Email is SAPUSER@default-domain. wherein it has to be the one maintained in SU01.

Kindly advice if any one has faced same issue in past.

Regards,

Bhawarlal C

Hello,

i have installed TREX 7.10 r64 on SLES 12 (amd64).

If i try to open the MC with IE Browser: http://<hostname>:50013/

i can see a message: The host <name> coud not be resolved.

But the /etc/hosts is OK.

The name resolv FQDN an short work on the system.

What is the Problem or how to fix it ?

Thanks

Dear All,

In SAP ABAP system, Own certificate of my system is still fine but one of certificate list was expired and the functional team need to keep it for reference in STRUST.

So a warning message will show everyday then I have to remove the message in SM02 every time.

Do you know how to disable the warning message without removing the expired certificate?

Thank in advance,

Korkiat

Dear friends,

I am upgrading an ERP 6.0 system to EHP7 and currently facing an issue in the START_SHDI_SHD2 phase. The shadow system is up and running, and I am able to login. But the RFC login to it fails with a short dump in SAPMSSY1 which mentions, "DYNPRO_NOT_FOUND".

When I checked in st22, the error is "You are trying to use screen 3004 in program "SAPMSSY1". This screen does not exist."

The current kernel is 742, I tried changing the kernels patch levels , and also tried downgrading it to 741 and 740. Unfortunately, didn't help.

Could you please advise, how to correct this error ?

Thanks and regards,

Sudarsan.