AdminGuideVEAuthorSP1v3

8/13/2019 AdminGuideVEAuthorSP1v3

http://slidepdf.com/reader/full/adminguideveauthorsp1v3 1/37



© Copyright 2013 SAP AG. All rights reserved

No part of this publication may be reproduced or transmitted in

any form or for any purpose without the express permission ofSAP AG. The information contained herein may be changed

without prior notice.Some software products marketed by SAP AG and its

distributors contain proprietary software components of othersoftware vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight,and Visual Studio are registered trademarks of Microsoft

Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5,System p, System p5, System x, System z, System z10, z10,z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power

Architecture, Power Systems, POWER7, POWER6+,POWER6, POWER, PowerHA, pureScale, PowerPC,BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX,Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter

Planet are trademarks or registered trademarks of IBM

Corporation.

Linux is the registered trademark of Linus Torvalds in theUnited States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader aretrademarks or registered trademarks of Adobe SystemsIncorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its

affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of

the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes,Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode aretrademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold,BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm,

BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry

App World are trademarks or registered trademarks ofResearch in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google

Data API, Google Maps, Google Mobile Ads, Google Mobile

Updater, Google Mobile, Google Store, Google Sync, Google

Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvikand Android are trademarks or registered trademarks of

Google Inc.

INTERMEC is a registered trademark of IntermecTechnologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola TrademarkHoldings LLC.

Computop is a registered trademark of Computop

Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign,SAP Business Objects Explorer, StreamWork, SAP HANA,

and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence,

Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos aretrademarks or registered trademarks of Business ObjectsSoftware Ltd. Business Objects is an

SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQLAnywhere, and other Sybase products and services mentionedherein as well as their respective logos are trademarks or

registered trademarks of Sybase Inc. Sybase is an SAPcompany.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services

are registered trademarks of Crossgate AG in Germany andother countries. Crossgate is an SAP company.

