sales group assignment table

• ABAP Snippets
• Top SAP Courses
• Top SAP Books

SAP and ABAP Free Tutorials

Sap Sales Organization Overview (Tables, Definition, Tcodes and SAP SD Sales Org)

This post will give you a deep technical overview of Sap Sales Organization. First we will start with some definition, then SAP Sales Organization Tables and Tcodes.

Finally, you will find some interesting tips for Sales Organization in SAP.

Table of Contents

SAP Sales Organization Definition

What is a sales organization.

Let’s start for the beginning and try to answer the following question What is a sales organization?

“Sales organization is a structured framework, specifying the formal authority and responsibility among persons working in the organization.

It consists of a group of individuals working to achieve selling objectives to increase sales, maximizing profits, expanding market share etc.” ( source )

Sales Organization in SAP

• Legally, a sales organization is included in exactly one company code.
• You assign sales offices and your own employees to a sales organization.
• All items in a sales & distribution document, that is, all items of an order, delivery or a billing document belong to a sales organization.

Definition of SAP Sales Group

The definition of sales groups is optional. You can use the SD system without creating sales groups. ⇾ You can assign a sales group to one or more sales offices. ( source )

SAP Sales Office

The definition of sales offices is optional. You can use the SD System without creating sales offices. ⇾ You assign a sales office to one or more sales areas.

If you want to go deeper of how to customize Sales Organization in SAP, check this link .

SAP Sales Organization Tcodes and Tables

Sap sales organization tcodes.

Some of the most important Tcodes for SAP Sales Organization are:

• OVX3 Company code ⇾ sales organization SD
• OVXA Division ⇾ sales organization SD
• OVB1 Sales organizations – Rebate SD
• OVX3N Company code ⇾ sales organization SD
• OVXAN Division ⇾ sales organization SD

SAP Sales Organization Tables

Here the list of main SAP Sales Organization Tables

• T001W Plant / sales organization
• TVKO Sales organization / company code
• TVKOV Distribution channel / sales organization
• TVKOS Division to sales organization
• TVKWZ Plants to sales organization

Useful Tips for SAP Sales Organization

How to find the mapping between r/3 sales org and crm org unit.

If you want to get the mapping between R/3 Sales Org Mapping with CRM Org Unit, check the following Tables:

Mapping between R/3 Sales Org and CRM Org Unit

If you prefer using SAP function modules, you may check the following SAP FM to find the mapping between ECC and CRM Sales Organization, Sales Group and Sales Office

SAP Table for sales org and plant assignment

The SAP Standard Tables TVKWZ ( or V_TVKWZ_ASSIGN ) stores the information for SAP Sales Org and Plant Assignment.

Actually, Plant is assign to Company code and not sales organization, but sales organization and distribution channel is assign to plant and the same you can get in

SPRO > Enterprise Structure > Assignment > Sales and Distribution > Assign sales org. Distribution channel plant .

Source: Table for sales org and plant assignment

Related Posts

The Most Important SAP Payment Terms Tables (ZTERM, Text…)

October 21, 2018 March 24, 2021

SAP Batch Management: User-exits and BAdIs

June 17, 2017 January 21, 2022

SAP Batch Management Tcodes, Tables and Customizing (SAP Batch Management)

June 16, 2017 January 21, 2022

Blog about all things SAP

ERProof » SAP SD » SAP SD Training » SAP Sales Group

SAP Sales Group

Prerequisites

Before you proceed with this tutorial, it is advisable to please go through the tutorial about SAP SD Organizational Structure available in SAP SD Training Course  until and unless you are aware of the organizational structure functionality of SAP SD .

What is SAP Sales Group?

Employees belonging to a certain SAP sales office can be divided into sales groups. These sales groups are assigned to their respective sales offices . SAP sales group is a subset of an SAP sales office .

How to Create SAP Sales Group?

I am sure you have gone through the tutorial SAP SD Organizational Structure available in the tutorials section. This tutorial will help you in learning the steps about configuration done in SAP customizing and how the SAP Sales & Distribution Organizational structure is configured during Realization Phase finalized in the Business Blueprint Phase.

There are two steps in Organizational Structure configuration:

• Definition : this is the first step in organizational structure configuration where you create and define the organizational structure with the ‘coding’ finalized in the Business Blueprint Phase.
• Assignment : this is the second step in the organizational structure configuration setup where you assign the configurable object created in the definition step to another configurational object in the same or in another module(s). E.g., assigning a Distribution Channel to a Sales Organization and / or assigning a Sales Organization to a Company Code.

Define SAP Sales Group

To define a new SAP sales group in the customizing of the SAP system it is necessary to either type SPRO in the transaction bar:

or the same can also be accessed through SAP Easy Access menu tree by the following path: Tools > Customization > IMG > SPRO – Execute Project .

In the SPRO transaction, you need to navigate to the following menu path:  SPRO > Enterprise Structure > Definition > Sales and Distribution > Maintain sales group .

Enter sales groups with the codes and description that you require.

Assigning SAP Sales Group

Now, the second step is to assign the sales group(s) created / defined at the first step to SAP sales offices as finalized in the Business Blueprint document. Navigate to the following menu path: SPRO > Enterprise Structure > Assignment > Sales and Distribution > Assign sales group to sales office .

Enter codes of sales offices and sales groups into the available columns.

Did you like this tutorial? Have any questions or comments? We would love to hear your feedback in the comments section below. It’d be a big help for us, and hopefully it’s something we can address for you in improvement of our free SAP SD tutorials.

Navigation Links

Go to next lesson: SAP Shipping Point

Go to previous lesson: SAP Sales Office

Go to overview of the course: Free SAP SD Training

Leave a Reply Cancel reply

Do you have a question and want it to be answered ASAP? Post it on our FORUM here --> SAP FORUM !

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

• TutorialKart
• SAP Tutorials
• Salesforce Admin
• Salesforce Developer
• Visualforce
• Informatica
• Kafka Tutorial
• Spark Tutorial
• Tomcat Tutorial
• Python Tkinter

