Hierarchy

⤷

⤷

IMG Activity
ID | /SAPCND/MNT_CHECK | BAdI: Maintenance Authorization |
Transaction Code | /SAPCND/68000635 | Impl. for /SAPCND/MNT_CHECK |
Created on | 20021122 | |
Customizing Attributes | /SAPCND/MNT_CHECK | BAdI: Maintenance Authorization |
Customizing Activity | /SAPCND/MNT_CHECK | BAdI: Maintenance Authorization |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /SAPCND/MNT_CHECK |
Use
You can permit one or more implemetaions to reject maintenance authorization for condition records in the current system (because for example the condition record comes from R/3) and require that R/3 compatibility exists.
Requirements
Implementation of methods is called within condition maintenance. Maintenance authorization is given before the first call, and R/3 compatibility denied.
Standard settings
Implementation has already been carried out by SAP, and implemented by the exchange of condition technique objects.
Activities
No acitivities required by the customer.
Ensure that a multiple implementation can be provided when making implementations on behalf of SAP. The parameter that controls maintenance authorization and compatibility is CHANGING. If there is no maintenance authorization, and if R/3 compatibility is requested as a result of an implementation, this may not be overwritten by another implementation.
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 | /SAPCND/MNT_CHECK | 0 | PFC0000016 | Condition Technique |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20021122 |
SAP Release Created in | 400 |