We just came across a peculiar situation. Recently we had developed a new approach towards developing new applications for Oracle EBS instance.
We do the following
Develop the prototype using developer 6i forms (hacked and patched for Windows 7 & Windows 8). The only change we make with the developer 6i is changing the “coordinate system” property from points to “inches”
This approach gives us rapid development scenarios, as we don’t have to upload the form module to instance top and compile it and try it against the TEST instances.
All we are doing is, once the complete application is tested on developer 6i, a copy of the same opened with Developer 10g forms, and copying the objects following the following sequence
- Window( s )
- Canvases
- Blocks
- Procedures & functions
- Parameters (if any)
Once mapping the PARAMETERS with PROFILE values, the form is ready for APPS instance testing (99% of the times everything is already tested, so a failure is seldom experienced)
Now, coming to one actual issue we are still struggling with is, using the :PARAMETER.xyz, :PARAMETER.abc as initial values for block elements.
The hacked developer 6i does not populate the initial value from :PARAMETER.xyz or :PARAMETER.abc during run time. ie, the first record (record orientation: forms) will not show the already populated values for the columns, however, the very next record(a delete does it) starts showing the :PARAMETER.xyz, abc values being populated to columns wherever they are set as initial values!!!
Do you have solutions? Please let us know with the comment section
Update 19.11.2012
With developer forms 6i, we loaded the values to column through the WHEN-NEW-FORM-INSTANCE like following
:PARAMETER.ORGANIZATION_ID := FND_PROFILE.VALUE(‘org_id’);
:PARAMETER.ORG_ID := FND_PROFILE.VALUE(‘mfg_organization_id’);
:PARAMETER.USERNAME := FND_PROFILE.VALUE(‘username’);
then, explicitly assigned the values to block columns like
:BLOCK.COLUMN1 := :PARAMETER.ORGANIZATION_ID;
in addition to setting up the initial value for the columns using :PARAMETER.xyz
Looks like the stuff are in place now :)
With Developer 10g, this issue has much easier to fix. All we had to do was to change the case of coding like following:
:parameter.organization_id := fnd_profile.value(‘org_id’);
:parameter.org_id := fnd_profile.value(‘mfg_organization_id’);
:parameter.username := fnd_profile.value(‘username’);
To
:PARAMETER.ORGANIZATION_ID := FND_PROFILE.VALUE(‘org_id’);
:PARAMETER.ORG_ID := FND_PROFILE.VALUE(‘mfg_organization_id’);
:PARAMETER.USERNAME := FND_PROFILE.VALUE(‘username’);
and without any further hacks, the 10g forms started showing initial values.
If you experienced the same, have a solution, please provide us the same with the comment section
regards,
admin
