Required SD configration steps

[Former Member]

HI all,

Recently i switched to SAP SD, Can any body please send me the documents for SAP SD configration steps ( Total full cycle), I need the documentation availbale with step by step.

Appriciate if any body help in this regards,

Thanks and Regards,

Muralikrishna Nandigama

[Former Member]

HI

SD Process Flow

The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customer’s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents – the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge – creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.

Transaction Codes:

Inquiry - VA11/VA12/VA13

Quotation - VA21/VA22/VA23

Sales Order - VA01/VA02/VA03

Delivery - VL01N/VL02N/VL03N

Billing/Invoicing - VF01/VF02/VF03

SD Tables

Customers KNA1 General Data

KNB1 Customer Master – Co. Code Data (payment method, reconciliation acct)

KNB4 Customer Payment History

KNB5 Customer Master – Dunning info

KNBK Customer Master Bank Data

KNKA Customer Master Credit Mgmt.

KNKK Customer Master Credit Control Area Data (credit limits)

KNVV Sales Area Data (terms, order probability)

KNVI Customer Master Tax Indicator

KNVP Partner Function key

KNVD Output type

KNVS Customer Master Ship Data

KLPA Customer/Vendor Link

Sales Documents VBAKUK VBAK + VBUK

VBUK Header Status and Administrative Data

VBAK Sales Document - Header Data

VBKD Sales Document - Business Data

VBUP Item Status

VBAP Sales Document - Item Data

VBPA Partners

VBFA Document Flow

VBEP Sales Document Schedule Line

VBBE Sales Requirements: Individual Records

SD Delivery Docume LIPS Delivery Document item data, includes referencing PO

LIKP Delivery Document Header data

Billing Document VBRK Billing Document Header

VBRP Billing Document Item

SD Shipping Unit VEKP Shipping Unit Item (Content)

VEPO Shipping Unit Header

MM Process flow:

The typical procurement cycle for a service or material consists of the following phases:

1. Determination of Requirements

Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.

2. Source Determination

The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.

3. Vendor Selection and Comparison of Quotations

The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.

4. Purchase Order Processing

The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.

5. Purchase Order Follow-Up

The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.

6. Goods Receiving and Inventory Management

Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.

7. Invoice Verification

The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.

Transaction Codes:

RFQ to Vendor - ME41

Raising Quotation - ME47

Comparison of Price - ME49

Creation of PO - ME21N

Goods Receipt - MIGO

Invoice (Bill PAssing) - MIRO

Goods Issue - MB1A

Physical Inventory - MI01( Create doc)

MI04 (Enter Count)

MI07 (Post)

MM Tables

EINA Purchasing Info Record- General Data

EINE Purchasing Info Record- Purchasing Organization Data

MAKT Material Descriptions

MARA General Material Data

MARC Plant Data for Material

MARD Storage Location Data for Material

MAST Material to BOM Link

MBEW Material Valuation

MKPF Header- Material Document

MSEG Document Segment- Material

MVER Material Consumption

MVKE Sales Data for materials

RKPF Document Header- Reservation

T023 Mat. groups

T024 Purchasing Groups

T156 Movement Type

T157H Help Texts for Movement Types

MOFF Lists what views have not been created

A501 Plant/Material

EBAN Purchase Requisition

EBKN Purchase Requisition Account Assignment

EKAB Release Documentation

EKBE History per Purchasing Document

EKET Scheduling Agreement Schedule Lines

EKKN Account Assignment in Purchasing Document

EKKO Purchasing Document Header

EKPO Purchasing Document Item

IKPF Header- Physical Inventory Document

ISEG Physical Inventory Document Items

LFA1 Vendor Master (General section)

LFB1 Vendor Master (Company Code)

NRIV Number range intervals

RESB Reservation/dependent requirements

T161T Texts for Purchasing Document Types

[Former Member]

hi

Consignment goods are goods which are stored at the customer location but which are owned by the company. The customer is not obliged to pay for these goods until they remove them from consignment stock. Otherwise, the customer can usually return consignment goods that are not required.

