Ansicht
Dokumentation

CRMC_IPM_RR_TYPE - Maintain Revenue Recognition Category

CRMC_IPM_RR_TYPE - Maintain Revenue Recognition Category

rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

In this activity you maintain the revenue recognition category. This defines the way in which revenues can be recognized and the values with which the revenue object is created in the Accrual Engine. Assigning the revenue recognition category to an item category, defines an item as being relevant to revenue recognition.

Revenue recognition method
This controls which accrual method is to be used in the Accrual Engine. Revenues are either distributed by time (period-related) or once a specific service has been performed (service-related).

Relevant application
This controls which data is used as the basis for revenue recognition. The following selection options are available here:

  • CRM contract data
    Revenues can be posted on the basis of the sales values
  • Billed values from the Billing Engine
    Revenues cannot be posted until billing has taken place.
  • IPM data values
    A data value, which is reported to the OR data collector, is to be used as the basis here, for instance if revenues are first to be posted during payment. You must first maintain the relevant data value in the R/3 Customizing settings.

Start of validity/ end of validity
The start and end of the accrual object are defined here. Revenues can only be posted within this period.

Revenue recognition start
This date defines the point from which revenues can be posted. This means that no revenue postings are made before this date. The following options for defining the date are available to you:

  • Revenues can be posted once the application data is available from the relevant application. The revenue recognition date in the contract is not relevant to this setting and is ignored here.
  • Revenue recognition date from the contract. A date can be set explicitly in the contract for each item (date type IPM_RR_DATE). This date is valid for the item and all lower-level distribution items. The date can be subsequently modified for each distribution item.
  • Manual date. The date can be set to 31.12.9999 for this option so that no revenues can be posted. You must then set the date to the correct value in the Accrual Engine.

Expand sub-items
You set this indicator if the billing request item is to be the main item instead of the accrual object. This can be relevant during milestone billing if revenue recognition is to be performed for each milestone.






ROGBILLS - Synchronize billing plans   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 2775 Date: 20240523 Time: 161619     sap01-206 ( 53 ms )