Solved: End User Activities

Former Member · ‎08-09-2007

Hi,

can onyone tell me Data flow in SD along with end user activities involved in SD.

Also where SAP SD is integrated with other SAP modules.

Please mail me @ nidhish.mathur@gmail.com

Regards

Former Member · ‎08-09-2007

hi

Mail sent..

Data Flow

 Master Data

 Sales Support

 Sales

 Shipping

 Billing

 Credit Management

 Foreign Trade / Customs

 Sales Information System

Master Data

 Business Partner / Customer

 Products

 Conditions

 Agreements / Contracts

 Terms of Payment

 Incoterms

 Routes

Sales Support

 Sales Promotions

 Sales Activities

 Potential Analysis

Sales

 Inquiry

 Quotation

 Order / Contract / Backorder

 Product Proposals

Shipping and Transportation

 Outbound Delivery

 Picking

 Packing

 Loading

 Shipment

 Post Goods Issue

 Billing

Billing

 Billing

Credit Management

Foreign Trade / Customs

Sales Information System

Activities Involved by the SAP – SD End User

 Inquiry Processing

 Quotation Processing

 Contract Processing

 Sales Order Processing

 Scheduling Agreement Processing

 Returns Processing

 Rebate Processing

 Sales Deal and Promotion Processing

 Display Customer and Material Information

 Billing Processing (online)

 Billing Processing (In The Background)

 Invoice List Processing

 Maintain Customer and Material Information

 Display Pricing

 Maintain Pricing

 Release Blocked Documents for Billing

 Release Sales Orders for Delivery

 Display Sales Information

 Display Billing Documents

 Sales Analysis

 Credit Management in Sales and Distribution Documents

 Backorder Processing

 Sales Support

 Output Processing

Inquiry Processing

 Create/change/display inquiries

 Generate lists for inquiries and incomplete inquiries

 Select sales documents according to object status

Quotation Processing

 Create/change/display quotations

 Generate lists for quotations and incomplete quotations

 Select sales documents according to object status

Contract Processing

 Create/change/display contracts

 Generate and process list of contracts

 Generate and process list of incomplete contracts

 Select sales documents according to object status

Sales Order Processing

 Create/change/display sales orders

 Generate and process list of sales orders

 Generate and process list of incomplete sales orders

 Select and process sales documents according to object status

 Select and process sales documents in a period of time

 Select and process duplicate sales documents in a period of time

Scheduling Agreement Processing

 Scheduling agreement processing

 Select and process incomplete scheduling agreements

 Select sales documents according to object status

Returns Processing

 Create/change/display sales orders

 Create/change outbound delivery

Rebate Processing

Rebate processing:

 Maintain rebate agreements

 Extend rebate agreement

 Settlement of rebate agreements

 Generate list of rebate agreements

Billing document:

 Display billing document

 Compare the rebate basis from billing documents and statistics

 Update billing documents referring to rebate conditions

Sales Deal and Promotion Processing

 Create/change/display sales deals

 Generate list of sales deals

 Create/change/display promotions

 Generate list of promotions

Display Customer and Material Information

 Display customer (Sales)

 Display material

 Display material listing/exclusion

 Select customer material info record according to customer

 Select customer material info record according to material

 Display customer hierarchy

 Display sales deals

 Display promotions

 Display rebate agreements

 Display cross selling materials

 Display assortment module for value contracts

Billing Processing (online)

 Create/change/display billing document

 Cancel billing document

 Retroactive billing

 Process billing due list

 Set billing date

 Display billing documents from the archive

 List of billing documents

 Rebook accounting indicator

 Release sales orders for billing

 Display sales and distribution documents blocked for billing

Billing Processing (In the Background)

 Display billing document

 Generate batch jobs for billing

 Generate log for billing document run

Invoice List Processing

There are two types of invoice lists in the Standard:

1. one for invoices and debit memos

2. one for credit memos

 Create/change/display invoice lists

 Process work list for invoice lists

 Generate invoice list

 Generate cancellation invoice list

 Display invoice list from the archive

Maintain Customer and Material Information

 Maintain material listing/exclusion

 Reference material listing/exclusion

 Maintain material substitution

 Reference material substitution

 Maintain material information

 Select customer material information according to material or customer

 Maintain material

 Maintain customer (Sales)

 Maintain customer hierarchy

 Maintain materials for cross selling

 Maintain value contracts

 Maintain Incoterms

