Other features with SAP

The Data Popup Tool is a new feature for users needing to do field mapping or debugging to determine which tables and fields are available and populated with data within the current transaction you are testing. It is a valuable tool to determine issues with a transaction or identify additional fields that will work for future or current field mapping. This tool is to be used only in a test environment as a tool for analysis of the transaction as it will interrupt the transaction and pop-up within the transaction you are testing when a call is made to Determination for a tax calculation. There is a configuration table that you access to turn on the feature within the Reports and tools menu that will allow you to target the data based on a single journey or set of journeys that are used within the specific transaction. If multiple journeys are selected the screen will advance to the next journey once you get out of the current journey pop-up and will continue to do so until you have gone through the list of journeys that you selected and are used in the transaction,

Some transactions make many calls to Determination during the transaction: a ME21N Purchase Order is especially invasive in this respect and can cause the system to literally loop again and again through this pop-up feature and not let you out of the transaction. If this occurs, simply start a second session and change/ deactivate the popup tool and return to your prior session. Doing this delete process will allow you to proceed with the transaction without further issues. See screen shots below to access this feature, configure it, and view how it works.

Transaction Code:

/N/IDT/DATA_POPUP_TOOL

Once in the screen you will be able to change it to change mode and add lines to the table for your username and activate the journey. Currently the tool is available for the below list of journeys. More journeys will be added to this tool in the future and a drop-down list added for easier use. To deactivate a given journey, just return to the menu and turn off the active button. Journeys currently available include:

Next go to the desired transaction you wish to use this tool on and enter your data. When a call to Determination is made within the transaction the tool will activate and pop-up the data for the first journey selected.

Further instructions on how to use this tool and how the screen levels work is shown in the Installation and Programmers Guide.

The ONESOURCE Indirect Tax Integration for SAP Reconciliation Extract enables an organization using the ONESOURCE Indirect Tax Integration for SAP for their tax calculations to extract the necessary data from the SAP FI module to use in the ONESOURCE Indirect Tax Reporting Reconciliation Report.

The Reconciliation Report in ONESOURCE Indirect Tax Reporting will compare the imported data from the SAP Reconciliation Extract with the data in Audit. The Reconciliation Report will indicate transactions missing in the ERP (SAP), transactions missing in Audit, as well as differences in tax amounts.

The following steps are necessary if you want to use the Reconciliation Extract Report:

The reconciliation extract process can either write a file to the person’s desktop (presentation server) or the SAP Application Server. If using the Application Server, it is recommended that a file directory is created on the SAP file system specifically for Reconciliation, and then mapped as a default. To do so follow these steps:

Transaction

AL11

:

Select on

Configure

to add a new directory definition/path:

Save

your entry.

Now that you have defined the directory you can also set it as a default in the Reconciliation Extract selection screen as follows:

Transaction

STVARV

:

Add a new entry for parameter name of

/IDT/RECON_APP_SERVER_PATH

with the value of the server path you created in the previous step.

A system user may have need to add other fields to the /IDT/D_TAX_DATA table for reporting or reconciliation processes. Their ABAP programmer can append the table with their own custom field and then use the field mapping table feature to be able to populate the new field per their needs. A simple procedure of appending the table is outlined below:

Transaction:

SE11

Select “

Display

”. Once in the table, use the “

Append Structure (F5)

” menu option.

Create a new append in the customer's name space or using ZZ* naming convention. Include the change in a transport:

Add custom fields as desired:

Save and activate the changes.

The newly added fields now can be used in the Global Next Flexible Field Mapper to which to map data.

When creating an invoice in VF01, there are 2 entries in the XML logs, the regular one and the one that posts to audit. If the invoices are created in the background in VF06, only one entry is listed in the log (the one that posts to audit) and the transaction code column does not populate the transaction code.

This can be confusing if a user is using the information on the transaction code. A key problem is that SY-TCODE is blank for background jobs. There is generally no screen and thus no need for a transaction code in background jobs. This is a known limitation in SAP. Customers who use the SY-TCODE field must consider that SAP will return a NULL value at times. They can add a fall back custom field mapping using a constant for situations when SAP returns a null value.