Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Rolling Time Zone- LETZ

Posted on January 10th, 2013 by Sanjit Anand ||Email This Post Email This Post

Timezone handling is bit tricky in EBS. Currently you may have only two options:

  1. Entering data in the standard corporate time zone as recommended by Oracle
  2. Entering data in their own local time zone and using a custom solution to resolve the issues that arise when comparing data across transactions in different time zones.

If your company/Client uses the second approach (entry in local time zone), enabling the user preferred time zone feature might result in unwanted date with time conversions (local date with times that are converted to the user preferred time zone) because the system assumes that all dates with time are stored in the corporate time zone.

If your company uses the standard corporate time zone for all business transactions, you can enable the user preferred time zone feature and have the choice to continue working in the standard corporate time zone as before, or to set your preferred time zone and start interacting with the system in your preferred time zone.

If you do not set the user level time zone preference, then the system will continue to operate in the standard corporate time zone as it always has, even though user time zone support is enabled for the implementation.

Lets discuss out-of-box LETZ feature.

Legal entity timezone(LETZ) feature will automatically report transactions in the relevant period .

In other word LETZ means that you can choose between recording accounting transactions according to a single worldwide reference location or by referring to the time zone of the legal entity involved. It means that you can select to have a rolling close, which allows you to close periods in relation to the local date, or you can continue to use a single world-wide reference when period close should take place.

This feature was introduced in 11i10 in Controlled Availability status and is also available on R12 – also in a Controlled Availability status.

arrow-up-3 Enbling LETZ

It required two simple steps to achieve this :

  1. Turn on and Set the ‘Enable Legal Entity Time Zone’ profile option to ‘Yes’ at site level.
    • Profile Option, ‘Enable Legal Entity Time Zone’, has been added and is available at site level only.
    • By default, this profile option is visible to the system administrator only. You will need to change its control access in the ‘Application Developer’ responsibility before it can be turned on.
  2. Set up the Time zone of the legal entity in HR Locations . Leave it blank for Non LETZ entities.

arrow-up-3How this works:


Conceptually, there are two types of date fields:

  • Dates with a time component – meant to indicate a specific point in time
  • Dates without a time component – meant to show a day but not a specific time

Majority of Finanancial Module , as consider as dates without time represent pointers to a financial period.

When the user preferred time zone feature enabled, date with time fields will be converted to the user’s preferred time zone.. That means if these profile setup :

  • ‘Server Timezone’ profile must be set at the Site level, and must be set to the same standard corporate time zone as the database
  • ‘Client Timezone’ profile must be set at the userlevel
  • ‘Enable Timezone Conversions’ must be set to ‘Yes’ (‘Y’) at the Sitelevel.


Example 1:

Lets assume ,

  • End user local timezone is GMT-6
  • Server timezone is GMT+8

Therefore , AR invoice date and GL date in AR Invoice Form is the date in server timezone (GMT+8), not end user local timezone.

whereas ship_date_actual in Sales Order form is in end user local timezone GMT-6, since it is a date with time and utilize the user preferred timezone feature.

Example 2:

Lets assume

  • Local timezone is GMT+9,
  • Server timezone is GMT-5

Invoice dates and GL dates are now based on the time zone of the legal entity from which goods are shipped ( end user local timezone), this would ensure that the invoice and the resulting revenue accounting is aligned with the localized GL period.

That means, when a sales order shipment is made from end user who based in Japan, on 01-Jan-2014 at 10:00Hrs, the invoice created in receivables with an invoice date of 01-Jan-2014.

Changes to support Legal Entity Time Zone have been made in Purchasing, Receiving, Inventory, Cost Management, Order Management and Process Manufacturing applications

