SAP SD / O2C Item Categories Interview Questions

Item Categories comes up in SAP SD / O2C interviews because it is one of the few areas where an interviewer can tell, in two questions, whether you have worked with the process or only read about it.

Item Categories control how each sales document line behaves in SD processing - determining pricing relevance, billing relevance, delivery relevance, schedule line usage, and whether an item is a standard product, free good, text item, value item, or service. This topic covers item category purpose, determination logic, configuration, and how item category settings drive document flow, integration, and troubleshooting across ECC and S/4HANA.

This page carries 20 reviewed SAP SD / O2C item categories interview questions, each with a complete written answer and no sign-in required. The set is 16 mid-level and 4 advanced — this is a topic interviewers use to separate candidates, so there is no warm-up section.

The fastest way to use this page is to read the question, answer it yourself, and only then read the answer. The gap between your version and the written one is your actual revision list for item categories.

20 Item Categories questions with answers

mediumItem Categories

1. A customer orders a configurable material (variant configuration) that must be individually produced (MTO), but the same order also contains a standard stock item shipped from existing inventory. How would you set up item categories and copy control so both items flow correctly through delivery and billing without cross-contamination of requirements?

Use item category determination (VOV4) so the configurable material's item category defaults to TAC (or similar MTO-relevant category with individual requirements 'E' in the strategy group), while the standard item defaults to TAN with collective requirements. Copy control (VTLA for delivery, VTFA for billing) is set at item category level, ensuring each item category has its own requirement type and account assignment. This keeps the configurable item's TOR tied to the specific sales order (individual customer stock) while the standard item consumes from unrestricted stock, preventing requirement mixing.
mediumItem Categories

2. For a make-to-order sales scenario, an item category determination is returning the standard TAN category instead of the expected TAB (individual purchase order) category. What determination factors and master data should you review?

Item category determination depends on sales document type, item category group from the material master (should be set to a value like 0002 or a custom MTO-specific group), usage, and higher-level item category. Verify the item category group on the material master's sales org view is correctly set for individual purchase order processing, and check the item category determination table (VOV4) has an entry combining the document type and that item category group pointing to TAB. Also confirm no manual item category override exists in the order.
mediumItem Categories

3. A returns process (RE order type) is copying from a standard billing document, but the returned item category is defaulting to a standard delivery-relevant category instead of a returns-specific one, causing incorrect stock posting logic downstream. How would you diagnose and fix this via item category determination and copy control?

Check item category determination (VOV4) for the combination of sales document type RE, item category group of the material, usage, and higher-level item category — it should resolve to REN, not TAN. If the entry is missing or incorrectly mapped, add/correct the VOV4 entry. Also verify copy control (VTAF for order-to-order, or relevant billing-to-order) at item category level specifies the correct target item category and copying requirements routine, since copy control can override determination logic when copying with reference.
mediumItem Categories

4. A customer places an order for a promotional free sample alongside a paid product. How should item category determination be configured to correctly process the free-of-charge item without triggering pricing or credit issues?

The free item is entered with a separate order type or the main item plus a free goods sub-item using item category TANN (free of charge item, no pricing, statistical value only) determined via item category determination (VOV4) based on item category group and usage indicator. TANN is not relevant for pricing (pricing procedure determination excludes it) and typically not credit-relevant, while cost is still tracked via VPRS for margin reporting. The higher-level item TAN remains billing-relevant for the paid product.
mediumItem Categories

5. A customer's sales order uses material substitution (via the condition technique, e.g., material determination) to automatically replace an obsolete material with its successor, but the item category determined for the substituted material routes it through a third-party procurement flow instead of the expected standard stock delivery. How would you diagnose and correct this within item category determination?

First confirm the substitution itself worked correctly by checking the material determination condition record and log, then examine item category determination inputs on the substituted line - specifically the item usage and the successor material's item category group in the material master, which may still carry a third-party-oriented group (e.g., BANS) inherited from setup rather than the intended standard group (NORM). Correct by updating the successor material's item category group or adding an explicit item category determination entry for the substitution's resulting combination, then retest via VA01 to confirm TAN determines instead of TAS.
mediumItem Categories

6. A customer orders a special machine that must be individually procured and delivered directly to them rather than stocked. Which item category setup handles this Individual Purchase Order scenario, and how does it differ from standard third-party?

This uses item category TAB (individual purchase order) with schedule line category CB, which creates a PR assigned to the sales order but requires goods receipt into a sales-order-specific stock segment before an SD delivery is created—unlike third-party (TAS/CS) which skips delivery entirely. The material is received against the sales order account assignment, then picked, packed, and delivered from that stock via a normal outbound delivery.
mediumItem Categories

