Interface IOG-Imaging Spec for AR Interfaces

8/13/2019 Interface IOG-Imaging Spec for AR Interfaces

http://slidepdf.com/reader/full/interface-iog-imaging-spec-for-ar-interfaces 1/8

IF394 - Imaging Spec for AR Interfaces

South Carolina Enterprise Information System

Interface Operations Guide (IOG)

IF394 - Ima in Spec for !" Interfaces

#9$%4$&9

1 | P a g e




Introduction

Document Purpose and Organization

Interface Operations Guides (IOG contain t!e interface specific information re"uired for Stateof Sout! #aro$ina Agencies to integrate %it! t!e S#&IS s'stem &ac! interface %i$$ contain aseparate IOG %it! specific information )!e IOG information %i$$ inc$ude t!e A*S num+er,description, fi$e name(s , e amp$es of $oad reports, fre"uenc', run sc!edu$e, error conditions,etc Additiona$$', t!e IOG %i$$ contain t!e fi$e $a'out for t!e interface

Genera$ s'stem updates can +e found on t!e S#&IS %e+site, !ttp.//%%% sceis sc go0

| P a g e

http://www.sceis.sc.gov/

http://www.sceis.sc.gov/




Ima in Spec for !" 'e acy Interfaces

Interface ! S um*er IF394

In*ound+Out*ound In+ound

Interface ,itle Imaging Spec for AR 2egac' Interfaces

Interface escription )!is interface is used to send images to S#&IS t!at e ist ase$ectronic fi$es in an agenc' s $egac' s'stem t!erefore, do notneed to +e scanned )!e interface %i$$ process images intoS#&IS and attac! t!em to t!e appropriate SAP recei0a+$edocument )!is imaging spec and processing %or5s incon6unction %it! IOG IF374, AR #ustomer In0oice In+ound

(8ote. For images t!at re"uire scanning t!ere is a manua$scanning and inde ing process used in con6unction %it! IOGIF374 t!at %i$$ attac! images to t!e appropriate SAP recei0a+$edocument )!e manua$ scanning and inde ing process is notpart of t!is specification

• Agencies %i$$ produce a standard image $oad fi$e: formatThe data in the load file must correspond to certaindata that is in the IF384 file (see fi$e $a'out +e$o%

Agencies %i$$ produce one image $oad fi$e for eac! IF374fi$e

• Important -- ! encies are responsi*le to assurethat the Source System In#oice um*er is a uni.uenum*er across all years$

• Agencies %i$$ p$ace t!e image $oad fi$e and image fi$esinto a specified F)P director'

• After S#&IS processes eac! IF374 fi$e and t!ecorresponding image $oad fi$e S#&IS %i$$ attac! t!eimage(s to t!e appropriate SAP recei0a+$e document(sImages %i$$ t!en +e a0ai$a+$e for 0ie%ing in t!e

attac!ment $ist of t!e SAP document• An error fi$e %i$$ +e produced +' S#&IS and p$aced into a

specified F)P director' )!e agenc' %i$$ +e responsi+$efor correcting errors and resu+mitting t!roug! t!einterface, or using t!e manua$ process to attac! imagesto SAP pa'a+$e documents

3 | P a g e




/ersion ;ersion 1 <

SCEIS 0oint of Contact =i5e Sa'$es (msa'$es>sceis sc go0

Source System State Agenc' Su+s'stems

estination System S#&IS

Interface ,ype 2oad Fi$e. Formatted te t fi$e ( t tImage Fi$es. )IF fi$es ( tif

1ode As'nc!ronous

Fre.uency Agencies %i$$ transmit IF394 fi$es in con6unction %it! IF374 fi$es)!ere can +e a corresponding IF394 fi$e for eac! IF374 fi$e, or asing$e IF394 fi$e for mu$tip$e IF374 fi$es

