Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
CORU (Package) R/3 Application development: PP Confirmations
Basic Data
| Data Element | CO_PRZST |
| Short Description | Control confirmation process |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CO_PRZST | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | TPRRU |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Control |
| Medium | 15 | Process control |
| Long | 20 | Process control |
| Heading | 4 | Ctrl |
Documentation
Definition
Controls the execution of the confirmation process.
Use
You use this key to define when each individual process that is automatically triggered by a confirmation is executed:
- Online
- In an update
- In the background
If no key is selected, the processes are executed online.
You can influence the following confirmation processes:
- Automatic goods receipt (only production orders)
- Backflushing
- Calculation of actual costs
You can define the process control key in the transaction OPKC:
Execute function
Dependencies
If processes are to be executed in the background, this can be carried out as follows:
- With the function Confirmation -> Predefined processes in the Shop Floor Control menu:
Execute function
- By scheduling the program CORUPROC in a background job:
Execute function
Supplementary Documentation - CO_PRZST 0001
Use
You can use this key to specify whether goods issues of components are to be decoupled and/or production activities are to be posted in aggregate.
You can also specify when these processes are to be carried out:
- at once online
- at once in update (processing is transferred to the update task and so the user can continue working online)
- later as background job
Procedure
You define the key in Customizing for repetitive manufacturing under Define confirmation processes and assign it to a repetitive manufacturing profile, if necessary.
Examples
Dependencies
Supplementary Documentation - CO_PRZST 0002
Use
Use this indicator to determine which processes are separated from the goods receipt posting or the reporting point backflush. Possible processes are:
- Posting the goods issue of the components
- The activity posting
You can also aggregate individual postings together when you later carry out the separated processes.
When you carry out these processes, you have the following options:
- Execute online
- Execute as a update task
- Execute in the background
You can define the process control key in the OPKC Customizing transaction.
Execute function
Dependencies
Aggregation is only possible for the combination of goods issue posting and activity posting. You cannot aggregate just one of these processes.
Example
History
| Last changed by/on | SAP | 19981210 |
| SAP Release Created in |
