Write Module Error Handling

I'm currently writing data to .csv using the "Append" feature in the write module. Depending on a selection within the worksheet, one of two write modules is selected. This is done in order to have the same worksheet handle both longterm fatigue data (with peak/valley averaging) and shortterm tests.
If the filename already exists, in one of the other formats, however, the file is inaccessible and will stop the worksheet.
Is there a way to throw an error or warning instead of stopping the whole thing? Is there a way to validate the file before trying to write data?
Thank you!

I'll try to get a simplified worksheet written up. In the meantime, I have a single input for a file type. The list seen on the top left controls which of the write modules it goes to. Only one of the modules runs at a time, controlled by that list.
If the filename already exists, however, and was in the "wrong" data format, the whole measurement stops. This would be the case in the follwing example:
1) Save file in "Static" mode. Stop Test
2) Start test in "Fatigue" mode, but same file name (this could be months later)
In this case, the measurement stops (which has ramifications for the whole control system).
I'd like to have some sort of check if the file already exists. I could imagine even a simple status light that says the filename is available.
Attachments:
File Change.JPG ‏14 KB

Similar Messages

Local Module (Error-Handler) Failed the verify environment test

When attempting to start the Messaging Server, the following error
message occurs and the server fails to start:

19980226114147:Dispatch:Notification:Local Module (Error-Handler) Failed
the verify environment test.
 Module not Loaded.
 Startup Problem:
 Module Error-Handler is required for proper operation.
 Netscape Messaging Server Exiting!

This problem can be caused by a corruption to the configuration file
for the admin server that controls the Messaging server
(install_dir/admin-serv/ns-admin.conf).
Specifically, if the
Port setting is missing, the above-mentioned error will occur.

Add a valid Port setting to the
ns-admin.conf file and
rerun the /etc/NscpMail start command.

Is anyone having any idea about it...

ADF Mobile Error handling and redirect

I'm stuck on how to handle errors within my ADF Mobile application. My application consumes a number of web services and we have found we often get error messages when phone connections switch from wifi to 3g or lose connection altogether. These are errors such as SSL handshake failure, HTTP500 errors, and also errors where it can't display the binding eh "Unable to get value for the property due to invalid binding iterator" because a WS call has failed. From the little information I can find - and none of it specific to ADF Mobile, I think I need to write an error handler class which I set against ErrorHandlerClass in databinding.cpx - if that correct? Am I able to catch these errors using that method and if so has anyone got any examples at all. Ideally what I'd like to do when I've caught those errors is redirect to another page (showing something like facebooks app does when it loses a connection and says tap to try again), does anyone have any suggestions or examples?
thanks
lynsey

A sample for ADF Mobile Error Handling.
SDA013
Error Handling in ADF Mobile
https://java.net/projects/smuenchadf/pages/ADFMobile#SDA013

How to ignore a DML operation using error handler.

In our streams replication application (using Oracle 10G), we have error handler to handle the errors at destination apply process. It uses straight apply process no DML handlers except error handlers. The error handler should just log the error and LCR info into the error log table and discard the DML LCR. Error logging is not a problem. But the problem is how to ignore the error DML LCR and move to next LCR in the same transaction without rollback of the transaction or any error.
Another question, do I need to use LCR.EXECUTE() procedure to continue the transaction in case of errors?
Appreciated your help.

Thanks for reference, confirmation of use of execute function.
I read those pages and other related pages in "Oracle® Streams Concepts and Administration" too.
I am able to write an error handler to handle errors with regular apply process. It is logging "no data found" errors but failing in case of foreign key violations. Error handler takes any kind of error and logs a record into errorlog table and ignores the error. I think it is not calling error handler. I checked for handlers in dba_apply_dml_handlers table. There is a handler for Inert, update and delete. I am investigating it further now. If you have any leads, please post.
Thanks for your time and help.
Dharma

Effective error handling in Adapter Module

eX(i)perts..
Can anybody share the effective error handling strategies inside adapter modules?
Specifically looking for
1. Module parameters configuration related error handling
2. Business logic failure owing to incorrect data.
-- Amol

Hi,
Please see the following PDF documents to develop the Module processor programs.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/02706f11-0d01-0010-e5ae-ac25e74c4c81
http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/02706f11-0d01-0010-e5ae-ac25e74c4c81
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e21106cc-0c01-0010-db95-dbfc0ffd83b3
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9913a954-0d01-0010-8391-8a3076440b6e
help : http://ifr.sap.com
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6f83d790-0201-0010-629d-ab5bf10c94e4
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7bf6e190-0201-0010-83b7-cc557eb76abe
Some weblogs for JAVA mapping for IDoc mapping
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-i
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-ii
Difference in using java,xslt,message mapping
Regards
Chilla..

Error with Writer module

Hello,
I am trying to read from an Azure SQL database and write to an empty one with the same column schema. When I run the experiment it says
Error 0000
and says
Process exited with error code -2
is there something I am doing wrong or is this a problem with the writer module?