arrow-up-3 Limitation

  • Legal Entity Time Zone features do not address encumbrance accounting transactions. Therefore you should not enable these features if you are using encumbrance accounting.
  • Oracle Reports do not display transaction dates/times in Legal Entity Time Zone, including internal reports which are used in the period end reconciliation process.
  • Legal Entity Time Zone has not yet been addressed entirely throughout Supply Chain Management (SCM).
  • Legal Entity Time Zone features do not address Periodic Costing, and Consigned Inventory Pay-on-Use Invoice Creation.
  • As per Oracle Note, in Oracle AR except for auto-invoice or debit memo documents created through upstream products such as Order Management and Procurement , all the dates for manually created transactions within Financials will be defaulted to the corporate time zone.
    • If the user wishes to enter a manual transaction and default certain dates (GL dates) in the context of the legal entity and not in the context of the corporate time zone (server time zone), the user will need to manually adjust the date and not accept the system defaulted date.

arrow-up-3 Limitation

Therefore when Implementaing , legal Entity Time Zone features make sure this does not changes to financial information, and therefore is recomendated

  • Work with Senior Finance person to determination as to whether the solution is correct for your company teams and get their buy-in.
  • Work with Oracle engagement team for Oracle Development approval for supporting LETZ. Remember this is still Controlled Availability status
  • Explore if you need to implement ‘User Preferred Time Zone’ along with LETZ.

arrow-up-3 Suggested Reading

Posted in AOL, Oracle Application | No Comments »

Localizations, Internationalizations, and Translations

Posted on October 8th, 2012 by Sanjit Anand ||Email This Post Email This Post

Do you know, Oracle’s E-Business Suite is used in over 150 countries.

In order to help global companies lower costs, drive compliant processes, and deploy country-specific capabilities to operate anywhere in the world, Oracle has developed 3 strategies called as localizations, internationalizations, and translations.

Localizations refer to functionality that is specific to certain regions or countries, usually based on regulations, legislation, or business processes in those regions/countries. You can refer to Country Specific Data Sheet for more details.

Internationalizations refer to products with the flexibility to be used worldwide with capabilities to allow for choice of locale (i.e. date format, currency, number format, etc.) and use with multiple languages.

Translations refer to changing the actual User Interface text of a module from English to another language.

Not all modules are translated into all languages, but with each release Oracle provides more and more translations.

dgreybarrow The difference

Internationalization and localization are different procedures.

Internationalization is the process of making software portable between languages or regions, while localization is the process of adapting software for specific languages or regions.

Internationalized software can be developed using interfaces that modify program behavior at runtime in accordance with specific cultural requirements.

Localization involves establishing online information to support a language or region, called a locale.These Locale are best understood as Date format, number format, currency, name/address order …etc.In EBS, Profile options control regional preferences (locale)

Whereas, in Translation, Translating product UI strings and Help from English to another language .

Posted in AOL, Oracle Application | No Comments »

Understanding Time Zone Features in Oracle E-Business Suite 12

Posted on October 6th, 2012 by Sanjit Anand ||Email This Post Email This Post

One unique aspect of a global implementation is that multiple locations may use the same system at the same time.

What if , You need to implement Timezones for each Legal entity like US, UK, Singapore and China in your Global single Instance.

Business transactions need to be accounted for in the correct period, in particular for financial transactions such as invoicing, collections,
etc. In addition, global instances with locations in vastly different geographical regions need the ability to close each location at period end in their own time zone.Therefore , you need to have understanding for Time Zone Features in EBS R12.

Date Fields in Oracle E-Business Suite can be classified under these broad categories

Transaction Date

This is Typically Date/Time which are associated as a part of transaction creation or maintenance.

Typical example in EBS context are Transaction date, Order Date, Shipment Date, service order effective date etc.

Accounting Date This is Typically GL Date. This date determines which Accounting period the transaction Accounting period the should be booked in.
Server (database) Date

This is dates that are primarily used in Data base operations.

Such dates are typically user to capture as Creation Date,Last updated Date

Standard Oracle provides three Time Zone features that can be used:

Server Time Zone

This determines the date and time on which Database dates are determined

