Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Create customer infotype in decoupled framework

Former Member

‎2007 Mar 12 4:48 AM

0 Likes
576

Hi,

I'm developing a customer infotype on ECC 6.00. SAP advises that the new method (de-coupling) should be used when creating new infotypes.

I've referenced the online help on UI Programming Guidelines for Infotypes and they mention that <i>the infotype-specific business logic for decoupled infotypes is programmed in ABAP Objects classes instead of in the module pool</i>.

I’ve implemented the methods of the check and conversion classes. When I test the UI via /PUIT_UI I can see the effect e.g. disabled field input etc. However, when I create a new infotype record via PA30, these changes are not reflected at all. The break-points in the UI methods are not even reached!

Do the methods of the generated conversion and checks classes replace the functionality of PBO and PAI? For example, does method FILL_HELP_VALUES replace PROCESS ON VALUE-REQUEST? When creating the infotype via PM01 the Module Pool is created as before. Should all the checks be programmed in the check class instead of the Module Pool? As far as I can deduct this should be the case but as mentioned earlier these changes are not reflected. Please advise.

I’ve referenced the online documentation (http://help.sap.com/saphelp_erp2005vp/helpdata/en/4f/d52552575e11d189270000e8322f96/frameset.htm ) for decoupled infotypes but there still seems to be a missing link somewhere.

I would appreciate any input in this regard.

Thank you.

Liza-Marie

Hi,

I'm developing a customer infotype on ECC 6.00. SAP advises that the new method (de-coupling) should be used when creating new infotypes.

I've referenced the online help on UI Programming Guidelines for Infotypes and they mention that <i>the infotype-specific business logic for decoupled infotypes is programmed in ABAP Objects classes instead of in the module pool</i>.

I’ve implemented the methods of the check and conversion classes. When I test the UI via /PUIT_UI I can see the effect e.g. disabled field input etc. However, when I create a new infotype record via PA30, these changes are not reflected at all. The break-points in the UI methods are not even reached!

Do the methods of the generated conversion and checks classes replace the functionality of PBO and PAI? For example, does method FILL_HELP_VALUES replace PROCESS ON VALUE-REQUEST? When creating the infotype via PM01 the Module Pool is created as before. Should all the checks be programmed in the check class instead of the Module Pool? As far as I can deduct this should be the case but as mentioned earlier these changes are not reflected. Please advise.

I’ve referenced the online documentation (http://help.sap.com/saphelp_erp2005vp/helpdata/en/4f/d52552575e11d189270000e8322f96/frameset.htm ) for decoupled infotypes but there still seems to be a missing link somewhere.

I would appreciate any input in this regard.

Thank you.

Liza-Marie

Reply
1 REPLY 1
Read only

Former Member

‎2009 Oct 29 7:44 AM

0 Likes
422

Hi Liza,

I have similar problem.I have enhanced standard country specific infotype through PM01 and the field is reflecting in PA30 screen but when i enter some value in it and save it is not updating in the data base.

Do i need to include any code in BADI hrpad00inftybl to save it .

Please suggest ASAP.

Thanks

Deepthi