When researching an issue with OMW, it is best to start with the OMW logging. In the debug log, this is done by searching for the F98211 table. Then you look at the insert statement to locate the data dictionary alias. The best way to do this is to download Notepad++. Then open the log file and do a Find (CTRL-F) for the F98211. Select the button for Find All in All Opened Documents or if you have multiple documents open use Find All in Current Document if only working with one file.
Then you can scroll through the results looking at the codes. As an example, in the log we would have an entry similar to the following:
Jun 22 13:45:31.990006 - 5892/9072 WRK:Starting jdeCallObject INSERT INTO SY910.F98211 (LDLOGKEY, LDLOGSEQ, LDOMWLDTAI, LDOMWLDATA, LDOMWDFS1, LDOMWDFS2, LDOMWDFS3, LDOMWDFD1, LDOMWDFD2, LDOMWDFD3, LDOMWDFN1, LDOMWDFN2, LDOMWDFN3, LDPID, LDMKEY, LDUSER, LDUPMJ, LDUPMT, LDTIMEZONES, LDDSAVNAME) VALUES ('B1B8210E-F047-45B8-95DA-3110F5F71E4E',17,'149T','R55000T|UBE|E910|USER |',' ',' ',' ',0,0,0,0.000000,0.000000,0.000000,'P98220', 'TOOLSB','USER',115173,134531.000000,' ',' ')
Reviewing the insert statement, we can locate the data dictionary error message alias '149T'.
Note: Many of the codes may be simply action called items which can be ignored. For example, 130S is one of these. As you go through the log, you’ll have to weed through these entries to locate the actual issue.
To look up any given code:
- Log into EnterpriseOne > Fastpath to DD > Launch the Error Messages application > Enter the alias into the Alias QBE field to search.
- Enter the alias from the insert statement from the log into the data item QBE and press find
- Open the data dictionary item and select the Item Glossary tab to see the full details of the message
If you look at the OMW logging in OMW, you should see a message similar to what we see in the Glossary Text.
- Highlight the object in OMW
- Row exit > Logging
- Select the log entry or Row > Log Detail
Some of the error codes can be self-explanatory in their resolution. However, others may need further research. Once you locate the error code, simply search in MOS for the code and you should get a document with details on its resolution. This process can be seen in the following examples where we locate the code and the document with additional details.
Example with Document:
Jun 03 07:24:44.061005 - 2608/3944 WRK:Starting jdeCallObject INSERT INTO SY910.F98211 (LDLOGKEY, LDLOGSEQ, LDOMWLDTAI, LDOMWLDATA, LDOMWDFS1, LDOMWDFS2, LDOMWDFS3, LDOMWDFD1, LDOMWDFD2, LDOMWDFD3, LDOMWDFN1, LDOMWDFN2, LDOMWDFN3, LDPID, LDMKEY, LDUSER, LDUPMJ, LDUPMT, LDTIMEZONES, LDDSAVNAME) VALUES ('54497473-6a7f-49b9-8fce-0e8a396c41b5',2,'130H','a required Template|the destination for this version. Template must exist in the target location before the version, or be in the same project if this action is being done on the project.|',' ',' ',' ',0,0,0,0.000000,0.000000,0.000000,'P98220', 'TOOLSB','USER',115154,72444.000000,' ',' ')
Check In Fails for One Specific UBE version. Error: 130H - Template Must Exist In The Target Location Before The Version (Doc ID 2011394.1)
Example with Document:
Jan 05 19:47:37.609003 - 3748/1612 WRK:Starting jdeCallObject INSERT INTO JDE812.SY812.F98211 VALUES ('07829c75-9eaf-4dbd-951d-903a85a685fa',12,'130J','c:\e812\DV812\include\F0005.h|FUtil::CopyF|',' ',' ',' ',0,0,0,0.000000,0.000000,0.000000,'P98220','TOOLSB','USER',110005,194737.000000,' ',' ')
Error 130J "Failed to write file" during Check-In or Check-Out of a Business Function or Table (Doc ID 631737.1)
Additional details on this troubleshooting process can be found in document Understanding OMW Logging in Object Management Workbench (P98220) (Doc ID 1569747.1) and OMW Troubleshooting Tips and Techniques (Doc ID 660791.1).