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_BANK_COMM_ITERATION |
| Short Description | Segment of Bank Communication |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | Segment |
| Medium | 20 | Comm. Segment |
| Long | 30 | Segment of Bank Communication |
| Heading | 40 | Segment of Bank Communication |
Documentation
Definition
Indicates the part of the content for the bank communication that was sent to the bank.
Use
Each bank communication comprises one or more segments. The number of segments necessary for one communication depends on your bank's limits on the amount of data that can be included in an XML message. This is a technical restriction that must be considered by your bank-specific implementation for communication with this bank. If your bank does not have any limit, then all bank communications have only one segment.
Dependencies
Note that your Customizing settings for the payment method (FBZP transaction) and payment medium formats (OBPM1 transaction) may impact what is included in a segment for a payment file.
Grouping of items in the settings in the payment method per company code Customizing view can be set so that one payment order contains several items to be paid, not one payment order per item to be paid. In the payment medium format Customizing, you can determine whether one payment file contains several payment orders or just one payment order. The amount of data included in the payment file because of these settings will also impact how the system determines if a bank communication is to be divided into segments.
Example
Bank A allows you to include the data for 100 items to be paid in an XML message for a payment file. You have considered this restriction in your implementation for creating the requests and processing the responses.
You want to query the status of 300 items that have already been sent to the bank for processing. You select these items on the Process Items tab page and send the query.
The system creates the XML message for the first 100 items in the payment file and then sends the message to the bank. This is the first segment of the bank communication. The system continues by creating the next segment of the bank communication, that is, an XML message with the next 100 items in the payment and sending the message to the bank. The last segment of the communication comprises the last 100 items.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in | 607 |
