If your organization creates Billing Plans in relation to sales orders and/or other SD data objects, this config change is relevant to you... The Gold Client team has performed some analysis and determined that SD exports may run more efficiently if the Billing Plan tables (FPLA, FPLT, FPLTC) are removed from being part of the SD data types (e.g. SD - SALES DOCUMENTS) and added to their own data type instead, and then added as a data type link. The potential efficiency gain comes from passing objects among the various tables using only key fields versus non-key fields. Breaking out the Billing Plan tables into their own data type also provides users the flexibility to copy these objects independently when needed.
If you are interested in following our lead by deploying these same changes to your organization's Gold Client config, follow the steps below.

1. Go to ZGOLD > Configuration > Framework > Data Echo
2. Create a new data type named SD - BILLING PLANS using the details in the following screen capture.
[I]Note that all three table relations must have common fields added and that they need to use FPLNR-FPLNR.


Name:  Capture16.PNG
Views: 427
Size:  79.7 KB

3. Create a new data type named LINK - SD OBJECT TO BILLING PLAN using the details in the following screen capture.

Name:  Capture17.PNG
Views: 88
Size:  79.8 KB

4. Create a data type link from LINK - SD OBJECT TO BILLING PLAN to SD - BILLING PLANS using the details in the following screen capture.

Name:  Capture18.PNG
Views: 90
Size:  91.3 KB

5. Create a data type link from SD - SALES DOCUMENTS to LINK - SD OBJECT TO BILLING PLAN using the details in the following screen capture.

Name:  Capture19.PNG
Views: 110
Size:  113.0 KB

Important! We have received feedback from some customers that using the VBKD table as the relation between the sales order and billing plan does not always lead to positive results and therefore you may want to consider adding a link from SD - SALES DOCUMENTS to SD - BILLING PLANS instead using the details in the screen capture below. This link uses the logic where the value stored in VBAK.RPLNR is passed to FPLA.FPLNR.
Since there are multiple ways to connect these two data objects, it may be best to consult with your SD team and/or query your organization's database to determine the ideal relation. Of course you could setup both linkages (1) SD - SALES DOCUMENTS to SD - BILLING PLANS and (2) SD - SALES DOCUMENTS to LINK - SD OBJECT TO BILLING PLAN to SD - BILLING PLANS, to try and ensure that the Billing Plan is copied using either method. Using both linkages adds overhead but it should be minimal.
Attunity has updated our "golden" config to use both the direct and indirect linkages so that customers have the flexibility of using one or the other or both as needed.

Name:  Capture20.PNG
Views: 105
Size:  94.4 KB

6. Delete table relations FPLA-VBAK, FPLT-FPLA, and FPLTC-FPLA as highlighted in the following screen capture. These are no longer needed since a data type has been created. If this step is not performed then it's likely that this data would be copied redundantly.

Name:  Capture21.PNG
Views: 124
Size:  98.4 KB

7. Repeat steps 5 and 6 as needed for other SD data types that exist within your Gold Client configuration. Possible candidates could be:
SD - CONTRACTS
SD - SALES DOCS TO CREDIT MEMO
SD - SALES DOCS TO DEBIT MEMO
SD - SALES DOCS TO RETURNS
SD - SALES DOCUMENTS FROM PO.