In addition to managing your own receivables, you can use the FI-CA component Revenue Distribution to manage receivables for third parties.

Transactions

Transaction
Description
FP60REvaluation of Revenue Distribution (Original Document)  => new FP60R_NEW
FP60R1Evaluation of Revenue Distribution (Distribution Document)
FP60MDistribute Revenues
FP60PPost Distribution  => new FP60PM
FP60ACreate Aggregated Distribution Information

 

Customizing

>Contract Accounts Receivable and Payable

>Business Transactions

>Distribution of Revenues

Define Specifications for Derivation of Final Recipient
Define Specifications for the Distribution of Revenues
Define Main and Subtransactions for Distribution Posting

Technical information

Tables

Table
Description
DFKKRDIRevenue Distribution
DFKKRDIRevenue Distribution
DFKKRDI_AGGRFAggregated Distribution Information
DFKKRDI_AGGRF_CAuxiliary Table for Aggregated Distribution
DFKKRDI_AGGRFHAggregated Distribution Information
DFKKRDI_BWLast Extraction to Business Intelligence
DFKKRDI_DOCLink between GUID and Actual Distribution Documents
DFKKRDI_PERIODAssignment of Distribution Periods to Distribution Groups
DFKKRDI_RATEInformation for Revenue Distribution to Final Recipient
DFKKOP .INCLUDE FKKOPRDStructure for Revenue Distribution
FINRE    FINRE_KKContract Account of Final Recipient
RDSTA   RDSTA_KKCurrent Distribution Status
RDSTB   RDSTB_KKLast Distribution Status Reported
FKKRDFINAMSummarization Structure for Revenue Distribution Doc. Postg
FKKRDI_ENHEnhanced Revenue Distribution

Events

Event
Description
0045Posting: Determine Last Recipient
0510Revenue Distribution Archiving: Check
1770Mass Activity: Revenue Distribution
1771Mass Activity: Revenue Distribution, Move Parameters
1872MassAct: Revenue Distribution – Post Distribution Documents
1873MassAct: Revenue Distribution – Distrib., Move Parameter
5400Revenue Distribution: Amount Distribution
5405Revenue Distribution: Derivations during Posting
5410Revenue Distribution: Obsolete
5415Revenue Distribution: Exclude Documents
5416Revenue Distribution: Set Correction Indicator
5420Revenue Distribution: Estimation of Distribution Installmnts
5430Revenue Distribution: File Creation by Analysis Report
5440Revenue Distribution: Select Items for Distribution
5450Revenue Distribution: Change of Amount to Be Distributed
5460Revenue Distribution: Analysis Reports

Reports

Report
Description
RFKKRD00Revenue Distribution: Create and Post Docum
RFKKRD01Revenue Distribution: List of Documents
RFKKRD02Evaluation of Revenue Distribution
RFKKRDI_AGGRCreate Aggregated Distribution Information
RFKKRDI_BWRevenue Distribution: Delta Extraction to Business Intelligence
RFKKRDI_FP60PSwitch for FP60P_OLD and FP60PM
RFKKRDI_FP60RSwitch for FP60R_OLD and FP60R_NEW
RFKKRDI_REPORTAnalysis of Revenue Distribution Based on Original Documents
RFKKRDI_REPORT_DISAnalysis of Revenue Distribution Based on Distribution Documents
RFKKRDI_REVReversal of Distribution Documents
RFKKRDRECEIPT_NOProcess Receipt File for eInvoice

Function modules

Function module
Description
FKK_RDI*
FKK_RDIP*
ENQUEUE_EFKKRDIRequest lock for object EFKKRDI
DEQUEUE_EFKKRDIRelease lock on object EFKKRDI

Posting areas

Posting area
Description
1380Derivation of Final Recipient
1381Specifications for Distribution Posting
1381Special Specifications for Distribution Posting

Archive object

Object
Description
FI_MKKREVDFI-CA: Revenue Distribution

KBA/ Consulting Notes

KBA
Description
2070651Ableitung des Verteilungsschlüssels beim Ausgleich statistischer Gebühren

Revenue Distribution

Incoming payments for third parties that you receive for example, as part of the exchange of information function, the use of value-added services, or the deregulated telephone market are automatically paid over to the final recipient.

You manage receivables for third parties and want to forward incoming payments to the final recipients.

