Support Packs -JSPM

7/23/2019 Support Packs -JSPM

http://slidepdf.com/reader/full/support-packs-jspm 1/65

1

SAP NetWeaver Product Management

SAP AG 2005

Ramp-Up Knowledge TransferSAP NetWeaver 2004s:

Support PackageManagement



2

Java Modification Management

Note Assistant

Java Support Package Manager

SAP NetWeaver Support Package Stack



3

Motivation

Features

Proceedings

Summary



4

Simplify by eliminating the need to go through bulky manuals etc

Have one common tool to apply support packs instead of multiples ones (e.g

SDM, SAPinst etc)

Due to the fact that there are no version dependencies between support packs,

you are never quite sure if the new SP would work

Due to the fact that existing version information does not say if the support pack is

cumulative

© SAP AG 2005/ 4

Motivation

Simplify the process of applying support packages

Standardize the software logistics tools to use a common user

interface (SDT)

Reduce uncertainty while applying new support packages

Introduce dependencies between support packages

Reduce manual steps while applying support packages (e.g.

JSPM makes sure that only one cluster node is running)

Deployment of components delivered without sources.

Deployment of the runtime archives for unmodified components.



5

Motivation

Features

Proceedings

Summary



6

© SAP AG 2005/ 6

Features (1/4)

Support Package Level Administration

Introduce dependencies on software component level

Check if new software component version may correctly

upgrade exist ing version

Dependencies between versions of the components, not

between their names

Usability Features

Simple, intui tive user interface

Automatically detect and offer to the user only content that

will upgrade the system

Show only necessary information. Any details will bedisplayed only if requested by the user

Shares common graphical user interface with other Software

Delivery Tools applications – SAPinst, SAPJup



7

JSPM provides functionality to deploy new support packages only for SAP

components that are already installed on the system and non-SAP components

(does not matter installed or not).

Regarding SAP components (for example, the Enterprise Portal Usage Type – EP

UT)

If there is EP UT on the system, EP components will be “allowed” components.

If there is no EP on the system installed, JSPM will not “see” EP components in the INBOX and

will not suggest them for deployment.

Consistency check: Before starting the deployment, dependencies between SCAs

will be checked. This check will prevent for example to be done patch of EP,

without AS UT.

Broken deployments: There is check if deployment fails and JSPM can be

restarted and continue from the point of the error.

© SAP AG 2005/ 7

Features (2/4)

Display Features

Show support package levels

Show component patch versions

Show support packages in the INBOX

Checks

Check that only allowed packages are deployed

Check, if a planned set of SPs can consistently be deployed

Check for broken deployments

Support for Kernel Binaries and SDM

Update kernel binaries Update SDM (SAP NetWeaver 2004s)

Installation Features

Deployment of new software components



8

JSPM is a integrated part of a SAP System (Java), therefore it is a subject of

system back up and restore, as well as system copy.

© SAP AG 2005/ 8

Features (3/4)

Deploy Features

Apply a single support package

Apply a set o f support packages Apply support package stack

Inform the user if server restart will be necessary during deployment

Monitor the deployment process until it is working

Al low restarting the deployment of support packages

Manage intermediate inconsis tent states

Administrative Features

Can be backed-up/restored together wi th the whole system

Part of the system copy

Patch itself

Cooperation with NWDI

Detect modified components

Apply non-modified components



9

© SAP AG 2005/ 9

Features (4/4)

Compatibility Features

Pure Java application – no native parts

Delivered and deployed as ordinary software component

Future Integration with SLM

Remote connectiv ity for SLM

SLM validates scenarios and downloads necessary content

SLM configures JSPM

SLM calls JSPM to implement the scenario using downloaded

content

No need of manual steps during implementation of support

package or stack

Minimization of Manual Steps

Goal is to remove the need of any manual steps when

applying support packages



10

Motivation

Features

Proceedings

Summary



11

Central instance profile: <inst-

dir>/<sapsid>/SYS/profile/<SAPSID>_<CENTRAL-INSTANCE>_<HOST>

The t r anspor t di r ect or y can be a net wor k f i l e syst em. Theref or e, ensur e t hat t he <sapsid>adm user can r each t hi snet wor k di r ect or y and owns at l east read and write

per mi ssi ons f or t hi s di r ect or y.

If you start JSPM for the very first time or after an update, the working