Programming

• Bash Script
• Julia Tutorial
• CouchDB Tutorial
• MongoDB Tutorial
• PostgreSQL Tutorial
• Android Compose
• Flutter Tutorial
• Kotlin Android

Web & Server

• Selenium Java
• SAP SD Tutorials
• SAP SD Enterprise Structure
• SAP SD - Define Sales Organization
• SAP SD - Define Distribution Channel
• SSAP SD - AP SD - Define Division
• SAP SD - Maintain Sales office
• SAP SD - Define Sales Group
• SAP SD - Define Sales Area
• SAP SD - Define Company Code
• SAP SD - Define Shipping Point
• ADVERTISEMENT
• SAP SD - Assignment of Organizational Units
• SAP SD - Assigning a Sales Organization to a Company Code
• Assigning a Distribution Channel to a Company Code
• SAP SD - Assigning a Division to a Sales Organization
• SAP SD - Assigning a Sales office to a Sales Area
• SAP SD - Assigning a Sales Group to a Sales Office
• SAP SD - Assigning a Sales Area to Credit Control Area
• SAP SD - Define sales area
• SAP SD Customer Master Data
• SAP SD - Create customer account groups
• SAP SD - Maintain number ranges for customer account groups
• SAP SD - Assign number ranges to customer account groups
• SAP SD - Define tolerance group for Customers
• SAP SD - Create sundry debtors accounts
• SAP SD - Partner determination procedures
• SAP SD - Create Customer Master Record
• SAP SD Pricing & Tax Determination
• SAP SD - What is pricing
• SAP SD - Maintain condition tables
• SAP SD - Maintain access sequences
• SAP SD - Maintain condition types
• SAP SD - Maintain pricing procedure
• SAP SD - Define pricing procedure determination
• SAP SD Sales Documents
• SAP SD - Define order reasons
• SAP SD - Define purchase order types
• SAP SD - Define item categories
• SAP SD - Assign item categories
• SAP SD - Define item category groups
• SAP SD - Define schedule line categories
• SAP SD - Assign schedule line categories
• SAP SD - Define sales document type
• SAP SD - Credit and Risk Management
• SAP SD - Maintain credit control area
• SAP SD - Assign credit control area to company code
• SAP SD - Define risk categories
• SAP SD - Define credit groups
• SAP SD - Assign sales documents & delivery documents
• SAP SD - Credit limit for customers
• SAP SD TCodes
• ❯ SAP SD Tutorials
• ❯ SAP SD - Define Sales Group

How to Define Sales Group in SAP

How to create sales group in sap.

In this SAP SD tutorials, you will lean how to define sales group in SAP SD step by step. In previous training we have learned how to set up sales area in SAP .

What is Sales Group?

Group of sales employees or organizational unit (branch wise) can be defines as a sales group. A sales office can have number of sales group, so sales group should be assigned to sales office.

Configuration process

You can define sales office through the following navigation method.

• SPRO -> IMG -> Enterprise Structure –> Definition –> Sales and Distribution –> Maintain Sales Group.

Step 1) Enter T-code “SPRO” in the SAP command field and enter.

Step 2) On execute project screen, click on “ SAP Reference IMG “

Step 3) On display IMG screen, navigate the menu path and click on sales group.

Step 4) On change view sales groups overview screen, click on “New entries” button to create new sales group in SAP as per company requirements.

Step 5) On new entries sales group screen, update the following details.

• Sales Group: – Enter the key that identifies the sales group in SAP. You are allowed to enter maximum three alphanumeric digits.
• Description: – Update the descriptive text of sales group.

Step 6) After maintaining all the required details of sales group, click on save button choose customize request and save the configured sales group details.

Successfully we have defined sales group in SAP .

Popular Courses by TutorialKart

App developement, web development, online tools.

Sales organization assignment to company code Table in SAP

