SETID Inconsistencies
Hello,
We were researching an issue internally when we discovered some SETID inconsistencies in our Financials 9.2.29 instance. We think they may have been introduced through the PUM Lifecycles, but we are unsure at this time. For lack of a better place to post, I chose to post this in the GL Group - but if there are other groups that are better suited, please re-direct accordingly.
We have examples of the following situations:
1. Entries are missing for some SETCNTRLVALUES (in particular, older ones) - namely, we have an entry for one BU, but that entry doesn't exist for an older BU.