USER EXIT's include (ZXFYTU01)

Hi
We are planning to modify USER EXIT's include (ZXFYTU01),
but before modifying i want to know what's the impact if i modify this include.
also how to check the same include has been used in some other place.
fyi : thru where-used list we cant find.
is there any other way we can find ?
regards
justin

Hi Justin,
I am not getting this ZXFYTU01.Can you tell me where you got this. Generally we will write code in the user exit. Here what is meant by "i want to know what's the impact if i modify this include". Please elaborate little more.
Regards,
Madhu.

Similar Messages

Is there a user exit to include Purchase Order (EBELN) in RFFOUS_T?

Is there a user exit to include the Purchase Order Number (EBELN) on the Payment Advice generated from RFFOUS_T? Or is this a custom modification?
I have field REGUP-EBELN defined in the form Z110_US_AVIS_SAP (clone of F110_US_AVIS_SAP), but the print program does NOT populate REGUP-EBELN.

Hi,
Please follow this an Example:-
The COOIS report (Order Info System) gives the complete information regarding Production Order like header report, Operation report, Component Report, document report.
This document deals with the addition of extra fields in the output display of COOIS.
For the demo purpose, I have added the material group (MATKL) for the production order material for header report.
BADI Name: WORKORDER_INFOSYSTEM
Method: TABLES_MODIFY_LAY
In the method TABLES_MODIFY_LAY there are many table parameters for different data display of the production order .In this scenario only the header detail structure is being extended with append structure.
Add the extra fields to be displayed to through append structure to IOHEADER_TAB, here MATKL.
In the method write the code for updating the field value.
DATA : BEGIN OF st_matkl,
           matkl TYPE matkl,
           END OF st_matkl.
DATA : st_header TYPE ioheader.
LOOP AT ct_ioheader INTO st_header.
    IF NOT st_header IS INITIAL.
      SELECT SINGLE matkl
             FROM mara
             INTO st_matkl
             WHERE matnr = st_header-matnr.
    ENDIF.
    st_header-matkl = st_matkl-matkl.
    MODIFY ct_ioheader FROM st_header.
ENDLOOP.
Regards,
Ravi

User Exit -- To include purchase requistion/purchase order in COOIS report

In a MTO envirnoment, trying to include purchase requistion/purchase order
with requested delivery date information in COOIS report. Is there a
user exit for this ?

Hi,
Please follow this an Example:-
The COOIS report (Order Info System) gives the complete information regarding Production Order like header report, Operation report, Component Report, document report.
This document deals with the addition of extra fields in the output display of COOIS.
For the demo purpose, I have added the material group (MATKL) for the production order material for header report.
BADI Name: WORKORDER_INFOSYSTEM
Method: TABLES_MODIFY_LAY
In the method TABLES_MODIFY_LAY there are many table parameters for different data display of the production order .In this scenario only the header detail structure is being extended with append structure.
Add the extra fields to be displayed to through append structure to IOHEADER_TAB, here MATKL.
In the method write the code for updating the field value.
DATA : BEGIN OF st_matkl,
           matkl TYPE matkl,
           END OF st_matkl.
DATA : st_header TYPE ioheader.
LOOP AT ct_ioheader INTO st_header.
    IF NOT st_header IS INITIAL.
      SELECT SINGLE matkl
             FROM mara
             INTO st_matkl
             WHERE matnr = st_header-matnr.
    ENDIF.
    st_header-matkl = st_matkl-matkl.
    MODIFY ct_ioheader FROM st_header.
ENDLOOP.
Regards,
Ravi

Access PSPAR in USER EXIT EXIT_SAPFP50M_001 - include ZXPADU01

Hi, Is it possible to access PSPAR in include ZXPADU01???? (PBAS0001 Enhancement)
I want the variable ACTIO from PSPAR.
In debugging mode when i tried ()PSPAR-ACTIO it s working, but when i tried it in report, showing error.
( '(' must follewed by atleast one space ).
Even PSPAR-ACTIO is also showing error.
How can i get that variable. Please give full details if possible.
Put it in other way........How can I know the action user done(create, display, change, copy??) in an user exit???
Veeranji.

