USER EXIT MB_CF001 NOT GETTING TRIGGERED

Hi All,
I am using EXIT_SAPLMBMB_001(MB_CF001)
I want it to be triggered after the document has been saved but its not trigeering..
How can I find out the reason???
Regards
Shilpa

Hi,
have you checked documentation for that enhancement? That function module is not called after goods movement creation.
The user exit MB_CF001 includes a function module that is called up
immediately before the COMMIT WORK when a goods movement is posted.
How do you test that FM? Some function modules from user exits are called in UPDATE TASK so they just ignore break points. In this case you can use the following trick. You need to enter an infinite loop into your user exit. Then you can connect to this program via transaction SM50 (Program/Session -> Program -> Debugging).
Cheers

Similar Messages

LT09 - Transfer Order User Exit is not getting trigerred though its active

Hi,
I am trying to assign the enhancement : MWMTO001
( Enhancements for end of transfer order generation )
which contains the user exit component : EXIT_SAPLL03T_001
I have created a project in CMOD and assigned the enhancement.
When I execute the TCode LT09 for transfer order, I noticed that this exit is not getting trigerred ...
I need to call a smartform whenever we save the data in the T-code LT09.
Am i using a wrong Exit ? Please help me to find out why this exit is not getting triggered though its activated ....
Thanking you in advance..
Nagasubramanyam.

Hi
Thank you for reply.
According to 1st scenario prgm is activated & also activated enhancement in CMOD.
According to 2nd scenario, can u suggest how to find out the correct exit...
Actually I written a print prgm in include of EXIT_SAPLL03T_001 & designed SMARTFORM for that...
if I do process thru LT09 transaction & save that SMARTFORM should be triggered which is not happening...I put break points & tried but the exit is not triggering.
pls suggest how to find out the correct exit of LT09 .
Thanks&Regards
NagaSubramanyam.

Enable User task is not getting triggered

Hi All
We have a provisioning workflow configured. "Enable User" task is not getting triggered while the user is enabled in OIM. Can anyone give a clue as to how to get it triggerd? Rest all the tasks are fine (Create, Disable, Delete, and other custom tasks)
Thanks,
Vinay

There is a OOTB scheduled Task "Enable After Start Date". once the user get enabled in OIM user profile. You have to run this task manually to have effect on corresponding RO for enablement. Else it will execute automatically as per scheduled time.
if the version of OIM is 11.1.1.5. There is an issue. update patch BP02. for same
--nayan

Events in USER objects type not getting triggered in PFCG

Hi,
We need to send some notifications to the concern person at the time of assiging roles to the user . There is an object type USER and has events like created,cloned, deleted, roles_changed. But these events not getting triggered.
I need to trigger the workflow. How do we activate the events as the entry doesnot exits in SWE2 tooo . Is ther any other way?

HI munish
If the entry is not in swe2 Put the entry for the business object USER and use the receiver type as your workflow number.
Regards
vijay

User command is not getting triggered in interactive ALV with LIST display

Hi experts,
I have developed an interactive ALV report with LIST display. Here, the issue is, when i double click a record in the primary ALV list, the control must go to the USER COMMAND event which i have written in my report. But the user command event is not getting triggered at all when i double click any record.
It gives the following information instead.
"Choose a valid function".
(My user command name and its respective form name are same.)
Here is my code..
START-OF-SELECTION.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
      i_callback_program       = sy-repid
      i_structure_name         = p_table
      i_callback_user_command = 'TST1'
      i_callback_pf_status_set = 'SET_PF_STATUS'
    TABLES
      t_outtab                 = <dyn_table>
    EXCEPTIONS
      program_error            = 1
      OTHERS                   = 2.
IF sy-subrc <> 0.
ENDIF.
FORM tst1 USING r_ucomm LIKE sy-ucomm
                rs_selfield TYPE slis_selfield.
* Local data declaration
DATA: li_tab TYPE REF TO data,
        l_line TYPE REF TO data.
* Local field-symbols
FIELD-SYMBOLS:<l_tab> TYPE table,
                <l_wa> TYPE ANY.
* Create table
CREATE DATA li_tab TYPE STANDARD TABLE OF (p_table).
ASSIGN li_tab->* TO <l_tab>.
* Create workarea
CREATE DATA l_line LIKE LINE OF <l_tab>.
ASSIGN l_line->* TO <l_wa>. CASE r_ucomm.
*   When a record is selected
    WHEN '&IC1'.
*     Read the selected record
      READ TABLE <dyn_table> ASSIGNING <dyn_wa> INDEX
      rs_selfield-tabindex.      IF sy-subrc = 0.
*       Store the record in an internal table
        APPEND <dyn_wa> TO <l_tab>.
