Re: EXITS

Former Member — Wed, 05 Mar 2008 04:39:13 GMT

Hai.

check this for va01_exits.

User Exits In Sales Document Processing

This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.

Involved program components

System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:

• MV45ATZZ

For entering metadata for sales document processing. User-specific metadata must start with "ZZ".

• MV45AOZZ

For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".

• MV45AIZZ

For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".

• MV45AFZZ and MV45EFZ1

For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.

User exits in the program MV45AFZZ

The user exits which you can use for modifications in sales document processing are listed below.

• USEREXIT_DELETE_DOCUMENT

This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.

For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.

The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.

• USEREXIT_FIELD_MODIFICATION

This user exit can be used to modify the attributes of the screen fields.

To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.

The usage of the field groups (modification group 1-4) is as follows:

• Modification group 1: Automatic modification with transaction MFAW

• Modification group 2: It contains 'LOO' for step loop fields

• Modification group 3: For modifications which depend on check tables or on other fixed information

• Modification group 4: is not used

The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.

This FORM routine is called up by the module FELDAUSWAHL.

See the Screen Painter manual for further information on structuring the interface.

• USEREXIT_MOVE_FIELD_TO_VBAK

Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".

The user exit is called up at the end of the FORM routine VBAK_FUELLEN.

• USEREXIT_MOVE_FIELD_TO_VBAP

Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".

The user exit is called up at the end of the FORM routine VBAP_FUELLEN.

• USEREXIT_MOVE_FIELD_TO_VBEP

Use this user exit to assign values to new fields at the level of the sales document schedule lines.

The user exit is called up at the end of the FORM routine VBEP_FUELLEN.

• USEREXIT_MOVE_FIELD_TO_VBKD

Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document" .

The user exit is called up at the end of the FORM routine VBKD_FUELLEN.

• USEREXIT_NUMBER_RANGE

Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.

The user exit is called up in the FORM routine BELEG_SICHERN.

• USEREXIT_PRICING_PREPARE_TKOMK

Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.

• USEREXIT_PRICING_PREPARE_TKOMP

Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.

• USEREXIT_READ_DOCUMENT

You use this user exit if further additional tables are to be read when importing TA01 or TA02.

The user exit is called up at the end of the FORM routine BELEG_LESEN.

• USEREXIT_SAVE_DOCUMENT

Use this user exit to fill user-specific statistics update tables.

The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.

Note

If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.

• USEREXIT_SAVE_DOCUMENT_PREPARE

Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.

The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.

User exits in the program MV45AFZA

• USEREXIT_MOVE_FIELD_TO_KOMKD

Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination" .

• USEREXIT_MOVE_FIELD_TO_KOMPD

Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination ".

• USEREXIT_MOVE_FIELD_TO_KOMKG

Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".

• USEREXIT_MOVE_FIELD_TO_KOMPG

Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".

• USEREXIT_REFRESH_DOCUMENT

With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.

For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.

The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.

The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.

User-Exits in program MV45AFZB

• USEREXIT_CHECK_XVBAP_FOR_DELET

In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).

• USEREXIT_CHECK_XVBEP_FOR_DELET

In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).

• USEREXIT_CHECK_VBAK

This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.

• USEREXIT_CHECK_VBAP

This user exit can be used to carry out additional checks (e.g. for completion) at item level.

• USEREXIT_CHECK_VBKD

The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.

• USEREXIT_CHECK_VBEP

This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).

• USEREXIT_CHECK_VBSN

You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.

• USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).

• USEREXIT_FILL_VBAP_FROM_HVBAP

You can use this user exit to fill additional fields in the sub-item with data from the main item.

• USEREXIT_MOVE_FIELD_TO_TVCOM_H

You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.

• USEREXIT_MOVE_FIELD_TO_TVCOM_I

You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.

• User-Exits for product allocation:

The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.

• USEREXIT_MOVE_FIELD_TO_COBL

Option to include new fields in structure COBL.

• USEREXIT_COBL_RECEIVE_VBAK

Option to assign values from the document header to the new fields.

• USEREXIT_COBL_RECEIVE_VBAP

Option to supply values from the item to the new fields.