In absence of Legal Entity Time Zone or User Preferred Time zone set up, this is the default time zone on which all date fields are determined

Legal entity Time Zone This determines the Accounting Date for certain in-scope transactions related to Accounting
User Preferred Time Zone This determines the time zone displayed for in-scope Transaction Dates
you can check out these two easy refrence note for more insights.
  • Doc ID 402650.1 -UPTZ User-Preferred Time Zone Support in Oracle E-Business Suite Release 12
  • Doc ID 726851.1 -LETZ (Legal Entity Timezone)

Posted in AOL, Oracle Application | No Comments »

“Signal 11” : Not So Scary Anymore..

Posted on March 11th, 2012 by Sanjit Anand ||Email This Post Email This Post

Signal 11’ is one of the most scary things in EBS developer/Apps DBA community . If you haven’t encounter yet , after working couple of years in EBS, that means you are quite lucky ..kidding

If you came from basic C programing skill, then you might be linking with malloc ..memory allocation , believe me, that is totally different.

In this post I will share some of the information which you need to know, rather than a creating a panic situation with developer or DBA .

dgreybarrow WHAT IS SIGNAL 11

In layman term, Signal 11 is an obscure way to say that there is hardware problem with the system’s memory

“Unaligned memory access” is a message coming back from the UNIX operating system letting you know that an Oracle executable has tried to access memory incorrectly. It’s not a problem with UNIX but is part of the operating system’s mechanism of protecting itself from crashing.

Chances are there you might get either of these ..Autoinvoice ,GLPPOS, GLLEZL, GLBMBO, APXXTR, GLNSVI, INCTGL , GLAMAS, ARZCAR, ARGLTP, RGRARG, GLCRVL,GLPAUTOP ,FADEPR – Depreciation, PDF Reports, XML OUTPUT


  • Not enough disk space in $APPL_TOP/out directory where the concurrent manager creates the report output files.
  • Lack of storage space in table spaces, rollback segments etc
  • Very complex SQL statements with many Group By columns (which may not all be required)
  • Incorrect OS permission’s
  • Parameter mismatches
  • The reports were FTPed incorrectly (ASCII instead of binary)
  • A ‘Numeric or Value error’ on some procedure code (although this may also cause a Signal 4 error). Typically this is because you have a field or variable which is too small to hold a value passed to it, which often happens when you are summing values.

dgreybarrow TECHNICALLY

  • All ‘Signal’ messages (there are between 15 and 36 different ones depending on the OS) mean that the OS is telling the current process that something has happened, or is ordering it to do something.
  • Take a example , when you do a ‘kill -9 <proc_id>’ on the server, you are actually sending a Signal 9 (SIGKILL) to that process.
  • Depending on the error, the running process can either ignore the Signal, exit gracefully, or exit and write a copy of its current memory stack to the filesystem
  • Core dump file is always unwanted.
  • Signals 6 (Abort), 10 (Bus Error), 11 (Memory Pointer Error) and 12 (Bad System Call) all fall into the last category and write a ‘core’ file.
  • Signal 11 is : “Process asked to be allocated <x> Bytes of memory, but is now trying to access an address which is not within that allocation or is trying to access a null address”.
  • This may be caused by code or data problems.

You usually find, windows equivalent of a Signal 11 error is when a process terminates with ‘Error -1073741819’


  1. First thing to look at is the last few lines of logfile – preferably with Debug on
  2. Searching that you might find in log file, chances are high you will get some node at metalink. if not
  3. Check with your apps DBA , pass the information , he will try to Analyze/diagnosis and advice.
    • what he will do, he will try to locate core file which got is written to the directory from which the executable was called.
    • Take a note,after a Signal 11 error has occurred, the program may write a dump of itself to $<product>_TOP/bin
    • The ‘core’ file which got located is just a dump of the memory occupied by the program at the time of failure, and as such is not easy to read.
    • they need some utilities to produce a readable output. DBA typically used these utilities adb, dbx, xdb, gdb,
  4. If nothing get solved Quickly, raise a SR with Oracle.

