Run time error COMPUTE_BCD_OVERFLOW coming at MFBF

Hi Guru's
User is getting runtime error at MFBF as below:
Runtime Errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
This coming at production but not coming at test server.
when user is trying to enter quantity 66059 there is error coming but when he enter quantiy as 6095 there is no dump.
Please suggest any solution to avoid and also suggest sap Notes if there is any available.
Thanks in advance,
regards,
Nilesh I

Hi,
I can see that there are several SAP notes regarding this issue, you just need to check their symptons and if they are valid for your SAP_APPL release and support package.
Here are the SAP notes:
- 1295055: Product cost collector: Field AFPO-WEMNG set incorrectly
- 964308: COMPUTE_BCD_OVERFLOW in CKMO_GET_ORD_HIST_NETWR_MMIM
I hope they help you.
Regards,
Marcelo

Similar Messages

Run time error COMPUTE_BCD_OVERFLOW when extracting data

Dear all,
We are facing an issue when trying to extract the data for CRM Service contract item Extractor. It is giving runtime error when trying to extract particular range of transaction number say 1 to 50. but if i split these into 2 packages i.e 1 to 25 & 26 to 50, the data is getting extracted without any problems. If anyone has come across the similar issue, please share your views.
details of the errro:
Runtime Errors         COMPUTE_BCD_OVERFLOW
Except.                CX_SY_ARITHMETIC_OVERFLOW
Short text
    Overflow during the arithmetical operation (type P) in program
Thanks in Advance!
Regards,
Pavan

Hi,
I can see that there are several SAP notes regarding this issue, you just need to check their symptons and if they are valid for your SAP_APPL release and support package.
Here are the SAP notes:
- 1295055: Product cost collector: Field AFPO-WEMNG set incorrectly
- 964308: COMPUTE_BCD_OVERFLOW in CKMO_GET_ORD_HIST_NETWR_MMIM
I hope they help you.
Regards,
Marcelo

Run time error while closing the CRM Order using BAPI

Hi Experts,
Need your invaluable suggestions here.Apologies for the lengthy mail, intention is to give clear idea of the issue.
I am facing an issue while closing the CRM orders. According to our business process, when an issue is solved we will keep the order in resolved status only. We will not directly close the order from the CRM tool, instead we have created a custom program for the same purpose.
For the custom program we will give input as the order number and execute it, this will close the order.
Here close the order means assigning it to Close status as well assign the reason code.
We have created some reason codes for closed status.
So when the program is run the Order moves from resolved status to closed status along with reason code.
But of late we are facing some problems with this program, it is giving run time error for some CRM orders.
Run time error message : The ABAP/4 Open SQL array insert results in duplicate database records.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "CRM_SERVICE_OS_UPD_OST_DU" "(FUNCTION)", nor was it propagated by a RAISING clause.
Please find my code which have used in the custom program
Closing the resolved SOs in the system
    CALL FUNCTION 'CRM_STATUS_CHANGE_EXTERN_OW'
        EXPORTING
          objnr                     = iv_guid
          user_status          = lc_status_closed
       EXCEPTIONS
         object_not_found          = 1
         status_inconsistent       = 2
         status_not_allowed       = 3
         OTHERS                        = 4.
    IF sy-subrc <> 0.
      WRITE : 'Error at maintaining status'.
    ENDIF.
Set reason code
build lt_subject
    ls_subject-ref_guid = iv_guid.
    ls_subject-katalogart = 'A2'.
    ls_subject-codegruppe = 'ZR000003'.
    ls_subject-code       = 'ZR33'.                      " Reason code
    ls_subject-mode       = 'A'.
    APPEND ls_subject TO lt_subject.
build lt_ossset
    ls_osset-ref_guid        = iv_guid.
    ls_osset-subject_profile = 'ZREASON03'.
    ls_osset-profile_type    = 'G'.
    ls_osset-subject         = lt_subject.
    APPEND ls_osset TO lt_osset.
build lt_service_os
    ls_service_os-ref_guid = iv_guid.
    ls_service_os-ref_kind = 'A'.
    ls_service_os-osset     = lt_osset.
    APPEND ls_service_os TO lt_service_os.
