T24: Error Message in Version Creation for TELLER

[Jim Myers]

Hi,

I need help

i'm having problems with TELLER...

I'm designing a version for TELLER.

when i commit, an ETEXT pops up right beside AMOUNT.LOCAL.1 saying INVALID FIELD SEQUENCE...

whats the meaning of this and how do i solve it??

-Best Regards


==================
Jim Jerry Myers
Global Solutions Limited.
42, Giffard Road,
Cantoments.

P. O. Box CT-2946
Accra,
Ghana.

Mobile +233 209513888

skype id => jimjerrymyers

==================
Charles M. Schulz  - "All you need is love. But a little chocolate now and then doesn't hurt."

[Santosh]

Hi,

 

This is because the order of creating fields of the version is not proper. Just list out all your fields see its position in I_F.TELLER in GLOBUS.BP you must follow the sequence of the fields. Say for instance in your screen Field No.1,2,3 you are trying to put it in your screen the order of fields must be 1,2, 3 only you can not create the version first 3rd field and then 2nd and then 1st field. After creating the the CORE fields(menas existing in the TELLER application) then you have to start with your LOCAL.REF fields. You can not alter the screen designing first by defining the local reference fields first and then you can not define core fields. I think you are trying to put your local ref fields first and then trying to put some core fields.

 

If still not clear, send me the screen shot of your TELLER version i can point out the error position.

 

Regards,

Santosh

--
Mobile: 973-39406098

[adnan isaac]

--- On Wed, 10/15/08, Santosh <santosh....@gmail.com> wrote: From: Santosh <santosh....@gmail.com> Subject: Re: T24: Error Message in Version Creation for TELLER To: jB...@googlegroups.com Date: Wednesday, October 15, 2008, 10:20 AM Hi Jim, Well try using AMOUNT.LOCAL.1-1 in the version.. as it is an associated field. Regards, Adnan Isaac.

[Saravanan Thangavelu]

Hi,

 

the problem is in teller AMOUNT.1 , AMOUNT.LOCAL.1, AMOUNT.FCY.1, NARRATIVE.1 these fields are assoicated multi values. you may left out any one of these fields. And these fileds should be in order. You check weather all these fields are in your version.

 

And in version the field sequence will not be a problem. you can give the fields in any order. Only thing you have to take care is of the associated fields. Associated fields should be in a set. Hope this will solve your problem.

 

Regards,

Saravanan.

On Wed, Oct 15, 2008 at 1:04 PM, Jim Myers <jimjer...@gmail.com> wrote:

[Harish Venugopal]

Santosh,

       I disagree with your reply. If that is the case, then the very purpose of having a version is lost in the first place. The version to my knowledge, has been designed to give the end user the option and flexibility to have the fields defined as per his wish. There is absolutely no restriction of placing a field in the exact sequence as stated by you depending on the insert file sequences. But however the restrictions are imposed but only for the associated fields to be in the exact sequence as they are defined, which sounds more logical than to have them distributed across the version definition.

 

Jim,

       I request you please provide me the details of the version, to enable me to look into it and come out with a solution or at the least a more appropriate reason for such a error message to be popped out on screen.

 

Rgds,

Harish

Skype : venugopal.harish

[John Watson]

This is not absolutely correct.

The fields can be in any order you like AS LONG AS THEY ARE NOT PART
OF AN ASSOCIATED MULTIVALUE SET

Values in a multivalue set must appear in the correct order or you
will get the mentioned error.

Hence a field order of 44 / 46 / 2 / 7.1 / 8.1 / 9.1 / 65 is correct
but an order of 44 / 46 / 2 / 8.1 / 7.1 / 9.1 / 65 is not.

(assuming fields 7. 8 & 9 are associated)

John.

> Mobile: 973-39406098- Hide quoted text -
>
> - Show quoted text -

[icht...@yahoo.com]

Hi Jim,

Normally you can create fields on versions in any order you like,
unless you are dealing with associated multi-value fields (if you are
using T24 Desktop then they are visually group together with a black
line). These need to be grouped together in a version, in the same
order as they have been created in the core application (E.g. TELLER).
you do not need to include all associated fields, but the ones you
include must be in the correct order.

Hope that helps.

Ryan

[Jim Myers]

Hi,

thanks so much.

I've corrected it.

Its working ok for me now.

-Best Regards


==================
Jim Jerry Myers
Global Solutions Limited.
42, Giffard Road,
Cantoments.

P. O. Box CT-2946
Accra,
Ghana.

Mobile +233 209513888

skype id => jimjerrymyers

==================

Lewis Mumford  - "Our national flower is the concrete cloverleaf."