Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Problem with Shared Buffers

Former Member
0 Likes
496

Hi SAP Experts,

My development worked fine with shared buffers, but I cannot use that now because the quality and production environments are multi-server. Is there an effective way to move the data?

So far I have two possible solutions: a custom database table to use as a buffer, or writing to a file and then reading it. Please help.

The reason the code worked well in Development Box is that it uses single server. Quality and Production has more than one server and the update task is not guaranteed to happen in the same server as the transaction. That might explain why it updated once(Iu2019m assuming mb1c was open before the change was transported) when bapi_transaction_commit was added.

Your help is greatly appreciated.

Miguel Basora

1 REPLY 1
Read only

Clemenss
Active Contributor
0 Likes
424

Hi Miguel,

you may consider ABAP shared objects using transactional Areas and propagation.

Transactional Areas are specified at design time using transaction SHMA.

Propagation is done via invalidation using the PROPAGATE methods.

data:
  root type ref to zcl_my_area_root,
  hdl type ref to zcl_my_area.
  hdl = zcl_my_area=> attach_for_write( ).
  create object root area handle hdl.
  hdl->set_root( root ).hdl-> detach_commit( ).
  zcl_my_area=> propagate_instance( ).
  commit work.

Regards

Clemens