terça-feira, 30 de agosto de 2022

Configuring HTTP Content Server (2) – Save printed document (1/2)

 I will not speak about installing and configuring the HTTP Content Server, there is already very good documentation about it. Here we will see how to use the content server to store printed document.

For the example, I will used the Sales Order in an IDES Server.

Configuring the output

The configuration of the output is done using the transaction NACE.

/wp-content/uploads/2014/01/nace_1_362099.png

To configure Sales Order output, you have to select the Application “V1” and press the button “Output types”

/wp-content/uploads/2014/01/nace_1_362099.png

The standard Output Types for the sales order is BA00, I will use it.

Select the Output type in the right part, and double click on “Processing routines”.

/wp-content/uploads/2014/01/nace_1_362099.png

The configuration of the Output type “BA00” for printing is this one. Program “ZSD_RVADOR01” and Smartform “ZSD_SALES_ORDER”.

Now we could open a Sales Order and check if the message BA00 works.

Transaction VA02.

/wp-content/uploads/2014/01/va01_1_362126.png

Press the button “Print preview” to display the default output type :/wp-content/uploads/2014/01/va02_4_362135.png

/wp-content/uploads/2014/01/va02_5_362136.png

The Smartforms works (good).

To display witch output type was used, you have to go in the menu :

/wp-content/uploads/2014/01/va02_2_362127.png

/wp-content/uploads/2014/01/va02_3_362128.png

This output is yellow because it’s not already processed. Print preview doesn’t process the message, even if you print during a preview !

To configure the automatic creation of this message you have to configure the transaction VV12.

/wp-content/uploads/2014/01/vv12_362137.png

(in your system, you could have several key combinations, for example to be able to specify the printer by plant / sales org / …)

if you go in detail of the condition record you will see something like this :

/wp-content/uploads/2014/01/vv12_362137.png

In this doc, we will try to use the option of the last parameter :

/wp-content/uploads/2014/01/vv12_362137.png

Configure the archiving of the Sales order

A long preparation for a quick configuration ..

Define document type :

Transaction OAM1, go in the menu :

/wp-content/uploads/2014/01/oam1_362832.png

(or directly using transaction OAC2)

/wp-content/uploads/2014/01/oam1_362832.png

I specify to the system to save the document in PDF format. I could set “*” if I will be able to store PDF, Word, Excel, …

Define the links

Transaction OAM1, go in the menu :

/wp-content/uploads/2014/01/send_362319.png

(or directly using transaction OAC3)

The key corresponding to Sales Order is VBAK :

/wp-content/uploads/2014/01/oam1_362832.png

In the OAC3 trans. we specify for this kind of document to store the document in the ContentRepository Z1 and to use the link table TOA01.

(You could use 99 link tables TOA01 -> TOA99)

Save it

Test

Now, we come back to the configuration of the output type in the VA02 transaction.

(menu : Extras -> Output -> Header -> Edit)

/wp-content/uploads/2014/01/oac3_362327.png

Select the line and Click on the button “Communication method” and select “Print & Archiv”

/wp-content/uploads/2014/01/oac3_362327.png

(don’t forget to set with the button “Further Data” : “Send immediately” )

Back and Save.

Result

In transaction VA03, go in the output type.

/wp-content/uploads/2014/01/oam1_362832.png

Select the line and go in the menu :

/wp-content/uploads/2014/01/oam1_362832.png

With Sales order you will have a popup like that, but with others transaction like Invoice you won’t.

/wp-content/uploads/2014/01/oam1_362832.png

Double-click on the document will open you an internet browser :

/wp-content/uploads/2014/01/oam1_362832.png


Source: https://blogs.sap.com/2014/01/13/configuring-http-content-server-2-save-printed-document-12/

Nenhum comentário:

Postar um comentário