SD Organizational Structure

Hi All
Could you please send me material you have regarding SD certification?
I will reward points.
Many Thanks.
Message was edited by:
        Ramesh Kollepara
Message was edited by:
        Surya

dear surya
ENTERPRISE STRUCTURE
Company Code: - It is the company for which we implement SAP.
NOTE: - It is defined by FI Consultants.
Sales Organisation: - It is the organizational unit, which is responsible for the sales activities in the company.
Distribution Channel: - It is the channel through which goods are reaching the customers.
Divisions: - The range of products or services that the company manufacturing falls into different divisions.
Sales Area: - It is the combination of sales Organisation, distribution channel and Division.
Sales Line: - It is the combination of Sales Organisation and distribution channel.
Sales Office: - It is the Geographical aspect of the structure.
Sales Group: - The employees in a sales office can be divided into different sales groups.
Plant: - The factory is called the plant in SAP.
RELATIONSHIPS:
Company code to Sales Organisation: - One company code can have many sales organizations. But one Organisation has to be assigned to one company code. So the relation is one to many.
Sales Organisation to Distribution channel: - One Organisation can have many distribution channels. One Distribution channel can be assigned to many organizations, so the relation is Many to Many.
Sales Organisation to Division: - One Organisation can have many divisions. One division can be assigned to many organizations. So the relationship is Many to Many.
Distribution channel to Division: - One Distribution channel can have many divisions. One division can be assigned to many Distribution channels. So the relationship is Many to Many.
NOTE: - Division is always Organisation specific.
NOTE: - If sales Organisation wants to use a plant that plant must be
assigned to the Sales Organisation.
Logistics
Sales and Distribution
Basic Function and Master Data in Sales and Distribution
Master data in Sales and Distribution
Organisational Structures
Organisational Structures in Sales and Distribution
Defining Sales Organisation: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Define Copy, Delete, Check Sales organization [EC04]
Go to Define Copy, Delete, Check Sales organization,
Go to Copy Organisational Object,
Come back
Define Sales Organisation
Select defined sales Organisation and go to details.
Select the Address icon & maintain the details and save it.
NOTE: - To unlock the locked data use the Transaction code SM12.
Rebate Process Active: - It controls whether rebate processing is active for a particular sales Organisation.
Defining Distribution Channel: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Define Copy, Delete, Check Distribution Channel [EC05]
Go to Define Copy, Delete, Check Distribution Channel
Go to Copy Organisational Object,
Come back
Go to Define Distribution Channel
Select defined sales Organisation and give the required name and save it.
Defining Division: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Define Copy, Delete, Check Division [EC06]
Go to Define Copy, Delete, Check Division
Go to Copy Organisational Object,
Come back
Go to Define Division
Select defined division and give the required name and save it.
Defining Sales Office: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Maintain Sales Office
Go to New entries and define the sales office
Go to Address Icon and maintain the details and save it.
Defining Sales Group: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Maintain Sales Group
Go to New entries and define the Sales Group
Go to Address Icon and maintain the details and save it.
Defining a Plant: -
SPRO
Enterprise Structure
Definition
Logistics General
Define, Copy, Delete, Check Plant [EC02]
Go to copy organisational object
Come back
Go to Define Plant
Select the defined Plant and go to details Address and Maintain Details and Edit details and save it.
Defining Company Code: -
SPRO
Enterprise Structure
Definition
Financial Accounting
Edit Copy, Delete, Check Company code [EC01]
Go to Define Company and save it.
Assigning Sales Organisation to the Company Code: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Sales Organisation to Company Code [OVX3]
Select the Company Code and go to assign from the list of sales Organisations and select required Sales Organisations and assign and save it.
Assigning Distribution Channels to Sales Organisations: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Distribution Channels to Sales Organisation [OVXK]
Select the Sales Organisation and go to assign from the list of the Distribution Channels and select required Distribution Channels and assign and save it.
Assigning Division to Sales Organisations: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Division to Sales Organisation [OVXA]
Select the Sales Organisation and go to assign from the list of the Divisions and select required Divisions and assign and save it.
Defining Sales area: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Setup Sales area [OVXG]
Select the Sales Organisation and assign Distribution channels
Select the distribution channel and assign the divisions and save it.
Assigning Sales Office to Sales area: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Sales Office to Sales are [OVXM]
Select the required Sales Area and assign the Sales Office.
Assigning the Plant to the Company Code: -
SPRO
Enterprise Structure
Assignment
Logistics General
Assign Plant to Company code [OX18]
Select the Company code and assign the required Plants.
Assigning the Plant to Sales Organisation: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Sales Organisation – Distribution Channel – Plant [OVX6]
Select the required sales line and assign the required Plants.
2. MASTER DATA (MD)
Master Data is divided into:
Customer Master Data
Material Master Data
Conditions Master Data
Customer Material Information Record
1. Customer Master Data: -
Logistics
Sales and Distribution
Master Data
Business Partner
Customer
Create
XD01 – Complete
Change
XD02 – Change
Display
XD03 – Display
The Customer Master Data contains 3 screens:
a. General Data
b. Company Code Data
c. Sales Area Data
Each screen contains different tab pages; each tab page contains different fields.
a. General Data screen: -
Marketing Tab Page: -
Customer Classification: - Specifies a classification of the customer for
Ex: - classifies the customer as a bulk buyer or it can be based on turnover.
Defining Customer Classification: -
SPRO
Sales and Distribution
Master data
Business Partner
Customers
Marketing
Define Customer Classifications
Go to new entries and define and save it.
Unloading Points Tab page: -
Unloading Point: - Specifies the point at which the material is to be unloaded.
Goods Receiving Hours: - Specifies the timings in which the customer can receive the goods.
Defining Goods Receiving Hours: -
SPRO
Sales and Distribution
Business Partner
Customers
Shipping
Define Goods Receiving Hours [OVSC]
Go to new entries and define and save it.
Contact persons tab page: - Enter the contact persons of the customer.
a. Company Code Data Screen: -
Account Management tab page: -
Reconciliation Account: - The Reconciliation account in General Ledger accounting is the account, which is, updated parallel to the sub ledger account for normal postings.
Payment Transactions tab page: -
Terms of Payment: - Specifies the key for defining payment terms composed of cash discount percentages and payment periods.
Defining terms of payment: -
SPRO
Sales and Distribution
Master Data
Business Partners
Customers
Billing Documents
Define terms of payment
Go to new entries and define and save it.
Payment History Record: - If we check this field the payment history of the customer will be recorded in his credit management.
To change the customer details go to xd02 and change the values and save it.
b. Sales Area Data Screen: -
Sales Tab Page: -
Sales District: - Specifies in which district the customer is there.
Before specifying the sales district we should define the sales district.
Defining Sales District: -
SPRO
Sales and Distribution
Master Data
Business Partners
Customers
Sales
Define sales district [OVR0]
Go to new entries and define and save it.
Customer Group: - Identifies a particular group of customers (for Ex: -wholesale or Retail) for the purpose of pricing or generating statistics.
Defining Customer Group: -
SPRO
Sales and Distribution
Master Data
Business Partners
Customers
Sales
Define customer groups [OVS9]
Go to new entries and define and save it.
Customer Pricing Procedure: - This field along with few other fields determines the pricing procedure that is given to a customer. [1]
Shipping Tab Page: -
Shipping Conditions: - This field along with few other fields determines the shipping point that is proposed by the system.
Defining Shipping Conditions: -
SPRO
Logistics Execution
Shipping
Basic shipping functions
Shipping point and goods receiving point determination scheduling
Define shipping conditions
Go to new entries and define and save it.
Delivering Plant: - Specifies the plant from which the goods should be delivered to the customer.
Order Combination: - If we want to combine multiple orders for the customer to create a single delivery we need to check this field.
Partial delivery per Item: - Specifies whether the customer requires full or partial delivery for the item.
Maximum partial delivery is 9.
Billing Documents Tab Page: -
Rebates: - If the customer wants to receive the rebates check this field.
If we check this field the customer can get rebates from the company.
Incoterms: - Incoterms specifies certain internationally recognised procedures that the shipper and the receiving party must follow for the shipping transaction to be successfully completed.
Account Assignment Group: - This field along with few other fields determines the General Ledger Account to which the sales values are to be posted.
Tax classification: - Specifies whether the customer is liable for tax or not.
Partner Functions Tab Page: -
Sold-to-Party (SP): - The customer who is placing order with the company.
Ship-to-Party (SH): - The customer who is receiving the goods.
Bill-to-Party (BP): - The customer on whom the bill is raised.
Payer (PY): - The customer who pays the bill.
Creating the Customer: -
Logistics
Sales and Distribution
Master Data
Business Partner
Customer
Create
XD01
Change
XD02
Display
XD03
Enter the Account Group [Here specify whether the customer is a SP, SH, BP or PY]
Enter the Account Group
Enter the Company Code
Enter the Sales Area
NOTE: - If we get the error sales area is not defined for the customers.
SPRO
Sales and Distribution
Master data
Define common distribution channels [VOR1]
And also go to
Define common divisions [VOR2]
Defining Account Groups: -
SPRO
Financial Accounting
Accounts Receivable and Accounts payable
Customer Accounts
Master Data / Records
Preparations for creating customer master data / record
Define account groups with screen layout (customer)
0001  Sold-to-party
Ship-to-party0002
Bill-to-party0003
0004  Payer
If the definition of the account group we can control the field status. We can make fields mandatory or optional or suppress or display mode.
Defining the number ranges for Account Groups: -
SPRO
Financial Accounting
Accounts Receivable and Accounts payable
Customer Accounts
Master Data / Records
Preparations for creating customer master data / record
Create number ranges for customer accounts [XDN1]
Go to change intervals
Select the button insert interval and define a number range.
NOTE: - If we check the field external for a number range it becomes an external assignment. Otherwise it becomes internal assignment.
Assigning the number ranges for Customer Account Groups: -
SPRO
Financial Accounting
Accounts Receivable and Accounts payable
Customer Accounts
Master Data / Records
Preparations for creating customer master data / record
Assign number ranges for customer account groups.
Assign the required number range to the account group.
Partner determination procedure: -
SPRO
Sales and Distribution
Basic Functions
Partner determination
Setup partner determination
Select setup partner determination for customer master
Step 1: -
Defining the Partner Functions: - Here we must not define any partner function.
Go to partner functions.
While defining the partner functions if we check the field “Unique” that partner faction has to be unique in the customer master i.e. we cannot have multiple partners of that function in a customer master.
Step 2: -
Assigning the partner functions to the Account group: -
Go to account group’s function assignment.
Go to new entries and assign the required partner functions to the required account group and save it.
Step 3: -
Defining the partner determination procedure: -
Go to partner determination procedures
Go to new entries and define and save it
NOTE: - Procedure contains all the required partner functions.
Step 4: -
Placing the required partner functions in the procedure: - select the defined procedure and go to partner functions in procedure.
Go to new entries and place the partner functions
If we check the field “Not Modifiable” for a partner function it cannot change in the customer master.
If we check the field “Mandatory Function” it becomes a mandatory in the customer master and save it.
Step 5: -
Assigning the procedure to the Account Group: - Go to partner determination procedure assignment. Assign the procedure to the account group and save it.
2. Material Master Data: -
Logistics
Sales and Distribution
Master Data
Products
Material
Other Material
Create
MM01
Change
MM02
Display
MM03
Material master contains different views.
Enter the material number
Enter the industry sector
Enter the material type
Go to select views
Select the following views:
Basic Data 1
Basic Data 2
Sales Organisation Data 1
Sales Organisation Data 2
Sales General and plant data
Sales text
MRP 1
Accounting 1 and select organisational levels
Enter the plant
Enter the sales Organisation then distribution channel
Basic Data 1: -
Base unit of measure: - Specifies the unit of measure in which stocks of the material are managed.
Material Group: - Key that we use to group together several materials or services with the same attributes.
Defining Material Group: -
SPRO
Logistics General
Material Master
Setting for key fields
Define Material groups [OMSF]
Division: - Specifies in which division the material falls.
Gross Weight and Net Weight: - Specify the weight of the material.
Weight Unit: - Specifies the weight unit.
Sales Organisation Data 1: -
Base Unit of Measure: -
Sales Unit: - Here enter the unit of measure in which the material sold. We need to enter a value in this field if the sales unit differs from base unit of measure.
Note: - If the sales unit differs from the base unit we can maintain the conversion factors. To see that information go to additional data.
Delivering Plant: - Specifies the plant from which the material is delivered to the customer.
Cash Discount: - If we check this field we can give cash discounts for this material.
Tax classification: - Specifies whether the material is liable for tax or not.
Note: - To leave the tax both the customer and the material must be liable for tax.
Minimum Order quantity: - Specifies the minimum quantity in the base unit of measure that a customer may order for base material.
Minimum Delivery quantity: - Specifies the minimum quantity that can be delivered to the customer.
Rounding Profile: - Key that the system uses to adjust the order proposal quantity to the deliverable units.
Sales Organisation Data 2: -
Account assignment Group: - This field along with other fields determines the General Ledger Accounts to which different sales values are to be posted.
Item Category Group: - It determines the nature of the material we are defining.
Ex: -
Standard ItemNORM
Service or DeliveryLEIS
Third partyBANS  Item
BOM ItemERLA/LUMF
PackagingVERP
Sales general / plant: -
Availability check: - Specifies whether and how the system checks the availability of the material and generating the requirement for the materials planning.
Batch Management: - Specifies whether the material is managed in Batches.
Transportation Group: - Grouping of the materials that share the same transportation requirement
Defining Transportation Group: -
SPRO
Logistics Execution
Shipping
Basic shipping functions
Routes
Route determination
Define transportation Group
Loading Group: - Grouping of the materials that share the same loading requirement.
Defining Loading Group: -
SPRO
Logistics Execution
Shipping
Basic Shipping Functions
Shipping point and Goods Receiving point determination scheduling
Define loading Group
MRP: - Material Requirement Planning
MRP 1: -
MRP Type: - Specifies how the requirement of the material can be planned.
Accounting 1: -
Valuation Class: -
Note: - Before creating the material master we should activate company code for material master.
Maintain Company codes for Material Management: -
SPRO
Logistics General
Material Master
Basic settings
Maintain company codes for material management [OMSY]
Define Storage Location: -
SPRO
Enterprise Structure
Definition
Materials Management
Maintain storage location [OX09]
Enter the plant number
Go to New entries
Extending the Organisational views for the Material Master: -
MM01-Create.
Enter the material, which you have already created.
Copy from material = material
Select the organisational views
Select the organisational levels
In the copy from fields enters the values in which the material has been already created.
In the fields on the left side of the screen enter the values to which we would like extend the material.
3. Customer Material Information Record: - We need to maintain this record then the customers are having their own names for the material rather the original names.
Note: - We need to enter the customer material number in the sales order on
the “Ordering Party” tab page, when we enter the customer material number in the sales order the system will automatically take the original material number.
Creating Customer Material Information Record: -
Logistics
Sales and Distribution
Master Data
Rebate Arrangements
Customer Material Information
VD51 – Create.
Material Number: - In this field enter the original name of the material
Customer Material: - Here enter the material number by which the customer places order.
Creating Sales Order: -
Logistics
Sales and Distribution
Sales
Order
VA01 – Create
Enter the order type “OR” & Enter the sales area.
Note: - To maintain the currency conversion rates use the transaction code
OC41.
4. Conditions Master Data: -
Condition Elements: -
a. Price
b. Discount or Surcharge
c. Tax
d. Freight
Ex: - for Condition Types: -
PricePR00 
Material DiscountK004
Customer DiscountK007
CustomerK005  Material Discount
FreightKF00
Maintaining the values for these condition types is called condition records.
Maintaining the condition records for condition types is conditions master data.
Maintaining Condition Records: -
Logistics
Sales and Distribution
Master Data
Conditions
Selecting using condition type
VK11 – create
Enter the condition type for which you are maintaining conditions Record.
Select the required key combination
In the material field enter the material for which we are maintaining the conditions record.
Enter the amount the system will automatically take currency and the calculation type.
Valid on and valid to: - The condition record is valid for those orders, which comes from the customer in the specified validity period.
Scales: - If we want to reduce or increase the amount as the quantity is increase select the condition record and go to scales.
Note: - Don’t enter any value in the first line.
Setting upper limit and lower limit: - Select the condition record and go to details.
Note: - The price information in the sales order can be seen on the conditions tab page.
3. SALES DOCUMENT PROCESSING (SDP)
Structure of the Sales Document:
Header Data: - The general data that is valid for the entire document is recorded in the document header. For Ex: - Sold-to-party, Ship to party, Document date….
Item Data: - The data in the document header applies to all items in the document but same data applies only two specific items. This data is stored at item level.
Ex: - Material number, order quantity, ship to party, pricing, plant and
storage location.
Scheduling Line Data: - It gives the information about the delivery dates and the corresponding conformed quantities.
Note: - An item can have multiple schedule lines.
To see the header data in the sales document. Select the Icon “Display Document Header Details” or select “Go to Header and select any tab page”.
To see the Item data select “Go to Item and select any tab page” or double click on the item.
Note: - To Change the Ship to party at the item level select the partner
tab page and change it.
To see the schedule line data go to item data and select the tab page schedule lines.
Creating the Sales Documents with Reference:
Creating Quotation: -
Logistics
Sales and Distribution
Sales
Quotation
VA21 – Create
Creating Order with reference to Quotation: -
Logistics
Sales and Distribution
Sales
Order
VA01 – Create
Enter the order type “OR” and the sales area.
Select the button Create with Reference.
Specify the quotation number and say copy.
Document Flow: - When we create the documents with reference to some preceding documents it forms a document flow. In this flow if we know one document number with the help of “Document Flow”. We can know the remaining document numbers.
Note: - To See the remaining document numbers, go to the any sales
document in the flow and select the icon “Display document flow”.
Note: - If we get the error the order type is not defined for sales area.
SPRO
Sales and Distribution
Sales
Sales documents
Sales documents header
Assign sales area to sales document types
Sales Document Types: -
SPRO
Sales and Distribution
Sales
Sales Document
Sales Document Header
Define Sales Document type [VOV8]
Ex: -
IN  Inquiry
QuotationQT
OrderOR
Returns sales documentsRE
CS  Cash Sale
Rush OrderRO
Scheduling AgreementDS
Functionality of the sales document type: -
Sales Document Category: - It’s a classification for the different types of documents that we can process in the sales and distribution system
Ex: -
InquiryA
QuotationB
C  Order
Sales Document Block: - Determines whether the sales document is blocked for use. If we block a sales document type users cannot create new sales documents of this type.
Number range internal assignment and Number range external assignment: - Number that determines how the documents are to the numbered by the system. It indicates which number range is relevant for document type.
Creating Number ranges for sales Documents: -
SPRO
Sales and Distribution
Sales
Sales Documents
Sales Document header
Define number ranges for sales documents [VN01]
Item Number Increment: - Specifies the increment by which you want the item numbers in the sales document to increase when the system automatically generates the item number.
Sub Item Increment: - This is for sub items.
Reference Mandatory: - Indicates whether a reference document is mandatory when we create a sales document. If so the indicator also specifies which type of reference document we should use.
Item Division: - If we check this field the division at the item level is proposed from the material master record of the item otherwise the division we enter in the sales document header also counts for all the items.
Check Division: - Controls how the system reacts during the sales order processing when the division at the item level differs from the division in the document header.
Read Info Record: - Determines whether the system read the customer material information record for the sales document type.
Check Credit Limit: - Specifies whether the system runs credit checks and how it response to the check during the sales order processing.
Check purchase order number: - Specifies whether the system should check if the purchase order number entered is already existing for other sales document.
Screen Sequence Group: - Controls which screen we see during a particular transaction and in which sequence they appear.
Transaction Group: - It’s a grouping that allows you to control certain characteristics of a transaction according to sales document type.
Document Pricing Procedure: - This field along with few other fields determines the pricing procedure that is proposed by the system.
Display Range: - Specifies whether the system displays only main items or sub items or all the items in the sales document.
F code for over view screen: - Determines which overview screen we reach during the sales order processing after we enter the data in the initial sales document screen.
Quotation Messages: - Set an indicator here if you want to receive a message informing you that open quotations exist when we create a sales document. Depending on the indicator we select the system searches for open quotations in the sales document either at the header level for the customer or item level for the material.
Outline agreement messages: - This is for agreements.
Incomplete Messages: - Specifies whether an incomplete document can be saved. If we check this field we cannot save the incomplete document until we enter the missing data.
Delivery type: - specifies the corresponding delivery document type for the sales document.
Outbound delivery with reference toEx: - LF  order.
Delivery Block: - Indicates it the entire sales document is blocked for delivery.
Shipping Conditions: - If we specify the shipping condition here the value from the customer master record is over return by this value.
BILLING: -
Delivery related billing type and order related Billing type: - Specifies the corresponding billing document types.
Ex: -  InvoiceF2
Billing Block: - Indicates whether the item is blocked for billing or not.
Propose Delivery Date: - If we check this field the system automatically proposes the current date as the delivery date.
Lead-time in days: - Specifies the number of days after the current date that the sales document uses for the proposal of the requested delivery date.
Propose P O Date: - If we check this field the system automatically proposes the current date as the purchase order date.
Contract Data allowed: - This field controls whether we can enter the contract data for the sales document type.
Item Categories: -
InquiryAFN
AGN  Quotation Standard Item
Sales OrderTAN
INAFNN
QT FreeAGNN  of charge Item
ORTANN 
Third Party ItemTAS
Defining Item Categories: -
SPRO
Sales and Distribution
Sales
Sales Documents
Sales Document item
Define item categories
Functionality of the Item Categories: -
Billing Relevance: - Specifies the reference document to create the billing document.
Pricing: - Specifies whether an item is relevant for pricing or not
Business item: - If we check this field during the sales order processing the business data that we enter an item is allowed to differ from the business data in the header.
Schedule Line allowed: - Indicates whether we can create schedule lines for the item.
Item relevant for delivery: - Indicates whether a text item is relevant for delivery processing.
Note: - We need to check this field in the item category “TATX”. Which is
for text items.
Returns: - If we check this field it becomes a returns item.
Note: - We need to check this field in the item category “REN”. Which is
for returns.
Weight / Volume Relevant: - Indicator that controls whether the system calculates weight and volume for the item in the sales document.
Credit Active: - Indicates whether the credit management functions are active for the document items.
Determine Cost: - Indicates whether the system determines the cost of a sales document item during pricing.
Note: - The cost condition type is “VPRS”.
Automatic Batch Determination: - If we want to use automatic batch determination for materials handled in the batch active this field.
Rounding Permitted: - Indicates whether rounding is permitted or not.
Note: - Depending on the rounding profile specified in the material master the order quantity can be rounded in the sales order.
Order Quantity = 1: - If we check this field the order quantity for each line item is limited to one.
Item Category Determination: -
SPRO
Sales and Distribution
Sales
Sales Documents
Sales Document Item
Assign Item Categories
We have to assign the item category to the combination of
Sales Document type
Item category group
Usage
Higher lever item category
Schedule line categories: -
Defining Schedule line categories: -
SPRO
Sales and Distribution
Sales
Sales Documents
Schedule Lines
Define schedule line categories [VOV6]
CS  Third party item
Inquiry schedule lineAT
Sales orderCP, CV, CN  schedule lines
QuotationBN
Functionality of a Schedule Line Category: -
Movement type: - Specifies the physical or logical movement of materials leading to a change in the stock levels or resulting in the consumption of the material.
Goods Issue Delivery601
602  Returns
Posting the stock in the plant561
Plant to plant stock301  transfer
Return of the stock transfer302
Item relevant for Delivery: - Indicates whether the item that is related to a schedule line is relevant for delivery or not.
Order type: - Specifies the order type “NB” purchase requisition.
Note: - We need to specify, “NB” in this field for the schedule line category “CS” which is used for third party item.
Requirement/Assembly: - If we check this field the transfer of requirements will take place into the inventory management for a better planning of material requirement.
Availability: - Specifies whether the system should check the availability of the material.
Schedule line category determination: -
SPRO
Sales and Distribution
Sales
Sales Documents
Schedule Lines
Assign schedule line categories
We need to assign the schedule line category to the combination of Item category and MRP Type.
NORMItem category group
Sales Document
IN
AFN
+MRP Type
AT Item Relevant Delivery
QT
AGN
+MRP Type
BN Item Relevant Delivery
OR
TAN
+MRP Type
CP Item Relevant Delivery
4. PRICING (PG)
This concept is based on condition technique.
It’s the combination of:
1) Condition Tables
2) Access Sequence
3) Condition Types
4) Pricing Procedure
1. Condition Tables: - Condition table contain the key fields for maintaining condition records. I.e. in other words condition records are stored in condition table.
Note: - A condition type can have multiple condition tables.
Note: - A condition table can be used for multiple condition types.
Defining condition tables: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define condition tables [V/03]
Create condition tables
Enter a table number beyond 600
From the field catalogue, which is there on the right side of the screen select the required key fields.
To get the valid on / valid to fields while maintaining the condition records we need to check the field “with validity period”.
Go to icon Technical View
The fields which are marked, as footer field appears at the footer level at the condition records and the remaining fields appears at the key level.
Select the Icon Generate for generating the condition table.
To save the condition table, select the button Local object.
2. Access Sequence: - Access sequence is a search strategy with the help of which the system gets the valid condition records. It contains the required condition tables in the required order.
Note: - If required an access sequence can be used or assigned to multiple
Condition types.
Note: - The order in which the condition table are placed in access sequence
is important generally it is most specific to most generic
Defining Access Sequence: -
SPRO
Sales and distribution
Basic functions
Pricing
Pricing control
Define access sequences
Maintain access sequences
Go to new entries and define the access sequence.
Select the defined access sequence and go to accesses.
Go to new entries and place the condition tables in the required order
While placing the condition tables check the field “exclusive”. By doing so if the system finds a valid condition record in the first condition table it will not go to the next condition table
Select the condition table and go to fields the system gives the warning message “the field assignment has not yet been made” say enter till we get the fields.
Repeat the same step for all the condition tables and save it.
Note: - After defining the access sequence assign it to the corresponding condition type.
3. Condition Types: -
Defining condition types: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define condition types.
Maintain condition types.
Functionality of a condition type: -
Access Sequence: - In this field specify the corresponding access sequence for the condition type.
Condition class: - It is the preliminary structuring of condition types.
Ex: - Surcharges or discounts and price
Plus/Minus: - If we specify negative here a condition type becomes discount and if we specify positive it becomes surcharge.
Calculation type: - Determines how the system calculates price discounts and surcharges in a condition type.
For Ex: - the system can calculate a price as a fixed amount or as a percentage based on the quantity, weight, or volume.
Condition Category: - It’s a classification of conditions according to pre-defined categories.
Rounding Rule: - The rule that determines how the system rounds of condition values during pricing.
Manual Entries: - Indicator which controls the priority with in a condition type between a condition enter manually and a condition automatically determined by the system.
Amount / Percent: - If we check this field the amount / percentage of a condition type can be change during the document processing.
Quantity Relation: - Specifies whether the conversion factors for the units of measure in the condition type can be change during document processing.
Delete: - If we check this field the condition type can be deleted during the sales document processing.
Value: - If we check this field the condition value can be changed during the document processing.
Calculation type: - If we check this field the calculation type can be change during the document processing.
Item condition: - If we check this field for a condition types it becomes item condition, which has to be enter at the item level only.
Header condition: - If we check this field for a condition type it becomes header condition, which has to be entered at the header level only
Ex: - RB00 (Discount).
Note: - After entering the header condition type click on the button activate.
Note: - The condition amount of the header condition is copied as it is to all the line items in the document
Group condition: - If we check a header condition as a group condition the condition amount is distributed proportionately among all the line items in the sales document.
Valid from & valid to: - specifies the beginning and ending of the validity date that the system automatically proposes when we create condition records for the condition types.
Scale Basis: - Determines how the system interprets a pricing scale in a condition, for Ex: - the scale can be based on quantity weight and volume.
Check value: - Indicates whether the sale rates must be entered in ascending or descending order.
Note: - Header condition won’t be having access sequence.
4. Pricing Procedure: - Pricing procedure contains all the required condition types in the required order.
Defining Pricing Procedure: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define and assign pricing procedures.
Maintain pricing procedures
Go to new entries and define the pricing procedure.
Select the defined pricing procedure and go

