Hierarchy

⤷

⤷

Basic Data
Data Element | COWB_SCRAP_TYPE_TEXT |
Short Description | Short Text for Scrap Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DDTEXT | |
Data Type | CHAR | Character String |
Length | 60 | |
Decimal Places | 0 | |
Output Length | 60 | |
Value Table |
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 | Scrap Type |
Medium | 15 | Scrap Type |
Long | 20 | Scrap Type |
Heading | 55 | Scrap Type |
Documentation
Definition
Defines the type of scrap confirmation the system is to post in the confirmation process.
Use
The following options are available:
- Post scrap at reporting point
If you choose this setting, the system determines the components for the specified reporting point only and posts the backflush of these components as well as the scrap confirmation. The scrap is posted for the assembly for which the confirmation is entered. You can only enter a confirmation for the current reporting point.
You use this form of scrap confirmation for the mandatory reporting point confirmation.
In the case of the optional reporting point confirmation, this form of scrap posting makes sense if you have already posted good quantities (yields) for previous operations and the scrap is to relate only to the operation for which a confirmation is currently being entered.
- Post scrap up to reporting point
If you choose this setting, the system posts the scrap confirmation and also retroactively posts the good quantities (yields) for all previous reporting points. You must have defined optional reporting point confirmation for this form of scrap posting.
In the caes of an optional reporting point confirmation, a confirmation is usually only entered if scrap has actually been incurred at a reporting point. In this case, the system determines the components for the reporting point and all previous reporting points and posts both the backflush and the scrap costs incurred.
- Excess component consumption
If you choose this setting, the system posts the scrap quantity entered not as scrap but as excess component consumption. At the time of posting, the system uses a goods issue movement type. In addition, the production activities necessary for the assembly of the components are posted.
You must choose this setting if components needed for the assembly were damaged during the current workstep.
Example:
During the manufacture of PCs, the hard disk is damaged during the assembly process. The hard disk is posted as excess consumption. In addition, the production activities for the installation of the hard disk are posted.
Dependencies
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 700 |