OE to PO 1

[jake29]

Does anyone happen to know why the data in the user defined fields (1-5) in the OEORDLIN table would not transfer over to the POORDLIN when a PO is generated? It would be convenient if it did for a project I am working on.

We are using Peak/Techtura/Exact OE to PO link. Could this be the problem? If so, any ideas on how I can resolve it?

Thanks

 

[stravis]

It would not transfer by design. The user defined fields on the purchase order may be used to store other values for some systems. If you want to transfer the user defined fields I would suggest writing a custom SQL Server Trigger.

Scott Travis

http://www.infospring.net

 

[AKPolarBear]

Is that for information that only needs to be printed on the PO? If so, that might be manipulated through the form field functions instead.

 

[jake29]

Unfortunately no. I will need to pull, update and then re-enter the data after the PO has been created but before it is printed. So for the sake of tightness, it would best to bring it over to the PO side and work on it from there.

 

[AKPolarBear]

I think the short answer is no. Can you make use of notes?

Did you contact Exact NJ? They might answer you without problem.

 

[jake29]

I use the line cmts now to allow for a more extensive product detail but I would like to be using the User defined fields.
It seems pretty logical that if the fields are available and are not in use, then why not.
I was leaning towards a SP for this. I guess it is time for a crash course in Triggers instead.

Thanks to both of you.

 

[stravis]

jake29 be very careful when developing a SQL Trigger. Any error that comes up due to an unexpected condition that your trigger does not handle will cause the originating transaction (write to sales order) to fail. I encourage learning how to do this, but my professional opinion is that you ought to do quite a bit of functional testing on a test company prior to deployment. If there is a problem with your trigger it could cause serious data corruption issues.

Scott Travis

http://www.infospring.net

 

[jake29]

Hey Scott, as cowboy as it sounded it is definitely not something I would take lightly.

I am actually going to use a Flex script on the OEGENPOS screen to make this happen.

Thanks again.

 

[jake29]

Related and not related to this thread.

Is it possible to programmatically change the labels for the user defined fields on the OE0101U based upon the item no. of the currently selected line?

 

[stravis]

It is possible. To do this modify the screenset using designer and hide all of the existing user defined field literals (labels). Now right-click on the screen and select "Special | Add Variable Label". Do this for all of the labels you want to make dynamic. Save your changes and launch the order entry screen, open flexibility, and navigate to the line item user defined screen (OE0101U). You can then assign values to the variable labels using LabelName.Text = "My Label" as your syntax, in the "InitForm" event.

 

[jake29]

In designer I hid the literals for the UDFs and added 5 Variable labels, saved and went into the UDF screen.

Found that, as they should be, the UDF's literals are all hidden.

Found
VarLabel
VarLabel1
VarLabel2
etc..

had been added

To test I added the following to the macForm_InitForm()

OE0101U.macform.VarLabel.Text = "Test"

but the text is not displaying.

The properties of the VarLabel indicate that
text = Test,
enable = true,
Visible = true,
backcolor is gray,
and
forecolor = blue in hex of course.

The number of controls on the form incremented to 10.

Re-checked the labels in designer, all good.

Am I missing something?

 

[stravis]

What version of Macola are you using? I seem to remember that this did not work on some older versions. Also, make sure that your variable label is not hiding under another control, as I recall Macola modifies the dimisions of the OE0101U screen when it opens the screen in the application.

If this does not work we can look at some Windows API based solutions.

Scott Travis

http://www.infoSpring.net

 

[jake29]

I am running 7.6.100

I removed all but one of the labels, moved them to different locations on the form thinking that they were being obscured
some how. Did not help.

 

[stravis]

Try setting the values through the GotFocus event of the first field with focus when you first start the form. The text paints differently when you do this. If this does not work I think I have a solution through the Windows API that appears to work. Let me know how the GotFocus test works out for you.

Scott Travis

http://www.infospring.net

 

[jake29]

No luck.