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

Exporting Information to GL

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

Do you know what information exported to general ledger from other products. Here is summarized information with Product vs transaction type.

Slide1

Posted in Oracle General Ledger | No Comments »

An overview of Oracle’s Bharosa products

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

Oracle's Identity Managment architect Nishant Kaushik has posted an excellent overview of the Bharosa products in his blog. Oracle has recently acquired to boost there Identity Managment Product.

Watch out this article: More on the Bharosa Acquisition

Posted in News | No Comments »

Oracle API Availability – Profile

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

In oracle user Profile functionality is provided in the FND_PROFILE package and the FNDSQF library.

What is inside this API:

  • Retrieve user profile values for the current run-time environment
  • Set user profile values for the current run-time environment

There are various Objects that can be used with this API's. These are discussed below:

1. Put :This can be used to put a value to the specified user profile option.

Usage:

  • FND_Profile.Put('PROFILE_NAME','New_Value')
  • FND_Profile.Put('USERNAME', Usr_Name)
  • FND_Profile.Put('RESP_ID', Resp_ID)
  • FND_Profile.Put('RESP_APPL_ID', Resp_App_ID)
  • FND_Profile.Put('USER_ID', User_ID)

2.DEFINED : this is function returns TRUE if a value has been assigned to the specified profile option.

Usage:

  • SELECT fnd_profile.defined('ACCOUNT_GENERATOR:DEBUG_MODE') ACC_GEN_DEBUG_SESSION_MODE FROM DUAL;

3.GET :This is used to retrieve the current value of the specified user profile option

Usage :

Different type of options can be retrieved like

  • FND_Profile.Get('PROFILENAME', Profile_name);
  • FND_Profile.Get('CONC_LOGIN_ID', Conc_login_id);
  • FND_Profile.Get('LOGIN_ID', loginid);

4.VALUE : This is function which returns a character string. Used to retrieve the current value of the specified user profile option.

Usage:

  • fnd_profile.value('PROFILEOPTION')
  • fnd_profile.value('MFG_ORGANIZATION_ID')
  • fnd_profile.value('login_ID')
  • fnd_profile.value('USER_ID')
  • fnd_profile.value('USERNAME')
  • fnd_profile.value('CONCURRENT_REQUEST_ID')
  • fnd_profile.value('GL_SET_OF_BKS_ID')
  • fnd_profile.value('ORG_ID')
  • fnd_profile.value('SO_ORGANIZATION_ID')
  • fnd_profile.value('APPL_SHRT_NAME')
  • fnd_profile.value('RESP_NAME')
  • fnd_profile.value('RESP_ID')

5.VALUE_WNPS: This is a function, returns a character string. This is Used to retrieve the current value of the specified user profile option without caching it.

6.SAVE_USER :This is function used to save a value for a profile option permanently to the database, for the current user level. It is necessary to explicitly issue a commit when using this function. Returns TRUE if profile option is successfully saved, otherwise FALSE.

7.SAVE :This is function used to save a value for a profile option permanently to the database, for a specified level. It is necessary to explicitly issue a commit when using this function. Returns TRUE if profile option is successfully saved, otherwise FALSE.

Usage

  • fnd_profile.save('GUEST_USER_PWD', 'GUEST/ORACLE', 'SITE');

8.INITIALIZE :This is used by internal Applications Object Library to initialize the internal profile information at the level context.
The cache is first cleared of all database options.

Usage:

  • fnd_profile.initialize(user_id);

9.PUTMULTIPLE :This is used by internal Applications Object Library to set multiple pairs of profile options and values.

Posted in API Integration | 5 Comments »

Oracle API Availability – Messaging

Posted on July 23rd, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

In Oracle application messaging is typically handled in different way. If you are working in Oracle application you may notice different types of alert window you will get depending upon the condition. In oracle application this would be typical handled by whole set of bundle API , which is called as FND_MessageAPI.

Then the very next question is what is FND_MESSAGE

In simple word , Messaging functionality controlled by FND_MESSAGE package and in the FNDSQF library.

What this API's do

-Manipulate messages which normally defined in the Message Dictionary under application developer responsibility.
-Client and Server-side procedures place messages on the message stack or in the global area.
-Client-side procedures retrieve messages from the stack and display them from the currently running form

Depending upon the development need , lets understand the various function in three different way.

  1. Server side
  2. client Side

