SAP R/3 Enterprise

Extension Set 1.10

Author: Werner Herhuth April 2003

SCM650 Cross-Functional Customizing in SD

Instructor Guide Level 3 Key to icons in the Instructor Guide:

Timing Next Slide (s) Instructor Demonstration Exercises Activity Summary Objectives Business Scenario
Sz en ari o B us in es s

Hints and Tips Warning or Caution Internal Note

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Contents SAP Contacts...................................................................................................7

Walldorf...............................................................................................................................7 North America......................................................................................................................7

Course Details.................................................................................................8
Duration...............................................................................................................................8 Course and other materials (training course).......................................................................8

Revisions to Previous Instructor Guide (4.6C).............................................9

Differences between 4.6C and 4.7.......................................................................................9

Trainer Profile................................................................................................10
Knowledge needed:...........................................................................................................10 Recommended courses to have attended:........................................................................10 Recommended reading:....................................................................................................10 How to prepare for the course:..........................................................................................10

Training System.............................................................................................11
Data Needed......................................................................................................................11 Master Data for Participants..............................................................................................11

Preparations in System................................................................................12
User ID and Passwords for Participants............................................................................12 Example ABAPs................................................................................................................12 CATTs...............................................................................................................................12 Some new Menu Paths for Unit 9 (Interface Modifications) missing in the participant handbook ............................................................................................................................................12

Course and Unit Goals..................................................................................13 Scenario..........................................................................................................14 Course Structure...........................................................................................15 Timetable........................................................................................................16

Day 1.................................................................................................................................16 Day 2.................................................................................................................................16 Day 3.................................................................................................................................17

Introduction to the Course...........................................................................18

Target Group......................................................................................................................18 Course goals......................................................................................................................18 Course Objectives.............................................................................................................18 Demonstration: SD Curriculum in the Internet...................................................................18

Understanding the Organizational Structures...........................................19

April 2003 Page 2

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

90 min..................................................................................................................................19 Topics..................................................................................................................................19 Place unit in context.............................................................................................................19 Unit Objectives....................................................................................................................19 Sales Organization...............................................................................................................19 Distribution Channels..........................................................................................................19 Division...............................................................................................................................19 Sales Area............................................................................................................................19 NEW SLIDE: Division and Business Area Account Assignment........................................20 Optional Organizational Elements in SD.............................................................................20 Demonstration......................................................................................................................20 Demonstration .....................................................................................................................22 Shared Master Data - Concept.............................................................................................22 Shared Master Data Example and Limits..........................................................................23 Shared Master Data and SIS.................................................................................................23 Multi-Divisional Sales Documents......................................................................................23 Demonstration......................................................................................................................24 Exercises..............................................................................................................................25

Copying Control............................................................................................26
140 min................................................................................................................................26 Topics..................................................................................................................................26 Place the unit in context.......................................................................................................26 Unit objectives.....................................................................................................................26 Document Flow....................................................................................................................26 Creating with Reference (1) + (2)........................................................................................27 Demonstration......................................................................................................................27 Copying Control Tables - Overview....................................................................................27 Copying Requirements.........................................................................................................28 Demonstration......................................................................................................................28 Copying Control - Header Level..........................................................................................29 Demonstration......................................................................................................................29 Demonstration......................................................................................................................30 Copying Control Item Level (1)........................................................................................31 Copying Control Item Level (2)........................................................................................31 Reference Status Update......................................................................................................31 Demonstration......................................................................................................................32 "Copying Control" Exercises...............................................................................................33

Text Control ..................................................................................................35

120 min................................................................................................................................35 Topics..................................................................................................................................35
April 2003 Page 3

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Place the unit in context.......................................................................................................35 Unit objectives.....................................................................................................................35 Texts....................................................................................................................................35 Using Texts in Business Processes.......................................................................................36 Text Control Overview (Sales Document)...........................................................................36 Demonstration......................................................................................................................36 Customizing for Text Control (1) to (5)...............................................................................37 Demonstration......................................................................................................................37 Demonstration......................................................................................................................37 Demonstration .....................................................................................................................38 Using Texts as Reference Copying Texts..........................................................................39 Demonstration .....................................................................................................................39 Text Source Preceding Document for Billing Documents................................................39 NEW SLIDE: Customer Specific Data Transfer Routine for Texts....................................39 OPTIONAL Demonstration of Using a user exit for texts................................................40 Exercises..............................................................................................................................40

Output.............................................................................................................41
90 min..................................................................................................................................41 Topics..................................................................................................................................41 Place the unit in context.......................................................................................................41 Unit objectives.....................................................................................................................41 Output Types, Transmission Media, Communication Strategy, Timing of Output..............41 Overview of Output Determination......................................................................................41 Output Determination Access Sequence...........................................................................41 Demonstration......................................................................................................................42 Output Determination Analysis.........................................................................................42 Exercises..............................................................................................................................42

Processing Output........................................................................................43
180 min................................................................................................................................43 Topics..................................................................................................................................43 Place the unit in context.......................................................................................................43 Unit objectives.....................................................................................................................43 Procuring and Preparing Data..............................................................................................43 Printing Data........................................................................................................................43 Example: Output BA00 (Order Confirmation).....................................................................44 New Fields for Printing Documents: Case 1 (Simple Case).................................................44 Demonstration (Part 1).........................................................................................................44 Demonstration (Part 2).........................................................................................................45 New Fields for Printing Documents: Case 2 (Complex case)...............................................45 Integrating a New Output Type............................................................................................46
April 2003 Page 4

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Example: Customer's Material Label ZMAT.......................................................................46 Demonstration: Customer's Material Label ZMAT..............................................................47 Exercises..............................................................................................................................47

System Modifications....................................................................................48
150 min................................................................................................................................48 Topics..................................................................................................................................48 Place unit in context.............................................................................................................48 Unit objectives.....................................................................................................................48 System Modification Overview...........................................................................................48 Elements of System Enhancement.......................................................................................48 Demonstration......................................................................................................................48 Adding New Fields with Condition Technique....................................................................49 Demonstration .....................................................................................................................49 Adding New Fields Without Condition Technique .............................................................49 Reserve Fields in Customer and Material Master.................................................................50 Demonstration .....................................................................................................................50 Routines...............................................................................................................................51 Demonstration .....................................................................................................................51 User Exits.............................................................................................................................52 Demonstration .....................................................................................................................52 Extending SAP Transactions................................................................................................52 Example: Function Module Exit SDVFX004.......................................................................53 Demonstration .....................................................................................................................53 Business Transaction Events (BTE).....................................................................................54 Demonstration of Business Transaction Events (BTE)....................................................54 Preview of Business Add-Inns.............................................................................................55 Exercises..............................................................................................................................55

Lists................................................................................................................56
60 min..................................................................................................................................56 Topics..................................................................................................................................56 Place unit in context.............................................................................................................56 Lists and List Viewer...........................................................................................................56 NEW SLIDE: New Fields For Lists Of Sales And Distribution Documents........................56 Demonstration .....................................................................................................................56 OPTIONAL Demonstration New Fields For Lists Of Sales And Distribution Documents ..............................................................................................................................................56 Exercises (can also postponed to the end of the course).......................................................57