environment (such as profiles, working directories etc.) will be generated or

updated. Therefore the startup takes a bit longer than usual.

The JSPM inbox is located under $DIR_EPS_ROOT/in

© SAP AG 2005/ 11

Starting JSPM

Configuration of the JSPM inbox in the central instance profi le

DIR_EPS_ROOT = <transport-dir>/EPS

Ensure that the path to the program sappfpar is included in theOS environment variable $PATH

Invocation restricted to the user <sapsid>adm

Start scr ipt located in the directory:

Java standalone installation:

<inst-dir>/<sapsid>/JC<instance-no>/j2ee/JSPM/

Java Add-in installation:

<inst-dir>/<sapsid>/DVEBMGS<instance-no>/j2ee/JSPM/

Script:

Windows: go.bat

Unix: go



12

For security reason, the SDM server will shut down after three failed logon

attempts. You must restart the SDM server.

© SAP AG 2005/ 12

Logging On

Provide the SDM

password



13

© SAP AG 2005/ 13

Deployed Components View



14

Configuration of tracing and logging severity in the file <inst-dir>/<sapsid>/<central-instance>/j2ee/JSPM/param/logging.properties

Trace file <inst-dir>/<sapsid>/<central-instance>/j2ee/JSPM/trc/JSPM.TRC

© SAP AG 2005/ 14

Log View



15

Deployment types:

Entire SP Stack for all usage types installed in the system

Single Support Packages of installed Software Components

New Software Component: for installation of additional applications

System types:

No NWDI control: System is not in a NWDI controlled landscape, therefore not modifiable und

extendable.

NWDI controlled Runtime systems: For modification and extension of SAP standard DEV and CONS: If the current system is a development or consolidation runtime system, JSPM updates the

unchanged software components and refuses to update the modified components. JSPM provides the SAP

standard SPs of the unchanged components to NWDI for modification adjustment.

QA and PROD: JSPM refuses the update of the current system at all, as long as the modification adjustment is

not completed.

Modified components include components whose sources has been changed and

components which are dependent on components with source changes.

High Availability system: For HA systems, the kernel binaries must be distributed to the back

up instances. (planned for NW04s SR1)

© SAP AG 2005/ 15

Specifying System and Deployment Type



16

© SAP AG 2005/ 16

Deployment: Choosing Support Packages



17

© SAP AG 2005/ 17

Deployment: Checking Status and Starting



18

JSPM is able to update itself if appropriate version of JSPM is available in the

JSPM inbox.

Appropriate version means that the version is higher than the currently deployed

one. It is an valid update of the current one.

After applying the update of JSPM, it must be restarted to continue with further

deployments.

© SAP AG 2005/ 18

Updating JSPM



19

JSPM is able to the system kernel and other OS level binaries (like IGS) of the

NW Java Application Server and distribute these parts in cluster environments.

Kernel and other OS level binaries are subsumed into the software component

sap.com/SAP KERNEL.

SDM is displayed as software component sap.com/SAP_JAVASL .

© SAP AG 2005/ 19

Updating System Kernel and SDM



20

Log view and files are the first means for troubleshooting.

INFO is the default severity for logging in JSPM.

All severity levels from INFO (inclusive) are logged automatically.

© SAP AG 2005/ 20

Troubleshooting: Log Files

Severities in ascending order:

DEBUG: Extensive and low level information that is relevant todebugging

PATH: Information that is relevant to tracing the execution f low

INFO: Execution progress

WARNING: Anomaly execution, user attention and manual

operations are necessary

ERROR: Execution interrupted due to error, deployment cannot

continue

FATAL: Fatal termination of the application



21

Log view and files are the first means for troubleshooting.



© SAP AG 2005/ 21

Troubleshooting: Log Files

Severities in ascending order:

DEBUG: Extensive and low level information that is relevant todebugging

PATH: Information that is relevant to tracing the execution f low

INFO: Execution progress

WARNING: Anomaly execution, user attention and manual

operations are necessary

ERROR: Execution interrupted due to error, deployment cannot

continue

FATAL: Fatal termination of the application



22



© SAP AG 2005/ 22

Troubleshooting: Starting Problems

User other than <sid>adm

No enough disk place available

Default GUI connection port (6240) occupied

Another JSPM instance al ready running

