F4311EndDoc errors

Andrew2009

Well Known Member
So I copied a vanilla application P4310 (Purchase Orders) into my own custom application so I can make some minor changes to it. I got the attached errors when I ran it. It happened in form A) Please see attached screenshot. I only got this error in DV and not PY or PD. Do you have any idea what these errors are?

Thanks
 

Attachments

  • 2017-10-25_15-57-27.jpg
    2017-10-25_15-57-27.jpg
    13.7 KB · Views: 26
Last edited:

Andrew2009

Well Known Member
Attached is a screenshot of the debugger and the values that were passed to this business function.
 

Attachments

  • 2017-10-26_10-18-05.jpg
    2017-10-26_10-18-05.jpg
    19.2 KB · Views: 10

Larry_Jones

Legendary Poster
I can't read the snapshot but I do have a comment.

Copying a major application such as P4310 for a "couple minor changes" may not be the best way to go here. There are attached Processing Options, possible dependencies on Application Program Name in called BSFNs, etc.

Really - you're much better off modifying the original P4310 if its just a few minor changes as you claim.

Just my 2 cents.
 

Andrew2009

Well Known Member
I agree with you except that someone did the copy a while back. I was just brought in to troubleshoot this issue in DV. Like I said it works in PY and PD.

I enlarged the screenshot to show you how I called this bsfn and below are the values

VA frm_CTID_ComputerID = "MGRBE1WS3"
VA frm_JOBS_JobNumber = "0"
"EP4310" is hard code for BF szCallingApplicationName
SL VersionName = "TMGBK15"
VA frm_USR0_UserID = "ANDY"
VA frm_EV01_UsesWorkFields = "2"
Zero is hardcoded for BF cConsolidateLines
VA frm_mnProcessID_PEID = "3092"
VA frm_mnTransactionID_TCID = "14"
FI mnROSI = null
FI mnTaskOrderNumber = null
FI szTaskOrderType = 'Blank'

Thanks
JDE 9.2
 

Attachments

  • 2017-10-26_13-39-27.jpg
    2017-10-26_13-39-27.jpg
    20.6 KB · Views: 6

johndanter

Legendary Poster
Search your debuglog for ERROR INFO JDEERR and sniff around there to see what it's doing and why it's getting upset

It could a PID value that doesn't like not being EP4310. Seen that before
 

nkuebelbeck

VIP Member
I can't read the snapshot but I do have a comment.

Copying a major application such as P4310 for a "couple minor changes" may not be the best way to go here. There are attached Processing Options, possible dependencies on Application Program Name in called BSFNs, etc.

Really - you're much better off modifying the original P4310 if its just a few minor changes as you claim.

Just my 2 cents.

This! We used to copy and mod. But since there is no way to "rebase" your custom object, your left with all the bugs oracle fixes overtime

better left modifing stock object

EDIT: make sure you document your mods well. Who asked for it, why they wanted it, exact lines changed, exact changes made.
 
Last edited:

BOster

Legendary Poster
We take everything on a case by case basis with modding the pristine object as the default. I have never understood the copy-and-mod methodology. Copying and modifying can create a ton of issues both now and in the future and, honestly, has no real advantages. Again there are exceptions, and we will occasionally copy and mod but only when it makes sense (it rarely makes any sense).
 
Top