SAP Knowledge Base Article - Preview

3114905 - TM planning keeps failing with error: The argument 'Initialization Error' cannot be interpreted as a number, CX_SY_CONVERSION_NO_NUMBER


While running the background planning report, there is dump similar to:

Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_X
ABAP Program           /BOBF/CL_FRW==================CP
Application Component  AP-RC-BOF-RNT
|    Message class....... /BOBF/FRW                                                                
|    Number.............. 013                                                                      
|    Variable 1.......... /SCMTMS/PLN                                                              
|    Variable 2.......... TM-PLN 
|    1|While executing action "OPTIMIZE" of node "ROOT" of business object "/SCMTMS/PLN" an        
|    2|exception has occured. The method "EXECUTE" of class "/SCMTMS/CL_PLN_A_ROOT_OPT" contains   
|    3|errors, which are described in the exception chain below. Please open a ticket to the       
|    4|responsible component "TM-PLN"! 
In the Unformatted Dump display, there is the following:
Exception chain (click button "Unformatted Display" for all details):                                                                                                                                   
1. Info: The argument 'Initialization Error' cannot be interpreted as a number, CX_SY_CONVERSION_NO_NUMBER, Program: <custom Z-implementation of SCMB_CL_DDD_CONNECTOR>=======CP, Include:<custom Z-implementation of SCMB_CL_DDD_CONNECTOR> =======CM004, Position:281                                         
2. Info: An exception with the type CX_SY_CONVERSION_NO_NUMBER occurred, but was neither handled locally, nor declared in a RAISING clause,
3. Info: Application error: Exception while calling method EXECUTE of action OPTIMIZE, /BOBF/CX_FRW_CORE, Program:/SCMTMS/VSR_OPT_BGD, Include:, Position:0  

Debugging in the custom Z-implementation of SCMB_CL_DDD_CONNECTOR, there is a proxy call to PC Miler or other external third party GIS provider.

In the INPUT response or RETURN, there is "Initialization error".  The expected value would be the distance for the OUTPUT call.



SAP Transportation Management


SAP NetWeaver 7.4


KBA , SCM-BAS-LDD , Lane, Distance and Duration Determination , TM-PLN , Planning , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.