*       Fetch the field catalog info
        CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
          EXPORTING
            i_program_name         = 'Z_DEMO_PDF_JG'
            i_structure_name       = p_table
          CHANGING
            ct_fieldcat            = i_fieldcat
          EXCEPTIONS
            inconsistent_interface = 1
            program_error          = 2
            OTHERS                 = 3.
Please advice what is the msitake i have done here..

Read the following code:
pass the i_callback_user_command = g_user_command to the ALV function module and write the FORM user_command USING ucomm    LIKE sy-ucomm
                        selfield TYPE slis_selfield.
as shown below.
thanx
Data for ALV display
DATA : gt_fieldcat TYPE slis_t_fieldcat_alv,
        gt_events           TYPE slis_t_event,
        g_variant LIKE disvariant,
        g_user_command      TYPE slis_formname VALUE 'USER_COMMAND',
        g_status            TYPE slis_formname VALUE 'SET_PF_STATUS',
        gt_list_top_of_page TYPE slis_t_listheader,
        g_repid LIKE sy-repid,
        gf_pos TYPE i
Data for ALV display
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
           EXPORTING
          i_callback_program      = g_repid
             i_callback_program      = sy-repid
             it_fieldcat             = gt_fieldcat[]
       it_events               = gt_events[]
          i_callback_user_command = g_user_command
             i_save                  = 'A'
             is_variant              = g_variant
           TABLES
             t_outtab                = it_print.
FORM user_command USING ucomm    LIKE sy-ucomm
                        selfield TYPE slis_selfield.
CASE ucomm.
    WHEN '&IC1'.
      CASE selfield-sel_tab_field.
        WHEN '1-KUNNR'.
          READ TABLE it_print INTO wa_print INDEX selfield-tabindex.
          IF sy-subrc = 0.
            SET PARAMETER ID 'BPA' FIELD wa_print-kunnr.
            CALL TRANSACTION 'BP'.
          ENDIF.
        WHEN '1-MATNR'.
          READ TABLE it_print INTO wa_print INDEX selfield-tabindex.
          IF sy-subrc = 0.
            SET PARAMETER ID 'JP_ISS' FIELD wa_print-matnr.
            CALL TRANSACTION 'JP29' AND SKIP FIRST SCREEN..
           GET PARAMETER ID 'WRK' FIELD wa_zprint-werks.
           SET PARAMETER ID 'VKO' FIELD wa_zprint-vkorg.
           SET PARAMETER ID 'VTW' FIELD wa_zprint-vtweg.
           CALL TRANSACTION 'JP29' AND SKIP FIRST SCREEN.
          ENDIF.
Endcase.
Endform.

Overhead user exit (COOM0001) not being triggered for specific plant

Hello all,
I was wondering if anyone came across this situation before. I activated user exit COOM0001 for overhead calculation. This user exit is triggered when I create PCE for plant A but not plant B.
I can't figure out why it is not being triggered for plant B at all. I put a break point in function module EXIT_SAPLKASC_001, EXIT_SAPLKASC_002 and EXIT_SAPLKASC_003 and the system didn't stop in anyone of these function module.
Any help is greatly appreciated.
Regards,
Cassandra

Hi
It seems that you are a Functional Consultant.
Please follow the following simple step for any userexit to see where all its been called.
1. Go To T. Code SMOD
2. Enter the Exit name COOM0001
3. Click on the COMPONANTS RADIO BUTTON and DISPLAY
4. U get Function Modules
EXIT_SAPLKASC_001
EXIT_SAPLKASC_002
EXIT_SAPLKASC_003
5. Now individually double click on each FM and put a break point ther.
6. Open a new session and see wheather it stop at the break-points of the T. code you are looking for.
I havent used this user exit, so no comments on how it ll be use ful.
Reward points if useful
Thank-You
regards
vinsee

User Exit not getting triggered

Dear all,
we are creating a workflow for PR Release which needed release strategy customization. so we are trying to set the release stratagy by changing the communciation structure CEBAN-USRC1 field.
for this, i had done the following things:
1. SMOD->M06B0005->components->EXIT_SAPLEBND_004->INCLUDE ZXM06U31 (double clicked) wrote few lines of code.
2. CMOD-> created a proj ZMM_PREL->assigned Enhancement M06B0005 under enhancements tab-> EXIT_SAPLEBND_004-> activated all
(User exit, project eveything).
Now my problem is when i create a PR, this user exit does not get triggered at all. I am working on ECC6.0 the same code which i did in Ecc5.0 for my previous client is still working fine.
Can anyone please guide me where i might have gone wrong?
Thank you,
Regards,
Lakshmi

