"Access not allowed for subject: principals=[]" Common Issue with no Repose

Hi all,
When upgrading from 8.1 to 8.1 SP4 (we have seen the issue as early as SP2), there is an exception thrown when trying to start the server where our application is deployed:
<pre>weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: Application Action: write, Target: Deployed
</pre>
Our application creates an InitialContext using properties from a standard properties file, and when the "java.naming.security.principal" and "java.naming.security.credentials" properties are omitted, the server will start and deploy the application, but it naturally will not work.
I have noticed that this issue has been brought up by several others:
http://forums.bea.com/bea/search.jspa?q=%22Access+not+allowed+for+subject%3A+principals%3D%5B%5D%22&objID=&dateRange=all&userID=&numResults=15
http://forums.bea.com/bea/thread.jspa?forumID=2058&threadID=200027601&messageID=200619947#200619947
http://forums.bea.com/bea/thread.jspa?forumID=2051&threadID=200021662&messageID=200590642#200590642
http://forums.bea.com/bea/message.jspa?messageID=200590569&tstart=0
But have seen nothing resembling even a hint of a cause.
Any suggestions that even get me going in the right direction would be appreciated.
<pre>
weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: Application Action: write, Target: Deployed
     at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:623)
     at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:510)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:398)
     at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:430)
     at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:387)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:741)
     at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
     at weblogic.management.configuration.ApplicationMBean_Stub.setDeployed(ApplicationMBean_Stub.java:408)
     at weblogic.management.mbeans.custom.ApplicationManager.setState(ApplicationManager.java:593)
     at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:740)
     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:501)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
     at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
     at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
     at weblogic.management.configuration.ApplicationManagerMBean_Stub.start(ApplicationManagerMBean_Stub.java:677)
     at weblogic.management.Admin.startApplicationManager(Admin.java:2821)
     at weblogic.management.AdminServerAdmin.startApplicationManager(AdminServerAdmin.java:624)
     at weblogic.management.Admin.finish(Admin.java:2299)
     at weblogic.management.AdminServerAdmin.finish(AdminServerAdmin.java:458)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:971)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
     at weblogic.Server.main(Server.java:32)
</pre>

For others who have received this error, I'll post what I think has turned out to be the cause.
Refer to
http://e-docs.bea.com/wls/docs81/jndi/jndi.html#471919
Which says:
=====
When you create a JNDI Context with a username and password, you associate a user with a thread. When the Context is created, the user is pushed onto the context stack associated with the thread. Before starting a new Context on the thread, you must close the first Context so that the first user is no longer associated with the thread. Otherwise, users are pushed down in the stack each time a new context created. This is not an efficient use of resources and may result in the incorrect user being returned by ctx.lookup() calls.
=====
Our application caches the Context created, and that Context is used by other objects to perform lookups. Prior to Sp2, this caused no issues when including the username and password as part of the properties passed to the InitialContext constructor.
I presume that closing the Context after it has been used would be the proper fix for this, but right now this Context is used in too many places once it is created. I was able to combat the issue by removing the username and password properties (java.naming.security.principal & java.naming.security.credentials) from the properties file. It seems to work as expected.

Similar Messages

With out goods issue for order system should not allow for order confirmati

Dear all
with out goods issue system should not allow for order/operation confirmation.
how it is possible.
Regrads
Srinivas

Dear ,
In some cases we required to do confirmation or TECO without GI .
We can change it as per req using user exit
Regards,
Ishwar

Payment method(s) are not allowed for this program / Program RFFOAVIS_FPAYM

Dear Friends,
In Se38 abap editor, I entered the program RFFOM100, i entered the details program run date,identification future,paying company code,payment methods T, House bank, Account Id and executed the program. I am getting the error 'Payment method(s) are not allowed for this program'.
Payment method S is not used in F110, It was not mentioned in vendor master or vendor invoice.It is not mentioned in fbzp in bank determination. When i tried to delete payment method 'S' the system shows a message Payment Method S is being used in the company code.
In the program RFFOAVIS_FPAYM, i entered the details program run date,identification future,paying company code,payment methods T, House bank, Account Id and executed the program. I am getting the error 'Program RFFOAVIS_FPAYM: No records selected'. But there open items or invoices.
Please suggest how to resolve the errors.
Regards
Sridhar