Meantime , you can also check the list of unix signals with their explanation in note id 1038055.6

Posted in AOL | 1 Comment »

Its all about globalization (formerly internationalization) support in Oracle E-Business Suite

Posted on October 8th, 2011 by Sanjit Anand ||Email This Post Email This Post

For company operating in multiple countries and have Single Global Instance, may have to understand the features of globalization (formerly internationalization) support in Oracle E-Business Suite. Things which is covered under internationalization are:

  • Unicode Support
  • Multilingual Support (MLS)
  • Regional Preferences (Locale) :Date format,number format,currency,name/Locale, support address order …etc.
  • Calendars
  • Currencies
  • Timezones
  • Address Management
  • Single, Complete Data Model

dgreybarrow Oracle EBS & National Language Support(NLS)

NLS setting gived ability to run in a language other than English and have ability to use date, number, and currency formats specific to certain country or region

Sometimes referred to as Locale , in EBS sometime you heard NLS patches…these are special patches that provide language translations including user interface labels, menus, and some Oracle seeded setup data.

dgreybarrow Oracle EBS and Unicode Support

Unicode is a universal character set which includes all major scripts of the world in a simple and consistent manner

  • Oracle database supports two Unicode character sets:
    • AL32UTF8: based on latest Unicode standard, currently 5.0
    • UTF8: on maintenance mode and supports Unicode 3.0 standard

Take a note, AL32UTF8 is the default Unicode database character set for Oracle EBusiness Suite installation in R12.1 when multiple languages are selected, where in 11i and R12 earlier had UTF8

Moreover ative character sets are still supported in EBS.

Oracle encourage to covert to AL32UTF8, as its support more characters and languages.

Fusion Apps will only support AL32UTF8 character set.

Those who is potentially looking for move to AL32UTF8 can explore Oracle Database Migration Assistant tool to provide an end-to-end
solution for migrating your databases from legacy encodings to Unicode

dgreybarrow Oracle EBS and Multilingual Support (MLS)

That means Oracle E-Business Suite supports running multiple languages on the same instance simultaneously

Any number of supported languages (aka NLS patches) can be installed in a given instance

This Supports 34 languages covering 92 countries.

  • American English, Arabic, Brazilian Portuguese, Canadian ,French, Croatian, Czech, Danish, Dutch, French, Finnish,German, Greek , Hebrew, Hungarian, Italian, Indonesian,Japanese, Korean, Latin American Spanish, Lithuanian,Norwegian, Polish, Portuguese, Romanian, Russian, Simplified Chinese, Slovak, Slovenian, Spanish, Swedish, Traditional Chinese, Thai, Turkish, Ukrainian, and Vietnamese

Indonesian,Lithuanian,Ukrainian, Vietnamese are new in R12.1

you can enable Languages via License Manager Page.

When MLS is enabled you can notice the number of rows in Base Table(xxxx_B) and Translation Table (xxxx_TL)

Base table row contains language-independent attributes

That means for each row in base table, N rows exist in translation table corresponding to the N installed languages

One row for each installed language contains translated textual attributes

dgreybarrow Regional Preferences that we call as Locale

These are typically consist of

  • Profile Settings :Some of the regional preferences (locale) is controlled via Profile . The setup can be done by administrators at various level like Site,Application,Responsibility & User. Setup for aech user can override default setting with preferred values
  • User Preference Page