build lt_input_fields
    REFRESH: lt_input_fields, lt_field_names.
    CLEAR : ls_input_fields, ls_field_names.
    ls_field_names-fieldname    = 'CODE'.
    APPEND ls_field_names TO lt_field_names.
    ls_field_names-fieldname    = 'CODEGRUPPE'.
    APPEND ls_field_names TO lt_field_names.
    ls_field_names-fieldname    = 'KATALOGART'.
    APPEND ls_field_names TO lt_field_names.
    ls_field_names-fieldname    = 'SERVICE_PROFILE'.
    APPEND ls_field_names TO lt_field_names.
    ls_input_fields-ref_guid    = iv_guid.
    ls_input_fields-ref_kind    = 'A'.
    ls_input_fields-objectname = 'SERVICE_OS'.
    ls_input_fields-field_names = lt_field_names.
    APPEND ls_input_fields TO lt_input_fields.
     CALL FUNCTION 'CRM_ORDER_MAINTAIN'
      EXPORTING
        it_service_os     = lt_service_os
      CHANGING
        ct_input_fields   = lt_input_fields
      EXCEPTIONS
        error_occurred    = 1
        document_locked   = 2
        no_change_allowed = 3
        no_authority      = 4
        OTHERS            = 5.
    IF sy-subrc <> 0.
      WRITE : 'Error at maintaining reason'.
    ENDIF.
    CALL FUNCTION 'CRM_ORDER_SAVE'
      EXPORTING
        it_objects_to_save   = lt_header_guid
        iv_update_task_local = lv_update_task_local
      IMPORTING
        et_saved_objects     = lt_saved_objects
      EXCEPTIONS
        document_not_saved   = 1
        OTHERS               = 2.
    IF sy-subrc <> 0.
      WRITE : 'Error at saving'.
    ELSE.
      WRITE : 'Successfully Closed'.
      COMMIT WORK AND WAIT.
    ENDIF.
Run time error is coming at COMMIT WORK AND WAIT statement.
Please let me know any corrections are required in the above program.
When I analyzed the run time error I have found that it trying to insert the record in CRMD_SRV_OSSET for that CRM order, but already one record is present in the table for the same CRM order number.
For most of the CRM orders there is no entry in this table so they are closing successfully but for a few orders for which there is an entry we are getting the above run time error.
There is nothing wrong with the orders which have an entry already in the table CRMD_SRV_OSSET, I need to close these kind of orders with out run time error.
Kindly provide your feedback.

Hi Dinakar,
You posted this in APO PPDS forum. This question should go to PP forum where someone could answer it.
Please close this thread and open a new thread in PP forum so that you could get help quickly from the relevant experts.
Regards - Pawan

Run time error while executing Project Info system Reports

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Run time Error while executing Project Info system Reports (CN41/CN41N)

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Run time Error while executing project infosystem reports (CN41/41N)

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Hi Rakesh,
The memory which can be managed by the logical database is approx.
100 MB. You can use the following rule of thumb to calculate the
allocated memory of your selection:
[( sum of projectdefinitions + sum of WBS elements + sum of networks and orders ) * 1 KB + ( sum of activities     ) * 4 KB ] *2,5 = memory consumption
Further objects - as relationships, capacities, ... will increase
the memory consumption. (see note 107605)
You can find out the number of objects bein used using the "Test selection scope" (CTRL+F12) button in CN41
Other recommendations are:
1) Check the profile (parameter "rdisp/PG_MAXFS") with your Basis
   colleague and adjust upwards (Note 133909)
2) Select a smaller range of objects by using status schema
   or more dynamic selections. Please review SAP Note 206264.
3) Please review also 107605, which gives you further information
   concerning the selection in Project Information System.
Hope this helps!
Regards
Martina
Message was edited by:
        Martina Modolell

Run time error while running BDC for production order creation and confirmation:

Dear Gurus,
We have a situation, where the users are trying to do the entries creation of order or confirmation (through manual and BDC). But, if there is any kind of a deficit quantities in consumption or GR quantity, then it is going to run time error and Dumps are coming in program SAPLCORB
and the transaction code is coming for CO11N.
How to avoid this error to run the production system in smoothing way...Any flash lights on this will be great full
Regards,
Madhu.G