Display Pricing

 Display condition records

 Display condition lists

 Display conditions using index

 Display free goods determination

Maintain Pricing

 Create/change/display condition

 Condition processing using index

 Create/change/display free good

 Create/change/display condition lists

 Process net price list

 Release expected customer price

Release Blocked Documents for Billing

 Release sales orders for billing

 Change billing document

 List of blocked billing documents

Release Sales Orders for Delivery

 Change sales order

 Block and unblock customer from sales view

 Generate lists for incomplete sales documents and for sales documents blocked for delivery

Display Sales Information

 Generate list for quotations, contracts, sales orders or scheduling agreements

 Generate list for incomplete quotations, contracts, sales orders or scheduling agreements

 Generate list of sales orders blocked for delivery

 Display sales activities, item proposals, material listing and material exclusion

 Sales support monitor

Display Billing Documents

 Display billing document

 Display list of billing documents

 Display blocked billing documents

Sales Analysis

 Contracts: Lists for overdue and completed contracts

 Quotations: Lists for overdue and completed quotations

 Backorder processing: Backlog list, selection list

 Generate list for: Inquiries, rebate agreements, scheduling agreements

 Information on the customer: Sales summary, list of top customer

 Material information: List of top materials

 Sales support monitor

 Flexible planning: Display/create/change

Credit Management in Sales and Distribution Documents

 Process credit authorization for sales and distribution documents

 List of released sales and distribution documents

 List of blocked sales and distribution documents

 Process credit authorization according to sales and distribution document

 Process credit authorization according to delivery

 List of incomplete sales and distribution documents

 Sales and distribution documents blocked for delivery

 Delivery monitor

 List of billing documents

Backorder Processing

 Display backlogged sales orders

 Process backorder processing using selection list according to sales documents

 Backorder processing: access using the material

 Execute rescheduling of sales documents

 Evaluate rescheduling of sales documents

Sales Support

 Create/change/display sales activities

 Executing mailing promotions

 Display and create interested parties and contact persons

 Display sales summary

 Sales support monitor

 Display competitive products

Output Processing

 Display/change/create output-condition records in Sales

Integration between SD and MM :-

1. When you create sales order in SD, all the details of the items are copied from Material master of MM.

2. MRP and availability check related data is also taken from MM although you control this data in SD also.

3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.

4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.

Integration between SD and FI :-

1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the background. eg. In case of standard sales order, you create an outbound goods delivery to the customer. Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.

2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI

3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM

Different areas where SD is Integrated

Sales Order –

•Availability Check - MM

•Credit Check - FI

•Costing - CO/ MM

•Tax Determination - FI

•Transfer of Requirements - PP/ MM

Delivery & Goods Issue –

•Availability Check - MM

•Credit Check - FI

•Reduces stock - MM

•Reduces Inventory $ - FI/ CO

•Requirement Eliminated - PP/ MM

Billing -

•Debit A/R - FI/ CO

•Credit Revenue - FI/ CO

•Updates G/ L - FI/ CO

