ERPClimb logoERPClimb

SAP SD / O2C Enterprise Structure Interview Questions

Interviewers use enterprise structure to test depth rather than coverage: the follow-up question is almost always "why does the system behave that way?", and that is where prepared answers usually run out.

Covers the SAP SD enterprise structure - the organizational backbone (sales organization, distribution channel, division, sales office, sales group, plant, storage location, shipping point) that determines pricing, availability, document flow and FI/MM integration for Order-to-Cash. Explains design principles, configuration nodes, assignments, and how the structure drives downstream master data and transactional behavior across ECC and S/4HANA.

This page carries 29 reviewed SAP SD / O2C enterprise structure interview questions, each with a complete written answer and no sign-in required. The set breaks down into 4 foundational, 14 mid-level and 11 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

If you can handle every question here without hesitating, enterprise structure is unlikely to be what costs you an SAP SD / O2C interview — and the same reasoning pattern transfers to the neighbouring topics linked at the bottom of this page.

29 Enterprise Structure questions with answers

easyEnterprise Structure

1. What is a sales organization in SAP SD, and how does it relate to the company code in the enterprise structure?

A sales organization is the highest organizational unit in SD responsible for selling and distributing goods, negotiating conditions, and defining liability for sales. It is assigned to exactly one company code, which links sales activity to a specific legal entity for financial posting. One company code can have multiple sales organizations, but a sales organization cannot be split across company codes, ensuring clean financial reporting.
easyEnterprise Structure

2. What is the purpose of the Sales Office organizational unit in SAP SD, and how does it relate to Sales Area and Partner Determination?

Sales Office is an organizational unit representing a physical or regional sales location (e.g., branch office) assigned to one or more Sales Areas. It's used for reporting, statistics, and can be set as a partner function (SA - Sales Office) in partner determination procedures on sales documents, enabling office-level responsibility tracking and output/text routing independent of the responsible Sales Group.
easyEnterprise Structure

3. What is the purpose of a Sales Office in the SD enterprise structure, and how is it related to Sales Organization and Distribution Channel?

A Sales Office is an organizational unit representing a physical or geographical sales location, such as a branch office, assigned to one or more Sales Area combinations (Sales Org + Distribution Channel + Division). It is optional but useful for regional reporting, territory management, and assigning sales groups/employees. It appears on sales documents as a partner-relevant field and can drive output and reporting segmentation without affecting pricing or account determination directly.
easyEnterprise Structure

4. What is the role of the Sales Organization in the SAP SD enterprise structure, and how does it relate to partner determination in sales documents?

Sales Organization is the top-level SD enterprise structure element representing a legally or organizationally distinct selling unit, responsible for revenue, sales conditions, and customer relationships. It is assigned to a Company Code and combined with Distribution Channel and Division to form a Sales Area. Partner determination procedures are assigned at document type level and often influenced by sales area, so sales organization indirectly drives which partner functions (sold-to, ship-to, bill-to, payer) are mandatory and how they default from customer master.
mediumEnterprise Structure

5. Which configuration and master data steps ensure a new material is sellable in a specific sales organization and distribution channel, and what commonly gets missed?

The material must have a sales org/distribution channel view (MVKE-relevant screens) maintained via MM01/MM02, including item category group, tax classification, delivering plant, and loading group. The plant must be assigned to the sales organization via the enterprise structure link, and a valid plant-to-sales-org-distribution-channel assignment must exist. Commonly missed: tax classification per country/departure country, missing plant assignment causing pricing/availability errors, and absent sales text or missing material status blocking order entry.
mediumEnterprise Structure

6. Your organization configures common distribution channels so that channel 10 and channel 20 share the same customer and material master records, but MM requires separate stock valuation and delivery lead-time behavior per channel via differing plant assignments. How would you design the enterprise structure so common distribution channel configuration is preserved while MM-specific data that legitimately differs by channel is not lost?

