You are on page 1of 22

V2.

470 July 2004 English

Livestock (G86)

Procurement

Building Block Configuration Guide

SAP AG Neurottstr. 16 69190 Walldorf Germany

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Copyright
Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein 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, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C 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. MaxDB is a trademark of MySQL AB, Sweden. 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 informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP AG

Page 2 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Icons
Icon Meaning Caution Example Note or Tip Recommendation Syntax

Typographic Conventions
Type Style 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.

Example text EXAMPLE TEXT

Example text

EXAMPLE TEXT

Example text <Example text>

SAP AG

Page 3 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Contents
Configuration Guide ......................................................................................................................... 5 1 Purpose .................................................................................................................................... 5 2 Preparation ............................................................................................................................... 5 2.1 Prerequisites .................................................................................................................. 5 3 Basic Settings ........................................................................................................................... 5 3.1 Creating Data Prerequisites ........................................................................................... 5 3.1.1 Creating Data Elements ............................................................................................. 5 3.1.2 Creating Append Structure ZAKOMPAZ ................................................................... 6 3.1.3 Adding Append Structure to KOMP and KOMG ........................................................ 7 3.2 Implementing Program Enhancements .......................................................................... 8 3.2.1 Creating the Include Source ZXM06U15 ................................................................... 8 3.2.2 Adding the User Exit to EXIT_SAPLMEKO_002 ....................................................... 9 3.2.3 Enhancing Include MM06EFKO_KOND_KOMP_FUELLEN ................................... 10 3.3 Project Management of SAP Enhancements............................................................... 11 4 Configuration .......................................................................................................................... 12 4.1 MM Cross Client Customizing ...................................................................................... 12 4.1.1 Extending Field Catalogs for Condition Tables ....................................................... 12 The fields have to exist in table KOMG, KOMK, or KOMP. ................................................... 12 4.1.2 Maintaining Condition Tables .................................................................................. 13 4.1.3 Defining Access Sequences .................................................................................... 13 4.2 Maintaining Client-Specific Customizing for MM.......................................................... 14 4.2.1 Defining Condition Types ......................................................................................... 14 4.2.2 Defining Calculation Schemas ................................................................................. 15 4.2.3 Defining Schema Groups ......................................................................................... 16 4.2.4 Defining Schema Determination .............................................................................. 16 5 Master Data ............................................................................................................................ 17 5.1.1 Creating Vendor C8600 ........................................................................................... 17 5.1.2 Creating Output Condition Record ERS .................................................................. 17 5.1.3 Creating ROH Materials C47000, C47010, C47020 ................................................ 18 5.1.4 Creating Stock Material Info Record C8600/C47000 .............................................. 18 5.1.5 Creating Condition Records for Condition Type YGB0 ........................................... 19 5.1.6 Creating Condition Records for PB00 (Gross Price) ............................................... 21

SAP AG

Page 4 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Configuration Guide 1 Purpose


This configuration guide provides the information you need to set up the configuration of this building block manually. If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the installation guide of this building block.

2 Preparation
2.1 Prerequisites
If you want to use this building block, you must first install the following building blocks: Building Block # J06 J07 G75 G89 Description Product Planning and Control Quality Management Batch Management Delta CO-PC for Meat

3 Basic Settings
3.1 Creating Data Prerequisites
Use
For offering a price determination referring to batch characteristics, it is essential to enhance the underlying data definitions and structures. You have to execute the following steps to enhance the data definitions and structures suitable for the needs of the purchase price update. This refers to the batch characteristics that are specified as a result of the quality inspection.

3.1.1 Creating Data Elements Use


The user exit provided with SAP Best Practices for FMCG requires suitable data elements to enable a pricing determination based on the batch characteristics of the livestock. Currently the user exit requires that the exact data elements listed below are used to determine the price. In the future, SAP Best Practices for FMCG hopes to make the user exit more flexible so that other characteristics can be used to determine the price after goods receipt of the livestock.

Procedure
1. Access the activity using the following navigation options: Transaction Code SE11

SAP AG

Page 5 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide Tools ABAP Workbench Development ABAP dictionary

IMG Menu

2. Choose DATA TYPE and enter the data element names below in the following order (in the entry field behind the radio button). Choose Create. Data element YG_W YG_P YG_F Data type NUMC NUMC NUMC Length 4 4 4 Short Description % -Water % -Protein % -Fat