Interface Modifications.................................................................................58
60 min..................................................................................................................................58
April 2003 Page 5

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Topics..................................................................................................................................58 Place the unit in context.......................................................................................................58 Unit objectives.....................................................................................................................58 Customer Master..................................................................................................................58 Customer Master Account Groups....................................................................................58 Customer Master - Selecting Fields for Data Groups...........................................................59 Customer Master - Selecting Fields for Account Groups ...................................................59 Customer Master - Additional Influences on Field Selection ..............................................59 Customer Master - Linking Rules in Field Selection ...........................................................59 Table Control.......................................................................................................................62 Demonstration .....................................................................................................................62 Transaction Variants / Screen Variants / GuiXT..................................................................62 Demonstration......................................................................................................................62 NEW SLIDE: Calling Transaction Variants for VA01........................................................62 Exercises..............................................................................................................................63

Unit: Conclusion............................................................................................64
15 mins................................................................................................................................64

Appendix........................................................................................................65
Coding of the Copying Requirement 904 for invoice items (part of the training master system)..................................................................................................................................65 Coding of the Data Transfer Routine 91 for texts (part of the training master system)........66 Contents of the Report Z_LO650_CODE (part of the training master system)....................67 Coding of the Function Module ZZLO650_INTERFACE_00503306 (part of the training master system)......................................................................................................................68

April 2003

Page 6

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

SAP Contacts
Walldorf Werner Herhuth Mail: Werner Herhuth Internet: [email protected] Phone: +49 6227 748987 North America Don Gosnell Mail: Donald Gosnell Internet: [email protected] Phone: 404 943-2850

April 2003

Page 7

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Course Details
Duration 3 days Course and other materials (training course) Course folder SCM650 ASAP Guides: Printout Design (Mat. No: 50022337) (Note: This guide can be ordered in the SAP-SHOP.)

April 2003

Page 8

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Revisions to Previous Instructor Guide (4.6C)

Differences between 4.6C and 4.7 The unit Data Transfer was removed from the course. In the meantime there are some new approaches like Legacy Migration Workbench (LSMW) and other aspects, so that we could no longer cover the topic adequately. The interested customer may attend the 5.day !! course BC420 Data Transfer. Furthermore the unit Organizational Structures in SD was renamed in Understanding the Organizational Structures to emphasize, that we expect that participants already know the basic elements so that we can make a review and concentrate on the problem areas. Finally the unit Lists was positioned after unit System Modifications and upgraded a bit with a slide and demo showing how to add a new field for the list of sales orders.

April 2003

Page 9

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Trainer Profile
Knowledge needed: Good understanding of the processes and functions in all of SD SD Customizing Basic understanding of ABAP/4 Recommended courses to have attended: SCM600, SCM605, SCM610, SCM615, (SCM620) Recommended reading: SD online documentation SD IMG documentation Extended help for transaction CMOD (Project Management of SAP Enhancements) How to prepare for the course: Visit SCM650 Work through the course demonstrations and exercises! This must be done to ensure a smooth flow to the demonstrations during the course, since many of the topics you will present are more complex than those found in other SD courses.

April 2003

Page 10

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Training System
Data Needed This course has been created as a continuation of LO150. Therefore we have also used part of the LO150 data. The system contains master data for the instructor to be used in the demos: Customer IDES Customer number
2300 1174

Name

Sales organization / Distribution channel / Division

1000 / 12 / 00 1000 / 12 / 00

1 2

Motormarkt Heidelberg GmbH Motormarkt Stuttgart GmbH

Material

IDES Material number

1400-100 1400-200 1400-300 1400-310

Description

Sales organization / Distribution channel

1000 / 12 1000 / 12 1000 / 12 1000 / 12

Stock

Plant / storage location

1000 / 0001 1000 / 0001 1000 / 0001 1000 / 0001

1 2 3 4

"Deluxe" headlight "Deluxe" back light Motorcycle1200 cm3 - Model "SUNFUN" Motorcycle 350 cm3 - Model "Junior"

100 100 100 100

Master Data for Participants Data has already been created in the training master system (copied from master data used by the instructor). For each participant group, there are: 2 customer master records in the sales area: 1000, 12, 00. T-S50A## and T-S50B## (## = group 01-20). 4 material master records with stock in plant 1000 T-AS1##, T-AS2##, T-AS3## and T-AS4##.

April 2003

Page 11

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Preparations in System
User ID and Passwords for Participants User ID for participants: SCM650-## (where ## = group number) Users must be created before starting the course using transaction ZUSR

ZUSR Copy from Copy (= name of course) No of workgroups Initial-password Execute The course should be already assigned to a training system with deactivated lock mechanism for maintaining tables. If the lock mechanism is still active you can start report: ZSENQOFF in transaction SE38. (Report: ZSENQON would then reactivate the lock mechanism.) This is necessary to avoid long delays for the students when doing the exercises. If you have not already done so, use report ZDEBLAN to convert the language of the customer master to the language of the country in which the course is being held. Example ABAPs There is an ABAP/4 program called Z_LO650_CODE in the system that contains the relevant coding for individual tasks (as a copying reference, etc). CATTs The scenario of the course continues from SCM600 (ex LO150,) so to keep things simple, data has been used from course SCM600. Some new Menu Paths for Unit 9 (Interface Modifications) missing in the participant handbook During the first teach it turned out that in Release 4.7 some details in the menu paths concerning Transaction Variants and Partner Determination were changed without notice. The changes are therefore not in the participant handbook. Please see the demos in Unit 9 and give a hint to participants before the exercises of unit 9.
April 2003 Page 12

SCM650-99 SCM650 20 TRAINING

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Course and Unit Goals

Business processes in sales and distribution are represented in the Sales and Distribution application component in the R/3 System with documents and master data. The implementation team needs a thorough understanding of cross-functional Customizing in order to adapt the component to meet the customer's needs. This course discusses how you can configure the system as well as related topics such as organizational structures, messages, system modifications and master data transfer.

April 2003

Page 13

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Scenario
The MSI project team for implementing R/3 has used the standard R/3 System as much as possible to represent MSI's business processes. However, some departments (such as Customer Service) have particular requests that can only be met by using cross-functional Customizing. As a member of the project team, you must get to know the functions in cross-functional Customizing so that you can find solutions for these requests. The preparations for going live also include managing authorizations and planning how to transfer data.

April 2003

Page 14

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Course Structure
Understanding the Organizational Structures: Increase understanding of the organizational structures in SD by introducing all the optional organizational elements including the sales person. Show how the organizational structure affects the master data and evaluations as well as how shared (common) master data can be used. Copying Control: Use these functions in the creation of a new sales document type (sample quotation). Text Determination: Create new text types for the sales document header and item. Output: Introduce output determination and modify the settings to meet specific requirements (change output condition records for output type BA00 for certain customers to fax). Processing Output: Among other things, introduce how to display the new text types from the "Output" chapter in printed documents. System Modifications: Introduce the basic principle behind system modifications in Sales and Distribution and create an example (billing document variants) that includes various elements such as reserve fields and copying requirements. Talk about the enhancement concept (transaction CMOD) and make an example enhancement project. Lists: Display the options of the List Viewer including adding a new field. Interface Modifications: Introduce the account group with field selection for customer master and talk about the field selection for the material master. Show how the user can use Table Control, using VA01 as an example. Show what the transaction variants do and show a simple example.

April 2003

Page 15

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Timetable
Day 1 Approx. times 10:00-10:30 10:30-12:00 12:00-13:00 13:00-13:30 13:30-14:30 14:30-14:50 14:50-16:20 16:20-17:00 Day 2 Approx. times 9:00-11:00 11:00-11:20 11:20-12:00 12:00-13:00 13:00-14:00 14:00-14:30 14:30-14:50 14:50-16:30 16:30-17:00 Contents: Units and Topics Text determination Coffee Exercises Lunch Output bungen Coffee Processing output Exercises Activities: Trainer and Participant Contents: Units and Topics Introduction to the course Understanding organizational structures Lunch Exercises Copying control (1) Coffee Copying control (2) Exercises Activities: Trainer and Participant

