cancel
Showing results for 
Search instead for 
Did you mean: 

vl01n and vl31n

Former Member
0 Kudos

hi all,

may i know what is the difference for vl01n outbound delivery and vl31n inbound delivery?

i understand that vl31n is a confirmation as physical goods receipt in migo. so vl01n also a confirmation or physical goods delivery?

thanks

Accepted Solutions (1)

Accepted Solutions (1)

jignesh_mehta3
Active Contributor
0 Kudos

Dear Friend,

VL01N is used for processing Outbound Deliveries & posting Goods Receipts for Returns. It is a Delivery Document & the confirmation is received when you go post goods issue.

VL31N is used for Confirmation for stock transfer cases.

Hope this helps...

Thanks,

Jignesh Mehta

Answers (6)

Answers (6)

sarthak_mohantysd
Active Contributor
0 Kudos

Hello,

The basic difference between VL01N and VL31N are given as follows :

1. After successful creation of Sales order, we create Outbound Delivery by using the T-code "VL01N" using a shipping point. Here this process is followed up by Good issues where stock value of the material in the plant get deduced But in case of VL31N the scene is something different. When a vendor delivers a material which was raised earlier through a Purchase order then inbound delivery is done with this T-code "VL31N". Here this process is followed up by Goods Receipt by which the value of the material increases in the plant.

Regards,

SARTHAK

Former Member
0 Kudos

Hi,

Inbound Process

VL31n

Goods Receipt

Is a follow-on activity to a purchase order. It forms the basis for updating the financials and inventory records and can trigger warehouse management and quality management processes.

With the warehouse management system, you can control the goods receipt and goods issue processes at a physical level. Goods receipts are possible from purchase order, inbound deliveries (advanced shipping notice), stock transport orders, or from production orders. Goods receipt begins the putaway process, which is supported by different advanced strategies.

Determination of External Demands

Determines the data describing a demand for a material that is procured externally. This data includes the quantity that is required, the release-to-supplier date of the demand, the goods receipt date for the delivery, and the location to which the material has to be shipped.

Advanced Shipping Notification

Comes from the vendor and contains the exact materials, quantities, and the delivery date with reference to a purchase order. This document becomes the Inbound Delivery in the receipt process.

Delivery Monitor Provides an overview of deliveries in working processes. Gives an overview of the workload in different areas, for example shipping, transportation, or invoicing, while also allowing you to collectively process documents that have the same selection criteria. Specialists in different execution areas of the organization can use this tool to gain a quick overview of their workload, drill down to single documents, and trigger follow-up activities.

.

Outbound Process

VL01N

Goods Issue

The outbound delivery forms the basis for goods issue posting. The data required for goods issue posting is copied from the outbound delivery into the goods issue document. When you post goods issue for an outbound delivery, the following functions are carried out on the basis of the goods issue document:

Warehouse stock is reduced by the delivery quantity.

Value changes are posted to the balance sheet account in inventory accounting.

Requirements are reduced by the delivery quantity.

The serial number status is updated.

The goods issue posting is automatically recorded in the document flow.

Stock determination is executed for the vendor's consignment stock.

A worklist for the proof of delivery is generated.

After goods issue is posted for an outbound delivery, the scope for changing the delivery document becomes very limited. This prevents discrepancies between the goods issue document and the outbound delivery.

Delivery Processing & Distribution

Controls the actual fulfillment of sales orders and purchase orders as well as stock transport orders. The execution of logistics tasks is handled here. With delivery processing, the goods are shipped and relevant documents are printed out. The sales requirements can be distributed to alternative locations. The delivery might be shipped to the customer directly from the fulfilling locations (more than one delivery), or consolidation may occur at one location before one complete shipment is transported to the end customer.

Proof of Delivery

Proof of delivery (POD) is 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 POD itself, you can also record the POD date, time, actual quantity, and the reason for possible differences in quantities. This is especially important for deliveries where the delivery quantity varies because of the nature of the goods or for which the exact delivery quantity is unknown from the start. You are now in a position to issue an accurate invoice based on the customer's confirmation of goods received. You no longer need to create credit memos. The reasons for deviation that occur most frequently in real-world scenarios, such as stock shrinkage, theft, certain characteristics of goods (volatility, for example), and transportation damage, are recorded and analyzed in the system. This analysis is especially valuable when you are negotiating with forwarding agents, vendors, or customers, since all deviations can be reflected.

Value-Added Services

Value-Add activities in the warehouses need to be managed and monitored. Using the VAS functionality, you are able to manage and control the execution of services in the warehouse. VAS is fully integrated into Warehouse Management, Handling Unit Management, Task and Resource Management, and Mobile Data Entry.

Delivery Monitor

Provides an overview of deliveries in working processes. Gives an overview of the workload in different areas, for example shipping, transportation, or invoicing, while allowing you to collectively process documents that have the same selection criteria. Specialists in different execution areas of the organization can use this tool to gain a quick overview of their workload, drill down to single documents, and trigger follow-up activities.

Former Member
0 Kudos

hello, ASKCOMM! long time no hear.

VL01n is generally used for outbound deliveries. when creating deliveries using VL01n or when in edit mode using VL02n, you can post goods issue within these transactions (just by clicking on the 'post goods issue' button).

VL31n is intended for purchase orders which have confirmation control keys configured. also, since this is an inbound delivery transaction, the purchase order type must be relevant for inbound delivery.

regards.

former_member839993
Active Participant
0 Kudos

Hi

Basic difference between VL01N and VL31N is

VL01N-used for delivering the goods to the customer

used for taking goods into the system when returns take place

used to create receipt document using MIGO transaction

VL31N-used for Stock Transfers between plants.

regards,

US

Former Member
0 Kudos

Hi,

VL31N is used for Confirmation for stock transfer cases.

VL01N is for processing Outbound Deliveries & posting Goods Receipts for Returns.

Former Member
0 Kudos

Hi,

VL01N is Outbound process means goods issue to customer,where as VL31N is Inbound process means goods receipts to vendor.

First one is with referene to sales order and second one is with reference to purchase order.

In VL01N the stock in inventory management reduces once you issue the goods, where as in VL31N the stock in inventory management is added.

Regards,

Hari Challa.