Configure SPA8800 for inbound calls in switzerland

Good Evening,
i have a problem with this gateway, i'm able to make correctly outbound calls but if i receive an inbound call from the pstn line it doesn't answer.. I saw that the psnt status reamains on "idle".
I'm in Swizterland (Lugano). How can i manage that?
Regards

Wrong line setting may cause ring is not recognized. Unfortunatelly, I know no correct setting for your Telco operator. Wait for someone's reply here or ask your operator for PSTN line specification. Also, seller of SPA8800 should support you. The European Telecomunication Standard ETS 300 001, table 1.7.9 (and others) may help you as well.
Now something completelly different. Are you sure you have call routing set properly ? If incomming calls have nowhere to go, then it will not be answered. Turn on syslog, debug log and catch them. It may reveal you something helpfull.

Similar Messages

  • Configuration path for Inbound delivery header text".

    Hi,
    I want separate text type for Inbound delivery, in transaction code VL31N.
    Can any body suggest on "Configuration path for Inbound delivery header text".
    Thanks & Regards
    Sudhansu

    Hi,
    Use Transaction VOTXN.
    *Select the radio button next to Delivery. and select Text types.
    *Go to new entries and create your own text ID after creating text ID go back to the previous screen and select change button.
    Create access sequence.
    select the access sequence you have created and double click ACCESS SEQUENCE FOR TEXT ID folder and Enter sequence number, Text object  and teh text ID you have created.
    Double click text procedure
    Select the text procedure which you are using for teh Delivery document type and double click TEXT ID IN TEXT PROCEDURE Folder.
    Assign the sequenec number TEXT ID and teh ACCESS sequence.
    Afer all teh above configuration steps the you can see the text ID in header text of billing document.
    To retrive teh contents of teh TEXT ID use Fuction module READ_TEXT with TEXT ID, LANG, NAME and TEXT OBJECT as input parameters.
    Note: The contents of the text ID will be in multiple lines of 70 characters each.
    Regards,
    Arun.S

  • How do I configure SPA8800 for a Viking FBI-1A?

    I am working with a customer who has had a phone system failure.  We're trying to replace the old Asterisk system that had a hardware interface card with a newer system and use an SPA8800 adapter (since I have that in stock and didn't have the hardware card in stock) to provide dialtone to the faxe machines and connect to the overhead paging system.  The problem I'm having is with the overhead paging system.
    The system is a Viking FBI-1A (http://www.vikingelectronics.com/products/view_product.php?pname=FBI-1A#), which can be configured either in Trunk Mode or Paging Mode.  In Paging Mode and connected to one of the FXS ports on the SPA8800, the paging system basically immediately "picks up" the FXS line and blares dial-tone over the overhead speakers, staying continuously off-hook, even after the "you left the phone of the hook, dummy" error beep starts playing.  In Trunk Mode and connected to one of the FXO ports on the SPA8800, the paging system never works -- when Asterisk tries to place any call to the SPA8800's FXO port, the SPA8800 replies with 503 Service Unavailable and nothing comes out the speakers.  I've done some testing with a plain old analog phone connected to the Viking in Trunk Mode, and the paging system basically isn't outputting dial-tone -- when in Trunk Mode it just sits there waiting for some audio to come in the trunk port and then records & rebroadcasts that audio.  My suspicion is that this lack of dial-tone is causing the SPA8800 to think the FXO line is dead.  I've looked for a setting to tell the SPA8800 to ignore the lack of dial-tone and just try to automatically blast audio out the FXO port, but I cannot find it.  Does that setting exist?  Is there a SIP Header I can have Asterisk send to make the SPA8800 just send the call to the FXO port without a dial string and without waiting for dial tone?

    Try 120 minute best quality.
    Don't forget to compress the audio to AC3.
    If that ends up too large, duplicate the preset you just used and dial down the bitrate and save it. Then apply the new version and try again.
    Rinse and repeat as nec till it fits.
    x

  • Configuration needed for SOA call to create PO in classic scenario

    Dear Experts,
    We are working in the SAP SRM 7.01 with backend system on ecc 6.0 Enhancement pack 5. The scenario configured is classic scenario.
    I want to know what are the configurations needed to use SOA calls to create a purchase order in the backend system.
    In the system landscape directory, when I use the system type "ERP_3.0" for backend system, the system uses the BAPI 'BAPI_PO_CREATE1' to create a purchase order in the backend system.
    When we use the system type "ERP_4.0", it does not use the BAPI 'BAPI_PO_CREATE1' to create purchase order. It tries to use SOA calls to create PO in the backend system. However, it fails to create one.
    Could you please let me know what are the settings we need to do to create a purchase order in the backend system?
    Thanks and regards,
    Ranjan
    Ranjan Sutradhar

    Hi Vardhan,
    Can you be a little clear? are you using PDP scenario as in your requirements are coming as PR from ECC into SRM as SC? Is this the scenario?
    Regards,
    Nikhil

  • CUBE- one way audio intermittent for inbound calls

         Have a CUBE on 3800 with 15.14M(6) with SIP to SIP dial peers. Some external inbound callers at times can hear no audio streaming from IVR.
    I run a traffic capture from the LAN side of the CUBE and I can hear the audio.
    I run a traffic capture on the WAN side (towards caller) and i hear nothing,  BUT the rtp stream is active (50 pps G711a). When i replay this stream on Wireshark i hear silence exactly what the caller can hear...
    G711a on both sides but no audio is heard on the WAN side exiting the CUBE towards telco
    DIal peers matched= 31 In from itsp and 40 Out to CUCM
    Setup:
    ITSP--SIP Trunk-- MyCUBE--SIP Trunk--CUCM--IVR(CTI Ports and RPs)
                                                                            |
                                                                     7900 Type A sccp Handsets  
    Config attached

    hi,
    Yes my itsp can connect and see that interface. Most calls work and only some fail. Intermittent. I have incuded a "show call active voice" for a "failed" incoming call from 0204002244 to 0498870440 . What happens here is silence to external caller coming in on dial peer 31 but there is an RTP stream being sent to him. Wireshark trace on WAN side proves silence within RTP stream exiting CUBE towards callers SBC at 10.193.202.100 from my cube at 10.66.41.1
    GENERIC:
    SetupTime=12:24:35.980 AEDT Thu Jan 30 2014
    Index=1
    PeerAddress=0204002244
    PeerSubAddress=
    PeerId=31
    PeerIfIndex=192
    LogicalIfIndex=0
    ConnectTime=12:24:36.080 AEDT Thu Jan 30 2014
    CallDuration=00:00:43 sec
    CallState=4
    CallOrigin=2
    ChargedUnits=0
    InfoType=speech
    TransmitPackets=2196
    TransmitBytes=351360
    ReceivePackets=2194
    ReceiveBytes=351040
    VOIP:
    ConnectionId[0x1D4C7D6F 0x888411E3 0xA9FBFF95 0xBEE5C848]
    IncomingConnectionId[0x1D4C7D6F 0x888411E3 0xA9FBFF95 0xBEE5C848]
    CallID=5201
    GlobalCallId=[0x1D4C7D6F 0x888411E3 0xA9FEFF95 0xBEE5C848]
    CallReferenceId=0
    CallServiceType=Unknown
    RTP Loopback Call=FALSE
    RemoteIPAddress=10.193.202.100
    RemoteUDPPort=14804
    RemoteSignallingIPAddress=10.193.202.100
    RemoteSignallingPort=5060
    RemoteMediaIPAddress=10.193.202.100
    RemoteMediaPort=14804
    RoundTripDelay=0 ms
    SelectedQoS=best-effort
    tx_DtmfRelay=inband-voice
    FastConnect=FALSE
    AnnexE=FALSE
    Separate H245 Connection=FALSE
    H245 Tunneling=FALSE
    SessionProtocol=sipv2
    [email protected]
    SessionTarget=10.193.202.100
    SafEnabled=FALSE
    OnTimeRvPlayout=0
    GapFillWithSilence=0 ms
    GapFillWithPrediction=0 ms
    GapFillWithInterpolation=0 ms
    GapFillWithRedundancy=0 ms
    HiWaterPlayoutDelay=0 ms
    LoWaterPlayoutDelay=0 ms
    TxPakNumber=0
    TxSignalPak=0
    TxComfortNoisePak=0
    TxDuration=0
    TxVoiceDuration=0
    RxPakNumber=0
    RxSignalPak=0
    RxComfortNoisePak=0
    RxDuration=0
    RxVoiceDuration=0
    RxOutOfSeq=0
    RxLatePak=0
    RxEarlyPak=0
    RxBadProtocol=0
    PlayDelayCurrent=0
    PlayDelayMin=0
    PlayDelayMax=0
    PlayDelayClockOffset=0
    PlayDelayJitter=0
    PlayErrPredictive=0
    PlayErrInterpolative=0
    PlayErrSilence=0
    PlayErrBufferOverFlow=0
    PlayErrRetroactive=0
    PlayErrTalkspurt=0
    ClockAdjustDuration=0
    EarlyPacketDuration=0
    LateDiscardDuration=0
    SilenceDiscardDuration=0
    JBuffDecreaseDuration=0
    JBuffIncreaseDuration=0
    OutSignalLevel=0
    InSignalLevel=0
    LevelTxPowerMean=0
    LevelRxPowerMean=0
    LevelBgNoise=0
    ERLLevel=0
    ACOMLevel=0
    ErrRxDrop=0
    ErrTxDrop=0
    ErrTxControl=0
    ErrRxControl=0
    ReceiveDelay=0 ms
    LostPackets=0
    EarlyPackets=0
    LatePackets=0
    SRTP = off
    TextRelay = off
    VAD = disabled
    CoderTypeRate=g711alaw
    CodecBytes=160
    Media Setting=flow-through
    CallerName=
    CallerIDBlocked=False
    OriginalCallingNumber=0204002244
    OriginalCallingOctet=0x0
    OriginalCalledNumber=0498870440
    OriginalCalledOctet=0x0
    OriginalRedirectCalledNumber=
    OriginalRedirectCalledOctet=0x80
    TranslatedCallingNumber=0204002244
    TranslatedCallingOctet=0x0
    TranslatedCalledNumber=0498870440
    TranslatedCalledOctet=0x0
    TranslatedRedirectCalledNumber=
    TranslatedRedirectCalledOctet=0x80
    GwReceivedCalledNumber=0498870440
    GwReceivedCalledOctet3=0x0
    GwReceivedCallingNumber=0204002244
    GwReceivedCallingOctet3=0x0
    GwReceivedCallingOctet3a=0x80
    MediaInactiveDetected=no
    MediaInactiveTimestamp=
    MediaControlReceived=
    LongDurationCallDetected=no
    LongDurCallTimestamp=
    LongDurcallDuration=
    Username=0204002244
    MlppServiceDomainNW=0 (none)
    MlppServiceDomainID=
    PrecedenceLevel=0 (PRECEDENCE_LEVEL_NONE)
    CPA Active Call Parameters
      CPA Event Status: DISABLE
    GENERIC:
    SetupTime=12:24:35.994 AEDT Thu Jan 30 2014
    Index=1
    PeerAddress=2440
    PeerSubAddress=
    PeerId=400
    PeerIfIndex=202
    LogicalIfIndex=0
    ConnectTime=12:24:36.074 AEDT Thu Jan 30 2014
    CallDuration=00:00:43 sec
    CallState=4
    CallOrigin=1
    ChargedUnits=0
    InfoType=speech
    TransmitPackets=2196
    TransmitBytes=351360
    ReceivePackets=4396
    ReceiveBytes=703360
    VOIP:
    ConnectionId[0x1D4C7D6F 0x888411E3 0xA9FBFF95 0xBEE5C848]
    IncomingConnectionId[0x1D4C7D6F 0x888411E3 0xA9FBFF95 0xBEE5C848]
    CallID=5202
    GlobalCallId=[0x1D4C7D6F 0x888411E3 0xA9FEFF95 0xBEE5C848]
    CallReferenceId=0
    CallServiceType=Unknown
    RTP Loopback Call=FALSE
    RemoteIPAddress=10.66.22.20
    RemoteUDPPort=31334
    RemoteSignallingIPAddress=10.66.22.20
    RemoteSignallingPort=5060
    RemoteMediaIPAddress=10.66.21.20
    RemoteMediaPort=31334
    RoundTripDelay=0 ms
    SelectedQoS=best-effort
    tx_DtmfRelay=rtp-nte
    FastConnect=FALSE
    AnnexE=FALSE
    Separate H245 Connection=FALSE
    H245 Tunneling=FALSE
    SessionProtocol=sipv2
    [email protected]
    SessionTarget=10.66.22.20
    SafEnabled=FALSE
    OnTimeRvPlayout=0
    GapFillWithSilence=0 ms
    GapFillWithPrediction=0 ms
    GapFillWithInterpolation=0 ms
    GapFillWithRedundancy=0 ms
    HiWaterPlayoutDelay=0 ms
    LoWaterPlayoutDelay=0 ms
    TxPakNumber=0
    TxSignalPak=0
    TxComfortNoisePak=0
    TxDuration=0
    TxVoiceDuration=0
    RxPakNumber=0
    RxSignalPak=0
    RxComfortNoisePak=0
    RxDuration=0
    RxVoiceDuration=0
    RxOutOfSeq=0
    RxLatePak=0
    RxEarlyPak=0
    RxBadProtocol=0
    PlayDelayCurrent=0
    PlayDelayMin=0
    PlayDelayMax=0
    PlayDelayClockOffset=0
    PlayDelayJitter=0
    PlayErrPredictive=0
    PlayErrInterpolative=0
    PlayErrSilence=0
    PlayErrBufferOverFlow=0
    PlayErrRetroactive=0
    PlayErrTalkspurt=0
    ClockAdjustDuration=0
    EarlyPacketDuration=0
    LateDiscardDuration=0
    SilenceDiscardDuration=0
    JBuffDecreaseDuration=0
    JBuffIncreaseDuration=0
    OutSignalLevel=0
    InSignalLevel=0
    LevelTxPowerMean=0
    LevelRxPowerMean=0
    LevelBgNoise=0
    ERLLevel=0
    ACOMLevel=0
    ErrRxDrop=0
    ErrTxDrop=0
    ErrTxControl=0
    ErrRxControl=0
    ReceiveDelay=0 ms
    LostPackets=0
    EarlyPackets=0
    LatePackets=0
    SRTP = off
    TextRelay = off
    VAD = disabled
    CoderTypeRate=g711alaw
    CodecBytes=160
    Media Setting=flow-through
    AlertTimepoint=12:24:36.004 AEDT Thu Jan 30 2014
    CallerName=
    CallerIDBlocked=False
    OriginalCallingNumber=0204002244
    OriginalCallingOctet=0x0
    OriginalCalledNumber=0498870440
    OriginalCalledOctet=0x0
    OriginalRedirectCalledNumber=
    OriginalRedirectCalledOctet=0x80
    TranslatedCallingNumber=00204002244
    TranslatedCallingOctet=0x0
    TranslatedCalledNumber=2440
    TranslatedCalledOctet=0x0
    TranslatedRedirectCalledNumber=
    TranslatedRedirectCalledOctet=0x80
    GwReceivedCalledNumber=0498870440
    GwReceivedCalledOctet3=0x0
    GwOutpulsedCalledNumber=2440
    GwOutpulsedCalledOctet3=0x0
    GwReceivedCallingNumber=0204002244
    GwReceivedCallingOctet3=0x0
    GwReceivedCallingOctet3a=0x80
    GwOutpulsedCallingNumber=00204002244
    GwOutpulsedCallingOctet3=0x0
    GwOutpulsedCallingOctet3a=0x80
    MediaInactiveDetected=no
    MediaInactiveTimestamp=
    MediaControlReceived=
    LongDurationCallDetected=no
    LongDurCallTimestamp=
    LongDurcallDuration=
    Username=0204002244
    MlppServiceDomainNW=0 (none)
    MlppServiceDomainID=
    PrecedenceLevel=0 (PRECEDENCE_LEVEL_NONE)

  • No ringbacktone for inbound calls with cucm 8.6

    Hi,
    we have this problem from many days...
    we have two branches with cucm cluster(Publisher and Subscriber) at Head office and cisco untiy.The branches are connected to Head office through MPLS vpn and all the ip phones are registred to publisher located at headoffice.
    our setup is like below
    HO and BR2 having SIP lines and BR1 has PSTN Lines.
    we implement greetings for head office and 2 branches at Headoffice Unity.
    when any call comes to headoffice gateway the greetings will be played and call will be diverted to the appropriate extension.everything is fine.
    But the problem is when the call comes to Branch gateway and the greetings will be played and the call gets diverted to the IP phone to which the caller dialed the extension. but the caller is not hearing the ringback tone while the extension is ringing. and the caller cannot know whether the extension is ringing or the call got disconnected.
    i tried to change the " Send h225 User Information Message"  in service parameters from "Use ANN for Ring Back" to H225 Info for call Progress Tone"
    whenever i am changing to  "H225 Info for call Progress Tone" then the branches problem getting solved but Headoffice getting the same problem.
    please can anyone help............................

    Hi Carlo,
    Thankyou for the Response...
    here is the Runn config for BR1 Connected to PSTN lines....
    voice-card 0
    dspfarm
    dsp services dspfarm
    voice service voip
    allow-connections h323 to h323
    allow-connections h323 to sip
    allow-connections sip to h323
    allow-connections sip to sip
    h323
    voice class codec 1
    codec preference 1 g711ulaw
    codec preference 2 g711alaw
    codec preference 3 g729r8
    codec preference 4 g729br8
    voice class h323 1
    h225 timeout tcp establish 3
    interface Tunnel100
    description " Tunnel JED-RYD "
    bandwidth 2048
    ip address 10.10.0.1 255.255.255.252
    tunnel source 172.31.217.202
    tunnel destination 172.31.3.18
    interface FastEthernet0/0
    description DAMMAM Local LAN
    no ip address
    duplex auto
    speed auto
    interface FastEthernet0/0.20
    description JEDDAH Local LAN
    encapsulation dot1Q 20
    ip address 192.168.20.5 255.255.255.0
    interface FastEthernet0/0.21
    description JEDDAH VOICE VLAN
    encapsulation dot1Q 21
    ip address 192.168.21.5 255.255.255.0
    h323-gateway voip interface
    h323-gateway voip bind srcaddr 192.168.21.5
    interface FastEthernet0/1
    ip address 172.31.217.202 255.255.255.252
    duplex auto
    speed auto
    router eigrp 200
    network 10.10.0.0 0.0.0.3
    network 192.168.20.0
    network 192.168.21.0
    no auto-summary
    router bgp 65412
    no synchronization
    bgp log-neighbor-changes
    neighbor 172.31.217.201 remote-as 65000
    no auto-summary
    ip forward-protocol nd
    ip route 0.0.0.0 0.0.0.0 192.168.20.1
    ip route 192.168.20.50 255.255.255.255 192.168.20.1
    ip http server
    ip http access-class 23
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    access-list 23 permit 10.10.10.0 0.0.0.7
    control-plane
    voice-port 0/0/0
    supervisory disconnect dualtone mid-call
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    timing hookflash-out 500
    timing guard-out 300
    timing sup-disconnect 50
    connection plar opx 2050
    impedance complex2
    description STC
    caller-id alerting dsp-pre-allocate
    voice-port 0/0/1
    supervisory disconnect dualtone mid-call
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    timing hookflash-out 500
    timing guard-out 300
    timing sup-disconnect 50
    connection plar opx 2050
    impedance complex2
    description STC
    caller-id alerting dsp-pre-allocate
    voice-port 0/0/2
    supervisory disconnect dualtone mid-call
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    timing hookflash-out 500
    timing guard-out 300
    timing sup-disconnect 50
    connection plar opx 2050
    impedance complex2
    description STC
    caller-id alerting dsp-pre-allocate
    voice-port 0/0/3
    supervisory disconnect dualtone mid-call
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    timing hookflash-out 500
    timing guard-out 300
    timing sup-disconnect 50
    connection plar opx 2050
    impedance complex2
    description STC
    caller-id alerting dsp-pre-allocate
    voice-port 0/2/0
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    connection plar 2022
    shutdown
    impedance complex2
    description STC
    voice-port 0/2/1
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    shutdown
    impedance complex2
    description STC
    voice-port 0/3/0
    supervisory disconnect dualtone mid-call
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    timing hookflash-out 500
    timing guard-out 300
    timing sup-disconnect 50
    connection plar opx 2050
    impedance complex2
    description STC
    caller-id alerting dsp-pre-allocate
    voice-port 0/3/1
    supervisory disconnect dualtone mid-call
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    timing hookflash-out 500
    timing guard-out 300
    timing sup-disconnect 50
    connection plar opx 2050
    impedance complex2
    description STC
    caller-id alerting dsp-pre-allocate
    voice-port 0/3/2
    supervisory disconnect dualtone mid-call
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    timing hookflash-out 500
    timing guard-out 300
    timing sup-disconnect 50
    connection plar opx 2050
    impedance complex2
    description STC
    caller-id alerting dsp-pre-allocate
    voice-port 0/3/3
    supervisory disconnect dualtone mid-call
    no battery-reversal
    input gain -3
    output attenuation -3
    echo-cancel coverage 32
    cptone BE
    timeouts initial 5
    timeouts interdigit 3
    timeouts call-disconnect 3
    timeouts ringing 5
    timeouts wait-release 1
    timing hookflash-out 500
    timing guard-out 300
    timing sup-disconnect 50
    connection plar opx 2050
    impedance complex2
    description STC
    caller-id alerting dsp-pre-allocate
    sccp local FastEthernet0/0.21
    sccp ccm 192.168.12.190 identifier 1 priority 1 version 5.0.1
    sccp ccm 192.168.12.189 identifier 2 priority 2 version 5.0.1
    sccp
    sccp ccm group 1
    associate ccm 1 priority 1
    associate ccm 2 priority 2
    associate profile 1 register CONFJEDRAW
    associate profile 2 register TRNJED
    associate profile 3 register MTPJED
    switchover method immediate
    switchback method immediate
    switchback interval 15
    dspfarm profile 2 transcode
    codec g711ulaw
    codec g711alaw
    codec g729ar8
    codec g729abr8
    maximum sessions 2
    associate application SCCP
    dspfarm profile 1 conference
    codec g711ulaw
    codec g711alaw
    codec g729ar8
    codec g729abr8
    codec g729r8
    codec g729br8
    shutdown
    dspfarm profile 3 mtp
    codec g729r8
    maximum sessions software 250
    associate application SCCP
    shutdown
    dial-peer voice 1 pots
    dial-peer voice 1000 voip
    description To CallManager - SBWPMPUB
    destination-pattern [1-5]...
    progress_ind progress enable 8
    voice-class codec 1
    voice-class h323 1
    session target ipv4:192.168.12.190
    dtmf-relay h245-alphanumeric
    no vad
    dial-peer voice 9001 pots
    description ** 02-6140294(outgoing) **
    destination-pattern [^2].T
    port 0/0/1
    dial-peer voice 9002 pots
    description ** 02-6140295(outgoing) **
    destination-pattern [^2].T
    port 0/0/2
    dial-peer voice 9003 pots
    description ** 02-6140296(outgoing) **
    destination-pattern [^2].T
    port 0/0/3
    dial-peer voice 9004 pots
    description ** 02-6140293(outgoing) **
    destination-pattern [^2].T
    port 0/0/0
    dial-peer voice 290 pots
    incoming called-number .
    direct-inward-dial
    dial-peer voice 9006 pots
    description ** 02-6529323(local) **
    destination-pattern [^0].T
    port 0/3/0
    dial-peer voice 9010 pots
    description ** 02-6578249(local) **
    destination-pattern [^0].T
    port 0/3/1
    dial-peer voice 9011 pots
    description "to pstn service"
    shutdown
    destination-pattern 0.T
    port 0/3/3
    dial-peer voice 9009 pots
    description "to pstn service"
    shutdown
    destination-pattern [^0].T
    port 0/3/2
    dial-peer voice 9005 pots
    destination-pattern .T
    dial-peer voice 1001 voip
    description To CallManager - Subscriber
    destination-pattern [1-5]...
    progress_ind progress enable 8
    voice-class codec 1
    voice-class h323 1
    session target ipv4:192.168.12.189
    dtmf-relay h245-alphanumeric
    no vad
    dial-peer voice 1002 voip
    description " TO Unity Greetings"
    destination-pattern 2050
    progress_ind progress enable 8
    voice-class codec 1
    voice-class h323 1
    session target ipv4:192.168.12.190
    dtmf-relay h245-alphanumeric
    no vad
    dial-peer voice 1003 voip
    description " TO Unity Greetings"
    destination-pattern 2050
    progress_ind progress enable 8
    voice-class codec 1
    voice-class h323 1
    session target ipv4:192.168.12.189
    dtmf-relay h245-alphanumeric
    no vad

  • No Redundancy for Inbound Calls

    Dear all,
    We have 2 CallManagers at our organization. Incoming calls are routed to Attendant Console to listening Music on Hold. Whenever the Publisher CallManager is down, calls coming into our organization receive a busy signal. I thought we were setup for redundancy, but I found out the hard way that this was not the case.
    We have a 2911 router which routes incoming phone traffic into our organization. On it are two dial peers which route our organization?s incoming calls to the CallManagers. The primary dial peer is supposed to route to the publishe  and the secondary dial peer to the subscriber. Below are the 2 dial peers which route our traffic.
    voice class h323 1
      h225 timeout tcp establish 3
    dial-peer voice 11 voip
     preference 2
     destination-pattern 3.......
     session target ipv4:10.1.11.30 ( publiser)
     dtmf-relay h245-alphanumeric
     codec g711alaw
    dial-peer voice 10 voip
     preference 1
     destination-pattern 3.......
     session target ipv4:10.1.11.31 ( subcriber)
     dtmf-relay h245-alphanumeric
     codec g711alaw
    If i delete dial peer voice 11, incoming call can route to subcriber successfully
     I would appreciate anyone taking the time to look at them and offer any suggestions.
    CCM 10.0
    I got debug for this as below:
    TSI-DC-VGR01-0#end
    Translating "end"
    % Bad IP address or host name
    Translating "end"
    % Unknown command or computer name, or unable to find computer address
    TSI-DC-VGR01-0#
    Jul 30 07:48:09.066: //-1/AEEEB6D6813B/CCAPI/cc_api_display_ie_subfields:
       cc_api_call_setup_ind_common:
       cisco-username=
       ----- ccCallInfo IE subfields -----
       cisco-ani=0905916072
       cisco-anitype=2
       cisco-aniplan=1
       cisco-anipi=0
       cisco-anisi=3
       dest=38236688
       cisco-desttype=0
       cisco-destplan=1
       cisco-rdie=FFFFFFFF
       cisco-rdn=
       cisco-rdntype=-1
       cisco-rdnplan=-1
       cisco-rdnpi=-1
       cisco-rdnsi=-1
       cisco-redirectreason=-1   fwd_final_type =0
       final_redirectNumber =
       hunt_group_timeout =0
    Jul 30 07:48:09.066: //-1/AEEEB6D6813B/CCAPI/cc_api_call_setup_ind_common:   Interface=0x2BA17414, Call Info(   Calling Number=0905916072,(Calling Name=)(TON=National, NPI=ISDN, Screenin
    etwork, Presentation=Allowed),
       Called Number=38236688(TON=Unknown, NPI=ISDN),
       Calling Translated=FALSE, Subscriber Type Str=RegularLine, FinalDestinatioag=TRUE,
       Incoming Dial-peer=9, Progress Indication=NULL(0), Calling IE Present=TRUE
       Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=F
    E), Call Id=-1
    Jul 30 07:48:09.066: //-1/AEEEB6D6813B/CCAPI/ccCheckClipClir:
       In: Calling Number=0905916072(TON=National, NPI=ISDN, Screening=Network, P
    entation=Allowed)
    Jul 30 07:48:09.070: //-1/AEEEB6D6813B/CCAPI/ccCheckClipClir:
       Out: Calling Number=0905916072(TON=National, NPI=ISDN, Screening=Network,
    sentation=Allowed)
    Jul 30 07:48:09.070: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    Jul 30 07:48:09.070: :cc_get_feature_vsa malloc success
    Jul 30 07:48:09.070: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    Jul 30 07:48:09.070:  cc_get_feature_vsa count is 1
    Jul 30 07:48:09.070: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    Jul 30 07:48:09.070: :FEATURE_VSA attributes are: feature_name:0,feature_time
    0612504,feature_id:1877
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/cc_api_call_setup_ind_common:
       Set Up Event Sent;
       Call Info(Calling Number=0905916072(TON=National, NPI=ISDN, Screening=Netw
    , Presentation=Allowed),
       Called Number=38236688(TON=Unknown, NPI=ISDN))
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/cc_process_call_setup_ind:
       Event=0x2B9DF948
    Jul 30 07:48:09.070: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
       Try with the demoted called number 38236688
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/ccCallSetContext:
       Context=0x300C4B5C
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/cc_process_call_setup_ind:
       >>>>CCAPI handed cid 1877 with tag 9 to app "_ManagedAppProcess_Default"
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/ccCallProceeding:
       Progress Indication=NULL(0)
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/ccCallSetupRequest:
       Destination=, Calling IE Present=TRUE, Mode=0,
       Outgoing Dial-peer=10, Params=0x300C606C, Progress Indication=NULL(0)
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/ccCheckClipClir:
       In: Calling Number=0905916072(TON=National, NPI=ISDN, Screening=Network, P
    entation=Allowed)
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/ccCheckClipClir:
       Out: Calling Number=0905916072(TON=National, NPI=ISDN, Screening=Network,
    sentation=Allowed)
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/ccCallSetupRequest:
       Destination Pattern=3......., Called Number=38236688, Digit Strip=FALSE
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/ccCallSetupRequest:
       Calling Number=0905916072(TON=National, NPI=ISDN, Screening=Network, Prese
    tion=Allowed),
       Called Number=38236688(TON=Unknown, NPI=ISDN),
       Redirect Number=, Display Info=
       Account Number=, Final Destination Flag=TRUE,
       Guid=AEEEB6D6-16F4-11E4-813B-A4934C055B80, Outgoing Dial-peer=10
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/cc_api_display_ie_subfields:
       ccCallSetupRequest:
       cisco-username=
       ----- ccCallInfo IE subfields -----
       cisco-ani=0905916072
       cisco-anitype=2
       cisco-aniplan=1
       cisco-anipi=0
       cisco-anisi=3
       dest=38236688
       cisco-desttype=0
       cisco-destplan=1
       cisco-rdie=FFFFFFFF
       cisco-rdn=
       cisco-rdntype=-1
       cisco-rdnplan=-1
       cisco-rdnpi=-1
       cisco-rdnsi=-1
       cisco-redirectreason=-1   fwd_final_type =0
       final_redirectNumber =
       hunt_group_timeout =0
    Jul 30 07:48:09.070: //1877/AEEEB6D6813B/CCAPI/ccIFCallSetupRequestPrivate:
       Interface=0x312C8048, Interface Type=1, Destination=, Mode=0x0,
       Call Params(Calling Number=0905916072,(Calling Name=)(TON=National, NPI=IS
     Screening=Network, Presentation=Allowed),
       Called Number=38236688(TON=Unknown, NPI=ISDN), Calling Translated=FALSE,
       Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-
    r=10, Call Count On=FALSE,
       Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, A
    ication Call Id=)
    Jul 30 07:48:09.070: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    Jul 30 07:48:09.070: :cc_get_feature_vsa malloc success
    Jul 30 07:48:09.074: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    Jul 30 07:48:09.074:  cc_get_feature_vsa count is 2
    Jul 30 07:48:09.074: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    Jul 30 07:48:09.074: :FEATURE_VSA attributes are: feature_name:0,feature_time
    0612952,feature_id:1878
    Jul 30 07:48:09.074: //1878/AEEEB6D6813B/CCAPI/ccIFCallSetupRequestPrivate:
       SPI Call Setup Request Is Success; Interface Type=1, FlowMode=1
    Jul 30 07:48:09.074: //1878/AEEEB6D6813B/CCAPI/ccCallSetContext:
       Context=0x300C601C
    Jul 30 07:48:09.074: //1877/AEEEB6D6813B/CCAPI/ccSaveDialpeerTag:
       Outgoing Dial-peer=10
    Jul 30 07:48:19.386: //1877/AEEEB6D6813B/CCAPI/cc_api_call_disconnected:
       Cause Value=102, Interface=0x2BA17414, Call Id=1877
    Jul 30 07:48:19.386: //1877/AEEEB6D6813B/CCAPI/cc_api_call_disconnected:
       Call Entry(Responsed=FALSE, Cause Value=102, Retry Count=0)
    Jul 30 07:48:19.386: //1878/AEEEB6D6813B/CCAPI/ccCallDisconnect:
       Cause Value=102, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconne
    Cause=0)
    Jul 30 07:48:19.386: //1878/AEEEB6D6813B/CCAPI/ccCallDisconnect:
       Cause Value=102, Call Entry(Responsed=FALSE, Cause Value=102)
    Jul 30 07:48:19.386: //1878/AEEEB6D6813B/CCAPI/cc_api_get_transfer_info:
       Transfer Number Is Null
    Jul 30 07:48:19.386: //1877/AEEEB6D6813B/CCAPI/ccCallDisconnect:
       Cause Value=102, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconne
    Cause=102)
    Jul 30 07:48:19.386: //1877/AEEEB6D6813B/CCAPI/ccCallDisconnect:
       Cause Value=102, Call Entry(Responsed=TRUE, Cause Value=102)
    Jul 30 07:48:19.386: //1877/AEEEB6D6813B/CCAPI/cc_api_get_transfer_info:
       Transfer Number Is Null
    Jul 30 07:48:19.386: //1878/AEEEB6D6813B/CCAPI/cc_api_call_disconnect_done:
       Disposition=0, Interface=0x312C8048, Tag=0x0, Call Id=1878,
       Call Entry(Disconnect Cause=102, Voice Class Cause Code=0, Retry Count=0)
    Jul 30 07:48:19.386: //1878/AEEEB6D6813B/CCAPI/cc_api_call_disconnect_done:
       Call Disconnect Event Sent
    Jul 30 07:48:19.386: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
    Jul 30 07:48:19.386: :cc_free_feature_vsa freeing 2C24DB50
    Jul 30 07:48:19.386: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
    Jul 30 07:48:19.386:  vsacount in free is 1
    Jul 30 07:48:19.394: //1877/AEEEB6D6813B/CCAPI/cc_api_call_disconnect_done:
       Disposition=0, Interface=0x2BA17414, Tag=0x0, Call Id=1877,
       Call Entry(Disconnect Cause=102, Voice Class Cause Code=0, Retry Count=0)
    Jul 30 07:48:19.398: //1877/AEEEB6D6813B/CCAPI/cc_api_call_disconnect_done:
       Call Disconnect Event Sent
    Jul 30 07:48:19.398: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
    Jul 30 07:48:19.398: :cc_free_feature_vsa freeing 2C24D990
    Jul 30 07:48:19.398: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

    Dear Okanlawon & islam.kamal,
    Both of you are correct. I used your command and it worked now. It also help me solved the problem related to Music On Hold cause i use g711ulaw ( MoH wont work with incoming call).
    I used c2900-universalk9-mz.SPA.151-4.M4.bin
    Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.1(4)M4,
    EASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Tue 20-Mar-12 18:57 by prod_rel_team
    ROM: System Bootstrap, Version 15.0(1r)M15, RELEASE SOFTWARE (fc1)
    Thank you very much ! You are the god !
    ThanhNT

  • Lync Dispalying wrong Name for inbound calls

    We have Active Directory running on Windows 2012 R2 Domain Controllers.  We have Exchange 2010 and LYNC 2013.  We have presence integration with our Avaya CM ver 6.x.  
    We have had a few employee's leave and have re-assigned their desk phone extensions to new employee's.  The old employee's were removed from Active Directory and the LYNC server.
    On the LYNC 2013 client when a call comes in it is showing the old employee's name on the LYNC Client.
    I have deleted the local LYNC Addressbooks at the client.
    Still happening.
    Where to look for the file containing the old employee that is causing this mismatch.
    Thank you,

    Hi WillieWinslow,
    Agree with Paul.
    Before starting a new test, you can check the following items.
    1. Make sure the contact who has left the company is not existing in the user’s Outlook Contact folders.
    2. (Optional)Run Update-CsUserDataBase to force Back-End to
    re-read all the user-related information stored in Active Directory Domain Services.
    Delete the .slabs file from the file share sitting on X:\share\1-WebServices-1\ABfiles\000000000\000000000 folder.
    3. Run Update-CsAddressBook
    4. Delete the test user’s Lync profile on the test machine.
    After doing the above, it should be able to solve your problem.
    Best regards,
    Eric

  • Configure VI front panel for subsequent calls

    When you call a VI with an unwired input, the default value for the control is used. Most of the time, this makes good sense. But then how can you configure a VI to operate in a particular way, and subsequently call it to repeatedly perform some function given the prior configuration?
    For example, suppose I have a VI that works something like a virtual o-scope. I want to configure the instrument once (set up all the controls: time base, volt ranges, etc) and then periodically take readings. Is there any way to do this without having to wire the setup every time I take a reading?

    Use Action Engines or Functional Globals.  They make use of un-initialized shift registers.  Upon first call, the initilization must take place inside the vi.  The init values get wired to the shift registers on the right side.  Upon next call, the shift registers will retain the values that were set on the first call.
    See the Action Engine Nugget created by Ben.  Very useful and very practical.
    - tbob
    Inventor of the WORM Global

  • I'm unable to accept inbound calls on my iPhone 5 for a holden commodore VE - 2012 model - any ideas on how to resolve?

    How do I resolve the issue for answering inbound calls on my iPhone 5 when connected to Bluetooth in a holden commodore VE - 2012 model. Outbound calls connect ok.

    I'm having the same problem with a 2013 GMC terrain.  I don't know if the problem is the car or the iPhone 5.  I have been seeing this problem more and more on threads.  Can anyone help us with this? Is there any info online from Apple re: new updates that would solve this problem?

  • Want to configure Oracle EDI Gateway for Inbound Invoice Interface

    Hello,
    Newbie to Oracle Apps and want to configure Oracle EDI Gateway for Inbound Invoice Interface. We are having Oracle EBS R12 installed on OEL 5.6
    Do i need to install EDI Gateway or it comes with APPS R12 installation ? if i have to install it explicitly then which EDI version i have to install ? what are steps should i follow to achieve desired results.
    One more query, we are having old version of Oracle APPS 6i too, is it possible to configure Oracle EDI Gateway on it ??
    You help will be highly appreciated.

    Try to post your message on dedicated EBS forums http://forums.oracle.com/forums/category.jspa?categoryID=3.

  • How can delayed delivery update be configured for Inbound delivery ?

    Hi All,
    How can delayed delivery update be configured for Inbound delivery ?
    There is setting for Outbound delivery delayed delivery update but how the same functionality be used for Inbound delivery?
    Regards
    Jimmi

    Hello Jimmi,
    Unfortunately I must confirm that the Delayed delivery update is only available for outbound deliveries. Please see below note for further details
    664316 Tips for the delayed delivery update for TO
    I hope this information helps!
    Martin

  • [PAP2] Configuring Multiple Service Providers for Outgoing Calls

    I'm trying to configure my PAP2 with Gizmo project (for incoming calls) and VOIPCheap (for outgoing calls).
    I tried to use the dialplan:
    (xx.<:@voipcheap.host.xxx:5060; usr=myvoipcheapuserid; pwd=myvoipcheappassword; >)
    But this doesn't seem to work. But when I configure the line for the VOIPCheap provider, then I am able to make calls through that account.
    Can someone help me configure my PAP2 adapter please?
    Thank you very much in advance.
    Sekhar.

    I shall have found this post a bit earlier... sik! 
    I have 2 PAP2T 'listenning' to 3 different providers (1 is common); that works... but to be optimal, both ATAs should allow using a 4th provider for outgoing calls.
    The ATA administration guide shows an example of a dial plan such as <8,:1408>xxxxxxx<:@pstn.Linksys.com:5061;usr=joe;pwd=joe_pwd;nat>
    Unfortunately, it applies for AG310 and SPA3102...
    VoIP_Addict, I guess that if you did find some time to 'play' with this, you can only confirm what has been said in this post, right?

  • Inbound Calls Fail

    HI.
    I'm running CME on a 2851.
    My issue is with inbound calls not failing totally, but then requiring the extension to be dialed. This only happens for calls where the calling number is unknown.
    So all calls inbound work if the inbound calling number is known. Calls route nicely.
    If the calling number is unknown the caller gets a tone, whereby they need to then dial the extension.
    Ideally I'd like to have unknown calling numbers simply route the call the same way as with a known calling number.
    FYI when i debug q931 caller id (if off) is shown as Calling Party Number i = 0x00A3, N/A
    Appreciate any help as this is causing some problems!!!
    Configuration attached

    Timothy,
    When the calls come in, a dial-peer match is made, and in this case, where the calling number is known, the dial-peer whose destination-pattern command matches the calling number is selected, and the call is routed.
    For calls where the calling number is not available, there is no dial-peer matched, so the default dial-peer (dial-peer 0) is used, and two stage dialing is then required.
    To resolve, a quick solution would be to create a new dial-peer that has the incoming called-number command (which matches on the called number), so that this dial-peer will always be used for all incoming calls regardless of whether the calling number is available or not.
    Use the direct-inward-dial command as well in this dial-peer to force one stage dialing.
    dial-peer voice 90 pots
    incoming called-number .
    direct-inward-dial
    port 0/0/0:15.
    See also
    * http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml#topic3
    * http://www.cisco.com/en/US/tech/tk652/tk698/technologies_tech_note09186a00800e00d0.shtml
    Hope this helps.
    Regards,
    Michael.

  • 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

  • Payment advice issue

    Dear sapguys, we had config fbzp in this one i assigned payment advice form and programme is rffous_c. but we are using manual payment at the time of manual payments like through f-53, but f-58 is automatic payment advice  but we need how do i take w

  • Who have knowledge from Femtocell technology at Sony (Xperia Z2 and Zperia Z)

    Contact request for a person who have knowledge from Femtocell technology at Sony (Xperia Z2 and Zperia Z). I have been unable to resolve mobile data connectivity issues occuring with femtocell. Me and the operator have been trying to find a resoluti

  • Error through Oracle update

    Hello, I have been using the UTL_FILE object to append to an audit log for some time now and has worked really well. But while i was on holiday i believe the version of Oracle 9i we have was upgraded with a new version. Now the UTL_FILE object keeps

  • What function should I use to composite two effect worlds with ADD mode?

    how can I do it without iterate suit? ADD mode means R = Ra+Rb, G = Ga+Gb, B = Ba+Bb, A = Aa+Ab Is there a simple way to composite worlds in plugs-in just like what AE does?

  • I can't enter my apple ID to iMessage

    I can't enter my apple ID to iMessage,when I enter they write,that apple ID or password isn' t right.why? I can use this apple ID in apple store,but in iMessage no