Getting Account-Determination related Error during Service Entry Approval

Dear Sir,
We have created a Service Order (Purchase Order)  with Account-Assignment Category as "Q"  and Item-Category as "D" . The In the Purchase Order , Account assignment given was a WBS Element  and appropriate GL for expense booking was also mentioned .
Subsequently , we did Service Entry (ML81n) .
Now during the approval of Service Entry Sheet , we are getting following error...
"Account determination for entry 9000 KBS 0001 not possible" .
We request to kindly guide us as what steps need to be followed to resolve this error . We will be highly greatful for the given  kind help pl .
With Regards
Sania

HI
.1. In OBYC, check the Account Determination check box is not ticked. This means the account determination is not done from OBYC. It is done as per the account assignment entered in PO. 2. Check  OMJJ go to OMJJ and enter teh movement type 101and go to Account geouping folder and click on it
all the line which has KBS in TEKey check the Check acc *** check box than you will not get this error.
3.Goto OBYC double click KBS and enter your valuation grouping code and assign to the G/L accounts and save

Similar Messages

  • Abab error during service entry sheet

    dear experts
    during service entry sheet the below error dump message is came.
    pls any one solver porblem.
    document # generated but which is not meet our oringla no range also its not save and terminated.
    Update was terminated
    System ID....   NEP
    Client.......   900
    User.....   mmusr
    Transaction..   ML81N
    Update key...   62B9FADE4AA3F18C8457001F29CC32A8
    Generated....   06.01.2010, 14:49:32
    Completed....   06.01.2010, 14:49:32
    Error Info...   ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC

    Check ST22 for abap dump. It looks program try to insert duplicate record. If there is an enhancement in standard tcode debug it. If not ask it to SAP via OSS.

  • Account determination error during service entry for service PO

    Dear Experts,
    This about service PO. I created PO # 4501517101 & wanted to perform service entry via t/code ML81N. But I'm getting error "147 Account determination for entry OP01 FR1 OP01 not possible"
    Appreciate if could anyone assist me on this issue. TQ.
    rgds,
    nantha

    Please correct the assignment in OBYC and also in this error itself u can see one icon of proceed.If you will click on Proceed, then it will take u in to OBYC, where u have to do the corrections.

  • During service entry sheet

    hi experts
    during service entry sheet i meet below problem can any one resolve this issue
    147 account determination for entry nrca fr2 not possible
    i hope this issue related vendor master
    waiting yours reply

    Hai VV,
    I am facing one problem at the time serviece entry sheet (ml81n) ,my user wants serviece valuation class they need seperated gl account (gr/ir clearing account), previously for all valuation classes are having same gl account in obyc key wrx.,but now i have changed the gl account new one for serviece valuation class ,i removed old one even though at ml81n the entry is coming with old gr/ir account.,can you tell me from where it is picking i am surly tell that it is not coming from wrx >vauation class(servieces)>grirglaccount.
    can you tell from where it is picking
    Thanks
    Amarnath Reddy.

  • Get '500 Internal Server Error' during SIP INVITE - cause 44

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    Get ‘500 Internal Server Error’ during SIP INVITE - cause 44
    Have you ever seen anything like this before?  It usually works, but intermittently, we see calls get rejected.  It somehow seems related to high loads on the router.  We reduced the occurrences by changing our code to throttle the number of SIP INVITEs we send, but this doesn’t scale well.  Once it occurs, the only way to clean it up is to do a shut/no shut on the voice-port associated to SIP INVITE.
    Any suggestions on how we can proceed to debug this issue?
    BACKGROUND:
    Cisco 2811 running (C2800NM-ADVENTERPRISEK9-M), Version 12.4(24)T3, RELEASE SOFTWARE (fc2)
    NAME: "2811 chassis", DESCR: "2811 chassis" PID: CISCO2811
    NAME: "9 Port FE Switch on Slot 0 SubSlot 1", DESCR: "9 Port FE Switch" PID: HWIC-D-9ESW
    NAME: "WIC/VIC/HWIC 1 Power Daughter Card", DESCR: "9-Port HWIC-ESW Power Daughter Card" PID: ILPM-8
    NAME: "Two port E1 voice interface daughtercard on Slot 0 SubSlot 2", DESCR: "Two port E1 voice interface daughtercard" PID: VWIC-2MFT-E1=
    NAME: "Two port E1 voice interface daughtercard on Slot 0 SubSlot 3", DESCR: "Two port E1 voice interface daughtercard" PID: VWIC-2MFT-E1=
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 0 SubSlot 4", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    NAME: "High Density Voice2 Network module with on board two port interface  on Slot 1", DESCR: "High Density Voice2 Network module with on board two port interface " PID: NM-HDV2-2T1/E1
    NAME: "2nd generation two port EM voice interface daughtercard on Slot 1 SubSlot 0", DESCR: "2nd generation two port EM voice interface daughtercard" PID: VIC2-2E/M
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 1 SubSlot 2", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 1 SubSlot 3", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 1 SubSlot 4", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 1 SubSlot 5", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    WIRESHARK:
    No.     Time        Source                Destination           Protocol Info
          2 0.057246    10.194.154.136        171.68.115.156        SIP      Status: 100 Trying
    Frame 2 (471 bytes on wire, 471 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 100 Trying
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41a-100875-517454db
            From: <sip:[email protected]:5060>;tag=82f4a00-9c7344ab-13c4-45026-41a-4ea64c5a-41a
            To: <sip:[email protected]:5060>
            Date: Wed, 08 Sep 2010 20:47:49 GMT
            Call-ID: 80e4f50-9c7344ab-13c4-45026-41a-10aff3f4-41a
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow-Events: telephone-event
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Length: 0
    No.     Time        Source                Destination           Protocol Info
          3 0.071428    10.194.154.136        171.68.115.156        SIP/SDP  Status: 183 Session Progress, with session description
    Frame 3 (1109 bytes on wire, 1109 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 183 Session Progress
       Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41a-100875-517454db
            From: <sip:[email protected]:5060>;tag=82f4a00-9c7344ab-13c4-45026-41a-4ea64c5a-41a
            To: <sip:[email protected]:5060>;tag=48645D8-1175
            Date: Wed, 08 Sep 2010 20:47:49 GMT
            Call-ID: 80e4f50-9c7344ab-13c4-45026-41a-10aff3f4-41a
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
            Allow-Events: telephone-event
            Remote-Party-ID: <sip:[email protected]>;party=called;screen=no;privacy=off
                [Expert Info (Note/Undecoded): Unrecognised SIP header (Remote-Party-ID)]
                    [Message: Unrecognised SIP header (Remote-Party-ID)]
                    [Severity level: Note]
                    [Group: Undecoded]
            Contact: <sip:[email protected]:5060>
            Supported: sdp-anat
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Type: application/sdp
            Content-Disposition: session;handling=required
            Content-Length: 264
        Message Body
            Session Description Protocol
                Session Description Protocol Version (v): 0
                Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 8759 6996 IN IP4 10.194.154.136
                    Owner Username: CiscoSystemsSIP-GW-UserAgent
                    Session ID: 8759
                    Session Version: 6996
                    Owner Network Type: IN
                    Owner Address Type: IP4
                    Owner Address: 10.194.154.136
                Session Name (s): SIP Call
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Time Description, active time (t): 0 0
                    Session Start Time: 0
                    Session Stop Time: 0
                Media Description, name and address (m): audio 18710 RTP/AVP 18 101
                    Media Type: audio
                    Media Port: 18710
                    Media Protocol: RTP/AVP
                    Media Format: ITU-T G.729
                    Media Format: DynamicRTP-Type-101
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Media Attribute (a): rtpmap:18 G729/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 18
                    MIME Type: G729
                    Sample Rate: 8000
                Media Attribute (a): fmtp:18 annexb=no
                    Media Attribute Fieldname: fmtp
                    Media Format: 18 [G729]
                    Media format specific parameters: annexb=no
                Media Attribute (a): rtpmap:101 telephone-event/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 101
                   MIME Type: telephone-event
                    Sample Rate: 8000
                Media Attribute (a): fmtp:101 0-16
                    Media Attribute Fieldname: fmtp
                    Media Format: 101 [telephone-event]
                    Media format specific parameters: 0-16
    No.     Time        Source                Destination           Protocol Info
          4 0.089917    10.194.154.136        171.68.115.156        SIP/SDP  Status: 200 OK, with session description
    Frame 4 (1116 bytes on wire, 1116 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 200 OK
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41a-100875-517454db
            From: <sip:[email protected]:5060>;tag=82f4a00-9c7344ab-13c4-45026-41a-4ea64c5a-41a
            To: <sip:[email protected]:5060>;tag=48645D8-1175
            Date: Wed, 08 Sep 2010 20:47:49 GMT
            Call-ID: 80e4f50-9c7344ab-13c4-45026-41a-10aff3f4-41a
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
            Allow-Events: telephone-event
            Remote-Party-ID: <sip:[email protected]>;party=called;screen=no;privacy=off
                [Expert Info (Note/Undecoded): Unrecognised SIP header (Remote-Party-ID)]
                    [Message: Unrecognised SIP header (Remote-Party-ID)]
                    [Severity level: Note]
                    [Group: Undecoded]
            Contact: <sip:[email protected]:5060>
            Supported: replaces
            Supported: sdp-anat
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Type: application/sdp
            Content-Disposition: session;handling=required
            Content-Length: 264
        Message Body
            Session Description Protocol
                Session Description Protocol Version (v): 0
                Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 8759 6996 IN IP4 10.194.154.136
                    Owner Username: CiscoSystemsSIP-GW-UserAgent
                    Session ID: 8759
                    Session Version: 6996
                    Owner Network Type: IN
                    Owner Address Type: IP4
                    Owner Address: 10.194.154.136
                Session Name (s): SIP Call
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Time Description, active time (t): 0 0
                    Session Start Time: 0
                    Session Stop Time: 0
                Media Description, name and address (m): audio 18710 RTP/AVP 18 101
                    Media Type: audio
                    Media Port: 18710
                    Media Protocol: RTP/AVP
                    Media Format: ITU-T G.729
                    Media Format: DynamicRTP-Type-101
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Media Attribute (a): rtpmap:18 G729/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 18
                    MIME Type: G729
                    Sample Rate: 8000
                Media Attribute (a): fmtp:18 annexb=no
                    Media Attribute Fieldname: fmtp
                    Media Format: 18 [G729]
                    Media format specific parameters: annexb=no
                Media Attribute (a): rtpmap:101 telephone-event/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 101
                    MIME Type: telephone-event
                    Sample Rate: 8000
                Media Attribute (a): fmtp:101 0-16
                    Media Attribute Fieldname: fmtp
                    Media Format: 101 [telephone-event]
                    Media format specific parameters: 0-16
    No.     Time        Source                Destination           Protocol Info
         7 1.661867    10.194.154.136        171.68.115.156        SIP      Status: 100 Trying
    Frame 7 (469 bytes on wire, 469 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 100 Trying
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100eca-13593e22
            From: <sip:[email protected]:5060>;tag=82f4b98-9c7344ab-13c4-45026-41c-669825d-41c
            To: <sip:[email protected]:5060>
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5138-9c7344ab-13c4-45026-41c-3f6bfc7-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow-Events: telephone-event
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Length: 0
    No.     Time        Source                Destination           Protocol Info
          8 1.676056    10.194.154.136        171.68.115.156        SIP/SDP  Status: 183 Session Progress, with session description
    Frame 8 (1107 bytes on wire, 1107 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 183 Session Progress
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100eca-13593e22
            From: <sip:[email protected]:5060>;tag=82f4b98-9c7344ab-13c4-45026-41c-669825d-41c
            To: <sip:[email protected]:5060>;tag=4864C1C-10F8
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5138-9c7344ab-13c4-45026-41c-3f6bfc7-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
            Allow-Events: telephone-event
            Remote-Party-ID: <sip:[email protected]>;party=called;screen=no;privacy=off
                [Expert Info (Note/Undecoded): Unrecognised SIP header (Remote-Party-ID)]
                    [Message: Unrecognised SIP header (Remote-Party-ID)]
                    [Severity level: Note]
                    [Group: Undecoded]
            Contact: <sip:[email protected]:5060>
            Supported: sdp-anat
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Type: application/sdp
            Content-Disposition: session;handling=required
            Content-Length: 264
        Message Body
            Session Description Protocol
                Session Description Protocol Version (v): 0
                Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 7991 6854 IN IP4 10.194.154.136
                    Owner Username: CiscoSystemsSIP-GW-UserAgent
                    Session ID: 7991
                    Session Version: 6854
                    Owner Network Type: IN
                    Owner Address Type: IP4
                    Owner Address: 10.194.154.136
                Session Name (s): SIP Call
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Time Description, active time (t): 0 0
                    Session Start Time: 0
                    Session Stop Time: 0
                Media Description, name and address (m): audio 17660 RTP/AVP 18 101
                    Media Type: audio
                    Media Port: 17660
                    Media Protocol: RTP/AVP
                    Media Format: ITU-T G.729
                    Media Format: DynamicRTP-Type-101
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Media Attribute (a): rtpmap:18 G729/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 18
                    MIME Type: G729
                    Sample Rate: 8000
                Media Attribute (a): fmtp:18 annexb=no
                    Media Attribute Fieldname: fmtp
                    Media Format: 18 [G729]
                    Media format specific parameters: annexb=no
                Media Attribute (a): rtpmap:101 telephone-event/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 101
                    MIME Type: telephone-event
                    Sample Rate: 8000
                Media Attribute (a): fmtp:101 0-16
                    Media Attribute Fieldname: fmtp
                    Media Format: 101 [telephone-event]
                    Media format specific parameters: 0-16
    No.     Time        Source                Destination           Protocol Info
         10 1.700567    10.194.154.136        171.68.115.156        SIP      Status: 100 Trying
    Frame 10 (471 bytes on wire, 471 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 100 Trying
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100f04-2fde97a9
            From: <sip:[email protected]:5060>;tag=82f4d30-9c7344ab-13c4-45026-41c-5c20b753-41c
            To: <sip:[email protected]:5060>
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5320-9c7344ab-13c4-45026-41c-7fbe4865-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow-Events: telephone-event
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Length: 0
    No.     Time        Source                Destination           Protocol Info
         11 1.726376    10.194.154.136        171.68.115.156        SIP/SDP  Status: 200 OK, with session description
    Frame 11 (1114 bytes on wire, 1114 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 200 OK
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100eca-13593e22
            From: <sip:[email protected]:5060>;tag=82f4b98-9c7344ab-13c4-45026-41c-669825d-41c
            To: <sip:[email protected]:5060>;tag=4864C1C-10F8
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5138-9c7344ab-13c4-45026-41c-3f6bfc7-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
            Allow-Events: telephone-event
            Remote-Party-ID: <sip:[email protected]>;party=called;screen=no;privacy=off
                [Expert Info (Note/Undecoded): Unrecognised SIP header (Remote-Party-ID)]
                    [Message: Unrecognised SIP header (Remote-Party-ID)]
                    [Severity level: Note]
                    [Group: Undecoded]
            Contact: <sip:[email protected]:5060>
            Supported: replaces
            Supported: sdp-anat
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Type: application/sdp
            Content-Disposition: session;handling=required
            Content-Length: 264
        Message Body
            Session Description Protocol
                Session Description Protocol Version (v): 0
                Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 7991 6854 IN IP4 10.194.154.136
                    Owner Username: CiscoSystemsSIP-GW-UserAgent
                    Session ID: 7991
                    Session Version: 6854
                    Owner Network Type: IN
                    Owner Address Type: IP4
                    Owner Address: 10.194.154.136
                Session Name (s): SIP Call
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Time Description, active time (t): 0 0
                    Session Start Time: 0
                    Session Stop Time: 0
                Media Description, name and address (m): audio 17660 RTP/AVP 18 101
                    Media Type: audio
                    Media Port: 17660
                    Media Protocol: RTP/AVP
                    Media Format: ITU-T G.729
                    Media Format: DynamicRTP-Type-101
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Media Attribute (a): rtpmap:18 G729/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 18
                    MIME Type: G729
                    Sample Rate: 8000
                Media Attribute (a): fmtp:18 annexb=no
                    Media Attribute Fieldname: fmtp
                    Media Format: 18 [G729]
                    Media format specific parameters: annexb=no
                Media Attribute (a): rtpmap:101 telephone-event/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 101
                    MIME Type: telephone-event
                    Sample Rate: 8000
                Media Attribute (a): fmtp:101 0-16
                    Media Attribute Fieldname: fmtp
                    Media Format: 101 [telephone-event]
                    Media format specific parameters: 0-16
    No.     Time        Source                Destination           Protocol Info
         13 1.727645    10.194.154.136        171.68.115.156        SIP      Status: 500 Internal Server Error
    Frame 13 (526 bytes on wire, 526 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 500 Internal Server Error
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100f04-2fde97a9
            From: <sip:[email protected]:5060>;tag=82f4d30-9c7344ab-13c4-45026-41c-5c20b753-41c
            To: <sip:[email protected]:5060>;tag=4864C50-3C3
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5320-9c7344ab-13c4-45026-41c-7fbe4865-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow-Events: telephone-event
            Server: Cisco-SIPGateway/IOS-12.x
            Reason: Q.850;cause=44
                Reason Protocols: Q.850
                Cause: 44(0x2c)[Requested circuit/channel not available]
            Content-Length: 0
    Thanks!
    -John

    Since it appears you are a Cisco Employee, my recommendation is that you use the many internal resource available to you (including, but not limited to) , like TAC access, internal forums, team leaders, etc.
    This not to give the casual reader, the impression that the best source of support at Cisco is a customer's public forum.

  • Error during manuel entry/Change of condition.

    Dear friends,
    while I am trying to create standard customer order(VA01), I have faced an error message as: Item 00001:Error during manuel entry/Change of condition.
    Can anyone tell me solution?
    Thanks in advance.

    Hi,
    Goto to V/08 for your pricing procedure, check for the condition type if it is mandatory condition and / or if it is manual condition.
    In V/06, select condition type and check the value for Manual entry field
    Hope you get some inputs
    regards,
    Sagar

  • I'm getting an unknown communication error during my chat to initiate AIM screen sharing. Any clues as to why? Here's the comm log...

    I'm getting an unknown communication error during my chat to initiate AIM screen sharing. Any clues as to why? Here's the comm log...
    I don't usually have problems reaching and doing IT for my family. Is weird.
    Date/Time: 2015-04-12 11:46:01 -0400
    OS Version: 10.10.2 (Build 14C1514)
    Report Version: 4
    Messages Connection Log:
    2015-04-12 11:45:33 -0400: 0x7ffb826cc310: State change from No State to Invited.
    2015-04-12 11:45:45 -0400: 0x7ffb826cc310: State change from Invited to Connecting.
    2015-04-12 11:45:58 -0400: 0x7ffb826cc310: State change from Connecting to Ended.
    2015-04-12 11:45:58 -0400: 0x7ffb826cc310: Error -1 (An unknown error occurred.)
    Video Conference Error Report:
    Video Conference Support Report:
    7.728039 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:1973 type=2 (00000000/0)
    [Connection Data for call id: 1 returns 1
    18.955646 @/SourceCache/VideoConference/VideoConference-473/VCChannel/VCChannel.m:303 type=2 (00000000/0)
    [VCChannel prepareConnectionWithRemoteConnectionData - remote VCConnectionData: 1]
    18.964195 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:1988 type=2 (00000000/0)
    [Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
    18.966613 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2180 type=2 (00000000/0)
    [Initiate Conference To User: 1002 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
    25.205927 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:1973 type=2 (00000000/0)
    [Connection Data for call id: 3 returns 1
    31.603943 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:1988 type=2 (00000000/0)
    [Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
    31.604365 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2180 type=2 (00000000/0)
    [Initiate Conference To User: 1002 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
    Video Conference User Report:
    0.000000 @:0 type=5 (00000000/16402)
    [Local SIP port]
    18.964411 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2085 type=5 (00000000/0)
    [Remote Router]
    [BAD TEST]
    18.964419 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2087 type=5 (00000000/0)
    [Remote CommNAT Result: 0x00000001
    18.966640 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VideoConferenceGlobalObjects.m:1679 type=5 (00000000/0)
    [Router]
    [FULLCONE]
    18.966648 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VideoConferenceGlobalObjects.m:1681 type=5 (00000000/0)
    [CommNAT Result: 0x00000102
    31.604133 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2085 type=5 (00000000/0)
    [Remote Router]
    [BAD TEST]
    31.604144 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2087 type=5 (00000000/0)
    [Remote CommNAT Result: 0x00000001
    31.604370 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VideoConferenceGlobalObjects.m:1679 type=5 (00000000/0)
    [Router]
    [FULLCONE]
    31.604379 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VideoConferenceGlobalObjects.m:1681 type=5 (00000000/0)
    [CommNAT Result: 0x00000102

    Hi
    Ah a homehub.
    Set the Quicktime streaming setting, goto sys prefs/quicktime/streaming/streaming speed, set to 1.5mbps(
    In ichats prefs click on video and change bandwidth limit to NONE.
    Goto sys prefs/security/firewall and check "set access for specific........" and click the + at the bottom and add ichat to the list.
    Restart ichat.
    Also try connecting to me dfcom1 .mac account.
    Tony

  • Accounting error in service entry sheet

    Hi
             while posting service entry sheet i get error 147 Account determination for entry INT WRX not possible.
    I have maintained valuation class of service master in OBYC setting also.Can anybody help me out.
    Thnx

    Hi,
    Your question already answered. Don't ask multiple questions in one posting. If you have new questions start a new thread. Check  Rules
    https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement
    GR/IR Clearing account is a balance sheet account which act an interim account where the Invoice value is stored but we have not actually receive the Invoice. You should have separate Account Group, separate Field status group. Create
    G/L account GR/IR clearing & keep it post automatically and select as Balance sheet account.
    WRX Transaction key is used for GR/IR clearing in OBYC in account determination and you can have *separate GR/IR clearing- material, GR/IR clearing-asset and GR/IR clearing-service.
    Regards,
    Biju  K

  • Error in service entry sheet

    Hi All
    When am creating service enrty sheet in ML81N am getting the following error.
    ""147 Account determination for entry CAIN WRX not possible""
    With Rgds
    Chandra

    Hi,
    For SES, Use t.code: OBYC, enter Chart of account and click WRX,
    In next screen Click “Rules”
    Select the check box of Debit/Credit in accounts are determine based on TAB and save.
    Now again
    Use t.code: OBYC, enter Chart of account and click WRX,
    here only u have to enter  G/L accounts for Dr and Cr  & Save.
    Now try your transaction.
    Regards,
    Biju K

  • Posting related Error during Order Confirmation

    Dear Experts,
    I am from PP forum and had to post this in FI forum as i am getting an error message during process order confirmation after the goods posting is done thro backflush "Acct. 21701300 for trans./event key BSX, postable directly" .The error explanation says "the stock account determined automatically by the system is one that is directly postable. However, this stock posting can only be made to an automatically postable account. How to solve this please help.....
    Regards,
    Sunit

    Hi
    Stock account should be 'Post automatically only'. This option should be selected in the respective GL master in FS00.
    Change the GL 21701300 to post automatically only in FS00 or assign a different stock account in config - OBYC - BSX for the respective material valuation class
    Thank You,

  • WBS Commitment during service entry sheet

    Dear SAP Guru,
    I have one query related with punching of service entry sheet with reference to PO of proejct WBS.
    I have made one service PO with accnt.assignment category P and item category D, i have assigned one WBS element in account assignment tab.
    Now I am entering service entry sheet w.r.t. this service PO, the service entry is posted.Acceptance is still pending.
    so no accountng docs.is generated.
    Now I have made again One similar PO by taking the same WBS as taken is previous PO.
    While entering SES, System is allowing to punch the service entry sheet. Is this possible?
    Are there any committment created by SAP w.r.t WBS if we are entering SES with same WBS again and again?
    Is there any logic,report or transaction available in SAP?
    Regards,
    Ravi

    Hi,
    Please check the below links..
    Total Commitment Report for Cost Centres, WBS & Orders
    /thread/1393246 [original link is broken]
    http://help.sap.com/saphelp_ides/helpdata/en/fd/45af5d9d6411d189b60000e829fbbd/content.htm
    Hopt it may help you..
    Kuber

  • Run time error in Service entry sheet

    Hi Experts
    When I create a Service Purchase Order & when I enter a Service Entry sheet using ML81N, When I save it I am getting a run time error (Short dump has not been completely stored (too big) ).Could you please tell me how to overcome to this problem.
    AR
    Edited by: Amit  Rana on Jan 8, 2010 12:53 AM

    Hi Experts,
    The following error i am getting when i am doing the MIGO from PO.
    Runtime Errors MESSAGE_TYPE_X
    Date and Time 10.01.2010 10:09:56
    Short dump has not been completely stored (too big)
    Short text
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    Error analysis
    Short text of error message:
    No RFC destination is defined for SAP Global Trade Services
    Technical information about the message:
    Message classe...... "/SAPSLL/PLUGINR3"
    Number.............. 002
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Trigger Location of Runtime Error
    Program SAPLMBWL
    Include LMBWLU21
    Row 59
    Module type (FUNCTION)
    Module Name MB_POST_GOODS_MOVEMENT
    AR

  • Prepayment functionalitygives an error during Order Entry

    Hi all,
    We have oracle applications Suite - 11i (11.5.10.2) .
    At time of prepayment during Order Entry form, we are getting following error.
    _"Function not available to this responsibility. Change responsibilities or contact your system administrator" ._
    Following is the Navigation Path :
    Sales Order Entry > Query with existing SO > Others TAB > Select ACTIONS button > Select PAYMENTS option .
    Thanks
    Sanjay

    Sanjay,
    This is because the Function that is invoked when you select the Payments Action from Sales Order Screen has not been granted to your responsibility. The best way is to check the ONT_SUPER_USER menu in application Developer (this is the menu that is used by order Management super user), and see what all functions are there (manily the ones without prompts like 'Sales Orders: Print Payment Receipt'). ANd then compare the same with the menu that your responsibility is using (System Adminsitrator >> Security >> Responsibilities). I think you should get your answer. Please let me know.

  • Error in service entry sheet acceptance

    Hi SAP Gurus,
    The users are facing the following error while trying to approve the service entry sheet.
    Period 003/2009 is not open for account type S and G/L account XXXXXX. What is the problem and how can it be solved
    Thanks
    Anusha

    Hi
    In that case 4th period (January - check To period in OB52 for your company code) be opened for account types S (GL), M (material) k (Vendor) in FI point of veiw in integration to MM. And also check OMSY what is the MM posting period in open - is it 4th period. If January is not yet opened then open in MMPV. If everything is correct then post in 4th period. I dont think you are using back posting to previous period. If back posting is allowed then check in OMSY for mm posting period 3 is open or not and also OB52 (from period) 3rd period is open or not. If open post in 3rd period.
    Thanks
    Edited by: Praveen Raghavendra on Jan 16, 2009 6:06 PM

  • Have to cahnge G/L account in Servie PO after service entry sheet posting

    Hi 
    Could you help me with this ?
    “We have created service-order and reception have been made for service order .Now G/L Account was wrong and we want to cancel reception. We try to cancel reception in MIGO- and MBST –transaction, but we got error “Transaction code MBST (=> use transaction ML81/ML85) not defined”
    For transaction ML81 I don’t have authorization, ML85 I do. How should we cancel reception, when we are dealing with service orders (so that we can change right account)?”

    You cannot use MIGO or MBST for cancelling service entry sheet acceptance.
    You have to do so only in ML81N or ML85.
    In ML85, there is an option in the selection screen - whether you want to post acceptance or cancel acceptance. Select the correct option and you can cancel acceptance.
    Lakshman

Maybe you are looking for