• PAYAC07 Table for Company Code/Company Code Groups Assignment (FM) Table Type : TRANSP Package : FMFI Module : PSM-FM-PO
• UDM_COMPCODE_MAP Table for Assignment of FI Company Code to Collection Company Code Table Type : TRANSP Package : UDM_COLL_CUSTOMIZING Module : FIN-FSCM-COL
• B402 Table for Sales Organization, Service Company Researcher Table Type : TRANSP Package : JSD Module : IS-M
• B404 Table for Sales Organization/Service Company/Error Reason Table Type : TRANSP Package : JSD Module : IS-M
• ESERV_C_BUKRS Table for Allocation of Auxilliary Company Code to Company Code Table Type : TRANSP Package : EE_DEREG_INV Module : IS-U-IDE
• OIUH_CM_OR1_CC Table for Mapping of Organization level to Company Code Table Type : TRANSP Package : OIU_H Module : IS-OIL-PRA-REV
• B002 Table for Sales Organization/Sales Activity Type Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• B405 Table for Sales Organization/Distribution Channel/Division/Sales Off. Table Type : TRANSP Package : JSD Module : IS-M
• SMOORGCO Table for attribute country for sales organization in CRM Mobile Sales Table Type : TRANSP Package : SMO3 Module : CRM-MSA
• GRPCORGUGRLCR Table for Assign Organization unit value to Organization Unit Group Table Type : TRANSP Package : GRPC_RULE_ENGINE Module : GRC-SPC
• GRPC_OLSP_SNP Table for Assign Organization unit value to Organization Unit Group Table Type : TRANSP Package : GRPC_RULE_ENGINE Module : GRC-SPC
• T001_UMKRS Table for Time-Dep. Assignment of Company Code to Sales/Purch. Tax Grp Table Type : TRANSP Package : FBAS Module : CRM
• /BEV4/PLDVKORGZ Table for Sales Organization Assignment Pendulum List Table Type : TRANSP Package : /BEV4/PL Module : SD-BIL-RB-PL
• TFK001GB Table for Company Codes for Company Code Groups Table Type : TRANSP Package : FKKB Module : FI-CA
• T5DC3 Table for Pension Organization for Company Pension Scheme Table Type : TRANSP Package : P01A Module : PA-PF-DE
• J_3GGBBKVB Table for Sales Area per Company Code/Business Area/Plant Table Type : TRANSP Package : J3GD Module : IS-EC-CEM
• T5DP4 Table for Assignment PAISY Company - Superordinate Company Table Type : TRANSP Package : P01Y Module : PY-DE
• A079 Table for Sales Organization/Distribution Channel/Material Group Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• A110 Table for Sales Organization/Destination Country Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• B001 Table for Sales Organization/Customer Number Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• B005 Table for Sales Organization/Order Type Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• B011 Table for Sales Organization/Billing Type Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• B012 Table for Sales Organization/Delivery Type Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• B018 Table for Sales Organization/Receiving Country Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• B019 Table for Messages: Sales Organization/Distribution Channel Table Type : TRANSP Package : WAUF Module : CRM
• B160 Table for Sales Organization/Condition Granter Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• B171 Table for Sales Organization/Distribution Channel/Division/Payer Table Type : TRANSP Package : VKON Module : AP-PRC-PR
• B403 Table for Sales Organization, Researcher Table Type : TRANSP Package : JSD Module : IS-M
• B409 Table for Sales Organization/Error Reason Table Type : TRANSP Package : JSD Module : IS-M
• CRMC_FS_SOG_AP Table for Assign Accounting Principle to Sales Organization Table Type : TRANSP Package : CRM_FS_1O_EXT_CLASSIFICATION Module : CRM-LAM-BTX
• CVLC18V Table for VELO : Vehicle Search Area - Sales Organization Table Type : TRANSP Package : ISAUTO_VLC Module : IS-A-VMS
• J_3GTVKO Table for Customer Internal Settlement per Sales Organization in CEM Table Type : TRANSP Package : J3GD Module : IS-EC-CEM
• KOTE201 Table for Sales Organization/Partner Object Table Type : TRANSP Package : JAS Module : IS-M
• S004 Table for SIS: Product/Sales Organization/Distribution Channel Table Type : TRANSP Package : MCS Module : CRM
• S004BIW1 Table for SIS: Product/Sales Organization/Distribution Channel Table Type : TRANSP Package : MCS Module : CRM
• S004BIW2 Table for SIS: Product/Sales Organization/Distribution Channel Table Type : TRANSP Package : MCS Module : CRM
• SMOTVKOS Table for Organizational Unit: Divisions per Sales Organization Table Type : TRANSP Package : SMO3 Module : CRM-MSA
• SMOTVKOV Table for Org. Unit: Distribution Channels per Sales Organization Table Type : TRANSP Package : SMO3 Module : CRM-MSA
• SMOTVKWZ Table for Org.Unit: Allowed Plants per Sales Organization Table Type : TRANSP Package : SMO3 Module : CRM-MSA
• TB991 Table for Differentiation Type Element Like Sales Organization Table Type : TRANSP Package : BUPA_COMMON Module : AP-MD-BP
• TB991T Table for Differentiation Type Element Like Sales Organization: Texts Table Type : TRANSP Package : BUPA_COMMON Module : AP-MD-BP
• TNAD1 Table for Output Control: Printers by Sales Organization Table Type : POOL Package : VN0C Module : CRM
• TVKOS Table for Organizational Unit: Divisions per Sales Organization Table Type : TRANSP Package : VZCORE Module : CRM-BTX-BF-IF
• TVKOV Table for Org. Unit: Distribution Channels per Sales Organization Table Type : TRANSP Package : VZCORE Module : CRM-BTX-BF-IF
• TVKWZ Table for Org.Unit: Allowed Plants per Sales Organization Table Type : TRANSP Package : VZ Module : CRM-BTX-BF-IF
• /BEV3/CHRGVKORG Table for Sales Organization Rule Table Type : TRANSP Package : /BEV3/CH Module : SD-SLS-PLL-OBS
• /BEV4/PLDANFVKO Table for Sales Organization-Dependent Control of Request Table Type : TRANSP Package : /BEV4/PL Module : SD-BIL-RB-PL
• /CEM/C_IC_ORGDET Table for Sales Organization Details for Intercompany Processing Table Type : TRANSP Package : /CEM/EE_COMMON Module : CRM-EM
• /DSD/ME_MAT_SOR Table for DSD CN: Material Sales Organization Data Table Type : TRANSP Package : /DSD/ME Module : LE-DSD-DC-CN
• IDPL_SI_TAX Table for Assign Tax Code for Self Invoices to Company Code Table Type : TRANSP Package : ID-FI-PL Module : FI-LOC
• T5PPBSIOE Table for SIOE: Organization code Table Type : TRANSP Package : PB19PS Module : PY-PT-PS
• VKBUK Table Data element for Company code of the sales organization
• SMO3VKBUK Table Data element for Company code of the sales organization
• VKORG_AUFT Table Data element for Sales organization of sales order
• W_MDSPVKO Table Data element for Sales Organization for Suggested Sales Price
• W_SPVKO Table Data element for Sales Organization for Suggested Sales Price
• EESERV_C_LBUKRS Table Data element for Company Code to Which an Auxill. Company Code is Allocated
• GLE_DTE_ECS_ORIG_BUKRS Table Data element for Source Company Code from Cross-Company-Code Posting
• VVKONTO3 Table Data element for Commitments to object company code (Management company code)
• RESCMSUREFCC Table Data element for Reference Company Code for Cross-Company-Code MSUs
• OIUH_OR_LVL_1_NO Table Data element for Organization level 1 number (Company Code)
• OIUH_OR2_OR_LVL_2_NO Table Data element for Second-highest organization level number ( Company Code)
• OIUH_OR3_OR_LVL_3_NO Table Data element for Third-highest organization level number ( Company Code)

Sales organization assignment to company code related terms

Definitions.

SAP is the short form of Systems, Applications & Products in Data Processing. It is one of the largest business process related software. This software focused on business processes on ERP & CRM.

