Measuring Point BDC error

[Former Member]

Hi,

When I am uploading data for IK01(Create Measuring Point), Lower Range limit value in additinal data is always showing zero. During uploading(with processing mode A),whatever data given in flat file it's showing on the screen. But after saving and checking in IK02 the Lower Range limit value in additinal data is showing 0. Please help in resolving this issue.

data: begin of record occurs 0,

• data element: IMRC_MPOTY

MPOTY_001(003),

• data element: IMRC_MPTYP

MPTYP_002(001),

• data element: EQUNR

EQUNR_003(018),

• data element: IMRC_PSORT

PSORT_004(020),

• data element: IMRC_PTTXT

PTTXT_005(040),

• data element: ATNAM

ATNAM_006(030),

• data element: IMRC_DESIC

• data element: IMRC_DECIM

DECIM_011(002),

DESIC_007(022),

• data element: IMRC_PSORT

• PSORT_008(020),

• data element: IMRC_PTTXT

• PTTXT_009(040),

• data element: ATNAM

• ATNAM_010(030),

• data element: IMRC_DECIM

• DECIM_011(002),

• data element: IMRC_DESIC

• DESIC_012(022),

• data element: IMRC_MRMAC

MRMAC_013(022),

• data element: IMRC_MRMIC

MRMIC_014(022),

• data element: IMRC_UNITM

UNITM_015(006),

• data element: IMRC_PSORT

• PSORT_016(020),

• data element: IMRC_PTTXT

• PTTXT_017(040),

• data element: ATNAM

• ATNAM_018(030),

• data element: IMRC_DECIM

• DECIM_019(002),

• data element: IMRC_DESIC

• DESIC_020(022),

end of record.

LOOP AT RECORD.

perform bdc_dynpro using 'SAPLIMR0' '1110'.

perform bdc_field using 'BDC_CURSOR'

'IMPT-MPTYP'.

perform bdc_field using 'BDC_OKCODE'

'/00'.

perform bdc_field using 'RIMR0-MPOTY'

record-MPOTY_001.

perform bdc_field using 'IMPT-MPTYP'

record-MPTYP_002.

perform bdc_field using 'EQUI-EQUNR'

record-EQUNR_003.

perform bdc_dynpro using 'SAPLIMR0' '5110'.

perform bdc_field using 'BDC_CURSOR'

'IMPT-ATNAM'.

perform bdc_field using 'BDC_OKCODE'

'/00'.

perform bdc_field using 'IMPT-PSORT'

record-PSORT_004.

perform bdc_field using 'IMPT-PTTXT'

record-PTTXT_005.

perform bdc_field using 'IMPT-ATNAM'

record-ATNAM_006.

perform bdc_field using 'RIMR0-DESIC'

record-DESIC_007.

perform bdc_dynpro using 'SAPLIMR0' '5110'.

perform bdc_field using 'BDC_CURSOR'

'RIMR0-DESIC'.

perform bdc_field using 'BDC_OKCODE'

'=ADPT'.

perform bdc_field using 'IMPT-PSORT'

record-PSORT_004.

perform bdc_field using 'IMPT-PTTXT'

record-PTTXT_005.

perform bdc_field using 'IMPT-ATNAM'

record-ATNAM_006.

perform bdc_field using 'IMPT-DECIM'

record-DECIM_011.

perform bdc_field using 'RIMR0-DESIC'

record-DESIC_007.

perform bdc_dynpro using 'SAPLIMR0' '6110'.

perform bdc_field using 'BDC_CURSOR'

'RIMR0-MRMIC'.

perform bdc_field using 'BDC_OKCODE'

'=BU'."'=NEXT'.

perform bdc_field using 'RIMR0-MRMAC'

record-MRMAC_013.

perform bdc_field using 'RIMR0-MRMIC'

record-MRMIC_014.

perform bdc_field using 'RIMR0-UNITM'

record-UNITM_015.

perform bdc_dynpro using 'SAPLIMR0' '5110'.

perform bdc_field using 'BDC_CURSOR'

'IMPT-PSORT'.

perform bdc_field using 'BDC_OKCODE'

'=BU'.

perform bdc_field using 'IMPT-PSORT'

record-PSORT_004.

perform bdc_field using 'IMPT-PTTXT'

record-PTTXT_005.

perform bdc_field using 'IMPT-ATNAM'

record-ATNAM_006.

perform bdc_field using 'IMPT-DECIM'

record-DECIM_011.

perform bdc_field using 'RIMR0-DESIC'

record-DESIC_007.

perform bdc_transaction using 'IK01'.

endloop.

Thanks

K Srinivas

[Former Member]

Do the recording again for the data you have, and see whether the data is being written again after some screen navigation (i.e lower range values written again ) in the recording .

Check whether any navigation takes place from the point you write data to another place and you return back to the same place ,if that is the case you need to write the data again

[Former Member]

Hello Srinivas,

You mean when you run BDC in all screen, lower range limit value is showing flat file value which is other than 0 but on transaction save you find value is 0.

Please check on any customization is done for this field or conditions are set.

Also check manually doing the same same set of data set transaction.

Thank You,

Nishikant.