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

About Me

Posted on August 31st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Sanjit Anand. Yes, you heard it right. That’s how I have been known to this planet for about 32 years now. My friends used to call me BBC and I never complained. Fun elements apart, I believe the tag of BBC reflected something uncanny about me and that was the inquisitiveness of storing as much information as I possibly could- sometimes to equip myself and sometimes to share with others.

Past Perfect:Been there and done that. However, it feels great to do everything all over again. This is how I would describe my professional life so far. As a no-nonsense Funco-Techno consultant I have in my kitty over 8.7+ years of specialized experience in Oracle Financials and manufacturing Modules. To be more specific, my areas of interest include-but are not restricted to- Transaction Management, Working Capital, Procure to Pay, Order to Cash, SOX, Upgrades, Implementations and System Integration. Besides all these I also possess hands-on expertise in oracle EBS and have been involved in some of the big roll outs in Asia, the United States and Europe.

I have worked in diverse positions at large oracle integrators such as: Computer Science Corp, Rapidigm and TCG - United Airlines and for about a year I worked as an independent consultant adding value to customized Oracle apps needs.

Drawing upon the training that I received at my undergrad level and subsequently at the post-grad level at IIT Kanpur, getting into IT was an easy and automatic choice. But what I learnt as a professional in my work life truly helped me put things in right perspective. Now I realize life is not all about bunking a lecture to catch up some programming tools in the computer lab.

Present Uncompromisable: Currently based out of Singapore associated with TCS, Singapore, I am laying my hands on rolling out an Implementation for a one of Asia's largest group of hospital moving from SAP to Oracle EBS. Having a challenging responsibility in hand in terms of living up to the diverse needs of clients based in the US, Singapore and UK., but then is not that what brings out the best in someone? Well, the answer is simple and it’s a big YES.

My only daughter Ankita has just added a new feather on my cap and it has been just great to unlearn few tech stuff when I am home. And to make things more beautiful there is my wife- Vinita who seems to have perfected the art of making life livable and lovable.

Future Promising:With the growing need for innovation at every step of human life, I guess one’s life time is never enough to live it out to its true potential. However, the appetite for taking fresh challenges seems to be enough to keep myself going.

Posted in Oracle Application | Comments Off

Archives

Posted on August 31st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Posted in Oracle Application | Comments Off

News Aggregator

Posted on August 31st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Aggregator for monitoring Oracle related weblogs and news.

This page is under construction as of 2007/12/29. Thank you for your patience.



[QuickRSS=false,false,false,5,true,200] http://www.oracle.com/rss/rss_ocom_pr.xml[/QuickRSS]



[QuickRSS=false,false,false,7,false,200] http://feeds.feedburner.com/OracleE-BusinessSuiteTechnology[/QuickRSS]


[QuickRSS=false,false,false,10,false,200] http://feeds.feedburner.com/orana[/QuickRSS]

Posted in Oracle Application | Comments Off

Trace the flow of “default values” in Account Payable.

Posted on August 27th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Do you know, there are many default value which can be controlled at set up level. Here is the explanation based out of close microscopic view of default values of Account Payable.

apsetup

Do we have any General Setup Hierarchy for Default values???

Yes , we have a General Setup Hierarchy for Default values, which can be typically described as:

aphir

Posted in Functional, Oracle Payable, Technical | No Comments »

Quick Tour for Account Payable

Posted on August 27th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

AP takes care of all payments in Oracle Applications. This module has active interaction with Purchasing and General Ledger modules.

The different functionality of the Payables module are:

  • Set up Supplier.
  • Enter, review and Approve invoices.
  • Pay invoices and reconcile payments to bank a/c.
  • Enter and apply pre-payments.
  • Create journal entries for posting to GL.

An top level overview of the module can be given as :

ap

1.Enter Suppliers

This step consist of set up as well as maintenance of existing one.During the setup, we need to do setup for

  • Supplier Accounts
  • Taxes
  • Payments
  • Term Date Basis
  • Due Date Basis
  • Invoice Currency
  • Holds

Importantly the other features in this area consist is :

  • Enter employees as Suppliers : this is for managing and controlling Expense report
  • Merge duplicate Suppliers

