EDI: Cyberbanking Certificate Altering for Microsoft Abundant Plains overview for Software Developer/Programmer/DBA

 31 December 18:00   

    EDI: Cyberbanking Certificate Altering for Microsoft Abundant Plains overview for software Developer/Programmer/DBA   by Andrew Karasev

    Microsoft Abundant Plains - Microsoft Business Solutions accounting and ERP system, originally targeted to mid-size - now, with advancements and accretion believability of its database - Microsoft SQL Server, Abundant Plains is adorable band-aid for ample corporation. Big companies usually accept purchasing and adjustment processing automation via alleged Cyberbanking Certificate Altering or EDI. EDI was alien continued time ago for UNIX systems and in alotof of the cases appears in the anatomy of Header, Curve and Bivouac of predefined anchored position fields.

    We would like to accord you - programmer, software developer, database ambassador the primary clues on bearing EDI formatted argument from Microsoft Abundant Plains database. Please, agenda about that Abundant Plains actuality is taken as the example, agnate access will plan for additional SQL based systems: Navision (SQL Database or C/SIDE database), Microsoft RMS, Solomon as able-bodied as Answer and additional non-Microsoft products. In the case of non-SQL system, such as old Abundant Plains Dynamics, ACCPAC on Common SQL - IDE interface will absorb ADO/ODBC or Microsoft Admission programming.

    1. Sample Concern The concern beneath uses Casting architecture to create the aftereffect anchored breadth and accommodated the positioning. Additional the unionizing allows to aftermath Attack and Detail in one baddest statement. Actuality we are ambidextrous with plan Sales Documents

    select

    case

    when b.LNITMSEQ=c.LNITMSEQ+1 and b.CMPNTSEQ=c.CMPNTSEQ+1 then CAST( Attack as char(10))

    else CAST( Detail as char(10))

    end

    as FIELD0,

    case

    when b.LNITMSEQ=c.LNITMSEQ+1 and b.CMPNTSEQ=c.CMPNTSEQ+1 then cast(a.CUSTNAME as char(65))

    else cast(cast(b.QTYDMGED as decimal(19,5)) as char(65))

    end

    as FIELD01,

    case

    when b.LNITMSEQ=c.LNITMSEQ+1 and b.CMPNTSEQ=c.CMPNTSEQ+1 then CONVERT(char(51), a.DOCDATE, 101)

    else cast(b.ITEMDESC as char(51))

    end

    as FIELD03

    --Additional fields go here

    from SOP10100 a accompany SOP10200 b on a.SOPTYPE=b.SOPTYPE and a.SOPNUMBE=b.SOPNUMBE join

    RM00101 d on a.CUSTNMBR=d.CUSTNMBR

    join

    (select SOPTYPE as SOPTYPE, SOPNUMBE as SOPNUMBE,

    LNITMSEQ

    as LNITMSEQ,

    CMPNTSEQ

    as CMPNTSEQ from SOP10200

    union

    select SOPTYPE as SOPTYPE, SOPNUMBE as SOPNUMBE, MIN(LNITMSEQ)-1 as LNITMSEQ, MIN(CMPNTSEQ)-1 as CMPNTSEQ from SOP10200

    group by SOPTYPE, SOPNUMBE

    ) c on a.SOPTYPE=c.SOPTYPE and a.SOPNUMBE=c.SOPNUMBE

    and ((b.LNITMSEQ=c.LNITMSEQ and b.CMPNTSEQ=c.CMPNTSEQ) or (b.LNITMSEQ=c.LNITMSEQ+1 and b.CMPNTSEQ=c.CMPNTSEQ+1))

    left accompany SOP10106 udf on a.SOPTYPE=udf.SOPTYPE and a.SOPNUMBE=udf.SOPNUMBE

    where a.ADDRESS3<> Exported and

    a.SOPTYPE=3 and upper(d.USERDEF2)= YES

    order by a.SOPTYPE, a.SOPNUMBE, b.LNITMSEQ asc

    2. Mark candy abstracts - for this cause we use SOP10100.ADDRESS3 acreage - which was not acclimated in Abundant Plains Dynamics/eEnterprise adaptation 6.0:

    update SOP10100 set ADDRESS3= Exported area SOPTYPE=3

    3. Advice with UNIX EDI Applicant or Server anniversary case requires alone approach. You may accept to accredit the book directory, apparent to the UNIX arrangement or use old DOS command to move the file, or you can accept automated email. Acceptable abstraction is to address advice appliance in your admired programming language

    4. Appointed DTS Amalgamation - you should apparently make DTS amalgamation to do all the steps: alarm SQL Concern and save it as a file, then alarm DOS command or simple EXE appliance - which does acquaint with UNIX

    Happy programming! if you wish us to do the job - accord us a alarm 1-866-528-0577! help@albaspectrum.com