If your organization uses Gold Client to copy Product objects within your CRM landscape, these enhancements may be relevant.
The 24 tables involved are listed below; see the screen captures and specific details below for deploying these enhancements within the Gold Client configuration.
Note: some of these tables may already exist within data type CRM - BUSINESS PARTNERS (CRMM) and if that's the case, you should consider removing them since the tables don't need to exist within two different Client Construct data types.
BBPM_PRGENERAL
BBPM_PRGENERALH
CRMM_PRREFOBJ
CRMM_PRREFOBJH
CRMM_PRSALESH
CRMM_PRWTY
CRMM_PRWTYH
CRMM_PRWTY_CAT
CRMM_PRWTY_CATH
CRMM_PRWTY_CNT
CRMM_PRWTY_CNTH
CRMM_PRWTY_SRV
CRMM_PRWTY_SRVH
CRMM_PR_BTRH
CRMM_PR_SALESAH
CRMM_PR_SALESGH
CRMM_PR_SRVDUR
CRMM_PR_SRVDURH
CRMM_PR_SRVENT
CRMM_PR_SRVENTH
CRMM_PR_SRVRR
CRMM_PR_SRVRRH
CRMM_PR_SUCCESS
CRMM_PR_SUCCESSH

Add these tables (highlighted in the screen capture below) to Client Construct data type CRM - PRODUCT BASE

Name:  Capture13.PNG
Views: 78
Size:  114.1 KB
Name:  Capture14.PNG
Views: 65
Size:  37.6 KB
To add these same tables to the Data Echo framework, use the details and screen captures that follow.
Create a new data type named CRM - PRODUCT-SET ASSIGNMT(HIST) and add the relevant tables viewed here:

Name:  Capture15.PNG
Views: 75
Size:  162.6 KB

All table relations within this data type should use common fields FRG_GUID = FRAGMENT_GUID and VALID_TO = VALID_TO (re: screen capture on left), except for the header table which should use the same fields and PRODUCT_GUID = PRODUCT_GUID (re: screen capture on right)

Name:  Capture16.PNG
Views: 63
Size:  48.5 KB

Add a link to this new data type CRM - PRODUCTS (and from any other Product-related data types that may exist within the Data Echo framework)

Name:  Capture17.PNG
Views: 80
Size:  159.1 KB

Create a new data type named CRM - PROD SALES-SET ASSGN(HIST) and add the relevant tables viewed here:

Name:  Capture18.PNG
Views: 70
Size:  89.8 KB

All table relations within this data type should use common fields FRG_GUID = FRAGMENT_GUID and VALID_TO = VALID_TO (re: screen capture on left), except for the header table which should use common fields DISTR_CHAN, FRAGMENT_TYPE, PRODUCT_GUID, SALES_ORG, and VALID_TO (re: screen capture on right)

Name:  Capture19.PNG
Views: 59
Size:  56.1 KB

Add a link to this new data type CRM - PRODUCTS (and from any other Product-related data types that may exist within the Data Echo framework)

Name:  Capture20.PNG
Views: 66
Size:  122.5 KB

Add the selected tables below to existing data type CRM - PRODUCT-SET ASSIGNMENT

Name:  Capture21.PNG
Views: 60
Size:  143.4 KB

All table relations added to this data type should use common fields FRG_GUID = FRAGMENT_GUID (re: screen capture below)

Name:  Capture22.PNG
Views: 64
Size:  16.1 KB

Be sure that data type CRM - PRODUCT-SET ASSIGNMENT is linked from CRM - PRODUCTS (and from any other Product-related data types that may exist within the Data Echo framework)

Name:  Capture23.PNG
Views: 86
Size:  143.5 KB

Add the selected tables below to existing data type CRM - PRODUCTS (and from any other Product-related data types that may exist within the Data Echo framework)

Name:  Capture24.PNG
Views: 62
Size:  111.0 KB

All table relations added to this data type should use common fields PRODUCT_GUID = PRODUCT_GUID (re: screen capture below)

Name:  Capture25.PNG
Views: 60
Size:  18.0 KB