Xi error MESSAGE_NOT_FOUND:

Hi Iam using a File - RFC scenario (Async- Sync without BPM) through adapter modules.We are on PI 7.0 SP14.
When the files are picked up in some cases Iam getting this error and the file is not archived...The RFC module is not called and XI throws error saying message not found.
Error: com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException
10/24/08 1:23:11 PM e8231032-729a-4daa-260b-c5516d36b875 Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MESSAGE_NOT_FOUND:
When I looked in Moni trace iam seeing an error saying message Id already exists..can any one tell me why this has happened??
When I looked at the message monitoring in RWB iam seeing a single message with CAncelled with errors status updating again and again..(Even for new set of files)??
any help is appreciated?
Larry

Hi
I think there are too many messages getting into Q. As you are not using BPM may be it is generating same ID for a message and RFC is throwing them as duplicates.
You need to generate the files in sequence. I think EOIO should help you with this as it can help generated unique ID for messages in a Q.
Check if you see anything in logs. If nothing check the LOGGING_SYNC is 1 or not in SXMB_ADM
Thanks
Gaurav

Similar Messages

BPM Scneario .. SOAP-XI-BW , Error: " MESSAGE_NOT_FOUND"

Hi all,
Webservice --> XI -->BW .
BPM has been used to send the response back.
BPM :
start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoBW)->Send(Send Response) ---> stop.
The request message processed succesfully and sent to BW system. But we are facing the problem while sending the Response back to the Webservice. The response map is done correctly but it is showing error as below and the same message is going as SOAP response.
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="PERSIST">MESSAGE_NOT_FOUND</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML message not found</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Kindly anyone please suggest what might be the problem.
Thanks
Deepthi

>start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoBW)->Send(Send Response) ---> stop.
Your first query doesnt suit my explanation, since you are using a transformation step for sending converted message (as expected by BW system) from SOAP request. Of course this is valid. the only difference is I said to use mapping outside BPM.
Send(Send Response):
before this step there should be one more transformation step
(performing a mapping the hardcoded values Status : OK
Text : Succesfully Processed.
to Webserive Response message structure).
The webservice wont consider any other message structure apart from its original response message structure.
So the flow will be like this,
start ->Receive(Request) in Open S/A mode> Transformation1(Responsemap)>Send(SendtoBW)->Transformation2(for Mapping hardcoded message structure to WebService Response Message Structure) >Send(Send Webservice Response) in Closes S/A mode-> stop.
Thanks,
- Gujjeti.
Edited by: Praveen Gujjeti on Feb 24, 2009 12:27 PM

Error MESSAGE_NOT_FOUND

Hi Guys,
We have a File to RFC synchronous scenario that used to work fine. However, currently we are getting the following error when uploading a file:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="PERSIST">MESSAGE_NOT_FOUND</SAP:Code>
<SAP:P1>(loc: WM9 ; TC: SXMSPERROR ; SM: 0 ; RR: 0 )</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML message not found</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
What is weird is that the interface sometimes works and sometimes it doesn't. We get this error in the sender file adapter and the receiver RFC adapter doesn't get invoked.

Hi ,
Please kindly re-check the following
1. Data type.
2. Message type
3.Message mapping: Update and activate
4. Interface mapping.
5. Activate the Interface mapping once again after updating it.
6. Test the scenario from ID by suppying XML payload.
7. Run an end to end testing once again.
regards
Anupam

Error: Read timed out&MESSAGE_NOT_FOUND.

Hi,
There's a synchronous scenario (File-File). A connection failure occured during a query from buisness-process (BPM). Since then an error (error message) appears constantly in Runtime Workbench-Component Monitoring-Communication Channels.
Success
RRB: entering RequestResponseBean
Success
RRB: passing through ...
Success
RRB: suspending the transaction
Success
RRB: leaving RequestResponseBean
Success
Application attempting to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.
Success
Trying to put the message into the call queue.
Success
Message successfully put into the queue.
Success
The message was successfully retrieved from the call queue.
Success
The message status set to DLNG.
Error
Received XI System Error. ErrorCode: GENERAL ErrorText: com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out ErrorStack:
Error
Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out.
Error
Transmitting the message using connection http://*****:8010/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out.
Error
The message status set to FAIL.
Error
Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out
Error
Attempt to process file failed with com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out
Error
Attempt to process file failed with com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException
File removing and the channel rebooting the channel donu2019t help.
After rebooting the channel:
Error
Received XI System Error. ErrorCode: MESSAGE_NOT_FOUND ErrorText: ErrorStack: XML message not found
Error
Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MESSAGE_NOT_FOUND:.
Error
Transmitting the message using connection http://*****:8010/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MESSAGE_NOT_FOUND:.
Error
The message status set to FAIL.
Error
Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MESSAGE_NOT_FOUND:
Error
Attempt to process file failed with com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MESSAGE_NOT_FOUND:
Error
Attempt to process file failed with com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException
Any ideas?

hi,
try this,
go to Message Monitoring in RWB, delete all the messages with status system error and onhold.
it shd solve your problem
Regards,
Sukarna.chirumamilla.

Error in Proportional Factor Calculation Program

Hi ,
I have developed an ABAP Program to calculate Proportional Factor(PF) as below.
Generally,to calculate the PF for a period , we need to use transaction /sapapo/sdp94 to create a profile .After doing that , to calculate PF we need to go transaction /sapapo/mv8v .
Now,the given program has three options :-
1)Create : To create the selection-ID by taking areabasepackRS as name of the selection-ID . Here we need to give the excel sheet that is used to load data into /sapapo/mc8v to calculate PF.
2)Calculate PF : This option is used to calculate proportional factor.
 Now if we try to calculate PF ,I get an error message saying there are no
 plannable characteristic combinations .
3) Delete : This option is used to delete the selection profile.
I am getting an error in this program which I have explained with the document attached in this mail .
Please could anyone help me out with this .
The program is as below:-
report ZRSNORMS_PPF
 no standard page heading line-size 255.
*include bdcrecx1.
INCLUDE ZAPO_DATA_DECLARATION_PPF.
INCLUDE Z_APO_FORMS_PPF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 program_name = syst-repid
DYNPRO_NUMBER = SYST-DYNNR
 field_name = p_file1
