All of the types/objects of data that can be uploaded in Spend Performance Management (SPM) thru the SPM Data Management Tool are set in the table OPMDM_TYPES. All of these data types are known as Upload Types in this context.
The SPM Data Mgmt. tool uses this table as its source for loading all data be it objects that are part of the SPM product or whether the objects have been included into the SPM data model as part of the implementation.
The OPMDM_TYPES table has the following fields:
Name of the target Object for data upload in SPM Data model
Whether it is master data or transaction data (two entries allowed: “IOBJ” or “DSO”)
Name of the Info object if it is a master data load or name of the Data Store if it is Transaction data
Group this entry belongs to “TRAN” for Transaction Data, “MDAT” for Master Data
Process Chain to be triggered after data is loaded in the Target (Specified in Column TARGET_NAME)
Defines Source system dependence for Master Data
Which application will this be used for, Fpr SPM, use “XSA”
For a more detailed explanation of Source System dependence, go to the following link: Source System Independence considerations during data load in SPM
The SPM products ships with 44 entries in this table (for the 2.1 release). This essentially means that out of the box, SPM supports 44 upload types.
There is a Text table supporting the internationalization labels for all of the entries in this table. The text table is OPMDM_TYPEST. This table already comes populated with entries in SPM supported languages for all 44 upload types. You need to populate the language specific labels for upload types that have been created during the implementation.
There is an additional table OPMDM_TYPES_KEY which allows for configuring additional concatenations per upload_type for uniqueness.
Hope this explains the way SPM Data Mgmt. identifies and loads data for different upload types in the data model. Pls feel free to comment if you have any furhter questions.