Ansicht
Dokumentation
/AIN/T_UE_RSN - Maintain Reasons for Unexpected Events (UE)
Fill RESBD Structure from EBP Component Structure TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
In this IMG activity, you maintain reason codes for unexpected events. These codes are required to provide predefined explanations for unforeseen occurrences that may arise during RFID processing. A printer jam during tag commissioning is an example of an unexpected event.
No reason codes for unexpected events are delivered with the standard system.
You must define at least one reason code for unexpected events. You categorize each reason code as belonging to one of two possible unexpected event (UE) types:
- Device group
- Action type
The steps to define an unexpected reason code are:
- Choose New Entries.
- Select the UE type (device group or action type).
- Assign a UE reason (a two-character user-defined alpha-numeric entry).
- Enter a UE Reason Description.
- Save the entry.
Below are some examples of possible unexpected reason code entries:
| UE Type | UE Reason | UE Reason Description | ||
| Device group | 01 | Device out of order | ||
| Device group | 02 | Printer jam | ||
| Device group | 03 | RF signal too weak | ||
| Action type | 01 | Case tag missing |
Vendor Master (General Section) ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 2709 Date: 20240424 Time: 132106 sap01-206 ( 25 ms )
