SMI310 EN Col62 FV Part A4-121-150

SMI310 Lesson: Business Blueprint
Exercise 4: Business Blueprint

Exercise Objectives
After completing this exercise, you will be able to:
Use the pre-defined SAP implementation content
Define the project scope by creating a project-specific solution structure
Assign responsible team members and administrative data
Document business and technical requirements along the project scope
Create a blueprint-specific issue using message-handling features
Generate a Business Blueprint document
Business Example
During Phase 2, Business Blueprint, the project team will define and document
all business process requirements, both functional and technical. When possible,
standard SAP business scenarios will be employed because they are delivered
with predefined implementation content such as process documentation, IMG
assignments, and test cases. Using these scenarios, you can significantly reduce
project implementation costs. At the end of Phase 2, a Business Blueprint
document should be generated for approval.
Task 1:
User menu; Business Blueprint <SOLAR01>
1. Choose the predefined training project (SMI310_200).
Task 2:
Review the available implementation content along the business process Lead
Analysis (Business Scenario: Lead and Opportunity Management).
1. Read the scenario documentation Business Scenario Lead and Opportunity
Management for the business process Lead Analysis.
2. Run the transaction assigned to the process task related to the business
process Lead Processing in CRM to evaluate the related SAP application.
Task 3:
Change Project to your group project SOLT200_##
Define your own project-specific solution structure in your group's project
1. In the Structure tab, create your own business scenario and processes:
Continued on next page
2006/Q2 2007 SAP AG. All rights reserved. 111

Unit 3: Managing Implementation Projects - in Detail SMI310
Go to Structure area Add Name

<Group Project Description> Sales <##>
Business Scenarios
<Group Project Description> Sales Process <##>
Business Scenarios
2. In the Structure tab, add process steps from the Business Process Repository
that are part of the project-specific solution structure. Use the following
structure areas and process steps :
Structure area Process Steps

Sales Order Processing (CRM)
Create Order
Process Order
Sales Sales Order Management
(SAP R/3 4.6C) Create Sales Order
Create delivery
Send/Print Delivery Documents
Create Customer Invoice
Send/Print Billing Documents
3.
In the Structure tab, sort the process steps in the sequence specified above.
4. In the Structure tab, rename the following process steps:
Original name (Description in New Name (Process Step)

Business Process Repository)
Create Order Create Order in CRM
Create Sales Order Create Order in ERP
5. In the Structure tab, add a NONSAP-specific process step such as Pricing

after the process step Create Order in CRM.
6. In the Graphic tab, display the related process graphic.
7. (Optional) Navigate to the structure area <Group Project Description>
Business Scenarios Sales <##> Business Processes.
8. (Optional) Add another business process and try to build a real
customer-specific process.
112 2007 SAP AG. All rights reserved. 2006/Q2

Task 4:
Maintain administrative data to track the progress of the project.
1.
2. In the Administration tab, enter the following data at the minimum:
Data Type Value

Status In Process
Assigned Project Member SMI310-## and SMI310-00
Plan Data <optional>
Actual Data <optional>
3. In the Administration tab, copy the administrative data to subitems and

change the status In Process in several process steps to another status value.
Note: The available status values depend on the assignments to the

project in Project Administration <SOLAR_PROJECT_ADMIN>.
4. Maintain/modify administrative data for other process steps.
Task 5:
In the Project Documentation tab, document the business and technical
requirements (Business Blueprint) along the project-specific solution structure.
1. At the process step Create Order in CRM, create a Customer Input (CI)
template and describe the business requirements for this process step.
Note: You can change the display/edit mode for documents in the
menu Settings User-Specific General Settings.
2. At the process step Create Order in CRM, create an Interface Form and
describe the technical requirements on the interface to the NONSAP process
task.
3. At the process task Create Order in ERP, link the CI template described at
the process step Create Order in CRM.
4. At the process step Create Order in ERP, create Meeting Minutes and
maintain the following document attributes:

Data Type Value

