print purchase receiver program -versions


Hello List,
I have a strange problem.A user ran a version program R43510 (Print purchase
receiver).This program updates the status of the purchase orders based on
the data selection for that version.The output of the program has a lot of
Purchase order document types that were not supposed to be on the data
selection for that version .Only 2 possibilities exist--either the data
selection was changed by the user before running the program and then
reverted to original data selection or there is some kind of bug in the
program that is causing it to print out document types that it was not
supposed to.

To restate the problem with an example:

data selection for version ABC Program R43510 is Order type (F4311) = OP
there fore the output for the program should only include OP
doctypes.Unfortunately this is not the case.It includes OB,OJ,OP doc types
as well.This could have happened only if the user had chosen these doc types
in version ABC at the time of running the program OR if there is some bug
in the program that is causing it to print the wrong information.On checking
the version ABC now , it still reads as Order type (F4311)= OP.

Is there any way I can find what was the exact data selection chosen by the
user at the time the program was run?

Any insights on how I can investigate will be greatly appreciated as this is
an issue that has occured before and I haven't been able to figure out the

B7331 SQL 7 Citrix



Well Known Member
Sorry no you cannot get a record of Data Selection after the event.

In Xe (I do not know about B7331) the data selection always reverts to the
original data selection after a user has run the report, so there is no
evidence left.

OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development


Thanks for all the information.The data selection reverts to the orinal data
selection once the report is run, unless the data selection was changed
using a the row exit for data selection.Looks like this is was a user who
changed the data selection as there is no known issue found in Knowledge
garden.Thanks once again.