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

Similar Messages

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

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.

Event of delegeted Object type not showing up in event trace

Hi,
Please forgive me if this question has already been posted, I created a subtype for the object BUS2032 as ZSALESDOC and delegated the later the to the standard object type BUS2032 , but when i create a sales order it is not showing up in the event trace (TCODE : SWEL), only standard object type BUS2032 is showing up, and the ZSALESDOC object type's CREATED event is not showing up, Please i need inputs on any other thing i am missing out for delegating this object.
Regards
Narendiran Rathinavelu

Hi
check whether you have done the following after delegation:
Event creation in status management(BSVW)
Press Customer settings
New entries
enter status(VBK) - Your copied object type ZSALESDOC
Status Restrictions
I00002 (syst Status) ..REL (released)..SAVE and see once again
Reward points if useful
Regards
Anji

Multiple Number Ranges for AP Document Type not getting triggered

Hi all,
We are posting receivables in the system using BAPI_CTRACDOCUMENT_CREATE. We have huge data of 3.9 million records for which receivables has to be posted. So multiple number ranges has been configured in the system for AP document type.
The issue is even though multiple number ranges for mass processing are configured in the below location in SPRO, none of them are getting triggered. The number range at the first level on the screen is only getting triggered, due to this it is taking lot of time to post documents. Any help on this?
Financial Accounting(new)
     Contracts Accounts Receivable and Payables
     BasicFunctions
     Postings and Documents
     Document
     Maintain Document Assignments
     Document Types
     Maintain Document Types and Assign Number Ranges
Regards,
Karthick.

Karthick:
Mass ranges are only used for FICA parallel mass activities. For your situation, you can define and assign multiple ranges for individual processing in the same IMG activity. Those would then be chosen for your mass postings.
regards,
bill.

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

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

Due to MODIF ID, SELECT query in START-OF-SELECTION not getting triggered

Dear SAP Gurus,
I'm stuck with this program, where, my program is not being executed, as in, my SELECT query in my event START-OF-SELECTION is not getting triggered. Since i hav used MODIF ID, for SELECT-OPTIONS, even after putting the entries in select-options...................when i click on the execute button, or press F8, the program still goes into the AT SELECTION-SCREEN OUTPUT event..........but i want it to goto START-OF-SELECTION event where my SELECT query is........what should i do??????????????
Please find the notepad file having the code, n exucse me for any selection-texts absence.
Need help from u in this issue.
Thanks in advance.
REPORT ZPPR_CONVSTAT NO STANDARD PAGE HEADING.
INCLUDE ZPPR_CONVSTAT_TOP.               " data declaration
INCLUDE ZPPR_CONVSTAT_SEL_CRITERIA.      " selection criteria
INCLUDE ZPPR_CONVSTAT_PBO.               " event at selection-screen output
INCLUDE ZPPR_CONVSTAT_START_SELECTION.   " event start-of-selection
INCLUDE ZPPR_CONVSTAT_F_START_OF_SEL.
*& Include           ZPPR_CONVSTAT_TOP
TABLES : VBUK,
          VBUP,
          VBAK,
          VBAP,
          VBEP,
          VBPA,
          TVAK,
          EKUB,
          LIKP,
          LIPS,
          MARA,
          MAKT,
          MARC,
          PLAF,
          AUFK,
          AFKO,
          AFPO,
          AFVC,
          AFVV,
          CRHD,
          PBIM,
          KNA1,
          T134,
          IOHEADER,
          IOITEM.
