• No results found

Planning Softproviding Meat User Documentation

N/A
N/A
Protected

Academic year: 2022

Share "Planning Softproviding Meat User Documentation"

Copied!
22
0
0

Loading.... (view fulltext now)

Full text

(1)

Great ideas are always simple –

Softproviding simply makes them happen.

Planning

Softproviding Meat

User Documentation

(2)

Version: 1.00

Date: 23 January 2019

Release: v5.40

Softproviding AG Dornacherstr. 210 CH-4053 Basel Switzerland +41 (0)61 508 21 21

[email protected] www.softproviding.com

SAP + Softproviding + YOU. Leading the field.

(3)

Contents

1 MRP Meat Management 4

1.1 Overview 5

1.2 Prerequisites 7

1.3 Creating the MRP Plan 8

1.3.1 Planning Data 9

1.3.2 Steps 9

1.3.2.1 Process Category: Further Processing 10

1.3.2.2 Process Category: Disassembly 11

1.3.2.3 Process Category: Other Processing (Customer-Specific Processing) 12

1.4 Changing an MRP Plan 14

1.4.1 Planning Data 14

1.4.2 Steps 14

1.5 Displaying an MRP Plan 15

1.6 Executing the MRP Run 16

1.6.1 Selection Variants 16

1.6.2 Processing Variants 17

1.6.2.1 Foreground Processing 17

1.6.2.2 Background Processing 17

1.6.3 Processing Log 17

1.7 Displaying the MRP Run 20

1.7.1 Run Data 20

1.7.2 Parameters 20

1.7.3 Steps 21

1.8 Documenting/Saving the Data 22

(4)

1 MRP Meat Management

(5)

1.1 Overview

The programs MRP Plan and MRP Run described in this document are provided by Softproviding AG as part of the Meat Management by Softproviding solution. They complement the existing SAP ERP planning.

Material requirements planning (MRP) is carried out exclusively with regard to BOMs. Meat Manage- ment by Softproviding enhances the existing processes with disassembly processes which typically requires one extra planning step. This planning step is done with MRP Calculation in Meat Manage- ment by Softproviding.

The use of SAP MRP requires separate planning runs. The example below shows the classic demand- driven planning (pull planning) which represents livestock production, further processing and disas- sembly processes. Each of these processes requires a planning run of its own.

Note

For further information on MRP Calculation see the „MRP Calculation” section in the Disassembly docu- mentation.

The Meat Management MRP Plan allows you to perform one combined planning run for disassembly and further processing. Take note that the plans are plant-dependent.

Linking the individual steps allows you to represent and plan different variants of process chains.

They are linked by using the components/products in the BOMs and cut lists.

SAP MRP: Livestock Production

Breeding/hatchery Fattening

Softproviding Meat MRP Calculation: Disassembly

Slaughtering Primal cutting Deboning

SAP MRP: Further Processing

Processing Packaging

(6)

Example for a process chain

Packaging Disassembly Breeding / Livestock

Production

Representation of MRP plan Breast

Breast

Tray Foil Chicken breast

Cl. A, packaged

Breast Drumstick

Wing Back

Chicken 1.2 kg

Chick Starter

Finisher

This linking is done in MRP Plan and saved as a variant. The respective steps are described in detail further down.

The Meat Management MRP Run makes use of the necessary parameters and functions in the SAP ERP planning run (transactions MD01/MD02) thus rendering a separate SAP MRP planning run re- dundant.

Note

For further information on the parameters and use of the SAP MRP planning run see the respective SAP documentation. The topic will not be dealt with in detail in this document.

(7)

1.2 Prerequisites

In order to maintain and use MRP Plan, the following parameters must configured in Softproviding Meat:

— Other MRP step categories

— Number range for the MRP run number

Other MRP step categories are implemented in connection with BAdI /SPMEAT/BADI_AP_RUN_- STE. This function is provided for customer-specific adjustments.

For detailed information please see the Disassembly configuration guide.

(8)

1.3 Creating the MRP Plan

SAP Menu Softproviding Meat > Production > Material Requirements Plan- ning > Planning Tool > MRP Plan > Create

Transaction Code /SPMEAT/APDA

Procedure