Similar Messages

  • Error while creating the Organization structure.

    Hi,
    I am trying to create an Organization structure in SRM 5 sytem, I have created a Root for the structure and when i try to click on the Attribute Inheritance or the Check tab below i am getting an error "Start program BBP_LOCATIONS_GET_ALL first (see note 563180 and long text)" but i have replicated one plant from the R/3 system using BBP_LOCATIONS_GET_SELECTED and the material groups and all the other relevant datas from R/3. I can see in the table BBP_LOCMAP the plant been associated with the relevant company code. I am now struck in creating the organization structure. I am not sure where i am going wrong while creating the Org model.Please give me your valuable inputs to overcome this error.
    Regards
    GGL

    Go to transaction SM30, table T77S0
    Add an X to the following entry:
    Group = EBP          
    Sem abbr. = LMIGR        
    Val. Abbr. = X       
    Description = Locations Successfully Migrated
    This tell the system that the locations have been replicated and the error indicating location get all needs be executed will go away.
    thanks,
    justin
    Edited by: Justin Farley on Feb 25, 2009 7:16 PM

  • Problems assigning BP to a position in the organizational structure

    I tried to assign a bp to a position in the organizational structure,
    but I receive this message "Object cannot be assigned to object CliC
    Agent in the period 21.12.2006 - 31.12.9999".
    Also, I notice that in the screen, the checkbox where i can select for
    the business partner is missing.
    However, I can assign a user to the org structure.
    Before upgrading, it was working. This is the support packages that it was in.
    SAP_ABAP: Level 9
    SAP_BASIS: Level 9
    PI_BASIS: Level 9
    SAP_AP: Level 6
    BBPCRM: Level 6
    After the upgrade to the following,
    SAP_ABAP: Level 10
    SAP_BASIS: Level 10
    PI_BASIS: Level 10
    SAP_AP: Level 7
    BBPCRM: Level 7
    The assigning of business partner to a position no longer works.

    Hi,
    we're facing exactly the same problem, it was all going well until we went on production.... we applied note 997009 which results in a different error... did you manage to find a solution yet ?
    Regards,
    Jacob.

  • FI organizational structure in ECC 6.0

    Dear all,
    I would like to know what is the suggested organizational structure in FI in ECC 6.0. For example, whether it supports multiple company code or single company code. If a company code is situated out of India, how the taxation and all will be consolidated etc. etc.
    Kindly can any one provide me documents on the above subject related to Finance Module.
    It will be very helpful If anyone sends the required documents
    Email id : [email protected]
    Thanking you in advance
    Vijaya

    Hi Vijayalaxmi,
    SAP 6.0 ECC is supports what data you doing in previous versions like 4.7 or 5.0 etc
    you can set company in india or out of india and  taxation also same what you doing in previous versions
    differece is ECC 6.0 is some extra functions is added on advance purpose
    Organizational Units and Basic Settings
    Definition
    Elements of the SAP System logical structure, important for Financial Accounting.
    Organizational units are used to structure business functions and for reporting. The organizational units of Financial Accounting are used for external reporting purposes, that is, they fulfil requirements that your business is subject to from external parties, for example, legal regulations. The financial statements for example, are created based on the organizational units of Financial Accounting.
    Basic settings in Financial Accounting are Customizing settings that you have to make in order to be able to carry out processes in Financial Accounting.
    Use
    You create your company-specific organizational structure in the SAP System by defining the organizational units and making the basic settings. Defining organizational units for Financial Accounting is obligatory, that is, you have to define these units in order to be able to implement the Financial Accounting component.
    Organizational unit
    Definition
    Client
    Obligatory
    Company
    Optional
    Company code
    Obligatory
    Business area
    Optional
    Basic setting
    Chart of accounts
    Obligatory
    Fiscal year
    Obligatory
    Currencies
    Obligatory
    Integration
    In the SAP System, you define the relevant organizational units for each component that you are implementing. For example, for Sales and Distribution, you define sales organizations, distribution channels, and divisions (product groups). Similarly, for Purchasing, you define purchasing organizations, evaluation levels, plants, and storage locations. The organizational units are independent of one another at this stage.
    Components and Organizational Units
    Component
    Organizational unit
    Sales and Distribution
    Sales organization, ...
    Logistics
    Purchasing organization, ...
    Financial Accounting
    Company code, ...
    Controlling
    Controlling area, ...
    Human Resources
    Employee groups, ...
    To transfer data between the individual components, you have to assign the organizational units to each other. You only need to make these assignments once in the system. Whenever you enter data subsequently, it is automatically transferred.
    For example, invoices that are posted in SD are transferred to FI.
    Below link will give total structure of organisational structure
    http://help.sap.com/saphelp_470/helpdata/en/e5/0779ee4acd11d182b90000e829fbfe/frameset.htm
    Hope this infirmation will helps you
    Prem

  • ALE: e-recruiting organizational structure transfer

    Hi friends,
    I want to transfer the organization structure or the organization plan with O,S,C object types from one SAP system to another SAP system.
    I have done the ALE configuration and using PAFL transaction to do the same.
    I would like to know that model view i should use for the distribution also i would want to know the screen parameters in PAFL transaction.
    I am doing the same for E-recruiting separate instance.
    Regards,
    Divya
    Points would be given

    Hello,
    We are still having a problem with failing iDocs everytime we pass over IT0105 Sty 1 records from our SAP system to E-Recruiting.
    Would anyone happen to know where I should start looking to troubleshoot this error message?
    "Password is not long enough (minimum length: 6 characters)"
    Currently both systems require that your password be at least 6 characters long, which makes this message even more perplexing.
    Having a better understanding of how RBDAPP01 processes inbound IDOCS in status 64 would help.  We are using message type HRMD_ABA.  Our data filter looks like....
    Infotype: 1000
    Object Type: C, O, S
    Infotype: 1001
    Object Type: C, O, S
    Subtypes: A002, A007, A008, A012, B002, B007, B008, B012
    Infotype: 1001
    Object Type: O, S
    Subtypes: A003, B003
    Infotypes: 0000, 0001, 0002
    Object Type: P
    Infotype: 0006
    Object Type: P
    Subtype: 1
    Infotype: 0105
    Object Type: P
    Subtypes: 0001, 0010   
    So the question is how is IT0105 Sty 1 being processed when RBDAPP01 runs?
    Thank you for your help!
    Ryan
    Edited by: Ryan Hubbell on Mar 31, 2009 7:00 PM
    Edited by: Ryan Hubbell on Mar 31, 2009 7:47 PM

  • Calculation of minority interest in matrix organization structure

    Hello-
    We are currently implementing sem-bcs and have a matrix organization structure in place. We use company code and profit center as consolidation units. Company code being the currency carrying unit.
    We are facing an issue in minority calculation-
    Let us take the following example -
    Investee A - books equity in pc A
    Holding entity B books investments in pc B
    The above information were entered in AFD and was also pulled in BCS as RFD..
    The first consolidation happens as per our expectations.
    For subsequent consolidation, the retained earnings account (additions movement) could have multiple profit centers. The system calculates minority interest correctly for combination of retained earnings addition @ PC A. However for all other combinations (I.e retained earnings for PC other than A), the system treats the entire amount as minority interest (even though that's not the case)..
    Kindly advise.
    Thanks!

    Hi,
    Thanks for your reply...
    The PC hierarchy is already in place..I maintained Additional Financial Data for the other combinations (of Cons Unit and PC) with 100% share and zero value. The system considered that and calculated minority interest correctly.
    I wish to know if the above approach is ok..
    Thanks

  • Organization structure in extended classic scenario

    Hi All
    I  am trying to configure extended classic scenario on SAP SRM 7.0.  I have made the following settings for the same:
    1. In SPRO->SRM Server-> Technical Basic Settings -> Define backend system from product category, I have specified target system as SRM system and not ECD system
    2. In SPRO->SRM Server->Cross Application Basic Settings-> Activate Extended Classic Scenario, I have selected all the options including "Back end purchasing group responsible"
    I have a few doubts.
    1. In organization Structure (PPOMA_BBP) Comapny code is corresponding to company code in back end but do I have to create local purchasing organization and local purchasing group i.e. in Functions-> Corresponds  I'll have to leave blank. plz suggest
    2. Also is IPC configuration mandatory for extended classic scenario
    Plz give your suggestion on above mentioned issue
    Regards
    Pawan Keshwani
    Edited by: pawankeshwani on Mar 18, 2011 8:33 AM

    Hi Pawan,
    No you should mention Purch Org & Purch Grp also wrt your backend (ECC).
    IPC need not be configured separately from SRM 5.0 onwards. To ascertain if IPC is working fine just run the report : RSVMCRT_HEALTH_CHECK. You should see 4 success messages. Else get in touch with Basis to enable Virtual Machine Container (VMC)
    Regards,
    Nikhil

  • Organization structure in CRM 7.0 from ECC and HR

    Hi,
    We are trying to download Org structures from ECC and HR. (CRM 7.0, HR & R/3 ECC 6.0)
    From HR
    The ALE distribution is set across the systems CRM and HR and I did the PFAL run as per the best practices BB C05. There are about 100,000 Idocs inbound to CRM system and out of which about 15K are in 51 status and the rest are in 53 status.
    Observations:
    The Organization structure from HR is not totally mapped in CRM but only a part of it is displayed in PPOMA_CRM.
    The remaining Org units are found in 'non-related objects' selection.
    All the Idocs in failure are in error "Error in subroutine read_namtb for structure  of infotype  ". When I go to the long text
    Message no. 5-109
    Diagnosis
    An error has occurred in subroutine read_namtb for structure  of infotype .
    Procedure
    Check the entry for infotype  in table T777D (structure, IDoc segment, expanded structure) and the corresponding structures.
    I am not sure which infotype needs to be checked in T777D.
    From ECC
    The CRM - ECC connectivity is set. Downloaded all the required customizing objects successfully. Switched the org model to "enhanced backend integration version " and then followed on to SPRO->CRM->Master Data->Organizational Management->Data transfer->Copy SAP ECC structure and selected all the available R/3 Organization assignments available and then selected the "generate selected lines".
    Observations:
    All the generated org units are in GREEN in SPRO but there are no assignments found in PPOMA_CRM not even in the unrelated objects
    Checked tables HRP1000 and HRP1001 from the CRM Sales org unit IDs (ex: O 5000012) created here and they are not found but the generation is in GREEN.
    I will appreciate any assistance I get here.
    << Moderator message - Everyone's problem is important >>
    Regards,
    DT
    Edited by: Rob Burbank on Oct 20, 2010 4:25 PM

    Hello DT,
    Could you please let me know the process how the problem is solved..
    even we are having the same issue like, we have downloaded the Org Model form HR to CRM system, till here it was fine.
    when we are trying to download the ECC sales structure(CRMC_R3_ORG_GENERATE) to CRM system, i have selected all the items and triggered the Gerenerated Selectd Lines, but after all the items are generating in a error with RED.
    Could you please share you knowledge, so that it will help me in figuring out the issue.
    Thanks in Advance DT. Hope you reply back.
    Regards,
    Ven

  • Regarding workflow  organization structure

    hi Gurs.
    How to create Organization Structure, Create Workflow with Multiple Approval based on Organization Structure.
    this is my requirement i dont no how to create  organization  structure in which tcode  i have to build and what all steps.
    pl help me.
    Regards
    vijay

    Hi,
    Your thread has had no response since it's creation over
    2 weeks ago, therefore, I recommend that you either:
    - Rephrase the question.
    - Provide additional Information to prompt a response.
    - Close the thread if the answer is already known.
    Thank you for your compliance in this regard.
    Kind regards,
    Siobhan

  • Organizational structure graphical view

    Hi Friends,
    we have problem with the organizational structure graphical view in OM. the system can not read the texts fonts, we don't use english characters. what should we do?
    Thanks

    Hi there!
    Hope you both don't mind but I am piggy backing on your OM discussion. You both sound like have good experience in working with Turkey. I am trying to find a standard infotype to store a Turkish Identification no, SSN, and Local ID card numbers. I am leaning towards IT0185 but first want to check around to see if there are Turkish infotypes specifically for these types of documentation. Your feedback is greatly appreciated.
    Thank you in advance.
    Dina

  • Organizational Structure Search Help in Webdynpro ABAP

    Hi,
    I need an organizational structure search help in webdynpro abap.
    It should list the organizational structure in tree view like RH_OBJID_REQUEST lists.
    I tried to use RH_OBJID_REQUEST function in webdynpro but I got " A RAISE statement in the program
    "CL_GUI_CUSTOM_CONTAINER=======CP" raised theexception condition "CNTL_ERROR" short dump.
    Is there such a function for webdynpro abap and  how can I achive this with select options?
    Thanks in advance..
    MERAL

    Great article.  I also had this probelm a year ago. My problems questions are:
    Is it possible to select more then one entry in the tree?
    What about selecting all childrens with one click?
    In my solution I inserted this tree, into a table and the table had a checkbox, row, so the user can check the required org units, (more then one) and there was a separate button, for "select all children"

  • Help in defining organization structure with reference to new gl

    Hi Experts,
    I need some help in defining organization structure with reference to new GL. I have three legal entities spread across 17 locations. In each location there may be three legal company entities in operation. And in each company code there are 5 to 6 several product lines. I have defined 3 legal entities as 3 company codes, but my concern is how do i define these 17 locations as and how do i define these product lines. We do location wise reporting meaning if i take one location i draw P&L for all the 15 product lines of the combined 3 company codes. Like wise for we do individual location wise reporting. As ususal we do budgeting location wise for departments for each individual company code.
    I thought of using business area as locations, but i heard SAP doesnt support anymore on business due to new gl concept and moreover business area doesnt populate in all transactions. Can we use new gl concept like segments and so, i am sorry i am very new to New gl. Can the location wise combined reporting be done in consolidation or it can achieved in new gl
    Can somebody share their expertise on how to achieve this either my new gl or traditional gl.
    Thanks in advance
    Best Regards,
    gj

    Hi Experts,
    Looking forward some help on this issue.
    Best Regards,
    gj

  • Sales organization structure changes in COPA

    Hi All,
    My client like to change Sales organization structure like Distribution channel,division,sales office,sales group etc. and profit centers in sales orders.
    from 01/01/2011 we like to post all open sales order's settlments to new sales organization,distribution channel,division,sales office,sales group and profit centers in COPA.
    What is the best way to achieve this?
    Any help is appreciated.....
    Thanks,
    Anusha

    Hi,
    I think COPA realignment should work for you.
    If you can establish the exact relation ship between old Sales org structure  to new Sales org structure, you can design your realignment in such a way that the new sales data will reflect the new structure.
    For this,
    1.You need to select the sales documents for which you want to change the sales org.
    2. If you want to derive them again, you can do so
    3. If you want the sales org structure elements to be replaced by new ones, you can do so.
    Following a realignment, only the new assignment is known in the information system and in planning. The characteristic values valid at the time the original posting was made can only be analyzed in line item reports. Because the existing profitability segments are changed to adhere to the new assignment, all objects assigned to those profitability segments - such as sales orders or projects - and all existing SAP documents - such as billing documents or FI documents - reflect the new assignment as well.
    For more details, check the following link. [http://help.sap.com/saphelp_erp60_sp/helpdata/en/7a/4c48c64a0111d1894c0000e829fbbd/frameset.htm]
    Njloy
    Siva

  • Set up the Organizational structure for MSS scenario

    Hi!
    I would like to set up the Organizational structure for MSS scenario within SAP Portal.
    Question:
    1) How to set up/map real user from SU01 to Manager? (tcode, report)
    2) How to mark them as 'Chief' (tcode, report)
    3) How to be sure that PA & OM are configured correctly and the integration switch is on?
    Which SAP course or SDN blog describes this?
    Thank you very much!
    regards
    Jürgen

    How to be sure that PA & OM are configured correctly and the integration switch is on?
    Check It000 and IT0001 here u will get objects from OM and PA  (position ID , Job Key, organisational Key)
    and integration switch
    check plogi orga , plogi plogi , plogi perli  in V_T77s0
    Edited by: Sikindar on Feb 10, 2009 6:53 PM

  • Monitor changes in the Organizational Structure

    Hello All,
    What is the best way to monitor the changes made in the Organizational Structure.
    We are observing changes in the Org Structure in our system. We want to find out the User who made the change.
    Thanks

    Hi,
    I'm afraid the only way is tcode: SCU3 (Table History), but it's not user friedly.
    Most important info is stored in tables:
    HRP1000 ( object info ),
    HRP1001 ( relations ),
    HRP1222 ( general attributes - id's  ),
    HRT1222 ( general attributes - data ).
    Regards, Robert

  • How to Link Organizational Structure to a report program

    Hi All,
              Can anyone pls help me out with my requirement. How can we link a organizational structure created in transaction PPOMW to a report program. Basically i want to send the report output as an XLS attachment to an external email id. For that i need to link Organizational Structure to the report program.
          There are many ways of doing it but i want it to be done by linking Organization structure to the report program. Pls help me as soon as possible as its a bit urgent for me.

    Hi,
    Please follow the below function modules and the paramters for reading archived data:
    CALL FUNCTION 'ARCHIVE_OPEN_FOR_READ'
      EXPORTING
        OBJECT                   = archiving object name
    IMPORTING
       ARCHIVE_HANDLE           = archive read handle
    Then in the loop(DO-ENDDO), use this FM:
    DO.
      CALL FUNCTION 'ARCHIVE_GET_NEXT_OBJECT'
           EXPORTING
                archive_handle          = archive read handle
    Then records from the data objects using this FM:
      CALL FUNCTION 'ARCHIVE_GET_TABLE'
           EXPORTING
                archive_handle        = archive read handle
                record_structure      = 'TABLENAME'
                all_records_of_object = 'X'
                automatic_conversion  = 'X'
           TABLES
                table                 = internal table for which you want to retrieve records.
    ENDDO.
    Then close the archive file using this FM:
    CALL FUNCTION 'ARCHIVE_CLOSE_FILE'
         EXPORTING
              archive_handle = archive read handle
    This will help u in reading archived data from archive file.
    may give some idea also on how to code the read prgram.
    Thanks,
    Shamim

Maybe you are looking for

  • Can anyone help with isolating the cause of an InDesign CS5 crash?  It's intermittent...

    Hi All, I've got a client that's running into an intermittent crashing problem with InDesign.  Ordinarily "intermittent" points to hardware, but we wanted to rule out bad software first, especially as InDesign is the ONLY application that's crashing

  • Problem with images disappearing from project

    I have inserted a number of images into my Robohelp 9 project topics using the Insert >> Image function.  Typically the images were stored on my hard drive on my pc, but some I pulled from a shared network drive that were prepared by other people.  T

  • New fonts not working in photoshop...

    I have installed new fonts on my mac but they will not work in Photoshop.. can somoene help me? I don't know if I have done something wrong or need to take another step.. I am running CS4 and OS 10.6.4. The message I get when I try to use a font I re

  • Unable to download Oracle 11g tools for VS2008

    I checked the checkbox to agree to the terms, clicked on the button below it and got the page with the 200MB zip file (size is an estimate because I can't see the page right now). I click on that zip file to download and the page just gives me errors

  • How to use a check box in smart forms????

    Hi All, Pls let me know how to use check boxes in smartforms.....?? there are check boxe available which are crossed (i.e,, selected checkboxes) in the smartforms.. But i need a checkbox which are not selected.( i.e.., which are not crossed). Its rea