Description

When running a script in ME22N a user receives an error message in the Log Column such as "[field name] is not an input field", "[field name] does not exist in the screen [screen name]".

As as example:

Applies to

All versions of Transaction, including Studio.

Cause

When the first record in an ME22N script is ran, it begins in Display Mode with the Header and Item Overview sections expanded. On all subsequent records, they begin in Change Mode, but the Header and Item Overview sections are collapsed, leading to errors.

Solution

Scenario 1: Change data in the Item Overview section.

Solution: Utilize the Filter button to isolate a specific item to change.  Click on the arrow button to move Item to the Filter Criteria section.  Click on the filter button and enter in the Item number.  This will show the Item Overview section with only that material.  Update the data and click on save.

Scenario 2: Change data in the Item Detail section.

Solution: Utilize the Filter button to isolate a specific item to change.  Click on the arrow button to move Item to the Filter Criteria section.  Click on the filter button and enter in the Item number.  This will show the Item Overview section with only that material.  Highlight the first row which is the filtered material.  Click on the detail button.  If the detail button is not used the script could change data for the wrong item especially if a loop is used.  Click on tab and change data.  Hit save.

Scenario 3:  Disable all the BDC cursors in the mapper.  This will cause errors on subsequent rows when processing.

Solution: When recording the script, the BDC_CURSOR MEPO1226-ZTERM is included.  This is fine for the initial run of the script but causes issues for all other data rows (see error under Description).
 
Make sure that this line is disabled prior to running the script.

Additional Information

1:   A loop can be used for the scenarios above but is not necessary.

2.  Place an IF First Transaction condition around the screen that changes the PO from Display to Change.  Look for the screen that contains the OK code =METOGG

3.  Place an IF NOT First Transaction condition around the screen that Expands/Collapses the Item Overview section.  This may not be in the mapper so it will have to be manually added.  When the script runs, after the first transaction row, it will collapse the Item Overview section.  This is why the IF condition is needed.  Add screen SAPLMEGUI-0014 with OK code =MEV4001BUTTON. The same steps may be required to open the Header section as well. OK code =MEV4000BUTTON should be used in that instance and would also require being placed inside an IF NOT First Transaction condition.