Refer the general scenario followed most commonly in WM,

A) IN MM At the time of good receipt MIGO

1.creation of transfer requirement takes place. Material Goes to Interim Storage type (902)

2. Transfer order from TR is created ( we get destination storage type) -- In LT04 or LT06

3. Confirmation of TO.(Put away completed )

In LT12

B) IN PP

1. Requirement we get from MD11,MD04,CO01.(staging , BOM Explosion etc.)

this time Generally TR, will be created Automatically( As per setting).

With LB10 TR to TO

TO will be confirmed in staging process.(Quantity of picked materials will be reduced )

(Hear the raw material will be consumed. & TR for finished material will be created.)

With LB10 we can perform creation of TO.

TO for finished material will be confirmed when it will placed in the destination Bin.

Hear we will get the Finished good in the Unrestricted stock.

C)IN SD.

Creation of sale order: VA01

Creation of Outbound deliveryu2019s TO. VL01
TO confirmation after reaching to destination.LT03 then LT12 to confirm.

=================================================
=====================
Inbound Processing and Receipt Confirmation with WM
Purpose
You can use this business process for your inbound processing and receipt
confirmation in conjunction with Warehouse Management (WM). Whenever a
company requires a product to be procured from an external source of supply,
whether for use in production (raw materials) or for direct consumption (Cmaterials), the product will be delivered according to the official procurement
document (a PO) agreed between two business partners. The arrival of the goods
could be announced by a message of the supplier (ASN). It will be delivered in a
certain quantity at a defined date and time at a defined company location. For
the delivered product an inbound delivery is selected and processed for putaway.
Once the goods are taken into stock, a goods receipt must be posted.
The actual physical receipt of materials at the warehouse or the receiving
locations can be controlled on different levels of detail. From controlling the
process on a document level only using purchase orders and stock transports
orders to inbound deliveries and shipments and even to the pallet and material
level, the receiving process is supported in different ways. Depending on specific
customer needs, it is optional to use inbound deliveries and advanced material
flow and process control capabilities.
Inbound processing and goods receipts are key steps in any procurement or
replenishment process. It is not industry-specific, but common practice for any
company procuring products, whether for production of its own or direct
consumption.
Inbound processing reflects the receipt of materials that are delivered to a
receiving location. This receipt can be processed based on purchase orders,
stock transport orders, or even a returns order. It includes the notification of

goods to be received, the putaway, goods receipt posting, and the proof-ofdelivery message to the supplier. By viewing the goods receipt from two
perspectives, it is possible to follow the purchase order process and the physical
material movements separately.
The processes described are good receipt against a purchase order (MIGO) using
Warehouse Management and inbound processing using the inbound delivery, the
ASN message and the POD of the customer. The good receipt posting can be
processed prior to or after putaway of the materials. Both possibilities are
described as alternatives in the business process procedure:
Goods Receipt for Purchase Order
Goods Receipt Posting for Inbound Delivery after Putaway
If Handling Unit Management is used for packing, you must use in inbound
delivery to pack against. An inbound delivery is also required if the warehouse is
implemented in a decentralized environment (BAPI connection between
Warehouse Management and the ERP System).
Process Flow

1. Receive advanced shipping notification (ASN) (SAP ECC)

The arrival of goods procured and received is announced by a message of the
supplier to the goods recipient. This message is called Advanced Shipping
Notification (ASN) and it contains logistically relevant data, such as date and

time of delivery, material, quantities, and packing information. The ASN is

typically sent by the shipper of the goods. This can be the supplier (external
or internal) or a third-party logistics service provider (3PL). The message is
received by the ship-to-party and mapped into an inbound delivery in the SAP
R/3 system.
Alternatively, an inbound delivery can be created by the receiving party to
reflect the planning and coordination of the inbound delivery processing.
2. Create inbound delivery (optional) (SAP ECC)
When the actual shipment arrives, the inbound delivery is selected and
processed for putaway. The putaway can be processed with or without
Warehouse Management (see process Inbound Processing and Receipt
Confirmation).
3. Post goods receipt (SAP ECC)
When a required product is delivered to a company from an external source
of supply according to a purchase order, it must be integrated into the
companys stock and a goods receipt must be posted.
With this process description, you can also execute a goods receipt with
reference to a production order.
When a goods receipt is effected, the system supports:
Message determination
Depending on the settings in Customizing, the system initiates the
printing of a material document and labels, for example for pallets or
packages.
Missing parts check
For example, if a given product is identified as a missing part in
production, the MRP controller is automatically informed by mail that a
goods receipt for this critical product has been posted.
Purchase order history
The system updates the purchase order history, so that the purchasing
department can monitor that the goods receipt to the PO has been posted
and may check delivery date, time, and quantity. This information may
also be relevant for Vendor Evaluation.
Final delivery indicator
If information about final delivery is desired, the system sets the final
delivery indicator to inform the purchasing department that the last
partial delivery has been effected.
Material valuation
A goods receipt posting triggers an update of stock balance and stock
value. After a goods receipt, the system creates a material document
serving as proof of the goods movement and an accounting document to
initiate the update of the relevant G/L accounts. From goods receipt you
can display the material document and from there the accounting
document. When the product is valuated with moving average price, the
material price is updated according to the price in the most recent PO.
SAP APO update
If you work with SAP APO, the new SAP R/3 stock balance data updates
the SAP APO stocks, relevant for planning.

 SAP BW update
