Tuesday, January 19, 2016

2206460 - Release restrictions for SAP NetWeaver 7.5

Symptom
Release restrictions for SAP NetWeaver 7.5


Other Terms
NW 7.5 NetWeaver 7.50 Restrictions Limitations


Reason and Prerequisites
At the time of the release of SAP NetWeaver 7.5 limitations existed concerning the productive usage of certain functions. This note provides customer information on these restrictions. See below.


Solution

BC-DB-HDB
Release with restrictions
Minimal DB system platform requirements for SAP NetWeaver 7.5
Details see note 2158828 - Minimal DB system platform requirements for SAP NetWeaver 7.5 Additionally, please check the OS/DB Product Availability Matrix at http://service.sap.com/pam for information on supported databases and operation systems.
( Changed at 14.09.2015 )

BC-EIM-ESH
No release
No extended language replacement vectors available in Enterprise Search
Any search will run and search in the language a user is logged in with, and will display results in that same language. The search will not show hits found in other languages.
( Changed at 14.09.2015 )

BC-ESI-WS-JAV-RT
No release
Dynamic Web Service and Proxy generation fail for external Schema
SAP NetWeaver 7.50 is built on Java 8. Java 8 uses the new Java API for XML Processing - JAXP 1.5, where some new properties have been introduced. One of these properties - javax.xml.XMLConstants. ACCESS_EXTERNAL_SCHEMA, interferes with the Web Services code in SAP NetWeaver 7.50 which is related with the dynamic Web Service Proxy generation. In this case, some specific WSDLs parsing fail, throwing exception that causes specific Web Service scenarios to fail. The root cause is due to an issue into the early versions of OpenJDK implementation of JAXB protocol. The issue is fixed into the newest versions of JAXB protocol implementation which is to be used in SAP NetWeaver 7.50 SP01 and later. The workaround for SAP NetWeaver AS Java 7.50 SP00 is described in SAP Note 2212028. The issue into the Java Application Server will be resolved into the newer Service Packs of SAP NetWeaver 7.50. For resolving the issue in SAP NetWeaver Developer Studio (NWDS) the need for applying SAP Note 2217399 will remain in the newer NetWeaver SPs.
( Changed at 12.10.2015 )

BC-INS-MIG
No release
SAP Strategy for Cluster and Pool Tables
See SAP note 1892354
( Changed at 20.10.2015 )

BC-JAS-SDO
No release
Java Enterprise Applications with SAP BPM business processes do not start after AS Java upgrade
After upgrading the the SAP NetWeaver AS Java to 7.50 SP00 patch level 0 it can happen that some Java Enterprise Application (EAR) that contain SAP BPM business processes do not start. In turn this means that the SAP BPM processes that are contained in the failing EARs can’t be executed. This can affect the start of new processes as well as existing process instances. To avoid running into this problem it is strongly recommended to apply at minimum patch level 1 for Software Component J2EE-FRMW as described in SAP Note 2186799.
( Changed at 12.10.2015 )

BC-SEC
No release
Extended secure server settings released for pilot customers only
Extended secure server settings released with NW AS ABAP 7.4 SP08 shall be used by pilot customers only. Application process and further details see customer note 2040644
( Changed at 14.09.2015 )

BC-TRX-SES
No release
SES cannot run with SAP HANA as a search engine
For NetWeaver systems running on SAP HANA as the database, the Search Engine Service (SES) still needs a TREX or BWA as search engine. SES details see note 1254901.
( Changed at 12.10.2015 )

BC-UPG
No release
Clustered tables as unknown objects in ABAP Dictionary in DB02 after upgrade to 7.50 on Hana DB
If your database management system is SAP HANA, the tables DOKTL, TERMC1 , TERMC2 and TERMC3 appear in the Tables and Indexes Monitor (transaction DB02) in section "Unknown objects in ABAP Dictionary" of the missing tables/indexes diagnostics. Check in the ABAP Dictionary Maintenace (transaction SE11) whether those  tables are of type "Cluster". If this is the case, you can drop those tables directly in the database. These tables are clustered after upgrade, even they have been transparent before. If such a table need to be transparent, for example,  if you want to use it in EXEC SQL (planned to be used as CDS Data View) , de-cluster it according to SAP Note 2227432 after the update or upgrade. The correction is planned with an SUM SP15 patch. Please see corresponding SAP note 2155664 for further information.
( Changed at 20.10.2015 )

