You are on page 1of 14

Intercompany Sales

Returns
February 26th, 2009

Bose | 2007 Proprietary

CONFIDENTIAL

Agenda

Meeting Objectives
Background
Finish Goods Returns Process
Parts Returns Process
Exception Process
Next Steps

Meeting Objectives
Review discussion points from meeting
held on 02/09
Agree on process to manage Finish Goods
returns and Spare Parts Returns
Review Exception Process

Background
The scope is limited to Intercompany Returns from
non-SAP subsidiaries to US or other SAP plant.
The SAP document used for the shipment is ZIS and
is currently created by the Mfg Planning group.
With the delay of D2 there is a need to define and
document the intercompany returns process from
non-SAP subs.
China is currently awaiting instructions to returns a
few thousands parts to the US.
During initial discussion it was decided FG returns
as well as parts returns should be able to be sent to
any plant (DC or Manufacturing). ASD returns will
continue using existing process using QN.
There is currently no exception process in place for
over or under shipments. 4

FG Returns Process
Shipment created
in Sub with RA #

Create RA in US

Product shipped to DRET

RA #

Return Order Processed


Credit Issued to Sub

Product received at DRET

HED Returns Process


HED Products returns from any non-SAP
subsidiary will be sent to DRET only.
An RA will be generated from the US by the
<Mfg Planning group>(SAP doc type ZOR) and
the RA# will be used with the shipment.
Upon receiving of shipment in Plant, the Credit
Specialist will create Return Order (SAP doc type
ZO) with reference to the RA.
Inbound delivery will be processed and credit
issued to the Sub for the non-defective
products.

Parts Returns Process


Shipment created
in Sub with RA #

Create RA in US

Parts shipped to
Destination
Plant

RA #

Return Order Processed


Credit Issued to Sub

Product received at Plant

Spare Parts Returns Process


Spare Parts returns from any non-SAP
subsidiary will be sent to any SAP plant (DC or
M plant)
An RA will be generated from the US by the
<Mfg Planning group> (SAP doc type ZOR)
and the RA# will be used with the shipment.
Upon receiving of shipment in DRET, the Credit
Specialist will create Return Order (SAP doc
type ZO) with reference to the RA.
Inbound delivery will be processed and credit
issued to the Sub for the non-defective
products.
9

Exception Process
The Exception Process will be used when an
over shipment or under shipment is identified
in the receiving Sub.
The process outlines the SAP transactions to
reconcile physical product quantity with
quantity recorded in the system.
In addition the process describes the steps
for scrapping product that was received
defective or damaged.

10

Exception Process Over Shipment


Sub receives
physical quantity

Contact shipping plant


for reconciliation

Contact customs to
report additional qty.

Increase Sales Order


qty for the additional
amount

RA #

Process ghost
delivery and PGI

11

Exception Process Under Shipment


Sub receives
physical quantity

Contact shipping plant


for reconciliation

Contact customs to
report additional qty.

Create ghost return


sales Order

RA #

Process ghost
inbound delivery
back into stock

12

Exception Process Scrap


Sub receives total
quantity

Inventory is inspected
for defective or
damaged units

Warehouse person
records scrapped units
in SAP and charges
Sub Internal Order

Scrap internal order


settles to I/C crosscharge account

Sub is notified and a


payable is recorded
in the Subs books.

13

Next Steps
Get approval on proposed process
Decide who will be responsible for
creating RA in SAP (Mfg Planning, other?)
Request SAP change to enable parts
returns to any plant (new order type?)
Roll out process to Subs and plants,
training, documentation.

14

You might also like