Solution : https://service.sap.com/sap/support/notes/664928 (SAP Service marketplace login required)
Summary :
This SAP Note addresses common questions related to version management within SAP systems, particularly focusing on purchasing documents such as purchase requisitions and orders. Key queries include issues with version generation after modifications, the lack of new versions following text changes, and operational concerns such as the impact on goods receipt postings when versions are incomplete. Conditions for setting a version to 'In process' are explored, along with details on certain field functionalities like EREV-BUDAT. The note emphasizes system behaviors and configuration tips to handle versioning correctly, ensuring users understand when and how versions are produced or influenced.
Key words :
frequently asked questions/answers, -> version management -> version-relevant fields, message screen displays status 2, contract scheduling agreement, method if_revision_manager_dcm~create_item, terms answer dcm, erev-budat field, required entry field, final processing state, -> messages -> fields relevant
Related Notes :
| 748493 | ME52NB: Icon for "Attachments" is visible |
| 642096 | DCM setting version in process, generating new version |
| 635811 | DCM ME21N Holding purchase order, no version created |
| 632482 | DCM Changing net order value, reset release strategy |
| 631999 | ME52N: Text changes do not generate new version |
| 620850 | DCM: Change of doc. type/purchasing org. causes short dump |
| 616644 | DCM release determination if version in process |
| 612234 | DCM: Customizing for change displays not taken into account |
| 605263 | DCM: Activation of the "Buyer approval" function |
| 603444 | DCM: PReq via ME_REQUISITION_EXT, no release strategy |
| 358680 | MEPO: Missing data in the print preview |