cancel
Showing results for 
Search instead for 
Did you mean: 

Automatic TO are not creating manuvally in background

Former Member
0 Kudos

Hi All,

We have configred the movemet type 309 and 321 with auto matic TO creation, after that we have schuduled a job (with program RLAUTA11)to create TO automatically , but for some of the posting changes TO es are creating automatically, but some of the posting changes TO are not creating and in the job log we found the error message"No quants exist for posting changes" message no : L3 094.

Could any one please kindly show the resolution for this issue.

Thanks & Regards,

Murali.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Answers (1)

Answers (1)

Former Member
0 Kudos

Please see the OSS notes 1004984 and 389492

this exactly explain your issue.

If you can not access the OSS than follow the help below

The goods receipt process has been completed so the quant no longer remains in the goods receipt interim storage type. It has been transferred from the dynamic bin created using the material document number and has been placed into the warehouse. Addition to stock is permitted in the destination storage type and the quant has been added to an already existing quant in the destination storage bin. As documented in Note 389492, the inspection lot data in the quant is not a splitting criteria so such quant mergers result in a loss of this data. Following the usage decision the system is unable to find the appropriate quants based on the inspection lot number.

Solution

The customising described in Note 389492 prevents quant mergers in the interim goods receipt area. However, if the stock is placed into the warehouse before the posting change notice is processed then quant mergers must also be avoided. The concept of avoiding loss of inspection lot data through mergers must be applied whenever the usage decision has not yet been processed by WM, not just in the goods receipt area. This can be achieved by the following methods:

Do not allow addition to stock in the destination storage type

Prevent placement into the warehouse from the goods receipt area until the usage decision and subsequent posting change notice has been processed. Documentation can be found in the SAP Library at path:

Logistics Execution -> Warehouse Management System -> Interfaces -> Interface to Quality Management -> Putting Away QM Relevant Material -> Putaway Before Usage Decision

The fourth processing option ignores the transfer requirement until the posting change notice has been processed. The IMG customising path is:

Logistics Execution -> Warehouse Management -> Interfaces -> Define Quality Management

It is possible to set this QM control for background processing which prevents any user intervention. If the putaway transfer order should be created automatically in the background then the automatic TO creation using report RLAUTA10 should be used. This report will ignore the putaway transfer requirement until the posting change notice has been processed. Documentation and the relevant customising can be found in the IMG at path:

Logistics Execution -> Warehouse Management -> Activities -> Transfers -> Set Up Autom. TO Creation for TRs / Posting Change Notices

If it is necessary to move the stocks out of the goods receipt area before the usage decision can be made then an alternative would be to use a destination storage type with placement strategy Q. The documentation regarding putaway strategy Q can be found in the SAP Library at path:

Logistics -> Logistics Execution -> Warehouse Management System -> Putaway and Picking Strategies -> Putaway Strategies -> Strategy Q: Dynamic Quant Number

An example of it's use would be to create dynamic storage bins for goods receipt as described in Note 389492, thus ensuring that no quant merger occurs in the interim goods receipt area. When goods are then placed into stock using strategy Q the quants are still not merged as they are placed into dynamic bins using the same number as the quant number. In this way quant mergers are prevented and the placement process can be carried out before the usage decision is completed.

Bear in mind that if the inspection lot control in the QM view of the material master is set to create different inspection lots for identical items in a material document then a quant merge in the goods receipt bin is inevitable, even with the customising from Note 389492. Such multiple identical items in a single material document should be avoided where possible.