You have made the following specifications for the distribution of revenues in the Implementation Guide forContract Accounts Receivable and Payable under Start of the navigation path Business Transactions Next navigation stepDistribution of Revenues End of the navigation path .

  • Define Specifications for Derivation of Final Recipient

  • Define Specifications for the Distribution of Revenues

  • Define Main and Subtransactions for Distribution Posting

Process Flow

  1. When you post the invoice you can enter the final recipient in the open items manually or have the system do this automatically in an installation-specific function module processed in event 0045. SAP delivers the sample function module FKK_SAMPLE_0045. Read the documentation for the module and define the function module that you created in the Implementation Guide for Contract Accounts Receivable and Payable under Start of the navigation path Program Enhancements Next navigation stepDefine Customer-Specific Function Modules. End of the navigation path SAP delivers the function module FKK_REVENUE_DIST_0045 for the automatic recording of the final recipient in FI-CA open items. Read the documentation for the function module.

  2. Using the transaction Mass Activity: Revenue Distribution , select the payments to be distributed to the final recipients in the system and, if neessary, select the open receivables for the final recipients caused by clearing reset, for example. The system creates a history (table DFKKRDI). When a payment is being distributed, the system adds an entry with an empty correction indicator to the history table. After a clearing reset for a payment that has already been distributed, an entry with correction indicator X is added with an opposite +/- sign since this amount has to be recovered from the final recipient. For a reversal and write-off of original receivables, the system creates an entry with the correction indicator R in the history table. The entries in the history are not included in the distribution posting to the final recipient. They are used as a comment and can be evaluated using customer-specific programs.

    Using an installation-specific function module in event 5415, you can exclude individual documents or line items from revenue distribution. For example, you can allow a period of 4 weeks before you forward a payment received to the final recipient.

  3. Then execute the transaction Revenue Distribution: Create and Post Documents – this distributes the revenues (incoming payments) to the final recipients. The program uses the amounts to be distributed to create totals document for each final recipient separately for further criteria, such as currency, main and subtransaction; this reduces the number of open items in the account of the final recipient. However, in individual cases distribution documents can also be created without totals. For more information, see the documentation of the report Revenue Distribution: Create and Post Documents (RFKKRD00).

    If payments and receivables for a final recipient balance to zero, two distribution documents with opposing +/- signs are posted. This enables you to create a payment advice note for the final recipient.

You can display the contents of the history using the transaction Revenue Distribution: List of Documents (SAP menu: Start of the navigation path Account Next navigation stepAdditional Information End of the navigation path ). This also displays the results of the transactions Mass Activity: Revenue Distribution and Revenue Distribution: Create and Post Documents . For more information, see the documentation of the report Revenue Distribution: List of Documents (RFKKRD01).

For a detailed evaluation of which documents were posted for distribution to a final recipient, which documents have already been paid, and which revenues have been forwarded to the final recipient, you can use transactionEvaluation of Revenue Distribution (see SAP menu: Start of the navigation path Account Next navigation stepMore Information End of the navigation path ). For more information, see the documentation for the report Evaluation of Revenue Distribution (RFKKRD02).

Using the transaction Distribute Revenues , you select existing payments that are to be distributed.

The final recipients are noted in the open items and the items were cleared.

  1. Choose the transaction Mass Activity: Revenue Distribution in the SAP menu under Start of the navigation path Periodic ProcessingNext navigation stepFor Contract Accounts Next navigation stepRevenue Distribution Next navigation stepDistribute Revenues. End of the navigation path

  2. Enter a date and an ID that you can use to identify the run later.

  3. Restrict the payments to be selected by business partner, contract account, company code, or final recipient.

  4. Start a simulation or schedule a run.

    For more information, see Functions for Scheduling Program Runs .

Post distribution

You use the transaction Post Distribution to distribute revenues (incoming payments) to final recipients.

You have selected the payments to be distributed via the Mass Activity: Revenue Distribution (menu: Start of the navigation path Periodic Processing Next navigation stepFor Contract Accounts Next navigation stepRevenue Distribution Next navigation stepDistribute Revenues End of the navigation path ).

  1. Choose the transaction Revenue Distribution: Create and Post Documents in the SAP menu under Start of the navigation path Periodic Processing Next navigation stepFor Contract Accounts Next navigation stepRevenue Distribution Next navigation stepPost Distribution End of the navigation path .

  2. Enter the run date and the ID of the distribution run ( Mass Activity: Revenue Distribution ) for which you want to post distributions. The program proposes a reconciliation key and the current date as document and posting date.

  3. Start the run as a test run or post it immediately.

