Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX-SR (Application Component) Sales-Based Rent and Settlement⤷
RE_SR_BC (Package) RE: Posting Costs
IMG Activity
| ID | BADI_RESR_POSTING | Implement Enhancements (BAdI): Prevent the Posting of Sales-Based Rent |
| Transaction Code | S_EE6_85000029 | (empty) |
| Created on | 20100714 | |
| Customizing Attributes | BADI_RESR_POSTING | Prevent the Posting of Sales-Based Rent |
| Customizing Activity | BADI_RESR_POSTING | Prevent the Posting of Sales-Based Rent |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_RESR_POSTING |
Use
Example 1
The BAdI makes it possible for you to prevent the posting of the results of a sales-based settlement. This is required especially when legacy data for sales-based settlements is to be transferred to the system. In this case, it is necessary that you execute sales-based settlements,which were posted in the legacy system, again in the SAP system. The results are needed, for example, to be able to post accumulated settlements or corrections due to certified sales at the end of the year. However, you do not want to post to financial accounting, since these postings were already made in the legacy system before the go-live date.
If, in the case that the end of the settlement period is before the date of the first posting, you do not want create any postings in the sales-based settlement, create an implementation for BADI_RESR_POSTING. You can use the example class CL_EXM_RESR_NO_POSTING as an example (take note of the comments in the sample code). Do not forget to activate the implementation.
Example 2
You have designated a real estate contract as 'relevant for sales'. The calculation object and possibly the distribution object are not valid in the entire period of the sales-based rent condition, but sales were also reported for this period. During the sales-based settlement, no distribution postings are made after the validity of the object assignment, but a receivables posting is made.
If you do both of the following, no receivable posting is made:
- Issue the message RESRBC 013 (control using transaction OBA5)
- Implement the method NO_POSTING so that the RETURNING parameter EF_DO_NOT_POST = 'X' is set
. The log contains a corresponding message.
If you issue the message as a warning, the step is designated as 'incomplete'. If you issue the message as a status or information message, then the posting step is designated as 'not required'. In that case, the settlement is also complete without the posting being executed.
There is an example implementation for this example situation in the class CL_EXM_IM_RESR_POSTING.
Requirements
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 153 | Design enhancements |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 1 | 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 | BADI_RESR_POSTING | 0 | ALN0000044 | Sales-Based Rent and Settlement |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20101011 |
| SAP Release Created in | 606 |
