Skip navigation
1 2 3 Previous Next

JDE EnterpriseOne Support Blog

31 Posts authored by: Peggyhr-Oracle

dollar signs.jpgFunctionality has been added in the 9.2 release to create separate General Ledger (F0911) journal entries for procurement price adjustments. When a procurement voucher is created with the new 4371 AAI configured, the system saves the actual cost and adjustment amounts in separate accounts associated with this AAI in the General Ledger table (F0911).

 

If the 4371 AAI is not configured, the system does not separate the journal entries for advanced pricing adjustments.

 

Adjustment types Accrued to GL and Rebate are not applicable for the 4371 AAI.

 

For additional information, see our knowledge document Actual Cost and Adjustment Amount AAI (4371) Introduced to Separate General Ledger (F0911) Entries for Procurement Price Adjustments Created in Match Voucher to Open Receipt (P4314) (Doc ID 2643177.1)

mail.jpgApproval processing has been enhanced to pass a user identified P43081 version dynamically so that the hyperlink will be populated with the correct version.

 

The originator can define the version of the Purchase Order Approvals program (P43081) while placing an order. The approver can also define the version of the P43081 program while approving or rejecting the order. The version of the P43081 program specified by the originator can be different from the version specified by the approver.

 

When a Purchase Order is entered in the Purchase Order Entry program (P4310) and awaits approval, the system sends mail notification to the approver. When the order is approved or rejected in Purchase Order Approvals (P43081), the system sends email notification to the originator.  When the approval authority is transferred in Work With Approval Level Revisions (P43008) or when approval authority is delegated in Work With Approval Delegation (P43280), the system sends the email notification for pending approval orders to new the approver.  While using the hyperlink from the email, approval review program (P43081) always launched with the hard-coded ZJDE0001 version.

 

For more information, see our document Purchase Order Approval (P43081) Enhanced to Allow User Defined Email Notification Version (Doc ID 2643135.1)

 

971429.pngSales Update (R42800) has been enhanced to create zero balance adjustment general ledger entries for all cost methods.

 

Two new AAIs, 4226 (Inventory) and 4228 (Expense or COGS), have been added to allow sales update to record the accounting entries for the zero balance adjustment.

 

The inventory integrity reports have been modified to utilize the new 4226 and 4228 AAIs when evaluating the item ledger (F4111) and general ledger (F0911) to identify the zero balance adjustment entries.

 

For additional information including a list of the ESUs to install and the objects updated by the enhancement, see Sales Update (R42800) Creates Zero Balance Adjustment General Ledger Entries (F0911) for All Cost Methods (Doc ID 2640788.1)

An enhancement has recently been delivered to allow users to choose to use the Invoice Date to update the exchange rate on a sales order.  Historically, Invoice Print (R42565) and Sales Update (R42800) have not have the functionality to update the exchange rate based on the invoice date.

 

Sales Order Batch Price / Cost Update (R42950) has been enhanced to provide the functionality to update the exchange rate based on the invoice date when calling from R42565 or R42800.

 

Now, if you have a delay between the time the sales order processes through invoice print and the time the sales order processes through Sales Update, a processing option on Sales Order Batch Price / Cost Update (R42950)  allows you to select the exchange rate based on the invoice date.  The default option is to  select the exchange rate based on the system date.

 

For additional information, see Sales Order Batch Price / Cost Update (R42950) Enhanced to Provide Functionality to Calculate Exchange Rate Based on the Invoice Date During Sales Update (R42800) (Doc ID 2302364.1)

A new processing option has been added to Returned Materials Authorization (P400511) in 9.2 to provide the flexibility when creating purchase orders. The new processing option allows user to specify if the Branch Plant and location defined in the RMA defaults will be populated to the purchase order fields or if the values from the original sales order are used for the purchase order.

 

See KM document E1: 42: RMA Receipt Location as Defined in Return Materials Authorization Defaults (P40052) Able to be Used When Performing the Credit Order from History Function in Returned Material Authorization (P40051) (Doc ID 2619716.1) for a review of the objects updated and a sneak peek at the new processing option.

Purchasing Clipart - Clip Art LibraryA recent enhancement in 9.2 updated the PO wrapper functions to include the managerial cost codes and types from the Purchase Order Detail Tag File (F4311T) in the generated XMLs for RTPOOUT and RTPOOUT2. ESU for Bug 30446174 delivers the updated objects.

 

