Skip to Content
avatar image
Former Member

transfer posting for special stock Q

We are trying to do a transfer posting (movement type 309 Q and 311 Q) via t-code MIGO_TR.

Problem is the destination batch is not being created in storage location level.

Via normal stock this is working fine, but if we put special indicator Q, batch is not created at storage location level, only at plant level.

I am an abap consultant, and my functional is asking me to look for an exit that would automatically create the batch at stor loc level. But I would like to make sure there is no missing config to fulfil this,

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 15, 2015 at 09:00 AM

    check MB51 ( Material Document List).

    MIGO - TransferPosting:

    If it is plant to plant: Try this movement type 301Q and 309Q via Migo_TR.

    ( Go to OMJ8 ,


    Option: A,

    if you select plant - place a tick mark in empty box (storage location automatically created with respect to specified plant)

    Option: B

    if you select Movement type - place a tick mark in empty box (storage location automatically created with respect to Movement type)

    If it is stloc to stloc: Try this movement type 311Q and 315Q via Migo_TR.

    For better clarity I had mentioned below, please have a look.

    301 Q - Transfer posting plant to plant ( one-step )

    309 Q - Transfer posting project material to material ( Two-step )

    311 Q - Transfer posting Storage location ( One-step) - Project

    315 Q - Transfer posting sloc to sloc ( Two-step ) - Place in storage

    Thanks,

    Vivek

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Jürgen Lins

      yes initially not able to post. But functional changed some customizing, now able to post but no MCHB segment.

      Anyway, requirement cancelled as functional found other ways to monitor the batch. Thanks for all your info

  • Oct 15, 2015 at 06:27 AM

    is the target batch field a mandatory field?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      No Its not.

      If you do a check before posting in MIGO_TR, it would say

      Batch 'MaterialX' 'PlantX' 'StorLocX' 'BatchX' does not exist.

      If you check in MSC3N, the batch exist in Plant Level. If you do an MSC1N, and extend the batch to the Storage Location, the document will be posted succesfully in MIGO_TR.

      What we want is skip MSC1N step, and the create the batch automaticaly in Stor Loc level during transfer posting. Which is the case for normal stock