We have recently added configuration to the Data Echo framework to support the copying of Dispute Cases. If your organization creates these data objects and has a need to copy them using Gold Client, then the configuration details below will need to be applied to your respective systems.
Step 1: In your primary Source client (typically Production) go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Create the 8 new data types listed below per the details within each respective screen capture
Data Type: LINK - OBJECT TO DISPUTE CASE
![Name: Capture96.PNG
Views: 1
Size: 78.4 KB]()
Data Type: CA - CASE MANAGEMENT
Suggestion: Add table relation SCMG_T_CASE - SCMG_T_CASE and its common fields first since it is the Header table for this data type; save changes. Then add the other five table relations and their common fields.
![Name: Capture97.PNG
Views: 1
Size: 187.8 KB]()
![Name: Capture98.PNG
Views: 1
Size: 171.1 KB]()
![Name: Capture99.PNG
Views: 1
Size: 159.8 KB]()
Data Type: CA - CASE MANAGEMENT ATTRIBUTES
![Name: Capture100.PNG
Views: 1
Size: 87.8 KB]()
Data Type: CA - CASE MGMT: LIO ATTR VALUES
![Name: Capture101.PNG
Views: 1
Size: 92.2 KB]()
Data Type: CA - CASE MGMT: LIO INSTANCES
Suggestion: Add table relation SCMGRECL01 - SCMGRECL01 and its common fields first since it is the Header table for this data type; save changes. Then add the other table relation and its common fields.
![Name: Capture102.PNG
Views: 1
Size: 150.6 KB]()
Data Type: CA - CASE MGMT: PIO INSTANCES
Suggestion: Add table relation SCMGRECP01 - SCMGRECP01 and its common fields first since it is the Header table for this data type; save changes. Then add the other four table relations and their common fields.
![Name: Capture103.PNG
Views: 1
Size: 185.2 KB]()
![Name: Capture104.PNG
Views: 1
Size: 148.0 KB]()
![Name: Capture105.PNG
Views: 1
Size: 80.0 KB]()
Data Type: CA - CASE MGMT: DOCUMENT CONTENT
![Name: Capture106.PNG
Views: 1
Size: 87.3 KB]()
Data Type: FI - DISPUTE CASE ATTRIBUTES
![Name: Capture107.PNG
Views: 1
Size: 69.1 KB]()
Step 3: Now that the data types have been created, it is necessary to link them together so that they create the following hierarchy.
•LINK - OBJECT TO DISPUTE CASE
•CA - CASE MANAGEMENT
•CA - CASE MANAGEMENT ATTRIBUTES
•CA - CASE MGMT: LIO ATTR VALUES
•CA - CASE MGMT: LIO INSTANCES
•CA - CASE MGMT: PIO INSTANCES
•CA - CASE MGMT: DOCUMENT CONTENT
•FI - DISPUTE CASE ATTRIBUTES
![Name: Capture108.jpg
Views: 1
Size: 87.5 KB]()
![Name: Capture109.jpg
Views: 1
Size: 94.0 KB]()
![Name: Capture110.PNG
Views: 1
Size: 194.3 KB]()
![Name: Capture111.PNG
Views: 1
Size: 114.6 KB]()
Step 4: Create a copy of data type FI - FINANCE DOCUMENTS and name it something like FI - FINANCE DOCS W/ DISP CASES. Then add a link from this new data type to LINK - OBJECT TO DISPUTE CASE.
Attunity suggests applying this config to a copy of FI - FINANCE DOCUMENTS rather than from this data type itself for two reasons:
1.In most instances, including the dispute case as part of the data copy is probably not needed (more the exception than the rule) and so this is avoided by not creating the link from FI - FINANCE DOCUMENTS.
2.This additional configuration may cause some exports to fail due to an error that is referred to by SAP as 'maximum internal sessions reached' so this error is avoided by not creating the link from FI - FINANCE DOCUMENTS (however this issue is avoided altogether if your organization is running exports with the new export engine introduced in version 8.5)
Here is a screen capture showing the data type copy named FI - FINANCE DOCS W/ DISP CASES and the linkage details to LINK - OBJECT TO DISPUTE CASE. Notice that the 'Prv. Field' contains an asterisk. Double-click this row for the last sub-screen to appear and add the concatenation details accordingly.
![Name: Capture112.PNG
Views: 1
Size: 148.3 KB]()
Save changes one last time and freely exit the Data Echo framework.
Step 1: In your primary Source client (typically Production) go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Create the 8 new data types listed below per the details within each respective screen capture
- LINK - OBJECT TO DISPUTE CASE
- CA - CASE MANAGEMENT
- CA - CASE MANAGEMENT ATTRIBUTES
- CA - CASE MGMT: LIO ATTR VALUES
- CA - CASE MGMT: LIO INSTANCES
- CA - CASE MGMT: PIO INSTANCES
- CA - CASE MGMT: DOCUMENT CONTENT
- FI - DISPUTE CASE ATTRIBUTES
Data Type: LINK - OBJECT TO DISPUTE CASE

Data Type: CA - CASE MANAGEMENT
Suggestion: Add table relation SCMG_T_CASE - SCMG_T_CASE and its common fields first since it is the Header table for this data type; save changes. Then add the other five table relations and their common fields.



Data Type: CA - CASE MANAGEMENT ATTRIBUTES

Data Type: CA - CASE MGMT: LIO ATTR VALUES

Data Type: CA - CASE MGMT: LIO INSTANCES
Suggestion: Add table relation SCMGRECL01 - SCMGRECL01 and its common fields first since it is the Header table for this data type; save changes. Then add the other table relation and its common fields.

Data Type: CA - CASE MGMT: PIO INSTANCES
Suggestion: Add table relation SCMGRECP01 - SCMGRECP01 and its common fields first since it is the Header table for this data type; save changes. Then add the other four table relations and their common fields.



Data Type: CA - CASE MGMT: DOCUMENT CONTENT

Data Type: FI - DISPUTE CASE ATTRIBUTES

Step 3: Now that the data types have been created, it is necessary to link them together so that they create the following hierarchy.
•LINK - OBJECT TO DISPUTE CASE
•CA - CASE MANAGEMENT
•CA - CASE MANAGEMENT ATTRIBUTES
•CA - CASE MGMT: LIO ATTR VALUES
•CA - CASE MGMT: LIO INSTANCES
•CA - CASE MGMT: PIO INSTANCES
•CA - CASE MGMT: DOCUMENT CONTENT
•FI - DISPUTE CASE ATTRIBUTES




Step 4: Create a copy of data type FI - FINANCE DOCUMENTS and name it something like FI - FINANCE DOCS W/ DISP CASES. Then add a link from this new data type to LINK - OBJECT TO DISPUTE CASE.
Attunity suggests applying this config to a copy of FI - FINANCE DOCUMENTS rather than from this data type itself for two reasons:
1.In most instances, including the dispute case as part of the data copy is probably not needed (more the exception than the rule) and so this is avoided by not creating the link from FI - FINANCE DOCUMENTS.
2.This additional configuration may cause some exports to fail due to an error that is referred to by SAP as 'maximum internal sessions reached' so this error is avoided by not creating the link from FI - FINANCE DOCUMENTS (however this issue is avoided altogether if your organization is running exports with the new export engine introduced in version 8.5)
Here is a screen capture showing the data type copy named FI - FINANCE DOCS W/ DISP CASES and the linkage details to LINK - OBJECT TO DISPUTE CASE. Notice that the 'Prv. Field' contains an asterisk. Double-click this row for the last sub-screen to appear and add the concatenation details accordingly.

Save changes one last time and freely exit the Data Echo framework.