Customizing Navigation for Change Request

Steps in the User Interface for Single-Object

Processing

Enter Title (Via Document Properties)

TABLE OF CONTENTS
BUSINESS SCENARIO .................................................................................................................................... 3
PREREQUISITE ................................................................................................................................................ 3
Create a Custom Change Request Type Copy Change Request Types: SFC01 and SFC02................. 4
Maintain the Processors for the Change Requests ..................................................................................... 5
CUSTOMIZE NAVIGATION .............................................................................................................................. 6
UI BEHAVIOUR................................................................................................................................................. 7
Creation of an Airline with Change Request Type Z_SFC01 ....................................................................... 7
Change with Change Request type Z_SFC02 ............................................................................................... 8

Enter Title (Via Document Properties)

BUSINESS SCENARIO
During Single Object Processing, you want to define different User Interfaces for individual Change Request
steps. For example, in a Supplier Scenario you might want one step to make the general data visible, and, in
another step you might want only the purchasing organization data to be visible.
PREREQUISITE
We use the application configuration that is created in the document Configuration and Enhancement of SAP
Master Data Governance -> Financial Data -> Creating a UI Configuration and Integrating it with the MDG
Communicator.
The technical components are as follows:
Web Dynpro Application: USMD_OVP_GEN
Application configuration: Z_USMD_SF_OVP_CARR_CP
In this configuration, the UIBB for Attachments is deleted.

Enter Title (Via Document Properties)

The following customizing activities are used in this example (Transaction MDGIMG):
General Settings -> Process Modeling -> Create Change Request Type
General Settings -> Process Modeling -> Configure Properties of Change Request Step

Create a Custom Change Request Type Copy Change Request Types: SFC01 and SFC02
In this example, we use customizing activity Create Change Request Type to copy change request type
SFC01 to Z_SFC01 and SFC02 to Z_SFC02.

Enter Title (Via Document Properties)

Maintain the Processors for the Change Requests

Use customizing activity Assign Processor to Change Request Step Number (Simple Workflow) to assign
processors to the change request steps.

Enter Title (Via Document Properties)

CUSTOMIZE NAVIGATION
Use the customizing activity Configure Properties of Change Request Step to customize change request
steps for a specific change request type.

During the creation of an airline using Change Request type Z_SFC01, we want to use the configuration
without an attachment UIBB in the draft step (00).

During the change of an airline with Change Request type Z_SFC02, we want to use the configuration
without an attachment UIBB in the processing step (01).

Enter Title (Via Document Properties)

UI BEHAVIOUR
Creation of an Airline with Change Request Type Z_SFC01
Using the role MDG Custom Objects - Flight Data Model (SAP_MDGX_FND_SAMPLE_SF_04), you create a
new Airline from the Search Screen. You use the change request type Z_SFC01.

After choosing the correct change request type, the UI cofigured for the initial step displays. No Attachments
section is visible.

Enter Title (Via Document Properties)

Now search for the newly created airline and click the icon for Pending Change Requests.

In the processing step (step 01) of this change request type, the Attachments section (attachment UIBB) is
visible again, as configured.

Change with Change Request Type Z_SFC02

For navigation into active data, navigation that depends on the change request step is not possible because
no change request type is known at this point in time. When the change request is saved as a draft later on,
the system considers navigation that depends on the change request step.

Enter Title (Via Document Properties)

Navigate to the active data of the newly created airline and edit this airline using the change request type
Z_SFC02.

Submit the change. In this step, the Attachment UIBB is visible.

Search for the changed airline again and clicking on the Change Request icon for the airline. As you are now
in the processing step (step 01), the Attachment UIBB is not visible.

www.sap.com

2013 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty.
.