SAP MM Invoice Verification : Handling unplanned delivery costs

Unplanned delivery costs are not known at the time of purchase order creation and hence these are not specified in the purchase order. These are only entered at the time of vendor invoice posting. These unplanned delivery costs can be either distributed to the individual items or to a separate G/L account.

Handling Unplanned Delivery Costs

SAP MM Physical Inventory Verification : Cycle Counting

Cycle counting is a method of physical inventory whereby inventory is counted at regular intervals within a fiscal year. Physical inventory may be required by financial accounting rules or tax regulations. Cycle counting process is less disruptive to operations. Cycle Counting allows you to count fast-moving items more frequently than slow-moving items.

Cycle counting process is fairly easy to implement. This process increase accuracy of inventory.

Cycle Counting Configurations and Flow

SAP MM Valuation and Account Determination : Offsetting Entry for Stock Posting (GBB)

Offsetting entry for stock posting (GBB) 

Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:

AUA: for order settlement
AUF: for goods receipts for orders (without account assignment)  and for order settlement if AUA is not maintained.
AUI: Subsequent adjustment of actual price from cost center directly to material (with account assignment)
BSA: for initial entry of stock balances
INV: for expenditure/income from inventory differences
VAX: for goods issues for sales orders without account assignment object (the account is not a cost element)
VAY: for goods issues for sales orders with account assignment object (account is a cost element)
VBO: for consumption from stock of material provided to vendor
VBR: for internal goods issues (for example, for cost center)
VKA: for sales order account assignment (for example, for individual purchase order)
VKP: for project account assignment (for example, for individual PO)
VNG: for scrapping/destruction
VQP: for sample withdrawals without account assignment
VQY: for sample withdrawals with account assignment
ZOB: for goods receipts without purchase orders (mvt type 501)
ZOF: for goods receipts without production orders (mvt types 521 and 531)

You can also define your own account groupings. Which for those with Z01 thru ZAX it appears are
custom for your company.

SAP MM Invoice Verification : Alternate Payee

There are 3 available options in SAP

-Alternative payee
-Alternative payee in document
-Permitted payee


Alternate Payee:

The Alternative payee field is available on the vendor master data screen on  two different screens: the general payment transaction screen and the company code specific  payment screen of the vendor. If an alternative payee is entered, all payments to a vendor are issued to the alternative payee. If the alternative payee is filled in both screens, general payment transaction and company code-specific payment transaction screen the company code-specific payee has priority.

Alternative Payee in Document: 

This option is similar to the one-time vendor invoice and  payment functionality in AP. Here, however, the user has the option to enter an alternate address  or bank information into the invoice, whereas for one-time vendors, this information must  always be filled in. To allow Alternative payee in document information to be entered, the Individual spec. box must be checked in the payment transaction screen of the vendor master
data. Once the Alternative payee in document information is allowed for a vendor, the Individual
payee check box is available during invoice entry on the Payment tab of the invoice. If you check
the Individual payee box, a new screen pops up that allows you to enter alternative address or bank information specific to this invoice.

Permitted Payee: 

This option allows the assignment of multiple permitted payees to the same  vendor. First, permitted payees need to be assigned in the vendor master data and then chosen during invoice entry. Permitted payees can be assigned in the general payment transaction screen in the vendor master data, and are therefore valid for all company codes. Once you click on the Permitted payee button, a second screen appears that allows multiple permitted payees to be assigned to the vendor. Once the Alternative payee in document information is allowed for a vendor, the Individual payee checkbox is available during invoice entry on the Payment tab of the invoice. The user must choose the correct payee address manually from the permitted payee list. Therefore, issuance of payments to the wrong payee address is avoided far more easily than with the alternative payee option.

Allowing Price change in Service Entry Sheet (ML81N)

In certain business cases user may have to change the Service Gross Price at the time of entering Service Entry Sheet. in standard scenario gross price field is not editable. Below document explains how it can be achieved with Configuration.

Configuration for Allowing Price Change in Service Entry Sheet

SAP ERS Error : “Table T169F: entry MRDC does not exist”

When Processing ERS (Evaluated Receipt Settlement) for Planned delivery cost settlement. i came across an  error “Table T169F: entry MRDC   does  not exist”.

Solution :

ERS Configuration Error “Table T169F: entry MRDC does not exist”

Automatically Populate “SGTXT” in MIGO

Recently our we had a requirement to automatically Flow the Material Text to Material Document Item Text (SGTEXT). Since there is no Standard Configuration available, MIGO User Exit "EXIT_SAPMM07M_001" (Enhancement MBCF0002) used.

Solution :

SAP MM : Automatically Populate SGTXT in MIGO