Hi
I believe u need to use the field-symbols, that exit transfer the field TCLAS only, so not ACTIO
FIELD-SYMBOLS <FS> TYPE PSPAR.
DATA: FIELD_NAME(30) TYPE C VALUE '(<MAIN PROGRAM>)PSPAR'.
ASSIGN (FIELD_NAME) TO <FS>.
IF <FS>-ACTIO = ....
ENDIF.
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 PM

Can 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!

User Exit in include LVKMPFZ3 for Sales Order credt Check

Hi,
I am writing a code in include LVKMPFZ3 which is used for Credit Check for Customer in a Sales Order. It will be triggered only of I check the box for User3 in OVA8 for a combination of Customer credit group/Risk Category and Customer group.
Has any one worked on that.
regards,
Rishi bhatia

Hi Siarhei Mahulenka
I have used the same Export/Import Logic, and also I have written above code in Includes of both Forms
USEREXIT_SAVE_DOCUMENT_PREPARE
and
USEREXIT_SAVE_DOCUMENT.
I have applied breakpoint over here and my value is coming for
both XVBAK-LIFSK & VBAK-LIFSK (I have checked for both)
But again while I doing Debugging after some time in some other function module
both XVBAK-LIFSK & VBAK-LIFSK are becoming NULL.
I donot know how USEREXIT_SAVE_DOCUMENT is the last step for VA01.
Please tell me why again these two variables are becoming NULL.
Please guide me , I am stuck on this and remaining time for my this Task is very short.
Best Regards
Rishi Bhatia
Mobile: +91 9833637268

User include structure and routines/program/user exits

Hello Gurus,
     following is the step for modify the field catalog in material determination .
Modify the field catalog (OV26)
1.     Add the new field to the user include structure:
o     Header data KOMKDZ
o     Item data KOMPDZ.
2.     Add coding to the routines for assigning values to the new fields in order processing in program MV45AFZA. Use user exits:
o     USEREXIT_MOVE_FIELD_TO_KOMKD (header fields)
o     USEREXIT_MOVE_FIELD_TO_KOMPD (item fields)
3.     Add the new field to the field catalog (Customizing activity Basic Functions  Material Determination  Maintain prerequisites for material determination  Maintain field catalog).
Will you please tell me what the step 1 and step 2 mean ? and what 's the user include structure and USEREXIT_MOVE_FIELD_TO_KOMKD/USEREXIT_MOVE_FIELD_TO_KOMPD and program MV45AFZA ?
thanks very much!

Hi,
KOMKD is cummunication header and KOMPD is communication item which are actually contained in KOMGD structure. So automatically when you add a field to either of header or item it becomes a part of KOMGD. And moreover KOMGD contains all the fields of KOMKD and KOMPD which are required for materail determination.
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 ".
regards
sadhu kishore

Display error message in user-exit EXIT_SAPMP56T_002

Hi,
I'm doing a validation in user-exit EXIT_SAPMP56T_002 (include ZXTRVU03), and I want to display a error message. So, I'm using the instructions:
continue_with_update = 'N'.
MESSAGE ID xxx TYPE 'E' NUMBER yyy.
What happens is that in SAP GUI it works fine, but in SAP Portal it gives a lot of java exceptions.
Is there other way to display the error message that it works fine in the portal?
Thanks.
Sónia

Hi,
I tried with that but it doesn't work.
With the instruction "Message ID..." the portal shows an RFC ERROR SYSTEM FAILURE with all that java exceptions.
With your suggestion it does not retrieve my message, and instead it retrieves a customized message "Trip cannot be saved in this status, check mileage start and end location", that refers to the expense report and does not make any sense when I'm only creating the trip.
Any idea for this?
Thanks.
Sónia

User EXits

can any one help me out as how to find the USER EXITS , or INCLUDES
in functional module for any enhancement
Cheers

HI,
http://sap.niraj.tripod.com/id21.html
Check thi lin very useful to you.
Regards,
kishore.

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
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.
Regards
Eswar

