Error with TCODE FM_FUNCTION and LSMW

[former_member562097]

Hi, team!

Can you help me with tcode FM_FUNCTION and LSMW recording?

I want create LSMW with this tcode to create many Function Areas, but can't to do... something is wrong with screens.

Or how can we create Function Area massive? Error code display is "No batchinput data for dynpro SAPLBUSS 2500" Message number no. 00344.

Waiting for your reply...

Please help me)

Thanks.

Best regards.

Cristina

[Sandra_Rossi]

The issue is due to the content of the SET/GET Parameter FBE, which fills the screen field "Functional Area" when the transaction FM_FUNCTION is started.

• If FBE contains a non-existing Functional Area code (empty for instance), the screen SAPLBUSS 5024 is displayed first, showing empty Functional Area details. If the user clicks one of the buttons Create, Change or Display, the entered Functional Area code is stored in FBE and the screen SAPLBUSS 2500 is displayed to show or enter the Functional Area details. The two screens SAPLBUSS 5024 and SAPLBUSS 2500 look identical.
• If FBE contains an existing Functional Area code, the screen SAPLBUSS 2500 is displayed immediately. If the user clicks one of the buttons Create, Change or Display, the screen SAPLBUSS 2500 is displayed again to show or enter the Functional Area details.

It's a problem if you have one Batch Input session (via LSMW or not) or CALL TRANSACTION USING, which creates a Functional Area with the screens SAPLBUSS 5024 and SAPLBUSS 2500, and if you create two or more Functional Areas sequentially:

• The first call works because FBE is blank
• The second and next calls fail because FBE is no more blank, the first displayed screen is SAPLBUSS 2500 but the screen defined in the Batch Input data is SAPLBUSS 5024, so the Batch Input fails.

The workaround to have only one transaction per session is not

Another workaround is to develop a program (see below) which initializes the SET/GET Parameter FBE with an EXISTING Functional Area code and calls the transaction FM_FUNCTION. Record the Batch Input data on the transaction SE38, call the program and create one functional area. Now run your Batch Input, it should work.

ABAP code:

REPORT ZZZ.
" 0001 is an existing functional area
SET PARAMETER ID 'FBE' FIELD '0001'.
CALL TRANSACTION 'FM_FUNCTION'.

Good luck!