SAP ABAP Data Element EPIC_COMM_OTHER_PARAMETERS (Structure with (Other) Parameters for Bank Communication)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FI-LOC (Application Component) Localization
     ⤷ ID-FI-EPIC-BACOM-BL (Package) Globalization: E-Payment Int. Bank Comm. Business Logic
Basic Data
Data Element EPIC_COMM_OTHER_PARAMETERS
Short Description Structure with (Other) Parameters for Bank Communication  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type AS4TAB    
Data Type CHAR   Character String 
Length 30    
Decimal Places 0    
Output Length 30    
Value Table DD02L    
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 Other Par. 
Medium 15 Other Prmtr Str 
Long 25 Other Parameter Struc. 
Heading 10 Other Par. 
Documentation

Definition

Shows the structure that the system fills with parameters necessary for creating an outgoing XML message in a bank communication. The system must derive these parameters from information already stored in the system.

Use

Enter the delivered structure (see Dependencies) that is to be filled with the derived parameters for the outgoing query for this bank. The system automatically fills these parameters when the user triggers the corresponding bank communication either on the Process Items or Process Files tab page.

Dependencies

Each bank communication type has a usage category assigned to it:

  • For bank communication types with the payment-item-related usage categories, enter the EPIC_S_ITEM_KEYS_BC_PARAMETER structure.

    This structure will be filled with the keys that identify each item, including the company code, fiscal year, accounting document number and number of line item within the accounting document. These keys are stored in the EPIC_T_GUID_BSEG_KEYS table and allow the implementation to keep track of which item is included in which query.

  • For bank communication types with the payment usage category, enter the EPIC_S_PAYM_FILE_BC_PARAMETER structure.

    This structure will be filled with the keys that identify the file, the items within the file, and the TemSe administration date for the file (stored in the REGUT table).

  • For bank communication types with other usage categories, leave this field blank.

Example

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