Вы находитесь на странице: 1из 7

Stock Transfer without Delivery

SAP Best Practices Baseline Package


(Vietnam)

SAP Best Practices


Scenario Overview – 1

Purpose and Benefits:

Purpose
 Transfer material requested automatically by MRP or manually by a buyer from
one plant to another within the same company code
Benefits
 Simple handling for processes where delivery is not required: Less documents
are generated
 Stock-in-transit can be monitored

Key process flows covered


 One-step stock transfer
 Creating stock transport order
 Posting goods issue for stock transport order
 Checking the status of the stock transfer
 Receiving transferred materials
Scenario Overview – 2

SAP Applications Required:


Required
 EHP3 for SAP ERP 6.0

Company roles involved in process flows


 Buyer
 Warehouse Clerk
Scenario Overview – 3

Detailed Process Description:


Stock Transfer without Delivery
The cross-plant internal procurement of materials can be carried out within one
company code (intercompany) or by using several company codes (cross-company).
This process can be dealt with using standard functions, such as material
requirements planning, purchase requisitions, stock transport orders, transportation
planning, and the handling of internal deliveries.
The process begins with a requirement to transfer material from one plant to another
within the same company code. The stock transfer without a delivery can be
performed in two different ways:
A one-step transfer posting at the issuing plant is possible which moves the stock
immediately from the issuing plant to the receiving plant. This is useful if the distance
between the two plants is short and when there is no need for stock-in-transit stock
overview.
A buyer at the receiving plant requests material with a stock transport order. This is
useful if the issuing plant needs a formal request to send material to the receiving
plant 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 the
stock transfer process. The material master must exist in both the procuring
(receiving) plant and the providing (issuing) plant. Also, stock transfer purchase
orders are not subject to approval like other purchase orders.
Process Flow Diagram
Stock Transfer without Delivery

Need for Material


material Arrival at End Process
Plant 2
t nev E RM
gni vi ece R r ell ort -noPC

Create Stock
Transport Order
(UB) (w/o MRP)
r ey u B
2 t nal P

GI Slip

Inventory Transfer
@ Standard Cost Post
Gain/Loss Goods
Inventory Transfer Issue Check Status of
1 t nal P

Stock Transfer
es uoher a W
gni ussI kr el C

Post Goods
receipt for
Delivery
Post Goods receipt
(one step stock
transfer)
2 t nal P

GR Slip
es uoher a W
gni vi ece R kr el C

MRP = Material Requirements Planning, GR = Goods Receipt


Legend

Symbol Description Usage Comments Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Payable Role band contains To next / From last Diagram: Leads to Flow chart continues on the next /
Clerk or Sales Representative. This band can also tasks common to the next / previous page of the previous page
Diagram
identify an organization unit or group, rather than a that role.
<Function>

specific role. Diagram


Connection
The other process flow symbols in this table go into
these rows. You have as many rows as required to cover
all of the roles in the scenario.
Hardcopy / Document: Identifies a Does not correspond to a task step in
printed document, report, or form a document; instead, it is used to
Hardcopy / reflect a document generated by a task
External Events: Contains events that start or end the step; this shape does not have any
scenario, or influence the course of events in the Document outgoing flow lines
scenario.
l anr et x E
PAS ot

Financial Actuals: Indicates a financial Does not correspond to a task step in


Flow line (solid): Line indicates the normal sequence of Connects two tasks posting document a document; instead, it is used to
steps and direction of flow in the scenario. in a scenario reflect a document generated by a task
process or a non- Financial step; this shape does not have any
Flow line (dashed): Line indicates flow to infrequently- step event Actuals outgoing flow lines
used or conditional tasks in a scenario. Line can also
lead to documents involved in the process flow.

Budget Planning: Indicates a budget Does not correspond to a task step in


Business Activity / Event: Identifies an action that either Does not planning document a document; instead, it is used to
leads into or out of the scenario, or an outside Process correspond to a task reflect a document generated by a task
Business that happens during the scenario step in the step; this shape does not have any
document Budget outgoing flow lines
Activity / Planning
Event

Unit Process: Identifies a task that is covered in a step-by- Corresponds to a


step manner in the scenario task step in the Manual Process: Covers a task that is Does not generally correspond to a
document manually done task step in a document; instead, it is
used to reflect a task that is manually
Unit Process Manual performed, such as unloading a truck
Proces in the warehouse, which affects the
s process flow.

Process Reference: If the scenario references another Corresponds to a


scenario in total, put the scenario number and name task step in the
here. document Existing Version / Data: This block Does not generally correspond to a
Process
Reference covers data that feeds in from an task step in a document; instead, this
external process shape reflects data coming from an
Existing external source; this step does not
Version / have any incoming flow lines
Sub-Process Reference: If the scenario references another Corresponds to a Data
scenario in part, put the scenario number, name, and the task step in the
step numbers from that scenario here document
Sub-
Process System Pass / Fail Decision: This block Does not generally correspond to a
Reference covers an automatic decision made by task step in the document; instead it is
System the software used to reflect an automatic decision
Pass/F by the system that is made after a step
Process Decision: Identifies a decision / branching point, Does not usually ail has been executed.
signifying a choice to be made by the end user. Lines correspond to a task Decisio
represent different choices emerging from different parts step in the n
Proces of the diamond. document; Reflects
s a choice to be made
Decisio after step execution
n
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.

Вам также может понравиться