Alerts in Sender File Adapter

phanikumar_akella · ‎09-17-2008

Hi All,

I have a File to File Scenario. Where Sender File Adapter will be polling for a file after every 2 hours.

I want to generate an exception if there is no file found for processing. Can you please suggest me the steps to achive this. Thanks in Advance.

phanikumar_akella · ‎11-13-2008

Thank you.

dharamveer_gaur2 · ‎09-17-2008

Use BPM wait step for 2 hrs.and if file not recieve by recieve step then trigger alert .

Former Member · ‎09-17-2008

Hi

Scenario 2: No files arrived till 10:00 AM. Now, I wish to generate an alert "No File Found in the poll Interval".

so for this you should use BPM the you had to use wait step and specify the time limit for 2 hrs ,then alert will be generated that file not found .

alert configuration i have already mentioned in previous reply .

Regard's

Chetan Ahuja

phanikumar_akella · ‎09-17-2008

Dear All,

I will explain it with an example.

Assume that the Poll interval set in Sender Adapter is 2 hrs.

Scenario 1: File arrived at 8:00AM and the File adapter has processes it. No issues...

Scenario 2: No files arrived till 10:00 AM. Now, I wish to generate an alert "No File Found in the poll Interval".

Is it possible using ALERT Configuration? If not suggest me some alternatives to achieve the same.

former_member183906 · ‎09-17-2008

Hii

Chk this blog by Michal,will help in alert config

http://help.sap.com/saphelp_nw70/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm

Almost same discussion in this thread for ur reference

Former Member · ‎09-17-2008

Hi

Defining Alert Categories

During alert category definition, you specify the alert text, expiry time, escalation, and all other conditions related to the sending of this kind of alert.

1. Ensure that you are in change mode in the alert category definition environment (transaction ALRTCATDEF).

2. Choose Create Alert Category.

3. In the Alert Category column, enter a technical key. Choose a key that describes the situation that triggers the alert, such as CUSTCANC for a category responding to a customer cancellation. This key is language-independent and identifies the alert category. The standard namespace convention applies to the key, this means keys Z* und Y* belong to the customer name space.

4. On the Properties tab page:

...

a. In the Description field, enter a description for the alert category. Choose a description that is informative with respect to the content of the alert category. The description is language-dependent.

b. If required, you can select a classification in the Classification field. If you do not choose a specific classification, the category is stored in the classification folder Unclassified. For more information on classifications, see Alert Classification.

c. In the Max. No. of Dels field, specify a maximum number of times that an alert of this category is to be delivered if it is not confirmed. This refers to delivery using a communication channel other than to the recipientu2019s display program (UWL, application-specific program, or alert inbox).

d. Select Dynamic Text if the texts of the alert category cannot be defined at this stage. This refers to situations in which the texts are not known until runtime, for example when CCMS Alerts are forwarded to ALM.

No translation can be performed for alerts with dynamic text. System messages can be entered manually in several languages.

e. In the Expiry Time in Min. field, you can enter a life span for alerts of this category if the alerts will no longer be relevant after a specific period of time. If the expiry time elapses, the alert is removed from the alert inbox and is no longer delivered using any other channel.

Expiry times can be derived from various sources. Priority is given first to the data provided by the triggering application, second to the BAdI ALERT_EXP_DATE, and third to this field in the alert category definition. If none is found in any of these sources, the default expiry of 31.12.2099 applies.

f. If you wish to specify an escalation recipient, select Escalation Active and enter the escalation recipient. Also specify a tolerance time in minutes. When escalation is active for an alert category, an alert is escalated if none of the alert recipients has confirmed the alert after this tolerance time. The escalation recipient is also informed that he or she has received the alert because of an escalation.

The escalation functionality is based on the administrator report RSALERTPROC. This report has to be scheduled as a regular job. For information on this report.

5. On the Container tab page, define any variables that you may want to use in the short text or long text. You can also define other application-specific variables, such as company code or material number. These variables are then replaced at runtime with values from the application. For more information, .

6. On the Short and Long Text tab page, enter texts for the alert category. You can include text variables referring to elements of the alert container or system symbols. In the case of a container element, the variable must be defined in the alert container. The entry in the text must be in the form &<ElementName>&.

The title is used as mail title, fax subject, and alert title in the inbox. The long text is used as mail/fax body and the long text view in the inbox. The short text is used for pager and SMS.

7. On the Optional Subsequent Activities tab page, you can enter URLs for subsequent activities. If you trigger your alerts by calling a function module, you can also specify dynamic subsequent activities. For more information, see Triggering by Calling a Function Module Directly in Triggering Alerts.

8. Save your entries.

You create an alert category to use in alert rules.

also you can refer the bleow mentioned links

Alert Inbox

http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm

Alert Notification Step-by-Step

http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm

Defining Alert Classifications

http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm

Triggering Alerts

http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm

Setting up alerts