SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

Migrate Collective security deposit payments

Former Member
0 Kudos

Hi,

We are in the process of migrating our open balances and interest charges on customer accounts. For the customer security deposits, we need to migrate the security request as well as their payments.

  In the case of collective accounts, we initially created request at the child level. This created a statistical document at the parent level. However, when we try to apply payment, should we provide the child request number or the parent?

  When we try to provide the collective account, system is saying there are no open items for the account. We are using the standard collective clearing variant '20S' and don't have any custom one build in the system. Do we need to create a new clearing variant for security deposit payment migration on collective accounts?

Please help me with the steps to migrate the security deposit payments on collective accounts.

Regards,

Santosh.

4 REPLIES 4

AmlanBanerjee
Active Contributor
0 Kudos

Hi Santosh,

I don't think the approach that you have taken is correct for migrating the SD and its corresponding payments for collective accounts.

Normally,in collectives, when you bill the child invoices (non-statistical), they roll-up to the parent account to create a Collective invoice (statistical). And when the payment comes in at the parent level, it clears the statistical item first then rolls down to clear the non-statistical items.

However, in your scenario, both the items (at parent and child) are statisitcal items and that's why you are getting the message "There are no open items in the account", as SAP is not able to post the entry.

The best approach would as of now would be to -

(a) Reverse the SD request from child level. It would autmatically reverse the request from parent level.

(b) De-link the parent-child relationship b/w the accounts. So the child accounts will normal accounts.

(c) Post the SD and the corresponding amount at the child accounts (normal accounts).

(d) Link them again with the parent account so that they become child account.

Hope it helps...

Thanks,

Amlan

0 Kudos

Amlan,

Thanks for your response. As per your suggestion, if I de-link the child parent relation and post the charges separately in both accounts, Should I tie them back before making a payment against collective account?

0 Kudos

Hi Santosh,

I would recommend you to post the SD charges at the Child account only after de-linking it from the parent account.

So after the de-linking, the child account becomes a normal contract account.

Now, if you post the SD request and the correpesponding `payment, it will not roll -up to the parent account, as there is no parent child realtionship.

Once you have posted the payment against the child account, and it has cleared the SD request, then you link them back again.

Even you link them up back again, the SD requests and the payment will not roll -up.

Hope it helps...

Thanks,

Amlan

0 Kudos

This issue is fixed now. It was due to a miscoding in the event R42 to set a clearing restriction on any posting happening on collective account. We didn't had to delink the relationship between child and parent account before posting securities.

Amlan, Sorry for not being clear about the issue on our side. Thanks for your inputs.

Regards,

Santosh.