User Exit / BAdI to update the pricing conditions of the Purchase Order

Hello SAPients,
This is my requirement:
"Copy the Pricing Conditions from the Shipment Cost Document (VI01 / VI02) to the automatically generated Purchase Order".
I'm using the enhancement V54U0002 (Function Module EXIT_SAPLV54U_002) to EXPORT the values of the Pricing Conditions to memory and I have used the enhancement MM06E005 ( FM EXIT_SAPMM06E_006, 007, 012, 013, 014, 016, and 017) to IMPORT the values from memory and store them in TKOMV. But, when the PO is generated the values don't stay, they are always changed with the standard PBXX pricing conditions.
My question is: Does anyone know the User Exit / BAdI that I can use to change the Pricing Conditions of the Purchase Order?
<<removed_by_moderator>>
Thanks!
Edited by: Vijay Babu Dudla on Jan 14, 2009 11:08 PM

>
kartik tarla wrote:
> check this badi
> ME_PROCESS_PO_CUST
>
> and the following user exit
> Goto-> include RV61AFZA then search for
> USEREXIT_PRICING_RULE see if its helpful to u.
Hello Kartik / SAPients,
I tried with ME_PROCESS_PO_CUST but didn't work. The system doesn't execute that code. Any other idea would be greatly appreciated.
Thanks.

Need help in user exits

Hi,
I am working on purchase req. enhancement,i developed a subscreen at item level with 9 fields. the screen is coming properly.when i enter data, i have to store this data in eban table. for this i append a str with those fields.How can i update this screen data in eban table.Have to implement another exit or can i write in PBO and PAI.What's the code i have to write here.Pls waiting for your reply.
Thanks in advance,
Avinas M.

Hello,
If you are using MEREQ001 user exit.
INCLUDE ZXM02U01                                                   *
                    Tables                                          *
tables: eban.
Reading current status of purchase requisition object and assigning to
local structure
data: s_mereq_item type mereq_item,
      s_temp type ref to if_purchase_requisition,
      s_trtyp type mepo_document.
call method im_req_item->get_data receiving re_data = s_mereq_item.
assiging data to the fileds on screen
move-corresponding s_mereq_item to eban.
*eban-zctarc = s_mereq_item-zctarc.
*eban-zuscno = s_mereq_item-zuscno.
*eban-zuscit = s_mereq_item-zuscit.
*eban-z1eldsze = s_mereq_item-z1eldsze.
*eban-z1especs = s_mereq_item-z1especs.
*eban-zalstr = s_mereq_item-zalstr.
*eban-znumcc = s_mereq_item-znumcc.
*eban-znumch = s_mereq_item-znumch.
*eban-znumsu = s_mereq_item-znumsu.
*eban-zinco1 = s_mereq_item-zinco1.
*eban-zinco2 = s_mereq_item-zinco2.
*eban-zcrnam = s_mereq_item-zcrnam.
*eban-zzterm = s_mereq_item-zzterm.
*eban-z1ecrrep = s_mereq_item-z1ecrrep.
*eban-z1etelfx = s_mereq_item-z1etelfx.
*eban-zektel = s_mereq_item-zektel.
*eban-matnr = s_mereq_item-matnr.
call method im_req_item->get_requisition receiving
re_requisition = s_temp.
call method s_temp->get_transaction_state importing ex_document =
s_trtyp.
export s_trtyp-trtyp to memory id 'TRT'.
and in
INCLUDE ZXM02U03                                                   *
                      Tables
tables : *eban.
data:     ls_mereq_item type mereq_item.
*get values if PReq item exists
if not im_req_item is initial.
*read item data from system
ls_mereq_item = im_req_item->get_data( ).
*if customer field changed
if eban ne *eban.
*fill field with new value
move-corresponding eban to ls_mereq_item.
   ls_mereq_item-zflag = eban-zflag.
*set new item data to system
    call method im_req_item->set_data( ls_mereq_item ).
*tell the system that there has something changed on the customer tab
    EX_CHANGED = 'X'.
endif.
endif.
Regards,
Shekhar Kulkarni

