Mass Processing for Control Cycles
In the transaction for control cycle maintenance (PKMC), in addition to individual processing you can carry out the mass processing of a whole group of control cycles. Key basis functions that are familiar to you from individual processing of the control cycles can also be used in mass maintenance - for example, the creation, copying, deletion, printing, control cycles, or the changing of control cycle category or replenishment strategy.
With the aid of the editable ALV grid, you can carry out an Excel download of the data of a group of control cycles, adjust the data, and retransfer the changes back to the SAP system using the
Copy and Insert
function in the transaction PKMC, for example.
As soon as you invoke the transaction for control cycle maintenance in change mode, the pushbuttons for mass processing appear in the toolbar above the ALV grid. They provide you with the following mass-processing functions:
Create Control Cycles
You can create a predefined number of control cycles with and without a template. If you choose this function, a dialog box opens in which you specify the control cycle category, the lifecycle status (provided that you have activated this function in Customizing), and – optionally – the target destination, consisting of plant and production supply area (PSA). The newly created control cycles are listed at the end of the ALV. They can be completed with regard to the key and the dependent parameters and checked for consistency. Note that the control cycles are not actually created until they are saved to the database.
Change Control Cycles
In change mode of mass processing you can change and adjust all fields that will accept input.
Once you have pressed the Enter key, the system starts an automatic consistency check. You get the result of this consistency check in a message log.l A status traffic light informs you whether the changed data is consistent (possibly taking the lifecycle status into account) and can be saved (yellow light) or requires further correction (red light).
Copy Control Cycles
You have the option of using one or more existing control cycles as templates and copying them. In the first case, you can make several copies of a reference control cycle. The material number is not adopted during this process. In the second case, you can make a single copy of a series of control cycles. Here the material number is inherited. In this way, you can copy the control cycle data of a group of materials from one plant or PSA to another plant or PSA, for example.
As in the case of the mass creation of control cycles, you define the control cycle category, where appropriate the lifecycle status, and optionally a target destination (plant and PSA) for the newly copied control cycles in a dialog box. Except for the key fields Material, Plant, and PSA, all other dependent control cycle data is otherwise adopted as it is from the template.
If the key parameters are clearly defined, the system immediately carries out an automatic consistency check for the new control cycles and shows the result in the message log.
Delete Control Cycles
This function enables you to delete multiple control cycles that you do not wish to use for production any more. Deletion is possible only if all the relevant kanban containers have the status
Locked. A message log informs you accordingly if control cycles cannot be deleted. Note that the physical deletion of the control cycles does not take place until you save.
Change Control Cycle Category
You can change the category of several control cycles at the same. After the new category has been entered, the control cycles are adjusted. The system deletes any parameter values that are incompatible with the new category. In addition, a consistency check is performed on the changed control cycles following the adjustment.
Change Replenishment Strategy
This function enables you to adjust the replenishment strategy of several control cycles. In the process, as with individual processing, the parameters linked to the replenishment strategy are deleted and can be re-entered.
Select a desired number of control cycles at the same time to have their documents (e.g. kanban cards) printed out together. A message log informs you about any problems that may have occurred during printing.
Manual Consistency Check
This function enables you to check the consistency of all or a selection of control cycles at any time. In addition to the results regarding inconsistencies following the automatic check, the message log records errors in control cycles with the status
In Creationthat you must correct prior to a status change.
For more information, see Consistency Check for Mass Processing .
Jump to Detailed Processing of Control Cycles
Even if the mass processing indicator is set, you can jump to detailed processing with a fully specified key and exit this mode again even if the control cycle still manifests inconsistencies. If you exit the detailed view, the consistency is checked and the status traffic light adjusted accordingly. If an error occurs, an warning message is issued in the case of control cycles with the status
Released. You must acknowledge this message before you can exit the detail screen. The detail view also enables you to jump to the change documents for the control cycle.
Save Control Cycles
As in individual processing, the changed or newly created control cycles are not written persistently to the database until you save. You can save all control cycles that have a yellow traffic light and whose lifecycle statuses are thus consistent. Control cycles with red traffic lights manifest inconsistencies and cannot be written to the database when you save, but must first be corrected. When you save, a message is issued informing you of the number of newly created, changed, or deleted control cycles.
The mass processing function is completely integrated in the transaction for control cycle maintenance. It is activated if you set the indicator for mass processing on the single or extended selection screen.
In Customizing, the Customizing activity
Changing of Fields and Their Readiness to Accept Input
is available under
. This BAdI enables you to process the content and properties of customer-specific additional fields of the customer include in the table for the control cycle (PKHD). It enables you to populate these customer-specific fields or define their readiness to accept input depending on the control cycle category, for example.
Was this page helpful to you?
Do you have any additional feedback?If you want us to get back to you, please enter your email address.
The following content is not part of SAP product documentation. For more information, see the following disclaimer .