ALE Error Message Handling

Hi,
In ALE:
(1) If it is a error means it has to be send to a particular user---> where we will configure these this thing.
(2) How the user will be intimated for the error in the IDOC, what's the medium he will be intimated whether by
e-mail it can be intimated. what are the other possible mediums?
In ALE STANDALONE METHOD (i.e., i created my own program for sending the IDOC)
(3) If i got error message --> i want to reprocess that IDOC, where i can reprocess.
(4) I what to find where that error has occured, where we can find. Is there any possibility of debugging there?

Hello Mahesh
On ERP 6.0 you have the standard report RSEIDOCA ( Active IDoc Monitoring as of Release 6.10 ) available. Unfortunately this report does not offer an e-mail notification (see also thread e-mailing: How to sent out an email to the Managers OUTLOOK express account). Normal procedure is to generate work items.
Reprocessing of failed IDocs is done using transaction BD87.
In order to debug IDoc processing you can use transaction WE19. Please note that in this case a new IDoc (having the same data as the chosen one) is created.
Regards
Uwe

Similar Messages

Error message handling in BAPI...

Hi Guys,
I am working on documentation of a BAPI used SAP insurance module. Now I want to see all the error messages associated/ handled in that BAPI. How can I do that ? Is there a table in data dictionary where I can see error messages handled by a given Function module/ BAPI?
Any inputs will be highly appreciated.
Thanks.
Regards,
Tushar.

Hi,
here´s one possible solution:
CALL FUNCTION 'MESSAGES_INITIALIZE'.
LOOP AT it_return_bapi.
    CALL FUNCTION 'MESSAGE_STORE'
         EXPORTING
              arbgb          = it_return_bapi-id
              exception_if_not_active = ' '
              msgty                = it_return_bapi-type
              msgv1          = it_return_bapi-message_v1
              msgv2          = it_return_bapi-message_v2
              msgv3          = it_return_bapi-message_v3
              msgv4          = it_return_bapi-message_v4
              txtnr          = it_return_bapi-number
              zeile          = ' '
         EXCEPTIONS
              message_type_not_valid = 1
              not_active              = 2
              OTHERS                  = 3.
ENDLOOP.
CALL FUNCTION 'MESSAGES_STOP'
       EXCEPTIONS
            a_message = 04
            e_message = 03
            i_message = 02
            w_message = 01.
IF NOT sy-subrc IS INITIAL.
    CALL FUNCTION 'MESSAGES_SHOW'
         EXPORTING
              i_use_grid         = 'X'
              i_amodal_window    = i_amodal_window
         EXCEPTIONS
              inconsistent_range = 1
              no_messages        = 2
              OTHERS             = 3.
ENDIF.
ENDFUNCTION.
Best regards

[BUG] Problem with Error message handling in JDeveloper 11.2.1.0

