cancel
Showing results for 
Search instead for 
Did you mean: 

FLOW

former_member2382
Active Participant
0 Kudos

Hi All,

Could anyone tell me the Flow of SD with its Transactions.

Regards,

Parvez.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Parveez,

Sales document flow is as below.

1)VA11- It starts with an enquiry where i am enquire regarding the products a company s based on pre sales activities the company carries out like say mailers on any campaign that i have carried out that leads to an enquiry.

2) Va21- Next A quatation is placed ,Customer may have enquired about 30 products but you give quotation to only 20 items subject to their availability with you. quotation is a binding document about conformed price & delivery schedule.

3) VA01- When a quatation is placed the next step is the sales order. The same is a purchase order for the person who places the order and a sales order for the person who sells the products.

4) VL01N- Once the order is placed i create a delivery where i need to deliver the goods to the customer, here I need to see that pick qty and delivery qty is the same pick qty is that qty where i pick the goods from my warehouse.

5) Once i do the delivery the next step is Post goods Issue, which means my stock gets reduced and all my previous documents get updated. A post goods issue can be done before the goods leave to the customer or when the goods are in transit. But the same should be done.

6) VF01- The next step would be billing where after doing the post goods issue i raise and invoice to the customer which is called billing.

7) If the customer finds that there are some goods which are damaged he would return the goods back which are called returns and i would then raise a credit memo which would give him credit for the damaged goods.

I hope this is helpful to you. Please do reward with points if this helps you.

Answers (7)

Answers (7)

Former Member
0 Kudos
  • How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Former Member
0 Kudos

Dear Md Parvez,

If your query is answered, please reward suitable points & close the Blog.

Regards.

Rajesh Banka

Former Member
0 Kudos

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.

Regards,

Rajesh Banka

Reward point if useful.

Former Member
0 Kudos

Sales & Operations Planning (SOP) is a flexible forecasting and planning tool with which sales, production, and other supply chain targets can be set on the basis of historical, existing, and estimated future data. Rough-cut planning can also be carried out to determine the amounts of the capacities and other resources required to meet these targets.

Use SOP to streamline and consolidate your company’s sales and production operations.

SOP is particularly suitable for long- and medium-term planning.

Integration

SOP constitutes the planning functionality of the LIS information systems.

You pass on SOP plans to Demand Management (PP-MP-DEM) in the form of independent requirements. In turn, this data is fed to Master Production Scheduling (PP-MP-MPS) and Material Requirements Planning (PP-MRP).

An interface with Profitability Analysis (CO-PA) allows you to use CO-PA data as the basis for sales planning in SOP.

You can also pass on the results of SOP to Profitability Analysis (CO-PA), Cost Center Accounting (CO-OM-CCA), and Activity-Based Costing (CO-OM-CCA).

For more information please visit the following link:

http://help.sap.com/saphelp_erp2005/helpdata/en/a5/632f3b43a211d189410000e829fbbd/frameset.htm

<b>Procurement Process consist of:</b>

Purchase Requisition - A purchase requisition is a request or instruction to Purchasing to procure a certain quantity of a material or a service so that it is available at a certain point in time.

Request For Quatation - A request for quotation (RFQ) is an invitation extended to a vendor by a purchasing organization to submit a quotation (bid) for the supply of materials or performance of services.

Purchase Order - Formal request or instruction from a purchasing organization to a vendor or a plant to supply or provide a certain quantity of goods or services at or by a certain point in time.

Outline Agreement with vendors

a. Outline Purchase Agreement - An outline purchase agreement is a longer-term agreement between a purchasing organization and a vendor regarding the supply of materials or the performance of services within a certain period according to predefined terms and conditions. (Outside SAP, such agreements may be referred to by a number of terms, including "blanket", "master", "framework" or "umbrella" agreements)

