Study guide

11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion

SAP S/4HANA Sales C_TS462

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure

1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration

2 Chapter 2: The Order-to-Cash Process and Sales Master Data

2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling

3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements

3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries

4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs

4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders

5 Chapter 5: Pricing and the Condition Technique

5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement

6 Chapter 6: Availability Check (ATP) and Delivery Scheduling

6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements

7 Chapter 7: Delivery Processing and Embedded EWM

7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries

8 Chapter 8: Billing and Integration with Financial Accounting

8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options

9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output

9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables

10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core

10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels

11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition

11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM

11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion

Key Takeaways Explain This Topic AI

The partner project manager sets up the SAP Cloud ALM project: roles, roadmap, timeboxes, team, scope (new implementations only), system group, and deployment plan.

For new implementations, the scope in SAP Cloud ALM is taken from the Digital Discovery Assessment, either manually or by importing its Excel export.

The SAP Readiness Check compares an ECC system with the simplification items and reports, among others, custom code, customer-vendor integration, financial data quality, and SAP Fiori app recommendations.

SUM does not create the SAP Fiori launchpad; after a conversion it is set up with Rapid Activation (task list SAP_FIORI_FOUNDATION_S4, roles SAP_FLP_USER and SAP_FLP_ADMIN).

Last updated: October 2026

Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion

SAP Cloud ALM turns the SAP Activate methodology into assigned, trackable tasks. For conversion projects, a set of analysis tools shows what has to change before the technical conversion starts. Both topics come from the S4C03 unit Setting Up Systems for Implementation .

Project Setup in SAP Cloud ALM

The partner project manager needs access first, because they create the project and assign the tasks to everyone else. The setup steps:

Users : the IT Contact adds the team members, who already exist in SAP Cloud Identity Services.

Roles : review the standard project roles, edit or delete them, and create roles such as one per line of business. One role can be assigned to several people, so LoB tasks reach the whole LoB team.

Project and roadmap : create the project and choose the SAP Activate roadmap (see the table below).

Timeboxes : enter the dates of each phase, working backwards from the planned go-live. The Explore phase with the fit-to-standard workshops usually needs the most time. The Overview app shows remaining days and open tasks per phase.

Team : assign people to roles and switch off unused roles; several roles or users can be combined into a team.

Scope (new implementations only): in Manage Scopes , choose the SAP Best Practices package for Private Edition or the Enterprise Management Layer (for companies with many intercompany processes), then select the business processes and local versions from the Digital Discovery Assessment (DDA) . You can select them manually, filtering by country and business process group, or import an Excel file exported from the DDA ( More → Import & Export → Export Excel in the DDA, then Scope from file ). The DDA is only a starting point; the scope usually changes after the workshops.

System group : group the development, quality, and production systems; the IT Contact supplies the system names.

Deployment plan : enter the upcoming releases within the project timeboxes, assign the system group, and then assign the deployment plan to the project.

Roadmap Typical Use

RISE with SAP Methodology - Clean Core Success Plan Clean core as a separate project running in parallel with, or beyond, the implementation

RISE with SAP S/4HANA Cloud Private Edition - Implementation New implementations, including replacements of non-SAP ERP systems

RISE with SAP S/4HANA Cloud Private Edition - System Conversion Conversion of SAP ECC, keeping customizations, configuration, and history

RISE with SAP S/4HANA Cloud Private Edition - Selective Data Transition Transfer of all or selected data, in one go or in stages

RISE with SAP S/4HANA Cloud Private Edition - Upgrade Release upgrades after go-live

The clean core tasks and quality gates are part of every Private Edition roadmap, not only of the clean core success plan. For conversions, the existing scope is analyzed and documented with SAP Signavio Process Manager (included in RISE with SAP) instead of scoping in SAP Cloud ALM.

  • Preparing a System Conversion
  • SAP Signavio Process Insights, Discovery Edition

Included in RISE with SAP, it analyzes a one-time data load from the ECC system, and the analysis expires after six months ; the full edition monitors daily without expiry and offers more functions. It shows processes that run inefficiently and units where processes run better than elsewhere, which feeds the fit-to-standard discussions. It succeeds the Business Scenario Recommendations report and Process Discovery.

SAP Readiness Check

The SAP Readiness Check is started from SAP for Me → Services & Support → ALM . It compares the customer's system with the SAP S/4HANA simplification items , which describe functions that were changed, replaced, or removed, and it can also be run before a release upgrade. Its report includes:

  • Area What It Shows
  • Simplification items and related activities Relevant items and proposed project activities
  • Compatibility scope analysis Classic ERP functions that may be used with limited rights in SAP S/4HANA
  • Add-ons and business functions Compatibility that must be validated before the conversion
  • Sizing and data volume management Target sizing, data growth, and archiving potential
  • Custom code analysis A first estimate of the remediation effort
  • Integration (interface analysis) Interfaces affected by the move

Customer vendor integration analysis Customers, vendors, and contact persons to synchronize with business partners

  • Planned downtime calculator Expected duration of the downtime phases
  • Financial data quality Inconsistencies in general ledger, asset accounting, and material ledger

App availability and recommended SAP Fiori apps Deprecated transactions and their SAP Fiori successors, based on actual usage

Business process discovery and innovation potential Cleanup candidates and business cases

The SAP Fiori Apps Recommendations report, run from the SAP Fiori Apps Reference Library, gives a dedicated list of apps. SAP S/4HANA delivers more than 500 business role templates , which customers copy and refine in the development system. The Custom Code Migration app (on SAP BTP) checks custom code against the Simplification Database and gives a detailed effort estimate (section 11.6).

Pre-Conversion Projects and the Technical Conversion

Resolve the pre-conversion projects found by the Readiness Check: data management , customer-vendor integration (synchronizing customers and vendors with business partners, section 2.2), reconciliation of financial data , and the cleanup and remediation of custom code .

Choose the method: SUM 2.0 , with or without the Database Migration Option, which usually reduces downtime.

Plan the conversion in the Maintenance Planner , which includes running the Simplification Item Check in the ECC system. The Readiness Check and the Simplification Item Check serve different purposes, so both are required. The master Simplification Item Catalog is in SAP for Me.

Address custom code with the Custom Code Migration app and the ABAP Test Cockpit , run the technical conversion with SUM, and finish with application-specific follow-up tasks and thorough testing.

Selective Data Transition: Business Transformation Center

For a selective data transition, run the SAP Readiness Check for SAP ERP Usage and Data Profiling (SAP Note 3112362), upload its result in SAP Cloud ALM with Manage Analysis Files , and create a Digital Blueprint with Manage Digital Blueprints . Further apps let you deselect data, for example company codes that have not been used for years, so that less data is transferred.

Rapid Activation of SAP Fiori

SUM does not generate the SAP Fiori launchpad, so after a conversion the launchpad is set up with Rapid Activation . It works only with the embedded deployment, which is recommended since SAP S/4HANA 1909. The task list SAP_FIORI_FOUNDATION_S4 activates the launchpad, scopes apps from SAP business role templates in the development system, and activates the customer roles in the quality system before they are transported to production. It creates the foundational roles SAP_FLP_USER and SAP_FLP_ADMIN and two composite roles with a customer prefix, for example Z_FIORI_FOUNDATION_USER and Z_FIORI_FOUNDATION_ADMIN , to which customers add their other roles.

Tip

Readiness Check = what changes (simplification items and more); Simplification Item Check = consistency check in the Maintenance Planner before SUM; Custom Code Migration app = which code must be adapted.