7. How is item category determination configured for a rush order scenario where delivery is expected immediately, and what MM integration points must be verified?

Rush order uses sales document type SO with immediate delivery creation triggered via the order type's delivery type assignment (usually LF) and the item category TAN with the delivery creation flag set to create delivery automatically upon order save. MM integration requires verifying stock availability at goods issue, that the plant is delivery-relevant, and that pricing/costing conditions are complete since billing typically follows delivery immediately without a separate delivery due list run.
mediumItem Categories

8. In a make-to-order sales order, the third-party item category (TAS) and standard item category (TAN) coexist on different lines, and the incompletion log flags missing purchase requisition data only for the TAS lines. Why does this occur, and how would you verify the incompletion procedure is correctly scoped?

Incompletion procedures are assigned per item category (via VOV7 for the item category and OVA2 for the procedure), so TAS items are typically linked to an incompletion procedure that includes fields relevant to third-party processing, such as purchase requisition or vendor data, while TAN items use a different procedure focused on delivery-relevant fields. This is expected behavior; verify by checking the incompletion procedure assignment per item category and confirming which fields are marked mandatory for each, ensuring TAN's procedure does not also need purchasing fields it structurally cannot populate.
mediumItem Categories

9. A customer orders a configurable material that should follow a make-to-order process, but the system is creating the order without generating a corresponding production order. What item category determination checks would you perform to resolve this?

Verify the item category determination in VOV4 for this order type, item usage, and higher-level item category is resolving to a make-to-order relevant category like TAK or TAB rather than a standard TAN category, since incorrect determination combination will default to a non-MTO category with no requirements transfer. Also confirm the material's strategy group and MRP type on the material master align with MTO planning strategy 20 or 25, and that the requirements class linked to the schedule line category has account assignment category set for the sales order-specific stock.
mediumItem Categories

10. A quotation for a configurable make-to-order product needs item category determination to correctly route to a third-party or standard item flow depending on characteristic values selected during variant configuration. How would you design this in item category determination?

Since item category determination (VOV4) keys on document type, item category group, usage, and higher-level item category, and cannot directly evaluate configuration characteristic values, the design typically routes through material determination or a manual item category override triggered by a configuration-dependent BOM or class node that assigns a different item category group. Alternatively, use requirement/order BOM logic combined with a pricing or variant condition to switch material master item category group per configured result, then let standard VOV4 determination pick up the correct item category downstream.
mediumItem Categories

11. For an individual purchase order (IPO) scenario using item category TAB, incompletion logs show missing vendor information at item level even though the material is procured internally otherwise. What is the likely root cause and fix?

TAB items require a vendor to be maintained because they trigger direct procurement via purchase requisition tied to the sales order item (account assignment E). If the vendor isn't derived from source list/info record and isn't manually entered, the incompletion procedure assigned to TAB (via incompletion group) flags it as mandatory since no PR/PO can be created without one. Fix involves either maintaining a source list/info record for automatic derivation or adjusting the incompletion procedure only if vendor entry is genuinely optional for that business scenario.
mediumItem Categories

12. A free-of-charge delivery order is being blocked from delivery creation due to incompletion, even though pricing shows zero value as expected. What incompletion procedure elements are commonly misconfigured in this scenario, and how would you fix it?

Free-of-charge item categories (e.g., TANN) typically exclude pricing and billing relevance, but the incompletion procedure assigned to the header or item may still require fields like pricing conditions, billing document type, or a specific reason code that doesn't apply to FOC. The fix is to assign a dedicated incompletion procedure to the FOC item category that omits billing-relevant fields but still checks logistics fields like delivery-relevant partner and schedule line data, ensuring the item isn't blocked purely for missing pricing/billing data that's intentionally absent.
mediumItem Categories

13. In a quantity contract used to support make-to-order releases, how would you configure item category determination for release orders so that MTO-relevant item categories are used instead of standard TAN, while still maintaining accurate contract quantity tracking?

Item category determination for the release order type must use the item category group from the material (relevant for configurable/MTO materials) combined with the release order's document type and item usage to derive an MTO-capable category (e.g., a TAK-equivalent) rather than defaulting to TAN. The item category must have 'completion rule' and requirement class settings pointing to the correct MTO requirement type, while copy control from contract to release order (VTAA) is configured to update the cumulative quantity/value in the contract without altering the underlying requirement class inherited from the release item category.
mediumItem Categories

