INBOUND

Table of Contents

1 Process Flow Diagram..............................................................................................

2 Countries Use............................................................................................................
3 Transactions / Programs / Reporting / User Exits...................................................
4 Interfaces...................................................................................................................
5 Batch Jobs.................................................................................................................

1
1. Process Flow Diagram

2
2. Countries Use
All Sony Phoneix companies use Inbound.

3. Transactions / Programs / Reporting / User Exits.

Transactions Program Reports User Exits Description \ Comments
YL96 YLUPD047 Inbound delivery creation
Change/ Display Inbound
VL32/3
delivery
YW10 YMUPD210 Vendor Update Program
YW11 YMUPD074 Inbound Shipment creation
program

Inbound Shipment Planning Tool

The Purpose of this report is to

display a full document flow for
the selected Shipments. The
Purchase Order, Shipping
YW12 YMUPD212
Notification and Received
Quantities are also shown. The
report can also display any
documents associated with each
Shipment.

YMSN YMREP171 Inbound Shipment Planning

PO / Inbound Delivery date
N/A YMUPD307
alignment via output ZF03
VT02N Change Shipment
Inbound Shipment update for
N/A YMUPD215
output
VT70 SD70AV7A Issue Shipment output
YMT0 YMREP180 Monitor DESADV

Config
Process Step Key Description \ Comments
table
ZTYP2 001 /
YMUPD074 /
"SKIP_NOTIFIC
Inbound Shipment X to skip ship notes with an
ATIONS_W" /
Planning Creation existing goods receipt
TRANSPORTAT
ION PLANNING
POINT
ZTYP2 001 /
YMUPD207 /
Inbound Shipment Number of days uplift used in
"UPLIFT
Planning Monitoring YM97 for correction
CALCULATION
" / PLANT

3
 Inbound Ship note ZTYP2 077 / VENDOR / Control of auto ship note creation
Planning creation PURCH ORG via YL96
Inbound Shipment ZTYP2 187 / Default shipment type
Planning Creation COMPANY ZTYP2 187 controls the inbound
CODE / PO shipment type which is used for
TYPE the inbound shipment. Table keys
are Company code, PO type and
Item category. The table data is
the inbound shipment type. This
table is checked by transaction
YW11, program YMUPD074.

ZTYP2 377 / Name of program & variant e.g.

EXPECTED UPD207,ZEX1_STATUS_6, -
Inbound Expected
RECEIPT used to set status 6 on an
Planning receipt
OUTPUT TYPE outbound shipment after the
expected receipt output is sent
ZS000_066 SHIPMENT Holds number of days that
Inbound Expected TYPE / T.P.P. controls expected receipt output
Planning receipt ZEX1. Output is created if status
5 date is with nrdays of today
YL015 • Shipping notifications
created from LINCS (or
DVAI) processing and non-
STREAM replenishment
process are created without
vendor numbers assigned.
Default
Inbound The vendors are updated by
vendor for
Planning transaction YW10, program
YW10
YMUPD210. The vendor
update is carried out on the
basis of entries in table
YL015. Table YL015 can be
updated in the transaction
YW10.

4. Interfaces
Interfaces Information Output Idoc
Expected Details from R/3 to ZEX1 SHPMNT Outbound
Receipts from WMS detailing what
R/3 to WMS shipment, materials,
batches and quantities
will be received.
Actual Details from the 3rd SHPMNT Inbound
Receipts from party WMS detailing
3rd party what materials, batches
WMS and quantities were
received for an Inbound
Shipment.

4
5. Batch Jobs
The batch jobs set for inbound process are below:

 Inbound Planning Job

YXXXX_DI_INBOUND_PLAN

 PGR Job
YXXXX_DU_DELY_PGI

 Inbound Update Job

YXXXX_DI_INBOUND_UPDATE