Priority High
Status Released
Keyword Administrative
Business Blueprint Relevant <deselect>
5. (Optional) At other process steps, use other options (Upload File, Copy
of a SAP Solution Manager Document, Web Link, etc.) and add project
documentation to specify additional business and technical requirements.
6. (Optional) Maintain the document attributes for other project documents.
Task 6:
Create a Business Blueprint-specific message for the process step Create Order
in CRM.
1. In the Messages tab, create a message about the interface specification using
the following data:
Data Type Value

Subject Docu Query
Priority High
Short text <text>
Long Text <text>
2. In the Messages tab, process the created message, as shown below:
Data Type Value

Pers. Resp. (Processor) SMI310-00
Status Put In Process (In Process)
3. Create messages for other process tasks.

Task 7:
Generate a Business Blueprint document.
Caution: Close all other Word applications before you generate the
Business Blueprint document.
1. Create a Business Blueprint document. Restrict the selection to the structure

area Sales Process <##>.
2. Upload the generated Business Blueprint document to your structure area.
Note: Deselect the document Business Blueprint-Relevant attribute.

Solution 4: Business Blueprint

Task 1:
User menu; Business Blueprint <SOLAR01>
1. Choose the predefined training project (SMI310_200).
a) if the correct project is not showing, choose the Other Project button,
then select the (SMI310_200) project.
Task 2:
Review the available implementation content along the business process Lead
Analysis (Business Scenario: Lead and Opportunity Management).
1. Read the scenario documentation Business Scenario Lead and Opportunity
Management for the business process Lead Analysis.
a)
In the Documentation (Gen.) tab, choose Lead Analysis and open
it by clicking the Display button.
Read the document to understand the general structure and
content of scenario documentation.
Click the Close Document button and return to the overview
screen.
2. Run the transaction assigned to the process task related to the business
process Lead Processing in CRM to evaluate the related SAP application.
a)
Navigate to the process task Lead Processing in CRM.
Click the Execute button beside the structure item to run the
default transaction. The SAP Solution Manager launches the
application in the related evaluation system.
Hint: You can change the system role, for example, Evaluation
and Development, through the Business Blueprint System
Role menu.
In the Transactions tab, you can run other transactions related
to the process task or designate another transaction as the
default (standard).
Click the Back (F3) button to return to the SAP Solution Manager.

Task 3:
Change Project to your group project SOLT200_##
Define your own project-specific solution structure in your group's project
1. In the Structure tab, create your own business scenario and processes:
Go to Structure area Add Name

<Group Project Description> Sales <##>
Business Scenarios
<Group Project Description> Sales Process <##>
Business Scenarios
a) Navigate to <Group Project Description> Business Scenarios.

Select the Structure tab. Create a new Scenario called Sales <##>.
Click the Save button.
b) Navigate to <Group Project Description> Business Scenarios
Sales <##> Business Processes. Select the Structure tab. In the
Business Process Name column, enter a new item using the naming
convention Sales Process <##>. Click the Save button.
2. In the Structure tab, add process steps from the Business Process Repository
that are part of the project-specific solution structure. Use the following
structure areas and process steps :

Structure area Process Steps

Sales Order Processing (CRM)
Create Order
Process Order
Sales Sales Order Management
(SAP R/3 4.6C) Create Sales Order
Create delivery
Send/Print Delivery Documents
Create Customer Invoice
Send/Print Billing Documents
a) Navigate to the business process <Group Project Description>

Business Scenarios Sales <##> Business Processes Sales
Process <##>.
Select the Structure tab.
In the Step Name column, use possible entry help (F4).
Navigate to the structure areas as shown above and select the
related process steps.
Click the Save button to transfer structure items to the project
structure and save.
3.
In the Structure tab, sort the process steps in the sequence specified above.
a) Select the process step(s), click the Move Up/Move down buttons to
sort the process steps, and Save.
4. In the Structure tab, rename the following process steps:
Original name (Description in New Name (Process Step)

Business Process Repository)
Create Order Create Order in CRM
Create Sales Order Create Order in ERP
a) In the Process Step column, overwrite the structure items with the
new names and Save.