Hi,
HAve u verifiyed that the user-exit u r using is triggered whenever u create ou PR.?
First of all u have to put breakpoints at each and every user-exits provided for that transaction, then check which user exit is getting triggered when u carete ur PR. and thenafter write ur code in this user-exit only.
Reward is useful.
Regards,
Harsha

User Exit not getting Triggered in Quality Server

Hi,
In FM 'IDOC_INPUT_DESADV' Iam using an User Exit 'EXIT_SAPLEINM_006' ,
which is getting triggered in Development server.But when I moved it to Quality,
The User Exit is not getting triggered.Thou the Exit is assigned to Enhancement
and that in turn is assigned to Project, still the problem persists.
Can any one suggest me what could be the problem.
Regards,
Kiran B.

Kiran,
Check the <b>Project</b> of that enhancement is active or not. not the enhancement.
<b><REMOVED BY MODERATOR></b>
Satish
Message was edited by:
Alvaro Tejada Galindo

User Exit RV60AFZZ not Triggered When Processing IDOC

Hi,
I'm writing to seek some advice on why is the user exit RV60AFZZ not getting triggered when I do a vf01 bdc inside my inbouund IDOC function module. But when I try SHDB the user exit is getting triggered normally.
Thanks,
Mawi

Hi,
Yes I'm creating invoice using delivery orders, inside the idoc function module I'm using bdc call transaction vf01 but somehow it does not trigger the user exit.
But when I do manual vf01 in sap, the user exit is getting triggered.
I cant figure out why this is the behavior of sap.
Regards,
Mawi

Userexit not getting triggered for 0CFM_CLASS_MASTER_DATA_ATTR

Hi Experts,
I have made enhancements to 0CFM_CLASS_MASTER_DATA_ATTR & 0CFM_FI_TRA_ATTR in RSAP0001(EXIT_SAPLRSAP_001). I have set the flag to New Data entry logic(Switch for Datasource feed) to populate the Timedependent attributes in 0CFM_CLASS_MASTER_DATA_ATTR .
I kept the break point in the Userexit and ran RSA3 for the above 2 datasources but the user exit is not getting triggered.
Can you please help why the userexit is not getting triggered?
Thanks,
bwuswer14.

Hi,
Thanks for ur post.issue resolved.im keeping the breakpoint in 1st user exit.After keeping the breakpoint in EXIT_SAPLRSAP_002 it got triggered.Closing the thread.
Thanks,
bwuser14

User exit MB_CF001 in MIGO

Folks,
I am using the user exit MB_CF001 to get the data from XMSEG table and send it to an external system. I was asked to call an RFC function module in this user exit to send the XMSEG data to an external system but the user exit documentation clearly says not to use RFC function call in this user exit.
I also heard that I can do this by using the idocs that get posted after MIGO is done. Could anyone give me step by step procedure how to do this as I am new to IDOCS.
Points will be rewarded for best answers.
Thanks,
Alok

Dear Alok,
Below is a documentation about IDOCs. Hope it will be useful to you.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
Important links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
>SAP ALE & IDOC
Steps to configuration(Basis)
>>1. Create Logical System (LS) for each applicable ALE-enabled client
>>2. Link client to Logical System on the respective servers
>>3. Create background user, to be used by ALE(with authorizaton for ALE postings)
>>4. Create RFC Destinations(SM59)
>>5. Ports in Idoc processing(WE21)
>>6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
>Steps to customize a new IDoc
>>1. Define IDoc Segment (WE31)
>>2. Convert Segments into an IDoc type (WE30)
>>3. Create a Message Type (WE81)
>>4. Create valid Combination of Message & IDoc type(WE82)
>>5. Define Processing Code(WE41 for OUT / WE42 for IN)
>>6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Best Regards,
Rajesh.
Please reward points if found helpful.

AT USER COMMAND is not getting triggerd

Hi Techie's
I have two fields on the selection screen
1) Name:   ___________
2) Id:         ___________
I have some buttons say on the Application toolbar say::
Save            Delete            Modify           Exit
I have created these buttons in the INITIALIZATION event.
I am using AT Selection Screen OUTPUT for some logic purpose.
Later I am writing AT USER COMMAND and pressing SAVE The function code for SAVE is "SAV".
But the drama is that AT USER COMMAND is not getting triggered at all.
It goes first to Initialization--->At selection Screen OUTPUT>Then screen appears> I give the values and press the SAVE button--
again it goes to the At Selection screen OUTPUT.
Not even getting the hang of it. Please help if anybody know the story of it.
ITS SO URGENT.

