Creation Credit memo

If customer claim return of 5 kg, but the actual goods return is only 3 kg, however customer needs to credit 5 kg back to customer.   Current situation: credit memo for 3 kg is creation based on return delivery, the credit memo for another 2 kg is created by FI.   we wish to be able to create only 1 credit memo for the 5 kg.  To be discussed in Integration with FI" 
Pls help me to know any possibility on this
Thanks in advance

Maintain Return Sales Order as Order Related Billing and do not link to return quantity.
Incase of Return Sales Order:
T.Code for copy control: VTAF
Source Document: F2
Target Document: RE
Item category REN
Considering the above settings are done:
Create return sales order RE (with Reference to Billing Document) & the data will be copied as it is in Return Sales Order - RE. For Eg: here you require to change to quantity from 10 to 2, as you want to take back into Inventory of only 2.
Incase of Return Delivery:
T.Code for copy control: VTLA
Source Document: RE
Target Document: LR
Item category REN
Considering the above settings are done:
Create Return Delivery through T.Code VL01N & do PGR (Post Goods Receipt). This will add the stock to blocked stock. This will take care of Inventory.
To address the issue of how to take Credit for Excise, use T.Code: J1IH --> other Adjustment & based on the credit to be taken, make the necessary entry.
Incase of Credit Memo:
T.Code for copy control: VTFA
Source Document: RE
Target Document: Credit Memo
Item category G2N (Check in System)
First in VA02, remove the Billing Block in Return Sales Order - RE & save the document. Now in T.Code: VF01, enter Return Sales Order Number & select the appropriate Billing Type (Credit Memo) & Enter& Save. This will create Credit Memo.
Regards,
Rajesh Banka