Default port used by another application: Change port setting/dialog/SDTServerConnection/port in<installation-dir>/<sapsid>/<central-

instance>/j2ee/JSPM/param/jspm_config.txt

Incompatible SDM version:

Noticeable during logon

Update the SDM to the version belongs to the current SP stack



23

© SAP AG 2005/ 23

Troubleshooting: Deployment Problems

No archive found in the inbox

Version of the SCA files in the inbox do not update the system (equal

or lower than the currently deployed version)

Check SMP for newer versions

J2EE administrator password wrong or expired

Change the password using UME

Update secure store with the same new password for SDM, see SAP

Note 870445

Other problems:

Memory overrun in the Java AS



24

Motivation

Features

Proceedings

Summary



25

© SAP AG 2005/ 25

Summary

J2EE support package manager can do the following

Apply Suppor t Package stacks

Apply Support Packages

Apply Suppor t Packages patches

Deploy non-SAP UT software components

Characteristics

The only tool for applying Support Packages and patches

Deployment is done via SDM currently and v ia deployment service in

future releases

Stand alone program with usage of the SDT GUI

Future integration with SLM



26


Note Assistant





27

© SAP AG 2005/ 27

Tools Used For Application of SP Stack

SPAM / SAINT: Al l ABAP Support Packages and ABAP Add-ons

JSPM: All Java Support Packages for Software Componentsrunning in the J2EE Engine

SAPinst: Some standalone engines like TREX

Different tools: i.g. ZIP



28

Stack definition files for different

© SAP AG 2005/ 28

Support Package Stack Deployment (Java)

Support Package Stack: Set of Support Packages for a particular

product version that must be used in combination

Reduction of complexity and dependency of Support Packages

Same tools and technologies for importing Support Package types

SP Stacks can be downloaded from the SAP Service Marketplaceunder the quick link /sp-stacks

Download page ordered by product versions and usage types

Only SPs of appropriate usage types need to be downloaded and

unpacked to the JSPM inbox

A s tack defini tion fi le as XML must be downloaded from the samepage and placed in the JSPM inbox

Al l SPs with required vers ions are defined in th is def in it ion f ile

Kernel and SDM patch versions are not covered by the definition fi le

Only use the kernel and SDM patch from the same stack download



29

© SAP AG 2005/ 29

Specifying Queue for Stack Update



30

A stack update can only be performed if all the packages found in the inbox fulfill

the requirements as defined in the stack definition file.

SDM update is performed first if an appropriate SDM patch version available in the

inbox.

JSPM update is performed immediately after the SDM update. After the JSPM

self-update, it must be restarted to use the updated version for further

deployments.

© SAP AG 2005/ 30

Checking Deployment Queue



31

© SAP AG 2005/ 31

More Information

Support Package Stack Guide SAP NetWeaver 2004s: SMP quick

link /maintenance2004s

Central SAP Note: 879289



32


Note Assistant





33

Installation Management

Support Package Management

Upgrade Management

Summary



34

Slide for your reference only!

© SAP AG 2005/ 34

Development Process in NWDI

CMS

DTR

CBS

Act ivation Trans por t

Check-in

Import

Ass embly Approval

Deployment

Development Consolidation Test Production



35

NWDI supports you not only on the implementation of a new SAP

system, but also on system maintenance during the operations and on

upgrading.

Appropriate conf igurat ion means:

Software components to be modified or to be developed with their required

components must be defined properly for the relevant track.

Customer’s own software components (extensions) must be defined in the

corresponding SLD (component name, release, dependencies).

Although the runtime systems for the stages of development,

consolidation and QA are optional, it is a recommended practice to

perform the tests of different development stages indedicatedsystems!

© SAP AG 2005/ 35

Installation of Systems to be Modified and Extended

Define a track in the NWDI with the appropriate configuration

You require additional development to fulfil l your business

requirements?

No problem! NWDI supports you to manage your development.

How do you proceed?

Install runtime systems as required

SAPinst will copy relevant software components to the CMS inbox

Always perform development tests, QA tests in di fferent systems

before going-live!

Perform your development and transport the changes as definedby NWDI



36

The proceeding is on ly valid for installation of SAP Systems based on SAP NetWeaver AS 2004s andhigher!

The animation illustrates the case that an SAP standard software component should be modified.Development for extensions takes place in similar way.

Installation and development steps:

