E1: 42: Ship Confirm Batch Application (R42500/R47500/P4205) (Doc ID 625613.1)

Last updated on FEBRUARY 17, 2025

Applies to:

JD Edwards EnterpriseOne Sales Order Management - Version XE and later
JD Edwards EnterpriseOne CRM Sales Order Entry - Version XE and later
JD Edwards EnterpriseOne Sales Order Entry - Version XE and later
JD Edwards EnterpriseOne Sales Order Processing - Version XE and later
Information in this document applies to any platform.

Purpose

Overview

The Ship Confirm Batch (R42500) application allows multiple sales orders to be confirmed at one time.

The process updates the EDI Purchase Order Change Header - Inbound (F47131) table and the EDI Purchase Order Change Detail - Inbound (F47132) table. The Ship Confirm Batch (R42500) application calls the Inbound Transaction Processor (R47500) which also uses the EDI Purchase Order Change Header - Inbound (F47131) table and the EDI Purchase Order Change Detail - Inbound (F47132) table.

Note: Despite the use of the system 47 tables, this is NOT an EDI process (i.e. 945 EDI Transaction Set Shipping Advice); the tables are merely 'borrowed' from EDI as work files. Running Inbound Transaction Processor (R47500) by itself is NOT supported. The process was designed to be run as part of the Ship Confirm Batch (R42500) process. Inbound Transaction Processor (R47500) is used to streamline batch processing.

Note 2: The R42500 is only used for sales orders that are NOT using Transportation (system 49).

The batch process used for Transportation Ship Confirm is the R49500 – this will correctly update the sales order statuses and the status of the shipment associated with the sales order. If the R42500 is used, these statuses will not be handled correctly.