TYPE-POOLS : slis.
TYPES : BEGIN OF ty_final,
        werks   TYPE vbap-werks, "Plant
        auart   TYPE vbak-auart, "Sales Order Doc. type
        erdat   TYPE vbak-erdat, "Sales Order Creation date
        vbeln   TYPE vbak-vbeln, "Sales Order No.
        posnr   TYPE vbap-posnr, "Sales Order Item No.
        aedat   TYPE vbak-aedat, "Sales Order Change Date
        kwmeng TYPE vbap-kwmeng, "Sales Order qty.
        vdatu   TYPE vbak-vdatu, "Requested Delivery Date
        lfimg   TYPE lips-lfimg, "Sales Order Delivered Qty.
        matnr   TYPE vbap-matnr, "Material ID
        arktx   TYPE vbap-arktx, "Material Description
        strgr   TYPE marc-strgr, "Planning Strategy
        vrkme   TYPE vbap-vrkme, "UOM
        plnum   TYPE plaf-plnum, "Plan Order No.
        gsmng   TYPE plaf-gsmng, "Plan Order Qty.
        auffx   TYPE plaf-auffx, "Plan Order Firming Indicator u2013 Qty.
        stlfx   TYPE plaf-stlfx, "Plan Order Firming Indicator - Component
        erdat2 TYPE aufk-erdat, "Production Order Creation Date
        aufnr   TYPE aufk-aufnr, "Production Order No.
        prdqty TYPE afko-gamng, "Production Order qty.
        pckqty TYPE lips-lfimg, "Packed Delivered Qty.
        psamg   TYPE afpo-psamg, "Allotted scrap
        igmng   TYPE afko-igmng, "Confirmed Yield Qty.
        iasmg   TYPE afko-iasmg, "Confirmed Scrap Qty
        iamng   TYPE afpo-iamng, "Expected Yield
        wemng   TYPE afpo-wemng, "Delivered Qty.
        altscrp TYPE c LENGTH 6, "Allotted Scrap %
        actscrp TYPE c LENGTH 6, "Actual Scrap %
        umrez   TYPE afvv-umrez, "Ups (from Prd. ORD)
        ups     TYPE clobjdat-ausp1, "Ups (from Material Master)
        crtnstl TYPE clobjdat-ausp1, "Carton Style
        ppopr   TYPE clobjdat-ausp1, "Pre-Printing Operation
        brdtyp TYPE clobjdat-ausp1, "Board Type
        lsdim1 TYPE clobjdat-ausp1, "Layout Size u2013 Dim 1
        lsdim2 TYPE clobjdat-ausp1, "Layout Size u2013 Dim 2
        lsgsm   TYPE clobjdat-ausp1, "GSM
        inktyp TYPE clobjdat-ausp1, "Ink Type
        foiltyp TYPE clobjdat-ausp1, "Foiling
        wintyp TYPE clobjdat-ausp1, "Window Type
        lamin   TYPE clobjdat-ausp1, "Lamination
        fsvrnsh TYPE clobjdat-ausp1, "Front Side Varnish
        bsvrnsh TYPE clobjdat-ausp1, "Back Side Varnish
        emboss TYPE clobjdat-ausp1, "Embossing
        punch   TYPE clobjdat-ausp1, "Punching
        paste   TYPE clobjdat-ausp1, "Pasting
        oprno   TYPE afvc-vornr,      "Operation No.
        wrkcntr TYPE crhd-arbpl,      "Work Centre
        oprtxt TYPE afvc-ltxa1,      "Operation Text
        oprqty TYPE afvv-mgvrg,      "Operation qty.
        yield   TYPE afvv-lmnga,      "Yield
        scrap   TYPE afvv-xmnga,      "Scrap
        jobtyp TYPE vbak-augru,      "Job Type
        prordst TYPE bsvx-sttxt,      "Production Order Status
        solinst TYPE vbup-lfsta,      "Sales Order Line Item Status
        sldprty TYPE kna1-name1,      "Sold to Party Name
        shpprty TYPE kna1-name1,      "Ship to Party Name
        shpcity TYPE kna1-ort01,      "Ship to party - City
        END OF ty_final.
TYPES : BEGIN OF ty_vbak,
        auart   TYPE vbak-auart,
        erdat   TYPE vbak-erdat, "Doc creation date
        vbeln   TYPE vbak-vbeln,
        aedat   TYPE vbak-aedat, "Doc change date
        vdatu   TYPE vbak-vdatu, "Requested delivery date
        kunnr   TYPE vbak-kunnr,
        augru   TYPE vbak-augru, "Job Type
        END OF ty_vbak.
TYPES : BEGIN OF ty_vbap,
        vbeln   TYPE vbap-vbeln,
        posnr   TYPE vbap-posnr,
        werks   TYPE vbap-werks,
        matnr   TYPE vbap-matnr,
        arktx   TYPE vbap-arktx,
        kwmeng TYPE vbap-kwmeng,
        vrkme   TYPE vbap-vrkme,
        END OF ty_vbap.
TYPES : BEGIN OF ty_pbim,
        pbdnr TYPE pbim-pbdnr, "Requirements Plan Number
        bdzei TYPE pbim-bdzei, "Independent requirements pointer
        matnr TYPE pbim-matnr,
        werks TYPE pbim-werks,
        END OF ty_pbim.
TYPES : BEGIN OF ty_pbhi,
        bdzei TYPE pbhi-bdzei, "Independent requirements pointer
        pdatu TYPE pbhi-pdatu, "Requirement date
        laeda TYPE pbhi-laeda, "Date of Last Change
        END OF ty_pbhi.
TYPES : BEGIN OF ty_ekko,
        ebeln TYPE ekko-ebeln, "STO doc no
        bsart TYPE ekko-bsart,
        reswk TYPE ekko-reswk, "Supplying plant
        aedat TYPE ekko-aedat, "Doc creation date
        END OF ty_ekko.
TYPES : BEGIN OF ty_ekpo,
        ebeln TYPE ekpo-ebeln,
        ebelp TYPE ekpo-ebelp,
        aedat TYPE ekpo-aedat, "Doc change date
        menge TYPE ekpo-menge,
        meins TYPE ekpo-meins,
        matnr TYPE ekpo-matnr,
        txz01 TYPE ekpo-txz01,
        END OF ty_ekpo.