For a complete list of the updated objects, see KM document E1: 43: Cost Object and Cost Object Type Fields in Purchase Order Detail Tag File (F4311T) Added to Generated XMLs for RTPOOUT/RTPOOUT2 (Doc ID 2538769.1).

Many customers have requested the functionality to use the Batch Transportation Shipment Confirmation UBE (R49500) to confirm Standard and Standard Intransit loads. With the 9.2 enhancement available in the ESU for Bug 13012700, Batch Transportation Shipment Confirmation (R49500) has been modified to allow confirmation of Standard and Standard Intransit loads. Compartmentalized and Compartmentalized Intransit loads cannot be confirmed in batch and still must be confirmed interactively using Work with Loads / Load Confirmation (P4960/P49640).

 

Two new processing options have been added to R49500. The first processing option allows users to choose to retain the current functionality to disable load confirmation or to activate the functionality to enable load confirmation. The second new processing option  allows users to specify a version of Transportation Load Confirmation (P49640) during the load confirmation process. The P49640 version indicates the load, shipment, and sales order status values used for confirming standard Intransit and standard Non-Intransite loads.

 

For complete information, see our knowledge document Transportation Batch Ship Confirm (R49500) Allows Confirmation of Standard and Standard Intransit Loads (Doc ID 2161470.1)

Record reservation functionality is available in a number of programs in EnterpriseOne.  With a recent 9.2 update, record reservation has been added to the Print Delivery Notes UBE (R42535) in the 9.2 release. With the ESU installed, if a record is reserved by another program Print Delivery Notes (R42535) will not process the record.

 

See Record Reservation Functionality in Print Delivery Notes (R42535) (Doc ID 2601784.1) for the Bug / ESU information along with post install instructions.

Address Book Data Security / Data Privacy allows you to restrict users from viewing sensitive Address Book information. After performing the required setup for this feature, secured users will be able to see the secured fields, but these fields are populated with asterisks.  These fields are also disabled so no changes can be made.

 

A recent update in the 9.2 release ensures your Address Book Data Privacy carries over to the Purchase Order Entry application (P4310).  See  Data Privacy Setting Functionality Available in Purchase Order Entry (Purchase Order Entry) (Doc ID 2565600.1) for the 9.2 Bug / ESU information.

 

For more information about Address Book Data Privacy, see How To Set Up Address Book Data Privacy In JD Edwards EnterpriseOne (P01138) (Doc ID 1517572.1).

Historically, there has been a difference in the Soft Rounding calculation between Sales Orders and Purchase Orders when using an Item Group (Purchasing Taxable) for Multiple Tax Rate configuration. In the Sales Order module, when Sales Update (R42800) creates Accounts Receivable records (F03B11/F0911), a Soft Rounding for Tax Calculation is done grouped by Tax Area and Item Group. In the Purchase Order module, when Match Voucher to Open Receipts (P4314) creates Accounts Payable records (F0411/F0911) a Soft Rounding for Tax Calculation is done grouped by Tax Area only. The Item Group (Purchasing Taxable) was ignored.

 

An enhancement is now available in releases 9.1 and 9.2 that allows users to choose to enable Voucher Match Tax Rounding by company for Accounts Payable.

 

For more information see Enhancement Available in Match Voucher Match to Open Receipts (P4314) to Allow Soft Rounding for Tax Calculation Grouped by Tax Area and Item Group (Doc ID 2475356.1).

You asked. We delivered.

 

Historically in sales order entry, in order to use existing Available to Promise (ATP) or Cumulative Available to Promise (CATP) calculations to determine a Delivery Date during current sales order entry, the user must exit to the Supply/Demand Inquiry form where the date is displayed and then return the date.

 

An Enhancement is now available in the 9.2 release that streamlines the sales order entry process by allowing for automatic population of sales order dates without having to access the Supply/Demand Inquiry form.

 

The new functionality automatically populates the pick date without having to access the Supply/Demand Inquiry form when the user enters a sales order line for a quantity of an item and tabs to the next line without entering any dates.

 

