122 erp606 process overview en xx

7

Click here to load reader

Upload: rajeshbhattu

Post on 03-Jun-2018

216 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 122 ERP606 Process Overview en XX

8/11/2019 122 ERP606 Process Overview en XX

http://slidepdf.com/reader/full/122-erp606-process-overview-en-xx 1/7

Batch Recall

SAP Best Practices

Page 2: 122 ERP606 Process Overview en XX

8/11/2019 122 ERP606 Process Overview en XX

http://slidepdf.com/reader/full/122-erp606-process-overview-en-xx 2/7

© 2012 SAP AG. All rights reserved. ‹#›

Purpose, Benefits, and Key Process Steps

Purpose A defect batch is identified and must be recalled from customers and prospects who havereceived the batch.

Benefits

Integrated follow-up process to the former delivered batchreturn stock managed separately from the rest of your stock

Key Process StepsCreation of direct mailing to customerPreparing follow-up process for the return of the batch

Receiving of returned batch into return stockDecision of further usage of the returned stockCreation of credit memo for customer

Page 3: 122 ERP606 Process Overview en XX

8/11/2019 122 ERP606 Process Overview en XX

http://slidepdf.com/reader/full/122-erp606-process-overview-en-xx 3/7

© 2012 SAP AG. All rights reserved. ‹#›

Required SAP Applications and Company Roles

Required SAP ApplicationsEnhancement package 6 for SAP ERP 6.0

Company RolesSales Administrator

Warehouse Clerk Accounts Receivable ManagerBilling AdministratorIT Administrator (Professional User)

Page 4: 122 ERP606 Process Overview en XX

8/11/2019 122 ERP606 Process Overview en XX

http://slidepdf.com/reader/full/122-erp606-process-overview-en-xx 4/7

© 2012 SAP AG. All rights reserved. ‹#›

Detailed Process Description

Batch Recall A program is executed to identify all customers who received a defect batch. The user thenchooses the addresses of the appropriate contact persons, and the system prints astandard letter to each customer to inform them of the recall. The subsequent activities foreach customer are stored in the system. Return deliveries are also entered and

documented, if necessary.To ensure that you contact all customers affected by a defect batch, you must identify ifsubsequent batches are affected by the defect batch. For this purpose, you can use thestandard system function “batch where -used list” that is described in detail in the standardSAP ERP documentation. This scenario recalls a batch from a finished product orwholesale product. Therefore you can simply find all customers who received theseproducts. However, a vendor could report that a raw, semi-finished, trading, or othermaterial used in your production, does not meet quality standards. In this case, you mustdetermine which finished or trading materials were produced with these defect batches.

Page 5: 122 ERP606 Process Overview en XX

8/11/2019 122 ERP606 Process Overview en XX

http://slidepdf.com/reader/full/122-erp606-process-overview-en-xx 5/7

© 2012 SAP AG. All rights reserved. ‹#›

Process Flow DiagramBatch Recall

S a l e s

A d m

i n i s t r a t o r

a n d I T - A

d m

i n i s t r a t o r

W a r e h o u s e

C l e r k / A c c o u n

t s

R e c e i v a b

l e M a n a g e r

E v e n

t

ProcessFollow-up

SalesActivities for

EachCustomer

Defect BatchMust BeRecalled

Address Listof CustomersWho Received

Batch

InvoiceFinancial

Accounting

ProfitabilityAnalysis

Direct Mailing – CreatingBasic Data

Create ReturnOrder

GenerateFollow-up

SalesActivities

Return Order

C u s t o m e r

CustomerReturnsMaterial

CustomerLetters

ReturnDelivery

Post GoodsReceipt

Release CreditMemo to

Billing

Credit Memo

Billing

SalesOrder

Processing: Sale fromStock (109)

B i l l i n g

A d m i n i s t -

r a t o r

AssignBatches

Assign SerialNumbers

Sales:Period End

