Can we have definition of standard object/element from TMF(ex-666, 637, 639) and ServiceNow Table Structure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2022 04:01 AM
Hello,
Can you please guide on below,
Can we have definition of standard object/element from TMFxxx(ex-TMF666, TMF637, TMF639, etc) and ServiceNow Table Structure against each standard TMFxxx API/payload.
What are tables are in scope for a individual TMFxxx, and what details can be stored with individual table from TMF payload.
How we can relate these TMFxxx API/Payload tables like 'product inventory', etc.. to CSDM model object/four section and how and where to bring TMFxxx API elements?
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2022 05:02 AM - edited 05-31-2023 06:10 AM
This likely warrants further discussion. Please reach out to me with further questions (tom.schnarr@servicenow.com) and we can explore the problem further. But here is a starting list - using San Diego table names:
TMF620 (Product Catalog) - Product Specification (sn_prd_pm_product_specification
TMF633 (ServiceCatalog) - Service Specification (sn_prd_pm_service_specification)
TMF622 (Product Order) / TMF641 (ServiceOrder) -> Customer Order (sn_ind_tmt_orm_order) (note my original reply had this as TMF620)
TMF637 (Product Inventory) - Product Inventory (sn_prd_invt_product_inventory)
TMF642 - (Alarm Managment) - Event(en_event) (i missed this in my original post)
TMF621 - (Trouble Ticket) - Case(sn_customerservice_case) or Incident (incident)
TMF645 (ServiceQualification) - also creates sn_ind_tmt_orm_order (I missed this in my original post)
Some APIs that are not yet productized and their likely map:
TMF666 (Account Management) - Customer Account (customer_account)
TMF651 (Agreement Management) - Contract (ast_contract)
TMF646 (Appointment). - FSM (need this definition)
TMF655 (Change) - Change Request (change_request)
TMF629 (Customer) - similar to account
TMF673 (Geological Address) - Location - (cmn_location)
TMF674/675 (Geographical Site) - Site (cmdb_ci_site)
TMF632 - Party Management - Account or contact (customer_contact)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2022 08:35 AM
Thanks Tom for response, and sharing details of table name.....
Will appreciate if we get guidance on entity/element to store where.... because in single TMFXXX api we could have more/multiple entity/elements and while consuming this in ServiceNow, where to create what. Ex. TMF637 consist for service, product instance, product offering, characterize, specification, location/site, customer/account...etc.
Can we get some example or usecase focusing around this and using CSDM framework.
Or any reference NowLearning materials on this would help to get detail.