Skip navigation

JDE EnterpriseOne Support Blog

14 Posts authored by: Teodors-Oracle

The Single Euro Payments Area (SEPA) is a payment-integration initiative of the European Union for simplification of bank transfers denominated in Euro. SEPA is used in the European Union (EU) countries and in a few countries outside of EU that use Euro. SEPA’s goal was to reduce the costs of doing cross border transactions in the Euro currency. SEPA electronic payment formats were developed for both Accounts Payable (SEPA Credit Transfer) and for Accounts Receivable (SEPA Direct Debit. SEPA was based on subsets of ISO20022 standard.

 

JD Edwards implemented SEPA electronic payments for both Accounts Payable and Accounts Receivable. In order to obtain all the features one needs to apply the ESUs returned by the SEPA query for their release in the Change Assistant tool. For more info on how to install and use the Change Assistant tool please see Frequently Asked Questions For Change Assistant Tool - "How To" Questions (Doc ID 1057524.1).

 

These would be found in the navigation tree under: Search for Packages> JD Edwards > Electronic Software Updates > Localizations.

 

Example:

Packages> JD Edwards > Electronic Software Updates > Localizations >SEPA 9.2.

 

SEPA for Accounts Payable was implemented as a separate Payment Print Program in the existing Automatic Payments process. SEPA for Accounts Receivable was implemented as an automatic debit program in the existing Automatic Debits process. They both make use of Report Definitions.

 

The documentation for SEPA can be found in the localization manuals:

  1. 9.2 JD Edwards EnterpriseOne Applications Localizations for European Reporting and SEPA Processing Implementation Guide.
  2. 9.1 JD Edwards EnterpriseOne Applications Localizations for European Reporting and SEPA Processing Implementation Guide

The Create Payment Control Group PDF (R04570) has been enhanced to provide a better user experience. The enhancement allows Accounts Payable users to more easily validate banking information when running electronic funds transfer payments.

 

The enhancement includes the following changes to the PDF output of the Create Payment Control Group (R04570):

  • In the header portion of the PDF:
    • The Payment Control Group number has been added. This number is stored in the automatic payment temporary tables A/P Payment Control Group (F04571), A/P Payment Header (F04572) and A/P Payment Detail (F04573).
    • The Bank Account Number displays both formatted and unformatted numbers. The Bank Account Information is stored in the Bank Account table (F0030).
  • In the detail portion of the PDF:
    • IBAN, SWIFT and Control Digit Information is printed for each supplier, if applicable. The Supplier’s bank account details are stored in the Bank Account table (F0030).
    • Label headings for all the bank related information (Bank Acc #, Transit #, IBAN, SWIFT and Ctrl Digit) have been added.

 

The addition of the IBAN info will help European customers where the IBAN is the standard Bank Account identifier and should be used in conjunction with another Enhancement for Bank Accounts by Address (P0030A) that added the possibility to configure which Bank Account identifier is a required field. See New Enhancement - Configured Required Bank Account Numbers in Bank Accounts by Address (P0030A) (Doc ID 2435342.1) mentioned in New KM Document About the Configured Required Bank Account Numbers Enhancement for Accounts Receivable and Accounts Payable blog post.

 

For the Create Payment Control Group enhancement see New Enhancement Create Payment Control Group for EnterpriseOne Releases 9.1 and 9.2 (R04570) (Doc ID 2418789.1).

Report Definitions bring the power of Oracle BI Publisher to JD Edwards EnterpriseOne users. With Report Definitions one can easily make various changes to standard reports output. Additionally Report Definitions can automatically e-mail parts of the output to e-mail addresses of Address Book entities from the reports without the need to learn Report Design Aid. This feature is called Data Driven E-Mail and can be leveraged in various scenarios. One such scenario is to e-mail the Print Payment PDFs (R04572ZZ) of the Print Payment Programs called by the Automatic Payment process. This KM document shows a very basic example of how to achieve this: How to e-mail Accounts Payable Payment Print PDFs to Suppliers using Report Definitions (Doc ID 1908922.1).

 

Other scenarios where this feature can be leveraged are: for e-mailing AR Notifications, for e-mailing AR Invoice Print output, etc.

Besides the traditional methods import/export JDE transactions to other applications and systems using Batch Processing, Interoperability tables or EDI, JD Edwards Enterprise One offers a lot of standard Business Services (BSSVs).  They enable software applications that are written in various programming languages and are running on various platforms to exchange information. BSSVs are based on widely used open standards like XML, SOAP, and WSDL. Because they are based on open standards, the knowledge for creating BSSVs interfaces is widely available. Also there are numerous third party programs and APIs for running SOAP/WSDL calls.

 

The standard Business Service for Accounts Payable is the Accounts Payable Manager (JP040000) has two methods:

  • processVoucher – for importing Vouchers into JDE
  • getVoucher – for exporting Voucher details to third party systems

 

The JD Edwards Enterprise One component that runs BSSVs is the Business Services Server (BSSV Server).

 

Basically if one wants to import voucher details from JDE they have to compile an xml file with the SOAP request for the processVoucher method. The file will have all the needed details of the voucher plus SOAP formatting specifics. Then they need to submit the SOAP request to the JDE BSSV Server. The BSSV Server will reply with a SOAP response that will confirm the transaction or with an error message.

 

To export vouchers from JDE one will have compile an xml file with the SOAP request for the getVoucher method. The request will include all the details to locate the voucher. After submitting the SOAP request to the JDE BSSV Server they will receive a SOAP response with all the voucher details.

 

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

 

More information can be found in:

Batch Approval and Post Security (P00241) restricts the approval and posting of batches to certain users. You may also want to restrict unauthorized users from viewing batches other than their own in the General Journal Review program (P0011). The Batch Approval/Post Security Constants establishes User Group Authority to be implemented for the Accounts Receivable, Accounts Payable and General Ledger modules. Each system can be set independently of the other systems. Additionally, batch approval and post security is not strictly limited to financial batches. The system security also applies to batches that feed into the financial systems, such as inventory and manufacturing.

 

More details on how this feature works can be found in:

  • Overview of Batch Approval and Post Security Setup (P00241/P0000) (Doc ID 664703.1)
  • Frequently Asked Questions on the Batch Approval and Post Security Setup (P00241) (Doc ID 664702.1)

The VAT Information Exchange System (VIES) is an electronic means of transmitting information relating to VAT registration (i.e., validity of VAT numbers) of companies registered in the European Union. EU law requires that, where goods or services are procured within the EU, VAT must be paid only in the member state where the purchaser resides. For this reason, suppliers need an easy way to validate the VAT numbers presented by purchasers. This validation is performed through VIES.

 

VIES does not itself maintain a VAT number database. Instead, it forwards the VAT number validation query to the database of the member state concerned and, upon reply, it transmits back to the inquirer the information provided by the member state. This information includes at least a "YES/NO" answer on the existence and validity of the supplied number. It may also include additional information, such as the holder's name and address, if this is provided by the member state.

 

The VIES also provides a Web Service that can be used by various applications to automatically do the VAT ID validation.

 

As of release 9.0 the JD Edwards EnterpriseOne added a feature that allows VAT ID validation for the Address Book records in European Union countries via the VIES Web Service. Before that there used to be separate business functions to validate the Tax IDs in various EU countries. The VIES validation can be turned off and in that case the individual country validations are still available (see E1: 74: How To Set Up Address Book Tax ID Validation for EMEA Localization (Doc ID 625787.1)) and can be used, but the new VIES validation streamlines the process.

 

Besides validations when adding and changing Address Book records there is also an UBE that does batch validations (Validate VAT ID VIES program (R74101) for the existing Address Book records.

 

In order to take advantage of this feature one needs to do some setup to allow the JD Edwards to communicate with the VIES Web Service. Find more on how to set up and use VIES in:

JD Edwards EnterpriseOne Working With the VIES to Validate EU VAT IDs (Doc ID 1193855.1)

 

How to use information is available in the 9.2 JD Edwards EnterpriseOne Applications Tax Processing Implementation Guide.

 

Setup information for Tools Release 9.2 can be found in the 9.2 JD Edwards EnterpriseOne Applications Business Interfaces Implementation Guide.

The assignment of a Tax Rate/Area to an Invoice, Sales Order, Voucher, or Purchase Order has been based upon the value provided in the Business Unit, Customer, or Supplier master. In the European Union, tax rates are different based upon the type of transaction as well as the origin and destination countries. This enhancement allows for an alternate method of assigning the Tax Rate/Area. This method is optional and can be turned on for specific companies as well as countries. The alternate tax rate/area assignment feature enables you to define the default tax rate/area to use based on a combination of the following fields:

  • Company
  • Ship From Country Code
  • Ship To Country Code
  • Transaction Source
  • Customer or Supplier Number

 

To find out what ESUs to apply for this feature check document JD Edwards EnterpriseOne Globalizations: Localizations, Translations, Certifications/Registrations (Doc ID 752291.1). The detailed description of Alternate Tax Rate Area Assignment is in the JD Edwards EnterpriseOne Applications Tax Processing Implementation Guide.

As of JD Edwards EnterpriseOne 9.1 the following mobile applications are available, to review and approve batches on mobile devices (tablets and smartphones). JD Edwards EnterpriseOne Batch Approvals for Smartphone and Tablet enhancement enables you to review transactions within a batch and approve the batch to be posted (journals, vouchers, payments, invoices and receipts).

 

The following applications work with Tools Release 9.1.4.6 and above and are called from Work With Batches application (P0011) in the JD Edwards EnterpriseOne system to review and approve batches:

  •     G/L Batch Approvals (available for Tablet and Smartphone)
  •     Invoice Batch Approvals (available for Tablet and Smartphone)
  •     Receipt Batch Approvals (available for Tablet and Smartphone)
  •     Voucher Batch Approvals (available for Tablet and Smartphone).

 

For more information on how to install and how they work see Overview Mobile Batch Applications in Accounts Payable, Accounts Receivable and General Accounting (Doc ID 1935777.1).

 

As of Tools Release 9.1.5 it is possible to review and approve Payment Batches.

  •     Payment Batch Approvals (available for Tablet and Smartphone).

 

This application is also called from the Work With Batches application (P0011). For more information on how to install and how they work see Overview Payment Batch Approval Mobile Applications in Accounts Payable (M04132/ M04131) (Doc ID 1964847.1).

 

Another useful reference for JD Edwards EnterpriseOne Mobile Applications is in: JD Edwards EnterpriseOne Mobile Applications (Doc ID 1637232.2).

Before 9.1 when A/R Receipt and A/P Payment entries were written to the G/L, the Document Company(alias KCO) was set to 00000. For business reasons many customers wanted to enforce restrictions by company via Row Security. And because the Document Company (alias KCO) was always 00000 for Accounts Receivable receipts and Accounts Payable payments they tried setting the Row Security by Company (alias CO) which was not part of the keys for the F0911 table.

 

This caused issues when generating the Automatic Entries for posting payments or receipts. When a payment or a receipt was in process of being written into the Account Ledger (F0911) table the system did a check to determine if the key values already existed. Security by CO could have prevented this check from finding existing records. Then the insert into F0911 table failed because the documents were duplicates based on the fact that all payments and receipts were written to Document Company (alias KCO) 00000 and that the Company (alias CO) is not part of the key for table F0911.

 

To address this issue in 9.1 the A/P Bank Account Company and the A/R Receipt Header Company are written to the Document Company for the G/L entries. We have added a new Next Number by Company for A/R Receipts to ensure the integrity of the  Next Numbers. A/P Next Numbers are not affected as they already exist. More information related to this can be found in Document Company (KCO) in the Account Ledger (F0911) Table for Accounts Payable Payments and Accounts Receivable Receipts (Doc ID 2187671.1).

Business services in JD Edwards EnterpriseOne are objects that enable interoperability between JD Edwards EnterpriseOne and other Oracle 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. They are based on widely used open standards like XML, SOAP, WSDL.

 

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.

 

Published business services are exposed to consumers. Internal business services are created for internal use by JD Edwards EnterpriseOne published business services. They are made available to consumers as a call from a published business service. Business services that are exposed to consumers are exposed as web service operations.

 

Numerous Business Services were implemented to allow interoperability of the Financials modules with third party systems. They allow importing and/or exporting Accounts Payable, Accounts Receivable and General Ledger transactions, Address Book, Customer Master, Supplier Master, Business Unit Master, Chart of Accounts, Companies information and others.

 

The list of available Business Services and usage details can be found in the Oracle JD Edwards Technical Catalog searching for Business Interfaces and Business Services.

 

To find out the capabilities of specific Business Services see:

 

http://docs.oracle.com/cd/E16582_01/doc.91/e38040/additional_info.htm#EOAAA1431

 

More information can be found in:

 

        Oracle JD Edwards Technical Catalog (Doc ID 1361438.1)

        Or in the JD Edwards EnterpriseOne Applications Business Interfaces Implementation Guide

        How To Test a Business Service deployed to a WebLogic Business Services Server using SOAPUI (Doc ID 1122313.1)

As of JD Edwards EnterpriseOne 9.1 Update 2, the Work with Batches application was enhanced to allow specifying the version of the G/L Post (R09801) to be submitted for different batch types. Use the UDC for Post Version by Batch Type (09/PV) to have the system select the post version by batch type when submitting the post from the Work with Batches program. When you run the GL Post program (R09801) for each financial batch type, the system first selects the version of the GL Post by Batch type from the UDC (09/PV). If the batch type is not found in this UDC table, the system will call the Batch Versions (P98305) with the GL Post (R09801) preselected and it uses the version specified in the Batch Versions (P98305) for the GL Post. If an invalid version is selected, the system displays an error message.

 

See this documented in the JD Edwards EnterpriseOne Applications Financial Management Fundamentals Implementation Guide.

JD Edwards EnterpriseOne One View Reporting is a real time operational reporting solution designed specifically for end users. An intuitive interface empowers users to access and personalize transactional data into lists, charts, graphs, and tables. With One View Reporting, users can select the data fields and perform specific data selection from within JD Edwards EnterpriseOne applications and leverage the layout capabilities within Oracle BI Publisher to define the report output formatting. It was first introduced with JD Edwards EnterpriseOne Applications release 9.1 and later it was also offered for Applications release 9.0.

 

One View Reporting enables end users to create and run One View reports based on Business Views using search criteria in applications (standard or custom Find Browse Forms) or even in Data Browser. These reports are typically specific to the user or role and are those that the user will run on a daily, weekly, or other periodic basis as part of their normal activities. With this type of report users are allowed a high degree of personalization regarding data selection, sequencing, data columns included, and data visualization (charts, tables, graphs). These end-user reports improve user productivity by providing users with better visibility into operational data as part of their standard day-to-day business process. Common use cases are customer reports, supplier reports, sales reports, and employee reports.


Together with the One View reporting feature a number of dedicated standard One View Applications and Reports were added for various JD Edwards EnterpriseOne modules.

 

In Financial Management new One View Applications were added for General Accounting, Accounts Payable and Accounts Receivable. Standard One View Reports for various use cases are delivered with each One View Application.

  

General Accounting

  • One View G/L Inquiry (P09219). One View G/L Inquiry can be used to analyze General Ledger transactions. It is based on the One View G/L Inquiry (F0911-F0901-F0006) Business View (V09219), which includes columns from the Account Ledger table (F0911), Account Master table (F0901), and Business Unit Master table (F0006).
  • One View Account Balance Inquiry application (P09217). One View Account Balance Inquiry can be used to report on account balances. It is based on the One View Account Balance Inquiry business view (V09217), which includes columns from the Account Balance table (F0902), F0901, and F0006.

  

Accounts Receivable

  • One View Customer Ledger Inquiry application (P03B2022). One View Customer Ledger Inquiry uses the One View Customer Ledger Inquiry Business View (V03B11I) (which includes columns from the Customer Ledger table (F03B11) and Customer Line of Business Master table (F03012)) to analyze the Customer Ledger.
  • One View Customer Receipt/Draft Inquiry application (P03B720). One View Receipt/Draft Inquiry should be used to inquire on Receipt/Draft transactions. It is based on the One View Receipt Draft Inquiry Business View (V03B720), which includes columns from the Receipt Detail table (F03B14), Receipt Header table (F03B13), and Customer Master table (F03012).
  • One View Supplier Ledger Inquiry application (P042022). One View Supplier Ledger Inquiry can be used to analyze supplier ledger transactions. It is based on the One View Supplier Ledger Inquiry Business View (V042022), which includes columns from the Accounts Payable Ledger table (F0411), Supplier Master table (F0401), and the Address Book table (F0101).
  • One View Supplier Payment Inquiry application (P04720). One View Supplier Payment Inquiry can be used to inquire on supplier payment transactions. It is based on the One View Supplier Payment Inquiry Business View (V04720), which includes columns from the Payment Detail table (F0414), Payment Header table (F0413), F0401, and F0101.  

 

JD Edwards EnterpriseOne Applications One View Reporting User Guide

 

With the One View Reporting for Financial Management Chapter

 

For an Administrative perspective check the JD Edwards EnterpriseOne Tools One View Administration Guide

The Real-Time Grid Summarization was added with the Tools Release 9.1.5. This new feature enables users to click on specific grid columns for which data will be totaled and summarized in new easy to view formats. Previously, users were required to navigate to the bottom of the grid to find totals, a process that is time consuming and is likely to cause system time out with a very large numbers of grid rows. With real-time summarization, users have immediate access to critical totals. The return of totals in milliseconds to seconds rather than minutes to hours results in better real-time decision-making and shortens the time to complete key business processes such as closing financial books and forecasting.

 

A number of existing applications were redesigned to take advantage of this Tools feature. Find below the applications and the corresponding BUGs :

 

P03B2002

 Customer Ledger Inquiry

ESU via BUG 19933280

P0411

 Supplier Ledger InquiryESU via BUG 19933310
P09200 Work with Account LedgerESU via BUG 19933326

P09201

 Work With Account Ledger by Object AccountESU via BUG 19933326

P09202

 Work With Account Ledger by Category CodeESU via BUG 19933326

P3460

Work with Forecasts

ESU via BUG 19933344

P42101

Sales Order Entry

ESU via BUG 19933362

P4310 Work With Order Headers

ESU via BUG 19933381

 

Additional details about this new feature and the applications that were redesigned can be found in the following documents: 

  • Frequently Asked Questions for JD Edwards EnterpriseOne Real-Time Summarization (Doc ID 1965855.1)
  • Frequently Asked Questions for JD Edwards EnterpriseOne Real-Time Financial Reconciliation and Oracle Database In-Memory (Doc ID 1965857.1)

  

The “FAQ Real Time Summarization” attachment from Frequently Asked Questions for JD Edwards EnterpriseOne Real-Time Summarization (Doc ID 1965855.1) includes a screen capture with the Summarization feature in the Customer Ledger Inquiry (P03B2002) program.

 

For detailed instructions on accessing the Real-Time Summarization feature, see these implementation guides.

JD Edwards EnterpriseOne Applications Accounts Payable Implementation Guide:

Using Real-Time Summarization in the Standard Voucher Entry Program (P0411)

 

JD Edwards EnterpriseOne Applications Accounts Receivable Implementation Guide:

Working with Customer Ledger Information

JD Edwards EnterpriseOne Applications General Accounting Implementation Guide

Using Real-Time Summarization in the Account Ledger Inquiry Program (P09200)

Using Real-Time Summarization in the Account Inquiry by Object Account Program (P09201)

Using Real-Time Summarization in the Account Inquiry by Category Code Program (P09202)

Automatic Table Cache Refresh is an enhancement added with release 9.1 Update 2. This new feature provides for the automatic clearing of certain table caches when updates occur. This will enable data to be changed and made available to users without the downtime previously associated with this process.

 

Many applications that update data in JD Edwards EnterpriseOne have been modified to enable this automatic clearing of the table cache. A typical example of such an application is the Company Constants (P0010) application. Table caching is a feature within JD Edwards EnterpriseOne that improves the performance of many applications. This is done by caching tables that are very often accessed for many processes to limit the number of database operations. These tables contain setup data such as constants and master tables. The main characteristic of cached tables is that the data in these tables does not change on a regular basis. One limitation of table caching is that if data is updated, users do not have immediate access to the new information.

 

In order to use this feature it is necessary to obtain the modified code for each application where the feature is used and to do some specific set up.

 

For the list of bugs check document Oracle Announces JD Edwards EnterpriseOne 9.1 Automatic Table Cache Refresh (Doc ID 1595627.1).

 

And for the setup details check the JD Edwards EnterpriseOne System Administration Guide (27.3 Resetting Database Table Cache Using a Pre-Configured Application), link from 9.1.x Tools manual.

 

 

 


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.