Hello!
I'm Daniel from Brazil.
I have been facing a problem recently to which I see no solution. I need to use a specific component called 'Panel Label and Message' in order to nest three other components which need to be grouped together to work properly (an input text box, a LOV calling 'search button', which searchs and populates the input box, and an output text box which displays text depending on the input field). This works fine!!
The problem comes when I try to place an Access Key that should focus on the input text box part of the group component. In order to do that, I put it on the 'Panel Label and Message' component, and set the 'for' property to the input text box. This too works fine, as when I access it the component redirect the focus to the right place.
Problem is, when the user decides to this specific field (which is required) blank, JDev has problems handling the actual name of the component, and just calls it 'Component', as the screenshots below show. Apparently, for the other error messages that are handled by myself or generated by other means, it deals with the component's actual name just fine. Is there any way around this? Thanks!
'Panel Label and Message' component properties. it9 is the id of the 'Input Text' field component. Access Key set to F.
http://img.photobucket.com/albums/v82/myfireburnsblack/PropertiesErrorBug.png
Error message I get (it's in portuguese). Field has been left blank, and JDev says I have to put something in, but refers to the field as 'Component'. Any other error is handled correctly, as far as I've tested.
http://img.photobucket.com/albums/v82/myfireburnsblack/jdevError.png

Hi Daniel,
You're not the only one who has seen this: {message:id=9938606}
As mentioned in that other thread - I had tested similar use cases and it works for me.
Do you have access to https://support.oracle.com to file an SR?
John

MASS, MM42(ALE) - error messages

I am updating MARA-LABOR for a number of articles in MASS. There are messages posted in the application log than pertain to checking tables and fields other than the one I have selected for update and related to sites that I do not have access to update.
I am wondering why the program is checking the site data related to the article (tables MARC, MBEW, WLK2 for example) when the table I am trying to update is not site specific.
I know that I can update the authorization profile to clean up the hard error I am getting but I would like to understand why the check is being made. I believe this has to do with ALE Master data distribution configuration but I am not sure.
Thank you.
L

There are some function modules like "KYVA_REPORT_VARIANTS_DELETE or get user variants "RM_GET_VARIANTS_4_REPORT_USER".
- is there any transaction in SAP, which delete the mass variants for reports for all users?
2- I am getting an error An Idoc without a message type was passed to the ALE layer.
I have already check file port is set up correctly and I am passing message type HROT_BRM.
This also happen in previous test, as user does not have the proper authorization, so I assign the authorization and ran it. It worked.
However, this time a user has the authorization and still the error messaging is coming. Am I missing something?

ALE Error Message

I have a master client tha sends vendor information to other production clients. I'm using the CREMAS message type. I'm getting the message the messages "Field LFA1-NODEL . is not an input field", "Field LFB1-NODEL . is not an input field" and "Field LFA1-SPERQ . is not an input field". If I look at the idoc, the field that the message is referencing is not populated with any value.
Any ideas what the issue might be,
Thanks,

I'm not sure what they systems was doing. When we tried to use our normal production id to process the idocs, this message appeared on all of them. Since the error message didn't go with what we were seeing, we decided to try a SAP delivered ALE administrator role. This id processed the idocs without any issues. We will continue to research incase the issue come up again.
Thanks for taking the time to respond,

Error Message Handling

Hi,
I am trying to execute the below code resulting in a 'refernce to null'. Could any one please help me with some sample code.
DATA : IM_MESSAGE_HANDLER type ref to IF_HRBAS_MESSAGE_HANDLER.
DATA message TYPE symsg.
MESSAGE E015(zhr) WITH 'ERROR MESSAGE' INTO message_dummy1.
MOVE-CORRESPONDING sy TO message.
im_message_handler->add_message( EXPORTING message = message ).
Thanks,
Vind.

Posted across ABAP forum, so closing here

BAPI Error Message Handling

Hi Group,
I am using BAPI ,How to display the BAPI Error Message (eg:BAPIRET1) which is returning by BAPI

HI ,
ITS SIMPLE TRY THIS CODE
AWARD PTS
DATA: gt_ret TYPE TABLE OF bapiret2,
 ls_ret TYPE bapiret2,
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
 EXPORTING
 salesdocument = p_vbeln
 order_header_in = gt_hdr
 order_header_inx = gt_hdrx
 TABLES
 return = gt_ret -
>>>>.IMPORTANT
 order_item_in = gt_itm
 order_item_inx = gt_itmx
 schedule_lines = gt_sched
 schedule_linesx = gs_schedx
 order_text = gs_stdtxt.
 PARTNERS = gs_partner
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
LOOP AT gt_ret INTO ls_ret.
 WRITE:/ ls_ret-type.
 WRITE:/ ls_ret-message.
ENDLOOP.

Error message handling in PO Badi

Hi,
We have some usewr checks in Process_item method of the purchase order BADI.
We use macro mmpur_message_forced to display the messages and macros:
mmpur_remove_messages_by_id le_item-id.
mmpur_business_obj_id le_item-id.
to delete the messages.
The problem is that this last two also delete the system messages. How can we solve this?.
Rgds,
Jose

hi kavitha,
Y dont u use BAPI, it can collect all the errors.
BAPI_INCOMINGINVOICE_CREATE
warm regards
Gokul

Error message handling in Integration Process

How to use the fault message type? when define the fault message type for inbound message interface, how to output that fault message?
hope from your helps
Thanks,
Michael

Hi,
A fault message is usually sent from the receiver system to the sender system.
when define the fault message type for inbound message interface,
We usually use fault messages when we need the receiver to report an application error to the sender.
How to use the fault message type?
In order to use these fault messages, we need to make use of the data type exchange fault data.
We need to create a message type which has exchange fault data as the message type.
When we create an outbound synchronous interface, we need to specify this fault message type.
how to output that fault message?
This i am not very sure.
But we must be able to map it to a similar structure, and send it as a file to a file server.
Regards,
Smitha.

RF screen FM error message handling

Hi Experts,
I have created RF transaction to create transfer orders to for moving storage loc.
Using the FM LEINT_To_MOVE_SU_CREATE
The issue is if the FM returns any Exception..its directly displayed in the status bar of the main SAP screen.
How can i capture the FM exception and show them on the RF screen itself.
Need help on this.
Thanks
Jaif

You need to check sy-subrc and capture those exceptions and messages from sy-msg* variables. Once you know exception is raised by FM, prepare your own screen output as per your RF screen setting (8x40 or 16x20) and populate proper message with message variables on custom error handeling screen.
Regards,
Pranav

Catching System Error Message in Abap Proxy.

Hi all,
I want to know whether it is possible to catch the system error message from SXMB_MONI in proxy scenario's.
The error i am getting 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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Service is not active</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 403 with the description Forbidden Error when sending by HTTP (error code: 403, error text: Forbidden)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Is it possble to catch the above message text.
Regards,
Keith

Hi Keith,
Check this forums also should be definitely help u..
Error message handling in Integration Process
and
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/content.htm
also refer
Check this weblog once ... sure it will give u an idea..
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
and also go through this
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
Regards,
Sridhar

About ale error handling in workflow?

Hi,
can any one explian in detail ale error handling through workflow,its urgent for me.
Regards,
phani

Hi Srikanth,
follw the steps it will helpful u,
Pre-requisites.
It is assumed that the reader of this article has some knowledge in SAP workflow BOR objects and ALE Idoc process like process code, Partner Profile etc.
Description
Here, we will be discussing in details the Error handling of an Inbound Idoc through triggering an event, which in turn will be triggering a workflow attached to the workflow.
Steps:-
1.     Create custom BOR object with the events, Start and Stop event
2.     Create a workflow for the error handling, like generating a notification whenever an error occurred in the Inbound Idoc.
3.     Creation of Function Module and attachment with the Process Code
4.     Create the settings for the Inbound Process of the Idoc through the Process Code.
Creation of BOR objects. Go to the[http://www.****************/Tutorials/ALE/ErrorHandling/page3.htm] transaction SWO1.
Enter a name for the Object type and click CREATE button for creating the custom BOR object.
Enter the details required for creating the BOR objects...
Create the Key fields and events of the BOR object.
For creating the Key fields place the cursor on the Key fields and Click on the Create Button
Create events for triggering the workflow and stopping the workflow.
For creating the event place the cursor on the EVENTS and Click the create button like Key fields.
Create two events.
Enter the event name description etc and proceed further to create it.
Similarly create another event for ending the Workflow in the similar manner like that created earlier.
Now, Generate the BOR object through the generate button
Release the EVENTS and subsequently release the BOR object.
After the creation of BOR object
Create a workflow for the generation of notification whenever an error is reached in the Inbound Idoc.
Execute the transaction SWDD.
Click on the CREATE button for creating the workflow for error handling.
Choose the Step type to be inserted for the notification like here we are using Send Mail option for sending a mail to the user whenever any error occurred.
Activate the Workflow and test it whether it is working as per the requirement.
After the successful completion it is required to attach the workflow with the event.
Go to the Header section (Denoted by CAP).
Go to the Start Events TAB.
Enter the details of the event with which the workflow should be linked like the category, BOR object type and the event with which that should be linked.
Enter here the BOR object that has been created and give the name of event created for starting the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Generate the binding and click OK button to save the binding.
Click on Activate / deactivate button for activating the linkage.
After the successful linkage the following sign will appear on the workflow.....
This shows that the workflow has been linked to the event and it will be triggered whenever that particular event will be triggered.
After the creation and successful linkage of workflow with the event it is required it is required to generate a function module and attached it to the process code.
Go to SE37 transaction and copy a standard process code function module to a custom one. Do no delete any parameters from the function module as the SAP standard program itself is calling this.
In that function module do the required validation and whenever the validation fails set a standard parameter WORKFLOW_RESULT to 9999 from within the function module, otherwise normally proceed to set the status to 53.
After the creation of function module it is required to attach it to the process code and corresponding attached to the message type at the Partner Profile stage.
The process code is being created through the transaction WE42
Go to the change mode and click the New Entries button for creating new process code.
Enter the Process Code Name, description and choose the processing type as Processing by function module. Click on the extension button of Identification.
The details for the of the Process Code after clicking the identification button will be
Whenever idoc arrives into the Destination system then the standard SAP triggers the Process code attached to the Message type in the partner profile. The partner profile is being maintained in the transaction WE20.
Since, it is and inbound scenario so the message type and the corresponding process code will be maintained for the Inbound Parameters.
Click on Create Inbound Parameters button for creating new Inbound Message type and the corresponding message type.
Enter the process code for the corresponding message type.
Click SAVE button for saving the changes.
Whenever the IDOC arrives into the target system, it checks the partner profile and finds the corresponding process code. The process code is being linked with the function module through which the IDOC is required to be processed.
Regards,
Phani.

I have just switched over to iCloud and I am now getting an error message in iCal which is the following: The server is currently unable to handle the connection due to a temporary overloading or maintenance of the server. If this continues you should con

I have recently switched from MobileMe to iCloud and I now getting an error message in iCal :
"The server is currently unable to handle the connection due to a temporary overloading or maintenance of the server. If this continues you should contact the server administrator.
You may try to connect to the server again or take the account offline."
Since I am working from home and I am not on a server other than iCloud I don't understand why I am getting this message. (for 3 days). How do I fix it?

TomCT60,
Is your MacBook using Mac OS X 10.6.8 as indicated in your post? If so you will not be able to fully integrate with iCloud.
iCloud and Snow Leopard, by Roger Wilmut describes what iCloud options are available for Snow Leopard.
If you are using Lion, go to iCal>Preferences...>Accounts, and delete/re-add your iCloud CalDAV server.

How To Handle Error Message In TCD Recording?

Hi All,
I tried recording a transaction (my own transaction) by not enterring value in an obligatory field. the error message came. but when i executed the script, it showed an error. but actualy, the error message was expected right? how to handle this situation? i tried with tcd and sapgui recording. both gave almot the same result.
i am including the script which i have written.
MESSAGE ( MSG_1 ).
*TCD ( ZCUST , ZCUST_1 , ECC ).
SAPGUI ( SAP_1 , ECC ).
ENDMESSAGE ( E_MSG_1 ).
v_mno = &tfill.
v_msg = E_MSG_1[v_mno]-msgtext.
v_mtp = E_MSG_1[v_mno]-msgtyp.
If Msg Type is E *** **** It Has To Be E ****
IF ( v_mtp = 'E' and v_msg = 'Account no AC02 does not exist EXIT = X').
logtext(0,'Passed').
ELSE.
log(v_mtp).
log(v_msg).
logtext(1,'Failed').
ENDIF.
End Of The Condition For Message Type E ******

I have recording messages using the TCD command.
My script (very simple):
MESSAGE ( MSG_2 ).
TCD ( ME21 , ME21_1 , R3 ).
ENDMESSAGE ( E_MSG_2 ).
In the MESSAGE command interface, I defined rules to allow several kind of messages.
Execution: 3 mesages found:
      * transform PR into PO
       MESSAGE     MSG_2 [1,009 sec]
         RULES MSG_2 = XML-DATA-01
        Message MODE EXIT TYPE ID    NR
        [1]      'A'         'I'   06    456
        [2]      'A'         'W'   'ME' 080
        [3]      'A'         'E'   'ZE' 029
         TCD    ME21                 [0,545 sec N] Target sys R3 -> ZDA010A219
        S06017 Standard PO created under the number 8201075606
           Tgt System Z_A219->R3->ZDA010A219 (ZDA 010 ... HP-UX ORACLE)
           CALL TRANSACTION ME21 ME21_1 XML-DATA-01
           03 MESSAGES FROM ME21 ME21_1 XML-DATA-01
           I 06 456 Release effected with release code 00001
           W ME 080 Delivery date: next workday is 02.05.2007
           S 06 017 Standard PO created under the number 8201075606
       ENDMESSAGE E_MSG_2 (&TFILL = 0)
As you can see, 3 messages are found but the &TFILL variable is still 0.
I guess (but cannot test yet) I would manage to record those messages using SAPGUI command.
Is there anything wrong with my script?
My SAP_BASIS component is in version 620. I'm not using the ultimate version of eCATT (no WEBDYNPRO command, etc.). Could it be an explanation?
Thank you in advance,
Olivier

How to handle error message during PAI?

Hi Experts,
Need help here.
In my dialog screen, I have a field which is typed 'QUAN'.
In entering different format , e.g. with non numeric value or a negative value, an error message appear and it does not process the MODULES inside the chain or FIELD MODULE ON REQUEST.
Does anyone knows how to handle this kind of error. I need to display into a separate screen the errors I encountered coz I'm creating a new RF transaction.
Points will be rewarded.
Thanks in advance.

Hai
in your case(RF case) it is other way...
yes you can use
field x_currency module check_currency.
in module check_currency.
you have to display errors in another screen say 200.
in that there will be 4 fields, all are display only fields.
X_MESSAGE-MSGV1 of type sy-msgv1
X_MESSAGE-MSGV2 of type sy-msgv2
X_MESSAGE-MSGV3 of type sy-msgv3
X_MESSAGE-MSGV4 of type sy-msgv4
you populate the messages with these fields and then display it in the screen.
method check_currency.
*--do all your checks here....
       if error
         clear x_message.
        x_message-msgv1 = 'Enter Valid Employee Number'(004).
        leave to screen 0200.
      endif.
    endif.
ENDMODULE.                 " VALIDATE_Currency
in screen 200 PBO you need to format the message
using the below logic.
       Method for formatting the message
method message_format.
    data : lt_text type table of tline,         "text table
           lx_text type tline.                  "work area
    refresh lt_text.
    clear lx_text.
    concatenate x_message-msgv1 x_message-msgv2 into lx_text-tdline
      separated by space.
    append lx_text to lt_text.
    clear lx_text.
    concatenate x_message-msgv3 x_message-msgv4 into lx_text-tdline
      separated by space.
    append lx_text to lt_text.
*- formatting the message
    call function 'FORMAT_TEXTLINES'
      exporting
        formatwidth = 20
      tables
        lines       = lt_text
      exceptions
        bound_error = 1
        others      = 2.
    clear: x_message.
*- transfer the message data to screen fields
    loop at lt_text into lx_text.
      if sy-tabix = 1.
        x_message-msgv1 = lx_text-tdline.
      elseif sy-tabix = 2.
        x_message-msgv2 = lx_text-tdline.
      elseif sy-tabix = 3.
        x_message-msgv3 = lx_text-tdline.
      elseif sy-tabix = 4.
        x_message-msgv4 = lx_text-tdline.
      else.
        exit.
      endif.
    endloop.
endmethod.                    "message_format
Regards
Vijay

ALE Error Message Handling

Similar Messages

Maybe you are looking for