Purchase order : user-exit to fill new field in table EBAN
Hi,
in EBAN table i created a new field named ZTYPE_SITE. Now i would like to fill this field when i save my purchase requisition. I don't found the user-exit or BADI to do that.
Thanks for help.
Cheers.
up
Similar Messages
-
Purchase Order User Exit (ME21N)
Hello experts,
I have a request to enhance SAP for authorization when a user creates a PO (ME21N)that all of the line items have the same purchasing group as the what is in the header, or it cannot be created.
Anybody have any idea what exit this would be in?
Thanks.Hi Tom,
Here are the user exits available for ME21N.
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
For your case, please check <b>MM06E005</b> or you can try BADI <b>ME_PROCESS_PO_CUST</b>.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful. -
Create Purchase Order : User Exit
Hi,
When creating a Purchase Order, before saving it, I want to check the line items for certain conditions and want to check or uncheck the Goods Receipt indicator based on the condition.
Could someone please let me know the user exit for this. I would really appreciate your help.
Thank You,
RekhaHere is a program which shows you user exits by transaction code. Implement the program, run it, and enter the transaction code, hit F8. This will give you a listing of exits. Look thru them, look at the function modules tied to them and look at the FM signature to see if your data is available. I don't know for sure if any will actually update a value.
report z_find_user_exit no standard page heading.
tables: tstc, tadir, modsapt, modact,
trdir, tfdir, enlfdir, tstct.
data : jtab like tadir occurs 0 with header line.
data : hotspot(30).
parameters : p_tcode like tstc-tcode obligatory.
at line-selection.
get cursor field hotspot.
check hotspot(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
call transaction 'SMOD' and skip first screen.
start-of-selection.
perform get_data.
perform write_list.
* FORM get_data *
form get_data.
select single * from tstc
where tcode eq p_tcode.
check sy-subrc eq 0.
select single * from tadir
where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
if sy-subrc ne 0.
select single * from trdir
where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir
where pname = tstc-pgmna.
select single * from enlfdir
where funcname = tfdir-funcname.
select single * from tadir
where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = tadir-devclass.
select single * from tstct
where sprsl eq sy-langu
and tcode eq p_tcode.
endform.
* FORM write_list *
form write_list.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
endform.
Regards,
Rich Heilman -
Regarding Purchase order User-exit
Hello friends,
Here is the situation.
when we create purchase order ... I need to modify the planned delivery field value under delivery tab at item level.
For this I found user exit. 'EXIT_SAPMM06E_016' and I have written the logic in the include program.
when I tested in debbugmode... the cursor is not at all comming to that point. It was failing always at the function module 'MODX_FUNCTION_ACTIVE_CHECK'.
I don't know alwys active field showing blank. I think we need to activate the user exit some where. how to do and where to do?
plese help me ..
extract the code --from include program MM06EF0C_CUSTSCR1_ITEM_SET_D03
User-Exit für Positionsfelder versorgen (PBO)
FORM custscr1_item_set_data_pbo USING im_no_screen LIKE fc_call.
DATA: l_enj_call TYPE c.
STATICS: first_call(1) TYPE c VALUE 'X',
active LIKE sy-calld.
IF NOT first_call IS INITIAL.
CLEAR first_call.
CALL FUNCTION 'MODX_FUNCTION_ACTIVE_CHECK'
EXPORTING
cprogname = 'SAPMM06E'
funcnumber = '016'
IMPORTING
active = active
EXCEPTIONS
not_found = 1
OTHERS = 2.
IF NOT sy-subrc IS INITIAL.
CLEAR active.
ENDIF.
ENDIF.
CHECK NOT active IS INITIAL. ==========================> always active sowing blank
IF fc_vorga EQ cva_en.
l_enj_call = 'X'.
ELSE.
l_enj_call = space.
ENDIF.
*-Define Fields:
DATA: l_ci_ekpo LIKE ekpo_ci,
lt_usr_tekpo LIKE bekpo OCCURS 0,
lt_usr_teket LIKE beket OCCURS 0,
lt_usr_tekkn LIKE ekknu OCCURS 0,
lt_usr_tkomv LIKE tkomv OCCURS 0.
*-Copy Tables:
MOVE-CORRESPONDING ekpo TO l_ci_ekpo.
lt_usr_tekpo[] = pot[].
lt_usr_teket[] = ett[].
lt_usr_tekkn[] = knt[].
lt_usr_tkomv[] = tkomv[].
*-User Exit
CALL FUNCTION 'EXIT_SAPMM06E_016'
EXPORTING
i_ekpo = ekpo
===============
thanks in advance
Regards
RaghuHi Raghunath
I hope you have included your enhancement in a project and activated the project.
1-Needed help
2-SMOD and CMOD
Hope it is helpful.
Regards
Neha -
Outbound Purchase order user exit EXIT_SAPLEINM_002 help
Hi,
Can somebody tell me how to stop the IDOC processing if the conditions are not met? My detail question is
I am modifying the data in the outbound IDOC (IDOC_OUTPUT_ORDERS) for purchase order. I am using the user exit EXIT_SAPLEINM_002 to modify the segment data.
But I would like to know how to stop for creating the IDOC if one of the condition will not met (for example if there is no data in Ztable while fetching then IDOC should not be created )?
If the condition will fail I don't want to create the IDOC but Purchase order has to create in R/3.
Any suggestions on my above query is highly appreciable.
Regards,
NoorulHi
The purchase order should always be created because it's created before creating the IDOC, I suppose it will be created by a particular message.
Have you tried to raise the exception DATA_NOT_RELEVANT_FOR_SENDING?
Max -
Is there a badi or user exit for including new field in XK01 ?
Hi
We have a legal requirement for incluiding new field in T/C XK01, is there a badi or user exit wich help it?
Thanks in advance.
Moderator message: please (re)search yourself first.
Edited by: Thomas Zloch on Dec 16, 2010 4:01 PMCan anyone provide the documentation for this BADI? Also, I'm concerned about the layout of the screen. Can this BADI do the necessary changes on the layout of the screen?
Thanks! -
Hello Firends,
I am unable to find suitable user exit. My requirement is whenever a new PO is created from Preq,the system should check a Z table where certain material/Sloc combinations are allowed. If combination is not maintained in z table, error message should be diaplayed and PO should not be created.
Please advise.
SanjayDear Sanjay,
You want to find User Exits its very simple, please do this way
Go to 'SMOD' and give here enhancement name and click Test or F8
if you dont know Enhancement name press F4 and give package "ME" press enter and here so many exit names displays select relavent and press test or F8 inside of that exit your user exit will appear
Hope this may helps you
Prem. -
Purchase order user exit / BADI / Enhancement points
Hello experts,
Please Help me to get the user exit or any way to enhance the PO functionality. I am trying to set the PO line item status to "Blocked" or "Unblocked" whenever a change is triggered in PO line item for transactions Me21N / Me22N. The blocked status will be triggered by the custom enhancement, this is the requirement.
Thanks in advance for your help.
I tried the user exit MM06E005, but not working.
- NagarajanHello Nagarajan Ramudu,
inside of MM06E005 you should try the function module EXIT_SAPMM06E_012,
i'm using this user-exit from all things in my company.
Regards,
Welinton Rocha -
Need All Sales Order user exit
Neeed all Sales Order user exits
Hi,
Check these Exits and their corresponding Programs
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.
Reward points if helpful.
Regards
Ravi -
Need to fill a new field in table EKKO
Hi all,
i created a new field (ZZCODE) in the table EKKO. Well, now i would like to fill this field when the user save his purchase order. Which user-exit or BADI can i use ?
I tried a lot but either i can't change the parameters values either the FM is not raise.
Thanks for help.HI CECG,
Yesterday itself i tried this example,
i will forward u the document to ur mail id,
plz provide me the mail id so that i will forward u the doc..
STEP-BY-STEP PROCEDURE FOR SCREEN EXIT IN ME21n TRANSACTION
Introduction:
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
Requirement:
You have to add the custom field in SAP standard table EKKO. Then we have to place the field in ME21N screen. When user enters any input into the field it should get updated in the database.
Note:
EKKO table is meant for Purchasing document header, you should add the field in the header level for ME21n screen. There you are provided with customer sub screens where you can add the field in the screen.
In EKKO table
include : cl_ekkodb
in that u can add the field u want
Procedure:
1. You have to create a field in the Custom Include of standard table, after creating activate it.
2. Double click on the include then you can add your custom field here.
Find out the Required Enhancements:
1. Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton Information system.
MM06E005 : CUSTOMER FIELDS IN PURCHASING DOCUMENT
2. Then mention the particular package name of the transaction you need to enhance. Then you will be shown the list of Enhancement components for that particular package.
3. Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
MM06E005 is the Enhancement component we are using here.
Development
Creating a Project to include the enhancement:
1. Go to transaction CMOD and create a project.
2. Enter a description for the project.
3. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
4. Click on the components in Application Toolbar.
5. Here you will be shown the function module exits, screen exits and Include tables.
6. Click on the custom screen SAPLXMO6 0101 in which it suits the requirement of adding the custom field to the layout.
7. Click on layout and go to get from dictionary and select the field you need to add and click ok.
8. Place the field in the layout and activate it.
9. After that you come back and check the respective function module in which you need to implement the code. So, we need to import the data from sub screen for purchasing document header. Therefore we have chosen the EXIT_SAPMM06E_008.
10. Write code in the Function Exits to synchronize the programs:
Now, code has to be written in the function modules EXIT_SAPMM06E_008 so that data flows to and fro between the main SAP program and custom sub screen program. Double clicking on the exit we get the following screen.
11. Double click on the include and write the required code inside it. Then activate it.
12. Now come back and activate the entire project.
13. Now go to ME21n transaction and create a purchase order by giving all the mandatory fields including custom field we have created. Go to SE16n, check whether the field got updated in the database or not.
Finally it gets updated in the database.
IF U PROVIDE ME UR MAILID I CAN SEND U THE DOCUMENT WHICH IS VERY CLEAR FOR PURCHASE ORDER
PLZ REWARDS POINTS IF HELPFUL,
Ganesh. -
BADI / USER-EXIT FOR DEFAULTING THE FIELD VTTK-TNDR_ACTC IN TCODE VT01N
Hi,
I require a BADI / USER-EXIT for defaulting the field VTTK-TNDR_ACTC(Currency of Actual Shipment costs) to 'EUR' in transaction VT01N(Shipment Transaction) .
Please could anyone help me with this .
Regards,
Sushanth H.S.Hi!
User Exits in Transportation
In Transportation, there are enhancements that you can use with transaction CMOD.
For a detailed description of the individual enhancements, see the documentation on the individual enhancements or function modules in transaction SMOD.
You can display all enhancements that are available for the area of transportation by choosing F4 in the Enhancement field. Enter V56* in the Enhancement field and choose Execute. Enter V54* to get a list of all enhancements for the area of shipment cost processing.
Business Add-Ins in the transports
Business add-ins (BADIs) are predefined user exits. They enable businesses, partners, and customers to add additional softward to the SAP source code. The linkup of SAP's New Dimension Products, such as APO and BW, to the standard system is thus possible.
Customer-specific functions can be executed before the save time and after the database update.
The following methods are available for the BADI with the definition name 'BADI_LE_SHIPMENT':
AT_SAVE: BADI is called up at the time of the save. Checks and return to dialog are possible.
BEFORE:_UPDATE: BADI is called up right before the data is saved to the database, that is, when all the data is available (for example, internal ly assigned shipment number).
IN_UPDATE: BADI is called up after the database update.
Standard Settings
Creating a BADI method:
Call up transaction SE19. Enter a name of your choice. Choose "create" and in the dialog box enter the definition name 'BADI_LE_SHIPMENT'. Afterwards, enter a short text for implementation. Save the BADI.
On the tab page 'Interface', choose the method for implementation by double-clicking on it. Now you can enter your customer-specific program code. Save and activate the code. You can acess the transmission parameters entered in the BADI definition. With the method ***_AT_SAVE you can initiate the exception ERROR_WITH_MESSAGE (description 'An error message has occurred' ) if you wish to return to the dialog.
Afterwards, go to the heading and activate the interface.
Regards
Tamá -
Purchase Order History Reference not filled
Hello everyone,
we are using BAPI_INCOMINGINVOICE_CREATE to create an invoice for an purchase order. It works just fine except that there no Reference filled in the Purchase Order History. We fill the number of the reference to the BAPI (headerdata-ref_doc_no) and the reference is visible on the created FI document as expected.
However the customer insists, that it has to be visible in the field Reference of the Purchase Order History as well. I know, it is the XBLNR field of the table BSEG. I dug deep in the source codes to find out, where is the problem, but setting of this field seems to be very complicated. Someone told me, that the field is only filled when the GR-Based Invoice Verification is checked (which in our case is not).
Can someone tell me the rules, when the field Reference gets filled? Or (if there is anything) how to customize the system, co make this field filled?Hi Oleg,
thank you for your reaction.
I am aware of that there is a field XBLNR in the BKPF table - and there we have the reference filled correctly (it is visible on the FI document as I mentoined). However in the BSEG table is the XBLNR as well and it is related to displaying Reference in the Purchase Order History (the bseg relates to an PO item) at least in our case. When I manually input in the BSEG-XBLNR a value (via SE16N for example), it displays afterwards in the required field when viewing the Purchase order.
In the case GR-Based Invoice Verification procedure and the table MKPF - i believe, you are right there (so the Reference is filled), however this is unfortunatelly not our case.
What I am trying to find out are the conditions, under which the XBLNR in BSEG is filled (I can tell you, what source codes I have been inspecting, but I got lost after I while, because there are literally thousands of lines of code:-( -
How to find user exits for a specific field
hi,
How can we find a user exit for a specific fields .
as i know Three ways to search user-exits
1. SE80 look includes in a packages with name user-exits
2. by zreport which will fetch user-exit in a T-CODE
3. SMOD
but what if we have to find a user-exit for particular field for e.g bupla(bussiness place) in MIRO.
Please suggest me.
Thanks and Regards ,
Rahul Singh.Hi Rahul,
Here is the procedure to create field exits.
Step by step procedure for creating Field Exits
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
u2022 Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
Step 2: Go To Field Exit Transaction
u2022 The transaction to create field exits is CMOD.
u2022 You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
u2022 From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
u2022 After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
u2022 From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
u2022 After choosing this menu path, a dialog box will prompt you for the appropriate data element .
u2022 Enter the data element name and click the u2018Continueu2019 pushbutton.
u2022 Now, you will be able to create the function module associated to the data elementu2019s field exit.
Step 4: Create Function Module
u2022 You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the u2018Continueu2019 pushbutton.
u2022 In the u2018Function moduleu2019 field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
u2022 You can add an identifier (an underscore followed by a single character ).
u2022 The first function module for a data elementu2019s field exit must be created without an identifier.
u2022 To create the function module, click on the u2018Createu2019 pushbutton, choose menu path Function module -> Create, or press u2018F5u2019.
u2022 After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing u2018Enteru2019, you will be able to go ahead and create the function module.
u2022 Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
u2022 From the function moduleu2019s attributes screen, click on the u2018Source codeu2019 pushbutton or choose the Goto -> Function module menu path to the code of the function module.
u2022 Here you will add your desired functionality for the field exit.
u2022 Remember that field exitu2019s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
u2022 You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
u2022 After coding the function module, you must remember to activate it.
u2022 Use the Function module -> Activate menu path to activate the function module.
u2022 At this point, you can return to the field exit transaction.
u2022 You should be able to 'green arrow' back to this transaction.
u2022 When you return to the field exit transaction, you will see an entry for the newly created field exit.
u2022 At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
u2022 Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
u2022 This step is only needed if you want to make a field exit local.
u2022 To make a field exit local, select the field exit and click on the u2018Assign prog./screenu2019 pushbutton.
u2022 In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
u2022 In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the u2018Fld. Exitu2019 field.
u2022 If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
u2022 If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
u2022 The field exit must be active for it to be triggered by the system.
u2022 Activate the field exit by choosing the Field exit -> Activate menu path.
u2022 After assigning the field exit to a change request, its status will change to u2018Activeu2019 and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Execute the transaction SE38 with PROGRAM NAME - RSMODPRF
Then give the Data Element Name for which field you want to create the exit(Just cross check with your field data element) and execute.
then it takes you to SE37 with the function module name FIELD_EXIT_<DATA ELEMENT NAME> and then create the same function module.
and in the coding part, You can write your logic to display the output of that field. and activate it.
once you complete the above,
Again execute SE38 transaction with program RSMODPRF and again click on Execute button without any Data Element Name. Now you select the data element which you have created and click on Assign prog/ Screen button and assign the program name and screen number of the filed and click on the menu Field Exit and Activate.
Hope it helps.
Regards
Radhika
Edited by: Radhika Pande on Nov 26, 2009 7:58 AM -
Purchase order screen exit SAPMM06E,screen number 0111
Hi
I am working on purchase order screen exit SAPMM06E and screen number 0111
i am able to see customer screen in transaction but program control is not going to flow logic
due to that i couldn't able to fetch data into custom fields.pls suggest me wat to do.
Thanks & Regards
VinayHi Vinay ,
I think you are implementing the screen exit with the enhancement component 'MM06E005'.
if thats the case you add your fiels in the screen area provided
in the screen 'SAPMM06E' 0111 by creating the subscreen in the SE51 with the name space 'SAPLXM06' 0111 with then will be reflected (fields added) in the ME21n transaction .
You have to write your logic in the EXITS provided in that enhancement component
You have to write your logic in the exit 'EXIT_SAPMM06E_008'
as it imports data from screen field which you placed in the tcode.
Revert back to me for any queries.
Reward points if useful.
Thanks ,
Surya Pydikondala. -
Change Confirmed Qty in Sales Order User exit/ATP User exit
HI
We have a requirement to change the ATP Qty for certain meterials & Order Types duing sales Order User exit(FORM USEREXIT_MOVE_FIELD_TO_VBEP.? ) or ATP User exit.( ATP...OUT?).
Is this ok to update the XVBEP in FORM USEREXIT_MOVE_FIELD_TO_VBEP of MV45AFZZ ?
Our requirement will be like this, for one order type ZSAL( and for certain Materials) we need to reserve 4 qty, if any order comes with 10 qty and the confimed qty is only 6( total available stock at present) , then we should only confirm 2 qty for the other order type( For Non ZSAL Order Type), and reserve the 4 QTY for ZSAL Order Type.
If there are multiple schedule lines for an Item, we need to reduce the qty equally( as possible) from all schdule lines.
i.e. date1 qty 4
date2 qty 6,
in this case we should confirm Date1 QTY 2, date2 qty 4, so that the remaining 4 will be reserved for ZSAL Order type.
Whats the Best way to achieve this ?
Edited by: agrud agrud on Sep 8, 2011 4:01 AMHi Agrud,
Did you check the possibilities with configuration.If it is not possible with configuration then you can use that exit.Before i used this but only to display not to change any thing.
Regards,
Madhu.
Maybe you are looking for
-
IPod stuck in Disk Mode(Restart won't work)
My iPod is stuck in disk mode, and no matter how many times I restart it, it stays in this. I've tried the 5R's and I've tried restarting it. Is there any other fixes?
-
Hello, Could somebody please help me here coz everything is quiet new for me. I'm trying to open up some applications i downloaded from the apple website , but as i try to open them up a window pops up saying there's no default application chosen to
-
Hello everybody, Does anyone knows if it is possible to have a column caption in a table that spans for more than one column, e.g., | number of veichles | | cars | boats | plains | | 23 | 3 | 1 | and also more than one caption per co
-
Serial # uploading limitation in physical inventory doc
Hi, when uploading a physical inventory document it allows only 18 serial numbers to upload at a time and it is very difficult task as per the business is concern where there are about 9000 seria (qty)l for some materials is there any way to upload t
-
Required password for itunes keeps pop up on my kid's ipad constantly nonstop. So i put in password and then it keeps appear the confirm purchased pop up. I clicked on cancel a thousand times but it keeps popup right after i clicked cancel. Tried so