April 2003

Page 16

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Day 3 Approx. times 9:00-10:50 10:50-11:10 11:10-11:30 11:30-12:00 12:00-13:00 13:00-14:00 14:00-15:00 15:00-16:00 Contents: Units and Topics System modifications (1) Coffee System modifications (2) Exercises Lunch Lists Interface modifications Exercises Activities: Trainer and Participant

April 2003

Page 17

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Introduction to the Course

The instructor and students introduce themselves. Explain the organizational aspects of the course. Get to know the group and find out about their expectations of the course. Cover any logistic issues (breaks, phones, restrooms, lunch, start and end times). Stress that this is a Level 3 course, and as such, will concentrate on the configuration aspects of pricing. The students will spend a considerable amount of time working on exercises, including building a complete working pricing model.

Target Group Course goals Course Objectives Explain how you can access in the internet the courses offered by SAP, the curriculum and the course descriptions and how you can register for courses.

Demonstration: SD Curriculum in the Internet.

Go to the Internet
Internet address www.sap.com Choose Education Choose Education Home Choose your local country Display the Curriculum: the following steps will be different depending on the country you have chosen: as an example for the USA it would be: Choose USA Choose SAP R/3 courses Choose Logistics Customer Order Management Explain the curriculum.

Choose the course description for the course, which you are teaching
Explain the prerequisites and the objectives for this course.

April 2003

Page 18

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Understanding the Organizational Structures

90 min

Topics Key organizational elements used in SD Defining organizational structures by linking them to organizational elements Shared master data Impact of organizational structure on master data and reporting Place unit in context See scenario slide in the unit

Unit Objectives At the conclusion of this unit, participants will be able to: Describe the main organizational elements in SD and their relationships Create organizational elements and use them to build organizational structures Use shared master data techniques to reduce maintenance workload Make Customizing settings which affect the use of organizational elements

Sales Organization Distribution Channels Division As an introduction, present the basic organizational elements in SD.

Sales Area A simple organizational structure is often better than a complex one. For example, it makes master data maintenance or order entry clearer for the user.

April 2003

Page 19

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

NEW SLIDE: Division and Business Area Account Assignment This slide helps to create an understanding for the possible problem in the customer project, if the customer says In our company, a product can belong to more than one division. .

Optional Organizational Elements in SD Introduce the sales office, sales group and sales persons. It is often not clearly understood by the user that they can analyze and evaluate data in the Sales Information System based on the levels they created in the organizational structure. Instead, they often create far too many sales areas.

Demonstration <Approx. duration> Menu path:

Tools AcceleratedSAP Customizing Edit Project SAP Reference IMG

Enterprise Structure Definition Sales and Distribution
Sales organization Distribution channel Sales office Sales group

The sales person can be managed as an employee in the Human Resources (HR) component. In HR the sales person is assigned to a sales organization, sales group and sales office. If your system does not include the Human Resources application module, you can transport the HR tables needed for creating, changing or displaying a sales employee from client 000 to the target client. (IMG menu: Sales and Distribution Master Data Business partners Use sales employee without HR). Example: 1.) Display customer master 2300 2.) Partner function SE Number 1264 Lindgren
April 2003 Page 20

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

3.) Double click on this partner. 4.) Go to "Display sales employee" screen 5.) Choose the Sales data view and choose Display You can see that the partner has been assigned to sales group 103

April 2003

Page 21

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Demonstration <Approx. duration> 1. Define a new distribution channel, for example, Y1 telephone sales 2. Assign the new distribution channel to sales organization 1000

Enterprise Structure Maintain structure Assignment Sales and Distribution

Assign distribution channel to sales organization
3. Create two new sales areas with the new distribution channel and division 00 (cross-division) and 02 (motorcycles).

Set up sales area

4. Maintain the business area account assignment for the new sales area

Business Area Account Assignment Define Rules by Sales Area Choose Rule 1 for your sales areas.

Shared Master Data - Concept Shared master data minimizes the amount of master record maintenance that must take place. You can specify in Customizing which sales areas can use the shared master data. On the "sales organization/distribution channel" level, you can define which distribution channel should be used for accessing the condition records and which should be used for accessing customer and material master data. On the "sales organization/division" level, you can define which division should be used for accessing condition records and which division should be used for accessing the customer master data.

April 2003

Page 22

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Shared Master Data Example and Limits Discuss the example on the slide

Shared Master Data and SIS Even if you are using shared master data, the data values transferred to SIS come from the values in the sales, delivery and billing documents. This allows detailed evaluations for all organizational structures while minimizing the amount of master data that needs to be maintained.

Multi-Divisional Sales Documents This discusses the problem of header and item divisions: If you want the division at item level to be proposed from the material master record for the item, the "Item division" field must be selected in Customizing for the sales document type. If you select this field, the system proposes the division from the material master record. If you leave the field blank, the division in the sales document header applies to all items. You must define the correct source field for the division in SIS so that this setting affects the updating rules in the sales information system accordingly.

April 2003

Page 23

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Demonstration <approx. duration> The new sales area Y1 should use the data from sales area 1000, 12, 00 in order to minimize the maintenance workload Menu path:

Tools AcceleratedSAP Customizing Edit Project SAP Reference IMG

Sales and Distribution Master Data Define Common Distribution Channels
1. Assign distribution channel 12 to sales organization 1000, distribution channel Y1, for conditions and the customer/material master data. 2. Show that the user cannot yet create an order for sales area (1000, Y1, 00). (Message: Order type OR has not been defined for sales area 1000, Y1,00) 3. Assign the sales document types permitted for the new sales area to the sales area by copying the agreements from distribution channel 10.

Sales and Distribution Sales Sales Documents Sales Document Header Assign Sales Area to Sales Document Types Combine distribution channels
Assign distribution channel 10 to (1000,Y1). 4. So that orders can be created properly, you must also enter the pricing determination procedure.

Sales and Distribution Basic Functions Pricing Pricing Control Define and Assign Pricing Procedures
Choose: Define Pricing Procedure Determination Place your cursor on sales area (1000,10,00) Select the entry for document procedure "A" and customer procedure "1" and choose "Copy as.." Overwrite the distribution channel with your new distribution channel and choose Enter. Save your entries. 5. You can now create an order for sales area (1000,Y1,00)

April 2003

Page 24

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Exercises 30 min The participants practice what you showed in the demo.

April 2003

Page 25

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Copying Control
140 min

Topics Configuring copying control Creating requirements and transferring data Place the unit in context See the unit scenario

Unit objectives By the conclusion of this unit, the participants are able to: Analyze the document flow Create documents with reference Use copying control tables to meet special requirements

Sales document type ZAG sample quotation has already been created in the training master system. You can study it and delete it before the course starts in order to create it again in the demo (maybe create a safety copy, such as YQT).

Document Flow A business process is composed of individual process steps that are recorded as documents. The data from a previous document is copied into its successor and this chain of steps is recorded in the document flow.

April 2003

Page 26

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Creating with Reference (1) + (2) You can create sales documents with reference to documents that were created previously. You can enter a different requested delivery date in the new document for all the items. You can also call up a selection screen for the referenced document. Before the data is copied, the system checks whether certain requirements have been met. Examples of these requirements are: Do the reference document and copied document have the same sold-to party? Has the item being copied already been rejected? Have the items being copied already been referenced? Has the validity period of the reference document been exceeded? You cannot copy incomplete sales documents.

