SAP ABAP IMG Activity ME_CHDOC_ACTIVE (BAdI: Activate Additional Updating in Change Documents)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
SRM-EBP (Application Component) Enterprise Buyer
⤷
BBP_APPLICATION (Package) Structure Package EBP
⤷
ME (Package) Application development R/3 Purchasing

⤷

⤷

⤷

IMG Activity
ID | ME_CHDOC_ACTIVE | BAdI: Activate Additional Updating in Change Documents |
Transaction Code | S_AL0_96000473 | (empty) |
Created on | 20011129 | |
Customizing Attributes | ME_CHDOC_ACTIVE | BAdI: Activate Additional Updating in Change Documents |
Customizing Activity | ME_CHDOC_ACTIVE | BAdI: Activate Additional Updating in Change Documents |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ME_CHDOC_ACTIVE |
Use
Application component: MM-PUR
The Business Add-In (BAdI) ME_CHDOC_ACTIVE enables you to specify whether changes to the following data are to be documented by means of change documents in Purchasing:
- Document conditions (for external purchasing documents only)
Changes to conditions in purchasing documents and in External Services Management are documented via the additional table KONVC within the change objects EINKBELEG and MM_SERVICE. - Linkages to Document Management System (DMS) documents (for external purchasing documents and purchase requisitions)
The generation or deletion of a linkage to a DMS document is documented via the new change object EINKDOKUMENT. - Subcontracting components (for external purchasing documents and purchase requisitions)
Changes in the subcontracting components in Purchasing are documented via the new change object MDSB. - Export/import data (for purchasing documents)
Changes to the export/import data are documented via the new change object EXPIMPBELEG.
If change documents exist, you can display the changes in the relevant change or display transaction for the external purchasing document or the requisition.
Requirements
If the system is to document the generation or deletion of the linkage to a DMS document, you must specify in Customizing for Document Management under Control Data -> Define Document Types that a change document is written for the relevant DMS document type.
Standard settings
- The BAdI is not active in the standard system.
- The BAdI is not filter-dependent.
- The BAdI cannot be used multiple times.
Activities
Example
You will find an example implementation under Goto -> Code Example.
In this example, all the above changes are documented.
Further notes
Business Attributes
ASAP Roadmap ID | 153 | Design enhancements |
Mandatory / Optional | 3 | Nonrequired 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 | ME_CHDOC_ACTIVE | 0 | HLA0009512 | Purchasing |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050718 |
SAP Release Created in | 470 |