Skip navigation

Do you have industry or regional data requirements to store additional information on your General Ledger Applications (Example: P0911, P0901)? Do you want to minimize your dependence on your limited IT resources to meet those requirements? Have you ever wished you could add additional columns to forms to meet your requirement?

 

With Form Extension, you can! Form Extension is where personalization meets extensibility to create a better user experience. With Form Extension, you can:

  • Create a holistic solution without creating barriers to continuous adoption
  • Capture additional information to meet industry and regional data requirements quickly and easily
  • Consume them in personalization frameworks like Personal Forms, Orchestrations, CafeOne layouts, etc.

 

Form Extension is a great way to extend and personalize your forms by adding more business view columns based on your needs without having to open application code.

 

Example: Add a column Reference 2 in the form Work with Journal Entries W0911I (P0911)

 

  1. Launch Work with Journal Entries W0911I(P0911)and look for Form Extension Icon .Then drag drop Reference 2 field to the grid. Save it.St1.png

2.  Launch W0911I(P0911) again with the new column Reference 2 added to the grid

St3.png

 

For More information on how to use form extension please refer to the below:

  1. Learnjde.com

    2. Understanding Form Extension Available Starting with 9.2.2.4 Tools Release (Doc ID 2384606.1)

Business services are objects that enable interoperability between JD Edwards EnterpriseOne and other Oracle applications or third-party applications and systems. Business services enable software applications that are written in various programming languages and running on various platforms to exchange information.

 

A web service is a standardized way of integrating web-based applications. In JD Edwards EnterpriseOne, published business services are exposed to consumers as web services. These web services enable JD Edwards EnterpriseOne to expose native transactions to other applications and systems.

 

The FinancialManager web service (JP090000) manages the processing of financial-related web service operations.

 

There are two financial web service Operations (Methods) :

 

  • getGLAccount (J0900001) – Is a database query operation that enables consumers to retrieve and review general ledger account records from the Account Master table(F0901).

 

How to check whether operation getGLAccount (J0900001) is working properly:

 

How can I tell if the operation completes successfully?

If the operation completes successfully, the system returns records that match the query, if they exist. If the operation ends in error, the consumer receives an error message.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

If I encounter errors while process a transaction, do I need to reverse the transaction?

This is a query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and try your query again. If the operation does not return any records, verify that a version matching your query exist in the JD Edwards EnterpriseOne database.

Does this operation use record reservation?

No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing.

 

  • insertBatchJournalEntry (J0900002) – Is a database insert operation that enables consumers to add journal entry records to the Journal Entry Transactions - Batch table (F0911Z1).

 

How to check whether operation insertBatchJournalEntry (J0900002) is working properly:

 

How can I tell if the operation completes successfully?

If the operation completes successfully, the system inserts records into the table.

If I encounter errors while process a transaction, do I need to reverse the transaction?

If the service does not complete successfully, no records are inserted into the table. You must reprocess the action to insert the records.

Does this operation use record reservation?

No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing.

 

Details on how to use the Financial Manager web service or any other standard Business Service methods are available in the JD Edwards Technical Catalog.

 

More information can be found in:

The management of financials of a Joint Venture is key to the successful business relationship between joint venture partners. Accurate management of joint venture, budgets, costs, invoices and payments help ensure transparency of the joint venture financials. Joint Venture Management (G09J) provides the architectural foundation to create and manage Joint Ventures and the Distribution of Interest among the joint venture partners.

 

A new enhancements for Joint Venture Management is now available to define and manage Allocations for Joint Ventures.  Allocations are the process of accumulating costs for various accounts for specific allocation business units and then cascading these costs to the business units which got the benefit from these expenses.

 

The Advanced Variable Numerator (AVN) method of computing joint venture-based allocations provides the same functionality that is available in the account balance-based variable numerator method but also supports allocations to different joint ventures and joint venture business units for indirect costs incurred by the managing partner.

 

The transactions to be allocated are excluded from the joint venture distribution process until the allocation process is complete. After the costs are allocated to the impacted business units, the amounts are distributed to the partners, including the managing partner.

 

The new Joint Venture Management enhancements can be downloaded from the Update Center under Bug 28711697 - JOINT VENTURE MANAGEMENT – ALLOCATIONS

 

For more detailed information on this functionality, please review: New Enhancement –Joint Venture Management Allocations EnterpriseOne 9.2 (Doc ID 2508350.1)

New enhancements for Joint Venture Management are now available to calculate overhead charges and billing for joint ventures:

  1. Overhead Calculation

Overhead is calculated once a month, and there can be only one overhead entry for the joint venture, business unit, rule, method, year, and month.

To calculate overhead, you use the Overhead Rules program (P09J50) to create an overhead rule that can contain different calculation methods. Each method has an effective start and end date for calculating the overhead amount. The system provides five overhead charging methods to use: Fixed Amount, Fixed Amount with Escalation, Fixed Percent, Fixed Percent with Sliding Scale, and Day Rate and User Defined Method.

 

   B. Billing and Paying the Partners

