SAP-Cross System Stock In Transit Without APO

“Stock In Transit”
Across SAP SystemsAcross SAP Systems
Solution BriefSolution Brief

Index
Synopsis11
Cross System Stock In Transit Requirements22 Cross System Stock In Transit Requirements22
IT Sapiens’ Solution Features33
Solution Process Flow44
Solution Demo55
Solution Merits66
Our Value Proposition77
1 November 1st 2017 ©2017IT Sapiens, Inc.
Proprietary and Confidential
Questions ?88

Synopsis11
 Goods Flow Across SAP Systems at most Customers:
 No SAP ERP Global Instance for possibly some of the following reasons:
 Disparate Business Processes across Companies or Regions, leadingp p g g
to disparate SAP designs that could not peacefully co-exist in 1
system
 Global Business Process Harmonization is an “in process” a multi-Global Business Process Harmonization is an in process a multi
year project
 Acquisitions could not be merged into 1 SAP system due to stringent
“Ti T B fit” ti li“Time To Benefit” timelines
 Batch Management level could not be changed from “Batch Unique at
Plant level” to “Batch Unique at Material Level”
 Use of “Sales Orders in sending system” as a surrogate for “Purchase
Orders in receiving system” to trigger the Logistics Cycle, leading to “NO
STOCK IN TRANSIT VISIBILITY” in receiving system, upon shipping from
2 November 1st 2017 ©2017 IT Sapiens, Inc.
g y p pp g
sending system
(Contd…)

Synopsis11
 Goods Flow Across SAP Systems at most Customers:
 No Cost Realization for Stock In Transit, in receiving System’s Company
books
 Extensive Custom development to manage cross reference across
systems
 Use of APO for process of orchestration across SAP SystemsUse of APO for process of orchestration across SAP Systems

Stock In Transit Across SAP systems - Requirements22
 Industry Requirements for “Cross SAP Systems Stock In Transit”:
 Need ability to create a Stock Transport Purchase Order (e.g.Type UB) or a
normal Purchase Order (e.g. Type NB), with Supplying Plant that does not( g yp ) pp y g
exists in the “receiving” SAP system
 Need ability for system to automatically create an immediate delivery in the
“sending” SAP system with reference to the Stock Transport Purchasesending SAP system, with reference to the Stock Transport Purchase
Order from the “receiving” system
 Need ability for system to automatically update the Purchase Order History
i “ i i ” t ith th d li i f ti f th “ di ”in “receiving” system with the delivery information from the “sending”
system
 Need ability for system to automatically update “Stock In Transit” in
“receiving” system, upon Posting Goods Issue for the Delivery in the
“sending” system
 Need ability for system to automatically create an “Inbound Delivery” in
4
y y y y
“receiving” system, upon Posting Goods Issue for the Delivery in the
“sending” system November 1st 2017 ©2017IT Sapiens, Inc.
(Contd…)

Stock In Transit Across SAP systems - Requirements22
 Industry Requirements for “Cross SAP Systems Stock In Transit”:
 Need ability for system to automatically post accounting documents for
“Stock In Transit” in “receiving” system, upon Posting Goods Issue for theg y p g
Delivery in the “sending” system
 Need ability to view Stock In Transit in Transaction MMBE
 Need ability to view Stock In Transit in Transaction MB5TNeed ability to view Stock In Transit in Transaction MB5T

 Solution Excerpts:
 Ability to create a Stock Transport Purchase Order (e.g.Type UB-Intra CC)
or a normal Purchase Order (e.g. Type NB-Inter CC), with Supplying Plant
that does not exists in the “receiving” SAP system
 Automatically creates a Replenishment Delivery in “sending” system with
reference to Purchase Order in “receiving” systemreference to Purchase Order in receiving system
 Automatically Updates Purchase Order History in “receiving” system with
Delivery Information from “sending” system
 D li i “ di ” t i ibl f P h O d Hi t Delivery in “sending” system is accessible from Purchase Order History
 If Delivery in “sending” system is deleted, the Purchase Order History in
“receiving” system is also updated to reflect the delivery deletion in
“sending” system
(Contd…)

 Solution Excerpts:
 Delivery Post Goods Issue in “sending” system, automatically updates:
 Posts a corresponding Material Document and related Accounting
Document in “receiving” system
 Updates Purchase Order History in “receiving” system
 Posts Stock In Transit in “receiving” system Posts Stock In Transit in receiving system
 Creates an Inbound Delivery in “receiving” system
 Stock In Transit in “receiving system” can be viewed in Transaction MMBE
 P h O d ifi St k I T it i “ i i t ” b Purchase Order specific Stock In Transit in “receiving system” can be
viewed in Transaction MB5T too
 Provides ability to maintain Master Data and Organizational Data
translation / mapping rules, if not same across systems
 Integration between SAP ECC 6.0 EHP4 and above ERP systems
 No Intermediate SCM-APO system required