Note:

Demonstration <Approx. duration> 1.) Create a quotation for customer 2300 with two items. 2.) Maintain the name and phone number in the header purchase order data (important for the next demo!) 3.) Create an order with reference to this quotation. 4.) Only copy one item. 5.) Display document flow.

Copying Control Tables - Overview The copying control tables are an important part of Customizing in your R/3 System. These tables control many of the functions performed when you create a sales document with reference to a preceding document. There are copying control tables for sales documents, deliveries and billing documents. There are control tables for all levels in the sales document.

April 2003

Page 27

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Copying Requirements Before data is copied from the source document to the target document, specific requirements must be satisfied at each level. These requirements are contained in the ABAB/4 routines and are chosen by their identification numbers in the copying control tables. Routines can be modified, or new routines can be created with transaction VOFM. Once the copying requirements are satisfied, the specified data transfer routines are executed.

Demonstration <Approx. duration> Show transaction VOFM. Menu path: (in IMG) Sales and Distribution System Modification Routines Define copying requirements

April 2003

Page 28

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Copying Control - Header Level In copying control, you define which source document types may be copied into which target document types. The system will not let you create a sales document with reference to another document type that is not in the copying control.

Demonstration <Approx. duration> Demo 1: Source document type - Target document type 1.) Create a new quotation for customer 2300. 2.) Show that you cannot copy a quotation to another quotation, for example. Demo 2: Copying requirement 001 "Same customer in header" 1.) Create order 2.) Enter customer 1174 as the sold-to party

Sales document Create with Reference use quotation created above.

3.) Not possible because the sold-to parties are different. Demo 3: Activate copying control 002 in copying control QT OR. Repeat demo 2. It is now possible to create the order with reference to the quotation.

April 2003

Page 29

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Talk about the significance of data transfer routines. Show, for example, that the purchase order data cannot be transferred in the order from the first demo (same sold-to party). In the next demo, show what the users have to do if they want to copy the purchase order data. The necessary coding is in the Z_LO650_CODE program and can be copied from there. Form routine 951 is needed in the exercises!

Demonstration <Approx. duration> Use form routine 051 to create routine 951, specifically for the customer. Menu path: (in IMG) Sales and Distribution System Modification Routines Define FORM Routines for Data Transfers Data transfer Orders 1. Overwrite the key entry 051 (general header data) with 951 and choose Enter. This copies the form routine. (if the system asks for a SAP development class, take e.g. VA0C) 2. Edit routine 951 and add the following coding at the end. (from Z_LO650_CODE) if tvak-vbtyp = charc. vbak-bname = cvbak-bname. vbak-telf1 = cvbak-telf1. endif. 3. Save and activate routine 951. 4. Activate 951. Note: CVBAK is the header of the reference document VBAK is the header of the target document TVAK-VBTYP = CHARC (i.e. C) means: target document is order 5. Activate form routine 951 in copying control QT OR (instead of 051). 6. Create a sales order for the quotation from the " Create with Reference" demo (with purchase order data). Use the same sold-to party! 7. Show that the purchase order data has been copied.
April 2003 Page 30

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Copying Control Item Level (1) In copying control, the controls for each item category are defined at item level for each "Target document type / Source document type". The details screen for an item category contains: Copying requirements Data transfer routines And the following important entries: Quantity/value pos/neg: Controls how the unreferenced quantity in the source document is affected by the copying action Copy quantity: Defines which quantity can be copied into the target document (e.g. Blank = best possible quantity = open order quantities for sales document type QT) Pricing type: Specifies how pricing data should be processed when copying Update document flow: Specifies whether the system updates the document flow when a document is copied

Copying Control Item Level (2) The rules for item category determination also apply to creating sales documents with reference. If an item category has been manually set in the source document, you must activate the "Default item category" field so that the correct item category is copied into the target document. Reference Status Update You can control when an item from the reference documents is complete: 1.) An item is complete as soon as it is referenced. In the above example, the inquiry is completely referenced even when only a partial quantity has been copied to the quotation. An item is only completed once the complete quantity has been copied into a subsequent document. In the above example, the quotation is only partially referenced which enables you to create several orders for an item until the quantity has been completely used up. You can choose these settings in Customizing for item categories. If an item is rejected, it is given "not referenced/completed" status.

April 2003

Page 31

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Present the "Sample quotation" scenario: The marketing department has requested a "sample quotation" for special promotions, which the individual sales offices can use as a template when they create quotations for certain customers. This will make the process for creating quotations more efficient. 1.) Copying QT to QT is not permitted in the system. 2.) Even if it were permitted, once you had copied it once, the sample quotation would be completed. (Quantity/value switch = +) The sales document type ZAG sample quotation has already been created in the training master system. You can study it and delete it before the course begins so that you can create it again in the demonstration (if necessary, make a security copy, for example, YQT), or you can just demonstrate it. Demonstration <Approx. duration> If you decided to delete ZAG, create it for the demo as follows (you should have practiced this before, otherwise use the existing ZAG and explain it). 1.) Create sales document type ZAG. Menu path: (IMG)

Sales and Distribution Sales Sales Documents Sales Document Header Define Sales Document Types
Select the table entry for document type QT Choose: Edit Copy as Overwrite QT with ZAG in the "Sales document type" field Choose Enter Answer the system inquiry "Is this entry also relevant for copying control?" with "No". Save your entries. 2.) Create new copying controls for source ZAG, target QT:
April 2003

Choose QT OR as a copying reference Replace target: OR with QT and source: QT with ZAG Set copying requirement 002 (header for different customer)
Page 32

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Copy all dependent entries Change the item categories at item level for copying control ZAG QT: Leave quantity/value pos./neg. blank If necessary replace the OR category in the item category field with the correct QT categories (for example, replace TANN with AGNN)

3.) Save your changes 4.) Create a one-time (conto pro diverse) customer for account group CPDA Name: CPD-SCM650 Note: Mention, that shipping condition, payment terms and incoterms will be entered when creating the sales document. 5.) Create a sample quotation for the one-time customer CPD-SCM650 Material 1400-300 (Sunfun) Promotion discount KA00 Payment terms: Incoterms: Shipping cond: 1 piece 25 % ZB01 EXW Hamburg 02 (Standard)

6.) Create a quotation for customer 2300 with reference to the sample quotation. Display pricing (25% KA00) Display the document flow (reference is still open!) 7.) Display the following information from the sample quotation: Overall status open Reference status not referenced Which means you can copy it as often as you like! Finally, show that you cannot create an order with reference to the sample quotation.

"Copying Control" Exercises 40 min

April 2003 Page 33

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

The participants activate the header copying rule 002 for their order type ZA## and do the exercises. Then they create their own sample quotation ZQ## as a copy of ZAG and do the exercises.

April 2003

Page 34

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Text Control
120 min

Topics Text types Texts in the SD process Configuration of text control Copy and reference texts Place the unit in context See scenario slide in the unit

Unit objectives By the conclusion of the unit, the participants should be able to: Identify the sources of texts in Sales and Distribution Describe the criteria which influence how texts are determined Define and assign text types in Customizing Edit texts manually in the sales document

