Shulou(Shulou.com)06/01 Report--

This article introduces the relevant knowledge of "what are the methods of practical application of SAP SD". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1.SD-how to read the header text of a text order

The last time the order tracking table was modified, the user proposed that the header text should be read. Because there are many languages when the user enters the text, if the text is extracted according to the user's language or setting language conditions in the conditional interface, the text will be missed. Later, after thinking about it, use the language that first gets the header text from the STXH table, and then uses that language to pass in the read_text function to read the text, which ensures that the text is read without omission. The code excerpt is as follows:

CLEAR lV_text.

Select single TDSPRAS into (w_LANG) from STXH

Where TDOBJECT = 'VBBK' and TDNAME = CS_TAB-vbeln and TDID =' YOD1'.

If sy-subrc = 0.

W_tdid = 'YOD1'.

W_tdspras = w_LANG.

W_tdname = CS_TAB-vbeln.

W_tdobject = 'VBBK'.

REFRESH w_lines.

CALL FUNCTION 'READ_TEXT'

EXPORTING

CLIENT = SY-MANDT

ID = w_tdid

LANGUAGE = w_tdspras

NAME = w_tdname

OBJECT = w_tdobject

TABLES

LINES = w_lines

EXCEPTIONS

ID = 1

LANGUAGE = 2

NAME = 3

NOT_FOUND = 4

OBJECT = 5

REFERENCE_CHECK = 6

WRONG_ACCESS_TO_ARCHIVE = 7

OTHERS = 8

2. SD-how to enhance the VF04 display of invoice amounts related to delivery orders

Sap leaves us an enhanced exit: EXIT_SAPLV60P_008, and we can modify the ZXV6PU08 to show the amount of Billing associated with the library.

The methods are as follows:

1. Add the field YYNETWR to VKDFIF to display the price.

2. Modify ZXV6PU08 and enter the YYNETWR field.

The code is copied as follows:

PERFORM y0000sd_0000_fill_vkdfif

TABLES

Lt_vkdfif []

USING lt_vkdfif-vkorg.

* we store the final result

C_vkdfif [] = lt_vkdfif [].

FORM y0000sd_0000_fill_vkdfif

TABLES tt_vkdfif STRUCTURE vkdfif

USING uv_vkorg TYPE vkorg.

DATA ls_vkdfif TYPE vkdfif.

DATA lv_tabix LIKE sy-tabix.

DATA: BEGIN OF t_vbap OCCURS 0

Vbeln TYPE vbeln

Kbmeng TYPE kbmeng

Netwr TYPE netwr

Waerk TYPE waerk

Lfimg TYPE lfimg

END OF t_vbap.

* *

LOOP AT tt_vkdfif INTO ls_vkdfif WHERE vkorg = uv_vkorg.

Lv_tabix = sy-tabix.

SELECT SINGLE vbfa~vbelv

Vbfa~waers

FROM vbfa AS vbfa

JOIN lips AS lips

ON lips~vbeln = vbfa~vbeln AND

Lips~posnr = vbfa~posnn

INTO (ls_vkdfif-yyvbeln_order

Ls_vkdfif-yywaers)

WHERE vbfa~vbeln = ls_vkdfif-vbeln

AND vbfa~vbtyp_n ='J' "delivery

AND vbfa~vbtyp_v 'Bowl. "quotation

CHECK sy-subrc = 0.

* * Confirmed qty value-CT115262 *

If ls_vkdfif-fkart ='F 2'.

Clear ls_vkdfif-yynetwr.

SELECT vp~vbeln vp~kbmeng vp~netwr vp~waerk lp~lfimg

INTO CORRESPONDING FIELDS OF TABLE t_vbap

FROM vbap as vp

INNER JOIN lips AS lp ON lp~vgbel = vp~vbeln AND

Lp~vgpos = vp~posnr

WHERE vp~vbeln = LS_VKDFIF-YYVBELN_ORDER.

LOOP AT t_vbap.

If t_vbap-kbmeng 0.

Ls_vkdfif-yynetwr = ls_vkdfif-yynetwr +

T_vbap-netwr * t_vbap-lfimg / t_vbap-kbmeng.

Ls_vkdfif-waerk = t_vbap-waerk.

Endif.

ENDLOOP.

Endif.

* * *

SELECT SINGLE vdatu

FROM vbak

INTO ls_vkdfif-yyvdatu

WHERE vbeln = ls_vkdfif-yyvbeln_order.

