Ansicht
Dokumentation

PM_ORDER_PRINT_CONTROL - NOTRANSL: PM: Order Print control (Dialog or Batch)

BAL Application Log Documentation   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Technical documentation to ORDER PRINT.

A diagram to illustrate the control tables and basic flow of ORDER Print.

|--------------| function |--------------------|

| ORDER |-----------------> |PM_VALID_WORKPAPERS |

|--------------| IHDR Print |--------------------|

papers saved |

Print view or <----------------------

Print to paper ? print option

|

| -------------------------

| Print view = yes |PM_ORDER_DATA_READ |

| -------------------------

| |-----------------------| |------------------------> |PM_ORDER_PRINT_CONTROL |

| Then call print |-----------------------| | control in DIALOG |

| passing all necessary data |--> Call Print ABAPS

| IE PAPERS and DATA to PRINT | with VIEW option

| in dialog

|

|Normal print PERFORM ORDER_POST in SAPLCOKO

|wait for F11 see CO_ZV_ORDER_POST function

|save. |--------------------|

| ---------------------> | PM_ORDER_DATA_READ |

| |--------------------|

| before commit work with export to memory flag

| is issued. First save see LCOIHF00

| the order date in memory.

| IE from CO_ZV_ORDER_POST

| the save data form is performed. PM_ORDER_DATA_SAVE_F00

|

So now |after the

commit |work we call called from LCOIHF00

| |----------------------|

------------------------->|PM_ORDER_PRINT_CONTROL|

CO_ZV_ORDER_POST ---------> |----------------------|

|

At this stage PM_ORDER_PRINT_CONTROL

checks that all information required is

available. eg Valid workpapers was called

and the data to print is successfully

<------------ exported to memory for the PRINT abaps to

| use. CALLED IN UPDATE TASK now in |UPDATE |TASK

|

|

----------------------------------|

|

Part of |--------------| perform all

PM_ORDER_PRINT_CONTROL | LIPRTIF02 | Print ABAPS

|--------------| to print papers

|

|

PRINT ABAPS Note all ABAPS must start|with form

PRINT_PAPER |

eg RIPRxxxx <-----------------------------|

STEPS: 1 IMPORT data to print These ABAPS are a possible

2 Print form source for customizing. Copy

3 Update Print Log and ABAP then make the

alterations. Add new paper

to t390. Similarly a form

can be copied and changed

-----------------------------------------------------------------------

D E T A I L N O T E S

CONTROL Tables: Transaction

T390 - Definition of workpapers OID1

T390_O - Definition of papers per order / notification type OID2

T390_U - What papers per user OID3

PM_VALID_WORKPAPERS

With the above tables, we have defined exactly which papers can be printed and which ABAPS and FORMS will be used to print these papers.

We have also defined which uses can print what papers. As a fine tuning option, you can also control what papers can be printed for a given order type.

When the function PM_VALID_WORKPAPERS is called the above tables are checked to see which papers are defined and can be printed.

A dialog box is displayed where the user decides which of the valid papers he wants to print. The selection is recorded for later use.

PRINT REDIRECTION. see ABAP RIPRIF01. form routines

This is an optional tool, for extreme print destination requirements.

T392 - Papers for which destination redirection is active

T392_V - The values on which to base redirection.

ORDER interface to Printing:

ORDER print is called from the order out of member LCOIHF00. There are 2 basic functions that control the entire order print cycle.

The first function calls a dialog box that determines what workpapers can be printed. Then it offers a list of papers to print where the user can fine tune what is to be printed and where. See PM_VALID_WORKPAPERS.

The second function calls PM_ORDER_PRINT_CONTROL. This control function checks that all information required for print is available.

PM_ORDER_PRINT_CONTROL_BATCH can be called in DIALOG or BATCH

CUSTOMIZING PRINT:

The individual print ABAPS RIPRxxxx can be copied and changed if you wish to make changes to what is printed. Do not forget to define the new paper in the T390 table (Transaction OID1). If it is only a very minor change to the form that is required then you can simply copy the FORM and make the necessary change. Again, you should enter this as a new form in T390. The collection of data will still be performed automatically for you. You must only ensure that when you create your own print ABAP that the data is imported exactly as it is in the ABAP you copied. It is also advisable, but not necessary, to update the print log. The code to update the print log is also in the ABAP you copied.

Parameters

CAUFVD
DEVICE
IAFFHD
IAFVGD
IDOCUMENTS
IHGNS_TAB
IHPAD_TAB
IHSG_TAB
ILOA
IQKAT
IRESBD
IRIPW0
IVIQMEL
IVIQMFE
IVIQMMA
IVIQMSM
IVIQMUR
IV_SESS_TZONE
IV_VRGNG
IWORKPAPER
KBEDP_TAB
N_IHPAD_TAB
N_RIWO1
OP_PRINT_TAB
PRINT_LANGUAGE
RIWO00
RIWO1
RQM00

Exceptions

NO_WORKPAPERS_PASSED

Function Group

IPRT

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 7709 Date: 20240523 Time: 141333     sap01-206 ( 91 ms )