b. Contract - In the MM Purchasing component, a contract is a type of outline purchase agreement against which release orders (releases) can be issued for agreed materials or services as and when required during a certain overall time-frame. (In the literature and in practice, similar concepts may also be referred to by a number of other terms, such as "systems contract", "blanket order agreement", "blanket contract", and "period contract".)

c. Schedulilng Agreement - A form of outline purchase agreement under which materials are procured on predetermined dates within a certain time period.

Goods Receipt - If your company uses the MM Purchasing component, deliveries from vendors are most likely the result of purchase orders initiated by the purchasing department.

The purchase order is not only the document with which the purchasing department orders goods from the vendor; it is also an important planning and tracking tool for the following departments: Purchasing, Material Requirements Planning (MRP), Inventory Management, and Invoice Verification.

Quality Inspection - If an inspection at the time of goods receipt has been defined for the material, the system automatically creates an inspection lot when the goods receipt is posted. Quality Management uses this inspection lot to carry out the inspection.

Confirmation - Working with confirmations has the advantage that Materials Planning does not have to depend solely on the delivery dates and quantities set out in purchase orders or the delivery schedules of scheduling agreements.

Confirmations enable you to plan more exactly, since during the time-span between the order date and the desired delivery date you receive increasingly more reliable information from the vendor regarding the anticipated delivery.

Receipt of Vendor Invoice - Document from an invoicing party containing the payments to be made based on business transactions performed in Purchasing and Inventory Management. An incoming invoice can be an invoice or a credit memo.

Invoice Verification - Logistics Invoice Verification is a part of Materials Management (MM). It is situated at the end of the logistics supply chain that includes Purchasing, Inventory Management, and Invoice Verification. It is in Logistics Invoice Verification that incoming invoices are verified in terms of their content, prices and arithmetic. When the invoice is posted, the invoice data is saved in the system. The system updates the data saved in the invoice documents in Materials Management and Financial Accounting.

<b>Sales</b>

Inquiry - A customer’s request to a company that they provide a quotation or sales information without obligation. An inquiry can relate to materials or services, conditions and if necessary delivery dates. The sales area that accepts the inquiry becomes responsible for further processing.

Quotation - A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. This offer is legally binding for the company within a specified time period. A sales area can reply to a customer inquiry with a customer quotation or use it to refer to a business partner contact.

Sales Order - Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time.

The sales area that accepts the inquiry is responsible for completing the agreement.

Create Delivery:a. Picking - The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.

b. Packing - Packing is part of delivery- and shipment processing. When you process a delivery, you can select delivery items for packing and assign them to handling units (HUs).

c. Goods Issue - As soon as the goods leave the company, the shipping business activity is finished. This is illustrated using goods issue for outbound deliveries.

Billing - Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.

<u><b>Sales Order Management Transactions</b></u>

<u>SALES ORDER PROCESSING</u>

Creating Sales Order - <b>VA01</b>

Maintaining a Sales Order - <b>VA02</b>

Displaying a Sales Order - <b>VA03</b>

Releasing an Order or Delivery from Credit Hold: Non-Flooring - <b>VKM1</b>

Display List of RMAs by Customer - <b>VA05</b>

Confirm RMA Goods Receipt - <b>VL02</b>

Generate list of open return orders for deletion - <b>VA05</b>

Display Customer returns eligibility - <b>MCSI</b>

Removing a Billing Block (Approving Credit/Debit Requests) - <b>V.23</b>

<u>PRICING MASTER DATA</u>

Create Pricing - <b>VK11</b>

Creating a Sales Deal - <b>VB21</b>

Maintaining a Sales Deal - <b>VB22</b>

Displaying a Sales Deal - <b>VB23</b>

Maintaining Prices - <b>VK12</b>

Displaying Prices - <b>VK13</b>

<u>MATERIAL MASTER DATA</u>

Creating Material Substitution Master Data - <b>VB11</b>

Maintaining/Deleting Material Substitution Master Data - <b>VB12</b>

Displaying Material Substitution Master Data - <b>VB13</b>

Creating a Bundled Master - <b>MM01</b>

