SAP ABAP IMG Activity SD_BADI_REVREC_001 (BAdI for Customer-Specific Events (POD))
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-BF (Application Component) Basic Functions
     ⤷ VFE (Package) B2R: DevClass for BAPI structures
IMG Activity
ID SD_BADI_REVREC_001 BAdI for Customer-Specific Events (POD)  
Transaction Code S_E4A_94000033   (empty) 
Created on 20080117    
Customizing Attributes SD_BADI_REVREC_001   BAdI for Customer-Specific Events (POD) 
Customizing Activity SD_BADI_REVREC_001   BAdI for Customer-Specific Events (POD) 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BADI_SD_REV_REC_PODEV    

Use

A sales document (not a contract) contains an item that is relevant for service-related revenue recognition (type 'B'). Revenue recognition does not occur until the customer has confirmed the performed service. The confirmation takes place using a customer-specific event.

This BAdI provides the following method:

  • GET_PODEV_CUSTSPEC - Manage Customer-Specific Event (PODEV)

Requirements

The event type for the sales document item has been maintained. This is done in the item category using transaction OVEP. The relevant specifications for a customer-specific revenue recognition event are:

  • Revenue event X - Customer-specific event X
  • Revenue event Y - Customer-specific event Y
  • Revenue event Z - Customer-specific event Z

Standard settings

Other revenue event types are:

  • Revenue event A - Incoming invoice
  • Revenue event B - Acceptance date

These are events that are implemented in the standard. Customer-specific events are processed in the same way as the standard types.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

In the standard the BAdI is delivered with a sample implementation, which is stored in the example class CL_BADI_SD_REV_REC_PODEV. For more information, see the documentation in the example implementation.

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20080117 
SAP Release Created in 604