STATIC = ' '
MASK = ' '
 CHANGING
 file_name = p_file1
EXCEPTIONS
MASK_TOO_LONG = 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.
start-of-selection.
PERFORM READ_DATA TABLES I_PROFILE
 I_EXEL
 IT_PROFILE_NAME
 USING P_FILE1
 CHANGING W_SUBRC.
PERFORM SAVE_SELECTION TABLES I_EXEL
 IT_SAVE_SEL
 IT_PROFILE_NAME.
IT_GRP-OBJNAM = 'ZRSBASPCK'.
APPEND IT_GRP.
LOOP AT IT_GRP INTO W_GROUP.
 APPEND W_GROUP TO IT_GROUP.
ENDLOOP.
G_PAREAID = 'ZRSPAHPC'.
G_MVIEW = 'ZRSPAHPC'.
G_COUNT = 0.
IF CREATE = 'X'.
LOOP AT IT_SAVE_SEL INTO W_SEL_SAVE.
 IF W_SEL_SAVE-IOBJNM = '9AVERSION' AND SY-TABIX > 1.
 G_COUNT = G_COUNT + 1.
 READ TABLE IT_PROFILE_NAME INDEX G_COUNT.
 G_NAME = IT_PROFILE_NAME-F_NAME.
 CALL FUNCTION '/SAPAPO/MCPSH_SELECTION_SAVE'
 EXPORTING
IV_SELID =
IV_FLG_USED_FOR =
 IV_PAREAID = G_PAREAID
 IV_MVIEW = G_MVIEW
 IV_SEL_DESCRIPTION = G_NAME
 IT_SELECTION = IT_SEL_SAVE
IT_OBJECTS =
 IT_SEL_GROUP = IT_GROUP
IV_POPUP_SEL_DESCRIPTION =
IMPORTING
EV_SELID =
EV_SEL_DESCRIPTION =
EXCEPTIONS
DUPLICATE_SELECTION = 1
MULTIPLE_SELECTION = 2
INCONSISTENT_DATABASE = 3
DUPLICATE_DESCRIPTION = 4
INVALID_DESCRIPTION = 5
NO_PERMISSION = 6
SELID_INVALID = 7
OTHERS = 8
 IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 CLEAR IT_SEL_SAVE[].
 APPEND W_SEL_SAVE TO IT_SEL_SAVE.
 ELSEIF W_SEL_SAVE-IOBJNM = '9AVERSION' AND SY-TABIX = 1.
 APPEND W_SEL_SAVE TO IT_SEL_SAVE.
 ELSE.
 APPEND W_SEL_SAVE TO IT_SEL_SAVE.
 ENDIF.
ENDLOOP.
G_COUNT = G_COUNT + 1.
READ TABLE IT_PROFILE_NAME INDEX G_COUNT.
G_NAME = IT_PROFILE_NAME-F_NAME.
CALL FUNCTION '/SAPAPO/MCPSH_SELECTION_SAVE'
 EXPORTING
IV_SELID =
IV_FLG_USED_FOR =
 IV_PAREAID = G_PAREAID
 IV_MVIEW = G_MVIEW
 IV_SEL_DESCRIPTION = G_NAME
 IT_SELECTION = IT_SEL_SAVE
IT_OBJECTS =
 IT_SEL_GROUP = IT_GROUP
IV_POPUP_SEL_DESCRIPTION =
IMPORTING
EV_SELID =
EV_SEL_DESCRIPTION =
EXCEPTIONS
DUPLICATE_SELECTION = 1
MULTIPLE_SELECTION = 2
INCONSISTENT_DATABASE = 3
DUPLICATE_DESCRIPTION = 4
INVALID_DESCRIPTION = 5
NO_PERMISSION = 6
SELID_INVALID = 7
OTHERS = 8
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IV_GROUP = 'ZRSBASPCK'.
LOOP AT IT_SEL_SAVE INTO w_confirm_sel.
 APPEND w_confirm_sel TO it_confirm_sel.
ENDLOOP.
CALL FUNCTION '/SAPAPO/MSDP_SH_OBJ_LIST_BUILD'
 EXPORTING
 IV_PAREAID = G_PAREAID
 IV_MVIEW = G_MVIEW
 IV_DVIEW =
 IV_FROMDATE =
 IV_ENDDATE =
 IV_NO_POPUPS =
IMPORTING
 ET_SH_OBJECTS =
EXCEPTIONS
 INVALID_INPUT = 1
 INTERNAL_ERROR = 2
 OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CLEAR IT_SEL_SAVE[].
ENDIF.
if calc_ppf = 'X'.
PERFORM CALC_PPF TABLES I_EXEL
 BDCTAB
 IT_PROFILE_NAME.
ENDIF.
if del_prof = 'X'.
LOOP AT I_EXEL.
concatenate i_exel-area I_EXEL-BASE INTO DEL_NAME.
SELECT SINGLE * FROM /SAPAPO/TS_SELKO INTO IT_TS_SELKO
WHERE SEL_DESRCIPTION = DEL_NAME.
DEL_PROFILE = IT_TS_SELKO-SELECTIONID.
CALL FUNCTION '/SAPAPO/MCPSH_SELECTION_DELETE'
EXPORTING
 IV_SELID = DEL_PROFILE
IV_FLG_CONFIRM_TRANS = 'X'
EXCEPTIONS
NO_ENTRY = 1
NO_AUTHORITY = 2
DELETION_NOT_POSSIBLE = 3
OTHERS = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDLOOP.
ENDIF.
INCLUDE ZAPO_DATA_DECLARATION_PPF .
types: t_ts_selpo type /sapapo/ts_selpo.
TYPES: BEGIN OF T_EXEL,
 PROF_DATFRM TYPE DATS,
 PROF_DATTO TYPE DATS,
 FORCAST_FROM TYPE DATS,
 FORCAST_TO TYPE DATS,
 AREA(60),
 BASE(60),
 POPID(60),
 RATING(60),
 RS(60),
 END OF T_EXEL.
types: begin of t_profile,
 obj(30),
 val(60),
 end of t_profile.
TYPES: begin of t_profile_name,
 f_name(60),
 end of t_profile_name.
