Run time error CONVT_NO NUMBER.
Hi,
I am getting the following error when i have writing the data.
I have reduced my itab-GAMNG to 5 characters
and i have a data which is *5000.
whenever this type of data comes i get the runtime error.
to avoid this error what should i do.
for eg:
data:idaylt(5) tYPE c.
idaylt = idaylt + itab_rep-pday
*5000 + 5428.
the answer should be in 10428, but because of the * i am getting a runtime error. to avoid this * which type of datatype shd i use.
please help and guide.
GAMNG is total order quantity and when you are converting it 5 characters..surely if the quantity is more than 5 char it is going to overflow, indicated by an asterix '*'.
So in your case the particular record the quantity cannot be accomodated in 5 chars and hence the asterix. If you try and perform numeric calculation on it...it is surely to fail. As in your example also please note that the value of the outcome would not be 10428 because 5000 is not the right value.
The <b>best solution</b> is to increase the field for itab-gamng to 10 chars and it should be fine. (using numeric for the field is a better option)
Similar Messages
-
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
3EDear 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. -
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" ?>
- <!-- Request Message Mapping
-->
- <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,
SrujanHi, 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 -
Xml Publisher run time error '5148'
Dear
I am using XML publisher to convert data in excel from the oracle,so first i have generated data in xml by report builder and open xml file in Word document through >template builder >data > load xml data,it's find but i use insert menu and select all field then it give message which i have mentioned below,
run time error '5148'
The number must be between 1 to 63
I think, is it column limitation because i have done this activity later but right now i have added more column so may be that's why it is showing the error but my client need to show data in excel,so how i can fulfill this requirement,is there any other solution ?
Please help on this regard. thanks in advance.Just for future poor souls who may be pulling their hair out over the same issue, I eventually got to the bottom of this cryptic error message.
Do not try to import all your fields at once if your group has over 63 of them, as it will fail.
If you use the Insert Table option, and try to put all the fields in at once, it will give you a more meaningful message, and the one it SHOULD have given you in the first place, which is "A table cannot contain more than 63 columns".
So - Import them, a few at a time. Then move them all into one group and you're good to go. -
Run time error while testing a service through transaction SICF/SOAMANAGER
Hi all,
We created a service for publishing the function module in web services through WSDL. When we try to test the service using SICF transaction / SOAMANAGER transaction, we get a run time error.
We are not sure whether any other settings or steps required for testing the web services..
Could you please let us know which steps/configurations we are missing?
Details of the run time error.
Service cannot be reached
What has happened?
URL http://in.ap1.sy.com:8000/wsnavigator call was terminated because the corresponding service is not available.
Note
The termination occurred in system ECC with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:J-i:INSISCSAPIDES_ECC_00-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
Thanks
SivaPlease ask you Basis admin to perform the following.
1) Check wether the Java Stack ( Portal, BI system etc) is avaliable in your landscape.
2) Execute tcode SOAMANAGER in ECC system. This will take you to a new browser where you have to login with your SAP username and password. Under SOA MANAGEMENT you can see Technical Configuration tab>click on System Global Settings>and select Access Information J2EE server. Here provide the hostname and the port number. Save the entries.
3)Execute tcode SMICM>Goto>Services. Here you can check for the HTTP Service Name/Port number
4) Activate the required services from tcode SICF
Thanks,
Sridhar -
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 creating sales order
hi all,
im working on ECC 4.7. normally when i create a sales order (VA01) and use incompletion log, it shows no errors. but when i start to save the same order . it shows a RUN TIME ERROR of ABAP . so plz help me to solve out this error
thanks\Hi Tarun,
When you get a run time error, you can see the error analysis on the left hand side. Check what the analysis is saying and you may need an ABAPer to find out the exact reason for the dump. I am just guessing it could be due to number range.. just a guess.
Regards,
Raghav -
While doing SO, im getting run time error - reg;
Hi,
While doing sales order and whenever im doing save its getting runtime error.
Runtime Errors MESSAGE_TYPE_X
Date and Time 14.12.2011 10:55:26
Short dump has not been completely stored (too big)
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Maintain the current CRM release (table CRMPAROLTP)
Long text of error message:
Diagnosis
Various transfer errors occur when transferring SAP sales orders to
CRM or there is no status update or the status update has errors
when transferring from CRM to the SAP system. This is caused by an
incorrect entry for the CRM release in the SAP table CRMPAROLTP, or
no entry is maintained at all.
System Response
To avoid data inconsistencies, this message causes a short dump.
Procedure
Maintain table CRMPAROLTP in your SAP system as is described in SAP
Note 691710 and then repeat the process again.
Procedure for System Administration
Technical information about the message:
Message class....... "V3"
Number.............. 302
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
Runtime Errors MESSAGE_TYPE_X
Date and Time 14.12.2011 10:55:26
hort dump has not been completely stored (too big)
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"
"BAPIDATEN_ERMITTELN"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "personal"
Network address...... "192.168.2.11"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 80686"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "PERSONAL"
Database type..... "ORACLE"
Database name..... "GCU"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 29 2006 00:18:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 75
Patch text.. " "
Runtime Errors MESSAGE_TYPE_X
Date and Time 14.12.2011 10:55:26
hort dump has not been completely stored (too big)
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 30311496
Heap.... 0
Page.... 139264
MM Used. 14538320
MM Free. 91952
User and Transaction
Client.............. 100
User................ "INFO_SD"
Language key........ "E"
Transaction......... "VA01 "
Program............. "SAPMV45A"
Screen.............. "SAPMV45A 4001"
Screen line......... 65
Information on where terminated
Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN".
The main program was "SAPMV45A ".
In the source code you have the termination point in line 338
of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".
Edited by: kiran35086 on Dec 14, 2011 6:30 AMDear kiran,
This might be many reasons.If you have not done configuration properly system will take you to dump(Run time error).
Try read the diagnosis possibly you may understand the problem.
If not You coordinate with your technical team.
Thanks&Regards
Raghu.k -
ALV issue: when save list using Local File command will get run time error!
help!!!!
report list using ALV method when to save this list using Local File.
i will get GETWA_NOT_ASSIGNED run time error information.
how resolve it?
source code :
REPORT ZIFT0103.
TABLES : MARA,MARC,CDHDR,CDPOS,MAKT.
******DEVK909212****************
****利用工厂来区分不同的SERVER的FTP ADDRESS ,user ,PASSWORD
DATA: FTP_WERKS LIKE MARC-WERKS.
********定义一个RANGE用来抓取MARC的信息
RANGES:R_MATNR FOR MARA-MATNR OCCURS 0.
********定义一个INTERNAL TABLE 来抓取MARC 的信息
DATA:BEGIN OF IT_MARC OCCURS 0,
MATNR LIKE MARC-MATNR,
WERKS LIKE MARC-WERKS,
USERNAME TYPE CDHDR-USERNAME,
UDATE TYPE CDHDR-UDATE,
FLAG_UI TYPE C,
END OF IT_MARC.
*******定义存放北京的数据的变量
DATA : BEGIN OF FTP_BEIJING OCCURS 0 ,
MATNR(25) ,
MATNR1(25) ,
MAKTX(30) ,
END OF FTP_BEIJING .
******定义福清的数据变量
DATA : BEGIN OF FTP_FUQING OCCURS 0 ,
MATNR(25) ,
MATNR1(25) ,
MAKTX(30) ,
END OF FTP_FUQING .
*******DEVK909212*****************
DATA : BEGIN OF FTP_ITEMDOC1 OCCURS 0 ,
MATNR(25) ,
MAKTX(30) ,
END OF FTP_ITEMDOC1 .
DATA : BEGIN OF FTP_ITEMDOC OCCURS 0 ,
MATNR(25) ,
MATNR1(25) ,
MAKTX(30) ,
END OF FTP_ITEMDOC .
DATA: WA_ZMSGTA TYPE ZMSGTA ,
l_ersda like MARA-ERSDA .
***********DEVK909553********************
****用来决定执行FTP还是显示LIST**********
DATA:g_tcode_flag.
***********DEVK909553********************
Error message process ******************************
DEFINE EXPLAIN_MSG.
break soe_richard.
CALL FUNCTION 'BAPI_MESSAGE_GETDETAIL'
EXPORTING
ID = &1 "SY-MSGID
NUMBER = &2 "SY-MSGNO
LANGUAGE = SY-LANGU
TEXTFORMAT = &3
LINKPATTERN =
MESSAGE_V1 = &4 "SY-MSGV1
MESSAGE_V2 = &5 "SY-MSGV2
MESSAGE_V3 = &6 "SY-MSGV3
MESSAGE_V4 = &7 "SY-MSGV4
IMPORTING
MESSAGE = &8 "WA_ZMSGTA-MSE1
RETURN =
TABLES
TEXT =
END-OF-DEFINITION.
DEFINE ERROR_MSG_UPDATA.
CALL FUNCTION 'ZINSERT_MSG' "IN UPDATE TASK
EXPORTING
XZMSGTA = &1 "WA_ZMSGTA
EXCEPTIONS
UPDATE_ERROR = 1
OTHERS = 2.
END-OF-DEFINITION.
IF SY-TCODE = 'ZIFT103' .
g_tcode_flag = 'L'.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
PERCENTAGE = 0
TEXT = '请耐心等候,系统正在抓数据'.
ENDIF.
l_ersda = sy-datum - 1 . "取前一天产生的物料号码。
DATA:BEGIN OF it_change OCCURS 0,
OBJECTID TYPE CDHDR-OBJECTID,
USERNAME TYPE CDHDR-USERNAME,
UDATE TYPE CDHDR-UDATE,
TABKEY TYPE CDPOS-TABKEY,
END OF it_change.
DATA:BEGIN OF it_cDhdr OCCURS 0,
OBJECTID type CDHDR-OBJECTID,
CHANGENR TYPE CDHDR-CHANGENR,
USERNAME TYPE CDHDR-USERNAME,
UDATE TYPE CDHDR-UDATE,
END OF it_cdhdr.
DATA:search_len TYPE I.
DATA:BEGIN of it_insert OCCURS 0,
MATNR TYPE MARA-MATNR,
WERKS TYPE MARC-WERKS,
END OF it_insert.
DATA:BEGIN OF it_MAKT OCCURS 0,
MATNR TYPE MAKT-MATNR,
MAKTX TYPE MAKT-MAKTX,
END OF it_makt.
DATA IT_MARA TYPE TABLE OF MARA WITH HEADER LINE.
DATA:BEGIN OF IT_OUT OCCURS 0,
MATNR TYPE MARA-MATNR,
WERKS TYPE MARC-WERKS,
MTART TYPE MARA-MTART,
MEINS TYPE MARA-MEINS,
MATKL TYPE MARA-MATKL,
MAKTX TYPE MAKT-MAKTX,
PSTAT TYPE MARA-PSTAT,
BRGEW TYPE MARA-BRGEW,
NTGEW TYPE MARA-NTGEW,
GEWEI TYPE MARA-GEWEI,
FERTH TYPE MARA-FERTH,
KZUMW TYPE MARA-KZUMW,
ERNAM TYPE MARA-ERNAM,
ERSDA TYPE MARA-ERSDA,
END OF IT_OUT.
*-- DECLARE DATA FOR ALV
TYPE-POOLS: slis.
DATA : g_variant LIKE disvariant,
g_save(1) TYPE c,
g_exit(1) TYPE c,
gx_variant LIKE disvariant.
DATA: gt_fieldcat TYPE slis_t_fieldcat_alv WITH HEADER LINE, "
gt_events TYPE slis_t_event,
gt_list_top_of_page TYPE slis_t_listheader,
gs_print TYPE slis_print_alv,
gs_layout TYPE slis_layout_alv .
******只能抓出系统有做更改的数据***************
******而第一次INSERT MARA的数据抓不出来********
START-OF-SELECTION.
SELECT AOBJECTID AUSERNAME AUDATE BTABKEY
INTO TABLE it_change
FROM ( CDPOS AS B INNER JOIN CDHDR AS A ON
AOBJECTCLAS = BOBJECTCLAS AND
AOBJECTID = BOBJECTID AND
ACHANGENR = BCHANGENR )
WHERE A~OBJECTCLAS = 'MATERIAL'
AND A~UDATE = l_ersda
AND B~TABNAME = 'MARC'
AND B~CHNGIND = 'I'.
LOOP AT it_change.
search_len = STRLEN( it_change-TABKEY ).
search_len = search_len - 4.
IF search_len > 0.
IT_MARC-WERKS = it_change-TABKEY+search_len(4).
ENDIF.
IT_MARC-MATNR = it_change-objectid+0(18).
IT_MARC-USERNAME = it_change-username.
IT_MARC-UDATE = It_change-udate.
IT_MARC-FLAG_UI = 'U'.
APPEND IT_MARC.
CLEAR IT_MARC.
CLEAR R_MATNR.
R_MATNR-SIGN = 'I'.
R_MATNR-OPTION = 'EQ'.
R_MATNR-LOW = IT_MARC-MATNR.
APPEND R_MATNR.
ENDLOOP.
****CDPOS is Cluster TABLE 所以没有办法用INNER JOIN******
SELECT OBJECTID CHANGENR USERNAME UDATE
INTO TABLE it_cdhdr
FROM CDHDR
WHERE OBJECTCLAS = 'MATERIAL'
AND UDATE = l_ersda.
AND TCODE = 'MM02'.
LOOP AT IT_cdhdr.
SELECT * FROM CDPOS
WHERE OBJECTCLAS = 'MATERIAL'
AND OBJECTID = IT_CDHDR-OBJECTID
AND CHANGENR = IT_CDHDR-CHANGENR
AND TABNAME = 'MARC'
AND CHNGIND = 'I'.
search_len = STRLEN( CDPOS-TABKEY ).
search_len = search_len - 4.
IF search_len > 0.
IT_MARC-WERKS = CDPOS-TABKEY+search_len(4).
ENDIF.
IT_MARC-MATNR = IT_cdhdr-objectid+0(18).
IT_MARC-USERNAME = IT_cdhdr-username.
IT_MARC-UDATE = IT_cdhdr-udate.
IT_MARC-FLAG_UI = 'U'.
APPEND IT_MARC.
CLEAR IT_MARC.
CLEAR R_MATNR.
R_MATNR-SIGN = 'I'.
R_MATNR-OPTION = 'EQ'.
R_MATNR-LOW = IT_MARC-MATNR.
APPEND R_MATNR.
CLEAR IT_MARC.
ENDSELECT.
ENDLOOP.
IF g_tcode_flag = 'L'.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
PERCENTAGE = 20
TEXT = '处理好当天CHANGE的数据'.
ENDIF.
*******抓当天做了INSERT的数据*************
*******不需要***********************
SELECT BMATNR BWERKS INTO TABLE IT_INSERT
FROM MARC AS B JOIN MARA AS A
ON AMATNR = BMATNR
WHERE A~ERSDA = l_ersda.
LOOP AT IT_INSERT.
IT_MARC-MATNR = IT_INSERT-MATNR.
IT_MARC-WERKS = IT_INSERT-WERKS.
IT_MARC-FLAG_UI = 'I'.
APPEND IT_MARC.
CLEAR IT_MARC.
CLEAR R_MATNR.
R_MATNR-SIGN = 'I'.
R_MATNR-OPTION = 'EQ'.
R_MATNR-LOW = IT_MARC-MATNR.
APPEND R_MATNR.
ENDLOOP.
IF g_tcode_flag = 'L'.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
PERCENTAGE = 40
TEXT = '处理好当天INSERT的数据'.
ENDIF.
IF g_tcode_flag = 'L'.
PERFORM get_MAKTX.
PERFORM get_mara.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
PERCENTAGE = 100
TEXT = '处理好数据,并开始显示数据'.
PERFORM do_data.
PERFORM display_alv.
ELSE.
PERFORM get_MAKTX.
PERFORM do_ftp.
ENDIF.
*& Form get_marktx
text
FORM get_maktx.
SELECT MATNR MAKTX INTO TABLE IT_MAKT FROM MAKT
WHERE MATNR IN R_MATNR AND SPRAS = '1'.
ENDFORM. "get_marktx
*& Form get_mara
text
FORM get_mara.
SELECT * INTO TABLE it_mara FROM MARA
WHERE MATNR IN R_MATNR.
ENDFORM. "get_mara
*& Form do_data
text
FORM do_data.
SORT IT_MARC BY MATNR WERKS.
DELETE ADJACENT DUPLICATES FROM IT_MARC COMPARING MATNR WERKS.
LOOP AT IT_MARC.
CLEAR IT_MAKT.
CLEAR IT_MARA.
READ TABLE IT_MAKT WITH KEY MATNR = IT_MARC-MATNR.
READ TABLE IT_MARA WITH KEY MATNR = IT_MARC-MATNR.
MOVE-CORRESPONDING IT_MARA TO IT_OUT.
IT_OUT-MAKTX = IT_MAKT-MAKTX.
IT_OUT-WERKS = IT_MARC-WERKS.
IF IT_MARC-FLAG_UI = 'U'.
IT_OUT-ERNAM = IT_MARC-USERNAME.
ENDIF.
APPEND IT_OUT.
CLEAR IT_OUT.
ENDLOOP.
ENDFORM. "do_data
*SELECT AMATNR BMAKTX INTO CORRESPONDING
*FIELDS OF FTP_ITEMDOC1 FROM MARA AS A JOIN MAKT AS B
*ON AMATNR = BMATNR WHERE A~ERSDA = l_ersda
*AND B~SPRAS = '1' . "代表为中文说明。
APPEND FTP_ITEMDOC1.
*******DEVK909212****************
*******添加RANGE*****************
CLEAR R_MATNR.
R_MATNR-SIGN = 'I'.
R_MATNR-OPTION = 'EQ'.
R_MATNR-LOW = FTP_ITEMDOC1-MATNR.
APPEND R_MATNR.
CLEAR FTP_ITEMDOC1.
*******DEVK909212****************
*ENDSELECT.
*******DEVK909212****************
****get WERKS information from MARC*******
*SELECT MATNR WERKS INTO TABLE IT_MARC
*FROM MARC
*WHERE MATNR IN R_MATNR.
*******DEVK909212****************
******DEVK909212****************
**MARK**************************
*LOOP AT FTP_ITEMDOC1 .
MOVE : FTP_ITEMDOC1-MATNR TO FTP_ITEMDOC-MATNR,
FTP_ITEMDOC1-MATNR TO FTP_ITEMDOC-MATNR1,
FTP_ITEMDOC1-MAKTX TO FTP_ITEMDOC-MAKTX.
APPEND FTP_ITEMDOC.
CLEAR FTP_ITEMDOC.
*ENDLOOP.
******DEVK909212****************
******DEVK909212***********************************
**根据IT_MARC中信息,往北京和福清的TABLE写数据*****
FORM do_ftp.
LOOP AT IT_MARC.
***福清的
IF IT_MARC-WERKS = '1010' OR IT_MARC-WERKS = '1020'
OR IT_MARC-WERKS = '1023' .
READ TABLE FTP_ITEMDOC1 WITH KEY MATNR = IT_MARC-MATNR.
MOVE : FTP_ITEMDOC1-MATNR TO FTP_FUQING-MATNR,
FTP_ITEMDOC1-MATNR TO FTP_FUQING-MATNR1,
FTP_ITEMDOC1-MAKTX TO FTP_FUQING-MAKTX.
CLEAR IT_MAKT.
READ TABLE IT_MAKT WITH KEY = IT_MARC-MATNR.
MOVE : IT_MARC-MATNR TO FTP_FUQING-MATNR,
IT_MARC-MATNR TO FTP_FUQING-MATNR1,
IT_MAKT-MAKTX TO FTP_FUQING-MAKTX.
APPEND FTP_FUQING.
CLEAR FTP_FUQING.
ENDIF.
***北京的
IF IT_MARC-WERKS = '1041' OR IT_MARC-WERKS = '1042'.
READ TABLE FTP_ITEMDOC1 WITH KEY MATNR = IT_MARC-MATNR.
MOVE : FTP_ITEMDOC1-MATNR TO FTP_BEIJING-MATNR,
FTP_ITEMDOC1-MATNR TO FTP_BEIJING-MATNR1,
FTP_ITEMDOC1-MAKTX TO FTP_BEIJING-MAKTX.
CLEAR IT_MAKT.
READ TABLE IT_MAKT WITH KEY = IT_MARC-MATNR.
MOVE : IT_MARC-MATNR TO FTP_BEIJING-MATNR,
IT_MARC-MATNR TO FTP_BEIJING-MATNR1,
IT_MAKT-MAKTX TO FTP_BEIJING-MAKTX.
APPEND FTP_BEIJING.
CLEAR FTP_BEIJING.
ENDIF.
ENDLOOP.
****清楚重复的数据**********
SORT FTP_FUQING.
DELETE ADJACENT DUPLICATES FROM FTP_FUQING.
SORT FTP_BEIJING.
DELETE ADJACENT DUPLICATES FROM FTP_BEIJING.
***传送数据********
REFRESH FTP_ITEMDOC.
FTP_ITEMDOC[] = FTP_FUQING[].
FTP_WERKS = '1010'.
PERFORM ftp_work.
REFRESH FTP_ITEMDOC.
FTP_ITEMDOC[] = FTP_BEIJING[].
FTP_WERKS = '1041'.
PERFORM ftp_work.
******DEVK909212***********************************
ENDFORM. "do_ftp
*& Form ftp_work
把以前FTP的工作做一个FORM
*******DEVK909212**************************
FORM ftp_work.
*******DEVK909212**************************
CHECK FTP_ITEMDOC[] IS NOT INITIAL.
FTP function *****************************************************
DATA : HDL TYPE I,
L_SLEN TYPE I ,
ERROR,
KEY TYPE I VALUE 26101957,
DEST TYPE RFCDES-RFCDEST VALUE 'SAPFTPA'.
DATA: FTP_RESULT TYPE TABLE OF TEXT.
DATA: P_FILE TYPE RLGRAP-FILENAME.
DATA: L_USER(16) TYPE C VALUE 'SFIS',
L_PWD(16) TYPE C VALUE 'SFIS',
L_HOST(16) TYPE C VALUE '172.16.31.17'.
*******DEVK909212**************************
*****根据不同的工厂来抓FTP的信息
CALL FUNCTION 'Z_FTP_SFIS'
EXPORTING
BLART = 'S'
WERKS = FTP_WERKS
IMPORTING
HOST = L_HOST
USER1 = L_USER
PASS1 = L_PWD.
*******DEVK909212**************************
CONCATENATE l_ersda '.KP' INTO P_FILE.
SET EXTENDED CHECK OFF.
ERROR = 0.
CHECK HDL IS INITIAL.
Connect to server
L_SLEN = STRLEN( L_PWD ).
CALL FUNCTION 'HTTP_SCRAMBLE'
EXPORTING
SOURCE = L_PWD
SOURCELEN = L_SLEN
KEY = KEY
IMPORTING
DESTINATION = L_PWD.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
TEXT = 'Connect to FTP Server'.
CALL FUNCTION 'FTP_CONNECT'
EXPORTING
USER = L_USER
PASSWORD = L_PWD
HOST = L_HOST
RFC_DESTINATION = DEST
IMPORTING
HANDLE = HDL
EXCEPTIONS
NOT_CONNECTED = 1
OTHERS = 2.
IF SY-SUBRC <> 0.
MOVE: 'B' TO WA_ZMSGTA-BLART,
l_ersda TO WA_ZMSGTA-REFNUMBER,
SY-MSGTY TO WA_ZMSGTA-MSGTY,
'MARA' TO WA_ZMSGTA-TBMA_VAL.
EXPLAIN_MSG SY-MSGID SY-MSGNO ' ' SY-MSGV1 SY-MSGV2 SY-MSGV3
SY-MSGV4 WA_ZMSGTA-MSE1.
ERROR_MSG_UPDATA WA_ZMSGTA.
EXIT.
ENDIF.
CALL FUNCTION 'FTP_COMMAND'
EXPORTING
HANDLE = HDL
COMMAND = 'ascii'
TABLES
DATA = FTP_RESULT
EXCEPTIONS
TCPIP_ERROR = 1
COMMAND_ERROR = 2
DATA_ERROR = 3.
IF SY-SUBRC <> 0.
EXPLAIN_MSG SY-MSGID SY-MSGNO ' ' SY-MSGV1 SY-MSGV2 SY-MSGV3
SY-MSGV4 WA_ZMSGTA-MSE1.
MOVE: 'B' TO WA_ZMSGTA-BLART,
l_ersda TO WA_ZMSGTA-REFNUMBER,
SY-MSGTY TO WA_ZMSGTA-MSGTY,
'MARA' TO WA_ZMSGTA-TBMA_VAL.
ERROR_MSG_UPDATA WA_ZMSGTA.
EXIT.
ENDIF.
CALL FUNCTION 'FTP_R3_TO_SERVER'
EXPORTING
HANDLE = HDL
FNAME = P_FILE
CHARACTER_MODE = 'X'
TABLES
TEXT = FTP_ITEMDOC
EXCEPTIONS
TCPIP_ERROR = 1
COMMAND_ERROR = 2
DATA_ERROR = 3
OTHERS = 4.
IF SY-SUBRC <> 0.
EXPLAIN_MSG SY-MSGID SY-MSGNO ' ' SY-MSGV1 SY-MSGV2 SY-MSGV3
SY-MSGV4 WA_ZMSGTA-MSE1.
MOVE: 'B' TO WA_ZMSGTA-BLART,
l_ersda TO WA_ZMSGTA-REFNUMBER,
SY-MSGTY TO WA_ZMSGTA-MSGTY,
'MARA' TO WA_ZMSGTA-TBMA_VAL.
ERROR_MSG_UPDATA WA_ZMSGTA.
EXIT.
ENDIF.
*******DEVK909212**************************
*******CLOSE FTP******************
CHECK NOT HDL IS INITIAL.
CALL FUNCTION 'FTP_DISCONNECT'
EXPORTING
HANDLE = HDL.
CALL FUNCTION 'RFC_CONNECTION_CLOSE'
EXPORTING
DESTINATION = DEST
EXCEPTIONS
OTHERS = 1.
CLEAR HDL.
ENDFORM. "ftp_work
*******DEVK909212**************************
FORM DISPLAY_ALV .
*-- PREPARE ALV DATA
PERFORM EVENTTAB_BUILD USING GT_EVENTS[].
PERFORM COMMENT_BUILD USING GT_LIST_TOP_OF_PAGE[].
*-- LAYOUT SETTING
PERFORM PREPARE_ALV_FIELD USING GT_FIELDCAT[].
*-- ALV DISPLAY
PERFORM CALL_REUSE_ALV_GRID_DISPLAY.
ENDFORM. " display_alv
*& Form eventtab_build
text
-->P_GT_EVENTS[] text
FORM EVENTTAB_BUILD USING PT_EVENTS TYPE SLIS_T_EVENT.
DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
I_LIST_TYPE = 0
IMPORTING
ET_EVENTS = PT_EVENTS.
READ TABLE PT_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
INTO LS_EVENT.
IF SY-SUBRC = 0.
LS_EVENT-FORM = 'TOP_OF_PAGE'.
MODIFY PT_EVENTS FROM LS_EVENT INDEX SY-TABIX.
ENDIF.
ENDFORM. " eventtab_build
*& Form comment_build
text
-->P_GT_LIST_TOP_OF_PAGE[] text
FORM COMMENT_BUILD USING PT_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA: LS_LINE TYPE SLIS_LISTHEADER,
L_DATE(30),
l_v_BWKEY like T001W-BWKEY, "Valuation area
l_v_BUKRS like T001K-BUKRS. "Firm/Company
Listenerschrift: Typ H
CLEAR LS_LINE.
LS_LINE-TYP = 'H'.
LS_LINE-KEY: not used for this type
select single BWKEY
into l_v_BWKEY
from t001w
where WERKS IN s_WERKS.
select single BUKRS
into l_v_BUKRS
from t001k
where BWKEY = l_v_BWKEY.
SELECT SINGLE butxt INTO LS_LINE-INFO
FROM t001
WHERE bukrs = l_v_BUKRS.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
Kopfinfo: Typ S
CLEAR LS_LINE.
LS_LINE-TYP = 'S'.
LS_LINE-KEY = '报表名称:'.
LS_LINE-INFO = SY-TITLE.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
CLEAR LS_LINE.
LS_LINE-TYP = 'S'.
LS_LINE-KEY = '打印日期:'.
WRITE SY-DATUM TO LS_LINE-INFO.
ls_line-info = sy-datum.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
CLEAR LS_LINE.
LS_LINE-TYP = 'S'.
LS_LINE-KEY = '打印時間:'.
WRITE SY-UZEIT TO LS_LINE-INFO.
ls_line-info = sy-uzeit.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
CLEAR LS_LINE.
LS_LINE-TYP = 'S'.
LS_LINE-KEY = '使用者:'.
LS_LINE-INFO = SY-UNAME.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
ENDFORM. " comment_build
*& Form prepare_alv_field
text
-->P_GT_FIELDCAT[] text
FORM PREPARE_ALV_FIELD USING P_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV.
DATA: LS_LINE TYPE SLIS_FIELDCAT_ALV.
*-- DEFINE MARCO
DEFINE APPEND_ALV_FIELD.
CLEAR LS_LINE.
LS_LINE-FIELDNAME = &1.
LS_LINE-TABNAME = &2.
LS_LINE-REPTEXT_DDIC = &3.
LS_LINE-SELTEXT_L = &3.
LS_LINE-SELTEXT_M = &3.
LS_LINE-SELTEXT_S = &3.
LS_LINE-QFIELDNAME = &4.
LS_LINE-QTABNAME = &5.
LS_LINE-NO_OUT = &6.
LS_LINE-NO_ZERO = &7.
LS_LINE-OUTPUTLEN = &8.
APPEND LS_LINE TO P_FIELDCAT.
END-OF-DEFINITION.
APPEND_ALV_FIELD: 'MATNR' 'IT_OUT' '料号'
'O' 'X' ''.
APPEND_ALV_FIELD: 'WERKS' 'IT_OUT' '工厂'
'O' 'X' ''.
APPEND_ALV_FIELD: 'MTART' 'IT_OUT' 'MTyp'
'O' 'X' ''.
APPEND_ALV_FIELD: 'MEINS' 'IT_OUT' 'BUn'
'O' 'X' ''.
APPEND_ALV_FIELD: 'MATKL' 'IT_OUT' '物料组\分群码'
'O' 'X' ''.
APPEND_ALV_FIELD: 'MATKX' 'IT_OUT' '物料描述'
'O' 'X' ''.
APPEND_ALV_FIELD: 'PSTAT' 'IT_OUT' '维护状态'
'O' 'X' ''.
APPEND_ALV_FIELD: 'BRGEW' 'IT_OUT' '毛重'
'O' 'X' ''.
APPEND_ALV_FIELD: 'NTGEW' 'IT_OUT' '净重'
'O' 'X' ''.
APPEND_ALV_FIELD: 'GEWEI' 'IT_OUT' 'WUn'
'O' 'X' ''.
APPEND_ALV_FIELD: 'FERTH' 'IT_OUT' '对外机种名'
'O' 'X' ''.
APPEND_ALV_FIELD: 'KZUMW' 'IT_OUT' '高关税标识'
'O' 'X' ''.
APPEND_ALV_FIELD: 'ERNAM' 'IT_OUT' '创建者'
'O' 'X' ''.
APPEND_ALV_FIELD: 'ERSDA' 'IT_OUT' '创建日期'
'O' 'X' ''.
ENDFORM. " prepare_alv_field
*& Form call_reuse_alv_grid_display
text
--> p1 text
<-- p2 text
FORM CALL_REUSE_ALV_GRID_DISPLAY .
gs_layout-f2code = 'DISPLAY'.
gs_print-no_print_listinfos = 'X'.
gs_layout-colwidth_optimize = 'X'. "列宽度自动根据内容优化
gs_layout-f2code = '&ETA'. "double check弹出详细信息
gs_layout-zebra = 'X'. "清单条纹显示
gs_layout-no_vline = ''. "是否显示列间隔线
gs_layout-box_fieldname = ''. "是否显示checkbox
gs_layout-confirmation_prompt = ''. "推出清单是否提示
gs_layout-detail_titlebar = '详细信息'."详细清单的标题
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = SY-CPROG
I_BACKGROUND_ID = 'ALV_BACKGROUND'
I_CALLBACK_PF_STATUS_SET = 'ALV_PF_STATUS'
I_CALLBACK_USER_COMMAND = 'ALV_USER_COMMAND'
I_CALLBACK_TOP_OF_PAGE = GT_LIST_TOP_OF_PAGE[]
IT_FIELDCAT = GT_FIELDCAT[]
IT_EVENTS = GT_EVENTS[]
I_STRUCTURE_NAME = 'IT_OUT'
I_SAVE = 'A'
IS_LAYOUT = GS_LAYOUT
IS_PRINT = GS_PRINT
TABLES
T_OUTTAB = IT_OUT
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " call_reuse_alv_grid_display
*& Form PREPARE_ALV_FIELD
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = GT_LIST_TOP_OF_PAGE.
ENDFORM. "TOP_OF_PAGEHi,
Please check your field catalog and refer field names once again.
Check spelling, or Check strucutre properly.
There are something wrong in your catalog definition
aRs. -
I am using FM - F4IF_INT_TABLE_VALUE_REQUEST on a selection screenf field. After that I do some validation and throw an error message in the at selection screen event.
But this results in DYNPRO_MSG_IN_HELP error.
I need to have the error message. I cannot change it to Info or Success message. (Program doesn't give run time error if i change the message to S or I or W ). How do I get around this ? What is wrong with F4IF_INT_TABLE_VALUE_REQUEST .
Am I not calling it correctly ?
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
retfield = 'CLASS' "Field from it_class
dynpprog = sy-cprog "Program
dynpnr = sy-dynnr "Dynpro number
dynprofield = 'P_FOLD' "Select-options field
value_org = 'S' "Value return: C: cell by cell, "S: structured
display = 'F' "Override readiness for input
TABLES
value_tab = it_class "table with selection values
return_tab = t_return "Return value
EXCEPTIONS
parameter_error = 1
no_values_found = 2
OTHERS = 3.
Error Message: The program attempted to issue a " " message during "F4" processing.
This is an illegal operation.
The program was terminated.
Screen name.............. "ZMMR0010_INFORECORD_UPDT"
Screen number............ 0200
Edited by: Shareen Hegde on Mar 29, 2011 1:47 AMHi,
ther are 3 things you can change.
Parameter dynpprog shouldn't be sy-cprog or sy-repid. Please decalre a variable where you can pass the value of sy-cprog to and give it to that parameter.
Parameter dynpnr shouldn't be sy-dynnr. Please decalre a variable where you can pass the value of sy-dynnr to and give it to that parameter.
Parameter display is of type DDBOOL_D and can have value 'X' or SPACE (see fix values of domain DDBOOL!).
Regards,
Klaus -
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 PradhanHi 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 doing PGI
hi gurus
while doing PGI i am experiencing run time error.
the ERROR ANALYSIS says that " check doc number 49 in company code 1234 and fiscal year 2007. and correct the number range status if necessary".
i'm confused. please guide how to rectify the problem.
thank you all in advance
regards
madhuCreate new number range in T.Code:FBN1
Go to menu path:
IMG > Materials Management >Inventory Management and Physical Inventory > Number Assignment > Define Number Assignment for Accounting Documents
Click on "Financial Accounting Document Types"
go to Accounting Documents WA, WI, WL and double click on them and change the number range to the new number range created.
Regards
AK -
RUN Time error while use filter table in query generator
Hai..
I have 2 Functions under "Scalar valued functions" in SQL Server,i try to call this functions in Query generator its working fine,result also display correctly, but i click filter table system showing Error Message " Run Time Error,Abnormal program termination" then SAP is get closed,i tested this scenario in 3 Database am getting same error , Is this BUG in SAP B1?There is no error number in error messageThis is my function
set ANSI_NULLS ON
set QUOTED_IDENTIFIER ON
go
-- =============================================
-- Author: <Author,,Name>
-- Create date: <Create Date, ,>
-- Description: <Description, ,>
-- =============================================
ALTER function [dbo].[Get_TransObjName](@Obj_type NUMERIC(20,5))
returns varchar(500) as
BEGIN
DECLARE @Obj_type_Name varchar(100)
select @Obj_type_Name =
case @Obj_type
when -2 then 'Opening Balance'
when -3 then 'Closing Balance'
when 1 then 'oChartOfAccounts'
when 2 then 'oBusinessPartners'
when 3 then 'oBanks'
when 4 then 'oItems'
when 5 then 'oVatGroups'
when 6 then 'oPriceLists'
when 7 then 'oSpecialPrices'
when 8 then 'oItemProperties'
when 12 then 'oUsers'
when 13 then 'A/R Invoices'
when 14 then 'A/R Credit Memo'
when 15 then 'A/R DeliveryNotes'
when 16 then 'A/R Returns'
when 17 then 'oOrders'
when 18 then 'A/P Invoice'
when 19 then 'A/P Credit Memo'
when 20 then 'Goods Receipt PO'
when 21 then 'Goods Returns'
when 22 then 'PurchaseOrders'
when 23 then 'Quotations'
when 24 then 'IncomingPayments'
when 25 then 'Deposit'
when 28 then 'oJournalVouchers'
when 30 then 'JournalEntries'
when 31 then 'oStockTakings'
when 33 then 'oContacts'
when 36 then 'oCreditCards'
when 37 then 'oCurrencyCodes'
when 40 then 'oPaymentTermsTypes'
when 42 then 'oBankPages'
when 43 then 'oManufacturers'
when 46 then 'VendorPayments'
when 48 then 'oLandedCostsCodes'
when 49 then 'oShippingTypes'
when 50 then 'oLengthMeasures'
when 51 then 'oWeightMeasures'
when 52 then 'oItemGroups'
when 53 then 'oSalesPersons'
when 56 then 'oCustomsGroups'
when 57 then 'ChecksforPayment'
when 58 then 'Stock List'
when 59 then 'Goods Receipt'
when 60 then 'Goods Issue'
when 64 then 'oWarehouses'
when 65 then 'oCommissionGroups'
when 66 then 'oProductTrees'
when 67 then 'Inventory Transfers'
when 68 then 'oWorkOrders'
when 69 then 'Landed Costs'
when 70 then 'oCreditPaymentMethods'
when 71 then 'oCreditCardPayments'
when 73 then 'oAlternateCatNum'
when 76 then 'Postdated Deposit'
when 77 then 'oBudget'
when 78 then 'oBudgetDistribution'
when 81 then 'oMessages'
when 91 then 'oBudgetScenarios'
when 97 then 'oSalesOpportunities'
when 93 then 'oUserDefaultGroups'
when 101 then 'oSalesStages'
when 103 then 'oActivityTypes'
when 104 then 'oActivityLocations'
when 112 then 'oDrafts'
when 116 then 'oDeductionTaxHierarchies'
when 117 then 'oDeductionTaxGroups'
when 125 then 'oAdditionalExpenses'
when 126 then 'oSalesTaxAuthorities'
when 127 then 'oSalesTaxAuthoritiesTypes'
when 128 then 'oSalesTaxCodes'
when 134 then 'oQueryCategories'
when 138 then 'oFactoringIndicators'
when 140 then 'oPaymentsDrafts'
when 142 then 'oAccountSegmentations'
when 143 then 'oAccountSegmentationCategories'
when 144 then 'oWarehouseLocations'
when 145 then 'oForms1099'
when 146 then 'oInventoryCycles'
when 147 then 'oWizardPaymentMethods'
when 150 then 'oBPPriorities'
when 151 then 'oDunningLetters'
when 152 then 'oUserFields'
when 153 then 'oUserTables'
when 156 then 'oPickLists'
when 158 then 'oPaymentRunExport'
when 160 then 'oUserQueries'
when 162 then 'Inventory Valuation'
when 163 then 'oCorrectionPurchaseInvoice'
when 164 then 'oCorrectionPurchaseInvoiceReversal'
when 165 then 'oCorrectionInvoice'
when 166 then 'oCorrectionInvoiceReversal'
when 170 then 'oContractTemplates'
when 171 then 'oEmployeesInfo'
when 176 then 'oCustomerEquipmentCards'
when 178 then 'oWithholdingTaxCodes'
when 182 then 'oBillOfExchangeTransactions'
when 189 then 'oKnowledgeBaseSolutions'
when 190 then 'oServiceContracts'
when 191 then 'oServiceCalls'
when 193 then 'oUserKeys'
when 194 then 'oQueue'
when 198 then 'oSalesForecast'
when 200 then 'oTerritories'
when 201 then 'oIndustries'
when 202 then 'oProductionOrders'
when 203 then 'A/R Down Payment'
when 204 then 'A/P Down Payment'
when 205 then 'oPackagesTypes'
when 206 then 'oUserObjectsMD'
when 211 then 'oTeams'
when 212 then 'oRelationships'
when 214 then 'oUserPermissionTree'
when 217 then 'oActivityStatus'
when 218 then 'oChooseFromList'
when 219 then 'oFormattedSearches'
when 221 then 'oAttachments2'
when 223 then 'oUserLanguages'
when 224 then 'oMultiLanguageTranslations'
when 229 then 'oDynamicSystemStrings'
when 231 then 'oHouseBankAccounts'
when 247 then 'oBusinessPlaces'
when 250 then 'oLocalEra'
when 280 then 'oSalesTaxInvoice'
when 281 then 'oPurchaseTaxInvoice'
when 300 then 'BoRecordset'
when 305 then 'BoBridge'
when 260 then 'oNotaFiscalUsage'
when 258 then 'oNotaFiscalCFOP'
when 259 then 'oNotaFiscalCST'
when 261 then 'oClosingDateProcedure'
when 10 then 'oBusinessPartnerGroups'
when 278 then 'oBPFiscalRegistryID'
else cast(@Obj_type as char(20)) end
return @Obj_type_Name
END -
Dear ALL,
When we are creating sales order after entering sold-to-party, Material & Quantity when we press ENTER key That time
we are getting following run time error
Hoe to resolve this?
Runtime Errors SAPSQL_INVALID_FIELDNAME
Except. CX_SY_DYNAMIC_OSQL_SEMANTICS
Date and Time 15.01.2009 16:04:19
Short dump has not been completely stored (too big)
Short text
A dynamically specified column name is unknown.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLV61Z" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
not caught in
procedure "SEL_KONDTAB" "(FORM)", nor was it propagated by a RAISING 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:
An Open SQL clause was specified dynamically. The contained field name
"ALAND" does not exist in any of the database tables from the FROM clause.
How to correct the error
Check the field name in the SELECT clause.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"SAPSQL_INVALID_FIELDNAME" "CX_SY_DYNAMIC_OSQL_SEMANTICS"
"SAPLV61Z" or "LV61ZU01"
"SEL_KONDTAB"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SEL_KONDTAB" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "slgsap-prd"
Network address...... "10.140.1.11"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SLGSAP-PRD"
Database type..... "MSSQL"
Database name..... "PRD"
Database user ID.. "prd"
Terminal................. "SD0123l"
Char.set.... "C"
SAP kernel....... 700
created (date)... "May 6 2008 00:13:21"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 159
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 20949200
Heap.... 0
Page.... 196608
MM Used. 15928048
MM Free. 828016
User and Transaction
Client.............. 900
User................ "ADMIN"
Language key........ "E"
Transaction......... "VA01 "
Transactions ID..... "03F0E2DD6B35F16CBBFF002219897F24"
Program............. "SAPLV61Z"
Screen.............. "SAPMV45A 4900"
Screen line......... 930
Information on where terminated
Termination occurred in the ABAP program "SAPLV61Z" - in "SEL_KONDTAB".
The main program was "SAPMV45A ".
In the source code you have the termination point in line 672
of the (Include) program "LV61ZU01".
The termination is caused because exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"
occurred in
procedure "SEL_KONDTAB" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPLV61Z "; its source code begins in line
260 of the (Include program "LV61ZU01 ".
Source Code Extract
Line SourceCde
642 if se_prestep = yes or
643 se_read_only_one_record = yes.
644 if t681-ksdat is initial.
645 if se_read_all_prestep is initial.
646 select * from (t681-kotab) appending table <cond_tab>
647 up to 1 rows
648 where kappl = se_kappl
649 and kschl = se_kschl
650 and (coding_tab).
651 h_subrc = sy-subrc.
652 else.
653 select * from (t681-kotab) appending table <cond_tab>
654 where kappl = se_kappl
655 and kschl = se_kschl
656 and (coding_tab).
657 endif.
658
659 * it is enough to find one record in prestep
660 * (care must be taken with pool tables - depending on database this
661 * will cost performance instead of saving)
662 if select_split ne 0 and h_subrc ne 0.
663 modify coding_tab from coding_alter index select_split.
664 select * from (t681-kotab) appending table <cond_tab>
665 up to 1 rows
666 where kappl = se_kappl
667 and kschl = se_kschl
668 and (coding_tab).
669 endif.
670 else.
671 if se_read_all_prestep is initial.
>>>>> select * from (t681-kotab) appending table <cond_tab>
673 up to 1 rows
674 where kappl = se_kappl
Regards,
Akshay
Edited by: Akshay Dalal on Jan 17, 2009 6:25 AM
Edited by: Akshay Dalal on Jan 17, 2009 6:30 AMDear Akshay,
We will NOT be able to provide you with a solution on this forum, because we have no clue what configuration do you have in your system and what user exits or other custom development may have been done in your specific system.
Lakshmipathi has already correctly pointed to a similar post. You might want to get an ABAPer to set a breakpoint just before the error occurs, then he/she might provide you with more information, which may (or may not) be helpful.
There is obviously something wrong in the pricing condition either on configuration level or in a user exit. If you write to SAP (which you should, because it's a standard program), they will ask to connect to your system, because they don't have any chrystal balls over there either.
Just in case - before going any further, try running the program RV80HGEN (in the test system, of course), which re-generates requirements and formulas. Sometimes it helps, although I doubt that it is the case here.
Also if you've used some custom (Z...) fields in the pricing configuration, that's where the problem is most likely. -
Run time error installing Premiere Pro 2.0
I am reinstalling a computer for one of my users on an XP PRo system and I get a run time error when installing Premiere PRo 2.0. I believe this happened the first time I installed as well but I can no longer get support directly from Adobe. Any help would be appreciated.
Bogus!
I'll see if I can find something on it. I recall linking to the source page in a fairly recent thread. However, as we know, some of the older post (pre-Big Bang... ) might be gone for ever. When I last posted on the RunTime.dll, I checked the links and they were still active then.
If I can find more, I'll post back.
Hunt
[Edit] Here is the LINK to that Adobe article. I am off to explore the links within.
PS I found the link within one minute of posting this. In that time, the Adobe forum logged me out. Doncha' just love the new fora?
[Edit 2] The last two links still work. Not sure about any links that those pages might contain. Number one is dead.
Maybe you are looking for
-
Is there a way to control the width of Sidebar in Finder (Leopard)?
Each time I open Finder (and there is no difference between different views - Icons, List, Column, Cover Flow!), my *Sidebar with its width takes a good 1/4 of my screen*, so I have to use mouse in order to decrease Sidebar's width!? No mattere I've
-
Are touch screen gestures supposed to be obvious?
Bought my father a new nano, loaded up some music, and I am trying to navigate. My iPod nano 2nd generation has the click wheel, so now I am trying to use the touch screen. I assumed it would be like the iPhone, iPad, iPod Touch that I am used to, bu
-
What version of itunes do i download that works with win 8 64 bit?
win 8 64 bit, what version of itunes can i download and install?
-
Oracle AP - Check Printing formats
Hi, I want to know about the different formats that Oracle supports for check printing. I am aware of the Evergrn check printing facility, but am looking for other possible ways of printing checks in pre-defined formats. Also wanted to know whether a
-
Kerberos - Multiple Domain logon using MS Acitve Directory (AS JAVA 7.0)
I tried to find document/steps to configure the UME LDAP data source in AS JAVA 7.0 to support multi-domains in a domain forest. Our multiple domains have bi-directionaly trust. Based on note 994791, the video/demo only shows you how to configure thi