Bob,
My company receives 810's by EDI, have an idea for you to think about. We
have a waiting period before processing invoices on our system. We process
invoices 6 days later to give time for supplies to be received first.
Today's mainframe invoice job: copies 5-day-old file to file to be processed
today; copies 4-day-old file to 5-day-old file, copies 3-day-old file to
4-day-old file, etc. Here are parts of our jcl:
//AGE5DAYS EXEC PGM=IDCAMS,REGION=4096K (5-day-old file copied to file
processed today)
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//INFILE DD DSN=PP1P.EDI810.XXPP810I.AGE5DAYS,DISP=SHR
//OUTFILE DD DSN=PP1P.BATCH.PPB810.IEDI810,
// DISP=(NEW,CATLG,CATLG),
// UNIT=SYSDA,SPACE=(CYL,(1,1),RLSE),
// RECFM=FB,LRECL=400,BLKSIZE=0
//*
//SYSIN DD *
REPRO INFILE(INFILE) OUTFILE(OUTFILE)
/*
//AGE4DAYS EXEC PGM=IDCAMS,REGION=4096K (4-day-old file copied to
5-day-old file)
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//INFILE DD DSN=PP1P.EDI810.XXPP810I.AGE4DAYS,DISP=SHR
//OUTFILE DD DSN=PP1P.EDI810.XXPP810I.AGE5DAYS,DISP=OLD
//*
//SYSIN DD *
REPRO INFILE(INFILE) OUTFILE(OUTFILE)
/*
//*
.....
(additional steps)
.....
//AGETODAY EXEC PGM=IDCAMS,REGION=4096K (copy 810's received today to
1-day-old file)
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//INFILE DD DSN=PP1P.EDI810.FLATFILE.XXPP810I,DISP=SHR
//OUTFILE DD DSN=PP1P.EDI810.XXPP810I.AGE1DAY,DISP=OLD
//*
//SYSIN DD *
REPRO INFILE(INFILE) OUTFILE(OUTFILE)
/*
//*
//XXPPB810 EXEC PGM=IKJEFT01,DYNAMNBR=20,REGION=9M (update 6-day-old
invoice records to system)
//STEPLIB DD DSN=PP6P.TIBATCH.LOADLIB,DISP=SHR
//*
//IEDI810 DD DSN=PP1P.BATCH.PPB810.IEDI810,DISP=SHR
//OEDI810 DD DSN=PP1P.BATCH.TIBAPEDI.EDIFILE,
// DISP=(NEW,CATLG,CATLG),
// UNIT=SYSDA,SPACE=(CYL,(1,1),RLSE),
// RECFM=FB,LRECL=400,BLKSIZE=0
//*
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSDBOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//*
//SYSTSIN DD *
DSN SYSTEM (DB2P)
RUN PROGRAM (PPB810) -
PLAN (TIBPASS)
END
/*
//*
You may be able to do something similar on your system. This is example for
3-day waiting time. Program could move invoice records (based on arrive-date
- current-date, since not all supplies will have same travel time) to a
1-day-old file; after copy 2-day-old file to file to be ftp'ed today for
EDI, and copy 1-day-old file to 2-day-old file.
This is hard to explain in words, but the jcl bits above will give you a
better picture. Give me a call if needed. Hope this helps.
Sandy Denis
business application developer
[EMAIL PROTECTED]
Basin Electric Power Cooperative
701-355-5509
-----Original Message-----
From: Bob Scheuermann [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 17, 2001 3:22 PM
To: [EMAIL PROTECTED]
Subject: Re: outbound 810
All:
Our normal process is to send the 810's the same day we ship the merchandise
to a partner. I had a partner call me today and tell me that I have to hold
the invoice and transmit it when the merchandise is received at their DC.
When I asked how I would know when it was received, they said to transmit it
after the number of days travel time. Example: shipped on 1-15 to arrive
1-18, so I have to send the invoice on 1-18.
They said their system won't process any EDI invoices received prior to the
merchandise being received at their warehouse.
This is the first time I've run into this situation. It means that we have
to hold the invoice and remember to send it 3 to 4 days later. Of course if
we don't EDI the invoice, we get fined.
Is this something anyone else has handled or heard of?
TIA,
Bob Scheuermann
EDI Manager
The Mentholatum Co., Inc.
707 Sterling Drive
Orchard Park, NY 14127
716.677.2500 ext. 1519
716.674.3696 fax
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