5. In the Structure tab, add a NONSAP-specific process step such as Pricing

after the process step Create Order in CRM.
a)
In theProcess Step column, enter a name for the new structure
item.
In the Logical component column, select ZNONSAP.
Use the Move Up/Move down buttons to place the structure item
correctly and Save.
6. In the Graphic tab, display the related process graphic.
a)
Hint: If prompted enter your username, SMI310-##, and

password.
7. (Optional) Navigate to the structure area <Group Project Description>

Business Scenarios Sales <##> Business Processes.
a)
8. (Optional) Add another business process and try to build a real
customer-specific process.
a)
Task 4:
Maintain administrative data to track the progress of the project.
1.
a)
2. In the Administration tab, enter the following data at the minimum:

Data Type Value

Status In Process
Assigned Project Member SMI310-## and SMI310-00
Plan Data <optional>
Actual Data <optional>

Process <##>.
b) Select the Administration tab.
c) In the Status field, use possible entry help (F4) and select the status
value In Process.
d) In the Assigned Project Member column, use possible entry help (F4)
and select users as indicated above.
e) Populate the Plan Data and Actual Data fields as required.
3. In the Administration tab, copy the administrative data to subitems and
change the status In Process in several process steps to another status value.
Note: The available status values depend on the assignments to the

project in Project Administration <SOLAR_PROJECT_ADMIN>.
a) Click the Copy Data to Sub items button to copy the values for Status
and Plan Data to process steps and Continue (Enter).
b) Navigate to several process steps and change the status value In Process
using possible entry help (F4) and Save.
4. Maintain/modify administrative data for other process steps.
a)

Task 5:
In the Project Documentation tab, document the business and technical
requirements (Business Blueprint) along the project-specific solution structure.
1. At the process step Create Order in CRM, create a Customer Input (CI)
template and describe the business requirements for this process step.
Note: You can change the display/edit mode for documents in the
menu Settings User-Specific General Settings.

Process <##> Create Order in CRM.
b) Select the Project Documentation tab.
c) Click the Insert Document button and select the Create New Document
option.
d) Select CI Template Business Processes as the documentation type.
e) Enter a document title and press Enter.
f) Enter sample data in the various sections of the template and save
the document.
g) Click the Close Document button to return to the overview screen and
confirm by saving again.
2. At the process step Create Order in CRM, create an Interface Form and
describe the technical requirements on the interface to the NONSAP process
task.
a) Click the Insert Document button and select the Create New Document
option.
b) Select Interface Form as the documentation type.
c) Enter a document title and press Enter.
d) Enter sample data in the form and save the document.
e) Click the Close Document button to return to the overview screen and
confirm by saving again.

3. At the process task Create Order in ERP, link the CI template described at
the process step Create Order in CRM.
Process <##> Create Order in ERP.
b) Select the Project Documentation tab.
c) Click the Insert Document button and select the Link to SAP Solution
Manager Document option and press Enter.
d) In the Find Info Object screen, choose Documentation Type CIT as
the search criteria and continue.
e) Select the created CI template from the list and continue.
4. At the process step Create Order in ERP, create Meeting Minutes and
maintain the following document attributes:
Data Type Value

Priority High
Status Released
Keyword Administrative
Business Blueprint Relevant <deselect>
a)
Click the Insert Document button and select the Create New
Document option.
Select Meeting Minutes as the documentation type.
Enter a document title and press Enter.
Enter sample data in the form and save the document.
Click the Close Document button to return to the overview screen
and confirm by saving again.
Select the row for the project document Meeting Minutes.
Click the Attribute button, modify the values as indicated above,
and continue.
Note: The Business Blueprint Relevant attribute is referenced
while generating the Business Blueprint document.

