Everh initial download of multiple product time slices

[kevin_dewilde]

Hi all,

We're doing an initial download of contracts from IS-U to CRM, but we have ran into a serious issue...

Take this scenario:

Installation has a move-in date of 01.01.2012. Since that dat the following rate cat changes have taken place:

1. 01.01.2012 - 31.12.2012 RATE A
2. 01.01.2013 - 30_06.2013 RATE B
3. 01.07.2013 - 31.12.9999 RATE C

By default the program to fill the EVERH table for initial download only supports 1 rate/product per contract. However, in this case we'd need to send 3 product slices for one contract to CRM.

We already changed the program so that it takes the correct product for a giving rate cat, but we cannot get the multiple slices to work.

Does anyone have experience with this issue? Can anyone please provide some insight on how to correctly fill EVERH for multiple products slices in one contract for initial load?

Thanks!

[Astrid_Gambill]

Hi Kevin

We didn't try to convert the full rate history and just downloaded the rate C.  The CRM side of things is complicated with product changes and to get the systems in sync you'd have to replicate the rate A and rate B product timeslices into CRM as well as having them in EVERH.

What's the business need for needing to see the full history in CRM?  for the occasions when it's needed our CSRs use ECC for a quick check on the rate history.

Regards

Astrid

[kevin_dewilde]

Astrid,

We have two issues with only pushing the last slice:

1) reversal processes in CRM. We cannot reverse the product changes one-by-one if we don't have the full rate cat history. Also because in the installation the field rate cat is locked as soon as you change a contract in CRM (standard behaviour to avoid mismatches between ISU rate cats and CRM products). Furthermore, we discovered there's a standard check in the MDT logic to make sure all product slices align with installation rate cat slices, as of the move-in date.

2) if we push only the last slice, I believe we would loose the notion of move-in date of ISU. If we try to load the last slice with the original move-in date we run again in the timeslice check of point 1.

So the real business need is just to be able to do all processes and all process reversals in CRM, also for contracts and products/rate cat that originate from ISU.

[Former Member]

Dear Kevin,

The rate categories have changed in the installation if I am not wrong.

There are a couple of ways to go with your situation.

You can map this scenario by properly designing the MDT- CRM Product combination.

I would suggest you create separate products for each rate category.

In general the constants in the MDT of node INSTALLATION and all of its

subnodes decides if the right product is found.

All the constants in the MDT have to be the same like in installation

AND contract.

If you run report ECRM_GENERATE_EVERH for a contract, the system

first determines which MDT's are possible in general.

Now within report ECRM_GENERATE_EVERH at line 223 there is a call of

function module ISU_MDG_READ_ANL_NODE and within this two times the

call of function module ISU_CRM_TABLE_MATCH.

Within this function module the system checks explicitely if the values

of constants of MDT are the same as in the contract and installation.

There is also the possibility to use the BAdI ISU_EVERH_XREPLCNTL to

determine the product by an own logic (note 1638578 explains it).

Regards

Ullas Saffarulla