aol

3/4/12 AOL « Dibyajyoti Koch:A Blog on Oracle Application

2/26imdjkoch.wordpress.com/category/oracle/oracle-apps/aol/

Here first DOWNLOAD the custom alert from the source instance, copy the ldt file to the new instance and thenUPLOAD to the destination instance.

Command to download:

FNDLOAD apps_user_name/apps_password 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alr.lctmy_file.ldt ALR_ALERTS APPLICATION_SHORT_NAME=’XXCUST’ ALERT_NAME=<Alert name

to download>

Here are some additional parameters that can also be passed are:

ALR_DISTRIBUTION_LISTS

ALR_LOOKUPS

ALR_MESSAGE_SYSTEMS

ALR_ORACLE_MAIL_ACCOUNTS

ALR_PROFILE_OPTIONS

ALR_PERIODIC_SETS

Command to upload:

FNDLOAD apps_user_name/apps_password 0 Y UPLOAD $ALR_TOP/patch/115/import/alr.lctmy_file.ldt – CUSTOM_MODE=FORCE

2] Using Alert Manager Responsibility:

You can use the Transfer Alert Definitions window to transfer an alert definition to another database, or make a copy of an

existing alert.

1. From the Menu, choose Tools > Transfer Alert.

2. In the Source Alert block of the Transfer Alert Definition window, enter:

* Application name associated with the alert to be transferred

* Alert name to be transferred

* Username and password for the database where the Alert to transfer resides



Enter the name of the application that will own the alert

Enter a suitable Name of the alert (up to 50 characters), and give it a meaningful description (up to 240 characters).

Select a frequency for your periodic alert. You can choose from nine frequency options:

1. On Demand

2. On Day of the Month

3. On Day of the Week

4. Every N Calendar Days

5. Every Day6. Every Other Day

7. Every N Business Days

8. Every Business Day

9. Every Other Business Day

Choose ‘On Demand’ frequency when you are developing a periodic alert so that you can test your alert at any time

you want. When you will sure that the alert is working fine, then you can change the frequency as per business need.

Depending on the frequency you choose in the previous step, the Start Time and End Time fields become enabled.

You may also specify the number of times within a 24-hour period that Oracle Alert checks your alert.

Specify a value in the Keep _ Days field to indicate the number of days of exceptions, actions, and response actions

history you want to keep for this alert.

Specify a value in the End Date field if you want to disable your alert by a certain date.

Enter a SQL Select statement that retrieves all the data your alert needs to perform the actions you plan to define.

Note:

Your periodic alert Select statement must include an INTO clause that contains one output for each column selected

by your Select statement.

Identify any inputs with a colon before the name, for example, :INPUT_NAME.



Identify any outputs with an ampersand (&) before the name, for example, &OUTPUT_NAME.

Do not use set operators in your Select statement.

You can use PL/SQL functions in your Select statement to fetch complex business logic.

Click on the ‘Verify’ button to check the select statement is correct.

Click on the ‘Run’ button to execute the Select statement.

Once you are satisfied with the SQL statement, save your work.

2] You can view all the input and output column details in ‘Alert Details’ Tab. 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.

3] After you define your alert you need to create the actions you want your alert to perform. For that click on the ‘Actions’tab.

Enter a name (up to 80 characters) and description (up to 240 characters) for your alert action.

Select a level for your action: Detail, Summary, or No Exception.



1. Detail action: performs once for each individual exception found

2. Summary action: performs once for all exceptions found

3. No exception action: performs when no exceptions are found.

4] Click on ‘Action Details’ tab to display the Action Details window.

Select the Action Type field as ‘Message’ if you want to send emails. Other action types are: Concurrent Program,

Operating System Script and SQL Script.Specify the electronic mail IDs of the recipients you want to send your message to in the To field.

If you list more than one recipient in any of these recipient fields, separate each recipient by a space, or a comma, ora combination of the two.

You can enter as many recipients as you want, up to 240 characters.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 whenreading the response.

Save your changes.

5] Click on ‘Action Sets’ tab in the main Alert Window.