All other product and service names mentioned are thetrademarks of their respective companies. Data contained inthis document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. Thesematerials are provided by SAP AG and its affiliated companies("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall

not be liable for errors or omissions with respect to thematerials. The only warranties for SAP Group products and

services are those that are set forth in the express warranty

statements accompanying such products and services, if any. Nothing herein should be construed as constituting anadditional warranty.

Portions of this software are based in part on OpenEXR. © 2002,

Industrial Light & Magic, a division of Lucas Digital Ltd. LLC.

All rights reserved.



Portions of this software are based in part on the JasPer Software.

© 1999-2000, Image Power, Inc. and the University of BritishColumbia. © 2001 Michael David Adams. All rights reserved.

Portions of this software are based in part on the Nvidia CG

Shader Library. © 2002 NVIDIA Corporation. All rightsreserved.

Portions of this software are based in part on the Nvidia SDK.

Copyright © 2002-2008, NVIDIA Corporation. All rightsreserved.

Portions of this software are based in part on the TIFF Library. ©

1988-1997 Sam Leffler. © 1991-1997 Silicon Graphics, Inc.

Portions of this software are based in part on PKWARE. © 1991,

1992, 1994 and 1995 PKWARE Inc. All rights reserved.

Portions of this software are based in part on TTF Foundations. ©

1996-2005 Trade and Technologies France. All rights reserved.

Portions of this software are based in part on the Autodesk DWF

Toolkit. © 1996-2005 Autodesk, Inc. All rights reserved.

This product includes software developed by the OpenSSLProject for use in the OpenSSL Toolkit.

(http://www.openssl.org).

Portions of this software are based in part on 3DConnexion. ©

1998-2005. All rights reserved.

This product includes software developed by COLLADA for use

with Maya and 3DS Max. Copyright © 2005-2007 Feeling

Software Inc. Copyright © 2005-2007 Sony ComputerEntertainment America.

Portions of this software are based in part on the

OpenGLExtension Wrangler Library. Copyright © 2002-2007,

Milan Ikits <milan ikits[]ieee org>. Copyright © 2002-2007,Marcelo E. Magallon <mmagallo[]debian org>. Copyright ©2002, Lev Povalahev. All rights reserved.

OpenEXR License

Copyright © 2002, Industrial Light & Magic, a division of Lucas

Digital Ltd. LLC. All rights reserved.

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions aremet:

Redistributions of source code must retain the above copyright

notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above

copyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materials providedwith the distribution.

Neither the name of Industrial Light & Magic nor the names of its

contributors may be used to endorse or promote products derivedfrom this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHTHOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS

OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY

AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT

OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORYOF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

SUCH DAMAGE.

JasPer Software License

Copyright © 1999-2000, Image Power, Inc. and the University of

British Columbia / Copyright (c) 2001 Michael David Adams. Allrights reserved.

IMAGE POWER JPEG-2000 PUBLIC LICENSE

Grant

Permission is hereby granted, free of charge, to any person (the"User") obtaining a copy of this software and associated

documentation, to deal in the JasPer Software without restriction,including without limitation the right to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the JasPerSoftware (in source and binary forms), and to permit persons to whom

the JasPer Software is furnished to do so, provided further that theLicense Conditions below are met.

License Conditions

A. Redistributions of source code must retain the above copyrightnotice, and this list of conditions, and the following disclaimer.

B. Redistributions in binary form must reproduce the above copyright

notice, and this list of conditions, and the following disclaimer in thedocumentation and/or other materials provided with the distribution.

C. Neither the name of Image Power, Inc. nor any other contributor(including, but not limited to, the University of British Columbia and

Michael David Adams) may be used to endorse or promote products

derived from this software without specific prior written permission.



D. User agrees that it shall not commence any action against Image

Power, Inc., the University of British Columbia, Michael DavidAdams, or any other contributors (collectively "Licensors") for

infringement of any intellectual property rights ("IPR") held by theUser in respect of any technology that User owns or has a right tolicense or sublicense and which is an element required in order to

claim compliance with ISO/IEC 15444-1 (that is, JPEG-2000 Part 1)."IPR" means all intellectual property rights worldwide arising understatutory or common law, and whether or not perfected, including,without limitation, all (i) patents and patent applications owned orlicensable by User; (ii) rights associated with works of authorship

including copyrights, copyright applications, copyright registrations,mask work rights, mask work applications, mask work registrations;

(iii) rights relating to the protection of trade secrets and confidentialinformation; (iv) any right analogous to those set forth in subsections

(i), (ii), or (iii) and any other proprietary rights relating to intangible property (other than trademark, trade dress, or service mark rights);and (v) divisions, continuations, renewals, reissues and extensions of

the foregoing (as and to the extent applicable) now existing, hereafter

filed, issued or acquired.

E. If User commences an infringement action against any Licensor(s)then such Licensor(s) shall have the right to terminate User's licenseand all sublicenses that have been granted hereunder by User to other

parties.

F. This software is for use only in hardware or software products thatare compliant with ISO/IEC 15444-1 (that is, JPEG-2000 Part 1). Nolicense or right to this Software is granted for products that do not

comply with ISO/IEC 15444-1. The JPEG-2000 Part 1 standard can be purchased from the ISO.

THIS DISCLAIMER OF WARRANTY CONSTITUTES ANESSENTIAL PART OF THIS LICENSE. NO USE OF THE JASPER

SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER

THIS DISCLAIMER. THE JASPER SOFTWARE IS PROVIDEDBY THE LICENSORS AND CONTRIBUTORS UNDER THISLICENSE ON AN ``AS-IS'' BASIS, WITHOUT WARRANTY OFANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,

WITHOUT LIMITATION, WARRANTIES THAT THE JASPERSOFTWARE IS FREE OF DEFECTS, IS MERCHANTABLE, IS FIT

FOR A PARTICULAR PURPOSE OR IS NON-INFRINGING.THOSE INTENDING TO USE THE JASPER SOFTWARE OR

MODIFICATIONS THEREOF FOR USE IN HARDWARE ORSOFTWARE PRODUCTS ARE ADVISED THAT THEIR USEMAY INFRINGE EXISTING PATENTS, COPYRIGHTS,TRADEMARKS, OR OTHER INTELLECTUAL PROPERTY

RIGHTS. THE ENTIRE RISK AS TO THE QUALITY AND

PERFORMANCE OF THE JASPER SOFTWARE IS WITH THEUSER. SHOULD ANY PART OF THE JASPER SOFTWARE

PROVE DEFECTIVE IN ANY RESPECT, THE USER (AND NOTTHE INITIAL DEVELOPERS, THE UNIVERSITY OF BRITISHCOLUMBIA, IMAGE POWER, INC., MICHAEL DAVID ADAMS,

OR ANY OTHER CONTRIBUTOR) SHALL ASSUME THE COSTOF ANY NECESSARY SERVICING, REPAIR OR CORRECTION.

UNDER NO CIRCUMSTANCES AND UNDER NO LEGALTHEORY, WHETHER TORT (INCLUDING NEGLIGENCE),

CONTRACT, OR OTHERWISE, SHALL THE INITIAL

DEVELOPER, THE UNIVERSITY OF BRITISH COLUMBIA,IMAGE POWER, INC., MICHAEL DAVID ADAMS, ANY OTHER

CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE JASPERSOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES,BE LIABLE TO THE USER OR ANY OTHER PERSON FOR ANY

INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIALDAMAGES OF ANY CHARACTER INCLUDING, WITHOUTLIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORKSTOPPAGE, COMPUTER FAILURE OR MALFUNCTION, ORANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES,

EVEN IF SUCH PARTY HAD BEEN INFORMED, OR OUGHT TOHAVE KNOWN, OF THE POSSIBILITY OF SUCH DAMAGES.

THE JASPER SOFTWARE AND UNDERLYING TECHNOLOGYARE NOT FAULT-TOLERANT AND ARE NOT DESIGNED,

MANUFACTURED OR INTENDED FOR USE OR RESALE ASON-LINE CONTROL EQUIPMENT IN HAZARDOUSENVIRONMENTS REQUIRING FAIL-SAFE PERFORMANCE,

SUCH AS IN THE OPERATION OF NUCLEAR FACILITIES,

AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS,AIR TRAFFIC CONTROL, DIRECT LIFE SUPPORT MACHINES,OR WEAPONS SYSTEMS, IN WHICH THE FAILURE OF THEJASPER SOFTWARE OR UNDERLYING TECHNOLOGY OR

PRODUCT COULD LEAD DIRECTLY TO DEATH, PERSONALINJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL

DAMAGE ("HIGH RISK ACTIVITIES"). LICENSORSPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED

WARRANTY OF FITNESS FOR HIGH RISK ACTIVITIES. USERWILL NOT KNOWINGLY USE, DISTRIBUTE OR RESELL THEJASPER SOFTWARE OR UNDERLYING TECHNOLOGY ORPRODUCTS FOR HIGH RISK ACTIVITIES AND WILL ENSURE

THAT ITS CUSTOMERS AND END-USERS OF ITS PRODUCTSARE PROVIDED WITH A COPY OF THE NOTICE SPECIFIED INTHIS SECTION.

NVIDIA CG Shader Library License

Copyright © 2002, NVIDIA Corporation. All rights reserved.

NVIDIA Corporation("NVIDIA") supplies this software to you inconsideration of your agreement to the following terms, and your use,

installation, modification or redistribution of this NVIDIA software

constitutes acceptance of these terms. If you do not agree with theseterms, do not use, install, modify or redistribute this NVIDIAsoftware.

In consideration of your agreement to abide by the following terms,

and subject to these terms, NVIDIA grants you a personal, non-exclusive license, under NVIDIA’s copyrights in this original NVIDIA

software (the "NVIDIA Software"), to use, reproduce, modify andredistribute the NVIDIA Software, with or without modifications, in

source and/or binary forms; provided that if you redistribute the NVIDIA Software, you must retain the copyright notice of NVIDIA,

this notice and the following text and disclaimers in all suchredistributions of the NVIDIA Software. Neither the name,

trademarks, service marks nor logos of NVIDIA Corporation may be



used to endorse or promote products derived from the NVIDIA

Software without specific prior written permission from NVIDIA.Except as expressly stated in this notice, no other rights or licenses

express or implied, are granted by NVIDIA herein, including but notlimited to any patent rights that may be infringed by your derivativeworks or by other works in which the NVIDIA Software may be

incorporated. No hardware is licensed hereunder.

THE NVIDIA SOFTWARE IS BEING PROVIDED ON AN "AS IS"BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANYKIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUTLIMITATION, WARRANTIES OR CONDITIONS OF TITLE,

NON-INFRINGEMENT, MERCHANTABILITY, FITNESS FOR A

PARTICULAR PURPOSE, OR ITS USE AND OPERATIONEITHER ALONE OR IN COMBINATION WITH OTHERPRODUCTS.

IN NO EVENT SHALL NVIDIA BE LIABLE FOR ANY SPECIAL,

INDIRECT, INCIDENTAL, EXEMPLARY, CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSTPROFITS; PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) OR ARISING IN ANY WAY OUT OF THE USE,REPRODUCTION, MODIFICATION AND/OR DISTRIBUTION OF

THE NVIDIA SOFTWARE, HOWEVER CAUSED AND

WHETHER UNDER THEORY OF CONTRACT, TORT(INCLUDING NEGLIGENCE), STRICT LIABILITY OROTHERWISE, EVEN IF NVIDIA HAS BEEN ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NVIDIA SDK License

Copyright © 2002-2008, NVIDIA Corporation.

NVIDIA Corporation("NVIDIA") supplies this software to you in

consideration of your agreement to the following terms, and your use,installation, modification or redistribution of this NVIDIA softwareconstitutes acceptance of these terms. If you do not agree with theseterms, do not use, install, modify or redistribute this NVIDIA

software.

In consideration of your agreement to abide by the following terms,and subject to these terms, NVIDIA grants you a personal, non-exclusive license, under NVIDIA's copyrights in this original NVIDIAsoftware (the "NVIDIA Software"), to use, reproduce, modify and

redistribute the NVIDIA Software, with or without modifications, insource and/or binary forms; provided that if you redistribute the

NVIDIA Software, you must retain the copyright notice of NVIDIA,this notice and the following text and disclaimers in all such

redistributions of the NVIDIA Software. Neither the name,trademarks, service marks nor logos of NVIDIA Corporation may beused to endorse or promote products derived from the NVIDIA

Software without specific prior written permission from NVIDIA.

Except as expressly stated in this notice, no other rights or licensesexpress or implied, are granted by NVIDIA herein, including but notlimited to any patent rights that may be infringed by your derivative

works or by other works in which the NVIDIA Software may be

incorporated. No hardware is licensed hereunder.

THE NVIDIA SOFTWARE IS BEING PROVIDED ON AN "AS IS"

BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANYKIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT

LIMITATION, WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY, FITNESS FOR A

PARTICULAR PURPOSE, OR ITS USE AND OPERATIONEITHER ALONE OR IN COMBINATION WITH OTHERPRODUCTS.

IN NO EVENT SHALL NVIDIA BE LIABLE FOR ANY SPECIAL,

INDIRECT, INCIDENTAL, EXEMPLARY, CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSTPROFITS; PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) OR ARISING IN ANY WAY OUT OF THE USE,

REPRODUCTION, MODIFICATION AND/OR DISTRIBUTION OFTHE NVIDIA SOFTWARE, HOWEVER CAUSED ANDWHETHER UNDER THEORY OF CONTRACT, TORT

(INCLUDING NEGLIGENCE), STRICT LIABILITY OROTHERWISE, EVEN IF NVIDIA HAS BEEN ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

TIFF License

Copyright © 1988-1997 Sam Leffler / Copyright © 1991-1997 SiliconGraphics, Inc. All rights reserved.

Permission to use, copy, modify, distribute, and sell this software and

its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permissionnotice appear in all copies of the software and related documentation,

and (ii) the names of Sam Leffler and Silicon Graphics may not be

used in any advertising or publicity relating to the software without thespecific, prior written permission of Sam Leffler and Silicon Graphics.

THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EXPRESS, IMPLIED OR

OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY

WARRANTY OF MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE.

IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICSBE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR

CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY

DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE

POSSIBILITY OF DAMAGE, AND ON ANY THEORY OFLIABILITY, ARISING OUT OF OR IN CONNECTION WITH THEUSE OR PERFORMANCE OF THIS SOFTWARE.

Autodesk FBX