DATA: G_COUNT TYPE I VALUE 0.
*TYPES: T_SAVE_SEL LIKE IT_SELECTION.
data: w_subrc TYPE sy-subrc,
 I_TS_SELPO TYPE Table of t_ts_selpo with header line,
 I_EXEL TYPE Table of t_EXEL with header line.
DATA: IV_GROUP TYPE /SAPAPO/IOBJNM.
DATA: IT_PROFILE_NAME TYPE TABLE OF T_PROFILE_NAME WITH HEADER LINE.
data: i_profile type table of t_profile with header line.
*/sapapo/ts_iobj_selection_tab.
data: IT_SEL_SAVE TYPE /sapapo/ts_iobj_selection_tab,
 w_SEL_SAVE type /SAPAPO/TS_IOBJ_SELECTION.
DATA: IT_CONFIRM_SEL TYPE /SAPAPO/SH_SEL_RANGE_TAB,
 W_CONFIRM_SEL TYPE /SAPAPO/SH_SEL_RANGE_STR.
TYPES: BEGIN OF T_SAVE_SEL,
 IOBJNM(30),
 SIGN,
 OPTION(2),
 LOW(60),
 HIGH(60),
 END OF T_SAVE_SEL.
DATA: IT_SAVE_SEL TYPE TABLE OF T_SAVE_SEL WITH HEADER LINE.
TYPES: BEGIN OF T_GRP,
 OBJNAM(30),
 END OF T_GRP.
DATA: IT_GRP TYPE TABLE OF T_GRP WITH HEADER LINE.
DATA DECLARATION FOR FUNC MODULE **************
DATA: IT_GROUP TYPE /SAPAPO/TS_GROUP_BY_TAB,
 W_GROUP TYPE /SAPAPO/TS_GROUP_BY_STR.
DATA: G_PAREAID TYPE /SAPAPO/TS_PAREAID,
 G_MVIEW TYPE /SAPAPO/PB_MVIEW,
 G_NAME TYPE /SAPAPO/TS_SEL_DESCR.
BDC TABLES ***************************
DATA: bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
DATA: it_messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
DATA : BDCTAB like BDCDATA occurs 0 with header line.
DATA : w_file type string.
****************BDC ERROR TAB ***************************
DATA : xcount1 TYPE i,
 xstat TYPE i,
 xmsgv1 LIKE balm-msgv1,
 xmsgv2 LIKE balm-msgv2,
 xmsgv3 LIKE balm-msgv3,
 xmsgv4 LIKE balm-msgv4,
 xmessage(80) TYPE c.
DATA : BEGIN OF t_errlog OCCURS 0,
 sno TYPE i,
 message(80) TYPE c,
 END OF t_errlog.
DATA: DEL_PROFILE TYPE /SAPAPO/SELECTIONID2,
 DEL_NAME(60).
************DUPLICATE NAME TAB **************************
DATA: IT_NOT_PROCESSED TYPE TABLE OF /SAPAPO/TS_SELPO WITH HEADER LINE.
DELETE TAB *****************************
DATA: IT_TS_SELKO TYPE TABLE OF /SAPAPO/TS_SELKO WITH HEADER LINE.
SELECTION-SCREEN : BEGIN OF BLOCK b1.
parameters: p_file1 TYPE rlgrap-filename.
parameters: create type c radiobutton group g1,
 calc_ppf type c radiobutton group g1,
 del_prof type c radiobutton group g1.
SELECTION-SCREEN END OF BLOCK b1.
Include Z_APO_FORMS_PPF
*& Include Z_APO_FORMS_PPF
*& Form READ_DATA
 text
 -->P_I_PROFILE text
 -->P_I_EXEL text
 -->P_IT_PROFILE_NAME text
 -->P_P_FILE1 text
 <--P_W_SUBRC text
FORM READ_DATA TABLES P_I_PROFILE STRUCTURE I_PROFILE
 P_I_EXEL STRUCTURE I_EXEL
 P_IT_PROFILE_NAME STRUCTURE IT_PROFILE_NAME
 USING P_P_FILE1
 CHANGING P_W_SUBRC.
DATA : iexcel LIKE zexcel_read OCCURS 0 WITH HEADER LINE,
 G_DATE TYPE DATS.
data: l_name(60).
CLEAR p_w_subrc.
CALL FUNCTION 'ZALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 filename = p_p_file1
 i_begin_col = 1
 i_begin_row = 1
 i_end_col = 62
 i_end_row = 50000
 TABLES
 intern = iexcel.
 EXCEPTIONS
 inconsistent_parameters = 1
 upload_ole = 2
 OTHERS = 3.
IF sy-subrc <> 0.
 p_w_subrc = 0 .
endif.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
LOOP AT iexcel WHERE row > 1.
 IF iexcel-col = '0001'.
 PERFORM CONVERT_DATE CHANGING G_DATE iexcel-value.
 p_i_EXEL-PROF_DATFRM = G_DATE.
 ENDIF.
 IF iexcel-col = '0002'.
 PERFORM CONVERT_DATE CHANGING G_DATE iexcel-value.
 p_i_EXEL-PROF_DATTO = G_DATE.
 ENDIF.
 IF iexcel-col = '0003'.
 PERFORM CONVERT_DATE CHANGING G_DATE iexcel-value.
 p_i_EXEL-FORCAST_FROM = G_DATE.
 ENDIF.
 IF iexcel-col = '0004'.
 PERFORM CONVERT_DATE CHANGING G_DATE iexcel-value.
 p_i_EXEL-FORCAST_TO = G_DATE.
 ENDIF.
 IF iexcel-col = '0005'.
 p_i_EXEL-AREA = iexcel-value.
 p_i_profile-obj = 'ZRSAREA'.
 p_i_profile-VAL = iexcel-value.
 append p_i_PROFILE.
 clear p_i_PROFILE.
 ENDIF.
 IF iexcel-col = '0006'.
 p_i_EXEL-BASE = iexcel-value.
 p_i_profile-obj = 'ZRSBASPCK'.
 p_i_profile-VAL = iexcel-value.
 append p_i_PROFILE.
 clear p_i_PROFILE.
 ENDIF.
 IF iexcel-col = '0007'.
 p_i_EXEL-POPID = iexcel-value.
 p_i_profile-obj = 'ZRSPOPULN'.
 p_i_profile-VAL = iexcel-value.
 append p_i_PROFILE.
 clear p_i_PROFILE.
 ENDIF.
 IF iexcel-col = '0008'.
 p_i_EXEL-RATING = iexcel-value.
 ENDIF.
 IF iexcel-col = '0009'.
 p_i_EXEL-RS = iexcel-value.
 p_i_profile-obj = 'ZRSCUSTMR'.
 p_i_profile-VAL = iexcel-value.
 append p_i_PROFILE.
 clear p_i_PROFILE.
 ENDIF.
 at end of row.
 append p_i_EXEL.
 clear p_i_EXEL.
 endat.
