Skip navigation

2015 Year-End 1099 is fast approaching!  The information below provides you with list to help you have a successful 1099 season:

  • September/October 2015
    • Get familiar with our EnterpriseOne 1099 knowledge resources (they share ALL training a new 1099 user will need).
      • Bookmark - Troubleshooting Assistant: 1099 Year End Processing (Doc ID 1594456.2)
      • Bookmark - VIP - How To Verify Supplier and Company Setup for 1099 Year End Processing [Video] (Doc ID 661098.1)
  • November 2015
    • Get ready for ESU release to come by middle of December 2015.
      • IMPORTANT!! Read 1099 Year-End ESU: Resolving 1099 Processing Errors Due to ESU Install - HowTo Obtain, Install and Verify Installation of the ESU (Doc ID 1596756.1)
        • Tip - VIP - Must do full force merge to "replace" all objects.
        • Tip - VIP - All Suppliers and Companies MUST have a Tax ID populated in Address Book for combining 1099 table builds to work properly!
  • December 2015
    • Estimated ESU Delivery (by mid December)
      • Bookmark - Important Yearly 1099 Year End Processing Bug/ESU Information For JD Edwards EnterpriseOne [Video]
  • January 2016
    • Printing your 1099s
  • February 2016
    • If you have less than 250 1099s, print 1099 to file to the I.R.S to meet deadline.
    • Note - Use electronic filing even if under 250 1099s as it saves time and office supply stock expense.
  • March 2016
    • Electronic Filing to I.R.S
  • April 2016 thru May 2016
    • Learn how to create 1099 corrections, if required.
  • Season will be complete!

Please subscribe to 2015 1099 - "Get Ready Campaign" - Live Growing Discussion for the 2015 Tax Reporting Season! community discussion and get the latest information.

Rounding2.jpgWhen using Match Voucher to Open Receipt (P4314) to voucher match a multi-currency order with retainage, a mismatch between the F43121, F43121T, F0911, and F0411 can occur resulting in R09801 post failing and producing an R09801E Out of Balance Post Error Report.

 

A new processing option has been added to Match Voucher to Open Receipts (P4314) to address the small variance calculated during voucher match.

 

 

Before the enhancement, rounding issues existed when a logged voucher was matched with purchase order lines that included. Additionally, before the enhancement, rounding issues existed when a non logged voucher was matched with retainage entered at voucher match. Taxes were calculated for one single amount of the logged voucher while the purchase order may contain many lines. A small difference may result between the logged voucher total amount and the amount posted to the general ledger. For non logged vouchers, the small difference may results when retainage is calculated for the amount during voucher match.

                                            

A difference caused by the prior logged voucher issue is calculated by checking the amount of the voucher and comparing it with the total of the general ledger amount. This entry is recorded in the purchaser order detail account (DMAAI 4332) depending on "Voucher Match Variance Account" flag (ON/OFF) in Line Type Constants. The difference is recorded only when the Last Chance Variance is ON in the P4314 processing option.

 

For non logged voucher, the difference is written to the purchase order detail account (DMAAI 4330) when the processing option Account For Rounding Differences in Process tab of P4314 is populated with a value and the difference is within the value in the processing option.

 

Note: Only the above mentioned rounding scenarios are handled in this bug. Scenarios such as large amount variances caused by changing an amount during voucher, variances caused by changing the exchange rate during voucher, and/or variances caused by changing tax amounts during voucher are not handled under this bug.

 

To obtain the enhanced functionality, install the ESU for the following Bug:

Percent.jpgThe Percent To Fill field provides you with the flexibility to fill an order line from one or more branch/plants. The Inventory Commitment preferences work with the system's normal checking that is done for quantity available, and adds a check on all branches that are defined in the preference.

 

What you should know when using Inventory Commitment Preference

  • You must activate the Inventory Commitment preference through a separate processing option in the Sales Order Entry program (P4210).
  • The Inventory Commitment preference does not function with kits or configured items.

 

If the value in the Percent To Fill field is zero percent (0%), the system performs normal processing. The system performs no checking for the quantity on hand.  Regardless of the quantity on hand, it is shipped to fill the order.

 

If the value in the Percent to Fill field is between 1 and 99 percent (1-99%), the system requires that any branch must be able to fill the percentage that is specified. If the branch can fulfill the percentage, the quantity available is shipped and the remainder is transferred to the next branch. The system checks each branch to determine if the quantity can be shipped.

 

If you specify a percent-to-fill value of 100 percent (100%) for each of several branch/plants, an order can only be filled from a single branch/plant that has sufficient quantity to fill the order. If no branch/plant has sufficient quantity to fill 100 percent of the order, the order is put on backorder or partially shipped from the first preference branch/plant that it can satisfy.

 

