on ‎2018 Jan 26 3:41 PM
Hi All , I am currently working on a FM that can trigger Re-connection order once customer had fully paid their debts. When a customer's invoices overdue for 6 months and accumulated to a certain amount , we will trigger DC request and the worker proceed to disconnect the supply. Previously customer will pay at the counter and request for re-connection. The counter staff will then trigger Re-connection order manually in SAP.
Things changes , client currently has payment kiosk on site. Some DC customers paid via kiosk and been complaining that they paid in full but no Re-connection performed.
Reason being , kiosk post payment to SAP but we do not have any linkage to the current DC and RC module.
I am looking at EDISCDOC, EDISCOBJ, EDISC* tables that store the disconnection information. But it only contain Ref Object Key which is either Installation, Logical Register Number (From Device) or Business Partner.
For payment purposes , to get the CA of the installation, I look at EVER table where Installation = EVER-ANLAGE then look for the Contract Account = EVER-VKONTO.
Should I get my ABAP team to union 2 tables ? We afraid that it will slow down the performance of Kiosk. Is there any work around ?
Request clarification before answering.
I am confused by this. Standard functionality for dunning disconnections will enable reconnection when payment is made. Why are you building something that already exists?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 11 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.