Skip to Content

QM-WM Integration - Error L3008 - System cannot find source storage bin

Hi gurus,

I'm trying to perform QA11 transactión, with some material placed in quants with stock status "Unrestricted use".

Expected behaviour:

When saving transaction QA11, the system should execute IM mov 333 / WM mov 331 and automatically create TO sending the material units to StoType 917 bin QUALITY.

Actual behaviour:

Whe saving transaction QA11, the system goes to LT04 transaction, and stops at Stock removal activity and brings the error mention in the tittle of this query:

The error leads me to this two pieces of standard code:

Program Found locations/short description

LL03AF0B 84 MESSAGE E008. 135 MESSAGE E008.

LL03AF1M 124 MESSAGE E008.

Which should be the steps to follow for both customizing and master data, to get propper behaviour of this activity?

Many thanks in advance.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Oct 10, 2017 at 12:25 PM

    Hello,

    Can we have the screen shot of B02 storage type what stock removal strategy it is assigned with?

    There is note which talks about this error.

    1622241 - Update Termination error L3008 in QA11

    This KBA explains that there might be missing storage type search sequence configuration and if you are transferring material from Interim storage type to Interim storage type, you will get an error L3008 as interim storage types have no stock removal strategies are assigned and hence system fails to find the source storage bin

    Best regards

    Shailesh Mishra

    Add comment
    10|10000 characters needed characters exceeded

    • Hello,

      My process is as follows:

      1) Good Receipt (EM). This include automatic inspection lot creation and automatic TR creation, when saving.

      NOTE: The process in the customer does not involve two line items in TR/TO neither special stock "Q" for the

      goods receipt. It sends all goods receipt to the specified bin with stock staturs "Unrestricted Use".

      2) LT04 to create TO W/reference to TR, to place the goods in Wh: 120/StoType: B02/Bin: R022/Quant: XXX

      3) QA11: To make usage decision (UD). As a result of this a material document is created, (which executes IMmov 333 + WMmov 331), and automatic TR is created to send the goods to Wh: 120 / StoType: 917 / BIN: CALIDAD. And TO should be created, but is not able to define "source bin" (THIS IS THE ERROR).

      Now I get to understand that the above mentioned customizing point, would lead me to split the quantities at GR time, in two item lines when it comes to TR/TO, right? One line item for goods to be placed in regular storage type/bin (B02/R022), and one line item for quantities to be sent to QA storage type/bin (917/CALIDAD).

      But I'm afraid this doesn´t meet customer expectations on the process.

      So it takes me again back to ground zero, when I'm doing QA11, and the TO w/ref to TR is not being created because "source bin cannot be determined".

      What do you think on this?

      Many thanks in advance for your kind collaboration.

      Best regards.

  • Oct 10, 2017 at 09:03 AM

    as you can see in your screenshot is the system looking for material in your storage type B02, but where are your quants?

    You should at least present a screenshot with your warehouse stock overview if you think this error message is wrong.

    This is already phrased by SAP in the long text of the error message, which you just copied.

    Wouldn't it be easier to just look into LX02, LS24 or LS26 instead of the coding from where the message is triggered?

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 10, 2017 at 09:40 AM

    Hi Jurgen,

    Many thanks for your prompt response.

    Kindly find attached what you have suggested. As you can see there is stock for the material 40033845 for Plant 1000, StoLoc 1200, Wh 120.

    LS26

    LS24

    LX02

    Many thanks in advance for your kind collaboration.

    Best regards.

    Add comment
    10|10000 characters needed characters exceeded