LESSON OVERVIEW
In this lesson, you will learn how to process multiple objects in a single change request, schedule changes using editions, and process multiple objects.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Process multiple objects in a single change request
● Schedule changes using editions
● Process multiple objects
Different Types of Change Requests
Figure 23: Categories of Change Request Types
There are three categories of change requests in Financials:
● Single object change requests that use a special workflow
● Multiple object change requests that include multiple object types
● Form-based change requests used only for single-object maintenance Characteristics of Change Request Types
In Financials, the change request type is a central element of the Master Data Governance process. Change request types are linked to edition types and are a single-object type. The
based template is used as an entity type, assign the template in the change request type for each entity type. Each entity type can have its own template. SAP delivers several change request types with predefined, form-based templates.
Editions with Assigned Object Changes
Figure 24: Editions with Assigned Object Changes
Change requests describe the business rationale for changing master data and control the approval and change process.
For master data that is maintained through the use of editions, first create an edition, then assign each change request to the specific edition. Multiple change requests can be assigned to a single edition.
When all change requests for an edition are approved or withdrawn, the edition as a whole can be released and no further change requests can be created. Data replication to local systems can be triggered either by the approval of a single change request or the entire edition.
Lesson: Processing Multiple Objects in a Single Change Request
Characteristics of Editions
Figure 25: Characteristics of Editions
An edition can be described as a container that stores the master data in change requests for a specified period of time. Editions are distributed using the Distribution Monitor, which propagates the master data to their target systems. Assign the change requests to an edition.
Edition Type Rules
Figure 26: Edition Type Rules
An edition type restricts the list of entity types for which master data may be requested. An edition type can include some or all of the entity types in the data model, but must contain at least one entity type.
Edition Elements and Options
● Technical edition name
● Description
● Edition type
● Validity dates
● Comments
● Immediate Distribute Change Requests
If you use the Immediately Distribute Change Requests option, the change requests are distributed automatically upon their final approval. This option eliminates the need to release and distribute the edition.
Edition Distribution Monitor
Figure 27: Edition Distribution Monitor
Before you can replicate data, set the appropriate options during the customizing process.
You can control the replication process from the Distribution Monitor. The Distribution Monitor lets you replicate previously released editions.
How to Schedule Changes using Editions
Your company is in the CD manufacturing business and wants to open up a new sales office in the beautiful city of Montreal, Canada by the middle of next month. You know that you need at least one cost center ready so that all expenses can be booked correctly.
1. Create an edition using the data in the following table.
Field Value
Edition CC_Mon_##
Lesson: Processing Multiple Objects in a Single Change Request
Field Value
Description New Cost Montreal Cost Center
Type Cost Center in Data Model 0G
Valid From (Period/Year) The 15th of next month
a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC.
b) Choose Enter.
c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc.
d) On the SAP Business Client screen, on the Workcenter toolbar, choose Financials Master Data Governance.
e) In the navigation panel, choose Editions → Create Editions.
f) On the Create Edition screen, enter the data from the table.
g) Choose Save.
h) Choose Close.
2. Create a new change request and change the standard data model to 0G.
a) In the navigation panel, choose Change Request → Create Change Request.
b) On the Create Change Request: Step 1 (General Data) screen, choose Change Model.
c) On the Change Model screen, in the Standard Data Model drop-down menu, choose 0G.
d) Choose Save and Apply.
3. Enter the data for the new change request using the data in the following table.
Screen Name Field Value
Create Change Request:
Step 1 (General Data)
Description New Montreal Sales Office
##
Create Change Request:
Step 1 (General Data)
Type Cost Center - Single
Processing
Step 2 (Reason for Change)
Explanation New Sales Cost Center for Montreal
Create Change Request:
Step 3 (Changes)
Cost Center Category 3
Screen Name Field Value
Description (short) Montreal Sales Office ##
a) On the Create Change Request: Step 1 (General Data) screen, enter the data from the table.
b) Choose Next.
c) On the Create Change Request: Step 2 (Reason for Change) screen, enter the data from the table.
d) Choose Next.
e) On the Create Change Request: Step 3 (Changes) screen, enter the data from the table.
f) Choose Next.
g) In the Warning in Consistency Check dialog box, choose Save.
h) On the Create Change Request: Step 4 (Check and Submit) screen, choose Submit.
i) Choose Close.
4. Approve the change request.
a) In the navigation panel, choose Change Requests → My Change Requests.
b) On the My Change Requests screen, choose New Montreal Sales Office ##.
c) Choose Finalize Processing.
d) Choose Close to return to the My Change Requests screen.
e) On the My Change Requests screen, choose Refresh.
f) Choose New Montreal Sales Office ##.
g) Choose Approve.
h) In the Confirmation Prompt dialog box, choose Yes.
i) Choose Close to return to the My Change Requests screen.
j) On the My Change Requests screen, choose Refresh.
k) Choose Close.
Lesson: Processing Multiple Objects in a Single Change Request
Types of Change Requests for Financials
Figure 28: Categories of Financial Change Requests
The change request type is a central element of the Financials process. Change request types are linked to edition types, which means that the entity types that can be used in the change request type depend on the contents of the edition type. Each entity type can have its own template. If a form-based template is used, it is required that you assign the template for each entity type. Several single-object change request types with predefined form-based templates are available.
The following three change request types are available:
● Single-object—uses a special workflow template
● Multiple-object—includes multiple object types
● Form-based—uses predefined templates solely for single-object maintenance One-Step and Two-Step Object Change Request Types for Financials Single Object Change Request Type and Two-Step Change Request Type
● Single object change request type
- In the configuration settings, check Single Object.
- Use with simple workflow template WS75700040.
- In the UI, create change requests and maintain changes to be made.
● Two-step change request type
- In the configuration settings, check Objects Required.
- Use with advanced workflow template WS75700027.
- In the UI, create change requests, specified objects (entity type to be changed), and maintain changes to be made.
1. Specify the object or objects within a workflow that must change.
2. Execute the changes on an individual object level or on the overall change request level.
You can select the Single Object checkbox for either workflow type, but usually only applies to the simple workflow templates. This option requires only a single step because the simple workflow already contains approval for the changes to the objects within it.
If you select the Objects Required checkbox, the change request requires two steps because you will have to specify the individual objects in the change request before the changes can be made. Use the workflow template for advanced workflow templates for this type of change request.
How to Maintain Account Detail for Cost Center Change Request
For the demonstration steps and data, see the exercise Assign New Cost Center Change Requests to an Edition.
How to Release an Edition
In this demonstration, when values include ##, replace the characters with your group number.
1. Verify the change request CC_MON_## is available in the edition.
a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC.
b) Choose Enter.
c) On the Launch NetWeaver Business Client screen, choose /nwbc.
d) On the SAP Business Client screen, on the Workcenter toolbar, choose Financial Master Data Governance.
e) In the navigation panel, choose Editions.
f) On the Editions screen, on the All tab, in the results table, select CC_MON_##.
g) Choose Run Validation.
h) Choose Validation Log.
i) On the All tab, choose Change Status → Mark for Release.
j) Choose Change Status → Release.
How to Distribute a Change Request for Financials
In this demonstration, when values include ##, replace the characters with your group number.
1. Distribute the released edition.
Lesson: Processing Multiple Objects in a Single Change Request
a) In the Financials Master Data Governance Workcenter, in the navigation panel, choose Distribution Monitor.
b) On the All tab, choose CC_MON_## → Cost Center 3000##.
c) Choose Replicate.
d) Choose Refresh.
2. Verify the 3000## cost center is active.
a) In the Financials Master Data Governance Workcenter, in the navigation panel, choose Change Requests → Entity Search.
b) On the Search for Entities screen, in the Entity Type drop-down menu, choose Cost Center.
c) In the Search Criteria table, choose Edition as the search attribute and CC_MON_## as the search value.
d) Choose Search.
e) In the search results table, find Cost Center 3000##.
f) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.