Configuration Guide Disassembly
Configuration Guide Disassembly
Disassembly
Softproviding Meat
Configuration Guide
Version: 1.00
Release v6.00
2024/02 Internal – authorized for customers and partners
Think ahead. Go there.
Softproviding AG
Dornacherstr. 210
CH-4053 Basel
Switzerland
+41 (0)61 508 21 21
[email protected]
www.softproviding.com
Contents
1 Overview 5
2 Customizing 8
2.1 Processes 8
3 Configuration/Production 11
3.1 Central Settings 11
3.1.1 Cross-Plant 12
3.1.2 Plant Group 18
3.1.3 Plant 18
3.2 Master Data / Cut 27
3.2.1 Allowed Material Types 27
3.2.2 Check Settings 28
3.2.3 Number Ranges: Cuts 30
3.2.4 Enhancement – Cut 30
3.3 Master Data / Cut List 31
3.3.1 Check Settings 31
3.3.2 Number Ranges: Cut Lists 33
3.3.3 Enhancement – Cut List 34
3.4 Master Data / Further Settings 34
3.4.1 Cost Groups 34
3.4.2 Cost Pools 36
3.4.3 Disassembly Processes 39
3.4.4 Disassembly Process Groups 42
3.4.5 Loss Types 43
3.5 SAP Standard Customizing 44
3.5.1 Disassembly Order 44
3.5.1.1 Order Types 44
3.5.1.2 Order Type-Dependent Parameters 46
3.5.1.3 Default Values 47
3.5.1.4 Scheduling Parameters 48
3.5.1.5 Settlement Profile 48
3.5.1.6 User Fields 50
3.5.1.7 Formulas and Formula Parameters 51
3.5.1.8 Activity Types 51
3.5.2 Production Order: Period-End Closing 52
3.5.2.1 Source Structure 52
3.5.2.2 Target Cost Version 52
3.5.2.3 Variance Keys 53
3.5.3 Long-Term Planning Calculation 53
3.5.3.1 Material Requirements Planning per Plant 53
3.5.3.2 Planned Independent Requirements Version 53
3.5.3.3 Define Selection Rules 54
3.6 Product Cost Planning / Standard Cost Estimate 54
3.6.1 General Settings 54
4 Enhancements 92
4.1 SAP Standard Enhancements 92
4.1.1 Mandatory Enhancements 92
4.1.2 Optional Enhancement 92
4.1.3 Others 93
4.2 Softproviding Core and Softproviding Meat Enhancements 93
4.2.1 Mandatory Enhancements 93
4.2.2 Optional Enhancements 93
5 Master Data 96
5.1 Classification Cut – Statistics 96
5.1.1 Classification Cut – Change/Display 96
5.1.2 Update Classification Statistics 97
5.2 Material Ledger 100
1 Overview
This Disassembly configuration guide describes the table and field settings which may be made for
the respective application. This configuration enables you to set up an executable and functioning
application.
Target Groups
— Application consultants, technical consultants and developers
— Members of the project team during implementation
— Super user
Prerequisites
Wherever necessary reference is made to prerequisites which must be given in order to be able to
make the respective settings (e.g. SAP Standard customizing, master data, authorizations).
References
In this configuration guide, references to other documents or possible program adjustments will be
given. This includes:
— User documentations
— Configuration guides for other application areas
Functions
In the Customizing tables, the following functions are usually available:
— Creating new entries
— Copying selected entries
— Deleting entries
— Canceling changes
— Switching from Display mode to Change mode
— Selecting all / selecting block / deselecting all
These functions are generally known and will therefore not be described explicitly.
Fiori-Apps – Instructions
SAP Fiori is the design concept for user interfaces within SAP applications. With this approach, Fiori
apps can be simplified and personalized, and made available in the Launchpad based on user roles.
SAP Fiori were created for the various applications of Softproviding Meat and can be executed in the
Fiori Launchpad. Please compare the following documents for the prerequisites and the procedure re-
garding the configuration of SAP Fiori apps:
— Softproviding Meat Security-Guide
The Security Guide documents for which Softproviding Meat Applications SAP Fiori apps were created
and which roles are required for this.
Customer-Specific Enhancements
In cases where enhancements are available for applications the configuration of which is described
here, this will be referred to at the respective section (configuration guide and user documentation).
BAdIs (business add-ins) are used to create customer-specific program enhancements which may be
implemented by the customer if necessary. In case of upgrades, these enhancements will not be af-
fected. BAdIs are implemented using SAP Standard transaction.
For further details please refer to the “Enhancements” section in this configuration guide.
Transport
The settings made should be transferred to a transport request when they are saved. The respective
settings to ensure this must be made by a responsible member of the project team. This allows you to
transport these settings into other systems.
Caution
Account must be taken of the particularities for the transport of number ranges.
Result
This configuration guide allows you to make the settings required to make productive use of the ap-
plications described. Any master data or authorizations which might be required are dealt with in the
respective user documentation.
2 Customizing
Start Customizing using one of the options stated below and then select the SAP Reference IMG but-
ton.
Within the IMG select the menu item Softproviding Meat and then item Production.
The following functions are listed under this menu item and are described in this configuration guide:
— Plant Groups (not relevant in this release)
— Central Settings
— Cross-Plant
— Plant Group (not relevant in this release)
— Plant
— Master Data
— Various sub-items (cut and cut list)
— Product Cost Planning
— Various sub-items (calculations/costing)
— Material Requirements Planning
— Various sub-items (calculations/costing)
— Execution – Disassembly Orders
— General Settings
— Plant-Dependent Settings
— Excluded Document Types
— Excluded Statuses)
— Execution – SAP Standard (Production Order)
— Order Types
— Order Type-Dependent Parameters
— Default Values
— Scheduling Parameters for Production Order
— Execution – SAP Standard (Production Order)
— Create Activity Types
2.1 Processes
In this document, first a short description of the application the configuration of which is being ex-
plained is given. This is followed by a description of the respective Customizing tables as well as a
detailed description of the field settings (configuration).
The following process overview shows the integration of the Softproviding Meat Standard Cost Esti-
mate and the MRP Calculation in the overall process.
In order to create the Softproviding Meat applications Standard Cost Estimate and MRP Calculation
as well as disassembly orders, various master data are required. Before these applications can be ex-
ecuted, these master data must be created. These are mainly the master data Cut and Cut List as well
as Material, Routing and Work Center. Cut and Cut List are Softproviding-Meat-specific master data in
Disassembly. Material, Routing and Work Center are SAP Standard master data. For a description of
how to create these master data, please refer to the following user documentation:
— Disassembly, “Master Data: Disassembly”.
Cut lists could be described as a sort of “reverse BOM”. They start with the topmost input material
which is then disassembled with the predefined cuts. The calculations and disassembly orders men-
tioned above are based on a cut list, which again consists of a number of n cuts.
The Softproviding Standard Cost Estimate (as a pre-calculation, push calculation) calculates the cut
list from the topmost input material down to the output materials with the aim of calculating them
on both quantity and value basis. The Softproviding MRP Calculation (push/pull) calculates the cut
list based on the needed requirements. The program aims to calculate the smallest quantity of input
material as possible that are needed to cover the requirements (optimization). The results of both cal-
culations may be updated into a manual calculation (SAP Standard costing). There, they serve to val-
uate the materials and may be used in subsequent processes.
The Purchasing Decision application supports the planner in the decision of whether to procure the
input/output materials externally or disassemble them in-house (make or buy). The calculation re-
sults may be defined as manual calculations and are available as basis for further calculations.
Disassembly orders are needed in order to collect materials (input and output) for disassembly process
entry. Disassembly orders are Softproviding Meat-specific production orders that are only used in Dis-
assembly. They collect the material costs that arise from disassembly inbounds and outbounds as
well as the labor costs needed or caused in Disassembly.
For further information on the above-mentioned calculations and disassembly orders, please refer to
the Disassembly user documentation
3 Configuration/Production
Menu Softproviding Meat > Production > Central Settings > Cross-Plant
This table is used for basic settings for the areas of Calculation and Disassembly. The most important
settings are:
— Units of measure (units)
— Units of measurer (weight)
— Price unit
— Unit calculation
Use
In calculations (Softproviding Meat Standard Cost Estimate and MRP Calculation) and in Disassem-
bly, the unit of measure (UoM) is called weight unit of measure. Examples for these units of measure
are the weight units kilogram (kg) or pound (lb). Further units of measure which may be used in par-
allel are the so-called double unit of measure and the UoM for the unit itself.
The double unit of measure (DUM) is not activated in Customizing. These settings are made in the
material master database. For further information please refer to the Disassembly user documenta-
tion.
The price unit specifies the number of UoMs to which the price refers. The price unit always refers to
the weight unit of measure.
The unit UoM may only be used if unit calculation is activated in this table.
Prerequisites
There are no prerequisites that must be fulfilled to be able to make entries in this table.
Activities/Recommendations
Make the necessary setting. None of the fields is defined as mandatory entry. In this table you may
make entries with respect to units of measure, for instance, entries on the weight unit of measure and
on the units unit of measure. These entries will then be transferred to the respective applications.
Note
Entries on the units of measures weight and units as well as on the price unit in this table may be overruled
with the settings in table Production > Central Settings > Plant.
3.1.1 Cross-Plant
Entries may be created by selecting the New Entries button.
Prerequisites
— The Use unit calculation indicator in this table was set.
— The Quantity (units) field in the material master database,
Disassembly tab, was selected.
Use
This unit of measure is used, among others, in the following mas-
ter data and applications:
— Cut (for input and output materials)
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Orders
Dependencies
The units UoM is determined according to the following sequence:
— Plant-dependent settings (table /SPMEAT/TC001W)
— General settings (table /SPMEAT/TC001)
— Units (= PC) is used if neither of the above-mentioned table
has any entry in this respect.
UoM (weight) The UoM (weight) unit of measure is available as unit of measure
in the Softproviding Meat calculations and disassembly orders:
Default settings
This unit of measure must be a weight unit of measure (e.g. kg,
ton). The input help (F4) therefore only provides weight units of
measure for selection.
Dependencies
The weight UoM is determined according to the following se-
quence:
— Plant-dependent settings (table /SPMEAT/TC001W)
— General settings (table /SPMEAT/TC001)
— Kilogram (kg) is used if neither of the above-mentioned ta-
bles has any entry in this respect.
Recommendation
Typically, the weight UoM is kilogram (kg) or pound (lb).
Price unit Definition
The price unit is the number of UoMs to which the price refers.
The price unit must always be seen in connection with the price.
Use
The price unit is used, among others, in the following master data
and:
— Cut
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Orders
Dependencies
The price unit UoM is determined according to the following se-
quence:
— Plant-dependent settings (table /SPMEAT/TC001W)
— General settings (table /SPMEAT/TC001)
Example
— Quantity (weight) input material = 100 kg
— Price = 2.00 Euro
Use
This unit is used as follows:
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
Default settings
The F4 input help provides time UoMs (e.g. min., hrs.) for selec-
tion.
Default Fixed Indicator Source Source for the fixed indicator in the cut.
Use
When creating a cut, the source for determining the fixed indica-
tor can be preset. The fields are located in the cut for each output
material in the views Material costs and Other costs.
Available values
— “A” = source A (material master - cross-plant)
— “-” = source B (material master - plant-dependent)
Note
The presetting can be changed in the cut.
Currency Definition
The currency is represented by a 3-digit currency key (e.g. EUR =
European euros; USD = US dollars). The amounts in the system
are kept in this currency.
Use
This currency is used as follows:
— Cut
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
The currency is used as default value for the creation of cuts and
in the calculations. This default value may be changes in the ap-
plication.
Default settings
The F4 input help provides all SAP Standard currencies for selec-
tion.
Dependencies
The currency is determined according to the following sequence:
— Plant-dependent settings (table /SPMEAT/TC001W)
— General settings (table /SPMEAT/TC001)
Use
If master data (cut list) or calculations (standard cost estimate
and MRP costing) are called up in the SAP-GUI, the screen is split
into two parts. The cut list is displayed on the left and the settings
and calculation results on the right. The width of the left screen
(cut list) can be adjusted by optionally entering a key in this field.
Use
The indicator can be used in MRP calculation.
Dependencies
This activation may later be set in the material master database,
Disassembly tab, for the desired material. In order to do so, the
Unit material field is selected, which will display the Unit UoM
field (e.g. PC = pieces).
Default settings
By default this indicator is not set.
Note
For unit calculation, not every material must be necessarily marked
as unit material. It makes sense, to mark only the primal cuts as unit
materials.
Do not show warning for Setting this indicator will prevent that a log is output for the fol-
movement data lowing calculations.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
Default settings
By default, this indicator is not set.
Plant, not plant group as de- This field is intended for a future release and does not have any
fault functionality in the current release.
Cut This field is intended for a future release and does not have any
functionality in the current release.
Cut list This field is intended for a future release and does not have any
functionality in the current release.
Cost determination The option selected here will determine which costs the external
input material will bear. Costs are displayed in the cost view.
Default settings
The following options may selected with cost determination for
external inputs (i.e. quantities of an external input material are
added in the disassembly process):
— determine only variable costs
— determine fixed and variable costs
— determine only fixed costs
— do not determine any costs
— Own costs from SAP costing
Price modification The option selected here will determine which costs are deducted
from the external input material. Costs are displayed in the cost
view.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
Default settings
The following options may be selected with cost determination
for external inputs (i.e. quantities of an external input material are
added in the disassembly process):
— deduct only variable costs from price
— deduct fixed and variable costs from price
— deduct only fixed costs from price
— deduct no costs from price
Cost group Entry of a key (max. 3-digit) uniquely identifying a cost group.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
Default settings
The following cost groups may be selected:
— FEK (production costs)
— FGK (production overhead)
— GK (overhead costs)
— MEK (direct material costs)
Dependencies
The table entries of customizing item Softproviding Meat > Produc-
tion > Master Data > Cost Group are maintained by Softproviding
and should only be changed after consultation with Softproviding
AG.
Menu Softproviding Meat > Production > Central Settings > Plant Group
Note
The table on work groups is intended for a future and is without functionality in the current release.
3.1.3 Plant
In the Implementation Guide, call menu item Plant for the plant-dependent settings as follows:
Menu Softproviding Meat > Production > Central Settings > Plant
This table is used for basic settings in the areas of Calculation and Disassembly. These settings are
made by plant. The most important settings are:
— Unit of measure (weight)
— Units of measurer (units)
— Price unit
— Optimization for calculations
— Cost views
Use
In calculations and in Disassembly, the unit of measure (UoM) in which data entry takes place is
called weight unit of measure. Typically, the unit of measure used here is the weight unit kilo (kg) or
pound (lb). Further units of measure which may be used in parallel are the so-called double unit of
measure and the UoM for the unit itself.
The double unit of measure (DUM) is not activated in Customizing. These settings are made in the
respective material master database.
The price unit specifies the number of UoMs to which the price refers. The price unit always refers to
the weight unit of measure.
In the Softproviding Meat calculations, an aggregated view on the costs situation may be called via
the cost views. The standard layouts used for this may be adjusted per customer in this table.
Prerequisites
There are no prerequisites that must be fulfilled to be able to make entries in this table.
Activities/Recommendations
Make the necessary setting. None of the fields is defined as mandatory entry. In this table you may
make entries with respect to units of measure, for instance, entries on the weight unit of measure
(disassembly UoM) and on the units unit of measure (disassembly unit UoM). These entries will then
be transferred to the respective applications
It is recommended to use plant-dependent entries for these units of measure if there are no existing
cross-plant entries available. If there are no entries made for either of the tables, the system will use
kg (kilogram) or PC (pieces) in the applications
Note
Entries on the units of measures weight and units as well as on the price unit in this table may be overruled
with the settings in table Production – Central Settings > Cross-Plant.
Use
This unit of measure is used, among others, in the following mas-
ter data and applications:
— Cut (for input and output materials)
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Orders
Default settings
This unit of measure must be a weight unit of measure (e.g. kg,
ton). The input help (F4) therefore only provides weight units of
measure for selection.
Dependencies
The weight UoM is determined according to the following se-
quence:
— Plant-dependent settings (table /SPMEAT/TC001W)
— General settings (table /SPMEAT/TC001)
— Kilogram (kg) is used if neither of the above-mentioned ta-
bles has any entry in this respect.
Recommendation
Typically, the weight UoM is kilogram (kg) or pound (lb).
Note
Instead of the plant-specific entries, a general setting may be made in
table Production – Central Settings > Cross-Plant.
Work. Time UoM This unit of measure is used as UoM for the calculation of working
times in calculations and disassembly processes.
Use
This unit is used as follows:
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Disassembly Orders
Default settings
From the F4 input help, time units (e.g. MIN, HRS) may be se-
lected.
Use
The currency is used as follows:
— Cut
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
Default settings
From the F4 input help, all currencies available in SAP Standard
are proposed for selection.
Dependencies
The currency is determined according to the following sequence:
— Plant-dependent settings (table /SPMEAT/TC001W)
— General settings (table /SPMEAT/TC001)
If both of the tables do not have an entry for the currency the cur-
rency of the company code is used.
Price unit Definition
The price unit is the number of units of measure to which the price
refers. The price unit must always be regarded in context with the
price.
Use
The price unit is used, among other, in the following master data
and applications:
— Cut
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Orders
Dependencies
The price unit is determined according to the following sequence:
— Plant-dependent settings (table /SPMEAT/TC001W)
— General settings (table /SPMEAT/TC001)
Example
— Quantity (weight) input material = 100 kg
— Price = 2.00 Euro
— Price unit = 5 kg
— Result: total value = 40 Euro
Note
Instead of the plant-specific entries, a general setting may be made in
table Production – Central Settings > Cross-Plant.
DAP UoM (units) If the following prerequisites are met the unit UoM is available as
independent unit of measure in the Softproviding Meat calcula-
tions and disassembly orders.
Prerequisites
— The Use unit calculation indicator in table /SPMEAT/TC001
was set.
— The Quantity (units) field in the material master database,
Disassembly tab, was selected.
Use
This unit of measure is used, among others, in the following mas-
ter data and applications:
— Cut (for input and output materials)
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Orders
Dependencies
The units UoM is determined according to the following sequence:
— Plant-dependent settings (table /SPMEAT/TC001W)
— General settings (table /SPMEAT/TC001)
Note
Instead of the plant-specific entries, a general setting may be made in
table Production – Central Settings > Cross-Plant.
Units rnd. The Units rounding parameter allows you to set whether, and if so,
how the rounding function for an entered quantity (in units) shall
be applied.
Use
This functionality is used among others in the following master
data and applications:
— Cut list
— Softproviding Meat Standard Cost Estimate
Default settings
The following rounding options are available:
— Round up (+)
— Round down (-)
— Round to the next whole number (x)
— No rounding (blank)
Background information
In the material master database ((Disassembly tab), a material
may be marked as unit material (Unit material field). In the
Softproviding Meat calculations as well as in the disassembly or-
ders the Quantity (units) field is ready to input a planned quantity
for the respective input or output material.
Example
If in Softproviding Meat MRP Calculation for material planning in
the disassembly order, a value of 9.6 is entered in the Quantity
(units) field and the rounding parameter is set to round to the next
whole number the quantity (units) is set to 10 after the entry is
confirmed with Enter.
Cut w/o routing – default If this indicator is set, the Cut without routing indicator in the cut
is checked by default.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
If this indicator is set, the cut will not use routings, meaning, no
other costs (i.e. labor costs) will be calculated for this cut.
Default settings
By default, this indicator is not set.
Note
In the cut, either a routing must specified or this indicator set.
Yield groups This field is intended for a future release and does not have any
functionality in the current release.
# Opt. (Mat.) This field is used to enter the optimization iterations (per mate-
rial). Values may range between 001 up to a maximum of 255.
Default settings
By default, this field is empty.
Note
Please not that a high number of iterations can have a negative influ-
ence on performance.
Note
In MRP Calculation, the current material stocks can be taken into ac-
count with the Read stock and Use stock function. If this function is
used, the Optimizer (Opt. (Mat.) and Opt (tot.) fields) should not be
set to active (i.e. value = 0), especially for small cut lists.
# Opt. (tot.) This field is used to enter the optimization iterations (total). Val-
ues may range between 001 up to a maximum of 255.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
Default settings
By default, this field is empty.
Note
Please note that a high number of iterations can have a negative in-
fluence on performance.
Note
In MRP Calculation, the current material stocks can be taken into ac-
count with the Read stock and Use stock function. If this function is
used, the Optimizer (Opt. (Mat.) and Opt (tot.) fields) should not be
set to active (i.e. value = 0), especially for small cut lists.
Master target calculation This setting determines which calculation is the leading calcula-
tion for disassembly orders.
Default setting
The following setting options are available:
— Target 2
— Target-plan
— Variance
Note
The cost view layout may be adjusted individually by copying the re-
port and appropriate assignments in this field.
Enhancement
Further options to influence the cost view are provided with the
following BAdI.
BAdIs
/SPMEAT/BADI_CTL_CVIEW
Method
CVIEW_REPORT_CALL
Cost view (DAO) In order to call the cost view in disassembly orders, report
/SPMEAT/R_CVIEW_ALL is used.
Note
The cost view layout may be adjusted individually by copying the re-
port and appropriate assignments in this field.
Enhancement
Further options to influence the cost view are provided with the
following BAdI.
BAdIs
/SPMEAT/BADI_CTL_CVIEW
Method
CVIEW_REPORT_CALL
Cut – NR no. This field is intended for a future release and does not have any
functionality in the current release.
CL - NumRangNo This field is intended for a future release and does not have any
functionality in the current release.
Double quantity – Rounding When calculating the schedule line quantity, rounding can be per-
formed automatically.
If this is the case, the quantity must be converted from the plan-
ning unit of measure (KG) to the schedule line unit of measure
(piece) and possibly rounded.
Standard settings
The following rounding options are available:
— No rounding
— Round up (+)
— Round down (-)
— Round to the next integer (x)
Complex Tree Iterations Over- Settings for this indicator and field can improve the performance
ride (indicator) of an MRP calculation. These settings are available as of release
v5.70.
Complex Tree Iterations
(field) Use
If this indicator is set, the program does not optimize the demand
for all cuts for which a material can be produced, but only for the
cut for which this material is the main material. An entry is then
made in the field Iter. Complex then has no effect.
Recommendation
If this optimization is not required (because the requirements of a
material are only to be covered from one cut), you should set the
indicator and the value in the field Iter. Complex to 0.
IBP integration active Indicator used to activate the IBP interface.
Use
If material assignments to the constraint have been made in the
cut list, this information (such as calculation number, material,
quantity) is made available in view /SPMEAT/V_IBPCO.
New sequence determination Sequence determination indicator.
(BETA)
Use
This indicator is a preliminary step for future developments in the
area of MRP Calculation. It is currently not intended for produc-
tive use. The indicator may only be set after consultation with
Softproviding.
Caution
Please do not set the indicator, it may lead to unexpected and un-
desired results in the calculation.
Menu Softproviding Meat > Production > Master Data > Cut
Examples
Typically, a separate material type is created for livestock and disassembly materials (e.g. ZVIE,
ZERL). This material type must then be entered in this table. Further examples for entries in this table
are:
— ROH
— HALB
Use
Materials which are created with a defined material type may be
used for the creation of cuts.
Materials for which the material type is not defined here may not
be used for the definition of cuts. In this case, an error message
would be displayed in the application.
Default settings
In the F4 input help, all defined material types are provided for se-
lection.
Values
The following inspections may be selected:
— Stock type: Output material = input material or without
stock type
— Material: All output materials set to ‘Fixed’
Note
The distribution of the material costs of an input material to the out-
put materials is carried out on the basis of fixed prices and equiva-
lence numbers. If, however, all output items of a cut are set to fixed
price, this may lead to inconsistencies within the calculation. There
must at least be one variable item (i.e. an item with an equivalence) so
the values to be distributed are correctly passed on to the outputs.
This applies both to material and labor costs.
Values
The following message types may be assigned:
— Default
— Information
— Warning
— Error
— Success (info W/o popup, or none
Example
The inspection “Material: Output material has a quotient of 0%” is
set to Error”.
Result
When the cut is saved an error message is displayed for those ma-
terials which do not have an entry in the Quotient in % field. In
this case saving is not possible.
Note
If this field is not selected, internal number assignment will be carried
out.
Note
Note that all intervals for the selected number range object are deleted in the target system first. After the
import, only the intervals you export are present. The number statuses are imported with their values at
the time of export.
In the Implementation Guide for the Softproviding Meat Customizing these menu items are called as
follows:
Menu Softproviding Meat > Production > Master Data > Cut List
Note
The output of warnings in the log can be switched off across plants in
Meat Customizing (IMG: Softproviding Meat > Production > Central
Settings > Cross-Plant). If the Do not display warnings for move-
ment data indicator is set here, warnings or information messages
that should actually be output on the basis of these settings for the
material status/cutting list check are switched off.
Recommendation
Softproviding recommends setting the planning strategy check to
E (Error) to alert the user to any errors when saving the MRP cal-
culation.
Use
These messages are displayed at the point of creation in the fol-
lowing applications:
— Standard Cost Estimate
— MRP Calculation
— Purchasing Decision
— Mass Calculation
Note
If this field is not selected, internal number assignment will be carried
out.
Note
Note that all intervals for the selected number range object are deleted in the target system first. After the
import, only the intervals you export are present. The number statuses are imported with their values at
the time of export.
The cost views give an overview of the cost structure for the selected calculation. In the above-men-
tioned applications, a cost view may be called on various levels. This allows you to compare costs
both at order level (all costs) and cut level for the individual output materials.
Important Note
These table entries are maintained by Softproviding AG and must not be changed without consulting
Softproviding.
Note
In Customizing, this field is only visible in the detail view.
Name (short) Freely selectable, 20-digit text for the short name of the cost
group.
Cost group type The cost group type specifies whether the costs in the cost view
of the application are to be collected or calculated.
Values
— Collected
— Calculated
Special types Only one cost group can be assigned to one of these special types
(radio button selection):
Note
These settings for the special types are made for technical reasons.
They are delivered by Softproviding and must not be changed.
Calculation sequence The entries made in this field per cost group are necessary for the
report structure.
Note
These settings are made for technical reasons. They are delivered by
Softproviding and must not be changed.
Output type The respective cost group is displayed with the output type speci-
fied here.
Values
— Costs
— Production depth
— Purchasing decision
— Blank
Use
The cost pools are used to display the disassembly labor costs in the calculations. In the applications
(Softproviding Standard Cost Estimate, MRP Calculation and Disassembly Order Calculation) they
are displayed in every cut (Other Costs tab).
Prerequisites
The prerequisites that must be given in order to calculate the labor costs in the application (and, con-
sequently to display them in the cost pools) are dealt with in detail in the Softproviding Meat user
documentation Disassembly.
Table Fields
Field Name Description
Cost pool A cost pool is defined by a key with a maximum of 3 digits. Al-
lowed values are C01 to C99. Cost pools are used to represent labor
costs.
Use
Cost pools are displayed via cut list in the various applications of
the calculation (Standard Cost Estimate, MRP Calculation and
Disassembly Order Calculation) at cut level. In the cut list, the
cost pool keys are replaced by the respective long text.
Examples
— C01 = Costs of slaughtering
— C02 = Costs of primal cutting
— C03 = Costs of deboning
Use
In this screen area you define the cost pools and assign cost
groups for the disassembly process calculation. If you don’t want
to make any assignments, the respective fields may remain
empty. The long text maintained here is displayed in the tabs of
the cut list.
Examples
— Costs of slaughtering
— Costs of primal cutting
— Costs of deboning
Note
In the application, all defined cost pools are always displayed at all
levels even if the cost pool does not have any own labor costs at a cer-
tain cut level. Cost pools are required to be represented at all cut levels
due to cost rollup.
Long text Freely selectable, 40-digit text for the long name of the cost
group. This name is displayed in the cost views of the applica-
tions.
Short text Freely selectable, 20-digit text for the short name of the cost
group.
Cost group An entry in this fields ensures that the costs are displayed in the
Variable / Internal cost view.
Examples
— Disassembling
— Cooking
— Defrosting
Here, an entry may be made per cost pool. Together with the de-
fined cost center (see next field), this entry will be used as default
value in the Softproviding Meat calculations if they contain man-
ually defined rates for the calculation of labor costs. This done in
the calculations in the Other Costs tab with the Fixed indicator.
Note
This default assignment may also be made directly at material level In
the material master Disassembly view.
Dependencies
An entry only makes only sense together with a cost center.
Values
All defined activity types are displayed in the F4 input help.
Cost center Definition
A cost center is an organizational unit within a controlling area. It
represents a clearly delimited location where costs occur.
Dependencies
An entry only makes only sense together with the activity type.
Values
All defined cost centers are displayed in the F4 input help.
Table Fields
Field Name Description
Controlling area Definition
The controlling area represents the topmost organizational unit in
Controlling.
Activity
In the input help, select the desired controlling area.
Activity type If a cost pool should be able to display the labor costs in the calcu-
lation (based on the cut assigned in the routing), the activity
types relevant to the cost pool must be assigned here.
Example
For material 2002 (pig half) a routing with the operation Slaugh-
tering was created and assigned to the respective cut. Activity
type 420 (disassembly personnel) was assigned to the routing op-
eration. The activity type is now assigned to cost pool CO1
(Slaughtering) in the same customizing menu item. In the calcula-
tion, the labor costs for slaughtering will then be displayed in the
cost pool for slaughtering.
Values
Al defined activity types are displayed in the F4 input help.
Activity
In the input help, select the desired activity type.
Use
A disassembly process is an organizational process in Slaughtering and Disassembly. Disassembly
processes are mandatory for the creation of cuts.
Note
Disassembly processes may already be assigned in the material master database. The disassembly process
is mandatory if you want to create a cut and it is transferred according to the default values in the material
master database.
Examples
— Cutting halves
— Primal cutting
— Deboning
Table Fields
Field Name Description
Plant The plant is a company’s production site.
Disassembly process A disassembly process is an organizational process in Slaughter-
ing and Disassembly. Disassembly processes are defined by speci-
fying a key with a maximum of 4 digits.
Use
When a disassembly order is created, the assigned disassembly
processes are proposed for selection.
Activities
Disassembly processes are required for the creation of cuts and
are transferred to the cuts according to the default values in the
material master database. For this reason, do define the needed
disassembly processes in Customizing.
Examples
— SCHL = Slaughtering
— GROB = Primal cutting
— FEIN = Deboning
Text Description of a disassembly process. This text is displayed in the
applications.
Profit Center Definition
A profit center is an organizational unit in accounting that re-
flects the organization for the purpose of internal control. Assign-
ing a profit center to a disassembly process is optional. However,
the following should be kept in mind:
Note
When you want to create a disassembly order you should make sure
that the selected disassembly processes are assigned to the same
profit center. Otherwise the order cannot be created. If different dis-
assembly processes (e.g. primal cutting, deboning) are assigned to dif-
ferent profit centers, these disassembly processes cannot be used for
the same disassembly order. Using disassembly processes without
profit center, however, does not prevent the creation of a disassembly
order if, also, disassembly orders with profit center are selected.
Note
Assigning a profit center to a disassembly process is not necessarily
required in order to create a profit center document. If no profit center
is assigned to disassembly processes (i.e. no entry is made in this ta-
ble), the dummy profit center will be written to the Profit Center field
when the profit center document is created, provided Profit Center Ac-
counting is activated. The Partner Profit Center field which is kept in
Recommendation
From a process point of view, Softproviding recommends to as-
sign the desired profit center to each disassembly process in this
table.
Adjustment options
If, from a process or company point of view, it is not possible or
desired to assign the disassembly order to the profit centers as de-
scribed above, there is an option in SAP Standard with which to
represent the internal relationships between profit centers:
— Maintaining the SAP table with transaction 0KEK (EC-PCA
Account Assignment).
Significance
If a cut list contains multiple cuts and different disassembly pro-
cesses, when the disassembly order is created, the selection of the
disassembly orders decides which cuts are relevant to the order
and thus for the data entries on this order.
Order types The order type is the key that distinguishes orders in terms of
their use. The order type is used to define parameters that influ-
ence the execution of the order.
Use
You can use different order types for disassembly process orders
by assigning them to the disassembly processes here. If no order
type is stored here for the plant and disassembly process, the or-
der type selected in the general settings for the disassembly pro-
cess is determined when disassembly process orders are created.
Please refer to chapter 3.12.1 (General Settings).
Use
In the disassembly order the disassembly order group is displayed at material level. It is available as
a selection criterion in Disassembly Entry (inbound and outbound) as well as in the report for the av-
erage price determination.
Note
Assignments to a disassembly process group (Disassembly Process view) are made in the material master
database.
Examples
— Halves
— Shoulder
— Loin
Table Fields
Field Name Description
Disassembly proc. grp. The disassembly process group collects materials from the point
of Disassembly. The group is defined by a key with a maximum of
3 digits.
Use
Prerequisites
Use
In the material master view Disassembly, an assignment to a loss type may be made. This allows you
to display losses occurring during disassembly in the disassembly order.
Examples
— Cooking losses
— Disassembly losses
Table Fields
Field Name Description
Loss type A loss type is defined by a 1-digit key.
Use
These losses are shown in the disassembly order (Controlling tab).
Note that these are target losses.
Prerequisites
Loss types were assigned in the material master tab Disassembly .
The display of loss types must also be specifically allowed which
is done in Disassembly Order Customizing (for details see the re-
spective chapter further down).
Examples
— K = Cooking losses
— Z = Disassembly losses
Text Description of the loss type.
Text (HTML) Description of the loss type. This description is HTML enabled.
In the following section, not all fields of these standard tables are described since they are not all
relevant for the respective applications and therefore do not require any mandatory settings to be
made.
In the Implementation Guide, call menu item Define Order Types as follows:
Menu Softproviding Meat > Production > Execution > SAP Standard > Pro-
duction Order
or
Production > Shop Floor Control > Master Data > Order > Define Or-
der Types
Transaction OPJH
You may create new entries by selecting the New Entries or Copy as… button.
Table Fields
Field Name Description
Order category The order category defines the technical properties of an order.
Note
By default, order category 10 (PPS-Production Order) is used for dis-
assembly orders.
Order type The order type is the key which differentiates the orders with re-
gard to their use. The order type is assigned to an order category.
Recommendation
Softproviding recommends to use your own order type (e.g. ZPP1)
for disassembly orders.
Procedure
Use entry PP01 as copy model. For disassembly orders, this new
entry is typically created as order type ZPP1. For disassembly or-
ders in DPS you would usually use a different order type of your
own, for instance, ZDP1.
Dependencies
In a further step, this order type is assigned to the order category
disassembly process. This setting is made in the Softproviding
Meat Customizing under Logistic > Process Data Acquisition > Or-
ders > Order Types.
Settlement profile Use
The settlement profile assigned here will be transferred to the set-
tlement rule of the disassembly process. This rule is necessary to
be able to carry out closing work on the disassembly order.
Non-ABAP software components are NOT qualified by SAP, they are provided directly by Softproviding (via the
Softproviding Extranet). Customers who install and operate these components do so on their own responsibility. They
are not part of the SAP license agreement but are still maintained by Softproviding.
For information on further setting options this customizing step please refer to the SAP Standard doc-
umentation.
Menu Softproviding Meat > Production > Execution > SAP Standard > Pro-
duction Order
or
Production > Shop Floor Control > Master Data > Order > Define Or-
der-Type Dependent Parameters
Transaction OPL8
You may create new entries by selecting the New Entries or Copy as… button.
Table Fields
Field Name Description
Plant The plant is a company’s production site.
Order type The order type is the key that differentiates the orders with re-
gard to their use.
Procedure
Use entry 0001/PP01 (plant / order type) as copy model, then as-
sign the order type for the disassembly orders.
For information on further setting options on this customizing step please refer to the appropriate
SAP Standard documentation.
In the Implementation Guide, call menu item Define Default Values as follows:
Menu Softproviding Meat > Production > Execution > SAP Standard > Pro-
duction Order
or
Production > Shop Floor Control > Operations > Task List Selection
Transaction OPJG
Select the desired plant as work area and confirm with Enter.
You may create new entries by selecting the New Entries or Copy as… button.
Table Fields
Field Name Description
Plant The plant is a company’s production site.
Order type The order type is the key which differentiates the orders with re-
gard to their use.
Procedure
For your copy, order type PP01 can be used as template, and the
appropriate order type for the disassembly orders can be assigned.
Note
It is important that the value 0010 is stored in the Operation field.
Use the entries from copy model PP01 for the field listed below. Verify whether these entries fit your
processes. For a detailed description of the fields, please use the F1 help function.
Fields
— Control key
— Task list unit
— Usage of the plan
— Denominator for the conversion into the base units of measure
— Counter for the conversion into the base units of measure
— Base quantity
— Work center
— Operation plus short text for the operation
— Purchasing group
— Material group
Menu Softproviding Meat > Production > Execution > SAP Standard > Pro-
duction Order > Define Scheduling Parameters for Production Orders
or
Production > Shop Floor Control > Operations > Scheduling > Define
Scheduling Parameters for Production Orders
Transaction OPU3
You may create new entries by selecting the New Entries or Copy as… button.
Table Fields
Field Name Description
Plant The plant is a company’s production site.
Order types The order type is the key which differentiates the orders with re-
gard to their use.
Recommendation
Use entry 0001/PP01 (plant / order type) as copy model, then se-
lect the order type for the disassembly orders.
Adjust dates This setting determines if and how the system adjusts the basic
dates and the dependent requirements dates of an order when it is
scheduling.
Recommendation
Use the option Adjust basic dates, adjust dependent requirements to
operation date.
Scheduling type The scheduling type is the key which defines fine-scheduling.
Recommendation
Use backwards scheduling.
For information on further setting options this customizing step please refer to the appropriate SAP
Standard documentation.
In the Implementation Guide, call menu item Create Settlement Profile as follows:
Menu Controlling > Product Cost Controlling > Cost Object Controlling >
Product Cost by Period > Period-End Closing > Settlement > Create
Settlement Profile
Transaction OPKT
You may create new entries by selecting the New Entries or Copy as… button.
Table Fields
Field Name Description
Settlement profile In the settlement profile the controlling parameters for settle-
ment are defined. The settlement profile is a precondition for en-
tering later, in the order master record, a settlement rule for a
sender. The settlement profile is drawn from the order type in the
settlement profile.
Recommendation
Select a name for the new entry, e.g. ZPP1 (disassembly order).
To be settled in full This indicator controls whether actual costs or costs of sales must
settled.
Recommendation
Select To be settled in full. This is the standard setting. If you try
to close the object or set the delete flag, an error message is dis-
played if the object’s balance is not zero.
Sourced structure The source structure is used to settle the costs incurred on the
sender (the disassembly order) to different receivers (order items)
depending on the cost element.
Note
No entry must be made in this field. The source structure is assigned
in the Softproviding Meat Customizing.
Max.no.dist.rls Maximum number of distribution rules. The value entered here is
the maximum number of possible distribution rules per settlement
rule. You can only settle with as many receivers as there are dis-
tribution rules.
Note
Enter the highest possible value (999).
100% Validation Indicator which controls the percentage validation of the settle-
ment rule for periodic settlement.
% settlement If you set this indicator you may define distribution rules in the
settlement rule for a percentaged settlement of the costs.
Menu Production > Shop Floor Control > Master Data > Routing Data
Transaction OPEC
You may create new entries by selecting the New Entries or Copy as… button.
Table Fields
Field Name Description
Field key The field key is a key which defines the key words (field names)
for the user fields.
Use
The key defined here is entered in Customizing table General Set-
tings (Softproviding Meat > Production > Execution > Disassembly
Orders).
Example
Field key ZSPMM
Field key description Description of the field key
Example
Softproviding Meat Management
Text (20) empty
Text (10) Descriptive examples
Cut number
Quantity Descriptive examples
Operation quantity
Parameter-ID Dependencies
Parameter IDs are defined in Customizing under Formula Parame-
ters.
Examples
ZVGMGY
Value empty
Date empty
Check box empty
Together with settings for activity and price planning, the labor costs are calculated. During this plan-
ning (e.g. fixed and variable costs), the settings for the combination of cost center and activity type
are made.
Note
In Customizing, own formulas and formula parameters may be defined, the predefined keys and parame-
ters provided by SAP can be used. Master data (e.g. routing, activity, and price planning) are not described
in this configuration guide.
For details on these setting options or examples, please refer to the chapters “Disassembly Orders” and
“Master Data” in the Disassembly user guide.
In the Implementation Guide, the tables for formulas, formula parameters and standard value keys
are called as follows:
Menu Production > Shop Floor Control > Operations > Scheduling
Transactions OPK2 (Formula parameters)
OPK3 (Formulas)
OPJQ (Standard value keys)
Menu Softproviding Meat > Production > Execution > SAP Standard > Con-
trolling
or
Controlling > Cost Center Accounting > Master Data > Activity Types
Transaction KL01 und KL02 (creating and changing)
Activity types may be created and changed using the above-mentioned menus and transactions.
Activity types are SAP Standard master data. For information on the setting options for these master
data, please refer to the appropriate SAP Standard documentation.
Menu Controlling > Product Cost Controlling > Cost Object Controlling >
Product Cost by Order > Period End Closing > Settlement
Transaction OKEU
You may create new entries by selecting the New Entries or Copy as… button.
The source structure is used to settle the costs incurred on the sender (the disassembly order) to dif-
ferent receivers (order items) depending on the cost element. After the structure is created it is as-
signed in Softproviding Meat Customizing accordingly (Production > Execution > Disassembly Orders >
Plant-Dependent Settings).
Note
The source structure must not be defined in the settlement profile.
It is highly recommended to create an assignment for the material costs and an assignment for the labor
cost, so these costs may be converted separately into equivalence numbers (also see the example in the
“Period-End Closing” chapter in the Disassembly user documentation).
Menu Controlling > Product Cost Controlling > Cost Object Controlling >
Product Cost by Order > Period End Closing > Variance Calculation
Transaction OKV6
You may create new entries by selecting the New Entries or Copy as… button.
The target cost version is prerequisite if you want determine variances within the framework of pe-
riod-end closing works. Target cost version 0 (target costs for total variances) must be assigned a sep-
arate variance variant for disassembly orders. The variance variant is also created under the Period-
End Closing menu item (transaction OKV6).
Menu Controlling > Product Cost Controlling > Cost Object Controlling >
Product Cost by Order > Period End Closing > Variance Calculation
Transaction OKV1
You may create new entries by selecting the New Entries or Copy as… button.
Variances can only be determined for orders for which a variance key was entered. For this a variance
key is defined in Softproviding Meat Customizing (Production > Execution > Disassembly Orders >
Plant-Dependent Settings).
If you want to assign a plant in the planning scenario, material requirements planning must be acti-
vated for this plant. The planning scenario is needed to start the Long-Term Planning Calculation. If
the indicator is activated, materials requirements planning may be carried out as total planning or as
single-item, multi-level planning.
Menu Production > Production Planning > Demand Management > Planned
Independent Requirements > Define Versions of Planned Independent
Requirements
Transaction OMP2
If you want to assign a plant in the planning scenario a planned independent requirements planning
version must be assigned. This version is, for one, needed in order to simulate material requirements
planning within the framework of Long-Term Planning Calculation. SAP provides versions of their
own. For long-term planning, a separate Z version should be created.
Examples
Language EN
Version Z1
Version text Long-term planning
In the Implementation Guide, call menu item Define Selection Rules as follows:
The selection rules delivered by SAP are sufficient. Creating new rules of your own is possible but not
required if you want to carry out Long-Term Planning Calculation. If you want to define your own
selection rules, you need to make sure that in the Selection Horizon only the Interval w/o limits is set.
Menu Softproviding Meat > Production > Product Cost Planning > Standard
Cost Estimate > General Settings
This table is used to configure basic settings for the Softproviding Meat Standard Cost Estimate.
These settings are plant-independent.
Use
Here, default values for, among others, the price source and the calculation variant are defined. In
Standard Cost Estimate the entry in the prices source serves as default value for the valuation of ma-
terials procured externally.
In the application, the calculation variant is used to update the calculation data to an SAP Standard
costing (calculation without quantity structure).
An update to material master price fields (for instance, periodically to the standard price) is also pos-
sible. After the update, these results are available for subsequent applications (e.g. product calcula-
tion).
Activities
Make the desired settings. None of the fields is defined as mandatory entry.
Table Fields
Entries may be created by selecting the New Entries button.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Long-Term Planning Calculation
— Softproviding Meat Disassembly Calculation
Examples
— Standard price
— Planned price 1
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
Recommendation
In the calculations this field is mandatory. It is therefore recom-
mended to define default values. In Product Cost Planning (SAP
Customizing, transaction OKKN), separate calculation variants
may be created.
MM calculation type This setting defines how the master model (MM) is used. “Master
model” is a term that is used for the price strategy function in
Standard Cost Estimate. This function allows you to change the
cost calculation of price strategy-relevant materials. A material in
a cut list is price strategy-relevant if it occurs in more than one
cut.
Use
— Softproviding Meat Standard Cost Estimate
Values
The following settings are possible:
— Use for update only (material costs only)
Prices are only changed when they are updated to SAP
Standard. The calculation itself remains unchanged.
— Replace and recalculate (material costs only)
Prices in the calculation are recalculated and adjusted.
— Replace and recalculate (material costs and labor costs)
Prices in the calculation are recalculated and adjusted.
Use
To prevent a user from having to run the Calculate function more
than once in the calculation in order for the program to correctly
determine and distribute prices, entries can be made in this field.
The numerical values 1 - 255 are allowed for input. An entered
value defines the number of additional calculation runs. By de-
fault the field is empty. This setting is optional.
Note
Entries in this field should only be made if the check of the cut list and
the standard cost estimate has shown that multiple calculation is nec-
essary in order to arrive at correct calculation and distribution re-
sults. Since an entry in this field also has an influence on the perfor-
mance, this setting should be chosen carefully.
Use
— Softproviding Meat Standard Cost Estimate
Use description from cut list The description of the cut list (long text) is passed on to this field
as default when it is activated.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Long-Term Planning Calculation
— Softproviding Meat Disassembly Order
Note
Without a default value, the Description field in the calculation must
be filled since it is mandatory.
Dependencies
As to the default values, there are separate setting options for the
applications Standard Cost Estimate, MRP and Long-Term Plan-
ning Calculation as well as for Disassembly Order.
Recommendation
Check this indicator.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
Background information
The assignment of a material to an origin group is done in the ma-
terial master, Calculation 1 tab. The information on the updated
origin group is displayed in the calculation without quantity
structure (transaction KKPBN) under Itemization.
Dependencies
This field is only relevant in the context with the updating of cal-
culation results to an SAP Standard calculation.
Values
— Input material
— Output material
Planned price 1 The entry in this field defines from which source to determine the
price for the plan 1 calculation. These costs are displayed in the
cost view of the calculation.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
Dependencies
As to the default values, there are separate setting options for the
applications Standard Cost Estimate, MRP Calculation and Disas-
sembly Order.
Menu Softproviding Meat > Production > Product Cost Planning > Standard
Cost Estimate > Number Ranges: Calculation Number
In this step, the number range for number range object /SPMEAT/CN (Post-Production Yield Calcu-
lation) is defined. After the IMG activity was started, a new entry may be made using the buttons
Intervals and Add interval.
Table Fields
Field Name Description
No. This number uniquely identifies a numbers range interval within
an object or sub-object.
From number 0000000001
To number 9999999999
Current number For internal numbers ranges the current number field shows the
number that assigned last.
Ext This indicator determines whether this is an external or internal
numbers range interval.
Note
If this field is not selected, internal number assignment will be carried
out.
Note
Note that all intervals for the selected number range object are deleted in the target system first. After the
import, only the intervals you export are present. The number statuses are imported with their values at
the time of export.
Menu Softproviding Meat > Production > Product Cost Planning > Purchas-
ing Decision > General Settings
As to data update, there is currently only one setting to be made in this table. These settings are plant-
independent.
Use
This setting enables the update of the calculation results (quantities and values) to SAP Standard
tables (transaction KKPBN; calculation without quantity structure = manual calculation). After the
update, these results are available for subsequent calculations (e.g. product calculation).
Activities
Make the desired settings. None of the fields is defined as mandatory.
Table Fields
Entries may be created by selecting the New Entries button.
Use
— Softproviding Meat Standard Cost Estimate
Menu Softproviding Meat > Production > Product Cost Planning > Purchas-
ing Decision > Number Ranges: Purchasing Decision Number
In this step, the number range for the number range object /SPMEAT/MC (Purchasing Decision Num-
ber) is defined. After the IMG activity was started, a new entry may be made using the buttons Inter-
vals and Add interval.
Table Fields
Field Name Description
No. This number uniquely identifies a numbers range interval within
an object or sub-object.
From number 0000000001
To number 9999999999
Current number For internal numbers ranges the current number field shows the
number that assigned last.
Ext This indicator determines whether this is an external or internal
numbers range interval.
Note
If this field is not selected, internal number assignment will be carried
out.
Note
Note that all intervals for the selected number range object are deleted in the target system first. After the
import, only the intervals you export are present. The number statuses are imported with their values at
the time of export.
Menu Softproviding Meat > Production > Product Cost Planning > Mass
Calculation > General Settings
Use
There are currently two cross-plant settings to be made in this table. The selection of the calculation
category determines which kind of calculation will be used in the Mass Calculation application,
whereas the second setting option enables the update of the calculation results in SAP Standard ta-
bles. After the update, these results will be available for subsequent applications (e.g. product calcu-
lation).
Table Fields
Entries may be created by selecting the New Entries button.
Values
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
Use
Mass Calculation allows you to create multiple calculations in one
go. These calculations may then be called via the Mass Calcula-
tion functionality or via the respective application (MRP-Calcula-
tion or Standard Cost Estimate).
Central update not allowed Check this field if you do not want the data to be updated to a unit
cost estimate. The respective functionality will then not be avail-
able in the application.
Use
This setting enables the update of the calculation results (quanti-
ties and values) to SAP Standard tables (transaction KKPBN; cal-
culation without quantity structure = manual calculation). After
the update these results are available for subsequent calculations
(e.g. product calculation).
Menu Softproviding Meat > Production > Product Cost Planning > Mass
Calculation > Number Ranges: Mass Calculation Number
In this step, the number range for the number range object /SPMEAT/MS (mass calculation number)
is defined. After the IMG activity was started, a new entry may be made using the buttons Intervals
and Add interval.
Table Fields
Field Name Description
No. This number uniquely identifies a numbers range interval within
an object or sub-object.
From number 0000000001
To number 9999999999
Current number For internal numbers ranges the current number field shows the
number that assigned last.
Ext This indicator determines whether this is an external or internal
numbers range interval.
Note
If this field is not selected, internal number assignment will be carried
out.
Note
Note that all intervals for the selected number range object are deleted in the target system first. After the
import, only the intervals you export are present. The number statuses are imported with their values at
the time of export.
Menu Softproviding Meat > Production > Material Requirements Planning >
Long-Term Planning Calculation > Cross-Plant Settings
This table is used to configure basic settings for Long-Term Planning Calculation (LTP). These set-
tings are cross-plant.
Use
Long-Term Planning calculation carries out a mid- to long-term planning. This planning activity is
only simulated, meaning it usually has no influence on operative planning.
Carrying out a long-term planning calculation hardly differs from running an MRP calculation. Both
calculations carry out a quantity- and value-based calculation of the cut list. It is the general objective
of both calculations to optimize the needed input quantities with which the desired requirements may
be covered. Due to its advanced requirement settings, Long-Term Planning Calculation allows to per-
form a more differentiated analysis.
Prerequisites
Prerequisites in the application
— Cut list was created
— Planning scenario was created
Prerequisites in Customizing
— Settings for material requirements planning per plant were made (Softproviding-Meat-Cus-
tomizing)
— A planned independent requirements version was created (SAP-Customizing)
Table Fields
Entries may be created by selecting the New Entries button.
Use
The order profile is needed in order to create planned orders when
the long-term planning calculation is released.
Background information
The profile assigned here can no longer be changed in the applica-
tion. Without an assignment made in Customizing, this field is
mandatory in the application. If you want to be able to select an
order profile in the application, do not define one here.
Default settings
There are no order profiles provided with the SAP Standard deliv-
ery.
Recommendation
Assign profile LA (warehouse order). This profile has the correct
parameters for this process.
Update allowed? Select this field if you want to allow the calculation data to be up-
dated in an SAP Standard unit cost estimate. The respective func-
tionality will then be available in the application. Update parame-
ters will be displayed.
Calc. variant The variant assigned here will be used as default value for the cal-
culation variant. This variant is required if you want to update the
data from the LTP in an SAP Standard calculation (calculation
without quantity structure; transaction KKPBN). This default
value may be changed in the application.
Recommendation
In the calculations this field is mandatory. Defining a default
value is therefore recommended. You can define your calculation
variants in Product Cost Planning (SAP Customizing, transaction
OKKN).
Source: origin The origin group serves to control materials the costs of which are
updated under the same cost element separately for controlling
reasons.
Use
The costs calculated in Long-Term Planning Calculation may be
passed on to the calculation without quantity structure (update),
whereby either the origin group of the output materials or the
origin group of the input materials (input material out of which
the output material is cut) is transferred.
Background information
The assignment of a material to an origin group is undertaken in
the material master, Calculation 1 tab. The information on the up-
dated origin group is displayed in the calculation without quantity
structure (transaction KKPBN) under Itemization.
Dependencies
This field is only relevant in the context with the updating of cal-
culation results to an SAP Standard calculation.
Values
— Input material
— Output material
Source: plan/target1 The entry in this field defines from which source to determine the
price for the plan 1 calculation. These costs are displayed in the
cost view of the calculation.
Note
Without a previously defined default value, the Description field in
the calculation must be filled since it is mandatory.
Recommendation
Check this field.
Menu Softproviding Meat > Production > Material Requirements Planning >
Long-Term Planning Calculation > Plant-Dependent Settings
This table is used to make plant-dependent settings for Long-Term Planning (LTP) with regard to the
requirement determination type.
Table Fields
Entries may be created by selecting the New Entries button.
Values
The following types of requirement determination are provided
for selection:
— Available quantity (negative)
— Total dependent requirements
— Total order reservations
— Total dependent requirements and order reservations
Caution
Do only use entries of type Total requirements and Total receipts and
requirements in Long-Term Planning Calculation. All of the other
selection options mentioned above are only shown for reasons of
compatibility and should not be used. This presets may be changed
in the header of the calculation.
Do not create purchase requi- This field is only relevant for purchase requisitions. Since no pur-
sition chase requisition can be created in LTP, this field has no function
and can be ignored.
1 planned order per calcula- If this indicator is set, only 1 planned order is created for the
tion instead of 1 PO per disas- whole calculation once it is released (instead of 1 planned order
sembly process. per disassembly process). If the indicator is not set, a planned or-
der is created for each disassembly process.
1 purchase requisition per cal- This field is only relevant for purchase requisitions. Since no pur-
culation instead of one PR per chase requisitions can be created in LTP, this field has no function
material and can be ignored.
Document type This field is only relevant for purchase requisitions. Since no pur-
chase requisitions can be created in LTP, this field has no function
and can be ignored.
Item category This field is only relevant for purchase requisitions. Since no pur-
chase requisitions can be created in LTP, this field has no function
and can be ignored.
Copy basic dates from plan- If this indicator is set, start and end dates from the planning sce-
ning scenario nario (fields Planned independent requirements from … to …) are
copied to the application. If these fields, however, are empty in
the planning scenario, the start and end dates fields in LTP are
filled with the current date.
Automatically adapt key date In Long-Term Planning Calculation, the fields Basic start date and
to basic dates Basic end date are filled according to the scheduling parameters.
The Key date field which is used for the determination of the cur-
rent equivalences, prices, cost data and fixed indicator can be con-
figured so that it adapts to the dates in the basic start and basic
end date fields.
If this indicator is not set, entries for the Key date field are inde-
pendent of the fields Basic start date and Basic end date.
If the indicator is set, the key date will always reflect the basic
dates. If the basic dates are changed, they key date is adjusted au-
tomatically if it lies outside the dates.
Recommendation
If you do not want the key date to adapt (even in exceptional
cases), the indicator should not be set
Note
Apart from Long-Term Calculation, this indicator is also used in:
— MRP Calculation
— Disassembly Order calculation
This indicator was integrated under the customizing items of these
calculations.
Menu Softproviding Meat > Production > Material Requirements Planning >
Long-Term Planning Calculation > Number Ranges: Long-Term Plan-
ning Calculation Number
In this step, the number range for the number range object /SPMEAT/CS (Long-Term Planning Cal-
culation Number) is defined. After the IMG activity was started, a new entry may be made using the
buttons Intervals and Add interval.
Table Fields
Field Name Description
No. This number uniquely identifies a numbers range interval within
an object or sub-object.
From number 0000000001
To number 9999999999
Current number For internal numbers ranges the current number field shows the
number that assigned last.
Note
If this field is not selected, internal number assignment will be carried
out.
Note
Note that all intervals for the selected number range object are deleted in the target system first. After the
import, only the intervals you export are present. The number statuses are imported with their values at
the time of export.
Menu Softproviding Meat > Production > Material Requirements Planning >
MRP Calculation > General Settings
Table
This table is used to configure basic settings for Softproviding MRP Calculation. These settings are
plant-independent.
Use
In this table presets for the planned order profile, for the price source and for the calculation variant
and other items are made.
The planned order profile serves to create the planned order. The entry for the price source is used as
a preset for the valuation of materials procured externally. The calculation variant is used to update
calculation data in a SAP Standard calculation (calculation without quantity structure). For the pur-
pose of valuation, these data may be updated to the material master price fields (e.g. periodically in
the standard price).
Prerequisites
There are no prerequisites that must be fulfilled to be able to make entries in this table.
Standard Settings
Order Profiles
In the SAP Standard delivery, order profiles are preset. The profile defines the order type, the procure-
ment type, the special procurement type and the account assignment category. The profiles are de-
fined in Material Requirements Planning Customizing.
Price Sources
In the SAP Standard delivery, price sources are preset. Furthermore, the following Softproviding
Meat-specific price sources are available:
— General view (material master tab Disassembly)
— Single plant view (material master tab Disassembly)
— Default from cut list
— Manual entry
— MPD market price (net)
— MPD market price (gross)
Calculation Variants
Calculation variants do come with the SAP Standard delivery. A calculation variant comprises all
controlling parameters for the calculation. These profiles are defined in Product Cost Controlling Cus-
tomizing.
Activities
— Check the order profiles included in the SAP Standard delivery. If necessary, create new order
profiles.
— Check the calculation variants included in the SAP Standard delivery. If necessary, create new
order profiles.
Table Fields
Entries may be created by selecting the New Entries button.
Use
The order profile is needed in order to create planned orders when
the long-term planning calculation is released. The planned order
may then be converted to disassembly orders in the application.
Recommendation
Assign profile LA (warehouse order). This profile has the correct
parameters for this process.
Price source The price source defined here is used as default value in MRP Cal-
culation. In the calculation, the price source is relevant for all ma-
terials with the procurement types external procurement and both
procurement types (external procurement and in-house produc-
tion). The value defined here may be changed per input material
in the calculation. The price source provides information on the
origin of the price.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
Examples
— Standard price
— Planned price 1
Dependencies
As to these default values, there are separate settings for the ap-
plications mentioned above.
Use description from cut list The description of the cut list (long text) is passed on to this field
as default when it is activated.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
Recommendation
Check this indicator.
Update in MRP calculation al- Select this field if you want to allow the calculation data to be up-
lowed? dated in an SAP Standard unit cost estimate. The respective func-
tionality will then be available in the application. Update parame-
ters will be displayed.
Note
In SAP Standard Customizing you may amend message KK 664
(Fixed price/value exceeds total price/value) to your needs. This is
necessary if a standard cost estimate or an MRP calculation is up-
dated in a unit cost estimate and you want to update negative calcu-
lation results. If you want to allow negative results (e.g. negative la-
bor costs, whereby the balance of positive material costs and nega-
tive labor costs is greater than zero), this message KK 664 must be
set to W or I (warning or information).
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Calculation
Recommendation
In the calculations this field is mandatory. It is therefore recom-
mended to define default values. In Product Cost Planning (SAP
Customizing, transaction OKKN), separate calculation variants
may be created.
Source: origin The origin group serves to control materials the costs of which are
updated under the same cost element separately for controlling
reasons.
Background information
The assignment of a material to an origin group is undertaken in
the material master, Calculation tab. The information on the up-
dated origin group are displayed in the calculation without quan-
tity structure (transaction KKPBN) under Itemization.
Dependencies
This field is only relevant in the context with the updating of cal-
culation results to an SAP Standard calculation.
Values
— Input material
— Output material
Planned price 1 The entry in this field defines from which source to determine the
price for the plan 1 calculation. These costs are displayed in the
cost view of the calculation.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Disassembly Order
As to the default values, there are separate setting options for the
applications Standard Cost Estimate, MRP Calculation and Disas-
sembly Order.
Menu Softproviding Meat > Production > Material Requirements Planning >
MRP Calculation > Plant-Dependent Settings
This table is used to configure basic settings for Softproviding MRP Calculation. These settings are
plant-dependent.
Use
This table is used to preset the values for requirement determination as well as settings with regard
to purchase requisition and planned order.
This setting for material requirements determination is required if, in the calculation, you want to
select material requirements for the specified key date from the current stock requirements list
(MD04). Releasing the calculation will create planned orders which are converted accordingly when
a disassembly order is created.
Prerequisites
There are no prerequisites that must be fulfilled to be able to make entries in this table.
Table Fields
Entries may be created by selecting the New Entries button.
Values
The following types of requirement determination are provided
for selection:
— Available quantity (negative)
— Total dependent requirements
— Total order reservations
— Total dependent requirements and order reservations
— Total requirements
— Total receipts and requirements
Do not create purchase requi- This function is no longer relevant. However, for compatibility
sition reasons, this field is still available.
Recommendation
Please set the indicator so that no purchase requisitions are gener-
ated. This is necessary for technical reasons.
History
In earlier releases, this setting was used to create purchase requi-
sitions for materials with the procurement type External procure-
ment in the MRP Calculation application after it had been released.
Normally, however, purchase requisitions are no longer created in
connection with an MRP Calculation.
If this indicator is not set, entries for the Key date field are inde-
pendent of the fields Basic start date and Basic end date.
System behavior
With a set indicator, the system behaves as follows:
— If the key date is less than the basic start date, the key date
is set to the basic start date.
— If the key date is greater than the basic end date, the key
date is set to the basic end date.
— If the key date lies between the basic start and end date it
remains unchanged.
Recommendation
If you do not want the key date to adapt (even in exceptional
cases), the indicator should not be set
Note
Apart from Long-Term Calculation, this indicator is also used in:
— MRP Calculation
— Disassembly Order calculation
This indicator was integrated under the customizing items of these
calculations.
Copy fixed quantities to disas- Indicator.
sembly order
Use
Using this indicator, fixed quantities defined in an MRP Calcula-
tion can be transferred to disassembly orders (DAOs). If the indi-
cator is not set, these fixed quantities are ignored when a DAO is
created.
Menu Softproviding Meat > Production > Material Requirements Planning >
MRP Calculation > Number Ranges: MRP Calculation Number
In this step, the number range for the number range object /SPMEAT/CP (MRP Calculation Number)
is defined. After the IMG activity was started, a new entry may be made using the buttons Intervals
and Add interval.
Table Fields
Field Name Description
No. This number uniquely identifies a numbers range interval within
an object or sub-object.
From number 0000000001
To number 9999999999
Current number For internal numbers ranges the current number field shows the
number that assigned last.
Ext This indicator determines whether this is an external or internal
numbers range interval.
Note
If this field is not selected, internal number assignment will be carried
out.
Note
Note that all intervals for the selected number range object are deleted in the target system first. After the
import, only the intervals you export are present. The number statuses are imported with their values at
the time of export.
Menu Softproviding Meat > Production > Requirement Planning > SAP MRP
> User-Exit MD01 Control
In this step, a user exit may be assigned to a material type. This user exit allows you to restrict the
planning run to certain material types. All materials belonging to the material types assigned here
will be included in the requirement planning run (transaction MD01) if the control key which is also
assigned here is defined in the Parameters field in Requirement Planning (transaction MD01).
Table Fields
Field Name Description
User Exit Optional entry of a user exit. User exits are defined in the SAP
Standard Customizing settings of Requirement Planning.
Example
— Z01 Packaging forecast
— Z02 Production forecast
Prerequisites
If it is to be used, the user exit must be activated within the scope
of the SAP enhancement concepts (transaction CMOD). The name
of the enhancement is M61X0001. See also the SAP documenta-
tion for this enhancement.
Material type Here, the desired material types are assigned to the user exit.
Menu Softproviding Meat > Production > Execution > Disassembly Orders >
General Settings
This table is used to configure basic settings for Softproviding Disassembly Orders. These settings are
plant independent.
Use
The Disassembly Order is the central object in Disassembly Production, i.e. the disassembly/cutting
of materials. Based on the Softproviding Meat MRP Calculation, a planned order may be converted
into a disassembly order. Also possible are manual planning and creating of disassembly orders. A
disassembly order is based on a cut list with n cuts. It is the principal object of the disassembly order
to establish, after completion of the order, how good (or bad) disassembly has worked (yield control).
Detailed target/actual evaluations are available for this task. Calculation of a disassembly order only
makes sense once disassembly has been completed, i.e. when all data entries (input and output) as
well as confirmation of the operations are completed.
This table is used to define, among others, the order type with which the disassembly orders are to be
created as well as the pre-settings for planned and actual price sources.
Prerequisites
If you want to select the appropriate order type it must be created beforehand.
Table Fields
Entries may be created by selecting the New Entries button.
Use
The selected order type is used to create the disassembly order
and the SAP production order.
Recommendation
It is common practice to work with your own order type (e.g.
ZPP1) for disassembly orders. It should be created as a copy of or-
der type PP01 and adjusted accordingly.
Note
You can use different order types for each disassembly process by as-
signing them in Softproviding Meat Customizing of Disassembly Pro-
cesses. Please refer to chapter 3.4.3 “Disassembly Processes”.
Field key General information
In the routing data of shop floor control (Customizing), individual
user fields may be made available by defining an own field key.
For more information on this topic see the section “Defining User
Fields” further up.
Use
The field key is used in the operations of the routing. In the opera-
tion details, the newly defined field key may be selected in the
Field key field. The key fields assigned in Customizing (e.g. Cut
number and Operation quantity) are the displayed.
Customizing
In field key Customizing enter the key word “cut number” for Text
(20), and the key word “operation quantity” for Quantity. Also en-
Objective
This field key serves to determine the correct planned input quan-
tity per cut as well as to represent the working times per cut in the
disassembly order.
Background information
The operation quantity entered (in field MGVRG) in the operation
overview of the production order (transaction CO02) is the
planned quantity of the topmost input material. However, this is
not the planned input quantity of the respective cut input materi-
als within the cut list. This is the reason, those user fields are
needed. In the details of the individual operations (in the produc-
tion order (CO02), User Fields tab) the information relevant to the
cut (cut number and operation quantity) are then stored.
Act: Alt. trans Reading actual data: Check alternative business transaction.
Note
This field should only be maintained if absolutely necessary!
APO modification imple- Setting this indicator will suppress the display of the settlement
mented rule on the screen when a disassembly order is created. The settle-
ment rule is required if you want to settle the costs of a sender ob-
ject to receiver objects within the context of period-end closing
works.
Background information
When a disassembly order is created, a settlement rule is dis-
played. This is an SAP Standard screen. In order to proceed with
the creation of the disassembly order, this settlement rule must be
exited with the Back button.
Use
Calculating synchronously may be very performance- and time-
consuming. This is the reason this setting must be selected explic-
itly.
Keep SAP data synchronous If this indicator is set, the SAP Standard data in Disassembly Or-
der are always kept up to date. If it is not set, the SAP Standard
costing is only updated when the disassembly order is saved.
Use
Keeping calculations synchronous may be very performance- and
time-consuming. This is the reason this setting must be selected
explicitly.
Note
If this Keep SAP data synchronized indicator is set, the SAP stand-
ard costing data is always up-to-date. If the indicator is not set, this
has the advantage of better performance, but in this case the solution
to the aforementioned rounding problem using the minimum quanti-
ties (see next field for description) may only be recognizable when the
period-end closing work is carried out.
Use minimum (default) quan- In special calculation scenarios, rounding problems can occur with
tity in SAP disassembly orders if the order quantity and/or component quan-
tities are too small.
To solve the problem and for flexible control, this indicator is pro-
vided for setting:
— Indicator is set
In this case, the system checks the Base quantity field in
the Default Values for Generation of Operations table (trans-
action OPJG) and copies the value stored there to the pro-
duction order (CO02) for the component quantity. In this
way, minimum quantities are used, which solves the
rounding problem.
— Indicator is not set
The above table is not checked, no minimum quantity is de-
termined and transferred to orders.
Note
Please note the information in the Keep SAP data synchronized field
(above).
Planned price The price source defined here is used as default value for the ini-
tial price. In the calculation, the price source is relevant for all ma-
terials with the procurement types external procurement and both
procurement types (external procurement and in-house produc-
tion). The value defined here may be changed per input material
in Standard Cost Estimate. The price source provides information
on the origin of the price.
Use
— Softproviding Meat Standard Cost Estimate
— Softproviding Meat MRP Calculation
— Softproviding Meat Long-Term Planning Calculation
— Softproviding Meat Disassembly Calculation
Examples
— Standard price
— Planned price 1
Dependencies
As to these default values, there are separate settings for the ap-
plications mentioned above.
Actual price An entry made in this field is used as preset for the actual prices of
the input materials in the disassembly order.
Use
In the application this preset may be changed manually per input
material.
Use description from cut list When a disassembly order is created, the description of the cut
as default list (long text) is passed on to the Short description field of the or-
der if this check is activated.
Use
— Softproviding Meat Disassembly Order
Note
Without a default value, the Description field in the calculation must
be filled since it is mandatory.
Recommendation
Check this indicator.
Note
An entry in this field defines the cost rate in the target 1 calculation.
These costs can be displayed in the cost view. There are separate set-
tings for Standard Cost Estimate, MRP Calculation and Disassembly
Order.
Menu Softproviding Meat > Production > Execution > Disassembly Orders >
Plant-Dependent Settings
Table
This table is used to configure basic settings for Disassembly Order. These settings are made by plant.
Use
Defaults
The plant-dependent settings include optional settings for the default settings in Disassembly Order
for the following fields:
— Production Scheduler Profile
— Variance Key
— Automatically adapt key dates to basic dates
Confirmations
Also, settings on Confirmations are made for the following fields:
— Confirmation type
The confirmation type determines whether the order is only confirmed and/or exited (i.e.
closed).
— Confirmation off
The confirmation is based on the actual, target 1, target 2 or variance values. Confirmations
are always based on input quantities. Depending on the settings made here, either the actual
or the target quantities are used for confirmation.
— Use actual labor costs
The actual working time in Disassembly Order corresponds to the target working time. How-
ever, if this indicator is set the determination will use the actual labor costs. The confirmation
function in Disassembly Order is inactivated, since the confirmation must be made via SAP
Standard (transaction CO11N).
For further details on the confirmation functionality please use the respective F1 field help function
as well as the explanations given in the Disassembly user documentation.
Period-end closing
Settings which are relevant within the framework of period-end closing works are made for those two
fields:
— Source structure
The source structure is used to settle the costs incurred on the sender (the disassembly order)
to different receivers (order items) depending on the cost element. It must be assigned in this
table and must not be defined in the settlement profile. The structure is defined using SAP
Standard transaction OKEU.
— Equivalences off
If data collecting in Disassembly is completed, you may settle the actual or target equivalences
with the Disassembly Order Presettlement program within the framework of period-end clos-
ing.
For further details and examples on source structures or equivalences use the respective F1 field help
function as well as the explanations given in the “Period-End Closing” section of the Disassembly user
documentation.
Table Fields
Entries may be created by selecting the New Entries button.
Use
In Disassembly Order the variance key is required if variances are
to be determined within the framework of period-end closing.
Without variance key, these production orders are not factored in
for variance determination.
Automatically adapt key date In Disassembly Order, the fields Basic start date and Basic end date
to basic dates are filled according to the scheduling parameters. The Key date
field which is used for the determination of the current equiva-
lences, prices, cost data and fixed indicator can be configured so
that it adapts to the dates in the basic start and basic end date
fields.
If the indicator is set, the key date will always reflect the basic
dates. If the basic dates are changed, they key date is adjusted au-
tomatically if it lies outside the dates.
System behavior
With a set indicator, the system behaves as follows:
— If the key date is less than the basic start date, the key date
is set to the basic start date.
— If the key date is greater than the basic end date, the key
date is set to the basic end date.
— If the key date lies between the basic start and end date it
remains unchanged.
Recommendation
If you do not want the key date to adapt (even in exceptional
cases), the indicator should not be set
Note
In Disassembly Order, constellations may occur in which the basic
dates are adjusted by SAP Standard (depending on the scheduling
type). In this case the key date is not adjusted automatically until the
disassembly order is saved and called again.
Note
“Only confirm” means that the order is only partially confirmed. In the
order, status TRÜCK is set. Data entries and confirmations are still
possible. “Confirm and exit”, on the other hand means, that the order
gets status RÜCK, and no more confirmations may be made.
Confirmation off Confirmation are carries out on the basis of the following values:
— Actual
— Target 1
— Target 2
— Variance
Do not calculate automatically If this indicator is set no calculation of the order is carried before
before confirmation the disassembly order is confirmed.
Note
If the activities are not converted, they will not be selected. Data are
used in the same way as in target calculation.
The values are only selected if Disassembly Order is restarted and re-
calculation is performed. The Update actual data button does not
have any function here.
Source structure The source structure is used to settle the costs incurred on the
sender (the disassembly order) to different receivers (order items)
depending on the cost element.
Values
Available structures are those that were defined in SAP Standard
Customizing.
Note
The source structure must be assigned in this table, it must not be de-
fined in the settlement profile. The structure is defined using SAP
Standard transaction OKEU.
For further details and examples on the source structure please see the
section on period-end closing in the Disassembly user documentation.
Equivalences off Equivalences or equivalence numbers are used to assessment val-
ues which are used to distribute costs. In Disassembly calculation,
the equivalence numbers are determined on the basis of real ac-
tual values or target or variance values. This is defined by the set-
ting made in this field.
Use
The equivalence numbers for the settlement rules are calculated
with data of Disassembly Process Calculation. This setting de-
fines from which calculation the values are to be calculated.
Recommendation
Typically, the determination of the equivalence numbers which is
based on the actual values is chosen.
Enhancement
In order to determine equivalences, there is the possibility of in-
fluencing the data in a customer-specific way (BAdI).
BAdI
Enhancement /SPMEAT/ES_COKO
BAdI /SPMEAT/BADI_COKO
Methods
For details, see the “Enhancements” section further down in this
document.
Price unit Definition
The price unit is the number of units of measure to which the price
refers. The price unit must always be regarded in context with the
price.
Use
The price unit defined in this field is used in the Controlling tab of
Disassembly Order. The per-kg price is determined with the prices
unit which is assigned here. If this field is without entry, price
unit 1 is used.
Examples
— Price unit: 1
— Quantity in kg: 2,000
— Total value: 50,00 EUR
— Price per 1 kg = 25,00 EUR
Target losses Use
In Disassembly Order (Controlling tab) disassembly losses may be
displayed. Note that these are target losses. Losses are displayed
by loss type or as a total, depending on the settings made in Cus-
tomizing. You also choose not to display those losses.
Values
— No
— By loss type
— Only total
Prerequisites
A loss type (e.g. cooling loss, cutting loss) was assigned to the ma-
terial in the material master database (Disassembly tab).
Batch assignment level To create the batches for the output materials in Disassembly you
select one of the following options:
Values
— Material
— Cut and material
Prerequisites
In SAP Standard Customizing one of the following settings was
made:
— Batch unique at material level
— Batch unique at material level for a material
Background information
If the batch level was set at unique at plant level in SAP Standard
Customizing (transaction OMCE), the Batch field is displayed
(General tab) when a disassembly order is created and an output
batch is assigned automatically. This output batch is valid for all
output of the order (as default batch in disassembly process en-
try).
Dependencies
The Batch field is available in Disassembly Order (General tab) if
the batch is assigned uniquely at plant level (transaction OMCE).
Do not carry out target 1 cal- In some implementations, a target 1 calculation is not necessary,
culation for instance, because the same prices are used for both Target 1
and Target 2 calculations. In this case it can be deactivated which
may result in improved performance.
Note
For further information, see the F1 input help for this field.
Consolidate component/oper- If set, the components and operations are consolidated, meaning
ations there is a maximum of 2 components (input/output) per material
and one operation per work center. This is the standard setting
per cut.
Use
If you do not weigh per cut, it is not useful to keep the dates per
cut either.
PS – Variances Price source for the calculation of values for variances.
Use
Settings for this field are relevant for variance calculation for dis-
assembly orders. The price source stored here is used for variance
calculation.
Caution
This setting is only relevant for special business scenarios in the
context of variance calculation and for special subsequent pro-
cesses for this form of calculation.
Posting date on last day of the This indicator is not used in the current release. It is intended for
period future developments in the context of the Material Ledger.
Caution
Do not set this indicator.
Menu Softproviding Meat > Production > Execution > Disassembly Orders >
Excluded Document Categories
Table Fields
This table is used to make settings applying to document categories which should only be used to a
limited extent for disassembly order processing.
Examples
— Document category GI (goods issue) for the disassembly or-
der
— Document category GR (goods receipt) for the further pro-
cessing order
Use
For disassembly orders, statistical data entries may be made in
disassembly inbound and disassembly outbound, which, for in-
stance, may be used for evaluations later on. Here, Softproviding
customers will typically use special document categories (e.g.
document category ST = statistical entries).
Examples
— ST (statistical entry)
— SE (statistical inbound)
— SA (statistical outbound)
Menu Softproviding Meat > Production > Execution > Disassembly Orders >
Excluded Statuses
Table Fields
This table is used to configure basic settings regarding the status of goods movements.
Example
If a PDA data record with status Blank is generated using a cus-
tomer-specific application (e.g. a customer-specific DGA), the ac-
tual quantities of the PDA data record are updated as effectively
posted actual quantities in the disassembly order if there is no en-
try maintained in this table. However, for status Blank or Canceled
this is neither desirable nor is it reasonable.
Recommendation
For this reason, Softproviding recommends to make the following
settings for the respective plant:
— Blank
— Canceled
4 Enhancements
BAdIs (Business Add-Ins) serve to set up customer-specific program enhancements which can be im-
plemented by customers as required. These enhancements remain unaffected by a change of software
release. The implementation is undertaken with SAP standard transactions.
If enhancements are available for applications which are described in this configuration guide, a ref-
erence will be made (in the user documentation as well as in the configuration guidelines.
Prerequisites
Authorizations required to create or change BAdI implementations:
— Developer key
In this chapter, enhancements are listed with their classes and methods.
4.1.3 Others
Settlement rule
When a disassembly order is created, a settlement rule is displayed. This is an SAP Standard screen.
In order to proceed with the creation of the disassembly order, this settlement rule must be exited
with the Back button.
The displaying of the settlement rule can be suppressed. However, this is a modification. It is de-
scribed in SAP OSS note 452010. In addition to this modification, an indicator must be set in
Softproviding Meat Customizing. This indicator must not be set without prior consultation with
Softproviding.
In this chapter, enhancements are listed with their classes and methods.
Note
See description at the end of this
table.
Import and export parameters of method and function module are identical:
— Import parameter I_PROCNR
— Export parameter ES_SPLIT
— Export parameter ET_SPLIT_AQZIF
This implementation is necessary so that the Softproviding Meat logic can be used in the material
ledger.
Note
If you have already implemented this in the Z area in a version prior to v5.40, we recommend that you
replace this Z implementation with the standard function module /SPMEAT/CT_CKML_COST_SPLIT.
Note
For more information on the material ledger, and in particular the other prerequisites that must be ful-
filled before you can also use disassembly orders in the material ledger: see the “Master Data / Material
Ledger” section in this document.
5 Master Data
This chapter describes those master data which are relevant to the applications mentioned in this
configuration guide. These are:
— Master data for which Softproviding either provides their own transactions in the user menu,
or
— Transactions or maintenance views, which were not explicitly added to the application menu.
In the calculation (Standard Cost Estimate and MRP Calculation), quantity quotients in % drawn from
the cut master data for these classification cuts may be replaced by historical data from this classifi-
cation cut statistics.
Prerequisites
Cuts of cut category X (classification cut) were created.
Procedure
The transactions for the classification cut are called as follows:
Menu Softproviding Meat > Production > Master Data > Cut > Classifica-
tion Cut - Statistics > Change/Display
Transaction /SPMEAT/CUTSB (Change)
/SPMEAT/CUTSC (Display)
1. Call the Change Classification Cut Statistics via one of the above-mentioned options.
2. In the Cut number field, enter the cutF4 input help number of a classification cut or select such a
cut using the F4 input help. Restrict your selection to cut category X (classification cut). Using
further parameters (e.g. plant or stock type) this selection may be further refined.
In the upper area of the table, the following fields are displayed:
The following buttons, entry options and information are displayed under the Quantity Distribution
tab:
Create button
Hitting the Create button will display the interval today’s date - 31.12.9999 by default. This proposed
interval may be changed using the Create function. The new interval, valid from – valid to is adjusted
using the Transfer button. In the same way, multiple intervals may be added.
For these intervals, quotients in % may be assigned to the cut output materials in the right-hand side
area of the table.
Result
If all the necessary entries have been made, they may be saved by selecting the Save button. These
entries will then be available in the above-mentioned calculations. Once the entries are saved, the
transaction is terminated automatically.
Prerequisites
PDAO data records are available. However they do not necessarily need to be posted.
Procedure
The transaction with which to create and update the classification statistics are started das follows:
Menu Softproviding Meat > Production > Master Data > Cut > Classification
Cut – Statistics > Update Classification Statistics
Transaction /SPMEAT/CUT_CLSTAT_R
Selection Fields
The following fields are provided for data entry and selection:
Cut Area
Field Name Description
Plant The plant is an organizational, logistical unit which structures the
company from the perspective of production, procurement,
maintenance and materials planning. Materials are produced and
goods and services are provided in a plant. The plant is a com-
pany’s production site.
Cut category Cut category X = classification cut predefined and fixed.
Cut number The program will search for PDAO data records for the materials
of the cut number entered here. If data were selected, they may be
stored as statistics data under this cut number.
Note
Data are only determined for classification cuts.
Valid on This field must be filed even if it is not explicitly declared as a
mandatory field.
Background information
The classification cuts entered in the Cut number field are checked
against the Valid on field. Later, only the cuts are valid are filtered
and used (field in cut Valid from … to).
Valid from The statistics of the classification cut contains the validity Valid
from.
Valid on The statistics of the classification cut contains the validity Valid
to.
PDAO Area
Field Name Description
Document group In SAP business transactions are represented by documents. This
field combines documents in one group which are treated uni-
formly from the PDA (Process Data Acquisition) view.
Example
— C = Disassembly order
Note
Since this program was developed to build statistics for the planning
of disassembly calculations, only entry C (disassembly order) is use-
ful here.
Document category In Softproviding Core and Softproviding Meat, business data en-
try operations are represented by document categories.
Example
— Document type WA (goods issue)
— Document type WE (goods receipt)
Note
Since the statistics for output materials are built in disassembly cal-
culation, entries for GR (goods receipt) and SE (statistical receipt) are
particularly useful.
Created on Here, the date specifies when the PDAO data record was created.
Terminal ID The selection can be restricted to terminals.
External ID The selection can be restricted to external IDs.
Storage location The selection can be restricted to storage locations.
Object The selection can be restricted to objects.
Vendor The selection can be restricted to vendors.
Customer The selection can be restricted to customers
Further Details
Field Name Description
Call in simulation If you select this option, determination and display is performed
in test mode. No statistics data are updated.
Selection Result
Display of the data on the screen is identical for test run as well as in update run. If an update run was
executed, an additional success message, “Classification statistics successfully saved”, is displayed.
A repeated start of the section in update run will overwrite an existing statistics record. This is the
case if further data entries for goods receipt or reversals of goods receipts were made.
The material ledger thus forms the basis for actual calculation and enables inventory valuation in
several currencies using different valuation approaches.
Note
Before activating the material ledger, you should check exactly which currencies/valuations are to be
used, since subsequent changes to the setting are no longer possible.
In addition to activating the material ledger for the desired valuation area(s), the following activities
are required to ensure the integration of the material ledger with the disassembly orders of the Meat
Management component.
Note
If Material-Ledger active, the ML indicator in the material master database is set active (Accounting tab).
Prerequisites
Definition of a header material for the disassembly orders
— The header material must be created (MM01) and is to be regarded as “dummy material”.
Caution
This header material should not be part of a cut list. In case an existing customer already uses the
header material in a cut and thus in a cut list, we recommend that they test this setting or constella-
tion extensively.
— This header material should not be part of a cut list. In case an existing customer already uses
the header material in a cut and thus in a cut list, we recommend that they test this setting or
constellation extensively.
Note
When a disassembly order is created, this material is written as the header material in the SAP production
order created in parallel and stored in table AFPO.
— When a disassembly order is created, this material is written as the header material in the SAP
production order created in parallel and stored in table AFPO.
Note
In this table, only one material can be assigned per plant.
Example
— Material DUMMY_SW Lebendtier STANDARD
— Material type used: ZVIE (slaughter material)
Note
No entry must be made for the Joint production button (Costing tab: cost distribution among co-prod-
ucts). The appropriate entries are made by the Meat Management software.
Example
— Production version Z001(header material for disassembly order)
— — Routing for material DUMMY_SW Lebendtier STANDARD
— Operation 0010 (dummy operation for header material)
— Blank routing (i.e. without entry)
— Basis quantity 1 kg
— BOM for material DUMMY_SW Lebendtier STANDARD
— BOM item 0010
— Item category T
— Name Dummy Material Disassembly
— Component quantity = 1 KG
Import and export parameters of the method and the function module are identical:
— Import parameter I_PROCNR
— Export parameter ES_SPLIT
— Export parameter ET_SPLIT_AQZIF
This implementation is necessary so that the Softproviding Meat logic can be used in the material
ledger.
Note
If you have already implemented this in the Z area in a version v5.40 or older, we recommend that you
replace this Z implementation with the standard function module /SPMEAT/CT_CKML_COST_SPLIT.