endloop.
loop at P_I_EXEL.
concatenate P_I_EXEL-AREA P_I_EXEL-BASE INTO L_NAME.
P_it_profile_name-f_name = l_name.
append P_it_profile_name.
ENDLOOP.
ENDFORM. " READ_DATA
*& Form CONVERT_DATE
 text
 <--P_G_DATE text
 <--P_IEXCEL_VALUE text
FORM CONVERT_DATE CHANGING P_G_DATE
 P_IEXCEL_VALUE.
 CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
EXPORTING
 DATE_EXTERNAL = p_iexcel_value
ACCEPT_INITIAL_DATE =
IMPORTING
 DATE_INTERNAL = p_g_date
EXCEPTIONS
DATE_EXTERNAL_IS_INVALID = 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. " CONVERT_DATE
*& Form SAVE_SELECTION
 text
 -->P_I_EXEL text
 -->P_IT_SAVE_SEL text
 -->P_IT_PROFILE_NAME text
FORM SAVE_SELECTION TABLES P_I_EXEL STRUCTURE I_EXEL
 P_IT_SAVE_SEL STRUCTURE IT_SAVE_SEL
 P_IT_PROFILE_NAME STRUCTURE IT_PROFILE_NAME.
DATA: L_PAREAID(40).
loop at p_i_exel.
p_it_save_sel-iobjnm = '9AVERSION'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = '000'.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
p_it_save_sel-iobjnm = 'ZRSAREA'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = P_I_EXEL-AREA.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
IF NOT P_I_EXEL-BASE IS INITIAL.
p_it_save_sel-iobjnm = 'ZRSBASPCK'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = P_I_EXEL-BASE.
ENDIF.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
IF NOT P_I_EXEL-POPID IS INITIAL.
p_it_save_sel-iobjnm = 'ZRSPOPULN'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = P_I_EXEL-POPID.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
ENDIF.
IF NOT P_I_EXEL-RS IS INITIAL.
p_it_save_sel-iobjnm = 'ZRSCUSTMR'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = P_I_EXEL-RS.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
ENDIF.
write 'hi'.
*CLEAR P_IT_SAVE_SEL[].
ENDLOOP.
*submit
ENDFORM. " SAVE_SELECTION
*& Form CALC_PPF
 text
 -->P_I_EXEL text
 -->P_BDCTAB text
 -->P_IT_PROFILE_NAME text
FORM CALC_PPF TABLES P_I_EXEL STRUCTURE I_EXEL
 P_BDCTAB STRUCTURE BDCTAB
 P_IT_PROFILE_NAME STRUCTURE IT_PROFILE_NAME.
DATA: PERIOD_FROM TYPE /SAPAPO/BASIS_VON_BIS,
 PERIOD_TO TYPE /SAPAPO/BASIS_VON_BIS,
 TRANSFER_FORM TYPE /SAPAPO/TARGET_VON_BIS,
 TRANSFER_TO TYPE /SAPAPO/TARGET_VON_BIS,
 SEL_PROFILE TYPE /SAPAPO/SEL_TXT.
DATA: SEL_NAME(60).
DATA : L_TEMP TYPE SY-DATUM,
 L_TEMP1 TYPE SY-DATUM,
 L_TEMP2 TYPE SY-DATUM,
 L_TEMP3 TYPE SY-DATUM.
LOOP AT P_I_EXEL.
L_TEMP0(2) = P_I_EXEL-FORCAST_FROM6(2). "passed date
L_TEMP2(2) = P_I_EXEL-FORCAST_FROM4(2). "passed Month
L_TEMP4(4) = P_I_EXEL-FORCAST_FROM0(4). "passed year
L_TEMP10(2) = P_I_EXEL-FORCAST_TO6(2). "passed date
L_TEMP12(2) = P_I_EXEL-FORCAST_TO4(2). "passed Month
L_TEMP14(4) = P_I_EXEL-FORCAST_TO0(4). "passed year
L_TEMP20(2) = P_I_EXEL-PROF_DATFRM6(2). "passed date
L_TEMP22(2) = P_I_EXEL-PROF_DATFRM4(2). "passed Month
L_TEMP24(4) = P_I_EXEL-PROF_DATFRM0(4). "passed year
L_TEMP30(2) = P_I_EXEL-PROF_DATTO6(2). "passed date
L_TEMP32(2) = P_I_EXEL-PROF_DATTO4(2). "passed Month
L_TEMP34(4) = P_I_EXEL-PROF_DATTO0(4). "passed year
PERIOD_FROM = L_TEMP2.
PERIOD_TO = L_TEMP3.
transfer_form = L_TEMP.
TRANSFER_TO = L_TEMP1.
concatenate P_I_EXEL-AREA P_I_EXEL-BASE INTO SEL_NAME.
SEL_PROFILE = SEL_NAME.
perform bdc_dynpro using '/SAPAPO/RMDP_SHARE_VERSION_M' '1000'.
perform bdc_field using 'BDC_CURSOR'
 'BPAREAID'.
perform bdc_field using 'BDC_OKCODE'
 '=ONLI'.
perform bdc_field using 'PAREAID'
 'ZRSPAHPC'.
perform bdc_field using 'FLG_AREA'
 'X'.
perform bdc_field using 'BPAREAID'
 'ZRSPAHPC'.
perform bdc_dynpro using '/SAPAPO/RMDP_SHARE_MANAGER' '1000'.
perform bdc_field using 'BDC_OKCODE'
 '=UCOMM1'.