Hi,
I created a new table with the exact output schema I want and a clustered index but now the issue I get when trying to write the data set to this table is:
[ModuleOutput] DllModuleHost Error: 1 : Program::Main encountered fatal exception: Microsoft.Analytics.Exceptions.ErrorMapping+ModuleException: Error 0000: Internal error ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: Incorrect syntax near 's'.
Module finished after a runtime of 00:00:04.9958146 with exit code -2
Module failed due to negative exit code of -2
seems like this is very difficult and confusing to write to a table and should be fixed

Module Pool Error handling

Hi friends,
This issue regarding Module Pool Error Handling
How to handle the multiple error on the same screen ,
For example in the below code you could see "Carrid is Invalid" when carrid is entred wrongly
"in the same way i also need " Connid is invalid" When the customer entres the wrong Connid
*Select single * from sflight into e_sflight*
where carrid = e_sflight-carrid AND
connid = e_sflight-connid AND
fldate = e_sflight-fldate.
IF NOT sy-subrc IS INITIAL.
MESSAGE ID 'ZADT' TYPE 'E'
NUMBER '002' WITH 'Carrid is invalid'.
Kindly let me know your feedback\
Thank you
Sandy

Hi Sandy,
in PAI. " Also try to close your Questions as currently 8 out of 8 are unresolved
Chain. " For More info take F1 help on this Key word
field : carrid, connid. " These are the Screen Field names
module validate on chain-request.
endchain.
in Program.
module validate.
select single carrid into carrid
     from scarr
      where carrid = carrid.
if sy-subrc = 0.
select single connid into connid
          from sflight
          where connid = connid,
if sy-subrc NE 0.
message 'Enter Valid Connid' type 'E'.
endif.
else.
message 'Enter Valid Carrid' type 'E'.
endif.
endmodule.
Cheerz
Ram
Edited by: Ramchander Krishnamraju on Apr 12, 2010 11:48 AM

How to write module pool program

hai,
what is the module -pool program ?
what are the procedures to write the module-pool program.
plz give the simple program for module-pool programs?
regards
surender

Hi
This component though is not attached to the screen painter, plays important role in transaction. Normally, for reports, on line executable programs are written but for transaction, Module Pool Programs are written. The module pool program contains only modules to handle various events associated with screen and data declaration statements.
System divides the module pool program into several include program. These are global field, PBO modules, and PAI modules. It is entirely users decision whether to use these modules or write directly into main program.
Creation of Module Pool Program
You can create module pool program either through
Object browser
System automatically creates the module pool program and for these program which are created through object browser, system creates the include modules.
Or
ABAP/4 editor
It is similar to normal program creation. Type of program should be given M and is not created by system.
Communication between Dynpro and Module Program
For each screen, the system executes the flow logic, which contains corresponding events. The control is passed to Module Pool Program. Module Pool Program handles the code for these events and again passes back control to the flow logic and finally to screen. Unlike on line program, in this case, the control remains with flow logic. The switching of control between flow logic and module pool program and back is common process when user executes transaction.
Creation of a Complete Transaction
Steps involved to create a complete transaction
 Create module pool program.
 From screen painter create screens.
 Write flow logic for each screen.
 Write code for all the events in module pool program.
 Check for any error in screen and flow logic.
 Generate each and every component of screen i.e. flow logic and screen.
 Single screen can be tested using Screen Painter.
 Create transaction code through object browser.
 Generate the transaction code.
 User can execute the transaction by entering the transaction code in the command field.
Handling Function Code
The function code or OKCODE is the last field of Field list. Function code can be handled as follows:
During the Designing of the screen, a function code is assigned to pushbutton.
 In field list, developer needs to specify OKCODE as last field.
 In module program it is a global field and can be evaluated in the PAI event.
 A function code is treated in the same way, regardless it comes from pushbutton, menu item or any other GUI element.
When the user clicks on the Display button, you want to display details of sflight, with corresponding carrid and connid (which is entered by the user).
Module pool program to handle this particular screen is as follows:
Program YVTEST7.
TABLES: SFLIGHT.
DATA: OKCODE (4).
MODULE INPUT1 INPUT,
CASE OKCODE.
 WHEN DISP.
 SELECT * FROM SFLIGHT
 WHERE CARRID = SFLIGHT CARRID AND
 CONNID = SFLIGHT CONNID.
 ENDSELECT.
 LEAVE TO SCREEN 200.
 WHEN EXIT. LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE. INPUT1 INPUT
MODULE USER_COMMAND_0200 INPUT.
CASE OKCODE.
WHEN BACK. LEAVE TO SCREEN 100.
ENDCASE.
ENDMODULE. USER_COMMAND_0200 INPUT
When the user clicks on display, control is transferred to screen no. 200 on which you display sflight details & on the same screen, when user clicks on BACK button, he comes back to main screen.
Flow logic for screen 100 is as follows:
PROCESS AFTER INPUT.
MODULE INPUT.
Flow logic for screen 200
PROCESS AFTER INPUT.
USER_COMMAND_0200.
MODULES: Modules are handled in module pool program.
You need to write flow logic for screen 200 and design screen 200.
In case of transaction transfer of data from program to screen is automatic i.e. you need not transfer the data from program to screen explicitly. The fields, which you define in the screen receives the data from program and displays the same.
The Field Checks
As already mentioned Transaction is the only method, which SAP recommends to update the database tables. Data entered in the database table should be valid and correct. Data entered is validated at each and every point. ABAP/4 offers various methods to validate data and those are as follows:
 Automatic field checks
 Checks performed in the flow logic
 Checks performed in the ABAP/4 module pool program
