NewFeature.pngLogs are an essential part of diagnosing and resolving issues. There are many different types of logs and they take time to collect but in most cases they are essential to finding a resolution. For these reasons the SRDC documents have been created and you may have already seen them but just not realized it.


Quite simply these are document that clearly explain what specific data (logs, information, table data, screen shots) is required to troubleshoot a specific problem and how to gather the required data.


SRDC’s are standard knowledge documents with a type of DIAGNOSTIC TOOLS that are based on a specific types of issue e.g. Package Build, UBE etc (just as our other documents are) but they are created using a specific builder to create a consistent look and feel and user experience.


These documents maybe attached to your Service Request by an Engineer or presented you whilst logging a new Service Request so you know immediately what information is required to resolve your issue and how to generate it. 


We are constantly adding to the list of SRDC’s but here are some example SRDC’s that exist today:

  • SRDC – How to Generate Logging Information for a Report or Batch Application (Doc ID 1630238.1)
  • SRDC - Data Collection for Troubleshooting a Package Assembly Issue (Doc ID 1931378.1)
  • SRDC - Data Collection for Troubleshooting a Package Build Issue with Tools Release 9.1.5 Enhanced Server Only Package Build Process (Doc ID 1931514.1)
  • SRDC - Data Collection for Troubleshooting a Package Build Issue (for Tools Releases pre-9.1.5) (Doc ID 1931379.1)
  • SRDC - Data Collection for Troubleshooting a Package Deployment Issue (Doc ID 1931381.1)
  • SRDC - Collecting Data For Troubleshooting Issues When Using The Change Assistant Tool (Doc ID 1906687.1)
  • SRDC - Data Collection for Troubleshooting a JD Edwards EnterpriseOne Software Update (e.g. ESU, ASU) Issue (Doc ID 1957734.1)