Consignment Fill-Up: Consignment fill-up replenishes the stock at the customer site. Since the goods remain the property of the company, this process is not relevant for pricing and consequently not for invoicing either.

Create a sales order using order type KB.

Enter the required data on the customer, the consignment goods and the delivering plant.

Enter all other relevant data and save the order.

Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.

The underlying goods movement type is a stock transfer. This ensures that when goods issue is posted, consignment special stock is created for the customer concerned. If special stock of this kind already exists in the delivering plant for this customer, the goods are posted to this special stock.

Order type: KB (document category C: sales order)

Std. Delivery type: LF

Item category: KBN (not relevant for pricing and billing)

Schedule line category: E1 (relevant for deliveries, uses availability check, 631 (GI consignment: lending) to post the stock into a special consignment category in the delivering plants stock for that particular customer and material)

Copy control rules for the sales doc, item category, and schedule line category.

Use trans MB58 or MMBE to check the stock.

In this case, Accounting document is required to be generated only for taxes, as the stock is still the ownership of the company. In the pricing procedure all condition type except for Taxes should be statistical.

Consignment Issue: The Consignment issue enables the customer to withdraw consignment goods from the special stock that are to be used or sold.

Create a sales order using order type KE.

Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.

Enter all other relevant data and save the order.

Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.

The goods are then reduced by the relevant quantity in the special stock assigned to the customer. This goods issue also reduces your total stock.

Invoice the delivery which issues the consignment goods.

Order type: KE (document category C: sales order)

Std. Delivery type: LF

Invoice: F2

Item category: KEN (relevant for pricing and deliver related billing, special stock indicator W, should determine cost too)

Schedule line category: C1 (relevant for deliveries, uses availability check, 633 (GI issue: customer consignment)

In this case, Accounting document is required to be generated only for most of the condition type, as it is being invoiced to end customer.

Consignment returns: proceed as follows: Consignment returns enable your customer to return goods to the consignment stock that has already been issued from it.

Create a sales order using sales order type CR.

Enter the required data on the customer and the consignment goods.

Enter all other relevant data and save the order.

Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The goods issue posting cancels the goods issue posting which was carried out when the consignment goods were issued. This posting records the return of the goods to the plant where goods receipt was carried out.

Create a credit memo for the consignment return you created in Step 1.

Order type: KR (document category H: returns)

Delivery type: LR

Credit for Returns Order type: RE (delivery or order related billing)

Item category: KRN (relevant for pricing and deliver related billing, special stock indicator W

Schedule line category: D0 (relevant for deliveries, no availability check, 634

In this case, Accounting document is required to be generated only for most of the condition type, as it is being returned by the customer & invoicing already done to customer..

Consignment Pick-Up: The company uses consignment pick-up to take back consignment goods that are faulty or excess materials that the customer does not need. This process is not relevant for billing since the goods remain the property of the company.

It may be beneficial to have a mandatory reference such as the consignment fill-up. In addition to it copy control rules can be used to further control it. In the copy control rules indicate the document flow. As the stock is coming back into the warehouse or plant, you can specify a returns shipping point to be automatically determined. No invoice is necessary, as the goods are not changing ownership.

Create a sales order using order type KA.

Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.

Enter all other relevant data and save the order.

Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The transaction is completed by the goods issue posting which initiates a transfer posting from the customer's special stock to your plant stock.

Order type: KA (document category C: sales order)

Delivery type: LR

No invoice

Item category: KAN

Schedule line category: F1 (relevant for deliveries, availability check against the stock on the customer's consignment, 632 (Consignment pickup)

In this case, Accounting document is required to be generated only for taxes, as the stock is still the ownership of the company. In the pricing procedure all condition type except for Taxes should be statistical, as the stock is being returned from consignment site to plant.

[Former Member]

hi

1. Maintaining Sales Organization

Sales Organization is an organizational unit responsible for the sale of certain products or services.

IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization

2. Assigning Sales Organization to Company Code

This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code

3. Maintaining Distribution Channel

Distribution Channel is the way, in which Products or Services reach Customers.

IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel

4. Assigning Distribution Channel to Sales Organization

This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization

5. Maintaining Division

Division is a way of grouping materials, products, or services.

IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division

6. Assigning Division to Sales Organization

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization

7. Setting up Sales Area

All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.

IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area

8. Assigning Sales Organization- Distribution Channel- Plant

Plant is created ny MM Consultant.

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant

9. Define Shipping Points

Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.

IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point

10 Assigning Shipping Point to Plant

This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.

IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant

Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.

11. Defining Common Distribution Channels for Master Data

Use

The purpose of this activity is to define distribution channels which have common master data..

Procedure

Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels

Transaction Code: VOR1

12. Defining Common Divisions for Master Data

Use

The purpose of this activity is to define distribution channels which have common master data..

Procedure

Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division

Transaction Code: VOR2

Pricing Procedure

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG -> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure -> Maintain Pricing Procedure.

b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure -> Determine Pricing Procedure.

5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

Normal Sales Order Cycle:-

Step 1: Sales Document Type

IMG > Sales and Distribution > Sales > Sales Documents >

Sales Document Header:

1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.

2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.

3. Assign Sales Area To Sales Document Types:

A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.

B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.

Sales Document Item:

1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.

2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category

Schedule Line:

1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.

2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.

Step 2:

IMG > Logistic Execution > Shipping > Deliveries >

1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.

3. Define Number Ranges for Deliveries: Ensure to maintain number range.

Step 3:

IMG > Sales and Distribution > Billing >

1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Number Range For Billing Documents: Ensure to maintain number range.

3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.

The configuration differs from scenario to scenario & requirement of the client.

MM01 - Create material

MM02 - Change material

MM03 - Display material

Views in material master:

1) Basic data 1

2) Basic data 2

3) Classification

4) Sales: Sales org data 1

