Skip to end of metadata
Go to start of metadata

Purpose

With the following steps you will be able to create a test landscape to practice with the Focused Build for SAP Solution Manager functionality without creating interferences with real TMS landscapes.

I will try to give tips and tricks for the common mistakes in the configuration of this scenario.

The given configurations activities are valid for a Focused Build for SAP Solution Manager 7.2 new installation, to configure the Requirement-to-Deploy (R2D) scenario for Innovate and Fix paces.

Focused Build for SAP Solution Manager is a preconfigured add-on solution for SAP Solution Manager 7.2. Software component ST-OST. See the ST/ST-OST supported combinations in SAP Note 2541761 - Focused Build: Release Planning.

“Focused Build projects use a standardized methodology and an integrated tool chain, which enable companies to build different and innovative software solutions on top of existing industry best practices provided by SAP – to lower the time to market and to realize tangible value. Following this new approach, customers assess business processes in collaboration with their business experts, start with best practices for commodity processes, and document requirements for differentiation and innovation.”

Note: This is just a starting document to start working with Focused Build for SAP Solution Manager written from a Change Control Management perspective.

For a complete view about how the different R2D functional areas like: Portfolio&Project Management, Process Management, Requirements Management, Change Control Management, Release Management, Test Management integrate together please don´t miss document Role-specific training curriculum document, last version here.


Important remark

To avoid methodically misuse of the functionality, it’s still highly recommended to:

  1. Start with Focused Build before you start with the conversion or implementation project, because it’s the project infrastructure where the project is based on. This is not only a tool set-up, but it comes along with methodology changes.
  2. After configuring the SAP Solution Manager/Focused Build development system, execute an initial project planning workshop with an experienced Focused build expert. E.g. the set-up of projects, release and test strategy should be discussed in context of your specific situation and needs, here.
  3. In addition, it makes very much sense to plan at least reviews for the topics:
    1. Solution Documentation/Document Management set-up before the Explore phase starts
    2. How to scope/tailor Requirement, Work Package and Work Items before the Realize phase starts
  4. Often underestimated is, to efficiently train the project team members before the project starts (general Focused Build overview) and during the project execution (brief role specific trainings according to the current project phase)

 

The documentation screenshots are taken from:


Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Configurations on the Managed Systems

1. Create the test landscape in TMS

The recommended managed system landscape for the usage of Focused Build for SAP Solution Manager is a 4-system landscape. So, this would be a typical customer scenario to be managed via Focused Build for SAP Solution Manager:

DEV:100 -> QUA:200 -> PRE:300 > PRD:400

The reason for this 4-system landscape can be seem in the next screen. When the Work Packages are getting status Handed over to Release and the last wave of the project is finished, the final Functional integration test/Regression tests are done in this preproduction system PRE.

Functional Integration Tests, Regression Tests and Performance Tests require a stable and singular Test Environment.

  • Stable means no Transports disturbing the test phase.
  • Singular means that Test Environment only contains functional changes of the current Release.

With a Three-System-Landscape No agile methodology is possible (no development and testing in parallel). Only one release can  be tested at a time.


The test landscape that I propose is this one: your Focused Build for SAP Solution Manager is installed in system CRY for example, and you are configuring in client 001 the settings of the Focused Build.

Then, create four additional clients in CRY, like local client copy from client 000 with SAP_ALL profile, let say you create clients 100, 200, 300 and 400. 

We assume that CRY:100 is going to be the Import system, the Design system and the Development system, CRY:200 the Quality system, CRY:300 the Pre-Production system and CRY:400 is the Production system.

In SCC4 assign the following client settings, roles, etc. to these clients.

Client roles: Customizing role for CRY client 100, Test role for CRY:200 and CRY:300 and Production role for CRY:400.

2. Configuration of TMS for this scenario according to Focused Build prerequisites

2.1. Key points

Transports are supported in the standard transport layer of each client. When you configure the transport routes, note that only consolidation routes that are assign to the standard transport layer of the relevant exporting client are taken into consideration.

