Please give me User Exit  for Credit Release -Urgent-

Please send the User Exit for Credit release

Mr.Goutam
My request is that dont continue your questions in one thread.
Two options are available for you to post in this forum
a)  First list out what are all your requirements and ask this forum in which specific area you have doubts.  If all your questions are answered, award points who have given the solution for you.
b)  Post question one by one and wherever your questions are answered, close the thread and reward points to the members.
If you take this thread, Initially you raised a question on Credit Limit and many of us have answered your question and the thread should have been closed.  But questions are continuing with same subject but with different topics which I feel is WRONG.
Hope you understand now.
Thanks
G. Lakshmipathi

Similar Messages

  • User Exits for Credit Check

    Hi Friends,
    I got user exits for credit check but I could not understand how to implement these rather these are not found in system (CMOD & SMOD tcodes) We have ECC6.0. These are the following.
    LVKMPTZZ
    LVKMPFZ1: USER_CREDIT_CHECK1
    LVKMPFZ2: USER_CREDIT_CHECK2
    LVKMPFZ3: USER_CREDIT_CHECK3
    Any help how to implement these is appriciable.
    Regards,
    Rajesh Vasudeva

    Hi Rajesh,
    You can make use of the implicit enhancement, where in you can add code to any standard program either at the start or after the last line in a form or function module.
    Refer the URL
    http://help.sap.com/saphelp_nw04s/helpdata/en/8f/f2e540f8648431e10000000a1550b0/frameset.htm
    for more info on Enhancement Framework.
    Hope this helps you.
    Reg
    Praveen Alex Luke.

  • User Exit for credit management  at confirmed quantity in sales order

    Dear All ,
    kinldy tell how to define a user exit and where i can write for credit check to be done to the confirmed quantity in the sales order .
    Also pls tell me that how to define the user exit and attach to customer reserve field in the customising for automatic credit control .
    regards
    Baranidharan Ramar

    Hi
    The following is the information from the sap documentation...you can also refer from IMG - SD - System modification - userexit - userexit for credit check
    Credit Check
    If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:
    LVKMPTZZ
    LVKMPFZ1: USER_CREDIT_CHECK1
    LVKMPFZ2: USER_CREDIT_CHECK2
    LVKMPFZ3: USER_CREDIT_CHECK3
    User exit for availability check
    User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
    This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.
    Thanks,
    Ravi

  • User exit for Credit Management check on SD document

    Is it possible to enhance and put in some custom logic during CREDIT check on SD documents?
    Can some one tell me which User exit can I used?

    Hi,
    Yes, I think you can do. Here is what SAP help says....
    If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:
    LVKMPTZZ
    LVKMPFZ1: USER_CREDIT_CHECK1
    LVKMPFZ2: USER_CREDIT_CHECK2
    LVKMPFZ3: USER_CREDIT_CHECK3
    User exit for availability check
    User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
    This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.
    Hope this helps
    Thanks
    Mukund S

  • User exit for Credit Memo creation

    I want to create an IDOC when the credit memo will be created.
    What is the name of the user exit  where I can write the IDOC generation code ?
    Edited by: Alvaro Tejada Galindo on Feb 18, 2008 9:47 AM

    IDoc Inbound User Exits
    1. ACC_BILLING
    Accounting: Post invoice (OAG: LOAD RECEIVABLE)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    2. ACC_EMPLOYEE_EXP
    FI/CO: HR posting GL (AcctngEmplyeeExenses)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    3. ACC_EMPLOYEE_PAY
    FI/CO: HR posting AP (AcctngEmplyeePaybles)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    4. ACC_EMPLOYEE_REC
    FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    5. ACC_GL_POSTING
    Accounting: General G/L account posting
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    6. ACC_GOODS_MOVEMENT
    Accounting: Post goods movement (OAG: POST JOURNAL)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    7. ACC_INVOICE_RECEIPT
    Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    8. ACLPAY Accounting: Inbound invoice
    - ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
    - ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
    - ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
    9. ACLREC
    Accounting: Billing document
    - ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
    - ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
    - ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
    10. ACPJMM
    Posting in accounting from materials management
    - ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
    11. ARTMAS
    Create and change of material master (Retail)
    - MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
    12. BLAOCH
    Purchasing contract change
    - MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
    - MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
    - MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
    13. BLAORD
    Purchasing contracts
    - MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
    - MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
    - MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
    14. BLAREL
    Release order documentation for distributed contracts
    - MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
    15. COND_A
    Conditions: master data for price determination
    - VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
    - VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
    16. CREMAS
    Distribute vendor master
    - VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
    17. DEBMAS
    Customer master
    - VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
    18. DELINS
    Delivery schedule/JIT schedule
    - VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
    - VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
    - VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
    - VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
    19. DESADV
    Delivery: Shipping notification
    - LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
    - MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
    - V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
    - V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
    - V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
    - V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
    - V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
    - V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
    20. DOCMAS
    Master document
    - CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
    21. DOLMAS
    Document-object links
    - CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
    22. EDLNOT
    EDL delivery notes
    - VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
    - VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
    - VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
    - VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
    23. FIDCC1
    Send entire FI documents (user exit 003/4)
    - F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    - F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
    - F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
    - F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
    24. FIDCC2
    Send entire FI documents (user exit 005/6)
    - F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    - F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
    - F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
    - F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
    25. FIDCMT
    Sending single items for FI-GL
    - F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    - F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
    26. FINSTA
    Bank Statement
    - FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
    - FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
    27. FIROLL
    General ledger rollup for FI-GL (delta f. line items FIDCMT)
    - F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    28. GSVERF
    Cred. memo procedure
    - VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
    - VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
    - VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
    29. HRMD_A
    HR: Master data and organizational data (appl. system)
    - RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
    - RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
    - RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
    30. INFREC
    Purchasing info record
    - MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
    - MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
    31. INVOIC
    Invoice / Billing document
    - FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
    - FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
    - FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
    - FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
    - FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
    - FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
    - FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
    - FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
    - FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
    - FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
    - MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
    - MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
    - MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
    - MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
    - MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
    32. LIKOND
    Listing conditions
    - WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
    33. MATMAS
    Material Master
    - MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
    34. MRESCR
    Create reservation
    - SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
    35. ORDCHG
    Purchase order/order change
    - MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
    - MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
    - VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
    - VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
    - VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
    - VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
    - VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
    - VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
    - VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
    - VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
    - VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
    - VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
    - VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
    36. ORDERS
    Purchase order / order
    - MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
    - MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
    37. ORDERS
    Purchase order / order
    - MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
    - MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
    - VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
    - VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
    - VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
    - VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
    - VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
    - VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
    - VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
    - VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
    - VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
    - VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
    - VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
    - WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
    38. ORDRSP
    Purchase order / order confirmation
    - MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
    - MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
    - MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
    - WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
    39. PORDCR
    Create purchase order
    - SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
    40. PREQCR
    Create purchase requisition
    - SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
    41. PROACT
    Stock and sales data
    - WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
    42. REMADV
    Payment advice
    - FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
    - FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
    43. REQOTE
    Inquiry
    - VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
    - VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
    - VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
    - VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
    - VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
    - VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
    - VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
    - VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
    - VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
    - VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
    - VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
    44. SBINV
    Credit memo procedure with invoice creation
    - VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
    - VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
    - VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
    - VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
    - VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
    45. SDPACK
    Packing confirmation
    - VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
    - VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
    46. SDPICK
    Picking confirmation
    - VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
    - VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
    47. SHP_IBDLV_CONFIRM_DECENTRAL
    Confirmation (Inbound Delivery)
    - V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
    48. SHP_IBDLV_SAVE_REPLICA
    BAPI Function Module for Duplication of Outbound Deliveries
    - V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
    49. SHP_OBDLV_CONFIRM_DECENTRAL
    Confirmation (Customer Delivery)
    - V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
    50. SHP_OBDLV_SAVE_REPLICA
    BAPI Function Module for Duplication of Outbound Deliveries
    - V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
    51. SHPCON
    Delivery: Shipping confirmation
    - V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
    - V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
    - V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
    - V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
    - V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
    - V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
    52. SHPMNT
    Shipping outbound
    - V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
    - V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
    - V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
    53. SRCLST
    Source List
    - MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
    - MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
    54. SRVMAS
    Master data service master
    - BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
    - BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
    55. TPSSHT
    Shipping planning system: Transfer planned shipments
    - V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
    - V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
    - V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
    56. WHSCON
    Delivery: Stock confirmation
    - V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
    - V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
    - V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
    - V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
    - V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
    - V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
    57. WMBBIN
    Block Storage Bins
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
    58. WMCATO
    Reversal/Reversal request for transfer order
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
    59. WMINVE
    Inventory count input
    - MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
    - MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
    60. WMMBXY
    IDoc Report goods movements in IM
    - MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
    61. WMSUMO
    Move storage unit
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
    62. WMTOCO
    Transfer order
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
    63. WMTORD
    Transfer order
    - MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
    - MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
    64. WMTREQ
    Create/Cancel transfer order
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
    65. WPUBON
    POS interface: Upload sales documents (compressed)
    - WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
    - WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
    - WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
    66. WPUFIB
    POS interface: Upload Fin.Acc. interface SRS/POS
    - WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
    - WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
    67. WPUFIB
    POS interface: Upload Fin.Acc. interface SRS/POS
    - WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
    68. WPUKSR
    POS upload cashier data
    - WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
    - WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
    - WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
    69. WPUUMS
    POS interface: Upload sales data (compressed)
    - WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
    - WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
    - WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
    70. WPUWBW
    POS interface: Upload goods movements
    - WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
    - WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
    - WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
    71. WVINVE
    Store physical inventory / sales price revaluation
    - WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
    - WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment

  • User exit for credit check

    Hi all,
    Can anyone give the user exit name for credit check.

    Hello,
    Following exits are available:
    LVKMPFZ1  
    LVKMPFZ2  
    LVKMPFZ3  
    Regards,
    John.

  • User exit for the release of Purchase Order

    Hi Friends,
    I am searching for a user exit which should trigger at the time of Purchase Order release in ME29n transaction.
    If anyone can help me for the same....!!!
    I need the exact exit which triggers at the release of PO....
    Points will be rewarded for the needful replies.
    Regards,
    Mandeep.

    HI,
    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.
    report zuserexit no standard page heading.
    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.
    *---End of Program
    USE THIS PROGRAM TO GET ANY USER EXIT BY GIVING THE TCODE.
    MMFAB001            User exit for generation of release order
    MRFLB001            Control Items for Contract Release Order
    REGARDS,
    PRIYA.
    Edited by: Priyadharshini Veluswamy on Mar 13, 2008 9:21 AM
    Edited by: Priyadharshini Veluswamy on Mar 13, 2008 9:40 AM

  • User exit for contract release order.......

    Hi All,
    I have a question...
    when we create a sales order and type the sold-to party the system dispalys(pop-up screen) the open contracts against the customer. It is up to us wheather we can copy any one of the contacts into the sales order and create a release order or we can just cancel the pop-up screen and create a new sales order with out reference to a sales order.
    <u>HERE my requirement is as follows</u>.
    1) <b>When a customer has open contacts  and validity period we should  make user to copy  any one of the the existing contracts in the pop-up screen.</b>
    2) <b>At the same time if the customer has got no contracts against him he should be allowed to cerate a plain sales order.</b>
    I have tried with user exit Change document & User exit Save document in include <b>MV45AFZZ</b> but our code (user exit) should fire before or at the time of pop-up screen(containing the open contracts against the customer) which is just not happening.
    Has any one of you came across of any solution for this kind of scenario...
    One last option i have got is to disable the close push button taking the access key  and changing the standard code........but this will effect the other places where this close button is used.
    Please let me know how to go about it.
    Thanks in advance......for your valuable time & precious knowledge.
    With regards,
    <b>Pavan</b>

    Have you tried applying code to EXIT_SAPLV46H_001 - Customer Function When Creating Item?
    Or EXIT_SAPLV46H_002 - Customer Function for Partner Changes?

  • Purchase requisition , ME51N, user exit for change Release date

    Hello.
    Purchase Requisition ( transaction ME51N).
    I want to change the value of u201ERelease dateu201C using user-exit EXIT_SAPLMEREQ_005.
    CALL METHOD im_req_item->get_data
      RECEIVING
        re_data = get.
    set = get.
    set-frgdt = u2026..
      CALL METHOD im_req_item->set_data
        EXPORTING
          im_data = set.
    Next, in dynpro is visible the right value from EXIT_SAPLMEREQ_005, but when saving the system uses another value, not the value from user exit.
    Do you anybody have some experiences with this problem?
    Lumir

    Hi
    The USer Exit you can use for the ME51n Tcode is by using Badi's.The Badi you can use is ME_PROCESS_REQ_CUST BADI.
    Method to be used: PROCESS_ITEM
    This link gives you a brief idea.Hope it helps you.
    BADI for ME51N
    Thanking you.

  • User exit for triggering release strategy

    Hello Experts,
    My requirement is when changes are made in purchase order (ME22N) then once again release strategy will have to get trigger.
    is the user exits exists for this purpose,if yes, What is it?. I searched alot but not able to find right exits.

    Hello ,
    I think you can achieve this via configuration .Basically you want the release strategy to get redetermined based on the changes in the item or if the price of these items increase a certain level .if you  have the release startegy as changeble in the SPRO ticked it will automatically go for new release strategy if you have the value of release indicator set .This can be done SPRO->MM->Purchase order->Release procedure for purchase order->Define release procedure->Release indicator.
    Set  the appropriate value  .
    Remember you need to know what is that it retrigger that release strategy .
    The link below deals with similar requirement ....
    [http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/retrigger-release-strategy-for-purchase-requisition-with-any-change-1858101]
    Thanks
    Anjaneya .
    Edited by: Anjaneya Bhardwaj on Aug 31, 2011 8:21 AM

  • User Exit for Requisition Release Strategy

    Hi All,
    Is anyone able to provide any guidance on determining the release strategy of a purchase requisition via a user exit? It has become neccessary to do this due to certain shortcomings of the classes and characteristic functionality.
    I believe it's possible, I just don't know how.
    Thanks.
    Richard

    go SMOD and enter enhancement M06E0004      it is exit LXM06U13

  • User Exit for PO Release

    Hi Gurus!
    I am searching for an Exit for the PO in ME21N.
    I want to restrict the PO value to a certain limit with respect to PR.
    Exit should trigger while creation of PO in ME21N.
    Points will be rewarded!!!
    Regards,
    Esaki

    Hi,
    You can use the BADI ME_PROCESS_PO_CUST to meet your requirement.
    Select the method depending on the requirement.
    Use SE18 to view the BADI definition and use SE19 to implement BADi.
    Reward points if it is helpful.
    regards,
    Prasanna
    Edited by: prasanna j on Mar 27, 2008 5:28 AM

  • User Exit in Credit Managment - Urgent

    Dear All,
    One of our customers want to use option of Oldest of open Items overdue in the Automatic credit check.
    WIth the only difference that he does not want the field  " Days oldestItem ( Table Name V_T691F / Field Name OITOL)" within IMG. He wants that field to be available in the customer master.
    In order to achieve this we have thought of following solution --
    1. Add new field in the customer master using screen exit in " General Data / Company Code" Tab for capturing  " Days oldestItem ( Table Name V_T691F / Field Name OITOL)"
    2. Use user exit LVKMPFZ1. Build following logic into the same.
    Refer table for Open Line Item (Table BSID)
    Due date = Document Date (Field BLDAT) + Days 1 (Field ZBD1T)
    If, Due date + Field in Customer Master added through screen exit (in no. of days) < Today, Credit Check will be active & depending on the setting in Automatic Credit Check, we can get either warning message or error
    Please check if above logic is OK. If you wish to suggest any changes, you are most welcome to do so. Points will be rewarded for any valuable suggestion. But please hurry up. Unfortunately we do not have much time.
    Regards
    Nikhil

    Hi,
    TRY THIS PROGRAM MAY BE HELP U,
    REPORT z_find_userexit NO STANDARD PAGE HEADING.
    *&  Enter the transaction code that you want to search through in order
    *&  to find which Standard SAP User Exits exists.
    *& Tables
    TABLES : tstc,     "SAP Transaction Codes
             tadir,    "Directory of Repository Objects
             modsapt,  "SAP Enhancements - Short Texts
             modact,   "Modifications
             trdir,    "System table TRDIR
             tfdir,    "Function Module
             enlfdir,  "Additional Attributes for Function Modules
             tstct.    "Transaction Code Texts
    *& Variables
    DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
    DATA : field1(30).
    DATA : v_devclass LIKE tadir-devclass.
    *& Selection Screen Parameters
    SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
    SELECTION-SCREEN SKIP.
    PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
    SELECTION-SCREEN SKIP.
    SELECTION-SCREEN END OF BLOCK a01.
    *& Start of main program
    START-OF-SELECTION.
    Validate Transaction Code
      SELECT SINGLE * FROM tstc
        WHERE tcode EQ p_tcode.
    Find Repository Objects for transaction code
      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 = enlfdir-area.
            MOVE : tadir-devclass TO v_devclass.
          ENDIF.
        ENDIF.
    Find SAP Modifactions
        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.
    Take the user to SMOD for the Exit that was selected.
    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.
    Thanksmate,
    Reward if helpful,
    Phani

  • User exit for sales order-Urgent

    How  Developed a User Exit, which will be triggered when a Sales Order is changed manually. This user exit will check the requested delivery date and update VBKD-BSARK field.
    Pls help me how to do it....
    Pts will be rewarded.....

    Hi,
    The following exits trigger during VA01 creation:
    EXIT_SAPMV45A_002 and
    EXIT_SAPMV45A_003
    Check this include MV45AFZZ also.
    Regards,
    Satish

  • User Exit for CJ2B

    Please give me user exit for CJ2B(Project Planning BOard)
    I need to add 2 columns in output of CJ2B.
    Thanks,
    Sachin

    To find customer exit/BADI perform some search at sdn you should easily [find some guide and tools|http://wiki.sdn.sap.com/wiki/dosearchsite.action?searchQuery.queryString=finduserexit&searchQuery.spaceKey=conf_global]
    Regards,
    Raymond

Maybe you are looking for

  • How to add two nodes in a Hierarchy

    Hi Experts,                 I have 0ACCOUNT hierarchy using for P&L report. I developed this hierarchy to get the values of Revenue and Expenses (nodes).  Once I get this values I want the difference of this two to get the Income Statement. I have Re

  • Premiere Elements 12 and Davinci Resolve Lite

    I'm reaching out to see if anyone is currently using Davinci Resolve Lite along with PE12. Can't seem to find any info regarding a Workflow of color correcting / editing using these two programs. There are several regarding Premiere Pro, but not PE.

  • Inbound Delivery Idoc not update PIC and PGI with split batch.

    Dear Experts, Delivery outbound with split batch send to third party Warehouse to PIC and PGI from SAP, then receive the delivery inbound IDOC to update the PIC and PGI in SAP from third party. Basic Idoc DELIVERY03 it's works fine with out split bat

  • IMovie export file type selection for iDVD

    I'm manipulating "home movies" (old Hi8 & new flash HD) with intent to eventually burn DVD's for various family members (e.g., children & grandparents) using iDVD. I have been creating Projects then exporting as either Movie (Medium .m4v) or Quicktim

  • Navigating to Frame Label In a MC

    Hi All, I need some help and I will try to explain what I am trying to do the best i can. I have a flash movie that has a mc called "pages" in Scene1. In the mc "pages" I have 4 key frames each representing 4 pages (i.e. 4 movie clips each one repres