FAQ: This section discusses the most asked question on the topic of Invoicing in SRM.
Frequently Asked Questions
Q. Can you cancel an invoice in the EBP system?
If the status is paid, you can not cancel an invoice. For more information please check OSS note 927824.
Q. Can you attach a URL link to invoice instead of a document ?
There is an OSS note that describes this. Please check OSS Note 434218 -3.0: Display configuration attachments/server configuration.
Q. What are some of the systems that can be used for tax calculation?
Following are some of the systems for tax calculation:
SAP R/3 system (tax calculation takes place in the financial accounting system)
If you already have an SAP R/3 financial accounting system, we recommend that you use the existing tax calculation provided by the R/3 system. You do not need to make any additional Customizing settings for tax calculation.
If you choose to calculate tax in the SAP R/3 system, tax calculation takes place in the respective financial accounting system (depending on the attribute of the user System Alias for Financial Accounting Systems in the organization model). The SAP R/3 system has to be defined as financial accounting system.
The system determines the tax code from the entries in the tables and fields, for example,from the product category, country of goods recipient, or the domestic/international indicator.
If the tax indicators in SAP Enterprise Buyer do not match the tax indicator in the financial accounting system, you can map them to the tax indicators of the financial accounting system.
The following table gives an overview of all settings you can make:
Settings in Enterprise Buyer for R/3 as the tax calculation system Setting Menu path in the Implementation Guide (IMG).
Maintain tax codes
Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Tax Calculation → Enter Tax Code
Map tax codes that have different names in the FI system and in SAP Enterprise Buyer to each other
Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Tax Calculation → Assign Enterprise Buyer Tax Code to FI System
use individual tax code determination.
Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Tax Calculation → Determine Tax Code
Change or supplement the data used to calculate tax depending on the system selected for tax calculation
Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Tax Calculation → Change Tax Data
Specify a tax code for country and product category (optional).
Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Tax Calculation → Determine Tax Code for Country/ Product Category
- External tax system (Vertex or Taxware)
If you do not have an SAP R/3 financial accounting system, you can use an external tax system, such as Vertex or Taxware (suitable for large customers only). This type of tax calculation is only valid for the USA and Canada.
If an external tax system is connected to the SAP R/3 system, it is called up automatically from the R/3 system.
- Customer-specific implementation (tax calculation in SAP Enterprise Buyer)
If you do not have an SAP R/3 financial accounting system, you can use a customer specific implementation for simple tax calculation (for example, if you only have two tax codes).
To Determine tax system for tax calculation go to below path :
Supplier Relationship Management → SRM Server → Cross-Application Basic settings → Tax calculation → Determine System for Tax calculation
Q. During posting of invoice in SRM, what method will be used for checking tolerance?
ECC tolerance will not be checked during SRM invoice posting.You need to maintain the same tolerances in both ECC and SRM as far as possible.
You can maintain tolerance in Supplier Relationship Management → SRM Server → Cross-Application Basic settings → Set Tolerance checks .
Q. How does one change the email format for IMS exceptions? Is there a BADI or a customizing table for this?
There is background job, BBP_IV_AUTO_COMPLETE, that runs regularly to repost invoices if a missing GR has been posted.
Q. Customer receives two types of invoices (which also have 2 different number ranges) - purchasing related invoices and pure FI invoices. Customer wants to be sure that the pure FI invoices will not trigger an exception based on missing previous document (PO / GR), etc.
SRM allows you to post non-PO invoices. For these invoices there won't be any PO or GR related exceptions.
Q. Why the initial value of contract number is blank and the contract item is 0000000000 ?
The data element are defined differently.The header contract number is CHAR 10 and initialize to blank, the contract item is NUMC 10 and initial value is 0...0. This is standard.
Q. What is saved in Price/Unit fields at item level?
Commonly the Unit is 1 so the Price/Unit is the price is per 1 unit. But in some cases the items with small prices (e.g. screws) is defined the price per XXX units: