How To Fix WRF_AT139 - AUREL change not permitted, because PO split for alloc. table item (FBG)

WRF_AT139 - Overview

• Message type: E = Error

• Message class: WRF_AT - Messages for Allocation Table RTFASH

• Message number: 139

• Message text: AUREL change not permitted, because PO split for alloc. table item (FBG)

What causes this issue?

Several (Fashion) purchase orders were created as follow-on documents
for the allocation table &V1&, item &V2&, including the purchase order
&V3&, item &V4&. When you change the allocation-table-relevant indicator
in this purchase order, the allocation-table-relevant indicator was also
changed in the referencing allocation table date during synchronization,
but not in the other relevant purchase orders. This may lead to
inconsistent data.

System Response

The system does not process the allocation-table-relevant change to the
purchase order.

How to fix this error?

Change the allocation-table-relevant indicator in this purchase order.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WRF_AT139 - AUREL change not permitted, because PO split for alloc. table item (FBG) ?

  Certainly! Here's a detailed explanation regarding the SAP error message:
  
  SAP Error Message:
  WRF_AT139 AUREL change not permitted, because PO split for alloc. table item (FBG)
  
  
  Cause:
  This error occurs when you attempt to change the AUREL field (which typically relates to the release indicator or release status in purchasing documents) in a Purchase Order (PO) item that has already been split for allocation purposes in the system.
  
  The system uses allocation tables (FBG) to manage the distribution of costs or quantities across different account assignment objects.
  When a PO item is split for allocation, certain fields become locked or protected to maintain consistency and integrity of the allocation data.
  Changing the AUREL field (release status) is not allowed because it could invalidate the allocation splits or cause inconsistencies in the release strategy or workflow.
  
  
  
  Solution:
  
  
  Check Allocation Splits:
  
  Review the PO item to see if it has been split for allocation (e.g., cost center, order, project).
  Use transaction codes like