Automatic Field Checks
These checks are based on the field information stored in the dictionary. These checks are performed by the system automatically when the user enters the data for the screen field. System performs these checks before PAI event is triggered. Types of field checks performed by system are as follows:
 Required input
While designing the screen, for particular screen field if you click the Req. Entry checkbox, the field becomes mandatory. When the transaction is executed if user leaves this particular field blank, the system displays error message. User cannot proceed until the user enters some data.
 Proper Data Format
Each field has its own data format whether it is table field or screen field. Whenever data is entered, system checks for the proper format of the data. For example date. Each user has its own format for date, which is defined in the user master record. If the date defined in the user master record is in the format DD/MM/YYYY, if the user enters the date, say, in YY/DD/MM, the user displays the error message. System also checks for the value of month or days. For example if month entered is greater than twelve then the error message is displayed.
 Valid Value for the Field
In data dictionary two tables are related by Primary key-Foreign key relationship. Whenever the user enters the data, the system checks for the check table values. Also in Domain, if you have fixed values, then the system checks for these values.
Automatic field checks are repeated each time the user enters the data.
About at Exit Command
Automatic field checks can be avoided by AT EXIT-COMMAND, which works exactly the same way as Cancel works on application tools bar. In the R/3 screen, if you want to quit the processing of that particular screen without entering the mandatory fields, user can click the Cancel button. Same functionality can be incorporated in the user-defined transaction by using AT EXIT-COMMAND. This module can be called before the system executes the automatic field checks and it goes without saying that before PAI event. Code for AT EXIT-COMMAND in flow logic and in module pool program can be written as follows:
In Flow Logic
Process After Input.
Module exit AT EXIT-COMMAND.
 In module pool program.
Module exit.
Case okcode.
When Exit.
Leave to screen 0.
To achieve this kind of functionality a pushbutton or menu item should be assigned a function type E. It tells the system to process this particular module before carrying out any field checks.
Flow Logic Validations
Consider the case where you want user to enter only LH and SQ for sflight-carrid. In this case, you are restricting value of a screen field. This cannot be achieved by automatic field check. Hence there is a need of additional validation. It can be done in flow logic by using following statement:
Field -
Values
Syntax
PAI.
Field sflight-carrid values (LH).
For multiple values
PAI.
Field sflight-carrid values (LH SQ).
Field sflight-price values (between 1000 and 2000).
In this case when the user enters the value, PAI is triggered and field is checked for that particular value. If the value entered happens to be wrong, that field is enabled for user to enter. If you have multiple Field statements in your flow logic, it is sequential execution.
Consider the following case:
PAI.
Module assign.
Field sflight-carrid values (LH SQ).
In ABAP/4
Module assign.
Data: carrid1 like sflight-carrid.
Carrid1 = sflight-carrid.
Endmodule.
In this case, Sflight-carrid is used in the flow logic before the field statement. The system will give invalid value or some previous value as the field sflight-carrid is used in module before it is checked i.e., field statement is after the module in which sflight-carrid is being used. The field is not available to the system unless it executes the field statement. Field statement transfers the values to the program and is done only once. If you dont have Field statement in your flow logic, transfer of values takes place in PAI event.
Consider one more case where you have multiple field statement
PAI.
Field Sflight-carrid values (LH).
Field Sflight-connid values (0400 0500).
In this case if the user enters only carrid wrong, then this particular field is enabled and rest of the fields are disabled for user to input. Many times if the user enters wrong value for one field, then you might want to give option to user to enter all the fields, which is not possible by using Field statement only. This functionality can be achieved by CHAIN ENDCHAIN.
Syntax
Chain.
Field sflight-carrid value (LH).
 Field sflight-connid values (between 200 and 500).
Endchain.
Field sflight-price values (100 1000).
In this case, if the user enters wrong value only for carrid, both the fields i.e. carrid and connid are enabled as they are grouped together in the Chain statement. The field price will be disabled for input. Usually, logically related fields are grouped together with Chain-Endchain statement.
Module Pool Program Validations
Checking fields ABAP/4 program includes
 Field statement in flow logic.
 Module statement in ABAP/4 module pool Program.
Syntax
PAI.
Field sflight-carrid module <name>.
This module can be handled in the main program i.e. module pool program.
In ABAP/4 program
Module Check.
Select single * from sflight where carrid = sflight-carrid.
If sy-subrc ne 0.
 Message e001.