This software contains Autodesk® FBX® code developed by

Autodesk, Inc. Copyright 2012 Autodesk, Inc. All rights, reserved.Such code is provided “as is” and Autodesk, Inc. disclaims any and all

warranties, whether express or implied, including without limitationthe implied warranties of merchantability, fitness for a particular purpose or non-infringement of third party rights. In no event shall

Autodesk, Inc. be liable for any direct, indirect, incidental, special,exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or

profits; or business interruption) however caused and on any theory ofliability, whether in contract, strict liability, or tort (includingnegligence or otherwise) arising in any way out of such code.”

Autodesk DWF Toolkit Disclaimer of Warranty

© 1996-2005 Autodesk, Inc. All rights reserved.

The incorporated portions of the Autodesk DWF Toolkit are provided"AS IS" and without any warranty of any kind. AUTODESK DOES NOT MAKE AND HEREBY DISCLAIMS ANY EXPRESS OR

IMPLIED WARRANTIES INCLUDING, BUT NOT LIMITED TO,THE WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE, OR ARISING FROM A COURSE OF DEALING,

USAGE, OR TRADE PRACTICE.

3DConnexion License

© 1998-2005 3Dconnexion. All rights reserved.

Permission to use, copy, modify, and distribute this software for all purposes and without fees is hereby granted provided that this

copyright notice appears in all copies. Permission to modify thissoftware is granted and 3Dconnexion will support such modifications

only is said modifications are approved by 3Dconnexion.

COLLADA for Maya, 3DSMax

Copyright © 2005-2007 Feeling Software Inc.

Copyright © 2005-2007 Sony Computer Entertainment America

Permission is hereby granted, free of charge, to any person obtaining acopy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, including

without limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and to permit

persons to whom the Software is furnished to do so, subject to the

following conditions:

The above copyright notice and this permission notice shall be

included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUTWARRANTY OF ANY KIND, EXPRESS OR IMPLIED,

INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSEAND NONINFRINGEMENT. IN NO EVENT SHALL THE

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANYCLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN ANACTION OF CONTRACT, TORT OR OTHERWISE, ARISING

FROM, OUT OF OR IN CONNECTION WITH THE SOFTWAREOR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Adobe Systems Incorporated Open Source License

NOTICE TO USER: Adobe Systems Incorporated is providing the

Software and Documentation for use under the terms of thisAgreement. Any use, reproduction, modification or distribution of theSoftware or Documentation, or any derivatives or portions thereof,constitutes your acceptance of this Agreement.

As used in this Agreement, "Adobe" means Adobe Systems

Incorporated. "Software" means the software code accompanying thisAgreement. "Documentation" means the documents, specifications

and all other items accompanying this Agreement other than theSoftware.

1. LICENSE GRANT

Subject to the terms of this Agreement, Adobe hereby grants you a

non-exclusive, worldwide, royalty free license to use, reproduce, prepare derivative works from, publicly display, publicly perform,distribute and sublicense the Software for any purpose, provided the

copyright notice below appears in a conspicuous location within the

source code of the distributed Software and this license is distributedin the supporting documentation of the Software you distribute.

Copyright (2011) Adobe Systems Incorporated and others. All rights

reserved. The original version of this source code may be found at

http://adobe.com.

Subject to the terms of this Agreement, Adobe hereby grants you anon-exclusive, worldwide, royalty free license to use, reproduce, publicly display, publicly perform, distribute and sublicense the

Documentation for any purpose. You may not modify theDocumentation.

No title to the intellectual property in the Software or Documentationis transferred to you under the terms of this Agreement. You do not

acquire any rights to the Software or the Documentation except as

expressly set forth in this Agreement.

If you choose to distribute the Software in a commercial product, youdo so with the understanding that you agree to defend, indemnify and

hold harmless Adobe against any losses, damages and costs arisingfrom the claims, lawsuits or other legal actions arising out of such

distribution. You may distribute the Software in object code formunder your own license, provided that your license agreement:

(a) complies with the terms and conditions of this license agreement;



(b) effectively disclaims all warranties and conditions, express or

implied, on behalf of Adobe;

(c) effectively excludes all liability for damages on behalf of Adobe;

(d) states that any provisions that differ from this Agreement are

offered by you alone and not Adobe; and

(e) states that the Software is available from you or Adobe and informslicensees how to obtain it in a reasonable manner on or through a

medium customarily used for software exchange.

2. DISCLAIMER OF WARRANTY

ADOBE LICENSES THE SOFTWARE AND DOCUMENTATION

TO YOU ONLY ON AN "AS IS" BASIS WITHOUT WARRANTIESOR CONDITIONS OF ANY KIND, EITHER EXPRESS OR

IMPLIED, INCLUDING WITHOUT LIMITATION ANYWARRANTIES OR CONDITIONS OF TITLE, NON-

INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A

PARTICULAR PURPOSE. ADOBE MAKES NO WARRANTYTHAT THE SOFTWARE OR DOCUMENTATION WILL BEERROR-FREE. Each user of the Software or Documentation is solely

responsible for determining the appropriateness of using and

distributing the Software and Documentation and assumes all risksassociated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance

with applicable laws, damage to or loss of data, programs, orequipment, and unavailability or interruption of operations. Use of theSoftware and Documentation is made with the understanding that

Adobe will not provide you with any technical or customer support or

maintenance. Some states or jurisdictions do not allow the exclusion ofimplied warranties or limitations on how long an implied warrantymay last, so the above limitations may not apply to you. To the extent

permissible, any implied warranties are limited to ninety (90) days.

3. LIMITATION OF LIABILITY

ADOBE AND ITS SUPPLIERS SHALL NOT BE LIABLE FORLOSS OR DAMAGE ARISING OUT OF THIS AGREEMENT OR

FROM THE USE OF THE SOFTWARE OR DOCUMENTATION.IN NO EVENT WILL ADOBE BE LIABLE TO YOU OR ANYTHIRD PARTY FOR ANY DIRECT, INDIRECT,CONSEQUENTIAL, INCIDENTAL, OR SPECIAL DAMAGES

INCLUDING LOST PROFITS, LOST SAVINGS, COSTS, FEES,OR EXPENSES OF ANY KIND ARISING OUT OF ANY

PROVISION OF THIS AGREEMENT OR THE USE OR THEINABILITY TO USE THE SOFTWARE OR DOCUMENTATION,

HOWEVER CAUSED AND UNDER ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY ORTORT (INCLUDING NEGLIGENCE OR OTHERWISE), EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

ADOBE'S AGGREGATE LIABILITY AND THAT OF ITS

SUPPLIERS UNDER OR IN CONNECTION WITH THIS

AGREEMENT SHALL BE LIMITED TO THE AMOUNT PAID BY

YOU FOR THE SOFTWARE AND DOCUMENTATION.

4. TRADEMARK USAGE

Adobe and XMP are the trademarks or registered trademarks of AdobeSystems Incorporated in the United States and other countries. Suchtrademarks may not be used to endorse or promote any product unless

expressly permitted under separate agreement with Adobe.

5. TERM

Your rights under this Agreement shall terminate if you fail to comply

with any of the material terms or conditions of this Agreement and donot cure such failure in a reasonable period of time after becomingaware of such noncompliance. If all your rights under this Agreementterminate, you agree to cease use and distribution of the Software and

Documentation as soon as reasonably practicable.

6. GOVERNING LAW AND JURISDICTION.

This Agreement is governed by the statutes and laws of the State of

California, without regard to the conflicts of law principles thereof. If

any part of this Agreement is found void and unenforceable, it will notaffect the validity of the balance of the Agreement, which shall remainvalid and enforceable according to its terms. Any dispute arising out of

or related to this Agreement shall be brought in the courts of SantaClara County, California, USA.

7. GENERAL

You acknowledge that you have read this Agreement, understand it,and that it is the complete and exclusive statement of your agreement

with Adobe which supersedes any prior agreement, oral or written, between Adobe and you with respect to the licensing to you of the

Software and Documentation. No variation of the terms of thisAgreement will be enforceable against Adobe unless Adobe gives itsexpress consent in writing signed by an authorized signatory of Adobe.

Little CMS

Copyright © 1998-2007 Marti Maria

Permission is hereby granted, free of charge, to any person obtaining a

