Order to Cash · EXPLORE · Prepared for Order-to-Cash Process Owner · 8/4/2026
Customer-order processing moves from email, spreadsheets, manual checks, and legacy entry to an integrated SAP S/4HANA sales-order process.
Pricing, discount approval, availability, credit, order status, and confirmation become visible and controlled within one process.
Customer service, sales management, pricing, and credit roles experience the largest changes.
Confirm role ownership, approval authority, pricing-data governance, exception handling, training, and spreadsheet retirement.
A customer sends a purchase order by email to the sales representative. The sales representative checks customer pricing in a spreadsheet or legacy pricing screen, requests approval by email for special discounts, contacts the warehouse or planning team for availability, and contacts the credit team when the customer may exceed the credit limit. The approved information is sent to customer service, which manually enters the order in the legacy ERP and emails the confirmed quantity and delivery date to the customer.
The customer purchase order is received by sales or customer service and entered into SAP S/4HANA. During sales-order creation, SAP determines customer pricing, applies eligible discounts, routes exceptional discounts for approval, performs available-to-promise and credit checks, proposes a confirmed delivery date, records approval and order status, and provides order-confirmation information from the same process.
The end-to-end process becomes integrated and exception-driven.
Order information moves through email, spreadsheets, separate teams, and legacy entry.
Customer service manages pricing, availability, credit, approval, and confirmation in one SAP order flow.
Users shift from informal follow-up to monitored exception queues.
Discount and credit exceptions are coordinated through email and direct contact.
Exceptional discounts and credit blocks become visible approval or release work.
Customer communication uses a single system record for confirmation details.
Customer service emails confirmed quantity and delivery date after legacy entry.
Acknowledgement information is sourced from the SAP sales order.
The role gains broader process accountability and system decision points.
Customer service receives approved information and performs legacy entry.
Customer service creates complete SAP orders and resolves or routes exceptions.
Routine price calculation is removed while exception awareness remains.
Sales checks or calculates customer pricing using a spreadsheet or legacy screen.
Sales reviews determined pricing without freely overwriting the base price.
Decision rights become explicit, traceable responsibilities.
Approvals and credit questions are handled through email or direct contact.
Managers approve exceptional discounts and credit analysts release blocked orders.
Users move their daily order work into SAP S/4HANA.
Email, spreadsheets, legacy screens, and manual contacts support order processing.
SAP sales-order, pricing, ATP, credit, approval, and status capabilities support the flow.
A familiar shadow tool is removed only after the replacement is proven.
Sales uses a spreadsheet as part of routine pricing work.
Configured pricing conditions provide routine pricing after stabilization.
Pricing quality depends on accurate records, validity dates, and maintenance ownership.
Customer pricing is checked in a spreadsheet or legacy pricing screen.
SAP determines pricing from eligible condition records.
Customer, material, sales-area, credit, partner, and shipping data become operational prerequisites.
People bridge information gaps through manual contact and local knowledge.
Pricing, ATP, credit, delivery-date, and confirmation outcomes use governed SAP data.
The approval threshold and evidence become consistent and auditable.
Special-discount approval is requested through email.
Discounts above 10% require sales-manager approval.
Credit exceptions move to a visible block-and-release control.
Sales contacts credit when a customer may exceed a limit.
SAP performs the check and the credit team releases blocked orders.
Operational follow-up can use a shared source of order status.
Status is fragmented across email, teams, and legacy screens.
SAP records order and approval status in the same process.
Trackers should retire only after replacement reports are accepted.
Local spreadsheets and email provide informal tracking.
SAP order and exception reporting supports operational visibility.
Training must cover the normal process and role-specific exceptions.
Users rely on legacy screens, spreadsheets, email, and team knowledge.
Each role performs defined SAP order, approval, pricing, ATP, credit, or monitoring activities.
Process communications must reinforce new ownership and sources of truth.
Work instructions and confirmations reflect the email and legacy process.
SOPs and acknowledgement guidance reflect SAP data and exception handling.
Testing must cover normal results, exceptions, rejections, blocks, and incomplete data.
Checks are performed separately and confirmed through people.
Interdependent SAP checks determine whether and how an order proceeds.
Deployment needs measurable exit criteria, support ownership, and a recoverable archive.
The pricing spreadsheet supports ongoing work.
It retires after the SAP process has stabilized.
Business Process Owner
Confirm the assessment-level handoff explicitly. Individual impact decisions never change this status.
Review can be recorded with proposed impacts remaining; no impact is accepted automatically.
OCM Lead or Analyst
Convert reviewed impacts into owned work. These records are separate from the AI recommendations below.
Seed the plan from reviewed recommendations or add a human-owned action.
Human-controlled lifecycle
Action updates never advance this lifecycle automatically.
Business Process Owner review
Expand to accept, edit, or dismiss role changes without altering impact decisions.
| ID | Impact | Owner | Timing | Status |
|---|---|---|---|---|
| IMP-001 | Integrated sales-order processing Process | Order-to-Cash Process Owner | explore | proposed |
| IMP-002 | Exception-driven approval and release Process | Order-to-Cash Process Owner | realize | proposed |
| IMP-003 | SAP-based order acknowledgement Process | Order-to-Cash Process Owner | realize | proposed |
| IMP-004 | Customer service becomes the order-processing owner People & roles | Order-to-Cash Process Owner | explore | proposed |
| IMP-005 | Sales shifts from price calculation to review People & roles | Pricing Analyst | explore | proposed |
| IMP-006 | Managers and credit analysts own formal exception decisions People & roles | Order-to-Cash Process Owner | realize | proposed |
| IMP-007 | SAP becomes the order-processing system of work Technology | Order-to-Cash Process Owner | realize | proposed |
| IMP-008 | Pricing spreadsheet retires after stabilization Technology | Pricing Analyst | hypercare | proposed |
| IMP-009 | Pricing conditions require governed ownership Data | Pricing Analyst | realize | proposed |
| IMP-010 | Order checks depend on complete master data Data | Order-to-Cash Process Owner | realize | proposed |
| IMP-011 | Discount threshold becomes a system control Controls | Sales Manager | explore | proposed |
| IMP-012 | Credit blocks and releases become auditable Controls | Credit Analyst | realize | proposed |
| IMP-013 | Order status becomes centrally visible Reporting | Order-to-Cash Process Owner | realize | proposed |
| IMP-014 | Shadow trackers need controlled retirement Reporting | Order-to-Cash Process Owner | deploy | proposed |
| IMP-015 | Role-based order and exception training Training & communication | Order-to-Cash Process Owner | test | proposed |
| IMP-016 | SOPs and customer communication must change Training & communication | Order-to-Cash Process Owner | test | proposed |
| IMP-017 | End-to-end pricing, ATP, and credit testing Testing & deployment | Order-to-Cash Process Owner | test | proposed |
| IMP-018 | Stabilization controls spreadsheet retirement Testing & deployment | Order-to-Cash Process Owner | hypercare | proposed |
| Action | Owner | Timing | Priority |
|---|---|---|---|
| ACT-001 · Confirm the future sales-to-customer-service handoff. | Order-to-Cash Process Owner | explore | high |
| ACT-002 · Approve the discount threshold scope and approver matrix. | Sales Manager | explore | high |
| ACT-003 · Define credit-release evidence, delegation, and escalation. | Credit Analyst | realize | high |
| ACT-004 · Assign pricing-condition ownership and quality controls. | Pricing Analyst | realize | high |
| ACT-005 · Define ATP exception handling and customer communication. | Order-to-Cash Process Owner | realize | high |
| ACT-006 · Inventory and remediate critical order master data. | Order-to-Cash Process Owner | realize | high |
| ACT-007 · Design role-based learning paths and practice exercises. | Order-to-Cash Process Owner | test | high |
| ACT-008 · Revise SOPs, job aids, and acknowledgement guidance. | Order-to-Cash Process Owner | test | medium |
| ACT-009 · Define role-specific order and exception reporting. | Order-to-Cash Process Owner | realize | medium |
| ACT-010 · Inventory spreadsheet trackers and replacement controls. | Order-to-Cash Process Owner | deploy | medium |
| ACT-011 · Execute the integrated business test pack. | Order-to-Cash Process Owner | test | high |
| ACT-012 · Approve stabilization exit criteria before spreadsheet retirement. | Order-to-Cash Process Owner | hypercare | high |
| Audience | Learning need | Intervention | Timing |
|---|---|---|---|
| Customer Service Representatives | Create, validate, and manage SAP sales orders and exceptions. | Role-based course, exercises, and desk guide. | Before UAT and reinforced before go-live. |
| Sales Representatives | Review SAP pricing and raise governed exceptions. | Scenario workshop and job aid. | Before UAT. |
| Sales Managers | Approve or reject exceptional discounts and manage delegation. | Workflow simulation and quick reference. | Before UAT. |
| Pricing Analysts | Maintain conditions and resolve pricing exceptions. | Advanced role course and data exercises. | Before integration testing. |
| Credit Analysts | Review and release credit blocks with evidence. | Role course and exception exercises. | Before integration testing. |
| Warehouse or Supply Planning Users | Support ATP exceptions and interpret confirmation outcomes. | Targeted briefing and scenarios. | Before UAT. |
| Order-to-Cash Process Owner | Monitor process, control, adoption, and stabilization measures. | Process-owner dashboard walkthrough. | Before deployment. |
Verify valid pricing, availability, credit, and confirmation.
Verify the eligible customer price is determined.
Verify an eligible discount below 10% does not require exceptional approval.
Verify a discount above 10% routes to the sales manager.
Verify rejection status and order resolution.
Verify the exception is visible and routed without invented pricing.
Verify full confirmation for the requested date.
Verify partial confirmation and exception communication.
Verify no-confirmation behavior and follow-up.
Verify the order proceeds without a credit block.
Verify the order is blocked for credit review.
Verify authorized release and retained history.
Verify incompletion prevents an unsupported confirmation.
Confirm supplied country variations without assuming unprovided rules.
Business Process Owner review
Expand to assign, edit, accept, or dismiss open questions before handoff.
Email-based customer orders remain in scope for the initial deployment. Basis: The To-Be continues to receive purchase orders through sales or customer service.
The supplied impacted-role list is complete for this workshop assessment. Basis: The list is explicit in the workshop input.
No EDI or customer self-service capability is delivered in this phase. Basis: The workshop decision explicitly places both in a future phase.
Synthetic reference capabilities are illustrative rather than customer configuration. Basis: The lab has no live SAP connection.
Validation score: 100/100 · MCP: sample · Model: sample-fixture · 0 model steps