NEOKNOVA
KNOWLEDGE TRANSFER  ·  ACCELERATED
Performance support · at the moment of need
in-app prompts

Standard Sales Order — Performance Support

The just-in-time prompts that surface in the system as the rep works — each tied to a screen, so help arrives exactly where people hesitate. Blue cards are the SAP step; gold cards are the decision points, where SAP makes a check and the rep handles what it finds. This pack is the content; in a rollout it drives an in-app overlay (DAP).

Creating the order
On screen · Fiori launchpad

Open the right app

Open the Create Sales Orders app — the Fiori successor to the classic VA01 transaction.

On screen · initial dialog

Name the order and the sales area

Enter order type OR and sales area 1010 / 10 / 00, then Continue.

Why it matters: the sales area (sales org · distribution channel · division) sets which customers, materials and pricing apply — wrong area, wrong rules.
On screen · Sold-To Party

Enter the customer, let the master fill the rest

Type the Sold-To number and press Enter. The Ship-To party and customer details derive from the customer master via partner determination.

If nothing populates: check the number against the customer master — the partner functions come from there, not from re-keying.
On screen · items · pricing

Add the line — and read the price right

Enter the material and quantity. The description comes from the material master; the net price is set by the condition technique (pricing procedure → access sequence → condition record).

If the price looks wrong: it's a pricing condition, not the material master — flag it to whoever owns pricing; don't edit the material to "fix" a price.
The decision points — SAP checks, you handle it
Decision · free goods

SAP applies the deal — you own the conversation

The SAP mechanic

When the quantity meets the free-goods condition record, SAP automatically adds a free-of-charge line. No one keys it in.

In practice

Verify the free line matches the promotion you know about, and tell the customer they're receiving it. If it's missing where you'd expect it, or the quantity's wrong, escalate rather than save.

Decision · availability (ATP)

Can the date be met?

The SAP mechanic

SAP runs an availability check (ATP) in the plant (advanced ATP: product allocation, supply protection): full, partial (a later date), or zero stock.

In practice

If only a later date can be met, communicate that proposed date to the customer before you commit — don't let a late delivery be how they find out.

Decision · backorder

Zero stock — backorder or not?

The SAP mechanic

If the customer is eligible, a pop-up (custom backorder check) prompts; the line can be processed as a backorder. If not eligible, the line is auto-rejected with a reason (custom rejection handler).

In practice

Ask the customer before placing a backorder. If they're not eligible and the line is rejected, offer an alternative — a substitute, a partial, a new date — not a flat "no".

Decision · credit block

Credit hold — don't override it

The SAP mechanic

SAP runs a credit check in the background (credit history + risk group). The order is clear, or blocked for credit.

In practice

A credit block isn't yours to release. Inform the customer the order is on hold and contact Credit Control to run the analysis — you're the bridge between the two.

Committing the order
On screen · Save · warnings dialog

Commit the promise

Choose Save and confirm the warnings dialog. SAP writes the order and returns a sales order number.

The confirmation dialog is a final "are you sure?", not an error — read it, then confirm.
NeoKnova · Performance Support · Standard Sales Order · v2026-06-10
← Dashboard