MODIFY tt_vkdfif INDEX lv_tabix FROM ls_vkdfif.

ENDLOOP.

ENDFORM.

3. SDmuri-how to enhance the same type of outgoing order using different number fields

In real business, a company has multiple sales organizations that use the same out-of-warehouse type, and businesses often want them to create different number ranges for warehouse orders. However, in sap, the outgoing order number range is set in the outgoing order type, that is, the same outgoing order type is used, that is, the same number range is used. If we want to meet the business requirements on demand, we can use enhanced implementation. For the specific implementation, see the following steps:

Step 1: create multiple number fields:

Path: Spro- > Sales and Distribution- > Sales- > Sales Documents- > Sales Document Header- > Define Number Ranges For Sales Documents

Or

Path: Spro- > Logistics Execution- > Shipping- > Deliveries- > Define Number Ranges for Deliveries

TCODE: VN01

Step 2: set the number range of the type of the library order

Path: Spro- > Logistics Execution- > Shipping- > Deliveries- > Define Delivery Types

TCODE: 0VLK

Step 3: modify the SAP enhancement code

Modify the source code to control use different number range for different sale organiztion

3.1 you can use se38 to open source code MV50AFZ1 and find the form userexit_number_range.

*-*

* FORM USEREXIT_NUMBER_RANGE *

*-*

* This userexit can be used to determine the numberranges for *

* the internal document number. *

* *

* US_RANGE_INTERN-internal number range *

* *

* This form is called from form BELEG_SICHERN *

* *

*-*

FORM USEREXIT_NUMBER_RANGE USING US_RANGE_INTERN.

* Example: Numer range from TVLK like in standard

* US_RANGE_INTERN = TVLK-NUMKI.

* {INSERT DEVK943692 1

DATA: z_werks TYPE lips-werks

Z_vkorg TYPE likp-vkorg

Z_nrnr TYPE nrnr

Z_vbtyp TYPE likp-vbtyp.

DATA: wa_xlikp LIKE likpvb

Wa_xlips LIKE lipsvb.

US_RANGE_INTERN = TVLK-NUMKI.

Data t (1).

T = TVLK-LFART (1).

If t = 'Zhe.

LOOP AT xlikp INTO wa_xlikp.

LOOP AT xlips INTO wa_xlips.

CASE wa_xlikp-vbtyp.

WHEN OTHERS.

MOVE: wa_xlikp-vbtyp TO z_vbtyp.

ENDCASE.

IF z_vbtyp EQ'J' or "outbound del.

Z_vbtyp eq'This. "return del." V003

MOVE: wa_xlips-werks TO z_werks, "V002" SBr16072007

Wa_xlikp-vkorg TO z_vkorg.

ELSEIF z_vbtyp EQ'7 years. "shipp.notification

MOVE: space TO z_vkorg

Wa_xlips-werks TO z_werks.

ENDIF.

If z_vkorg = '6001mm.

If z_vbtyp eq'Jacks.

Case z_werks.

WHEN '6255.

US_RANGE_INTERN ='D 1'.

WHEN '6245mm.

US_RANGE_INTERN ='D 2'.

WHEN '6254.

US_RANGE_INTERN ='D3'.

WHEN '6234.

US_RANGE_INTERN ='D 4'.

WHEN '6101.

US_RANGE_INTERN ='D 5'.

Endcase.

Elseif z_vbtyp EQ'T'.

Case z_werks.

WHEN '6255.

US_RANGE_INTERN ='R 1'.

WHEN '6245mm.

US_RANGE_INTERN ='R 2'.

WHEN '6254.

US_RANGE_INTERN ='R3'.

WHEN '6234.

US_RANGE_INTERN ='R4'.

WHEN '6101.

US_RANGE_INTERN ='R5'.

Endcase.

Endif.

Endif.

EXIT.

ENDLOOP.

EXIT.

ENDLOOP.

Endif.

*} INSERT

ENDFORM.

4. SDMI-how to add custom fields to the output control

In the output control of sap, we sometimes need to add fields that are not defined by the system as fields in the condition table, and we need to modify and enhance them in order to achieve this requirement.

Communication structure used in output control

KOMKBK1 (Output Determination Communication Area CAS Appl. K1)

KOMKBV1 (Output Determination Communication Area Header Appl. V1)

KOMKBV2 (Output Determination Communication Area Header Appl. V2)

KOMKBV3 (Output Determination Communication Area Header Appl. V3)

KOMKBV5 (Communication Structure for Output Control Groups Appl. V5)

