Supply Chain Management Blog Posts by Members
cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
250

Introduction:

Recently, I received a simple but interesting requirement from our client:
They wanted to mass change the Issuing Storage Location (RESLO) in Stock Transport Orders  ME21N/ME22N transactions.

At first glance, this seemed like a quick win using SAP's Fast Change functionality. However, I soon realized that the standard SAP system does not support fast change for some fields, including RESLO.

Initial Investigation:

I initially thought of using a BAdI to default the issuing storage location automatically as per business logic. But before going that route, I wanted to understand why SAP does not allow Fast Change for certain fields, especially since RESLO is a part of structure MEPOITEM (Purchase Order Item).

Root Cause Analysis:

After a bit of debugging and research, I discovered that, SAP internally uses a data type called MEGUI_MASSCH_ALLOWED_FIELDS.

This structure defines which fields in the MEPOITEM structure can be used in the Fast Change functionality

When comparing MEPOITEM with MEGUI_MASSCH_ALLOWED_FIELDS, it's clear that many fields (including RESLO) are simply not included — which is exactly why Fast Change isn’t available for them by default.

Solution:

To enable Fast Change for a field like RESLO, follow these steps:

1. Enhance the structure MEGUI_MASSCH_ALLOWED_FIELDS by Appending the desired field from MEPOITEM (e.g., RESLO)

kannanchokkanathan1_0-1750334446152.png

2. After making the change, execute the report in SE38 - BALVBUFDEL, this clears the ALV buffer so that the Fast Change UI picks up your added fields.

kannanchokkanathan1_2-1750334614010.png

kannanchokkanathan1_1-1750334566213.png

Reference:

SAP Note: 2124015 - Fast Change: fields that can/cannot be changed in ME21N and ME22N

Takeaway:

SAP's Fast Change is a powerful tool — but it’s limited to fields listed in MEGUI_MASSCH_ALLOWED_FIELDS. If your required field isn’t there, don’t jump directly to customer exit or BAdIs. Instead, first check this structure — you might only need to append one field and refresh the buffer to meet the business requirement.

Regards,

Kannan Chokkanathan