2.Invoices

This consist Setup for;

  • Distribution Set
  • Tax
  • Setup tolerance, matching options

3. Approve invoice

This required set up for rule, so that approval and validation process can validate based on some parameter.

4.Payments

This requires set up for payment related dependency which include ;

  • Format
  • Bank
  • Bank account
  • Build program
  • Payment Methods
    • Manual
    • Quick Check
    • Automatic Check

Take a note in manual and Quick check, you have to simply enter payment details and correlate to invoices. Automatic check is applicable for batch payments.

5. Create Journal entries

Typical flow for creating Journal entries is summarized as:

AP2GL

And here is final note of accounting Entries of AP :

  • During Invoicing
    • Expenses A/C Dr to vendor liability
  • During Payment
    • Vendor liability A/C Dr to Cash/Bank A/C

...And, This is Four Rule of Payables

  • You must have a vendor to do anything
  • Every Invoice must be fully Charged out before paid or posting to GL.
  • All Payments must have an invoice
  • Every Invoice must run through approval process.

Hope this is a brief overview of the Payable business flow, will discuss & share some more in next couple of post.Till then keep watching this space.

Posted in Functional, Oracle Payable, Technical | 1 Comment »

Understanding Shared Product & Data

Posted on August 26th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

The idea of having 'DEPENDENT' OR "SHARED" PRODUCTS or DATA in Oracle application is because of tight integration within the other area.

As Oracle application is tightly integrated.

  • Each Application depends on components from other products,called dependent or "shared" products, for full functionality.
    • For example, Oracle Payables uses components in Oracle General Ledger, Oracle Purchasing, and Oracle Personnel.
    • Components always differ: 60-80% of all Applications files are needed by two or more products.
  • When you install a product, you install the database components of all Oracle Applications products.
    • This only applies to the database portion of Oracle Applications.
      • You will not install the filesystem component of all Oracle Applications products.
    • Shared products are mostly transparent to the user.

If you take a case, to understand the sharing data concept in oracle application, you can find lot many nodes , but after all that's beauty of Oracle application.

sharedData

Posted in Oracle Application | No Comments »

Great FNDLOAD – Part -II

Posted on August 25th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

I have already posted note on FNDLOAD utility for doing movement of application setup data from one database to the other.There are instances when we need to move some AOL and seeded data from one Environment to another Environment, thus at that time it is necessary to understand what are different options Available within the Oracle. Here is extensive list for some of the objects , that should be migrated by FNDLOAD.

fnd

Posted in AOL, Oracle Application | 2 Comments »

..Bit on DFF Context Synchronization

Posted on August 24th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

What is Descriptive Flexfield Context Synchronization

Descriptive Flexfield Context Synchronization allows the runtime descriptive flexfield (DFF) context to be determined from a current reference field value for the entity instance (current record) instead of a previous value of the reference field

How/where this can be actioned?

Typically as per AOL documentation it is enable by providing new check box "Synchronize with Reference Field" on the Descriptive Flexfields
Segments form (FNDFFMDC)

What is meant by Checking and unchecking

  • Value of "Yes" means context is always synchronized with reference field value.
  • Value of "No" denotes that context will be defaulted from reference field value, the first time the record is created and the DFF is touched. Thereafter, context would never be synchronized by the flex engine.Context prompt treated differently by DFF view generator.

Reference:

Posted in AOL | 3 Comments »

How to use Descriptive Flex Fields (DFF) in forms

Posted on August 24th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Implementing DFF in Form consist of two steps Process. The first steps consist of designing the table structure and registration and step 2 consist of enabling in the form.

Steps 1:

  • Define DFF fields in the custom tables

ATTRIBUTE1…ATTRIBUTE15 and ATTRIBUTE_CATEGORY are the normal fields used for DFF

  • Register the table with Oracle AOL
  • Register the DFF with Oracle AOL

For this you have to login into application with :

Application Developer -> Flex Field -> Descriptive -> Register

Then you should specify the name of the DFF (Say BTL_AR_DFF) and specify the associated table.

Step 2:

  • Create DFF fields in the custom form

