ER Compare copy problems retrofitting from Xe to 8.10

vmcdaniel

Active Member
Hello -
We are currently retrofitting custom changes made in XE into 8.10 objects. Everything has gone fine up until now. When we use ER Compare to copy just a single line of code(or a single comment!) to 8.10 for large objects such as P4310 or P4210, and then validate ER, we get MANY errors unrelated to that single ER line copied. Another programmer showed it to me on his pc, and I reproduced the problem on my pc in DV810...errors such as these:

*************************

EVENT RULE VALIDATION LOG

APPL - P4210 - Sales Order Entry

Created : Fri Apr 22 16:42:40 2005

*************************

/* CER ERROR #3027 : Invalid Behavior Template Id */
Function Name: P4210_W4210A_5_1563
Function Description: ER for W4210A_5_1563
Form: W4210A - Sales Order Detail Revisions
Control: 5 -
Event: 1563 - Post Button Clicked
/* D4205310 */

*************************

/* CER ERROR #3027 : Invalid Behavior Template Id */
Function Name: P4210_W4210A_570_0
Function Description: ER for W4210A_570_0
Form: W4210A - Sales Order Detail Revisions
Control: 570 - &Blanket Orders Sales Blanket Order Information
Event: 0 - Button Clicked
/* D4205310 */

*************************

/* CER ERROR #3027 : Invalid Behavior Template Id */
Function Name: P4210_W4210A_811_0
Function Description: ER for W4210A_811_0
Form: W4210A - Sales Order Detail Revisions
Control: 811 - Delete Lines
Event: 0 - Button Clicked
/* D4205310 */

*************************

/* CER ERROR #3027 : Invalid Behavior Template Id */
Function Name: P4210_W4210A_812_0
Function Description: ER for W4210A_812_0
Form: W4210A - Sales Order Detail Revisions
Control: 812 - ProcessBlanketOrder
Event: 0 - Button Clicked
/* D4205310 */

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210B_0_272
Function Description: ER for W4210B_0_272
Form: W4210B - SOE - Additional Information
Control: 0 - FORM
Event: 272 - Dialog is Initialized
Seq #: 150
Line #: 149
Line Text: FC Cross-Dock Priority = "0"

*************************

/* CER ERROR #3021 : Invalid destination for assignment */
Function Name: P4210_W4210B_0_272
Function Description: ER for W4210B_0_272
Form: W4210B - SOE - Additional Information
Control: 0 - FORM
Event: 272 - Dialog is Initialized
Seq #: 150
Line #: 149
Line Text: FC Cross-Dock Priority = "0"

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210B_0_272
Function Description: ER for W4210B_0_272
Form: W4210B - SOE - Additional Information
Control: 0 - FORM
Event: 272 - Dialog is Initialized
Seq #: 165
Line #: 164
Line Text: FC Cross-Dock Priority = FI mnCrossDockingPriority

*************************

/* CER ERROR #3021 : Invalid destination for assignment */
Function Name: P4210_W4210B_0_272
Function Description: ER for W4210B_0_272
Form: W4210B - SOE - Additional Information
Control: 0 - FORM
Event: 272 - Dialog is Initialized
Seq #: 165
Line #: 164
Line Text: FC Cross-Dock Priority = FI mnCrossDockingPriority

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210B_0_1536
Function Description: ER for W4210B_0_1536
Form: W4210B - SOE - Additional Information
Control: 0 - FORM
Event: 1536 - Post Dialog is Initialized
Seq #: 150
Line #: 149
Line Text: VA frm_mnPrevCrossDockPrior_XPTY = FC Cross-Dock Priority

*************************

/* CER ERROR #3022 : Invalid source for assignment */
Function Name: P4210_W4210B_0_1536
Function Description: ER for W4210B_0_1536
Form: W4210B - SOE - Additional Information
Control: 0 - FORM
Event: 1536 - Post Dialog is Initialized
Seq #: 150
Line #: 149
Line Text: VA frm_mnPrevCrossDockPrior_XPTY = FC Cross-Dock Priority

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210B_11_0
Function Description: ER for W4210B_11_0
Form: W4210B - SOE - Additional Information
Control: 11 -
Event: 0 - Button Clicked
Seq #: 127
Line #: 126
Line Text: If FC Cross-Docking Flag (Y/N) is not equal to VA frm_cCrossDockFlagYN_XDCK Or FC Cross-Dock Priority is not equal to VA frm_mnCrossDockingPriorit_XPTY Or FC Cross Dock Order Number is not equal to VA frm_mnCrossDockOrderNumbe_XORN Or FC Cross Dock Order Type is not equal to VA frm_szCrossDockOrderType_XCTO Or FC Cross Dock Order Company is not equal to VA frm_szCrossDockCmpyKeyNo_XKCO Or FC Cross Dock Order Suffix is not equal to VA frm_szCrossDockOrdeSuffix_XSFX Or FC Cross Dock Line Number is not equal to VA frm_mnCrossDockLineNumber_XLLN