Like most other software, SAP also using database tables to store the data. In SAP thousands of tables are there to store different data. A table contains several fields and some of the fields will be key fields.

Popular Table Searches

Latest table searches.

• Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers
• Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand
• OverflowAI GenAI features for Teams
• OverflowAPI Train & fine-tune LLMs
• Labs The future of collective knowledge sharing
• About the company Visit the blog

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Get early access and see previews of new features.

Relationship between Sales Organization, Sales Office and Sales Group in SAP ERP [closed]

I want to know the relationship between Sales Organization ( VAKPA-VKORG ), Sales Office ( VAKPA-VKBUR ) and Sales Group ( VAKPA-VKGRP ) in SAP ERP.

Relationship in the sense, does One-to-One or One-to-Many relation exist between them, or do they form an hierarchy?

3 Answers 3

A Sales Org is assigned to a company code.

A Division and Distribution Channel are then assigned to the Sales Org (note: these can be assigned to as many sales orgs as you like in as many combinations as you like).

Together, the Sales Org, Division, and Distribution Channel form a Sales Area

Sales Offices are then assigned to the Sales Areas. You can assign a Sales Office to as many Sales Areas as you like. Likewise, multiple Sales Groups can be assigned to a single Sales Office... but also you can assign one Sales Group to multiple Sales Offices.

In summary:

• 1 Company Code : Many Sales Orgs
• {Sales Org, Division, Dist. Ch.} -> 1 Sales Area (you can have as many sales areas as there are permutations of the three)
• Many Sales Offices : Many Sales Areas
• Many Sales Groups : Many Sales Offices

From SAP Help:

Sales Group The definition of sales groups is optional. You can use the SD system without creating sales groups. You can assign a sales group to one or more sales offices.

Sales Office The definition of sales offices is optional. You can use the SD System without creating sales offices. You assign a sales office to one or more sales areas.

Sales Organization Legally, a sales organization is included in exactly one company code. You assign sales offices and your own employees to a sales organization. All items in a sales & distribution document, that is, all items of an order, delivery or a billing document belong to a sales organization.

It looks like you have an hierarchical structure starting at the Sales Org with a 0:n -relationship to Sales Office which in turn have a 0:n -relationship to Sales Group.

• Sales Group check table is TVKGR .
• Sales Office check table is TVBUR .
• Sales Org check table is TVKO .

You can find the sales offices assigned to sales groups by checking the table TVBVK in Tcode SE16N

Not the answer you're looking for? Browse other questions tagged sap-erp or ask your own question .

• Featured on Meta
• Upcoming initiatives on Stack Overflow and across the Stack Exchange network...
• Announcing a change to the data-dump process
• What makes a homepage useful for logged-in users

Hot Network Questions

• Questions about writing a Linear Algebra textbook, with Earth Science applications
• Gloomy anime about suicidal athletes
• Ideas for an alternative to nuclear weapons as a deterrent?
• Is setting setenforce 0 equivalent to setting permissive mode in the configuration and rebooting?
• ミラさん が すんで いた うち を かいました。who brought the house? Me or mira san?
• Default QGIS style symbologies not displaying
• Draw a Regular Reuleaux Polygon
• Mechanism behind a pink human skeleton
• What happened to the job market for assembly programmers once high level languages became mainstream?
• Excel in both teaching and research as a junior faculty member
• Calculate sum of self-exponentation
• Team member working from home is distracted with kids while on video calls - should I say anything as her manager?
• I feel guilty about past behavior in my college
• how to say the adjectival "one-time" / "non-recurrent" in Latin
• Has a rocket engine ever been reused by a second/third stage
• Which civil aircraft use fly-by-wire without mechanical backup?
• Membership and offices in the Privy Council – what is the significance of the different predicates used to describe the transactions?
• Implementation of Euler-Maruyama numerical solver
• Computing norm of a matrix with positive entries
• Looking for piece name/number, it looks like a wedge with 4 studs
• Continued calibration of atomic clocks
• A web site allows upload of pdf/svg files, can we say it is vulnerable to Stored XSS?
• Smallest singular value of triangular matrix with constant rows
• Guarantor for 60-day Indonesia C1 tourism visa?

How to Create Sales Group in SAP | Sales Group in SAP

How to sales group in sap.

The following  SAP tutorials guide you on how to create a sales group in SAP Sales and Distribution (SD)

IMG Menu Path:-

SPRO > SAP Implementation Guide (IMG) > Enterprise Structure > Definition > Sales and Distribution > Maintain Sales Group

Step 1:- Enter T Code SPRO in SAP Command Field and press enter from Keyboard.

Step 2:- In the next screen, Click on SAP Reference IMG.

Step 3:- Follow the IMG Menu Path

Step 4:- Next, click on New entries to maintain a new sales group.

Step 5:- In the Next screen, update the required data

• Sales Group:- Enter 3 digits key of Sales Group
• Description:- Update the description of the sales group

Step 6:- After maintaining the Sales group and description, click on save Icon

Thus sales groups are successfully configured in SAP SD.

Sales by Region & Team

November 03, 2017 - by Bill Jelen

You have a report showing sales for 16 sales reps. Each sales rep belongs to a team. How can you create a report showing total sales for each team?

Watch Video

• Build a Sales Report by Region and Team
• Original data has sales rep and region
• A second (badly shaped) table organizes the sales reps in to teams
• Bill method 1: Re-shape the team hierarchy data. Make both ranges into Ctrl + T tables
• Create a pivot table, adding the data to the data model. Pull Team from second table.
• Create a relationship
• Mike Method2: Build a SUMIFS where the Criteria2 field is an array!
• Pass the SUMIFS in to the SUMPRODUCT function
• Bill Method 3: Rearrange the hierarchy table so sales rep is on the left.
• Add a VLOOKUP to the original data
• Build a pivot table
• Mike Method 4: Use the Relationship icon on the Data tab of the ribbon
• When you create the pivot table, choose Use this Workbook's Data Model
• Bill Method 5: Power Query. Add the lookup table as a Connection Only
• Add the original table as a lookup only
• Merge those two tables, group by to produce the final report