For each exporting client, exactly one target client and one target group are permitted.

In the Focused Build for SAP Solution Manager system, in client 000, call /nSTMS (the TMS configuration should be done in the domain controller system of your real TMS managed landscape). In our example, CRY is the only system and so it is the domain controller.

2.2. Configure transport routes and transport strategy

/nstms:

Note: CRY client 001 does not need to take part of your TMS landscape. It is where the Focused Build scenario is configured.

Note: Please see in wiki page First steps to work with Change Request Management scenario in SAP Solution Manager 7.2, section 1. Create the test landscape in TMS, to see the details to create the transport routes until to get this final transport route created.

In System Attributes tab: the use of Single transport is a prerequisite for all the systems in the landscape:

Note: These is a prerequisite for managing the transport from the Focused Build scenario:

  • Deactivate the quality assurance approval procedure
  • Activate the single transports strategy

Activating the single transports strategy will ensure that the Import All option can’t be executed in the TMS.

From /STMS you can create a transport layer like Z100 in Transport Routes, Edit -> Transport Layer -> Create and then a Zpackage for this transport layer in Transport Routes, Environment-> Packages-> Create)

In Standard Transport Layer tab: ensure you enter the client 100, (client with customizing role for the development box CRY:100 in our example)), you need to configure client-specific transport layer settings for development system.

If you have more than one development systems/clients, please make sure that for all of the transport layer settings are configured correctly here, otherwise Focused Build may not be able to calculate the transport tracks based on your STMS configurations.


Consolidation routes:

Create the consolidation transport routes from CRY:100 to CRY:200, transport route must be CLIENT SPECIFIC for the use in Focused Build scenario, this is real important!

From development system to quality system you need at least two consolidation routes, SAP and ZXXX.

In case of a real landscape you need to choose from which system and CLIENT to which system and CLIENT, use button Extended Transport Control (F6) to see the client field if you choose create the transport route from Edit->Transport route -> Create option.


Delivery routes:

I make the same to create the Delivery transport route from CRY:200 to CRY:300 and from CRY:300 to CRY:400, delivery routes are always from first target system to the rest of the systems until to production systems.


Save and distribute the changes.


Note: All the previous work has to be done in the domain controller system in real TMS managed landscapes.

The following TMS parameters are required for all ABAP systems in the managed landscape:

CTC  1 (Extended Transport Control activated)

IMPORT_SINGLE_ONLY 1

IMPORT_SINGLE_STRATEGY 1

NO_IMPORT_ALL 1

WORKFLOW_STRATEGY 0

Note: CTC must be set to 1 for single ABAP stack systems and dual stack systems; for standalone non-ABAP systems CTC should be set to 0.

For the required setting for non-ABAP system check wiki page Configuring CTS+ in SAP Solution Manager 7.1 and 7.2 Step 2. TMS System Landscape Configuration.


Preparations on the Focused Build for SAP Solution Manager system

Different areas are involved in Requirement-to-Deploy (R2D) scenario, like:

  • Portfolio & Project Management
  • Process Management
  • Test Suite
  • Requirement Management
  • Change Control Management
  • Release Management

1. Review of the main configuration points in SAP Solution Manager system

Before trying to test the Focused Build scenario please ensure that you go through:

  • Configuration guide for Focused Build for SAP Solution Manager: you can find these guide for your specific patch level here, Use tab.

Example: https://help.sap.com/doc/59abbad28d5343f38faff834d641ecaa/270/en-US/FocusedBuild_ConfigGuide.pdf

Change the value 260, for getting the configuration guide for Focused Build patch level ST-OST 200 SP 6.

Go through the SOLMAN_SETUP for example for a ST-OST 06 system:

  • Mandatory Configuration of SAP Solution Manager: System Preparation, Infrastructure Preparation and Basic Configuration
  • Managed System Configuration: for the systems included in the transport track to be managed from Focused Build

