E10: Down-Payment Processing

Transcription

1 V1.470 July 2004 English E10: Down-Payment Processing Building Block Configuration Guide SAP AG Neurottstr Walldorf Germany

2 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 may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of 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 ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced 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 jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mysap, mysap.com, xapps, xapp, 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. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary. SAP AG Page 2 of 17

3 Icons Icon Meaning Caution Example Note Recommendation Syntax Typographic Conventions Type Style Example text Example text EXAMPLE TEXT Example text EXAMPLE TEXT Example text <Example text> Description Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation. Emphasized words or phrases in body text, titles of graphics and tables. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SAP AG Page 3 of 17

4 Contents Down-Payment Processing: Configuration Guide Purpose Preparation Prerequisites Configuration Billing Plan Maintaining Billing Plan Types for Milestone Billing Defining Date Descriptions Maintaining Date Category for Billing Plan Type Maintaining Date Proposals for Billing Plan Types Assigning Billing Plan Types to Sales Document Types Assigning Billing Plan Types to Item Categories Pricing Defining Customer Pricing s Pricing Determination Copy Control Copy Control: Header Copy Control: Item Financial Accounting Field Status for Posting Keys Maintaining Field Status Variants...17 SAP AG Page 4 of 17

5 Down-Payment Processing: Configuration Guide 1 Purpose The purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides. If you want to use BC Sets and CATT procedures for an automated installation process with the support of automated configuration tools, refer to the installation guide for the Down Payment Processing building block. 2 Preparation.2.1 Prerequisites Building Blocks The following building blocks form the basis for all mysap All-in-One High Tech and mysap Allin-One Industrial Machinery and Components solutions. You only have to install these building blocks once. Building Blocks Comment Baseline Building Blocks B32 - Best Practices R/3 Installation J02 - Organizational Structure J03 - Financial Accounting J08 - Cost/Profit Center Accounting J05 - Material Management J04 - Sales and Distribution J06 - Production Planning J07 - Quality Management J14 - Human Resources J16 - Smart Form Setup J17 - Profitability Analysis J18 - Product Cost Controlling J20 - Cost Object Controlling (Make-to-Order) J21 - Cost Object Controlling (Make-to-Stock) Industry-Generic Blocks SAP AG Page 5 of 17

6 Building Blocks Comment A01 - DI Basic Settings E04 - Supplement Settings H39 - CO/PA Supplement Settings E30 - MTO Quotation Processing E31 - MTO Sales Order Processing 3 Configuration.3.1 Billing Plan Maintaining Billing Plan Types for Milestone Billing A down payment agreement is created as a deadline in a billing plan. You define a billing plan type for this here. OVBO Sales and Distribution Billing Billing Plan Define Billing Plan Types Maintain billing plan types for milestone billing 2. To create a new billing plan type, choose New entries. 3. Make the following entries for the new billing plan type: Field name Description R/O/C r action and values Note Billing plan type R Y1 Milestone billing Start date R 01 Today s date Online order R Y Fcode- OvervScrn R Save your entries. SAP AG Page 6 of 17

7 3.1.2 Defining Date Descriptions Typically one milestone in a billing plan is the delivery. You define an additional date description for this here. 1. Access the activity using the following navigation options: SPRO 2. To create a new date description, choose New Entries. 3. Make the following entries for the new date description: Sales and Distribution Billing Billing Plan Define Date Descriptions Field name Description R/O/C r action and values Note DtDs R YM01 Date description R Delivery 4. Save your entries Maintaining Date Category for Billing Plan Type In this step, you assign and allocate date categories to the newly-defined billing plan type. Prerequisites Definition of billing plan type and date categories as described above. OVBJ Sales and Distribution Billing Billing Plan Define and assign Date Categories 2. Choose the activity Maintain Date Category for Billing Plan Type. 3. To create new assignments, choose New entries. 4. Make the following entries for the billing plan type and date categories. Field name Description R/O/C r action and values BillingPlanType R Y1 Date category R 01 Date descript. R YM01 Note SAP AG Page 7 of 17

8 Field name Description R/O/C r action and values Billing rule R 1 Fixed date R 0 Billing block R 02 BillingPlanType R Y1 Date category R 02 Date descript. R 0008 Billing rule R 3 Fixed date Billing block R 02 BillingPlanType R Y1 Date category R 03 Date descript. R 0009 Billing rule R 4 Fixed date R 0 Billing block Billing type R FAZ BillingPlanType R Y1 Date category R 04 Date descript. R 0009 Billing rule R 5 Fixed date R 0 Billing block Billing type R FAZ 5. Choose Back and choose the activity Allocate date category. 6. Make the following entries for the billing plan type: Field name Description R/O/C r action and values BillingPlanType R Y1 DD R Save your entries. Note Note SAP AG Page 8 of 17

9 3.1.4 Maintaining Date Proposals for Billing Plan Types The purpose of this activity is to create a reference billing plan for a billing plan type. The following description is only an example for such a reference billing plan. You can define any other reference billing plan. Prerequisites Reference billing plans are not transported. Definition of the billing plan type as described above. OVBM 2. Choose the newly-defined billing plan type Y1. 3. To create a reference billing plan, choose Maintain data. Sales and Distribution Billing Billing Plan Maintain date proposals for billing plan types 4. Make the following entries for the reference billing plan or define a reference billing plan on your own: Field name Description R/O/C r action and values Note Start date <start date for the reference billing plan> e.g. today s date Billing date DtDs R 0009 <billing date for the down payment> e.g. today s date % <percentage of value to be invoiced with down payment> e.g. 10 Block BR R 4 Dcat R 03 Billing type R FAZ Billing date <billing date for the first milestone billing> e.g. today s date + 6 months SAP AG Page 9 of 17

10 Field name Description R/O/C r action and values Note DtDs R YM01 % <percentage of value to be invoiced with milestone billing> e.g. 60 Block R 02 BR R 1 Dcat R 01 Billing type Billing date DtDs R 0008 % Block R 02 BR R 3 Dcat R 02 Billing type 5. Save your entries. <billing date for the closing invoice> e.g. today s date + 8 months SAP AG Page 10 of 17

11 3.1.5 Assigning Billing Plan Types to Sales Document Types In this step, you assign each sales document type that is used with billing plans to the billing plan type. Prerequisites Definition of billing plan type as described above. OVBP Sales and Distribution Billing Billing Plan Assign billing plan types to sales document types 2. On the Change View Maintain Assignment of Billing Plan Type to Sales Doc. T screen, make the following entries: Field name Description R/O/C r action and values Note SaTy BillPlanTy R Y1 3. Save your entries. <your sales document type> Assigning Billing Plan Types to Item Categories In this step, you assign each item category that is used with billing plans to the billing plan type. Prerequisites Definition of the billing plan type as described above. OVBR Sales and Distribution Billing Billing Plan Assign billing plan types to item categories 2. On the Change View: Maintain Assignment of Billing Plan Type to Item Catego screen, make the following entries: Field name Description R/O/C r action and values Note ItCa BillR R I <your item category> SAP AG Page 11 of 17

12 Field name Description R/O/C r action and values Note BillPlanTy R Y1 3. Save your entries..3.2 Pricing Defining Customer Pricing s In order that the correct pricing procedure for customers who work with down payments is determined, you define a customer pricing procedure. SPRO Sales and Distribution Basic Functions Pricing Pricing Control Define and assign pricing procedures Define customer pricing procedure 2. On the Change View Define Customer Pricing s : Overview screen, choose New entries. 3. Make the following entries: Field name Description R/O/C r action and values CuPP R Y Description 4. Save your entries. With down payments Note Pricing Determination You use the newly-defined customer pricing procedure to define the pricing procedure determination. Prerequisites The definition of a pricing procedure and customer pricing procedure as described previously. SAP AG Page 12 of 17