3. Choose DATA ELEMENT in the screen that appears. 4. On the DATA TYPE tab page, enter the short description shown in the table above and choose BUILT-IN TYPE. Insert the value NUMC in the field DATA TYPE and the value 4 in the field LENGTH. 5. On the FIELD LABEL tab page, fill in the short description from the table above in all four field labels. 6. Save and activate the structure KOMP by choosing Activate (Ctrl+F3). 7. Please assign individual package, e.g. Z001.

Result
The 3 data elements as a data based condition for executing the price determination referring are created.

3.1.2 Creating Append Structure ZAKOMPAZ Use


To combine the required data elements for the price determination referred to in the batch characteristics, you need to enhance the structure KOMPAZ Pricing communication item: Customer modifications with a suitable append structure.

If the modification assistant is switched on, you have to create the append for the standard structure KOMPAZ via the SE11 menu as described in section 4.1.3 below.

Procedure
1. Access the activity using one of the following navigation options:

If the name ZAKOMPAZ is already used in the customer system, choose another name beginning with a Z as the first character. Transaction Code IMG Menu SE11 Tools ABAP Workbench Development ABAP dictionary

2. Insert the name ZAKOMPAZ of the data structure you want to create after the field DATA TYPE. 3. Choose Create.

SAP AG

Page 6 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

4. Choose STRUCTURE and enter the short description Price determintion referred to the batch characteristics the data element names below in the follow order (in the entry field behind the radio button). Choose Activate. Append Structure ZAKOMPAZ Component Component type YG_W YG_P YG_F YG_OK YG_W YG_P YG_F KBSTAT Data type NUMC NUMC NUMC CHAR Length Short Description 4 4 4 2 % -Water % -Protein % -Fat Processing status for conditions

5. The structure with name ZAKOMPAZ is to be created including the four fields below. 6. Activate the append structure ZAKOMPAZ Price determination referred to the batch characteristics. 7. Assign an individual package, e.g. Z001.

Result
The three data elements for the price determination by batch characteristics are now created in the customer target system.

3.1.3 Adding Append Structure to KOMP and KOMG Use


To make the structure ZAKOMPAZ available for the purchase pricing dialog programs, you have to add it to two SAP R/3 price-relevant structures: KOMP Pricing communication item KOMG Allowed fields for condition structures

If the modification assistant is switched on, you have to create the append for the standard structure KOMPAZ via the SE11 menu.

Procedure
1. Access the activity using one of the following navigation options:

Transaction Code IMG Menu

SE11 Tools ABAP Workbench Development ABAP dictionary

2. Choose Data Type and enter the name KOMP in the entry field behind it. 3. Choose Change. 4. When the system asks you in which language the structure should be changed, choose the language EN (English). 5. Find the include KOMPAZ (column: Component type) in the table field structure of KOMP.

SAP AG

Page 7 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

6. 7. 8. 9. 10.

11.

12.

