E1: 46: 49: 42: F49211 Incorrectly Updated after Pick Confirm (P4617) (Doc ID 2285171.1)

Last updated on JULY 11, 2017

Applies to:

JD Edwards EnterpriseOne Warehouse Management - Version 9.2 and later
JD Edwards EnterpriseOne Transportation Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When confirming a pick suggestion in P4617 for a order that uses the Ship Ascending Dates Advanced Lot Preference, the system is wrongly updating the F49211 [Sales Order Detail File - Tag File] for the fields Check Sell By Date (SBCK), Check Expiration Date (EDCK), Commitment Date Method (CMDM), Check
Best Before Date (BBCK) to BLANK.
 

The issue can be reproduced at will with the following steps:
1. Advanced Preference setup for item and customer where all fields are active (Check Sell By Date (SBCK), Check Expiration Date (EDCK), Commitment Date Method (CMDM), Check Best Before Date (BBCK) fields set to 1)
2. The process will take into account the information in table F4239 for the last lot shipped for the customer.
3. Item availability - have multiple lots with multiple expiration dates
4. P4210 Enter a transportation order.
5. Make sure the Ship Ascending Dates Advanced Lot Preference is being used by checking the F49211 table. In this tables the order is displayed with the Check Sell By Date (SBCK), Check Expiration Date (EDCK), Commitment Date Method (CMDM), Check Best Before Date (BBCK) fields set to 1.
6. P4915 ¿ approve the shipment
7. When approving the shipment a pick request is created for the entire quantity of the order.
8. R46171 generate suggestions.
9. The system will generate multiple suggestions based on the lots.
10. P4617 confirm one of the suggestions.
11. Check F4211. The sales order lines are split as per the suggested quantity
12. Check F49211. A new line is added but the Check Sell By Date (SBCK), Check Expiration Date (EDCK), Commitment Date Method (CMDM), Check Best Before Date (BBCK) fields are BLANK instead of 1.
13. Ship Confirm the line P4205
14. Notice the last lot is not updated in F4239 because the fields were not populated in F49211.


Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms