User Exit for CO11N to populate the Ref Order in Prod Order when Rework Ord

HI All,
I created a Production Order(100023) using TCode CO01 with 10 Qty.
When i am creating a Production Order confirmation using TCode CO11N, i Confirmed 9 Qty and 1 Qty for Rework Order, it is confirming the 9Qty and creating a new Production Order (100024) for 1Qty.
As per the requirement it is working fine. While system creating a Production Order (100024) for the Rework Qty, i need to populate the Reference Production Order number (100023) in the field Ref. Order in Control Data tab in the Production Order.
Can any one suggest me how to populate this field? Is this possible by any USER EXIT or BADI ?
Or Can we do it by configuration?
Regards,

Hey all: I already have solved it. This was solved using a batch input application: before is launched the MIGO transaction, we print the smartorm using ME38 transaction with SHDB.

Similar Messages

  • How user exit is used to populate the Profit center field in  Sales order?

    Hi All,
    Please let me know :
    How the user exit is used to populate the Profit center field in the Sales order?
    Please gurus answer as quickly as possible as I require this urgently.

    Hi,
    To derive the correct profit center in the Sales Order, you customize in 0KEM.
    Trust this helps much and do encourage our efforts!
    Cheers!

  • User Exit for CO11N

    Hi Experts,
               I have a requirement that An equipment under Breakdown Maintenance will have a System Condition u201C0u201D.Based on this System condition, the User will not be allowed for Confirmation of PP Order in CO11N Screen. Could any one tell me is there any user exit for this.
    Thanks,
    Kumar.

    Hi,
    These are the user exits available for the CO11N screen:
    CONF0001  Enhancements in order confirmation
    CONFPI01  Process order conf.: Calculate cust.specific default va
    CONFPI02  Process order confirmation: Customer spec. input checks
    CONFPI03  Process order conf.: Cust. spec. check after op. select
    CONFPI04  Process order conf.: Customer specific input checks 2
    CONFPI05  Process order conf.: Cust. spec. enhancements when savi
    CONFPI06  Process order confirmation: Actual data transfer
    CONFPM01  PM/SM order conf.: Determine cust. specific default val
    CONFPM02  PM/SM order confirmation: Customer specific input check
    CONFPM03  PM/SM order conf.: Cust. spec. check after op. selectio
    CONFPM04  PM/SM order conf.: Customer specific input check 2
    CONFPM05  PM/SM order conf.: Cust. specific enhancements when sav
    CONFPP01  PP order conf.: Determine customer specific default val
    CONFPP02  PP order conf.: Customer specific input checks 1
    CONFPP03  PP order conf.: Cust. specific check after op. selectio
    CONFPP04  PP order conf.: Customer specific input checks 2
    CONFPP05  PP order conf.: Customer specific enhancements when sav
    CONFPP06  PP Order Confirmations: Actual Data Transfer
    CONFPP07  Single Screen Entry: Inclusion of User-Defined Subscree
    CONFPS01  PS confirmation: Determine customer specific default va
    CONFPS02  PS confirmation: Customer specific input checks 1
    CONFPS03  PS confirmation: Customer specific check after op. sele
    CONFPS04  PS confirmation: Customer specific input checks 2
    CONFPS05  PS confirmation: Customer specific enhancements when sa
    Hope it will help you.
    Regards,
    Alok Tiwari

  • User Exit for FF68 to modify the bank deposit slip

    Hi ,
    I am searching for a user exit on FF68-to modify the bank deposit slip.
    Users want to print the cheque deposit slip grouped by the bank/branch and the cheque number.
    currently it is not grouping them even they have the same cheque number
    i am a bit new to enhancements, and user exists
    I searched the cmod and vmod but could not find smthing useful
    Can you please help?
    Thank you

    hi Shailaja
    thank you very much for your help
    i checked it via smod
    It says Transfer Additional Data in Finnish TITO Format.
    do you know what steps to follow to make the change?
    i am new to this
    as far i read i need to change this exit -change the table
    but how to link this with the code?
    does the ff68 knows that exit already?

  • How to create user Exits for selecting ranges of the month

    Hi Bw Experts,
    Right now i need to create a user exits for my report which is coming from Infocube which has 12 months and 12 qtys. But if my client want to see the content of the report for e.g 1 to 3 months in selection screen means then we need to create a variable and user exit to accomplish this problem or is there any solution by which we can solve the problem. Try to suggest me and steps to achieve.
    Thanks in advance,

    Hi,
    Thanks for your input. But the questions is 12 amounts and 12 qtys not 12 months sorry for the typoerror. We are not carrying month field. But the User want to see the for e.g 1 to 3 months data means then how it is possible to accomplish this issue. Try to suggest me.
    Thanks in advance
    Message was edited by:
            mano_biw durai

  • User exit for FB60 after POSTING the Document.

    Hi,
    I have requirement with FB60 transaction where i have to display the error message to the user if the amount of the invoice is greater than some threshold value( this will be maintained in the custom table) to park the document .
    I have created project with enhancement SAPLF051 using the exit EXIT_SAPLF051_002 it is triggering only when parks the document .
    But my requirement is  i need an enhancement which trigger after user posts the document.
    Please help me...
    regards
    paveee.....

    Hi
    Following are the available user exits for fb60 transaction...
    F050S001            FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
    F050S002            FIDCC1: Change IDoc/do not send
    F050S003            FIDCC2: Change IDoc/do not send
    F050S004            FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not sen
    F050S005            FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
    F050S006            FI Outgoing IDoc: Reset Clearing in FI Document
    F050S007            FIDCCH Outbound: Influence on IDoc for Document Change
    F180A001            Balance Sheet Adjustment
    FARC0002            Additional Checks for Archiving MM Vendor Master Data
    FEDI0001            Function Exits for EDI in FI
    RFAVIS01            Customer Exit for Changing Payment Advice Segment Text
    RFEPOS00            Line item display: Checking of selection conditions
    RFKORIEX            Automatic correspondence
    SAPLF051            Workflow for FI (pre-capture, release for payment)
    If you still not find appropriate exit, go for badi's...
    1)To search for a badi, go to se 24 display class cl_exithandler.
    2) double click on method get_instance,
    3) get a break point on case statement. execute and start the required transaction in new session.
    4)look for variable exit_name. It would show the available badi's.
    <b>Please do reward if useful</b>
    Regards
    Dinesh

  • 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 Exit for CO11n transaction code

    Dear friends,
    I have a requirement that in T-Code CO11n the user enters the order confirmation and when they go for the goods movement, the screen shows the BOM list with quantities.
    My requirement is that the user will put one quantity for the main material and the rest of the quantities should be calculated through the input value and appear in the respective fields.
    For that I need an enhancement so please suggest me a userexit or any possible solution for the same.
    Thanks in advance.
    Regards,
    Mubashir

    Hi mubhasir,
    The following are the list of available user-exits in transaction code co11n, go thru the documentation of all userexit in Tcode SMOD and choose a appropriate one for ur requirement.
    Reward points, if helpful....
    Regards
    Karthik D
    <b>Transaction Code - CO11N                    Single Screen Entry of Confirmations
    Enhancement/ Business Add-in            Description
    Enhancement</b>
    CONFPP01-                                PP order conf.: Determine customer specific default values
    CONFPP02-                                PP order conf.: Customer specific input checks 1
    CONFPP03-                                PP order conf.: Cust. specific check after op. selection
    CONFPP04-                                PP order conf.: Customer specific input checks 2
    CONFPP05-                                PP order conf.: Customer specific enhancements when saving
    CONFPP06-                                PP Order Confirmations: Actual Data Transfer
    CONFPP07-                                Single Screen Entry: Inclusion of User-Defined Subscreens
    CONFPS01-                                PS confirmation: Determine customer specific default values
    CONFPS02-                                PS confirmation: Customer specific input checks 1
    CONFPS03-                                PS confirmation: Customer specific check after op. selection
    CONFPS04-                                PS confirmation: Customer specific input checks 2
    CONFPS05-                                PS confirmation: Customer specific enhancements when saving
    CONF0001-                                Enhancements in order confirmation
    CONFPI01-                                Process order conf.: Calculate cust.specific default values
    CONFPI02-                                Process order confirmation: Customer spec. input checks 1
    CONFPI03-                                Process order conf.: Cust. spec. check after op. selection
    CONFPI04-                                Process order conf.: Customer specific input checks 2
    CONFPI05-                                Process order conf.: Cust. spec. enhancements when saving
    CONFPI06-                                Process order confirmation: Actual data transfer
    CONFPM01-                                PM/SM order conf.: Determine cust. specific default values
    CONFPM02-                                PM/SM order confirmation: Customer specific input checks 1
    CONFPM03-                                PM/SM order conf.: Cust. spec. check after op. selection
    CONFPM04-                                PM/SM order conf.: Customer specific input check 2
    CONFPM05-                                PM/SM order conf.: Cust. specific enhancements when saving
    <b>No.of Exits:         24</b>

  • User exit for va01 to validate the value for schedule line category

    Hi All,
    Pls tell me which user exit i used for to validate schedule line category for tcode VA01 .suppose i have two value in scedule line category CP and CN. but when user enter CP it will show warning message that CN is default or pls enter valied value.How to do in user exit.
    Nitin K

    Hi Nitin
         Try userexit_move_field_to_vbep in MV45AFZZ
             or userexit_check_vbep in MV45ZAFZB.
           check vbep-ettyp for the schedule line category and write the logic.
    Kuntal

  • User exit for ME38 to modify the received quantity

    Dear Gurus:
    My customer demands the printings he makes from ME38, using the menu Header -> Messages, show the scheduled quantity he originally put in a new schedule line he added, in spite of he already had gone to MIGO transaction and he already had put this quantity as good receipt. Currently, due to the Good receipt operation, we try to print the new schedule lines that we put in the schedule order via ME38, but I know that EKET table assigns the scheduled quantity on the MENGE field, and when we execute a Good receipt from MIGO, the quantity received is assigned on EKET-WEMNG. If these two fields are the same, it is natural SAP doesn't print the scheduled agreement smartform, because SAP recognizes there was an order, but the material in demand has already received. How can I to avoid this behaviour to print the new schedule lines in spite of have already executed a Good receipt operation for these new lines? Is there any user exit that can help me? Is it a MM functional issue?
    Thank you in advance and best regards

    Hey all: I already have solved it. This was solved using a batch input application: before is launched the MIGO transaction, we print the smartorm using ME38 transaction with SHDB.

  • User Exit for Updating Delivery Plant at Item Level in Sales Order

    Hello Experts
    There is a requirement to determine the delivery plant for each item level and than update the items with newly determined plant.  There is a user exit MV45AFZZ routine FORM USEREXIT_MOVE_FIELD_TO_VBAP. to update the item level entries in Sales Order in VA01 or VA02. Is this the right place to do this?, if yes , do i need to perform any other standard logic (like re determine Shipping points , schedule lines ) for newly determined plant? If not , can you please suggest any other place , BADI or user exit to change the delivery plant of sales order.
    Thanks a lot....
    -Harkamal

    Best place is MV45AFZZ-USEREXIT_SAVE_DOCUMENT_PREPARE. Populates the values just before saving the document. You can have your own deriving logic. Make sure that peice of code is trigger only for Sales Order create or change (VA01/VA02).
    Are you kidding???  You do realize that this is AFTER all validations against configuration, ATP, pricing, etc. have been performed??!!!  Never, ever change a critical value like plant in the SAVE user exits...

  • User Exit for ME21 PO Creation at the time of saving--Urgent

    Hi,
    Can some one help me out in finding the user exit for PO creation at the time of saving.
    The Requirement is:
    I need to create a custom field in EKKO table.
    After appending the structure with the field to the EKKO table, i need to create a PO.
    Now i need to update the field which has been created at the time of pressing the SAVE button.
    I need to update the EKKO table it self.
    I could find the user exits but none of them have the EKKO table either in Changing or in Tables.
    Thanks,

    Hi,
              You may want to check this user exits.
    EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
    EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
    Here is the list of available user exits for ME21.
    EXIT_SAPMM06E_001 - Other Number Range or Own Document Number
    EXIT_SAPMM06E_004 - User Exit for Cust.-Specific Control of Import Data Screens in Purchasing
    EXIT_SAPMM06E_005 - Field Selection Control: Vendor Address Screen
    EXIT_SAPMM06E_006 - Export Data to Customer Subscreen for Purchasing Document Header (PBO)
    EXIT_SAPMM06E_007 - Export Data to Customer Subscreen for Purchasing Document Header (PAI)
    EXIT_SAPMM06E_008 - Import Data from Customer Subscreen for Purchasing Document Header
    EXIT_SAPMM06E_009 - Reset Customer Data at Beginning of New Document (Without Dialog)
    EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
    EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
    EXIT_SAPMM06E_014 - Read Customer-Specific Data when Importing Purchasing Document
    EXIT_SAPMM06E_016 - Export Data to Customer Subscreen for Purchasing Document Item (PBO)
    EXIT_SAPMM06E_017 - Export Data to Customer Subscreen for Purchasing Document Item (PAI)
    EXIT_SAPMM06E_018 - Import Data from Customer Subscreen for Purchasing Document Item
    EXIT_SAPMM06E_020 - User Exit: Change Document for Requisitions (Conversion into PO)
    EXIT_SAPMM06E_021 - Fulfillment of Target Value: Release Orders Against a Contract
    <b>Reward points</b>
    Regards

  • What are the User Exits for Sales Order creation process?

    Hi,
    what are the User Exits for Sales Order creation process? how can I find them?
    thanks in advance,
    will reward,
    Mindaugas

    Please check this info:
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    Regards
    Eswar

  • Extended Idoc - User exit for delivery VL01 and Invoice VF01

    Hi Experts,
    We are developing Extended Idoc for order - cash cycle.The extended Idoc contains 4 extra fields.
    I want to know the User exits where i can populate the extended segment field values for VL01 and VF01 transactions.

    HI
    exits available for  VL01.
    VMDE0004                                Shipping Interface: Message SDPACK (Packing, Inbound)
    VMDE0003                                Shipping Interface: Message SDPICK (Picking, Inbound)
    VMDE0002                                Shipping Interface: Message PICKSD (Picking, Outbound)
    VMDE0001                                Shipping Interface: Error Handling - Inbound IDoc
    V53W0001                                User exits for creating picking waves
    V53C0002                                W&S: RWE enhancement - shipping material type/time slot
    V53C0001                                Rough workload calculation in time per item
    V50S0001                                User Exits for Delivery Processing
    V50R0004                                Calculation of Stock for POs for Shipping Due Date List
    V50R0002                                Collective processing for delivery creation
    V50R0001                                Collective processing for delivery creation
    V50Q0001                                Delivery Monitor: User Exits for Filling Display Fields
    V50PSTAT                                Delivery: Item Status Calculation
    V02V0004                                User Exit for Staging Area Determination (Item)
    V02V0003                                User exit for gate + matl staging area determination (headr)
    V02V0002                                User exit for storage location determination
    V02V0001                                Sales area determination for stock transport order
    For VF01..
    Enhancement
    V61A0001                                Customer enhancement: Pricing
    V60P0001                                Data provision for additional fields for display in lists
    V60A0001                                Customer functions in the billing document
    V05N0001                                User Exits for Printing Billing Docs. using POR Procedure
    V05I0001                                User exits for billing index
    SDVFX011                                Userexit for the komkcv- and kompcv-structures
    SDVFX010                                User exit item table for the customer lines
    SDVFX009                                Billing doc. processing KIDONO (payment reference number)
    SDVFX008                                User exit: Processing of transfer structures SD-FI
    SDVFX007                                User exit: Billing plan during transfer to Accounting
    SDVFX006                                User exit tax line in transfer to accounting
    SDVFX005                                User exit reserves in transfer to accounting
    SDVFX004                                User exit G/L line in transfer to accounting
    SDVFX003                                User exit cash clearing in transfer to accounting
    SDVFX002                                User exit for A/R line in transfer to accounting
    SDVFX001                                User exit header line in delivery to accounting
    J_3RSINV

  • User exits for VA01

    Hi Experts,
    For transaction VA01, is it possible to know list of  user-exits available.
    Thank you

    Hi Peter,
    You can have the User Exits for sales order processing not for the VA01 transaction.
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    I hope it will help you,
    Regards,
    Murali.

