Error L9 023 during VL10B

[girish_raj]

Dear Experts,

I have the below scenario.

Material is being  transferred between 2 plants. Material is of spares type (ERSA).
WM is active in both plants, but only for FERT materials storage location.

Storage location for ERSA is different, hence no WM applicable for them.

PO is created in the receiving plant. During  delivery creation in VL10B, we are facing L9 023 error.

Issuing Sloc is not warehouse managed & material is ERSA (No WM views).

What might be the reason behind this error, pls throw some light.

To add some input, if we are selecting different document type in PO (i.e UB - intracompany STO, via SD route), we are not facing this error.

Regards,

Girish

[JL23 · Accepted solution]

The error is based on the fact that the material has no warehouse views.

The storage location is determined from customizing task: determine picking location

Here you can only have multiple picking locations if use storage conditions.

If you do that in customizing, then check your material if the right storage condition is entered.

I am not sure what you want to tell with this part: To add some input, if we are selecting different document type in PO (i.e UB - intracompany STO, via SD route), we are not facing this error.

VL10B is SD route, more important would be to tell if you do one-step or two-step stock transfers. So it is unclear what you actually want to tell with this input.

What document type do you use in your PO?

To which plant belongs IN3 warehouse, I guess to the sending plant.

What info do you have if you open the folder in front of the message to the next level?

[girish_raj · Accepted solution]

Dear Jurgen,

Apologies for incomplete information.

After thorough testing we have arrived at the below situation-

System picks the storage location (irrespective of document type & material type) maintained in customizing node  Assign Picking Locations (table TVKOL). Here we have maintained the sloc as FG01 which is both warehouse & HU managed. (IN3 warehouse belongs to sending plant.)

But since the material being transferred is ERSA, which has no WM views, system tries to pick the material from this location & since it is not available, issues error message VL 412 & simultaneously this sloc data for material is deleted since it is not maintained.

Even though an error message is thrown, delivery is created in background which is updated in PO history as well.(Note 1790435)

Now the problem is in the below cases-

1. If the STO PO has an account assignment Q, then system issues error message L9 023 & not delivery is getting generated. Is there any config that we are missing? Also, we are not using Storage Conditions functionality. Can this configured to suit the material type & account assignment?
2. If the ERSA material is extended to WM & HUM storage location FG01 in MMSC by mistake, then also we are facing the error L9 023.How to undo the sloc extension?

Also, We are not using availability check functionality.

[Former Member · Accepted solution]

Hi Girish,

Thanks for the update!

The mentioned message VL412 'material does not exist in storage
location' does normally come up if the check for the storage location
is active and no material master record for this storage location
exists for the used material (table MARD).

If the 'check storage location' is not active for the used item
category no message should come up. You can deactivate the check in
the customizing of the item categories: transaction '0VLP'.

BR,

Enrique

[JL23 · Accepted solution]

it does not matter what material type the material has, material types do not control if a movement has to be posted in WM too. This is just controlled by the plant/storage location which is assigned to WM.

If you want send ERSA material from a different picking location, then you have to have a second picking location in IMG: determine picking location

And you can only add a second location if you differ by a storage condition. Hence create a storage condition "no WM" maintain it to all your ERSAs with MM17, add a record with this storage condition and a different storage location in determine picking location.

It is in general no foreseen to remove views from a material master. The only option would be marking  the location for deletion in MM06, and run archiving for MM_MATNR. But you need a modification to be able to archive a certain organisation level only, as the standard archiving can only archive a material entirely. This modification can be found as OSS note in Service Marketplace.

[girish_raj]

Many thanks Jurgen. Proposed solution of yours worked.

I maintained a storage condition based picking location determination.

one thing that I dint understand was how does account assignment Q has any relation with picking location? Why was the system throwing L9 023 error while creating delivery for this account assigned item?  Any info related to this is greatly appreciated.

@enrique: The solution proposed by you also works, thanks for throwing light in that direction too.

In this case, there would be too much config coz new item category should be defined, copy controls & mass maintenance of item category groups in material master.

[JL23]

Account assignment Q just means the stock is assigned to a project, but you have stock, no doubt. And if the picking location determination finds a location which is WM, then it just has to check if there is a WM view.

It is quite possible to manage special stock in WM.