Line Order No doesnt match with Invoice line number

Question

At the line level , the line order no doesnt match with the invocie line number
ie. say for example in a sales order we have 3 lines
1. A
2. B
3. C
where as in transaction at AR level the line no is different
1. B
2. A
3. C
the customer wants in AR also the line no should be same as sales order line nos
Please help us what is the setup where we define the line level numbering in AR.
I have checked the line ordering rules but i am not clearly understanding, if anyone can explain with an example how this no generates witht he setup details it would be great

Answer 1

This can be done in XSL OR in procedure on the DB side. Performance wise better to do in procedure as mentioned by other use. You can choose to go with DB or XSL approach depending on number of orders you are expecting in a single message. If it is going to be 100s or few thousand messages then keeping it in XSL is not a problem. But if you are planning tens or hundreds of thousands of orders in the same request then better do it in stored procedure.
How do you do in XSL?
1. Put a for each on every unique order no. You can use xsl:Key or xslt:distinct-values() for this.
2. Within for each unique value of order no, use position() function to pass line/order no as 1,2,3... etc. As soon as the loop moves to second iteration for the next unique order no, count will automatically start again from 1,2,3... and so on.
Apart from slightly slower processing time, another drawback from this approach is that the data in the XML you send to DB procedure will be sorted by order numbers. All orders with same number will appear together.
Another problem with this approach is that this will work only within one request, i.e. if the next request contains an order with same no which was already sent in a previous request, for this order the count will again start from 1. So if you want to keep the sequencing maintained across multiple requests, the easiest way to do is in the DB procedure where you can lookup in the table before inserting a new row and insert with next sequence of that order no.