cancel
Showing results for 
Search instead for 
Did you mean: 

MI31 Inventory: Max. number of selected materials

Former Member
0 Kudos

Hello,

we are actually working on the selection of physical inventory documents (transaction MI31).

When we select all materials of a plant (by only selecting the plant and leaving the material fields empty) the transaction works fine.

But when we select one or a few range of materials, the programm creates a short dump:

016060

016070

016080 * Read all materials (MARD, MARA) for this plant

016090 select (l_t_mchb_fields)

016100 into corresponding fields of table l_1200_t_mchb_lean

016110 from MCHB as a

016120 join mara as b

016130 on amatnr = bmatnr

016140 where a~matnr in l_t_matnr_ra and

016150 a~werks = l_s_aux_param-werks and "only 1

016160 a~lgort in l_t_lgort_ra and

016170 b~MTART in l_t_mtart_ra and

016180 b~matkl in l_t_matkl_ra and

016190 ( b~attyp in l_t_attyp_ra or "EXLUDE!!

016200 b~attyp is NULL ) and

> (l_t_mchb_dyn_cond).

016220

016230 if sy-subrc is initial.

016240 * fill keys for further database selection MARC, MCHA, and MCH1

016250 loop at l_1200_t_mchb_lean assigning <S_MCHB_LEAN>.

This interruption must be caused by the number of material in the selection (in line 016210).

Does anyone have an idea how many materials can be selected at the most at the same time in order to avoid the interruption of the program?

Thanks and Regards

Peter

Accepted Solutions (0)

Answers (2)

Answers (2)

JL23
Active Contributor
0 Kudos

did you "load" the numbers of the materials via multiple selection?

multiple selection has a restriction of bytes, dependend on your material number length you may be limited to a certain amount of materials.

Former Member
0 Kudos

Hi,

Please check the dump by going in trans :st22.

You will to come to know exact problem.

Regards,

Joginder