Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 3523

Disconnection Notification randomly picks the connection object which is not desirable according to business requirement

$
0
0

Hi Experts:

 

We are using SAP standard program to create the disconnection document and then the disconnection order and then the disconnection notification.

 

For example, we created a disconnection document #123.  This disconnection document finds 2 devices as its disconnection object - device E is a electric meter and device W is a water meter.  In most of the cases, one contract account has both electric meter and water meter and they are located in same premise (i.e. same connection object).  However, a few contract accounts have device E in premise A and device W in premise B.  In this case, our business requirement is to go to premise A to disconnect the electric meter instead of going to premise B to disconnect the water meter (as we only collect water bills on behalf of the City and we do not have rights to turn off the water).

 

We are using workflow, which calls the standard business object DISCONNECT-> method DARKCREATEOFDCORDER to create the disconnection order.  This "method" eventually calls a FM "ISU_DISCDOC_CREATE_NOTIFIC" to create the disconnection notification.  This function module performs a subroutine "order_get_bzgobj".  This subroutine finds all equipments' functional location and their respective connection objects (from view V_EGPL) and randomly picks the first connection object on the list as the connection object of the notification.   In this case, premise B's connection object is picked and saved in ILOA table. 

 

ehau.PNG

 

Any idea how other companies deal with this type of situation?  Is there a place where I can put user exit with the custom logic in order to pick the most desirable connection object for disconnection notification? 

 

Thanks.

Jennifer


Viewing all articles
Browse latest Browse all 3523

Trending Articles