File ame(s) In+ound interface fi$e.?+usiness area@ if394 imaging in+ound ?date/time stamp@

)!e ?date/time stamp@ does not !a0e to +e t!e same?date/time stamp@ of t!e corresponding IF374 fi$e(s

&rror fi$e.?+usiness area@ if394 imaging errors ?date/time stamp@

F,0 0ath *etermined +' securit' re"uirements of t!e sending agenc'

4 | P a g e




Ima e 'oad File 'ayout

8e% *oc1 usinessArea. ? usiness Area@*oc)'pe. ?)ransaction Be'@

32egac'Be'. ? usiness AreaCSource S'stem IdentifierCSource S'stem In0oice 8um+er@4DipaaPri0ate. ?Ees/8o@Fi$e8ame. <<<<<<<1 )IFFi$e8ame. <<<<<<< )IF

8e% *oc1 usinessArea. ? usiness Area@

*oc)'pe. ?)ransaction Be'@32egac'Be'. ? usiness AreaCSource S'stem IdentifierCSource S'stem In0oice 8um+er@4DipaaPri0ate. ?Ees/8o@Fi$e8ame. <<<<<<<3 )IFFi$e8ame. <<<<<<<4 )IFFi$e8ame. <<<<<<< )IF

Repeat for eac! Source S'stem In0oice 8um+er to %!ic! images must +e attac!ed

| P a g e




Ima e 'oad File "e.uirements1 )!e imaging interface is used in con6unction %it! IOG spec IF374 (AR #ustomer In0oice

In+ound )!e image $oad fi$e specifies %!ic! SAP document eac! image %i$$ +e attac!edto A different SAP document is produced for eac! different Deader Se"uence 8um+er: int!e IF374 interface fi$e )!e Deader )e t fie$d of t!e IF374 interface must contain t!eSource S'stem In0oice 8um+er

&ac! fie$d 0a$ue in t!e image $oad fi$e must e2actly match t!e specified fie$d in t!e IF374interface fi$e

Field ame IF3 4 /alue Clarifications1 usinessArea usiness Area Same format as IF374

*oc) 'pe )ransaction Be' Same format as IF37432egac'Be' usiness AreaCSource S'stem

IdentifierCSource S'stem In0oice8um+er

8ote. Source S'stem In0oice8um+er must +e in t!e Deader)e t fie$d of t!e IF374 fi$e

)i$de separated (Cconcatenation of 0a$ues%it! same format for eac!0a$ue as IF374

4DippaPri0ate Ees/8o

8ote. DipaaPri0ate is not a datafie$d in t!e IF374 interface

HEes in t!is fie$d %i$$ restrict0ie%ing of t!ese images tousers t!at !a0e t!e DIPPAImage ;ie%ing ro$e

3 Source S'stem In0oice 8um+er must +e in t!e Deader )e t fie$d of t!e IF374 fi$e

4 Source S'stem In0oice 8um+er must +e uni"ue across a$$ 'ears )!e agenc' isresponsi+$e for insuring uni"ueness If Source S'stem In0oice 8um+er is repeated, imagesma' +e attac!ed to t!e %rong SAP document

)!ere ma' +e more t!an one 3LegacyKey $ine in a New Doc segment & p$anation. (a Ift!ere is one 3LegacyKey $ine in a New Doc segment t!e tif fi$es in t!at New Doc segment%i$$ +e attac!ed to 6ust one SAP document (+ If t!ere is more t!an one 3 LegacyKey $inein t!e New Doc segment t!e tif fi$es in t!at New Doc segment %i$$ +e attac!ed to mu$tip$eSAP documents

| P a g e




FileName fie$ds identif' t!e image fi$es t!at %i$$ +e attac!ed to t!e SAP document(s Imagefi$es ma' +e sing$e-page or mu$ti-page )IF fi$es &ac! fi$e %i$$ +e a separate attac!ment int!e SAP document attac!ment $ist

J | P a g e




0rocess Flo chart

7 | P a g e

Documents

Interface IOG-Imaging Spec for AR Interfaces