Once you create your alert actions, you must include them in an enabled action set for Oracle Alert to perform

during an alert check. An action set can include an unlimited number of actions and any combination of actions.Enter a Sequence number that lets you order the execution of action sets during an alert check.

Give any suitable name and description.Check Suppress Duplicates if you want Oracle Alert to suppress the actions in this action set if the exception foundis a duplicate that occurred during the last alert check.

6] Click on ‘Action Set Details’ tab.

Go to ‘Members’ tab.Find and attach the action that is created in Step 3.

Save the changes.

7] Since it is an ‘On Demand’ periodic alert, we can run the alert at any time we want. For that go to Request > Check

and enter the alert details. Then click on ‘Submit Request’.



2] In Actions Tab, choose the type as ‘MENU’ and select the Menu Entry and give a Proper Menu Label.

3] Create the Concurrent Program which you want to attach to this custom menu item. Once created, assign the programto the Request Group of the Responsibility. Also it is required to add the ‘Lunch SRS Form’ Function (Requests: Submit)

to the main menu of that responsibility. If you don’t do this step you may get Form Personalization error in later steps.

4] Create one more entry in Form Personalization window with Trigger Event as your custom menu item.



Sample setting to debug everything:

FND: Debug Log Enabled YES FND: Debug Log Filename NULL FND: Debug Log Level STATEMENT

FND: Debug Log Module %

Sample setting to debug ONLY Receivables:

FND: Debug Log Enabled YES FND: Debug Log Filename NULL FND: Debug Log Level STATEMENT

FND: Debug Log Module ar%

Sample Program:

Create or replace PACKAGE BODY xx_debug_pkgAS g_level_statement CONSTANT NUMBER := fnd_log.level_statement; g_level_procedure CONSTANT NUMBER := fnd_log.level_procedure; g_level_event CONSTANT NUMBER := fnd_log.level_event; g_level_exception CONSTANT NUMBER := fnd_log.level_exception; g_level_error CONSTANT NUMBER := fnd_log.level_error; g_level_unexpected CONSTANT NUMBER := fnd_log.level_unexpected; g_default_module CONSTANT VARCHAR2 (240) := 'Any_Package_Name'; g_level_log_disabled CONSTANT NUMBER := 99; g_log_level NUMBER; g_log_enabled BOOLEAN;

PROCEDURE DEBUG ( p_log_level IN NUMBER, p_module IN VARCHAR2, p_message IN VARCHAR2, p_request_id IN NUMBER ) IS BEGIN fnd_profile.put ('AFLOG_MODULE', g_default_module);

IF ((p_module IS NULL) OR (p_message IS NULL)) THEN fnd_file.put_line (fnd_file.LOG, 'Error in package:' || g_default_module || ' , module : debug :Parameters p_module and p_message cant be null' ); ELSE BEGIN IF (NVL ((fnd_profile.VALUE ('AFLOG_ENABLED')), 'N') = 'Y') THEN

IF (p_message IS NOT NULL AND p_log_level >= g_log_level) THEN fnd_log_repository.init; fnd_log.STRING (p_log_level, g_default_module, p_message);



END IF; END IF; EXCEPTION WHEN OTHERS THEN fnd_file.put_line (fnd_file.LOG, 'Error in package: ' || g_default_module || ', module : debug, at check point 1 :' || SQLERRM ); END; END IF; EXCEPTION WHEN OTHERS THEN fnd_file.put_line (fnd_file.LOG, 'Error in package:' || g_default_module || ' , module : debug, at check point 2 :' || SQLERRM ); END DEBUG;END xx_debug_pkg;

Debugging an API from SQL*Plus

You can enable FND logging for just one single PL/SQL API. Here is how we can do it from SQL*Plus:

1. From SQL*Plus, issue the following:

fnd_global.apps_initialize(fnd_user_id, fnd_resp_id, fnd_appl_id);fnd_profile.put('AFLOG_ENABLED', 'Y');fnd_profile.put('AFLOG_MODULE', '%');fnd_profile.put('AFLOG_LEVEL','1'); -- Level 1 is Statement Levelfnd_log_repository.init;