Maybe you are looking for

  • Low res images when placed in indesign

    I'm having a problem with my graphics. I create the graphics in photoshop and save them as TIF and PSD (300 dpi) files and they look great, but when I place them in indesign the quality looks very bad (low res). What am I doing wrong ? Thanks

  • Custom attributes on adf components?

    I asked this question before: howto modify components in tree? and got no answer. So I'm trying a different approach. I'm using aop to intercept methods as such: <include within="oracle.adfinternal.view.faces.renderkit.rich..*"/> @Pointcut("execution

  • Command line to sort semi-colon delimited string

    I'm sure there's a simple solution eluding me... I have an app which stores sets as a string like: "bee;ant;cow;ant;Aardvark;dog" which I want to sort to a string like: "Ardvark;ant;bee;cow;dog" ...where letter sort** is case insensitive and number s

  • Toggling Location Services for apps to "While Using" not possible in iOS 8

    So I've read one of the features in iOS 8 is being able to toggle the location services features of apps as follows: Never Always While Using I thought this would be useful because it could potentially help saving battery, however, I've only got the

  • MUSIC VIDEOS HAVE VANISHED!

    Just upgraded to v7. Really like it, but the music videos I bought have gone. You'll also notice there is no option on the left to select 'videos'. I checked preferences, and it won't let you include videos either! Apple, give us the videos back or l