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

HR_INFOTYPE_OPERATION No Batch Input data for screen

Former Member
0 Likes
2,040

Hi everyone,

I have a problem with the function module, and I think I know the problem but I need some confirmation.

I'd like to update the infotype 176 (country specific infotype). But I get the error No Batch Input data for screen MP017600 2000

As I understand the problem here, is that the HR_INFOTYPE_OPERATION uses CALL DIALOG statement to insert the new values, and for this infotype No batch input screens were defined, therefore the whole insert operation ends in an error.

Can you please confirm / correct my idea about this problem?

My second question:

Is there a way to correct this? Can I define these screens? Or only SAP can define it? Is there any other way to insert the record to this infotype ( I can simply insert the record to the PA0176 database table, but this is not a nice solution...)

Thanks

N.

Hi

Whatever you are doing is the right way for updating any infotype. The screens 1000, 2000 and 3000 are generated by SAP whenever you create a infotype. What i would suggest you is,

1) Try creating the IT0176 record for a personnel number using PA30 transaction with the same data which you are trying to use from the program.

2) Check the msgv1...msgv4 parameters of the returned BAPI. Since these infotypes are country specific, there are some settings in tables like V_T588M which can make particular parameter invisible. When you pass the values to these parameters from the FM even then you'll get same message. So, msgv1 ... msgv4 parameters will hold any fieldnames because of which the error might be raised.

Regards

Ranganath

7 REPLIES 7
Read only

Former Member
0 Likes
1,592

Hi

Whatever you are doing is the right way for updating any infotype. The screens 1000, 2000 and 3000 are generated by SAP whenever you create a infotype. What i would suggest you is,

1) Try creating the IT0176 record for a personnel number using PA30 transaction with the same data which you are trying to use from the program.

2) Check the msgv1...msgv4 parameters of the returned BAPI. Since these infotypes are country specific, there are some settings in tables like V_T588M which can make particular parameter invisible. When you pass the values to these parameters from the FM even then you'll get same message. So, msgv1 ... msgv4 parameters will hold any fieldnames because of which the error might be raised.

Regards

Ranganath

Read only

MrWhan
Participant
0 Likes
1,592

In that function try the parameter


        dialog_mode      = '2'

This will make it show the dialogue in the foreground and you may be able to see where the error is.

My second hunch is that you may not be in screen 2000. It might be 20xx depending on the previously mentioned table and country codes. Feature P0176 may also be something to look at.

Read only

Former Member
0 Likes
1,592

Hi everyone,

Thank you for the answers, but unfortunatelly, I'm still facing the issue, and I don't know what is the problem.

I'm familiar with the HR feature-infotype screen concept.

There is a Feature for this infotype P0176 and in the T588M a special screen is definied for this company, where every field is Optional

I also tried the dialog_mode = 2 before, but if I run the FM this way, everything works perfectly. The P0176 infotype comes up with the correct value, and I can save it without any error.

As I wrote in my first comment, The error message (which comes up only when I run it in dialog mode = '0' ) is:

No Batch Input data for screen MP017600 2000

Does anyone has any idea what can be the problem, or how to find it?

Thanks

N.G.

Read only

Former Member
0 Likes
1,592

In the mean time I debugged the whole operation. The problem is that in dialog mode = 0 some optional fields are filled in the customer include ZXPADU01.

Read only

Former Member
0 Likes
1,592

While doing the session with CALL_DIALOG = '2' pls check at the bottom of the screen if the message is raised, sometime it gets overlooked. Also, in addition to optional check, check if any screen field is disabled and you are passing value for that screen field. Even then the error will be raised.

Regards

Ranganath

Read only

Former Member
0 Likes
1,592

The problem was inthe customer include

Read only

0 Likes
1,592

No Batch Input data for screen MP017600 2000 which means that you are passing some extra values to that screen.

Please check it out