Skip to Content
author's profile photo Former Member
Former Member

Storage Location Control issue

Hello everyone,

I've come across a problem that I thoughtI could share and get your thoughts on it.

Basically, it's a simple storage location control process - standard.

My settings:
- Set up SLoc 0001 as standard.
- Set up SLoc 0002 as no copy to TR

- Set up storage location trigger - Parameters - My WhNum / Storage type 921 / My standard SLoc - 0001
- PCN creation - cumulative is unchecked - (pcn triggered on TO confirm) / mail control - express to my account / plant - default 0001

How things appear to work on the system:
- I create a movement from production SLoc (0003) to non-standard WM SLoc (0002) IM mv.type 311 - WM mv-typ 312 (this is OK)
- TR is created - SLoc is not copied into TR (this is OK)
- TO is created - it is created for standard SLoc 0001 - (this is OK)

- TO is confirmed - This Is Where The Problem Occurs
In the last step, because cumulative option is not checked, the system should create PCN automatically in background and post from 0002 to 0001 (in ST 921), but nothung happens. No mail - express message too ?! It seems to not be triggering it at all. If it trigerred it and it returned an error in bkgrd, it would have sent me an express mesage.

Even more weird, when I change the storage location control customizing to use 921 - 0002 (non-standard SLoc) - and mv-typ 311, and then repeat the process, all stock from ST 921 - SLoc 0001 get transferred to ST 921 - SLoc 0002 automatically. But I cannot reverse the SLoc's now since I have around 500 000 SSCC's at the moment in stock.

It doesn't add up to me, it should work different by default.
Am I missing something here?!

Thanks in advance,
Mihailo

EDIT:
I forgot to mention that by running report RLLQ0100 I can successfuly transfer stock from 0002 to 0001, it works fine, but I need the data to be processed at TO confirmation not by a bckg job...

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Nov 18, 2015 at 09:40 AM

    As per OSS note 311678 it would make sense of checking the queue in transaction SMQ1. If an error occured (and it was not handled) it can block all tasks which were created after the error had occured.

    This can be be one possible source of the problem.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Czaba,

      Thank you for your reply.
      That was actually the first thing I have checked upon finding out docs are not being processed.
      I had no tasks with problems in SMQ1 on production system.

      Further, in QAS system there were no entries in SMQ1 at all, but still the process fails for some reason.
      I have no more ideas where to look since customizing for this process is very limited and I'm not getting any ideas where to look.

      Not sure where in technical terms to look for problems since in functional side I can't find the reason.
      Maybe I need to debug and see what happens in background during TO confirmation and how the automatic posting works and why it fails to initiate...

      Not sure... still baffled... very simple process, which I implemented easily once without any problems, now gives a bad headache in this system...

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.