erp process overview
TRANSCRIPT
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 1/30
Sales Order Management
SAP Best Practices for Retail
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 2/30
© 2011 SAP AG. All rights reserved. 2
Purpose, Benefits, and Key Process Steps
Purpose
Sales Order Management describes a Business-to-Business (B2B) scenario: you sell to your known customer(s)(with master data record), who in turn sell(s) the merchandise to their customers (wholesale function). Inaddition to sales order processing functions, this scenario also includes the following process steps: credit limitcheck and availability check, consignment, backorder processing, customer contract, product catalog, onlinestore, customer billing document, payment handling, and subsequent settlement.
Benefits The entire document chain - presales phase, order, follow-up actions - forms a document flow or history. The
flow of data from one document to another reduces manual processing and facilitates problem solving.
Backorder fulfillment from returns stock allows you to manage how returns are to be allocated for backordersand stock transfers: If the article is unused and can be readily shipped again, then it is quicker and more cost-effective to use it to fill sales backorders or stock transfer orders rather than to move it back to unrestricted-usestock and for subsequent picking and reshipment.
Key Process Steps Creation of Standard Orders, Rush Orders, Third-Party Orders
Backorder Processing and Rescheduling
Creation of Customer Billing Documents
Payment Handling
Customer Returns Handling
Subsequent Settlement
Customer Consignment Handling
Customer Contract Handling
Product Catalog Handling
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 3/30
© 2011 SAP AG. All rights reserved. 3
Required SAP Applications and Company Roles
Required SAP Applications
SAP SAP enhancement package 3 for SAP ERP 6.0
Company Roles
Retail Sales Person
Retail Store Manager
Retail Warehouse Clerk
Accounts Payable Assistant
Accounts Receivable Assistant
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 4/30
© 2011 SAP AG. All rights reserved. 4
Process Flow DiagramSales Order / Backorder Processing and Rescheduling
R e t a i l
W a r e h o u s e C l e r k
R e t a i l S t o r e
M a n a g e r
R e t a i l S a l e s
P e r s o n Standard Order/
Rush Order/Third Party
Order
Analyze SalesDocument
Rescheduling
Backorder Processing andRescheduling
Monitor theReturns Stock
after Distribution
DirstibuteReturns Stockto Backorders
RescheduleSales
Documents
Credit LimitCheck
AvailabilityCheck
Run CATTMonitor the
Returns Stock
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 5/30
© 2011 SAP AG. All rights reserved. 5
Sales Order: Alternatives
A Sales order is a customer request to the company for the delivery of goods or services at a certain time.
The request is received by a sales area, which is then
responsible for fulfilling the order.
Standard order:
Merchandise will be collected or rather delivered and invoicedafterwards.
Rush order:
Merchandise will be collected or rather delivered imme-
diately and invoiced afterwards.
Third-party order:
Merchandise will be delivered directly by the vendor to the
customer. The ordering enterprise invoices to the customer
Cash sales order:
Merchandise will be collected and payed immediately.
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 6/30
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 7/30© 2011 SAP AG. All rights reserved. 7
Options in the order creation - 2
The credit limit check is a check, whether
a customer has already covered his credit limit
and which consequences are connected
with it (warning, fault, delivery block).
This check can be carried out in every sales document.
The delivery of a product to a delivery date is only possible
if this product is available for all processing steps to be
carried out before the delivery.
To guarantee this the availability check is used in the
order.
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 8/30© 2011 SAP AG. All rights reserved. 8
Backorder Processing
Backorder processing with a
selective list for sales
documents
Select and process
backorders for a particular
article
Manual processing
Assignment of the ATP-
quantities
Check the returns stocks on goodsnot damaged and not used
Listing of relevant requirements for sales documents
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 9/30© 2011 SAP AG. All rights reserved. 9
Rescheduling
Selection of the open sales document
Positions of the selected article
and
availability check
Analysis of the last rescheduling run
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 10/30© 2011 SAP AG. All rights reserved. 10
“Customer billing document” is an umbrella term
for invoices, credit memos, debit memos, pro-forma invoices, and cancellation documents.
Billing represents the final processing stage for a
business transaction in Sales and Distribution
Customer Billing Document
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 11/30© 2011 SAP AG. All rights reserved. 11
Process Flow DiagramCustomer Billing Document
R e t a i l S a l e s P e
r s o n
GeneratePreceeding
Documents viaECATT
Create BillingDocumnet Online
on the basis of the Outbound
Delivery
IncomingPayment in FI
GenerateCollective billingDocument in the
Background
Alternative 1
Alternative 2
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 12/30© 2011 SAP AG. All rights reserved. 12
The milestone billing in the billing plan is used for
the payment processing of a deposit.
Milestone billing means, that the total value, which
should be invoiced, is divided in several partialamounts in the billing plan (percentage /
absolute), they are to be paid at certain dates.
A milestone billing is a schedule with particular
billing dates.
Payment Handling
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 13/30© 2011 SAP AG. All rights reserved. 13
Process Flow DiagramPayment Handling
A c c o u n t s R e c e i v a b l e
A s s i s t a n t
A c c o u n t s P a y a b l e
A s s i s t a n t
R e t a i l S a l e s P e r s o n
Down PaymentAgreement in
the Sales Oder
Print the FinalBilling
Document(Screen)
IncomimgPayment for theDown PaymentRequest in FI
Clear thePayment thathas already
been made in FI
DownPayment
request in SD
Print the DownPaymentRequest(Screen)
Final Billing withDown PaymentClearing in SD)
IncomimgPayment in FI
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 14/30© 2011 SAP AG. All rights reserved. 14
There are various reasons for returning goods:- The goods are damaged in some way so that they cannot
be transferred back into normal stock, but have to bereturned to the vendor.
- The customer did not like the goods and wants to replacethem. The goods can, however, be reused either fully or
partially.- The customer did not like the goods and wants their money back or a credit memo. The goods can bereused either fully or partially.
When the returned goods are received from the customer,they are initially posted into blocked returns stock. Thereturned goods are checked and a decision is made as to
what
to do with them, for example: breakage stock (returnedto vendor or destroyed), staff sales, transfer tonormal stock/distribution to backorders.
Customer Return
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 15/30© 2011 SAP AG. All rights reserved. 15
Process Flow DiagramCustomer Return
R e t a i l S a l e s P e r s o n
Preparations
Execution
Transfer from
Rerurns Stockto Blocked
Stock
Stock Control
Goods Issue for the Free of
ChargeSubsequent
Delivery
Create a
Delivery for theFree of Charge
SubsequentDelivery
Create aReturnsDelivery
Full Transfer
PostingtoUnrestricted-
Use Stcok
Stock Control
Release theReturns for SubsequentProcessing
Create aReturn
Monitor theReturns Stock
Transfer fromBlocked Stock
to ReturnDeliveryStoragelocation
Check theDocument Flow
Create a Free of Charge
SubsequentDelivery
Remove theBilling Block
Issue theCredit Memo
CreateReturns Order
Post the GoodsReceipt for the
Returns
Post the Goodsreceipt for the
ReturnedGoods
Monitor theReturns Stock
Create a Returnwith Free of
ChargeSubsequent
Delivery
Stock Display
Create CreditMemo
Release toAccounting
Create aReturnsDelivery
Post theReturnsDelivery
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 16/30© 2011 SAP AG. All rights reserved. 16
Process of Returns Handling
Finance: Logistics:
Input of customer returns
Credit note or
Subsequent delivery free of
charge
Stock
Stock correction (Input to
blocked stock)
Following processes
Log. invoice verification
Input of customer returns
Goods receipt
Creation of customer returns order
Stock transfer posting
into unrestricted stock or
Dispatching to backorders
Transfer posting to returns stock
Following processes
Return delivery to vendor
Invoice verification
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 17/30© 2011 SAP AG. All rights reserved. 17
Arrival of the return goods
Posting in blocked stock
Goods receipt posting
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 18/30
© 2011 SAP AG. All rights reserved. 18
Evaluation of the return goods
Control of the goods
Decision of further use
Transfer back to
unrestricted stock
Transfer to
returns stock
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 19/30
© 2011 SAP AG. All rights reserved. 19
Additional Use I – Unrestricted Stock
Tranfer back to unrestricted stock
Allocate to open orders
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 20/30
© 2011 SAP AG. All rights reserved. 20
Additional Use II – Returns Stock
Transfer back to returns stock
Disposal
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 21/30
© 2011 SAP AG. All rights reserved. 21
Subsequent process
Return delivery to vendor
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 22/30
© 2011 SAP AG. All rights reserved. 22
As part of the subsequent settlement procedure,you can offer a reduced price, for example,
when a customer buys certain quantities of particular articles together, uses a customer card for payment, or reaches or exceeds thesales volume in a period that has been agreedupon in advance.
Subsequent Settlement
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 23/30
© 2011 SAP AG. All rights reserved. 23
Process Flow DiagramSubsequent Settlement
R e t a i l S a l e s P e r s o n
8.3RebateProcessing
(in SD)
8SubsequentSettlement
8.3.3Update the
Sales Volume
8.3.2Create Rebate
Agreement
8.3.4Generate
‚New‘ SalesVolume
8.3.1.1Settlemenr of
theAgreement(s)
8.3.1Display theStatus of Rebate
Agreement
8.3.4.1Create Sales
Order
8.3.5Display SalesVolume Data
8.3.4.2.3Document
Flow
8.3.4.3Create Billing
Document
8.3.4.2.1Create Delivery
8.3.4.2.2Create Transfer
Order andCorfirm with GI
8.3.4.2OutboundDelivery
8.3.6Display Drill
Downs
8.3.8Release
Agreement
for Settlement
8.3.7Carry outpartcial
Settlement
8.3.7.1Release CreditMemo Requestfor the Partial
RebateSettlement
8.3.7.2Bill Credit
Memo Requestfor the Partial
rebateSettlement
8.3.9Create Final
Settlement
8.3.9.2Bill RebateCredit MemoRequest for theFinalSettlement
8.3.9.1Release RebateCredit MemoRequest for theFinalSettlement
8.3.10DisplayPaymentHistory
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 24/30
© 2011 SAP AG. All rights reserved. 24
Consignment goods are goods that are stored at acustomer location but that are still owned by your company. From a planning point of view this stock isno longer available and is managed independently.
The customer is not obliged to pay for these goods until
they remove them from consignment stock.Otherwise, the customer can usually returnconsignment goods that are not required.
Consignment processing is advantageous to bothparties. Customers store the consignment goods attheir own warehouses. The customer can access thegoods in the consignment warehouse at any time.
They are only billed for the goods when they areremoved from the warehouse and only for the actualquantity taken.
Customer Consignment
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 25/30
© 2011 SAP AG. All rights reserved. 25
Process Flow DiagramCustomer Consignment
R e t a i l S a l e s P e r s o n
Reduce theConsignment
Stock atCustomer
Alternative 1:ConsignmentIssue
Create Delivery
Alternative 2:ConsignmentPick-Up
Optional Processafter Consignment
Issue:Consignment
Returns
Billing or CreditMemo for theConsignment
Return Created
Remove theBilling Block
Goods Receipt
Billing Goods Issue
ConsignmentFill-Up
Create andCorfirm
Transfer Order Document Flow
ConsignmentStock
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 26/30
© 2011 SAP AG. All rights reserved. 26
Customer contracts are outline customer
agreements that display when goods are
purchased within a certain time period.
Contracts are concluded with the customer so that
the purchasing/production and sale of goods
can be estimated better, which in turn enables
better conditions to be negotiated.
Customer Contract
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 27/30
© 2011 SAP AG. All rights reserved. 27
Process Flow DiagramCustomer Contract
R e t a i l S a l e s P e r s o n
Create Contractrelease Order
for ValueContract
Create Contractrelease Order
for QuantityContract
Value Contract
Quantity
Contract
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 28/30
© 2011 SAP AG. All rights reserved. 28
The product catalog is the basis for printed andelectronic catalogs. The catalog is maintained in
the SAP ERP System and can be transported toexternal systems and processed as templatesfor print catalogs or electronic catalogs (CD-
ROM or Internet). IDocs and BAPIs areavailable for exporting the catalog data.
Product Catalog
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 29/30
© 2011 SAP AG. All rights reserved. 29
Process Flow DiagramProduct Catalog
R e t a i l S a l e s P e r s o n
Create aProductCatalog
Create BasicData
MaintainDocuments and
Texts in theArticle Master
Add ArticlesLayout Areas
Manually
Pricing in theProductCatalog
Create aLayout
HierarchyManually
Create Lower-
Level LayoutAreas
Determine the
PricingProcedure
Create theLayout
Hierarchy of theProduct Catalog
Customer
PricingProcedure
MaintainArticles
MaintainLayout Areas
Maintain Textsand Documentsfor Articles andLayout Areas
Alternative:Create Layout
HierarchyAutomatically
Link betweenPromotion and
Product Catalog
PromotionalSales Prices
CreateDocument Info
Records
Add ArticlesLayout Areas
Using theDefault Article
Create aPromotion
Product Catalog
Create layoutHierarchy
Create BasicData
7/30/2019 ERP Process Overview
http://slidepdf.com/reader/full/erp-process-overview 30/30
No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.
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 registeredtrademarks 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 aretrademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide 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 BusinessObjects Explorer,StreamWork, 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.
© 2011 SAP AG. All rights reserved
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarksof Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.
The information in this document is proprietary to SAP. No part of this document may bereproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or anyother agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to anyparticular course of business, product strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does notwarrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct,
special, indirect, or consequential damages that may result from the use of these materials.This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has nocontrol over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of third-party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.