For finding the include KOMPAZ, use Find (Crtl+F). Choose the component type KOMPAZ. A screen with the KOMPAZ (Pricing communication item: Customer modifications) dictionary structure opens and choose. Activate the change mode (CTRL+F1). Choose Append Structure (F5). A subscreen named Choose append for table KOMPAZ arises. Choose none of the append structures shown in the subscreen. Instead, choose New Append Structure (F6). If an information message appears on your screen, choose Continue (Enter). Another append screen appears in which you have to insert the name of the new append structure. Type in ZAKOMPAZ. (If the name ZAKOMPAZ is already used in the target customer system choose a different one (example: ZBKOMPAZ). In the next step the specification of the append structure fields is needed. In the empty rows on your screen fill in the columns COMPONENT and COMPONENT TYPE the values from the table below.

Append ZAKOMPAZ Component Component type YG_W YG_P YG_F YG_OK YG_W YG_P YG_F KBSTAT Data type NUMC NUMC NUMC CHAR Length Short Description 4 4 4 2 % -Water % -Protein % -Fat Processing status for conditions

13. Save and activate the KOMP structure by choosing Activate (Ctrl+F3). 14. Assign an individual package, such as Z001. 15. The corresponding KOMG structure will be generated automatically in the background.

Result
The three data elements are combined in the data structure ZAKOMPAZ.

3.2 Implementing Program Enhancements


Use
For offering a price determination referring to batch characteristics, it is essential to implement two program enhancements. The purpose of this activity is to enable the price determination (for Condition Type YGB0) for purchase order items after the specification of the batch characteristics at the end of the quality inspection.

3.2.1 Creating the Include Source ZXM06U15 Use


In a first step the user exit program for price determination referring batch characteristics has to be generated. The source code for the user exit is delivered in a text file.

SAP AG

Page 8 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SE38 Tools ABAP Workbench Development ABAP editor

2. In the Program field, enter ZXM06U15 and choose Create. If now the warning message no. DS027 Program names ZX... are reserved for includes of exit function groups arises at your screen pr ess ENTER. 3. Enter the following ABAP program attributes: TITLE = Include ZXM06U15, TYPE = I INCLUDE program 4. In the ABAP editor that appears, navigate along the following path: Utilities More Utilities Upload/Download Upload 5. In the dialog editor that appears, insert the content of the following text file:

The implementation of ZXM06U15.txtmust be done manually. Use the .txt files ZXM06U15.txt located on the documentation CD in the MISC folder. 6. Activate the user exit ZXM06U15 (Ctrl+F3).

If you are working on a Unicode system, after this step a syntax error message might appear at the bottom of your screen. In this case, position the cursor in the row of the program source written in the error message and search for a in that row. Reset the to the character which is used in the text file for this digit. 7. Assign an individual package, e.g. Z001.

Result
After performing this activity, the user exit ZXM06U15 is active in your system.

3.2.2 Adding the User Exit to EXIT_SAPLMEKO_002 Use


For performing the user exit created in the step above it has to be incuded and activated in the user exit EXIT_SAPLMEKO_002.

Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SE37 Tools ABAP Workbench Development Function builder

2. In the Module field function, enter EXIT_SAPLMEKO_002 and choose Change (with language English).

A dialog box appears, asking for a developer key and object key. If you do not have one or both, you will need to obtain them in SAP Service Marketplace. 3. Activate the user exit EXIT_SAPLMEKO_002 (Ctrl+F3).

SAP AG

Page 9 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Result
After performing this activity, the user exit ZXM06U15 is correctly placed in the main program.

3.2.3 Enhancing Include MM06EFKO_KOND_KOMP_FUELLEN Use


The next step of the basic settings for this installation guide is to check that the user exit was correctly installed.. Therefore the include MM06EFKO_KOND_KOMP_FUELLEN from standard program SAPLMEPO has to be enhanced.

Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SE38 Tools ABAP Workbench Development ABAP editor

2. In the Program field, enter MM06EFKO_KOND_KOMP_FUELLEN and choose Change.

A dialog box appears, asking for a developer key and object key. If you do not have one or both, you will need to obtain them in SAP Service Marketplace. 3. Insert the following coding into the include MM06EFKO_KOND_KOMP_FUELLEN: a) After the comment/command lines 57 * weitere Einschrnkungen in belegbearbeitung setzen and 58 komp-kaend_typ = '.....'.. insert the following source commands 59 60 61 62 63 *+++ KAISER 23.04.2004 START perform user-exit_smb26_G86. * *+++ KAISER 23.04.2004 END

b) After the command line 74 ENDFORM. "KOND_KOMP_FUELLEN insert the following source comments/commands 76 77 *+++ KAISER 27.04.2004 78 * necessary for price determination by batch characteristics 79 *+++ the user exit ZXM06U15 moves an 'OK' to the field komp-yg_ok 80 *+++ if several terms are fulfilled: 81 *+++ 1. goods receipt is completed 82 *+++ 2. the inspection batch was accepted after the qualtity check etc. ... 83 *+++ the price update will be opened for making the price determination 84 *+++ by the batch characteristics wich are specidfied in the quality 85 *+++ inspection.

SAP AG

Page 10 of 22

SAP Best Practices 86 87 88 89 90 91

Livestock Procurement (G86): Configuration Guide form user-exit_smb26_G86. if komp-yg_ok = 'OK'. move space to WERE-WE. endif. endform. *

4. Choose Save and Activate.

3.3 Project Management of SAP Enhancements


Use
To make the user exit active in your system, you have to create a development project and assign the enhancement to it.

Note that the user exit already exists. The intension of this step is to activate it for making it run in your system.

Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu CMOD Tools ABAP Workbench Utilities enhancements CMOD