KOMPBV1 (Output Determination Communication Area Item Appl. V1)

KOMPBV2 (Output Determination Communication Area Item Appl. V2)

KOMPBV3 (Output Determination Communication Area Item Appl. V3)

SAP reserves INCLUDEs in these structures, and users can add new fields to these structures

Sales activities: KOMKBZ1 (in KOMKBK1)

Sales document header: KOMKBZ3 (in KOMKBV1)

Delivery header: KOMKBZ4 (in KOMKBV2)

Groups header: KOMKBZF (in KOMKBV5)

Billing document header: KOMKBZ5 (in KOMKBV3)

Sales document item: KOMPBZ1 (in KOMPBV1)

Delivery item: KOMPBZ3 (in KOMPBV2)

Billing document item: KOMKBZ5 (in KOMPBV3)

If we need to create a condition table with a new field, we need to add that field to the KOMBZ structure as well (KOMBZ is included in the communication structure KOMB).

After completing the above two parts, we also need to enhance the sap code to assign values to the fields of the communication structure. Sap reserves a lot of exits in RVCOMFZZ, RVCOMFZ1 and RVCOMFZ4 units.

The exits in RVCOMFZ1 are as follows:

USEREXIT_KOMPBV2_FILL (item fields in delivery)

USEREXIT_KOMPBV2_PARTNER (item fields for partners in delivery)

USEREXIT_KOMPBV3_FILL (item fields in billing document)

USEREXIT_KOMPBV3_PARTNER (item fields for partners in billing document)

The exits in RVCOMFZZ are as follows:

USEREXIT_KOMKBK1_FILL (header fields in sales activities)

USEREXIT_KOMKBK1_PARTNER (header fields for partners in sales activ.)

USEREXIT_KOMKBV1_FILL (header fields for sales documents)

USEREXIT_KOMKBV1_PARTNER (header fields for partners in sales documents)

USEREXIT_KOMKBV2_FILL (header fields in delivery)

USEREXIT_KOMKBV2_PARTNER (header fields for partners in delivery)

USEREXIT_KOMKBV3_FILL (header fields in billing document)

USEREXIT_KOMKBV3_PARTNER (header fields for partners in billing doc.)

The exits in RVCOMFZ4 are as follows:

USEREXIT_KOMKBV5_FILL (header field for groups)

In output determination, communication table KOMB contains all key fields that can be used for conditions for output determination.

When you create new fields for output determination, you can distinguish between two types of fields:

Fields that are used in condition tables

Fields which are only used to query conditions.

Both types of field have to be included in KOMKBV1. Fields which are only used to query conditions do not have to be included in KOMB and T681F or in the field catalog.

The detailed steps for adding custom fields to the order output control are as follows

1. Use SE11 to add custom fields to KOMKBZ3 in KOMKBV1

2. Use SE11 to add custom fields to KOMBZ in KOMB

3. Add custom fields to the allowed fields with Vmax 86 (the fields must come from KOMB, otherwise they will not be visible when creating the table)

4. Define the condition table with Vmax 57

5. Define the conditional storage order

6. Assign the conditional storage order to the conditional type

7. Modify the subprocedure USEREXIT_KOMKBV1_FILL in the code RVCOMFZZ

5. SDMI-batch deletion of orders

In sap applications, it is often necessary to delete some mistakenly entered documents in batches, so a Mini Program is developed for this. For the sake of safety, the program does some control.

1. Restrict users to delete only their own orders and cannot delete orders entered by others. If you need to modify the query conditions,

2. The system defaults to "Test run", which makes it convenient for users to verify the order before deleting the order and make sure that they do not misoperate.

The program code is as follows, for your reference!

REPORT zsde0099.

TYPE-POOLS: slis.

*-*

* data Declarations

*-*

TABLES: vbak. "Sales Document: Header Data

*-*

* table control Output Declarations

*-*

TYPES: BEGIN OF tc_0100

Sel (1), "Check box"

Vbeln LIKE vbak-vbeln, "Sales Order Number"

Erdat LIKE vbak-erdat, "Sales order creation date"

Ernam LIKE vbak-ernam

Kunnr LIKE likp-kunag, "Sold-to Party"

Name1 LIKE kna1-name1, "Sold-to Company Name"

Text (200)

END OF tc_0100.

DATA: wa_tc_0100 TYPE tc_0100

It_tc_0100 TYPE tc_0100 OCCURS 0 WITH HEADER LINE.

