SAP ABAP Data Element POS_NO_WARNINGS (POS Outbound: Warnings Should Be Treated Like Notes)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       WPOS (Package) IS-R: POS interface
Basic Data
Data Element POS_NO_WARNINGS
Short Description POS Outbound: Warnings Should Be Treated Like Notes  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type FLAG    
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  
Medium 15 Warning-> Notes 
Long 25 Warnings as Notes 
Heading 34 Declare Warnings as Notes 
Documentation

Definition

Indicator: Warnings in the status header to be declared as notes.

If a data record cannot be formatted during the formatting of data in POS outbound, the entire download is classed as being incorrect and has to be repeated, provided a 'Repetition of Formatting' does not take place via the POS monitor.

If this indicator is set, the header status is set to 'Note' instead of 'Warnings'. This means that the entire download is "OK" and does not have to be repeated. The download is now shown as being 'Processed' instead of 'Not fully processed'.

The IDOCs in which errors occured are still indicated as having errors, therefore the error logs recorded can be displayed as before.

If you set this flag, we strongly recommended that you take a look at the downloads set to 'Note' in the POS monitor and that you correct any errors that may have occured.

Attention: If 'serious errors' occur, that is errors where an entire IDOC cannot be formatted, these will not be converted into a 'Note'.

History
Last changed by/on SAP  20130529 
SAP Release Created in 46C