SAP SD Interview Questions and Answers

The pricing procedure is determined (in configuration, transaction OVKK) from three values:

• Sales area – sales organisation, distribution channel, division.
• Document pricing procedure – assigned to the sales document type (and billing type).
• Customer pricing procedure – maintained in the customer's sales area data.

This lets the same company use different pricing logic for, say, domestic and export customers, or for standard orders versus free-of-charge orders.

The condition technique is SAP's generic determination method, used for pricing, output, free goods, material determination and more:

1. Field catalogue – allowed fields.
2. Condition tables – key combinations, for example *sales org / customer / material*.
3. Access sequence – the order in which tables are searched, from specific to general, with an exclusive indicator to stop after the first hit.
4. Condition type – the pricing element, linked to an access sequence.
5. Procedure – sequence of condition types with subtotals, requirements and account keys.
6. Condition records – the actual values.

• Step / counter – sequence of conditions.
• From / to – the base for percentage conditions, such as a discount on gross price.
• Manual – condition is only applied when entered manually.
• Required – pricing is incomplete if the condition is missing (typical for the base price).
• Statistical – shown but not added to the net value, for example cost (VPRS).
• Subtotal – stores values in fields used for reporting or later calculation.
• Requirement – a routine that decides if the condition applies.
• Alternative calculation type / base value – routines that change how a condition is calculated.
• Account key / accrual key – used for revenue and accrual account determination.

Copy control defines how data flows from a source document to a target document and which checks apply. Main transactions:

• VTAA – sales document to sales document (for example quotation to order).
• VTLA – sales document to delivery.
• VTFA – sales document to billing (order-related billing).
• VTFL – delivery to billing.
• VTFF – billing to billing (for example invoice to cancellation).

Settings exist at header, item and schedule line level: copy requirements, data transfer routines, whether document flow is updated, and the pricing type that decides whether prices are copied or redetermined in billing.

Revenue account determination (VKOA) uses the condition technique. Typical access fields are chart of accounts, sales organisation, customer account assignment group, material account assignment group and the account key from the pricing procedure (for example ERL for revenue and ERS for sales deductions). If a key combination is missing, the billing document cannot be released to accounting.

In S/4HANA, credit checks in sales documents use SAP Credit Management (FIN-FSCM). The credit check is triggered according to settings for the sales document type and credit control area, and if the business partner's exposure exceeds the limit, the order or delivery is blocked. The credit team reviews and releases blocked documents, often through documented credit decisions. Classic SD credit management is not used in S/4HANA.

1. A sales order item gets item category TAS (through the item category group or manually).
2. Schedule line category CS creates a purchase requisition automatically; no outbound delivery is created.
3. Purchasing converts it into a purchase order to the supplier, who ships directly to the customer.
4. The supplier invoice is posted in MM; a statistical goods receipt can be used if required.
5. The customer is billed, typically based on the supplier invoice quantity.

In an individual purchase order (item category TAB), the supplier delivers to your plant, where stock is received as customer-specific special stock, and then you deliver to the customer through a normal outbound delivery. In third-party, the supplier delivers directly to the customer and no outbound delivery is created.

Consignment stock remains your property while stored at the customer's site, tracked as special stock.

• Fill-up (KB, item KBN) – moves stock to the customer; not billed.
• Issue (KE, item KEN) – customer consumes stock; delivered and billed.
• Pick-up (KA, item KAN) – unused stock returned to your plant.
• Returns (KR, item KRN) – customer returns consumed goods; credit issued.

A returns order (RE, item REN) is created with reference to the original invoice or order, usually with an order reason and a billing block. A returns delivery receives goods back into stock, typically into blocked stock first (movement type 651) for inspection. After approval, the billing block is removed and a credit memo is created. S/4HANA also offers Advanced Returns Management for inspection and refund control.

Credit memo requests (CR) and debit memo requests (DR) correct invoice amounts without physical goods movement, for example a price difference or late delivery penalty. They usually carry a billing block so that a supervisor can approve before the credit memo (G2) or debit memo (L2) is created.

A customer orders from sales organisation A (company code 1000), but the goods are delivered from a plant belonging to company code 2000. The process:

1. Sales order in sales org A with a delivering plant from company 2000.
2. Delivery and goods issue from the plant of company 2000.
3. Customer invoice (F2) from company 1000 to the end customer.
4. Intercompany invoice (IV) from company 2000 to company 1000, using an internal price condition such as PI01.

Configuration includes allowing the plant for the sales area, an internal customer representing company 1000, and the intercompany billing type.

S/4HANA offers output management based on BRF+ (output parameter determination), with output types, determination rules, channels such as email or print, and form templates. Classic NAST-based output determination using the condition technique is still supported for SD in many on-premise systems, and projects choose per application. Know which one your project used and how you configured an email output.

• Shipping point = shipping conditions (from customer or sales document type) + loading group (material master) + delivering plant.
• Route = departure zone of the shipping point + shipping conditions + transportation group (material) + transportation zone of the ship-to party; it can be redetermined in the delivery using the weight group.

The system checks, in order: the customer-material info record, the ship-to party's customer master, and then the material master sales data. If no plant is found, it can be entered manually; without a plant, availability check and delivery are not possible.