Skip to Content
avatar image
Former Member

Valuation type in QMLR_BLOCKED_TO_FREE_STOCK

Hi All,

We have assigned two actions in action box to our QM notification. One allows to post 344 movement[Stock from Unrestricted to Blocked] and the other allows to post 343[From Blocked to Unrestricted.]

Material is valid for Split Valuation. Action of "344" movement is triggered successfully, but when trying to trigger "343" movement we get error# M7347 [enter valuation type]. There is no direct field in QM notification where, valuation type can be entered, also to my understanding it should be determined automatically.

Notfication type being used is "Q1".

Same movement from MIGO is posted successfully.

For posting of 343 movement type, FM# QMLR_BLOCKED_TO_FREE_STOCK is being used, and execution from SE37 also gives the same problem.

Please help in identfying the possible causes and how we can fix this.

Regards,

Avinash

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    May 31, 2017 at 02:27 PM

    I recommend you get with a developer and use debug to see the issue. The FM is clearly doing something different. If you look at the code of the FM it's clear it uses MB1B. Try using MB1B and see if you get the error.

    Craig

    Add comment
    10|10000 characters needed characters exceeded

  • May 31, 2017 at 03:44 PM

    why should a valuation type be determined automatically?

    If you work with batches, then the valuation type is a field in the batch record and you will not have a problem with the valuation type if this field is maintained and you enter the correct batch number in the function module.

    If you do not work with batches, then the valuation type is the batch number itself. Based on what info or customizing should SAP pick valuation type X if you have multiple valuation types? Did you do anything for that determination?

    Add comment
    10|10000 characters needed characters exceeded

    • Is it possible to set blocked stock inventory as non-valued across the board?

      I.e. when they move into blocked stock they write-off the value for all batches to zero value? So there is no need to select a valuation type?

      But when they move the stock back to unrestricted, they have to specifiy the valuation?

      I'm not sure why it would behave differently in MIGO unless in MIGO something gets defaulted in from say a PID value or something.

      But to debug, they need to run the same transaction the FM does. Which is not MIGO but MB1b.

      Craig

  • avatar image
    Former Member
    Jun 30, 2017 at 02:39 PM

    We created a FM, copy of "QMLR_BLOCKED_TO_FREE_STOCK" and made sure to pass "Valuation Type" in the Batch field.

    Add comment
    10|10000 characters needed characters exceeded