TYPES : BEGIN OF ty_eket,
        ebeln TYPE eket-ebeln,
        ebelp TYPE eket-ebelp,
        eindt TYPE eket-eindt, "Requested delivery date
        END OF ty_eket.
TYPES : BEGIN OF ty_lips,
        vbeln TYPE lips-vbeln,
        posnr TYPE lips-posnr,
        vgbel TYPE lips-vgbel,
        vgpos TYPE lips-vgpos,
        lfimg TYPE lips-lfimg,
        END OF ty_lips.
TYPES : BEGIN OF ty_plaf,
        plnum TYPE plaf-plnum,
        matnr TYPE plaf-matnr,
        gsmng TYPE plaf-gsmng,
        auffx TYPE plaf-auffx,
        stlfx TYPE plaf-stlfx,
        kdauf TYPE plaf-kdauf,
        kdpos TYPE plaf-kdpos,
        pbdnr TYPE plaf-pbdnr,
        END OF ty_plaf.
TYPES : BEGIN OF ty_aufk,
        aufnr TYPE aufk-aufnr,
        erdat TYPE aufk-erdat,
        objnr TYPE aufk-objnr,
        END OF ty_aufk.
TYPES : BEGIN OF ty_afko,
        aufnr TYPE afko-aufnr,
        gamng TYPE afko-gamng, "Total order quantity
        gasmg TYPE afko-gasmg, "Total scrap quantity in the order
        igmng TYPE afko-igmng, "Confirmed Yield Qty
        iasmg TYPE afko-iasmg, "Confirmed Scrap Qty
        aufpl TYPE afko-aufpl, "Routing number of operations in the order
        END OF ty_afko.
TYPES : BEGIN OF ty_afpo,
        aufnr TYPE afpo-aufnr,
        plnum TYPE afpo-plnum,
        matnr TYPE afpo-matnr,
        pgmng TYPE afpo-pgmng, "Plan Order Qty
        kdauf TYPE afpo-kdauf,
        kdpos TYPE afpo-kdpos,
        psamg TYPE afpo-psamg, "Allotted scrap
        iamng TYPE afpo-iamng, "Expected Yield Variance
        wemng TYPE afpo-wemng, "Delivered Qty
        END OF ty_afpo.
TYPES : BEGIN OF ty_afvc,
        vornr TYPE afvc-vornr,
        aufpl TYPE afvc-aufpl, "Routing number of operations in the order
        aplzl TYPE afvc-aplzl, "General counter for order
        arbid TYPE afvc-arbid, "Object ID of the resource
        ltxa1 TYPE afvc-ltxa1,
        END OF ty_afvc.
TYPES : BEGIN OF ty_afvv,
        aufpl TYPE afvv-aufpl, "Routing number of operations in the order
        aplzl TYPE afvv-aplzl, "General counter for order
        umrez TYPE afvv-umrez,
        mgvrg TYPE afvv-mgvrg,
        lmnga TYPE afvv-lmnga,
        xmnga TYPE afvv-xmnga,
        END OF ty_afvv.
TYPES : BEGIN OF ty_mdvm,
        mdkey TYPE mdvm-mdkey,
        disst TYPE mdkp-disst,
        matnr TYPE mdkp-matnr,
        plwrk TYPE mdkp-plwrk,
        END OF ty_mdvm.
DATA : it_final TYPE STANDARD TABLE OF ty_final,
        it_vbak   TYPE STANDARD TABLE OF ty_vbak,
        it_vbap   TYPE STANDARD TABLE OF ty_vbap,
        it_lips   TYPE STANDARD TABLE OF ty_lips,
        it_pbim   TYPE STANDARD TABLE OF ty_pbim,
        it_pbhi   TYPE STANDARD TABLE OF ty_pbhi,
        it_ekko   TYPE STANDARD TABLE OF ty_ekko,
        it_ekpo   TYPE STANDARD TABLE OF ty_ekpo,
        it_eket   TYPE STANDARD TABLE OF ty_eket,
        it_plaf   TYPE STANDARD TABLE OF ty_plaf,
        it_aufk   TYPE STANDARD TABLE OF ty_aufk,
        it_afko   TYPE STANDARD TABLE OF ty_afko,
        it_afpo   TYPE STANDARD TABLE OF ty_afpo,
        it_afvc   TYPE STANDARD TABLE OF ty_afvc,
        it_afvv   TYPE STANDARD TABLE OF ty_afvv,
        it_mdvm   TYPE STANDARD TABLE OF ty_mdvm.
