SS4TechnicalReferenceManual PDF

Infor SunSystems Technical
Reference Guide
Version 4.4.2
Copyright © 2018 Infor
Important Notices
The material contained in this publication (including any supplementary information) constitutes and
contains confidential and proprietary information of Infor.
By gaining access to the attached, you acknowledge and agree that the material (including any
modification, translation or adaptation of the material) and all copyright, trade secrets and all other
right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or
interest in the material (including any modification, translation or adaptation of the material) by virtue
of your review thereof other than the non-exclusive right to use the material solely in connection with
and the furtherance of your license and use of software made available to your company from Infor
pursuant to a separate agreement, the terms of which separate agreement shall govern your use of
this material and all supplemental related materials ("Purpose").
In addition, by accessing the enclosed material, you acknowledge and agree that you are required to
maintain such material in strict confidence and that your use of such material is limited to the
Purpose described above. Although Infor has taken due care to ensure that the material included in
this publication is accurate and complete, Infor cannot warrant that the information contained in this
publication is complete, does not contain typographical or other errors, or will meet your specific
requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or
otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or
omissions in this publication (including any supplementary information), whether such errors or
omissions result from negligence, accident or any other cause.
Without limitation, U.S. export control laws and other applicable export and import laws govern your
use of this material and you will neither export or re-export, directly or indirectly, this material nor any
related materials or supplemental information in violation of such laws, or use such materials for any
purpose prohibited by such laws.
Trademark Acknowledgements
The word and design marks set forth herein are trademarks and/or registered trademarks of Infor
and/or related affiliates and subsidiaries. All rights reserved. All other company, product, trade or
service names referenced may be registered trademarks or trademarks of their respective owners.
Publication Information
Release: SunSystems v4
Publication date: March 6, 2018
Document version: v442
Contents
About this guide ............................................................................................................................. 19

Intended audience ......................................................................................................................... 19
Related documents ........................................................................................................................ 20
Contacting Infor.............................................................................................................................. 20
Chapter 1 System Overview ......................................................................................................... 23
Chapter 2 Naming Conventions ................................................................................................... 29

Source files .................................................................................................................................... 30
Examples ................................................................................................................................. 30
Copy files ....................................................................................................................................... 30
Examples ................................................................................................................................. 31
Compiled program files .................................................................................................................. 31
Examples ................................................................................................................................. 32
System load files ............................................................................................................................ 32
Template file .................................................................................................................................. 32
Examples ................................................................................................................................. 33
Message files ................................................................................................................................. 33
Examples ................................................................................................................................. 33
Layout files ..................................................................................................................................... 33
Report heading files ....................................................................................................................... 34
Example ................................................................................................................................... 34
Run Time License .......................................................................................................................... 34
Indexed and non-indexed temporary work files ............................................................................ 35
Example ................................................................................................................................... 35
Example ................................................................................................................................... 35
Stored print files ............................................................................................................................. 35
Backup files.................................................................................................................................... 36
SunSystems v4 Technical Reference Manual | 3

Contents
Examples ................................................................................................................................. 36

Archive files.................................................................................................................................... 36
Examples ................................................................................................................................. 37
Transfer files .................................................................................................................................. 37
Examples ................................................................................................................................. 37
Audit files ....................................................................................................................................... 38
Examples ................................................................................................................................. 38
Chapter 3 Screens and Menus ..................................................................................................... 39

General format ............................................................................................................................... 39
Screen layout ................................................................................................................................. 40
Numbering of template fields ......................................................................................................... 40
How to use the Template Editor SZTE .......................................................................................... 41
P-Print ............................................................................................................................................ 42
B-Backup ....................................................................................................................................... 42
R-Restore ....................................................................................................................................... 42
N-New ............................................................................................................................................ 44
X-Exit.............................................................................................................................................. 44
D-Delete ......................................................................................................................................... 44
E-Edit ............................................................................................................................................. 45
E-End ............................................................................................................................................. 45
A-Abort ........................................................................................................................................... 45
T-Template..................................................................................................................................... 45
R-Ruler ........................................................................................................................................... 45
I-Ids ................................................................................................................................................ 45
D-Display ....................................................................................................................................... 46
F-Field ............................................................................................................................................ 46
Q-Query ......................................................................................................................................... 47
W-Windows .................................................................................................................................... 48
Edit option S-Selections................................................................................................................. 48
Example ................................................................................................................................... 49
Action numbers .............................................................................................................................. 49
Actions table .................................................................................................................................. 49
4 | SunSystems v4 Technical Reference Manual

Contents
Local actions .................................................................................................................................. 55

Routing selections ......................................................................................................................... 55
Routing Selection Number ...................................................................................................... 55
Routing Selection Mnemonic................................................................................................... 55
Program Id ............................................................................................................................... 55
Permission Type ...................................................................................................................... 56
Action Permission Indicator ..................................................................................................... 56
Process Mode .......................................................................................................................... 56
System Id ................................................................................................................................. 56
Reference Maintenance Record Type .................................................................................... 56
Template Suffix ........................................................................................................................ 56
Module Number ....................................................................................................................... 57
Sub Menu ................................................................................................................................ 57
Permission Slot Number .......................................................................................................... 57
Type of Selection ..................................................................................................................... 57
Menu Number .......................................................................................................................... 57
Sub-Menu Type ....................................................................................................................... 57
Sub-Menu Menu ...................................................................................................................... 57
Other ways to run SZTE ................................................................................................................ 58
Introduction .................................................................................................................................... 58
UI Hint impact ................................................................................................................................ 59
Template targets ............................................................................................................................ 59
Applying UI Hints to the Template File .......................................................................................... 60
Standard Template data practices................................................................................................. 60
UI Hint data principles.................................................................................................................... 60
Backing up UI Hints ....................................................................................................................... 61
Common Return String maintenance ............................................................................................ 61
How to access ......................................................................................................................... 61
How to maintain ....................................................................................................................... 61
Validation limitations ................................................................................................................ 61
Held in Template file (.dat/.idx) as ........................................................................................... 62
Recorded in Template Backup file (.BAK) as .......................................................................... 62
Parsed to the New UI as ......................................................................................................... 62
Common ComboBox content maintenance................................................................................... 62
How to access ......................................................................................................................... 62
How to maintain ....................................................................................................................... 62

Contents

Field associated Hint maintenance................................................................................................ 64
How to access ......................................................................................................................... 64
How to maintain ....................................................................................................................... 64
Held in Template file (.dat/.idx) as: .......................................................................................... 65
Recorded in Template Backup file (.BAK) as: ......................................................................... 65
UI Text String Hint maintenance.................................................................................................... 65
How to access ......................................................................................................................... 66
How to maintain ....................................................................................................................... 66
Hint Error Reporting ....................................................................................................................... 67
Parsed Template data ............................................................................................................. 68
Form/Field Hint/Control qualification Checklist.............................................................................. 69
Modified/New field ................................................................................................................... 69
Calendar Check ....................................................................................................................... 69
CheckBox Check ..................................................................................................................... 69
ComboBox Check .................................................................................................................... 70
Maintenance ............................................................................................................................ 70
Impact on Form Layout .................................................................................................................. 70
Low Risk .................................................................................................................................. 70
Minimal Risk ............................................................................................................................ 70
Translation Considerations ............................................................................................................ 71
Data File Format ............................................................................................................................ 76
Owner ...................................................................................................................................... 76
System ..................................................................................................................................... 76
Function ................................................................................................................................... 77
Action ....................................................................................................................................... 77
Menu Item ................................................................................................................................ 78
XML Schema ................................................................................................................................. 78
MenuIcon Types ............................................................................................................................ 82

Contents
Index of Categories ........................................................................................................................ 82

Menu Tables .................................................................................................................................. 85
Chapter 4 Reference Maintenance ............................................................................................... 89

Record Type Code .................................................................................................................. 90
Template .................................................................................................................................. 90
Routing Parameters................................................................................................................. 90
Layout Definition ...................................................................................................................... 90
Record information ........................................................................................................................ 96
Character ................................................................................................................................. 96
Field information ............................................................................................................................ 96
Character ................................................................................................................................. 96
Type 1 ............................................................................................................................................ 97
Type 2 ............................................................................................................................................ 97
Type 3 ............................................................................................................................................ 98
Type 4 ............................................................................................................................................ 98
Type 5 ............................................................................................................................................ 98
Type 6 ............................................................................................................................................ 99
Report information ......................................................................................................................... 99
Character ................................................................................................................................. 99
Example ................................................................................................................................. 100
Example ................................................................................................................................. 101
Example A) NDF .................................................................................................................... 104
Example B) CDF .................................................................................................................... 104
Introduction .................................................................................................................................. 105
Audit Control flag location ............................................................................................................ 105
AUC Record Layout ..................................................................................................................... 106
AUC Record maintenance ........................................................................................................... 106
AUC flag access .......................................................................................................................... 106
Reference Maintenance Audit Control Function Layout.............................................................. 107
Audit Control flag Copy facility..................................................................................................... 107
Audit Control management checklist ........................................................................................... 107
New AC flag preparation ....................................................................................................... 107
Map new AC flag(s) ............................................................................................................... 108
Test the new AC flag(s) ......................................................................................................... 109

Contents
Add-on Product - Suggested slot assignment/layout format ....................................................... 109
Chapter 5 Printed Output ............................................................................................................ 111
Chapter 6 User Hooks ................................................................................................................. 113

Overview ...................................................................................................................................... 134
Standard User Hook Definition .............................................................................................. 134
Report Definition User Hooks ................................................................................................ 134
Entries – Standard User Hook Definition..................................................................................... 135
Description ............................................................................................................................. 135
Number .................................................................................................................................. 135
User Hook Program ............................................................................................................... 135
Start of Session ..................................................................................................................... 135
Actions ................................................................................................................................... 135
End of Session ...................................................................................................................... 135
Actions ................................................................................................................................... 136
Calling Points 1-4 .................................................................................................................. 136
Actions ................................................................................................................................... 136
Retain in Memory .................................................................................................................. 136
Data Items 1-4 ....................................................................................................................... 136
Values 1-4.............................................................................................................................. 136
Indicators 1-4 ......................................................................................................................... 136
Data Type .............................................................................................................................. 136
Entries – Report Definition user hooks ........................................................................................ 137
Calling Program ..................................................................................................................... 137
Description ............................................................................................................................. 137
Number .................................................................................................................................. 137
User Hook Program ............................................................................................................... 137
Format Code .......................................................................................................................... 137
UHD ....................................................................................................................................... 137
User hook calling points............................................................................................................... 137
Journal Entry - SAJE ............................................................................................................. 137
Journal Import - SATF ........................................................................................................... 138
Sales Order Entry – Header Level - SBTE............................................................................ 138
Sales Order Entry – Detail Level - SBTD .............................................................................. 138
Sales Order Import - SOSI .................................................................................................... 138
SOP Print Invoices - SBPI ..................................................................................................... 139
SOP Print Dispatch Notes - SBPS ........................................................................................ 139

Contents
Purchase Order/Invoice Entry – Header Level - SPPE......................................................... 139

Purchase Order/Invoice Entry – Detail Level - SPPD ........................................................... 139
Purchase Import - SPPI ......................................................................................................... 139
Report Formatter – SSRF ..................................................................................................... 140
Chapter 7 Hidden Functions ....................................................................................................... 141

Import or Export ..................................................................................................................... 141
Transfer Filename ................................................................................................................. 141
Transfer Profile From/To ....................................................................................................... 141
Companion Verification ......................................................................................................... 142
UVRULES Directory .............................................................................................................. 142
Companion Bank Reconciliation ........................................................................................... 143
Database Code ...................................................................................................................... 143
Ledger .................................................................................................................................... 143
Suspense Account................................................................................................................. 143
Backup Directory ................................................................................................................... 143
Ledger Export Set-Up ............................................................................................................ 143
Database Code ...................................................................................................................... 143
Conversion............................................................................................................................. 143
Language Code ..................................................................................................................... 144
Module ................................................................................................................................... 144
Function ................................................................................................................................. 144
Description ............................................................................................................................. 145
Menu Group ........................................................................................................................... 145
Profile Codes 1-20 ................................................................................................................. 145
Transfer ................................................................................................................................. 145
Transfer Screen ........................................................................................................................... 145
Import or Export ..................................................................................................................... 145
Transfer File Name ................................................................................................................ 145
Language Code ..................................................................................................................... 145
Module ................................................................................................................................... 145
Process Transfer ................................................................................................................... 146
Database Code ...................................................................................................................... 146
File Code ............................................................................................................................... 146
Record Type .......................................................................................................................... 146
Record Key ............................................................................................................................ 146
Lock On ................................................................................................................................. 146
Pick ........................................................................................................................................ 152
Keybd ..................................................................................................................................... 152

Contents
Close ...................................................................................................................................... 152

Date ....................................................................................................................................... 152
IR (Item Record) .................................................................................................................... 152
Progs ..................................................................................................................................... 152
Archv (Archive) ...................................................................................................................... 153
Locks ..................................................................................................................................... 153
Sort ........................................................................................................................................ 153
VAT ........................................................................................................................................ 153
Chapter 8 Data Dictionary and Report Definition ..................................................................... 155

Template Id SSRU32 .......................................................................................................... 155
Record Id DDS .................................................................................................................... 155
Language Code ..................................................................................................................... 156
Report Type ........................................................................................................................... 156
System ................................................................................................................................... 156
Description ............................................................................................................................. 156
File Code ............................................................................................................................... 156
Record Type .......................................................................................................................... 156
Occurrence ............................................................................................................................ 156
Record Code.......................................................................................................................... 156
Record Description ................................................................................................................ 157
Template Id SSRU30 .......................................................................................................... 157
Record Id DDR ................................................................................................................... 157
Language Code ..................................................................................................................... 157
File Code ............................................................................................................................... 157
Data Record Type ................................................................................................................. 158
Description ............................................................................................................................. 158
Template Id SSRU28 .......................................................................................................... 158
Record Id DDD ................................................................................................................... 158
File Code ............................................................................................................................... 158
Data Record Type ................................................................................................................. 158
Item Number .......................................................................................................................... 158
Item Name ............................................................................................................................. 158
Entity ID ................................................................................................................................. 158
Offset ..................................................................................................................................... 159
COBOL Name........................................................................................................................ 159
Omit From Query ................................................................................................................... 159
Template Id SSRU29 .......................................................................................................... 159
Record Id DDT .................................................................................................................... 159

Contents
Language Code ..................................................................................................................... 159

File Code ............................................................................................................................... 159
Data Record Type ................................................................................................................. 159
Item Number .......................................................................................................................... 159
Description ............................................................................................................................. 160
Long Heading ........................................................................................................................ 160
Short Heading ........................................................................................................................ 160
Lookup Description ................................................................................................................ 160
Template Id SSRU25 .......................................................................................................... 160
Record Id DDE .................................................................................................................... 160
Database Code ...................................................................................................................... 160
Entity Id .................................................................................................................................. 160
Length on File ........................................................................................................................ 161
Input/Output Length ............................................................................................................... 161
Data Type .............................................................................................................................. 161
Numeric Type ........................................................................................................................ 161
Numeric Sign ......................................................................................................................... 161
Justification ............................................................................................................................ 161
Case Conversion ................................................................................................................... 161
Template Id SSRU26 .......................................................................................................... 162
Record Id DDL .................................................................................................................... 162
Language Code ..................................................................................................................... 162
Entity Id .................................................................................................................................. 162
Description ............................................................................................................................. 162
Long Heading ........................................................................................................................ 162
Short Heading ........................................................................................................................ 162
Template Id SSRU34 .......................................................................................................... 162
Record Id DDF .................................................................................................................... 162
Language Code ..................................................................................................................... 162
Report Type ........................................................................................................................... 163
Sub-Headings and Sub-Footings .......................................................................................... 163
Template Id SSRU27 .......................................................................................................... 163
Record Id DDK .................................................................................................................... 163
File Code ............................................................................................................................... 163
Data Record Type ................................................................................................................. 163
Relationship Number ............................................................................................................. 163
Element Data ......................................................................................................................... 163
File Code ............................................................................................................................... 163

Contents
Record Type .......................................................................................................................... 163

Item Number .......................................................................................................................... 164
Chapter 9 Associating Images with SunSystems v4 Modules ............................................... 165
Chapter 10 Appendix A – SunSystems v4 Data Tables and Files ............................................ 169
Chapter 11 Appendix B - Master Data Files ................................................................................ 173

Description ................................................................................................................................... 173
Summary of record types............................................................................................................. 173
Cobol File Description (FD) ................................................................................................... 173
Reference file record descriptions ............................................................................................... 174
Description ................................................................................................................................... 498
Ledger file record descriptions .................................................................................................... 500
Description ................................................................................................................................... 508
Summary of record types ...................................................................................................... 508
Ledger archive file record ............................................................................................................ 508
Description ................................................................................................................................... 509
Indexing of balance file ................................................................................................................ 509
Cobol File Description ........................................................................................................... 510
Description ................................................................................................................................... 518
Sales Order File record descriptions ........................................................................................... 519
Description ................................................................................................................................... 536
Movement File record descriptions.............................................................................................. 538
Description ................................................................................................................................... 544
Stock Take File record descriptions ............................................................................................ 545
Description ................................................................................................................................... 553

Contents

Purchase Order File record descriptions ..................................................................................... 555
Description ................................................................................................................................... 619
Sales History file record descriptions .......................................................................................... 620
Description ................................................................................................................................... 625
Purchase History file record descriptions .................................................................................... 626
Description ................................................................................................................................... 631
Reference Audit file record descriptions ...................................................................................... 632
Description ................................................................................................................................... 633
Transfer file record descriptions .................................................................................................. 634
Description ................................................................................................................................... 642
Cobol Select...Assign Statement ........................................................................................... 642
Bank Payments file record description ........................................................................................ 643
Description ................................................................................................................................... 645
Description ................................................................................................................................... 657
Journal hold file record descriptions ............................................................................................ 659
Description ................................................................................................................................... 697
Summary of record ...................................................................................................................... 697
Chapter 12 Appendix C – SunSystems v4 Backup Files ........................................................... 719

Contents
Description ................................................................................................................................... 719

Reference backup file record descriptions .................................................................................. 719
Description ................................................................................................................................... 719
Ledger backup file record descriptions........................................................................................ 720
Transaction Backup record .......................................................................................................... 721
Control Backup record ................................................................................................................. 723
Version 4.0 ................................................................................................................................... 724
The Control Backup record .......................................................................................................... 726
Description ................................................................................................................................... 728
Sales order backup file record descriptions ................................................................................ 728
Sales Order/Invoice Header Backup record ................................................................................ 728
Sales Order Detail Backup record ............................................................................................... 731
Sales Order Detail Extra Backup record ..................................................................................... 736
Description ................................................................................................................................... 737
Movement backup file record descriptions .................................................................................. 737
Movement Backup record ............................................................................................................ 738
Description ................................................................................................................................... 741
Stock take backup file record descriptions .................................................................................. 741
Stock Take Header Backup record.............................................................................................. 741
Stock Take Detail Backup record ................................................................................................ 743
Description ................................................................................................................................... 746
Purchase order backup file record descriptions .......................................................................... 746
Purchase Order Header Backup record ...................................................................................... 747
Goods Received Note Header Backup record ............................................................................ 750

Contents
Purchase Invoice Header Backup record .................................................................................... 752

Purchase Order Detail Backup record ......................................................................................... 755
Description ................................................................................................................................... 761
Sales history backup file record descriptions .............................................................................. 761
Sales History Usage Backup record ............................................................................................ 762
Description ................................................................................................................................... 764
Purchase history backup file record descriptions ........................................................................ 764
Balance Backup record................................................................................................................ 764
Description ................................................................................................................................... 767
Journal hold file record descriptions ............................................................................................ 767
Standard Backup record .............................................................................................................. 767
Journal Control Backup record .................................................................................................... 768
Analysis Backup record ............................................................................................................... 773
Transaction Control Backup record ............................................................................................. 774
Transaction Line record ............................................................................................................... 776
Period Backup record .................................................................................................................. 779
Journal Hold Version Backup record ........................................................................................... 780
Journal Hold Control Backup record............................................................................................ 780
Journal Hold Journal Backup record ........................................................................................... 781
Chapter 13 Appendix D – Import Records .................................................................................. 783

Movement Import Batch Control record ...................................................................................... 783
Movement Import Detail record ................................................................................................... 783
Purchase Import Header/Detail/Text records .............................................................................. 786
Purchase Order Entry Header record - OENTH ................................................................... 786
Purchase Order Entry Item Lines - OENTI............................................................................ 790
Order Entry Text Lines - OENTT ........................................................................................... 795
Goods Received Header/Detail records ...................................................................................... 797
GRN Match Item Header - OGRNH ...................................................................................... 797
GRN Match Item Lines - OGRNI ........................................................................................... 798
Purchase Invoice Header/Detail records ..................................................................................... 800

Contents
Invoice Match Item Header - OINVH ..................................................................................... 800

Invoice Match Item Lines - OINVI.......................................................................................... 802
Direct Purchase Import Header/Detail/Text records ................................................................... 806
Direct Invoice Header - DINVH ............................................................................................. 806
Direct Invoice Item Line - DINVI ............................................................................................ 809
Direct Invoice Text Line - DINVT ........................................................................................... 816
Sales Import Batch Control record .............................................................................................. 817
Sales Import Header record ........................................................................................................ 819
Sales Import Detail record ........................................................................................................... 822
Sales Import Description record .................................................................................................. 826
Journal Import record................................................................................................................... 829
Control record ........................................................................................................................ 829
Accounting transaction .......................................................................................................... 830
Chapter 14 Appendix E - Installation File Records for version 4.4 DataLink .......................... 835
ODN records ................................................................................................................................ 835
SUN_DATA definition ............................................................................................................ 835
GDN records ................................................................................................................................ 837
Data and Miscellaneous Restrictions (ACP) ............................................................................... 838
ACP records .......................................................................................................................... 838
Menu Restrictions (OPA, DOP) ................................................................................................... 848
OPA records .......................................................................................................................... 848
SunSystems v4 functions (user input *** in database code)................................................. 850
SunAccount functions (user input – System = “LA”, System Code=”SA”) ............................ 851
Commitment Inquiry .............................................................................................................. 852
Corporate Allocation functions (user input – System = “CO”, System Code=”SC”) ............. 855
Asset Register (user input – System = “AR”, System Code = “SF”) ..................................... 856
Inventory Control (user input – System = “IC”, System Code = “SM”) ................................. 859
Sales Order Processing (user input – System = “SO”, System Code = “SO”) ..................... 860
Purchase Order Processing (user input – System = “PO”, System Code = “SP”) ............... 863
DOP records ................................................................................................................................ 866
Transfer Manager Restrictions (TDA).......................................................................................... 867
TDA record ............................................................................................................................ 867
DAG records ................................................................................................................................ 870
System Code = SS (user input – database code = ***)............................................................... 876
System Code = SA (user input LA) ............................................................................................. 878

Contents
System Code = SC (user input CO) ............................................................................................ 880

System Code = SF (user input AR) ............................................................................................. 882
System Code = SO (user input SO) ............................................................................................ 884
System Code = SP (user input PO) ............................................................................................. 886
System Code = SM (user input IC) .............................................................................................. 888
System Code = SG (user input MM) ........................................................................................... 890
System Code = SX (user input SX) ............................................................................................. 892
Chapter 15 Appendix F – Limits in SunSystems v4 ................................................................... 895

Btrieve .......................................................................................................................................... 896
UNIX............................................................................................................................................. 896
Chapter 16 Appendix G – Process Manager Commands and Call Points ............................... 897

Contents

About this guide
The SunSystems v4 Technical Reference Manual is designed to assist you in the following
ways:
 It explains the internal workings of SunSystems v4, so you can gain an understanding of the
flexibility of the software, and so ensure more efficient trouble shooting
 It explains how to establish interfaces to other systems by reading and writing to backup and
transfer files
 It enables you to customise SunSystems v4, particularly by modifying screens and print
formats, and by storing your own data items on reference files
The manual is written for technical users of SunSystems v4. It assumes familiarity with
standard computing procedures and techniques and uses computer terminology. It covers all
SunSystems v4 hardware environments and operating systems. Where relevant, there are
references to specific hardware environments.
Note: The information in this manual can be used to enhance SunSystems v4. If you
are not careful, the information could also render your system unusable.
Types and versions of COBOL

SunSystems v4 is written in ANSI (American National Standards Institute) COBOL:
 Micro Focus COBOL NetExpress
If you write additional programs to interface directly with SunSystems v4 you must use the
same version of the COBOL language as used by your current version of SunSystems v4.
Please contact your supplier to determine which COBOL version you should use.
Making changes
References are made throughout this manual to ‘making amendments to text files’.
For example:
 To COBOL program source files (see the section Printed Output)
 To backup data files (see the appendices)
 To screen layouts (see the section Screens and Menus).
Changes can be made to text files using any text editor as long as it does not insert special
control characters.
You are advised to document all file amendments. This is not just good practice, it is an
essential source of information if you upgrade to a new version of SunSystems v4, when your
amendments will have to be reapplied.
Intended audience
This document is intended for System Administrators, SunSystems Consultants and Channel
Partner Consultants involved in deploying and maintaining SunSystems.

Related documents
In addition to this Technical Reference Manual, SunSystems v4 is accompanied by the
following. These files, apart from the Help and Technical Reference Manual, are available on
the installation CD, and can also be accessed from the Windows Start menu after installation,
via Programs >> Infor SunSystems v4 >> Online Documentation.
 Readme
 User Note
 Installation Guide
 Upgrade Guide
 Implementation and Appreciation Guide
 Help
An interconnected suite of Help files is provided in HTML Help format. These are structured
as follows:
 SunSystems v4 Basics
 SunSystems v4 Modules
 SunSystems v4 Administration
Note: The table of contents within the Help is designed to mirror SunSystems v4 when
serialised for all modules. As such, the same help topic is displayed by multiple table of
contents entries when the associated function can be launched from multiple module-level
groups. For example, the SunSystems v4 Modules >> SunAccount >> Ledger Accounting >>
Journal Import >> Overview, and the SunSystems v4 Modules >> SunAccount >> Corporate
Allocations >> Journal Import >> Overview table of contents entries, both display the same
topic.
Accessing Help
The Help files are accessed in the following ways:
 From the Start menu, via Programs >> Infor SunSystems v4 >> Online Documentation.
 The main Help file, System Basics, can be accessed from within the application via Help >>
Contents.
 Specific, context sensitive, Help topics can be accessed within a screen or function, via Help
>> Function Help.
Demonstration database
A fully operational demonstration database, in multiple languages, is provided to allow you to
familiarise yourself with the system before using your live database(s). Instructions for
restoring the demonstration database are given in the SunSystems v4 Installation Guide.
Contacting Infor
If you have questions about Infor products, go to the Infor Xtreme Support portal at
www.infor.com/inforxtreme.
If we update this document after the product release, we will post the new version on this
Web site. We recommend that you check this Web site periodically for updated
documentation.

If you have comments about Infor documentation, contact documentation@infor.com.

Chapter 1 System Overview
1
Structure of SunSystems v4
This section describes the structure of SunSystems v4 and the way the system works.
The system may be divided into the following areas:
 The control program
 The kernel programs
 The utility programs
 The application programs.
The following diagrams represent the relationship between these areas.
Kernel programs Utilities Application programs
These programs will be loaded into main A suite of These programs are cancelled on
memory by SSMM. programs program exit. They are not memory
Exceptions are sub-modules not that perform resident.
required in a particular system. miscellaneo
For example: Inventory Movement File us tasks
Handler is not used by Asset Register. throughout
the system.
Control programs
Control programs are the driving programs of the system:
 SunSystems.v4.exe
This displays the SunSystems v4 menu and controls all calls to other functions on that
menu. This is the only program loaded directly from the operating system.

Application programs
There is an application program for each function you can select in SunSystems v4. The
application program is called by the control program. For example, SALR.GNT is the
application program that provides LR=Ledger Revaluation in SunAccount.
The naming conventions for these programs are described in the section Naming
Conventions.
Kernel programs
When an operator invokes SunSystems v4, kernel programs are loaded by the control
program SSMM. They act as service programs to the rest of SunSystems v4. Once loaded,
they remain in memory until SunSystems v4 is closed down.
 The .NET Screen Handler handles user input to the display and acceptance of data within
the SunSystems application.
 The File Handler (SSFH) and its sub-modules control all access to SunSystems v4
permanent data and print files. An access can be any file statement, for example OPEN,
READ ON KEY or START. Though the file handler does not control file access to
temporary, local work files, it can supply a name for these files. Should an error occur
during the processing of such a work file, the file handler can provide a suitable error
message.
 The Report Handler (SSRH) controls production of reports by providing report headings
and report text.
File handler submodules

The File Handler (SSFH) is used for access to all SunSystems v4 permanent data files
and print files. There is a separate file handler module for each type of data file. The file
handler is also used for naming temporary work files, and for formatting standard error
messages:
 The File Handler Common Routines (SSFHCR) is invoked by SSFH when a work filename
is required, an error message is to be formatted, or a file is to be cleared. It is also used to
check that a file or program exists
 Specific File Handler modules (SSFH??) are invoked by SSFH when a program requires
access to one of the SunSystems v4 permanent data files. The module is named
according to the data file it uses. There is one module for each data file. The last two
characters of the module name depend on the data file that the module uses. The
following modules exist:
– SSFHDD Data Dictionary File Handler
– SSFHIN Installation File Handler
– SSFHKF Stock Take File Handler
– SSFHLB Balance File Handler
– SSFHLF Ledger File Handler
– SSFHLH Archive File Handler
– SSFHLP Print File Handler
– SSFHMF Movement File Handler
– SSFHOF Sales Order File Handler
– SSFHPC Purchase Order File Handler (for “C” record types)
– SSFHPF Purchase Order File Handler (for entire P.O.P file)
– SSFHPJ Purchase Order File Handler (for “J” record types)
– SSFHPK Purchase Order File Handler (for “K” record types)
– SSFHPL Purchase Order File Handler (for “L” record types)
– SSFHPM Purchase Order File Handler (for “M” record types)
– SSFHPN Purchase Order File Handler (for “N” record types)

– SSFHPO Purchase Order File Handler (for “O” record types)
– SSFHPP Purchase Order File Handler (for “P” record types)
– SSFHPS Purchase Order File Handler (for “S” record types)
– SSFHQF Journal Hold File Handler
– SSFHRA Reference Audit File Handler
– SSFHRE Report File Handler
– SSFHRF Reference File Handler
– SSFHTR SunBusiness Transfer File Handler
The following file handler modules can only be found in the SQL server version of
SunSystems v4:
– SSFHHF Sales Order History File
– SSFHPY Payment File Handler
– SSFHPU Purchase Order History File Handler
Utility programs
The utility programs perform a number of miscellaneous tasks:
 The Special Functions program (SSSF) controls the CP=Change Printer, CD=Change
Database, and terminal functions. It switches file logging on and off, and performs various
other housekeeping functions. It also validates passwords when logging in and sets up
some system parameters.
 The Reference Maintenance programs (SSRU, SSRR, SSRT and SSRA) control the
updating, reporting, auditing and transfer of master data on the reference file. The
Reference Maintenance section of this manual gives more details on these programs.
 The Report Handling programs (SSRD and SSRF) provide a standard means of report
design and production.
 The Database Management programs (SSFC, SSFB and SSFB??) control the creation,
backup and recovery of files.
 The View Report program (SSVR) enables the operator to look at reports that have been
Stored on Disk, rather than printed directly. See the section View Stored Reports in the
SunAccount and SunBusiness Help.
 The Analysis Category Length program (SSNL) enables the operator to amend the lengths
of analysis codes within database code and category. These lengths are maintained in the
data dictionary.

Naming Conventions
Chapter 2 Naming Conventions

2
File types
Broadly speaking there are two file types:
 Program files that hold instructions or parameters governing the way the system operates.
These files are not updated by SunSystems v4 but have read only access.
 Data files that hold data such as transactions or account details. These files have
read/write access.
Each of these categories can be divided further into the following file types:
SunSystems v4 uses the following types of program files:
 Source files
 Copy files
 Compiled program files
 System load files
 Template file
 Message files
 Layout files
 Report heading files
 Run time system files
 Transfer layout files.
The first two characters of a program file are:
 SA - SunAccount specific programs
 SF - Asset Register specific programs
 SC - Corporate Allocations specific programs
 SO - Sales Order Processing specific programs
 SM - Inventory Control specific programs
 SP - Purchase Order Processing specific programs
 SB - Sales Order Processing, Inventory Control and Purchase Order Processing programs
 SS - SunSystems v4 specific programs
 SZ - Utility programs.
Some ‘SA’ files may also be used by AR=Asset Register and CO=Corporate Allocations.
SunSystems v4 data files can be divided into the following types:
 Permanent indexed files
 Permanent non-indexed files
 Temporary indexed work files
 Temporary non-indexed work files
 Stored print files
 Backup files
 Archive files
 Transfer files
 Audit files
 FreeFormat macro files.

Naming Conventions
Program file naming

Source files
Program source files contain the COBOL code, as written by the authors of SunSystems
v4. These files must be compiled before they can be used to perform their respective
functions.
They are named Sxyyzz.CBL where:
 x is the system from the following list:
– S=SunSystems v4
– A=Ledger Accounting
– F=Asset Register
– C=Corporate Allocations
– O=Sales Order Processing
– M=Inventory Control
– P=Purchase Order Processing
– B=Common to SunBusiness
– Z=SunSystems v4 Utilities.
 yy usually reflects the program function code, for example, SAJL is the program name for
the function JL=Journal Listing.
 zz are optional characters used to distinguish between variants of the same program.
Examples
SAJL.CBL SunAccount Journal Listing
SBIA.CBL SunBusiness Inventory Allocation
SSFH.CBL SunSystems v4 File Handler
SSFBQF.CBL SunSystems v4 Journal Hold File Backup/Restore.
Copy files
Copy files contain COBOL code, which is used throughout SunSystems v4. They can
contain different types of code. For example:
 File Record Layouts
 Standard working-storage section
 Standard linkage section
 Common processing (e.g. date conversion).
Copy files are named Sxcccccc.CPY where:
– S=SunSystems v4
– B=Common to SunBusiness.

Naming Conventions
 cccccc is a meaningful name for the COPY statements contained therein.
Examples
SALBKPRC.CPY Ledger Backup Record Layout
SALDGRRC.CPY Ledger File Record Layout
SAPAYRC.CPY Payment File Record Layout
SFSPRRC.CPY Spread Ratio Reference Record Layout
SFFDRRC.CPY Asset Diary Reference Record Layout
SFFVRRC.CPY Asset Value Reference Record Layout
SMMFBKRC.CPY Inventory Movements Backup Record Layout
SMMFRC.CPY Inventory Movements File Record Layout
SMMVDRC.CPY Movement Definitions Reference Record Layout
SOHFBKRC.CPY SOP History Backup Record Layout
SOHFRC.CPY SOP History File Record Layout
SOMFBKRC.CPY SOP Transactions Backup Record Layout
SOMFRC.CPY SOP Current Data Master File Record Layout
SOOPIRC.CPY SOP Order Detail Presets Reference Record Layout
SPHFBKRC.CPY POP History File Backup Record Layout
SPHFRC.CPY POP History File Record Layout
SPMFBKRC.CPY POP Transactions Backup Record Layout
SPMFRC.CPY POP Current Data Master File Record Layout
SPPUCRC.CPY Unit Conversion Table Reference Record Layout
SSINSRC.CPY Install File Record Layouts
SSANDRC.CPY Analysis Definitions Reference Record Layout.
Compiled program files
The source files are compiled by a COBOL language compiler to produce object files.
Depending on the version of the COBOL language used, the object code may be

Naming Conventions
intermediate code or native code (or Unlinked Object and Linked Object). Native code is
closer to the natural language of the computer hardware, and consequently will run faster.
You will find more details on this subject in the manual for the appropriate COBOL
language.
Compiled program files are named Sxyyzz.ttt where:
– S=SunSystems v4
– B=Common to SunBusiness
– Z=SunSystems v4 Utilities.
 yy usually reflects the program function code, for example, JL=Journal Listing.
 zz are optional characters used to distinguish between variants of the same program.
 ttt will vary according to the COBOL language. For Micro Focus COBOL/2 it is INT for
intermediate code files, and GNT for native code files.
Examples
SAJE.INT SunAccount JE=Journal Entry (intermediate code)
SAJL.GNT Native code version of JL=Journal Listing
SSFBRF.GNT Reference FB=File Backup/Restore native code.
System load files
System load files are invoked when you start to use SunSystems v4. The name depends
on the operating system.
Template file
Templates or screens, that is the screen layouts displayed during the operation of
SunSystems v4, are all stored in the template file. More information on this can be found
in the section Screens and Menus, which also describes how to use the Template Editor
(SZTE) to create and amend screens.
The template file is an indexed sequential file named SS??TMPL.DAT/IDX, though this
will vary according to the operating system being used. ?? represents the language
version where:
 01=English
 33=French
 34=Spanish
 39=Italian
 49=German
 55=Portuguese-Brazilian
 81=Japanese
 86=Chinese Simplified
 87=Chinese Traditional.

Naming Conventions
Each screen in SunSystems v4 has its own template entry in the template file. Individual
templates are named as follows:
Sxyynn where:
– S=SunSystems v4
 yy usually reflects the program function code, for example, JL=Journal Listing.
 nn reflects the template number, which can be any two digit number.
Examples
SSRD38 Report Definition control parameters screen
SALR39 Ledger Revaluation request screen.
Message files
Message files are described in the section Screens and Menus.

They are relative files called SxnnMSSG.MSG where:
– S=SunSystems v4
– A=SunAccount
– B=SunBusiness.
 nn represents the language version where:
– 01=English
– 33=French
– 34=Spanish
– 39=Italian
– 49=German
– 55=Portuguese-Brazilian
– 81=Japanese
– 86=Chinese Simplified
– 87=Chinese Traditional.
Examples
SB33MSSG.MSG SunBusiness French Screen Messages file
SA01MSSG.MSG SunAccount English Screen Messages file.
Layout files
The reference maintenance layout files are described in the section Reference
Maintenance.

Naming Conventions
The reference maintenance layout files define the different reference file record types and
are named as follows:
SxnnRM.LYT where:
– S=SunSystems v4
– 01=English
– 33=French
– 34=Spanish
– 39=Italian
– 49=German
– 81=Japanese
Report heading files
These are named SxnnHEAD where:

 x is the system from the following:
– S=SunSystems v4
– B=Sales Order Processing/Inventory Control.
– 01=English
– 33=French
– 34=Spanish
– 39=Italian
– 49=German
– 81=Japanese
Example
SA01HEAD SunAccount English Report Headings.
Run Time License
The Micro Focus License Manager service is delivered with the application. This enables
execution of the COBOL language code.

Naming Conventions
Data file naming

Indexed and non-indexed temporary work files
Indexed sequential work files are named Sxyy-iii.ttt where:

– S=SunSystems v4
 yy is usually the program function code, for example, JL=Journal Listing.
 iii is the operator Id.
 ttt is DAT for the data file, and IDX for the index file.
Example
SAJL-ABC.DAT Journal Listing Work File for operator ABC.
SAJL-ABC.IDX
Other work files that are not indexed sequential files are named Sxyy-aaa.iii where:
– S=SunSystems v4
 yy is usually the program function code, for example, JL=Journal Listing.
 aaa is the database code, for example, DEM-Demonstration Database.
Example
SOSE-DEM.ABC Sales Entry Work File for operator ABC.
Stored print files
The convention used for stored print filenames is yyiiinnnn.PRN where:

 yy is the program function code, for example, JL=Journal Listing.
 iii is the operator Id (omitted in single user and PC network environments).
 nnnn is an optional four digit number (1-9999), used to establish a unique filename.
It may be necessary to extend the conventions described previously, in order to identify
files more positively. For example, in SunAccount, JL=Journal Listings and FA=Financial
Analysis /FS=Financial Statements have longer filenames to represent the file content
more fully:

Naming Conventions
Print type Single user and PC Multi-user

networks
Ordinary Print yynnnn.PRN yyiiinnnn.PRN
Forced Journal Print JLmmmmm.PRN JLmmmmmiii.PR

N
Financial Analysis/Statement lllllnnnn.PRN llllliiinnnn.PRN
where:
 yy is the menu selection
 nnnn is an optional number to make the filename unique
 mmmmm is the journal number
 lllll is the layout code
In the case of spooled prints, the file naming convention should be as described
previously except the suffix .SPL is used instead of .PRN.
Backup files
The backup versions of all files retain the prefix of the permanent (data) filenames, and
are suffixed with .BAK. Backup files have no indexes, and therefore there is no index file.
These files contain only displayable characters, i.e. numeric fields are not held in any
compressed form.
Examples
SALF-DEM.BAK Ledger backup file
SSRF-DEM.BAK Reference backup file
SSINSTAL.BAK Installation backup file
SSREPORT.BAK Report backup file
Archive files
If Ledger Archiving is set to Y-Yes in LD=Ledger Definition, the SunAccount PC=Period

Cleardown function removes relevant transaction details to an archive file. The
SunAccount archive files are indexed files. They have the same format as the main ledger
file and can be backed up using FB=File Backup/Restore.
The standard name for a SunAccount archive file is SAyy-aaa.DAT (and .IDX) where:
 yy is the year, for example, 10 (for 2010).
 aaa is the database code for example, DEM-Demonstration Database.
By using a concealed system feature, described in the subsection Installation Parameters
in the section Concealed System Features, SunBusiness transactions destined for
deletion at PC=Period Cleardown can also be written to archive files.
The SunBusiness archive files are held in backup format.

Naming Conventions
Examples
SA10aaa.DAT Ledger archive file for 2010
SA10aaa.IDX
SOMHaaa.BAK Sales order archive file
SMMHaaa.BAK Movements archive file
SPMHaaa.BAK Purchase order archive file
Transfer files
The SunBusiness Transfer File (SBF format) for database code aaa has a default name of
SBTR-aaa.DAT. Import files used by the SunAccount JI=Journal Import function can
have any name.
Data files that are output when using particular transfer functions adopt a particular format
and are suffixed according to the output format.
The standard name for the output file, created when using a transfer format in
SunAccount financial reports, is FTlllll.ttt where:
 lllll is the financial statement/analysis/table layout code.
 ttt is the type of format.
The standard name for the output file created when using a transfer format in
SunBusiness reports is TAlllll.ttt where:
 lllll is the Movement/Sales Analysis Layout code.
The standard name for an output file when using reference maintenance Transfer (see the
Reference Maintenance section) is Sxzz-aaa.ttt where:
 x is the system:
– P=Purchase Order Processing.
 zz is the reference maintenance function.
 aaa is the database code.
Examples
SBTR-DEM.DAT SunBusiness transfer data file for demonstration database
DEM
SBTR-DEM.IDX
FTBS.CDF A financial statements transfer file, in this case called

BS,output in comma delimited format for, say, Lotus 1-2-3

Naming Conventions
SACA-DEM.CDF A reference transfer file, created by an export from CA=Chart

of Accounts in Ledger Accounting, comma delimited format
Audit files
Reference audit provides a means of monitoring changes to reference data. The function
AC=Audit Control is used to specify the reference records for which audit trails are
required. Each reference record type has its own audit file, which is created if the audit
flag for that record type is set to Y-Yes.
Amendments, additions and deletions to existing records are logged on the appropriate
audit file. The audit data is held in line sequential format.
Audit files are named SSRA-aaa.ttt where:
 aaa is the database code, which in the case of the Install audit file is INS.
 ttt is the reference record type. See the subsection Standards for Reference Record
Types in the section Reference Maintenance.
Examples
SSRADEM.CAT Calculation table audit file
SSRADEM.ANV Analysis codes audit file
SSRAINS.ODN Operator definitions audit file
SSRAINS.PDN Printer definitions audit file

Chapter 3 Screens and Menus
3
This section describes how to modify and create screens. You may want to do this in the
following circumstances:
 If you are undertaking a translation to another language
 If you have added fields to a data file
 If you simply wish to change the wording on a screen.
In the section System Overview, the screen handler is described as controlling all interfaces
to screens using screen templates. A template defines the layout and contents of each
SunSystems v4 screen. The definition includes the following characteristics:
 The static text that is to be displayed
 The fields into which you will key data
 Certain validation criteria for those fields (e.g. alpha/numeric)
 The attributes of fields (e.g. justification)
 Query details for the fields
 The fields in which the program displays or accepts data
 The position of the fields
 The window definitions for the template (i.e. position, size)
 The valid selections.
The screen handler obeys the instructions coded into a template. The template contains
some validation rules which are used by screen handler; though most validation is done
within the application program after it has called screen handler.
In this section the following areas are covered:
 The rules governing the design of templates
 How the Template Editor (SZTE) may be used to create and change templates
 How to change messages that appear on the screen.
Please note that if you do change templates or messages, you will have to re-apply the
changes to any updated version of SunSystems v4. Therefore, you must document all the
changes you make.
Standards for template design

General format
SunSystems v4 templates are laid out in the following way:
Column 1.....................……………………...............…….....80
(Line 1) DDDDD...DDDDD
************ Page headings (if relevant) ***********
(Line 3-6) -------------------------------------------------------------------------------------
Body of screen

Screens and Menus
(Line 20 last Text Line)
where:
DDDDD... is the Template Description or Heading
Screen layout
The following standards should be observed:

 Never use the top left hand character (Line 1, Col 1 to 3)
 Text on line 1 is always used as the screen-title by screen handler, and the title bar under a
GUI environment. Never define fields on line 1
 If possible leave at least two spaces between a text heading and the field that follows
 Fields should always be aligned as left justified
 Defaults should be aligned as left justified, under the heading ‘Assumption if Blank’
 Line 20 is the last text line
 As far as possible avoid abbreviations in field names, and use capitals for all significant words
 Avoid having a field at the end of a line (in position 80), if the first space on the following line is
used for display of text or data.
Numbering of template fields
Usually there are fields into which the user will key data, and fields in which the program will
display data. Each of these fields must be defined on the template and given a unique
number which should be allocated, wherever possible, in accordance with the following rules:
 Number fields in ascending sequence from left to right and down the screen
 Number fields consecutively, avoiding gaps in the sequence. Note that when initially loading a
template, screen-handler will automatically display consecutive fields on the template until it
finds a gap in the field numbers from field 1 (e.g. 1, 2, 3....N)
 Always use field number 1 for reference maintenance key fields. If you need other fields for
key fields, use field numbers 2, 4, 5...
 Use field number 2 (or the first available field number if more than one key field is present) for
reference maintenance description fields
 Always use field number 3 for reference maintenance Lookup fields
 Do not define fields below line 20
 Do not define a field greater than 149
 Do not define field 80 as this is a special selection field common to all templates.
Grouping of template fields

When numbering, GROUP and SEQUENCE numbers must be added to fields used for input.
By giving several fields the same GROUP NUMBER, they will be accepted from the screen
as a group by screen handler under a GUI environment. In other words, data can be entered
into any of these fields, in any order, using the TAB key or a mouse. SunSystems v4 programs
will not look at the data entered into fields in a group until the user signals that the entire
group is complete (by clicking the OK icon, or ALT F7). SEQUENCE NUMBER defines the
tab-sequence for these fields in a group. Both GROUP and SEQUENCE numbers can by any
numerical value.
 Key fields are usually held as one group or a separate group from the data referenced

Screens and Menus
 Any field which requires an explicit display of data after the group fields have been accepted,
should be at the end of a group
 Any field which causes the application program to alter its processing directly after the field
has been accepted, should be at the end of a group
 It is advisable to increment sequence number in tens to allow for later additional fields.
Template file
All templates are stored on one indexed sequential file called SSnnTMPL.DAT/ IDX, where
nn represents the language code. See the subsection, Program File Naming in the section
Naming Conventions. This file uses ‘data compression’ to save disk space. There are up to
six record types for each template. They are:
 Type ‘S’ records which hold information regarding routing selections
 Type ‘T’ record which holds the static text that is displayed on the screen
 Type ‘Q’ record which holds the Query definitions
 Type ‘P’ record which holds field parameters
 Type ‘A’ record which holds valid Action selection information for the Templates
 Type ‘W’ record that holds any window definitions if they exist for the template
 Type ‘D’ record that holds local action responses and descriptions referenced by action codes
in the 231-250 range (please note that this applies from version 4.1.3 onwards).
This file is indexed by Template Name and Record Type, and is updated using the Template
Editor program described below.
Template Editor
The Template Editor is a program called SZTE which may be used to create, amend,
examine or print SunSystems v4 templates. All SunSystems v4 templates are stored in the
template file. SZTE may also be used to backup/restore a range of templates and to delete
templates from the file.
This section describes how to use SZTE. SZTE is not part of the standard SunSystems v4
issue, but is issued along with other SunSystems v4 SunUtils with this manual. Use of the
wrong version can corrupt files.
The Journal Import template SATF17 is used in the examples which follow.
How to use the Template Editor SZTE
Your screen should be showing the symbol that it is ready to accept commands from you. To
use SZTE, you should enter one of the following:
 SZTE
 RUN SZTE
 Non-English file - SZTE , , nn
 UNIX - szrun SZTE
 VAX - Under OpenVMS, in order to be able to type SZTE at the OpenVMS prompt, it is
necessary to set up a symbol name as follows:
$ SZTE :== “$ $DISK1:(SUN42)SZTE.EXE”
where $DISK1:(SUN42) is the name of the disk/directory where the SunSystems v4
programs reside.
You are asked for the name of the template to be processed. Enter the six-character name of
the required template. See the subsection Program File Naming in the section Naming
Conventions.

Screens and Menus
TEMPLATE FILE NAME (! TO EXIT) _

If the template is found, it is loaded into memory and displayed. If not, you are asked to
confirm that a new template will be created:
TEMPLATE FILE NAME (! TO EXIT) _ NEW FILE? (Y/N)
If the template file itself (SSnnTMPL.DAT/IDX) is not found, you are asked if you would like to
create a new one:
ERROR OPENING TEMPLATE FILE, CREATE NEW ONE (Y/N)?
If you are not sure which template you require, then a listing of available templates may be
obtained by using wildcard characters. The list will also indicate which records exist on each
template. The template name will be displayed with:
 P - if Parameter records exist
 Q - if Query records exist
 S - for Selection records
 T - for Text records
 W - for Window records.
If you suffix the wildcard template name with one of the characters P, Q, S, T or W, then only
the templates that have that record type will be shown. For example, SA????Q will display all
templates that begin with SA and have Query records.
If the wildcard character is suffixed by T, then the listing will include text from the first text line
of the templates.
You are offered a number of options at the bottom of the screen:
P-Print
This option prints the details of the template which is currently loaded. It prints the template
text followed by a list of the actions defined on the template, the field parameters and routing
selections defined (on menus), and then a list of the query window definitions, and window
definitions.
You are asked for the printer device (default LST:), or you may overwrite this with a disk file
name so that the report is Stored on Disk.
B-Backup
This option is used to extract template details to a text file. The format of the backup file is
described below. You are offered different record types to backup, i.e. SELE records, TEXT
records, etc.
R-Restore
This option is used to restore template details from a text file containing records in backup
format (described below). Again you are offered different record types to restore. Note that
existing records for that template are deleted first, before the restore process (for those
record types you have selected) begins.
The format of the backup file is:

Screens and Menus
Bytes 1-8 template name
Bytes 7-8 pop up window number
Byte 9 record type:

S-Selections
T-Text
Q-Query Definitions
A-Actions
D-Local Actions
P-Field Parameters
W-Window Definitions.
Bytes 10-92 backup data as follows:
Record type ‘S’:
Bytes 9-64 SELE data
There will be one selections backup record per SELE (menu routing parameter) defined on
the template.
Record type ‘T’:
Bytes 10-11 text line number
Bytes 12-91 template text
There will be one text backup record per non-blank line of text defined on the template.
Record type ‘A’:
Bytes 10-11 action slot number
Bytes 12-75 8 x actions (each 2 x 4-byte action numbers)
Actions are backed up onto a maximum of eight records which contain eight actions each.
Record type ‘D’: (version 4.1.4 onwards)
Bytes 10-11 First local action slot number of this record
Bytes 12-91 4 x 20-byte local actions, each consisting of response (2 bytes), and
description (18 bytes)
Local actions are backed up onto a maximum of five records, each containing four local
action slots. Although action codes in the range 231-250 may be entered via the template

Screens and Menus
editor currently, their respective local action description records must be entered and
maintained within the backed up version of template using a text editor. In other words, where
a type ‘A’ record contained the action code entries 232 and 234, the type ‘D’ record must be
entered as follows:
SATF17 D02T Local action two F Local action four
where SATF17 represents the template name
‘D’ represents the record type
‘02’ identifies the first record slot as local action 2, the first block of 20
bytes is local action 02 response and description, the second block of 20
bytes is blank as 233 is not used in this example, and the third block of 20
bytes is local action 04 response and description.
Record type ‘P’:
Bytes 1012 field number of the first field on this line
Bytes 13-84 4 x 18-byte field parameters. Each consisting of size (2 bytes),
position (4 bytes), type (1 byte), justification (1 byte), display (1 byte), overlay (1 byte),
group (3 bytes), sequence (5 bytes).
There is one backup record for every four field parameters, with a start-slot-number stored on
each record so that you know which eight field parameters are on the record. The record is
created only if those four parameters exist (as there may be gaps in the fields defined).
Record type ‘Q’:
Bytes 10-71 Query data.
There will be one query backup record per query defined on the template, if query data exists.
Record type ‘W’:
Bytes 1012 Window start slot number
Bytes 13-92 10 x 8-byte windows definitions.
There is one backup record for every ten window definitions, with a start-slot-number stored
on each record so you know which ten are on the record (as there may be gaps in the window
definitions table).
N-New
This option is used to load a different template into memory. You will be asked for the name
of the new template.
X-Exit
This option enables you to exit from template editor, back to the operating system.
Note that the Esc key can also be used here. (On UNIX systems Esc must be entered twice).
OpenVMS uses F11.
D-Delete
Select this option if you want to delete all records for the current template from the template
file.

Screens and Menus
E-Edit
This option enables you to change to the Edit mode, ready for making changes to the
template. The Edit options are displayed at the foot of the screen.
E-End
End returns control to the main template menu, saving the current edited version of the
template, and overwriting any existing previous version.
A-Abort
Abort returns control to the main template menu, without saving any changes you may have
made. Note that the Esc key can also be used here (on UNIX systems Esc must be entered
twice, or F11 on OpenVMS). However Esc will not cause the changes to be lost; if you enter
Edit again, the changes you have made in this run are still held.
T-Template
This option is used for editing the static text. The cursor is placed at column 1 of line 1 and
you may insert, amend, or delete the static text on the screen. In the example above, the
static text includes everything to (but not including) line 22.
A proportional font is used. For this reason, text may not line up. You can use ‘|’ pipes to
ensure that text is aligned when using proportional fonts by placing the pipe before a piece of
text which must be in the same column as the CUI (character) version.
When viewing the template for JL=Journal Listing, SAJL12 in SZTE, notice that characters ‘|’
pipes appear before Entry Period and after Accounting Period.
Because there is only one space between “Entry Period” and “by”, if “Entry Period” is to line
up directly above “Entry Date” and “Accounting Period”, the pipe is necessary when using a
proportional font in the GUI version.
Also, the (A) after Accounting Period does not line up under the (D) after Entry Date.
If there is more than one space between two pieces of defined text on the same line, then
pipes are not necessary. The GUI treats the two pieces of unrelated text separately. Notice
that there is more than one space in front of (E) of Entry Period and the (D) of Entry Date.
Although pipes have been defined on the screen, they are not necessary.
R-Ruler
This option places rulers (graduations) on the screen to help with the positioning of template
text or fields.
I-Ids
Ids displays the field numbers in the screen position for all fields currently defined.

Screens and Menus
D-Display
This option re-displays the template, removing any rulers, Ids etc, that were previously
displayed.
F-Field
This option is used to define a field into which the user will enter data or into which the
program will display data. The rules governing the numbering of fields are given earlier in this
section. Enter the number of the field that you wish to examine, amend or create.
For each field, you are asked for the following:
Position (4 digits)
Respond with position 0000 to erase a field definition.
Otherwise respond in the format llcc where:
 ll is the line number
 cc is the column number.
Size (2 digits)
Respond with the size or length of the field.
Respond with size 00 if you wish the Screen Handler to take no action when asked to
accept or display the field.
Type (1 character)
X for Alphanumeric fields
U for Upper case conversion
P for Passwords (upper case converted)
9 for Numeric fields.
Justification (1 character)
(space) for no justification
L for left justification
R for right justification.
Only available with field type 9:
A for conversion to numeric amount field format as defined in DB=Database
Definitions
0-9 for conversion to 0-9 decimal places with implicit right justification
Z right justified with leading zeros inserted.
Display (1 character)
D for display field
T for display field with template attribute
M for display field with message attribute
(space) for accept field
S to enable an accept field with auto skip. This means that entry on this field ends
when you reach the end of the field, without the necessity to press Enter.
Overlay (1 character)
If this field is a Query field, then an ‘&’ ampersand must be entered in this field.
Group (3 digits)
Any numerical value used to group fields logically.
Sequence (5 digits)
Any numerical value indicating the sequence of fields within a group.

Screens and Menus
When no further fields are required, the field definition process may be terminated by
selecting field number 000.
Q-Query
This option is used to define or amend Query definitions for fields on the current template.
You are asked for the relevant field number, then details concerning the data to be displayed
in the window. You are asked for the following:
File (2 characters)
RF for the Reference File
IN for the Installation File.
Key Position (2 digits)
Specifies the position of the key in the Reference record that is to be selected.
Length (2 digits)
Specifies the length of the key above.
Data 1 Position (3 digits)
Specifies the position in the Reference record of the first Query data to be extracted
and displayed.
Length (2 digits)
Specifies the length of the data above.
Data2 Position (3 digits)
Specifies the position in the Reference record of the second Query data to be
extracted and displayed.
Length (2 digits)
Specifies the length of the data above.
Lookup (1 character, Y or space)
Specifies whether Lookup is available in this Query window.
Key Prefix (3 characters)
Specifies the Reference record type or prefix. You can restrict the Query data that is
displayed by using this Prefix field. For example, in the CA=Chart of Accounts screen
you may use Query in the Analysis codes boxes, but in the Analysis Code 1 box only
A1 data is displayed when Query is selected, whilst if in the box for Analysis Code 2
then only A2 data would be displayed.
This is controlled by setting the Key Prefix to ANVA1 or ANVA2, etc., so you specify
not only the record type but also the specific data type that you require.
Lookup Prefix (3 characters)
Specifies the record type or prefix to be used for the Lookup data in Query. You may
restrict the data selected as described above.
Line (2 digits)
Specifies the line at which the top of the window will appear.
Column (3 digits)
Specifies the column at which the window will begin.
Detail Depth (3 digits)
Specifies the number lines of data that will be shown in the window. Note that there
will be a heading line and two border lines in addition to these, so add three to get the
total window depth.

Screens and Menus
Note: The last three fields will be calculated automatically and can be changed.
However this is not normally necessary, as SZTE works out the optimal size and
position. When changing the depth, ensure that the window does not go below line
24.
You must enter ‘&’ ampersand in the overlay field in the F-Field option for all Query
fields.
W-Windows
This option is used to define or amend a window definition for the current template. There
may be up to 99 windows defined on a template. They are displayed 20 per screen. Enter the
line and column where the window begins, then the height and the width of the window.
Template editor will not allow you to define a window that exceeds line 22 or column 80.
In the SATF17 example, there is one field, number 5, which has a Query definition set up.
This is indicated by the ‘&’ sign next to the field number shown when Iids is selected (see
above).
If F-Field is selected in edit mode, and 005 entered, the following is displayed in place of the
selection lines:
FIELD NUMBER 005 POSN 1940 SIZE 10 TYPE X JUST L DISPLAY OVLY &
This shows that field number 005 is defined at line 19 column 40, is 10 characters long, is
type X (alphanumeric), left justified, and takes the accept field attribute.
If Q-Query is selected, and 005 entered for the field number, then the following is displayed in
place of the selection lines:
FIELD 005 FILE RF KEY POS 004 LEN 10 DATA1 POS 036 LEN 10 DATA2
POS 054 LEN 32
LOOKUP Y KEY PREFIX ACC LOOKUP PREFIX ACC LINE 04 COL 13
DETAIL DEPTH 10
This indicates that there is a Query set up to display data from the reference file (RF), the key
is at character 004 of the reference record and is 10 characters long. The first data field to be
displayed is at character 036 and is 10 characters long.
The second part of the data to be displayed is at character 054 in the reference record and is
32 bytes long. Lookup is available and the reference Record type is ACC, as is the Lookup
record type. The last figures are calculated by SZTE, and specify the position and size of the
window. You may amend these if you want to move the window.
Edit option S-Selections
This option is used to define the valid values that can be entered in the selection box, and to
define what options will be offered to the user at the bottom of a classic screen mode, or in
the pull-down menus displayed in Action mode.
These selections are known as Actions and there may be up to 80 of them defined on each
template. They are entered in five screens of 16 actions each. Gaps are allowed when
creating actions but when saving, the actions will be shuffled up so gaps are removed. The
Action is entered in two parts, as the selection may be done in two parts. The Actions defined
on a template are stored on the template file PARA record for that template.

Screens and Menus
Actions appearing on the same template must have different values, in other words, you
cannot have B-Back and B-Bottom as valid selections on the same template. If it is not
possible to find a word which has a different initial, then a second or subsequent letter of the
word is used.
Example
S-Selections is entered for SATF17.
Enter the value of the action as defined in the ACTION-RESPONSES table. Each action is
two-byte parts. Enter spaces to leave it undefined.
There are only four selections allowed from this template, each is a 1-character selection.
If the action code entry is within the following ranges it is recognised as being in local action:
231-250
481-500
731-750 or
981-999
The text ‘** Local Action **’ will be displayed to the right of the entry field.
The local action response details are undefinable in the ACTION-RESPONSES table. They
are directly linked to the template and are currently to be maintained by the application
programmer as type ‘D’ records in the backed up template file.
Action numbers
The action number is taken from the SunSystems v4 action table listed below, the values of
which are loaded from messages 581 to 620 and 978 to 987 on the SSnnMSSG message file.
Ensure, therefore, that the correct version of the message file is available when defining the
actions in SZTE.
When an action is defined on the template, it means that it will be displayed as a valid
selection by screen handler on the pull-down selections.
Actions can also be defined so that they are hidden i.e., they may be selected on a screen but
are not displayed by screen-handler. If you want to ‘hide’ the option from the screen, then add
250 to the action slot number.
You may create dummy selections by adding 750 to the action slot number. This results in the
Action being displayed on the template but it is ignored by screen-handler’s validation routine.
Actions table
1 ACTION-AMEND
2 ACTION-ANALYSIS
3 ACTION-AMEND-ALLOCATE
4 ACTION-RESTORE-APPEND
5 ACTION-ALLOCATION-RANGE
6 ACTION-ALLOCATION
7 ACTION-AMEND-PRESETS
8 ACTION-BACK
9 ACTION-BACK-BACK
10 ACTION-BACKUP
11 ACTION-BALANCES

Screens and Menus
12 ACTION-BOTTOM
13 ACTION-PERIOD-BALANCES
14 ACTION-TRANSACTION-BALANCES
15 ACTION-CREATE
16 ACTION-CONVERSION
17 ACTION-AMEND-CONSOLIDATION
18 ACTION-CLEAR-REPORT
19 ACTION-CLEAR-JOURNAL
20 ACTION-SCALES-ON
21 ACTION-CREATE-FILES
22 ACTION-CREATE-SUPPRESS
23 ACTION-DELETE
24 ACTION-DESCRIPTION
25 ACTION-DOWN
26 ACTION-PAGE-DOWN
27 ACTION-DATABASE
28 ACTION-TRANS-DATE
29 ACTION-EXAMINE
30 ACTION-EXTRACT
31 ACTION-EXAMINE-FORMAT
32 ACTION-FIRST
33 ACTION-FIRST-FIRST
34 ACTION-FIND
35 ACTION-FORMAT-DETAILS
36 ACTION-FULL-CLEARDOWN
37 ACTION-GENERATE
38 ACTION-HOLD
39 ACTION-TRANSFER-IN
40 ACTION-ITEMS
41 ACTION-BACKUP-INDEXED
42 ACTION-JOURNAL
43 ACTION-JOURNAL-ACCOUNT
44 ACTION-LAST
45 ACTION-LAST-LAST
46 ACTION-LEFT
47 ACTION-MENU
48 ACTION-NEXT
49 ACTION-NEXT-NEXT
40 ACTION-NEXT-ACCOUNT
51 ACTION-NEXT-ASSET
52 ACTION-NEXT-REFERENCE
53 ACTION-OVERLAY
54 ACTION-TRANSFER-OUT
55 ACTION-POST
56 ACTION-PARAMETERS
57 ACTION-PERIOD
58 ACTION-PERIOD-CLEARDOWN
59 ACTION-POST-BATCH

Screens and Menus
60 ACTION-POST-ALLOCATIONS
61 ACTION-SB-DESC
62 ACTION-PRINT
63 ACTION-PROCESS
64 ACTION-PERIOD-RANGE
65 ACTION-POST-JOURNAL
66 ACTION-RESEQUENCE
67 ACTION-QUERY-ITEM
68 ACTION-REPORT
69 ACTION-RELEASE
70 ACTION-RESTORE
71 ACTION-RIGHT
72 ACTION-REFERENCE
73 ACTION-REFERENCE-RANGE
74 ACTION-REFERENCE-AMEND
75 ACTION-START
76 ACTION-SELECT
77 ACTION-SELECTIONS
78 ACTION-START-ACCOUNT
79 ACTION-START-BATCH
80 ACTION-START-CUSTOMER
81 ACTION-START-FORMAT
82 ACTION-START-ITEM
83 ACTION-START-JOURNAL
84 ACTION-START-REPORT
85 ACTION-START-TRANSACTION
86 ACTION-START-ASSET
87 ACTION-START-SUPPLIER
88 ACTION-STORE-ON-DISK
89 ACTION-SPLIT
90 ACTION-ASSET-DETAILS
91 ACTION-TRANSFER
92 ACTION-TOP
93 ACTION-TOTALS
94 ACTION-PROCESS-TRANSFER
95 ACTION-TRANSACTION
96 ACTION-MATCH
97 ACTION-TRANS-DATE-RANGE
98 ACTION-UP
99 ACTION-DUE-DATE
100 ACTION-REPORT-AUDIT-TRAIL
101 ACTION-VIEW
102 ACTION-VIEW-STORED-JOURNALS
103 ACTION-EXIT
104 ACTION-RANGE-ALLOCATE
105 ACTION-YEAR-CLEARDOWN
106 ACTION-HIDDEN-OPTION
107 ACTION-ANALYSIS-CODE-1

Screens and Menus
112 ACTION-VIEW-RIGHT
113 ACTION-OVER-DELIVERY
114 ACTION-FIND-TRANSACTION
115 ACTION-PAGE
116 ACTION-SETUP
117 ACTION-FINISH
118 ACTION-RETURN
119 ACTION-HIDDEN-Z-RELEASE
120 ACTION-SUMMARY
121 ACTION-DATE
122 ACTION-ORDER
123 ACTION-TRANSACTION-TYPE
124 ACTION-CUSTOMER-REF
125 ACTION-RESELECT
126 ACTION-ALLOC-REF
127 ACTION-LINE
128 ACTION-QUALITY
129 ACTION-VALUE
130 ACTION-STATUS
131 ACTION-PAGE-SELECT
132 ACTION-PAGE-RANGE
133 ACTION-SUPPLIER
134 ACTION-SECOND-REF
135 ACTION-POP-AUDIT-REF
136 ACTION-RECALL
137 ACTION-ROUGH
138 ACTION-APPROVE
139 ACTION-CONVERT
140 ACTION-QUOTATION
141 ACTION-Q-REQUEST
142 ACTION-SPLIT-QTY
143 ACTION-SPLIT-VALUE
144 ACTION-TELEPHONE
145 ACTION-ANALYSIS-0
150 ACTION-COPY
151 ACTION-OTHER-OPERATORS
152 ACTION-HOME-KEY
153 ACTION-END-KEY
154 Undefined
155 Undefined

Screens and Menus
156 ACTION-INVOICE
157 ACTION-GRN
158 ACTION-DOUBLE-CLICK
159 ACTION-INQUIRE
160 ACTION-ACCOUNT
161 ACTION-ALLOCATED
162 ACTION-BALANCE
163 ACTION-RETURN-TO-ENTRY
164 ACTION-DETAIL
165 ACTION-ORDERED
166 ACTION-ONLINE-ALLOC
167 ACTION-NEW-FORM
168 ACTION-CLEARDOWN
169 ACTION-SUSPEND
170 ACTION-SAVE
171 ACTION-BASE-AMOUNT
172 ACTION-OTHER-AMOUNT
173 ACTION-ALL
174 ACTION-CLEAR-AUDIT-TRAIL
175 ACTION-OTHER-TOTAL
176 ACTION-CLEAR
177 ACTION-SWAP-WINDOW
178 ACTION-OFF
179 ACTION-BSP
180 ACTION-CALC-CODES
181 ACTION-SEQUENCE
182 ACTION-MISC
183 ACTION-DB-SEQ
184 ACTION-TAX
185 ACTION-AM
186 ACTION-MATHS
187 ACTION-ONLINE-ALL
188 ACTION-OTHER-AMT
189 ACTION-TRANSACTION-PAGE
190 ACTION-SUMMARY-PAGE
191 ACTION-REBUILD-ACB
192 ACTION-EXPIRY-DATE
193 ACTION-COST
194 ACTION-CONV
195 ACTION-TEXT-FIELDS
196 ACTION-AMOUNTS-DATA
197 ACTION-FLAGS-CHECKSUMS
231 ACTION-LOCAL01 (Virtual Slot 231)

Screens and Menus

250 ACTION-LOCAL20 (Virtual Slot 250).
Each action slot may be up to two characters in length, for example, ACTION-CREATE-
SUPPRESS is ‘CS’ (in English).
The second part of the action definition in SZTE is used for overlay processing. This is
required when you wish to have the choice of entering a selection as a two-byte entry, or
entering it as two one-byte entries. An example of this is in AQ=Account Inquiry.
In the details screen, you may select ‘OA’ for Overlay Analysis, or you may enter ‘O’, and
then ‘A’ to achieve the same result. In the latter case, on entering ‘O’, the list of options
changes to the valid Overlay Options.
To define such actions on a template, you must define the first part of the action as usual, but
with zero entered in the second part. Then define another with the same first part, but with a
valid entry in the second part. Define one for each of the possible selections.
The final block of 20 actions, ACTION-LOCAL01 through ACTION-LOCAL20, are maintained
by the screen handler with responses, known as local actions. They are linked directly to the
current template.
The block ACTION-LOCAL01 to ACTION-LOCAL20 is currently using slots 191 through to
210. However, it will always reside in the last 20 slots used in the action table. Therefore, the
next new action will be placed in slot 191, moving ACTION-LOCAL01 to slot 192, etc.
As local actions are not in fixed slots within linkage, the local action responses can only be
referenced by their relative action names. For example, the first local action on the template,
action code 231, is ACTION-LOCAL01 (version 4.1.3 onwards).
Below is an example of how the AQ=Account Inquiry Sequence actions are defined:
First part Second part
0066 Q = Sequence 0000 ZERO
0066 Q = Sequence 0028 D = Transaction Date
0066 Q = Sequence 0028 L = Allocation
0066 Q = Sequence 0057 P = Period
0066 Q = Sequence 0072 R = Reference

Screens and Menus
First part Second part
0066 Q = Sequence 0099 U = Due Date
0066 Q = Sequence 0171 B = Base Amount
0066 Q = Sequence 0171 O = Other Amount
The definition in actions 4 tell screen-handler that it is a two-part selection, because of the
0000 action in the second part. Therefore screen-handler knows that if the user enters only
the first part, then it must accept the second part, displaying the relevant options, before
returning to the application that called it.
Local actions
Developers can add their own local actions. They are considered local because the actions
are template specific. There are 20 slots reserved for local actions, numbered from 231 to
250.
To define these actions enter L=Local on the template edit menu. Then next to each local
action number, enter a one or two character action, and up to 18 characters of description.
Once the local actions have been defined they can then be entered in the selections menu as
normal actions.
Routing selections
If the template you are editing is a menu template, i.e. if the number of the template is 01 (e.g.
SAMM01) then after the actions screens, the routing selections screens will be displayed. This
is where you define routing parameters which are used when calling other programs, and the
options and descriptions that appear on the menu (displayed by screen-handler). There may
be up to 99 routing parameters defined on a template; 20 are displayed per screen. For each
routing parameter, you are asked for the following information:
Routing Selection Number
2 characters
Respond with a number in the range 01 to 99. Respond with 00 or Esc (twice on UNIX
systems) to terminate this routing definition process. If you want to amend or create a number
beyond those shown on the current screen, then enter the number required and the relevant
screen is displayed. Gaps in the routing selection numbers are not allowed.
Routing Selection Mnemonic
normally 2 characters
Respond with a suitable mnemonic.
The next nine fields are entered into one long field entitled Route:
Program Id
4 characters
The name of the program to be called when this route is selected.

Screens and Menus
Permission Type
1 character
This controls the type of permission allowed for a menu option. It is used by the Operator
Permissions program and the menu program SSMM.
 ‘ ’ space indicates that permissions can be set up for all users for this menu entry via Operator
Permissions function
 ‘S’ indicates that this menu selection is only available to the SuperUser and may be subject to
permissions set up via the Operator Permissions function
 ‘N’ indicates that this menu selection is only available to non SUN users and may be subject
to permissions set up via the Operator Permissions function
 ‘A’ indicates that this menu selection is available to all users and cannot have permission
restrictions applied to it via the Operator Permissions function.
Action Permission Indicator

1 character
Enter U so that the routing selection may also set permissions on the actions available to this
process.
Process Mode
1 character
This value is used by the program which is called. It is useful in enabling one program to
handle several routing selections. The called program can then respond differently according
to the process mode associated with the selection. SSMM sets the linkage variable LINK-
PROCESS-MODE to this value before calling the program.
System Id
2 characters
This defines the System which is to receive this routing:
 SA is for Ledger Accounting
 SF is for Asset Register
 SC is for Corporate Allocations
 SO is for Sales Order Processing
 SM is for Inventory Control
 SP is for Purchase Order Processing
 SS is for SunSystems v4
 SX is for SunExtras.
Reference Maintenance Record Type

3 characters
The Reference Id record type to be used on the reference file. This option is used only when
the Program Id is SSRU. A list of these Ids can be found in the section Reference
Maintenance.
Template Suffix
2 digits
This option is used only when the Program Id is SSRU. It identifies the relevant template
associated with the selected reference record type.

Screens and Menus
Module Number
2 digits
The number is for internal use only. It defines the SunSystems v4 module to which the option
is applicable. It must have a value otherwise you will get the message:
SELECTION NOT AVAILABLE
If you are adding new programs to the menu set this to 31.
Sub Menu
1 character
The number is for internal use only. Leave it blank.
Permission Slot Number
2 digits
Indicates the unique slot number in the linkage section containing the permission level for a
menu option. Do not enter a number above 99. If defaulting to the SunSystems v4 permission
i.e. if the permission type is ‘D’, then this must not be greater than 40.
Type of Selection
1 character
Indicates the type of program to be run. Valid entries are:
 E-Entry
 I-Inquiry
 M-Maintenance
 P-Procedure
 R-Report
 S-System, or ‘ ’ space.
This tells screen-handler which heading the option should appear under on the menu. If ‘ ’
space is entered, then it will not be shown but can still be selected in the selection box.
Menu Number
1 digit
Indicates whether the entry should appear on the main menu or sub-menu. Enter 1 for the
main menu, 2 for the sub-menu (usually setup menu), or zero.
Sub-Menu Type
1 character
Indicates the type of sub-menu in which this selection is available. Valid entries are:
 E-Entry
 I-Inquiry
 M-Maintenance
 P-Procedure
 R-Report
 S-System, or ‘ ’ space.
This is normally the same as the selection type above.
Sub-Menu Menu
1 digit

Screens and Menus
This should be zero if the selection is used to select a sub-menu (i.e. SU=Setup), otherwise
blank.
Other ways to run SZTE
There are other ways to execute SZTE. To go directly to the desired template from the
command line enter:
 SZTE SATF17
 SZTE SATF17,, nn (non-English file)
To go directly to the desired template option B for Backup, enter:
 SZTE B
 SZTE B,, nn (non-English file)
Taking the selection on the above screen, number 53, we have the following setup:
 NA - is the mnemonic
 SSRU - is the program that is to be called
 U - is the permission type
 0 - is the process mode
 SA - is the system id
 ADD - is the reference record type
 22 - is the suffix of the template corresponding with that reference record
 24 - is the module number
 space - is the sub-menu number
 13 - is the permission slot number
 M - is the selection type (maintenance)
 1 - is the menu number (main menu)
 space - is the sub-menu type
 space - is the sub-menu menu
 space - is the sub-menu menu
 Names & Addresses - is the description.
SZTE UI Hints
Introduction
This section describes how to modify and create common and template specific UI hints,
which instruct the new UI front end to apply changes to a standard template definition. The
instruction/hint can target an existing label or input field for a location change, it may supply
additional or replacement template text or provide an instruction, with relevant details, to
apply a control to an existing input field.
The Form/Field Hint/Control qualification checklist later in this section, is a summarized aid for
the analysis of new or modified fields and forms with regard to presentation layer
manipulation via hints. However, if you are unfamiliar with UI hint/control concepts,
maintenance processes and tools, please acquaint yourself before attempting to implement
related changes.

Screens and Menus
UI Hint impact
The User Interface (UI) Hint specific modifications to the template file layout and content are
not intended to impact on standard SunSystems v4 processing via the standard screen
presentation layer; the changes should be completely transparent when SunSystems v4 is
accessed via SUN32.exe and its screen handler applications. See Note below.
Only when invoking the new UI front-end, accessed via SunSystems.v4.exe which calls
the parser ResourceAccess.dll to supply template specific information, is the UI Hint
information appended to the standard template data.
The UI Hint specific information is intended to supplement and/or override existing template
details in the template layout translation for the new presentation layer.
Note: Changes to screen text and field positions have been applied directly to the
standard template definitions; however, text hint functionality is still available and may
be required at some point if text is required outside of the legacy screen size limits
(22 rows x 80 columns).
Template targets
The UI Hint specific information is intended to enhance the user experience by targeting text
strings and fields for realignment and/or rephrasing on the translated screen layout and the
fields that are eligible for a control icon attachment or replacement.
For the initial implementation, the following features are included:
Existing Fields:
 can be moved to a new location
 can also have one of the following add-ons applied:
– a Calendar control
– a CheckBox control
– a ComboBox control.
Existing Text can be (see Note below):
 blanked out
 moved to a new location
 replaced by new text:
– at the same location
– at a different location.
New Text can be added at a specified location.
Note: Changes to screen text and field positions have been applied directly to the
standard template definitions; however, text hint functionality is still available and may
be required at some point if text is required outside of the legacy screen size limits
(22 rows x 80 columns).

Screens and Menus
Applying UI Hints to the Template File
As before, the UI Specific Hints can be applied directly to the Template Backup File and
Restored (with no immediate validation, this is not recommended) or via the Template Editor
tool SZTE.
The details documented herein apply to data entry via the development tool SZTE; however,
references are made to the resulting Template Backup File layout and some examples are
given with any layout variations to the parsed data.
Note: SZTE does not, and in most case cannot, supply a visual representation of the
impact of the hints on the template as it does for standard template
entry/maintenance.
Standard Template data practices
Legacy template data storage practices limited the storage of template data in its backed-up
state to 80 bytes plus key information; this presented all of the backup record in a DOS
window.
However, in an attempt to limit the number of records presented in the backup file, the Field,
Action and pop-up window details are held in backup records containing multiple definitions;
the field parameters are held in type ‘P’ records and each record string holds the definition of
up to 4 fields, only the first being identified by its field number, the remainder are implied. For
example, a record headed ‘P011’ contains field parameters for field numbers from 011 to 014.
Standard template data is split into various different record types, for example, ‘T’ for Text, ‘A’
for Actions, ‘W’ for pop-up Windows, ‘Q’ for Query, etc.
UI Hint data principles
Unlike the standard template data split into different record types, all UI Hint data sets are
recognizable by the new record type ‘H’.
Common Hint data sets are recognizable in their backup form by a blank Template Id
followed by record type ‘H’ and an identifier, ‘R’ for return strings or ‘C’ for ComboBox entries.
 Return strings have a unique alpha reference, for example, ‘S’ (reserved by SunSystems for
existing requirements); CheckBox hint references refer to a slot in a common return string
record, for example, S2 refers to the second byte of the returns sting in the common record
headed ‘HRS’.
 ComboBox entry records have references with a unique alpha prefix, for example, ‘S’
(reserved by SunSystems for existing requirements) followed by 3 numeric; ComboBox hints
store this reference as the link to its content, for example, S021 refers of all common records
headed ‘HCS021’.
Field specific Hint data sets are recognisable by the Template Id followed by type ‘H’ and 3
numeric, they imitate the type ‘P’ records, however each record string holds the hints of up to
6 fields. For example, a record headed ‘H060’ contains field Hints for field numbers 060 to
065; this is possible because Hint definitions for ComboBox controls only hold a reference to
its content. CheckBox controls also hold references, however these are held to avoid having
to translate all occurrences of the response; both reference types refer to common hint
records, also a measure adopted to limit the translation requirement.

Screens and Menus
Text String Hint data is recognisable by the Template Id followed by type ‘H’ and an ‘S’, one
record per Text String Hint requirement.
Backing up UI Hints
Selection B-Backup, from the SZTE Main or Template specific menus, does not allow for the
backup of UI Hints to the Template Backup File in isolation:
 The UI Hints are included with the text selection, labelled ‘Backup Text & Hints
(Y/N)?’
 Selection of this option always includes common hints data, but also includes the field
specific hints and UI text hints for the selected template(s).
Hidden selection P-Parser Backup, from the SZTE Main menu, backs up the selected
templates(s) data in the format that it will be parsed to the New UI by the
ResourceAccess.DLL; this backup is for reference and comparison only, any attempt to
restore from this backup will corrupt the actual template data.
Common Return String maintenance
Strings of up to 9 return values that represent the Checked or Unchecked state of a

CheckBox control; each string is identified by a unique character, ‘S’ being reserved for
SunSystems use. The 9 values in the string are referenced by their slot, for example, S1
refers to the first slot in the ‘S’ string, which is ‘Y’; a field hint type 2 links the field to a
CheckBox control, it stores a different return reference for each state.
The same return reference can be linked to many field CheckBox control states.
The limit of 9 return values per return string is more than adequate for SunSystems v4
requirements, considering that the SunSystems v4 reserved return string (Id ‘S’) currently
only recognises return values ‘Y’, ‘N’ or ‘ ‘(space) and that alternative string Ids can be used
by third party developers, therefore an additional 9 per string Id.
How to access
SZTE Main Menu – select hidden option ‘U’
Common Hint Maintenance – by default in mode to ‘** Edit RETURN values **’
 enter the string Id (‘S’ is the default)
How to maintain
String Id ‘S’ is reserved - maintenance of this string is not recommended, any changes impact
the many existing CheckBox controls already referencing its content; however <F10>
overrides and allows access.
A new string Id prompts for confirmation that you wish to create – press <F4>.
When the slot numbers are all displayed:
 identify a slot number (1 to 9)
 add or amend the content – return redisplays all
 select ‘Esc’, then ‘Enter’ to Save the details
Common Hint Maintenance – ‘Esc’ automatically writes changes to file.
Validation limitations
Prevents duplicate return codes in the same returns string.

Screens and Menus
Does not warn if an amended value is already referenced via a CheckBox Hint.
Held in Template file (.dat/.idx) as
A single record – using SunSystems reserve as example
key/content ‘ S000 H00YN ‘ (leading 2 bytes blank)
Recorded in Template Backup file (.BAK) as
A single record – using SunSystems reserve as example
key/content ‘ HRS YN ‘ (leading 8 bytes blank)
Parsed to the New UI as
This record is not parsed to the new UI, however its content is used to substitute the
references in field CheckBox hints.
Common ComboBox content maintenance
A set of up to 90 ComboBox entries, consisting of a Code and Description combination, can

be recorded for each ComboBox reference, each reference prefix character can have up to
999 variations, the ‘S’ prefix is reserved for SunSystems use; a field hint type 1 stores this
reference to link the field to a ComboBox control which presents a drop-down list containing
entries stored under that reference.
The same ComboBox reference can be linked to many field ComboBox controls.
The limit of 90 entries per ComboBox entry set is imposed by the template record size, the
limit of 999 reserved sets (prefixed ‘S’) is considered sufficient for existing SunSystems v4
requirements, particularly considering that alternative prefixes can be used by third party
developers, therefore an additional 999 per unique prefix.
How to access
SZTE Main Menu – select hidden option ‘U’
Common Hint Maintenance:
 select <F2> to switch mode to ‘** Edit COMBO entries **
 enter the reference prefix (‘S’ is the default)
 enter the 3 digit numeric identifier.
How to maintain
References prefixed ‘S’ are reserved – we do not recommend editing these ComboBox
entries. Any changes impact on at least one existing ComboBox control already linked to its
contents; however <F10> overrides and allows access.
An existing reference presents up to the first 20 entries and default the slot prompt for the
next available, a new reference displays the empty set and prompt entry of slot 1.
When the existing entries grid is displayed:
 identify a slot (from 1 to existing definitions+1)
– add a new entry:
 Provide a code, unique to the set, and its description
 Pressing Enter redisplays to include the new slot/details
– amend or delete existing entry:
 <F8> replaces the details in the slot with a <remove from list> marker
 Pressing Enter redisplays to include the edited slot details

Screens and Menus
 <F6> to scroll the display - forward by default, backward having reached the last
 Drill-down feature:
– enter ‘’ as the Code
– identify another Combo reference within <include-annn>, for example, <include-S001>
– Resulting set is not immediately visible, see ‘Parsed to’
 select ‘Esc’, then ‘Enter’ to Save the details
Common Hint Maintenance – Escape automatically writes changes to file.
Prevents entry of duplicate codes in the same entry set
Warns include/drill-down feature only drills down one level (see Note below)
Prevents include/drill-down entry of duplicate references
Prevents include/drill-down entry of itself
Does not warn if any codes in a drill-down entry set are duplicates of the codes in the host
entry set.
Note: The Parser includes entries from the include reference into the host reference,
however any embedded include references will be ignored, for example, in the
following purpose built example:
Field hint TEST01 H00100001S555
Common records HCS555 <include-S666> B B-In host
HCS666 <include-S777> A A-Included
S555 includes code A from S666, yet the S777 include/codes will be ignored,
resulting in Parsed records.
TEST01 H00100001S555
TEST01 HCS555 A A-Included B B-In host

A single record with up to 90 entries – using SunSystems reserve as example:
key/content S010 H00D D-Debtor C C-C…(leading 2 bytes blank)
Multiple records with same key, containing two selections each, therefore up to 45 records
per reference – using SunSystems reserve as example:
key/content
‘ HCS010 D D-Debtor C C-C…‘ (leading 8 bytes blank)
‘ HCS010 T T-Client P P-Profit & Loss…‘ etc.
These records are not parsed to the New UI as common records, however if these records
are referenced via a field ComboBox hint in the template being parsed, they will be parsed as
template specific hint records – using an actual hint as an example:
Field hint ‘SSRU21 H00400001S001’
also parses

Screens and Menus
‘SSRU21 HCS001 D D-Debtor C C-Creditor…’

‘SSRU21 HCS001 T T-Client P P-Profit & Loss‘ etc.
Note: For predictive result set generation, select hidden option ‘P’ from SZTE Main
Menu - this produces a file (default PARSER.TST) that imitates the data construction
process, in ResourceAccess.cbl, prior to Parsing a template string to the new UI.
Field associated Hint maintenance
Although fields cannot be introduced to the template via a UI Hint, any existing fields can
have hints applied to them; field related hints are limited to relocation and/or the application of
one of a selection of control add-on’s.
There is a limit of 149 field related Hint definitions per template, the same legacy limit
imposed on field P-Parameter definitions.
How to access
SZTE Template Edit Menu:
 Select a Template from the Main Menu and option E-Edit
 It may be advantageous to select I-Ids and R-Ruler (line and column) options at this point
 select hidden option ‘U’
Field Hint Maintenance:
 enter the existing 3 digit field number.
How to maintain
The selected field’s current/defined position is displayed:
 if a change of location is required on the new UI presentation, enter a new coordinate
 if an UI control add-on is required, select its numeric Id from the list displayed:
– If type 1 ‘ComboBox Hint’ is selected:
 Identify an existing ‘Common Combo Set Id’, for example, ‘S001’
– If type 2 ‘CheckBox Hint’ is selected:
 Identify the Checked state Return Reference, for example, ‘S1’
 Identify the Unchecked state Return Reference, for example, ‘S2’
– If type 3 ‘Calendar Hint’ is selected – no further detail required
 select ‘Enter’ to Save the details.
Amend field Hints
 Re-enter the field Id
 Override the relocation coordinate and/or type Id (and its related reference(s)).
Delete field Hints
 Re-enter the field Id
 Set the relocation coordinate and type Id to zeros (0000 and 0)
SZTE Template Edit Menu – E-End will automatically write changes to file.
Only allows hints to be applied to an existing field number.
Does not allow 00 as row or column in a new location coordinate.
Only allows selection of valid ComboBox references and CheckBox return references.
Does not:

Screens and Menus
 validate location of new coordinates supplied

 prevent a clash with a field already assigned a Query – new UI ignores the hint
 validate the suitability of the field to control type link
 validate the controls values against the field requirement.
Held in Template file (.dat/.idx) as:

A single string within the existing record type ‘T’, replacing trailing filler – using actual hints as
an example:
Area content
‘ 00002S1S2 00003 00003.. ‘ (leading 11 bytes blank)
All field numbers are implied, this shows that fields 1 and 3 are not defined.
Recorded in Template Backup file (.BAK) as:
Multiple records with key identifying leading field number, containing up to 6 hint definitions
each, therefore up to 25 records per template – using actual hints as an example..
key/content ‘SADB25 H00200002S1S2 00003 00003..’
Leading field number is 2, remainder are implied, this shows that field 3 is not defined.
These records are parsed in a similar format to those held in the backup file, with the
following exceptions:
 the CheckBox hint references are substituted with values from the referenced return string –
using the hint above as an example:
key/content ‘SADB25 H00200002YN 00003 00003..’
Note: Space values are represented as ‘_’.
 The ComboBox hint references are accompanied by the content of the referenced common
records - using an actual hint as an example:
Field hint ‘SAAL04 H04000001S024’
also parses
‘SAAL04 HCS024 Y Y-Yes N N-No’
‘SAAL04 HCS024 R R-Rough only ‘
Note: For predictive result set generation, select hidden option ‘P’ from SZTE Main
Menu - this produces a file (default PARSER.TST) that imitates the data construction
process, in ResourceAccess.cbl, prior to Parsing a template string to the new UI.
UI Text String Hint maintenance
The UI Text Hint maintenance definitions allow for the removal, relocation or replacement of
existing template text strings or the inclusion of new UI only text strings.
Although the maintenance options for all of these variations have been retained, the decision
to drop SUN32.exe means that all changes to template layouts were carried out directly on
the templates ‘T’ext records for SunSystems v4 version 4.4, the removal and replacement
options effectively became redundant; however, if the decision is made to cross the current
legacy 22 row & 80 column boundaries, the Relocation text hints and the New text hints will
be required due to the inherent SZTE/‘T’ext record standard text limitation.

Screens and Menus
There is an adequate limit of 440 UI Text Hint definitions per template, a limit imposed by the
key definition.
How to access
SZTE Template Edit Menu –
 Select a Template from the Main Menu and option E-Edit
 It may be advantageous to select I-Ids and R-Ruler (line and column) options at this point
 select hidden option ‘U’.
Field Hint Maintenance –
 leave the 3 digit field number as 000.
How to maintain
The UI Text Hint is composed of three data sets; application of the hint depends on which of
the three data sets have been provided.
Add new UI only text string:
 First data set, ‘current location and length of text string’ – leave as 0000 and 00
 Second data set, ‘location for new text’ – must be entered
 Third data set, ‘new text string’ – must be entered. As standard, new text strings should be
limited to a maximum of 50 of the available 65 bytes; this allows for a 30% text increase
during translation.
Removal, Relocation or Replacement of existing template text strings:
 First data set, ‘current location and length of text string’:
– When relocating an existing text string, supply a string length increased by 30% to allow
for the potential increase during translation, e.g. for 20 bytes of text set the length to 26.
– These options all require the entry of these details, having entered them, the target text
string is displayed for confirmation.
Note: Relocation and Replacement coordinates must target the first byte of a text
string, otherwise the UI Client ignores the hint (although it will report it, see ‘Hint Error
Reporting’), only the redundant removal/clearance hint can provide a location mid
text, because the hint is handled in advance by the parser.
 Second data set, ‘new location for text’:
– Ignore/leave 0000 in this field to:
 Remove existing text – leave the new text string (3rd data set) blank (Redundant
option)
 Replace existing text at same coordinate – enter 1 to 32 characters of new text string
(3rd data set) (Redundant option)
– Supply a new coordinate to:
 Relocate existing text – leave the new text string (3rd data set) blank. When relocating
an existing text string, supply a string length increased by 30% to allow for the
potential increase during translation, e.g. for 20 bytes of text set the length to 26.
 Replace existing text at the new coordinate – enter 1 to 32 characters of new text
string (3rd data set) (Redundant option)
Amend UI Text Hints:
 Existing data manipulation – re-enter/identify the location in the first data set
 UI only text string – re-enter/identify the location in the second data set
Delete UI Text Hints:
 Existing data manipulation:

Screens and Menus
– re-enter/identify the location in the first data set

– from text string (third data set), select F8
 UI only text string:
– re-enter/identify the location in the second data set
– from text string (third data set), select F8
SZTE Template Edit Menu – ‘E’nd automatically writes changes to file.
Does not allow 00 as row or column in a location/coordinate.
Warns the user if an existing text coordinate does not target the first byte of a text string.
Only allows the data set entry combinations detailed above.
Prevents entry of multiple spaces within the text string (otherwise it would be truncated).
Does not:
 prevent a mid-text string coordinate being applied to a Relocation or Replacement hint.
 validate for text positional overlaps.
 check compliance with new text length restrictions or existing text length definitions for
translation purposes.
 Limit entry to 440 Text String Hints per template; if this limit is exceeded, the excess will be
lost without warning.

Up to 99 records containing up to 44 UI Text Hints each – using actual hints as an example:
key/content ‘SSRU21 H010602220000Account Type...’
Templates first record – instructs text at 0602, 22 bytes, to be replaced by ‘Account Type’
A single record per UI Text Hint, therefore up to 4356, all with the same key – using actual
hint as an example..
key/content ‘SSRU21 HS0602220000Account Type’
These records are parsed in the same format as those held in the backup file.
Hint Error Reporting
The data in a Hint definition may not be subjected to any form of validation until it is presented
to the UI Client via the parser.
UI Hints added via the backup file bypass validation completely.
Although SZTE provides validation for Hint data setup against host fields or text, the reverse
is not true, consequently any adjustments to the host field or text string can sever links with UI
Hints or invalidate its content. This may occur while bug fixing or during a translation phase;
SZTE is also incapable of validating the content of ComboBoxes or the return values of
CheckBoxes.
To counter the problem of overlooking incomplete, detached or invalid hints, a switchable
registry setting prompts the UI Client to inform the user when an UI Hint cannot be processed,
and when the hint content conflicts with the requirements of the associated application.

Screens and Menus
Note: This function does not report consistently, and is therefore targeted for further
development in a later version of SunSystems v4.
To switch Hint Error reporting ON:
To override the registry setting’s installed/default state
Start > Run ‘regedit’ and locate the registry key
HKEY_CURRENT_USER\Software\SunSystems\4.4\UISettings
Set the ‘HintErrorReport’ REG_DWORD value (Right-click > Modify) to 1
If you intend to switch this registry setting regularly, create your own .reg files:.
Start > Run ‘regedit’ and locate the registry key
HKEY_CURRENT_USER\Software\SunSystems\4.4\UISettings
Right-click the ‘UISettings’ registry folder > Export and name, for example,
HintErrorReport_OFF.reg
Copy HintErrorReport_OFF.reg to HintErrorReport_ON.reg
Edit HintErrorReport_ON.reg, changing "HintErrorReport"=dword:00000000 to
00000001
Double-click the appropriate .reg file to set/reset the registry setting.
Parsed Template data
Template data is generally parsed in the same format as that held in the backup file, with the
following variations:
1. Field hint type 1 (ComboBox) references are accompanied by converted common record
Combo Set contents.
2. Field hint type 2 (CheckBox) references are substituted by their referenced common record
return values (space values are represented as ‘_’).
3. Type ‘T’ext records are edited in advance to satisfy the UI Text String clearance hint
requirements (blanking out of existing text only) and the hint is suppressed from the transfer of
data.
4. all records are strung together to form a single parsed record/string.
5. all hints related data is parsed at the end of the record/string.
The SZTE Main Menu hidden option P-Parser Backup simulates the types and format of the
hint data being parsed with standard template data to the New UI, however the results do not
match points 3, 4, and 5 above; see the sections entitled Parsed to the New UI as, and the
example extract below:
The ‘Maintain Analysis Codes’ template SARU23 hints...
SARU23 H00700002S1S3 00001S033 00002S1S3
Referencing translated Common hint records…
HRS YN
HCS033 <include-S001> C C-Combined
HCS001 Y Y-Yes N N-No
Are constructed and presented as…
SARU23 H00700002Y_ 00001S033 00002Y_
SARU23 HCS033 Y Y-Yes N N-No
SARU23 HCS033 C C-Combined

Screens and Menus
To simulate the data being Parsed to the New UI, please note:
 The field 7 & 11 CheckBox(code’2’) hints, with S1 & S3 references replaced by ‘Y’ & ‘_’
(representing space) from the translated common returns records.
 The field 10 ComboBox(code’1’) hint related template specific S033 entries, constructed from
translated common ComboBox content records S001 & S033 in accordance with the ‘include’
instruction.
Form/Field Hint/Control qualification Checklist
The Form/Field Hint/Control qualification Checklist is intended to be a quick reference to aid

identification of elements of screens that qualify for the application of New UI Hints to
enhance the presentation in line with the new standard for SunSystems v4 version 4.4
onwards.
When you have identified the elements requiring a control or textual changes, the methods of
applying them can be found in the preceding sections.
Follow the narrative from Modified/New field, drop through the instructions until you are
directed otherwise; if you are applying hints to an existing form for the first time treat it as a
series of new fields.
Qualification to apply a control could impact on the form layout, consequently, you may also
need to follow the Impact on Form Layout section.
Modified/New field
Does the subject field reference variable (user defined) data?
 Yes – it qualifies for a Query, not UI hint related. Exit the Checklist.
Is the subject field a 10 byte Date field?
 Yes – it potentially qualifies for Calendar hint/control. Go to Calendar Check.
Is the subject field more than 3 bytes in length?
 Yes – it cannot qualify for any other New UI hint/control. Exit the Checklist.
Is the subject field 1 byte in length?
 Yes – it potentially qualifies for CheckBox hint/control. Go to CheckBox Check.
 No – it potentially qualifies for ComboBox hint/control. Go to ComboBox Check.
Calendar Check
Does the date field already have a hint/control applied?
 No.
– Is the date field Display only or attached to a Presets form?
– Yes – Does not qualify. Exit the Checklist.
– No – Qualifies for a Calendar control/hint. Go to Maintenance.
 Yes.
– Is the existing hint/control a Calendar hint/control?
– No – Remove the inappropriate control/hint. See Maintenance, then restart check.
– Yes – Is the date field Display only or attached to a Presets form?
 No – Existing hint/control is correct. Exit the Checklist.
 Yes – Remove the inappropriate control/hint. Go to Maintenance.
CheckBox Check
Does this 1 Byte field only accept a combination of ‘Y’ and ‘N’ or ‘Y’ and ‘ ‘(Space)?
 No – It potentially qualifies for ComboBox hint/control. Go to ComboBox Check.

Screens and Menus
 Yes.
– Does this 1 Byte field already have a hint/control applied?
– No – Qualifies for a CheckBox control/hint. Go to Maintenance.
– Yes.
 Does the existing hint define a CheckBox control?
 No – Remove the inappropriate control/hint. See Maintenance, then restart check.
 Yes - Does the hint represent the correct state return combination?
i. Yes – Existing CheckBox hint/control is correct. Exit the Checklist.
ii. No – Adjust the existing CheckBox control/hint. Go to Maintenance.
ComboBox Check
Does this 1-3 Byte field already have a hint/control applied?
 No – Qualifies for a ComboBox control/hint. Go to Maintenance.
 Yes.
– Does the existing hint define a ComboBox control?
– No – Remove the inappropriate control/hint. See Maintenance, then restart check.
– Yes - Does the ComboBox hint reference the correct content records?
 Yes – Existing ComboBox hint/control is correct. Exit the Checklist.
 No – Adjust the existing ComboBox control/hint. Go to Maintenance.
Maintenance
If the Maintenance instruction is to:
 ‘remove the inappropriate control/hint’ - follow the ‘Delete Field hints’ instruction in section
‘Field associated Hint maintenance’.
 ‘qualifies for a Calendar (or Checkbox or ComboBox) control/hint’ - follow the ‘How to
Maintain’ instruction in section ‘Field associated Hint maintenance’. Finally, check for any
impact on the screen/form layout.
 ‘adjust the existing Checkbox (or ComboBox) control/hint’ - follow the ‘Amend Field hints’
instruction in section ‘Field associated Hint maintenance’. Finally, check for any impact on the
screen/form layout.
Impact on Form Layout
If you have added or adjusted a hint, the end result will have an impact on the layout of the
screen/form; the degree of impact varies depending on the type of hint/control and how busy
the host screen/form already is.
The following is an assessment of the risk levels and some of the options that can be
considered when attempting to resolve the layout impact.
Low Risk
If applying or adjusting the return values of a CheckBox hint, the control currently has less of
an impact on the layout than its host 1 byte field; this may change if a description is
introduced to the control.
Minimal Risk
If applying a Calendar hint and the screen/form is busy (more than two columns of
input/display fields and their labels), there is a minimal risk because the total length of the
field and its control icon is greater than its host 10 byte field.

Screens and Menus
If the control impacts on a label or field or control immediately to its right in the layout, you
may have to consider adjusting one or more column positions (all labels or fields in the
column) while attempting to maintain the equilibrium/positional balance.
High Risk.
If applying a ComboBox hint and the screen/form is relatively busy (more than one column of
input/display fields and their labels), there is a high risk of impact because the control,
replacing the 1-3 byte field, includes a description of the 1-3 byte code and therefore
potentially extends the area of occupation by approximately 7000% (1 byte field becomes
control containing up-to 65 bytes of text and a drop-down icon).
If the control impacts on labels and/or fields and/or other controls to its right in the layout, you
have several options, however the solution should where possible maintain consistency with
other similar forms, therefore refer to it/them in advance of implementing one of the following
solutions:
 Adjust one or more column positions (all labels or fields in the column) while attempting to
maintain the equilibrium/positional balance in the layout, for example, IC/MD; had to remove
bracketed label extensions to achieve this.
 Reduce the length of the code related descriptions, however, this will only be a viable option if
the end result remains descriptive enough to meet its objective; better to force the user to
seek an explanation from the Online Help rather than confuse, for example, LA/LD; removed
‘Category’ from descriptions to avoid multiple column adjustments.
 Present the ComboBox control with only the code in the description; the drop-down will
provide a list of valid codes, but will force the user to seek an explanation from the Online
Help, for example, LA/TM; both Selections and Match Criteria had negative right-hand impact.
 Remove the control/hint to revert to an alphanumeric or numeric input field; this should be a
last resort, but may be necessary in particularly busy forms, for example, SO/LI; this form has
11 columns (most qualifying for controls) repeated on 10 rows.
 Combination of two or more of the solutions detailed above.
Translation Considerations
The new UI Hint related template data is partially subject to translation.

Measures have been taken to reduce the translation requirements by keeping the UI Hint
footprint as minimal as is possible; this includes:
 Only defining CheckBox return values once, all CheckBox controls reference a value in
common data set(s), consequently only the common records require translation. See the
section Common Return String Maintenance for further details.
 Only defining ComboBox contents once, all ComboBox controls reference common data
set(s) comprised of Code and Description combinations, the data set itself can include the
content of another data set, further reducing the footprint, consequently only the common
record codes and their descriptions require translation.
 If an existing text string only requires relocation, this can be specified via an UI Text String hint
without repeating the text and duplicating translation requirement.
The following text visits each UI Hint record type in the order that a translator will encounter
them in the backed up version of the template file SSnnTMPLT.BAK.
Record Type UI common CheckBox return value record (with eight preceding spaces).
Presented as HRS YN

Screens and Menus
Overview The translator is only likely to encounter one record of this type; the
content is unlikely to change, only three values are currently set, ‘Y’
(RESPONSE-YES), ‘N’ (RESPONSE-NO) and ‘ ‘ (space). These return
values reflect the nature of a CheckBox control and meet the requirement
for the fields linked to CheckBox controls.
Translation Key information ( HRS) is not to be translated.

The remainder of the record is a 9 byte block of single byte characters,
which are referenced as S1 to S9, these are subject to translation as
indicated above.
Control links Identifying the controls that reference a particular return value is unlikely
to be necessary, however if required, the easiest method is to search for
the return values specific reference, for example, ‘N’s reference S2, this
will not provide an exclusive search, but if the result is linked to a Field
Hint record with the CheckBox control Id ‘2’ it will provide a field number
reference, the following is an good example, although not a true hint
setup:
SAGP09 H00300002S1S2 00002S2S3
This indicates that on form SAGP09, field 3 has a CheckBox control with
‘N’ as its Unchecked value, and field 4 has a CheckBox control with ‘N’
as its Checked value.
Other results should be ignored, for example, SAAR21 HS2024050000
is an UI Text String Hint.
Record Type UI common ComboBox content records (with eight preceding spaces).
Presented as HCS007 D D-Entry Date T T-Transaction Date

HCS007 J J-Journal
Overview The translator will encounter many records of this type; multiple records
per reference, for example, two records for S007 above, and for many
references, for example, S001 through S164 represent the requirement
at the first stage of UI Hint development, with S901 and beyond
represented those content records reused (included) time and again.
Translation Key information ( HCS007) is not to be translated, nor embedded

include references, for example, <include-S010>.
Most of the remaining combinations of a 3 byte Code with a 32 byte
Description require translation, with the exception of numeric codes and
some literals e.g. Ledger/Budget codes.

Screens and Menus
Where possible translations should be limited to 130% of the original text

string; screen displays were only reworked to allow for a 30% expansion
of the ComboBox control.
Where translations cannot be limited to 130% of the original text string
and the increase negatively impacts the screen layout, Code only
translations should be considered or a Jira request to adjust the screen
layout submitted
Context These Code and Description combination data sets were set up based on
the English requirement, many references are only used once, see
Control Links to verify its source, therefore translation can be based on
the source functions error messages (Code values) and Help text
(Descriptions), however it is possible that the reference is used in
multiple functions and if the translation for one function is inappropriate
for another, the translator will have to consider an alternative method,
see re-referencing.
Control links Identifying the controls that reference a particular ComboBox reference is
simple, combining the ComboBox control Id ‘1’ with the reference will
usually reveal only the Field Hints associated with that reference, for
example, a search for ‘1S007’ only returns one result SAJE33
H01100001S007, indicating that the ControlBox content is only used by
form SAJE33’s field 11.
Re-referencing Where the ComboBox reference is used by multiple form sources and the
initial translation does not satisfy one or more of the fields referencing it,
alternative ComboBox reference(s) must be setup and referenced by the
appropriate field hints.
ComboBox references prefixed ‘S’ are reserved for SunSystems,
however to avoid claiming a reference that may be used by the English
version at a later date, an alternative, for example, ‘T’ranslation, would be
a safer option; there is of course the potential to clash with a third party
developer, therefore if you know of one that generally uses ‘T’ as his
unique identifier that works with a company using the language in
question, it would be advisable to use an alternative.
Cross referencing content is not a problem, therefore if you are
developing an alternative, for example, T001, yet you wish to include the
content of an already translated reference, for example, S007, you may
still do so using <include-S007>.
Record Type UI Field Hint records.
Presented as SAAR21 H05400002S1S2 00001S008 00003 12240

Screens and Menus
Overview The translator will encounter many records of this type; however, the field
hints are designed to contain only co-ordinates and references prefixed
by Ids that are not subject to translation, for example, SunSystems
reserved ‘S’, consequently they do not require direct translation.
The example shown above is not an actual hint record, yet it
demonstrates most variations that may be encountered.
Translation UI Field Hints are not subject to translation.
Record Type UI Text String Hint records
Presented as SARU58 HS0515110000

SARU58 HS0703310743
SARU58 HS1103191112 Last Proc.date label (9 to right)
SARU58 HS0000002103 additional UI only text.
Overview Although two of the above are hints designed to test the UI Client, the
records show all text string hint variations:
The first is a Clearance hint, which identifies an existing text string by its
location and length as presented on the ‘T’ext record, the zeros and
spaces indicate that is not to be relocated or replaced by alternative text
(redundant option).
The second is a Relocation hint, which identifies an existing text string by
its location and length as presented on the ‘T’ext record and a new
position at which the existing string is to be placed, the spaces indicate
that it is not to be replaced by alternative text.
The third is a Replacement hint, which identifies an existing text string by
its location and length as presented on the ‘T’ext record and the new
position at which the alternative text string is to be placed; if the new
location is set to zeros, the alternative text string is placed at the original
coordinate (redundant option).
A New Text hint, with the existing text string location and length set to
zeros, it specifies a location for the new text string.
Translation Direct translation of the text string in hint type 4 should be the only
requirement; translation considerations should have been made during
development as follows:
Type 2 - Relocations should have specified a text length that allows for a
30% increase during translation.

Screens and Menus
Type 4 - New text hints should be limited to a maximum of 50 bytes of

text to allow for a 30% increase during translation.
Additional menus API – third party installer

You can add menus to SunSystems v4 for new functions and actions, or for existing functions
and actions, by using the .NET assembly Infor.SunSystems.AdditionalMenus.dll and the
application ThirdPartyInstaller.exe, as detailed below.
Note: This tool cannot modify existing menus delivered with SunSystems v4, or
export installed menus.
1. Prepare the data – an XML file in a predefined format must be produced containing the
additional menu information. A sample XML file is provided in the installation folder which
defines the data format. Refer to the sections XML Schema and Data Format below.
2. Install the Application Programming Interface (API) – add
Infor.SunSystems.AdditionalMenus.dll to your project. Create a new instance of
class AdditionalMenuHandler and call the install method with the file name of the
menu data XML file.
Sample code:
AdditionalMenuHandler handler = new AdditionalMenuHandler();
bool succ = handler.Install(menusFile);
or
bool succ = handler.Install(menusFile, userName, password, encoding)
menusFile is the name of the XML file containing the menu data
userName is the name of the SunSystems user to have access to this menu
password is the password of SunSystems user to have access to this menu
encoding is the file encoding of the template file, the default is code page1252
A message is displayed stating whether or not the menu has been installed into the
database menu tables successfully. If unsuccessful, you can track the problem in the log
file.
If the single sign on fails, you are asked to enter the user name and password.
Administrator privileges are required.
3. Install the executable – additional menus can also be inserted into SunSystems database by
using the following command line:
C:\ThirdPartyInstaller.exe [-u userName] [-p password] [-c encoding] filename
username, password and encoding are optional.
For details about menu tables in databases, see the section Menu Tables below.
4. Set permissions – you must set the correct permissions to the new menus in User Manager.
5. Execute the menu – the menu should now be available in the Navigator main menu. However,
you must also add it to the relevant template file.

Screens and Menus
Data File Format
Four sections are included in the menu data XML file where System, Function, Action, and
Menu Item can be defined.
Owner
<Owner>…</Owner>
A GUID can be provided to identify this additional menu. This is optional, if no <owner> is
provided, it will be installed as the default additional menu which one SunSystems instance
can only have one.
An example of the GUID is:
20D208B4-AB55-4477-ABE8-EA8E7A2BE412.
A free tool guidgen.exe to generate the GUID can be found at:
http://www.microsoft.com/downloads/en/details.aspx?familyid=94551f58-484f-4a8c-bb39-0.
adb270833afc&displaylang=en
System
The System tag is defined below:
<Systems>
<System>
<Key>…</Key>
<Resources>
<Resource>
<LanguageCode>…</LanguageCode>
<Code>…</Code>
<Text>…</Text>
</Resource>
…
</Resources>
</System>
…
</Systems>
‘Key’ is used to identify a system; normally it is the shortcut of this system in the base
language, for example, LA. Both system code and system name are localizable which can be
defined in the ‘Resource’ tag. Resource of base language (language code = 1) is mandatory.
The code of the new system should NOT conflict with predefined ones.

Screens and Menus
Function
The definition for ‘Function’ is:
<Functions>
<Function>
<Key>…</Key>
<Resources>
<Resource>
<Code>…</Code>
<Text>…</Text>
</Resource>
</Resources>
<EXECUTABLENAME>…</EXECUTABLENAME>
<CMDLINEARG>…</CMDLINEARG>
<WOKRDIR>…</WOKRDIR>
</Function>
…
</Function>
Key and localizable texts in based language are mandatory.
Function Code should NOT conflict with predefined ones
Action
‘Action’ can be defined in the Actions section.
<Actions>
<Action>
<Code>…</Code>
<Resources>
<Resource>
<Text>…</Text>
</Resource>
…
</Resources>
</Action>

Screens and Menus
…
</Actions>
New Action code should NOT conflict with predefined ones.
Menu Item
This is used to build up the structure of the additional menus by specifying which system the
function belongs to and what action a function can support.
Navigator uses this structure to display them on the menu panel.
<MenuItems>
<MenuItem>
<System>…</System>
<MenuIconType>…</MenuIconType>
<CategoryId>…</CategoryId>
<FunctionSlot>…</FunctionSlot>
<FunctionCode>…</FunctionCode>
<Actions>
<Action>…</Action>
…
</Actions>
</MenuItem>
…
</MenuItems>
‘CategoryId’ is a fixed set, not customizable, and must be chosen from predefined scope.
‘FunctionSlot defines the position in the database to store permission information. For
customized systems it could be 01—99, for predefined systems it should NOT conflict with
predefined functions in that system.
CategoryId and FunctionSlot are optional, if not specified they will be retrieved from the
template.
MenuIconType defines how the menu item is executed. For example, open a form such as
Chart of Accounts, or invoke an application such as UM.
XML Schema
<?xml version="1.0" encoding="utf-8"?>

<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="AdditionalMenus">

Screens and Menus
<xs:complexType>
<xs:sequence>
<xs:element name="Systems">
<xs:complexType>
<xs:sequence>
<xs:element name="System">
<xs:complexType>
<xs:sequence>
<xs:element name="Key" type="xs:string" />
<xs:element name="Resources">
<xs:complexType>
<xs:sequence>
<xs:element name="Resource">
<xs:complexType>
<xs:sequence>
<xs:element name="LanguageCode" type="xs:unsignedByte" />
<xs:element name="Code" type="xs:string" />
<xs:element name="Text" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Actions">
<xs:complexType>
<xs:sequence>
<xs:element name="Action">
<xs:complexType>

Screens and Menus
<xs:sequence>
<xs:element name="Code" type="xs:unsignedShort" />
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="Resource">
<xs:complexType>
<xs:sequence>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Functions">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="Function">
<xs:complexType>
<xs:sequence>
<xs:element name="Key" type="xs:string" />
<xs:complexType>
<xs:sequence>
<xs:element name="Resource">
<xs:complexType>
<xs:sequence>

Screens and Menus

<xs:element name="Code" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="EXECUTABLENAME" type="xs:string"
/>
<xs:element minOccurs="0" name="CMDLINEARG" type="xs:string" />
<xs:element minOccurs="0" name="WOKRDIR" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="MenuItems">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="MenuItem">
<xs:complexType>
<xs:sequence>
<xs:element name="System" type="xs:string" />
<xs:element name="MenuIconType" type="xs:unsignedByte" />
<xs:element minOccurs="0" name="CategoryId" type="xs:unsignedByte"
/>
<xs:element minOccurs="0" name="FunctionSlot" type="xs:unsignedByte"
/>
<xs:element name="FunctionCode" type="xs:string" />
<xs:element minOccurs="0" name="Actions">
<xs:complexType>
<xs:sequence>
<xs:element name="Action" type="xs:unsignedShort" />

Screens and Menus
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
MenuIcon Types
SystemProcess = 1,
PostingProcess = 2,
Inquiry = 3,
Maintenance = 4,
Report = 5,
ExternalFile = 6,
ExternalUrl = 7,
ExternalApp = 8,
ExtensionFunctions = 9
Index of Categories
Category Index
Entry 0
Ledger Configuration 1
Inquiry 2
Financial Reports 3
Report Document Configuration 4

Screens and Menus
Receipts and Payments 5
Financial Processes 6
Financial Processes Setup 7
Reference Data 8
Currencies 9
Ledger Period Management 10
Ledger Budgets 11
Ledger Balances 12
Audit Control 13
Data Integrity Checks 14
Corporate Allocations Configuration 15
Corporate Allocations Reports 16
Corporate Allocations 17
Asset Register Configuration 18
Fixed Asset Reports 19
Fixed Asset Processes 20
Fixed Asset Reference Data 21
Materials Management Configuration 22
Materials Management Reference Data 23
Inventory Configuration 24
Inventory Reports 25
Inventory Processes 26
Inventory Processes Setup 27

Screens and Menus
Inventory Period Management 28
Inventory Revaluation 29
Sales Configuration 30
Sales Reports 31
Sales Processes 32
Sales Processes Setup 33
Sales Price Books 34
Sales Period Management 35
Purchase Configuration 36
Purchase Reports 37
Purchase Processes 38
Purchase Processes Setup 39
Purchase Period Management 40
Transfer Manager 41
Reconciliations 42
Process Rules 43
Databases 44
Security 45
Hidden Options 46
Modules 47
Reports 48
Procedures 49
Maintenance 50

Screens and Menus
Menu Tables
[DOMN_OWNR_MENU_ITEM_ACTION]
[DOMN_OWNR_MENU_TXT]
[DOMN_OWNR_HIDDEN_GRP]
[DOMN_OWNR_MNU_ITM_GRP_TXT]
[DOMN_OWNR_MENU_GRP_ITEM]
[DOMN_OWNR_MENU_ITEM_GRP]
[DOMN_OWNR_MENU]
[DOMN_OWNR_MENU_ITEM_TXT]
[DOMN_OWNR_MENU_ITEM]
[DOWN_OWNR_ACTION_TXT]
[DOWN_OWNR_ACTION]
[DOWN_OWNR_PERMISSION_POS]
SunExtras menu and external programs

Note: Also see the previous section Additional menus API – third party installer.
A special menu template, SXMM01 is available on request. It is a blank menu whose contents
can be defined by the user. This enables users to compose a tailored SunSystems v4 menu
and to incorporate functions developed especially for them into the system. The menu is
invoked when the user keys the mnemonic SX.
It is possible to call external programs from the SunSystems v4 menus, that is, programs
which run independently of SunSystems v4. The program may be written in COBOL; it should
not matter as long as the executable program is in the SunSystems v4 directory. You must
restrict the executable program file name to a maximum of four characters and a suffix of
.EXE, .COM, .INT, or .GNT.
For example, suppose you want to run a program called ABCD.EXE in SunSystems v4 by
entering the selection ‘AB’. You need to add a selection to the relevant SunSystems v4 menu
using SZTE. The selection mnemonic would be ‘AB’, and the Program Id ‘ABCD’. The System
Id field should be ‘Xz’ where z is any other character. Although the module number usually is
only for SunSystems v4 use, it must be set in this case otherwise you receive the message:
SELECTION NOT AVAILABLE
when selecting ‘AB’ at the menu. Set it to 31. Set the rest of the options to spaces except for
Permission Slot number which may be set for OP=Operator Permissions to pick up this
selection.
For example:
No: 41 Code: AB Route: ABCD XX 31 41 Type:
P Menu: 1
Submenu Type: Submenu Menu: Desc: ABCD Program

Screens and Menus
Message files
Message files contain the messages that are displayed on the screen. They are either whole
lines of message, typically displayed on the bottom line of the screen, or small variable length
messages or headings displayed in the body of a template.
Each record in the file has its own number, and the numbers are not always sequential.
Messages belonging to the same function are generally grouped together. The message files
also contain values for validation of some operator input. This validation data is used to
interpret operator input in other languages.
There are three message files:
 SunSystems v4 SSnnMSSG.MSG
 SunAccount SAnnMSSG.MSG
 SunBusiness SBnnMSSG.MSG.
These files are in a special format to be used by the SunSystems v4 programs. To change
their contents, they must be converted to text format, amended with a text editor, and then
converted back to SunSystems v4 format.
The program SZMR is used to convert to and from text format. It is available on request from
your supplier. Note that the version of SZMR must be compatible with the software release
being amended.
To convert to text format:
SZMR xx, E , nn
where xx is:
 SS to convert the SunSystems v4 Message File (SSnnMSSG.MSG)
 SA to convert the SunAccount Message File (SAnnMSSG.MSG)
 SB to convert the SunBusiness Message File (SBnnMSSG.MSG)
where nn is the language number.
In some hardware environments, the program will not pick up the xx,E: you are prompted for
it separately. The files themselves are not converted but are written to an output file. In
environments other than VAX/OpenVMS, the output file name is the same as the input file but
without a suffix. On VAX/OpenVMS systems, the output file name has a suffix of .TXT.
Having used SZMR to extract the text file from the SunSystems v4 (.MSG) file, any standard
editor can be used to change the messages but care should be taken not to introduce control
characters into the file.
To convert the message text files back to SunSystems v4 format, SZMR should be used
again:
SZMR xx ,, nn
or on VAX or Alpha:
Under OpenVMS, in order to be able to type SZMR at the OpenVMS prompt, it is necessary
to set up a symbol name as follows:
$ SZMR :== “$ $DISK1:(SUN42)SZMR.EXE”
where $DISK1:(SUN42) is the name of the disk/directory where the SunSystems v4
programs reside.
where, again, xx is SS, SA or SB, and nn is the language number.
A message is made up of a number of fields:
 Characters 1 to 4 - Message number, used by programs to identify a message.
 Character 5 - Special indicator:

Screens and Menus
– H (Hold) - The program must wait for operator input before clearing the message from the
screen. If a command file or macro is running, the operator input will be taken from the
command file or macro file.
– K (Keyboard) - The program must wait for operator input before clearing the message
from the screen. The operator input must come from the keyboard and never from a
command file or macro file.
 Character 6 - B (Bell) - A bell will be sounded when the message is displayed.
 Character 7 - Severity Indicator:
– W (Warning) - When this message occurs in a GUI system, it will be displayed in a dialog
box next to a warning icon ‘!’ which appears with buttons. These buttons are described in
Characters 8 to 10 below.
– I (Information) - When this message occurs in a GUI system, it will be displayed in a dialog
box and an information icon ‘i’ will appear in the box along with buttons.
– C (Critical) - When this message occurs in a GUI system, it will be displayed in a dialog
box and a critical icon ‘stop sign’ will appear in the message box with buttons.
 Characters 8 to 10 - A message can contain up to three of the following values, each one
being assigned to a button which can be activated with a mouse. They can appear in any
order but the character in column eight defines the default button for the message, that is, the
button that is activated by pressing the Enter key.
– 1=Yes
– 2=No
– 3=OK
– 4=Cancel
– 5=Enter.
For example, W21 would give a message box with a warning icon in the top left-hand
corner of the message box and a Yes and No button, with No being the default.
 Characters 11 to 90 - Message text or operator responses.
The first four characters of the message should not be altered.
There are some special messages which are used for response definitions such as N-No, C-
Credit. These are used when translating SunSystems v4 to other languages.
The messages in question are 056, 057, 394, 449, 502, 664, 665, 679, 726, 741, 742, 743
from SSnnMSSG.MSG, 557 in SAnnMSSG.MSG, and 258 and 655 in SBnnMSSG.MSG. Other
special messages are those containing the values that are loaded into the actions table (see
the subsection The Template Editor), that is 581 to 620 in the SS message file.
The SunSystems v4 message file also contains special words used by FreeFormat. These
words are contained on message number 338. Each word may be up to 20 characters in
length and cannot contain spaces. If the words are less than 20 characters long they must be
padded with spaces so that each word starts in a fixed position in the message. For example,
the English language version of this message is:
0338 LEARN STOP DELAY BREAK
A special method has been used to create messages 188 to 193 on the SunSystems v4
message file. These messages need to have information merged with them when
SunSystems v4 is running.
To make this simple, a special character ‘~’ tilde has been used wherever a space is to occur
in the message:
0188 Learning~
0189 ~...~To~stop,~enter~\~and~STOP
0190 Learning stopped
0191 Executing~

Screens and Menus
0192 ~...~To~stop,~enter~!=Abandon
0193 Enter~
For example, when a FreeFormat macro is running, line 21 of the screen displays the macro
name, like this:
Learning END_OF_DAY_REPORTS ... To stop, enter \ and STOP
It is important that leading and trailing ‘~’ tildes are not misplaced. For example, message 188
must not start with ~ but must end with ~.
You may find that some messages end with a ‘/’ slash or ‘//’ slashes. This indicates the
maximum length of the message, and text must not go beyond this marker. Some messages
contain ‘!’ exclamation mark which indicate where data is to be inserted into the message by
an application program before it is displayed.

Chapter 4 Reference Maintenance
4
Introduction
This section describes how to modify and create record types in the reference file. This is the
master file, common to both SunAccount and SunBusiness, which stores fundamental
reference data. The application programs constantly refer to the reference file.
You might want to modify or create reference record definitions in the following
circumstances:
 When undertaking a translation of SunSystems v4 to another human language
 When adding fields to an existing reference record
 When adding new record types to the reference file.
If you add new fields or new record types, they will not be used by the SunSystems v4
software packages. However, SunSystems v4 reference maintenance can update, report,
audit and transfer such records. You can have access to them directly from your own COBOL
programs or through reference Transfer, and then from other software packages. Thus,
SunSystems v4 can be used to update the new data for you, and you can then use it in your
own software.
In the section System Overview, the reference maintenance programs are described as
controlling the updating, transfer, auditing and reporting of master data on the reference file.
The section Naming Conventions covers the conventions used for naming the reference file
and other associated files.
The full data file definition for the reference file is given in the appendices to this manual.
The reference file contains many record types. They include, for example:
 Items of stock
 Customer addresses
 Calculations to be made on invoices.
The various record types are defined on the reference layout files. The layouts define the
characteristics of the record types including, for example, the following:
 The format for reporting the data
 The number of key fields
 The number of fields.
The layout files are a link between the data on the reference record and the corresponding
reference maintenance screen.
There are four reference maintenance utility programs which use the reference file:
 The Reference Update program (SSRU)
 The Reference Reporting program (SSRR)
 The Reference Transfer program (SSRT)
 The Reference Audit program (SSRA).
These programs treat all record types in the same way, but use the layout files to distinguish
between the different record types. So the reference maintenance programs obey the
instructions coded into the reference layout file.
In this section the following areas are discussed:

Reference Maintenance
 The rules governing reference records

 How to use these rules to create new reference records and change existing ones
 How to transfer reference records to external files using SunSystems v4 reference Transfer.
Standards for reference record types

These standards govern the reference record types provided with SunSystems v4. If you
create your own record types, they must adhere to these standards.
Associated with each reference record type is the following:
Record Type Code
3 characters
This is a unique three character code, which will form the primary portion of the record key
(the total key length is 64 characters). The subsection The Template Editor describes the
relationship between the two character screen selection codes and the three character record
type.
Template
A suitable template is set up which is used by the program SSRU to maintain and retrieve
records of that type. See the section Screens and Menus.
Routing Parameters
For each reference maintenance function, routing parameters are inserted on the appropriate
menu template. See the section Screens and Menus.
Layout Definition
Appropriate layout definitions are inserted in the relevant reference layout files, which are
described later in this section.
The following record types are used by SunSystems v4 and should not be used when
creating new record types:
 ACB Account Balance
 ACC Chart of Accounts
 ACP Generate Payments/Debits selection
 ADB Address Analysis
 ADD Names and Addresses
 AJD Journal Definition
 AJP Journal Presets
 ALC Period Calendar
 ALD Allocation Definition
 ALR Allocation Ratio
 ALS Allocation Source
 ALT Allocation Target
 ALW Allocation Work File Details
 ALX Allocation Change in Balance
 AND Analysis Definition
 ANV Analysis Code
 ARS Analysis Mapping Rules
 AST Assembly Structure
 AUC Audit Control
 BCD Budget Check Definition

 BKA Bank Details

 BPF SOP/POP Print Selection
 BUD Budget Definition
 BUS Business Definition
 CAD Calculation Definition
 CAT Calculation Table
 CND Daily Conversion Rate Definition
 CNV Conversion Table
 COL Column Heading
 CON Financial Analysis Consolidation
 CSD Control Sequence
 CVD Conversion Definitions
 DAG Data Access Group Record
 DBA Database Definition
 DAY Daybook Definition
 DBK Daybook Layout
 DCC Document Counters
 DCD Despatch Counter
 DDC Database Categories
 DDD Data-item Definition
 DDE Entity Definitions
 DDF Sub Headers/Footers
 DDK Data Record Type
 DDL Entity Descriptions
 DDR Record Description
 DDS Report Types
 DDT Item Description
 DPH Depreciation Table Heading
 DPT Depreciation Table
 ESR Payment Reference Details / Standard Description
 FAA Asset Analysis
 FBR Asset Budget Value
 FCD Calculate Depreciation Selection
 FDI Asset Disposal Selection
 FDR Asset Diary
 FLT Formatted Layouts
 FMT Format Definition
 FMX User Format
 FTC Financial Table Column
 FTF Financial Table Format
 FTR Financial Table Row
 FVR Asset Value
 GAN Financial Analysis Layout
 GLI Ledger Interface
 GLT Aged Analysis Layout
 HAL Additional Header Labels
 IAD Systems Labels
 INF Debtor/Creditor Transfer Selection
 INP Invoice Prefix
 INT Debtor/Creditor Transfer Layout

 ITD Extended Item Descriptions

 ITM Item Record
 ITP Item Special Process
 ITS Item Supplier
 KLT Statistical Layouts
 LAN Language Definition
 LDG Ledger/Register Definition
 LIT Location Item Record
 LOC Location Definition
 LXC Ledger Export Consolidation
 LXD Ledger Export Definition
 LXS Ledger Export Selection
 MAN Inventory Control Analysis Layout
 MCD New Cost Definition
 MIV Item Validation
 MLC Location Accounts
 MMC Movement Accounts
 MRA Revaluation Analysis
 MRP Revaluation Profile
 MSD Stock Take Definition
 MVD Movement Definition
 MVP Movement Preset
 MVV Movement Values Definition
 OAG Authorisation Groups
 OAN Sales Analysis Layout
 OAU Release Authorisation
 OBA Maintain Operator Buttons
 ODM Standard Density Maintenance
 ODN Operator Definitions
 OFG Free Goods Setup
 OFR Free Goods Rules
 OIM Invoice Modification
 OOT Minimum Order Tolerance
 OPH Sales Order Header Preset
 OPI Sales Order Detail Preset
 ORX Returns and Exchanges
 OSN Credit / Debit Notes
 OTD Sales Order Definition
 OTM Tracking Code Maintenance
 OTP Tracking Code Parameters
 OXC Tracking Codes Excluded Combinations
 PCA SunAccount Period Cleardown Consolidation
 PCB SOP/Inventory Control Period Cleardown Consolidation
 PCP POP Period Cleardown Consolidation
 PCI Charge Index
 PDN Printer Definitions
 PFD Purchase Format
 PLE Payment Terms Instalments
 POD Purchase Order Definition
 PPF Payment Profile Record

 PPH Purchase Order Header Preset

 PPI Purchase Order Detail Preset
 PRB Price Book Record
 PRD Price Book Definition
 PRH Price Book Hierarchy
 PTE Payment Terms Header
 PUC Unit Conversion Table
 SDE Additional Descriptions
 SDT Additional Descriptions
 SFD Sales Format Definition
 SLN Statement Line Contents
 SPP Print Picking Control
 SPR Spread Ratio
 SQN Sequence Number Definition
 TAX Tax Defaults
 TDN Terminal Definition
 TID Treasurer Interface Definition
 TLL Tax Listing Layouts
 TMS Transaction Matching Selection
 TTR Treasurer Transaction Reference
 TXA Tax Accounts Definition
 VER Version Record
 VPX Void Payments Selections
 XLT Lead Times
In addition to the preceding list, which is used by Infor, there is an official register of reference
record types that are used by external developers. To acquire an up-to-date list of these
reference records, please contact your supplier.
Reference layout files

This subsection describes the logic of the layout files. With this information you can add fields
to existing record types and create new record types.
Note that certain reference records are shared by a number of SunSystems v4 modules. The
layout may appear in more than one layout file, but this is not always the case. For example,
CT=Calculation Tables can be used in both Sales Order Processing and Purchase Order
Processing, so the layout appears in the SunBusiness common layout file SBnnRM.LYT,
where nn is the language code for the file. However, LD=Ledger Definition and RD=Register
Definition are defined on SAnnRM.LYT and SFnnRM.LYT, even though they share the same
reference record. Always check whether the layout appears on more than one layout file.
Please note that as SunSystems v4 is enhanced by Infor, fields are frequently added to
existing records. Generally, the first available space on the record is used. Therefore, to avoid
the risk of your amendments clashing with the authors’ amendments, you are advised to use
the available space at the bottom of the record, at the end of the filler.
When creating your own reference maintenance records, only use field number 3 for a
Lookup code. If there is no Lookup code do not use this field. In certain reference
maintenance processes (for example, reference Transfer), field 3 is assumed to be the
Lookup code.
Infor has allocated some specific space to users on record types such as NA=Names &
Addresses. This space will not be used in future updates to SunSystems v4.

Should you wish to upgrade to a new version of SunSystems v4, changes you make to the
.LYT files etc. must be reapplied. For this reason, it is important that such adjustments are
fully documented.
Reference layout files are text files. They can, therefore, be edited using a word processor.
The following is the beginning of the SunBusiness (common) layout file SB01RM.LYT:
ITMR ITEM RECORDS 00RF01BU061EXT
ITMI00100000Item Code 01001000415Y
ITMI00200000Item Description 01018008630Y
ITMI00300000Lookup Code 01050006810
ITMI00400000Unit of Stock 04018011605
ITMI01900000Whole Units only 05018037501 100031 Y
ITMI00500000Unit of Sale 06018012105
ITMI00700000Whole Units only 07018037601 100031 Y
ITMI03100000AlternateItem Code 02018043415
ITMI01000000Unit Weight 04061030218 5NUM
ITMI03900000Set Purchase Price 07040075701 P100031 Y
ITMI03700000Def Purchase Price 08017073918 5NUM
ITMI03800000Update Price 08040073801 100532 OIY
ITMI04100000Purchases Acct. Dsc 00000999900N B000000
ITMI04200000Purchase Account 02098041610Y f000607
ITMI02000000Standard Cost 01061032018 5NUM
ITMI02100000Latest Cost 02061033818 5NUM
ITMI02200000Leading Sign 03080035601 K101033+-
ITMI02300000Average Cost 03061035718 5NUM
ITMI01600000Item Process 01087037801
ITMI03000000Stock Take Frequency03087043103 0
ITMI02400000Comments 02040038120
ITMI02600000Allocation Method 02087037701 100487 FMBOS
ITMI02700000Picking by Exp Date 06087075801 102099 1
ITMI02800000Supplier Control 03040037901 100519 YN
ITMI02900000Customer Control 04040038001 100519 YN
ITMI04300000Audit Date 09018076001 102220 N
ITMI03200000Commodity Code 03018059915
ITMI04000000VCF/WCF Indicators 11001075901 102178 WV
ITMI03300000Assembly Level 05040061401 100397 0123456789
ITMI03400000Process Components 06040061501 100398 PD
ITMI03500000SOP Ext Item Descr 04087061601 100426 1234A
ITMI03600000POP Ext Item Descr 05087061701 100426 1234A
ITMI05001179BSP - Text 1 00000999900N L000000
ITMI05101179BSP - Price 1 07047012618 5AMT
ITMI05201179BSP - Next Price 1 07067019818 5AMT
ITMI05301179BSP - Date 1 07087027008 DAT
ITMI05401179BSP - Text 2 00000999900N M000000
ITMI05701179BSP - Date 2 08087027808 DAT
ITMI05801179BSP - Text 3 00000999900N N000000


ITMI06101179BSP - Date 3 09087028608 DAT
ITMI06201179BSP - Text 4 00000999900N O000000
ITMI06501179BSP - Date 4 10087029408 DAT
ITMI07002002Analysis Category 0 01118044915 INC0
ITMI13005160Sales Account Desc 00000999900N A000000
ITMI13105160Purchases Acct. Dsc 00000999900N B000000
ITMI13205160Account Code 1 Desc 00000999900N C000000
ITMI13305160Account Code 2 Desc 00000999900N D000000
ITMI13405160Account Code 3 Desc 00000999900N E000000
ITMI13505160Account Code 4 Desc 00000999900N F000000
ITMI13605160Account Code 5 Desc 00000999900N G000000
ITMI13705160Account Code 6 Desc 00000999900N H000000
ITMI13805160Account Code 7 Desc 00000999900N I000000
ITMI13905160Account Code 8 Desc 00000999900N J000000
ITMI12005160Sales Account 01098040110 f000607
ITMI12105160Purchase Account 02098041610 f000607
ITMI12205160Account Code 1 03098061810 f000607
ITMP001Item Code Item Description Lookup
ITMP002Standard Cost Item Process Sales Account Analysis 0
ITMP003 Alternate Item Comments
ITMP004 Latest Cost Alloc Method Purchase Account.
ITMP005 Commodity Code Supplier Control
ITMP006 Average Cost Stk. Take Frq. Account Code 1.
ITMP007 Stock Unit Customer Control
ITMP008 Unit Weight SOP Extra Desc..
ITMP009 Whole Unit Assembly Level
ITMP010 POP Extra Desc..
ITMP011 Sale Unit Proc Components
ITMP012 Pckng by Xpiry Dte 8 9

ITMP013 Whole Unit Set Purchase Price

ITMP014 Date Next
ITMP015 Def Purchase Price Update Base Selling Price
ITMP016 Next Selling Price Applies
ITMP017 Audit Date
 Characters 1-3 - define the reference record type.
 Character 4 - defines the line type. There are three line types in a layout file:
– R for Record information
– I for Field information
– P for Report information
These line types are described next:
Record information
Character
 4 - line type = R
 5-7 - not used
 8-27 - name of record type
 28-29 - not used
 30-31 - file Id = RF for Reference File, IN for Install File, DD for Data Directory
 32-33 - number of key items
 34-35 - AUC record type SS=System or BU=BU specific or NA=Not Audited; for visual
reference/auditing only
 36-38 - AUC record Slot number which contains this functions Audit control flag/setting
 39-41 - setting of EXT triggers user-hook call at record level
Field information
Character
 4 - line type = I
 5-7 - field number on template
Note: A maximum of 120 fields can be defined on each reference record. If more
than 120 are added they will be ignored by SunSystems v4, and so will not appear
on the relevant reference maintenance screen.
 8-9 - Pop-up window number. When Reference Maintenance processes the first field that has
a non-zero window number, a window for that field will automatically pop up for the fields with
that window number. That window’s dimensions should also be defined on the window. For
information on defining windows on templates see the section Screens and Menus.
 10-12 - Overlay action number. When reference maintenance displays pop-up windows, the
windows can also be selected from the selection bar. Overlay must be defined on the template
as a parent action (action 0053), and the overlay action number must be defined as a child
action to overlay action. For more information on defining actions on templates, see the
section Screens and Menus.
 13-32 - field name
 33-34 - print line (1-12)
 35-37 - print start column (001-132)
 38-41 - offset in record

 42-43 - field length

 44+ - validation parameters etc., as follows:
 44:
– ‘Y’ - Accept field, mandatory
– SPACE - Accept field, optional
– ‘N’ - Display field.
 45 - Decimal places for numeric validation, except for analysis code checking (type 5) where
this is the analysis category letter. Note that validation types 3 and 4 can use character 46 to
indicate the number of decimal places for the input. See the following descriptions of the
validation types.
There are six validation types, depending on the contents of character 46+. When character
46 is a space, simple character validation is achieved. This is shown by validation types 1 to
3. In some cases the validation types can be combined. For example, the simple character
validation can be combined with the more complex special validation of type 4. Also, the
number of decimal places can be used with the other validation types.
Type 1
Single character validation.

This is identified by ‘ 10’ in characters 46-48.
 46 - SPACE
 47-48 - ‘10’
 49-52 - Error message number
 53+ - Valid single character values.
For example, ‘ 100432 YS’.
Error number 432.
Valid single character values are a ‘ ’ space, ‘Y’ and ‘S’.
Type 2
Two single character validation in a two character field.

 46 - SPACE
 47-48 - ‘11’
 53+ - Valid single character values for position 1, followed by a space separator, followed by
valid single character values for position 2.
For example, ‘ 110433ABC YZ’.
Error number 433.
Valid two character combinations are ‘A ’ ‘AY’ ‘AZ’ ‘B ’ ‘BY’ ‘BZ’ ‘C ’ ‘CY’ ‘CZ’.
Note: If a space was valid in position 1, there would be a space in front of ‘ABC’ in
the validation string, that is, ‘ 110433 ABC YZ’.
Note: That the first space after ABC separates the position 1 valid characters from
the position 2 characters. The second space after ABC shows that the second
character can be a space.

Type 3
Two character validation.

 46 - SPACE
 47-48 - ‘20’
 53+ - Valid two character values.
For example, ‘ 200434A1B2C3’.
Error number 434.
Valid two character values are ‘A1’ ‘B2’ ‘C3’.
Note: If this was a type 2 validation (‘ 110434ABC 123’) the valid characters would be
‘A1’ ‘A2’ ‘A3’ ‘B1’ ‘B2’ ‘B3’ ‘C1’ ‘C2’ ‘C3’.
Type 4
Special validation.
This is identified by a non-space in character 46 and numeric digits in characters 47-48.
 46 - Special validation type (‘A’ to ‘z’) and numbers and special characters (e.g. ‘[’)
 47-48 - Two numeric digits ‘00’, ‘10’, ‘11’ or ‘20’
 53+ - Optionally used for character validation.
For example, ‘M000435’.
Special validation type ‘M’. This indicates the validation routine to be used by reference
maintenance. Since a new validation type requires a change to the program, operators
cannot add their own special validation. This type of validation is mainly for internal use by
SunSystems v4 and is not intended to be used externally. Consequently, the special
validation types are not documented.
Error number 435.
When characters 47-48 are ‘00’ there is no character validation. When these characters are
‘10’, ‘11’ or ‘20’ the character validation is performed before the special validation. For
example, ‘C10031 Y’ - check entry to be a space or ‘Y’ and if valid perform special validation
type ‘C’.
Type 5
Analysis code checking.

This is identified by ‘NC’ in characters 46-47.
 45 - Analysis category letter
 46-47 - ‘NC’
 48 - Analysis category number
 49+ - Not used.
For example, ‘ANC1’.

The entered analysis code is validated to be a type A1. If the code is valid, the associated
name is displayed at the bottom of the screen. If the code is invalid, a message:
DOES NOT EXIST
is displayed instead. The NC=Analysis Category name is displayed in fields 90-99 when the
template is first displayed.
Type 6
Special processing.
This is identified by characters 46-47 not being ‘NC’ and characters 47-48 being non-numeric.
 46-48 - Special process type
 49+ - Not used.
For example, ‘DPD’.
Special processing type ‘DPD’. This indicates that a special process is to be performed
following the entry of a field. This particular process is the validation of the disposal period on
the asset value record. It is similar to type 4 except that the error message number is hard
coded in the routine. It could be a special file update, calculation or screen display.
As with type 4, a new special process requires a change to the reference file maintenance
program, so operators cannot add their own special process. This facility is mainly used for
specialised low-level processing, but some of the special processes might be of use when
writing add-on reference maintenance functions.
The following is a list of possible useful routines:
 ‘PER’ - Period validation.
 ‘DAT’ - Date validation.
 ‘NUM’vNumeric validation. Leading zeros are inserted before storing on file and likewise
leading zeros are removed before displaying. If ‘NUM’ is not used, leading spaces are stored
on file.
 ‘AMT’ - The same as ‘NUM’ but the number of decimal places is taken from the ledger
definition rather than from character 45.
 ‘QTY’ - The same as ‘NUM’ but the number of decimal places is taken from the BD=Business
Definition rather than from character 45. The BD=Business Definition states whether
quantities are integer or not. Integer quantities have no decimal places, non-integer quantities
are always three decimal places.
 ‘RDI’ - Record delete inhibit. If the field is spaces, the record can be deleted. If the field is non-
spaces, record deletion is inhibited.
 ‘EXT’ - This is perhaps the most complex special validation technique, but is very flexible and
allows you to write your own COBOL validation routine. The routine must be written in the
same version of COBOL as the version used for the particular SunSystems v4
implementation. The routine will be called by the reference maintenance program when a field
with a validation type of ‘EXT’ is encountered. The routine is called whenever the field is
displayed or accepted, so it is important for the routine to take note of the current update
mode. See the section User Hooks for more details on the user hook and how to use this
facility.
Report information
Character
 4 - line type = P

 5-7 - Heading number

 001 = - Heading-1 characters 1-66
 007 = - Heading-4 1-66
 008 = - Heading-4 67-132
 009 = - Heading-5 1-66
 010 = - Heading-5 67-132
 011 = - Heading-6 1-66
 012 = - Heading-6 67-132
 013 = - Heading-7 1-66
 014 = - Heading-7 67-132
 015 = - Heading-8 1-66
 016 = - Heading-8 67-132
 8-73 - Heading text.
At least one and at most ten heading lines may be defined. Heading lines 3 to 10 will only be
printed if they are non-space.
Example
The following line is taken from the preceding layout file SB01RM.LYT:
ITMI[072]02002Analysis Category 2 [03118047915] INC2
This line represents the following:
Value Char
ITM 1-3 Record Type
I 4 Line Type
[012] 5-7 Field Number on Template
02 8-9 Pop-up Window Number
002 10-12 Pop-up Window Action Number
Analysis Category 2 13-32 Field Name
02 33-34 Print Line (1-16)
128 35-37 Print Start Column (001-132)
252 38-41 Offset in Record
05 42-43 Field Length

Value Char
SPACE 44 space
INC2 45+ Validation Parameters for Analysis Code I2
Example
If a fax number was added to record type ACC, it would appear on SunSystems v4 screens
and reports. It could be used by the operator’s own programs. However, apart from reference
maintenance, it would not be processed by SunSystems v4.
Such additions are useful if tailoring SunSystems v4 for a particular industry-specific
application.
Reference transfer
This feature enables reference records to be I-Imported and E-Exported to and from
SunSystems v4 (Transfer in or out). Since reference transfer is an option on most of the
reference maintenance screens, the facility is described in System Basics Help in the Actions
section.
The transfer file contains only one record type, relating to the reference maintenance screen
used for I-Import and E-Export. The transfer format in which reference data is transferred is
selected by the operator. Any of the available transfer formats can be used. This is described
in System Basics Help in the Actions section.
The layout of records in the transfer file is very similar to the layout of the actual reference
record being transferred. These layouts are listed in the appendices to this manual. The
transfer file layout is the same, except that the first three characters (record type) are omitted.
An example of this is shown next, where the transfer layout for the CA=Chart of Accounts
record is described, with examples of a transfer record in:
 NDF format
 CDF format.
Note that the field before the Lookup code is always the reference lookup Id and must contain
the correct three-character code for that particular record type. The field after the Lookup
Code is Date of Last Update, and is actually defined as a filler on the reference record layout.
Compare this example with the record layout for CA=Chart of Accounts in the appendices to
this manual. Note that the fields called ‘Filler’ in the following example are required only on
NDF and FLF formats.
The exception to this is any field called ‘Filler’ that is described as ‘Date Last Updated’. This
must be included, though the value may be zero, as it will be overwritten with the system date
when the import is performed.
Field Position Length
Account Code 0001 10

Filler 0011 51 value SPACES
Reference Lookup Id 0062 03 value ‘ACC’
Lookup Code 0065 10
Date of Last Update 0075 08 format YYYYMMDD
Account Name 0083 30
A/c Type(D/C/T/P/B/M) 0113 01
Bal.Fwd/Op.Item(B/O) 0114 01
Account Status 0115 01
Conversion Code Ctrl 0116 01
Conversion Code 0117 05
Suppress Revaluation 0122 01
Commitment Check Account 0123 15
Comments 0138 20
Permission 0158 01
Enter Anal Code T0 0159 01

Address Code 0169 10
Direct Debit 0179 01
Priority 0180 01
Pay Method(C/B/S/) 0181 01
Credit Limit 0182 10
Payment Days 0192 03
Payment Terms 0195 01
Discount Days 0196 03
Discount % 0199 05
Discount Days 2 0204 03
Discount % 2 0207 05
Last Transaction 0212 08 format YYYYMMDD
Transactions Present 0220 01
Account Balance 0221 19
Acc. Order Balance 0240 19
Allocation in Progress 0259 01
User Area 0260 30
Tax Code 0290 20
Analysis Category A0 0310 15

Filler 0460 64 value SPACES
Operator Group Mask 0524 5
Filler 0529 05
Settlement 0534 01
Link Account 0535 10
Def Bank Account Code 0545 05
Example A) NDF
64001 ACCPECKED
19961022Pecked Poultry
ProductsDO 64001
1
0000300000030 015030000000000019910228Y-000000000089188420-
000000000165689000
US1 W JP-
EC R
00000
Example B) CDF
64001,ACC,PECKED,19961022,Pecked Poultry
Products,D,O,,,,,,,64001,,1,,300000,30,,15,3000,,,19910228,Y,-
000000000089188420,-000000000165689000,,,,US1,W,JP-EC,,,R,,,,,,,,

Note: Most fields on the transfer record are not validated during import. Therefore
you are advised to initialise numeric fields; in other words, do not leave them blank or
leave any non-numeric data in them. This will ensure that there are no problems later
with invalid decimal data.
Note: When using NDF, the record terminates after the last non-space character, i.e.
it is variable length. When using other formats, such as CDF, the record terminates
after the delimiter on the last field, i.e. all fields must be included.
Remember also that alphanumeric fields are not validated during import, and no left or right
alignment is done; they are simply written to the reference file as they appear on the import
file. This is important with regard to analysis codes – you may be using numeric values for
analysis codes, but as these are actually alphanumeric fields, you must ensure that the
alignment is consistent.
Audit Control management

Introduction
This section describes how to modify and create function related Audit Control (AC) flags,
which allow the user to switch on, or off, the availability of the Report Audit Trail option from
the Actions drop-down list on the associated functions form. It also describes the elements
that support automated Auditing via Reference Maintenance.
As a third party developer upgrading an external product to version 4.4, refer to document
‘v4.4 Audit Control Upgrade Guide’ to establish whether the Audit Control Management
project requires modification of External product Audit Control in accordance with the new
version 4.4 standard. In summary:
 If your Audit Control processing is totally independent of the pre-v4.4 Audit Control
infrastructure, for example, you are not using the standard AC record types to store your AC
flags, the necessity to upgrade is unlikely; however, you may choose to integrate with the
extended and more flexible AC management structure implemented under this project.
 Otherwise, refer to the v4.4 Audit Control Upgrade Guide for guidance.
The Audit Control management checklist later in this section, is designed as a prompt for
those familiar with the version 4.4 AC flag management process; for those unfamiliar with this
process, please read on to familiarize yourself with all of the processing elements
Audit Control flag location
SunSystems v4 version 4.4 introduced Audit Control at Business Unit level, therefore the
location of the new AC flag must first be identified; either on the:
 System AC record – which contains the Audit Control flags associated with functions
accessible from the SS menu.
 Business Unit AC record – which contains the Audit Control flags associated with functions
from all other modules, Ledger Accounting, Sales Order Processing, Inventory Control, etc.
This record exists for each of the registered Business Units and therefore duplicates the same
flag to make it Business Unit specific.
SunSystems v4 version 4.4 also introduced the concept of grouping like flags, although since
many are shared between modules this has not always been possible, however, when
selecting a position for the new flag, add to the end of an appropriate group in the gap

provided; as third party developers, you are advised to use the slot numbers 501 thru 700
reserved for the purpose, see the section Add-on product - suggested slot assignment/layout
format later in this guide.
AUC Record Layout
Both standard SunSystems v4 version 4.4 Audit Control record types are defined in copy
library ssinsrc.cpy.
Each currently maintained AC flag is logged, grouped and assigned a slot in the appropriate
AUC record layout, the slot is fully documented in the record layout in its appropriate data
record variation (AUC-SS-DATA or AUC-BU-DATA). For example, the first two Business Unit
related AC flags are defined as follows:..
* Business Unit AC flags, key with BU specified, e.g. 'AUCDEM'
02 AUC-BU-DATA REDEFINES AUC-DATA.
* 086/Slot 1 - Chart of Accounts
03 AUC-ACC PIC X.
* 087/Slot 2 - Names & Addresses
03 AUC-ADD PIC X.
The 086/Slot 1 reference in the comment refers to:

1. Position of the AC flag in the whole AUC record (086) – used to maintain/audit the AC flag
2. Position of the AC flag in the AUC data area (slot 1) – used to access the AC flag in RM.
The unique flag reference, for example, AUC-ACC, is used by functions, other than those
maintained via RM, to access the flag directly; however, even if the flag is not being
referenced, it effectively becomes a place marker and helps to avoid unintentional slot re-use.
AUC Record maintenance
The AC flags record position in the comment is represented in the layout file(s) for the
purpose of AC flag maintenance and auditing (using example * 086/Slot 1 - Chart of
Accounts).
 wherever the flag is being maintained (or audited) via an AUC function, its associated item
record (AUCI) in the layout file (sa01rm.lyt, sc01rm.lyt, sf01rm.lyt, etc.) identifies the
record position (086) in the string. For example:
AUCI00100000Chart of Accounts 01013008601 100031 Y
If it was only being audited by the AUC function, it would appear as:
AUCI99900000Chart of Accounts 01013008601
AUC flag access
If the function associated with the AC flag is also maintained via Reference maintenance,
access to and evaluation of the AC flag is automated, to facilitate this:
 The AC flag slot reference on the functions header record is 5 bytes in length, consisting of:
a 2 byte alphanumeric reference

+ the 3 byte slot no reference

This new initiative has increased the potential to identify the last byte of the AUC-DATA field
(slot number 715) and therefore an overall maximum number of AC flags to 1430.
The AC flags slot number in the comment is represented in the appropriate layout file(s) (also
using example * 086/Slot 1 - Chart of Accounts):
 wherever the function is being maintained, its associated header record (ACCR) in the layout
file (sa01rm.lyt, sc01rm.lyt, sf01rm.lyt, etc.) identifies the slot number (1). For example:
ACCR CHART OF ACCOUNTS 00RF01BU001EXT
Note: The preceding two bytes (‘BU’ in this case) are a reference to the AUC record
type in which the flag resides (BU specific in this case), the alternative being ’SS’
referring to the System record type; this is a visual reference only and does not
influence record access processing
Alternatively, the function associated with the AC flag that is NOT maintained via Reference
maintenance:
 Will read the appropriate AUC record, reference the flag directly, for example, as AUC-ACC,
and carry out its own processing based on the retrieved value.
Reference Maintenance Audit Control Function Layout
When the new AC flag has been added to the layout file, ensure that it is audited correctly on
its own record (also defined in the layout file); using the same example * 086/Slot 1 - Chart
of Accounts:
 Place a reference for the AC flag in the print header, for example:
AUCP005 CA NA NC BK BD JD JP TF TR TC SL AD AS AR AB AA
 And set the related report position of the AC flag (line 01 column 013) in the Item string, for
example:
AUCI00100000Chart of Accounts 01013008601 100031 Y
Audit Control flag Copy facility
Prior to version 4.4, all Business Unit specific AC flags were held on a single AC record,
therefore, existing customers requiring uniformity of auditing across Business Units may have
been negatively impacted by the new project changes.
Consequently, a facility to copy setting from one Business Unit to another (or All others) was
introduced to all Audit Control setup functions (shortcut AC) as action Copy; this is not a
selective process (all settings are transferred between Business Units).
Audit Control management checklist
The following checklist is a suggested approach based on the version 4.4 implementation; it
assumes that you intend to adopt the new method for AC flag assignment.
New AC flag preparation
Locate the spreadsheet used to upgrade to version 4.4 and add new line(s)
detailing:

New function to be Audited with action Report Audit Trail (0100) ‗‗‗‗‗
The intended AC flag processing source, RM layout file(s)/function Id or ‗‗‗‗‗

application
Assign and detail/audit a new AC flag in the reserved area via a record layout ‗‗‗‗‗
Add the AC flags details to the spreadsheet, this includes:
New AC flag location, System or Business Unit specific AUC record or other ‗‗‗‗‗
Assigned AC flag slot number, Offset and unique AUC-aaa reference ‗‗‗‗‗
Map new AC flag(s)

Using the spreadsheet as your guide:
Regarding AC flag maintenance via RM:
Add new AC flag label and input field to the Audit Control template ‗‗‗‗‗
Add related RM layout Item line with the assigned record offset ‗‗‗‗‗
Add any Audit only RM layout Item lines in other related AC functions ‗‗‗‗‗
If an application is maintaining the AC flag:
Ensure that it accesses the correct System or Business Unit specific AUC ‗‗‗‗‗
record type
Use the unique AUC-aaa reference assigned to reference the AC flag ‗‗‗‗‗
Regarding AC flag access via RM:
Use the assigned slot numbers in the functions RM layout Header line ‗‗‗‗‗
Regarding AC flag access via an application:
Ensure that it accesses the correct System or Business Unit specific AUC ‗‗‗‗‗
record type
Use the assigned unique AUC-aaa reference to reference the AC flag ‗‗‗‗‗

Test the new AC flag(s)

For each new AC flag:
Access the AC flag maintenance function and set the flag to On ‗‗‗‗‗
Access the related function and verify that action Report Audit Trail is ‗‗‗‗‗
available
Access the AC flag maintenance function and set the flag to Off ‗‗‗‗‗
Access the related function and verify that action Report Audit Trail is ‗‗‗‗‗
unavailable
Add-on Product - Suggested slot assignment/layout format
There are no specific rules applied to the assignment of slots for add-on product auditing
requirements, however, since the implementation of the audit control management project in
version 4.4, there are far more slots available on each AC record, consequently blocks have
been reserved for both the Infor add-ons and the third party Companion Products to avoid
unnecessary overlaps.
For Infor add-ons, target slot numbers 401 thru 550 only, as follows:
*
02 AUC-BU-I-AO REDEFINES AUC-DATA.
* First 400 Slots reserved for standard v44
03 FILLER PIC X(400).
* 486/Slot 401 - First Infor Add-on BU specific AC flag
03 AUC-I01 PIC X.
* 487/Slot 402 - Second Infor Add-on BU specific AC flag
03 AUC-I02 PIC X.
* 488/Slot 403 - etc..
If there are AC flags at System level, an AUC-SS-I-AO redefinition will also be required,
bringing the reserved number of slots to 300.
For third party Companion Products, target slot numbers 501 thru 700 only, as follows:
*
02 AUC-BU-3-CP REDEFINES AUC-DATA.
* First 550 Slots reserved for standard v44 & Infor Add-on’s

* 636/Slot 551 - First Companion Product BU specific AC flag

03 AUC-C01 PIC X.
* 637/Slot 552 - Second Companion Product BU specific AC flag
03 AUC-C02 PIC X.
* 638/Slot 553 - etc..
If there are AC flags at System level, an AUC-SS-3-CP redefinition will also be required,
bringing the reserved number of slots to 300.

Chapter 5 Printed Output
5
SunSystems v4 reports can be printed immediately or stored on disk. In the latter case, the
report can be printed later, or the file transferred to another software package.
Reference report headings are held in the layout files:
SxnnRM.LYT
where x represents the system, and nn represents the language code. Other reports (for
example IT=Inventory Status) and those produced as part of another function (for example
GP=Generate Payments or JI=Journal Import), take their headings from the headings files.
You can also design your own documents in SunSystems v4. These include SunAccount
debtor statements, creditor remittances, and cheques. SunBusiness documents include forms
such as quotations, invoices, picking lists, etc. The definitions for these documents are held in
the report format file. Similarly, the definitions for AL=Account Listing, JL=Journal Listing and
DB=Daybook Listing reports are held in the report format file.
Report heading file

Like the message file described in the section Screens and Menus, this is a file that can be
tailored to an operator’s requirements by editing it using a word processor.
The report heading file is called SxnnHEAD, where x represents the system and nn
represents the language code.
SunSystems v4 report headings and other report text are retrieved via calls to the report
handler program SSRH.
Each report title or other line is shown in full as it will appear when printed. The maximum
length of a line is 132 characters, plus the line number. If amending the text, do not assume
that you can use all 132 characters on any line. The length of line printed is governed by the
print program in each case. You can normally assume that all of the line up to the last text
character can be used. If a delimiter of ‘//’ two slashes is shown, that marks the end of
available space. If a series of exclamation marks is shown, this means that a data item is
printed in that space, so it should not be used for headings. The line number should not be
amended.
Some reports in SunAccount have two formats: single-currency and multi-currency. A
separate set of headings is given for each. Note that some reports occur in both SAnnHEAD
for LA=Ledger Accounting and SFnnHEAD for AR=Fixed Asset Register.
The default column headings for reports are held towards the end of each report heading file.
These headings are printed over columns of ten characters and can be centred or aligned as
required. Part of the SunAccount report heading file is shown here:
015Account Balance
016Report Balance
017Brought Forward
018Period Total
019END OF REPORT
020 TRIAL
BALANCE

Printed Output
022Account Account Name Account

Opening Peri
023 Code Type
Balance Debi
024Total @@@@@@@@@@
025Ledger Total
@@@@@@@@@@@@@@@@@@@@ @
026DEBTOR //
027CREDITOR //
028PROFIT & LOSS //
029BALANCE SHEET //
030Summary //
031
032Account Code: Priority: Base Date:
033 To: To:
034 Date Reference Description
035 Alloc Due After Due
Due
036 Withhold Alloc Due Due
Due
037Withhold Payment
038Payment
040Account Total //
041Discount Days:
042Report Total //
043AGED DEBTOR ANALYSIS
/044AGED CREDITOR ANALYSIS

Chapter 6 User Hooks
6
Several SunSystems v4 programs include a ‘user hook’ facility. This means that at certain
points in the program a subprogram can be called. The subprogram is written externally,
usually to carry out special validation, and is written for a specific operator. At the start of the
SunSystems v4 program, it checks for the existence of the user hook, which is done by
actually calling the subprogram.
If a subprogram is present, then the main program calls it at the appropriate times. Otherwise,
it ignores any user hook processing.
On returning to the main program, the content of relevant fields is checked, and the program
will act accordingly. For example, it might display a message set up by the user hook
program.
The programs that offer this facility are:
 AA=Account Allocation
 AQ=Account Inquiry
 JE=Journal Entry
 JI=Journal Import
 GP=Generate Payments
 GD=Generate Debits
 Reference Maintenance
 Reference Maintenance Special Edit
 SE=Sales Order Entry
 SI=Sales Order Import
 PE=Purchase Order Entry
 PI=Purchase Import
 VE=Purchase Invoice Entry
 VM=Purchase Invoice Matching
 GM=Goods Receipt Matching
Each is discussed in detail in this section.
Note for VAX/VMS users: The sub-program should be linked with the other
SunSystems v4 object programs in SUN.EXE.
Reference maintenance user hook SSRUEXT

The user hook facility is available when you are updating reference records which have been
defined by the relevant reference layout files, and a field has a special validation parameter of
EXT. See the section Reference Maintenance. On entering that field, the reference
maintenance program (SSRU) will call the user hook program. This program must be called
SSRUEXT. It can be used to perform additional validation for that field, and can instruct SSRU
to display a message and/or re-accept that field, or to continue on to the next.
The following linkage section is used to transfer data to and from the routine:
01 EXTERNAL-EDIT-DATA.
03 EXTERNAL-RECORD-ID PIC X(03).
03 EXTERNAL-ITEM-NO PIC 9(03).
03 EXTERNAL-UPDATE-MODE PIC X(01).

User Hooks
03 EXTERNAL-ERROR-MESSAGE PIC X(79).

03 EXTERNAL-REENTER PIC X(01).
03 EXTERNAL-ITEM PIC X(30).
03 EXTERNAL-PRIOR-ITEM PIC X(30).
where:
EXTERNAL-RECORD-ID - is the reference record type.
EXTERNAL-ITEM-NO - is the current field number.
EXTERNAL-UPDATE-MODE - is the reference maintenance update mode. This can be
any of the valid selection box entries. For example, C-Create or A-Amend. Note that this
action will vary if other language versions are in use.
EXTERNAL-ERROR-MESSAGE - is an error message returned from the external
routine. This message will be displayed by the reference maintenance program if it is not
spaces.
EXTERNAL-REENTER - is returned by the external routine. ‘Y’ indicates that the field
was in error and must be re-accepted. ‘N’ or a space indicates that the field was valid and
so the next field can be accepted.
EXTERNAL-ITEM - is the data typed in the field to be handed to the external routine.
EXTERNAL-PRIOR-ITEM - is the content of the field before being changed by operator
input.
In addition, the standard SunSystems v4 linkage area is available.
The format of the call statement from SSRU is:
CALL EXTERNAL-EDIT-PROG USING EXTERNAL-EDIT-DATA,
LINK-RECORD
The reference maintenance program will redisplay the field immediately on return so that any
changes made to the data by SSRUEXT are shown.
Report formatter amount in words hook

SSRF??EX
The indicator on report definition, which defines the language to be used in word sentence
construction, currently allows settings of 1 through to 4, but this has been expanded to accept
the standard numeric language codes supported by SunSystems v4. The two types of word
sentences that can be passed are amount in words and date in words.
When word sentence construction is requested, the language code will be checked and, if set
to anything other than English (01), will result in a call to a user hook for the appropriate
language code (i.e. SSRFnnEX where nn is the language code), to construct the word
sentence.
01 WS-USER-AREA.
03 WS-USER-DEFAULT-DEC-PL PIC 9.
03 WS-USER-DATE-FORMAT PIC X.
03 WS-USER-SENTENCE-AMOUNT PIC 9(10)V9(3).
03 WS-USER-SENTENCE-DATE PIC 9(8).
03 WS-USER-SENTENCES.
05 WS-USER-SENTENCE1 PIC X(80).

User Hooks

03 WS-USER-SENTENCE REDEFINES WS-USER-SENTENCES PIC X(80) OCCURS
4.
03 WS-USER-SENTENCE-LENGTHS.
05 WS-USER-SENTENCE1-LGTH PIC 99.
03 WS-USER-SENTENCE-LGTH REDEFINES WS-USER-SENTENCE-LENGTHS PIC
99 OCCURS 4.
03 WS-USER-ERROR-IND PIC XX.
where:
WS-USER-DEFAULT-DEC-PL – is the number of decimal places in the amount passed.
WS-USER-DATE-FORMAT – is the date format required.
Valid date formats are:
– 1 = 03 November 2010
– 2 = 3 November, 2010
– 3 = November 3, 2010
– 4 = 3-Nov-2010
– 5 = November 10
– 6 = Nov, 10
– 7 = 3rd November 2010
– 8 = November 3rd 2010
– A = mm/dd/yyyy
– B = dd/mm/yyyy
– C = yyyy/mm/dd
WS-USER-SENTENCE-AMOUNT - Amount to be converted to words from the report
formatter.
WS-USER-SENTENCE-DATE - Date to be converted to words from the report formatter.
WS-USER-SENTENCES - Area to return the amount in words from the user hook. There
are four areas of 80 bytes each.
WS-USER-SENTENCE-LENGTHS - The lengths from the report formatter of the amount
in words in the four areas of linkage.
WS-USER-ERROR-IND - The user hook should set this to Y if the amount or date in
words is too long for the area defined.
In addition, the standard SunSystems v4 linkage area, report formatter linkage area and
report format layout are available. The format of the call statement is:
CALL EXTERNAL-EDIT-PROG USING WS-USER-AREA
RFLINK-COMMON-RECORD
LINK-RECORD
REPFMT-ITEM-RECORD.
Journal Entry/Import user hook

SAJEEXT/SAJIEXT
The user hook program for JE=Journal Entry must be called SAJEEXT. If this program exists,
the JE=Journal Entry function calls it after each line created or amended on the journal, so
the hook program can be used for extra validation.

User Hooks
The fields passed to the sub-program are:

01 WS-USER-RECORD PIC X(512).
01 WS-USER-LINK-AREA.
03 WS-USER-DATABASE-CODE PIC X(3).
03 WS-USER-OPERATOR-ID PIC X(3).
03 WS-USER-ACC-RECORD PIC 1024.
03 WS-USER-TRANS-LINE-NO PIC 9(03) .
01 WS-USER-STATUS PIC X(1).
01 WS-USER-MESSAGE PIC X(80).
where:
WS-USER-RECORD - Holds the current transaction line in SAF (ledger backup) format.
WS-USER-DATABASE-CODE - Holds the current database code.
WS-USER-OPERATOR-ID - Holds the operator Id.
WS-USER-ACC-RECORD - Holds the CA=Charts of Accounts record for the account
currently being processed.
WS-USER-TRANS-LINE-NO - Holds the line number of the journal about to be posted.
This field is only valid in SAJE.
In addition, the standard SunSystems v4 linkage area is available. The format of the call
statement is:
CALL WS-USER-PROG USING WS-USER-RECORD,
WS-USER-LINK-AREA,
WS-USER-STATUS,
WS-USER-MESSAGE,
LINK-RECORD.
On returning to JE=Journal Entry, if WS-USER-MESSAGE is not spaces, then it will be
displayed on the JE=Journal Entry screen. If WS-USER-STATUS is ‘E’, then JE=Journal
Entry assumes the current line is invalid and goes back to the period box ready to accept that
line again. If at the posting stage, then posting will not take place.
WS-USER-STATUS may also be set to A’, which means the hook program has changed the
content of the current transaction record and JE=Journal Entry must reset its own fields
accordingly, or it may be ‘F’, which means the hook program has changed the content of the
record but there is an error, so the line must be re-entered (as with ‘E’).
There is also an initial ‘start-of-session’ call, an ‘end-of-journal’ call and an ‘end-of-session’
call. See the following for details of the content of the linkage fields for each of these calls to
the sub-program, and whether JE=Journal Entry will take heed of the content of WS-USER-
STATUS and WS-USER-MESSAGE when control is passed back to it. This facility is also
available with JI=Journal Import, where the program would be called SAJIEXT. In this case, if
the user hook returns a status of ‘E’ or ‘F’ during the validation of transactions phase, then the
transaction is rejected. If the message is not blank, then the first ten characters of the
message will be printed on the journal import report next to the relevant transaction.
When amending data on the journal line, only the following fields can be amended:
 Line Description
 Line Due Date
 Line Allocation
 Line Allocation Date
 Line Allocation Period
 Line Allocation Reference

User Hooks
 Line Transaction on Analysis Codes.
Call Contents of Contents of WS-USER- Responds to

WS-USER- LINK- AREA STATUS and
RECORD MESSAGE
1. Start of JE/JI SPACES DATABASE-CODE and NO

session OPERATOR-ID
2. Start of Journal ALL ‘S’ DATABASE-CODE and NO

OPERATOR-ID
3. End of Journal line CURRENT DATABASE-CODE, YES

TRANSACTI OPERATOR-ID and
ON ACCOUNT-RECORD
4. End of Journal ALL ‘E’ DATABASE-CODE and YES

(post) OPERATOR-ID
5. End of session ALL ‘Z’ SPACES NO
Account Allocation user hook SAAREXT

The user hook program for AA=Account Allocation must be called SAAREXT.
The first call to this program has WS-USER-STATUS set to spaces. If the user requires, this
field can then be set to ‘Y’ and alternative user hook handling occurs. If this program exists
and the field WS-USER-STATUS is not returned with a value of ‘Y’ then AA=Account
Allocation function calls it just before a ledger transaction is either amended or created. This
user hook is a read only program and does not update the transactions being posted.
If the WS-USER-STATUS field is set to 'Y' by the SAAREXT program in the first call, this calls
SAAREXT again when the user selects Action >> Post. Amended, created and generated
transactions are written to a file called SAXX-xxx.DAT where xxx is the operator Id. The user
hook is then called with WS-USER-STATUS set to ‘E’ and WS-USER-MESSAGE set to the
path and name of the new file. On return, if WS-USER-MESSAGE is not spaces, because the
changes did not meet the external program's validation criteria, the contents of WS-USER-
MESSAGE is displayed at the bottom of the screen and posting is halted. If this field is blank,
there is no error and the transactions can be posted.
The fields passed to the sub-program are:
01 WS-USER-RECORD.
03 WS-USER-STATUS PIC X.
03 WS-REST PIC x(431).
03 WS-USER-SPLIT PIC X(1).
03 WS-USER-AMEND PIC X(1).
03 WS-USER-ALLOC PIC X(1).
03 WS-USER-GENERATE PIC X(1).
where:

User Hooks
WS-USER-RECORD - initially holds WS-USER-STATUS and WS-USER-MESSAGE for

the alternative usage of this user hook. Subsequently, holds the current transaction line in
SAF (ledger backup) format.
WS-USER-SPLIT - is set to ‘Y’ if the transaction was created because of a split
transaction in account allocation.
WS-USER-AMEND - is set to ‘Y’ if the transaction was amended in account allocation.
WS-USER-ALLOC - is set to ‘Y’ if the transaction was allocated in account allocation.
WS-USER-GENERATE - is set to ‘Y’ if the transaction was created by a generated
journal in account allocation.
The layout of SAXX.xxx.DAT (if used) is as follows:
01 LDGTMP-RECORD.
03 LDGTMP-KEY.
05 LTMP-UNIQUE PIC 9(7).
05 LDG-TMP-KEY.
07 LDGTMP-AC PIC X(15).
07 LDGTMP-ALTERNATE-KEY.
09 LTMP-JN-X.
11 LTMP-JN PIC S9(07) COMP-3.
09 LTMP-TN-X.
11 LTMP-TN PIC S9(7) COMP-3.
03 LDGTMP-DAT
05 LDGTMP-TYPE PIC X.
05 LDGTMP-REST PIC X(367).
statement is:
CALL WS-USER-PROG USING WS-USER-RECORD
WS-USER-LINK-AREA
LINK-RECORD.
Account Allocation user hook SAAREXT2

The user hook program for account allocation/inquiry must be called SAAREXT2. If this
program exists, the AA=Account Allocation or AQ=Account Inquiry function calls it if the
operator has entered the F5 key when the cursor is in the selection box. This user hook is a
read only program and will not update any records passed to it. The fields passed to the sub-
program are:
01 WS-USER-ACCOUNT-RECORD PIC 1024.
where:
WS-USER-ACCOUNT-RECORD - Holds the account record for the account currently
being processed or queried.
statement is:
CALL WS-USER-PROG-2 USING WS-USER-ACCOUNT-RECORD
LINK-RECORD

User Hooks
Generate Payments/Debits user hook SAGPEX

The user hook is not called directly by the generate payments/debits functions, rather it is
called after the GP=Generate Payments or GD=Generate Debits functions have completed
processing. This user hook can then read and amend the payment file before print
remittances processes and then deletes the payment file.
Generate payments/debits takes note of two new ‘process modes’. For instructions on how to
set up the process mode for on the MM01 Selection Menu see the section Screens and
Menus. So the following are valid process modes for calling the generate payments/debits
program (SAGP) and how that program will handle those codes:
 0 = Generate Payments, No Call to User Hook
 1 = Generate Debits, No Call to User Hook
 2 = Generate Payments, Call to User Hook
 3 = Generate Debits, Call to User Hook
If the process mode is set to 2 or 3, the program, on completing successfully, will pass control
to program SAGPEX.
Depending on the setting of the force journal listing indicator, generate payments may pass
control to journal listing prior to print remittance. If the process mode is set to 2 or 3, this link
will be by-passed, therefore this link will need to set up by the user hook program (SAGPEX).
The processing to determine which program is called next will remain in generate payments
and if the user hook is called next, will be reflected in the value assigned to the LINK-
PROCESS-MODE indicator.
The LINK-PROCESS-MODE will be set to one of the following values when control is passed
to SAGPEX:
 2 = from Generate Payments, no link to Journal Listing required
 3 = from Generate Debits, no link to Journal Listing required
 4 = from Generate Payments, link on to Journal Listing (Direct Print)
 5 = from Generate Debits, link on to Journal Listing (Direct Print)
 6 = from Generate Payments, link on to Journal Listing (Store Print)
 7 = from Generate Debits, link on to Journal Listing (Store Print)
The user hook will need to set the following linkage area depending on the LINKPROCESS-
MODE. To link to journal listing set LINK-SUBSEQUENT-PROG to “SAAS” and LINK-NEXT-
PROGRAM-ID to “SAJL”. The LINK-PROCESSMODE is set to 2 if printing direct and to 3 if
storing to disk.
If linking directly to print remittance, LINK-PROCESS-MODE should be set to 2, and LINK-
NEXT-PROGRAM-ID to “SAAS”.
Sales Order Entry/Import user hook SBTDEXT

The user hook program for SE=Sales Order Entry and SI=Sales Order Import must be called
SBTDEXT. If this program exists, the sales order entry program will call the user hook after
each calculation code and item code, before the calculation code designated as the inventory
quantity, for each line created or amended on the SE=Sales Order Entry, Items screen. There
is also an initial call and a final call to the sub-program. SI=Sales Order Import behaves in the
same way except you will not be amending lines, just creating them.
The user hook can be used to amend the following values on an SE=Sales Order detail line:
calculation codes, analysis codes (M-codes), inventory quantity, and also the account code. It
can also write new description records.

User Hooks

*
* Record Layout for Order Detail Record (Backup Form)
01 FILLER REDEFINES WS-USER-RECORD.
03 WS-USER-KEY.
05 WS-USER-TRANS-TYPE PIC X(01).
* Type “D”, Order detail record.
* Type “E”, Quotation detail record.
05 WS-USER-TRANS-REF.
07 WS-USER-TRANS-PREF PIC X(04).
07 WS-USER-TRANS-SUFF PIC X(06).
05 WS-USER-TRANS-LINE-NO.
07 WS-USER-TRANS-LINE-NUMBER PIC 9(03).
07 WS-USER-TRANS-LINE-SUFF.
09 WS-USER-TRANS-LINE-SUFF-A PIC X(01).
09 WS-USER-TRANS-LINE-SUFF-B PIC X(01).
03 WS-USER-ALTERNATE-KEY.
05 WS-USER-KEY-ID PIC X(01).
05 WS-USER-LOCATION PIC X(05).
05 WS-USER-ITEM-CODE.
07 WS-USER-ITEM-CODE-1 PIC X(01).
05 WS-USER-TRANS-DATE-X.
07 WS-USER-TRANS-DATE PIC 9(8).
05 WS-USER-SEQUENCE-X.
07 WS-USER-SEQUENCE PIC 9(4).
03 WS-USER-DATA.
05 WS-USER-STATUS.
07 WS-USER-STATUS-1 PIC 9(01).
07 WS-USER-STATUS-2 PIC 9(01).
05 WS-USER-TRANS-CD PIC X(01).
05 WS-USER-ITEM-DESCRIPTION PIC X(030)
* Calculation code values
07 FILLER OCCURS 20.
09 WS-USER-VALUE PIC S9(13)V9(5) SIGN LEADING
SEPARATE.
05 WS-USER-VALUES-R REDEFINES WS-USER-VALUES.
07 WS-USER-VALUE-1 PIC S9(13)V9(5) SIGN LEADING
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.

User Hooks

SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
05 WS-USER-VALUEXS REDEFINES WS-USER-VALUES.
07 FILLER OCCURS 20.
09 WS-USER-VALUEX PIC X(19).
05 WS-USER-VALUEXS-R REDEFINES WS-USER-VALUES.
07 WS-USER-VALUEX-1 PIC X(19).

User Hooks

05 WS-USER-MISC-DATA.
07 WS-USER-TRANS-CODE PIC X(05).
07 WS-USER-DATE-DELIVERED PIC 9(08).
07 WS-USER-DATE-INVOICED PIC 9(08).
07 WS-USER-PERIOD-ORDERED PIC 9(07).
07 WS-USER-PERIOD-INVOICED PIC 9(07).
07 WS-USER-UNIT-SALE PIC X(05).
07 WS-USER-INVOICE-NO PIC X(15).
07 WS-USER-ACK-PRINT PIC X(01).
07 WS-USER-MISC-PRINT PIC X(01).
05 WS-USER-ALLOCATION-REF PIC X(19).
05 WS-USER-RECPT-REF PIC X(15).
05 WS-USER-LINE-ANAL-IND PIC X(01).
05 WS-USER-ACCOUNT-CODE PIC X(15).
05 WS-USER-ASSET-CODE PIC X(10).
05 WS-USER-ASSET-SUB-CODE PIC X(5).
05 WS-USER-ASSET-IND PIC X(01).
05 WS-USER-ID-ENTERED PIC XXX.
05 WS-USER-ID-INVOICED PIC XXX.
05 WS-USER-LINKED-TEXT PIC X(01).
05 WS-USER-ANALYSIS-CODES.
07 WS-USER-ANALYSIS-CODE PIC X(15) OCCURS 10.
05 WS-USER-ANALYSIS-CODES-R REDEFINES WS-USER-ANALYSIS-CODES.
07 WS-USER-ANALYSIS-CODE-1 PIC X(15).
05 WS-USER-ASSEMBLY-IND PIC X(01).
05 WS-USER-ASSEMBLY-DESC-IND PIC X(01).
05 WS-USER-ASSEMBLY-LEVEL-IND PIC X(01).
05 WS-USER-PRICE-BOOK PIC X(05).
05 WS-USER-SALES-QTY-VALUE PIC 9(2).
05 WS-USER-STOCK-QTY-VALUE PIC 9(2).
05 WS-USER-TOTAL-VALUE PIC 9(2).
05 WS-USER-DISPLAY-VALUES.
07 WS-USER-DISPLAY-VALUE-1 PIC 9(2).

User Hooks

05 FILLER REDEFINES WS-USER-DISPLAY-VALUES.
07 WS-USER-DISPLAY-VALUE OCCURS 3 PIC 9(2).
05 FILLER PIC X(2).
*
* User Hook Order Header record
*
*
03 WS-ACTION PIC 99 VALUE 99.
*
03 WS-CALLING-FLAGS PIC X(50).
03 WS-CALCULATION-CODE PIC X(3).
03 WS-CALCULATION-NUMBER PIC 99.
03 WS-RECORDS-ADDED PIC 99.
03 WS-USER-MESSAGE.
04 WS-MESS-PART1 PIC X(40).
01 FILLER REDEFINES WS-USER-HEADER.
03 WS-USER-H-KEY.
05 WS-USER-H-TRANS-TYPE PIC X(01).
* Type “O” - Order header record
* Type “I” - Invoice header record
* Type “Q” - Quotation header record
05 WS-USER-H-TRANS-REF.
07 WS-USER-H-TRANS-PREF PIC X(04).
07 WS-USER-H-TRANS-SUFF PIC X(06).
03 WS-USER-H-ALTERNATE-KEY.
05 WS-USER-H-KEY-ID PIC X(01).
* Id = “H”
* Id = “Q”
05 WS-USER-H-CUSTOMER-CODE PIC X(10).
05 WS-USER-H-TRANS-DATE PIC 9(08).
03 WS-USER-H-DATA.
05 WS-USER-H-STATUS.
07 WS-USER-H-STATUS-1 PIC 9(01).
* Status-1: 0 = Awaiting Picking,
* 3 = Awaiting Despatch,
* 7 = Awaiting Invoice,
* 8 = Complete
07 WS-USER-H-STATUS-2 PIC 9(01).
* Status-2: 1 = Order Held
05 WS-USER-H-TRANS-CD PIC X(01).
05 WS-USER-H-TRANS-CODE PIC X(05).
05 WS-USER-H-ORDER-NO PIC X(10).

User Hooks
05 WS-USER-H-D-NOTE-NO PIC X(15).

05 WS-USER-H-DELIVERY-CODE PIC X(10).
05 WS-USER-H-DATE-ORDER PIC 9(08).
05 WS-USER-H-DATE-ACKNOWLEDGED PIC 9(08).
05 WS-USER-H-DATE-PICKED PIC 9(08).
05 WS-USER-H-DATE-DELIVERED PIC 9(08).
05 WS-USER-H-DATE-INVOICED PIC 9(08).
05 WS-USER-H-PERIOD-INVOICEDPIC 9(07).
05 WS-USER-H-CUSTOMER-REF PIC X(025).
05 WS-USER-H-COMMENTS PIC X(025).
05 WS-USER-H-TRANS-VALUE PIC S9(13)V9(5) SIGN LEADING
SEPARATE.
05 WS-USER-H-PAYMENT-DUE-DATE PIC X(8).
05 WS-USER-H-ANALYSIS-ADDRESS PIC X(01).
05 WS-USER-H-LINKED-TEXT PIC X(01).
05 WS-USER-H-ANALYSIS-CODES.
07 WS-USER-H-ANALYSIS-CODE PIC X(15) OCCURS 10.
05 WS-USER-H-ANALYSIS-CODES-R REDEFINES WS-USER-H-ANALYSIS-
CODES.
07 WS-USER-H-ANALYSIS-CODE-1 PIC X(15).
05 WS-USER-H-QUOTE-CONVERT PIC X(01).
05 WS-USER-H-QUOTE-PRINT PIC X(01).
05 WS-USER-H-QUOTE-EXPIRY-DATE PIC 9(8).
05 WS-USER-H-PERIOD-QUOTED PIC 9(7).
05 FILLER PIC X(5).
05 WS-USER-H-QUOTATION-REF PIC X(10).
05 WS-USER-H-DATE-QUOTED PIC 9(8).
where:
WS-USER-RECORD - Is the current order detail record in backup format.
WS-ACTION - Indicates what stage in the processing the SE=Sales Order Entry,
SI=Sales Order Import program is at when it calls the user hook:
– 00 - Initialisation
– 01 - Creation of detail line
– 02 - Amendment of detail line (SE only),
– 09 - Termination of sales entry items/sales import
– 98 - Last call to user hook before termination of user hook
– 99 - Test if the user hook is present.
Other values should be ignored by the hook program.

User Hooks
WS-CALLING-FLAGS - Indicate to the calling program when to call the sub-program.

These fields must be set to Y or blank by the user hook during the initialisation call.
– Characters 1 to 20 correspond to the 20 calculation codes, and should be set to Y if the
user hook is to be called after that calculation code.
– Characters 21 to 30 are not currently used.
– Character 31 indicates whether the user hook should be called directly after the item code
has been entered.
– Character 32 indicates whether the user hook should be called prior to entering the
inventory quantity in SE=Sales Order Entry. The quantity returned by the user hook will be
displayed on the screen and, unless the operator amends it on the screen, this quantity
will be used for all further calculations.
– Character 33 is not currently used.
– Character 34 indicates whether the user hook should be called just prior to writing or
rewriting the detail record.
– Characters 35 to 50 are not defined.
WS-CALCULATION-CODE - Contains the calculation code currently being processed.
WS-CALCULATION-NUMBER - Contains the sequence number of the calculation code
being processed at the time, i.e. 1 to 20, or 34 for end-record processing.
WS-RECORDS-ADDED - Contains the number of description records added by the user
hook.
WS-USER-MESSAGE - Contains a message passed by the user hook to the calling
program after the end-processing call to the user hook. The calling program will
display/print the message providing WS-USERLINK- STATUS is set to E or W.
WS-USER-LINK-STATUS - Indicates whether or not an error has occurred in the hook
prior to returning from the end-record processing hook:
– E - An error has occurred. WS-USER-MESSAGE will be displayed on return from the
hook and the current line is assumed to be invalid.
– W - A discrepancy has occurred. WS-USER-MESSAGE will be displayed on return from
the hook and normal processing will continue.
– Blank - Normal processing will continue.
WS-USER-HEADER - Is the current order header in backup format.
Nothing in the order header may be updated by the user hook.
WS-USER-LINK-AREA,
WS-USER-LINK-STATUS,
WS-USER-HEADER
LINK-RECORD
Purchase Order Entry/Import user hook

SPPDEXT
The user hook program for PE=Purchase Order Entry and PI=Purchase Import must be
called SPPDEXT. If this function exists, the purchase order entry program will call the user
hook after each calculation code and item code, before the purchase and inventory quantities
for each line created or amended on the PE=Purchase Order Entry, Items screen. There is
also an initial call and a final call to the sub-program.
The user hook can be used to amend the following values on a PE=Purchase Order Entry
detail line: the purchase and inventory quantities, the calculation codes, analysis codes (M-

User Hooks
codes), account code, asset code and asset subcode. It can also write new description
records.
The format of the call statement is:
* Record Layout for Purchase Order Detail Record (Backup Form)
01 FILLER REDEFINES WS-USER-RECORD.
03 WS-USER-KEY.
05 WS-USER-REC-TYPE PIC X(01).
05 WS-USER-REFERENCE-LINE.
07 WS-USER-REFERENCE.
09 WS-USER-REF-PREFIX PIC X(04).
09 WS-USER-REF-SUFFIX PIC 9(06).
07 WS-USER-LINE-NO.
09 WS-USER-LINE-NO-A PIC 9(03).
09 WS-USER-LINE-NO-B PIC X(01).
03 WS-USER-DATA.
05 WS-USER-ALTERNATE-KEY-1.
07 WS-USER-KEY-1-ID PIC X(01).
07 WS-USER-LOCATION PIC X(05).
07 WS-USER-ITEM-CODE PIC X(15).
07 WS-USER-DEL-DATE PIC 9(08).
07 WS-USER-SEQUENCE PIC 9(04).
05 WS-USER-ALTERNATE-KEY-2.
07 WS-USER-KEY-2-ID PIC X(01).
07 WS-USER-HIGHEST-REFERENCE PIC X(10).
05 WS-USER-REST-OF-DATA.
07 WS-USER-ORDER-STATUS.
09 WS-USER-ORDER-STATUS-1 PIC 9(01).
09 WS-USER-ORDER-STATUS-2 PIC 9(01).
07 WS-USER-GRN-STATUS.
09 WS-USER-GRN-STATUS-1 PIC 9(01).
09 WS-USER-GRN-STATUS-2 PIC 9(01).
07 WS-USER-INVOICE-STATUS.
09 WS-USER-INVOICE-STATUS-1 PIC 9(01).
09 WS-USER-INVOICE-STATUS-2 PIC 9(01).
07 WS-USER-CD PIC X(01).
07 WS-USER-LINKED-TEXT PIC X(01).
07 WS-USER-ID-ORDER PIC X(03).
07 WS-USER-ID-GRN PIC X(03).
07 WS-USER-ID-INVOICED PIC X(03).
07 WS-USER-SUPP-ITEM-DESC PIC X(30).
07 WS-USER-SUPP-ITEM-CODE PIC X(15).
07 WS-USER-PURCH-QTY PIC S9(13)V9(05) SIGN LEADING SEPARATE.
07 WS-USER-PURCH-UNIT PIC X(05).

User Hooks
07 WS-USER-STOCK-QTY PIC S9(13)V9(05) SIGN LEADING SEPARATE.

07 WS-USER-BASE-COST PIC S9(13)V9(05) SIGN LEADING SEPARATE.
07 WS-USER-CALC-VALUES.
09 WS-USER-CALC-VALUE-1 PIC S9(13)V9(05) SIGN LEADING
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
SEPARATE.
07 WS-USER-CALC-VALUE REDEFINES WS-USER-CALC-VALUES PIC
S9(13)V9(05)
SIGN LEADING SEPARATE
OCCURS 17
07 WS-USER-GRN-REFERENCE PIC X(10).
07 WS-USER-GRN-DATE PIC 9(08).
07 WS-USER-DEL-ADVISED PIC X(01).
07 WS-USER-INV-DATE PIC 9(08).
07 WS-USER-INV-PERIOD PIC 9(07).
07 WS-USER-INV-APPROV-DATE PIC 9(08).
07 WS-USER-TRANS-TYPE PIC X(05).

User Hooks
07 WS-USER-STOCK-UPDATED PIC X(01).

07 WS-USER-REASON-CODE PIC X(01).
07 WS-USER-LINE-VALUE PIC 9(02).
07 WS-USER-MATCH-VALUE PIC 9(02).
07 WS-USER-COST-VALUE PIC 9(02).
07 WS-USER-ACCOUNT-CODE PIC X(15).
07 WS-USER-ASSET-CODE PIC X(10).
07 WS-USER-ASSET-SUB-CODE PIC X(05).
07 WS-USER-ASSET-IND PIC X(01).
07 WS-USER-RECEIPT-REF PIC X(15).
07 WS-USER-AUDIT-DATE PIC 9(08).
07 WS-USER-ANAL-CODES.
09 WS-USER-ANAL-CODE-0 PIC X(15).
07 WS-USER-ANAL-CODE REDEFINES WS-USER-ANAL-CODES PIC X(15)
OCCURS 10.
07 WS-USER-UNAPP-PERIOD-POSTED PIC 9(7).
07 WS-USER-ORDER-DATE PIC 9(8).
07 WS-USER-STOCK-PERIOD-POSTED PIC 9(7).
07 WS-USER-PERIOD-ORDERED PIC 9(7).
07 WS-USER-AMEND-DATE PIC 9(8).
07 WS-USER-ORIG-LINE-NO-X.
09 WS-USER-ORIG-LINE-NO-A PIC 999.
09 WS-USER-ORIG-LINE-NO-B PIC X.
07 WS-USER-MVT-VALUE PIC S9(13)V9(5).
07 WS-USER-BCHECK-VALUE PIC 99.
07 WS-USER-EXPEND-VALUE PIC 99.
03 WS-ACTION PIC 99 VALUE 99.
03 WS-CALLING-FLAGS PIC X(50).
03 WS-CALCULATION-CODE PIC X(03).
03 WS-CALCULATION-NUMBER PIC 9(02).
03 WS-RECORDS-ADDED PIC 9(02).
01 WS-USER-LINK-STATUS PIC X(01).
01 WS-USER-HEADER.
03 WS-USER-HEADER-ORDER PIC X(700).
03 WS-USER-HEADER-INVOICE PIC X(700).
01 WS-USER-J-RECORD.

User Hooks
* Purchase Order Header Record.

03 WS-USER-J-KEY.
05 WS-USER-J-REC-TYPE PIC X(01).
* Record Type = “J”.
05 WS-USER-J-REFERENCE.
07 WS-USER-J-REF-PREFIX PIC X(04).
07 WS-USER-J-REF-SUFFIX PIC 9(06).
03 WS-USER-J-DATA.
05 WS-USER-J-ALTERNATE-KEY-1.
07 WS-USER-J-KEY-1-ID PIC X(01).
07 WS-USER-J-SUPP-ADDRESS PIC X(10).
07 WS-USER-J-ORDER-DATE PIC 9(08).
05 WS-USER-J-ALTERNATE-KEY-2.
07 WS-USER-J-KEY-2-ID PIC X(01).
07 WS-USER-J-SECOND-REF PIC X(15).
05 WS-USER-J-REST-OF-DATA.
07 WS-USER-J-STATUS.
09 WS-USER-J-STATUS-1 PIC 9(01).
09 WS-USER-J-STATUS-2 PIC 9(01).
07 WS-USER-J-CD PIC X(01).
07 WS-USER-J-TRANS-TYPE PIC X(05).
07 WS-USER-J-DEL-ADDRESS PIC X(10).
07 WS-USER-J-COMMENTS PIC X(25).
07 WS-USER-J-ACK-REF PIC X(15).
07 WS-USER-J-ACK-DATE PIC 9(08).
07 WS-USER-J-DEL-DATE PIC 9(08).
07 WS-USER-J-DEL-ADVISED PIC X(01).
07 WS-USER-J-ORDER-VALUE PIC S9(13)V9(05) SIGN LEADING
SEPARATE.
07 WS-USER-J-ORDER-QUANTITY PIC S9(13)V9(05) SIGN LEADING
SEPARATE.
07 WS-USER-J-ORDER-PERIOD PIC 9(7).
07 WS-USER-J-LINKED-TEXT PIC X(01).
07 WS-USER-J-ANAL-CODES.
09 WS-USER-J-ANAL-CODE-0 PIC X(15).

User Hooks
07 WS-USER-J-ANAL-CODE REDEFINES WS-USER-J-ANAL-CODES PIC

X(15) OCCURS 10.
07 WS-USER-J-DOC-ISSUE-DATE PIC 9(08).
07 WS-USER-J-GRN-IND PIC X(01).
07 WS-USER-J-ID-RELEASED PIC X(03).
07 WS-USER-J-POST-UNAPP-GRN PIC X(01).
01 WS-USER-L-RECORD.
* Invoice Header Record.
03 WS-USER-L-KEY.
05 WS-USER-L-REC-TYPE PIC X(01).
*Record Type = “L”.
05 WS-USER-L-REFERENCE.
07 WS-USER-L-REF-PREFIX PIC X(04).
07 WS-USER-L-REF-SUFFIX PIC 9(06).
03 WS-USER-L-DATA.
05 WS-USER-L-ALTERNATE-KEY-1.
07 WS-USER-L-KEY-1-ID PIC X(01).
07 WS-USER-L-SUPP-ADDRESS PIC X(10).
07 WS-USER-L-INV-DATE PIC 9(08).
05 WS-USER-L-ALTERNATE-KEY-2.
07 WS-USER-L-KEY-2-ID PIC X(01).
07 WS-USER-L-SUPP-INV-REF PIC X(15).
05 WS-USER-L-REST-OF-DATA.
07 WS-USER-L-STATUS.
09 WS-USER-L-STATUS-1 PIC 9(01).
09 WS-USER-L-STATUS-2 PIC 9(01).
07 WS-USER-L-CD PIC X(01).
07 WS-USER-L-TRANS-TYPE PIC X(05).
07 WS-USER-L-COMMENTS PIC X(25).
07 WS-USER-L-PAY-DATE PIC 9(08).
07 WS-USER-L-MATCHED-TOT-QTY PIC S9(13)V9(05) SIGN LEADING
SEPARATE.
07 WS-USER-L-MATCHED-TOT-VAL PIC S9(13)V9(05) SIGN LEADING
SEPARATE.
07 WS-USER-L-INV-PERIOD PIC 9(7).
07 WS-USER-L-INV-TOT-QTY PIC S9(13)V9(05) SIGN
LEADING SEPARATE.
07 WS-USER-L-INV-TOT-VAL PIC S9(13)V9(05) SIGN
LEADING SEPARATE.
07 WS-USER-L-ORDER-REFERENCE PIC X(10).
07 WS-USER-L-LINKED-TEXT PIC X(01).
07 WS-USER-L-ANAL-CODES.

User Hooks
09 WS-USER-L-ANAL-CODE-0 PIC X(15).

07 WS-USER-L-ANAL-CODE REDEFINES WS-USER-L-ANAL-CODES PIC
X(15) OCCURS 10.
07 WS-USER-L-ID-RELEASED PIC X(03).
where:
WS-USER-RECORD - Is the current order detail record in backup format.
WS-ACTION - Indicates what stage in the processing the PE=Purchase Order Entry
program is at when it calls the user hook:
– 00 - Initialisation
– 01 - Creation of detail line
– 02 - Amendment of detail line
– 09 - Termination of purchase order entry items/ purchase import
– 98 - Last call to user hook before termination of user hook
– 99 Test if the user hook is present
Other values should be ignored by the hook program.
WS-CALLING-FLAGS - Indicate to the calling program when to call the Journal line sub-
program. These fields must be set to Y or blank by the user hook during the initialisation
call.
– Characters 1 to 17 correspond to the 17 calculation codes, and should be set to Y if the
user hook is to be called for that calculation code.
– Characters 18 to 30 are not currently used.
– Character 31 indicates whether the user hook should be called directly after the item code
has been entered.
– Character 32 indicates whether the user hook should be called prior to entering the
purchase order quantity in PE=Purchase Order Entry.
– The quantity returned by the user hook will be displayed on the screen and, unless the
operator amends it on the screen, this quantity will be used for all further calculations.
– Character 33 indicates the user program should be called just prior to accepting the
inventory quantity in PE=Purchase Order Entry.
– The quantity returned by the user hook will be displayed on the screen and, unless the
operator amends it on the screen, this quantity will be used for all further calculations.
– Character 34 indicates whether the user hook should be called just prior to writing or
rewriting the detail record.
– Characters 35 to 50 are not defined.
WS-CALCULATION-CODE - Contains the calculation code currently being processed.
WS-CALCULATION-NUMBER - Contains the number of the flag being processed at the
time.
WS-RECORDS-ADDED - Contains the number of description records added to the order
by the user hook.

User Hooks
WS-USER-MESSAGE - Contains a message passed by the user hook to the calling

program after the end-record processing call to the user hook. The calling program will
display the message providing WS-USER-LINK-STATUS is set to E or W.
WS-USER-LINK-STATUS - Indicates whether or not an error has occurred in the hook
prior to returning from the end-processing call to the user hook.
– E - An error has occurred. WS-USERMESSAGE will be displayed on return from the hook
and the current detail line is assumed to be invalid.
– W - A discrepancy has occurred. WSUSER-MESSAGE will be displayed on return from
the hook and the calling program will continue normal processing.
– Blank - Normal processing will continue.
WS-USER-HEADER - Is the current order and invoice headers in backup format. If both
order and invoice headers are present, then they will both be in linkage.
Nothing in the order or invoice header may be updated by the user hook.
WS-USER-LINK-AREA,
WS-USER-LINK-STATUS,
WS-USER-HEADER
LINK-RECORD
Note: The account code can only be amended using end-record processing.
Link to Journal Import

It is possible to run JI=Journal Import on exiting from another program without actually
entering the JI=Journal Import screen in the usual way.
The program that links to the JI=Journal Import module in this case must be a SunAccount
program, accessible from the LA=Ledger Accounting, AR=Fixed Asset Register or
CO=Corporate Allocations menus, and should have a prefix of SA, SF or SC accordingly. It
must use the standard SunSystems v4 linkage copy member as part of its linkage section.
Prior to exiting the user program, the following linkage parameters must be set:
LINK-NEXT-PROGRAM-ID SATF (JI=Journal Import program name).
LINK-SUBSEQUENT-PROG User program name, if it is required to return to

the user module.
LINK-PROCESS-MODE ‘1’ for batch mode.
LINK-ALLOCATIONS-AREA Spaces (group field).
LINK-JI-SUCCESS-CODE Zeros.
LINK-JI-JOURNAL-NUMBER-FROM Zeros.
LINK-JI-JOURNAL-NUMBER-TO Zeros.
LINK-JI-NUMBER-LINES Zeros.

User Hooks
LINK-JI-TOTAL-AMOUNT Zeros.
LINK-JI-DATABASE-CODE Database code of database to which the journal

should be posted. This field is mandatory and
must be set even if the database code required
is the same as the current database.
LINK-JI-AB A (Actuals), which is the default, or B-K

(Budgets). This field is mandatory.
LINK-JI-IMPORT-FILE-NAME The name of the file to be imported by the

JI=Journal Import program (mandatory).
LINK-JI-PRINT-OR-STORE P-Print Report, S-Store on Disk (default) the

journal import report.
LINK-JI-POST-TRANSACTIONS N to validate only (default), or a space to post if

there are no errors.
LINK-JI-PROCESS-ROUGH Spaces or Y (in English) if the journals posted

are to be rough and rough book processing is
defined.
LINK-JI-ALLOW-BAL-TRANS Y or N.
LINK-JI-SUSPENSE-AC Spaces or account code.
JI=Journal Import will validate and post the import transactions according to the preceding
link parameters settings. A JL=Journal Listing will be done in the usual way if Force Journal
List is set on the LD=Ledger Definition.
If LINK-SUBSEQUENT-PROGRAM is set to the user program name, then control will be
passed back to the top of that program on exiting from JI=Journal Import. If this is the case,
then the following parameters will be set for the user program to use:
LINK-JI-SUCCESS-CODE Zero if link/posting procedure was successful.
LINK-JI-JOURNAL-NUMBER- First journal number of journal posted, if any.

FROM
LINK-JI-JOURNAL-NUMBER-TO Last journal posted. There may be multiple journals

because of rough book processing.
LINK-JI-NUMBER-LINES Number of lines posted, if any.
LINK-JI-TOTAL-AMOUNT Total amount posted, if any.

User Hooks
File Backup user hook SSFBEXT

The user hook program for file backup must be called SSFBEXT. If this program exists, the
FB=File Backup/Restore function will call the user hook just before writing any record to any
SunSystems v4 backup file.
01 WS-EXTERNAL-FILE-CODE PIC X(03).
01 WS-EXTERNAL-RECORD PIC X(800).
where:
WS-EXTERNAL-FILE-CODE - Is the three character mnemonic for the file the operator is
backing up. These can be found in SSFHWS.CPY.
WS-EXTERNAL-RECORD - Is the record passed to the user hook. The user hook may
amend any record, but the backup program will not validate the amendment.
CALL WS-USER-PROG USING WS-EXTERNAL-FILE-CODE
WS-EXTERNAL-RECORD.
Goods Receipt Matching

Call Points are available on the Goods Receipt Matching header and detail functions to allow
user hook programs to be called. In Header record processing, this is on release of the GRN;
in Detail record processing, this is at the end of a line and on release. They can also be called
at the start and end of the session.
Process Manager can be invoked at these points and hooks are available in UD=User Hook
Definition. The GRN Header Data Items and the GRN Detail Line Data Items are available for
selection in Event Profiles and Rule Sets.
UD=User Hook Definition

Overview
You can use this function to define user hook programs in SunSystems v4. It allows more
than one user hook program to be called from the same point. It also allows user hook
programs to be activated only when certain actions are used in the calling function. Finally, it
allows parameters to be passed to the user hook program. All user hooks that are used as
part of SunSystems v4 core functionality are included in the SunSystems v4 installation file,
and can be seen in UD=User Hook Definition.
Two types of user hook can be set up via the User Hook Definition screen:
Standard User Hook Definition
A standard user hook, called from one of the many SunSystems v4 programs, for example,
Journal Entry (SAJE) or Sales Order Entry.
Report Definition User Hooks
A Report Definition user hook, called each time Report Formatter processes an item defined
as a user hook item in a report or document.

User Hooks
Entries – Standard User Hook Definition
Calling Program
maximum 4 characters
Enter the filename without the extension of the calling program. This is the SunSystems v4
program that your user hook is being called from, for example, SAJE, SBTE.
Description
Enter a description for your user hook. For information only.
Number
maximum 999999
Enter the user hook sequence number. This is normally set to 1. This variable controls the
sequence in which multiple user hooks for the same calling program are processed. If adding
another user hook to be called from the same program as an existing user hook, use the next
available user hook number.
A maximum of 20 user hooks can currently be called from one point, except in Report
Formatter, where there is a limit of 50 user hooks per document or report.
User Hook Program
Enter the user hook program name. This is appended to the calling program name. Together
these two names make up the filename of the user hook. For example, if the calling program
is SAJE and the user hook program is EXT, the user hook that your program needs to be
called is SAJEEXT.
Start of Session
Y/blank
This is currently only used in Journal Entry and Journal Import. If the user hook is to be called
at the start of a session, set it to Y-Yes, followed optionally by the actions that should trigger
the use of the user hook. If no actions are entered, then the user hook is always called at the
start of each session. If actions are defined, then the user hook is only called at the start of
the session if one of the specified actions is the current action, for example 0001=amend,
0023=delete.
Actions
Actions are defined by using the number by which they are identified in the message file. See
the subsection Message Files in the Technical Reference Manual for a list of actions and their
codes.
End of Session
Y/blank
As for Start of Session above. This is currently only available for Journal Entry (SAJE) and
Journal Import (SATF).

User Hooks
Actions
the subsection Message Files in this manual for a list of actions and their codes.
Calling Points 1-4
Y/blank
Enter Y-Yes to use a particular calling point, or leave it blank. These calling points operate in
different ways depending upon which program the user hook is called from, see the
subsection User Hook Calling Points for further details.
Actions
the subsection Message Files in this manual for a list of actions and their codes.
Retain in Memory
Y/N/blank
This is used only by the functions Sales Order Entry, Purchase Order, and Invoice Entry. In
order to avoid reloading user hooks for each line, this flag can be set to cause them to be
loaded when passing from the header to the detail screen and they are then retained in
memory.
Data Items 1-4
These are optional entries with no validation. They can be used to pass nonnumeric data to a
user hook program where the user hook definition data is passed as part of the linkage.
Values 1-4
numeric 15.3
These are optional entries, but if present must be signed. They can be used to pass numeric
values data to a user hook program where the user hook definition data is passed as part of
the linkage.
Indicators 1-4
maximum 1 character
These are optional entries with no validation. They can be used to pass data to a user hook
program where the user hook definition data is passed as part of the linkage.
Document Type and Filter Code are currently not implemented.
Data Type
2 digits
This is used only for Report Definition user hooks, where it is mandatory and needs to be
completed with the type of box that is passed back to the formatter.
 01 Alphanumeric
 02 Period
 03 Date
 10-19 Signed numeric, where the second digit indicates the number of decimal places, for
example, 13 means signed numeric with 3 decimal places.

User Hooks
Entries – Report Definition user hooks
To set up a Report Definition user hook call that is actioned each time the box you wish to
print is processed by Report Formatter requires the following:
Firstly, you need to create a new user hook definition record as follows:
Calling Program
Enter SSRD for the user hook called from the Report Definition program.
Description
Enter a description for the user hook. For information only.
Number
This is the user hook number which is then entered in the user hook Item UHD box on the
report format. It is used to link the report format to the user hook.
User Hook Program
This is appended to the calling program name. For example, if you enter TST1, the user hook
program is called SSRDTST1.
Leave the remaining boxes on the first screen blank as they are not required for Report
Definition user hooks.
Leave all the boxes on the second screen blank, except for the final box, Data Type. This
needs to be completed with the type of data that is passed back to the formatter.
The next stage is to complete the following entries using RD=Report Definition:
Format Code
Select the Format Code and enter F in the selection box to go to the Format Details screen.
Create or select the required box by using F2 to go into the Data Items screen.
Change the Item Type to U-User Hook value.
UHD
Enter the user hook definition number. This must match the number entered in the user hook
definition screen for the user hook number box. The description should confirm you have
picked the correct user hook definition.
This means that every time the box is processed by RD=Report Definition, the user hook
program is called and processed before it is passed back to the Report Formatter.
User hook calling points
This subsection highlights the programs that make use of user hook definitions. It also details
what calling points need to be set in order to activate the hook.
Journal Entry - SAJE
The following calling points require the setting of Y-Yes if the user hook program is to be
called at these points:
 Start of Session
 End of Session

User Hooks
 Calling Point 1 – End of Line

 Calling Point 2 – End of Journal (prior to posting)
 Calling Point 3 – On holding a journal (passes held journal reference)
 Calling Point 4 – As each line is posted (supplies assigned journal number, no user hook
feedback allowed).
No action codes should be entered as the calling points imply the action being used.
User hook calls and the linkage passed to and from them are described in the User Hooks
section in this manual. Some additional boxes on hook linkage, see SAJEHKLK, is also
passed in linkage from the user hook definition record.
Journal Import - SATF
 Start of Session
 End of Session
 Calling Point 1 – End of Line
 Calling Point 2 – End of Journal (prior to posting)
No action codes should be entered as the calling points imply the action being used.
User hook calls and the linkage passed to and from them are described in the User Hooks
section of this manual. Some additional boxes on hook linkage, also using SAJEHKLK, are
passed in linkage from the user hook definition record.
Sales Order Entry – Header Level - SBTE
Uses the following calling point which requires the setting of Y-Yes if the hook is to be called
at this point. It only carries out the call if a matching action code is set. Currently actions
Amend, Create, Delete, Examine and Release are available.
 Calling Point 1 – on completion of screen details, prior to reference number being assigned.
See SBTDHKLK for boxes passed on hook linkage, is also passed in linkage the user hook
definition record.
SBTE also loads up SBTD hooks if the Retain in Memory box on their user hook definitions is
set to Y-Yes.
Sales Order Entry – Detail Level - SBTD
Uses calling point 1 to indicate if the user hook program should be called if insufficient stock
is encountered, otherwise continues to use calling flags as defined in the User Hooks section
in this manual.
The following new flags have been added.
 Flag 35 – indicates that the hook should be called prior to deleting lines.
 Flag 36 – indicates the hook to be called prior to order being released.
See SBTDHKLK for boxes passed on hook linkage. It also passes the user hook definition
record in linkage.
SBTD does not cancel out or load up hooks if the Retain in Memory box on their user hook
definitions is set to Y-Yes, as SBTE has already loaded them.
Sales Order Import - SOSI
The following calling point requires the setting of Y-Yes, if the user hook program is to be
called at this point:

User Hooks
 Calling Point 1 – for Header records only. At two stages within the import process, the first on
validation, which allows set boxes to be changed, and the second prior to posting.
Otherwise Sales Order Import continues to use calling flags as defined above.
See SOSIHKLK for boxes passed in hook linkage. It also passes the user hook definition
record in linkage.
SOP Print Invoices - SBPI
 Calling Point 1 – called on identifying an order to be invoiced (passes the total invoice value)
 Calling Point 2 – called on completion of screen selection criteria
 Calling Point 3 – called on completion of Print Invoice run
See SBPIHKLK for boxes passed on hook linkage. It also passes the user hook definition
record in linkage.
SOP Print Dispatch Notes - SBPS
The following calling point requires the setting of Y-Yes if the user hook program is to be
 Calling Point 1 – called on locating an order to be dispatched. If the hook returns an error, the
order is ignored and no dispatch processing is carried out.
See SBPSHKLK for boxes passed on hook linkage. It also passes the user hook definition
record in linkage.
Purchase Order/Invoice Entry – Header Level - SPPE
Uses the following calling point which requires the setting of Y-Yes if the hook is to be called
at this point. It only carries out the call if the matching action code is set. Currently actions
Amend, Create, Delete, Examine and Release are available.
 Calling Point 1 – on completion of screen details, prior to reference number being assigned.
See SPPDHKLK for boxes passed on hook linkage, it also passes in linkage the user hook
definition record.
SPPE also loads up SPPD hooks if the Retain in Memory box on the user hook definition is
set to Y-Yes.
Purchase Order/Invoice Entry – Detail Level - SPPD
Does not use calling points, continues to use calling flags as defined in the User Hooks
section in this manual.
The following new flags have been added:
 Flag 35 – indicates that the hook should be called prior to deleting lines.
 Flag 36 – indicates the hook to be called prior to the order being released.
See SPPDHKLK for boxes passed on hook linkage. It also passes the user hook definition
record in linkage.
SPPD does not cancel out or load up hooks if the Retain in Memory box on their user hook
definition is set to Y-Yes. SPPE has already loaded them.
Purchase Import - SPPI
The following calling point requires the setting of Y-Yes, if the user hook program is to be

User Hooks
 Calling Point 1 – for Header records only. At two stages within the import process, the first on
validation, which allows set boxes to be changed, and the second prior to posting.
Otherwise Purchase Import continues to use calling flags as defined in the User Hooks
section in this manual. See SPPIHKLK for boxes passed on hook linkage. It also passes the
user hook definition record in linkage.
Report Formatter – SSRF
A box on a report can be the output from a user hook. Such Items are created as type U-User
Hook, and the user hook definition to be used is defined on the RD=Report Definition by use
of the sequence number.
See SSUHLINK for boxes passed in hook linkage. All other user hooks function in the way
defined in the User Hooks section in this manual, and do not make use of user hook
definition.

Chapter 7 Hidden Functions
7
There are hidden functions in addition to those appearing on the SunSystems v4 menus.
These are directed towards systems managers rather than operators, or are only intended to
be used under direction. Some of these functions are only available to the SuperUser. This is
why they do not appear on the menus or in the Help. Detailed information about these
functions is provided in this section.
The section Screens and Menus describes how a screen validates routing instructions
against a list of permissible options. For example, JL=Journal Listing is a routing instruction to
invoke program AJL1. Thus, these concealed features can only be selected from certain
screens. They each have an associated two character code. They are accessed by entering
this two character code into the function selection box whilst in query mode.
Bank File Formats

All supported bank file formats are supplied in the file called BANKREC.NDF, which is held in
the SunSystems v4 program directory. This file contains all the formats of the bank statement
layouts, and the transfer profiles and mapping information related to using them, as well as
the data item definitions.
To import this information, select TP=Transfer Profiles and then use Transfer from the Action
menu. Once complete, the profile becomes available in Reconciliation Manager.
Import or Export
I/E
Enter I-Import to transfer data from a file to the installation file.
Transfer Filename
Enter the filename BANKREC.NDF. No directory path is required.
Transfer Profile From/To

maximum 5 characters/blank
Leave blank if you want to import all bank file formats, otherwise enter the required profile
code from the following list:
 AI001 BAI Format
 AN001 ANZ
 APACS APACS Format
 AZ001 ANZ Bank (New Zealand)
 BA001 Bank Artha Graha Indonesia
 BB001 Barclays Bank (UK)
 BI001 Bank of Ireland (APACS)
 BU001 Bank Utama (M) Berhad
 BV001 Bank Administration V1
 BV002 Bank Administration V2
 BZ001 National Bank of New Zealand
 CA001 Commonwealth Bank Australia
 CB001 Colonial State Bank

Hidden Functions
 CM001 Chase Manhatten Bank

 CR001 Bank of Costa Rica
 CT001 NationsBank
 HK001 Hong Kong & Shanghai Bank
 HO001 Bank of Scotland (HBoS)
 IR001 Allied Irish Bank
 LL001 Lloyds Bank (APACS)
 MB001 Macquarie Bank Limited
 MD001 Midland Bank UK (APACS)
 NA001 National Australia Bank
 NB001 Northern Bank
 NW001 Natwest Bank (UK) Bankline
 NZ001 Bank of New Zealand
 RA001 Bank RA001
 RB001 Royal Bank, Canada
 SC001 Standard Chartered Bank
 WC001 Westpac Banking Corporation
 WZ001 Westpac of New Zealand.
BC=Business Conversion
Business Conversion, or Business Rules Conversion, and certain predefined TP=Transfer
Profiles provide an upgrade path from certain SunSystems v4 functions and companion
products. The upgrade is from SunSystems v4 4.2 formats. Using BC=Business Conversion,
you can convert the following:
 Verification rule sets from companion products
 Bank reconciliation rules and data from companion products
 XC=Export Consolidation and XD=Export Definitions from the Ledger Accounting module of a
previous SunSystems v4 product.
Business Conversion runs on the data files (.dat and .idx), however, bank reconciliation
data, which is held in a budget ledger, is converted from the backup files (.bak).
Make sure you have taken a security backup of your data before you run this conversion
process, including your installation file.
When you have identified the conversions to take place, use Conversion on the Action menu
to begin the process.
Note: Verification rule set calculations are not converted by this function. The rule
sets created in Process Manager need to be manually amended by adding the
required calculations after the conversion has been run.
Companion Verification
Y/blank
Enter Y-Yes if you wish to convert your companion product verification rules to business rules
format, otherwise leave blank. The default is blank.
UVRULES Directory
40 characters
Enter the directory where your data is stored.
Note: The files located in this directory should be UVRULES.DAT and UVRULES.IDX.

Hidden Functions
Companion Bank Reconciliation

Y/blank
Enter Y-Yes if you wish to convert your companion product bank reconciliation data to
business rules format, otherwise leave blank. The default is blank.
Database Code
3 characters
Enter the database code, which contains the reconciliation data you wish to convert. Use
Query to select a code.
Ledger
B-K
Enter the budget ledger code B-K where you wish to store your converted reconciliation data.
Suspense Account
10 characters
Enter the suspense account in the budget ledger where balancing entries are to be posted.
Use Query to select a code.
Backup Directory
40 characters
Enter the path to where your companion product bank reconciliation data is backed up.
Note: The file located in this directory should be PABS-XXX.BAK (where XXX=database
code).
Ledger Export Set-Up
Y/blank
Enter Y-Yes to convert your XC=Export Consolidation and XD=Export Definitions to business
rules format, otherwise leave blank. The default is blank.
Database Code
3 characters
Enter the code for the database whose consolidation data you wish to convert. Use Query to
select a code.
Conversion
Use Conversion from the Action menu to start the conversion process.
BI=Backup Indexed
This function is only available from within the function FB=File Backup/Restore and is only
available to the SuperUser.
This produces a backup file in indexed, rather than random, sequence. If the backup file is to
be edited by a word processor, an indexed backup will make it easier to find the required
records. However, the indexed backup does take longer than a regular backup.
BU=Business Menus
This function is only available to the SuperUser.

Hidden Functions
Because the profiles you create in TP=Transfer Profiles are user definable, they do not exist
on any standard menu within SunSystems. BU=Business Menus enables you to attach your
user defined profiles to the existing menus. For each menu function you define in
BU=Business Menus, you must identify the language code and the module to which it relates.
You must then assign a mnemonic unique to the module in which it is used.
A single menu function can relate to one, or to a series of, profiles. You can combine up to 20
profiles in a single menu function. Profiles must be entered in the BU=Business Menus record
in the logical order in which they must be run to complete the user defined process. Once you
have set up or amended a business menu, you must update the SunSystems template files
(SSnnTEMPL.idx and SSnnTEMPL.dat) and also the corresponding Navigator menu
screen entries.
The program used to update the template files, SSTU.EXE, is an external program located in
the SunSystems installation folder. Before you run SSTU.EXE, the business menu record
must be exported to a file using the BU=Business Menus action Transfer. Ensure all users
are logged out of SunSystems before running SSTU.EXE.
The program used to update the Navigator screen menu entries, ThirdPartyInstaller.exe, is
an external program also located in the SunSystems installation folder. Before you run
ThirdPartyInstaller.exe, you must recreate key elements of your new menu entries in an
appropriate .XML file.
Note: If you run SSTU.EXE and ThirdPartyInstaller.exe on the server, you must
ensure that the updated template files are copied to any thin client PCs, and
ThirdPartyInstaller.exe is run again on each client.
After a system upgrade, the existing template files are overwritten, therefore the entries
created using BU=Business Menus need to be re-added. Once you have restored the
SSINSTAL file, re-export the business menu record and run SSTU.EXE and
ThirdPartyInstaller.exe as previously described.
Language Code
00-99
Enter the language code for the function. Use Query to select a language code.
Module
SM/SA/SO/SP/SF/SC/SG
Enter the code for the module to which this function relates, according to the following list:
 SM-Inventory Control
 SA-Ledger Accounting
 SO-Sales Order Processing
 SP-Purchase Order Processing
 SF-Fixed Assets
 SC-Corporate Allocations
 SG-Materials Management.
Function
Enter the mnemonic that you want to associate with this function. This must be a unique
mnemonic within the module you have specified. Use Query to review existing user defined
mnemonics.

Hidden Functions
Description
Enter a description for this function. This is used and displayed as the function name.
Menu Group
E/I/R/P/M
Enter the code that determines the menu group to which the function is associated.
This must be one of the following:
 E-Entry
 I-Inquiry
 R-Reports
 P-Procedures
 M-Maintenance.
Profile Codes 1-20

Enter the codes of the TP=Transfer Profiles you wish to include in this function in the order in
which they are to be processed. Use Query to select a profile code.
Transfer
Use Transfer from the Action menu to produce a file for use by the program SSTU.EXE that
updates the SunSystems v4 template.
Transfer Screen
Import or Export
I/E
Enter E-Export to export the business menu to a file.
Transfer File Name
SSBU-TU.NDF
Accept the default of SSBU-TU.NDF displayed.
Language Code
99
Enter the range of language codes for the business menus you wish to export or leave blank
to export menus for all language codes. The default is blank.
Module
SM/SA/SO/SP/SF/SC/SG/blank
Enter the range of module codes for the business menus you wish to export or leave blank to
export menus for all modules. The default is blank.
 SM-Inventory Control
 SA-Ledger Accounting
 SO-Sales Order Processing
 SP-Purchase Order Processing

Hidden Functions
 SF-Fixed Assets
 SC-Corporate Allocations
 SG-Materials Management.
Process Transfer
Use Process Transfer from the Action menu to create the file used to update the SunSystems
v4 template.
CS=Create Suppress
CS=Create Suppress is only available from within the JE=Journal Entry screen in
SunAccount, and the ME=Movement Entry screen in SunBusiness. It allows a new journal or
movement transaction line to be created without using any of the presets that are defined in
JP=Journal Presets or MP=Movement Presets.
RA=Restore Append
This function is only available from within the function FB=File Backup/Restore and is only
available to the SuperUser. Enter RA and click OK. Once you have entered the required
information, the dialog, ‘Append will add to existing data?’ is displayed with the options Yes
and No.
This allows a file restore to take place without wiping out the original indexed file. Records
being restored are merged with the existing indexed data file. If a restored record already
exists on the indexed file the operator is prompted to ignore the duplicate, or abandon the
restore append.
RL=Record Locking Testing Tool

This function allows you to lock selected records for a specified database. It enables you to
test what the system will do when it encounters the locked record.
Database Code
3 characters
Enter a database code as defined in DB=Database Definitions.
File Code
IN/DD/RE/RF/LF/AF/LB/OF/PY/DB/PF/MF/SF/KF/LFx (where x is a valid budget code)
Enter the required file code. For example, LF-Ledger File or MF-Movement File.
Record Type
Enter a record type that is valid for the file code selected. For example, ACC from the
Reference File or O from the Sales Order File.
Record Key
Enter a record key exactly as defined in the record description. Include numeric data in
numeric fields and enter spaces where required.
Lock On
Enter Y-Yes to lock a record. Enter N-No or leave blank to turn a lock off.

Hidden Functions
ZB=Benchmarking Log
This function is only available to the SuperUser. Enter ZB in the selection box and the
message ‘BENCH-MARK ON’ is displayed on the status bar. The system will write to a file
called BENCH.LOG, the start time, end time and program being executed.
To turn this function off, type ZB in the selection box again. The message ‘BENCH-MARK
OFF’ is displayed on the status bar.
Here is an example of what this file might look like:
ZB SSSF H SUN 12 41 20.59 12 41 20.65 0.06
ZB SSSF K SUN 12 41 20.65 12 41 20.70 0.05
X SSSF B SUN 12 41 29.22 12 41 29.27 0.05
ZB SSSF H DEM 12 41 48.50 12 41 48.50
ZB SSSF K DEM 12 41 48.55 12 41 48.61 0.06
LA SSSF 1 DEM 12 41 51.30 12 41 54.21 2.91
LA SSSF 6 DEM 12 41 54.37 12 41 54.59 0.22
LA SSSF E DEM 12 41 54.65 12 41 54.65
LA SSSF K DEM 12 41 54.81 12 41 54.98 0.17
JE SAJE 0 DEM 12 42 02.45 12 43 03.69 61.24
X SSSF E DEM 12 43 03.74 12 43 03.80 0.06
X SSSF K DEM 12 43 03.96 12 43 04.02 0.06
ZB SSSF K DEM 12 43 09.62 12 43 09.73 0.11
ZB SSSF H DEM 12 43 09.73 12 43 09.73
The following uses a line from the file to explain what each indicator means.
JE SAJE 0 DEM 12 42 02.45 12 43 03.69 61.24
 JE - The last two letter selection mnemonic entered on the screen. In this case it is
JE=Journal Entry
 SAJE - The program executed. In this case Journal Entry
 0 - Process Mode. This has no meaning here, but in the case of program SAAR, which
executes both AQ=Account Inquiry and AA=Account Allocation, it would be 0 and 1
respectively.
 DEM - The Operator Id using the process
 12 42 02.45 - The start time of the process
 12 43 03.69 - The termination time of the process
 61.24 - The elapse time of the process.
ZC=Clear Users
This function is used to clear (log out) a single operator Id or all SunSystems v4 users who
are currently logged in to the system, or to revalidate an Operator Id after a password
violation has occurred.
Enter ZC in the selection box and the Clear Operator ID dialog is displayed.
Only the SuperUser may clear all users who are currently logged in to the system or
revalidate an Id. Normal operators may clear individual users one at a time, provided the
operator has permission to do so.
When the SuperUser chooses to clear all operators by leaving the Operator Id box blank, the
Clear In-Use Allocation Markers dialog is displayed. This asks the user to confirm whether or
not to clear all allocation markers currently in use by operators logged in. Enter Y to clear
these allocation markers, or leave the box blank to clear operators only.

Hidden Functions
Note: If you choose to clear these allocation markers, the process may take a
considerable amount of time to complete.
ZF=Form Feed
This option is available from all screens.
When ZF=Form Feed is selected, the printer performs a form feed. In most cases
SunSystems v4 print routines perform a form feed before printing. The exception is when
printing formatted documents which could be printed on special stationery that has been
carefully aligned.
This feature may be used after formatted documents have been printed.
Also, if SunSystems v4 is being used in conjunction with software that does not perform a
form feed before printing, ZF may be used.
The feature is particularly useful when printers are sited remotely.
ZL=File Log
This feature is available from the SunSystems v4 menu/screens.
It is used to switch on and off the file handler activity log, SSFH-ooo.LOG (where ooo is the
Operator Id of the User running this session of SunSystems v4) which records all the main file
activities. It can be useful when trouble shooting but should not be used under normal running
since the logging process will degrade performance and the resulting log file can be very
large.
The following is an example of the records that might appear in this Log:
FILE LOG
RF RD 23 11 17 36.28 11 17 36.28 ACC1101
RF RD 00 11 17 39.47 11 17 39.47 ACC110
RF RD 00 11 18 07.48 11 18 07.54 0.06 ANVT1
RF RD 00 11 18 09.79 11 18 09.79 ANVT24
RF RD 23 11 18 13.41 11 18 13.41 ANVT5e
RF RD 00 11 18 15.50 11 18 15.50 ANVT5E
RF SG 00 11 18 15.56 11 18 15.56 BCD
RF RN 00 11 18 15.61 11 18 15.61 BCD310
To use the first line of the example here:
RF RD 23 11 17 36.28 11 17 36.28 ACC1101
The first two characters define which file is being processed. In this case RF indicated the
reference file (or tables in the case of a SQL Server system). Other valid values that can
appear in that column are:
File File characters
Installation File IN
Data Dictionary DD
Reference File RF

Hidden Functions
File File characters
Reference Audit File RA
Format File FO
Report Format File RE
Asset File AF
Ledger File LF
Allocations File LC
Hold File QF
Payment File PY
Debit File DB
Transfer File TR
Ledger Archive File LH
Balance File LB
Sales Order File OF
Purchase Order File PF
Movement File MF
Serial Tracking File SF
Stock Take File KF
Sales Order History File HF
Purchase Order History File PU
The second two characters are the file handler process performed on the file. In the example
above RD represents a normal file read. Here is a list of possible file handles and their
associated two characters:

Hidden Functions
File handle Handle characters
Call SQL CS
Exits FX
Clear FC
Name Request NM
Error Request ER
Close CL
Close Cursor CC
Commit CO
Delete DL
Open Extend OE
Open Input OI
Open Output OO
OPEN I O O
Open Lock OL
Rollback RB
Read RD
Read Lock RL
Read Nend RN
File Handle Handle Characters
Read Balance BR
Rewrite RW
Start Equal SE

Hidden Functions
File handle Handle characters
Start Greater SG
Start Not Less SN
Start SQL QS
Write WR
Write Page WB
Write Balance BW
Unlock All UA
Unlock One UO
Creation CF
The third set of characters are numbers, and they represent the return code from the file
handler. If the file handler was successful, then the return code will be 00.
In the case of the example above the 23 indicates that the file was not found. Here is a list of
possible first digits of the return codes and what they might mean:
Return code Meaning
0 Operation successful
1 End of file
2 Record not found or duplicate key
9 Disastrous operation. The system should

stop and display an error message
To explain the following time indicators, please refer to the following example:
RF RD 00 11 18 07.48 11 18 07.54 0.06 ANVT1
The next set of numbers is 11 18 07.48, the start time of the particular file process.
This process started at 11:18 am 07.48 represent 7 seconds and 48 hundredth’s seconds in
that minute.
After that is the time that the file handle terminated 11 18 07.54
The last of the time indicators is the elapse time of the file handler. It is merely the difference
between the start and termination time of the file handle process.
The last indicator on the log is:

Hidden Functions
 The key of the record being processed

 The smart or direct statement that was built into the file handle in the application program
ZP=Installation Parameters
This function is only available to the SuperUser. It allows you to set the following installation
parameters:
Pick
Y/blank
Enter Y-Yes, to specify that the picking program will pick a sales order detail irrespective of
the stock balance (then it will allow the stock to go negative).
Keybd
Y/blank
Enter Y-Yes to specify that the keyboard can be scanned during batch processes, such as
printing reports and using FreeFormat to enable pausing or abandoning.
This is not available in all environments.
Close
Y/blank
Enter Y-Yes to force the main data files to be closed after each menu screen selection. This
is only useful if data is not being written to disk correctly.
Date
Y/A/blank
If Y-Yes is entered, the operating system date is read when logging in to SunSystems v4 and
becomes Today’s Date. Enter A-Automatic to automatically use the operating system date for
all operators without allowing the opportunity to change it.
IR (Item Record)
Y/blank
If Y-Yes is entered, the alternative Item Record screen is used, in conjunction with Inventory
Revaluation. This Item Record screen has an extra input field for an Account, and does not
allow entry into the Standard Cost field.
Progs
0-9
This parameter controls the number of SunSystems v4 program modules which may remain
loaded in addition to the current module. The default for this parameter is 0 and this indicates
that no additional modules should remain loaded. If 3 is selected, then three additional
program modules remain loaded simultaneously.
The facility gives slight performance improvements on some machines when some functions
are repeatedly used.
Note: In some operating environments, where there is insufficient memory for the
requested number of modules to be loaded into memory, SunSystems v4 may page
in and out some of its modules, causing a dramatic drop in performance.

Hidden Functions
Archv (Archive)
B/Y/blank
Enter Y-Yes for records deleted by the SunBusiness PC=Period Cleardown functions to be
written to an archive file. The SunBusiness archive file is in the format as the backup of the
same file. See the section Data File Naming for information regarding file naming.
The valid settings for the parameter are:
 Y or B - Archive SunBusiness transactions
 Blank - No archiving of SunBusiness transactions.
To write deleted SunAccount transactions to an archive file, set Ledger Archiving to Y-Yes in
the LD=Ledger Definition for that database. See the topic Ledger Definition in the
SunAccount Administrator Help.
Locks
Y/blank
Enter Y-Yes to force automatic retry on records that are locked, otherwise leave blank for
standard retry message.
Note: This applies to Oracle only.
Sort
Y/blank
This field has no effect unless SunAccount FA=Financial Analysis reports transactions. Enter
Y-Yes and a COBOL sort is used rather than writing to an indexed file. In some environments
this causes a performance improvement.
VAT
V/blank
Enter V-Vat to prevent VAT transactions in SunAccount having settlement discount applied to
them. VAT lines are identified by analysis code T5 being set to V.
ZR=Remove Journal In Use flag

This is accessed from the View Held Journals option in JE=Journal Entry. ZR allows you to
remove the message ‘Journal in use’, and access that journal.
ZS=Serialisation
This feature is used to enter the serialisation details for your system as provided by your
supplier. It is only available to the SuperUser.
The Update Code provided by your supplier varies according to the screen settings.
The serialisation is only accepted with a valid update code.
This method can be used to convert a system from the demonstration version to a full working
version, or to add modules, increase the number of permitted users, or to clear time-fusing.
ZU=Unbalanced Journal
ZU enables you to Post journals in SunAccount which do not balance. This may be required
under exceptional circumstances to correct an imbalance in the ledger following a file
corruption which has occurred as a result of hardware failure.

Hidden Functions
In SunAccount, the ZU feature may be used from within JE=Journal Entry, and AA=Account
Allocation. When used in JL=Journal Listing, a report of unbalanced journals is produced
using the unbalanced journal listing report format.
This feature should only be used when absolutely necessary.
Note: After a journal has been subject to a PC=Period Cleardown, parts of the
journal, but not necessarily all, will have been deleted. Consequently, these journals
no longer balance individually. The resultant balancing amounts are generated in
consolidated summary transactions posted to the affected accounts by the period
cleardown process, so that the accounts retain their balances, and the ledger as a
whole remains balanced.
Tip: TB=Trial Balance can be used to rapidly ascertain whether the ledger balances,
and to establish which account(s) are associated with an imbalance if there is one.

Chapter 8 Data Dictionary and Report
Definition 8
Introduction
This section describes how to modify and create record types in the data dictionary.
This is the master file, common to both SunAccount and SunBusiness, which stores record
information to be reported by RD=Report Definition.
You might want to modify or create data dictionary records in the following circumstances:
 When undertaking a translation of SunSystems v4 to another language
 When adding fields to an existing reference record
 When adding new record types to the reference file.
 When writing a report driver for RD=Report Definition.
If you add new fields or new record types, they will not be accessed by SunSystems v4.
However, SunSystems v4 reference maintenance functions can update, report, audit, and
transfer such records. You can access them directly from your COBOL programs or through
reference transfer, and then from other software packages.
Thus, SunSystems v4 can be used to update the new data for you, and you can then access
it in your own software.
Although the data dictionary is a separate file from the reference file, it is processed by the
same program that processes the reference file (SSRU). The only difference is that the
reference maintenance layout file record information record is slightly different. In order to get
SSRU to process the data dictionary, SSDDICTY.DAT, and SSDDICTY.IDX, the file type on
the record information record for each data dictionary file Id must be ‘DD’, for the data
dictionary.
For more information on the information record and the file Id, refer to the Reference
Maintenance section.
Although the templates to amend each record type exist in the template file, there are no
routing selections on the SSMM01 menu to select these templates. This prevents users from
accidentally modifying the data dictionary. To add these selections to the SSMM01 menu, use
SZTE. For more information on how to add menu selections see the Screens and Menus
section.
Listed with data dictionary maintenance function are the template Id’s and record Id’s needed
to add the selections to the SSMM01 menu.
Maintain Report Types

Template Id SSRU32
Record Id DDS
For each language code and report type combination in RD=Report Definition there is a
report type record.

Data Dictionary and Report Definition
Language Code
2 digits
Enter a two digit language code. This must be defined on the installation file.
Report types in RD=Report Definition are language specific.
Report Type
Enter a three letter code to identify this report type. You must not use the codes ‘XX’, ‘Y’ and
‘YY’ in this box.
System
SA/SB/blank
Leave this box blank for all systems. Enter SA for SunAccount only or SB for SunBusiness
only.
Description
Enter a description for the report type. This appears in the Report Type box on the
Control Parameters screen in RD=Report Definition when the Report Type is selected.
File Code
2 characters
Enter the file Id of the location in which the report record is stored. For example, enter RF for
the Reference File. These are defined in the data dictionary maintenance function, Maintain
Data-Record Descriptions, described later in this section.
Record Type
This is the Record Type as it appears on the file to be read. If it is a reference maintenance
record it is one of the three letter record Id’s described in the section Reference Maintenance.
Otherwise it is the record type on the record of the file. For valid record types for different
SunSystems v4 files, see the subsection Maintain Data-Record Descriptions.
Occurrence
1 character
A record type may appear more than once in a report. If, for example, two different address
records a delivery address and a billing address, appear on a report, these have the same file
code and record type combination. Enter a different occurrence number to differentiate
between the two.
Record Code
3 characters
Enter the code that is displayed for this record in RD=Report Definition under the heading
Type in the Record Types window. If you leave this box blank the data record type defined on
the Data-Record Descriptions record is displayed in RD=Report Definition.

Record Description
Enter the description that appears in RD=Report Definition in the Record Types window.
Leave blank to display the default description defined on the Data-Record Descriptions
record.
Up to 20 records can be listed on the Report Type Record. After you have entered 15, a
window appears to accept the remaining five.
This screen shows how the Report Type Record information is displayed in RD=Report
Definition. When selecting record information to appear on a report, the Record Types
window displays when F5 is pressed in the Data Items window. The record types are also
displayed after using F5 in the Only If box in the Data Items window.
Two record types appear on every report definition. They are common fields and selection
fields. These record types are discussed later in this section. These are not defined in this
function.
The remaining records that appear in this window appear in the order that they are entered in
the Maintain Report Types screen.
The record description comes from the default file code defined on the Data-Records
Description record discussed later in this section. If a description for that record is defined on
the Report Types Record, that description is displayed instead.
Note: Analysis Category and Analysis Codes records are automatically expanded.
RD=Report Definition does this when the letter of the analysis category is appended
to either of these record types.
Maintain Data-Record Descriptions

Template Id SSRU30
Record Id DDR
For each combination of language code, file code, and data record type there is a Data-
Record Description record.
Language Code
2 digits
Enter a two digit language code. This must be defined on the installation file. Report types in
RD=Report Definition are language specific.
File Code
2 characters
Enter the file Id of the location in which the record is stored. For example, enter RF for the
Reference File.
There are additionally two special file codes that may be used:
 XX - For common fields that may appear on all reports in Report Definition. These are Time,
Date, Page Number, etc.
 YY - For selection fields. These may be fields typed into the report driver selection screen by
the user, or data that is generated by the report driver at runtime.

Data Record Type

This is the record type as it appears on the file to be read. If it is a reference maintenance
Otherwise, it is the record type on the record of the file.
For valid record types in the different SunSystems v4 files see the subsection Maintain Report
Types.
Description
This description appears in the record description window on the Format Details screen in
RD=Report Definition. To display the Record Descriptions window press F5 when prompted
in the Data Item window or press F5 on the Only If box in Data Items.
Maintain Data-Item Definitions

Template Id SSRU28
Record Id DDD
For each file code, data record type, and item number combination there is a Data Record
Description record. These records describe the individual field that can be found on each
Data Record.
File Code
2 digits
Enter the file Id for the location in which the record is held. For example, enter RF for the
Reference File.
Data Record Type
Otherwise it is the record type on the record of the file.
For valid record types in the different SunSystems v4 files, see the appendices.
Item Number
maximum 999
This is a unique item number for each individual entry on each data item record. It is used by
RD=Report Definition to display each data item in a particular order.
Item Name
This is for the SQL Data Names. This is not currently used.
Entity ID
maximum 999999
This is used by RD=Report Definition to read the entity definition for this data item. Maintain
Entity Definition is described later in this section.

Offset
maximum 9999
This records the start position of the field on the record.
COBOL Name
This is the COBOL data name from the file layout copy.
Omit From Query
1/blank
Enter 1 in this box for the data item not to be displayed for selection in RD=Report Definition.
Note: The Data Items for the Chart of Accounts Record Type display in the same
order as they appear in the query on Data Item Records.
The Item Description, Type, and Length displayed come from the following Data Dictionary
Maintenance Functions.
Maintain Data-Item Descriptions

Template Id SSRU29
Record Id DDT
For each language code, file code, data record type, and item number combination there is a
Data-Item Description Record. These are used to display the language description of each
data item in RD=Report Definition.
Language Code
2 characters
File Code
2 characters
Enter the two letter file Id for the location in which the record is stored. For example, enter RF
for the Reference File.
Data Record Type
record then it is one of the three letter record Id’s described in the section Reference
Maintenance. Otherwise it is the record type on the record of the file. For valid record types in
the different SunSystems v4 files, refer to the appendices.
Item Number
This is a unique number for each individual field on each data record. It is used by
RD=Report Definition to read the description on each data item description record.

Description
This is displayed in RD=Report Definition, in the Data Items selection window.
Long Heading
Not currently used.
Short Heading
Not currently used.
Lookup Description
This is displayed once a data record is selected from the available list and more than one key
definition exists for that file code/data record type combination. Key definitions are explained
in the subsection Maintain Key Definitions.
Maintain Entity Definitions

Template Id SSRU25
Record Id DDE
For each Database Code/Entity Id combination there is an Entity Definition. These records
define attributes of particular field types.
Database Code
This is used for Analysis Categories and Codes. Since the length of entities are defined on
this record, and analysis code lengths are unique for each database, these records must be
entered by database code. If the entity has no relation to analysis category lengths, this box
will be blank.
Entity Id
maximum 999999
This is a six digit code assigned to the unique physical properties of a data item. Numbers 1
to 99999 are reserved for the use of entities that have been defined by Infor. Numbers above
100000 are reserved for external developers.
There are ranges of the entity Ids that group similar entity types together. These ranges are:
 10000 - Codes
 20000 - Dates and Periods
 30000 - Amounts and Quantities
 40000 - Numbers
 50000 - Flags
 60000 - Text
 70000 - RunTime
 80000 - Report Selections
 90000 – Words.
The Entity Description is displayed beside the entered Id.

Length on File
maximum 999
Enter the length of the item on the file. Packed Data Items will have the number of packed
bytes.
Input/Output Length
maximum 999
The number of characters that this Entity should take up on a screen or report.
Data Type
01/02/03/04/10-19
Enter one of the following valid attribute indicator:
 01 - Alphanumeric
 02 - Period
 03 - Date
 04 - Password
 10-19 - Numeric, where the second digit is the number of decimal places.
Numeric Type
0/1/2
Enter one of the following COBOL numeric storage types:
 0 - Display
 1 - Comp (Binary)
 2 - Comp-3 (Packed).
Numeric Sign
0/1/2
You can enter one of the following parameters for a numeric sign:
 0 - Unsigned
 1 - Signed
 2 - Leading Sign Separate.
Justification
0/1/2
Enter one the following for justification:
 0 - No Justification
 1 - Left Justification
 2 - Right Justification.
Case Conversion
0/1
Valid parameters are:
 0 - No Conversion
 1 - Upper Case Conversion.

Maintain Entity Descriptions

Template Id SSRU26
Record Id DDL
For each Language Code/Entity Id combination there will be an Entity Description Record.
These records define language description of each entity.
Language Code
2 characters
Entity Id
maximum 999999
Is a six digit code that is assigned to the unique physical properties of a Data Item. See the
subsection Maintain Entity Definitions for valid entity ranges.
Description
This displays the English description on the Maintain Entity Definition screen which appears
once the entity code is entered. This is not used elsewhere in the system.
Long Heading
Not currently used.
Short Heading
Not currently used.
Maintain Sub-Headings and Sub-Footings

Template Id SSRU34
Record Id DDF
For each language code and report type combination there is a sub-headings and footing
record.
These records define logical breaks within the report format and may appear as headings or
footings. A logical break would be a change of account or period. Both sub-headings and sub-
footings are dependent on the report driver.
These records define heading and footing text that may appear at the beginning or end of a
report section in a report generated in RD=Report Definition.
Language Code
2 characters

Report Type
Enter a three letter code that uniquely identifies this record type. XX, Y and YY should not be
used in this box.
Sub-Headings and Sub-Footings
These are what can be selected and can appear on a report created in RD=Report Definition.
Maintain Key Definitions

Template Id SSRU27
Record Id DDK
For each report type, a maximum of 13 records may be directly read by the report driver
program. An additional seven records may be read by the report formatter (SSRF), and thus
be available to the report type if a key definition is defined for those additional records. Each
key definition defines the data elements to build the key for the addition records to be read.
File Code
2 characters
Enter the file Id to define which record is to be read by the report formatter. Enter either RF
for the reference file, or IN for installation file.
Data Record Type
Enter the record type of the file to be read. This is a three letter Id of the installation or
reference record described in the section Reference Maintenance.
Relationship Number
maximum 999
Enter a three digit number used to identify each file code and data record type combination. A
file code and data record type combination is defined by many keys, and this unique
relationship number is used to build the key.
Element Data
This defines the data item for this key definition.
File Code
Enter the two letter file Id of the file where the data item used to build the key is held. For
example, enter RF for the Reference File.
Record Type
This is the data record type on the file from which the key data item is selected. If it is a
reference maintenance record it is one of the three letter record Id’s described in the section
Reference Maintenance. Otherwise, it is the record type on the record of the file. For valid
record types for the different SunSystems v4 files, refer to the appendices.

Item Number
maximum 999
This is the data item number on the record. This is used in conjunction with the record type to
build the key for the report formatter to read this record.
For each file code, data record type, and item number combination, a Lookup Description
should be entered in the Maintain Data-Items Description function for each language code.
These descriptions will appear in the record selection window of RD=Report Definition.

Chapter 9 Associating Images with
SunSystems v4 Modules 9
Overview
You can display bitmap (.bmp) images on the SunSystems v4 screen. You can associate
different images with different modules of SunSystems v4. You may wish to do this for a
variety of reasons, for example to add your company logo to SunSystems v4 screens, or to
help SunSystems v4 operators differentiate between the modules.
Note: Images are not provided with SunSystems v4. You must create your own
images if you require them.
Inserting images
To insert images in SunSystems v4, you must edit the [WIN-BITMAPS] section of the
SUNPANEL.SF file in your main SunSystems v4 program directory. This is a plain text file that
can be edited using a text editor such as Windows Notepad.
In the left hand column, enter the code of the module. The modules are:
Module code Description
SSMM01 SS=SunSystems v4 main menu
SAMM01 LA=Ledger Accounting menu
SCMM01 CO=Corporate Allocations menu
SFMM01 AR=Fixed Asset Register menu
SPMM01 PO=Purchase Order Processing menu
SOMM01 SO=Sales Order Processing menu
SMMM01 IC=Inventory Control menu
In the right hand column, enter the name of the bitmap image you have created, for example
SSMM01.BMP.
Ensure that the format of the new entry matches the format of existing entries in the file. See
the subsection Example of SUNPANEL.SF.
Note: Any image referred to in SUNPANEL.SF must reside in the main SunSystems
v4 program directory. If the image does not exist, it is not displayed, rather than
producing an error message.

Associating Images with SunSystems v4 Modules
Example of SUNPANEL.SF
The following extract shows the beginning of a typical SUNPANEL.SF file, including a new
entry at the bottom to display the image SSMM01.BMP on the SS=SunSystems v4 main
menu screen:
[WIN-ICONS]
SUNWIN : SUNWIN.ICO
[WIN-BITMAPS]
OK : OK.BMP
CANCEL : CANCEL.BMP
INFO : INFO.BMP
WARN : WARN.BMP
CRIT : CRIT.BMP
HELP : HELP.BMP
LOOKUP : LOOKUP.BMP
DUP : DUP.BMP
FREEF : FREEF.BMP
SHAND : SHAND.BMP
DUPTOEND : DUPTOEND.BMP
CALC : CALC.BMP
QUERYE : QUERYE.BMP
QUERYD : QUERYD.BMP
CONTEXT : CONTEXT.BMP
TOGGLE : TOGGLE.BMP
SUNLOGO : SUNLOGO.BMP
TICK : TICK.BMP

Associating Images with SunSystems v4 Modules
CROSS : CROSS.BMP
SSMM01 : SSMM01.BMP

Chapter 10 Appendix A – SunSystems
v4 Data Tables and Files 10
The table and file layouts given in these appendices enable you to establish interfaces to
SunSystems v4. The appendices do not provide definitions for all SunSystems v4 data tables
and files, only those for which it is appropriate to establish interfaces.
The tables described in these appendices are:
Table/File name Description
SALFLDGddd SunAccount Ledger Table
SAxFLDGddd SunAccount Budget Table
SALHARCddd SunAccount Archive Table
SMKFHDRddd, SMKFDETddd SunBusiness Stock Take Tables
SMMFMOVddd SunBusiness Movement Table
SMMFMOVddd SunBusiness Serial Number Tracking

Table
SOHFOHFddd SunBusiness Sales History Table
SOMFHDRddd, SOMFDETddd SunBusiness Sales Order Tables
SPHFPHFddd SunBusiness Purchase History Table
SPMFDETddd, SPMFDTGddd, SunBusiness Purchase Order Tables

SPMFDTIddd, SPMFDTOddd,
SPMFGRNddd, SPMFINVddd,
SPMFORDddd
SBTRTRNddd SunBusiness Transfer Table
SPTRTRNddd SunBusiness Commitment Transfer Table
SAPYPAYddd SunAccount Payment Table
SAQFHLDddd SunAccount Journal Hold Table
SSRFACC SunSystems v4 Reference Table – Chart

of Accounts

Appendix A – SunSystems v4 Data Tables and Files
SSRFADB SunSystems v4 Reference Table –

Address Analysis
SSRFADD SunSystems v4 Reference Table – Names

and Addresses
SSRFANV SunSystems v4 Reference Table –

Analysis Codes
SSRFAST SunSystems v4 Reference Table –

Assembly Structure
SSRFBKA SunSystems v4 Reference Table – Bank

Details
SSRFCAT SunSystems v4 Reference Table –

Calculation Table
SSRFCND SunSystems v4 Reference Table – Daily

Conversion Rate
SSRFCNV SunSystems v4 Reference Table –

Conversion Table
SSRFCVD SunSystems v4 Reference Table –

Conversion Definition
SSRFFBR SunSystems v4 Reference Table – Asset

Budget Value
SSRFFVR SunSystems v4 Reference Table – Asset

Value
SSRFITM SunSystems v4 Reference Table – Item

Record
SSRFITS SunSystems v4 Reference Table – Item

Supplier
SSRFLIT SunSystems v4 Reference Table –

Location Item Record
SSRFMSC SunSystems v4 Reference Table -

Miscellaneous

SABK-ddd.nnn SunAccount Bank Payments File
SSRA-ddd.ttt SunSystems v4 Reference Audit File
SSRF-ddd.BAK SunSystems v4 Reference Backup File
SALF-ddd.BAK SunAccount Ledger Backup File
SMKF-ddd.BAK SunBusiness Stock Take Backup File
SMMF-ddd.BAK SunBusiness Movement Backup File
SOHF-ddd.BAK SunBusiness Sales History Backup File
SOMF-ddd.BAK SunBusiness Sales Order Backup File
SPHF-ddd.BAK SunBusiness Purchase History Backup File
SPMF-ddd.BAK SunBusiness Purchase Order Backup File
SAQF-ddd.BAK SunAccount Journal Hold Backup File
where:
 x - is the Budget Code.
 ddd - is Database Code.
 nnn - is the Bank Identity Code.
 ttt - is the Reference Record Type.
In SQL and Oracle environments, the master data is stored in tables in the SQL/Oracle
database. Some reference functions have their own table defined, though some data is stored
in ‘miscellaneous’ tables.
The backup tables are text tables, which may be edited using any standard editor. These
tables can be transported across different environments and are compatible with SunSystems
v4 on each environment.
Tip: Ensure the editor used to edit tables can handle any foreign characters that may
be present.
It is recommended that interfaces be based upon backup tables rather than data tables.
When enhancing the product, data table formats are likely to change, but backup table
formats should remain compatible.
For each table the following information is given:
 A table description, in words.
 A summary of record types.
 The COBOL table description (FD).
 A table showing the COBOL data names, the position of the fields in the record, SQL table
names, column names, field sizes and types, and a brief description of the fields.

Please consider the following points when using the table layouts:
 The FIELD TYPE column is used to describe the sort of field, taken from the COBOL
PICTURE clause. There are alphanumeric fields (type X), unsigned numeric fields (type N)
and signed numeric fields (type S). In some cases, for the numeric fields (types S and N), the
number of decimal places is specified. If it is not, then assume zero decimal places. Also
assume that the fields are stored in ASCII format (COBOL USAGE DISPLAY) unless specified
otherwise in the Comments column. If setting up new data, ensure that any numeric fields that
do not contain a value are initialised to zero.
 Assume all FILLER fields and fields marked as ‘Not used ...’ are set to spaces, unless
specified otherwise in the Comments column. Likewise, if creating new data, ensure such
fields are initialised.
 Dates and Periods are stored in internal format, that is, CCYYMMDD and CCYYPPP format
respectively.
In some cases fields are defined for the COBOL data tables but not in the SQL tables, and
vice versa. A ‘-’ hyphen in the tables indicates where something is not relevant. In the COBOL
definitions, some fields are redefined by others, but not in the SQL table. In this case, the
application itself handles the redefinition of the data, so there is no need to have the extra
columns in the SQL table.
The COBOL examples for the Table Definitions (FDs) have L and V flags in the margin.
These depict the different types of COBOL used: M=MicroFocus Cobol/2, V=Vax Cobol.

Appendix B - Master Data Files
Chapter 11 Appendix B - Master

Data Files 11
Reference File
Description
The Reference File holds the static data for both SunAccount and SunBusiness. There
are many different types of static data held. For example, customer addresses, items of
stock, analysis codes.
Summary of record types
For each type of static data there is a corresponding record type. The record types on the
file are defined on the Reference Layout Files - see the Reference Maintenance section of
this manual. Each is a three character code and is always found in the first three
characters of the record. There is a list, in the Reference Maintenance section of this
manual, detailing all the reference record types. Each record type is defined in a separate
COBOL copy file, and each one is simply a redefinition of the Reference
File master record, type ‘REF’, which does not actually exist on the data file. The COBOL
record layout is listed below.
Cobol File Description (FD)
M FDREF-FILE.
V* FDREF-FILE VALUE OF ID IS REF-FILE-NAME.
01 REF-RECORD.
03 REF-KEY.
05 REF-RECORD-ID PIC X(003).
05 REF-KEY-2 PIC X(028).
05 REF-KEY-CONT PIC X(001).
03 REF-LOOKUP-KEY.
05 REF-LOOKUP-ID PIC X(003).
05 REF-LOOKUP-CODE PIC X(010).
03 REF-DATA.
05 REF-DATA-1 PIC X(723).
The physical record length on disk (800 bytes) is less than the logical record length within
the programs (1024 bytes):
Logical Record bytes
Physical Record
Primary Key 64
Alternate Key 13
Date Last Updated 8
Data 715
-----

Total Physical 800

Filler 224
-----
Total Logical 1024
Reference file record descriptions
Note that each Reference record type does not have its own SQL table, though some do.
If the SQL definitions are not included for a particular Reference record layout below, then
there is no specific SQL table for that Reference record type. The Reference data will be
stored in the miscellaneous table called SSRFMSC. This table is defined as follows:
SQL field name SQL field type Description
SUN_DB char(3) Database Code
SUN_TB char(3) Table Code
KEY_FIELDS char(61) Key Fields
LOOKUP char(10) Lookup Code
UPDATED char(8) Date Last Updated
SUN_DATA char(939) Composite Data

Account Balance record, SSACBRC.CPY, (SQL miscellaneous table SSRFMSC)
COBOL FIELD NAME POS’N IN FIELD FIELD DEC. DESCRIPTION COMMENT

RECORD LENGTH TYPE PLACES
FILLER 001 003 X - Reference Record Type Value ‘ACB’, mandatory
R-ACB-ACCOUNT 004 015 X - Account Code Mandatory
R-ACB-ANAL-CAT1 019 002 X - Analysis Definition 1
R-ACB-ANAL-MASK1 021 001 X - Analysis Mask 1
R-ACB-ANAL-CODE1 022 015 X - Analysis Code 1
R-ACB-ANAL-CAT2 037 002 X - Analysis Definition 2
R-ACB-ANAL-MASK2 039 001 X - Analysis Mask 2
R-ACB-ANAL-CODE2 040 015 X - Analysis Code 2
FILLER - 010 X - -
R-ACB-LOOKUP-ID 065 003 X - Lookup Id
FILLER 068 018 X - -
R-ACB-ACT-BAL 086 019 S 3 Actual Balance
R-ACB-BUD-BAL 105 019 S 3 Budget Balance
R-ACB-COM-BAL 124 019 S 3 Commitment Balance
R-ACB-BUDGET-TYPE 143 001 X - Budget Type
FILLER 144 657 X - -


FILLER 801 224 X - -

Chart of Accounts record, SSACCRC.CPY, SQL table name SSRFACC
COBOL FIELD NAME POS’N IN FIELD FIELD DEC. SQL COLUMN SQL FIELD DESCRIPTION COMMENT
RECORD LENGTH TYPE PLACES TYPE
- - - - - SUN_DB char(3) Database Code Mandatory
FILLER 001 003 X - - - Reference Record Type Value ‘ACC’, mandatory
R-AC 004 015 X - ACCNT_CODE char(15) Account Code Mandatory
FILLER 019 046 X - - - -
R-AC-LOOKUP-ID 065 003 X - - - Lookup Id
R-AC-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
FILLER 078 008 X - UPDATED char(8) Date Last Updated
R-AC-NAME 086 030 X - ACCNT_NAME char(30) Account Name Mandatory
R-AT 116 001 X - ACCNT_TYPE char(1) Account Type Mandatory
R-BAL-OPEN 117 001 X - BALNCE_OPN char(1) Open Item or Bal/Fwd Mandatory
R-AC-SUSPEND 118 001 X - SUSPEND char(1) Account Status
R-CONV-CODE- 119 001 X - CONV_CNTRL char(1) Conv. Code Control

CONTROL
R-AC-CONV-CODE 120 005 X - CONV_CODE char(5) Conversion Code
R-AC-SUPP-REVAL 125 001 X - SUPP_REVAL char(1) Suppress Revaluation
R-COMMITMENT- 126 015 X - COMMIT_ACC char(15) Commitment Check Account

CHECK-ACCOUNT

R-AC-COMMENT 141 020 X - COMMENTS char(20) Comment
FILLER 161 001 X - - - -
R-ACC-ENTER-ANAL- 162 010 X - ENTER_ANAL char(10) Enter Analysis Codes One for each
INDS T-code, T0 - T9
R-AC-ADD 172 010 X - ADD_CODE char(10) Address Code
R-DIRECT-DEBIT 182 001 X - DIRECT_DB char(1) Direct Debit Indicator
R-PRIORITY 183 001 X - PRIORITY char(1) Account Priority
R-PAY-METHOD 184 001 X - PAY_METHOD char(1) Payment Method
R-CREDIT-LIMIT 185 010 N 0 CREDIT_LIM numeric Credit Limit
R-PAYMENT-DAYS 195 003 N 0 PAYMNT_DAY smallint Payment Days
R-PAYMENT-TERMS 198 001 X - PAYMNT_TRM char(1) Payment Terms
R-DISCOUNT-DAYS 199 003 N 0 DISC_DAYS smallint Discount Days 1
R-DISCOUNT 202 005 N 3 DISCOUNT numeric Discount Percent 1

Chart of Accounts record, SSACCRC.CPY, SQL table name SSRFACC – (continued)
R-DISCOUNT-DAYS-2 207 003 N 0 DISC_DAYS2 smallint Discount Days 2
R-DISCOUNT-2 210 005 N 3 DISCOUNT_2 numeric Discount Percent 2
R-LATEST-TRANS 215 008 X - LAST_TRANS char(8) Last Transaction Date
R-TRANS-PRESENT 223 001 X - TRANS_PRES char(1) Transactions Present Ind’r
R-AC-BALANCE 224 019 S 3 ACC_BALNCE numeric Account Balance
R-AC-ORDER-BALANCE 243 019 S 3 ORD_BALNCE numeric On-Order Balance
R-ALLOC-IN-PROGRESS 262 001 X - ALLOC_PROG char(1) Allocation-in-Progress Ind’r
R-USER-AREA 263 030 X - USER_AREA char(30) Area not used by SunSystems
R-TAX-CODE 293 020 X - TAX_CODE char(20) Tax Code
R-AN-0 313 015 X - ANAL_A0 char(15) Account Analysis Code 0

FILLER 463 064 X - - - -
R-AC-GRP-MASK 527 005 X - DATA_1 char(5) Operator Group Mask
FILLER 532 005 X - - - -
R-SETTLEMENT 537 001 X - SETTLEMENT char(1) Settlement Account
R-AC-LINK-ACCOUNT 538 010 X - LINK_ACC char(10) Linked Account
R-AC-DEF-BANK-CODE 548 005 X - DEF_BANK_CODE char(5) Default Bank Code
R-ACC-DAYS- 553 001 X - OVER_TOL_IND char(1) Override Days Tolerance from

OVERRIDE-IND Journal Definition
R-ACC-DAYS-TO-APPLY 554 002 N - TOL_DAYS smallint Days to apply
R-ALLOC-USER-ID 556 003 X - ALLOC_USER char(3) Allocation In Progress User ID

Chart of Accounts record, SSACCRC.CPY, SQL table name SSRFACC
- - - - - PAYTO_BANK char(15) Own Bank Account Details Relevant only to Debtor, Creditor and
Client Account Types
R-ACC-PAYTO-ACC 559 010 X - - - Own Bank Account Details - Account
R-ACC-PAYTO-SUB 569 005 X - - - Own Bank Account Details - Subcode
FILLER 574 227 X - - - -
FILLER 801 224 X - - - -

Generate Payments/Debits Selection, SAACPRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ACP’, mandatory
R-ACP-PROFILE-CODE 004 005 X - Payment Profile Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-ACP-LOOKUP-ID 065 003 X - Lookup Id
R-ACP-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-ACP-CASH-AC 086 015 X - Cash Account Code
R-ACP-DISC-AC-CR 101 015 X - Input (Creditor) Discount Account Code
R-ACP-DISC-AC-DR 116 015 X - Output (Debtor) Discount Account Code
R-ACP-BANK-REF 131 018 X - Default Bank transaction Reference
R-ACP-BANK-FILE-ID 149 003 X - Bank File Identifier
R-ACP-ANAL-CODES 152 150 X - Analysis Codes (10 x 15)
R-ACP-SUPP-TRANS 302 001 X - Suppress Report Transactions
R-ACP-PAY-BASE-DATE 303 008 N - Payment Base Date
R-ACP-DISC-BASE-DATE 311 008 N - Discount Base Date

R-ACP-PAY-DATE 319 008 N - Payment Date
R-ACP-NEXT-PAY-DATE 327 008 N - Next Payment Date
FILLER 335 153 X -
R-ACP-TYPE 488 001 X - Used by SARB
R-ACP-COST-AC 489 015 X - Used by SARB
R-ACP-PAY-CODE-1 504 002 X - Used by SARB
R-ACP-COUNTRY-CAT 512 001 X - Used by SARB

Generate Payments/Debits Selection, SAACPRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-ACP-LDG-PAY-REF 513 010 X - Used by SARB
R-ACP-SINGLE-PAYMENT 523 001 X - Used by SARB
R-ACP-PRINT-LINK 524 001 X Used by SARB
R-ACP-SELECTION-FROM-1 525 015 X Selection Codes
R-ACP-SELECTION-TO-1 600 015 X Selection Codes
R-ACP-SELECTION-CODE (1) 675 002 X Selection Codes

FILLER 685 340 X Filler

Address Analysis record, SSADBRC.CPY, SQL table name SSRFADB
FILLER 001 003 X - - - Reference Record Type Value ‘ADB’, mandatory
R-ADB 004 010 X - ADB_CODE char(10) Address Code Mandatory
FILLER 014 051 X - - -
R-ADB-LOOKUP-ID 065 003 X - - - Lookup Id
R-ADB-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
R-ADD-ACCOUNT-CODE 086 015 X - ACCNT_CODE char(15) Account Code Mandatory
R-ADD-ANAL-ADDR 101 001 X - ANAL_ADDR char(1) Address Analysis Ind’r
R-ADD-PICK-METHOD 102 001 X - PICK_METH char(1) Pick Method
R-ADD-PRIORITY 103 001 X - PRIORITY char(1) Priority
R-ADD-MIN-ORDER-VALUE 104 018 N 5 MIN_ORDER numeric Minimum Order Value
R-ADD-LAST-TRANS 122 008 X - LAST_TRAN char(8) Last Transaction Date
R-ADD-TRANS-PRESENT 130 001 X - TRAN_PRES char(1) Transactions Present Ind’r
R-ADD-AN-0 131 015 X - ANAL_C0 char(15) Address Analysis Code 0

R-ADD-CRED-LIM-BLOCK 281 1 X - CRED_LIM_BLOCK char(1) SOP Credit limit blocking flag
R-ADD-DEF-POD-TYPE 282 005 X - DEF_POD_TYPE char(5) Default Purchase Order Type
FILLER 287 514 X - - - -
FILLER 801 224 X - - - -

Names and Addresses record, SSADDRC.CPY, SQL table name SSRFADD
FILLER 001 003 X - - - Reference Record Type Value ‘ADD’, mandatory
R-ADD 004 010 X - ADD_CODE char(10) Address Code Mandatory
FILLER 014 051 X - - -
R-ADD-LOOKUP-ID 065 003 X - - - Lookup Id
R-ADD-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
R-ADD-LINE-1 086 035 X - ADDRESS_1 char(35) Address Line 1 Mandatory
R-ADD-LINE-2 121 035 X - ADDRESS_2 char(35) Address Line 2
R-ADD-COMMENT-1 296 015 X - TELEPHONE char(15) Telephone Number
R-ADD-COMMENT-2 311 015 X - CONTACT char(15) Contact
R-ADD-TELEX 326 015 X - TELEX char(15) Telex Number

R-ADD-COMMENT-3 341 030 X - COMMENT_1 char(30) Comment
R-ADD-USER-AREA 371 003 X - USER_AREA char(03) Area unused by SunSystems
R-ADD-COMMENT-4 374 030 X - COMMENT_2 char(30) Comment
R-ADD-EMAIL-ADDRESS 404 124 X - E_MAIL char(124) Email Address
R-ADD-WEB-PAGE- 528 124 X - WEB_PAGE char(124) Web Page Address

ADDRESS
- - - - - DEF_OBA char(15) Default Own Bank Account Details Relevant only to account code
‘0000000000’
R-ADD-DEF-OBA-ACC 652 010 X - - - Default Own Bank Account Details -

Account
R-ADD-DEF-OBA-SUB 662 005 X - - - Default Own Bank Account Details -

Subcode
FILLER 667 134 X - - - -
FILLER 801 224 X - - - -

Journal Definitions record, SAAJDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘AJD’, mandatory
R-AJD-JOURNAL-TYPE 004 005 X - Journal Type Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-AJD-LOOKUP-ID 065 003 X - Lookup Id
R-AJD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-AJD-JOURNAL-NAME 086 025 X - Journal Name
R-AJD-PRESET-CODE 111 005 X - Journal Preset Code
R-AJD-ANAL-CAT1 116 002 X - Analysis Category 1

R-AJD-SUPPRESS-AGEING 136 001 X - Suppress Ageing
R-AJD-DESC-PER-LINE 137 001 X - Description per Line
R-AJD-FORCE-WITHHOLD 138 001 X - Allocation Marker
R-AJD-NEXT-PERIOD-REVERSAL 139 001 X - Next Period Reversal
R-AJD-DUE-DATE-ENTRY 140 001 X - Due Date Entry
R-AJD-UNIQUE-REFERENCES 141 001 X - Unique References
R-AJD-CREATE-WITHOUT-PAUSE 142 001 X - Create Without Pause
R-AJD-CONVERSION 143 001 X - Conversion

Journal Definitions record, SAAJDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-AJD-ASSET-ENTRY 144 001 X - Asset Details Entry
R-AJD-SUPPRESS-JE 145 001 X - Suppress Journal Entry
R-AJD-SUPPRESS-JI 146 001 X - Suppress Journal Import
R-AJD-SUPPRESS-AA 147 001 X - Suppress Account Allocation
R-AJD-SEQ-CODE 148 005 X - Sequence Code
R-AJD-TRANS-SEQ 153 001 X - Transaction Sequence
R-AJD-INPUT-DISC-ACC 154 015 X - Input Discount Account
R-AJD-OUTPUT-DISC-ACC 169 015 X - Output Discount Account
R-AJD-DISC-TOL-PERC 184 011 N 2 Discount Tolerance Percent
R-AJD-DISC-TOL-VAL 195 012 N 3 Discount Tolerance Value
R-AJD-AUTO-TAX-IND 207 001 X - Automatic Tax Indicator
R-AJD-TAX-ACC-IND-CR 208 001 X - Tax Ind Creditors
R-AJD-TAX-ACC-IND-DB 209 001 X - Tax Ind Debtors
R-AJD-TAX-ACC-IND-CT 210 001 X - Tax Ind Clients
R-AJD-TAX-ACC-IND-MEM 211 001 X - Tax Ind Members
R-AJD-TAX-ACC-IND-PL 212 001 X - Tax Ind Profit & Loss

R-AJD-TAX-ACC-IND-BAL 213 001 X - Tax Ind Balance
R-AJD-STP-ACC-IND-CR 214 001 X - Stoppage Tax Creditors
R-AJD-STP-ACC-IND-DB 215 001 X - Stoppage Tax Debtors
R-AJD-STP-ACC-IND-CT 216 001 X - Stoppage Tax Clients
R-AJD-STP-ACC-IND-MEM 217 001 X - Stoppage Tax Members
R-AJD-STP-ACC-IND-PL 218 001 X - Stoppage Tax Profit & Loss
R-AJD-STP-ACC-IND-BAL 219 001 X - Stoppage Tax Balance
R-AJD-AUTO-TAX-ACC 220 001 X - Input/Output Tax Ind
R-AJD-EUR-TO-OV 221 001 X - Zero Tol Flag for Euro
R-AJD-OTHER-AMT-BAL-OV 222 001 X - Other Amount Balance Override
R-AJD-DISC-TOL-DAYS 223 002 N - Discount Tol Days
R-AJD-DISCOUNT-OVERRIDE 225 001 X - Discount Override

Journal Definitions record, SAAJDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 226 301 X -
R-AJD-GRP-MASK 527 005 X - Operator Group Mask
FILLER 532 069 X -
FILLER 601 200 X -
FILLER 801 224 X -

Journal Presets record, SAAJPRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘AJP’, mandatory
R-AJP-PRESET-CODE 004 005 X - Preset Code Mandatory
R-AJP-LINE-NO 009 003 N - Transaction Line Number Mandatory
FILLER 012 021 X -
FILLER 033 032 X -
R-AJP-LOOKUP-ID 065 003 X - Lookup Id
R-AJP-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-AJP-LINE-PROMPT 086 025 X - Line Prompt
R-AJP-BASE-LINE-NO 111 003 N - Base Line Number
R-AJP-ACC-PERIOD 114 008 X - Accounting Period
R-AJP-TRANSACTION-DATE 122 010 X - Transaction Date
R-AJP-DUE-DATE 132 010 X - Due Date
R-AJP-DESCRIPTION 142 025 X - Description
R-AJP-ACC-CODE 167 015 X - Account Code
R-AJP-ACC-TYPE 182 001 X - Account Type

R-AJP-ASSET-CODE 183 010 X - Asset Code
R-AJP-ASSET-SUBCODE 193 005 X - Asset Sub Code
R-AJP-VD 198 001 X - Value/Depreciation Marker
R-AJP-CONV-CODE 199 005 X - Conversion Code
R-AJP-OTHER-AM 204 016 X - Transaction Other Amount
R-AJP-CONV-RATE 220 019 X - Conversion Rate
R-AJP-AM 239 016 X - Transaction Amount
R-AJP-DC 255 001 X - Debit/Credit
R-AJP-ANAL-1 256 015 X - Preset Analysis Code 1

Journal Presets record, SAAJPRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-AJP-AUTO-ONLINE-ALLOC 406 001 X - Automatic Online Allocation
R-AJP-FORCE-PRESET 407 001 X - Force Preset
R-AJP-2ND-ACC-TYPE 408 001 X - 2nd Account Type
FILLER 409 124 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Calendar Definition record, SCALCRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ALC’, mandatory
ALC-PERIOD 004 007 N - Calendar Month Mandatory
FILLER 011 022 X - -
FILLER 033 032 X - -
ALC-LOOKUP-ID 065 003 X - Lookup Id
ALC-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
ALC-EXCL-DAY(1) 086 001 X - Exclude date 1
ALC-PER-START(1) 087 003 N - Period Start 1


Calendar Definition record, SCALCRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)


ALC-PER-START (20) 163 003 N - Period Start 20

Calendar Definition record, SCALCRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 210 323 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Allocation Definitions record, SCALDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ALD’, mandatory
ALD-DEFINITION-CODE 004 005 X - Alloc’n Definition Code Mandatory
ALD-SEQ-NO 009 005 X - Alloc’n Sequence Number Mandatory
FILLER 014 019 X - -
FILLER 033 032 X - -
ALD-LOOKUP-ID 065 003 X - Lookup Id
ALD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
ALD-NAME 086 025 X - Alloc’n Definition Name Mandatory
ALD-TYPE 111 001 X - Allocation Type Mandatory
ALD-SOURCE-CODE 112 005 X - Alloc’n Source Code
ALD-TARGET-CODE 117 005 X - Alloc’n Target Code
ALD-RATIO-CODE 122 005 X - Alloc’n Ration Code
ALD-TRNSFR-PER-FROM 127 005 X - Transfer Period From
ALD-TRNSFR-PER-TO 132 005 X - Transfer Period To
ALD-JOURNAL-TYPE 137 005 X - Alloc’n Journal Type Mandatory

ALD-SOURCE-DB-POSTING 142 001 X - Source Database Posting Mandatory
ALD-TARGET-DB-POSTING 143 001 X - Target Database Posting Mandatory
ALD-BASE-AMT 144 001 X - Alloc’n Base Amount
ALD-OTHER-AMT 145 001 X - Alloc’n Other Amount
ALD-AMOUNT-REVERSAL 146 001 X - Alloc’n Amount Reversal
ALD-UPDATE-ASSETS 147 001 X - Update Assets
ALD-TL-TARGET 148 001 X - Target and Source Reversal
ALD-TL-OFFSET 149 001 X - Include Offset
ALD-RETAIN-JOURNAL-TYPE 150 001 X - Retain Journal Type
ALD-RETAIN-JOURNAL-SOURCE 151 001 X - Retain Journal Source
FILLER 152 381 X - -

Allocation Definitions record, SCALDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 533 268 X - -
FILLER 801 224 X - -

Allocation Ratio record, SCALRRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ALR’, mandatory
ALR-RATIO-CODE 004 005 X - Allocation Ratio Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
ALR-LOOKUP-ID 065 003 X - Lookup Id
ALR-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
ALR-NAME 086 025 X - Allocation Ratio Name Mandatory
ALR-ACCT-FROM(1) 111 015 X - Ratio Account From 1 Mandatory
ALR-ACCT-TO(1) 126 015 X - Ratio Account To 1
ALR-ACCT-FROM(2) 141 015 X - Ratio Account From 2

ALR-AN-CODE(1) 261 002 X - Ratio Analysis Code 1
ALR-AN-CODE-FROM(1) 263 015 X - Ratio Analysis Code From 1
ALR-AN-CODE-TO(1) 278 015 X - Ratio Analysis Code To 1
ALR-AMT 357 001 X - Ratio Amount Mandatory

Allocation Ratio record, SCALRRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

ALR-ACT-BUD 358 001 X - Ratio Actual/Budget Mandatory
ALR-BASIS 359 001 X - Ratio Basis Mandatory
FILLER 360 173 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Allocation Source record, SCALSRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ALS’, mandatory
ALS-SOURCE-CODE 004 005 X - Allocation Source Code Mandatory
ALS-CONTINUE 009 001 X - Alloc’n Source Continuation
FILLER 010 023 X - -
FILLER 033 032 X - -
ALS-LOOKUP-ID 065 003 X - Lookup Id
ALS-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
ALS-NAME 086 025 X - Allocation Source Name Mandatory
ALS-ACCT-FROM 111 015 X - Account Code From Mandatory
ALS-ACCT-TO 126 015 X - Account Code To
ALS-AN-CODE(1) 141 002 X - Selection Code 1
ALS-AN-CODE-FROM(1) 143 015 X - Selection Code From 1
ALS-AN-CODE-TO(1) 158 015 X - Selection Code To 1

ALS-OFFSET-ACCT 237 015 X - Offset Account
ALS-OFFSET-AN 252 010 X - Offset Account Consol’n Table, 10 x 1 byte
ALS-AMT 262 001 X - Source Amount
ALS-ACT-BUD 263 001 X - Actual/Budget
ALS-THRESHOLD-FROM 264 018 N 3 Threshold From
ALS-THRESHOLD-FROM-DC 282 001 X - Threshold From D/C
ALS-THRESHOLD-TO 283 018 N 3 Threshold To
ALS-THRESHOLD-TO-DC 301 001 X - Threshold To D/C

Allocation Source record, SCALSRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

ALS-SOURCE-REVERSE-AN-CODE 302 010 X - Source Reversal Consol’n Table, 10 x 1 byte
ALS-RETAIN-SOURCE-PERIOD 312 001 X - Retain Source Period
FILLER 313 220 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Allocation Target record, SCALTRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ALT’, mandatory
ALT-TARGET-CODE 004 005 X - Target Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
ALT-LOOKUP-ID 065 003 X - Lookup Id
ALT-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
ALT-NAME 086 025 X - Target Name Mandatory
ALT-DBASE-AN-CODE 111 002 X - Target D’base Analysis Code
ALT-DBASE-DBASE-CODE 113 003 X - Target Database Code
ALT-ACT-BUD 116 001 X - Actual/Budget Mandatory
ALT-ACCT 117 015 X - Target Account
ALT-ACCT-AN-CODE 132 010 X - Target A/c Analysis One for each T-code, T0-T9
ALT-OFFSET 142 015 X - Offset
ALT-OFFSET-AN-CODE 157 010 X - Offset A/c Analysis One for each T-code, T0-T9
ALT-ASSET-CODE 167 010 X - Asset Code

ALT-ASSET-SUB-CODE 177 005 X - Asset Sub Code
ALT-ASSET-IND 182 001 X - Asset Indicator
FILLER 183 350 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Allocation Target record, SCALWRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ALW’, mandatory
ALW-OPERATOR 004 003 X - Operator ID Mandatory
FILLER 007 058 X - -
ALW-LOOKUP-ID 065 003 X - Lookup Id
ALW-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
ALW-FILE-NAME 086 030 X - Target Name
FILLER 116 909 X

Allocation Change in Balance record, SCALXRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ALX’, mandatory
ALX-DEFINITION-CODE 004 005 X - Allocation Definition Code Mandatory
ALX-SEQ-NO 009 005 X - Allocation Sequence Number Mandatory
ALX-TYPE 014 001 X - Allocation Type Mandatory
ALX-TYPE-CODE 015 005 X - Allocation Type Code Mandatory
FILLER 020 045 X -
ALX-LOOKUP-ID 065 003 X - Lookup Id
ALX-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
ALX-JOURNAL-NO 086 007 9 - Highest Journal No for processed Allocation

Definition
FILLER 093 932

Analysis Definition record, SSANDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘AND’, mandatory
R-AND-CODE 004 002 X - Analysis Category Mandatory
R-AND-MASK-ID 006 001 X - Analysis Sub Category
FILLER 007 058 X - -
R-AND-LOOKUP-ID 065 003 X - Lookup Id
R-AND-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-AND-DESCR 086 020 X - Analysis Heading Mandatory
R-AND-SHORT-DESCR 106 005 X - Short Heading Mandatory
R-AND-MASK 111 015 X - Sub Category Mask
R-AND-NON-VALIDATE-CODE 126 001 X - Non Validate Code
R-AND-AMEND-CODE 127 001 X - Amend Code
FILLER 128 673 X - -
FILLER 801 224 X - -

Analysis Code record, SSANVRC.CPY, SQL table name SSRFANV
FILLER 001 003 X - - - Reference Record Type Value ‘ANV’, mandatory
R-ANV-CODE 004 002 X - CATEGORY char(2) Analysis Category Mandatory
R-ANV-VALUE 006 015 X - CODE char(15) Analysis Code SQL - not null
FILLER 021 044 X - - - -
R-ANV-LOOKUP-ID 065 003 X - - - Lookup Id
R-ANV-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
R-ANV-NAME 086 030 X - NAME char(30) Analysis Code Name Mandatory
R-ANV-PROHIBIT-POSTING 116 001 X - PROHB_POST char(1) Prohibit Posting
R-ANV-BUDGET-CHECK 117 001 X - BUDGET_CHECK char(1) PO Budget Check Flag
R-ANV-BUDGET-STOP 118 001 X - BUDGET_STOP char(1) PO Stop Flag
FILLER 119 408 X - - - -
R-ANV-GRP-MASK 527 005 X - DATA_1 char(5) Operator Group Mask
FILLER 532 269 X - - - -
FILLER 801 224 X - - - -

Assembly Structure record, SBASTRC.CPY, (SQL table name SSRFAST)
- - - - - SUN_DB Char(3) Database Code Mandatory
FILLER 001 003 X - - - Reference Record Type Value ‘AST’, mandatory
R-AS-ITEM 004 015 X - ITEM_CODE Char(15) Item Code Mandatory
R-AS-PAGE 019 002 N 0 PAGE Smallint Page Number Mandatory
FILLER 021 012 X - - - - -
FILLER 033 032 X - - - - -
R-AS-LOOKUP-ID 065 003 X - - - Lookup ID
R-AS-LOOKUP-CODE 068 010 X - - - Lookup Code
FILLER 078 008 X - - - -
R-AS-ITEM-CODE-1 086 015 X - ITEM_CODE_L1 Char(15) Item Code 1
R-AS-LOCATION-1 101 005 X - LOCATION_L1 Char(5) Location 1
R-AS-QUANTITY-1 106 018 N 5 QUANTITY_L1 Numeric Quantity 1
R-AS-ITEM-CODE-3 162 015 X - ITEM_CODE_L3 Char(15) Item Code-3


Assembly Structure record, SBASTRC.CPY, (SQL table name SSRFAST) – (continued)
R-AS-SUB-TOTALS 428 001 X - SUB_TOTALS Char(1) Subtotals Flag
FILLER 429 372 X - - - -
FILLER 801 224 X - - - -

Budget Check Definitions record, SSBCDRC.CPY, (SQL miscellaneous table SSRFMSC)

R-BCD-REC-TYPE 001 003 X - Reference Record Type Value ‘BCD’, Mandatory
R-BCD-ACCOUNT-FROM 004 015 X - Budget Account From Mandatory
R-BCD-ACCOUNT-TO 019 015 X - Budget Account To
FILLER 034 031 X - - -
R-BCD-LOOKUP-ID 065 003 X - Lookup ID
FILLER 068 018 X - - -
R-BCD-B-CHK-ACCOUNT 086 015 X - Budget Check Account
R-BCD-CAT1 101 002 X - 1st Analysis Category
R-BCD-SUBCAT1 103 001 X - 1st Analysis Sub Category
R-BCD-CAT2 104 002 X - 2nd Analysis Category
R-BCD-SUBCAT2 106 001 X - 2nd Analysis Sub Category
R-BCD-BUDGET-TYPE 107 001 X - Budget Type
R-BCD-CHECK-BOTH 108 001 X Both Analysis codes set Yes or blank
FILLER 109 692 X -
FILLER 801 224 X - -

Bank Details record, SABKARC.CPY, (SQL miscellaneous table SSRFBKA)
FILLER 001 003 X - - - Reference Record Type Value ‘BKA’, Mandatory
R-BKA-CODE 004 015 X BANK_CODE
R-BKA-BANK-CODE 019 005 X BANK_SEQUEN Char(15) Account Code Mandatory

CE
FILLER 024 009 X - - - - -
FILLER 033 032 X
R-BKA-LOOKUP-ID 065 003 X Lookup ID
R-BKA-LOOKUP-CODE 068 010 X LOOKUP Char(10) Lookup Code
FILLER 078 008 X UPDATED Char(08)
R-BKA-BANK 086 025 X BANK Char(25) Bank Name Mandatory
R-BKA-BRANCH 111 025 X BRANCH Char(25) Bank Branch Mandatory
R-BKA-SORT-CODE 136 015 X SORT_CODE Char(15) Sort Code Mandatory
R-BKA-ACC-NAME 151 035 X ACC_NAME Char(35) Account Name Mandatory
FILLER 186 001 X
R-BKA-ACC-NUM 187 034 X ACC_NUM Char(34) Account Number Mandatory

R-BKA-TRANS-LIMIT 221 018 N TRANS_LIMIT numeric Transaction Limit
R-BKA-TRANS-REF 239 018 X TRANS_REF Char(18) Transaction Reference
R-BKA-FIRST-PAYMENT 257 001 X FIRST_PAYME Char(01) First Payment

NT
R-BKA-COMMENTS 258 015 X COMMENTS Char(15) Comments
R-BKA-ADDRESS-CODE 273 010 X ADDRESS_CO Char(10) Address Code

DE
FILLER 283 244 X
R-BKA-DAG-CODE 527 005 X DAG_CODE Char(05) Data Access Code
FILLER 532 493 X

PRINT FORMATS in POP and SOP, SBBPFRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘BPF’, mandatory
BPF-DEFINITION-CODE 004 061 X - Allocation Definition Code Mandatory
BPF-LOOKUP-ID 065 003 X - Lookup Id
BPF-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-BPF-PI-SEL 086 005 X Print Invoice Format default
R-BPF-PV-SEL 091 005 X Print Movements Format default
R-BPF-PS-SEL 096 005 X Print Despatch Format default
R-BPF-PP-SEL 201 005 X Print Picking Format default
R-BPF-PA-SEL 206 005 X Print Acknowledgements Format default
R-BPF-POP-PP-SEL 211 005 X Print Purchase Orders Format default
R-BPF-PQ-SEL 216 005 X Quotation Format default
R-BPF-ANAL-CAT 221 002 X Analysis category default
R-BPF-SOP-SL-SEL 223 005 X Sales Listing
R-BPF-SOP-CL-SEL 228 005 X Customer Listing
R-BPF-POP-PL-SEL 233 005 X Purchase Listing

R-BPF-POP-SL-SEL 238 005 X Supplier Listing
R-BPF-IC-ML-M-SEL 243 005 X Movement Listing - by Reference
R-BPF-IC-IL-SEL 248 005 X Inventory Listing
R-BPF-IC-EI-SEL 253 005 X Expired Items
R-BPF-IC-ML-B-SEL 258 005 X Movement Listing - by Batch
FILLER 263 762 X

Budget Definition record, SABUDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’BUD’, mandatory
R-BUD-BUDGET-CODE 004 001 X - Budget Code Mandatory
FILLER 005 028 X - -
FILLER 033 032 X - -
R-BUD-LOOKUP-ID 065 003 X - Lookup Id
R-BUD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-BUD-BUDGET-NAME 086 015 X - Budget Name Mandatory
R-BUD-ROUGH-BOOK 101 001 X - RoughBook
FILLER 102 425 X - -
R-BUD-GRP-MASK 527 005 X - Operator Group Mask
FILLER 532 001 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Business Definition record, SSBUSRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘LDG’, Mandatory
BUS-CODE 004 003 X - Database Code Mandatory
FILLER 007 058 X -
BUS-LOOKUP-ID 065 003 X - Lookup ID
BUS-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
FILLER 086 030 X -
BUS-CURRENT-PERIOD 116 008 X - Current Period Mandatory
BUS-MAX-PERIODS 124 003 N 0 Maximum Periods in Year Mandatory
BUS-OPEN-PERIOD-FROM 127 008 X - Open Period From
BUS-OPEN-PERIOD-TO 135 008 X - Open Period To
BUS-OPEN-DATE-FROM 143 010 X - Open Date From
BUS-OPEN-DATE-TO 153 010 X - Open Date To
FILLER 163 005 X -
BUS-OVER-EXPEND-CHECK 168 001 X - Over Expend Check
BUS-FIXED-EUR-RATE 169 018 N 9 Euro Rate

FILLER 187 019 X - Spare for SB expansion
FILLER 206 080 X - Used by SA Ledger/Register Definition
BUS-NEXT-ORDER-NO 286 006 N 0 Next Order No
BUS-NEXT-INVOICE-NO 292 006 N 0 Next Invoice No
BUS-NEXT-CR-NOTE-NO 298 006 N 0 Next Credit Note No
BUS-NEXT-P-ORDER-NO 304 006 N 0 Next Purchase Order No
BUS-ANAL-CAT0 310 002 X - LI Analysis Category 0

Business Definition record, SSBUSRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

BUS-CURR-CODE-CAT 330 002 X - Conversion Code
BUS-ORDER-AS-COMMITMENTS 332 001 X - All Order as Commitments
BUS-OMIT-P-ORDERS 333 001 X - Omit Purchase Orders
BUS-P-VAL-BALANCING 334 001 X - Purchase Value Balancing
BUS-P-QTY-BALANCING 335 001 X - Purchase Quantity Balancing
BUS-ALLOC-TYPE 336 001 X - Allocation Type
BUS-AUTO-SALES-REF 337 001 X - Auto Order References
BUS-INT-QTY 338 001 X - Integer Quantities
BUS-SERIAL-TRACKING 339 001 X - Serial Number Tracking
BUS-AUDIT-AS-EXPIRY 340 001 X - Audit Date Expiry
BUS-STOCK-TAKE-PER-YEAR 341 003 N 0 Stock takes per year
BUS-STOCK-TAKE-DEFAULT 344 003 N 0 Default Stock Take Cycle

BUS-STOCK-TAKE-TOLERANCE 347 005 N 3 Stock Take Tolerance
BUS-STOCK-TAKE-APPROVAL 352 001 X - Stock Take Approval
BUS-CONV-CODE-C2 353 005 X - Conversion Code C2
BUS-CONV-CODE-C3 358 005 X - Conversion Code C3
BUS-NEXT-QUOTE-NO 363 006 N 0 Next Quote No
BUS-PICK-ALLOCATION 369 001 X - Pick Allocation
BUS-POST-UNAPP-GRN 370 001 X - Post Unapproved at GRN
BUS-APP-PER-UNAPP 371 001 X - Approved Period Unapp/Current
BUS-CRED-LIM-BLOCK 372 001 X - Credit Limit Block


BUS-ALLOC-OVERLAY 373 001 X - Allocation Overlay
BUS-INV-PAGE-CTRL 374 001 X - Invoice Page Control
BUS-EXCL-DESC-LINES 375 001 X - Exclude Invoice Description Lines
BUS-MULTI-COUNTER 376 001 X - Multiple Invoice Number Counters
BUS-LOC-COST 377 001 X - Location Cost
BUS-LOC-LOCK 378 001 X - Location Lock
BUS-MULTI-DESP-DOCS 379 001 X - Multiple Despatch Counters
BUS-EXCL-DESP-DESC-LINES 380 001 X - Exclude Despatch Description Lines
BUS-LOT-NO-VALIDATION 381 001 X - Lot Number Validation
BUS-AUTO-GENERATE 382 001 X - Auto Generate Item Entry Records Flag
BUS-AMEND-RR-IA 383 001 Amendment of Receipt Ref in Inventory Allocation

flag
BUS-AUTOALLOC-RR-AD 384 001 X - Activation of Automatic Allocation by Receipt

Reference and Audit Date flag
FILLER 385 200 X
BUS-ANAL1 585 002 X - Invoice Prefix Anal 1

BUS-D-ANAL1 593 002 X - Despatch Prefix Anal 1
BUS-VOID-NUMBER 601 001 X - Void Unused Number
BUS-VOID-ADDRESS 602 010 X - Address Code for voiding
BUS-VOID-ORDER-TYPE 612 005 X - Order Type for voiding
BUS-IGR-M-CODE-0 617 001 X - Multiple Inventory References M Code 0


BUS-DEFAULT-LEAD-DAYS 627 003 N 0 Lead Time (days)
BUS-LEAD-ANAL-1 630 002 X - Lead Anal 1
BUS-LEAD-ANAL-2 632 002 X - Lead Anal 2
FILLER 634 018 X -
BUS-VCF-TEMP 652 002 N 0 Temperature Accounting temperature
BUS-VCF-I-CODE 654 001 N 0 I Code to be used for Temperature Accounting
FILLER 655 145 X -
FILLER 800 225 X -

Calculation Definition record, SBCADRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’CAD’, mandatory
R-CAD-CODE 004 003 X - Calculation Code Mandatory
FILLER 007 026 X - -
FILLER 033 032 X - -
R-CAD-LOOKUP-ID 065 003 X - Lookup Id
R-CAD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-CAD-DESCRIPTION 086 030 X - Description Mandatory
R-CAD-SHORT-DESC 116 010 X - Short Description
R-CAD-ID1 126 003 X - Base Value Code
R-CAD-CONSTANT1 129 018 N 5 Constant 1
R-CAD-OP1 147 001 X - Operator 1
R-CAD-ID2 148 003 X - Value Code 2

R-CAD-ACCM-SIGN 195 001 X - Accumulator Sign
R-CAD-ACCM 196 003 X - Accumulator Code
R-CAD-TABLE-NAME 199 005 X - Table Code
R-CAD-TABLE-CAT1 204 002 X - Analysis Category 1
R-CAD-TABLE-CAT2 206 002 X - Analysis Category 2
R-CAD-ITEM-PROCESS 208 001 X - Item Process
FILLER 209 001 X - -
R-CAD-DEC-PL 210 001 X - Decimal Places
R-CAD-QTY-RELATED 211 001 X - Quantity Related Indicator

Calculation Definition record, SBCADRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-CAD-SPLIT-VALUE 212 001 X - Suppress Split Values
R-CAD-CONVERSION-RATE 213 001 X - Conversion Rate Override
R-CAD-PRICR-BOOK-CODE 214 005 X - Price Book Code
FILLER 219 582 X - -
FILLER 801 224 X - -

Calculation Table record, SBCATRC.CPY, SQL table name SSRFCAT
FILLER 001 003 X - - - Reference Record Type Value’CAT’,mandatory
R-CAT-NAME 004 005 X - NAME char (5) Table Code SQL-not null
R-CAT-ANCAT1 009 002 X - CATEGORY_1 char (2) Analysis Category1 SQL-not null
R-CAT-ANCODE1 011 015 X - CODE_1 char(15) Analysis Code 1 SQL-not null
R-CAT-ANCAT2 026 002 X - CATEGORY_2 char (2) Analysis Category 2 SQL-not null
R-CAT-ANCODE2 028 015 X - CODE_2 char(15) Analysis Code 2 SQL-not null
FILLER 043 022 X - - - -
R-CAT-LOOKUP-ID 065 003 X - - - Lookup Id
R-CAT-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
FILLER 078 008 X - UPDATED char (8) Date Last Updated
R-CAT-THRESHOLD(1) 086 013 N 0 THRESH_1 numeric Range From/To Value 1 Mandatory
R-CAT-THRESHOLD(2) 099 013 N 0 THRESH_2 numeric Range From/To Value 2

R-CAT-VALUE(1) 190 018 N 5 VALUE_1 numeric Value 1 Mandatory
R-CAT-VALUE(2) 208 018 N 5 VALUE_2 numeric Value 2
R-CAT-DESCRIPTION 334 030 X - DESCRIPTN char(30) Description

Calculation Table record, SBCATRC.CPY, SQL table name SSRFCAT
R-CAT-RANGE-CODE 364 003 X - RANGE_OF char (3) Ranges of Calc ’n Code Mandatory
R-CAT-PRA(1) 367 001 X - PRA_1 char (1) %, Rate or Amount 1 Mandatory
R-CAT-PRA(2) 368 001 X - PRA_2 char (1) %, Rate or Amount 2
R- CAT-PRA(7) 373 001 X - PRA_7 char (1) %, Rate or Amount 7
FILLER 375 426 X - - - -
FILLER 801 224 X - - - -

Daily Conversion Rate record, SSCNDRC.CPY, SQL table name SSRFCND
- - - - - SUN_DB char (3) Database Code Mandatory
FILLER 001 003 X - - - Reference Record Type Value’CND’,mandatory
R-CND-CODE 004 005 X - CODE char (5) Conversion Code Mandatory
R-CND-DATE 009 008 N 0 CONV_DATE int Date Mandatory
R-CND-AC-FROM 017 015 X - FROM_ACCT char(15) Account Code From SQL not null
FILLER 032 033 X - - -
R-CND-LOOKUP-ID 065 003 X - - - Lookup Id
R-CND-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
FILLER 078 008 X - UPDATED char (8)
R-CND-AC-TO 086 015 X - TO_ACCT char(15)
R-CND-NAME 101 030 X - NAME char(30) Conversion Name Mandatory
R-CND-OPERATOR 131 001 X - OPERATOR char(1) Multiply or Divide Mandatory
R-CND-CONV-RATE 132 018 N 9 RATE numeric Conversion Rate
R-CND-DEC-PLACES 150 001 X - DEC_PLACES char(1) Number of Decimal Places
R-CND-NET-ACCOUNT 151 015 X - NET_ACCT_REAL char(15) Net or Loss Account Code

R-CND-LOSS-ACCOUNT 166 015 X - LOSS_ACCT_REA char(15) Losses Account Code

L
R-CND-GAIN-ACCOUNT 181 015 X - GAIN_ACCT_REAL char(15) Gain Account Code
R-CND-EUR-RATE 196 018 N 9 EURO_RATE Numeric Euro Rate
FILLER 214 587 X - - -
FILLER 816 224 X - - -

Conversion Table record, SSCNVRC.CPY, SQL table name SSRFCNV
- - - - - SUN_DB char( 3) Database Code Mandatory
FILLER 001 003 X - - - Reference Record Type Value ’CNV’, mandatory
R-CNV-CODE 004 005 X - CODE char (5) Conversion Code Mandatory
FILLER 009 001 X - - - -
R-CNV-PERIOD 010 007 X - PERIOD int Accounting Period SQL - not null
R-CNV-AC-FROM 017 015 X - FROM_ACCT char(15) Account Code From SQL - not null
FILLER 032 033 X - - - -
R-CNV-LOOKUP-ID 065 003 X - - - Lookup Id
R-CNV-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
FILLER 078 008 X - UPDATED char (8) -
R-CNV-AC-TO 086 015 X - TO_ACCT char(15) Account Code To
R-CNV-NAME 101 030 X - NAME char(30) Conversion Name Mandatory
R-CNV-OPERATOR 131 001 X - OPERATOR char (1) Multiply or Divide Mandatory
R-CNV-CONV-RATE 132 018 N 9 RATE numeric Primary Conv’n Rate
R-CNV-DEC-PLACES 150 001 X - DEC_PLACES char (1) Decimal Places
R-CNV-NET-ACCOUNT 151 015 X - NET_ACCT_REAL char(15) Net Account Code

R-CNV-LOSS-ACCOUNT 166 015 X - LOSS_ACCT_REAL char(15) Losses Account Code
R-CNV-GAIN-ACCOUNT 181 015 X - GAIN_ACCT_REAL char(15) Gains Account Code
R-CNV-CONV-RATE-2 196 018 N 9 RATE_2 numeric Conversion Rate 2
FILLER 286 015 X - - - -
R-CNV-NET-ACC-NON-REAL 301 015 X - NET_ACCT_NON_REAL char(15) Account Code Net or Loss
R-CNV-LOSS-ACC-NON-REAL 316 015 X - LOSS_ACCT_NON_REAL char(15) -
R-CNV-GAIN-ACC-NON-REAL 331 015 X - GAIN_ACCT_NON_REAL char(15) Account Code Gain
R-CNV-EUR-RATE 346 018 N 9 EURO_RATE Numeric Euro Rate

Conversion Table record, SSCNVRC.CPY, SQL table name SSRFCNV – (continued)
FILLER 364 467 X - - - -
FILLER 831 224 X - - - -

Column Heading record, SACOLRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value’COL’, mandatory
R-COL-CODE 004 002 X - Column Code Mandatory
R-COL-BUDGET 006 001 X - Column Budget Code
R-COL-CONV 007 001 X - Other Amount
FILLER 008 025 X - -
FILLER 033 032 X - -
R-COL-LOOKUP-ID 065 003 X - Lookup Id
R-COL-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-COL-HEADING-1 086 010 X - Column Heading 1
R-COL-CALC 126 003 X - Column Calculation
FILLER 129 404 X - -
FILLER 533 268 X - -

FILLER 801 224 X - -

Financial Analysis Consolidation Record, SACONRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘CON’, mandatory
FILLER 004 061 X - -
R-CON-LOOKUP-ID 065 003 X - Lookup Id
R-CON-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-CON-LEDGER-CODE(1) 086 003 X - Ledger Code


Financial Analysis Consolidation Record, SACONRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

Conversion Definitions Record, SSCVDRC.CPY, (SQL miscellaneous table SSRFMSC)

R-CVD-REC-TYPE 001 003 X - Reference Record Type Value ‘CVD’, Mandatory
R-CVD-CODE 004 005 X - Conversion Definition Code Mandatory
FILLER 009 056 X - -
R-CVD-LOOKUP-ID 065 003 X - Lookup ID
R-CVD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-CVD-CONV-NAME 086 030 X - Conversion Name
R-CVD-CURRENCY-NAME 116 015 X - Currency Name
R-CVD-USE-DAILY 131 001 X - Whether to use Daily Conversion Tables
R-CVD-DAY-LIMIT 132 002 X - No of days validity for Daily rates
R-CVD-NET-AC-REAL 134 015 X - Ledger Reval Diff Account Code (Net/Losses (Realised)
R-CVD-GAIN-AC-REAL 149 015 X - Ledger Reval Diff Account Code (Gains) (Realised)
R-CVD-NET-AC-NON-REAL 164 015 X - Ledger Reval Diff Account Code (Net/Losses) (Non-Realised)
R-CVD-GAIN-AC-NON-REAL 179 015 X - Ledger Reval Diff Account Code (Gains) (Non-Realised)
R-CVD-PAYMENT-AC 194 015 X - Payment Account Code
R-CVD-DEBIT-AC 209 015 X - Debit Account Code

FILLER 224 030 X - -
R-CVD-DEC-PLACES 254 001 X No of decimal places
R-CVD-CURRENCY-UNIT-NAME 255 015 X - Currency unit name
R-CVD-CURRENCY-GENDER 270 001 Zero Tolerance Flag
R-CVD-EUR-ZERO-TOL 271 001 X -
FILLER 272 753 X - -

Daybook Definition record, SADAYRC.CPY, (SQL miscellaneous table SSRFMSC)

DAY-REC-TYPE 001 003 X - Reference Record Type Value ‘DAY’, Mandatory
DAY-DBKEY 004 003 X - Database Code Mandatory
FILLER 007 058 X - - -
FILLER 065 013 X - - -
FILLER 078 008 X - - -
DAY-SQN-CODE 086 005 X - Sequence Code Mandatory
DAY-SEQUENCE-BY 091 001 X - Sequence By Mandatory
DAY-NUMBER-METH 092 001 X - Numbering Method Mandatory
DAY-UPDATE-OPEN 093 001 X - Update Open Date
DAY-LAST-PROC 094 008 X - Last Processed Date
FILLER 102 002 X - - -
DAY-NEXT-PAGE-NUM 104 010 N 0 Next Page Number
DAY-EX-JOURN-F 114 005 X - Exclude Journal From
DAY-EX-JOURN-T 119 005 X - Exclude Journal To
DAY-EX-ACCT-F 124 015 X - Exclude Account From
DAY-EX-ACCT-T 139 015 X - Exclude Account To

DAY-USED-DEFINITIVE 154 001 X - Definitive Request Flag
FILLER 155 646 X - -
FILLER 801 224 X - -

Daybook Listing Reference Record, SADBKRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘DBK’, mandatory
FILLER 004 061 X -
R-DBK-LOOKUP-ID 065 003 X - Lookup Id
R-DBK-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-DBK-DATE-FROM 086 010 X -
R-DBK-DATE-TO 096 010 X
R-DBK-DEFINITIVE 106 001 X
R-DBK-FORMAT-CODE 107 005 X
R-DBK-SEQUENCE-NUMBER-CODE 112 005 X
R-DBK-REPRINT 117 001 X
R-DBK-NEXT-PAGE 118 010 X
FILLER 128 897 X

Document Counter record, SBDCCRC.CPY, (SQL miscellaneous table SSRFMSC)

R-DCC-REC-TYPE 001 003 X - Reference Record Type Value ‘DCC’, Mandatory
R-DCC-PREFIX 004 004 X - Prefix Mandatory
FILLER 008 057 X - - -
R-DCC-LOOKUP-ID 065 003 X - Lookup ID
R-DCC-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
R-DCC-DESCRIP 086 030 X - Description Mandatory
R-DCC-NEXT-NUM 116 006 N - Next Number Mandatory
R-DCC-LAST-DATE 122 008 N - Last Date Mandatory
R-DCC-DATE-CTRL 130 001 X - Document Date Control
R-DCC-STATUS 131 001 X - Status
R-DCC-SUPPRESS-NUM-OV 132 001 X - Suppress Number Override
R-DCC-LOCK 133 001 X - Lock
FILLER 134 393 X - -
R-DCC-GRP-MASK 527 005 X - Operator Group
FILLER 532 269 X - - -

FILLER 801 224 X - - -

Despatch Counter record, SODCDRC.CPY, (SQL miscellaneous table SSRFMSC)

DCD-REC-TYPE 001 003 X - Reference Record Type Value ‘DCD’, Mandatory
DCD-CODE-1 004 015 X - Analysis Code Number 1
FILLER 064 001 X - - -
FILLER 065 013 X - - -
FILLER 078 008 X - - -
DCD-COUNTER 086 004 X - Despatch Counter
FILLER 090 711 X - - -
FILLER 801 224 X - - -

Depreciation Table Heading record, SFDPHRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’DPH’, mandatory
R-DPH-TABLE-CODE 004 005 X - Table Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-DPH-LOOKUP-CODE 065 013 X - Lookup Id & Code
FILLER 078 008 X - -
R-DPH-HEADING-1 086 030 X - Description Line 1 Mandatory
R-DPH-HEADING-2 116 030 X - Description Line 2
FILLER 266 267 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Depreciation Table record, SFDPTRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’DPT’, mandatory
R-DPT-TABLE-CODE 004 005 X - Table Code Mandatory
R-DPT-TABLE-COLUMN 009 002 N 0 Table Column Mandatory
R-DPT-NTH-30-YEARS 011 001 N 0 Set of yrs (1/2...9) Mandatory
FILLER 012 021 X - -
FILLER 033 032 X - -
R-DPT-LOOKUP-CODE 065 013 X - Lookup Code
FILLER 078 008 X - -
R-DPT-HEADING 086 008 X - Heading
R-DPT-VALUE-01 094 005 N 3 Depcn. Percentage for Year 1


Depreciation Table record, SFDPTRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 244 289 - - -
FILLER 533 268 - - -
FILLER 801 224 - - -

Payment Reference Details record, SSESRRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ESR’, Mandatory
R-ESR-CODE 004 015 X - Account Code Mandatory
R-ESR-TRANS-REF 019 015 X - Transaction Reference Mandatory
R-ESR-JRNL-NO 034 007 N 0 Journal Number
R-ESR-JRNL-LINE-NO 041 007 N 0 Journal Line Number
FILLER 048 017 X -
R-ESR-LOOKUP-ID 065 003 X - Lookup ID
R-ESR-LOOKUP-CODE 068 010 X - Lookup Code
R-ESR-DATE-UPD 078 008 X - Date Last Updated
R-ESR-TEXT1 086 040 X - Text 1
R-ESR-TEXT1-FLAG 126 001 X - Text 1 Flag

R-ESR-AMOUNT1 455 019 S 3 Amount 1

Payment Reference Details record, SSESRRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-ESR-AMOUNT1-CD 474 001 X - Amount 1 Credit/Debit Code
R-ESR-CHECKSUM1 575 001 X - Checksum 1

R-ESR-COUNTRY-NAME1 585 010 X - Country Name 1
R-ESR-COUNTRY-CODE1 595 003 X - Country Code 1
R-ESR-COUNTRY-NAME2 598 010 X - Country Name 2
R-ESR-COUNTRY-CODE2 608 003 X - Coutnry Code 2
R-ESR-CURRENCY-CODE1 611 003 X - Currency Code 1
R-ESR-CURRENCY-CODE2 614 003 X - Currency Code 2
R-ESR-FLAG1 617 001 X - Currency Flag 1

Payment Reference Details record, SSESRRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-ESR-REF-NO1 627 030 X - Reference Number 1
R-ESR-REF-NO2 657 030 X - Reference Number 2
R-ESR-OTHER-DATE1 687 008 N 0 Other Date 1

R-ESR-TRANS-PERIOD 735 008 N 0 Transaction Period Posted
R-ESR-TRANS-STATUS 743 002 X - Transaction Status
FILLER 745 280 X - -

Asset Analysis record, SFFAARC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’FAA’, mandatory
R-FAA-ASSET-CODE 004 010 X - Asset Code Mandatory
R-FAA-ASSET-SUB-CODE 014 005 X - Asset Sub Code
FILLER 019 014 X - -
FILLER 033 032 X - -
R-FAA-LOOKUP-ID 065 003 X - Lookup Id
R-FAA-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-FAA-DESC-1 086 030 X - Description
R-FAA-FACTOR 116 010 N 5 Factor
R-FAA-TEMPORARY 126 001 X - Temporary Record
R-FAA-DEPRCN 127 016 S 3 Base Depreciation
R-FAA-OTHER-DEPRCN 143 016 S 3 Other Depreciation
R-FAA-GROSS 159 016 S 3 Base Gross Value
R-FAA-NET 175 016 S 3 Base Net Value
R-FAA-OTHER-GROSS 191 016 S 3 Other Gross Value

R-FAA-OTHER-NET 207 016 S 3 Other Net Value
R-FAA-AN-0 223 015 X - Analysis Code 0
FILLER 373 160 X - -

Asset Analysis record, SFFAARC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 533 268 X - -
FILLER 801 224 X - -

Asset Budget record, SFFBRRC.CPY, SQL table name SSRFFBR
COBOL FIELD NAME POS’N IN FIELD FIELD DEC. SQL COLUMN SQL DESCRIPTION COMMENT
RECORD LENGTH TYPE PLACES FIELD
TYPE
FILLER 001 003 X - - - Reference Record Type Value ’FBR’,

mandatory
R-FBR-ASSET-CODE 004 010 X - ASSET_CODE char(10) Asset Code Mandatory
R-FBR-BUDGET-CODE 014 001 X - BUDGET char (1) Budget Code Mandatory
FILLER 015 018 X - - - -
FILLER 033 032 X - - - -
R-FBR-LOOKUP-ID 065 003 X - - - Lookup Id
R-FBR-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
FILLER 086 025 X - - - -
R-FBR-STATUS 111 001 X - STATUS char (1) Asset Status
R-FBR-START-PERIOD 112 008 X - START_PERD char (8) Start Period Deprec’n
R-FBR-END-PERIOD 120 008 X - END_PERD char (8) End Period Deprec’n
R-FBR-LAST-PERIOD 128 008 X - LAST_PERD char (8) Last Period Deprec’n
R-FBR-DISPOSAL-PERIOD 136 008 X - DISP_PERD char (8) Disposal Period

R-FBR-BS-AC 144 015 X - BS_AC char(15) Deprec’n Balance Sheet

Account
R-FBR-PL-AC 159 015 X - PL_AC char(15) Deprec’n P&L Account
R-FBR-ASSET-DISPOSED 174 001 X - DISPOSED char (1) Asset Disposed
R-FBR-TRANS-PRESENT 175 001 X - TRANS_PRES char (1) Transactions Present
R-FBR-LATEST-TRANS 176 008 X - LAST_TRANS char (8) Last Transaction
R-FBR-BASE-GROSS-VAL 184 019 S 3 BASE_GROSS numeric Base Gross Value
R-FBR-BASE-ACCUM-DEP 203 019 S 3 BASE_DEP numeric Base Accumulated Deprec’n
R-FBR-BASE-NET-VAL 222 019 S 3 BASE_NET numeric Base Net Value
R-FBR-BASE-DEP-METHOD 241 001 X - BASE_METH char (1) Base Deprec’n Method
R-FBR-BASE-PERCENT 242 005 N 3 BASE_PERC numeric Base Deprec’n Percent
R-FBR-BASE-FINAL-VAL 247 018 N 3 BASE_FINAL numeric Base Final Value

Asset Budget record, SFFBRRC.CPY, SQL table name SSRFFBR – (continued)
TYPE
R-FBR-TABLE-CODE 265 005 X - TABLE_CODE char (5) Deprec’n Table Code
R-FBR-TABLE-COLUMN 270 002 N 0 TABLE_COL char (2) Deprec’n Table Column
R-FBR-CONV-CODE 272 005 X - CONV_CODE char (5) Conversion Code
R-FBR-OTHER-GROSS-VAL 277 019 S 3 OTHER_GROS numeric Other Gross Value
R-FBR-OTHER-ACCUM-DEP 296 019 S 3 OTHER_DEP numeric Other Accumulated

Deprec’n
R-FBR-OTHER-NET-VAL 315 019 S 3 OTHER_NET numeric Other Net Value
R-FBR-OTHER-DEP-METHOD 334 001 X - OTHER_METH char (1) Other Deprec’n Method
R-FBR-OTHER-PERCENT 335 005 N 3 OTHER_PERC numeric Other Deprec’n Percent
R-FBR-OTHER-FINAL-VAL 340 018 N 3 OTHER_FINL numeric Other Final Value
R-FBR-OTHER-TABLE-CODE 358 005 X - OTHER_CODE char (5) Other Deprec’n Table Code
R-FBR-OTHER-TABLE-COLUMN 363 002 N 0 OTHER_COL char (2) Other Deprec’n Table

Column
FILLER 365 184 X - - - -
R-FBR-EXC-FV-OVR 549 001 X - FV_OVER char (1) Final Value Calculation

Override

R-FBR-BASE-DAYS-FIRST- 550 003 N 0 BASE_DAYS_1ST_PD int Depreciation Base Days 1st

PERIOD period
R-FBR-BASE-ACTIVE-DAYS 553 003 N 0 BASE_ACTIVE_DAYS int Depreciation Active Days
R-FBR-OTHER-DAYS-FIRST- 556 003 N 0 OTHER_DAYS_1ST_PD int Depreciation Other Days 1st

PERIOD Period
R-FBR-OTHER-ACTIVE-DAYS 559 003 N 0 OTHER_ACTIVE_DAYS int Depreciation Other Active

days
R-FBR-LAST-DEP-AM 562 019 S 3 FIELD LAST_DEP_AM numeric Last Depreciation Amount
R-FBR-LAST-DEP-O-AM 581 019 S 3 FIELD numeric Last Depreciation Other

LAST_DEP_O_AM Amount
R-FBR-BASE-POST-FINAL-VAL 600 018 N 3 BASE_POST_FIN_VAL numeric Depreciation Base Post final

value
R-FBR-OTHER-POST-FINAL-VAL 618 018 N 3 OTHER_POST_FIN_VAL numeric Depreciation Other Post final

value
FILLER 636 389 X - - - -

Calculate Depreciation Selection Record, SFFCDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘FCD’, mandatory
FILLER 004 061 X -
R-FCD-LOOKUP-ID 065 003 X - Lookup Id
R-FCD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-FCD-BS-AC 086 015 X - Default Balance Sheet Account
R-FCD-PL-AC 101 015 X Default Profit & Loss Account
R-FCD-POST-PERIOD 116 001 X Default Posting Period (S=Single, H=Historic)
R-FCD-CONSOL-T0-YES 117 001 X
R-FCD-CONSOL-T0-FROM 118 015 X
R-FCD-CONSOL-T0-TO 133 015 X


Calculate Depreciation Selection Record, SFFCDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 426 599 X

Asset Disposal Record, SFFDIRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘FDI’, mandatory
FILLER 004 061 X -
R-FDI-LOOKUP-ID 065 003 X - Lookup Id
R-FDI-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-FDI-PL-AC 086 015 X - Default Profit and Loss Account
R-FDI-DIS-SUS-AC 101 015 X - Disposal Suspense Account
FILLER 116 909 X -

Asset Diary record, SFFDRRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value’FDR’, mandatory
R-FDR-ASSET-CODE 004 010 X - Asset Code Mandatory
R-FDR-ASSET-DIARY-CODE 014 005 X - Asset Diary Code
FILLER 019 014 X - -
FILLER 033 032 X - -
R-FDR-LOOKUP-ID 065 003 X - Lookup Id
R-FDR-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-FDR-DESC-1 086 030 X - Description Line 1
R-FDR-SERIAL-NO 206 030 X - Serial No
R-FDR-PUR-DATE 236 008 X - Purchase Date
R-FDR-PUR-PRICE 244 016 N 3 Purchase Price
R-FDR-COMM-DATE 260 008 X - Commission Date

R-FDR-INSURE-VAL 268 016 N 3 Insure Value
R-FDR-INSURE-DUE-PER 284 003 N 0 Insure Due Period
R-FDR-INSURE-DESC 287 015 X - Insure Description
R-FDR-DE-COMM-DATE 302 008 X - De-commission Date
R-FDR-DISPOSAL-DATE 310 008 X - Disposal Date
R-FDR-DISPOSAL-PRICE 318 016 N 3 Disposal Price
R-FDR-DISPOSAL-REF 334 015 X - Disposal Ref
R-FDR-MAINT-FREQ 349 005 X - Maintenance Freq
R-FDR-MAINT-DESC 354 015 X - Maintenance Descr
FILLER 369 164 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Formatted Layout record, SAFLTRC.CPY, (SQL miscellaneous table SSRFMSC)

R-FLT-KEY-TYPE 001 003 X - Reference Record Type Value ’FLT’, mandatory
R-FLT-CODE 004 005 X - Layout Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-FLT-LOOKUP-ID 065 003 X - Lookup Id
R-FLT-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-FLT-LAYOUT-NAME 086 025 X - Layout Name Mandatory
R-FLT-ACCOUNT-TYPE-1 111 001 X - Account Type 1 (Debtor)
R-FLT-ACCOUNT-TYPE-2 112 001 X - Account Type 2 (Creditor)
R-FLT-ACCOUNT-TYPE-3 113 001 X - Account Type 3 (Client)
R-FLT-ACCOUNT-TYPE-4 114 001 X - Account Type 4 (B/S)
R-FLT-ACCOUNT-TYPE-5 115 001 X - Account Type 5 (P/L)
R-FLT-ACCOUNT-TYPE-6 116 001 X - Account Type 6 (Memo)
R-FLT-SELECTION-CODE-1 117 002 X - Selection Code 1

R-FLT-SELECTION-FROM-1 127 015 X - Selection Code From 1
R-FLT-SELECTION-TO-1 202 015 X - Selection Code To 1

Formatted Layout record, SAFLTRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-FLT-DATE-PERIOD-IND 277 001 X - Select by Date/Period Mandatory
R-FLT-REPORT-TRANSACTIONS 278 001 X - Report Transactions
R-FLT-FORMAT-CODE 279 005 X - Format Code Mandatory
R-FLT-INCLUDE-GP 284 001 X - Include group
FILLER 285 248 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Format Definition record, SAFMTRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘FMT’,Mandatory
R-FMT-FORMAT-CODE 004 005 X - Format Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-FMT-LOOKUP-ID 065 003 X - Lookup Id
R-FMT-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-FMT-FORMAT-DESC 086 025 X - Format Description Mandatory
R-FMT-FORMATTER 111 005 X - Formatter Name Mandatory
R-FMT-FORMAT-TITLE 116 025 X - Format Title
R-FMT-CHEQUE-NO 141 010 N - Cheque Number
R-FMT-CHEQUE-OV 151 001 X - Suppress Cheque Number Override
R-FMT-ALLOCATION-FROM 152 001 X - Allocation Marker From
R-FMT-ALLOCATION-TO 153 001 X - Allocation Marker To
R-FMT-ALLOCATION-NEW 154 001 X - New Allocation Marker
R-FMT-ALLOC-SEQ 155 001 X - Allocation Sequence

R-FMT-ALLOC-CEILING 156 001 X - Allocation Marker Ceiling
FILLER 157 376 X - -
FILLER 533 268 X - -
FILLER 801 224 X -

User Format Code Record, SAFMXRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘FMX’, mandatory
FILLER 004 061 X -
R-FMX-LOOKUP-ID 065 003 X - Lookup Id
R-FMX-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-FMX-FORMAT-CODE-D 086 005 X - Statements Format Code - Debtor
R-FMX-FORMAT-CODE-C 091 005 X - Statements Format Code – Creditor
R-FMX-FORMAT-CODE-T 096 005 X Statements Format Code – Client
R-FMX-FORMAT-CODE-P 101 005 X Statements Format Code – Profit & Loss
R-FMX-FORMAT-CODE-B 106 005 X Statements Format Code – Balance Sheet
R-FMX-FORMAT-CODE-REM 111 005 X Statements Format Code – Remittances
R-FMX-FORMAT-CODE-PAY 116 005 X Statements Format Code – Payments
R-FMX-FORMAT-CODE-M 121 005 X Statements Format Code - Memo
FILLER 126 899 X -

Financial Table Columns record, SAFTCRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’FTC’, Mandatory
R-FTC-COL-CONTENT-CODE 004 005 X - Column Content Code Mandatory
R-FTC-COL-NUMBER 009 002 N - Column Number Mandatory
FILLER 011 022 X - -
FILLER 033 032 X - -
R-FTC-LOOKUP-ID 065 003 X - Lookup Id
R-FTC-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-FTC-COL-TYPE 086 001 X - Column Type Mandatory
R-FTC-BASIS 087 002 X - Column Basis
R-FTC-RANGE-FROM 089 015 X - Column Basis Range From
R-FTC-RANGE-TO 104 015 X - Column Basis Range To
R-FTC-PRINT-COL 119 002 X - Print Column
R-FTC-FORMAT 121 001 X - Format
R-FTC-HEADING-1 122 010 X - Heading Line 1

R-FTC-COL-DATA 162 002 X - Column Data
R-FTC-ACTUAL-BUDGET 164 001 X - Actual/Budget
R-FTC-OTHER-AMOUNT 165 001 X - Other Amount
R-FTC-SUBSIDIARY 166 003 X - Subsidiary Ledger
R-FTC-SELECTION-1-CODE 169 002 X - Selection Category 1
R-FTC-SELECTION-1-FROM 171 015 X - Selection Code 1 From
R-FTC-SELECTION-1-TO 186 015 X - Selection Code 1 To
R-FTC-SELECTION-2-FROM 203 015 X - Selection Code 2 To
R-FTC-SELECTION-2-TO 218 015 X - Selection Code 2 From

Financial Table Columns record, SAFTCRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-FTC-SELECTION-3-FROM 235 015 X - Selection Code 3 To
R-FTC-SELECTION-3-TO 250 015 X - Selection Code 3 From
R-FTC-FIRST-ENTRY-CODE 265 002 N - Column Number 1
R-FTC-FIRST-ENTRY-TYPE 267 001 X - Row/Statistic 1
R-FTC-OPERATOR 268 001 X - Operator
R-FTC-SECOND-ENTRY-CODE 269 002 N - Column Number 2
R-FTC-SECOND-ENTRY-TYPE 271 001 X - Row/Statistic 2
R-FTC-REVALUE 272 001 X - Revalue from Other Amount
R-FTC-BRACKET-NEGATIVES 273 001 X - Bracket Negatives
R-FTC-SUPPRESS-AMOUNT 274 001 X - Suppress Amount
R-FTC-SUPPRESS-MATH-TOTAL 275 001 X - Suppress Math Total
R-FTC-COL-DEC-PL 276 001 X - Decimal Places
FILLER 277 256 X - -
FILLER 533 268 X - -
FILLER 801 224 - - -

Financial Table Format record, SAFTFRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’FTF’, Mandatory
R-FTF-TABLE-CODE 004 005 X - Table Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-FTF-LOOKUP-ID 065 003 X - Lookup Id
R-FTF-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-FTF-TABLE-NAME-1 086 030 X - Table Name Line 1 Mandatory
R-FTF-TABLE-NAME-2 116 030 X - Table Name Line 2
R-FTF-ROW-CONTENT-CODE 146 005 X - Row Content Code Mandatory
R-FTF-COL-CONTENT-CODE 151 005 X - Column Content Code Mandatory
R-FTF-LEVEL-2-CAT 156 002 X - Level Code 2 Category
R-FTF-LEVEL-2-SUBCAT 158 001 X - Level Code 2 Sub-Category
R-FTF-LEVEL-2-PRINT-CODE 159 001 X - Report Codes 2
R-FTF-LEVEL-1-CAT 160 002 X - Level Code 1 Category
R-FTF-LEVEL-1-SUBCAT 162 001 X - Level Code 1 Sub-Category

R-FTF-LEVEL-1-PRINT-CODE 163 001 X - Report Codes 1
R-FTF-BRACKET-NEGATIVES 164 001 X - Bracket Negatives
R-FTF-WIDE-COLUMNS 165 001 X - Wide Columns
R-FTF-HELD-JOURNALS 166 001 X - Held Journals
R-FTF-TRANSFER-FORMAT 167 005 X - Transfer Format
R-FTF-TRANSFER-INT-COLS 172 001 X - Transfer Internal Columns
R-FTF-ZERO-SUPPRESS 173 001 X - Row Zero Suppress
R-FTF-INCLUDE-ROUGH 174 001 X - Include Rough Book
R-FTF-SPREAD 175 001 X - Actuals Flag
R-FTF-PAGE-LEVEL 176 001 X - Page Throw
R-FTF-PRINTER-CODE 177 005 X - Printer Code
FILLER 182 345 X - -

Financial Table Format record, SAFTFRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-FTF-GRP-MASK 527 005 X - Operator Group Mask
FILLER 532 001 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Financial Table Row record, SAFTRRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’FTR’, mandatory
R-FTR-ROW-CONTENT-CODE 004 005 X - Row Content Code Mandatory
R-FTR-ROW-LINE-NUMBER 009 005 N - Row Line Number Mandatory
FILLER 014 019 X - -
FILLER 033 032 X - -
R-FTR-LOOKUP-ID 065 003 X - Lookup Id
R-FTR-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-FTR-ROW-TYPE 086 002 X - Row Type Mandatory
R-FTR-ROW-NAME 088 030 X - Row Name
R-FTR-BASIS 118 002 X - Row Basis
R-FTR-RANGE-FROM 120 015 X - Row Basis Range From
R-FTR-RANGE-TO 135 015 X - Row Basis Range To
R-FTR-BREAK-OUT 150 001 X - Break Out Details
R-FTR-NORMAL-SIGN 151 001 X - Normal Sign
R-FTR-AMOUNT-REVERSE 152 001 X - Amount Reverse

R-FTR-SUPPRESS-ROW 153 001 X - Suppress Row
R-FTR-REPORT-CODE 154 001 X - Report Code
R-FTR-UNDERSCORE 155 001 X - Underscore
R-FTR-SELECTION-1-CODE 156 002 X - Selection 1 Code
R-FTR-SELECTION-1-FROM 158 015 X - Selection 1 Range From
R-FTR-SELECTION-1-TO 173 015 X - Selection 1 Range To

Financial Table Row record, SAFTRRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-FTR-COLUMN-CHANGE 252 001 X - Column Change
R-FTR-OFFSET-COLN 253 002 N - Offset Column
FILLER 255 278 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Asset Value record, SFFVRRC.CPY, SQL table name SSRFFVR
FILLER 001 003 X - - - Reference Record Type Value ’FVR’, mandatory
R-FVR-ASSET-CODE 004 010 X - ASSET_CODE char(10) Asset Code Mandatory
FILLER 014 019 X - - - -
FILLER 033 032 X - - - -
R-FVR-LOOKUP-ID 065 003 X - - - Lookup Id
R-FVR-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
R-FVR-NAME 086 025 X - NAME char(25) Asset Name Mandatory
R-FVR-STATUS 111 001 X - STATUS char (1) Asset Status
R-FVR-START-PERIOD 112 008 X - START_PERD char (8) Start Period Deprec’n
R-FVR-END-PERIOD 120 008 X - END_PERD char (8) End Period Deprec’n
R-FVR-LAST-PERIOD 128 008 X - LAST_PERD char (8) Last Period Deprec’n
R-FVR-DISPOSAL-PERIOD 136 008 X - DISP_PERD char (8) Disposal Period
R-FVR-BS-AC 144 015 X - BS_AC char(15) Deprec’n Balance Sheet

Account

R-FVR-PL-AC 159 015 X - PL_AC char(15) Deprec’n P&L Account
R-FVR-ASSET-DISPOSED 174 001 X - DISPOSED char (1) Asset Disposed
R-FVR-TRANS-PRESENT 175 001 X - TRANS_PRES char (1) Transactions Present
R-FVR-LATEST-TRANS 176 008 X - LAST_TRANS char (8) Last Transaction
R-FVR-BASE-GROSS-VAL 184 019 S 3 BASE_GROSS numeric Base Gross Value
R-FVR-BASE-ACCUM-DEP 203 019 S 3 BASE_DEP numeric Base Accumulated Deprec’n
R-FVR-BASE-NET-VAL 222 019 S 3 BASE_NET numeric Base Net Value
R-FVR-BASE-DEP-METHOD 241 001 X - BASE_METH char (1) Base Deprec’n Method
R-FVR-BASE-PERCENT 242 005 N 3 BASE_PERC numeric Base Deprec’n Percent
R-FVR-BASE-FINAL-VAL 247 018 N 3 BASE_FINAL numeric Base Final Value

Asset Value record, SFFVRRC.CPY, SQL table name SSRFFVR – (continued)
R-FVR-TABLE-CODE 265 005 X - TABLE_CODE char (5) Deprec’n Table Code
R-FVR-TABLE-COLUMN 270 002 N 0 TABLE_COL char (2) Deprec’n Table Column
R-FVR-CONV-CODE 272 005 X - CONV_CODE char (5) Conversion Code

Asset Value record, SFFVRRC.CPY, SQL table name SSRFFVR
R-FVR-OTHER-GROSS-VAL 277 019 S 3 OTHER_GROS numeric Other Gross Value
R-FVR-OTHER-ACCUM-DEP 296 019 S 3 OTHER_DEP numeric Other Accumulated Deprec’n
R-FVR-OTHER-NET-VAL 315 019 S 3 OTHER_NET numeric Other Net Value
R-FVR-OTHER-DEP-METHOD 334 001 X - OTHER_METH char (1) Other Deprec’n Method
R-FVR-OTHER-PERCENT 335 005 N 3 OTHER_PERC numeric Other Deprec’n Percent
R-FVR-OTHER-FINAL-VAL 340 018 N 3 OTHER_FINL numeric Other Final Value
R-FVR-OTHER-TABLE-CODE 358 005 X - OTHER_CODE char (5) Other Deprec’n Table Code
R-FVR-OTHER-TABLE-COLUMN 363 002 N 0 OTHER_COL char (2) Other Deprec’n Table Column
R-FVR-AN-O 365 015 X - ANAL_F0 char(15) Analysis Code F0
R-FVR-AN-1 380 015 X - ANAL_F1 char(15) Analysis Code F1

R-FVR-AN-EXTRA 515 034 X - - - Not used at version 4.2
R-FVR-EXC-FV-OVR 549 001 X - FV_OVER char (1) Final Value Calculation override
R-FVR-BASE-DAYS-FIRST- 550 003 N 0 BASE_DAYS_1ST_ int Depreciation Base Days 1st

PERIOD PD period
R-FVR-BASE-ACTIVE-DAYS 553 003 N 0 BASE_ACTIVE_DA int Depreciation Base Active Days

YS
R-FVR-OTHER-DAYS-FIRST- 556 003 N 0 OTHER_DAYS_1S int Depreciation Other Days 1st

PERIOD T_PD period
R-FVR-OTHER-ACTIVE-DAYS 559 003 N 0 OTHER_ACTIVE_ int Depreciation Other Active Days

DAYS
R-FVR-LAST-DEP-AM 562 019 S 3 LAST_DEP_AM numeric Last Depreciation Amount
R-FVR-LAST-DEP-O-AM 581 019 S 3 LAST_DEP_O_AM numeric Last Depreciation Other Amount

Asset Value record, SFFVRRC.CPY, SQL table name SSRFFVR – (continued)
R-FVR-BASE-POST-FINAL-VAL 600 018 N 3 BASE_POST_FIN_ numeric Depreciation Base Posted Final

VAL value
R-FVR-OTHER-POST-FINAL-VAL 618 018 N 3 OTHER_POST_FI numeric Depreciation Other Posted Final

N_VAL Value
FILLER 636 389 X - - - -

Financial Analysis/Statement Layout record, SAGANRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Referenc e Record Type Value ’GAN’, Mandatory
R-REPORT-CODE 004 005 X - Layout Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-GAN-LOOKUP-ID 065 003 X - Lookup Id
R-GAN-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-REPORT-NAME-1 086 030 X - Report Name Line 1 Mandatory
R-REPORT-NAME-2 116 030 X - Report Name Line 2
R-C1-CODE 146 003 X - Column A Code
R-C2-CODE 149 003 X - Column B Code
R-C3-CODE 152 003 X - Column C Code
R-C4-CODE 155 003 X - Column D Code
R-C5-CODE 158 003 X - Column E Code
R-C6-CODE 161 003 X - Column F Code
R-C7-CODE 164 003 X - Column G Code

R-C8-CODE 167 003 X - Column H Code
R-C9-CODE 170 003 X - Column I Code
R-C10-CODE 173 003 X - Column J Code
R-C11-CODE 176 003 X - Column K Code
R-C12-CODE 179 003 X - Column L Code
R-C1-CONV 182 001 X - Column A Other Amount
R-C2-CONV 183 001 X - Column B Other Amount
R-C3-CONV 184 001 X - Column C Other Amount
R-C4-CONV 185 001 X - Column D Other Amount
R-C5-CONV 186 001 X - Column E Other Amount
R-C6-CONV 187 001 X - Column F Other Amount
R-C7-CONV 188 001 X - Column G Other Amount

Financial Analysis/Statement Layout record, SAGANRC.CPY, (SQL misc. table SSRFMSC) – (continued)

R-C8-CONV 189 001 X - Column H Other Amount
R-C9-CONV 190 001 X - Column I Other Amount
R-C10-CONV 191 001 X - Column J Other Amount
R-C11-CONV 192 001 X - Column K Other Amount
R-C12-CONV 193 001 X - Column L Other Amount
R-RATIO-BASE-AC-FIRST 194 015 X - Ratio Base A/c From
R-RATIO-BASE-AC-LAST 209 015 X - Ratio Base A/c To
R-GST-LINE-CODE 224 005 X - Line Content Code Mandatory on Statement Layout
R-PAGE-LEVEL 229 001 X - Page Level
R-AMOUNT-FORMAT 230 001 X - Amount Format
R-REPORT-TRANSACTIONS 231 001 X - Report Transactions
R-REPORT-CODES 232 001 X - Report Codes
R-NEGATIVE-BRACKETS 233 001 X - Bracket Negatives
R-WIDE-COLUMN 234 001 X - Wide Columns
R-ZERO-SUPPRESS 235 001 X - Line Zero Suppress
R-TRANSFER-FORMAT 236 005 X - Transfer Format

R-HELD-JOURNALS 241 001 X - Held Journals
R-GAN-CONSOLIDATE 242 001 X - Consolidate
R-S1-CODE 243 002 X - Selection Category 1
R-L3-CODE 253 002 X - Level Category 3 Mandatory on Analysis Layout
R-L2-CODE 255 002 X - Level Category 2
R-L1-CODE 257 002 X - Level Category 1
R-L3-MASK-ID 259 001 X - Level SubCategory 3

Financial Analysis/Statement Layout record, SAGANRC.CPY, (SQL misc. table SSRFMSC) – (continued)

R-S1-MASK-ID 262 001 X - Selection Sub Category 1
R-S2-MASK-ID 263 001 X - Selection SubCategory 2
R -S4-MASK-ID 265 001 X - Selection SubCategory 4
R-INCLUDE-ROUGH 267 001 X - Include Rough
R-GAN-PRINTER-CODE 268 005 X - Printer Code
FILLER 273 254 X - -
R-GRP-MASK 527 005 X - Operator Group Mask
FILLER 532 001 X -
FILLER 533 268 X -
FILLER 801 224 X -

General Ledger Interface record, SBGLIRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’GLI’, Mandatory
R-GLI-CODE 004 005 X - Interface Code Mandatory
FILLER 009 056 X - -
R-GLI-LOOKUP-ID 065 003 X - Lookup Id
R-GLI-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-GLI-DESCRIPTION 086 030 X - Description Mandatory
R-GLI-JOURNAL-TYPE 116 005 X - Journal Type
R-GLI-ACC-CODE1 121 015 X - Account Code 1
R-GLI-VALUE-CODE1 136 003 X - Base Value 1
R-GLI-CD1 139 001 X - C/D 1
R-GLI-CD2 158 001 X - C/D 2

R-GLI-CD3 177 001 X - C/D 3
R-GLI-CD4 196 001 X - C/D 4
R-GLI-CD5 215 001 X - C/D 5
R-GLI-CD6 234 001 X - C/D 6

General Ledger Interface record, SBGLIRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-GLI-CD7 253 001 X - C/D 7
R-GLI-CD8 272 001 X - C/D 8
R-GLI-CD9 291 001 X - C/D 9
R-GLI-CD10 310 001 X - C/D 10
R-GLI-ACC-CODE1-CONS 311 010 X - Consolidate 12345678910 1

R-GLI-UPDATE-ASSET(1) 411 001 X - Update Assets 1

General Ledger Interface record, SBGLIRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-GLI-OTHER-CODE(1) 421 003 X - Other Value 1
R-GLI-TRA-CODE1 451 006 X - Transfer Data Codes 1 Table, 6 x 1 byte

FILLER 511 290 X - -
FILLER 801 224 X - -

Aged Analysis Layout record, SAGLTRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’GLT’, Mandatory
R-GLT-CODE 004 005 X - Layout Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-GLT-LOOKUP-ID 065 003 X - Lookup Id
R-GLT-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-GLT-REPORT-NAME-1 086 030 X - Report Name Line 1 Mandatory
R-GLT-REPORT-NAME-2 116 030 X - Report Name Line 2
R-GLT-DEBTOR-ACCOUNTS 146 001 X - Debtor Account Type
R-GLT-CREDITOR-ACCOUNTS 147 001 X - Creditor Account Type
R-GLT-CLIENT-ACCOUNTS 148 001 X - Client Account Type
R-GLT-BALANCE-SHEET- 149 001 X - Balance Sheet Account Type

ACCOUNTS
R-GLT-PROFIT-LOSS-ACCOUNTS 150 001 X - P&L Account Type
R-GLT-MEMO-ACCOUNTS 151 001 X - Memo Account Type

R-GLT-EXCLUDE-ALLOCATED 152 001 X - Exclude Allocated
R-GLT-AGE-BY-DATE 153 001 X - Age by Due/Trans’n Date Mandatory
R-GLT-AGE-FOR-BACK 154 001 X - Age Forwards/Backwards Mandatory
R-GLT-REPORT-TRANSACTIONS 155 001 X - Report Transactions
R-GLT-DC-TOTALS 156 001 X - Totals by Debit/Credit
R-GLT-REPORT-OTHER 157 001 X - Report Other Amount
R-GLT-AGE-DAYS-1 158 003 N - Default Ageing Days 1

Aged Analysis Layout record, SAGLTRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-GLT-SELECTION-1 173 002 X - Selection Code 1
R-GLT-LEVEL-5 183 002 X - Level Code 5
R-GLT-BALANCE-SEQUENCE 193 001 X - Balance Sequence
R-GLT-PAGE-LEVEL 194 001 X - Page Level
R-GLT-INCLUDE-ROUGH 195 001 X - Include Rough
FILLER 196 331 X - -
R-GLT-GRP-MASK 527 005 X - Operator Group Mask
FILLER 532 001 X - -

FILLER 533 268 X - -
FILLER 801 224 X - -

Additional Header Labels record, SBHALRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘HAL’, Mandatory
FILLER 004 029 X - - -
FILLER 033 032 X - - -
R-HAL-LOOKUP-ID 065 003 X - Lookup ID
R-HAL-LOOKUP-CODE 068 010 X - Lookup Code
R-HAL-DATE-UPD 078 008 X - Date Last Updated
R-HAL-SOH-LABEL1 086 020 X - Sales Header Label 1

R-HAL-POH-LABEL1 326 020 X - Purchase Header Label 1

Additional Header Labels record, SBHALRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 526 459 X - -

System Labels record, SBIADRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘IAD’, Mandatory
R-IAD-DBASE-CODE 004 003 X - Database Code
FILLER 007 026 X - - -
FILLER 033 032 X - - -
R-IAD-LOOKUP-ID 065 003 X - Lookup ID
R-IAD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
R-IAD-SALES-ACCOUNT-NAME 086 020 X - Sales Account Report Name
R-IAD-PURCH-ACCOUNT-NAME 106 020 X - Purchase Account Report Name
R-IAD-ACCOUNT-NAME-1 126 020 X - Item Account Report Name 1
R-IAD-ACCOUNT-CODE-1 146 015 X - Ledger Interface Recognition Code 1

R-IAD-BSP-NAME-1 406 020 X - Base Selling Price Name 1

System Labels record, SBIADRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 486 315 X - -
FILLER 801 224 X - -

Debtor/Creditor Transfer Selection Record, SAINFRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘INF’, mandatory
R-INF-CODE 004 001 X Interface Code
FILLER 005 060 X -
R-INF-LOOKUP-ID 065 003 X - Lookup Id
R-INF-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-INF-LAYOUT 086 005 X Layout
R-INF-ACC-FROM 091 015 X Account From
R-INF-ACC-TO 106 015 X Account To
R-INF-PRIORITY-FROM 121 001 X Priority From
R-INF-PRIORITY-TO 122 001 X Priorty To
R-INF-CAT-FROM (1) 123 015 X Category From
R-INF-CAT-TO (1) 138 015 X Category To

R-INF-DEBT-FROM-Z 273 015 9 Debt From
R-INF-DEBT-TO-Z 288 015 9 Debt From
R-INF-DAYS-FROM 303 003 9 Days From
R-INF-DAYS-TO 306 003 9 Days To
R-INF-WITHHOLD 309 001 X Withold
R-INF-OLDEST-DEBT 310 001 X Oldest Debt

Debtor/Creditor Transfer Selection Record, SAINFRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-INF-INCLUDE-ROUGH 311 001 X Include Rough
R-INF-FILENAME 312 030 X Interface Filename
FILLER 342 783 X -

Invoice Prefix record, SOINPRC.CPY, (SQL miscellaneous table SSRFMSC)

INP-REC-TYPE 001 003 X - Reference Record Type Value ‘INP’, Mandatory
INP-CODE-1 004 015 X - Analysis Code 1
FILLER 064 001 X - - -
FILLER 065 013 X - - -
FILLER 078 008 X - - -
INP-PREFIX 086 004 X - Invoice Prefix
FILLER 090 711 X - -
FILLER 801 224 X - -

Debtor/Creditor Transfer Layout record, SAINTRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’INT’, Mandatory
R-INT-CODE 004 005 X - Transfer Layout Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-INT-LOOKUP-ID 065 003 X - Lookup Id
R-INT-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-INT-NAME 086 030 X - Layout Name Mandatory
R-INT-FORMAT 116 005 X - Transfer Format Mandatory
R-INT –ITEMS(1) 121 005 X - Item Name 1
R-INT-ITEMS(2) 126 005 X - Item Name 2


Debtor/Creditor Transfer Layout record, SAINTRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-INT-SELECTION-1 221 002 X - Selection Code 1
FILLER 231 302 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Item Extended Descriptions record, SBITDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ITD’, Mandatory
R-ITD-CODE 004 015 X - Item Code Mandatory
R-ITD-CUST-CODE 019 010 X - Customer Code
R-ITD-ANCAT 029 002 X - Analysis Category
R-ITD-ANCODE 031 015 X - Analysis Code
R-ITD-RECORD-NO 046 001 N - Record Number Mandatory
FILLER 047 018 X - - -
R-ITD-LOOKUP-ID 065 003 X - Lookup ID
FILLER 068 010 X - - -
FILLER 078 008 X - - -
R-ITD-DESCRIPTION-1 086 030 X - Description Line 1

R-ITD-ADDITIONAL-CODE 266 015 X - Additional Item Code
FILLER 281 520 X - -
FILLER 801 224 X - -

Item record, SBITMRC.CPY, SQL table name SSRFITM
TYPE
FILLER 001 003 X - - - Reference Record Type Value ’ITM’,

Mandatory
R-ITM-CODE 004 015 X - ITEM_CODE char(15) Item Code Mandatory
FILLER 019 014 X - - - -
FILLER 033 032 X - - - -
R-ITM-LOOKUP-ID 065 003 X - - - Lookup Id
R-ITM-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
R-ITM-DESCRIPTION 086 030 X - DESCRIPTN char(30) Item Description
R-ITM-UNIT-STOCK 116 005 X - UNIT_STOCK char (5) Unit of Stock
R-ITM-UNIT-SALE 121 005 X - UNIT_SALE char (5) Unit of Sale
R-ITM-BASE-SP(1) 126 018 N 5 BASE_PRICE1 numeric Base Selling Price 1

R-ITM-NEXT-SP(1) 198 018 N 5 NEXT_PRICE1 numeric Next Selling Price 1
R-ITM-NEXT-DATE(1) 270 008 N 0 NEXT_DATE1 char(8) Date Next Price Applies 1
R-ITM-UNIT-WEIGHT 302 018 N 5 UNIT_WGHT numeric Unit Weight
R-ITM-STD-COST 320 018 N 5 STD_COST numeric Standard Cost
R-ITM-LAT-COST 338 018 N 5 LAT_COST numeric Latest Cost
R-ITM-AVE-COST 356 019 S 5 AVE_COST numeric Average Cost signed

Item record, SBITMRC.CPY, SQL table name SSRFITM – (continued)
TYPE
R-ITM-WHOLE-UNITS 375 001 X - WHOLE_UNIT char (1) Whole Units
R-ITM-WHOLE-UNITS-SALE 376 001 X - WHOLE_UNIT_SALE char (1) Whole Units
R-ITM-ALLOC-METHOD 377 001 X - ALLOC_METH char (1) Allocation Method
R-ITM-PROCESS 378 001 X - ITEM_PROC char (1) Item Process
R-ITM-SUPPLIER-CONTROL 379 001 X - SUPP_CNTRL char (1) Supplier Control
R-ITM-CUSTOMER-CONTROL 380 001 X - CUST_CNTRL char (1) Customer Control
R-ITM-COMMENT 381 020 X - COMMENTS char(20) Comment
R-ITM-SALES-ACCOUNT 401 015 X - SALES_ACC char(15) Sales Account
R-ITM-PURCH-ACCOUNT 416 015 X - PURCH_ACC char(15) Purchase Account
R-ITM-STOCK-TAKE- 431 003 N 0 ST_FREQ char (3) Stock Take Frequency

FREQUENCY
R-ITM-ALT-CODE 434 015 X - ALT_ITEM_CODE char(15) Alternate Item Code
R-ITM-AN-0 449 015 X - ANAL_I0 char(15) Analysis Code 0

R-ITM-COMMODITY-CODE 599 015 X - COMM_CODE char(15) Commodity Code
R-ITM-ASSEMBLY-LEVEL 614 001 X - ASSEMBLY_LEVEL char (1) Assembly Level
R-ITM-PROCESS-COMPONENT 615 001 X - PROCESS_COMP char (1) Process Component
R-ITM-SOP-ITD-DESCR 616 001 N 0 SOP_EXT_DESC char (1) SOP description
R-ITM-POP-ITD-DESCR 617 001 N 0 POP_EXT_DESC char (1) POP description
R-ITM-GLI-ACCOUNT-1 618 015 X - GLI_ACCOUNT_1 char(15) Ledger Interface Account 1

Item record, SBITMRC.CPY, SQL table name SSRFITM – (continued)
TYPE
R-ITM-UPD-PURCH-PRICE 738 001 X - UPD_PURCH_PRICE char(1) Update Purchase Price
R-ITM-DEF-PURCH-PRICE 739 018 N 5 DEF_PURCH_PRICE numeric Default Purchase Price
R-ITM-SET-PURCH-PRICE 757 001 X - SET_PURCH_PRICE char(1) Set Purchase Price
R-ITM-PCK-BY-X-DTE 758 001 X - PICK_BY_X_DATE char(1) Pick By Expiration Date
R-ITM-QUANTITY 759 001 X - ITEM_QUANTITY char(1) Volume/Weight Flag
R-ITM-AUDIT-DATE 760 001 X - AUDIT_DATE char(1) Audit Date Flag
FILLER 761 264 X - - - -

Item Special Processes record, SBITPRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ITP’, Mandatory
R-ITP 004 001 X - Item Process
FILLER 005 060 X - - -
R-ITP-LOOKUP-ID 065 003 X - Lookup ID
R-ITP-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-ITP-DESCRIPTION 086 030 X - Description Mandatory
R-ITP-UPDATE-STOCK 116 001 X - Update Stock Balances
R-ITP-DC 117 001 X - Debit/Credit Indicator
R-ITP-SOP-LS 118 001 X - Line or Sub-total (sales)
R-ITP-SOP-VALUE 119 003 X - Subtotal Value
R-ITP-SOP-START 122 003 X - Process Line Calculation From
R-ITP-SOP-ENTRY-STATUS 125 001 X - Entry Status
R-ITP-POP-LS 126 001 X - Line Or Sub Total (purchase)
R-ITP-POP-VALUE 127 003 X - Subtotal Value
R-ITP-POP-START 130 003 X - Process Line Calculation From

R-ITP-POP-ENTRY-STATUS 133 001 X - Entry Status
FILLER 134 667 X - -
FILLER 801 224 X - -

Item Supplier record, SBITSRC.CPY,SQL table name SSRFITS
TYPE
FILLER 001 003 X - - - Reference Record Type Value ’ITS’,

Mandatory
R-ITS-CODE 004 015 X - ITEM_CODE char(15) Item Code Mandatory
R-ITS-RANKING 019 001 N 0 RANKING char (1) Ranking Code Mandatory
FILLER 020 013 X - - - -
FILLER 033 032 X - - - -
R-ITS-LOOKUP-ID 065 003 X - LOOKUP char(10) Lookup Id
R-ITS-SUPPLIER 068 010 X - SUPPLIER char(10) Supplier Code
R-ITS-DESCRIPTION 086 030 X - DESCRIPTN_1 char(30) Supplier Item Description
R-ITS-SUPP-ITEM-CODE 116 015 X - SUPP_ITEM_CODE char(15) Supplier Item Code
R-ITS-LEAD-TIME 131 004 N 0 LEAD_TIME char (4) Lead Time
R-ITS-PURCH-COST 135 018 N 5 PURCH_COST numeric Base Purchase Cost
R-ITS-UNIT-PURCH 153 005 X - UNIT_PURCH char (5) Unit of Purchase
R-ITS-MIN-PURCH-QTY 158 018 N 5 MIN_QTY numeric Minimum Order Quantity

R-ITS-WHOLE-P-UNITS 176 001 X - WHOLE_UNIT char (1) Whole Units
R-ITS-DESCRIPTION-1 177 030 X - DESCRIPTN_2 char(30) Description
FILLER 207 594 X - - - -
FILLER 801 224 X - - - -

Statistical Layout record, SBKLTRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’KLT’, mandatory
R-KLT-CODE 004 005 X - Layout Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-KLT-LOOKUP-ID 065 003 X - Lookup Id
R-KLT-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-KLT-LAYOUT-NAME 086 025 X - Layout Name Mandatory
R-KLT-ARRIVAL-DESPATCH 111 001 X - Arrivals or Despatches Mandatory
R- KLT-SOP-SELECTION 112 001 X - SOP Selection
R-KLT-SOP-SEL-CODE-1 113 002 X - SOP Selection Code 1
R-KLT-SOP-SEL-FROM-1 121 015 X - SOP Selection Code From 1

R-KLT-SOP-SEL-TO-1 181 015 X - SOP Selection Code To 1
R-KLT-POP-SELECTION 241 001 X - POP Selection
R-KLT-POP-SEL-CODE-1 242 002 X - POP Selection Code 1
R-KLT-POP-SEL-FROM-1 250 015 X - POP Selection Code From 1

Statistical Layout record, SBKLTRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-KLT-POP-SEL-TO-1 310 015 X - POP Selection Code To 1
R-KLT-FORMAT-CODE 370 005 X - Format Code Mandatory
FILLER 375 426 X - -
FILLER 801 224 X - -

Ledger/Register Definition record, SSLDGRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’LDG’, Mandatory
LDG-LEDGER-CODE 004 003 X - Database Code Mandatory
FILLER 007 058 X - -
LDG-LOOKUP-ID 065 003 X - Lookup Id
LDG-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
FILLER 086 030 X - -
LDG-CURRENT-AP 116 008 X - Current Period Mandatory
LDG-MAX-PERIODS 124 003 N 0 Maximum Periods in Year Mandatory
LDG-OPEN-PERIOD-FROM 127 008 X - Open Period From
LDG-OPEN-PERIOD-TO 135 008 X - Open Period To
LDG-OPEN-DATE-FROM 143 010 X - Open Date From
LDG-OPEN-DATE-TO 153 010 X - Open Date To
FILLER 163 005 X - -
LDG-OVER-EXPEND-CHECK 168 001 X - Over Expend Check
LDG-FIXED-EUR-RATE 169 018 N 9 Euro Rate

LDG-T-PAYMT-TERM-CAT 187 002 X - Payment Term T Code
LDG-A-PAYMT-TERM-CAT 189 002 X - Payment Term A Code
LDG-NO-ON-HARD 191 001 X - Transaction Sequence update on hard posting

only flag
FILLER 192 014 X -
LDG-CURRENCY-CONV 206 011 N 5 Consolidate Conversion Rate
LDG-CONV-CODE 217 005 X - Base Conversion Code
LDG-OTHER-AM-BAL 222 001 X - Other Amount Balancing
LDG-MINIMUM-PAYMENT-LEVEL 223 001 X - Minimum Payment Level
LDG-AC-SUB-CHARAS 224 001 N 0 A/c Subtotal Characters
LDG-REVAL-METHOD 225 001 X - Revaluation Method
FILLER 226 010 X - -

Ledger/Register Definition record, SSLDGRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

LDG-FORCE-JOURNAL-LISTING 236 001 X - Force Journal Listing
LDG-FORCE-JOURNAL-SOURCE 237 001 X - Force Journal Source
LDG-BANK-PAYMENTS 238 001 X - Automatic Bank Payments
LDG-PAY-OTHER-AM 239 001 X - Other Amount Payment
LDG-REPORT-CORRECTIONS 240 001 X - Report Corrections
LDG-SUPPRESS-CRED-SUMMARY 241 001 X - Suppress Creditor Summarise
LDG-SUPPRESS-DEBT-SUMMARY 242 001 X - Suppress Debtor Summarise
LDG-RATE-TOLERANCE 243 005 N 3 Conversion Rate Tolerance
LDG-DIRECT-DEBITS 248 001 X - Direct Debits
LDG-SPREAD-CODE 249 003 X - Spread Ratio Code
LDG-ARCHIVING 252 001 X - Ledger Archiving
LDG-LJUST-REFS-JI 253 001 X - Journal Import – Left Justify Flag
LDG-NEXT-ALLOC-REF 254 009 N 0 Next Allocation Reference
LDG-ROUGH-BOOK 263 001 X - Rough Book
LDG-TAX-CAT 264 002 X - Tax Category
LDG-TRANS-SEQ-CAT 266 002 X - Transaction Sequence Category

LDG-DAY-BOOK-SEQ-CAT 268 002 X - Day Book Sequence Category
LDG-BAL-BY-REF 270 001 X - Balance By Reference
LDG-TAX-ON-DISCOUNT 271 001 X - Tax On Discount
LDG-FORCE-JOURNAL-LIST- 272 005 X - Default Force Journal Listing Report Code

CODE
FILLER 277 003 X - -
LDG-SEQ-AUDIT-REGISTER 280 001 X - Sequential Audit Register
LDG-EXC-FV-FROM-DEP 281 001 X - Exclude Final Value from Depreciation
FILLER 282 004 X - Spare for SA expansion
FILLER 286 100 X - Used by SB Business Definition
LDG-SYSTM-SQN-GP 386 005 X - Sequence Code GP


LDG-SYSTM-SQN-GD 391 005 X - Sequence Code GD
LDG-SYSTM-SQN-TM 396 005 X - Sequence Code TM
LDG-SYSTM-SQN-VP 401 005 X - Sequence Code VP
LDG-SYSTM-SQN-LR 406 005 X - Sequence Code LR
LDG-SYSTM-SQN-TA 411 005 X - Sequence Code TA
LDG-SYSTM-SQN-DB 416 005 X - Sequence Code DB
LDG-SYSTM-SQN-CD 421 005 X - Sequence Code CD
LDG-SYSTM-SQN-AD 426 005 X - Sequence Code AD
FILLER 431 050 X - -
FILLER 481 320 X - -
LDG-TAX-CAT 264 002 X - Tax Category
LDG-TRANS-SEQ-CAT 266 002 X - Transaction Sequence Category
LDG-DAY-BOOK-SEQ-CAT 268 002 X - Day Book Sequence Category
LDG-BAL-BY-REF 270 001 X - Balance By Reference
LDG-TAX-ON-DISCOUNT 271 001 X - Tax On Discount

LDG-FORCE-JOURNAL-LIST- 272 005 X - Default Force Journal Listing Report Code

CODE
FILLER 277 003 X - -
LDG-SEQ-AUDIT-REGISTER 280 001 X - Sequential Audit Register
LDG-EXC-FV-FROM-DEP 281 001 X - Exclude Final Value from Depreciation
FILLER 282 004 X - Spare for SA expansion
FILLER 286 100 X - Used by SB Business Definition
LDG-SYSTM-SQN-GP 386 005 X - Sequence Code GP
LDG-SYSTM-SQN-GD 391 005 X - Sequence Code GD
LDG-SYSTM-SQN-TM 396 005 X - Sequence Code TM


LDG-SYSTM-SQN-VP 401 005 X - Sequence Code VP
LDG-SYSTM-SQN-LR 406 005 X - Sequence Code LR
LDG-SYSTM-SQN-TA 411 005 X - Sequence Code TA
LDG-SYSTM-SQN-DB 416 005 X - Sequence Code DB
LDG-SYSTM-SQN-CD 421 005 X - Sequence Code CD
LDG-SYSTM-SQN-AD 426 005 X - Sequence Code AD
FILLER 431 050 X - -
LDG-BALANCE-BY 481 002 X - Balance By
LDG-SORT-IMPORT-FILE 483 001 X - Sort Import File
LDG-BASE-AMT-BAL 484 001 X - Balance By Base Amount
LDG-AUTO-BASE-DB-ACC 485 015 X - Automatic Base Debtor Account
LDG-AUTO-BASE-CR-ACC 500 015 X - Automatic Base Creditor Account
LDG-AUTO-OTHER-DB-ACC 515 015 X - Automatic Other Debtor Account
LDG-AUTO-OTHER-CR-ACC 530 015 X - Automatic Other Creditor Account
LDG-BASE-AMT-TOL 545 016 N 3 Base Amount Tolerance
LDG-OTHER-AMT-TOL 561 016 N 3 Other Amount Tolerance

LDG-STD-DESC-CAT 577 002 X - Standard description analysis category
LDG-DISCOUNT-CAT 579 002 X - Discount Category
FILLER 581 053 X -
LDG-NEXT-AUTO-REF 634 009 N 0 Next Auto Reference
LDG-NEXT-MAN-REF 643 009 N 0 Next Manual Reference
LDG-LOCK-DEF 652 001 X - Lock Depreciation
FILLER 653 372 X - -

Item Balance record, SBLITRC.CPY, SQL table name SSRFLIT
TYPE
FILLER 001 003 X - - - Reference Record Type Value ’LIT’,

Mandatory
R-LIT-CODE 004 015 X - ITEM_CODE char(15) Item Code Mandatory
R-LIT-LOCATION 019 005 X - LOCATION char (5) Item Location
FILLER 024 009 X - - - -
FILLER 033 032 X - - - -
R-LIT-LOOKUP-ID 065 003 X - - - Lookup Id
R-LIT-LOOKUP-CODE 068 010 X - LOOKUP char(10) Lookup Code
FILLER 078 008 X - UPDATED char (8) Date last updated
R-LIT-PHYSICAL-BAL 086 019 S 5 PHYSICAL numeric Physical Stock Balance
R-LIT-ON-ORDER-BAL 105 019 S 5 ON_ORDER numeric On-order Stock Balance
R-LIT-ALLOCATED-BAL 124 019 S 5 ALLOCATED numeric Allocated Stock Balance
R-LIT-PICK-BAL 143 019 S 5 PICKED numeric Picked Stock Balance
R-LIT-UNAPPROVED-BAL 162 019 S 5 UNAPPROVED numeric Unapproved Stock Balance
R-LIT-MINIMUM-TYPE 181 001 X - MIN_TYPE char (1) Minimum Stock Level (Type)

R-LIT-MINIMUM-BAL 182 018 N 5 MINIMUM numeric Minimum Stock Level

(Qty/Prd)
R-LIT-MAXIMUM-TYPE 200 001 X - MAX_TYPE char (1) Maximum Stock Level

(Type)
R-LIT-MAXIMUM-BAL 201 018 N 5 MAXIMUM numeric Maximum Stock Level

(Qty/Prd)
R-LIT-PERIOD-USAGE 219 018 N 5 PUSAGE numeric Usage
R-LIT-BIN-NAME 237 015 X - BIN_NAME char(15) Bin Name
R-LIT-LAST-COMP-STOCKTAKE- 252 005 N 0 ST_LAST_NO int Last Complete Stock-Take

NO Number
R-LIT-LAST-COMP-STOCKTAKE- 257 008 N 0 ST_LAST_DT int Last Complete Stock-Take

DATE Date
R-LIT-CURRENT-STOCKTAKE-NO 265 005 N 0 ST_CURR_NO int Current Stock-Take Number

Item Balance record, SBLITRC.CPY, SQL table name SSRFLIT – (continued)
TYPE
R-LIT-CURRENT-STOCKTAKE- 270 008 N 0 ST_CURR_DT char (8) Current Stock-Take Date

DATE
FILLER 278 523 X - - - -
FILLER 801 224 X - - - -

Location Definition record, SBLOCRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’LOC’, mandatory
R-LOC-CODE 004 005 X - Location Code
FILLER 009 056 X - -
R-LOC-LOOKUP-ID 065 003 X - Lookup Id
R-LOC-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-LOC-DESC 086 030 X - Description
R-LOC-ADD 116 010 X - Address Code Not used at version 4.2
R-LOC-BALANCE-NUMBER 126 002 N - Balance Number Not used at version 4.2
R-LOC-SUPPRESS-STOCK- 128 001 X - Suppress Stock Taking

TAKING
FILLER 129 672 X - -
FILLER 801 224 X - -

Ledger Export Consolidation record, SALXCRC.CPY, (SQL miscellaneous table SSRFMSC)

LXC-KEY-TYPE 001 003 X - Reference Record Type Value ’LXC’, Mandatory
R-LXC-CODE 004 005 X - Export Code Mandatory
R-LXC-LINE 009 005 N - Export Line Mandatory
FILLER 014 019 X - -
FILLER 033 032 X - -
R-LXC-LOOKUP-ID 065 003 X - Lookup Id
FILLER 068 018 X - -
R-LXC-ACFROM 086 015 X - Account Code From
R-LXC-ACTO 101 015 X - Account Code To
R-LXC-OUTPUT 116 015 X - Output Account
R-LXC-SUPPRESS 131 001 X - Suppress Amount
R-LXC-CAT0 132 002 X - Analysis Category 0

R-LXC-ACODE0 152 015 X - Analysis Code 0

Ledger Export Consolidation record, SALXCRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-LXC-REVERSAL 302 001 X - Reversal Flag
FILLER 303 230 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Ledger Export Definition record, SALXDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’LXD’, Mandatory
R-LXD-CODE 004 005 X - Export Code Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-LXD-LOOKUP-ID 065 003 X - Lookup Id
FILLER 068 018 X - -
R-LXD-NAME 086 025 X - Export Name Mandatory
R-LXD-SUMMARISE 111 001 X - Summarise
R-LXD-CONTROL 112 001 X - Journal Control
R-LXD-PERIOD 113 004 X - Transfer Period
R-LXD-TYPE 117 005 X - Journal Type
R-LXD-LAYOUT 122 005 X - Transfer Layout
R-LXD-BASE 127 001 X - Base Amount
R-LXD-OTHER 128 001 X - Other Amount
R-LXD-REVERSAL 129 001 X - Amount Reversal
R-LXD-CAT1 130 002 X - Selection Category 1

R-LXD-SUB1 140 001 X - Selection Sub-Category 1
R-LXD-SELECTION-PRESENT 145 001 X - Selection Record Present
R-LXD-INCLUDE-ROUGH 146 001 X - Include Rough
FILLER 147 386 X - -

Ledger Export Definition record, SALXDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 533 268 X - -
FILLER 801 224 X - -

Export Definition Selection Record, SALXSRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘LXS’, mandatory
R-LXS-CODE 004 005 X Export Code
R-LXS-AB-MARKER 009 001 x Whether A=Actuals or B thru K comparative

Budget file
FILLER 010 055 X -
R-INF-LOOKUP-ID 065 003 X - Lookup Id
R-INF-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-LXS-JOURNAL-FROM 086 007 9 From Journal Number
R-LXS-JOURNAL-TO 093 007 9 To Journal Number
R-LXS-PERIOD-FROM 100 008 x From Period
R-LXS-PERIOD-TO 108 008 To Period
R-LXS-SEL-FROM1 116 015 Selection Code From
R-LXS-SEL-TO1 131 015 Selection Code To

R-LXS-PERIOD 266 008 Transfer Period
R-LXS-FILENAME 274 030 Transfer File Name
FILLER 304 721

Movement Analysis Layout record, SMMANRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’MAN’, Mandatory
R-MAN-REPORT-CODE 004 005 X - Layout Code Mandatory
FILLER 009 056 X - -
R-MAN-LOOKUP-ID 065 003 X - Lookup Id
R-MAN-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-MAN-REPORT-NAME-1 086 030 X - Report Name Line 1 Mandatory
R-MAN-REPORT-NAME-2 116 030 X - Report Name Line 2
R-MAN-L3-CODE 146 002 X - Level Category 3 Mandatory
R-MAN-L2-CODE 148 002 X - Level Category 2
R-MAN-L1-CODE 150 002 X - Level Category 1
R-MAN-C1-CODE 152 005 X - Column A Codes
R-MAN-C2-CODE 157 005 X - Column B Codes
R-MAN-C3-CODE 162 005 X - Column C Codes
R-MAN-C4-CODE 167 005 X - Column D Codes
R-MAN-C5-CODE 172 005 X - Column E Codes

R-MAN-C6-CODE 177 005 X - Column F Codes
R-MAN-C7-CODE 182 005 X - Column G Codes
R-MAN-C8-CODE 187 005 X - Column H Codes
R-MAN-PAGE-LEVEL 192 001 X - Page Level
R-MAN-RE-EVAL-MVMTS 193 001 X - Re-evaluate Movements
R-MAN-REPORT-TRANS 194 001 X - Report Transactions
R-MAN-AMOUNT-FORMAT 195 001 X - Amount Format
R-MAN-TRANSFER-FORMAT 196 005 X - Transfer Format
R-MAN-ZERO-SUPPRESS 201 001 X - Line Zero Suppress
R-MAN-S1-CODE 202 002 X - Selection Category 1

Movement Analysis Layout record, SMMANRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-MAN-S1-MASK-ID 212 001 X - Selection SubCategory 1
R-MAN-S3- MASK-ID 214 001 X - Selection SubCategory 3
R-MAN-L3-MASK-ID 217 001 X - Level SubCategory 3
R-MAN-WIDE-COLUMN 220 001 X - Column Width Control
R-MAN-PRINTER-CODE 221 005 X - Printer Definition
FILLER 226 575 X - -
FILLER 801 224 X - -

New Cost Definition record, SMMCDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘MCD’, Mandatory
MCD-AP 004 007 N 0 Account Period Mandatory
MCD-ITEM-CODE 011 015 X - Item Code Mandatory
FILLER 026 039 X - - -
MCD-LOOKUP-ID 065 003 X - Lookup ID
MCD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
MCD-CURRENT-COST 086 018 N 5 Current Cost
MCD-NEW-COST 114 018 N 5 New Cost
FILLER 132 903 X - -

Item Validation record, SMMIVRC.CPY, (SQL miscellaneous table SSRFMSC)

R-MIV-CODE 001 003 X - Reference Record Type Value ‘MIV’, Mandatory
R-MIV-ITEM-CODE 004 015 X - Item Code Mandatory
R-MIV-REC-REF 019 015 X - Receipt Reference Mandatory
FILLER 034 031 X - - -
FILLER 065 003 X - - -
FILLER 068 010 X - - -
FILLER 078 008 X - - -
R-MIV-AUDIT-DATE 086 008 X - Audit Date
R-MIV-PROHIBIT-POSTING 094 001 X - Prohibit Posting
R-MIV-REASON-FOR-CHANGE 095 030 X - Reason For Change
FILLER 125 676 X - - -

Location Accounts record, SMMLCRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘MLC’, Mandatory
MLC-LOCATION 004 005 X - Location Code Mandatory
FILLER 009 056 X - - -
MLC-LOOKUP-ID 065 003 X - Lookup ID
MLC-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 947 X - - -

Movement Accounts record, SMMMCRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘MMC’, Mandatory
MMC-MVT-CODE 004 005 X - Movement Code Mandatory
FILLER 009 056 X - - -
MMC-LOOKUP-ID 065 003 X - Lookup ID
MMC-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 947 X - -

Revaluation Analysis record, SMMRARC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘MRA’, Mandatory
MRA-PROFILE 004 005 X - Profile Code Mandatory
MRA-ACCOUNT-TYPE 009 001 X - Account Type Mandatory
FILLER 010 055 X - - -
MRA-LOOKUP-ID 065 003 X - Lookup ID
MRA-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
MRA-CAT(1) 086 002 X - Analysis Category 1
MRA-ANAL-CODE(1) 088 015 X - Analysis Code 1

FILLER 256 769 X - -

Revaluation Profile record, SMMRPRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘MRP’, Mandatory
MRA-PROFILE 004 005 X - Profile Code Mandatory
FILLER 009 056 X - - -
MRP-LOOKUP-ID 065 003 X - Lookup ID
MRP-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
MRP-DESC 086 030 X - Description Mandatory
MRP-LEVEL-1 116 002 X - Level Code 1
MRP-OTHER-CURR 122 005 X - Other Currency Code
MRP-INV-REF 127 015 X - Inventory Reference
MRP-GAIN-LOSS-ACC 142 015 X - Gain/Loss Account Code Mandatory
MRP-GAIN-LOSS-REF 157 015 X - Gain/Loss Reference
MRP-ADD1-ACC 172 015 X - Additional Account Code 1
MRP-ADD1-REF 197 015 X - Additional Reference 1

MRP-ADD2-ACC 212 015 X - Additional Account Code 2
MRP-ADD2-REF 227 015 X - Additional Reference 2
MRP-INV-TRANS-DESC 242 025 X - Inventory Transaction Description
MRP-GAIN-LOSS-TRANS-DESC 267 025 X - Gains/Loss Transaction Description
MRP-ADD1-TRANS-DESC 292 025 X - Additional Transaction Description 1
MRP-ADD2-TRANS-DESC 317 025 X - Additional Transaction Description 2
MRP-JNL-TYPE 342 005 X - Journal Type
MRP-JNL2-TYPE 347 005 X - Journal Type 2
MRP-OFFSET-DESC 352 025 X - Offset Description
MRP-OFFSET-REF 377 015 X - Offset Reference
MPR-OTHER 392 001 X - Other

Revaluation Profile record, SMMRPRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

MRP-POSTING-PERIOD 393 001 X - Posting Period Flag
FILLER 394 631 X - -

Stock Take Definition record, SMMSDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’MSD’, Mandatory
R-MSD-STOCK-TAKE-CODE 004 005 X - Stock Take Code Mandatory
FILLER 009 056 X - -
R-MSD-LOOKUP-ID 065 003 X - Lookup Id
R-MSD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-MSD-DESCRIPTION 086 030 X - Description Mandatory
R-MSD-STOCK-TAKE-METHOD 116 001 X - Stock Take Method Mandatory
R-MSD-INCLUDE-ZERO- 117 001 X - Include Zero Balances

BALANCES
R-MSD-DISPLAY-ORIGINAL-QTY 118 001 X - Display Original Quantity
R-MSD-PRINT-ORIGINAL-QTY 119 001 X - Print Original Quantity
R-MSD-CHECK-ALL-LOCATIONS 120 001 X - Check All Locations
R-MSD-POSITIVE-MOVEMENT- 121 005 X - +ve Movement Definition Mandatory

DEF
R-MSD-NEGATIVE-MOVEMENT- 126 005 X - -ve Movement Definition Mandatory

DEF

R-MSD-ITEM-CODE-FROM 131 015 X - Item Code From
R-MSD-ITEM-CODE-TO 146 015 X - Item Code To
R-MSD-LOCATION-CODE-FROM 161 005 X - Location Code From
R-MSD-LOCATION-CODE- TO 166 005 X - Location Code To
R-MSD-RECEIPT-REF-FROM 171 015 X - Receipt Reference From
R-MSD-RECEIPT-REF-TO 186 015 X - Receipt Reference To
R-MSD-ANALYSIS-CATEGORY 201 002 X - Analysis Category
R-MSD-ANALYSIS-CODE-FROM 203 015 X - Analysis Code From
R-MSD-ANALYSIS-CODE-TO 218 015 X - Analysis Code To
R-MSD-L4-CODE 233 002 X - Stock Take Sequence Level 4 Mandatory
R-MSD-L3-CODE 235 002 X - Stock Take Sequence Level 3 Mandatory
R-MSD-L2-CODE 237 002 X - Stock Take Sequence Level 2

Stock Take Definition record, SMMSDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-MSD-L1-CODE 239 002 X - Stock Take Sequence Level 1
FILLER 241 560 X - -
FILLER 801 224 X - -

Movement Definition record, SMMVDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’MVD’, Mandatory
R-MVD-TYPE 004 005 X - Movement Type Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-MVD-LOOKUP-ID 065 003 X - Lookup Id
R-MVD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-MVD-MOVEMENT-DESCR 086 030 X - Description
R-MVD-MOVE-CODE 116 001 X - Receipt/Issue/Transfer Mandatory
R-MVD-PRINT-DOC 117 001 X - Print Document
R-MVD-DOC-FORMAT 118 005 X - Document Format
R-MVD-GLI-CODE 123 005 X - G/L Interface Code
R-MVD-PHYSICAL-BAL 128 001 X - Physical Balance
R-MVD-ON-ORD-BAL 129 001 X - On Order Balance
R-MVD-RECPT-REF 130 001 X - Receipt Reference
R-MVD-REF-DESCR 131 010 X - Reference Description

R-MVD-ACCOUNT-PER-LINE 141 001 X - Account Codes per Line
R-MVD-ASSET-PER-LINE 142 001 X - Asset Codes per Line
R-MVD-ANAL-CAT-0 143 002 X - Analysis Category M0

Movement Definition record, SMMVDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-MVD-MANUAL-ALLOC 163 001 X - Manual Allocation
R-MVD-AUDIT-DATE 164 001 X - Audit Date Accept
R-MVD-REPORT-COST 165 003 X - Report Cost
R-MVD-COST-INPUT-1 168 001 X - Cost Input 1
R-MVD-COST-DESC-1 171 015 X - Cost Input Description 1
R-MVD-EUR-TOL-OV 216 001 X - Euro Tolerance Override
FILLER 217 584 X - -
FILLER 801 224 X - -

Movement Presets record, SMMVPRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’MVP’, Mandatory
R-MVP-TYPE 004 005 X - Movement Type Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-MVP-LOOKUP-ID 065 003 X - Lookup Id
R-MVP-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-MVP-ITEM-CODE 086 015 X - Item Code
R-MVP-RECPT-REF 101 015 X - Receipt Reference
R-MVP-BALANCE-CODE 116 005 X - Location
R-MVP-TRANSFER-LOC 121 005 X - Transfer To
R-MVP-QUANTITY 126 018 N 5 Quantity
R-MVP-COST-1 144 018 N 5 Cost 1
R-MVP-VALUE-1 198 018 N 5 Value 1

R-MVP-RATE-1 252 018 N 9 Rate 1
R-MVP-RATE-2 270 018 N 9 Rate 2
R-MVP-AUDIT-DATE 288 008 N 0 Audit Date
R-MVP-ACCOUNT-CODE 296 015 X - Account Code
R-MVP-ASSET-CODE 311 010 X - Asset Code
R-MVP-SUB-CODE 321 005 X - SubCode
R-MVP-ANAL-CODE-0 326 015 X - Analysis Code 0

Movement Presets record, SMMVPRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-MVP-TRAN-CODE-0 476 015 X - Transfer To Code 0

FILLER 626 175 X - -
FILLER 801 224 X - -

Movement Values Definition record, SMMVVRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’MVV’, Mandatory
R-MVV-DBASE-CODE 004 003 X - Database Code Mandatory
FILLER 007 058 X - -
R-MVV-LOOKUP-ID 065 003 X - Lookup Id
R-MVV-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-MVV-REPORT-NAME-1 086 015 X - Report Name 1
R-MVV-VALUE-1 101 003 X - Value 1
FILLER 140 661 X - -
FILLER 801 224 X - -

Authorisation Groups record, SOOAGRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘OAG’, Mandatory
ZAG-OPERATOR-GROUP 004 005 X - Operator Group
FILLER 009 056 X - - -
ZAG-LOOKUP-ID 065 003 X - Lookup ID
ZAG-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
ZAG-CL 086 001 X - Credit Limit Mandatory
ZAG-OA 087 001 X - Overdue Amounts Mandatory
ZAG-LS 088 001 X - Legal Status Mandatory
ZAG-MO 089 001 X - Minimum Order Mandatory
ZAG-RELEASE 090 001 X - Release Mandatory
FILLER 091 934 X - -

Sales Analysis Layout record, SOOANRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’OAN’, Mandatory
R-OAN-REPORT-CODE 004 005 X - Layout Code Mandatory
FILLER 009 056 X - -
R-OAN-LOOKUP-ID 065 003 X - Lookup Id
FILLER 068 018 X - -
R-OAN-REPORT-NAME-1 086 030 X - Report Name Line 1 Mandatory
R-OAN-REPORT-NAME-2 116 030 X - Report Name Line 2
R-OAN-L3-CODE 146 002 X - Level Code 3 Mandatory
R-OAN-L2-CODE 148 002 X - Level Code 2
R-OAN-L1-CODE 150 002 X - Level Code 1
R-OAN-C1-CODE 152 005 X - Column A Codes
R-OAN-C2-CODE 157 005 X - Column B Codes
R-OAN-C3-CODE 162 005 X - Column C Codes
R-OAN-C4-CODE 167 005 X - Column D Codes
R-OAN-C5-CODE 172 005 X - Column E Codes
R-OAN-C6-CODE 177 005 X - Column F Codes

R-OAN-C7-CODE 182 005 X - Column G Codes
R-OAN-C8-CODE 187 005 X - Column H Codes
R-OAN-ANALYSIS-TYPE 192 001 X - Orders/Invoices/All Mandatory
R-OAN-PAGE-LEVEL 193 001 X - Page Level
R-OAN-REPORT-TRANS 194 001 X - Report Transactions
R-OAN-AMOUNT-FORMAT 195 001 X - Amount Format
R-OAN-TRANSFER-FORMAT 196 005 X - Transfer Format
R-OAN-ZERO-SUPPRESS 201 001 X - Line Zero Suppress
R-OAN-S1-CODE 202 002 X - Selection Category 1

Sales Analysis Layout record, SOOANRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-OAN-S1-MASK-ID 212 001 X - Selection SubCategory
R-OAN-S2-MASK-ID 213 001 X - Selection SubCategory 2
R-OAN-L3-MASK-ID 217 001 X - Level SubCategory 3
R-OAN-WIDE-COLUMN 220 001 X - Wide Column
R-OAN-PRINTER-CODE 221 005 X - Printer Code
FILLER 226 307 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Release Authorisation Parameters record, SOOAURC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 085 X -
ZAP-OVERDUE-INTOLERANCE 086 018 N 5 Overdue Tolerance
ZAP-MINIMUM-ORDER-VALUE 104 018 N 5 Minimum Order Value
ZAP-LEGAL-STATUS-CAT 122 002 X - Legal Status Category
ZAP-STATUS-CODE(1) 124 015 X - Legal Status Code 1
ZAP-OVERDUE-CHECK 169 001 X - Overdue Check Mandatory
ZAP-CREDIT-LIMIT-CHECK 170 001 X - Credit Limit Check Mandatory
ZAP-LEGAL-STATUS-CHECK 171 001 X - Legal Status Check Mandatory
ZAP-MINIMUM-ORDER-CHECK 172 001 X - Minimum Order Check Mandatory
ZAP-RELEASE-CHECK 173 001 X - Release Check Mandatory
ZAP-ALLOCATION-VALUE(1) 174 001 X - Allocation Value 1

FILLER 189 836 X -
Standard Density Maintenance record, SOODMRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘ODM’, Mandatory
R-ODM-CODE 004 015 X - Item Code Mandatory
R-ODM-LOCATION 019 005 X - Location
R-ODM-START-DATE 024 008 N 0 Start Date

FILLER 032 033 X - - -
FILLER 065 021 X - - -
R-ODM-PROD-DENSITY 086 006 N 2 Product Density
R-ODM-TEMPERATURE 092 006 N 3 Temperature
R-ODM-HCF 098 001 N 0 Hydro Correction Flag Mandatory
R-ODM-STD-DENSITY 099 006 N 2 Standard Density
R-ODM-TEMP-NEG 105 001 X - Plus/Minus Flag
FILLER 106 919 X - - -

Free Goods Setup record, SOOFGRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘OFG’, Mandatory
FILLER 004 061 X - - -
ZFG-LOOKUP-ID 065 003 X - Lookup ID
ZFG-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
ZFG-PRICE-NO 086 001 X - Default Price Number Mandatory
ZFG-NEW-ORDER 087 001 X - Generate New Order Mandatory
ZFG-NEW-TRANS-CODE 088 005 X - New Order Transaction Type
ZFG-LOCATION 093 005 X - Location
ZFG-M0 098 015 X - Analysis Code 1

FILLER 248 777 X -

Free Goods Rules record, SOOFRRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘OFR’, Mandatory
ZFR-ITEM-CODE 004 015 X - Item Code
ZFR-TRANS-CODE 019 005 X - Sales Order Type
ZFR-PRICE-BOOK 024 005 X - Price Book Mandatory
FILLER 029 036 X - - -
ZFR-LOOKUP-ID 065 003 X - Lookup ID
ZFR-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
FILLER 086 005 X - - -
ZFR-PRICE-NO 091 001 X - Price Number Mandatory
ZFR-AWARDED-ITEM 092 015 X - Awarded Item Mandatory
ZFR-LOCATION 107 015 X - Location
ZFR-COMMENTS-1 122 025 X - Comments Line 1
ZFR-START-DATE 187 008 X - Start Date

ZFR-END-DATE 195 008 X - End Date
ZFR-DISABLED 203 001 X - Disabled Mandatory
ZFR-NEW-TRANS-CODE 204 005 X - New Transaction Code
ZFR-ORIGINAL-ANALYSIS 209 001 X - Original Analysis Code Mandatory
ZFR-ANALYSIS-CODE(1) 210 015 X - Analysis Code 1

Free Goods Rules record, SOOFRRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 360 665 X -

Invoice Modification record, SOOIMRC.CPY, (SQL miscellaneous table SSRFMSC)

OIM-RECORD-ID 001 003 X - Reference Record Type Value ‘OIM’, Mandatory
OIM-OP-GROUP 004 005 X - Operator Group
FILLER 009 056 X - - -
FILLER 065 013 X - - -
FILLER 078 008 X - - -
FILLER 086 001 X - - -
OIM-DELV-ADDR 087 001 X - Delivery Address Flag
OIM-CUST-REF 088 001 X - Customer Reference Flag
OIM-DELV-REF 089 001 X - Delivery Reference Flag
OIM-COMMENT 090 001 X - Comments Flag
OIM-VOID-FLAG 091 001 X - Void Flag
OIM-ADDL-FIELD1 092 001 X - Additional Field 1 Flag

FILLER 104 697 X - -
FILLER 801 224 X - -

Minimum Order Tolerance record, SOOOTRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘OOT’, Mandatory
ZOT-CUSTOMER-CODE 004 010 X - Address Code Mandatory
ZOT-ITEM-CODE 014 015 X - Item Code
FILLER 029 036 X - - -
ZOT-LOOKUP-ID 065 003 X - Lookup ID
ZOT-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
ZOT-OVERDUE-TOLERANCE 086 018 N 5 Overdue Tolerance
ZOT-MINIMUM-ORDER-VALUE 104 018 N 5 Minimum Order Value
FILLER 122 903 X -

Sales Order Header Presets record, SOOPHRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’OPH’, Mandatory
R-OPH-CODE 004 005 X - Sales Order Type Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-OPH-LOOKUP-ID 065 003 X - Lookup Id
R-OPH-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-OPH-INV-ADD 086 010 X - Customer Invoice Address
R-OPH-DEL-ADD 096 010 X - Customer Delivery Address
R-OPH-TRANS-DATE 106 010 X - Transaction Date
R-OPH-CUST-REF 116 025 X - Customer Reference
R-OPH-DEL-REF 141 015 X - Delivery Reference
R-OPH-COMMENTS 156 025 X - Comments
R-OPH-ANAL-CAT-0 181 002 X - Analysis Category 0

R-OPH-ANAL-CODE-0 201 015 X - Analysis Code 0

Sales Order Header Presets record, SOOPHRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 351 450 X - -
FILLER 801 224 X - -

Sales Order Details Presets record, SOOPIRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’OPI’, Mandatory
R-OPI-CODE 004 005 X - Sales Order Type Mandatory
R-OPI-LINE 009 005 X - Line Number Mandatory
FILLER 014 019 X - -
FILLER 033 032 X - -
R-OPI-LOOKUP-ID 065 003 X - Lookup Id
R-OPI-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-OPI-ITEM-CODE 086 015 X - Item Code
R-OPI-DESCRIPTION 101 030 X - Item Decsription
R-OPI-LOCATION 131 005 X - Location Code
R-OPI-DUE-DATE 136 010 X - Due Date
R-OPI-ACCOUNT-CODE 146 015 X - Account Code
R-OPI-CALC-CODE-1 161 003 X - Calculation Code 1

R-OPI-CALC-VALUE-1 170 018 N 5 Calculation Value 1
FILLER 224 577 X - -
FILLER 801 224 X - -

Returns/Exchanges record, SOORXRC.CPY, (SQL miscellaneous table SSRFMSC)

R-ORX-REC-TYPE 001 003 X - Reference Record Type Value ‘ORX’, Mandatory
FILLER 004 061 X - - -
R-ORX-LOOKUP-ID 065 003 X - Lookup ID
FILLER 068 010 X - - -
FILLER 078 008 X - - -
R-ORX-CREDIT-NOTE 086 005 X - Default Credit Note Mandatory
R-ORX-RETURN-LOCATION 091 005 X - Return Location Mandatory
FILLER 096 929 X -

Credit/Debit Notes record, SOOSNRC.CPY, (SQL miscellaneous table SSRFMSC)

OSN-REC-TYPE 001 003 X - Reference Record Type Value ‘OSN’, Mandatory
OSN-SALES-ORDER-TYPE 004 005 X - Sales Order Type Mandatory
FILLER 009 056 X - - -
OSN-LOOKUP-ID 065 003 X - Lookup ID
OSN-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
FILLER 086 939 X -

Sales Order Definition record, SOOTDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’OTD’, Mandatory
R-OTD-CODE 004 005 X - Transaction Type Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-OTD-LOOKUP-ID 065 003 X - Lookup Id
R-OTD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-OTD-DESCRIPTION 086 030 X - Description Mandatory
R-OTD-CD 116 001 X - Credit/Debit Mandatory
R-OTD-MANUAL-REF 117 001 X - Manual Order Numbers
R-OTD-UPDATE-STOCK 118 001 X - Update Stock
R-OTD-DUE-DATES 119 001 X - Enter Due Date
R-OTD-ACKNOWLEDGE 120 001 X - Acknowledgements
R-OTD-PICK-LIST 121 001 X - Picking Documents
R-OTD-DESPATCH 122 001 X - Despatch Documents
R-OTD-DIRECT-INV 123 001 X - Direct Print Invoice

R-OTD-OPTION-8 124 001 X - Not used at version 4.2
FILLER 125 005 X - -
R-OTD-DOC-PREF 130 004 X - Document Ref Prefix
R-OTD-GL-INTERFACE 134 005 X - Interface Code-Invoice
R-OTD-CALC-CODE-1 139 003 X - Calculation Code 1

Sales Order Definition record, SOOTDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-OTD-CALC-CODE-16 184 003 X - Calculation Code16
R-OTD-LINE-TOTAL-1 199 003 X - Displayed Value 1
R-OTD-GSP 208 003 X - Credit Balance Value

R-OTD-AMEND-CALC-1 211 001 X - Calc Code Override 1


R-OTD-INVOICE-FORMAT 231 005 X - Invoice Document Format
R-OTD-ACKNOWL-FORMAT 236 005 X - Acknowledgement Doc’nt Format
R-OTD-PICKING-FORMAT 241 005 X - Picking Document Format
R-OTD-DESPATCH-FORMAT 246 005 X - Despatch Document Format
R-OTD-STOCK-INTERFACE 251 005 X - Interface Code-Stock
R-OTD-LINE-ANAL(0) 256 002 X - Analysis by Line 0

R-OTD-PAYMENT-DUE-DATE 276 001 X - Enter Payment Date
R-OTD-ACCOUNT-CODES-PER- 277 001 X - Account Codes per Line

LINE
R-OTD-QUOTATION 278 001 X - Quotation


R-OTD-QUOTATION-FORMAT 279 005 X - Quotation Format
R-OTD-QUOTE-EXPIRY-DATE 284 003 N - Quotation Expiry Date
R-OTD-SALES-QTY 287 003 X - Sales Quantity
R-OTD-PRICING-BASE-DATE 290 001 X - Pricing Base Date
R-OTD-SALES-UNIT 291 003 X - Sales Unit
R-OTD-STOCK-QTY 294 003 X - Stock Quantity
R-OTD-BRT-HIER-1 297 005 X - Hierarchy LA Tax Requirements
R-OTD-BRT-CALC-1 322 003 X - Hierarchy Calc Code 1

R-OTD-SALES-QTY-2 337 003 X - Sales Quantity 2
R-OTD-RELEASE-HEADER 340 001 X - Release On Header
R-OTD-RR-AD 341 001 X - Receipt Reference Audit Date Flag
R-OTD-SUP-ADD-HDR-LBLS 342 001 X - Suppress Additional Header Labels
R-OTD-BASE-SALES-PRICE 343 001 X - Basic Sales Price Calculation Code Position
FILLER 344 457 X - -
FILLER 801 224 X - -

Tracking Code Maintenance record, SOOTMRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘OTM’, Mandatory
OTM-ITEM-CODE 004 015 X - Item Code Mandatory
OTM-DEST-CODE 019 015 X - Destination Analysis Code Mandatory
OTM-ORIGIN-CODE 034 015 X - Origin Analysis Code
FILLER 049 037 X - - -
OTM-ANALYSIS-CODE 086 015 X - Tracking Analysis Code Mandatory
OTM-EXPIRATION 101 008 N 0 Expiration Date Mandatory
OTM-IN-PROCESS 109 001 X - In Process Flag
OTM-FIELD-1 110 025 X - Field 1
OTM-FIELD-3 160 008 N 0 Field 3
OTM-FIELD-4 168 008 N 0 Field 4
FILLER 179 846 X -

Tracking Code Parameters record, SOOTPRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 085 X - Reference Record Type Value ‘OTP’, Mandatory
OTP-DEST-CAT 086 002 X - Destination Analysis Category Mandatory
OTP-ORIGIN-CAT 088 002 X - Origin Analysis Category
OTP-SANITARY-CAT 090 002 X - Tracking Analysis Category Mandatory
FILLER 092 933 X -

Tracking Code Excluded Combinations record, SOOXCRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘OXC’, Mandatory
OXC-ITEM-CODE 004 015 X - Item Code
OXC-DEST-CODE 019 015 X - Destination Analysis Code Mandatory
OXC-ORIGIN-CODE 034 015 X - Origin Analysis Code
FILLER 049 976 X -

Period Cleardown Consolidation Record, Sun Account, SAPCARC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PCA’, mandatory
FILLER 004 061 X -
R-PCA-LOOKUP-ID 065 003 X - Lookup Id
R-PCA-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-PCA-CONSOL-T0-YES 086 001 X T0
R-PCA-CONSOL-T0-FROM 087 015 X Consolidate from T0
R-PCA-CONSOL-T0-TO 102 015 X Consolidate to T0


Period Cleardown Consolidation Record, Sun Account, SAPCARC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 386 639 X

Period Cleardown Consolidation Record, IC and SOP, SBPCBRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PCB’, mandatory
R-PCB-TYPE 004 001 Cleardown Invoices/Movements/All
FILLER 005 060 X -
R-PCB-LOOKUP-ID 065 003 X - Lookup Id
R-PCB-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-PCB-CONSOL-ITEM-YES 086 001 X Items to be consolidated
R-PCB-CONSOL-ITEM-FROM 087 015 X Range of Items from
R-PCB-CONSOL-ITEM-TO 102 015 X Range of Items to
R-PCB-CONSOL-CUST-YES 117 001 X Customers to be consolidated
R-PCB-CONSOL-CUST-FROM 118 010 X Range of Customers from
R-PCB-CONSOL-CUST-TO 128 010 X Range of Customers to
R-PCB-CONSOL-PERIOD-YES 138 001 X Consolidate Periods
R-PCB-CONSOL-PERIOD-FROM- 139 004 9 Period from Year

CCYY
R-PCB-CONSOL-PERIOD-FROM- 143 003 9 Period from Period Number

PPP

R-PCB-CONSOL-PERIOD-TO- 146 004 9 Period to Year

CCYY
R-PCB-CONSOL-PERIOD-TO-PPP 150 003 9 Period to Period Number
R-PCB-CONSOL-M0-YES 153 001 X Consolidate M Code Yes/No

Period Cleardown Consolidation Record, IC and SOP, SBPCBRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-PCB-CONSOL-M0-FROM 163 015 X Consolidate M Code From
R-PCB-CONSOL-M0-TO 313 015 X Consolidate M Code To


Period Cleardown Consolidation Record, IC and POP, SBPCBRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PCP’, mandatory
FILLER 004 061 X -
R-PCP-LOOKUP-ID 065 003 X - Lookup Id
R-PCP-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-PCP-CONSOL-ITEM-YES 086 001 X Items to be consolidated
R-PCP-CONSOL-ITEM-FROM 087 015 X Range of Items from
R-PCP-CONSOL-ITEM-TO 102 015 X Range of Items to
R-PCP-CONSOL-CUST-YES 117 001 X Customers to be consolidated
R-PCP-CONSOL-CUST-FROM 118 010 X Range of Customers from
R-PCP-CONSOL-CUST-TO 128 010 X Range of Customers to
R-PCP-CONSOL-M0-YES 138 001 X Consolidate M Code Yes/No

R-PCP-CONSOL-M0-FROM 148 015 X Consolidate M Code From

Period Cleardown Consolidation Record, IC and POP, SBPCBRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-PCP-CONSOL-M0-TO 298 015 X Consolidate M Code To
R-PCP-CONSOL-PERIOD-YES 448 001 X Consolidate Periods

R-PCP-CONSOL-PERIOD-FROM- 449 004 9 Period from Year

CCYY
R-PCP-CONSOL-PERIOD-FROM- 453 003 9 Period from Period Number

PPP
R-PCP-CONSOL-PERIOD-TO- 456 004 9 Period to Year

CCYY
R-PCP-CONSOL-PERIOD-TO-PPP 460 003 9 Period to Period Number

Charge Index record, SPPCIRC.CPY, (SQL miscellaneous table SSRFMSC)

R-PCI-REC-TYPE 001 003 X - Reference Record Type Value ‘PCI’, Mandatory
R-PCI-INDEX-CODE 004 005 X - Index Code Mandatory
R-PCI-CATEGORY 009 002 X - Index Category Mandatory
R-PCI-CODE 011 015 X - Index Code From
FILLER 026 039 X - -
R-PCI-LOOKUP-ID 065 003 X - Lookup ID
R-PCI-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-PCI-DESCRIPTION 086 030 X - Description Mandatory
R-PCI-FACTOR 116 010 N 5 Weighing Factor
FILLER 126 674 X - -
FILLER 800 225 X - - -

Purchase Format Definition record, SPPFDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PFD’, Mandatory
R-PFD-CODE 004 005 X - Format Code Mandatory
FILLER 009 024 X - - -
FILLER 033 032 X - - -
R-PFD-LOOKUP-ID 065 003 X - Lookup ID
R-PFD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
R-PFD-DESCRIPTION 086 030 X - Description Mandatory
R-PFD-DOC-FORMAT 116 005 X - Document Format Mandatory
R-PFD-PURCHASE-DEF(1) 121 005 X - Purchase Definition 1 Mandatory
R-PFD-PURCHASE-DEF(2) 126 005 X - Purchase Definition 2
R-PFD-ORD-STATUS-FROM 146 001 X - Order Status From
R-PFD-ORD-STATUS-TO 147 001 X - Order Status To

R-PFD-INV-STATUS-FROM 148 002 X - Invoice Status From
R-PFD-INV-STATUS-TO 150 002 X - Invoice Status To
R-PFD-GRN-STATUS-FROM 152 002 X - GRN Status From
R-PFD-GRN-STATUS-TO 154 002 X - GRN Status To
R-PFD-DOC-TYPE 156 001 X - Document Type
R-PFD-DOC-NUMBERING 157 001 X - Document Numbering
R-PFD-SEL-CODE(1) 158 002 X - Selection Code 1
R-PFD-REPRINT-FLAG 168 001 X - Reprint Flag

Purchase Format Definition record, SPPFDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-PFD-DOC-DATE 169 001 X - Document Date Indicator
R-PFD-DESC-LINE-IND 170 001 X - Description Line Indicator
R-PFD-INCLUDE-EXCLUDE 171 001 X - Include/Exclude Indicator
FILLER 172 361 X - -
R-PFD-GRP-MASK 533 005 X - -
FILLER 538 269 X - -
FILLER 807 218 X - -

Payment Terms Instalments record, SSPLERC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PLE’, Mandatory
R-PLE-CODE 004 010 X - Payment Terms Code
R-PLE-LINE 014 002 N 0 Payment Terms Line No Mandatory
FILLER 016 049 X - - -
R-PLE-LOOKUP-ID 065 003 X - Lookup ID
R-PLE-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 020 X - - -
R-PLE-DATE-IND 098 002 N 0 Date Indicator
R-PLE-DATE-BASE-IND 100 002 N 0 Date Based On Indicator
R-PLE-TERMS-NUMBER 102 003 N 0 Payment Terms Number
R-PLE-TERMS-UNIT 105 001 N 0 Time Units
R-PLE-TERMS-MONTH-END 106 001 N 0 Round To End Of Month
R-PLE-TERMS-PERCENT 107 005 N 3 Percentage
R-PLE-TERMS-R-DATE(1) 112 002 N 0 Rounding Date 1

R-PLE-TERMS-R-DAY(1) 120 001 X - Rounding Day – Sunday
R-PLE-TERMS-R-DAY(2) 121 001 X - Rounding Day – Monday
R-PLE-TERMS-R-DAY(3) 122 001 X - Rounding Day – Tuesday
R-PLE-TERMS-R-DAY(4) 123 001 X - Rounding Day – Wednesday
R-PLE-TERMS-R-DAY(5) 124 001 X - Rounding Day – Thursday
R-PLE-TERMS-R-DAY(6) 125 001 X - Rounding Day – Friday
R-PLE-TERMS-R-DAY(7) 126 001 X - Rounding Day – Saturday
FILLER 127 482 X - - -
FILLER 609 416 X - - -

Purchase Order Definition record, SPPODRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’POD’, Mandatory
R-POD-CODE 004 005 X - Transaction Type Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-POD-LOOKUP-ID 065 003 X - Lookup Id
R-POD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-POD-DESCRIPTION 086 030 X - Description
R-POD-ORDER-RETURN 116 001 X - Order/Return Mandatory
R-POD-ORDER-INVOICE 117 001 X - Order/Invoice Entry Mandatory
R-POD-GOODS-RECEIPT 118 001 X - Goods Receipt
R-POD-UPDATE-STOCK 119 001 X - Update Stock
R-POD-DUE-DATE 120 001 X - Due Date per Line
R-POD-ACCOUNT-ENTRY 121 001 X - Account Code per Line
R-POD-INV-ADDRESS 122 010 X - Invoice Address Code
R-POD-MANUAL-REF 132 001 X - Manual Order References

FILLER 133 005 X - -
R-POD-DOC-PREF 138 004 X - Order Reference Prefix
R-POD-DIRECT-PRINT-ORDER 142 001 X - Direct Print Order
R-POD-ORDER-FORMAT 143 005 X - Document Format
R-POD-COMM-INTERFACE 148 005 X - Commitment Interface Code
R-POD-INVY-INTERFACE 153 005 X - Inventory Interface Code
R-POD-UINV-INTERFACE 158 005 X - Unapproved Invoices Interface Code
R-POD-AINV-INTERFACE 163 005 X - Approved Invoices Interface Code
R-POD-ORDER-ANAL-0 168 001 X - Analysis by Header 0

Purchase Order Definition record, SPPODRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-POD-LINE-ANAL-0 178 001 X - Analysis by Detail 0

R-POD-CALC-CODE-1 188 003 X - Calculation Code 1


R-POD-AMEND-BPC 239 001 X - BPC Override
R-POD-AMEND-CALC-1 240 001 X - Calc Code Override 1

R-POD-LINE-VALUE 257 003 X - Line Value
R-POD-MATCH-VALUE 260 003 X - Match Value
R-POD-COST-VALUE 263 003 X - Cost Value
R-POD-ASSET-ENTRY 266 001 X - Asset Code per Line
R-POD-RECEIPT-REF 267 001 X - Receipt Reference per Line


R-POD-AUDIT-DATE 268 001 X - Audit Date
R-POD-SPLIT-VAL 269 003 X - Split Value
R-POD-UPD-COST-TOL-PER 272 005 N 2 Update Cost
R-POD-UPD-COST-TOL-VAL 277 018 N 5 Update Cost Tolerance Value
R-POD-COST-ADJ-INTERFACE 295 005 X - Cost Adjustment Interface
R-POD-BCHECK-VALUE 300 003 X - Budget Check Value
R-POD-EXPEND-CHECK-VALUE 303 003 X - Budget Check Value
R-POD-UPDATE-MOVEMENT 306 001 X - Update Movement Costs
R-POD-C2-CODE 307 003 X - Conversion Code
R-POD-C3-CODE 310 003 X - Conversion Code
R-POD-ADV-FACTOR 313 003 X - Additional Cost Charge Factor
R-POD-ADV-INDEX 316 005 X - Additional Cost Charge Index
R-POD-BRT-HIER-1 321 005 X - Brazilian Tax Hierarchy 1

R-POD-BRT-CALC-1 346 003 X - Brazilian Tax Calculation Code 1
R-POD-MATCH-VALUE2 361 003 X - Match Value 2
R-POD-SUP-ADD-HDR-LBLS 370 001 X - Suppress Additional Header Labels
FILLER 371 430 X - -
FILLER 801 224 X - -

Payment Profile record, SAPPFRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PPF’, Mandatory
R-PPF-CODE 004 005 X - Payment Profile Code Mandatory
FILLER 009 056 X - - -
R-PPF-LOOKUP-ID 065 003 X - Lookup ID
R-PPF-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
R-PPF-PROFILE-NAME 086 030 X - Profile Name Mandatory
R-PPF-PAY-DEBIT 116 001 X - Payments Or Debits Mandatory
R-PPF-DAG 117 005 X - Data Access Group
R-PPF-PAY-FILE-IND 122 001 X - Payment File Indicator Mandatory
R-PPF-AC-FROM 123 010 X - Account From
R-PPF-AC-TO 133 010 X - Account To
R-PPF-PRIORITY-FROM 143 001 X - Priority From
R-PPF-PRIORITY-TO 144 001 X - Priority To
R-PPF-PAY-OPTION 145 001 X - Payment Option Mandatory
R-PPF-PAY-METHOD 146 001 X - Payment Method

R-PPF-CLIENT-DEBITS 147 001 X - Include Client Account Debits
R-PPF-CODES-OP 148 001 X - Code List Operator
R-PPF-CONV-CODE(1) 149 005 X - Conversion Code 1

Payment Profile record, SAPPFRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)


R-PPF-ALLOC-FROM 299 001 X - Allocation Marker From Mandatory
R-PPF-ALLOC-TO 300 001 X - Allocation Marker To Mandatory
R-PPF-SELECTION-CODE(1) 301 005 X - Selection Code 1
R-PPF-SUB-CATEGORY(1) 326 001 X - Sub Category 1


R-PPF-BANK-CODE 331 005 X - Bank Code
R-PPF-AMT-TYPE 336 001 X - Amount Type
R-PPF-AMOUNT-FROM 337 015 N 0 Amount From
R-PPF-AMOUNT-TO 352 015 N 0 Amount To
R-PPF-CONV-AMT-FROM(1) 367 015 N 0 Conversion Amount From 1
R-PPF-CONV-AMT-TO(1) 382 015 N 0 Conversion Amount To 1



R-PPF-PAYMENT-ACC 757 015 X - Payment Account
R-PPF-MAX-PAYMENT 772 015 N 0 Maximum Payment
R-PPF-SINGLE-PAYMENT 787 001 X - Single Payment
R-PPF-EXCLUDE-ROUGH 788 001 X - Exclude Rough
FILLER 789 027 X -
FILLER 816 209 X -

Purchase Header Presets record, SPPPHRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’PPH’, Mandatory
R-PPH-CODE 004 005 X - Transaction Type Mandatory
FILLER 009 024 X - -
FILLER 033 032 X - -
R-PPH-LOOKUP-ID 065 003 X - Lookup Id
R-PPH-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-PPH-SUPP-ADDRESS 086 010 X - Supplier Address
R-PPH-DEL-ADDRESS 096 010 X - Delivery Address
R-PPH-TRANS-DATE 106 010 X - Order Date
R-PPH-REFERENCE 116 015 X - Second Order Reference
R-PPH-COMMENTS 131 025 X - Comments
R-PPH-ACK-REF 156 015 X - Acknowledgement Reference
R-PPH-ACK-DATE 171 010 X - Acknowledgement Date
R-PPH-DEL-DATE 181 010 X - Delivery Date
R-PPH-DEL-ADVISED 191 001 X - Date Confirmed Indicator

R-PPH-INV-DATE 192 010 X - Invoice Date
R-PPH-SUPP-INV-REF 202 015 X - Suppliers Invoice Reference
R-PPH-PAY-DATE 217 010 X - Payment Date
R-PPH-ANAL-CODE-0 227 015 X - Analysis Code 0

Purchase Header Presets record, SPPPHRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 377 424 X - -
FILLER 801 224 X - -

Purchase Detail Presets record, SPPPIRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’PPI’, Mandatory
R-PPI-CODE 004 005 X - Transaction Type Mandatory
R-PPI-LINE 009 004 X - Line Number Mandatory
FILLER 013 020 X - -
FILLER 033 032 X - -
R-PPI-LOOKUP-ID 065 003 X - Lookup Id
R-PPI-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-PPI-ITEM-CODE 086 015 X - Item Code
R-PPI-DESCRIPTION 101 030 X - Description
R-PPI-LOCATION 131 005 X - Location
R-PPI-PURCH-QTY 136 018 N 5 Purchase Quantity
R-PPI-STOCK-QTY 154 018 N 5 Stock Quantity
R-PPI-DEL-DATE 172 010 X - Delivery Date
R-PPI-DEL-ADVISED 182 001 X - Delivery Advised
R-PPI-ACCOUNT-CODE 183 015 X - Account Code

R-PPI-ASSET-CODE 198 010 X - Asset Code
R-PPI-ASSET-SUB-CODE 208 005 X - Asset SubCode
R-PPI-ANAL-CODE-0 213 015 X - Analysis Code 0
R-PPI-ANAL- CODE-7 318 015 X - Analysis Code 7

Purchase Detail Presets record, SPPPIRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

FILLER 363 438 X - -
FILLER 801 224 X - -

Price Book Maintenance record, SBPRBRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PRB’, Mandatory
R-PRB-CODE 004 005 X - Price Book Code Mandatory
R-PRB-ANCODE1 009 015 X - Analysis Code 1
R-PRB-START-DATE 054 008 N 0 Start Date
FILLER 062 003 X - - -
R-PRB-LOOKUP-ID 065 003 X - Lookup ID
R-PRB-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
R-PRB-END-DATE 086 008 N 0 End Date
R-PRB-BSP 094 003 X - Base Selling Price
R-PRB-UNIT-OF-SALE 097 005 X - Unit Of Sale
R-PRB-RANGE-CODE 102 003 X - Range Code
R-PRB-THRESHOLD(1) 105 013 N 0 Threshold Amount 1

R-PRB-VALUE(1) 209 018 N 5 Table Value 1

Price Book Maintenance record, SBPRBRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-PRB-PRAV(1) 353 001 X - Percent, Amount, Rate or Value 1 Mandatory
R-PRB-PRAV(2) 354 001 X - Percent, Amount, Rate or Value 2
R-PRB-OP(1) 361 001 X - Operator 1

FILLER 369 656 X - -

Price Book Hierarchy record, SBPRDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PRD’, Mandatory
R-PRD-PRICE-BOOK-CODE 004 005 X - Price Book Code Mandatory
FILLER 009 024 X - - -
FILLER 033 032 X - - -
R-PRD-LOOKUP-ID 065 003 X - Lookup ID
R-PRD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-PRD-DESCRIPTION 086 020 X - Description Mandatory
R-PRD-CATEGORY(1) 106 002 X - Selection Category 1
R-PRD-SUB-CATEGORY(1) 112 001 X - Sub Category 1
FILLER 115 910 X - -

Price Book Hierarchy record, SBPRHRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PRH’, Mandatory
R-PRH-DBASE-CODE 004 003 X - Database Code
FILLER 007 026 X - - -
FILLER 033 032 X - - -
R-PRH-LOOKUP-ID 065 003 X - Lookup ID
R-PRH-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
R-PRH-SEQ-NO(1) 086 001 X - Sequence Number 1
R-PRH-CODE(1) 087 005 X - Price Book Code 1

FILLER 146 879 X - -

Payment Terms Header record, SSPTERC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘PTE’, Mandatory
R-PTE-CODE 004 010 X - Payment Terms Code Mandatory
FILLER 014 051 X - - -
R-PTE-LOOKUP-ID 065 003 X - Lookup ID
R-PTE-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 020 X - - -
R-PTE-DESCRIPTION 098 050 X - Description
R-PTE-DOC1-DESC 148 050 X - Doc 1 Description
R-PTE-TAX-IN-FIRST 348 001 X - Tax to be included in first payment flag
FILLER 349 676 X -

Unit Conversion Table record, SPPUCRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’PUC’, Mandatory
R-PUC-FROM-UNITS 004 005 X - Convert From Mandatory
R-PUC-TO-UNITS 009 005 X - Convert To Mandatory
FILLER 014 051 X - -
R-PUC-LOOKUP-ID 065 003 X - Lookup Code
R-PUC-LOOKUP-CODE 068 010 X - Lookup Id
FILLER 078 008 X - -
R-PUC-OPERATOR 086 001 X - Multiply/Divide Mandatory
R-PUC-FACTOR 087 018 N 9 Factor Mandatory
FILLER 105 696 X - -
FILLER 801 224 X - -

Additional Descriptions record, SASDERC.CPY, (SQL miscellaneous table SSRFMSC)

SDE-REC-TYPE 001 003 X - Reference Record Type Value ‘SDE’, Mandatory
SDE-CODE 004 005 X - Standard Description Code Mandatory
FILLER 009 056 X - - -
FILLER 065 013 X - - -
FILLER 078 008 X - - -
SDE-DESCRIPTION-1 086 040 X - Description Line 1 Mandatory
SDE-DESCRIPTION-2 126 040 X - Description Line 2
FILLER 326 475 X - -
FILLER 801 224 X - -

Additional Descriptions record, SASDTRC.CPY, (SQL miscellaneous table SSRFMSC)

SDT-REC-TYPE 001 003 X - Reference Record Type Value ‘SDT’, Mandatory
SDT-HELD-CODE 004 001 X - Ledger/Budget Code Mandatory
SDT-HOLD-REF 005 005 X - Journal Held Control Reference Mandatory
SDT-TRN-REF 010 015 X - Transaction Reference Mandatory
SDT-JRNL-NO 025 005 N - Journal Line Number Key Mandatory
SDT-JRNL-SUFFIX 030 002 N - Journal Line Number Suffix Mandatory
SDT-OPERATOR 032 003 X - User Operator Mandatory
FILLER 035 030 X - - -
FILLER 065 013 X - - -
FILLER 078 008 X - - -
SDT-DESCRIPTION-1 086 040 X - Description Line 1 Mandatory
SDT-DESCRIPTION-2 126 040 X - Description Line 2

FILLER 326 475 X - -
FILLER 801 224 X - -

Sales Format record, SOSFDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘SFD’, Mandatory
R-SFD-CODE 004 005 X - Format Code Mandatory
FILLER 009 024 X - - -
FILLER 033 032 X - - -
R-SFD-LOOKUP-ID 065 003 X - Lookup ID
R-SFD-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
R-SFD-DESCRIPTION 086 030 X - Description Mandatory
R-SFD-DOC-FORMAT 116 005 X - Document Format Mandatory
R-SFD-SALES-DEF(1) 121 005 X - Sales Definition 1 Mandatory
R-SFD-SALES-DEF(2) 126 005 X - Sales Definition 2
R-SFD-STATUS-FROM 146 001 X - Status From
R-SFD-STATUS-TO 147 001 X - Status To

R-SFD-SEL-CODE(1) 148 002 X - Selection Code 1
R-SFD-REPRINT-FLAG 158 001 X - Reprint
R-SFD-DOC-DATE 159 001 X - Document Date Indicator
R-SFD-DESC-LINE-IND 160 001 X - Description Line Indicator
R-SFD-HELD-ORDERS-IND 161 001 X - Held Orders Indicator
FILLER 162 365 X - -

Sales Format record, SOSFDRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-SFD-GRP-MASK 527 005 X - Data Access Group
FILLER 532 269 X - -
FILLER 801 224 X - -

Statement Line Contents record, SASLNRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’SLN’, Mandatory
R-LINE-CODE 004 005 X - Line Content Code Mandatory
R-LINE-NO 009 005 X - Statement Line Number Mandatory
FILLER 014 019 X - -
FILLER 033 032 X - -
R-SLN-LOOKUP-ID 065 003 X - Lookup Id
R-SLN-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-LINE-TYPE 086 002 X - Line Type Mandatory
R-LINE-NAME 088 030 X - Line Name Mandatory except on type ’H’ lines
R-LINE-AC-FIRST 118 015 X - Account Code-From Mandatory on type ’L’ and ’C’ lines
R-LINE-AC-LAST 133 015 X - Account Code-To
R-NORMAL-SIGN 148 001 X - Normal Sign Mandatory except on type ’H’ lines
R-LINE-REVERSE 149 001 X - Amount Reverse
R-AC-TOTAL 150 001 X - Account Details
R-LINE-LEDGER-CODE 151 003 X - Subsidiary Ledger

R-LINE-COL-CHANGE 154 001 X - Column Change
R-LINE-REVALUE 155 001 X - Revalue from Other Amount
R-LINE-SUPPRESS-DC 156 001 X - Suppress Line/Account
R-LINE-SUP-ACCOUNT 157 001 X - Suppress at Account Level
R-LINE-ANAL-CAT(1) 158 002 X - Selection Category 1
R-LINE-ANAL-FIRST(1) 160 015 X - Selection Code-From1
R-LINE-ANAL-LAST(1) 175 015 X - Selection Code-To1
R-LINE-ANAL-FIRST(2) 192 015 X - Selection Code-From 2
R-LINE-ANAL-LAST(2) 207 015 X - Selection Code-To 2
R-LINE-ANAL-FIRST(3) 224 015 X - Selection Code-From 3

Statement Line Contents record, SASLNRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-LINE-ANAL-LAST(3) 239 015 X - Selection Code-To 3
FILLER 254 279 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Print Picking Control Record, SBSPPRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘SPP’, mandatory
FILLER 004 061 X -
R-SPP-LOOKUP-ID 065 003 X - Lookup Id
R-SPP-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-SPP-DOC-FORMAT 086 005 X - Document Format
R-SPP-LEVEL-1 091 002 X - Level 1
R-SPP-LEVEL-2 093 002 X - Level 2
R-SPP-LOCATION-FROM 095 005 X - Location From
R-SPP-LOCATION-TO 100 005 X - Location To
R-SPP-ITEM-CODE-FROM 105 015 X - Item From
R-SPP-ITEM-CODE-TO 120 015 X - Item To
R-SPP-ANAL-CAT 135 002 X - Analysis Category
R-SPP-ANAL-CODE-FROM 137 015 X - Analysis Code From
R-SPP-ANAL-CODE-TO 152 015 X - Analysis Code To
FILLER 167 858 X - Filler

Spread Ratios record, SFSPRRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’SPR’, Mandatory
R-SPREAD-CODE 004 003 X - Ratio Code Mandatory
FILLER 007 026 X - -
FILLER 033 032 X - -
R-SPR-LOOKUP-ID 065 003 X - Lookup Id
R-SPR-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-SPREAD-DESCR 086 030 X - Ratio Name Mandatory
R-RATIO 116 300 N - Period Ratios Table, 60 x 5 - digit numbers
R-OPERATING-PERIODS 416 003 N - Operating periods
FILLER 419 114 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Sequence Number record, SASQNRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘SQN’, Mandatory
R-SQN-SEQUENCE-CODE 004 005 X - Sequence Code Mandatory
R-SQN-BUDGET 009 001 X - Budget Mandatory
FILLER 010 023 X - - -
FILLER 033 032 X - - -
FILLER 065 021 X - - -
R-SQN-DESCRIPTION 086 030 X - Description Mandatory
R-SQN-AUTO-MAN 116 001 X - Automatic, Manual, Date, Entry Mandatory
R-SQN-NEXT-NUMBER 117 007 N 0 Next available number
R-SQN-REG-DATE 124 008 X - Registration Date
FILLER 132 401 X - - -
FILLER 533 268 X - - -
FILLER 801 224 X - - -

Tax Account record, SATAXRC.CPY, (SQL miscellaneous table SSRFMSC)

R-TAX-KEY-TYPE 001 003 X - Reference Record Type Value ‘TAX’, Mandatory
R-TAX-DET-CODE 004 015 X - Tax Analysis Code Mandatory
FILLER 019 014 X - - -
FILLER 033 032 X - - -
R-TAX-LOOKUP-ID 065 003 X - Lookup ID
R-TAX-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - - -
R-TAX-DESC-1 086 030 X - Tax Description Line 1
R-TAX-RATE 206 007 N 5 Tax Rate
R-TAX-ACCOUNT-CODE 213 015 X - Account Code
R-TAX-INPUT-ACCOUNT 228 015 X - Input Account
R-TAX-OUTPUT-ACCOUNT 243 015 X - Output Account
R-TAX-2ND-INPUT-ACCOUNT 258 015 X - 2nd Input Account

R-TAX-2ND-OUTPUT-ACCOUNT 273 015 X - 2nd Output Account
R-TAX-INPUT-PERCENT 288 004 N 2 Input Percent
R-TAX-OUTPUT-PERCENT 292 004 N 2 Output Percent
R-TAX-STOPPAGE-RATE 296 007 N 5 Stoppage Rate
R-TAX-INPUT-STOPPAGE-ACC 303 015 X - Input Stoppage Account
R-TAX-OUTPUT-STOPPAGE-ACC 318 015 X - Output Stoppage Account
R-TAX-INPUT-STOPPAGE- 333 015 X - Input Stoppage Contra Account

CONTRA
R-TAX-OUTPUT-STOPPAGE- 348 015 X - Output Stoppage Contra Account

CONTRA

Tax Account record, SATAXRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-TAX-ROUND-METHOD 363 001 X - Tax Rounding Method
R-TAX-ROUND-UNITS 364 001 X - Tax Rounding Units
FILLER 365 660 X - -

Treasurer Interface Definition record, SATIDRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’TID’, Mandatory
R-TID-TRANS-TYPE 004 002 X - Transaction Type Mandatory
R-TID-AC-BANK 006 004 X - A/c Bank
R-TID-BANK-AC 010 004 X - Bank A/c
FILLER 014 019 X - -
FILLER 033 032 X - -
R-TID-LOOKUP-ID 065 003 X - Lookup Id
R-TID-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-TID-M-D-AC 086 015 X - Primary Memo Debit A/c
R-TID-M-C-AC 101 015 X - Primary Memo Credit A/c
R-TID-S-D-AC 116 015 X - Primary Settl’nt Dr A/c Mandatory
R-TID-S-C-AC 131 015 X - Primary Settl’nt Cr A/c Mandatory
R-TID-M-D-INT-AC 146 015 X - Interest Memo Debit A/c
R-TID-M-C-INT-AC 161 015 X - Interest Memo Credit A/c
R-TID-S-D-INT-AC 176 015 X - Interest Settl’nt Dr A/c

R-TID-S-C-INT-AC 191 015 X - Interest Settl’nt Cr A/c
FILLER 206 327 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Tax Listing Layout record, SATLLRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘TLL’, Mandatory
R-TLL-LAYOUT-CODE 004 005 X - Layout Code Mandatory
FILLER 009 024 X - - -
FILLER 033 032 X - - -
FILLER 065 021 X - - -
R-TLL-DESCRIPTION 086 025 X - Description Mandatory
R-TLL-GROSS-ACCOUNT-FROM(1) 111 015 X - Gross Account From 1
R-TLL-GROSS-ACCOUNT-TO(1) 186 015 X - Gross Account To 1

R-TLL-GROSS-ACCOUNT-TYPE-D 261 001 X - Gross Account Type D
R-TLL-GROSS-ACCOUNT-TYPE-C 262 001 X - Gross Account Type C
R-TLL-GROSS-ACCOUNT-TYPE-T 263 001 X - Gross Account Type T
R-TLL-GROSS-ACCOUNT-TYPE-B 264 001 X - Gross Account Type B
R-TLL-GROSS-ACCOUNT-TYPE-P 265 001 X - Gross Account Type P
R-TLL-GROSS-ACCOUNT-TYPE-M 266 001 X - Gross Account Type M

Tax Listing Layout record, SATLLRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-TLL-SELECTION-1 267 002 X - Selection Code 1
R-TLL-INCLUDE-ARCHIVE 277 001 X - Include Archive
R-TLL-CASH-INVOICE 278 001 X - Cash Or Invoice
R-TLL-PERIOD-DATE 279 002 X - Period Or Date Range to be entered
R-TLL-SEQUENCE-NO-CODE 281 005 X - Sequence No Code
R-TLL-FORMAT-CODE 286 005 X - Format Code Mandatory
R-TLL-TAX-ACCOUNT-FROM(1) 291 015 X - Tax Account From 1
R-TLL-TAX-ACCOUNT-TO(1) 351 015 X - Tax Account To 1

R-TLL-NET-ACCOUNT-FROM(1) 411 015 X - Net Account From 1
R-TLL-NET-ACCOUNT-TO(1) 471 015 X - Net Account To 1

Tax Listing Layout record, SATLLRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-TLL-PERIOD-DATE-SEQ 531 002 X - Period Date Sequence
FILLER 533 268 X - -
FILLER 801 224 X - -

Transaction Matching Selections Record, SATMSRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘TMS’, mandatory
FILLER 004 061 X -
R-TMS-LOOKUP-ID 065 003 X - Lookup Id
R-TMS-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-TMS-AC-TYPE 086 001 X Account Type
R-TMS-AC-FROM 087 015 X Account From
R-TMS-AC-TO 102 015 X Account To
R-TMS-SELEC-1 117 002 X Selection 1
R-TMS-SELEC-1-FROM 119 015 X Selection From 1
R-TMS-SELEC-1-TO 134 015 X Selection To 1

R-TMS-MATCH-1 213 002 X Match Criteria 1
R-TMS-BASE-OTHER 219 001 X Base or Other Amount Matching
R-TMS-REP-UNMATCHED 220 001 X Report Unmatched
R-TMS-SUP-REP-MATCHED 221 001 X Report Matched
R-TMS-POST 222 001 X Post Transactions
R-TMS-DISC-AC 223 015 X Input Discount Account Code
R-TMS-DISC-AC-NAME 238 030 X Input Discount Account Code Name
R-TMS-EXCH-AC 268 015 X Output Discount Account Code

Transaction Matching Selections Record, SATMSRC.CPY, (SQL miscellaneous table SSRFMSC) – (continued)

R-TMS-EXCH-AC-NAME 283 030 X Output Discount Account Code Name
R-TMS-LOSS-AC 313 015 X Loss Account
R-TMS-LOSS-AC-NAME 328 030 X Loss Account Name
R-TMS-DISC-TOLERANCE 358 007 X Discount Tolerance

Treasurer Transaction Reference record, SATTRRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’TTR’, Mandatory
R-TTR-REFERENCE 004 007 X - Transaction Reference Mandatory
FILLER 011 022 X - -
FILLER 033 032 X - -
R-TTR-LOOKUP-ID 065 003 X - Lookup Id
R-TTR-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X - -
R-TTR-MEMO-POS 086 001 X - Memo Account +ive Mandatory
R-TTR-MEMO-NEG 087 001 X - Memo Account -ive Mandatory
R-TTR-SETT-POS 088 001 X - Settlement Account +ive Mandatory
R-TTR-SETT-NEG 089 001 X - Settlement Account -ive Mandatory
FILLER 090 443 X - -
FILLER 533 268 X - -
FILLER 801 224 X - -

Tax Accounts Definition record, SSTXARC.CPY, (SQL miscellaneous table SSRFMSC)

TXA-REC-TYPE 001 003 X - Reference Record Type Value ‘TXA’, Mandatory
TXA-DATABASE 004 003 X - Database Code Mandatory
FILLER 007 058 X - - -
FILLER 065 013 X - - -
FILLER 078 008 X - - -
TXA-SO-AC-1 086 015 X - Sales Order Tax Account 1
TXA-PO-AC-1 236 015 X - Purchase Order Tax Account 1

FILLER 396 629 X - -

Version Control record, SSVERRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ’VER’, Mandatory
FILLER 004 061 X - -
FILLER 065 021 X - -
VER-VERSION 086 003 X - Version Mandatory, value numeric
VER-LAN-CODE 089 002 N - Language Code
FILLER 091 710 X - -
FILLER 801 224 X - -

Void Payments Record, SAVPXRC.CPY, (SQL miscellaneous table SSRFMSC)

FILLER 001 003 X - Reference Record Type Value ‘VPX’, mandatory
FILLER 004 061 X -
R-VPX-LOOKUP-ID 065 003 X - Lookup Id
R-VPX-LOOKUP-CODE 068 010 X - Lookup Code
FILLER 078 008 X -
R-VPX-PAYMENT-ACCOUNT-CODE 086 015 X - Payment Account
R-VPX-DISCOUNT-ACCOUNT- 101 015 X - Discount Account

CODE
R-VPX-WITHHOLD- 116 001 X - Withold Transactions

TRANSACTIONS
R-VPX-POST-TRANSACTIONS 117 001 X - Post Transactions

Lead Times record, SBXLTRC.CPY, (SQL miscellaneous table SSRFMSC)

R-XLT-REC-ID 001 003 X - Reference Record Type Value ‘XLT’, Mandatory
R-XLT-LEAD-ANAL-1 004 015 X - Lead Analysis Code 1
R-XLT-LEAD-ANAL-2 019 015 X - Lead Analysis Code 2
FILLER 034 031 X - - -
FILLER 065 013 X - - -
FILLER 078 008 X - - -
R-XLT-LEAD-DAYS 086 003 X - Lead Days
FILLER 089 712 X - - -
FILLER 801 224 X - - -

Ledger file (and Budget file)

Description
The Ledger file holds the ledger transactions for SunAccount. The Budget files are
defined in the same way as the Ledger file. The transactions held on the Budget files are
ledger transactions that have been posted to budget rather than actuals in SunAccount.
These files have exactly the same format as the Ledger file.
If the system you are using includes the Asset Register module, then there will exist an
Asset file along with the Ledger file. The Asset file is a simple index file, containing details
of transactions posted in the Asset Register, that is, the link between the Asset and the
Account.
Note that with SQL versions of SunSystems v4, the tables containing the budget data are
separate to the ledger data tables. The layout is the same; the only difference is the table
name.
There are two types of record on the Ledger file:

 control record
 transaction record.
There is one control record (type ‘C’) per file: there is one transaction (type ‘T’) record per
transaction posted to the ledger. For each transaction posted to the Ledger file, if that
transaction includes asset details, then an entry is posted to the Asset file.
M FD LEDGER-FILE.
V *FD LEDGER-FILE VALUE OF ID IS LEDGER-FILE-NAME.
01 STD-LEDGER-RECORD.
02 STD-LEDGER-KEY.
03 STD-LEDGER-AC PIC
X(015).
03 FILLER PIC
X(015).
03 STD-LEDGER-ALTERNATE-KEY PIC X(008).
02 STD-LEDGER-DATA PIC
X(339).
M FD ASSET-FILE.
V *FD ASSET-FILE VALUE OF ID IS ASSET-FILE-NAME.
01 ASSET-RECORD.
02 ASSET-KEY.
03 ASSET-AC
PIC X(015).
03 FILLER
PIC X(023).
02 ASSET-DATA PIC
X(015).
Physical Record

Primary Key
Key Data 30
Alternate Key 8
____
38
Data 339
____
Total Physical 377

Filler 135
____
Total Logical 512

Note: The alternate key is embedded in the key data.

Ledger file record descriptions
Note: The SQL table that contains the Ledger transactions is named according to
the database being used. The control record is stored in a table shared by other
databases.

Ledger Transaction record, see SALDGRRC.CPY, SQL table name SALFLDGddd for the Actual Ledger or SAbFLDGddd where b=Budget Code (B-K)
COBOL POS’N IN FIELD FIELD DEC. SQL COLUMN SQL FIELD DESCRIPTION COMMENT
FIELD NAME RECORD LENGTH TYPE PLACES TYPE
L-AC 001 015 X - ACCNT_CODE char(15) Account Code Mandatory
L-AP 016 007 N 0 PERIOD int Accounting Period Mandatory
L-DT 023 008 N 0 TRANS_DATE int Transaction Date Mandatory
L-JN 031 004 S 0 JRNAL_NO int Journal Number Mandatory,PICS 9

(07) COMP-3
L-TN 035 004 S 0 JRNAL_LINE int Journal Line Number Mandatory, PICS 9
(07) COMP-3
L-RECORD-TYPE 039 001 X - - - Record Type Mandatory, value ’T’
L-AM 040 010 N 3 AMOUNT numeric Base Amount Mandatory, PIC 9

(15) V999 COMP-3
L-DC 050 001 X - D_C char(1) Debit/Credit Indicator Mandatory
L-AI 051 001 X - ALLOCATION char(1) Allocation Indicator
L-TT 052 005 X - JRNAL_TYPE char(5) Journal Type Mandatory
L-JR 057 005 X - JRNAL_SRCE char(5) Journal Source
L-RF 062 015 X - TREFERENCE char(15) Transaction Reference
L-DS 077 025 X - DESCRIPTN char(25) Transaction Description
L-ED 102 008 N 0 ENTRY_DATE int Entry Date Mandatory
L-EP 110 007 N 0 ENTRY_PRD int Entry Period Mandatory
L-ADD-DATE 117 008 N 0 DUE_DATE int Due Date
FILLER 125 010 X - - - -
L-ALLOC-RF 135 005 N - ALLOC_REF int Payment/Allocation Refernce
L-ALLOC-DT 140 008 N 0 ALLOC_DATE int Payment/Allocation Date
L-ALLOC-AP 148 007 N 0 ALLOC_PERIOD int Payment/Allocation Period
L-ASSET-IND 155 001 X - ASSET_IND char(1) Asset Marker
L-ASSET-CODE 156 010 X - ASSET_CODE char(10) Asset Code

L-ASSET-SUB-CODE 166 005 X - ASSET_SUB char(5) Asset Sub-Code
L-CONV-CODE 171 005 X - CONV_CODE char(5) Conversion Code
L-CONV-RATE 176 010 N 9 CONV_RATE numeric Conversion Rate PIC 9(9)

V9(9) COMP-3

Ledger Transaction record, see SALDGRRC.CPY, SQL table name SALFLDGddd for the Actual Ledger or SAbFLDGddd where b=Budget Code (B-K) –
(continued)
COBOL POS’N IN FIELD FIELD DEC. SQL COLUMN SQL DESCRIPTION COMMENT
FIELD NAME RECORD LENGTH TYPE PLACES FIELD
TYPE
L-OTHER-AM 186 010 N 3 OTHER_AMT numeric Other Amount PIC 9(15)

V999 COMP-3
L-OTHER-DP 196 001 X - OTHER_DP char(1) Other Amount d.p.
Next two fields redefine above three fields (not SQL):
L-CLEARDOWN 197 005 N 0 CLEARDOWN char(5) Cleardown Sequence

Number
FILLER 202 004 X - - - -
L-REVERSAL 206 001 X - REVERSAL char(1) Next Period Reversal
L-LOSS-GAIN 207 001 X - LOSS_GAIN char(1) Revaluation Flag Gain/Loss
L-ROUGH-FLAG 208 001 X - ROUGH_FLAG char (1) Flag of Rough Book status
L-IN-USE-FLAG 209 001 X - IN_USE_FLAG char(1) In Use Flag
L-AN-0 210 015 X - ANAL_T0 char(15) Analysis Code 0
L-POSTING-DATE 360 008 N 0 POSTING_DATE int Posting Date
FILLER 368 001 X - - - -

L-ALLOC-IN-PROGRESS 369 001 X - ALLOC_IN_PROGRES char(1) Allocation in Progress

S
L-HOLD-REF 370 005 N - HOLD_REF int Held Journal Reference
L-HOLD-OP-ID 375 003 X - HOLD_OP_ID char(3) Operator ID for Held Journal
L-BCHECK-ACCT 378 015 X - BCHECK_ACCT char(15) Budget Check

Ledger Transaction record, see SALDGRRC.CPY, SQL table name SALFLDGddd for the Actual Ledger or SAbFLDGddd where b=Budget Code (B-K) –
(continued)
TYPE
L-LAST-CHANGE-USER-ID 393 003 X - LAST_CHANGE_USER char(3) Purchase Order Original

_ID value
L-LAST-CHANGE-DATE-X 396 004 N - LAST_CHANGE_DATE int Last change date
L-ORIGINATOR-ID 400 003 X - ORIGINATOR_ID char Originator

Ledger Control record, see SALDGRRC.CPY, SQL table name SALFMSC
- - - - - D_BASE char(3) Database Code Mandatory
FILLER 001 038 X - - - -
FILLER 039 001 X - A_B char(1) Budget Code B-K Redefines Record
Type - ”C”=
Control Record
L-HIGHEST-JN 040 007 N - HIGH_JRNAL char(7) Highest Journal Number Mandatory
L-HIGHEST-CLEARDOWN 047 005 N - HIGH_CLRDN char(5) Last Cleardown Number
L-VERSION 052 003 N - VERSION char(3) Version Number
L-LANGUAGE-ID 055 002 N - LANG_CODE char(2) Language Code
FILLER 057 210 X - - - -
FILLER 267 246 X - - - -
FILLER 513 512 X - - - -

Ledger Allocation record SALDGRRC.CPY

COBOL POS’N IN FIELD FIELD DEC. DESCRIPTION COMMENT
FIELD NAME RECORD LENGTH TYPE PLACES
LC-ACCOUNT 001 015 X - Account Code
LC-PERIOD 016 009 N - Account Period
LC-DATE 023 008 N - Transaction Date
LC-JOURNAL 031 004 S - Journal Number PICS 9(07) COMP-3
LC-LINE-NO. 035 004 S - Journal Line Number Number PICS 9(07) COMP-3
FILLER 039 986 X - -

Ledger Archive file

Description
The ledger archive file holds the ledger transactions that have been deleted from the
ledger file during Period Cleardown. The layout is the same as the ledger transactions.
There is no corresponding asset file.
Again, there are two types of record on the ledger archive file:
 control record
There is one control record (type ‘C’) per file; there is one transaction (type ‘T’) record per
transaction cleared off the ledger.
M FD ARCHIVE-FILE.
V *FD ARCHIVE-FILE VALUE OF ID IS ARCHIVE-FILE-NAME.
01 STD-ARCHIVE-RECORD.
02 STD-ARCHIVE-KEY.
03 STD-ARCHIVE-AC PIC X(15).
03 STD-ARCHIVE-ALTERNATE-KEY PIC X(8).
02 STD-ARCHIVE-DATA PIC X(339).
Physical Record
Primary Key
Key Data 30
Alternate Key 8
____
38
Data 339
____
Total Physical 378

Filler 134
____
Total Logical 512

Note: The alternate key is embedded in the key data.
Ledger archive file record
Note that the SQL table that contains the ledger archive transactions is named according
to the database being used. The control record is stored in a table shared by other
databases.
Ledger Archive Transaction record, see SALDGRRC.CPY, SQL table name
SALHARCddd:

This record has the same layout as the ledger transaction. The exception to this is with
SQL versions, where an additional field is required to identify the archive year. The
archive data in non-SQL systems is stored in separate files for different years, so this field
is not necessary, whereas in SQL versions, the archive data is all in one table (per
database) regardless of the year. Hence the following field exists
SQL field name SQL field type Description Comment field
ARC_YEAR char(2) Archive Year Mandatory
Ledger Archive Control record, see SALDGRRC.CPY, SQL table name SALHMSC:
Again there is one extra field in the SQL table, defined as above.
Balance file
Description
The balance file holds records with balances for each ledger file combination of:
 Account Code
 Credit/Debit
 Analysis Code
 Conversion Code
 Period.
The budget balance files are defined in the same way as the ledger balance file.
Instead of maintaining a record for each transaction, as in the case of the ledger file, each
balance file record will hold a table of period balances in both base and other amount, for
up to thirteen periods of data (i.e. typically a year’s data). If a user defines more than
thirteen periods in a year then more balance records are created. In addition to the
thirteen periods, a prior year’s balance is held in base and other amount. This is
maintained by a year cleardown process when rolling up prior years’ balances.
The information held in this file is equivalent to that on the ledger file after a cleardown.
This means that any process requiring transaction based information, such as transaction
reference, journal number, or asset information will need to access the ledger file. Where
only periodic or balance data is required, then the balance file may be used instead.
The basic access method for the balance file will present period totals back to the
application in account code sequence (i.e. as if the ledger was being read with only
cleared down balances).
Indexing of balance file
The full primary key to the balance file, including analysis codes, represents
approximately 180 characters. However since most of this key simply represents
uniqueness rather than being of use for reporting purposes, the key may be reduced
considerably by creating a hash code based on credit/debit indicator, conversion code,
period and all the analysis codes. This hash code is then used for accessing records for
updating.
When accessing the balance file for reporting purposes, the hash part of the key is
ignored, and period totals will appear back to the application in random sequence within
account.
It is important to note that a difference between the balance file and the ledger file is the
sequence of processing within an account, must be considered as random. It would be
incorrect for an application to assume that having read a record for a period greater than

required, that there would be no more records on the balance file with earlier periods.
Periods can be processed in blocks of 13 and although the application may only be
interested in the first three periods, the next record may also contain information for the
same three periods but with different analysis.
There are two types of records on the balance file:

 the control record
 the transaction record.
There is one control record (type ‘C’) per file; there is one transaction (type ‘T’) record for
every combination of account code, credit/debit, analysis code, conversion code, and
period.
Cobol File Description
M FD BALANCE-FILE.
V *FD BALANCE-FILE VALUE OF ID IS BALANCE-FILE-NAME.
01 LA-RECORD.
03 LA-KEY.
* Key length = 31 characters
05 LA-ACCOUNT-CODE PIC X(15).
* ledger account code
05 LA-HASH PIC X(16).
* hashed representation of the key data below
03 LA-KEY-DATA.
* Data length = 658 characters
05 LA-CD PIC X(01).
* Debit /Credit marker
05 LA-PERIOD PIC 9(07).
* Base period for record - moves by 13 (1, 14, 27)
* up to the number of periods set for the database
05 LA-CONV PIC X(05).
* Conversion Code
05 LA-ANALS.
* T codes - 10 of them
07 LA-ANAL-T0 PIC X(15).
05 LA-ANAL-T-CODES REDEFINES LA-ANALS.
07 LA-ANAL-T-CODE PIC X(15)OCCURS 10.
03 LA-VALUES.
* the balances:
05 LA-B-LY-BAL-X.
07 LA-B-LY-BAL PIC S9(15)V999.
* Brought Froward base amount

05 LA-O-LY-BAL-X.
07 LA-O-LY-BAL PIC S9(15)V999.
* Brought Forward other amount
05 LA-B-VALUE-X OCCURS 13.
07 LA-B-VALUE PIC S9(15)V999.
* 13 periods base amount (from la-period to la-period + 12)
05 LA-O-VALUE-X OCCURS 13.
07 LA-O-VALUE PIC S9(15)V999.
* 13 periods other amount (from la-period to la-period + 12)
03 LA-OTHER-DP PIC X.
* number of decimals for ther amounts
03 LA-RECORD-TYPE PIC X.
* ‘C’ = Control Record
* ‘T’ = Transaction Record
*
01 LA-CONTROL-RECORD REDEFINES LA-RECORD.
* the control record for the balance file
03 LA-CONTROL-KEY PIC X(31).
* key is low values
03 LA-HIGHEST-JN PIC 9(07).
* last journal updated to the balance file
03 LA-HIGHEST-TN PIC 9(07).
* transaction number of the last journal to be
* updated to the balance file
03 LA-VERSION PIC 9(03).
* the version number (eg 410)
03 LA-CONSOLIDATION PIC X(10).
* the 10 consolidation flags for T codes
* each is Y or blank
03 LA-LAST-UPDATED.
05 LA-LAST-UPDATE-DATE PIC 9(8).
* date of last successful or empty update
05 LA-LAST-UPDATE-TIME.
* time of last successful or empty update
07 LA-LAST-UPDATE-HH PIC 99.
07 LA-LAST-UPDATE-MM PIC 99.
03 LA-CONTROL-RECORD-TYPE PIC X.
* ‘C’ = Control Record
* ‘T’ = Transaction Record
The physical and logical record length is the same (1024 bytes):
Key 031
Data 993
____
Total 1024

Balance File record, see SABALRC.CPY, SQL table name SALFBALddd for the Actual Ledger Balance file or SAbFBALddd where b=Budget Code (B-K)
TYPE
LA-ACCOUNT-CODE 001 015 X - ACCNT_CODE char(15) Account Code Mandatory
LA-HASH 016 016 X - - char(16) Hash Key Mandatory
LA-CD 032 001 X - D_C char(1) Debit/Credit Indicator Mandatory
LA-PERIOD 033 007 X - PERIOD int First Accounting Period Mandatory
LA-CONV 040 005 X - CONV_CODE char(5) Conversion Code
LA-ANAL-T0 045 015 X - ANAL_T0 char(15) Analysis Code 0

LA-B-LY-BAL 195 018 S 3 LAST_YEAR_BAL_BAS numeric Last Year’s Base Balance

E
LA-O-LY-BAL 213 018 S 3 LAST_YEAR_BAL_OTH numeric Last Year’s Other Amount

R Balance
LA-B-VALUE [01] 231 018 S 3 VALUE_1_BASE numeric Period 1 Base Balance

Balance File record, see SABALRC.CPY, SQL table name SALFBALddd for the Actual Ledger Balance file or SAbFBALddd where b=Budget Code (B-K) –
(continued)
TYPE
LA-O-VALUE [01] 465 018 S 3 VALUE_1_OTHER numeric Period 1 Other Amount

Balance

Balance

Balance

Balance

Balance

Balance


Balance

Balance

Balance

Balance

Balance

Balance

Balance

Balance File record, see SABALRC.CPY, SQL table name SALFBALddd for the Actual Ledger Balance file or SAbFBALddd where b=Budget Code (B-K) –
(continued)
TYPE
LA-OTHER-DP 699 001 X - OTHER_DP char(1) Other Amount Decimal

Places
LA-RECORD-TYPE 700 001 X - - - Record Type Mandatory, Value

‘T’
FILLER 701 324 X - - - -

Balance File Control record see SABALRC.CPY, SQL table name SABFMSC
TYPE
- - 003 X - D_BASE char(3)
- - - - - A_B char(1)
LA-CONTROL-KEY 001 031 X - - - Key Low-Values
LA-HIGHEST-JN 032 007 X - HIGH_JRNAL char(7) Highest Journal Number Mandatory
LA-HIGHEST-TN 039 007 X - HIGH_JRNAL_LINE char(7) Highest Line Number Mandatory
LA-VERSION 046 003 X - VERSION char(3) Version Number
LA-CONSOLIDATION 049 010 X - CONSOLIDATION char(10) Balance Consolidation

Indicators
LA-LAST-UPDATE-DATE 059 008 X - LAST_UPDATED char(8) Last Update Date
LA-LAST-UPDATE-HH 067 002 N 0 - - Last Update Hour
LA-LAST-UPDATE-MM 069 002 N 0 - - Last Update Minutes
FILLER 071 629 X - - - -
LA-CONTROL-RECORD-TYPE 700 001 X - - - Record Type Mandatory, Value

‘C’
LA-UPDATE-IN-PROGRESS 701 001 X - UPDATE_IN_PROGRES char (1) Update in Progress

S
FILLER 702 323 X - - - -

Sales order file

Description
The sales order file holds the current Sales Order Processing data, that is, the sales orders entered into
SunBusiness through Sales Order Entry or Sales Order Import. The invoice details are also stored on
this file, when an order reaches the invoice stage.
There are the following types of record on the sales order file:
 control record
 order header record
 invoice header record
 detail record.
There is one control record (type ‘C’) per file: there is one header (type ‘O’) record per order, and one
Header (type ‘I’) record per invoice. There is one detail (type ‘D’) record per order/invoice line.
M FDORDER-FILE.
V *FD ORDER-FILE VALUE OF ID IS ORDER-FILE-NAME.
01 ORDER-RECORD.
03 ORDER-KEY PIC X(21).
03 ORDER-ALTERNATE-KEY.
05 ORDER-ALTERNATE-KEY-ID PIC X(01).
03 ORDER-DATA PIC X(600).
The physical record length on disk (650 bytes) is less than the logical record length within the programs
(1024 bytes):
Physical Record
Primary Key 21
Alternate Key 29
Data 600
____
Total Physical 650

Filler 374
____
Total Logical 1024

Sales Order File record descriptions
Control record, see SOMFRC.CPY,SQL table name SOMFMSC
OC-TRANS-TYPE 001 001 X - - - Record Type Mandatory, value

’C’
OC-CONTROL 002 020 X - - - - Always set to

LOW-VALUES
OC-KEY-ID 022 001 X - - - Alternate Key Id Mandatory, value

’C’
FILLER 023 028 X - - - -
OC-VERSION 051 003 N - VERSION char(3) Version Mandatory, value

420
OC-LANGUAGE 054 003 X - LANUAGE_CODE char(3) Language Code
FILLER 057 520 X - - - -
FILLER 577 224 X - - - -
FILLER 801 224 X - - - -

Sales Order/Invoice Header record, see SOMFRC.CPY,SQL table name SOMFHDRddd
TYPE
OH-TRANS-TYPE 001 001 X - REC_TYPE char(1) Record Type Mandatory value

’O’ for Order
Header ‘I’ for
Invoice Header
FILLER 002 005 X - - - -
- - - - - TRANS_REF char(10) Transaction Reference Mandatory
OH-TRANS-PREF 007 004 X - - - Transaction Ref. Prefix
OH-TRANS-SUFF 011 006 X - - - Transaction Ref. Suffix Mandatory
FILLER 017 005 X - - - -
OH-KEY-ID 022 001 X - HEADER_ID char(1) Alternate Key Id Mandatory, value

’H’
OH-CUSTOMER-CODE 023 010 X - CUST_CODE char(10) Address Code
OH-TRANS-DATE 033 005 N - TRANS_DATE int Transaction Date Mandatory, PIC

9(8) COMP-3
FILLER 038 013 X - - - -
- - - - - STATUS char(2) Status 1 & 2 See below
OH-STATUS-1 051 001 N 0 - - Status 1 Value may be:

0=Awaiting
Picking
3=Awaiting

Despatch
7=Awaiting
Invoice
8=Complete
OH-STATUS-2 052 001 N 0 - - Status 2 Value may be:

1=OrderHeld
else 0
OH-TRANS-CD 053 001 X - TRANS_CD char(1) Credit/Debit Mandatory, value

’C’ or ’D’
OH-TRANS-CODE 054 005 X - TRANS_CODE char(5) Transaction Type
FILLER 059 005 X - - - -
OH-ORDER-NO 064 010 X - ORDER_NO char(10) Order Number Mandatory
OH-D-NOTE-NO 074 015 X - D_NOTE_NO char(15) Delivery Note Number

Sales Order/Invoice Header record, see SOMFRC.CPY,SQL table name SOMFHDRddd – (continued)
TYPE
OH-DELIVERY-CODE 089 010 X - DELIV_ADD char(10) Delivery Address Code
OH-DATE-ORDER 099 008 N 0 ORDER_DATE int Order Date Mandatory
OH-DATE-ACKNOWLEDGED 107 008 N 0 ACK_DATE int Acknowledgement Date
OH-DATE-PICKED 115 008 N 0 PICK_DATE int Picking Date
OH-DATE-DELIVERED 123 008 N 0 DEL_DATE int Delivery Date
OH-DATE-INVOICED 131 008 N 0 INV_DATE int Invoice Date
OH-PERIOD-INVOICED 139 007 N 0 INV_PRD int Invoice Period
OH-CUSTOMER-REF 146 025 X - CUST_REF char(25) Customer Reference
OH-COMMENTS 171 025 X - COMMENTS char(25) Comments
OH-TRANS-VALUE 196 010 S 5 TRANS_VAL numeric Transaction Value PICS 9(13)

V99999 COMP-3
OH-PAYMENT-DUE-DATE 206 008 X - PAY_DATE char(8) Payment Due Date May be relative
date e.g.+12
OH-ANALYSIS-ADDRESS 214 001 X - ANAL_ADD char(1) Address Analysis
OH-LINKED-TEXT 215 001 X - LINKED_TEXT char(1) Linked Text Flag
OH-ANALYSIS-CODE-0 216 015 X - ANAL_M0 char(15) Analysis Code 0

OH-QUOTE-CONVERT 366 001 X - QUOTE_CONVERT char(1) Convert Quote
OH-QUOTE-PRINT 367 001 X - QUOTE_PRINT char(1) Print Quote
OH-QUOTE-EXPIRY-DATE 368 008 N 0 QUOTE_EXPIRY_DATE int Quote Expiry Date

Sales Order/Invoice Header record, see SOMFRC.CPY,SQL table name SOMFHDRddd – (continued)
TYPE
OH-PERIOD-QUOTED 376 007 N 0 PERIOD_QUOTED int Period Quoted
FILLER 383 005 X - - - -
OH-QUOTATION-REF 388 010 X - QUOTATION_REF char(10) Quotation Reference
OH-DATE-QUOTED 398 008 N 0 DATE_QUOTED int Quotation Date
OH-VOID-STATUS 406 001 X VOID_STATUS char(1) Values 0, 1 or 2
OH-EXTRA-CUST-CODE1 407 010 X EX_CUST_CODE_1 char(10) Sales Order Header;

Additional Data
OH-EXTRA-CUST-CODE2 417 010 X EX_CUST_CODE_2 char(10) Sales Order Header;

Additional Data
OH-EXTRA-TEXT1 427 030 X EX_TEXT1 char(30) Sales

OH-EXTRA-VALUE1 552 010 S EX_VAL1 Numeric Sales
FILLER 582 443 -

Sales Order/Invoice Detail record, see SOMFRC.CPY, SQL table name SOMFDETddd
TYPE
SD-TRANS-TYPE 001 001 X REC_TYPE char(1) Record Type Mandatory, value

’D’
FILLER 002 005 X - - -
- - - - - TRANS_REF char(10) Transaction Reference Mandatory
SD-TRANS-PREF 007 004 X - - - Transaction Ref. Prefix
SD-TRANS-SUFF 011 006 X - - - Transaction Ref. Suffix Mandatory
- - - - - TRANS_LINE char(5) Transaction line Number Mandatory
SD-TRANS-LINE-NUMBER 017 003 N - - - Transaction Line No. Prefix Mandatory
SD-TRANS-LINE-SUFF 020 002 X - - - Transaction Line No. Suffix Value ’A’ to ’Z’ for
descriptive lines
else Space or
numeric
SD-KEY-ID 022 001 X - DETAIL_ID char(1) Alternate Key Id Value ’D’ for
Detail record or
’A’ for Descriptive
record
SD-LOCATION 023 005 X - LOCATION char(5) Location Code
SD-ITEM-CODE 028 015 X - ITEM_CODE char(15) Item Code
SD-TRANS-DATE 043 005 N - DUE_DATE int Transaction Date PIC 9(8) COMP-3

SD-SEQUENCE 048 003 N - - - - PIC 9(4) COMP-3.
- - - - - STATUS char (2) Status 1 & 2 See below
SD-STATUS-1 051 001 N - - - Status 1 Value may be:

0=Awaiting
Picking
1=Picked but no
stock
3=Awaiting
Despatch
7=Awaiting
Invoice
8=Complete

Sales Order/Invoice Detail record, see SOMFRC.CPY, SQL table name SOMFDETddd – (continued)
TYPE
SD-STATUS-2 052 001 N - - - Status 2 Value may be:

0=Process
complete
5=Allocated
balance updated
6=Picked
SD-TRANS-CD 053 001 X - TRANS_CD char(1) Creditor Debit Mandatory, value

’C’ or ’D’
SD-ITEM-DESCRIPTION 054 030 X - DESCRIPTN char(30) Item Description
SD-VALUE-1 084 010 S - VALUE_1 numeric Value of Calculation Code PICS 9(13) V9(5)
COMP-3
SD-VALUE-2 094 010 S - VALUE_2 numeric Value of Calculation Code 2 PICS 9(13) V9(5)
COMP-3
COMP-3
COMP-3
COMP-3
COMP-3

COMP-3
COMP-3
PICS 9(13) V9(5)
COMP.
10 PICS 9(13) V9(5)
COMP.

TYPE
11 PICS 9(13) V9(5)
COMP.
12 PICS 9(13) V9(5)
COMP.
13 PICS 9(13) V9(5)
COMP.
14 PICS 9(13) V9(5)
COMP.
15 PICS 9(13) V9(5)
COMP.
16 PICS 9(13) V9(5)
COMP.
17 PICS 9(13) V9(5)
COMP.

18 PICS 9(13) V9(5)
COMP.
19 PICS 9(13) V9(5)
COMP.
20 PICS 9(13) V9(5)
COMP.

TYPE
SD-TRANS-CODE 284 005 X - TRANS_TYPE char(5) Transaction Type
SD-DATE-DELIVERED 289 008 N - DEL_DATE int Delivery Date
SD-DATE-INVOICED 297 008 N - INV_DATE int Invoice date
SD-PERIOD-ORDERED 305 007 N - ORD_PRD int Period Ordered
SD-PERIOD-INVOICED 312 007 N - INV_PRD int Period Invoiced
SD-UNIT-SALE 319 005 X - UNIT_SALE char(5) Unit of Sale Code
FILLER 324 005 X - - - -
SD-INVOICE-NO 329 010 X - INV_NO char(10) Invoice Number
SD-ACK-PRINT 339 001 X - ACK_PRINT char(1) Acknowledgement Print

Indic’r
SD-MISC-PRINT 340 001 X - MISC_PRINT char(1) Miscellaneous Print Indicator
SD-ALLOCATION-REF 341 019 X - ALLOC_REF char(19) Allocation Reference
SD-RECPT-REF 360 015 X - RECPT_REF char(15) Receipt Reference
SD-LINE-ANAL-IND 375 001 X - LINE_ANAL char(1) Analysis by Line
SD-ACCOUNT-CODE 376 015 X - ACCNT_CODE char(15) Account Code
SD-ASSET-CODE 391 010 X - ASSET_CODE char(10) Asset Code

SD-ASSET-SUB-CODE 401 005 X - ASS_SUB_CODE char(5) Asset Sub-Code
SD-ASSET-IND 406 001 X - ASSET_IND char(1) Asset Marker
SD-ID-ENTERED 407 003 X - ID_ENTERED char(3) Entered Id
SD-ID-INVOICED 410 003 X - ID_INVOICED char(3) Invoiced Id
SD-LINKED-TEXT 413 001 X - LINKED_TEXT char(1) Linked Text Flag
SD-ANALYSIS-CODE-0 414 015 X - ANAL_M0 char(15) Analysis Code 1

TYPE
SD-ASSEMBLY-IND 564 001 X - ASSEMBLY_IND char(1) Assembly Indicators
SD-ASSEMBLY-DESC-IND 565 001 X - ASSEMBLY_DESC char(1) Assembly Description Line
SD-ASSEMBLY-LEVEL-IND 566 001 X - ASSEMBLY_LEVEL char(1) Assembly Level Indicator
SD-PRICE-BOOK 567 005 X - PRICE_BOOK char(5) Name of price book
SD-SALES-QTY-VALUE 572 002 N - SALE_QTY_VALUE int (2) Pointer to Sales Quantity

Value
SD-STOCK-QTY-VALUE 574 002 N - STK_QTY_VALUE int (2) Pointer to Stock Quantity

Value
SD-TOTAL-VALUE 576 002 N - TOT_VALUE int (2) Pointer to Credit Balance

Value
SD-DISPLAY-VALUE-1 578 002 N - DISP_VAL_1 int (2) Pointer to display value 1
SD-DISPLAY-VALUE-2 580 002 N - DISP_VAL_2 int (2) Pointer to display value 2
SD-DISPLAY-VALUE-3 582 002 N - DISP_VAL_3 int( 2) Pointer to display value 3

SD-MISC-DOC-PRINT 584 005 X - MISC_DOC_PRINT_1 char(1) Miscellaneous reprint flags

the table size is 1 bytes by 5
- - - - - MISC_DOC_PRINT_2 char(1) -
SD-D-NOTE-NO 589 010 X - D_NOTE_NO char(10) Despatch Note Number
SD-AUDIT-DATE 599 005 S - AUDIT_DATE int Audit Date
FILLER 604 401 - - - - -

Movement file
Description
The movement file holds the current inventory movements that have been posted into
SunBusiness Inventory Control.
There are the following types of record on the movement file:

 control record
 movement record
 summary record.
There is one control record (type ‘C’) per file: there is one movement (type ‘M’) record for
each movement line posted in Movement Entry or Movement Import, or through Sales or
Purchase Order Processing. There is one summary or usage (type ‘S’) record for every
balance created by the Inventory Control Period Cleardown. When the movement file is
first created, by using the File Create function, if Serial Number Tracking is set on the
Business Definition for that database, then a serial number tracking file is also created.
This is a simple index file which holds information which links the item code and serial
number with the movement record on the movement file.
M FD MOVEMENT-FILE.
V *FD MOVEMENT-FILE VALUE OF ID IS MOVEMENT-FILE-NAME.
01 MOVEMENT-RECORD.
03 MOVEMENT-KEY PIC X(20).
03 MOVEMENT-ALTERNATE-KEY.
05 MOVEMENT-ALTERNATE-KEY-ID PIC X(01).
05 MOVEMENT-ITEM-CODE PIC X(15).
03 MOVEMENT-DATA.
05 MOVEMENT-RECPT-REF PIC X(15).
M FD SERIAL-TRACKING-FILE.
V *FD SERIAL-TRACKING-FILE VALUE OF ID IS
V * SERIAL-TRACKING-FILE-NAME.
01 SERIAL-TRACKING-RECORD.
03 SERIAL-TRACKING-KEY.
05 SERIAL-ITEM-CODE PIC X(15).
05 SERIAL-RECPT-REF PIC X(15).
* Serial Number
03 SERIAL-TRACKING-DATA PIC X(20).
* Primary key of Movement File
The physical record length of the movement file is on disk (450 bytes) less than the logical
record length within the programs (1024 bytes):
Physical Record
Primary Key 20

Alternate Key 29
Data 401
____
Total Physical 450

Filler 574
____
Total Logical 1024

Movement File record descriptions
Control record, see SMMFRC.CPY,SQL table name SMMFMSC
TYPE
MC-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’C’
MC-CONTROL 002 019 X - - - - Always set to

LOW-VALUES
MC-KEY-ID 021 001 X - - - Alternate Key Id Mandatory, value

’C’
FILLER 022 028 X - - - -
MC-VERSION 050 003 N - VERSION char(3) Version Mandatory, value

420
MC-HIGHEST-BATCH 053 005 N - HIGH_BATCH char(5) Highest Batch Number
MC-HIGHEST-USAGE 058 009 N - HIGH_USAGE char(9) Highest Usage Number
MC-LANGUAGE 067 003 X - LANGUAGE_CODE char(3) - Not used at

version 4.2
FILLER 070 731 X - - - -
FILLER 801 224 X - - - -

Movement/Summary record, see SMMFRC.CPY,SQL table name SMMFMOVddd
TYPE
MM-REC-TYPE 001 001 X - REC_TYPE char(1) Record Type Mandatory,

value ’M’ for
Movement
S’ for Summary
If record type is ’M’: -
MM-MVT-REF 002 015 X - MVMNT_REF char(15) Movement Reference Mandatory
MM-MVT-LINE-NO 017 004 N - MVMNT_LINE char(4) Movement Line No. Mandatory
Else if record type is ’S’: -
MM-PERIOD 002 007 N - - - Period Summarised
MM-USAGE-NUMBER 009 009 N - - - Usage Number
MM-EXTRA-USAGE-CHAR 018 001 X - - - Extra Usage Char.
FILLER 019 002 X - - - -
MM-KEY-ID 021 001 X - MM_KEY_ID char(1) Alternate Key Id Mandatory, value

’D’
MM-LOCATION 022 005 X - LOCATION char(5) Location Code Mandatory, may

be spaces
MM-ITEM-CODE 027 015 X - ITEM_CODE char(15) Item Code Mandatory
MM-MVT-DATE 042 005 N - MVMNT_DATE int Movement Date PIC 9(8) COMP-3

MM-SEQUENCE 047 003 N - SEQUENCE int Minutes since midnight PIC 9(4) COMP-3
- - - - STATUS char(2) Status 1 & 2 See below
MM-STATUS-1 050 001 N - - - Status 1 0=Awaiting

movement
Document
8=Complete
MM-STATUS-2 051 001 N - - - Status 2 0=Process

Complete
3=Reserved
(Receipts only)
5=Awaiting
allocation
MM-RI-IND 052 001 X - RI_IND char(1) Receipt/Issue Indicator ’R’ for Receipt,
‘I’ for Issue
MM-BATCH-NO 053 005 N - BATCH_NO char(5) Batch Number

Movement/Summary record, see SMMFRC.CPY,SQL table name SMMFMOVddd – (continued)
TYPE
MM-BATCH-LINE-NO 058 005 N - BATCH_LINE char 5) Batch Line Number
MM-RECPT-REF 063 015 X - RECPT_REF char(15) Receipt Reference
MM-MVT-QTY 078 010 S - QUANTITY numeric Quantity PICS 9(13)

V99999 COMP-3
MM-VALUE-1 088 010 S - STD_VALUE numeric Value 1 as on Movement PICS 9(13)

Value Definition V99999 COMP-3
MM-VALUE-2 098 010 S - LAT_VALUE numeric Value 2 as on Movement PICS 9(13)

MM-VALUE-3 108 010 S - AVE_VALUE numeric Value 3 as on Movement PICS 9(13)

FILLER 118 001 X - - - -
MM-PERIOD-POSTED 119 007 N - PERIOD int Period Posted
MM-UNIT-STOCK 126 005 X - UNITS char(5) Unit of Stock
MM-MVT-CODE 131 005 X - MVMNT_TYPE char(5) Movement Type
MM-UPDATE-PHYSICAL 136 001 X - UPDTE_PHYS char(1) Update Physical Stock
MM-UPDATE-ON-ORDER 137 001 X - UPDTE_ORDR char(1) Update On-order Balance
MM-ALLOCATION-REF 138 020 X - ALLOC_REF char(20) Allocation Reference

MM-AUDIT-DATE 158 005 N - AUDIT_DATE int Audit Date PIC 9(8) COMP-3
MM-SERIAL-NO-INDEX 163 001 X - SERIAL_IDX char(1) Serial Number
MM-LINKED-TEXT 164 001 X - LINKED_TEXT char(1) Linked Text Flag
MM-ID-ENTERED 165 003 X - ID_ENTERED char(3) User Id
MM-ID-ALLOCATED 168 003 X - ID_ALLOC char(3) Allocated Id
MM-ACCOUNT-CODE 171 015 X - ACCNT_CODE char(15) Account Code
MM-ASSET-CODE 186 010 X - ASSET_CODE char(10) Asset Code
MM-ASSET-SUB-CODE 196 005 X - ASSET_SUB char(5) Asset Sub-Code
MM-ANALYSIS-CODE-0 201 015 X - ANAL_M0 char(15) Analysis Code 0

Movement/Summary record, see SMMFRC.CPY,SQL table name SMMFMOVddd – (continued)
TYPE
MM-PO-LINE-NO-A 351 003 N - ORIG_LINE_NO char(4) Original PO number
MM-PO-LINE-NO-B 354 001 X - - - Original PO Value
MM-PO-VALUE 355 010 S - PO_VALUE numeric - PICS 9(13) V9(5)

COMP-3.
FILLER 365 436 X - - - -
FILLER 801 224 X - - - -

Stock take file

Description
The stock take file holds the current stock take information, that is, values of stock by item
code and location. Also stored here are the new values of stock calculated when a stock
check is run, and the differences found.
There are the following types of record on the stock take file:
 control record
 header record
 detail record.
There is one control record (type ‘C’) per file: there is one header (type ‘H’) record per
stock take run, and there is one detail (type ‘D’) record per item being stock checked.
M FD STOCK-TAKE-FILE.
V *FD STOCK-TAKE-FILE VALUE OF ID IS STOCK-TAKE-FILE-
NAME.
01STOCK-TAKE-RECORD.
03 STOCK-KEY PIC X(056).
03 STOCK-ALT-KEY PIC X(021).
03 STOCK-DATA PIC X(473).
The physical record length of the stock take file is on disk (550 bytes) less than the logical
record length within the programs (1024 bytes):
Physical Record
Primary Key 56
Alternate Key 21
Data 473
____
Total Physical 550

Filler 474
____
Total Logical 1024

Stock Take File record descriptions
Control record, see SMTFRC.CPY,SQL table name SMKFMSC
TYPE
TC-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’C’
FILLER 002 055 X - - - - Always set to all

’0’
TC-KEY-ID 057 001 X - - - Alternate Key Id Mandatory, value

’C’
FILLER 058 020 X - - - -
TC-VERSION-NO 078 003 N - TC_VERSION char(3) Version Mandatory, value

420
TC-NEXT-STOCK-TAKE-NO 081 005 N - NEXT_STOCK_TAKE_N char(5) Next Stock Take Number

O
FILLER 086 715 X - - - -
FILLER 801 224 X - - - -

Control record, see SMTFRC.CPY,SQL table name SMKFMSC
TYPE
TC-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’C’
FILLER 002 055 X - - - - Always set to all

’0’
TC-KEY-ID 057 001 X - - - Alternate Key Id Mandatory, value

’C’
FILLER 058 020 X - - - -
TC-VERSION-NO 078 003 N - TC_VERSION char(3) Version Mandatory, value

420
TC-NEXT-STOCK-TAKE-NO 081 005 N - NEXT_STOCK_TAKE_N char(5) Next Stock Take Number

O
FILLER 086 715 X - - - -
FILLER 801 224 X - - - -

Stock Take Header record, see SMTFRC.CPY,SQL table name SMKFHDRddd
TYPE
TH-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’H’
TH-STOCK-TAKE-NO 002 005 N - STOCK_TAKE_NO char(5) Stock Take Number Mandatory
FILLER 007 050 X - - - -
TH-KEY-ID 057 001 X - - - Alternate Key Id Mandatory, value

’H’
FILLER 058 020 X - - - -
TH-PERIOD-EXTRACTED 078 007 N - PERIOD_EXTRACTED int Period Extracted
TH-STOCK-TAKE-CODE 085 005 X - STOCK_TAKE_CODE char(5) Stock Take Code
TH-STOCK-TAKE-SEQ 090 004 X - STOCK_TAKE_SEQ char(4) Stock Take Sequence Internally

generated no.
TH-OPERATOR-ID 094 003 X - OPERATOR_ID char (3) Operator Id
TH-STOCK-TAKE-DATE 097 005 N - STOCK_TAKE_DATE int Stock Take Date Mandatory, PIC
9(8) COMP-3
TH-ANALYSIS-CATEGORY 102 002 X - ANALYSIS_CATEGORY char 2) Analysis Category
FILLER 104 697 X - - - -
FILLER 801 224 X - - - -

Stock Take Detail record, see SMTFRC.CPY,SQL table name SMKFDETddd
TYPE
TD-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’D’
TD-STOCK-TAKE-NO 002 005 N - STOCK_TAKE_NO char(5) Stock Take Number Mandatory
TD-COMPOSITE-KEY 007 050 X - COMPOSITE_KEY char(50) Composite data fields
TD-KEY-ID 057 001 X - - - Alternate Key Id Mandatory, value

’D’
TD-ITEM-CODE 058 015 X - ITEM_CODE char(15) Item Code
TD-LOCATION-CODE 073 005 X - LOCATION_CODE char(5) Location Code
TD-ANALYSIS-CODE 078 015 X - ANALYSIS_CODE char(15) Analysis Code
TD-STOCK-TAKE-CODE 093 005 X - STOCK_TAKE_CODE char(5) Stock Take Code
TD-STOCK-TAKE-LINE-NO 098 004 N - STOCK_TAKE_LINE_N char(4) Stock Take Line Number

O
TD-RECEIPT-REFERENCE 102 015 X - RECEIPT_REFERENCE char(15) Receipt Reference
TD-OPERATOR-ENTER 117 003 X - OPERATOR_ENTER char(3) Not used at version 4.2
TD-OPERATOR-APPROVED 120 003 X - OPERATOR_APPROVE char(3) Not used at version 4.2

D
TD-OPERATOR-POSTED 123 003 X - OPERATOR_POSTED char(3) Not used at version 4.2

TD-PERIOD-POSTED 126 007 N - PERIOD_POSTED int Period Posted
TD-ORIGINAL-QTY 133 010 S - ORIGINAL_QTY numeric Original Quantity PICS 9(13)

V99999 COMP-3
TD-ORIGINAL-VALUE-1 143 010 S - ORIGINAL_VALUE_1 numeric Original Value 1 PICS 9(13)

V99999 COMP-3

V99999 COMP-3

V99999 COMP-3
TD-VARIANCE-QTY 173 010 S - VARIANCE_QTY numeric Variance Quantity PICS 9(13)

V99999 COMP-3
TD-VARIANCE-VALUE-1 183 010 S - VARIANCE_VALUE_1 numeric Variance Value 1 PICS 9(13)

V99999 COMP-3

V99999 COMP-3

Stock Take Detail record, see SMTFRC.CPY,SQL table name SMKFDETddd – (continued)
TYPE

V99999 COMP-3
TD-REPORT-COST 213 003 X - REPORT_COST char(3) Report Cost
TD-UNIT-OF-STOCK 216 005 X - UNIT_OF_STOCK char(5) Unit of Stock
TD-MOVEMENT-CODE 221 005 X - MOVEMENT_CODE char(5) Movement Code
TD-UPDATE-PHYSICAL 226 001 X - UPDATE_PHYSICAL char (1) Update Physical Balance
TD-UPDATE-ON-ORDER 227 001 X - UPDATE_ON_ORDER char(1) Update On-order Balance
TD-AUDIT-DATE 228 005 N - AUDIT_DATE int Audit Date PIC 9(8) COMP-3
TD-ACCOUNT-CODE 233 015 X - ACCOUNT_CODE char(15) Account Code
TD-ASSET-CODE 248 010 X - ASSET_CODE char(10) Asset Code
TD-ASSET-SUB-CODE 258 005 X - ASSET_SUB_CODE char(5) Asset Sub-Code
TD-STATUS 263 001 X - STATUS char(1) Status
Value may be: -
TD-CLEAR-ON-ORDER 264 001 X - CLEAR_ON_ORDER char(1) Clear On-order Balance
TD-CNV-RATE-2 265 010 N - CNV_RATE_2 numeric Conversion Rate 2 PIC 9(9) V9(9)
COMP-3

TD-CNV-RATE-OP2 275 001 X - CNV_RATE_OP2 char(1) Conversion 2 Operator ’*’ or

’/’
TD-CNV-OTHER-DP2 276 001 X - CNV_OTHER_DP2 char(1) Conversion 2 No. d.p.
TD-CNV-RATE-3 277 010 N - CNV_RATE_3 numeric Conversion Rate 3 PIC 9(9) V9(9)
COMP-3
TD-CNV-RATE-OP3 287 001 X - CNV_RATE_OP3 char(1) Conversion 3 Operator ’*’ or

’/’
TD-CNV-OTHER-DP3 288 001 X - CNV_OTHER_DP3 char(1) Conversion 3 No. d.p.
TD-COST-1 289 010 S - COST_1 numeric Cost Value 1 PICS 9(13)

V99999 COMP-3

V99999 COMP-3

V99999 COMP-3
TD-MVT-ANALYSIS-CODE-0 319 015 X - ANAL_M0 char(15) Analysis Code 0

Stock Take Detail record, see SMTFRC.CPY,SQL table name SMKFDETddd – (continued)
TYPE
TD-BIN-NAME 469 015 X - BIN_NAME char(15) Bin Name
FILLER 484 317 X - - - -
FILLER 801 224 X - - - -

Purchase order file

Description
The purchase order file holds details of the current purchase orders, goods received
notes, and purchase invoices that have been entered into SunBusiness through the
Purchase Order Processing module.
There are the following types of record on the purchase order file:
 control record
 purchase order header record
 goods received note header record
 purchase invoice header record
 detail record.
There is one control record (type ‘C’) per file: there is one purchase order header (type ‘J’)
record per purchase order created in the purchase order entry function. A purchase order
header record is also created when entering purchase invoice for which the corresponding
order does not already exist. There is a goods received note (GRN) header (type ‘K’)
record for every GRN entered into the system. There is a purchase invoice header (type
‘L’) record per invoice entered into the system through purchase invoice entry or invoice
matching.
The detail (type ‘S’) records are shared by the various headers; a detail record exists for
every order/invoice/GRN line. M,O and P records are exact duplicates of the detail (type
‘S’) record layout. The details on the ‘M’ type record are created if there is any
amendments to the detail record between the order being issued and before the GRN
being approved and released, i.e. this shows that the details at order (issued). The ‘O’
type record is created if any amendment is made after the detail has been approved
(released) in GRN and before the unapproved stage in invoicing (matched, released), that
is, this shows the detail as it was at GRN approved release stage. Type ‘P’ is created
when there is an amendment to the detail record between the unapproved and approved
stages.
M FD POP-FILE.
V *FD POP-FILE VALUE OF ID IS POP-FILE-NAME.
01 POP-RECORD.
03 POP-KEY PIC X(020).
03 POP-ALTERNATE-KEY-1 PIC X(029).
03 POP-ALTERNATE-KEY-2 PIC X(016).
03 POP-DATA PIC X(635).
*
The physical record length of the purchase order file is on disk (700 bytes) less than the
logical record length within the programs (1024 bytes):
Physical Record
Primary Key 20
Alternate Key 1 29
Alternate Key 2 16
Data 635

____
Total Physical 700

Filler 324
____
Total Logical 1024

Purchase Order File record descriptions
Control record, see SPMFRC.CPY,SQL table name SPMFMSC
TYPE
SPMF-C-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’C’
SPMF-C-CONTROL 002 019 X - - - - Always set to

LOW-VALUES
SPMF-C-KEY-1-ID 021 001 X - - - Alternate Key 1 Id Mandatory, value

’C’
FILLER 022 028 X - - - -
SPMF-C-KEY-2-ID 050 001 X - - - Alternate Key 2 Id Mandatory, value

’C’
FILLER 051 015 - - - - -
SPMF-C-VERSION 066 003 N - VERSION char(3) Version Mandatory, value

420
SPMF-C-LAST-GRN-REF 069 015 N - LAST_GRN_REF char(15) Last GRN Reference
SPMF-C-LAST-INV-REF 084 015 N - LAST_INV_REF char(15) Last Invoice Reference
SPMF-C-LANGUAGE 099 003 X - LANGUAGE_CODE char(3) - Not used at

version 4.2

FILLER 102 599 - - - - -
FILLER 701 324 - - - - -

Purchase Order Header record, see SPMFRC.CPY,SQL table name SPMFORDddd
TYPE
SPMF-J-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’J’
FILLER 002 005 X - - - -
- - - - - ORDER_REF char(10) Order Reference Mandatory
SPMF-J-REF-PREFIX 007 004 X - - - Order Reference Prefix
SPMF-J-REF-SUFFIX 011 006 N - - - Order Reference Suffix Mandatory
FILLER 017 004 X - - - -
SPMF-J-KEY-1-ID 021 001 X - - - Alternate Key 1 Id Value Space
SPMF-J-SUPP-ADDRESS 022 010 X - SUPP_CODE char(10) Supplier Code Mandatory
SPMF-J-ORDER-DATE 032 005 N - ORDER_DATE int Order Date Mandatory, PIC

9(8) COMP-3
FILLER 037 013 X - - - -
SPMF-J-KEY-2-ID 050 001 X - - - Alternate Key 2 Id Mandatory, value

’J’
SPMF-J-SECOND-REF 051 015 X - SECOND_REF char(15) Second Reference SQL-not null
- - - - - STATUS char(2) Order Status 1&2 See below
SPMF-J-STATUS-1 066 001 N - - - Order Status 1 Value may be:

0=Held

3=Released
6=Issued
(Printed)
9=Dummy-
entered as
Invoice/
Receipt
SPMF-J-STATUS-2 067 001 N - - - Order Status 2 Always zero
SPMF-J-CD 068 001 X - ORDER_CD char(1) Credit/Debit Indicator Value ’C’ or ’D’
SPMF-J-TRANS-TYPE 069 005 X - TRANS_TYPE char (5) Purchase Order Type Mandatory
SPMF-J-DEL-ADDRESS 074 010 X - DEL_ADD char(10) Delivery Address Code
SPMF-J-COMMENTS 084 025 X - COMMENTS char(25) Comments
SPMF-J-ACK-REF 109 015 X - ACK_REF char(15) Acknowledgement

Reference

Purchase Order Header record, see SPMFRC.CPY,SQL table name SPMFORDddd – (continued)
TYPE
SPMF-J-ACK-DATE 124 005 N - ACK_DATE int Acknowledgement Date PIC 9(8) COMP-3
SPMF-J-DEL-DATE 129 005 N - DEL_DATE int Delivery Date PIC 9(8) COMP-3
SPMF-J-DEL-ADVISED 134 001 X - DEL_ADVISD char(1) Delivery Advised
SPMF-J-ORDER-VALUE 135 010 S - ORDER_VAL numeric Outstanding Order Value PICS 9(13)
V99999 COMP-3
SPMF-J-ORDER-QUANTITY 145 010 S - ORDER_QTY numeric Outstanding Order Qty PICS 9(13)
V99999 COMP-3
SPMF-J-ORDER-PERIOD 155 007 N - ORDER_PRD int Period Ordered
SPMF-J-LINKED-TEXT 162 001 X - LINK_TEXT char(1) Not used at version 4.2
SPMF-J-ANAL-CODE-0 163 015 X - ANAL_M0 char(15) Analysis Code 0

SPMF-J-DOC-ISSUE-DATE 313 005 N - ISSUE_DATE int Document Issue Date PIC 9(8) COMP-3
SPMF-J-GRN-IND 318 001 X - GRN_IND char(1) GRN Indicator
SPMF-J-ID-RELEASED 319 003 X - ID_RELEASED char(3) Release User Id
SPMF-J-POST-UNAPP-GRN 322 001 X - POST_UNAPP_GRN char(1) GRN Approval
FILLER 323 012 -
SPMF-J-VOID-STATUS 335 001 X - VOID_STATUS char(1) Values 0, 1 or 2
SPMF-J-EXTRA-CUST-CODE1 336 010 X - EX_CUST_CODE_1 char(10) Purchase Order Header;

Additional Data
SPMF-J-EXTRA-CUST-CODE2 346 010 X - EX_CUST_CODE_2 char(10) Purchase Order Header;

Additional Data

Purchase Order Header record, see SPMFRC.CPY,SQL table name SPMFORDddd – (continued)
TYPE
SPMF-J-EXTRA-TEXT1 356 030 X - EX_TEXT1 char(30) Purchase
SPMF-J-EXTRA-VALUE1 481 010 S - EX_VAL1 Numeric Purchase
SPMF-J-ORIG-ORDER-VALUE 511 010 S - ORIG_ORDER_VAL Numeric Purchase Order Original

value
FILLER 521 504 X -

Goods Received Note Header record, see SPMFRC.CPY, SQL table name SPMFGRNddd
TYPE
SPMF-K-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’K’
FILLER 002 005 X - - - -
- - - - - GRN_REF char(10) GRN Reference Mandatory
SPMF-K-REF-PREFIX 007 004 X - - - GRN Reference Prefix
SPMF-K-REF-SUFFIX 011 006 N - - - GRN Reference Suffix Mandatory
FILLER 017 004 X - - - -
SPMF-K-KEY-1-ID 021 001 X - - - Alternate Key 1 Id Value Space
SPMF-K-SUPP-ADDRESS 022 010 X - SUPP_ADDR char(10) Supplier Address Code Mandatory
SPMF-K-GRN-DATE 032 005 N - GRN_DATE int GRN Date Mandatory, PIC

9(8) COMP-3
FILLER 037 013 X - - - -
SPMF-K-KEY-2-ID 050 001 X - - - Alternate Key 2 Id Mandatory,

value’K’
SPMF-K-SUPP-GRN-REF 051 015 X - SUPP_GRN_REF char(15) Supplier’s GRN Ref. Mandatory
- - - - - STATUS char(2) GRN Status 1&2 Not used-value

zero

SPMF-K-STATUS-1 066 001 N - - - GRN Status 1 Not used-value

zero
SPMF-K-STATUS-2 067 001 N - - - GRN Status 2 Not used-value

zero
SPMF-K-LINKED-TEXT 068 001 X - LINK_TEXT char(1) Not used at version 4.2
SPMF-K-CD 069 001 X - INV_CD char(1) Credit/Debit Indicator Value ’C’ or ’D’
SPMF-K-DEL-ADDRESS 070 010 X - DEL_ADDR char(10) Delivery Address Code
FILLER 080 005 X - - - -
SPMF-K-ORDER-REFERENCE 085 010 X - ORDER_REF char(10) Order Reference Mandatory
SPMF-K-MATCHED-TOT-QTY 095 010 S - MATCH_QTY numeric GRN Quantity Matched PICS 9(13)
V99999 COMP-3
SPMF-K-GRN-TOT-QTY 105 010 S - GRN_QTY numeric GRN Total Quantity PICS 9(13)
V99999 COMP-3
SPMF-K-COMMENTS 115 025 X - COMMENTS char(25) Comments

Goods Received Note Header record, see SPMFRC.CPY, SQL table name SPMFGRNddd – (continued)
TYPE
SPMF-K-ORDER-TRANS-TYPE 140 005 X - TRANS_TYPE char(5) Purchase Order Type Mandatory
SPMF-K-ID-RELEASED 145 003 X - ID_RELEASED char(5) Release User Id
SPMF-K-PAY-DATE 148 005 N - PAY_DATE int Unapproved I/F Pay date PIC 9(8) COMP-3
SPMF-K-ORDER-DATE 153 005 N - ORDER_DATE int Order Date PIC 9(8) COMP-3
FILLER 158 177 - - - - -
SPMF-K-VOID-STATUS 335 001 X - VOID_STATUS char(1) Values 0, 1 or 2
SPMF-K-EXTRA-CUST-CODE1 336 010 X - EX_CUST_CODE_1 char(10) Purchase Order Header;

Additional Data
SPMF-K-EXTRA-CUST-CODE2 346 010 X - EX_CUST_CODE_2 char(10) Purchase Order Header;

Additional Data
SPMF-K-EXTRA-TEXT1 356 030 X - EX_TEXT1 char(30) Purchase

SPMF-K-EXTRA-VALUE1 481 010 S - EX_VAL1 Numeric Purchase
FILLER 511 514 - - - - -

Invoice Header record, see SPMFRC.CPY, SQL table name SPMFINVddd
TYPE
SPMF-L-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’L’
FILLER 002 005 X - - - -
- - - - - INV_REF char(10) Invoice Reference Mandatory
SPMF-L-REF-PREFIX 007 004 X - - - Invoice Ref. Prefix
SPMF-L-REF-SUFFIX 011 006 N - - - Invoice Ref. Suffix Mandatory
FILLER 017 004 X - - - -
SPMF-L-KEY-1-ID 021 001 X - - - Alternate Key 1 Id Value Space
SPMF-L-SUPP-ADDRESS 022 010 X - SUPP_CODE char(10) Supplier Address Code Mandatory
SPMF-L-INV-DATE 032 005 N - INV_DATE int Invoice Date Mandatory, PIC

9(8) COMP-3
FILLER 037 013 X - - - -
SPMF-L-KEY-2-ID 050 001 X - - - Alternate Key 2 Id Mandatory,

value’L’
SPMF-L-SUPP-INV-REF 051 015 X - SUPP_INV_REF char(15) Supplier’s Invoice Ref. Mandatory
- - - - - STATUS char(2) Invoice Status 1 & 2 Not used - value

zero

SPMF-L-STATUS-1 066 001 N - - - Invoice Status 1 Not used - value

zero
SPMF-L-STATUS-2 067 001 N - - - Invoice Status 2 Not used - value

zero
SPMF-L-CD 068 001 X - INV_CD char(1) Credit/Debit Indicator Value ’C’ or ’D’
SPMF-L-TRANS-TYPE 069 005 X - TRANS_TYPE char(5) Purchase Order Type Mandatory
FILLER 074 010 X - - - -
SPMF-L-COMMENTS 084 025 X - COMMENTS char(25) Comments
SPMF-L-PAY-DATE 109 005 N - PAY_DATE int Payment Date PIC 9(8) COMP-3
SPMF-L-MATCHED-TOT-QTY 114 010 S - MATCH_QTY numeric Total Matched Quantity PICS 9(13)
V99999 COMP-3
SPMF-L-MATCHED-TOT-VAL 124 010 S - MATCH_VAL numeric Total Matched Value PICS 9(13)
V99999 COMP-3
SPMF-L-INV-PERIOD 134 007 N - INV_PRD int Period Invoiced Mandatory

Invoice Header record, see SPMFRC.CPY, SQL table name SPMFINVddd – (continued)
TYPE
SPMF-L-INV-TOT-QTY 141 010 S - INV_QTY numeric Total Invoice Quantity PICS 9(13)
V99999 COMP-3
SPMF-L-INV-TOT-VAL 151 010 S - INV_VAL numeric Total Invoice Value PICS 9(13)
V99999 COMP-3
FILLER 161 005 X - - - -
SPMF-L-ORDER-REFERENCE 166 010 X - ORDER_REF char(10) Order Reference Mandatory
SPMF-L-LINKED-TEXT 176 001 X - LINK_TEXT char (1) Not used at version 4.2
SPMF-L-ANAL-CODE-0 177 015 X - ANAL_M0 char(15) Analysis Code 0

SPMF-L-ID-RELEASED 327 003 X - ID_RELEASED char(3) Release User Id
SPMF-L-ORDER-DATE 330 005 N - ORDER_DATE int Order Date PIC 9(8) COMP-3
SPMF-L-VOID-STATUS 335 001 X - VOID_STATUS char (1) Values 0, 1 or 2
SPMF-L-EXTRA-CUST-CODE1 336 010 X - EX_CUST_CODE_1 char(10) Purchase Order Header;

Additional Data
SPMF-L-EXTRA-CUST-CODE2 346 010 X - EX_CUST_CODE_2 char(10) Purchase Order Header;

Additional Data
SPMF-L-EXTRA-TEXT1 356 030 X - EX_TEXT1 char(30) Purchase

Invoice Header record, see SPMFRC.CPY, SQL table name SPMFINVddd – (continued)
TYPE
SPMF-L-EXTRA-VALUE1 481 010 S - EX_VAL1 Numeric Purchase
SPMF-L-EXTRA-VALUE2 491 010 S - EX_VAL2 Numeric Purchase
SPMF-L-EXTRA-VALUE3 501 010 S - EX_VAL3 Numeric Sales
FILLER 511 514 - - - - -

Order/Invoice Detail record, see SPMFRC.CPY, SQL table name SPMFDETddd
TYPE
SPMF-S-REC-TYPE 001 001 X - REC_TYPE char(1) Record Type Mandatory,

value’S’
FILLER 002 005 X - - - -
- - - - - TRANS_REF char(10) Order Reference Mandatory
SPMF-S-REF-PREFIX 007 004 X - - - Order Ref. Prefix
SPMF-S-REF-SUFFIX 011 006 N - - - Order Ref. Suffix Mandatory
- - - - - TRANS_LINE char(4) Transaction Line No. Mandatory, 1st 3

chars. numeric
SPMF-S-LINE-NO-A 017 003 N - - - Transaction Line No. A Mandatory
SPMF-S-LINE-NO-B 020 001 X - - - Transaction Line No. B
SPMF-S-KEY-1-ID 021 001 X - - - Alternate Key 1 Id Mandatory, value

Space
SPMF-S-LOCATION 022 005 X - LOCATION char(5) Location Code Mandatory
SPMF-S-ITEM-CODE 027 015 X - ITEM_CODE char(15) Item Code Mandatory
SPMF-S-DEL-DATE 042 005 N - DEL_DATE int Delivery Date Mandatory, PIC

9(8) COMP-3
SPMF-S-SEQUENCE 047 003 N - - - Sequence PIC 9(4) COMP-3

SPMF-S-KEY-2-ID 050 001 X - ITM_TYPE char(1) Alternate Key 2 Id Mandatory, value:

‘Q’ for Order
‘S’ for Invoice
FILLER 051 005 X - - - -
SPMF-S-HIGHEST-REFERENCE 056 010 X - HIGH_REF char(10) Highest Reference May be Order,

GRN, or Invoice
Reference
- - - - - ORD_STATUS char(2) Order Status 1 & 2 See below
SPMF-S-ORDER-STATUS-1 066 001 N - - - Order Status 1 Value may be:

0=Held/ Released
6=Issued
(Printed)
9=Dummy -
Invoice/ Receipt
entry

Order/Invoice Detail record, see SPMFRC.CPY, SQL table name SPMFDETddd – (continued)
TYPE
SPMF-S-ORDER-STATUS-2 067 001 N - - - Order Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
- - - - - GRN_STATUS char(2) GRN Status 1 & 2 See below
SPMF-S-GRN-STATUS-1 068 001 N - - - GRN Status 1 Value may be:

0=Awaited
1=Matched (Held)
2=Matched
(Held), Approved
(Held)
3=Matched
(Released)
4=Matched
(Released),
Approved (Held)
5=Matched
(Released),
Approved
(Released)
9=No Goods
Expected
SPMF-S-GRN-STATUS-2 069 001 N - - - GRN Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
4=Over-delivered

- - - - - INV_STATUS char(2) Invoice Status 1 & 2 See below

TYPE
SPMF-S-INVOICE-STATUS-1 070 001 N - - - Invoice Status 1 Value may be:

0=Awaited
1=Matched (Held)
2=Matched
(Held), Approved
(Held)
3=Matched
(Released)
4=Matched
(Released),
Approved (Held)
5=Matched
(Released),
Approved
(Released)
SPMF-S-INVOICE-STATUS-2 071 001 N - - - Invoice Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
SPMF-S-CD 072 001 X - TRANS_CD char(1) Credit/Debit Indicator Value ’C’ or ’D’
SPMF-S-LINKED-TEXT 073 001 X - LINK_TEXT char(1) Not used at version 4.2
SPMF-S-ID-ORDER 074 003 X - ID_ORDER char(3) Order Id
SPMF-S-ID-GRN 077 003 X - ID_GRN char(3) User Id
SPMF-S-ID-INVOICED 080 003 X - ID_INV char(3) Invoice Id

SPMF-S-SUPP-ITEM-DESC 083 030 X - SUPP_DESCR char(30) Supplier Item Description
SPMF-S-SUPP-ITEM-CODE 113 015 X - SUPP_ITEM_CODE char(15) Supplier Item Code
SPMF-S-PURCH-QTY 128 010 S - PURCH_QTY numeric Purchase Quantity PICS 9(13)

V99999 COMP-3
SPMF-S-PURCH-UNIT 138 005 X - PURCH_UNIT char(5) Unit of Purchase
SPMF-S-STOCK-QTY 143 010 S - STOCK_QTY numeric Stock Quantity PICS 9(13)

V99999 COMP-3
SPMF-S-BASE-COST 153 010 S - BASE_COST numeric Base Purchase Cost PICS 9(13) V9(5)
COMP-3
SPMF-S-CALC-VALUE-1 163 010 S - VALUE_1 numeric Value of Calc’n Code 1 PICS 9(13)
V99999 COMP-3

TYPE
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3

V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
FILLER 333 020 X - - - -
SPMF-S-GRN-REFERENCE 353 010 X - GRN_REF char(10) GRN Reference

TYPE
SPMF-S-GRN-DATE 363 005 N - GRN_DATE int GRN Date PIC 9(8) COMP-3
SPMF-S-DEL-ADVISED 368 001 X - DEL_ADVISD char(1) Delivery Advised
SPMF-S-INV-DATE 369 005 N - INV_DATE int Invoice Date PIC 9(8) COMP-3
SPMF-S-INV-PERIOD 374 007 N - INV_PRD int Period Invoiced
SPMF-S-INV-APPROV-DATE 381 005 N - INV_APPR_DATE int Approval Date PIC 9(8) COMP-3
SPMF-S-TRANS-TYPE 386 005 X - TRANS_TYPE char(5) Purchase Order Type
SPMF-S-STOCK-UPDATED 391 001 X - STOCK_UPD char(1) Stock Updated Indicator
SPMF-S-REASON-CODE 392 001 X - REASON char(1) Reason Code
SPMF-S-LINE-VALUE 393 002 N - LINE_VAL char(2) Line value calc’n code no.
SPMF-S-MATCH-VALUE 395 002 N - MATCH_VAL char(2) Match value calc’n code no.
SPMF-S-COST-VALUE 397 002 N - COST_VAL char(2) Cost value calc’n code no.
SPMF-S-ACCOUNT-CODE 399 015 X - ACCNT_CODE char(15) Account Code
SPMF-S-ASSET-CODE 414 010 X - ASSET_CODE char(10) Asset Code
SPMF-S-ASSET-SUB-CODE 424 005 X - ASSET_SUB char(5) Asset Sub-Code
SPMF-S-ASSET-IND 429 001 X - ASSET_IND char(1) Asset Marker

SPMF-S-RECEIPT-REF 430 015 X - RECEIPT_REF char(15) Receipt Reference
SPMF-S-AUDIT-DATE 445 005 N - AUDIT_DATE int Audit Date PIC 9(8) COMP-3
SPMF-S-ANAL-CODE-0 450 015 X - ANAL_M0 char(15) Analysis Code 0

TYPE
SPMF-S-UNAPP-PERIOD- 600 007 N - UNAPP_PRD_POSTED int Unapproved Posting Date

POSTED
SPMF-S-ORDER-DATE 607 005 N - ORDER_DATE int Order Date PIC 9(8) COMP-3.
SPMF-S-STOCK-PERIOD- 612 007 N - STOCK_PRD_POSTED int Period SI posted

POSTED
SPMF-S-PERIOD-ORDERED 619 007 N - PERIOD_ORDERED int Period Ordered
SPMF-S-AMEND-DATE 626 005 N - AMEND_DATE int Amended Date PIC 9(8) COMP-3.
SPMF-S-ORIG-LINE-NO-A 631 003 N - ORIG_LINE_NO char(4) Original Line Number
SPMF-S-ORIG-LINE-NO-B 634 001 X -
SPMF-S-MVT-VALUE 635 010 9 - MOVEMENT_VALUE numeric Movement Value PICS 9(13) V9(5)
COMP-3.
SPMF-S-BCHECK-VALUE 645 002 N - BCHECK_VALUE int Budget Check
SPMF-S-EXPEND-CHECK-VALUE 647 002 N - EXP_CHECK_VALUE int Expenditure Check
SPMF-S-MISC-DOC-PRINT(1) 649 001 X - MISC_DOC_PRINT1 char(1)

SPMF-S-ACV-INVOICE1 654 010 X - ADD_COST_VOUCHER char(10)

1

2

31

41
FILLER 694 331 X - - -

SP42RC.CPY contains Order/GRN/Invoice Header, as in SPMFRC.CPY, plus the following:

Order Issue Stage record, see SP42RC.CPY SQL table name SPMFDTOddd
TYPE
SPMF-M-REC-TYPE 001 001 X - REC_TYPE char(1) Record Type Mandatory, value

’M’
FILLER 002 005 X - - - -
SPMF-M-REF-PREFIX 007 004 X - - - Order Ref. Prefix
SPMF-M-REF-SUFFIX 011 006 N - - - Order Ref. Suffix Mandatory

chars. numeric
SPMF-M-LINE-NO-A 017 003 N - - - Transaction Line No. A Mandatory
SPMF-M-LINE-NO-B 020 001 X - - - Transaction Line No. B
SPMF-M-KEY-1-ID 021 001 X - - - Alternate Key 1 Id Mandatory, value

Space
SPMF-M-LOCATION 022 005 X - LOCATION char(5) Location Code Mandatory
SPMF-M-ITEM-CODE 027 015 X - ITEM_CODE char(15) Item Code Mandatory
SPMF-M-DEL-DATE 042 005 N - DEL_DATE int Delivery Date Mandatory, PIC

9(8) COMP-3
SPMF-M-SEQUENCE 047 003 N - - - Sequence PIC 9(4) COMP-3

SPMF-M-KEY-2-ID 050 001 X - ITM_TYPE char(1) Alternate Key 2 Id Mandatory, value:

‘Q’ for Order
‘S’ for Invoice
FILLER 051 005 X - - - -
SPMF-M-HIGHEST-REFERENCE 056 010 X - HIGH_REF char(10) Highest Reference May be Order,

GRN, or Invoice
Reference

Order Issue Stage record, see SP42RC.CPY SQL table name SPMFDTOddd – (continued)
TYPE
SPMF-M-ORDER-STATUS-1 066 001 N - - - Order Status 1 Value may be:

0=Held/
Released
6=Issued
(Printed)
9=Dummy -
Invoice/
Receipt entry
SPMF-M-ORDER-STATUS-2 067 001 N - - - Order Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
SPMF-M-GRN-STATUS-1 068 001 N - - - GRN Status 1 Value may be:

0=Awaited
1=Matched (Held)
2=Matched
(Held), Approved
(Held)
3=Matched
(Released)
4=Matched
(Released),
Approved (Held)
5=Matched
(Released),
Approved
(Released)

9=No Goods
Expected
SPMF-M-GRN-STATUS-2 069 001 N - - - GRN Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
4=Over-delivered

TYPE
SPMF-M-INVOICE-STATUS-1 070 001 N - - - Invoice Status 1 Value may be:

0=Awaited
1=Matched (Held)
2=Matched
(Held), Approved
(Held)
3=Matched
(Released)
4=Matched
(Released),
Approved (Held)
5=Matched
(Released),
Approved
(Released)
SPMF-M-INVOICE-STATUS-2 071 001 N - - - Invoice Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
SPMF-M-CD 072 001 X - TRANS_CD char(1) Credit/Debit Indicator Value ’C’

or ’D’
SPMF-M-LINKED-TEXT 073 001 X - LINK_TEXT char(1) Not used at version 4.2
SPMF-M-ID-ORDER 074 003 X - ID_ORDER char(3) Order Id
SPMF-M-ID-GRN 077 003 X - ID_GRN char(3) User Id

SPMF-M-ID-INVOICED 080 003 X - ID_INV char(3) Invoice Id
SPMF-M-SUPP-ITEM-DESC 083 030 X - SUPP_DESCR char(30) Supplier Item Description
SPMF-M-SUPP-ITEM-CODE 113 015 X - SUPP_ITEM_CODE char(15) Supplier Item Code
SPMF-M-PURCH-QTY 128 010 S - PURCH_QTY numeric Purchase Quantity PICS 9(13)

V99999 COMP-3
SPMF-M-PURCH-UNIT 138 005 X - PURCH_UNIT char(5) Unit of Purchase
SPMF-M-STOCK-QTY 143 010 S - STOCK_QTY numeric Stock Quantity PICS 9(13)

V99999 COMP-3
SPMF-M-BASE-COST 153 010 S - BASE_COST numeric Base Purchase Cost PICS 9(13) V9(5)
COMP-3
SPMF-M-CALC-VALUE-1 163 010 S - VALUE_1 numeric Value of Calc’n Code 1 PICS 9(13)
V99999 COMP-3

COBO POS’N IN FIELD FIELD DEC. SQL COLUMN SQL DESCRIPTION COMMENT
TYPE
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3

V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
FILLER 333 020 X - - - -
SPMF-M-GRN-REFERENCE 353 010 X - GRN_REF char(10) GRN Reference

TYPE
SPMF-M-GRN-DATE 363 005 N - GRN_DATE int GRN Date PIC 9(8) COMP-3
SPMF-M-DEL-ADVISED 368 001 X - DEL_ADVISD char(1) Delivery Advised
SPMF-M-INV-DATE 369 005 N - INV_DATE int Invoice Date PIC 9(8) COMP-3
SPMF-M-INV-PERIOD 374 007 N - INV_PRD int Period Invoiced
SPMF-M-INV-APPROV-DATE 381 005 N - INV_APPR_DATE int Approval Date PIC 9(8) COMP-3
SPMF-M-TRANS-TYPE 386 005 X - TRANS_TYPE char(5) Purchase Order Type
SPMF-M-STOCK-UPDATED 391 001 X - STOCK_UPD char(1) Stock Updated Indicator
SPMF-M-REASON-CODE 392 001 X - REASON char(1) Reason Code
SPMF-M-LINE-VALUE 393 002 N - LINE_VAL char(2) Line value calc’n code no.
SPMF-M-MATCH-VALUE 395 002 N - MATCH_VAL char(2) Match value calc’n code no.
SPMF-M-COST-VALUE 397 002 N - COST_VAL char(2) Cost value calc’n code no.
SPMF-M-ACCOUNT-CODE 399 015 X - ACCNT_CODE char(15) Account Code
SPMF-M-ASSET-CODE 414 010 X - ASSET_CODE char(10) Asset Code
SPMF-M-ASSET-SUB-CODE 424 005 X - ASSET_SUB char(5) Asset Sub-Code
SPMF-M-ASSET-IND 429 001 X - ASSET_IND char(1) Asset Marker

SPMF-M-RECEIPT-REF 430 015 X - RECEIPT_REF char(15) Rece ipt Reference
SPMF-M-AUDIT-DATE 445 005 N - AUDIT_DATE int Audit Date PIC 9(8) COMP-3
SPMF-M-ANAL-CODE-0 450 015 X - ANAL_M0 char(15) Analysis Code 0

TYPE
SPMF-M-UNAPP-PERIOD- 600 007 N - UNAPP_PRD_POSTED int Unapproved Posting Date

POSTED
SPMF-M-ORDER-DATE 607 005 N - ORDER_DATE int Order Date PIC 9(8) COMP-3.
SPMF-M-STOCK-PERIOD- 612 007 N - STOCK_PRD_POSTED int Period SI posted

POSTED
SPMF-M-PERIOD-ORDERED 619 007 N - PERIOD_ORDERED int Period Ordered
SPMF-M-AMEND-DATE 626 005 N - AMEND_DATE int Amended Date PIC 9(8) COMP-3.
SPMF-M-ORIG-LINE-NO-A 631 003 N - ORIG_LINE_NUMBER char(4) Original Line Number
SPMF-M-ORIG-LINE-NO-B 634 001 X -
SPMF-M-MVT-VALUE 635 010 N - MOVEMENT_VALUE numeric Movement Value PICS 9(13) V9(5)
COMP-3.
SPMF-M-BCHECK-VALUE 645 002 N - BCHECK_VALUE int Budget Check
SPMF-M-EXPEND-CHECK-VALUE 647 002 N - EXP_CHECK_VALUE int Expenditure Check
SPMF-M-MISC-DOC-PRINT(1) 649 001 X - MISC_DOC_PRINT1 Char (1)

FILLER 654 371 X - - -

Goods Receipt Stage record, see SP42RC.CPY SQL table name SPMFDTGddd
TYPE
SPMF-O-REC-TYPE 001 001 X - REC_TYPE char(1) Record Type Mandatory, value

’O’
FILLER 002 005 X - - - -
SPMF-O-REF-PREFIX 007 004 X - - - Order Ref. Prefix
SPMF-O-REF-SUFFIX 011 006 N - - - Order Ref. Suffix Mandatory

chars. numeric
SPMF-O-LINE-NO-A 017 003 N - - - Transaction Line No. A Mandatory
SPMF-O-LINE-NO-B 020 001 X - - - Transaction Line No. B
SPMF-O-KEY-1-ID 021 001 X - - - Alternate Key 1 Id Mandatory, value

Space
SPMF-O-LOCATION 022 005 X - LOCATION char(5) Location Code Mandatory
SPMF-O-ITEM-CODE 027 015 X - ITEM_CODE char(15) Item Code Mandatory
SPMF-O-DEL-DATE 042 005 N - DEL_DATE int Delivery Date Mandatory, PIC

9(8) COMP-3
SPMF-O-SEQUENCE 047 003 N - - - Sequence PIC 9(4) COMP-3

SPMF-O-KEY-2-ID 050 001 X - ITM_TYPE char(1) Alternate Key 2 Id Mandatory, value:

‘Q’ for Order
‘S’ for Invoice
FILLER 051 005 X - - - -
SPMF-O-HIGHEST-REFERENCE 056 010 X - HIGH_REF char(10) Highest Reference May be Order,

GRN, or Invoice
Reference
SPMF-O-ORDER-STATUS-1 066 001 N - - - Order Status 1 Value may be:

0=Held/ Released
6=Issued
(Printed)
9=Dummy-
Invoice/ Receipt
entry

Goods Receipt Stage record, see SP42RC.CPY SQL table name SPMFDTGddd – (continued)
TYPE
SPMF-O-ORDER-STATUS-2 067 001 N - - - Order Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
SPMF-O-GRN-STATUS-1 068 001 N - - - GRN Status 1 Value may be:

0=Awaited
1=Matched (Held)
2=Matched
(Held), Approved
(Held)
3=Matched
(Released)
4=Matched
(Released),
Approved (Held)
5=Matched
(Released),
Approved
(Released)
9=No Goods
Expected
SPMF-O-GRN-STATUS-2 069 001 N - - - GRN Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
4=Over-delivered


TYPE
SPMF-O-INVOICE-STATUS-1 070 001 N - - - Invoice Status 1 Value may be:

0=Awaited
1=Matched (Held)
2=Matched
(Held), Approved
(Held)
3=Matched
(Released)
4=Matched
(Released),
Approved (Held)
5=Matched
(Released),
Approved
(Released)
SPMF-O-INVOICE-STATUS-2 071 001 N - - - Invoice Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
SPMF-O-CD 072 001 X - TRANS_CD char(1) Credit/Debit Indicator Value ’C’ or ’D’
SPMF-O-LINKED-TEXT 073 001 X - LINK_TEXT char(1) Not used at version 4.2
SPMF-O-ID-ORDER 074 003 X - ID_ORDER char(3) Order Id
SPMF-O-ID-GRN 077 003 X - ID_GRN char(3) User Id
SPMF-O-ID-INVOICED 080 003 X - ID_INV char (3) Invoice Id

SPMF-O-SUPP-ITEM-DESC 083 030 X - SUPP_DESCR char(30) Supplier Item Description
SPMF-O-SUPP-ITEM-CODE 113 015 X - SUPP_ITEM_CODE char(15) Supplier Item Code
SPMF-O-PURCH-QTY 128 010 S - PURCH_QTY numeric Purchase Quantity PICS 9(13)

V99999 COMP-3
SPMF-O-PURCH-UNIT 138 005 X - PURCH_UNIT char (5) Unit of Purchase
SPMF-O-STOCK-QTY 143 010 S - STOCK_QTY numeric Stock Quantity PICS 9(13)

V99999 COMP-3
SPMF-O-BASE-COST 153 010 S - BASE_COST numeric Base Purchase Cost PICS 9(13) V9(5)
COMP-3
SPMF-O-CALC-VALUE-1 163 010 S - VALUE_1 numeric Value of Calc’n Code 1 PICS 9(13)
V99999 COMP-3

TYPE
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3

V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
FILLER 333 020 X - - - -
SPMF-O-GRN-REFERENCE 353 010 X - GRN_REF char(10) GRN Reference

TYPE
SPMF-O-GRN-DATE 363 005 N - GRN_DATE int GRN Date PIC 9(8) COMP-3
SPMF-O-DEL-ADVISED 368 001 X - DEL_ADVISD char(1) Delivery Advised
SPMF-O-INV-DATE 369 005 N - INV_DATE int Invoice Date PIC 9(8) COMP-3
SPMF-O-INV-PERIOD 374 007 N - INV_PRD int Period Invoiced
SPMF-O-INV-APPROV-DATE 381 005 N - INV_APPR_DATE int Approval Date PIC 9(8) COMP-3
SPMF-O-TRANS-TYPE 386 005 X - TRANS_TYPE char(5) Purchase Order Type
SPMF-O-STOCK-UPDATED 391 001 X - STOCK_UPD char(1) Stock Updated Indicator
SPMF-O-REASON-CODE 392 001 X - REASON char(1) Reason Code
SPMF-O-LINE-VALUE 393 002 N - LINE_VAL char(2) Line value calc’n code no.
SPMF-O-MATCH-VALUE 395 002 N - MATCH_VAL char(2) Match value calc’n code no.
SPMF-O-COST-VALUE 397 002 N - COST_VAL char(2) Cost value calc’n code no.
SPMF-O-ACCOUNT-CODE 399 015 X - ACCNT_CODE char(15) Account Code
SPMF-O-ASSET-CODE 414 010 X - ASSET_CODE char(10) Asset Code
SPMF-O-ASSET-SUB-CODE 424 005 X - ASSET_SUB char(5) Asset Sub-Code
SPMF-O-ASSET-IND 429 001 X - ASSET_IND char(1) Asset Marker

SPMF-O-RECEIPT-REF 430 015 X - RECEIPT_REF char(15) Receipt Reference
SPMF-O-AUDIT-DATE 445 005 N - AUDIT_DATE int(4) Audit Date PIC 9(8) COMP-3
SPMF-O-ANAL-CODE-0 450 015 X - ANAL_M0 char(15) Analysis Code 0

TYPE
SPMF-O-UNAPP-PERIOD- 600 007 N - UNAPP_PRD_POST int Unapproved Posting Date

POSTED
SPMF-O-ORDER-DATE 607 005 N - ORDER_DATE int Order Date PIC 9(8) COMP-3.
SPMF-O-STOCK-PERIOD- 612 007 N - STOCK_PRD_POSTED int Period SI posted

POSTED
SPMF-O-PERIOD-ORDERED 619 007 N - PERIOD_ORDERED int Period Ordered
SPMF-O-AMEND-DATE 626 005 N - AMEND_DATE int Amended Date PIC9(8)COMP-3.
SPMF-O-ORIG-LINE-NO-A 631 003 N - ORIG_LINE_NUMBER char(4) Original Line Number
SPMF-O-ORIG-LINE-NO-B 634 001 X - - - -
SPMF-O-MVT-VALUE 635 010 N - MOVEMENT_VALUE numeric Movement Value PICS9(13)V9(5)C

OMP-3.
SPMF-O-BCHECK-VALUE 645 002 N - BCHECK_VALUE int Budget Check
SPMF-O-EXPEND-CHECK-VALUE 647 002 N - EXP_CHECK_VALUE int Expenditure Check
SPMF-O-MISC-DOC-PRINT(1) 649 001 X - MISC_DOC_PRINT1 char(1)

FILLER 654 371 X - - -

Unapproved Invoice Stage record, see SP42RC.CPY SQL table name SPMFDTIddd
TYPE
SPMF-P -REC-TYPE 001 001 X - REC_TYPE char(1) Record Type Mandatory, value
’P’
FILLER 002 005 X - - - -
SPMF-P-REF-PREFIX 007 004 X - - - Order Ref. Prefix
SPMF-P-REF-SUFFIX 011 006 N - - - Order Ref. Suffix Mandatory

chars. numeric
SPMF-P-LINE-NO-A 017 003 N - - - Transaction Line No. A Mandatory
SPMF-P-LINE-NO-B 020 001 X - - - Transaction Line No. B
SPMF-P-KEY-1-ID 021 001 X - - - Alternate Key 1 Id Mandatory, value

Space
SPMF-P-LOCATION 022 005 X - LOCATION char(5) Location Code Mandatory
SPMF-P-ITEM-CODE 027 015 X - ITEM_CODE char(15) Item Code Mandatory
SPMF-P-DEL-DATE 042 005 N - DEL_DATE int Delivery Date Mandatory, PIC

9(8) COMP-3
SPMF-P-SEQUENCE 047 003 N - - - Sequence PIC 9(4) COMP-3

SPMF-P-KEY-2-ID 050 001 X - ITM_TYPE char(1) Alternate Key 2 Id Mandatory, value:

‘Q’ for Order
‘S’ for Invoice
FILLER 051 005 X - - - -
SPMF-P-HIGHEST-REFERENCE 056 010 X - HIGH_REF char(10) Highest Reference May be Order,

GRN, or Invoice
Reference
SPMF-P-ORDER-STATUS-1 066 001 N - - - Order Status 1 Value may be:

0=Held/ Released
6=Issued
(Printed)
9=Dummy-
Invoice/ Receipt
entry

Unapproved Invoice Stage record, see SP42RC.CPY SQL table name SPMFDTIddd – (continued)
TYPE
SPMF-P-ORDER-STATUS-2 067 001 N - - - Order Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
SPMF-P-GRN-STATUS-1 068 001 N - - - GRN Status 1 Value may be:

0=Awaited
1=Matched (Held)
2=Matched
(Held), Approved
(Held)
3=Matched
(Released)
4=Matched
(Released),
Approved (Held)
5=Matched
(Released),
Approved
(Released)
9=No Goods
Expected
SPMF-P-GRN-STATUS-2 069 001 N - - - GRN Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
4=Over-delivered


TYPE
SPMF-P-INVOICE-STATUS-1 070 001 N - - - Invoice Status 1 Value may be:

0=Awaited
1=Matched (Held)
2=Matched
(Held), Approved
(Held)
3=Matched
(Released)
4=Matched
(Released),
Approved (Held)
5=Matched
(Released),
Approved
(Released)
SPMF-P-INVOICE-STATUS-2 071 001 N - - - Invoice Status 2 Value may be:

1=Cancelled
2=Undelivered
3=Rejected
SPMF-P-CD 072 001 X - TRANS_CD char(1) Credit/Debit Indicator Value ’C’ or ’D’
SPMF-P-LINKED-TEXT 073 001 X - LINK_TEXT char(1) Not used at version 4.2
SPMF-P-ID-ORDER 074 003 X - ID_ORDER char(3) Order Id
SPMF-P-ID-GRN 077 003 X - ID_GRN char(3) User Id
SPMF-P-ID-INVOICED 080 003 X - ID_INV char(3) Invoice Id

SPMF-P-SUPP-ITEM-DESC 083 030 X - SUPP_DESCR char(30) Supplier Item Description
SPMF-P-SUPP-ITEM-CODE 113 015 X - SUPP_ITEM_CODE char(15) Supplier Item Code
SPMF-P-PURCH-QTY 128 010 S - PURCH_QTY numeric Purchase Quantity PICS 9(13)

V99999 COMP-3
SPMF-P-PURCH-UNIT 138 005 X - PURCH_UNIT char(5) Unit of Purchase
SPMF-P-STOCK-QTY 143 010 S - STOCK_QTY numeric Stock Quantity PICS 9(13)

V99999 COMP-3
SPMF-P-BASE-COST 153 010 S - BASE_COST numeric Base Purchase Cost PICS 9(13) V9(5)
COMP-3

TYPE
SPMF-P-CALC-VALUE-1 163 010 S - VALUE_1 numeric Value of Calc’n Code 1 PICS 9(13)
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
SPMF -P-CALC-VALUE-6 213 010 S - VALUE_6 numeric Value of Calc’n Code 6 PICS 9(13)
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3

V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3

FILLER 333 020 X - - - -
SPMF-P-GRN-REFERENCE 353 010 X - GRN_REF char(10) GRN Reference
SPMF-P-GRN-DATE 363 005 N - GRN_DATE int GRN Date PIC 9(8) COMP-3
SPMF-P-DEL-ADVISED 368 001 X - DEL_ADVISD char(1) Delivery Advised
SPMF-P-INV-DATE 369 005 N - INV_DATE int Invoice Date PIC 9(8) COMP-3
SPMF-P-INV-PERIOD 374 007 N - INV_PRD int Period Invoiced
SPMF-P-INV-APPROV-DATE 381 005 N - INV_APPR_DATE int Approval Date PIC 9(8) COMP-3
SPMF-P-TRANS-TYPE 386 005 X - TRANS_TYPE char(5) Purchase Order Type
SPMF-P-STOCK-UPDATED 391 001 X - STOCK_UPD char(1) Stock Updated Indicator
SPMF-P-REASON-CODE 392 001 X - REASON char(1) Reason Code
SPMF-P-LINE-VALUE 393 002 N - LINE_VAL char(2) Line value calc’n code no.
SPMF-P-MATCH-VALUE 395 002 N - MATCH_VAL char(2) Match value calc’n code

no.
SPMF-P-COST-VALUE 397 002 N - COST_VAL char(2) Cost value calc’n code no.
SPMF-P-ACCOUNT-CODE 399 015 X - ACCNT_CODE char(15) Account Code
SPMF-P-ASSET-CODE 414 010 X - ASSET_CODE char(10) Asset Code

SPMF-O-ASSET-SUB-CODE 424 005 X - ASSET_SUB char(5) Asset Sub-Code
SPMF-O-ASSET-IND 429 001 X - ASSET_IND char(1) Asset Marker
SPMF-O-RECEIPT-REF 430 015 X - RECEIPT_REF char(15) Receipt Reference
SPMF-O-AUDIT-DATE 445 005 N - AUDIT_DATE int(4) Audit Date PIC 9(8) COMP-3

TYPE
SPMF-O-UNAPP-PERIOD- 600 007 N - UNAPP_PRD_POST int Unapproved Posting Date

POSTED
SPMF-O-ORDER-DATE 607 005 N - ORDER_DATE int Order Date PIC 9(8) COMP-3.
SPMF-O-STOCK-PERIOD- 612 007 N - STOCK_PRD_POSTED int Period SI posted

POSTED
SPMF-O-PERIOD-ORDERED 619 007 N - PERIOD_ORDERED int Period Ordered
SPMF-O-AMEND-DATE 626 005 N - AMEND_DATE int Amended Date PIC9(8)COMP-3.
SPMF-O-ORIG-LINE-NO-A 631 003 N - ORIG_LINE_NUMBER char(4) Original Line Number
SPMF-O-ORIG-LINE-NO-B 634 001 X - - - -
SPMF-O-MVT-VALUE 635 010 N - MOVEMENT_VALUE numeric Movement Value PICS9(13)V9(5)C

OMP-3.
SPMF-O-BCHECK-VALUE 645 002 N - BCHECK_VALUE int Budget Check
SPMF-O-EXPEND-CHECK-VALUE 647 002 N - EXP_CHECK_VALUE int Expenditure Check

FILLER 654 371 X - - -

Sales history file

Description
The sales history file holds a summary of completed sales orders and invoices that were
entered into SunBusiness through the Sales Order Processing module, and then cleared
down through Period Cleardown.
There are the following types of record on the sales order file:
 control record
 usage record.
There is one control record (type ‘C’) per file; there is one usage (type ‘U’) record per item
been cleared down - this depends on the amount of consolidation being performed at the
cleardown.
M FD HISTORY-FILE.
V *FD HISTORY-FILE VALUE OF ID IS HISTORY-FILE-NAME.
MV COPY ‘SOHFRC.CPY’.
The record length is 1024 bytes.

Sales History file record descriptions
Control record, see SOHFRC.CPY, SQL table name SOHFMSC
TYPE
HC-TRANS-TYPE 001 001 X - - - Record Type Mandatory, value

’C’
HC-VERSION 002 003 N - VERSION char(3) Version Mandatory, value

420
FILLER 005 398 X - - - -
FILLER 403 098 X - - - -

Usage record, see SOHFRC.CPY, SQL table name SOHFOHFddd
TYPE
BD-TRANS-TYPE 001 001 X - - - Record Type Mandatory, value

’U’
BD-PERIOD 002 007 N - PERIOD int Period Mandatory
BD-LOCATION 009 005 X - LOCATION char(5) Location Code
BD-ITEM-CODE 014 015 X - ITEM_CODE char(15) Item Code
BD-TRANS-DATE 029 008 N - TRANS_DATE int Transaction Date
BD-TRANS-CD 037 001 X - TRANS_CD char(1) -
Not used - value zero
BD-VALUE-1 038 010 S - VALUE_1 numeric Value of Calc’n Code 1 PICS 9(13)
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3

V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3

Usage record, see SOHFRC.CPY, SQL table name SOHFOHFddd – (continued)
TYPE
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
BD-TRANS-CODE 238 005 X - TRANS_CODE char(5) Sales Order Type
BD-CUSTOMER-CODE 243 010 X - CUSTOMER_CODE char(10) Customer Address Code
BD-ANALYSIS-CODE-0 253 015 X - ANALYSIS_CODE_0 char(15) Analysis Code 0

FILLER 403 098 X - - - -

Purchase history file

Description
The purchase history file holds a summary of completed purchase orders and invoices
that were entered into SunBusiness through the Purchase Order Processing module, and
then cleared down through Period Cleardown.
There are the following types of record on the purchase order file:
 control record
 balance record.
There is one control record (type ‘C’) per file: there is one balance (type ‘S’) record per
item been cleared down - this depends on the amount of consolidation being performed at
the cleardown.
M FD HISTORY-FILE.
V *FD HISTORY-FILE VALUE OF ID IS HISTORY-FILE-NAME.
MV COPY “SPHFRC.CPY”.
The record length is 1024 bytes.

Purchase History file record descriptions
Control record, see SPHFRC.CPY, SQL table name SPHFMSC
TYPE
SPHF-C-REC-TYPE 001 001 X - - - Record Type Mandatory,

value’C’
SPHF-C-VERSION 002 003 N - VERSION char(3) Version Mandatory, value

420
FILLER 005 496 X - - - -

Balance record, see SPHFRC.CPY, SQL table name SPHFPHFddd
TYPE
SPHF-S-REC-TYPE 001 001 X - - - Record Type Mandatory, value

’S’
SPHF-S-INV-PERIOD 002 007 N - INV_PERIOD int Period Invoiced
SPHF-S-LOCATION 009 005 X - LOCATION char(5) Location Code
SPHF-S-ITEM-CODE 014 015 X - ITEM_CODE char(15) Item Code
SPHF-S-DEL-DATE 029 005 N - DEL_DATE int Delivery Date PIC 9(8) COMP-3
SPHF-S-CD 034 001 X - CD char(1) Credit/Debit Indicator Value ’C’ or ’D’
SPHF-S-PURCH-QTY 035 010 S - PURCH_QTY numeric Purchase Quantity PICS 9(13)

V99999 COMP-3
SPHF-S-STOCK-QTY 045 010 S - STOCK_QTY numeric Stock Quantity PICS 9(13)

V99999 COMP-3
SPHF-S-CALC-VALUE-1 055 010 S - CALC_VALUE_1 numeric Value of Calc’n Code 1 PICS 9(13)
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3

V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3

Balance record, see SPHFRC.CPY, SQL table name SPHFPHFddd – (continued)
TYPE
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
V99999 COMP-3
SPHF-S-TRANS-TYPE 225 005 X - TRANS_TYPE char(5) Purchase Order Type
SPHF-S-SUPPLIER-CODE 230 010 X - SUPPLIER_CODE char(10) Supplier Address Code
SPHF-S-REASON-CODE 240 001 X - REASON_CODE char(1) Reason Code
SPHF-S-ANAL-CODE-0 241 015 X - ANAL_CODE_0 char(15) Analysis Code 0

FILLER 391 110 X - - - -

Reference audit file

Description
The reference audit file holds the audit trail details for the relevant reference data. See the
subsection Data File Naming, in the section Naming Conventions for further information
about naming and usage of reference audit files.
M FD REF-AUDIT-FILE.
V *FD REF-AUDIT-FILE
V * VALUE OF ID IS REF-AUDIT-FILE-NAME.
01 REF-AUDIT-RECORD PIC X(1024).

Reference Audit file record descriptions
Reference Audit record, see SSAUDREC.CPY

REF-AUDIT-BEFORE-AFTER 001 001 X - Before/After Indicator
REF-AUDIT-SELECTION 002 001 X - Selection (Create, Amend etc)
REF-AUDIT-OP-ID 003 003 X - Operator Id
FILLER 006 064 X - Key Fields
REF-AUDIT-LOOKUP-ID 070 003 X - Lookup Id
FILLER 073 010 X - Lookup Code
REF-AUDIT-DATE-UPDATED 083 008 N - Date Updated
FILLER 091 939 X - Rest of Reference Data
FILLER 103 007 X - Rest of Reference Data

In SQL systems, the data is stored in the following table, called SSRAINS for the
installation file audit trail, and SSRAREF for the Reference file.
FIELD NAME FIELD TYPE COMMENT
DATA_1 char(5) Contains Before/After Indicator,Selection, and

Operator Id
DATA_2 char(29) Rest of key fields and Lookup fields
DATA_3 char(255) Rest of Reference Data
REC_TYPE char(3) Record Type
UPDTE_DATE char(8) Date Updated
UPDTE_TIME char(8) Extra Field, not on non-SQL
Note: Oracle (O) fields have different datatype to SQL Server fields (S)
SunBusiness transfer file

Description
The SunBusiness transfer files hold transactions that have been created in SunBusiness,
ready to be posted into SunAccount. This may be sales invoices, purchase invoices, or
inventory movements. The file is called SBTR-DEM.DAT and is indexed-sequential. There
is a separate file for purchase commitments, though the layout is the same. The purchase
commitment file is called SPTR-ddd.TXT. This file is a sequential file.
There are the following types of record on the transfer files:

 control record
There is one control record (type ‘C’) per file; there is one transaction (type ‘L’) record per
journal line that is to be posted to the ledger.
M FD TRANSFER-FILE.
V *FDTRANSFER-FILE VALUE OF ID IS TRANSFER-FILE-NAME.
01 TRANSFER-RECORD.
03 TRANSFER-DATA-1 PIC X(033).
03 TRANSFER-KEY PIC X(014).
03 TRANSFER-DATA-2 PIC X(353).

Transfer file record descriptions
Transaction record, see SALBKPRC.CPY, SQL table name SBTRTRNddd or SPTRTRNddd
TYPE
L-B-AC 001 015 X - ACCNT_CODE char(15) Account Code
L-B-AP 016 007 N 0 PERIOD int Accounting Period
L-B-DT 023 008 N 0 TRANS_DATE int Transaction Date
FILLER 031 002 X - - - -
L-B-RECORD-TYPE 033 001 X - RECORD_TYPE char - Record Type
- - - - - JRNAL_REF char(14) See below
L-B-SB-SOURCE 034 002 N - - - Value may be:

If in SOP ’1’=
Invoice trans’n
or ’2’= Inventory
trans’n
or in IC ’0’=
Inventory trans’n
or in POP ’6’=
Inventory trans’n
‘3’= UnApproved
Invoice trans’n
‘4’= UnApproved
Invoice reversal
‘5’= Approved
Invoice trans’n

L-B-SB-SEQ 036 005 N - - - Next Sequence No. from

Control record
L-B-SB-LINE 041 007 N - - - Sequence No. within L-B-

SEQ
L-B-AM-3DP 048 018 N 3 AMOUNT numeric Base Amount
L-B-DC 066 001 X - D_C char(1) Debit/Credit Indicator

Transaction record, see SALBKPRC.CPY, SQL table name SBTRTRNddd or SPTRTRNddd – (continued)
TYPE
L-B-AI 067 001 X - ALLOCATION char(1) Allocation Indicator
L-B-TT 068 005 X - JRNAL_TYPE char(5) Journal Type
L-B-JR 073 005 X - JRNAL_SRCE char(5) Journal Source
L-B-RF 078 015 X - TREFERENCE char(15) Transaction Reference
L-B-DS 093 025 X - DESCRIPTN char(25) Transaction Description
L-B-ED 118 008 N - ENTRY_DATE int Entry Date
L-B-EP 126 007 N - ENTRY_PRD int Entry Period
L-B-ADD-DATE 133 008 N - DUE_DATE int Due Date
FILLER 141 006 X - -
L-B-ALLOC-RF 147 009 N 0 ALLOC_REF char(15) Payment/Allocation Ref.
L-B-ALLOC-DT 156 008 N 0 ALLOC_DATE int Payment/Allocation Date
L-B-ALLOC-AP 164 007 N 0 ALLOC_PERIOD int Payment/Allocation Period
L-B-ASSET-IND 171 001 X - ASSET_IND char(1) Asset Marker
L-B-ASSET-CODE 172 010 X - ASSET_CODE char(10) Asset Code
L-B-ASSET-SUB-CODE 182 005 X - ASSET_SUB char(5) Asset Sub-Code

L-B-CONV-CODE 187 005 X - CONV_CODE char(5) Conversion Code
L-B-CONV-RATE 192 018 N 9 CONV_RATE numeric Conversion Rate
L-B-OTHER-AM 210 018 N 3 OTHER_AMT numeric Other Amount
L-B-OTHER-DP 228 001 X - OTHER_DP char(1) Other Amount d.p.
L-B-CLEARDOWN 229 005 N - CLEARDOWN numeric period cleardown number
FILLER 234 004 X - -
L-B-REVERSAL 238 001 X - REVERSAL char(1) Next Period Reversal
L-B-LOSS-GAIN 239 001 X - LOSS_GAIN char(1) G=Gains L=Losses

Revaluation Flag
L-B-ROUGH-FLAG 240 001 X - ROUGH_FLAG char(1) Rough Book Status
L-B-IN-USE-FLAG 241 001 X - IN_USE_FLAG char(1) Rough Line Recalled Flag
L-B-AN-0 242 015 X - ANAL_T0 char(15) Analysis Code 0

Transaction record, see SALBKPRC.CPY, SQL table name SBTRTRNddd or SPTRTRNddd – (continued)
TYPE
L-B-POSTING-DATE 392 008 N 0 POSTING_DATE int Posting Date
L-B-UOB 400 001 X - UOB char(1) Update Order Balance Ind’r
L-B- 400 001 X - UOB char(1) Update Order Balance on

SunBusiness
L-B-ALLOC-IN-PROGRESS 401 001 X - ALLOC_IN_PROGRESS char(1) Allocation in Progress
L-B-HOLD-REF 402 005 N - HOLD_REF int Held Journal Reference No
L-B-HOLD-OP-ID 407 003 X - HOLD_OP_ID char(3) Held Journal Operator ID

L-B-BCHECK-ACCT 410 015 X - BCHECK_ACCT char(15) Budget Check Account

Number
FILLER 425 088 X - - - -

Control record for the SunBusiness transfer file, see SALBKPRC.CPY, SQL table name SBTRMSC
TYPE
- - - - - CONTROL_IND char(1) -
FILLER 001 032 X - - - -
FILLER 033 001 X - - - Record Type Value ’C’
L-B-KEY 034 014 X - - - Key fields Value Spaces
FILLER 048 003 X - - - -
L-B-LAST-SEQ-NO 051 005 N - LAST_SEQNO char(5) Last Sequence No. used
- - - - - VERSION char(3) -
- - - - - LANG_CODE char(2) -
FILLER 056 244 X - - - -
FILLER 300 213 X - - - -

Control record for the purchase commitment file, SQL table name SPTRMSC
TYPE
TRANSFER-HEADER-KEY 001 032 X - - - Control Key Value all ’P’
- - - - - CONTROL_IND char(1) -
TRANSFER-HEADER-LEDGER 033 001 X - PCF_BUDGET char(1) Budget Code Mandatory
- - - - - VERSION char(3) -
- - - - - LANG_CODE char(2) -

SunAccount bank payment file

Description
The bank payments file holds details of payments made by the Generate Payments or
Generate Debits programs, for further processing. It is created when running Generate
Payments/Debits, if the Ledger Definition Automatic Bank Payments box is set to Y, and
the Payment Method you have selected is B. The bank payment file is for use with
automated payments systems, such as BACS. This file is a sequential file: there is no
index. There is no SQL table for this data – the file is the same for all environments. See
SunAccount Help for more information.
There is one type of record on the bank payments file:

 payment record
This record is created for each account being paid/direct debited.
Cobol Select...Assign Statement
SELECT BANK-FILE ASSIGN
M BANK-FILE-NAME
V *“BANK.FIL”
M ORGANISATION LINE SEQUENTIAL
V ORGANISATION IS SEQUENTIAL
STATUS BANK-FILE-STATUS.
M FD BANK-FILE.
V *FD BANK-FILE VALUE OF ID IS BANK-FILE-NAME.
01 BANK-RECORD.
03 BANK-SORT-CODE PIC X(15).
03 BANK-ACCOUNT-CODE PIC X(34).
03 BANK-ACCOUNT-NAME PIC X(35).
03 BANK-BASE-AMOUNT PIC 9(15)V999.
03 BANK-DEBIT-CREDIT PIC X(01).
03 BANK-FIRST-PAYMENT PIC X(01).
03 BANK-REFERENCE PIC X(18).
03 BANK-PROCESS-DATE PIC X(10).
03 BANK-SUN-AC PIC X(15).
03 BANK-CURRENCY PIC X(05).
03 BANK-OTHER-AM PIC 9(15)V999.
03 BANK-OTHER-DC PIC X(01).
03 BANK-PAYER-NUM PIC X(34).

Bank Payments file record description

BANK-SORT-CODE 001 015 X - Sort Code from Creditor/Debtor Bank Details
BANK-ACCOUNT-CODE 016 034 X - Bank Account Number from Creditor/Debtor Bank Details
BANK-ACCOUNT-NAME 050 035 X - Bank Account Name from Creditor/Debtor Bank Details
BANK-BASE-AMOUNT 085 018 N 3 Base Amount Paid
FILLER 103 004 X - -
BANK-DEBIT-CREDIT 107 001 X - Base Amount Debit/Credit Ind’r
BANK-FIRST-PAYMENT 108 001 X - First Payment Indicator
FILLER 109 003 X - -
BANK-REFERENCE 112 018 X - Transaction Reference from Creditor/Debtor Bank Details
FILLER 130 007 X - -
BANK-PROCESS-DATE 137 010 X - Payment Processing Date
FILLER 147 004 X - -
BANK-SUN-AC 151 015 X - Account Code SunSystems v4 Creditor/Debtor Account

Code
BANK-CURRENCY 166 005 X - Conversion Code

BANK-OTHER-AM 171 018 N 3 Other Amount Paid
BANK-OTHER-DC 189 001 X - Other Amount Debit/Credit
BANK-PAYER-NUM 190 034 X - Own Bank Account Number i.e. of Payment

Account

SunAccount payment file

Description
The payment file holds details of payments/direct debits made by the Generate Payments
or Generate Debits programs, for further processing. It is created when running Generate
Payments/Debits. The payment file contains details of all payments/direct debits being
made. It is used by the Print Remittances program after the Generate Payments has
posted the payments to the ledger. After Generate Debits has posted the direct debit
transactions, then the file is cleared, as it is no longer required.
There are the following types of record on the payment file:

 control record
 account header record
 detail record
 payment record
 total discount record.

M FD PAYMT-FILE.
V *FDPAYMT-FILE VALUE OF ID IS PAYMT-FILE-NAME.
COPY “SAPAYRC.CPY”.

Payment file record descriptions see SAPAYRC.CPY

P-PROFILE-IND 001 001 X - Profile Indicator PIC X
P-AC-SEQ 002 005 N 0 Unique sequence number
P-CONV-CODE 007 005 X - Conversion Code PIC X (5)
P-RECORD-TYPE 012 001 X - Record Type Value ’C’, ’A’, ’P’, ‘D’ or ’Z’
P-DETAIL-COUNT 013 005 N 0 Count of detail records
P-DETAIL-TYPE 018 001 N 0 Detail Type Value

1=Original trans’n
2=Discount Trans’n
FILLER 019 006 X - -
FILLER 025 008 X - -
If the record type is ‘P’ or ‘Z’, then the key includes Analysis Codes rather than the above four fields.
P-HASH-KEY 013 012 X - Hash Analysis Code
FILLER 025 008 X - -
If the record type is ’B’, then the
P-BANK-ACC-KEY 013 015 X -
P-BANK-CONV-CODE 028 005 X -

The data is defined according to the record type, each group being a definition of the first:
Control record, type ‘C’

P-BANK-ACCOUNT 033 015 X - Payment Account Code
P-RECORD-COUNT 048 005 N 0 Count of type ’A’ recs.
P-OTHER-AM-RUN 053 001 X - Other Amount run Y Other Amount payment
P-STORED-DP 054 001 X - Other Amount d.p. From Conv. Table
P-PAY-DATE 055 008 N 0 Base Date for Payment
P-BANK-ACC-NUM 063 034 X - Payment A/c Bank A/c No. From Bank Details
P-STORED-OPERATOR 097 001 X Store Conversion operator (*/)
P-NUMBER-PAYMENTS 098 004 N Total number of credit balances PIC 9(6) COMP-3.
P-NUMBER-DEBIT-BAL 102 004 N Total number of debit balances PIC 9(6) COMP-3.
P-NUMBER-DEBIT-SETTLED 106 004 N Number of debit balances settled PIC 9(6) COMP-3.
P-CASH-TOTAL 110 010 S Base Cash Total PICS 9(15) V999 COMP-3.
P-DISCOUNT-TOTAL 120 010 S Base Discount Total PICS 9(15) V999 COMP-3.
P-TAX-TOTAL 130 010 S Base Tax Total PICS 9(15) V999 COMP-3
P-IN-USE-TOTAL 140 010 S Base in-use total PICS 9(15) V999 COMP-3
P-DEBIT-BAL-TOTAL 150 010 S Base Debit Balance Total PICS 9(15) V999 COMP-3

P-DEBIT-SETTLED-TOTAL 160 010 S Base Debit Settled Total PICS 9(15) V999 COMP-3
P-CASH-TOTAL-O 170 010 S Other Cash Total PICS 9(15) V999 COMP-3
P-DISCOUNT-TOTAL-O 180 010 S Other Discount Total PICS 9(15) V999 COMP-3
P-TAX-TOTAL-O 190 010 S Other Tax Total PICS 9(15) V999 COMP-3
P-IN-USE-TOTAL-O 200 010 S Other In-use Total PICS 9(15) V999 COMP-3
P-DEBIT-BAL-TOTAL-O 210 010 S Other Debit Balance PICS 9(15) V999 COMP-3
P-DEBIT-SETTLED-TOTAL-O 220 010 S Other Debit balance settled PICS 9(15) V999 COMP-3
P-NUMBER-ACCEPTED 230 004 N Number Accepted PICS 9(15) V999 COMP-3.
P-NUMBER-REJECTED 234 004 N Number Rejected PICS 9(15) V999 COMP-3
P-BANK-ACCEPT-TOT 238 010 S Accepted Base Value PICS 9(15) V999 COMP-3.
P-BANK-REJECT-TOT 248 010 S Rejected Base Value PICS 9(15) V999 COMP-3
P-BANK-ACCEPT-TOT-O 258 010 S Accepted Other Value PICS 9(15) V999 COMP-3

Control record, type ‘C’ – (continued)

P-BANK-REJECT-TOT-O 268 010 S Rejected Other Value PICS 9(15) V999 COMP-3
P-D-NUMBER-ACCEPTED 278 004 N Number of debit transactions accepted PIC 9(6) COMP-3
P-D-NUMBER-REJECTED 282 004 N Number of debit transactions rejected PIC 9(6) COMP-3
P-D-BANK-ACCEPT-TOT 286 010 S Value accepted PICS 9(15) V999 COMP-3.
-D-BANK-REJECT-TOT 296 010 S Value rejected PICS 9(15) V999 COMP-3
P-D-BANK-ACCEPT-TOT-O 306 010 S Other Accepted Value PICS 9(15) V999 COMP-3
P-D-BANK-REJECT-TOT-O 316 010 S Other Rejected Value PICS 9(15) V999 COMP-3
P-NUMBER-ZERO-BAL 326 003 N Number of zero balances PIC 9(5) COMP-3.
P-NUMBER-C-BAL 329 003 N Number of credit balances PIC 9(5) COMP-3
P-NUMBER-D-BAL 332 003 N Number Of debit balances PIC 9(5) COMP-3
P-NUMBER-TOTAL 335 003 N Number of balances PIC 9(5) COMP-3
AM-D-BAL 338 010 N Total of debit balances PIC 9(15) V999 COMP-3.
AM-C-BAL 348 010 N Total of credit balances PICS 9(15) V999 COMP-3.
AM-D-BAL-O 358 010 N Total of other debit balances PICS 9(15) V999 COMP-3.
AM-C-BAL-O 368 010 N Total of other credit balances PICS 9(15) V999 COMP-3.
AM-TOTAL 378 010 S Total Amount PICS 9(15) V999 COMP-3.

FILLER 388 005 X - -

Account Header record, type ‘A’

P-AC 033 015 X - Account Code
P-AC-NAME 048 030 N 0 Account Name
P-AC-ADD 078 010 X - Address Code
P-AC-AM 088 018 S 3 Payment Base Amount
P-AC-SIGN 106 001 X - Payment Sign
P-AC-PAY-METHOD 107 001 X - Payment Method
P-AC-PROCESSED 108 001 X - Account processed by Print Remittances
P-AC-OTHER-AM 109 018 S 3 Payment Other Amount
P-AC-PAID 127 001 X - Payment/debit to be generated
P-AC-DISC 128 018 N 0 Base discount PICS 9(15) V999.
P-AC-OTHER-DISC 146 018 N 0 Other Discount PICS 9(15) V999.
P-AC-DP 164 001 X - Decimal places PIC X
P-AC-OPERATOR 165 001 X - Conversion Operator (*/)
P-AC-BANK-ACCOUNT 166 015 X - Payment account PIC X(15)
P-AC-IN-USE-TOTAL 181 018 S 3 Total in-use PICS 915) V999 Comp-3
P-AC-IN-USE-TOTAL-O 199 018 S 3 Total in-use Other PICS 9(15) V999 Comp-3

P-AC-TAX-TOTAL 217 018 S 3 Total Tax PICS 9(15) V999 Comp-3
P-AC-TAX-TOTAL-O 235 018 S 3 Total Tax Other PICS 9(15) V999 Comp-3
P-AC-PROCESSED-PAYMENT 253 001 X - Process payment Ind PIC X
P-AC-BANK-CODE 254 005 X - Bank Code PIC X(5)
FILLER 259 134 - -

Detail record, type ‘D’

PAYMENT-TRANSACTION 033 359 X - Ledger Transaction generated
FILLER 033 208 - - -
P-ANAL-CODE-0 241 015 X - Analysis Code 0
P-D-TRANS-PROCESSED 391 001 X - Set externally if processed PIC X
FILLER 392 001 X - -
The Payment record, type ’P’

P-SUPP-AC-KEY 033 038 X - Key to Payment Trans’n on Creditor/Debtor

A/c
P-CASH-AC-KEY 071 038 X - Key to Payment Trans’n on Payment A/c
P-PAYMENT-AMOUNT 109 018 S 3 Payment Base Amount
P-PAYMENT-OTHER-AM 127 018 S 3 Payment Other Amount
P-PAY-TWO-RECORDS 145 001 X - Amount and Other Amount same sign
FILLER 146 245 X - -
P-P-TRANS-PROCESSED 246 001 X - Set externally if processed PIC X
FILLER 247 001 X - -
The Total Tax Record, type ’T’
P-TAX-AMOUNT 033 018 S 3 Tax Amount
P-TAX-OTHER-AM 051 018 S 3 Tax Other Amount
FILLER 069 150 - - -

Detail record, type ‘D’ – (continued)

P-TAX-AC 219 015 X - Tax Account
FILLER 234 007 X - -
P-TAX-ANALS 241 150 X - Tax Analysis Codes
FILLER 391 002 X - -

Total Discount record, type ‘Z’

P-DISC-INPUT-AMOUNT 033 018 S 3 Input base amount S 9(15) V999 Comp-3.
P-DISC-INPUT-OTHER-AM 051 018 S 3 Input Other amount S 9(15) V999 Comp-3.
P-DISC-OUTPUT-AMOUNT 069 018 S 3 Output base amount PICS 9(15) v999 Comp-3
P-DISC-OUTPUT-OTHER-AM 087 018 S 3 Output other amount PICS 9(15) V999 Comp-3
P-DISC-INPUT-AC 105 015 X - Input account PIC X(15)
P-DISC-OUTPUT-AC 120 015 X - Output account PIC X(15)
P-DISC-INPUT-ENTER-INDS 135 010 X - Input entry inds PIC X(10)
P-DISC-OUTPUT-ENTER-INDS 145 010 X - Output entry inds PIC X(10)
FILLER 155 086 X - -
P-DISCOUNT-ANALS 241 150 X - Discount analysis codes PIC X(150)
FILLER 391 002 X - -
The Bank Record, type ’B’
P-BANK-BASE 033 010 S 3 Bankbase PICS 9(15) V999 COMP-3.
P-BANK-OTHER 043 010 S 3 Bank Other PICS 9(15) V999 COMP-3.
P-BANK-STORED-DP 053 001 X - Bank decimal places
FILLER 054 339 - - -

In SQL versions, the data is stored in the following table, called SAPYPAYddd:
Oracle Field name Field type

/ SQL
PROFILE_IND char(1)
AC_SEQ char(5)
CONV_CODE char(5)
REC_TYPE char(1)
DETAIL_KEY char(6)
ANALYSIS KEY char(150)
BANK_KEY char(20)
KEY_FIELDS char(156)
O DATA_1 char(153)
S DATA_1 binary(153)
O DATA_2 char(241)
S DATA_2 binary(241)
Note: Oracle (O) fields have different datatype to SQL Server fields (S).
SunAccount journal hold file

Description
The journal hold file holds transactions that have been created in Journal Entry and then
held prior to posting. When a Rough Book is in use, transactions may be recalled from the
ledger file and then held prior to re-posting.
There are the following types of record on the journal hold file:
 Standard record
 Journal Control record
 Analysis record
 Transaction Control record
 Transaction Line record
 Split record
 Amendment record
 Period record
 Query Record 1

 Query Record 2
 Query Record 3
 Query Record 4
 Query Record 5
 Journal Hold Control record
 Journal Hold Version record
 Journal Hold Actual/Budget record
 Journal Hold Journal record.

M FD HOLD-FILE.
V *FD HOLD-FILE VALUE OF ID IS HOLD-FILE-NAME.
01 HOLD-RECORD.
03 FILLER PIC
X(32).
03 HOLD-KEY
PIC X(15).
03 HOLD-DATA
PIC X(465).

Journal hold file record descriptions
Standard record, see SAJEWORK.CPY

SAJE-WORK-REC-TYPE 001 001 X - Record Type Key 1 Mandatory
SAJE-WORK-REFERENCE 002 015 X - Reference Mandatory
SAJE-WORK-LINE-NO 017 003 N 0 Line Number Key 1 Mandatory
SAJE-WORK-LINE-NO-SUFF 020 002 N 2 Line Number Suffix
SAJE-WORK-REC-TYPE-2 022 001 X - Record Type Key 2
SAJE-WORK-REF-ID 023 005 N 0 Reference Id
SAJE-WORK-LINE-NO-2 028 003 N 0 Line Number Key 2
SAJE-WORK-LINE-NO-2-SUFF 031 002 N 0 Line Number Suffix
SAJH-WORK-TYPE 033 001 X - Journal Held Type
SAJH-WORK-AB 034 001 X - Journal Held Actual/Budget
SAJH-WORK-JOURNAL-REF 035 005 N 0 Journal Held Reference
SAJH-WORK-REC-TYPE 040 001 X - Journal Held Record Type
SAJH-WORK-JOURNAL-SEQ 041 007 N 0 Journal Held Sequence Number
FILLER 048 465 X - -

FILLER 513 512 - - -

Journal Control record, see SAJEWORK.CPY

SAJE-WORK-C-REC-TYPE 001 001 X - Record Type Key 1 Mandatory value "C"
SAJE-WORK-C-REFERENCE 002 015 X - Reference Mandatory value "000000000000000"
SAJE-WORK-C-LINE-NO 017 003 N 0 Line Number Key 1 Mandatory value "000"
SAJE-WORK-C-LINE-NO-SUFF 020 002 N 0 Line number suffix
SAJE-WORK-C-REC-TYPE-2 022 001 X - Record Type Key 2 Value "C"
SAJE-WORK-C-REF-ID 023 005 N 0 Reference Id Value "00000"
SAJE-WORK-C-LINE-NO-2 028 003 N 0 Line Number Key 2 Value "000"
SAJE-WORK-C-LINE-NO-2-SUFF 031 002 N 0 Line number suffix
SAJH-WORK-C-TYPE 033 001 X - Journal Held Type Type "2"
SAJH-WORK-C-AB 034 001 X - Journal Held Actual/Budget
SAJH-WORK-C-JOURNAL-REF 035 005 N 0 Journal Held Reference
SAJH-WORK-C-REC-TYPE 040 001 X - Journal Held Record Type Value "C"
SAJH-WORK-C-JOURNAL-SEQ 041 007 N 0 Journal Held Sequence Number
SAJE-WORK-HIGHEST-REF-ID 048 005 N 0 Highest Reference Id
SAJE-WORK-CURRENT-KEY 053 011 X - Current Key
SAJE-WORK-CURRENT-FIELD 064 003 N 0 Current Field

SAJE-WORK-HIGHEST-PERIOD 067 007 N 0 Highest Period
SAJE-WORK-HIGHEST-PRESET 074 003 N 0 Highest Preset
SAJE-WORK-CURRENT-OVERLAY 077 001 X - Current Overlay
SAJE-WORK-TOTAL-INDICATOR 078 001 X - Total Indicator
SAJE-WORK-JT-INDICATOR 079 001 X - Journal type indicator
SAJE-WORK-ACTUAL-BUDGET 080 001 X - Actual/Budget
SAJE-WORK-AJD-JOURNAL-NAME 081 025 X - Journal Name
SAJE-WORK-AJD-PRESET-CODE 106 005 X - Preset Code
SAJE-WORK-AJD-ANAL-CAT 111 020 X - Analysis Category Occurs 10 Times
SAJE-WORK-AJD-SUPPRESS- 131 001 X - Suppress Ageing

AGEING

Journal Control record, see SAJEWORK.CPY – (continued)

SAJE-WORK-AJD-DESC-PER- 132 001 X - Description per Line

LINE
SAJE-WORK-AJD-FORCE- 133 001 X - Force Withhold

WITHHOLD
SAJE-WORK-AJD-NEXT-PERIOD- 134 001 X - Next Period Reversal

REV
SAJE-WORK-AJD-DUE-DATE- 135 001 X - Due Date Entry

ENTRY
SAJE-WORK-AJD-UNIQUE-REFS 136 001 X - Unique References
SAJE-WORK-AJD-CREATE-NO- 137 001 X - Journal Definition Create with no Pause

PAUSE
SAJE-WORK-AJD-CONVERSION 138 001 X - Journal Definition Conversion
SAJE-WORK-AJD-ASSET-ENTRY 139 001 X - Journal Definition Asset Entry
SAJE-WORK-AJD-SUPPRESS-JE 140 001 X - Journal Definition Suppress Journal Entry
SAJE-WORK-AJD-SUPPRESS-JI 141 001 X - Journal Definition Suppress Journal Import
SAJE-WORK-AJD-SUPPRESS-AA 142 001 X - Journal Definition Suppress Account Allocation
SAJE-WORK-AJD-SEQ-CODE 143 005 X - Journal Definition Sequence Code
SAJE-WORK-AJD-TRANS-SEQ 148 001 X - Journal Trans sequence

AJE-WORK-AJD-IN-DISC-ACC 149 015 X - Journal definition In discount account
SAJE-WORK-AJD-OUT-DISC-ACC 164 015 X - Journal definition Out discount account
SAJE-WORK-AJD-DISC-TOL- 179 011 N 2 Journal definition tolerance percent

PERC
SAJE-WORK-AJD-DISC-TOL-VAL 190 012 N 3 Journal definition tolerance value
SAJE-WORK-AJD-AUTO-TAX-IND 202 001 X - Journal definition auto tax ind
SAJE-WORK-AJD-TAX-ACC-IND- 203 001 X - Journal definition tax ind creditors

CR
SAJE-WORK-AJD-TAX-ACC-IND- 204 001 X - Journal definition tax ind debtors

DB
SAJE-WORK-AJD-TAX-ACC-IND- 205 001 X - Journal definition tax ind clients

CT


SAJE-WORK-AJD-TAX-ACC-IND- 206 001 X - Journal definition tax ind memo

MEM
SAJE-WORK-AJD-TAX-ACC-IND- 207 001 X - Journal definition tax ind profit & loss
PL
SAJE-WORK-AJD-TAX-ACC-IND- 208 001 X - Journal definition tax ind balance sheet

BAL
SAJE-WORK-AJD-STP-ACC-IND- 209 001 X - Journal definition stop ind creditors

CR
SAJE-WORK-AJD-STP-ACC-IND- 210 001 X - Journal definition stop ind debtors

DB
SAJE-WORK-AJD-STP-ACC-IND- 211 001 X - Journal definition stop ind clients

CT
SAJE-WORK-AJD-STP-ACC-IND- 212 001 X - Journal definition stop ind memo

MEM
SAJE-WORK-AJD-STP-ACC-IND- 213 001 X - Journal definition stop ind profit & loss
PL
SAJE-WORK-AJD-STP-ACC-IND- 214 001 X - Journal definition stop ind balance sheet

BAL
SAJE-WORK-AJD-AUTO-TAX-ACC 215 001 X - Auto tax account
SAJE-WORK-ANAL-LOC 216 020 X - Analysis Location (T-Codes) Occurs 10 Times

SAJE-WORK-JOURNAL-TYPE 236 005 X - Journal Type
SAJE-WORK-JOURNAL-SOURCE 241 005 X - Journal Source
SAJE-WORK-DATABASE-CODE 246 003 X - Database Code
SAJE-WORK-JOURNAL-NUMBER 249 007 N 0 Journal Number
SAJE-WORK-NUMBER-OF-REFS 256 007 N 0 Number of References
SAJE-WORK-AUTO-SEQ 263 001 X - Auto Sequence
SAJE-WORK-ENTRY-DATE 264 008 N 0 Entry date
SAJE-WORK-ENTRY-PERIOD 272 007 N 0 Entry period
SAJE-WORK-J-BASE-TOTAL-D 279 010 N 3 Base Total Debit PIC 9(15) V9(3) COMP-3
SAJE-WORK-J-BASE-TOTAL-C 289 010 N 3 Base Total Credit PIC 9(15) V9(3) COMP-3
SAJE-WORK-J-OTHER-TOTAL-D 299 010 N 3 Other Total Debit PIC 9(15) V9(3) COMP-3


SAJE-WORK-J-OTHER-TOTAL-C 309 010 N 3 Other Total Credit PIC 9(15) V9(3) COMP-3
SAJE-WORK-J-MEMO-TOTAL-D 319 010 N 3 Memo Total Debit PIC 9(15) V9(3) COMP-3
SAJE-WORK-J-MEMO-TOTAL-C 329 010 N 3 Memo Total Credit PIC 9(15) V9(3) COMP-3
SAJE-WORK-J-RATIO-TOTAL-B 339 010 N 9 Ratio Total Base PIC 9(9) V9(9) COMP-3
SAJE-WORK-J-RATIO-TOTAL-O 349 010 N 9 Ratio Total Other PIC 9(9) V9(9) COMP-3
SAJE-WORK-C-SOURCE-FLAG 359 001 X - Source Flag
SAJE-WORK-JOURNAL-NO 360 007 N 0 Journal Number
SAJE-WORK-NEXT-SEQ-NO 367 005 N 0 Next sequence no from online allocations
SAJE-WORK-CURRENT-L-KEY 372 032 X - Current key from online allocations
SAJE-WORK-LAST-TRANS-SEQ 404 001 X - Last transaction sequence from online

allocations
SAJE-WORK-LAST-OVERLAY 405 001 X - Last overlay from online allocations
SAJE-WORK-NO-OF- 406 005 N 0 No of allocations from online allocations

ALLOCATIONS
SAJE-WORK-NON-ROUGH 411 007 N 0 Non-rough alloactions from online alloactions
FILLER 418 094 X - -
SAJE-WORK-LAST-SELECTION 512 001 X - Last selection from online allocations

FILLER 513 512 X - -

Analysis record, see SAJEWORK.CPY

SAJE-WORK-A-REC-TYPE 001 001 X - Record Type Key 1 Mandatory Value "A"
SAJE-WORK-A-FILLER 002 020 X - - Value "000000000000000000"
SAJE-WORK-A-REC-TYPE-2 022 001 X - Record Type Key 2 Mandatory Value "A"
SAJE-WORK-A-FILLER-2 023 010 X - - Value "00000000"
SAJH-WORK-ANALYSIS-TYPE 033 001 X - Journal Held Type Value "2"
SAJH-WORK-ANALYSIS-AB 034 001 X - Journal Held Actual/Budget
SAJH-WORK-ANALYSIS- 035 005 N 0 Journal Held Reference

JOURNAL-REF
SAJH-WORK-ANALYSIS-REC- 040 001 X - Journal Held Record Type Value "A"

TYPE
SAJH-WORK-ANALYSIS- 041 007 N 0 Journal Held Sequence Number

JOURNAL-SEQ
SAJE-WORK-ANAL-CAT-SHORT- 048 050 X - Analysis Category Short Name Occurs 10 Times

NAMES
SAJE-WORK-ANAL-CAT-LONG- 098 200 X - Analysis Category Long Name Occurs 10 Times

NAMES
FILLER 298 215 X - -
FILLER 513 512 X - -

Transaction Control record, see SAJEWORK.CPY

SAJE-WORK-T-REC-TYPE 001 001 X - Record Type Key 1 Mandatory Value "T"
SAJE-WORK-T-REFERENCE 002 015 X - Reference
SAJE-WORK-T-LINE-NO 017 003 N 0 Line Number Key 1 Value "000"
SAJE-WORK-T-LINE-NO-SUFF 020 002 N 0 -
SAJE-WORK-T-REC-TYPE-2 022 001 X - Record Type Key 2 Mandatory Value "T"
SAJE-WORK-T-REF-ID 023 005 N 0 Reference Id
SAJE-WORK-T-LINE-NO-2 028 003 N 0 Line Number Key 2 Value "000"
SAJE-WORK-T-LINE-NO-2-SUFF 031 002 N 0 -
SAJH-WORK-TRANS-TYPE 033 001 X - Journal Held Type Type "2"
SAJH-WORK-TRANS-AB 034 001 X - Journal Held Actual/Budget
SAJH-WORK-TRANS-JOURNAL- 035 005 N 0 Journal Held Reference

REF
SAJH-WORK-TRANS-REC-TYPE 040 001 X - Journal Held Record Type Type "T"
SAJH-WORK-TRANS-JOURNAL- 041 007 N 0 Journal Held Sequence Number

SEQ
SAJE-WORK-HIGHEST-LINE-NO 048 003 N 0 Highest Line Number

SAJE-WORK-HIGHEST-PRESET- 051 003 N 0 Highest Preset Used

USED
SAJE-WORK-T-BASE-D 054 010 S 3 Base Total Debit PIC 9(15) V9(3) COMP-3
SAJE-WORK-T-BASE-C 064 010 S 3 Base Total Credit PIC 9(15) V9(3) COMP-3
SAJE-WORK-T-OTHER-D 074 010 S 3 Other Total Debit PIC 9(15) V9(3) COMP-3
SAJE-WORK-T-OTHER-C 084 010 S 3 Other Total Credit PIC 9(15) V9(3) COMP-3
SAJE-WORK-TU-BASE-D 094 010 S 3 Non Posting Base Total Debit PIC 9(15) V9(3) COMP-3
SAJE-WORK-TU-BASE-C 104 010 S 3 Non Posting Base Total Credit PIC 9(15) V9(3) COMP-3
SAJE-WORK-TU-OTHER-D 114 010 S 3 Non Posting Other Total Debit PIC 9(15) V9(3) COMP-3
SAJE-WORK-TU-OTHER-C 124 010 S 3 Non Posting Other Total Credit PIC 9(15) V9(3) COMP-3
SAJE-WORK-TRANS-SEQ-NUM 134 007 N 0 Transaction Sequence Number
SAJE-WORK-NUMBER-OF-TRANS 141 007 N 0 Number of Transactions

Transaction Control record, see SAJEWORK.CPY – (continued)

SAJE-WORK-NUMBER-OF-SUFF 148 003 N 0 Number of suffixes
FILLER 151 362 X - -
FILLER 513 512 X - -

Transaction Line record, see SAJEWORK.CPY

SAJE-WORK-L-REC-TYPE 001 001 X - Record Type Key 1 Mandatory Value "L"
SAJE-WORK-L-REFERENCE 002 015 X - Reference
SAJE-WORK-L-LINE-NO 017 005 N 0 Line Number Key 1
SAJE-WORK-L-LINE-NO-SUFF 022 002 N 0 Line number suffix 1
SAJE-WORK-L-REC-TYPE-2 024 001 X - Record type Key 2 Mandatory Value "L"
SAJE-WORK-L-REF-ID 025 005 N 0 Reference Id
SAJE-WORK-L-LINE-NO-2 030 003 N 0 Line Number Key 2
SAJE-WORK-L-LINE-NO-2-SUFF 033 002 N 0 Line number suffix 2
SAJH-WORK-LINE-TYPE 035 001 X - Journal Held Type Type "2"
SAJH-WORK-LINE-AB 036 001 X - Journal Held Actual/Budget
SAJH-WORK-LINE-JOURNAL-REF 037 005 N 0 Journal Held Reference
SAJH-WORK-LINE-REC-TYPE 042 001 X - Journal Held Record Type Value "L"
SAJH-WORK-LINE-JOURNAL-SEQ 043 007 N 0 Journal Held Sequence Number
SAJE-WORK-LINE-DELETED 050 001 X - Line Deleted
SAJE-WORK-ACC-PERIOD 051 007 N 0 Accounting Period
SAJE-WORK-TRANS-DATE 058 008 N 0 Transaction Date

SAJE-WORK-DUE-DATE 066 008 N 0 Due Date
SAJE-WORK-DESCRIPTION 074 030 X - Description
SAJE-WORK-ACC-CODE 104 015 X - Account Code
SAJE-WORK-AM 119 010 N 3 Base Amount PIC 9(15) V9(3) COMP-3
SAJE-WORK-DC 129 001 X - Debitor Credit Flag
SAJE-WORK-OTHER-AM 130 010 N 3 Other Amount PIC 9(15) V9(3) COMP-3
SAJE-WORK-CONV-CODE 140 005 X - Conversion Code
SAJE-WORK-OTHER-DP 145 001 X - Other Decimal Places
SAJE-WORK-OPERATOR 146 001 X - Conversion Rate Operator (*or/)
SAJE-WORK-CONV-RATE 147 010 N 9 Conversion Rate PIC 9(9) V9(9) COMP-3
SAJE-WORK-ANAL-CODE 157 150 X - Analysis Code Occurs 10 Times

Transaction Line record, see SAJEWORK.CPY – (continued)

SAJE-WORK-ASSET-CODE 307 010 X - Asset Code
SAJE-WORK-ASSET-SUBCODE 317 005 X - Asset Subcode
SAJE-WORK-VD 322 001 X - Asset VID Marker
SAJE-WORK-ACC-TYPE 323 001 X - Account Type
SAJE-WORK-ACC-NAME 325 030 X - Account Name
SAJE-WORK-ENTER-T 354 010 X - Account T-Code Indicator Occurs 10 Times
SAJE -WORK-AI 364 001 X - Allocation Indicator
SAJE-WORK-ALLOC-RF 365 005 N 0 Allocation Reference PIC 9(9) COMP-3
SAJE-WORK-ALLOC-DT 370 008 N 0 Allocation Date
SAJE-WORK-ALLOC-AP 378 007 N 0 Allocation Period
SAJE-WORK-LINE-ROUGH-FLAG 385 001 X - Rough Flag
SAJE-WORK-L-JOURNAL-TYPE 386 005 X - Journal Type
SAJE-WORK-L-JOURNAL-SOURCE 391 005 X - Journal Source
SAJE-WORK-L-ENTRY-DATE 396 008 X 0 Entry Date
SAJE-WORK-L-ENTRY-PERIOD 404 007 N 0 Entry Period
SAJE-WORK-L-ALLOC-IND 411 001 X - Allocated Ind

SAJE-WORK-L-ALLOC-SEQ 412 005 N 0 Allocated Seq
SAJE-WORK-L-JOURNAL-NO 417 007 N 0 Journal Number
SAJE-WORK-L-LEDGER 424 090 N - Online Cash Flag
FILLER 425 090 X - -
FILLER 515 512 X - -

Split record, see SAJEWORK.CPY

SAJE-WORK-M-REC-TYPE 001 001 X - Record type
SAJE-WORK-M-SEQ-NO 002 005 N 0 Sequence number
SAJE-WORK-M-SEQ-LINE-NO 007 003 N 0 Line number
SAJE-WORK-M-LINE-NO-SUFF 010 002 N 0 Line number suffix
SAJE-WORK-M-REFERENCE 012 010 X - Reference
SAJE-WORK-M-REC-TYPE-2 022 001 X - Record Type 2
SAJE-WORK-M-SEQ-NO-2 023 005 N 0 Sequence number 2
SAJE-WORK-M-SEQ-LINE-NO-2 028 003 N 0 Line number 2
SAJE-WORK-M-LINE-NO-2-SUFF 031 002 N 0 Suffix number 2
SAJH-WORK-M-TYPE 033 001 X - Type
SAJH-WORK-M-AB 034 001 X - Actualor Budget
SAJH-WORK-M-JOURNAL-REF 035 005 N 0 Journal reference
SAJH-WORK-M-REC-TYPE 040 001 X - record type
SAJH-WORK-M-JOURNAL-SEQ 041 007 N 0 Sequence number
SAJE-M-ALLOC 048 001 X - Allocation
SAJE-M-LEDGER-KEY 049 038 X - Ledger Key

SAJE-M-LEDGER-DATA 087 400 X - Ledger data
FILLER 487 026 X - -
FILLER 513 512 X - -

Amendment record, see SAJEWORK.CPY

SAJE-WORK-N-REC-TYPE 001 001 X - Record Type 1
SAJE-WORK-N-SEQ-NO 002 005 N 0 Sequence number 1
SAJE-WORK-N-SEQ-LINE-NO 007 003 N 0 Line number 1
SAJE-WORK-N-LINE-NO-SUFF 010 002 N 0 Suffix 1
FILLER 012 010 X - -
SAJE-WORK-N-REC-TYPE-2 022 001 X - Record Type 2
SAJE-WORK-N-SEQ-NO-2 023 005 N 0 Sequence number 2
SAJE-WORK-N-SEQ-LINE-NO-2 028 003 N 0 Line number 2
SAJE-WORK-N-LINE-NO-2-SUFF 031 002 N 0 Suffix number 2
SAJH-WORK-N-TYPE 033 001 X - Type
SAJH-WORK-N-AB 034 001 X - Actual or Budget
SAJH-WORK-N-JOURNAL-REF 035 005 N 0 Journal reference
SAJH-WORK-N-REC-TYPE 040 001 X - Record type
SAJH-WORK-N-JOURNAL-SEQ 041 007 N 0 Journal sequence
SAJE-N-ALLOC 048 001 X - Allocation
SAJE-N-LEDGER-KEY 049 038 X - Ledger key

SAJE-N-LEDGER-DATA 087 400 X - Ledger data
FILLER 487 026 X - -
FILLER 513 512 X - -

Period record, see SAJEWORK.CPY

SAJE-WORK-P-REC-TYPE 001 001 X - Record Type Key 1 Mandatory Value "P"
SAJE-WORK-P-PERIOD 002 007 N 0 Period Key 1
SAJE-WORK-P-FILLER 009 013 X - - Value "0000000000000"
SAJE-WORK-P-REC-TYPE-2 022 001 X - Record Type Key 2 Mandatory Value "P"
SAJE-WORK-P-PERIOD-2 023 007 N 0 Period Key 2
SAJE-WORK-P-FILLER-2 030 003 X - - Value "0"
SAJH-WORK-PERIOD-TYPE 033 001 X - Journal Held Type "2"
SAJH-WORK-PERIOD-AB 034 001 X - Journal Held Actual/Budget
SAJH-WORK-PERIOD-JOURNAL- 035 005 N 0 Journal Held Reference

REF
SAJH-WORK-PERIOD-REC-TYPE 040 001 X - Journal Held Record Type Type "P"
SAJH-WORK-PERIOD-JOURNAL- 041 007 N 0 Journal Held Sequence Number

SEQ
SAJE-WORK-P-BASE-D 048 010 N 3 Base Total Debit PIC 9(15) V9(3) COMP-3
SAJE-WORK-P-BASE-C 058 010 N 3 Base Total Credit PIC 9(15) V9(3) COMP-3
SAJE-WORK-P-OTHER-D 068 010 N 3 Other Total Debit PIC 9(15) V9(3) COMP-3
SAJE-WORK-P-OTHER-C 078 010 N 3 Other Total Credit PIC 9(15) V9(3) COMP-3

FILLER 088 425 X - -
FILLER 513 512 X - -

Query record 1, see SAJEWORK.CPY

SAJE-WORK-Q1-REC-TYPE 001 001 X - Record type Value "Q"
SAJE-WORK-Q1-FILLER 002 020 X - Filler Value "00000000000000000001"
SAJE-WORK-Q1-REC-TYPE-2 022 001 X - Record type 2 Value "Q"
SAJE-WORK-Q1-FILLER-2 023 010 X - Filler Value "0000000001"
SAJH-WORK-QUERY1-TYPE 033 001 X - Query type Type "2"
SAJH-WORK-QUERY1-AB 034 001 X - Actual or budget
SAJH-WORK-QUERY1-JOURNAL- 035 005 N 0 Journal reference

REF
SAJH-WORK-QUERY1-REC-TYPE 040 001 X - Record type Value "Q"
SAJH-WORK-QUERY1-JOURNAL- 041 007 N 0 Journal sequence

SEQ
SAJE-WORK-Q1-PROCESS-MODE 048 002 X - Process mode
SAJE-WORK-Q1-TRANS-DATA 050 020 X - Trans data
SAJE-WORK-Q1-LINE-DATA 070 367 X - Line data
FILLER 437 076 X - -
FILLER 513 512 X - -


SAJH-WORK-QUERY2-AB 034 001 X - Actual or Budget

REF
SAJH-WORK-QUERY2-REC-TYPE 040 001 X - Record Type "Q"

SEQ
SAJE-WORK-Q2-LINE-PRESETS 048 333 X - Journal Presets
SAJE-WORK-Q2-ANAL-VALIDATE 381 010 X - -
FILLER 391 122 X - -
FILLER 513 512 X - -



REF
SAJH-WORK-QUERY3-REC-TYPE 040 001 X - Record type "Q"

SEQ
SAJE-WORK-TEMP-TRANS-DATA 048 020 X - Temp Trans data
SAJE-WORK-TEMP-LINE-DATA 068 367 X - Temp Line data
SAJE-WORK-TEMP-HIGHEST- 435 005 N 0 Highest ref Id

REF-ID
SAJE-WORK-TEMP-HIGHEST- 440 003 N 0 Highest line number

LINE-NO

SAJE-WORK-TEMP-TRANS-LINE- 443 003 N 0 Trans line number

NO
SAJE-WORK-TEMP-TRANS-LINE- 446 002 N 0 Trans line suffix

SUFF
SAJE-WORK-TEMP-HIGHEST- 448 003 N 0 -

PRESET
FILLER 451 062 X - -
FILLER 513 512 X - -


SAJE-WORK-Q4-REC-TYPE 001 001 X - Record Type Value "Q"

REF
SAJH-WORK-QUERY4-REC-TYPE 040 001 X - Record type

SEQ
SAJE-WORK-Q4-TRANS-TOTALS 048 040 X - Trans totals
SAJE-WORK-Q4-T-UNPOST- 088 040 X - Unposted total

TOTALS
SAJE-WORK-Q4-HIGHEST-LINE- 128 003 N 0 Highest line no

NO
SAJE-WORK-Q4-HIGHEST- 131 003 N 0 Highest preset

PRESET

SAJE-WORK-Q4-TEMP-TOTALS 134 160 X - Temp totals
SAJE-WORK-Q4-PRIOR-ACC- 294 001 X - Prior account type B

TYPE-B
SAJE-WORK-Q4-PRIOR-ACC- 295 001 X - Prior account type O

TYPE-O
SAJE-WORK-Q4-CUR-PRESET- 296 003 N 0 Current preset line number

LINENO
SAJE-WORK-Q4-DISPLAY-CONV 299 001 X - Display conversion
SAJE-WORK-Q4-CONV-CODE- 300 001 X - Conversion code control

CONTROL
FILLER 301 069 X - -

Query record 4, see SAJEWORK.CPY – (continued)

SAJE-WORK-Q4-STR-ACC-TYPE 370 001 X - Account type
FILLER 371 142 X - -
FILLER 513 512 X - -

Query 5 record, see SAJEWORK.CPY

SAJE-WORK-Q5-REC-TYPE 001 001 X - Record Type Value "Q"
SAJH-WORK-QUERY5-TYPE 033 001 X - Type "2"
SAJH-WORK-QUERY5-JOURNAL- 035 005 N 0 Journal Reference

REF
SAJH-WORK-QUERY5-REC-TYPE 040 001 X - Record type "Q"
SAJH-WORK-QUERY5-JOURNAL- 041 007 N 0 Journal Sequence number

SEQ
FILLER 048 002 X - -
FILLER 050 020 X - -
SAJE-WORK-Q5-PREV-LINE- 070 361 X - Previous Line data

DATA
SAJE-WORK-Q5-PREV-JOURNAL- 431 043 X - Previous Journal data

DATA

AJE-WORK-Q5-PREV-TRANS- 474 020 X - Previous Trans data

DATA
SAJE-WORK-Q5-PREV-LINE-NO 494 003 N 0 Previous Line number
SAJE-WORK-Q5-PREV-LINE-NO- 497 002 N 0 Previous line suffix

SUFF
FILLER 499 014 X - -
FILLER 513 512 X - -

Journal Hold Control record, see SAJEWORK.CPY

SAJE-WORK-HOLD-J-REC-TYPE 001 001 X - Record Type Key 1 Mandatory Value "Z"
SAJE-WORK-HOLD-J-FILLER 002 020 X - - Value "00000000000000000000"
SAJE-WORK-HOLD-J-REC-TYPE- 022 001 X - Record Type Key 2 Mandatory Value "Z"

2
SAJE-WORK-HOLD-J-FILLER-2 023 010 X - - Value "0000000000"
SAJH-WORK-HOLD-J-TYPE 033 001 X - Journal Held Type Value "5"
SAJH-WORK-HOLD-J-AB 034 001 X - Journal Held Actual/Budget
SAJH-WORK-HOLD-J-JOURNAL- 035 005 N 0 Journal Held Reference

REF
SAJH-WORK-HOLD-L-REC-TYPE 040 001 X - Journal Held Record Type
SAJH-WORK-HOLD-J-JOURNAL- 041 007 N 0 Journal Held Sequence Number

SEQ
SAJE-WORK-HOLD-J-REFERENCE 048 005 N 0 Reference
SAJE-WORK-HOLD-J-OPERATOR 053 003 X - Operator Id
FILLER 056 457 X - -
FILLER 513 512 X - -

Journal Hold Version record, see SAJEWORK.CPY

FILLER 001 032 X - -
SAJH-VERSION-TYPE 033 001 X - Journal Held Type Mandatory Type "4"
SAJH-VERSION-AB 034 001 X - Journal Held Actual/Budget
SAJH-VERSION-JOURNAL-REF 035 005 N 0 Journal Held Reference
SAJH-VERSION-REC-TYPE 040 001 X - Journal Held Record Type
SAJH-VERSION-JOURNAL-SEQ 041 007 N 0 Journal Held Sequence Number
SAJH-VERSION 048 003 N 0 Version Number
SAJH-LAN-CODE 051 002 N 0 Language Code
FILLER 053 460 X - -
FILLER 513 512 X - -

Journal Hold Actual/Budget record, see SAJEWORK.CPY

FILLER 001 032 X - -
SAJH-CONTROL-TYPE 033 001 X - Journal Held Type Mandatory Type "0"
SAJH-CONTROL-AB 034 001 X - Journal Held Actual/Budget
SAJH-CONTROL-JOURNAL-REF 035 005 N 0 Journal Held Reference
SAJH-CONTROL-REC-TYPE 040 001 X - Journal Held Record Type
SAJH-CONTROL-JOURNAL-SEQ 041 007 N 0 Journal Held Sequence Number
SAJH-CONTROL-NEXT-REF 048 005 N 0 Next Journal Reference
FILLER 053 460 X - -
FILLER 513 512 X - -

Journal Hold Journal record, see SAJEWORK.CPY

FILLER 001 032 X - -
SAJH-JOURNAL-C-TYPE 033 001 X - Journal Held Type Mandatory Type "1"
SAJH-JOURNAL-C-AB 034 001 X - Journal Held Actual/Budget
SAJH-JOURNAL-C-JOURNAL-REF 035 005 N 0 Journal Held Reference
SAJH-JOURNAL-C-REC-TYPE 040 001 X - Journal Held Record Type
SAJH-JOURNAL-C-JOURNAL-SEQ 041 007 N 0 Journal Held Sequence Number
SAJH-JOURNAL-C-JT 048 005 X - Journal Type
SAJH-JOURNAL-C-JS 053 005 X - Journal Source
SAJH-JOURNAL-C-CHANGED 058 008 N 0 Date Last Changed
SAJH-JOURNAL-C-TRANS-CT 066 007 N 0 Count of Transactions
SAJH-JOURNAL-C-DEBIT 073 010 N 3 Base Total Debit PIC 9(15) V9(3) COMP-3
SAJH-JOURNAL-C-CREDIT 083 010 N 3 Base Total Credit PIC 9(15) V9(3) COMP-3
SAJH-JOURNAL-C-OPERATOR 093 003 X - Operator Id
SAJH-JOURNAL-C-BUSY 096 001 X - Journal in Use
SAJH-JOURNAL-C-ROUGH 097 001 X - Rough Source
SAJH-JOURNAL-C-NUMBER 098 007 N 0 Journal Number if Rough Source

FILLER 105 408 X - -
FILLER 513 512 X - -

In SQL versions, the data is stored in the following table, called SAQFHLDxxx:
Oracle Field name Field type

/ SQL
DATA_1 char (32)
KEY_FIELDS char (15)
O DATA_2 char (250)
S DATA_2 binary (250)
O DATA_3 char (221)
S DATA_3 char (221)
Note: Oracle (O) fields have different datatype to SQL Server fields (S).
Purchase import file

Description
The purchase import file holds details of purchase orders, GRN’s and invoices to be used
to update the purchase order master file, via the Purchase Import function within
SunBusiness Purchase Order Processing.
Summary of record
There are the following record types on the purchase import file:
 Order Header record
 Order Detail record
 Order Description record
 GRN Header record
 GRN Detail record
 Invoice Header Record
 Invoice Detail record
 Direct Invoice Header record
 Direct Invoice Detail record
 Direct Invoice Description record

Purchase Import Order Header record, see SPPIRC.CPY

OENTH-TYPE 001 005 X - Record type Value ‘OENTH’ , mandatory
OENTH-OPERATOR-ID 006 003 X - Operator I.D.
OENTH-REF-PREFIX 009 004 X - Order Reference prefix
OENTH-REF-SUFFIX 013 006 X - Order Reference suffix
OENTH-SUPP-ADDRESS 019 010 X - Supplier Address Code
OENTH-ORDER-DATE 029 008 X - Order Date
OENTH-SECOND-REF 037 010 X - Second Reference
OENTH-ORDER-STATUS-1 047 001 N - Order status 1 Value may be :

0 = Held
3 = Released
6 = Issued (Printed)
OENTH-TRANS-TYPE 048 005 X - Transaction Type
OENTH-DEL-ADDRESS 053 010 X - Delivery Address Code
OENTH-COMMENTS 063 025 X - Comments
OENTH-ACK-REF 088 010 X - Acknowledgement Reference
OENTH-ACK-DATE 098 008 X - Acknowledgement Date
OENTH-DEL-DATE 106 008 X - Delivery Date

OENTH-DEL-ADVISED 114 001 X - Delivery Advised
OENTH-ORDER-PERIOD 115 007 X - Period Ordered
OENTH-ANAL-CODE 122 150 X - Analysis Codes 10 x 15 bytes
OENTH-DOC-ISSUE-DATE 272 008 X - Document Issue Date
OENTH-DEL-AUX 280 210 X - Auxiliary Delivery Address 6 x 35 bytes
FILLER 490 211 X - -

Purchase Import Order Detail record, see SPPIRC.CPY

OENTI-TYPE 001 005 X - Record Type Value ‘OENTI’, mandatory
OENTI-UP-BPC 006 001 X - Update Base Cost Indicator
OENTI-OPERATOR-ID 007 003 X - Operator I.D.
OENTI-REF-PREFIX 010 004 X - Order Reference Suffix
OENTI-REF-SUFFIX 014 006 X - Order Reference Prefix
OENTI-LINE-NO-A 020 003 N - Transaction Line Number A
OENTI-LINE-NO-B 023 001 X - Transaction Line Number B
OENTI-LOCATION 024 005 X - Location Code
OENTI-ITEM-CODE 029 015 X - Item Code
OENTI-SUPP-ITEM-DESC 044 030 X - Supplier Item Description
OENTI-DEL-DATE 074 008 X - Delivery Date
OENTI-DEL-ADVISED 082 001 X - Delivery Advised
OENTI-ORDER-STATUS-1 083 001 N - Order Status 1 Value may be :

0 = Held
6 = Issued (printed)
OENTI-ORDER-STATUS-2 084 001 N - Order status 2 Value may be :

0 = O.K.

1 = Cancelled
2 = Undelivered
OENTI-PURCH-QTY 085 019 N - Purchase quantity PIC S9(13)V9(5)

Leading sign separate
OENTI-STOCK-QTY 104 019 N - Stock Quantity PIC S9(13)V9(5)

OENTI-BASE-COST 123 019 N - Base Purchase Cost PIC S9(13)V9(5)

OENTI-CALC-VALUE 142 323 N - Calculation Values 17 x 19 bytes PIC S9(13)V9(5)

OENTI-ACCOUNT-CODE 465 010 X - Account Code
OENTI-ASSET-CODE 475 010 X - Asset Code
OENTI-ASSET-SUB-CODE 485 005 X - Asset Subcode
OENTI-ANAL-CODE 490 150 X - Analysis Code 10 x 15 bytes
FILLER 640 061 X - -

Purchase Import Order Description record, see SPPIRC.CPY

OENTT-TYPE 001 005 X - Record Type
OENTT-OPERATOR-ID 006 003 X - Operator I.D.
OENTT-REF-PREFIX 009 004 X - Order Reference Prefix
OENTT-REF-SUFFIX 013 006 X - Order reference Suffix
OENTT-LINE-NO-A 019 003 N - Transaction Line Number A
OENTT-LINE-NO-B 022 001 X - Transaction Line Number B
OENTT-ITEM-CODE 023 015 X - Item Code
OENTT-SUPP-ITEM-DESC 038 030 X - Suppliers Item Description
FILLER 068 633 X - -

Purchase Import GRN Header record, see SPPIRC.CPY

OGRNH-TYPE 001 005 X - Record Type
OGRNH-TOTAL-QTY 006 019 N - Total Quantity PIC S9(13)V9(5)

OGRNH-OPERATOR-ID 025 003 X - Operator I.D.
OGRNH-REF-PREFIX 028 004 X - Order Reference Prefix
OGRNH-REF-SUFFIX 032 006 X - Order reference Suffix
OGRNH-SUPP-GRN-REF 038 010 X - Suppliers GRN Reference
OGRNH-GRN-DATE 048 008 X - GRN Date
OGRNH-COMMENTS 056 025 X - Comments
OGRNH-PAYMENT-DATE 081 008 X - Payment Date
FILLER 089 612 X - -

Purchase Import GRN Detail record, see SPPIRC.CPY

OGRNI-TYPE 001 005 X - Record Type
OGRNI-POST-PERIOD 006 007 X - Posting Period
OGRNI-OPERATOR-ID 013 003 X - Operator I.D.
OGRNI-REF-PREFIX 016 004 X - Order Reference Prefix
OGRNI-REF-SUFFIX 020 006 X - Order Reference Suffix
OGRNI-GRN-REFERENCE 026 010 X - GRN Reference
OGRNI-LINE-NO-A 036 003 N - Line Number A
OGRNI-LINE-NO-B 039 001 X - Line Number B
OGRNI-STATUS-1 040 001 N - GRN Status 1 Value may be:

1 = Matched (Held)
2 = Matched (Held), Approved (Held)
3 = Matched (Released)
4 = Matched (Released), Approved
(Held)
(Released)
OGRNI-STATUS-2 041 001 N - GRN Status 2 Value may be:

0 = O.K.
1 = Cancelled
2 = Undelivered
4 = Over delivered

OGRNI-PURCH-QTY 042 019 N - Purchase Quantity PIC S9(13)V9(5)

OGRNI-RECEIPT-REF 061 015 X - Receipt Reference
OGRNI-AUDIT-DATE 076 008 X - Audit Date
FILLER 085 617 X - -

Purchase Import Invoice Header record, see SPPIRC.CPY

OINVH-TYPE 001 005 X - Record Type
OINVH-OPERATOR-ID 006 003 X - Operator I.D.
OINVH-TOTAL-QTY 009 019 N - Total Invoice Quantity PIC S9(13)V9(5)

OINVH-TOTAL-VALUE 028 019 N - Total Invoice Value PIC S9(13)V9(5)

OINVH-REF-PREFIX 047 004 X - Order Reference prefix
OINVH-REF-SUFFIX 051 006 X - Order Reference Suffix
OINVH-SUPP-INV-REF 057 010 X - Suppliers Invoice Reference
OINVH-INV-DATE 067 008 X - Invoice date
OINVH-COMMENTS 075 025 X - Comments
OINVH-PAY-DATE 100 008 X - Payment Date
OINVH-INV-PERIOD 108 007 X - Period Invoiced
FILLER 115 586 X - -

Purchase Import Invoice Detail record, see SPPIRC.CPY

OINVI-TYPE 001 005 X - Record Type
OINVI-OPERATOR-ID 006 003 X - Operator I.D.
OINVI-UP-BPC 009 001 X - Update Base Base Cost Indicator
OINVI-REF-PREFIX 010 004 X - Order Reference Preffix
OINVI-REF-SUFFIX 014 006 X - Order Reference Suffix
OINVI-INV-REFERENCE 020 010 X - Invoice reference
OINVI-LINE-NO-A 030 003 N - Line Number A
OINVI-LINE-NO-B 033 001 X - Line Number B
OINVI-DEL-DATE 034 008 X - Delivery Date
OINVI-DEL-ADVISED 042 001 X - Delivery advised
OINVI-STATUS-1 043 001 N - Invoice Status 1 Value may be:

1 = Matched (Held)
(Held)
(Released)
OINVI-STATUS-2 044 001 N - Invoice Status 2 Value may be:

0 = O.K.

1 = Cancelled
2 = Undelivered
OINVI-PURCH-QTY 045 019 N - Purchase Quantity PIC S9(13)V9(5)

OINVI-STOCK-QTY 064 019 N - Stock Quantity PIC S9(13)V9(5)

OINVI-BASE-COST 083 019 N - Base Cost PIC S9(13)V9(5)

OINVI-CALC-VALUE 102 323 N - Calculation Values 17 x 19 bytes PIC S9(13)V9(5)

OINVI-INV-PERIOD 425 007 X - Period Invoiced
OINVI-INV-APP-DATE 432 008 X - Invoice Approval Date
OINVI-RECEIPT-REF 440 015 X - Receipt Reference

Purchase Import Invoice Detail record, see SPPIRC.CPY – (continued)

OINVI-AUDIT-DATE 455 008 X - Audit date
OINVI-ACCOUNT-CODE 463 010 X - Account Code
OINVI-ASSET-CODE 473 010 X - Asset Code
OINVI-ASSET-SUB-CODE 483 005 X - Asset Sub Code
FILLER 488 213 X - -

Purchase Import Direct Invoice Header record, see SPPIRC.CPY

DINVH-TYPE 001 005 X - Record Type
DINVH-TOTAL-QTY 006 019 N - Total Invoice Quantity PIC S9(13)V9(5)

DINVH-TOTAL-VALUE 025 019 N - Total Invoice Value PIC S9(13)V9(5)

DINVH-OPERATOR-ID 044 003 X - Operator I.D.
DINVH-REF-PREFIX 047 004 X - Order Reference Prefix
DINVH-REF-SUFFIX 051 006 X - Order Reference Suffix
DINVH-SUP P-ADDRESS 057 010 X - Suppliers Address Code
DINVH-INV-DATE 067 008 X - Invoice Date
DINVH-SUPP-INV-REF 075 010 X - Suppliers Invoice Reference
DINVH-TRANS-TYPE 085 005 X - Transaction Type
DINVH-DEL-ADDRESS 090 010 X - Delivery Address Code
DINVH-COMMENTS 100 025 X - Comments
DINVH-PAY-DATE 125 008 X - Payment Date
DINVH-INV-PERIOD 133 007 X - Period Invoiced
DINVH-ANAL-CODE 140 150 X - Analysis Codes 10 x 15 bytes

DINVH-DEL-AUX 290 210 X - Auxiliary Delivery Address 6 x 35 bytes
FILLER 500 201 X - -

Purchase Import Direct Invoice Detail record, see SPPIRC.CPY

DINVI-TYPE 001 005 X - Record Type
DINVI-POST-PERIOD 006 007 X - Posting Period
DINVI-UP-BPC 013 001 X - Update Base Cost Indicator
DINVI-OPERATOR-ID 014 003 X - Operator I.D.
DINVI-REF-PREFIX 017 004 X - Order Reference Prefix
DINVI-REF-SUFFIX 021 006 X - Order reference Suffix
DINVI-INV-REFERENCE 027 010 X - Invoice Reference
DINVI-LINE-NO-A 037 003 N - Line number A
DINVI-LINE-NO-B 040 001 X - Line Number B
DINVI-LOCATION 041 005 X - Location
DINVI-ITEM-CODE 046 015 X - Item Code
DINVI-SUPP-ITEM-DESC 061 030 X - Suppliers Item Description
DINVI-DEL-DATE 091 008 X - Delivery Date
DINVI-DEL-ADVISED 099 001 X - Delivery Advised
DINVI-INVOICE-STATUS-1 100 001 N - Invoice Status 1 Value may be:

1 = Matched (Held)

4 = Matched (Released), Approved (Held)

5 = Matched (Released), Approved (Released)
DINVI-INVOICE-STATUS-2 101 001 N - Invoice Status 2 Value may be:

0 = O.K.
1 = Cancelled
2 = Undelivered
DINVI-PURCH-QTY 102 019 N - Purchase Quantity PIC S9(13)V9(5)

DINVI-STOCK-QTY 121 019 N - Stock Quantity PIC S9(13)V9(5)

DINVI-BASE-COST 140 019 N - Base Cost PIC S9(13)V9(5)

DINVI-CALC-VALUE 159 323 N - Calculation Values 17 x 19 bytes PIC S9(13)V9(5)


Purchase Import Direct Invoice Detail record, see SPPIRC.CPY – (continued)

DINVI-ACCOUNT-CODE 482 010 X - Account Code
DINVI-ASSET-CODE 492 010 X - Asset Code
DINVI-ASSET-SUB-CODE 502 005 X - Asset Sub Code
DINVI-RECEIPT-REF 507 015 X - Receipt Reference
DINVI-AUDIT-DATE 522 008 X - Audit Date
DINVI-ANAL-CODE 530 150 X - Analysis Codes 10 x 15 bytes
FILLER 680 021 X - -

Purchase Import Direct Invoice Description record, see SPPIRC.CPY

DINVT-TYPE 001 005 X - Record Type
DINVT-OPERATOR-ID 006 003 X - Operator I.D.
DINVT-REF-PREFIX 009 004 X - Order Reference Prefix
DINVT-REF-SUFFIX 013 006 X - Order Reference Suffix
DINVT-INV-REFERENCE 019 010 X - Invoice Reference
DINVT-LINE-NO-A 029 003 N - Line Number A
DINVT-LINE-NO-B 032 001 X - Line Number B
DINVT-ITEM-CODE 033 015 X - Item Code
DINVT-SUPP-ITEM-DESC 048 030 X - Suppliers Item Description
FILLER 078 623 X - -

Chapter 12 Appendix C – SunSystems v4
Backup Files 12
The backup files (created using FB=File Backup/Restore) are sequential text files with no
index keys. The records are variable length, and are terminated by carriage return, line feed
or line feed alone depending on the environment.
All backup files have a version control record, which is the first record on the file. This is the
same format on each file (see below). Note that some files have their own control record too,
which is not connected with the version control record.
The version control record has the following layout:
 bytes 01 to 07 contain the word ‘VERSION’
 bytes 08 to 32 contain spaces
 bytes 33 to 35 contain the version, currently ‘420’ in all cases
 bytes 36 to 37 contain the language code.
The backup files are compatible over all operating systems.
Reference backup file

Description
The reference backup file is called SSRF-ddd.BAK. Each record on the data file has a
corresponding record on the backup file.
The three character code at the beginning of each record identifies the record type. See the
subsection Standards for Reference Record Types, in the section Reference Maintenance,
for a complete list of the record types.
Reference backup file record descriptions
The layout of the records on this file is identical to the layout of the records on the master
indexed data file, SSRF-ddd.DAT. Therefore, see Appendix B: Master Data Files for the
record descriptions.
Ledger, budget and archive backup file

Description
The ledger backup file is called SALF-ddd.BAK. Note that the layout of this file is used as the
basis for the SunBusiness transfer file (see Appendix B). Note also that the budget backup
files and the archive backup files share the same record layout. Each record on the data file
has a corresponding record on the backup file.

Appendix C – SunSystems v4 Backup Files
There are the following record types on the ledger backup file:
 control record
There is one control (type ‘C’) record per file. Note that the SunBusiness transfer files also
have a control record, which is not the same as the ledger control record. There is one
transaction (type ‘L’) record for each transaction line posted to the ledger.
Note: Earlier formats of transaction backup records (Types ‘E’ and ‘T’) are still
available when using this layout for a SAF format import file to Journal Import.
Ledger backup file record descriptions
See Appendix B, subsection Ledger File Record Descriptions, for descriptions of the
individual fields on the record.

Transaction Backup record
COBOL POS’N IN FIELD FIELD DEC.

L-B-AC 001 015 X -
L-B-AP 016 007 N 0
L-B-DT 023 008 N 0
FILLER 031 002 X -
L-B-RECORD-TYPE 033 001 X -
L-B-JN 034 007 N 0
L-B-TN 041 007 N 0
L-B-AM-3DP 048 018 N 3
L-B-DC 066 001 X -
L-B-AI 067 001 X -
L-B-TT 068 005 X -
L-B-JR 073 005 X -
L-B-RF 078 015 X -
L-B-DS 093 025 X -
L-B-ED 118 008 N 0
L-B-EP 126 007 N 0
L-B-ADD-DATE 133 008 N 0
FILLER 141 006 X 0
L-B-ALLOC-RF 147 009 X -
L-B-ALLOC-DT 156 008 N 0


L-B-ALLOC-AP 164 007 N 0
L-B-ASSET-IND 171 001 X -
L-B-ASSET-CODE 172 010 X -
L-B-ASSET-SUB-CODE 182 005 X -
L-B-CONV-CODE 187 005 X -
L-B-CONV-RATE 192 018 N 9
L-B-OTHER-AM 210 018 N 3
L-B-OTHER-DP 228 001 X -
L-B-CLEARDOWN 229 005 N 0
FILLER 234 004 X -
L-B- REVERSAL 238 001 X -
L-B-LOSS-GAIN 239 001 X -
L-B-ROUGH-FLAG 240 001 X -
L-B-IN-USE-FLAG 241 001 X -
L-B-AN-0 242 015 X -
L-B-AN-1 257 015 X -
L-B-AN-2 272 015 X -
L-B-AN-3 287 015 X -
L-B-AN-4 302 015 X -
L-B-AN-5 317 015 X -
L-B-AN-6 332 015 X -
L-B-AN-7 347 015 X -


L-B-AN-8 362 015 X -
L-B-AN-9 377 015 X -
L-B-POSTING-DATE 392 008 N 0
L-B-UOB 400 001 X -
L-B-ALLOC-IN-PROGRESS 401 001 X -
L-B-HOLD-REF 402 005 N 0
L-B-HOLD-OP-ID 407 003 X -
L-B-BCHECK-ACCT 410 015 X -
L-B-ALLOC-MARKER-ID 425 003 X -
L-B-ALLOC-MARKER-DATE 428 008 N 0
FILLER 436 077 X -
Control Backup record

FILLER 001 032 X -
FILLER 033 001 X -
L-B-HIGHEST-JN 034 007 N 0
L-B-HIGHEST-CLEARDOWN 041 005 N 0
FILLER 046 002 X -
L-B-LANGUAGE-ID 048 002 N -
FILLER 050 001 X -
FILLER 051 248 X -


FILLER 299 214 X -
The ledger backup file record layout is also used as the import record layout for Journal
Import SunAccount Format (SAF) transactions. You may use the record layout above with
record type ‘M’, or if you wish you may use the version 4 record layout as described below.
Version 4.0

L-B-AC 001 015 X -
L-B-AP 016 007 N 0
L-B-DT 023 008 N 0
FILLER 031 002 X -
L-B-JN 034 007 N 0
L-B-TN 041 007 N 0
L-B-AM-3DP 048 018 N 3
L-B-DC 066 001 X -
L-B-AI 067 001 X -
L-B-TT 068 005 X -
L-B-JR 073 005 X -
L-B-RF 078 015 X -
L-B-DS 093 025 X -
L-B-ED 118 008 N 0
L-B-EP 126 007 N 0


L-B-PAID-RF 141 015 X -
L-B-PAID-DT 156 008 N 0
L-B-PAID-AP 164 007 N 0
L-B-CLEARDOWN 229 005 N 0
FILLER 234 006 X -
L-B-AN-1 240 005 X -
L-B-AN-2 245 005 X -
L-B-AN-3 250 005 X -
L-B-AN-4 255 005 X -
L-B-AN-5 260 005 X -
L-B-AN-EXTRA 265 034 X -
L-B-UOB 299 001 X -
FILLER 300 213 X -

The Control Backup record

FILLER 001 032 X -
FILLER 033 001 X -
L-B-HIGHEST-JN 034 007 N 0
L-B-HIGHEST-CLEARDOWN 041 005 N 0
FILLER 046 002 X -
L-B-LANGUAGE-ID 048 003 X -
FILLER 051 248 X -
FILLER 299 214 X -
Version 3
L-B-AC 001 010 X -
L-B-AP 011 004 N 0
L-B-DT 015 006 N 0
L-B-RF 021 010 X -
FILLER 031 002 X -
FILLER 034 001 X -
If Record Type is “T”
FILLER 035 008 - -
L-B-AM-2DP 035 010 N 2
If Record Type is “E”


L-B-AM-3DP 035 018 N 3
L-B-DC 053 001 X -
L-B-TT 054 005 X -
L-B-ED 059 006 N 0
L-B-AI 065 001 X -
L-B-JN 066 005 N 0
L-B-TN 071 005 N 0
L-B-JR 076 005 X -
L-B-EP 081 004 N 0
L-B-DS 085 030 X -
L-B-AN-1 115 005 X -
L-B-AN-2 120 005 X -
L-B-AN-3 125 005 X -
L-B-AN-4 130 005 X -
L-B-AN-5 135 005 X -
FILLER 169 001 X -


Sales order backup file

Description
The sales order backup file is called SOMF-ddd.BAK. Each record on the data file (SOMF-
ddd.DAT) has a corresponding record on the backup file. Note that the sales order import file
has the same layout as this file.
There are the following record types on the sales order backup file:
 the order header record
 the invoice header record
 the detail record.
See Appendix B, subsection Summary of Record Types, for further information about the
existence of the different types of record.
Sales order backup file record descriptions
See Appendix B, subsection Sales Order File Record Descriptions, for descriptions of the
individual fields on the records.
Sales Order/Invoice Header Backup record

FIELD NAME RECORD LENGT TYPE PLACE
H S
OHB3-TRANS-TYPE 001 001 X -
FILLER 002 005 X -
OHB3-TRANS-PREF 007 004 X -
OHB3-TRANS-SUFF 011 006 X 0
FILLER 017 005 X -


H S
OHB3-KEY-ID 022 001 X -
OHB3-CUSTOMER-CODE 023 010 X -
OHB3-TRANS-DATE 033 008 N 0
FILLER 041 014 X -
OHB3-STATUS-1 055 001 N 0
OHB3-STATUS-2 056 001 N 0
OHB3-TRANS-CD 057 001 X -
OHB3-TRANS-CODE 058 005 X -
FILLER 063 005 X -
OHB3-ORDER-NO 068 010 X -
OHB3-D-NOTE-NO 078 015 X -
OHB3-DELIVERY-CODE 093 010 X -
OHB3-DATE-ORDER 103 008 N 0
OHB3-DATE-ACKNOWLEDGED 111 008 N 0
OHB3-DATE-PICKED 119 008 N 0
OHB3-DATE-DELIVERED 127 008 N 0
OHB3-DATE-INVOICED 135 008 N 0
OHB3-PERIOD-INVOICED 143 007 N 0
OHB3-CUSTOMER-REF 150 025 X -
OHB3-COMMENTS 175 025 X -
OHB3-TRANS-VALUE 200 019 S 5 (Leading sign separate)


H S
OHB3-PAYMENT-DUE-DATE 219 008 X -
OHB3-ANALYSIS-ADDRESS 227 001 X -
OHB3-LINKED-TEXT 228 001 X -
OHB3-ANALYSIS-CODE-0 229 015 X -
OHB3-QUOTE-CONVERT 379 001 X -
OHB3-QUOTE-PRINT 380 001 X -
OHB3-QUOTE-EXPIRY-DATE 381 008 N 0
OHB3-PERIOD-QUOTED 389 007 N 0
FILLER 396 005 X -
OHB3-QUOTATION-REF 401 010 X -
OHB3-DATE-QUOTED 411 008 N 0
OHB3-VOID-STATUS 419 001 X -


H S
OHB3-EXTRA-CUST-CODE1 420 010 X -
OHB3-EXTRA-CUST-CODE2 430 010 X -
OHB3-EXTRA-TEXT1 440 030 X -
OHB3-EXTRA-VALUE1 565 019 S 5
FILLER 622 176 - -
Sales Order Detail Backup record

FIELD NAME RECORD LENGTH TYPE PLACE
S
SDB3-TRANS-TYPE 001 001 X -
FILLER 002 005 X -
SDB3-TRANS-PREF 007 004 X -
SDB3-TRANS-SUFF 011 006 X -


S
SDB3-TRANS-LINE- 017 003 N 0

NUMBER
SDB3-TRANS-LINE-SUFF 020 002 X -
SDB3-KEY-ID 022 001 X -
SDB3-LOCATION 023 005 X -
SDB3-ITEM-CODE 028 015 X -
SDB3-TRANS-DATE 043 008 N 0
SDB3-SEQUENCE 051 004 N 0
SDB3-STATUS-1 055 001 N 0
SDB3-STATUS-2 056 001 N 0
SDB3-TRANS-CD 057 001 X -
SDB3-ITEM- 058 030 X -

DESCRIPTION
SDB3-VALUE-1 088 019 S 5 (Leading sign separate)


S
SDB3-TRANS-CODE 468 005 X -
SDB3-DATE-DELIVERED 473 008 N 0
SDB3-DATE-INVOICED 481 008 N 0
SDB3-PERIOD-ORDERED 489 007 N 0
SDB3-PERIOD-INVOICED 496 007 N 0
SDB3-UNIT-SALE 503 005 X -
FILLER 508 005 X -
SDB3-INVOICE-NO 513 010 X -
SDB3-ACK-PRINT 523 001 X -
SDB3-MISC-PRINT 524 001 X -


S
SDB3-ALLOCATION-REF 525 019 X -
SDB3-RECPT-REF 544 015 X -
SDB3-LINE-ANAL-IND 559 001 X -
SDB3-ACCOUNT-CODE 560 015 X -
SDB3-ASSET-CODE 575 010 X -
SDB3-ASSET-SUB-CODE 585 005 X -
SDB3-ASSET-IND 590 001 X -
SDB3-ID-ENTERED 591 003 X -
SDB3-ID-INVOICED 594 003 X -
SDB3-LINKED-TEXT 597 001 X -
SDB3-ANALYSIS-CODE-0 598 015 X -
SDB3-ASSEMBLY-IND 748 001 X -


S
SDB3-ASSEMBLY-DESC- 749 001 X -

IND
SDB3-ASSEMBLY-LEVEL- 750 001 X -

IND
SDB3-PRICE-BOOK 751 005 X -
SDB3-SALES-QTY-VALUE 756 002 N 0
SDB3-STOCK-QTY-VALUE 758 002 N 0
SDB3-TOTAL-VALUE 760 002 N 0
SDB3-DISPLAY-VALUE-1 762 002 N 0
SDB3-MISC-DOC- 768 001 X -

PRINT(1)

PRINT(2)

PRINT(3)

PRINT(4)

PRINT(5)
SDB3-D-NOTE-NO 773 010 X -
SDB3-AUDIT-DATE 783 008 N 0
FILLER 791 007 X -

Sales Order Detail Extra Backup record

ODXB-TRANS-TYPE 001 001 X -
FILLER 002 005 X -
ODXB-TRANS-PREF 007 004 X -
ODXB-TRANS-SUFF 011 006 X -
ODXB-TRANS-LINE- 017 003 N 0

NUMBER
FILLER 020 005 X -
FILLER 025 033 X -
ODXB-ORIG-QTY 055 019 S 5
ODXB-AMB-TEMP 074 019 S 5
ODXB-AMB-VOLUME 093 019 S 5
ODXB-AMB-WEIGHT 112 019 S 5
ODXB-AMB-DENSITY 131 019 S 5
ODXB-AMB-PROD-DENS 150 019 S 5
ODXB-AMB-PROD-TEMP 169 019 S 5
ODXB-AMB-HCF 188 001 N 0
ODXB-AMB-DATE 189 008 N 0
FILLER 197 631 - -

Movement file
Description
The movement backup file is called SMMF-ddd.BAK. Each record on the data file has a

 the movement record
 the summary record.
See Appendix B, subsection The Movement File, for more details about the existence of the
different types of record.
Movement backup file record descriptions
See Appendix B, subsection Movement File Record Descriptions, for descriptions of the

MCB3-REC-TYPE 001 001 X -
MCB3-CONTROL 002 019 X -
MCB3-KEY-ID 021 001 X -
FILLER 022 032 X -
FILLER 054 003 X -
MCB3-HIGHEST-BATCH 057 005 N 0
MCB3-HIGHEST-USAGE 062 009 N 0
MCB3-LANGUAGE 071 003 X -
FILLER 074 342 X -

Movement Backup record
COBOL POS’N FIELD FIELD DEC.

FIELD NAME IN LENGTH TYPE PLACE
RECORD S
MMB3-REC-TYPE 001 001 X -
MMB3-MVT-REF 002 015 X -
MMB3-MVT-LINE-NO 017 004 N 0
MMB3-KEY-ID 021 001 X -
MMB3-LOCATION 022 005 X -
MMB3-ITEM-CODE 027 015 X -
MMB3-MVT-DATE 042 008 N 0
MMB3-SEQUENCE 050 004 N 0
MMB3-STATUS-1 054 001 N 0
MMB3-STATUS-2 055 001 N 0
MMB3-RI-IND 056 001 X -
MMB3-BATCH-NO 057 005 N 0
MMB3-BATCH-LINE-NO 062 005 N 0
MMB3-RECPT-REF 067 015 X -
MMB3-MVT-QTY 082 019 S 5 (Leading sign separate)
MMB3-VALUE-1 101 019 S 5 (Leading sign separate)
FILLER 158 001 X -
MMB3-PERIOD-POSTED 159 007 N 0


RECORD S
MMB3-UNIT-STOCK 166 005 X -
MMB3-MVT-CODE 171 005 X -
MMB3-UPDATE-PHYSICAL 176 001 X -
MMB3-UPDATE-ON-ORDER 177 001 X -
MMB3-ALLOCATION-REF 178 020 X -
MMB3-AUDIT-DATE 198 008 N 0
MMB3-SERIAL-NO-INDEX 206 001 X -
MMB3-LINKED-TEXT 207 001 X -
MMB3-ID-ENTERED 208 003 X -
MMB3-ID-ALLOCATED 211 003 X -
MMB3-ACCOUNT-CODE 214 015 X -
MMB3-ASSET-CODE 229 010 X -
MMB3-ASSET-SUB-CODE 239 005 X -
MMB3-ANALYSIS-CODE-0 244 015 X -


RECORD S
MMB3-PO-LINE-NO-A 394 003 N -
MMB3-PO-LINE-NO-B 397 001 X -
MMB3-PO-VALUE 398 018 N -

Stock take backup file

Description
The stock take backup file is called SMKF-ddd.BAK. Each record on the data file has a
 the header record
See Appendix B, subsection The Stock Take File, for more details about the existence of
these records.
Stock take backup file record descriptions
See Appendix B, subsection Stock Take File Record Descriptions, for descriptions of the

TC-BK-REC-TYPE 001 001 X -
FILLER 002 055 X -
TC-BK-KEY-ID 057 001 X -
FILLER 058 020 X -
TC-BK-VERSION-NO 078 003 X -
TC-BK-NEXT-STOCK- 081 005 N 0

TAKE-NO
FILLER 086 501 X -
Stock Take Header Backup record

TH-BK-REC-TYPE 001 001 X -


TH-BK-STOCK-TAKE-NO 002 005 N 0
FILLER 007 050 X -
TH-BK-KEY-ID 057 001 X -
FILLER 058 020 X -
TH-BK-PERIOD- 078 007 N 0

EXTRACTED
TH-BK-STOCK-TAKE-CODE 085 005 X -
TH-BK-STOCK-TAKE-SEQ 090 004 X -
TH-BK-OPERATOR-ID 094 003 X -
TH-BK-STOCK-TAKE-DATE 097 008 N 0
TH-BK-ANALYSIS- 105 002 X -

CATEGORY
FILLER 107 480 X -

Stock Take Detail Backup record

TD-BK-REC-TYPE 001 001 X -
TD-BK-STOCK-TAKE-NO 002 005 N 0
TD-BK-COMPOSITE-KEY 007 050 X -
TD-BK-KEY-ID 057 001 X -
TD-BK-ITEM-CODE 058 015 X -
TD-BK-LOCATION-CODE 073 005 X -
TD-BK-ANALYSIS-CODE 078 015 X -
TD-BK-STOCK-TAKE- 093 005 X -

CODE
TD-BK-STOCK-TAKE- 098 004 N 0

LINE-NO
TD-BK-RECEIPT- 102 015 X -

REFERENCE
TD-BK-OPERATOR-ENTER 117 003 X -
TD-BK-OPERATOR- 120 003 X -

APPROVED
TD-BK-OPERATOR- 123 003 X -

POSTED
TD-BK-PERIOD-POSTED 126 007 N 0
TD-BK-ORIGINAL-QTY 133 019 S 5 (Leading sign

separate)
TD-BK-ORIGINAL- 152 019 S 5 (Leading sign

VALUE-1 separate)



VALUE-2 separate)

VALUE-3 separate)
TD-BK-VARIANCE-QTY 209 019 S 5 (Leading sign

separate)
TD-BK-VARIANCE- 228 019 S 5 (Leading sign

VALUE-1 separate)

VALUE-2 separate)

VALUE-3 separate)
TD-BK-REPORT-COST 285 003 X -
TD-BK-UNIT-OF-STOCK 288 005 X -
TD-BK-MOVEMENT-CODE 293 005 X -
TD-BK-UPDATE- 298 001 X -

PHYSICAL
TD-BK-UPDATE-ON- 299 001 X -

ORDER
TD-BK-AUDIT-DATE 300 008 N 0
TD-BK-ACCOUNT-CODE 308 015 X -
TD-BK-ASSET-CODE 323 010 X -
TD-BK-ASSET-SUB-CODE 333 005 X -
TD-BK-STATUS 338 001 X -
TD-BK-CLEAR-ON-ORDER 339 001 X -
TD-BK-CNV-RATE-2 340 018 N 9


TD-BK-CNV-RATE-OP2 358 001 X -
TD-BK-CNV-OTHER-DP2 359 001 X -
TD-BK-CNV-RATE-3 360 018 N 9
TD-BK-CNV-RATE-OP3 378 001 X -
TD-BK-CNV-OTHER-DP3 379 001 X -
TD-BK-COST-1 380 019 S 5 (Leading sign

separate)

separate)

separate)
TD-BK-MVT-ANALYSIS- 437 015 X -

CODE-0

CODE-1

CODE-2

CODE-3

CODE-4

CODE-5

CODE-6

CODE-7



CODE-8

CODE-9
TD-BK-BIN-NAME 587 015 X -
Purchase order backup file

Description
The purchase order backup file is called SPMF-ddd.BAK. It contains the same data as the
purchase order file, in backup format.
There are the following record types on the purchase order backup file:
 the purchase order header record
 the goods received note header record
 the purchase invoice header record
See Appendix B, subsection The Purchase Order File, for further information about the
existence of these records.
Purchase order backup file record descriptions
See Appendix B, subsection Purchase Order File Record Descriptions, for descriptions of the

SPMFBK-C-REC-TYPE 001 001 X -
SPMFBK-C-CONTROL 002 019 X -
SPMFBK-C-KEY-1-ID 021 001 X -


FILLER 022 032 X -
SPMFBK-C-KEY-2-ID 054 001 X -
FILLER 055 015 X -
SPMFBK-C-VERSION 070 003 N 0
SPMFBK-C-LAST-GRN-REF 073 015 N 0
SPMFBK-C-LAST-INV-REF 088 015 N 0
SPMFBK-C-LANGUAGE 103 003 X -
FILLER 106 919 X -
Purchase Order Header Backup record

SPMFBK-J-REC-TYPE 001 001 X -
FILLER 002 005 X -
SPMFBK-J-REF-PREFIX 007 004 X -
SPMFBK-J-REF-SUFFIX 011 006 N 0
FILLER 017 004 X -
SPMFBK-J-KEY-1-ID 021 001 X -
SPMFBK-J-SUPP- 022 010 X -

ADDRESS
SPMFBK-J-ORDER-DATE 032 008 N 0
FILLER 040 014 X -
SPMFBK-J-KEY-2-ID 054 001 X -


SPMFBK-J-SECOND-REF 055 015 X -
SPMFBK-J-STATUS-1 070 001 N 0
SPMFBK-J-STATUS-2 071 001 N 0
SPMFBK-J-CD 072 001 X -
SPMFBK-J-TRANS-TYPE 073 005 X -
SPMFBK-J-DEL-ADDRESS 078 010 X -
SPMFBK-J-COMMENTS 088 025 X -
SPMFBK-J-ACK-REF 113 015 X -
SPMFBK-J-ACK-DATE 128 008 N 0
SPMFBK-J-DEL-DATE 136 008 N 0
SPMFBK-J-DEL-ADVISED 144 001 X -
SPMFBK-J-ORDER-VALUE 145 019 S 5 (Leading sign

separate)
SPMFBK-J-ORDER- 164 019 S 5 (Leading sign

QUANTITY separate)
SPMFBK-J-ORDER- 183 007 N 0

PERIOD
SPMFBK-J-LINKED-TEXT 190 001 X -
SPMFBK-J-ANAL-CODE-0 191 015 X -


SPMFBK-J-DOC-ISSUE- 341 008 N 0

DATE
SPMFBK-J-GRN-IND 349 001 X -
SPMFBK-J-ID-RELEASED 350 003 X -
SPMFBK-J-POST-UNAPP- 353 001 X -

GRN
FILLER 354 012 X -
SPMFBK-J-VOID-STATUS 366 001 X -
SPMFBK-J-EXTRA-SUPP- 367 010 X -

CODE1
SPMFBK-J-EXTRA-SUPP- 377 010 X -

CODE2
SPMFBK-J-EXTRA-TEXT1 387 030 X -


SPMFBK-J-EXTRA- 512 019 S 5

VALUE1

VALUE2

VALUE3
FILLER 569 456 - -
Goods Received Note Header Backup record

S
SPMFBK-K-REC-TYPE 001 001 X -
FILLER 002 005 X -
SPMFBK-K-REF-PREFIX 007 004 X -
SPMFBK-K-REF-SUFFIX 011 006 N 0
FILLER 017 004 X -
SPMFBK-K-KEY-1-ID 021 001 X -
SPMFBK-K-SUPP-ADDRESS 022 010 X -
SPMFBK-K-GRN-DATE 032 008 N 0
FILLER 040 014 X -
SPMFBK-K-KEY-2-ID 054 001 X -
SPMFBK-K-SUPP-GRN-REF 055 015 X -
SPMFBK-K-STATUS-1 070 001 N 0
SPMFBK-K-STATUS-2 071 001 N 0


S
SPMFBK-K-LINKED-TEXT 072 001 X -
SPMFBK-K-CD 073 001 X -
SPMFBK-K-DEL-ADDRESS 074 010 X -
FILLER 084 005 X -
SPMFBK-K-ORDER- 089 010 X -

REFERENCE
SPMFBK-K-MATCHED-TOT- 099 019 S 5 (Leading sign separate)

QTY
SPMFBK-K-GRN-TOT-QTY 118 019 S 5 (Leading sign separate)
SPMFBK-K-COMMENTS 137 025 X -
SPMFBK-K-ORDER-TRANS- 162 005 X -

TYPE
SPMFBK-K-ID-RELEASED 167 003 X -
SPMFBK-K-PAY-DATE 170 008 N O
SPMFBK-K-ORDER-DATE 178 008 N 0
FILLER 186 177 - -
SPMFBK-K-EXTRA-SUPP- 363 010 X -

CODE1
SPMFBK-K-EXTRA-SUPP- 373 010 X -

CODE2
SPMFBK-K-EXTRA-TEXT1 383 030 X -


S
SPMFBK-K-EXTRA-VALUE1 508 019 S 5
FILLER 565 210 X -
FILLER 775 459 X -
Purchase Invoice Header Backup record

SPMFBK-L-REC-TYPE 001 001 X -
FILLER 002 005 X -
SPMFBK-L-REF-PREFIX 007 004 X -
SPMFBK-L-REF-SUFFIX 011 006 N 0
FILLER 017 004 X -
SPMFBK-L-KEY-1-ID 021 001 X -
SPMFBK-L-SUPP- 022 010 X -

ADDRESS
SPMFBK-L-INV-DATE 032 008 N 0
FILLER 040 014 X -
SPMFBK-L-KEY-2-ID 054 001 X -


SPMFBK-L-SUPP-INV- 055 015 X -

REF
SPMFBK-L-STATUS-1 070 001 N 0
SPMFBK-L-STATUS-2 071 001 N 0
SPMFBK-L-CD 072 001 X -
SPMFBK-L-TRANS-TYPE 073 005 X -
FILLER 078 010 X -
SPMFBK-L-COMMENTS 088 025 X -
SPMFBK-L-PAY-DATE 113 008 N 0
SPMFBK-L-MATCHED- 121 019 S 5 (Leading sign

TOT-QTY separate)
SPMFBK-L-MATCHED- 140 019 S 5 (Leading sign

TOT-VAL separate)
SPMFBK-L-INV-PERIOD 159 007 N 0
SPMFBK-L-INV-TOT-QTY 166 019 S 5 (Leading sign

separate)
SPMFBK-L-INV-TOT-VAL 185 019 S 5 (Leading sign

separate)
FILLER 204 005 X -
SPMFBK-L-ORDER- 209 010 X -

REFERENCE
SPMFBK-L-LINKED-TEXT 219 001 X -
SPMFBK-L-ANAL-CODE-0 220 015 X -


SPMFBK-L-ID-RELEASED 370 003 X -
SPMFBK-L-ORDER-DATE 373 008 N 0
SPMFBK-L-VOID-STATUS 381 001 X -
SPMFBK-L-EXTRA-SUPP- 382 010 X -

CODE1
SPMFBK-L-EXTRA-SUPP- 392 010 X -

CODE2
SPMFBK-L-EXTRA-TEXT1 402 030 X -
SPMFBK-L-EXTRA- 527 019 S 5

VALUE1



VALUE2

VALUE3
SPMFBK-L-MATCHED- 584 019 S 5

TOT-VAL-2

TOT-VAL-3

TOT-VAL-4
SPMFBK-L-INV-TOT- 641 019 S 5

VAL-2

VAL-3

VAL-4
FILLER 698 327 - -
Purchase Order Detail Backup record

SPMFBK-S-REC-TYPE 001 001 X -
FILLER 002 005 X -
SPMFBK-S-REF-PREFIX 007 004 X -
SPMFBK-S-REF-SUFFIX 011 006 N 0
SPMFBK-S-LINE-NO-A 017 003 N 0
SPMFBK-S-LINE-NO-B 020 001 X -


SPMFBK-S-KEY-1-ID 021 001 X -
SPMFBK-S-LOCATION 022 005 X -
SPMFBK-S-ITEM-CODE 027 015 X -
SPMFBK-S-DEL-DATE 042 008 N 0
SPMFBK-S-SEQUENCE 050 004 N 0
SPMFBK-S-KEY-2-ID 054 001 X -
FILLER 055 005 X -
SPMFBK-S-HIGHEST- 060 010 X -

REFERENCE
SPMFBK-S-ORDER- 070 001 N 0

STATUS-1
SPMFBK-S-ORDER- 071 001 N 0

STATUS-2
SPMFBK-S-GRN-STATUS- 072 001 N 0

1
SPMFBK-S-GRN-STATUS- 073 001 N 0

2
SPMFBK-S-INVOICE- 074 001 N 0

STATUS-1
SPMFBK-S-INVOICE- 075 001 N 0

STATUS-2
SPMFBK-S-CD 076 001 X -
SPMFBK-S-LINKED-TEXT 077 001 X -
SPMFBK-S-ID-ORDER 078 003 X -
SPMFBK-S-ID-GRN 081 003 X -


SPMFBK-S-ID-INVOICED 084 003 X -
SPMFBK-S-SUPP-ITEM- 087 030 X -

DESC
SPMFBK-S-SUPP-ITEM- 117 015 X -

CODE
SPMFBK-S-PURCH-QTY 132 019 S 5 (Leading sign

separate)
SPMFBK-S-PURCH-UNIT 151 005 X -
SPMFBK-S-STOCK-QTY 156 019 S 5 (Leading sign

separate)
SPMFBK-S-BASE-COST 175 019 S 5 (Leading sign

separate)
SPMFBK-S-CALC-VALUE- 194 019 S 5 (Leading sign

1 separate)

2 separate)

3 separate)

4 separate)

5 separate)

6 separate)

7 separate)

8 separate)



9 separate)

10 separate)

11 separate)

12 separate)

13 separate)

14 separate)

15 separate)

16 separate)

17 separate)
FILLER 517 020 X -
SPMFBK-S-GRN- 537 010 X -

REFERENCE
SPMFBK-S-GRN-DATE 547 008 N 0
SPMFBK-S-DEL-ADVISED 555 001 X -
SPMFBK-S-INV-DATE 556 008 N 0
SPMFBK-S-INV-PERIOD 564 007 N 0
SPMFBK-S-INV-APPROV- 571 008 N 0

DATE


SPMFBK-S-TRANS-TYPE 579 005 X -
SPMFBK-S-STOCK- 584 001 X -

UPDATED
SPMFBK-S-REASON-CODE 585 001 X -
SPMFBK-S-LINE-VALUE 586 002 N 0
SPMFBK-S-MATCH-VALUE 588 002 N 0
SPMFBK-S-COST-VALUE 590 002 N 0
SPMFBK-S-ACCOUNT- 592 015 X -

CODE
SPMFBK-S-ASSET-CODE 607 010 X -
SPMFBK-S-ASSET-SUB- 617 005 X -

CODE
SPMFBK-S-ASSET-IND 622 001 X -
SPMFBK-S-RECEIPT-REF 623 015 X -
SPMFBK-S-AUDIT-DATE 638 008 N 0
SPMFBK-S-ANAL-CODE-0 646 015 X -


SPMFBK-S-UNAPP- 796 007 N 0

PERIOD-POSTED
SPMFBK-S-ORDER-DATE 803 008 N 0
SPMFBK-S-STOCK- 811 007 N 0

PERIOD-POSTED
SPMFBK-S-PERIOD- 818 007 N 0

ORDERED
SPMFBK-S-AMEND-DATE 825 008 N 0
SPMFBK-S-ORIG-LINE- 833 003 N 0

NO-A
SPMFBK-S-ORIG-LINE- 836 001 X -

NO-B
SPMFBK-S-MVT-VALUE 837 018 S 5
SPMFBK-S-BCHECK- 855 002 N 0

VALUE
SPMFBK-S-EXPEND- 857 002 N 0

CHECK-VALUE
SPMFBK-S-MISC-DOC- 859 001 X -

PRINT(1)

PRINT(2)

PRINT(3)

PRINT(4)



PRINT(5)
SPMFBK-S-ACV- 864 010 X -

INVOICE1

INVOICE2

INVOICE3

INVOICE4
FILLER 904 121 X -
Sales history backup file

Description
The sales history backup file is called SOHF-ddd.BAK. It contains the same data as the sales
history file, only in backup format.
There is the following record type on the sales history backup file:
 the usage record
See Appendix B, subsection The Sales History File, for further information about the
existence of the records. Note that there is no control record - except for the standard version
control record found on all backup files.
Sales history backup file record descriptions
See Appendix B, subsection Sales History File Record Descriptions, for descriptions of the

Sales History Usage Backup record

BDB3-TRANS-TYPE 001 001 X -
BDB3-PERIOD 002 007 N 0
BDB3-LOCATION 009 005 X -
BDB3-ITEM-CODE 014 015 X -
BDB3-TRANS-DATE 029 008 N 0
BDB3-TRANS-CD 037 001 X -
BDB3-VALUE-1 038 019 S 5 (Leading sign

separate)

separate)

separate)

separate)

separate)

separate)

separate)

separate)

separate)



separate)

separate)

separate)

separate)

separate)

separate)

separate)

separate)

separate)

separate)

separate)
BDB3-TRANS-CODE 418 005 X -
BDB3-CUSTOMER-CODE 423 010 X -
BDB3-ANALYSIS-CODE-0 433 015 X -


Purchase history backup file

Description
The purchase history backup file is called SPHF-ddd.BAK. It contains the same data as the
purchase history file, only in backup format.
There is the following record type on the purchase history backup file:
 the balance record
See Appendix B, subsection The Purchase History File, for further information about the
existence of these records.
Purchase history backup file record descriptions
See Appendix B, subsection Purchase History File Record Descriptions, for descriptions of
the individual fields on the records.
Balance Backup record

SPHFBK-S-REC-TYPE 001 001 X -
SPHFBK-S-INV-PERIOD 002 007 N 0


SPHFBK-S-LOCATION 009 005 X -
SPHFBK-S-ITEM-CODE 014 015 X -
SPHFBK-S-DEL-DATE 029 008 N 0
SPHFBK-S-CD 037 001 X -
SPHFBK-S-PURCH-QTY 038 019 S 5 (leading sign separate)
SPHFBK-S-STOCK-QTY 057 019 S 5 (leading sign separate)
SPHFBK-S-CALC-VALUE- 076 019 S 5 (leading sign separate)

1
SPHFBK -S-CALC- 095 019 S 5 (leading sign separate)

VALUE-2

3

4

5

6

7

8

9

10



11

12

13

14

15

16

17
SPHFBK-S-TRANS-TYPE 399 005 X -
SPHFBK-S-SUPPLIER- 404 010 X -

CODE
SPHFBK-S-REASON-CODE 414 001 X -
SPHFBK-S-ANAL-CODE-0 415 015 X -


Journal hold backup file

Description
The journal hold backup file is called SAQF-ddd.BAK. It contains the same data as the journal
hold file, only in backup format.
 the standard record

 the journal control record
 the analysis record
 the transaction control record
 the transaction line record
 the split record
 the allocation record
 the journal hold control record
 the period record
 the journal hold version record
 the journal hold journal record.
See Appendix B, subsection, The SunAccount Journal Hold File for further information about
the existence of these records.
Journal hold file record descriptions
See Appendix B, The SunAccount Journal Hold File for descriptions of individual fields on the
records.
Standard Backup record

SAJE-B-WORK-REC-TYPE 001 001 X -
SAJE-B-WORK-REFERENCE 002 015 X -
SAJE-B-WORK-LINE-NO 017 003 N 0


SAJE-B-WORK-LINE-NO- 020 002 N 0

SUFF
SAJE-B-WORK-REC-TYPE- 022 001 X -

2
SAJE-B-WORK-REF-ID 023 005 N 0
SAJE-B-WORK-LINE-NO-2 028 003 N 0
SAJE-B-WORK-LINE-NO- 031 002 N 0

2-SUFF
SAJH-B-WORK-TYPE 033 001 X -
SAJH-B-WORK-AB 034 001 X -
SAJH-B-WORK-JOURNAL- 035 005 N 0

REF
SAJH-B-WORK-REC-TYPE 040 001 X -
SAJH-B-WORK-JOURNAL- 041 007 N 0

SEQ
SAJE-B-WORK-DATA 048 465 X -
Journal Control Backup record

SAJE-B-WORK-C-REC-TYPE 001 001 X -
SAJE-B-WORK-C- 002 015 X -

REFERENCE
SAJE-B-WORK-C-LINE-NO 017 003 N 0
SAJE-B-WORK-C-LINE-NO- 020 002 N 0

SUFF


SAJE-B-WORK-C-REC- 022 001 X -

TYPE-2
SAJE-B-WORK-C-REF-ID 023 005 N 0

2

2-SUFF
SAJH-B-WORK-C-TYPE 033 001 X -
SAJH-B-WORK-C-AB 034 001 X -
SAJH-B-WORK-C-JOURNAL- 035 005 N 0

REF
SAJH-B-WORK-C-REC-TYPE 040 001 X -
SAJH-B-WORK-C-JOURNAL- 041 007 N 0

SEQ
SAJE-B-WORK-HIGHEST- 048 005 N 0

REF-ID
SAJE-B-WORK-CURRENT- 053 011 X -

KEY
SAJE-B-WORK-CURRENT- 064 003 N 0

FIELD

PERIOD

PRESET
SAJE-B-WORK-CURRENT- 077 001 X -

OVERLAY
SAJE-B-WORK-TOTAL- 078 001 X -

INDICATOR


SAJE-B-WORK-JT- 079 001 X -

INDICATOR
SAJE-B-WORK-ACTUAL- 080 001 X -

BUDGET
SAJE-B-WORK-AJD- 081 025 X -

JOURNAL-NAME

PRESET-CODE
SAJE-B-WORK-AJD-ANAL- 111 020 X -

CAT
SAJE-B-WORK-AJD-SUPP- 131 001 X -

AGEING
SAJE-B-WORK-AJD-DESC- 132 001 X -

PER-LINE
SAJE-B-WORK-AJD-FORCE- 133 001 X -

WITHHOLD
SAJE-B-WORK-AJD-NEXT- 134 001 X -

PER-REV
SAJE-B-WORK-AJD-DUE- 135 001 X -

DATE-ENTRY

UNIQUE-REFS

CREATENOPAUSE

CONVERSION
SAJE-B-WORK-AJD-ASSET- 139 001 X -

ENTRY
SAJE-B-SUPPRESS-JE 140 001 X -


SAJE-B-SUPPRESS-JI 141 001 X -
SAJE-B-SUPPRESS-AA 142 001 X -
SAJE-B-WORK-AJD-SEQ- 143 005 X -

CODE
SAJE-B-WORK-AJD-TRANS- 148 001 X -

SEQ
SAJE-B-WORK-AJD-IN- 149 015 X -

DISC-ACC
SAJE-B-WORK-AJD-OUT- 164 015 X -

DISC-ACC
SAJE-B-WORK-AJD-DISC- 179 011 N 2

TOL-PERC
SAJE-B-WORK-AJD-DISC- 190 012 N 3

TOL-VAL
SAJE-B-WORK-AJD-AUTO- 202 001 X -

TAX-IND
SAJE-B-WORK-AJD-TAX- 203 006 X -

ACC-INDS
SAJE-B-WORK-AJD-STP- 209 006 X -

ACC-INDS
SAJE-B-WORK-AJD-AUTO- 215 001 X -

TAX-ACC
SAJE-B-WORK-ANAL-LOC 216 020 X -
SAJE-B-WORK-JOURNAL- 236 005 X -

TYPE
SAJE-B-WORK-JOURNAL- 241 005 X -

SOURCE


SAJE-B-WORK-DATABASE- 246 003 X -

CODE
SAJE-B-WORK-JOURNAL- 249 007 N 0

NUMBER
SAJE-B-WORK-NUMBER-OF- 256 007 N 0

REFS
SAJE-B-WORK-AUTO-SEQ 263 001 X -
SAJE-B-WORK-ENTRY-DATE 264 008 N 0
SAJE-B-WORK-ENTRY- 272 007 N 0

PERIOD
SAJE-B-WORK-J-BASE- 279 018 N 3

TOTAL-D
SAJE-B-WORK-J-BASE- 297 018 N 3

TOTAL-C
SAJE-B-WORK-J-OTHER- 315 018 N 3

TOTAL-D
SAJE-B-WORK-J-OTHER- 333 018 N 3

TOTAL-C
SAJE-B-WORK-J-MEMO- 351 018 N 3

TOTAL-D
SAJE-B-WORK-J-MEMO- 369 018 N 3

TOTAL-C
SAJE-B-WORK-J-RATIO- 387 018 N 9

TOTAL-B
SAJE-B-WORK-J-RATIO- 405 018 N 9

TOTAL-O
SAJE-B-WORK-C-SOURCE- 423 001 X -

FLAG


SAJE-B-WORK-JOURNAL-NO 424 007 N 0
SAJE-B-WORK-NEXT-SEQ- 431 005 N 0

NO
SAJE-B-WORK-CURRENT-L- 436 032 X -

KEY
SAJE-B-WORK-LAST- 468 001 X -

TRANS-SEQ

OVERLAY
SAJE-B-WORK-NO-OF- 470 005 N 0

ALLOCATIONS
SAJE-B-WORK-NON-ROUGH 475 007 N 0
FILLER 482 030 X -

SELECTION
Analysis Backup record

SAJE-B-WORK-A-REC- 001 001 X -

TYPE
SAJE-B-WORK-A-FILLER 002 020 X -
SAJE-B-WORK-A-REC- 022 001 X -

TYPE-2
SAJE-B-WORK-A-FILLER- 023 010 X -

2
SAJH-B-WORK-ANALYSIS- 033 001 X -

TYPE



AB
SAJH-B-WORK-ANALYSIS- 035 005 N 0

JRNL-REF

REC-TYPE
SAJH-B-WORK-ANALYSIS- 041 007 N 0

JRNL-SEQ
SAJE-B-WORK-ANAL-CAT- 048 050 X -

SHORT-NAM
SAJE-B-WORK-ANAL-CAT- 098 200 X -

LONG-NAM
FILLER 298 215 X -
Transaction Control Backup record

RECORD S
SAJE-B-WORK-T-REC- 001 001 X -

TYPE
SAJE-B-WORK-T- 002 015 X -

REFERENCE
SAJE-B-WORK-T-LINE-NO 017 003 N 0
SAJE-B-WORK-T-LINE- 020 002 N 0

NO-SUFF
SAJE-B-WORK-T-REC- 022 001 X -

TYPE-2
SAJE-B-WORK-T-REF-ID 023 005 N 0


RECORD S

NO-2

NO-2-SUFF
SAJH-B-WORK-TRANS- 033 001 X -

TYPE
SAJH-B-WORK-TRANS-AB 034 001 X -
SAJH-B-WORK-TRANS- 035 005 N 0

JOURNAL-REF
SAJH-B-WORK-TRANS- 040 001 X -

REC-TYPE
SAJH-B-WORK-TRANS- 041 007 N 0

JOURNAL-SEQ

LINE-NO
SAJE-B-WORK-HIGH- 051 003 N 0

PRESET-USED
SAJE-B-WORK-T-BASE-D 054 019 S 3 (Leading sign separate)
SAJE-B-WORK-T-BASE-C 073 019 S 3 (Leading sign separate)
SAJE-B-WORK-T-OTHER-D 092 019 S 3 (Leading sign separate)
SAJE-B-WORK-T-OTHER-C 111 019 S 3 (Leading sign separate)
SAJE-B-WORK-TU-BASE-D 130 019 S 3 (Leading sign separate)
SAJE-B-WORK-TU-BASE-C 149 019 S 3 (Leading sign separate)
SAJE-B-WORK-TU-OTHER- 168 019 S 3 (Leading sign separate)

D


RECORD S
SAJE-B-WORK-TU-OTHER- 187 019 S 3 (Leading sign separate)

C
SAJE-B-WORK-TRANS- 206 007 N 0

SEQ-NUM
SAJE-B-WORK-NUMBER- 213 007 N 0

OF-TRANS
SAJE-B-WORK-NUMBER- 220 003 N 0

OF-SUFF
FILLER 223 290 X -
Transaction Line record

FIELD NAME IN LENGTH TYPE PLACES
RECORD
SAJE-B-WORK-L-REC-TYPE 001 001 X -
SAJE-B-WORK-L-REFERENCE 002 015 X -
SAJE-B-WORK-L-LINE-NO 017 003 N 0
SAJE-B-WORK-L-LINE-NO- 020 002 N 0

SUFF
SAJE-B-WORK-L-REC-TYPE- 022 001 X -

2
SAJE-B-WORK-L-REF-ID 023 005 N 0
SAJE-B-WORK-L-LINE-NO-2 028 003 N 0
SAJE-B-WORK-L-LINE-NO- 031 002 N 0

2-SUFF
SAJH-B-WORK-LINE-TYPE 033 001 X -


RECORD
SAJH-B-WORK-LINE-AB 034 001 X -
SAJH-B-WORK-LINE- 035 005 N 0

JOURNAL-REF
SAJH-B-WORK-LINE-REC- 040 001 X -

TYPE
SAJH-B-WORK-LINE- 041 007 N 0

JOURNAL-SEQ
SAJE-B-WORK-LINE- 048 001 X -

DELETED
SAJE-B-WORK-ACC-PERIOD 049 007 N 0
SAJE-B-WORK-TRANS-DATE 056 008 N 0
SAJE-B-WORK-DUE-DATE 064 008 N 0
SAJE-B-WORK-DESCRIPTION 072 030 X -
SAJE-B-WORK-ACC-CODE 102 015 X -
SAJE-B-WORK-AM 117 018 N 3
SAJE-B-WORK-DC 135 001 X -
SAJE-B-WORK-OTHER-AM 136 018 N 3
SAJE-B-WORK-CONV-CODE 154 005 X -
SAJE-B-WORK-OTHER-DP 159 001 X -
SAJE-B-WORK-OPERATOR 160 001 X -
SAJE-B-WORK-CONV-RATE 161 018 N 9
SAJE-B-WORK-ANAL-CODE 179 150 X -
SAJE-B-WORK-ASSET-CODE 329 010 X -


RECORD
SAJE-B-WORK-ASSET- 339 005 X -

SUBCODE
SAJE-B-WORK-VD 344 001 X -
SAJE-B-WORK-ACC-TYPE 345 001 X -
SAJE-B-WORK-ACC-NAME 346 030 X -
SAJE-B-WORK-ENTER-T 376 010 X -
SAJE-B-WORK-AI 386 001 X -
SAJE-B-WORK-ALLOC-RF 387 009 N 0
SAJE-B-WORK-ALLOC-DT 396 008 N 0
SAJE-B-WORK-ALLOC-AP 404 007 N 0
SAJE-B-WORK-LINE-ROUGH- 411 001 X -

FLAG
SAJE-B-WORK-L-JOURNAL- 412 005 X -

TYPE
SAJE-B-WORK-L-JOURNAL- 417 005 X -

SOURCE
SAJE-B-WORK-L-ENTRY- 422 008 N 0

DATE
SAJE-B-WORK-L-ENTRY- 430 007 N 0

PERIOD
SAJE-B-WORK-L-ALLOC-IND 437 001 X -
SAJE-B-WORK-L-ALLOC-SEQ 438 005 N 0
SAJE-B-WORK-L-JOURNAL- 443 007 N 0

NO
SAJE-VB-WORK-L-Ledger 450 001 X -


RECORD
FILLER 451 062 X -
Period Backup record

SAJE-B-WORK-P-REC-TYPE 001 001 X -
SAJE-B-WORK-P-PERIOD 002 007 N 0
SAJE-B-WORK-P-FILLER 009 013 X -
SAJE-B-WORK-P-REC- 022 001 X -

TYPE-2
SAJE-B-WORK-P-PERIOD-2 023 007 N 0
SAJE-B-WORK-P-FILLER-2 030 003 X -
SAJH-B-WORK-PERIOD- 033 001 X -

TYPE
SAJH-B-WORK-PERIOD-AB 034 001 X -
SAJH-B-WORK-PERIOD- 035 005 N 0

JOURNAL-REF
SAJH-B-WORK-PERIOD- 040 001 X -

REC-TYPE
SAJH-B-WORK-PERIOD- 041 007 N 0

JOURNAL-SEQ
SAJE-B-WORK-P-BASE-D 048 018 N 3
SAJE-B-WORK-P-BASE-C 066 018 N 3
SAJE-B-WORK-P-OTHER-D 084 018 N 3
SAJE-B-WORK-P-OTHER-C 102 018 N 3


FILLER 120 393 X -
Journal Hold Version Backup record

FILLER 001 032 X -
SAJH-B-VERSION-TYPE 033 001 X -
SAJH-B-VERSION-AB 034 001 X -
SAJH-B-VERSION- 035 005 N 0

JOURNAL-REF
SAJH-B-VERSION-REC- 040 001 X -

TYPE
SAJH-B-VERSION- 041 007 N 0

JOURNAL-SEQ
SAJH-B-VERSION 048 003 N 0
SAJH-B-LAN-CODE 051 002 N 0
FILLER 053 460 X -
Journal Hold Control Backup record

FILLER 001 032 X -
SAJH-B-CONTROL-TYPE 033 001 X -
SAJH-B-CONTROL-AB 034 001 X -
SAJH-B-CONTROL- 035 005 N 0

JOURNAL-REF


SAJH-B-CONTROL-REC- 040 001 X -

TYPE
SAJH-B-CONTROL- 041 007 N 0

JOURNAL-SEQ
SAJH-B-CONTROL-NEXT- 048 005 N 0

REF
FILLER 053 460 X -
Journal Hold Journal Backup record

FILLER 001 032 X -
SAJH-B-JOURNAL-C-TYPE 033 001 X -
SAJH-B-JOURNAL-C-AB 034 001 X -
SAJH-B-JOURNAL-C- 035 005 N 0

JOURNAL-REF
SAJH-B-JOURNAL-C-REC- 040 001 X -

TYPE

JOURNAL-SEQ
SAJH-B-JOURNAL-C-JT 048 005 X -
SAJH-B-JOURNAL-C-JS 053 005 X -

CHANGED

TRANS-CT
SAJH-B-JOURNAL-C-DEBIT 073 018 N 3



CREDIT
SAJH-B-JOURNAL-C- 109 003 X -

OPERATOR
SAJH-B-JOURNAL-C-BUSY 112 001 X -
FILLER 113 400 X -

Chapter 13 Appendix D – Import Records
13
Movement Import
Movement Import Batch Control record
A batch control record can be included in your import file. This record contains values which
should match the counted values at the end of the report. The batch control record must be
the last record in your file. The following table shows the data items, their length, start
position, and valid entries.
Data item Length Start Valid entries

position
Record Type 1 1 B
Batch Quantity 16 2 first character must be + then

numeric, or blank
Batch Value 16 18 first character must be + then

numeric, or blank
Record Count 12 34 numeric integer
Values must be filled with leading zeros. Quantity and value assume three decimal places
(without a decimal point) so +000000000010999 is taken to be +10.999. When reported, the
decimal places specification on the DB=Database Definitions is used.
Movement Import Detail record
Movement import performs the following validation:
Item Length Validation
Record Type 1 M (upper case)
Movement Reference 10 Non-blank. If it exists on movement file, further

lines are appended
Unused 5 Ignored

Appendix D – Import Records
Movement Line Number 4 Ignored. Assigned during posting
Alternate Key Type 1 Ignored
Location Code 5 Valid location code
Item Code 15 Valid item code (Note 2)
Movement Date 8 ccyymmdd
Sequence 4 Ignored
Order Line Status Key 1 1 Ignored
Order Line Status Key 2 1 Ignored
Receipt/Issue Indicator 1 R or I
Batch Number 5 Ignored
Batch Line No 5 Ignored
Receipt Reference 15 Any or blank. Ignored if movement definitions

does not require one. Must be unique if the item
record uses serial number tracking
Movement Quantity 1+18 Non-zero (Note 3)
Movement Value 1 1+18 Any value (Note 5)
Unused 1 Ignored
Posting Period 7 yyyyppp or 0000000 or blank (Note 4)
Unit of Stock Description 5 Any or blank. If blank, taken from the item
record
Movement Type 5 Valid movement definition (Note 1)

Physical Stock Update 1 Ignored
Indicator On Order Stock 1 Ignored

Update
Allocation Reference 20 Ignored
Audit Date 8 yyyymmdd, blank, or zeros
Serial Number Index Flag 1 Ignored
Unused 7 Ignored
Account Code 10 Valid account code
Unused 5 Ignored
Asset Code 10 Valid asset code
Asset Subcode 5 Valid asset subcode
Analysis Codes 10x15 Valid analysis categories
Note 1: If documents are required, the status is set accordingly. If ledger interface
postings are required, they are posted to the transfer file. Balances are updated as
specified on the movement definition. Costs will be imported if defined on
MD=Movement Definitions. Receipt reference and allocation are also taken from the
movement definition. Associated movement presets are ignored.
Note 2: This item code controls the allocation method, and the unit of stock.
Note 3: + in first character, then numeric. The last five digits are treated as decimal
places. If BD=Business Definition has Integer Quantities set to Y-Yes, then the last
five digits are ignored.
Note 4: The movement is rejected if the period is greater than the maximum number
of periods, or is outside the open period range on the BD=Business Definition. If zero
or blank, the current period on the business definition is used.
Note 5: Any one of these three values can be the base value. All three values are
defined and conform to the rules set in MV=Movement Values Definition.

Purchase Import
Purchase Import Header/Detail/Text records
Purchase Order Entry Header record - OENTH

If you leave any of the following fields blank, the purchase order header preset for this
transaction type is used: Supplier, Delivery Address, Order Date, Second Order Reference,
Delivery Date, Confirmed, Acknowledgement Reference, Acknowledgement Date,
Comments, Analysis Codes.
Data item Position Length Valid entries
Record Type 1 5 OENTH
Operator Id 6 3 Use a valid Operator ID. If this field

is left blank, the Id of the operator
running PI=Purchase Import is used.
Transaction 9 10 If manual references are used for

Reference this transaction type, you must enter
(Prefix: 9/4) a transaction reference and the
(Suffix: 13/6) transaction reference used must not
have been used before. If you leave
these fields blank, the entry is
invalid. If automatic references are
used for this transaction you must
leave this field blank. If you enter
any text, the entry is invalid.
Supplier Code 19 10 Enter a valid address code. If the

status of the address code entered
is closed, the entry is invalid. If the
status of the address code entered
is suspended, the entry causes a
warning. If you leave this field blank
and there is no preset for the
transaction type, the entry is invalid.
Trans (Order) 29 8 Enter a valid date in the form Date

ccyymmdd. If you leave this box
blank, the preset for this transaction
type is used if there is one.
Otherwise the entry is invalid.

Second Ref 37 10 Enter text. If you leave this box

type is used if there is one,
otherwise spaces are valid.
Order Status 1 47 1 Enter 0 for a status of Held, 3 for a

status of Released, or 6 for a status
of Issued(Printed).
Transaction Type 48 5 Enter a valid PD=Purchase Order

Definitions transaction type. This is
one which has the Order/Invoice
Entry box set to O-Order.
Delivery Address 53 10 Enter a valid address code. If you

Code leave this box blank, the preset for
this transaction type is used if there
is one. If a temporary address is to
be created leave blank and enter
the address in the Delivery Address
fields.
Comments 63 25 Enter text. If you leave this box

Acknowledgement 88 10 Enter text. If you leave this box

blank, the Ref preset for this
transaction type is used if there is
one, otherwise spaces are valid.
Acknowledgement 98 8 Enter a valid date in the form

Date ccyymmdd. If you leave this box

Delivery Date 106 8 If the Due Date Per Line box for this
transaction type is set to Y-Yes, this
field is ignored. Otherwise enter a
valid date in the form ccyymmdd. If
you leave this box blank, the preset
for this transaction type is used if
there is one; otherwise the
transaction date is used.
Delivery Date 114 1 If the Due Date Per Line box for this
Advised transaction type is set to Y-
Yes, this field is ignored. Otherwise
enter Y-Yes or leave the field blank.
If you leave this field blank, the
preset for this transaction type is
used if there is one; otherwise
spaces are valid.
Order Period 115 7 Enter a valid period in the form

ccyyppp. If you leave this box blank,
the current period specified in
BD=Business Definition is used.
Analysis Codes 122 150 Enter a valid analysis code for each
(M0-M9) of the header analysis categories
(10 x 15 chars) specified in PD=Purchase Order
Definitions for this transaction type.
used if there is one; otherwise
spaces are valid for analysis
categories not specified in
PD=Purchase Order Definitions.

Document Issue 272 8 Unless you have set the Order

Date Status 1 field to 6-Issued(Printed),
this entry is ignored. If, in
PD=Purchase Order Definitions, the
Direct Print Order box for this
transaction type is set to Y-Yes, N-
No, or is left blank, enter a valid date
in the form ccyymmdd. If you leave
this field blank or enter zeros, the
date defaults to today’s date. If, in
PD=Purchase Order Definitions, the
Direct Print Order box for this
transaction is set to S-Suppress,
enter zeros or spaces. An invalid
entry in this field produces import
warnings rather than import errors.
Delivery Address 280 210 Enter text. Ignored if a Delivery

(6 x 35 chars) Address code has been entered or a
preset Delivery Address exists for
this transaction type. You can leave
this field blank.
Void Status 490 1 0 - Normal, 1 – Voided Not Posted,

2 – Void and Posted, or blank
Extra Supplier Code 491 10 Valid address code, or blank

1
Extra Supplier Code 501 10 Valid address code, or blank

2
Extra Text 1 511 30 Any text, or blank

Extra Value 1 636 19 Numeric, or blank
Purchase Order Entry Item Lines - OENTI

If you leave any of the following fields blank, the purchase detail preset for this transaction
type is used: Item Code, Description, Asset Code, Asset Subcode, Location Code, Purchase
Quantity, Stock Quantity, Delivery Date, Confirmed, Account Code, Analysis Codes.
Record Type 1 5 OENTI
Update Base Price 6 1 Any entry you make in this field is

ignored unless the Update Price on
the Item Record is set to Y-Yes or O-
Order Entry. Enter Y-Yes to amend
the default purchase price for this
item if the price entered differs to the
existing default purchase price. If the
Supplier Control box in IR=Item
Records is set to Y-Yes or is left
blank and the price entered differs to
the existing default purchase price,
an IS=Item Supplier record is created
or amended. If the Supplier Control
box in IR=Item Records is set to N-
No, the item record is amended.
Operator Id 7 3 Use a valid Operator ID. If this field is

left blank, the Id of the operator

Transaction 10 10 If manual references are used for this

(Prefix: 10/4) Reference transaction type, and the
(Suffix: 14/6) order header is created earlier in the
import file or already exits on the
Purchase Order master file enter the
transaction reference of the order. If
you leave this box blank, the entry is
invalid.
If automatic references are used for
this transaction type, and the order
header already exists on the
Purchase Order master file, enter the
automatic references are used for
this transaction type and the order
header is created earlier in the import
file, leave this box blank. (Invalid if
attempting to access a direct invoice
- a transaction with an order status of
9.)
Line Number 20 4 If you want the line number to be

(Prefix: 20/3) generated automatically, enter
(Suffix: 23/1) 000space (3 Zeros and a space).
Otherwise enter a line number with a
prefix from 001 to 999 and a suffix of
blank or from 1 to 9.
Location 24 5 Enter a valid Location Code unless

the line is for a non-stocked item. If
you leave this box blank, the
purchase order detail preset is used
if there is one. If you leave this field
blank and there is no preset, the
entry is invalid.
Item Code 29 15 If the item is a non-stocked item use

‘-’ hyphen followed by text. If the item
is a stocked item, use a valid item
code. If you leave this field blank the
preset is used if one exists,
otherwise the entry is invalid.

Item Description 44 30 Enter text. If the item is a non-

stocked item, you can use this field
for additional description. If you leave
this field blank, the description from
the item supplier record is used. If
that is not present, the description
from the purchase order detail preset
for this transaction type is used. If
that is not present, the description
from the item record is used. If the
description from the item supplier
record is used and there is a second
line of description on the item
supplier record or if the item record
description is use and the Extended
Item Description box is set to 1,2,3,4,
or A-All, descriptive lines are
generated automatically.
Delivery Due Date 74 8 Ignored if Delivery Due Date per line

= spaces in Purchase Definition Valid
date ccyymmdd Zeros or spaces =
use Preset if present otherwise
defaults to transaction date.
Delivery Date 82 1 This is ignored if Delivery Due Date

Per Line is spaces in PD=Purchase
Order Definition. Otherwise enter Y-
Yes or leave the field blank. If you
leave the field blank, the preset for
this transaction type is used.
Order Status 1 83 1 Use 0 for a status of Held, or 6 for a

status of Issued (Printed).

Order Status 2 84 1 Use 0 for a status of OK, 1 for a

status of Cancelled, or 2 for a status
of Undelivered.
If the Order Status 1 field (above) is
set to 0-Held, the Order Status 2 field
must be set to 0-OK.
N.B. GRN and Invoice Status 2 will
be automatically set to the same
status. Purchase Quantity 85 19 If
you enter a number, the first
character must be + or -. You can
enter up to 5 decimal places. If you
leave this field blank or enter spaces,
the purchase order detail preset for
is one. If there is no preset, the
purchase quantity is calculated
based on the stock quantity. If there
is no stock quantity, zero is assumed
as the purchase quantity.
Purchase Quantity 85 19 If you enter a number, the first

character must be + or 0. You can
enter up to 5 decimal places.
If you leave this field blank or enter
spaces, the purchase order detail
used if there is one. If there is no
preset, the purchase quantity is
calculated based on the stock
quantity. If there is no stock quantity,
zero is assumed as the purchase
quantity.

Stock Quantity 104 19 If you enter a number, the first

If you leave this field blank or enter
used if there is one.
If there is no preset, the stock
quantity is calculated based on the
purchase quantity. If there is no
purchase quantity, zero is assumed
as the stock quantity.
Base Cost Price 123 19 The entry in this field is ignored

unless the Override box for the
calculation code BPC is set to Y-Yes
for this transaction type.
If you enter a number, the first
Calculation Values 142 323 The entry in this field is ignored

unless the Override box for a
calculation code is set to Y-Yes for
this transaction type.
Account Code 465 10 If the Accounts Code per line box for
this transaction type is left blank, the
entry for this field is ignored.
If the Accounts Code per line box for
this transaction type is set to O-Order
Entry, you must enter a valid account
code in this field. An account code is
invalid if it doesn’t exist or if it is
closed. If you leave this field blank,
the purchase detail preset for this
transaction type is used. If there is no
purchase detail preset, spaces may
be valid.

Asset Code 475 10 If the Asset Code per line box for this
transaction type is left blank, the
entry for this field is ignored.
If the Asset Code per line box for this
transaction type is set to O-Order
Entry, you must enter a valid asset
code in this field.
purchase detail preset for this
purchase detail preset, spaces may
be valid.
Asset Subcode 485 5 If the Asset Code per line box for this
transaction type is left blank, the
entry for this field is ignored. If you
leave this field blank, the purchase
detail preset for this transaction type
is used. If there is no purchase detail
preset, spaces are valid. Any asset
subcode entered must be valid for
the asset code.
(10 x 15 chars) specified for this transaction type. If
you leave this field blank, the
purchase detail preset for this
purchase detail preset, spaces are
valid for analysis categories not
specified for this transaction type.
Order Entry Text Lines - OENTT

Record Type 1 5 OENTT


Reference 9 10 If manual references are used for this

(Prefix: 9/4) transaction type, and the order header
(Suffix: 13/6) is created earlier in the import file or
already exists in SunBusiness enter
the transaction reference of the order.
If you leave this box blank, the entry is
invalid.
header already exists in SunBusiness,
enter the transaction reference of the
order. If automatic references are
used for this transaction type and the
order header is created earlier in the
import file, leave this box blank.
(Invalid if attempting to access a direct
invoice - a transaction with an order
status of 9.)
Line Number 19 4 If you want the line number to be

(Prefix 19/3) generated automatically, enter
(Suffix 22/1) 000space (3 zeros and a space).
Otherwise enter a line number with a
prefix from 001 to 999 and a suffix of
blank or from A to z.
Item Code 23 15 Enter text. If you leave this box blank,

the purchase order detail preset is
used for this transaction type. If there
is no purchase order detail preset for
this transaction type, spaces is a valid
entry.
Item Description 38 30 Enter text. If you leave this box blank,

the purchase order detail preset is
used for this transaction type. If there
is no purchase order detail preset for
this transaction type, spaces is a valid
entry.

Goods Received Header/Detail records
GRN Match Item Header - OGRNH

Record Type 1 5 OGRNH
Total Quantity 6 19 If the Purchase Quantity Balancing

box in BD=Business Definition is
blank, this field is ignored.
If you leave this field blank, the total
quantity is assumed to be zero.
Operator Id 25 3 Enter a valid Operator ID. If this field

Order Reference 28 10 Enter an existing issued order

reference i.e. an order with a status of
6- Issued(Printed).
Supplier GRN 38 10 Enter text. You can leave this field

Reference blank. A warning is generated if the
Supplier
GRN Reference is not unique.
GRN Date 48 8 Enter a valid date in the form

ccyymmdd
otherwise the entry is invalid.
Comments 56 25 Enter text. You can leave this box

blank.
Payment Date 81 8 Unless the Post Unapproved at GRN

box in BD=Business Definition is set
to Y-Yes, this field is ignored.
Enter a valid date in the form
ccyymmdd.
If you enter zeros or spaces the
record defaults to zeros.

Void Status 89 1 0 - Normal, 1 – Voided Not Posted, 2

– Void and Posted, or blank
Extra Supplier 90 10 Valid Address Code, or blank

Code 1

Code 2
GRN Match Item Lines - OGRNI

Record Type 1 5 OGRNI

Posting Period 6 7 The entry in this field is ignored unless

the GRN Status 1 for this line is set to
5-Matched Released Approved
Released. Use a valid period in the
form ccyyppp.
If you use zeros or spaces, the
posting period is set to the default
posting.
Note: If several lines for the same
GRN are released in the same run,
the posting period on the first line will
be applied to all the lines for that
GRN.

Transaction 16 10 Enter an existing issued Order

Reference reference - i.e. one with an order
(Prefix: 16/4) status of 6- Issued(Printed).
(Suffix: 20/6)
GRN Reference 26 10 Enter an existing GRN reference only

when you are appending to an
existing GRN reference. Otherwise
leave blank.
Line Number 36 4 Use an existing line number for the

(Prefix: 36/3) order specified.
(Suffix: 39/1) The prefix must be numeric (001-999)
and the suffix can be spaces or 1-9.
GRN Status 1 40 1 Enter the GRN Status 1. This can be

1-Matched Held, 2-Matched Held
Approved Held, 3-Matched Released,
4-Matched Released, or 5-Matched
Released Approved Released.
GRN Status 2 41 1 Enter the GRN Status 2. This can be

0-OK, 1-Cancelled, 2-Undelivered, or
4-Over Delivered.
Note: The Order Status 2 and Invoice
Status 2 will automatically be set to
the same status.


Receipt Reference 61 15 If the Allocation Method box in

IR=Item Records for this item is set to
S-Serialised, enter text or leave this
field blank. If you enter text, you must
not enter a duplicate reference.
If the Allocation Method box in
IR=Item Records for this item is not
set to Sserialised and the Receipt
Reference per line box for this
transaction type is blank, this field is
ignored.
Otherwise enter text or leave this field
blank.
Audit Date 76 8 If the Audit Date box for the

ignored. Enter a Valid date in the form
ccyymmdd. Otherwise the entry is
invalid.
Note: You can use OGRNI to update the status of Purchase Order Detail to goods
matched and import GRN details.
Purchase Invoice Header/Detail records
Invoice Match Item Header - OINVH

Record Type 1 5 OINVH



Otherwise, enter a number. The first
character must be + or -.
Total Value 28 19 If the Purchase Quantity Balancing

Order Reference 47 10 Enter an existing issued Order

(Prefix: 47/4) reference - i.e. an order with an order
(Suffix: 51/6) status of6-Issued(Printed).
Suppliers Invoice 57 10 Enter text. You can leave this field

Ref blank. If you use a reference that is
not unique, a
warning is generated when the file is
imported.
Invoice Date 67 8 Enter a valid date in the form

ccyymmdd. Otherwise the entry is
invalid.
Comments 75 25 Enter text. You can leave this field

blank.
Payment Date 100 8 Enter a valid date in the form

ccyymmdd. If you use zeros or
spaces, these are stored as zeros.
Invoice Period 108 7 Enter a valid period in the form

ccyyppp. If you set this field to zeros
or spaces, the default period is
assumed.
Void Status 115 1 0 - Normal, 1 – Voided Not Posted, 2

– Void and Posted, or blank

Code 1


Code 2
Invoice Match Item Lines - OINVI

Record Type 1 5 OINVI


Update Base 9 1 If the Update Price box in IR=Item

Price Records for the item is set to O-
Order or is left blank, this field is
ignored.
current base price is not changed.
If the entered base cost is different to
the current base price and you want
to amend the current base price, set
this field to Y-Yes.
If the Supplier Control box on the
item record is set to Y-Yes or is
blank, an item supplier record is
created or amended.
item record is set to N-No, the item
record is amended.
Order Reference 10 10 Enter an existing issued Order

(Prefix: 10/4) reference, i.e. an order with an order
(Suffix: 14/6) status of 6-Issued(Printed).
Invoice Reference 20 10 Enter an existing invoice reference

only if appending to an existing
invoice.
Otherwise leave blank.
Line Number 30 4 Enter an existing line number for the

(Prefix: 30/3) order specified.
(Suffix: 33/1) The prefix must be numeric (001-
999) and the suffix can be spaces or
1-9.
Delivery Due Date 34 8 If the Delivery Due Date per line box
for this transaction type is set to
ccyymmdd.
Otherwise the field defaults to the
invoice date.
Delivery Date 42 1 If the Delivery Due Date per line box

for Advised this transaction type is
blank, this field is ignored. Enter Y-
Yes or space.

Invoice Status 1 43 1 Enter the Invoice Status 1. Enter 1-

Matched Held, 2-Matched Held
Approved Held, 3-Matched Released,
4-Matched Released Approved Held,
or 5-Matched Released Approved
Released.
Invoice Status 2 44 1 Enter the Invoice Status 2.

Use 0-OK, 1-Cancelled, or 2-
Undelivered.
Note: Order Status 2 and GRN
Status 2 will be automatically set to
the same status.

If you use spaces, the purchase
quantity is set to zero.

If you use spaces, the stock quantity
is set to zero.
Base Cost Price 83 19 If you enter a number, the first

If you use spaces, the base cost
price is set to zero.

Invoice Period 425 7 This is used as the posting period.

Use a valid period in the form
ccyyppp.
If you enter zeros or spaces in this
field, the default period is assumed.

Invoice Approval 432 8 Enter a valid date in the form

Date ccyymmdd.
If you enter zeros or spaces in this
field, today’s date is assumed.

IR=Item Records for this item is set to
S-Serialised, enter text or leave this
field blank.
If you enter text, you must not enter a
duplicate reference.
set to S-Serialised and the Receipt
ignored. Otherwise enter text or leave
the field blank.

ignored. Enter a valid date in the form
ccyymmdd.
Account Code 463 10 Enter a valid account code.

If the Account Code per line box for
this transaction type is set to blank,
this field is ignored.
this transaction type is set to M-
Invoice Match and Invoice Status 1 is
set to 1-Matched Held, 3-Matched
Released, or 4-Matched Released
Approved Held, the field must not be
blank.
this transaction type is set to A-
Invoice Approval and Invoice Status
1 is set to 2-Matched Held Approved
Held, or 5- Matched Released
Approved Released, the field must
not be left blank. Otherwise spaces
are valid.

Asset Code 473 10 Enter a valid asset code.

If the Asset Code per line for the
transaction type is set to blank, this
field is ignored.
transaction type is set to M-Invoice
Match and Invoice Status 1 is set to
1-Matched Held, 3-Matched
left blank.
transaction type is set to A-Invoice
Approval and Invoice Status 1 is set
to 2-Matched Held Approved Held, or
5- Matched Released Approved
Released, the field must not be left
blank. Otherwise spaces are valid.
Asset Sub Code 483 5 Enter a valid asset subcode.

field is ignored. Any Asset Sub Code
entered must be valid for the Asset
Code.
Note: You can use OINVI to update the status if a Purchase Order Detail line to
invoiced and import invoice details. Calculation values can also be amended with this
record type.
Direct Purchase Import Header/Detail/Text records
Direct Invoice Header - DINVH

If you leave any of the following fields blank, the purchase order header preset for this
transaction type is used: Supplier, Delivery Address, Invoice Date, Supplier Invoice
Reference, Payment Date, Comments, Analysis Codes.
Type 1 5 DINVH


Total Value 25 19 If the Purchase Quantity Balancing


Order Reference 47 10 If manual references are used for this

(Prefix: 47/4) transaction type you must enter an
(Suffix: 51/6) Order Reference which has not been
used. The entry is invalid if you leave
this blank.
this transaction type you must leave
this blank.
If you enter any text the entry is
invalid.
Supplier Code 57 10 Enter a valid address code.

If the status of the address is
suspended you are warned.
If you leave this field blank, and there
is no preset for the transaction type,
a blank field is invalid.
Trans (Invoice) 67 8 Enter a valid date in the form

Date ccyymmdd.
If you leave this box blank, the preset
for this transaction type is used if one
exists. Otherwise the entry is invalid.
Supplier Invoice Ref 75 10 Enter text or leave this field blank.

Note: If you enter a supplier invoice
reference that is not unique, an
warning is generated when the file is
imported.

Transaction Type 85 5 Enter a valid PD=Purchase Order

Definition transaction type which has
its Order/Invoice Entry box set to I-
Invoice.
Delivery Address 90 10 Enter a valid address code.

Code If you leave this field blank, the
preset for the transaction type is
If a temporary address is to be
created leave blank and enter the
address as the delivery address.
Comments 100 25 Enter text. If you leave this field blank

the preset for the transaction type is
used if there is one. Otherwise
spaces are valid.
Payment Date 125 8 Enter a valid date in the form

ccyymmdd.
If you use zeros or spaces, the field
is set to zeros.
This field is ignored if the Post
Unapproved at GRN box in
BD=Business Definition is set to Y-
Yes.
Invoice Period 133 7 Enter a valid period in the form

ccyyppp.
If you use zeros or spaces, the
invoice period is set to the default
posting period.
(10 x 15 chars) specified in PD=Purchase Order
Definition for this transaction type.
Otherwise, spaces are a valid entry
for analysis categories not specified
in PD=Purchase Order Definition.

Delivery Address 290 210 Enter text. This is ignored if a

(6 x 35 chars) Delivery Address Code has been
entered or a preset Delivery Address
Code exists. You can leave this box
blank.
Extra Supplier Code 500 10 Valid Address Code, or blank

1
Extra Supplier Code 510 10 Valid Address Code, or blank

2
Direct Invoice Item Line - DINVI

If you leave any of the following fields blank, the purchase order detail preset for this
transaction type is used: Item Code, Description, Asset Code, Asset Subcode, Location
Code, Purchase Quantity, Stock Quantity, Delivery Date, Confirmed, Account Code, Analysis
Codes.
Record Type 1 5 DINVI

Posting Period 6 7 Enter a valid period in the form

ccyyppp.
If you set this field to zeros, the
posting period is set to the default
period.
Update Base Price 13 1 If the Update Price box in IR=Item

Records for the item is set to O-
Order or is left blank, this field is
ignored.
current base price is not changed.
If the entered base cost is different to
the current base price and you want
to amend the current base price, set
this field to Y-Yes.
item record is set to Y-Yes or is
blank, an item supplier record is
created or amended.
item record is set to N-No, the item
record is amended
Operator Id 14 3 Enter a valid Operator ID.

If this field is left blank, the Id of the
operator running PI=Purchase Import
is used.

(Prefix: 17/4) transaction type, enter the
(Suffix: 21/6) transaction reference of the order.
If you leave this box blank, the entry
is invalid.
header already exists on the
Purchase Order master file, enter the
transaction reference of the order.
this transaction type, leave this box
blank.


only if you are updating an existing
invoice, otherwise leave blank.
Line Number 37 4 To generate a line number

(Prefix: 27/3) automatically enter 000space.
(Suffix: 30/1) Otherwise enter a line number with a
prefix from 001 to 999 and a suffix
from 1 to 9.
To amend an existing line use an
existing line number for the invoice
specified.
Location 41 5 Enter a valid Location Code unless

the line is for a non-stocked item.
If you leave this box blank, the
purchase order detail preset is used
if there is one.
If you leave this field blank and there
is no preset, the entry is invalid.
Item Code 46 15 If the item is a non-stocked item use

‘-’ hyphen followed by text.
If the item is a stocked item, use a
valid item code.
If you leave this field blank and there
is no preset, the entry is invalid.

Item Description 61 30 Enter text. If the item is a non-

stocked item, you can use this field
for an additional description.
description from the item supplier
record is used. If that is not present,
the description from the purchase
order detail preset for this transaction
type is used. If that is not present the
description from the item record is
used.
If the description from the item
supplier record is used and there is a
second line of description on the item
supplier record or if the item record
description is use and the Extended
Item Description box is set to 1,2,3,4,
or A-All, descriptive lines are
generated automatically.
Delivery Due Date 91 8 Enter a valid date in the form

ccyymmdd.
This box is ignored if Delivery Due
Date per line is spaces in
PD=Purchase Order Definition.
If you set this field to zeros or
spaces, the purchase item preset for
is one. Otherwise the delivery due
date is assumed as the invoice date.
Delivery Date 99 1 Set this field to Y-Yes or blank.

Advised If you set the field to blank, the preset
for this transaction type is used. This
field is ignored if the Delivery Due
Date per line box for the transaction
type is blank.
Invoice Status 1 100 1 Enter the Invoice Status 1. This can

be 2-Matched Held Approved Held,
3- Matched Released, 4-Matched
Released Approved Held, or 5-
Matched Released Approved
Released.

Invoice Status 2 101 1 Enter the Invoice Status 2. This can

be 0- OK, 1-Cancelled, or 2-
Undelivered.
Purchase 102 19 If you enter a number, the first

character Quantity must be + or -.
You can enter up to 5 decimal
places.
If you leave this blank, or enter
preset the purchase quantity is
calculated based on stock quantity. If
there is no stock quantity zero is
assumed as the purchase quantity.

If you leave this box blank or enter
preset the stock quantity is calculated
based on the purchase quantity. If
there is no purchase quantity zero is
assumed as the stock quantity.
Base Cost Price 140 19 This entry is ignored unless the

override box for the calculation code
BPC is set to Y-Yes for this
transaction type. If you enter a
number, the first character must be +
or -. You can enter up to 5 decimal
places. If you use spaces, the base
cost price is set to zero.


Account Code 482 10 Enter a valid account code.

this transaction type is set to blank,
this field is ignored.
this transaction type is set to M-
Invoice Match and Invoice Status 1 is
set to 1-Matched Held, 3-Matched
set to space or left blank.
this transaction type is set to A-
Invoice Approval and Invoice Status
1 is set to 2-Matched Held Approved
Held, or 5- Matched Released
Approved Released, the field must
not be set to space or left blank.
If you leave the field blank, the
purchase order detail preset for the
one, otherwise spaces may be valid.
Asset Code 492 10 Enter a valid asset code.

field is ignored.
transaction type is set to M-Invoice
Match and Invoice Status 1 is set to
1-Matched Held, 3-Matched
set to space or left blank.
transaction type is set to A-Invoice
Approval and Invoice Status 1 is set
to 2-Matched Held Approved Held, or
5- Matched Released Approved
Released, the field must not be set to
space or left blank.

Asset Sub Code 502 5 Enter a valid asset subcode.

field is ignored.
Any asset subcode entered must be
valid for the asset code.

IR=Item Records for this item is set
to S-Serialised, enter text or leave
this field blank. If you enter text, you
must not enter a duplicate reference.
set to Sserialised and the Receipt
ignored. Otherwise enter text or
leave the field blank.

ignored.
ccyymmdd.
(10 x 15 chars) specified for the transaction type.
purchase detail preset is used if there
is one, otherwise spaces are valid for
analysis categories not specified for
the transaction type.
Note: You can use DINVI to update the status of existing Invoice Detail lines.

Direct Invoice Text Line - DINVT

Record Type 1 5 DINVT
Operator Id 6 3 Enter a valid Operator ID.

If this is blank the ID of the operator

(Prefix: 9/4) transaction type, enter the transaction
(Suffix: 13/6) reference of the order.
If you leave this box blank, the entry is
invalid.
header already exists on the Purchase
Order master file, enter the
automatic references are used for this
transaction type, leave this box blank.

only if you are updating an existing
invoice line, otherwise leave blank.
Line Number 29 4 To generate a line number

(Prefix: 19/3) automatically enter 000space.
(Suffix: 22/1) Otherwise enter a line number with a
prefix from 001 to 999 and a suffix
from 1 to 9.
To amend an existing line use an
existing line number for the invoice
specified.
Item Code 33 15 Enter text. If you leave this field blank,

the purchase detail preset for the
purchase detail preset for the
transaction type, spaces is a valid
entry.

Item Description 48 30 Enter text. If you leave this field blank,

the purchase detail preset for the
purchase detail preset for the
transaction type, spaces is a valid
entry.
Sales Import
Sales Import Batch Control record
A batch control record can be included in your import file. This record contains values which
should match the counted values at the end of the report.
The batch control record must be the last record in your file. The following table shows the
data items, their length, start position, and valid entries.
Data item Length Position Valid entries
Record Type 1 1 B
Batch Count Lines 12 2 Numeric
Batch Count 12 14 Numeric

Headers
Batch Count Item 12 26 Numeric

Lines
Batch Count 12 38 Numeric

Description Lines
Batch Total 19 50 first character must be + then

Calculation Code 1 numeric, or blank.





















Values must be filled with leading zeros.Values assume five decimal places (without a
decimal point) so +00000000001099999 istaken to be +10.99999. When reported, the
decimal places specification in DB=Database Definitionsis used. ‘Batch Counts’ are integers.
With all totals, ignore positive and negative values.
All additional records created as a result of exploding a kit list assembly, will not be included
in the counts and totals used for comparison with the batch control record.
Sales Import Header record
When your file is imported the system checks its contents. The following table shows which
data items must be present, their length and valid entries:
Data item Length Valid entries
Record Type 1 O (upper case) for order header

Q (upper case) for quotation header
Unused 5 Ignored
Trans Reference 4 Any text or blank (Note 1)

Prefix
Trans Reference 6 Any text or blank (Note 1)

Suffix
Unused 5 Ignored
Customer Code 10 Valid Address Code or blank for preset (Note 2).
The Address Code must include a valid Account
Code.
A warning is given if the Account is suspended or
over its Credit Limit
Transaction Date 8 ccyymmdd or blank for preset

(Note 2)
Alternate Key Data 14 Ignored

Order Status Key 1 1 Ignored
Order Status Key 2 1 0 for Released or 1 for Held.

Picking and Despatched not allowed
Debit/Credit 1 Ignored
indicator
Transaction Type 5 Valid Sales Order Definition (Note 1)
Unused 5 Ignored
Order Number 10 Ignored - Copied from Transaction Reference
Delivery Reference 15 Any text or blank for preset (Note 2)
Delivery Address 10 Valid Address Code or blank for preset (Note 2).
Code Delivery Address Details are used in preference to
presets. A
warning is given if the associated Account Code is
different from Customer Address
Order Date 8 Ignored - Copied from Transaction Date
Ackn Date 8 Ignored
Picking Date 8 Ignored
Delivery Date 8 Ignored
Invoice Date 8 Ignored
Period Invoiced 7 ccyyppp or 0000000 or blank (Note 6)
Customer 25 Any text or blank for preset (Note 2)

Reference
Comments 25 Any text or blank for preset (Note 2)
Order Total 1+18 Ignored - Calculated on posting
Payment Due Date 8 ccyymmdd or a relative date i.e. +10
Unused 2 Ignored

Analysis Codes M0- 10 x 15 Valid Codes in Categories specified on Sales Order

M9 Definition. Blank for preset (Note 2)
Unused 2 Ignored
Quot. Expiry Date 8 ccyymmdd or 00000000 or blank (Note 7)
Period Quoted 7 ccyyppp or 00000000 or blank (Note 6)
Unused 5 Ignored
Quotation Ref. 10 Ignored
Date-Quoted 8 ccyymmdd or 00000000 or blank
Void Status 1 Ignored – 0, 1, 2, or blank
Extra Supplier Code 10 Valid Address Code, or blank

1
Extra Supplier Code 10 Valid Address Code, or blank

2
Extra Text 1 30 Any text, or blank
Extra Value 1 19 Numeric, or blank
Filler 176

Del Address Details 6 x 35 Any text (spaced appropriately) or blank. Only used
if Delivery Address Code is blank
Inv. Address Details 6 x 35 Any text (spaced appropriately) or blank. Only used
if Customer Code is blank and quotation being
imported
Sales Import Detail record
Sales order import performs the following validation:
Record Type 1 D (upper case) for order item line or E (upper case)
for quotation item line
Unused 5 Ignored
Trans Reference 4 Any existing Header or blank (Note 1)

Prefix

Suffix
Trans Line number 3 3 digits e.g. 001
Trans Line number 2 2 digit (description lines) or blank

suffix
Location Code 5 Valid Location Code or blank for preset (Note 1 & 3)
Item Code 15 Valid Item Code or blank for preset (Note 3 & 4) or ‘-
’ plus any text for nonstocked item
Transaction Date 8 ccyymmdd or 00000000 or copied from Header

(Due Date) (Note 1)
Sequence 4 Ignored

Debit/Credit 1 Ignored
indicator
Item Description 30 Any text or blank for preset (Notes 3 & 4)
Calc Code Values 20 x Note (1, 3 & 5)

1+18
Transaction Type 5 Ignored - Copied from Header
Delivery Date 8 Ignored
Invoice Date 8 Ignored
Period Ordered 7 ccyyppp or 0000000 or blank
Invoice Period 7 ccyyppp
Unit of Sale Desc 5 Ignored
Unused 5 Ignored
Invoice Number 10 Ignored
Print Ackn 1 Ignored
Print Misc 1 Ignored
Allocation Ref 19 Ignored
Receipt Ref 15 Ignored
Line Analysis 1 Ignored

Indicator
Account Code 15 Any Valid Chart of Account Code
Unused 23 Ignored
Analysis Codes M0- 10x15 Valid Codes in Categories specified on Sales Order
M9 Definition. Blank for preset (Note 1 & 2)
Assembly Indicator 1 * or blank (Note 8)

Assembly Desc. 1 Y or blank (Note 8)

Ind.
Assembly Level Ind. 1 T or blank (Note 8)
Price Books 5 Ignored
Qty Pointers 4 Ignored
Total Value 2 Ignored
Value Pointers 6 Ignored
Misc Decs 5 Ignored
D Note 10 Ignored
Audit Date 8 ccyymmdd or 00000000 or blank
Unused 7
Delivery 1+5 Temperature Accounting only.

Temperature
+ or - in the first character then numeric. The last
two digits are treated as decimal places.
Delivery Quantity 1 1+18 Temperature Accounting only.

+ in the first character then numeric. The last five
digits are treated as decimal places. This quantity
may reflect either volume or weight, depending on
the individual sales order line item, i.e. if the item is
a ‘volume’ item, Delivery Quantity 1 reflects volume,
if the item is a ‘weight’ item Delivery Quantity 1
reflects weight. Delivery Quantity 1 and Delivery
Quantity 2 are mutually exclusive. If Delivery
Quantity 2 is being input, Delivery Quantity 1 should
contain zeroes, i.e. +000000000000000000.

Delivery Quantity 2 1+18 Temperature Accounting only.

+ in the first character then numeric. The last five
digits are treated as decimal places. This quantity
may reflect either volume or weight, depending on
the individual sales order line item, i.e. if the item is
a ‘volume’ item Delivery Quantity 2 reflects weight, if
the item is a ‘weight’ item Delivery Quantity 2
reflects volume. Delivery Quantity 1 and Delivery
Quantity 2 are mutually exclusive. If Delivery
Quantity 1 is being input, Delivery Quantity 2 should
contain zeroes, i.e. +000000000000000000.
Delivery Date 8 Temperature Accounting only.

Ccyymmdd. This date is matched against
DE=Standard Density records to retrieve the
required Standard Density value. If no appropriate
DE record exists, Standard Density must be
supplied either via import fields Product Density,
Product Density Temperature and HCF (which
together allow it to be calculated), or explicitly via
import field Standard Density.
Product Density 5 Temperature Accounting only.

Numeric. The last digit is treated as a decimal place.
If Standard Density is being retrieved from DE=
Standard Density or supplied explicitly via import
field Standard Density this field should contain
zeroes.
Product Density 6 Temperature Accounting only.

Temperature
+ or - in the first character then numeric. The last
two digits are treated as decimal places. If Standard
Density is being retrieved from DE=Standard density
or supplied explicitly via import field Standard
Density this field should contain zeroes, i.e. +00000.
Hydrometer 1 Temperature Accounting only.

Correction Factor
0 or 1. If Standard Density is being retrieved from
DE=Standard Density or supplied explicitly via
import field Standard Density this field should
contain zero.

Standard Density 5 Temperature Accounting only.

Numeric. The last digit is treated as a decimal place.
If Standard Density is being retrieved from
DE=Standard Density or supplied via import fields
Product Density, Product Density Temperature and
HCF this field should contain zeroes.
Sales Import Description record
Sales order import performs the following validation:
Record Type 1 D (upper case) for orders

E (upper case) for quotations
Unused 5 Ignored

Prefix

Suffix
Trans Line number 3 3 digits e.g. 001
Trans Line number 2 2 characters, not spaces and not numeric

suffix
Location Code 5 Ignored
Item Code 15 any text or blank for preset (Notes 3 & 4)
Transaction Date 8 Ignored
Sequence 4 Ignored
Unused 3 Ignored
Item Description 30 Any text or blank for preset (Note 3 & 4)

Note 1: This sales order definition controls many things.

The debit/credit transaction indicator overrides the sign for quantity shown on item
lines. This in turn may be reversed by IP=Item Special Processes.
If update stock is required, a location code must be supplied on the import file or from
a detail preset (Note 3). If there is not sufficient free stock, a warning is printed. If
stock update is not required the location code is ignored. This applies to nonstock
items. If an item special process states that stock update is not required, this
overrides any other indicators.
If due date entry is not required the order header date is copied to detail lines and
used for picking and the due date on the import file is ignored. If it is required, one
must be supplied or taken from a detail preset.
If manual order numbers are required, the import file must include references. A
reference which already exists will be rejected. If not required, headers must be
supplied without references which will be taken from the BD=Business Definition.
These automatically allocated numbers must not duplicate numbers that already
exist. The order number on detail lines must either match a header that already exists
or one that precedes them on the import file. If detail lines do not show numbers, it is
assumed they belong to the previous header.
If you are using automatic numbering the prefix is taken from SD=Sales Order
Definitions if one is not supplied on the import file.
Analysis codes are copied from the header to detail lines. They may be supplied on
detail lines only if the sales order definition requests entry by line.
Calculation values/manual override work as in sales order entry. Normally they
should be left blank in the import file and will be calculated. If manual override is Y-
Yes, then the value on the import file is used. Zero is used if the calculation cannot be
made. CT=Calculation Tables are ignored and zero substituted if the tables depend
on item codes and a nonstock item has been specified.
Note 2: HP=Sales Order Header Presets may be used for invoice address, delivery
address, transaction date, customer reference, delivery reference, comments, and
analysis codes. The invoice address may be blank if importing a quotation for a
prospective customer.
Note 3: DP=Sales Order Detail Presets may be used for item code, item description,
location code, up to 3 calculation values (Note 1), due date and account code.
Note 4: The IR=Item Records description is used if there is neither one on the import
file, the extended item description record, nor on a detail preset. The following are
also taken from the item record: unit of sale, base/next selling price, and item special
processes. The latter are used exactly as if the order were being entered manually.
So if you are subtotalling, you must present lines in the correct sequence.
Extended item descriptions will be added to the imported record if the item record
description is used and the SOP Extended Item Description on the IR=Item Records
is not blank and the description or the import file is blank.

Note 5: + or - in the first character then numeric. The last five digits are treated as
decimal places. If BD=Business Definition has integer quantities set to Y-Yes, then
the last five digits of the Sale and Stock Quantities are ignored.
Note 6: The transaction is rejected if the period is greater than the maximum number
of periods, or outside the Open Periods Ranges on the BD=Business Definition. If
zero, the Current Period on the BD=Business Definition, is used. Do not leave this
blank.
Note 7: The quotation expiry date is used only on quotation header records. If zero or
blank the Quotation Expiry date on the SD=Sales Order Definition is added to
Today’s Date to give a calculated quotation expiry date.
Note 8: These items should only be used if you are importing items as part of an
assembly. The assembly indicator should be set to ‘*’ asterisk if the item code is part
of an assembly which has already been exploded. Leave blank if the assembly is to
be exploded by the import program.
The assembly description indicator should be set to Y-Yes if the item on the detail line
is part of a process components type assembly which has already been exploded.
The assembly level indicator should be set to T-Top Level if the item on the detail is
the top level item of an already exploded assembly.
Import of returns and exchanges credit notes

You can use Sales Import to import returns and exchanges credit notes. To allow for this, two
fields are available on the import file as follows:
Field Name Position in file Field length SQL field type Value
Receipt Reference (Lot 544-558 15 CHAR Alphanumeric

Number)
Audit Date (Expiry 783-790 8 INT Numeric (YYYYMMDD)

Date)
Receipt Reference and Audit Date are only required if the sales order type is configured as
follows:
Transaction Type Field Value
Sales Return Debit/Credit C
Update Stock Y
Recpt. Ref/Audit Date Y
Lot number validation procedures are the same as for movement and purchase import
functions. Only if one or more valid transactions exist for the order, is the header imported, if

an order contains three transaction lines, of which one is invalid, then that one is rejected but
the other two are posted.
Reporting follows the standard sales import reporting methods. If Report Transactions is set
to ‘Y’, then detail lines along with description lines are printed; otherwise, a summary report is
produced.
After successful import, credit notes are placed on hold.
Upon printing a credit note, the Receipt Reference and Audit Date data are transferred to the
resulting movement receipt transaction on the movement table.
SunAccount transfer file

Journal Import record
This transfer file is used to import transactions into SunAccount, using the JI=Journal Import
function. A table of this format is also generated by SunBusiness in order to transfer data
from SunBusiness to the SunAccount ledgers. JI=Journal Import can accept transfer files in
the formats: SAF, SBF and PCF, from previous versions of SunSystems v4.
The same layout is created when you backup the ledger and budget tables in SunAccount
(backup files are created by the FB=File Backup/Restore function). However, it contains a
control record which is not required for JI=Journal Import files.
The SAF format transfer file may be created by any application which is able to present it in
ASCII text format.
This layout should be used for every transaction that is to be imported into Ledger
Accounting, Corporate Allocations and the Fixed Asset Register. Remember that the debits
and credits should balance to zero.
Fields which are not used should be space filled.
Note: A full list of the maximum values permitted in is provided in Appendix F.
Control record
This is not required for JI=Journal Import, although a warning message appears if none is
found.
Data item Start Length Comments

position
Filler 1 32 Space
Record Type 33 1 =C
Highest Journal 34 7
Number Used
Last Cleardown 41 5
Sequence Used
Filler 46 2 Spaces


position
Language Id. 48 2
Filler 50 463 Spaces
Accounting transaction
position
Account Code 1 10 10 characters
Filler 11 5 Spaces
Accounting Period 16 7 yyyyppp (year number, period

number)
Transaction Date 23 8 yyyymmdd (year, month, and day

number)
Filler 31 2 Spaces
Record Type 33 1 =M
(Record Types E, T, N and L can
still be read in version 4.2. If your
records include analysis codes T0,
or T6 to T9 you must use Record
Type L or M.)
Journal Number 34 7 Journal Number

(The SunBusiness transfer file
divides this item into a SOURCE of
2 chars at Start Position 34,
followed by the Journal Number of 5
chars at Start Position 36.)
Line 41 7 Line Number
Amount 48 18 15 integer and 3 decimal
Debit/Credit Marker 66 1 = D or C
Allocation Indicator 67 1


position
Journal Type 68 5
Journal Source 73 5
Transaction 78 15 15 characters
Reference
Description 93 25
Entry Date 118 8 yyyymmdd (Generated by

JI=Journal Import)
Entry Period 126 7 yyyyppp (Generatedby JI=Journal

Import)
Due Date 133 8 yyyymmdd
Filler 141 6 Spaces
Payment/Allocation 147 9 9 integer

Ref
Payment/Allocation 156 8 yyyymmdd

Date
Payment/Allocation 164 7 yyyyppp

Period
Asset Indicator 171 1 =V, D, I, or Space
Asset Code 172 10
Asset Sub-code 182 5
Conversion Code 187 5
Conversion Rate 192 18 9 integer and 9 decimal
Other Amount 210 18 15 integer and 3 decimal
Other Amount Dec. 228 1

Places


position
Cleardown 229 5
Filler 234 4
Next Period Reversal 238 1 Leave blank
Text Linked 239 1 Leave blank
Rough Book Flag 240 1 Leave blank
In Use Flag 241 1 Leave blank
Analysis Code 0 242 15
Posting date 392 8 For rough journals:

date when un-roughed
(Generated by JI=Journal Import)
Update Order Bal. 400 1 Leave blank

Ind.
Allocation in progress 401 001 Leave blank
Hold Reference 402 005 Leave blank


position
Hold operator ID 407 003 Leave blank
Budget Account 410 015 Leave blank
Allocation Marker ID 425 003 Leave blank
Allocation Marker 428 008 Leave blank

Date
Filler 436 077 Leave blank


Chapter 14 Appendix E - Installation
File Records for version 4.4 DataLink 14
Operator Definitions (ODN)

ODN records
The SSINSTAL record (total length 1024) has three fields as the following table highlights:
Field name Start Length Comments

position
INS_TB 1 3 Each record in the SSINSTAL table is

defined by a 3 character code, this field is
“ODN”
INS_KEY 4 61 (3 + 58) This is the key for the ODN record and
holds the value of Operator ID as
specified in the enterable list of fields
above; it is a 3 character code. This is
followed by a further 58 spaces, making a
total INS_KEY of length 61.
SUN_DATA 65 960 This is one string of data which holds the

values for all the other fields
SUN_DATA definition
When pushing a record into the SSINSTAL table you need to set up the SUN_DATA field as
one long string of data as the following table highlights:
Field name SUN_DATA Length Type Comments

start position
Record 1 3 X The same as INS_TB

Type
Operator ID 4 3 X The same as INS_KEY (first 3

characters)
Spaces 7 15 X 15 spaces
Operator 22 25 X As entered in the Operator Name

Name field

Appendix E - Installation File Records for version 4.4 DataLink

start position
Password 47 6 X Always set to spaces
Printer 53 5 X The value selected from the printer

Code code list as defined in the Printer
Code field above
Print Device 58 10 X The Print File Drive as described

in the enterable list of fields above
Login 68 1 X Always set to space
Terminal 69 5 X Now defunct so always set to

Code spaces
Date 74 1 X Always set to space

Format
Menu Style 75 1 X Must be Y or Blank as specified by

the Classic Menu field defined in
the list of enterable fields
Work Drive 76 10 X The work file drive as defined in

the list of enterable fields.
Current 86 3 X Always set to spaces

Database

System

Function
Query Level 93 1 X Must be set to 0, 1 or 2 as defined

in the query level enterable field.
Language 94 2 9 The value selected from the list of

valid language codes as defined in
the enterable field list above.


start position
Current 96 11 X Currently this is the password the

Password user would define but will be
defunct with GSS but should be
set to non spaces.
Operator 107 5 X The value selected from the list of

Group valid operator groups as defined in
the enterable field list above.
Password 112 6 X Always set to zeros

Date
Old 118 143 X Always set to spaces

Passwords
Violate Date 261 8 X Always set to zeros
Transfer 269 10 X The value entered into transfer file

Directory drive as specified in the enterable
field list above.
Spaces 279 682 X 682 extra spaces which will be

used for future fields.
Group Definition records (GDN)

GDN records
Field name Start position Length Comments

defined by a 3 character code, this
field is “GDN”
INS_KEY 4 61 (5 + 56) This is the key for the GDN record

and is built up as follows:
Operator Group – The Operator
Group entered on the Operator
Permissions screen.

SUN_DATA 65 960 This is one string of data which holds

the values for all the other fields
Field name SUN_DATA start Length Type Comments

position
Spaces 1 21 X Spaces
Description 22 30 X This is set to the

Operator Group Name on
the Operator Permissions
screen
Password 52 2 X As passwords will now be

Length handled by GSS this field
is spaces
Password 54 3 X As passwords will now be

Interval handled by GSS this field
is spaces
Spaces 57 904 X Set to spaces
Operator Permissions
Data and Miscellaneous Restrictions (ACP)
ACP records

position
INS_TB 1 3 Each record in the SSINSTAL table is defined

by a 3 character code, this field is “ACP”


position
INS_KEY 4 61 (8 + This is the key for the ACP record.

53)
The key is built up of:
Operator Group as defined on the operator
permissions entry screen. (5 characters)
Database Code as defined on the operator
permissions entry screen. (3 characters)
A further 53 spaces pad out the key.


start position
Account Types 22 6 X As specified in the

Account Types
enterable field in
Miscellaneous
Restrictions.
Open Period 28 8 X As specified in the

From open period from field
in Miscellaneous
Restrictions. A period
is recorded in the
format PPP/CCYY
(1st leading zero of
PPP is suppressed,
eg 01/2006)
Open Period To 36 8 X As specified in the

open period to field in
Miscellaneous
Restrictions (recorded
as above).


start position
Open Date 44 10 X As specified in the

From open date from field
in Miscellaneous
Restrictions. A date is
recorded in the format
defined for the
database, eg
31/12/2005).
Open Date To 54 10 X As specified in the

open date to field in
Miscellaneous
Restrictions (recorded
as above).
Reprint 64 1 X The value of the

Acknowledgem reprint
ents Flag acknowledgements
enterable field in
Miscellaneous
Restrictions.
Reprint Picking 65 1 X The value of the

List reprint picking list
enterable field in
Miscellaneous
Restrictions.

Despatch Note reprint despatch note
enterable field in
Miscellaneous
Restrictions.
Reprint Sales 67 1 X The value of the

Invoice reprint sales invoice
enterable field in
Miscellaneous
Restrictions.


start position

Purchase Order reprint purchase order
enterable field in
Miscellaneous
Restrictions.

Movements reprint movements
enterable field in
Miscellaneous
Restrictions.
Field Name SUN_DATA Length Type Comments

Start Position

Quotations reprint quotations
enterable field in
Miscellaneous
Restrictions.
Override 71 1 X The value of the

Insufficient Free override insufficient
Stock free stock enterable
field in Miscellaneous
Restrictions.
Override Over- 72 1 X The value of the

commit override overcommit
enterable field in
Miscellaneous
Restrictions.
Maximum 73 13 9 The value of the

Purchase Order maximum purchase
Value order value enterable
Restrictions.


start position
Override 86 1 X The value of the

Insufficient override insufficient
Physical Stock physical stock
enterable field in
Miscellaneous
Restrictions.
Credit Limit 87 13 9(13) The value of the

Tolerance Value credit limit tolerance
enterable field in
Miscellaneous
Restrictions.
Credit Limit 100 6 9(3)v9(3) The value of the

Tolerance credit limit tolerance
Percentage percentage enterable
Restrictions. Note the
decimal point must be
removed for example
99.99 becomes
099990
Account Code 106 2 X The value of the data

entry and report
inquiry entered fields
for account codes in
data restrictions
Account Type 108 2 X The value of the data

entry and report
for account types in
data restrictions
Journal Types 110 2 X The value of the data

entry and report
for journal types in
data restrictions


start position
T0 Codes 112 2 X The value of the data

entry and report
for T0 codes in data
restrictions

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions


start position

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions
M0 Codes 132 2 X The value of the data

entry and report
for M0 codes in data
restrictions

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions


start position

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions

entry and report
restrictions
Bank Account 152 1 X The value of the bank

Overdrawn account overdrawn
enterable field in
Miscellaneous
Restrictions.


start position
PO Cred/Bal 153 1 X The value of the POP

Display cred/bal display
enterable field in
Miscellaneous
Restrictions.
SO Cred/Bal 154 1 X The value of the SOP

Display cred/bal display
enterable field in
Miscellaneous
Restrictions.
Import/Export 155 1 X The value of the

Transfer import/export
Restrictions enterable field in
Miscellaneous
Restrictions.
Ledger Export 156 1 X The value of the

Account Code ledger export entered
field in data
restrictions for
account code

Account Type ledger export entered
field in data
restrictions for
account types

Journal Type ledger export entered
field in data
restrictions for journal
types

T0 ledger export entered
field in data
restrictions for T0
Code


start position

field in data
restrictions for T1
Code

field in data
restrictions for T2
Code

field in data
restrictions for T3
Code

field in data
restrictions for T4
Code

field in data
restrictions for T5
Code

field in data
restrictions for T6
Code

field in data
restrictions for T7
Code


start position

field in data
restrictions for T8
Code

field in data
restrictions for T9
Code
Menu Restrictions (OPA, DOP)
OPA records

“OPA”

INS_KEY 4 61 (12 + This is the key for the OPA record and is
49) built up as follows:
Operator Group – The Operator Group
entered on the Operator Permissions
screen.
Database Code – The database entered
on the operator permission screen.
System
The 2 character code entered by the user
is mapped against a different 2 character
code as follows:
AR = SF, CO = SC, IC = SM,
LA = SA, PO = SP, SO = SO,
SX = SX, MM = SG, SS = SS
For example if a user enters the system
as PO then System code on the
SSINSTAL record will be SP.


start position
Actions(1) 22 8 X 2 four digit codes


start position
Spaces 182 779 X Fill with Spaces
The following grids show which functions have which permissions and the code number that
is associated with each menu option.
SunSystems v4 functions (user input *** in database code)
Control Sequence Definitions, Data Access Groups, Database Definitions, Printer Definitions,
Language Definitions, Operator Definitions, Operator Buttons, Event Profiles, Rule Sets, Rule
Messages, Lookup Table Profiles, Lookup Tables, External File Types, Definable Data Items,
Transfer Profiles, Reconciliation Profiles, Business Views
Menu description Action code
Create 00150000
Amend 00010000

Delete 00230000
Transfer 00910000
Report Audit Trail 01000000
Clear Audit Trail 01740000
Analysis Category Lengths
Create 00150000
Amend 00010000
Delete 00230000
Audit Control
Amend 00010000
User Hook Definitions
Create 00150000
Amend 00010000
Delete 00230000
SunAccount functions (user input – System = “LA”, System

Code=”SA”)
Journal Definition, Journal Presets, Tax Listing Layouts, Tax Details, Statement Layouts,
Statement Line Contents, Table Formats, Table Rows, Table Columns, Column Headings,
Export Definitions, Export Consolidation, Chart Of Accounts, Names and Addresses, Bank
Details, Conversion Definitions, Conversion Tables, Analysis Codes, Budget Definitions,
Analysis Definitions, Format Definitions, Transfer Layouts, Formatted Layouts, Sequence

Number Definitions, Payment Profiles, Aged Analysis Layouts, Treasurer Interface

Definitions, Treasurer Transaction Definitions, Payment Reference Data, Standard
Descriptions
Create 00150000
Amend 00010000
Delete 00230000
Transfer 00910000
Commitment Inquiry
Transfer 00910000
Ledger Definition, Audit Control, Daybook Definition
Amend 00010000
Journal Entry
Start Journal 00830000
Recall Journal 01360000
List Rough Journals 02020000
Create 00150000
Amend 00010000

Delete 00230000
Hold 00380000
Start 00750000
Post 00550000
Rough 01370000
Clear Journal 00190000
Other Operators 01510000
Reference Amend 00740000
Amend Presets 00070000
Unbalanced Z Option 01060000
Release Z Option 01190000
Journal Import
Post 00550000
Rough 01370000
Hold 00380000
Ledger Revaluation, Generate Debits, Generate Payments, Void Payments, Transaction

Matching, Cash Tax Allocation
Post 00550000
Rough 01370000
Account Allocation
Post 00550000

Rough 01370000
Generate 00370000
Amend/Alloc Allocation 00030006
Amend/Alloc Description 00030024
Amend/Alloc Due Date 00030099
Amend/Alloc Analysis 0 00030145
Closed Period Access 02100000

Corporate Allocation functions (user input – System = “CO”,

System Code=”SC”)
Statement Layouts, Statement Line Contents, Table Formats, Table Rows, Table Columns,
Column Headings, Export Definitions, Export Consolidation, Chart Of Accounts, Allocation
Definitions, Allocation Sources, Allocation Targets, Allocation Ratios, Analysis Codes,
Budget Definitions
Create 00150000
Amend 00010000
Delete 00230000
Transfer 00910000
Ledger Definition, Audit Control
Amend 00010000
Journal Import
Post 00550000
Rough 01370000
Hold 00380000
Generate Allocations
Post 00550000
Rough 01370000

Calendar Definitions
Create 00150000
Amend 00010000
Delete 00230000
Transfer 00910000
Asset Register (user input – System = “AR”, System Code =

“SF”)
Journal Definitions, Journal Presets, Analysis Layouts, Table Formats, Table Rows, Table
Columns, Column Headings, Export Definitions, Export Consolidation, Chart Of Accounts,
Asset Records, Asset Budget Records, Asset Analysis, Asset Diary, Conversion Definitions,
Conversion Tables, Daily Conversion Tables, Analysis Codes, Budget Definitions, Analysis
Definitions, Spread Ratios, Table Headings, Depreciation Tables.
Create 00150000
Amend 00010000
Delete 00230000
Transfer 00910000
Register Definition, Audit Control
Amend 00010000
Calculate Depreciation, Asset Disposal

Post 00550000
Rough 01370000
Journal Entry
Start Journal 00830000
Recall Journal 01360000
List Rough Journals 02020000
Create 00150000
Amend 00010000
Delete 00230000
Hold 00380000
Start 00750000
Post 00550000
Rough 01370000
Clear Journal 00190000
Other Operators 01510000
Reference Amend 00740000
Amend Presets 00070000
Journal Import
Post 00550000

Rough 01370000
Hold 00380000

Inventory Control (user input – System = “IC”, System Code =

“SM”)
Movement Definitions, Movement Presets, Analysis Layouts, Item Records, Item
Descriptions, Item Suppliers, Analysis Codes, Analysis Definitions, Ledger Interface, Chart
Of Accounts, Location Definitions, Stock Take Definitions, Assembly Structure, Conversion
Definitions, Conversion Tables, Daily Conversion Tables, User Hook Definitions, Location
Accounts, Revaluation Analysis, Revaluation Profiles, New Cost Definition, Movement
Accounts, Item Entry
Create 00150000
Amend 00010000
Delete 00230000
Transfer 00910000
Inventory Balances
Create 00150000
Amend 00010000
Delete 00230000
Business Definition
Amend 00010000
Movement Values Definition, System Labels

Create 00150000
Amend 00010000
Audit Control
Amend 00010000
Stock Take Entry
Post Batch 00590000
Approve 01380000
Stock Take Approval
Post Batch 00590000
Sales Order Processing (user input – System = “SO”, System

Code = “SO”)
Sales Order Definitions, Sales Order Header Presets, Sales Order Detail Presets, Analysis
Layouts, Chart Of Accounts, Names and Addresses, Address Analysis, Item Records, Item
Descriptions, Credit/Debit Note Association, Analysis Codes, Analysis Definitions,
Calculation Definitions, Calculation Tables, Ledger Interface, Location Definitions, Item
Special Processes, Statistical Layouts, Assembly Structure, Price Book Maintenance, Price
Book Definition, Sales Format Definition, Conversion Definitions, Conversion Tables, Daily
Conversion Tables, Payment Reference Data, User Hook Definitions, Free Goods Setup,
Free Goods Rules, Authorisation Groups, Authorisation Parameters, Minimum Order
Tolerance, Return/Exchange Parameters, Tracking Code Parameters, Tracking Code
Maintenance, Excluded Combinations, Document Counter

Create 00150000
Amend 00010000
Delete 00230000
Transfer 00910000
Inventory Balances, Price Book Hierarchy,
Create 00150000
Amend 00010000
Delete 00230000
System Labels
Create 00150000
Amend 00010000
Quotation Entry
Approve 01380000

Convert 01390000
Reject 01410000
Inventory Allocation
Start Transaction 00850000
Next 00480000
Back 00080000
First 00320000
Last 00440000
Amend/Alloc 00030000
Post Allocations 00600000
Business Definition
Amend 00010000
Audit Control
Amend 00010000
Transaction Audit Control

Create 00150000
Amend 00010000
Examine 00290000
Report 00680000
Sales Order Entry
Release 00690000
Create 00150000
Amend 00010000
Delete 00230000
Purchase Order Processing (user input – System = “PO”, System

Code = “SP”)
Purchase Order Definitions, Purchase Header Presets, Purchase Detail Presets, Chart Of
Accounts, Names and Addresses, Address Analysis, Item Records, Item Descriptions, Item
Suppliers, Inventory Balances, Analysis Codes, Analysis Definitions, Calculation Definitions,
Calculation Tables, Ledger Interface, Location Definitions, Unit Conversion Tables, Item
Special Processes, Statistical Layouts, Budget Account Definition, Conversion Definitions,
Conversion Tables, Daily Conversion Tables, Charge Index, Purchase Format Definitions
Create 00150000
Amend 00010000
Delete 00230000
Transfer 00910000

Transaction Audit Control
Create 00150000
Amend 00010000
Examine 00290000
Report 00680000
System Labels
Create 00150000
Amend 00010000
Commitment Inquiry
Transfer 00910000
Business Definition
Amend 00010000
Audit Control

Amend 00010000
Purchase Order Entry
Release 00690000
Create 00150000
Amend 00010000
Delete 00230000
Hold 00380000
Split Quantity 01420000
Goods Receipt Matching
Approve 01380000
Over Delivery 01130000
Purchase Invoice Entry, Purchase Invoice Matching
Release 00690000
Approve 01380000
Match 00960000
Create 00150000
Amend 00010000
Hold 00380000

Split Quantity 01420000
DOP records

defined by a 3 character code, this field
is “DOP” for miscellaneous permissions
INS_KEY 4 61 (10 + 51) This is the key for the DOP record and is
built up as follows:
First 5 characters = Operator Group
Name
Next 3 characters = Database Code
Next 2 characters = System
For example GAZ DEMSA is the key for
operator group GAZ, database DEM,
system SA.
Database Code
A valid database as defined in database
definitions.
System
The 2 character code entered by the
user is mapped against a different 2
character code as follows:
AR = SF, CO = SC, IC = SM,
LA = SA, PO = SP, SO = SO,
SX = SX, MM = SG, SS = SS
For example if a user enters the system
as PO then System code on the
SSINSTAL record will be SP.
The rest of the key is spaces


Field name SUN_DATA start Length Type Comments

position
Default flag 22 1 X Must be set to enabled or

disabled.
Permissions 23 99 X A list of 99 individual 1

character permissions
which are either Y or N. If
the default flag above is
set to Y then all the
permissions must be set
to space. Consequently if
the default flag is N then
all the permissions must
be set to space. On some
functions the value can be
set to A, which controls
the Actions available in
the function (OPA
records). See Slot
Numbers later in this
section.
Spaces 122 838 X Set to spaces
Transfer Manager Restrictions (TDA)
TDA record


“TDA”
INS_KEY 4 61 (5 + 56) This is the key for the TDA record and is
built up as follows:
Operator Group – The Operator Group
entered on the Operator Permissions
screen.


start position
Export Flags 86 30 X Can be either tick or blank
Import Flags 116 30 X Can be either tick or blank
Spaces 239 879 x Fill with Spaces
Each export and import flag is linked to a function and should be in the following order.
Export Flags
1. Ledger File
2. Sales Order File
3. Sales Invoices
4. Sales Quotations
5. Purchase Orders
6. Purchase Invoices
7. Goods Received Notes
8. Inventory Movements
9. External File Types
10. Chart Of Accounts
11.Address Record

12.Address Analysis
13.Analysis Codes
14.Bank Details
15.Asset Record
16.Asset Analysis
17. Asset Diary
18.Asset Budget
19.Conversion Definition
20.Conversion Tables
21. Daily Conversion
22. Item Record
23. Item Supplier
24. Extended Item Description
25. Inventory Balances
26.Price Book
27. Bill Of Materials
28.Space
29.Space
30.Space
Import Flags
1. Ledger File
2. Sales Order File
3. Sales Invoices (note no import flag on screen so set to space)
4. Sales Quotations (note no import flag on screen to set to space)
5. Purchase Orders
6. Purchase Invoices
7. Goods Received Notes
8. Inventory Movements
11.Address Record
12.Address Analysis
13.Analysis Codes
14.Bank Details
15.Asset Record
16.Asset Analysis
17. Asset Diary
18.Asset Budget
19.Conversion Definition
21. Daily Conversion
22. Item Record
23. Item Supplier
24. Extended Item Description
26.Price Book
28.Space
29.Space
30.Space

Data Access Groups (DAG)

DAG records

position

“DAG”
INS_KEY 4 61 (5 + 56) This is the key for the DAG record and
holds the value of data access group as
specified in the enterable list of fields
above; it is a 5 character code. This is
followed by a further 56 spaces, making a


start position
Record Type 1 3 X The same as INS_TB
Data Access Group 4 5 X The same as INS_KEY

(first 5 characters)
Spaces 9 13 X 13 spaces
Description 22 25 X As entered in the

description field
Include/Exclude Flag 47 1 X As entered in the

include/exclude flag.
Must be I or E
Default Operator Flag 48 1 X As entered in the default

operator flag. Must be Y
or space


start position
Operator Group * 64 49 64 * 6 X 64 slots, 1 for each

(384) operator group. Note
that each field is 6
characters long
although the enterable
field is 5 characters. The
first five should be set to
the operator group and
the 6th set to space
unless the operator
group entered includes
wildcard characters. If
the group includes
wildcard characters the
6th character should be
set to Y
Spaces 433 528 X 528 extra spaces for

use in future
development
Event Profile Record (ZED)

INS_TB 1 3 Each record in the SSINSTAL

table is defined by a 3 character
code, this field is “ZED”
INS_KEY 4 61 (5 + 56) This is the key for the ZED

record and holds the name of
the Event Code it is a 5
character code. This is followed
by a further 56 spaces, making a
SUN_DATA 65 960 This is one string of data which

holds the values for all the other
fields


start position
Filler 1 13 X Filler
Date Amended 14 8 9(8) Date amended
Description 22 35 X As entered in the description

field
Status 57 1 X As entered in the

include/exclude flag. Must be I
or E
Effective Period 58 7 9(7) Period

From
Effective Period 65 7 9(7) Period

To
Effective Date To 72 8 9(8) Date
Effective Date 80 8 9(8) Date

From
Lock 88 1 X Lock
Spaces 89 872 X 872 extra spaces for use in

future development
Rule Table Record (ZRT)


“ZRT”

INS_KEY 4 61 (17 This is a string of technical data which

+ 44) contains references to the data
dictionary. The length is 17.
This cannot be interpreted for simple
reporting.


start position

future development
Rule Set Record (ZRS)


defined by a 3 character code, this field
is “ZRS”
INS_KEY 4 61 (5 + This is the key for the ZRS record and

5+4+ holds the name of the Event Code, the
47) Rule Set and the line number. This is
followed by a further 47 spaces, making
a total INS_KEY of length 61.



start position
ZRS Data 22 86 X This is a string of technical

data which contains
references to the data
dictionary.
This cannot be interpreted for
simple reporting.

future development
Rule Description Record (ZRH)

position

table is defined by a 3
character code, this field is
“ZRH”
INS_KEY 4 61 (5 + 5 + 51) This is the key for the ZRH

record and holds the name of
the Event Code and the Rule
Set. This is followed by a
further 51 spaces, making a
SUN_DATA 65 960 This is one string of data

which holds the values for all
the other fields

start position


start position
Rule Description 22 35 X This is the description of the

Rule.

future development
Rule Message Record (ZRM)


table is defined by a 3
character code, this field is
“ZRM”
INS_KEY 4 61 (2 + 5 + 54) This is the key for the ZRM

record and holds Language
Code and the Message Code
This is followed by a further
54 spaces, making a total
INS_KEY of length 61.
SUN_DATA 65 960 This is one string of data

which holds the values for all
the other fields

start position
Rule Message 22 60 X This is the description of the

Description Rule.

future development

Slot numbers
System Code = SS (user input – database code = ***)
The number determines the position in the permissions field and the words define the function
to restrict.
1. Ledger Accounting
2. Sales Order Processing
3. Change Database
4. File Backup/Restore
5. File Creation
6. View Stored Report
7. Change Printer
8. Purchase Order Processing
9. Operator Definitions
10. Printer Definitions
11. Database Definitions
12. Fixed Asset Register
13.Corporate Allocations
14.
15.System Parameters
16. Clear Operators
17.Serialisation
18.Operator Permissions
19.Inventory Control
20. Materials Management
21.
22.
23. Language Definitions
24. User Hook Definition
25.Control Sequence Definitions
26.Amend Password
27. Report Definition
28.Operator Buttons
29.
30.
31.SunQuery
32.SunExtras
33. Data Access Groups
34.Analysis Mapping Rules
35.Analysis Mapping
36.Analysis Category Lengths
37.
38.
39.
40.
41.Audit Control
42.
43.

44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81. Event Profiles
82. Rule Sets
83. Rule Messages
84. Lookup Table Profiles
85.Lookup Tables
87. Definable Data Items
88. Transfer Profiles
89. Transfer Manager
90.
91. Reconciliation Profiles
92. Reconciliation Accounts
93.Reconciliation Manager

94.
95.
96.
97.
98.
99.Business Views
System Code = SA (user input LA)
to restrict.
1. Journal Entry
2.
3. Account Inquiry
4. Account Allocation
5. Journal Import
6. Journal Listing
7. Account Listing
8. Trial Balance
9. Ledger Revaluation
10.Change Budgets
11.Period Cleardown
13.Names and Addresses
14.Analysis Codes
15.Ledger Definition
16. Journal Definitions
17.Analysis Definitions
18. Statement Layouts
19. Statement Line Contents
21. Transfer Layouts
22.Column Headings
23. Commitment Inquiry
25.Financial Statements
26.Financial Analysis
27.Analysis Layouts
28.
29.Debtor Transfer
30. Standard Descriptions
31.Generate Payments
32. Print Remittences
33. Creditor Transfer
34.Balance File Rebuild
35.Bank Details
36. New Period
37.Balance File Update
38.

39.
40. Print Statements
41. Transaction Matching
42. Print Tax Listing
43. Print Account Tax Listing
44.Cash Tax Allocation
45.Day Book Listing
46. Treasurer Interface Definitions
47.Treasurer Transactions Definitions
48.Budget Definitions
49.Discount Terms Definition
50. Format Definitions
51.Audit Control
52.Void Payments
53. Ledger Export
54. Export Definitions
55. Export Consolidation
56.Journal Presets
57.
58. Daybook Definition
59.
60.
61. Payment Listing
62.Generate Debits
63. Table Formats
64. Table Rows
65. Table Columns
66.
67.Financial Tables
68.Aged Analysis
69.Aged Analysis Layouts
71. Formatted Layouts
72. Print Formatted Accounts
73.Tax Listing Layouts
74.
75.Conversion Definitions
76. Payment Profiles
77. Tax Details
78. Daily Conversion Tables
79.Sequence Number Definition
80.Post Rough Book
81.Budget Check Definition
82. Payment Reference Data
83.
84.
85.
86.
87.
88.Tax Accounts

89. Payment Term Definitions

90.Payment Term Instalments
91.
92.
93.
94.
95.
96.
97.
System Code = SC (user input CO)
to restrict.
1.
2.
3. Account Inquiry
4.
5. Journal Import
6. Journal Listing
7. Account Listing
8.
9.
10.Change Budgets
11.
13.
14.Analysis Codes
15.Ledger Definition
16.Analysis Layouts
17.
18. Statement Layouts
19. Statement Line Contents
21.
22.Column Headings
23.
24.
25.Financial Statements
27.
28.
31.
32.
33.
34.
35.

36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.Budget Definition
49.
50.
51.Audit Control
52.
53. Ledger Export
56.
57.
58.
59.
60.
61.
62.Financial Tables
63. Table Formats
64. Table Rows
65. Table Columns
66.
67.
68.
69.
71.
72.
73. Allocation Ratios
74. Allocation Sources
75.Allocation Targets
76. Allocation Definitions
77.Generate Allocations
78.Definition Report
79. Calendar Definitions
80.
82.
83.
84.
85.

86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.
System Code = SF (user input AR)
to restrict.
1. Journal Entry
2. Journal Import
3. Calculate Depreciation
4.
5.
6.
7. Asset Inquiry
8. Mark For Disposal
9. Asset Disposal
10.Asset Budget Records
11.Asset Records
13.Asset Analysis
14.Analysis Codes
15. Asset Diary
17. New Period
18.Change Budgets
19.Period Cleardown
21.
22.
25.Journal Listing
26. Asset Listing
27. Asset Register
28. Asset Status
30. Standard Descriptions
31.

32.
33.Register Definition
34.Budget Definitions
36. Journal Definitions
37. Spread Ratios
38.Audit Control
39.Analysis Layouts
40.Column Headings
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53. Ledger Export
56.Journal Presets
57. Table Headings
58.Depreciation Tables
59.Depreciation Tables Listing
60.
61.
62.
63. Table Formats
64. Table Rows
65. Table Columns
66.
67.Financial Tables
68.
69.
71.
72.
73.
74.
76.
77. Tax Details
79.Sequence Number Definitions
80.
81.Budget Check Definitions

82.
83.
84.
85.
86.
87.
88.Tax Accounts
89. Payment Terms Definitions
90.Payment Terms Instalments
91.
92.
93.
94.
95.
96.
97.
98.
System Code = SO (user input SO)
to restrict.
1. Sales Order Entry
2. Inventory Allocation
3. Sales Import
4. Quotation Entry
5. Sales Inquiry
6. Customer Inquiry
7. Item Inquiry
8.
11. Item Records
13.Analysis Codes
14. New Period
15.Period Cleardown
16. Customer Listing
17.
18.Sales Analysis
19.Order Status
20.
21.Sales Listing
22.Quotation Conversion
23.Despatch Counter
24. Print Quotations
25. Print Acknowledgements
26. Print Picking Docs
27. Sales Format Definition

28. Print Invoices

29.Business Definition
30.Analysis Definition
31. Calculation Definitions
32. Calculation Tables
33.Sales Order Definitions
34.Sales Order Header Presets
35.Sales Order Detail Presets
36.Ledger Interface
37. Location Definitions
38. Item Special Processes
40.Analysis Layouts
41.Void Despatch Numbers
42.
43.
44. Print Despatch Docs
45. Item Descriptions
46.Price Books Maintenance
47.Price Book Hierarchy
48.Audit Control
49. Unit Conversion Tables
50.Price Book Definitions
51. Document Counter
52.Returns/Exchange Parameters
53.Credit/Debit Note Assoc
54. Update BSP
55. Print Alt Picking Docs
56.Statistical Layouts
57. Prints Stats Declaration
58.Minimum Order Tolerance
59.Authorisation Parameters
60.Invoice Prefix
61. Assembly Structure
62. Assembly Structure List
63.Print SOP Miscellaneous Docs
64.System Labels
65.Price Book Listing
66.Authorisation Groups
67. Release Cleardown
68. Invoice Modification
69. Order Modification
70. Modification Definition
71.Address Analysis
72.Release Authorisation
73.Expiration Lead Times
74.Amend Picked Quantities
76.Void Invoices Numbers


79. Free Goods Rules
80. Free Goods Setup
81.Generate Returns
82. Payment Reference Data
83. Tracking Code Parameters
84.Tracking Code Maintenance
85.Excluded Combinations
86. Density Maintenance
87.
88. Transaction Audit Control
89.
90.
91.
92.
93.
94.Additional Header Labels
95.
96.
97.
98.
System Code = SP (user input PO)
to restrict.
1. Purchase Order Entry
2. Purchase Invoice Entry
3. Purchase Invoice Matching
4. Goods Receipt Matching
5. Invoice Approval
6.
7. Purchase Import
8.
9.
10.Purchase Inquiry
11.Supplier Inquiry
12. Item Inquiry
15. Item Records
16. Item Suppliers
18.Analysis Codes
19. New Period
20.
21. Commitment Transfer
22.Period Cleardown
23.

24.Purchase Listing
25.Supplier Listing
26.Invoice Register
27.Purchase Commitment
28. Commitment Inquiry
29.Purchase Order Status
30.Order Amendment Listing
31.Print POP Miscellaneous Documents
32.Additional Header Labels
33. Print Purchase Orders
34.Maintain Document Counter
35.
36.
37.
38.
39.
43. Calculation Definitions
44. Calculation Tables
45.Purchase Order Definitions
46.Purchase Header Presets
47.Purchase Detail Presets
48.Ledger Interface
51. Item Special Processes
52.Audit Control
53.
54.
55.
56.Statistical Layouts
57. Print Statistical Declaration
58.
59.
60.
61.
62.
63.
64.System Labels
65.
66.
67.
68.
69.
70.
71.Address Analysis
72.
73.

74.
76.
80.
82.
83.Purchase Format Definition
84.
85.
86.
87.
88. Transaction Audit Control
89.
90.
91.
92.
93.
94.
95.Charge Index
96.Additional Cost Voucher
97.
98.
System Code = SM (user input IC)
to restrict.
1. Movement Entry
2. Inventory Allocation
3. Movement Import
4.
5. Inventory Inquiry
6. Movement Inquiry
7.
8.
9. Item Records
10. Item Suppliers
12.Analysis Codes
13. New Period
14.Period Cleardown
15. Inventory Status
16.
17.Movement Analysis
18. Movement Listing
19.Inventory Listing

20.
21. Inventory Evaluation
22.Inventory Usage
23. Inventory Cover
24.
25. Print Movements
26.
27.
28.
31. Movement Definitions
32.Movement Presets
33.Ledger Interface
37.Analysis Layouts
38.
39.
40.
41.
42.
43.
44.
45. Expired Items
46.
47.
48.Audit Control
49.
50.
51.
52.
53. Stock Take Definitions
54. Generate Stock Take
55. Stock Take Entry
56. Stock Take Inquiry
57. Stock Take Approval
58. Stock Take Listing
59. Stock Take Valuation
60.Movement Values Definition
61. Assembly Structure
63. Assembly Structure List
64.Stock Take Clearance
65.System Labels
66.Batch Allocation
67.Amend Receipt Reference
68.Inventory Transfer
69. Revalue Inventory

70. New Cost Definition

71. Movement Accounts
72. Location Accounts
73.Revaluation Analysis
74.Revaluation Profiles
76. Cost Import
79. Item Entry
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.
System Code = SG (user input MM)
to restrict.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.

16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
41. Item Records
43. Item Suppliers
45.Analysis Codes
49.Address Analysis
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.

66.
67.
68.
69.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
System Code = SX (user input SX)
to restrict.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

13.
14.
15.
16.
17.
18.
19.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.

63.
64.
65.
66.
67.
68.
69.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.

Chapter 15 Appendix F – Limits in
SunSystems v4 15
The following is a list of potential restrictions not obvious to users of SunSystems v4.
This list should not however be taken as definitive, as other restrictions may apply which are
not listed here.
Journal Entry and Journal Import

The maximum number of lines in a journal is 9999999. If this limit is reached Journal Entry or
Journal Import will start again at Journal line number 0000001 which potentially could cause a
duplicate key error.
Account Listing
Maximum of 50 conversion codes.
Account Inquiry and Account Allocation

A maximum of 14 conversion codes for any single account can be displayed and a maximum
of 999999 transactions per account, although the sequencing function uses a COBOL sort
routine which may be Operating System dependent.
Financial Tables
Maximum of 500 table rows and 50 table columns.
Purchase Order Processing

999 is the maximum number of lines per order. The maximum descriptive lines per detail line
is 52 (A-Z, a-z). The maximum split lines per detail line is 9.
Sales Order Processing

999 is the maximum number of lines per order. The maximum descriptive lines per detail line
is 2500 (AA-zz). The maximum split lines per detail line is 99.
Inventory Control
A maximum of 9999 lines per Movement.
Stock take
Each stock take generated is limited to 9000 lines (0001 - 9000). If one stock take is longer
than 9000 lines a new stock take is automatically generated. Line numbers 9001 - 9999 are
reserved for creating movements.
Standard macro definition format

There is a maximum of 10000 lines per macro, a maximum of 10 variables per macro and the
limit of macros allowed is 200.

Appendix F – Limits in SunSystems v4
File size limits

The maximum sizes of files available in SunSystems v4 on various platforms are listed below.
You should ensure that your files do not reach the maximum sizes listed. Regular use of
PC=Period Cleardown helps reduce file size. To prevent files reaching maximum size limits
you may also want to use more than one database.
Maximum known file sizes available in SunSystems v4 on various platforms are:
MS DOS/MS Windows
Current versions of Microfocus COBOL limit the size of indexed files to 1 gigabyte.
Btrieve
Btrieve limits files to a size of 4 gigabytes.

UNIX
There is a generic UNIX constraint which limits files to a size of 2 gigabytes. You can use the
system parameter ULIMIT if you want to impose a lower limit.
Movement Order Batch Number limits

The maximum movement order batch number is 99999.

Appendix G – Process Manager Commands and Call Points
Chapter 16 Appendix G – Process

Manager Commands and Call Points 16
This appendix provides information about the matrix of commands and call points for each
function in Process Manager. See the section Event Profiles for details.
The notes below apply to the following tables where marked:
Notes
1. Not supported by this function.
2. If set, this will be treated like DISPLAY.
3. Workspace fields, plus Description, Due Date, ten T-Codes, Allocation Indicator (W, F, P,
R, space, or number).
4. Workspace fields only.
5. Only with WRITE MACRO.
6. Before Quantity.
7. Before Calculation Value.
8. Workspace fields, plus M-Codes, Account Codes, and Calculation Values.
9. Workspace fields plus Order Quantity.
10.Workspace fields plus Stock Quantity.
11.Display results in a message being output to Business Analyser. The message code will
also be shown in the Sales Order Import file SI report.
12.After Item Code.
13.Before Purchase Quantity.
14.Workspace fields, plus M-Codes, Account Codes, Calculation Value, Asset Code and
Asset Subcode.
15.Workspace fields, plus Supplier Item description.
16.Workspace fields, plus Purchase Quantity.
17.Workspace fields, plus Stock Quantity.
18.Display results in a message being output to Business Analyser. The message code is
also shown in the Purchase Order Import file report.
19.Only where source is Bill of Materials and target is Inventory Movements file, or Sales
Order file, or external files based on these two.
20.Workspace fields, plus Analysis Codes M0-M9.

JE=Journal Entry
Call Point Command
AMEN CAL CALL DISPL ERR EXPLOD IF MATC OR RUN RUN SET WRIT
D1 C AY OR E1 H1 W E
(Default) No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes Yes5
3
s
00001 Transaction Line No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes Yes5
3
s
00002 Prior to Journal Post No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes Yes5
4
s
00003 Each Line Posted No Yes Yes Yes Yes2 No Yes No Ye Yes Yes Yes Yes5
4
s
00004 Start of Session No Yes Yes Yes Yes2 No Yes No Ye Yes Yes Yes Yes5
4
s
00005 End of Session No Yes Yes Yes Yes2 No Yes No Ye Yes Yes Yes Yes5
4
s
00006 Header1 No No No No No No No No No No No No No
00007 Release1 No No No No No No No No No No No No No
00008 Hold Journal No Yes Yes Yes Yes2 No Yes No Ye Yes Yes Yes Yes5
4
s
00009 Journal Posted No Yes Yes Yes Yes2 No Yes No Ye Yes Yes Yes Yes5
4
s

Call Point Command
00100 Item Code1 No No No No No No No No No No No No No
00101 Order Quantity1 No No No No No No No No No No No No No
00102 Stock Quantity1 No No No No No No No No No No No No No
00103 Calculation Code 11 No No No No No No No No No No No No No

Call Point Command
00200 Transfer Manager No No No No No No No No No No No No No

Summary1

JI=Journal Import
Call Point Command
AMEN CALC CALL DISPL ERR EXPLOD IF MATC OR RU RUN SET WRIT
1 1 1
D AY OR E H N W E
(Default) No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes3 Yes5
s
00001 Transaction Line No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes3 Yes5
s
00002 Prior to Journal Post No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes4 Yes5
s
00003 Each Line Posted No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes4 Yes5
s
00004 Start of Session No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes4 Yes5
s
00005 End of Session No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes4 Yes5
s
00008 Hold Journal1 No No No No No No No No No No No No No
00009 Journal Posted1 No Yes Yes Yes Yes No Yes No Ye No No Yes4 Yes5
s

Call Point Command
D1 AY OR E1 H1 N W E

Call Point Command
D1 AY OR E1 H1 N W E

Summary1

QE=Quotation Entry and SE=Sales Order Entry

Call Point Command
AMEND1 CAL CALL DISPL ERR EXPLOD IF MATC OR RU RUN SET WRIT
C AY OR E1 H1 N W E
(Default) No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes8 Yes5
s
00001 Transaction Line No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes8 Yes5
s
00002 Prior to Journal Post1 No No No No No No No No No No No No No
00003 Each Line Posted1 No No No No No No No No No No No No No
00004 Start of Session1 No No No No No No No No No No No No No
00005 End of Session1 No No No No No No No No No No No No No
00006 Header No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes4 Yes5
s
00007 Release No Yes Yes Yes Yes2 No Yes No Ye Yes Yes Yes4 Yes5
s
00009 Journal Posted1 No No No No No No No No No No No No No
00100 Item Code1 No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes4 Yes5
s

Call Point Command
C AY OR E1 H1 N W E
00101 Order Quantity6 No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes9 Yes5
s
00102 Stock Quantity6 No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes1 Yes5
0
s
00103 Calculation Code 17 No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes8 Yes5
s
s
s
s
s
00108 Calculation Code 67 No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes8 Yes
s
s
s

Call Point Command
C AY OR E1 H1 N W E
s
s
s
s
s
s
s
00118 Calculation Code 167 No Yes Yes Yes Yes No Yes No Ye Yes Yes Yes8 Yes
s
s
s

Call Point Command
C AY OR E1 H1 N W E
s
s

Summary1

SI=Sales Order Import

Call Point Command
AMEND1 CALC CALL DISPLAY ERROR EXPLODE1 IF MATCH1 OR RUN RUNW SET WRITE
(Default) No Yes Yes Yes11 Yes11 No Yes No Yes Yes Yes Yes Yes
00001 Transaction No Yes Yes Yes11 Yes11 No Yes No Yes Yes Yes Yes Yes
Line
00002 Prior to Journal No No No No No No No No No No No No No

Post1
00003 Each Line No No No No No No No No No No No No No

Posted1
00004 Start of No No No No No No No No No No No No No
Session1
00005 End of No No No No No No No No No No No No No
Session1
00006 Header No Yes Yes Yes Yes2 No Yes No Yes Yes Yes Yes4 Yes5
00007 Release No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes4 Yes5
00009 Journal No No No No No No No No No No No No No
Posted1
00100 Item Code No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes Yes5

Call Point Command
00101 Order No No No No No No No No No No No No No
1
Quantity
00102 Stock No No No No No No No No No No No No No
Quantity1
00103 Calculation No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes Yes5
Code 1
Code 2
Code 3
Code 4
Code 5
Code 6
Code 7
Code 8

Call Point Command
Code 9
Code 10
Code 11
Code 12
Code 13
Code 14
Code 15
Code 16
Code 17
Code 18

Call Point Command
Code 19
Code 20
00200 Transfer No No No No No No No No No No No No No
Manager
Summary1

PE=Purchase Order Entry, VE=Purchase Invoice Entry, and

VM=Purchase Invoice Matching
Call Point Command
(Default) No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes14 Yes
00001 Transaction No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes14 Yes
Line
00002 Prior to No No No No No No No No No No No No No
Journal Post1

Posted1
Session1
Session1
00006 Header No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes4 Yes5
00007 Release No Yes Yes Yes Yes2 No Yes No Yes Yes Yes Yes4 Yes5
Posted1

Call Point Command
00100 Item Code12 No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes15 Yes5
00101 Order No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes16 Yes5
13
Quantity
00102 Stock No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes17 Yes5
Quantity6
00103 Calculation No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes14 Yes5
7
Code 1
Code 27
7
Code 3
Code 47
7
Code 5
Code 67
7
Code 7

Call Point Command
7
Code 8
7
Code 9
7
Code 10
7
Code 11
7
Code 12
7
Code 13
7
Code 14
7
Code 15
7
Code 16
7
Code 17

Call Point Command
7
Code 18
7
Code 19
7
Code 20
Manager
Summary1

PI=Purchase Import
Call Point Command
(Default) No Yes Yes Yes18 Yes18 No Yes No Yes Yes Yes Yes14 Yes
00001 Transaction No Yes Yes Yes18 Yes18 No Yes No Yes Yes Yes Yes14 Yes
Line
Journal Post1

Posted1
Session1
Session1
00006 Header No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes Yes
00007 Release No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes Yes
Posted1

Call Point Command
1
Quantity
Quantity1
00103 Calculation No No No No No No No No No No No No No
1
Code 1
Code 21
1
Code 3
Code 41
1
Code 5
Code 61
1
Code 7
Code 81

Call Point Command
Code 91
Code 101
Code 111
Code 121
1
Code 13
Code 141
1
Code 15
Code 161
1
Code 17
Code 181

Call Point Command
1
Code 19
Code 201
Manager
Summary1

TR=Transfer Manager
Call Point Command
AMEND CALC CALL DISPLAY ERROR1 EXPLODE IF MATCH OR RUN RUNW SET WRITE
(Default) Yes Yes Yes Yes No Yes19 Yes Yes Yes Yes Yes Yes Yes
00001 Transaction Yes Yes Yes Yes No Yes19 Yes Yes Yes Yes Yes Yes Yes
Line

Post1

Posted1
Session1
00005 End of Session No Yes Yes Yes No No Yes No Yes Yes Yes Yes4 Yes5

Call Point Command
Code 11
Code 21
Code 31
Code 41
Code 51
Code 61
Code 71
Code 81
Code 91

Call Point Command
Code 101
Code 111
Code 121
Code 131
1
Code 14
Code 151
1
Code 16
Code 171
1
Code 18
Code 191

Call Point Command
1
Code 20
00200 Transfer No Yes Yes Yes No No Yes No Yes Yes Yes Yes Yes
Manager
Summary

RN=Reconciliation Manager
Call Point Command
AMEND1 CALC1 CALL1 DISPLAY1 ERROR EXPLODE1 IF MATCH OR RUN1 RUNW1 SET1 WRITE1
1
(Default) No No No No No No Ye Yes Ye No No No No
s s
00001 Transaction Line No No No No No No Ye Yes Ye No No No No

s s

Post1
00003 Each Line Posted1 No No No No No No No No No No No No No
00004 Start of Session1 No No No No No No No No No No No No No
00005 End of Session1 No No No No No No No No No No No No No

Call Point Command
1
00112 Calculation Code No No No No No No No No No No No No No

101

1
11

121

Call Point Command
1

131

141

151

161

171

181

191

201

Summary1

ME=Movement Entry
Call Point Command
(Default) No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes20 Yes5
00001 Transaction No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes3 Yes5
Line
Journal Post

Posted
Session
00005 End of No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes Yes
Session
Posted1

Call Point Command
Quantity1
Quantity1
Code 11
Code 21
1
Code 3
Code 41
1
Code 5
Code 61
1
Code 7
Code 81

Call Point Command
1
Code 9
Code 101
1
Code 11
Code 121
1
Code 13
Code 141
1
Code 15
Code 161
1
Code 17
Code 181

Call Point Command
Code 191
Code 201
Manager
Summary1

MI=Movement Import
Call Point Command
(Default) No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes20 Yes5
00001 Transaction No Yes Yes Yes Yes No Yes No Yes Yes Yes Yes3 Yes5
Line
Journal Post

Posted
Session
Session
00007 Release No No No No No No No No No No No No No
00008 Hold Journal No No No No No No No No No No No No No
Posted

Call Point Command
Quantity1
Quantity1
Code 11
Code 21
1
Code 3
Code 41
1
Code 5
Code 61
1
Code 7
Code 81

Call Point Command
1
Code 9
Code 101
1
Code 11
Code 121
1
Code 13
Code 141
1
Code 15
Code 161
1
Code 17
Code 181

Call Point Command
Code 191
Code 201
Manager
Summary1

SS4TechnicalReferenceManual PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SS4TechnicalReferenceManual PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Infor SunSystems Technical

About this guide ............................................................................................................................. 19

Chapter 1 System Overview ......................................................................................................... 23

Chapter 2 Naming Conventions ................................................................................................... 29

SunSystems v4 Technical Reference Manual | 3

Examples ................................................................................................................................. 36

Chapter 3 Screens and Menus ..................................................................................................... 39

4 | SunSystems v4 Technical Reference Manual

Local actions .................................................................................................................................. 55

SunSystems v4 Technical Reference Manual | 5

Validation limitations ................................................................................................................ 63

6 | SunSystems v4 Technical Reference Manual

Index of Categories ........................................................................................................................ 82

Chapter 4 Reference Maintenance ............................................................................................... 89

SunSystems v4 Technical Reference Manual | 7

Add-on Product - Suggested slot assignment/layout format ....................................................... 109

Chapter 5 Printed Output ............................................................................................................ 111

Chapter 6 User Hooks ................................................................................................................. 113

8 | SunSystems v4 Technical Reference Manual

Purchase Order/Invoice Entry – Header Level - SPPE......................................................... 139

Chapter 7 Hidden Functions ....................................................................................................... 141

SunSystems v4 Technical Reference Manual | 9

Close ...................................................................................................................................... 152

Chapter 8 Data Dictionary and Report Definition ..................................................................... 155

10 | SunSystems v4 Technical Reference Manual

Language Code ..................................................................................................................... 159

SunSystems v4 Technical Reference Manual | 11

Record Type .......................................................................................................................... 163

Chapter 9 Associating Images with SunSystems v4 Modules ............................................... 165

Chapter 11 Appendix B - Master Data Files ................................................................................ 173

12 | SunSystems v4 Technical Reference Manual

Summary of record types............................................................................................................. 553

Chapter 12 Appendix C – SunSystems v4 Backup Files ........................................................... 719

SunSystems v4 Technical Reference Manual | 13

Description ................................................................................................................................... 719

14 | SunSystems v4 Technical Reference Manual

Purchase Invoice Header Backup record .................................................................................... 752

Chapter 13 Appendix D – Import Records .................................................................................. 783

SunSystems v4 Technical Reference Manual | 15

Invoice Match Item Header - OINVH ..................................................................................... 800

16 | SunSystems v4 Technical Reference Manual

System Code = SC (user input CO) ............................................................................................ 880

Chapter 15 Appendix F – Limits in SunSystems v4 ................................................................... 895

SunSystems v4 Technical Reference Manual | 17

18 | SunSystems v4 Technical Reference Manual

Types and versions of COBOL

SunSystems v4 Technical Reference Manual | 19

20 | SunSystems v4 Technical Reference Manual

SunSystems v4 Technical Reference Manual | 21

Kernel programs Utilities Application programs

SunSystems v4 Technical Reference Manual | 23

File handler submodules

24 | SunSystems v4 Technical Reference Manual

SunSystems v4 Technical Reference Manual | 25

Chapter 2 Naming Conventions

SunSystems v4 Technical Reference Manual | 29

Program file naming

SBIA.CBL SunBusiness Inventory Allocation

SSFH.CBL SunSystems v4 File Handler

SSFBQF.CBL SunSystems v4 Journal Hold File Backup/Restore.

30 | SunSystems v4 Technical Reference Manual

 cccccc is a meaningful name for the COPY statements contained therein.

SALDGRRC.CPY Ledger File Record Layout