Upload
deco-estrela
View
75
Download
0
Embed Size (px)
Citation preview
28.06.2013 Page 1 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
Note Language: English Version: 43 Validity: Valid Since 28.06.2013
Summary
SymptomThis note is the central correction note of SAP Solution Manager 7.1, areaChange Request Management, Support Package (SP) 7.
This note is necessary to guarantee the basic functions of your ChangeRequest Management in SAP Solution Manager. It is a composite note that islinked to additional notes. It is expanded and updated regularly.
Other termsChange Request Management Basic Configuration, Change Request Managementbasic configuration, Solution Manager
Reason and Prerequisites
SolutionYou should implement this note by default using the SAP Solution Managerconfiguration (SOLMAN_SETUP).
When you implement this note, the system does not automatically take intoaccount whether there are newer versions of required notes that havealready been implemented in the SAP Support Portal.
To ensure that all prerequisite notes are implemented in the currentversion, call the Note Assistant (transaction SNOTE), choose "Goto ->SAPNote Browser -> Execute (F8)", and then choose "Download Latest Version ofSAP Notes" in the application toolbar.As a result, when you implement this note using the Note Assistant, thesystem checks whether the necessary notes have been implementedsuccessfully. If this is not the case, the Note Assistant implements thelatest version.
This note is divided into three sections:
1) Corrections with manual steps
2) Additional information (notes for managed systems, FAQ notesgeneral notes)
3) Notes that can be implemented automatically
The "Date" column contains the day on which the listed note was included inthis note, or when a relevant change was made. Go through the notes in thespecified order (from top to bottom). Page
All of the notes are listed again under "Related Notes".
######################################################################1) Corrections with manual steps######################################################################
28.06.2013 Page 2 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
The notes of this section are divided into three groups:
1.a) Notes that you must implement manually using SNOTE. The reasonfor this may be, for example, that manual pre-implementation stepsare required or that the note requires a large amount of memoryspace.
1.b) Notes for which you must still carry out manual activitiesafter you implement the central correction note
1.c) Notes whose manual steps can be carried out automaticallyusing postprocessing in the SAP Solution Manager configuration(SOLMAN_SETUP -> System Preparation -> 3. Implement SAP Note ->Post-Process)Alternatively, execute the function module AGS_SISE_MANU_NOTE_ACTSin the Function Builder (transaction SE37) after you implement thecentral correction note. Ensure that you carry out thesepostprocessing steps in the work client.
The category indicates the type of manual activity. Possible values:
o A = Mandatory; you must carry this out.
o B = Optional, if required (for example, error message texts,starting reports manually)
1.a)
24.09.2012
Category Note number Short text (may be abridged)A 1764423 Problems and Knowledge articles not addable in IMGactivity
03.12.2012
Category Note number Short text (may be abridged)A 1792703 Preliminary Import - error message stays afterrecheck
06.12.2012
Category Note number Short text (may be abridged)A 1741751 ChaRM: new remote infrastructure without domain link
31.01.2013
Category Note number Short text (may be abridged)B 1575201 Approval Procedure activities missing
23.02.2013
28.06.2013 Page 3 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
Category Note number Short text (may be abridged)A 1749036 Message: Enter a valid partner ID for all approvalsteps
Category Note number Short text (may be abridged)B 1821188 Numbered User status not filtered in the Status Ass.Block
02.05.2013
Category Note number Short text (may be abridged)A 1830403 Genehmigungsschema Änderungsantrag wird nichtinitialisiert
Category Note number Short text (may be abridged)A 1749355 UI object status control and performanceenhancement
03.06.2013
Category Note number Short text (may be abridged)A 1855399 ChaRM: input invalid component value manually causedump
1.b)
12.10.2012
Category Note number Short text (may be abridged)B 1772445 BadI definition for 'Create Transport Request'
23.01.2013
Category Note number Short text (may be abridged)A 1749036 Message: Enter a valid partner ID for all approvalsteps
21.06.2013
Category Note number Short text (may be abridged)B 1865128 Error msg (COPY_ALL) parameter &1 is not replaced
28.06.2013
Category Note number Short text (may be abridged)A 1724697 Authorities for UI objects in the assignment blocks
######################################################################2) Additional information (notes for managed systems, FAQ notes, generalnotes)######################################################################
28.06.2013 Page 4 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
Implement the following notes in the managed systems:
Pease refer to note 1703391 'General note for managed systems in ChangeManagement'. There you find the overview of notes which need to beimplemented in the managed system.
FAQ notes
13.07.20111609210 SAP GUI and Internet Explorer browser settings
######################################################################3) Corrections that can be implemented automatically######################################################################
In this section, you can see the list of notes that can be implementedautomatically and that are implemented with this central correction note.
20.07.20121738132 (SAP_BASIS)
04.09.201217606221724926175850317520501758131 (BBPCRM)
10.09.2012176207217486391761128
24.09.2012170062317282841763981 (SAP_BASIS)176207217037901767522
26.09.20121758387
04.10.2012176681017658051764241176047917560141752050
12.10.2012177414017641311774781
02.11.2012
28.06.2013 Page 5 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
177027417660991632706
08.11.2012163270617702741779871177987117400831778184
12.11.20121759644177830717789671772052177205217710791782398
26.11.20121729753178946417866801716051
03.12.201217930341792366178941317918241584174179270317421701740552
06.12.20121741751 (SAP_BASIS)
14.12.201217967651788357
21.12.201217663011800300
07.01.2013180318717960631767233180318512838361728284180033817978881803170
28.06.2013 Page 6 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
18.01.2013180786017246971786704
21.01.20131705702
23.01.20131238530174903617993721742801
30.01.2013180587818075311641712
31.01.2013181253418032631810403181031018098831808936
07.02.2013171000917259951810064
23.02.201317490361818374158969018211881772445
04.03.2013181837417867041766810181986317883571779871
11.03.20131830816
22.03.201318376511836519
04.04.20131743385
28.06.2013 Page 7 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
19.04.20131835375183299318375841836960183299318293631722467
02.05.20131445181184334818519501830403181832517870621850681
17.05.201318537671854177185906018590611856307
24.05.20131847006185606318476141854780
03.06.201318638261060987186727318650251267123186003718553991745969
21.06.201318638141854827185564518654321835997
28.06.2013172246718658171868414182079618186281870267186373718785771865294
28.06.2013 Page 8 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
Header Data
Release Status: Released for CustomerReleased on: 28.06.2013 14:11:52Master Language: EnglishPriority: Correction with high priorityCategory: Program errorPrimary Component: SV-SMG-CM Change Request Management
Valid Releases
Software Component Release FromRelease
ToRelease
andSubsequent
ST 702 710 710
Related Notes
Number Short Text
1878577 Change Request Management Change Document is not AET usable
1870267 ChaRM: performance improvements when closing task list
1868414 Request for Change: Dump SAPSQL_ARRAY_INSERT_DUPREC
1867273 ChaRM: "Delta Errors" in tracking monitor shows irrelevant t
1865817 CSOL/DGP: Unnecessary lock entries occupying space
1865432 Fehler bei Konsistenzprüfungen im ChaRM sind nicht sichtbar
1865294 ChaRM Report: All Solution-Rel.RfCs Shown Not Structure-Rel.
1865025 Retrofit: empty Change ID in Retrofit screen for transports
1863826 ChaRM: cannot create ToC due to exist empty released task
1863814 Incorrect iBAse Compnent inherited by Change Doc from RFC
1863737 QGM: It takes minutes to open the risk tab page
1860037 ChaRM&QGM: number of risk is not correct
1859061 ChaRM: transport request type is wrong in risk overview
1859060 ChaRM: non-imported ToC risk only for the first QAS system
1856307 Genehmigungsstatus wird nicht korrekt zurückgesetzt
1856063 ChaRM: Check organization unit BP for critical object
1855645 ChaRM: error reassigning with target group in other domain
1855399 ChaRM: input invalid component value manually cause dump
1854827 Documents do not allow CRM email integration
1854780 DGP: ignored conflicts become open after checking
1854177 ChaRM: Status-dependent import job does not work
1853767 Wartungszyklus wird nicht entsperrt nach Anlage Korrektur
1851950 ChaRM: IBase component description is displayed incorrectly
1850681 QGM: no IBase for system/client when create change
1847614 ChaRM: cannot import ToC into QAS with QGM integration
1847006 Performance Improvement when linking documents & task list
1843348 ChaRM: BSP error when create transport request or task
28.06.2013 Page 9 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
Number Short Text
1837651 Possible double entries in IMG activity F4 help
1837584 DGP: Assignment of non-ABAP transport requests are blocked
1836960 ChaRM: only main partner can be searched in CRM Web UI
1836519 Change Transactions dump with Time Recording
1835997 Error in Approve critical objects button field control
1835375 CSOL/DGP: Performance improvement dumps with big data
1832993 CSOL: long SID systems cannot be managed in /TMWFLOW/CMSCONF
1830816 Runtime error: ASSERTION_FAILED in SAPLCRM_ORDER_API
1829363 Create from template dumps in request for change
1821188 Numbered User status not filtered in the Status Ass. Block
1820796 Dump in Charm_Check Functionality if too many messages
1819863 Test plan not found in test management F4 help : Charm
1818628 Retrofit Conflict Calculation
1818374 ChaRM: BSP error when click Transport Management block
1818325 CSOL: Deletion in Lock Monitor deletes extra records
1812534 ChaRM: runtime error when click cancel button in CRM Web UI
1810064 Approved at date and time not cleared with extend scope
1807860 Dialog box for item selection appears for follow-on doc (CD)
1807531 SolMan Web Dynpro application log displays non-local time
1805878 CSOL/DGP: Conflict check performance improvement
1803263 ChaRM: Assign TR doesn't work well in multi track project
1803187 ChaRM: show task information directly after selecting one TR
1803185 ChaRM: change document cannot be created for non-ABAP system
1800300 ChaRM: CRM_SOCM_SERVICE_REPORT does not work
1799372 Bei Zurücksetzen v Status bleibt Genehm.verfhrn geschlossen
1796765 CSOL/DGP: cross-transport domain support
1796063 Retrofit: problem of workbench object in customizing request
1792703 Preliminary Import - error message stays after recheck
1791824 QGM: runtime error occurs when reassign transport request
1789464 Approving critical objects not allowed as change manager
1789413 Domain controller error for non-ABAP systems in ChaRM check
1788357 DGP: import check reports extraneous overtaker conflicts
1787062 ChaRM: project ID is incorrect in search result of cycles
1786704 ChaRM: problem of schedule import jobs out of ChaRM
1786680 Transport to Sandbox Error if several tracks in Project
1782398 QGM: insert or change in a sorted table error when do import
1779871 ChaRM/QGM: Status of TR displays wrong on QGM side
1778967 ChaRM:Project ID not shown in change document search result
1778307 ChaRM: reassigning urgent change to other project fails
1778184 Solution context Assignment not copied : RFC
1774781 External reference number is not copied
1774140 Performance Enhancement in the Change Request Framework
1772445 BadI definition for 'Create Transport Request' window
1772052 Retrofit: auto-import failed with return code 0152
1771079 ChaRM: BO link creation error in reassignment report
28.06.2013 Page 10 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
Number Short Text
1770274 Approval Procedure won't be locked after intial save
1767522 Issues generating change documents with CTS+ non-ABAP system
1767233 ChaRM: approval error about CRM_SSC_INIT_SCREEN_DATA
1766810 ChaRM: project transaction is not created for old cycle type
1766099 SAP Notes are not copied from RfC to Change Document
1765805 ChaRM: transport tracking information inconsistency
1764423 Problems and Knowledge articles not addable in IMG activity
1764241 ChaRM: action CLEAR_EMPTY cannot delete non-ABAP requests
1764131 CSOL/DGP: no results for open TRs after cycle-switch
1763981 View BCOS_CUST has bad column texts
1762072 Status Reset with administr. in scope for dev/test system
1761128 Project Reassignment won't return change cycles
1760479 Urgent Change: incorrect error message for release check
1760097 Create Incident followup authority issue for RFC f4
1759644 Transport to Sandbox dropdown list box has wrong values
1758503 ChaRM: button of assignment block non-effective in Web UI
1758387 CSOL: lock monitor cannot filter by customizing lock keys
1758131 Endless loop in CRM_DOC_FLOW_SAVE_OB
1756014 Harmonizing RFC communication infrastructure for ChaRM Check
1752050 ChaRM & QGM: maintenance cycle Phase or QGate shift issue
1749355 UI object status control and performance enhancement
1749036 Message: Enter a valid partner ID for all approval steps
1748639 ChaRM: request is not kept in queue after preliminary import
1745969 ChaRM: cannot correct import for transport request
1743385 ChaRM: Support wildcards usage for status driven import
1742801 CSOL: low performance dealing with large customizing TR
1742170 ChaRM: fix regression bug in transport area
1741751 ChaRM: new remote infrastructure without domain link
1740552 ChaRM & QGM: CTS+ Web Browser display error for non-ABAP TR
1740083 ChaRM: Performance Improvement for 7.1 SP05 and afterwards
1738132 Inheritance change causes deletion of method implementations
1728284 ITSM: Partner Functions for the WebClient UI
1725995 Wrong system client default in transport request creation
1724926 Enhanced Retrofit: Sequence Dependency Check does not work
1724697 Authorities for UI objects in the assignment blocks
1722467 Assignment blocks not accessible in Charm / Change documents
1716051 ChaRM: preliminary import doesn't work for 3-tier landscape
1710009 Category Links are not copied to schema's new version
1705702 ChaRM: No result when searching iBase for change document
1703790 When status is reset approval procedure stays closed
1700623 ChaRM: Issues with Document assignment block
1641712 ChaRM: transaction type specific UI configuration subtype
1632706 Service Process BUS2000116 triggers Subject Profile error
1589690 ChaRM: Request is imported even authentication fail
1584174 CSOL: RFC to client 000 is required for activation
28.06.2013 Page 11 of 11
SAP Note 1726917 - Master Note for Change RequestManagement 7.10, SP7
Number Short Text
1575201 Request for Change: Approval Procedure activities missing
1509091 QGM: General note for Quality Gate Management 7.1
1445181 ChaRM: critical object check with program ID R3TR
1283836 Work Center: Change Management performance improvements
1267123 System remains in SAFE mode after update
1238530 Work Center: Wrong transaction opened from transaction list
1060987 Copy of multiple documents in the change request
Correction Instructions
CorrectionInstructions
Validfrom
Validto
SoftwareComponent
Type*)
ReferenceCorrection
LastChanged
1133516 710 710 ST C SD7K087822 28.06.201310:27:43
*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work