Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Implementation Notes – Payment Term Validation

edited Aug 23, 2018 10:45AM in Order Management 2 comments

Summary

Dev. update for OM - AR, setting payment term validation

Content

From Oracle Order Management Cloud product team:

What are we recommending: 

Customers using Oracle Order Management Cloud and Receivables Cloud must create a custom submit constraint to enforce payment term with conditions, to filter out the return lines, the internal transfer order lines (destination organization is NULL), the included lines, lines that have been closed, lines with ordered quantity as 0, or lines that have been sent to the Billing system. This is a must have validation.

Customers, who are in 18A or migrating to 18A from an earlier release, are requested to disable the seeded constraint “DOO_FulfillmentLine_PaymentTerms_Missing” after creating or modifying the custom submit constraint for payment term.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!