Publishing event when error log is written

Cristiana D'Agosto cristiana.dagosto at au1.ibm.com
Tue May 27 23:41:40 EDT 2003


Hi John,
 
thanks for your help. Unfortunately the client wants it to be an Error and
not a Warning and they don't want to send a MAIL for every error, only for
BP 603 (Item #### Order #### budget exceeded).
 
Anyway, I couldn't figure out how the Mail is sent when I did set it to 2;
is it a TS? I couldn't find a log for it. I thought that perhaps I could
try to use a similar logic to solve my problem. Would you know?
 
Thanks for your help,
 
Cheers
 
Cristiana
 
 
 
 
 
"Soden, John" <John.Soden at newmont.com.au>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
27/05/2003 02:32 PM
Please respond to "SAP Workflow Users' Group"
 
 
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Re: Publishing event when error log is written
 
 
 
The responsible person is set in the 'Responsibilities' tab in txn CJ03
for
the WBS element
 
Another path to the tolerance settings is  SPRO > Project System > Costs >
Budget > Define Tolerance Limits (this takes you to the same maintenance
view)
 
Availability of 1 generates a warning, 3 generates an error, you should
see
different % values in the usage for these two entries. If you increase
your
tolerance limits you should be able to get around the time confirmations
error
 
-----Original Message-----
From: Cristiana D'Agosto [mailto:cristiana.dagosto at au1.ibm.com]
Sent: Tuesday, 27 May 2003 11:51 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Publishing event when error log is written
 
 
Hi John,
 
that looks interesting! I will try to find out who configured this part in
the IMG and the reasons why there are 2 entries for the profile; one of
the
entries has the availability control set to 1 and the other entry is set
to
3.
 
If I set to 2, how does the system knows who is the person responsible?
 
Much thanks!
 
Cristiana
 
 
 
 
 
"Soden, John" <John.Soden at newmont.com.au>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
27/05/2003 12:19 PM
Please respond to "SAP Workflow Users' Group"
 
 
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Re: Publishing event when error log is written
 
 
 
Hi Cristiana
 
You can actually configure the BP messages to be sent via email to the
responsible person for the project via 'SPRO > Investment Management >
Projects as investment measures > Planning and budgeting > Define
tolerance
limits for availability control' setting the 'Availability control action'
to
2 (Warning with MAIL to person responsible)
 
Cheers john
 
-----Original Message-----
From: Cristiana D'Agosto [mailto:cristiana.dagosto at au1.ibm.com]
Sent: Tuesday, 27 May 2003 8:28 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Publishing event when error log is written
 
 
Hello all,
 
still trying to trigger a workflow...We are in 4.6c.
 
Do you know if there is a way to publish an event / start a workflow when
an
error log is written?
 
If a time confirmation is entered against a work order that is linked to a
 
WBS element (via the additional data screen) and the calculated actual
costs
of the time confirmation exceed the budget amount for the object an error
is
produced.  The person entering the time confirmation (tx code
IW41) is able to exit out of the error log screen and is able to save the
confirmation. Whilst the confirmation has been saved the actual costs are
not
reflected in the work order's actual cost data nor are they represented in
any of the control reports available for the project. The problem does not
affect orders that have a reference to a WBS element in their settlement
rule.  However an error is generated and saved in an error log at the time
of
settlement (table AFRC - Incorrect Cost Calculation from Confirmation). It
is
a business and functional requirement for employees to be able to book
their
time to work orders.  It is not appropriate that the processing
 
of time confirmations be aborted as a result of the actual costs exceeding
 
the available budget.
I need for a workflow to be triggered when such an error occurs i.e.
trigger
a workflow when error BP 603 happens. The standard SAP delivered system
publishes AFVC_PM PARTIALLYCONFIRMED regardless if there was an error or
not.
I suppose I could trigger a workflow whenever AFVC_PM is published and
have a
FM checking if the workflow should start or not...(a bit ugly, isn't it?).
The error log can also be seen by running transaction code COFC. For Order
Category 'Network', SAP provides the option of triggering a workflow on
the
scenario that I described above by switching on a flag in SPRO (Project
Systems > Workflow > Configure Standard Tasks for Workflow in the Project
Systems. Unfortunately, for Order Category 'Maintenance Order', such
option
does not exist (SPRO > Plant Maintenance and Customer Service >
Maintenance
and Service Processing > Completion Confirmation > Define Control
Parameters
for Completion Confirmations). If else fails i.e. none of you can suggest
anything better!, I am thinking
 
of writing a program that will check table AFRC for errors and
SWE_CREATE_EVENT if applicable? Any ideas or suggestions are very
welcomed!!
Thanks and regards
 
Cristiana
 
 
Scanned by Newmont Australia Ltd. Anti Virus gateway
 
 
 
 
IMPORTANT NOTICE - By storing, copying, relying upon or otherwise using
this
e-mail, you agree to be bound by our Terms Governing Electronic
Communications. A copy of these terms can be reviewed at
www.newmont.com.au/eComm-terms.htm or obtained by phoning us on +61 8 8303
1700. If you do not accept these terms or suspect that you may have
received
this e-mail message in error, please notify the sender and promptly delete
this e-mail.
 
 
Scanned by Newmont Australia Ltd. Anti Virus gateway
 
 
 
 
IMPORTANT NOTICE - By storing, copying, relying upon or otherwise using
this e-mail, you agree to be bound by our Terms Governing Electronic
Communications. A copy of these terms can be reviewed at
www.newmont.com.au/eComm-terms.htm or obtained by phoning us on +61 8 8303
1700. If you do not accept these terms or suspect that you may have
received this e-mail message in error, please notify the sender and
promptly delete this e-mail.
 


More information about the SAP-WUG mailing list