Great ideas are always simple Softproviding simply makes them happen. Livestock Management Softproviding Meat User Documentation
Version: 1.00 Date: 24. August 2017 Release: 5.50 Softproviding AG Riehenring 175 CH-4058 Basel Switzerland +41 (0)61 508 21 00 support@softproviding.com www.softproviding.com SAP + Softproviding + YOU. Leading the field. 2/44
Contents 1 Overview 5 2 Basic Elements / Master Data in the Livestock Management Module 6 2.1.1 Organizational Units 6 2.1.2 Processes 7 2.1.3 Activities 7 2.1.4 Customizing Settings for Using Data Records (PDA Records) 8 2.1.5 SAP ERP Master Data 8 2.1.6 Authorizations 8 3 Maintaining Organizational Units in Livestock Management 10 3.1 Creating Units 10 3.1.1 Organizational Level 0 Plant 11 3.1.2 Organizational Level 1 Farm 11 3.1.3 Organizational Level 2 Barn 12 3.1.4 Organizational Level 3 Barn Area 12 3.2 Changing Units 13 3.3 Deleting Units 13 3.4 Inactive Organizational Units 14 4 Livestock Management Cockpit 15 4.1 Selection Screen 15 4.2 Tree Structure - Organizational Units 16 4.3 Header Data 16 4.4 Process Data 17 5 Livestock Management Activities 19 5.1 General Information 19 5.2 Creating Activities 20 5.3 Changing Activities 22 5.4 Canceling Activities 23 6 Detailed Description of Activities According to Use 25 6.1 Information Activities (without Goods Movements) 25 6.2 Activities Involving Livestock Movement 26 6.2.1 Livestock Housing with Reference 26 6.2.2 Livestock Housing without Reference 28 6.2.3 Rehousing 29 6.2.3.1 Rehousing to Another Organizational Unit 30 6.2.3.2 Rehousing to Several Organizational Units 31 6.2.3.3 Rehousing within an LSM unit and the Same LSM Process 32 6.2.4 Livestock Removal for Other Use 33 6.2.5 Removal for Slaughtering 35 6.2.6 Other Functions in Livestock Removal 37 6.2.6.1 Stock Transfer 37 3/44
6.2.6.2 Stock Reservation 37 6.2.6.3 Disassembly Order 38 6.3 Activities for Consumable Materials 38 7 Status Management in the Livestock Management Cockpit 41 7.1 Status Dependencies 41 7.2 Status Change Concept 41 8 Other Functions 44 8.1 ALV Grid Control 44 8.2 Selection/Display Variant 44 4/44
1 Overview Livestock Management in Meat Management by Softproviding was developed to document the necessary information about quantities and costs associated with breeding and fattening cycles. This allows all the processes for the different stock types to be presented. The Livestock Management module is split into three areas: Fattening planning (pen/barn capacity) Livestock Management Cockpit (management, data collection) Analysis/evaluation of fattening cycles This document provides a description of the functions of the Livestock Management Cockpit, using examples from poultry breeding. The Livestock Management process is integrated into and documented in the following Meat Management areas: Meat Management Customizing Meat Management tables for LSM processes and activities Integration with the SAP ERP is achieved by using production orders (similar to the PP01 order type) and the required master data (material masters, bills of material, routings, calculations). : Please refer to the relevant SAP documentation for information about the necessary creation/adaptations to SAP ERP master data and about using production orders. 5/44
Poultry plant Think ahead. Go there. 2 Basic Elements / Master Data in the Livestock Management Module To be able to use the Livestock Management Cockpit functions, the following basic elements must be defined beforehand and maintained in a suitable Customizing area: Organizational units Livestock management processes Livestock management activities Settings in Softproviding Core for plant data collection (PDA records) SAP ERP master data Authorizations The values stored in Customizing are not automatically translated. If you intend to use the system in multiple languages, the items in the various languages must be input separately. 2.1.1 Organizational Units Organizational units are used to mean the structure of a breeding farm. The basic structure is dependent on the plant. In other words, an organization is defined per stock type for each plant. The plant is the SAP ERP organizational unit and is absolutely vital for integrating and using the required master data and accounts. Breeders Barn 1 Sector 1 Hatchery Incubator 1 Incubator 2 Sector 1 Fattening farm Barn 1 Barn 2 Sector 2 Sector 3 Organizational units can be split into n levels (see the figure), with these then being maintained as a basic structure in Customizing. 6/44
2.1.2 Processes Processes are split into two areas: Livestock management process (for evaluation purposes) The Livestock Management process is defined by a feature that is used when creating the LSM organization. This feature determines which process is displayed in the Livestock Management Cockpit (breeders, hatchery, fattening). Several processes can be displayed, depending on the organizational structure of a (fattening) farm. Process level (for plant data collection and tracking) The process level is crucial to using the production order and providing data for the fattening cycle. Livestock management data records are created at this level, which are assigned to a production order. Any subsequent site data (activities) is entered for this process and the relevant production order. 2.1.3 Activities Activities equate to the site data that is generated within the scope of Livestock Management (e.g. housing, weighing, inoculating). Activities are entered at the lowest organizational level. Activities are defined for each process in Customizing as a description and are assigned a particular type of behavior. An activity s behavior corresponds to using information. A detailed explanation will be provided later of the various types of activities (information, planning, costs). An extract is shown below of poultry-related activities: (Grand-) Parent husbandry Hatcheries Fattening Housing Consumption of operating supplies (feed, water, vitamins, etc.) Eggs yield Losses (animals) Vet activities Sale of stock (animals) Removal of stock (animals) for slaughtering Removal / sale of eggs Housing Consumption of operating supplies (disinfectant, power, etc.) Egg yield (fertilized, not fertilized) Losses (eggs) Sale Removal / rehousing for fattening Housing Consumption of operating supplies (feed, water, vitamins, etc.) Fattening process (feed use efficiency) Losses (animals) Veterinär-Aktivitäten (Partial) removal for sale (Partial) removal for slaughtering 7/44
2.1.4 Customizing Settings for Using Data Records (PDA Records) Data records are created for site data to suit the type of activity. To do this, entries must be input in Customizing Softproviding Core in the area Logistics Process Data Acquisition in the case of the following input tables: Organization Control data Terminal with username Entry operation, goods movement The Process Data user documentation is available to provide you with further information. The behavior and impact of PDA records on tracking will be discussed later on. 2.1.5 SAP ERP Master Data The following master data is required to enable you to handle a LSR process with the cockpit: Material master data for all components (all raw, materials and operating supplies such as feed, bedding, water, vitamins, etc.); Material master data for the materials to be produced (products (semi-finished/livestock such as eggs, hybrid category A, pigs, standard fattening pig, etc.)); Bills of material (with components) must be available for the defined LSM processes; Work centers/routings must be available to calculate wages. In general, a specific order type is used for Livestock Management, which derives from the SAP ERP standard order type PPO1. 2.1.6 Authorizations To be able to use the cockpit, authorizations must be defined beforehand and maintained via a suitable customizing table. The authorizations relate to an SAP user and are defined for the following levels: Maintaining LSM organizations; Processing (creating, changing and deleting) activities within a group (activity type); Processing (creating, changing and deleting) individual activities. You can find the relevant information in the Livestock Management Configuration Guide. 8/44
Example of the Structure: Barn 1 - Breeders process Group: Breeding laying hens Group: Egg production Process 00000500 - Production order 10000010 Process 00000502 - Production order 1000011 Housing Feeding Vet check Housing Check Sorting n PDA n PDA Info n PDA Info n PDA The structure and dependencies are shown once again in the figure. One process is assigned per barn 1 n groups are assigned per process 1 n LSM processes can be assigned per group 1 n production orders are assigned to each LSM process N activities are carried out per LSM process A PDA (site data record) or an activity information record is created per activity. 9/44
3 Maintaining Organizational Units in Livestock Management SAP Menu Transaction Code Softproviding Meat > Procurement > Livestock > Livestock Management > Organizational Units Maintenance /SPMEAT/BFRM_ORG To be able to use the Livestock Management Cockpit, the organizational structure of Livestock Management must be defined beforehand and maintained in Meat Management Customizing. This basic structure is then transferred by creating organizational units in the maintenance cockpit with a description. When creating organizational units in the maintenance cockpit, a number is assigned by the system (controlled via a number range), which is required as a reference or basis for continuing to use the Livestock Management Cockpit. This is displayed as a tree structure in the cockpit. The following determining factors apply to maintaining organizational units: The SAP user must have appropriate authorization. Organizational units may be expanded at any time. Organizational units may be deleted if no LSM processes were carried out in this unit. Organizational units may be deactivated as soon as no LSM processes are available. Alternatively, the tree structure can also be created via the Livestock Management Cockpit. It provides the Organizational units in LSM button for this purpose. 3.1 Creating Units Procedure This tool provides you with the following navigation options: Navigation via mouse If you right-click with your mouse, a pull-down menu appears, offering you the following options: Function Expand sub-tree Compress sub-tree Add row Change row Delete row Description Displays the entire tree structure with all the subfolders Displays the top organizational level of the tree structure Inserts a level or element Changes a level or element Deletes a level or element Navigation via bar 10/44
The navigation bar offers the following action options: Icon Function Description Expand sub-tree Displays the entire tree structure with all the subfolders Compress sub-tree Displays the top organizational level of the tree structure Find Recalculate columns Print view Select layout Add row Change row Delete row Standard search function Standard function for totaling (not applicable here) Standard print function Selects a display variant Inserts a level or element Changes a level or element Deletes a level or element The transaction starts in display mode and is then switched to change mode. The structure is created based on the organizational units specified previously in the Customizing settings. When expanding or creating levels, it is important that the referencing level is selected. With each additional level the features already previously defined (plant, LSM group, etc.) appear in gray. You save the settings by clicking on the icon in the standard navigation bar. 3.1.1 Organizational Level 0 Plant The plant is assigned at the first level. This is where the materials to be produced there (livestock for fattening, breeders, eggs, etc.) are defined. The LSM process and LSM group can then be defined at this level. If data is input here, it automatically appears when all the other organizational levels are created. Field Name Plant LSM process LSM group Description The plant is a production site in your company Option field for defining the process (fattening, hatchery, etc.) Option field for selecting an LSM group (breeder, store pigs, Bio cattle, etc.) 3.1.2 Organizational Level 1 Farm A vendor or customer must be input at level 1. The vendor/customer is required to be able to carry out the following settlements. Field Name Description 11/44
Plant Not ready for input, as already defined at level 0 Vendor Customer A vendor is a business partner who supplies materials or services. Payment must be made to the vendor for a delivery that has been made or a service that has been received. A customer is a business partner with whom you have a relationship involving the transfer of goods and services. LSM process If applicable, ready for input; if not ready yet, defined at level 0 LSM group If applicable, ready for input; if not ready yet, defined at level 0 3.1.3 Organizational Level 2 Barn You can create a number n of organizational units at this level. Field Name Description Plant Not ready for input, as defined at level 0 Vendor Not ready for input, as defined at level 1 Customer Not ready for input, as defined or definable at level 1 LSM unit no. LSM unit name LSM process LSM group Internal (system-generated) number that is assigned via a number range during the creation process External input option for providing a customer-specific name for the organizational unit If applicable, ready for input; if not ready yet, defined at a higher level If applicable, ready for input; if not ready yet, defined at a higher level When you create a level, a system-generated number is assigned (based on a number range table) for you to use later to identify the organizational unit. This number will be saved in all data records at a later juncture and be forwarded to integrated processes (such as slaughter planning). 3.1.4 Organizational Level 3 Barn Area In this example, this is the lowest organizational level defined for the Livestock Management processes and the activities to be carried out. The procedure when creating organizational units corresponds to the procedure documented in level 2 where n units can be created. Field Name Description Plant Not ready for input, as defined at level 0 Vendor Not ready for input, as defined at level 1 Customer Not ready for input, as defined or definable at level 1 LSM unit no. Internal (system-generated) number that is assigned via a number range during the creation process 12/44
LSM unit name LSM process LSM group External input option for providing a customer-specific name for the organizational unit If applicable, ready for input; if not ready yet, defined at a higher level If applicable, ready for input; if not ready yet, defined at a higher level 3.2 Changing Units If you want to name the organizational units (such as plant, barn, barn area used in this example) or expand levels, you use the Customizing table. You can amend in the input template for the organizational units only the data that has been input manually within the structure (e.g. vendor, unit names, etc.). Procedure The amendments are applied to the data element. To do this, you need to select the element here (in the same way as with creating structures). The amendments can only be applied at the level where the characteristics/data were entered for the first time, for example: Vendor at farm level Process at barn level LSM group at barn area level LSM unit name at the created element The relevant fields are available to amend according to the appropriate level. Once you have made the amendment, you must save the transaction. 3.3 Deleting Units You can delete units at various levels. One requirement for this is that there is no Livestock Management data available in the form of LSM orders and activities. Procedure You must select completely the element you created to delete it. If you select the wrong level, a message appears telling you that you cannot perform the deletion. All the elements attached to the selected level are also deleted. The deletion is only applied after you have saved the transaction. 13/44
3.4 Inactive Organizational Units Apart from deleting organizational units, you can also remove them temporarily from the structure by deactivating them. Procedure Select the relevant level by double-clicking it. The input screen for changing data is displayed. It contains a checkbox that you can use to activate/deactivate the unit. You can only do this if all the Livestock Management processes within the organizational unit are complete. These units can be recognized by a relevant check mark appearing in the overview. 14/44
4 Livestock Management Cockpit SAP Menu Transaction Code Softproviding Meat > Procurement > Livestock > Livestock Management > Livestock Management Cockpit /SPMEAT/BFRM The Livestock Management Cockpit contains all the relevant data (actions/information) entered for a Livestock Management process. The production orders required for this are generally created during the planning process. Part of the evaluation can be carried out directly in the cockpit, while the cost analysis is carried out at production order level in the SAP ERP. The cockpit comprises the following elements: Selection screen Organizational structure in the form of a data tree in the left section of the cockpit Header data Navigation bar Process data (detail display for LSM processes and activities) The individual elements will be described in detail in the following sections. 4.1 Selection Screen The cockpit opens with a selection screen, which you can add further selection and mandatory fields to, as required. Field Name Stock type Plant Vendor Customer LSM unit no. LSM process no LSM group Inactive LSM units Description Field for selecting the stock type (pigs, cattle, hens, etc.) Organizational unit where the material (in this case, livestock for fattening, breeders) is produced. Vendor such as the company providing service/fattener Customer (in the case of contract fattening) Organizational unit number assigned by the system Number assigned by the system for the process Option field for selecting an LSM group (breeder, store pigs, Bio cattle, etc.) Field indicating deactivated organizational units You can use the selection criteria to create variants and save them. The Plant and Stock type fields must be completed as an absolute minimum. The following functions are available via a navigation bar in the program: 15/44
Icon Function Description Execute Get variants Organizational units in LSM This starts the program The program starts after clicking on the Execute function button. This accesses and chooses the selection variants available (This button only appears in the navigation bar if there are variants available.) You can switch directly to the maintenance program for the organizational units in LSM. 4.2 Tree Structure - Organizational Units The selected organizational structures are displayed in the form of a tree structure in the left section of the cockpit. The units cannot be amended any further here, but the available information can be made user-specific and saved as a variant. You will find information about using and adapting ALV grid tables in the section Status management in the Livestock Management Cockpit. You can display on the right side, at your discretion, the data for an LSM order or the relevant actions. You can open and close the structure in the tree via the navigation bar. The level the process is defined. icon identifies at which 4.3 Header Data Header data cannot be amended and contains the selected values from the cockpit s initial screen. Information is adapted according to the selected organizational units. If you double-click on the level in the selection tree, other transactions will become available for you to choose. An overview will also appear on the right side of the cockpit, indicating subsequent input options you can choose. Field Name Org. level Plant Vendor Customer LSM unit no. LSM process no. Description Field for selecting the stock type (pigs, cattle, hens, etc.) Organizational unit where the material (in this case, livestock for fattening, breeders) is produced. Vendor such as the company providing service/fattener Customer (in the case of contract fattening) Organizational unit number assigned by the system Number assigned by the system for the process 16/44
LSM group Option field for selecting an LSM group (breeder, store pigs, Bio cattle, etc.) 4.4 Process Data Process data comprises the following elements: LSM header data Item data Activities The LSM header data is created prior to starting the breeding cycle. There is a function available for this in the navigation bar called New LSM process. This data record contains the following information: Field Name Org. level Plant Vendor Customer LSM unit no. LSM process no. LSM group Item LSM process no. header Vendor Customer Description Field for selecting the stock type (pigs, cattle, hens, etc.) Organizational unit where the material (in this case, livestock for fattening, breeders) is produced. Vendor such as the company providing service/fattener Customer (in the case of contract fattening) Organizational unit number assigned by the system Number assigned by the system for the process Option field for selecting an LSM group (breeder, store pigs, Bio cattle, etc.) Indicates which of the LSM processes displayed is active in this organizational unit. Organizational unit where the material (in this case, livestock for fattening, breeders) is produced. Vendor such as the company providing service/fattener Customer (in the case of contract fattening) The item data is generated when the first activity is executed. This item can contain a group of animals or individual animals. All the activities for the livestock assigned to the item are carried out within this item. Item data cannot be deleted as the activity exists. However, a deletion flag can be set. To do this, all the available activities need to be canceled beforehand. You can create the new Livestock Management process via the navigation bar. When you click the button in the action bar, the transaction is automatically run. The data required is extracted from the previously created organizational structure. The data record is then displayed in the right section of the cockpit. This data record is used to create the header data. 17/44
The Livestock Management process has no link to Standard SAP. It is used only as a document within the Livestock Management Cockpit. You can only delete the Livestock Management process if no items have been created. To perform a deletion, you click on the relevant icon in the action bar and confirm the transaction. 18/44
5 Livestock Management Activities 5.1 General Information To be able to cover the entire Livestock Management process, various activity classes have been developed. Activity classes are assigned in Customizing to the various activities and form the basis for the background updates in the standard SAP program. Activities are defined and assigned to the relevant activity classes in a customizing table. A suitable, detailed description is provided in the Customizing documentation Livestock Management. Creating the activity Creating the PDA record Entry in the activizy table The activities are split into the following activity categories/groups: Information activities (I-activities) This is straight information management without any impact on the processes in SAP. This function mainly fulfills reporting or monitoring purposes. The data that has been entered has no impact (in terms of cost, value or quantity) on the referenced production order used to settle this Livestock Management process. Activities involving material movements Executing these activities triggers transactions in the standard SAP program or in Softproviding Meat. This action is processed in the background and is not directly visible to the user. All activities are completely effective in terms of cost in the production order assigned for this Livestock Management process. The whole Livestock Management process is initiated, controlled and ended via these movement activities. Activities for consumable materials In this case, all the activities are assigned that enter all the necessary operating supplies in a Livestock Management process and post them to the relevant production order, thus affecting costs. In this instance, other postings are also launched in the background in Standard SAP or Softproviding Meat. 19/44
Activities with goods movements Activities for consumable materials Information activities Housing (with or without reference) Rehousing (individual/mass change) Removal (complete partial) for sale (e.g. sale of pigs for fattening to trader, laying hens, etc.) Removal (complete/partial) for slaughtering Vitamins Feed Bedding Oil, water, etc. Planning vet visits Fattening process statisitical weighings Losses(animals) Vet activities 5.2 Creating Activities Procedure There are three functions available in the right header area of the cockpit for you to create activities: Button for executing the LSM activity Input field (using input help) for selecting the activity category Input field (using input help) for selecting the activity : The Execute button can only be activated if the appropriate values were input for the activity category and activity. Otherwise, you will get the message: Enter the correct activity. When you click on the button to confirm, an input screen appears. This input screen contains the following elements: Header data This displays all the data from the selection: Activity category LSM activity Stock type Livestock Management process Header data cannot be amended. If the header data is incorrect, you should stop entering data. 20/44
Section for entering source data All the data is entered in this area that is used as input for the Livestock Management process. This source data may have different variants: Text field containing freely defined text for information messages (information activity) Quantities and units of measure Reference to SAP cost objects (number of order/production order) Material number of the components used (raw materials and operating supplies) Batch of used components Plant (for the components used) Storage location (for the components used) The input fields available vary according to the activity category. Section for entering target data The target section is aimed at the recipient of the information or site data. This recipient may have different variants: The production order assigned for this LSM process Subsequent process Slaughter planning Subsequent process Disassembly Subsequent process Rehousing of livestock in another organizational unit with the same production order Subsequent process Rehousing of livestock in a new Livestock Management process with a new production order The fields for inputting data may be opened or blocked, depending on the variant. The variants are described in detail in this documentation based on activity category. The following functions are available in the bottom area of the input screen for you to exit the screen: Button Description The activity is created and the PDA records generated The screen is closed without saving Result When the activity is carried out, a new row is always created with the activity in the Livestock Management Cockpit for the selected Livestock Management process. The data entered is also available there. In the case of activities involving material movements, a PDA record (Meat Management site data record) is generated in the background. When the activity is accessed again, an icon appears for retrieving the available PDAO records. If you click on the document number, you can retrieve the relevant PDAO file and all the information about the SAP documents generated is displayed: 21/44
If you change or cancel activities, the associated PDAO records are canceled and recreated. You will find detailed information about the data fields and the structure, as well as about managing and using PDA records in our Process Data documentation. 5.3 Changing Activities One factor taken into account during this procedure is whether goods movements (PDA records, material documents) have taken place or only an activity has been created in the activity table. Procedure To make an amendment, you need to select the relevant activity completely in the cockpit. You then click on the Change activity button. An input screen appears allowing you to apply the changes directly. The fields that you can change are available for you to overwrite. Result The following data is created depending on the activity category: Activities involving PDA records Cancellation indicator in the activity table Cancellation of the PDA record Creation of a new activity Creation of a new PDA record with the amended data 22/44
This ensures that all the postings related to the original activity are completely modified. The amendments are documented in the cockpit and Livestock Management process. An entry is made in the change history. Activities without PDA records Cancellation indicator in the activity table Creation of a new activity 5.4 Canceling Activities You can only cancel activities if the follow-up activities with material documents (feed consumption) have been previously canceled. Housing Consumable materials Removal You cannot cancel livestock housing if the consumable materials have already been entered. You can cancel consumable materials even if livestock removal has already taken place Procedure To cancel activities, you need to select the relevant activity in the cockpit and click on the Change activity button. The button for canceling the activity is in the activity itself. After you select the button, a message screen appears where you need to confirm again that you wish to cancel the activity. Result After you have confirmed the successful operation, this will result in: a cancellation indicator being inserted in the activity table the PDA record being canceled The PDA records that were originally created and posted are canceled and receive a new PDA record as an offsetting entry. Once the PDA record is posted, the cancellation material document is generated in the SAP ERP. The canceled activities are still displayed, depending on the display variant in the cockpit s activity overview. With the deletion/cancellation indicator being excluded from the variant, they are no longer displayed. 23/44
24/44
6 Detailed Description of Activities According to Use 6.1 Information Activities (without Goods Movements) The main purpose of these activities is to document values and information, without having an impact on costs or balances. The activities are created using the following classes: Activity Class /SPMEAT/ Application Area Features CL_BRACT_INFORMATION Documenting room temperature, other information Text field CL_BRACT_INFO_MORTAL Scrap (number of dead animals) Number and unit of measure CL_BRACT_VETERVISIT_CO Confirming dates (e.g. vet) Date (selection field in calendar) and freely defined text CL_BRACT_VETERVISIT_PL Scheduling dates (e.g. vet) Date (selection field in calendar) and freely defined text Text information In this case, only text can be input. The maximum number of characters is restricted to 46. You can define the nature of the information in the text you input or also as a description of the activity. Value input This activity helps you document values without any impact on balances or costs. The reason for using it is to describe the activity. Example Value Number of dead animals Quantity of bedding Volume of water Activity Counting dead animals Consumption of bedding barn Water consumption drinking Planning and monitoring activities This activity category allows you to enter time data relating to an information field. In this case, the number of characters is restricted to 46. There is also an additional activity for confirming and monitoring planning data. Example Planning vet visits Planning statistical weighings 25/44
6.2 Activities Involving Livestock Movement These activities are used to launch other processes in Meat Management by Softproviding or in the standard SAP program. A variety of functions are available for this in the activities, which you can use to make further entries. The term Livestock movement is used to describe the process of housing livestock and removing them from housing, as well as entering by-products. A PDA record (process data records) is always generated with every activity. When the PDA records are posted, a material document is generated with the specified movement type. The following classes are used for goods movements: Activity Class /SPMEAT/CL_BRACT_INDUCT_REF /SPMEAT/CL_BRACT_INDUCT_NOREF /SPMEAT/CL_BRACT_COMPLETE_FULL /SPMEAT/CL_BRACT_COMPLETE_PART /SPMEAT/CL_BRACT_DISPATCH_FULL /SPMEAT/CL_BRACT_DISPATCH_PART /SPMEAT/CL_BRACT_MASS_MOVEMENT /SPMEAT/CL_BRACT_MOVEMENT Application Area Livestock housing with reference (for purchase order) Livestock housing without reference (for purchase order) Complete removal/slaughtering Partial removal/slaughtering Complete removal/sale Partial removal/sale Rehousing in different units Rehousing in another unit These functions and their impact are described in detail in the following sections. 6.2.1 Livestock Housing with Reference This activity launches the Livestock Management process, creating a reference to an external procurement process (SAP document Purchase order). When the activity is executed, the following processes are handled in an integrated manner: Goods receipt for purchase order Posting the purchased material to inventory The input template features the following options in terms of data fields: Mandatory input fields (indicated by the icon) Optional input fields (are generally identified by a white background) Pre-assigned data fields (standard values from referenced documents) The reference data is entered for the component in the source area: 26/44
Field Name Description Feature Purch. doc. SAP number for purchase order Mandatory field Item Number of the purchasing item Mandatory field Plant Plant number Default field Storage loc. Material Default value, if it features in the purchase order Mandatory field Number and name of the purchase material (chicks, piglets, etc.). They are inserted from the purchase order Default field Batch Batch number for tracking the vendor Optional input field Quantity Basic quantity and unit of measure Mandatory field Quantity in DUM Double quantity and units of measure Optional input field The target data contains the information for the material to be produced, along with the relevant organizational units. Field Name Description Feature Plant Plant number Default field Vendor Fattener according to the LSM unit Default field LSM unit no. Number of the organizational unit Default field Prod. order Number of the SAP production order Mandatory field Storage loc. Is inserted from the production order Default field Material Batch Number and name of the material to be produced similar to a production order Batch number for tracking the produced material similar to a production order Default field Default field Order quantity Basic quantity and unit of measure Mandatory field Quantity in DUM Double quantity and units of measure Optional input field The following buttons are available in the screen: Button Description The activity is created and the PDA records generated The screen is closed without saving The following data fields contain buttons that you can use to switch manually to a standard SAP function: Source data Field Name Purchasing document & item Batch Description Selection help (F4) and switch to change mode (ME22N) Selection help (F4) and create a batch 27/44
Target data Field Name Production order Description Selection help (F4) and create/change an order Please refer to the relevant SAP documentation for a description of the functions for the standard SAP transactions. Executing the activity generates two PDA records, while posting generates the following material documents: Goods receipt posting for purchase order (The posting is then available in the purchase order history). Goods issue posting for production order (including the consumption of material). The posting is stored in the production order under Documented goods movement. 6.2.2 Livestock Housing without Reference The Housing without reference feature involves posting the consumable materials to the production order using two variants. You select the variant using the checkbox in the activity. Variant 1 Material not in stock (GR + GI) Executing the activity generates two PDA records/postings: Unplanned goods receipt for stock Goods issue for production order Variant 2 Material is in stock (only GI) Executing the activity generates one PDA record/posting: Goods issue for production order Source data Field Name Description Feature Plant Plant number Mandatory field Storage loc. Material Batch Default value, if it features in the purchase order Mandatory field Number and name of the component (chicks, piglets, etc.) Batch number for tracking; can be generated directly Mandatory field Optional input field Quantity Basic quantity and unit of measure Mandatory field Quantity in DUM Double quantity and units of measure Optional input field Target data Field Name Description Feature Plant Plant number Default field Vendor Fattener according to the LSM unit Default field LSMUnitNo. Number of the organizational unit Default field 28/44
Prod. order Number of the SAP production order Mandatory field Storage loc. Is inserted from the production order Default field Material Batch Number and name of the material to be produced similar to a production order Batch number for tracking the produced material similar to a production order Default field Default field Order quantity Basic quantity and unit of measure Mandatory field Quantity in DUM Double quantity and units of measure Optional input field 6.2.3 Rehousing This activity is used to transfer material (chicks/livestock for fattening) to other organizational units. Rehousing can be carried out for both the whole and partial stock in an LSM unit. The following rehousing activities are available: Rehousing in a new organizational unit (1:1 rehousing) Rehousing in several organizational units (1:n) The following functions are available in both activities: Changing the organizational unit Creating or assigning a production order The production order is generally transferred for the new organizational unit if the current fattening process will still continue completed and a new production order assigned if a new fattening process is started. The source data corresponds to the master data from the production order that is active in this organizational unit, and is the same for all activities: Field Name Description Feature Plant Plant number Default field Vendor Fattener according to the LSM unit Default field Cust. Customer number in the case of contract fattening Default field LSMUnitNo. Number of the organizational unit Default field Order Number of the SAP production order Default field Stor. loc. Is inserted from the production order Optional input field Material Batch Number and name of the material to be produced similar to a production order Batch number for tracking the produced material similar to a production order Default field Default field Targ. qty Basic quantity and unit of measure Default field Quantity in DUM Double quantity and units of measure Default field 29/44
Poultry plant Think ahead. Go there. 6.2.3.1 Rehousing to Another Organizational Unit Section 1 Incubator 1 Section 2 (source) Hatchery Incubator 2 Section 3 Barn 1 (targetl) Fattening farm Barn 2 Target data Field Name Description Feature Plant Plant number; is inserted from source data Mandatory field Vendor Fattener according to the LSM unit Mandatory field Cust. Customer number in the case of contract fattening Mandatory field LSMUnitNo. Number of the organizational unit Mandatory field Order Number of the SAP production order; is inserted from the source data Optional input field Stor. loc. Is inserted from the production order Optional input field Material Batch Number and name of the material to be produced similar to a production order Batch number for tracking the produced material similar to a production order Default field Default field Targ. qty The total order quantity and unit of measure Default field Quantity Quantity and unit of measure for rehousing (stock) Mandatory field Dbl. Quantity Double quantity and units of measure Optional input field You must input a plant first so that you can select the next lowest LSM unit by pressing F4. There is also an option for creating a stock reservation for the subsequent procurement process or slaughtering process. If you click on the function another data input area appears: 30/44
Poultry plant Think ahead. Go there. Field Name Slaughtering method Slaughtering plant Vendor Slaughtering site Description Field for selecting the slaughtering method Plant that is allocated to the slaughtering site Vendor such as the company providing service/fattener Vendor number for the slaughtering site Detailed information about using livestock reception documents and the necessary data are provided in the Slaughtering product documentation. This activity is created with the following entries: Source process Activity referring to the new organizational unit PDA record with goods receipt for production order Target process An LSM process is created Activity for rehousing with reference to the source process or organizational unit. PDA record with goods issue for production order If the Stock reservation function is being used, a stock reservation is generated and the document number in the activity is updated. 6.2.3.2 Rehousing to Several Organizational Units Section 1 Hatchery Incubator 1 Inkucator 2 Section 2 (source) Section 3 Fattening farm 1 Barn 1 Barn 2 (target) Fattening farm 2 Barn 1 (target) Barn 2 31/44
Poultry plant Think ahead. Go there. The structure of the source data is identical to that for the single unit variant. The difference when entering the target data is that the operation is carried out in the form of a table for several organizational units. Rehousing is carried for each row, which also includes the option of generating a new production order, new target unit and, if required, a new livestock reception document. Example The day s chicks from the hatchery are distributed to several fatteners. Each fattener has its own organizational units and new production orders for fattening. An activity is created per row with the following entries: Source process Activity referring to the new organizational unit PDA record with goods receipt for production order Target process An LSM process is created Activity for rehousing with reference to the source process or organizational unit. PDA record with goods issue for production order If the Stock reservation function is being used, a stock reservation is generated and the document number in the activity is updated. 6.2.3.3 Rehousing within an LSM unit and the Same LSM Process Hatchery Incubator 1 Incubator 2 Section 1 Section 2 Fattening farm 1 Barn 1 (sourcee) Barn 2 (target) Fattening farm 2 Barn 1 Barn 2 32/44
You can use this function to display the physical rehousing of the livestock within the leading LSM unit and the Livestock Management process, so that the assigned production order remains unchanged. This allows you to distribute the livestock resources (number of animals) from one LSM unit to various new LSM units. You can activate this function using the Rehousing (multiple) activity. This activity is created with the following entries: Source process Activity referring to the new organizational unit(s) PDA record with goods receipt for production order Target process An LSM process is created Activity for rehousing with reference to the source process or organizational unit. PDA record with goods issue for production order If the Stock reservation function is being used, a stock reservation is generated and the document number in the activity is updated. Caution Any change to the activity must be made in the original LSM unit. A suitable message is displayed by the system if the wrong LSM unit is selected. 6.2.4 Livestock Removal for Other Use This activity controls the removal of animal resources for other processes outside slaughtering. The following processes may be displayed using this activity: Sales of eggs to third parties Sales of livestock for fattening to third parties There are two different activities for partial and complete removal, with the input screen and other postings being identical for both. Source data Field Name Description Feature Plant Plant number Default field Vendor Fattener according to the LSM unit Default field LSMUnitNo. Number of the organizational unit Default field Order Number of the SAP production order Default field Stor. Location Is inserted from the production order Default field Material Batch Number and name of the material to be produced similar to a production order Batch number for tracking the produced material similar to a production order Default field Default field 33/44
Target quantity Basic quantity and unit of measure Default field Dbl. Quantity Double quantity and units of measure Default field Target data Field Name Description Feature Plant Plant number; is inserted from source data Mandatory field Stor. Location Material Batch Date of Manuf. Quantity Is inserted from the production order and can be changed Number and name of the material to be produced similar to a production order Batch number for tracking the produced material similar to a production order Hatching date, fattening date, which is updated in the batch features, is inserted Quantity and unit of measure for rehousing (stock) Mandatory field Default field Default field Mandatory field Mandatory field Dbl. Quantity Double quantity and units of measure Optional input field This activity generates the following data: Activity in the activity table PDA record with goods receipt about quantity produced for production order Confirmation for the production order with the quantity produced Caution If full removal is carried out to storage, no other activities or partial removals can be carried out. The production order is completely confirmed. Removal of main and by-products in a single entry When carrying out a partial/complete removal, you can also remove a by-product or unplanned product. However, the material needs to be entered as a by-product in the bill of material of the planned material. Please refer to the relevant SAP-ERP documentation for information about maintaining and using byproducts. You enter by-products by checking the action box. The necessary data fields are then made available for editing. The By-product field is a selection list that refers to the bill of material. If the by-product is not entered, the bill of material must be adapted and the master data read in the production order. Field Name Description Feature By-product Selection list referring to the bill of material. Selection field Quantity Quantities and unit of measure Mandatory field Batch Batch number for tracking; is recreated Mandatory field 34/44
The date of manufacture for the main material is used in parallel for the by-product. This activity generates the following data: Activity in the activity table PDA record with goods receipt about main material and quantity produced for production order PDA record with goods receipt from unplanned material (by-product) and quantity produced for production order Confirmation for the production order with the quantity produced Removing a by-product To do this, you need to enter the by-product s relevant material number in the Material field in the Target data section. You do not need to activate the by-product function. After inputting the material number, a message will appear if the material is not to be included in the bill of material. You confirm by pressing the Enter key. This message is mainly used as a confirmation prompt to ensure that a by-product is entered. This activity generates the following data: Activity in the activity table PDA record with goods receipt from unplanned material (by-product) and quantity produced for production order Confirmation for the production order with the quantity produced 6.2.5 Removal for Slaughtering Removal for slaughtering is generally the last step in the Livestock Management process. There are two options available for removing livestock for slaughtering: Partial removal This function and the input screen are identical to those for the Complete removal activity. The difference between them is that the process is not complete with partial removal as further activities can be carried out. The section Complete removal will describe exactly what this activity entails. Complete removal This activity completes the Livestock Management process in the cockpit. This means that no further activities can subsequently be carried out. One reason for this is that the production order is confirmed and completed. To make retroactive corrections, you need to cancel the activity first. This then makes the Livestock Management process available for other activities to be entered. In a similar way to livestock removal, a by-product is entered for other uses. The source data is exactly the same for both activities: Field Name Description Feature 35/44
Plant Plant number Default field Vendor Fattener according to the LSM unit Default field LSMUnitNo. Number of the organizational unit Default field Order Number of the SAP production order Default field Storage loc. Is inserted from the production order Default field Material Batch Number and name of the material to be produced similar to a production order Batch number for tracking the produced material similar to a production order Default field Default field Target quantity Basic quantity and unit of measure Default field You can also deactivate the organizational unit by checking the action box. There are several functions available for target data: Livestock removal with reference to the slaughtering site in the same plant Transfer posting of material (plant to plant) Creating a stock reservation Creating a production order for disassembly/slaughtering The target data for general livestock removal is as follows: Field Name Description Feature Plant Plant number; is inserted from source data Mandatory field Stor. loc. Material Batch Production date Quantity Is inserted from the production order and can be changed Number and name of the material to be produced similar to a production order; the data is inserted from the production order Batch number for tracking the produced material similar to a production order Hatching date, fattening date, which is updated in the batch features; the current date is inserted Quantity and unit of measure for rehousing (stock) Mandatory field Mandatory field Mandatory field Mandatory field Mandatory field Dbl. Quantity Double quantity and units of measure Optional input field Slght. plant Slaug. Stor. Loc. Number of the SAP plant where slaughtering is assigned Storage location where the material for slaughtering should be posted Mandatory field Mandatory field Slaught. site Vendor number for the slaughtering site Mandatory field The storage location for posting the livestock resources in the Livestock Management process and the storage location in the slaughtering process are generally different. 36/44