14. Product allocation checks are activated for a material, but sales orders for that material are not being checked against the allocation quota, even though the product allocation object and sequence are correctly configured. What item category configuration would you review?

I would check whether the item category assigned to the order item is flagged as relevant for product allocation, since even correctly configured allocation objects and sequences will not trigger a check if the item category excludes it. In S/4HANA this is typically controlled via the item category's relevance settings for product allocation (often tied to characteristics-based or advanced ATP product allocation configuration), and I'd also confirm the material's product allocation object (PAOB) determination procedure is correctly linked at the material or characteristic level for that specific item category and sales area.
mediumItem Categories

15. For cash sales order type BV, which item category is typically determined, and how does item category determination differ when handling free-of-charge items within the same cash sales transaction?

Cash sales order type BV typically determines item category BVN, which is configured as relevant for immediate delivery and pricing, with billing plan set for immediate invoice printing at order save. For free-of-charge items in the same order, item category determination uses the item category group and a pricing indicator combination to derive a category like TANN (free goods), which is statistical, has no pricing relevance, and does not generate revenue recognition, while still copying quantity into the same delivery.
mediumItem Categories

16. A standard sales order is created for a material with MRP strategy 20 (make-to-order), but the system determines item category TAN instead of the expected TAK. What integration points would you check to correct this?

Check the item category group on the material master (should be 0002 or similar MTO-relevant group, not NORM), since item category determination uses document type plus item category group plus usage plus higher-level item category. Verify item category determination table (VOV4) has an entry mapping the correct group to TAK, and confirm the requirements type derived from the strategy group correctly flows via MRP group/strategy to trigger the special stock indicator (E) for individual customer stock. Also check that the plant and MRP view settings for strategy 20 are correctly maintained in the material master.
hardItem Categories

17. In a make-to-order scenario, why might a quotation not trigger an ATP check or requirements transfer to MRP, and how would you configure it to do so if required?

Quotations typically use item categories with no requirements transfer (e.g., AGN) since they are pre-sales, non-binding documents, so no ATP check or planning relevance is triggered by default. If a business needs preliminary capacity reservation, the schedule line category can be changed to one with requirement transfer and availability check active (via VOV6), and the item category assigned via VOV4 determination, but this is unusual since it consumes planning resources for non-firm demand.
hardItem Categories

18. You are designing a global architecture where product substitution (material determination) can swap an ordered material for an alternative during order entry, but the substitute material has a different procurement type (in-house produced vs. externally procured) than the original. How would you architect item category and schedule line determination so the substitution correctly redirects to third-party or standard MTO processing without manual intervention?

Design material determination (listing/exclusion or condition-based substitution) to trigger a re-determination of item category using the substitute material's own material type/MRP data, not the originally entered material. Ensure item category determination access sequence keys off the substituted material, and schedule line category determination reflects the substitute's procurement type so third-party (TAS) or MTO (TAK) routing occurs automatically. Test that pricing and ATP re-run against the substitute material after substitution executes.
hardItem Categories

19. A make-to-order item unexpectedly determines a standard TAN item category instead of the expected TAK/make-to-order relevant category, causing the schedule line to skip production order creation. How would you troubleshoot the root cause?

I would first check item category determination (VOV4) for the combination of sales document type, item category group from material master (should be 0002 for MTO, not NORM), usage, and higher-level item category, since the item category group is the most common culprit if material master MRP/sales views weren't set up as make-to-order relevant. I would also verify the item category assignment supports the correct schedule line category with requirements type linked to strategy group 20/25 in MRP4, and confirm the requirement type/class is properly derived to trigger production order or planned order creation instead of standard delivery-only processing.
hardItem Categories

20. You are designing item category determination for a multi-level sales BOM sold across several document types (standard order, rush order, and consignment fill-up). What architectural principles should guide the higher-level and sub-item category assignments?

Design determination so the higher-level item category (e.g., TAQ for BOM header not relevant for delivery/pricing) is consistent across document types unless business rules genuinely differ, while sub-items derive their category based on the higher-level item category field in VOV4, ensuring pricing and delivery relevance are set only at the intended level (usually sub-items for delivery, header for pricing if a fixed BOM). Rush order and consignment variants should reuse the same item category group and BOM usage to avoid duplicating master data, differing only in document-type-specific schedule line/billing behavior, keeping determination centralized and maintainable.

Related lesson

Architecting a Scalable Item Category Strategy for Global Templates

Related topics

Next practice step