Hello,
Why are you directly executing these programs?
You will not expect these program to execute directly by going to SE38.
I would have configured the relevant payment methods in the country with DME structure or classical RFFO* programs, which in turn pick up the inherent programs at the time of running F110.
For example, if you need to generate BACS file for country GB, either you copy the GB_BACS to ZGB_BACS or use GB_BACS directly in FBZP settings.
Make sure that you have maintained OBPM1 / OBPM2 / OBPM3 and OBPM4 settings properly.
The system automatically gives the access to system RFFOAVIS_FPAYM. Prepare a variant against this program in F110. Relevant file gets generated to folder path mentioned in OBPM4 will get generated. The file get generated can be seen in AL11.
Hope this is informative and solves your issue.
Regards,
Ravi

ESS Business Package Error: Period type not allowed for profile ESS

Hi,
We are trying to configure the business package for Employee Self Service on Enterprise Portal 6.0. We followed this SDN contribution <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a">ESS doc guide</a>
So far we have successfully deployed the business packages and followed all the configurations that were pointed out in the doc guide. Unfortunately when we try to access the Employee Self-Service portal pages (Overview, Employee Search, etc), we encounter this error:
Critical Error:
Period type not allowed for profile ESS, error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Period type not allowed for profile ESS, error key: RFC_ERROR_SYSTEM_FAILURE
Any ideas on how to fix this issue?
Regards,
Jojo

Hi Jojo,
Have you solved the problem? If yes can you please help me even I am facing the same error.
this is very help full to me .
Thanks and Regards,
Shilpi.

SQLException: Access not allowed (problem with ACL)

Hi, I'm getting the following error when I start my Weblogic (7.0) server.
java.sql.SQLException: weblogic.common.ResourceException: Access not allowed
I followed these steps to Provide the necessary ACl permisiions:
1. Compatibility Security => ACLs
Create a new ACL:
name : weblogic.jdbc.connectionPool.yourPoolname
permission : admin
group : Administrators
2. Create a new Connection Pool:
ACL Name : weblogic.jdbc.connectionPool.yourPoolname
In 'Target' tab, choose server and click the Apply button.
I even checked fileRealm.properties, the user admin123 (the user name with which I start the server), is included in all the connectionpool ACL lists. I restarted the server to pick the new changes but it still gives the same errors.
Please help,
Thanks

You need to create the correct ACL for the DataSource following this procedure in the Administration Console:
1. Compatibility Security => ACLs
Create a new ACL:
name : weblogic.jdbc.connectionPool.yourPoolname
permission : admin
group : Administrators
2. Compatibility => click Refresh button
3. Services => JDBC => Connection Pool
Create a new Connection Pool:
ACL Name : weblogic.jdbc.connectionPool.yourPoolname
In 'Target' tab, choose server and click the Apply button.
4. Services => JDBC => Data Sources
You can create a new Data Source using this connection pool successfully
Regards,
Prasanna Yalam

BB Pearl 8130 "access not allowed!" when trying to download Blackberry App World

Hi, well I am trying to download blackberry app world onto my blackberry pearl 8130 and whenever I try to download it it goes through the language prompts but then goes to a page with "access not allowed" My device software is v4.5, I am currently in Canada, I have the data plan, I can use the internet browser and my carrier is Telus. All help is appreciated, please and thank you!

Hi and Welcome to the Forums!
"Access Not Allowed"? Is that the precise and exact message? If not, please do provide the precise message.
Please check this page to ensure you meet the minimum requirements (including if it is available in your country):
http://na.blackberry.com/eng/services/appworld/download.jsp
If it is available in your country and you feel you meet the device-level system requirements, then contact your carrier to ensure that you meet the service plan (from them) requirements for access (via their network) to AppWorld. Generic data plans, even unlimited, are usually not sufficient...a specific BB data plan is normally required.
Lastly, do be aware that AppWorld is merely a portal, vending apps developed mainly by others. As such, it is not your exclusive procurement source -- there are others that you can try (e.g., Handango, Handmark, BPlay, GetJAR or Mobihand). I have found that there are very few apps that are exclusive to AppWorld. You can search the on-line catalog and then search out other procurement sources, including quite often the developer website itself.
Good luck!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

ResourceException: Access not allowed (when trying to grab a connection from weblogic pool)

I am using WLS7 with SP1.
I just recently migrated from WLS6.0. When my code tries to grab a
connection from the pool, it throws an exception
java.sql.SQLException: Pool connect failed:
weblogic.common.ResourceException: Access not allowed
at weblogic.jdbc.pool.Driver.connect(Driver.java:202)
Does anyone know if anything changed from 6.0 to 7?
Here is a piece of the code that throws exception.
Driver driver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver")
.newInstance();
conn = driver.connect("jdbc:weblogic:pool:" +
dbName, null);
Thanks in advance.

Hi Jung,
"Jung Yang" <[email protected]> wrote in message
news:[email protected]...
Do you know how to change security setting on the connection pool?
Thanks.WebConsole:
1.Compatibility Security => ACLs
Create a new ACL,
name : weblogic.jdbc.connectionPool.yourPoolname
permission : reserve, reset
group : everynone
2.Services => JDBC => Connection Pool
Create a new Connection Pool
ACL Name : weblogic.jdbc.connectionPool.yourPoolname
In 'Target' tab, choose server and click the Apply button
Slava
>
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Jung,
Could you try providing weblogic user name and password
in the properties?
Could you also check security setting of the connection pool?
Regards,
Slava Imeshev
"Jung Yang" <[email protected]> wrote in message
news:[email protected]...
Well that is exactly what I am doing. The variable dbName is database
connection pool name that I created in weblogic console. Again, it
worked
in WLS6 but after migration, it stopped working.
Thanks.
"Mitesh Patel" <[email protected]> wrote in message
news:[email protected]...
In my code I am supplying name of the connection pool already
created
in
weblogic server. I am asking you to get connection from the pool
using
pool
driver.
In your case you are trying to create connection straight to
database
using pool
driver.
What I am asking is pass name of the connection pool instead of
database
name.
Thanks,
Mitesh
Jung Yang wrote:
What would be the difference between your code and mine? Mine
simple
appends dbName string value for connection pool name at the end of
"jdbc:weblogic:pool:"? And why same exact code would work in WLS6and
not
work in WLS7?
Thanks.
"Mitesh Patel" <[email protected]> wrote in message
news:[email protected]...
conn = driver.connect("jdbc:weblogic:pool:" +
dbName, null);Instead of doing this what if you use
Connection conn =
myDriver.connect("jdbc:weblogic:pool:myConnectionPool", null);
Will you please try this and see if that helps?
Mitesh
Jung Yang wrote:
Isn't that exactly what I posted for my code piece?
Thanks.
"Mitesh Patel" <[email protected]> wrote in message
news:[email protected]...
Try As described below:
The following example demonstrates how to use a database
connection
pool
from a servlet.
Load the pool driver and cast it to java.sql.Driver. The
full
pathname
of
the driver is weblogic.jdbc.pool.Driver. For example:
Driver myDriver = (Driver)
Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Create a connection using the URL for the driver, plus
(optionally)
the
name of the registered connection pool. The URL of the pool
driver
is
jdbc:weblogic:pool.
You can identify the pool in either of two ways:
Specify the name of the connection pool in a
java.util.Properties
object
using the key connectionPoolID. For example:
Properties props = new
Properties();props.put("connectionPoolID",
"myConnectionPool");Connection conn =
myDriver.connect("jdbc:weblogic:pool", props);
Add the name of the pool to the end of the URL. In this case
you
do
not
need a Properties object unless you are setting a username
and
password
for using a connection from the pool. For example:
Connection conn =
myDriver.connect("jdbc:weblogic:pool:myConnectionPool",
null);
Note that the Driver.connect() method is used in theseexamples
instead of
the DriverManger.getConnection() method. Although you may
use
DriverManger.getConnection() to obtain a databaseconnection,
we
recommend
that you use Driver.connect() because this method is not
synchronized
and
provides better performance.
Note that the Connection returned by connect() is an
instance
of
weblogic.jdbc.pool.Connection.
Call the close() method on the Connection object when youfinish
with
your
JDBC calls, so that the connection is properly returned to
the
pool. A
good coding practice is to create the connection in a try
block
and
then
close the connection in a finally block, to make sure the
connection
is
closed in all cases.
conn.close();
Mitesh
Jung Yang wrote:
I am using WLS7 with SP1.
I just recently migrated from WLS6.0. When my code tries
to
grab a
connection from the pool, it throws an exception
java.sql.SQLException: Pool connect failed:
weblogic.common.ResourceException: Access not allowed
at
weblogic.jdbc.pool.Driver.connect(Driver.java:202)
Does anyone know if anything changed from 6.0 to 7?
Here is a piece of the code that throws exception.
Driver driver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver")
.newInstance();
conn =
driver.connect("jdbc:weblogic:pool:"
+
dbName,
null);
>>>>>>>>>
Thanks in advance.

Limit PO Err Combination of GR/IR control not allowed for external services

