Think ahead. Go there.

Great ideas are always simple –

Softproviding simply makes them happen.

Process Data
Softproviding Core
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

SAP + Softproviding + YOU. Leading the field.

Think ahead. Go there.

Contents

1 Overview 5

2 Customizing 8
2.1 Processes 8

3 Configuration / Process Data Acquisition 10

3.1 Definitions 10
3.1.1 Devices (DGS Remote Devices) 10
3.1.2 Strategies 11
3.1.3 Work Group 13
3.1.4 Further Processing Group 14
3.1.5 Empties Levels 15
3.1.6 Define Change Reasons 16
3.1.7 Application for Material Groups 16
3.2 Organization 17
3.2.1 Plants / Storage Locations 18
3.2.1.1 Plants 18
3.2.1.2 Storage Locations 27
3.2.1.3 Further Information: Pair Formation 28
3.2.2 Terminals 28
3.2.3 Number Ranges 39
3.3 Orders 40
3.3.1 Order Types 40
3.3.2 Item Categories 42
3.3.3 Component Replacement 46
3.3.3.1 Define Conditions 47
3.3.3.2 Implement Conditions 47
3.3.3.3 Post Replacement 48
3.3.4 Quality Inspection 48
3.4 Control Settings 50
3.4.1 PDA Program Logic 50
3.4.2 Entry Operation 51
3.4.2.1 Recording Devices 63
3.4.2.2 Label Printer 65
3.4.2.3 Log Printer 65
3.4.2.4 Allowed Storage Locations 66
3.4.2.5 Change ID Label Printer 66
3.4.2.6 PDA Checks 67
3.4.3 Goods Movement 68
3.4.3.1 Further Information: Batch Jobs 72
3.4.4 Usage 73
3.4.5 Entry Subscreen 76
3.4.6 Barcodes 78
3.4.6.1 Field Definition 80
3.4.7 Scanner Entry 81

Process Data – Softproviding Core Configuration Guide 3/112

Think ahead. Go there.

3.4.7.1 Process Variants 81

3.4.7.2 BAdI for Scanner Entry 83
3.5 System Modifications 83
3.6 Archiving 84
3.7 Miscellaneous 86
3.7.1 Warehouse Stock Cleanup: Movement Types 86
3.7.2 Purchase Order Category (Purchasing) 87

4 Enhancements 89
4.1 SAP Standard Enhancements 89
4.1.1 Mandatory Enhancements 89
4.1.2 Optional Enhancements 89
4.2 Softproviding Core and Meat Enhancements 90
4.2.1 Mandatory Enhancements 90
4.2.2 Optional Enhancements 90
4.3 User-Exits 100
4.3.1 Overview 100
4.3.2 Mandatory Enhancements 102
4.3.2.1 Batch Where-Used List 102
4.3.2.2 Order Confirmation (Further Processing) 102
4.3.2.3 Requirements Planning (MD01) 103
4.3.2.4 Requirements/Stock List (MD04) 104
4.3.3 Optional Enhancements 105
4.3.3.1 Order Confirmation (Process Orders) 105
4.3.3.2 Actual Data Entry (Repetitive Manufacturing) 105

5 Other 107
5.1 Component Replacement 107
5.1.1 Create Entries for Replacement 108
5.2 Control Settings for Period Batch 110
5.2.1 Overview 110
5.2.2 Settings 110
5.2.2.1 Material Master 110
5.2.2.2 Master Data Table 111
5.2.3 Executing the Program 112

Process Data – Softproviding Core Configuration Guide 4/112

Think ahead. Go there.

1 Overview

The descriptions in the Process Data configuration guide explain the table and field settings that can
be applied to the respective application. As far as possible, the settings are described in a process-
oriented manner. Therefore, the descriptions do not always follow the order of the tables listed in the
Softproviding Core Customizing menu. This documentation will help you to set up a fully functional
application.

The tables described are

— Softproviding Core and Softproviding Meat tables and, where applicable,
— SAP standard tables

Descriptions relate to
— the IMG activity (view of the table) and to
— the individual table fields

The descriptions may contain the following information:

— Definitions and standard settings
— Prerequisites and use
— Process data dependencies and examples
— Procedure and recommendations

In general, the following settings are possible in the Customizing tables:

— Field contents
Field contents can be determined via the input help (F4).
— Indicators
Setting indicators activates or deactivates the described functionality.
— Text fields
Keys and text descriptions can be input.

Target Group
— Application consultants, technical advisers, and developers
— Project team members during implementation
— Super users

Prerequisites
Reference is made where applicable to prerequisites that must be met in order for the corresponding
settings to be applied (e.g. SAP standard customizing, master data, authorizations).

References
Where applicable, this guide refers to other documents or to possible program adjustments. Specifi-
cally, these are:
— User documentation

Process Data – Softproviding Core Configuration Guide 5/112

Think ahead. Go there.

— Configuration guides for other application areas

— Customer-specific enhancements by way of BAdIs (Business Add-Ins)

Functions
The following functions are usually available in the Customizing tables:
— Create new entries
— Copy marked entries
— Delete entries
— Undo changes
— Change from Display mode to Modify mode
— Mark all / mark block / Unmark all

These functions are generally well-known and are therefore not explained in detail in this document.

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
If enhancements are available for an application whose configuration is described here, reference is
made to the relevant point (configuration guide and user documentation).

BAdIs (Business Add-Ins) are used to create customer-specific program enhancements that can be
implemented by the customer if required. These enhancements remain unaffected in the event of a
release change. SAP standard transactions are used to implement BAdIs.

The following options are available for customer-specific enhancements (BAdIs):

— SAP standard enhancements
— Enhancements by Softproviding

For further details, see the chapter “Enhancements” in this configuration guide.

Process Data – Softproviding Core Configuration Guide 6/112

Think ahead. Go there.

Transport
The applied settings should be transferred to a transport request via the Save function. The appropri-
ate configuration for ensuring that this happens must be set by the project team member responsible.
This ensures that these settings can also be transported to other systems.

Caution
The special prerequisites must be observed when transporting number range intervals.

Result
This configuration guide will help you to apply the settings needed to use the applications described.
Any master data and authorizations required are explained in the relevant user documentation.

Process Data – Softproviding Core Configuration Guide 7/112

Think ahead. Go there.

2 Customizing

Open the Customizing function using one of the following options and then click on the SAP Reference
IMG button.

Menu Tools > Customizing > IMG > Project Processing

Transaction SPRO

Then, within the Implementation Guide, open the menu item Softproviding Core > Logistics > Process
Data Acquisition

The following functions are available in this menu item and are described in this guide:
— Definitions
various subareas
— Organization
various subareas
— Orders
various subareas
— Control
various subareas
— System modifications
various subareas
— Archiving
various subareas
— Other
various subareas

2.1 Processes
Below you will find a brief initial explanation of the applications whose configuration is described
here. Descriptions of the respective Customizing tables then follow, along with a detailed description
of the field settings (configuration).

General
Process data is created through entries in the various processes of the Softproviding Meat and
Softproviding Core applications. The data records created (PDA data records) and the process infor-
mation they contain can be designated process data. They are stored, among other places, centrally
in the table /SPDGS/PDAO. PDA stands for Process Data Acquisition.

The Softproviding Core transaction /SPDGS/PDAO opens these data records (PDA operations). This
transaction can also be called up via the central Process Data Cockpit (transaction /SPDGS/PDAON).

Process data is generated at every stage of the applications, from livestock management through to
disassembly, production and picking goods. The Customizing settings that can be applied to Process

Process Data – Softproviding Core Configuration Guide 8/112

Think ahead. Go there.

Data Acquisition (configuration) thus permit and control entries for the various application areas
mentioned above.

For example, information captured at the disassembly and further processing inbound and outbound
or during goods receipt for a purchase order leads to such data records. These data entries in the plants
are generally made during operations via DGA (Device Gateway Applet) touchscreen applications or
via mobile end devices with RAF (Remote Application Framework). 

Background
A large number of entries are made in a short period of time in the meat industry in various fields of
application (e.g. disassembly and production). Posting these entries immediately would lead to stock-
relevant postings being generated straight away, which is not desired. In order to prevent this, the
PDA operations created with the entries are stored in the table /SPDGS/PDAO mentioned above.
These PDA operations are posted at a later time. Batch jobs are usually set up for this. Here, PDA op-
erations of the same type (e.g. same plant, storage location or material) are collected and posted at
set intervals according to the definition in the job.

This collective posting via jobs ensures the temporal separation of the data capture on the one hand
and stock updating on the other. It is also possible to post these PDA operations manually with trans-
action /SPDGS/PDAC; however, this is not common.

Examples
Examples of settings in this guide are:
— Certain terminals and entry devices are authorized
— Processes (e.g. entries in disassembly) are authorized for individual terminals and users
— Control of the posting of goods movements
— Forming order pairs (= linking orders)
— Customer-specific developments are possible (BAdIs)

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.

Process Data – Softproviding Core Configuration Guide 9/112

Think ahead. Go there.

3 Configuration / Process Data Acquisition

3.1 Definitions
Open the menu item Definitions in the implementation guide as follows:

Menu Softproviding Core > Logistics > Process Data Acquisition > Defini-
tions

The settings for the following tables are described in this section:
— Devices (DGS Remote Devices)
— Strategies
— Work Group
— Further Processing Group
— Empties Levels
— Define Change Reasons
— Application for Material Groups

Use
Basic data acquisition settings are applied in these tables. The most important settings are:
— Device definitions
— Data acquisition strategy (preset)

3.1.1 Devices (DGS Remote Devices)

Use
In this section, you can define devices on a per-plant basis (e.g. scanners, scales). The necessary tech-
nical settings (device type and RFC destination) are applied to each device individually.

The devices defined in this table are required, for example, in tare management, i.e. in the settings for
empties management. These settings are made in the Tare Management table, which can be accessed
with transaction /SPDGS/EMPT or via the Softproviding Core Application Menu DGS > DGA > Appli-
cations. For further settings for the tare functionality see the table Empties Levels (below).

The Softproviding Core user documentation DGS - Device Gateway System describes the settings for
the table Tare Management.

Activities
Entries can be created by selecting the button New Entries.

Process Data – Softproviding Core Configuration Guide 10/112

Think ahead. Go there.

Table Fields
Field Name Description
Plant Definition
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 serves as a
production site for a company.
Device A device can be a scanner, scales, a flow meter, or an external sys-
tem. The precise variant is defined in DGS Customizing.

Examples
— ITEC
— BANS
— AutoFOM
Description The name provides a more detailed description of a device. It is
not necessary to enter one. However, it is recommended to do so
in order to ensure unambiguous designation.

Use
The name is shown in applications (e.g. on buttons).

Example
— The device WAAGEIP23 is named WE-Zone 2.
Device type This setting assigns a device to a device type and classifies it on
this basis.

Value selection
The following device types are defined and can be used:
— Device Gateway Client
— Database
— TCP/IP
Processing routine The field Processing routine is no longer used.
Destination Enter the name of the logic destination (RFC destination). This is
indicated in a function call.
Command The field Command is no longer used.

3.1.2 Strategies
Use
Data acquisition strategies (PDA strategies) are a key function in Further Processing Entry. The pre-
defined PDA (Process Data Acquisition) strategies are provided in this table. They determine whether

Process Data – Softproviding Core Configuration Guide 11/112

Think ahead. Go there.

input or output material is entered, calculated, or just displayed. It is not possible to make an entry in
the application without inputting and using a strategy.

The strategy is assigned to the output material in the material master data (Core Further Processing
or Core Process Data) and/or at the PDA point (Customizing: Softproviding Core > Logistics > Process
Data Acquisition > Organization > Terminals). Assigning to the material takes priority. If no strategy
is entered at either point, the system default ($SYS) is used.

The strategy can be changed in the process if the indicator Fixed strategy is not activated in the plant
settings in the Customizing menu for process data acquisition.

Note
In contrast, the strategy IWOW is always used in the Softproviding Meat Disassembly Process Entry.

Standard Settings
The following PDA strategies are supplied by Softproviding AG as standard.

PDA strategies Description

$SYS (= system default) Input and output are entered
(Enter input and output)
IGOW Only the output is entered; the input is calculated and
(Input via quantity / enter output) proposed using the quantity and can optionally be en-
tered. This PDA strategy is only permitted for the unit
KG.
IPOP No entry is made. The input and output are identical to
(Input plan = actual / output plan = ac- the planned quantity.
tual)
IPOW The input is not entered; it is identical to the planned
(Input plan = actual / enter output) quantity. The output is entered.
IQOW The input is calculated and optionally entered. The out-
(Input via ratio / enter output) put is entered.
IWOG The input is entered. The output is entered. This PDA
(Enter input / output via quantity) strategy is only permitted for the unit KG.
IWOP The input is entered. The output is not entered; it is
(Enter input / output plan = actual) identical to the planned quantity.
IWOQ The input is entered. The output is calculated and op-
(Enter input / output via ratio) tionally entered.
IWOW Input and output are entered
(Enter input / enter output)

Caution
These settings must not be changed. They are set up correctly for the respective entry and posting
processes.

Process Data – Softproviding Core Configuration Guide 12/112

Think ahead. Go there.

Activities/Recommendations
Additional entries can be made. However, this is generally not necessary, as the strategies supplied
cover all the entry options normally used.

Table Fields
Field Name Description
PDA strategy 4-character abbreviation to designate a PDA strategy.
Description This text indicates the PDA strategy.

One setting option is possible per input and per output material for each PDA strategy as follows:

Control Option Description

Weigh If this indicator is activated, the input and/or output are/is en-
tered.
Calculate If this indicator is activated, the input and/or output are/is calcu-
lated.
Plan = actual If this indicator is activated, the input and/or output plan = actual
are/is posted.
No action If this indicator is activated, the input and/or output are/is not
used.

Field Name Description

Method If an input or output is calculated, a method must be stored. This
is then the case if (in the fixed strategies supplied) a W (for
weight) or Q (for quota) is used in the strategy name.

Value selection
The following two calculation methods are currently supported.
— Weight of entry
— Quota of entry

Note
Please refer to the detailed description of the field (F1 help).

3.1.3 Work Group

Use
A work group is an organizational unit within production. The work group is defined in this table. It
is used as a selection criterion in Further Processing Entry and for evaluation purposes in DGS. When
displaying the PDA data records in the PDA data cockpit, the field can be used as a filter criterion.

Process Data – Softproviding Core Configuration Guide 13/112

Think ahead. Go there.

Dependencies
In the Customizing settings for Process Data Acquisition (Control Settings > Entry Operation), it can be
defined whether this field is to be used as a required field in dialog applications.

Table Fields
Field Name Description
Work group Alphanumeric key with max. 8 characters that defines a work
group.

Use
A work group is an organizational unit within production. It is
used as a selection criterion in Further Processing Entry and for
evaluation purposes in DGS. When displaying the PDA data rec-
ords in the PDA data cockpit, the field can be used as a filter crite-
rion.

Example
— 1000 (Team A)
— 2000 (Team B)
Description Freely selectable, 40-character text to identify the work group

3.1.4 Further Processing Group

Use
The further processing group is used as a selection criterion in Further Processing Entry. A further
processing group is defined in this table for this purpose. It can then be assigned to the material to be
produced (output material) in the material master data. When selecting a further processing order in
the entry, orders can be explicitly selected or excluded from the selection using the further processing
group.

Table Fields
Field Name Description
Further processing group Numeric key with max. 3 characters that defines a further pro-
cessing group.

Use
The further processing group is used as a selection criterion in
Further Processing Entry. It can be assigned to the material to be
produced (= output material) in the material master data.

Process Data – Softproviding Core Configuration Guide 14/112

Think ahead. Go there.

Field Name Description

When selecting an order in Further Processing Entry, orders can
then be explicitly selected or excluded from the selection using
the further processing group.

Example
— 100 (raw sausage)
— 200 (cooked sausage)
— 300 (boiled sausage)
Further processing group text Freely selectable, 40-character text to identify the further pro-
cessing group

3.1.5 Empties Levels

Use
This Customizing table is used to define empties levels and assign the desired number of materials to
the level. Entries in this table are used in the Tare Management master data table. This table can be
found in the Softproviding Core application menu under Softproviding Core > DGS – Device Gateway
System > DGA > Applications

The definition of devices (see above) is required in the settings for Tare Management (empties man-
agement). For more information, refer to the Softproviding Core user documentation DGS - Device
Gateway System.

Table Fields
Field Name Description
Empties level Alphanumeric key of max. 3 digits. Within the empties level, the
user can define whether one or multiple materials may be se-
lected.

Use
The empties level groups empties materials within the empties
list and group.

The empties level is assigned in the Tare Management transac-

tion (SPDGS/EMPT).
Material selection type per The number of different materials that can be added to a quantity
level within an empties level.

Allowed values
— One
— Multiple
— Blank

Process Data – Softproviding Core Configuration Guide 15/112

Think ahead. Go there.

Field Name Description

Description Name of the empties level.

3.1.6 Define Change Reasons

Note
Entries in this customizing table are only relevant for the so-called "old" Change ID Control application.
This was developed for releases v5.30 and v5.40. Releases v5.40 and higher use the so-called "new", fur-
ther developed Change ID Control application.

3.1.7 Application for Material Groups

Use
In various DPS-RAF applications (e.g. Goods Receipts or PDA Postings), these applications can be
used to simplify material selection and thus achieve faster material entry. The definition of applica-
tions and assignment of styles for display in RAF is done in this table. The material and group assign-
ments and other settings for display in RAF are made in an application table in the Softproviding Core
menu (see the following description of the Application field)

Field Description
Application Alphanumeric key with a maximum of 20 characters to describe
the application.

Depending on the individual needs, a general application or one

application per process can be defined.

Example
— MAT_SEL_1 (material selection shoulder)
— MAT_SEL_2 (material selection rack)
— MAT_SEL_3 (material selection packaging)

Use
The applications defined here are used for the creation of material
groups and material allocation. These assignments are made in
the Softproviding Core application menu under DGS > DGA > Ap-
plications > Material Groups. For more information, refer to the
Softproviding Core user documentation DGS - Device Gateway Sys-
tem.

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.

Process Data – Softproviding Core Configuration Guide 16/112

Think ahead. Go there.

Field Description
Material button Style Style for the button of the material in the RAF application (quick
selection). If no style is defined, the style from the RAF Work-
bench is used.
Material button Style Active Style for the active material. If no style is defined, the Style But-
tonSmallSelected is used.
Material button Style Not Ac- Style for the button of the material if it is inactive. If there is no
tive order, the button of the material is set inactive. In this case the
button gets this style.
Condition number Material DPS condition number that is called up when the material is se-
(push button) lected. If no condition is defined, condition 1 is called.
Text Alphanumeric key with a maximum of 40 characters to describe
the Application.

3.2 Organization
Open the menu item Organization in the implementation guide as follows:

Menu Softproviding Core > Logistics > Process Data Acquisition > Organi-
zation

The settings for the following tables are described in this section:
— Plants/storage locations
— Terminals
— Numbers range

Use
Enhanced settings, plant settings and/or terminal-dependent settings for data acquisition are applied
in these tables. The most important settings are:
— Dialog control
— Batch consideration
— Order pair formation
— Stock evaluation
— Terminal functionalities

Activities
Entries can be created by selecting the button New Entries.

Process Data – Softproviding Core Configuration Guide 17/112

Think ahead. Go there.

3.2.1 Plants / Storage Locations

Use
Depending on the plant, organizing the process data requires different settings. These are, primarily:
— Quantity calculation (target) and stock updating
— Order confirmation
— Behavior in the dialog
— Functions for batch entry
— Order pair formation

The stock updating, i.e. updating stock levels in the table /SPDGS/PDAT, can be carried out synchro-
nously (immediately) or asynchronously. The setting is applied in the field Stock update posting.

If the quantities of co-products and by-products are to be included in the material quantity in the
order confirmation, appropriate indicators must be set and a CMOD enhancement implemented (see
descriptions of the fields in the table).

The system behavior when entering data during further processing can be influenced by several in-
dicators. Examples include:
— Permit incomplete operations
— Warning of missing actual entry

The order pair formation function is activated in this table and controlled via detailed settings. Order
pair formation enables several orders to be linked together. Entries are thereby automated and PDA
operations can be automatically created.

