Registration number mapping for SAP

Providing the proper set of registration numbers to Determination is important in the taxing decision. Integration for SAP provides a flexible approach to meet that requirement by combining the Address Mapping and Field Mapping features.

Mapping for VAT registration numbers based on the partner function are managed through the address mapping table with the use of three check boxes (Buyer, Seller, and Middleman roles) at the far-right side of the table. You will see that we have set standard mapping for these in the standard view only table but that a user can append or override them using the customer address mapping table.

Transaction Code:

/N/IDT/ADDRESS_MAP_NEW

A partial view of the combined Address Mapping is provided here.

You will see by the table example above that there are boxes checked to map the VAT registration numbers for each of the various routes in the table. Each route will need a mapping for a buyer role and a seller role. The middleman role has not been mapped in the standard mapping; however, you can elect to map a middleman role based on your requirements.

Address and Registration Source Same

In some cases, you might desire a different partner function as the source for registrations than what is delivered in the standard. In these cases, you can add a new mapping to the Address Mapping table and check the proper registration source. In that case that source serves as the address and registrant source.

Address and Registration Source Different

When the address source needs to be different than the VAT Registration source you can add a mapping using a DUMMY address mapping which serves only as the registration source. The DUMMY base does not carry with it the address but can be used for the mapping of the registration numbers.

In our standard mapping for LIV transactions the address and registration source for the SELLER_PRIMARY is the Vendor. In above sample the registration source has been switched to the Invoicing Party (IP), while the address source is still the Vendor by using the SELLER REGISTRATION DUMMY address type.

The VAT Registration mapping that is shown here is all done via the address mapping table and the field mapping table within in SAP. However, you may also elect to maintain the VAT Registration Numbers for each of your companies via the configuration within the Determination. In that case you would “remove” the check mark from the VAT registration columns on any of the VAT registration mapping lines that use the company code address by creating custom copies of the Thomson Reuters provided mappings. Once done, the VAT Registration is then taken from Determination company configuration setup instead of SAP.

The address mapping-based registration solution provides means to source the primary and foreign registrations from SAP. However, in some cases registration numbers might be stored in the additionally provided Tax Number 1 through 4 (or 5 depending on SAP EHP) fields. This is mainly the case when there are Federal and lower level (Provincial) registrations required, like for example in Canada.

To map these sources a field mapping-based entry has to be made from two parts.

The source field definition:

PARTNER_TAB[PARVW=AG]-KNA1-STCD1

The target field definition:

REGISTRATIONS-BUYER-ROLE[ADD]

For customer mapping the target would be the REGISTRATIONS-BUYER_ROLE. The source field would be entered as shown below for the route groups involving customers:

PARTNER_TAB[PARVW=AG]-KNA1-STCD1

For vendor mapping the target would be the REGISTRATIONS-SELLER_ROLE. The source field would be entered as shown below for the route groups involving vendors:

PARTNER_TAB[PARVW=LF]-LFA1-STCD1

Based on the SD based mapping above a registration collection sent to Determination could look like this:

<REGISTRATIONS>

<BUYER_ROLE>123123123RT</BUYER_ROLE>

<BUYER_ROLE>PST-1234-5678</BUYER_ROLE>

<SELLER_ROLE>231231235RT</SELLER_ROLE>

</REGISTRATIONS>

Determination will return the three possible VAT registration numbers used to make the taxing decision for possible use in invoice printing, reporting, and compliance. A standard mapping is provided to have them written back to the Thomson Reuters Tax Data table.

Registration Based on Business Place Configuration

For many non-EU countries (Brazil, India, Taiwan, Korea, etc...) registration information is not stored in T001N or T001 tables in SAP but stored in the Business place in SAP.

Transaction:

SPRO

navigate to

> Cross Application Components > General Application Functions > Place of Business > Define Business Place

.

Within a company code there can be many business places with different registration information for each depending on the country tax policy. The Business Place is selected during transaction processing and tied through configuration to the sales office for sales order processing.

See screen print below that shows the two fields used within the business place configuration to store the VAT registration numbers. For purpose of this example we are using the Tax 2 field.

Table name:

J_1BBRANCH

Field names

STCD1

and

STCD2

Utilize fields from the

J_1BBRANCH

table within the Flexible Field Mapper for the following journeys:

NOTE

:

The source of Business Place is different per transaction, it is therefore recommended to map fields from the J_1BBRANCH table source to Determination, and not from the transaction tables. If using the value from the transaction, then it would be as follows:

Sample mappings for the registration from the business place are shown below for the three journeys mentioned above.

Header request journey mapping

Item request journey mapping

NG Item request journey mapping: note use of HDR-> in this one also.

The HDR-> pointer is used when mapping the field from the Header record to the line-item on the order and is required for the latter two journey mappings as shown above.

Other standard SAP configuration set up would be required to create the business place for the specified company code and country as well as tying it to the sales organization and sales area structures in SD module, etc. We have not shown all Business Place standard SAP configurations in this example.

A new address source for custom address mapping of BUSINESS PLACE address has also been created as part of this solution. Use transaction

/N/IDT/ADDRESS_MAPPING

to enable this feature if you also desire to map the address from the business place master data in addition to the registration numbers shown here. See Address Mapping table instructions noted above.