Pick Slip Report Not Being Printed to the Printer Selected in the Choose Printers Form (Doc ID 753988.1)

Last updated on MARCH 10, 2016

Applies to:

Oracle Shipping Execution - Version 11.5.10.0 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.

Symptoms

When submitting Pick Release SRS with a printer specified in  the Choose Document and Labels Form, the pick slip report (and any other documents in the pick release document set) are not being printed on the selected printer; although the same printer is specified in the Choose Printers setup form.


STEPS:
---------

1. Order Management Super User Responsibility
2. Nav->Shipping->Setup->Documents->Choose Printer
3. Choose a specific printer at the organization level or user level, for the pick slip report.
4. Change organizations to the same organization as was used in step 3.
5. Nav->Shipping->Pick Release->Pick Release SRS
6. In Pick Release SRS form:
   6.1 Choose a pick release rule.
7. Submit the request.
8. View->requests. When requests complete, see:
     8.1 For pick selection list generation, print option is disabled.
     8.2 For pick slip report, printer defaulted to no print. This is the value of the profile option "Printer"

Changes

NOTE:  A related issue was initially submitted to development on bug 7494849:  If customer specifies a printer in the "Upon Completion" section in the Pick Release form,  this printer is not honored.  The report will be printed on the printer defined in the Choose Document and Label Printers form, or if no printer is defined here, then the report will be printed on the printer specified in the Profile "Printers". 

Shipping Development states this behavior is "As Designed", and that the printer specified under Upon Completion applies only to the parent request, not to any child requests.  In the case of Pick release; the parent request is Pick Selection List Generations (there will never be a report attached to this request, since this request does not produce any output).  A child request is spawned for each report specified in the Print Release document set..  The printer specified in the Upon Completion section will not be cascaded down to the child requests for the reports.

In addition, when a printer is passed as a parameter to Pick Slip report , query also expects the data to be present in ( Shipping -> Setup-> Documents-> Choose printers form ) for this report with same subinventory or organization as on delivery details. You can run the following query for the setup data :

select * from wsh_Report_printers
where CONCURRENT_PROGRAM_ID in ( select concurrent_program_id from
fnd_concurrent_programs_vl
where concurrent_program_name = 'WSHRDPIK'
and application_id = 665 );

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms