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

Problem with HR_MAINTAIN_MASTERDATA delimiting infotypes

Former Member

‎2007 Nov 26 9:28 PM

0 Likes
786

hi,

I'm trying to delimit a register of the infotype 0017 using the FM

HR_MAINTAIN_MASTERDATA because i had to execute a infogroup (like the PA40

transaction) this is the call:

CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'

EXPORTING

pernr = gwa_data-pernr

massn = 'A9'

actio = 'INSS'

tclas = 'A'

begda = gwa_data-begda

endda = gwa_data-endda

werks = gwa_data-persa

persg = gwa_data-persg

persk = gwa_data-persk

plans = gwa_data-plans

dialog_mode = '2'

  • NO_EXISTENCE_CHECK = 'X'

TABLES

proposed_values = ltd_valprop.

The customizing of the T588D (Infogroups for Actions) table is:

ITYGR     ACTIO        INFTY
   A9     COP           0001
   A9     INS           0015
   A9     LIS9          0017

When I execute the FM first it creates the 0000 infotype, then the copy of the

001 and the new 0015, but when gets to the infotype 0017, it is not showed!

(i mean skips the infotype 0017, notice the 0017 register in the table has the LIS9 action), i thought this FM works like the PA40

transaction, reading the T588D table and appliaying the corresponding action

to each infotype, but this is not working. Any help will be very grateful.

Greetings,

Felipe.

hi,

I'm trying to delimit a register of the infotype 0017 using the FM

HR_MAINTAIN_MASTERDATA because i had to execute a infogroup (like the PA40

transaction) this is the call:

CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'

EXPORTING

pernr = gwa_data-pernr

massn = 'A9'

actio = 'INSS'

tclas = 'A'

begda = gwa_data-begda

endda = gwa_data-endda

werks = gwa_data-persa

persg = gwa_data-persg

persk = gwa_data-persk

plans = gwa_data-plans

dialog_mode = '2'

  • NO_EXISTENCE_CHECK = 'X'

TABLES

proposed_values = ltd_valprop.

The customizing of the T588D (Infogroups for Actions) table is:

ITYGR     ACTIO        INFTY
   A9     COP           0001
   A9     INS           0015
   A9     LIS9          0017

When I execute the FM first it creates the 0000 infotype, then the copy of the

001 and the new 0015, but when gets to the infotype 0017, it is not showed!

(i mean skips the infotype 0017, notice the 0017 register in the table has the LIS9 action), i thought this FM works like the PA40

transaction, reading the T588D table and appliaying the corresponding action

to each infotype, but this is not working. Any help will be very grateful.

Greetings,

Felipe.

Reply
1 REPLY 1
Read only

Former Member

‎2007 Nov 27 8:24 AM

0 Likes
451

Hi Felipe ,

can u tell me what fields+values u are passing to this FM , bcos when i try this FM it wll goes to infotype 17 without passing any screen fields to this FM.

And Better to Add Return tables to this FM , then u wll get some idea.

Regards

Peram