Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VA (Package) Application development R/3 Sales
Basic Data
| Data Element | RMA_REPKZ |
| Short Description | Repair proced:Confirmation from inspection lot/service order |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RMA_REPKZ | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | Confirmtn |
| Medium | 15 | Confirmation |
| Long | 20 | Confirmation |
| Heading | 5 | Conf. |
Documentation
Use
The results of the technical check are reported back to the repair order by an inspection lot or service order as codes. You assign each code to the relevant combination of stage and action. The system uses the code, in combination with the stage and the action, to determine which actions need to be taken to complete the goods repair process. Where possible, the system attempts to generate the appropriate sub-item for the action.
Example
The customer sends you a printer to be repaired. You create a repair order for the printer and post goods receipt for it. The system creates an inspection lot for the printer. A technician checks the printer and determines that it can be repaired. The results of the technical check are reported to the repair order as code "01" (repair).
The system accesses the following information from the repair procedure. For code "01", the action "101" (repair) needs to be taken at the stage "Start of repair process". It determines that the Manual processing required field is not activated so it creates a repair item automatically.
History
| Last changed by/on | SAP | 19990504 |
| SAP Release Created in |