ClosingOperations(203)

AccountsReceivable(157)

(Optional)Return to

Vendor(136)

(Optional)Stock UsageBlocking and

Scrapping(131)

(Optional)Rework

Processing(Stock-Manuf.Material)(151)

ReleaseBilling

Documentsfor

Accounting

Page 6: 122 ERP606 Process Overview en XX

8/11/2019 122 ERP606 Process Overview en XX

http://slidepdf.com/reader/full/122-erp606-process-overview-en-xx 6/7

© 2012 SAP AG. All rights reserved. ‹#›

Legend

Symbol Description Usage Comments

To next / From last Diagram: Leadsto the next / previous page of theDiagram

Flow chart continues on the next /previous page

Hardcopy / Document: Identifies aprinted document, report, or form

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Financial Actuals: Indicates afinancial posting document

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Budget Planning: Indicates abudget planning document

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Manual Process: Covers a taskthat is manually done

Does not generally correspond toa task step in a document;instead, it is used to reflect a taskthat is manually performed, suchas unloading a truck in thewarehouse, which affects theprocess flow.

Existing Version / Data: This blockcovers data that feeds in from anexternal process

Does not generally correspond toa task step in a document;instead, this shape reflects datacoming from an external source;this step does not have anyincoming flow lines

System Pass / Fail Decision: Thisblock covers an automaticdecision made by the software

Does not generally correspond toa task step in the document;instead it is used to reflect anautomatic decision by the systemthat is made after a step has beenexecuted.

E x

t e r n a

l

t o S A P

BusinessActivity / Event

Unit Process

ProcessReference

Sub-Process

Reference

ProcessDecision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProcess

ExistingVersion /

Data

SystemPass/FailDecision

Symbol Description Usage Comments

Band: Identifies a user role, such as AccountsPayable Clerk or Sales Representative. This bandcan also identify an organization unit or group,rather than a specific role.

The other process flow symbols in this table gointo these rows. You have as many rows asrequired to cover all of the roles in the scenario.

Role band containstasks common to thatrole.

External Events: Contains events that start or endthe scenario, or influence the course of events inthe scenario.

Flow line (solid): Line indicates the normal sequenceof steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow toinfrequently-used or conditional tasks in ascenario. Line can also lead to documents involvedin the process flow.

Connects two tasks ina scenario process ora non-step event

Business Activity / Event: Identifies an action thateither leads into or out of the scenario, or anoutside Process that happens during the scenario

Does not correspondto a task step in thedocument

Unit Process: Identifies a task that is covered in astep-by-step manner in the scenario

Corresponds to a taskstep in the document

Process Reference: If the scenario referencesanother scenario in total, put the scenario numberand name here.

Corresponds to a taskstep in the document

Sub-Process Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenariohere

Corresponds to a taskstep in the document

Process Decision: Identifies a decision / branchingpoint, signifying a choice to be made by the enduser. Lines represent different choices emergingfrom different parts of the diamond.

Does not usuallycorrespond to a taskstep in the document;Reflects a choice tobe made after stepexecution

< F u n c

t i o n

>

Page 7: 122 ERP606 Process Overview en XX

8/11/2019 122 ERP606 Process Overview en XX

http://slidepdf.com/reader/full/122-erp606-process-overview-en-xx 7/7© 2012 SAP AG. All rights reserved. ‹#›

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, PowerPoint, Silverlight, and Visual Studio areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power

Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registeredtrademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

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.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered t rademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerryTorch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android aretrademarks or registered trademarks of Google Inc.

© 2012 SAP AG. All rights reserved

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of W i-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, and other SAP products and services mentioned herein as wellas their respective logos are t rademarks or registered trademarks of SAP AG in Germanyand other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal

Decisions, 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 orregistered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°

, and B2B 360°

Services are registered trademarksof Crossgate AG in Germany and other countries. Crossgate 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 priorwritten permission of SAP AG.