cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Error"RAISE_EXCEPTION" Exception condition "NO_BP" raised

Former Member

Hello Everybody,

We are facing runtime error in Prodcution Solution Manager 7.0 SP15, during SE38 ---> RSGET_SMSY -


> execute , then its ending with Runtime error "RAISE_EXCEPTION" Exception condition "NO_BP" raised

We already updated the Development Solman 7.0 to SP16.

We are not able to proceed further.

We struck here

============================================

Runtime Errors RAISE_EXCEPTION

Date and Time 28.07.2008 09:37:46

Short text

Exception condition "NO_BP" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

Error analysis

A RAISE statement in the program "CL_AI_SDK_SP_TOOLS_BP=========CP" raised the

exception

condition "NO_BP".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

Trigger Location of Runtime Error

Program CL_AI_SDK_SP_TOOLS_BP=========CP

Include CL_AI_SDK_SP_TOOLS_BP=========CM005

Row 193

Module type (METHOD)

Module Name SEARCH_FOR_BP

Source Code Extract

Line SourceCde

163 ENDIF.

164 ENDIF.

165 IF ev_bpartner IS INITIAL.

166 RAISE no_bp.

167 ENDIF.

168 EXIT.

169 ENDIF.

170

171 IF iv_ext_id IS NOT INITIAL.

172

173 CALL FUNCTION 'BAPI_PARTNER_GET_BY_IDNUMBER'

174 EXPORTING

175 identificationcategory = iv_category

176 identificationnumber = iv_ext_id

177 TABLES

178 businesspartner = lt_bpartner

179 return = et_return.

180

181 READ TABLE lt_bpartner INTO ls_bpartner INDEX 1.

182 IF ls_bpartner-partner IS NOT INITIAL.

183 ev_bpartner = ls_bpartner-partner.

184 ELSE.

185 lv_ext_id = iv_ext_id.

186 SHIFT lv_ext_id LEFT DELETING LEADING '0'.

187 CONCATENATE '%' lv_ext_id '%' INTO lv_ext_id.

188 SELECT SINGLE partner INTO ev_bpartner

189 FROM but0id

190 WHERE type = iv_category

191 AND idnumber LIKE lv_ext_id.

192 IF sy-subrc <> 0.

>>>>> RAISE no_bp.

194 ENDIF.

195 ENDIF.

196 EXIT.

197 ENDIF.

198

199 IF ev_bpartner IS INITIAL.

200 RAISE no_bp.

201 ENDIF.

202

203 ENDMETHOD.

===========================================

Please let me know, how to proceed.

Thanks in advance.

Best Regards,

Pratyusha

Accepted Solutions (0)

Answers (2)

Answers (2)

joo_migueldimas
Active Participant
0 Kudos

I have the same problem, the system show me a short dump when I´m setup the SLD (SMSY) in solution manager. When I´m create/apply new systems the system crash and he don´t enable be to make that activities!! Why... I already read and verify all instruction on that note 1144386, but even so that not solve this problem!!

Can you help me ?! How you solve this problem, it´s exactly the same situation that you had!

Best regards,

João Dimas

former_member209604
Active Contributor
0 Kudos

>

> We are facing runtime error in Prodcution Solution Manager 7.0 SP15, during SE38 ---> RSGET_SMSY -


> execute , then its ending with Runtime error "RAISE_EXCEPTION" Exception condition "NO_BP" raised

> We already updated the Development Solman 7.0 to SP16.

Please refer to SAP Note 1144386.

If your company is a VAR (Value Added Reseller), please see SAP Note 1023598.

Best regards,

Ruediger

Former Member
0 Kudos

Hi Ruediger,

Thanks for your valuable information.

Runtime error is solved.

Now we are facing another error,

SE38 ---> RSGET_SMSY -


> execute, then we are getting

" The SLD server connection is inactive"

Not able to proceed further

Best Regards,

Pratyusha

former_member209604
Active Contributor
0 Kudos

Hi Pratyusha,

I am not really an expert in this error message.

Long text oft the error message shows:

The SLD server connection is inactive

Message no. SCDT_LIS_IF011

Diagnosis

An error occurred during communication with the System Landscape Directory (SLD).

Procedure

1. Call transaction SLDCHECK to check the connection to the SLD. If the result does not contain the following sentence:

Summary: Connection to SLD works technically, but the SLD content may need maintenance

proceed as described in SAP Note 768452.

2. Call transaction SLDAPICUST to check the SLD receipt data.

3. If you do not have an SLD connected, choose the TMS as the data source for the automatic transfer of data in transaction SMSY.

Use SMSY_SETUP for step 3.

Best regards

Ruediger

joo_migueldimas
Active Participant
0 Kudos

Hi Ruediger Stoecker,

Can you help me too! Thanks in advance

"I have the same problem, the system show me a short dump when I´m setup the SLD (SMSY) in solution manager. When I´m create/apply new systems the system crash and he don´t enable be to make that activities!! Why... I already read and verify all instruction on that note 1144386, but even so that not solve this problem!!

Can you help me ?! How you solve this problem, it´s exactly the same situation that you had! "

Best regards,

João Dimas