Outgoing interface modification

Hello,
Im trying to find out as I am somehow lost in the middle now about how to change the interface used for the outgoing connection/packet .
3 options :
 1. change in the FWPM_LAYER_IPFORWARD_V4
changing the interface index in the FwpsInjectForwardAsync0 IF_INDEX
interfaceIndex to represent the outgoing interface number
2.
change the Destination Mac Address or the interfaceindex(as its how forwarding works, usually) to the required interface mac address.
using FWPM_LAYER_OUTBOUND_MAC_FRAME_ETHERNET with FwpsInjectMacSendAsync0 changing the IF_INDEX interfaceIndex3. Using FWPM_LAYER_ALE_BIND_REDIRECT_V4 changing FWPS_BIND_REQUEST0 changing localAddressAndPort to represent the ip address of the interface needed to be used as an outgoing interfaceAny help would be totally helpfulThank you very much .

any suggetions please....??

Similar Messages

  • Itunes COM SDK: cannot register function with iTunes Outgoing Interface

    I am doing benchmarks and I want to time the encoding of a Music CD. In order to stop the "clock" and compute the time I am trying to bind a function with the _IITConvertOperationStatusEvents::OnConvertOperationCompleteEvent()
    I am writing a AutoIt script and I can create the iTunes application object but when I use the ObjEvent function to register my function with the event above it causes a COM exception to be raised and the ObjEvent completes with an error. The exception code I get is 80040200 which seems to be a generic error.
    $objApp=ObjCreate("iTunes.Application")
    $SinkObject=ObjEvent($objApp, "ITEvent", "_IITConvertOperationStatusEvents")
    <<exception 80040200>>
    Browsing the iTunes COM TypeLib the _IITConvertOperationStatus does not seem to be a child in the iTunes object hierarchy so I think this is way the exception is being raised. I have tried to register another function with another outgoing interface and this works just perfectly: _IiTunesEvents::OnQuitting()
    Do I need to create another object which gets passed as the first parameter to the ObjEvent function?
    *Here is the entire script:*
    $ITSourceKindAudioCD = 3
    $begin = 0
    Global $trackName, $progressValue, $maxProgressValue, $SinkObject
    $oMyError = ObjEvent("AutoIt.Error","MyErrFunc") ; Install a custom error handler
    $objApp = ObjCreate("iTunes.Application")
    If @error Then
    MsgBox(0, "ObjCreate", "Create Object Failed", 3)
    Exit
    EndIf
    $event = ObjEvent($objApp, "ITEvent1_", "_IiTunesEvents")
    If @error Then
    MsgBox(0, "Failed", "IiTunesEvent binding failed", 5)
    Exit
    EndIf
    $SinkObject = ObjEvent($objApp, "ITEvent_", "_IITConvertOperationStatusEvents") ; Assign events to UDFs starting with IEEvent_
    If @error Then
    MsgBox(0, "ObjEvent binding", "ObjEvent failed!", 10)
    $objApp.Quit()
    Exit
    EndIf
    $colSources = $objApp.Sources
    $begin = TimerInit()
    For $objSource in $colSources
    If $objSource.Kind = $ITSourceKindAudioCD Then
    $strName = $objSource.Name
    $colPlaylists = $objSource.Playlists
    $objPlaylist = $colPlaylists.ItemByName($strName)
    $colTracks = $objPlaylist.Tracks
    $objApp.ConvertTracks2($colTracks)
    EndIf
    Next
    Do
    ; Wait around for the ripping to complete
    Until False
    ; This is my custom error handler
    Func MyErrFunc()
    $HexNumber = hex($oMyError.number,8)
    Msgbox(0,"","We intercepted a COM Error !" & @CRLF & _
    "Number is: " & $HexNumber & @CRLF & _
    "Windescription is: " & $oMyError.windescription )
    EndFunc
    Func ITEvent1_OnQuittingEvent()
    MsgBox(0, "Bye", "Bye-Bye", 10)
    EndFunc
    func ITEvent_OnConvertOperationCompleteEvent()
    $dif = TimerDiff($begin)
    MsgBox(0,"Time Difference",$dif)
    $objApp.Quit()
    EndFunc

    much of this is speculation because I can't remember how many previous versions of iTunes were on these machines...but this is what we're seeing:
    extra entries in two registry keys... when it didn't work these two registry entries contained "AppID" values:
    HKEYCLASSESROOT\CLSID\{B9E1D2CB-CCFF-4AA6-9579-D7A4754030EF}\Implemented
    Categories
    HKEYLOCALMACHINE\SOFTWARE\Classes\CLSID\{B9E1D2CB-CCFF-4AA6-9579-D7A4754030EF}
    with the APpID set to the same iTunes CLSID string:
    {B9E1D2CB-CCFF-4AA6-9579-D7A4754030EF}
    and when it did work the AppIDs entries were gone. this is only on XP.
    on vista there never was any AppID entry.
    but, again, i wonder if that was added by previous versions of iTunes which we didn't install on the vista machines...
    Also, worthy of noting is this post from Apple:
    http://support.apple.com/kb/HT1925
    ciao, raza

  • Outgoing interface with bank

    Hi all,
    my client wants to establish outgoing bank interface between our company and bank. we have sap 4.6c.
    what are the configuration for this and what is the necessary for this?
    if anybody give the bank interface configuration?
    Thanks in advance. points will be awarded accordingly.
    Raghav.

    any suggetions please....??

  • Choosing the outgoing interface

    Hello all.
    I have a (two) C160 mail security appliance with the following network configuration .
    1 phisical interface
    2 IP interfaces, let's say 192.168.1.100 and 192.168.1.101
    2 Listeners. "Public" (192.168.1.100) and "private" (192.168.1.101).
    Mails flow is working great, but we are having a problem with the outgoing email traffic.
    Our email server sends outgoing traffic to the ironport appliances (DMZ) on the private listener.
    The ironport relay emails from that address.
    Isn't possible to have the ironport to take the messages from the "private" listener and then send them out from the "public" listener?
    Many thanks for you precious help.
    Giovanni

    Hello Giovanni,
    listeners are for receiving only, so I suppose you mean the messages coming from private listeners should be delivered via the interface with IP 192.168.1.100. You can do that with an outbound content filter,  simply create such a filter without any condition, and a single action "Deliver from IP Interface", where you specify the interface 192.168.1.100. Submit, and add them to all you outgoing mail policies, then commit.  In case you want to do that with message filters (if familiar with them), then you'd also need a condition checking for the listeners, as message filters don't differ between inbound and outbound (relayed) messages.
    Hope that helps,
    Andreas

  • How to configure multiple outgoing interfaces + NAT + PfR

    Hello,
    I have the following config running on Cisco2851.
    Five interfaces (four ADSL and one LAN 10Mb/s) connected to Internet using pppoe.
    Local policy is used to make working route tracking.
    The PfR also configured to load balance traffic coming from LAN to Internet.
    PAT is also configured with "oer" keyword at the end of string to not relocate working translations.
    But the router is not performing good. :-(
    After investigation I found that the selection of the exit interface and setting source ip for
    NAT is not synchronized. The provider's router just drops the incoming packet due to uRPF check.
    Also, the selection of the exit interface is not PFR aware (mode select-exit best) during
    NAT session setup, and router selects one of the possible exit interfaces randomly.
    I have two questions:
    1. How to make synchronization of NAT and Routing to build matching pair of Out_IP=Out_Interface and make my setup working?
    2. How to select the less loaded interface during setup of NAT phase and Routing phase and really involve PfR?
    Actually, these two questions is just my one requirement: during setup of NAT session, I need
    to find less loaded interface (PfR should check current rx/tx load), select it, and keep it untouched.
    Thanks,
    Sergey
    Config:
    version 15.1
    service tcp-keepalives-in
    service tcp-keepalives-out
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    hostname bif
    boot-start-marker
    boot system flash:c2800nm-adventerprisek9-mz.151-4.M8.bin
    boot-end-marker
    enable secret 5 $1$3ggj$huERPVt0luOX6qo6
    no aaa new-model
    crypto pki token default removal timeout 0
    dot11 syslog
    no ip source-route
    ip cef
    no ip domain lookup
    ip domain name zzz.mgm
    no ipv6 cef
    multilink bundle-name authenticated
    key chain PFR
     key 0
      key-string 7 107E2F2B
    voice-card 0
    pfr master
     logging
     border 192.168.254.254 key-chain PFR
      interface Dialer5 external
      interface Dialer4 external
      interface Dialer3 external
      interface Dialer2 external
      interface Dialer1 external
      interface GigabitEthernet0/0 internal
     mode select-exit best
    pfr border
     logging
     local Loopback0
     master 192.168.254.254 key-chain PFR
    license udi pid CISCO2851 sn FCZ0929
    username se privilege 15 secret 5 $1$DUbm$RuZKP8X.19uBtm21
    username ru privilege 15 secret 5 $1$1V.h$iotp/bjhUg4ho93d
    redundancy
    ip ssh version 2
    track 1 ip sla 1 reachability
     delay down 30 up 15
    track 2 ip sla 2 reachability
     delay down 30 up 15
    track 3 ip sla 3 reachability
     delay down 30 up 15
    track 4 ip sla 4 reachability
     delay down 30 up 15
    track 5 ip sla 5 reachability
     delay down 30 up 15
    interface Loopback0
     ip address 192.168.254.254 255.255.255.255
    interface GigabitEthernet0/0
     description ### LAN ###
     ip address 192.168.68.1 255.255.255.0
     no ip redirects
     no ip proxy-arp
     ip flow ingress
     ip nat inside
     ip virtual-reassembly in
     duplex auto
     speed auto
    interface GigabitEthernet0/1
     description ### WDSL link to Dialer 5 ###
     no ip address
     duplex auto
     speed auto
     pppoe enable group global
     pppoe-client dial-pool-number 5
    interface ATM0/0/0
     description ### DSL link 1 to Dialer 1 ###
     no ip address
     no atm ilmi-keepalive
     shutdown
     pvc 1/32
      pppoe-client dial-pool-number 1
    interface ATM0/1/0
     description ### DSL link 2 to Dialer 2 ###
     no ip address
     no atm ilmi-keepalive
     pvc 1/32
      pppoe-client dial-pool-number 2
    interface ATM0/2/0
     description ### DSL link 3 to Dialer 3 ###
     no ip address
     no atm ilmi-keepalive
     pvc 1/32
      pppoe-client dial-pool-number 3
    interface ATM0/3/0
     description ### DSL link 4 to Dialer 4 ###
     no ip address
     no atm ilmi-keepalive
     pvc 1/32
      pppoe-client dial-pool-number 4
    interface GigabitEthernet1/0
     description ### Virtual interface to NME-16ES-1G-P ###
     ip address 192.168.254.253 255.255.255.254
    interface Dialer1
     description ### Dialer for line 1 ###
     bandwidth 224
     bandwidth receive 1728
     ip address negotiated
     ip mtu 1492
     ip nat outside
     ip virtual-reassembly in
     encapsulation ppp
     ip tcp adjust-mss 1452
     load-interval 30
     dialer pool 1
     ppp authentication chap callin
     ppp chap hostname
     ppp chap password
     no cdp enable
    interface Dialer2
     description ### Dialer for line 2 ###
     bandwidth 224
     bandwidth receive 1728
     ip address negotiated
     ip mtu 1492
     ip flow ingress
     ip nat outside
     ip virtual-reassembly in
     encapsulation ppp
     ip tcp adjust-mss 1452
     dialer pool 2
     ppp authentication chap callin
     ppp chap hostname
     ppp chap password
     no cdp enable
    interface Dialer3
     description ### Dialer for line 3 ###
     bandwidth 224
     bandwidth receive 1728
     ip address negotiated
     ip mtu 1492
     ip flow ingress
     ip nat outside
     ip virtual-reassembly in
     encapsulation ppp
     ip tcp adjust-mss 1452
     dialer pool 3
     ppp authentication chap callin
     ppp chap hostname
     ppp chap password
     no cdp enable
    interface Dialer4
     description ### Dialer for line 4 ###
     bandwidth 224
     bandwidth receive 1728
     ip address negotiated
     ip mtu 1492
     ip flow ingress
     ip nat outside
     ip virtual-reassembly in
     encapsulation ppp
     ip tcp adjust-mss 1452
     dialer pool 4
     ppp authentication chap callin
     ppp chap hostname
     ppp chap password
     no cdp enable
    interface Dialer5
     description ### Dialer for WDSL line ###
     bandwidth 10000
     bandwidth receive 10001
     ip address negotiated
     ip mtu 1492
     ip flow ingress
     ip nat outside
     ip virtual-reassembly in
     encapsulation ppp
     ip tcp adjust-mss 1452
     load-interval 30
     dialer pool 5
     ppp authentication chap callin
     ppp chap hostname
     ppp chap password
     no cdp enable
    ip local policy route-map LOCAL-PBR
    no ip forward-protocol nd
    no ip http server
    no ip http secure-server
    ip nat inside source route-map NAT1 interface Dialer1 overload oer
    ip nat inside source route-map NAT2 interface Dialer2 overload oer
    ip nat inside source route-map NAT3 interface Dialer3 overload oer
    ip nat inside source route-map NAT4 interface Dialer4 overload oer
    ip nat inside source route-map NAT5 interface Dialer5 overload oer
    ip nat inside source static tcp 192.168.68.160 22 $$$Dialer5-IP$$$ 2222 extendable
    ip nat inside source static tcp 192.168.68.160 22 $$$Dialer2-IP$$$ 2222 extendable
    ip nat inside source static tcp 192.168.68.160 22 $$$Dialer3-IP$$$ 2222 extendable
    ip nat inside source static tcp 192.168.68.160 22 $$$Dialer4-IP$$$ 2222 extendable
    ip nat inside source static tcp 192.168.68.230 21 $$$Dialer1-IP$$$ 21 extendable
    ip nat inside source static tcp 192.168.68.160 25 $$$Dialer1-IP$$$ 25 extendable
    ip nat inside source static tcp 192.168.68.22 143 $$$Dialer1-IP$$$ 143 extendable
    ip nat inside source static tcp 192.168.68.22 443 $$$Dialer1-IP$$$ 443 extendable
    ip nat inside source static tcp 192.168.68.160 22 $$$Dialer1-IP$$$ 2222 extendable
    ip route 0.0.0.0 0.0.0.0 Dialer1 track 1
    ip route 0.0.0.0 0.0.0.0 Dialer2 track 2
    ip route 0.0.0.0 0.0.0.0 Dialer3 track 3
    ip route 0.0.0.0 0.0.0.0 Dialer4 track 4
    ip route 0.0.0.0 0.0.0.0 Dialer5 track 5
    ip sla 1
     icmp-echo 8.8.8.8 source-ip $$$Dialer1-IP$$$
     timeout 1000
     frequency 5
    ip sla schedule 1 life forever start-time now
    ip sla 2
     icmp-echo 8.8.8.8 source-ip $$$Dialer2-IP$$$
     timeout 1000
     frequency 5
    ip sla schedule 2 life forever start-time now
    ip sla 3
     icmp-echo 8.8.8.8 source-ip $$$Dialer3-IP$$$
     timeout 1000
     frequency 5
    ip sla schedule 3 life forever start-time now
    ip sla 4
     icmp-echo 8.8.8.8 source-ip $$$Dialer4-IP$$$
     timeout 1000
     frequency 5
    ip sla schedule 4 life forever start-time now
    ip sla 5
     icmp-echo 8.8.8.8 source-ip $$$Dialer5-IP$$$
     timeout 1000
     frequency 5
    ip sla schedule 5 life forever start-time now
    access-list 100 permit ip any any
    access-list 101 permit ip host $$$Dialer1-IP$$$ any
    access-list 102 permit ip host $$$Dialer2-IP$$$ any
    access-list 103 permit ip host $$$Dialer3-IP$$$ any
    access-list 104 permit ip host $$$Dialer4-IP$$$ any
    access-list 105 permit ip host $$$Dialer5-IP$$$ any
    access-list 199 permit ip 192.168.68.0 0.0.0.255 any
    route-map LOCAL-PBR permit 10
     match ip address 101
     set interface Dialer1
    route-map LOCAL-PBR permit 20
     match ip address 102
     set interface Dialer2
    route-map LOCAL-PBR permit 30
     match ip address 103
     set interface Dialer3
    route-map LOCAL-PBR permit 40
     match ip address 104
     set interface Dialer4
    route-map LOCAL-PBR permit 50
     match ip address 105
     set interface Dialer5
    route-map LOCAL-PBR permit 100
     match ip address 100
     set global
    route-map NAT3 permit 10
     match ip address 199
     match interface Dialer3
    route-map NAT2 permit 10
     match ip address 199
     match interface Dialer2
    route-map NAT1 permit 10
     match ip address 199
     match interface Dialer1
    route-map NAT5 permit 10
     match ip address 199
     match interface Dialer5
    route-map NAT4 permit 10
     match ip address 199
     match interface Dialer4
    control-plane
    mgcp profile default
    line con 0
    line aux 0
    line 66
     no activation-character
     no exec
     transport preferred none
     transport input all
     transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
    line vty 0 4
     session-timeout 15
     login local
     transport input all
    line vty 5 15
     session-timeout 15
     login local
     transport input all
    scheduler allocate 20000 1000
    end
    Show ip route:
    sh ip route 0.0.0.0
    Routing entry for 0.0.0.0/0, supernet
      Known via "static", distance 1, metric 0 (connected), candidate default path
      Routing Descriptor Blocks:
        directly connected, via Dialer5
          Route metric is 0, traffic share count is 1
      * directly connected, via Dialer3
          Route metric is 0, traffic share count is 1
        directly connected, via Dialer4
          Route metric is 0, traffic share count is 1
        directly connected, via Dialer2
          Route metric is 0, traffic share count is 1
    Log:
    *Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, Stateful Inspection(5), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, Ingress-NetFlow(21), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, Virtual Fragment Reassembly(25), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, Access List(31), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, Virtual Fragment Reassembly After IPSec Decryption(39), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, TCP Adjust MSS(82), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.103: FIBipv4-packet-proc: route packet from GigabitEthernet0/0 src 192.168.68.2 dst 8.8.4.4
    *Apr 16 07:04:18.103: FIBfwd-proc: Default:0.0.0.0/0 process level forwarding
    *Apr 16 07:04:18.103: FIBfwd-proc: depth 0 first_idx 3 paths 4 long 0(0)
    *Apr 16 07:04:18.103: FIBfwd-proc: try path 3 (of 4) v4-ap-Dialer5 first short ext 0(-1)
    *Apr 16 07:04:18.103: FIBfwd-proc: v4-ap-Dialer5 valid
    *Apr 16 07:04:18.103: FIBfwd-proc: Dialer5 no nh type 3  - deag
    *Apr 16 07:04:18.103: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Dialer5 nh none deag 1 chg_if 0 via fib 0 path type attached prefix
    *Apr 16 07:04:18.103: FIBfwd-proc: packet routed to Dialer5 p2p(0)
    *Apr 16 07:04:18.103: FIBipv4-packet-proc: packet routing succeeded
    *Apr 16 07:04:18.103: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Dialer5 nh none uhp 1 deag 0 ttlexp 0
    *Apr 16 07:04:18.103: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Dialer5 nh none uhp 1 deag 0 chgif 0 ttlexp 0 rec 0
    *Apr 16 07:04:18.103: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, Post-routing NAT Outside(24), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.103: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, Stateful Inspection(27), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.103: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
    *Apr 16 07:04:18.103:     UDP src=61183, dst=53, CCE Post NAT Classification(38), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
    *Apr 16 07:04:18.107:     UDP src=61183, dst=53, Firewall (firewall component)(39), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
    *Apr 16 07:04:18.107:     UDP src=61183, dst=53, TCP Adjust MSS(50), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
    *Apr 16 07:04:18.107:     UDP src=61183, dst=53, NAT ALG proxy(55), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
    *Apr 16 07:04:18.107:     UDP src=61183, dst=53, Post-Ingress-NetFlow(68), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
    *Apr 16 07:04:18.107:     UDP src=61183, dst=53, Dialer idle reset(84), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
    *Apr 16 07:04:18.107:     UDP src=61183, dst=53, Dialer idle reset(85), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), g=8.8.4.4, len 66, forward
    *Apr 16 07:04:18.107:     UDP src=61183, dst=53
    *Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Virtual-Access3), len 66, sending full packet
    *Apr 16 07:04:18.107:     UDP src=61183, dst=53

    hi,is this question is ok?
    if you forget do this config like below:
    pfr master
    learn
    delay
    throughput
    periodic-interval 3
    monitor-period 1
    pfr master
    delay threshold 200
    jitter threshold 50 
    mode route control 
    mode monitor passive
    mode select-exit best 
    i will do like this,four ADSL connect a switch ,this switch connect a router 2911(with data license)
    at 2911 do four  pppoe
    i want to load balance at this four adsl.

  • Output errors on an interface of etherchannel

    Hi all,
    I have 2 interfaces  which are a part of  an etherchannel link from  Core switch 2 to back up servers These 2 interfaces are displaying output errors
    This core switch 2 has an connection to a 3550 to which a linux server is attached
    Backup is been performed from linux server to the backup servers everyday and we see a network performance issue as backup take way too long.
    Lnx server is attached to 3550 at 100/ full connection on port fa0/17 and there is no duplex mismatch issues, port fa0/17 has underrun errors (see attachment)
    Core switch 2 has port gi5/15 and gi5/16 in the etherchannel and are on 1000/full connection (see attachment)
    Can anybody provide me a solution for this problem
    Thanks

    Hi all,
    I
    have 2 interfaces  which are a part of  an etherchannel link from  Core
    switch 2 to back up servers These 2 interfaces are displaying output errors
    This core switch 2 has an connection to a 3550 to which a linux server is attached
    Backup is been performed from linux server to the backup servers everyday and we see a network performance issue as backup take way too long.
    Lnx server is attached to 3550 at 100/ full connection on port fa0/17 and there is no duplex mismatch issues, port fa0/17 has underrun errors (see attachment)
    Core switch 2 has port gi5/15 and gi5/16 in the etherchannel and are on 1000/full connection (see attachment)
    Can anybody provide me a solution for this problem
    Thanks
            Attachments:
    Core 2.txt.zip (1.0 K)
    3550.txt.zip (869 bytes)
    Hi,
    Following are the observation of interface logs of 3550:-
    There have been 8414 'output buffer failures' reported.  If outgoing interface buffers are not available, an output buffer failure is reported.If an interface buffer is available but the Transmit Queue Limit is reached,  the packet is dropped. However, if 'transmit-buffers backing-store' is enabled,  the packet is placed in a System Buffer (which has to be obtained from an appropriate  Free-List), and enqueued in the Output Hold queue for future transmission at  the Process level, and an Output Buffer Swap is reported.
    and  8414 'underruns' have been reported, which amounts to 0.00514% of the  total input traffic. This is because, the far-end transmitter runs faster than
    the receiver of the near-end router can handle.
    Check out this:- Monitor the level of underruns over time. If they continue increasing,  consider buffer and queue tuning or upgrading hardware.
    Check out the below link for buffer tuning
    http://www.cisco.com/en/US/customer/products/hw/routers/ps133/products_tech_note09186a00800a7b80.shtml
    Hope to help !!
    Ganesh.H
    Cisco are currently donating money to the Haiti earthquake appeal for every rating so please consider rating all helpful posts.

  • EEM TCL for interface commands

    I am working on a script that will make interface changes.  I am trying to do the following:
    1) save the output from the following command:  #show cdp nei detail | i Interface
    2) this will most likely give a list of interfaces some of which will be repeated.  If the interface is listed more than once then i would like to remove the
        repeated interface.  (note i am not concerned about the outgoing interface)
    3)using the above information i would then like to make configuration to the interfaces with the following commands
         #config t
         #interface $intf
         #no mls qos vlan-based
         #mls qos trust dscp
    i have started this script (please see attached file) and would really appreciate some assistance especially with how to eliminate multiple instances of the same interface.
    thanks!!

    I am having issues running scripts on my 3750x.  One of the few commands i am getting to work is the
    router(tcl)#puts "testing this command"
    most all other commands are not working for example:  ios_config, set
    I am attaching a file with more details.  Any help would be greatly appreciated!

  • Why Bandwidth is not reserved for incoming interfaces?

    Hi,
    When i put show mpls traffic-eng topology command i see reservation only on outgoing interfaces of the router. Why? Why not the incoming interfaces?
          link[0]: Broadcast, DR: 3.3.3.53, nbr_node_id:12, gen:40
              frag_id 1, Intf Address:3.3.3.35
              TE metric:1, IGP metric:1, attribute flags:0x0
              SRLGs: None
              physical_bw: 100000 (kbps), max_reservable_bw_global: 75000 (kbps)
              max_reservable_bw_sub: 0 (kbps)
                                     Global Pool       Sub Pool
                   Total Allocated   Reservable        Reservable
                   BW (kbps)         BW (kbps)         BW (kbps)
            bw[0]:            0            75000                0
            bw[1]:            0            75000                0
            bw[2]:            0            75000                0
            bw[3]:            0            75000                0
            bw[4]:            0            75000                0
            bw[5]:            0            75000                0
            bw[6]:            0            75000                0
            bw[7]:            0            75000                0
          link[1]: Broadcast, DR: 2.2.2.32, nbr_node_id:3, gen:40
              frag_id 2, Intf Address:2.2.2.32
              TE metric:1, IGP metric:1, attribute flags:0x0
              SRLGs: None
              physical_bw: 100000 (kbps), max_reservable_bw_global: 75000 (kbps)
              max_reservable_bw_sub: 0 (kbps)
                                     Global Pool       Sub Pool
                   Total Allocated   Reservable        Reservable
                   BW (kbps)         BW (kbps)         BW (kbps)
            bw[0]:            0            75000                0
            bw[1]:            0            75000                0
            bw[2]:            0            75000                0
            bw[3]:            0            75000                0
            bw[4]:            0            75000                0
            bw[5]:            0            75000                0
            bw[6]:            0            75000                0
            bw[7]:        70000             5000                0
    Link 1 reservation is there but on link 0 NO RESERVATION. Why? Since link 0 is incoming interface and Link 1 is outgoing interface.of the tunnel.

    Hi Ankur,
    That is because MPLS TE Tunnels are unidirectional.
    So they are setup only in one direction from source to destination.
    Consequently the resources reserved for a particular tunnel are reserved in one direction only.
    So you might want to setup a tunnel in the opposite direction as well.
    adam

  • MTU for out going interface.

    Hi Expert,
    I have ASR9010 with single incoming interface(GE) and two outgoing interfaces(TenG1 and Bundle-E(TenG2)). the routing/cef/label is configured to forwarding traffic out TenG1. All interfaces are configured with MTU 9194.
    - When I inject traffic with 1500byte size, traffic has been forwarded out TenG1 as intended.
    - Same traffic but change the size to 9000byte, traffic has been forwared out Bundle-E and it can not reach the destination.... routing /CEF still say that it should be forwared out TenG1.
    Any possibility that I have done something wrong?
    Regard,
    Marit.

    Thank guys,
    After Spirent has been took out then I generated traffic by using ping with jumbo frame packet from CPE it suddenly reached the destination. So, there might be something wrong with Spirent configuration but I still wonder even wrongly configured spirent could effect routing decision on router ??
    Xander,
    I can confirm that the load balance had been took out and CEF clearly shown that the outgoing was TenG interface.
    "if the egress interface had a smaller mtu then the packet size, meaning that the egress Lc would punt for fragmentation, it could be the sw injected the packets down into other paths then what you'd expect." <-- This is what I worry, could it possible to happen that way?

  • Virtual Interface

    Hi All,
    1) Is it possible can i able to create virtaul interface for Outlgoing mails in the Ironport c350 box. ?
    2) Or - Can I assign a Pool of Ip Address for outgoing interface and the Ironport c350 box will pick any ip address and send the mail?
    Anyone help me for above doubts?
    Thanks in Advance,
    Ram.N

    A. To create new virtual gateway's,
    We would recommend that you go to the support portal and download the PDF version of the AsyncOS Advanced User Guide. (http://www.ironport.com/support/login.html )
    Once you have the PDF of the Advanced User Guide, search for this
    "USING VIRTUAL GATEWAY TECHNOLOGY"
    This section will get into details on how Virtual Gateways work on the Ironport appliance.
    How many virtual gateways can be configured on each appliance?
    -- AsyncOS 5.1.x and up
    C10/1x0 4 Virtual Gateways
    C30/3x0 32 Virtual Gateways
    C3x0D 256 Virtual Gateways
    C60/6x0 32 Virtual Gateways
    X10x0 32 Virtual Gateways
    B. To assign the virtual gateway IP's to a group and have delivery go to this group, follow these steps.
    Warning: Can only be done from the command line of the appliance
    1. After you've created your virtual gateway IPs, type "interfaceconfig"
    2. then type, "groups" and add the IP's that you want to this group.
    3. Press enter a few times to return to the main prompt and type "commit"
    4. Then, type "deliveryconfig" and it will allow you to choose which interface to use. Select the new gorup that you created in the steps above.
    5. "commit" changes.
    If there are multiple IP's in the group that you create, it will round-robin through the IP addresses.
    Hi All,
    1) Is it possible can i able to create virtaul interface for Outlgoing mails in the Ironport c350 box. ?
    2) Or - Can I assign a Pool of Ip Address for outgoing interface and the Ironport c350 box will pick any ip address and send the mail?
    Anyone help me for above doubts?
    Thanks in Advance,
    Ram.N

  • Netflow and interface

    there are interfaces in netflow output,   source interface and destination interface.   but how netflow know incoming and outgoing interface.
      i see some traffic has same interface for source interfce and destination interface,

    AFAIK:
    1. "ip route-cache flow" is deprecated starting in 12.2(18)SXD. See this URL for other IOS trains: http://www.cisco.com/en/US/docs/ios/netflow/command/reference/nf_01.html#wp1049320
    2. It's generally correct, due to the unidirectional nature of NetFlow records. Otherwise, you run the risks such as only seeing one direction of a given "conversation".
    3. My understanding was NetFlow cache could only be enabled on layer-3 interfaces. However, on the catalyst 6000s (and sup720?), you can get layer-2 bridged traffic between hosts in the same VLAN, using the following config:
    ip flow ingress layer2-switched vlan
    ip flow export layer2-switched vlan
    Then, there's this recent thread that makes it sound promising that layer-2 ports could become NetFlow-enabled, though it's not clear (to me) how it works out in practice:
    https://supportforums.cisco.com/message/678612#678612
    So YMMV. The best bet is to actually attempt configuring it. Odds are the physical interfaces won't accept the "ip route-cache flow" or "ip flow ingress/egress" config.

  • DMVPN in Cisco 3945 output drop in tunnel interface

    I configured DMVPN in Cisco 3945 and checked the tunnel interface. I found out that I have output drop. How can I remove that output drop? I already set the ip mtu to 1400.
    CORE-ROUTER#sh int tunnel 20
    Tunnel20 is up, line protocol is up
      Hardware is Tunnel
      Description: <Voice Tunneling to HO>
      Internet address is 172.15.X.X./X
      MTU 17878 bytes, BW 1024 Kbit/sec, DLY 50000 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation TUNNEL, loopback not set
      Keepalive not set
      Tunnel source 10.15.X.X (GigabitEthernet0/1)
       Tunnel Subblocks:
          src-track:
             Tunnel20 source tracking subblock associated with GigabitEthernet0/1
              Set of tunnels with source GigabitEthernet0/1, 1 member (includes iterators), on interface <OK>
      Tunnel protocol/transport multi-GRE/IP
        Key 0x3EA, sequencing disabled
        Checksumming of packets disabled
      Tunnel TTL 255, Fast tunneling enabled
      Tunnel transport MTU 1438 bytes
      Tunnel transmit bandwidth 8000 (kbps)
      Tunnel receive bandwidth 8000 (kbps)
      Tunnel protection via IPSec (profile "tunnel_protection_profile_2")
      Last input 00:00:01, output never, output hang never
     --More--           Last clearing of "show interface" counters never
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 7487
      Queueing strategy: fifo
      Output queue: 0/0 (size/max)
      30 second input rate 0 bits/sec, 0 packets/sec
      30 second output rate 0 bits/sec, 0 packets/sec
         48007 packets input, 4315254 bytes, 0 no buffer
         Received 0 broadcasts (0 IP multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
         42804 packets output, 4638561 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 unknown protocol drops
         0 output buffer failures, 0 output buffers swapped out
    interface Tunnel20
     description <Bayantel Voice tunneling>
     bandwidth 30720
     ip address 172.15.X.X 255.255.255.128
     no ip redirects
     ip mtu 1400
     no ip next-hop-self eigrp 20
     no ip split-horizon eigrp 20
     ip nhrp authentication 0r1x@IT
     ip nhrp map multicast dynamic
     ip nhrp network-id 1002
     ip nhrp holdtime 300
     ip tcp adjust-mss 1360
     tunnel source FastEthernet0/0/1
     tunnel mode gre multipoint
     tunnel key 1002
     tunnel protection ipsec profile tunnel_protection_profile_2 shared

    Hi,
    Thanks for the input. If the radio is sending out the packet but client did not receive, not output drop should be seen since packet is sent out, right?
    From my understanding, output drop is related to congested interface. Outgoing interface cannot take the rate packets coming in and thus droping it. What I don't understand is input and output rate has not reached limit yet. Also input queue is seeing drop of packet as well even though input queue is empty.
    Any idea?

  • 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

  • Date format Issue after HRSP Update

    Hi,
    We are faced with a strange issue after HRSP update was applied on our client system (upgraded from SAP-KE-30 to SAP-KE-36).
    There is an outgoing interface which picks up all the the starters into the local government pension scheme and updates a B2A document. This is implemented via a z-program.
    When we look at the out put after the interface has run for the  vast majority of employees it shows their date of birth as 21.05.1968 when it should show it as 21051968. This only appears to have happen after the HRSP's have been applied.
    No modifications have been made to the z-program. What could be the reason for this issue. has anyone faced such an issue post HRSP update?
    Any pointers on how to further investigate and resolve the issue will be most helpful.
    Regards

    Hello Iside,
    In this case we can try to reload the software on the BlackBerry Smartphone to make sure it is running the latest version and there are no issues with the OS on the device.
    To do this we would need to back up the BlackBerry Smartphone. Please open the BlackBerry Desktop Manager and connect your device. Click on the Backup and Restore options and select Back Up. Please note the location where the backup is being saved as we will need to access it later to restore the BlackBerry Smartphone.
    Once you have backed up your BlackBerry Smartphone please follow the link below to complete a clean reload of the BlackBerry Smartphone software.
    Link: http://www.blackberry.com/btsc/KB11320
    Please test the date once the software is reloaded prior to restoring the backup.
    Thank you
    -DrP
    Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
    Be sure to click Kudos! for those who have helped you.
    Click Solution? for posts that have solved your issue(s)!

  • 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..

Maybe you are looking for

  • How to create a connection key for an intranet

    I'm trying to create a connection key for a client of ours to update a page on their intranet. The intranet is only available internally. How do I go about doing this?

  • Podcast Download error (-50)

    I can subscribe to a free podcast but when I try to download an ! with a little grey circle around it appears to the left and gives me the following error message... There was a problem downloading "Podcast name". An unknown error occurred (-50). Ple

  • Page not found error when  navigating in Iview  application

    Hi, I have developed an application,and I am able to view a sucessfull preview of the Page as well.There are htmlb links on the page.When clicked,they navigate to the next jsp page.This iview was assigned to a user,and the portal was logged in though

  • 2 different COGS in CO-PA

    Dear CO-PA gurus. I have requirement to keep 2 different COGS in CO-PA. For example, if sold qty is 10pcs and standard cost is $10 and managerial accounting purpose cost is $12, I'd like to send both of $10x10pc=$100 and $12x10pc=$120. So, in order t

  • Oracle Workflow Vote Yes/No problems

    Hi, I am new to Oracle Workflow and trying to solve this problem: I set up a process which includes the Vote Yes/No Activity (notification). The notification should be sent to a role (a group of users) and I want all users to respond before the proce