Credit memo duplication

Hi All,
i have made the configuration for checking duplicate invoice.
but when i post Credit memo it  post even if it is duplicate
thanks for your help.
Regards
Sunitha
Message was edited by:
        sunitha l m

Hi Sunitha,
Please go through the SAP note 305277 Check for Double Credit memos.
This functionality is not present in most of the Standard SAP R/3 Systems.
Award points if useful
Thanks & Regards
Kishore

Similar Messages

  • Duplication of credit memo

    Hi,
    How can we check the duplication of credit memo.
    In case of invoice we can do setting " Set Check for Duplicate Invoices". similarly do we have any facility to set check for the duplication of credit memo. my client wants the system to throw an error when a credit memo is entered with same reference no.
    Thanks in advancce.
    Regards
    GP

    Please refer to the SAP Library -> Logistics -> Material Management
    ->Logistics Invoice Verificaion -> Invoice Verfication Online ->
    Balance -> Check for duplication of Invoice entry
    "Only invoices are checked. When you enter credit memos or subsequent
    debit or credits, the system does not check for duplicate invoices in
    logistics.
    If a previously created document is canceled and then created again, the
    system does not display a message."
    Please read this documentation for further details on duplicate
    invoices.
    Please refer to note 305201 - Description: Check for duplicate invoices
    "In the invoice verification in MM, only invoices are checked"
    If you want to check whether a corresponding credit memo has already
    been entered when you enter credit memos, implement the modification
    proposal from note 305277.
    Hope the information help.

  • Duplication of document numbers for Credit Memo, Inventory Transfer, etc.

    Hi folks!
    Good Day!
    We have noticed that there are credit memo numbers, inventory transfer numbers etc. that were duplicated in two different transaction in two different dates. Can you give a theory or possible reasons why this one happened? Let's refer to the credit memo first. I have searched these two credit memo in the database and I only found 1 of them... I used their names, details, codes and other info to locate the other CM but I failed.
    SCENARIO:
    A/R CREDIT MEMO NUMBER follows a pattern of  (COMPANY NAME)-(CREDIT MEMO NUMBER)-(BRANCH)
    I have created a credit memo last April 12, 2011 with the document number (ABCD-20050002-MNL) generated by the system.
    with one item (BLUE TILE) and addressed to John Scott.
    We found out that another credit memo dated April 29, 2011 having  the same document number (ABCD-20050002-MNL) making it a duplicate of the first one. This second transaction has one item also (BLACK PAINT) and was addressed to Olivia Dunham.
    We found this when they are already printed or in hard copies. I just want to ask for your opinions, theory or suggestion with regard to this situation. Is there a possibility where it was duplicated while in the printing process?
    Looking forward to hear from you....
    Thanks!
    =)

    Hi Kambadasan,
    Thanks.
    I already checked the relationship and linking of number from the document to the layout printing and everything seems to be ok.
    It follows and copy's the exact numbers.
    Thanks again

  • Cancel Duplicate MIRA(Credit Memo)

    Dear All
    We are following LIV process.
    My case is as follows:
    I have done 101Movement type for GR,done MIRA and then MIR6 to post Incoming Invoice.
    Later ,rejected few quantity through line rejection by doing 122 Movement type(GR created).Then again raised Credit Memo which got held up due to some system error(Please note that accounting document is not created here).Then instead of posting this Credit Memo,raised new Credit Memo which got posted corrected and accounting impact is taken care off.
    My problem is to cancel  the earlier Credit Memo as Accounting effect is not taken care in this one and it is a mere duplication .
    Please advise.
    Thanks In Advance
    Payal Saxena

    Hi Payal,
    If you have only parked than you can delet the park document and post credit memo than you have reverse the document in MIR7
    Regards,
    Anil Chaudhary

  • MIRO - Credit Memo - Duplicate Check - Reference Field

    Hi
    I have created a credit memo in MIRO against an invoice with reference as 10000. Then I create one more credit memo with the same reference thru MIRO, system is allowing to post to the credit memo.
    There is no warning against the duplication.
    Any configuration is there to control the duplication in credit memo, please guide.
    Thanks
    Aras

    Hi,
    Make "Reference number" mandatory in 'Required during document entry segment' in "RE" document type in  OBA7 t.code
    Set Error  for message M8-471,M8-108 & M8-462 in t.code: OMRM .
    Regards,
    Biju K

  • 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

  • Error while adding A/P Credit Memo!

    Error while adding A/P Credit Memo..........
    'G/L Accounts' (OACT) (ODBC-2028) Message - 131-183
    Please advice me .....
    Thanks...

    Hi
    Check this thread this may help you.
    [Re: AP Invoice - No Matching Account Error]
    Regards
    Balaji

  • Credit memo generate in case of free goods

    Dear Friends
    one material price is rs450/- and with 5+1 when customer place order 5 pc that time system delivery 6 bec 1 is free. when customer return 1pc then what will be the credit memo pricing for each material.
    Thanking you
    Arun

    Dear Friends
    I am just clearly adding question with exact requirement.
    material per pc 450/- and scheme is 5+1
    order qty 5   Price is 450*5=2250
    dlv qty 6
    now client generate credit memo request for one pc in sap it is coming Rs450/- pc
    but client requrement is not this
                               2250/6=Rs. 375/- that mean they will give rs 375/- per pc not Rs 450/- per pc. for that what should i do customisation for credit memo request pricing.
    regards
    arun

  • Sale Order Credit Block due to open credit memo

    Dear All,
    System is blocking sale order for open items(credit). And the only open item is credit memo.
    Can we avoid credit note to be considered as open item?
    Thanks
    Arun

    Dear Arun,
    Do not think this is possible in standard.
    I would suggest the following way.
    Currently system is giving a message during sales order creation . right?
    Ask your abaper to find an EXIT before that point.
    There write a code to exclude CREDIT MEMO document types from BSEG of the customer code.
    It is possible as i have worked in similar requirement.
    Check and revert back.
    Thanks & Regards,
    Hegal K Charles

  • Error while creating a credit memo with reference to invoice

    HI aLL,
    I am facing one issue while creating a credit memo request in VA01 with reference to invoice.
    Our project stock is valuated stock.
    When we try top copy the error pops up" Valuated project stock not allowed with customer stock." and the line item is not copied in the credit memo.
    Diagnosis:The entered wbs manages a valuated project stock,at the same time sales order stock is maintained on sales order line item.this combo is not allowed as different valuation methods within a project is not allowed.
    Tarun Kapur

    Dear Tarun!
    1.Within a project we can get stock only in PROJECT or in SALES ORDER STOCK.....a single material can not be a both place at particular time ..so keep only one
    Project Stock or Sales Order Stock..
    2.Check DIP PRofile (ODP1) in usage BILLING AND RESULT ANALYSIS -Charectiristic -SDOC TYPE CMR.....are you selecting right document to which you want to copy .....
    Rewards Points if usefull
    Regards
    SMITH

  • Applying A/P Credit memo

    2007A PL49
    Have a GRPO in system.  Have not created an A/P invoice yet for the material.  Also have a vendor credit that has not been created in SAP either.
    How, if I can, apply the credit memo to the A/P invoice?  Do i create a service A/P invoice so as to not disturb inventory (but leaves GRPO open)?  Or create item A/P invoice (as normal)  and create service A/P credit memo? 
    Thanks,
    Rich

    discovered a solution to my own question and i will share regardless, with the SDN community:
    1.     Create the A/P invoice as normal (item a/p invoice tied to GRPO)
    2.     Create the A/P credit memo as a service memo (service memos do not disturb inventory qtys.)
    3.     Reconcile the A/P invoice under business partners > int. recon
    a.     Enter the vendor code, choose manual
    b.     Checkmark the Credit memo and the invoice to be paid
    c.     Enter the amount of the invoice in the u201Camount to reconcileu201D field for credit memo (if CM has more cash than invoice, vice versa)
    4.     Click Reconcile

  • UoM field in A/P Credit Memo

    Hello Gurus,
    I'm currently using SP01 PL04.  Programmatically saved a A/P Credit Memo in draft with Base Unit=tYes, the quantity is fine but the UOM is still the purchase UoM.  Please Help...

    Hello Gilbert,
    Yes it is shown the UoM is still the purchase UoM you defined, but actually the UoM does not work any longer since you have chosen Base Unit=Yes.
    That means when the document is submitted, the quantity in stock would decrease by 1 (if you input quantity=1), rather than decrease by 1*items/unit. You can find that from the total price in the row, or after submission from the item master data -> (find the item) -> inventory data -> in stork.
    Hope that helps.
    Nick

  • Deleting/Voiding an A/P Credit Memo

    I accidently entered in an A/P Credit Memo which should not be in the system. I cannot figure out a way to get it out. Can someone please let me know if there is a solution to this problem?

    Hi Andrew,
    it is not possibile to cancel a credit memo, the cancellation document is an invoice.
    Hence the cleanest way of reversing this incorrect AP credit memo is to create a corresponding AP invoice using the same items, quantities, prices & dates as in the CM. This will reverse the stock transactions & also balance the BP account balance.
    Once you have created the invoice, you need to manually reconcile the 2 transactions.
    Once they're reconciled, you can exclude them from the vendor statement by clicking on 'Display unreconciled transaction only' in the ageing report.
    If there was no stock transaction in the CM, then technically you could also use a manual journal entry, pull up the JE created by the credit memo & then create a manual JE with the opposite data. You still need to reconcile manually, though.
    All the best,
    Kerstin

  • GL Account Missing : A/P Credit Memo

    Hi
    I am trying to create A/P Credit memo by copying A/P Invoice.
    I am getting the error: GL Account Missing : A/P Credit Memo.
    Kindly solve this.
    Regards
    pawan

    Hi Pawan,
    Check sales Return account are defined in Warehiuse accounting Setup and aslo
    check the following thread
    GL Account missing in AR Credit Memo
    Issuing a Credit memo - G/L account is missing
    AR Credit Memo - Account Missing Error?
    GL Account Missing: A/R Credit memo
    *Close the thread if issue solved.
    Regards
    Jambulingam.P
    Edited by: Jambulingam P on Jul 25, 2009 12:03 PM

  • Error While doing the Asset Credit Memo -ABGL

    HI,
    While doing the Asset Credit Memo -ABGL,i am getting the below error.Kindly help me with your inputs.
    Balance for transaction type group 10 negative for the area 01
    Message no. AA629
    Asset affected: 406000000004-0000
    Diagnosis
    With the transaction entered, the balance for the transactions in group 10 in area 01 will be negative in this fiscal year. However, the balance of transaction type group 10, according to its definition, must be positive in each fiscal year.
    System response
    The system rejects this posting.
    Procedure
    Check the transaction type, the amount and the fiscal year in your posting. If you want to post a credit memo to an acquisition from the previous year, then use a transaction type for a retirement. If necessary, you can change balance rules after talking with your SAP consultant.
    Thanks
    Supriya

    Check your config in OABN / OADB
    The depriciation area 01 can allow you post values only postive .. in OADB
    it has maintained Acquisition values Postive or zero values and net book
    values has miantained Postive or 0 values. so based on this setting u cannt
    post any negative values for this asset.

Maybe you are looking for

  • Invoice report with BPChCODE and BPChName

    Hello Xperts I want to produce a report that will show Invoices by country and their BPChCODE and BPCh NAME In order to get the BPCh name, I have linked a second OCRD Table. but now the query gives me only the Invoices that has BPChCODE, I want to se

  • Exceptions while creating ABAP client Proxy

    Hi Experts, I tried to create a client proxy on the CRM system for a web service URL (where the WSDL exists), in the transaction SE80. When I tried creating this, i got exception as follows. Exception occured in communication framework:error in HTTP

  • Risk Categories in credit management

    Hello Gurus, How can I get the configuration details for the different risk categories that are defined in an sap systems for credit controlling area? Thank you.

  • Photoshop CS5: Any color with zero red information will turn black

    I've been having this problem ever since I installed Photoshop CS5 (12.0.4) on a Windows 7 64-bit machine. I've used the program on a Windows Vista 64-bit PC in the past with no problems. Any color that has zero red information will turn black when i

  • Error when adding keyframe

    Hey all! So I'm getting a memory error when I try adding a keyframe to a rather large flash file that says "Not enough memory available" but I know I have plenty. I'm running a 3.0ghz Quad core with 8GB of ram and about 100 gigs of HD space free on e