Create the RFC Destinations from the SolMan system to the managed systems:clients in LMDB

Create READ, TMW and TRUSTED RFC to every Managed System:Client, so in our example for clients: 100, 200, 300 and 400.

Basic configurations for:

  1. Change Control Management
  • Implementation of Mandatory SAP notes on the managed systems

1731806 - ChaRM: support multi-client import

1818804 - Enable client restriction for import subsets in SAP ChaRM

1384598 - Harmonizing RFC communication infrastructure in ChaRM/QGM

2468171 - ChaRM: Dump DBIF_RSQL_TABLE_UNKNOWN for table /SDF/TMW_ADM on shadow systems

2335056 - ChaRM: runtime error PERFORM_PARAMETER_MISSING during creation of transport of copies

  • Changes to Number Ranges in Change Request Management

2. Process Management

3. Test Suite

4. Embedded Search

Finally perform the tasks included in Focused Build guided procedure (screenshot for SP06 system)

Pay attention to these tasks:

  • Read relevant Focused Build Central note for the corresponding patch level
  • Activate required Piece List(s) like /SALM/FB_CUST: in scc1, enter in the Transport request field value /SALM/FB_CUST, check the activation logs in SCC3 -> Transport Requests
  • Maintain AGS_WORK_CUSTOM automatically
  • Implement relevant Focused Build Technical collective note for the corresponding patch level
  • Activate SAP Gateway services (OData services) for Focused Build
  • Create the template users
  • Standard jobs: like for extracting data for the Solution Readiness dashboard, job /SALM/DATA_EXTRACTION_PPMITSM, variant FOCUSED_BUILD1 has to be scheduled.
  • Check also that the transaction types used in Focused Build are added in /ndno_cust04 as indicated in the Configuration guide

Note: In Change Request Management the recommendation is in 7.2 to copy the standard transaction types used in ChaRM to Z transaction type. However, for Focused Build as this is a turn-key solution, you must use always the standard transactions types.

  • Activate the following services in sicf_inst
    • SM_CHARM
    • SM_CRM_UI
    • SALM_FB


  • Activating BC-Sets

To activate relevant bc-sets, follow these steps:

  1. Start transaction SCPR20.
  2. Activate the following bc-set:
  • /SALM/72SP04/KPI_FRAMEWORK

Caution If you have already configured and adjusted the KPI framework with predecessor SP of Focused Build, you should not activate the above bc-set /SALM/72SP04/KPI_FRAMEWORK.

  • /SALM/TESTSUITE o /SALM/TEST_STEPS

Caution If you have adjusted the Test Steps settings already with Focused Build SPS 4, you should not activate the above bc-set /SALM/TEST_STEPS.

3. To avoid overwriting existing customizing adjustments, perform a comparison before activating the following bc-set.


2. Solution Administration: Setup

In the Solution Documentation /nSOLADM you need to perform these activities:

  • 2.1. Create a solution
  • 2.2. Create the branches required for Focused Build
  • 2.3. Create a logical component group LCG "Maintain Logical Component Groups"
  • 2.4. Assign the technical systems "Assign Technical Systems" to this LCG in the correct branches
  • 2.5. Select the document types to use
  • 2.6. Import the Best Practice
  • 2.7. Releasing Scope-Relevant Processes into the Design Branch
  • 2.8. Create a change control landscape
  • 2. 9. Configuring Branch Mapping

In the wiki page How to create a solution for Change Request Management in SAP Solution Manager 7.2 you will see the steps to create a solution for a test landscape. Change in the wiki page the SID EYE for CRY then you could follow the same steps explained there, this time we have also one additional system, the preproduction system. 

This would be the final picture for our test case:

Notice that system CRY:100 is used in the Import and Design branch and also as Development system in the Development branch.

2.1. Create a solution

The solution should contain the complete customer system landscape, processes, and solution documentation in a customer's business.

Technically, a solution is the root of a structure that contains all those objects.

From a process perspective, a solution covers all the company’s business processes. It acts as container for version of solution documentation, one of which is the production version.

