Hierarchy
⤷ FIN-FSCM-COL-AR (Application Component) Accounts Receivable Accounting Process Integration
⤷ FDM_AR_COLLECTION (Package) FSCM Collections Management FI-AR
Basic Data
Data Element | FDM_COLL_TEXT30 |
Short Description | Text Field |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TEXT30 | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
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 | 0 | |
Medium | 15 | Text |
Long | 0 | |
Heading | 30 | Text |
Documentation
Definition
At account level, this field provides information about whether the data of a customer is recreated, deleted, or updated in Collections Management.
In the case of an update (only relevant for periodic data transfer according to delta procedure), the system displays at item level whether this is an increase, a decrease, or a document change. With corresponding totaling, the information about how the data in Collections Management changes (after sending) is available.
In the case of a recreation, all existing open items of the corresponding customers are displayed.
All payments of the respective customer are displayed in accordance with the entry on the selection screen of the report.
For more information (for example, the reason for deletion) see the detailed display for the item concerned.
Note that in the case of a recreation, the data of a customer is deleted in Collections Management if there are no open items and payments in FI.
Use
Dependencies
Example
- A new invoice item is entered for a customer in the amount of EUR 100. Then an update run is performed with the option Periodic Data Transfer. In the output list, the increase in the receivables balance by EUR 100 is visible, that is, this transaction is documented as an increase in the amount of EUR 100.
- After the update run, this invoice item is changed in information relevant for Collections Management. After this change, an update run is performed with the option Periodic Data Transfer. On the output list, you can see that the receivables balance has not changed, that is, this transaction is documented as a document change with amount 0 in the output list.
- After the update run this invoice item is cleared. After this change, an update run is performed with the option Periodic Data Transfer. On the output list, you can see that the receivables balance has decreased, that is, this transaction is documented as a decrease with amount EUR 100.
- A new invoice item is entered for a customer in the amount of EUR 100. Before this information is sent or transferred to Collections Management, the invoice item is cleared. Then an update run is performed with the option Periodic Data Transfer. On the output list, you can see that the receivables balance has not changed, that is, this transaction is documented as a document change with amount 0 in the output list.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 600 |