(Tax, discounts, surcharges

•Milestone Billing - PS

Return Delivery & Credit Memo -

•Increases Inventory - MM

•Updates G/ L - FI

•Credit Memo - FI

•Adjustment to A/R - FI

•Reduces Revenue - FI

Reward if USeful

Thanx & Regards

Naren..

Former Member · ‎08-09-2007

End user activities during implementation is undergoing training on how to execute the Transaction & how to view reports. Core team member is responsible to collect the data required to be uploaded from the end user & also to get UAT - User Acceptance Test from selected group of end users.

Post Implementation, the end user acticities is to maintain amster data as & when required. Master data such as customer master, material master, condition records for pricing & so on.... End user are the persons who actually work on live system i.s production system & execute day to day activities.

The flow in SD has already been mentioned by other friends, but in summary the sales cycle depends on scenario's:

1. Normal Sales Cycle:

Inquiry --> Quotation --> Sales Order --> Delivery (Create Delivery, Picking, Packing & PGI) --> Billing Document

2. Export Sales Scenario:

Inquiry --> Quotation --> Sales Order --> Proforma Invoice --> Delivery (Create Delivery, Picking, Packing & PGI) --> Billing Document

3. STO - Stock Transfer Order:

Pruchase Order (By Receiving Plant) --> Delivery (Create Delivery, Picking, Packing & PGI) (by Delivering Plant) --> Proforma Invoice (by Delivering Plant) --> Goods Receipt (By Receiving Plant)

4. Third Party Sale with Shipping Notification:

Sales Order --> Purchase Order --> Statistical Goods Receipt --> Invoice Verfication --> Billing Document

& so on ..................................

Regards,

Rajesh Banka

Reward points if helpful

Former Member · ‎08-09-2007

Hi Nidhish,

Please find the total stuff Below Related to your Thread.

Sales Flow:

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.

Sales Order Management Transactions

SALES ORDER PROCESSING

Creating Sales Order - VA01

Maintaining a Sales Order - VA02

Displaying a Sales Order - VA03

Releasing an Order or Delivery from Credit Hold: Non-Flooring - VKM1

Display List of RMAs by Customer - VA05

Confirm RMA Goods Receipt - VL02

Generate list of open return orders for deletion - VA05

Display Customer returns eligibility - MCSI

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

PRICING MASTER DATA

Create Pricing - VK11

Creating a Sales Deal - VB21

Maintaining a Sales Deal - VB22

Displaying a Sales Deal - VB23

Maintaining Prices - VK12

Displaying Prices - VK13

MATERIAL MASTER DATA

Creating Material Substitution Master Data - VB11

Maintaining/Deleting Material Substitution Master Data - VB12

Displaying Material Substitution Master Data - VB13

Creating a Bundled Master - MM01

Creating a Sales BOM - CS01

Maintaining a Sales BOM - CS02

Displaying a Sales BOM - CS03

CUSTOMER MASTER DATA

Creating Partner Records - XD01

Maintaining Customer Master Data - XD02

Displaying Customer Master Data - XD03

Deactivating a Partner - VD06

CUSTOMER CREDIT INFO

Creating/Maintaining New Customer Credit Information - FD32

Displaying Customer Credit Information - FD33

Blocking or Unblocking a Customer - VD05

SHIPPING

Creating a Delivery - VL01N

Displaying a Delivery - VL03N

Changing a Delivery - VL02N

Shipment Inquiry / Display - VT03

Adjusting Transfer Order - Confirmation Quantity - LT12

Collectively Confirm Transfer Order - LT25

Batch Shipment Confirmation - VL19

PGI Reversal Cancellation - VL09

Creating Service Provider/Carrier Master Data - XK01

Maintaining Serive Provider/Carrier Master Data - XK02

Displaying Service Provider/Carrier Master Data - XK03

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

IDoc Inquiry - WE02 / WE05

BILLING

Invoicing a Customer Shipment - VF01

Reprinting an Invoice - VF31

Releasing a Sales Order for Billing - V.23

Creating an Invoice by Using the Billing Due List - VF04

Checking Open Billing Documents - VF05

Create Credit/Debit Memo - FB01

A/R

Controlling Total Debit/Credit bkgs - F.03

Generate FI Account balance - F.08

Generate Month-to-date Inv. register - F.02

Process payments - FBZ1

Rqst Individual Customer Corresp. - FB12

Generate Customer Correspondence - F.61

Enter Batch totals under Control ttl - FB07

Display G/L Acct. totals - FBL3N

Reverse Posted Amounts - FB08

Customer Refunds - FBL6

Customer Refund to other than Payer - FB05

Clearing Debit/Credit on Cust. acct. - FB1D

Customer Balance in Local Currency - F.23

G/L Account Balance Report - F.08

Create Invoice - legal entity adjust - FB01

Generate Cust. Acct. statements - F.27

Generate Dunning Letters - F150

Generate Billing Due List - VF04

Generate Blocked Billing Doc list - VFX3

Inq. via Credit Release Screen - VKM1

List orders by partner - VA05

Past Due invoices by customer - FD11

Check number info by G/L account - FBL3N

Display customer Line items - FBL5N

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.

he 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.

SD FLOW

SD Flow Cycle:

INQUIRY ( VA11)

|

QUOTATION (VA21)

|

PURCHASE ORDER (ME21)

|

ORDER CONFIRMATION (VA01)

|

PICKING LIST – (VL36)

|

PACKING LIST - (VL02, VL01)

|

SHIPPING – (VT01)

|

INVOICE – (VF21, VF01)

|

AR

INTERGRATION BETWEEN SD AND MM AND SD & FICO

The link between SD and MM: -

1. When you create sales order in SD, all the details of the items are copied from Material master of MM.

2. MRP and availability check related data is also taken from MM although you control this data in SD also.

3. While you create inbound/outbound delivery with reference to a sales order, the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.

4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.

There are many such links between SD and MM.

SD AND MM INTGRATON

1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped

directly to your customer).