3.2.1.1 Plants
Field Name Description
Plant The plant serves as a production site for a company.
ALE active Set this indicator in order to activate ALE data distribution be-
tween a main system and a PDA subsystem (PDC system).
PDA subsystem This indicator determines which role this system assumes in the
plant. Activate this indicator if this system assumes the role of
the PDA subsystem.
GR zone In this field, enter the workplace that signifies the WE zone
(goods receipt zone)

Use
This information is needed in order to e.g. select the right inspec-
tion plan for goods receipt in quality management.

Note
This is only valid for DGA-GR. Not relevant for DPS-RAF!

Process Data – Softproviding Core Configuration Guide 18/112

Think ahead. Go there.

Field Name Description

Input help
All defined workplaces are displayed in F4 input help.
Fixed strategy If this indicator is set, the PDA strategy used first is fixed in the
entry document after an entry. The acquisition strategy can
therefore no longer be changed in the application after the first
entry operation for the order.

If the indicator is not set and if the strategy is, for instance,
changed several times during Further Processing Entry, the entry
and calculation results can no longer be tracked.

Recommendation
For this reason, Softproviding AG recommends fixing the strat-
egy, i.e. setting this indicator.
Target from BP (concerns only If this indicator is set, input target quantities are also calculated
IQOW) from the by-product entry. The entry of main or co-products is not
affected.

Note
This setting only has an effect in the strategy IQOW.

Dependencies
The calculation of the input quantities for IQOW is influenced by
the following two indicators:
— Target from BP
— Total incl. BP

The combination of both indicators has the following conse-

quences (100% of the planned quantity is entered as the actual in
the output):

Target from BP Total incl. BP Target input

X X = 100%
= 100%
X < 100%
X > 100%

Example
See F1 Help for this field.
Total incl. BP If this indicator is set, the planned quantity of by-products is in-
cluded in the total output. When entering main, co- and by-prod-
ucts, this is compared with the actual quantity, providing the ra-
tio for the target input.

Note
This setting only has an effect in the strategy IQOW.

Process Data – Softproviding Core Configuration Guide 19/112

Think ahead. Go there.

Field Name Description

Dependencies
The calculation of the input quantities for IQOW is influenced by
the following two indicators:
— Target from BP
— Total incl. BP

The combination of both indicators has the following conse-

quences (100% of the planned quantity is entered as the actual in
the output):

Target from BP Total incl. BP Target input

X X = 100%
= 100%
X < 100%
X > 100%

Example
See F1 Help for this field.
Stock update posting The entry in this field decides whether the posting of PDA opera-
tions is to take place synchronously or asynchronously. Synchro-
nous posting takes place immediately, while asynchronous post-
ing takes place later.

Dependencies
The settings for this field are only relevant if the Softproviding
Core stock update is activated for each plant / storage location.
The Customizing settings for this can be applied under Softprovid-
ing Core > Logistics > Process Data Acquisition > Organization >
Plants/Storage Locations (set the following indicator: DGS stock
evaluation active).

Background
In the case of synchronous posting of the stock update in the table
/SPDGS/PDAT, the stock is updated for every PDA operation im-
mediately.
In the case of asynchronous posting, the relevant PDA operations
for the stock changes are written to the intermediate table
/SPDGS/PDAT_DELT. The program /SPDGS/R_PDAT_UPDATE
updates the Softproviding Core stock in the table /SPDGS/PDAT
(PDA stock). The program /SPDGS/R_PDAT_UPDATE must be
planned as a job in order to do this. It can also be started manually
if needed (deactivate Background processing indicator).
Co-products Activate this indicator if the quantities of co-products are to be in-
cluded in the material quantity in the order confirmation.

Process Data – Softproviding Core Configuration Guide 20/112

Think ahead. Go there.

Field Name Description

Dependencies
In order to fill the material quantity with quantities from Further
Processing Entry in the confirmation, the CMOD enhancement
CONFPP01 (PP order confirmation: determine customer-specific
proposed values) must be activated with the component
EXIT_SAPLCORF_101. The following line must be included in the
code: include /spdgs/zxcofu11_userexit”.
By-products Activate this indicator if the quantities of by-products are to be
included in the material quantity in the order confirmation.

Dependencies
In order to fill the material quantity with quantities from Further
Processing Entry in the confirmation, the CMOD enhancement
CONFPP01 (PP order confirmation: determine customer-specific
proposed values) must be activated with the component
EXIT_SAPLCORF_101. The following line must be included in the
code: “include /spdgs/zxcofu11_userexit”.
New confirmation Indicator.

If this indicator is set, the new order confirmation program logic is

called up in the relevant applications of the Process Data Cockpit.

Dependencies
This setting is only relevant in connection with the use of the new
PDA program logic. This is called up if the PDA new indicator is
set in the PDA program logic customizing table. This program
logic is available from release v6.00.
Batch entry Production batches can be created in production for further pro-
cessing orders. This means that the total quantity to be produced
for the order is divided into smaller amounts.

Prerequisites
— Plant-dependent activation of this functionality by setting
this indicator
— Definition of a target batch size in the material master data
(tab Process Data Acquisition) for the material to be pro-
duced (output).
— If applicable, definition of a minimum batch size in the ma-
terial master data (tab Process Data Acquisition) for the ma-
terial to be produced (output) (optional).

Use
If these prerequisites are met, these production batches can be
created in the application when entering the bill of materials com-
ponents (= input materials). The production batches are saved in
the table /SPDGS/MPBH.

Process Data – Softproviding Core Configuration Guide 21/112

Think ahead. Go there.

Field Name Description

The production batches are calculated on the basis of a standard
calculating rule within the program. This can be adapted to spe-
cific customers via BAdIs (Business Add-Ins). This BAdI
/SPDGS/BADI_BATCH_CALC is described in the corresponding
chapter in this document.

Documentation
Examples of calculating the production batches are available in
the user documentation Process Data.
Batch staging Batch staging describes the process of manually selecting batches
for the components of a production order.

Use
Batch staging can be used in Further Processing Entry after corre-
sponding activation (see prerequisites). This is done after the en-
try is opened (transaction /SPDGS/PDAON) at the level of the in-
put components by selecting the button Batch Staging. Batch
staging is a function for manually staging batches; it is not a
batch determination tool. After the batches are staged for the de-
sired components, these are searched for at the end of the order
and written into the automatically created PDA data records. This
function can reduce the manual effort of making entries when
concluding production orders.

Prerequisites
— Plant-dependent activation of this functionality by setting
this indicator.
— Activation of the Batch staging dialog for each terminal and
user (Process Data Acquisition > Organization > Terminal).

Notes
The batches staged are saved in the table /SPDGS/CHBE.

The number intervals of the following number range objects are to be

checked and, if necessary, to be created:
— /SPDGS/CA (batch activation)
— /SPDGS/CB (batch staging)

The functionality of batch staging is useful for input components

where the quantity is calculated automatically based on the order
strategy when the order is completed and the PDA data records are
created automatically (example: IQOW, IPOW).

Batches can be staged externally via RFC-compatible API (Appli-

cation Programming Interface).
Allow incomplete operations When concluding an order, PDA operations can be generated au-
tomatically (depending on the acquisition strategy). If these oper-
ations are incomplete (e.g. due to a missing batch), they must be

Process Data – Softproviding Core Configuration Guide 22/112

Think ahead. Go there.

Field Name Description

processed. When orders are concluded in Further Processing En-
try, a pop-up appears in order to enable this processing.

Caution
If this indicator is set, the operations that are to be created auto-
matically may also be generated as incomplete operations. How-
ever, these incomplete data records must be processed. This is
done using the transaction /SPDGS/PDAO or with the report
/SPDGS/R_PP_CONFIRM_AND_END (confirmation of production
orders).

PDA data records that have not been corrected and are thus in-
complete cannot be posted in Materials Management.

Note
The BAdI /SPDGS/BADI_PDAGENO (enhancement spot
/SPDGS/BADI_PA_GENERIC_OPS) can be used to modify incomplete
records according to customer logic.
Caution: Missing actual entry If this indicator is set, it is checked at the end of further pro-
(FPO) cessing orders whether items (input or output) are present that
are provided for entering actual quantities but for which no entry
has been made.

When the indicator is set, a pop-up with a corresponding message

appears at the end of the order for Further Processing Entry. How-
ever, if the report /SPDGS/R_PP_CONFIRM_AND_END (confir-
mation of production orders) is used, this check does not take
place.
Caution: Missing actual entry If this indicator is set, it is checked at the end of the order whether
(REM) items are present that are provided for actual entries but for
which no entry has been made.

Use
This indicator is considered in mass production entry.
Go to output if only one single If this indicator is set, the list of outputs is skipped in Further Pro-
item cessing Entry if the order has only one output item.

Recommendation
Activate this indicator if you want to spare the user one unneces-
sary step.
Further processing is locked If this indicator is set, the order is locked if there is a data entry for
at data entry input or output materials. For instance, the order may then only
be called up with transaction CO03.
Order pairs Order pair formation enables several orders to be linked together.
Entries are thereby automated and PDA operations can be auto-
matically created. This significantly reduces the manual effort
needed to make entries.

Process Data – Softproviding Core Configuration Guide 23/112

Think ahead. Go there.

Field Name Description

Linking is performed automatically or manually together with the

indicator to the preceding and/or for the following order (material
master data, tab Process Data Acquisition).

Note
For more information, see the explanations on order pair formation at
the end of this table.

Use
Order pairs can be formed between disassembly and/or further
processing orders. Two or more orders can be linked together. The
settings for this field activate the order pair formation function
and define the degree of compatibility that must be present for al-
location to occur.

Input help
The following allocations are possible
— Inactive
— Active (allocation via material and batch)
— Active (allocation via material and batch or material only)

Prerequisites
— Activation of pair formation in this field
— The indicator for the preceding or following order is set for
the desired material in the material master data (tab Process
Data Acquisition).

Example
Pair formation between a disassembly order (DAO) and a further
processing order (FPO) must be performed such that the DAO out-
put is posted on the FPO.
— DA order = 10040
— FP order = 10060
— DAO output = material 250

The indicator For preceding order must be set in the material mas-
ter data for material 250. If pair formation is activated with auto-
matic allocation, once the input quantity for material 250 has
been entered (order 10060), this quantity is automatically posted
to the DA order (material 250 > DAO output).
Orders exclusion Exclusion criteria for production orders during pair formation.

Use
This indicator can be used to define which production orders are
excluded from pair formation

Process Data – Softproviding Core Configuration Guide 24/112

Think ahead. Go there.

Field Name Description

Background information
Orders with a certain status (e.g. Technically completed) are usu-
ally not used for pair formation. An additional setting for pair for-
mation with exclusion criteria is therefore useful so that not all
orders are offered for pair formation.

The following settings are possible:

— "C": completed production orders are excluded
(/SPDGS/MPAK-MPAST = 'C').
— "T": technically completed production orders are excluded.
— "X": both statuses are checked for exclusion.

The following statuses are always checked for all three variants:
— Order released
— Deletion indicator

The domain values of this field can be extended via an append.

The production orders can thus be checked via a customer-spe-
cific logic in the method /SPDGS/BADI_ORDER_PAIR-FIL-
TER_ORDER.
Manual order pair formation If this indicator is set, order pairs are formed via manual alloca-
tion. The user can see the corresponding buttons in the order
overview for Further Processing Entry.
DAO pair formation allowed If this indicator is set, the pair formation function can also be per-
formed between disassembly and further processing orders.

Production Order
Field Name Description
No automatic pair formation If this option is selected, there will be no pair formation for pro-
duction orders.
Basic start date = basic start When searching for order pairs, the system will only look for or-
date ders with the same basic start date if this option is selected.
Scheduled start = scheduled When searching for order pairs, the system will only look for or-
start ders with the same scheduled start if this option is selected.
Customer-specific If this indicator is set, customer-specific rules for order pair for-
mation can be defined. A customer-specific program must be writ-
ten for this.

In the standard settings, orders with the same order start date
and/or scheduled start date can be used to form pairs. If pair for-
mation is to take place based on other fields, e.g. Release Date or
MRP Controller, a customer-specific program must be developed.
For this, the BAdI /spdgs/badi_order_pair must be implemented.

Process Data – Softproviding Core Configuration Guide 25/112

Think ahead. Go there.

Goods Receipt for Purchase Order

Field Name Description
No pair formation for pur- If this option is selected, pair formation between purchase orders
chase order (goods receipts) on the one hand and disassembly orders and fur-
ther processing orders on the other hand is not allowed.
Delivery date = basic start If this option is selected, order pair formation is possible between
date goods receipts for purchase order and disassembly orders or fur-
ther processing orders. Pair formation will take place if the deliv-
ery date (purchase order item) and the basic start date (disassem-
bly order or further processing order) are identical.
Delivery date = scheduled If this option is selected, order pair formation is possible between
start goods receipts for purchase order and disassembly orders or fur-
ther processing orders. Pair formation will take place if the deliv-
ery date (purchase order item) and the scheduled start (disassem-
bly order or further processing order) are identical.
Customer-specific If this indicator is set, customer-specific rules for order pair for-
mation can be defined. A customer-specific program must be writ-
ten for this.

In the standard settings, orders with the same order start date
and/or scheduled start date can be used to form pairs. If pair for-
mation is to take place based on other fields, e.g. Release Date or
MRP Controller, a customer-specific program must be developed.
For this, the BAdI /spdgs/badi_order_pair must be implemented.

Goods Issue for Delivery

Field Name Description
No pair formation at delivery If this option is selected, pair formation between disassembly or-
ders and further processing orders on the one hand and deliveries
(goods issues) on the other hand is not allowed.
Material staging date = basic If this option is selected, order pair formation is possible between
start date disassembly orders or further processing orders and deliveries
(goods issues). Pair formation will take place if the basic start date
(disassembly order or further processing order) and the material
staging date (delivery) are identical.
Material staging date = sched- If this option is selected, order pair formation is possible between
uled start disassembly orders or further processing orders and deliveries
(goods issues). Pair formation will take place if the scheduled
start (disassembly order or further processing order) and the ma-
terial staging date (delivery) are identical.
Customer-specific If this indicator is set, customer-specific rules for order pair for-
mation can be defined. A customer-specific program must be writ-
ten for this.

In the standard settings, orders with the same order start date
and/or scheduled start date can be used to form pairs. If pair for-
mation is to take place based on other fields, e.g. Release Date or

Process Data – Softproviding Core Configuration Guide 26/112

Think ahead. Go there.

Field Name Description

MRP Controller, a customer-specific program must be developed.
For this, the BAdI /spdgs/badi_order_pair must be implemented.

Change ID for Traceability

Field Name Description
Field name The contents of this field name are written in the Container field
in the /SPDGS/CHANGEID table.

Prerequisites
A new change ID was created.

The contents itself is imported from the customizing table of field

SPDGS/TCHANGEID-CHGCO.

Note
This field is only relevant for the so-called “old” Change ID Control
application. This was developed for releases v5.30 and v5.40. Re-
leases v5.40 and higher use the so-called “new”, further developed
Change ID Control application.

PDA Weighing Strategy

Common dimensional UoM All dimensional quantities in the quota calculation are converted
into this unit. A weight unit such as KG or pounds is usually used
for input.
Common non-dimensional Materials that are calculated in the quota and are CWM-active
UoM must be converted into this unit. A unit such as piece (ST) is usu-
ally used for the input.

3.2.1.2 Storage Locations

The indicator DGS stock evaluation active can be activated in the following table for each plant and
storage location.

Field Name Description

Storage locations The storage location is an organizational unit which allows a dis-
tinction to be made between the different inventories within a
plant.
Description of storage loca- The name of the storage location is entered in this field.
tion
DGS stock evaluation active If this indicator is set, the PDA operations for batches are updated
in the table /SPDGS/PDAS and are only removed again once the
event Batch complete occurs. A stock evaluation can be generated
in the double unit of measure with this data. In addition, the stock

Process Data – Softproviding Core Configuration Guide 27/112

Think ahead. Go there.

Field Name Description

per unit of measure is updated in the table /SPDGS/PDAT (cumu-
latively). When the event Batch complete occurs, the stock update
for the batch is reset or deleted.

3.2.1.3 Further Information: Pair Formation

Indicator Preceding/Subsequent
In addition to the Customizing settings mentioned above, the following two indicators in the material
master data are important for order pair formation. They are available in the tab Process Data Acqui-
sition.

Field Names Description

preceding If a material is used as input for an order, the system automatically
creates a reference to the output of a suitable preceding order. In-
put entries for this material are then simultaneously posted on the
output of the previous order.

Note
This indicator can only be activated if automatic pair formation is ac-
tive in DGS Customizing. This indicator does not play any role in man-
ual pair formation.
subsequent If a material is used as output for an order, the system automati-
cally creates a reference to the input of a suitable subsequent or-
der. Output entries for this material are simultaneously posted on
the input of the subsequent order.

Note
This indicator can only be activated if automatic pair formation is ac-
tive in DGS Customizing. This indicator does not play any role in man-
ual pair formation.

3.2.2 Terminals
Use
In this section, you can activate and define various functions per terminal ID and user name, e.g.:
— PDA strategy (as default value)
— Hiding and unhiding tabs in the Process Data Cockpit
— Hiding and unhiding function buttons in the Process Data Cockpit (e.g. Component Replace-
ment)
— Change ID (for releases v5.30 and v5.40 only)

Process Data – Softproviding Core Configuration Guide 28/112

Think ahead. Go there.

— Label printing

Data acquisition strategies (PDA strategies) are a key function in Further Processing Entry. They de-
termine whether an input or output material is entered, calculated, or just displayed. The strategy is
assigned to the output material in the material master data and/or in this table. Assigning to the ma-
terial takes priority here. If no strategy is entered at either point, the system default (= $SYS) is used.

The component replacement can be used in Further Processing to replace one or more bill of materi-
als components provided for production with other components (interchangeable parts).

The access sequence for this table follows the following order:
— Terminal ID + user name
— User name + initial terminal ID (or *)
— Terminal ID + initial user name (or *)

Activities
Entries can be created by selecting the button New Entries.

Table Fields
Field Name Description
Terminal ID The terminal ID corresponds to the computer name in Windows
and unambiguously identifies a computer in the local network.

Use
The transaction control is dependent on the terminal ID. If no en-
try is found in this table for the calling terminal, the generic entry
(*) is searched for and used.
User name The name of the user (SAP login name) is required to log in to the
terminal. The username can also be the entry * (= asterisk). This
entry is then valid for all user logins at this terminal.

General
Field Name Description
PDA strategy 4-character abbreviation to designate a PDA strategy.

Value selection
— $SYS System default (enter everything)
— IGOW Input via output actual - enter output
— IPOP Input planned = actual - output planned = actual
— IPOW Input planned = actual - enter output
— IQOW Input via quota - enter output
— IWOG Enter input - output via input actual
— IWOP Enter input - output planned = actual
— IWOQ Enter input - output via quota
— IWOW Enter input - enter output

Process Data – Softproviding Core Configuration Guide 29/112

Think ahead. Go there.

Field Name Description

Note
For further details, please refer to the information in the section
“Strategies” further up in this chapter and the F1 documentation on
this field.
Scanner The entry in this field specifies how the scanner is connected to
the terminal.

Value selection
— Serial scanner
— Keyboard scanner
— Blank

A serial connection is controlled by software. The Dynpros

(screens) remain in the original state. The focus (cursor)
(SETCURSOR) is also as normal.

The keyboard type refers to a scanner that is looped through on

the keyboard cable. A device is looped through if it is installed be-
tween two plugs. The new device is operated but the old connec-
tion (keyboard - PC) is looped through, i.e. it remains in place. As
this only simulates keyboard input, Further Processing Entry gen-
erates separate input fields in this case, on which the focus (cur-
sor) is placed.

If the entry is empty, no scanner is used.

Check external ID If this indicator is set, the content of the field external identifica-
tion (external animal number) is checked against the table Exter-
nal Identification Value List (/SPDGS/MPEN) in the entry window
during further processing. The maintenance dialog for this table is
called /SPDGS/V_MPEN.
No input entry If input entry has been deactivated for a terminal, the following
message is displayed in the SAP GUI during process data entry
(further processing order / process order): Input entry is not per-
mitted.

