Decoupled Infotype - Correct Buffer Access for PA30 and from BAPI?

Question

Weu2019ve created a custom decoupled infotype and read/delete/update/insert work just fine with PA30, but the same methods supplied with the corresponding Check class do not work when called from a program.  The Check class inherits from CL_HRPA_INFOTYPE_NNNN.  After going through some documentation, we made the Check class inherit from CL_HRPA_INFTY_NNNN and now the modify method works if we redefine the modify method to use the direct buffer update methods from IF_HRPA_MASTERDATA_BUFFER (implementation in CL_HRPA_MASTERDATA_BUFFER). But then, PA30 stops working and throws an exception - u201CInfotype does not support legacy accessu201D.
Anyone know why the SAP generated infotype check class methods not work when called as it is? There are no error messages thrown and no messages returned in the message handler too. Just that the database does not get updated. The Read method always works for all cases though. Help documentation is clear about the risks and differences between the two buffer access methods but issues exist when using PA30 and when trying to access/update the buffer from a program or BAPI.

Answer 1

Since you are adopting an approach per [SAP help|http://help.sap.com/saphelp_erp2005/helpdata/en/43/21d2254bba2bebe10000000a1553f7/frameset.htm], I guess only SAP can help. May be you should try your luck by opening a Customer message (i.e. if you haven't already done so).
~Suresh