It worked. Thanks so much!

Thanks @Avinash A In the Filters, I can't see the Custom label I added for the Formula(Text) in Results Subtab. If I just add Formula (Text) again directly, it doesn't show the option to add Formula again to it. [Sorry, if these are dumb questions!]

Thanks! How can I get only the lines in the results when the formula returns 'T' i.e different Bill To and Ship To

Thanks!

I wish we could talk in person and explain more :)

Yes, the computation is correct in both cases and because all the amounts and FX on source TX and RA and Rev Elements is the same, we don't understand why Rev Plan FX and Amount are different in both instances. P.S: Thanks for trying hard to help!

Thanks @Patrick Fresnosa-Oracle as always! I could add the formula finally in my Rev Element SS to get Rev Plan Per period amount in Contract Curr! Here is the one I used which might be helpful for others too! ROUND({revenueplan.lineamount}/{revenueplan.exchangerate},2)

Hi @Patrick Fresnosa-Oracle If we have to calculate the Foreign Currency Amount per Posting/planned period of a Revenue Plan in a custom saved search, how can we do it? I am using Formula (Numeric) in Saved Search Results for below formula but it is giving an error. Can you please help?…

Thanks Patrick for trying! Yes, the Plan FX Rate will be the same on all revenue elements of merged RA but our issue is this plan FX rate in one NS Instance is not matching with the plan FX Rate in other NS Instance!

Thanks! Let me try to explain -> We need to migrate some Open SOs from one NS Instance to another (Both NS Instances have different existing configs) -> For the Open SOs, the Rev Rec Rules are migrated as is (with same rev rec method) to be used in the NS instance where it is being migrated to -> The allocation is kept the…

Hi @Patrick Fresnosa-Oracle , The Start and End Dates are the same on both instances for all Rev Elements. However, when tested recently, we found that the order of operations on the merged Revenue Arrangements might be causing the issue. I am sure its hard to debug when there is not enough info/access to the the instance…

Hi @Patrick Fresnosa-Oracle Thanks for your response! Unfortunately, I cannot share the screenshots here, too much info to hide! Let me provide a little bit more background here which might help. We have two separate NS Instances (two different companies now merged!) where we are trying to migrate Open Sales orders…

Thanks @Clarisa De Torres-Oracle You answered all my questions. I guess we will have to write a custom script to Uncheck the Compliant Checkbox for all RAs that need to be reallocated!

Thanks @Patrick Fresnosa-Oracle That's exactly how I did it and was working until I got light on other requirement that the nested KIT (PF KIT Item Nov 2023 from your example) can come as an individual/Standalone KIT as well without Parent Item ( PF KIT Items Nov 2023 (Nest) from your example) and in that case the…

Thanks @Patrick Fresnosa-Oracle I don't have access to the link you posted.. Just to clarify, here is an example of two scenarios: Parent KIT has Child Items: CI1, CI2 and CI3. CI3 is Nested KIT Item with further Child Items NCI1 and NCI2 Scenario 1: Nested KIT Sales Order has One Line: Parent KIT has Sales Price of…

The NS Rev Plan Fields " Hold Revenue Recognition" and "Catch up Period" are very closely coupled. As per NS Documentation Catchup Period : This field is used only when the check is cleared from the Hold Revenue Recognition box. When the hold is removed, the catch up period defaults according to the option selected in the…

Thanks for your quick response! I tested it in SB and looks like it will work. The only question I have is that what default catchup period does NS use when it is blank in case the Hold is removed. Also, we would still need custom script to update for all existing open plans!

Thanks @timblun ! This is very informative. However, I found that instead of updating anything else on Revenue Plan (Rev Rec End Date etc), if we put the plans on Hold and then remove the Hold, it triggers the adjustment of split period automatically in Rev Plans. Did you try that? Do you see any negative consequences of…

Hi @timblun We are in the same situation where we split the accounting period and would like to adjust the revenue plans for the two split periods for one! As you mentioned, we couldn't do it via "Update Revenue Plans". It doesn't trigger the adjustment of accounting period update (split) in the plans for existing Revenue…

Thanks!

Thanks @Tigran Shahnazaryan! That is what we are doing now to update Individual Revenue Plan by changing the allocated amounts.

Hi @Patrick Fresnosa-Oracle Sorry for the typo. The Custom field is actually at the Revenue Arrangement header/body level and not at revenue element level.

We use Revenue Field Mapping for some Transaction fields but not all! The Custom field is on the RA Line right now but I can add it to SO Custom Form as well.

Thanks! I am just trying to find another workaround than creating the script. Can we add the custom field at Sales order level and RA level and populate it on SO TX via csv upload and then run update RA which I assume should update the custom field?

Thanks @Tigran Shahnazaryan SuiteScript would mean developing a custom script to perform this one time update? Please confirm.

Thanks for all the solutions. We went through the Script creation route and were able to see the expected results!

Thanks so much @Katerina Winklerova-Oracle I tested this setup in our Sandbox instance and it worked. Many Thanks!

We have had only two sales orders for same date (12/9/2022) with this issue. I have the SOAP Request and Response for a recent transaction but it has too much confidential information and it is hard to remove all of it but I can ensure you that there is no field named "exchangerate" in it. Hope it helps

Thanks @Leonard Mallare-Oracle for your response! I can provide generic SOAP Request for another Sales Order as we retain only 1 month SOAP Requests/responses in NS currently and this Sales order with incorrect FX Rate is older than that!

Thanks!