Endif.
In this case, field sflight-carrid is checked in the table for its existence.
Dynamically Calling the Screens
About Displaying Next Screen
Transaction is a sequence of screens, which are displayed one after the other. The next screen displayed depends upon the attributes of first screen. In attributes you need to give Next Screen number i.e. if next screen displayed should be 200 screen, then this number should be given in next Screen attributes. These are static attributes of the screen. By default, if nothing is specified in the program, the system branches out to the screen number, which is specified in the attribute screen.
In this case, if user selects MARA pushbutton, then fields from Mara table are displayed. When the user clicks on the MARD, then the fields from MARD table are displayed. Depending upon users selection, the screen is branched out and this has to be done during runtime. This functionality can be achieved by dynamically calling the screen in module pool program.
The screen can branch out to new screen depending upon user selection. Following command in module pool program can do this:
 SET SCREEM
 CALL SCREEN
 LEAVE TO SCREEN <NUMBER>
All these commands override the specifications given in the attributes. This overriding is temporary. The values stored in the attribute are not changed.
Set Screen
Syntax
Set screen <number>.
In module pool program
Case okcode.
 When DISP.
 Set screen 200.
 When LIST.
 Set screen 300.
Endcase.
In this case, the entire processing of current screen takes place and then the system branches out to next screen. If you want to branch out to the next screen without processing the current screen, LEAVE SCREEN should be used along with the SET SCREEN.
For Example:
Case okcode..
 When DISP.
 Set screen 200.
 Leave Screen.
 When LIST.
 Set screen 300.
 Leave Screen.
Endcase.
When SET SCREEN is used, control cannot be transferred to the main screen or previous screen, unless you write code for the same.
Call Screen
Usually used for pop up screens. Many times, there is a need for user to enter additional information or secondary information on another screen or pop up screen. Once the user enters the data, he should be able to go back to main screen or to the screen where he started. This is not possible by using SET SCREEN. CALL SCREEN achieves this functionality.
Syntax
Call Screen 200.
Will simply call a screen number 200 from a main screen. Once the screen is displayed the user can enter all the data and return to the main screen by clicking BACK button.
To call screen as pop up screen the syntax is
Call screen starting at <col.no.> <line no>
 Ending at <col no> <line no>.
In this case window will be popped as window and user can close it by using BACK button.
Leave to screen
To SET a new screen without processing current screen, you need to use the following two statements together:
SET SCREEN 200.
LEAVE SCREEN.
Or a Single statement
LEAVE TO SCREEN 200.

Equivalent for IBM specific Error handling routines

Hi,
There is a couple of IBM specific error handling routines - AFHCEEN (CEE3SPM) and XUFLOW in our FORTRAN source code which suppresses the overflow and underflow exceptions. Is there any equivalent of these routines available in SUN Solaris O/S ?

Yes, there are two ways to do it. First, if you simply want to suppress those exceptions throughout the code you can compile with -ftrap=%none.
If you need to be able to turn off those exceptions temporarily, then you can use the IEEE_EXCEPTIONS module, which is part of the Fortran standard (and thus ought to be portable). Here is an example:
use ieee_exceptions
real x
integer status
logical m
call get_command_argument(1, status=status)
if (status .eq. 0) then
   print *, 'Enabling signals'
   m = .true.
else
   print *, 'Disabling signals'
   m = .false.
end if
call ieee_set_halting_mode((/ ieee_overflow, ieee_underflow, ieee_inexact /), m)
x = 0.1
do while (x .ne. 0.0)
   x = x / 2.0
end do
endYou should be aware, though, that the standard requires the halting mode to be saved on entry to a procedure and restored on exit. Therefore, you cannot write a subroutine whose purpose is to change the halting mode in the procedure that calls it.

Fieldpoint write.vi error - 33816 (Unexpected character received from Optomux response)

Hi, I have been running a program for a few months now and yesterday I got an error at the fieldpoint write.vi error - 33816 (Unexpected character received from Optomux response). The program will run fine for approx. 5 minutes and then the error occurs, if I click continue the program will run fine again for another 5-10 minutes before occuring again. The field point module that is being affected is a digital output which is controlling a relay connected to a heating element. When the error occurs it freezes the program and if the relay happens to be on it can cause a potentially dangerous over temperature event. Luckily I happened to be in the room when it first occured but the program is supposed to rund 24-7. I tried taking off automatic error handling but that caused the program to run incorrectly.
What is causing this error ?? Why did it just materialize ? How can prevent it from happening again ?
Any insight would be greatly appreciated !

beaster wrote:
Hi, I have been running a program for a few months now and yesterday I got an error at the fieldpoint write.vi error - 33816 (Unexpected character received from Optomux response). The program will run fine for approx. 5 minutes and then the error occurs, if I click continue the program will run fine again for another 5-10 minutes before occuring again. The field point module that is being affected is a digital output which is controlling a relay connected to a heating element. When the error occurs it freezes the program and if the relay happens to be on it can cause a potentially dangerous over temperature event. Luckily I happened to be in the room when it first occured but the program is supposed to rund 24-7. I tried taking off automatic error handling but that caused the program to run incorrectly.
What is causing this error ?? Why did it just materialize ? How can prevent it from happening again ?
Any insight would be greatly appreciated !
I believe Optomux was used for the serial connection scheme (please correct me if I'm wrong) so we are looking for something that could corruprt the serial comm.
Quick Test:
Try disconnecting the relay and run the program without the heater and external circuitry to rule out glitches etc.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

LV7.1 Strange behavior with Automatic Error Handling occuring when it shouldn't [LV 7.1 Pro on WinXP for Tablet PC's]