From a system perspective, a solution covers all productive systems that are connected through interfaces.

Even for an international multi-site company one solution will generally be sufficient.

2.2. Create the branches required for Focused Build

A branch represents a version of the solution documentation that contains processes, libraries and systems.

With the branch concept, it is possible to distinguish between documentation that describes productive processes and documentation that describes processes currently in design or build.

Typically, a solution contains a production branch, a maintenance branch, and a development branch.

- The production branch represents the productive version of the entire solution documentation.

- The maintenance branch represents the editable version of the productive solution documentation. It provides a safe environment for performing changes.

- The development branch represents the documentation of a future solution documentation.

For an SAP S/4HANA implementation, we recommend the following branch structure:

When you create a solution by default the Production and Maintenance branches are created.

In /nSOLADM select your solution and click on the Branches tab.

Then select the Production branch and click on Create, select option Implementation Branches (Best Practices) to get a Development- Design- Import branches created.

Select the Development branch and click on Properties to enable the Change Control for Development branch.

For Focused Build setup, it is mandatory that you create at least one additional branch (such as design) below the development branch.

But please remember that still the real data are the data maintained in the TMS of the managed systems, the systems included in the Logical Component Groups should fit with the created TMS transport routes.


2.3. Create a logical component group LCG

In /nSOLADM select your solution and click on the System Landscape tab.

LCG can be regarded as a projection of managed system infrastructure into SAP Solution Manager system, so it must represent the real landscape and the system roles (names of the columns) should be consistent to system roles at TMS level. That is, for development system, the Type of Role should be Source Systems; for quality and preproduction systems, the Type of Role should be Target Systems; for production system, the Type of Role should also be Production Systems.

Remember that the solution, branches, logical component groups, system roles ... will represent the TMS REAL LANDSCAPE that you want to manage via Focused Build, but the TMS IS THE MASTER OF THIS DATA AS ALWAYS!

Ensure that there are consolidation routes defined from the source system to the first target system and delivery routes created between target systems and from the last target system to production system.

This will be check during the task list creation, if the systems entered in the LCG are not consistent with the real TMS landscape Focused Build could not create a task list for the release cycle and you will receive the usual errors:

  • No exporting system for system
  • No consolidation system found for


System Roles (Names of the columns)

When you were assigning the technical systems to a branch you saw that you need to fill a system:client under a column with a name.

Each column name is linked to a type of system role such as source system, target system, production system, etc..

Note: You can use all lower and upper-case letters except A, B, C, D, E, F, P, S, T, V, as well as numbers. This is necessary to assign systems of multiple sites to the same logical component (countries, plants). Use system roles for this purpose, do not create site logical components,

In sm30: smsy_roles you can create new system roles.

However, what it is really important is not the description name of the role, the name of the column, what it is really important is the Type of Role linked to it, assigned in transaction /nmaint_roles:

2.4. Assign the technical systems "Assign Technical Systems" to this LCG in the correct branches

In our test example I have created only 4 additional clients: 100, 200, 300, 400.

I would use CRY:100 under the Import and the Design branch as well as Development system under the Development branch.

In the configuration guides this test scenario used:


At the start of an SAP S/4HANA project, the customer might not have built up the full system landscape yet.

However, the customer will most likely have an SAP S/4HANA sandbox to perform the fit-gap analysis. This makes the sandbox system the relevant system for the activities to be documented in the import and design branches.


2.5. Select the document types to use

In /nSOLADM select your solution and click on the Document Types tab.

To ensure a smooth transition to Build Execution, all results documents should be available and uploaded to SAP Solution Manager at the end of the FitGap/Delta Design.

Examples for document types and templates are shipped in the name range 0SAP_XX as shown in the table below:

Put in the Scope those ones that you want to use in your solution.

To create your own document types based on standard types, follow these steps: Navigate to Solution Administration -> Global Functions -> Document Type Administration.

Right-click on the entry to be copied and select Copy.