Common distribution channel settings should only be used to share master data screens (customer/material) that are genuinely identical, not to force valuation or lead-time differences into a single record. Keep plant assignment, storage location, and MRP area distinct so MM valuation and delivery scheduling remain channel-appropriate at the plant level, while the sales order's delivering plant determination (via customer-material info records or shipping conditions) drives the correct MM behavior. Document which fields are truly shared versus derived at order time to avoid data conflicts.
mediumEnterprise Structure

7. A regional sales manager wants Fiori apps to reflect sales group-level performance dashboards, but the sales group is not correctly appearing in some transactional data. How does sales group assignment to sales area affect Fiori reporting apps?

Sales group is assigned indirectly through the sales employee or organizational unit linked to a sales office within a sales area; it is not a mandatory field on all sales documents, so if not defaulted via customer master or manually entered, it remains blank and Fiori analytical apps relying on VBAK-VKGRP will show incomplete data. You need to verify the sales group defaulting logic in customer master sales area data and ensure CDS views feeding Fiori apps include fallback logic or mandatory field checks at document entry.
mediumEnterprise Structure

8. How do you configure and assign a Sales Group so that it correctly appears as a selectable field in the sales area assignment for a customer master, and what Fiori app supports this maintenance in S/4HANA?

Sales Group is defined under Enterprise Structure and assigned to one or more Sales Offices, which in turn belong to a Sales Area. Once assigned, it becomes available for selection in the customer's sales area segment (Sales tab). In S/4HANA, this can be maintained via the classic IMG paths or the 'Manage Customer Master Data' / 'Maintain Business Partner' Fiori app, which reflects the same underlying assignment tables.
mediumEnterprise Structure

9. Your company wants to sell the same materials through two distribution channels (Direct Sales and Distributor Sales) using shared Business Partner records but different pricing and account assignment. What enterprise structure and master data design would you recommend?

Design two distinct sales areas (same sales org/division, different distribution channel) so pricing procedures, statistics groups, and partner function determination can differentiate by channel while reusing the same Business Partner as the base customer record. Extend the customer to both sales areas (KNVV records) rather than creating duplicate BPs, since Business Partner is the single source of truth in S/4HANA and only the sales-area-dependent segment needs channel-specific data like pricing group, credit limit checks, or output parameters. Use condition records with distribution channel as a key field for channel-specific pricing.
mediumEnterprise Structure

10. A distribution channel used for direct e-commerce sales needs to share material master data with the traditional wholesale channel, but pricing and output must differ. How do you design this without duplicating material masters, and what MM integration points must be checked?

Retain a single material master and use sales organization/distribution channel-specific sales views (MVKE) to differentiate pricing-relevant fields like pricing reference material, statistics group, or sales status per channel, while output determination is driven by condition records at the distribution channel level rather than material-level changes. Confirm MM integration points: plant assignment to distribution channel via sales organization, availability check group consistency, and delivering plant determination rules so both channels resolve to the correct plant.
mediumEnterprise Structure

11. How do you configure common distribution channels and common divisions, and what are the practical constraints of this approach?

Common distribution channel/division configuration (OVMB, OVMC) lets you designate a reference channel or division whose customer and material master data other channels/divisions reuse, avoiding redundant KNVV/MVKE extensions. It works well when pricing, partner functions and output rules are identical across channels. Constraints: pricing condition records and credit settings are still sales-area specific, so channels with different pricing strategies cannot truly share, and reporting by channel loses granularity.
mediumEnterprise Structure

12. How does the Sales Group organizational unit integrate with Business Partner-based customer master data in an S/4HANA environment using account groups for customer creation?

Sales Group is maintained as sales-area-specific data on the Business Partner's customer sales view (BP transaction, role FLCU00 sales area tab), stored in KNVV, and is independent of the account group used for BP creation. Account group controls number ranges, field status, and partner function screen behavior during BP creation, but does not restrict which sales groups are assignable; sales group assignment is typically governed by authorization or organizational data validation rules configured separately, sometimes via BAdI or partner function default logic.
mediumEnterprise Structure