DATA g_fieldcat TYPE slis_t_fieldcat_alv.

*-*

* Selection Screen

*-*

SELECTION-SCREEN BEGIN OF BLOCK params1 WITH FRAME TITLE text-001.

PARAMETER: s_vkorg LIKE vbak-vkorg DEFAULT '6001' OBLIGATORY MODIF ID S1. "" Sales Org.

SELECT-OPTIONS:

S_vtweg FOR vbak-vtweg OBLIGATORY, "Distribution Channel"

S_spart FOR vbak-spart OBLIGATORY DEFAULT'10 years, "Division"

S_auart FOR vbak-auart OBLIGATORY, "Order type"

S_erdat FOR vbak-erdat OBLIGATORY, "Sales order creation date"

* s_ERNAM FOR vbak-ERNAM OBLIGATORY, "Sales order creation date"

S_kunnr FOR vbak-kunnr, "Sold-to party"

S_vbeln FOR vbak-vbeln. "Sales Order

PARAMETER p_test AS CHECKBOX DEFAULT'Xuan.

SELECTION-SCREEN END OF BLOCK params1.

*

* INITIALIZATION.

*

INITIALIZATION.

S_auart-sign = 'Iike.

S_auart-option = 'EQ'.

S_auart-low = 'ZC01'.

APPEND s_auart.

S_auart-low = 'ZC03'.

APPEND s_auart.

S_auart-low = 'ZC06'.

APPEND s_auart.

S_auart-low = 'ZC20'.

APPEND s_auart.

S_vtweg-sign = 'Iike.

S_vtweg-option = 'EQ'.

S_vtweg-low = '10cm.

APPEND s_vtweg.

S_vtweg-low ='20 years.

APPEND s_vtweg.

S_vtweg-low = '30mm.

APPEND s_vtweg.

S_vtweg-low = '40mm.

APPEND s_vtweg.

*-*

* Selection Events Processing

*-*

AT SELECTION-SCREEN OUTPUT.

PERFORM screen_check.

AT SELECTION-SCREEN.

CLEAR: it_tc_0100, wa_tc_0100.

REFRESH: it_tc_0100.

START-OF-SELECTION.

PERFORM extract_data.

END-OF-SELECTION.

PERFORM change_sales_orders.

PERFORM display_mes.

* &-- *

* & Form SCREEN_CHECK

* &-- *

* text

*-*

FORM screen_check.

DATA: l_line TYPE i.

DESCRIBE TABLE s_erdat LINES l_line.

IF l_line EQ 0.

S_erdat-sign = 'Iike.

S_erdat-option = 'BT'.

S_erdat-high = sy-datum.

S_erdat-low = sy-datum.

APPEND s_erdat.

ENDIF.

DESCRIBE TABLE s_vtweg LINES l_line.

IF l_line EQ 0.

ENDIF.

ENDFORM. "SCREEN_CHECK

* &-- *

* & Form extract_data

* &-- *

* text

*-*

FORM extract_data.

DATA: lt_it1 LIKE it_tc_0100 OCCURS 0 WITH HEADER LINE

L_chk (1). "for exclude incomplete SO

SELECT a~vbeln a~erdat a~ernam a~kunnr INTO CORRESPONDING FIELDS OF TABLE lt_it1

FROM vbak AS a

WHERE a~vbeln IN s_vbeln

AND a~auart IN s_auart

AND a~vkorg EQ s_vkorg

AND a~vtweg IN s_vtweg

AND a~spart IN s_spart

AND a~erdat IN s_erdat

AND a~ernam = sy-uname

AND a~kunnr IN s_kunnr.

LOOP AT lt_it1.

* get sold-to party company name

PERFORM get_customer_company_name USING lt_it1-kunnr CHANGING lt_it1-name1.

MODIFY lt_it1.

ENDLOOP.

It_tc_0100 [] = lt_it1 [].

ENDFORM. "extract_data

* &-- *

* & Form GET_CUSTOMER_COMPANY_NAME

* &-- *

* text

*-*

*-- > F_KUNNR text

*-- > F_NAME text

*-*

FORM get_customer_company_name USING f_kunnr CHANGING f_name.

CLEAR f_name.

SELECT SINGLE name1 INTO f_name

FROM kna1

WHERE kunnr = f_kunnr.

ENDFORM. "GET_CUSTOMER_COMPANY_NAME

* &-- *

* & Form change_sales_orders

* &-- *

* text

*-*

FORM change_sales_orders.