Video Transcript

Dueling ExcelPodcast, Episode 188: Sales Team Report By Region.

Bill:   Hey. Welcome back. It's time for another Dueling Excel Podcast. I'm Bill Jelen from MrExcel. I’ll be joined by Mike Girvin from ExcelIsFun. This is our episode 188, Sales Team Report By Region.

Alright, so, here's the question we have, a dataset over here with various sales reps, how much their sales were by region, and some people have sales in both regions, and then the company has organized those 16 sales reps into these four sales teams, and we're trying to figure out, for each sales team, how much revenue they had.

Alright. So, my approach to this is, you know, I don't like this format here. I'm going to rearrange that format into some sort of a table, a little hierarchy here, that shows for each team who the sales reps are and then, if provided we’re in Excel 2013 or Excel 2016 using Windows and not a Mac, then we can make use of the data model, and, in order to do this, we have to take each of these tables and FORMAT AS TABLE which is CONTROL+T. So, there's the first table which they call Table 8 and the second table which they will call Table 9. I'm going to rename these. I'm going to take the first one and I’m going to call it SALES TABLE and I'm going to take the second one and I'm going to call it TEAM HIERARCHY, like that. Alright.

Now, check this out. Starting in Excel 2013, on the INSERT tab, we create a PIVOT TABLE from the first data set but we say ADD THIS DATA TO THE DATA MODEL which is the boringest way to let you know that you actually have the Power Pivot engine sitting behind Excel 2013. Even if you're not paying for Power Pivot, even if just have the base level Excel Office 365 or Excel, you have that. Alright, so, here's our new report and what I'm going to do is I definitely want to report by REGION, so there's the REGIONS, and I want to see the total SALES but I want to look at this by sales team. Check this out. I’m going to choose ALL and that gives me the other tables in this group, including TEAM HIERARCHY. I'll take the TEAM and move it across the COLUMNS.

Now, the first thing that's going to happen here is we get the wrong answers. That's very, very normal to get the wrong answers. So, what we're going to do is we're going to click CREATE. If you're in ’16, you can AUTO-DETECT. Let's pretend they're in Excel 2013 where we go to our SALES TABLE. There's a field there called SALES REP and it's related to the HIERARCHY, field called SALES REP, click OK, and we have the correct answers. Mike, let's see what you have.

Mike: Thanks, MrExcel. Yes, the data model is an awesome way to go with two different tables to build one pivot table and that's really my preferred method, but if you had to do it with a formula and you needed to have SALES TEAM at the top of each column like this, that means, with the formula, we literally have to look through this data set and, for each record, I have to ask, is the SALES REP = to Gigi or Chin or Sandy or Sheila, and then, if it's a net sale, I have to say, and is the region North America.

Well, we can do that. We can do an AND logical test and an OR logical test in the SUMIFS function. SUM_RANGE, those are all the numbers, so I'm going to click in the top cell, CONTROL+SHIFT+DOWNARROW+F4 , CRITERIA_RANGE, I'm going to highlight the entire SALESREP column, CONTROL+SHIFT+DOWNARROW+F4 ,. Now, normally we put a single item like JUNE SALES REP into criteria. That tells SUMIFS to spit out one answer for JUNE, but, if I highlight 4 different cells -- 1 for each sales rep -- we're instructing SUMSIFS to do a SUMIF for each individual sales rep.

Now, when I copy this formula down, I need it locked, but I copy it to the side, it needs to move. So, I have to hit the F4 key 1, 2 times, lock the row, but not the column. Now I'm going to ). This is a function argument array operation. That's the function argument. The fact that we have multiple items means it's an array operation. So, when I click at the end and hit F9, SUMIFS obeyed us. It spit out the total amount for June, Sioux, Poppi, and Tyrone. [=SUMIFS($B$4:$B$45,$A$4:$A$45,F$4:F$7)]

Now, we need to further limit those amounts by adding an AND condition. We really need it to be June and North America or Sioux and North America or Poppi and North America, and so on. CONTROL+Z. We simply extend , CRITERIA RANGE 2. Now we need to look through the REGION column. CONTROL+SHIFT+DOWNARROW+F4 , and I'm going to click on the single condition, F4 1, 2, 3 times to lock the column but not the row. If I click at the end and F9, those are the totals for each one of our sales rep in North America. When we copy it down, SUMIFS will deliver the total for each sales rep for South America. [=SUMIFS($B$4:$B$45,$A$4:$A$45,F$4:F$7,$C$4:$C$45,$E8)]

Notice it's just SUMIFS delivering multiple numbers we need to add. CONTROL+Z. So, I could put it into this SUM function but the SUM function NUMBER 1 argument will not calculate this array operation correctly without using CONTROL+SHIFT+ENTER. So, I'm going to cheat and use SUMPRODUCT. Now, normally, SUMPRODUCT takes multiple arrays and multiplies them -- that's the PRODUCT part -- and then adds them, but I'm just going to use ARRAY1 and just use the SUM part of SUMPRODUCT, ), CONTROL+ENTER, copy it down and over to the side, and since I got lots of crazy cell references, I'm going to come to the last one in F2 and, sure enough, it's got all of the cells and ranges correct. Alright. I'm going to throw back to MrExcel. [=SUMPRODUCT(SUMIFS($B$4:$B$45,$A$4:$A$45,F$4:F$7,$C$4:$C$45,$E8))]

Bill:   What? That's crazy. Mike. Point to Mike. Oh my gosh. Putting a range of values in SUMIFS and then sending it into SUMPRODUCTS and make it treat it like an ARRAY. Hey, that is wild. We should just stop right there. Point to Mike.