1. Install the runtime systems required for the relevant track and specify the roles (DEV, CONS, TEST andPROD) of the systems in the corresponding track. SAPinst will supply the NWDI track with the relevantsoftware components (to be modified and their required underlying components) by putting them tothe inbox of CMS.

2. Specify the installed runtime systems in the previous step in the track definition accordingly.

3. Check-in and import the required software components (and the software components to bemodified with sources, if applicable).

4. Develop your extension software components or modify the SAP standard software components inNWDI as usual.

The deployments in the development and consolidation stage takes place at the level of DevelopmentComponents (DC). It means, only DCs affected by the changes (either the changed DCs and those DCswhich depend on the change DCs) will be (re-)built and (re-)deployed.

5. Assemble the software components from the consolidation stage as a whole and deploy them intothe test (QA) runtime system when the development reach a certain status for QA tests.

6. After the QA stage, you can release (by approving) the software components for productive usage.

Now you can deploy the software components into the production runtime systems.

*In order to prevent assembled or approved software components being deployed unintentionally into the testand production runtime systems, you CAN disable the import function for these two stages.

© SAP AG 2005/ 36

Installation of Systems to be Modified or Extended

CMS

DTR

CBS


Check-in

Import

Ass embly Approval

Development Consolidation Test (QA) Production

SAPinst

ive



37



Upgrade Management

Summary



38

Each SAP NetWeaver Application Server (Java) has its own Support Package

Manager (JSPM) running on it. Therefore, JSPM works with its own local directory

by default.

NWDI uses a transport directory for distributing software changes to the relevant

systems in the landscape.

In order to make JSPM and NWDI working together (means enable file exchange

between them), a common transport directory shared by NWDI and JSPM of all

relevant systems in the landscape should be used.

In NWDI, you can specify the path to the transport directory in the transport

domain definition.

For JSPM, you can specify a custom transport directory by defining profile

parameter DIR_EPS_ROOT in the instance profile of the central instance of the

Java Engine (file name <SID>_JC<instance-no.>_<HOSTNAME).

© SAP AG 2005/ 38

Transport Directory for JSPM and NWDI

NW AS Java

JSPMhost

…

…

…

NW AS Java

JSPMhost

…

…

…

host

…

…

…

NWDI

host

…

…

…



39

At tention : Deploying assembled software components archives (SCA) with

inconsistent states will very likely damage your productive environment and stop

your business operations!

To prevent improper SCAs being deployed into your test system and productive

systems unintentionally, you MUST disable the import function for these two

stages.

© SAP AG 2005/ 39

Applying Support Packages in An Environment with Modificationsand Extensions

You have to apply Support Packages to modified SAP Systems?

No problem! NWDI suppor ts you to adjust your modifications and

extensions.

How do you proceed?

Update the runtime systems for the development and consolidationstages with JSPM

JSPM will refuse to deploy the new version of modif ied components

JSPM will copy all relevant sof tware components to the CMS inbox

Check-in and adjust the modified components in the NWDI

Assemble the adjusted software components and update the QA runt imesystem with JSPM

Approve the adjusted software components for productive usage andupdate the productive runtime systems with JSPM

But on ly after exhaustive QA tests



40

This proceeding is o nly valid for SAP Systems based on SAP NetWeaver AS 2004s and higher!

The animation illustrates the adjustment of a modified software component from SAP. Adjusting custom extensions takes place in similarway.

The adjustments take place in the same track set up on installation.

Adjustment steps:

1. Update the development and consolidation runtime systems using JSPM.

JSPM will omit deploying the new version of modified software components from SAP, but will put them andtheir required underlying components to the transport directory in order to make them available for theNWDI. At this time, the modified SCs and custom extension SCs are still out-dated.

At this point in time, JSPM refuses to update the test and production runtime systems.

2. Check-in and import the new version of the modified software components and their required underlying components intothe track.

Version conflicts are likely.3. Adjust the modifications and extensions in the development stage. Once you activate the adjustment, new version of the

affected DCs (including the changed DCs and DCs depending on them) are (re-)built and deployed into the developmentruntime system.

Now the development runtime system is up-to-date.

4. Transport the changes to the consolidation stage. Perform the tasks in the consolidation stage as usual (corrections, unitand integration tests etc.). Deploy the new version of the affected DCs into the consolidation runtime system.

