Navigate to the Alert Details window to complete the definition of your periodic alert. See: Specifying Alert Details. To create an event alert, you perform the following tasks in the order listed:. This section focuses on the first task of defining the database events that trigger your event alert and divides the task into smaller sub-tasks. In the Application field, use the list of values to choose the name of the application that owns the alert.
Specify the name of the application and the database table that you want Oracle Alert to monitor. Although the application you enter here need not be the same application that owns the alert, both applications must reside in the same Oracle database and the application that owns the alert has to have Select privileges on the tables listed in the alert Select statement.
Important: You cannot use a view as the event table for your alert. Oracle Alert submits a concurrent request to the concurrent manager when an event alert is triggered by an insert or update to an event table.
If you define an event alert on this table, you create a situation where the event alert will cause an exception to occur recursively. To enter a SQL Select statement for your event alert. Enter a SQL Select statement in the Select Statement field that retrieves all the data your alert needs to perform the actions you plan to define.
Your event alert Select statement must include an INTO clause that contains one output for each column selected by your Select statement. Your event alert Select statement must also include a join from the table where the event transaction occurs to an implicit input we call :ROWID.
Oracle Alert supplies the values for implicit inputs. If you want to send an alert message to that user, or use that user's email username in an action, simply select :MAILID into an output. Navigate to the Alert Details window to complete the definition of your event alert.
Once you define an event or periodic alert in the Alerts window, you need to display to the Alert Details window to complete the alert definition. The Alert Details window includes information such as which Application installations you want the alert to run against, what default values you want your inputs variables to use, and what additional characteristics you want your output variables to have.
With your alert definition displayed in the Alerts form, choose Alert Details. The Alert Details window that appears contains three tabbed regions: Installations, Inputs, and Outputs. The values of the implicit inputs are as follows:. You can optionally add a description for each input, but you must specify the data type either character, number, or date for the input, because Oracle Alert uses the data type to validate the default values for inputs you enter in the Default Values field and in the Action Set Inputs tabbed region of the Action Sets block.
Enter a default value for your input. You can enter up to characters. This value automatically becomes the default value for your input in each action set you define. Note: When you change an input value in an action set, you simply change the value for that action set. The new value does not get propagated as a new default value for other occurrences of that input. You can add meaningful descriptions for the outputs.
You can specify the maximum number of output characters you want to display in your detail or summary message actions. See: Formatting Summary Message Actions. You can also check the Check for Duplicates check box to customize the combination of outputs you want to verify as a possible duplicate exception each time the alert is checked. A duplicate exception is an exception that existed in your database during previous alert checks.
You can define Oracle Alert to perform certain actions based on the presence of these duplicate exceptions. Note: You must save history for your alert to use duplicate checking. You can select only those Oracle IDs that are associated with the application that owns your alert.
If you do not specify an Oracle ID in this region, Oracle Alert checks your alert against all installations in your database of the application that owns your alert.
If you have multiple organizations defined in your application schema, you must perform the following steps:. If you want your alert to run against several operating units of the multiorg schema, you must enter them individually in the Installations tabbed region.
Delete any records in this region that do not have a valid Oracle ID and operating unit. If it is set, then you must set the MO: Default Operating Unit profile value to a valid organization that you want the alert to run against in the Operating Unit field. If it is not set, then the MO: Operating Unit profile option should be set to a valid organization that you want the alert to run against in the Operating Unit field.
Please note that the MO: Security Profile profile option is to designate which set of operating units the event alert can be triggered. The MO: Default Operating Unit is to designate which operating unit will default the event alert to be triggered. If the MO: Security Profile profile option is set, then you must specify the default operating unit for the event alert to be triggered in the MO: Default Operating Unit profile. Once you finish specifying the details for your alert definition, you need to create the actions for your alert.
After you define your alert you need to create the actions you want your alert to perform. There are four types of actions you can create:. Enter a name up to 80 characters and description up to characters for your alert action. Select a level for your action: Detail, Summary, or No Exception. During an alert check, a detail action performs once for each individual exception found, a summary action performs once for all exceptions found, and a no exception action performs when no exceptions are found.
Depending upon the action level and type you choose, different fields appear in the Action Details window. To define message actions. Choose Message in the Action Type field of the Action Details window if you want the alert to send a message as its action. Specify the electronic mail IDs of the recipients you want to send your message to in the To field. You can also enter the IDs of recipients to whom you want to send "carbon" Cc and "blind" Bcc copies of your alert message.
If you list more than one recipient in any of these recipient fields, separate each recipient by a space, or a comma, or a combination of the two. You can enter as many recipients as you want, up to characters.
You can also enter in the List field, a distribution list that you define in the Distribution Lists window. See: Defining a Distribution List. If you enter a distribution list name, Oracle Alert displays all electronic mail IDs on the list in the To field, and does not let you change any values in the To, Cc, Bcc, Print For, or Printer fields. In the Reply To field, you can optionally specify the address that should receive the reply to the alert message.
This address must be either the reply-to address for the Workflow Notification Mailer, the e-mail address for a human in charge of response processing, or the address for a custom processing agent external to the notification mailer. If you leave this field blank, the Workflow Notification Mailer uses the value of its own Reply-to Address configuration parameter instead.
You can also have Oracle Alert print your message to the printer you specify in the Printer field. Enter in the Print For User field, the names, or alert outputs or response variables that represent the names of the recipients for whom you want to print a copy of the message. Separate the names by commas and do not use blank spaces within a name. Oracle Alert prints the message preceded by a banner page with the name as it appears in the Print For User field. You can enter as many names as you want, up to characters.
In the Subject field, enter a brief statement that describes the message's subject matter. You can also enter alert outputs or response variables in any of the alert detail fields. Oracle Alert automatically substitutes the associated output value when checking the alert or the associated response variable value when reading the response. By entering an output or response variable rather than a mail ID in a recipient field, you can make use of dynamic distribution.
See: Defining a Response Processing Alert. For a detail message action, you can either send the contents of a file as the message, or write the text of your message in Oracle Alert. If you want to write your message in Oracle Alert, choose the Text option and enter the text in the Text field.
You can also click on the Import button and import the contents of a file into the Text field. You can include any outputs in the message text.
If you want to send the contents of a file, choose the File option and enter the file name including the full path , or the output from the alert Select statement that represents the file name and location, in the File field. You may use any outputs to construct the file name. Note: If this message action has a response set associated with it, you must define the text of the message within Oracle Alert. For detail message actions, Oracle Alert distributes one message for each exception found during an alert check.
Place outputs wherever you need to in the message text, to format your message as you like. When Oracle Alert sends the message it substitutes the output variables with the exception values found during the alert check.
Oracle Alert reads the value for a response variable from the response message. If the response message does not include the response variable, Oracle Alert uses the default value from your response variable definition. For a no exception message action, Oracle Alert distributes a message when no exceptions are found for an alert check. Do not use outputs to define your no exception message and recipients.
Note: If you decide to change the Action Level of your action after entering message text in the Text field, you must delete the message text yourself.
Oracle Alert does not automatically delete the text for you. Important: For detail or no exception message actions, the message text that you specify for an event alert must be less than characters. This includes a limitation for the number of operating units that can be defined in the Installation tab.
The message file that you specify must be less than 32K. For information about defining operating units in the Installation tab, see Specifying Alert Details.
For summary message actions, complete your action details by following the instructions listed in the next section. When you are done defining actions, close the Actions and Action Details window and choose Action Sets to define the action set s for your alert definition. See: Creating an Action Set for an Alert. You can place outputs anywhere in the three parts of the summary message body: above the summary template in the opening text, within the Summary Message Template, and after the summary template in the closing text.
Enter the opening text of your summary message at the top of the window above the summary template. Use this area to enter any introductory text that you want to precede the columns in your message and to lay out your column headings. Tip: You can use any output values in the opening text of your summary message.
Use outputs like current date if you want to display the date that the exception was found in the introductory text of the message to avoid repeating the date as a separate column in the summary.
Leave the summary template lines exactly as you find them. Move the cursor between the two template lines and enter your outputs in this space, lined up below your column headings. You have up to spaces across in which to lay out your outputs, and you can vary this value by specifying a number of characters in the Max Width field. The number of characters your message displays for each output depends on the number of characters you allot for each output in the Max Length field in the Outputs tabbed region of the Alert Details window.
Oracle Alert defines the right margin of an output's column area as two spaces to the left of the next column. Oracle Alert left-justifies any character or date outputs within that output's column area.
For number outputs, Oracle Alert right-justifies the data within the column area. If the output in the rightmost column is defined as a number, Oracle Alert right-justifies the data in a column 15 characters wide. If the numeric data is wider than the column width allotted, Oracle Alert displays ' ' in the message. If you want to use multiple lines per exception, position your outputs on as many lines as you need, in the positions you want.
If you want a blank line between each set of exceptions, leave a blank line between your outputs and the lower summary template line. Enter the closing text below the summary message template. You can use any outputs in your closing text. If you define a header and footer, Oracle Alert adds it to every message constructed, including messages for which Oracle Alert is expecting a response. See: Defining Boilerplate Message Text. When naming an action set, do not use the words "Action" or "Set".
Relate the name of the action set to either the types of actions or the type of recipients. Try to limit the name to one or two words. When writing a distribution list description, do not use the word "List". Instead, use the description to fully explain the use.
Use the AD Splicer adsplice utility to register custom applications. If you wish to define alerts for a custom application, you need to register the installation of the custom application with Oracle E-Business Suite first. A custom application is any application that was not installed using AutoUpgrade and resides in the same database as Oracle Alert, or any application that resides in a database other than the one in which Oracle Alert is installed.
Before you can register an installation, you must first register your custom application. Navigate to the Define Application Installations form. Choose from the list of values in the Application field, the name of the custom application installation you are registering. Choose from the list of values in the Oracle Username field, the Oracle ID associated with this custom application.
If you are registering a custom application installation that resides in a different database, choose Oracle Alert's Oracle ID as the Oracle Username for your application installation.
Defining Boilerplate Message Text You can use the Message Elements tabbed region of the Oracle Alert Options form to define constant text that you want to appear in your message actions.
To define constant text in your message actions Navigate to the Oracle Alert Options form. Display the Message Elements tabbed region. There are four message text options that you can edit: Variable Description Message Action Header Standard text that appears in the beginning of every message action you define in Oracle Alert. Oracle Alert does not add a header to a message action that is an external file. Oracle Alert does not append a footer to a message action that is an external file. Response Text Standard text that instructs your message recipients how to respond to alert messages.
Oracle Alert appends this text to every message it sends that is associated with a response set. After appending this text to the end of the message, Oracle Alert lists the valid responses defined for the message. Oracle Alert supplies you with default Response Text; you can use this default text or modify it to create your own.
Returned Message Header Standard text that lets respondents know that their reply to an alert message was not understood, and that they must reply again. Oracle Alert adds this text to the beginning of every Return Original Message invalid response action. Oracle Alert supplies default Returned Message Header text; you can use this default text or modify it to create your own. Enter or edit the text for the selected option in the Text field below.
Save your changes. To define other miscellaneous options Navigate to the Oracle Alert Options form. Display the More Options tabbed region. Enter the value for the option in the Value field.
There are eight miscellaneous options you can modify: Variable Description Business Day System Use this option to select the method for determining business days.
The American system starts with Sunday and defines Monday through Friday as business days. The European system starts with Monday and defines Monday through Friday as business days. Concurrent Manager Name Use this option to specify the name of the concurrent manager. Concurrent Manager Startup Command Use this option to specify the name of the operating system command that starts the concurrent manager.
The default value is startmgr. Diagnostics: Message File Use this option to specify the full path and file name of the diagnostics message file.
The suggested file is called alrmsg , located in the bin subdirectory under your Alert directory. Diagnostics: Operating System Command Use this option to specify the operating system command used in operating system actions in the predefined diagnostic alerts.
The default value is ls. Maximum Summary Message Width Use this option to specify the maximum number of characters your printers can print across the top of a page.
Items become Installed Base trackable and Asset Tracking trackable across all organizations. Do not change this item attribute at the organization level. Additional Tracking Considerations The Installed Base tracking attribute of an item cannot be changed when on-hand quantity is greater than zero. Attribute changes are not applied to pre-existing transactions in the Oracle Asset Tracking record.
If you change the tracking attribute of an item from No to Yes, transactions that occurred before the change have no record in Oracle Asset Tracking. If you change the tracking attribute of an item from Yes to No, Oracle Asset Tracking no longer processes the pre-existing transactions. Depreciable Items Items that are trackable by Asset Tracking are defined as either normal or depreciable items. The difference between normal and depreciable items is in the way that assets can be created from the items.
For a normal item, the asset is created after an item is put in service. For a depreciable item, the asset is created when an item is received, either in Oracle Inventory or Oracle Projects.
For a depreciable item, you must define the item as depreciable at the master organization level only. For more details, see Define Depreciable Items. Serial Number Control You must designate serial number control for the trackable items at the master organization level.
This ensures that serial number control for an item is the same across all inventory organizations. You specify serial number control in the Inventory tab. Do not change serial control for an item after transactions have been entered. Additional Serial Number Control Considerations In Oracle Inventory, you may enter a miscellaneous issue transaction to remove all on-hand inventory, change the serial control attribute, then enter a miscellaneous receipt to restore the on-hand quantities.
During the process of correcting on-hand quantities, items that already have transactions are not affected. As a result records in Oracle Asset Tracking do not show the change in the serial control attribute. If the Inventory Item check box is not marked, you cannot store or move the item. These attributes let you enter and maintain costs for the items. Do not modify the Oracle Account Generator logic for deriving the depreciation expense account.
The depreciation expense account is derived from the book type corporate or tax and the asset category. Oracle Asset Tracking assumes that the depreciation expense account remains unchanged as a result of subinventory or inter-organization transfers.
Define Organization Classifications Oracle Asset Tracking tracks those inventory items which you have defined as trackable in Asset Tracking. Each module that interacts with Oracle Asset Tracking passes messages that contain specific information for all items that are marked as trackable in Asset Tracking. For these messages to be sent and received successfully, the organizations you define must have the following classifications: HR Organization Use to associate employees, such as buyers and planners, with items within the organization.
Inventory Organization Use to define, maintain, transact, and have on-hand balances for item numbers. Use to monitor the expenditures for a project and task by reviewing the account through Oracle Projects.
You use capital projects to collect construction-in-process CIP and expensed costs for assets you are building. When you are ready to place the asset in service, you generate asset lines from the CIP costs in Oracle Projects. You can send these lines to Oracle Assets to become depreciable, fixed assets. Therefore allow entry of capital project in your organization and issue material to the Capital Projects only.
You must specify any additional classifications you need for your organization. Defining Organization Parameters When you issue material to projects and tasks, all costs are initially charged to a project clearing account.
This account provides a convenient check point for tracking project costs. The organization parameters described below ensure that the costs associated to a project or task are passed to the clearing account for the Inventory organization that has been set up to own inventory items.
Use these steps to define organization parameters. Prerequisites You must define your organizations when you set up Oracle Inventory before you can define the organization parameters. To define organization parameters In the Inventory responsibility, navigate to Setup. Select Organizations and then select Parameters. Defining User-Definable Transaction Types Using the Inventory responsibility, you must define certain user-definable transaction types.
The following transactions must be defined to use Oracle Asset Tracking miscellaneous transactions. However, you must specify the source type and action as shown and select the Project check box for each of the transaction types required for Oracle Asset Tracking. To define user-definable transaction types Using the Inventory responsibility, navigate to Setup. Select Transactions and then select Types. In the Transaction Types window, click the User tab. Enter name, source type, action, and check box.
Defining Normal Items You must define an item master organization and at least one organization in Oracle Asset Tracking. To define normal items In the Inventory responsibility, navigate to Items and then select Master Items. In the Master Item window, enter the appropriate information into the header region of the window. Click the Inventory tab. Check Inventory Item. Stockable and Transactable are checked by default. Select the Service tab and check Track in Installed Base. Enter or select information in the remaining fields of the window.
Defining Depreciable Items You must define an item master organization and at least one organization in Oracle Asset Tracking. To define depreciable items In the Inventory responsibility, navigate to Items and then select Master Items. Select the Service tab and check Installed Base Tracking. Associating Subinventories to Locations Associate asset subinventories to a location. Use the Location field in the subinventory setup to link the deliver-to location of the item with its asset location.
Note: This is a standard setup step in Oracle Inventory. For more details, see the Oracle Inventory User's Guide. Defining Inventory Period Set the first inventory period. Make sure that you align this with the current period of the other modules. In the Inventory Accounting Periods window, in the first Period region, enter the current period.
Oracle Asset Tracking transfers only the Material cost element that is defined for the item to Oracle Projects. Define Shipping, Inter-Organization Shipping Use the Inter-Organization Shipping window to define accounting information and the relationships that exist between shipping and destination organizations.
You can specify whether an organization is a shipping organization, a destination organization or both. For more information see the Oracle Inventory User's Guide.
0コメント