BP BAPIs and Geocoding:M_TAB_GEOOBJECTS not clearedon commit
[address] [ADDR_CONTAINER_SAVE] [BAPI_BUPA_ADDRESS_CHANGE] [BAPI_TRANSACTION_COMMIT] [CL_GEOOBJ_CAM_PERSIST_SERVICE] [geocoding] [IF_AES_MEMORY_SAVE~MEMORY_SAVE] [m_tab_geoobjects] [Partner]
Symptom
When an external application tries to change an address using BAPI_BUPA_ADDRESS_CHANGE, an entry is added to the table m_tab_geoobjects. If several addresses are changed, the table keeps on growing. Ideally it should have been cleared on COMMIT when we execute BAPI_TRANSACTION_COMMIT.
Other terms
BAPI_TRANSACTION_COMMIT BAPI_BUPA_ADDRESS_CHANGE m_tab_geoobjects IF_AES_MEMORY_SAVE~MEMORY_SAVE ADDR_CONTAINER_SAVE CL_GEOOBJ_CAM_PERSIST_SERVICE geocoding address partner
Reason and Prerequisites
On COMMIT,the [...]