copy of this software and associated documentation files (the

"Software"), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the


The above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the Software.



THE SOFTWARE IS PROVIDED "AS IS", WITHOUT

WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSEAND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY

CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN ANACTION OF CONTRACT, TORT OR OTHERWISE, ARISINGFROM, OUT OF OR IN CONNECTION WITH THE SOFTWAREOR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

OpenSSL Combined License

Copyright © 1995-1998 Eric Young ([email protected]). All rightsreserved.

This package is an SSL implementation written by Eric Young

([email protected]).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long asthe following conditions are adhered to. The following conditions

apply to all code found in this distribution, be it the RC4, RSA, lhash,

DES, etc., code; not just the SSL code. The SSL documentationincluded with this distribution is covered by the same copyright termsexcept that the holder is Tim Hudson ([email protected]).

Copyright remains Eric Young's, and as such any Copyright notices inthe code are not to be removed. If this package is used in a product,

Eric Young should be given attribution as the author of the parts of thelibrary used. This can be in the form of a textual message at program

startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are

met:

1. Redistributions of source code must retain the copyright notice,

this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above

copyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materials provided

with the distribution.

3. All advertising materials mentioning features or use of thissoftware must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young([email protected])"

The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative

thereof) from the apps directory (application code) you mustinclude an acknowledgement:

"This product includes software written by Tim Hudson

([email protected])"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT

NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THEAUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,

INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORYOF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.

The license and distribution terms for any publically available versionor derivative of this code cannot be changed. i.e. this code cannot

simply be copied and put under another distribution license [includingthe GNU Public License.].

OpenGL Extension Wrangler Library License

The OpenGL Extension Wrangler Library.

Copyright © 2002-2007, Milan Ikits <milan ikits[]ieee org>.

Copyright © 2002-2007, Marcelo E. Magallon <mmagallo[]debianorg>.

Copyright © 2002, Lev Povalahev.

All rights reserved.

Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are

met:

Redistributions of source code must retain the above copyright

notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above

copyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materials providedwith the distribution.

The name of the author may be used to endorse or promote

products derived from this software without specific prior written

permission.



THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT

HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED

TO, THE IMPLIED WARRANTIES OF MERCHANTABILITYAND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT

OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORYOF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,

OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.

Mesa 3-D graphics library

Version: 7.0

Copyright © 1999-2007 Brian Paul. All Rights Reserved.

Permission is hereby granted, free of charge, to any person obtaining acopy of this software and associated documentation files (the

"Software"), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the


The above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT

WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSEAND NONINFRINGEMENT. IN NO EVENT SHALL BRIAN

PAUL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR INCONNECTION WITH THE SOFTWARE OR THE USE OR OTHERDEALINGS IN THE SOFTWARE.

Copyright © 2007 The Khronos Group Inc.

Permission is hereby granted, free of charge, to any person obtaining a

copy of this software and/or associated documentation files (the"Materials"), to deal in the Materials without restriction, including

without limitation the rights to use, copy, modify, merge, publish,

distribute, sublicense, and/or sell copies of the Materials, and to permit persons to whom the Materials are furnished to do so, subject to thefollowing conditions:

The above copyright notice and this permission notice shall be

included in all copies or substantial portions of the Materials.

THE MATERIALS ARE PROVIDED "AS IS", WITHOUT

WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,

INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE

AND NONINFRINGEMENT. IN NO EVENT SHALL THE

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY

CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN

ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING

FROM, OUT OF OR IN CONNECTION WITH THE MATERIALS

OR THE USE OR OTHER DEALINGS IN THE MATERIALS.

Terms for Included OpenSource SoftwareThis SAP software contains also the third party open source software

products listed below. note that for these third party products the

following special terms and conditions shall apply.

1. This software was developed using ANTLR.

2. gSOAP

Part of the software embedded in this product is gSOAP software.

Portions created by gSOAP are Copyright (C) 2001-2004 Robert A.

van Engelen, Genivia inc. All Rights Reserved.

THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDEDBY GENIVIA INC AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND

FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.

IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY

DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY

OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,

OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

SUCH DAMAGE.



3. SAP License Agreement for STLport SAP License Agreement for

STLPort between SAP Aktiengesellschaft Systems, Applications,

Products in Data Processing Neurottstrasse 16 69190 Walldorf,

Germany (hereinafter: SAP) and you (hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive, non-transferrable, royalty-

free license to use the STLport.org C++ library (STLport) and its

documentation without fee.

B) By downloading, using, or copying STLport or any portion thereof

Customer agrees to abide by the intellectual property laws, and to all

of the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled with STLport

(whether original or modified) without any royalties or restrictions.

D) Customer shall maintain the following copyright and permissions

notices on STLport sources and its documentation unchanged:

Copyright 2001 SAP AG

E) The Customer may distribute original or modified STLport sources,

provided that:

o The conditions indicated in the above permissions notice are met;

o The following copyright notices are retained when present, and

conditions provided in accompanying permission notices are met:

Copyright 1994 Hewlett-Packard

Company

Copyright 1996,97 Silicon Graphics

Computer Systems Inc.

Copyright 1997 Moscow Center for

SPARC Technology.

Copyright 1999,2000 Boris Fomitchev

Copyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and

its documentation for any purposes is hereby granted without fee,

provided that the above copyright notice appear in all copies and that

both that copyright notice and this permission notice appear in

supporting documentation. Hewlett-Packard Company makes no

representations about the suitability of this software for any purpose.

It is provided “as is” without express or implied warranty.

Permission to use, copy, modify, distribute and sell this software andits documentation for any purpose is hereby granted without fee,



supporting documentation. Silicon Graphics makes no representations

about the suitability of this software for any purpose. It is provided “as

is” without express or implied warranty.





supporting documentation. Moscow Center for SPARC makes no

representations about the suitability of this software for any purpose. It

is provided “as is” without express or implied warranty.

Boris Fomitchev makes no representations about the suitability of this

software for any purpose. This material is provided "as is", with

absolutely no warranty expressed or implied.

Any use is at your own risk. Permission to use or copy this software

for any purpose is hereby granted without fee, provided the above

notices are retained on all copies.

Permission to modify the code and to distribute modified code is

granted, provided the above notices are retained, and a notice that the

code was modified is included with the above copyright notice.





supporting documentation. SAP makes no representations about the

suitability of this software for any purpose. It is provided with a

limited warranty and liability as set forth in the License Agreement

distributed with this copy.

SAP offers this liability and warranty obligations only towards its

customers and only referring to its modifications.

b) Support and Maintenance SAP does not provide software

maintenance for the STLport. Software maintenance of the STLport

therefore shall be not included.

All other services shall be charged according to the rates for services

quoted in the SAP List of Prices and Conditions and shall be subject to

a separate contract.

c) Exclusion of warranty

As the STLport is transferred to the Customer on a loan basis and free

of charge, SAP cannot guarantee that the STLport is error-free,without material defects or suitable for a specific application under

third-party rights. Technical data, sales brochures, advertising text and

quality descriptions produced by SAP do not indicate any assurance of

particular attributes.

d) Limited Liability



A) Irrespective of the legal reasons, SAP shall only be liable for

damage, including unauthorized operation, if this (i) can be

compensated under the Product Liability Act or (ii) if caused due to

gross negligence or intent by SAP or (iii) if based on the failure of a

guaranteed attribute.

B) If SAP is liable for gross negligence or intent caused by employees

who are neither agents or managerial employees of SAP, the total

liability for such damage and a maximum limit on the scope of any

such damage shall depend on the extent to which its occurrence ought

to have anticipated by SAP when concluding the contract, due to the

circumstances known to it at that point in time representing a typical

transfer of the software.

C) In the case of Art. 4.2 above, SAP shall not be liable for indirect

damage, consequential damage caused by a defect or lost profit.

D) SAP and the Customer agree that the typical foreseeable extent of

damage shall under no circumstances exceed EUR 5,000.

E) The Customer shall take adequate measures for the protection of

data and programs, in particular by making backup copies at the

minimum intervals recommended by SAP. SAP shall not be liable for

the loss of data and its recovery, notwithstanding the other limitations

of the present Art. 4 if this loss could have been avoided by observing

this obligation.

F) The exclusion or the limitation of claims in accordance with the