You can upload your own template documents.

Each document type can be assigned to a different element, check this in the Usage tab of the document type:

The used Status Schema like 0DEFAULTSAP Default Status Schema is an important information too. As of SP07 you can use your own status values and schemas.

If you are defining your own document types you need to include then in the SAP Reference IMG SPRO point: Document KPI Framework.

Specify the document type use in the relevant documentation group: FSPEC, SFTEST, TSPEC.

2.6 Import the Best practices

Make the settings indicated in SAP Note 2194123 - Setup HTTP connections to import SAP Best Practices Packages into solutions.

Then in /nSOLADM select your solution and click on the Imports tab.

Click on Import and choose SAP Best Practices Packages, select the appropriate best practice package.

Select the Import from the Import Branch, select New deployment and provide a name for the deployment. Choose Import.

As a result, a background job starts the importing of content. When finished, a message appears and confirms the successful import.

For our example I selected SAP Best Practices for SAP Solution Manager 7.2, edition 03:

Now, you could open the Solution Documentation from the Branches tab by clicking in this link 

Or simply call /nSOLDOC and select this Solution and Import Branch

Expand the Import branch’s content Business Processes ->SAP Best Practices.. to show the imported best practice content: Packages, Processes, Process Steps.

Note: To switch to another solution, select Global Functions -> Solution

To switch to a different branch in the selected solution, use the branch drop down field.

Example:

Define and create folder structures for future documentation in:

  • business process
  • process step library
  • configuration library
  • interface library

Define name conventions for:

  • business processes
  • documents
  • diagrams


2.7. Releasing Scope-Relevant Processes into the Design Branch

Once the imported best practice processes have been scoped and it is clear which are relevant for the customer, they can be released to the Design branch.

To release to the Design branch, follow these steps:

  1. Right-click (right select) on a relevant best practice process
  2. Choose Release Changes
  3. Release

As a result, the selected process has now been released from the Import to the Design branch, where gaps are documented, and the best practice process can be adjusted.

When the required business processes are moved to the target structure you can rename them following your name convention.

Remove not project related assignments (building blocks, generic descriptions) if required.

The starting point from creating Requirements are the business processes and process steps in the Design branch.

2.8. Create a change control landscape

For Focused Build it is mandatory to create a Change Control Landscape that will be used later to create the release cycle.

In /nSOLADM select your solution and click on the Change Control Landscape tab.

Make right-click in the white area and select New:

Put the created logical component group In Scope by selecting In Scope radio button:

2.9. Configuring Branch Mapping

In SAP Reference IMG SPRO point Define Branch Mapping you need to add the entries for the change control landscape and the Design and Development branches, to indicate when the work package Handed over to the work item, to which branch we move the business processes or processes steps elements and documentation.

This is a MANDATORY task.

Final result that you need to see for your Solution:


3.     Release Management: Setup

Now we need to create the release cycles for this change control landscape in the Release Planning.

For Focused Build we are not using the SMRE transaction types for the release cycle, we need to use specifically the Focused Build transaction type S1MR and then S1RL variant when creating the task list.

One thing that is easy to skip although it is explained in the Configuration guide under section “Activating Enhanced Release Management Functionalities”, is that we need to indicate the use of this transaction type S1MR for our change control landscape in SAP Reference IMG SPRO point: Specify Transaction Type for Release Cycle.

3.1. Specify Transaction Type for Release Cycle

Select your CHANGE CONTROL LANDSCAPE created for the Solution, not the Solution name and then enter S1MR.

3.2. Define Release Management Settings

Then in SAP Reference IMG SPRO point Define Release Management Settings select Define Release Management Profiles:

You see entry for /SALM/STANDARD

If no entries are available there is a problem with the FB piece list activation.

Define Release Profile Mapping

Ensure there is one entry for your change control landscape and Rel Profile /SALM/STANDARD:

3.3. Release Planning

