Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BF (Application Component) Basic Functions⤷
VFE (Package) B2R: DevClass for BAPI structures
IMG Activity
| ID | SD_BADI_REVREC_002 | BAdI for Displaying Customer-Specific PODEV Documents |
| Transaction Code | S_E4A_94000041 | (empty) |
| Created on | 20080204 | |
| Customizing Attributes | SD_BADI_REVREC_002 | BAdI for Displaying Customer-Specific PODEV Documents |
| Customizing Activity | SD_BADI_REVREC_002 | BAdI for Displaying Customer-Specific PODEV Documents |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_SD_REV_REC_PODEV_DISP |
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 is made using a customer-specific event, which is not based on an SD standard document. However, this document should be displayed in the following transactions:
- VF43 - Revene Recognition: Posting Doc.
- VF44 - Revene Recognition: Worklist
- VF45 - Revene Recognition: Revenue Report
- VF46 - Revene Recognition: Cancellation
The following method is available for the BAdI:
- DISPLAY_PODEV_DOCUMENT: Display Document for Customer-Specific Event (PODEV)
Requirements
With the customer-specific revenue event, the event document number (REVEVDOCN) must have been filled in the revenue table (VBREVE). The field must also be included in the display variant of the relevant transaction so that a branch operation is possible.
Standard settings
If there is no implementation, a fallback class is accessed. The implementation in the fallback class attempts to display a sales document using the RV_CALL_DISPLAY_TRANSACTION function module. If it does not find a document, there is no branch operation and therefore no document is displayed.
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:
- 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. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- 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.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.andendmethod.statements. - 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: - Choose Activate.
When the application program is executed, the code you created is run through.
Example
Business Attributes
| ASAP Roadmap ID | 153 | Design enhancements |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20080211 |
| SAP Release Created in | 604 |