perform bdc_field using 'BDC_CURSOR'
 'Z_DATE-HIGH'.
perform bdc_field using 'B_VER'
 '000'.
perform bdc_field using 'B_KENN'
 '9AVCORHIST'.
perform bdc_field using 'B_DATE-LOW'
 PERIOD_FROM.
perform bdc_field using 'B_DATE-HIGH'
 PERIOD_TO.
perform bdc_field using 'VERSION'
 '000'.
perform bdc_field using 'Z_DATE-LOW'
 transfer_form.
perform bdc_field using 'Z_DATE-HIGH'
 TRANSFER_TO.
perform bdc_field using 'FLG_ONE'
 'X'.
perform bdc_dynpro using '/SAPAPO/RMDP_SHARE_MANAGER' '1000'.
perform bdc_field using 'BDC_OKCODE'
 '=ONLI'.
perform bdc_field using 'BDC_CURSOR'
 'SEL_TXT'.
perform bdc_field using 'SEL_TXT'
 SEL_PROFILE.
perform bdc_dynpro using '/SAPAPO/RMDP_SHARE_MANAGER' '1000'.
perform bdc_field using 'BDC_OKCODE'
 '/EE'.
perform bdc_dynpro using '/SAPAPO/RMDP_SHARE_VERSION_M' '1000'.
perform bdc_field using 'BDC_OKCODE'
 '=ONLI'.
perform bdc_field using 'BDC_OKCODE'
 '/EE'.
perform bdc_field using 'BDC_CURSOR'
 'PAREAID'.
*perform bdc_transaction using '/SAPAPO/MC8V'.
SELECT SINGLE * FROM /SAPAPO/TS_SELKO INTO IT_TS_SELKO
WHERE SEL_DESRCIPTION = sel_NAME.
if sy-subrc = 0.
call transaction '/SAPAPO/MC8V'
 using bdctab
 mode 'A'
 update 'L'
 messages into it_messtab.
describe table it_messtab lines xcount1.
read table it_messtab index xcount1.
LOOP AT it_messtab WHERE msgtyp = 'E'
 OR msgtyp = 'A'.
 MOVE It_messtab-msgv1 TO xmsgv1.
 MOVE It_messtab-msgv2 TO xmsgv2.
 MOVE It_messtab-msgv3 TO xmsgv3.
 MOVE It_messtab-msgv4 TO xmsgv4.
 CALL FUNCTION 'MESSAGE_PREPARE'
 EXPORTING
 LANGUAGE = sy-langu
 msg_id = It_messtab-msgid
 msg_no = It_messtab-msgnr
 MSG_VAR1 = xmsgv1
 MSG_VAR2 = xmsgv2
 MSG_VAR3 = xmsgv3
 MSG_VAR4 = xmsgv4
 IMPORTING
 MSG_TEXT = xmessage
 EXCEPTIONS
 FUNCTION_NOT_COMPLETED = 1
 MESSAGE_NOT_FOUND = 2
 OTHERS = 3
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 MOVE sy-tabix TO t_errlog-sno.
 MOVE xmessage TO t_errlog-message.
 APPEND t_errlog.
 CLEAR t_errlog..
 ENDLOOP.
CLEAR BDCTAB[].
CLEAR SEL_NAME.
CLEAR P_I_EXEL.
endif.
ENDLOOP.
ENDFORM. " CALC_PPF
*& Form bdc_dynpro
 text
 -->P_0424 text
 -->P_0425 text
FORM bdc_dynpro USING PROGRAM DYNPRO.
CLEAR bdcTAB.
bdcTAB-program = program.
bdcTAB-dynpro = dynpro.
bdcTAB-dynbegin = 'X'.
APPEND bdcTAB.
ENDFORM. " bdc_dynpro
*& Form bdc_field
 text
 -->P_0494 text
 -->P_TRANSFER_FROM text
FORM bdc_field USING FNAM FVAL.
CLEAR bdcTAB.
bdcTAB-fnam = fnam.
bdcTAB-fval = fval.
APPEND bdcTAB.
ENDFORM. " bdc_field

Hi,
As I have not been able to attach the document, I will explain the problem in full as below:-
Business scenario - Consider a factory having 5 different customers (which is known as Customer_rs). We need to supply stock to each of them based on their past consumption. So to forecast this, we calculate a factor known as proportional factor based on the data we have for previous months.
So to calculate the PF for a period, we need to create a profile in /sapapo/sdp94 .
After creating the profile, the profile can be seen by clicking on SPD94 and going to selection-screen button .
Then to calculate PF , we need to go to transaction /sapapo/mv8v .
Here we will have to give the selection id that was saved in SDP94.
All this process has to be automated and a program has been created to do this.
A description of how the program works is as given below.
When we try to calculate the proportional factor with this program , the following error is obtained :-
There are no plannable characteristic combinations.
We are passing the same parameters that were passed by the SDP94 transaction to the standard function module for saving the selection ids. This is shown in the below screenshots.
In spite of this we are getting the error.
Now to delete the selection ids,click on delete option in the program .
But the problem is even if we click on delete , the PPF data will be stored in the database inspite of deleting the selection profiles .
Please can anyone help me out with this .
Regards,
Sushanth H.S.
 Now we will have to give the selection description
