lo extraction part 1 sd overview

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

LO Extraction – Part 1: SD

Application Short Overview

Applies to:

SAP BI, NW2004s Business Intelligence, ABAP, BI. For more information, visit the EDW homepage.

Summary

This article explains about LO extraction and its relevant SD application overview.

Author: P Renjith Kumar

Company: SAP Labs India PVT Ltd

Created on: 10 June 2010

Author Bio

P Renjith Kumar is presently working in SAP Labs India Pvt Ltd and specializes in Extraction and Modeling areas of BI. Basically as an ABAP consultant, he has extensive cross functional experience and has been with end to end SAP ERP and BI implementation projects across manufacturing domain.

https://www.sdn.sap.com/irj/sdn/nw-bi

LO Extraction – Part 1: SD Application Short Overview


© 2010 SAP AG 2

Table of Contents

Introduction ................................................................................................................................................... 3

Sales ......................................................................................................................................................... 3

Shipping........................................................................................................................................................ 3

Billing ......................................................................................................................................................... 3

Organization Structure in Sales and Distribution ............................................................................................ 4

Sales and Distribution Process Overview ...................................................................................................... 6

Order Creation .............................................................................................................................................. 7

Delivery......................................................................................................................................................... 7

Billing ......................................................................................................................................................... 9

Tables Involved ........................................................................................................................................... 10

Transactions ............................................................................................................................................... 11

The complete SD flow ................................................................................................................................. 12

In next part we will see about the extractors in LO extraction for SD module. ............................................... 12

Related Content .......................................................................................................................................... 13

Copyright .................................................................................................................................................... 14



© 2010 SAP AG 3

Introduction

This article addresses the requirement and significance of SD application in LO extraction. This article gives you a brief overview of SD application module relevant for BI. The first part deals with Functional flow, Transaction, Tables and their relations.

In SD overview we learn 3 important areas of SD where we do OLAP analysis. Those are.

Sales

Sales allow you to execute different business transactions based on sales documents defined in the system.

Four groups of sales documents are differentiated:

Customer inquiries and quotations Sales orders Outline agreements, such as contracts and scheduling agreements Complaints, such as free of charge deliveries, credit and debit memo requests and returns

Shipping

Shipping is an important part of the logistics chain in which guaranteed customer service and distribution planning support play major roles.

In shipping processing, all delivery procedure decisions can be made at the start of the process by

Taking into account general business agreements with your customer Recording special material requests Defining shipping conditions in the sales order

The result is an efficient and largely automatic shipping process in which manual changes are only necessary under certain circumstances.

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.

This component includes the following functions:

Creation of:

1. Invoices based on deliveries or services

2. Issue credit and debit memos

3. Pro forma invoices

Cancel billing transactions

Comprehensive pricing functions

Issue rebates

Transfer billing data to Financial Accounting (FI)



© 2010 SAP AG 4

Organization Structure in Sales and Distribution

CLIENT:

Client is the highest level in SAP

Client is representing group or corporate identity and

Under which the SAP system runs normal business

Common data base for the client

Data of one client cannot be accessed from other client Company

Company signifies a legal unit under the client level that produces its own financial documents, balance sheet and profit and loss statement Plant

Plant is a production facility or a group of storage locations where stocks are kept.Planning and inventory management take place at plant level. Sales Organization

A Legal unit responsible for selling materials and services for one or more plants and for negotiating

Prices and terms of delivery with the Customer. Distribution Channel

Products, services selling channel to customer Division

A way of grouping Materials, Products or services.



© 2010 SAP AG 5

Sales Area

Combination of

Sales Organization

Distribution Channel

Division Master Data in Sales and Distribution

The source of master data for sales order includes

Customer master data : Info about customers

Material Master data : Has info about material

Conditions master data : For automatic pricing

Output : Information that is sent to customer using various media

Control tables : Tables maintained in customizing Customer Master data has these details

General Data Company Code data Sales area Data Excise details

Partner Functions in customer master

Partner functions are terms that describe the people and organizations with whom you do business, and who are therefore involved in transactions. For example, when you create an Activity, based on Customizing settings, it automatically includes the partner functions activity partner, contact person, and person responsible. Partner functions are always assigned to partner function categories, which are hard-coded in the system.

Partner function Partner function category Relationship category

Sold-to party Sold-to party

Ship-to party Ship-to party/Service recipient Is the goods recipient of

Sales prospect Activity partner Is the activity partner for

Activity partner Activity partner Is the activity partner for

Sales manager Employee Is the employee responsible for

In general

Sold-to-party : Places the order

Ship-to-party : Receives the goods or services

Bill-to-party : Receives the invoices for goods or services

Payer : Responsible for paying the amount

http://help.sap.com/saphelp_sm40/helpdata/EN/ce/5c4872328cd311ae690060b03c9bbe/content.htm

http://help.sap.com/saphelp_sm40/helpdata/EN/ef/8370208881d3118f330060b03ca38c/content.htm



© 2010 SAP AG 6

Sales and Distribution Process Overview

Presales activity

Enquiry and Quotations comes at this stage. Sales order processing

Acceptance of customer’s Sales order

Important type of Sales orders are Scheduling agreement Order Rush order Stock transport order Free of cost order



© 2010 SAP AG 7

Order Creation

Delivery

Out bound Delivery Creation > A document created with reference to Sales order



© 2010 SAP AG 8

A delivery document will have header and item

Post Goods issue Once this is done the outbound delivery status is updated. The billing due list is updated. Material stock will be reduced.



© 2010 SAP AG 9

Billing

Bills can be created with reference to Order

Delivery

Previous bill After creating billing

Customer accounted debited

Cost of goods sold account credited

Tax & Duties GL account posted

Billing types

Invoce creation



© 2010 SAP AG 10

A billing document has header and item

A billing document creation has following effects

Tables Involved

Sales order VBAK -SD header

VBAP -SD item



© 2010 SAP AG 11

Billing VBRK -Billing header

VBRP -Billing item

Shipping VTTK -Shipment header Delivery LIKP -Delivery header

LIPS -Delivery item

Pricing KONH -Conditions header

KONP -Conditions item

Transactions

MM01-Create material

VA01-Create sales order

VA32-Scheduling agreement

VF02-Change billing document

VL01 -Create delivery

VK01 -Create sales order

VD01 -Create sales area

FD01 -Create accounting

VA21-Create quotation

VA11-Create inquiry

VA41-Create contract

VA05-List of sales order



© 2010 SAP AG 13

Related Content

http://help.sap.com/saphelp_erp60_sp/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm

For more information, visit the EDW homepage

http://help.sap.com/saphelp_erp60_sp/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm

https://www.sdn.sap.com/irj/sdn/nw-bi



© 2010 SAP AG 14

Copyright

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,

PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,

Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems

Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by

Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered

trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable fo r errors or

omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituti ng an

additional warranty.

lo extraction part 1 sd overview

Education