User Prefrence

  • Site Level Profile Options :ICX: Client IANA Encoding is used for IANA character encoding determines character set of HTML based
    UI on client tier (Browser), this should be set to an IANA encoding equivalent to database character set. Recomebded is to set at site level
  • User Level Profile Options : These are the some
    1. ICX: Language : This is defaulted to application language if no language is selected at login time. This profile determines language of email notifications, which can also be set to user’s preferred language
    2. ICX: Territory : This profile should be set to user’s territory (country), if this correctly setup , then it is used in conjunction with language code to pick the correct translation resources such BI Publisher templates .
    3. Client Timezone : R12 of Oracle E-Business Suite includes as standard a feature called User-Preferred Time Zone Support. In most existing E-Business Suite implementations, all users interact with the system in the “corporate time zone”, which will normally be the time zone of the headquarters of the implementing company, and the time zone in which the database runs. This means that remote users have to be aware of the time difference between their location and that of the corporate headquarters.This should be set to user’s Timezone.

      Users see date-with-time fields in their preferred (local) time zone, and can enter dates with time in this time zone.

      The data in the database continues to be stored in the standard corporate time zone

    4. FND: NATIVE CLIENT ENCODING : This is used to set the client (user) PC encoding, this also determines character encoding of file name and content. The will be used while exporting/importing spreadsheet data, uploading/downloading text files. Its Recommended to use the pre-set default value
    5. ICX: Date format mask : This can be set to user’s preferred date format
    6. ICX: Numeric characters : This is used to get any of these support combination.
      • Comma / period (10,000.00)
      • Period / comma (10.000,00)
      • Space / comma (10 000,00)
      • Space / period (10 000.00)
      • Single quote / comma (10’000,00)
      • Single quote / period (10’000.00)

dgreybarrow International Calendar Support

R12.1.1 support Arabic Hijrah(The official calendar in Saudi Arabia with Arabic Hijrah month names ),English Hijrah(The official calendar in Saudi Arabia with English transliterated Hijrah month names). Users can choose their preferred calendar.

Hope this post helps to understand the latest internationalization suppport for Oracle EBS.

Posted in AOL, Oracle Application | No Comments »

What Is Extensible Attribute Architecture?

Posted on June 13th, 2011 by Sanjit Anand ||Email This Post Email This Post

Extensibility framework and features basically comes from Oracle Product Lifecycle Management (PLM).

Extensible Attributes are similar to DFF’s in the sense that Extensible Attributes feature provides out-of-the box capability to store additional information associated with certain EBS modules entities.In the past, Oracle Descriptive FlexFields (DFF) had a limitation of 15 or 22 data fields per record. There is no limit for Extensible attributes.

The functionality allows you to view and maintain these additional attributes without having to create custom screens. It also allow you to group related attributes and display attributes on specific UI pages.

dgreybarrow R12 Extensible Attributes –What are they?

  • Extensible attributes add additional rows or records into the database structure and therefore are limitless.
  • Extensible attributes can contain one single record (of numerous extended. data fields) or multiple record
  • The extended database fields have four data types to choose from and can contain list of value (LOV) definitions for data consistency (entry and reporting) and can control record inserts to be based upon uniqueness (no duplicates)

dgreybarrow In Comparison to Descriptive FlexFields (DFF)

Here are the quick comparision with DFF.

Extensible Attribute

dgreybarrow Some of the features are

  • Limited to certain EBS modules entities.
  • Attributes can be displayed as text, check box or radio group.
  • Database view is created for each attribute group.
  • Uses Value Set for attribute validation.
  • Extensible Attributes store unlimited number of repeating attributes (multiple rows of similar data), unlike Descriptive Flexfields.

dgreybarrowComponents of an extension:

  • Attribute Group
  • Attributes
  • Associations
  • Pages
  • Functions
  • Actions
  • Value Sets (Recommend creating before attribute groups)

Extensible entities have corresponding tables to store additional attributes.

For example, in the case of Teleservice some of the tables are CS_INCIDENTS_EXT_B, CS_INCIDENTS_EXT_AUDIT, etc.

If customer wants to use Extensible Attributes in Oracle Loans then you need to check with Loans Development to see if they implemented or not Extensibility framework.

Will see more details for TCA Extensible Attributes, in next post.

Posted in AOL, Oracle TCA | No Comments »

EBS Concurrent Manager

Posted on November 30th, 2010 by Sanjit Anand ||Email This Post Email This Post

Concurrent program are the batch Processing Sub-System. These programs are run as operating system background processes.These programs may be written using a variety of Oracle tools, programming languages for executables, or OS scripts.

  • The Internal Concurrent Manager (ICM) controls all other concurrent managers. It administers the startup and shutdown of managers as defined by their work shift, monitors for process failure, and cleans up if a failure occurs.
  • The Conflict Resolution Manager (CRM) enforces rules designed to ensure that incompatible concurrent requests do not run in the same conflict domain.
  • The Standard Manager as shipped with Oracle Applications will accept and run any concurrent requests.

dgreybarrowConcurrent Manager – Tables

Here are the list of table assocaited with concurrent programs.

Table Content
FND_CONCURRENT_REQUESTS Details of user requests, including status, start date, and completion date
FND_CONCURRENT_PROGRAMS Details of concurrent programs, including execution method, whether the program is constrained, and whether it must be run alone
FND_CONCURRENT_PROCESSES Cross-references between concurrent requests and queues, and a history of concurrent manager processes
FND_CONCURRENT_QUEUES Information about each of the concurrent manager queues

dgreybarrowConcurrent Request – Lifecycle

Here are summary for concurrent prgram phases in a typical lifecycle of concurrent program.

Phase Activity
Pending / Normal The request is waiting to be run
Pending / Standby The request is waiting at CRM
Running / Normal The request is running
Completed / Normal The request has finished
Inactive / No Manager The request cannot be run. No manager available to process it.

dgreybarrowSimilar Post on Concurrent Program

Posted in AOL | No Comments »

Output Post Processor – OPP – Troubleshooting 2 common issue

Posted on November 28th, 2010 by Sanjit Anand ||Email This Post Email This Post

Before getting insight on two common issue , read this post on “Output Post Processor – OPP

dgreybarrowI S S U E # 1: This error often you get.

The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status.


  • You need to set the Profile Option “Concurrent: OPP Response Timeout” to a higher value may be necessary.
  • If the value of the Profile Option „Concurrent:OPP Response Timeout. is 120 then increase it to 240. (Value * 2).
  • Increase the number of processes or threads (or both) .


dgreybarrowI S S U E # 2 :Program end-up with this error.

The Concurrent Manager has timed out waiting for the Output Post Processor to finish this Request.
Check that there are enough Output Post Processor Service Processes running. More information may be found in the Service Process logfile.


  • You need to check the Profile Option “Concurrent:OPP Process Timeout”.
  • Increase the setting to a higher value.

For example: Set the value to 10800 sec (3 hours). After this change, the Concurrent Request will wait maximum 3 hours, for the Output Post Processor to finish the Request.


hope this helps.



Posted in AOL | No Comments »

Output Post Processor – OPP

Posted on November 2nd, 2010 by Sanjit Anand ||Email This Post Email This Post

Concurrent Processing uses the Output Post Processor (OPP) to enforce Post Processing actions for concurrent requests.

The Output Post Processor (OPP) is an enhancement to Concurrent Processing and is designed to support XML Publisher as post-processing action for concurrent requests. If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.

Ensure that enough OPP process existing to serve the incoming request load. Otherwise increase “process”.

Thread Vs Process :You can either increase process (or) threads. It depends on the load .

Reseting and altering can be done via these navigation

Concurrent -> Manager -> Define > Output Post Processor




If you refer to metalink node 563233.1 , it is advised to have each PCP node should have one OPP must be defined.

dgreybarrow Locating OPP log file?

whenever XML issues or other publishing problems occurs, first thing you will do is to trace the OPP logfile.Locating such logs is not a big things, just follow the steps below:

  1. logon with System Administrator
  2. Function: Concurrent –> Manager –> Administration and select the Output Post Processor
  3. Click on the Processes button
  4. Select the Concurrent Process which was active during the time that the request ran
  5. Click on the Manager Log button to open the Output Post Processor log file

