Jump to content


Anorton

Member Since 17 Jan 2006
Offline Last Active Dec 02 2009 08:01 PM
-----

Topics I've Started

Glovia - Error handling when function is run by Unix script

30 November 2009 - 03:37 PM

This is a redundant post, so I apologize, but I could not find how to change the topic on my post, and I wanted to include 'Glovia' - in hopes to draw in more of the Glovia crowd for my Glovia specific problem:

We are in the process of developing integrations with another system. We are using GAPI for the most part, and there are certain processes that we want automated in our system, once we receive the GAPI document.

For example, we receive a sales order message, which creates the sales order; we then want PRP to run immediately to generate a work order for the sales line, then we want to automatically commit parts to the work order, issue parts to the work order, complete the work order, ship the sales line, and forward the order to bill.

So, we decided that a good solution would be to have GAPI call a function which then executes a Unix script that executes the screen function for each process we want to automate (each process/function will have it's own script).

So, once the sales line is created by GAPI, GAPI calls and passes information to a Unix script which then basically runs the PRP process, just as though a user would.

We have one stumbling block, how do we capture any errors that occur while the Unix script executes the screen function?

If it is an error message that would normally display to the user, these are being captured in the log files, a bit messy, but they're there.

However, there are other types of errors/warnings (SLERRs) that occur in the application that can only be viewed by clicking on an error or warning icon - we aren't sure how to capture these.

We need to, so that if a transaction fails, we can determine why.

Appreciate any input!!!!!

Allison

Error handling when function is run by Unix script

25 November 2009 - 07:18 PM

We are in the process of developing integrations with another system. We are using GAPI for the most part, and there are certain processes that we want automated in our system, once we receive the GAPI document.

For example, we receive a sales order message, which creates the sales order; we then want PRP to run immediately to generate a work order for the sales line, then we want to automatically commit parts to the work order, issue parts to the work order, complete the work order, ship the sales line, and forward the order to bill.

So, we decided that a good solution would be to have GAPI call a function which then executes a Unix script that executes the screen function for each process we want to automate (each process/function will have it's own script).

So, once the sales line is created by GAPI, GAPI calls and passes information to a Unix script which then basically runs the PRP process, just as though a user would.

We have one stumbling block, how do we capture any errors that occur while the Unix script executes the screen function?

If it is an error message that would normally display to the user, these are being captured in the log files, a bit messy, but they're there.

However, there are other types of errors/warnings (SLERRs) that occur in the application that can only be viewed by clicking on an error or warning icon - we aren't sure how to capture these.

We need to, so that if a transaction fails, we can determine why.

Appreciate any input!!!!!

Allison

Regen Error

04 August 2006 - 08:22 PM

I am getting this error when trying to regen the function, however I have made no changes to anything related to this variable. I went back and tried to regen the copy version of the function before any changes had been made to it (by me anyway) and it does the same thing. What are some possible causes of this?

Report print column

19 January 2006 - 09:35 PM

We have a report that in Function Layout Edit is set to print in column one, however it prints about 3/4 inch in from the left margin and doesn't fit the form. Is there any way - spooler settings or some other printing specifications that we can use to get this report printing farther to the left?

I would think column one should print as far left as possible, but apparently not.

Also, it is not a printer issue, it prints this way on all printers.