Planning - Attribute Hierarchy question
I currently have an attribute defined for one of my dimensions and would like to re-arrange the defined attribute members into a simple hierarchy. That does not appear to be possible. I can create Siblings and Children, but cannot move an existing member to be a child of Parent. Has anyone found a way around this? Thanks -
Tom
Dianne,
The whole purpose of 52 is to build the lower levels of the BOMs to the forecast, and to ignore any extraneous factors (such as sales orders and FGs stock). SAP specifically excludes netting against FGs stock for this strategy. In an ideal world, such stock does not exist. When it does exist, it must be handled manually.
Some companies add a step to their forecasting process, by reducing the forecast by the amount of stock contained in FGs, before converting the forecast to Planned independent requirements, as a partial workaround.
Generally, your ATPs will not consider FGs stock. As soon as you issue FGs to the order, then the FGs buildable planned orders disappear during the next MRP run, and everything falls back into synch.
If you wish to net against FGs stock, use a strategy like 40 or 10, and use a regular ATP. Or, consider using enhancements.
Best Regards,
DB49
Similar Messages
-
Error While Opening dataform after creating Planning Unit Hierarchy
Hi All,
I created a Planning Application through classic wizard. Then i created a planning unit hierarchy, after which I am getting the following error: (when i try to open a dataform, from some user other than admin/owner)
*"Security and/or filtering has resulted in a required dimension not being represented on this data form"*
I know that this error occurs when some dimension members are represented on dataform but are not assigned with security rights. But thats not the problem in my case. Because I assign security rights to all members of all dimension just for the sake of testing. I later on identifed that this error occurs due to dimensions present in POV i.e. I need to select a single member of each POV dimensions, then in such case this error disappears.
Now my question is that why i need to select a single member from each POV dimension? I general i leave POV dimensions as it is, while creating dataform
Right now i aad a dummy member at the top of each dimension, e.g Account_UnSpecified, Entity_UnSpecified and so on . . . and then i select this member from each of POV dimension.Hi,
You can try creating new Root folder and new workspace for your NWDS.
1. Create a new folder with name ' <userID>_NWDS_NEW_ROOT ' in your machine
2. Create a new folder with name ' <userID>_NWDS_NEW_WORKSPACE ' in your machine
3. Open NWDS (and logon to DTR)
4. Remove all configurations from your Development Configuration perspective (except 'Local Development')
5. Go to Window --> Preferences --> Java Development Infra --> Development Configurations
6. Change 'Root Folder' to the folder created in step-1
7. Close NWDS
8. Create ' Run_NWDS.bat ' file in your NWDS installation folder which has 'SapIde.exe' file
(it will be generally in --> C:\Program Files\SAP\IDE\IDE70\eclipse)
9. Type following in .bat file -->
SapIde.exe -data "<complete path to folder created in step-2>"
10. Now double click on this .bat file to open NWDS
Now logon to DTR, import configuration, create project from 'inactive DCs' and you should be able to create project and see it in respective perspective.
Regards,
Amey -
Product : Errors in attribute hierarchy structure SAP BCA 000164
Hi All ,
When ever i create /Display /Change Product in
Financial Supply Chain Management --> In House Cash > Master Data>Product Definition--> Product --> Create /Change/Display
system through below mentioned error .
I tryed to resolve problem as per below mentioned program through se38 , but still getting same error
Errors in attribute hierarchy structure SAP BCA 000164
Message no. FIPR217
System Response
An error was found in the attribute hierarchy.
In some cases, it is not possible to display the attribute hierarchy without having to correct the errors first.
Procedure
It is recommended that you run the FIPR_CLEAN_ATTRIBUTES (by using transaction SE38). This report can recognize errors, and it attempts to correct them automatically.
Caution: This report can change your table entries permanently.
Once this report has run, you need to check the hierarchy structure, and make any necessary changes.
Regards
Prakash SharmaHi,
the realignment (KEND) does not change the line item tables (CE1***, CE2***), thats why they remain unchanged.
The line items in CE1**** can not be changed. If you really want to have new line items (with the new prod. hierarchy) try in test-client if the use of report RKECADL1 and the new transfer to CO-PA for the deleted line items (KE4S, KE4SFI,...) can help you (SAPNET-note 69370 for details).
CE2**** + SQL-error: As per now, I don't have an idea how to deal with that cases.
best regards, Christian -
Hi all
I have a date dimension that (type time) with attributes
- [FiscalYear] (type years)
- [FiscalMonth] (type months)
- [FiscalWeek] (type weeks)
In addition to the attributes used in the natural hierarchy, I have an attribute [PerType] containing one member comming from the relational table 'WTD' which corresponds to 'Current Date'. All other members of this attribute hierarchy are calculated members (defined in the MDX script). Examples:
--Last year
CREATE MEMBER CURRENTCUBE.[Date].[PerType].[LY] AS NULL,
VISIBLE = 1;
SCOPE([Date].[PerType].[LY]);
SCOPE(DESCENDANTS([Date].[Fiscal].[All], [Date].[Fiscal].[Year], SELF_AND_AFTER));
THIS = ([Measures].CurrentMember, [Date].[PerType].[WTD], ParallelPeriod([Date].[Fiscal].[Year], 1));
END SCOPE;
END SCOPE;
--Month to date
CREATE MEMBER CURRENTCUBE.[Date].[PerType].[MTD] AS NULL,
VISIBLE = 1;
SCOPE([Date].[PerType].[MTD]);
SCOPE(DESCENDANTS([Date].[Fiscal].[All], [Date].[Fiscal].[Week], SELF_AND_AFTER));
THIS = Aggregate(CrossJoin({[Date].[PerType].[WTD]}, MTD([Date].[Fiscal].CurrentMember)));
END SCOPE;
END SCOPE;
--Year to date
CREATE MEMBER CURRENTCUBE.[Date].[PerType].[YTD] AS NULL,
VISIBLE = 1;
SCOPE([Date].[PerType].[YTD]);
SCOPE(DESCENDANTS([Date].[Fiscal].[All], [Date].[Fiscal].[Period], SELF_AND_AFTER));
THIS = Aggregate(CrossJoin({[Date].[PerType].[WTD]}, YTD([Date].[Fiscal].CurrentMember)));
END SCOPE;
END SCOPE;
The defalut member of FiscalWeek attribute hierarchy is set dynamically in the MDX script:
ALTER CUBE CURRENTCUBE UPDATE DIMENSION [Date].[FiscalWeek], DEFAULT_MEMBER =
Filter(
[Date].[FiscalWeek].Members,
[Date].[FiscalWeek].Properties( "FiscalWeekStartDate", TYPED) <= DateAdd("d", -2, CDate(CStr(Month(Now())) + "/" + CStr(Day(Now())) + "/" + CStr(Year(Now()))))
AND
[Date].[FiscalWeek].Properties( "FiscalWeekEndDate", TYPED) >= DateAdd("d", -2, CDate(CStr(Month(Now())) + "/" + CStr(Day(Now())) + "/" + CStr(Year(Now()))))
)(0).PrevMember;
If I run the following query:
with member
measures.x as [Date].[Fiscal].DefaultMember.Name
measures.y as [Date].[FiscalWeek].DefaultMember.Name
select
measures.x,
measures.y
} on axis(0)
from [GLWeekly]
it gives me back correctly the default member set over the MDX script.
I order the statements in the MDX Script so that the default period (week) is set at the beginning of the script (just after the calculate).
I do not understand why creating the following calculated member I am obliged to specify [Date].[Fiscal].CurrentMember in the tuple to have correct results:
MEMBER [Account].[CoA].[Standard Engagement Revenue (MTD)] AS ([Account].[CoA].[Standard Engagement Revenue], [Date].[PerType].[MTD], [Date].[Fiscal].CurrentMember)
I would expect that:
([Account].[CoA].[Standard Engagement Revenue], [Date].[PerType].[MTD])
is sufficient.
If the default week is specified in the slicer using a member of the natural hierachy (=> [Date].[Fiscal].x) it works.
Why can't SSAS use the default member if it is must defined in the MDX script?
Can someone explains me this. Thanks a lot in advance.Hi Ina,
have you thought about adding a dynamic statement inside the MDX script? You could define the default member like this:
... DEFAULT_MEMBER = iif( Day( Now() ) = 3, <expression for previous month>, <expression for current month> );
This way you don't need to change it everytime by running a script.
By the way, what do you mean it doesn't update the default member? When you execute this MDX what does it says?
with member measures.x as [Dimension].[HierarchyName].DefaultMember.Name
select { measures.x } on 0 from Cubename
If this returns the correct name, then the problem is somewhere else. I believe it should return you the correct name. Look here, test this on Adventure Works, statement by statement and see what happens.
ALTER
CUBE [Adventure Works]
UPDATE
DIMENSION [Product].[Product Categories],
DEFAULT_MEMBER = [Product].[Product Categories].[Category].&[1]
with
member measures.x
as [Product].[Product Categories].DefaultMember.Name
select measures.x on 0
from [Adventure Works]
ALTER
CUBE [Adventure Works]
UPDATE
DIMENSION [Product].[Product Categories],
DEFAULT_MEMBER = [Product].[Product Categories].[All Products]
with
member measures.x
as [Product].[Product Categories].DefaultMember.Name
select measures.x on 0
from [Adventure Works]
I think you can see which members are default (on related hierarchies) using
MDX Studio. This should help you detect which attributes have not moved accordingly and hence cause problems in your report. The usual suspects are those attributes used in your last month reports. If that's too much for you, just copy paste the definition
of the measure x and use .CurrentMember instead .DefaultMember. And so for all related hierarchies of your dimension. You can run it as one query, just put enough measures (x1, x2, ...), one for each hierarchy, ok?
Here's a test for Day():
with
member measures.y
as
iif( Day(Now()) = 28, 'Yes', 'No' )
select
measures.y on 0
from [Adventure Works]
Today this returns Yes, tomorrow it will be No.
Ups, I just checked one more thing. When you run the script, it sets the default member only for that session. If you execute the first two of the four statements that I've sent you, it will set the default member on Bikes and show you that.
But, if you open another query windows and execute that select statement (only), you'll see All member instead. So, it has set it to Bikes only for the currect session. Consequence? You reports are not aware of it. So, better use dynamic statement in
your MDX script.
Regards,
Tomislav Piasevoli
Business Intelligence Specialist
www.softpro.hr -
User In Planning unit Hierarchy unable to see data form in editable mode
hi all,
we are facing a problem in planning unit hierarchy in Hyperion planning, where we have 4 users, Hierarchy is define as
hierarchy: budget approved
version: approved
Entity: Finance
Senario:Budget
haroon asghar ( owner)
adeel javid (Reviewer)
Naeem asghar (Reviewer)
Imtiaz (Reviewer)
Issue is that,after start the budget activity (promotional path) by Admin, the data form editable to Owner haroon asghar
but after completing his work by haroon,when he promote the planning unit ,the next user in Hierarchy "Adeel javid" unable to see data form in respective planning unit in uneditable data form not only for this user but all rest of the users as well,while i think data form should only uneditable(grayed) for user Haroon Asghar who promote the planning unit.
we have checked all security rights to the users those are "Write access" but still Adeel javid is unable to enter data,so the budget activity is stop due to this problem.
when i remove the planning unit then i log in with all user one by one and see all data form required version,scenario and entity were editable to all users mention above
we want to run budget activity with the above planning unit hierarchy.
plz any one provide the proposed solution of the said issue
we are using Product Version 11.1.2.0.00
Regards
AnwarReviewers will not be able to write data to the intersection. Reviewers can only review the data and follow-up with a Reject, Promote, Sign off, Delegate, Originate or Freeze.
Please refer Article ID 1226783.1 in MOS.
HTH-
Jasmine. -
Aggregates based on Nav Attribute Hierarchy
Hi,
I have naviational attribute hierarchy based on created by and enabled as navigation attribute from Infocube. So for each transaction the created by pulls up the corresponding nav attribute from master data.
I have enabled the Created By nav attribute hierarchy in the query and the rendering of the hierarchy is really slow and the performance went down.
What is the best way to increase performace creating aggregates at Created by level or Created by Nav attribute hierarchy level?
Is there any document available on this topic?
Thank you
ArunHi Arun,
I don't know if this can be useful, but take a look to OSS Note 738098 'Performance problems with hierarchies'..
Hope it helps!
Bye,
Roberto -
Attribute /hierarchy change run
Hi,
I have to run the Attribute/Hierarchy change run for only one infoobject. When I click on "Infoobject list", the list is empty even though some changes were made in the hierarchy. How can I get the infoobject list?
Thanks.Hi.......
The easiest method is ........use the Program : RSDDS_AGGREGATES_MAINTAIN.........there give the infoobject name.........Then in the top Program tab >> Execute in background...........then u can monitor the Job in SM37........the job name will be RSDDS_AGGREGATES_MAINTAIN..........
But logically if changes has done to the Master data......Transaction RSA1 --> Tools --> Apply Hierarchy/Attribute Change... --> InfoObject List & Hierarchy List ............this List should contain the list of infoobjects.............if nothing is there..............it means no changes has been done.............and there is nothing to be activated............So also check whether the changes hav been done properly or not.....................then use this program............it should be done........
Regards,
Debjani...... -
No Purchasing Group is assigned to Org plan attributes
Hi,
When the user is creating a SC he is getting the following error "No Purchasing Group is assigned to Org plan attributes".I have checked the users Org structure in PPOMA_BBP,But everything looks fine.
Any inputs will be appreaciated!!
Thanks
Rakesh.Hi
product category are directly related to purchase group. depends upon the settings in the organisation structure , the system determines which purchase group is responsible for procuring this product category.
so back track your product category and purchase group link and this purchase group is made a link with purchase organisation. since product category responsiblity is a mandatory in srm.
Can you update here . where your user was positioned in org structure?
hope that you made a link between purch organ with purchase group?
po1
--> pg1
and moreover check following settings. are you try to procure via describe (spl request)?
Purchase group - responsibilty tab what are the product category you mentioned?
have you maintain Organisation responsibility under the responsibility tab?.
still you find difficulty ?
regards
muthu -
Planning Unit Hierarchy - multiple owners per Entity
Hi there everyone
I have the following scenario and hope you can help me out with a few ideas:
I have a planning unit hierachy set up. It works well except for one thing - the fact that you can assign only one owner per entity member. The business essentially has multiple owners for most entities. Ownership is determined by which accounts the user is responsible for. An example:
User 1 is an owner for Entity A, but only for accounts 111-444.
User 2 is an owner for Entity A, but only for accounts 555-777
User 3 is an owner for Entity A, but only for accounts 888-999
As far as I can see in the Edit Planning Unit Hierarchy screen, I am able to assign User 1 as an Owner for Entity A on the Assign Owners tab and I can specify accounts 111-444 in the Primary and Subhierachy Selection tab. Since I can only assign one owner, how can I now provide for User 2 and User 3 requirement?
I'm using version 11.1.2.1. Any workarounds or suggestions would be highly appreciated!
Thanks
JuanitaI had a similar business case in my previous project. There was no direct solution to this. But we had to stick to a workaround ( not a very nice and comfortable solution, but we were under critical timelines).
User 1 is an owner for Entity A, but only for accounts 111-444.
User 2 is an owner for Entity A, but only for accounts 555-777
User 3 is an owner for Entity A, but only for accounts 888-999
make a secondary hierachy with different entities i.e. User1_EntityA,User2_EntityA
Entity A
User1_EntityA
User2_EntityA
and then you can assign different users to all these entities. One major drawback with this is, if we have 100 entities with 10 users .. that will make 1000 more members.. anyhow we did it that ways.. if you get a better solution you can post it.
Thank You
Sandeep Kumar Upadhyay -
2 issues - Invalid Serial Number issue & Lightroom 5 Trial vs full version folder hierarchy question
Hello
not sure if I should split these two questions...
1 - Invalid Serial Number issue
I'm helping out a friend with their large photo collection and they bought Lightroom 5 and received the serial number but when we add this to Lightroom it states that it's invalid - I tried leaving it until the following week (I visit them weekly) and it still refusing the number - when I went into their Adobe account and took a look at downloads the option to download the full version is greyed out (or an x - I'm not sat on their computer right now so can't double check) but it wouldn't allow me to do anything so we just had the trial version.
anyone know what the issue is - shall I get them to contact Adobe to get them to take a look - I also had issues trying to find a customer support email address lol. (I seem to faffing with lots of websites/software/companies this week so getting a little frazzled!)
2 - Lightroom 5 Trial vs full version folder hierarchy question
This question is linked to the above i- I am wondering if the folders in Lightroom are different in the trial version vs the fully paid version.
I had set up some greeting card templates and contact sheet layouts for my friend and tried to transfer them to her computer but whilst, LR 'sees' the folders it just doesn't acknowledge the templates - I tried it several ways but I've not had that issue before so will that sort itself when I get the serial number fixed?
Thank you for any help or suggestions - hope you all have a good weekend :-)
LennyHi Lenny, the two questions may be related but the trial is actually the same as the full version. I would suggest getting the serial number issue sorted out first. There have been known issues where a paid for product still shows up as a trial.There is not a lot the community can do. You need to contact Adobe directly using the link below. Use the dropdown menu for boxes (1) & (2) to scroll down the list and choose:
1. Adobe Photoshop Lightroom
2. Serial number issues or activating my product
3. Click on the blue button: Still need help? Contact us – then click the button marked “chat now”
It’s usually possible to start a live chat, if an Adobe agent is free, and often to get the problem fixed right away.
Click here to get help now Contact Customer Care -
Unable to create Planning product Hierarchy
Hello,
I am having a planning material in ECC assigning this material to another finished product.
Defined the planning strategy 60 in the material master of the finished product and assigning the the planning product there.
When I am transferring in CIF , selecting the Planning material check box as well as regular finished product.
My expectation is a planning product hierarchy has to be created in APO but this is not getting created.
I am not sure whether any additional settings to be defined or not.
Can somebody help me out.
Regards,
nandhaHello,
In CFM1 select the Planning material check box without any finished product.
Planning materials should be X0 in material master and same you should use in selection.
Do the CFM2 followed by RIMODINI
System will transfer the Planning materials and FG connection as per the entries in PGMI table.
Also refer OSS note 1025982 - Product hierarchy transfer is not working properly
Best Regards,
R.Brahmankar -
ODI Planning Attribute Dimension
I have an existing Product dimension that was created via ODI 10.1.5.6 to Planning 11.1.1.3.03 -- the Product Dim loads fine. Then I attached an attribute dimension called "Product Line" to it using custom attributes. I added four attributes to attach to products. Then re-reversed the Planning application in ODI Planning Model. I can see "Product Line" attribute load dimension (to load new attributes) in the Dimension hierarchy in ODI. However I cannot see a new Column for "Product Line" under the "Product" dimension in ODI. Am I missing something??
So adding the manual dimension seemed like it would work. However it gave me an error as it didn't recognize it when I executed the integration. In any event, deleted the planning model, recreated it and reversed it and the field showed up. Fun stuff! Thanks again.
-
Planning Level Root Question (Periodid Vs Monthly)
Hello,
I have a question related with planning level configuration.
In the standard SAP Planning area
SAP2 - All the planning levels have been defined monthly attribute as the root for time
SAP4 - All the planning levels have been defined periodid attribute as the root for time
What is the difference between both type of configuration. (Selecting Monthly / period id as the root, what difference it creates and how it affects other areas)
I was testing consensus demand key figure in SOP 3.0 and I am unable to edit the key figure value in my planning area (KF value change in Excel) which is a copy of SAP4 planning area. Initial response from SAP OSS is to modify the planning level and use monthly instead of Periodid (But I have just copied the standard SAP4 planning area).
Uploading the key figure using KF template works fine but issues comes only when I tried to change the value in Excel or try to input new values in blank cells.
Same thing I also tested in IBP 4.0 FP1 Patch 1 and configuration is exactly the same as SOP 3.0 (Both SAP2 and SAP4 planning area) but I am able to modify consensus demand key figure in both the copied planning area (Copy of SAP2 and SAP4) irrespective of monthly / periodid selected as the root.
Please let me know if you have observed this before and what are your feedback/suggestions.
Thanks
GirishHello,
I have a question related with planning level configuration.
In the standard SAP Planning area
SAP2 - All the planning levels have been defined monthly attribute as the root for time
SAP4 - All the planning levels have been defined periodid attribute as the root for time
What is the difference between both type of configuration. (Selecting Monthly / period id as the root, what difference it creates and how it affects other areas)
I was testing consensus demand key figure in SOP 3.0 and I am unable to edit the key figure value in my planning area (KF value change in Excel) which is a copy of SAP4 planning area. Initial response from SAP OSS is to modify the planning level and use monthly instead of Periodid (But I have just copied the standard SAP4 planning area).
Uploading the key figure using KF template works fine but issues comes only when I tried to change the value in Excel or try to input new values in blank cells.
Same thing I also tested in IBP 4.0 FP1 Patch 1 and configuration is exactly the same as SOP 3.0 (Both SAP2 and SAP4 planning area) but I am able to modify consensus demand key figure in both the copied planning area (Copy of SAP2 and SAP4) irrespective of monthly / periodid selected as the root.
Please let me know if you have observed this before and what are your feedback/suggestions.
Thanks
Girish -
Loading Planning attribute dimension alternate hierarchies with ODI
Does anyone know how to load an attribute dimension alternate hierarchy via an ODI interface? I'm assuming that alternate hierarchies are allowed in attribute dimensions?
Edited by: jayfin on Mar 28, 2011 5:59 PMIf you are talking about created a shared hieararchy then no this is not possible as you shouldn't be able to do it in planning.
If it is just another hierarchy in your attribute dimension then you should be able to load parent/child members to build it using ODI.
Cheers
John
http://john-goodwin.blogspot.com/ -
I have 2 questions related to hierarchy :
1. How do I assign a record say individual product record to an hirarchy e.g.
All Product ->Electrical Products->Fan->4 blade fan , 230 V AC
->Motors-> 3 phase induction motor , 415 V AC
->Mechanical Products->Compressor-> 1000 cc air compressor
2. Also how can i assign attribute to specific node of an hierarchy say Fan in this case .
Guess above can be achieved using taxonomy but how to do it in the hierarchy
Can some one provide the steps , thanksHi Amit,
Replying to ur first query:
This u can do in the hierarchy mode of the data manager.
Note:Although you can view, add, edit and delete the records of a hierarchy table in <u>Record mode</u>, you should usually edit a hierarchy table in <u>Hierarchy mode</u> so that you can view and edit the hierarchical relationships in addition to the other fields of each record.
MDM supports inner node assignments indirectly , while preserving the rule that a hierarchy lookup field be assigned only to a leaf node in the hierarchy using an internal leaf node .
You can then make inner node assignments to the parent by assigning records to the internal leaf which acts as a proxy for the parent for assignment purposes just as you would assign records to any other leaf node .
When you use the Create Internal Leaf command to create an internal
leaf for a parent node, MDM creates a duplicate of the parent node as
its first child
Steps:
To create an internal leaf node for a hierarchy tree item:
1. In the hierarchy tree, select the parent node for which you want to
create an internal leaf.
2. Right-click on the node and choose Create Internal Leaf from the
context menu, or choose Tree > Create Internal Leaf from the main
menu.
3. MDM adds an internal leaf node named [parent] as the first child of
the selected node.
NOTE ►► The name of the internal leaf node is the name of the
parent node in square brackets ([]).
NOTE ►► You cannot edit the node name nor any of the fields of the
internal leaf, which are auto-populated with the values of the parent
when the internal leaf record is first created. This means that if the
name of the parent changes, the internal leaf will continue to display
the old parent name in square brackets.
NOTE ►► A normal leaf node cannot be converted into an internal
leaf node nor can an internal leaf node be converted into a normal leaf
node. Instead, you must create a second node, reassign records from
the first node to the second node, and then delete the first node.
Create Internal Leaf Constraints
Operation Constraints
Add
Internal Leaf
�� Must be in Hierarchy or Taxonomy mode
�� Tree must have focus
�� Exactly one node must be selected
�� Root node cannot have internal leaf node child
�� Node cannot be an alias
�� Node cannot have an alias
�� Node cannot have a matching set
�� Node already has internal leaf
�� Node is an internal leaf
Please reward me with points if u find this information useful.
Thanks & Regards
Deepankar
Maybe you are looking for
-
Error Message FMBAS202 Year of cash effectivity mandatory for budget cat 9G
Hi all, I activated BCS and use update profile 000350 (Separate PB/CB budget lines; standard), we tried to post simple FI posting and the error come up ============================================================== Year of cash effectivity mandatory
-
I was trying to burn DVD with GUI it failed multiple times, so I tried with growisofs, but problem is the same: :-[ WRITE@LBA=10h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument if I try again it shows :-[ WRITE@LBA=0h failed with SK=5
-
What is wrong with the screen stays black
what is wrong with the iPod if the screen stays black and won't turn on, but is fully charged.
-
Hi, In a three-tier architecture, has anyone successfully implemented VPD in combination with Toplink and a ConnectionPool? When all my web-users are connecting to the database with the same (connection pool) credentials, how, when and where do I tel
-
Acrobat freezing when PDFs are opened
Acrobat XI Standard is freezing and not responding in Windows 8.1 when I try to double click to open most PDFs. This does not occur when I go to File>Open and navigate to their location to open them, and it does not occur when I set all files to open