Texts Texts are stored in various objects in documents in the SAP R/3 System, such as the customer master record, the material master record, the customer-material-info record and in all documents. The customer master record contains central texts, texts specific to Accounting and Sales and Distribution as well as texts for contact persons. You can define different text types for each of these areas. Example of text types specific to Sales and Distribution are: Marketing notes, notes on sales, shipping instructions The material master record contains a purchase order text and a sales text. Documents contain texts at header and item levels. You can enter texts in several different languages.

April 2003

Page 35

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Using Texts in Business Processes Texts can be stored in the master data and copied from the master data into sales and distribution documents. Texts can also be copied from a reference document into another sales and distribution document, for example, from a quotation into an order, or from an order into a delivery.

Text Control Overview (Sales Document) Text control is for creating texts automatically when you create a text object.

Demonstration <Approx. duration> 1.) Create a quotation for customer 2300 2.) Create some header text For example Please check our special offers" 3.) Enter item with 1 piece of material 1400-300 4.) Use the analysis to display the source of the text (material) 5.) Create an order with reference to the quotation 6.) Show that the header text has been copied 7.) Show the source of the item text (now preceding document!)

April 2003

Page 36

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Customizing for Text Control (1) to (5) Explain text control using these slides

Demonstration <Approx. duration> Menu path: (IMG)

Sales and Distribution Basic Functions Text Control

Show how texts are determined in Customizing, in the same way as depicted in the slides. Adding the quotation header text to the header text types: The customer service employee wants to be able to create a special quotation header text for quotations. For example "As long as stocks last. Offered subject to prior sale!"

Demonstration <Approx. duration> 1.) Create text type Y001 for sales document / header. 2.) Copy text control procedure Y1 from 01 (Clipboard) and include text type Y001. Use care in copying the contents of procedure 01! Sometimes the entire values do not get pasted into the new procedure. Correct manually if necessary. 3.) Create access sequence 9900. VBBK,Y001,all languages, requirement 1 4.) Assign text determination procedure to document types QT and OR. 5.) Test document flow for quotation order 6.) Show text determination analysis

April 2003

Page 37

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Adding "Additional label text" to the item text type: A special material label will be created in the R/3 System to improve sales processing in your company. This "additional label text" should help the customer (retailer) to identify goods that have been delivered and make it easier to assign the goods to his own (end) customers.

Demonstration <Approx. duration> Add item text "label text" (for example, for all customers that use item category TAN) 1. Create text type Z001 for sales document / item level. 2. Create access sequence 9800 for this text VBBP,Z001,all languages, requirement 50 3. Copy text determination procedure Z1 from 01 (Clipboard) and include Z001. 4. Assign text determination procedure to item category TAN. 5. Create additional label text in existing demo sales order: For example, Commission: Speed Control Corp.

April 2003

Page 38

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Using Texts as Reference Copying Texts Explain the differences between referencing and copying.

Demonstration <Approx. duration> 1.) Create a standard text: Text name: LO650 Text ID: SDVD Language: Course language "For up-to-date information, read the test report in the latest issue of Motorcycle Today" 2.) Change the sales order from the first demo. 3.) Go to the Texts tab for the first item. Double-click on the material sales text to create a new text. Enter a blank space and choose Details at the bottom of the screen. 4.) On the editor screen, include and expand the standard text module 5.) Display the sales document on the screen

Text Source Preceding Document for Billing Documents Problem: Only one document, either the sales order or the delivery note, can be the source for the text objects VBBK and VBBP. This is decided in the configuration of the Billing Type (flag Delivery text) NEW SLIDE: Customer Specific Data Transfer Routine for Texts Shows the routine that is eventually demonstrated, so you need not distribute additional hardcopies.

April 2003

Page 39

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

OPTIONAL Demonstration of Using a user exit for texts <Approximate Duration> A Data Transfer Routine for texts (no. 91) is available in the training system (coding see Appendix). IMG Sales and Distribution System modifications Routines Define Copying Requirements Data Transfer Texts With this routine you can read standard texts with a variable key composed like ZMAT:material number (for example. ZMAT:1400-300 in the case of Sunfun 1200ccm) With this routine we can (for example) extend the access sequence 23 Sales document item / Packing notes to read a material-specific Packaging note.

This is particularly interesting, because there is no standard configuration in text control for the material texts and customers appreciate it if you show them a way out.
1.) Make sure that routine 91 is active. 2.) Create a standard text. Tools SAPscript Standard Text Text name Text-ID Language ZMAT:1400-300 SDVD (Std. Text for SD Forms) Course Language

3.) Extend the access sequence 23 Sales document item / Packing notes by a new line: TEXT, SDVD, all Languages, UserExit 91 (in field DATA!) 4.) Create a sales order using material 1400-300. Show that the Packing note is filled with your standard text.

Exercises 40 min Text analysis, own header text determination procedure, referencing and copying texts

April 2003

Page 40

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Output
90 min

Topics Output types Transmission media Dispatch times Determining output Place the unit in context

Unit objectives At the conclusion of this unit, the participants will be able to: Describe the purpose of output types Set up various transmission media for issuing and printing output Change dispatch times to affect when output is issued Make the necessary Customizing entries to adjust output determination to meet the customers requirements

Output Types, Transmission Media, Communication Strategy, Timing of Output

Overview of Output Determination Present output determination using sales document type OR as an example

Output Determination Access Sequence Show how an access sequence is structured and create one as Z001 in the next demo

April 2003

Page 41

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Demonstration <Approx. duration> Show how output is determined using the sales document type OR as an example: 1. Procedure V10000 2. Output type BA00 3. Access sequence 0002 (order type) 4. Create your own access sequence Z001 Copy 0001 Add access 007 (sales order type) to level 30 Go to field level before saving, otherwise there might be problems when generating the sequence 5. Assign the new access sequence to output type BA00 6. Create a condition record for customer 2300 with the fax as medium. 7. Create an order and show the determination analysis 8. Maintain customer master 2300: fax number 1234567. 9. Repeat order.

Output Determination Analysis Important aid for Customizing output determination as well as for later.

Exercises 30 min Output condition records, determination analysis

April 2003

Page 42

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Processing Output
180 min

Topics Adjusting layout sets for output types Processing your own output types Place the unit in context

Unit objectives At the conclusion of this unit, participants will be able to: Explain how output types are processed in the R/3 System Judge how difficult it is to adjust existing layout sets to meet your requirements Name the steps needed for integrating customer-specific output types

The first part of this unit explains how to make simple changes to the layout of print output, which can be made by "non-programmers" using the ASAP Guide "Printout Design".

Procuring and Preparing Data In order to transmit output, the system needs to procure all the data from the database and prepare it for the transmission medium being used. Printing Data The system procures and prepares data in two separate steps to print out documents The printing controls are defined in the SAPscript for separately from the printing program The output is then transmitted to a printer or other device.

April 2003

Page 43

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Example: Output BA00 (Order Confirmation) This is the first time you mention communication structures. Explain that all fields that are available for output are represented in the applicable communication structures. New Fields for Printing Documents: Case 1 (Simple Case) Prepare the following demo: Incoterms (e.g. EXW) should be printed out with the corresponding description text (field VBDKA-INCO1_BEZ).

Demonstration (Part 1) <Approx. duration> 1. Copy form RVORDER01 from client 000 to ZRVORDER01 Tools SAPscript Form Utilities Copy from client (Development class, e.g. Z001) 2. Form ZRVORDER01 Change Page window MAIN Edit Text elements 3. Add the description to terms of delivery in the form. Set up (VBDKA-INCO1_BEZ) as follows: &'Terms of delivery 'VBDKA-INCO1& &VBDKA-INCO1_BEZ& &VBDKA-INCO2&,, 4. Activate the form 5. Assign form ZRVORDER01 to output type BA00 6. Issue the order confirmation (to screen) from the existing order.