Directly from the file system based after identifying the corresponding OPP log file name using the following SQL statement:

SELECT fcpp.concurrent_request_id req_id, fcp.node_name, fcp.logfile_name
FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp
WHERE fcpp.processor_id = fcp.concurrent_process_id
AND fcpp.action_type = 6
AND fcpp.concurrent_request_id = &&request_id

dgreybarrowBi Publisher Enhancement Parameters

You often encounter issue whenever you have XML Publisher concurrent program with OOP. You can slightly enhance without chasing DBA everytime.

  • Use XML Publisher’s XSLT processor set to True (see fig 1 & 2cbelow)
  • Enable XSLT runtime optimization set to True (see fig 3 below)
  • Enable scalable feature of XSLT processor set to False.
    • Small Report – It is still recommended this remain false at Site level. This has the advantage of faster performance by not using temporary files for XSLT processing for small to medium reports.
    • Large Reports – what you need to do apply Patch 7599031. once Patch is applied this will safely set to True at the data definition level, enabling improved JAVA heap utilization along with ScalableFlag parameter and ‘Options’ field with the value to -Xmx1024M (or higher).

Simply follow these steps

Go to sys admin
add XML publisher administrator and choose the same responsblity
Home ->Administration

select the FO Properties


Fig 1: select FO processing

next is to reset these values


Fig 2: reseting the FO processing paramater

Go to sys admin
add XML publisher administrator and choose the same responsblity
Home ->Data Definition
search for data definition and view
then reset the value to TRUE as per figure below


Fig 3: reseting the XSLT runtime optimization set

Hope this post will help you to understand OOP.

Posted in AOL | No Comments »

Priority for Concurrent Program

Posted on September 29th, 2010 by Sanjit Anand ||Email This Post Email This Post

If you are working in big user environment, user always complain there request get stuck or takes time to start processing. Majority of time Support team cann’t do anything, unless waiting or asking DBA to check the server performance.

There is couple of option you can try , if you know a demanding user and there request name( Concurrent Program) he/she always want in periority.

dgreybarrowOptions 1: If you know what particular program user required in priority.

In oracle EBS you need to set the priority of specific users so that when they run specific reports, those reports should be run on high priority. The steps are very simple:

  1. Go to Sysadmin Responsibility and go to menu Profile > System.
  2. Make sure Site and User boxes are checked.
  3. Select the user name for the user for whom you want to increase the priority
  4. Enter the following within the Profile box and click on Find: Concurrent:Request Priority
  5. Change the priority for the user as you see fit (1 is highest, 99 is lowest, 50 is the default) , Save and exit.

Concurrent Priority1

dgreybarrowOptions 2: You know the Program name, and want to make execution in priority

The steps are very simple:

  1. Login system administrator /Application developer and go to define concurrent screen
    Under Concurrent >> Program >> Define
  2. Find the Program name whose priority you wish to change for ex. “Payable Transfer to GL”
  3. On this screen you can set priority of this request by entering value in “Priority” field( as mark in red) (1 is highest, 99 is lowest, 50 is the default) , Save and exit.

Concurrent Priority

dgreybarrow Oracle definition for Priority

Priority is used to indicate the priority that the concurrent request will be assigned when it is submitted. If you do not assign a priority, the user’s profile option Concurrent:Priority sets the request’s priority at submission.

dgreybarrow Profile : Concurrent:Request Priority

This displays the default priority number for your concurrent requests. Only a system administrator can change your request priority.

Requests normally run according to start time, on a “first-submitted, first-run” basis. Priority overrides request start time. A higher priority request starts before an earlier request.

Priorities range from 1 (highest) to 99 (lowest). The standard default is 50.

Users can see this profile option, but they cannot update it. This profile option is visible and updatable at all four levels.

Posted in AOL, Technical | 2 Comments »

« Previous Entries