For event-based deferred revenues, neither the time nor amount for revenue recognition is known at the time of invoicing. This means that each event that triggers revenue recognition must be reported to the SAP system, along with the date and amount.

You have made the following settings in Customizing for Contract Accounts Receivable and Payable:

  • Define account determination for deferred revenue under Start of the navigation path Business Transactions Next navigation stepDeferred Revenue Postings Next navigation stepMaintain Account Determination for Deferred Revenue Postings End of the navigation path.

  • Specify the document type for the documents created by the transfer posting run by choosing Start of the navigation path Business Transactions Next navigation stepDeferred Revenue Postings Next navigation stepMaintain Default Values for Transfer Posting Run End of the navigation path.

  • Enter an alternate cost center under Start of the navigation path Business Transactions Next navigation stepDeferred Revenue Postings Next navigation stepExchange of No Longer Valid Account Assignments Next navigation stepAssign New Cost Center End of the navigation path.

  • Enter an alternate profit center under Start of the navigation path Business Transactions Next navigation stepDeferred Revenue Postings Next navigation stepExchange of No Longer Valid Account Assignments Next navigation stepAssign New Profit Center End of the navigation path.

The functions for event-based deferred revenue use the following four, new database tables, belonging to three different categories:

  • The header table DFKKDEFREV_HEAD contains an entry for each G/L posting for which the functions for event-based deferred revenue should be used.

  • The item table DFKKDEFREV_POS contains the information for the initial transfer from the revenue account to the G/L account for deferred revenue.

  • The trigger tables DFKKDEFREV_TRIG and DFKKDEFREV_TRIGE contain the information about the reported events (DFKKDEFREV_TRIG: revenue recognition/DFKKDEFREV_TRIGE: check date) that is processed by the transfer run for deferred revenues.

SAP provides the following function modules that you can use to implement the functions for event-based deferred revenues:

  • FKK_DEFREV_BY_EVENT_CREATE

    The module registers the desired G/L items when an FI-CA document is posted, and thereby activates further processing of these G/L items in the context of event-based deferred revenues.

  • FKK_DEFREV_BY_EVENT_RAISE

    The module reports the events (with date and amount).

In the standard system, these function modules are called from invoicing. Invoicing documents arise from billing documents, which in turn can be created using event detail records (EDRs). When an event is reported to the SAP system, the system generates a trigger table entry (DFKKDEFREV_TRIG/DFKKDEFREV_TRIGE). The transfer run for deferred revenues processes these entries.

Test of the Function

You can use the report TEST_DEFREV_TABLE_ENTRIES to test the processing of event-based deferred revenues. Using this report, you can create a list of all DFKKDEFREV* table entries for an assignment key. To test the reporting of an event (revenue recognition), you can use report TEST_DEFREV_RAISE_EVENT.

In the document display transaction, you can display the most important attributes of deferred revenue postings by choosing Start of the navigation path Extras Next navigation stepDeferred Revenues End of the navigation path.

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 *