Adding fields to VL06o

[Former Member]

I need to add a Customer PO Number (BSTNK) to the output display of VL06o.

Since this cant be fetched from LIPS / LIKP , we have a problem.

Let me know if the user exit EXIT_SAPLV50Q_002 may be useful.

Thanks in advance.

[Former Member]

I need to add a Customer PO Number (BSTNK) to the output display of VL06o.

Since this cant be fetched from LIPS / LIKP , we have a problem.

Let me know if the user exit EXIT_SAPLV50Q_002 may be useful.

Thanks in advance.

[former_member182371]

Hi,

in the wiki section of SCN ( https://www.sdn.sap.com/irj/sdn/wiki )

there is a sample.

Once in the wiki go to Code Gallery and search for:

"Additional fields in output for VL06O - List Outbound Delivery "

This is the path:

My Home > Code Gallery > Home > Additional fields in output for VL06O - List Outbound Delivery

Best regards.

[Former Member]

Hi Pablo,

Sorry that WIKI dint solve my issue, since the filed which i reuired for output is not available in LIPS/LIKP/VBUP as mentioned above. Thanks for your immediate response

[former_member182371]

Hi,

please do have a look at OSS Note 128150 .

(one doubt: is field BSTNK the equivalent of field LIPS-KDAUF?)

Best regards

Edited by: pablo casamayor on Jul 16, 2008 4:43 PM

[Former Member]

Hi Pablo,

field BSTNK - Cusomer PO number and the field LIPS-KDAUF - Sales Order number.

Still the question is unanswered

[former_member182371]

Hi,

the answer is in OSS Note 128150

Please pay special attention to the part of EXIT_SAPLV50Q_001

Summary

Symptom

You want to add your own fields to the standard display variants of the delivery monitor.

Other terms

SAPLV50Q, outbound delivery monitor, inbound delivery monitor, VL06O, VL06I, VL06G, VL06P, VL06T, VL06F, VL06C, VL06IP, VL06IC, VL06IT, VL06IG, VL06IF, ALV, SAP List Viewer, list tool, LIPOV, LIPOVZ

Reason and Prerequisites

You can no longer branch from Customizing to maintain your own display variants.

The documentation of the function modules in the SAP enhancement V50Q0001 was not delivered for Release 4.5A because of a transport error.

Solution

General information about the enhancement concept of the delivery monitor

An internal table, the structure of which is derived from the structure LIPOV created in the ABAP Dictionary, is used for displaying the list of the delivery monitor. This structure can be enhanced by customer-specific fields in the structure LIPOVZ provided for this. Keep the following in mind:

• If additional data from the delivery item table LIPS, the delivery header table LIKP or the item status table VBUP is to be set in the table, it is sufficient to create a field with the same name in the structure LIPOVZ. The program will automatically fill this field. You do not have to enter additional Customizing settings or enhancements in a user exit for this.

Examples:

o If you want also want to display the batch number, you must only include the field CHARG in the structure LIPOVZ. This field is then filled automatically in a list of items.

o The weight group of the delivery is also read automatically if you include the field GRULG in the structure LIPOVZ.

• All header status information relevant to the delivery (from the table VBUK) is also available after you create a field with the same name in the structure LIPOVZ. In this way, you can choose to have the following status information displayed if required:

Field name Description

RFSTK Reference document header status

BESTK Confirmation status

LFSTK Delivery status

LFGSK Overall delivery status for all items

WBSTK Total goods movement status

FKSTK Billing status

FKSAK Billing status (order-related billing document)

BUCHK Accounting status of billing document

ABSTK Overall rejection status of all sales document items

GBSTK Overall processing status of sales document

KOSTK Overall picking status

KOQUK Confirmation status of picking

LVSTK Overall status of warehouse management activities

UVALS Totals incompleteness status of all items: general

UVVLS Totals incompleteness status of all items: delivery

UVALS Totals incompleteness status of all items: Billing document

UVALL General incompleteness status of header

UVVLK Incompleteness status regarding delivery

UVFAK Header incompleteness status regarding billing

UVPRS Document incomplete regarding pricing

PKSTK Overall packing status of all items

TRSTA Transportation planning status

CMGST Overall status of credit checks

Some of these fields are already contained in the delivered structure LIPOV.

Note that the changes to the structure LIPOV or LIPOVZ may affect the display variants only after you reset the ALV buffer (see Note 122975).

Note: If you add a field to the structure LIPOVZ that has the same name in the tables LIKP and LIPS (for example, the change date AEDAT), the field is filled with the value from the table LIKP in header lists but, in accordance with the program logic, with the value from the item table LIPS at item list level. If you want to display the header information always and on all types of lists, you must implement the user exit V50Q0001 (see below).

SAP enhancements

If the added fields cannot be filled automatically by the program, you can use the SAP enhancement V50Q0001. You can use transaction CMOD to call it:

• In transaction CMOD, choose 'Utilities -> SAP Enhancements'.

• Enter the name of the enhancement 'V50Q0001' and choose 'Execute'.

You are transferred to a list of function modules that you can use to enhance the functions of the delivery monitor. The function module EXIT_SAPLV50Q_001 is used to read your own data for display on the list.

Using the function module EXIT_SAPLV50Q_001

In the interface of the module, the internal table CT_POSTAB is transferred with the selected data of the delivery.

• If you want to issue a list with header information of the delivery, internal table CT_POSTAB contains an entry for every delivery with a document number different from the initial value and item number '000000'.

• If you want to issue item information, the table contains both the header lines mentioned above with the item number 000000, and for each item that matches the selection criteria an entry with an item number that differs from the initial value.

• The header information of the delivery can also be found in the corresponding fields at item level. The fields for the ship-to party, for example, are also filled at item level.

• The function module is called after all data that can be displayed on the list is read. Thus, the table CT_POSTAB is already filled with information that you can use to read your own data. Only the determination of the picking requests to be confirmed is carried out after this module because individual entries of the output table can be duplicated when this information is read. This occurs if there are several pick orders or putaway orders for a delivery.

• For performance reasons, this module is not called separately for each entry in the output table. Rather, the output table is transferred all together as a parameter. To read the additional data and modify the table entries, you must program a loop through the internal table CT_POSTAB and transport the necessary data to the table.

• Note that some fields of structure LIPOV do not appear in the display as visible fields, but are needed for technical purposes. Do not change the content of these fields.

• The restriction to a maximum of 90 fields in structure LIPOV, which is mentioned in the documentation for function module EXIT_SAPLV50Q_001, is incorrect. No more than 90 fields can be included in a display variant, but there is no restriction on the number of fields in the structure on which the display is based.

The function module EXIT_SAPLV50Q_001 contains two other parameters. They provide information about the processing mode of the delivery monitor:

• IF_FLAG_INBOUND: This flag specifies whether inbound or outbound deliveries are being processed. It is not equal to SPACE in the case of deliveries.

• IF_PROCTYPE: This parameter controls the current processing type. Fixed values for this parameter are stored in Include LV50QTOP. These values indicate the processing type (the names of the constants start with 'proctype_').

Best regards.

Edited by: pablo casamayor on Jul 18, 2008 10:06 PM

[Former Member]

The OSS Note helped me to get an idea. Thanks

[Former Member]

This message was moderated.