Now the consolidation runtime system is up-to-date.

5. Assemble the modified and extension SCs.

NWDI will put the resulting SCAs into the inbox of JSPM.

6. Update the test runtime system using JSPM. JSPM uses the new version from SAP for unmodified SCs and uses theversion produced in NWDI for modified and extension SCs.

7. After exhaustive tests, you can release (by approving) the relevant SCs and update the productive systems using JSPM.

*In order to prevent assembled or approved software components being deployed unintentionally into the test and production runtime systems,SAP strongly recommends you to disable the import function for these two stages.

© SAP AG 2005/ 40

Applying Support Packages of Modified Components

CMS

DTR

CBS


JSPM


Import

Ass embly Approval

Check-in

Deployment



41

© SAP AG 2005/ 41

Deployment Check of Modified Software Components



42

© SAP AG 2005/ 42

Deployment Results of Modified Software Components



43

© SAP AG 2005/ 43

Version Conflict on Importing Support Packages into NWDI

Import log: Step repository import

Version Graph



44

There three ways to adjust modifications:

Discarding conflicting version: The active version in the current workspace is

taken.

Discarding active version: The conflicting version overwrites the current active

version.

Merging two version manually:

1.Create a new activity

2.Compare two version in the diff-tool

3.Take changes from of the two versions

4.Check in and activate the new version

© SAP AG 2005/ 44

Version Graph and Resolving Version Conflicts

Version graph and its context menu



45

© SAP AG 2005/ 45

Diff Tool



46



Upgrade Management

Summary



47

Similar to applying Support Packages:

In the runtime systems for the development and consolidation stages, the SAP Java

Upgrade Tool (SAPJUp) updates only the software components which are not modified to the

new release and makes the new release of the modified software components with their

required underlying software components available for the new NWDI track. Modified

components and extension components are adjusted in the new track and deployed by CMS.

SAPJUp refuses to update the test runtime system and the production system as long as the

modified software components are not adjusted and assembled by NWDI. If the modified

components are assembled or approved respectively, the software component archives

(SCAs) are stored in the transport directory. SAPJUp uses the version of modified components

from the transport directory for the upgrade instead of the SAP standard ones on the delivery

CD/DVD.

© SAP AG 2005/ 47

Upgrade of Modified and Extended Systems

Similar to apply ing Support Packages

Main di fference: Structure of software components and theirdependencies might be changed

Requires a new NWDI track copied from the track for the older

release

Track Switch Upgrade



48

In the Web AS 6.40, modified and extension software components are currently

not marked as such. Therefore, SAPJUp is not able to recognize whether a

system has been modified.

The SAP Systems based on SAP Web AS 6.40 must be updated to a certain SP

Stack level which contains features supporting the modification management.

Refer to the Upgrade Guide – SAP NetWeaver 2004s: Java, downloadable under

http://service.sap.com/upgardenw2004s.

Prerequisite: Modifications in the system based on Web AS 6.40 have been done

using NWDI.

© SAP AG 2005/ 48

Upgrading SAP Web AS 6.40 to SAP NetWeaver AS 2004s

You want to upgrade your SAP System based on SAP Web AS 6.40

with modified or extension software components to a System based

on SAP NetWeaver AS 2004s.

Situation: SAP Web AS 6.40 does not support the full range of the

modification process.

Solution:

1. Update the runtime systems to SP Stack ??

2. Upgrade the NWDI system to NetWeaver AS 2004s (with NWDI).

3. In the CMS, save the track configuration used for customdevelopment based Web AS 6.40 again.

CMS marks the modified and extension components in the relevant

runtime systems as modified.

4. Upgrade the runtime systems using SAPJUp (see next slide).



49

This proceeding is only valid fo r upgrade from SAP NetWeaver 2004 to SAP NetWeaver

2004s!

The animation illustrates the adjustment of a modified software component from SAP. Adjusting

custom extensions takes place in similar way.

The adjustments take place in a new track copied from the track used for 6.40.

Adjustment steps:

1. Update the runtime systems to SAP Web AS 6.40 SP level ?? (refer to the Upgrade Guide – SAP

NetWeaver 2004s: Java for the necessary SP level) using Support Package tools for 6.40.

This step is necessary for enabling the runtime systems to mark modified software components.2. Upgrade the SAP System(s) on which NWDI is running and the NWDI building blocks running on it

