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: 

Not possible to update operand EQ_N_DAYS to the installation facts

Former Member
0 Kudos

Hi,

Please help how to handle following error message......

Not possible to update operand EQ_N_DAYS to the installation facts

Message no. AJ056

Diagnosis

Values were calculated in billing for operand EQ_N_DAYS that are to be updated in the installation facts. However, the update could not be carried out because installation facts already exist in the period in which the update is to be carried out (20.12.2008 - 15.01.2009).

The following cases may have occurred:

For the operand there is already an installation fact whose from-date is in the period 20.12.2008 - 15.01.2009.

For the operand there is already an installation fact whose to-date is past the period 20.12.2008 - 15.01.2009.

System Response

The value could not be updated in the installation facts in the above situations. Therefore, the update was terminated.

With Regards,

Sunil

1 ACCEPTED SOLUTION

rajesh_popat3
Active Participant
0 Kudos

Hi,

As per my understanding, the operand EQ_N_DAYS would be a runtime operand, whose value would be updated to installation fact during run time (billing execution) along with the billing document no. generated at that time.

For your case, it seems that this operand value has been maintained manually in the installation fact.

So, please delete the time slice value for this operand in the installation fact and try to bill the account, the value for this operand should get updated and the billing should get executed successfully.

If the value of the operand for the period you billing, is already present in the installation facts (maintained manually), this kind of error occurs.

Hope this helps!!

Regards,

Rajesh Popat

View solution in original post

4 REPLIES 4

rajesh_popat3
Active Participant
0 Kudos

Hi,

As per my understanding, the operand EQ_N_DAYS would be a runtime operand, whose value would be updated to installation fact during run time (billing execution) along with the billing document no. generated at that time.

For your case, it seems that this operand value has been maintained manually in the installation fact.

So, please delete the time slice value for this operand in the installation fact and try to bill the account, the value for this operand should get updated and the billing should get executed successfully.

If the value of the operand for the period you billing, is already present in the installation facts (maintained manually), this kind of error occurs.

Hope this helps!!

Regards,

Rajesh Popat

0 Kudos

Hi Rajesh,

Thanks for the reply, I have to update the Oprand during creation of billing document. there is no time slice created for this but still showing the error.

With regards,

Sunil

rajesh_popat3
Active Participant
0 Kudos

Hi Sunil,

Could you please check, on the installation fact, if the value for this operand is already present for the same period used for billing.

Basically, when the operand is updated during billing, the operand (run time), also has the billing document no. along with the period for which it was updated on installation fact.

If by any chance, the value is maintained for this operand manually on the installation fact (the billing doc no. field on the operand value would be blank), it would give the " update error: value for this operand for that period already present on installation fact".

If that is the case, please delete the values maintained for the operand on the installation fact for that period (having billing doc no blank) and then re execute the billing.

Hope this might be of some help!!

Regards,

Rajesh Popat

0 Kudos

Hi Rajesh,

As i confirmed there was no value or time slice for the operand, But this was because of the seasonal operand I am using which hasn't been considered during the billing period. Now this problem is resolved.

Thanks with regards,

Sunil