change pointers for iflo table ??

[Former Member]

we work with functional locations and als have customized to keep track of the changes of all zfields

now for 3 custom fields changes in tcode IL02 and iflo table are logged. but for the other custom fields no logging occurs

I also found

when traced tcode IL02 with se30 I got as far as include

FIFLOCDC

there is

CALL FUNCTION 'IFLO_WRITE_DOCUMENT ' IN UPDATE TASK

but I can't debug any further, I can't get inside the function ? what is different with this function that I may not enter in debug modus?

I also found table TBD62 with some fields of table iflo but not my 3 zfields ?

with tcode bd52 I can see the fields for logging but I also miss my custom fields in this list which are logged ?

does anybody know where I can set my other custom fields for keeping track of changes ?

kind regards

arthur de smidt

[Former Member]

we work with functional locations and als have customized to keep track of the changes of all zfields

now for 3 custom fields changes in tcode IL02 and iflo table are logged. but for the other custom fields no logging occurs

I also found

when traced tcode IL02 with se30 I got as far as include

FIFLOCDC

there is

CALL FUNCTION 'IFLO_WRITE_DOCUMENT ' IN UPDATE TASK

but I can't debug any further, I can't get inside the function ? what is different with this function that I may not enter in debug modus?

I also found table TBD62 with some fields of table iflo but not my 3 zfields ?

with tcode bd52 I can see the fields for logging but I also miss my custom fields in this list which are logged ?

does anybody know where I can set my other custom fields for keeping track of changes ?

kind regards

arthur de smidt

[Former Member]

A FM called in Update Mode cannot be debugged as it is not executed immediately. It is executed upon Commit Work.

I found the following from Moderator Matt, which may be helpful:

"Set a break point in your update task FM. Set a break point on the commit statement. Run the transaction. You'll enter the debugger at the commit statement. Now set UPDATE DEBUGGING on, and continue. A new debug window will open in the update task. Hit F8, and the debugger will stop at your break point in the update task."

[Former Member]

thanks, now I could finally debug this thing until I got to the function DDIF_NAMETAB_GET.

and then I realised that I should check the custom created elements in se11

there I saw that on the data element level you could check the changelog in tab further characteristics.

thanks

Arthur