Urgent: User Exit Coding

Need help in missing coding for the below:
DATA : wa_var_range LIKE LINE OF i_t_var_range,
wa_e_t_range TYPE LINE OF rsr_t_rangesid.
When zmbpbrnd.
If I_step =2
Clear wa_e_t_range.
select * from zmbp_brand_auth where zmbp_de_brand= zmbpbrnd and xubname = sy-uname into I_brand.
if sy-subrc eq 0.
MOVE 'I' TO wa_e_t_range-sign.
MOVE 'EQ' TO wa_e_t_range-opt.
MOVE zmbp_brand_auth-zmbp_de_brand TO wa_e_t_range-low.
APPEND wa_e_t_range TO e_t_range.
Check I_step=2.
When zmbplgrp.
Clear wa_e_t_range
Select * from zmbp_brand_auth where zmbp_de_plangroup=zmbplgrp and xubname= sy-uname into I_plangroup.
if sy-subrc eq 0.
MOVE 'I' TO wa_e_t_range-sign.
MOVE 'EQ' TO wa_e_t_range-opt.
MOVE zmbp_brand_auth-zmbp_de_plangroup TO wa_e_t_range-low.
APPEND wa_e_t_range TO e_t_range.
Check I_step=2.
Endcase.
Thanks
Michelle

No case statement is already defined.
In select statement table is used for into which is not defined. need help in that
and then need help for writing loop where doing append need help in that
Points will be assigned.
Thanks
MK

Similar Messages

Urgent: User Exit (ZXM06U02) have some problem in coding.

Hi All,
This is regarding the user exit,
The present issue is.
When sending the PO to supplier portal, the outbound IDOC segment does not get populated properly. The text format = is again converted to space in ECC 6.0 which was not the case with 4.5B.
This is an upgrade issue as the function module used to format text FORMAT_TEXTLINES is completely different in ECC 6.0. The entire code of this function module in 4.5B has been commented in ECC 6.0 and new code has been implemented which splits the text and inserts spaces while formatting as shown below.
This issue can be resolved by implementing a customer exit which gets called after standard SAP populates the IDOC. It requires implementing custom code to remove the unwanted spaces inserted by standard SAP for text id F07. Hence after SAP completes its processing to populate the IDOC, the text would be processed further to remove unwanted spaces before actually sending the IDOC out from SAP R/3.
Thus this upgrade issue resolution requires R/3 development,
I write the code in exit include ZXM06U02:
Coding part:
DESCRIBE TABLE int_edidd LINES tabix.
READ TABLE int_edidd INDEX tabix.
IF int_edidd-segnam = 'E1EDPT2'.
 CLEAR E1EDPT1.
 CLEAR E1EDPT2.
Check whether its higher level segment E1EDPT1 has F07 in field E1EDPT1-TDID
by looking back internal table int_edidd
 w_tabix = tabix - c_1.
 w_i = tabix - c_1.
 DO w_tabix times.
 READ TABLE int_edidd INDEX w_i.
 IF int_edidd-segnam = 'E1EDPT1'.
 MOVE int_edidd-sdata TO E1EDPT1.
 EXIT.
 ENDIF.
 w_i = w_i - 1.
 ENDDO.
 IF E1EDPT1-TDID = 'F07'.
 READ TABLE int_edidd INDEX tabix.
 MOVE: int_edidd-sdata TO e1edpt2.
Remove unwanted Space(s) in field E1EDPT2-TDLINE
 CONDENSE E1EDPT2-TDLINE.
 MOVE E1EDPT2 TO int_edidd-sdata.
 MODIFY int_edidd INDEX tabix.
 ENDIF.
ENDIF.

But the code statement 'CONDENSE E1EDPT2-TDLINE.' does not work for removing space.
i did not understand why the code is not working properly.
Could any one please explain how write the code for condense the text with out spaces ASAP.
Thanks,
sridhar

"Condense" will leave one space between words by default... so you may want to add "no-gaps" on the end i.e. "CONDENSE E1EDPT2-TDLINE no-gaps." to eliminate all spaces between the words.
Jonathan

Urgent: USER exit for W2 Box 13 of Tax reporter 4.7