Here are the list of Procedure and Functions which can be used for retrieving and Buffer Messages at Client Side.

  1. Set_Name :Retrieves message from Message Dictionary and sets it on the stack
  2. Set_String :Procedure, used to place the passed string on the message stack.
  3. Set_Token :Substitutes token with specified value
  4. Retrieve :Retrieves a message from the server-side buffer, translates and substitutes tokens, and sets message on the stack
  5. Get (function) :Retrieves a message from the stack. Returns the retrieved message
  6. Clear : Clears the message stack
  7. Get_Encoded :This is a function, returns an encoded message from the message stack.
  8. Parse_encoded :This is a procedure used to parse the Application Short Name and the message Name out of an encoded message

For the retrieving and Buffer Messages at Server Side here are some standard procedure:

  1. Set_Name Sets a message name in the global area without retrieving it from the Message Dictionary
  2. Set_Token Adds a token/value pair to the global area without doing the substitution
  3. Clear Clears the message stack
  4. Get_Number :This is function, returns number of the specified message. Function returns 0 if the message has no number, or the message number is zero. If the message can not be found, function returns NULL
  5. Raise_error :This is Procedure that can raises an application error, returning the message information contained in the package variables

In fact for displaying purpose these are the standard procedures and Functions we can use from API, these are mostly used for displaying message at Client Side.

  • Error :Displays an error message in a forms modal window.
  • Show :Displays an informational message in a forms modal window.:
  • Warn (function) :Displays a warning message in a forms modal window. Allows user to accept or cancel the operation. Returns TRUE if user accepts.:
  • Question :Displays a message and up to three buttons in a forms modal window. Similar to a Forms Alert.
  • Hint :Displays a message in the forms status line.
  • Erase :Clears the forms status line.
  • Debug :Used for debugging. Display the specified string.
    Example: FND_Message.Debug('here is error…');

Apart from this you may also used few other like:

  • WORKING :This is used to display a message in a dialog box without any buttons. The dialog box must be closed explicitly with WORKING_CLOSE.
  • WORKING_CLOSE This can used to close the dialog box invoked by the WORKING procedure.
  • HISTORY :used to display a message in a dialog box, with the History button. If the user presses this button they see all the
    messages on the stack

Is there any way to displaying Messages from Concurrent Programs

Yes, there are two procedure which can be used :

  • Show :Displays top message on the stack in the out file. Does not print message number
  • Error :Displays top message on the stack in the log file. Prints the message number if it is not zero

Hope this would be great help in understanding and utilizing the functionality. Next will discuss how to implement these.

Posted in API Integration | No Comments »

Oracle Buys Bharosa

Posted on July 23rd, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Recent happening last week from Oracle was that "Bharosa" is now part of Oracle. Guess 32th company acquired in last 31 months. Bharosa has online identity theft package. It is expected that with Tracker and Authenticator software will be available on a standalone basis or as part of an Oracle suite. Hopefully this is boost in Oracle identity management. Guessing Single sign-on(SSO) would be armed with new software in near time.

more details can be found at
http://www.oracle.com/bharosa/index.html?msgid=5791959

http://www.oracle.com/corporate/press/2007_jul/bharosa.html

Posted in News | No Comments »

Integration with Oracle Purchasing – Shared Data Flow

Posted on July 21st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Last article I have mention , Integration aspect with oracle other modules. Here is the flow diagram of some of the shared data with other modules.

POINtegartionDependcy

Posted in Oracle Purchasing | 2 Comments »

Integration with In Oracle Purchasing

Posted on July 21st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

..why integration is important ..

Integration is an extremely important part to ERP's. ERP's main goal is to integrate data and processes from all areas of an organization and unify it for easy access and work flow. ERP's usually accomplish integration by creating one single database that employs multiple modules providing different areas of an organization with various business functions.

Oracle Purchasing Integration

Oracle Purchasing works in conjunction with other Oracle Applications to share information.

  • Oracle EDI Gateway: Electronic Data InterchangePOintegration
  • Oracle Inventory: Items, demand, receipts
  • Oracle Master Scheduling/MRP: Demand
  • Oracle Order Management: Internal requisition
  • Oracle Work in Process: Outside processing
  • Oracle Human Resources: Employees
  • Oracle Project Manufacturing: Project Details
  • Oracle Quality: Quality Details
  • Oracle Payables: Invoice Matching
  • Oracle General Ledger :Journal Entries, Set of Books
  • Oracle Supplier Scheduling: Approved Supplier List (ASL)
  • Oracle Assets: Asset Details
  • Oracle Bill of Material: Resources
  • Oracle Cost Management :Pricing

 

When Oracle Inventory, Oracle Master Scheduling/MRP, and Oracle Purchasing are used in conjunction, they share supply information. The following information is shared:

  • Open purchase orders.
  • Open releases.

POintegration1

By using Oracle Project Manufacturing and oracle Purchasing, you can now specify project sand tasks for your requisition and purchasing transactions. Specifically, you can specify projects and tasks for the Inventory and Shop Floor destination types.