DATA : wa_final TYPE ty_final,
        wa_vbak   TYPE ty_vbak,
        wa_vbap   TYPE ty_vbap,
        wa_lips   TYPE ty_lips,
        wa_pbim   TYPE ty_pbim,
        wa_pbhi   TYPE ty_pbhi,
        wa_ekko   TYPE ty_ekko,
        wa_ekpo   TYPE ty_ekpo,
        wa_eket   TYPE ty_eket,
        wa_plaf   TYPE ty_plaf,
        wa_aufk   TYPE ty_aufk,
        wa_afko   TYPE ty_afko,
        wa_afpo   TYPE ty_afpo,
        wa_afvc   TYPE ty_afvc,
        wa_afvv   TYPE ty_afvv,
        wa_mdvm   TYPE ty_mdvm.
DATA : it_object TYPE hum_object_t,
        wa_object TYPE hum_object,
        it_item   TYPE hum_hu_item_t,
        wa_item   TYPE vepovb,
        count1(6) TYPE n.
DATA : gv_objek TYPE ausp-objek.       "Put matnr for use in FM u2018CLAF_CLASSIFICATION_OF_OBJECTSu2019
DATA : BEGIN OF it_sclass OCCURS 0.
        INCLUDE STRUCTURE sclass.
DATA : END OF it_sclass.
DATA : BEGIN OF it_clobjdat OCCURS 0.
        INCLUDE STRUCTURE clobjdat.
DATA : END OF it_clobjdat.
*& Include           ZPPR_CONVSTAT_SEL_CRITERIA
SELECTION-SCREEN FOR 'PLANNING STAGE'
SELECTION-SCREEN BEGIN OF BLOCK main WITH FRAME TITLE text-001.
PARAMETERS: mrpntdn RADIOBUTTON GROUP sel                    DEFAULT 'X' user-command flag,
              pldord RADIOBUTTON GROUP sel,
              prdord RADIOBUTTON GROUP sel.
SELECTION-SCREEN END OF BLOCK main.
SELECTION-SCREEN FOR 'SELECTION BY PLANT AND PLANT DATA'
SELECTION-SCREEN BEGIN OF BLOCK plant WITH FRAME TITLE text-002.
PARAMETERS      : p_werks   LIKE ioheader-werks OBLIGATORY DEFAULT '1100' MATCHCODE OBJECT H_T001W.
SELECT-OPTIONS : so_matnr FOR   ioitem-matnr                              MATCHCODE OBJECT MAT1.
PARAMETERS      : so_mtart TYPE t134-mtart     OBLIGATORY DEFAULT 'ZFIN' MATCHCODE OBJECT H_T134.
SELECT-OPTIONS : so_plnum FOR   ioitem-plnum                              MATCHCODE OBJECT plnum MODIF ID pld,
                    so_aufnr FOR   ioheader-aufnr                            MATCHCODE OBJECT orde   MODIF ID prd.
PARAMETERS      : p_prdsta LIKE tj02t-txt04                                                       MODIF ID prd.
SELECTION-SCREEN END OF BLOCK plant.
SELECTION-SCREEN FOR 'SELECTION BY REQUIREMENT TYPE'
SELECTION-SCREEN BEGIN OF BLOCK reqtyp WITH FRAME TITLE text-003.
PARAMETERS      : cb_so     TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                    cb_sto    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                    cb_pir    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag.
SELECTION-SCREEN END OF BLOCK reqtyp.
SELECTION-SCREEN FOR 'SELECTION BY DATE AND REQUIREMENT TYPE NOS'
SELECTION-SCREEN BEGIN OF BLOCK dtreqtypno WITH FRAME TITLE text-004.
SELECT-OPTIONS : so_crtdt FOR vbak-erdat                                                                MODIF ID gen,
                    so_vbeln FOR vbap-vbeln                                  MATCHCODE OBJECT WTY_F4_VBAP MODIF ID rso,
                    so_posnr FOR vbap-posnr                                                                MODIF ID rso,
                    so_ebeln FOR ekub-ebeln                                  MATCHCODE OBJECT MEKKM        MODIF ID rst,
                    so_ebelp FOR ekub-ebelp                                                                MODIF ID rst,
                    so_pbdnr FOR pbim-pbdnr                                                                MODIF ID rpi,
                    so_reqdt FOR vbep-edatu                                                                MODIF ID gen.
SELECTION-SCREEN END OF BLOCK dtreqtypno.
SELECTION-SCREEN FOR 'SELECTION BY OTHER PARAMETERS'
SELECTION-SCREEN BEGIN OF BLOCK othrparam WITH FRAME TITLE text-005.
SELECT-OPTIONS : so_kunnr FOR kna1-kunnr                                   MATCHCODE OBJECT debi   MODIF ID rso,
                    so_auart FOR tvak-auart                                   MATCHCODE OBJECT H_TVAK MODIF ID rso,
                    so_lfsta FOR vbup-lfsta                                                           MODIF ID rso.