DATA: lt_order_header_in LIKE bapisdh2

Lt_order_header_inx LIKE bapisdh2x

Lt_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE

Lt_order_item_in LIKE bapisditm OCCURS 0 WITH HEADER LINE

Lt_order_item_inx LIKE bapisditmx OCCURS 0 WITH HEADER LINE

Cp_eind (1).

SORT it_tc_0100 BY vbeln.

DELETE ADJACENT DUPLICATES FROM it_tc_0100.

LOOP AT it_tc_0100.

CLEAR: lt_order_header_inx,lt_order_item_in, lt_order_item_inx, lt_return,cp_eind.

REFRESH: lt_order_item_in, lt_order_item_inx, lt_return.

Lt_order_header_inx-updateflag = 'Downs.

IF p_test NE'Xuan.

CALL FUNCTION 'BAPI_SALESORDER_CHANGE'

EXPORTING

Salesdocument = it_tc_0100-vbeln

* ORDER_HEADER_IN = LT_ORDER_HEADER_IN

Order_header_inx = lt_order_header_inx

TABLES

Return = lt_return.

* handle error messages: determine whether BAPI is successful by judging the type of message

LOOP AT lt_return.

IF lt_return-type EQ 'E'OR

Lt_return-type ='A'OR

Lt_return = 'Xantha.

Cp_eind = 'Xantha. "failure.

It_tc_0100-text = lt_return-message.

ENDIF.

ENDLOOP.

IF cp_eind NE'Xuan.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

Wait = 'Xantha.

ELSE.

CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.

ENDIF.

ENDIF.

IF cp_eind NE'X 'AND sy-subrc = 0.

IF p_test = 'Xantha.

It_tc_0100-text = 'Test successfully.'.

ELSE.

It_tc_0100-text = 'Delete successfully.'.

ENDIF.

ELSE.

CONCATENATE it_tc_0100-text'-'- 'Delete error.' Into it_tc_0100-text.

ENDIF.

MODIFY it_tc_0100.

ENDLOOP.

ENDFORM. "change_sales_orders

* &-- *

* & Form init_fieldedi

* &-- *

* text

*-*

*-- > P_P_FIELDTAB text

*-*

FORM init_fieldedi USING p_p_fieldtab TYPE slis_t_fieldcat_alv.

DATA: l_fieldcat TYPE slis_fieldcat_alv.

REFRESH p_p_fieldtab.

CLEAR l_fieldcat.

L_fieldcat-fieldname = 'VBELN'.

L_fieldcat-seltext_m = 'ORDER NUMBER'.

L_fieldcat-outputlen = 10.

APPEND l_fieldcat TO p_p_fieldtab.

CLEAR l_fieldcat.

L_fieldcat-fieldname = 'ERDAT'.

L_fieldcat-seltext_m = 'Create Date'.

L_fieldcat-ref_fieldname = 'ERDAT'.

L_fieldcat-ref_tabname = 'VBAK'.

L_fieldcat-outputlen = 10.

APPEND l_fieldcat TO p_p_fieldtab.

CLEAR l_fieldcat.

L_fieldcat-fieldname = 'ERNAM'.

L_fieldcat-seltext_m = 'Input Person'.

L_fieldcat-ref_fieldname = 'ERDAT'.

L_fieldcat-ref_tabname = 'VBAK'.

L_fieldcat-outputlen = 10.

APPEND l_fieldcat TO p_p_fieldtab.

CLEAR l_fieldcat.

L_fieldcat-fieldname = 'KUNNR'.

L_fieldcat-seltext_m = 'Sold Code'.

L_fieldcat-ref_fieldname = 'KUNNR'.

L_fieldcat-ref_tabname = 'VBAK'.

L_fieldcat-outputlen = 10.

APPEND l_fieldcat TO p_p_fieldtab.

CLEAR l_fieldcat.

L_fieldcat-fieldname = 'NAME1'.

L_fieldcat-seltext_m = 'Sold Name1'.

L_fieldcat-outputlen = 35.

APPEND l_fieldcat TO p_p_fieldtab.

CLEAR l_fieldcat.

L_fieldcat-fieldname = 'TEXT'.

L_fieldcat-seltext_m = 'Message'.

L_fieldcat-outputlen = 120.

APPEND l_fieldcat TO p_p_fieldtab.

ENDFORM. "INITIALIZE_FIELDEDI

* &-- *

* & Form display_mes

* &-- *

* text

*-*

*-- > p1 text

*

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.