cancel
Showing results for 
Search instead for 
Did you mean: 

Print Layout Designer Questions

Former Member
0 Kudos

Hi all,

I know this isnt necessarily the proper place for this post, but I haven't been able to get an answer from the Partner Portal Forums.

First Question: Does ANYONE know what the "Next Segment" selection combo does for a database field?

Next question (more specific): I am trying to display a pick list grouped and sorted by sales order. When I attempt to include the sales order line information, I get double lines for each item in that sales order. Removing the sales order row lines resolves the issue, but I need to display specific item information for the sales order lines.

here is my dependancy chain (I am not using next segment as I dont know what it does):

1. Pick List Order Entry --> Sales order Document Number

2. Pick List Order Entry --> PickList Rows OrderID

this next dependancy causes duplicate lines

3. Pick List Order Entry --> Sales Order Rows Document Key

it doesnt matter if I link the Sales Order Rows Doc Key field with the pick list order entry or the sales order document number, the results are the same.

If anyone knows how I might get around this, please let me know.

TYI,

Anthony Mann

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Anthony,

This report is based on a query ?

When you try your query, do you get double lines too ? Have you already try the 'Distinct' operator in sql ?

Is there any difference between double lines that you can test in the layout to hide one ?

Former Member
0 Kudos

Quentin,

I figured out the problem after some detective work. In answer to your question, no it is not based on a query, It is a modification of the pick list print layout. I found that the joining information between the Sales Order, Sales Order Lines, and the Pick List Lines tables are a bit weird. So how it works is like this (for those that might come across this problem in the future):

PKL1 has a reference to RDR1 and ORDR

RDR1 has a Reference to ORDR

both references are used for the lines.

when joining the tables, on sales order lines and sales order, duplicates happen at the line references. I am not sure why, but I know they are there.

for example, PKL joins on two line items with line number 0 and 1, and RDR1 joins on tow line items with line number 0 and 1. The resulting records come out like this:

(Item Number 1) (pick reference line 0) (sales order ref line 1)

(Item Number 1) (pick reference line 0) (sales order ref line 0)

(Item Number 2) (pick reference line 1) (sales order ref line 1)

(Item Number 2) (pick reference line 1) (sales order ref line 0)

so the records are duplicated. I fixed this by testing against (pick line ref) == (sales line ref), and hide records (lines in the report) that are not equal.

It's a bit confusing, but it worked for me.

Anthony

Answers (0)