present Art. 4 includes claims against employees or agents of SAP.

4. Adobe Document Services Adobe, the Adobe logo, Acrobat,

PostScript, and Reader are either registered trademarks or trademarks

of Adobe Systems Incorporated in the United States and / or other

countries. For information on Third Party software delivered with

Adobe document services and Adobe LiveCycle Designer, see SAP

Note 854621.



Typographic Conventions

Type Style Description

Example Text Words or characters quoted fromthe screen. These include fieldnames, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrases inbody text, graphic titles, andtable titles

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, table names,and key concepts of aprogramming language whenthey are surrounded by body

text, for example, SELECT andINCLUDE.

Example text Output on the screen. Thisincludes file and directory namesand their paths, messages,names of variables andparameters, source text, andnames of installation, upgradeand database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example text> Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Librarydocumentation to help you identify differenttypes of information at a glance. For more

information, see Help on Help GeneralInformation Classes and Information Classesfor Business Information Warehouse on the

first page of any version of SAP Library .



Administrator’s Guide for SAP Visual Enterprise Author 7.1

November 2013 13

History of Changes

Caution

Before you start the implementation, make sure you have the latest version of this document.You can find the latest version at the following location: http://service.sap.com/instguides.

The following table provides an overview of the most important document changes:

Version Description

1.00 (November 2012) First version

1.1.0 (May 2013) Updated licensing information fornetwork licensing

1.2.0 (November 2013) Included information about opening aCSS message for component CA-VE-VEA




14 November 2013

Contents

1. Getting Started ........................................................................ 16 1.1 About this Document ..................................................................... 16

1.1.1 Purpose .............................................................................................. 16 1.2 SAP Notes for the Installation....................................................... 17

1.2.1 SAP Notes relating to SAP Visual Enterprise Planner ................... 17 1.3 Information Available in SAP Service Marketplace .................... 18

2. SAP Visual Enterprise Author 7.1 .......................................... 19 2.1 System Landscape......................................................................... 19 2.2 Overall Implementation Sequence ............................................... 19

3. Installation Information .......................................................... 20 3.1 Installing the Software ................................................................... 20 3.2 Acquiring and Activating Licenses for SAP Visual EnterpriseAuthor 7.1 ............................................................................................. 21

3.2.1 Technical Licensing models............................................................. 21 3.2.2 Activating a Network License Server .............................................. 22 3.2.3 Activating a Standalone License ..................................................... 25

4. Operation Information ............................................................ 27 4.1 Monitoring of SAP Visual Enterprise Author .............................. 27

4.1.1 Trace and Log Files ........................................................................... 27

4.2 Backup and Restore ...................................................................... 27 5. Security Information ............................................................... 28

5.1 Sandbox .......................................................................................... 28 6. Technical System Landscape ................................................ 30

6.1 Supported Operating Systems ..................................................... 30 6.2 Hardware Configuration ................................................................ 30 6.3 Additional Requirements ............................................................... 31

7.

Upgrade Information ............................................................... 32

8. SAP Visual Enterprise Planner .............................................. 33




November 2013 15

8.1 Software Units ................................................................................ 33 8.2 Software Component Matrix ......................................................... 34 8.3 System Landscape......................................................................... 34 8.4 Business Scenarios of SAP Visual Enterprise Planner ............. 35

8.4.1 Create or Update a Material BOM using SAP Visual EnterprisePlanner ........................................................................................................ 35 8.4.2 Create or Update a Planning Scope ................................................. 35

8.5 Technical System Landscape ....................................................... 36 8.6 Authorizations ................................................................................ 37

8.6.1 Standard Authorization Objects ....................................................... 37 8.7 User Administration and Authentication ..................................... 37



Getting Started

16 November 2013

1. Getting Started

1.1 About this Document

1.1.1 PurposeThis Administration Guide is the central source of information for the technical implementation ofSAP Visual Enterprise Author. It provides cross-scenario implementation information as well asscenario-specific information.

You can use the Administrator’s Guide to get an overview of SAP Visual Enterprise Author andits software units from a technical perspective. The Administration Guide is a planning tool thathelps you to design your system landscape and it refers you to the detailed documentation thatis required, mainly:

Installation guides for single software units

SAP Notes

Configuration documentation

SAP Library documentation

This Administration Guide is a single source of information for the documentation that isavailable to support the installation and operation of SAP Visual Enterprise Author. Therefore,this Guide contains all of the following:

Installation Information

This chapter gives you an overview of the installation components and the sequence inwhich they are installed.

Security Information

This chapter provides you with the information that you require to operate SAP VisualEnterprise Viewer securely.

Upgrade Information

This chapter provides you with the latest upgrade information.

Information on SAP Visual Enterprise Planner

This chapter provides you with further information on the component SAP VisualEnterprise Planner.

You can find the most current version of this document on SAPService Marketplace at

http://service.sap.com/instguides

We strongly recommend that you use the document availablethere. The guide will be updated according to updates of thesoftware.






Getting Started

November 2013 17

1.2 SAP Notes for the InstallationYou must read the following SAP Note before you start the installation. These SAP Notescontain the most recent information on the installation, as well as corrections to the installation

documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find in the

SAP Service Marketplace at the Internet address: service.sap.com/notes .

SAP NoteNumber

Title Description

1787261 SAP Visual Enterprise 7.1: Correctionsto Online Documents

Applicable changes to onlinedocuments post release

1789940 File Formats Supported by SAP VisualEnterprise Author

Clarification on the full list of2D and 3D file formatssupported by SAP VisualEnterprise Author 7.1.

1.2.1 SAP Notes relating to SAP Visual EnterprisePlannerThese SAP Notes contain the most recent information on SAP Visual Enterprise Planner, aswell as corrections to the installation documentation.

They are also located at http://service.sap.com/notes .

SAP Note Number Title Description

1660552 Metadata enhancementwithin CDMU package

Possibility to save metadatafor a transformation matrix

1661003 Correction of DMUPOBexistence check

Correction of DMUPOBexistence check

1768377 SAP Visual EnterprisePlanner SLIN Check Issue &menu entry

SAP Visual EnterprisePlanner SLIN Check Issue &menu entry

1779959 Planner is dumping whileplanning recursive assembly

Planner is dumping whileplanning recursive assembly

1784282 SAP Visual Enterprise

Planner issue with emptyBOM reload

SAP Visual Enterprise

Planner issue with emptyBOM reload

https://service.sap.com/sap/support/notes/1787261


















Getting Started

18 November 2013

1.3 Information Available in SAP ServiceMarketplaceInformation on the following areas is available in the SAP Service Marketplace.

Documentation

Description Internet Address Title

Application Help for SAPVisual Enterprise Author

http://help.sap.com/ SAP

Business Suite – Additional Applications – SAP VisualEnterprise – SAP Visual Enterprise

Author – SAP Visual Enterprise Author 7.1

Application Help for SAPVisual Enterprise Author


Viewer

service.sap.com/instguides

SAP Business Suite Applications –> SAP Visual Enterprise


Viewer Administrator’sGuide

SAP Visual EnterpriseGenerator

service.sap.com/instguidesSAP Business Suite Applications –> SAP Visual Enterprise

SAP Visual EnterpriseGenerator Administrator’sGuide

General Quick Links

Description Internet Address Title

SAP Notes service.sap.com/notes –

Released platforms service.sap.com/platforms –

System sizing service.sap.com/sizing Quick Sizer tool

Front-end installation service.sap.com/instguides Front End InstallationGuide

Security service.sap.com/security –

Information aboutcreating error messages

service.sap.com/messages _

SAP Software DistributionCenter (softwaredownload and ordering ofsoftware)

service.sap.com/swdc _

SAP Product Availability

Matrix

service.sap.com/PAM _

http://help.sap.com/


http://service.sap.com/swdc

http://service.sap.com/PAM

http://service.sap.com/PAM

http://service.sap.com/swdc




SAP Visual Enterprise Author 7.1

November 2013 19

2. SAP Visual Enterprise Author 7.1SAP Visual Enterprise Author 7.1 is a standalone application used to manage and author 2D,3D, animation, video, and audio assets residing on a computer or network. With it, you cansearch, view and manage all your assets in one program, repurpose 3D assets for use in Webpages, training, sales presentations and marketing, and create interactive 3D content for Web-based presentations.

