Engineering project.
Hi,
I am studying electronic engineering and would like to know how java language can help me to develop an engineering related project. I mean must be related to electronic engineering. I need to submit project proposal soon, any help using java ?
Regards,
thinkwork.
Hi,
In my point of view, java is a programming language which is powerful enough to solve any engineering problem, you can pick your engineering problem by yourself, then sum up the algorithm involved with it, then you can start writing your java code, just as you can write it with C++.
If you need help on a specific part of your project concerning java language, you can email me at [email protected] I will reply you as soon as possible.
With my best,
Zike Huang(jim)
Similar Messages
-
Need help with almost completed plugin engine project
Hi all,
For a while now I have been working on a plugin engine. After a few iterations, the engine is similar to the Eclipse engine, in that plugins use extension points and extensions to allow contributions. Unlike the eclipse engine I have added the ability for plugins to fire events through the engine and other plugins can add listeners, all through the plugin.xml manifest. Dependencies are mostly handled automatically at plugin load time (when extensions get resolved to extension points, and listeners get resolved to events). For the case where a plugin needs to use classes from another plugin, dependencies are also allowed to be declared. Like the eclipse engine, activation of plugins occurs the first time a class is used within the plugin's classpath, OR a plugin can be activated after it is loaded.
What I need help with is testing, working on examples to provide with the engine project, and feedback/suggestions before we release the M1 build. I am asking for those that are interested in this type of work to volunteer to help where applicable and possible. I want to provide a solid plugin engine to the java community, one that is easy to use, works well, and is pretty effecient in terms of resource usage and performance.
Of particular interest to me right at the moment is dealing with multiple versions. As I see it, the engine will be used within an application and as such plugins would be distributed with a specific application version. The plugin version itself is more of a notification as to what version a plugin is, although I imagine it will help when updating at runtime as well.
Just a few other details of the engine. It handles (or will soon) dynamic load, unload and reload of plugins at runtime. Plugins can be distributed in an archive file format, we call .par (Plugin ARchive), with additional plugin filename extensions configurable at runtime. The plugins can be developed and deployed in an expanded directory format as they are in Eclipse as well, or in the archive format. In the archive format they do not need to be unzipped when deployed, and they can contain embeded jar/zip libraries. The engine handles finding and creating classes directly out of the .par file at runtime.
Multiple locations to find plugins are configurable before the engine starts, and even after it starts more could be added to allow additional locations to find plugins. URLs are supported, and soon the HTTP protocol will be supported so that plugins can be downloaded and installed at runtime.
The project can be found at www.sourceforge.net/projects/genpluginengine. If you would like to get involved and help out, please sign up on the dev mail list and send an email to introduce yourself to the rest of the members on the list.
I'll also add that I am working on a Swing UI Framework built entirely from plugins. It provides a ready-to-launce UI application that developers can simply add their plugins to, extending various extension points of the framework to have menu items, toolbar buttons, status bar access, help and preferences dialog additions, file i/o choosers, tons of open-source components ready to use (or extend to add on to), and like Eclipse, hopefully... draggable window frames that can be dropped on any other frame to form a tabbed frame of windows. Some of this is a ways off, some is getting there now. Presently you can add menu items that do allow plugin activation when first clicked, so plugins can be loaded but not activated until needed. The Preference dialog works but is not completed, and a plugin that adds a plugin control panel to view all loaded plugins, activate them, load/unload/reload, view extension points, extensions, dependencies, etc is partially completed. The point is, to allow a ready to run UI framework in Swing with an easy path for developers to quickly build applications with. If you are interested in this, when you join the mail list and introduce yourself, indicate that you are interested in this as well, as we need help with plugin development for it and would appreciate more help here too.
Look forward to some replies.Might I suggest setting up a project at a known project-site? I've seen your progress and questions posted here from time to time, but one of the drawbacks is that you have to fill each post with the entirity of your vision to explain what you're doing. That's a lot of text to read - and most folks will skip right over it.
On the other hand, a well-crafted, good-looking project web-site, with appropriate links and docs and vision statements, diagrams, etc. will have more likelyhood of attracting volunteers. java.net and sourceforge.net are likely spots to set up shop. In addition, you get CVS and bug-tracking systems, which can be quite valuable in such a large-scale project where there are lots of pieces. -
A question for Tokenizer in a search engine project.
I am doing a search engine project in Java. The project will need two parts: indexer and query Processer. The class I have includes IndexBuilder.java, InvertedIndex.java, Parser.java, Tokenizer.java, StopWordList.java, Lovinstemmer.java.
Among above class files, I am not quite understand how Tokenizer works. The following is what I am understanding the scenario of index part works. Please check what I talk about how Tokenizer works, it might be wrong.
I think Parser object will get the input file, then will deal with the words in the file one by one. FOr example, for the first word in the input file, Parser will contact StopWordList.java and Lovinstemmer.java to get rid of unuseful characters, then pass this changed word to Tokenizer, Tokenizer will then do sth to this words, then return a token( here, token is the words) to the Parser, then Parser will put this token into InvertedIndex.
Am I right? If I misunderstood sth, please let me know. Thanks,
JamesIt's quite possible that what you say is correct, but why are you asking us? Those classes are not part of the standard Java API, but were written (or at least) specified by somebody else. So ask that person.
-
3 PHP Template Engine Project Sharing
Three [PHP Template Engine |http://www.phpkode.com/projects/category/php-template-engine/]Project Recommended:
Smarty is a PHP template engine.Smarty is best described in a situation where the application programmer and the template designer play different roles, or in most cases are not the same person.Smarty is primarily promoted as a tool for separation of concerns. More specifically, it facilitates a manageable way to separate application logic and content from its presentation.
RainTPL, now part of Rain Framework, is an open source PHP template engine that compile HTML template in PHP to improve the speed. Divide the works of graphics by the works of programmers by splitting statics code (HTML) from dynamic code (PHP
Dwoo is a PHP template engine. It features fully compatible with Smarty templates and plugins, but is written from scratch for PHP5. Template inheritance, a fresh look at complex template structures. Sub-template declaration within templates to allow recursive templates.
Any one suggest more better php template engine?
Tks!
Best regards!http://phpsavant.com/
is pretty cool -
Configuration docs for construction engineering projects.
Dear Gurus,
pls provide the conf steps and blue print for construction engineering projects.
The following are the diff sales senarios.
1.Residential sales
2.commercial sales
3.service
4.lease
5.scrap sales
Regards
RAMSHi Rams,
{Do reward points for good answers so that you are encouraging the members to help you and others in a better and clear way}
Residential Customers:
http://www8.sap.com/businessmaps/BEED3A34D61C4FA4BCE5839375C4545E.htm
Regards
AK -
Hi
Im basically building a 3d engine (very simple one) using software rendering (no opengl or directx) for learning purposes.
The 3d engine has one simple rendering method thats suppose to render a point from world space to the 2d space (monitor)
i believe i got the rendering working properly, but it has no perspective
i believe i need a perspective matrix
can you pros help me build one
public static Pixel2D render(Camera c, Pixel3D p) {
//matrix transformations (with euler style rotation)
//fm = pm * cm * wm * point
double fm[][];
double om[][] = createMatrix(4, 1);
double cm[][];
double ctm[][] = createIdentityMatrix(4); //camera translation
double crxm[][] = createIdentityMatrix(4); //camera x-axis rotation
double crym[][] = createIdentityMatrix(4); //camera y-axis rotation
double crzm[][] = createIdentityMatrix(4); //camera z-axis rotation
double pm[][] = createIdentityMatrix(4); //perspective matrix
double rx = Math.toRadians(c.getRoll());
double ry = Math.toRadians(c.getPitch());
double rz = Math.toRadians(c.getYaw());
//camera matrix
//translation
ctm[0][3] = c.getX();
ctm[1][3] = c.getY();
ctm[2][3] = c.getZ();
//roll
crxm[1][1] = Math.cos(rx);
crxm[1][2] = Math.sin(rx);
crxm[2][1] = -Math.sin(rx);
crxm[2][2] = Math.cos(rx);
//pitch
crym[0][0] = Math.cos(ry);
crym[0][2] = -Math.sin(ry);
crym[2][0] = Math.sin(ry);
crym[2][2] = Math.cos(ry);
//yaw
crzm[0][0] = Math.cos(rz);
crzm[0][1] = Math.sin(rz);
crzm[1][0] = -Math.sin(rz);
crzm[1][1] = Math.cos(rz);
cm = multiplyMatrix(crxm, crym);
cm = multiplyMatrix(cm, crzm);
cm = multiplyMatrix(cm, ctm);
//projection matrix
pm[3][2] = 1;
pm[3][3] = 0;
//object matrix (point)
om[0][0] = p.getX();
om[1][0] = p.getY();
om[2][0] = p.getZ();
om[3][0] = 1;
//we have no world matrix
//fm = multiplyMatrix(pm, cm);
//fm = multiplyMatrix(cm, om);
fm = multiplyMatrix(cm, om);
return new Pixel2D( (int) fm[0][0], (int) fm[1][0], p.getColour());
}for complete source code so far: http://williamchan.brixonsolutions.com/myworks/java/graphics3d/source.phpI can't remember the details of doing a perspective transformation, but what I do remember is that you add an extra column to your data to put it into a 4d space, called homogenous coordinates. Then you apply a linear transformation that maps the viewpoint into a plane in 4d. This causes all the lines that project out from the viewer to be parallel. You can then lose the 4th dimension and the resulting x and y are in perspective and the z is the distance from the viewer. The phrase to google for is "homogenous transformation".
-
Testapplication Engineer LabView - Medical Engineering project in beautiful Austria
----------Please find the English Version attached below----------
Sind Sie auf der Suche nach einer neuen, spannenden Herausforderung?
Für meinen österreichischen Kunden aus der Medizintechnikbranche suche ich einen Testapplication Ingenieur.
Aufgaben:
-verantwortlich für die Softwareentwicklung für das Testing
-Implementierung spezifischer Kundenanforderungen
-Validierung von Messergebnissen
-Fehleranalyse
-Dokumentation
Anforderungen:
-Abschluss in Elektrotechnik oder Nachrichtentechnik
-Sehr gute Kenntnisse in NI LabView und Teststand software
-Erfahrungen im Bereich Elektrotechnik von Vorteil
-Gute Englischkenntnisse
Projektdaten:
-Standort: Österreich
-Laufzeit: mindestens 6 Monate
-attraktive Vergütung
Ich freue mich auf Ihren aktuellen Lebenslauf: [email protected]
Bei Fragen können Sie mich jederzeit unter der 089/55197880 erreichen.
Viele Grüße aus München,
Johannes Donat
Are you currently on the hunt for an exciting job opportunity?
I am looking for a test application engineer for my austrian customer in the field of medical engineering.
Tasks:
-responsible for software design
-testing electronic assemblies
-implementation of specific requirements
Requirements:
-degree in electronics or telecommunications
-very good knowledge in NI LabView
-very good knowledge in TestStand Software
Project data:
-location: Austria
-duration: 6 months
I look forward to your updated CV: [email protected]
Please don't hesitate to contact me at: 0049-89-55197-88009-09-2012
Dear Hiring Manager:
As a Senior LabVIEW Engineer, and long time contributor to the technical ladder, I have expertise in consumer and government communication systems. I have 20 plus years excelling in manufacturing, development, material and reliability engineering. Additionally, I have 10 plus years of automation expertise.
Whether planning for new product introduction or field failure rate improvements, I believe you will find my experience in RF, hardware & software and deployment of root cause analysis methods into key processes, a value-added asset to your programs.
My broad technical skills and leadership abilities have been major contributors to driving cost reduction and corrective action over many new product launches, and I am looking forward to repeating success stories in your group.
Experience has taught me that technical skill alone cannot guarantee meeting all goals and I bring your firm commitment, perseverance, flexibility, and the critical ability to work productively with others in challenging situations.
I welcome the opportunity to speak with you further about how my diverse experience and up-to-date skills will add value to your company’s bottom line.
I look forward to hearing from you directly at (561) 792-6026, (561) 351-4776
Sincerely,
Brian N. Nover
14635 Horseshoe Trace
Wellington, FL 33414
Attachments:
Nover-Brian-Resume-2012RFLV.docx 23 KB -
Im having the following errors when creating a New Team Project by Visual Studio on TFS2012 with a Sharepoint Site...
This problem not occurs when i don't select to create a sharepoint site...
My Sharepoint is 2010 with SP2...
Here is the errors log:
2013-12-05T10:06:10 | Module: Internal | Team Foundation Server proxy retrieved | Completion time: 0 seconds
2013-12-05T10:06:10 | Module: Wizard | Retrieved IAuthorizationService proxy | Completion time: 0 seconds
2013-12-05T10:06:10 | Module: Wizard | Project creation permissions retrieved | Completion time: 0.016 seconds
2013-12-05T10:06:10 | Module: Internal | The template information for Team Foundation Server "srv-tfs2012\TJMTCollection" was retrieved from the Team Foundation Server. | Completion time: 0.047 seconds
2013-12-05T10:06:15 | Module: Engine | Thread: 50 | New project will be created with the "Microsoft Visual Studio Scrum 2.2" methodology
2013-12-05T10:06:15 | Module: Engine | Retrieved IAuthorizationService proxy | Completion time: 0 seconds
2013-12-05T10:06:15 | Module: Engine | Project creation permissions retrieved | Completion time: 0.007 seconds
2013-12-05T10:06:15 | Module: Internal | Team Foundation Server proxy retrieved | Completion time: 0 seconds
2013-12-05T10:06:15 | Module: Internal | The template information for Team Foundation Server "srv-tfs2012\TJMTCollection" was retrieved from the Team Foundation Server. | Completion time: 0.005 seconds
2013-12-05T10:06:15 | Module: Exporter | Wrote compressed process template file | Completion time: 0 seconds
2013-12-05T10:06:16 | Module: Exporter | Extracted process template file | Completion time: 0.448 seconds
2013-12-05T10:06:16 | Module: Engine | Thread: 50 | Starting Project Creation for project "Teste" in domain "srv-tfs2012\TJMTCollection"
2013-12-05T10:06:16 | Module: Engine | The user identity information was retrieved from the Group Security Service | Completion time: 0 seconds
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard is starting to initialize the plug-ins.
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Ms.Internal.LinksCreator.
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Ms.Internal.Groups.
2013-12-05T10:06:16 | Module: CssStructureUploader | Thread: 50 | Entering Initialize in CssStructureUploader
2013-12-05T10:06:16 | Module: CssStructureUploader | Thread: 50 | Initialize for CssStructureUploader complete
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Classification.
2013-12-05T10:06:16 | Module: Rosetta | Thread: 50 | Entering Initialize in RosettaReportUploader
2013-12-05T10:06:16 | Module: Rosetta | Thread: 50 | Exiting Initialize for RosettaReportUploader
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Reporting.
2013-12-05T10:06:16 | Module: WSS | Thread: 50 | Entering Initialize in WssSiteCreator
2013-12-05T10:06:16 | Module: WSS | Thread: 50 | Site information: Title = "Teste" Description = ""
2013-12-05T10:06:16 | Module: WSS | Thread: 50 | Base site url: http://srv-tfs2012/sites/TJMTCollection/Teste
2013-12-05T10:06:16 | Module: WSS | Thread: 50 | Admin site url: http://srv-tfs2012:17012/
2013-12-05T10:06:16 | Module: WSS | Thread: 50 | Exiting Initialize for WssSiteCreator
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Portal.
2013-12-05T10:06:16 | Module: Groups and Permissions | Thread: 50 | Entering Initialize in GssStructureCreator
2013-12-05T10:06:16 | Module: Groups and Permissions | Thread: 50 | Exiting Initialize for GssStructureCreator
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Groups.
2013-12-05T10:06:16 | Module: Work Item Tracking | Thread: 50 | About to begin the creation of project Teste on server srv-tfs2012\TJMTCollection
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.WorkItemTracking.
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.VersionControl.
2013-12-05T10:06:16 | Module: Test Management | Thread: 50 | Initialization of Test Management Plugin for Project Creation Wizard succeeded.
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.TestManagement.
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Build.
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Lab.
2013-12-05T10:06:16 | Module: Initializer | Thread: 50 | The New Team Project Wizard successfully initialized the plug-ins.
2013-12-05T10:06:16 | Module: Engine | Thread: 50 | Process template XML loaded
2013-12-05T10:06:16 | Module: Engine | Thread: 50 | Starting Project Creation Engine execution
2013-12-05T10:06:16 | Module: Engine | Thread: 53 | Running Task "UploadStructure" from Group "Classification"
2013-12-05T10:06:16 | Module: CssStructureUploader | Thread: 53 | Getting CSS proxy
2013-12-05T10:06:16 | Module: CssStructureUploader | Thread: 53 | CSS proxy retrieved
2013-12-05T10:06:16 | Module: CssStructureUploader | Thread: 53 | The uploading of the Classification Service has started
2013-12-05T10:06:16 | Module: CssStructureUploader | Thread: 53 | Uploading CSS structure: "<Nodes><Node StructureType="ProjectLifecycle" Name="Iteration" xmlns=""><Children><Node StructureType="ProjectLifecycle"
Name="Release 1"><Children><Node StructureType="ProjectLifecycle" Name="Sprint 1" /><Node StructureType="ProjectLifecycle" Name="Sprint 2" /><Node StructureType="ProjectLifecycle"
Name="Sprint 3" /><Node StructureType="ProjectLifecycle" Name="Sprint 4" /><Node StructureType="ProjectLifecycle" Name="Sprint 5" /><Node StructureType="ProjectLifecycle" Name="Sprint
6" /></Children></Node><Node StructureType="ProjectLifecycle" Name="Release 2" /><Node StructureType="ProjectLifecycle" Name="Release 3" /><Node StructureType="ProjectLifecycle"
Name="Release 4" /></Children></Node><Node StructureType="ProjectModelHierarchy" Name="Area" xmlns="" /></Nodes>"
2013-12-05T10:06:16 | Module: CssStructureUploader | Thread: 53 | Creating Project : Teste
2013-12-05T10:06:17 | Module: CssStructureUploader | Thread: 53 | Created Project Administrators group S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-0-0-0-0-1 successfully.
2013-12-05T10:06:17 | Module: CssStructureUploader | Thread: 53 | CSS structure upload finished
2013-12-05T10:06:17 | Module: CssStructureUploader | Thread: 53 | Updating project properties for :vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc
2013-12-05T10:06:17 | Module: CssStructureUploader | Thread: 53 | Updating catalog settings for :vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc
2013-12-05T10:06:17 | Module: CssStructureUploader | Thread: 53 | Received 'Teste' team project entity object for :vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc
2013-12-05T10:06:17 | Module: CssStructureUploader | Thread: 53 | Updated team project description: ""
2013-12-05T10:06:17 | Module: Engine | Task "UploadStructure" from Group "Classification" completed with success | Completion time: 0.676 seconds
2013-12-05T10:06:17 | Module: Engine | Thread: 56 | Running Task "" from Group ""
2013-12-05T10:06:17 | Module: Engine | Thread: 49 | Running Task "GroupCreation1" from Group "Groups"
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Entering Execute in GssStructureCreator
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Getting list of structures for: vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "GENERIC_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-2757176466-3218051407-2887278433-795240796" deny: "True"
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Replacing macros: @creator.
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Macros replaced: [Teste]\@creator.
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Adding the following identity to a group: [Teste]\@creator. Group name: Teste Team.
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Creating application group for "Readers" URI "vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc"
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "GENERIC_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-903229747-404692801-3102686175-2727812972" deny: "True"
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "VIEW_TEST_RESULTS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-903229747-404692801-3102686175-2727812972" deny:
"True"
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "GENERIC_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-903229747-404692801-3102686175-2727812972" deny: "True"
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "WORK_ITEM_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-903229747-404692801-3102686175-2727812972" deny: "True"
2013-12-05T10:06:17 | Module: Groups and Permissions | Thread: 49 | Creating application group for "Contributors" URI "vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "GENERIC_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325" deny: "True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "DELETE_TEST_RESULTS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325" deny:
"True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "PUBLISH_TEST_RESULTS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325" deny:
"True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "VIEW_TEST_RESULTS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325" deny:
"True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "GENERIC_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325" deny: "True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "WORK_ITEM_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325" deny: "True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "WORK_ITEM_WRITE" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325" deny:
"True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "MANAGE_TEST_PLANS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325" deny:
"True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "MANAGE_TEST_ENVIRONMENTS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325"
deny: "True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "MANAGE_TEST_CONFIGURATIONS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-4264286424-1586018371-2454857484-902542325"
deny: "True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Replacing macros: @defaultTeam.
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Macros replaced: [Teste]\@defaultTeam.
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding the following identity to a group: [Teste]\@defaultTeam. Group name: Contributors.
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Creating application group for "Build Administrators" URI "vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "GENERIC_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003" deny: "True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "DELETE_TEST_RESULTS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003" deny:
"True"
2013-12-05T10:06:18 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "PUBLISH_TEST_RESULTS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003"
deny: "True"
2013-12-05T10:06:19 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "VIEW_TEST_RESULTS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003" deny:
"True"
2013-12-05T10:06:19 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "GENERIC_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003" deny: "True"
2013-12-05T10:06:19 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "WORK_ITEM_READ" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003" deny:
"True"
2013-12-05T10:06:19 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "WORK_ITEM_WRITE" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003" deny:
"True"
2013-12-05T10:06:19 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "MANAGE_TEST_PLANS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003" deny:
"True"
2013-12-05T10:06:19 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "MANAGE_TEST_ENVIRONMENTS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003"
deny: "True"
2013-12-05T10:06:19 | Module: Groups and Permissions | Thread: 49 | Adding access entry - actionName "MANAGE_TEST_CONFIGURATIONS" sid: "S-1-9-1551374245-1609553727-2111082564-2151496797-660325100-1-1182136727-3720210756-2911721059-2444575003"
deny: "True"
2013-12-05T10:06:19 | Module: Groups and Permissions | Thread: 49 | Exiting Execute for GssStructureCreator
2013-12-05T10:06:19 | Module: Engine | Task "GroupCreation1" from Group "Groups" completed with success | Completion time: 1.822 seconds
2013-12-05T10:06:19 | Module: Engine | Thread: 53 | Running Task "" from Group ""
2013-12-05T10:06:19 | Module: Engine | Thread: 56 | Running Task "LinkTypes" from Group "WorkItemTracking"
2013-12-05T10:06:19 | Module: Work Item Tracking | Thread: 56 | Synchronizing users and groups.
2013-12-05T10:06:20 | Module: Work Item Tracking | Thread: 56 | Synchronizing CSS structures.
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 56 | LinkType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\LinkTypes\SharedStep.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 56 | LinkType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\LinkTypes\TestedBy.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 56 | Uploading link types from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\LinkTypes\SharedStep.xml'...
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 56 | Uploaded LinkType definitions from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\LinkTypes\SharedStep.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 56 | Uploading link types from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\LinkTypes\TestedBy.xml'...
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 56 | Uploaded LinkType definitions from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\LinkTypes\TestedBy.xml
2013-12-05T10:06:21 | Module: Engine | Task "LinkTypes" from Group "WorkItemTracking" completed with success | Completion time: 1.717 seconds
2013-12-05T10:06:21 | Module: Engine | Thread: 53 | Running Task "WITs" from Group "WorkItemTracking"
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\Task.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\Bug.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\CodeReviewRequest.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\CodeReviewResponse.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\FeedbackRequest.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\FeedbackResponse.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\Impediment.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\ProductBacklogItem.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\SharedStep.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | WorkItemType definition file found: C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\TestCase.xml
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\Task.xml'...
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\Task.xml.
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\Bug.xml'...
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\Bug.xml.
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\CodeReviewRequest.xml'...
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\CodeReviewRequest.xml.
2013-12-05T10:06:21 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\CodeReviewResponse.xml'...
2013-12-05T10:06:22 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\CodeReviewResponse.xml.
2013-12-05T10:06:22 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\FeedbackRequest.xml'...
2013-12-05T10:06:22 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\FeedbackRequest.xml.
2013-12-05T10:06:22 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\FeedbackResponse.xml'...
2013-12-05T10:06:22 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\FeedbackResponse.xml.
2013-12-05T10:06:22 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\Impediment.xml'...
2013-12-05T10:06:22 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\Impediment.xml.
2013-12-05T10:06:22 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\ProductBacklogItem.xml'...
2013-12-05T10:06:23 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\ProductBacklogItem.xml.
2013-12-05T10:06:23 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\SharedStep.xml'...
2013-12-05T10:06:23 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\SharedStep.xml.
2013-12-05T10:06:23 | Module: Work Item Tracking | Thread: 53 | Uploading work item type from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\TestCase.xml'...
2013-12-05T10:06:23 | Module: Work Item Tracking | Thread: 53 | Uploaded WorkItemType definition from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\TypeDefinitions\TestCase.xml.
2013-12-05T10:06:23 | Module: Engine | Task "WITs" from Group "WorkItemTracking" completed with success | Completion time: 2.825 seconds
2013-12-05T10:06:23 | Module: Engine | Thread: 34 | Running Task "Categories" from Group "WorkItemTracking"
2013-12-05T10:06:23 | Module: Engine | Thread: 56 | Running Task "Queries" from Group "WorkItemTracking"
2013-12-05T10:06:23 | Module: Work Item Tracking | Thread: 34 | Uploading categories from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Categories.xml'...
2013-12-05T10:06:23 | Module: Work Item Tracking | Thread: 56 | Group [SERVER]\Project Collection Administrators was granted the following permissions: Read, Contribute, Delete, ManagePermissions, FullControl
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | Group [vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc]\Project Administrators was granted the following permissions: Read, Contribute, Delete, ManagePermissions, FullControl
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | Group [vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc]\Readers was granted the following permissions: Read
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | Group [vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc]\Contributors was granted the following permissions: Read
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | Group [vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc]\Build Administrators was granted the following permissions: Read
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query was found in C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\ProductBacklog.wiq: Product Backlog
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query has been imported from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\ProductBacklog.wiq: Product Backlog
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query was found in C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\Feedback.wiq: Feedback
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query has been imported from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\Feedback.wiq: Feedback
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query folder was found: Current Sprint
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query folder has been created: Current Sprint
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query was found in C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\OpenImpediments.wiq: Current Sprint/Open Impediments
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query has been imported from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\OpenImpediments.wiq: Current Sprint/Open Impediments
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query was found in C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\BlockedTasks.wiq: Current Sprint/Blocked Tasks
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query has been imported from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\BlockedTasks.wiq: Current Sprint/Blocked Tasks
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query was found in C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\WorkInProgress.wiq: Current Sprint/Work in Progress
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query has been imported from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\WorkInProgress.wiq: Current Sprint/Work in Progress
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query was found in C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\UnfinishedWork.wiq: Current Sprint/Unfinished Work
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query has been imported from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\UnfinishedWork.wiq: Current Sprint/Unfinished Work
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query was found in C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\SprintBacklog.wiq: Current Sprint/Sprint Backlog
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query has been imported from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\SprintBacklog.wiq: Current Sprint/Sprint Backlog
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query was found in C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\TestCases.wiq: Current Sprint/Test Cases
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 56 | The following query has been imported from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Queries\TestCases.wiq: Current Sprint/Test Cases
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 34 | Uploaded work item types categories from C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\WorkItem Tracking\Categories.xml.
2013-12-05T10:06:24 | Module: Engine | Task "Categories" from Group "WorkItemTracking" completed with success | Completion time: 0.182 seconds
2013-12-05T10:06:24 | Module: Engine | Thread: 53 | Running Task "ProcessConfiguration" from Group "WorkItemTracking"
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 53 | Processing element CommonConfiguration.
2013-12-05T10:06:24 | Module: Engine | Task "Queries" from Group "WorkItemTracking" completed with success | Completion time: 0.431 seconds
2013-12-05T10:06:24 | Module: Work Item Tracking | Thread: 53 | Processing element AgileConfiguration.
2013-12-05T10:06:24 | Module: Engine | Task "ProcessConfiguration" from Group "WorkItemTracking" completed with success | Completion time: 0.589 seconds
2013-12-05T10:06:24 | Module: Engine | Thread: 49 | Running Task "" from Group ""
2013-12-05T10:06:24 | Module: Engine | Thread: 34 | Running Task "TestVariable" from Group "TestManagement"
2013-12-05T10:06:24 | Module: Engine | Thread: 44 | Running Task "TestResolutionState" from Group "TestManagement"
2013-12-05T10:06:24 | Module: Engine | Thread: 39 | Running Task "TestSettings" from Group "TestManagement"
2013-12-05T10:06:24 | Module: Engine | Thread: 37 | Running Task "VersionControlTask" from Group "VersionControl"
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | <permission allow="Read, PendChange, Checkin, Label, Lock, ReviseOther, UnlockOther, UndoOther, LabelOther, AdminProjectRights, CheckinOther, Merge, ManageBranch" identity="[$$PROJECTNAME$$]\$$PROJECTADMINGROUP$$"
/>
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | Allowing permission(s) Read, PendChange, Checkin, Label, Lock, ReviseOther, UnlockOther, UndoOther, LabelOther, AdminProjectRights, CheckinOther, Merge, ManageBranch to group [vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc]\Project
Administrators
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | <permission allow="Read, PendChange, Checkin, Label, Lock, Merge" identity="[$$PROJECTNAME$$]\Contributors" />
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | Allowing permission(s) Read, PendChange, Checkin, Label, Lock, Merge to group [vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc]\Contributors
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | <permission allow="Read, PendChange, Checkin, Label, Lock, Merge" identity="[$$PROJECTNAME$$]\Build Administrators" />
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | Allowing permission(s) Read, PendChange, Checkin, Label, Lock, Merge to group [vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc]\Build Administrators
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | <permission allow="Read" identity="[$$PROJECTNAME$$]\Readers" />
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | Allowing permission(s) Read to group [vstfs:///Classification/TeamProject/169e471b-5e7c-4168-9c13-ddd37d64b1dc]\Readers
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | Changing project setting ExclusiveCheckout to "False"
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | Changing project setting GetLatestOnCheckout to "False"
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | User chose to create new empty folder $/Teste
2013-12-05T10:06:24 | Module: SccTask | Thread: 37 | No xml nodes of type "checkin_note" were found in the task xml
2013-12-05T10:06:24 | Module: Test Management | Thread: 34 | Proper team project 'Teste' permissions are added to group 'S-1-9-1551374245-1204400969-2402986413-2179408616-0-0-0-4-1'.
2013-12-05T10:06:24 | Module: Test Management | Thread: 34 | Uploading TestVariable from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\Test Management\TestVariable.xml'...
2013-12-05T10:06:24 | Module: Test Management | Thread: 39 | Uploading TestSettings from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\Test Management\TestSettings.xml'...
2013-12-05T10:06:24 | Module: Test Management | Thread: 44 | Uploading TestResolutionState from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\Test Management\TestResolutionState.xml'...
2013-12-05T10:06:24 | Module: Test Management | Thread: 39 | Uploaded TestSettings from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\Test Management\TestSettings.xml'.
2013-12-05T10:06:24 | Module: Engine | Task "TestSettings" from Group "TestManagement" completed with success | Completion time: 0.161 seconds
2013-12-05T10:06:24 | Module: Test Management | Thread: 34 | Uploaded TestVariable from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\Test Management\TestVariable.xml'.
2013-12-05T10:06:24 | Module: Engine | Task "TestVariable" from Group "TestManagement" completed with success | Completion time: 0.174 seconds
2013-12-05T10:06:24 | Module: Engine | Thread: 49 | Running Task "TestConfiguration" from Group "TestManagement"
2013-12-05T10:06:24 | Module: Test Management | Thread: 49 | Uploading TestConfiguration from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\Test Management\TestConfiguration.xml'...
2013-12-05T10:06:24 | Module: Test Management | Thread: 44 | Uploaded TestResolutionState from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\Test Management\TestResolutionState.xml'.
2013-12-05T10:06:24 | Module: Engine | Task "TestResolutionState" from Group "TestManagement" completed with success | Completion time: 0.183 seconds
2013-12-05T10:06:24 | Module: Test Management | Thread: 49 | Uploaded TestConfiguration from file 'C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp\Test Management\TestConfiguration.xml'.
2013-12-05T10:06:24 | Module: Engine | Task "TestConfiguration" from Group "TestManagement" completed with success | Completion time: 0.012 seconds
2013-12-05T10:06:24 | Module: Engine | Thread: 56 | Running Task "" from Group ""
2013-12-05T10:06:24 | Module: Engine | Task "VersionControlTask" from Group "VersionControl" completed with success | Completion time: 0.189 seconds
2013-12-05T10:06:24 | Module: Engine | Thread: 39 | Running Task "" from Group ""
2013-12-05T10:06:24 | Module: Engine | Thread: 53 | Running Task "BuildTask" from Group "Build"
2013-12-05T10:06:24 | Module: Engine | Thread: 34 | Running Task "Site" from Group "Reporting"
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <ProcessTemplate Type="Default" Filename="Build\Templates\DefaultTemplate.11.1.xaml" Description="This is the default build process template for this
Team Project." ServerPath="$/$$PROJECTNAME$$/BuildProcessTemplates" />
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <ProcessTemplate Type="Upgrade" Filename="Build\Templates\UpgradeTemplate.xaml" Description="This is the upgrade build process template for this Team
Project." ServerPath="$/$$PROJECTNAME$$/BuildProcessTemplates" />
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <ProcessTemplate Type="Custom" Filename="Build\Templates\AzureContinuousDeployment.11.xaml" Description="This is the build process template for continuous
delivery in this Team Project." ServerPath="$/$$PROJECTNAME$$/BuildProcessTemplates" />
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <Permission allow="ViewBuilds, ViewBuildDefinition" identity="[$$PROJECTNAME$$]\Readers" />
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | Allowing permission(s) ViewBuilds, ViewBuildDefinition to account [Teste]\Readers.
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <Permission allow="EditBuildQuality, ViewBuilds, QueueBuilds, ViewBuildDefinition" identity="[$$PROJECTNAME$$]\Contributors" />
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | Allowing permission(s) EditBuildQuality, ViewBuilds, QueueBuilds, ViewBuildDefinition to account [Teste]\Contributors.
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <Permission allow="DeleteBuilds, DestroyBuilds, EditBuildQuality, ManageBuildQualities, RetainIndefinitely, ViewBuilds, ManageBuildQueue, QueueBuilds, StopBuilds, DeleteBuildDefinition,
EditBuildDefinition, ViewBuildDefinition, AdministerBuildPermissions" identity="[$$PROJECTNAME$$]\Build Administrators" />
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | Allowing permission(s) DeleteBuilds, DestroyBuilds, EditBuildQuality, ManageBuildQualities, RetainIndefinitely, ViewBuilds, ManageBuildQueue, QueueBuilds, StopBuilds, DeleteBuildDefinition,
EditBuildDefinition, ViewBuildDefinition, AdministerBuildPermissions to account [Teste]\Build Administrators.
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <Permission allow="DeleteBuilds, DestroyBuilds, EditBuildQuality, ManageBuildQualities, RetainIndefinitely, ViewBuilds, ManageBuildQueue, QueueBuilds, StopBuilds, DeleteBuildDefinition,
EditBuildDefinition, ViewBuildDefinition, AdministerBuildPermissions" identity="[$$PROJECTNAME$$]\$$PROJECTADMINGROUP$$" />
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | Allowing permission(s) DeleteBuilds, DestroyBuilds, EditBuildQuality, ManageBuildQualities, RetainIndefinitely, ViewBuilds, ManageBuildQueue, QueueBuilds, StopBuilds, DeleteBuildDefinition,
EditBuildDefinition, ViewBuildDefinition, AdministerBuildPermissions to account [Teste]\Project Administrators.
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <Permission allow="EditBuildQuality, ManageBuildQueue, OverrideBuildCheckInValidation, QueueBuilds, UpdateBuildInformation, ViewBuildDefinition, ViewBuilds" identity="$$PROJECTCOLLECTIONBUILDSERVICESGROUP$$"
/>
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | Allowing permission(s) EditBuildQuality, ManageBuildQueue, OverrideBuildCheckInValidation, QueueBuilds, UpdateBuildInformation, ViewBuildDefinition, ViewBuilds to account Project
Collection Build Service Accounts.
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <Permission allow="ViewBuildDefinition, EditBuildDefinition, DeleteBuildDefinition, QueueBuilds, ManageBuildQueue, StopBuilds, ViewBuilds, EditBuildQuality, RetainIndefinitely,
DeleteBuilds, ManageBuildQualities, DestroyBuilds, AdministerBuildPermissions" identity="$$PROJECTCOLLECTIONBUILDADMINSGROUP$$" />
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | Allowing permission(s) ViewBuildDefinition, EditBuildDefinition, DeleteBuildDefinition, QueueBuilds, ManageBuildQueue, StopBuilds, ViewBuilds, EditBuildQuality, RetainIndefinitely,
DeleteBuilds, ManageBuildQualities, DestroyBuilds, AdministerBuildPermissions to account Project Collection Build Administrators.
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | <Permission allow="DeleteBuilds, DestroyBuilds, EditBuildQuality, ManageBuildQualities, RetainIndefinitely, ViewBuilds, ManageBuildQueue, QueueBuilds, StopBuilds, DeleteBuildDefinition,
EditBuildDefinition, ViewBuildDefinition, AdministerBuildPermissions, OverrideBuildCheckInValidation" identity="$$PROJECTCOLLECTIONADMINGROUP$$" />
2013-12-05T10:06:24 | Module: Microsoft.ProjectCreationWizard.Build | Thread: 53 | Allowing permission(s) DeleteBuilds, DestroyBuilds, EditBuildQuality, ManageBuildQualities, RetainIndefinitely, ViewBuilds, ManageBuildQueue, QueueBuilds, StopBuilds, DeleteBuildDefinition,
EditBuildDefinition, ViewBuildDefinition, AdministerBuildPermissions, OverrideBuildCheckInValidation to account Project Collection Administrators.
2013-12-05T10:06:24 | Module: Rosetta | Thread: 34 | Creating site: /TfsReports/TJMTCollection/Teste
2013-12-05T10:06:25 | Module: Engine | Task "Site" from Group "Reporting" completed with success | Completion time: 0.253 seconds
2013-12-05T10:06:25 | Module: Engine | Thread: 25 | Running Task "Populate Reports" from Group "Reporting"
2013-12-05T10:06:25 | Module: Rosetta | Thread: 25 | Creating folder: /TfsReports/TJMTCollection/Teste/Builds
2013-12-05T10:06:25 | Module: Rosetta | Thread: 25 | Creating folder: /TfsReports/TJMTCollection/Teste/Tests
2013-12-05T10:06:25 | Module: Rosetta | Thread: 25 | Creating report: /TfsReports/TJMTCollection/Teste/Backlog Overview
2013-12-05T10:06:25 | Module: Engine | Task "BuildTask" from Group "Build" completed with success | Completion time: 0.591 seconds
2013-12-05T10:06:25 | Module: Engine | Thread: 37 | Running Task "" from Group ""
2013-12-05T10:06:25 | Module: Engine | Thread: 39 | Running Task "LabTask" from Group "Lab"
2013-12-05T10:06:25 | Module: LabTask | Thread: 39 | <permission allow="Read, Create, Write, Edit, Delete, Start, Stop, Pause, ManageSnapshots, ManageLocation, DeleteLocation, ManagePermissions, ManageChildPermissions, ManageTestMachines" identity="$$PROJECTCOLLECTIONADMINGROUP$$"
/>
2013-12-05T10:06:25 | Module: LabTask | Thread: 39 | <permission allow="Read, Create, Write, Edit, Delete, Start, Stop, Pause, ManageSnapshots, ManageLocation, DeleteLocation, ManageChildPermissions, ManageTestMachines" identity="[$$PROJECTNAME$$]\$$PROJECTADMINGROUP$$"
/>
2013-12-05T10:06:25 | Module: LabTask | Thread: 39 | <permission allow="Read, Create, Write, Edit, Start, Stop, Pause, ManageSnapshots" identity="[$$PROJECTNAME$$]\Contributors" />
2013-12-05T10:06:25 | Module: LabTask | Thread: 39 | <permission allow="Read" identity="[$$PROJECTNAME$$]\Readers" />
2013-12-05T10:06:25 | Module: LabTask | Thread: 39 | <permission allow="Read, Write, Edit, Start, Stop, Pause, ManageSnapshots" identity="$$BUILDSERVICEGROUP$$" />
2013-12-05T10:06:25 | Module: Rosetta | Thread: 25 | Setting data sources for report: /TfsReports/TJMTCollection/Teste/Backlog Overview
2013-12-05T10:06:25 | Module: Rosetta | Thread: 25 | Creating report: /TfsReports/TJMTCollection/Teste/Builds/Build Summary
2013-12-05T10:06:25 | Module: Microsoft.ProjectCreationWizard.Lab | Thread: 39 | <ProcessTemplate Type="Custom" Filename="Lab\Templates\LabDefaultTemplate.11.xaml" Description="This is the default Lab process template for this Team
Project." ServerPath="$/$$PROJECTNAME$$/BuildProcessTemplates" />
2013-12-05T10:06:25 | Module: Engine | Task "LabTask" from Group "Lab" completed with success | Completion time: 0.559 seconds
2013-12-05T10:06:25 | Module: Engine | Thread: 49 | Running Task "" from Group ""
2013-12-05T10:06:26 | Module: Rosetta | Thread: 25 | Setting data sources for report: /TfsReports/TJMTCollection/Teste/Builds/Build Summary
2013-12-05T10:06:26 | Module: Rosetta | Thread: 25 | Creating report: /TfsReports/TJMTCollection/Teste/Builds/Build Success Over Time
2013-12-05T10:06:26 | Module: Rosetta | Thread: 25 | Setting data sources for report: /TfsReports/TJMTCollection/Teste/Builds/Build Success Over Time
2013-12-05T10:06:26 | Module: Rosetta | Thread: 25 | Creating report: /TfsReports/TJMTCollection/Teste/Sprint Burndown
2013-12-05T10:06:26 | Module: Rosetta | Thread: 25 | Setting data sources for report: /TfsReports/TJMTCollection/Teste/Sprint Burndown
2013-12-05T10:06:26 | Module: Rosetta | Thread: 25 | Creating report: /TfsReports/TJMTCollection/Teste/Release Burndown
2013-12-05T10:06:27 | Module: Rosetta | Thread: 25 | Setting data sources for report: /TfsReports/TJMTCollection/Teste/Release Burndown
2013-12-05T10:06:27 | Module: Rosetta | Thread: 25 | Creating report: /TfsReports/TJMTCollection/Teste/Tests/Test Case Readiness
2013-12-05T10:06:27 | Module: Rosetta | Thread: 25 | Setting data sources for report: /TfsReports/TJMTCollection/Teste/Tests/Test Case Readiness
2013-12-05T10:06:27 | Module: Rosetta | Thread: 25 | Creating report: /TfsReports/TJMTCollection/Teste/Tests/Test Plan Progress
2013-12-05T10:06:27 | Module: Rosetta | Thread: 25 | Setting data sources for report: /TfsReports/TJMTCollection/Teste/Tests/Test Plan Progress
2013-12-05T10:06:27 | Module: Rosetta | Thread: 25 | Creating report: /TfsReports/TJMTCollection/Teste/Velocity
2013-12-05T10:06:28 | Module: Rosetta | Thread: 25 | Setting data sources for report: /TfsReports/TJMTCollection/Teste/Velocity
2013-12-05T10:06:28 | Module: Engine | Task "Populate Reports" from Group "Reporting" completed with success | Completion time: 3.176 seconds
2013-12-05T10:06:28 | Module: Engine | Thread: 44 | Running Task "" from Group ""
2013-12-05T10:06:28 | Module: Engine | Thread: 49 | Running Task "SharePointPortal" from Group "Portal"
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Language id: 1033
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Creating site with the following parameters
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Site Url: http://srv-tfs2012/sites/TJMTCollection/Teste
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Site Title: Teste
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Site Description:
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Locale: 1033
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Template: Team Foundation Server Project Portal
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Owner Login: PJMT\23571
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Owner Name: João Vitor Paes de Barros do Carmo
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | Owner Email:
---begin Exception entry---
Time: 2013-12-05T10:06:28
Module: WSS
Exception Message: Server was unable to process request. ---> Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (type SoapException)SoapException Details: <soap:Detail xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
/>
Exception Stack Trace: at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.HandleReply(TfsClientOperation operation, TfsMessage message, Object[]& outputs)
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.Invoke(TfsClientOperation operation, Object[] parameters, TimeSpan timeout, Object[]& outputs)
at Microsoft.TeamFoundation.Client.SharePoint.SharePointTeamFoundationIntegrationService.CreateSite(String webApplicationUrl, String absolutePath, String title, String description, UInt32 localeId, String template, Boolean templateIsTitle, String
ownerLogin, String ownerName, String ownerEmail, Guid applicationInstanceId, Guid projectCollectionId)
at Microsoft.TeamFoundation.Client.SharePoint.WssUtilities.CreateSite(ICredentials credentials, Uri adminUrl, WssSiteData siteCreationData, Guid configurationServerId, Guid projectCollectionId)
at Microsoft.TeamFoundation.Client.SharePoint.WssUtilities.CreateSite(WssSiteData siteCreationData, TfsConnection tfs, Uri adminUrl)
at Microsoft.VisualStudio.TeamFoundation.PCW.WssSiteCreator.CreateSite(WssSiteData siteCreationData, TfsTeamProjectCollection tfs, Uri adminUrl)
at Microsoft.VisualStudio.TeamFoundation.PCW.WssSiteCreator.HandleSiteCreation(WssCreationContextWrapper contextWrapper, XmlNode taskNode)
--- end Exception entry ---
---begin Exception entry---
Time: 2013-12-05T10:06:28
Module: WSS
Exception Message: TF250025: The following URL does not point to a valid SharePoint site: http://srv-tfs2012/sites/TJMTCollection/Teste. Verify that you have the correct URL and that it points to a SharePoint site. (type TeamFoundationServerException)
Exception Stack Trace: at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.HandleReply(TfsClientOperation operation, TfsMessage message, Object[]& outputs)
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.Invoke(TfsClientOperation operation, Object[] parameters, TimeSpan timeout, Object[]& outputs)
at Microsoft.TeamFoundation.Client.SharePoint.SharePointTeamFoundationIntegrationService.GetWebIdentifier(String absolutePath)
at Microsoft.TeamFoundation.Client.SharePoint.WssUtilities.GetWebIdentifier(ICredentials credentials, Uri url)
at Microsoft.VisualStudio.TeamFoundation.PCW.WssSiteCreator.HandleSiteCreation(WssCreationContextWrapper contextWrapper, XmlNode taskNode)
Inner Exception Details:
Exception Message: TF250025: The following URL does not point to a valid SharePoint site: http://srv-tfs2012/sites/TJMTCollection/Teste. Verify that you have the correct URL and that it points to a SharePoint site. (type SoapException)SoapException Details:
<detail exceptionType="TeamFoundationServerException" />
Exception Stack Trace:
--- end Exception entry ---
2013-12-05T10:06:28 | Module: WSS | Thread: 49 | TF30267: Exception: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at Microsoft.VisualStudio.TeamFoundation.PCW.WssSiteCreator.HandleSiteCreation(WssCreationContextWrapper contextWrapper, XmlNode taskNode)
at Microsoft.VisualStudio.TeamFoundation.PCW.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
---begin Exception entry---
Time: 2013-12-05T10:06:28
Module: Engine
Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: An error occurred in the New Team Project Wizard while attempting to create a site on the following SharePoint Web application: srv-tfs2012.
Exception Details: The Project Creation Wizard encountered a problem while uploading documents to the following server running SharePoint Products: srv-tfs2012. The reason for the failure cannot be determined at this time. Because the operation failed, the
wizard was not able to finish creating the team project.
Stack Trace:
at Microsoft.VisualStudio.TeamFoundation.PCW.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
at Microsoft.VisualStudio.TeamFoundation.PCW.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
at Microsoft.VisualStudio.TeamFoundation.PCW.ProjectCreationEngine.RunTask(Object taskObj)
-- Inner Exception --
Exception Message: Server was unable to process request. ---> Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (type SoapException)SoapException Details: <soap:Detail xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
/>
Exception Stack Trace: at Microsoft.VisualStudio.TeamFoundation.PCW.WssSiteCreator.HandleSiteCreation(WssCreationContextWrapper contextWrapper, XmlNode taskNode)
at Microsoft.VisualStudio.TeamFoundation.PCW.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
--- end Exception entry ---
2013-12-05T10:06:28 | Module: Engine | Thread: 49 | TF30202: Task "" from Group "" will not be run because a prior task failed.
2013-12-05T10:06:28 | Module: Engine | Thread: 50 | Deleting from Build ...
2013-12-05T10:06:28 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:28 | Module: Engine | Thread: 50 | Deleting from Version Control ...
2013-12-05T10:06:28 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:28 | Module: Engine | Thread: 50 | Deleting from Work Item Tracking ...
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Deleting from TestManagement ...
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Deleting from Git ...
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Deleting from ProcessManagement ...
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Deleting from LabManagement ...
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Deleting from ProjectServer ...
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Deleting Report Server files ...
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Warning. Did not find SharePoint site service.
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Deleting from Team Foundation Core ...
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Done
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | The project Teste was deleted successfully.
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | Attempting to delete folder "C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp"
2013-12-05T10:06:29 | Module: Engine | Thread: 50 | The folder C:\Users\23571\AppData\Local\Temp\TPW_tmpA31.tmp was removed.Hi,
According to your post, my understanding is that you had Errors TF30162 and TF250025 when creating a New Team Project in TFS2012 with Sharepoint Site on Visual Studio.
The Errors TF30162 seemed that the reports for TFS could not be uploaded due a permission problem. The fix was really easy.
Go to your team foundation server
Open the administration console.
Click on Reporting
Click on Edit
Click on Reports Tab
Enter the credential for the Reports
Save
Click on Start Jobs
In addtion, the problem may be due to the caching done by Team Explorer in Visual Studio. Exiting the copy of VS on the client and reloading it will fix the problem as the updated team process settings will cached locally.
To resolve the Errors TF250025, you will need to register a new internal URL for the SharePoint site using Alternate Access Mappings.
Here are two great blogs for you to take a look at:
http://blogbaris.blogspot.in/2012_08_01_archive.html
http://petersullivan.com.au/2009/11/23/tf250025-and-tf262600-errors-on-team-foundation-server-tfs-2010-project-portal-dashboard/
If still no help, for quick and accurate answers to your questions, it is recommended that you initial a new thread in Visual Studio Team Foundation Server forums.
Team Foundation Server – General:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=tfsgeneral
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support -
Auto project triggering when multiple FG line item's in sales order
Dear Friends,
I am working on engineering project scenario mainly all are the Customer projects.
Basically my client executes Customer projects for Establishing Dairy Plant, Pharma Plant, and Chemical Plant. For that they manufacture various FG assemblies & delivers to Customer site & accordingly Billing will be done to Customer.
Here my area of concern is for any single customer project for Ex. u201CSetting up Dairy Plantu201D requires multiple FG assemblies. For example in this case 20 FG assemblies to be manufactured & delivered to customer & accordingly billing will be done.
By using strategy group u201C21u201D Make-to-order prod. / Project settlement Can is it possible to trigger the project at sales order level with multiple FG assemblies as a multiple line items in sales order. For example, 20 FG assemblies.
If it is possible then what are the prerequisite configurations needs to be done from PS, SD & MM module.
I think strategy group u201C85u201D Assembly processing with network/project will not be applicable in above scenario. This strategy group is applicable for single FG line item in Sales Order not for multiple line items.
Kindly guide me how to overcome from above scenario.
Thanks & Regards,
PrasadHi Ahmed,
Thanks for quick response....
Can you explore about strategy u201C21u201D Make-to-order prod. / Project settlement.
By using strategy group u201C21u201D Make-to-order prod. / Project settlement Can is it possible to trigger the project at sales order level with multiple FG assemblies as a multiple line items in sales order. For example, 20 FG assemblies.
If it is possible then what are the prerequisite configurations needs to be done from PS, SD & MM module
Thanks & Regards,
Sandeep -
Senior Project Engineer Postion - Bloomy Controls, Milford, MA
Senior Project Engineer Postion - Bloomy Controls, Milford, MA
Purpose
Lead the development of automated test, data acquisition, and control systems. Involves extensive customer contact and moderate travel within New England. Contribute to system designs and specifications.
Requirements
- BS in Science or Engineering. EE Preferred. MS a plus
- Ten years of overall test, measurement, automation, and control engineering experience
- 5+ years LabVIEW required. TestStand, LabWindows/CVI or C/C++ experience desired
- DAQ, PXI, GPIB, VXI, vision, motion experience
- Experience writing requirements, documentation, UML
- Strong mathematics background, including signal processing in time and frequency domains
- Excellent verbal and written communication skills
- Experience in a variety of industries, such as electronics, communications, life sciences, power/energy, a plus
Responsibilities
- Write project specifications and system designs
- Design, develop, implement and document Test and Measurement applications using LabVIEW and TestStand
- Serve as technical mentor for less experienced engineers
- Devise, document, and oversee execution of test strategies
- Participate in tradeshows, conferences, seminars, and events
- Write technical papers and give presentations on applications
- Flexible career path may include principal engineering, project management, sales engineering, or engineering management
Note
- Candidates must be legally authorized to work in the United States. Bloomy Controls will not sponsor a new visa or transfer an existing one.
About Bloomy Controls
Bloomy Controls provides automated test, data acquisition, and control systems that help customers throughout the Northeast United States increase productivity, improve quality, and reduce costs. We support leading companies in a variety of industries, including aerospace, electronics, and life sciences.
Our employees enjoy highly stimulating and challenging work. We provide a creative, collaborative environment that is committed to your professional development and growth.
Send your resume to [email protected]PPB,
Thanks for the posting. I just sent my resume and coverletter to the email address you listed. I look forward to hearing from you.
Respectfully,
Dave Lehman -
Primavera Vs MS Project with Projects R12
I am looking to find out whether people recommend Primavera or Microsoft Project for integration with Projects R12, and why they recommend it.
I do not know which of the two to choose. It is a company of 150 staff with complex engineering projects and manufacturing.
Thanks,
MattI would recommend use Primavera for project management and Oracle projects for Costing and Billing.
1. Primavera is userfriendly compare to oracle project management.
2. Primavera allows scheduling.
3. Easy Resource management functionalities
But primavera has a very limited integration with Oracle Project through AIA PIP. You may need to build custom integarations based on your need.
Thanks
Govind -
Project Manager: Dealing with FOLDERS that contain audio?
Hello everyone,
I just started using Project Manager, and I'm in the process of reorganizing files. Upon examination, I've found I dont like the current location of some folders that contain audio files and would like to move them. I know its possible to "cut & paste" audio files into new places, but the manual says nothing about folders of audio and how to move them. Is there a way to do this in PM?
Along the same lines, I dont like the names I have given to some folders and want to change them. Again, the manual shows how to change audio file names, but NOT folder names. I'm assuming folder names are just as important in searching databases correctly as file names, so is it possible to change these in PM?
The only solution I've found to both problems is to create new folders in the finder and cut/past the audio files in PM? Seems kind of ridiculous to have to use two "programs" (finder & PM) just to move/rename folders, thus I wanted to check here first and make sure I'm doing it right. Is there another way
Sorry for the stupid question. We now return you to your regularly scheduled programing...Hmmmm... this is one of those cans-of-worms situations... The PM has a "move" function, but judging by the menu choices, no "rename" function.
If you went into an individual song and usde the "move audio file(s)" function in the audio window, you could create a new folder (with the name you want) when the file selector opens; then you've save (actually, move) the files into that new folder. Then, re-save your song/project.
The downside to doing this is that other songs (previous versions, backups, etc.) will not find those audio files any longer (because the folder that originally contained those files is now empty). So Logic will invoke the search engine/project manager to find them.
If the PM has been updated, this might not end up being a problem. But unless the names of those audio files have unique names, when you update PM, it will ask you which of the similarly-named files you want to choose to resolve the references for those other songs. It might mean that you spend a bit of time in front of the PM answering dialogs about it.
I think you have to try this out to see if it works well or not.
-=iS=- -
Website Categorization in j2ee project
Hi all,
i am working in a search engine project now. I have to categorize the web sites when they are listed, that is type of website also should be included in result like e-commerce site,educational site,information site or general site like that.
Is there any standard way for this?
Otherwise how i can achieve this requiremnet?
help me pleasePreparedStatements are always worth the extra time as they isolate you from the independant database formatting requirements. Plus in a real world scenario this would be a statement that would be executed multiple times, which would provide a sizable speed increase on the 2+ request.
With PreparedStatements you also don't have to worry about encoding/decoding any text a user might enter, it gets encoded for you automatically. This in itself will prevent most SQL injection attacks, which cannot be a bad thing. -
Civil Engineering Applications
I am new to spatial and want to use spatial for civil engineering projects.
1.Can I use oracle 10g express edition + html DB + map viewer.
2. How to start.
I have worked on oracle Db,JSP,9ias ,D2k .SEVERE: Unsuccessful: create table ASSET_REFERENCE (ASSET_REFERENCE_ID number(19,0) not null, ASSET_NAME varchar2(256 char), ASSET_URI varchar2(256 char), SPATIAL_EXTENT mdsys.sdo_geometry, START_DATE timestamp, END_DATE timestamp, COORD_SYS_WKS varchar2(256 char), primary key (ASSET_REFERENCE_ID))
[hibernatetool] Nov 21, 2005 7:56:50 PM org.hibernate.tool.hbm2ddl.SchemaExport create
[hibernatetool] SEVERE: ORA-00902: invalid datatype
The lack of sdo in XE is a deal breaker for us. Very disappointing. It looks like we are going with PostGIS. The GeoTools project was looking at adding spatial to Derby. I thought XE was too good to be true. -
Variant Configuration
Variant configuration is for manufacturing complex products in which customer determines the features of the product. Objective of variant configuration is to react quickly to customers' requirements.
Here it needs not to create separate material for each variant of a product. When companies introduce variant configuration this often goes beyond a business process re-engineering project. Variant configuration offers an opportunity to restructure product structures for which then processes are defined. This has a direct impact to the core areas such as marketing and product data management.
2 Advantages of VC
 No need to Create separate material master for each variant combination.
 Super BOM and Super Routing is enough for representing all possible Variants and Operations.
 Able to react more flexible to customer demands.
 Increase Information exchange between sales, engineering and production.
3 What is Configurable Material?
 A material with different features or characteristics and options is known as configurable material. Example: PC, Car.
 Configurable materials are either created in a material type that allows the configuration (n the standard system, the material type KMAT) or they are given the indicator Configurable in the material master record.
4 Master Data used for VC
Following Objects are used as Master data for Variant configuration.
1. Super BOM
2. Super Routing
3. Characteristic
4. Class
5. Object Dependencies
6. Configuration Profile
7. SD Condition records
4.1 Super BOM
Super BOM Contains all the components for producing configurable product. It contains both variant as well as non-variant parts required for producing configurable product.
4.1.1 Super BOM configuration
Super BOM can be created either one of the following methods.
 Create BOM with class Item of 200-class type that contains all characteristic of a configurable material.
 Create BOM with all possible materials as its components. Then assign /define dependencies to each component.
The different between this two method is
 BOM with class item, no need to assign or define object dependencies. Instead of that each material is classified in material master itself using class 200.
 For both cases all characteristics are assigned to class 300 which is again assigned to KMAT material in order to trigger configuration in configuration profile.
4.1.2 Super BOM with Class Item
Class items used to control the selection of variant parts in a BOM. Variant parts are classified in a class, and the class is entered in the BOM as a class item. When you configure the material, the class is replaced by a suitable variant part.
4.1.3 Advantages of using Class Item in BOM
 Only one item for the class is enough, instead of several items for the individual variant parts.
 No need to create and assign selection conditions.
 Able to classify additional objects in the class at any time, without having to change the BOM.
4.1.4 Steps involved in super BOM with Class
Define all Characteristics and its Values assign it to Class with type 200.
Assign characteristic Values to materials by Classification material
Assign class 200 with material instead of assigning all BOM items.
Create and Assign class 300 (with same characteristics) with configurable product using configuration profile.
4.1.5 Super BOM with Material Components
This bill of material (BOM) of a configurable material contains all the components that are required to manufacture the material. The BOM contains components that are only used in specific variants (variant parts), as well as components that are used in all variants (non-variable parts).
4.1.6 Steps involved in super BOM with Material Components
Define all Characteristics and its values assign it to Class with type 300.
Assign Class with configurable material in Configuration profile.
BOM is created with all variant and non-variant items.
Define interdependency between objects (Characteristic, BOM item, Routing Operation etc ) by using Object Dependencies.
Assign class 300 with configurable product using configuration profile.
4.2 Super Routing
A configurable routing describes the production process for all variants of a product. Instead of creating a routing for each variant of a product, you can create operations for one routing, or a "super" routing.
It is possible to maintain Object dependencies for following in super routing:
 Sequences
 Operations/sub-operations
 Production resource/tool assignments
The routing is configured by system, when order is created for KMAT material.
4.3 Characteristic
Characteristic is used to define the features of a configurable material. To enable to use characteristics to configure a material, assign the material to a class of class type 300. The customer can choose from among different options for each characteristic.
 Characteristics describe the properties of objects. The values of a characteristic specify these properties.
 Value assignment to characteristic may be single value or multiple value with required entry or restrict able entry.
 In characteristic it is also possible to use table name and its field name in order to change the Object quantity or values. I.e. BOM item quantity or Operation time, which is known as reference characteristic.
 In Restriction screen allowed Class types are entered i.e. for what are the class this characteristic may used. In general for Variant configuration class 200 and 300 are used.
 It is also possible to assign Dependency to characteristic values maintained in Characteristic.
4.4 Variant Class
 In Variant configuration, Class is used to hold the characteristics that describe about configurable material. Class type to determine which object types can be classified.
 Class is used in variant configuration if the class has a class type that supports variant configuration. In Customizing for Classification, the Variant class type indicator must be set for the class type. In the standard system, this is class type 300.
4.5 Dependencies
 Dependencies restricts the combinations of options i.e. characteristic that are not allowed. It also select exactly the right BOM components and operations to produce a variant.
 It also describe the interdependencies between characteristics and characteristic values
 It control which components are selected from a bill of material (BOM) and which operations are selected from a task list
 It also changes the values of fields in BOM items and operations during configuration.
4.5.1 Global and Local Dependencies
Global dependencies have the following properties:
 They are independent of any object.
 They are identified by a name that you assign, and are maintained and managed centrally.
 If you change a global dependency, the change affects all the objects where the dependency is used
Local dependencies have the following properties:
 They are only available to the object for which you create them
 You cannot use the central maintenance functions on these dependencies, and you cannot allocate them to other objects
 They are identified by a number assigned by the system, not an external name
Local dependencies are only used where certain dependency will not be needed elsewhere
The differences between global and local dependencies are as follows:
 Global dependencies are created centrally and can be assigned to several objects.
 Local dependencies are created for one object and can only be used with this object
4.5.2 Declarative and Procedural Dependency
 In Declarative dependencies the result are explained logically
 Declarative dependencies are easier to trace than procedural dependencies, because the point in time when the dependency is processed and the sequence in which the dependencies are processed are not relevant.
 Example for Declarative dependency:
- Constraint
- Actions
- Preconditions (provided that they contain no non-declarative expressions)
- Selection conditions (provided that they contain no non-declarative expressions)
 In Procedural Dependency result depends on the processing sequence and the point in time when the dependency is processed.
- Procedures
- Preconditions (only if they contain non-declarative expressions)
- Selection conditions (only if they contain non-declarative expressions)
4.5.3 Dependencies Types
The SAP System supports the following types of dependencies:
 Preconditions
 Selection conditions
 Procedures
 Actions (obsolete)
 Constraints
4.5.4 Preconditions
Preconditions can be allocated to the following objects:
 A characteristic that you want to hide
 A characteristic value that you want to hide
Preconditions are used to hide characteristics and characteristic values that are not allowed and thereby ensure that the configuration of an object is consistent. In the precondition, it is also possible define the circumstances under which a characteristic or value is hidden.
A precondition is fulfilled if the condition you enter is either true or not violated.
4.5.5 Selection Conditions
Selection conditions used to ensure that all the objects relevant to a variant are selected:
 Selection conditions determine which variants require a specific component or operation
 Selection conditions determine when it is mandatory to assign a value to a characteristic
Selection conditions may allocate to the following objects:
 Characteristics
 BOM items
 Operations in task lists
 Sub-operations
 Sequences of operations
 Production resources/tools (PRTs)
A selection condition is fulfilled if the condition in it is unambiguously true.
4.5.6 Procedure
Procedures can be assigned to the following objects:
 The characteristic value that triggers the procedure
 The characteristic that triggers the procedure
 The configuration profile of the configurable object
Procedure is used for following purposes.
 A procedure is used to infer a value for a characteristic, you enter the variable $SELF before the characteristic.
 Procedures can overwrite values that are set by other procedures.
 Procedures are always used for pricing (see Variant Conditions).
Processing Sequences of Procedure
If an object has more than one procedure, a processing sequence is used to define the point when the procedure is processed.
4.5.7 Action
Actions are used to infer characteristic values. An action is processed as soon as the characteristic to which it is assigned has a value. It is not possible to overwrite the characteristic values that are set by an action.
The following Objects can assign to action:
 The characteristic value that triggers the action
 The characteristic that triggers the action
 The configuration profile of the configurable object
 Configuration profile
 BOM items to change the quantity
 Operations in task lists to change the standard values
Since Action is lead to serious system performance problems, it is replaced by Procedure and Constraint.
4.5.8 Constraint
This dependency type is mainly for intensively interactive configuration tasks and for configuration tasks in which you need to take into account the dependencies between the characteristics of several objects. The main purpose of a constraint is to monitor the consistency of a configuration.
Constraints have the following distinguishing features:
 Constraints are used to describe the dependencies between completely different objects and their characteristics.
 Constraints are used to store information on which conditions must be fulfilled if the configuration is to be consistent.
 Constraints are not directly allocated to individual objects. They are grouped together to form dependency nets and allocated to a configurable material in the configuration profile.
 In constraints, you enter objects in their general form of expression, without using $SELF, $ROOT, or $PARENT to identify objects. As a rule, you refer to objects in constraints by entering the class to which the objects are allocated.
 Constraints are declarative dependencies. The processing sequence of constraints and the point in time when constraints are processed is not relevant.
 Constraints are not processed in a specific order. You cannot determine when a specific constraint is used.
In any processing situation, a constraint is only processed once. If a value that is relevant to the constraint is changed, the constraint is triggered again.
4.5.8.1 Structure of Constraints
There are four sections in a constraint. Each part is identified by a keyword. A colon follows the keyword. Each section ends with a period.
OBJECTS:
In this section, you enter the objects that are relevant to the constraint. You must enter the relevant objects in all constraints. You can also define variables for objects or characteristics.
CONDITION:
The condition entered here must be fulfilled in order for the constraint to be used. You do not need to enter a condition in a constraint. You can leave out the keyword CONDITION: if required. However, if you enter the keyword you must enter a condition.
RESTRICTIONS:
In this section, you enter the relation that must exist between the objects and characteristics if the configuration is to be consistent. You must enter a restriction in a constraint.
INFERENCES:
In this section, you enter the characteristics for which characteristic values are to be inferred. The main purpose of constraints is to check the consistency of a configuration. Usually, values are only inferred if you make an entry in this section.
For reasons of performance, only use constraints to infer values if it is really necessary. Constraints are grouped together to form dependency nets. The dependency net is allocated to a configurable material in the configuration profile.
4.5.9 Dependency Net:
Constraints are grouped together in dependency nets. For this reason, the variant configuration menu does not support a function for creating constraints directly. So that only constraints are defined within a dependency net.
5 Configuration Profile
The configuration profile for a material controls the configuration process in sales order. Configurable profile also used to define central settings for configuring the object. Using this profile it is possible to hide some of the characteristic value defined during characteristic creation. We can assign any number profile for a configurable material in which selection is based on either priority or manual selection during configuration.
By defining a filter in the configuration profile, possible to determine the scope of the BOM items to improve system performance when exploding the BOM. The filter is active in high-level configuration, in result-oriented BOMs, and in SET processing.
5.1 Filters in Configurable Profile
Following objects can be used as filter:
 Object type
Class, material, document, text
In the standard system, all object types are selected and therefore exploded in the configuration. Deselect the object types that you do not want to be displayed.
 Item category, for example, stock or non-stock item
All item categories in the configuration are exploded in the standard system. Remove the selection for the item categories you do not want to be displayed.
 Item status
You maintain the status of a BOM item in maintain BOM dependent on its usage.
All items are displayed regardless of their item status in the standard system. However, only the items with this status are displayed when you select specific item statuses. Items are not displayed that do not have the selected status.
 Sort string
You can assign sort strings for BOM items in maintain BOM. You can restrict the display of the BOM items by using these sort strings.
Only items that carry sort strings are checked and only those that match are displayed. Items that have no sort string are always displayed.
5.2 Component availability in the configuration profile
The availability check is just a snapshot, telling that whether the materials required are in stock at this moment. Several users can access the same material at once. This means that supply problems can sometimes be overlooked.
Example: Only 2 pieces of a material are in stock, but the material is used in 3 BOMs. The availability check does not detect a supply problem. The availability check for all 3 BOMs shows 2 pieces in stock.
5.3 Process Overview
There are different processes for configurable materials in sales documents. These processes can be defined on the Configuration initial screen tab in the configuration profile, by choosing the Configuration parameter tab.
The Process are described in the following scenarios:
Planned/Production orders
This processing type is used to describe variant products whose configurable materials are assembled using planned and production orders. The bill of material (BOM) can have single-level, multi-level, or no explosion.
Sales Order (SET)
This processing type is used to describe variant products that comprise salable configurable materials. These products are supplied together, but are not assembled in a production order. Only sales-relevant BOM items are exploded in the sales order.
Order BOM.
You use this processing type if you want to make customer-specific changes to the BOM of a material that you configure in the sales order. In the sales order, you assign values to the characteristics of the header material, but the BOM is not exploded in the sales order.
6 Material Variant and Planning Material
6.1 Material Variant
 Material Variant is an material that can arises from individual Configuration of a configurable product and can be kept in stock
 For variants that are required frequently, we can create material variants, which can be produced without a sales order and kept in stock. When a sales order is received, it is possible to check whether the variant required is in stock, so that it can deliver immediately.
 For material variants, a separate material master record is created with a material type that is kept in stock.
 Separate BOM and routing for a material variant, or you can link the material variant to the BOM and routing of the configurable material. The correct BOM items and operations are determined from the characteristic values assigned to the variant.
6.2 Planning Material
 Planning Material is a material, which contains all the non-variant parts.
 By using planning material all non-variants are procured / produced before sales order.
 It is also possible for Planing the Planning Materials without reference to any sales requirement.
 Planning material is planned separately using strategy 65 and produced before sales order creation.
7 Planing in VC
The following strategies are used for planning configurable materials and its variant parts.
Make to Order production of Variants
Make to Order for Material Variant. - 26
Planning Variants without final Assembly- 55
Planning Variants with planning Material - 65
Make to order with configurable material.- 25
Characteristic Planning with dependent requirement - 56 and
Assembly Processing with Characteristic Planning - 89
8 Variant Configuration: (Object Diagram)
9 Variant Pricing and Surcharges
9.1 Sales BOM
A bill of material (BOM) describes the different components that together create a product. A BOM for a bicycle, for example, consists of all the parts that make up the bicycle: the frame, the saddle, wheels, and so on.
When you enter the material number of a bill of materials that is relevant for sales order processing, the system displays the material that describes the whole bill of materials as a main item. The individual components are displayed as lower-level items.
There are two ways to process a bill of materials in Sales. Once you have entered a bill of material in a sales order, the system runs pricing, inventory control, and delivery processing at: Main item level if the material is assembled, or - Component level if the material is not assembled.
9.2 Processing at Main Item Level (ERLA)
If you want the system to carry out pricing, inventory control, and delivery processing at main item level, enter ERLA in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. This means that the components only function as text items and are not relevant for delivery.
9.3 Processing at Component Level (LUMF)
If you want the system to carry out pricing, inventory control, and delivery processing at the component level, enter LUMF in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. In this case, only the components are relevant for delivery. During processing the system automatically creates a delivery group. The latest delivery date among all the components becomes the delivery date for the entire delivery group.
10 Configuration of VC
10.1 Production Planning and Control
10.1.1 Creating Material
Use
The purpose of this activity is to create the material masters for the materials required in this scenario.
Procedure
Access the activity using one of the following navigation options:
SAP Menu Logistics  Materials Management  Material Master  Material  Create (General)  Immediately
Transaction Code MM01
In Material Master of KMAT material following settings are maintained:
 Configurable material indicator in Basic Data must set.
 MRP type is PD.
 Lot size EX ( Lot for lot size)
 Availability check 02
 Planning Strategy 25 is entered in MRP 3 screen view.
 Item category group 0002 or 0004 is to be given in sales view.
10.1.2 Creating Bill of Material
Purpose:
 The purpose of this activity is to create bills of material (BOMs) for the configurable material which is known as super BOM
 Super BOM comprise all the variant as well as non-variant parts required for producing configurable material.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Production  Master Data  Bills of Material  Bill of Material  Material BOM  Create
Transaction Code CS01
 The Create Material BOM: initial screen appears. On this screen, data that identifies the bill of material are maintained as well effectivity data.
 In the Material field, the configurable material for which super BOM need to create is entered.
 Plant and BOM usage is entered. In general BOM usage 1 for production and 3 is for Universal.
 In Component screen list of variant and non-variant parts are entered along with that quantity is entered based on Base qty. of the configurable material.
 It is also possible to enter a class as a BOM component with item category class Item. This class must hold all characteristics and also classified with each material.
 Class type 200 and 300 can be used as a class item.
Following Procedure is followed for assigning class with BOM as a class Item.
 Enter the item category for class items in BOM.
 Make entries in the fields that identify the class
Class types
Class
 Enter the quantity.
- Enter a unit of measure if appropriate.
- The system determines the unit of measure from the additional data of the class.
- If a unit of measure without a dimension is maintained in the additional data of the class, you cannot change this unit.
10.1.3 Creating Characteristic
Purpose:
 Characteristic is created with possible values.
 It is also possible to use table name and its field name in order to change the Object quantity or values. Ie BOM item quantity or Operation time. This is known as Reference characteristic.
 For changing BOM quantity Characteristic is created with table name STOP-MENGE is used.
 For Variant pricing purpose SDCOM-VKOND is used.
 Characteristics allow describing and distinguishing between objects, such as length, color, or weight within the classification system.
Procedure
SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
Transaction Code CT04
 From the classification menu, choose Characteristics.
 Enter data on the initial screen.
 In the Characteristic field, enter a name for new characteristic
 Enter a change number if you want to create the characteristic using engineering change management.
 To do this, choose processing type Create characteristic.
 You can also copy the data of an existing characteristic. Use the pushbutton Create by copying. Enter the name of a characteristic you want to copy.
 Confirm the entries.
 On the Basic data tab page enter the most important control data for the characteristic.
 You must maintain the basic data for all characteristics. All other screens are optional.
 In the formatting data for value assignment, whether a characteristic is single-value, multiple-value, or retractable is defined. It is not possible change the value assignment indicator once it has set. It applies wherever the characteristic is used.
 The data type of the characteristic determines which values can be entered for the characteristic. I can any one of the following
- Characters
- Numeric
- Time format/Date format
- Currency format and
- User defined data type.
 For numeric characteristic it need to maintain that whether interval values to a numeric characteristic, or only individual values need to be maintain in Basic Data screen itself.
 Languages in which characteristic want to describe are entered.
 Choose the tab page Values.
 Enter values in the entry fields. Enter each value in a separate field.
 The values must match the format that you defined on the Basic Data screen. You can enter up to the number of characters that you defined in the format.
 If your characteristic is an alphanumeric characteristic, enter a language-dependent value description. You can enter up to 30 characters.
 It is not possible to enter a language-dependent description for numeric values
 It is also possible to define one value as a default value. This value then appears as a default in characteristic value assignment functions
 Additional value indicator determines that whether values that are not defined as allowed values can be assigned to a characteristic
 The following value check strategies are available in value maintenance screen.
- Allowed Values:
- Check Tables
- Function module
- Catalog character
 Allowed values permits only values defined in characteristics maintenance are used to check a characteristic value
 Check table permits only values entered in characteristics maintenance is used to check a value
 Function module entered is used to check characteristic values.
 Value catalog entered is used to check characteristic values
 Documents, such as drawings or photographs, with characteristics can be linked in additional data screen. Before link a document to a characteristic, it must create a document info record in the document management system.
 In this screen it also possible to restrict or hidden or displaying only allowed values to characteristic.
 It is possible to that characteristic can be only assigned to particular class type by assigning type in restriction screen.
 To change a characteristic selects the pushbutton Change in characteristics after entering the characteristic. To display the characteristic chooses the pushbutton Display.
10.1.4 Creating Class:
Purpose:
 A class is used to hold the characteristics that describe a configurable material. By linking the class to the configurable material, you allow the material to be configured using the characteristics of the class.
Procedure
SAP Menu Logistic->Central function->Environment->classification->Class
Transaction Code CL01
 Class holds all characteristics describe configurable material.
 Class with class type 300 is used in configuration profile.
 On basic Data screen class description, its status is entered. Status determines:
 whether a class can be maintained
 whether objects can be allocated to a class
 whether the class can be used for selecting objects
 Class group is used to group together related classes and also for finding classes quickly via a matchcode.
 Same Classification indicator determines whether system check for identical characteristic values. In this case, where several objects are assigned that have the same values for all characteristics to the same class. Depends upon indicator system give warning or error message or no message.
 Keyword string is used for finding a class via matchcode.The description entered on the basic data screen serves as the first keyword
 On characteristic screen list characteristic which has to attach with configurable material is entered.
 Using document tab screen it is possible to assign documents related to configurable object.
 On additional data screen whether or not this class can be used as a class component in bills of material. If it is yes then Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure and resulting item category which will replace this class item in BOM (i.e. Stock, Non-stock item etc ).
10.1.5 Creating Dependency
Purpose
Dependency describes the interdependencies between characteristics and characteristic values and it controls which components to be selected from a bill of material (BOM) and which operations to be selected from a task list. It also changes the field values in BOM items and operations during configuration.
Procedure
SAP Menu Logistic->Central function->Variant Configuration->dependency->Single Dependency->Create Dependency
Transaction Code CU01
 From the variant configuration menu, choose Dependency -> Single dependency-> Create
 In initial screen name of the dependency is entered. If dependency need to create for a specific date, enter a change number. It is also possible to create dependency by copying from existing dependency.
 On basic data screen the following data are required to enter
- A language-dependent description for the dependency
- Also possible to enter descriptions in different languages by choosing Descriptions.
- Long texts for the dependency, choose Extras -> Documentation.
- In the standard R/3 System, the status In preparation when a dependency is created first time. The status is set to Released when the source code is syntactically correct.
- Finally suitable dependency type is selected.
 In Dependency editor the source code for the dependency is entered. Once the source code is syntactically correct, the source code is saved.
 Now the status of the dependency is turns to Released. Save the Dependency and exit.
10.1.6 Changing Bill of Material (Assign Dependencies)
Purpose:
By assigning dependencies to BOM components, it is possible to restrict the selection of irrelevant variant parts.i.e correct BOM components are get selected at result of configuration. It is also possible to change the component quantity depends upon characteristic value changed.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Production  Master Data  Bills of Material  Bill of Material  Material BOM  Change
Transaction Code CS02
 Dependencies are assigned with respect to characteristic for each variant part.
 Dependencies are created either locally within object or globally which can be assigned to any objects.
 In BOM General Item overview screen choose the component in which dependency need to assign and choose menu path Extras -> Dependency -> assignment of dependency for assignment.
 It also possible to enter dependency directly in BOM itself by choosing Extras -> Dependency -> dependency editor.
10.1.7 Creating Configuration Profile
Purpose
 Configuration profile used for assigning configurable material with variant class (300) and also used to maintain some central settings.
 It is possible to assign more than one configurable profile for one KMAT material.
 The selection of profile depends upon either by priority or by manual selection.
 It is also possible to assign dependencies to configurable profile.
 Class with type 300, which hold the entire characteristics of KMAT material, are assigned to each profile
Procedure:
Access the activity using one of the following navigation options:
SAP Menu Logistics  Production  Master Data  Material Master  Environment  Configuration Profile  Create
Transaction Code CU41
 From the Variant Configuration menu, choose Configuration profile->Create.
 A dialog box will be displayed. The object name is entered. Confirm your entries.
 On profile overview screen the following data need to be entered.
 Profile name and the class type of classes used for configuration. In Customizing for the Classification System, the class type must be defined as a variant class type.
 Choose Goto -> Class assignments or the Class assignment pushbutton to assign the object to a class.
 In the classification screen, names of the classes are entered.
 It is possible to restrict allowed characteristic values for the configurable object if required.
 Release of profile is possible only if configurable object is assigned to a class. To go to the detail screen, where you define further settings, choose the Profile detail pushbutton or double-click on the profile.
10.1.7.1 Optional Settings on the Profile Overview
 Organizational Areas
You can specify organizational areas for configuration. If you restrict a profile to specific organizational areas, you only see the characteristics that are relevant to your area when you configure the object.
You can change how characteristics are displayed according to organizational area for your user on the value assignment screen.
 Priority of Configuration Profiles
You can create several configuration profiles for a configurable material. The profile with the lowest number has the highest priority.
If you define several profiles for an object, you see a dialog box for selecting a profile when you start configuration. The profile with the highest priority is at the top of the list.
The priority is also relevant if you use Application Link Enabling (ALE) or intermediate documents (IDocs) to run configuration, rather than dialog mode. In this case, the profile with the highest priority is selected for the object. Profiles that have no priority are at the top of the list, because they automatically have priority 0.
10.1.7.2 Profile Detail
 Configuration Profiles for Materials
The configuration profile has several screens. Depending on what you enter for the BOM explosion and configuration process, fields are shown or hidden.
The parameters you maintain for a material apply to the material as a header material in a BOM structure. You cannot define separate settings for use of a configurable material as an assembly in a BOM.
- By choosing the Assignments pushbutton, you can assign dependencies to the configuration profile. You also see this pushbutton on the basic data tab, once at least one dependency is assigned.
 Basic Data Tab
- In the basic data, click on the profile overview data.
- If configuration process need to starts with a Start logo, documents are assigned such, as a graphic showing the product you want to configure, to the variant class.
- Configuration Initial Screen Tab
 Configuration parameters
- The parameters for BOM explosion and the configuration process in the sales order are specified here.
- BOM application must be entered, if BOM explosion None is selected rather than single and multi level explosion is selected.
- By entering a level of detail for a multi-level configuration, system performance will be improved.
- It is also possible to define a filter and set the indicator for an availability check on assemblies.
10.1.8 Changing Configuration Profile: Add User Interface Settings
Purpose
Settings for the configuration editor in user interface.
- An interface design is used to group characteristics together on the value assignment screen.
- Here it also possible to define object-specific settings for functions in the configuration editor. These settings are defaults for configuration, and can be overwritten for your user in the configuration editor.
- For all configuration parameters except BOM explosion None, manually select the screens for the configuration editor and define which screen configuration starts with. The start screen must be one of the allowed screens.
- The indicator for the configuration browser independently of the other start screens can be selected, because the browser is an additional screen section.
Configuration Profiles for Objects Other than Materials
- Object-specific settings for displaying characteristics and characteristic values in the configuration editor can be defined. These settings are defaults for configuration, and can be overwritten for your user in the configuration editor.
Procedure
Access the activity using one of the following navigation options:
SAP Menu Logistics  Production  Master Data  Material Master  Environment  Configuration Profile  Change
Transaction Code CU42
10.1.9 Configuration Simulation
Purpose:
 Configuration simulation is used to check the configuration model. In the configuration simulation, the whether or not Object structure is created correctly and dependencies are working fine is checked.
 Simulation of Sales/Engineering
- The configuration parameters in the configuration profile apply. Whether the configuration is simulated from the sales point of view or the engineering point of view is defined.
- If select Sales & distribution is selected the configuration in a sales document will be simulated (sales order or quotation), so the BOM explosion depends on the settings in the configuration profile.
- If Engineering is selected, the configuration in order BOM processing will be simulated. The configuration and BOM explosion depend on the configuration parameters in the same way as when maintaining an order BOM. For example, we cannot configure the header material, because the configuration is copied from the sales order.
 Simulation of a Planned Order
- On the characteristic value assignment screen, we can choose Planned order to display the components that are determined in material requirements planning (MRP) according to the characteristic values assigned. This is especially relevant to assemblies whose BOMs are exploded in MRP, not in Sales & distribution (for example, assemblies with the BOM explosion setting None in their configuration profile).
Procedure:
SAP R/3 menu Logistics  Production  Master Data  Bills of Material  Environment  Variant Configuration  Environment  Configuration Simulation
Transaction Code CU50
 On the initial screen of the configuration simulation, select BOM to display the entire structure on the result screen.
 If you have created more than one configuration profile for a material, you see a dialog box. Select a profile and choose Continue. If you want to call detailed information on the profile, choose Profile Detail or double-click on the profile.
 To display the task list of an assembly on the result screen, select the assembly and choose View  Objects  Task list.
 You see the operations or activities in the task list that was selected for the assembly during configuration.
 Operations that have been changed by dependencies have an information icon next to them. You can display changes by choosing Information.
 To return to the BOM explosion, choose View  Objects  BOM
10.2 Sales and Distribution
10.2.1 Creating Condition Records - VA00
Purpose:
The purpose of this activity is to create condition records for VA00.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Sales and Distribution  Master Data  Conditions  Select Using Condition Type  Create
Transaction Code VK11
 Create price for each value of the characteristics by select using condition type VA00.
 Create the Price for the condition type that represents these types of the standard-delivered condition type for this functionality is VA00.
 Condition type VA00 requires as key fields the sales Organization, distribution channel, and material number of the configurable.
 Condition type PR00 used to maintain base price of the configurable material.
 Using VA01it is also possible to maintain Surcharges and discounts.
10.2.2 Condition records for Variant Price and Surcharges
Purpose
Condition records allow you to store and retrieve pricing data in the system. All the pricing elements of your daily business - the prices, discounts, and surcharges for freight and taxes - that you want to use for automatic pricing must be stored in the system as condition records. You can define as many condition records as you want for the different pricing elements for any validity period.
You create condition records for all the pricing elements that the system takes into account during automatic pricing. During document processing, the system transfers data from the condition records and determines the amounts for individual pricing elements (prices, discounts and surcharges) and the final amount for the sales document
Procedure
10.2.2.1 Create a characteristic for the Pricing
- Create Pricing characteristic like CAR_Pricing and go to additional data tab give SDCOM table name VKOND field name.
SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
Transaction Code CT04
10.2.2.2 Assign the characteristic to the class
Assign given characteristics to class, In variant configuration, a class is used to hold the characteristics that describe a configurable material. By linking the class to the configurable material, it allows the material to be configured using the characteristics of the class. In the standard R/3 System, the class type for configurable material is 300.
SAP Menu Logistic->Central function->Environment->classification->Class
Transaction Code CL01
10.2.2.3 Create a dependency that triggers the price
A Dependency is a rule that defines how the different options and option values, represented by characteristics and characteristic values, relate to one another. To create a dependency, follow the menu path
SAP Menu Logistic->Central_function->VariantConfiguration->dependency->Single Dependency->Create Dependency
Transaction Code CU01
10.2.2.4 Assign the dependency to the characteristic value that triggers the price
For example eCar2002, the value V8 refers to the engine selected by the customer. Therefore, the dependency must be linked to the value V8 of the characteristic that represents the engine type. To do this, go to the master data record of the characteristic CAR_ENGINE
SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
Transaction Code CT04
Go to the Values tab. From there, select theV8 entry and use the menu path Extras Object dependencies Assignments, which brings you to the screenshot to the right; if you have created a global dependency, you can link it to the characteristic value.2 Once the dependency has been assigned, the information on this screen, such as the description (Engine price), will default to the information entered when you created the characteristic.
10.2.2.5 Create variant price
Create price for each value of the characteristics using condition type (or transaction VK11). Create the Price for the condition type that represents these types of the standard-delivered condition type for this functionality is VA00. Condition type VA00 requires as key fields the sales Organization, distribution channel, and material number of the configurable.
In the same way using condition type VA01 is also used to maintain prices for surcharges and discounts.
10.2.2.6 Creating the output condition records for sales
Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
10.2.3 Creating Output Condition Records: Sales
Purpose:
Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Sales and Distribution  Master Data  Output  Sales Document  Create
Transaction Code VV11
 Choose Edit >Key combination
 Select the key combination for which condition records are to be created.
 Choose Enter.
 Enter the appropriate key for each condition record, according to the key combination you selected.
 For transmission medium 1 (Print output) or 7, you can maintain the communication data. To do this, choose Communication.
 Save the condition records.
10.2.3.1 Creating Output Condition Records: Billing
Purpose
The purpose of this activity is to create output condition records for billing. Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Sales and Distribution  Master Data  Output  Billing Document  Create
Transaction Code VV31
Enter an output type.
 Choose Edit >Key combination
 Select the key combination for which condition records are to be created.
 Choose Enter.
 Enter the appropriate key for each condition record, according to the key combination you selected.
 For transmission medium 1 (Print output) or 7, you can maintain the communication data. To do this, choose Communication.
 Save the condition records.
10.2.4 Order BOM
Purpose:
Products that are made to order in plant engineering and construction and mechanical engineering are generally very complex and are specific to one customer. For this reason, you cannot define a BOM entirely in advance. Once you have created your sales order, you need to make manual changes to the BOM by creating an order BOM especially for the sales order, without changing the original BOM.
The sales order, sales order item, and material number identify an order BOM. In variant configuration, you can work with 2 types of order BOM. The difference is in the way they are saved.
Knowledge based order BOM
The order BOM is saved as a copy of the super BOM with manual changes and dependencies.
Result Oriented BOM
The configuration result is saved as an order BOM, with manual changes but without dependencies.
Procedure (For knowledge based BOM)
SAP Menu Logistics  Production Planning  Master Data  Bills of Material -> Order BOM Maintain (Multi-Level)
Transaction Code CU51
 The Create Order BOM: initial screen appears.
 Enter the sales order number, the order item, the material number and the BOM usage
 If you want to use material BOM, or an existing order BOM to copy from, go to step 4. If you want to create an order BOM without a reference, click and go to step 7
 You cannot use a configurable BOM as a reference
 Click on copy order BOM or Click on copy material BOM
 The Copy material BOM or Copy order BOM dialog box appears
 Enter the data required and click . The item overview appears, for the bill of material you are using as a reference.
 Enter new items and alter items if necessary. Entering items in order BOMs is similar to entering items in material BOMs. However, you<u><i><b>Steps for SD Variant Configuration</b></i></u>
Some light on Variant Configuration in Detail.
The procedure is as follows:
1. Create a Material - KMAT type with Item category (002)
2. Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
3. Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)
4. Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
5. Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save
6. Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
7. Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
8. Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
9. Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
Reward if it helps
Regards,
Anbu
Maybe you are looking for
-
Hi guys, First of all let me say hello to everyone, this is my first post in here. I kindly ask your help before sending my MP to apple support. I have to tell you as many other somewhere I installed third party ram on my machine from OWC 4x2gb. But
-
Apple devices not detected in Windows 8.1
Win 8.1, Itunes 11.2.2.3, Ipod 5 and Ipad Air not recognized in iTunes nor PC. Tried everything I've found in the net and nothing helps. USB ports working fine. Apple mobile device USB driver not listed. This is driving me nuts! Don't send me to the
-
My MacBook Air lost mac os x. So I would like to reinstall mac os. But I can't select the disk to install mac os x. Only Recovery HD is shown and I can't select it. How can I reinstall my Mac os x? Thank you!
-
ITunes connection timed out problem. Please help
Hey guys, I've purchased an iPod Touch 4th Gen recently but a problem I've had after installing iTunes is connecting to the internet. I haven't even got the software on the iPod Touch due to an error - "iTunes could not connect to the iTunes store. T
-
Down Payment settlement Line is not appearing in the final Billing
Hello All, Activated the Milestone billing plan. Created a Sales order > Down payment Billing document > and cleared the Down payment billing document. While trying to bill the final invoice the down payment settlement line is not appearing. Please s