Now the profile can be seen by going to SDP94 and clicking on selection profile button.
Now to calculate PF, go to transaction /sapapo/mv8v
Click on execute and give following inputs
This will forecast the PF for the period 01.09.2007 to 21.02.2007 based on data from 21.04.2007 to 20.05.2007
Click on other settings
Here we will have to give the selection id that was saved in SDP94.
Click on execute.
All this process has to be automated and a program was created to do this.
A description of how the program is given below.
Program zrsnorms_ppf
Execute.
Give file path of excel sheet.
Execute.
This will create the selection id by taking areabasepackRS as name of id.
This is the excel sheet that is used to load data into /sapapo/mc8v to calculate the PF.
Upon executing, the ids have been created
The new selection ids can be seen by going to /sapapo/sdp94
And clicking on selection profile.
Parameters passed to standard function module in order to save the selection id.
Now if we try to calculate PF using the program, the following happens
When executed,
BDC is called to input data to transaction /sapapo/mc8v to calculate ppf.
An error screen is generated with the message There are no plannable characteristic combinations.
We are passing the same parameters that were passed by the SDP94 transaction to the standard function module for saving the selection ids. This is shown in the below screenshots.
In spite of this we are getting the error.
When IV_POPUP_SEL_DESCRIPTION is passed, a popup will be displayed where the selection description will have to be entered. I am passing the same selection description here as is picked by the program.( H3HPCDEL00110096, H3HPCDEL00110063)
To avoid this, we need to go to SDP94 and after going to selection window, we need to save the selections as shown in the following screenshots.
Select the selection id one by one.
Click on save selection
Click on save.
Do the same for all ids created by the program.
Now if we try to calculate the PF using the program, it is seen to work
So what needs to be done is that we need to avoid going to SDP94 in order to save the selections after the ids are created by the program.
How the Program works
Se38
Program zrsnorms_ppf
Execute.
Give file path of excel sheet.
Execute.
This will create the selection id by taking areabasepackRS as name of id.
The new selection ids can be seen by going to /sapapo/sdp94
And clicking on selection profile.
Now the selection has to be saved. For that, follow the following procedure.
Click on selection window.
Click on load selection.
Select the ids.
Select and then press save.
Do the same for every id.
Only then can proportional factor be calculated.
Now go to program and select Calc_ppf, with filepath to excel sheet as the sel_ids will be pulled from the excel.
When executed,
BDC is called to input data to transaction /sapapo/mc8v to calculate ppf.
Now go to sdp94 and load the selection
Click on load data.
And make sure, data view is TDP_VIEW_PROP as shown
PPF will be shown for the period chosen in the excel sheet.
Now to delete the selection ids.
Go to the program and give file path of the excel sheet and execute.
The selection profiles will be deleted as shown.
But PPF data will be stored in the database inspite of deleting the selection profiles. And ppf can be shown by selecting the basepack and the sales area.
Click load data.
Business scenario - Consider a factory having 5 different customers (which is known as Customer_rs). We need to supply stock to each of them based on their past consumption. So to forecast this, we calculate a factor known as proportional factor based on the data we have for previous months.
So to calculate the PF for a period, we need to create a profile in /sapapo/sdp94
How it is done in standard transaction /SAPAPO/SDP94
Important pushbuttons and their functions
Click on selection window.
Give the selections
Click on save selection
A break-point has been set in the standard program to show what all parameters are being passed to the standard function module /SAPAPO/MCPSH_SELECTION_SAVE used to save the selection
Now we will have to give the selection description
Now the profile can be seen by going to SDP94 and clicking on selection profile button.
Now to calculate PF, go to transaction /sapapo/mv8v
Click on execute and give following inputs
This will forecast the PF for the period 01.09.2007 to 21.02.2007 based on data from 21.04.2007 to 20.05.2007
Click on other settings
Here we will have to give the selection id that was saved in SDP94.
Click on execute.
All this process has to be automated and a program was created to do this.
A description of how the program is given below.
Program zrsnorms_ppf
Execute.
Give file path of excel sheet.
Execute.
This will create the selection id by taking areabasepackRS as name of id.
This is the excel sheet that is used to load data into /sapapo/mc8v to calculate the PF.
Upon executing, the ids have been created
The new selection ids can be seen by going to /sapapo/sdp94
And clicking on selection profile.
Parameters passed to standard function module in order to save the selection id.
Now if we try to calculate PF using the program, the following happens
When executed,
BDC is called to input data to transaction /sapapo/mc8v to calculate ppf.
An error screen is generated with the message There are no plannable characteristic combinations.
We are passing the same parameters that were passed by the SDP94 transaction to the standard function module for saving the selection ids. This is shown in the below screenshots.
In spite of this we are getting the error.
When IV_POPUP_SEL_DESCRIPTION is passed, a popup will be displayed where the selection description will have to be entered. I am passing the same selection description here as is picked by the program.( H3HPCDEL00110096, H3HPCDEL00110063)
To avoid this, we need to go to SDP94 and after going to selection window, we need to save the selections as shown in the following screenshots.
Select the selection id one by one.
Click on save selection
Click on save.
Do the same for all ids created by the program.
Now if we try to calculate the PF using the program, it is seen to work
So what needs to be done is that we need to avoid going to SDP94 in order to save the selections after the ids are created by the program.
How the Program works
Se38
Program zrsnorms_ppf
Execute.
Give file path of excel sheet.
Execute.
This will create the selection id by taking areabasepackRS as name of id.
The new selection ids can be seen by going to /sapapo/sdp94
And clicking on selection profile.
Now the selection has to be saved. For that, follow the following procedure.
Click on selection window.
Click on load selection.
Select the ids.
Select and then press save.
Do the same for every id.
Only then can proportional factor be calculated.
Now go to program and select Calc_ppf, with filepath to excel sheet as the sel_ids will be pulled from the excel.
When executed,
BDC is called to input data to transaction /sapapo/mc8v to calculate ppf.
Now go to sdp94 and load the selection
Click on load data.
And make sure, data view is TDP_VIEW_PROP as shown
PPF will be shown for the period chosen in the excel sheet.
Now to delete the selection ids.
Go to the program and give file path of the excel sheet and execute.
The selection profiles will be deleted as shown.
But PPF data will be stored in the database inspite of deleting the selection profiles. And ppf can be shown by selecting the basepack and the sales area.
Click load data.

Communication chaneel error

Hi Experts,
My scenario is FileRFCFile Syncrinous. All the files being picked up from output tray by the Sender file CC.
and because of one error file suddenly Sender File CC is not picking remaining all the files in the tray. even after deleting the error file and after stopping and starting the Sender File CC, the new files came in the tray are not getting picked up.
kindly advice me how to resolve the issue.
Thanks,
Siva

Hi Abhijit,
Thanks for your reply,
The Error in auditlog is as ErrorCode: MESSAGE_NOT_FOUND
and Error Category : XI_J2EE_ADAPTER_XI_HANDLER
and Error code : CALL_CONSUMER_ERROR
Earlier somany times i got the same issue and by deleting the error file and restarting the Sender file CC by start and stop, the files has been picked up. But now the file adapter not picking the new files and it is persisting the old messsage id only which was for the error file.
Thanlks,
Siva

PI File Adapter Error.

Hi all,
I am facing one issue in the Production environment.My PI scenario is File to SAP R/3.At the source side file is being kept in one of the shared folder and PI file adapter is picking the file.When network goes down in the middle of processing a file form this shared folder PI file adpater is throwing some error as given below:
"Bean SMPP_CALL_JAVA_RUNTIME3not found on host XXX, ProgId =AI_RUNTIME_PRD"
Even though the network comes up after sometime we are getting the error as
"PERSIST">MESSAGE_NOT_FOUND"
If we try to reprocess the files it keeps on throwing the error until we remove the corresponding file (whose processing got interrupted) and refresh the cache.Once the corresponding file is removed PI will start processing the remaining files but the moment we keep the file which got stuck in PI it throws the error again "PERSIST">MESSAGE_NOT_FOUND".
Could someone throw some light on this as i have to remove the file from the source location everytime and reprocess it by renaming the file.
Thanks,
Lekshmi.

Hi all,
I have gone through the SAP note mentioned by Abhishek.Thanks for that,it will solve my issue.
But i want to clear my doubt regarding this error message.Whenever there is some network problem i.e. when the adapter fails to contact target system it gives some delievery exception and finally MESSAGE_NOT_FOUND.The same message can be found in the source location when this error is thrown in PI.Could someone provide any link which will explain why PI is throwing such error.I mean why is it unable to find an existing message in the source location???
In my case whenever it happens i will be informed by the source team that they are not receiving any response(so for the time being i can manage without configuring the alerts as it is not a frequent issue).But i wanted to know what is the root cause for this issue.
Regards,
Lekshmi.

URGENT: system error - Maual restart possible

Hi Experts,
I'm facing a problem in Xi prodoction. Both inbound and outbound are throwing system error - Maual restart possible. The user is restarting manually in order to post the invoice.
Basically this is retail project, from POS s/w to Xi to SAP R/3. The scenario is file to idoc(inbound) and idoc to file (outbound).
The error is :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="PERSIST">MESSAGE_NOT_FOUND</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML message not found</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The acknowledgement error is :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have gone throw the sdn post and blogs but i'm uable to trace the problem.
Kindly suggest me ASAP as this is business critical and posting have been stoped.
Regards,
Pawan

Hi,
Please find the interface determination trace. Hope this will help you to provide some suggestion.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: XIBGUSER</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="2" type="T">Tunneling needed?</Trace>
<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
<Trace level="3" type="T">Sender Interface</Trace>
<Trace level="3" type="T">WP_PLU.WP_PLU03 urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPRT2</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
<Trace level="2" type="T">Port : SAPRT2</Trace>
<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">RFCDest :</Trace>
<Trace level="2" type="T">Release : 700</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Direct : 1</Trace>
<Trace level="2" type="T">SAPREL : 700</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
<Trace level="2" type="T">Port : SAPRT2</Trace>
<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">Create XML-Control Record</Trace>
<Trace level="2" type="T">Create XML-Data Records</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
</Trace>
<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
<Trace level="2" type="T">Set Sender Routing-object</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<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="3" type="T">system-ID = XIP</Trace>
<Trace level="3" type="T">client = 600</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIBGUSER</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:02Z UTC-7</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 = DCFBC7EA238100F1B64A00145EDC94EF</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="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
<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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface WP_PLU.WP_PLU03*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<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="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XIP</Trace>
<Trace level="3" type="T">client = 600</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIBGUSER</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7</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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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 level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - e_solutionsPOS</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 2</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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 level="2" type="T">Check conditions for (Inb: Party Srvc If) e_solutionsPOS WP_PLU.WP_PLU03</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: WP_PLU.WP_PLU03</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Thanks,
Pavan

Whenever messages created in XI, initially it will go to error status

Whenever messages created in XI, initially it will go to error status
As soon as IDOCs released in ECC system the messages are going to error status. But they are processing successfully later. They are going to error state as soon a they release. Thats the problem.
Information message "XML message not found". But I am able to see XML message in payload. When I try to reprocess the message it will succeed. It is happening for all the interfaces.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="PERSIST">MESSAGE_NOT_FOUND</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML message not found</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please provide any help.

Hi !
It seems that the message type / interface message defined in interface determination does not match with one in the message. Are you using the imported IDOC as interface message or did you create a new interface mapping? you should use the imported IDOC in interface mapping and also in interface determination objects. Also try to reactivate the interface determination object.
Regards,
Matias.

MESSAGE_NOT_FOUND

Hi Guys,
In my file to proxy sync scenario, i am getting the following error.
Message_Not_Found
XML message not found.
when i look into RWB, in the Inbound Message, there is no payload available.
Is there anyway to check this?
Experts pls guide me.
Regards
Bala.

Hi Hemant,
Thanks for the response.
I have checked RWB, it is showing error "Canceled with Errors"
Even when i check in SXMB_MONI, there is no payload in the inbound message.
can you tell me is there any other way to check this?
Regards
Bala.

How do i get data when displaying error message in BDC

hi,
I have generated one internal table for displaying error message using BDCMSGCOLL, i want the the error to display according to the field name,
Hw can i get it...
ex: <Material name> Error message as name already created or unit doesnt exit...
Pls reply,
Regards,
Divi.

Hi Divya,
Try the below
CALL TRANSACTION 'MM01'
 USING bdcdata
 MODE 'N'
 MESSAGES INTO MSGTAB.
IF SY-SUBRC NE 0.
move itab-matnr to jtab-matnr.
append jtab.
PERFORM CHECK.
ENDIF.
FORM CHECK.
LOOP AT MSGTAB where msgtyp = 'E'.
read table jtab index sy-index.
write:/ jtab-matnr.
CALL FUNCTION 'MESSAGE_PREPARE'
EXPORTING
 LANGUAGE = sy-langu
 MSG_ID = MSGTAB-MSGID
 MSG_NO = MSGTAB-MSGNR
 MSG_VAR1 = MSGTAB-MSGV1(50)
 MSG_VAR2 = MSGTAB-MSGV2(50)
 MSG_VAR3 = MSGTAB-MSGV3(50)
 MSG_VAR4 = MSGTAB-MSGV4(50)
 IMPORTING
 MSG_TEXT = L_MSG