If input data entry has been deactivated for a terminal, the follow-
ing message is displayed in the SAP GUI during process data entry
(further processing order / process order): Input entry is not per-
mitted.

If input entry has been deactivated for a terminal, the following

buttons are hidden in the DPS-RAF during process data entry (fur-
ther processing order / process order / disassembly order):
— Input and process
No output entry If outgoing data entry has been deactivated for a terminal, the fol-
lowing message is displayed in the SAP GUI during process data

Process Data – Softproviding Core Configuration Guide 30/112

Think ahead. Go there.

Field Name Description

entry (further processing order / process order): Output recording
is not permitted.

If outbound data entry has been deactivated for a terminal, the

following button is hidden in the DPS-RAF during process data
entry (further processing order / process order / disassembly or-
der):
— Output

Functions in Further Processing Entry

Field Name Description
Change ID active Note
This field is only relevant for the so-called "old" Change ID Control
application. This was developed for releases v5.30 and v5.40. Re-
leases v5.40 and higher use the so-called "new", further developed
Change ID Control application.
Manual quality inspection Setting this indicator activates the quality inspection function
across the board in Further Processing Entry.

Prerequisites
The relevant inspection type for input and output must also be set
in Softproviding Customizing in order for this function to be used.
This setting can be found under Softproviding Core > Logistics >
Process Data Acquisition > Orders > Quality inspection.
Direct posting of quota In Further Processing Entry, target values are calculated for spe-
cific PDA strategies, e.g. IQOW, IGOW, IWOQ, IWOG, after actual
quantities are recorded and said values are stored in the table
/SPDGS/MPCT. When the production order is completed, PDA data
records are created using the target values stored in the table
/SPDGS/MPCT.

By setting this indicator, it is possible to generate PDA data records

immediately without having to create target values and make en-
tries in the table /SPDGS/MPCT.

Note
If the indicator is set, every actual entry also directly leads to gener-
ated PDA data records. It should be noted that, on the one hand, this
increases the number of PDA data records, and on the other hand the
immediate preparation of the generated PDA data records can have a
negative impact on performance.

Recommendation
If direct preparation of the generated PDA data records is not nec-
essary from an operational standpoint, we recommend not setting
the indicator and thus using the creation of target values via the
table /SPDGS/MPCT.

Process Data – Softproviding Core Configuration Guide 31/112

Think ahead. Go there.

Field Name Description

Note
If the functionality of the new PDA program logic is used, this setting
is no longer relevant. You can check the configuration in customizing
as follows: Softproviding Core > Logistics > Process Data Acquisi-
tion > Control Settings > PDA Program Logic.
Double UoM is checked at When quantities are entered in the Double UoM field, it is checked
weighing whether an appropriate conversion factor is maintained, provided
this indicator is set. Without a conversion factor between base
UoM and alternative UoM it is not possible to enter a quantity for
this field.
Order Pairs: Always select or- If order pair formation is active (field Order Pair in the table Plants
der manually / Storage Locations) and if several suitable preceding or subse-
quent production orders are found during entry, the user must
manually select an order for pair formation. A corresponding pop-
up is displayed in the application. This process must be repeated
for every entry relating to the same order. However, if this indica-
tor is set, it is no longer necessary to manually choose the order
for pair formation in further entries. The program notes the order
assigned in the first entry and automatically uses this in further
entries.
Production batch status will Production batches can have status A (open), B (in process) or C
not be updated (completed). If a PDA data record is created for a production
batch, the status will change automatically from A (open) to B (in
process).

Use
If this indicator is set, the production batch will retain status A
(open).
PDA job administration and If this indicator is set, buttons for job management and for acti-
activation vating/deactivating the PDA frontend functions (frontend = user
PC) are displayed in the dialogs for Process Data Acquisition (fur-
ther processing and disassembly).

Use
The PDA frontend function includes the automatic entry of pro-
cess data.

The following buttons are displayed or hidden accordingly:

— Jobs
— PDA in
— PDA out

Hide Function Buttons in the Transaction

