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: 118
Message text: System error; allocation-table-relevant indicator set to "Not Relevant"
You want to set the allocation table relevancy indicator to 'Not
Relevant for Allocation Table'. However, this is not permitted.
The purchase order processing only transfers those changes to the
allocation table relevancy indicator that do not equal 'Not Relevant for
Allocation Table' to the synchronization module (synchronization with
the allocation table). However, this does not apply in this case (order
&V1&, item &V2&).
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The system does not accept the change.
Change the allocation-table-relevant indicator to a permitted value.
Error message extract from SAP system. Copyright SAP SE.
WRF_AT118
- System error; allocation-table-relevant indicator set to "Not Relevant" ?SAP Error Message:
WRF_AT118 – System error; allocation-table-relevant indicator set to "Not Relevant"
Cause
This error occurs when the system tries to process a transaction or operation that requires the allocation table to be relevant, but the allocation-table-relevant indicator is set to "Not Relevant" (usually 'N'). In SAP, allocation tables are used in various modules (e.g., Controlling, Asset Accounting) to allocate costs or values based on predefined rules.
The root cause is typically one of the following:
Check Allocation Table Relevance Indicator:
Review Configuration:
Check Master Data:
Debugging / Logs:
Consult SAP Notes:
OKKN
– Maintain Settlement RulesKSH1
/ KSH2
– Allocation Table MaintenanceAS02
– Change Asset Master (check settlement parameters)Aspect | Details |
---|---|
Error Message | WRF_AT118: System error; allocation-table-relevant indicator set to "Not Relevant" |
Cause | Allocation table relevance indicator incorrectly set to "Not Relevant" when process expects "Relevant" |
Solution | Correct the allocation-table-relevant indicator in customizing/master data to "Relevant" |
Check | Allocation table configuration, master data, settlement rules, and related customizing |
Tools | ST22, SM21, Debugger, SAP Notes |
If you provide the exact transaction or process where this error occurs, I can help you with more specific steps.
Get instant SAP help. Sign up for our Free Essentials Plan.
WRF_AT117
Order unit is different from stock transfer unit
What causes this issue? In cross-docking, the order unit &V3& must be the same as the allocation stock transfer unit &V4&. This is no...
WRF_AT116
Bundeling of multiple alloc. table items for synchronization not allowed
What causes this issue? Bundeling of multiple allocation table items is not supported for the synchronization of purchase order and allocation table ...
WRF_AT119
Following exceptions during incompleteness check of alloc.tab. &1,itm &2:
What causes this issue? The exceptions listed below were raised during the incompleteness check for allocation table &V1&, item &V2&....
WRF_AT120
--- Messages for customer BAdI for allocation table &1, item &2:
What causes this issue? The subsequent messages were created within the customer BAdI for allocation table &V1&, item &V2&; not withi...
Click on this link to search all SAP messages.