BC-XI-IBD-MOD
No release
Integrated ARIS (modeling) in ESR end of support
Details see note 2120723
( Changed at 12.10.2015 )

BC-XI-IS-IEN
No release
Payload is always encrypted entirely when persisted in message store
If you have selected Sensitive Information for a service interface in the ES Repository, the Process Integration runtime encrypts the entire payload before persisting it in the message store and logs any access to an encrypted message of this kind. It is not possible to encrypt only a few attributes of the payload. The encryption is applied to the entire payload. This feature can only be enabled at interface level. If the interface contains multiple operations, the encryption and logging is extended to all operations. It is not possible to maintain or control the Sensitive Information check box at operation level.
( Changed at 12.10.2015 )

CA-FE-FLP-EU
No release
Fiori Launchpad limited browser support on Microsoft Windows Phone 8.1
See SAP note 2097198
( Changed at 11.11.2015 )

CA-UI5-COR
No release
Limited Browser Support - XML Templating
Applications using XML templating (i.e like Smart Template based applications on S/4 HANA and certain Smart Business applications) cannot be run on Microsoft IE 10, IE 11 and Microsoft Edge - Details see SAP note 2218120.
( Changed at 12.10.2015 )

CA-UI5-FL-LRP
No release
LRep authorization check for APF Namespace
LRep Content route for APF Namespace can be accessed without authorization checks. For correction see SAP note 2232004
( Changed at 19.11.2015 )

EP-PIN-TOL
No release
EP upgrade to 7.50 with multiple server nodes requires restart for custom themes to be available
When upgrading the Enterprise Portal to 7.50 SP0 for landscapes with more than one server node: After upgrade some of the server nodes might not contain the custom theme. System restart will restore the custom theme on all server nodes.
( Changed at 11.11.2015 )

XX-PART-ADB
No release
SAP Interactive Forms by Adobe does not support INT8 data type
Details see note 2182500
( Changed at 14.09.2015 )

Size of a single document for printing
In special cases, business applications require the creation of large PDF forms containing more than 1.000 (up to 20.000) pages. Depending on the operating system, Adobe Document Services (ADS) have a technical limitation regarding the form size. When creating large documents using ADS there are limitations with regard to the maximum number of pages: See SAP Notes 1009567 and 894389 To be able to create large PDF documents, you need to implement an application-side workaround. Workaround: Stitching bundled forms to one PDF form Further information: http://help.sap.com/saphelp_nw74/helpdata/en/1f/d9bc3854564800be3a220912428288/frameset.htm
( Changed at 14.09.2015 )

Fixed Limitation(s)
BC-DB-ORA
No release
Limitation of new OpenSQL features on Oracle
See SAP note 2231924
This restriction is no longer valid.
Fixed with Kernel 7.45 PL22
( Changed at 04.11.2015 )

BC-UPG
No release
One step Upgrade & Database migration option to Hana  (SUM DMO) is not be available at RTC
With RTC of NetWeaver 7.50 the one step Upgrade & Database migration option to Hana (SUM DMO) will not be available. The support is planned for SUM SP15 Patch. Please see corresponding SAP note 2155664 for further information.
This restriction is no longer valid.
Successfully tested with SUM SP15
( Changed at 16.11.2015 )

BC-XI-IBF
No release
Dual Stack split at PI Upgrade to NW 7.50 SP00 not working
Link to Incident: https://support.wdf.sap.corp/sap/support/message/1570806497 The root cause of the issue is that the target host was reached but no process listens to the target port"sapgw00". This error can be caused by the usage of the wrong TCP-port (sometimes presented only by the instance number, e.g. "00")   or the fact that the target server is not running at the moment.
This restriction is no longer valid.
Tests have been completed successfully: Dual Stack split at PI Upgrade to NW 7.50 is now supported
( Changed at 08.12.2015 )

No comments:

Post a Comment