7
y q
 NO SOURCE CODE MODIFICATIONS OF ANY KIND
November 1st 2017 ©2017IT Sapiens, Inc.

Solution Process Flow – Purchase Order Creation in
“Receiving” System
44
(Contd…)

Solution Process Flow – Delivery Processing in “Sending”
System
44
Proprietary and Confidential (Contd…)

Solution Process Flow – Goods Receipt Processing in
“Receiving” System
44
Proprietary and Confidential (Contd…)

Demo – Systems Landscape and Dataset55
 Process:
 “Receiving / Procuring” System
 SAP ECC 6.0 Client 030
 Logical System IENCLNT030
 Procuring Plant  1100 (with Customer # P1100)
 Purchase Order CreationPurchase Order Creation
 Stock In Transit Update and visibility in MMBE and MB5T
 Inbound Delivery creation
 Goods Receipt Goods Receipt
 “Sending / Shipping” System
 SAP ECC 6.0 Client 020
 Logical System IENCLNT020
 Supplying Plant  1900
 Replenishment Delivery Creation
11
 Delivery Picking and Goods Issue Posting
(Contd…)

Demo – Purchase Order Creation in “Receiving” System55
 Process:
 Stock Transport Purchase Order created for a Supplying Plant NOT existing in “receiving /
procuring” system
12 (Contd…)

Demo – Auto.Delivery Creation in “Sending/Shipping”
System
55
 Process:
 Replenishment Delivery Automatically created in “Sending/Shipping” System
Proprietary and Confidential (..Contd…)

System
55
 Process:
 Purchase Order Reference and Source Document System stored in Delivery

System
55
 Process:
 Purchase Order History updated with Delivery Information in the “Receiving / Procuring” System

Demo – Delivery Goods Issue in “Sending/Shipping”
System
55
 Process:
 Delivery Goods Issue in “Sending / Shipping” System updates Purchase Order History in
“Receiving / Procuring System”

System
55
 Process:
 Delivery Goods Issue in “Sending / Shipping” System updates Stock In Transit in “Receiving /
Procuring System” (Txn MB5T Shown Below)

System
55
 Process:
 Delivery Goods Issue in “Sending / Shipping” System creates Inbound Delivery in “Receiving /
Procuring System”

System
55
 Process:
 Delivery Goods Issue in “Sending / Shipping” System updates Stock In Transit in “Receiving /
Procuring System” (Txn MMBE Shown Below)

Demo – Goods Receipt w.r.t. PO in “Receiving/Procuring”
System
55
 Process:
 Goods Receipt w.r.t. Purchase Order in “Receiving / Procuring” System decrements Stock In
Transit and increments regular stock (Txn MMBE Shown Below)

Solution Merits66
 “Stock In Transit Across Systems” Merits:
 Slim process that does not require creation of Sales Order in “Sending /
Shipping” System to trigger Delivery creationpp g y gg y
 Cross System real time Purchase Order History updates on:
 Delivery creation
 Delivery Goods Issue Delivery Goods Issue
 Inbound Delivery
 Real time visibility of Purchase Order specific “Stock In Transit” in receiving
l t l ith G/L d t f hi b i i C C dplant along with G/L update for ownership by receiving Company Code
 Standard SAP Transactions used to orchestrate the process
 Solution can be deployed across any SAP ECC 6.0 EHP4 and above ERP
systems
 Does not require the use of intermediate SAP SCM-APO system between
the SAP ERP systems
21
y
 NO SOURCE CODE MODIFICATIONS OF ANY KIND

 Reduced TCO, Highest First Pass Yield and Highest Quality from:
 Strong expertise in providing end-to-end Supply Chain Solutions
 Strong Expertise implementing SAP, enriching Business processes and
alleviating GAPs in SAP, for Life Sciences, Consumer Products, Chemical and
High-Tech Industry segments
 Very experienced consulting resource base with 13+ years experience andy p g y p
deep cross-functional expertise
 Rich Knowledge base of custom solutions to address GAPs in most SAP
applicationspp
 Ability to demonstrate end-state on Day 1 using in-house SAP Systems rich
with:
 Pre-configured SolutionsPre configured Solutions
 demo-able “Value Add” and “GAP Alleviating” SAP Functionality
 Demo-able IT Sapiens custom solutions
 Framework to develop strawman solutions
22
 Framework to develop strawman solutions
 Our “Say-To Do” Ratio is 1:1

Questions ?88
 For more information…kindly contact
Vijay Pisipaty
Director-ERP Solutions & Consulting
IT Sapiens, Inc.
e-mail: vijay.pisipaty@itsapiens.com

SAP-Cross System Stock In Transit Without APO

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to SAP-Cross System Stock In Transit Without APO

Similar to SAP-Cross System Stock In Transit Without APO (20)

More from Vijay Pisipaty

More from Vijay Pisipaty (20)

Recently uploaded

Recently uploaded (20)

SAP-Cross System Stock In Transit Without APO