2. Call the desired API.

3. Call step 1 again, but this time set AFLOG_ENABLED to N.

Since the debugging routine will start writing messages to the table, we want to know which messages pertain to our test. If

you are tracking the debug messages for a concurrent request, note down the Concurrent Request id. Otherwise, notedown current max value of log sequence retrieved as follows:

SELECT MAX(LOG_SEQUENCE)FROM FND_LOG_MESSAGES;

If you are debugging a concurrent process:

SELECT log.module , log.message_text messageFROM fnd_log_messages log, fnd_log_transaction_context conWHERE con.transaction_id = < request_id >AND con.transaction_type = 'REQUEST'AND con.transaction_context_id = log.transaction_context_idORDER BY log.log_sequence;

Otherwise use this:



[REPEAT_INTERVAL_TYPE=< resubmission type>] \[REPEAT_END=<resubmission end date and time>] \[START=<date>] \[IMPLICIT=< type of concurrent request> \[<parameter 1> ... <parameter n>]

The Parameters:

Parameter Name Required? Comment<username/password> Yes The ORACLE username and password that provides access to

the data that the program uses.

<responsibility application shortname>

Yes The application short name of the responsibility whoseconcurrent processing options to be used.

<responsibility name> Yes The name of the responsibility. If the name of the responsibilityincludes spaces, enclose that name in double quotes.

<username> Yes The uppercase username of the application user whoseconcurrent processing options to use.

<WAIT> No A flag that indicates whether to wait for the submitted request tocomplete. If one leaves this parameter out, the default value of

N makes CONCSUB return to the operating system promptwithout waiting for the request to complete. Set WAIT=Y tohave CONCSUB check the request status every 60 secondsand returns to the operating system prompt when the request iscompleted.

<CONCURRENT> Yes A flag that separates the program specific parameters from theoperating system parameters.

<program application shortname>

Yes The application short name of the concurrent program.

<program name> Yes The uppercase name of the program. It must be the short namethat was enter in the Concurrent Programs window whendefining a concurrent program.

<PROGRAM_NAME> No A descriptive name for your program.

<ORG_ID> No Introduced in R12, set to org id required for the report to berun with.

<REPEAT TIME> No The time of day to resubmit the request. The format for the timeis HH24:MI or HH24:MI:SS

<REPEAT_INTERVAL> No The interval between resubmission (a positive integer or realnumber). Use this parameter along withREPEAT_INTERVAL_UNIT to specify the time betweenresubmissions.

<REPEAT_INTERVAL_UNIT>No The unit of time used for the interval between resubmissions.The available units are MINUTES, HOURS, DAYS orMONTHS. Use this parameter along withREPEAT_INTERVAL to specify the time between

resubmissions.<REPEAT_INTERVAL_TYPE>No Whether to time the resubmission interval from the requested

start time of the request or from its completion. Set thisparameter either to START or END. The default value isSTART.

<REPEAT_END> No The date and time to stop resubmitting the concurrent request.<START> No A start date and time for the program in this format:



DDMONRR HH24:MI:SS (as in 07ϝϝAPR02 18:32:05ϝϝ)

Because this date format includes a space, one must enclose thedate in double quotation marks and single quotation marks.

<IMPLICIT> No Whether to show this concurrent request on the View Requestsform. Specify NO, YES, ERROR or WARNING. The value

IMPLICIT=NO allows the request to appear on the ViewRequest form. The default value is NO.

<REPEAT_DAYS> No The number of days after which to repeat the concurrentrequest, calculated from the last requested start date.

<parameter 1> …<parameter

n>

No The program specific parameters. If a parameter includes

spaces, enclose that parameter in double quotes, then in singlequotes. If a parameter contains a double quotation mark as partof the argument, precede that mark with a backslash [\].

Here is an example of the command to run CONCSUB:

$ CONCSUB APPS/APPS \SYSADMIN \System Administrator \SYSADMIN \WAIT=N \CONCURRENT \FND \FNDFMRTC \PROGRAM_NAME=Register Custom Tables Weekly \REPEAT_INTERVAL=7 \REPEAT_INTERVAL_UNIT=DAYS \REPEAT_INTERVAL_TYPE=START \START='"08ϝJUN96 23:55:00ϝ"'CGLAPPLSYSALLCGL

Notes:

1] For parameters that follow the CONCURRENT parameter and include spaces, enclose the parameter argument indouble quotes, then again in single quotes. Oracle Application Object Library requires this syntax because it parses the

