Skip to Content
Author's profile photo Former Member

Upload Types in SPM

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:

Column Name

Description

UPLOAD_TYPE

Name of the target Object for data upload in SPM Data model

TARGET_TYPE

Whether it is master data or transaction data (two entries allowed: “IOBJ” or “DSO”)

TARGET_NAME

Name of the Info object if it is a master data load or name of the Data Store if it is Transaction data

UPLOAD_GROUP

Group this entry belongs to “TRAN” for Transaction Data, “MDAT” for Master Data

CHAIN_ID

Process Chain to be triggered after data is loaded in the Target (Specified in Column TARGET_NAME)

AUTO_CHAIN_START

Pls ignore

IS_SYS_DEPENDENT

Defines Source system dependence for Master Data

APPLICATION

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.

OPMDM_TYPES Table:

OPMDM_TYPEST Table:

 

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.

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Ashish Sharma
      Ashish Sharma
      Hi Rajesh,

      Data uploads were successfully carried out by one of the SPM users. However, other users (with different user id) are not able to see anything in the Data Upload Summary screen.

      Is there a restriction on the visibility of Data Upload Summary for data uploads carried out with one User id to other users in SPM?

      A similar behaviour is observed for other screens within the Data upload workbench screens.

      Incase this is not the expected behaviour, it would be great if you could please provide pointers to possible reasons for this.

      Just for your information, all users have been granted same privileges in the SPM application.

      Thanks in advance.

      Regards,
      Ashish Sharma

      Author's profile photo Former Member
      Former Member
      Blog Post Author
      Hi Ashish

      I am not sure how I missed your post. Sorry for that.

      Different users seeing different actions/data in the UI usually points to Authorizations. I  have not seen this happen for any other reason.

      Pls double check if all of the backend Roles, authorization profiles are exactly the same.

      Regards
      Rajesh

      Author's profile photo Former Member
      Former Member

      Hi Rajesh,

      Very good information for SPM implementation. When we create the upload type in OPMDM_TYPES it should also relfect in the table OPM_SOURCES while setting up the extractors. However we are able to save the upload types in OPMDM_TYPES table but this custom type is not visible while creating entry in the OPM_SOURCES. Do we need to maintain this in any where else to reflect.

      Thank you

      Best regards,

      Amarnath