Field Name Description
Confirm and/or complete If this indicator is set, the confirm and/or complete function is inac-
tivated in Further Processing Entry (transaction /SPDGS/PDAON.

Process Data – Softproviding Core Configuration Guide 32/112

Think ahead. Go there.

Field Name Description

This means, the Confirm and/or complete button is hidden at order

level and the functionality will therefore not be available.
Manual order pair formation If this indicator is set, the manual order pair formation function is
inactivated in Further Processing Entry (transaction
/SPDGS/PDAON
Change strategy If this indicator is set, the change strategy function is inactivated
in Further Processing Entry (transaction /SPDGS/PDAON.

This means, the Change strategy button is hidden at order level

and the functionality will therefore not be available.

Note
A strategy change for an order can be made temporarily or perma-
nently in Further Processing Entry. An adapted strategy is adopted
permanently if the Save function is selected in the Change strategy
function in the application. The changed strategy is then retained
even if the processing session is restarted.
Origin of strategy If this indicator is set, the origin of strategy function is inactivated
in Further Processing Entry (transaction /SPDGS/PDAON.

This means, the Origin of strategy button is hidden at order level

and the functionality will therefore not be available.
Recalculate target If this indicator is set, the recalculate target function is inactivated
in Further Processing Entry (transaction /SPDGS/PDAON.

This means, the Recalculate target button is hidden at order level

and the functionality will therefore not be available.
Communication with WM This function is no longer used. The indicator should be set. The
button is hidden in the application.

Former use
If this indicator is set, the communication with WM function is in-
activated in Further Processing Entry (transaction
/SPDGS/PDAON.

This means, the Communication with WM button is hidden at order

level and the functionality will therefore not be available.
Manage production batches If this indicator is set, the manage production batches function is
inactivated in Further Processing Entry as well as in data entry
for the production order (transaction /SPDGS/PDAON.

This means, the Manage production batches button is hidden at or-

der level and the functionality will therefore not be available.
Batch staging dialog Batch staging describes the process of manually selecting batches
for the components of a production order.

Process Data – Softproviding Core Configuration Guide 33/112

Think ahead. Go there.

Field Name Description

Use
Batch staging can be used in Further Processing Entry after corre-
sponding activation (see “Prerequisites” below). This is done after
data entry is called up (transaction /SPDGS/PDAON) at the level
of the input components by selecting the button Batch staging.
Batch staging is a function for manually staging batches; it is not
a batch determination tool. After the batches are staged for the
desired components, these are searched for at the end of the order
and written into the automatically created PDA data records. This
function can reduce the manual effort of making entries when
concluding production orders.

Prerequisites
— Plant-dependent activation of this function (Process Data
Acquisition > Organization > Plants/storage locations)
— This Batch staging dialog indicator must not be set

Notes
The batches staged are saved in the table /SPDGS/CHBE.

The number intervals of the following number range objects are to be

checked and, if necessary, to be created:
— /SPDGS/CA (batch activation)
— /SPDGS/CB (batch staging)

The functionality of batch staging is useful for input components

where the quantity is calculated automatically based on the order
strategy when the order is completed and the PDA data records are
created automatically (example: IQOW, IPOW).

Batches can be staged externally via RFC-compatible API (Appli-

cation Programming Interface).
Component replacement Setting this indicator deactivates the Component Replacement
function during data entry in the SAP GUI as well as in the DPS-
RAF.

Use
The component replacement can be used in Further Processing to
replace one or more BOM components provided for production
with other components (= interchangeable parts). These materials
are defined as alternative components.

Prerequisites
In order to perform component replacement in the application, the
replacement relationship between the components to be replaced
and the replacement material must be defined in the master data

Process Data – Softproviding Core Configuration Guide 34/112

Think ahead. Go there.

Field Name Description

table (view cluster /SPDGS/VC_ATKO). This view can also be
opened via the transaction /N/SPDGS/AT01.

This master data table may be called up in the Softproviding Core

application menu under Softproviding Core > Logistics > Process
Data Acquisition > Processing > Component Replacement

Note
See detailed description of this table in the chapter “Other”.

Enhancements
Further conditions for component replacement can be defined on
a customer-specific basis using BAdI. This function is described in
more detail below in the section “Component Replacement”.
Unplanned goods movement If this indicator is set, the unplanned goods movement function is
inactivated in Further Processing Entry (transaction
/SPDGS/PDAON as well as in DPS-RAF).

This means, the Unplanned goods movement button is hidden at

order level and the functionality will therefore not be available.
This goes for input as well as output materials
Reactivate order If this indicator is set, the reactivate order function is inactivated
in Further Processing Entry (transaction /SPDGS/PDAON.

This means, the Reactivate order button is hidden at order level

and the functionality will therefore not be available.

Background information
In Further Processing Entry, orders can be highlighted and put on
hold by selecting the Hold order button (orders are highlighted in
red color). These orders can then be excluded from selection when
the application is called up. They can later be reactivated, mean-
ing the on-hold status is undone.

Example
Sausages are put in the smoking chamber for smoking. The smok-
ing process typically takes four to six weeks. For this period, the
order can be put on hold. Once the smoking process is completed,
the order can be activated again (i.e. reactivated) for further pro-
cessing.
Hold order If this indicator is set, the hold order function is inactivated in Fur-
ther Processing Entry (transaction /SPDGS/PDAON.

This means, the Hold order button is hidden at order level and the
functionality will therefore not be available.

Process Data – Softproviding Core Configuration Guide 35/112

Think ahead. Go there.

Field Name Description

Background information
In Further Processing Entry, orders can be highlighted and put on
hold by selecting the Hold order button (orders are highlighted in
red color). These orders can then be excluded from selection when
the application is called up.

Example
Sausages are put in the smoking chamber for smoking. The smok-
ing process typically takes four to six weeks. For this period, the
order can be put on hold.

Functions in the PDA Data Cockpit

Field Name Description
Mass processing active This indicator is used to activate the functions for mass pro-
cessing in the PDA Data Cockpit. This concerns the following but-
tons for processing PDA operations.

Functions
— Delete
The deletion indicator in the PDA operation is set
— Reverse
The goods movement of the PDA operation is reversed
— Post
The goods movement of the PDA operation is carried out
— Print
PDA operations can be printed

If the indicator is not set, the mentioned buttons are hidden in the
application.

However, the activation of mass processing only affects the

global display of the PDA operations that are displayed after the
transaction is started. Individual PDA operations that can be
called up separately after selecting a process (e.g. further pro-
cessing, purchase order, inventory) remain unaffected by this set-
ting.
Check chain Indicator for controlling an allowed deletion or reversal of gener-
ated PDA data records.

Use
With order pair formation or quota calculation, PDA data records
can be generated based on other, manually created, PDA data rec-
ords. You can use this indicator to control whether these gener-
ated PDA data records can be deleted or reversed directly or only
automatically using the source PDA data record.

Process Data – Softproviding Core Configuration Guide 36/112

Think ahead. Go there.

Field Name Description

Indicator is set
— It is not possible to manually delete or reverse generated
PDA data records. These data records are automatically de-
leted or reversed if the source PDA data record is deleted or
reversed.

Indicator is not set

— Generated PDA data records can be deleted or reversed
without checking, regardless of whether they originate
from order pair formation or quota calculation.

Hiding the Tab in the Transaction

Depending on the process (e.g. Further Processing Entry, Disassembly Process Entry, or Inventory
Count Data Entry), operation data are not only stored in table /SPDGS/PDAO but also in other tables
(see the overview below). These table entries may be displayed in the PDA Data Cockpit by deactivat-
ing said indicators (or activate them if they are not to be displayed).

Tab Description
Tab of table PDAOE1 If you activate or inactivate this indicator, the tab Customer-Spe-
cific Additional Fields is hidden or displayed in the PDA Data Cock-
pit when a PDA process is called. The contents of table
/SPDGS/PDAOE1 (PDAO Custom Extension 1) are output in this
tab.

This table is delivered by Softproviding in the standard system

with at least the fields Client, Plant and PDA Process. The table can
be extended by customers for individual purposes.
Tab of table PDAT If you activate or inactivate this indicator, the tab PDA Stock Up-
date is hidden or displayed in the PDA Data Cockpit when a PDA
process is called up. The contents of table /SPDGS/PDAT are out-
put in this tab.

This table is closely related and dependent to the Process Data

Acquisition table /SPDGS/PDAO (PDA operation). This table is
filled under certain conditions. The entries in table /SPDGS/PDAT
are used for real inventory management of the double unit of
measure and can be used for corresponding evaluations.
Tab of table MPCT If you activate or inactivate this indicator, the tab Calculated Tar-
get from Physical Data Entries is hidden or displayed in the PDA
Data Cockpit when a PDA process is called up. The contents of ta-
ble /SPDGS/MPCT are output in this tab.

In Further Processing Entry, so-called target values are calculated

for certain PDA strategies such as IQOW, IGOW, IWOQ, IWOG af-
ter recording actual quantities and stored in the table
/SPDGS/MPCT. When the production order is completed, PDA

Process Data – Softproviding Core Configuration Guide 37/112

Think ahead. Go there.

Tab Description
data records are created based on the target values stored in table
/SPDGS/MPCT.

Note
If the functionality of the new PDA program logic is used, this setting
is no longer relevant. You can check the configuration in customizing
as follows: Softproviding Core > Logistics > Process Data Acquisi-
tion > Control Settings > PDA Program Logic.
Tab of table PDAOs If you activate or inactivate this indicator, the tab Generated PDA
Operations is hidden or displayed in the PDA Data Cockpit when a
PDA process is called up. The contents of table /SPDGS/PDAO are
output in this tab.

Generated PDAOs are automatically created by the program. This

is the case, for example, when a PDA data record is reversed. The
reversal document is then generated.
Tab of table PDOF If you activate or inactivate this indicator, the tab PDA Operation
Flow is hidden or displayed in the PDA Data Cockpit when a PDA
process is called. The contents of table /SPDGS/PDOF are output
in this tab.

These tables document the flow of operations of entered source

and target quantities. This table is only filled when using special
DPS processes.

Label Printing from Order Overview

Field Name Description
Printer In order to be able to print out labels from the order overview, in-
Program formation on the printer, printing program, form routine, form
name and label number is needed.
FORM routine
Form name The following standard programs are delivered:
— SPDGS/PMON_LABELPRINT
— /SPMEAT/PMON_LABELPRINT

The form routine for both programs is ORDER. It will call up

PrintMonitor.

Note
The form name combines the RFC destination and the PrintDesigner
layout

Example
— PRMON_SNB009;TPE.LAY

However, this name is only valid for the two programs mentioned
above. Other names can also be used for individual customers.

Process Data – Softproviding Core Configuration Guide 38/112

Think ahead. Go there.

Field Name Description

Number of labels Number of labels printed for the same document.

Dependencies
If label printing is done via the SAP standard spool, the number of
labels is limited to 255. Up to 9999 identical labels can be printed
via the PrintMonitor.

3.2.3 Number Ranges

Use
In this step, the number intervals are defined for the following number range objects:
— /SPDGS/OPR (DGS: PDC operation)
— /SPDGS/JOB (DGS: Job for AutoClient)

After the IMG activity has started, a new entry can be created using the buttons Intervals and Add
interval.

Field Name Description

No. This number for the number range unambiguously identifies a
number range interval within an object or sub-object.
From number 0000000001
To number 9999999999
Number level For internal numbers ranges the current number field shows the
number that was assigned last.
Ext This indicator determines whether an external or internal number
range interval is concerned.

For internal number range intervals, the number assignment is

performed via the SAP system. A number is assigned automati-
cally. The automatically assigned number is between the “from”
number and the “to” number. In the case of external number as-
signment, the user must enter a number. The number entered
must be between the “from” number and the “to” number.

Note
Not marking this field will lead to internal number assignment being
performed.

Note – Transport
Number range objects can be transported via the menu item Intervals > Transport. Please note that all
intervals for the selected number range object are first deleted in the target system so that only the ex-
ported intervals are present after the import. The number levels are imported with the value that they have
at the time of the export. Dependent tables are not transported or implemented.

Process Data – Softproviding Core Configuration Guide 39/112

Think ahead. Go there.

3.3 Orders
Open the menu item Orders in the implementation guide as follows:

Menu Softproviding Core > Logistics > Process Data Acquisition > Orders

The settings for the following tables are described in this section:
— Order types
— Item categories
— Component replacement
— Quality inspection

Use
The most important settings in these tables are:
— Assign order type to order category
— Control via item categories
— Enhancement options for component replacement

Activities
Entries can be created by selecting the button New Entries.

3.3.1 Order Types

Use
In this table, the order types for process data acquisition (e.g. in Disassembly and Further Processing)
are activated on a per-plant basis. This is done by assigning the order type to the order category. En-
tries for orders are then possible.

Order types (e.g. PP01) categorize orders according to their use. Parameters that affect the implemen-
tation of the order are defined via the order type.

Table Fields
Field Name Description
Plant The plant serves as a production site for a company.
Order type The order type is the key that differentiates the orders in terms of
their application. The order type is assigned to the order category
in this table.

Process Data – Softproviding Core Configuration Guide 40/112

Think ahead. Go there.

Field Name Description

Input help
All order types – including self-defined ones – are offered to
choose from in the input help.

Procedure
Perform the assignment of order type to order category.

Recommendation
— Assign the order type PP01 to the order category Further
Processing
— Assign the order type ZPP1 (for example) to the order cate-
gory Disassembly
— Assign the order type PI01 (e.g.) to Order category Process
Order

Note
Where applicable, new order types are created in projects. These must
then be correspondingly assigned to the process (order category) in
this table.
Order category The DGS order category distinguishes between production orders
on the basis of their data model and function.

Input help
The following order categories are available:
— Further Processing
— Process Order
— Disassembly
— Purchase Order (to be used internally only)
— Delivery (to be used internally only)

Use
The order category is used as a distinguishing criterion in Custom-
izing and controls the functionality in dialog and remote applica-
tions.

Recommendation
See the description above in the field Order type.
Posting date The settings in this field define the posting date for the confirma-
tion. The confirmation itself is completed in the respective appli-
cation (Disassembly/Further Processing).

It may be necessary for organizational reasons to not confirm pro-

duction orders until the following month.

Example
Production orders with entries in April are first confirmed in May.
If the confirmation is then completed in May, the system uses the

Process Data – Softproviding Core Configuration Guide 41/112

Think ahead. Go there.

Field Name Description

actual date as the posting and confirmation date. This means that
the costs for the confirmation are posted in May, which is not cor-
rect in terms of calculation. The actual costs for the confirmation
must be posted in the April period, as the goods movements for
the production order were also completed in April.

Input help
The following settings can be selected:
— SAP Standard (= date)
— Order end date
— Order start date
— Date
— Manual pop-up individual entry (i.e. a posting date must be
entered manually for every individual production order)
— Manual pop-up collective entry (i.e. the posting date applies
to all marked production orders in Further Processing Entry.
The posting date must be entered manually)

Note
If no other entry is selected, the default entry is SAP Standard.

The Manual pop-up (individual and collective) settings are only in-
tended for use with further processing orders, not for disassembly or-
ders. If these settings are applied to disassembly orders, they will have
no effect.

The individual and collective entry pop-up functions are not con-
sidered in the confirmation in a collective run. If these settings are
applied in Customizing, the actual date is always used for the col-
lective run.

A confirmation with a pop-up (individual and collective) is not

currently possible for disassembly orders.

3.3.2 Item Categories

In this section, strategy categories are assigned on a per order type basis for bill of materials item
categories in production orders. Item categories are not dependent on an order type in mass produc-
tion. In all other respects, the explanations provided in this section apply to production orders and
mass production to the same extent.

This table also includes the settings that determine the extent to which the bill of materials item is
entered and/or displayed in Further Processing Entry.

Note
Entry settings are applied at the following points:
— Material master data (tab Process Data Acquisition)

Process Data – Softproviding Core Configuration Guide 42/112

Think ahead. Go there.

— Customizing (Item categories table)

The entry that limits the application to the greatest degree always has priority here. The effect of these
settings is limited to DGS process data acquisition but is not dependent on the interface used (SAP Dialog
or DGA Applets). DGA Applets are touchscreens.

Use
In Further Processing Entry, therefore, various parameters decide how a bill of materials component
can be used. In summary, these parameters are as follows:
— Item category
— Strategy category
— Entry decision
— Indicator backflushed (material master data or work plans)

Table Fields
Field Name Description
Order type The order type is the key that differentiates the orders in terms of
their application.

Input help
All order types – including self-defined ones – are offered to
choose from in the input help.

Procedure
Assign the order type to the desired item category and strategy
category.
Item category The item category enables the items in a bill of materials to be
categorized according to defined criteria.

Use
Categorization enables item-relevant data to be processed. Select-
ing the item categories lets you control e.g. the field selection, se-
lected values for bill of materials maintenance or special system
activities.

Input help
In addition to the SAP standard item categories, item categories
specially created for further processing or disassembly orders are
displayed here.

Note
The item categories additionally used in Softproviding Core and Meat
are created with the SAP standard transaction OPJD (Production >
Production Control > Master Data).

Process Data – Softproviding Core Configuration Guide 43/112

Think ahead. Go there.

Field Name Description

See the explanations at the end of this table.
Item category name The description of the item category is shown in this field.
Strategy category The strategy category defines the properties of an item and deter-
mines the application of an item in Further Processing Entry de-
pendent on the entry strategy.

Note
The available strategy categories are predefined by Softproviding and
cannot be changed.

The explanations at the end of this table show how the strategy cate-
gories are typically used.
Enter material This indicator determines whether the BOM item may be entered
or not.

Input help
The following values are available to choose from:
— Material is entered
— Material is not entered and not displayed
— Material is not entered but is displayed

Note
Entry settings are applied at the following points:
— Material master data (tab Process Data Acquisition)
— In this field

The entry that limits the application to the greatest degree always has
priority here.

Table Item Category / Strategy Category / Entry

— The Softproviding Meat item types listed below are usually created in addition to the SAP
standard item categories
— The table shows the combinations (settings) of item categories normally used (both SAP
standard and Softproviding item categories), the strategy categories and the entry decisions.

Item Cate- Item Category Strategy Category Enter

gory Name
A Meat Management entry Entry item Material is entered
item
B Meat Management calcula- Calculation item Material is entered
tion item
C Planning element Calculation item Material is not entered but
is displayed
G Meat Management weight Weight item Material is entered
item
L Storage item Weight item Material is entered

Process Data – Softproviding Core Configuration Guide 44/112

Think ahead. Go there.

Item Cate- Item Category Strategy Category Enter

gory Name
P Meat planning item Planning item Material is not entered but
is displayed
T Text item Additional item Material is not entered but
is displayed
X Meat Management addi- Weight item Material is entered
tional item
Y Meat Management master Master item Material is entered
item
Z Meat Management addi- Additional item Material is not entered but
tional item is displayed

Note – Further Processing Order

The following must be observed so that entries can be made (inbound/outbound).

For the order type of further processing (e.g. PP01) there must be an entry as follows:
— Field Item category = the item category is freely selectable
— Field Strategy type = "W" (weight item)
— Field Enter material = "Material is entered"

If the above-mentioned entry is missing, the error message “/SPDGS/PDA307 (Table /SPDGS/TMP3 not
maintained)" is issued in Process Data Acquisition for Further Processing (Process Data Cockpit).

Note – Disassembly Orders

The following must be observed so that entries can be made (inbound/outbound).

The previous program logic (up to and including release v2.80/v5.80) included the fixed query for item
category "G" (weight item Meat Management). This fixed query was removed in release v2.90/v5.90. It is
no longer mandatory to use item category "G". However, existing entries with item category "G" can con-
tinue to be used without restriction.

It is recommended to make entries in table /SPDGS/TMP3 as follows:

— Field Order type = Order type for Disassembly (e.g. ZPP1)
— Field Item category = “L” (stock item)
— Field Strategy type = “W” (weight item)
— Field Enter material = «Material is entered

For the production order created in parallel, the item category “L” (stock item) is always used for the order
items.

Note – Translation
Assignments for data entry are made as follows in the item category table:
— Material is entered
— Material is not entered and not displayed
— Material is not entered but is displayed

Process Data – Softproviding Core Configuration Guide 45/112

Think ahead. Go there.

These entries must be translated in the logon language of the user so that entries for the respective orders
can be made without problems.

Strategy Category table

— The table shows the possible strategy categories.

Strategy category Description

Other An “other” item can then be used if an item cannot be assigned to
any other strategy category.
Entry item * Items or materials that are not listed in kg are shown under an en-
try item.
Calculation item * Under a calculation item, the item or material is only calculated
and is not weighed or entered.
Master item A master item is a leading item. All other items are calculated de-
pendent on the master item. The master item is normally used in
the input. However, it also works for the output.
Planning item * Under a planning item, the planned quantity is used as the actual
quantity. The item or material cannot be weighed.
Weight item A weight item is always an item or material that is listed in kg.
Additional item An additional item is not normally entered. It is used to display an
item or material in Further Processing Entry.

Note
The use of an item is primarily governed by the PDA strategy. The strategy categories marked with (*)
above override the more general PDA strategy.

Example: A calculation item is always calculated, even if the PDA strategy is e.g. IWOW.

3.3.3 Component Replacement

The component replacement can be used in Further Processing to replace one or more bill of materials
components provided for production with other components (interchangeable parts). These materials
are defined as alternative components.

The prerequisites and master data for component replacement are explained in this chapter under
“Other”. They are:
— Maintenance of the master data table (view cluster /SPDGS/VC_ATKO)
— Basic activation of component replacement

Further conditions for component replacement can be defined on a customer-specific basis using
BAdIs. This function is implemented using the following three tables.
— Define conditions
— Implement conditions
— Post replacement

Process Data – Softproviding Core Configuration Guide 46/112

Think ahead. Go there.

3.3.3.1 Define Conditions

Further conditions for component replacement can be defined on a customer-specific basis by way of
BAdIs.

The conditions defined in this step can be assigned in the above-mentioned table (view cluster
/SPDGS/VC_ATKO). The conditions are programmed on a customer-specific basis (see section “Im-
plement Conditions”). This is done in BAdI /SPDGS/BADI_AT_COND.

Table Fields
Field Name Description
Condition Definition of a numeric key with max. 3 digits that represents a
condition.
Name Description of the condition

3.3.3.2 Implement Conditions

This Customizing item can be used to execute BAdI implementation for BAdI
/SPDGS/BADI_AT_COND from enhancement spot /SPDGS/BADI_PA_REPLACEMENT. The en-
hancement spot /SPDGS/BADI_PA_REPLACEMENT can also be opened using transaction SE18.

This BAdI /SPDGS/BADI_AT_COND can be programmed on a customer-specific basis. Filter values

are used for this purpose in enhancement implementation in accordance with the defined conditions
(see section “Define Conditions”).

Example
— A condition 100 (production supervisor) is defined
— A filter value 100 is created in the implementation
— The replacement condition is programmed as follows in the implemented class:

if is_aufk-fevor = 001. “Production supervisor”

XV_SUBRC = 0.
else.
XV_SUBRC = 1.
endif.

The condition 100 is stored in the view /SPDGS/VC_ATKO.

Process Data – Softproviding Core Configuration Guide 47/112

Think ahead. Go there.

Result
If the production supervisor is entered as 001 in the production order, the replacement variant accord-
ing to the entry in the view /SPDGS/VC_ATKO is offered as a choice. If the production supervisor is
not 001 in the order, no replacement variant is offered as a choice.

The definition of the conditions on the one hand and the implementation of the BAdI
/SPDGS/BADI_AT_COND on the other makes it possible to store the conditions in the above-men-
tioned view /SPDGS/VC_ATKO and use them in the application during the replacement.

3.3.3.3 Post Replacement

This Customizing item can be used to execute BAdI implementation for BAdI
/SPDGS/BADI_AT_EXEC from enhancement spot /SPDGS/BADI_PA_REPLACEMENT. The en-
hancement spot /SPDGS/BADI_PA_REPLACEMENT can also be opened using transaction SE18.

Recommendation
It is recommended to use the BAdI /SPDGS/BADI_AT_EXEC as supplied and not to execute any cus-
tomer-specific implementation here, as this BAdI already contains all the necessary programming to
post the replacement.

“Posting” replaces the material to be replaced with the replacement material and determines the
quantity in accordance with the factor definition (see table above).

Result
After component replacement has been performed, the following modifications are made in the appli-
cation:
— The quantity of material to be replaced is set to 0 (zero) in the component view for the order.
— The replacement material is entered in the component view for the order.

3.3.4 Quality Inspection

In this section, settings can be applied that relate to performing a quality inspection in Further Pro-
cessing Entry.

Table Fields
Field Name Description
Plant The plant serves as a production site for a company.

Process Data – Softproviding Core Configuration Guide 48/112

Think ahead. Go there.

Field Name Description

Category (order category) The DGS order category distinguishes between production orders
on the basis of their data model and function.

Input help
The following order categories can be selected:
— Further Processing
— Process Order
— Disassembly
— Purchase Order (to be used internally only)
— Delivery (to be used internally only)

Use
The order category is used as a distinguishing criterion in Custom-
izing and controls the functionality in dialog and remote applica-
tions.

Note
The order categories Delivery and Purchase Order offered for selec-
tion are used internally within the program and must not be selected
and assigned

Note
Currently the function is only programmed with the order category
Further Processing. The order category Disassembly does not yet
have a function in this table.
I/O (Input/Output) This setting determines wither the quality inspections are possi-
ble for input or output.

Note
Input means goods issue (i.e. material reservation); output means the
(planned) goods receipt for production order.
Inspection type The inspection type defines how an inspection is to be performed.

Input help
Users can choose from all inspection types available in SAP.
Perform Q inspection For each inspection type, this instruction controls how the sys-
tem should react in Further Processing Entry.

Input help
The following settings can be selected:
— Mandatory
— Possible
— Recommended
— Not possible

Process Data – Softproviding Core Configuration Guide 49/112

Think ahead. Go there.

Field Name Description

Note
This control is only relevant if the quality inspection function for the
terminal is active (IMG: Softproviding Core > Logistics > Process
Data Acquisition > Organization > Terminal).

3.4 Control Settings

Open the menu item Control Settings in the implementation guide as follows:

Menu Softproviding Core > Logistics > Process Data Acquisition > Control
Settings

The settings for the following tables are described in this section:
— Entry operation
— Goods movement
— Use
— Entry subscreen
— Barcodes
— Scanner entry

Use
The most important settings in these tables are:
— Determining the posting behavior for each document group (e.g. Further Processing) and doc-
ument category (e.g. goods receipt)
— Determining the movement types for each document category (e.g. per goods receipt)
— Controlling the input-output item in the entry (predefined/must not be changed)
— Determining the screen for the entry for each document group and category
— Scanner control settings including BAdI definition

Activities
Entries can be created by selecting the button New entries.

3.4.1 PDA Program Logic

Use
Table with indicators for activating the new PDA program logic

Process Data – Softproviding Core Configuration Guide 50/112

Think ahead. Go there.

Table Fields
Field Name Description
New PDA Indicator

This setting activates the new PDA program logic. This is availa-
ble from release v6.00 and includes the following additional func-
tions:
— Integration of Change ID Control via quota and pairing
— Consideration of actual data recording for quotas and the
option of switching off pair formation
— Checks during the facility of PDA records (stock, planned
quantity, target quantity)
— Consideration of two units of measure in the quota calcula-
tion

Recommendation
Activate these functions by setting the indicator.

Note
This indicator is not set by default. Please contact Softproviding
Support before activating it.

3.4.2 Entry Operation

Use
In this section, settings for entering and editing process data are applied for each:
— Plant
— Document group
— Document category
— Terminal ID
— User name

Recording devices, printers and storage locations can then be assigned for each table entry (PDA pro-
cess data). There is no limit on the number of recording devices, printers and storage locations that
can be created for each table entry.

Table Fields
Field Name Description
Plant The plant serves as a production site for a company.

Process Data – Softproviding Core Configuration Guide 51/112

Think ahead. Go there.

Field Name Description

Document group Business transactions are represented in SAP by documents. This
field pools documents of the same group that are treated in the
same way from the perspective of process data acquisition.

Input help
The document groups can be found in the input help.

Examples
— Purchase order
— Disassembly order
— Further processing order
Document category In Softproviding Core and Softproviding Meat, document catego-
ries indicate business-related entry operations. They are therefore
a type of categorization.

Example
— Document category GI (goods issue)
— Document category GR (goods receipt)
Terminal ID The terminal ID corresponds to the computer name in Windows
and unambiguously identifies a computer in the local network.

Use
The transaction control is dependent on the terminal ID. If no en-
try is found in this table for the calling terminal, the generic entry
(*) is searched for and used.
User name Entries are made in this table on a per-user basis. The username
can also be the entry * (= asterisk). This entry is then valid for all
users.

Posting
Field Name Description
PDA operation The settings in this field decide how PDA operations created dur-
ing data acquisition should be processed.

Input help
The following settings are possible:
— Synchronous (V1)
— Asynchronous (V2)

Synchronous posting takes place immediately, while asynchro-

nous posting takes place later.

Recommendation
For performance reasons, it is recommended to choose the setting
Asynchronous.
Material document The settings in this field decide whether and how PDA data rec-
ords are posted.

Process Data – Softproviding Core Configuration Guide 52/112

Think ahead. Go there.

Field Name Description

Input help
The following settings are possible:
— X = not relevant (although a PDA data record is created, it
cannot be posted (no material document is created)
— 1 = immediately (V1/V2) (immediate creation of a material
document after the PDA data record is created)
— 3 = batch/job (V3) (the material document is created during
implementation of the batch job (program
/SPDGS/GMOVBTCH))
— On application level (REM)
— Blank = no PDA record is created (a message is displayed in
the application)

Recommendation
The creation of the material document should be set to V3 for rea-
sons of data consistency. That the material document is gener-
ated immediately should be the exception (possibly for perfor-
mance reasons).

Note
Depending on the process, it may be necessary to override the above
setting for creating the material document. The additional import pa-
rameters I_CREGM and IV_CREGM in the function modules listed be-
low provide this option.

If necessary, the customizing settings can be overridden, and the ma-

terial document can be posted directly.

The parameters mentioned above have been incorporated in the fol-

lowing function modules:
— /SPDGS/PDAON_CREATE_OPERATION
— /SPDGS/API_PR_CREATE_OPERATION
Reversal document The settings in this field decide whether and how reversed PDA
data records are posted.

Input help
The following settings are possible:
— X = not relevant (although a PDA data record is created, it
cannot be posted (no material document is created)
— 1 = immediately (V1/V2) (immediate creation of a material
document after the PDA data record is created)
— 3 = batch/job (V3) (the material document is created during
implementation of the batch job (program
/SPDGS/GMOVBTCH))
— On application level (REM)
— Blank = no PDA record is created (a message is displayed in
the application)

Process Data – Softproviding Core Configuration Guide 53/112

Think ahead. Go there.

Field Name Description

Recommendation
The creation of the reversal document should be set to V3 for rea-
sons of data consistency. That the material document is gener-
ated immediately should be the exception (possibly for perfor-
mance reasons).

Dialog
Field Name Description
“Work group” field is manda- If this indicator is set, the field Work group becomes a mandatory
tory field in dialog applications for Further Processing Entry.

Use
A work group is an organizational unit within production. It is
used as a selection criterion in Further Processing Entry and for
evaluation purposes in DGS. When displaying the PDA data rec-
ords in the PDA data cockpit, the field can be used as a filter crite-
rion.

Example
— 1000 (Team A)
— 2000 (Team B)
“Clear remaining batches” If this indicator is set, the function Clear remaining batch stock is
function active available. The additional button Complete is then displayed in the
entry window (e.g. for Further Processing Entry input (= goods is-
sue)) in the corresponding applications and can be used to mark
the desired batch. By using this button to confirm the batch, the
latter is written into the table /SPDGS/GMBA and is thus marked
for clearing (consumption posting or destruction). The postings
are then made with the program /SPDGS/SCRPBTCH.

Use
If it is determined in the production facilities when removing
goods from storage that the physical quantity of a material is
zero, this function can be used to ensure that the material level is
also set to zero in the SAP system in accordance with the actual
quantity.

Note
This function is only offered for goods issue processes, as it is not
practical for goods receipt.

See also the detailed description of this function in the document

Core230_User_ProcessData.
Default storage location A default storage location can be entered in this field that can be
used in Further Processing Entry. If a storage location is assigned
here, the button Default storage location is displayed in the entry

Process Data – Softproviding Core Configuration Guide 54/112

Think ahead. Go there.

Field Name Description

window in the application. After confirming with this button, the
storage location entered here is used in the application as default
value.

Input help
A proposed storage location must first be entered in this table be-
fore it can be selected (see the description of the field Allowed
Storage Locations below in this table).

Use
This function is used e.g. in:
— Disassembly entry outbound and inbound
— Further Processing Entry, outbound and inbound
— Goods Receipt for Purchase Order
Process order
HU mandatory If this indicator is set, a handling unit must be specified when a
PDA record is created. If no handling unit is specified, the PDA
record cannot be created.

Production Date and SLED

Field Name Description
Source field Production date Depending on the settings in the material master data for the ma-
terial to be entered (field Total shelf life), the fields Expiration
date/SLED or Production date are displayed (mandatory fields) in
the application (e.g. Further Processing Entry goods receipt).

Example
Material master data: The field Total shelf life has an entry. The
field Production date is displayed in the application.
Material master data: The field Total shelf life has no entry. The
field Expiration date/SLED is displayed in the application.

The entry in this source field determines which date will fill the
Production date field. This date can be overwritten in the applica-
tion.

Note
The source field is only relevant to goods receipt processes. If no entry
is made in this source field, the Production date field must be main-
tained manually in the application.

Use
— Further Processing Entry, goods receipt
— Enter Process Order
— Goods Receipt for Purchase Order
— Disassembly Entry Outbound (= goods receipt)
— Repetitive manufacturing goods receipt

Process Data – Softproviding Core Configuration Guide 55/112

Think ahead. Go there.

Field Name Description

General recommendation
Make an entry so that the Production date field is filled with a date
in the application.

Default value
For example, the system date (entry SY-DATUM) can be used.

Furthermore, the fields of the following structures may be used:

— SYST ABAP system fields
— VBAK, VBAP, VBEP for sales orders
— EKKO, EKPO for purchase orders
— CAUFVD for production orders
— LIKP, LIPS for deliveries

Make sure that fields are used whose data types have the proper-
ties of a date format. Structure and field name must be separated
with a minus sign (-) when entered.

Example
— ABAP system fields: SYST-DATUM for document group
“empty” and document type “WE”.
— Production orders: CAUFVD-GSTRP for document group “D”
and document type “WE”.
— Inbound deliveries: LIKP-LFDAT for document group “B”
and document type “WE”
Production date for change ID If this field is maintained and a change ID exists, the defined date
field from the change ID is used for the production date.
Production date changeable If this indicator is set, the production date can be changed on the
entry screen.
Suppress shelf-life expiration If this indicator is set, querying of the shelf-life expiration date or
date / production date production date is prevented in the dialog applications. This is
achieved by hiding the fields Expiration date/SLED or Production
date (see also the below description of the field Source field pro-
duction date).

Note
The above-mentioned fields would then also be hidden if the infor-
mation on the SLED or production date is required in accordance with
the plant and movement type settings and is therefore also necessary
from a process perspective. This may result in PDA data records being
created that cannot be posted, as e.g. the production date is missing at
goods receipt. This would lead to reworking being necessary.

Recommendation
Check whether it is really necessary to hide this information from
a process perspective.

Process Data – Softproviding Core Configuration Guide 56/112

Think ahead. Go there.

Field Name Description

Copy production date and Setting this indicator activates the calculation of the expiration
SLED from batch date in Further Processing Entry. The expiration date is calculated
when the PDA data record is entered.

Unplanned Movements
Field Name Description
Operation The settings in this field determine whether unplanned move-
ments are permitted.

Input help
— Intended
— Not intended but possible
— Prohibited

If unplanned movements are provided for, or are not provided for

but are possible, according to these settings, the button Un-
planned movements is displayed in the process data acquisition
programs.

Note
The field “Unplanned movements” does not apply to mass production.

Object Determination
Field Name Description
Class type Specify a class type for the object search here.
Class Specify the class in the class type for the object search here.
FM Determination Object Determination can be performed on a customer- or indus-
try-specific basis.

Recommendation
Use the function module /SPDGS/MAST_DETERMINE_OBJECT
as a template for your own implementation. The function module
/SPMEAT/LGPF_WAREHOUSE_GROUP is supplied for the stor-
age group object in Softproviding Meat.

Dependencies
For further information on the prerequisites in Customizing and
the maintenance of master data, please see the Softproviding
Core Object Determination user documentation which includes in-
formation on the application, customizing settings as well as mas-
ter data.
Automatically execute object The object search is performed automatically (optionally in the
determination background) with the data from the current operation.

Process Data – Softproviding Core Configuration Guide 57/112

Think ahead. Go there.

Field Name Description

Dependencies
If an object search is to be performed for background processes
(e.g. AutoClient), this indicator must be activated.
Allow evaluation for object The critical features for the object determination can be changed
determination by the user. A new determination is then performed.

Dependencies
This indicator has no effect on background processes (e.g. Auto-
Client).
Manual object entry allowed The result of the object determination can be manually overwrit-
ten.

Dependencies
This indicator has no effect on background processing (e.g. Auto-
Client).

WM Request
Field Name Description
Function module This function is no longer used. This field remains without entry.

Former use
Enter the function module here that contains the function for a
WM request. A WM request is the sending of commands to a WM
subsystem that does not have a direct connection to the dialog con-
text.

The necessary dialogs (pop-ups) and the specific function and

control of the subsystem must be programmed into this function
module.

Recommendation
Use /SPDGS/MAST_WM_SUBSYS_REQUEST as a template for
your own implementation.

Use
If a module is stored, a button WM request is provided in the dialog
applications. Otherwise, the button is hidden.

Communication with WM
Field Name Description
Active (indicator) This function is no longer used. The indicator should be set. The
button is hidden in the application.

Former use
This button activates/deactivates the function WM Request in
Further Processing Entry. After the PDA data (entry data) is

Process Data – Softproviding Core Configuration Guide 58/112

Think ahead. Go there.

Field Name Description

posted, the interface with the WM system is opened. Communica-
tion is established via a (potentially customer-specific) function
module that is defined on the device used (e.g. scales).
Subsystem This function is no longer used. This field remains empty.

Former use
A PDA operation can trigger immediate subsequent activities in a
WM subsystem. Enter the technical name of the system that is to
be addressed here.

Dependencies
In order for processing to take place, you must also specify a func-
tion module with the processing logic for the assigned entry de-
vices. If no module is specified for the device, the information sent
to the PDA operation has no effect.

Change ID
Field Name Description
Logist. process If a logistical process is entered in this field, this value is used for
the Change ID Control process. Without this specific entry, deter-
mination takes place via the document type and document group
of Origin Control (customizing).
Comm. point A communication point is a precisely specified point in a plant
where data relating to a logistical process is generated, ex-
changed and/or documented. A distinction is made between
check and assign communication points.

Determination
Defined communication points can be determined via the Origin
Control customizing table.
Nr. days past This value is passed on to the function module by the calling pro-
gram. By specifying the number of days in the past, the function
module determines the relevant change IDs not only for the cur-
rent day, but also for the days in the past.

Example
The number 1 means that the function module fills the list of
change IDs with all the change IDs from today and yesterday.

This field can also be used (in conjunction with the Logistical Pro-
cess field), for example, to display the change ID only in a specific
work area (for example, a sausage production area).
Enter/change characteristic If this indicator is set, characteristic values can be recorded or
value changed on the entry screen.

Process Data – Softproviding Core Configuration Guide 59/112

Think ahead. Go there.

Field Name Description

Use
This indicator controls the recording and changing or displaying
of characteristic values of a change ID for individual shop floor
processes. If this indicator is set, characteristic values can be rec-
orded and stored in the change ID. If this indicator is not set, the
characteristic values of a change ID can only be displayed.

Determination
The characteristic fields allowed for entry (e.g. LIFNR for the GR
for purchase order process) are defined in the application table
Origin Class definition (Rules dialog).
Material and batch master If the indicator is set, the characteristic values of the classifica-
classification as input tion of a material are copied directly as input values.

Use
This indicator controls whether the classification values from the
material master are copied directly from the entry screen as input
values during component checks. This applies to material class
001 and batch class 023. The user cannot make any changes or
deletions but does not have to enter anything either. If this indi-
cator is not set, the values are not copied automatically.

Dependencies
In the material master for the current material, characteristic val-
ues should be created for one or more material classes of class
type 001 or for the batch class of class type 022 or 023. No mes-
sage is issued if no values could be determined. The characteristic
values of all classes are passed on. Whether they are relevant for
the check is determined by the rules of the origin class. Only if
there is a rule for the characteristic does the transfer of the values
have an effect on the change validation and the documentation in
the change ID.
Material master classification Definition
as ref. If the indicator is set, the characteristic values of the classifica-
tion of a material are copied as reference values.

Use
This indicator controls whether the reference values for the con-
formity check are copied from the material master on the basis of
the classification of the current material instead of the allowed
single values from the origin class.

Dependencies
In the material master for the current material, characteristic val-
ues should be created for one or more material classes of class

Process Data – Softproviding Core Configuration Guide 60/112

Think ahead. Go there.

Field Name Description

type 001 or for the batch class of class type 022 or 023. If no refer-
ence values are available, an error message of the conformity
check is issued.

The characteristic values of all classes are passed on. Whether

they are relevant for the check is determined by the rules of the
origin class. Only if there is a rule for the characteristic does the
transfer of the values have an effect on the change validation and
the documentation in the change ID.
Material master classific. as Definition
template If the indicator is set, the characteristic values of the classifica-
tion of a material are copied as template.

Use
This indicator controls whether the classification values are auto-
matically copied from the material master as entered when char-
acteristic values are entered. The user can make any changes or
deletions. Also, they can enter further values for same or differ-
ent field characteristics. If this indicator is not set, no entry pro-
posal is made.

Dependencies
In the material master for the current material, characteristic val-
ues should be created for one or more material classes of class
type 001 or for the batch class of class type 022 or 023. If no val-
ues exist, no entry proposal is made. No message is issued if no
values could be determined.

The characteristic values of all classes are passed on. Whether

they are relevant for the check is determined by the rules of the
origin class. Only if there is a rule for the characteristic does the
transfer of the values have an effect on the change validation and
the documentation in the change ID.
Change ID on PDA mandatory Definition
If the indicator is set, the system checks whether a proof of origin
(change ID) is required for the current PDA operation.

Use
Before you create a PDA operation, the indicator controls
whether the change ID (field: /SPDGS/PDAO-CHGID) is a re-
quired entry as proof of origin and must not be empty.
Conformity check for material If this indicator is set, a conformity check is carried out for the
current material.

Use
This indicator controls in Assign mode whether the current
change ID may be assigned to a material. If the indicator is set,

Process Data – Softproviding Core Configuration Guide 61/112

Think ahead. Go there.

Field Name Description

the system simultaneously checks whether the characteristic
values of the change ID (input) conform to the origin class as-
signed to the current material in the material master and its rules
and characteristic values (reference) when determining the cur-
rent change ID. If the result conforms, the current change ID can
be assigned to the material. If the result does not conform, an error
message is issued. The current material cannot be entered with
this change ID.
Change ID editable Definition
If this indicator is set, the Change ID field can be changed on the
entry screen.

Use
This indicator controls whether the Change ID field can only be
displayed or also changed on the entry screen. Usually the cur-
rent change ID is determined automatically.

A change of the current change ID to the next one is triggered via

the scroll bar Change Control and the function Next Change ID. It
can also be used to call up a list with all the change Ids valid for
this process. A change ID can be selected from this list and set as
the current ID. It does not make sense to enter directly or select a
change ID from all possible change IDs.

Dependencies
In editing mode, the user can enter any value as a change ID. No
plausibility check is made.

If the user chooses a change ID from the list, the corresponding

batch number is also copied to the entry screen. An implausible
change ID is accepted as a value in the PDA process. Nothing is
stored in the data model for Change ID Control.
Origin class editable If this indicator is set, the Origin Class field can be changed on the
entry screen.

Use
This indicator controls whether the Origin Class field can only be
displayed or also changed on the entry screen. The origin class is
usually determined automatically via the material or the produc-
tion order.
LoPro conf.chck The value CONF (conformity check) can be entered to check con-
formity.
Comm.pt. conf. The value CC (conformity check; without change ID) can be en-
tered to check conformity.

Process Data – Softproviding Core Configuration Guide 62/112

Think ahead. Go there.

3.4.2.1 Recording Devices

Mark a table entry (line). The following device-specific settings can now be applied to each plant/doc-
ument group/document category/terminal ID/user name.

Field Name Description

Device A device can be a scanner, a scale, a flow meter, or another exter-
nal system.

Input help
The allowed devices can be selected in the input help. These de-
vices are predefined in Customizing as follows: Softproviding Core
> Logistics > Process Data Acquisition > Definition > Devices (DGS
Remote Devices).

Example
— ITEC
— BANS
— AutoFOM

SAP Dialog Mode

Field Name Description
Device active You must activate this indicator if you want to authorize a PDA
device for manual operations (e.g. entry from the SAP entry win-
dow).

It is possible to store several devices for one PDA operation and

thus authorize them for manual operations.
Default device This indicator defines the device as the default device. If a maxi-
mum of one device per PDA operation is defined as the default,
this device is selected for the entry. If no default is specified, a
pop-up with a selection list appears in the entry window.

Note
It is not possible to mark several devices as the default device for one
PDA operation. If this setting is nonetheless applied, the system will
take the first device defined as the default device.
Identification Activate this indicator if unambiguous identification of the en-
tered object must take place in the PDC operation. In this case, the
additional field Identification is displayed in the dialog applica-
tions.
Batch management require- If this indicator is set, the field Batch in the SAP GUI dialog appli-
ment cations is a mandatory field. However, this does not apply to DGA
applications.

Process Data – Softproviding Core Configuration Guide 63/112

Think ahead. Go there.

AutoClient Mode (Job)

Field Name Description
Device active You must activate this indicator if you want to authorize a PDA
device for automatic operations (e.g. AutoClient). It is possible to
store several devices for one PDA operation and thus authorize
them for automatic operations.
Default device This indicator defines the device as the default device. If a maxi-
mum of one device per PDA operation is defined as the default,
this device is selected for the entry. If no default is specified, a
pop-up with a selection list appears in the entry window.

Note
It is not possible to mark several devices as the default device for one
PDA operation. If this setting is nonetheless applied, the system will
take the first device defined as the default device.
RFC AutoClient PDA operations can be transmitted to AutoClients as a job. These
AutoClients then complete the PDA operations and send the data
collected to the SAP system in the background. AutoClients are
addressed via logic RFC destinations.
Batch rule The batch rule determines the origin of the batch number for en-
try operations in the job. Dialog programs have their own logic
and do not use this rule.

Input help
The following batch rules can be selected:
— No rule
— Batch must be defined in the job
— Batch must be supplied by the subsystem
— Batch must be supplied by the subsystem, if init., then by
the job
— Automatic batch number assignment (MM)
— Batch number is generated with module (customer)
Function module If the batch rule is set to “Batch number is generated with module
(customer)”, the batch number for the goods movement is created
with a function module. Depending on the system settings, the
module must create the batch using BAPI.

Use
The module /SPDGS/MAST_CREATE_BATCH_ID is supplied in
DGS Standard. This module can be copied into a customer-specific
function group and adapted to individual needs.

Device Unit
Field Name Description
Device unit This information is only relevant if the PDA device is a set of
scales. Please enter the units (e.g. g, kg, lb) in which the scales op-
erate and send weights to SAP.

Process Data – Softproviding Core Configuration Guide 64/112

Think ahead. Go there.

Field Name Description

This information is essential for conversion to the weight unit of
the material.

WM Subsystem
Field Name Description
Subsystem This function is no longer used. This field remains without entry.
Funtion module This function is no longer used. This field remains without entry.

3.4.2.2 Label Printer

Mark a table entry (line). The following printer-specific settings (for the label) can now be applied to
each plant/document group/document category/terminal ID/user name.

Field Name Description

Output device Name of the printer that is to generate the printout.

Parameters
Field Name Description
Default printer This printer is the default printer for the PDA operation. Only one
assigned printer may be designated the default printer.
Number The number of copies to be printed. This field is only visible in the
detailed view.

Preparation
Field Name Description
Program Name of the printing program.

Softproviding provides the following programs in the standard de-

livery:
— /SPDGS/PMON_LABELPRINT
— /SPMEAT/PMON_LABELPRINT
FORM routine Name of the form routine of the printing program.
Form name Form name for the label.

3.4.2.3 Log Printer

Mark a table entry (line). The following printer-specific settings (for the report) can now be applied
to each plant/document group/document category/terminal ID/user name.

Field Name Description

Output device Name of the printer that is to generate the printout.

Process Data – Softproviding Core Configuration Guide 65/112

Think ahead. Go there.

Parameters
Field Name Description
Default printer This printer is the default printer for the PDA operation. Only one
assigned printer may be designated the default printer.
Number The number of copies to be printed. This field is only visible in the
detailed view.

Print preparation
Field Name Description
Program Name of the printing program.
FORM routine Name of the form routine of the printing program.
Form name Form name for the report.

3.4.2.4 Allowed Storage Locations

Mark a table entry (line). The following settings can now be applied to each plant / document group /
document category / terminal ID / user name.

Field Name Description

Storage location The storage locations created in this table view can be used as
proposed storage locations in the table PDA Processes mentioned
above. See also the description of the field Suggested storage loca-
tion above.
Storage location name Name of the storage location

3.4.2.5 Change ID Label Printer

Select a table entry (line). The following settings can now be made for each plant/document
group/document category/terminal ID/user name.

Depending on the process, the relevant settings for printing the change ID (control of label printing)
are stored in this table.

Field Name Description

Output device Printer on which the list is to be printed.

Change ID label printer

Field Name Description
Default printer This printer is the default printer for the PDA operation. Only one
of the printers assigned may be defined as default printer.
Number of labels Number of labels to be printed. This field is only displayed in de-
tail view.

Process Data – Softproviding Core Configuration Guide 66/112

Think ahead. Go there.

Field Name Description

Program Name of the print program.

Softproviding delivers the following standard program:

— /SPMEAT/PMON_LABELPRINT_CHGID
FORM routine Name of the form routine for the print program.
Form name Form name for the label.

3.4.2.6 PDA Checks

Select a table entry (line). The following settings can now be made for each plant/document
group/document type/terminal ID/user name.

Depending on the process, the relevant settings for the PDA checks are stored in this table.

Field name Description

Stock check If this indicator is set, the system checks whether there is suffi-
cient stock for the quantity entered (goods issue process).
Stock rev. mess type This setting determines which message type is to be output dur-
ing the inventory check.

With message type 'E', the PDA data record is not created.
SLED check If this indicator is set, the SLED date of the batch is checked
(goods issue process).

If this date is in the past, a message is displayed.

SLED check mess type This setting determines which message type is to be output dur-
ing the SLED check.

The PDA data record is not created for message type 'E'.
Overdel. check If this indicator is set, the quantity entered is checked against the
overdelivery tolerances of the order.
Use
— Goods receipt for order
— Delivery
— Production order
— Process order
Over.check mess type This setting determines which message type is to be output dur-
ing the transfer check.

With message type 'E', the PDA data record is not created.
Targ. Overdel. If this indicator is set, the system checks whether the actual
quantity is greater than the target quantity.

Process Data – Softproviding Core Configuration Guide 67/112

Think ahead. Go there.

Field name Description

The target quantity is calculated depending on the goods issues
for the order.

Use
— Goods receipt for production order
— Goods receipt for process order
Target qty. over.mess This setting determines which message type is to be output dur-
ing the overdelivery check for the target quantity.

With message type 'E', the PDA data record is not created.

3.4.3 Goods Movement

Use
In this section, control settings for posting the entered PDA data records are applied. The entries are
made in each case per:
— Document group
— Document category
— Stock type
— Special stock

These settings concern the movement type to be used (SAP standard movement types) per business
transaction (e.g. per goods receipt or per return).

Note
Without the corresponding process settings, PDA data records created cannot be posted. In this case, an
error message is displayed in this table with reference to the missing settings. Corresponding error mes-
sages are output in the case of manual posting in the transaction /SPDGS/PDAON and in the report on
batch jobs normally created for posting PDA data records (program /SPDGS/GMOVBTCH).

How to create these batch jobs and which special features have to be considered is described at the end of
this chapter in the “Further Information: Batch Jobs” section.

Table Fields
Field Name Description
Document group Business transactions are represented in SAP by documents. This
field pools documents of the same group that are treated in the
same way from the perspective of Process Data Acquisition.

Input help
The document groups can be found in the input help.

Process Data – Softproviding Core Configuration Guide 68/112

Think ahead. Go there.

Field Name Description

Examples
— Purchase order
— Disassembly order
— Further processing order
Document category In Softproviding Core and Softproviding Meat, document catego-
ries indicate business-related entry operations. They are therefore
a type of categorization.

Example
— Document category GI (goods issue)
— Document category GR (goods receipt)
Stock type The stock type specifies the stock into which the material is
posted in goods receipt or from which it is posted in goods issue.

Note
This function is not currently programmed and therefore cannot be
used.
Special stock This indicator specifies the type of special stock concerned.

Note
This function is not currently programmed and therefore cannot be
used.

Material Posting Control

BAPI GM Code (Normal) Control of the goods movement posting is derived from the BAPI
code assigned here.

Input help
The available BAPI codes can be selected via the input help.

Note
For the individual BAPI codes, please refer to the documentation on
the function module BAPI_GOODSMVT_CREATE (in particular the
field GM_CODE) (opened using transaction SE37).

Note
The BAPI code Goods issue confirmation is a Softproviding-specific
code. It concerns planned goods movements such as goods issue for a
production order or goods receipt for a purchase order.

This code controls the special processing for the confirmation of SD

deliveries. The specification of movement types etc. is not relevant to
this setting.

In the PDA operation control (table /SPDGS/TDEC) the poster for the
material document must be set to V3 (batch/ job for this process (BAPI
code Goods issue confirmation). This table can be opened as follows:

Process Data – Softproviding Core Configuration Guide 69/112

Think ahead. Go there.

IMG: Softproviding Core > Logistics > Process Data Acquisition >
Control Settings > Entry Operation (field Material document).

Posting is performed using the function module WS_DELIVERY_UP-

DATE. Please also refer to the documentation on this function module
(opened with transaction SE37).
Movement type (normal) Specify a key for the type of goods movement. Every goods move-
ment (e.g. purchase order to storage) is assigned a movement type
in the system.

Examples
— 101 (goods receipt)
— 261 (goods issue)
Inventory document Indicator

For certain processes, it is necessary to be able to post stock in-

creases or decreases in the SAP system and to use the PDA update
logic. This is the case, for example, when a handling unit has
physically more stock than is available in the SAP system. In such
cases, it is possible to post a receipt or issue using a PDA data rec-
ord with document categories I/WE or I/WA. The BAPI GM codes
WE and WA as well as the movement types 701 and 702 are used
for this purpose.

With the combination I/I1 an inventory with inventory document

is also possible inventory document is also possible using the PDA
update logic.

To map the process and create the desired inventory documents,

make the following settings:
— Document group I (inventory)
— Document category I1 (inventory)
— Inventory type Freely usable
— BAPI GN code “without entry”
— Movement type “without entry”
— Inventory Doc X

Note
The setting option I/I1 with the Inventory Doc indicator is intended
for future developments and currently has no function.
Movement type (return) Specify a key for the type of goods movement. Every goods move-
ment (e.g. purchase order to storage) is assigned a movement type
in the system.

Examples
— 161 (goods receipt return)
— 451 (goods issue returns)

Process Data – Softproviding Core Configuration Guide 70/112

Think ahead. Go there.

Reason for Movement Specify a key with which you can open a standard text for provid-
ing a reason for a goods movement (e.g. return note for a return
delivery).

Dependencies
For each movement type, you can define in the Customizing set-
tings for inventory management (transaction OMBS) whether a
reason for the return must or can be given and/or which reasons
are permitted.
BAPI GM Code (unplanned) See the basic explanation above of the field BAPI GM Code (Nor-
mal).

BAPI GM Code (unplanned)

Unplanned goods receipts may occur in purchasing or production.
These must be posted using an alternative BAPI GM code.

The system recognizes that an unplanned goods receipt is con-

cerned
— for GR in purchasing at the missing order number
— for orders at the missing order item (order number must be
present)

Recommendation
If necessary, apply the following settings:
— Goods receipt in purchasing without purchase order: GM
code 05 with movement type 501
— Unplanned goods receipt for a production order: GM code 05
with movement type 531
Movement type (unplanned) Specify a key for the type of goods movement. Every goods move-
ment (e.g. purchase order to storage) is assigned a movement type
in the system.

Example
— 531 (by-product access)
BAPI GM Code Subsequent See the basic explanation above of the field BAPI GM Code (Nor-
(OO process) mal).

Recommendation
For operations of document category OO (order to order), enter
the BAPI GM code here that is used for the subsequent movement
(= goods issue for order). This is normally BAPI code 03.
Movement type Subsequent General
(OO process) Every goods movement (e.g. purchase order to storage) is as-
signed a movement type in the system.

Recommendation
For operations of document category OO (order to order), enter
the movement type here with which the subsequent movement is

Process Data – Softproviding Core Configuration Guide 71/112

Think ahead. Go there.

to be posted. This is normally movement type 261 (GI for order).

This setting has no effect on other document categories.

3.4.3.1 Further Information: Batch Jobs

If a batch job for program /SPDGS/GMOVBTCH is scheduled, it is possible that this batch job is exe-
cuted again, although the batch that was started earlier is still running.

Such situations may occur if the repetition frequency of the batch job is too high and/or a great num-
ber of batch jobs needs to be processed. As a consequence, the data records are processed repeatedly
which results in the creation of duplicate material documents and duplicate follow-on documents in
Accounting.

Such an error situation is prevented by the coordinated scheduling of batch jobs for programs
/SPDGS/GMOVBTCH and /SPDGS/R_JOB_CYCLE_START described below.

This program is the trigger that makes sure that batch jobs can only be executed with program
/SPDGS/GMOVBTCH once the previous job is completed.

Notes
Program /SPDGS/R_JOB_CYCLE_START has been available since the standard Softproviding Core release
v2.40. Up to this version, this program needed to be implemented in the Z-namespace.

A second batch must be assigned to each batch job that is to be repeated. This second batch will trigger the
repetition. Softproviding recommends following this procedure for the creation of jobs.

Procedure
In order to define and set up the batch jobs, proceed as follows (steps 1-5):

1. Create the desired variants for program /SPDGS/GMOVBTCH

— Note: if multiple variants are used, selection parameters used for them must not overlap
or repeat themselves.

2. Create the desired batch job for program /SPDGS/GMOVBTCH

— In this batch job the variants from step 1 are assigned.
— In this batch job, no start condition is maintained. No periodic repetition of this batch
job is to be set.

3. Create the desired variant for program /SPDGS/R_JOB_CYCLE_START

— For information on the available fields see the table below.

4. Create the desired batch job for program /SPDGS/R_JOB_CYCLE_START

— In this batch job the variant from step 3 is assigned.
— In this batch job the start condition is After job. Batch job from step 2 is entered.
— The Job status check field is NOT marked.

Process Data – Softproviding Core Configuration Guide 72/112

Think ahead. Go there.

5. Once all settings have been made, start the batch job from step 2 by calling transaction SM37,
selecting the job, selecting the Release button and then activate the start option Immediately.

Result
Once the batch job /SPDGS/GMOVBTCH is completed, batch job /SPDGS/R_JOB_CYCLE_START
starts automatically and schedules batch job /SPDGS/GMOVBTCH again and with the selected delay
(variant from step 3).

Fields from Program /SPDGS/R_JOB_CYCLE_START (to create the variant in step 3)

Field Name Comments
Period in days Enter the number of days to wait for reprocessing. Entering nu-
merical values (max. 5 digits) is possible.
Time: hours Enter the number of hours to wait for reprocessing. Entry of nu-
merical values 00-23 is possible.
Interval in minutes Enter the number of minutes to wait for reprocessing. Entry of nu-
merical values 1-59 is possible.

Transactions
Transaction Description
SE38 Creating variants
SM36 Defining batch jobs
SM37 Batch jobs overview

3.4.4 Usage
Use
This table is classified as a system table, i.e. the table contents are supplied by Softproviding. It is not
intended for the customer to modify or supplement them.

Caution
After installing Softproviding Core - also as part of an upgrade - Softproviding strongly recommends
checking the entries in table /SPDGS/TMP4 (usage control). It is recommended to compare the deliv-
ered table entries with those in the production system and, if necessary, to make adjustments. If you
have any questions in this regard, please enter an SAP portal message with the IS-MFM component
to contact Softproviding Support.

Recommendation
It is therefore strongly recommended not to modify the table contents. A corresponding message ap-
pears when opening the table: “Caution: this table is cross-client! Do not make any changes (SAP data).”

Process Data – Softproviding Core Configuration Guide 73/112

Think ahead. Go there.

Background
The application is determined for every item (input or output) in Process Data Acquisition. The appli-
cation assigned to the input and output materials determines the further editing options. Examples of
applications include “Enter item” and “Backflushing”.

The table entries are made in each case per:

— Level (e.g. input/output level)
— Level strategy
— Master item (indicator) and
— Strategy category

Table Fields
Field Name Description
Level The level of an application is the table RESB (reservations) for the
input and the table AFPO (order items) for the output.
Level strategy In Further Processing Entry, the order is assigned a PDA strategy.
This strategy can have a different effect on the two levels (in-
put/output). The effect on a level is called the level strategy.
Master If master items are used in the level (i.e. this indicator is set), the
control for the strategy categories can be different. A master item
is a leading input item. All other input items are calculated de-
pendent on the master item.
Strategy category The strategy category defines the properties of an item and deter-
mines the application of an item in Further Processing Entry.

Note
The available strategy categories are predefined by Softproviding and
cannot be changed.

The explanations at the end of this table show how the strategy cate-
gories are usually used.
Usage The application is determined for every input and output item in
Process Data Acquisition. Depending on the application, an entry
and/or calculation may or may not take place.

The following application options are available:

— Enter actual
— Calculate target
— Post backflush
— Post plan = actual
— Calculate target / enter actual

Note
For details on the individual applications, see the explanations at the
end of this table.

Process Data – Softproviding Core Configuration Guide 74/112

Think ahead. Go there.

Field Name Description

The following criteria are used to determine the application:

— Strategy category of the item
— Combination of strategy categories for all items
— Active PDA strategy on the order level
— Indicator in the material master data (tap Process Data Ac-
quisition)
— Indicator Backflushing in the further processing order (re-
quirements)

Assignment is carried out in the system table Use.

Item total If this indicator is set, the actual value of the item is included in
the sum of the level (input or output). The total is optionally used
to calculate the other level. However, this also depends on the
PDA strategy and calculation rule.
Display This setting can override the settings in Customizing that relate
to displaying an item/level.

The following options are available:

— According to master data (material master data: tab Process
Data Acquisition). The master data decides whether an
item/level is shown or not
— Force (the display is forced)
— Suppress (the display is suppressed)

Table Strategy Category

The following table shows the possible strategy categories:

Strategy type Description

Other An “other” item can then be used if an item cannot be assigned to
any other strategy category.
Entry item * Items or materials that are not listed in kg are shown under an en-
try item.
Calculation item * Under a calculation item, the item or material is only calculated
and is not weighed or entered.
Master item A master item is a leading item. All other items are calculated de-
pendent on the master item. The master item is normally used in
the input. However, it also works for the output.
Planning item * Under a planning item, the planned quantity is used as the actual
quantity. The item or material cannot be weighed.
Weight item A weight item is always an item or material that is listed in kg.
Additional item An additional item is not normally entered. It is used to display an
item or material in Further Processing Entry.

Process Data – Softproviding Core Configuration Guide 75/112

Think ahead. Go there.

Note
The use of an item is primarily determined by the PDA strategy (e.g. IWOW = enter input - enter output).
The strategy categories marked with (*) above override the more general PDA strategy.

Example: A calculation item is always calculated, even if the PDA strategy is e.g. IWOW.

Table Usage
The following table shows the possible applications:

Use Description
Enter actual (= A) The actual quantity is entered for the item. Target quantities for
the B and E items are calculated from this quantity. Special case:
Target quantities are only calculated from by-products (output) if
this is explicitly activated in Customizing.
Calculate target (= B) The target quantity for the item is calculated from the A item en-
tries and posted as target=actual when the order is completed. It
is not possible to enter actual quantities for this item.
Post backflushing (= C) The item quantity is automatically posted when the order is com-
pleted. Target calculations or actual entries are not possible.
Post plan = actual (= D) The planned quantity is posted as plan = actual when the order is
completed. Target calculations or actual entries are not possible.
Calculate target - The target quantity for the item is calculated from the A item en-
enter actual (= E) tries and posted as target=actual when the order is completed.
However, the actual quantity can also optionally be entered.

3.4.5 Entry Subscreen

Use
Dedicated (where applicable, customer-specific) entry screens (screen plus logic) are defined in this
table.

This is done for each

— Document group
— Document category
— User and
— Terminal ID

Entries in this table apply to all SAP GUI programs for Process Data Acquisition, such as Further Pro-
cessing Entry, Disassembly Process Entry or Goods Receipt for Purchase Order.

Process Data – Softproviding Core Configuration Guide 76/112

Think ahead. Go there.

Table Fields
Field Name Description
Document group Business transactions are represented in SAP by documents. This
field pools documents of the same group that are treated in the
same way from the perspective of process data acquisition.

Available values
— See input help (F4)

Examples
— Purchase order
— Disassembly order
— Further processing order
Document category In Softproviding Core and Softproviding Meat, document catego-
ries indicate business-related entry operations. They are therefore
a type of categorization.

Example
— Document category GI (goods issue)
— Document category GR (goods receipt)
User name Entries are made in this table on a per-user basis. The username
can also be the entry * (= asterisk). This entry is then valid for all
users.
Terminal ID The terminal ID corresponds to the computer name in Windows
and unambiguously identifies a computer in the local network.

Use
The transaction control is dependent on the terminal ID. If no en-
try is found in this table for the calling terminal, the generic entry
(*) is searched for and used.
Function group The correct function group (program) for the document
group/document category combination is stored in this field. If
entries do not already exist upon delivery, it is recommended to
use the following programs:

Recommendation
All document groups (except for disassembly orders and without
reference) /SPDGS/SAPLWSC2N

For the document group disassembly orders and without refer-

ence /SPMEAT/SAPLWSC2N.
Screen The relevant screens are to be assigned in accordance with the
function groups, if these entries have not already been supplied.

Suitable screens (dynpro numbers) can be found via the Screen

Painter (transaction SE51).

Process Data – Softproviding Core Configuration Guide 77/112

Think ahead. Go there.

Field Name Description

For the two above-mentioned function groups /SPDGS/SAP-

LWSC2N and /SPMEAT/SAPLWSC2N, screen 1003 can be used,
for example.
PDAON Activating this flag ensures that the currently valid entry screen
and function module /SPDGS/PDAON_CREATE_OPERATION is
called.

Recommendation
Set this indicator for all document groups.

3.4.6 Barcodes
Use
The allocation of the variant, barcode number and terminal ID is managed in this table. A freely se-
lectable detail ID must also be created. This detail ID enables assignment to individual fields (field
definition).

Further information and details on using these barcode settings can be found in the Softproviding
Core TechApps documentation BCParser.

Table Fields
Field Name Description
Variants The barcode variant makes it possible to use several different bar-
codes at one PDA point (= location of data entry). If no variant is
desired, this field is automatically filled with the value 0.
Barcode number The barcode number is an unambiguously defined ID that comes
from the DGC (Device Gateway Server). This number determines
the barcode type concerned.

Input help
The barcode number can be selected via the input help.

Example
10 UPC/EAN
11 EAN 8
100 PDF 417
Terminal ID The terminal ID corresponds to the computer name in Windows
and unambiguously identifies a computer in the local network.

Process Data – Softproviding Core Configuration Guide 78/112

Think ahead. Go there.

Field Name Description

Use
The terminal ID describes the work station where the barcode is
read. If the field Terminal ID is empty, all terminals can be used.
Detail ID The barcode detail ID is an unambiguous number (alphanumeri-
cal, max. 4 characters) that is needed for the parsing operation.
This number can be used to determine which Customizing data
record is concerned. In a further step, fields are assigned to the de-
tail ID (see table Field Definition below).

Barcode Definition
Layout name The entry in this field is for information purposes.

Example
This makes it possible to distinguish between various labels for
the same terminal ID.
Barcode separator The barcode separator is an unambiguous identifier that is used to
separate fields in a barcode. In normal situations, this is always
<1D> Therefore, a default value is entered for a new table entry.
However, this value can be changed if required.

Example
FIELD1(1D)Field2(1D)Field3 () replace with <>
Hexadecimal Indicates the barcode or barcode number

This indicator specifies whether the separator is identified as a

string or as a hexadecimal character when the barcode is parsed.
This allows you to maintain non-displayable characters as separa-
tor.

Dependencies
If this indicator is set, a valid hexadecimal value must be specified
as separator. Otherwise, an exception will occur when the parser is
executed.

Example
For an example, please use the F1 help function.
Strict Use
When a barcode is parsed, its content is analyzed and broken down
using the defined fields. If this indicator is activated, the barcode
must be structured in a way that it can be broken down entirely
with these fields. If a rest that cannot be assigned to any of the
fields remains after parsing is completed the barcode is considered
not valid for this barcode definition. It follows that with strict pars-
ing the barcode needs to be broken down completely.

Example
For an example, please use the F1 help function.

Process Data – Softproviding Core Configuration Guide 79/112

Think ahead. Go there.

3.4.6.1 Field Definition

Table Fields
Field Name Description
Field name Field name that appears in the barcode.

Example
— MATNR
— CHARG

Note
Only fields that are contained in the table /SPDGS/SCAN can be used.
Detail ID See the description of the field Detail ID (above). The defined de-
tail ID is entered here.

Input help
The permitted detail IDs can be selected via the F4 help.
Data element The data element is automatically applied using the field name.

A distinction is made below between the barcode types Separator and Fixed separation.

Field Definition
Field Name Description
Barcode type The type of barcode is selected in this field.

Input help
— Separator
— Fixed division

With the separator, the prefix specified in the prior customizing

item is used every time for separation (<1D>). In contrast, for val-
ues with fixed separation, the precise position and the number of
digits must be specified (see table below).

Barcode Separator
Field Name Description
Barcode identifier ID The barcode identifier ID is the max. 4-character code that can as-
sign the fields to the numbers in the barcode. In certain barcode
types (e.g. EAN), these numbers are standardized. Please refer to
the standardized EAN table for this purpose.

Process Data – Softproviding Core Configuration Guide 80/112

Think ahead. Go there.

Number of Digits/Fld (for barcode type Fixed separation)

Field Name Description
Start position This field contains the start position in the barcode. This infor-
mation tells the parser where to begin.
Number of digits This field contains the number of digits in the barcode.

Internal Format?
Field Name Description
Internal format? In internal format, the data is displayed, or the fields filled in the
same manner as they are stored in the database. If this indicator is
set, conversion routines stored in the data element are ignored.

Field Name Description

Decimal places? A drop-down menu with the following options is available for the
Decimal places field:
— Blank (no decimal places)
— D (dynamic number of decimal places)
— X (fixed number of decimal places)

If the value Fixed number of decimal places is set, a value must be

entered in the then visible field Decimal places.

Decimal places give the number of figures permitted after the dec-
imal point for a value.

Dependencies
Decimal places only have significance for the data types CURR,
DEC, FLTP and QUAN.

3.4.7 Scanner Entry

3.4.7.1 Process Variants
The following settings are described in this table:
— Process variants
— Maintenance
— Assigning

After the variants are created, they are assigned to e.g. the user and terminal. The process variant is
used as a filter criterion for the BAdIs used for controlling the scanner.

Process Data – Softproviding Core Configuration Guide 81/112

Think ahead. Go there.

Table Fields
Manage process variants
Field Name Description
PDA process variant (PrVar) The process variant allows specialized control of a process. This
makes it possible to react to different requirements within the
same process.

Dependency
This process variant is assigned in the table Assign process vari-
ant.

Use
The process variant is used as a filter criterion for the BAdIs used
for controlling the scanner.
Description Give the process variant a name in this field.

Assign Process Variants

Field Name Description
User name User’s login name. An asterisk (*) can be entered. If * is entered,
this is valid for all logged-in users.
Terminal ID The terminal ID corresponds to the computer name in Windows
and unambiguously identifies a computer in the local network.

Use
The transaction control is dependent on the terminal ID. If no en-
try is found in this table for the calling terminal, the generic entry
(*) is searched for and used.
Document group Business transactions are represented in SAP by documents. This
field pools documents of the same group that are treated in the
same way from the perspective of process data acquisition.

Input help
The document groups can be found in the input help.

Examples
— Purchase order
— Disassembly order
— Further processing order
Document category In Softproviding Core and Softproviding Meat, document catego-
ries indicate business-related entry operations. They are therefore
a type of categorization.

Example
— Document category GI (goods issue)
— Document category GR (goods receipt)
PDA process variant (PrVar) The process variant described in the table above is assigned here.

Process Data – Softproviding Core Configuration Guide 82/112

Think ahead. Go there.

Field Name Description

Use
The process variant is used as a filter criterion for the BAdIs used
for controlling the scanner.

3.4.7.2 BAdI for Scanner Entry

This Customizing item is used to create the BAdI implementation for BAdI /SPDGS/BADI_PDASCAN
from enhancement spot /SPDGS/BADI_PD_SCANNER.

Note
You can find further explanations and details on these BAdIs in this document under the paragraph “En-
hancements”.

3.5 System Modifications

Open the menu item System modifications in the implementation guide as follows:

Menu Softproviding Core > Logistics > Process Data Acquisition > System
Adjustments

In this Customizing item, various BAdI implementations can be created for the following areas:
— Posting
— Production order and repetitive manufacturing (generated processes)
— Goods movements
— Process postings
— Quality inspection
— Expiration date

Enhancement in area BAdI Methods

Posting /SPDGS/BADI_PDAO Multiple methods
Production order /SPDGS/BADI_PDAGENO 1 method
Repetitive manufacturing /SPDGS/BADI_PDAGENO_REM 1 method
Goods movements /SPDGS/BADI_GMOV Multiple methods
Process postings /SPDGS/BADI_PDAPROC 1 method
Quality inspection /SPDGS/BADI_PDAQCHK Multiple methods
Expiration date SPDGS/PDAO_BATCH_EXPIRA- 1 method
TION

Note
You can find further explanations and details on these BAdIs in this document under the paragraph “En-
hancements”.

Process Data – Softproviding Core Configuration Guide 83/112

Think ahead. Go there.

3.6 Archiving
Open the menu item Archiving > Process Data Table in the implementation guide as follows:

Menu Softproviding Core > Logistics > Process Data Acquisition > Archiv-
ing > Process Data Table

The settings for the following tables are described in this section:
— Residence times

Use
Archiving or physical deletion of process data is performed using the SAP standard transaction SARA.
The data archiving procedure corresponds to the SAP standard procedure for this activity.

In this table, residence times are stored for each plant, document group and document category. The
residence time is the configurable time period that must elapse before the system can archive the ap-
plication data of an archiving object. The application data is only selected and checked for archiving
suitability after the end of this time period.

The residence times stored in this table are relevant for the Softproviding archiving object
/SPDGS/PD (process data).

Data from the following tables are archived with this object:
— /SPDGS/MPCT Calculated target from physical entries
— /SPDGS/PD_CONID PDAO Index table Conid
— /SPDGS/PD_TENUM PDAO Index table Tenum
— /SPDGS/PDAO (PDA operation = process data)
— /SPDGS/PDAOE1 (PDAO custom extension 1)
— /SPDGS/PDOF PDA operation flow

Prerequisites
Entries can only be made in the table “Residence times” if the following entry is present in the table
TVDIR (open via View V_TVDIR):

View/Table /SPDGS/V_TARC
Function group /SPDGS/GENTAB
Maintenance type 1
Overview screen 16
No. of individual screen 0

Process Data – Softproviding Core Configuration Guide 84/112

Think ahead. Go there.

Example
Process data from Further Processing Entry (goods receipt and goods issue in plant 1000) should be
archived. Order data is only to be archived two months after the deletion notice is set and can only be
fully deleted at the earliest one month after the deletion marker is set.

Entries can then be made as follows:

Plant Document Group Document Cate- Residence Time 1 Residence Time 2

gory
1000 Further processing order Goods receipt 2 1
1000 Further processing order Goods issue 2 1

Table Fields
Field Name Description
Plant The plant serves as a production site for a company.
Document group Business transactions are represented in SAP by documents. This
field pools documents of the same group that are treated in the
same way from the perspective of process data acquisition.

Input help
The document groups can be found in the input help.

Examples
— Purchase order
— Disassembly order
— Further processing order
Document category In Softproviding Core and Softproviding Meat, document catego-
ries indicate business-related entry operations. They are therefore
a type of categorization.

Example
— Document category GI (goods issue)
— Document category GR (goods receipt)
Residence time 1 Definition
Residence time 1 specifies the time span in calendar months that
must elapse between the setting of the delete flag (stage 1) and
the setting of the deletion indicator (stage 2).

As a rule, the following three stages must be gone through before

data of an object (e.g. order data) can be archived and deleted:
— Stage 1: Setting the delete flag (reversible)
— Stage 2: Setting the final deletion indicator (not reversible)
— Stage 3: Reorganization (swapping out for sequential stock
and deletion from the system)

Process Data – Softproviding Core Configuration Guide 85/112

Think ahead. Go there.

Field Name Description

Recommendation
Choose a Residence time 1 that allows you to be certain that or-
ders not used within the residence time will no longer be needed
in future either.
Residence time 2 Definition
Residence time 2 specifies the time span in calendar months that
must elapse between the setting of the deletion indicator (stage 2)
and the reorganization (stage 3).

Note
The Softproviding Core user documentation Archiving describes the prerequisites and the archiving pro-
cess for this archiving object in detail.

3.7 Miscellaneous
Open the menu item Other in the implementation guide as follows:

Menu Softproviding Core > Logistics > Process Data Acquisition > Miscella-
neous

The settings for the following table are described in this section:
— Warehouse Stock Cleanup: Movement Types
— Purchase Order Category (Purchasing)

3.7.1 Warehouse Stock Cleanup: Movement Types

Use
The Softproviding Core program Clear Warehouse Stocks enables you to adjust the stock levels in the
SAP system in line with the actual physical levels in the warehouse. Here, stock levels can be com-
pletely cleared (i.e. set to zero. The program is integrated in the Softproviding Core application menu
in the Process Data Acquisition area.

The appropriate settings must be applied in this Customizing table before the program can be used.
You must ensure that the movement type is correctly assigned to the combination of plant, storage
location and stock type, and that the BAPI code is also correctly assigned.

Note
The Softproviding Core user documentation Process Data describes the prerequisites and the program im-
plementation in detail.

Process Data – Softproviding Core Configuration Guide 86/112

Think ahead. Go there.

Table Fields
Field Name Description
Plant The plant serves as a production site for a company.
Storage location The storage location is an organizational unit which allows a dis-
tinction to be made between the different inventories within a
plant.
Stock type The stock type specifies the stock into which the material is
posted in goods receipt or from which it is posted in goods issue.

Example
— Unrestricted use stock
— Blocked stock
— Quality inspection stock
Special stock indicator This indicator specifies the type of special stock concerned.
Clear The movement type that is to be used to completely clear the
stock levels (i.e. set to zero)
Issue The movement type that is to be used to post material issues from
the warehouse.
Receipt The movement type that is to be used to post material receipts in
the warehouse.
BAPI GM Code Control of the goods movement posting is derived from the BAPI
code assigned here.

Input help
The available BAPI codes can be selected via the input help.

Note
For the individual BAPI codes, please refer to the documentation on
the function module BAPI_GOODSMVT_CREATE (in particular the
field GM_CODE) (opened using transaction SE37).

Note
It is not possible to make a posting without assigning a BAPI code.

3.7.2 Purchase Order Category (Purchasing)

Use
This table is used to assign the desired Purchasing document types to a purchasing document cate-
gory. This assignment is required, so the necessary purchasing documents can be called up in the
Goods Receipt for Purchase Order application in the Process Data Cockpit.

Process Data – Softproviding Core Configuration Guide 87/112

Think ahead. Go there.

Selecting purchasing documents and performing data entries is only possible for the combinations of
purchasing document categories and purchasing document types stored here

Table Fields
Field Name Description
Plant The plant serves as a production site for a company.
Purchasing document cate- In this field, the purchasing document category is stored.
gory
Available values
— See input help (F4)

Examples
— Request for quotation
— Purchase requisition
— Purchase order
Purchase order type Assignment of a purchase order type.

Use
Only the keys assigned here are considered in the Process Data
Cockpit during a data selection. In the application, the Purchasing
document type field is also a selection criterion.

Available values
— See possible input help (F4)

Example
— NB Normal purchase order
— UB Stock transfer order
Maximum number of docu- In the Goods Receipt for Purchase Order application in the Process
ments Data Cockpit, only so many documents are displayed as were al-
lowed to in this field.

Please do note that this refers to the number of purchase order

items and not the number of purchasing documents.

Process Data – Softproviding Core Configuration Guide 88/112

Think ahead. Go there.

4 Enhancements

BAdIs (Business Add-Ins) are used to create customer-specific program enhancements that can be
implemented by the customer if required. These enhancements remain unaffected in the event of a
release change. SAP standard transactions are used to implement BAdIs.

If enhancements are available for an application whose settings are described in this configuration
guide, this is indicated at the relevant point (both in the user documentation and here in the configu-
ration guide).

Prerequisites
Approval for creating/changing BAdI implementations
— Developer key

The following options are available for customer-specific enhancements (BAdIs):

— SAP standard enhancements
— Enhancements by Softproviding

4.1 SAP Standard Enhancements

SAP standard enhancements are BAdIs provided by SAP that are used in SAP standard programs and
may also be advantageous to use in Softproviding Core or Softproviding Meat programs/processes. If
this is the case, the possibility of using these BAdIs is indicated at the relevant point.

These enhancements are divided into

— Mandatory enhancements (enhancements that must be applied)
— Optional enhancements (enhancements that do not have to be applied)

The enhancements and the associated methods are listed in this chapter.

4.1.1 Mandatory Enhancements

BAdI Function Area Method Description

4.1.2 Optional Enhancements

BAdI Function Area Method Description

Process Data – Softproviding Core Configuration Guide 89/112

Think ahead. Go there.

4.2 Softproviding Core and Meat Enhancements

Softproviding offers its own BAdIs for customer-specific implementation for programs in Softprovid-
ing Core and Softproviding Meat. The description in this configuration guide indicates the opportuni-
ties to use these BAdIs.

These enhancements are divided into

— Mandatory enhancements (enhancements that must be applied)
— Optional enhancements (enhancements that do not have to be applied)

The enhancements and the associated methods are listed in this chapter.

4.2.1 Mandatory Enhancements

BAdI Function Area Method Description

4.2.2 Optional Enhancements

BAdI /SPDGS/BADI_ORDER_PAIR
Enhancement spot /SPDGS/BADI_PA_ORDER_PAIR

Customer-specific search for order pairs

This BAdI enables you to redefine the search for order pair formation. In the standard settings for
Softproviding Core, e.g., orders with the same order start date and/or scheduled start date can be used
to form pairs. If pair formation is to take place based on other fields, e.g. release date or MRP controller,
a customer-specific implementation must be developed.

BAdI Function Area Method Description

/SPDGS/BADI_PA_O Pair Formation (fur- FILTER_ORDER Filtering the order
RDER_PAIR ther processing/dis-
assembly processes)
/SPDGS/BADI_PA_O Pair Formation (fur- GET_CONDITION Build dynamic part of the
RDER_PAIR ther processing/dis- WHERE condition.
assembly processes)
/SPDGS/BADI_PA_O Pair Formation (fur- GET_CONDITION_PUR- Build dynamic part of the
RDER_PAIR ther processing/dis- CHASING WHERE condition.
assembly processes)
/SPDGS/BADI_PA_O Pair Formation (fur- GET_CONDITION_DE- Build dynamic part of the
RDER_PAIR ther processing/dis- LIVERY WHERE condition.
assembly processes)

Process Data – Softproviding Core Configuration Guide 90/112

Think ahead. Go there.

BAdI Function Area Method Description

/SPDGS/BADI_PA_O Pair Formation (fur- PDAOE1_CHANGING lt_pdaoe1 changing before
RDER_PAIR ther processing/dis- PDAO Create
assembly processes)
/SPDGS/BADI_PA_O Pair Formation (fur- PDAC_CHANGING lt_pdac changing before
RDER_PAIR ther processing/dis- PDAO Create
assembly processes)

BAdI /SPDGS/BADI_PDAGENO
Enhancement spot /SPDGS/BADI_PA_GENERIC_OPS

Editing generated operations

This BAdI is used to influence or modify data from generated PDA data records.

BAdI Function Area Method Description

/SPDGS/BADI_PDAG Further Processing MAIN- Collects and processes
ENO Entry TAIN_POSTED_OPERA- generated operations (see
TIONS description below)

Method MAINTAIN_POSTED_OPERATIONS
The generated operations from target = actual and plan = actual postings are first collected and then
processed together. In this way, it is possible to implement an incompleteness dialog even with non-
SAP interfaces. When processing the collected records (flush), the method MAINTAIN_POSTED_OP-
ERATIONS is implemented before the completeness check. There is an incompleteness flag for every
relevant data field in the internal table XT_MPPO (changing parameter for the method).

Example
For the field CHARG there is the flag CHARGX.

BAdI /SPDGS/BADI_PDAGENO_REM
Enhancement spot /SPDGS/BADI_PA_GENERIC_OPS

Editing generated operations (mass production)

This BAdI is used to influence or modify data from generated PDA data records.

BAdI Function Area Method Description

/SPDGS/BADI_PDAG Further Processing MAIN- Collects and processes gen-
ENO_REM Entry TAIN_POSTED_OPER- erated operations (see de-
ATIONS scription below)

Method MAINTAIN_POSTED_OPERATIONS
The generated operations from target = actual and plan = actual postings are first collected and then
processed together. In this way, it is possible to implement an incompleteness dialog even with non-

Process Data – Softproviding Core Configuration Guide 91/112

Think ahead. Go there.

SAP interfaces. When processing the collected records (flush), the method MAINTAIN_POSTED_OP-
ERATIONS is implemented before the completeness check. There is an incompleteness flag for every
relevant data field in the internal table XT_MPPO (changing parameter for the method).

Example
For the field CHARG there is the flag CHARGX.

BAdI /SPDGS/BADI_PDASCAN
Enhancement spot /SPDGS/BADI_PD_SCANNER

PDA image control with scanner

Process data acquisition transactions (e.g. /SPDGS/PDAON Further Processing Entry) can optionally
be operated virtually completely via a scanner. Both serial and keyboard scanners are supported here.
The scanned string is analyzed in every Dynpro and the selection of orders, items etc. is made and
navigation triggered on this basis.

Only one implementation can be created for this BAdI. A complex fallback implementation is already
supplied as standard with the class /SPDGS/CL_IM_BADI_PDASCAN. This should be used where
possible.

Individual implementation or modification of the standard logic requires deep and extensive
knowledge of dialog control in process data acquisition.

Note
It is strongly recommended to allow this development to be controlled by Softproviding.

BAdI Function Area Method Description

/SPDGS/BADI_PDAS- Process data/scanner Various methods avail- This BAdI can be used to
CAN able. enhance PDA image con-
trol with a scanner.

There is one method each for serial and keyboard scanners for each Dynpro in process data acquisi-
tion. In the interface, further data from the actual image is supplied along with the scanned string.
The control is influenced by a return parameter of structure /SPDGS/SMPSC. There is also a common
method for the PBO time in Dynpro 1032.

BAdI /SPDGS/BADI_PDAO
PDA posting

BAdI Function Area Method Description

/SPDGS/BADI_PDA Process data/posting Various methods avail- This BAdI is used to influ-
O able. ence the PDA data during
posting.

Process Data – Softproviding Core Configuration Guide 92/112

Think ahead. Go there.

Methods
CREATE_BATCH
Edit communication structure for BATCH_CREATE.

DELETE_OPR_BEFORE
Before deleting an operation.
This method can prevent PDC operations from being deleted. This may become necessary if e.g. sub-
sequent operations are based on this operation that can no longer be canceled or deleted.

DELETE_OPR_AFTER
After deleting an operation.
This method can perform subsequent functions for deleting a PDC operation. This is necessary if sub-
sequent operations for a PDC operation must be canceled or deleted.

INSERT_CUSTOM_EXTENSION
Post PDAO Custom Extension.
Method for posting additional data (PDAO Custom Extension) for a PDAO. This additional data is
stored as standard in the table /SPDGS/PDAOE1. However, if the BAdI /SPDGS/BADI_PDAO has
been activated, the standard posting is triggered by the method INSERT_CUSTOM_EXTENSION.
Therefore, implementation is mandatory if the PDAO Custom Extension is used.

BEFORE_PDA_VALIDATION
Modify/repair PDAO before the validity check.

CUSTOM_PERIOD_FOR_DAILY_BATCH
Customer-specific period for daily batch

BAdI /SPDGS/BADI_GMOV
Goods movements

BAdI Function Area Method Description

/SPDGS/BADI_GMOV Process data/goods Various methods avail- This BAdI is used to influ-
movement able. ence or modify PDA data
when generating the goods
movement.

Methods
SPLIT_CRITERIA
Set split criteria.
When generating the material document, the PDC operations (table PDAO) is compressed as much as
possible. All records that have the same values in the following fields are merged:
— LIFNR Vendor
— BELGR Document group
— BELTY Document category
— BWART Movement type
— WERKS Plant
— MATNR Material

Process Data – Softproviding Core Configuration Guide 93/112

Think ahead. Go there.

— CHARG Batch
— LGORT Storage location
— UMWRK Target plant
— UMLGO Target storage location
— UMMAT Target material
— UMCHA Target batch

Further customer-specific split criteria can be defined using the field SPCRI.

ITEM_TEXT
Set item text.
This method can be used to set the item text for the material document. It must be noted that differing
texts cause an item split.

CREATE_BEFORE1
This method is implemented before the goods movement is generated.
The PDAO data is already copied to the GMIT (Goods Movement Item) but is not yet compressed (AP-
PEND or COLLECT is performed directly after this method is implemented).

CREATE_BEFORE2
This method is implemented before the goods movement is generated.
The PDAO data is already copied to the GMIT (Goods Movement Item) and compressed. There is no
longer a connection to the individual PDAO records.

CREATE_BEFORE3
Before generating the material document.
The BAPI header data can be manipulated using this method.

CREATE_BEFORE4
BAPI call.
This method replaces the BAPI call with a customer-specific development.

CREATE_BEFORE5
Before generating the material document
This method is used during goods movements for delivery. It allows the customer to influence the
BAPI header data.

CREATE_BEFORE6
Before generating the material document – with error return.

CREATE_BEFORE7
Before generating the material document – BAPI item data.

CREATE_AFTER1
After generating the material documents.
This method is implemented after the material documents are generated. The material document
numbers are already entered in IT_PDAO. It is possible for the documents to be available in the data-
base in incomplete form if material documents are posted asynchronously.

CANCEL_BEFORE1

Process Data – Softproviding Core Configuration Guide 94/112

Think ahead. Go there.

Before generating the PDAO cancelation records (source records).

Cancelations can be made in two ways in Softproviding Core: In relation to an existing PDAO record
(GMOV_CANCEL_GOODSMVT) or in the form of an actual entry (GMOV_CREATE_GOODSMVT).
This BAdI method only works in the first case (GMOV_CANCEL_GOODSMVT).

CANCEL_BEFORE2
Before generating the PDAO cancelation records (target records).

CANCEL_AFTER1
After generating the PDAO cancelation records.
The original data records for which cancelations are to be generated are located in IT_SOURCE. These
cancelation records are located in IT_TARGET. This data has already been posted. The time that the
cancelation is posted in MM depends on the Softproviding Core Customizing settings.

BAdI /SPDGS/BADI_PDAPROC
Process postings
BAdI Function Area Method Description
/SPDGS/BADI_PDAP- Process postings SELECT_BATCH This BAdI is used to deter-
ROC mine the batch number in
batch processing.

Methods
SELECT_BATCH
Here it is determined which batch is used during input posting to a subsequent order (order pairs, pro-
cess posting). The method is only implemented if the subsequent order includes any batches. At this
time point, the batches have already been automatically stored in the database.

Note
Please note when implementing this method that a GUI is not necessarily available. Implementation may
take place e.g. via DGAs in the background.

Process Data – Softproviding Core Configuration Guide 95/112

Think ahead. Go there.

BAdI /SPDGS/BADI_PDAQCHK
Quality inspection
BAdI Function Area Method Description
/SPDGS/BADI_PDAQ Quality inspection Multiple methods This BAdI can be used to
CHK manipulate the inspection
relevance of a PDA opera-
tion (PDAO). Only values
according to domain
/SPDGS/QINSP may be set.

Methods
FORCE_OR_SUPPRESS_INSPECTION
Forces or suppresses the inspection.

SET_INSPECTION_POINT
Setting inspection points (see method documentation)
This method is implemented if an inspection lot for a PDA operation (PDAO) has inspection point rel-
evance. At this time point, the inspection lot has already been generated and exists on the database
(COMMIT WORK has been executed).

BAdI /SPDGS/PDAO_BATCH_EXPIRATION
Expiration date
BAdI Function Area Method Description
/SPDGS/PDAO_BATC Expiration date 1 method This BAdI can be used to
H_EXPIRATION define customer-specific
expiration date calcula-
tions.

Methode
HANDLE_CUSTOM_EXP_DATE

BAdI /SPDGS/BADI_AT_COND
Component replacement / implement conditions

BAdI Function Area Method Description

/SPDGS/BADI_AT_C Component replace- CONDITION This BAdI enables you to
OND ment define the condition for
component replacement.
The conditions are defined
in DGS Customizing and
implemented in this BAdI.

Process Data – Softproviding Core Configuration Guide 96/112

Think ahead. Go there.

Method

CONDITION
Define condition.
This method can be used to define or create the condition for a replacement variant in component
replacement.

BAdI /SPDGS/BADI_AT_EXEC
Component replacement / post replace

BAdI Function Area Method Description

SPDGS/BADI_AT_EX Component replace- REPLACE See text for method
EC ment

Method
REPLACE
Replace input component.
In this method, the component replacement function is implemented in order to replace one input
component with another.

Recommendation
It is recommended to use the BAdI /SPDGS/BADI_AT_EXEC as supplied and not to execute any cus-
tomer-specific implementation here, as this BAdI already contains all the necessary programming to
post the replacement.

“Posting” replaces the material to be replaced with the replacement material and determines the
quantity in accordance with the factor definition (see table above).

BAdI /SPDGS/BADI_BATCH_CALC
Enhancement spot /SPDGS/BADI_PA_BATCH_CALC

Calculating batch sizes (production batches)

The batch size can be modified for individual customers using the BAdI SPDGS/BADI_BATCH_CALC.
As a rule, the batch size for the further processing order is taken from the material master data (tab
Process Data Acquisition). Customer-specific coding can be used to recalculate this batch size.

BAdI Function Area Method Description

/SPDGS/BADI_BATC Further Pro- CALCU- Customer-specific recalcu-
H_CALC cessing/production LATE_BATCHES lation of the batch size
batches

Method
CALCULATE_BATCHES
Calculate batch size and number of batches.

Process Data – Softproviding Core Configuration Guide 97/112

Think ahead. Go there.

BAdI /SPDGS/BADI_CHANGEID
Enhancement spot /SPDGS/BADI_PA_CHANGEID

Change control
This BAdI can be used to store further customer-specific fields (in addition to the change ID number)
in the table /SPDGS/PDAOE1.

BAdI Function Area Method Description

/SPDGS/BADI_CHAN Change control FILL_CHANGEID See description of the
GEID method

Method
FILL_CHANGEID
fill structure /spdgs/changeid
This method can be used to fill in the customer-specific fields for change control in the structure
/SPDGS/CHANGEID and store them in the table /SPDGS/CHANGEID.

BAdI /SPDGS/BADI_TIMETICKETS
Enhancement spot /SPDGS/BADI_PA_TIMETICKETS

BAdI Function Area Method Description

/SPDGS/BADI_TIME BAPI structure PP Multiple methods See description of the
TICKETS confirmation methods
Timetickets

Methods
TIMETICKETS_BEFORE
Fill Timetickets before.

TIMETICKETS_AFTER
Fill Timetickets after.

BAdI /SPDGS/BADICALL_GMOV
BAPI replacement calls
This BAdI is used to replace specific BAPI calls.

BAdI Function Area Method Description

/SPDGS/BADI- Multiple methods See description of the
CALL_GMOV methods

Methods
BAPI_CALL_GOODSMVT_CREATE

Process Data – Softproviding Core Configuration Guide 98/112

Think ahead. Go there.

Replaces the call for BAPI BAPI_GOODSMVT_CREATE.

BAPI_CALL_MATPHYSINV_COUNT
Replaces the call for BAPI BAPI_MATPHYSINV_COUNT

GOODSMVT_CREATE
Replace form goodsmvt_create.

BAdI /SPDGS/DG_DGC_INIT
Enhancement spot /SPDGS/DG_DGC_SERVER

BAdI for DGC server

BAdI /SPDGS/DG_DGC_INIT is implemented upon initialization of the service, i.e. when the service
is started. The service connects to SAP and supplies the plant and terminal to the BAdI (from Custom-
izing) and awaits a table in return listing the DGC devices to be connected. Methods can be imple-
mented right at startup for these devices, e.g. in order to set parameters in the driver or start Advise
objects.

In addition to the devices to be connected, error messages and a return code can also be sent to the
service.

BAdI Function Area Method Description

/SPDGS/DG_DGC_INI Initialize driver INIT_DGC See description of the
T method

Method
INIT_DGC
Initialize DGC

Example
A terminal logs on in plant 0001. A barcode scanner that is to be used is connected to this terminal. In
the request table in the BAdI, an entry must be made for the scanner with the IP address of the DGC
and the DGC line. In addition, the method StartAdvise must also be implemented in this case so that
the DGC can also send the scan events from the scanner to the service. If errors occur, the return code
can be set accordingly, and text entered in the error table.

Note
The BAdI /SPDGS/DG_DGC_INIT must be implemented when communicating with the DGC server service.
The DGC server service is a Windows service that can connect one or more DGCs (potentially on different
terminals) directly to the SAP system. Methods for the DGC devices can then be implemented via the ser-
vice or Advise objects routed from the device to SAP, where they trigger a processing operation.

BAdI /SPDGS/DG_DGC_REQ_FROM_NET
Enhancement spot /SPDGS/DG_DGC_SERVER

Process Data – Softproviding Core Configuration Guide 99/112

Think ahead. Go there.

Processing service requests

This BAdI is implemented if the service wants to trigger a processing operation in SAP. This may be
the case, for example, if the DGC sends an Advise object to the service. This Advise object is then
forwarded to the SAP and thus to the BAdI. Here a decision can be made as to what should happen
with the Advise object, whether a subsequent processing operation is to be triggered and what this
will be.

The BAdI supplies the plant and terminal as parameters so that the request can be allocated in organ-
izational terms. In addition, a return code and four more tables are supplied. One of these tables con-
tains driver information for the DGC devices (if this was previously requested). Another one contains
errors that have occurred in the service or DGC, for example if a connection to a device could not be
established. The third table contains the data from the Advise object sent by the DGC. The final table
contains answers to requests from the SAP system. Here, a request corresponds to a method that is
implemented by SAP but has been processed with a time delay and asynchronously.

BAdI Function Area Method Description

/SPDGS/DG_DGC_RE RE- See description of the
Q_FROM_NET QUEST_NET_TO_SAP method

Method
REQUEST_NET_TO_SAP
Request from DGC

Example
A barcode scanner is connected to the SAP system via a DGC and a DGC server service. If scanning is
performed here, the DGC creates an Advise object. This is sent to the service, which forwards it on to
the SAP system. This BAdI can be used to decide what happens to this scan, where applicable depend-
ing on what was scanned. If it was a container number, for example, posting of the container from the
warehouse can be triggered.

Note
The BAdI /SPDGS/DG_DGC_REQ_FROM_NET must be implemented when communicating with the DGC
server service. The DGC server service is a Windows service that can connect one or more DGCs (poten-
tially on different terminals) directly to the SAP system. Methods for the DGC devices can then be imple-
mented via the service or Advise objects routed from the device to SAP, where they trigger a processing
operation.

4.3 User-Exits
4.3.1 Overview
Introduction
User exits are enhancements provided by SAP. Using user exits allows you to influence the behavior
of SAP standard programs without actually making any modifications.

Process Data – Softproviding Core Configuration Guide 100/112

Think ahead. Go there.

User exits can be profitably used in different Softproviding Core and Softproviding Meat processes.
For this reason, we recommend that you use the user exits listed in this document if, from a process
point of view, an implementation is advisable in your company.

Transactions
Transaction SMOD can be used to search for existing user exits. In addition, the enhancements (ob-
jects) are documented there in detail.

Transaction CMOD is used to create, activate, or deactivate projects and to display existing projects
with the enhancements.

If modifications are implemented in a different way (for example, SAP Standard programs that can be
modified explicitly), this option is described accordingly.

Procedure
1. Start the Project Management functionality of the SAP enhancement using transaction CMOD.
Enter a name in the Project field (e.g. ZMEAT o ZCORE).

2. Then, select the Create button and enter a short description of the project.

3. Save the project. Use the desired package (for instance, $TMP (temporary objects are never
transported). It is recommended to use the $TMP package.

4. Enter the desired enhancement and select Enter.

5. Selecting the Component button will display the assigned function exits. These can be extended
with the coding described below (see the "Enhancements" section).

6. These user exits are activated with the Activate button. The user exits only take effect when the
components and the project are activated.

Note
The SAP enhancements are grouped together under a project name to create enhancement projects. An
enhancement project consists of at least one SAP enhancement. SAP enhancements in the same enhance-
ment project are always activated and deactivated together.

The SAP enhancements have been created by SAP and generally consist of several components. The cus-
tomer selects the SAP enhancements that they want to edit, assembles them into enhancement projects,
processes the components, and activates the projects.

If the extension is already assigned to another project, an error message is displayed. In this case, any
further steps must be coordinated so that both user exits continue to function.

Process Data – Softproviding Core Configuration Guide 101/112

Think ahead. Go there.

4.3.2 Mandatory Enhancements

The following user exits are mandatory enhancements since they are usually required when using
Softproviding Core or Meat. An implementation is therefore recommended.

4.3.2.1 Batch Where-Used List

Function
With this enhancement, batch traceability with regard to disassembly process orders was imple-
mented in the Batch Information Cockpit (transaction BMBC).

Enhancement Short Text Component

SAPLCHVW Batch Where-Used List EXIT_SAPLCHVW_001

Procedure
1. Double-click on component EXIT_SAPLCHVW_001.

2. Create include ZXBWLU01 (in the function module by double clicking on the include name).

3. The following code can be copied and inserted:

CALL FUNCTION '/SPMEAT/EXIT_CHVW_EXPLODE_ALL'

TABLES
xt_shadow = t_shadow.

CALL FUNCTION '/SPMEAT/EXIT_CHVW_HKW'

TABLES
xt_shadow = t_shadow[ ].

Documentation
Module /SPMEAT/EXIT_CHVW_HKW is described in detail in the SAP documentation for the func-
tion module.

4.3.2.2 Order Confirmation (Further Processing)

Function
Determining customer-specific default values in order confirmation. The PDAO data record quantities
are accessed when further processing orders are confirmed.

Process Data – Softproviding Core Configuration Guide 102/112

Think ahead. Go there.

Enhancement Short Text Component

CONFPP01 PP Order Confirmation: Determine Customer-Specific EXIT_SAPLCORF_101
Default Values

Procedure
1. Double-click on component EXIT_SAPLCORF_101.

2. Create include ZXCOFU11 (in the function module by double clicking on the include name).

3. The following code can be copied and inserted:

include /spdgs/zxcofu11_userexit.

4.3.2.3 Requirements Planning (MD01)

Function
Material requirements planning can be restricted to the materials defined in the Softproviding Core
Customizing table /SPMEAT/TMD01 (control user exit MD01; IMG: Softproviding Meat > Production >
Requirements Planning > SAP MRP).

Note
An entry in this table is only possible if a control key has been created in the SAP Standard table T450U
(user exit Material selection for the planning run; IMG: Production > Material Requirements Planning
> Planning). This control key is then assigned in planning run MD01.

Enhancement Short Text Component

M61X0001 User-Exits PP-MRP Requirements Planning EXIT_SAPLM61C_001

EXIT_SAPMM61X_001

Procedure
1. Double-click on component EXIT_SAPLM61C_001.

2. Create include ZXM61U02 (in the function module by double clicking on the include name).

3. The following code can be copied and inserted:

include /spmeat/zzxm61u02.

1. Double-click on component EXIT_SAPMM61X_001.

2. Create include ZXM61U01 (in the function module by double clicking on the include name).

Process Data – Softproviding Core Configuration Guide 103/112

Think ahead. Go there.

3. The following code can be copied and inserted:

include /spmeat/zzxm61u02.

Note
The coding for both function modules (EXIT_SAPMM61X_001, EXIT_SAPLM61C_001) should be identi-
cal, that is, the includes ZXM61U01 and ZXM61U02 should be identical. For more information, see the
description of enhancement M61X0001 (transaction SMOD).

4.3.2.4 Requirements/Stock List (MD04)

Function
Enhancement Short Text Component
M61X0002 User-Exits PP-MRP Requirements Planning Evalua- EXIT_SAPLM61R_001
tions
EXIT_SAPMM61R_001

Procedure
1. Double-click on component EXIT_SAPLM61R_001.

2. Create include ZXM61U03 (in the function module by double clicking on the include name).

3. The following code can be copied and inserted:

if not ibutt1 is initial.

call function '/SPMEAT/USEREXIT_SAPLM61R_001'
exporting
is_mdez = imdezexit
is_mdps = ie3mdpslx
importing
e_usex = emdezx_usex1.
endif.

Note
There are three exit buttons in transaction MD04. If the first one is taken, the second or third one must be
used. Then ibutt2 or ibutt3 should be used instead of ibutt1 and emdezx_usex2 or emdezx_usex3 instead
of emdezx_usex1.

1. Double-click on component EXIT_SAPMM61R_001.

2. Create include ZXM61U04 (in the function module by double clicking on the include name).

3. The following code can be copied and inserted:

Process Data – Softproviding Core Configuration Guide 104/112

Think ahead. Go there.

CALL FUNCTION '/SPMEAT/USEREXIT_SAPMM61R_001'

IMPORTING
e_button_ez = button1_ez.

Note
Here too, the three exit buttons must be considered. If another than the first above-mentioned button is
used, use button2_ez or button3_ez instead of button1_ez.

4.3.3 Optional Enhancements

The following user exits are optional and are recommended for use by Softproviding provided they
can be used in productive operation.

4.3.3.1 Order Confirmation (Process Orders)

Function
Determine customer-specific default values for order confirmation.

Enhancement Short Text Component

CONFPI01 Process Order Confirmation: Determine Customer- EXIT_SAPLCORF_401
Specific Default Values

Procedure
Double-click on component EXIT_SAPLCORF_401.

Create include ZXCOFU06 (in the function module by double clicking on the include name).

The following code can be copied and inserted.

include /spdgs/zxcofu06_userexit.

4.3.3.2 Actual Data Entry (Repetitive Manufactur-

ing)
Function
Extend PDAO records with data from Repetitive manufacturing.

Process Data – Softproviding Core Configuration Guide 105/112

Think ahead. Go there.

Enhancement Short Text Component

XMRM0001 Customer-Exits: Actual Data Entry (Backflush) Repet- EXIT_SAPLBARM_004
itive Manufacturing

Procedure
1. Double-click on component EXIT_SAPLBARM_004.

2. Create include ZXMRMU04 (in the function module by double clicking on the include name).

3. The following code can be copied and inserted:

include /spdgs/zxmrmu04_userexit.

Process Data – Softproviding Core Configuration Guide 106/112

Think ahead. Go there.

5 Other

This chapter describes the master data and programs that are relevant to the applications in this con-
figuration guide but are not set or executed by the end user. For this reason, these functions are not
described in the relevant user documentation but in the configuration guide.

These are
— Master data for which Softproviding provides its own transactions in the application menu or
— Transactions or maintenance views that are not explicitly included in the application menu

In terms of process data, this currently refers to the following master data and settings or programs:
— Component replacement
— Period batch

5.1 Component Replacement

Use
The component replacement can be used in Further Processing to replace one or more bill of materials
components provided for production with other components (= interchangeable parts). These mate-
rials are defined as alternative components.

Prerequisites
— In order to perform component replacement in the application, the replacement relationship
between the components to be replaced and the replacement material must be defined in the
master data table (view cluster /SPDGS/VC_ATKO). This view can also be opened via the
transaction /N/SPDGS/AT01. These table fields are described below.
— As a rule, component replacement must be activated (see IMG menu Softproviding Core > Lo-
gistics > Process Data Acquisition > Organization > Terminals).

Enhancements (Optional)
Further conditions for component replacement can be defined on a customer-specific basis using
BAdIs. This function is described in this chapter in the section “Component replacement” above (see
IMG menu Softproviding Core > Logistics > Process Data Acquisition > Orders > Component Replace-
ment).

Procedure
Start the activity Component Replacement as follows:

Process Data – Softproviding Core Configuration Guide 107/112

Think ahead. Go there.

Menu Softproviding Core > Process Data Acquisition > Processing > Com-
ponent Replacement
Transaction /N/SPDGS/AT01

When managing the table Component Replacement with this transaction (header and item data), it is
defined, based on the plant, which materials can be replaced with other materials. In order for a re-
placement to be possible, the corresponding entries must be made in this table.

5.1.1 Create Entries for Replacement

Field descriptions for the table Component Replacement (header and item data)

Header Data
Field Names Description
Plant The plant serves as a production site for a company.
Material (component) This material is the material to be replaced. The replacement
takes place using a material stored in the item data (see table Item
Data).
Material (product) This material is the material to be produced. An optional entry can
be used to further limit the replacement reference via the product.
Old Every material/plant combination must be provided with a se-
quential number in this field. You must start with the value 1 for
every material/plant combination.

Entries for the same material/plant combination are distinguished

using sequential numbers (1, 2, 3 etc.).

As a rule, the entry with the number 1 is always used for the re-
placement.

Multiple entries for the same material/plant combination can be

given the same number in the field Old (e.g. the value 1) if they
are distinguished using sequential numbers in the field Replace-
ment variant (see description in field Replacement variant).

Note
The value 0 (zero) in the field Old is ignored by the program.
Replacement Variant Multiple entries for the same material/plant combination that
have been given the same number in the field Old can be distin-
guished using sequential numbers entered in this field.

In this case, all stored alternatives are displayed as options in Fur-

ther Processing Entry.
Material short text Text with a maximum of 40 characters to describe the material.
The material short text is the name of the material.

Process Data – Softproviding Core Configuration Guide 108/112

Think ahead. Go there.

Field Names Description

Name Free input of a description of the plant/material/old/serial no.
combination.
Condition A replacement condition can be entered in this field (values from
the F4 help). This condition must be defined in advance in Cus-
tomizing. Together with the BAdI implementation, this condition
can be used to replace materials in accordance with customer-spe-
cific modifications (see “Enhancements (optional)”).

This condition must be met before a replacement variant can be

used in a production order. If this is the case, the replacement op-
tions stored in the table Component replacement are shown in the
application.

If the condition is not met, the replacement variants are not

shown in the replacement options.

The conditions are defined in Softproviding Core Customizing and

implemented as a BAdI (see “Enhancements (optional)”).

Note
Component replacement can also be used without conditions being de-
fined and the above-mentioned BAdIs being implemented. Inputting a
condition is therefore optional.
Valid from Date from which an entry is valid.
Valid until Date until which an entry is valid.

Item Data
Field Names Description
Material This is the replacement material that will take the place of the
material to be removed (see table Header data).
Material description Text up to 40 characters long that describes the material in more
detail. The material description is the name of the material.
Factor When making a replacement in the application (GUI or DGA), the
material to be removed is replaced by the material in its position
line and the ratio in which the quantity of material to be removed
is to be transferred to the replacement component is determined.

This transfer ratio is defined by this factor.

The factor can be any positive value. Negative values are not per-
mitted. A factor of 0 is permitted.

Examples
— Factor 0.9
— Factor 1.0
— Factor 1.25

Process Data – Softproviding Core Configuration Guide 109/112

Think ahead. Go there.

Field Names Description

Example
— Quantity of material to be replaced = 100 kg
— Factor 1.20
— Quantity for the replacement material = 120 kg

Result
Once all entries have been made, this can be saved by pressing the button Save. If all requirements
have been met, the function can be used in Further Processing Entry. The button Component replace-
ment is shown in the application for this purpose.

5.2 Control Settings for Period Batch

5.2.1 Overview
The period batch describes the functionality with which the system, independent of the production
order, can always assign the same batch number to an output material within the same period (e.g.
within the same day).

To activate this functionality, the Period batch indicator in the material master is set. In addition, in
the Period Batch Control master data table, the material is assigned, and the period batch type is de-
fined. No further settings in Customizing are required.

Use
Once activated, the Period Batch functionality is available in the following processes:
— Further processing Entry (outbound)
— Process Order (outbound)
— Disassembly Process Entry (outbound)

5.2.2 Settings
The Period Batch functionality can be used if, firstly, the indicator for the period batch was set in the
material master database and secondly an entry for the material was made in the master data table.

5.2.2.1 Material Master

In the application menu, the material master can be called as follows:

Process Data – Softproviding Core Configuration Guide 110/112

Think ahead. Go there.

Procedure
Menu Softproviding Meat Application Menu > Production > Master Data >
Material > Change
Transaction MM02

In the initial screen, enter the desired material number and confirm with Enter. In the Process Data
Acquisition tab, the Period batch field is available for selection.

Note
The tab names in the material master database (here the Process Data Acquisition tab) may be named
individually by the customer.

Goods Movements
Field Name Description
Period Batch Indicator specifying that for this material only one batch number
is created per period (day, week, month, year, or customer-spe-
cific). By default, this indicator is not set.

5.2.2.2 Master Data Table

The table can be called via the application menu as follows:

Procedure
Menu Softproviding Core Application Menu > Logistics > Process Data Ac-
quisition > Processing > Control Settings for Period Batch
Transaction /N/SPDGS/TDCH

The following fields are provided for the settings to be made

Field Name Description

Plant The plant is an organizational logistical unit that structures the com-
pany from the perspective of production, procurement, maintenance,
and materials planning. Materials are produced and goods and ser-
vices are provided in a plant. The plant is a company’s production site.
Material A material is an item that is the subject of a business transaction. In
SAP, materials such as raw materials, semi-finished products, operat-
ing supplies, and finished products are identified using a unique mate-
rial number.
Period Batch The following settings can be made for the period batch:
— Day
— Week
— Month

Process Data – Softproviding Core Configuration Guide 111/112

Think ahead. Go there.

Field Name Description

— Year
— Customer-specific

Note
The customer-specific period batch is implemented with BAdI /SPDGS/-
BADI_PDAO and method CUSTOM_PERIOD_FOR_DAILY_BATCH (cus-
tomer-specific period for period batch).

5.2.3 Executing the Program

If the indicator is set in the material master and there is an entry for the output material in the master
data table, the Period Batch functionality is activated, and batches are allocated according to the
specified batch period.

Batches are allocated automatically when quantities are entered in Disassembly Process outbound (=
goods receipt) and Further Processing outbound (= goods receipt).

If the functionality is active, the system will assign the same batch number to the output entered
within the same period (e.g. day or month). This is done independent of the production order, meaning
the same batch is allocated for multiple production orders (e.g. per day) producing the same material.

This may also be used in Disassembly if the same disassembly material is produced in different pro-
cesses – and, possibly, in multiple disassembly orders.

Note
Period batches are stored in Softproviding table /SPDGS/D_BATCH with the following information:
— Material
— Date on which the period batch was created
— Allocated period batch

Process Data – Softproviding Core Configuration Guide 112/112