• USEREXIT_COBL_SEND_ITEM

A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).

• USEREXIT_COBL_SEND_HEADER

A changed field can be copied from the structure to the header (see source text MV45AFZB)

• USEREXIT_SOURCE_DETERMINATION

You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.

• USEREXIT_MOVE_FIELD_TO_ME_REQ

With this user exit you can include additional fields for the following fields:

• EBAN (purchase requisition)

• EBKN (purchase requisition-account assignment)

• USEREXIT_GET_FIELD_FROM_SDCOM

Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.

• USEREXIT_MOVE_WORKAREA_TO_SDWA

You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.

• User-Exits for first data transfer:

The following user exits can only be used for the first data transfer.

Note

Only use the user exits if the names/fields do NOT have the same name.

• USEREXIT_MOVE_FIELD_TO_VBAKKOM

Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)

• USEREXIT_MOVE_FIELD_TO_VBAPKOM

Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)

• USEREXIT_MOVE_FIELD_TO_VBEPKOM

Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)

• USEREXIT_MOVE_FIELD_TO_VBSN

You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).

• USEREXIT_MOVE_FIELD_TO_KOMKH

You can use this user exit to include new fields for batch determination (document header).

• USEREXIT_MOVE_FIELD_TO_KOMPH

You can use this user exit to include new fields for batch determination (document item).

• USEREXIT_CUST_MATERIAL_READ

You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)

• USEREXIT_NEW_PRICING_VBAP

Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.

• USEREXIT_NEW_PRICING_VBKD

Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.

• User-Exits in Program MV45AFZD

• USEREXIT_CONFIG_DATE_EXPLOSION

The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).

User exits in the program FV45EFZ1

• USEREXIT_CHANGE_SALES_ORDER

In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).

If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.

User-Exits in Program RV45PFZA

• USEREXIT_SET_STATUS_VBUK

In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).

The following workareas are available for this user exit:

• VBUK (header status)

• FXVBUP (item status)

• FXVBUV (Incompletion)

• USEREXIT_SET_STATUS_VBUP

In this user exit you can you can store a specification for the reserve fields for VBUP (item status).

The following workareas are available for this user exit:

• FXVBAP (Item data)

• FXVBAPF (Dynamic part of order item flow)

• FXVBUV (Incompletion)

• USEREXIT_STATUS_VBUK_INVOICE

You can use this user exit to influence billing status at header level.

User exits in the screens

Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.

Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.

For field transports, you do not have to make changes or adjustments.

Example

A new field, VBAK-ZZKUN, should be included in table VBAK.

If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.

User Exits in Program MV45AFZ4

• USEREXIT_MOVE_FIELD_TO_KOMK

You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.

• USEREXIT_MOVE_FIELD_TO_KOMP

You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.

User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs

• EXIT_SAPFV45P_001

You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.

V45A0002 Predefine sold-to party in sales document

V45A0003 Collector for customer function modulpool MV45A

V45A0004 Copy packing proposal

V45E0001 Update the purchase order from the sales order

V45E0002 Data transfer in procurement elements (PRreq., assembly)

V45L0001 SD component supplier processing (customer enhancements)

V45P0001 SD customer function for cross-company code sales

V45S0001 Update sales document from configuration

V45S0003 MRP-relevance for incomplete configuration

V45S0004 Effectivity type in sales order

V45W0001 SD Service Management: Forward Contract Data to Item

V46H0001 SD Customer functions for resource-related billing

V60F0001 SD Billing plan (customer enhancement) diff. to billing plan

check this for va01_bdc.

Check the code :

DATA: bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.

DATA : w_auart(4) TYPE c,

w_vkorg(4) TYPE c,

w_vtweg(2) TYPE c,

w_spart(2) TYPE c,

w_kunnr(10) TYPE c,

w_kunrg(10) TYPE c,

w_bstkd(35) TYPE c,

w_bstdk(10) TYPE c,

w_kwmeng(18) TYPE c,

w_zterm(4) TYPE c,

w_inco1(3) TYPE c,

w_inco2(28) TYPE c,

w_augru(3) TYPE c.

DATA : var1 TYPE string,