13. A company wants to simplify master data maintenance across four distribution channels that all share the same pricing, customers and materials. How does configuring common distribution channels and divisions help, and what are the trade-offs?

Common distribution channels/divisions (via table entries in customizing, sometimes referred to as the 'reference' channel/division setting) let the system reuse customer and material master records across multiple distribution channels by pointing to one master data-holding channel, avoiding duplicate maintenance of KNVV or MVKE records. Trade-off: it restricts flexibility for channel-specific pricing, credit limits, or partner functions, since underlying master records are shared; if channels later diverge functionally, you may need to unlink them, which requires careful data migration and re-extension of records.
mediumEnterprise Structure

14. A business user in a Fiori app attempts to create a new Business Partner customer role and assign a sales area, but the sales area value help returns no results even though the distribution channel and division individually exist. What is the most likely governance root cause and how do you resolve it?

The most likely cause is that the specific combination of sales organization, distribution channel, and division has not been maintained as a valid sales area combination in configuration (via IMG 'Assign sales area' / OVXG), even though each element exists individually. Resolve by maintaining the valid combination in the backend IMG, then verify the Fiori app's value help cache or OData service is refreshed. Also confirm the BP role for sales data (e.g., FLCU00 or FLCU01) is properly assigned to the business partner before sales area data entry is possible.
mediumEnterprise Structure

15. How is Sales Group configured and used within the SD enterprise structure, and what is its typical integration point with MM for reporting?

Sales Group is a subdivision within a Sales Office representing a team of sales staff, configured via customizing and assigned to Sales Offices. It's used to segment responsibility for order processing and reporting, often linked to employee master records via personnel assignment. From an MM integration perspective, Sales Group appears in purchasing-triggered sales scenarios like third-party or intercompany processing where cross-functional reporting needs consistent org attribution across SD and MM documents.
mediumEnterprise Structure

16. A global company ships from three plants but wants deliveries for a single sales order to always originate from the plant closest to the customer, while respecting shipping point rules per plant. How would you configure shipping point determination to support this?

Shipping point determination is based on shipping condition (customer), loading group (material), and plant. Since plant is already determined at item level (via customer-material info or MRP), I'd ensure each plant has correctly assigned shipping points in the determination table, and use plant determination logic (e.g., customer-material info records or sourcing rules) to select the closest plant first. Shipping point then follows automatically per plant/loading group/shipping condition combination without needing custom routines unless exceptions exist.
mediumEnterprise Structure

17. A business user reports via Fiori app that a material's sales view data appears correct in the backend but the Fiori 'Manage Material' app shows the material as not sales-relevant for a specific sales area. What should you check to resolve this?

Check whether the material has maintained sales views (MVKE) for the specific Sales Organization and Distribution Channel combination the user is querying, since Fiori apps filter based on exact sales area assignment, not just plant-level extension. Also verify OData service authorization and business partner/material replication filters in the Fiori catalog, and confirm the material's cross-distribution-chain status (X-distribution chain status) isn't blocking visibility for that specific combination.
mediumEnterprise Structure

18. In S/4HANA, how do you configure and assign a Distribution Channel so that it becomes usable within a valid Sales Area, and what governs its visibility in Fiori apps for master data creation?

You define the distribution channel code centrally (VOR2/OVXI equivalent), then assign it to a Sales Organization and combine it with a Division to create a valid combination in sales area maintenance (OVXG or via IMG 'Assign sales area'). Only sales areas explicitly maintained as valid combinations appear in customer/material master creation, including Fiori apps like 'Manage Customer Master' or 'Create Sales View', because the app's value help filters on the TVTA-based valid combination table.
hardEnterprise Structure