SELECTION-SCREEN END OF BLOCK othrparam.
*& Include           ZPPR_CONVSTAT_PBO
*&   Event AT SELECTION-SCREEN OUTPUT
AT SELECTION-SCREEN OUTPUT.
IF mrpntdn = 'X'.
    LOOP AT SCREEN.
      IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
        screen-active = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ELSEIF pldord = 'X'.
    LOOP AT SCREEN.
      IF screen-group1 = 'PLD'.
        screen-intensified = 1.
        MODIFY SCREEN.
      ENDIF.
      IF screen-group1 = 'PRD'.
        screen-active = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ELSEIF prdord = 'X'.
    LOOP AT SCREEN.
      IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
        screen-intensified = 1.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
IF ( cb_so = ' ' AND cb_sto = ' ' AND cb_pir = ' ' ).
    LOOP AT SCREEN.
      IF ( screen-group1 = 'GEN'
      OR screen-group1 = 'RSO'
      OR screen-group1 = 'RST'
      OR screen-group1 = 'RPI' ).
        screen-active = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
IF cb_so = 'X'.
    LOOP AT SCREEN.
      IF screen-group1 = 'RSO'.
        screen-active = 1.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
    IF cb_sto = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RST'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF cb_pir = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RPI'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ELSEIF cb_sto = 'X'.
    IF cb_so = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RSO'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF cb_pir = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RPI'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ELSEIF cb_pir = 'X'.
    IF cb_so = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RSO'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF cb_sto = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RST'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ENDIF.
*& Include           ZPPR_CONVSTAT_START_SELECTION
*&   Event START-OF-SELECTION
IF mrpntdn = 'X'.
PERFORM start_of_selection_mrpntdn.
ELSEIF pldord = 'X'.
PERFORM start_of_selection_pldord.
ELSEIF prdord = 'X'.
PERFORM start_of_selection_prdord.
ENDIF.
*& Include           ZPPR_CONVSTAT_F_START_OF_SEL
*&      Form START_OF_SELECTION
      Subroutine for MRP NOT DONE
FORM start_of_selection_mrpntdn.
    SELECT mdkey INTO TABLE it_mdvm FROM mdvm
                 WHERE GSAEN = 'X'
                   AND AKKEN = 'X'.
      IF sy-subrc = 0.
        LOOP AT it_mdvm INTO wa_mdvm.
          wa_mdvm-disst = wa_mdvm-mdkey(3).
          wa_mdvm-matnr = wa_mdvm-mdkey+3(18).
          wa_mdvm-plwrk = wa_mdvm-mdkey+21(4).
          MODIFY it_mdvm FROM wa_mdvm INDEX sy-index TRANSPORTING disst matnr plwrk.
        ENDLOOP.
      ENDIF.
ENDFORM.
*&      Form START_OF_SELECTION
      Subroutine for PLAN ORDER CREATED
FORM start_of_selection_pldord.
ENDFORM.
*&      Form START_OF_SELECTION for PRODUCTION ORDER CREATED
      Subroutine for PRODUCTION ORDER CREATED
FORM start_of_selection_prdord.
ENDFORM.

You need to mention START-OF-SELECTION explicitly in your code.
Change your code as below:
*& Event START-OF-SELECTION
START-OF-SELECTION.
IF mrpntdn = 'X'.

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.

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

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

Events not getting triggered

in the code my event subtot_text is not getting triggered .... any solution plz
REPORT zver_alv_basic.
TYPE-POOLS slis.
DATA: BEGIN OF itab OCCURS 0,
          vbeln LIKE vbap-vbeln,
          posnr LIKE vbap-posnr,
          matnr LIKE vbap-matnr,
          netwr LIKE vbap-netwr,
       END OF itab.
DATA: fcat TYPE slis_t_fieldcat_alv,
      wa_fcat TYPE slis_fieldcat_alv,
      i_sort TYPE slis_t_sortinfo_alv WITH HEADER LINE,
      i_event TYPE slis_t_event.
SELECT vbeln
       posnr
       matnr
       netwr
FROM vbap
INTO TABLE itab
UP TO 30 ROWS.
I_SORT-FIELDNAME = 'POSNR'.
I_SORT-TABNAME = 'ITAB'.
I_SORT-UP = 'X'.
I_SORT-SUBTOT = 'X'.
APPEND I_SORT.
Perform to populate ALV event
PERFORM sub_get_event.
To prepare field catalog
PERFORM sub_field_catalog.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
    i_callback_program = sy-cprog
    it_fieldcat        = fcat
    it_events         = i_event
    it_sort = i_sort[]
TABLES
    t_outtab           = itab.
*&      Form SUB_FIELD_CATALOG
FORM sub_field_catalog .
PERFORM sub_fill_alv_field_catalog USING:
     '01' 'VBELN' 'ITAB' 'VBELN' 'VBAP' ,
     '02' 'POSNR' 'ITAB' 'POSNR' 'VBAP' ,
     '03' 'MATNR' 'ITAB' 'MATNR' 'VBAP' ,
     '04' 'NETWR' 'ITAB' 'NETWR' 'VBAP' .