2.1 System LandscapeThe following graphic shows the system landscape for SAP Visual Enterprise Author with therequired software units and the required business functions:

2.2 Overall Implementation SequenceVisual Enterprise Author is standalone, and does not integrate with a back-end system, so there

is no equivalent installation sequence. SAP Visual Enterprise Author and SAP Visual EnterprisePlanner are installed directly onto your desktop, with no reliance on any other software orhardware.




20 November 2013

3. Installation InformationSAP Visual Enterprise Author 7.1 is installed directly onto your computer, with no reliance onany other software or hardware.

3.1 Installing the Software

Use

This section describes the process for installing SAP Visual Enterprise Author on yourcomputer. As part of the SAP Visual Enterprise Author installation, you can also choose toinstall SAP Visual Enterprise Planner, which is one of its subcomponents.

Prerequisites

If you intend using the PDF Template Designer, you have Adobe Acrobat installed andconfigured.

Procedure

1. Close all applications on the computer.

2. Navigate to, and double-click the VisualEnterpriseAuthor_xx.exe file (where 'xx is

the version number), file in Windows Explorer.

3. Choose Next when the installer starts. The Front-End Installer screen is displayed.

4. Do one of the following:

Choose Select All to install both SAP Visual Enterprise Author and SAP Visual Enterprise

Planner on the local hard drive. Note that this is the recommended option.

Use the checkboxes to select the features to be installed.

5. Continue to the next window to select an install location, and do one of the following:

Accept the default location in which to install SAP Visual Enterprise Author.

Choose Browse, navigate to and select the installation folder you require.

6. Choose Next to start the installation, and then Close when the installation is complete.

7. Register and activate the product.




November 2013 21

3.2 Acquiring and Activating Licenses forSAP Visual Enterprise Author 7.1

Use

SAP Visual Enterprise Author is licensed per-user. You must activate your licenses in order tooperate SAP Visual Enterprise Author on any computer after the 30 day temporary periodexpires.

3.2.1 Technical Licensing modelsThere are two basic models for licensing:

Served license – also called Network License. A single license file with licenses for all users, which resides on a network license server

on your local network. This is suitable for larger installations with many users. Administering a license server is simpler than managing licenses on each user machine.The system administrator installs and configures the license server, and obtains andinstalls a single license file to activate all the served licenses.

Fixed License – also called Standalone or Un-served license. A license key specific to each user’s workstation is installed. There are two methods toget the Fixed License key.

These models are illustrated in the following diagrams.

If you are using SAP Visual Enterprise Author in a corporate environment, typically the systemadministrator will decide which licensing model is preferred.

License Server

PCs or Laptops running Visual Enterprise Author software,

obtaining license from Network License Server on demandPCs or Laptops running Visual Enterprise Author software,

Each with a locally installed and activated license key

License

key

License

key

License

key

License

key

Network License Server approach (Concurrent or Served Licenses) Fixed License approach (Standalone or un-served Licenses)

Figure 1: License Models

Prerequisites

SAP software and licenses are delivered via the SAP Service Marketplace (SMP) –

http://www.service.sap.com . If you have purchased SAP software, one or more people

in your organization are set up as a user on SMP. If you purchased through a partner, that

http://www.service.sap.com/






22 November 2013

partner can obtain your licenses for you. The licenses are available through a “license self -

service” page on the portal http://service.sap.com/licensekeys .

You or your system administrator needs to be able to log into the SMP to get license keys insome situations.

3.2.2 Activating a Network License Server A License Server delivers licenses to the users on an internal network.

Network License activation is a four part process. You must:

1. Install the Network License Server

2. Acquire the License File

3. Install the License File on your License Server

4. Configure SAP Visual Enterprise Author

1. Installing the Network License Server

1. Download the SAP Visual Enterprise Author package from SMP.

2. Extract the License Server software from the download.

3. Select your target license server machine, and install the License Server software.

4. Install the service by choosing Start SAP Visual Enterprise SAP Visual Enterprise

Author Network License Manager Install License Server . Ensure that you haveadministrative privileges, and that the command is executed with elevated to admin UACrights.

5. Use the HostID utility to determine the Host ID for the server machine by choosing

Start SAP Visual Enterprise SAP Visual Enterprise Author Network License

Manager HostID Tool .

http://service.sap.com/licensekeys







November 2013 23

2. Acquiring the License File

1. Log into the SMP License Keys area http://service.sap.com/licensekeys , and

select the appropriate installation. If you do not know how to find an installation or if youcannot log in to SMP, contact the SAP Customer Interaction Center (CIC), or the partnerwho supplied SAP Visual Enterprise Author.

2. In the Select System window, do one of the following:

Edit an existing system.

Create a new system by choosing New System. If you are creating a new system, youmust generate a System ID.

3. Enter the appropriate information in the required fields. Choose SAP Visual Enterprise Author from the drop down list of products, and choose the appropriate version.

Note

If SAP Visual Enterprise Author is not in the list, there is aproblem with the order or the entitlement. You must do one ofthe following:

Contact your account executive

Contact your supplier or partner

Open a CSS message for component CA-VE-VEA.

4. Continue to the License Generating screen, choose the entitlement, (the set of availablelicenses to use), and choose Select to Generate. Note that this does not generate thekeys immediately.

5. In the License Model window, choose the licensing model Served License.

6. Define the number of licenses to serve on this License Server.

7. Enter the required information about the server (machine name, machine host ID), andany optional information. You can find more information in the documentation deliveredwith the license server software installation.

8. Generate the license file and download it to the location of the license server software.

3. Installing the License File on your License Server

The next step in the process is to install the Named licenses on your license server. The fourstep workflow is as follows:

Define the set(s) of users (by username, hostname, IP-address) who are entitled tocheck out licenses for SAP Visual Enterprise Author by creating an Option File. Anexample file is shown below.

Reference the Option file in your License File by editing the license file obtained in theSAP marketplace.

Deploy the license and option files by placing them into a location where the server canaccess them.

Start the RLM service by choosing Start All Programs Administrative Tools

Services(Computer Management Console) .








24 November 2013

Step 1. Creating an Option File (*.opt)

1. Create a text file in Notepad.exe. Add your users’ group(s), name(s), and end users‘names, as detailed in the example below:

Note

The tag [users] in the above example must be populated withyour Windows login names.

2. When editing is complete, rename the file extension from .txt to .opt.

Step 2. Referencing the Option file in the License File

Open the license file (*.lic) in Notepad.exe. Copy and paste your option file name to the ISV

option line.

Important

With the exception of two optional parameters: option file nameand port number, all other parameters in the license file areprotected by digital signature. Never modify these values asthis will make the license file invalid.




November 2013 25

Step 3. Deploying the Named license

1. Save the License File (*.lic) and the Option file (*.opt) to the SAP Visual

Enterprise Author Network License Manager installation directory. The default path is:%PROGRAMFILES32%\SAP\Visual Enterprise Author Network License Manager\.

2. Re-start the RLM service.

Step 4. Starting the RLM service

The RLM service can be manually started by choosing Start All Programs

Administrative Tools Services(Computer Management Console) .

4. Configuring SAP Visual Enterprise Author

1. Set up all named users in the options file on the license server. Refer to the

documentation that was delivered with the license server. This also helps you to set upyour options file with all the named users in it.

2. Install SAP Visual Enterprise Author on a client machine, configure it to point to thelicense server, and test the installation.

3. Start SAP Visual Enterprise Author and open the Activation Wizard from the Help menu.

4. Select the Network option and continue to the next window.

5. Enter the Server Name or IP Address and Port Number of the main license server.Optionally, you can specify a backup server. This information is supplied by the systemadministrator.

6. Choose Next to save the settings to the registry. SAP Visual Enterprise Author is now

licensed.

Note

Access to the license server is required each time SAP VisualEnterprise Author is run.

3.2.3 Activating a Standalone LicenseIf you are using standalone licenses, you must obtain and install a license key specific to eachuser’s workstation.

There are two options for activating standalone licenses:

Automatic: You can automatically activate licenses if Internet access is available.You can enter the activation code into SAP Visual Enterprise Author and obtain a licensekey automatically from an Internet Activation Server.

