x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 8 replies
  • Subscribers 105 subscribers
  • Views 2478 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
bethbowers

2018 Import into Job Posting Entry - Error

SOLVED
Posted By

Having an issue with Cost Codes in an import into Job Posting Entry.  The cost codes, with "-", are longer than 9 characters, and I do have the Skip Source Data Transaction checked.  It still did not like the Cost Code, so I did a calculated field where I took out the dashes.  It then seemed to calculate the cost code correctly, but said it was not on file (which it clearly is).  I changed the Job Cost Options to do no validation, and still cannot get it to accept the cost codes.

I have a cost type (valid, although it shows as invalid since there is no valid cost CODE) and a job number (valid).

Parents
  • 0

    Use DFDM on JC_CostCode and confirm the length of the CostCode in the file. In my 2018 install, regardless of segment length selected under JC Options, the CostCode is zero padded on the right to 3 characters for each segment regardless of whether or not the CostCode is numeric or alpha-numeric.

  • +1 in reply to David Speck
    verified answer

    Also, it seems Job Posting Entry automatically pads zeros on the left for each segment but VI doesn't do any automatic padding and i have been unable to find a method available to do this with the available business objects.

    I did however find that VI would not let me use the Next operation on the EntryNo field but i was able to make this work by using the following in a Calculated statement.

    ""; coBusiness'GetNextEntryNo(Var$)

Reply
  • +1 in reply to David Speck
    verified answer

    Also, it seems Job Posting Entry automatically pads zeros on the left for each segment but VI doesn't do any automatic padding and i have been unable to find a method available to do this with the available business objects.

    I did however find that VI would not let me use the Next operation on the EntryNo field but i was able to make this work by using the following in a Calculated statement.

    ""; coBusiness'GetNextEntryNo(Var$)

Children
No Data

*Community Hub is the new name for Sage City