If you're working in R6 and have a spirit of adventure, you might try the approach I tried. Recently, when I needed to do a bit of work with user exits for R6, I found a couple documents in the MXACSR6 folder under Integrator Samples. The documents helped quite a bit . . . after I read them several times. I managed to make my first set of changes to an R6 browser file based on those documents and some trial and error programming changes.

Bob Heavilin
IT Project Manager
Stant Corporation

Im making my first attempt to work with User Exit on the browser. I need
someone to correct me if I am thinking wrong and maybe throw in some

The part that is confusing is the extension file. Im not exactly sure what
this is.

Im suspecting its more like a parameter file. A method in which to get the

input data to the User Exit program so that it can be worked on i.e.

checked, edit. I understand I need to modify at least two programs. One
that actual populates the extension/parameter file and the other to read
it and do some processing and return a result. this correct????

In the mean time I have identified the User Exit shell programs, located
the source on the i5 and Activated both User Exit programs from the
Business Object browser.

My next step is to create two files one with keys the other with out.

The fields in the files are the fields I want to look at and process.
Basically I am

creating somewhat of a generic parameter list. that correct?????


This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.