argument string twice.

2] The above example uses the UNIX line continuation character ‘\’, not all operating systems support the use of thischaracter. If the line continuation character is not supported then the CONCSUB command should be submitted as one

continuous line.

3] COCNSUB is also used to shutdown the concurrent managers, however to start the concurrent manager you have to

use startmgr utility.

CONCSUB apps/apps SYSADMIN ‘System Administrator’ SYSADMIN WAIT=N CONCURRENT FNDSHUTDOWN

CONCSUB apps/apps SYSADMIN ‘System Administrator’ SYSADMIN WAIT=N CONCURRENT FND ABORT

4] The CONCSUB executable is located at $FND_TOP/bin/CONCSUB.



''||${item.MTL_TRX_LINE.SOURCE_TASK_NUMBER.value}||'',''||${item.MTL_TRX_LINE.EXPENDITURE_TYPE.value}||'',''||${item.MTL_TRX_LINE.EXPENDITURE_ORG.value}||'') from dual

Note that the variable in this case is written as “${item.MTL_TRX_LINE.ITEM.value}”. The text“MTL_TRX_LINE.ITEM.” is the Block and Field where the item number is written. The syntax around the block andfield name ensures that the callout is made to replace the value of the item before passing the text to the function. You canuse similar naming for your own fields finding the name of the Block and Field using Help > Diagnostics > Examine. Also

don’t put semicolon (;) after the statement.

Open the form that you want to personalize, then choose Help > Diagnostics > Custom Code > Personalize. In this

case, the miscellaneous transactions form is opened.

Enter the main information about when this personalization will be active.

Use the ‘Validate’ button to test if the syntax of your string is valid. If the evaluation fails, the processing engine will return

an ORA error as if the string had been part of a SQL expression. Otherwise, it will display the text exactly as it wouldappear at runtime in the current context.

Enter the action information detailing what the personalization will do. Here select the ‘Property Name’ as VALUE and

then put the above sql statement.



Unique ID Column: CATEGORY_ID

Comment: You must design and configure your Item Categories Flexfield before you can start defining items since all items

must be assigned to categories. You can define multiple structures for your Item Categories Flexfield, each structurecorresponding to a different category grouping scheme. You can then associate these structures with the categories andcategory sets you define.

4] Sales Orders

Flexfield Code: MKTS

Table: MTL_SALES_ORDERS

Unique ID Column: SALES_ORDER_ID

Comment: The Sales Order Flexfield is a key flexfield used by Oracle Inventory to uniquely identify sales order

transactions Oracle Order Entry interfaces to Oracle Inventory. Your Sales Order Flexfield should be defined as OrderNumber, Order Type, and Order Source. This combination guarantees each transaction to Inventory is unique. You mustdefine this flexfield before placing demand or making reservations in Oracle Order Entry. You must set up the OE: SourceCode profile option to determine the source code you will use in for the third segment of this flexfield to guarantee thateach transaction is unique. (Oracle Inventory defaults the value of the OE: Source Code profile option to ‘ORDER

ENTRY’.)

5] Stock Locators

Flexfield Code: MTLL

Table: MTL_ITEM_LOCATIONS

Unique ID Column: INVENTORY_LOCATION_ID

Comment: You can use the Stock Locators Flexfield to capture more information about stock locators in inventory. If youdo not have Oracle Inventory installed, or none of your items have locator control, it is not necessary to set up thisflexfield. If you keep track of specific locators such as aisle, row, bin indicators for your items, you need to configure your

Stock Locators Flexfield and implement locator control in your organization. This key flexfield supports only onestructure.

