ForumsMessage Boards
Can we combine two QXI Qdocs (two different screens) into one and process
Balasubramanian Muthukumarasamy, modified 3 Years ago.
Can we combine two QXI Qdocs (two different screens) into one and process
Post Date: 11/20/13 (Bronze, 1 Post) Recent PostsIs it possible to combine two QXI Qdocs into one and process in QAD application. Say for example I need to process issue inventory and receive inventory in a single transaction. Whether this can be processed by joining two Qdocs, if possible will this make any lock issue if the QXI request is more or will there be any other impact.
Krzysztof Noga, modified 12 Years ago.
Re: Can we combine two QXI Qdocs (two different screens) into one and proce
Post Date: 11/20/13 (Silver, 92 Posts) Recent Posts
Hi Balasubramanian, there is no any standard way to combine two QDocs into one; a custom QDoc is required and a custom "wrapper" program. For UIAPI QDocs the wrapper must call the maintenance screens you want to combine - for example:
/* xxwrap1.p - COMBINE 3.7 & 3.9 */
{us/bbi/mfdeclre.i}
define variable vTmp as character no-undo.
repeat:
update vTmp.
/* 3.7 Issues - Unplanned */
execname = "icunis.p".
{us/bbi/gprun.i execname}
/* 3.9 Receipts - Unplanned */
execname = "icunrc.p".
{us/bbi/gprun.i execname}
end.
For such wrapper you need to create a custom QDoc using QGen and that is all. I have seen working solutions using that approach. The combined screens will not lock each other of course, unless there are multiple QDocs processed at the same time and related to the same site / item.
For SIAPI/FinAPI QDocs the idea is similar but then the wrapper procedure would be (much) more complex.
/* xxwrap1.p - COMBINE 3.7 & 3.9 */
{us/bbi/mfdeclre.i}
define variable vTmp as character no-undo.
repeat:
update vTmp.
/* 3.7 Issues - Unplanned */
execname = "icunis.p".
{us/bbi/gprun.i execname}
/* 3.9 Receipts - Unplanned */
execname = "icunrc.p".
{us/bbi/gprun.i execname}
end.
For such wrapper you need to create a custom QDoc using QGen and that is all. I have seen working solutions using that approach. The combined screens will not lock each other of course, unless there are multiple QDocs processed at the same time and related to the same site / item.
For SIAPI/FinAPI QDocs the idea is similar but then the wrapper procedure would be (much) more complex.
Message place holder