Automate

Welcome to the Automate community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Here are some useful links where you can find more information:

Product Announcements

Discussions

Members

Resources

Events

 View Only
Back to discussions
Expand all | Collapse all

MM01 Transaction Script Error – "No batch input data for dynpro (SAPLCLFM 1101 Clfy 99...)" during Classification recording via Reference Materia

  • 1.  MM01 Transaction Script Error – "No batch input data for dynpro (SAPLCLFM 1101 Clfy 99...)" during Classification recording via Reference Materia

    Posted 5 hours ago

    Hi Precisely Support Team,

    We're running into a batch input error in a Transaction script built for MM01 (Material Master creation) and would like guidance on the correct fix.

    Environment

    • Product: Precisely Automate Studio (Transaction module)
    • Studio/Evolve/Connect version: [please fill in]
    • SAP system / ECC or S/4HANA version: [please fill in]
    • Transaction: MM01, Classification view

    What we did While recording the script, we used a Reference Material to auto-populate the material, including the Classification view (class and characteristics were copied in automatically from the reference). The only field we manually changed during recording was the Characteristic Value column for one characteristic - everything else was left as copied from the reference.

    Error on playback When we run the script, it fails with:

    No batch input data for dynpro (SAPLCLFM 1101 Clfy 99: From Object, Assign Object to Classes and Classify) SAPLCLFM 1101

    This happens on the Classification screen specifically; the rest of the material master (Basic Data, etc.) processes fine.

    What we suspect Since the classification fields were pre-filled by the reference-material copy rather than typed by us, we suspect the recording may not have captured a mapped step for every occurrence of the SAPLCLFM 1101 screen (e.g., rows we didn't type into), and/or that the number of screen occurrences varies depending on the class/characteristics carried over from the reference material or on whether a characteristic allows multiple values.

    We found a very similar case on the Precisely Community, where the same error (also referencing SAPLCLFM 1101) was resolved with a loop-based classification template (MM01_CreateClassification.xlsx / .Txr) provided by your team: https://community.precisely.com/discussion/no-batch-input-data-found-for-dynpro-saplmgmm-0060-initial-screen-matl-no-industry-sector-matl-type-etc-saplclfm-1101-expected

    What we're asking

    1. Could you confirm whether our scenario (Reference Material copy + editing only the Characteristic Value field) has the same root cause as the thread above, or a different one?
    2. If it's the same issue, could you share the MM01_CreateClassification loop template (or the current equivalent), or point us to documentation on building a loop around the class/characteristic-value screens for MM01?
    3. If it's a different cause, could you advise how the recording should handle screens that get auto-filled from a reference material but still need an explicit mapped step during playback?

    Happy to share our current .Txr and Excel data file if that helps you diagnose faster.

    Regards,

    Surendar



    ------------------------------
    Surendar C
    Vibrantz Corporation
    ------------------------------


  • 2.  RE: MM01 Transaction Script Error – "No batch input data for dynpro (SAPLCLFM 1101 Clfy 99...)" during Classification recording via Reference Materia

    Employee
    Posted 3 hours ago
    Edited by jagat kaushal 2 hours ago

    Hi Surendar C,

    Thank you for your message.

    Please find my answers below to your queries:

    Is your scenario the same root cause as the community thread?

    Yes - your scenario shares the same fundamental root cause, but has an additional contributing factor specific to using a Reference Material.
    The "No Batch Input for Screen" error occurs because the sequence of screens when running a script is different from that of the original recording, and SAP is displaying a screen that either did not appear in the recording or appears in a different place in the sequence. The error means that the script doesn't have any data for the particular screen being processed and therefore the run terminates. 
    There are two specific sub-causes at play in your case:
    Sub-cause 1 - The "first record" popup suppression: When creating or updating a material in MM01/MM02, the Classification tab will display a popup for the first material which is then suppressed for the remaining materials.SAP will remember your choice after picking the classification number and it won't be a choice next time. Classification is one of those oddities where the first time you enter the view, you make a selection. The 2nd time, it remembers the selection you made so the box doesn't pop up. 
    Sub-cause 2 - Auto-filled fields from Reference Material are NOT recorded: When you used a Reference Material to auto-populate the Classification view, the fields were pre-filled by SAP - you never manually typed into them. Automate Studio's transaction recorder only captures keystrokes and interactions you actually perform. Since you only manually changed one Characteristic Value, the script only captured that one interaction on the SAPLCLFM 1101 screen. During playback, SAP may present the full classification screen (with all characteristics) expecting input for every occurrence, but the script has no mapped step for the rows/occurrences you didn't interact with.
    This message can appear in the following scenarios:
    • New Screen: If a new screen is popping up for the current record that didn't exist for the record that was recorded (different screen flows for different data).
    • Missing/Skipped Screen: If the script has a screen recorded that does not appear for certain data - the recording is done with a set of screen flows, but for particular data, one of the screens is not displayed by SAP. 

     Q2 - The MM01_CreateClassification Loop Template

    The loop template referenced in the Community thread is the correct fix for your scenario.
    You can access and download these files directly from the Precisely Community thread:  No batch input data found for dynpro SAPLCLFM 1101 - Precisely Community

    Q3 - How to Handle Auto-Filled Screens from a Reference Material

    Since your reference-material-filled classification fields weren't captured during recording, here is the recommended approach:

    Step-by-Step Fix

    1. Use the loop template as your base: The MM01_CreateClassification.xlsx / .Txr loop template already handles the variable number of SAPLCLFM 1101 screen occurrences (classes and characteristics) via loops, which your recording cannot reliably replicate when fields are auto-filled.
    2. Add the "first record" IF condition: The suggested fix is to add an"If First" (or IF condition on the first record) around the classification number selection step, so the script correctly handles the popup that only appears for the first material. 
    3. Handle the Class Type popup manually if needed: The Class Type popup will only pop up for the first material. After that, the GUI assumes you are going to use the same class type for the next one. You should put an IF statement around the section that deals with the popup - OR - you can force it each time by clicking the "switch class type" button. You can either record it that way, or paste that section into your script that doesn't have the popup. 
    4. Debug step-by-step to identify missing screens: If you see this error, try running in step-by-step mode and stop on each screen to see if you can identify the issue. You can also record the scenario that is generating the error and compare it with the original script. This should illustrate what is processing differently so that you can then edit/modify the existing script to accommodate the new scenario. 
    5. Manually insert missing popup screens if the recorder fails to capture them: If popup screens are not being captured during recording, you can try to manually insert the screens. This approach has been confirmed to fix the problem - adding the steps in manually does resolve the issue. 
    Do you need further guidance on structuring the loop within the Excel data template, or would you like clarification on how to apply the IF condition for the Class Type popup? Feel free to share your current .Txr file for a more targeted review by a support ticket on our support portal .
    Thanks
    jagat kaushal
    *Precisely Software Inc.
    ------------------------------