Skip to Content
0

No batch input data for screen SAPMF02D 0230

Jan 17, 2017 at 09:55 AM

230

avatar image
Former Member

Hello guys,

we have created a custom report which creates customers by batch input. This works fine in our default company codes. But we have one company code where the handling is difficult. The batch input session canot be runned automatically in background because we always get the error message 'No batch input data for screen SAPMF02D 0230'.

The message is right, because in our dynpros we do not deliver dynpro 0230. But we do not understand why SAP needs ist? Dynpro 0230 is called Insurance. We do not use this dynpro tab and if we create a customer in foreground, there is no problem and the dnypro is not visible because it is deactivated in the field status groups for customers. So why is it needed in background and why only for this company code? Is there any customizing checkbox for insurance?

Any idea?

Regards
Michael

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

6 Answers

Jürgen L
Jan 17, 2017 at 10:06 AM
0

Are you in an old system where this OSS note is not yet implemented: 802008 - ALE: Extend a customer to a new company code fails

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Jan 17, 2017 at 10:18 AM
0

No, we use newer system ECC 6.

The customer also does not get created by IDOC but with batch input session Recording of transaction FD01.

Share
10 |10000 characters needed characters left characters exceeded
Pablo Casamayor Jan 17, 2017 at 03:01 PM
0

Hi,

if we search in the OSS for "No batch input data for screen SAPMF02D 0230" we get these notes:

Version 2 from 08.08.2014

1989123 - Enhancement buttons not available in the Application Bar

Version 2 from 31.07.2015

2161953 - Incorrect display of inactive pushbuttons in customer master data screens

Version 2 from 20.12.2016

2404306 - GUID definition error for SAPMF02D

Best regards,

Pablo

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Jan 19, 2017 at 02:26 PM
0

Hey,

we found out what was the reason for the different company code handling. It was an internal problem in our custom report. We also found out the problem with dynpro 0230 but we do not understand why.

Explanation: We used SM35 transaction recording with transaction FD01 for our batch input program which creates customers. In our field status of customer branch data the tab 'Insurance' (dynpro 0230) is invisible. When creating a customer in foreground we do not see the tab 'Inscurance' due to the invisible field status, but when recording the transaction with SM35 we get guided through dynpro 0230 as well. Why is there a difference between background and foreground?

Regards
Michael

Share
10 |10000 characters needed characters left characters exceeded
Jürgen L
Jan 19, 2017 at 02:46 PM
0

I know about some old OSS note (e.g. 121781) where SAP is just saying that even screens with no input field have to be taken into account in background processes. Unfortunately they did not say why. But why did you use an own recording? I initially assumed you are using SAP's standard batch input RFBIDE00

Share
10 |10000 characters needed characters left characters exceeded
Chaouki AKIR Jan 19, 2017 at 07:28 PM
0

May be you can try to debug your job in background from sm37 using the "JDBG" okcode technique. An old discussion related to this technique introduces a note : 573128 - Debugging programs in the background.

Share
10 |10000 characters needed characters left characters exceeded