Remind the class of the new text types that were created in the text determination unit: Y001 Quotation header text Z001 Additional label text (Item text)

April 2003

Page 44

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Demonstration (Part 2) <Approx. duration> 1. Form ZRVORDER01 Change Page window MAIN Edit Text elements 2. INCLUDE for text type Y001 in the form (at the end of text element HEADER TEXT) IF &VBDKA-VBTYP& = B INCLUDE &VBDKA-TDNAME& OBJECT VBBK ID Y001 PARAGRAPH HT ENDIF So that it looks as follows:
/E HEADER_TEXT /: INCLUDE 'SD_RVADOR01' OBJECT TEXT ID SDVD PARAGRAPH HT /: INCLUDE &VBDKA-TDNAME& OBJECT VBBK ID 0001 PARAGRAPH HT /: IF &VBDKA-VBTYP& = 'B' /: INCLUDE &VBDKA-TDNAME& OBJECT VBBK ID Y001 PARAGRAPH HT /: ENDIF

3. Activate the form 4. Assign form ZRVORDER01 to output type AN00. In the configuration of output type AN00, choose Processing routines. Change the Form field to ZRVORDER01. 5. Issue the quotation confirmation (to the screen) from an existing quotation with quotation header text

New Fields for Printing Documents: Case 2 (Complex case) No demo for this part. Refer to the IMG path for the procedure Sales and Distribution System Modification Create new fields (using the condition technique) New fields for output control Discussed later in the "System Modifications" unit.

April 2003

Page 45

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

The second part of this unit demonstrates the steps necessary needed to integrate new output types with new processing programs and forms in the R/3 System. This is obviously too complex for "lay" users. If the customers wish to undertake these changes in their company, they will need trained ABAP/4 and SAPscript programmers. Integrating a New Output Type Prepare for the following demo using ZMAT: New output types are normally based on existing document types. This means that if you need to create any document data, you can copy most of it from an existing communication structure. The real work starts when writing the processing program and its form definitions. This is where you need an ABAP/4 programmer and someone familiar with SAPscript.

Example: Customer's Material Label ZMAT A processing program has to be written for procuring the transmission data and controlling the form output. This program should be given a name from the customer's name range (for example ZZLO650) and be based on the specified communication structures VBDKL (document header view for delivery note) and VBDPL (document item view for delivery note). The processing program, together with the relevant SAPscript form in which the required layout was programmed (name, for example ZZ_MAT_LABEL) is assigned to output type ZMAT in Customizing. You must add output type ZMAT to the output determination procedure for deliveries so that the system includes it during output determination.

April 2003

Page 46

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Demonstration: Customer's Material Label ZMAT <Approx. duration> Starting point: simple material label Link it to item text "additional label text" Use "Output Determination Overview" slide from previous unit. Include a new output:

The first three steps have already been executed in the training master system 4.6 to make it easier for the instructor!
1.) Output type ZMAT (delivery item): IMG Logistics Execution Shipping Basic Shipping Functions Output Control Output Determination Maintain Output Determination for Outbound Deliveries Maintain output types Copy from LQCA Access sequence 3 SLSORG/customer(2 levels) 2.) Assign output to partner function (ZMAT,1,SH) 3.) Assign processing program ZZLO650 and form ZZ_MAT_LABEL to ZMAT, with FORM routine ENTRY (available in training system!) Assign forms and programs Assign to shipping documents 4.) Include output in procedure V20001 (Level 10, counter 1, ZMAT) 5.) Output Control Define Print Parameters Shipping Shipping point Output device Suffix 1 Suffix 2 1000 LP01 ZMAT MAT-LABEL 6.) Create output condition record for ZMAT (Sales org. 1000, customer 2300, dispatch time 3) Otherwise, dispatch time 1 with RSNAST00! Transfer the text type from the order to the delivery: 1.) Include output Z001 in text determination procedure 02 for the delivery item Create and use access sequence 9700 (VBBP,Z001,x, req. 50)

Exercises 30 min Display output, understand how to process your own output types.

April 2003

Page 47

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

System Modifications
150 min

Topics Basic system modifications in Sales and Distribution Elements of system modifications Enhancing SAP transactions Place unit in context

Unit objectives At the conclusion of this unit, the participants will be able to: Describe the options for making release-insensitive modifications to the system in Customizing for Sales and Distribution Explain the idea behind the SAP enhancement concept

System Modification Overview Explain the difference between customer enhancements and customer modifications. Customer enhancements use interfaces defined by SAP and are normally releaseinsensitive - MORE SECURITY! Customer modifications that don't use this concept can mean a high maintenance workload when the release is upgraded. Elements of System Enhancement Introduce the individual elements within system modifications for Sales and Distribution. Demonstration <Approx. duration> 1.) Show the participants the Sales and Distribution/System Modification path in Customizing. 2.) Expand some of the subnodes to show how much there is. 3.) Go to an example in the online documentation.
April 2003 Page 48

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Adding New Fields with Condition Technique The technique is used by pricing, output control, account determination, listing, exclusion and substitution to determine prices or output, for example. In each component, all the permitted fields for accessing condition records are combines in their own communication structure. Communication structures contain all the data fields that can be used to access a condition table. You can only evaluate fields that are contained in the relevant communication structure for the access sequences within the different applications of the condition technique. INCLUDES are linked to all the relevant communication structures, and new data fields are added to these. The system does not overwrite them when you upgrade your release. Demonstration <Approx. duration> Use pricing as an example: Reserve field ZZKVGR1 (customer group 1) has already been added to table KOMKAZ in the training master system for the pricing course. According to the procedure checklist in Customizing, this can be included in the catalog of permitted fields. Adding New Fields Without Condition Technique Briefly discuss some of the examples that use this technique.

April 2003

Page 49

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Reserve Fields in Customer and Material Master Explain the purpose of reserve fields Show how the fields are already integrated in the document chain, which means that adapting the fields for the customer problem saves you a lot of work compared to including new fields. Discuss ways for changing the short text for a data element.

Demonstration <Approx. duration> 1.) We enter a short text for data element KVGR1 as "BILLING VARIANT" Menu path: Tools ABAB/4 Workbench Utilities Enhancements Project management Goto Text enhancements Keywords Change Enter KVGR1 Enter and save texts Message: Activated asynchronously 2.) In the relevant checking table TVV1 (view V_TVV1), maintain the value list. You can find the table name in the documentation for the IMG activity: Sales and Distribution System Modification Create new fields (without condition technique) Reserve fields in the customer master record) Transaction SM31 / View maintenance for view V_TVV1: Blank = STANDARD 001 = SPECIAL 3.) Assign the attribute 001 SPECIAL (= for example combination or new pricing) to customer 2, group 20 (search term: 20LO150-2) Change customer Sales area data

Extras Additional data

4.) Create an order with customer T-S50B20 and two items (1400-100 and 1400-200) and show that the field is activated in the additional data for the order header.

April 2003

