Check in error

[Rauf]

I could check in a report template, business view.
But when I try to check in a version of the same report, I get the following error.
[ QUOTE ]

Error: General Error in method, Check-In


[/ QUOTE ]

I checked jdedebug.log, it says the following
<font class="small">Code:</font><hr /><pre>
Jul 09 13:09:21.737124 - 5628/4472 WRK:Starting jdeCallObject Exited jdeCloseDictionary with DDType 0
Jul 09 13:09:21.737125 - 5628/4472 WRK:Starting jdeCallObject Return value is 0 for OMWGetNextConfigSetting. (BSFNLevel = 3)
Jul 09 13:09:21.737126 - 5628/4472 WRK:Starting jdeCallObject Value for 7014, doesn't exist in the parameter list.
Jul 09 13:09:21.737127 - 5628/4472 WRK:Starting jdeCallObject Unable to get the OMW parameter, 7014.
Jul 09 13:09:21.737128 - 5628/4472 WRK:Starting jdeCallObject Failed to checkin TAM specs for the version, RRAUFTST|VER001.
Jul 09 13:09:21.737129 - 5628/4472 WRK:Starting jdeCallObject COB00001: jdeCallObject called to launch GetUDC.
Jul 09 13:09:21.737130 - 5628/4472 WRK:Starting jdeCallObject COB00001: jdeCallObject called to launch GetUDC.
Jul 09 13:09:21.737131 - 5628/4472 WRK:Starting jdeCallObject Calling Business function GetUDC from UNKNOWN for MRAUF. Application Name [P98220], Version [ZJDE0001] (BSFNLevel = 3)
</pre><hr />

 

[Adrian_Chimirel]

I saw this error when my colleague tried to check-in a new batch version, while in PY.
In what environment are you? And what is your project status?

 

[Rauf]

Yes.
I am in PY.
The project status is 21-Programming.

 

[DSauve]

Have you tried to create this in DV, and then promote it to PY?

 

[Rauf]

I could not do it. Because the login is customized to access PY while logging.
But why other objects <font color="green"> don't</font> have issue with check-in ?

 

[Adrian_Chimirel]

Because the OMW check-in rule for UBEVER specifies so, as the exception

Don't we love JDEdwards?

 

[Rauf]

So what is the workaround? Try with DV ? And can you guess why should I get this error only for new reports?

 

[Adrian_Chimirel]

In DV it should work; the best practices principle assumes you start development in .... Development (not in PY), then you promote to Prototype where other people (not you) are supposed to test the same obejct with different business data, and approve for final promotion to Production. This methodology ensures your object behaves reliably, not dependent on specifi business data.
PS Chosing to ignore/bypass the standard object life cycle, in other words to use JDE in a manner not supported traditionally by Oracle's development and support staff, is known in Denver, the JDE birth place, as "the cowboy way", or "The Law of The West"

 

[lmujica]

If you want to check-in a version while in PY, before you must promote the proyect that contains the template (UBE) from 21 to 26.

Regards,



Luis.