At user command is for list processing, you need something like this:
Pushbuttons in the Application Toolbar
In the application toolbar of the standard GUI status of the selection screen, five pushbuttons are predefined with the function codes FC01 to FC05, but are inactive by default. You can activate them during the definition of the selection screen as follows:
SELECTION-SCREEN FUNCTION KEY i.
The numbering i must be between 1 and 5. The individual function texts must be assigned to the functxt_0i components of structure sscrfields before the selection screen is called. You must declare this structure as an interface work area using the TABLES statement.
If the user chooses one of these buttons, the runtime environment triggers the AT SELECTION-SCREEN event and the function code FC0i is placed into the component ucomm of the structure sscrfields.
After the AT SELECTION-SCREEN event has been processed, the system displays the selection screen again. The only way to exit the selection screen and carry on processing the program is to choose Execute (F8). Consequently, the pushbuttons on the application toolbar are more suitable for controlling dynamic modifications of the selection screen than for controlling the program flow.
REPORT demo_sel_screen_function_key.
TABLES sscrfields.
PARAMETERS: p_carrid TYPE s_carr_id,
            p_cityfr TYPE s_from_cit.
SELECTION-SCREEN: FUNCTION KEY 1,
                  FUNCTION KEY 2.
INITIALIZATION.
sscrfields-functxt_01 = 'LH'.
sscrfields-functxt_02 = 'UA'.
AT SELECTION-SCREEN.
CASE sscrfields-ucomm.
      WHEN'FC01'.
      p_carrid = 'LH'.
      p_cityfr = 'Frankfurt'.
    WHEN 'FC02'.
      p_carrid = 'UA'.
      p_cityfr = 'Chicago'.
ENDCASE.
START-OF-SELECTION.
WRITE / 'START-OF-SELECTION'.
This defines a standard selection screen with two parameters. In the application toolbar, two pushbuttons are assigned the texts LH and UA and activated.
When the user clicks one of the buttons, the AT SELECTION-SCREEN event is triggered and there the input fields are preassigned correspondingly.

User-exit not getting triggered in VA32

Hello Experts,
Iu2019ve a requirement and Iu2019m working on Change Scheduling Agreement u2018t-code VA32u2019. According to requirement I need to capture all header data and data in Sales, Item Overview, Item Detail and Ordering party tabs. Iu2019ve set the break points in almost all the user-exits but only one FM (EXIT_SAPLV45L_002) of exit u2018V45L0001u2019 is getting trigger. Even though other exits/FM has all the tables as import/export parameters which I need but they are not getting triggered. Can anybody please tell me which user-exit / BADI I should use to capture the required data?
Thanks.

Hello Experts,
Thanks a lot Vijay for you reply. Iu2019ve seen user exits of MV45AFZZ include and looks like USEREXIT_SAVE_DOCUMENT_PREPARE is the correct user exit. But I havenu2019t use Includes before can you or anybody else please tell me how to write code in include. I know how to search an include in a program but not sure how to add code in the user exit.
Thanks

User exit not getting triggered while creating the vendor

Hi all,
I wanted to extend the idoc(crermas01) according to my reqiurement.
But when I am trying to create a vendor using the IDOC cremas01 the user exit EXIT_SAPLKD01_001 is not getting triggered.
Can anybody tell me the reason why it is happening so...........
Thanks and regards,
Vinil.

Is your Idoc generated after the execution?
Where is you break-point, it is inside EXIT_SAPLKD01_001. Please note FM EXIT_SAPLKD01_001 will not be called unless it is implemented using project (CMOD) and project is active.

Event not getting triggered for a few users in production

Hi Experts!!
We have a workflow that gets triggered on the event REQUESTCREATED of BUS2089. In production, we see that for a few users the event is getting triggered and even the workflow is. But for a few users, the workflow is not getting triggered. However, we didn't check SWEQADM yet and are waiting to get auth to check the same. But before that, I need your valuable suggestions on this.
When I check SWEL, I cannot see any entries at all. Not even for the successfully processed ones.
Auth objects cannot be a reason, as all the users have same auth. Please suggest me on what else can be the reasons.
Your help is highly appreciable.

Hello Srinivas !
              Check in SWEQADM to know whether the event is on queue.If so, redeliver it.
              If there is no event on queue, check the RFC queue( transaction SWU2 ) and ST22 for possible ABAP dumps.
              Call work item list report (transaction SWI1) and check event linkages (transaction SWETYPV )of the users for whom the event is not triggered.Are you using BAdI or user- exit to trigger the workflow ? If so, check whether those are in active state.
             Refresh the workflow buffers(transaction SWU_OBUF).Check either of the workflow versions are in active state.
Regards,
S.Suresh

USER EXIT MB_CF001 NOT GETTING TRIGGERED

Similar Messages

Maybe you are looking for