Upload
smiti84
View
213
Download
0
Embed Size (px)
Citation preview
8/3/2019 Cross Company
1/8
Cross-Company Sales Order
ProcessingSAP Best Practices Baseline Package
(India)
SAP Best Practices
8/3/2019 Cross Company
2/8
8/3/2019 Cross Company
3/8
Scenario Overview 2
Required SAP ECC 6.0 EhP3
Company roles involved in process flows Sales Administration
Sales Billing
Warehouse Clerk
SAP Applications Required:
8/3/2019 Cross Company
4/8
Scenario Overview 3
Cross-Company Sales Order Processing
A customer orders goods from their vendors sales organization. The vendor
has a production/warehouse plant that belongs to a different company code.
The goods are produced/contained here and delivered from the
production/warehouse plant to the customer directly.
Detailed Process Description:
8/3/2019 Cross Company
5/8
Process Overview
Cross-Company Sales Order Processing
Delivers
IntercompanyBilling
Invoicesexternally
Orders
Customer100009
Sales Center
Deliv. Plant 1000Sales org. 1000Distr. channel 10Division 10Company code 1000
Production Plant
Plant 1010
Company code 1010Sales org. 1010Distr. channel 10Division 10Payer 1000 (for IVrepresenting CCode 1000
Payment
IntercompanyPayment
8/3/2019 Cross Company
6/8
Process Flow Diagram
Cross-Company Sales Order Processing
Sales A
dminis
tration
Sales
Billing
Event
W
areh
o
Custom
er
AR = Accounts Receivable
Create SalesOrder
Sales Need toBe Processed
Across DifferentCompany Code
OrderConfirmation
Daily shipmentworklist, enough
inventory
Delivery Due List
Delivery Note Bill of Lading
Check Batches /Assign Serial
Numbers
Post GoodsIssue
Pick List(Optional)Picking
Create BillingDocument
CreateIntercompany
Document
DisplayIntercompany
Document
Display BillingDocument
AR-IncomingPayment
(157)
End Process
8/3/2019 Cross Company
7/8
Legend
Symbol Description Usage Comments
To next / From last Diagram: Leads tothe 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 task step ina document; instead, it is used toreflect a document generated by a taskstep; this shape does not have anyoutgoing flow lines
Financial Actuals: Indicates a financialposting document
Does not correspond to a task step ina document; instead, it is used toreflect a document generated by a taskstep; this shape does not have any
outgoing flow lines
Budget Planning: Indicates a budgetplanning document
Does not correspond to a task step ina document; instead, it is used toreflect a document generated by a taskstep; this shape does not have anyoutgoing flow lines
Manual Process: Covers a task that ismanually done
Does not generally correspond to atask step in a document; instead, it isused to reflect a task that is manuallyperformed, such as unloading a truckin the warehouse, which affects theprocess flow.
Existing Version / Data: This blockcovers data that feeds in from anexternal process
Does not generally correspond to atask step in a document; instead, thisshape reflects data coming from anexternal source; this step does nothave any incoming flow lines
System Pass / Fail Decision: This blockcovers an automatic decision made bythe software
Does not generally correspond to atask step in the document; instead it isused to reflect an automatic decisionby the system that is made after a stephas been executed.
Hardcopy /Document
Financial Actuals
Budget Planning
ManualProcess
ExistingVersion /
Data
SystemPass/Fa
ilDecisio
n
Symbol Description Usage Comments
Band: Identifies a user role, such as Accounts Payable
Clerk or Sales Representative. This band can alsoidentify an organization unit or group, rather than aspecific role.
The other process flow symbols in this table go intothese rows. You have as many rows as required to coverall of the roles in the scenario.
Role band contains
tasks common tothat role.
External Events: Contains events that start or end thescenario, or influence the course of events in thescenario.
Flow line (solid): Line indicates the normal sequence ofsteps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-
used or conditional tasks in a scenario. Line can alsolead to documents involved in the process flow.
Connects two tasksin a scenarioprocess or a non-step event
Business Activity / Event: Identifies an action that eitherleads into or out of the scenario, or an outside Processthat happens during the scenario
Does notcorrespond to atask step in thedocument
Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario
Corresponds to atask step in thedocument
Process Reference: If the scenario references anotherscenario in total, put the scenario number and namehere.
Corresponds to atask step in thedocument
Sub-Process Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenario h ere
Corresponds to atask step in thedocument
Process Decision: Identifies a decision / branching point,signifying a choice to be made by the end user. Linesrepresent different choices emerging from differentparts of the diamond.
Does not usuallycorrespond to atask step in thedocument; Reflectsa choice to be madeafter step execution
External
toSAP
BusinessActivity / Event
Unit Process
ProcessReference
Sub-Process
Reference
ProcessDecisio
n
DiagramConnection
8/3/2019 Cross Company
8/8
Copyright 2008 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.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and associated logos displayed
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other 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 any particular course of business, product strategy,
and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or
other items contained 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 no control over the information that you may access through the use of hot links contained in these
materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.