Distribution - JDE1 (MOSC)

MOSC Banner

Aging limit hold/release functionality

edited Jan 30, 2012 4:01PM in Distribution - JDE1 (MOSC) 1 comment
Hi there,

For those of you who are using JDE XP onwards and have been using the credit/aging hold and release functionalities, I would like to know how you think about the aging checking functionality.

Since XP, JDE has changed the functionality that when checking for whether the customer has exceeded aging limit, it does the checking base on the sales order HEADER's requested date. Prior to XP, it checks base on today's date and see whether the order should be on hold if the customer's outstanding balance has aged over certain period.

This is what Oracle explained the design change: "The assumption is made that if an order is placed with a requested date in the future, any existing accounts receivable will still be outstanding on that future date and on that future date it will no longer be in the current A/R period but will be in a past due period. The customer may very well pay off the outstanding AR invoice before the order requested date is shipped, but there is no way to know that at the time the order is entered"

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center