A salesperson marks an opportunity as qualified, but the fulfilment team cannot find a sales order. That can be a valid business state: qualification records the likelihood and readiness of a deal; an accepted order records a commitment that the receiving system can process. This SAP CRM learning exercise explains how to investigate the gap without creating a duplicate order.
Identify the product before choosing a troubleshooting path
Classic SAP CRM and SAP Sales Cloud are different products. Classic CRM landscapes can use CRM Middleware and configured ERP integration. Sales Cloud integrations use the services and integration architecture selected for that cloud product and version. A screen, queue name or transaction from one landscape should not become a universal instruction for the other.
For this fictional case, assume classic SAP CRM connected to an ERP order-processing system. The business has agreed that an authorised sales user creates an order from an accepted quotation, and the configured integration transfers eligible orders. These are exercise assumptions, not standard behaviour guaranteed in every installation.
For the wider document sequence, read the existing SAP CRM lead-to-order guide. This exercise focuses on the evidence needed at the handoff.
Worked case: a qualified opportunity for ten pumps
Fictional customer Harbour Engineering needs ten pumps. Opportunity O-410 lists ten units at an indicative Rs. 8,000 each, so its estimated value is Rs. 80,000 before tax and freight. That arithmetic describes the opportunity estimate. It does not prove that pricing, tax, credit or delivery conditions have been accepted.
The customer later accepts quotation Q-410 for eight pumps at Rs. 8,200 each: Rs. 65,600 before tax and freight. An authorised user creates CRM order C-410 for those eight units. The exercise expects one receiving ERP order, E-920, referencing C-410. Record the source and receiving identifiers separately; identical document numbers are not a requirement.
If the opportunity remains at ten units while the order contains eight, that difference can be legitimate. Reconcile against the accepted quotation and actual order, rather than forcing every stage to match the first estimate.
Find the first missing piece of evidence
- Commercial decision: inspect the quotation, acceptance evidence and approval requirements. A qualified opportunity without acceptance may simply need another sales action.
- Source order: establish whether C-410 exists, has the expected items and is eligible for transfer under the configured transaction type and status rules.
- Master-data mapping: confirm the customer, ship-to party, product, unit of measure and organisational assignments needed by the receiving system. A readable customer name is insufficient evidence that its identifiers are correctly mapped.
- Integration evidence: ask an authorised support user to inspect the relevant message, queue or monitoring record for this landscape. Capture its timestamp, correlation information and full error.
- Receiving document: search using the supported source reference and confirm the ERP order’s customer, quantity and document flow. Message submission alone does not establish successful business-document creation.
Diagnose without multiplying the problem
Suppose the first transfer failed because the receiving customer lacked the required sales-area data. Correcting that master data does not justify repeatedly pressing a create button. First determine whether the source order is waiting for supported reprocessing, whether a retry already completed, or whether an ERP order exists but its acknowledgement has not returned.
Use the system’s authorised retry or recovery process after checking document references. The business should define how duplicate requests are identified; do not assume every interface has the same duplicate-protection mechanism. Preserve the original failed message and relate the recovery result to it.
An ERP order may also exist with a delivery or credit block. In that case, the handoff succeeded, while fulfilment needs a separate investigation. “No delivery” and “no order” are different symptoms.
Acceptance checks for a training exercise
- Qualifying O-410 alone creates no ERP order under this exercise’s agreed process.
- Accepted quotation Q-410 and CRM order C-410 show eight pumps and the correct agreed commercial details.
- Exactly one receiving order references C-410 after successful processing; a controlled repeat does not create a second commitment.
- A deliberate missing-data case produces traceable failure evidence and a documented supported recovery.
- The final explanation distinguishes order creation, acknowledgement and readiness for delivery.
These are expected checks, not results from an executed SAP test. Keep actual outcomes, screenshots and timestamps only when you run the scenario in an authorised training system. To connect this investigation with sales, service and ERP integration learning, review Softenant’s SAP CRM training in Vizag and confirm the product and practice landscape used by the batch.