Skip to Content
0

Billing related installation via Emigall is happening with 06 reason code

Apr 12, 2017 at 10:46 AM

130

avatar image
Former Member

Dear All,

I am trying to migrate(using Emigall) Installation management object INST_MGMT . The Meter reading Reason is set by default as 21 for 'Meter reading at billing related installation'. But after load completion, it also generates a line item with '06 'meter reading reason however there are no contracts/contract accounts in the system. Ideally this '06' reason code should never have appeared for billing relevant installation. Could you please let us know what could be possible solution for this and what are the preventive measures.

Regards,

Krishanu.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Daniel McCollum Apr 12, 2017 at 07:22 PM
1

Migration Obj: INST_MGMT

Rec data type: DI_CNT

Field Name: NO_AUTOMOVEIN (Migration: No Automatic Move-In Meter Reading)

set to 'X'

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Apr 13, 2017 at 09:02 AM
0

Thanks Daniel for your inputs. However I have checked the same in my migration object structure and could see NO_AUTOMOVEIN is set to 'X' . I've attached the structure that I am using. Please share your thoughts.

Attachments - inst-mgmt-structure1.pnginst-mgmt-structure2.pnginst-mgmt-structure3.pngissue1.pngissue2.png


Show 1 Share
10 |10000 characters needed characters left characters exceeded

The system only takes the NO_AUTOMOVEIN field into account during a billing-related device installation or a full device installation.

Though you appear to be performing a full install from the reading reasons on issue1.png

For each action, you can transfer one data record of the CONTAINER structure. I see you have it as a fixed value,in my experience, I have set the value directly in each record.

Ultimately, somehow the NO_AUTOMOVEIN is not being considered in your dataset. I'd recommend a debug session to identify the failure state.

0