ICR deleting transaction data

[Former Member]

Hello experts,

when using the ICR auxiliary program "delete transactional data" I get the following a runtime error. Can anyone help me on that?

Regards,

Maria Noack

-

---

Runtime Errors SYNTAX_ERROR

Date and Time 15.10.2008 18:34:10

Short text

Syntax error in program "FBICRC003_DATA_DEL ".

What happened?

Error in the ABAP Application Program

The current ABAP program "FBICRC_TOOLS" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "FBICRC003_DATA_DEL " in include

"FBICRC003_DATA_DEL_F01 " in

line 58:

"Die FORM "BUILD_LOGS_PER_COMPANY" existiert nicht."

" "

" "

" "

The include has been created and last changed by:

Created by: "SAP "

Last changed by: "STADTER "

Error in the ABAP Application Program

The current ABAP program "FBICRC_TOOLS" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

The following syntax error was found in the program FBICRC003_DATA_DEL :

"Die FORM "BUILD_LOGS_PER_COMPANY" existiert nicht."

" "

" "

" "

Trigger Location of Runtime Error

Program FBICRC_TOOLS

Include FBICRC_TOOLS_C01

Row 37

Module type (METHOD)

Module Name HANDLE_LINK_CLICK

Source Code Extract

Source Code Extract

Line SourceCde

7 PUBLIC SECTION.

8 METHODS handle_link_click

9 FOR EVENT link_click OF cl_gui_column_tree

10 IMPORTING node_key

11 item_name.

12 ENDCLASS. "lcl_tree_event_receiver DEFINITION

13 ----

---

14 * handle TREE events

15 CLASS lcl_tree_event_receiver IMPLEMENTATION.

16 METHOD handle_link_click.

17 * IMPORTING

18 * node_key TYPE tv_nodekey

19 * item_name TYPE tv_itmname.

20 CONSTANTS: lc_prefix TYPE progname VALUE 'FBICRC'.

21 CONSTANTS: lc_delimiter TYPE char01 VALUE '_'.

22 DATA: ld_progname TYPE progname.

23 CASE node_key(1).

24 WHEN '%'.

25 SHIFT node_key LEFT DELETING LEADING '%'.

26 CALL TRANSACTION node_key. "#EC CI_CALLTA

27 WHEN OTHERS.

28 CONCATENATE

29 lc_prefix

30 pa_rproc

31 lc_delimiter

32 node_key

33 INTO ld_progname.

34 SUBMIT (ld_progname) "#EC CI_SUBMIT

35 VIA SELECTION-SCREEN AND RETURN.

36 ENDCASE.

>>>>> ENDMETHOD. "handle_link_click

38

39 ENDCLASS. "lcl_tree_event_receiver IMPLEMENTATION

[Former Member]

Hello Ralph,

thanks for your fast support to undo the import being messed up. Nevertheless I understood that we need the functionalitties of SP13 or OSS 863630 to import OSS 1159776 for sender ledgers options and OSS 1112275 for data upload.

Best regards,

Maria

[former_member572578]

Hello Maria,

It is correct that note 863630 is a prerequisite for almost all notes, simply because it basically contains a certain level of corrections. However, note 863630 specifies what actions are necessary for which support package levels. For ERP2005 >= SP11 no actions are necessary meaning that it is not necessary to apply the transport files.

Best regards,

Ralph

[Former Member]

Hello Ralph,

Now I hope once more that you are able to find a quick and good solution for our problem ;o)

The thing is that we are here on support package 13. Nevertheless not all funtionality regarding ICR is available (e.g. core requirements not covered: sender legder to be chosen for process 001 and 003 to cover the newGL online split and upload functionality).

Hope you can help us on that!

Regards

Maria

[former_member572578]

Hello Maria,

Selecting data from new GL was introduced later on. However, it is not contained in 863630. When you imported the transport in ECC60 SP13 you overwrote some of the coding with an outdated version. As I wrote in the service ticket - the easiest way to undo these changes is to create a transport of copies in a system where the P3E transport has not been imported yet and then import the object list from the P3E transport and import that new transport of copies in the system where you are having issues. That way you are basically undoing what the P3E transport messed up.

Best regards,

Ralph

[Former Member]

Hello Ralph,

we're having trouble uploading OSS-note 863630. The customer is still working on it... If the error message remains, I will get to you again...

Thanks for your help!

Maria

[former_member572578]

Hello Maria,

Please note that the transports from 863630 may not have to imported at the customer site at all depending on their SP level - I think I am working on service ticket of that customer regarding that problem right now

Ralph

[former_member572578]

Hello Maria,

Did you import the transport requests from note 863630 in the correct order? Did you implement note 1062292 after note 863630?

Best regards,

Ralph