19. You are designing the enterprise structure for a company with one plant supplying multiple sales organizations across different countries. What are the key architectural considerations for plant and shipping point assignment, including FI implications?

A plant must be assigned to a company code, and that company code drives the valuation and FI posting for goods movements originating from that plant regardless of which sales organization sells from it. Shipping points are assigned to plants, and multiple shipping points can serve one plant based on shipping conditions. Cross-company sales scenarios arise when the plant's company code differs from the sales organization's company code, requiring intercompany billing configuration and careful account determination to avoid incorrect revenue recognition.
hardEnterprise Structure

20. For a global rollout, how would you architect the relationship between Plants and Shipping Points across multiple sales organizations to support both centralized MDG governance and correct partner determination for shipping-related partner functions?

Design plants as the physical/logistics master data anchor, assigned to company codes and shared across sales organizations where legally permissible; shipping points are assigned to plants (one plant can have multiple shipping points) and derived in the order via shipping point determination rules based on plant, shipping condition, and loading group. For MDG governance, plant and shipping point master data should be centrally maintained with change request workflows, while partner determination for functions like SH (ship-to) or forwarding agent should reference plant-derived shipping data rather than hardcoding per sales organization, ensuring consistency when new sales orgs are onboarded.
hardEnterprise Structure

21. A merger requires consolidating two legacy divisions into a single division while preserving historical reporting granularity and partner determination logic. What architectural approach would you propose and what are the trade-offs?

Introduce a new consolidated division but retain the legacy divisions as inactive/reference values by using a custom reporting attribute (e.g., a classification characteristic or BI/BW hierarchy) rather than reusing division as the sole reporting dimension, since collapsing division changes partner determination procedures and pricing determination tied to division. Trade-off: consolidating divisions simplifies master data and order entry but requires re-mapping historical documents for reporting via a crosswalk table, and any partner determination procedure keyed by division must be redesigned to avoid breaking existing partner function assignment.
hardEnterprise Structure

22. Multiple plants ship the same material to a customer, but shipping point determination is inconsistently selecting a plant/shipping point combination that causes pricing to pull the wrong condition records, leading to systemic underpricing across regions. As an architect, how would you diagnose and remediate this?

I would trace shipping point determination logic (shipping condition from customer/document + loading group from material + plant) to confirm which combination table entries exist, since an incorrect or missing entry can default to an unintended shipping point tied to a different sales area or pricing condition table access. I'd check if pricing analysis (order item pricing conditions) shows access sequence hitting wrong condition records due to sales org/plant mismatch, then correct shipping point determination table entries and potentially the plant determination logic in the order, followed by mass reprocessing of open orders and regression testing across affected regions.
hardEnterprise Structure

23. You are designing the enterprise structure for a company acquiring multiple regional distributors, each with existing customer-material info records tied to legacy sales areas. How should you architect the Customer-Material Info Record strategy to avoid pricing and data conflicts post-integration?

Design a harmonized sales area structure first, mapping legacy sales organizations to the target model, then migrate CMIR (KNMT) records with careful attention to duplicate customer-material combinations across merged sales areas, since CMIR data is sales-area specific and can override standard pricing/delivery defaults. Establish a data governance rule for conflict resolution (e.g., most recent or highest-priority source wins) and validate that CMIR-driven fields like customer material number, delivery priority, and minimum delivery quantity don't create inconsistent order processing across the newly consolidated sales areas.
hardEnterprise Structure

24. When designing the Division structure for a multinational client with diverse product lines, what enterprise structure and FI integration considerations must an architect evaluate before finalizing division count?

Architect must weigh reporting granularity against master data maintenance overhead: divisions drive pricing procedure determination, credit management groupings, and can be used for profit center or segment reporting in FI via account assignment. Excessive divisions increase material master and customer-material info record maintenance burden. FI integration considerations include whether divisions map to business segments for segment reporting in Universal Journal (ACDOCA) and whether separate G/L account determination is needed per division-driven account assignment group.
hardEnterprise Structure

