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: 

EMIGALL Security Deposit Payment

ivor_martin
Active Contributor
0 Kudos
474

Hello Colleagues,

We're have migrated Security Deposit Request documents and are now try to Pay the requests using the PAYMENT migration object.

We're supplying the Origin Key "RZ".

Structure FKKPOK contains the G/L (Clearing Account for Payment) and the Payment Amount (BETRW) (e.g. 100)

Structure SELTNS contains the Security Deposit Request FI-CA doc#(OIBEL) and the Amount is the Payment Amount (e.g. 100)

Result:

While the Deposit Request is cleared/Paid, there are 2 open items additionally posted :

Main/Sub 0060/0010 = 100- (open credit on acct)

Main/Sub 0060/0020 = 100 (open debit on acct)

We do not want the additional postings.

Any insights would be really appreciated.

Thanks a lot in advance.

Regards,

Ivor Martin

1 ACCEPTED SOLUTION

AmlanBanerjee
Active Contributor
0 Kudos
227

Hi Ivor,

Rather than using the payment migration object for migrating the SD payments, I would suggest you to create a payment lot containing the legacy payments for SD and post it in SAP, during the migration period.

It will follow the normal SAP process for clearing the statistical items and would not create the additional line items.

Thanks,

Amlan

View solution in original post

2 REPLIES 2

AmlanBanerjee
Active Contributor
0 Kudos
228

Hi Ivor,

Rather than using the payment migration object for migrating the SD payments, I would suggest you to create a payment lot containing the legacy payments for SD and post it in SAP, during the migration period.

It will follow the normal SAP process for clearing the statistical items and would not create the additional line items.

Thanks,

Amlan

0 Kudos
227

Hi Amlan,

Thanks for your useful suggestion.

We'll proceed as you suggest, without wasting time trying to figure out why the Payment migration object is acting up.

Regards,

Ivor