SAP ABAP Data Element ARCH_OBJ_PROT_OUTPUT_2 (Archiving: Log Output in ARCHIVE_PROTOCOL* FB)
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-CCM-ADK (Application Component) Archive Development Kit
     S_ARCH_PROT (Package) Archiving: Logs
Basic Data
Data Element ARCH_OBJ_PROT_OUTPUT_2
Short Description Archiving: Log Output in ARCHIVE_PROTOCOL* FB  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type ARCH_OBJ_PROT_OUTPUT_2    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Log Output 
Medium 20 Log Output 
Long 35 Log Output 
Heading 30 Log Output 
Documentation

Definition

Choose List, if you want the log to be written to the list (spool for background jobs). The advantage of saving the log in this manner is that you can use the option of automatically storing the log in an optical archive (see spool parameter for job scheduling). Logs that have been written to the application log can only be stored manually from within the display.

Furthermore, logs that have been written to the list are automatically removed when the corresponding background job is deleted. Logs that are written to the application log have to be deleted manually.

Choose Application Log, if you want the log to be written to the application log. You can then display the log in transaction SARA using Goto -> Logs.

The advantage of saving logs in this manner is that the log messages are written to the application log already during the program runtime. (In the case of background programs this takes place every 30 minutes and for dialog programs every 10 seconds). Logs that were written to the list are only visible after the program has finished.

Furthermore, you can call up details (if available) for a message or an object per double click from the log view.

Choose List and Application Log, if you want the log to be available in both places.

Use

Dependencies

Example

History
Last changed by/on SAP  20110908 
SAP Release Created in 710