Subject: | |
From: | |
Reply To: | |
Date: | Wed, 17 Nov 1999 19:09:34 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
File PART Org Detail Type Image
Record PART
Item PART-NBR Cha*18 ; Index to A-PART
Item PART-TYPE Cha*2
Item PART-NAME Cha*30
Item PART-UM Cha*4
Item PART-UM-PRCH Cha*4
Item PART-UM-SALE Cha*4
Item PART-UNIT-WGT Num*18 Decimals 3
; and so on
File BILL Org Detail Type Image
Record BILL
Item PARENT Cha*18 ; Index to A-PARENT
Item CHILD Cha*18 ; Index to A-CHILD
Item REVISION Cha*4
Item REV-BEGIN Date Century Included
Item REV-END Date Century Included
Item BILL-QTY Num*18 Decimals 3
; and so on.
The program then chains recursively thusly:
While Reading Part
Chain to BILL where PARENT equals PART-NBR
Chain to PART 2nd occurrance where 2nd PART-NBR equals CHILD
Ignore records out of REV-BEGIN to REV-END range.
Example:
PART-NBR TYPE WGT-PER-UNIT NAME
TITAN-IVB LV 1,895,000 Titam IVB Launch Vehicle
USRM SRB 770,500 Stage Zero Boosters
TIVB-1 LRB 325,000 Core Stage 1
TIVB-2 LRUS 90,000 Core Stage 2
CENTAUR-G LRUS 45,000 Upper Stage
PARENT CHILD BILL-QTY
TITAN-IVB USRM 2
TITAN-IVB TIVB-1 1
TITAN-IVB TIVB-2 1
TITAN-IVB CENTAUR-G 1
Everything else is added on as you wish - Pricelists, UPC Xrefs, and so
on.
Marc Walgren wrote:
>
> Greeting. I have to write a bill of materials application for my hp3k. I
> have an proprietory inventory system running TurboImage.
>
> Anybody have any suggestions on an existing data structure I could adapt for
> my use?
>
> TIA
> Marc Walgren
|
|
|