Skip to main content

Stock Transfer Process - Inter Company process explained

Stock transfer process

Inter-Company process

If the transaction between two different plants of different company codes then this is considered as an intercompany transaction in SAP.Hence settlement needs to be done for the supplying company code so commercial invoice will be raised for receiving company.

Pre-requisites

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

Business process flow:

1.       Create  Stock transfer Order using ME21N with document type ‘NB’
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 Commercial Invoice using VF01 for outbound delivery using VF01
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)
11.   Create Vendor invoice using MIRO

Movement types used:

Ideally movement types will be determined from Schedule line categories which would be the basis for the generation of accounting document upon goods issue.

Inter-Company Transfer:  

One Step - 645

Two step - 643

Comments

Post a Comment

Popular posts from this blog

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.
Post a Comment
Read more

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button
Post a 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