Print Solution

The functionality of beas common service

- print asynchronously (Example WEB Application)

- create all SAP transaction asynchronously (Example WEB Application)

- simple interface to third applications.

Idea of asynchronous working

If lots of clients are working parallel with SAP Transaction on one SAP Table, it does not work because SAP must lock the database for every transaction.

This working tends to get unstable causing long waiting time for clients.

In the Beas common service work is carried out with a Stack. Every service sends the transaction command in this stack.

The Beas common service executes this in SERIAL and not PARALLEL.

This does not create deadlocks or an overload of the database and results in stable execution.

The worker does not need to wait for a response and can continue since the web service does not execute the transaction itself.

The Beas common service sends the answer (good, docentry number, error message etc.) in an answer stack.

The client can check if an answer is available at any moment, and can display it in the window (= synchronous working).

In Beas you can see the current stack in the Beas common dashboard.

To open the Beas common dashboard from Beas manage server, click on the configuration Icon see image below.

Selecting this option makes it possible to print a Crystal document:

PATH: Human Resources > Personnel > Edit an entry > Master Data – Attendance sub-tab > double-click right of "WEB terminal group" field > single-click relevant webapp 2.1 > "Setup Web Version 2" > select "Crystal" from dropdown > Click "Crystal" tab

Window webwindow_user_setup.psr

Example:  Report "IncomingGoodsLabelExample" for Goods receipt

The following variables are available in the Print interface:

(only for apps which create SAP transaction document as receipt, issue, transfer, invoice document)

This variables are available as PrintObject Variable and instance variable.

Note:

The Report "sale_and_purchase_example.rpt" is not working together with this Print Service.

For Testing you can choose "IncomingGoodsLabelExample.rpt" for Stockmanagement – Receipt App.

Send additional information to Crystal document as argument

It is possible to read additional information and to send this as arguments to the crystal document.

You can do this in the tab "Print Script", which is executed before printing

Follow script is working for every document type

You can create Labels / Documents with RTF text.

It is possible to work with placeholders.

The following variables are available in the Print interface:

(only for apps which create SAP transaction document as receipt, issue, transfer, invoice document)

This variables are available as PrintObject Variable and instance variable.

Button "Standard"

If you click on Button "Standard", Beas insert an example.

Additional Variables

If you need additional Variables, you can define this in tab "Print Script". Beas execute the script before printing the RTF text.

(beas 9.3 PL 3 HF 1)

Example: You want to send ItemCode, ItemName, DistNumber, Quantity and another information

With the following SQL Statement you can read Serial numbers, Bin locations (only Beas), Item Code,  ItemName and other information from the generated document:

instance datastore d

// Table Name is in <PrimaryTable>

// We need name of Line table: This is header table from place 2 + 1

// example: OIGN = IGN1

setvar=ls_linetable=<PrimaryTable,mid 2>1

// exceute sql statement. We use Version 2 (v2). In this way the name of columns same as field name

// (without (v2): Header_DocNum, with (v2): DocNum

d.(v2)select Header."DocNum",Header."CardName",Line."VisOrder" +1 as "VisOrder",Line."ItemCode",Line."Dscription",Line."WhsCode",Line."Quantity",&

 case when "OITM"."ManSerNum"='Y' then "OSRN"."DistNumber" else "OBTN"."DistNumber" end as "BatchNumber" ,&

 "BEAS_WHSBINJOURNAL"."BINCODE" &

from "<ls_linetable>"  Line &

 inner join "OITM" on "OITM"."ItemCode" = Line."ItemCode" &

 inner join "<PrimaryTable>" Header on Header."DocEntry"=Line."DocEntry" &

 left outer join "OITL" on "OITL"."DocType"=Line."ObjType" and "OITL"."DocEntry"=Line."DocEntry" and "OITL"."DocLine"=Line."LineNum" &

 left outer join "ITL1" on "ITL1"."LogEntry"="OITL"."LogEntry" and "ITL1"."ItemCode"="OITL"."ItemCode" &

 left outer join "OBTN" on "OBTN"."SysNumber"="ITL1"."SysNumber" and "OBTN"."ItemCode"="ITL1"."ItemCode" and "OITM"."ManBtchNum"='Y' &

 left outer join "OSRN" on "OSRN"."SysNumber"="ITL1"."SysNumber" and "OSRN"."ItemCode"="ITL1"."ItemCode" and "OITM"."ManSerNum"='Y'  &

 inner join "OIVL" on "OIVL"."TransType"=Line."ObjType" and "OIVL"."CreatedBy"=Line."DocEntry" and "OIVL"."DocLineNum"=Line."LineNum" &

 inner join "OIVK" on "OIVK"."TransSeq"="OIVL"."TransSeq" and "OIVK"."LayerID"=0 &

 left outer join "BEAS_WHSBINJOURNAL" on "BEAS_WHSBINJOURNAL"."TransNum"="OIVK"."TransNum" and (case when "OITM"."ManSerNum"='Y' then CAST("OSRN"."SysNumber" AS varchar(30)) when "OITM"."ManBtchNum"='Y' then "OBTN"."DistNumber" else '' end) = "BEAS_WHSBINJOURNAL"."BatchNum" &

 where Line."DocEntry"=<DocEntry>;

in RTF you can insert all additional placeholders:

Execute the script.

if Print type is Crystal or RTF, Beas executes the script BEFORE printing.

In this way you can define additional variables or arguments.

The following variables are available in the Print interface:

(only for apps which create SAP transaction document as receipt, issue, transfer, invoice document)

This variables are available as PrintObject Variable and instance variable.

Example:

Write Information in the Beas protocol:

protocol=error<tab>area=WEB<tab>info=<DocNumber>, <DocEntry>