Upload
anandna
View
233
Download
0
Embed Size (px)
Citation preview
8/3/2019 Socm Copy Document
http://slidepdf.com/reader/full/socm-copy-document 1/7
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG
Enabling Multiple ChangeDocument Creation from SingleChange Request in SolutionManager
Applies to:
Article applies to Solution Manager functional consultants in SAP practice.
Summary This document will explain how to enable creation of multiple change documents from single change requestin SAP Solution Manager.
Author: Senthil Kumar Panneer Selvam
Company: Infosys Technologies Ltd
Created on: 20th October 2010
Author Bio
Senthil Kumar Panneer Selvam is a PP / Solution Manager functional consultant with Infosys TechnologiesLtd and has over 4.5 years of experience in SAP PP / Solution Manager module and about 9.5 years ofexperience in total. He is basically a production engineering graduate from Bharathiyar University.
8/3/2019 Socm Copy Document
http://slidepdf.com/reader/full/socm-copy-document 2/7
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG
Table of Contents Introduction ......................................................................................................................................................... 3 Procedure to Enable Multiple CD Creation ......................................................................................................... 3
Step 1: ............................................................................................................................................................. 3 Step 2: ............................................................................................................................................................. 3 Step 3: ............................................................................................................................................................. 4 Step 4: ............................................................................................................................................................. 4 Step 5: ............................................................................................................................................................. 5
Disclaimer and Liability Notice ............................................................................................................................ 7
8/3/2019 Socm Copy Document
http://slidepdf.com/reader/full/socm-copy-document 3/7
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG
Introduction
In Solution Manager change request management process (ChaRM), Only one change document can becreated from a change request as a standard functionality. In some business cases, multiple changedocuments to be created from one change request. This document will help to enable the multiple changedocument creation from a change request.
Procedure to Enable Multiple CD Creation
The subject and ibase fields in the fast entry screen are being used as a reference to create the changerequest and change document. The subject field refers the process type which needs to be created andIbase component is to identify the system landscape to which the change has to be implemented. Basicallyonce the change document is created from the change request, the subject and Ibase fields will greyed out.
In standard, by default the change document check is enabled in the change request to restrict the multiplechange document creation. If required the change document check can be disabled in the change request bychanging the action profile settings.
Step 1:
Follow the IMG path to access the action profile
SPROSAP Solution manager Scenario specific settings Service deskservice desk Define actionprofilechange actions and conditions Define action profile and action
Step 2:
Select the action profile which you have assigned to the transaction type.
8/3/2019 Socm Copy Document
http://slidepdf.com/reader/full/socm-copy-document 4/7
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG
Step 3:
Choose the action definition “Upon Release: Create Change Document”
Step 4:
Select the process type assigned for the action definition.
8/3/2019 Socm Copy Document
http://slidepdf.com/reader/full/socm-copy-document 5/7
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG
Step 5: Click on “Display” icon
8/3/2019 Socm Copy Document
http://slidepdf.com/reader/full/socm-copy-document 6/7
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG
The following pop-up will be displayed.
In the container editor check for the value “X” for the container element “CHECK”.
The value “X” is set to the container element to restrict multiple Change document creation. Toenable multiple change document creation, remove the value “X” for the container element“CHECK”.
Save the changes.
When the action is triggered, it will refer the container values. If the change document “CHECK” isnot activated, it will allow to create multiple change documents from one change request.
8/3/2019 Socm Copy Document
http://slidepdf.com/reader/full/socm-copy-document 7/7
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG
Disclaimer and Liability Notice
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.