Add Table to EDIPckSl Report Data Definition

Yahoo Archive
1
Thanks for the update, Adam. I'm hoping to move to 407C over the next few weeks.


--- In vantage@yahoogroups.com, "adam.whipp" <adam.whipp@...> wrote:
>
> Nigel -- I just wanted to let you know that we are now on 407B, and this function now works. I linked in BOLHead and BOLDetail and they show up in the EDI flat file.
>
> --Adam
>
> --- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@> wrote:
> >
> > When using "outbound EDI" you *can't* add new tables to an RDD. That
> > is, you can create relationships but no data will be output for any
> > table that's not already included or linked.
> >
> > So, if the table you need is not already listed as a Linked table for
> > some other table (and BOLDetail doesn't seem to be), then you're out
> > of luck.
> >
> > We use BPMs to copy data from these missing tables into UD fields on
> > (for example) ShipHead or ShipDtl when the shipment is being created.
> >
> >
> > Nigel.
> >
> >
> > --- In vantage@yahoogroups.com, "adam.whipp" <adam.whipp@> wrote:
> > >
> > > We have duplicated the EDIPckSl RDD and called it 856. We need to
> > > include bill of lading info, so here is what we did: We have added
> > the
> > > BOLDetail table, and created the necessary relationship to join
> > > ShipHead to BOLDetail using the company, bolnum, and bolline
> > fields.
> > > When I print using "outbound EDI" report style, the XML file
> > contains
> > > the BOL Detail data like it should. However, the txt file
> > > that "outbound EDI" creates does not include any info from the
> > > BOLDetail table. Does anyone have any insight? I don't get how it
> > can
> > > be present in the XML but not in the txt file. Thanks for your
> > help!
> > >
> > > Adam
> > >
> >
>
2
We have duplicated the EDIPckSl RDD and called it 856. We need to
include bill of lading info, so here is what we did: We have added the
BOLDetail table, and created the necessary relationship to join
ShipHead to BOLDetail using the company, bolnum, and bolline fields.
When I print using "outbound EDI" report style, the XML file contains
the BOL Detail data like it should. However, the txt file
that "outbound EDI" creates does not include any info from the
BOLDetail table. Does anyone have any insight? I don't get how it can
be present in the XML but not in the txt file. Thanks for your help!

Adam
3
When using "outbound EDI" you *can't* add new tables to an RDD. That
is, you can create relationships but no data will be output for any
table that's not already included or linked.

So, if the table you need is not already listed as a Linked table for
some other table (and BOLDetail doesn't seem to be), then you're out
of luck.

We use BPMs to copy data from these missing tables into UD fields on
(for example) ShipHead or ShipDtl when the shipment is being created.


Nigel.


--- In vantage@yahoogroups.com, "adam.whipp" <adam.whipp@...> wrote:
>
> We have duplicated the EDIPckSl RDD and called it 856. We need to
> include bill of lading info, so here is what we did: We have added
the
> BOLDetail table, and created the necessary relationship to join
> ShipHead to BOLDetail using the company, bolnum, and bolline
fields.
> When I print using "outbound EDI" report style, the XML file
contains
> the BOL Detail data like it should. However, the txt file
> that "outbound EDI" creates does not include any info from the
> BOLDetail table. Does anyone have any insight? I don't get how it
can
> be present in the XML but not in the txt file. Thanks for your
help!
>
> Adam
>
4
Adam,



I have a similar situation and a call logged with Epicor. I am trying
to use the ShipMisc table - which is shown in the RDD already, but not
outputting any schema or data - but does show in the XML. I have a
response, but it addresses if you get a 0KB XML - not the case for
either of us...But, since I am only in test at this time, I may try the
steps - I already have a busy day ahead, so it might take till the end
of the day before I get back to this.



Karen S



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of adam.whipp
Sent: Wednesday, January 28, 2009 6:21 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Add Table to EDIPckSl Report Data Definition



We have duplicated the EDIPckSl RDD and called it 856. We need to
include bill of lading info, so here is what we did: We have added the
BOLDetail table, and created the necessary relationship to join
ShipHead to BOLDetail using the company, bolnum, and bolline fields.
When I print using "outbound EDI" report style, the XML file contains
the BOL Detail data like it should. However, the txt file
that "outbound EDI" creates does not include any info from the
BOLDetail table. Does anyone have any insight? I don't get how it can
be present in the XML but not in the txt file. Thanks for your help!

Adam





[Non-text portions of this message have been removed]
5
Nigel -- I just wanted to let you know that we are now on 407B, and this function now works. I linked in BOLHead and BOLDetail and they show up in the EDI flat file.

--Adam

--- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@...> wrote:
>
> When using "outbound EDI" you *can't* add new tables to an RDD. That
> is, you can create relationships but no data will be output for any
> table that's not already included or linked.
>
> So, if the table you need is not already listed as a Linked table for
> some other table (and BOLDetail doesn't seem to be), then you're out
> of luck.
>
> We use BPMs to copy data from these missing tables into UD fields on
> (for example) ShipHead or ShipDtl when the shipment is being created.
>
>
> Nigel.
>
>
> --- In vantage@yahoogroups.com, "adam.whipp" <adam.whipp@> wrote:
> >
> > We have duplicated the EDIPckSl RDD and called it 856. We need to
> > include bill of lading info, so here is what we did: We have added
> the
> > BOLDetail table, and created the necessary relationship to join
> > ShipHead to BOLDetail using the company, bolnum, and bolline
> fields.
> > When I print using "outbound EDI" report style, the XML file
> contains
> > the BOL Detail data like it should. However, the txt file
> > that "outbound EDI" creates does not include any info from the
> > BOLDetail table. Does anyone have any insight? I don't get how it
> can
> > be present in the XML but not in the txt file. Thanks for your
> help!
> >
> > Adam
> >
>
6
When did 407B drop?



~Charlie

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
adam.whipp
Sent: Wednesday, April 08, 2009 11:26 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Add Table to EDIPckSl Report Data Definition



Nigel -- I just wanted to let you know that we are now on 407B, and this
function now works. I linked in BOLHead and BOLDetail and they show up in
the EDI flat file.

--Adam

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com, "Nigel
Kerley" <nigel.kerley@...> wrote:
>
> When using "outbound EDI" you *can't* add new tables to an RDD. That
> is, you can create relationships but no data will be output for any
> table that's not already included or linked.
>
> So, if the table you need is not already listed as a Linked table for
> some other table (and BOLDetail doesn't seem to be), then you're out
> of luck.
>
> We use BPMs to copy data from these missing tables into UD fields on
> (for example) ShipHead or ShipDtl when the shipment is being created.
>
>
> Nigel.
>
>
> --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com,
"adam.whipp" <adam.whipp@> wrote:
> >
> > We have duplicated the EDIPckSl RDD and called it 856. We need to
> > include bill of lading info, so here is what we did: We have added
> the
> > BOLDetail table, and created the necessary relationship to join
> > ShipHead to BOLDetail using the company, bolnum, and bolline
> fields.
> > When I print using "outbound EDI" report style, the XML file
> contains
> > the BOL Detail data like it should. However, the txt file
> > that "outbound EDI" creates does not include any info from the
> > BOLDetail table. Does anyone have any insight? I don't get how it
> can
> > be present in the XML but not in the txt file. Thanks for your
> help!
> >
> > Adam
> >
>





[Non-text portions of this message have been removed]