Symptom
When purchasing info record general text is updated via ME12, no change pointer is written to BDCP2 for message type INFREC, despite change pointer configuration; change pointers for standard fields are created, but not for texts.
Environment
- Materials Management (MM)
- SAP R/3
- SAP R/3 Enterprise 4.7
- SAP ERP Core Component
- SAP ERP
- SAP enhancement package for SAP ERP
- SAP enhancement package for SAP ERP, version for SAP HANA
- SAP S/4 HANA
Reproducing the Issue
- Start transaction ME12 and enter the selection parameters for a purchasing info record.
- Open the General Data tab.
- Choose Goto > Texts and update the info record note text.
- Save the changes.
- Check table BDCP2 and observe that no entry exists for message type INFREC related to the text change.
Cause
- Side effect caused by implementing pilot SAP Note 2624902, which prevents writing change pointers for info record texts.
Resolution
- Verify whether SAP Note 2624902 is implemented in the system.
- De-implement SAP Note 2624902.
- Implement SAP Note 2476093.
- Re-test by changing the purchasing info record general text in ME12, save, and verify that BDCP2 contains a change pointer for message type INFREC.
See Also
- refer to: 2476093 - ME12: INCLUDE text being added in the SAPSCRIPT editor will not be saved
- refer to: 2624902 - ME12: INCLUDE Texts not saved
- refer to: 1720404 - No change pointers created for purchasing documents
- refer to: 2863595 - Change pointers not processed for message type INFREC
- refer to: 422707 - Consulting: Change pointers for purchasing documents
Keywords
ME12, info record text, general text, change pointer, BDCP2, INFREC, INFOSATZ, AT*, not created, purchasing info record, change documents, EINA, EINE, MM-PUR , KBA , MM-PUR-GF-TEXT , Texts , Problem
Product
SAP S/4HANA Cloud Public Edition all versions
SAP Knowledge Base Article - Public