Skip to main content

Stock Transfer process - Intra company explained

Stock transfer process

Stock transfer will be of two kinds:

1. Intra company
2. Inter company 

Intra Company process

If business requires transaction to be performed between two different plants of same company code. Then this considered as intra company transaction in SAP .Hence no billing document will be generated and if required proforma invoice will be raised.

Pre-requisites

1.       Supplying plant and receiving plant need to be created for the same company code
2.       Receiving sales line should be extended to supplying and receiving plant
3.       Supplying plant need to be maintained in supplying sales line
4.       Create customer in supplying sales area
5.       Shipping data need to be maintained for both supplying and receiving plant
6.       During shipping data maintenance customer need to be assigned to receiving sales area
7.       Supplying plant need to be assigned to Delivery type ‘NL’ and purchase document type ‘UB’
8.       Purchasing document type ‘UB’ need to be assigned to the combination of supplying and receiving plant
9.       One step or Two step process need to enabled at the combination of supplying and receiving plant
10.   Shipping point determination need to be done for both supplying and receiving plant
11.   Storage location determination need to be done for both supplying and receiving plant
12.   Material need to be extended to both plants

Business process flow:

1.       Create  Stock transfer Order using ME21N with document type ‘UB’
2.       Create Outbound delivery document with reference to Purchase Order using VL10B or VL10D
3.       Perform Picking and Packing using VL02N
4.       Perform Goods issue using VL02N
5.       Display stock in Transit ( Only in case of two-step process) using MB5T
6.       Create proforma Invoice using VF01 against outbound delivery ( If required)
7.       Create GST Outbound Invoice ( Applicable only in India)
8.       Perform Goods receipt using MIGO ( Only in case of two-step process)
9.       Upon completion of Goods Receipt stock in transit will be disappeared
10.   Create  GST Inbound Invoice document via Code   ‘J_1IG_INV’ ( Applicable only in India)

Movement types used:

Intra Company Transfer:  
One Step - 647

Two step - 641

Comments

Post a Comment

Popular posts from this blog

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more