ENDFORM.                    " SUB_FIELD_CATALOG
*&      Form SUB_FILL_ALV_FIELD_CATALOG
FORM sub_fill_alv_field_catalog USING    p_rowpos
                                          p_fldnam p_tabnam   p_ref_fieldname p_ref_tabname .
wa_fcat-col_pos = p_rowpos.
wa_fcat-fieldname = p_fldnam .
wa_fcat-tabname = p_tabnam .
wa_fcat-ref_fieldname = p_ref_fieldname .
wa_fcat-ref_tabname = p_ref_tabname.
IF P_FLDNAM = 'NETWR'.
    wa_fcat-do_sum = 'X'.
ENDIF.
APPEND wa_fcat TO fcat.
CLEAR wa_fcat.
ENDFORM.                    " SUB_FILL_ALV_FIELD_CATALOG
*&      Form SUB_GET_EVENT
FORM sub_get_event .
DATA: wa_event TYPE slis_alv_event.
    CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      i_list_type     = 4
    IMPORTING
      et_events       = i_event.
READ TABLE i_event INTO wa_event
                    WITH KEY name = 'SUBTOTAL_TEXT'.
IF sy-subrc = 0.
    MOVE 'SUBTOT_TEXT ' TO wa_event-form.
    MODIFY i_event FROM wa_event INDEX sy-tabix.
ENDIF.
ENDFORM.                    " SUB_GET_EVENT
*&      Form subtotal_text
      Build subtotal text
      P_total Total
      p_subtot_text Subtotal text info
FORM subtot_text CHANGING
               p_total TYPE any
               p_subtot_text TYPE slis_subtot_text.
Material level sub total
IF p_subtot_text-criteria = 'VBELN'.
    p_subtot_text-display_text_for_subtotal
    = 'VENDOR level total'(009).
ENDIF.
Plant level sub total
IF p_subtot_text-criteria = 'POSNR'.
    p_subtot_text-display_text_for_subtotal = 'POSNR level total'(010).
ENDIF.
ENDFORM.                    "subtotal_text

*& Report ZVER_ALV_BASIC
REPORT zver_alv_basic.
TYPE-POOLS slis.
DATA: BEGIN OF itab OCCURS 0,
          vbeln LIKE vbap-vbeln,
          posnr LIKE vbap-posnr,
          matnr LIKE vbap-matnr,
          netwr LIKE vbap-netwr,
       END OF itab.
DATA: fcat TYPE slis_t_fieldcat_alv,
      wa_fcat TYPE slis_fieldcat_alv,
      i_sort TYPE slis_t_sortinfo_alv ,
      wa_sort TYPE slis_sortinfo_alv,
      i_event TYPE slis_t_event.
START-OF-SELECTION.
SELECT vbeln
       posnr
       matnr
       netwr
FROM vbap
INTO TABLE itab
UP TO 30 ROWS.
wa_sort-spos = '01' .
wa_sort-fieldname = 'VBELN'.
wa_sort-tabname = 'ITAB'.
wa_sort-up = 'X'.
wa_sort-subtot = 'X'.
APPEND wa_sort TO i_sort .
CLEAR wa_sort.
Wa_sort-spos = '02' .
wa_sort-fieldname = 'POSNR'.
wa_sort-tabname = 'ITAB'.
wa_sort-up = 'X'.
wa_sort-subtot = 'X'.
APPEND wa_sort TO i_sort .
CLEAR wa_sort.
Perform to populate ALV event
PERFORM sub_get_event.
To prepare field catalog
PERFORM sub_field_catalog.
END-OF-SELECTION.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
    i_callback_program = sy-cprog
    it_fieldcat        = fcat
    it_events         = i_event
    it_sort = i_sort[]
TABLES
    t_outtab           = itab.
*&      Form SUB_FIELD_CATALOG
FORM sub_field_catalog .
PERFORM sub_fill_alv_field_catalog USING:
     '01' 'VBELN' 'ITAB' 'VBELN' 'VBAP' ,
     '02' 'POSNR' 'ITAB' 'POSNR' 'VBAP' ,
     '03' 'MATNR' 'ITAB' 'MATNR' 'VBAP' ,
     '04' 'NETWR' 'ITAB' 'NETWR' 'VBAP' .
ENDFORM.                    " SUB_FIELD_CATALOG
*&      Form SUB_FILL_ALV_FIELD_CATALOG
FORM sub_fill_alv_field_catalog USING    p_rowpos
                                          p_fldnam p_tabnam   p_ref_fieldname p_ref_tabname .
wa_fcat-col_pos = p_rowpos.
wa_fcat-fieldname = p_fldnam .
wa_fcat-tabname = p_tabnam .
wa_fcat-ref_fieldname = p_ref_fieldname .
wa_fcat-ref_tabname = p_ref_tabname.
IF p_fldnam = 'NETWR'.
    wa_fcat-do_sum = 'X'.