*************************

/* CER ERROR #3020 : Invalid criteria subject */
Function Name: P4210_W4210B_11_0
Function Description: ER for W4210B_11_0
Form: W4210B - SOE - Additional Information
Control: 11 -
Event: 0 - Button Clicked
Seq #: 127
Line #: 126
Line Text: If FC Cross-Docking Flag (Y/N) is not equal to VA frm_cCrossDockFlagYN_XDCK Or FC Cross-Dock Priority is not equal to VA frm_mnCrossDockingPriorit_XPTY Or FC Cross Dock Order Number is not equal to VA frm_mnCrossDockOrderNumbe_XORN Or FC Cross Dock Order Type is not equal to VA frm_szCrossDockOrderType_XCTO Or FC Cross Dock Order Company is not equal to VA frm_szCrossDockCmpyKeyNo_XKCO Or FC Cross Dock Order Suffix is not equal to VA frm_szCrossDockOrdeSuffix_XSFX Or FC Cross Dock Line Number is not equal to VA frm_mnCrossDockLineNumber_XLLN

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210B_11_0
Function Description: ER for W4210B_11_0
Form: W4210B - SOE - Additional Information
Control: 11 -
Event: 0 - Button Clicked
Seq #: 160
Line #: 159
Line Text: FC Cross-Dock Priority = "0"

*************************

/* CER ERROR #3021 : Invalid destination for assignment */
Function Name: P4210_W4210B_11_0
Function Description: ER for W4210B_11_0
Form: W4210B - SOE - Additional Information
Control: 11 -
Event: 0 - Button Clicked
Seq #: 160
Line #: 159
Line Text: FC Cross-Dock Priority = "0"

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210B_11_0
Function Description: ER for W4210B_11_0
Form: W4210B - SOE - Additional Information
Control: 11 -
Event: 0 - Button Clicked
Seq #: 168
Line #: 167
Line Text: FI mnCrossDockingPriority = FC Cross-Dock Priority

*************************

/* CER ERROR #3022 : Invalid source for assignment */
Function Name: P4210_W4210B_11_0
Function Description: ER for W4210B_11_0
Form: W4210B - SOE - Additional Information
Control: 11 -
Event: 0 - Button Clicked
Seq #: 168
Line #: 167
Line Text: FI mnCrossDockingPriority = FC Cross-Dock Priority

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210B_11_1563
Function Description: ER for W4210B_11_1563
Form: W4210B - SOE - Additional Information
Control: 11 -
Event: 1563 - Post Button Clicked
Seq #: 20
Line #: 19
Line Text: F4211FSEditLinePreProcess

*************************

/* CER ERROR #3003 : Unable to assign to data structure */
Function Name: P4210_W4210B_11_1563
Function Description: ER for W4210B_11_1563
Form: W4210B - SOE - Additional Information
Control: 11 -
Event: 1563 - Post Button Clicked
Seq #: 20
Line #: 19
Line Text: F4211FSEditLinePreProcess

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210B_172_512
Function Description: ER for W4210B_172_512
Form: W4210B - SOE - Additional Information
Control: 172 - Cross-Dock Priority
Event: 512 - Control Exited/Changed-Asynch
Seq #: 5
Line #: 4
Line Text: IfFC Cross-Dock Priorityis not equal toVA frm_mnPrevCrossDockPrior_XPTY

*************************

/* CER ERROR #3020 : Invalid criteria subject */
Function Name: P4210_W4210B_172_512
Function Description: ER for W4210B_172_512
Form: W4210B - SOE - Additional Information
Control: 172 - Cross-Dock Priority
Event: 512 - Control Exited/Changed-Asynch
Seq #: 5
Line #: 4
Line Text: IfFC Cross-Dock Priorityis not equal toVA frm_mnPrevCrossDockPrior_XPTY

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210G_397_9849
Function Description: ER for W4210G_397_9849
Form: W4210G - Sales Order Header
Control: 397 - Additional Header Information
Event: 9849 - Tab Page is Selected
Seq #: 5
Line #: 4
Line Text: FC SoldTo Buying Segment Code = BC Buying Segment Code (F4201)

