WS: WW: Update File Fields with World Writer
(Doc ID 627488.1)
Last updated on JULY 21, 2020
Applies to:JD Edwards World World Writer - Version A7.3 cume 4 and later
Information in this document applies to any platform.
The document provides the steps to update fields in a file. Some FAQs and troubleshooting tips are included.
Intended for personnel with the knowledge of file structure and an understanding of how a change to a file field can impact the business process.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|About Updating Files|
|Frequently Asked Questions (FAQs)|
|Question 1: How do you enter a literal value to update a julian date field?|
|Question 2: How do you update an alphanumeric field to blank?|
|Question 3: How do you update a numeric field to blank?|
|Question 4: Can a Non-JDE World file be updated using World Writer?|
|Question 5: Is there a way to write to a work file only when report criteria changes?|
|Error 2929 - 'Join files cannot use file update' is received when you put option 7 next to a field to be updated.|
|Error 1778 - ' Field must be selected for query output ' when you type a field name in the From Field Name field on the Update Spec window.|
|Error 1761 - ' End of expression expected, not found ' when you type a field name in the From Field Name field on the Update Spec window.|
|Error 1737 - ' Not authorized to version ' when you attempt to run the version in update mode. You have set up the Group Level Security and Field Level Security.|
|Error 1769 - 'Expected a Numeric Value' when you attempt to update a packed numeric field with a negative value. You have entered the Expression as 1234.56-.|
|Your version runs successfully (no joblog) in update mode but the field does not get updated. |
|You are getting the following errors when the version is in update mode: Data Mapping errors CPF5035 & CPF5029 and SQL0406 Conversion error to column xxxxx.|
|Your version updates a numeric field and the results of the calculated field look as expected on the report, but when the file update takes place, the new value of the field contains the wrong data.|