Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: WRF_AT - Messages for Allocation Table RTFASH
Message number: 160
Message text: There is no valid message type in Customizing for message WRF_AT 104
No valid message type (warning or error) has been maintained for the
message WRF_AT 104 in Customizing. However, this is required.
INCLUDE ISR_STOP
Contact the system administrator.
Message WRF_AT 104 is delivered with the message type 'Error'. You can
modify its message type in the Customizing activity "Properties of
System Messages" in allocation table environment.
Error message extract from SAP system. Copyright SAP SE.
WRF_AT160
- There is no valid message type in Customizing for message WRF_AT 104 ?SAP Error Message:
WRF_AT160 There is no valid message type in Customizing for message WRF_AT 104
Cause:
This error occurs because the system cannot find a valid message type configuration in the Customizing settings for the specified message (
WRF_AT 104
). In other words, the message type that the system is trying to use for output processing (such as printing, emailing, or IDoc generation) is not properly maintained or assigned in the SAP Customizing (SPRO).Typically, this happens in scenarios involving output determination for documents (e.g., sales orders, deliveries, billing documents) or workflow messages where the system expects a message type to be configured but none is found or the existing configuration is incomplete or invalid.
Solution:
Check Output Message Type Configuration:
- Go to SAP Customizing Implementation Guide (IMG):
SPRO -> Logistics Execution -> Shipping -> Basic Shipping Functions -> Output Control -> Message Types
- Verify that the message type
WRF_AT 104
(or the relevant message type related toWRF_AT
) is correctly defined.- Ensure that the message type is assigned to the correct application and output device.
Maintain Output Determination Procedure:
- Check the output determination procedure for the relevant application (e.g., sales order, delivery).
- Make sure the message type is included in the procedure and that condition records exist for triggering the message.
Check Partner Profiles (if IDoc related):
- If the message involves IDoc processing, verify the partner profiles in transaction
WE20
.- Ensure the message type is assigned to the correct partner and that the outbound parameters are maintained.
Verify Workflow or Custom Messages:
- If this message is related to a workflow or custom development, check the message type assignment in the workflow customizing or the custom code.
- Make sure the message type exists and is active.
Recreate or Adjust Message Type:
- If the message type is missing, create it according to the business requirements.
- If it exists but is invalid, correct the settings or delete and recreate it.
Related Information:
Transaction Codes:
SPRO
— Customizing Implementation GuideNACE
— Output Types (for sales and distribution output)WE20
— Partner Profiles (for IDoc)WE21
— Port Definition (for IDoc)SM58
— Transaction log (to check for errors in asynchronous processing)SWU3
— Workflow Customizing CheckNotes and Documentation:
Common Scenarios:
The error WRF_AT160
indicates a missing or invalid message type configuration in SAP Customizing for the message WRF_AT 104
. To resolve it, verify and maintain the message type in the output determination settings, partner profiles, or workflow customizing as applicable to your scenario.
Get instant SAP help. Sign up for our Free Essentials Plan.
WRF_AT159
The recipient referenced in purchase order &3, item &4 no longer exists
What causes this issue? The recipient referenced in purchase order &V3&, item &V4&, no longer exists in allocation table &V1&...
WRF_AT158
Synchronization with allocation table &1, item &2 is not possible
What causes this issue? The subitem for item &V4& in purchase order &V3& does not have a reference to an allocation table.System Resp...
WRF_AT161
Error while reading the Cusomizing table T160AT
What causes this issue? An error occurred while reading the message type in Customizing table T160AT.System Response INCLUDE ISR_STOPHow to fix this...
WRF_AT164
New DC delivery date not synchronized with allocation table &1, item &2
What causes this issue? Follow-on documents already exist for allocation table &V1& for recipients. Follow-on documents exist when there are ...
Click on this link to search all SAP messages.