POintegration2

By using Oracle Workflow and Oracle Purchasing, you can automate the approval and document creation processes by using predefined Workflow processes.

POintegration3

Posted in Oracle Purchasing | 1 Comment »

Oracle Purchasing Product Overview

Posted on July 21st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

What is Oracle Purchasing?

Oracle Purchasing is a comprehensive procurement solution designed to:

  • Help purchasing professionals reduce administration costs.
  • Process requisitions, purchase orders, requests for quotation, and receipts quickly and efficiently.
  • Enable you to focus on:
    o Value Analysis
    o Development of strategic supplier relationships
    o Management of the procurement process

Oracle Purchasing satisfies the following business needs:

  • Replaces paper processing with online requisition generation, purchase-order creation, and document approval.
  • Regulates document access, controls modification activity and approval, and is based on organizational signature and security policies.
  • Minimizes data entry time with item-saving templates.
  • Controls purchasing activity and enables accurate,automatic pricing using approved suppliers and supplier lists.
  • Consolidates purchase requirements from multiple warehouses, plants or locations.
  • Enables negotiating from a position of strength based on easy access to purchase volume statistics and supplier performance reports.
  • Facilitates communication between requesters, buyers, receiving staff, and accounts payable staff using online enquiries, attachments and notes.
  • Provides related functions, such as marketing, finance, master scheduling, inventory management, production, cost accounting, and customer order entry with access to
    purchasing information.
  • Manages historical purchasing data.

What is in Oracle Procurement solution suite?

From the oracle there are 4 different products , that helps in fulfilling complete business requirement as discussed above, these are mainly:

1. Internet Procurement (formerly Self-Service Purchasing) :A web-shopping solution for all employees that automates finding and requisitioning goods and services using self-guiding on-line catalogs coupled with efficient content management. Industry standard XML interfaces allow integration to customers' existing Oracle, non-Oracle or legacy financial systems.

2. Purchasing Intelligence :a web-enabled analysis tool which provides access to enterprise-wide procurement information, along with the ability to perform ongoing analysis of sourcing decisions, contract compliance, and supplier performance .

3. Internet Supplier Portal, a self-service solution giving trading partners internet access to purchasing, receiving and payment information, as well as providing suppliers the capability to easily process their own transactions·extending process efficiencies across the entire supply chain.

4. Purchasing, which streamlines order planning and management for purchasing professionals.

Apart from these four basic products , these are also used as advance version of purchasing solutions:

  • Oracle Sourcing is the enterprise application that drives more and better sourcing through online collaboration and negotiation.
  • Oracle Procurement Contracts is used for createing and enforces better purchasing contracts.
  • Oracle Daily Business Intelligence for Procurement is used for the spend-analysis application that allows buyers to spot savings opportunities immediately.
  • Quality

More information can be found at :

Posted in Oracle Purchasing | 2 Comments »

Reports Options for accessing Purchase Order informations

Posted on July 21st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

How many reports options available in Oracle Purchasing(PO) to access purchase order information.

They are 15-16 reports provide the access PO information in reporting format.Lets summarize some of them, these listing are based on the availability as per Oracle 11i10.2.

1. Purchase Order Detail Report

This report can be used to review all, specific standard, or planned purchase orders. This is used for review the open purchase orders to
determine how much you still have to receive and how much your supplier has already billed you.

2. Printed Change Orders (Landscape) Report
This report is used to print changed purchase orders in landscape format. Oracle Purchase provides a default format for the preprinted form.

3.Printed Change Orders (Portrait) Report
This report can be used to provides the same information as the landscape version, but printed in portrait format.

4.Printed Purchase Orders (Landscape Report)
This report can be used to print purchase orders in landscape format.Oracle Purchase provides a default format for the preprinted form.

5.Printed Purchase Orders (Portrait) Report
This report contains the same information as the landscape version, but is printed in portrait format.

6.Blanket and Planned PO Status Report
This report can be used to review purchase order transactions for blanket purchase agreements and planned purchase orders. Information will print for releases existing against the orders. If no release exists, only the purchase order header information is printed.

7.Contract Status Report
This review the status of your contract and list purchase order information regarding each contract using this report.

8.Purchase Agreement Audit Report
This report is used to review purchase order transactions for items normally required to buy using blanket purchase agreements. Oracle Purchase shows you when you purchased items using a standard purchase order that you could have purchased using a blanket purchase agreement.

9.Purchase Order and Releases Detail Report
This report can be used to review detail information for your blanket purchase agreements and planned purchase orders. The quantity ordered, receive and billed and the quantity due to be received are displayed so you can monitor the status Purchase Order Commitment by Period Report