Page 50

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Routines Routines are short subprograms that perform different functions during document processing. In SD, you can use transaction VOFM for creating and processing routines for copying requirements, data transfers, requirements and formulae. Demonstration <Approx. duration> 1. Go to copying control for "Delivery to billing document" 2. Display copying control routine 004 at item level (source text) All the data required can be accessed here. 3. Use the SHOW command to display structure VBAK and check that the VBAKKVGR1 field is available. (SHOW command may not be available.) 4. NEW demo with Release 4.6: Go to transaction VOFM and show copy requirement 904 (already part of the training master system 4.6). This routine (see Appendix) has the advantage of being 100 % releaseinsensitive, because we call the original routine 004 at the end of the routine. If SAP changes the routine 004, we will inherit the changes too! 5. Change the Copying Control: Delivery to Billing for: Target F2, source LF and Target ZF20, source LF by replacing the copying requirement 004 with 904 for all item categories. 6. Show that the demo order for customer T-S50B20 (group 20) can no longer be billed with F2. 7. Enter billing type ZF20 in the default data and it works! The copying requirement can be changed easily for all item categories at the same time by: Select all Edit change field contents Copying requirements

April 2003

Page 51

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

User Exits User exits are locations in the SAP transaction, where the customer can enter the transaction and implement their own additional programming logic for a certain installation. They can be used, for example, to process new fields. User exits require a certain discipline because the interface is not as clearly defined as in function modules.

Demonstration <Approx. duration> Add field TKOMK-ZZKVGR1 to the MV45AFZZ program in the PRICING_PREPARE_TKOMK user exit, thereby complementing the additional field in Pricing. To demonstrate this fully, you must create all relevant pricing configuration and master data to use the new field ZZKVGR1 in the field catalog. Treat this as an optional demonstration based on the interest of the participants. Extending SAP Transactions The enhancement concept means customer modifications rarely need to be adjusted when the release is upgraded. In contrast to customer modifications, there are specific SAP interfaces for customer enhancements. The customer can write coding in a level that is separate to those provided by SAP and adjust the processes to suit their requirements to a certain extent.

April 2003

Page 52

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Example: Function Module Exit SDVFX004 Start the demonstration of transaction CMOD. Demonstration <Approx. duration> 1. Define the enhancement project Menu path: Tools ABAB/4 Workbench Utilities Enhancements Project management Enter project name DEMO650 Create project 2. Choose: SAP enhancements / Change 3. Search for all SAP enhancements without entering any selection criteria and page down the list so that the customers get an impression of the enhancements that exist. 4. Now restrict the search to SD*. 5. Choose function exit SDVFX004 6. Display enhancement component: EXIT_SAPLV60B_004 7. Edit source text for function module EXIT_SAPLV60B_004 Include ZXVVFU04 8. Add the move command XACCIT-SGTXT = XVBRP-MATNR to the ZXVVFU04 include. 9. Activate the project 10. To be safe, display the function module and choose: Function module Activate 11. Bill the delivery 12. Display the accounting document Item details (Domestic sales revenue). You can see the material number.

April 2003

Page 53

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Business Transaction Events (BTE)

The BTE technique was introduced in SD in Release 4.5. For this reason we have only a few enhancements in SD with this technique.

Demonstration of Business Transaction Events (BTE) < Approx. duration >. Step 1: Show existing interfaces. Menu path: IMG Sales and Distribution System modifications Use Business Transactions Environment Info system (P/S) Field Component: enter SD and choose Execute Existing P/S-interfaces will be displayed. Choose Documentation. IMG Sales and Distribution System modifications Use Business Transactions Environment Info system (Processes) Field Component: enter SD and choose Execute Existing P/S-interfaces will be displayed. Choose Documentation. OPTIONAL!! Step 2: Activate BTE-interface (P/S) 00503306 Maintain conditions: Text determination. IMG Sales and Distribution System modifications Use Business Transactions Settings Products ...of a customer Choose: New Entries Product: Text Save LO650 Demo BTE LO650

Settings P/S function modules ...of a customer

Choose: New Entries
April 2003 Page 54

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Event: Product:

00503306 LO650

Function module : ZZLo650_Interface_00503306

Settings Products ...of a customer

Set product active indicator for product LO650 and save. TEST: Display the condition record for condition type PR00 and material 1400-300. In the field text you will see BRUUUUUMMMMMM.

Preview of Business Add-Inns Only for complete information. In the future the new interfaces will be realized with ABAP-Objects.

Exercises 50 min Configure the "billing variant" and test it. Get to know the enhancement concept.

April 2003

Page 55

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Lists
60 min

Topics Document lists in Sales and Distribution Document analysis ABAP List Viewer Place unit in context See scenario in unit

Lists and List Viewer This is the simplest topic: Discuss slides The list viewer has replaced the old lists.

NEW SLIDE: New Fields For Lists Of Sales And Distribution Documents Shows the use of the respective user-exit in this area. Demonstration <Approx. duration> Use the list of orders to show the functions needed by the participants for the exercises (see exercises). OPTIONAL Demonstration New Fields For Lists Of Sales And Distribution Documents <Approx. duration> IMG Sales and Distribution System modifications Create New Fields (Without Condition Technique) New Fields For Lists Of Sales And Distribution Documents Choose: Further display fields for lists in sales documents
April 2003 Page 56

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

1. Choose: Structural enhancement Enter in field component: ZZKVGR1 Enter in field component type: KVGR1 and activate the structure. 2. Choose: Include member V05TZZMO Enhance the header moves:
* * WHEN 'VBAK'. header MOVE LVBAK-XXXXX TO LVBMTV-ZZXXXXX. MOVE LVBAK-kvgr1 TO LVBMTV-ZZkvgr1.

and activate the include. 3. Choose: Allowed fields Choose: New Entries Enter in field field: ZZKVGR1 Enter in field Acc.(access type): D Save your entries. 4.Go in the list of sales orders (VA05) Field Customer Group 1 is now available in the column set and can be selected for display. 5. If it does not work immediately, enter /SYNC in the command-field to clear the buffers.

Exercises (can also postponed to the end of the course) 20 min

April 2003

Page 57

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Interface Modifications
60 min

Topics Account groups Customer master field selection Table control Transaction variants Place the unit in context

Unit objectives At the conclusion of the unit, the participants will be able to: Define account groups for maintaining customer master records Name the most important factors that influence the field selection for maintaining customer data Adjust screens with the display element "table control" to meet your requirements Create and use transaction variants

Customer Master The participants should already be aware of the structure of the customer master and know that the fields are divided up between views. Customer Master Account Groups Introduce the account group as a main controlling element. Give an overview of ways of controlling. In this unit, we are mainly concerned with the field selection. Important: The account group should not be used as an evaluation criterion. This is what the criteria in the master record are for.

April 2003

Page 58

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Customer Master - Selecting Fields for Data Groups From this slide on, you introduce the criteria that play a role in field selection. Each field in each account group can be changed so that the user can enter or must enter data. The fields are then combined in groups. Customer Master - Selecting Fields for Account Groups Account groups have been defined for each partner function with the relevant screens in the standard system. When the user creates a new customer, the system proposes account group 0001.

Customer Master - Additional Influences on Field Selection The account group and the maintenance transactions that are available for the user reduce the maximum of fields that can be displayed in the view. Customer Master - Linking Rules in Field Selection Example: If a field has been activated as "hidden" in the controlling options, the field will always be hidden regardless of the other control criteria. Therefore, if the field for terms of payment should be hidden for a certain account group, it cannot be reactivated by the transaction. Note: It is possible to change the account group for a customer master record later. This is particularly useful for changing a sales prospect into a sold-to party but with the same customer number. This kind of subsequent change is only possible if the field selection for the new account group does not hide any fields that were available in the old account group.

April 2003

