Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX-CN (Application Component) Real Estate Contract⤷
RE_CN_NT (Package) RE: Notice
IMG Activity
| ID | RECN_NOTICE | Implement Enhancements (BAdI) |
| Transaction Code | S_EE6_85000187 | (empty) |
| Created on | 20110802 | |
| Customizing Attributes | RECN_NOTICE | Implement Enhancements (BAdI) |
| Customizing Activity | RECN_NOTICE | Implement Enhancements (BAdI) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_RECN_NOTICE |
Use
The Business Add-In (BAdI)
- makes it possible to enhance the standard behavior when saving a notice and
- to change the reason for notice for already active notices.
Requirements
Standard settings
Activities
You can implement the following methods of the BAdI using transaction SE19:
- AFTER_STORE (Perform additional actions after saving)
Parameters:
IO_OBJECT Generic object reference
IT_OLD_LIST Notice - old status
IT_INSERT_LIST Notice - new
IT_UPDATE_LIST Notice - changed
IT_DELETE_LIST Notice - deleted
IT_OLD_OBJREL Assigned contract objects of the notice - old status
IT_INSERT_OBJREL Assigned contract objects of the notice - new
IT_UPDATE_OBJREL Assigned contract objects of the notice - changed
IT_DELETE_OBJREL Assigned contract objects of the notice - deleted
When a notice is saved, this method is called exactly once in order to perform its own additional actions.
- GET_BEHAVIOR_CONTEXT (Gets the behavior context of the notice)
Parameters:
IO_OBJECT Reference of the real estate contract
IS_NOTICE Entry to be changed in the table of notices
IT_NOTICE_DB All notices saved on the database (table VICNNT)
CF_CHANGE_NTREASON Allow change of notice reason?
Using this method, you can allow a change of the notice reason for already activated notices. Set the changing parameter CF_CHANGE_NTREASON = 'X'.
Within this method, it is imperative that you do not issue a message directly using MESSAGE (without addition of RAISING ERROR), nor are you allowed to use the COMMIT WORK and ROLLBACK WORK statements, since this could cause data inconsistencies.
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired 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 | 20110802 |
| SAP Release Created in | 606 |