5) Sales: Sales org data 2

6) Sales: General/Plant data

7) Foreign trade: Export data

😎 Sales text

9) Purchasing

10) Foreign trade: Import data

11) Purchase order text

12) MRP 1

13) MRP 2

14) MRP 3

15) MRP 4

16) Forecasting

17) Work scheduling

18) Production resources/Tools

19) General plant data/Storage 1

20) General plant data/Storage 2

21) Quality management

22) Accounting 1

23) Accounting 2

24) Costing 1

25) Costing 2

26) Plant stock

27) Storage location stock

Select the organization levels for which you want the data to be created/changed/displayed in the selected views----

-

---

Basic Data 1

General Data:

Base unit of measure = Unit of measure in which stocks of the material are managed.

You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.

Ex: piece(s), gram, second, pound

Material group = Key that you use to group together several materials or services with the same attributes

Ex: metal processing, steel, electronics, mechanics, casing, monitor, hard disks

Old material number = Number under which you have managed the material so far or still manage it, for example, in another system or card index

Division = A way of grouping materials, products or services. The systems uses divisions to determine the sales areas and the business areas for a material, product or service

Material Authorization Group:

Authorization group = The authorization group enables you to protect access to certain objects

Dimensions:

Gross weight, Net weight, Volume, Weight unit, Volume unit

Basic Data 2

Other Data:

Basic material = Basic constituent of the material

Standard desc = Description of the material in accordance with the appropriate industry standard (ANSI or ISO) Environment:

DG indicator profile = Alphanumeric key that uniquely identifies the dangerous goods profile Design Documents Assigned:

No link = To create links to drawings/documents in the document management system, select Extras à Document data Drawing:

Document (without document management system) = Number of the drawing that exists for the object

Sales: Sales Org 1

General Data:

Base unit of measure, Material group, Division, Delivering plant

Tax Data:

Country, Tax category, Tax classification

Quantity Stipulation:

Min order qty, Min dely qty, Delivery unit