Hi Madhu,
Expert Caetano has rightly point out. Refer Note 1840705 - RAISE_EXCEPTION short dump if running CO11N in background
Cause
The short dump is triggered because SAP transaction CO11N contains new GUI elements that cannot always be dealt with in a background process,
such as the confirmation texts.
Resolution
SAP recommends that the standard production order BAPIs, such as BAPI_PRODORDCONF_CREATE_TT, should be used to post a confirmation in background.
If this is not feasible, the following workaround may be uses:
Define a confirmation profile in transaction OPK0;
In the detail areas, remove the area "Confirmation text";
Set this profile as standard, so that it is chosen automatically by the system when a batch-job
is started;
Assign this confirmation profile to the batch user with transaction SU3 using parameter CORUPROF.
Also see Note 429432 - CO11N: Batch input in background dumps if long text is maintained
Refer to note 1154692 - Endless loop during confirmation in background if you doing Auto GR during confirmations
Thanks & Regards,
Ramagiri

Run time error while doing VL10B transaction for STO

Dear All,
We are facing problem of run time error while creating Delivery (VL10B) for STO .We have two company codes .For one company code its working fine .But we are trying for another company code ,this error coming.error detals
Error in the ABAP Application Program
The current ABAP program "SAPLV05I" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not cau
     in
    procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAI
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
Kindly suggest as to how to resolve this asap.
regards
umesh

These Kind of Errors Generally Occor for the wrong maitnaince of the partner functions. If you are using any user exits to detremine the partner functions. check the logic in that routine.
Because we do frequently get this error, but only if we hae not maintained as per the rule written in the user exit..
The USer exits for partner Determiantion to check is Function Module EXIT_SAPLV09A_003. THis gets activated, if you have give the source parner function as "X/Y/Z" in your partenr determiantion procedures.

Run time error in MIGO after maintaining tax code

Hello Experts,
I had configured the new tax code ,which is working fine for the PO document ZLOC domestic and the account category Z.
While doing the MIGO for purchase document type ZGEN general purchase , I am getting run time error:
"Division by 0 (type P) in program "SAPLJ1IEX".
When I debugged the code i found that inside FM: 'J_1IEX_DEFAULT_EXCISE_DUTY'
one another FM is being called: 'J_1I6_UNIT_CONVERSION' which is returning the value "ls_ekpo-menge" as 0(Zero).
later in the code when "ls_ekpo-menge" used in calculation then divide by 0 runtime error is coming.
Please suggest what need to be done.
Is there anything related to tax code? How should I correct it?

Hi,
There is not value in that field for PO quantity / Value it is missing while doing MIGO. Check whether you have maintained values for all required fields.
Kiran

Run-Time Errors cause wierdness

I have a remote object call that sends a query string to a
database. I am trying to catch errors coming from the database
because of bad sql statements. In my code there is an IF statements
that checks if the first row returned is an object by trying to
convert it to a string. If it is not equal to "[object Object]"
then I know its an error message generated from the database. My
problem is as soon as I uncomment the IF statement and test my app
everything begins acting wierd as soon as my app hits that logic.
Items highlight, tree controls show junk, etc. If I comment out the
IF everything works fine but I get a alert for rows returned and
one with the error message. I tried enclosing everything in a try
catch but there seems to be no run-time error occuring. Has anybody
else experience wierd things when errors occur?
private function queryResults(event:ResultEvent):void
var call:Object = event.token;
var isError:Boolean = false;
if( call.state == "FillGrid" )
results = event.result as ArrayCollection;
if( results.length == 1 )
var errMsg:String = results.getItemAt(0).toString();
//if( errMsg != "[object Object]" )
Alert.show(errMsg,"Error");
//isError = true;
if( !isError)
results.filterFunction = searchData;
Alert.show( results.length.toString() + " Rows Returned!
","Results");
SortColumns();
if( results.length > 0 )
calculateGrandTotals(results);

I have adjusted some of the logic in my code and now it works
fine. I would still like to know what was causing the wierd stuff.
private function queryResults(event:ResultEvent):void
var call:Object = event.token;
var isError:Boolean = false;
var msg:String = "";
var msgHeader:String = "Results";
if( call.state == "FillGrid" )
var tmpResults:ArrayCollection = event.result as
ArrayCollection;
msg = tmpResults.length.toString() + " Rows Returned! ";
if( tmpResults.length == 1 )
var errMsg:String = tmpResults.getItemAt(0).toString();
if( errMsg != "[object Object]" )
msg = errMsg;
msgHeader = "Error";
isError = true;
Alert.show( msg,msgHeader);
if( isError == false )
results = tmpResults;
results.filterFunction = searchData;
SortColumns();
if( results.length > 0 )
calculateGrandTotals(results);
}

Run-time error '429':Active X component can not create an object

