My Oracle Support Banner

E1: 42: Existing Credit Hold Over Writen Via Sales BSSV (Doc ID 2205080.1)

Last updated on FEBRUARY 03, 2019

Applies to:

JD Edwards EnterpriseOne Sales Order Entry - Version 9.1 and later
Information in this document applies to any platform.


On : 9.1 version, BSSV

When a hold is applied via the P4210 we lock down the hold code field so users are not able to override it. When using the processSalesOrder BSSV it allows you to enter new hold codes that get written to the F4209 and overrides the existing credit hold in the header as long as the new hold code that is alphabetically before the current hold code.

You should not be allowed to add a new hold code to a sales order if the header file is currently populated with a hold code. The functionality should be the same as P4210 where we disable the hold code field in the header.

The issue can be reproduced at will with the following steps:
1) Create a new sales order via BSSV or P4210 that goes on credit hold.
2) Update the order via BSSV and add another hold code that is an order level hold.

3) Review work with held orders and the 2nd hold code was added.
4) Release the credit hold.
5) The second hold code is not updated in the header.
6) Update the order via BSSV and add another order level hold code that is alphabetically before the current hold code.

7) P4210. Review the order and the C2 credit hold has been replaced by the A1 hold code.

The issue has the following business impact:
Due to this issue a valid credit hold on the order header can be replaced without releasing the hold via the P43070.


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

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