Stock Transfer without DeliverySAP Best Practices Baseline Package(China)

SAP Best Practices

Scenario Overview – 1

PurposeTransfer material requested automatically by MRP or manually by a buyer fromone plant to another within the same company code

BenefitsSimple handling for processes where delivery is not required: Less documentsare generatedStock-in-transit can be monitored

Purpose and Benefits:

Scenario Overview – 2

SAP ECC 6.0 EhP3

SAP Applications Required:

BuyerWarehouse Clerk

Company Roles Involved in Process Flows :

Key Process Flows Covered:

One-step stock transferCreating stock transport orderPosting goods issue for stock transport orderChecking the status of the stock transferReceiving transferred materials

Scenario Overview – 3

Stock Transfer without DeliveryThe cross-plant internal procurement of materials can be carried out within onecompany code (intercompany) or by using several company codes (cross-company).This process can be dealt with using standard functions, such as materialrequirements planning, purchase requisitions, stock transport orders, transportationplanning, and the handling of internal deliveries.

The process begins with a requirement to transfer material from one plant to anotherwithin the same company code. The stock transfer without a delivery can beperformed in two different ways:

A one-step transfer posting at the issuing plant is possible which moves the stockimmediately from the issuing plant to the receiving plant. This is useful if the distancebetween the two plants is short and when there is no need for stock-in-transit stockoverview.

A buyer at the receiving plant requests material with a stock transport order. This isuseful if the issuing plant needs a formal request to send material to the receivingplant or the distance between the two plants is longer and there is a need for stock-in-transit stock overview.

There are no master data requirements beyond the material master to support thestock transfer process. The material master must exist in both the procuring(receiving) plant and the providing (issuing) plant. Also, stock transfer purchase ordersare not subject to approval like other purchase orders.

Detailed Process Description:

Process Flow DiagramStock Transfer without Delivery

War

ehou

seC

lerk

Rec

eivi

ngPl

ant 2

Even

t Need formaterial

MaterialArrival atPlant 2

MRP = Material Requirements Planning, GR = Goods Receipt

War

ehou

se C

lerk

Issu

ing

Plan

t 1

Create StockTransportOrder (UB)(w/o MRP)B

uyer

Rec

eivi

ngPl

ant 2

InventoryTransfer @

Standard CostGain/LossInventoryTransfer

Post GoodsIssue

Check Statusof StockTransfer

GI Slip

Post Goodsreceipt forDelivery

GR Slip

End Process

Post Goodsreceipt (onestep stocktransfer)

Legend

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.

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

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

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

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.

Manual Process: Covers a taskthat is manually done

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

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

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

Flow chart continues on the next /previous page

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

Usage CommentsDescriptionSymbol

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProcess

ExistingVersion /

Data

SystemPass/FailDecisionDoes not

usuallycorrespond to atask step in thedocument;Reflects achoice to bemade after stepexecution

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.

Corresponds toa task step inthe document

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

Corresponds toa task step inthe document

Process Reference: If the scenario references anotherscenario in total, put the scenario number and namehere.

Corresponds toa task step inthe document

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

Does notcorrespond to atask step in thedocument

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

Connects twotasks in ascenarioprocess or anon-step event

Flow line (solid): Line indicates the normal sequenceof steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line canalso lead to documents involved in the process flow.

External Events: Contains events that start or end thescenario, or influence the course of events in thescenario.

Role bandcontains taskscommon to thatrole.

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 go intothese rows. You have as many rows as required tocover all of the roles in the scenario.

UsageComments

DescriptionSymbol

<Fun

ctio

n>E

xter

nal

to S

AP

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

ProcessDecision

Copyright 2008 SAP AGAll 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 changedwithout 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 aretrademarks 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 displayedare 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 documentcontains 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, orother 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 ofmerchantability, 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 limitationshall 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 thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.