In an initial step the plan is created to define the general condition. Mandatory fields are available for data entry in the initial screen:

Field Name Description

MRP Plan External data entry field where a name for the plan (10 charac- ters) is specified. This field may no longer be changed later on.

Plant Organizational unit in which this plan and the assigned materials are planned and produced.

Once you confirmed your entries with the Enter key the program switches to the assignment screen.

Example for an entry screen

The screen is composed of the following areas (in vertical order):

(9)

1.3.1 Planning Data

Field Name Description

MRP Plan Name of the plan given in the entry screen. This field cannot be changed.

MRP Plan description Entry field, 40 characters. May be changed.

Plant Organizational unit in which this plan and the assigned materials are planned and produced. This value is copied from the entry screen.

Stock type A stock type is a specific type of animal, for example, pigs, cattle, turkeys, sheep.

Valid from/to Validity period for this plan if required. The system will automati- cally fill these fields with today’s date and 31.12.9999.

The planning data are the header data of the MRP plan. Here, the basic conditions for the plan are defined. The stock type is used as characteristic in order to be able to link it with the cut lists. In the cut lists the stock type is a basic characteristic on which plausibility checks are made.

The validity-from/to dates may be used to specify validity intervals to those in BOMs and price con- ditions. If a MRP plan is no longer needed, the valid-to date is set to today’s date and then saved.

1.3.2 Steps

The process chain is modeled via steps. Each step represents a process step in Planning and deter- mines the sequence for planning. The numbering is (as with BOMs) specified by the system. The pro- cess is determined by means of an MRP process category.

The following process categories are available:

— (M) – Further processing

— (T) – Disassembly process

— (Z) – Other processing (customer-specific processing)

Depending on the process the planning objects are created and controlled:

In further processing requirements are created and processed via SAP MRP run. In disassembly pro- cesses requirements are imported and processed. In other processing the behavior needs to be defined according to customer requests.

At the bottom of the screen there is a navigation bar. Selecting the respective process category will open additional data fields according to the process category chosen which need to be maintained for this process step.

(10)

1.3.2.1 Process Category: Further Processing

When this process is created the following fields are made available for editing:

Field Name Description Features

Step Sequential number allocated by the system (10, 20, etc.)

System field, no data en- try possible

Description Description of the planning step. Is also used as short text for the created MRP calculation.

Free text with 40 charac- ters

MRP process category Category of the process (further processing, disassembly process, or other process).

List box Material Material number of the product / semi-prod-

uct which is being planned and produced.

Alpha-numeric key, entry field

MRP area Number of the MRP area for which a separate requirements planning is to be carried out.

List box Planning scenario Key, identifying the planning scenario (e.g. of

long-term planning).

List box

Since in connection with further processing an SAP MRP run is created, the following parameters need to be defined:

Field Name Description Features

Multi-level planning This indicator controls whether the planning for a material is to be carried out in one step or in multiple steps.

Check box to activate the function

Also plan unchanged components

If this indicator is set, all components in the BOM are planned regardless of whether any changes which are relevant to planning actu- ally were made to the components.

Check box to activate the function

Use creation indicator from MRP group

This indicator determines whether to include the indicators from the planning parameters from the current application or from the MRP group for the planning of the material.

Check box to activate the function

Processing type Determines the processing for the MRP run:

N – Net change for total horizon P – Net change for planning horizon G – Regenerative planning

List box, default value is blank

Create purchase requi- sition

Determines how the system is to proceed for externally procured material:

1 – Purchase requisition

2 – Purchase requisition in opening period 3 – Planned orders

List box, default value is blank

Schedule lines This indicator controls whether the system, creates a schedule line during the planning run:

1 – No schedule lines

List box, default value is blank

(11)

2 – Schedule lines in the opening period 3 – Schedule lines

Create MRP list This indicator controls whether the system will create an MRP list:

1 – MRP list

2 – Depending on the exception messages 3 – No MRP list

List box, default value is blank

Planning mode Specifies how to treat the requirement pro- posals from the last planning run:

1 – Adapt planning data

2 – Re-explode BOM and routing 3 – Delete and recreate planning data

List box, default value is blank

