Well, my answer was meant to be somewhat funny, but your observation is 
correct, 
things that "don't" happen are harder for COMPUTERS to deal with.  However, in 
my many years of experience with SAP and EDI in the manufacturing vertical, I 
have found that users are acutely aware of when they're "supposed" to get their 
data and of any reasons why they may not, resulting in a near zero false 
reporting and near 100% accurate recognition of problems they can't even see in 
SAP or elsewhere.

There is no true substitute for human cognition.

Leah





________________________________
From: Michael Mattias/LS <[email protected]>
To: [email protected]
Sent: Fri, October 22, 2010 10:04:32 AM
Subject: Re: [EDI-L] SAP Alerts for forecasting / scheduling agreements

  
>> Does anyone know if SAP has an alert process or adapter for customers 
>> setup on
>> scheduling agreements who don't send an EDI forecast on time or are late?
>> Please no sales or service emails, just a yes or no and what the service 
>> name or

> Well, it's not quite Friday, but, mostly, those would be "users".

It's not quite that simple, Mrs. H...

It's one thing to "do something"  when something *happens* .. eg, a schedule 
or forecast arrives.

It can be a bit trickier to "do something" when the dog does NOT bark.

If SAP has some kind of task scheduler subsystem, it would make perfect 
sense to use it to "check to see if we have received <something> from 
<someone>  within the last <some time period>  and if not,  do <something>.

I don't know if SAP has such a subsystem, or if it does it, that it supports 
"user defined tasks."

Ergo, I think Mr. Garwick's question is perfectly reasonable... and I also 
think it reasonable to ask in the context of this forum, since the 'event of 
interest' is the receipt and processsing of an ANSI '830' or EDIFACT 
'DELFOR' document.

(I know Windows' Scheduler or Unix 'cron' could be used, but I prefer to 
stay within the ERP system when possible).

Michael C. Mattias
Tal Systems Inc.
Racine WI
[email protected]
.


 


      

[Non-text portions of this message have been removed]



------------------------------------

...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to