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

Lesson 5 of 5

What changed from ECC

9 min

Contoso's order-to-cash users have worked in SAP ECC SD for years. Most of their transactions still exist in SAP S/4HANA, and a seasoned user can enter an order in VA01 on day one. Underneath, several things changed. Some change what users do; others change what the system stores, which matters for reports, interfaces and tests. SAP lists all of them as simplification items, and the readiness check for a conversion reports which ones affect a given system.

AreaECC SDSAP S/4HANA
Customer masterCustomer maintained with XD01 / VD01Business partner with customer roles; customer vendor integration keeps them in step
Credit managementFI-AR credit management; SD check types A, B, CSAP Credit Management; check type D
Document statusSeparate status tables for header and itemStatus fields held directly on the document header and item tables
Pricing dataPricing conditions in a cluster tableA new pricing element table; custom code that read the old table must change
OutputMessage control with condition-based outputNew output management is the default for many documents; classic output still possible in places
RebatesSD rebate agreementsSettlement management with condition contracts
Material numberUp to 18 charactersUp to 40 characters, where activated
User interfaceSAP GUI transactionsFiori apps alongside SAP GUI transactions
The main order-to-cash changes from ECC SD to SAP S/4HANA.
The Sign-Off Table · thesignofftable.com/academy/sap-sd-101

Changes users notice

Business partner. New customers are created as business partners with roles, not with the old customer transactions. Great Lakes Fleet Services is one business partner with a customer role for financial data and another for sales data in sales area 1710 / 10 / 00. The sales master data course covers this in detail.

Credit management. Credit limits sit on the business partner in SAP Credit Management, and orders that fail the check are released through its release functions. Credit controllers learn new screens; sales users see a credit block as before.

Fiori apps. Apps such as Manage Sales Orders, Sales Order Fulfillment monitoring and Manage Billing Documents give list views, filters and drill-downs that replace several ECC lists. The old transactions remain for users who prefer them.

Changes that matter for reports and tests

Status tables. ECC kept order and delivery status in separate tables; SAP S/4HANA stores status fields on the documents themselves. Pricing. The pricing conditions of documents moved to a new table. Document flow was simplified as well. Standard programs were adjusted, but custom reports and interfaces that read the old tables must be remediated, and any report that changed must be compared with ECC results in testing.

Output. Order confirmations and invoices may be produced by the new output management rather than the ECC message control. Forms, email settings and print routing are often rebuilt, which makes invoice output a common source of go-live defects. Test the content, the channel and the recipient of every output type the business uses.

Some things did not change, and it helps to say so to anxious users. Order types, item categories, copy control, pricing procedures, partner determination and the document chain itself work as they did in ECC. A conversion keeps Contoso's configuration of these, so a well-run order-to-cash process in ECC remains recognizable on day one. The testing effort belongs where the data model or the tooling changed.

Light touchFiori list apps alongside known transactions
Train and test the processCredit management screens and release; business partner maintenance
Remediate and compareStatus and pricing tables read by custom reports and interfaces
Rebuild and test end to endOutput management, rebates moving to settlement management
How much testing each ECC-to-S/4HANA change needs at Contoso.
The Sign-Off Table · thesignofftable.com/academy/sap-sd-101

What would you do?

After Contoso's first test conversion, the custom 'open orders by customer' report shows every order as open, including fully billed ones. ECC showed the right result. What is the most likely cause?

Key points
  • Simplification items list every change; the readiness check shows which apply to your system.
  • Users notice the business partner, SAP Credit Management and Fiori apps.
  • Status fields, pricing data and document flow changed in the data model; remediate and compare custom reports.
  • Output management and rebate processing changed; test output content, channel and recipient end to end.

Check your understanding · not graded

Lesson check

  1. 1. In SAP S/4HANA, where are sales document status fields stored?

  2. 2. What replaces SD rebate agreements in SAP S/4HANA?

  3. 3. Why is invoice output a common source of go-live defects after conversion?

  4. 4. Where do you find which simplification items affect Contoso's system?