EXCEPTIONS
 FUNCTION_NOT_COMPLETED = 1
 MESSAGE_NOT_FOUND = 2
 OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
WRITE: L_MSG.
ENDLOOP.
ENDFORM.
- Satish

Errors in BDC

Hi,
what are the errors we get normally while working with BDC. how do we handle them.
regards,
vijay.

Hi vijay,
The errors you get depends upon the transaction you are
running.
 This is how you handle:
Let's consider you are recording for the transction CJ40
(Messages table declaration )
DATA :BEGIN of t_msg occurs 0.
 include structure BDCMSGCOLL.
DATA END of t_msg.
Handling it :
CALL TRANSACTION 'CJ40' using T_BDCDATA MODE 'N' UPDATE 'S' MESSAGES INTO t_msg.
commit work.
If you want to display the errors in the screen you can use a function module named 'RPY_MESSAGE_COMPOSE'
This gives you the corresponding message for the message number that you input.
Below is the sample code
Loop at t_msg. " Messages internal table
 w_msgid = t_msg-msgid.
 w_msgno = t_msg-msgnr.
 w_msgv1 = t_msg-msgv1.
 w_msgv2 = t_msg-msgv2.
 w_msgv3 = t_msg-msgv3.
 w_msgv4 = t_msg-msgv4.
 CALL FUNCTION 'RPY_MESSAGE_COMPOSE'
 EXPORTING
 LANGUAGE = SY-LANGU
 MESSAGE_ID = w_msgid
 MESSAGE_NUMBER = w_msgno
 MESSAGE_VAR1 = w_msgv1
 MESSAGE_VAR2 = w_msgv2
 MESSAGE_VAR3 = w_msgv3
 MESSAGE_VAR4 = w_msgv4
 IMPORTING
 MESSAGE_TEXT = t_text-text.
TABLES
LONGTEXT =
EXCEPTIONS
MESSAGE_NOT_FOUND = 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.
MESSAGE_TEXT contains the message.
Please reward points if this explanation useful.
Regards,
Siva

What are the common errors we wil get in BDC?

what are the common errors we wil get in BDC?

hi sunil
BDC errors are similar to what you get in online transaction. Suppose you enter an invalid material number in online ME21N ( create Po ) system will throw an error and you have to correct it by chnaging a valid material number . Same error you can get in BDC as well. It is very difficult to generalize types of error as errors will depend on the transacation you are doing.
However some of the common BDC errors are ( Data for Screen Not Found, Field Not available in Screen ). These again are transaction specific and you have to analyze it by calling the transacion in display ALL mode.
The errors you get depends upon the transaction you are
running.
This is how you handle:
Let's consider you are recording for the transction CJ40
(Messages table declaration )
DATA :BEGIN of t_msg occurs 0.
include structure BDCMSGCOLL.
DATA END of t_msg.
Handling it :
CALL TRANSACTION 'CJ40' using T_BDCDATA MODE 'N' UPDATE 'S' MESSAGES INTO t_msg.
commit work.
If you want to display the errors in the screen you can use a function module named 'RPY_MESSAGE_COMPOSE'
This gives you the corresponding message for the message number that you input.
Below is the sample code
Loop at t_msg. " Messages internal table
w_msgid = t_msg-msgid.
w_msgno = t_msg-msgnr.
w_msgv1 = t_msg-msgv1.
w_msgv2 = t_msg-msgv2.
w_msgv3 = t_msg-msgv3.
w_msgv4 = t_msg-msgv4.
CALL FUNCTION 'RPY_MESSAGE_COMPOSE'
EXPORTING
LANGUAGE = SY-LANGU
MESSAGE_ID = w_msgid
MESSAGE_NUMBER = w_msgno
MESSAGE_VAR1 = w_msgv1
MESSAGE_VAR2 = w_msgv2
MESSAGE_VAR3 = w_msgv3
MESSAGE_VAR4 = w_msgv4
IMPORTING
MESSAGE_TEXT = t_text-text.
TABLES
LONGTEXT =
EXCEPTIONS
MESSAGE_NOT_FOUND = 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.
MESSAGE_TEXT contains the message.
Please reward points if this explanation useful.
Regards,
navjot
reward points

Error in starting Adobe Bridge in Photoshop CS2

I've just installed Photoshop CS2, however upon opening Adobe Bridge this error message appears " The application has failed to start because libagluc28.dll was not found. Reinstalling to application may fix the problem"
I have reinstalled and click repair but to no avail
I followed Adobe Support Knowledgebase solution and run CMD and this appears:
c:Documents and Settings/Jesus M Ferraris>
then i entered the command
cacls c:\windows\installer /T /E /C /G administrators:F
but an error message appears - 'cacls' is not recognized as an internal or external command, operable program or bathc file
I also entered the next command
cacls "c:\documents and setting\all users" /Y /E /C /G administrators:F
still the same error as above appears, Please help, have I miss something or was my procedure correct...
P4, 512ram, WXP 80gHD

Very useful.
Good Luck.
My
Si
tes

Windows Vista: Ipod Error Message, no longer read by PCs

Hello,
I have a 5th generation black ipod video with 30GB of memory.
The other day I hooked it up to my laptop (Toshiba, 4 months old) that it's been functioning on with no problems whatsoever. This weird error message flashed twice about it not being able to sync because of some software problem.
Eversince then, the only thing I can charge my ipod on is the family treadmill in the basement (~_~) as no other computer in the house recognizes it. I can't even charge it through the wall sockets, either.
I have changed the ipod cord, still no luck. I've also reset the device about 3 or 4 times and uninstalled, restarted the laptop then reinstalled itunes. I would like to reset it back to factory settings but that's impossible as computers/laptops don't pick it up. I live very far from a Mac store...
What's a girl to do? I can't live without my Busta Rhymes and Wu-Tang Clan!
Any advice would be greatly appreciated! Thanks!

you have to update Vista go to this site and up-date http://windowsupdate.microsoft.com

Xi error MESSAGE_NOT_FOUND:

Similar Messages

Maybe you are looking for