CA SDM loading Special Handling - VIP

Document created by TMACUL Champion on Oct 4, 2016
Version 1Show Document
  • View in full screen mode

The first thing what you need know: VERY Important! Using pdm_load can be destructive so always back up your database before you perform a pdm_load, and use pdm_userload unless instructed to use pdm_load.

 

Important! Make a backup copy of the database before running pdm_load with this option. After old database records are removed, you must restore the CA SDM database with this backup copy if you want to recover any deleted records, use pdm_extract for this procedure.

 

1. BACKUP

 

BACKUP COMMAND
pdm_extract usp_contact_handling > usp_contact_handling.txt

 

 

2. Structure table

 

bop_sinfo -dq special_handling
actory special_handling < usp_special_handling >
Attributes:
id INTEGER UNIQUE
producer_id LOCAL STRING(20)
persistent_id LOCAL STRING(60)
delete_flag del SREL -> actbool.enum REQUIRED
sym STRING(60) REQUIRED
description STRING(4000)
alert_text STRING(60)
alert_icon_url STRING(1000)
autodisplay_notes SREL -> bool.enum REQUIRED
escalate_urgency SREL -> bool.enum REQUIRED
cnthandling_list BREL <- contact_handling.special_handling (LREL contact)
{special_handling = ?}
last_mod_dt DATE
last_mod_by SREL -> cnt.id TENANCY_UNRESTRICTED

 

 

Structure load: pdm_extract usp_contact_handling

TABLE usp_contact_handling
contact id special_handling tenant
{ "521C1F8D470A3F4BB6FF907A8C50B2E4" ,"400001" ,"1001" ,"" }

 

 

 

 

CA SDM Loading contacts pdm_load 

DEREF - pdm_deref - Everthing do you need know 

CA SDM Load department using pdm_load - dept - ca_resource_department 

CA SDM Load department using pdm_load - dept - ca_resource_department 

 

 

Was this information helpful? Feedback.

2 people found this helpful

Attachments

    Outcomes