ENDIF.
APPEND wa_fcat TO fcat.
CLEAR wa_fcat.
ENDFORM.                    " SUB_FILL_ALV_FIELD_CATALOG
*&      Form SUB_GET_EVENT
FORM sub_get_event .
DATA: wa_event TYPE slis_alv_event.
    CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      i_list_type     = 4
    IMPORTING
      et_events       = i_event.
READ TABLE i_event INTO wa_event
                    WITH KEY name = 'SUBTOTAL_TEXT'.
IF sy-subrc = 0.
    MOVE 'SUBTOT_TEXT ' TO wa_event-form.
    MODIFY i_event FROM wa_event INDEX sy-tabix.
ENDIF.
ENDFORM.                    " SUB_GET_EVENT
*&      Form subtotal_text
      Build subtotal text
      P_total Total
      p_subtot_text Subtotal text info
FORM subtot_text CHANGING
               p_total TYPE any
               p_subtot_text TYPE slis_subtot_text.
Material level sub total
IF p_subtot_text-criteria = 'VBELN'.
    p_subtot_text-display_text_for_subtotal
    = 'VENDOR level total'(009).
ENDIF.
Plant level sub total
IF p_subtot_text-criteria = 'POSNR'.
    p_subtot_text-display_text_for_subtotal = 'POSNR level total'(010).
ENDIF.
WRITE :/ 'cow'.
ENDFORM.                    "subtotal_text }

IMS-exception type "Other errors" is not getting triggered

Hi experts,
                 I am trying out some scenarios in IMS. I want to check exception type- "Other Errors" which is a most generic exception type. I have tried many options like- removed country from partner id address, tried posting invoice after removing account assignment category but for all these invoice triggers exception- duplicate invoice which i am unable to understand. can anybody please tell me what are the settings required for exception type- other errors?
2. I even tried exception type "missing goods receipt". Excption type is getting triggered but after creation of confirmation- the status of the exception is not getting changed to clarified. Instead it gives an error- User is locked please try after some time.
Please help
Regards
Kapil

Hi Friend,
Please read the possible exception types in IMS
Have you set these exception in Settings for Invoice Monitor
Purpose
In the Settings for Invoice Monitor application, you can make settings directly on the user interface for every exception that you wish to adjust.
Digital signature
For each exception, you can define whether you want to use a digital signature.
If you use a digital signature, the field Digital Signature is active on the Adobe PDF form and the processor of the form has to sign it before sending it back.
The system then checks that the signature is valid.
If the signature is invalid, or the processor does not sign the form, an error message is written to the log and the e-mail is closed.
You can assign a digital signature to a vendor in two different ways.
·        The user assigns a partner certificate and sends it to the vendor.
·        The user uses the vendors signature certificate. This certificate has to be registered on the ADS server. For more information, see the SAP NetWeaver Configuration Guide Interactive Forms based on Adobe Software on the SAP Service Marketplace under service.sap.com/instguidesNW2004s.
Additionally, you can make settings for the following exceptions:
   Invoice duplicate
This exception is triggered if you try to post an invoice that has already been posted. The two invoices are compared using criteria that you have specified. In the settings, you can define whether a notification e-mail is automatically sent in the case of an invoice duplicate exception, and to whom this e-mail is sent. Furthermore, you can tailor the duplicate check to suit your requirements. The following criteria are available:
    Consider special characters in the vendor invoice number
     Check the number of items and purchase order number
     Additionally, you can define that the invoice is automatically deleted as soon as the vendor confirms that a duplicate invoice exists.
