Process documentationEnhanced Revenue Distribution

 

You manage receivables for third parties and you want to transfer incoming payments and open receivables of the customer to final recipients. In addition, you want to extract distribution information to Business Intelligence (BI).

Prerequisites

You executed the report in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Program Enhancements Next navigation step Prepared Enhancements Next navigation step Enhanced Revenue Distribution End of the navigation path. For more information, see the report documentation.

You made the following specifications for the distribution of revenues in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Business Transactions Next navigation step Revenue Distribution End of the navigation path:

  • Define Specifications for Revenue Distribution

  • Define Main and Subtransactions for the Distribution Posting

  • Define Specifications for Invoicing

    If you want to clear distribution documents against other documents during invoicing and create corresponding invoices for the recipient, you have to activate distribution documents for Invoicing in Contract Accounts Receivable and Payable. For more information, see the documentation of the Customizing activity.

You also executed the following activities for enhanced revenue distribution in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Business Transactions Next navigation step Revenue Distribution Next navigation step Enhanced Revenue Distribution End of the navigation path:

  • Make Settings for Enhanced Revenue Distribution

    Here you can activate enhanced revenue distribution. At the same time, this also activates the distribution of assigned payments (receivables items cleared by payment). In addition, you can activate the distribution of unassigned payments (payments on account with a subtransaction designated as relevant for payment) and expected revenues (line items that are still open, but not including unassigned payments).

  • Define Distribution Groups

    Here you have to create at least one distribution group. A distribution group groups original line items that belong together based on content and that are to be processed together in revenue distribution. For each distribution group, you can also specify if you want the revenue distribution to be posted in aggregated form. These postings are made using aggregated distribution information that is created for each distribution group and application period (period key). You can analyze, assess, and adjust the aggregated distribution information before you post the distribution documents.

    The prerequisite for creating aggregated distribution information is that you use application periods. This means that the system cannot create aggregated distribution information for applications that do not use application periods.

  • Define Transaction Determination for Distribution Groups

    You assigned the necessary main and subtransactions to the distribution groups.

  • Define Distribution Periods

    You defined distribution periods. The distribution period specifies when the revenue distribution was executed in the system.

  • Define Distribution Periods for Distribution Groups

    Assign a start distribution period to each distribution group. After you have made all distributions for the distribution period, you can also increase the distribution period for the individual distribution groups.

Process

  1. Enhanced revenue distribution is based on a different technical concept than classic revenue distribution. For example, in enhanced revenue distribution, the final recipients and their respective distribution share of receivables items must already be created and exist in the table of distribution information (DFKKRDI_RATE) before you can post the receivables in Contract Accounts Receivable and Payable. The distribution information is linked to the line items (DFKKOP) using the distribution key - a GUID that is contained in the table of distribution information and in the line items.

    When posting the documents, you can use an installation-specific function module processed at event 5440 to specify which line items you want to be distributed using enhanced revenue distribution. SAP provides the sample function module FKK_SAMPLE_5440. See the documentation of the function module.

    The following applies to the information for the final recipient and the corresponding distribution ratios:

    • For assigned payments and expected revenues, you have to define the final recipient and distribution ratios before the revenue distribution process begins and write them to the table of distribution information (DFKKRDI_RATE) together with the distribution keys created.

      The corresponding distribution key is inherited on the receivables items (DISKEY field in table DFKKOP). You have to make the necessary implementation in a customer project. To add the distribution information, you can use function module FKK_RDI_RATE_INSERT.

      Note for the industry component Public Sector Contract Accounts Receivable and Payable

      To add the distribution information, you can use the Business Rules Framework (BRF). SAP delivers the BRF object TRM_TEMPLATE_OBJECT with the implementing class 0TRMRD001. With an implementation of this class, you can determine the distribution information required.

    • For unassigned payments, you first have to define the final recipients and distribution ratios using an installation-specific function module at event 5420 (sample function module FKK_SAMPLE_5420). This event is called by the mass activity for revenue distribution. The distribution key is not inherited by the payables items (in table DFKKOP), it is only recorded in the distribution table (DFKKRDI).

  2. Using the mass activity for revenue distribution, you select the line items that you want the system to distribute to the final recipients using enhanced revenue distribution. On the SAP Easy Access screen, choose Start of the navigation path Periodic Processing Next navigation step For Contract Accounts Next navigation step Revenue Distribution Next navigation step Distribute Revenues End of the navigation path. The system creates a history of the distribution, similar to the one for classic revenue distribution. (For more information, see Classic Revenue Distribution). 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 received payment to the final recipient.

  3. For distribution groups, for which aggregated posting of revenue distribution is supposed to take place, you first have to create aggregated distribution information before you can post the distribution documents. To do so, run the report Create Aggregated Distribution Information. On the SAP Easy Access screen, choose Start of the navigation path Periodic Processing Next navigation step For Contract Accounts Next navigation step Revenue Distribution End of the navigation path. The processing follows these steps:

    • The report reads the complete revenue distribution information from tables DFKKRDI and DFKKRDI_RATE (assigned payments) for the distribution group and application period you enter.

    • The report uses this information determine the proportion of the total amount being distributed that is distributed to each final recipient.

    • Then the report writes this aggregated distribution information to table DFKKRDI_AGGRF. In addition, the report marks the entries from table DFKKRDI that are now to be distributed using the aggregated distribution information.

    You can modify the data created by the report in table DFKKRDI_AGGRF. However, the system does not provide any assistance for this. If you want to use a history for your versions, you can use table DFKKRDI_AGGRFH. The mass activity for posting distribution documents then uses the aggregated distribution information from table DFKKRDI_AGGRF, rather than the distribution information from table DFKKRDI_RATE.

    For more information, see the report documentation.

  4. Run the mass activity for posting distribution documents. This activity distributes the revenues to the final recipients. (On the SAP Easy Access screen, choose Start of the navigation path Periodic Processing Next navigation step For Contract Accounts Next navigation step Revenue Distribution Next navigation step Post Distribution End of the navigation path.) Based on the amounts to be distributed, the program creates totals for each final recipient. These totals are divided into separate totals for outgoing payments and recalls, as well as for other summarization criteria, such as currency, main and subtransaction, distribution period, and type of distribution. For each total created this way, the system posts a distribution document. The posted distribution document numbers are recorded in table DFKKRDI_DOC and linked using a technical key (a GUID) with the table of revenue distributions (DFKKRDI). The summarization criteria are contained in the structure FKKRDFINAM, which you can add to as needed. This summarization reduces the number of open items on the account of the final recipient.