Ansicht
Dokumentation

PSM_MM_MAA: Setting the Final Account Assignment Indicator in Purchase Orders (New) ( RELNPSM_605_MAAFINALAA_1 )

PSM_MM_MAA: Setting the Final Account Assignment Indicator in Purchase Orders (New) ( RELNPSM_605_MAAFINALAA_1 )

Vendor Master (General Section)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

PSM_MM_MAA: Setting the Final Account Assignment Indicator in Purchase Orders (New)

Use

As of SAP enhancement Package 5 for SAP ERP 6.0 (SAP_APPL 605), business function PSM, Multiple Account Assignment - Final Account Assignment Indicator (PSM_MM_MAA), you can set the final account assignment indicator for individual account assignment items in purchase orders with multiple account assignments. This function allows you to prevent further quantity postings to the account assignment items in question and - assuming encumbrance tracking takes place for the assignment - to reduce the open commitment value accordingly.

You can set the final account assignment indicator in manually created purchase order items with multiple account assignments for which you have already created follow-on documents. If you want to set the FAA indicator for account assignment items, you need to have specified valuated goods receipt for the purchase order item or you need to have excluded goods receipts in general. You can only set the FAA indicator in purchase order items without a goods receipt if you have not created an invoicing plan and if you have specified during invoice entry that the account assignments cannot be changed. If you have specified valuated goods receipt, you can only use account assignment objects in the purchase order item that are assigned to the company code in which you enter the purchase order. In this case, cross-company code processing of purchase orders is not possible.

If you want to set the final account assignment indicator in service items, you must first have activated service-based invoice verification. In unplanned service lines (up to a limit), the final account assignment indicator is simply for information purposes. You cannot set a final account assignment indicator in returns items.

When you set the final account assignment indicator, the system determines from the purchase order history the quantity that has already been posted to this account assignment item. The system compares the delivered and invoiced quantities and sets the higher of the two as the final account assignment quantity. In the case of distribution by amount, the final account assignment quantity is calculated and stored to the floating point. You have the following options for balancing out the difference between the account assignment quantity that was originally stored in the purchase order, and the final account assignment quantity:

  • You can reduce the quantity at purchase order item level by the difference in quantities.
  • You can specify in a new Business Add-In (BAdI) how the system should distribute the quantity difference across the remaining open account assignment items.
  • You can distribute the quantity difference manually across the remaining open account assignment items.
  • You can add new account assignment items and post the quantity difference to these items.

If you chose percentage distribution in the purchase order, and then set the final account assignment indicator, the system changes the distribution logic from percentage distribution to distribution by quantity, as this is the only way to avoid rounding errors when the quantity difference is distributed. We therefore recommend that you do not choose percentage distribution if you want to work with the final account assignment indicator in your procurement process.

In Customizing for Materials Management, you can create different final account assignment reasons with texts and in this way save in the purchase order a reason for having set the final account assignment indicator for an account assignment item.

If you deselect the final account assignment indicator for an account assignment item, the existing quantity distribution remains unchanged. When distributing amounts relating to future goods receipts and invoice receipts, the system again takes into account the account assignment item that previously had a final account assignment indicator.

Effects on Existing Data

In transactions ME22N (Change Purchase Order) and ME23N (Display Purchase Order) there are the following new table fields in the item details on the Account Assignment tab.
The fields are at account assignment item level:

  • Final AA Indicator (Check box final account assignment indicator: AA_FINAL_IND)
  • Final Quantity (Final account assignment quantity: AA_FINAL_IND)
  • Final Reason (Final account assignment reason: AA_FINAL_REASON)
  • Reason Text (Text for final account assignment reason: AA_FINAL_REASON_TXT)

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

You create final account assignment reasons in Customizing for Materials Management under Purchasing -→ Purchase Order -→ Specify Final Account Assignment Reasons.

With the BAdI ME_MAA_ADJUST, you can define your own logic with which the system distributes the difference in quantity after the final account assignment indicator has been set. Implement the BAdI in Customizing for Materials Management, under Purchasing -→ Business Add-Ins for Purchasing -→ BAdI: Adjusting MAA Distribution after Final Account Assignment.

If you are not expecting a goods receipt for the purchase order item and you want to set the FAA indicator for account assignment items, you have to lock the account assignments against changes during invoice entry. You do this in Customizing for Materials Management under Purchasing ->Account Assignment -> Maintain Account Assignment Categories.

Further Information






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 6771 Date: 20240523 Time: 064214     sap01-206 ( 148 ms )