Scheduling Sets whether to determine basic dates for planned orders or whether to carry out addi- tional lead time scheduling.

The indicator refers to all planned orders hat are new or that were changed or for which the BOM was re-exploded.

List box, default value is blank

Include firm planned or- ders

This indicator controls whether firm planned orders from operative planning are to be cop- ied to long-term planning:

1 – Use settings in planning scenario 2 – Copy firm planned orders from operative

planning

3 – Do not copy firm planned orders from oper- ative planning

List box, default value is blank

Note

For information on the application possibilities of the individual characteristics in material requirements planning (MRP) see the respective documents.

1.3.2.2 Process Category: Disassembly

The following fields are available for data entry when the process is created:

Field Name Description Features

Step Sequential number allocated by the system (10, 20, etc.)

System field, no data en- try possible

Description Description of the planning step. Is also used as short text for the created MRP calculation.

Free text with 40 charac- ters

MRP process category Category of the process (further processing, disassembly process, or other process).

List box

(12)

Cut list The cut list is the topmost organizational unit in Disassembly. It consists of n cuts and rep- resents the entire disassembly for a certain stock type.

Material Material number of the component (disassem- bly material) to be cut.

Stock determination In MRP Calculation, various stock determina- tion are available for stock determination (available quantity on key date, or current quantity (key date-independent)).

Requirements determi- nation

This setting is required if in MRP Calculation you want to import material requirements from the current stock/requirements list (MD04) for the specified key date.

Selection rule A selection rule is a combination of certain time information, planning elements an stocks in a rule which controls the importing of this data into the current stock /require- ments list and the repetitive manufacturing planning table:

Note

For detailed information see the “MRP Calculation” section in the Disassembly user documentation.

1.3.2.3 Process Category: Other Processing (Cus- tomer-Specific Processing)

The following fields are available for data entry when the process is created:

Field Name Description Features

Step Sequential number allocated by the system (10, 20, etc.)

System field, no data en- try possible

Description Description of the planning step. Is also used as short text for the created MRP calculation.

Free text with 40 charac- ters

MRP process category Category of the process (further processing, disassembly process, or other process).

List box Step category Customer-specific step in MRP Plan/Run.

This requires that a BAdI is implemented.

List box, entry field with plausibility check

Result

You may create any number of steps and processes in one plan. When the transaction is saved the MRP Plan is created and is available for changing or displaying.

(13)

Example for an MRP plan with breeding process (sales-oriented planning)

Packaging Disassembly Breeding / Livestock

Production

Example for an MRP plan without breeding process

Packaging Disassembly

(14)

1.4 Changing an MRP Plan

SAP Menu Softproviding Meat > Production > Material Requirements Planning >

Planning Tool > MRP Plan > Change Transaction Code /SPMEAT/APDB

The initial screen features a data entry field with input help for the MRP plan to be edited. Selecting the Enter key will take you to the detail view.

The data available for editing typically have a white background and may be selected by means of the TAB key. Depending on the level (overview data / detail data), additional fields are made availa- ble for changing.

1.4.1 Planning Data

In this area the following data fields may be changed:

— MRP plan description

— Stock type

— Valid from/to

The selection name (MRP plan) and the plant cannot be changed. Where necessary, a new plan must be created. The old plan may be marked das obsolete by restricting the validity period accordingly.

1.4.2 Steps

In order to change the steps or the details stored in them, the desired step is selected by double- clicking in the respective row. The selected step is identified by an arrow in the leftmost column.

The following data may be changed in the step overview:

— The step number in order to change the sequence

— The step description

All other data may be changed in the detail view in the right-hand screen area.

The step category (further processing, disassembly process) cannot be changed and must be com- pletely deleted. In order to do so, select the step by double-clicking and push the Delete step button in the navigation bar.

After this you may add steps or change the sequence any time.

Selecting the Save button will save your changes and end the program.

(15)

1.5 Displaying an MRP Plan

SAP Menu Softproviding Meat > Production > Material Requirements Planning >

Planning Tool > MRP Plan > Display Transaction Code /SPMEAT/APDC

Enter the MRP plan to display in the initial screen and start the program by hitting the Enter key.

This mode does not allow you to change any data. To exit the program, select the icon in the SAP standard navigation bar or by hitting the Escape key.