Hi,
I am having a problem while replicating free text Limit PO's to R/3 in SRM 4.0 SP 13. The issue is while creating Free Text Limit SC with the "Confirmation and Invoice" option checked in, the PO's get created in SRM but fails while replicating to R/3 and in RZ20 errors as "Combination of GR/IR control not allowed for external services" although in vendor master i don't have check for the field "GR-Based Invoice Verification".
On the contrary while creating SC with the "Invoice Only" the PO is successfully replicated to R/3 with item category as B for limit orders.
Now i have noticed if i make changes in the vendor master data i.e. check the flag "GR-Based Invoice Verification" then the PO in my first scenario gets replicated successfully and also with respect to the second scenario but it gets replicated in both the scenarios as item category "D".
As far as SRM standard it should have ideally behave like the below:
Limit SC with GR AND Invoice -> item category D
Limit SC with invoice only -> item category B.
Now my question is why do my PO's fail in R/3 in the first scenario and also if i check the flag in vendor master for GR-Based Invoice verification then in the second scenario the item category is "D" instead of "B".
Thanks in Advance.
Best Regards
Anirban

Hi Georg,
We don't have any active implementation for the BADI BBP_PO_INBOUND_BADI.
Best Regards,
Anirban

Limit PO :Combination of GR/IR is not allowed for external services

Hi,
we are working in SRM40 sp09 & back end ECC.50
In the Limit PO:
we are able to create Limit PO from a shopping cart.The follow on documents in ECC, it is creating a PO with Item category "B" and the "invoices" are only possible.
The Issue:
The Client wants the Confirmation/GR functionality to be enabled and the Invoices.
but for Limit PO, with follow on documents--"Confirmation" is checked, we have a error messagecombination of GR/IR is not allowed for external services".
Is there any addition configuration or steps involved.
Thanks and Regards,
RK.

Hi
<b>Please go through the links below, which address the same issue -></b>
Limit PO(Item category D instead of B)
SRM: Item category B/D for limit PO
Re: Problem with Unknown account assignment with limit order...reply soon...
Do let me know.
Regards
- Atul

Set type COMM_PR_UNIT is not allowed for product type

Hello all, I am working in SRM 7.0 and when I try to replicate service master (DNL_CUST_SRVMAS) I have this error:
Set type COMM_PR_UNIT is not allowed for product type
What can I do? I think that is an ABAP problem
Thanks in advance
Rosa Rodríguez

Rosa,
This note is something different and nothing to do with the issue. Can you share how did you resolve the DNL_CUST_SRVMAS issue? We are also getting same error.
Thanks,
Jagadish

Java.sql.SQLException: Cannot obtain connection after 3600 seconds. , Exception = Access not allowed

Using Weblogic Platform 7.0 (installed from platform700_win32.exe),
Running a BPM Doamin(WLIDomain with BPM only).
When I try to access my entity bean(CMP), the following exception is getting thrown.
I have seen a similar post in here, but the answer to that post, which says to
provide ACL. does not apply quite well my scenario.
To do this, I right clicked on the connection pool and selected define Ploicy..
It shows two options
RealmAdapterAuthorizer and DefaultAuthorizer; On DefaultAuthroizer i specified
role accessing the resource would be "everyone". - restarted the server - but
still the same error.
Please suggest a solution if any. Do i have to get some service pack for this?
TIA
Ranjith.

We have never seen a case yet where this was not a permissions problem.
Do you have a fileRealm.properties file as part of your configuration?
"Ranjith" <[email protected]> wrote in message
news:3f0fdeb3$[email protected]..
>
java.sql.SQLException: Cannot obtain connection after 3600 seconds. ,Exception
= Access not allowed
java.sql.SQLException: Cannot obtain connection after 3600 seconds. ,Exception
= Access not allowed
atweblogic.jdbc.jts.Connection.wrapAndThrowSQLException(Connection.java:701)
atweblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:623)
atweblogic.jdbc.jts.Connection.prepareStatement(Connection.java:133)
atweblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.ja
va:139)
atweblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:81
atservice.samplemgt.v1_0.ejb.entity.BanksampletypeCMP_ckv0ao__WebLogic_CMP_RDB
MS.ej
bFindAll(BanksampletypeCMP_ckv0ao__WebLogic_CMP_RDBMS.java:873)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.collectionFinder(RDBMSPersi
stenceManager
java:300)
atweblogic.ejb20.manager.BaseEntityManager.collectionFinder(BaseEntityManager.
java:715)
atweblogic.ejb20.manager.BaseEntityManager.collectionFinder(BaseEntityManager.
java:688)
atweblogic.ejb20.internal.EntityEJBLocalHome.finder(EntityEJBLocalHome.java:47
6)
at ...

