Skip to Content
author's profile photo Former Member
Former Member

Stock Transfer from one plant to another plan but in the same warehouse

Hi SAP Experts

I have a scenario where I need to transfer the material from one plant to another plant of different company code but both the plants are assigned to same warehouse. So When we tyransfer the goods it does not move physically. We want the same Bin number and pallet number should be proposed at the time of recieving the goods as it was at the time of issuing the goods.

Also the Purchase Order is Intercompany and also it is subcontracting Purchase order. So it is a Intercompany subcontracting Purchase Orcer.So here we need to consume the Component provided to vendors also. I am sure few Expert must have faced this problem and solved also. Please suggest to me. Thanks in advance.

Best regards

Deepak kumar

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on May 03, 2011 at 08:04 PM

    In standard SAP WM you can solve the ownership change of the stock via posting change notice (PCN) (= you can manage the WM part of the process via PCNs). You can set in the storage type definition (V_T3010-KZUAP) that the stock should 'remain' in the same bin (there will be movments in WM but at the end the stock will be in the same bin).

    Storage unit number won't change.

    Please explore PCNs going through SAP online help:

    As for intercompany (cross company) STO with item category "L": the main item (parent material) behaves as any other item in normal STO. The components are managed in the same way as components in a PO with external vendor (the components are posted to special stock 'O' of the vendor assigned to supplying plant via mvt 541 and consumed later by mvt 543).

    It means it is not an integrated solution.

    Please explore it by testing in your system.

    Edited by: Csaba Szommer on May 3, 2011 10:04 PM

    Add a comment
    10|10000 characters needed characters exceeded

    • Yes, in case of im-mvt 301 you can use the PCN, however you cannot manage the subcontracting part of the process. Using STO you can manage the subcontracting scenario.

      I'm not aware of any standard setting through which you could solve the, it's very likely you should go for development.

      Possible solutions (just my dummy ideas):

      - Use one-step STO with delivery --> TO creation (removal) / bin block-unblock / TO creation (putaway) should be automized. (It means you should automize ~what the PCN does)

      - Use one-step STO with delivery with dummy main item (FOC non stock / non valuated material). GR would trigger auto MB1B + 301 (badi: MB_DOCUMENT_BEFORE_UPDATE interface: IF_EX_MB_DOCUMENT_BADI; method: MB_DOCUMENT_BEFORE_UPDATE can be used to trigger the 301 mvt. Dummy item with components enables to manage the components. In this case in WM no development is needed)

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.