1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.

2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc. *-- Shahee

The link between SD and MM :-

1. When you create sales order in SD, all the details of the items are copied from Material master of MM.

2. MRP and availability check related data is also taken from MM although you control this data in SD also.

3. While you create inbound/outbound delivery with reference to a sales order, the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.

4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.

There are many such links between SD and MM

In Pricing we would want to determine the cost of the product

thru VPRS Condition Type. This cost of the material is

picked from the Material Master. How this happens is, if

we would want to determine this cost VPRS in the Sales Order

for Profitability purpose then , all those Item categories

that can appear in a sales order must be activated for

Determine Cost Check box in customizing. That’s one of the SD

MM Integration.

Now the link between SD and FI: -

1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the background. E.g. In case of standard sales order, you create an outbound goods delivery to the customer.

Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.

2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI

3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM

SD Integration points with other modules

SD module is highly integrated with the other modules in SAP.

Sales Order –

Integration Points Module

•Availability Check - MM

•Credit Check - FI

•Costing - CO/ MM

•Tax Determination - FI

•Transfer of Requirements - PP/ MM

Delivery & Goods Issue –

Integration Points Module

•Availability Check - MM

•Credit Check - FI

•Reduces stock - MM

•Reduces Inventory $ - FI/ CO

•Requirement Eliminated - PP/ MM

Billing -

Integration Points Module

•Debit A/R - FI/ CO

•Credit Revenue - FI/ CO

•Updates G/ L - FI/ CO

(Tax, discounts, surcharges, etc.)

•Milestone Billing - PS

Return Delivery & Credit Memo -

Integration Points Module

•Increases Inventory - MM

•Updates G/ L - FI

•Credit Memo - FI

•Adjustment to A/R - FI

•Reduces Revenue - FI

SD Transaction Code Flow:

Inquiry / Document type IN

Tcode for creation VA11, VA12, VA13. Tables VBAK, VBAP

Quotation / QT

Tcode for creation VA21, VA22, VA23. Tables VBAK, VBAP

Purchase Order PO

Tcode for creation ME21, ME22, and ME23. Tables EKKO, EKPO.

Sales Order OR

Tcode for creation VA01, VA02, VA03. Tables VBAK, VBAP

Delivery LF

Tcode for creation VL01, VL02, and VL03. Tables LIKP, LIPS

Billing MN

Tcode for creation VF01, VF02, and VF03. Tables VBRK, VBRP

To create a sales order we need purchase order number and customer number. Before that, to create a purchase order we need to have material no, vendor no.

To create vendor tcode is

xk01 (create), xk02 (change), xk03 (display)

Tables are lfa1.

To create customer tcode is xd01, xd02, xd03.

Table is kna1.

A2.SD Module is integrated with various modules during transaction processing ...

Sales Order – Integration Points Module

•Availability Check MM •Credit Check FI •Costing CO/ MM •Tax Determination FI •Transfer of Requirements PP/ MM

Delivery & Goods Issue – Integration Points Module

•Availability Check MM •Credit Check FI •Reduces stock MM •Reduces Inventory $ FI/ CO •Requirement Eliminated PP/ MM

Billing - Integration Points Module

•Debit A/R FI/ CO •Credit Revenue FI/ CO •Updates G/ L FI/ CO (Tax, discounts, surcharges, etc.) •Milestone Billing PS

Return Delivery & Credit Memo - Integration Points Module

•Increases Inventory MM •Updates G/ L

FI •Credit Memo FI •Adjustment to A/R FI •Reduces Revenue FI

check following link also

http://sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm

If you work in SD area, then the most important process where you really need to know MM area is the third-party process. In this case from SD sales order automatically the purchase requisition will be created on MM side. From this purchase requisition on MM side you create the purchase order on MM side. This purchase order updates the sales order on SD side, if you create the confirmation of the purchase order. This process takes place for the pure third-party as well as for individual purchase order process. Later the invoice will be sent from MM to SD (transaction MIRO) and will update the status of the SD order. If you work with this process then you need really know MM transactions quite well, because it is the same SD and MM system.

Another area where you have SD of one system integrated with MM of another system is the EDI process. Here several remarks concerning EDI concept of SD:

EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronically documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.

If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every time send a change to the existing order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).

So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOICE.

Additional processes in SD, where EDI are used in communication with MM are:

