Ameco ERP/BPM
AM
Company Fit-Gap Case StudiesIntermediate

SAP SD Organization Structure

Fit-Gap Document Source

Amecath_SD_Fit_Gap_V2.0.pdf

Reference Page: 5

1. Business-User Summary

In SAP, the organizational structure is the framework that maps our physical and logical business structure into the system. It dictates how sales are tracked, how pricing is determined, who is authorized to do what, and how revenue is ultimately reported.

2. Key Organizational Elements

Company Code

The highest financial reporting level (e.g., Ameco Main). It represents the independent legal entity where a complete set of financial statements (balance sheet and income statement) is created.

  • Why it matters: All revenue and accounting entries from sales ultimately post to the Company Code.

Sales Organization

The unit legally responsible for selling products, negotiating terms, and customer liability. We have distinct Sales Orgs for Domestic vs. Export.

  • Why it matters: Pricing, master data, and sales reports are grouped by Sales Organization.

Distribution Channel

Defines how the goods reach the customer (e.g., Wholesale, Retail, Direct Sales, Online).

  • Why it matters: We might offer different pricing or products based on the channel (e.g., wholesale gets a bulk discount).

Division

Represents a product line or group of materials (e.g., Finished Goods, Spare Parts, Heavy Machinery).

  • Why it matters: Allows us to track profitability by product line and restrict sales reps to only selling divisions they manage.

Sales Area

The specific combination of Sales Organization + Distribution Channel + Division.

  • Why it matters: Customer master data and sales documents are always created within a specific Sales Area. It determines what products a customer can buy and at what price.

Sales Office & Sales Group

Geographical or organizational subsets of a Sales Area. A Sales Office might be "North Region", and a Sales Group might be "Enterprise Sales Team".

  • Why it matters: Critical for granular sales reporting, tracking team KPIs, and process ownership.

3. Visual Hierarchy

Rendering diagram…

4. Why This Structure Matters

This structure is not just technical; it drives the business:

  • Customer Creation: Customers must be extended to specific Sales Areas to buy from them.
  • Sales Order Processing: The system uses this structure to validate if a transaction is allowed.
  • Pricing: We set different price lists for different Distribution Channels.
  • Reporting: It allows executives to slice revenue by region, product line, or sales team.
  • Authorization: Restricts users from viewing or changing data outside their assigned Sales Area.

5. Fit-Gap / Customization Notes

  • GAP: The standard SAP structure groups divisions universally, but Ameco requires specific tax reporting split by division.
  • Resolution: Custom logic was added at the billing document level to ensure division-specific GL account determination for accurate tax compliance.

Source Document Reference

Document Source

Amecath_SD_Fit_Gap_V2.0.pdf

Reference Page: 5

Knowledge Check

Question: Which of the following makes up a "Sales Area" in SAP? A) Company Code, Sales Organization, and Sales Office. B) Sales Organization, Distribution Channel, and Division. C) Sales Organization, Sales Group, and Sales Office. D) Company Code, Distribution Channel, and Division.

(Answer: B)