User exit not being called

Hi,
We have implemented user exit EXIT_SAPLMRMH_015, include ZXM08U26.
Problem 1:
When we tested in development system by processing a Idoc in debug, mode this user exit got called and the code in the user exit (include ZXM08U26) was executed.
Now we moved our changes to the quality system. Again we tested in quality by processing a idoc in debug mode. The user exit is getting called, but the code is not getting executed ( its not going inside include ZXM08U26). Why?
Problem 2:
In quality when I try to put break points in include ZXM08U26, a message pops up saying "The position of a breakpoint could not be ascertained". Why cant I put breakpoints?
The project (in CMOD) and the include (ZXM08U26) are all active in quality.
Thanks in advance.
Mick

When you create/change a project, you must create a correction. This correction contains only the attributes and the SAP enhancements associated with a project, as well as a program that is automatically started with the transport and activates the project in the target system. Since activating a project affects all components, you should transport all components associated with a project at the same time, in other words with the same transport request. To ensure that the project is activated automatically in the target system, the correction that contains the program concerned must also be in the same transport request. If this is not the case, or the project has not been activated in the target system for other reaons, you can also activate it by manually starting the program (RSMODACT).

ABEND in Java User Exit with RAW DataType

I have a Java User Exit Extract running against a trail file that has been pumped to the GoldenGate instance in question. The extract starts up without any issues, but gives the following error after I update a record that has a RAW datatype as the primary key:
JAVAWRITER(javawriter.c:269) [ERROR]: Error occurred (Java exception): UEDataSource.createOperation:
com.goldengate.atg.datasource.InvalidTransactionState: A new operation was received without first receiving a BEGIN transaction. This can happen when processing is resumed in the middle of a transaction, or when there are "before" images in the trail that are not being sent to the user exit (always include "GetUpdateBefores" in the user-exit parameter file).
I have tried a number of things to try to resolve this, but I can't seem to make this work. the params for this extract currently looks like this:
extract uePump
sourcedefs ./dirdef/my_defgen.def
setenv (GGS_USEREXIT_CONF = "dirprm/javaue.properties")
getupdatebefores
cuserexit ./dirprm/libggjava_ue.so CUSEREXIT passthru includeupdatebefores
table my_schema.B_PLN_DIR, fetchmodcols (PLN_DIR_ID, *);
table my_schema.*;
... I've tried leaving off the "includeupdatebefores" argument to the cuserexit, leaving out the fetchmodcols handling for the table with the RAW PK field, but I still get the error shown above.
Any help / pointers is much appreciated.

includeupdatebefores (lowercase) doesn't work; you must use the uppercase INCLUDEUPDATEBEFORES !!

Order entry user exit flags

I have a problem that I have tracked down to the code below.
In order entry through EDI, if a material is not on the customers buying list it is rejected by setting ABGRU. The problem occurs when the last 2 lines are rejected we get strange error messages like customer not maintained in dist channel xx or posting date is in the past.
At the end of the inbound orders user exit (EXIT_SAPLVEDA_001 include ZXVEDU03), we do this (see below) but I do not know why we set flag PBES = 'X' ?
What does it do?
When I remove the line setting PBES, it is OK
But before I can make a change to the live system I need to know what this does. Pls help
Update output parameters
    IF NOT xvbap-abgru IS INITIAL.
      d_flag_p      = dd_flag_p.
      d_flag_p-pbes = 'X'.
      d_flag_p-pde1 = 'X'.
      dd_flag_p     = d_flag_p.
      dxvbap        = xvbap.
Update Material No if mapped from EAN Code
    ELSE.
      dxvbap        = xvbap.
    ENDIF.

Hi,
You can maintain Production Storage location in BOM as well as you can maintain also in Material Master--> MRP-2 View--> Production Storage location.
So system will by default take the respective storage location and user need not select each time manually.
For this purpose, you need not implement any exit.
Revert in case any doubt.
Hope this solves your problem.
Regards,
Tejas

USER EXIT's include (ZXFYTU01)

Similar Messages

Maybe you are looking for