Alright. Let's go back to my method but pretend that you don't have Excel 2013. You're back in Excel 2010 or, worse, Excel for the Mac. I mean, it says it's Excel. I don't know. It just drives me crazy what the Mac can or can't do. So, we’re going to take my HIERARCHY TABLE over here, and, because VLOOKUP can't look to the left, I'm going to take the SALES REP information, CONTROL+X, and paste. Yeah, I know I can do index and match. I'm not in the mood to do index and match today. Alright, so, it's really simple. Here, =VLOOKUP, take that SALESREP name over there, and we will F4 , 2 , EXACTMATCHFALSE like that, double click to copy that down. [=VLOOKUP(A4,$F$4:$G$19,2,FALSE)]

Now that we have all this data back in one table, simple little INSERT, PIVOT TABLE. Even if you don't have the check box at this stage of the data model, we can build our report with SALES TEAM going across, REGION going down, and SALES like that. You can even, here, let's reverse these, REGION across and add the SALES REP in like that, in case you want to see who the sales reps were, and if, by default, if you don't want that, we could just collapse the whole group. So, from here, I go to the ANALYZE tab and collapse. Alright. So, there's our sales teams by region, and then, if someone wants to say, well, who was SALES TEAM 2, we can open that up individually, something like that. Mike, you got another one?

Mike: Still got to love VLOOKUP. It does so many amazing things and, yes, I agree with you MrExcel. Excel for the Mac, that's not even Excel, is it? Alright. Okay. I have another method but I'm going to have to jump over to a different workbook. So, I just have the same two data sets and I've converted them to Excel tables and named them. There's the SALES table, there's the TEAM table, and I like your Power Pivot option so much I'm going to steal that but do it a slightly different way because, as you say, if you have Excel 2013 or later, you have the Power Pivot data model there, but it gets even better. On the DATA ribbon tab -- and I have Excel 2016 -- if you have the RELATIONSHIPS button, you can just build the relationship as if it was a VLOOKUP between these two tables and it will automatically send it to the data model.

So, here's the MANAGE RELATIONSHIPS. I'm going to click NEW. I'm going to select SALES table, SALES REP. This, in essence, is our lookup value, right, and then I'm going to select the lookup table dTEAM, and the SALES REP. This is the lookup table so it can look up SALES REP and return the SALES TEAM, but there's no VLOOKUP column. It simply is two tables in our pivot table field list. Yeah. Look at that, the relationships, when I click OK, it’s sending it to the data model.

Now I'm going to click in a cell off to the side ALT+N+V to open up CREATE PIVOTTABLE dialog box and -- look at that -- it already assumes I want the data model because there's stuff in the data model. Now I click OK and I have my two tables right there. I'm going to click the drop-down, SALES TEAM to ROW, SALES REP down below ROWS, and then SALES from the SALES TABLE down to VALUES. ROW LABELS. I don't like that so I'm going to go up to SHOW IN TABULAR, right click, NUMBER FORMATTING, something like CURRENCY, click OK.

Now, just as MrExcel said, we can collapse this if we do not want to see the SALES REP, and then drag REGION down to COLUMNS, and, just like that, we have all of our sales teams’ totals for each region. I could even open this up. Whether you access the data model either through the check box in CREATE PIVOTTABLES dialog box or simply DATA, RELATIONSHIPS, that is the way to go. So fast and easy, and we can pull fields from two different tables. Alright, I'm going to throw it back to MrExcel.

Bill:   Whoa, Mike, the RELATIONSHIPS out here on the DATA tab, I'm sure I've never noticed that and I guess, in my defense, in the smaller version of Excel here, it doesn't have a word on it. Just looks like a tiny little icon and I realize it was new. That is super, super cool.

Alright. Let’s just do one more here. I'm going to use power query. So, on the DATA tab, GET & TRANSFORM DATA. FROM A TABLE, I select the first table, and I want to take this REGION field and I'm going to pivot it, so I'm going to create a pivot table right here in power query. I'd be careful here. The values are in the SALES area. Click OK. So, now, for each SALES REP, we have their sales to NORTH AMERICA and SOUTH AMERICA, and I'm going to call this ByRep. BYREP. I'll call it BYREP, and then HOME, CLOSE & LOAD, but I'm not going to CLOSE & LOAD to the workbook. I'm going to say ONLY CREATE CONNECTION, like that.

Alright. Then, I'll come to the second one and say that I'm going to create a query FROM A TABLE, alright, and this is just going to stay exactly the way it is. We'll call this TEAMS, and CLOSE & LOAD, CLOSE & LOAD to ONLY CREATE CONNECTION, like that.

Alright. So, now we have two different reports here and I'm going to say that I want to create a COMBINE QUERY, a MERGE QUERY, and my first query is going to be called BYREP, and then I'm going to look up into the TEAMS query. Now, this part is the part that is not intuitive at all. Click on SALES REP here, click on SALES REP here, and we want ALL FROM FIRST, MATCHING FROM SECOND. Click OK. Alright. So, now, here's all of our SALES REP information, what they sold in North America, what they sold in South America, and use the expand icon here, and all we want to get is the TEAM information. I just want to call it TEAM. I don't want to call it TEAMS.TEAM. That would be crazy.

Alright. At this point, we no longer need the SALES REP information. I'll remove that column. I'll take the TEAM and move it over to the left, and then -- check this out -- GROUP BY. We're going to GROUP BY the TEAM and the NEW COLUMN NAME is going to be called NORTH AMERICA, the OPERATION is going to be SUM, the NORTH AMERICA COLUMN, and then we'll add a second one called SOUTH AMERICA, SUM, the SOUTH AMERICA COLULMN. There we go. GROUP BY TEAM, two columns, and we have our information here.

Let's order this. So, on the HOME tab, we want to SORT A to Z. SALES TEAM 1, 2, 3, 4. There's our NORTH AMERICA. There's our SOUTH AMERICA. Now, finally, we'll CLOSE & LOAD and we have our results, and -- check this out -- that's even cooler than that. So, if I go back to BILLPQ and we take POPPI and we move POPPI to SALES TEAM 2 and then come back to our results out here, alright, so, SALES TEAM 2, we should see these numbers increase. Come here and click the refresh icon, and those numbers changed, right? How cool? How cool is that?