[LV 7.1 Pro on WinXP for Tablet PC's]
I recently let a rather large LV app of mine run in the development environment while I was out for a couple of days. Upon returning I found that the app had hung for ~22 hours waiting for an answer to an Automatic Error Handling (AEH) dialog proclaiming an Error 7 in New File without any indication of the VI hierarchy that called New File. I set about ensuring that AEH dialogs would not pop up and have not been able to discover how I could have possibly received one in the first place.
Subsequent investigation revealed:
Neither AEH option in Options>Block Diagrams were checked.
Network problems had occurred around the time that the app had hung. All file paths are network paths when running in the development environment, so the cause of the error was most likely valid, even if the AEH dialog appearance wasn't.
My app has only one instance where the New File primitive is used by me. That subVI and all others above it in the hierarchy DO NOT have the AEH property enabled. The error out cluster of New File in my subvi is wired.
My app has three instances where New File is called from a vi.lib vi (Open/Create/Replace File.vi, Open Config Data.vi, and Prompt Web Browser Path.vi), none of which have the AEH property enabled. Nor does any of their calling VI's. All three instances also have their error out cluster wired.
A utility to examine the AEH property of all VI's (with all top level and dynamic VI's loaded) in memory reported that only 1 of 308 vi's ( RGT Does File Exists.vi from the Report Generation Toolkit) had that property true. That vi has no subVI's other than the File/Directory Info primitive and no calling VI's in common with any of the vi's that call New File, except a top level VI.
As long as 'Enable automatic error handling dialogs' remains unselected in options>block diagram, I am unable to get an AEH dialog for either the New File or File/Directory Info primitives in a test VI with AEH property enabled and their error out clusters unwired no matter what invalid path I pass to the functions. As soon as the options>block diagram>Enable AEH dialogs' is selected, both primitives fire AEH dialogs with no error out wired and don't when wired. i.e. works as advertised.
In other words I can find no reason why I should have gotten the problem AEH dialog...
I cannot afford for this app to hang because of a network problem, other portions of the app that were running concurrently correctly handled the error and, had the AEH dialog not appeared, the app would have made corrections or shutdown in an orderly fashion.
Any ideas?

Very good.
Write Characters to File.vi>Open/Create/Replace File.vi>New File
New File throws the error. Open/Create/Replace strips the hierarchy from the source of the error. Write Characters passes it to the General Error Handler. I never looked above O/C/R file in the hierarchy except for enable automatic error handling property. The tip-off should have been to realize that O/C/R file was stripping the hierarchy from the error and look above that.
The real irony is that Write Characters was being used to log error cluster data to an error log file...
Save as... Copy without updating... the OEM 'Write Characters to File' is gone from this app.
Thanx (a bunch)

Error handling in File - XI - SOAP scenario without BPM

Hello!
We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
Regards, Tanja

Hi Tanja,
>>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
I think, you should check that out. It is assumedly only 2 days work to build a scenario:
IDoc -> BP
BP <-> SOAP/HTTP
BP -> IDoc (Acknowledgement)
In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
>>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
Filling of ALEAUD fields:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
I ve done such a scenario several times. That works without any problems.
Regards,
Udo

Flex bug in global error handling

My application's global error handler (uncaught error handler) works mostly, but I found a case where it doesn't work, but should. Before I filed an official bug report I wanted to post the issue here.
Here is the issue: in a module, ErrorEvents that are not listened for and are dispatched by a Flex component are never caught in the application's uncaught error handler.
I have a sample project that demonstrates this. Here is the module in my test case:
<?xml version="1.0" encoding="utf-8"?>
<s:Module xmlns:fx="http://ns.adobe.com/mxml/2009"
 xmlns:s="library://ns.adobe.com/flex/spark"
 xmlns:mx="library://ns.adobe.com/flex/mx">