1. Create a form based on the custom table

  • Copy TEMPLATE form has example descriptive flexfield which we can use
  • Use the TEXT_ITEM_DESC_FLEX property class
  • Attach ENABLE_LIST_LAMP_LOV for the field

2. Create a non-base table text item in the block with property class TEXT_ITEM_DESC_FLEX
3. Make sure that DFF is mapped to fields (ATTRIBUTE) of the table and is enabled.

  • Next is to call Flexfield Routines to add DFF built-ins in the form to invoke DFF.
    • This consist of these steps:

1. Write, a form level trigger WHEN-NEW-FORM-INSTANCE to invoke the DFF as

FND_DESCR_FLEX.DEFINE(
Block => 'Name of the DFF block',
Field => 'BTL_DFF',
Appl_short_name => 'AR',
Desc_flex_name => 'BTL_AR_DFF',
Title => 'BPL AR More Info' );

2. Write, block level triggers PRE-QUERY and POST-QUERY as

  • FND_FLEX.EVENT('PRE-QUERY');
  • FND_FLEX.EVENT('POST-QUERY');
  • FND_FLEX.EVENT('Pre-Query');
  • FND_FLEX.EVENT('When-Validate-Record');
  • FND_FLEX.EVENT('Post-Query');
  • FND_FLEX.EVENT('When-New-Item-Instance');
  • FND_FLEX.EVENT('Pre-Insert');
  • FND_FLEX.EVENT('When-Validate-Item');
  • FND_FLEX.EVENT('Pre-Update ');

Posted in AOL, Beginner | 4 Comments »

12 Steps for Enabling Flexfields in Oracle Report

Posted on August 24th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

If any one want to use Flexfield in report, there is minimum steps you have to follow to make things Functional. These are the standard steps as per AOL guide.

Step 1 Define your Before Report Trigger

Here you suppose to call FND SRWINIT from the Before Report Trigger like :

SRW.USER_EXIT('FND SRWINIT');

This user exit sets up information for use by flexfields, user profiles, the concurrent manager, and other Oracle Applications features as discussed in one of previous post.

Step 2 Define your After Report Trigger

Next, is you need to call FND SRWEXIT from the After Report Trigger like :

SRW.USER_EXIT('FND SRWEXIT');

Step 3 Define your required parameters

In this step you need to define the parameters your report needs by using the Data Model Painter. You use these parameters in the user exit calls and SQL statements.

Lexical Parameters

  • P_CONC_REQUEST_ID
  • P_FLEXDATA

You must always create the P_CONC_REQUEST_ID lexical parameter. "FND SRWINIT" uses this parameter to retrieve information about the concurrent request that started this report.

The P_FLEXDATA parameter holds the SELECT fragment of the SQL query. The initial value is used to check the validity of a query containing this parameter and to determine the width of the column as specified by the column alias. Its initial value is some string that contains columns with a cumulative width more than the expected width required to hold the data. Make sure the width of this column is sufficient. If there are total 30 segments in the table then the safest initial value will be:

(SEGMENT1||'\n'||SEGMENT2||'\n'||SEGMENT3 ... SEGMENT30)
You determine the width by determining the length of that string. That length is roughly the number of characters in the table alias plus the length of the column name, times the number of segments your code combinations table contains, times the number of structures you expect, plus more for delimiter characters as shown in the string above.

Step 4 Define your rest other parameters

You define the rest of the parameters your report needs by using the Data Model Painter. You use these parameters in the user exit calls and SQL statements.

Step 5 Call FND FLEXSQL from your Before Report Trigger to populate P_FLEXDATA

Next, given that you want to display flexfield information like concatenated values and descriptions, and arrange them in order, you make one call to FND FLEXSQL from the Before Report Trigger specifying the lexical parameters. This call changes the value of the lexical parameter P_FLEXDATA at runtime to the SQL fragment that selects all flexfields value data. For example, the parameter changes to (SEGMENT1||'\n'||SEGMENT2||'\n'||SEGMENT3||'\n'||SEGMENT4).

When you incorporate this lexical parameter into the SELECT clause of a query, it enables the query to return the concatenated segment values that are needed as input to other AOL user exits. These exits then retrieve the actual flexfield information for display purposes.