10.Open Purchase Orders Report (by Buyer)
This report is used to review all or specific open purchase orders for specific buyers.

11.Open Purchase Order Report (by Cost Centre)
This report can be used to review all or specific open purchase orders relating to order charged to one or more cost centre suing this report.

12.Purchasing Activity Register Report
This report can be used to review purchase order monetary activity carried out for a time interval, such as a day or month.

13.Purchase Order Distribution Detail Report
This report can be used to review account distribution for a purchase order.

14.Purchase Summary Report by Category
This report can used to review the number of orders you place with vendors for a given category of item.

15.Cancelled Purchase Orders Report
This is used to review cancelled purchase orders.

16. Standard Notes Listing
This is used to review standard notes.

Posted in Oracle Purchasing | 3 Comments »

Year End Closing

Posted on July 21st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Continuing last article Does the "Year End Close" is different than "Month end close" - Part -I , lets have a look on the some steps involved for the year end process

Steps as required for year End Close in Oracle EBS.

These are the some of the standard steps performed for year-end processing in Oracle General Ledger.

1. Set the status of the first accounting period in the new fiscal year to Future Entry. Generally the first period of the new fiscal year should not be opened until all of the year-end processing for the last period of the current year has completed.

2. (Optional) Create reversing entries at the beginning of every period, generate and post accruals from the prior period now.

3. If you have other source make transfer data from all of subledgers and feeder systems to the GL_INTERFACE table.

4. Then ,run the Journal Import process to populate the GL_JE_BATCHES, GL_JE_HEADERS, and the GL_JE_LINES tables. This can be done automatically from the subledger systems, or manually from Oracle General Ledger.

5. Now the next is review the Journal Import Execution Report to check the status of all imported journal entries.

6. If there is any error journal entry batches, delete it.

7.a. If you encounter a small number of errors, make the necessary corrections in the GL_INTERFACE table using the Correct Journal import Data window. Run Journal Import.

7.b . If you encounter a large number of errors, delete the Journal Import data from the GL_Interface table, correct the information in the feeder or subledger system and run Journal Import.

8. Close the period for each subledger. This prevents future subledger transactions from being posted to General Ledger in the same period as part of regular month end close process.

9. Review the imported journal entries in Oracle General Ledger. These can be reviewed online or in reports. Reviewing journal entries before posting minimizes the number of corrections and changes that need to be made after posting.Normally these Reports are run for review.

  • Journal Batch Summary Report
  • General Journal Report
  • Journal Entry Report
  • Journal Line Report
  • Journal Source Report
  • Journals by Document Number Report (This is when document sequencing is used)
  • Unposted Journals Report.

10. Then the Post all the imported journal entries.

11. Perform reconciliations of ledgers by reviewing and correcting balances.The following reports are useful to help with the reconciliation:

  • Account Analysis with Payables Detail
  • Account Analysis with Subledger Detail
  • Account Analysis with Subledger Detail II
  • General Ledger Report
  • Posted Journals Report
  • Journals Report with Subledger Detail
  • Accrual Reconciliation Report
  • Other Reports

12. Generate all recurring journals.

13. (Optional) If you did not generate and post your prior period reversals at the beginning of this period, be sure to generate reversals now.

14. Running the revaluation process to get revalue balances to update foreign currency journals to the functional currency equivalents.

15. Then the posting all journal wheather its is manual, recurring, step-down allocations, and reversals.

16. Review your posting results. The following reports are helpful:

  • Posting Execution Report
  • Error Journals Report

17. Update any unpostable journal entries and then post them again. Common reasons for unpostable batches include:

  • Control total violations
  • Posting to unopened periods
  • Unbalanced journal entries

All errors in the journal entry batches must be corrected and resubmitted for posting.

18. Run General Ledger reports, such as the Trial Balance reports, Account Analysis reports, and Journal reports.

19. Consolidate the other sets of books if you instance is having multiple Operating units.

20. If using a calendar with an adjusting period that represent the last day of the fiscal year, close the current period and open the adjusting period.

21. Create and post adjusting entries and accruals in the adjusting period.

22. Run Trial Balance reports and other General Ledger Reports in the adjusting period after adjustments are made.

23. Post the Balance Sheet Closing Journal by submitting the Create Balance Sheet Closing Journals program, once this is done balance sheet will now reflect zero balances which is same as mention above.

24. Close the last period of the fiscal year using the period window.

25. Open the first period of the new fiscal year to launch a concurrent process to update account balances. Opening the first period of a new year automatically closes our your income statement and posts the difference to your retained earnings account specified in the Set of Books form.

26. Run FSG reports for the last period of the year.

Posted in Oracle General Ledger | 1 Comment »

Page 2 of 41234

« Previous Entries Next Entries »