Page 59

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Demonstration Approx. 30 min 1.) Display customer master with various partners Menu path: Logistics Sales and distribution Master data Business partner Note: Various partners that can be distinguished both by their master data types (such as customer, personnel master data) as well as by the different account groups in the customer area (sold-to party, ship-to party, etc.)

Business partners Customer Change Sales and Distribution

Refer to the different maintenance transactions Customer 1670 (CompSmart) Sales area: 1000 12 00 Refer to different tabs and data groups. Delete the Country field Enter (error message!) Enter country again Enter Display Sales area data. 2.) Show Customizing for the customer master and carry out any changes IMG Logistics - General Business Partner Customers Control Define Account Groups and Field Selection for Customers Select Account group 0001 Copy as.. button Enter Account group Z00, description Account group LO650-Ref and choose Enter. Select Z00 and choose the Details button Point out the one-time acct indicator. Explain field status Sales field group Choose Sales data and Expand field status button Subgroup list button = Lists all the fields in the

Point out the Default product proposal entry Back Sales field Details button 1. Change Default product proposal from an optional entry to a suppressed (hidden) entry. 2. Change Customer group from an optional entry to a required entry.
April 2003 Page 60

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Optional: To display the documentation for a field, choose Field check and then display the documentation for the Product proposal field by choosing F2. Go back. Save

Display the other settings in detail but don't change them. 3.) In order to maintain and use the master data record, partners need to be assigned to account groups. IMG Sales and Distribution Basic Functions Partner Determination Set Up Partner Determination Set Up Partner Determination for Customer Master Choose: Account Groups - Function Assignment in the dialog structure Assign partner functions SP, SH, PY and BP to account group Z00. Save 4.) Create a customer record. Logistics Sales and distribution Master data Business partner Customer Create Sales and Distribution Account group Account group LO650-Ref Sales area 1000 12 00 Use the reference to customer 2300

Don't try to enter a customer number but let the system propose one: Error Enter customer number Enter customer number Save 910001 10001 Error (number range!)

April 2003

Page 61

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Table Control

Demonstration <Approx. duration> Create demo to match the exercises.

Transaction Variants / Screen Variants / GuiXT

Demonstration <Approx. duration> 1.) Create transaction variant. IMG General Settings Field display characteristics Configure Application Transaction Fields Enter Transaction Code: VA01, Transaction Variant: ZPHONE In the first screen: Copy field values, do not display screen. Save using development class Z001 (if necessary several screens). 2.) Create variant transaction IMG General Settings Field display characteristics Configure Application Transaction Fields Enter Transaction Code: VA01, Transaction Variant: ZPHONE Choose: Goto Create Variant transaction Enter transaction code: ZVA01 Save 3.) Add the new transaction ZVA01 to your favorites. Favorites Insert Transaction NEW SLIDE: Calling Transaction Variants for VA01 Transaktion VA01 is a special case!

April 2003

Page 62

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Exercises 30 min

April 2003

Page 63

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Unit: Conclusion

15 mins

Summarize briefly the most important parts of the course. Review the objectives and provide brief examples of how those objectives have been met. Review the Process flow chart to remind students of all the different things they have learned during the course.

Demonstration: SD Curriculum in the Internet.

Go to the Internet
Internet address www.sap.com Choose Education Choose Education Home Choose your local country Display the Curriculum: the following steps will be different depending on the country you have chosen: as an example for the USA it would be: Choose USA Choose SAP R/3 courses Choose Logistics Customer Order Management Discuss the follow up activities suggested for the students. Course participants leave after completing a course evaluation.

April 2003

Page 64

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Appendix
Coding of the Copying Requirement 904 for invoice items (part of the training master system).
FORM BEDINGUNG_PRUEFEN_904. *==============================

* MODIFICATION "Billing variant" sy-subrc = 0. CHECK : ANALYZE_MODE IS INITIAL. CASE tvfk-fkart. when 'F2'. IF VBAK-KVGR1 = '001'. PERFORM VBFS_HINZUFUEGEN USING LIPS-POSNR '012' 'Lo650' SPACE SPACE. SY-SUBRC = 4. EXIT. ENDIF. when others. IF VBAK-KVGR1 NE '001'. PERFORM VBFS_HINZUFUEGEN USING LIPS-POSNR '012' 'Lo650' SPACE SPACE. SY-SUBRC = 4. EXIT. ENDIF. endcase. *============================== Perform bedingung_pruefen_004. * ENDFORM.

April 2003

Page 65

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Coding of the Data Transfer Routine 91 for texts (part of the training master system) *---------------------------------------------------------------------* * FORM DATEN_KOPIEREN_91 *---------------------------------------------------------------------* * Use material-no. FTVCOM-MATRN to read a specific standard text. * * This is an example for course Lo650 form daten_kopieren_91 . referenz-tdid referenz-tdname = 'SDVD'. '. = 'ZMAT:'. 14.10.1999 WH *---------------------------------------------------------------------*

referenz-tdobject = 'TEXT

referenz-tdname+5 = FTVCOM-MATNR. endform.

April 2003

Page 66

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Contents of the Report Z_LO650_CODE (part of the training master system).

REPORT Z_LO650_CODE . " Release 4.6

THIS PARTS OF CODE ARE MEANT TO HELP THE LO650-INSTRUCTOR !! ************************************************************************ UNIT "Copying Control" - Coding for Data-Transfer-Routine 951 1.) COPY 051 -> 951 2.) INSERT AT THE END (IMMEDIATELY BEFORE STATEMENT ENDFORM) IF TVAK-VBTYP = CHARC. " only for orders VBAK-BNAME = CVBAK-BNAME. VBAK-TELF1 = CVBAK-TELF1. ENDIF. ************************************************************************ UNIT "Processing Output" - layout-set ZRVORDER01 &'Lieferbedingungen 'VBDKA-INCO1& &VBDKA-INCO1_BEZ& &VBDKA-INCO2&,, IF &VBDKA-VBTYP& = 'B' INCLUDE &VBDKA-TDNAME& OBJECT VBBK ID Y001 PARAGRAPH HT ENDIF ************************************************************************ UNIT "System Modification" Routine 904 is already installed in the training master system! You must only activate it! *======================================================== =============== CODING FOR INCLUDE ZXVVFU04: ****INCLUDE ZXVVFU04 . XACCIT-SGTXT = 'Material:'. XACCIT-SGTXT+10 = XVBRP-MATNR.

April 2003

Page 67

SAP AG

SCM650 Cross-Functional Customizing in SD Appendix

Coding of the Function Module ZZLO650_INTERFACE_00503306 (part of the training master system)
FUNCTION ZZLO650_INTERFACE_00503306. *"-----------------------------------------------------------*"*"Lokale Schnittstelle: *" IMPORTING *" VALUE(FIELDNAME) TYPE CHAR30 *" VALUE(VALUE) *" VALUE(KOMG_I) TYPE KOMG *" VALUE(KONP_I) TYPE KONP *" VALUE(T681E_I) TYPE T681E *" EXPORTING *" VALUE(TEXTSTRING) TYPE CHAR40 *" CHANGING *" REFERENCE(GET_TEXT) TYPE CHAR1 *"-----------------------------------------------------------IF KONP_I-KSCHL eq 'PR00' AND KOMG_I-VKORG eq '1000'. IF FIELDNAME eq 'MATNR' and VALUE eq '1400-300'. TEXTSTRING = 'BRUUUUUUMMMM'. CLEAR GET_TEXT. ENDIF. ENDIF. ENDFUNCTION.

April 2003

Page 68