printer in erp

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

printer in erp

satish
Dear Erman,

We dont want to use our production printers in test instance after clone.what are the post steps we need to perform for this.can you please help us

Thanks,
satish
Reply | Threaded
Open this post in threaded view
|

Re: printer in erp

ErmanArslansOracleBlog
Administrator
So you need to update the printer definitions during your clone operation. (or just after your clone operation)

In EBS , these printer definitions are stored in fnd_printer table.
In OS, these printers definitions are stored in files. (it changes according to your OS vendor and distro)

These EBS printers are mapped to OS printers.

That is;

In EBS (in fnd_printer) , we just have the "OS name" of the printer.

So, if you want to change the definition of a printer, then the exact change should be done in the OS layer.

So the flow is like the following;

EBS printer -> OS printer -> Physical Printer.

Ex: EBS_TEST_PRINTER  - > OS_TEST_PRINTER -> Printer

For changing a printer definition in Linux OS(Redhat or Oracle), you can use system-config-printer command. This program is actually a  gui for cups administration..

Anyways, just change the printer definition in OS layer and that's it. (again, not the name, just the definition/configuration)
Reply | Threaded
Open this post in threaded view
|

Re: printer in erp

satish
Thanks for the update erman.Few concurrent programs use some printers in prod.after clone to test,w dont want any program to use printers in test.can you provide any update command which will do it

Reply | Threaded
Open this post in threaded view
|

Re: printer in erp

ErmanArslansOracleBlog
Administrator
Then, your question is something different.
You need to make those programs to not to print anything.
This is related with concurrent program configuration.

It depends on the concurrent program and the way that you use to print its output.

If the conc program is not a custom one, and if it is not communicating with the printer using its own custom way, then you can check fnd_concurrent_programs to see the printer used by it.There is a column named PRINTER_NAME there.