J62_BB_ConfigGuide_EN_DE

SAP ECC 5.00 June 2005 English Cross-Company Sales Order Processing (J62) Building Block Configuration Guide SAP AG Neurottstr. 16 69190 Walldorf Germany Nothing herein should be construed as constituting an additional warranty. S/390. Tivoli. OS/390. Outlook. HTML. National product specifications may vary.SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide Copyright © Copyright 2005 SAP AG. All rights reserved. OSF/1. JavaScript is a registered trademark of Sun Microsystems. Netfinity. XHTML and W3C are trademarks or registered trademarks of W3C®. Parallel Sysplex. mySAP. Citrix. and PowerPoint are registered trademarks of Microsoft Corporation. Sweden. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only. ICA. R/3. xApp. © SAP AG Page 2 of 13 .. XML. 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. Windows. Inc. SAP. Java is a registered trademark of Sun Microsystems.com. AS/400. WebSphere. xApps. IBM. World Wide Web Consortium. DB2. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Massachusetts Institute of Technology. MetaFrame. The information contained herein may be changed without prior notice. without representation or warranty of any kind. z/OS. xSeries. DB2 Universal Database. Inc. AIX. mySAP. All other product and service names mentioned are the trademarks of their respective companies. These materials are subject to change without notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Inc. Microsoft. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. iSeries. Intelligent Miner. MVS/ESA. UNIX. Data contained in this document serves informational purposes only. X/Open. used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB. zSeries. OS/400. OS/2. Program Neighborhood. and Motif are registered trademarks of the Open Group. Oracle is a registered trademark of Oracle Corporation. WinFrame. and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. and SAP Group shall not be liable for errors or omissions with respect to the materials. pSeries. if any. and MultiWin are trademarks or registered trademarks of Citrix Systems. AFP. VideoFrame. Example text EXAMPLE TEXT Emphasized words or phrases in body text. for example. for example. when surrounded by body text. Screen output. Example text EXAMPLE TEXT Example text <Example text> © SAP AG Page 3 of 13 . paths and options. screen titles. Exact user entry. Keys on the keyboard. function keys (such as F2) or the ENTER key. This includes file and directory names and their paths. source code. titles of graphics and tables. pushbuttons as well as menu names. These include report names. program names. and individual key words of a programming language.SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide Icons Icon Meaning Caution Example Note Recommendation Syntax Typographic Conventions Type Style Example text Description Words or characters that appear on the screen. Variable user entry. Cross-references to other documentation. These include field names. names of variables and parameters as well as names of installation. Names of elements in the system. These are words or characters that you enter in the system exactly as they appear in the documentation. upgrade and database tools. Pointed brackets indicate that you replace these words and characters with appropriate entries. SELECT and INCLUDE. transaction codes. messages. table names. .........1 Maintaining Intercompany Billing......4.................5 ..........................................................................................................................................................................................................3............................................................1 Defining Internal Customer Number by Sales Organization..8 ......7 4 Creating Master Data.5 3 Configuration.......1......................................................5 3......................................................................10 .....................4..1 Creating Classification View C20050......4..........................5 3.............................1 Prerequisites..................................................................................10 ...............4 Creating Condition for Inter-company Billing .......................................1.........3 Creating Batch Determination Condition Record C20050 ..................2......................................................................................................................................2 Creating Pricing Condition for material C20050 ........3 Maintaining Copy Control for Delivery Document to Billing Document....2 Defining Order Type for Intercompany Billing...........4..................5 ...................6 3.1..............5 1 Purpose.......................................8 ......................12 © SAP AG Page 4 of 13 .......SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide Contents Cross-Company Sales Order Processing: Configuration Guide.................................................5 2 Preparation.......................................................... On the Change View “View for Inter-Company Billing”: Overview screen. 2 Preparation .SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide Cross-Company Sales Order Processing: Configuration Guide 1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually. Access the activity using the following navigation options: IMG Menu Transaction Code Sales and Distribution → Billing → Intercompany Billing → Define Internal Customer Number By Sales Organization SPRO 2.2. refer to the SAP Best Practices Quick Guide.1 Maintaining Intercompany Billing 3.1.3. you must first install the following building blocks: Building Block # Layer 0 J19 Description All layer 0 building blocks Batch Management 3 Configuration Defining Internal Customer Number by Sales Organization .1 Prerequisites If you want to use this building block. If you do not want to configure manually and prefer an automated installation process using the SAP Best Practices Installation Assistant and other tools. Procedure 1. enter the following customer numbers for inter-company billing: © SAP AG Page 5 of 13 .1 Use The purpose of this activity is to create the customer numbers for the sales organizations used in the inter-company billing process. Description Standard Order Intercompany Billing Type IV Result The inter-company billing type has been assigned to the sales order type. make the following entries: Sales Doc Type OR 6. Access the activity using one of the following navigation options: IMG Menu Transaction Code Sales and Distribution → Billing → Intercompany Billing → Define Order Type for Intercompany Billing SPRO 2. choose Position. Choose Back (F3). On the Change View “Sales Order Types for Inter-Company Billing”: Overview screen.SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide 3. On the Change View “Sales Order Types for Inter-Company Billing”: Overview screen. 4. Save your settings. © SAP AG Page 6 of 13 . 3.2 Use Defining Order Type for Intercompany Billing The purpose of this activity is to assign the inter-company billing type which follows from a standard order. Choose Continue (Enter). Save your settings. 7.1. 5. Enter OR in the input field SalesDoc. 3. Result The customer numbers for the sales organizations have been created.Type in the Another entry dialog box. Procedure 1. Choose Back (F3). 4. On the New Entries: Details of Added Entries screen. 8. choose Position. enter the values shown below. enter the values shown below. 5.SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide 3. 10. choose New Entries. Secondly. 7. Save your settings. Choose Continue (Enter). Access the activity using the following navigation options: IMG Menu Transaction Code Sales and Distribution → Billing → Billing Documents → Maintain Copying Control For Billing Documents VTFL 2. On the Change View: Details of Added Entries screen. the item types in the delivery document which result in an intercompany billing item are also created. On the Change View “Header”: Overview screen. On the Display View “Header”: Overview screen. choose New Entries. Mark the line of your selected document types and double click on Item in the Dialog Structure.1. 6.3 Use Maintaining Copy Control for Delivery Document to Billing Document The purpose of this activity is to assign the source document for the inter-company billing document. 12. Enter IV in the input field Billing type and LF in the input field Delivery type in the Another entry dialog box. On the Change View “Header”: Overview screen. © SAP AG Page 7 of 13 . 9. 4. choose Display -> Change (Ctrl+F1). 11. 3. Choose Copying Control: Delivery document to billing document in the Choose Activity dialog box. Procedure 1. On the Change View “Item”: Overview screen. Access the activity using one of the following navigation options: SAP ECC Menu Transaction Code Logistics  Materials Management  Material Master  Material  Create MM01 © SAP AG Page 8 of 13 . Procedure 1. Result The inter-company billing type has been assigned to the delivery type.1 Creating Classification View C20050 The purpose of this activity is to create a classification view for the material C20050. Save your settings. Repeat steps 11. to 13.4. 14. Choose Back (F3).SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide 13. for the item category YG05 as shown in the screenshot below. 15. and the necessary item categories have been assigned as well. 4 Use Creating Master Data . On the Create Material (Initial Screen) screen. enter material number C20050 in the input field Material. Choose Back (F3). The system issues the sub-screen Values for Class 023_001 – Object C20050 (see below). select Classification by marking the appropriate line. On the Classification screen. Result You have created a classification view for C20050. 9. 8. Save your entries. 4. 3. The system issues a message that “Material type Trading goods and industry Mechanical engineering copied from master record”. Choose Enter. 10. On the Select View(s) dialog box. 6. enter 023_001 in the input field Class in the sub-screen Assignment (see below). Choose Enter. 11. 5. Choose Enter. 7. Choose Continue (Enter). © SAP AG Page 9 of 13 .SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide 2. 7. © SAP AG Page 10 of 13 . In the Key Combination dialog box. Choose Enter. 3. 5. Choose Back (F3).SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide . enter the values shown below. enter PR00 in the input field Condition type and 303 in the input field Table. On the Create Price Condition (PR00): Fast Entry screen. Procedure 1. On the Create Condition Records screen. . Save your entries. On the Create Batch Search Strategy: Initial Screen. Procedure 1. enter YBP1 in the input field Strategy type.2 Creating Pricing Condition for material C20050 Use In order to run through a sales activity. 6. Result The pricing condition for material C20050 has been created.4.3 Creating Batch Determination Condition Record C20050 Use The purpose of this activity is to create a batch search strategy for material C20010. Choose Key Combination. Transaction Code Access the activity using one of the following navigation options: VK15 2. 8. the pricing condition must be created for material C20010. Access the activity using one of the following navigation options: Transaction Code VCH1 2. This is used in the batch determination which takes place when creating a delivery (not in the sales order). 4. tick the radio button of Material with release status.4. 11. Choose Enter. 9. Choose Key combination. 12. On the Create Material (YBP1): Sort Rule screen. On the Create Material (YBP1): Classification screen. © SAP AG Page 11 of 13 . 4. mark the line of material C20050 and choose Selection Criteria. enter the values shown below. enter the values shown below. enter the values shown below. 8. Choose Enter. mark the line of material C20050 and choose Sort.SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide 3. In the Key Combination dialog box. 6. 7. On the Create Material (YBP1): Fast Entry screen. tick the radio button Material. Choose Back (F3). On the Create Material (YBP1): Fast Entry screen. 5. Choose Enter. 13. 10. On the Create Material (YBP1): Fast Entry screen. Procedure 1. © SAP AG Page 12 of 13 . On the Create Condition Records screen.4. Save your entries. enter PI02 in the input field Condition type. 6. Save your entries. Result The batch search strategy for material C20050 has been created. Choose Enter.4 Creating Condition for Inter-company Billing Use The purpose of this activity is to create a condition used in inter-company billing. enter the values shown below. Choose Back (F3) twice and leave the transaction. .SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide 14. 5. 3. On the Create Inter-company % Condition (PI02): Fast Entry screen. Access the activity using one of the following navigation options: Transaction Code VK15 2. 4. Choose Back (F3). 15. © SAP AG Page 13 of 13 .SAP Best Practices Cross-Company Sales Order Processing (J62): Configuration Guide Result The inter-company pricing condition has been created.