E1: 43. Purchase Order Planned Effective Date and Work Day Calendar (Doc ID 2291141.1)

Last updated on JULY 27, 2017

Applies to:

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

Symptoms

Purchase Order Entry (P4310)

ACTUAL BEHAVIOR
When a purchase order is created with a Promised Delivery Date that falls on a Friday and the Purchasing Effective Days (PEFD) is set to 2 on the Item Branch (F4102) record, the Planned Effective Date on the Purchase Order is populated with a date which falls on a Sunday.

EXPECTED BEHAVIOR
The client wants the PO Entry (P4310) program to use the Work Day Calendar in calculating the Planned Effective Date. In this example instead of calculating a Planned Effective Date on Sunday, it would calculate a Planned Effective Date of Tuesday.

The issue can be reproduced at will with the following steps:

  1. On the Lot Processing Tab of the Item Branch Revisions Screen (P41026) the Purchasing Effective Days (PEFD) is set to 2. These 2 days are needed to inspect and put away the material after it is received.
  2. When the Purchase Order is entered (P4310), for the item the Promised Delivery Date is entered as Friday, 8/4/2017.
  3. Based on the Purchasing Effective Days of 2, the Planned Effective Date when the lot will be available to promise to a sales customer is calculated as Sunday, 8/6/2017.
  4. However the real date that the material would be ready would be 8/8/2017 because the warehouse is not working on the weekend and would not have the items ready to be sent out on Sunday.

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