Connect Salesforce demand to SAP fulfillment

Start with a decision a team can make

A useful cross-system question is which committed customer orders associated with an agreed sales cohort are at risk of missing a promise date. Asking whether all pipeline can be fulfilled mixes uncertain demand with confirmed orders. Keep those populations separate so planners know what action a result supports.

Identify the opportunity-to-order relationship and the product mapping. One opportunity may create multiple orders, while an order can contain lines unrelated to the particular opportunity being reviewed. A shared customer identifier is not enough to allocate every line correctly.

Use an exception that exposes the mapping

Synthetic example: a commercial commitment covers 100 units of product A. SAP contains an associated line for those 100 units and a separate line for 20 units of product B. Deliveries cover 70 units of A and all of B. Customer-level quantities produce 90 delivered units; the relevant commitment still has a 30-unit gap.

Review product A at its mapped order-line grain. Then compare the requested date, confirmed promise and delivery checkpoint under the agreed calendar. Record which date drives the exception rather than choosing whichever makes a delay disappear.

• MappingOpportunity, order, line and product identifiers with unmatched records retained.
• QuantityRequested, rejected, delivered and returned quantities in compatible units.
• TimeNamed cutoff and the original or revised promise selected by the owner.

Separate observed gaps from predicted causes

A shortage at the checkpoint does not prove a supplier failure or a future missed delivery. Explanations need additional evidence such as approved supply, shipment or change records. Where the connected sources do not contain that evidence, present the gap as a review task.

Check access on both sides. A sales manager may be entitled to an account without being entitled to every financial or operational detail held by the ERP. Source combinations should narrow to the permitted use case, not create a new route to sensitive fields.

Use the same exception in the demonstration

Bring one partial delivery, one rejected line and one unmapped deal to a Nexatron session. Confirm the exact supported source objects and review the result with both owners. The acceptance question is whether the workflow identifies the right exceptions with the right limitations, not whether it can join two vendor names.