*************************

/* CER ERROR #3021 : Invalid destination for assignment */
Function Name: P4210_W4210G_397_9849
Function Description: ER for W4210G_397_9849
Form: W4210G - Sales Order Header
Control: 397 - Additional Header Information
Event: 9849 - Tab Page is Selected
Seq #: 5
Line #: 4
Line Text: FC SoldTo Buying Segment Code = BC Buying Segment Code (F4201)

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210G_397_9849
Function Description: ER for W4210G_397_9849
Form: W4210G - Sales Order Header
Control: 397 - Additional Header Information
Event: 9849 - Tab Page is Selected
Seq #: 7
Line #: 6
Line Text: FC SoldTo Buying Segment Code = VA frm_SoldToBSC

*************************

/* CER ERROR #3021 : Invalid destination for assignment */
Function Name: P4210_W4210G_397_9849
Function Description: ER for W4210G_397_9849
Form: W4210G - Sales Order Header
Control: 397 - Additional Header Information
Event: 9849 - Tab Page is Selected
Seq #: 7
Line #: 6
Line Text: FC SoldTo Buying Segment Code = VA frm_SoldToBSC

*************************

/* CER ERROR #3036 : Form Control with NO szDict assigned */
Function Name: P4210_W4210G_397_9849
Function Description: ER for W4210G_397_9849
Form: W4210G - Sales Order Header
Control: 397 - Additional Header Information
Event: 9849 - Tab Page is Selected
Seq #: 10
Line #: 9
Line Text: If FC Ship To is not equal to <Zero> And FC SoldTo Buying Segment Code is not equal to <Blank>

*************************

/* CER ERROR #3020 : Invalid criteria subject */
Function Name: P4210_W4210G_397_9849
Function Description: ER for W4210G_397_9849
Form: W4210G - Sales Order Header
Control: 397 - Additional Header Information
Event: 9849 - Tab Page is Selected
Seq #: 10
Line #: 9
Line Text: If FC Ship To is not equal to <Zero> And FC SoldTo Buying Segment Code is not equal to <Blank>

Has anyone seen this problem before, and if so, what can be done so that we're not literally reproducing ER line by line in 8.10 for P4210?

Thanks,
Vernon
 
Vernon,
Do you have the same ER Validation errors if you do not use ER Compare? What happens if you check out P4210 and then just do Validate ER? Or manually retrofit one of your mods (or just one of your comments) and then Validate ER?

Did you check your data dictionary to make sure those data items actually exist? What about other related objects ... data structures, etc. Does the client machine have all the latest objects & specs?

Just a few quick thoughts...
Good luck!
 
Hi Vernon,

Did you compared 8.10 objects against the original XE Path Code?

Try to create a new 8.10 Path Code.
Check-Out the effected objects from XE then Check-In to the new 8.10 Path Code.

Compare the objects against the new 8.10 Path Code.

Regards,

Zoltán
 
Hello Zoltan,

I was comparing ER between 8.10 DV(pristine P4210 object) and our XE production pathcode(using remote spec location on my local drive after getting the specs from PD in XE, and then using Snapshot.exe to go back in 8.10). I'm not sure what you mean by comparing against the "original" XE pathcode..Pristine?

Also, just for the sake of getting smarter(been developing in One World for 4 years), how does one check out from XE and then check-in to 8.10. I assume when you say create a new pathcode, you mean something like a DEVSAVE(i.e., pathcode not in the object promotion pathcodes..DV, PY, PD). The only way I know of to retrofit between two upgraded One World systems is using Snapshot and copying specs down locally in order to "Copy Right" into 8.10.

Just to keep these thoughts in the same thread..Michelle D. also asked

"Do you have the same ER Validation errors if you do not use ER Compare? What happens if you check out P4210 and then just do Validate ER? Or manually retrofit one of your mods (or just one of your comments) and then Validate ER?

Did you check your data dictionary to make sure those data items actually exist? What about other related objects ... data structures, etc. Does the client machine have all the latest objects & specs?"

