Credit Memo User Exit

Hi Guru's,
In transaction VA01 when we try to create memo by clicking on "create with reference" and giving the invoice no. there, it should copy all the line items of the invoice to that particular credit memo but it is not doing in my client but in standard SAP it happens.
Can anybody help me to know, if any user exit is responsible for this or any particular section of stoping this to happen?
The error message I am getting is "Material in item 000040 does not
plant/storage location " but this is already there.
Please help me to resolve this issue.
Thanks in advance....
Regards
Abinash

Hi Naren,
Thanks for your reply!
While debugging, I come to know that the error message is coming due to the fact that MARD table(Storage Location Data for Material) do not have any data.
If you go through the error message "Material in item 000040 does not exist in plant/storage location". It is very much clear that error message is coming due to this only.
I have access to diff. client, in the other client this error message is not coming and also MARD table is maintained for all the materials.
Could you please suggest what could be the reason for MARD table not being updated? Also if you can suggest the solution for it.
Regards
Abinash

Similar Messages

  • Credit Mgmnt - User Exit Logic

    Dear Experts
    Automatic credit mgmnt settings  are completed . Customized authorizations  required is like below:
    The reqt is like
    1) Rs 0- Rs 50 Lakh - Person A
    2) Rs50 Lakhs-Rs 1 Crore - Person B
    3) Rs 1 Cr- Rs 2.5 Cr- - Person C
    4) Rs 2.5 Cr & above - Person D
    I presume that this can be done by using user exit... Field of 'Credit Limit'- KLIMK
                                                                                    'Credit Exposure'. OBLIG       [from FD32]
    Help/suggestions request ASAP.
    Rgds
    Sumanth.G

    hi,
    this is to inform you that,
    you can solve your issue with an ABAPER,
    he will write a big code for this.
    these are the steps:
    please write a piece of code in USER_EXIT_SAVE_DOCUMENT_PREPARE, which saves a document and triggers an email and stops proceeding further.
    1) if the credit limit in KNKK reaches 50 lakhs mark you have to trigger a mail through a work flow to person ARs 0- Rs 50 Lakh - Person A
    read the data basing on CCA/CREDIT LIMIT OF THE CUSTOMER/CUSTOMER NUMBER by catching user id who is preparing the sales order goto PA0105 to get the employee number and using employee number go to get the manager for amployee number using Z_GET_MANAGER a function module. after getting manager id from PA0105 trigger an standard function module called EFG_GEN_GET_USER_EXIT to get teh mail id of the manager - and trigger to approve the mail.
    for this you have to link WORK FLOW event also in Z_GET_MANAGER function module.
    here you have to create
    1.new function module : Z_GET_MANAGER - which gets the total details of persons who are working in the whole organization.
    2. 2 HR tables to get the details upto manager : PA0001, PA0105.
    3. use standard FM : EFG_GEN_GET_USER_EXIT
    4.finally link WORK FLOW EVENT which triggers an mail id to manager's in box with approval infomation.
    hope this should help you
    regards,
    balajia
    Edited by: balaji timmampalli achari on Nov 30, 2010 12:06 PM

  • Credit Management Routin - Credit Exposure User Exit

    Dear SDNs,
    I have requirement in Credit Management.
    I have activated Credit Management and working fine. Client requirement is: To deactivate Cedit Check if it is the case of LC (Letter of Credit). I have written a routin in OVA8 > Document Controlling > No credit check. Here I have checked the field LCNUM of Table VBKD which is there in Sales Order > Billing Tab (Header) > Financial doc. no.
    It is working fine again. But here this LCNUM activates Foreign Trade. So we used other Z-Field called ZLCNUM. Again it is working fine. But after using ZLCNUM we noticed that the Credit Exposure has started getting updated.
    So now I am looking for the solution.
    Can I go for any User Exit of Credit Exposure?? If yes, which User Exit can I use.??
    If any other solution is there.. Do respond.
    Quick reply would be highly appreciable...
    Thanks,
    HP

    Hi,
    Actually I have got some User exits for credit checks...
    LVKMPTZZ
    LVKMPFZ1: USER_CREDIT_CHECK1
    LVKMPFZ2: USER_CREDIT_CHECK2
    LVKMPFZ3: USER_CREDIT_CHECK3
    And trying with that also but looking for any other solution if it is available..
    And using another Sales Document Type is not possible in this case..
    Any inputs...?? anybody???
    Thanks..
    HP

  • Credit Management: User Exit LVKMPTZZ and LVKMPFZ1

    Hi,
    I'm trying to implement crdit management and have a special requirment which is not satified by the standard risk control checks.
    Hence i'm planning to implement the USER1 check in the risk catogery.
    I'm aware that some ABAP code has to be done to activate and the user exits are LVKMPTZZ and LVKMPFZ1.
    Where should be the code written LVKMPTZZ or LVKMPFZ1.
    I guess the code has to be written in LVKMPTZZ  and call the exit LVKMPFZ1 which in turns call the function module SD_ORDER_CREDIT_CHECK.
    Am I true in my understanding.
    Does editing LVKMPTZZ SAP access key.
    Please help.
    Thank you in advance.

    Hiii
    You can write the code to call the funtion module for credit check in LVKMPTZZ but for same you need Access key from SAP to edit the Include.
    Regards
    Shambhu Sarkar

  • Work flow - user is not reciving mail,once CREDIT MEMO submits for approval

    Hi All,
    Please find the issue as below.
    User created the credit memo and submitted for approval. user is expecting the mail in his mail-box, once he submitted the credit memo for approval and same way once approver approved the credit memo, user is expecting mail such that credit memo has been approved.
    He informed that previously he is receiving the mails as expected.
    Now all of sudden he is not receiving mails.
    I have checked work flow mailer, mailer is up and running.
    I have gone through the wf_notifications table, here i can see that MAIL_STATUS column having value of "MAIL".
    even i have gone through WF_USERS table this particular user is existing and status is "ACTIVE".
    But user is not yet received any mail.
    Kindly some one help me to sort out this issue.
    Thanks in Advance.
    Edited by: user627525 on Jun 8, 2011 5:58 AM

    Thanks RK for your quick reply.
    I was gone through the details you have provided. every thing is fine as expected.
    Later i have checked workflow mailer, it was down, due to that notifications are not reached to users/customers.once it is up and running mail notifications sent to respective users successfully.
    Many Thanks.

  • User exit for va01/va02 for std program

    Hi ,
    how are u all....
    here is my problem...
    i created a customized screen for va01.
    this screen gets called after user saves the order.
    in this screen i provided 4 options .
    1. accept the order
    2 change the order
    3.reject the order
    4 release unconfirmed.
    i am calling this screen in user exit userexit_refresh_document.
    before this am capturing the order number .
    once user clicks on first radion button i.e on accept.
    then i am passing the order number and removing the block using BAPI_salesorder_change.
    but here bapi is passing the error message as plese enter the order number ....
    my doubt is the userexit whr am calling the screen is correct ?
    can we do the same using BDC ..?
    if anybody working actions on user entry for va01 and va02..
    please let me know whr and how u r writing the code... sooon
    thx in advance...
    regards
    sanjay

    what are u doing ? , u cannt call BAPI in the same user exit.
    if user accepts the order --->then u have to unblock the order ?
    then u have to activate Credit Control User exits ->SPRO->SD->System Modifications>Credit Control User exits.
    regards
    Peram

  • User Exit for additional processing in Credit memo

    Hi.
    While saving a credit memo , I want to read a Z table and do some processing on it and then show a popup to user. Which Customer Exit is most suitable for this task. pls advise.
    Thanks

    Hi,
    you can use USEREXIT_FILL_VBRK_VBRP  in RV60AFZC.
    Regards
    William

  • 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 - sales order, credit block

    Moderator message: moved to correct forum.  In future please use meaningful subject.
    my requiremnet is, Delivery for an sales order should be created even if it is a credit block i.e even the credit check is unsuccessful the order should be deliverd when we deliver the order from salesdocument->deliver.
    i need a user-exit for this to put this check.
    can ne one help me.
    regards,
    pavan,

    Hi,
    According to Std SAP if in case credit mgmt is activated system will check for credit limit for that customer before delivery.You will be trying to change the std scenario which is not advisable.
    However,
    Try user exit MV45AFZZ & in that
    FORM USEREXIT_SAVE_DOCUMENT_PREPARE.
    Also check other exits related to delivery & credit mgmt from
    SPRO->Sales & Distr-> System Modifications->User Exits
    and check out the documentation part next to each exit in that category.
    Regards,
    Amit

  • User exit for merging the credit limit in different credit control area.

    Dear All,
    Please provide user exit for the merging the credit limit in different credit control area as well as logic for the same.
    I have to merge the overall credit limit of the customer for some divisions. At this time in one company code we have created 9 credit control area as per product line. While creating customer master data and Credit management (FD32) user has assigned the different limit with respective to credit control area e. g Customeru2019s total limit assigned is 10 laks.  For credit control 1100 Limit is Rs. 3 laks and for credit control area 2200 limit is 7 laks. Now the user wants to merge the credit limit for only above two credit control area. The sales orders should get created in any credit control area up to 10 laks.
    Regards,
    Suresh

    Dear Damodhar/All,
    Would you please explain me prerequisite setting from functional side for these user exit?
    I want complete functional setting prior to ABAP application so that it work properly post configuration.
    Regards,
    Suresh

  • Delete credit memo work item created in VA01 when the user change value

    Hi,
    In T.code VA01 Credit memo request is creating, this document will automatically create  work item.  Based on Net value in credit memo request, the work item should go for 5 levels of approval. After 1st person is approved, the workflow initiator realized that the net value in created Credit Memo request is wrong; he is going to VA02 and correcting the net value. Again we have to create new work item for this and delete the already created work item. Client has clearly mentioned when ever there is change in 5 critical fields in VA02 then only create fresh work item otherwise no need to create SECOND TIME work item. Net value is one of the critical field in the list.
    How to track already created credit memo request and how to delete the previously created work item. What is the feasibility of this requirement and how to handle this situation?
    Regards
    Vijay

    Hi,
    Just put a Fork and put 1 out of 2 outcomes and in the first alternative, you put your witem that goes to user B. In the 2nd alternative, put a Wait for event "CHANGED". And after this, put a process control step with "Set workitems to Obsolete" or "Cancel workflow" etc., depending on your requirement.
    Pl note that this will only take out old witems, but you need to send a new witem for which you need to trigger another instance of the workflow as well. pl put CHANGED event also as one of the triggering events and use condition editor to restrict the fields that triggers the workflow.
    Also, look into the IMG config of the following path. This might be a fitting solution.
    In SPRO, go to Financial Accounting (New)---> Financial Accounting Global settings(New) -
    >Tools --->Workflow ---> Workflow for Document Parking -->Reset Release Approvals(Customers).
    Here, you can list down the fields, the workflow should restart. But, then you need to give the workflow details etc., in the relevant config settings.
    We have used this in restarting workflows for General Ledger(GL) documents' workflow when some important fields are changed.
    For this config settings, look into the following help link.
    http://help.sap.com/erp2005_ehp_02/helpdata/en/01/a9cdd8455711d182b40000e829fbfe/frameset.htm
    Hope this helps.
    venu

  • 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

  • What are the user exits available related to Credit Management?

    What are the user exits available related to Credit Management?
    <b>I have blocked users from releasing SO through Tciode VKM3 , now I want to block
    the same (releasing of SO through VKM4) ,I want VKM4 to be used only for releasing delivery orders. Can anyone help me in configuring the same?.</b>
    Thanx in advance,
    Regrds,
    Binayak

    Hi,
    User Exits For Credit Checks And Risk Management
    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.
    Risk Management for Receivables
    RVKMPUS2
    Using this user exit, you can define new forms of payment guarantee.
    Regards,
    Amrish Purohit

  • Sales Order Line Items User Exit - Credit Management/ Exposure Calculation

    Hello Folks
    I am looking for a solution to a peculiar problem we have in credit management.
    In case of Drop Ship sales order life cycle, the system automatically creates two line items per sales order - one each for Freight and Handling Fees. these are NOT relevant to schedule line delivery, nor are they billed to the customer along with the material billing. The default update rule for credit control area concerned is 12. The system, on finding line items not relevant to schedule line delivery automatically switches from rule 12 to 18. This leads to Open Deliveries field (S067-OLIWW) being updated instead of Open Orders (S066-OEIKW) on saving the sales order.
    Once the sales order is billed for the material, the system should logically display net value as zero for the open order (as the 2 lines of fees and freight are not yet billed, the order is still open). But the system considers this figure at SALES DOCUMENT HEADER level and considers the net value as the total value of the sales document (including the material that is already billed).
    What I am looking for is if there is an exit available whereby the system considers only those line items whose billing status indicator is "not complete". As such, the net value should be updated to the S067-OLIKW field net of the billed items.
    Please advise if there is any such user exit available. Also, is there a way to customize this? We are exploring this at our end, but would appreciate an expert advise. Right advise will be awarded with brownie points
    Regards
    Mandar Barve

    VKM1 uses FM SD_ORDER_CREDIT_RELEASE to release orders on credit.

  • 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

Maybe you are looking for