SAP ABAP Data Element SD_SEPA_FLAG (SEPA-Relevance)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-BF (Application Component) Basic Functions
     ⤷ VD (Package) Application development R/3 printing, SAPscript
Basic Data
Data Element SD_SEPA_FLAG
Short Description SEPA-Relevance  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type SD_SEPA_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 10 SEPA-Rel. 
Medium 15 SEPA-Relevant 
Long 20 SEPA-Relevant 
Heading 25 SEPA-Relevant 
Documentation

Definition

Specifies whether a sales document (quotation, sales order, or contract) is to be processed using the SEPA procedure.

Use

The system determines at header or item level, whether a sales document is relevant for billing and payment using SEPA.

Dependencies

A sales document is SEPA-relevant if the following prerequisites are met:

  • You have activated the SEPA procedure in your system in Customizing for Sales and Distribution under Basic Functions -> SEPA ->Activate SEPA.
  • You have defined SEPA-relevant payment terms and payment methods in Customizing under Sales and Distribution -> Basic Functions -> SEPA -> Define Terms of Payment or Set Up Payment Methods per Country for Payment Transactions.
  • In the sales document, on the Billing tab page, you have entered a SEPA-relevant payment method. If you have defined the Payment Method at header level, the entire order is SEPA-relevant. If you have defined the payment method at item level, that specific order item is SEPA-relevant.
  • You have created a mandate reference in the system and have had it approved by the sold-to party.
  • You have defined a payment date.

Example

History
Last changed by/on SAP  20130529 
SAP Release Created in 617