After making these settings, please access Release Planning via tile Release Management Releasing Planning or calling SM_CRM select /SALM/RLSMNG - Release Manager business role.

Important points here, we are going to create release cycles for the change control landscape of our solution.

We will only create Major releases, never Minor releases, and always for the Development branch.


Then you need to create the release cycles for these you Major Releases created, or at least for the first major release via Create-> Release cycles

In se16: CRMD_ORDERADM_H enter this document 8000002022 and ensure that transaction type is S1MR.

If you see that the PROCESS_TYPE is SMRE then this means that you forgot to create the entry in the SAP Reference IMG SPRO point Specify Transaction Type for Release Cycle.

If this is the case please forget about this created release cycle and about this Change control landscape, they are not valid anymore for Focused Build.

Go to the Solution and create a new Change control landscape and make the settings indicated at the begin of this section.

Click on the cycle link to open the cycle, select /SALM/RLSMNG - Release Manager business role.

3.4. Task list creation

Click on Edit and select Actions->Switch to “Prepare” Phase

Then the popup to create the task list is shown


Ensure you select S1RL variant, no SAP0 variant.

In the Define Scope you could remove transport tracks in case that you have a solution branch which contains more than one LCG.

You could remove also parallel systems and leave only a track following the line from development to production.

It is not supported the use of cCTS for Focused Build release cycle.

In the last step Complete select Create, this will create the R* task list linked to the release cycle.


A CTS project will be created automatically in the development managed system, by default no IMG project is created in Solman 7.2.

You can check the CTS project in table se16 /TMWFLOW/PROJMAN

Go to the task list with More->Open Task List to Unlock the track group

The task list contains the transport tracks. For the calculation of transport tracks, only from the selected branch, the source systems, for example development systems, are used as a starting point to identify transport tracks.

Once again, always create a LCG that fits with the real TMS managed landscape, if not the scenario could not be activated. This point is always the point that more problems gives in the task list creation!!!

Focused Build expects to see consolidation routes from source to target systems, delivery routes between target systems and from the last target system to production system.

Cycle is ready for working. You can start the creation of Requirements, Work Packages and Work Items.

Note: For Focused Build, release cycles will be mainly, time speaking, in Prepare phase, only when you are ready to set the Work Package in status Handed over to Release you need to move the release cycle to Build/Test phases.

4. Project Management: Setup

Finally, in Focused Build we need to create projects. In this example we will create a Master project that will contain two Build Projects.