Creating Payment Advice Notes

The payments to be distributed to the final recipient are created in the form of totals postings. The payment program uses these to create a transfer. However, in this transfer for the final recipient, it is not visible which business partners have paid which open items. For the final recipient to see which paid items make up the payment amount transferred, in data medium creation you can create a payment advice note where you explain which payments make up the totals posting to the final recipient.

  • The payment program is used for the payment to the final recipient; the data media are created in the payment program.

  • There has been no manual or automatic clearing in the account of the final recipient, which means that you can use the payment program for payment.To prevent clearing, when you post the distribution documents, set the clearing restriction Z . This has the effect that only the payment program can perform clearing. To set the clearing restriction, make the corresponding setting in the Implementation Guide for Contract Accounts Receivable and Payable under Start of the navigation path Business Transactions Next navigation stepDistribution of Revenues Next navigation stepDefine Specifications for Distribution of Revenues End of the navigation path .

  • If a payment run posts payments to a final recipient and receivables for the same amount due to adjustment postings, zero balance clearing can occur. In this case, no data media and no payment advice note are created. You can prevent this by defining an installation-specific function module for event 0600. This module should set the different grouping criteria for credit memos and debits.

  • You do not use a separate payment media format for revenue distribution – you use the same payment media formats for different payment methods. In the payment media format, in the company code you have defined that a payment note advice is only to be created for an excess of information lines. If you use your own payment media format for revenue distribution, in the company code you can configure that a payment medium advice note is always to be created. The subsequent steps are then partially superfluous.

  1. In the Implementation Guide for Contract Accounts Receivable and Payable choose: Start of the navigation path Business Transactions Next navigation stepPayments Next navigation stepIncoming/Outgoing Payment Creation Next navigation stepMaintain Note to Payee Type for Payment Media. End of the navigation path

  2. Create a note to payee type (for example, RDI) for the payment media creation for revenue distribution and the payment media format that you use.

    Do not make any entries under User-Defined Specifications for Creation of Note to Payee , and do not set the creation to active.

  3. Under Program Technical Specifications for Creation of Note to Payee , define a customer-defined function module or the function module FKK_PAYMEDIUM_SET_XAVIS provided by SAP. This module forces the creation of a payment advice note in every case. Then set the indicator Creation Active .

  4. For the content of the note to payee type for the notification type A , specify the text that is to appear in the note to payee when the payment advice note is created (for example, Payment advice note will follow by post ).

  5. In the Implementation Guide for Contract Accounts Receivable and Payable choose Start of the navigation path Business Transactions Next navigation stepPayments Next navigation stepIncoming/Outgoing Payment Creation Next navigation stepDefine Payment Methods. End of the navigation path

  6. Define separate incoming and outgoing payment methods for payments with the final recipient (for example, X and Y), and define the previously created note to payee type (for example, RDI) in these payment methods.

  7. Define the incoming and outgoing payment method X and Y in the contract accounts of the final recipient.

  8. Create a customer-specific application form for the payment advice note to the final recipient. SAP delivers the example forms of form class FI_CA_PAYMENT: FI_CA_PAYMENT_REV_DIST_SF (SmartForm) and FI_CA_PAYMENT_REV_DIST_PDF (PDF). Note that the selection of distribution table DFKKRDI is provided in the user exit include RFKKRD_PRINT_SAMPLE_EXIT delivered by SAP. If the data selected is sufficient to meet your purposes, you can use this include again. If the data is not sufficient, you have to create your own includes for data procurement.

  9. In the Implementation Guide for Contract Accounts Receivable and Payable , choose Start of the navigation path Business Transactions Next navigation stepPayments Next navigation stepIncoming/Outgoing Payment Creation Next navigation stepDefine Specifications for Paying Company Code End of the navigation path and define the application form for payment methods X and Y in the payment company code under Specifications for Payment Advice Note .

 

Average Rating
0 out of 5 stars. 0 votes.
My Rating:

0 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *