cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP Process Control 12.0 SP5. V1200 issue with two same fields in data source configurable scenario

Pawel_Kuriata
Discoverer
0 Kudos
145

Hi everyone,

I have strange issue with Process Control 12.0 SP5, V1200.
During Data Source creation we have to define table fields. I want to join RBKP, RSEG and EKPO and compare fields RSEG-WRBTR with EKPO-NETWR. But it is necessary to add also fields RBKP-WAERS (to add RSEG-WRBTR) and EKKO-WAERS (to add EKPO-NETWR). When I tried to execute ad-hoc query dump occurred 🙂
During program debugging I verified that:
1. when data source contain one field type (one WAERS), program analyse just field name, but
2. when data source contain two field type (two WAERS from RBKP and EKKO tables), program analyse ALL WAERS FIELDS from ALL tables including RSEG, where field WAERS doesn't exist.
During SAP Knowledge Base Search I found out few notes witch program correction for that issue but... I have SP5, V1200 and all programs corrections already exist.
So, do you had similar issue or know how to fix it?
Maybe my understanding of Data Source, Configurable scenario is wrong? I defined belows join condition:
1. RBKP-BELNR to RSEG-BELNR
2. RSEG-EBELN to EKPO-EBELN
3. EKPO-EBELN to EKKO-EBELN
and belows fields:
1. RSEG-EBELN
2. RSEG-BELNR
3. RBKP-WAERS (must have to add WRBTR)
4. RSEG-WRBTR
5. EKKO-WAERS (must have to add NETWR)
6. EKPO-NETWR
Without one WAERS field, ad hoc query works fine, but error (dump) occurred with two WAERS fields. Any snotes describing problems with two WAERS fields already implemented...

Few words describing ABAP program in that case.
In one method we have check if field exists in table, if not dump occured. (code line: read table me->attributes->* into attribute_info with table key name=lv_name)
With just one field in data source (WAERS), program checks only field name lv_name=WAERS and everything works fine. With two same fields (two WAERS), program checks field name with reference to table lv_name=RBKP_WAERS problem is - field is checking not only in RBKP_WAERS but also in RSEG_WAERS where column WAERS does not exist.

Accepted Solutions (0)

Answers (0)