Hi Folks,
I am using some VBA code to run logic in BPC for Excel. When i try to click on VBA button, It's giving the below error.However when i am trying to execute same from server it is working fine. Accessing from BPC client only we are facing this problem.
Code have no issues. Is there any specific thing need to mentioned in client when we use VBA programming? Basically we used the VBA program to create the id's in BPC for Excel. So that it will automatically created on fly. Testing was fine interms of working in Server.
" Run-time error '429':Active X component can not create an object ."

Hi,
Are you trying to add a member into the dimension from excel? As you said that this has been already tested in the server and is working fine, I believe, you have taken care of everything.
Now, coming to the point, when you are adding a member in the membersheet, you need to process the dimension. This requires the admin rights. So, please check the task profile of the user ID, with which you are trying from your system. This user ID should be the primary admin.
Hope this helps.
Additionally, can you please elaborate on the steps on what you followed for adding a member from the excel directly?

I am getting run time error 6034 after updating iTunes to new version.Any help?

I am getting run time error 6034 after updating iTunes to new version.Any help?
I tried different ways to resolve it like uninstall/install itunes
I am also getting error message on iTunes helper.exe

Hi isush!
I have an article for you that will help you troubleshoot this issue:
iTunes 11.1.4 for Windows: Unable to install or open
http://support.apple.com/kb/TS5376
Thanks for coming to the Apple Support Communities!
Cheers,
Braden

Getting run time error in organizer Photoshop Elements 5.0??

How do I fix run time error for Adobe PhotoShop Elements
5.0 when I pull up organizer?

What operating system?

Run time error

Dear All,
During the transaction /n/sapapo/ccr (Reconsilation of transaction data) in client SCP 950, system displays the run time error which are attached herewith.
This is the activity a used to execute regularly (Daily) and first time i recieved this message - -
Runtime Errors         ASSERTION_FAILED
Date and Time          13.07.2007 10:13:37
ShrtText
The ASSERT condition has been violated.
What happened?
In the current application program, the system recognized a situation
    involving the ASSERT statement that should not occur. A runtime error
    occurred, either because there was no activation ID entered or because
    the ID of the activation mode used was set to "Cancel.
What can you do?
Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
     termination messages, especially those beyond their normal deletion
    date.
is especially useful if you want to keep a particular message.
Error analysis
The following activation ID was used: "No checkpoint group specified"
If the FIELDS addition was used with this ASSERT statement, the content
    of the first 8 fields is as follows:
    " (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
"ASSERTION_FAILED" C
"/SAPAPO/SAPLTIMESTAMP" or "/SAPAPO/LTIMESTAMPU08"
    "/SAPAPO/TIMESTAMP_DIFFERENCE"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".
2. A suitable printout of the system log
       To obtain this, call the system log through transaction SM21.
       Limit the time interval to 10 minutes before and 5 minutes
       after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, select the Editor function "Further Utilities->
       Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "scmprd"
    Network address.......... "172.16.10.47"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "0002BFAAD700"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 0
    Short dump setting....... "full"
Database server.......... "scmprd"
    Database type............ "ORACLE"
    Database name............ "SCP"
    Database owner........... "SAPSCP"
Character set............ "C"
SAP kernel............... "640"
    Created on............... "Jan 18 2006 20:47:39"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
Patch level.............. "109"
    Patch text............... " "
Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
     10.2.0.."
SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
    Roll..................... 16192
    EM....................... 196923232
    Heap..................... 0
    Page..................... 98304
    MM Used.................. 186636840
    MM Free.................. 1895288
    SAP Release.............. "640"
User and Transaction
Client.............. 950
    User................ "SCMATP"
    Language key........ "E"
    Transaction......... "/SAPAPO/CCR "
    Program............. "/SAPAPO/SAPLTIMESTAMP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    The termination occurred in the ABAP program "/SAPAPO/SAPLTIMESTAMP" in
     "/SAPAPO/TIMESTAMP_DIFFERENCE".
    The main program was "/SAPAPO/CIF_DELTAREPORT3 ".
The termination occurred in line 61 of the source code of the (Include)
     program "/SAPAPO/LTIMESTAMPU08"
    of the source code of program "/SAPAPO/LTIMESTAMPU08" (when calling the editor
     610).
Source Code Extract
Line SourceCde
31     lv_time_int_low      TYPE i,
   32     lv_timediff_int      TYPE i,
   33     lv_datediff_int      TYPE i,
   34     lv_time              TYPE t,
   35     ls_time              TYPE tstr_timestr.
   36
