Pls ppt on SD overview

[Former Member]

Any one please send me ppt presentation on complete SD overview

at sthanugundla@yahoo.com.

[Former Member]

Hi Sent the mail

Reward if helps

[Former Member]

Hi,

check in the following site.

https://www.hostlogic.hu/caghelp/Navigation/B.htm

Regards,

nandha

[Former Member]

hi,

sent to your email id

reward points if the answer is helpful

REgards,

Murali

[Former Member]

Hi,

Visit <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm">All about Sales and Distribution</a> SAP help link.

Sales-related business transactions are recorded in the system as sales documents. These are grouped into four categories:

• Pre-sales documents: inquiries and quotations

• Sales orders

• Outline agreements, such as contracts and scheduling agreements

• Customer problems and complaints, leading to free-of-charge deliveries and credit memo requests

During sales order processing, the system carries out basic functions, such as:

• Monitoring sales transactions

• Checking for availability

• Transferring requirements to materials planning (MRP)

• Delivery scheduling

• Calculating pricing and taxes

• Checking credit limits

• Creating printed or electronically transmitted documents (confirmations and so on)

Depending on how your system is configured, these functions may be completely automated or may also require some manual processing. The data that results from these basic functions (for example, shipping dates, confirmed quantities, prices and discounts) is stored in the sales document where it can be displayed and, in some cases, changed manually during subsequent processing.

<b>Document Flow in Sales</b>

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. For more information about how to display the document flow for a particular sales document

<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/dd/55fa8c545a11d1a7020000e829fd11/content.htm">Sales Document Flow with Graphical Diagram</a> shows how the various types of sales documents are inter-related and how data subsequently flows into shipping and billing documents

Sales transactions occur within the organizational structure of sales and distribution. This means, for example, that all sales activities are allocated to a sales organization, a distribution channel and a division. Since sales activities within your organization are processed in different geographical locations, the system allows you to specify additional organizational structures that define sales offices, sales groups, and sales people.

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.