13 OVKK Sales and Distribution Basic Functions Pricing Pricing Control Define and assign pricing procedures Define Pricing Determination 2. On the Change View Pricing s: Determination in Sales Docs : Overview screen, choose New Entries. 3. Make an entry for each sales area, that is to use the defined pricing procedure: Field name Description R/O/C r action and values SOrg. DChl Dv DoPr R A CuPP R Y <your sales organization> <your distribution channel> <your division> PriPr. R ZDPJUS Ctyp R PR00 4. Save your entries. Note.3.3 Copy Control Copy Control: Header To create down payment requests with reference to sales documents, you define the copy control for the header of the sales document and the items. VTFA Sales and Distribution Billing Billing Documents Maintain Copying Control for Billing Documents Copying control: Sales document to billing document SAP AG Page 13 of 17

14 2. On the Display View Header : Overview screen, choose Display Change. 3. Choose New entries and make the following entries: Field name Description R/O/C r action and values Note Target billing type Source sls doc. Type Copying requirements 4. Save your entries and choose Back. R FAZ R 001 <your sales document type, YMTA> 5. Select the new entry and choose the Item folder in the left screen area. 6. Choose New Entries and make the following entries: Field name Description R/O/C r action and values Note Target billing type R FAZ Source sls doc. Type Item Category Copying requirements R 020 Date VBRK/VBRP R 000 Billing quantity R A Pos./neg. quantitiy R + Pricing type R G 7. Save your entries. <your sales document type, YMTA > <your item category, YMT1, YMT2> Copy Control: Item To create invoices with reference to sales documents, you define the copy control for the header of the sales document and the items. VTFA Sales and Distribution Billing Billing Documents Maintain Copying Control for Billing Documents Copying control: Sales document to billing document SAP AG Page 14 of 17

15 2. On the Display View Header : Overview screen, choose Display Change. 3. Choose New entries and make the following entries: Field name Description R/O/C r action and values Note Target billing type R F2 Source sls doc. Type Copying requirements R 001 Copy item number R X 4. Save your entries. 5. Select the new entry and choose the Item folder. 6. Choose New Entries and make the following entries: <your sales document type> Field name Description R/O/C r action and values Note Target billing type R F2 Source sls doc. Type Item Category Copying requirements R 023 Date VBRK/VBRP R 000 Billing quantity R A Pos./neg. quantitiy R + Pricing type R K 7. Save your entries. <your sales document type> <your item category>.3.4 Financial Accounting Field Status for Posting Keys A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, you have to maintain the field status for posting key 19 and 16 as described in this step. OB41 Financial Accounting General Ledger Accounting Business Transactions G/L Account Posting Carry out and SAP AG Page 15 of 17

16 check document settings Define Posting Keys 2. To post key 19 (Special gen. ledger customer), the Sales order field must not be hidden (recommendation: optional entry). To check this, double-click the entry 19, choose Field status and choose Additional account assignments. 3. For the Sales order field, select the radio button for Req. Entry or Opt. entry. 4. Save your settings. 5. Double-click on the entry 16, choose Field status and choose General Data, the field Text should be as Opt. Entry. SAP AG Page 16 of 17

17 3.4.2 Maintaining Field Status Variants A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, you maintain the field status variant for the company code as described in this step. OB14 Financial Accounting General Ledger Accounting Business Transactions G/L Account Posting carry out and check document settings Maintain field status variants 2. In the Determine Work Area: Entry dialog box, enter the number of your field status variant. 3. For the field status variant of your company code, the sales order under the field status group Accounts for down payments received (G031) under additional account assignment must not be hidden (recommendation: optional entry). To check this, double-click the entry G Choose Additional account assignments. 5. For the Sales order field, select the radio button for Req. Entry or Opt. entry. 6. For the field status variant of your company code, the sales order under the field status group Reconciliation accounts (G067) under additional account assignment must not be hidden (recommendation: optional entry). To check this, double-click the entry G Choose Additional account assignments. 8. For the Sales order field, select the radio button for Req. Entry or Opt. entry. 9. Save your entries. SAP AG Page 17 of 17