37 * check timestamp parameter
   38 * ASSERT NOT iv_timestamp_high IS INITIAL.
   39 * ASSERT NOT iv_timestamp_low IS INITIAL.
   40 * ASSERT iv_timestamp_low <= iv_timestamp_high.
   41   IF iv_timestamp_high IS INITIAL
   42   OR iv_timestamp_low IS INITIAL.
   43     RAISE invalid_parameter.
   44   ENDIF.
45   IF iv_timestamp_high < iv_timestamp_low.
   46     RAISE invalid_parameter.
   47   ENDIF.
48
49 * prepare timestamps
   50 * .. split into date and time integers
   51   ls_timestamp_high = iv_timestamp_high.
   52   lv_date_int_high = ls_timestamp_high-date.
   53   lv_time_int_high = ls_timestamp_high-time.
   54   ls_timestamp_low = iv_timestamp_low.
   55   lv_date_int_low   = ls_timestamp_low-date.
   56   lv_time_int_low   = ls_timestamp_low-time.
   57
58 * .. calc date diff
   59 * .. check against max. allowed integer difference
   60   lv_datediff_int = lv_date_int_high - lv_date_int_low.
>>>>>   ASSERT lv_datediff_int <= lc_datediff_intmax.
   62
63 * calc time diff
64   lv_timediff_int = lv_time_int_high - lv_time_int_low.
   65   IF lv_timediff_int < 0.
   66     ADD 86400 TO lv_timediff_int.
   67     SUBTRACT 1 FROM lv_datediff_int.
   68   ENDIF.
69
70 * calc total duration
   71   lv_duration_int = lv_datediff_int * 86400 + lv_timediff_int.
   72   lv_time = lv_timediff_int.
   73   ls_time = lv_time.
   74   ls_duration-hours   = lv_duration_int DIV 3600.
   75   ls_duration-minutes = ls_time-minute.
   76   ls_duration-seconds = ls_time-second.
   77
78   ev_duration_packed = ls_duration.
   79   ev_duration_integer = lv_duration_int.
   80 ENDFUNCTION.
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 1
SY-DBCNT 1
SY-FDPOS 6
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE CIF - Comparison/Reconciliation of Transaction Data
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
      Name
5 FUNCTION     /SAPAPO/SAPLTIMESTAMP               /SAPAPO/LTIMESTAMPU08                  61
      /SAPAPO/TIMESTAMP_DIFFERENCE
    4 FORM         /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3F17                349
      COMPARE_ORDER_HEADER
    3 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U03                125
      /SAPAPO/CIF_DELTA3_COMP_ORDER
    2 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U01                871
      /SAPAPO/CIF_DELTA3_COMP
    1 EVENT        /SAPAPO/CIF_DELTAREPORT3            /SAPAPO/CIF_DELTAREPORT3              189
      START-OF-SELECTION
Chosen variables
Name
Val.
No.       5 Ty.          FUNCTION
Name /SAPAPO/TIMESTAMP_DIFFERENCE
IV_TIMESTAMP_HIGH
#q1###
02073899
2001125C
IV_TIMESTAMP_LOW
##q!####
00720899
2011125C
EV_DURATION_INTEGER
0
0000
0000
EV_DURATION_PACKED
000000
00000C
SYST-REPID
/SAPAPO/SAPLTIMESTAMP
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454254545444554452222222222222222222
    F31010FF310C49D5341D00000000000000000000
%_SPACE
0
0
2
0
LS_TIMESTAMP_HIGH
22000713182959
00000000000000
00000000000000
33333333333333
22000713182959
LV_DATE_INT_HIGH
803363
0042
0C23
LS_TIMESTAMP_HIGH-DATE
22000713
00000000
00000000
33333333
22000713
LV_TIME_INT_HIGH
66599
0002
0147
LS_TIMESTAMP_HIGH-TIME
182959
000000
000000
333333
182959
LS_TIMESTAMP_LOW
20071210182959
00000000000000
00000000000000
33333333333333
20071210182959
LV_DATE_INT_LOW
733021
0025
0BFD
LS_TIMESTAMP_LOW-DATE
20071210
00000000
00000000
33333333
20071210
LV_TIME_INT_LOW
66599
0002
0147
LS_TIMESTAMP_LOW-TIME
182959
000000
000000
333333
182959
SY-UNAME
SCMATP
000000000000
000000000000
544455222222
33D140000000
SCREEN-INPUT
1
0
0
3
1
LV_DATEDIFF_INT
70342
001C
0126
LV_TIMEDIFF_INT
0
0000
0000
SYST
#######################################Ō###############################################䵘 C#Ԁ##
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
    000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
    0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
    0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
