Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-BP (Application Component) Business Partners⤷
FB0C (Package) Financial Accounting customers
IMG Activity
| ID | FIBL_VC_FIEB_RETURNS | Configure Returns Processing |
| Transaction Code | S_AL0_96000816 | (empty) |
| Created on | 20020205 | |
| Customizing Attributes | FIBL_VC_FIEB_RETURNS | Configure Returns Processing |
| Customizing Activity | FIBL_VC_FIEB_RETURNS | Configure Returns Processing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FIBL_VC_FIEB_RETURNS |
Use
There are two possible configurations in this Customizing activity:
Configuration 1: You define how the electronic account statement processes returned debit memos.
- Assign internal returns reasons to external returns reasons.
You assign an internal returns reason to a combination of external transaction code and external returns reason dependent on bank details.
If you want to make the same assignments for all bank details of a transaction type, you can specify the transaction type and leave the fields for the bank details blank.
If you do not specify a returns reason in the account statement, or you want to define the same returns activities for all returns reasons, enter the external transaction code and leave the field External Returns Reason empty.
- Returns activities
You define the accounts to which the returns line items and charges are to be posted and whether clearing is to be reset for the returns line item.
- Changing opened items
If you select the Reverse Clearing field, you can have the system automatically change the customer items that are reopened for each company code. You can set a dunning or payment block, or change or delete the payment method.
If you leave the fields blank, the system does not change the documents.
Configuration 2: You define which changes are to be made in the mandate when debit memos are returned by the bank.
- Remove use
If a payment run pays a payment using a SEPA mandate, the system stores this usage information in the mandate. The uses that follow control whether the system sets the indicator for a first use or follow-on use. If there is a return for a payment, then the system can delete the use information in the mandate.
- Change mandate status
You can change the mandate status. For example, you can lock or reverse the mandate.
- Select reason code for status change
You select a reason code for the change to the mandate status. For more information, see Reason Code for Status Change.
- Define lock days
Define the number of days for which the mandate is to be locked. For more information, see Duration of Lock for Mandate in Days.
Requirements
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | FIBL_VC_FIEB_RETURNS | 0 | HLA0100028 | Electronic Bank Statement |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VC_FIEB_RETURNS | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20020205 |
| SAP Release Created in | 470 |
