Returns

Returns enables you to process bank returns that may occur as part of a debit memo or collection procedure, or with check deposits or outgoing payments

In the first step, you have to enter the returns data in returns lots manually using returns notes or automatically using a transfer program and then post these lots. The system then processes the returns automatically.

First, the receivables or payables that were cleared on the basis of incoming or outgoing payments are determined. Then the clearing is reset, which means that the original receivables or payables are open again, and a returns document is created with the offsetting postings for the payment document items.

The system also creates further postings that are necessary because of taxes or charges, and executes follow-up activities such as adoption of incoming and outgoing payment methods. Bank charges, as well as any tax amounts contained therein, are determined from the returns amount, if this is specified, and posted to the general ledger. You can pass on any bank charges to your business partners (without tax).

By specifying amount-specific scaled charges in Customizing for the returns reason, you can levy additional charges to your business partner. These returns charges can be posted in the general ledger or statistically.

You can define the follow-up activities in the system dependent on the returns reason, the creditworthiness of the business partner, the tolerance group of the contract account, and the number of returns that have occurred. Possible follow-up activities are:

Changes to the item:

Setting a deferral date, a dunning block and/or a payment block for the reopened receivables

Changes to the contract account:

Setting a dunning block, incoming payment block, outgoing payment block and/or changing the incoming payment method, from direct debiting to payment on demand, for example.

You can also manually set a processing block with a certain time limit in order to prevent dunning notices and debit memos being generated for a contract account.

In an industry solution or a customer project, you can also realize the following activities:

• Connect processing to a workflow

• Create and transfer information for the clerk responsible

• Create correspondence for the business partner:

The system records all data and activities in a returns history. Here, for example, you can see the number of returns for a business partner. The system uses the returns history to determine the creditworthiness of a business partner

You use predefined application forms in the Correspondence component to print paper records such as return notifications. You define application forms using the Print Workbench .

Sample Transaction Codes

Transaction Code	Description
FP09	Entering and Posting Returns Lots Manually
FPM4	Returns History
FPCRL	Clarification Cases: Returns Lots

Sample Perocess Flow

Customizing

SPRO
SAP Reference IMG
- Financial Accounting
-- Contract Accounts Receivable and Payable
--- Business Transactions
---- Returns

Number Range Object

Posting Areas:

Posting Area	Description
0110	Returns

Tables

Table	Description
DFKKRK	Returns lot: Header data
DFKKRP	Returns lot: Data for payment
DFKKCFRLS	Clarification Cases: Returns Lots
DFKKRP3	Returns: Manual Posting Specifications
DFKKRP3H	Returns: History for Manual Posting Items
DFKKRPE	Returns lot: Error message for returns item
DFKKRH	Returns History
DFKKRF	Returns Lot: Reconciliation Key
TFK012	Bank clearing accounts
TFK045A	Returns table
TFK045AT	Returns texts
TFK045B	Returns Charges
TFK045C	Maximum Amount Differences
TFK045D	Assign return reasons
TFK045E	Returns Activities (Returns Lot)
TFK045ET	Texts on returns activities
TFK045T	User ID for Bank Transactions

Authorization Objects

Function Modules / BAPI

Function Module	Description
FKK_RLS_POST_LOT	Buchen eines Rückläuferstapels
FKK_RLS_POST_ITEM	Buchen einer einzelnen Rückläuferposition
FKR2_CREATE_HEADER	Erstellen eines Beleg-Headers
FKR2_CREATE_LINES	Erzeugen aller Buchungszeilen zu einer RL-Zeile
FKR2_COMPLETE_CHECK	Abschließender Check über alle erzeugten Zeilen
FKR2_ACTIVITIES_SEPA	SEPA Aktivitäten für Rückläufer
FKK_REFUSAL_POST	Buchen Rückläufer zu einer Zahlung
FKK_REFUSAL_POST_MASS	Buchen Rückläufer zu einer Zahlung
FKR2_HISTORY_CREATE_ENTRY	Erstellen einer Historien-Zeile
FKR2_HDR_CHECK_STARS	Überprüfen des Stapel-Status
FKK_RLS_STORNO	Nacharbeit bei Storno eines Rückläuferbeleg
FKR2_MANUAL_MAINTAIN	Einstieg in die manuelle Rückläuferbearbeitung
FKR2_ITEM_KILL	Löschen einer Position ohne Prüfungen
FKR2_ACTIVITIES_PROCESS	Executing Activities

Events

Archiving Objects

The entry in table DFKKRK is not deleted with the archiving deletion run. Instead the status of an archived payment lot is changed into 9 (Lot archived).

FI_MKKRET

Updates in progress - Stay Tuned..!!!