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

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

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.

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...