25. In a multi-plant, multi-shipping-point sales organization design, how should the assignment between Plant, Shipping Point, and Sales Organization be structured to support both delivery efficiency and credit management integration?

Plants should be assigned to Sales Organizations via Sales Area assignment, and each Plant linked to one or more Shipping Points based on loading conditions and shipping calendar. Shipping Point determination uses delivering plant, shipping condition, and loading group. For credit management, the sales area on the order (derived from customer-material combination and plant) determines the credit control area indirectly through company code assignment, so plant-to-company-code mapping must align with the credit control area structure to avoid credit exposure fragmentation across plants.
hardEnterprise Structure

26. You are designing a global sales organization structure where each sales org must support region-specific text determination requirements (e.g., legal disclosures per country) while sharing material master sales views across sales orgs to minimize maintenance. Credit management must remain accurate per sales org despite this sharing. How would you architect this to avoid conflicts between text determination granularity, material sales data replication, and credit control area accuracy?

Keep material sales views (MVKE) maintained per sales org/distribution channel so credit-relevant fields like credit group and delivering plant remain accurate per org, even if base material data is templated centrally to reduce duplication effort. Configure text determination procedures at the sales document type level, using access sequences that pull region-specific text objects (e.g., customer or sales org text) rather than hardcoding into shared material texts, so legal disclosures vary without touching shared material master content. Validate that credit control area assignment follows company code/sales org mapping independently of any shared master data template.
hardEnterprise Structure

27. In a global template rollout, how should the relationship between Plant and Shipping Point be designed to support multiple sales organizations shipping from a shared distribution center, and what FI implications arise from the Plant-to-Company Code assignment?

Design Shipping Points as sub-units under a Plant, with one Plant able to have multiple Shipping Points (e.g., by shift or carrier). Multiple Sales Organizations across Company Codes can deliver from the same Plant if the Plant is assigned to a single Company Code but the Sales Organization-Distribution Channel-Plant combination allows cross-company sales, triggering intercompany billing. The Plant's Company Code assignment drives which FI ledger and valuation area apply, so misassignment causes incorrect COGS posting and inventory valuation.
hardEnterprise Structure

28. A global rollout requires adding a new distribution channel to an existing sales organization that already has years of transactional history. What is the process and what risks must be assessed before extending the sales area?

Extend the sales organization/distribution channel/division combination via enterprise structure assignment (OVXA/OVXG), then extend all relevant material master and customer master records to the new sales area using mass extension tools (MASS or MM17/XD99). Assess pricing procedure determination, output determination, and copy control impacts since new combinations may trigger different condition records. Validate that existing sales document types, item categories, and credit control area assignments remain consistent, and test in a sandbox before mass extension to avoid broken master data links.
hardEnterprise Structure

29. After a company acquisition, sales orders created under the newly merged sales organization are failing to post billing documents to FI with an account determination error. As the architect, how do you diagnose whether this is an enterprise structure design issue versus a master data issue?

Start by checking if the new sales organization is correctly assigned to a company code and whether that company code's chart of accounts and account determination procedure include the condition types used in the merged pricing procedure. If assignment is correct, check customer/material master account assignment groups feeding the account determination access sequence (VKOA). A structural gap (missing sales org-company code assignment or missing condition records in the new combination) points to enterprise structure design; missing account assignment group values on individual customers/materials point to master data.

Related lesson

Advanced Enterprise Structure Design: Common Assignments, Multi-Entity Landscapes, and Restructuring

Related topics

Advanced SD Scenarios, Integration and Production SupportS/4HANA SD Transformation, Migration, Public Cloud and ArchitecturePricingBillingCustomer and Business PartnerOutput ManagementSchedule Line CategoriesItem CategoriesCopy ControlCredit ManagementAvailability CheckSales Documents

Next practice step

Practice with Interview AITake a mock test