topic Re: Change Document Read Positions in Application Development and Automation Discussions

Change Document Read Positions

Former Member — Mon, 19 Jun 2006 14:52:30 GMT

Hi Gurs,

I get an error message in the FM "Change Document Read Positions"

which is used in FB03 the error message is

"System error: Error in routine POSITIONEN_LESEN RC

= 1"

CDPOS table does not find a value for certain changenumber and hence the select query returs 0 sy-dbcnt

which is why I get this error message ..

could you help me in undersatnding where does this CDPOS gets populated and why is this so crucial here and how can I rectify this probs .

your inputs are greatly appreciated and will be highly rewarded by me ..

Thanks!!

Aryan

Message was edited by: Aryan T

Re: Change Document Read Positions

Former Member — Mon, 19 Jun 2006 15:57:09 GMT

Hi,

how are you calling show it,.

 CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
    EXPORTING
      changenumber                  = ws_cdhdr_tbl-changenr
      tablename                     = 'VBPA'
    IMPORTING
      header                        = ws_cdhdr_tbl
    TABLES
      editpos                       = ws_cdshw_tbl
    EXCEPTIONS
      no_position_found             = 1
      wrong_access_to_archive       = 2
      OTHERS                        = 3

Regards

vijay

Re: Change Document Read Positions

Former Member — Mon, 19 Jun 2006 16:23:05 GMT

Hi,

refer the OSS Note 422547

Symptom

When you display all change documents in the customer or vendor master data, the system generates error message F4308 "System error: Error in routine POSITIONEN_LESEN RC=1".

Additional key words

FD02, FK02, XD02, XK02, VD02, MK02,

FD03, FK03, XD03, XK03, VD03, MK03

Cause and prerequisites

There are several entries in the change document header table (CDHDR), however, there are no corresponding change document items (CDPO). This may be due to report SAPF019 ("Deleting Master Data") which, in error, only deleted line item data (refer to Note 0134293).

These change documents are old documents which were created when you used Release 4.0.

Solution

Execute report YDELCDHD of Note 134293 in the test mode and check whether the error is actually due to this problem. If so, execute report YDELCDHD in the update run.

Source code corrections