LSMW in 4.6c: Screen error on field KNA1-BRSCH

[Former Member]

I am stuck on a customer master upload in LSMW - All is set up for a batch input. I have mapped all fields but one is giving me a headache:

I am trying to load field BRSCH in KNA1 - it is a required field for us. When I convert the data and generate the batch input session, the system for some reason creates logic to try to input this particular field on both screens 0120 for and again on screen 0125. It should only do it only on screen 0125 - the field does not exist on screen 0120, thus I get an error.

Where can I edit or control this? I have recreated the mapping several timkes to see if it was afluke, but it does it every time... Any help is appreciated!

[Former Member]

Hi Yves,

Once again check ur Recording and see whether u had recorded for 0120/0125,

if ur recorded particular field twice then put the correct screen field and delete which u dont need and save that recording and continue remaining procedure

Thanks

Naveen khan

[Former Member]

I am not using batch input recording, but rather use the first method "Standard Batch/Direct Input" using Object 50, Method 0000 and program RFBIDE00, Program Type B (Batch Input). So all the screens are generated from the program and I am not finding a way to correct the system's "mistake".

[Former Member]

Are you using the standard program?

[Former Member]

Have you by any chance suppressed that field from the users view in the transaction?

Are you using the auto field mapping functionality in LSMW?

Also, are you running in the foreground or background mode? Does it make a difference if you change the processing mode?

[Former Member]

Indeed the field is suppressed on screen 0120 and displayed on 0125 as required.

I have tried to process using each of the 3 methods, foreground, errors only and background. Same result on each.

Now that I have established that it's a suppressed field on screen 0120, how do I fix it (other then removing the suppression?). I suppose I could make the field not required and not import it since for this load it is a generic entry, but I could not leave it this way as it must be required for the rest of the organizations on the system.

Any ideas?

Not sure what you mean with auto-mapping option - I manually mapped each field from the upload file to the respective customer master field. I do not think I have seen the auto option?

[Former Member]

The easiest solution seems to me to remove the suppression.

Your other solution of making the field not required should work too, but I understand your business requirements.

I am not too familiar with the customer master - but in other areas I have seen user exits employed to check that a field is not null before saving the transaction.

Maybe you could try to make the field not required and then employ a customer exit to check that the field is populated before saving the record. This should work with the business requirement to have this field populated.

Third Option: Try a recording, if you do not have any parent/child relationships then maybe this would work too. It should only pick up fields that are visible to the end user processing the transaction.

FYI - Auto Field Mapping:

I ask this because if you use this option it could be moving your source field into the wrong target field/structure. Auto field mapping is in the Field Mapping and Conversion Rules step in LSMW under the extra's menu.

[Former Member]

Thanks! I have resorted to setting the field to not required for the period of the import and then settig it back to required. Found a few more errors in my coding for other translations, but first job is now running...

Thanks for all the input! I certainly learned a few things!