(16)

1.6 Executing the MRP Run

SAP Menu Softproviding Meat > Production > Material Requirements Planning >

Planning Tool > MRP Run > Execute Transaction Code /SPMEAT/APRA

When the Meat Management MRP run is used, the SAP ERP MRP Planning Run (transaction MD01/MD02) and the Meat Management MRP Calculation (/SPMEAT/CLP*) are combined and exe- cuted. Separate planning runs for the materials allocated in the MRP plans are not necessary.

1.6.1 Selection Variants

In the initial screen the following fields are available for data entry:

Field Name Description Features

MRP Plan Name of the plan Mandatory field, input

help available Planning date Date for which the planning run is to be exe-

cuted. Typically, this is today’s date.

Entry field, relevant for further processing Basic start date Basic start date. Relevant for the disassembly

process settings.

Entry field, today’s date is proposed

Basic finish date Basic finish date. Relevant for the disassem- bly process settings.

Entry field, today’s date is proposed

Key date Relevant for the disassembly process set- tings. This date is used for stock determina- tion type available quantity on key date (MRP Calculation).

Entry field, today’s date is proposed

Display log If this indicator is active, a log is created and displayed when the MRP run is executed.

Check box to activate the function

The parameters which are used may be saved as selection variants.

Note

The variant function offers you the option of saving data entered into programs as variants. This is par- ticularly useful for programs that are frequently started up with identical restrictions. This means that you do not need to enter the same values every time you start the program. When you select the variant, the fields that are already populated with data are used when the program starts.

Any number of variants can be created for each program. After a program starts, input fields are dis- played. When you have entered the parameters you want, you can save them by clicking on the Save as variant button. After adding a variant name and a description and entering data in other fields or high- lighting them, you can save your entries.

By choosing the Goto > Variant menu option, you can display, modify and delete existing variants.

(17)

Click on the User documentation button or access the SAP online help to obtain more information about using variants.

1.6.2 Processing Variants

The program may be executed in the foreground (online) or via a background job (offline). The re- spective function may be found in the SAP ERP navigation bar.

1.6.2.1 Foreground Processing

Foreground processing is carried out by entering the parameters and selecting the Execute button.

The executed planning run is documented by means of an MRP run number. If the Display log indica- tor in the initial screen was set, the program now changes to the log display view.

After processing has been successfully carried out the message „Planning run completed“ is dis- played at the bottom of the screen.

1.6.2.2 Background Processing

With the necessary parameters the MRP run may be carried out as a background job. The settings and intervals of the times of execution must be defined per project. The job is documented via the SAP ERP job management. The overview is the place where the executed job is displayed and the planning runs/documents created in the background are logged.

Note

The job overview is used to manage jobs and is the central area for running a variety of job monitoring and management tasks, such as searching, scheduling, repeating, cancelling and deleting jobs, checking the job status and displaying job reports. The job overview can be accessed using transaction SM37.

See the relevant SAP standard system documentation for more information about the extensive job over- view options.

1.6.3 Processing Log

The processing log is created if the Display log field in the initial screen was activated.

The log display consists of the following components:

— Navigation bar

(18)

The navigation bar features the following functions:

Navigation Bar Icons Description

Detailed information on the documented steps Long text for the message

Technical information for the message Application help

The overview shows information on the planning run carried out. A log entry is created per created step, and the following results are documented:

For further processing steps: the planned material or the material to be produced (BOM header material)

For disassembly process steps: the MRP calculation number and any planning order that might have been created

If you double-click on the rows, additional information will be displayed in the detail view. Also, con- firmations in the form of message categories are output. Depending on the specifications made there are the following message categories:

Message Category Description

Red Error, termination, order creation not successful

Yellow Notification, no termination, order creation successful (possibly with restrictions!).

Green No notification, Order creation successful.

The log may be further edited with the familiar SAP standard functionalities. The following function buttons are available:

Button Function Description Technical infor-

mation notification

Detailed technical information for the message.

Sort descend- ing/ascending

Sorts the list content in descending or ascending order.

Find tool Search function with which values may be determined.

Find next Function with which to search again.

Filter Filter function. By means of the field list the user may define any column content to display certain data.

