LPC on converted documents.

[Former Member]

We are converting over open FICA documents into SAP. We are also bringing
over the unpaid LPC posted in legacy into SAP.  Now when we turn on dunning in
SAP it is calculating LPC on the unpaid charges converted into SAP though they
were already assesed LPC in the legacy system.  Without converting the dunning
history - is there any way to workaround SAP calculating the LPC again. 

We also do not want to place a dunning lock on the converted charges, since
we want it to flow through the other dunning steps.

We also do no want to completely ignore converted docs from being assessed
for LPC.

One possible solution we were thinking is to pull a list of converted
documents that were already assessed LPC in legacy and load them in a custom
table in SAP.  In dunning when a FICA doc is about to be assessed for LPC we
check this custom table and if an entry exist not include that document for LPC
assessment. 

Please could you share thoughts on how this was handled with other
clients.

[AmlanBanerjee]

Hi Yuvaraj,

I could get the following from your post-

(a) Legacy items for which LPC items have already been calculated in legacy and are migrated over as well, should not incur interest again in SAP.These items should proceed through the dunning treatment path but no LPC should be posted in SAP against them.

(b) Legacy items for which LPC items have not been calculated in legacy should incur interest in SAP, as per the standard functionality.

So, Say a migrated Contract account can have items which satisfy both the above scenarios.So, its not possible to segregate them at the master data level.

Assuming my above understanding is correct, I would suggest you to place an interest lock on for all Legacy documents for which LPC items have already been calculated in legacy at the document level.

If you have not performed the migration yet, the best approach would find a list of all such items and give it your data migration team and ask them to migrate all these documents with an interest lock till 31.12.9999.

So once they migrate over into SAP, and the dunning is turned on, only dunning levels will be incremented and since there will be an interest lock, so no interest will be posted for them as per the standard SAP functionality.

Hope it helps...

Thanks,

Amlan

[Former Member]

Hi Amalan,

Your understanding is right.

We are not calculating Interest in the dunning steps, we are using Charge Schedule to calculate the LPC.  We have already tested and the Interest Lock is not stopping the LPC from being calculated.

Regards,

Yuvaraj.

[AmlanBanerjee]

Hi Yuvavraj,

My assumption was that you were using the standard interest functionality in dunning for posting LPC.. So, if you are using Charge Schedule, placing an interest lock would not help in restricting the LPC from getting posted.

Then the only option as I can see is to enchance event 360.

You can check whether the legacy documents which are going to be dunned have a charge schedule assigned to them in table FKKMAKO or not.

If yes, then you can delete them from the event so that the charges dont get posted.

Or, if there is no link b/w the legacy documents and the LPC charged against them, the only way is enter them into a custom table and check them during dunning as you proposed in your initial post.

Hope it helps...

Thanks,

Amlan