If the percent to fill value is 100 percent (100%), the system requires that the branch must be able to ship the entire quantity. This prevents shipping from multiple branches, but enables the system to check all branches to determine if the entire quantity can be shipped. If you specify a percent-to-fill value of 100 percent for each of several branch/plants, an order can only be filled from a single branch/plant that has sufficient quantity to fill the order. If no branch/plant has sufficient quantity to fill 100 percent of the order, the order is backordered or partially shipped from the first preference.

 

For additional information, see Inventory Commitment Preference Basic and Advanced Profiles (Doc ID 1641298.1).

We have a new poll Mobile applications (Tablet / Smartphones). Please take just a minute or two and provide your feedback. We would love to have your voice heard.

In an earlier blog we discussed how you can use the Autocash functionality to save time as you can set it up to apply cash receipts to A/R invoices automatically. However,
sometimes you receive money from clients in forms that cannot be processed through your Autocash setup (and this does not happen frequently enough to add to your setup).


For these situations, where you cannot use bulk processing, you can use either of the following cash receipt entry programs:

  • Standard Receipts (P03B102)
  • Speed Receipts (P03B0001)


Regardless of which program you use to enter manual receipts, there are three steps to the process:

  1. Enter the receipt
  2. Review the receipt, and revise it if necessary
  3. Post the receipt

 

Before you can enter a receipt, make sure that the following is set up:

  • Set up these AAIs and make sure that the G/L accounts attached to them exist and can be used by the G/L Post (R09801):
    • RKD for discounts taken.
    • RCxxxx, where xxxx is the chargeback G/L offset code, for the chargeback A/R trade account.
    • RAxx, where xx is the write-off reason code.
    • RN, for the deduction suspense account.
  • Set up these UDC tables for any reason codes you want to use:
    • 00/DE for discount reason codes
    • 03B/CB for chargeback reason codes
    • 03B/RC for write-off reason codes
    • 03B/CR for deduction reason codes      

 

When you create a receipt, the system creates at least two records in the following tables:

  • A receipt header record that stores the amount of the receipt, the check number, receipt and general ledger dates, and so on. The system stores receipt header records in the Receipts Header table (F03B13).  There is only ever one record per receipt in this table.
  • A receipt detail record that stores the amount of the receipt that is applied to each invoice. The system stores receipt detail records in the Receipts Detail table (F03B14). There is one record for each invoice matched on the receipt, and one for each standalone record (write-off, deduction, or chargeback), and one for any amount left unapplied


In the receipt header there are two date fields:

      • the Receipt Date
      • the G/L Date


The Receipt Date field can be set to the date on which you enter the receipt into the system, or it can be set to the date on the customer’s check, or to the date on which the EFT payment from the customer came in, for example. However, the system does not use this date field for anything, so it is for informational purposes only.


The G/L date on the other hand is used for the following:

      • exchange rate calculations,
      • to determine whether a discount is earned, and
      • to update account information when you post the receipt. 

 

Because the system uses the general ledger date for so many reasons, you cannot change the general ledger date after you enter the receipt, even if the receipt is not
posted yet.


To apply a receipt manually to an invoice, you need to use something called a Type Input Code. This Type Input Code will automatically calculate amounts to apply for payments, discounts, write-offs, chargebacks, and deductions. The following Type Input Codes are available:

      • 10: Simple Invoice Match
      • 11: Invoice Match with Automatic Chargeback for Discount Amount
      • 15: Invoice Match with Write-Off
      • 16: Invoice Match with Chargeback
      • 17: Invoice Match with Deduction
      • 25: Stand-alone write-off
      • 26 (Stand-alone chargeback)
      • 27 (Stand-alone deduction)


There is much more to processing standard receipts than can be included, so if you need more information, please have a look at the following knowledge articles:

      • E1: 03B: How To Create and Manage Manual Receipts In EnterpriseOne Accounts Receivable (P03B102, P03B0001) (Doc ID 1451219.1)
      • E1: 03B: FAQ - Frequently Asked Questions on Accounts Receivable Manual Receipts (P03B102, P03B0001) (Doc ID 625851.1):

NewFeature.pngThe U.S. Department of Labor published a final rule that reduces reporting requirements for federal contractors and subcontractors who hire and employ veterans under provisions of the Vietnam Era Veterans' Readjustment Assistance Act of 1974, as amended VEVRAA.

 

The final rule revises the VETS-100A Report and renames it the VETS-4212 Report. The VETS-100 Report will no longer be used. The VETS-4212 Report requires contractors to report specified information on protected veterans in their workforce in the aggregate, rather than for each category of veterans protected under the statute, reducing the required reporting elements by almost half, from 82 to 42. Under VEVRAA, the term "protected veterans" includes: disabled veterans, veterans who served on active duty during a war or campaign for which a campaign badge was authorized, veterans who were awarded an Armed Forces Service Medal and recently separated veterans.

 