Sales: Sales Org 2

Material statistics group (whether relevant for statistics or not), Account assignment group, item category group, product hierarchy.

Sales: general/plant

Availability check, transportation group (a grouping of materials that share the same route and transportation requirements), loading group (group sharing same loading reqts, combined with shipping conditions and delivering plant determines shipping point for the item), material group: shipping materials (groups together materials which require similar shipping materials.

MRP1

MRP type, reorder point (if the qty falls below this point, the system flags the material for requirements planning), Lot size (procedure to calculate the qty procured or produced).

MRP2

GR processing time (number of workdays required after receipt of the material for its inspection and placement into storage), planned delivery time (no of days needed to obtain the material or service if it is procured externally), safety stock (qty whose purpose is to satisfy unexpectedly high demand in the coverage period).

MRP3

Strategy group (the strategy group groups all the planning strategies that can be used for a particular material), availability check, total replenishment lead time (In an availability check where the system takes the replenishment lead time into consideration, it only checks whether there are sufficient incoming qts and stocks available to cover the reqts within the replenishment lead time)

Plant data/storage 1

Unit of issue (maintain if only different from the base unit of measure), temperature conditions, storage conditions, container requirements.

Accounting1

Currency, valuation class (depends on material type), price control (std or moving avg price)

[Former Member]

Dear Muralikrishna Nandigama,

Visit the followingl links:

https://wiki.sdn.sap.com/wiki/display/ERPLO/SD+Configuration

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/cin%2bconfiguration

Also, visit the following threads:

/message/3505991#3505991 [original link is broken]

SD Configuration:

Enterprise Structure:

1. Maintaining Sales Organization

Sales Organization is an organizational unit responsible for the sale of certain products or services.

IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization

2. Assigning Sales Organization to Company Code

This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code

3. Maintaining Distribution Channel

Distribution Channel is the way, in which Products or Services reach Customers.

IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel

4. Assigning Distribution Channel to Sales Organization

This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization

5. Maintaining Division

Division is a way of grouping materials, products, or services.

IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division

6. Assigning Division to Sales Organization

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization

7. Setting up Sales Area

All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.

IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area

8. Assigning Sales Organization- Distribution Channel- Plant

Plant is created ny MM Consultant.

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant

9. Define Shipping Points

Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.

IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point

10 Assigning Shipping Point to Plant

This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.

IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant

Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.

11. Defining Common Distribution Channels for Master Data

Use

The purpose of this activity is to define distribution channels which have common master data..

Procedure

Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels

Transaction Code: VOR1

12. Defining Common Divisions for Master DataUse

The purpose of this activity is to define distribution channels which have common master data..

Procedure

Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division

Transaction Code: VOR2

Pricing Procedure

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

Normal Sales Order Cycle:-

Step 1: Sales Document Type

IMG > Sales and Distribution > Sales > Sales Documents >

Sales Document Header:

1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.

2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.

3. Assign Sales Area To Sales Document Types:

A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.

B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.

Sales Document Item:

1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.

2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category

Schedule Line:

1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.

2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.

Step 2:

IMG > Logistic Execution > Shipping > Deliveries >

1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.

3. Define Number Ranges for Deliveries: Ensure to maintain number range.

Step 3:

IMG > Sales and Distribution > Billing >

1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Number Range For Billing Documents: Ensure to maintain number range.

3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.

The configuration differs from scenario to scenario & requirement of the client.

Interesting &important link to learn much more about configuration & business process is as under:

Link: http://help.sap.com/

Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.

Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on.

Regards,

Naveen.

[Former Member]

Hi muralikrishna nandigama,

A small search on SDN SD forum will help you to answer your query.

I will suggest you to visit http://sap-img.com/sap-sd.htm. It will give you the overview of SAP SD module.

Moreover there is a separate section of FAQs with answers which will help you in great deal.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

P.S. you can send me a mail at my mail id rakeshsinghchauhan@gmail.com for any specific details