SAP has an enterprise architecture framework and trained enterprise architects . One of the common questions that I have to address these days is “what exactly is the difference between solution and enterprise architecture. As we see it there’s a clear line that can be drawn between enterprise architects and solution architects. In a nutshell enterprise architects are dealing with more abstract architecture and their outputs are inputs for the solution architects. Enterprise architects should have a holistic view of the enterprise including the business, Information, Application and Technology domains of the enterprise. Equipped with a holistic view , an enterprise architect can define the target architecture of the enterprise domains, identify gaps between the current architecture and the target architecture, set time-lined projects to fill the gaps and govern those projects. The most important outputs of enterprise architect are: Principles, Constraints, standards and blueprints. These outputs should guide the defined time-lined projects. The solution architect is responsible for one or several of those time-lined projects. His /her duty is to create information, application and technology architecture for the project/s he /she is responsible for . Part of the solution architect’s inputs are the Principles, Constraints, standards and blueprints defined by the enterprise architect and the current and target architecture. Using those inputs, and others, the solution architect should come up with architecture for given project/s. The Enterprise architect deals with more abstract architecture. His /her work is more focused in the business and technology domain and although the EA might come from technical background the EA work isn’t technology oriented. The solution architect is the technology guy /gal . He /she is focused on the application and technology aspects of given project/s and we expect him /her to come up with the perfect solution architecture. Natty Gur.