Creating a Sales BOM - <b>CS01</b>

Maintaining a Sales BOM - <b>CS02</b>

Displaying a Sales BOM - <b>CS03</b>

<u>CUSTOMER MASTER DATA</u>

Creating Partner Records - <b>XD01</b>

Maintaining Customer Master Data - <b>XD02</b>

Displaying Customer Master Data - <b>XD03</b>

Deactivating a Partner - <b>VD06</b>

<u>CUSTOMER CREDIT INFO</u>

Creating/Maintaining New Customer Credit Information - <b>FD32</b>

Displaying Customer Credit Information - <b>FD33</b>

Blocking or Unblocking a Customer - <b>VD05</b>

<u>SHIPPING</u>

Creating a Delivery - <b>VL01N</b>

Displaying a Delivery - <b>VL03N</b>

Changing a Delivery - <b>VL02N</b>

Shipment Inquiry / Display - <b>VT03</b>

Adjusting Transfer Order - Confirmation Quantity - <b>LT12</b>

Collectively Confirm Transfer Order - <b>LT25</b>

Batch Shipment Confirmation - <b>VL19</b>

PGI Reversal Cancellation - <b>VL09</b>

Creating Service Provider/Carrier Master Data - <b>XK01</b>

Maintaining Serive Provider/Carrier Master Data - <b>XK02</b>

Displaying Service Provider/Carrier Master Data - <b>XK03</b>

Maintaining Product Master/Serial # Profile/Unit of Measure/Shipping Unit - <b>MM02</b>

IDoc Inquiry - <b>WE02 / WE05</b>

<u>BILLING</u>

Invoicing a Customer Shipment - <b>VF01</b>

Reprinting an Invoice - <b>VF31</b>

Releasing a Sales Order for Billing - <b>V.23</b>

Creating an Invoice by Using the Billing Due List - <b>VF04</b>

Checking Open Billing Documents - <b>VF05</b>

Create Credit/Debit Memo - <b>FB01</b>

<u>A/R</u>

Controlling Total Debit/Credit bkgs - <b>F.03</b>

Generate FI Account balance - <b>F.08</b>

Generate Month-to-date Inv. register - <b>F.02</b>

Process payments - <b>FBZ1</b>

Rqst Individual Customer Corresp. - <b>FB12</b>

Generate Customer Correspondence - <b>F.61</b>

Enter Batch totals under Control ttl - <b>FB07</b>

Display G/L Acct. totals - <b>FBL3N</b>

Reverse Posted Amounts - <b>FB08</b>

Customer Refunds - <b>FBL6</b>

Customer Refund to other than Payer - <b>FB05</b>

Clearing Debit/Credit on Cust. acct. - <b>FB1D</b>

Customer Balance in Local Currency - <b>F.23</b>

G/L Account Balance Report - <b>F.08</b>

Create Invoice - legal entity adjust - <b>FB01</b>

Generate Cust. Acct. statements - <b>F.27</b>

Generate Dunning Letters - <b>F150</b>

Generate Billing Due List - <b>VF04</b>

Generate Blocked Billing Doc list - <b>VFX3</b>

Inq. via Credit Release Screen - <b>VKM1</b>

List orders by partner - <b>VA05</b>

Past Due invoices by customer - <b>FD11</b>

Check number info by G/L account - <b>FBL3N</b>

Display customer Line items - <b>FBL5N</b>

Regards,

Rajesh Banka

Reward points if helpful.

Former Member
0 Kudos

Document Flow in Sales

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.

IN->QT>OR>DELIVERY->BILLING

VA11>VA21 >VA01>VL01N->VF01

Former Member
0 Kudos

VA01 CREATE SALE ORDER

VL01N CREATE DELIVERY

VL02N PGI

VF01 BILLING

RAMKI

Former Member
0 Kudos

Document Flow in Sales

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(va11), the quotation(VA21), the sales order(va01), the delivery(VL01N),picking(VL02N), the invoice(VF01), 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.

sree s