Similar Messages

  • Dispute Case creation (credit memo reference to Billing invoice)

    Hey
    We are using SD module to create Billing invoices and Credit Memo's.
    1. Dispute case created for Accounting invoice (Generated from Billing invoice).
    2 Credit memo raised in reference to billing invoice and FI document generated for Credit memo.
    We are in need to add Credit memo to the existing Dispute case in the Billing invoice.
    I have tested this scenario and this is not an standard. Any inputs in this regard is highly appreciated.
    Thanks
    Rajanikanth.

    adding the credit memo is not available as standard.
    Object type BUS2094 is the object type for a sales order - so you could use this - but this will bespoke

  • FM to create a Credit Memo Request

    hi,
    i have to create a credit memo request that will be created on creation of debit memo. actually output determination of debit memo will trigger the creation credit memo request.
    please provide me a FM to create a Credit Memo Request.
    regards

    Hi,
      Try to use the BAPI BAPI_SALESDOCU_CREATEFROMDATA1
    Please check this thread for sample codes.
    https://forums.sdn.sap.com/click.jspa?searchID=46332&messageID=2304043
    rEGARDS

  • Withholding Tax in FB75 Recording - Creation of Credit Memo

    Hi Xperts,
      Here I have one problem while Creating Credit Memo using BDC.
            - I am trying to write a BDC for transaction FB75 ( Creation of Credit Memo)
            - All things are going fine except Withholding Tax part.
            - Transaction FB75 have a Tab "Withholding Tax".
            - Here, there is a Table control with 6 rows.
            - While creating Credit Memo it populate this table control with Withholding  taxes.
            - The main task is,<b>Based on certain condition, I want to clear few Withholding tax values.</b>
            - If This table control has only 6 rows populated, then there is no orblem.
            - But in case of more then 6 withholding tax values i need to scroll down and process, however, that again we can do using p++ or P+ things.
            - Problem is, in this case we are not able to scroll down or page down which create a problem in accessing other rows.
            - What would b the solution......?
              Lets have brain Game for all ABAP Consultants................
    Thanks in Advance,
    Chetan Joshi.

    Hi Vijay
    credit memo request is a sales document used in complaints processing to request credit for a customer.
    EXAMP--->
    If the price calculated for the customer was too high (for example, with the wrong scaled prices or because a discount was forgotten), you can create a credit memo request. The credit memo request can be automatically blocked for checking. Once it has been approved, you can remove the block.
    The system uses the credit memo request to create a credit memo.
    the credit memo request(CR) Iis created ith referance to invoice based on configuration settings in vov8 and credit memo(g2)created refarance to credit memo request
    refer to the links below.. might be of some use to ..
    Credit Memo
    http://help.sap.com/erp2005_ehp_02/helpdata/en/a8/b99890452b11d189430000e829fbbd/frameset.htm
    Creating Credit Memo / Debit Memo
    http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/561076545a11d1a7020000e829fd11/frameset.htm
    Creating Credit Memo / Debit Memo Requests
    http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/55fed1545a11d1a7020000e829fd11/frameset.htm
    Credit & Debit Memos
    http://help.sap.com/erp2005_ehp_02/helpdata/en/a2/40418a496e11d3b3850008c719be0f/frameset.htm
    Processing Credit Memo : Example
    http://help.sap.com/erp2005_ehp_02/helpdata/en/4e/b3c399a1f711d194e700a0c9306794/frameset.htm
    Regards,
    Ramana

  • Credit Memo Creation - Sold-to-party / Ship-to-party fields

    I am trying to create a SD Credit memo document.
    From the thread Credit Memo Creation I understand that  the BAPI BAPI_SALESORDER_CREATEFROMDAT2  cant be used and instead I gotta use the FM SD_SALESDOCUMENT_CREATE for this purpose.
    On this backdrop, I am trying to pass sold-to-party / ship-to-party values into this FM.
    But, in the structure SALES_HEADER_IN type BAPISDHD1, I couldnt find the fields to pass these values.
    Please advise the name of the fileds/structure where I should pass shiptoparty and soldtoparty values.
    In VA01 screen, you could see these fields.
    Thanks,
    Message was edited by:
            Jay
    Message was edited by:
            Jay

    jay,
    check the below link for couple of sample codes...
    Re: BAPI_SALESDOCU_CREATEFROMDATA, create credit memo request
    May be helpful for you
    ~~Guduri

  • Document still appears on Billing Due List after creation of Credit Memo

    Hello everyone!
    I would like to seek your help in knowing the reason why documents in the Billing Due List dated on or before June 30, 2008 with billing type ZRJF would require three creations of Credit Memo before the delivery returns status will change from "being processed" to "completed." Please note that there was a configuration made on June 31, 2008 in the copy control of ZREF to ZRBO wherein the pos./neg. quantity of item cat ZRBO was changed from to (+).
    Moreover, what should I do with the documents in VF04 dated on or before June 30, 2008 that still appears after one creation of credit memo?
    Thanks in advance. Have a great day to all!

    Hi Ravi,
    Thanks for your prompt response. I checked the delivery return status and it is still "being processed" eventhough I have already created a credit memo for all the returned goods.
    I actually observe this in my documents dated on or before June 31, 2008. At that time, the copy control pos./neg. quantity was set to negative (-). Is this the reason why documents still appear in the billing due list? If so, what should I with these documents so it will no longer appear in the Billing Due List?
    Thank you very much!

  • Automatic creation of debit or credit memo

    Hi All,
    I have a requirement of automatic creation of credit note with reference to sales order when i click save at transaction VF01 after generating billing document against delivery number.
    I used the include ZXVVFU08  it is triggered when the save button is pressed in VF01. i have wriiten BDC code in this include. At the point when i click save, the billing number is getting generated but credit memo is not getting generate.It is giving an error 'No billing documents were generated'
    How do i ensure that the invoice number is already saved before the BDC starts?
    Need help. Thank you!

    Dear seetharamsapsd ,
    Create a new document type for both credit memo and debit memo requests.
    Copy control to the respective credit memo and debit memo should be there.
    Pricing procedure should contain provision to map the difference amount.
    Create  a Z program recording a BDC for the creation of Debit and credit memo request.
    It is better to keep have only one Z program.
    In the program write a logic to check the price change comparing the values of previous month created orders and
    this months condition record values.
    Based on whether there is increase or decrease , system should run the respective BDC for the debit or credit memo request.
    This program can be set in background maybe at midnight.
    Also save VF04 as a background job (so that the debit / credit memos as also created automatically)
    Set this VF04 background job to run after say 1 or 2 hours from the time our Z program is running.
    I hope you know the different tables/fields from where you can get the desired condition to run the program.
    Thanks & Regards,
    Hegal K Charles

  • Need API for Credit Memo creation-R12

    Hi All,
    I am working on R12 Implementation process.  I have a requirement for creating the "Credit Memo" using API.
    Could you please any one provide the API for Credit Memo creation process.
    Thanks,
    LSP

    Hi,
    Please refer the following links:
    http://www.betteroracle.com/2012/08/ar-api-create-credit-memo-r12.html
    http://easyoracleapps.blogspot.com/2011/08/creating-credit-memos-and-appling-these.html
    http://prasanthapps.blogspot.com/2011/05/credit-memo-creation-via-api.html
    Googling will help you indeed
    Rgds,

  • Creation of credit memo

    Hi
    I started creating a credit memo request. I filled all the item data. But the processing status is displayed as 'incorrect'. When i leave the tab ' reason for rejection' blank , i get the processing status as 'processed'. I dont understand the relation.
    When i try creating a memo(with request whose status is 'processed'), I am getting the status of memo also as 'incorrect'. I find the error message" order type ' credit memo request' cannot be used to create billing type 'credit memo'".
    I am not able to find a solution to overcome this and complete the creation of Credit memo.
    Pl suggest

    Hi,
    Kindly confirm weather it is Reason for rejection or Order reason which you are talking about.
    By the way to crate the memo both the order reason and the reason for rejection should be blank.
    Now check which docu type u r selecting for the credit memo request and credit memo.
    Pls Reward if helpful
    With Regards,
    Ranjith

  • Creation of Credit Memo request from Invoice.

    Dear All,
    We have requirement for creation of CRM Credit Memo request from CRM Invoice.
    Please guide any one if you have clue on this requirement.
    Regards,
    Mallik Kosuru

    This can be achieved by creating  complaints . You create a complaint -credit memo request-credit memo  with reference to billing document, refer to C28 CRM complaints for more info.

  • Update Billing Document During Credit Memo Creation

    Hi,
    I need to update the billing document during credit memo creation in VA01. Is it possible to achieve this requirement since the billing document is in use during the runtime?
    Thanks & Regards,
    Mawi

    Hi Mawi,
          When you are trying to change billing document use CALL FUNCTION 'DEQUEUE_ALL'. It will unlock that billing number and you can change that billing document.
    Thanx & Regards
    Rami Reddy

  • Re: Credit memo creation - Update terminated

    Hello
    I have a issue related to Credit memo creation.
    When i try to create a Credit memo with reference to Credit memo request, below error is appearing.
    Express error - Update was terminated
    Error info - TD465: device type ZHPLJCM1
    Credit memo number is getting generated but when i go to view mode (VF03) there is no credit memo in the database.
    Even in table VBRK, no data is available.
    Could you please suggest how to resolve this issue.
    thank you
    Anirudh

    Hello,
    Goto Transaction code SM13 and clilck on the ALL option in Status and Execute.
    Then it will lead to the next screen where you have option  of MODULES, click on it and and it will give the Program and Technical data.
    Clearly it will give the details where the problem lies, Work with your ABAPER and fix.
    Regards,
    santosh

  • Vendor Credit Memo creation in SAP via IDOC Interface (Inbound)

    Hello Team,
    I have a client requirement to create Vendor Invoices & Credit memo via Idoc Interface. Iam using INVOIC02 idoc type for posting Invoices and could able to create the invoice successfully. For credit memo , I'm aware that we can use the same idoc type (INVOIC02) and need to pass CRME value for the segment field BSART.
    What i need is a sample Inbound INVOIC02 idoc file for credit memo to identify the required fields for successful credit memo creation.
    Regards,
    Vijay

    Hello Team,
    I have a client requirement to create Vendor Invoices & Credit memo via Idoc Interface. Iam using INVOIC02 idoc type for posting Invoices and could able to create the invoice successfully. For credit memo , I'm aware that we can use the same idoc type (INVOIC02) and need to pass CRME value for the segment field BSART.
    What i need is a sample Inbound INVOIC02 idoc file for credit memo to identify the required fields for successful credit memo creation.
    Regards,
    Vijay

  • Need to avoid credit memo creation if the value is zero'0'

    Hi All,
    I want to avoid the creation of Credit Memo if the value is zero, how this can be controlled in SD. Please pore your ideas.
    Regards,
    Ragu

    Hi,
    In standard SAP system, Credit memo is created with reference to
    1) Credit memo request
    2) Return order 
    3) Invoice correction request.
    Before releasing these docs for Credit memo creation, check whether the
    value is non-zero.
    You can put a billing block(Check credit memo) on these documents if the value is ZERO.
    And the billing block will only be removed if the value of the doc is non-zero,and a Credit
    memo can be raised from these doc.
    Second alternative is to check the value in prior request doc by ABAP enhancement,
    and if it zero do not create the request/document.
    Thanks ,
    Umesh Karane.

  • 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

Maybe you are looking for

  • Calling Crystal Reports from Oracle Forms 10G

    Hi everyone, I am trying to call a crystal report from Oracle Forms 10G. I have a button on my Form which when clicked calls a Crystal Report which the uaser then wants to save as a PDf file. Can someone please send me the code to do this and also th

  • Error with month end payroll Accruals

    We have an error when posting month end payroll accruals for our weekly payroll, though the bi-weekly payroll works fine! I have checked tables T549S and T51A1 and all of the dates are correct and set as I would expect, however the system did not cre

  • Reg : nQSError:10058 in OBIEE

    Hi Experts, Am getting the following error in my dashboard.Can anyone provide inputs as what is the cause of this issue and how to resolve it. nQSError: 10058] A general error has occurred. The backend MDX query did not generate correct output and co

  • Batch Management Process Flow Diagrams

    Hi, please provide the process flow diagram of batch mangement in MM. any links or documents.... It's urgent... Thanks AK

  • How do install EPC header on the ASR router? or is it now part of the IOS?

    There was a discussion of using the router to look at the trace capture from the router, I downloaded the EPC header, but don't know to install.  Is there any documentation on how to install the script file onto the ASR router?  Thank you Osh