If you work with SAP Business Warehouse, new SAP R/3 stock balance
data updates user-defined figures in SAP BW, relevant for reporting.
Depending on special procurement processes (identified by specific PO item
categories), the consequences of posting a goods receipt are the following:
Consignment
The goods receipt is posted, but material valuation is not affected,
because the supplier still is the material owner.
Subcontracting
The goods receipt is posted and effects the withdrawal of material
components from special stock, necessary for the subcontractor to
assemble the final product.
For this business process, we will assume that all steps are carried out
manually. Many of these steps can be processed in the background for more
efficient processing, but it is important to understand which steps are
required within the entire process before you can automate it. The Goods
Receipt Posting can be processed before or after putaway of the materials.
Following the Goods Receipt posting for an external purchase order, materials
are located in the warehouse in an interim storage type of 902.
If Cross-Docking functionality is desired, see Cross Docking.
For further information on Warehouse Management, see Warehousing and
Storage.
4. Create WM transfer order (SAP ECC)
The transfer order is required to move the materials to their final storage
destination. It consists of items that contain the quantity of the material to
move and specifies the source and destination storage bins. The transfer
order logic finds an appropriate bin for storage based on configuration
settings in the warehouse customizing. The transfer order will list the source
(902) location as well as the destination location for the materials.
5. Confirm WM transfer order (SAP ECC)
The transfer order must be confirmed for inbound delivery items using the
Warehouse Management System (WMS). Upon confirmation of the transfer
order, the materials are available at their final destination. If the placement
logic is used, it searches for the Next Empty Bin, progressing through the
storage type search sequence as configured to find the next available place
appropriate to store this material.
6. Send proof of delivery (POD) (SAP ECC)
To report the actual received quantities, times, and dates of delivery back to
the supplier for invoicing, the message Proof-of-Delivery (POD) is sent.
7. Track and evaluate procurement process with SCEM (optional) (SAP SCM)
Optionally, the process Inbound Processing/Receipt Confirmation can be
monitored with the help of SAP EM. Since the visibility process Procurement
describes the procurement process for production materials, it spreads
Purchase Order Processing as well as Inbound Processing and Invoice
Verification. A detailed description on the visibility steps as well as the
configuration can be found in Procurement Visibility.

Procurement visibility covers

Events from purchase requisition to payment, including order
acknowledgement, shipping notifications, goods receipt, and invoice
functions
Triggering of follow-up activities
Analyzing the business process in the SAP Business Information
Warehouse (SAP BW)
The application process step relevant for this is: Monitor the fulfillment of
purchase orders.
All relevant intermediate steps are reported by the buyer (or supplier) so that
you get a complete picture of the application process:
Order acknowledgement
Advanced shipping notification
Goods receipt
ERS/invoice
Payment
Furthermore, some unexpected events may be posted:
Shipment delayed
Quantity change
Delivery quantity change
Due date change
Delivery date change
Deletion indicator set

Outbound Processing with WM

Purpose
You can use this business process for your outbound processing with warehouse
management (WM). Outbound processing comprises of the preparation of goods
to be delivered from a warehouse to a receiving location.
Outbound processing starts with an outbound delivery that has been created
either on the fly, or that is more typically based on reference documents such as
sales orders or stock transport orders.
Outbound processing in warehouse management typically comprises the
following activities:
The notification of goods to be supplied from a warehouse to a customer for
which the outbound delivery serves as the reference document
Picking (with the WM transfer order in this example)
Packing
Physical Goods Issue in warehouse (that is movement to the Goods Issue
Zone)
Loading
Goods issue and goods issue posting to Inventory Management (IM)
Advising of advanced shipping notifications to business partners
Obtaining a Proof of Delivery (POD) from the receiving business partner

Process Flow

1. Create delivery (SAP ECC)

The outbound delivery contains essential information to enable the
warehouse to meet outbound fulfillment objectives. It also contains business
partner information, data as to materials required and their quantities
ordered. The outbound delivery also stipulates delivery deadlines, delivery
points and conditions, mode of transport and delivery terms.
An outbound delivery is typically created based on a reference document,
such as a sales order (see also Sales Order Processing Process Master),