Q1 and Q2: No, when I checked out from DV, I was using the original pristine object, and it validated in designer. My base install of DV is from a full package with dev objects, and rarely is this a problem.
Q3: If I manually add a line, everything works fine. It's when an ER copy is done..the spec ID's for some lines gets wiped out I think.
Q4:Everything in the DD exists, no problems there.
Q5:See answer to 1 and 2 above.

Anyway, I am done with copying ER from XE to 8.10. Did it all in one fell swoop, and then fixed the breakage in designer. But, to sum up..if I went back to ER Compare to copy a stray line I missed in P4210, I would break the same lines over again that were broken after copying just one comment or line when I first started. It had nothing to do with any missing objects on the client, but I think it was a matter of spec lines getting corrupted. It didn't happen with most other objects I worked with in ER Compare. Just wondered if anyone else had seen this problem..and was only looking for causes/solutions if people had seen this problem.

Thanks,
Vernon
 
I can confirm the issues at Service Partners - I spent a couple hours trying to help determine a resolution.

Additional things we tried:
* Boomerang an object from Pre 8.x to 8.10. As soon as any line was VERC'd - the Unicode version logged errors during validation
* VERC'd against a local copy of the XE Spec folder (you copy the spec folder from XE to a safe place on your 8.x development machine - then VERC against it) - as soon as any line was VERC'd - the Unicode version logged errors during validation.
* We copied an original 8.x object to a new name, then VERC'd lines of code between - No Errors during Validation...

What I can tell you from personal experience - that this is not the norm. I can VERC between my Standalone versions of 8.x, ERP8 and JDE5 - without getting ER Validation errors. While at a client's site - we VERC'd between 8.x and a local copy of the XE spec folder on a regular basis (with no validation errors).

I'd really like to know why this issue occurs on the Service Partner's implementation.... I found it darn right frustrating.

Best regard, guys!

(db)
 
Hi,

we got the same for retrofitting from Xe to 811. There were many many ER validation problems in the supposedly standard P4210 and in P4310. We simply did an advanced get from Pristine and "magically" all of the validation problems went away. Don't know how but please try it, it might save you a lot of pain!

Rgds

Andrew
 
Hi Vernon,

I apologize for my brief and missunderstable reply.

I will try to explain it more exactly, what did I mean.

1.) I meant "original XE Path Code" any Path Code, which belongs to XE and functional/usable on XE. It can be any Path Code on your XE (DV7333, JD7333, PY7333, PD7333) as well on the server as on your fat client as Remote Location.

2.) Make accessible your "original" XE Path Code available and accessible from 8.10. I can not describe for you, how to do it, because I am not a CNC guy, but It is possible, because our CNCs did for us on 8.9 with success. Let name it PD7333 under 8.10

The reason of this: you will be able Check-Out/Get object from the XE Path Code under 8.10.

3.) Create a new 8.10 Path Code. Yes, it is like DEVSAVE, namely an empty Path Code. Lets name it XE_ON_810

The reason of this: You can the Checked-Out XE object Check-In into a separate and 8.10(!) Path Code.

4.) Create a new Project Status (let nam it XEGET) and configure it the way, that the Check-Out/Get From Location for Objects is PD7333 and the Check-In target location is XE_ON_810. Add a promotion path to be able to promote a project to XEGET status.

5.) On 8.10:
- create a project and promote it to XEGET status
- add your objects to this project
- Check-Out the object (it will come from PD7333)
- Check-In the object (it will go to XE_ON_810)
- release the token of the object
- Check-Out the object in a project with status 21
- now you can VERC the object against XE_ON_810.

Maybe alternativly you can spare 2-4 and a half of 5. I didn't try it, but hopfully works too.

2.) Install (temporarily) a second 8.10 Path Code on the fat client, just to store XE object on a 8.10 local spec. Let say PY10.

3.) on 8.10:
- sign on 8.10 to PY10
- add the object to a project
- Advanced GET the object from PD7333
- log-off EO1
- sign on 8.10 to DV10
- check-out the object under your project with status 21
- you can now VERC the object against your local PY10\spec

I hope, this time I was a bit more clear, hopefully enough clear.
I apologize for my English.

Please, let us know, if you tried one of the described technique.

Good luck,

Zoltán
 
Zoltan,

By the way..thanks!Trying to tighten up my nettiquette. : )

Vernon
 
Back
Top