This page (revision-26) was last changed on 21-Dec-2022 09:14 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
26 21-Dec-2022 09:14 10 KB Kevin Higgs to previous
25 26-Nov-2021 10:22 10 KB Kevin Higgs to previous | to last
24 26-Nov-2021 10:22 10 KB Kevin Higgs to previous | to last
23 26-Nov-2021 10:22 9 KB Kevin Higgs to previous | to last
22 26-Nov-2021 10:22 9 KB Kevin Higgs to previous | to last
21 26-Nov-2021 10:22 9 KB Kevin Higgs to previous | to last

Page References

Incoming links Outgoing links
IDIF
IDIF

Version management

Difference between version and

At line 30 changed 2 lines
;[Beginning Position|FIELD_START_BYTE]:This field will be the starting value for the fixed position in the file. If the File Format = 'Fixed Format', you must specify the Beginning and Ending positions. These positions must be continuous without gap, otherwise an error situation will occur. Beginning/Ending positions are not needed for XML and other file formats - the value -1 should be used.
;[Ending Position|FIELD_END_BYTE]:This field will be the ending position for the for the fixed position in the file. If the File Format = 'Fixed Format', you must specify the Beginning and Ending positions. These positions must be continuous without gap, otherwise an error situation will occur. Beginning/Ending positions are not needed for XML and other file formats - the value -1 should be used.
;[XML Tag|XML_TAG]:This optional field is used for XML File Format only. If XML Tag is not specified for XML File, then the Name field is used as XML Tag.
;[Beginning Position|FIELD_START_BYTE]:Used if the File Format is a 'Fixed Format'. The Beginning and Ending positions must be continuous without gap.
;[Ending Position|FIELD_END_BYTE]:If the File Format = 'Fixed Format', you must specify the Beginning and Ending positions. These positions must be continuous without gap, otherwise an error situation will occur. Beginning/Ending positions are not needed for XML and other file format.
At line 44 removed 2 lines
;[XML Tag|XML_TAG]:This optional field is used for XML File Format only. If XML Tag is not specified for XML File, then the Name field is used as XML Tag.
;[Reference Id|REFERENCE_ID]: This field is used in the [UEINH] program. This will contain the ID of the column to be loaded.
At line 60 changed 2 lines
;[Domain|DOMAIN]: This is used by certain pre-loaded programs to further define characteristics and behaviours of a field. This field is not used in [UPPHF], [UEEF], [UPGLF], [LMTD], [LBEN] or [LPTS].
;[Derivation Expression|DERIVATION_EXPRESSION]:This field specifies the derivation expression for the Variable name. Derivation expressions provide the ability to translate values or to retrieve information otherwise not accessible in an interface format in IDIF. Data from within the Personality database may need to be translated to match the requirements from a receiving third party system. Also, data within a source file may need to be translated to match the Personality specifications.
;[Derivation Expression|DERIVATION_EXPRESSION]:This field specifies the derivation expression for the Variable name. Derivation expressions provide the ability to translate values or to retrieve information otherwise not accessible in an interface format in IDIF. Data from within the [{$applicationname}] database may need to be translated to match the requirements from a receiving third party system. Also, data within a source file may need to be translated to match the [{$applicationname}] specifications.
At line 63 removed one line
;[Comments|COMMENTS]: This field can be used to add notes to the actions taking place in the interface. This is an ideal location to add notes on derivation expression set up or vendor notes.
At line 65 removed one line
At line 90 changed one line
This option specifies when an IDIF field value is NULL, how UPGLF returns the field value for the Entire GL File. The value options are listed in the lexicon as shown below.
This option specifies when an IDIF field value is NULL, how UPGLF returns the field value for the Entire GL File
At line 92 removed 4 lines
|__Lexicon__ |__Lexicon Value__
|X_GL_NULLVALUE|00 - Use IDIF Derivation Expression
|X_GL_NULLVALUE|01 - Use NULL for all NULL values
|X_GL_NULLVALUE|02 - Use 1 Space for all NULL values
At line 97 removed 8 lines
!!Usages
Each option has specific usages associated with them. The chart below outlines each lexicon value and their specific usage within IDIF.
|__Lexicon Value__|__Usage__
|00 - Use IDIF Derivation Expression|__A:__ When no Derivation Expression is configured the system uses a space\\__B:__ When Derivation Expression is configured using decode(~,'','NULLVALUE',~) no space is populated.
|01 - Use NULL for all NULL values|All spaces (e.g ' ') are changed to Null values (e.g '') for entire GL unless specified otherwise by using a Derivation Expression, decode(~,'','NULLSPACE',~).
|02 - Use 1 space for all null value is|All fields that have a null value are populated with 1 space. (e.g. ' ' are changed to '') unless specified otherwise by using a Derivation Expression, decode(~,'','NULLVALUE',~).
This page (revision-26) was last changed on 21-Dec-2022 09:14 by Kevin HiggsTop