Hierarchy

⤷

⤷

IMG Activity
ID | RHPV0001 | BAdI: Additional Checks for Booking |
Transaction Code | S_AL0_96000451 | (empty) |
Created on | 20011121 | |
Customizing Attributes | RHPV0001 | BAdI: Additional Checks for Booking |
Customizing Activity | RHPV0001 | BAdI: Additional Checks for Booking |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | RHPV0001 |
Use
The Business Add-In (BAdI) RHPV0001 enables additional checks of attendance or business event data before an attendee is booked for an event.
For example, it allows an attendee to be booked only if he or she satisfies the credit rating check.
The BAdI is processed when a booking, prebooking, rebooking, or replacement is made. If the BAdI is activated, it enables additional checks to be carried out on attendance or business event data in addition to the checks in the standard system. The messages generated by this are output after the BAdI is called.
Note
The checks performed in the standard system can be switched off by the method Activate/ deactivate checks.
Structure
The BAdI interface contains attendee data, business event data, and information about whether attendees are group or individual attendees.
In addition, a function code is transferred that displays what action is currently being performed.
Error messages can be generated when additional checks are performed (error, warning, and information messages). The message type determines whether a booking is permitted or not.
Note
The BAdI can also run without dialog (for example, the ESS application). In this case, no messages are output. If an error message is generated during the run, the attendee will not be booked, prebooked, rebooked, or replaced.
For more information, refer to to the documentation for Interface.
Requirements
Standard settings
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
- In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
- Enter a short text for the implementation in the Short text for implementation field.
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Further notes
For more information on using Business Add-Ins, refer to the SAP Library under Basis Components ->ABAP Workbench (BC-DWB) ->Changing the SAP Standard (BC)->Business Add-Ins.
Example
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | RHPV0001 | 0 | HLA0009703 | Training and Event Management |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20011121 |
SAP Release Created in | 470 |