Proxy calls are not permitted on IS

Hello,
I have implemented a scenerio between SAP AR -
XI --- SAP FCSM.
Now SAP and Xi are on same server but clients are different.
For SAP client is 110 for XI client is 100.
In sxmb_adm we have set SAP as application server and Xi as IS.
While testing this secerio i got a error as Proxy calls are not permitted on sender or receiver side on the IS (client)
If i check in sxmb_moni i found 2 messages one is sucessful and other one with error shown above.
can anyone help me out in this.
regards,
Vikrant

Hi Vikrant,
Need to be configure the Business Systems as the Local Integration Engine
In the respective application client, choose Exchange Infrastructure -> Administration -> Integration Engine u2013 Administration (SXMB_ADM) in the user menu.
2.Choose Integration Engine Configuration.
3. In the menu bar, choose Edit -> Change Global Configuration Data.
4.In the Global Configuration Data frame, choose Application System as the role of the business system.
5.In the Corresponding Integ. Server field, specify the HTTP destination that the business system uses to address the central Integration Server. Use the following syntax: dest://<HTTP Destination>
Specify the HTTP destination of the Integration Server that you created during the technical configuration of SAP Exchange Infrastructure.
regards
Ashwin
Edited by: ashwin dhakne on Mar 6, 2009 5:26 PM

Similar Messages

Calls are not getting thru in Cisco voice GW for a particular Number

Cisco gateway is connecte to a PBX with an Qsig interface, for a particualr destination number the calls are not gettin estabilished.
the output of the Q931 debug :
Aug 16 16:17:46.145: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x7E05
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98396
                Exclusive, Channel 22
        Facility i = 0x9FAA068001008201008B0100A16E0202070102011530650201010A010
1800101A111A00FA50D0A010212083530303035393938A211A00FA50D0A010212083530303035393
938A312801054454C45434F4D20574F524B524F4F4DA412801054454C45434F4D20574F524B524F4
F4DA50C06062B0C02FF373730020500
        Facility i = 0x9FAA068001008201008B0100A11D0202010002010080144E455453202
F204C4F4E472044495354414E4345
        Calling Party Number i = 0x2183, '8168911010'
                Plan:ISDN, Type:National
        Called Party Number i = 0x89, '18553808521'
                Plan:Private, Type:Unknown
        Sending Complete
Aug 16 16:17:46.149: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0xF
E05
        Channel ID i = 0xA98396
                Exclusive, Channel 22
Aug 16 16:17:55.709: ISDN Se0/0/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x
FE05
        Cause i = 0x80BF - Service/option not available, unspecified
Aug 16 16:17:55.741: ISDN Se0/0/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x7E0
5
Aug 16 16:17:55.741: ISDN Se0/0/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref =
0xFE05
The Qsig and dial-peer configration :
interface Serial0/0/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn overlap-receiving
isdn incoming-voice voice
isdn send-alerting
no cdp enable
dial-peer voice 1 voip
description To CBTS GK
destination-pattern +1T
signaling forward rawmsg
session protocol sipv2
session target ipv4:10.9.5.10
session transport tcp
voice-class codec 1
dtmf-relay rtp-nte
no vad
interface Serial0/0/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn overlap-receiving
isdn incoming-voice voice
isdn send-alerting
no cdp enable
dial-peer voice 1 voip
description To CBTS GK
destination-pattern +1T
signaling forward rawmsg
session protocol sipv2
session target ipv4:10.9.5.10
session transport tcp
voice-class codec 1
dtmf-relay rtp-nte
no vad

Hi Raj,
My name is Edson Pineiro, I understand that your problem description is in regards to failed incoming calls from a qsig trunk.
According to the received q931 setup message I can see the called party number is 18553808521 and as so the gateway should route the dnis based on the best match in destination-pattern. My first suggestion would be to ensure your outgoing dial-peers has a matching destination-pattern that matches the dialed number, for example:
dial-peer voice 1 voip
destination-pattern 1T
The T is a wild card for any digit any length
Or you can be very specific.
dial-peer voice 1 voip
destinaton-pattern 18553808521
The next suggestion would be to ensure that your incoming pots dial-peers contains 'direct-inward dial'. This is so that you don't receive secondary dial tone when dialing in, which I don't think is happening here.
Another suggestion would be to remove 'isdn overlap-receiving' from interface serial 0/0/0:23. Reason being is that the DNIS received is enbloc and not overlapping. You can clearly see that the complete e164 number is received within the setup and no further digits are needed.
But overall the disconnect cause code is 0x80BF the 80 portion is related to the source of the disconnect which is the router and BF "Service/option not available, unspecified" which is described as:
The network or remote equipment cannot provide the service option that the user requests, due to an unspecified reason. A subscription problem can cause this issue.
Any ways seems like the router does not support the protocol or type of message included in the Setup. After decoding one of the facility message:
        Facility i = 0x9FAA068001008201008B0100A16E0202070102011530650201010A010
