headershadow

Middleware Monitoring in SAP CRM: BUPA_MAIN error analysis -5

Print Friendly

Relevancy:
BDOC Type: BUPA_MAIN
Error message: Tax number category XXX does not exist

Cause:
Some Tax number categories are not available in the CRM system compared to the R/3 system.

Dependant on the country of the customer, some Tax relevant fields may be entered in R/3.

Make sure someone from the tax department or master data manager validates if the Tax relevant master data is entered in the correct field AND in the correct format!!
In the example above the customer 120444 is a Chinese customer (so not an EU country). In this case the field VAT reg. No. is misused!!! So do not blindly add new tax number categories in the CRM system.

VAT registration number

VAT registration number (VAT reg.no.) of the customer, vendor or your company code.

Use

The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed.

Tax number 1

Specifies the tax number.

Use

Enter the appropriate tax number:

Country Tax Number
Argentina CUIT number or CUIL number
Belgium Enterprise number
Brazil CNPJ number
Bulgaria Unified identification code
Chile RUT number
China VAT registration number (shui wu deng ji hao)
Colombia NIT number
Croatia Legal persons: company identification number
Natural persons: JMBG number
Czech Republic DIC number
France SIRET number
Greece Personal ID
Hungary Tax number
Italy Tax number
Mexico RFC number
Peru RUC number
Philippines Taxpayer identification number (see below)
Poland NIP number
Portugal NIF number
Romania Tax number
Russia INN
Slovakia DIC number
Slovenia Tax number
South Korea Natural persons: Personal identification number
Legal persons: Corporation ID
Spain NIF number
Taiwan GUI registration number
Thailand Personal ID
Turkey Name of business partner's tax office
Ukraine Taxpayer identification number
United States Social security number
Venezuela RIF number

 

Dependencies

In the Philippines, enter the taxpayer identification number with a V or N at the end, as follows:

  • If the business partner is liable to VAT: 999-999-999-999V
  • If the business partner is not liable to VAT: 999-999-999-999N

Tax number 2

Specifies the tax number.

Use

Enter the appropriate tax number:

Country Tax Number
Argentina NIP number or CM number
Belgium VAT number
Brazil CPF number
Bulgaria Legal persons: tax number
Natural persons: personal number
Czech Republic ICO number
France SIREN number
Greece AFM number
Russia OKPO number
Slovakia ICO number
South Korea VAT registration number
Sweden Organization registration number
Switzerland VAT registration number
Taiwan Tax registration number
Thailand Tax ID
Ukraine Legal persons: USREOU number
Natural persons: SRNP number
Turkey Tax number
United Kingdom NI number
United States Employer identification number
Venezuela NIT number

Procedure:
After verification that the master data (tax relevant fields) were correctly filled out (format) and also the correct fields were used (depending on the country of the business partner) you might need to add a new tax number category in the CRM System.

You need to update the relevant Table Views in CRM:
- V_TFKTAXNUMTYPE
- V_TFKTAXNUMTYPEC

Use Transaction SM30 to make the following new entry in view V_TFKTAXNUMTYPE:
e.g.

Then use the same transaction to maintain a new entry for this new tax number category 'BE0' in view V_TFKTAXNUMTYPEC.

Remark:
You need to change this customizing view in your CRM Development system. After adding the entries via SM30 in both tables you will get a Transport Request, which you need to transport via your Quality Assurance system into your Production system. When the changes are available in your Productive system, you can reprocess the Bdocs.

Kind Regards

Davy Pelssers

The SAP University Team

Davy has been working as an SAP Consultant since 2000 and started working in the SAP IS-U Module , but as of 2002 he has mainly worked as functional SAP CRM consultant and SAP Authorizations consultant.
More about

0 thoughts on “Middleware Monitoring in SAP CRM: BUPA_MAIN error analysis -5

Leave a Reply


*