For more information see Enhancement Available in Sales Order Entry (P4210/P42101) to Automatically Return Pick Date from Available to Promise (ATP) or Cumulative Available to Promise (CATP) (Doc ID 2555461.1)

Have you ever identified a batch that posted completely but not correctly?

 

Maybe, during your review of integrity reports you identified a batch where the AE entry was not created but the remainder of the entries in the batch are posted. Or, you may have identified a batch where the debits do not equal the credits but all the entries in the batch are posted.

 

After researching the batch, you identify the amounts and accounts that are missing entries.  Now what?

 

How do you create a journal entry, or multiple journal entries, to bring the batch back into balance? How do you create a one-sided journal entry and then successfully post the journal entry to update the Account Ledger (F0911) and the Account Balance (F0902) tables?

 

Our knowledge document How To Create and Post a One-Sided Journal Entry (Doc ID 2513031.1) walks you through successfully creating and posting a one-sided journal entry.

impact-clipart-599193-migrateorsynchr_13BED_CLIPART_OF_31983_SMJPG_2.jpg

Are you using the customer credit limits and credit hold codes to effectively manage accounts receivable?

 

Credits granted to your customers are similar to financial loans.  Effective use of the credit limit ensures that the amount of credit granted a customer aligns with the financial abilities of each customer.

 

Setting up a credit limit on a customer account does not mean that new sales orders cannot be created for the customer. In EnterpriseOne, credit holds can be setup based on the customer's credit limit or based on the age of open accounts receivable.  A credit hold on a customer's sales order(s) will prevent further processing of the order, to reduce your risk.  You don't always want to ship items to customers who are poor payers, customers with a history of late payments or missed payments.

 

Did you know that you can record information for credit insurance policies (insured credit limit) in EnterpriseOne?

 

Don't get caught with large noncollectable accounts receivable balances. Review the functionality available in EnterpriseOne in Credit Checking (Doc ID 2319760.2).

 

 

8iE6jn6bT.gifMany suppliers have a business process where they cannot invoice customers until the customer confirms delivery of the product, which completes the supplier’s performance obligation. The elapsed time between shipping and delivery can be as great as 60 days. With this business process, suppliers cannot recognize revenue until the invoice has been posted, which must occur after the performance obligation. Also during the in-transit period the shipping company continues to have legal ownership of the product until it has been accepted by the receiving customer.

 

During this period, the value of in-transit inventory must remain on the balance sheet of the shipping company until the material is received and accepted by the customer. Invoicing and Sales Update processing must be delayed until the material is received and accepted at which time the legal ownership is transferred from the Supplier to the Customer.

 

An enhancement is available in the 9.2 release of JD Edwards EnterpriseOne to provide the functionality to create journal entries for In-Transit Inventory at the time of Ship Confirm (P4205).  For additional information see 9.2 Enhancement - Retaining Ownership of Inventory While In Transit (Doc ID 2246772.1).

An enhancement is available for JD Edwards EnterpriseOne 9.2 customers using the distribution modules.  Refresh Inventory Commitments (R42990) refreshes any inventory commitments in F41021 (Item Location File) where the item does not have any active sales orders associated with it. The existing program, Repost Active Sales Orders (R42995) refreshes the commitments for only those items that have an active sales order. There may be a case where the sales orders are all completed for an item but for some reason there is still an outstanding commitment recorded in F41021 that needs to be cleared out. R42995 will not update this item in F41021.

 

Prior to the enhancement, if no active sales orders exist prior to running the Repost Active Sales Orders (R42995), when R42995 was run for locations that have hard/soft committed buckets filled but no open orders in the Sales Order Detail (F4211) exist, commitments would not be cleared for those Item Locations in the F41021 file. One workaround involved creating a 'dummy' order for the specific item so that R42995 would correctly repost the order. The 'dummy' order would then need to be cancelled after running the Repost Active Sales Orders (R42995) program. Another workaround involved using a database utility program such as SQL to clear the commitment buckets in the Item Location (F41021) prior to running the Repost Active Sales Orders (R42995). This process was more efficient if numerous items need to have the quantities and amounts reposted but do not have an open order in the Sales Order Detail (F4211). This process eliminated the need to create and delete what could be many individual "dummy" orders.

 

For complete information on the enhancement, see Refresh Inventory Commitments (R42990) (Doc ID 2230896.1).

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.