ABAP does not know which tables to associate when the ALV is retrieved

You need to be clear about what conditions you provide when you do it, and what inputs you will provide.

makt-matnr = mseg-matnr, how do you connect this? It doesn't make much sense to connect them.

You use se16n to go in and check it slowly.

mara-matnr=vbap-matnr, inside vbap, there will be a connection to mara. MSEG, use mara to string, MKPF also uses mara, and makt also uses mara for stringing.

To do a table join, you need to find the header first, find 1 center point, and you can also string the rest later.

...First of all, we need to think about what parts a form consists of. It is mainly composed of the header body and the appendix items.

The header and the body are associated with each other through the master. For example, if you have a material voucher, its primary key is the material voucher number. This is something that both the header and the body have in common.

Therefore, when looking for the relationship between the forms, we must first understand what the business is, know the logical relationship of the business, and then go to the background to see the structure of the form, which has the primary key of each business document, and each document corresponds through the corresponding key.

It depends on your business needs, and you can't take it randomly, the example you gave above is a foreign key associated with two tables.

For example, mseg-mblnr = mkpf-mblnr, which means that the two tables mseg and mkpf can be concatenated with the mblnr field.

The business consultant will give you the needs, and the logical relationship needs to be thought of by yourself.

The mara-matnr field is associated with the item number.

First of all, take the material description according to the material to MAKT.

Get the material voucher number from the item number to MKPF and then take the material voucher line item from the material voucher number to the MSEG.

Look at the structure of the table through SE11 and then look at the data according to SE16N.

If there is no problem in the report, then see if the samrtform is correct.

When setting the global definition, if the inner table is created by SE11, it does not need to be initialized, if not, the inner table must be initialized and the address of the inner table should be reassigned.

The value can't be transmitted, or what's wrong?

Define an inner table with the fields you want to display when calling alv function T outtab = Inner table you defined.

I don't know if you're asking about data in ALV or extracting fields from two tables in a database?

It's too annoying to write this **.

I don't know if you will abap, I'll tell you the direction first, the 3 tables are displayed separately on the same screen, and you can use custom container controls; The third one, if the table items are too complicated, you can directly declare the table with row strings, and write the table title + data in the inner table.

Take a look and it should be able to fulfill your requirements.

The first one is very easy, make a display interface and make two ALV screens on one display, the second ALV display should not be supported.

Find the right data to go to the table, and slowly become familiar with it.

You can ask others for advice. Remember!

Define a class yourself and write the implementation method.

Write a method in the class to handle the user command event

for event user_command of cl_gui_alv_grid

Importing e ucomm, and then create an instance object of the Create Object event receiver class

Register Set Handler Event Receiver->Handle User Command for Grid1

It should be enough to clear the field of the corresponding row, or when processing the data, determine whether the safety stock quantity is 0, and if it is 0, append the empty row in the table

It's also the first time I've seen this function...

The solution is that the name of your table is not capitalized. . . Tragedy, you try to mess around

If you want to update in real time on ALV, it's slightly high-end... I don't know yet

If it's a normal display assignment, then it's easy as follows:

data: itab1 like table of zvpap001 with header line. "Define an internal table with the same structure as zvpap001.

start-of-selection.

select vbeln posnr matnr zwert "Complete the value.

from vbap

into corresponding fields of table itab1 "Output the fields that need to be displayed with alv.

where vbeln in s_vbeln.

perform frm_exhibit_data. "Here's the ALV display data, and I'll write it if you want to add it, but I think you will

end-of-selection.

loop itab1. "Update the data to zvpap001

move-corresponding itab1 to zvpap001.

modify zvpap001.

endloop.