Billing Document User Exit

Is there a user exit that I can use when a Billing Document (in SD) is being created to change the NAST record ( specifically field VSZTP ) based on certain conditions.
Thanks
Amit

Try EXIT_SAPLV60A_002 in enhancement V60A0001.
Or here are userexits triggered by VF01 and VF04:
SDVFX007            User exit: Billing plan during transfer to Accounting
SDVFX008            User exit: Processing of transfer structures SD-FI
SDVFX009            Billing doc. processing KIDONO (payment reference number)
SDVFX010            User exit item table for the customer lines
SDVFX011            Userexit for the komkcv- and kompcv-structures
V05I0001            User exits for billing index
V05N0001            User Exits for Printing Billing Docs. using POR Procedure
V60A0001            Customer functions in the billing document
V60P0001            Data provision for additional fields for display in lists
V61A0001            Customer enhancement: Pricing
<i><b>Points are always welcome!</b></i>

Similar Messages

  • Cancel Billing document User Exit

    Hi,
    The requirement at our client is as follows:
    In transaction VF02, if the user selects to cancel the billing document "Menu: Billing document->Cancel", then we need an user exit to check that, for a particular pricing condition if an accounting document exists. If so, then put out a message and stop the cancel from happening.
    Are there any user exits that get triggered specifically when cancelling a billing document so that I will have access to VBRK, VBRP and KONV data to read table BSET?
    Any suggestions will be appreciated.
    TIA.
    Cheers,
    -Ramesh

    Hi Ramesh,
    In configuration of the billing document type, there is a section for 'cancellation'. In this section, you can enter a copying requirement. In that requirement(probably your custom one), you can write the logic for your purpose. You can see this configuration by following the path
    IMG--> Sales and Distribution
           -->Billing
              -->Billing Documents
                 -->Define Billing Types
                    -->Define Billing Types
    Once you select your billing type and do the display, you will see this section in there.
    Srinivas

  • Copy header text from DO to billing via user-exit

    Dear Experts,
    We have a requirement to copy one text field in the DO header to Billing header text field. I've searched the forum before posting this one but none seems to fit my requirement. I am using RV60AFZC form USEREXIT_FILL_VBRK_VBRP for this. From VF01, I see the header text was populated but after saving, it is being cleared out. I suspect the copy control from sales order to billing header text is doing this, nothing is saved in the SO.
    Any idea how to do this by configuration or by user-exit/enhancement spot?
    Looking forward for your responses.
    Thanks in advance.
    nEnE

    Can you please check VOFM>Copying Requirements>Texts, Routine 1. The documentation states:
    "This requirement checks if the reference document header has a text entry.  If so, it is automatically transferred. This requirement is assigned in the detail of the access sequence for header text determination."
    You can copy this in a 9XX routine number and write your specific code there.
    Hope this helps!

  • Billing output user exit

    Hi,
    My requirement is to have checking on material price during billing process.
    When billing document posted -> the output determination is set automatically. But when user try to print the billing doc, I want to have some checking on material pricing group and be able to show error message if pricing not maintained.
    Is there any user exit can be used ?
    Thanks,
    Melissa

    Hi Melissa,
    You need to get a routine written through VOFM and need to assign this routine in Billing Output Rocedure with the output Type in the requirements column.
    You need to identify the Material Pricing group which particular groups/ else identify the Pricing Condition type which is responsible for this Material Pricing group based discount/surcharge and look for the values from KONV table the PK-FK relationship between VBRK/VBRP table and KONV table id done through KNUMV field in the billing tables ,take that number and then go to KONV look for that particular Condition Type KSCHL Files and its value in KWERT/KBETR check if the vlaue is not null.
    Hope it helps.

  • Create new BPS documents from "COPY DOCUMENTS" user exit.

    Hi Gerd,
    thank you so much for your reply.
    I'm continuing other thread here. (Copy "document icon" to new sheet from "SEM-BPS 1" sheet)
    <b> We've a layout that doesn't use macros. </b>
    We'd like to attach a document for each line that is entered on this layout. All the document attribute characteristics are included in this layout.
    Document contents & technical name can be any thing.
    Should I be able to do this?
    This ensures that users be able to edit documents on other layouts which is crucial.
    I tested this For couple of lines and I was successful.
    Before I'd like to start implementing this, I appreciate your inputs on the prcoess that I follow if this is an effective way of doing?
    Any concerns from the performance side?
    any other hidden issues/concerns that you might be familiar with?
    1) I'm reading all document attribute characteristic values of the layout new lines from the user exit.
    2) I've created one variable for each "document attribute characteristic"
    3) I've created "COPY DOCUMENTS planning function" and included variables in the parameter group
    4) user exit in step 1 fills all variables (fills only 1 value at a time) & passes to "COPY DOCUMENTS parameter group"
    4) due to restriction of only single entry variables usage in
    "COPY plannig funciton", I'm using "API_SEMBPS_FUNCTION_EXECUTE" and executing "COPY DOCUMENTS planning funciton" as many times as number of new lines
    5) if there are 6 new lines, user exit in step 1 loops 6 times & calls "API_SEMBPS_FUNCTION_EXECUTE" 6 times which inturn executes "COPY DOCUMENTS planning funciton" 6 times
    Am I on the right & effective path?
    Is there any better approach?
    Appreciate your inputs

    Hi,
    This is one way you can do that. The bad side of your implementation is that the planning function is called 6 times. It would be better to copy the coding of the planning function and modify it in such a way that you can do all of the steps in one go. If the performance is all right I would still leave it the way it is as then you do not have to change to coding.
    Best regards,
    Gerd

  • How to Suppress billing  using user exit EDMSUBI

    Dear ALL,
    Could anyone let me know how to use this user exit EDMSUPBI.  Basically my requirements is to suppress billing for certain meter readings during upload of reading using meter reading upload BAPI.
    This user exit gets triggered during the above mentioned meter reading upload event. But I would like to know how to pass the parameters to enable the suppress billing order functionality.
    There are no export or import parameters in this user exit. Whereas  the user exit has the following tables
    XT_EABL
    XT_EABLG
    XT_ETRG
    YT_SUPPR_ETRG
    YT_DEACT_EABL
    Let me know how to pass the paramets such that the suppress billing order functionality is enabled
    WIth Regards
    Balaji.J

    If you still care:
    You will have to access the mtr_obj in memory to get informations.
    DATA:
           ls_obj TYPE ISU17_METERREAD.
       import  xy_obj TO ls_obj
           FROM memory  id 'ISU_MR_EXIT_SAPLEL01_015'.
    Cheers.

  • Sales order Change document user exit

    A colleague of mine has been asked if there is a way of inserting a different username to the standard one when a change document is created for the sales order header.  Is there a userexit that would suffice?
    Thanks in advance
    Ian

    You have only one option as far as I know:
    All change document creation occurs in function
    CHANGE_POINTERS_CREATE centrally.
    The only option would be to apply a repair to this function to set the username (CDHDR-USERNAME) to the value you want. You would do this only for sales document change docs - object class is VERKBELEG I think. This is also held on CDHDR.
    Hope this helps.
    Cheers
    Colin

  • USER EXITS IN BILLING

    HI ALL,
    Scenario. Billing document created and the user wants to cancel the billing document after the closing period . but the system should not allow to do that what is the user exit to be used ?
    Please provide the user exit
    Regards
    Anil Mairpady

    Dear Anil,
    Instead, what i would suggest to discuss with FI-Personnels and resolve the same.
    Best Regards,
    Amit.
    Note: As far as, your exact requirement is concerned, Lemme check and If, I come-up with some alternate solution, I'll definitely update. meanwhile, you may check with BAPI_BILLINGDOC_CANCEL1 (haven't much knowledge about it as never encountered such requirement at my end).
    Also, you may look in to following threads, if you get some helpful information:
    [Thread1|Fixing Billing Date in vf11 (cancel billing Document)]
    [Thread2|User-Exit to cancel a  Billing Document]
    [Thread3|Cancel Billing document User Exit]
    Edited by: Amit Yadav on Dec 8, 2008 7:08 AM

  • To set the "Pricing Exchange rate type" in the billing document

    Hello SAP Experts,
    I have a customer requirement to determine the "pricing exchange rate" as "C Exchange rate determination according
    to Billing date" in Billing documents ONLY for specific Sales Org and customer Country and NOT for ALL sales orgs.. This field is present in the Item level copy control setting.
    This will ensure Exchange rate will be based on "Billing date" and NOT from date copied from Sales order for that specific Sales org.
    Can I write this validation in the Billing document User-exit -RV60AFZC to achieve this functionality? Or there would be some Configuation required?
    If anyone has worked upon this kind of requirement or know the method to achieve this, can you please help me?
    Thanks in advance.
    Umesh Karane.

    In that case, you can try with  USEREXIT_FILL_VBRK_VBRP.  Alternatively, you can also add this logic to your existing routine assigned in Delivery to Billing copy control against the field "Data VBRK/VBRP".  Similarly, for all such copy controls as you mentioned.
    G. Lakshmipathi

  • GTS Billing document of orders that are blocked should be prevented

    Hi GTS Gurus:
    I am trying to find a way to prevent billing documents from created if its sales order document is blocked by GTS. Seems like that I have 2 choices, either use billing document user exit or use VOFM routines. I looked note 579357, it contains example code to stop delivery from being created. Can I use the same example in note 579357 to stop billing document from being created? If so, which routine in VOFM should I use?
    thanks!!

    Hi Jim,
    All the orders relevant for Compliance/Customs/Risk check will be passed on to GTS. If the check turns to be positive, then the subsequent order will be blocked for delivery and hence billing cannot happen.
    Are you looking for to activate this for order related billing and not delivery related billing scenarios?
    Thx
    Sathees G

  • User Exit in VF01 for Tax Conditions

    Hello,
    Please inform if any user exit is available for processing Conditions (Tax) in a Sales Order.
    I'm facing a problem that while Invoicing, a certain Tax condition is not being executed.
    Thanks,
    Shalabh Jain

    HI Colleague,
    I will list the available user-exit to be used for Billing Document:
    User Exits For Billing
    USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
    The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created.
    USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
    In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields).
    USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
    In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields).
    USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
    Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy). USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
    USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
    This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data.
    USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
    Printing the item line of a billing document can be supplemented or changed.
    USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
    Printing the header line of a billing document can be supplemented or changed.
    User exits in program RV60AFZD
    Short descriptions of the user exits are contained in the program:
    USEREXIT_RELI_XVBPAK_AVBPAK
    USEREXIT_NEWROLE_XVBPAK_AVBPAK
    USEREXIT_NEWROLE_XVBPAP_AVBPAK
    The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):
    EXIT_SAPLV60B_001: Change the header data in the structure acchd
    You can use this exit to influence the header information of the accounting document. For example, you can change the business transaction, "created on" date and time, the name of the person who created it or the transaction with which the document was created.
    EXIT_SAPLV60B_002: Change the customer line ACCIT
    You can use this exit to change the customer line in the accounting document. This exit is processed once the ACCIT structure is filled in with data from document header VBRK.
    EXIT_SAPLV60B_003: Change the customer line in costing
    The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure.
    EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item (such as quantity specifications) with this exit.
    EXIT_SAPLV60B_005: User exit for accruals
    Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit.
    EXIT_SAPLV60B_006: Change the control line ACCIT
    You can use exit 006 to add information to the control line.
    EXIT_SAPLV60B_007: Change the installment plan
    You can use exit 007 to add information to the installment plan
    parameters in the GL account item.
    EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD
    After the accounting document is filled in with data, you can use exit 008 to change the document once again.
    EXIT_SAPLV60B_010: Item table for customer lines
    You can use exit 10 to influence the contents of customer lines before they are created.
    EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account determination
    You can use this exit to change inbound parameters in order to influence account determination.
    I hope that one of them could be helpful.
    Regards
    Ruy Castro

  • User Exit - clearing document FBRA

    Hello,
    I'm clearing a document in FBRA and I want to make a validation.
    Is there any user-exit where I can make it?
    When I am reversing a document, it is possible to make the validations throught OB28, but not when clearing.
    Thanks in advance.

    Hi Ravi,
    Clearing is a standard option. It is possible, just to clear a document.
    When we reverse a document, we loose the connection throught AUGBL, between the reversed document and the one before it in the flow. For example, if I reverse a payment document, the connection throught AUGBL will be lost with the invoice document, in BSEG.
    In fact, what I want is not really a validation, but use OB28 and make this connection in a user-exit in programm PFM_1FIUE02 (we use ZPFM_1FIUE02 here).
    My problem is that, if I just clear a document, user-exit doesn't run. So if I reverse the document later, the connection throught AUGBL is lost and it is not possible to connect the reversed document to the one before it.
    Could you help find a solution?
    Thanks.

  • User exit for incoming PO - (PO is created by CIFing TLB order to R/3)

    Hi All,
        I need to find out the APO INBOUND user exit for reciving the PO information from the connected R/3 system. Initially a TLB order is created in APO and CIFed to APO and after the PO is created in connected R/3 system this PO number and related information is CIFed back to APO and this TLB order is replaced by the R/3 PO number.
    Please help me outto gain full points.
    Thanks in Advance,
    Chandan Dubey

    Hi,
    I am not clear with ur query and therefore check out the list of Inbound and outbound Idoc user-exits:
    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
    IDoc Outbound User Exits
    72.    ACCONF
    Confirmation of IDoc processing from the application
    ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
    73.    ACLPAY
    Accounting: Inbound invoice
    ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
    ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
    ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
    ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
    74.    ACPJMM
    Posting in accounting from materials management
    ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
    ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
    75.    ARTMAS
    Create and change of material master (Retail)
    MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
    76.    BLAORD
    Purchasing contracts
    MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
    MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
    77.    BLAREL
    Purchasing contracts
    MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
    78.    COND_A
    Conditions: master data for price determination
    VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
    VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
    79.    CREMAS
    Distribute vendor master
    VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
    80.    DEBMAS
    Customer master
    VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
    81.    DELPKB
    KANBAN call
    MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
    MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
    82.    DIRDEB
    Preauthorized withdrawal
    FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
    83.    DOCMAS
    Master document
    CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
    CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
    84.    DOLMAS
    Document-object links
    CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
    CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
    85.    FIDCC1
    Send entire FI documents (user exit 003/4)
    F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
    F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
    86.    FIDCC2
    Send entire FI documents (user exit 005/6)
    F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
    F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
    F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    87.    FIDCMT
    Sending single items for FI-GL
    F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
    88.    FIPAYM
    Payment data
    FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
    FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
    FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
    FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
    FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
    89.    FIROLL
    General ledger rollup for FI-GL (delta f. line items FIDCMT)
    F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    90.    GSVERF
    Cred. memo procedure
    MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
    91.    HRMD_A
    HR: Master data and organizational data (appl. system)
    RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
    RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
    RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
    92.    INFREC
    Purchasing info record
    MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
    93.    INVOIC
    Invoice / Billing document
    LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
    LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
    LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
    LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
    94.    KANBAN
    KANBAN call
    MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
    MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
    95.    LIKOND
    Listing conditions
    WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
    96.    MATMAS
    Material Master
    MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
    97.    ORDCHG
    Purchase order/order change
    MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
    MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
    MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
    98.    ORDERS
    Purchase order / order
    MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
    MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
    MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
    99.    ORDRSP
    Purchase order / order confirmation
    MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
    MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
    MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
    SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
    SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
    SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
    SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
    SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
    SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
    SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
    SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
    WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
    WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
    100.    PAYEXT
    Extended payment order
    FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
    FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
    FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
    FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
    101.    PICKSD
    Picking data confirmation to customer delivery
    VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
    102.    PRDCAT
    Product Catalog
    WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
    103.    PRDPOS
    Product catalog item
    WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
    104.    PRICAT
    Price list / catalog
    VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
    VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
    VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
    105.    PROACT
    Stock and sales data
    WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
    106.    REMADV
    Payment advice
    FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
    107.    REQOTE
    Inquiry
    VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
    VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
    VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
    VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
    VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
    VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
    VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
    VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
    108.    SRCLST
    Source List
    MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
    109.    SRVMAS
    Master data service master
    BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
    BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
    110.    SYPART
    Partner profiles
    SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
    SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
    SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
    SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
    SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
    SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
    SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
    111.    TPSDLS
    Shipping planning system: Transfer delivery
    V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
    V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
    V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
    V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
    V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
    V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
    V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
    112.    WBBDLD
    Assortment list: Material data
    WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
    113.    WMCATO
    Reversal/Reversal request for transfer order
    MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
    114.    WMINVE
    Inventory count input
    MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
    115.    WMRREF
    Release reference number
    MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
    116.    WMTORD
    Transfer order
    MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
    117.    WP_EAN
    POS interface: Upload / Download EAN assignments
    WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
    118.    WP_PER
    POS interface: Upload / Download person data
    WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
    WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
    119.    WP_PLU
    POS interface: Upload / Download material master
    WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
    WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
    120.    WPDCUR
    POS interface: Download exchange rates
    WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
    121.    WPDNAC
    POS interface: Download products
    WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
    WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
    122.    WPDSET
    POS interface: Download set assignments
    WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
    123.    WPDSET
    POS interface: Download set assignments
    WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
    124.    WPDTAX
    POS interface: Download tax rates
    WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
    125.    WPDWGR
    POS interface: Download material group master
    WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
    WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
    126.    WPUBON
    POS interface: Upload sales documents (compressed)
    WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
    127.    WTADDI
    Additionals
    WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
    128.    WTADDI_CVB1
    Additionals w/o 06
    WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
    General IDoc User Exits
    ALE00001 EXIT_RBDPROSE_001 Old: exit for converting preproduction system to production
    ALE00001 EXIT_SAPLBD11_001 User exit for the IDOC version changer
    BDMO0001 EXIT_SAPLBDMO_001 Old: Enhancement to the ALE distribution reference model
    KKCD0001 EXIT_SAPFKCIM_001 SAP-EIS: User exit for data compression of sender records (used for IDoc conversion)
    KKCD0001 EXIT_SAPFKCIM_002 SAP-EIS: User exit for data summ. Of summarized records befo (used for IDoc conversion)
    Link for the same:
    http://erpgenie.com/abaptips/content/view/302/62/
    Pls reward helpful points.
    Regards,
    Ameet

  • User Exits for Inbound Process

    hi all
    can any one please give some example user exits in inbound process and explain the omportance of user exits
    Thank you,
    Swapna

    hi
    Userxits allow us to add our own functionality to SAP standard program
    without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
    Types of User exits
    1. Menu Exits
    2.Function exits
    3.Table exits
    4.Screen exits
    5.Keyword exits
    6.Field exits.
    also refer to the links below.. can get more info on user exits
    list of user exits
    http://www.planetsap.com/userexit_main_page.htm
    can also get the list of user exits thru..
    Tcode: CMOD -> Utilities -> SAP Enhancements -> F8 Execute
    User Exits Notes:
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/81/8c5738ee806b0ee10000009b38f889/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
    below are some of the useful invound and outbound userexits
    <b>IDoc Inbound User Exits</b>
    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
    <b>IDoc Outbound User Exits</b>
    72.     ACCONF
    Confirmation of IDoc processing from the application
    •     ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
    73.     ACLPAY
    Accounting: Inbound invoice
    •     ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
    •     ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
    •     ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
    •     ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
    74.     ACPJMM
    Posting in accounting from materials management
    •     ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
    •     ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
    75.     ARTMAS
    Create and change of material master (Retail)
    •     MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
    76.     BLAORD
    Purchasing contracts
    •     MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
    •     MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
    77.     BLAREL
    Purchasing contracts
    •     MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
    78.     COND_A
    Conditions: master data for price determination
    •     VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
    •     VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
    79.     CREMAS
    Distribute vendor master
    •     VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
    80.     DEBMAS
    Customer master
    •     VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
    81.     DELPKB
    KANBAN call
    •     MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
    •     MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
    82.     DIRDEB
    Preauthorized withdrawal
    •     FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
    83.     DOCMAS
    Master document
    •     CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
    •     CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
    84.     DOLMAS
    Document-object links
    •     CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
    •     CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
    85.     FIDCC1
    Send entire FI documents (user exit 003/4)
    •     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    •     F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
    •     F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
    86.     FIDCC2
    Send entire FI documents (user exit 005/6)
    •     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    •     F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
    •     F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
    •     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    87.     FIDCMT
    Sending single items for FI-GL
    •     F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
    88.     FIPAYM
    Payment data
    •     FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
    •     FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
    •     FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
    •     FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
    •     FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
    89.     FIROLL
    General ledger rollup for FI-GL (delta f. line items FIDCMT)
    •     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    90.     GSVERF
    Cred. memo procedure
    •     MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
    91.     HRMD_A
    HR: Master data and organizational data (appl. system)
    •     RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
    •     RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
    •     RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
    92.     INFREC
    Purchasing info record
    •     MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
    93.     INVOIC
    Invoice / Billing document
    •     LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
    •     LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
    •     LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
    •     LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
    94.     KANBAN
    KANBAN call
    •     MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
    •     MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
    95.     LIKOND
    Listing conditions
    •     WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
    96.     MATMAS
    Material Master
    •     MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
    97.     ORDCHG
    Purchase order/order change
    •     MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
    •     MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
    •     MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
    98.     ORDERS
    Purchase order / order
    •     MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
    •     MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
    •     MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
    99.     ORDRSP
    Purchase order / order confirmation
    •     MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
    •     MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
    •     MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
    •     SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
    •     SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
    •     SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
    •     SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
    •     SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
    •     SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
    •     SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
    •     SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
    •     WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
    •     WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
    100.     PAYEXT
    Extended payment order
    •     FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
    •     FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
    •     FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
    •     FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
    101.     PICKSD
    Picking data confirmation to customer delivery
    •     VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
    102.     PRDCAT
    Product Catalog
    •     WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
    103.     PRDPOS
    Product catalog item
    •     WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
    104.     PRICAT
    Price list / catalog
    •     VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
    •     VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
    •     VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
    105.     PROACT
    Stock and sales data
    •     WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
    106.     REMADV
    Payment advice
    •     FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
    107.     REQOTE
    Inquiry
    •     VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
    •     VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
    •     VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
    •     VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
    •     VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
    •     VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
    •     VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
    •     VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
    108.     SRCLST
    Source List
    •     MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
    109.     SRVMAS
    Master data service master
    •     BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
    •     BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
    110.     SYPART
    Partner profiles
    •     SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
    •     SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
    •     SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
    •     SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
    •     SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
    •     SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
    •     SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
    111.     TPSDLS
    Shipping planning system: Transfer delivery
    •     V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
    •     V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
    •     V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
    •     V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
    •     V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
    •     V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
    •     V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
    112.     WBBDLD
    Assortment list: Material data
    •     WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
    113.     WMCATO
    Reversal/Reversal request for transfer order
    •     MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
    114.     WMINVE
    Inventory count input
    •     MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
    115.     WMRREF
    Release reference number
    •     MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
    116.     WMTORD
    Transfer order
    •     MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
    117.     WP_EAN
    POS interface: Upload / Download EAN assignments
    •     WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
    118.     WP_PER
    POS interface: Upload / Download person data
    •     WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
    •     WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
    119.     WP_PLU
    POS interface: Upload / Download material master
    •     WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
    •     WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
    120.     WPDCUR
    POS interface: Download exchange rates
    •     WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
    121.     WPDNAC
    POS interface: Download products
    •     WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
    •     WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
    122.     WPDSET
    POS interface: Download set assignments
    •     WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
    123.     WPDSET
    POS interface: Download set assignments
    •     WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
    124.     WPDTAX
    POS interface: Download tax rates
    •     WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
    125.     WPDWGR
    POS interface: Download material group master
    •     WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
    •     WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
    126.     WPUBON
    POS interface: Upload sales documents (compressed)
    •     WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
    127.     WTADDI
    Additionals
    •     WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
    128.     WTADDI_CVB1
    Additionals w/o 06
    •     WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
    General IDoc User Exits
    •     ALE00001 EXIT_RBDPROSE_001 Old: exit for converting preproduction system to production
    •     ALE00001 EXIT_SAPLBD11_001 User exit for the IDOC version changer
    •     BDMO0001 EXIT_SAPLBDMO_001 Old: Enhancement to the ALE distribution reference model
    •     KKCD0001 EXIT_SAPFKCIM_001 SAP-EIS: User exit for data compression of sender records (used for IDoc conversion)
    •     KKCD0001 EXIT_SAPFKCIM_002 SAP-EIS: User exit for data summ. Of summarized records befo (used for IDoc conversion)
    ===
    User exits for Pricing.
    1.•USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ
    2.•USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
    3.•USEREXIT_FIELD_MODIFICATION
    4.•USEREXIT_FIELD_MODIFIC_KZWI
    5.•USEREXIT_FIELD_MODIFIC_KOPF
    User exits for Sales order
    1•USEREXIT_DELETE_DOCUMENT
    2•USEREXIT_FIELD_MODIFICATION
    3.•USEREXIT_MOVE_FIELD_TO_VBAK
    4.•USEREXIT_NUMBER_RANGE
    5.•USEREXIT_SAVE_DOCUMENT
    User exits for billing
    1.•USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
    2.•USEREXIT_ACCOUNT_PREP_KOMPCV
    3•USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
    4•USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
    5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
    ====
    Reward if USeful
    Thanx & regards
    Naren..

  • Brief about enhancements and user exits

    hai,
    can any  one tell me what are enhancements and user exits in sap sd,
    their  signifcance & configuration
    regards
    sriram

    hi,
    an example of user exit
    In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the “Target *** Qty required” and the “Target *** Date” for a specific customer who was not sending “*** Qty Received” by him.
    So for that specific customer we used the search term and added the same in the “Data 4” field of the IDOC under segment E1EDK09.
    There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating “*** Issued” and then find out the difference from “Target *** Qty” and get “*** Qty Received” for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
    <b>User exits in SD</b>
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Pl reward if helpful.
    Thanks
    Sadhu Kishore