Here is an example FND FLEXSQL call. Notice that the arguments are very similar to other flexfield routine calls; CODE= and NUM= designate the key flexfield and its structure, respectively. For a report on a different key flexfield (such as the System Items flexfield), you would use a different CODE and NUM.

SRW.REFERENCE(:P_STRUCT_NUM);
SRW.USER_EXIT('FND FLEXSQL
CODE="GL#"
NUM=":P_STRUCT_NUM"
APPL_SHORT_NAME="SQLGL"
OUTPUT=":P_FLEXDATA"
MODE="SELECT"
DISPLAY="ALL"');

You should always reference any source column/parameter that is used as a source for data retrieval in the user exit. This guarantees that this column/parameter will contain the latest value and is achieved by "SRW.REFERENCE" call as shown above.

Step 6 Call FND FLEXSQL from your Before Report Trigger to populate other parameters
What you suppose ti do here is just need to call FND FLEXSQL once for every lexical parameter.

Step 7 Define your report query or queries
Define your report query Q_1:

SELECT &P_FLEXDATA C_FLEXDATA
FROM CODE_COMBINATIONS_TABLE
WHERE CODE_COMBINATIONS_TABLE.STRUCTURE_DEFINING_COLUMN
= &P_STRUCT_NUM

The query fetches the data required to be used as input for the FLEXIDVAL user exit later.

When the report runs, the call to FND FLEXSQL fills in the lexical parameters. As a result the second query would look something like:

SELECT (SEGMENT1||'-'||SEGMENT2||'-'||SEGMENT3||'-'||
SEGMENT4) C_FLEXDATA
FROM CODE_COMBINATIONS_TABLE
WHERE CODE_COMBINATIONS_TABLE.STRUCTURE_DEFINING_COLUMN = 101< /FONT >

Step 8 Create formula columns

Now create columns C_FLEXFIELD and C_DESC_ALL (and any others your report uses) corresponding to the values and descriptions displayed in the report. They all are in group G_1.

Step 9 Populate segment values formula column
Now you need to retrieve the concatenated flexfield segment values and description which you incorporate the flexfields user exits in these columns. In the column definition of C_FLEXFIELD, you incorporate the FND FLEXIDVAL user exit call in the formula field. You pass the concatenated segments along with other information to the user exit, and the user exit populates the concatenated values in this column as specified by the VALUE token. A typical call to populate segment values in this column looks as follows:

SRW.REFERENCE(:P_STRUCT_NUM);
SRW.REFERENCE(:C_FLEXDATA);
SRW.USER_EXIT('FND FLEXIDVAL
CODE="GL#"
NUM=":P_STRUCT_NUM"
APPL_SHORT_NAME="SQLGL"
DATA=":C_FLEXDATA"
VALUE=":C_FLEXFIELD"
DISPLAY="ALL"');
RETURN(:C_FLEXFIELD);

Refer this how to enable user exits in reports.

Step 10 Populate segment descriptions< /STRONG>


To populate the segment description use DESCRIPTION="C_DESC_ALL" instead of VALUE="C_FLEXFIELD" as in the previous call. The user exit call becomes:

SRW.REFERENCE(:P_STRUCT_NUM);
SRW.REFERENCE(:C_FLEXDATA);
SRW.USER_EXIT('FND FLEXIDVAL
CODE="GL#"
NUM=":P_STRUCT_NUM"
APPL_SHORT_NAME="SQLGL"
DATA=":C_FLEXDATA"
DESCRIPTION=":C_DESC_ALL"
DISPLAY="ALL"');
RETURN(:C_DESC_ALL);

You have created parameters and columns that are containers of all the values to be displayed. Now, in the following steps, you create the layout to display these values on the report.

Step 11 Create your default report layout

First choose Default Layout to generate the default layout. Deselect C_FLEXDATA. Specify a "Label" and a reasonable "Width" for the columns you want to display.

Step 12 Finish your report By adjusting report layout.

Posted in AOL, Technical | 7 Comments »

Page 1 of 41234

« Previous Entries