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

R12 SLA : Profile Options related to SLA

Posted on May 27th, 2010 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Some of the key Profile Options for SLA that you should aware of;

  • SLA: Accounting Methods Builder Context
  • SLA: Additional Data Access Set
  • SLA: Allow Reports Journal Source Override
  • SLA: Disable Journal Import
  • SLA: Display Timestamp on Trace
  • SLA: Enable Data Access Set Security in Subledger
  • SLA: Enable Diagnostics
  • SLA: Enable PL/SQL Profiler
  • SLA: Enable SQL Trace
  • SLA: Enable SRS Log/Output
  • SLA: Enable Subledger Transaction Security in GL
  • SLA: Enable Trace
  • SLA: Flush Trace File
  • SLA: INITIAL DATE FOR HISTORICAL UPGRADE
  • SLA: Oracle Forms Trace Mode
  • SLA: SRS Trace Mode
  • SLA: Trace File Override Directory
  • SLA: Trace File Override Filename
  • SLA: Trace Level
  • SLA: Trace Timeout

dgreybarrow Similar Post

Posted in Subledger Accounting | No Comments »

Contrasting Workflow and BPEL

Posted on May 19th, 2010 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Here is quick compare with two process modeling tool available in oracle.

 

Aspect Workflow BPEL
Repository DB Tables Message/DB
Comm. Method DB Queues XML Messages
Scope EBS All Fusion products
“Widget” Development PL/SQL /Java Web Services wrapper
Architecture Proprietary Standards Based
Versioning No Yes
Scalability Good Excellent

Suggested Read

Posted in Technical | No Comments »

How To Enable Tracing ( Request Running/Normal)

Posted on May 11th, 2010 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

dgreybarrow Enable Tracing On Program Level is not recommended by Oracle. there is way to do

System Administrator Responsibility

Navigation: Concurrent -> Program -> Define

Click the “Enable Trace” button

TRACE

Fig 1

Please take a note, once it enabled, this generates trace for all the request submitted by all end- users. Hence this could generate lots of trace files which is an additional overhead and degrade performance of the application.

dgreybarrowEnable Tracing On Request Level , this is Recommended way to do:

Steps are :

  • Responsibility: System Administrator
  • Navigate: Profiles > System
  • Query Profile Option Concurrent: Allow Debugging
  • Set profile to Yes
  • Logon to the Responsibility that runs the Concurrent Program
  • In the Submit Request Screen click on Debug Options (B) [ see fig 2]
  • Select the Checkbox for SQL Trace and select desired Trace level.[ see fig 3]
  • Submit the Request.

TRACE1

Fig 2

TRACE2

Fig 3

Once you have obtained the Raw trace file you need to format the file using TKPROF :

tkprof raw_trace_file.trc output_file explain=apps/<passwd> \sort=(exeela,fchela, prsela)

If you do not know the path for those directories, you can run a command like the following query in SQL :

select name, value from v$parameter where name = 'user_dump_dest';

Posted in AOL | No Comments »

Understanding difference between Credit Hold & Credit Check

Posted on May 3rd, 2010 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

CREDIT HOLD

Oracle EBS Credit Hold is the ability to place ALL customer orders on hold immediately regardless of customer credit limits or exposure or credit risk.

When the user enables credit hold on a customer or customer site, all orders are placed on hold immediately to prevent further processing. If a user enters a new order it will go immediately on hold and will not book or progress further.

This is used by Receivables Departments when a customer is an immediate risk to prevent any order processing for a specific customer bill-to site, or specific customer

ENABLING CREDIT HOLD

Oracle EBS AR or OM analysts can enable Credit Hold by querying the Customer Record.

Navigation should be Customer -> Standard. Once setup done , this will prevent the sales orders from booking.

If Credit Hold needs to be applied at the Customer Level enable the check box Credit Hold. You need to flag this at Profile: Transaction.

If Credit Hold needs to be applied at the Bill-to Level. Select Addresses and select Bill-to then enable the check box Credit Hold.

When the credit hold check box is enabled a hold source is created that places all current and future orders on hold irregardless of credit limits.

When the credit hold check box is disabled, the hold source is removed and the orders will progress.

If credit hold is enabled at the Bill-to Site, lines with this bill-to are placed on hold. The order can still be booked if the profile option OM: Prevent Booking for Line Generic Holds is set to No.

ENABALING CREDIT HOLD AUTOMATICALLY

You can esaily achieved this by simply putting $0.00 in the profile amounts on the customer header, does not stop an order from being created. That mean when a customer account is on credit hold, you can still create new sales orders for that customer in Oracle Order Management

However, all new orders will have a status of 'on hold' and orders cannot be booked or shipped until the hold on the customer account is removed

A hold will automatically be place on a customer under the following conditions:

  1. 'Credit Check' must be selected for both the Payment Term and Order Type for the related customer
  2. The customers credit limit must = $0.00 or the customer must have exceeded their limit
  3. Alternatively, the customer can manually be placed on Credit Hold by selecting the Credit Hold check box

There is another term called Credit Check , which Often confuse . Have a detail look.

CREDIT CHECK

Credit Check is is used during the Order Life Cycle to verify customer credit worthiness.

EBS credit check functionality requires setting up credit limits and assigning credit check rules to determine the exposure of the specific customer based on a series of parameters such as open uninvoiced orders, past due invoices, shipping horizon days against credit limit.

If the customer exceeds set credit limits, total exposure or has past due invoices, the orders will be placed on hold.

Oracle EBS Credit Check can be done at Order Booking, Pick or Purchase Release, Packing and Shipping.

ENABLING CREDIT CHECK

Enabling this feature for credit check , you can do at following level:

  1. Item category level
  2. Bill To Site level
  3. Customer level ONLY if the Bill-to Site is enabled as well
  4. Party level (Remember if Option/level is only used if have Credit Management is installed.)
  5. Operating Unit Default level

You can define credit Limits defined at one of the above specified Levels.

There are two credit limits, the order credit limit and the credit limit. The credit limit if null is assumed to be unlimited.

The credit limit specifies the maximum value of exposure that the Customer is allowed.

The order credit limit if null assumes there is no maximum value per order. If specified is the maximum value of an order that can be placed.

For example if the Order Limit is $500 and a customer places an order for $505 the order will be placed on Check Failure Hold regardless of the credit exposure.

Once Credit Check is enabled on the customer at the level needed and credit limits are defined, credit check must be enabled on the Payment Terms Record.

The Credit Check Rule defined must be included in the transaction type used when placing an Order. Main Tab > Credit Check Rule area

The Credit Check Rule (same credit check rule, or different credit check rules) can be defined for the following four (4) phases:

  • Ordering
  • Picking/Purchase Release
  • Packing
  • Shipping

Hope this helps.

Posted in Oracle Order Management | No Comments »

Page 1 of 11