1800101A111A00FA50D0A010212083530303035393938A211A00FA50D0A010212083530303035393
938A312801054454C45434F4D20574F524B524F4F4DA412801054454C45434F4D20574F524B524F4
F4DA50C06062B0C02FF373730020500
decode -->
Facility IE first byte (protocol profile): 0x9f(Network Extentions), depends on Network Protocol Profile
**Note:
**0x91/0x9f both be used by older qsig spec, including:
**ISO 11582:1995, ETSI 300 239:1993/1995
**newer qsig spec use 0x9f only, including:
**ISO 11582:1995/Cor.1:1999, ECMA 165(4th), ETSI 300 239:2003
**see CSCeb58118 for CCM compatibility issue
NetworkFacilityExtension ::= {
sourceEntity: 0
destinationEntity: 0
NetworkProtocolProfile not present
APDU is a ROSE
0
DivertingLegInformation2Invoke ::= {
invokeID: 1793
operationValue: 21
argument: DivertingLegInformation2Arg ::= {
diversionCounter: 1
diversionReason: 1
originalDiversionReason: 1
divertingNr: PrivatePartyNumber ::= {
privateTypeOfNumber: 2
privateNumberDigits: 50005998
originalCalledNr: PrivatePartyNumber ::= {
privateTypeOfNumber: 2
privateNumberDigits: 50005998
redirectingName: 54 45 4C 45 43 4F 4D 20 57 4F 52 4B 52 4F 4F 4D
originalCalledName: 54 45 4C 45 43 4F 4D 20 57 4F 52 4B 52 4F 4F 4D
Looks like this is a redirected call (call forward or transfer), the redireted number is "50005998" and the other end of the PRI maybe attempting to do either a 2 B channel transfer or B channel optimization, which is not supported certain gateways or needs the use of a tcl scripts. Any ways is it possible to confirm if such features are enabled on the other end of the qsig trunk? and what the number 50005998 is assigned too. This may warrant a TAC case.
However please ensure your carry through the first three configuration changes before looking at the possible bad facility message.
Here are some good documents on ISDN, IOS dial-peers and call legs:
Understanding debug isdn q931 Disconnect Cause Codes
http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a008012e95f.shtml
Configuring Telephony Call-Redirect Features
Two B-Channel Transfer
http://www.cisco.com/en/US/docs/ios/voice/ivr/pre12.3_14_t/configuration/guide/ivrapp.pdf
Understanding Dial Peers and Call Legs on Cisco IOS Platforms
http://www.cisco.com/en/US/partner/tech/tk652/tk90/technologies_tech_note09186a008010ae1c.shtml
Understanding Direct-Inward-Dial (DID) on IOS Voice Digital (T1/E1) Interfaces
http://www.cisco.com/en/US/partner/tech/tk652/tk653/technologies_tech_note09186a00801142f8.shtml
Understanding Inbound and Outbound Dial Peers Matching on IOS Platforms
http://www.cisco.com/en/US/partner/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml#prereq
Voice Translation Rules
http://www.cisco.com/en/US/partner/tech/tk652/tk90/technologies_tech_note09186a0080325e8e.shtml
Let me know how you go.
Thanks again for asking the tuff questions.
Cheers
Edson

Postings to G/L accounts with open item management are not permitted Messag

HI All,
Me activiated New GL. and when I am trying to post the
document, I am getting the below error.
The GL used 200100 is Cash A/c (40)
Cr Eq Share Capital A/c (50)
As Cash A/c requires Clearing, I have activated "Open Item Management".
Can you advice me why Its giving me the below mentioned error.
Thanks
Postings to G/L accounts with open item management are not permitted
Message no. FAGL_POST_SERVICE012
Diagnosis
You use G/L account 200100 in company code RLIF with open item
management. However, postings are not permitted to G/L accounts in
individual ledgers with open item management.
Procedure
If you have not yet made any postings to this account and if the
account is to be used for closing processes in non-leading ledgers,
deactivate the Open Item Management indicator in the company code data
for the G/L account.
Thanks,
Niranjan Yandamuri

Hi,
Please, refer to note 1646466 for the info on this message.
Regards,
Eli

Decimal Places are not Permitted for Chile Country

Hi All,
In OVA8 settings for Chile country at the field max.doc value, i am not able to use the decimals. getting error message as Decimlas are not permitted (Message no - 00011). checked OY04 - there is no decimals for Chile currency. checked - OY01 Dec.Pt. format as 1.234.567,89
For Argentina, Peru and Uruguay same settings has been done and i am able to save the decimal points in OVA8 at the field max.doc value.
Please let me know if there is any specifis settings for Chile or SAP NOTE
Thanks,
Mahesh

HI,
just looking at a brand-new ECC60 / EhP4 system where nobody changed OY04 settings.
I can find CLP (Chilean Peso) in the list with ' ' decimal places, so thats why there are no decimal places allowed.
Check again OY04, if you find an entry for CLP and NOTHING is maintained it means that ZERO dec. places are allowed.
If you find an entry in OY04 with a number of decimal places >0 than this decimal places are allowed.
If there is NO entry for a given currency then its used with 2 decimal places (SAP standard).
So OY04 is only for the currencies that should be treated different as SAP standard.
Best regards, Christian
Edited by: Christian Ortner on Feb 3, 2011 5:09 PM

Error: Reason codes with automatic charge-off are not permitted here(F-28)

Hi All
I creted a reason code in obxl t-code and assigned a gl code in OBXL transaction code, But when I am trying to clear a payment with reason code in F-28, System is throwing the following error..Can some one tell me why i am getting this error?
Reason codes with automatic charge-off are not permitted here
Message no. F5605
Diagnosis
The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose. Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
System Response
The reason code entered is not accepted.
Procedure
You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.

Hi Venkata,
It seems while entering the payment (partial payment / residual items) ... you are clearing multiple items with differences. (e.g. if the difference amount is $30, then may the difference consists of two invoices underpaid by $15 each). In this scenario, F-28 doesn't know which additional account assignment fields should be picked up ... hence the error.
First of all, to validate that this indeed is the case, try clearing a payment with the same reason code where difference can be attributed to a single invoice. If you still get an error, then there is some other problem.
Then, to take care of a the business scenario where the difference can indeed be due to multiple documents, select "charge off difference" option and create an entry to post the difference as necessary.
HTH,
Manish Patel
Sr. SAP Solutions Consultant

I updated my Iphone4S this week to the newest IOS 7.1 and now everyone who calls me says the calls are not clear, muffled. Is there something I can do to clear this? 4 people in 4 different states that called me all said the same thing.

I updated my Iphone4S this week to the newest IOS 7.1 and now everyone who calls me says the calls are not clear, muffled. Is there something I can do to clear this? 4 people in 4 different states that called me all said the same thing.

Settings > General > Reset > Reset Network Settings
Contact the carrier to troubleshoot.

Postings to G/L accounts with open item management are not permitted

Dear all,
i am getting one error FB01L ledger specific posting for ledger group L2 ledger (IFRS) error is "postingst o GL accounts with open item management are not permitted " i am posting both gl accounts are balance sheet account, please help me how to resolve the problem .
Message no. FAGL_POST_SERVICE012
Reregards
rajashekhar

Dear all,
Thanks for reply, The error message appears FAGL_POST_SERVICE012 because it is generally not permitted to use the O/I managed account as an adjustment account.It is not possible to post on Individual Ledger (on a Leading or non-leading) on OI Account. This is for your informations
We want to post ledger specific for L2 ledger i am getting above error can help me how to sovle the problem , otherwise any alternaitve solution for posting L2 Ledger

Posting to gl a/c with open item management are not permitted.

hello,
When i run FAGL_FC_VAL it display the report and generate the batch input session.
But when i run the session the error massage appear -
"posting to gl a/c with open item management are not permitted."
When i post the same gl mannually, it doesn't show any error.
The Same Problem appear when i run the session generated from FAGLF101- the regrouping program.
Can any body give some idea, what should be done.
Thanx
Subodh

Hello this is chandu,
When u run the fc val it posts the ex gain or loss to respective a/cs.Means those a/cs are not B/S a/cs.Only B/S a/cs we select open item management which r require to maintain on OI management basis.
So try to maintain other a/cs for ex gain and loss y bcoz once u post any transaction in those a/cs which r created already on O Item mgnt basis u cannot change that again.
Then assign those a/cs to automatic postings and run the rc val again
May it will be useful to u
Thank u

FB50L error: Postings to G/L accounts with open item management are not permitted

Dear All
I need your help.
I am trying to do some adjustment to GR/IR clearing account in Non-leading ledger. Since for this account open item management is ticked, I am getting an error message 'Postings to G/L accounts with open item management are not permitted'.
Now I have checked the forum to find some solution...but does not fit my requirement.
I cannot create a new account. I cannot change the existing account. I tried OBA5, but the message persists.
I also checked the notes.
Appreciate a response on how the post to open item managed accounts in non-leading ledger.
Regards
Kunaal

Hi Kunaal
Usually, OIM accounts are not allowed for Non Leading Ledger postings... With EhP4 or 5, i guess, a new feature is added in GL Master whereby you can specify that a GL will be OIM for Leading Ledger and Not OIM for a Non Leading Ledger
Regards
Kavita Agarwal

Postings to G/L accounts with open item management are not permitted in ASKB

Hi Gurus,
I have the error FAGL_POST_SERVICE012 'Postings to G/L accounts with open item management are not permitted' when i run the transaction ASKB. The very strange thing is that in table APERB_ITEMS for this company code there isn't any record. My questions are:
1. The ASKB posts only if the APERB_ITEMS is populated?
2. If yes, Why the ASKB wants to create postings on this company code?
3. If no, which are the logic conditions that include a asset in the ASKB execution?
4. If the logic is correct, how i can to run the ASKB on OI accounts?
Thanks in advance,
Best Regards,
Emanuele

Hi ,
I believe you know why do you run transaction code ASKB if not please see below
The report evaluates all asset transactions since the last run. Unlike the periodic depreciation posting program, the APC posting run is not tied to a certain accounting period. It generates one document per posting period and depreciation area. That means that asset values are summarized for various account groups in one document. Document number assignment is external. You have to enter the document type in Customizing for Asset Accounting.
There are various possible ways of posting APC values:
To an account set within the original company code
To an account set of an alternative company code
To an account set directly in a special ledger
The account set can be determined from a different depreciation area.
Derived depreciation areas can be treated as real depreciation areas. This means that the system posts APC differences rather than special reserves, as was the case up to now.
During a test run, the system completes all accounting checks (for example, budgetary control of objects belonging to Funds Management).
While doing above system reads and update table APERB_ITEMS . If you look to Program for ASKB is RAPERB2000 and if you take your ABAper help to under the coding he will tell you that is program use APERB_ITEMS to update and read.
MANY THANKS
REGARDS
Preeti Agarwal

Down pmnts with taxes are not permitted when processing with jur.code (Message no. FS206)

Hi Guys,
I am facing very critical issue on down Payment request, to process with saperate Tax Value.
We are supporting on Roll-out for Germany. We have implemented all standard SAP processes in the Project. We have also implemented many interfaces and one of the Interface is Sabrix Tax Engine (Tax Jurisdiction Code).
As per the Germany legal requirement, the Tax has to get calculated whenever the funds gets transfered from one Bank Account to Another Bank Account.
Coming to the issue: In the Customer Down Payment scenario, we are creating the Down payment request for Customer and as per Germany local requirement the Tax of 19% has to get calculated on Down payment.
For an Example: We have the Sales Order Contract Value of 100,000.00 EUR and we are creating the Down Payment reqeust of 10% which is 10000 EUR + Tax 19% 1900 EUR.
We are trying to post the Down Payment request in F-37 and we get the issue "Down pmnts with taxes are not permitted when processing with jur.code". This error is appearing due to Sabrix Tax engine (Tax Jurisdiction Code) has implemented in our System.
We have gone through the SAP notes 97288 and 213567 and understood that the Standard SAP does not support us to post the Down Payment request with Separate Tax Value, when the External Tax Engine has implemented.
I request you to suggest me, if you have already seen this issue in any of your Projects and fixed through the work-around solution. We have been working on work-around since 2 weeks, however no result.
Below is the error message:
Down pmnts with taxes are not permitted when processing with jur.code
Message no. FS206

HI Preeti,
Thanks for your response. We have already seen the similar SAP notes and the SAP notes explains that the "Down pmnts with taxes cannot be done along with with jur.code". The only solution is to post the DP without Tax.
However there might be some workaround which can be done in SAP, to process the Down Payment/Advance Payments with Tax Value along with Jurisdiction Code. I would like to know this.
Did any one seen this case in your experiece, if yes, what is the work-around solution?.
Need your help guys!,...
Regards,
Damodar Naidu

Missed calls and placed calls are not saving in 7942 phone

HI
i am facing some issue in telephone directory, in my phone missed calls and placed calls are not saving. i am using cisco call manager and 7942 phone. please help me in this issue.
Thanks
Shijo

Hi Shijo,
Is this affecting only one 7942 IP phone or all of them? if this is affecting all then you may try ta firmware upgrade. If this is only affecting one of them then you can compare the settings of this phone with the working ones or try setting the phone to factory defaults.
HTH
Manish

Decimal places are not permitted for asset useful life

Dear SAP experts,
I need to post a new net book value on a new depreciation area 50 for fixed assets. The new deprecation for depreciation area 50 will start in July 2011 on all existing (also fully depreciated or to be disposed) assets with a different useful life unlike the book deprecation for depreciation area 01. The depreciation method for depreciation area 50 is straight line.
I have a requirement to assign the new useful life for the depreciation area 50 which may contain decimals, for example 5.5 years. Basically, I need to depreciate the asset for the remaining 6 months of 2011 and the entire 2012 to 2016.
SAP does not allow decimals on asset useful life (Decimal places are not permitted, Message no. 00011).
Have you come accross a similar situation? How can that be managed via depreciation methods and keys?
Please advise.
Thank you in advance,
Inna

Hi Inna,
You can define your useful life of 5.5 years for the depreciation area 50 as follows:
Useful life : 5
period : 6
here, useful life(5) represents 5 years and period(6) as 6 months which gives you 5.5 years starting depreciation from Depreciation calculation start date.
Kind Regards,
Mehul

Error: Common entries are not permitted for plan queries and input queries

Hi,
I have a 2 selections in the column struct:
1. year = 2005, version = actual
2. year = 2006, version = plan, marked as data can be changed using user entry or planning function
row has posting periods from 1-12
in the workbook I have inserted this query in the workbook in analysis grid. it runs good.
now i added a button and assigned planning function to it. this planning function copies 2005, actuals to 2006, plan.
when i execute the workbook and hit this button, it gives me following error:
"Common entries are not permitted for plan queries and input queries"
please can anyone provide me assistance with this issue.
thanks,
sam

when i go to diagnosis it displays following:
Diagnosis
InfoProvider ZIP_PLAN2 must be described in this application by both a plan query and by a input-ready query, which is directly defined on the InfoProvider ZIP_PLAN2.
System Response
This is not permitted.

Cross-client customizing are not permitted

Hi,
I am trying to remove "Transformation Object" in BI 7.0, QA server, and it not allowe to me access, I have SAP_ALL access
I am getting this error messages:
"changes to repository or cross-client customizing are not permitted"
I know we can't change anyitng in QA its goes through Transport, but the problem is DEV system this objects didn't show and QA this objects shows, so I want to remove this bi object from QA system
I know while installation NW 2004s its post installation steps to not change objects
in SE06 I am trying to change these objects to modifible but still not allow to changeable
please help me out

Hi Angeline,
In transaction SCC4 double click the client on which you are working. There will be a setting "Changes to repository or cross-client customizing are not permitted." Modify this option to "Automatic recording of changes."
Making that will allow you to delete the object.
Make sure after you achieve your desired objective, you revert back the client settings to "Changes to repository or cross-client customizing are not permitted." Also revert back the settings in SE06 in QA to the original what you had in post installation.
Regards
Sourabh Majumdar

Proxy calls are not permitted on IS

Similar Messages

Maybe you are looking for