The expenses incurred and revenue generated by a joint venture are shared among the joint venture partners. You record expenses and revenue for actual amounts, and then bill the distributed expenses or pay the distributed revenue to the partners based on ownership percentages maintained in the Division of Interest (DOI) tables (F09J20 and F09J21).

 

The new Joint Venture Management enhancements can be downloaded from the Update Center under the following bugs:

Bug 27046889 - JOINT VENTURE MANAGEMENT - OVERHEAD RULES

Bug 26963997 - JOINT VENTURE MGMT – INVOICING

 

For more detailed information on this functionality, please review:

Overview of Joint Venture Management (G09J) (Doc ID 2317050.1)

JD Edwards EnterpriseOne Applications Joint Venture Management Implementation Guide Release 9.2

JD Edwards EnterpriseOne Notifications enable you to improve your business efficiency through the use of proactive notifications that are actionable. Proactive notifications enable the system to notify users of business events as they happen without the need for the user to be online.

 

Users can choose to subscribe to available notifications and receive updates within EnterpriseOne, as browser pop-up messages, through the Work Center, by email, or by email to SMS (Short Message Service)

 

Example

During Month End Close the accounting managers at Company A must be available at all times to approve month-end adjustment entries that are being made by many different groups. They need to be notified whenever there are batches awaiting approval, even while they are away from their desks or away from the office. Today, Watchlists serve this purpose well, but the accounting managers must be logged into EnterpriseOne to see the Watchlist. Receiving an e-mail or text message on their mobile device will enable them to be away from their desk and still perform their jobs.

 

Solution

Company A wants to design a notification that will send the information to the accounting managers even if they are not currently signed into EnterpriseOne. Company A can create a notification:

  • Use a Watchlist type notification and define the notification message text to explain that there are batches needing review and approval.
  • Add a shortcut to the Work with Batches application from the notification message.
  • Allow the accounting managers to subscribe to the notification and select the email delivery option.

 

You can also review the following resources for more information on the new Notification feature:

  • Advisor Webcast Recording: JD Edwards Enterprise One (JDE E1) - JD Edwards EnterpriseOne Integration Technologies-Getting Started with the new Notification Feature held on May 22, 2018 [Video] (Doc ID 2378851.1)
  • JD Edwards EnterpriseOne Delivered Notifications (Doc ID 2365066.1)
  • How to Create a Simple Notifications in Orchestrator Studio - External Email, Work Center and Bell. (Doc ID 2356747.1)

As we approach the end of FY 2017 (for those of you who are following a non-calendar date pattern), it’s a great time to start thinking about year-end close issues. Rather than wait until the end of closing month, getting a head start can improve your chances of closing smoothly without any issues by the closing month.

 

There are several tasks that need to be completed as part of the closing process; including closing the accounting period, changing the financial reporting date and closing the fiscal year.  Before closing the year, there are several other tasks that need to be performed before the annual close can take place:

 

  • Verify General Ledger Automatic Accounting Instructions (AAIs)
  • Set up Leger Type points to close to retained earnings
  • Enter period-end accruals
  • Review and post all batches
  • Verify data integrity
  • Reconcile General Ledger to bank accounts
  • Run monetary account valuation and financial reports

 

In addition to these tasks, organization should develop their own detailed closing tasks and include them in their internal documentation.

 

You can also review these knowledge articles for more information on the Annual Close Process:

  • Overview of Annual Close Report (R098201) (Doc ID 664688.1)
  • Frequently Asked Questions on the Annual Close Report (R098201) (Doc ID 664687.1)

In order for companies to remain competitive in the market place, more companies are joining together in joint partnerships.  A Joint Venture is a partnership between multiple entities that share in the cost and revenue associated with the joint venture.

 

The management of financials of a Joint Venture is key to the successful business relationship between joint venture partners. Accurate management of joint venture, budgets, costs, invoices and payments help ensure transparency of the joint venture financials. 

 

Percentage of Ownership and Distributions feature from JD Edwards EnterpriseOne provides the architectural foundation to create and manage joint ventures and the distribution of amounts among joint venture partners using a JV’s percentage of ownership.

 

The JVM solution can be downloaded from the update center on the ESU associated with BUG 22541426. The optional UX One content requires Tools 9.2.2.x. UDOs can be downloaded from the update center on the BUGS 26585889 & 26929340

 

You can also review these knowledge articles for more information on Joint Venture Management:

 

  • New Enhancement – Joint Venture Management EnterpriseOne 9.2 (Doc ID 2317440.1)
  • Overview of Joint Venture Management (G09J) (Doc ID 2317050.1)

AdvisorWebcast.pngYou may have attended on May 17th, 2017, the Advisor Webcast on JD Edwards EnterpriseOne Financials Intercompany Settlements. Or maybe you saw the MOSC thread on the webcast,

https://community.oracle.com/docs/DOC-1013138. Whether you have or haven’t, I thought that it is an important enough topic to discuss on the Intercompany Settlement methods here in the blog as well.