to SAP NetWeaver AS 2004s using SAPJUp.

3. Save the track configuration again in order to mark the modified software components in the

runtime systems.

4. Copy the track (T1) used for modification and extension development based on Web AS 6.40 to a

new track (T2) intended for development based on NetWeaver AS 2004s.

Immediately after the track copy, T1 and T2 have exactly identical states.

(Cont. on the next slide)

© SAP AG 2005/ 49

Upgrade Systems with Modifications and Extensions

CMS

DTR

CBS


SAPJUp

NWDI 6.40

SAPJUp

NWDI based on

NW AS 2004s

T1

T2

SP toolfor Web AS 6.40

SP ?? SP ?? SP ?? SP ??

Approval

Upgraded



50



Upgrade Management

Summary



51

© SAP AG 2005/ 51

Summary

NWDI supports the full software lifecycle management

process

Automated transport management

You have got acquainted with

Installation of SAP Systems to be modi fied and extended

Support Package process for modified and extended SAP

Systems

Upgrade process of modif ied and extended SAP Systems



52


Note Assistant





53

Overview of Features

Shipment and Impacts



54

© SAP AG 2005/ 54

Software Maintenance

SAP Note: Correction of single errors

Error description

Correction instruction or workaround

Published on demand

Support Package: Collection of program correctionsand updates to a particular software component

Includes all corrections and updates within the period from thelast Support Package

Published regularly according to schedule

Support Package Stack: Set of Support Packages fora particular product version that must be used incombination

Reduction of complexity and dependency of Support Packages

Same tools and technologies for importing Support Packagetypes



55

SSCR (SAP Software Change Registration) not required when using Note

Assistant for implementing SAP Notes.

© SAP AG 2005/ 55

Note Assistant

Automated implementation of SAP Notes

Record of SAP Notes in a particular system

Implemented notes

Implementation status

Management of dependencies and relations to

Other SAP Notes (prerequisi tes)

Support Packages (validity)

Modifications

Control updates

Support Packages

Upgrades



56

© SAP AG 2005/ 56

Benefits

Less manual actions

Accelerating implementation of SAP Notes

Improving implementation quality

TCO reduction



57

Note Assistant 1.2:

Only support automated implementation of ABAP source code (insert, delete

and replace lines of source code)

Other object types must be implemented manually according to the correction

instructions in the note

Incompatible format: The SAP Note format has been extended in order

to support new object types. Therefore, SAP Notes created for Note

Assistant 2.0 are possibly unreadable by Note Assistant 1.2 and lower.

© SAP AG 2005/ 57

New Features

Extended set of object types

ABAP programs and includes

Type Groups ABAP objects (ABAP-OO): c lasses, in ter faces and local c lass

definitions

Function modules: interfaces and attributes

Screens: attributes and flow logics

Business Server Pages

MIME objects

Messages and message classes

DDIC objects are not supported by the Note Assistant

Delivery of new objects

New user interface (for instance, PDF viewer for note text)

Incompatible format of SAP Notes: Corrections created for Note Assistant 2.0 possibly cannot be implemented w ith Note Assistant 1.2



58

ABAP-OO:

SAP’s Corrections to ABAP class definition and implementation are included in

correction instructions and can be imported by the Note Assistant 2.0

Customers cannot incorporate their changes (with the split-screen editor) to the

class definition and implementation in question (on top of them) with the Note

Assistant

Correction instructions don’t include following entities:

New function groups

New BSP applications

New DDIC objects and corrections to existing DDIC objects

New database contents and corrections to existing database contents

New XSLT and corrections

Therefore, Note Assistant does not support the import of these entity types.

© SAP AG 2005/ 58

Restrictions

Unsupported actions by Note Assistant 2.0:

Inserting new function groups

Inserting new BSP applications

Inserting and correcting DDIC objects

Inserting and correcting database contents(i.e. customizing templates)

Deleting existing objects

Changing sections in ABAP-OO class definit ion and

implementation

Correcting Language-dependent texts

Inserting and correcting XSLT



59

Overview of Features

Shipment and Impacts



60

Switch to the new format of the correction instructions for releases based on SAP

BASIS 6.40 and lower will take place in Q1 2006. SAP will inform you about the

precise date via SMP pages (service.sap.com/maintenance) and Service and

Support newsletter.