Refer to https://federalregister.gov/a/2014-22818 for more information regarding the final rule.

 

JD Edwards EnterpriseOne Human Resources application has been updated to create the required VETS 4212 information.  Access R080436 (VETS-4212 Employment Report) for your reporting requirements.

 

To receive the new functionality, refer to Veteran Employment Report (VETS 4212) (Doc ID 2038041.1) and How To Process The Veterans Employment Report (Doc ID 2042542.1) will provide tips on how to generate a successful report.

The Affordable Care Act (ACA) is a buzz word these days for human resource professionals. JD Edwards EnterpriseOne and World products have created a central repository for 'all things ACA'.

 

Please visit JD Edwards EnterpriseOne and World - Affordable Care Act Overview (Doc ID 2038044.2) for information pertaining to:

 

  • Enhancement currently delivered and planned
  • JD Edwards Human Capital Management Position Statement
  • Advisor Webcast details
  • Hours of Service Reporting
  • Health Coverage Information Returns
  • Other documents and resources

 

We encourage you to visit this central source of information periodically to keep yourself abreast of 'all things ACA'.

In a previous Attitude@Altitude blog, Denise Grills, Vice President JD Edwards Content and Communications Engineering, provided insight into the similarities between Internet of Things (IoT) and the opera.

In her latest blog, Denise compares opera and technology, and explains how a powerful, flexible technology foundation with strong industry functionality enables JD Edwards to modernize and innovate its software to meet the demands of the next generation.

 

Read the full blog at Attitude@Altitude. Visit the blog regularly for JD Edwards information, news, opinions, and to engage in debate with JD Edwards leaders. Post your comments - we would love to hear from you

Attention! - The sixth annual JD Edwards Special Issue of Profit Magazine is here.

One of the highlights of this issue is an interview with Lyle Ekdahl, JD Edwards Senior Vice President and General Manager. Read about Lyle's vision for JD Edwards software and the Oracle customers who depend on these modern solutions for measurable and breakthrough return.

 

If you haven't already seen this - it is a great article.

"Changes call for innovation, and innovation leads to progress."


With this quote in mind , we bring to you JD Edwards EnterpriseOne Internet of Things.

 

The Internet of Things (IoT) is the network of physical objects or "things" embedded with electronics, software, sensors, and connectivity to enable objects to exchange data with the production, operator and/or other connected devices. The enormous potential of machine to machine communications for the purpose of solving hitherto intractable business that cost businesses millions of dollars are widely recognized. Now, the affordable hardware and infrastructure to support such communications and business solutions are available.

 

JD Edwards has been working with customers and partners to identify IoT use cases that enable customers to use beacons, sensors, and other devices to gather information and then use JD Edwards EnterpriseOne applications to use the information to solve the business problems.

 

Have a look at JD Edwards EnterpriseOne Integration Platform White Paper in this document : JD Edwards EnterpriseOne Integration Platform Overview (Doc ID 1996534.2)

 

The guide below, describes how to design and create IoT orchestrations for the JD Edwards EnterpriseOne Internet of Things (IoT) Orchestrator. The IoT Orchestrator processes orchestrations to enable the immediate, real-time transformation of raw data from devices to valuable and transaction-capable information in JD Edwards EnterpriseOne.

Guide: https://docs.oracle.com/cd/E24705_01/doc.91/e64166/toc.htm

 

Experience it yourself through the Oracle JDEdwards Videos below :

 

Demo by JD Edwards Labs:

 

 

Check this demonstration on how the IoT Orchestrator can accept input from devices and invoke JD Edwards EnterpriseOne applications:

 

Its vacation time but the piggy bank isn’t quite full enough. Did you know that you can provide your employees with vacation payments before they take vacation leave? You can enter an interim check to pay an employee in advance of a regular pay period. This payment can replace the regular payment for one or more pay periods. If the payment spans one or more pay periods, you must enter a Tax Factor to calculate the taxes for each of the advance pay periods. When you enter an interim payment the Tax Factor field (AAF) is located on the Payment Overrides tab.

You use JD Edwards EnterpriseOne Contract and Service Billing to bill customers for services and goods rendered. JD Edwards Contract and Service Billing offers a suite of features to accommodate the intricacies of both interdivisional and customer billing.  Have you ever wondered which one may be more suited for your billing needs?

 

How To Understand the Difference Between Service Billing (48S) and Contract Billing (52) In EnterpriseOne (Doc ID 626871.1) helps you to decide which application or a combination of applications will work best for your billing needs.  This document gives you a comparison of the major billing processes such as Workfile Generation, Revenue Generation, Invoice Generation and Creating AR and GL Entries.  It also show the major functionality differences in setup and Invoice Generation and highlights some of the advantages and disadvantages of Service Billing and Contract Billing.

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.