SAP ABAP Table TST03 (TemSe data) Hierarchy ☛ SAPBASIS (Software Component) SAP Basis Component ⤷ BC-CCM-PRN (Application Component) Print and Output Management ⤷ STMS (Package) TemSe. Table Category: TRANSP: Transparent table: Transparent table: TST03. The spool system uses the TemSe to store output data temporarily. The spool system uses the TemSe to store output data temporarily. You can set whether the spool data is to be stored by TemSe in the SAP database or in the file system (for more information, see Storage Methods for Spool Objects in TemSe).
SAP TemSe consistency check is to check wether entries in the TemSe data store are consistent. The TemSe consistency checks the header entry in table TST01 (TemSe objects) and object associated with the header entry; it can be stored in the file system or in the database table TST03 (TemSe.
Skip to end of metadataGo to start of metadataTemse Sap Portal
- Output in File System
the created file to be saved in the file system of the application server and not in the TemSe in the SAP System (SAP Note 1104567). - Output in the TemSe
If required, the file created can be held within the SAP System (saved in TemSe, not filed in the file system), and therefore protected from external access. The file can be downloaded to the user's file system via DME administration.
File name
relevant SAP Note 1234970
You can use exit 21 see consulting note 1234970. In exit 21 (transaction OBPM3), you can change the file name during runtime.
At event 21, you can add to a header or prefix of the payment medium that was created by event 20 by changing entries in table T_FILE_OUTPUT.
The file name can be changed using changing parameter C_FILENAME.
Import parameter I_XFILESYSTEM specifies if the file should be output to the file system or the TemSe file that was entered on the selection
screen of the generic payment medium program.
Sap Temse Consistency Check
Known issue for Output:
FZ205 : note 1786620
SAP Note 1224437 PMW: When are separate payment advice notes created?
It is a complex topic, it should be consered a lot of settings like note point 4 in note 305414
4. In payment program Customizing you have made an entry in field T042E-ANZPO (Line items per form) for the form data (Transaction FBZP / Pmnt methods in company code / Form data) and have not set the flag 'Pmnt advice if form is full' (T042E-XAVIS) A value < 99 denotes that only this number of items can be paid per form. If you define for example the value '4', then four items are always paid collectively.
Furthermore, bear in mind that an additional line is generated for an item which contains a line item text (item text BSEG-SGTXT) beginning with '*', provided that you want the text output in the form. Thus, if you want to pay four items, each containing a line item text beginning with '*', a total of 8 items are generated. Consequently, only two documents (i.e., four items) could be paid at a time per form in the above-mentioned example.
Temse Sap Services
- Lack of space for generating XML files.
Solution :note 1932233
to restrict the number of payments in a Payment Medium Workbench (PMW) file.