My Oracle Support Banner

CLOSE_PURCHASE_ORDERS Entity Does Not Update CLOSE_DATE Field In ORDHEAD Table (Doc ID 2955375.1)

Last updated on JUNE 14, 2023

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version 22.1 to 23.1 [Release 22.1 to 23.1]
Information in this document applies to any platform.

Symptoms

CLOSE_PURCHASE_ORDERS entity does not update CLOSE_DATE field in ORDHEAD table

The CLOSE_DATE date field inserted in file ordhead.dat is successfully uploaded using entity CLOSE_PURCHASE_ORDERS but does not update the field in final table ORDHEAD when closing the purchase order.


EXPECTED BEHAVIOR
-----------------------
The close date should be included in the ORDHEAD table when using CLOSE_PURCHASE_ORDERS entity.

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

1-Upload PO (with active status - A and without close date) using CREATE_PURCHASE_ORDERS entity
2-Upload shipment using SHIP_PURCHASE_ORDERS entity
3-Upload receipt using RECEIVE_PURCHASE_ORDERS entity
4-Upload PO (with close status - C and close date) CLOSE_PURCHASE_ORDERS entity

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
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.