Skip to Content
0
Former Member
Dec 08, 2006 at 02:44 AM

Extraction Runtime Error

105 Views

I have an InfoCube that receive data from ODS. I deleted its DataMart InfoPackages and tried to recreate it manually.

Then I tried to run extraction via ODS' InfoPackage and suddenly I encounter with the following error.

Runtime Errors SYNTAX_ERROR

Date and Time 08.12.2006 10:38:36

Short dump has not been completely stored (too big)

ShrtText

Syntax error in program "GP42JWTUKUNAEGOIF06K05QLPC2 ".

What happened?

Error in ABAP application program.

The current ABAP program "SAPLRSDRO" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

In program "GP42JWTUKUNAEGOIF06K05QLPC2 ", the following syntax error occurred

in the Include "GP42JWTUKUNAEGOIF06K05QLPC2 " in line 35:

"The type "/BIC/B0002168000" is unknown."

" "

" "

" "

Author and last person to change the Include are:

Author "XXX"

Last changed by "XXX"

Error analysis

In program "GP42JWTUKUNAEGOIF06K05QLPC2 ", the following syntax error occurred:

"The type "/BIC/B0002168000" is unknown."

" "

Trigger Location of Runtime Error

Program SAPLRSDRO

Include LRSDROU05

Row 105

Module type (FUNCTION)

Module Name RSDRO_UPDATE_ODS

Source Code Extract

Line SourceCde

75 i_odsobject i_s_minfo '66' sy-msgid sy-msgty sy-msgno

76 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4 0 0.

77 RAISE x_message.

78 *ENDINSERTAS 04122002

79 ENDCASE.

80 ENDIF.

81

82 * IF l_subrc <> 0.

83 * CASE l_subrc.

84 * WHEN 1.

85 * PERFORM idoc_append_monitor

86 * USING i_odsobject i_s_minfo

87 * 'E' 003 'READ' space space space

88 * CHANGING c_t_idocstate.

89 * WHEN 2.

90 * PERFORM idoc_append_monitor

91 * USING i_odsobject i_s_minfo

92 * 'E' 003 'PROGRAM_GENERATE' space space space

93 * CHANGING c_t_idocstate.

94 * ENDCASE.

95 * ENDIF.

96

97 * push data into Activation Queue belonging to ODS

98 PERFORM update_ods IN PROGRAM (l_program_name)

99 USING i_odsobject

100 i_s_minfo

101 CHANGING c_t_data

102 c_t_idocstate

103 l_no_insert.

104

>>>> IF i_no_commit EQ rs_c_false.

106 * DB-Änderungen bestätigen

107 CALL FUNCTION 'RSDU_DB_COMMIT'.

108 ENDIF.

109

110 PERFORM write_monitor_success

111 USING i_odsobject

112 i_s_minfo

113 002

114 l_no_insert

115 0. "immer nur INSERT!

116

117 ENDFUNCTION.

Can someone help me to debug this? Thanks!