<fx:Script>
 <![CDATA[
 private function onClickSparkDispatch():void {
 dispatchEvent( new ErrorEvent( ErrorEvent.ERROR, false, false, "test" ) ); // this isn't caught in the uncaught error handler
 private function onClickNonSparkDispatch():void {
 var nonSparkDispatcher:EventDispatcher = new EventDispatcher();
 nonSparkDispatcher.dispatchEvent( new ErrorEvent( ErrorEvent.ERROR, false, false, "test" ) ); // this is caught in the uncaught error handler
 ]]>
</fx:Script>
 <s:HGroup>
 <s:Button label="Module Spark Dispatch (broken)" click="onClickSparkDispatch()" />
 <s:Button label="Module Non-Spark Dispatch" click="onClickNonSparkDispatch()" />
 </s:HGroup>
</s:Module>
Using Flex 4.6
My application statically links in the Flex SDK ("merged into code" in Flash Builder).
My applications works around these two exsiting bugs:
 https://bugs.adobe.com/jira/browse/SDK-28018
 http://blogs.adobe.com/aharui/2011/04/catching-uncaughterror-in-flex-modules.html
Is this a bug?
Thanks,
Rick

It’s been reported. Here is more information and a workaround. http://blogs.adobe.com/aharui/2011/04/catching-uncaughterror-in-flex-modules.html

How to perform Error Handling in this Bdc Code

Hi,
I had created this BDC for the tcode MB1B and i want to know how to perform the ERROR HANDLING in it ..
Plzz provide me guidelines for doing it . here's d code:-
report ZBDC_MB1B
 no standard page heading line-size 255.
include bdcrecx1.
data: begin of record OCCURS 0,
 WERKS_001(004), "Plant
 MATNR_002(018), "ItemId
 ERFMG_003(013), "Quantity in Unit of Entry
 ERFME_004(003), "Unit of Entry
 LGORT_005(004), "Storage Location
 CHARG_006(010), "BatchId
 KDAUF_007(010), "Sales Order Number
 KDPOS_008(006), "Item Number in Sales Order
 end of record.
PARAMETERS : P_FILNAM LIKE RLGRAP-FILENAME.
initialization.
CTUMODE = 'A'.
CUPDATE = 'A'.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILNAM.
CALL FUNCTION 'WS_FILENAME_GET'
 EXPORTING
 MASK = ',. '
 MODE = 'O'
 IMPORTING
 FILENAME = P_FILNAM
 EXCEPTIONS
 INV_WINSYS = 1
 NO_BATCH = 2
 SELECTION_CANCEL = 3
 SELECTION_ERROR = 4
 OTHERS = 5
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.
CALL FUNCTION 'WS_UPLOAD'
 EXPORTING
 FILENAME = P_FILNAM
 FILETYPE = 'DAT'
 TABLES
 DATA_TAB = RECORD
 EXCEPTIONS
 CONVERSION_ERROR = 1
 FILE_OPEN_ERROR = 2
 FILE_READ_ERROR = 3
 INVALID_TYPE = 4
 NO_BATCH = 5
 UNKNOWN_ERROR = 6
 INVALID_TABLE_WIDTH = 7
 GUI_REFUSE_FILETRANSFER = 8
 CUSTOMER_ERROR = 9
 NO_AUTHORITY = 10
 OTHERS = 11
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT RECORD.
BEGIN OF SCREEN 1
perform bdc_dynpro using 'SAPMM07M' '0400'.
perform bdc_field using 'BDC_CURSOR'
 'RM07M-SOBKZ'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
*perform bdc_field using 'MKPF-BLDAT'
 '22.12.2008'.
*perform bdc_field using 'MKPF-BUDAT'
 '22.12.2008'.
perform bdc_field using 'RM07M-BWARTWA'
 '411'.
perform bdc_field using 'RM07M-SOBKZ'
 'E'.
perform bdc_field using 'RM07M-WERKS'
 RECORD-WERKS_001. "Plant
perform bdc_field using 'XFULL'
 'X'.
perform bdc_field using 'RM07M-WVERS2'
 'X'.
BEGIN OF SCREEN 2
perform bdc_dynpro using 'SAPMM07M' '0421'.
perform bdc_field using 'BDC_CURSOR'
 'MSEG-CHARG(01)'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'MSEG-MATNR(01)'
 RECORD-MATNR_002. "ITEMID
perform bdc_field using 'MSEG-ERFMG(01)'
 RECORD-ERFMG_003. "QTY.
perform bdc_field using 'MSEG-ERFME(01)'
 RECORD-ERFME_004. "UOM
perform bdc_field using 'MSEG-LGORT(01)'
 RECORD-LGORT_005. "ST.LOC
perform bdc_field using 'MSEG-CHARG(01)'
 RECORD-CHARG_006. "BATCHID
perform bdc_field using 'MSEGK-MAT_KDAUF'
 RECORD-KDAUF_007. "S.O.
perform bdc_field using 'MSEGK-MAT_KDPOS'
 RECORD-KDPOS_008. "S.O.LINE ITEM
perform bdc_field using 'DKACB-FMORE'
 'X'.
BEGIN OF SCREEN 3
perform bdc_dynpro using 'SAPLKACB' '0002'.
perform bdc_field using 'BDC_OKCODE'
 '=ENTE'.
perform bdc_field using 'DKACB-FMORE'
 'X'.
perform bdc_dynpro using 'SAPLKACB' '0002'.
perform bdc_field using 'BDC_OKCODE'
 '=ENTE'.
perform bdc_dynpro using 'SAPMM07M' '0421'.
perform bdc_field using 'BDC_CURSOR'
 'MSEG-ERFMG(01)'.
perform bdc_field using 'BDC_OKCODE'
 '=BU'.
perform bdc_field using 'DKACB-FMORE'
 'X'.
BEGIN OF SCREEN 4
perform bdc_dynpro using 'SAPLKACB' '0002'.
perform bdc_field using 'BDC_OKCODE'
 '=ENTE'.
perform bdc_transaction using 'MB1B'.
ENDLOOP.

hi,
check this code in bold letters.
INCLUDE BDCRECX1.
TABLES : MARC.
TYPES : BEGIN OF TY_UPLOAD,
 MATNR TYPE MARA-MATNR,
 WERKS TYPE MARC-WERKS,
 STEUC TYPE MARC-STEUC,
 END OF TY_UPLOAD.
TYPES : BEGIN OF TY_MARC,
 MATNR TYPE MARA-MATNR,
 WERKS TYPE MARC-WERKS,
 END OF TY_MARC.
TYPES : BEGIN OF TY_MTART,
 MATNR TYPE MARA-MATNR,
 MTART TYPE MARA-MTART,
 END OF TY_MTART.
DATA : T_MARC TYPE STANDARD TABLE OF TY_MARC,
 : T_UPLOAD TYPE STANDARD TABLE OF TY_UPLOAD,
 : T_BASIC TYPE STANDARD TABLE OF TY_UPLOAD,
 : T_SALES TYPE STANDARD TABLE OF TY_UPLOAD,
 : T_ERROR TYPE STANDARD TABLE OF TY_UPLOAD.
DATA : IT_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
 IT_BDCDATA_VIEW LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
 IT_DATA(3200) OCCURS 0 WITH HEADER LINE,
 IT_FIELD(3200) OCCURS 0 WITH HEADER LINE,
 IT_BDCMSG TYPE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA GI_MSG LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : CHAR1(500),
 CHAR2(500),
 CHAR3 TYPE STRING,
 V_SELECTION TYPE STRING. " For View Selection
DATA : W_MARC TYPE TY_MARC,
 WA_UPLOAD TYPE TY_UPLOAD,
 WA_BASIC TYPE TY_UPLOAD,
 WA_SALES TYPE TY_UPLOAD,
 WA_ERROR TYPE TY_UPLOAD,
 WA_MTART TYPE TY_MTART.
DATA : VAR TYPE N,
 VAR1 TYPE STRING.
SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001. "SELECTION SCREEN
PARAMETERS: P_FNAM LIKE RLGRAP-FILENAME.
PARAMETERS: P_BAS LIKE RLGRAP-FILENAME.
PARAMETERS: P_SAL LIKE RLGRAP-FILENAME.
PARAMETERS: P_ERR LIKE RLGRAP-FILENAME.
SELECTION-SCREEN : END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FNAM.
PERFORM SEARCH USING P_FNAM.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_BAS.
PERFORM SEARCH USING P_BAS.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_SAL.
PERFORM SEARCH USING P_SAL.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_ERR.
PERFORM SEARCH USING P_ERR.
*& Form SEARCH
 text
 -->PFNAME text
FORM SEARCH USING PFNAME.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 STATIC = 'X'
 CHANGING
 FILE_NAME = PFNAME.
ENDFORM. "SEARCH
START-OF-SELECTION.
PERFORM UPLOAD_PROCESS USING P_FNAM.
PERFORM OPEN_GROUP.
PERFORM PROCESS.
PERFORM CLOSE_GROUP.
IF NOT T_BASIC[] IS INITIAL.
 PERFORM DOWNLOAD TABLES T_BASIC[] USING P_BAS .
ENDIF.
IF NOT T_SALES[] IS INITIAL.
 PERFORM DOWNLOAD TABLES T_SALES[] USING P_SAL .
ENDIF.
IF NOT T_ERROR[] IS INITIAL.
 PERFORM DOWNLOAD TABLES T_ERROR[] USING P_ERR.
ENDIF.
*& Form PROCESS
 text
FORM PROCESS.
LOOP AT T_UPLOAD INTO WA_UPLOAD.
 PERFORM CONV_ROUTINE USING WA_UPLOAD-MATNR
 CHANGING WA_UPLOAD-MATNR.
 SELECT COUNT(*) FROM MARA WHERE MATNR = WA_UPLOAD-MATNR.
 IF SY-SUBRC NE 0.
 MOVE-CORRESPONDING WA_UPLOAD TO WA_BASIC.
 APPEND WA_BASIC TO T_BASIC.
 CLEAR WA_BASIC.
 CONTINUE.
 ENDIF.
 SELECT COUNT(*) FROM MARC WHERE MATNR = WA_UPLOAD-MATNR
 AND WERKS = WA_UPLOAD-WERKS
 AND PSTAT LIKE '%V%'.
 IF SY-SUBRC NE 0.
 MOVE-CORRESPONDING WA_UPLOAD TO WA_SALES.
 APPEND WA_SALES TO T_SALES.
 CLEAR WA_SALES.
 CONTINUE.
 ENDIF.
 CLEAR : WA_MTART.
 SELECT SINGLE MATNR MTART FROM MARA INTO WA_MTART WHERE MATNR = WA_UPLOAD-MATNR.
 PERFORM BDC_DYNPRO USING 'SAPLMGMM' '0060'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'RMMG1-MATNR'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=AUSW'.
 PERFORM BDC_FIELD USING 'RMMG1-MATNR'
 WA_UPLOAD-MATNR.
 CALL FUNCTION 'MATERIAL_BTCI_SELECTION_NEW' " Function module
 EXPORTING
 MATERIAL = WA_UPLOAD-MATNR " Material number
 MATERIALART = WA_MTART-MTART " Material Type
 SELECTION = 'V' "
 TCODE = 'MM02' " Tcode where view's are called.
 TABLES
 BTCI_D0070 = IT_BDCDATA_VIEW
 EXCEPTIONS
 MATERIAL_NOT_FOUND = 1
 MATERIAL_NUMBER_MISSING = 2
 MATERIAL_TYPE_MISSING = 3
 MATERIAL_TYPE_NOT_FOUND = 4
 NO_ACTIVE_DYNPRO_SELECTED = 5
 NO_AUTHORITY = 6
 OTHERS = 7.
 READ TABLE IT_BDCDATA_VIEW WITH KEY FVAL = 'X'.
 IF SY-SUBRC = 0.
 V_SELECTION = IT_BDCDATA_VIEW-FNAM.
 ELSE.
 CONTINUE.
 ENDIF.
 VAR = IT_BDCDATA_VIEW-FNAM+17(2).
 VAR = VAR + 3.
 CONCATENATE 'MSICHTAUSW-KZSEL(' '0' VAR ')' INTO VAR1.
 PERFORM BDC_DYNPRO USING 'SAPLMGMM' '0070'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'MSICHTAUSW-DYTXT(06)'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ENTR'.
 PERFORM BDC_FIELD USING VAR1
 'X'.
 CLEAR VAR.
 CLEAR VAR1.
 PERFORM BDC_FIELD USING 'MSICHTAUSW-KZSEL(06)'
 'X'.
 PERFORM BDC_DYNPRO USING 'SAPLMGMM' '0080'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'RMMG1-VKORG'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ENTR'.
 PERFORM BDC_FIELD USING 'RMMG1-WERKS'
 WA_UPLOAD-WERKS.
 PERFORM BDC_DYNPRO USING 'SAPLMGMM' '4004'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=BU'.
 PERFORM BDC_FIELD USING 'MAKT-MAKTX'
 'MTI_ESE_HALB_01'.
 PERFORM BDC_FIELD USING 'MARC-STEUC'
 WA_UPLOAD-STEUC.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'MARC-HERKR'.
 PERFORM BDC_FIELD USING 'MARC-HERKL'
 'IN'.
 PERFORM BDC_FIELD USING 'MARC-HERKR'
 'MAH'.
 PERFORM BDC_TRANSACTION USING 'MM02'.
move the error record into seperate internal table nad down load it ****
 IF MESSTAB-MSGTYP = 'E'.
 MOVE-CORRESPONDING WA_UPLOAD TO WA_ERROR.
 APPEND WA_ERROR TO T_ERROR.
 CLEAR WA_ERROR.
 ENDIF.
ENDLOOP.
ENDFORM. "PROCESS
*& Form UPLOAD_PROCESS
 text
 -->PFNAME text
FORM UPLOAD_PROCESS USING PFNAME.
DATA : PFNAME1 TYPE STRING.
PFNAME1 = PFNAME.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = PFNAME1
 FILETYPE = 'ASC'
 HAS_FIELD_SEPARATOR = 'X'
 TABLES
 DATA_TAB = T_UPLOAD[].
IF SY-SUBRC <> 0.
ENDIF.
ENDFORM. "UPLOAD_PROCESS
*& Form CONV_ROUTINE
 text
 -->P_INPUT text
 -->P_OUTPUT text
FORM CONV_ROUTINE USING P_INPUT
 CHANGING P_OUTPUT.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = P_INPUT
 IMPORTING
 OUTPUT = P_OUTPUT.
ENDFORM. "CONV_ROUTINE
*& Form DOWNLOAD
 text
 -->GI_FINAL text
 -->PFNAME text
FORM DOWNLOAD TABLES
 GI_FINAL
 USING PFNAME .
DATA : FNAME TYPE STRING.
FNAME = PFNAME.
CALL FUNCTION 'GUI_DOWNLOAD'
 EXPORTING
 FILENAME = FNAME
 FILETYPE = 'DAT'
 WRITE_FIELD_SEPARATOR = 'x'
 HEADER = '00'
 IMPORTING
 FILELENGTH =
 TABLES
 DATA_TAB = GI_FINAL[]
 FIELDNAMES = GI_FIELDNAMES[]
IF SY-SUBRC = 0.
 MESSAGE 'FILE DOWNLOADED SUCCESSFULLY' TYPE 'I'.
ENDIF.
ENDFORM. " DOWNLOAD
Regards
Siva Prasad

Error Handling in Batch Script

Hi,
I have a script for deleting files from specific folders -
forfiles /P X:\<path> /D -7 /M *.* /S /C "cmd /C del @path /Q"
forfiles /P X:\<path> /D -7 /M *.* /S /C "cmd /C del @path /Q"
I need to implement error handling like folder doesn't exist or files not there etc.
Kindly help me to write the same.
Thanks,
Sugata

Robocopy is a built-in command.
There is no need to be helpless. You can find information if you search:
http://www.bing.com/search?q=robocopy
Note that this is not a support forum for the robocopy command.
-- Bill Stewart [Bill_Stewart]

Write Module Error Handling

Similar Messages

Maybe you are looking for