var2 TYPE c VALUE '(',

var3 TYPE c VALUE ')',

num(2) TYPE c,

flag(1) TYPE c.

DATA : BEGIN OF it_order, " Internal table Structure

auart(4) TYPE c, " Sales Order Type

vkorg(4) TYPE c, " Sales Organization

vtweg(2) TYPE c, " Distribution Channel

spart(2) TYPE c, " Division

kunnr(10) TYPE c, " Sold-to-Party

kunrg(10) TYPE c, " Ship-to-Party

bstkd(35) TYPE c, " Purchase Order No

bstdk(10) TYPE c, " Purchase Order Date

zterm(4) TYPE c, " Payment Terms

inco1(3) TYPE c, " Inco Terms1

inco2(20) TYPE c, " Inco Terms2

augru(3) TYPE c, " Order Reason

mabnr(18) TYPE c, " Material No

kwmeng(18) TYPE c, " Quantity

END OF it_order,

itab LIKE STANDARD TABLE OF it_order WITH HEADER LINE.

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

PARAMETER filename LIKE rlgrap-filename.

PARAMETER session LIKE apqi-groupid.

SELECTION-SCREEN END OF BLOCK b1.

AT SELECTION-SCREEN ON VALUE-REQUEST FOR filename.

************************************************************************

Get the file path

************************************************************************

CALL FUNCTION 'WS_FILENAME_GET'

EXPORTING

def_filename = filename

def_path = ' '

mask = ',.,..'

mode = 'O'

title = 'Select File'

IMPORTING

filename = filename

EXCEPTIONS

selection_cancel = 1.

CHECK sy-subrc = 0.

START-OF-SELECTION.

CALL FUNCTION 'WS_UPLOAD'

EXPORTING

codepage = ' '

filename = filename

filetype = 'ASC'

headlen = ' '

line_exit = ' '

trunclen = ' '

user_form = ' '

user_prog = ' '

dat_d_format = ' '

IMPORTING
FILELENGTH =

TABLES

data_tab = itab

EXCEPTIONS

conversion_error = 1

file_open_error = 2

file_read_error = 3

invalid_type = 4

no_batch = 5

unknown_error = 6

invalid_table_width = 7

gui_refuse_filetransfer = 8

customer_error = 9

OTHERS = 10.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

PERFORM open_group.

LOOP AT itab.

CLEAR : w_auart,w_vkorg,w_vtweg,w_spart,w_kunnr,w_kunrg,

w_bstkd,w_bstdk,w_zterm,w_inco1,w_inco2,w_augru.

w_auart = itab-auart.

w_vkorg = itab-vkorg.

w_vtweg = itab-vtweg.

w_spart = itab-spart.

w_kunnr = itab-kunnr.

w_kunrg = itab-kunrg.

w_bstkd = itab-bstkd.

w_bstdk = itab-bstdk.

w_zterm = itab-zterm.

w_inco1 = itab-inco1.

w_inco2 = itab-inco2.

w_augru = itab-augru.

ON CHANGE OF itab-kunnr OR itab-kunrg OR itab-bstkd .

flag = 0.

num = 1.

PERFORM bdc_dynpro USING 'SAPMV45A' '0101'.

PERFORM bdc_field USING 'BDC_CURSOR'

'VBAK-AUART'.

PERFORM bdc_field USING 'BDC_OKCODE'

'/00'.

PERFORM bdc_field USING 'VBAK-AUART' " Order Type

itab-auart.

PERFORM bdc_field USING 'VBAK-VKORG' " Sales Organization

itab-vkorg.

PERFORM bdc_field USING 'VBAK-VTWEG' " Distribution Channel

itab-vtweg.

PERFORM bdc_field USING 'VBAK-SPART' " Division

itab-spart.

PERFORM bdc_dynpro USING 'SAPMV45A' '4001'.

PERFORM bdc_field USING 'BDC_OKCODE'

'/00'.

PERFORM bdc_field USING 'VBKD-BSTKD' " PO Number

itab-bstkd.

PERFORM bdc_field USING 'VBKD-BSTDK' " PO Date

