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: 

TE221-LEISTMONAT: demand per month is not operating in removal/inst.

Former Member
0 Kudos

Hi experts, please help:

MR Result rel-billing period:

-


Install.

Log. reg.

MR date

Equipment

Device

Reg.

RR

MR

UMR

Short Descript.

G2074849

1001897703

24.05.2011

5000431771

46038330

2

01

5,200

KW

Periodic Meter Reading

G2074849

1001897703

10.05.2011

5000431771

46038330

2

21

0,000

KW

Meter reading at billing-rel. inst.

G2074849

1000447226

09.05.2011

5000422593

46038857

2

22

6,200

KW

Meter reading at billing-rel. removal

G2074849

1000447226

25.04.2011

5000422593

46038857

2

01

8,300

KW

Periodic Meter Reading

The register operand of watt has set the flag 'Demand per month', so I hope that DEMAND14 get the greatest value (6,2) and not the sum of the two demands (6,2 + 5,2 = 11,4), the latter is what is currently happening.

Thanks.

Regards,

David Ampuero

6 REPLIES 6

william_eastman
Advisor
Advisor
0 Kudos

David:

That is standard functionality - to get the result you desire, you need to ensure that the replacement transaction transfers the logical register number from the first device to the second. If that is not done, then the demand will be added as you see.

regards,

bill.

0 Kudos

Hi Bill:

thanks, but this is another case with the same scenario, but if is operating correctly here.

-


Billing-Relevant Meter-Reading Results

-


Installat.

Log. reg.

MR date

Equipment

Device

Reg.

RR

MR

UMR

Short Descript.

G201097

1001897709

17.02.2011

5000452361

36040428

2

01

1,200

KW

Periodic Meter Reading

G201097

1001897709

29.01.2011

5000452361

36040428

2

21

0,000

KW

Meter reading at billing-rel. inst.

G201097

1001791198

28.01.2011

5003359202

36142615

2

22

1,020

KW

Meter reading at billing-rel. removal

G201097

1001791198

19.01.2011

5003359202

36142615

2

01

1,197

KW

Periodic Meter Reading

After having debugged the function ISU_DEMAND_PROLONG i think that the problem in my first case is that the MR at billing-rel. removal (05.09.2011) has the same month of "Meter reading allocation date" (EABL-ZUORDDAT) that Periodic Meter Reading (05.24.2011), which is: "2011.05".

then, how i do in these cases to get just the peak between Meter reading at billing-rel. removal (05.09.2011) and Periodic Meter Reading (05.24.2011)?

Thanks.

Regards,

David Ampuero

william_eastman
Advisor
Advisor
0 Kudos

As i alluded to in my response, check your logical registers for each device. The demand will be added unless the values are the same.

0 Kudos

But how I can get that to executed the replace of device, the numerator of demand maintain the same logical register number?.

Thanks,

David

0 Kudos

In the replacement transaction this is enabled. also have you tried EG60?

0 Kudos

I execute EG60 and then click "Create proposal", the system assigns the same logical register numbers from device 46038857 to device 46038330, but when I save is displayed the following error:

******************************************************************************************************************************************************

The register specified does not exist in this period

Message no. EN414

Diagnosis

Register 001, device 46038330 does not exist over the entire processing period.

The problem is probably due to one of the following reasons:

The device has not been installed yet.

The device has already been removed.

The logical registers have been prorated.

Upon replacement, no register of the installed device assumed the task of the register from the removed device.

The logical register was prorated when it was maintained.

For more information, please refer to Restrictions for processing register relationships.

System Response

Processing is canceled.

Procedure

Specify a register that exists over the entire processing period.

******************************************************************************************************************************************************

Thanks.

Regards,

David