2. Type in a project name, such as Z001, and choose Create. Make sure that the Radio-Button "Attributes" is set. 3. Enter a short text and choose Enhancement Assignments. 4. Save the short text and 5. Create the object directory Entry as LOCAL OBJECT 6. Enter the enhancement name LMEKO002. 7. Save the enhancement. 8. Activate the enhancement project (e. g. Z001).

Result
You have completed your program enhancements. CAUTION: If you do not execute this step, the main purchase order program will not notice the user exit ZXM06U15.

SAP AG

Page 11 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

4 Configuration
4.1 MM Cross Client Customizing
4.1.1 Extending Field Catalogs for Condition Tables Use
In this step, you can extend the field catalog for condition tables to include fields that are not available for the purpose in the standard system. In this scenario it is used for the creation of conditions for fat, protein and water.

Prerequisites
The following development steps have to be realized before starting with the field catalog extension: Create data elements Create Append Structure ZAKOMPAZ Add Append Structure to KOMP and KOMG

The fields have to exist in table KOMG, KOMK, or KOMP.

Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SPRO IMG Materials Management Purchasing Conditions Define Price Determination Process Extend Field Catalog for Condition Tables

2. In the Table entry field, enter the three-digit number 901 (in the customer name space). Choose Enter. 3. In the Field Overview screen that appears, select the following four fields for the new condition table:

The sequence of the attributes below is obligatory! 4. Make new entries in Change View Field Catalog (Pricing Purchasing): Overview screen Field name Entry 1 Entry 2 Entry 3 Field YG_F YG_P YG_W Description %-Fat Percentage Protein Percentage Water

5. Choose Generate (Shift + F4) to create the condition table. 6. In the upcoming subscreen Create the object directory Entry fill in the PACKAGE Z001 and save as LOCAL OBJECT

SAP AG

Page 12 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Result
The condition table has been created.

4.1.2 Maintaining Condition Tables Use


In this step, you define the price dependencies. You can make prices, discounts and surcharges dependent on almost all the fields in a purchasing document. You define these dependencies with the aid of condition tables. In a condition table, you specify the combination of fields for which you can create condition records.

Prerequisites Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu Alternative Transaction Code SPRO IMG Materials Management Conditions Define Price Determination Process Maintain Condition Table M/03

2. In the Create condition table (Pricing Purchasing): Field Overview screen enter Table 901 Material/Protein %/Water in %/Fat Cont %. 3. In View Create Condition Table (Pricing Purchasing): Field Overview screen: Choose the entries in the field catalog in the right column to add them to the left column. a. Material b. Protein Content in % c. Water Content in % d. Fat Content in % 4. Save.

4.1.3 Defining Access Sequences Use


In this step you define access sequences. An access sequence is a search strategy with the aid of which the System searches for valid condition records of a certain condition type. For example, you can stipulate for a price that the system first searches for a price for a specific plant, and then for a generally applicable price. For condition types for which you wish to maintain conditions with their own validity period, you must assign an access sequence. With this, you define which fields the system checks in searching for a valid condition record.

Procedure
1. Access the activity using one of the following navigation options: Transaction Code SPRO

SAP AG

Page 13 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide IMG Materials Management Purchasing Conditions Define Price Determination Process Define Access Sequence

IMG Menu

2. On the screen Change View Access Sequences: Overview create a new entry for access sequence YG01: Field 1 Acsq YG01 Field 2 Description Material, %Protein, Water, Fat Field 3 Cat Leave it empty > Access sequence relevant for pricing

3. Save. The access sequence YG01 is created. 4. Leave the newly created access sequence YG01 marked and choose the field accesses. In theChange view Accesses: Overview- screen make a new entry with the following values: Field name YG01 Field 1 AcNo 1 Field 2 Tab 901 Field 3 Description Material / %Protein / %Water / %-Fat Requirement Leave field empty. Exclusive Leave field empty.

5.

Save. Leave the newly-created entry marked and choose the field Fields.

If you get the warning The field assignment has not yet been made, choose Enter twice. You will create the missing fields in the next step. 6. Choose the field fields in the New entries: Overhead of added entries screen. Now you can see the conditions belonging to the table 901. Condition MATNR YG_P YG_W YG_F 7. Save. Doc Structure KOMP KOMP KOMP KOMP

