You are on page 1of 44

1.

ERP Manufacturing (PP)

2.

3.

Process Management

Configuration of Customizing

Skip to end of metadata


Created by Rachel Tang, last modified about 19 hours ago
Go to start of metadata

Purpose
Configure and explain the customizing of process management.

Overview
Customizing of control recipe, digital signature, process instruction and process message will be mainly discussed here.
All the customizing can be found under:
SPRO -> SAP Customizing Implementation Guide -> Production Planning for Process Industries -> Process Management

Purpose

Overview

<Control recipe>

Control recipe destination

Control recipe status

Related Transaction code

Related Table

<Process Instruction>

Process Instruction category

Related transactions:

<Process Message>

Process message category

Process message destination

Mandatory Characteristics:

Related transactions:

<Digital Signature>

Customizing Path

Authorization Group

Individual Signature

Signature Strategy

Digital Signature Log

Related Content

Related Documents

Related SAP Notes/KBAs

<Control recipe>
Control recipe destination

Transaction Code O10C. Customizing is plant specific.

Overview

Process instruction assignment: Only possible for control recipe destination type 2 and 3.Process instructions to be generated: Defines the automatically generated process instructions f
or cert
be generated when the
control

recipe is generated.SortMat: Defines how the process in

Detail

Dest.Type: Control Recipe Destination Types. Only FOUR types are provided by SAP standard.

Destination type 1: ABAP list-based PI sheet will be created when control recipe is gener
d. Destination type 2&3: Control recipe will be sent to external system for further process. Desctination type 4: Browser-based PI sheet will be c
eated when control recipe is generated. - This is the most common destination type which is used.Simple Password Check: Only possible for de
tination type 1. You only need to entry your user but no need to use pas
ital signature: Strategy is defined in digital signature customizing.
finication in process instruction, it will check the definition here.

For deviations, the signature can be defined in process instruc


Process step is one logically unit of work in the PI sheet. T

al signature means
the steps between two digital signatures are wihtin

one process step.Logging in PI Sheet: If the action

All the changes that are done here can only work when a new control recipe is created.

Control recipe status


SAP On-line dcumentation:
Control Recipe Status
New control recipe(PI Sheet) can be discarded. In Process control recipe can be canceled.

Related Transaction code


CO53: Control Recipe Monitor
OPKP: If the control recipe/instructions can be generated automatically during order release.
Command CTKT within COR2: Generate control recipe for test within order process. (Test control recipe can only be generated when order is with status CRTD)
Command CTLL within COR2/COR3: Send control recipe within order process.

Related Table
COCH

Process Management: Control Recipe Header

COCHP

PI sheet: Control Recipe Header

<Process Instruction>
Process Instruction category

ey are

Transaction code O12C: Customizing is plant specific.


Process instruction category is a set of predefined characteristics which is used to constitute an integral part of PI Sheet.

Overview

PI assistant: It is used to construct, test and simulate the process instruction category, the characteristics within the process instruction can also be changed here. This can not be
used for
process instruction type 0.

Detail

Process Instruction Type:

For type 0 you can define the process instructions/characteristics as you like but for the others you need to define it accoring to the types.

Related transactions:
Transaction code O20C: Copy process management settings between plants.
Transaction code O21C: Where-used list of characteristics in process management.
Transaction code O23C: Client Copy of PP-PI Characteristics.

<Process Message>
Process message category
Transaction code O13C: Customizing is plant specific.
Process message send the information from PI sheet to actual receivers for further processing.

Overview

Characteristics

You can make certain characteristics as mantory in the process instruction here by ticking on the "Req" indicator for that characteristic.

Destinations

Target fields: They are defined in the destination and mapped here with characteristics.

Process message destination


Transaction code O03C

Destination types:

Type 01 and 04 are most common used ones, they are sending data to ERP Function module and ERP database table to make further process of the process orders.

