[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference edieng::edi_standards_information

Title:EDI_STANDARDS_INFORMATION
Moderator:METSYS::HELLIAR
Created:Thu Apr 13 1989
Last Modified:Fri Mar 21 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:116
Total number of notes:532

116.0. "X.12 and EDIFACT - Y2k compliant?" by REFDV1::ESULLIVAN () Thu Mar 20 1997 21:37

    Are EDI Standards, ASC X.12 and EDIFACT, Y2k compliant?
    
    Eleanor
T.RTitleUserPersonal
Name		DateLines
116.1Its open to interpretationSYSTEM::HELLIARhttp://samedi.reo.dec.com/Fri Mar 21 1997 17:276
    What is 'Y2K compliant'?
    
    Dates can be in many forms in the EDI data, although YYMMDD is quite
    common in the service segments. 
    
    Graham
116.2EDI and the year 2000REFDV1::REF_SUPPORTFri Mar 21 1997 20:0621
    Graham,
    
    	ASC X.12 V3020 introduces the field, century, to the DTM segment. 
    	So, CCYYMMDD, would meet a trading partner's semantic requirement
    	to pass/receive 19991231 or 20000101 in the DTM segment.  I have
    	not looked for other date representations in ANSI X.12 version,
    	but I did notice that ASC X.12 V3050 (the latest manual that I
        have) ISA segment has a date field of 6/6.
    
    	Will EDI date fields of 6/6 cause a problem in the year 2000?
    	What is ANSI and EDIFACT's position on  6/6 date fields?  Will
    	these date fields be expanded to include century?  Will the century
    	field be added to those segments that have 6/6 date fields?
    
    	Will DEC/EDI(Filebridge) require a release to meet Y2k processing
    	requirements (whatever they are), or are no changes necessary?
    	Have any requirements been presented by DEC/EDI users? 
    
    Regards,
    
    Eleanor