Ahh, my package build report has an error on FDASPEC 0 records….
I can never remember what file FDA spec is… Actually, I can. I open UTB, I open spec files.
Then choose a pathcode and see the relationships – great!
I then used a web based OCR program http://www.onlineocr.net/ to covert this image to words, so we can all do a search on this information and find it quicker next time! Nice!
| JDESPECTYPE_SVRHDR | |
| F98753 | JDESPECTYPE_SVRDTI |
| F98720 | JDESPECTYPE_BUSVIEW |
| F98710 | JDESPECTYPE_DDTABL |
| F98711 | JDESPECTYPE_DDCLMN |
| F98712 | JDESPECTYPE_DDKEYH |
| F98713 | JDESPECTYPE_DDKEYD |
| F98743 | JDESPECTYPE_DSTMPL |
| F98751 | JDESPECTYPE_FDASPEC |
| F98750 | JDESPECTYPE_FDATEXT |
| F98761 | JDESPECTYPE_RDASPEC |
| F98760 | JDESPECTYPE_RDATEXT |
| F98740 | JDESPECTYPE_GBRLINK |
| F98741 | JDESPECTYPE_GBRSPEC |
| F98762 | JDESPECTYPE_BUSFUNC |
| F98745 | JDESPECTYPE_SMRTIMPL |
| F98306 | JDESPECTYPE_POTEXT |
So now we know the relationship of spec files to central objects tables.
1 comment:
I am getting this same error when i try to build a full package. The server build completed successfully but the client build gets stuck at trying to build fdaspec. How do i solve this issue?
Post a Comment