6] System Items

Flexfield Code: MSTK

Table: MTL_SYSTEM_ITEMS

Unique ID Column: INVENTORY_ITEM_ID

Comment: You can use the System Items Flexfield (also called the Item Flexfield) for recording and reporting your iteminformation. You must design and configure your Item Flexfield before you can start defining items. All Oracle Applicationsproducts that reference items share the Item Flexfield and support multiple-segment implementations. However, this

flexfield supports only one structure. You must set up your OE: Item Flexfield profile option to specify the ItemFlexfield structure that you will use for your Oracle applications. Users can also set up the OE: Item Flexfield EntryMethod profile option to specify your preferred method of entry for this flexfield.



Filed under AOL, Oracle Inventory Tagged with key flexfields, KFF, KFF in Oracle Inventory

← Older posts

Blog Stats

215,682 visits since May 2010

Live On!

Categories

AOL (39)APIs (11)Apps Tables (8)Architecture (9)Discoverer (8)

Forms (14)General Ledger (5)Interface (8)Java (1)Life (7)OA Framework (9)Oracle Inventory (8)Oracle Projects (8)

Oracle Workflow (3)Payables (13)Photography (18)Random Post (10)Receivables (10)Reports (9)



Script (17)Short Story (11)Simply Oracle (4)SQL*Loader (4)

SQL-PL/SQL (17)Technology (2)Travel (6)Unix (2)Xml Publisher (4)

Unique Visitors

Email Subscription

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 92 other followers

Sign me up!

Archives

February 2012 (4)January 2012 (2)December 2011 (4)November 2011 (1)October 2011 (2)September 2011 (10)August 2011 (10)

July 2011 (14)June 2011 (4)



May 2011 (17)April 2011 (11)March 2011 (6)February 2011 (3)January 2011 (7)December 2010 (10)

November 2010 (10)October 2010 (7)September 2010 (20)August 2010 (23)July 2010 (26)June 2010 (11)May 2010 (1)

Recent Comments

Dibyajyoti Koch on Steps to Create Report in Orac…

Shobha on Steps to Create Report in Orac…

Muzafar on My First Hello World Page in O…

sudhakar on SRW Package in Oracle Rep…

Query to find Projec… on Query to find Project Manager …

Dibyajyoti Koch on Alerts in Oracle Applicat…

Dibyajyoti Koch on Registering SQL*Loader as a…

Dibyajyoti Koch on Build simple search page in OA…

Useful Sites

Oracle DocumentationOracle IR

Oracle Metalink

Blogroll

In Depth AppsKnow OracleShare Oracle AppsSteven ChanSuresh VaishyaTanel PoderTom Kyte

Meta

RegisterLog inEntries RSSComments RSSWordPress.com



My Recent Posts

Playing with Dates in Oracle!Understanding the Workflow Definition (Set up) TablesAPI to add Classification to an Oracle ProjectQuery to find Project Manager Info of an Oracle ProjectFew Queries for Oracle ProjectsHappy New Year & 2011 in blogging!A Visit to Aga Khan Palace, PuneMax number in a Varchar column!

Top Posts Today

Triggers in Oracle FormsHomeBuild a Create Page in OAF!Summary column vs. Formula Column vs. Placeholder ColumnOverview of Procure to Pay Cycle in Oracle AppsHZ tables in Oracle ReceivablesVarious Canvas Types in Oracle FormAP invoice interface

Category Cloud

AOL APIs Apps Tables Architecture Discoverer Forms General Ledger

Interface Java Life OA Framework Oracle Inventory Oracle Projects Oracle Workflow

Payables Photography Random Post Receivables Reports Script Short

Story Simply Oracle SQL*Loader SQL-PL/SQL Technology Travel Unix Xml Publisher

Blog at WordPress.com.

Theme: Enterprise by StudioPress. Fonts on this blog.

aol

Technology

3 4 12 aoldibyajyoti koch

operating system prompt

n ielg n ieptln fdfl

miscellaneous transactions form

special menu item

key flexfield supports

lunch srs form

sales order flexfield