SY-REPID
/SAPAPO/SAPLTIMESTAMP
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454254545444554452222222222222222222
    F31010FF310C49D5341D00000000000000000000
%_DUMMY$$
0000
0000
2222
0000
No.       4 Ty.          FORM
Name COMPARE_ORDER_HEADER
SYST-REPID
/SAPAPO/SAPLCIF_DELTA3
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454254544445444543222222222222222222
    F31010FF310C396F45C413000000000000000000
GC_APPEND_MODE
3
0
0
3
3
LS_FIELDS_TO_COMPARE-DUEDATE
    X
0
0
5
8
SYST
#######################################Ō###############################################䵘 C#Ԁ##
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
    000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
    0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
    0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
LS_APO_ORDER-ORDTYPE
5
0
0
3
5
GC_PLANNED_ORDER
5
0
0
3
5
LS_R3_ORDER-STATUSCNF
0
0
2
0
GC_ORDER_STATUS_NO_CONF
1
0
0
3
1
LS_APO_ORDER-STATUSCNF
0
0
2
0
GC_PRED_OUT_DEL
A
0
0
4
1
GC_TND_DELETE
CN
00
00
44
3E

Dear Sajit,
Go through the following OSS Notes:
<a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=901957&_NLANG=E">901957</a>, <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1036880&_NLANG=E">1036880</a>, <a href="https://websmp110.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067414&_NLANG=E">1067414</a>
Regards,
Naveen.

Interface Mapping run time error...java.lang.nullpointerException thrown

Hi,
I am trying to create a simple f2f scenairo and when I tested the configuration xi throws this message as :
Interface Mapping run time error...java.lang.nullpointerException thrown during application mapping.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:TimeSent>2007-01-09T03:43:49Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>CAMEL_BS_01</SAP:Service>
<SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>Camel_BService_01</SAP:Service>
<SAP:Interface namespace="http://kia.com/fiel2file">Target01_MI</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>j5qiPBwVPU2yonkPwhdt/g==</SAP:ObjectId>
<SAP:SWCV>tR26oJ7nEdu5oM/vCXwv+g==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_Equipment_MM_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_Equipment_MM_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-01-09T03:43:49Z" wasRead="false">
<SAP:Engine type="AE">af.pi7.gbdci550</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2007-01-09T03:43:50Z" wasRead="false">
<SAP:Engine type="IS">is.03.gbdci550</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20070108</SAP:Date>
<SAP:Time>224350</SAP:Time>
<SAP:Host>gbdci550</SAP:Host>
<SAP:SystemId>PI7</SAP:SystemId>
<SAP:SystemNr>03</SAP:SystemNr>
<SAP:OS>AIX</SAP:OS>
<SAP:DB>DB6</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>014</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PIAFUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>002</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_MAPPING_REQUEST</SAP:PipelineService>
<SAP:QIdInternal>XBTOW0__0001</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">097C2FFA403445A30F7600CE</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>168</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2608</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>168</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>67</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Sender_Agreement_GUID>49574D50A74F3F5D902E20831759594C</SAP:Sender_Agreement_GUID>
<SAP:Serialize_Children>X</SAP:Serialize_Children>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.025474</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.064329</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.067038</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.085552</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.085573</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.472198</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.473649</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.483159</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.483341</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.48668</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.486921</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.49182</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.491835</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.720028</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.721545</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 9E0AD3009F9311DB8770000D60514DD2</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOW0__0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- 
<Trace level="1" type="T">Interface Mapping http://kia.com/fiel2file Equipment_IM_Outbound</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_Equipment_MM_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Please I request to give me some hint how to troubleshoot this issue.
Thanks a lot,
Srujan

Hi, i have the same type of error when testing configuration, but it seems that the mapping even doesn't start :
i'm creating an EBP to XCBL scenario, so it's a RFC->XI->XCBL 3.5
Here is the Java exception
Mappage d'interface
Can someone be helpful for that ?
Regards
Laurent
Message was edited by:
Laurent Gitton

Run time error COMPUTE_BCD_OVERFLOW coming at MFBF

Similar Messages

Maybe you are looking for