We'd love to hear from you! Provide  feedback  to earn a badge today. Take our quick survey
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

Multiple steps versus lesser steps in Order Management Algorithm for OM to Receivables Integration

edited Jun 9, 2021 8:19AM in Order Management


How does application behaves in terms of having more or lesser steps in OM Algorithm for OM to Receivables Integration


There are a couple of data coming from Order Management Sales Order Header and Fulfillment Lines Extensible Flexfields that are sent to the AR Transaction Header and Line Descriptive Flexfields. Those data to be mapped are from various contexts of Order Header Fulfillment Line EFF. In the FulfillmentIntegration service mapping, a couple of custom entities were defined corresponding to each of the EFF context.

The OM Algorithm for InvoiceService defined ended up of  12 Steps. We are looking at bring it down to 6 steps or less by combining some of steps by adding the datasets for other custom entities. Is compacting some of the steps into 1 and reducing the overall total steps in the algorithm impact performance of the application in Create Billing Task?  All the current steps are independent and have no dependency over the other. Will it help to combine steps? Are we gaining in terms for performance?

Howdy, Stranger!

Log In

To view full details, sign in.


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