Hi,
I am working on tax reporter version 4.7 and while printing the W2 forms saw that the Box 13 (selection of Statutory employee or Retirment plan or third party sick pay ) is not ticked. I worked in one of the clients on ECC 6.0 last year whom had a custom user exit for this same box 13 of W2 which used to get ticked on W2 form depending on the logic in that user exit.
I suggested to this present client that an user exit needs to be written, they asked me to write functional specs for the user exit, can someone help me in writing the functional specs for this W2 form Box 13 selection of Tax reporter on 4.7. what do I need to specify and how do i need to write the functional specs reflecting the logic of this Box 13 of W2 form in tax reporter. Please help me guys, its very urgent.
I apprecite your answers.
Thank you so much
Tony

Hi Oscar Romero,
Sorry its an typo error. second range should be 001.2006 to 007.2006.
1. I want to know how to create Multiple Interval(Range) value variable? - I have used selection option and created variable. Is it correct?
2. Pls find my coding.
when 'ZFISCYAC'.
IF I_STEP = 2.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZFYPEROP'. ---> Value entered is 001.2005 - 012.2006
CLEAR L_S_RANGE.
L_S_RANGE-LOW = LOC_VAR_RANGE-LOW(4).
L_S_RANGE-LOW4(3) = LOC_VAR_RANGE-LOW4(3).
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZSCENAR'. -
> Value entered 20060804, 20060705.
*concatenate LOC_VAR_RANGE-LOW(4) '0' LOC_VAR_RANGE-LOW+4(2)
*into L_S_RANGE-high.
L_S_RANGE-high = LOC_VAR_RANGE-LOW(4).
L_S_RANGE-high+4(1) = '0'.
L_S_RANGE-high5(2) = LOC_VAR_RANGE-LOW4(2).
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'BT'.
APPEND L_S_RANGE TO E_T_RANGE.
ENDLOOP.
ENDLOOP.
ENDIF.
Final range should be for 20060804, "ZFISCAY" should be from 001.2005 to 008.2006
For 20060705 range should be 001.2005 to 007.2006.
*Coding for Filling variable "Fiscal year/Period Plan Multiple values
when 'ZFISCYPL'.
IF I_STEP = 2.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZSCENAR'.
CLEAR L_S_RANGE.
L_S_RANGE-LOW = LOC_VAR_RANGE-LOW(4).
L_S_RANGE-LOW+4(2) = '00'.
L_S_RANGE-LOW6(1) = LOC_VAR_RANGE-LOW4(2) + 01.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZFYPEROP'.
L_S_RANGE-HIGH = LOC_VAR_RANGE-high(4).
L_S_RANGE-HIGH4(3) = LOC_VAR_RANGE-high4(3).
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'BT'.
APPEND L_S_RANGE TO E_T_RANGE.
ENDLOOP.
ENDLOOP.
ENDIF.
With same variable values entered as above plan value for variable "ZFISCPL" should be of range 009.2006 to 012.2006 for 20060804
Range should be 008.2006 to 012.2006 for 20060705.
Hope this is clear.
Pls answer very urgent.
Thanks.
Bhuvana.

User exit coding in FBE1

Hi,
We want to do some external coding in tcode FBE1 for checking the posting date and due date of the invoice document number before saving the document. Pl. suggest the name of correct user exit where we can do this coding.
Regards,
rajesh.

hi
you can use the validation for documents line items

Urgent user exits

Hi,
how to make a user exit for the particular field in the idoc .That is when i want to change a field value in idoc with some condition it should not reflect in the outbound values but it should effect in inbound .please tell me detailly .

Hai Amit Teja
Check the following Field Exit Creation for Idoc fields
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
- Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
- An easy way to determine the data element associated to a particular screen field is to:
Go the appropriate screen.
Position the cursor in the appropriate field.
Press eF1f for field-level help.
Click on the eTechnical infof pushbutton (or press eF9f) on the help dialog box.
On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
Step 2: Go To Field Exit Transaction
- The transaction to create field exits is CMOD.
- You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
- From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
- 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
- From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
- After choosing this menu path, a dialog box will prompt you for the appropriate data element .
- Enter the data element name and click the eContinuef pushbutton.
- Now, you will be able to create the function module associated to the data elementfs field exit.
Step 4: Create Function Module
- You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the eContinuef pushbutton.
- In the eFunction modulef 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>
- You can add an identifier (an underscore followed by a single character ).
- The first function module for a data elementfs field exit must be created without an identifier.
- To create the function module, click on the eCreatef pushbutton, choose menu path Function module -> Create, or press eF5f.
- 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 eEnterf, you will be able to go ahead and create the function module.
- 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
- From the function modulefs attributes screen, click on the eSource codef pushbutton or choose the Goto -> Function module menu path to the code of the function module.
- Here you will add your desired functionality for the field exit.
- Remember that field exitfs 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.
- 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
- After coding the function module, you must remember to activate it.
- Use the Function module -> Activate menu path to activate the function module.
- At this point, you can return to the field exit transaction.
- You should be able to 'green arrow' back to this transaction.
- When you return to the field exit transaction, you will see an entry for the newly created field exit.
- 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.
- Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
- This step is only needed if you want to make a field exit local.
- To make a field exit local, select the field exit and click on the eAssign prog./screenf pushbutton.
- 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.
- In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the eFld. Exitf field.
- If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
- 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
- The field exit must be active for it to be triggered by the system.
- Activate the field exit by choosing the Field exit -> Activate menu path.
- After assigning the field exit to a change request, its status will change to eActivef 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
Thanks & regards
Sreenivasulu P

