Tax Jurisdiction Determination Using Vertex in MDG

[Former Member]

Hi,

We are using SAP MDG Customer 8.0 and planning to use Vertex as Tax Jurisdiction Code Determination.

However we are not sure how to integrate the vertex with MDG.

We are thinking two approaches but not sure which is correct way to go.

1. Integrate Vertex to ECC-Part of MDG like regular integration. We are under impression that MDG will accommodate the ECC configuration and show the popup that we used to get in XD01. So we are not doing anything in MDG if this approach works.

2. Utilize the Enrichment Framework in MDG. We are thinking of using the enrichment framework to make BADI/RFC calls to vertex and then get the tax jurisdiction codes. But this may have challenge of developing User Interface and rules etc. In this case we don't have to do anything in ECC part of MDG.

If there are any options, please let us know.

Can any one share some experience on how you have implemented.

[Former Member]

Vertex is already integrated with MDG though the application layer. Make sure it works in your regular transactions (XK01 & XD01) and it will work with MDG.

[Former Member]

What is the recommended approach if its a Hub deployment .

Integrate Vertex to

1) MDG Hub & ECC(operational)

2) Only to ECC(operational)

asking because

Option 1 :  In the ideal world this should work, but in the realistic world – if a record is created with a bad address and the user over-rides the address standardization (via SAP Data Services) then we have seen cases  where the record fails due to ‘Unable to determine tax jurisdiction code’ . Even if the address is standardized by data services there are errors due to periodic updates in the vertex system.

Option 2 : There are licensing / cost implications if we go with option 2 (if client does not go in for vertex cloud) . Not sure if there are other options to address this implication.

[Former Member]

I find there is tax jurisdiction enrichment(ENRICH_TAXJUR) which calls same method CALLMETHOD cl_mdg_bs_fnd_bp_services=>get_tax_jurisdiction_codes as the MDG UI handler method CL_MDG_BS_BP_HANDLER-IF_MDG_BS_BP_ACCESS_HANDLER~DERIVE_DATA(derive_taxjurcode) calls. This enrichment framework has the webdynpro interface which comes as standard. Do you know how to disable option1 and enable option 2?

Which approach you have selected as we are facing same issue with ‘Unable to determine tax jurisdiction code’ with option 1. Also it's not working seamlessly with address enrichment as it clears fields and at times goes into endless loop.

Thanks in advance.