Alright, so, wrap up. The goal today, we're going to build a sales report by region and team. The original data has sales rep in region and then there's a lookup table -- in my opinion, badly shaped -- that organizes sales reps into teams. So, my method reshaped that data into a team hierarchy data, make both ranges into Control+T tables, create a pivot table, adding the data to the data model, and then create a relationship. Mike’s method: use SUMIFS where the Criteria2 to field is an array -- didn’t know you could do that -- and then the SUMPRODUCT function. My third method: rearrange the hierarchy table so sales rep is on the left and then do a VLOOKUP building a pivot table. Mike's method: use the RELATIONSHIP icon to build a relationship first, and then a pivot table from the workbook data model. And then, the fifth version -- the no VLOOKUP-no pivot table version in case you're afraid of both of those -- power query. Add the lookup table as a connection only, add the original table as a lookup only, doing the pivot right there to get North America and South America,  merge those two tables, group by, and then group by within power query, and you can refresh.

Alright. Well, hey. I want to thank you for stopping by for this very long Dueling Excel Podcast. We'll see you next time for another episode from MrExcel and ExcelIsFun.

Download File

Download the sample file here: Duel188.xlsm

Title Photo: MichaelGaida / Pixabay

• Implementing Common Features for Financials and Project Management

What reference data objects can be shared across business units?

The following table contains the reference data objects for the Oracle Fusion Applications that can be shared across business units and the method in which the reference data for each is shared.

• Integrations
• Learning Center

MoSCoW Prioritization

What is moscow prioritization.

MoSCoW prioritization, also known as the MoSCoW method or MoSCoW analysis, is a popular prioritization technique for managing requirements. 

  The acronym MoSCoW represents four categories of initiatives: must-have, should-have, could-have, and won’t-have, or will not have right now. Some companies also use the “W” in MoSCoW to mean “wish.”

What is the History of the MoSCoW Method?

Software development expert Dai Clegg created the MoSCoW method while working at Oracle. He designed the framework to help his team prioritize tasks during development work on product releases.

You can find a detailed account of using MoSCoW prioritization in the Dynamic System Development Method (DSDM) handbook . But because MoSCoW can prioritize tasks within any time-boxed project, teams have adapted the method for a broad range of uses.

How Does MoSCoW Prioritization Work?

Before running a MoSCoW analysis, a few things need to happen. First, key stakeholders and the product team need to get aligned on objectives and prioritization factors. Then, all participants must agree on which initiatives to prioritize.

At this point, your team should also discuss how they will settle any disagreements in prioritization. If you can establish how to resolve disputes before they come up, you can help prevent those disagreements from holding up progress.

Finally, you’ll also want to reach a consensus on what percentage of resources you’d like to allocate to each category.

With the groundwork complete, you may begin determining which category is most appropriate for each initiative. But, first, let’s further break down each category in the MoSCoW method.

Start prioritizing your roadmap

Moscow prioritization categories.

1. Must-have initiatives

As the name suggests, this category consists of initiatives that are “musts” for your team. They represent non-negotiable needs for the project, product, or release in question. For example, if you’re releasing a healthcare application, a must-have initiative may be security functionalities that help maintain compliance.

The “must-have” category requires the team to complete a mandatory task. If you’re unsure about whether something belongs in this category, ask yourself the following.

If the product won’t work without an initiative, or the release becomes useless without it, the initiative is most likely a “must-have.”

2. Should-have initiatives

Should-have initiatives are just a step below must-haves. They are essential to the product, project, or release, but they are not vital. If left out, the product or project still functions. However, the initiatives may add significant value.

“Should-have” initiatives are different from “must-have” initiatives in that they can get scheduled for a future release without impacting the current one. For example, performance improvements, minor bug fixes, or new functionality may be “should-have” initiatives. Without them, the product still works.

3. Could-have initiatives

Another way of describing “could-have” initiatives is nice-to-haves. “Could-have” initiatives are not necessary to the core function of the product. However, compared with “should-have” initiatives, they have a much smaller impact on the outcome if left out.

So, initiatives placed in the “could-have” category are often the first to be deprioritized if a project in the “should-have” or “must-have” category ends up larger than expected.

4. Will not have (this time)

One benefit of the MoSCoW method is that it places several initiatives in the “will-not-have” category. The category can manage expectations about what the team will not include in a specific release (or another timeframe you’re prioritizing).

Placing initiatives in the “will-not-have” category is one way to help prevent scope creep . If initiatives are in this category, the team knows they are not a priority for this specific time frame. 

Some initiatives in the “will-not-have” group will be prioritized in the future, while others are not likely to happen. Some teams decide to differentiate between those by creating a subcategory within this group.

How Can Development Teams Use MoSCoW?

  Although Dai Clegg developed the approach to help prioritize tasks around his team’s limited time, the MoSCoW method also works when a development team faces limitations other than time. For example: 

Prioritize based on budgetary constraints.

What if a development team’s limiting factor is not a deadline but a tight budget imposed by the company? Working with the product managers, the team can use MoSCoW first to decide on the initiatives that represent must-haves and the should-haves. Then, using the development department’s budget as the guide, the team can figure out which items they can complete. 

Prioritize based on the team’s skillsets.

A cross-functional product team might also find itself constrained by the experience and expertise of its developers. If the product roadmap calls for functionality the team does not have the skills to build, this limiting factor will play into scoring those items in their MoSCoW analysis.

Prioritize based on competing needs at the company.

Cross-functional teams can also find themselves constrained by other company priorities. The team wants to make progress on a new product release, but the executive staff has created tight deadlines for further releases in the same timeframe. In this case, the team can use MoSCoW to determine which aspects of their desired release represent must-haves and temporarily backlog everything else.

What Are the Drawbacks of MoSCoW Prioritization?

  Although many product and development teams have prioritized MoSCoW, the approach has potential pitfalls. Here are a few examples.

1. An inconsistent scoring process can lead to tasks placed in the wrong categories.

  One common criticism against MoSCoW is that it does not include an objective methodology for ranking initiatives against each other. Your team will need to bring this methodology to your analysis. The MoSCoW approach works only to ensure that your team applies a consistent scoring system for all initiatives.