itab-bstdk.

PERFORM bdc_field USING 'KUAGV-KUNNR' " Sold to Party

itab-kunnr.

PERFORM bdc_field USING 'KUWEV-KUNNR' " Ship to Party

itab-kunrg.

PERFORM bdc_field USING 'VBKD-ZTERM' " Payment Terms

itab-zterm.

PERFORM bdc_field USING 'VBKD-INCO1' " Inco Terms1

itab-inco1.

PERFORM bdc_field USING 'VBKD-INCO2' " Inco Terms2

itab-inco2.

PERFORM bdc_field USING 'VBAK-AUGRU' " Order Reason

itab-augru.

ENDON.

IF flag = 0.

LOOP AT itab WHERE bstkd = itab-bstkd AND kunnr = itab-kunnr .

var1 = 'RV45A-MABNR'.

CONCATENATE var1 var2 num var3 INTO var1.

PERFORM bdc_field USING var1

itab-mabnr.

var1 = 'RV45A-KWMENG'.

CONCATENATE var1 var2 num var3 INTO var1.

PERFORM bdc_field USING var1

itab-kwmeng.

PERFORM bdc_dynpro USING 'SAPMV45A' '4001'.

PERFORM bdc_field USING 'BDC_OKCODE'

'/00'.

num = 2.

ENDLOOP.

ELSE.

CONTINUE.

ENDIF.

flag = 1.

PERFORM bdc_dynpro USING 'SAPMV45A' '4001'.

PERFORM bdc_field USING 'BDC_OKCODE'

'=SICH'.

PERFORM bdc_transaction USING 'VA01'.

ENDLOOP.

PERFORM close_group.

WRITE : / 'Session',session, 'was Created'.

FORM open_group.

CALL FUNCTION 'BDC_OPEN_GROUP'

EXPORTING

client = sy-mandt

group = session

user = sy-uname

keep = 'X'.

ENDFORM.

FORM close_group.

CALL FUNCTION 'BDC_CLOSE_GROUP'.

ENDFORM.

FORM bdc_transaction USING tcode.

CALL FUNCTION 'BDC_INSERT'

EXPORTING

tcode = tcode

TABLES

dynprotab = bdcdata.

ENDFORM.

FORM bdc_dynpro USING program dynpro.

CLEAR bdcdata.

bdcdata-program = program.

bdcdata-dynpro = dynpro.

bdcdata-dynbegin = 'X'.

APPEND bdcdata.

ENDFORM.

FORM bdc_field USING fnam fval.

IF fval <> ' '.

CLEAR bdcdata.

bdcdata-fnam = fnam.

bdcdata-fval = fval.

APPEND bdcdata.

ENDIF.

ENDFORM.

check this for va01_screenexits.

refer this site.

From SAP note 209278 and 302497 and others it looks like the Additional Data B screens are intended for customer changes.

https://www.sdn.sap.com/irj/sdn/forums

If you have to Design the screen on the Standard Transaction VA01. And if you have Authorizations , Then in the sales order Screen if you go to header and you can find Additional Data A and Additional Data B . This screen can be used for your fields .

And You can use include MV45AFZZ, and use the perform

----

FORM USEREXIT_MOVE_FIELD_TO_VBAK *

----

This userexit can be used to move some fields into the sales *
dokument header workaerea VBAK. *
*
SVBAK-TABIX = 0: Create header *
SVBAK-TABIX > 0: Change header *
*
This form is called at the end of form VBAK_FUELLEN. *
*

----

form userexit_move_field_to_vbak.

Endform.

To move the fields .

check this for va01_newfield add

The program SAPMV45A screen 8309 is the Additional Data B tab provided by SAP to add your custom fields . In order to capture the data from your custom fields you can use the user exit MV45AFZZ, USEREXIT_SAVE_DOCUMENT_PREPARE OR

USEREXIT_SAVE_DOCUMENT depening on your functionality.

You need to append the fields in VBAP. Then use the screen painter to add the fields in the screen.

regards.

sowjanya.b

topic Re: EXITS in Application Development and Automation Discussions

EXITS

Re: EXITS

Re: EXITS