Question: Exchange Rate at point of billing integration from SD to FI-AR, different from the Sales Order Exchange Rate creation time? Is there something like in PO Header - a "Fixed Exchange Rate" indicator to locked in the Exchange Rate at the SD Sales Order.
.jpg)
Answer: The case is that the SD Billing correctly retrieve the Exchange Rate from the Sales Order Header BUT when posting the FI and FI-AR uses another Exchange Rate, and WHY ?
Cause: In SAP, this currency mismatch happens because SD billing documents and FI accounting documents can determine their exchange rates at different times or from different sources based on your system configuration.
SAP SD billing uses different fields for pricing determination (VBRP-KURSK) versus FI financial postings (VBRK-KURRF). By default, if an accounting exchange rate isn't manually fixed in the sales order header, SAP re-fetches the FI posting rate from table OB08 based on the billing or posting date, causing a discrepancy.
.jpg)
Solution 1: At the Sales Order Header - Accounting Tab, set the Exchange Rate same as the Exchange Rate in the Sales Tab.
.jpg)
Solution 1: At the Sales Order Header - Accounting Tab, set the Exchange Rate same as the Exchange Rate in the Sales Tab.
Caution: There could be other configuration in the FI customizing SPRO which require checking if the above recommendation was not able to address the issue.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: An External Services PO (eg: Account Assignment K and Item Category "D", the Service Master is 1 AU $1000. (AU is UOM for Activity Unit)
SES in full of 1 AU $1000
Invoice in full at $1000
Then perform Subsequent Credit of $100 with the following results:
.jpg)
.jpg)
Answer: Note the following FI entries at different stages of the above scenario:
at SES Approval: Debit Purchasing Expenses $1000
Credit SR/IR $10000
at Invoice Entry: Debit SR/IR $1000
Credit Vendor $1000
Subsequent Credit: Debit Vendor $1000
Credit Purchasing Expenses $100
The above Financial Posting SHOULD BE acceptable in Accounting Principles.
Situation: User required the Delivered to be reversed to $900 as well so that it is EQUAL to the Invoiced amount of $900.
Analysis: since the Qty of the Services is 1 "AU" at $1000/1AU, REVERSAL of the SES is not possible with 1 "AU" case. However, even if it is possible; the FI entries will be
Debit SR/IR $100
Credit Purchasing Expenses $100
This would result in Double Credit of $100 to the Purchasing Expenses Account ie: 1 time at the Subsequent Credit step and this time at the Reversal step!
Reasoning: The Reason why there is a USER REQUEST to make the Delivered amount $1000 to be EQUAL to the Invoice amount $1000 despite a Subsequent Credit is that such a Discrepancy in that is the $100 genuinely still waiting for another Supplier Invoice or is it via a Subsequent Credit entry. This is especially difficult to troubleshoot when there are many lines of SES, Invoice, and Subsequent Credit.
Suggested Solution: Whenever a Subsequent Credit is entered, the User is required to "WRITE" a NOTE both in the Subsequent Credit Document as well as the related PO Header Text Type to indicator the Subsequent Credit Document number and the Amount. This is to allow Users AUDITING the PO Header of a different Delivered and Invoice Amounts for verification of reference to which Subsequent Credit that causes the DISCREPENCY.
Implementation consideration:
- To force a user to enter a note (header text/notes tab) in SAP transaction MIRO, standard configuration is not enough because the header note field cannot be set to mandatory via screen variants (SHD0) or field status. You must implement an ABAP validation using BAdI MRM_HEADER_CHECK or user exit LMR1M001.
- Another User Exit can be implemented to write the Subsequent Credit document to the PO Header.
- If the above cannot be implemented, then MANUAL Entry will be necessary.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: How to set a Pricing Condition type to be Statistical in SD?
Answer: Use the following menu path to set a condition type to be Statistical in the selected Pricing Procedure:
IMG > Sales & Distribution > Basic Functions > Pricing > Pricing Control > Define and Assign Pricing Procedure - Set Pricing Procedure
Note: Setting a condition type to statistical in an SD pricing procedure ensures its calculated value displays on the sales order or invoice for informational or reporting purposes only, meaning it does not alter the net value, total final price, or trigger financial postings to general ledger accounts.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Release Strategy for Service Entry Sheet.
Answer: In SAP MM (Materials Management), the Service Entry Sheet (SES) Release Strategy is an approval procedure used to verify and accept service entry sheets (transaction ML81N / ML85) before they allow invoice verification and financial postings. Similar to Purchase Orders, SES release strategies use the classification technique based on communication structure CESSR (specifically fields like net value LWERT).
Configuration references MM Release Strategy:
- IMG > Material Management > External Service Management > Define Release Strategy for SES
- IMG > Material Management > Purchasing > Purchase Requisition > Release Procedure > Procedure for Classification
- IMG > Material Management > Purchasing > Purchase Order > Release Procedures for Purchase Orders
- IMG > Material Management > Purchasing > Contracts > Release Procedures for Contracts
- IMG > Material Management > Purchasing > RFQ and Quotation (SAP ERP) > Release Procedure for RFQs
Standard Workflow for SES:
- the standard flexible workflow template for a Service Entry Sheet (SES) is workflow scenario WS00800321 (tied to standard release task TS00800593).
Authorization Object for SES:
- Authorization Object M_EINK_FRG
Click here to view the Presentation
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.