Manual: If Internet access is unavailable, (perhaps because of firewalls or securitypolicy), you must manually obtain a license key and install it. Again, there are twooptions:

An administrator or user logs in to SMP to obtain the license keys manually. In thiscase, you need to know the HostID of the particular workstation in order to obtain thelicense key.

Open a CSS message for component CA-VE-VEA, including the computer HostID to

obtain a license key.




26 November 2013

This describes the process of automatically obtaining a license key using an activation code.The activation code is either supplied to you by your partner or it is available for download in theService Marketplace.

Procedure

To activate a standalone license:

1. Obtain the activation code directly from the license self-serve area in SMP.

2. Log into SMP. http://service.sap.com/licensekeys .

3. In the Select Installation window, select an appropriate installation to work with, eitherfrom the Recently Used Installations section, or by searching.

4. In the Select System window, do one of the following:

Edit an existing system.

Create a new system by choosing New System.

5. If you are creating a new system, you must generate a System ID. You can include all ofyour workstations grouped under this one System ID.

6. Enter the appropriate information in the required fields. Choose SAP Visual Enterprise Author from the drop down list of products, and choose the appropriate version.

Note

If SAP Visual Enterprise Author is not in the list, there is aproblem with the order or the entitlement. You must contactyour Account Executive, your supplier or partner, or open aCSS message for component CA-VE-VEA.

7. Continue to the License Generating window, choose the entitlement, (the set of availablelicenses to use), and choose Select to Generate. Note that this does not generate thekeys immediately.

8. In the License Model window, choose the licensing model Activation Codes.

9. Move to the Number of Activation Codes window and enter the required quantity. Youcan generate up to 10 codes at a time. Click Generate to generate the license keys,which displays the final window showing a list of activation codes.

10. Open SAP Visual Enterprise Author, and open the License Activation window from the

Help menu by choosing Help Activate SAP Visual Enterprise Author .

11. Choose the Standalone (Unserved) option, continue, and choose the Automatically option.

12. Enter the activation code in the space provided. You can specify a proxy server ifrequired.

Note

If activation fails - for example, because of a firewall or Internetaccess issue, you must either correct the Internet connectivity,or use the manual method of license activation. A windowalerts you if there is an error.







Operation Information

November 2013 27

4. Operation Information

4.1 Monitoring of SAP Visual EnterpriseAuthorWithin the management of SAP Technology, monitoring is an essential task. A section hastherefore been devoted solely to this subject.

4.1.1 Trace and Log FilesTrace files and log files are essential for analyzing problems. Log files contain details of errorsthat occur during a working session. These errors can be interrogated with the log viewer.

Important Log and Trace files for component SAP Visual Enterprise Author

Component Content File Path

SAP VisualEnterprise Author

Systemprocesses,memory state

SAP VisualEnterprise Author7.1.log

<ApplicationData>\SAP\SAP VisualEnterprise Author 7.1\

SAP VisualEnterprise Planner

Log and trace file *.log

*.trc

<ApplicationData>\SAP\SAP VisualEnterprise Planner 7.1\

4.2 Backup and RestoreYou need to back up your system landscape regularly to ensure that you can restore andrecover it in case of failure.

The following table lists the components used by SAP Visual Enterprise Author, and therequired actions.

Component Data to bebacked up

BackupMethod / Tool

RecommendedBackupFrequency

Backup Sequence (ifrequired)

SAP VisualEnterprise

Author

Application dataat <Application

Data>\SAP\SAPVisual Enterprise

Author 7.1\

No backup,new

installation incase of arecovery

1 month Install application

Run SAP VisualEnterprise Author

Exit SAP VisualEnterprise Author

Restore ApplicationData

SAP VisualEnterprisePlanner

None No backup,newinstallation incase of arecovery

N/A Install application




28 November 2013

5. Security InformationSAP Visual Enterprise Author uses sandboxing to provide security controls.

5.1 SandboxSome of SAP Visual Enterprise Author‘s supported file formats use third party libraries overwhich there is little control in terms of security. This means that vulnerabilities in third partycode, encountered when processing corrupt data from an external, untrusted source, mightpose security issues and compromise SAP products.

Sandboxing provides guarantees about what a piece of code can or cannot do, no matter whatthe inputs. Sandboxing leverages the operating system-provided security to allow codeexecution that cannot make persistent changes to the computer or access information that isconfidential. The architecture and exact assurances that the sandbox provides are dependenton the operating system.

Security through sandboxing is achieved by granting the sandboxed code the least possibleaccess rights and privileges, ensuring that it works in accordance with a predefined set of rules.The collection of rules that any code running in the Sandbox must obey is called a Policy, andno other system resources beyond those defined in the policy can be accessed or operated onfrom within the sandbox.

Use

The Sandbox for plug-ins feature is found in the Plugin Manager in SAP Visual Enterprise Author. Sandboxing leverages the OS-provided security to allow code execution that cannotmake persistent changes to the computer or access information that is confidential. Thearchitecture and exact assurances that the sandbox provides are dependent on the operating

system.

The Sandbox for plug-ins feature also supports the Group Policy option. Using this, the networkadministrator can set a maximum security level and prevent users from changing it. This feature(sandbox handling) is implemented over registry, and is version dependent. The Group Policywrites to the registry and SAP Visual Enterprise Author uses it to enable or disable sandboxsettings.

The .adm file is located at:

SAP Visual Enterprise Author 7.1\Domain Group Policies\Sandbox.adm.

Prerequisites

You have:

A Windows Server setup with a domain

Full administrative rights to that server

SAP Visual Enterprise Author already installed

Procedure

Installing the SAP Visual Enterprise Author Group Policy "SandBox.adm"

1. Log into the domain server with full administrative rights.




November 2013 29

2. Copy the file Sandbox.adm from the installation folder of SAP Visual Enterprise Author,

and paste into a location in the domain server for installation.

3. From the Windows Start Menu, choose Administrative Tools Group Policy

Management .

4. In the Group Policy Management tree, right click Group Policy Objects and choose New .

Give the group policy a name; for example, <SAP Group Policy> . The newly added

group policy displays under the Group Policy objects.

5. Select the newly created policy object, right-click and choose Edit to display the GroupPolicy Object Editor window.

6. From the User Configuration folder, right-click Administrative Templates, select Add/Remove Templates, and choose Add .

7. Browse for the file Sandbox.adm that you have transferred across to the domain server,

and open it.

8. Choose Close to apply the changes. A folder entitled "SAP Visual Enterprise" displays in

the administrative templates. In that folder, double click the Sandbox item to display thesandbox properties.

9. Close the Group Policy Object Editor window to return to the Group Policy Managementwindow. Right click the domain to which you want to apply the group policy, and chooseLink an Existing GPO.

10. In the Select GPO, under Group Policy Objects, the group policy object is displayed.

11. Login and run SAP Visual Enterprise Author. Check whether the changes in group policydisplay in the SAP Visual Enterprise Author settings.

Note

You must login again to see the updates. This is based on howgroup policy update is configured.

The following links provide further assistance for administrators when implementing sandboxing:

http://blogs.technet.com/b/askds/archive/2007/08/14/deploying-custom-

registry-changes-through-group-policy.aspx

http://www.windowsecurity.com/articles/Pushing-Out-Security-Settings-

Configured-Registry.html

http://www.windowsecurity.com/articles/group-policy-management-

console.html

http://blogs.technet.com/b/askds/archive/2007/08/14/deploying-custom-registry-changes-through-group-policy.aspx



http://www.windowsecurity.com/articles/Pushing-Out-Security-Settings-Configured-Registry.html



http://www.windowsecurity.com/articles/group-policy-management-console.html











Technical System Landscape

30 November 2013

6. Technical System Landscape

6.1 Supported Operating SystemsSAP Visual Enterprise Author can run on three supported operating systems. These are:

Windows XP (SP3 32) and 64 - note that there is no SP3 for x64 operating system.

Vista (32 and 64).

Windows 7 (32 and 64).

The recommended Operating System is:

Windows 7 (32 and 64).

6.2 Hardware ConfigurationThe minimum configuration for SAP Visual Enterprise Author is:

Pentium 4 1Ghz processor or higher

512MB of RAM (more for large model and texture sizes)

3D hardware accelerator video card, capable of displaying 24-bit color and supportingShader Model 3.0

Internet Explorer 7

