Коллеги, всем доброго времени суток!

может кто сталкивался... формируем отчет "Обзор запасов (Россия)" за прошедший месяц по запасам СПП элемента по неликвидам.
Возникает дамп, думаем возможно ли решить без обращения в САП...
Из ST22
Категория Программная ошибка ABAP
ДинамОшибка GETWA_NOT_ASSIGNED
АВАР-прогр. J_3RMOBVED
Прикладной компонент MM
Дата и время 02.11.2020 11:43:15

Краткий текст
Field symbol has not been assigned yet.

Что произошло?
Error in the ABAP Application Program
The current ABAP program "J_3RMOBVED" had to be terminated because it has
come across a statement that unfortunately cannot be executed.

Что Вы можете сделать?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.

Анализ ошибки
An attempt was made to access a field symbol that has not been assigned
yet (data segment number "-1").

That error occurs if
- a typed field symbol is addressed before it has been set with ASSIGN,
or
- a field symbol is addressed that points to a row in an internal table
that has been deleted, or
- a field symbol is addressed that was previously reset using UNASSIGN,
or that pointed to a local field that no longer exists, or
- a parameter of a global function interface is address, although the
corresponding function module is not active (is not in the list of
active calls). The list of active calls can be taken from this short
dump.

Указания по устранению ошибки
If the error occurs in a non-modified SAP program, you might be able t
find a solution in the SAP Notes system. If you have access to the SAP
Notes system, check there first using the following keywords:

"GETWA_NOT_ASSIGNED"
"J_3RMOBVED" or J_3RMOBVEDF08
"DOCUMENT_ITEMS_GETTING"
If you cannot solve the problem yourself, please send the following
information to SAP:

1. This description of the problem (short dump)
To do this, choose System -> List -> Save -> Local File (unconverted)
on the screen you are in now.

2. A suitable system log
To do this, call the system log in transaction SM21. Restrict the time
interval to ten minutes before the short dump and five minutes after
it. In the display, choose System -> List -> Save -> Local File
(unconverted).

3. If these are programs of your own, or modified SAP programs: Source
code of these programs
To do this, choose More Utilities -> Upload/Download -> Download in
the Editor.

4. Details regarding the conditions under which the error occurred or
which actions and input caused the error.

SAP Release..... 740
SAP Basis level 0021

Operating system... AIX
Release.............. 7.2
Hardware type....... 00CB28AD4C00
Character length..... 16 Bits
Pointer length........ 64 Bits
Work process number... 58
Shortdump setting. full
Database server... node212
Database type..... ORACLE

Пользователь, транзакция...
Language key.......... R
Transaction......... J3RFLVMOBVED
Transaction ID...... 8B0D0C6BAB6800B0E005F9BF306C1848
EPP whole context ID...... 5AB68E821E061EEB879CDA8DD7B41F78
EPP connection ID........ 00000000000000000000000000000000
EPP call counter......... 0

Program.............. J_3RMOBVED
Screen.............. SAPMSSY0 1000
Screen line.......... 6
Active debugger..... "none"

The termination occurred in ABAP program "J_3RMOBVED", in
"DOCUMENT_ITEMS_GETTING". The main program
was "J_3RMOBVED".

In the source code, the termination point is in line 1594 of (Include)
program "J_3RMOBVEDF08".

Фрагмент исходного текста программы
Строк ИсхднТкст
1564 LOOP AT
1565 lt_mlit_mlc
1566 ASSIGNING
1567 <fs_mlit_mlcrf>
1568 WHERE
1569 matnr = <fs_bsim_bkpf>-matnr
1570 AND bukrs = <fs_bsim_bkpf>-bukrs
1571 AND belnr = lv_belnr_ml
1572 AND kjahr = lv_gjahr_ml
1573 AND bwkey = <fs_bsim_bkpf>-bwkey
1574 AND bwtar = <fs_bsim_bkpf>-bwtar
1575 AND poper = lv_poper
1576 AND fi_found = abap_false.
1577
1578 <fs_mlit_mlcrf>-prdif = abs( <fs_mlit_mlcrf>-prdif ).
1579
1580 CHECK <fs_mlit_mlcrf>-prdif = <fs_bsim_bkpf>-dmbtr.
1581
1582
1583 "BSEG KEY: buzei belnr hkont bwkey bukrs gjahr bwtar ebelp ebeln
1584 "There are no fields Vbeln Posnr and Pspnr in BSIM table
1585 LOOP AT pt_bseg ASSIGNING <fs_bseg>
1586 WHERE buzei = <fs_bsim_bkpf>-buzei
1587 AND belnr = <fs_bsim_bkpf>-belnr
1588 AND bukrs = <fs_bsim_bkpf>-bukrs
1589 AND gjahr = <fs_bsim_bkpf>-gjahr.
1590 EXIT.
1591 ENDLOOP.
1592
1593 "Check Vbeln and Posnr. Cope values from ML to bsim_bkpf and to bseg if emp
>>>>> IF <fs_bseg>-vbel2 IS NOT INITIAL.
1595 CHECK <fs_bseg>-vbel2 = <fs_mlit_mlcrf>-vbeln.
1596 CHECK <fs_bseg>-posn2 = <fs_mlit_mlcrf>-posnr.
1597 ELSE.
1598 <fs_bseg>-vbel2 = <fs_mlit_mlcrf>-vbeln.
1599 <fs_bseg>-posn2 = <fs_mlit_mlcrf>-posnr.
1600 ENDIF.
1601
1602 <fs_bsim_bkpf>-vbel2 = <fs_mlit_mlcrf>-vbeln.
1603 <fs_bsim_bkpf>-posn2 = <fs_mlit_mlcrf>-posnr.
1604
1605 "Check WBS Element. Cope values from ML to bsim_bkpf and to bseg if empty
1606 IF <fs_bseg>-projk IS NOT INITIAL.
1607 CHECK <fs_bseg>-projk = <fs_mlit_mlcrf>-pspnr.
1608 ELSE.
1609 <fs_bseg>-projk = <fs_mlit_mlcrf>-pspnr.
1610 ENDIF.
1611
1612 <fs_bsim_bkpf>-projk = <fs_mlit_mlcrf>-pspnr.
1613

из разговора с прогером стало понятно, что:
это старая проблема, не находятся документы в BSEG.
на строке 1594 Begin of SAP Note 2392907

Если ограничивать выборку номерами ОЗМ, то отчет собирается. Падает как минимум на материале 1000004213.
зачем-то выбираются документы РМ (47*), к материалам в нашем запасе вообще не относятся (другой СПП). движений по материалам в ошибке вообще нет. Ограничивать конкретными ОЗМ не применимо, а запускать отчет в фоне не всегда удобно. правда пару раз отчет формировался без дампа, но почему так никто не понял.

В коде нет проверки, что программа заходила в цикл по pt_bseg. Если без обращения в сап - можно сделать неявный энхансмент в начале подпрограммы, где повторять стандартную логику + проверка что <fs_bseg> Is assigned.