Error : T161W: Vendor+subcontracting vendor not allowed for 2-step stock tr

Hi Gurus,
When we creating a STO to sub contractor vendor ( in the delivery address tab we are entering the vendor # and activating the SC vendor check box)we are getting the error message as "T161W: Vendor+subcontracting vendor not allowed for 2-step stock transfer".
Message no: MEPO140
Note:
The STO is creating with out error in ECC 5.0 for the above scenario but when i'm trying the same in ECC 6.0 in another system I'm getting this error, Can any one please advice.
Thanks in advance,
Sai

Hi Charlie
I had same issue and we sloved it. but i have one more issue here.
We have created Po and SC Vendor is not check marked. When we go into the change mode of Po i can't see the field at all. but its availalbe in disply mode.
I am using ECC 6.0, Please suggest why this is happening. I need to put check mark for SC vendor.
thanks,
Raju

Weblogic 7.0, Oracle9i - "Access not allowed" error

All:
I am looking for any suggestions/help/advice/etc on my problem. The background is this, I have an application that uses 3 MDBs, 3 Entity Beans, is deployed on Weblogic7.0 (the latest), and needs to query an Oracle9i database.
I have set up my drivers and URL, they work fine under a normal java class making a connection. They also return "success" when using dbping to test the connection, so the set up is right.
When Weblogic starts, the connection pool is made, the DataSource is fine -- but when the EJB is deployed it comes back with the SQLException "Access not allowed".
I've put the classes12.zip file at the beginning of the classpath, modified the setenv.cmd file so the PATH includes %ORACLE_HOME%\bin and %WL_HOME%\bin\oci920_8.
I've also put in the following in the weblogic-ejb-jar file:
<security-permission>
<description>Oracle</description>
<security-permission-spec>
grant {
permission java.lang.RuntimePermission "loadLibrary.ocijdbc9";
</security-permission-spec>
</security-permission>
I've even tried to do what the Security Manager portion of the Weblogic documentation says to do. It said to "activate the security manager" by putting the following line in the startWeblogic file:
-Djava.security.manager
None of these have worked -- I keep getting that error. Like I said previously I have tried the connections and they have worked through other methods.
I've tried everything, including using an XA driver -- to no avail. My forehead is getting really sore from banging it on the monitor --- can you help???? :/
Thanks!
The connection pool information follows (from the config.xml file):
<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="1"
LoginDelaySeconds="1" MaxCapacity="36" Name="P3IConnectionPool"
Properties="user=EI_SERVICES;password=EI_SERVICES;dll=ocijdbc9;protocol=thin"
RefreshMinutes="0" Targets="beaserver"
TestConnectionsOnReserve="true" TestTableName="STATE_LKUP" URL="jdbc:oracle:thin:@192.168.23.45:1521:ORASUN"/>

Just in case anyone needs this in the future....
After creating the connection pool in Weblogic 7.0 (using the Weblogic console) right click on the connection pool and select "Define Policy", select "Default Authorizer", then enter "Caller is a member of the group everyone" and apply.
That takes care of the problem... didn't happen in Weblogic 6.1

Transaction CLM1 not allowed for notification type QL

Hello guys,
one of our user try to open the transaction CLM1/CLM2/CLM3 he getting error message Transaction CLM1 not allowed for notification type QL
please any one give solution for this issue.
find the error screen shot for your reference.
Thanks
Surya

Hello Surya,
Have you done Basic configuration for Claims processing in SAP Project System.
SPRO > Project System > Claim > Notification - Claim > Notification creation
Also check config for Settings for Claims.
Refer sap help for more details
SAP Library - Claim Management
Regards
Tushar

When am reversing 201 document.. 202 is not allowed for warehouse abc

hi friends,
when am reversing 201 document.. 202 is not allowed for warehouse abc
what is the reason and why they have made not allowed.
thanks and regards,
Bala R.V

Dear Friend,
now i have entered 202 for that ware house but now it is giving an error WP1(wh) GIA TEST 10(cost centre) does not exists.
Please help me in resolving this issue.
Thanks and regards,
Balakrishna

"Access not allowed for subject: principals=[]" Common Issue with no Repose

Similar Messages

Maybe you are looking for