I regularly use TX_CUST_MEMBERSHIP in v15 to make some updates that can't be done in the application, but that table has been deprecated in v16 and I can't seem to find what table now holds that data. Does anyone know where it lives in v16? (We're still testing...)
Thanks!Anne Robichaux
It is T_MEMBERSHIP, some fields aren't quite there. I've started a quick migration document, but I haven't mapped all the fields yet.
Original Field
New Table.Field
avc_amt
?
ben_holder_ind
ben_provider
T_MEMBERSHIP. benefit_provider_no
category_trend
current_status
T_MEMBERSHIP.override_status_id ?
cust_memb_no
T_MEMBERSHIP.id
campaign_no
T_MEMBERSHIP.id => T_CONTRIBUTION.Membership_id
T_CONTRIBUTION.campaign_no
declined
T_MEMBERSHIP. decline_benefits_ind
expr_dt
T_MEMBERSHIP.expiration_dt
init_dt
T_MEMBERSHIP.start_dt ? Need to go back and replace quite a few
memb_amt
memb_level
T_MEMBERSHIP.level_id => T_MEMBERSHIP_LEVEL.id T_MEMBERSHIP_LEVEL.short_desc
memb_org_no
T_MEMBERSHIP.level_id => T_MEMBERSHIP_LEVEL.id => T_MEMBERSHIP_LEVEL.organization_no
memb_trend
T_MEMBERSHIP.level_trend_id
NRR_STATUS
CASE WHEN a.originating_period_id = -1 then 'NE' -- Not a Member WHEN a.originating_period_id in (-7,-8,-2,-3,-4,-5) then 'RN' -- Future, Active, Upgrade, Renewal, Grace and Lapsed ELSE 'RI' -- Reacquisition END as NRR_Status
parent_no
T_MEMBERSHIP.previous_membership
recog_amt
ship_method
T_MEMBERSHIP is the table, but there are three new views that are referenced in the criteria and output sets. Off the top of my head, the views are a current member view, a historic view, and then an all membership view. Can't remember the view names though
Kendall Bingham said:recog_amt
This field has been deprecated, and our Devo folks are missing it in advance (still on v15.x).
VS_MEMBERSHIP_CURRENT
VS_MEMBERSHIP_LATEST
VS_MEMBERSHIP_HISTORY
Also, VS_CONTRIBUTION now has membership columns.
Kendall Bingham said:T_MEMBERSHIP.id => T_CONTRIBUTION.Membership_id T_CONTRIBUTION.campaign_no
It's not quite that simple, as you can have multiple contributions connected to the same membership, all with potentially different campaigns (this was always true, but the campaign from the first contribution was typically assigned to the membership and then left). In a more strategic sense, Tessitura has done away with displaying a campaign with a membership, so I think the general idea is to not consider them as being connected.