Difference between revisions of "MAS 90 or 200"

From DataSelf Knowledge Base
Jump to navigation Jump to search
(Created page with "{{#breadcrumb:Tips for specific data sources}} = MAS 90 or 200 = {{toc}} == AR Invoice History Header/Detail == === Kit line items === Import fields ExplodedKitItem. Add...")
 
(Import fields ExplodedKitItem (SQL Server?))
 
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
{{#breadcrumb:Tips for specific data sources}}
 
{{#breadcrumb:Tips for specific data sources}}
 
+
[[Category:MAS90]]    [[Category:MAS200]]  [[Category:MAS90/200]]
 
+
__NOTOC__
= MAS 90 or 200 =
 
 
 
{{toc}}
 
 
 
 
== AR Invoice History Header/Detail ==
 
== AR Invoice History Header/Detail ==
  
 
=== Kit line items ===
 
=== Kit line items ===
  
Import fields ExplodedKitItem. Add the following fields to ''F'' '''SalesLine''':
+
===== Import fields AR_InvoiceHistoryDetail.ExplodedKitItem =====
 +
Add the following fields to <tt> _F_SalesLine </tt>:
  
CASE WHEN ExplodedKitItem = ‘Y’ THEN ‘Kit’ WHEN ExplodedKitItem = ‘C’ THEN ‘Component’ ELSE ‘Regular Item’ END AS KitLineType
+
<tt> CASE WHEN ExplodedKitItem = ‘Y’ THEN ‘Kit’ WHEN ExplodedKitItem = ‘C’ THEN ‘Component’ ELSE ‘Regular Item’ END AS KitLineType </tt>
  
 
And use these values to make a Kit Line Type dimension (probably with default for As Sold records)
 
And use these values to make a Kit Line Type dimension (probably with default for As Sold records)
  
[[Image:https://dataselfsupport.com/attachments/69/KitItems.PNG|https://dataselfsupport.com/attachments/69/KitItems.PNG]]
+
https://dataselfsupport.com/attachments/69/KitItems.PNG
  
 
May want to change QtySold and/or AmtCostofSales for Components to zero, and/or make a ComponentsQtySold measure.
 
May want to change QtySold and/or AmtCostofSales for Components to zero, and/or make a ComponentsQtySold measure.
  
'''Sales Order Lines''':<br />Import both ExplodedKitItem and SaleskitLineKey.
+
===== Sales Order Lines =====
 +
Import both ExplodedKitItem and SaleskitLineKey.
  
CASE WHEN ExplodedKitItem = ‘Y’ THEN ‘Kit’ WHEN SalesKitLineKey &gt; ‘000000’ THEN ‘Component’ ELSE ‘Regular Item’ END
+
<tt> CASE WHEN ExplodedKitItem = ‘Y’ THEN ‘Kit’ WHEN SalesKitLineKey &gt; ‘000000’ THEN ‘Component’ ELSE ‘Regular Item’ END </tt>
  
 
== ver 4.5 in SQL ==
 
== ver 4.5 in SQL ==
  
 
SY0 table changes to a new location, and has all companies in one. So have to import once and make it static (or filter for each company).
 
SY0 table changes to a new location, and has all companies in one. So have to import once and make it static (or filter for each company).

Latest revision as of 22:59, 28 May 2015

AR Invoice History Header/Detail

Kit line items

Import fields AR_InvoiceHistoryDetail.ExplodedKitItem

Add the following fields to _F_SalesLine :

CASE WHEN ExplodedKitItem = ‘Y’ THEN ‘Kit’ WHEN ExplodedKitItem = ‘C’ THEN ‘Component’ ELSE ‘Regular Item’ END AS KitLineType

And use these values to make a Kit Line Type dimension (probably with default for As Sold records)

KitItems.PNG

May want to change QtySold and/or AmtCostofSales for Components to zero, and/or make a ComponentsQtySold measure.

Sales Order Lines

Import both ExplodedKitItem and SaleskitLineKey.

CASE WHEN ExplodedKitItem = ‘Y’ THEN ‘Kit’ WHEN SalesKitLineKey > ‘000000’ THEN ‘Component’ ELSE ‘Regular Item’ END

ver 4.5 in SQL

SY0 table changes to a new location, and has all companies in one. So have to import once and make it static (or filter for each company).