Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 6

Scenario setup

8 min

This course follows one connected story through three core processes. Contoso Motor Co. buys rotors from a supplier, uses them to build alternators in its Detroit plant, and sells the alternators to a fleet customer. Each process is often taught, configured and tested by a different team. Seeing them as one chain is what turns a collection of passing tests into confidence that the business works.

The structure mirrors SAP's own Executing Basic ERP Processes with SAP S/4HANA learning journey (procure to pay, plan to produce, order to cash) and the SAP Best Practices scope items behind it: J45 Procurement of Direct Materials, BJ5 Make-to-Stock Production for discrete manufacturing, and BD9 Sell from Stock. You can explore those process flows in SAP Signavio Process Navigator.

  1. Procure to payBuy 100 rotors CMC-RTR-200 from Lakeside Components
  2. Plan to producePlan and build 100 alternators CMC-ALT-100 in plant 1710
  3. Order to cashSell and ship 50 alternators to Great Lakes Fleet Services and collect payment
The tour: three processes, one chain of value.

The organization

Org unitContoso valueRole in the tour
Company code1710 (Contoso Motor Co., USD)Every journal entry in the tour posts here
Plant1710 DetroitReceives rotors, produces alternators, ships to the customer
Second plant1720 ChicagoNot used in this tour; a good variant for later tests
Purchasing organization1710Buys from the supplier
Sales areaSales org 1710, distribution channel 10, division 00Sells to the customer
Storage locationThe plant's standard storage locationHolds both rotors and finished alternators

Contoso's organizational setup for the tour.

Master data that must exist before you start

An end-to-end tour fails in the first five minutes if the data is not ready. Check this list before anything else:

Business partnersSupplier Lakeside Components with supplier roles for company code 1710 and purchasing org 1710. Customer Great Lakes Fleet Services with customer roles for company code 1710 and sales area 1710 / 10 / 00.
ProductsRotor CMC-RTR-200 (raw material): purchasing, MRP and accounting views for plant 1710. Alternator CMC-ALT-100 (finished good): sales views for 1710 / 10, MRP, work scheduling and accounting views for 1710, with a standard price of 160.00 USD.
Production master dataBill of material for CMC-ALT-100 in plant 1710 (one rotor plus other components), a routing with assembly and test operations, work centers, and a production version.
Purchasing dataPurchasing info record: rotor from Lakeside at 40.00 USD; source list if your project requires one.
PricingSales price condition for CMC-ALT-100 at 250.00 USD, valid on the test dates.
FinanceOpen posting period in company code 1710; G/L accounts and account determination for inventory, GR/IR, cost of goods sold and revenue; cost centers for the work centers; profit center for alternators.
Pre-tour master data, from partners to finance.

Who does what

Each step in the tour belongs to a role. In SAP S/4HANA these map to business roles in the Fiori launchpad, such as purchaser, warehouse clerk, accounts payable accountant, production planner, production operator, internal sales representative, shipping specialist, billing clerk and accounts receivable accountant. Running the tour with a single super-user ID proves the process works technically; running it with real role IDs proves that people can actually do their jobs. Plan for both.

How to use this tour

You can follow the tour in three ways. As a reader, use it to understand how your own team's step fits into the whole. As a key user, run it in a test or training client with the documents and checks described, and keep the document numbers as your evidence. As a test designer, use it as the backbone of an integration test: one happy path through all three legs, then variants that each change one thing.

  • Plant variant: repeat the sell-from-stock leg from plant 1720 Chicago after a stock transfer from Detroit.
  • Price variant: let the supplier invoice arrive at 42.00 USD instead of 40.00 USD and follow the price variance.
  • Scrap variant: confirm two scrapped alternators and follow the production variance into settlement.
  • Partial variant: ship 30 alternators now and 20 next week, and follow two deliveries and two invoices.

Everything in this tour applies to SAP S/4HANA Cloud Private Edition and on-premise. In Public Edition the same processes and documents exist, but you work only through Fiori apps and the SAP GUI transaction codes shown here are not available.

What would you do?

A Contoso key user wants to start the end-to-end tour this afternoon. The product team confirms the alternator and rotor exist, but nobody has checked the BOM, routing or production version. What should the key user do?

Key points
  • The tour follows one chain: buy a component, build the product, sell it.
  • It mirrors SAP's basic ERP processes journey and Best Practices scope items J45, BJ5 and BD9.
  • Partners, products, production data, purchasing data, prices and finance settings must all exist first.
  • Write expected values before you post anything.
  • Run with role-based users, not only a super-user.

Check your understanding · not graded

Lesson check

  1. 1. Which SAP Best Practices scope item covers selling from stock?

  2. 2. Which master data is needed for the plan-to-produce leg in addition to the product?

  3. 3. Why run the tour with role-based user IDs?

  4. 4. What is the expected revenue for 50 alternators at 250.00 USD?