5. (Optional) At other process steps, use other options (Upload File, Copy
of a SAP Solution Manager Document, Web Link, etc.) and add project
documentation to specify additional business and technical requirements.
a)
6. (Optional) Maintain the document attributes for other project documents.
a)
Note: The locking function in Project Administration
<SOLAR-PROJECT-ADMIN, Scope tab enables you to
freeze the process scope and protect changes to the project
documentation.
Task 6:
Create a Business Blueprint-specific message for the process step Create Order
in CRM.
1. In the Messages tab, create a message about the interface specification using
the following data:
Data Type Value

Subject Docu Query
Priority High
Short text <text>
Long Text <text>
a)
Select the Messages tab.
Create a message using the Create button.
Use possible entry help (F4) to specify the subject area and
priority.
Enter a short text, for example, interface requirements.
Describe the issue in the Messages tab.
Optional: In the Attachmt tab, upload an attachment using the
Import button.
Save the message using the Save button.
2. In the Messages tab, process the created message, as shown below:

Data Type Value

Pers. Resp. (Processor) SMI310-00
Status Put In Process (In Process)
a)
Select the created message row.
Click the Display button to launch the message.
Change to the edit mode using the Change button.
Assign user SMI310-00 as Resp. Person and change the status
to In Process.
Optional: Create an internal note using the New Text button.
Save and return to the overview screen using the Back button (F3)
and confirm by saving again.
Save.
3. Create messages for other process tasks.
a)
Note: Transaction Message Handling <DNOTIFWL> enables
users to view all messages.

Task 7:
Generate a Business Blueprint document.
Caution: Close all other Word applications before you generate the
Business Blueprint document.
1. Create a Business Blueprint document. Restrict the selection to the structure

area Sales Process <##>.
a)
Go to the menu at the top of the screen. Choose Business
Blueprint Generate Blueprint Document. A selection screen
with three tabs will pop up.
In the General tab, select the check-boxes beside which Graphics
should be included in the Blueprint.
You can leave the default directory location for storing the
document.
In the Scope tab, decide how much you want to include in the
blueprint.
To do this, press the Structure button and drill down to your
business process area.
Make sure to include only those structure items below Sales
Process ## , otherwise you will generate a very large blueprint!
In the Display Options tab, accept the defaults.
Next, choose the execute button. A window will appear
telling you the file has been downloaded to the subdirectory
indicated and that you should open Word and run a macro called
SAP_BUSINESS_BLUEPRINT.
In Word, go to the menu ToolsMacroMacros, select the
proper macro, then choose run.
The blueprint document will open.

2. Upload the generated Business Blueprint document to your structure area.
Note: Deselect the document Business Blueprint-Relevant attribute.
a)
Choose File Save Copy as to store the Business Blueprint
document on the hard drive.
Click the Back button (F3) to return to the Business Blueprint
transaction.
Navigate to the business process SAP Solution Manager -
Training Project Business Scenarios Sales-<##>
Business Processes Sales Process.
Select the Project Documentation tab.
Click the Insert Document button.
Enter the document title and select BB - Business Blueprint as
the documentation type.
Choose the Upload File option and click OK (Enter).
Select the saved Blueprint file from the local directory.
Select the row with the Business Blueprint document and click
the Attribute button.
Deselect the document attribute Business Blueprint-Relevant
and choose Continue (Enter).
Save.

Lesson Summary
You should now be able to:
Explain the Business Blueprint phase
Create project documentation
Use the message handling functions
Generate the Business Blueprint document

Lesson: Realization
Lesson Overview
This lesson explains how to use the SAP Solution Manager in the Realization
phase. The purpose of this phase is to implement business process requirements
based on the Business Blueprint. The objectives of the Realization Phase are the
final configuration of the system, robust functional and system testing, and the
release of the system for production (live) operation.
Lesson Objectives
After completing this lesson, you will be able to:
Use Solution Manger to configure the system based upon the Blueprint
Requirements.
Understand the concept of Customizing Distribution.
Plan, manage and conduct testing of the system.
Understand the concept of BC Sets
Business Example
Your project team has completed the Blueprint Phase of the project and a complete
and signed-off Business Blueprint is available to all teams to guide the process
of customizing (configuration) the system. You will use Solution Manager to
accomplish this.