Pro tip: One proven method is weighted scoring, where your team measures each initiative on your backlog against a standard set of cost and benefit criteria. You can use the weighted scoring approach in ProductPlan’s roadmap app .

2. Not including all relevant stakeholders can lead to items placed in the wrong categories.

To know which of your team’s initiatives represent must-haves for your product and which are merely should-haves, you will need as much context as possible.

For example, you might need someone from your sales team to let you know how important (or unimportant) prospective buyers view a proposed new feature.

One pitfall of the MoSCoW method is that you could make poor decisions about where to slot each initiative unless your team receives input from all relevant stakeholders. 

3. Team bias for (or against) initiatives can undermine MoSCoW’s effectiveness.

Because MoSCoW does not include an objective scoring method, your team members can fall victim to their own opinions about certain initiatives. 

One risk of using MoSCoW prioritization is that a team can mistakenly think MoSCoW itself represents an objective way of measuring the items on their list. They discuss an initiative, agree that it is a “should have,” and move on to the next.

But your team will also need an objective and consistent framework for ranking all initiatives. That is the only way to minimize your team’s biases in favor of items or against them.

When Do You Use the MoSCoW Method for Prioritization?

MoSCoW prioritization is effective for teams that want to include representatives from the whole organization in their process. You can capture a broader perspective by involving participants from various functional departments.

Another reason you may want to use MoSCoW prioritization is it allows your team to determine how much effort goes into each category. Therefore, you can ensure you’re delivering a good variety of initiatives in each release.

What Are Best Practices for Using MoSCoW Prioritization?

If you’re considering giving MoSCoW prioritization a try, here are a few steps to keep in mind. Incorporating these into your process will help your team gain more value from the MoSCoW method.

1. Choose an objective ranking or scoring system.

Remember, MoSCoW helps your team group items into the appropriate buckets—from must-have items down to your longer-term wish list. But MoSCoW itself doesn’t help you determine which item belongs in which category.

You will need a separate ranking methodology. You can choose from many, such as:

• Weighted scoring
• Value vs. complexity
• Buy-a-feature
• Opportunity scoring

For help finding the best scoring methodology for your team, check out ProductPlan’s article: 7 strategies to choose the best features for your product .

2. Seek input from all key stakeholders.

To make sure you’re placing each initiative into the right bucket—must-have, should-have, could-have, or won’t-have—your team needs context. 

At the beginning of your MoSCoW method, your team should consider which stakeholders can provide valuable context and insights. Sales? Customer success? The executive staff? Product managers in another area of your business? Include them in your initiative scoring process if you think they can help you see opportunities or threats your team might miss. 

3. Share your MoSCoW process across your organization.

MoSCoW gives your team a tangible way to show your organization prioritizing initiatives for your products or projects. 

The method can help you build company-wide consensus for your work, or at least help you show stakeholders why you made the decisions you did.

Communicating your team’s prioritization strategy also helps you set expectations across the business. When they see your methodology for choosing one initiative over another, stakeholders in other departments will understand that your team has thought through and weighed all decisions you’ve made. 

If any stakeholders have an issue with one of your decisions, they will understand that they can’t simply complain—they’ll need to present you with evidence to alter your course of action.  

Related Terms

2×2 prioritization matrix / Eisenhower matrix / DACI decision-making framework / ICE scoring model / RICE scoring model

Prioritizing your roadmap using our guide

Talk to an expert.

Schedule a few minutes with us to share more about your product roadmapping goals and we'll tailor a demo to show you how easy it is to build strategic roadmaps, align behind customer needs, prioritize, and measure success.

Share on Mastodon

In this topic, we described about the Assign Sales organization – Distribution channel to plant process along with technical information.

For every Organisation, sales organisation and plant should be existed. Plant manufactures the goods and organization sells them in market through different distribution channels.

So, the Sales organization, distribution channel and plant should be linked with each other. The linking can be achieved by assigning sales organization – distribution channel to plant.

Assign Sales organization – Distribution channel to plant

Below process is step by step procedure to assign sales organization (TCS1), distribution channel (T1) to plant (TCPD).

Step-1: Enter the transaction code OVX6N in the SAP command field and click Enter to continue.

Enter the transaction code SPRO in the SAP command field and click Enter to continue.

Click on SAP Reference IMG .

Expand SAP Customizing Implementation Guide → Enterprise Structure → Assignment → Sales and Distribution → Assign sales organization – distribution channel - plant . Click on Execute .

Step-2: In the next screen, click on New Entries .

Step-3: In the next screen, enter the below details and click on Enter .

• SOrg. - Specify the sales organization code
• DChCust/Mt - Specify the distribution channel code
• Plnt - Specify the plant code

Step-4: Once all the details entered, click on Save button to save the details.

Step-5: It prompt for the Change Request. Create/Select the change request and Click on right mark to proceed.

Step-6: Status bar displays the below message once the sales organization, distribution channel, plant assigned together successfully.

Technical details: -

• Transaction: OVX6N
• Menu Path: SPRO → SAP Reference IMG → SAP Customizing Implementation Guide → Enterprise Structure → Assignment → Sales and Distribution → Assign sales organization – distribution channel - plant

Microcity Sales Office by Mossine Partners, Moscow, Rusia

Mossine Partners have designed this futuristic bubbles structure as a temporary sales office. It is located in Moscow region, Russia.The initial design was created by Studio Mossine Partners and resembles the use of membrane as a structural elements. This temporary structure meets all requirements and apart from creating a very innovative facade system. The structure houses a showroom and office for the real estate company that’s developing the site. The internal program is organized into three zones: the largest central ‘bubble’ houses an exhibition area with 1:1 apartment models. Branching off this are two smaller ‘bubbles’ with a sales area for managers in one and a relax area, complete with café and playroom for children, in the other.

Copyright © 2016 - 2024 DesignRulz . All rights reserved.