Urgent user exit

dear friends
Developed user exits which will automatically assign the order type with purchase order number while making a Purchase Order using Customer functions. (ME21N)
Developed user exit while making Release strategy after release the P.O if any lower level changes the P.O gives information message and exit the screen.(ME28)
pl. send to my mailid. [email protected]

Hi,
For ME21N;
User-Exits;
MEQUERY1
MEVME001
MM06E001
MM06E003
MM06E004
MM06E005
MM06E007
MM06E008
MM06E009
MM06E010
MMAL0001
MMAL0002
MMAL0003
MMAL0004
MMDA0001
MMFAB001
MRFLB001
MELAB001
AMPL0001
LMEDR001
LMELA002
LMELA010
LMEQR001
LMEXF001
LWSUS001
M06B0001
M06B0002
MEFLD004
MEETA001
ME590001
M06E0005
M06E0004
M06B0005
M06B0004
M06B0003
BADI's
ME_PROCESS_PO
ME_PROCESS_COMP
ME_PO_SC_SRV
ME_PO_PRICING_CUST
ME_PO_PRICING
ME_INFOREC_SEND
ME_HOLD_PO
ME_GUI_PO_CUST
ME_FIELDSTATUS_STOCK
ME_DP_CLEARING
ME_DEFINE_CALCTYPE
ME_COMMTMNT_REQ_RE_C
ME_COMMTMNT_REQ_RELE
ME_PROCESS_PO_CUST
SMOD_MRFLB001
MM_EDI_DESADV_IN
MM_DELIVERY_ADDR_SAP
ME_WRF_STD_DNG
ME_TRIGGER_ATP
ME_TRF_RULE_CUST_OFF
ME_TAX_FROM_ADDRESS
ME_REQ_POSTED
ME_REQ_OI_EXT
ME_RELEASE_CREATE
ME_PURCHDOC_POSTED
ME_PROCESS_REQ_CUST
ME_PROCESS_REQ
ME_COMMTMNT_PO_REL_C
ME_CCP_BESWK_AUTH_CH
ME_CCP_ACTIVE_CHECK
ME_BSART_DET
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC
ME_ACTV_CANCEL_PO
MEGUI_LAYOUT
EXTENSION_US_TAXES
ARC_MM_EKKO_WRITE
ARC_MM_EKKO_CHECK
ME_CCP_DEL_DURATION
ME_COMMTMNT_PO_RELEV
ME_COMMITMENT_STO_CH
ME_COMMITMENT_RETURN
ME_CIP_REF_CHAR
ME_CIP_ALLOW_CHANGE
ME_CIN_MM06EFKO
ME_CIN_LEINRF2V
ME_CIN_LEINRF2R
ME_CHECK_SOURCES
ME_CHECK_OA
ME_CHECK_ALL_ITEMS
ME_CHANGE_OUTTAB
ME_CHANGE_CHARACTER
For ME28;
User Exits;
MEQUERY1
MEVME001
MM06E001
MM06E003
MM06E004
MM06E005
MM06E007
MM06E008
MM06E009
MM06E010
MMAL0001
MMAL0002
MMAL0003
MMAL0004
MMDA0001
MMFAB001
MRFLB001
MELAB001
AMPL0001
LMEDR001
LMELA002
LMELA010
LMEQR001
LMEXF001
LWSUS001
M06B0001
M06B0002
MEFLD004
MEETA001
ME590001
M06E0005
M06E0004
M06B0005
M06B0004
M06B0003
BADI's
******************ME_PROCESS_PO
ME_PROCESS_COMP
ME_PO_SC_SRV
ME_PO_PRICING_CUST
ME_PO_PRICING
ME_INFOREC_SEND
ME_HOLD_PO
ME_GUI_PO_CUST
ME_FIELDSTATUS_STO
ME_DP_CLEARING
ME_DEFINE_CALCTYPE
ME_COMMTMNT_REQ_RE
ME_COMMTMNT_REQ_RE
ME_PROCESS_PO_CUST
SMOD_MRFLB001
MM_EDI_DESADV_IN
MM_DELIVERY_ADDR_S
ME_WRF_STD_DNG
ME_TRIGGER_ATP
ME_TRF_RULE_CUST_O
ME_TAX_FROM_ADDRES
ME_REQ_POSTED
ME_REQ_OI_EXT
ME_RELEASE_CREATE
ME_PURCHDOC_POSTED
ME_PROCESS_REQ_CUS
ME_PROCESS_REQ
ME_COMMTMNT_PO_REL_C
ME_CCP_BESWK_AUTH_CH
ME_CCP_ACTIVE_CHECK
ME_BSART_DET
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC
ME_ACTV_CANCEL_PO
MEGUI_LAYOUT
EXTENSION_US_TAXES
ARC_MM_EKKO_WRITE
ARC_MM_EKKO_CHECK
ME_CCP_DEL_DURATION
ME_COMMTMNT_PO_RELEV
ME_COMMITMENT_STO_CH
ME_COMMITMENT_RETURN
ME_CIP_REF_CHAR
ME_CIP_ALLOW_CHANGE
ME_CIN_MM06EFKO
ME_CIN_LEINRF2V
ME_CIN_LEINRF2R
ME_CHECK_SOURCES
ME_CHECK_OA
ME_CHECK_ALL_ITEMS
ME_CHANGE_OUTTAB
ME_CHANGE_CHARACTER