purchase order, and stock transport order, but may also be created on the fly
(that is without reference to a reference document).
In its role as central object of the goods issue process, the outbound delivery
supports all shipping activities including picking, packing, transportation, and
goods issue. During the outbound delivery process, shipping-planning
information is recorded, status of shipping activities is monitored, and data
accumulated during shipment processing is documented. When the outbound
delivery is created, the shipping activities, such as picking or delivery
scheduling, are initiated, and data that is generated during shipment
processing is included in the delivery. For more information, see Delivery
Creation.
2. Pick with WM transfer order (SAP ECC)
Based on the outbound delivery data and subject to the configured picking
strategies and activities, a pick transfer order (TO) is created that stipulates
which materials in which quantities are to be moved from which source to
which destination location. For example, a material required may be subject
to a Value Added Service (VAS) if so determined by applied conditions.
In the simplest case, this entails the movement from a storage bin location to
the Goods Issue Zone. A simple pick execution in a Handling Unit managed
warehouse could create a pick transfer order from a storage bin, assign a pick
handling unit, and then move the picked items to the Goods Issue Zone or
Area.
For more information, see Picking.
3. Pack (SAP ECC)
Packing the picked items and repacking is frequently required if, for example,
an outbound delivery mandates items to be picked:
Delivery items have either more or less quantity than the storage units of
these items in the warehouse
Delivery items of different material are to be packed together on to one
pallet for transport
The delivery quantity does not fit one pallet and needs to be split over
several pallets of equal quantity, with the remaining quantity to be
packed in a carton
Packing is part of delivery and shipment processing. When you process a
delivery, you can select delivery items for packing and assign them to
handling units. You could, for instance, pack delivery items in boxes, pack the
boxes on pallets for delivery to the customer, and load the pallets onto a
truck.
For more information, see the SAP Library under mySAP Business
Suite SCM Processes and Business Scenarios Generic SCM
Processes Warehousing Outbound Processing Packing.
4. Confirm goods issue in warehouse (SAP R/3 Enterprise).
Upon transfer order confirmation of the picked or picked-and-packed items
contained in the delivery to the Goods Issue Zone (916), Goods Issue is
confirmed. Upon Goods Issue, confirmation, and posting of the outbound
delivery is updated.
For more information, see Packing.

5. Load (SAP ECC)

The delivery items in the Goods Issue Zone can now be moved onto a truck
or into transport equipment, such as a container using an RF (LE-LMOB)
loading transaction.
Using an RF device, you can do the following:
Load handling units (HUs) on or unload HUs from a means of transport,
if you know the number of the shipment to which the HUs are assigned.
Load HUs on or unload HUs from a means of transport, if you know the
number of the delivery to which the HUs are assigned.
Perform system-guided loading. You enter a shipment number and the
system proposes the load sequence of the HUs assigned to it. In the case
of nested HUs, you can enter the higher-level HU, and the respective
lower-level HUs are loaded automatically.
Vehicle or transport equipment sealing activity is also supported.
For more information, see Loading.
6. Post goods issue to inventory management (IM) (SAP ECC)
Upon transfer order confirmation of the picked or picked-and-packed items
contained in the delivery to the Goods Issue Zone (916), Goods Issue is
confirmed and posted to Inventory Management (IM). Upon Goods Issue,
confirmation and posting of the outbound delivery is updated. As soon as the
goods leave the company, the shipping business activity is finished. This is
illustrated using goods issue for outbound deliveries.
For more information, see Goods Issue.
7. Send ASN to business partner (SAP ECC)
Following the Outbound delivery update based on loading confirmation, the
business partners (receiving customer, logistics service provider, and trucker
or shipping company) can receive an Advance Shipping Notification (ASN)
announcing the dispatch. It advises the impending arrival of the delivery. An
ASN can be either sent electronically by EDI, XML, or non-electronic means.
In the EDI scenario, you create a message with the delivery which is sent to
the customer via EDI as a shipping notification. On your side, the delivery can
be initiated automatically by a forecast delivery schedule from the customer,
for example.
An Advanced Shipping Notification (ASN) contains logistically relevant data,
such as date and time of delivery, material, quantities, and packing
information.
For more information, see ASN to Business Partner.
8. Receive POD from business partner (SAP ECC)
The receipt of a Proof of Delivery (POD) marks the end of outbound
processing and has the objective of confirming the arrival of the dispatched
goods and their associated conditions (damage, differences in orders
shipped, ordered, and so on).
A POD is also an instrument involved in business processes in which an
invoice is issued only after the customer has confirmed the delivery's arrival.
In addition to the proof of delivery itself, you can also record the POD date,
POD time, the actual quantity that arrived, and the reason for possible
differences in quantities. This is especially important for deliveries in which

the delivery quantity varies because of the nature of the goods or for which
the exact delivery quantity is unknown from the start.
You can record proofs of delivery in inbound deliveries for which your vendor
has sent shipping notifications and send them via IDoc. You have three
different options for recording differences and reasons for deviation:
Automatic creation
When you change quantities in an inbound delivery, the system
generates the POD data, including the difference quantity, and standard
reason in the background. In this case, you cannot change this data or
create other data manually.
Partially-automated creation
When you change quantities in an inbound delivery, an input screen
appears with the POD data that was generated by the system as
suggested values. You can use this screen to add other data or change
the reasons manually.
Manual creation
When you change quantities in an inbound delivery, an input screen
appears in which you must enter all POD data manually.
For more information, see POD from Business Partner.
9. Track and evaluate process with SCEM (SAP SCM) (optional).
Optionally, you can track and evaluate the process in the Supply Chain Event
Management (SCEM) as explained