Field of structures to create BO WebIntelligence report

[Former Member]

Hello friends, greetings to all. I write here because I have a great doubt about MM fields that come in transaction ME2L.I am developing a report in WebIntelligence and I am taking the fields that are presented to me when running the transaction. My problem is that there are some fields that are determined from structures that are created in standard programs. In my case to elaborate my DB, I had to generate some infosets from the ERP (SQ02), to manage them in the IDT (Information Design Tool) because in BO can not be used structures to take the fields. I hope someone can explain how to generate the fields or calculations for use in the report and generate it. I'll comment the fields below:

Historial de pedido - Order history - ICON_PO_HIST
Cantidad Previa Pendiente - Pending Previous Quantity - OFZMG
Por entregar (cantidad) - To be delivered (quantity) - MGLIEF
Por entregar (valor) - To be delivered (value) - WTLIEF
Por calcular (cantidad) - To calculate (quantity) - MGINV
Por calcular (valor) - To calculate (value) - WTINV

Thanks for the help.

[JL23]

Your translation is not correct, you should have logon in English to see the right translation, also selecting the column header and F1 would give an explanation on the meaning.

Historial de pedido - Order history - ICON_PO_HIST --> this field has an icon in case you display the purchase order history

Cantidad Previa Pendiente - Pending Previous Quantity - OFZMG --> the right term is "Open Target Quantity in the Case of Outline Agreements"

Por entregar (cantidad) - To be delivered (quantity) - MGLIEF --> the right term is Still to be Delivered (Quantity)

Por entregar (valor) - To be delivered (value) - WTLIEF --> the right term is Still to be Delivered (Value)

Por calcular (cantidad) - To calculate (quantity) - MGINV --> Still to be Invoiced (Quantity)

Por calcular (valor) - To calculate (value) - WTINV --> Still to be Invoiced (Value)

One PO item can have a single or several receipts till it is fulfilled, same for invoices. A structure is used because this information is calculated by an ABAP logic during runtime of the report. Based on the order quantity and value from EKPO table minus the already received quantities and values (considering also cancellations) from one or more entries in table EKBE. Also considered will be the complete delivery indicator which can be set automatically if the received quantity is in the delivery tolerances or it can be set manually before the ordered quantity is reached. But once it is set it is completed even the ordered quantity is not reached.

[Former Member]

Thank you very much for the explanation Jürgen. Let me investigate a few more about the fields. Do you know something else about how i can do the calculations (the fields that i must use)?

Thanks.

[TammyPowlas]

Easy answer is to do download ME2L to Excel and thing bring that into Web Intelligence - but that's not the ideal way

Why not recreate the calculations in SQ00 against SAP transparent tables instead of looking at using the logical database? Then you can create an ECC universe against this SAP Query

[Former Member]

Hi Tammy, thanks for your answer. I created the universe, using the tables (EKET, EKKO, EKPO, EBAN, EKBE, T163Y) of the transaction. The problem is that the comented fields are only availables from structures and i don't have idea what must look to recreate the calculations.

Do you have another suggestion? Thank you very much for the help.