To get Project Management working, start transaction /n/RPM/CUST_COPY and copy all customizing tables starting with /RPM/* and INM* to the current/working client from client 000.

From the Fiori Launchpad /n/sm_workcenter click on tile Project Management.

4.1. Create Projects

I created one master project like

And two build projects like

You can get the project templates attached to the respective Focused Build: Central note. Look for section “Creating Project Templates” in the configuration guide.

4.2. Assign Build Projects to the Master Project

Select the build project and click on Assign Master to assign the two build projects to the master project created.

You need to see this final picture, I left only two waves, with 3 sprints per wave:

4.3. Assign the Release cycle to the projects

Assign the cycle created in section 3.3. Release Planning to master and build projects, at header level. Then the waves under this project will get the same release cycle.

Troubleshooting

If you cannot see in the Release search help of a project or project wave the expected release cycle to be assigned check the following:

  1. The created release cycle document number in 3.3. has transaction type S1MR, check this by opening the document in se16: CRMD_ORDERADM_H, enter the release cycle document number and ensure that transaction type is

PROCESS_TYPE = S1MR.

If you see that the PROCESS_TYPE is SMRE then this means that you forgot to create the entry in the SAP Reference IMG SPRO point Specify Transaction Type for Release Cycle.

If this is the case please forget about this already created release cycle and about this Change control landscape, they are not valid anymore for Focused Build.

Go to the Solution and create a new Change control landscape and make for this new Change control landscape the settings indicated at the beginning of this section 3.

2. The release cycle needs to be in status Created or Prepared

3. Ensure that you followed the setting described in 3.2. Define Release Management Settings

4. Ensure that you implemented SAP Note 3001180 - Focused Build: Release cannot be assigned to a Project (ST-OST 03-05) 

4.4. Prepare first Wave and Sprint

To be able to use this project in the creation of the Work Package you need to set the Build project to status Released, at header level, and then set the Wave1-Sprint 1 to status Released.


Until the Project and the sprint of a wave is not in Released status, you will not see this project to be selected when creating a Work Package later:

Please check in the configuration guide for the recommendation to check start dates, end dates, and duration of related waves between master and sub projects.

Project Milestones Maintenance and the Release of Q-Gates for the Solution Readiness Dashboard.

5. Last settings to be able to work with Focused Build scenario

5.1. Activating Virus Scan Profiles

Activate the virus protection in your SAP Solution Manager system:

  • Execute transaction /n/IWFND/VIRUS_SCAN
  • Activate the virus scan profile /UI5/UI5_INFRA_APP/REP_DT_PUT. Ensure that the Virus Scan Switched Off checkbox is not selected.
  • You could also select the option to deactivate the virus scan for your SAP Solution Manager system

5.2. Customizing Requirements Management

The main purpose of this customizing activity is to check if the work packages and the business requirements transaction types are customized correctly and maintain them if needed.

In the customizing of SAP Solution Manager, choose SAP Solution Manager → Focused Build → Work Package Configuration → Define Requirement and Work Package.

For the last attribute Required relationship between requirement and work packages there are  several customizing options:

  • 1:1
  • 1:n
  • n:m

5.3. Activation of Required Business Add-ins

  • Navigate to the customizing of SAP Solution Manager → Focused Build → Work Package Configuration → Activation of required BadIs → Activation of COM_PARTNER_BADI

Activate the implementation /SALM/ITR_PARTNER.

  • Navigate to the customizing of SAP Solution Manager → Focused Build → Work Package Configuration → Activation of required BadIs → Activation of CRM_ORDER_FIELDCHECK_NEW

Activate the implementation /SALM/FIELDCHECKS


5.4. Configuring E-Mail Notifications on Document Status Change

On Document Status change, the e-mail notification will be sent to the e-mail address maintained in business partner information. Transaction Code ‘BP’ and the email updated in the Communication of the business partner form

To receive e-mail notification upon status change of the document, the customizing can be maintained in SAP Reference IMG SPRO -> SAP Solution Manager –> Focused Build -> Documentation -> Activate BAdI for Email Notification

Select the next option Configure E-Mail Notifications on Document Status Change.                                                                                          

On status change, an email is triggered, and it can be found in the MyDocuments application.


5.5. Configuring Multilevel Categorization

To configure multilevel categorization for Focused Build start transaction SM_CRM and  click on Service Operations and then Categorization Schemas.

Create a new categorization schema called FOCUSED_BUILD.

Assign the application areas as follows:

Application ID: Service Order

Parameter: Transaction Type / Catalog Category

Choose all S1*/D  and save your selection.

Upload the categorization schema FB_General.txt via /nCATEGOTOOL -> Import Schema.

Release the FOCUSED_BUILD schema.

Repeat the steps to create a second categorization schema and call it FOCUSED_BUILD_TESTING for S1TR (test requests).

5.6. (Optional) Enabling and Displaying Rich Text

See the required settings in the relevant configuration guide.


Now you can see how to use the scenarios that we configured in wiki page First steps to work with Focused build for SAP Solution Manager - Workflow.

Related Content

Related Documentation 

Search for SAP Solution Manager -> Focused Solutions ->Focused Build section to see demos for the different scenarios in Focused Build

Related Notes

2541761 – Release planning information for Focused Build

1731806 - ChaRM: support multi-client import

1818804 - Enable client restriction for import subsets in SAP ChaRM

1384598 - Harmonizing RFC communication infrastructure in ChaRM/QGM

3001180 - Focused Build: Release cannot be assigned to a Project

  • No labels