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: 

EMIGALL, DEVINFOREC - probs with reg.codes/factors for multiple registers

Former Member
0 Kudos
369

Hi, guys!

I have a problem with the migration object DEVINFOREC in EMIGALL. When I try to create a device info record with two registers, I don't get the fields register code (field KENNZIFF in structure DVMREG) and register factor (ZWFAKT in structure DVMREG) updated for the second register!!! The first register is OK, but for the second one, "nothing happens".

I'm using the flags KENNZIFF and ZWFAKT in structure DVMRFL. The problem I have here is, that it seems that only ONE entry of the DVMRFL record is allowed and therefor I can only update the first register (I think!!!).

When I tried to create an extra DVMRFL record with register number 002, I get an error saying:

Data error in automation data of device modification

Message no. EN262

Diagnosis

An error occurred in table reg_flag for automation data. The following lines are unpermissible.

Date 01.01.2001 - 31.12.9999

Equipment (device) DEV_0001

Register 002

-


This is the input file to EMIGALL for DEVINFOREC:

900000000012345682 DVMINT 01 E02 DEV_0001

900000000012345682 DVMDEV DEV_0001 4416 E02

900000000012345682 DVMDFL DEV_0001 E02

900000000012345682 DVMREG DEV_0001 E02 001 E10 10,00000

900000000012345682 DVMREG DEV_0001 E02 002 E11 10,00000

900000000012345682 DVMRFL DEV_0001 E02 001

900000000012345682 &ENDE

In the file above I would like to create a device info record called DEV_0001 with two registers with register factor 10 and with register codes E10 for register 1 and E11 for register 2.

When I look at the device info record in trx EG43, I can see that only the first register is updated correctly. For the second register the register factor is 1 and the register code is empty.

Suggestions, anyone?

Thanx in advance!

With regards,

Tony

Edited by: TonyN64 on Apr 27, 2011 9:45 AM

3 REPLIES 3

Former Member
0 Kudos
194

Hi Tony,

If you're still interested have a look:

12312312 DVMINT 20080322 DEV1234

12312312 DVMDEV 99991231 20080322 DEV1234 Info devinfo

12312312 DVMDFL 99991231 20080322 DEV1234 X

12312312 DVMREG DEV1234 001 99991231 20080322

12312312 DVMREG DEV1234 002 99991231 20080322

12312312 DVMRFL 99991231 20080322 DEV1234 001

12312312 DVMRFL 99991231 20080322 DEV1234 002

12312312 &ENDE

I didn't migrate the fields you need (for DVMREG structure), but the problem seems to be the 2nd DVMRFL which is missing in your sample.

Good luck,

Catalin

Former Member
0 Kudos
194

Hi Catalin!

Thanx 4 your answer!

I'm aware of the second missing DVMRFL record, but as I wrote earlier, when I had two DVMRFL entries in the file, I got an error message!!! Are you saying you don't get an error with the file below?

With kind regards,

Tony

-


12312312 DVMINT 20080322 DEV1234

12312312 DVMDEV 99991231 20080322 DEV1234 Info devinfo

12312312 DVMDFL 99991231 20080322 DEV1234 X

12312312 DVMREG DEV1234 001 99991231 20080322

12312312 DVMREG DEV1234 002 99991231 20080322

12312312 DVMRFL 99991231 20080322 DEV1234 001

12312312 DVMRFL 99991231 20080322 DEV1234 002

12312312 &ENDE

0 Kudos
194

Hi Tony,

Migration was ok for this object (DEVINFOREC).

Maybe this will help you (customer structure of DEVINFOREC object):

We suppose that material(MATNR) generic used for creation of device inforecords is called 'DEVINFOREC'.

DataType: DVMINT

Fld CTyp DTyp DLen To Short descriptn.

KEYDATE 3 DATS 8 Key Date for Selection According to Time-Related Validity

SPARTE 2 CHAR 2 Division --- constant: 02 -gas

MATNR 2 CHAR 18 Material Number --- constant: DEVINFOREC for example