Method Details:

  • There are three methods of setting up intercompany settlements:
  • The Hub Method (1)
  • The Detail Method (2)
  • The Configured Hub Method (3) - Introduced in 8.9
  • The Intercompany Settlements process is system wide. In other words, you cannot choose to allow intercompany settlements between specific companies and not others.
  • If you are using intercompany settlements, you must set up ALL companies for this functionality even if you have companies which will never use the process.
  • You create intercompany settlements to ensure that each company's net balance equals zero (that is, debits equal credits). You can either create these settlements yourself or have the system create them automatically.
  • When you post (R09801) transactions using one of these methods, the system creates journal entries for intercompany settlements based on Automatic Accounting Instructions (AAIs). Two AAI items exist for intercompany settlements. Depending on the method that you choose, you must set up one or both of the AAIs.
  • If your organization uses multiple currencies, you must use either the detail (2) or configured hub (3) method for intercompany settlements.
  • Hub methods are more commonly used than Detail Methods. Hub methods require more account setup than detail methods, but create fewer records in the Account Ledger table (F0911) when you post entries.
  • Detail methods are commonly used by multi-national companies and government agencies that need a detailed audit trail.
  • When you choose the Hub Method, the system creates summarized journal entries by batch and GL date between a hub (main) company and related subsidiary companies. You can have only one hub company. The system reconciles transactions between subsidiary companies through the hub company.
  • When you choose the Detail method, the system creates detailed journal entries by document between companies, using the company on the first line of a journal entry as the hub company. Because no designated hub company exists, the system reconciles transactions between the companies involved.
  • Configured hubs are groups of companies that you can define, or configure, to accommodate intercompany settlements.

 

For more detailed information, you can play the recording of the webcast or review a PDF of the presentation. To find these:

  1. Go to knowledge article Advisor Webcast JD Edwards EnterpriseOne Schedule and Archived Recordings (Doc ID 1450327.1)
  2. Click on the tab named ‘Archived 2017’
  3. Scroll down to May 17.
  4. Then either click on the webcast title ‘JD Edwards EnterpriseOne Financials Intercompany Settlements.’, or on the recording or PDF links for this webcast.

 

You can also review these knowledge articles for more information on the Intercompany Settlements:

  • E1: 09: Overview of Intercompany Settlement Methods (P0000) (Doc ID 1416193.1)
  • E1: 09: Frequently Asked Questions on the Intercompany Settlement Methods (P0000) (Doc ID 664765.1)
  • E1: 09: Overview of Automatic Accounting Instructions (AAI) in General Accounting (P0012) (Doc ID 664682.1)

The Journal Entry (P0911) application functionality has been enhanced such that now users have a choice to allow or restrict JX journal entries that are created for accounts with Posting Edit Code as 'M'(PEC=M). The new functionality brings gives more flexibility to the users for creating adjustment journals.

 

Upon further review by Oracle Support and Development teams, Enhancement Bug 25169318 will now be implemented as a Code Bug and the ESU is expected to be available by March, 2017.

 

Prior to the change, JX journal entries can be created for accounts with the Posting Edit Code as "M".

 

Now when creating JX journal entries users will have a choice whether to restrict entries for accounts with Posting Edit Code as "M".

 

The revised functionality is included in the following bugs:

9.0 Bug 25169318

9.1 Bug 25436948

9.2 Bug 25436956

 

In P0911 JX Entries Are Allowed For An Account With Posting Edit Code M (Doc ID 2208531.1) has more information on this change.

AdvisorWebcast.pngYou may have attended on August 24th , 2016, the Advisor Webcast on JD Edwards EnterpriseOne General Ledger Integrity Issues. Or maybe you saw the MOSC thread on the webcast,

https://community.oracle.com/thread/3942031.

 

Whether you have or haven’t, I thought that it is an important enough topic to discuss on the best practices here in the blog as well.

 

Best Practices :

  • Designate only a group of Power Users who can update GL system constant(P000),Business Unit Master(P0006),Company Names and Numbers(P0010) and Account Master(P0901).This Users should not have a security set a BU/Company Level.
  • All Accounts which are meant for automatic entries(Example –AR/AP Trade Account) should always have a posting edit code of "M" and should not be removed.
  • Run GL Integrity as often as possible.
  • Run Integrity reports after office hours. Example - Repost Report(R099102), which takes a lot of system resources.
  • Post all batches (R09801) before running any integrity report.
  • Save the PDF Report Output for Integrity Reports such that it can be used for research in future.
  • Verify the Report Output for R09801 and make sure that the Dr and Cr entries are correct.
  • Create a central Contact to report, research and correct integrity issues at the earliest.

 

For more detailed information, you can play the recording of the webcast or review a PDF of the presentation. To find these:

  1. Go to knowledge article Advisor Webcast JD Edwards EnterpriseOne Schedule and Archived Recordings (Doc ID 1450327.1)
  2. Click on the tab named ‘Archived 2016’
  3. Scroll down to August 24.
  4. Then either click on the webcast title ‘JD Edwards EnterpriseOne General Ledger Integrity Issues.’, or on the recording or PDF links for this webcast.

Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see https://community.oracle.com/docs/DOC-1022508 for instructions.