Total/subtotal Standard function for the totaling of values. This function is not active for this log category.

Print Outputs the log on a printer.

Views Standard view is the grid format. Switching view to list output or Microsoft Excel is possible.

Export Data may exported to different variants: to a local file, sending per email/communicator, saving to an Office file, or HTML download.

(19)

Button Function Description

Change layout Changing layouts, defining of display variants.

Termination The number of terminations for the program run may be dis- played.

Error The number of error messages may be displayed.

Warning The number of warning messages may be displayed.

Information The number of information messages may be displayed.

Note

For further information please see the SAP ERP documentation on logs.

(20)

1.7 Displaying the MRP Run

SAP Menu Softproviding Meat > Production > Material Requirements Planning >

Planning Tool > MRP Run > Display Transaction Code /SPMEAT/APRC

In the initial screen, the number of the MRP run created last is proposed. The user may enter or select via the input help a different number. Additional functions for the detail view are available in this run. If the user is authorized to use this transaction, he/she may jump to the respective program.

The MRP run display screen consists of the following components:

— Header area with run data

— Parameters

— Steps Note

Data cannot be changed. I necessary a new MRP run must be created.

1.7.1 Run Data

The run data contain information on the execution of the MRP run and the user.

Field Name Description

MRP run Number of the MRP run

Run type Processing type for the run (foreground or background) User User ID and name of the SAP creating the run

Start Date and time of execution

End Date and time of the ending

Furthermore, the user may switch to the log by selecting the run log button. The User button may be used to call the user’s contact data, if maintained.

1.7.2 Parameters

The data listed here correspond to the values specified in the MRP plan.

Field Name Description

MRP Plan Name of the plan given in the entry screen. This field cannot be changed.

Plant Organizational unit in which this plan and the assigned materials are planned and produced. This value is copied from the entry screen.

(21)

Stock type A stock type is a specific type of animal, for example, pigs, cattle, turkeys, sheep.

MRP date This field is filled if a date was specified. Typically this is today’s date.

Basic start date Basic start date. Relevant for the disassembly process settings.

Basic finish date Basic finish date. Relevant for the disassembly process settings.

Key date Relevant for the disassembly process settings. This date is used for stock determination type available quantity on key date (MRP Calculation).

1.7.3 Steps

In the Steps tab the details per step may be displayed by double-clicking. Successful execution is in- dicated by a checkered flag icon. From the details the user may jump to the following further func- tions:

MRP Step Category Further Functions

Further processing Stock and requirements list for displaying the planned orders (transaction MD04).

Disassembly process Displaying the MRP calculation

Displaying the disassembly inbound view Displaying the disassembly outbound view

The created MRP calculation is displayed with the parameters defined in the MRP plan.

(22)

1.8 Documenting/Saving the Data

All data created in connection with MRP Plan and MRP run are documented or saved in the follow- ing Meat Management tables:

— SPMEAT/APDK MRP Plan (header)

— SPMEAT/APDKT MRP Plan (short text)

— SPMEAT/APDP MRP Plan (step)

— SPMEAT/APRK MRP Run (header)

— SPMEAT/APRP MRP Run (step)

References

Related documents

Solution: AVEVA’s Asset Life Cycle Information Management solution; AVEVA’s Control of Work solution; AVEVA Enterprise Asset Management™.. Asset Visualisation

This year, Telchac Education received $52, 000 pesos that will continue to sponsor the 18 students from last year (remember, we have a yearly commitment with the students) and take

The repository is much like an ordinary file server, except that it remembers every change ever made to your files

The result of the research in the data persentation in chapter IV concluded that the second grade students of MAN Pasir Pengaraian Kabupaten Rokan Hulu have Poor

The research included in this literature review contain material discussing;- language development and the historical background of the Welsh language; mother

In this review, various types of EEG-NFB training are described, including training of slow cortical potentials (SCPs) and frequency and coherence training, with their main

Jacada WorkSpace is well suited for contact center environments where agents are either burdened with multiple desktop applications or where complex business rules (whether

Instituto de Ciência e Tecnologia, Universidade Federal de São Paulo, Talim St. The presence of noise in data can affect the complexity of classification problems, making