GERAET 3 CHAR 18 Device

DataType: DVMDEV

Fld CTyp DTyp DLen To Short descriptn.

BIS 3 DATS 8 Date at Which a Time Slice Expires

AB 3 DATS 8 Date from which time slice is valid

GERAET 3 CHAR 18 Device

MATNR 2 CHAR 18 Device category --- constant: DEVINFOREC for ex

EGERR_INFO 3 CHAR 30 Information Field of Device Info Record

DataType: DVMDFL

Fld CTyp DTyp DLen To Short descriptn.

BIS 3 DATS 8 Date at Which a Time Slice Expires

AB 3 DATS 8 Date from which time slice is valid

GERAET 3 CHAR 18 Device

MATNR 2 CHAR 18 Device category --- constant: DEVINFOREC for ex

EGERR_INFO 3 CHAR 1 Indicators

DataType: DVMREG

Fld CTyp DTyp DLen To Short descriptn.

GERAET 3 CHAR 18 Device

MATNR 2 CHAR 18 Material Number --- constant: DEVINFOREC for ex

ZWNUMMER 3 NUMC 3 Register

BIS 3 DATS 8 Date at Which a Time Slice Expires

AB 3 DATS 8 Date from which time slice is valid

CALOR_AREA 3 CHAR 8 Calorific value district

DataType: DVMRFL

Fld CTyp DTyp DLen To Short descriptn.

BIS 3 DATS 8 Date at Which a Time Slice Expires

AB 3 DATS 8 Date from which time slice is valid

GERAET 3 CHAR 18 Device

MATNR 2 CHAR 18 Device category --- constant: DEVINFOREC for ex

ZWNUMMER 3 NUMC 3 Register

CALOR_AREA 3 CHAR 1 Indicators

Bellow is a sample of 3 records from a file which was imported:

K10073 DVMINT 20080101 K10073

K10073 DVMDEV 99991231 20080101 K10073 BL. B1 SC.2

K10073 DVMDFL 99991231 20080101 K10073 BL. B1 SC.2

K10073 DVMREG K10073 001 99991231 20080101

K10073 DVMREG K10073 002 99991231 20080101

K10073 DVMRFL 99991231 20080101 K10073 001

K10073 DVMRFL 99991231 20080101 K10073 002

K10073 &ENDE

K10074 DVMINT 20080101 K10074

K10074 DVMDEV 99991231 20080101 K10074 BL. B1 SC.3

K10074 DVMDFL 99991231 20080101 K10074 BL. B1 SC.3

K10074 DVMREG K10074 001 99991231 20080101

K10074 DVMREG K10074 002 99991231 20080101

K10074 DVMRFL 99991231 20080101 K10074 001

K10074 DVMRFL 99991231 20080101 K10074 002

K10074 &ENDE

K10075 DVMINT 20080101 K10075

K10075 DVMDEV 99991231 20080101 K10075 BL. B1 SC.4

K10075 DVMDFL 99991231 20080101 K10075 BL. B1 SC.4

K10075 DVMREG K10075 001 99991231 20080101

K10075 DVMREG K10075 002 99991231 20080101

K10075 DVMRFL 99991231 20080101 K10075 001

K10075 DVMRFL 99991231 20080101 K10075 002

K10075 &ENDE

Service module for DEVINFOREC object is: ISU_S_SMALL_DEVICE_CREATE

with following parameters:

Export

X_DEVICE EMG_DEVMOD_INT-GERAET

X_MATNR EMG_DEVMOD_INT-MATNR

X_DEVISION

X_KEYDATE EMG_DEVMOD_INT-KEYDATE

X_UPD_ONLINE U_ONLINE

X_NO_DIALOG N_DIALOG

X_AUTO AUTO

X_OBJ

X_INT_NUM

X_EXT_NUM

Import

Y_DB_UPDATE DB_UPDATE

Y_EXIT_TYPE

Y_EQUNR EGERR-EQUNR

Y_DEVICE

Good luck,

Catalin