URGENT User exit for Trans FB60

Hi
   I need a little help with a requirement, I have a trans FB60 enter vendor invoice, In the reference field the put a tracking number. The requirement is when they enter the tracking number in the reference field and it is identical to the vendor which is possible. They want a pop up warning. I cannot seem to find a user exit that will work. I tried putting a breakpoint in a few of the includes but they do not seem to be getting hit by the transaction. Any ideas again the Trans is FB60 and the program is SAPMF05A.. several user exits exist but none seem to allow me to do what is required
Thanks

Hello,
Alternatively, you can use the open FI interface. Very good tool that not many people know.
1. Copy FM SAMPLE_INTERFACE_00001025 to Z_YOUR_FM
E.G:
FUNCTION Z_YOUR_FM.
""Local Interface:
*" IMPORTING
*"     VALUE(I_BKDF) LIKE BKDF STRUCTURE BKDF OPTIONAL
*" TABLES
*"      T_AUSZ1 STRUCTURE AUSZ1 OPTIONAL
*"      T_AUSZ2 STRUCTURE AUSZ2 OPTIONAL
*"      T_AUSZ3 STRUCTURE AUSZ_CLR OPTIONAL
*"      T_BKP1 STRUCTURE BKP1
*"      T_BKPF STRUCTURE BKPF
*"      T_BSEC STRUCTURE BSEC
*"      T_BSED STRUCTURE BSED
*"      T_BSEG STRUCTURE BSEG
*"      T_BSET STRUCTURE BSET
*"      T_BSEU STRUCTURE BSEU OPTIONAL
IF sy-uname = 'MKLEMBA'.
    BREAK-POINT.
ENDIF.
ENDFUNCTION.
2. TAC FIBF ( IMG Financial Accounting > Financial Accounting Global Settings > Business Transaction Events )
settings > product > of customer
Create a new product, e.g. ZZTEST. Make it active.
settings > p/s modules > of customer
00001025 ZZTEST Z_YOUR_MODULE
Have a good try!
Michal

Urgent: User exit for ME22N and ME32K transactions

I need to know a user exit(s) for changing Purchase Order and Contract line item fields from EKPO table. Please let me know if you know any. BADIs are also fine if the user exit does not exits. Thanks

Dear AP,
   I'm enlisting all the exits :-
Transaction Code - ME22N             Change Purchase Order
Exit Name
Description
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
No of Exits:         35
Transaction Code - ME32K                   Change Contract
|Exit Name|Description                                   |
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
No of Exits:         35
Regards,
Deva.

URGENT: user exit& customer exit

hi every body,
pls let me know the difference between USER EXIT& CUSTOMER EXIT.and How& What Type of the TICKETS are received in realtime.is there any tool for receiving the tickets in SRM.
Generally how many USERS are must for implementing the SRM project in real time.
which implementation scenario is best for INDIA?&Why.
i am requesting the GURUS please send me the detailed answers asap...............points will be rewarded soon.
thanks
warm regards
rakhi

