Pricing Procedure Not Determined in Sales Order

The order desk reports that a new sales order has no price at all, not a wrong price, no price. The conditions tab is blank, sometimes with a system message saying no pricing procedure could be determined, sometimes just an empty screen the user does not know how to read. It is usually reported as the order 'won't calculate' or 'has no conditions tab data,' and it tends to surface right after a new sales organization, plant, or customer account is rolled out, or when an existing customer places the first order in a distribution channel or division they have never ordered through before. The complaint is almost always tied to a specific customer and sales area combination rather than a specific material, which is the first clue this is a determination problem and not a missing condition record.

Pull open and recently created sales orders filtered by the sales area and customer in question and check the pricing procedure field on the order header, it will be blank or show a value that does not match what is expected for that document type. Cross-reference the customer pricing procedure value on the customer master against the pricing procedure determination table entries for the same sales organization, distribution channel and division, a missing row confirms the determination gap rather than a data entry mistake on one order.

If the customer master is missing the customer pricing procedure value or the customer has not been extended to the sales area, this is a master data fix, done directly on the customer record, no transport needed. If the pricing procedure determination table is missing the combination entirely, this is a configuration change and must go through the transport process, it cannot be patched on a single order. If the document pricing procedure on the sales document type or item category is wrong, that is also a config change requiring transport, and should be checked against other order types in the same landscape to confirm the fix does not break a working combination elsewhere. If the item category pricing relevance flag is the cause, correcting it is config but carries wider impact since the item category is shared across many document types, so it needs impact analysis before transport, not a same-day fix. Copy control issues are config as well, adjusted per source-to-target document type pair.

The reflex fix is to manually re-enter or re-key the order, or to copy an existing working order as a template and swap the material and quantity. This sometimes appears to work if the new order happens to land in a sales area that already has a valid determination entry, which convinces the team the original order was just a fluke. It is not a fluke, it is missing configuration or master data for that specific combination, and the next order placed for that customer or sales area fails the same way. Manually keying condition types into the item is not possible either, since without a procedure there is no pricing screen structure to key values into.

Owned by the SD pricing configuration team, since the fix is either a determination table entry or a document type setting, both transportable objects. Order management raises the ticket. The handover note should specify the exact sales organization, distribution channel, division, customer pricing procedure and document pricing procedure combination that failed, plus whether the customer master extension is also missing, so config and master data owners are not chasing two separate causes as one.