In JD Edwards EnterpriseOne 9.2, Voucher Match Automation for all rules now shows summarized pay items on the R4304020, R4304016, and R4304021 Voucher Match Automation reports when summarizing the Accounts Payable Ledger (F0411) summarized. Previously, the reports did not show the F0411 pay item(s) summarized when the actual F0411 pay items were summarized.
For ESU information including the objects updated, see E1: 43: Voucher Match Automation Reports (R4304020, R4304016, R4304021) do not Summarize Accounts Payable Voucher Pay Items on Reports when Summarized in Accounts Payable Ledger (F0411) (Doc ID 2043005.1)
In JD Edwards EnterpriseOne 9.2, a new processing option has been added to the Agreement Master to allow users to validate that an agreement partner (supplier/customer) has been placed on hold. Users can choose to set a warning message or an error message when the partner is on hold or not validate the hold code of the partner.
For additional information including the objects updated and a link to the ESU, see E1: 38: Agreement Master (P38010) Enhanced to Display Error During Agreement Creation if the Supplier is on Hold (Doc ID 2340829.1).
The Supplier Catalog Revision form has been enhanced in the 9.2 release. Previously, when a record was selected on the Work with Supplier Catalog application, the selection criteria was not carried over to the Supplier Catalog revisions form. All records for the given supplier and catalog were displayed.
With the enhancement in 9.2, a new field Item Number has been added in the Work with Supplier Catalog form. If this field contains a value, then the supplier catalog revisions form will only show records for that item, supplier and catalog; otherwise if left blank, all records for catalog and supplier will be displayed on the revisions form. Also if item number is entered in header field, then updation or creation of records is allowed for only that item.
For additional information, see E1: 43: Supplier Catalog Revision (P41061|W41061B) Enhanced to Use Filter for Selection Criteria (Doc ID 1939654.1).
Our Freight Update (R4981) program has been enhanced in the 9.2 and 9.1 releases to continue processing records after encountering an error message. Prior to the enhancement, R4981 stopped processing further records after successful processing first eligible record if it encounters warning message.
For additional information including the objects updated, bugs listed, and links to the Update Center ESUs, see our document E1: 49: Freight Update (R4981) Revised to Continue Processing When a Warning Message is Encountered (Doc ID 2366807.1).
Outbound Inventory Management has been enhanced to provide users with the ability to Generate Outbound Billing Orders (R42I20) triggered by Report Consumption (P42I03) on a monthly basis. Users would like to generate one sales order per Sold To address not per Ship To, as the customer informs the business once a month of all sales done for sales in consignment, hence the customer is expecting to receive only one invoice.
New versions of Generate Outbound Billing Order (R42I20) are provided to allow users to generate one sales order per Sold To address. The new versions use added logic along with specific data sequencing to generate the invoices.
See our document E1: 42I: Generate Outbound Billing Order (R42I20) Triggered By Report Consumption (P42I03) Invoice By Sold To Monthly (Doc ID 2489940.1) for additional information and the objects updated.
Note: Support for Outbound Inventory Management functionality is available for customers who are licensed to the module. Confirmation of a valid contract is required when logging service requests for support of Outbound Inventory Management.
In JD Edwards EnterpriseOne release 9.2 users now have the ability to sort Item Ledger/Cardex (F4111) by Unique Key ID (UKID) value in the Item Ledger application (P4111). The application has been revised to include UKID as a grid column for sorting.
See our document E1: 41: Ability to Sort on Unique Key ID (UKID) in Item Legder/Cardex (P4111) Application (Doc ID 2685732.1).
In JD Edwards EnterpriseOne, the functionality to convert a requisition to a purchase order has been enhanced. Previously, if a Requisition (OR) was created with Buyer Number (ANBY) as blank on the OR header and detail lines and the Buyer Number was added at the time of requisition release (P43060), the Buyer Number (ANBY) was blank on the OP Header (F4301) and populated on the OP Detail (F4311).
With the enhancement, the buyer number of the first detail line will populate on the generated purchase order. If the buyer number is blank on the requisition header, the system retrieves the buyer number from the item record in the Item Branch / Plant program (P41026).
For additional information, see E1: 43: When Converting a Requisition (OR) to a Purchase Order (P43060) the Buyer Number (ANBY) is not Populated on the Purchase Order Header (F4301) (Doc ID 2119862.1).
Functionality 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)
Approval 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)
Sales 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.
A 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)