SMI310 Lesson: Realization
Customizing
Figure 68: Activities and Functions by Phase Realization
The objective of the Realization Phase is to implement business process

requirements based on the Business Blueprint. Activities are focused on
configuring the solution and testing the implemented solution. The objectives
are final configuration of the system, overall testing, and release of the system
for production (live) operation.
In this phase, settings are made and tested for master data, organizational units,
and business processes placed into scope in the Business Blueprint phase.
Prerequisites:
The Business Blueprint has been created and approved.
The development system is available.
The following Realization phase project tasks are supported by the SAP Solution
Manager:
Configuration
Customizing Distribution
Consistency Check
Setup Project Systems
Test Organization
Solution Manager transaction: SOLAR02

Figure 69: Create and Assign Additional Customizing Objects
You can access the various Customizing tools using the SOLAR02 transaction. It
is the central point of access to configure system settings for the implementation
project. You can enter transactions to edit BC Sets and the Implementation Guide
or transactions to import Add-Ons and maintain CATTs.
In SOLAR02, there is also the ability to change the Configuration. When doing
so, there is a useful filter tool to help you during the process.

Figure 70: Scenario and Industry-Specific Filters for BPR
When making changes to the configuration, the Scenario-specific filter for the
Business Process Repository allows one to see only those BPR elements which are
part of the Scenario/Roadmap configured for the selected project. At the same
time, the Industry-specific filter allows one to choose which elements to display
based on selected industries
To use this filter, go to transaction SOLAR02:
In the Configuration Structure window, select the Configuration structure
element of the project
On the right side of the screen, select the Structure tab and click on the
Change Configuration Structure button
Confirm that the Source field is set to Business Process Repository
Select the Configuration Element field and press the F4 key
The resulting window is the Business Process Repository Selection Help. At
the bottom of this window are the filter buttons. One for Scenarios, one for
Industries. If it displays Scenarios: Active then the filter is active and only those
elements related to the Scenario/Roadmap configured for the Project will be
shown. Clicking on the button will toggle the filter to Inactive and all elements of
the Scenario/Roadmap will be visible. The Industries filter works the same way
as the scenario filter, except that, when activating the filter, the industries to use
for the filter must be selected.

Features of SOLAR02:
You can create new BC Sets, assign them to a structure, view the content of
assigned BC Sets, and delete the assignments of BC Sets that are no longer
required from the project in application systems.
You can activate one or more assigned BC Sets.
You can view the settings configured by BC Sets in the Implementation
Guide (IMG) and edit the system settings that could not be configured by
BC Sets.
You can assign CATTs to process steps and call them to configure system
settings or store pre-configuration.
You can store documentation for individual configuration steps. You can
assign existing documentation and create new documentation.
You can also import Customizing contained in Add-On transports to your
system.
You can specify the processing status and the person responsible for each
object you assigned.
A configuration document is used to describe configuration processes that do not
take place in the SAP world. It does not contain any descriptions of IMG settings.
Figure 71: Tracking Customizing in SAP Solution Manager

You can specify the processing status and the person responsible for each object
assigned.
Note:
Documentation of customizing can take place at the IMG level or
through project documentation on process/process step level
No automated replication of IMG status and responsible from IMG
into Config TAB
Figure 72: Realization: Comparing Customizing
After implementing and configuring a system landscape, you customized

various SAP application components. The system landscape comprises various
components that have their own (independent) customizing tables (technical
view). These components also require joint customizing for practical reasons.
For example, when you implement e-Business software, you use a system
landscape in which an SAP ERP system works with SAP CRM. Ideally, the CRM
system uses data in the ERP system. The configuration of the two systems should
match in specific areas. Joint customizing should be synchronized. In particular,
changes in ERP can require changes in a SAP application component.
You need to regularly check the consistency of customizing to verify that the SAP
R/3 customizing is still synchronous with the application component customizing.
The Solution Manager contains a tool that compares customizing in SAP, the
Customizing Scout.

