Skip to Content
0
Nov 06, 2015 at 07:16 AM

Error While creating BP - ABAP

3837 Views

Dear Expert

I tested on Sandbox how to create the BP automatically while creating customer from specific account group.. but after while i transport the request to QAS i face this error..

while i used another account group with same steps , no error happen

Runtime Errors MESSAGE_TYPE_X_TEXT

Date and Time 06.11.2015 09:16:41

Short dump has not been completely stored (too big)

Short text

The running application consciously caused an abort with short dump.

What happened?

An abnormal situation was detected in the running application program.

Therefore, a termination with short dump was consciously triggered using

the language element MESSAGE (type X).

Error analysis

Short text of the error message:

" "

Trigger Location of Runtime Error

Program MDS_CTRL_STRATEGY=============CP

Include MDS_CTRL_STRATEGY=============CM004

Row 120

Module type (METHOD)

Module Name SYNCHRONIZE

Source Code Extract

Line SourceCde

90 message x898.

91 endif.

92

93

94 call method gr_ppo_order_creation->create_order

95 EXPORTING

96 is_error = ls_error.

97

98 *To avoid that errors are stored twice in PPO-orders AND

99 *if error is logged in PPO-order program continues normally without further error indication

100 clear ls_error.

101

102 when ' '.

103 "Postprocessing Office is not active -> this leads to an intended dump.

104 clear ls_message.

105 LOOP AT ls_error-messages INTO ls_message

106 WHERE type CA 'EAX'.

107 * Short Dump MESSAGE x010.

108 MESSAGE ID ls_message-id

109 TYPE 'X'

110 NUMBER ls_message-number

111 WITH ls_message-message_v1

112 ls_message-message_v2

113 ls_message-message_v3

114 ls_message-message_v4.

115 ENDLOOP.

116 * PPO is not active ; maintain it in the customizing tables.

117 IF ls_message is initial.

Runtime Errors MESSAGE_TYPE_X_TEXT

Date and Time 06.11.2015 09:16:41

Short dump has not been completely stored (too big)

118 * MESSAGE x010.

119 CONCATENATE text-001 text-002 INTO lv_text SEPARATED BY space.

>>>>> MESSAGE lv_text TYPE 'X'.

121 ENDIF.

122

123 "If dump occours here, have a look at the content of the structure LS_ERROR

124 "in the debugger for error messages causing the error.

125 "Hint: This is a quite complex data structure, so you might have to navigate dow

126 "some levels in the structure to find the relevant error messages.

127

128 when others.

129 message x899.

130 endcase.

131

132 when others.

133 "do nothing

134

135 endcase.

136

137 endloop.

138

Regards

Mahmoud EL nady