SAP Note 875816: Delivers supplementary features to overcome some

inconsistencies that probably occur if Note Assistant 2.0 is imported. It must be

implemented in following releases and SP levels:

SAP BASIS 6.40 SP 13-14: The note is included in SP 15, therefore this note is valid for the SP

levels 13 and 14.SAP BASIS 7.00 SP 1-4: if it is upgraded from a lower release to 7.00.

SAP Note 853524: relevant for customers at SP level 51-54 of SAP BASIS 6.20

and they download SAP Notes from the SAP Service Marketplace. Customers

who download SAP Notes using OSS connection don’t need to implement this

note.

For up-to-date information about the transition to the new Note Assistant see SAP

Note 875986 and SMP quick link /jspm.

© SAP AG 2005/ 60

Shipment

Shipments of the Note Assistant 2.0

SAP Business Sui te 2005 / SAP NetWeaver 2004s

SAP Web AS 6.20 ~ 6.40: shipped with Suppor t Package

6.40: Support Package Stack 13 (July 25, 2005) + SAP Note 875816

6.20: Support Package 55 (End of September 2005, SAP BASIS)

Transition period for releases 6.20 ~ 6.40: from now to Q1 2006

Delivery of SAP Notes in the new format: as of Q1 2006

From this point in time, all features are enabled for creatingcorrection instructions.

Customers who omi t applying the corresponding Support Packages

or additional SAP Notes will probably have increased manualimplementation effort or even won’t be able to implement new SAP

Notes



61

© SAP AG 2005/ 61

Two Formats in One SAP Note

In order to meet the requirements of using one single note for an

error correction instead of using two dif ferent notes for different

versions of the Note Assistant

New SAP Notes must contain two different formats of the

correction instructions for the different NA versions

Format used by Note Assistant 1.2 and lower: Contains only sourcecode correction

Format used by Note Assistant 2.0: XML-based and contains the

extended object set

Note Assistant 2.0 considers the previously downloaded SAP Notes

with the format 1.2 incomplete

A certain mechanism is required to overcome poss ible

inconsistencies after system update or upgrade to a SP level with

the Note Assistant 2.0 SAP Notes 875816 and 853524



62

© SAP AG 2005/ 62

SAP Notes with Changes to Source Code only

Bug fix requiring only source code changes

Only one note required

Valid for all releases

Can be implemented using older versions of the Note Assistant



63

From Q1 2006 for SAP Systems based on SAP BASIS 6.20 and h igher :

If you have already applied the appropriate Support Packages, you are able to

implement all SAP Notes including new features with the Note Assistant 2.0.

If you omit the appropriate Support Packages, the old Note Assistant will only

implement the part of a SAP Note for source code changes. The other part wi th

non-source changes must be implemented manually. The manual steps are

described in the note. However, this proceeding leads to inconvenience with the

modification adjustment (SPAU) when you update/upgrade the system to versions

or SP levels with the new Note Assistant later (after Q1 2006).

© SAP AG 2005/ 63

SAP Notes with non-source Code Changes

Bug fix including changes to other repository objecttypes:

Automated implementation only possib le wi th Note Assistant 2.0

During the transition period: SAP will create SAP Notes using new

functionalities, only if

The SAP Notes concerns all product releases, and

The concerned correction is only possible with new funct ions

Limited number of SAP Notes in new format

From Q1 2006:

No limitation for creating SAP Notes using new funct ionalities

Expectation: Increased number of SAP Notes using newfunctionalities

Increased manual implementation effort if not using the Note Assistant 2.0



64

© SAP AG 2005/ 64

Summary

Note Assistant 2.0 provides an enhanced set of functions forautomated SAP Note implementation support

SAP Systems based on SAP BASIS 6.20 and 6.40 must importthe following Support Packages before the end of the transitionperiod (Q1 2006) in order to be able to implement SAP Notescontaining the new features

6.20: Support Package 55

6.40: Support Package Stack 13

For up-to-date information about Note Assistant 2.0, see SAP Note

875986 and service.sap.com/jspm



© SAP AG 2005/ 65

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 informationcontained 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.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. All other product and service names mentionedare the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose

without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intendedstrategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product

strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,

links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limitedto the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of

these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of

hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Webpages.

Copyright 2005 SAP AG. All Rights Reserved

Documents

Support Packs -JSPM