Business Configuration (BC) Sets
Figure 73: Advantages of BC Sets
A BC Set is a collection of customizing settings:

Grouped according to logical, business management criteria of a unit
For documentation, quality assurance and reuse purposes
Independent of the original Customizing tables/views
Accessible across the system landscape
Figure 74: BC Set Transactions
They can be used for a group rollout, where the customizing settings, for example,
are bundled by the group headquarters and passed on in a structured way to its
subsidiaries.

BC Sets are provided by SAP for selected industry sectors, and customers can also
create their own. When a BC Set is created, values and combinations of values are
copied from the original Customizing tables into the BC Set and can be copied
into the tables, views and view clusters in the customer system. The BC Sets are
always transported into the customer system in which Customizing is performed.
The loading of BC Sets is logged by the system, i.e. which BC Set was copied
when into the system, and any errors which occurred. This information is
significant for Continuous Change and Upgrade.
Only customizing data can be captured in a BC Set. Master Data, Transaction
Data and Repository Objects are not valid for BC Sets.
Figure 75: Customizing Setting Attributes in BC Sets
When creating BC Sets the customizing settings may be configured with one
of the following values
Default
Fixed
Variable
Default copies,the existing values of the table fields in the source system (in this
case, Solution Manager) into the BC Set, overwrites the value in the activation
system without confirmation, once the BC Set is activated, and allows manual
changes.
Fixed copies a set value into the BC Set, which cannot be changed in the
activation system.

Variable allows the attribute value to be set upon activation. All values which
cannot be set at the time the BC Set is created must have this attribute.
Figure 76: BC Set Types
There are two primary types of BC Sets:

Simple BC Set
Hierarchical BC Set
The Simple BC Set is the most common, being built from customizing data
created in the IMG activities.
A Hierarchical BC Set is a BC Set comprised of other BC Sets. The BC Sets
included can be Simple BC Sets or other Hierarchical BC Sets. There is no limit
to the depth of the nesting when including Hierarchical BC Sets in a Hierarchical
BC Set.
A third type of BC Set which is sometimes mentioned is the BC Set from transport
request. However, this is really only another example of a Simple BC Set where a
transport request is used as the customizing template.
To find out more about BC Sets go to http://service.sap.com/rkt-solman and select
the BC Sets E-Learning.

Customizing Distribution
Typical challenges/Usage Scenarios

Customizing of specific objects should be synchronized across systems
Existing customizing of ERP should be reused in other systems (such
as CRM)
Redundant customizing activities within a Solution Landscape (such as
ALE scenarios) should be avoided
Basic functions
Editor for Synchronization Groups
Activation of a Customizing Distribution Scenario
Manual customizing distribution
Activation log and error-handling features
Distribution Scenarios
Delta Customizing
Initial Customizing
Figure 77: Customizing Distribution
You often need to synchronize selected customizing settings in various systems

in a system landscape. You can use Customizing Distribution to synchronize
customizing settings in a source system (for example, ERP2005) with the
customizing settings in target systems, such as a SAP CRM system in a SAP
system landscape.

Customizing Distribution is performed only between development systems.

Customizing objects (Synchronization Objects) that should be synchronized
between various SAP components are predefined.
When you create a synchronization group, you can select synchronization and
other customizing objects using the Synchronization Group Editor.
When you change customizing settings of an object in the source system,
Customizing Distribution begins transferring the changes to the target system.
Figure 78: Distribution Options Distribution Types
You use Customizing Distribution to transfer customizing changes made in a SAP

ERP development system to other development systems in the system landscape.
For example, you can use Customizing Distribution to:
Download selected customizing from SAP ERP to a newly-installed SAP
APO system.
Synchronize customizing in an HR and a non-HR system and use ALE
distribution in a stand-alone HR.
Synchronize customizing in a SAP ERP and a SAP CRM system, because
there are business processes that run in both systems.
Using Customizing Distribution, you can perform the following functions on
customizing settings in a development landscape:
Initial distribution from a SAP ERP to a target system
Timed distribution
Automatic distribution after each transport release or customizing change
Manual distribution in a transport request

