Escolar Documentos
Profissional Documentos
Cultura Documentos
Description
Confidential
SAP releases enhancements/service packs in the form of SAP Notes. These notes are available on the
SAP Web site. Once downloaded the required SAP Note can be applied to the Development / Quality /
Production Landscape (Tcode SNOTE). The BASIS Support team validates the SAP Notes to be applied.
The validated Notes are applied by the BASIS Support team on the Development client and a request is
generated for transporting the upgrades first to Quality and there from to the Production client.
1.1
An L2 Helpdesk team member of the BASIS Support team shall access the SAP web site, identify the
required Notes and validate the details made available by the requester, check the compatibility of the
Notes with the Development, Quality and Production Landscapes of the SAP Application/s on which the
Notes need to be applied. Issues, if any, are recorded and the request is returned to the requester for
resolution.
1.2
The L2 team member of BASIS Support team shall apply the notes in the Development landscape
release for testing by the ABAP team. Corresponding Transport Kit created automatically shall be
retained.
1.3
Based on the feedback from the ABAP team, the application of notes shall be withdrawn or the
Transport Kit shall be attached to the Program Change Request part of the identified Solman ticket for
their application in Quality Landscape and subsequently to the Production Landscape.
1.4
As and when the Transport pertaining to Notes application for the Quality and Production Landscapes
are received, they shall be applied by the identified L1 team member as per the set procedure (refer
CRM_DNO_MONITOR-Transports to Quality/Production).
2.0
Schedule of Authority
2.1
2.2
2.3
3.0
Prerequisites
3.1 Appropriate SNOTE authorization to the L2 team member for each of the SAP Development
application/s.
3.2 Access to the SAP Support site for review and application of Notes.
December 2007
1
Confidential
December 2007
2
Confidential
December 2007
3
Confidential
Responsibility
Escalation
(if any)
Escalation
Window
6.1
L2 Team member
L2 Team lead
Real Time
6.2
L2 Team member
L2 Team lead
Real Time
December 2007
4
Confidential
Processing Steps
6.1
6.1.1
Obtain the details of the Notes to be applied by accessing the SA Support web site.
6.1.2
Study the note and obtain the details with respect to the Service Pack level requirements and
dependence on other notes (if any).
6.1.3
Logon to the Development Landscape of each of the Application/s where the Notes need to be
applied.
6.1.4
Using the T Code SPAM (refer to steps 6.4.1.1 to 6.4.1.2 of SAP-Client Administration for details),
obtain the details of the Service Pack levels and SAP Notes details from the Development
Landscape.
6.1.5
Check the Service Pack Level and status of the dependence notes requirements compiled in step
6.1.2 with the details complied in step 6.1.4.
6.1.6
6.1.6.1
6.1.6.2
6.1.7
Open an entry in the SNOTE-SAP Notes Application Control Log for each of the Notes and SAP
Application concerned and update the details for the Development Landscape.
6.1.8
6.1.9
6.1.9.1
Update the SNOTE-SAP Notes Application Control Log for successful completion in the
Development Landscape.
6.1.10
Otherwise,
Await the receipt of workflow email for promoting the notes application to Quality landscape
6.1.12
6.1.13
6.1.13.1 Identify the entry for the Note concerned in the SNOTE-SAP Notes Application Control Log and
update the details for successful completion in the Quality Landscape.
6.1.14
else
6.1.14.1 Report and escalate the problem to the ABAP team concerned.
6.1.14.2 Identify the entry for the Note concerned in the SNOTE-SAP Notes Application Control Log and
update the details for unsuccessful completion in the Quality Landscape.
6.1.14.3 Discontinue application of the notes.
6.1.15
Await the receipt of workflow email for promoting the notes application to Production Landscape
6.1.16
December 2007
5
Confidential
Identify the entry for the Note concerned in the SNOTE-SAP Notes Application Control Log and
update the details for successful completion in the the Production Landscape.
6.1.18
Otherwise,
December 2007
6
Confidential
6.2
6.2.1
Logon to the Development Landscape of SAP Application concerned and initiate the T Code SNOTE.
6.2.2
Select the menu item Goto and click on the Download SAP Note option.
6.2.3
Enter the Note Number in the box and click on the Execute button.
December 2007
7
Confidential
6.2.4
Check for an entry in the SAP Notes/Inconsistent for the Note number to be downloaded,
6.2.4.1
6.2.5
Place the cursor on the entry for the Note number to be downloaded in the SAP Notes/New.
6.2.5.1
6.2.6
Confirm that the details of the notes have been read and understood by clicking on the Yes button.
December 2007
8
Confidential
6.2.7
6.2.8
In the popup window Prompt for transportable Workbench request, click on the Create Request
button.
December 2007
9
Confidential
6.2.9
Enter Short Description for the transport request (include the Note number in the Short Description)
and click on the Save button.
6.2.10
Enter Short Description for the transport request (include the Note number in the Short Description)
and click on the Save button.
December 2007
10
Confidential
6.2.11
List of object to be changed will be displayed. Confirm changes by clicking on the Continue button.
6.2.12
In the confirmation screen for the changes carried out, click on the Continue button.
December 2007
11
Confidential
6.2.13
In the Note Assistant screen notice that the entry for the note has moved from the SAP
Notes/New to the SAP Notes/In Processing.
6.2.14
Go to step 6.1.7.
December 2007
12
Confidential
SAP Note
Identity
SAP Note 1
SAP Note 2
SAP
Application
Identity (App)
Development Landscape
Applied Result &
Date
by
Remarks
Quality Landscape
Applied Result &
Date
by
Remarks
Production Landscape
Applied
Result &
Date
by
Remarks
App 1.1
App 1.2
--App 1.a
App 2.1
App 2.2
--App 2.b
---
SAP Note n
App n.1
App n.2
--App n.c
8.0
Process Linkages
8.1 CRM_DNO_MONITOR-Transports to Quality/Production (refer steps 6.1.11, 6.1.15).
9.0
Description
The SAP Note has been loaded into the system, but not yet
processed. At this stage the Note is yet to take effect.
The Sap Note is being processed. At this stage the Note has
taken effect. At this stage, the implementer has the choice of
withdrawing the Note.
The SAP Note has been confirmed by the implementer after
the same has been processed.
Note: Once the SAP Note has been confirmed, it can not be
withdrawn.
December 2007
13
Confidential
The SAP Note has been analyzed and classified as Not
Relevant to the SAP Applications landscape concerned.
Implementation Status
If an SAP Note contains correction instructions, the implementation status indicates
whether all the relevant correction instructions in the note have been implemented in the
system.
The system sets the implementation status automatically. It can have the following values:
Processing Status
Incompletely implemented
Can be implemented
Implemented completely
Cannot be implemented
Obsolete
9.2
Description
Not all the relevant correction instructions have been
implemented, or some correction instructions have
only been partly implemented. The objects that need
to be corrected are inconsistent.
Such implementation needs to be investigated and if
required, the SAP Note needs to be reapplied.
The SAP Note applied earlier has been modified by
SAP due to errors. Such SAP Note needs to be
analyzed and if required, the SAP Note needs to be
reapplied using the latest version of the SAP Note.
The SAP Note contains correction instructions that can
be implemented.
The corrections in the SAP Note have been
implemented completely. No action is required.
The SAP Note does not contain any correction
instructions that can be implemented. No action is
required.
After an SAP Note has been implemented, a Support
Package containing corrections pertaining to the SAP
Note is marked obsolete and informed during the
support upgrade.
Output(s)
9.2.1 Transport Kit for the notes to be promoted to Quality/Production Landscapes.
December 2007
14