Microsoft DirectX, version 9.0c

The recommended configuration for SAP Visual Enterprise Author is:

Intel core i3 530 2.93 GHz

8GB of RAM

3D hardware accelerator video card with 512MB of RAM, supporting Shader Model 3.0

64 bit Operating System

Internet Explorer 8

Microsoft DirectX, version 9.0c



Technical System Landscape

November 2013 31

6.3 Additional RequirementsThere are a number of additional requirements, depending on the way in which you plan to useSAP Visual Enterprise Author:

To create custom PDF Templates using the included PDF Template Designer requiresone of the following versions of Adobe® Acrobat:

Acrobat 8.1+ Pro, Acrobat 3D v8.1+, Acrobat 9 Pro or Acrobat 9 Pro Extended

To view and save Autodesk 3ds max files, a copy of 3ds max 2010 and above must beinstalled

To view and save Autodesk Maya files, a copy of Maya 2010 and above must beinstalled

To view Inventor files, Autodesk Inventor Viewer must be installed

To view 3D content in a HTML Document with 3D (.html) files, SAP Visual Enterprise

Viewer must be installed

The .rh file type must be added to the Microsoft Windows Server 2003 “recognized file

type” set

If you are going to use XMetaL, a copy of XMetaL must be installed and activated

Note

XMetaL DITA-OT depends on a component included in JavaJDK. You can install the component by going to the Java maindownload page:http://www.oracle.com/technetwork/java/javase/downloads/index.html and choosing JDK Download .



Upgrade Information

32 November 2013

7. Upgrade InformationInstallation of SAP Visual Enterprise Author 7.1 does not upgrade or uninstall previous versions.These must be uninstalled manually if they are not required.

The user interface settings and licensing information is copied automatically from SAP VisualEnterprise Author 7.0 if found, for each user.



SAP Visual Enterprise Planner

November 2013 33

8. SAP Visual Enterprise Planner A key sub-component of SAP Visual Enterprise Author 7.1 is SAP Visual Enterprise Planner.This section deals with the specifics of this subcomponent which were not mentioned above.

The section discusses the following:

SAP Visual Enterprise Planner as a UI tool

SAP Visual Enterprise Planner in ERP

SAP Visual Enterprise Planner is a tool that enables the user to visually create or update amaterial BOM from a document assembly. A planning scope with alternative is created in ERPfor a document assembly to load in SAP Visual Enterprise Planner. When you publish thematerial BOM hierarchy back to ERP a material BOM is created.

Document assembly should already have been converted for light weight .rh files before loadinga planning scope in SAP Visual Enterprise Planner.

Note

You can find the most current information about the technicalimplementation of Visual Enterprise Planner on SAP ServiceMarketplace at

http://service.sap.com/instguides.

We strongly recommend that you use the documents availablehere. The guides are regularly updated.

Constraints

The business scenarios that are presented here serve as examples of how you can useSAP software in your company. The business scenarios are only intended as models anddo not necessarily run the way they are described here in your customer-specific systemlandscape. Ensure to check your requirements and systems to determine whether thesescenarios can be used productively at your site. Furthermore, we recommend that you testthese scenarios thoroughly in your test systems to ensure they are complete and free oferrors before going live.

This section primarily discusses the overall technical implementation of SAP VisualEnterprise Planner, rather than its subordinate components. This means that additionalsoftware dependencies might exist without being mentioned explicitly in this document. Youcan find more information on component-specific software dependencies in thecorresponding installation guides.

SAP Visual Enterprise Planner is extensively used in Product Lifecycle Management to creatematerial BOMs in an easy and visual way.

8.1 Software UnitsSAP Visual Enterprise Planner:

Material BOM: Software unit involved is SAP_APPL. The installation of the planner creates aregistry entry in REGEDIT which is the key source for opening the SAP Visual EnterprisePlanner from SAP.

When a planning scope is loaded in SAP Visual Enterprise Planner to create or update an XML,the related .rh file from the document assembly is downloaded into the folder VEP_workspace in

your user-specific SAP workspace.




34 November 2013

8.2 Software Component MatrixThis section provides an overview of which business scenario of SAP Visual Enterprise Planneruses which software unit.

BusinessScenario

Software Units

Key: X = mandatory (X) = optional

SAP_APPL

Material BOM X

8.3 System LandscapeThe figure below shows an overview of the technical system landscape for the integration withSAP Visual Enterprise Planner

Central System(DMS)

SAP ECC 6.0

SAP_APPL

Plant Specific System

SAP ECC 6.0

SAP_APPL

ABAP ABAP

Visual Author for

Manufacturing Planning

CAD System

File System for VMP

(XML+RH)

DU

DBPlanning

Scopes

Content Server

The planning scope created in a central system can have material BOMs created in plantspecific system. The plant specific system is given as an input in the transaction in the form oftarget system.




November 2013 35

8.4 Business Scenarios of SAP VisualEnterprise Planner

8.4.1 Create or Update a Material BOM using SAPVisual Enterprise Planner

Overview

Document assembly selected to create or update a planning scope for material BOMs is loadedin SAP Visual Enterprise Planner. When loading the material BOM, the system identifies if thereis any legacy child material BOM or planning scope for child and gives these as conflicts to beresolved. The resolved conflicts are taken into consideration while loading the planning scope inSAP Visual Enterprise Planner.

The loaded planning scope is arranged by dragging and dropping the components intorespective locations to create or update a material BOM in SAP. The system in which thematerial BOMs are to be created or updated depends on the target system associated with theplanning scope.

8.4.2 Create or Update a Planning Scope

Overview

This scenario enables the user to create a planning scope for an existing material BOM so thatthe material BOM can be loaded into the SAP Visual Enterprise Planner for furtherenhancements or modifications. The planning scope can also be created as a purchased partthat does not require any planning by itself in respect to its parent material BOM as well.

The planning scope can be updated with check out and purchased part flags. The associatedchild material BOMs can be disassociated.

A planning scope can be deleted.




36 November 2013

8.5 Technical System Landscape

Use

The figure below shows an overview of SAP Visual Enterprise Planner for creating or updating amaterial BOM using SAP Visual Enterprise Planner.

ERP VMP

Invoke(DBOM RH)

return

Generate monolitic file

Representing the DMS file

structure

return

Create

MBOM Structure

MBOM content

return

Create

MBOM

return

Assign

Instances

Manufacturing BOM ItemGrouping with SortOrder

Document BOM

Document BOM ItemManufacturing BOM

The table below shows the security aspect to be considered for the process step and whatmechanism applies.

Step Description Security Measure

Generate monolithic filerepresenting the DMS filestructure

The monolithic file isgenerated through theconversion process

Security aspects forconversion process.

Load document structure inthe form of planning scope in

SAP Visual EnterprisePlanner

An XML is generated for theplanning scope with all

resolved conflicts for childmaterial BOMs and isdownloaded to user specificSAP workspace

The monolithic rh file is alsodownloaded to user specificSAP workspace

As the workspace is specificto a user profile, there is no

risk of another user loggedinto the same system beingable to access the files.

Publish the material BOMback to ERP

The material BOM structuredin SAP Visual EnterprisePlanner is created or updatedin ERP




8.6 Authorizations

8.6.1 Standard Authorization ObjectsThe table below shows the security-relevant authorization objects that are required.

Standard Authorization Objects

AuthorizationObject

Field Value Description

MFG_PLNR

ACTVT 01 Create Planningscope

ACTVT 02 Change Planning

scope ACTVT 03 Display planning

scope

ACTVT 06 Delete Planningscope

8.7 User Administration and AuthenticationUser administration and authentication is only relevant for SAP Visual Enterprise Planner ratherthan the whole component.

An SAP Visual Enterprise Planner session is started from SAP GUI, where you must be alreadyauthenticated and allowed to access the planning state. SAP GUI downloads the required filesand starts SAP Visual Enterprise Planner.

To synchronize a planning session back to ERP, you must provide a valid ERP user name andpassword. Other connection data (host address, system ID, client ID, etc.) is already providedby SAP GUI. The system remembers these data fields, and they are pre-populated the nexttime you send a planning session to ERP. The password field is not pre-populated for securityreasons, and must be entered every time.

Communication between SAP Visual Enterprise Planner and ERP is established using astandard RFC method call.