1) sending (from MM side) and application (on SD side) of delivery schedules to the scheduling agreement: IDOC of type DELINS. In this case we have practically automatically communication between SD and MM scheduling agreements via IDOCs;

2) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV are sent from MM customer to SD customer. So, the output function module belongs to MM area and the inbound function module - to SD area.

FI-SD Integration: The integration is done in T-code VKOA

1. Sales Order Created

~~-No Entry~~-

2. PGI done (Goods issue)

Cost of Goods Sold Dr (Configured in OBYC GBB T-Key)

To Inventory Account

3. Billing document released to Accounting

Customer Account Dr.

To Sales Revenue Account (ERL T-key in Pricing procedure)

Note: The GL account is assigned to this ERL in VKOA

4. Payment Received

Bank Clearing A/c Dr

Customer A/c Cr.

Points to Know: Good to understand the pricing procedure and how the different transaction keys are used like ERL, ERS etc.

1. looking at MM and SD integration first, take the scenario of a 3rd party order process. This process uses a purchase order (which is sent to your vendor).Also invoice verification is used further along the process to check that the invoice you send to your customer is the same quantity as that which the vendor sends to you (but obviously shipped directly to your customer)

2.billing in an SD FUNCTION . but sap needs to know when processing a customer payment , to which G/L accounts the payment has to be processed. for example payment of the UK based on material would be placed in different G/L account to that of a non-uk based material

Further more, a uk based customer may have a different G/L account to that of an export customer this is configured in account determination.

The following are the role matrix for SD end users:

SD - Roles Matrix

Transaction Description : Transaction Code

Master Data - Customer

Customer Master - Create - Sales Area: XD01

Customer Master - Change - Sales Area: XD02

Customer Master - Display - Sales Area: XD03

Customer Master - Display Changes - Sales Area: VD04

Customer Master - Flag for Deletion - Sales Area: VD06

Customer List - Block: VD05

Customer Change Account Group: XD07

Master Data - Conditions (Pricing)

Conditions Master - Create: VK11

Conditions Master - Change: VK12

Conditions Master - Display: VK13

Transaction Data - Sales Orders

Sales Order - Create: VA01

Sales Order - Change: VA02

Sales Order - Display: VA03

Sales order - List display: VA05

BLOCKED SD DOCUMENTS: VKM1

Transaction Data - Delivery

Delivery Create: VL01N

Delivery Change: VL02N

Delivery Display: VL03N

Delivery due list for sales & purchase orders: VL04

Outbound Delivery Monitor: VL06O

Incomplete Outbound Deliveries: V_UC

Transaction Data - Billing

Billing Document Create: VF01

Billing Document Change: VF02

Billing Document Display: VF03

Maintain Billing Due List: VF04

List Billing Documents: VF05

Billing Document Cancel: VF11

List - Blocked Billing Documents: VFX3

Billing Document - Background Processing: VF06

OUTPUT FROM BILLING: VF31

Excise Transaction Data (Indian Manufacturing Scenario)

Excise Invoice for Factory sales: J1IIN

Excise post & print for others mvmts: J1IV

Selection of Excise Invoice - Common: J1IK

Excise Invoice for Depot Sales: J1IJ

Cancel Excise Invoice/JV: J1IH

Excise Invoice Print: J1IP

PRINT EXCISE REGISTER: J2I6

EXTRACT EXCISE REGISTER: J2I5

PRINT EXCISE REGISTER: J2I6

CREATE EXCISE BOND: J1IBN01

CREATE / UPDATE ARE-1: J1IA101

CREATE / UPDATE ARE-3: J1IA301

PRINT ARE-1: J1IA101

Sales tax register: J1I2

Help on Internally Generated Documents: J1I7

Standard Reports - SD

Incomplete sales orders: VA.2

Outbound Delivery Monitor: VL06O

Customer Analysis- Sales: MC+E

Customer Returns-Analysis: MC+A

Material Analysis(SIS): MCTC

Sales org analysis: MCTE

Material Returns-Analysis: MC+M

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula

Former Member · ‎08-09-2007

Hi,

check ur mail, doc sent for Integration of SD with MM and FI.

Regards

Ali

End User Activities

Accepted Solutions (1)

Accepted Solutions (1)

Answers (3)

Answers (3)

Re: HANA DB PYTHON

HANA DB PYTHON

S/4 HANA Public Cloud Access

Re: Why we can move stock from quality management ...

Re: How to add tcode to role