The Address Mapping could be considered a “cousin” of the Field Mapping in that it functions much like the field mapping logic however it relates solely to the function of address and registrations. As of the 6.4.4.0 release the address mapping table has been improved to allow a user to easily add via mapping, new fields to the address logic as well as a source address mapping. These two new tables are designed to make available logic that was in prior releases, part of the class that was behind the address source logic. Now instead of hidden within the program, the fields and logic are available for users to easily adjust as needed. This change was in response to the new field additions within the Cloud Determination 2018.3 release for new XML fields for Oil and Gas customers.
If you are not taking advantage of the Oil and Gas fields in Cloud Determination you will not be forced into converting your custom address sources over to this new table function and will not be required to populate these new tables unless you choose to do so for new customizations or to make visible your current address source classes. The new logic and table usage is placed in the program after our standard logic and the prior class has not been removed. The program will access the old class program logic and then augment it with the new table mappings we describe below if they are populated for the given address source.
Field Mapping for Address Journey
This is covered in the current field mapping table for JOURNEY_ADDRESSES. This journey provides a way to add new attribute fields to the address that are used within the various address sources. It maps /IDT/JOURNEY_ADDRESSES using the base logic within GN_ADDRESSES to the fields that are available within the Determination list of mappable address target fields. In prior releases this mapping was done behind the scenes within the address_journey class, which means all those address fields were hard coded there hence to add new fields we would have need to change the program. Now the mapping and other functions have been exposed to users so they can easily add new fields to the address sources and types as needed. This is helpful for customers that need to add new data for Oil & Gas usage in Determination 2018.3 and above.
Transaction Code:
/IDT/FIELD_MAP_NEW
- Field Mappings
Transaction Code:
/IDT/ADDR_FIELD_MAP
- Address Source Field Mappings
This new mapping table exposes to the customer mappings that were part of the class that was attached to the address source. You can see in the example below that it maps the address source or partner function to the target field in the Integration. The table is populated with all the standard mappings that are required and would normally not need to be appended with custom mappings unless the customer has created a new custom address source or has added new fields to the address sources as needed for Oil & Gas customers, etc.
Source_field determines from where address needs to be collected (SADRVB or ADRC tables). F4 on this field displays other tables and their fields can be mapped but logically that are not address related tables/fields and hence are not useful for us.
This ALV program can be used in the same fashion as a normal field mapping program which includes maintaining adjustments and simple expressions.
For example – simple expressions and adjustments maintained in the standard mapping for partner functions.
A new Combined View with default mappings has been provided.
Transaction Code:
/IDT/ADDRESS_MAP_NEW
When you first select the new transaction code you will see the selection screen which allows you to select portions of the table by entering a given route or set of routes using the multiple selection options.
To get the full set of the address mappings table including both standard lines and customer created lines you can just hit
EXECUTE
to get the full table listing.
Here you can maintain your own address mappings or augment existing ones. You can also define alternate registration sources, other than what is pre-delivered. See the “Registration Number Mapping” topic for more details.
Explanation of the columns in the address mapping table:
| |
|
In this column you specify one of the logical address types that are listed in the standard delivery /N/IDT/ADDRESS_TYPES_V, it represents Determination target address structure.
|
|
Defines the applicable address source within SAP.
NOTE: Address Source can’t be used at the same time as the Partner Function column (Funct)
|
|
This column is a drop-down list of applicable partner functions from SAP Table TPAR and can be used to map your address instead of one of the address sources described prior.
NOTE: Address Source can’t be used at the same time as the Partner Function column (Funct)
|
VAT Registration number check boxes
|
The three columns of check boxes are used to indicate the target mapping for Buyer, Seller, or Middleman VAT Registrations.
|
Integration will always provide a list of registration numbers based on the primary registration and the foreign registrations maintained on the source master record. For foreign registrations we select the ones that match the countries represented across all address sources used in the business process.
There are no default mappings provided for ORDER_ORIGIN and ORDER_ACCEPTANCE addresses. Customers must add custom mappings to make use of them, especially in the US.
Special Note for Onetime Vendor Mapping
New address sources have been added for Onetime Customer and Onetime Vendor addresses. We have not included these in the standard mappings that we provide. If a user wishes to adjust the Vendor address source to come from the manually entered Onetime Vendor address entry on the PO (or Onetime Customer on the sales order and billing), then the user will have to add a custom mapping to this table to do so. This may be required for VAT Ship-from calculations if you are using a onetime vendor master record and need complete address for the ship from location in the XML request. See example below.
The Address Types table represents the addresses supported in the Determination XML structure. There are three special address types for use with Registrations, see “
Registration Number Mapping” for their specific use. This table is provided as a standard default only. There is no corresponding custom table for this as address types can only be changed via a tax calculation interface change in Determination.
Transaction Code:
/N/IDT/ADDRESS_TYPES_V
The Address Source table represents a list of SAP address entities supported with Integration. Behind each address source, code has been implemented that knows how to gather the necessary data based on the business process used. The address sources are in addition to the partner function based addresses supported in the address mapping.
Transaction Code:
/N/IDT/ADDRESS_SOURC_V
List of the predefined address sources delivered with Integration.
You will see that we now have a new column for “Class to Set Address” that is populated with the name of the programming class that contains the program logic for this address source. If you have need to change the address source so that it pulls the address based on a different master data field, you can make your modifications to this class as noted in the table.
Any customization that you may have done in your system prior to Integration release 6.3.0.0 will likely be ignored with the creation of these new classes. When upgrading to release 6.3.0.0 from a prior release of our product you should update any customizations by making the changes to the class we have noted in this table as opposed to how you modified the address source prior in your system.
You can create custom address sources via Transaction Code:
/N/IDT/ADDRESS_SOURCES
You would name your custom address source in this screen and then program the logic on how that address has to be found from the business transaction. Once done so you can map the source in the address mapping. See the Installation and Programmers Guide topic “Custom Address Source” for a programming example.