Maybe you are looking for

  • What does the orange light on the power cord mean?

    i have a brand new Macbook and am charging it for the second time but when I plug it in the power adaptor goes green then orange? Anyone know what this is? i do not see anything about this online or in the manual. thanks, mark

  • Warning: [unchecked] unchecked call to getMethod when updating to JDK 1.6

    I'm received the following compilation warnings after I switched to Java 6 from Java 5: warning: [unchecked] unchecked call to getMethod(java.lang.String, java.lang.Class<?>...> as a member of the raw type java.lang.Class removeChangeListener = myPar

  • How does object memory management works?

    Hi all, I'm having a lot of problems with memory which seems not to be released when using objects (on Oracle 9i 9.0.1.1.1). I've prepared the following test: create type t_test as object ( id number, member function FunctTest(TBL IN CHAR, expand IN

  • No led backlight

    Hi I have a Compaq presario CQ57 wiith a screen so dark it cannot be seen without a bright light shone at it. its model no: CQ57-426SA I have it plugged into an external monitor and thats fine, desktop duplicated on both screens. I have updated the d

  • Attaching a new 4506-E switch to 2 N7K's using vPC?

    Hi, I need to connect a new 4506-E switch to my existing two N7K switches using port-channels and vPC. Will there be any traffic disruptions when assigning the vPC id to the port-channel? Thanks, Pradeep