Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from R. N. Wilhite on May 17 at 9:22 AM So, here's what we think is going to be our final answer (with notes on why
we came to this decision:
We BOL in a third party system. It then interfaces with SAP. BOL induces
our Invoicing. However, the systems don't have to be in sync and often are
slightly off. BOL indicates Picking occurred and should be posted in SAP.
But if we don't have inventory exactly right in SAP the Picking can't
happen and so on.
We use VL06O to see if something scheduled to have been picked hasn't been
invoiced. There should be less than a 10 minute delay if we are in sync.
We have some lines on the delivery that represent non-invoicable
components. In this case, CHEP pallets. If we don't exclude them, then
very many deliveries appear to have open lines. Too much to handle
manually. So we were looking for not billed, not CHEP. Now we will be
looking for Billable, not billed. We hope that will work.
Neal
| | | ---------------Original Message---------------
From: R. N. Wilhite
Sent: Monday, May 14, 2012 12:11 PM
Subject: VL06O Crashes Due to No More Memory - in SAP-DEV
VL06O is dumping. This happened suddenly. At the time that it dumps it is trying to fill an itab with VLPMA data. The problem is that though there are conditions in the select, none of them effectively limit the select. It is selecting 4M+ records.
So 4 days ago, it ran fine. Today it won't run at all. It also does the same in QA and DEV. Dev is a copy of Production from a year and a half ago.
There are no relevant notes. Lots of searching has turned up nothing. OSS says it runs as intended.
Any suggestions out there?
I'm going to post this in the SD forum as well...
Neal |
| Reply to this email to post your response. __.____._ |   _.____.__ |