Define target fields: Field in a process message destination to which the system transfers the value of a message characteristic.

Whether you can or have to define target fields for a destination, depends on the destination type:

Type 1: External function - no target fields

Type 2: SAPoffice user - no target fields

Type 3: ABAP/4 table - target fields required, otherwise no message data can be transferred

Type 4: SAP function module - whether target fields are required depends on the definition of the function module.

Type 5: Alert category - target fields are required if text variables are used in the alert text
You later assign the message characteristics to the target fields in the message category in O13C.

Mandatory Characteristics:
Transaction code OPMC: If you want to make certain characteristic as mandatory when it is not included in any process messages.

The enhancement POC_MANDATORY_INPUT should be activated and:

With these steps, you can make a characteristic which is not contained in any process messages as mandatory/required in process instructions and PI Sheet. If the characteristic is
contained in the process message, then the process message setting has a higher priority, means even you have set the characteristic as mandatory with this method, the characteristic
will be considered as not mandatory because the control in process message set it as not mandatory.

Related transactions:
CO54: Process message monitor.
Transaction code O22C: Copy standard settings of SAP Messages to target plant.

<Digital Signature>
Customizing Path
SPRO -> Production -> Shop Floor Control -> Integration -> Process Integration -> Control Instructions/Work Instructions -> Digital Signatures
SPRO -> Production Planning for Process Industries -> Process Management -> Control Recipes / PI Sheets -> Digital Signatures

Authorization Group
Transaction code ELSIG01

Authorization groups are defined here, they are normally different task areas or roles for one Line of Business. In the user master record, you give each user authorization for the
authorization group corresponding to his or her task area with authorization object C_SIGN_BGR to make it actually work for the user.

Individual Signature
Transaction code ELSIG02

Individual Signatures are defined here, they are assigned to different authorization groups and will be used in signature strategy to stand for one real signature.

Signature Strategy
Transaction code ELSIG00

Signatue strategy is defined here, some settings need to be done like if the comment and remark need to be displayed and what is the signature method. Then the individual signatures
need to be assigned here in

Three indivdual signatures are assigned here means if you use this signature strategy, there will be maximum three signature need to be done to finish the signature process. Then the
sequence of sign need to be specified in

for each individual signature

You may also press the

button in the initial screen to define the sequence

Here the sequence is ZTR_01 is the first person need to sign, ZTR_03 can only sign after ZTR_01 has signed, ZTR_05 can only sign after both ZTR_01 and ZTR_03 have signed.

Then the release status can be maintained in

The release status defines how many signatures need to be signed to complete the whole signature, the details of each release status is defined in

You may also press the

button to define the release status details

This defination means only all the three signature are signed, the whole signature can be completed.
So with the above customizing, you will have the following behavior with the signature strategy:
1.

You have user A, B, C assigned with user group ZTR01, user C, D, E assigned with user group ZTR02, user F, G assigned with user group ZTR03.

2.

You use signature strategy ZTR001 in your PI Sheet to do signature.

3.

When a signature process is triggered, one of user A, B, C can sign it first (they are considered as individual signature ZTR_01), then one of user C, D, E can sign it next (they
are considered as individual signature ZTR_02), finally one of user F, G can sign it at last to complete the whole signature process (they are considered as individual signature ZTR_03).

Digital Signature Log


Transaction code DSAL

Related Content
Related Documents
Insert SAP Help links or other WIKI content link.
Please hyperlink the title of the related document
Example: Explanation about how to create a WIKI page

Related SAP Notes/KBAs


Insert links to any related SAP Notes/KBAs that support your topic or are related. Please hyperlink ONLY SAP Note or KBA number.
Example:
SAP Note 83020: What is consulting, what is support
SAP KBA 12345: This is an example KBA link
(Use the following Hyperlink with SAP Note/KBA number at end: https://service.sap.com/sap/support/notes/123456)
__________________________________________________________________________________________________________
Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.;