4.2 Maintaining Client-Specific Customizing for MM


Use
This section contains all the information needed to implement the general customizing settings for MM.

4.2.1 Defining Condition Types Use


SAP AG Page 14 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

In this step you define condition types. The condition types are used to represent pricing elements for prices in this solution. These are stored in the system in condition records.

Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SPRO IMG Materials Management Conditions Define Price Determination Process Define Condition Types

2. In the Change view Conditions: Condition Types: Overview screen, make a new entry for condition type YGB0: Field name Description Condition Type Description Acess sequence Cond. class Calculat.type Cond.category Group cond. Amount/percent Qty. relation Item condition Pricing Proc Delete fr. DB Scale basis Exclusion 3. Save. User action and values YGB0 Gr.Price batch Char YG01 B =Price C =Quality H 0 Basic Price Set check Set check Set check Set check RM0002 Do not delete C = Quntity scale X = Gross price Note

4.2.2 Defining Calculation Schemas Use


In this step, you define the calculation schema. This calculation schema - a framework of steps used to calculate or determine something - is used to calculate prices in out scenario.

Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SPRO IMG Materials Management PurchasingConditions Define Price Determination Process Define Calculation Schema

SAP AG

Page 15 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

2. Make new entries in Change View Schemas: Overview screen. Copy entry RM0000 Purchasing Document (Big) Field name Entry Field 1 Procedure YGRM06 Field 2 Description Batch Char. Purch. Doc.(Big)

3. Add the following entries with the command New Entries [F5]: Step 1 1 Cntr 1 2 CTyp YGB0 PBXX Description Gr.Price batch Char Gross Price Sub To 9 9 5 Reqt

4. Save. 5. Delete the following entries with the command Delete [Shift+F2]: Step 1 6. Save. Cntr 1 CTyp PB00 Description Gross Price Sub To 9 Reqt

4.2.3 Defining Schema Groups Use


In this step, you define schema groups. These allow you to group together purchasing organizations that use the same calculation schema.

Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SPRO IMG Materials Management Conditions Define Price Determination Process Define Schema Group

2. Select: Schema group: Vendors. 3. Make new entries in Change View Schema groups for vendors: Overview screen. Copy entry RM0000 [F6] Purchasing Document (Big). Field name Field 1 Schema gp. vnd. Y6 Field 2 Description Price determin. by batch char.

Entry 2

4.2.4 Defining Schema Determination Use

SAP AG

Page 16 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

In this step, you assign purchasing transactions and processes to a calculation schema; that is, you specify the cases in which a certain schema is used for our standard purchasing order.

Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SPRO IMG Materials Management Conditions Define Price Determination Process Define Schema Determination

2. Select: Determine Calculation Schema for Standard Purchase Orders. 3. Make new entries in Change View Determination of Calculation Schema in Purchasing: Overview Field name Field 1 Sceme gp. POrg YG01 Field 2 Sceme gp. vnd Y6 Field Proc. YGRM06 Field 3 Description Batch Char. Purch. Doc.(Big)

Entry 4 4. Save.

5 Master Data
5.1.1 Creating Vendor C8600 Use
The purpose of this activity is to create the master data using transaction XK01.

Procedure
1. Access the activity as follows: Transaction Code XK01

2. Detailed information about the vendor mentioned can be found in the LSMW file case SMB26_XK01_L310_G86.txt. To view the content of the SMB26_XK01_L310_G86.txt, refer to the Essential Information, section Importing vendor Master Data.

Result
The master data has been created.

5.1.2 Creating Output Condition Record ERS Use


The purpose of this activity is to create an output-condition record ERS for invoice verification.

Procedure
1. Access the activity as follows: Transaction Code MRM1

SAP AG

Page 17 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

2. Choose the condition type ERS ERS Procedure on the Create Output - Condition Records: Invoice Verification screen and press enter. 3. On the Key Combination screen, choose the Company Code/Invoicing button and press Enter. 4. Enter the necessary data as follows: Key field Company Code Inv. Pty. PartF Medium Date / Time Value (description) BP01 C8600 PI 1 3

5. Choose the communication icon and enter the necessary data as follows: Key field Output Device 6. Save. Value (description) LOCL

Result
You have created the output condition records for ERS (ERS Procedure).

5.1.3 Creating ROH Materials C47000, C47010, C47020 Use


