Message text: SAP GTS: Legal check: Point (&) is not transferred I checked the configurations for the document types on the ECC and GTS side and there are no activation and mapping issues. We are on GTS 8.0. However, Project is one of the license-level attributes that can be enabled with Config. Licenses can then be created with project numbers managed as attributes. For standard sales processes (for example, selling controlled products to customers as part of a project), the system is able to determine a license for a specific project. Business scenario – Controlled products are moved from one project inventory to another within the same plant. This is achieved by a transfer display via MIGO transaction with motion type 415. If I created a purchase order in ECC, compliance documents are created in GTS without legal lock-in. The /SAPSLL/CUHD table and CDCUS field are marked with an “X”. No active legal regulations for the investigation could be found. “LELOC” Please let me know what additional configuration needs to be kept to fix the error. Currently, we have a legal regulation that represents two FTO for one country. There are two company codes in the loader and they are directly assigned to FTO`s V1.470 July 2004 English H42: Configuration Compliance Management of Global Commercial Services Configuration Guide SAP AG Neurottstr Building Blocks Configuration Guide.
16 69190 Walldorf Germany SAP Best Practices H42 Global Trade Services Compliance Mgmnt: Configuration Guide Copyright Copyright © 2004 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 of SAP AG. The information contained herein is subject to change without notice. Some software products distributed by SAP AG and its distributors contain proprietary software components from other software vendors. Microsoft®, WINDOWS, NT, EXCEL, Word®, PowerPoint®, ®® ® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2, DB2® Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390, AS/400, OS/390, OS/400®®®®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix, and Informix® Dynamic Server™ are trademarks of IBM Corporation in the United States and/or other countries. ORACLE is a registered trademark of ORACLE® Corporation. UNIX, X/Open, ® OSF/1® and Motif® are registered trademarks of Open® Group. Citrix, the Citrix logo®, ICA®, Program Neighborhood®, MetaFrame, WinFrame, VideoFrame®®®, MultiWin®, and other Citrix product names mentioned herein are trademarks of Citrix Systems, Inc.HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.
used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are joint trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned herein, together with their respective logos, are trademarks or registered trademarks of SAP AG in Germany and several other countries around the world. All other product and service names mentioned are trademarks of their respective companies. The data contained in this document is provided for informational purposes only. National product specifications may vary. © SAP AG Page 2 of 70 SAP H42 Best Practices Global Commercial Services Compliance Management: Configuration Guide Symbols Meaning of the symbol Warning example Note or advice recommendation syntax Typographical conventions Style description Sample text Words or characters that appear on the screen. This includes field names, screen titles, push buttons and menu names, paths, and options. References to other documents.
Sample text Highlighted words or phrases in body text, chart titles, and tables. SAMPLE TEXT System element names. This includes report names, program names, transaction codes, table names, and individual programming language keywords when surrounded by continuous text, such as SELECT and INCLUDE. Example of text screen output. This includes file and directory names and their paths, messages, source code, variable and parameter names, and installation, upgrade, and database tool names. SAMPLE TEXT keys on the keyboard, such as function keys (such as ENTER. Sample text Exact user input. These are words or characters that you enter into the system exactly as they appear in the documentation. Variable user input. The square brackets indicate that you are replacing these words and characters with the appropriate entries. © SAP AG F2) or page 3 of 70 SAP Best Practices H42 Global Trade Services Compliance Mgmnt: Content Compliance Management Configuration Guide: Configuration Guide…….
7 1 Purpose……………………… 7 2 Preparation………………. 7 2.1 3 Prerequisites…. 7 Configuration…………………. 8 3.1 Prerequisites in SAP R/3……………….. 8 3.1.1 Definition of the type of sales document in SAP R/3………. 25 3.14.4 Distribution of plants…………..