Hi,
For difference between USER EXIT& CUSTOMER EXIT,see this very good related thread:
Re: user exit vs customer exit
BR,
Disha.
Do reward points for useful answers.

Urgent-- User Exit- FB01. Changing field BSEG-XREF3

Hi,
I need a user exit for FB01. I need to give vendor name in field BSEG-XREF3.
Please specify exact user exit for this purpose as I already have list of exits being used by FB01.
Points will be awarded for best answers.
Regards,
Navin

hi
use this steps to find all the exits of fb01
Finding the user-exits of a SAP transaction code
Enter the transaction code in which you are looking for the user-exit
and it will list you the list of user-exits in the transaction code.
Also a drill down is possible which will help you to branch to SMOD.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
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.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
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.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
call transaction 'SMOD' and skip first screen.

Restriction of BAPI_TRANSACTION_COMMIT in User Exit

Dear Experts,
I am trying to create Sales Order upon saving Purchase Order through user exit EXIT_SAPMM06E_012 using BAPI_SALESORDER_CREATEFROMDAT2.But i got to know that ...we should not use BAPI TRANSACTION COMMIT in user exits as it leads to data inconsistency.....Can any one please let me know the other way other around..
Regards,
Kartheek.

Don't call BAPI_TRANSACTION_COMMIT or COMMIT WORK anywhere in your user exit coding that is all )
Really, SAP will save your sales order when the purchase order will be committed and saved.
It doesn't matter where the COMMIT happens so far it happens within same LUW. Now if you are calling BAPI to create sales order within EXIT_SAPMM06E_012 and don't do a COMMIT in anyway then the purchase order save will automatically commit it.
I think EXIT_SAPMM06E_012 is an ideal place to call the sales order create BAPI as it is just called before the PO is saved. If for some reason PO doesn't save and ROLLBACK occurs then your sales order also won't get created.

Doubt in Idoc user exit..............

Hi All,
 i have written the user exit for Sales Order subscreen tab called additional data2 , this tab is provided by sap for developer can write their own user exit coding.
 my doubt is whenever PO comes as an Inbound IDOC i need to pass the value from segment to my user exit fields.
 where can i find the inbound idoc user exit for SO .
 Thanks in advance,
Regards,
Saravanan.

Look at enhancement VEDA0001. It has got quite a few user exits you can use. You will also need to enhance the IDOC for the additional fields you have added on your screen.
Cheers,
Sanjeev

User exit of va01

need help in user exit coding i.e. the requirement is like this.
Exit is V09A0004.
After entering the sold to party in VA01,one pop up comes when we press enter.
In that pop up we can see SH,BP,PY.From that if we select SH and that SH having account group 'zjst' then that default values of BP, PY should be override with that SH partner selected.
And also user not be able to enter any values in that BP,PY after overriding.
do we need to modify userexit_save_document_prepare .If how can we do that whole thing.
Pls help me in this.
Thanks.

need help in user exit coding i.e. the requirement is like this.
Exit is V09A0004.
After entering the sold to party in VA01,one pop up comes when we press enter.
In that pop up we can see SH,BP,PY.From that if we select SH and that SH having account group 'zjst' then that default values of BP, PY should be override with that SH partner selected.
And also user not be able to enter any values in that BP,PY after overriding.
do we need to modify userexit_save_document_prepare .If how can we do that whole thing.
Pls help me in this.
Thanks.

New User Exit ABAP help Needed

Hi ABAPers.
I need some help please
PLease give me the coding for the following scenario
if a user exists in table usgrp_user with user group 'x'
allow that user to post to GL account HKONT '441100' without a trading partner VBUND
If not, then issue message
thanks so much guys
Brian

Hello
Check with ABAPer on the user exit coding. Once done create a substitution rule and assign the user exit there.
Reg

Doubt In VA01 User Exit........

Hi,
we are using sap4.7. In VA01 ( sales Order ) we have a tab called additional data B. where we can write our own user exit coding.
my doubt is where can i find user exit enhancement. i tried in smod t.code but i am not able to find. can any one tell me the enhancement name if you already done.
thank you,
Regards,
Saravanan.

Check out this documentation.....
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
Under user exits>user exits in sales>user exits in sales document processing
Regards,
Rich Heilman

Urgent: User Exit Coding

Similar Messages

Maybe you are looking for