Let’s say I create a Sales Order with header level...
# arm
h
Let’s say I create a Sales Order with header level start and end dates of, for example, 2019/1/1 and 2019/12/31, respectively, with ARM enabled. Then I create two transaction line items with item level start and end dates of: Item 1 – 2019/1/1 and 2019/6/30, respectively Item 2 – 2019/7/1 and 2019/12/31, respectively In this case I just have two items for which I want to recognize revenue in those distinct periods. Once I go to update Revenue Arrangements and Revenue Elements, each of the Revenue Elements corresponding to Items 1 & 2 have a start and end date of 2019/1/1 and 2019/12/31, ignoring the item level dates I input. I can work around this by going into the associated Revenue Arrangement and manually editing each Revenue Element’s date fields, but is there a way to have the Revenue Element source the values the way I want to begin with, natively?
j
I might be wrong, but you could try setting the items' Allocation Type to Exclude Otherwise it all gets bundled into one amortization schedule, I believe
k
@HL - to make this work you have to create rev rec rules for these items where REv Rec Start (and End) Date Source is Revenue Element date. I also suggest Recognition method as SL exact days and Amt Source as event % based on Amt. this way you won’t need to update Rev Element
h
@Karina That's actually already the setup of the rev rec rule the item is using unfortunately.
k
@HL - you can update items with new rev rec rules, no?
h
Yes, for sure. But I guess I don't see how that affects how the Revenue Element sources its own start/end dates from the Sales Order to start with
k
@HL - not sure what it means. Perhaps this is about already posted SOs - then no, it won’t affect them, they will need to edited manually