Figure 79: Customizing Distribution in Detail
Figure 80: Prerequisites for Customizing Distribution

The RFC connections for distribution should be Trusted System connections.

Proceed as described in the following OSS notes regarding Trusted System
connections
Note 0128447
Note 0131387
Note 0204039
Note 0524193
There should be a Trusted System RFC connection from the source system to the
Solution Manager system. When using normal connections, customizing in the
target system and logs are made with the user initiating the connection, which
drastically reduces reproducibility. RFC destinations with a log in screen require
you to log on to the target system for each customizing change.
Figure 81: Setting Up Customizing Distribution
To set up Customizing Distribution, you need to:

Select the synchronization group that should be activated for customizing
distribution
Determine the logical systems for the source development system
Determine the logical systems for the target development system
Decide if customizing should be distributed during customizing, after
transport release, or periodically at specified times
Select the synchronization group that should be activated for customizing
distribution

SMI310 EN Col62 FV Part A4-121-150

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SMI310 EN Col62 FV Part A4-121-150

Uploaded by

Copyright:

Available Formats

SMI310 Lesson: Business Blueprint

Exercise 4: Business Blueprint

Continued on next page

2006/Q2 2007 SAP AG. All rights reserved. 111

Go to Structure area Add Name

Structure area Process Steps

Original name (Description in New Name (Process Step)

5. In the Structure tab, add a NONSAP-specific process step such as Pricing

Continued on next page

112 2007 SAP AG. All rights reserved. 2006/Q2

Data Type Value

3. In the Administration tab, copy the administrative data to subitems and

Note: The available status values depend on the assignments to the

4. Maintain/modify administrative data for other process steps.

Continued on next page

2006/Q2 2007 SAP AG. All rights reserved. 113

Data Type Value

Data Type Value

2. In the Messages tab, process the created message, as shown below:

Data Type Value

3. Create messages for other process tasks.

Continued on next page

114 2007 SAP AG. All rights reserved. 2006/Q2

1. Create a Business Blueprint document. Restrict the selection to the structure

Note: Deselect the document Business Blueprint-Relevant attribute.

2006/Q2 2007 SAP AG. All rights reserved. 115

Solution 4: Business Blueprint

Continued on next page

116 2007 SAP AG. All rights reserved. 2006/Q2

Go to Structure area Add Name

a) Navigate to <Group Project Description> Business Scenarios.

Continued on next page

2006/Q2 2007 SAP AG. All rights reserved. 117

Structure area Process Steps

a) Navigate to the business process <Group Project Description>

Original name (Description in New Name (Process Step)

Continued on next page

118 2007 SAP AG. All rights reserved. 2006/Q2

5. In the Structure tab, add a NONSAP-specific process step such as Pricing

Hint: If prompted enter your username, SMI310-##, and

7. (Optional) Navigate to the structure area <Group Project Description>

Continued on next page

2006/Q2 2007 SAP AG. All rights reserved. 119

Data Type Value

a) Navigate to the business process <Group Project Description>

Note: The available status values depend on the assignments to the

Continued on next page

120 2007 SAP AG. All rights reserved. 2006/Q2

a) Navigate to the business process <Group Project Description>

Continued on next page

2006/Q2 2007 SAP AG. All rights reserved. 121

Data Type Value

Continued on next page

122 2007 SAP AG. All rights reserved. 2006/Q2

Data Type Value

Continued on next page

2006/Q2 2007 SAP AG. All rights reserved. 123

Data Type Value

Continued on next page

124 2007 SAP AG. All rights reserved. 2006/Q2

1. Create a Business Blueprint document. Restrict the selection to the structure

Continued on next page

2006/Q2 2007 SAP AG. All rights reserved. 125