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

issue with FM HR_MAINTAIN_MASTERDATA

Former Member
0 Likes
358

Hello,

I'm using FM HR_MAINTAIN_MASTERDATA to update an infotype(specific infotype 9nnn). the PBO of this infotype default values for some fields : example : field1 = 2000

The issue is that when I try to run the FM with another value for this field field1= 3000 for example, it's not done, the field is created with the defaulted value 2000.

Could you please help?

Best regards,

K

Hello,

I'm using FM HR_MAINTAIN_MASTERDATA to update an infotype(specific infotype 9nnn). the PBO of this infotype default values for some fields : example : field1 = 2000

The issue is that when I try to run the FM with another value for this field field1= 3000 for example, it's not done, the field is created with the defaulted value 2000.

Could you please help?

Best regards,

K

1 REPLY 1
Read only

Former Member
0 Likes
317

From the functional standpoint, the business logic to default value '3000' should be coded within the PBO of custom infotype(9xxxx). The logic that currently defaults '2000' should be enhanced to default '3000' whenever it becomes applicable. If for some requirement you have to pass '3000' from the FM, the same should happen if someone maintains the infotype in a dialog mode i.e. via PA30 for example. The user must not be asked to first remove '2000' defaulted by PBO and then enter '3000' in it's place. If the business logic demands the value '3000', the same should be defaulted by PBO.

Here the idea is to keep things uniform whether the infprtype is maintained Programatically(FM) or in Dialog.

Thanks.