The purpose of this activity is to create the master data using transaction MM01.

Procedure
1. Access the activity as follows: Transaction Code MM01

2. You need to create Materials C47000, C47010, C47020 as ROH. 3. Detailed information about the materials mentioned can be found in their LSMW file SMB26_MM01_L314_G87.txt. To view the content of the file SMB26_MM01_L314_G87.txt, refer to the Essential Information, section Importing Material Master Data.

5.1.4 Creating Stock Material Info Record C8600/C47000 Use


The purpose of this activity is to create an output-condition record ERS for invoice verification.

Procedure
1. Access the activity as follows: Menu Path Logistics Materials Management Purchasing Master Data Info Record Create

SAP AG

Page 18 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Transaction Code

ME11

2. On the Create Info Record : initial Screen, enter the necessary data as follows: Key field Vendor Material Value (description) C8600 C47000

3. On the Create Info Record: General Data and enter the necessary data as follows: Key field Vendor Mat. No. Order Unit Equal To Var. order unit Ctry of origin Region 4. Save. Value (description) CEK47000 PC 2 PC <-> 5 KG 1 DE 01

Result
You have created the stock material info record for vendor C8600and material C47000.

5.1.5 Creating Condition Records for Condition Type YGB0 Use


The purpose of this activity is to create the condition records for YGB0 (Gr. Price batch Char).

Procedure
1. Access the activity as follows: Menu Path Transaction Code Logistics Sales and Distribution Master Data Conditions Select using Condition Type Create MEK31

2. Choose the condition type YGB0 Price on the Create Condition Records screen and press Enter. 3. On the menu Choose Condition Create 4. On the Create YGB0 : Overview, enter the necessary data as follows and save. Key field Material % Protein % Water % Fat Amount Unit Value (description) C47000 0016 0048 0008 1,88 EUR

SAP AG

Page 19 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Per UoM

1 KG

5. Repeat the steps until step 3. 6. On the Create YGB0 : Overview, enter the necessary data as follows and choose save. Key field Material % Protein % Water % Fat Amount Unit Per UoM Value (description) C47000 0010 0030 0005 1,11 EUR 1 KG

7. Repeat the steps until step 3. 8. On the Create YGB0 : Overview, enter the necessary data as follows and save. Key field Material % Protein % Water % Fat Amount Unit Per UoM Value (description) C47000 0015 0045 0005 1,22 EUR 1 KG

9. Repeat the steps until step 3. 10. On the Create YGB0 : Overview, enter the necessary data as follows and save. Key field Material % Protein % Water % Fat Amount Unit Per UoM Value (description) C47000 0018 0048 0006 1,33 EUR 1 KG

11. Repeat the steps until step 3.

SAP AG

Page 20 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

12. On the Create YGB0 : Overview, enter the necessary data as follows and save. Key field Material % Protein % Water % Fat Amount Unit Per UoM Value (description) C47000 0020 0050 0005 1,55 EUR 1 KG

13. Repeat the steps until step 3. 14. On the Create YGB0 : Overview, enter the necessary data as follows and save. Key field Material % Protein % Water % Fat Amount Unit Per UoM Value (description) C47000 0012 0036 0006 1,44 EUR 1 KG

Result
You have created the condition records for YGB0 (Gr. Price batch Char).

5.1.6 Creating Condition Records for PB00 (Gross Price) Use


The purpose of this activity is to create the condition records for PB00 (Gross Price).

Procedure
1. Access the activity as follows: Menu Path Transaction Code Logistics Sales and Distribution Master Data Conditions Select using Condition Type Create ?? MEK31

2. Choose the condition type PB00 Price on the Create Condition Records screen and press enter. 3. On the Key Combination screen, choose Material Info Records and choose enter. 4. Enter the necessary data as follows and choose Execute.

SAP AG

Page 21 of 22

SAP Best Practices

Livestock Procurement (G86): Configuration Guide

Key field Vendor Material Purch. Organization Amount

Value (description) C8600 C47000 BP01 9,00

5. Enter the necessary data as follows and choose Execute. Key field Amount Unit Per UoM Valid to Value (description) 1,00 EUR 1 KG 31.12.9999

6. You get the message: Condition records saved.

Result
You have created the condition records for PB00 (Gross Price).

SAP AG

Page 22 of 22