My Oracle Support Banner

E1: 40R: R47171 Errors With Transportation Sequencing TSPUR 05 (Doc ID 2388834.1)

Last updated on APRIL 19, 2018

Applies to:

JD Edwards EnterpriseOne Demand Scheduling Execution - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Demand Scheduling

When using Transportation Sequencing with Demand Scheduling and replacing the previous Demand using TSPUR 05 the following error occurs but demand records were updated anyway. If pull signal is populated the error will not be set.

ERROR
-----------------------
Duplicate Demand Detail Record
Informational: Call From : Todd Jacobsen
Contact :
Phone Number :
Tickler Date : 4/4/2018
Subject :
CAUSE . . . EDI Company 00001, Document Number 2112, Document Type SA, Line Number 1.000, Subline Number 1 with quantity of 11 contains duplicate indexing data (Cost Center, Sold To, Ship To, Short Item, Demand Type and Period, Requested Ship Date and Time, Pull Signal, Customer PO, Job Number and Job Sequence Number) which has previously been processed with quantity of 11.

RESOLUTION . . . This EDI record with quantity of 11 will not be processed into System 40R. Review the record. If needed, modify and rerun records as necessary.

EXPECTED BEHAVIOR
-----------------------
Pull signal is not used or required by the Trucking industry and should not be required when doing a replace.

STEPS
-----------------------

1) P03013. Customer Master setup.
 
2) P4906. Carrier Master Revisions. Verify a SCAC code is populated.
 
3) Menu G40R41. P40R20. Demand Rules Revisions.
 
4) P40R21. Demand Processing Cross Reference. Setup a Demand Type of Q for Production Sequencing Demand.
 
5) P40R22. Demand workflow setup.
 
6) P40R23. Product CUM Model setup. CUM tracking off.
 
7) P40R24. Carton CUM Model setup.
 
8) P4104. Item Cross Reference setup.
 
9) Menu G40R11. P47171. Create EDI data for 2 items. Populate Job Number and Job Sequence Number.
 
10) R47171. Copy version XJDE0002. Change WF option to K47171DWF and submit over EDI data.
 
11) The UBE will complete and Demand is created. Review the data in DemandTables.xls and note that records were created correctly
 
12) P47171. Remove the SP = Y record from all EDI data then set the Transaction Set Purpose to 05 for Replace in the EDI header and change the quantity on both lines to 11.
 
13) R47171. Run the UBE again which should replace existing data even if nothing has changed. The following shows in the PDF. Duplicate EDI Schedule Record above has been bypassed and message sent to Work Center
 
14) Work Center. Note the following error message stating Pull Signal must be different which in this case was never populated in the first place. Pull Signal is not used in the Trucking industry with PACCAR, Navistar, etc.

Duplicate Demand Detail Record
Informational: Call From : Todd Jacobsen
Contact :
Phone Number :
Tickler Date : 4/4/2018
Subject :
CAUSE . . . EDI Company 00001, Document Number 2112, Document Type SA, Line Number 1.000, Subline Number 1 with quantity of 11 contains duplicate indexing data (Cost Center, Sold To, Ship To, Short Item, Demand Type and Period, Requested Ship Date and Time, Pull Signal, Customer PO, Job Number and Job Sequence Number) which has previously been processed with quantity of 11.

RESOLUTION . . . This EDI record with quantity of 11 will not be processed into System 40R. Review the record. If needed, modify and rerun records as necessary.

15) Review the data in DemandTables.xls and note that records were created even though the above error states otherwise.

16) P47171. Remove the SP = Y record from all EDI data then populate the pull signal in both demand schedule records.
 
17) R47171. Run the UBE again since the previous error stated no records were processed when in fact they were. The UBE completes with no errors.
 
18) Review the data in DemandTables.xls and note that records were created

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Trucking manufacturers like Navistar and Paccar do not use the pull signal and will never pass it into the EDI data. On the E1 side this causes an error to be thrown thereby making the user think the data did not process when in fact it did. This causes extra costs to manually populate a faux pull signal when it is not required for the trucking industry.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.