¡        Fields for duplicate check
On this tab page, you can activate the fields that are relevant for the duplicate check. Furthermore, you can define a maximum variance for each field. In other words, you define whether the data in the fields should be an exact match, or whether small differences are acceptable.
¡        Exclude vendor values and or invoice values
On this tab page, you can exclude certain vendors and/or invoice values from the duplicate check. If, for example, you always receive invoices from one vendor for the same amount, you can enter this here so as to prevent unnecessary checks.
¡        Group vendors
On this tab page, you can group vendors that have several vendor numbers together in a data record to facilitate the duplicate check. Entries in this table cause an update in the TREX database which might lead to a short delay.
Regardless of your settings, the system performs a standard duplicate check (for vendor invoice numbers or vendor numbers that match exactly, for a +/- 7 day period) to ensure that these duplicates are found. If this standard check is not successful, a further check is performed using the settings that you made.
·        Missing external information
This exception is triggered if you try to post an invoice that contains incomplete or incorrect information. In the settings, you can define whether a notification e-mail is automatically sent in the case of an exception caused by missing external information, and to whom this e-mail is sent. Furthermore, you can define whether the e-mail contains a link to the SRM System, where the missing/incorrect information can be entered directly in an interactive form.
·        Missing internal information
This exception is triggered if you try to post an invoice that contains incomplete or incorrect information. In the settings, you can define whether a notification e-mail is automatically sent in the case of an exception caused by missing internal information, and to whom this e-mail is sent. Furthermore, you can define whether the e-mail contains a link to the SRM System, where the missing/incorrect information can be entered directly in an interactive form.
·        Missing goods receipt
If no digital signature is used, two additional fields are displayed in the PDF form. The processor has to enter his first and last name into these fields before he/she sends the e-mail back.
In the settings, you can define whether a notification e-mail is automatically sent in the case of an exception caused by a missing goods receipt, and to whom this e-mail is sent. You can define how long the invoice should remain with status 'Waiting for Preceding Documents' before it receives the status 'To be Corrected Manually. Furthermore, you can define how many days pass before an e-mail is sent to the goods recipient. When the goods recipient then confirms that no goods delivery has taken place, an e-mail is automatically sent to the vendor. If the goods receipt has already taken place, you can either define that the goods recipient confirms this automatically in an interactive form, or that the goods recipient uses a link in the e-mail to confirm the goods receipt in the SRM system.
·        Incorrect reference
This exception is triggered if you try to post an invoice that refers to an incorrect reference. In the settings, you can define whether a notification e-mail is automatically sent in the case of an exception caused by an incorrect reference, and to whom this e-mail is sent. Furthermore, you can define whether the e-mail contains a link to the SRM System.
·        Approval overdue
This exception is triggered if an invoice remains in approval status for longer than allowed. You can define how long an invoice can remain in approval status before the exception is triggered.
·        Other errors
This exception is triggered if you try to post an invoice that contains errors. In the settings, you can define whether a notification e-mail is automatically sent in the case of an exception caused by other errors, and to whom this e-mail is sent. Furthermore, you can define whether the e-mail contains a link to the SRM System.
Note that the invoice is checked in accordance with the vendor tolerance limits in the case of the following exceptions: If these are exceeded, an error message is output.
·        Price variance
This exception is triggered if you try to post an invoice that contains price variance that exceeds the tolerance limit. In the settings, you can define whether a notification e-mail is automatically sent in the case of a price variance, and to whom this e-mail is sent. You can stipulate that the invoice is posted automatically if the price variance is approved on account of the e-mail. Furthermore, you can define whether the e-mail contains a link to the SRM System.
·        Quantity variance
This exception is triggered if you try to post an invoice that contains quantity variance that exceeds the tolerance limit. In the settings, you can define whether a notification e-mail is automatically sent in the case of a quantity variance, and to whom this e-mail is sent. You can stipulate that the invoice is posted automatically if the quantity variance is approved on account of the e-mail. Furthermore, you can define whether the e-mail contains a link to the SRM System.
·        Tax variance
This exception is triggered if you try to post an invoice that contains tax variance that exceeds the tolerance limit. In the settings, you can define whether a notification e-mail is automatically sent in the case of a tax variance, and to whom this e-mail is sent. You can stipulate that the invoice is posted automatically if the tax variance is approved on account of the e-mail. Furthermore, you can define whether the e-mail contains a link to the SRM system.
In Invoice monito system pls check the what setting is done for Duplicate invoice, Missing GR and other invoice.
Based on these setting only system identifies what type of exception it is.
In other errors you should mention in Settings for Invoice Monitor what are the fileds your consider for other exception.
Hope this information will help.
Thanks & Best regards
Girish

Output type is not getting triggered for ship to party in shippment output

Hi,
we have maintained output determination procedure for shipments. It was working fine.
We have just added new condition table to access sequence, and maintained the condition records also for condition type ZABC. I have checked in NACE, Application V7, I am able to find the condition type. checked in VV73, condition records displayed. But in VT02N/VT03N, we are unable to get print for the output type.
Why this is happening? we are able to see the procedure, condition type, access sequence, condition records in place ...why condition type ZABC is not getting triggered in the shipment output.
Please advise and let me know if you need more details....thanks in advance.
Thanks,
SS

Hi Noel,
Thanks for your time and reply.
We have output determination procedure for shipments, condition type ZABC, Access sequence ZABC, Condition tables 550,600,650,700 already maintained. output is working fine.we have a new requirement and created new condition table 700 with the fields" Ship to party and transportation planing point "(Condition table 700 ). we assigned the condition table 700 to access sequence ZABC. Condition type ZABC already placed in Output determination procedure.
We test the output, new condition record is not triggering in the output, even in output determination analysis also, we are unable to see the record 700 for the condition type ZABC. we are not sure what is the reason for the condition table that is not picking up ? Why condition type ZABC with condition record 700 not visible in output determination analysis.
I have checked condition records, output determination procedure. Please advise and let me know you need more details.
Thanks,
SS

Events in USER objects type not getting triggered in PFCG

Similar Messages

Maybe you are looking for