Product-relevant tables newly added

October 25, 2017, 3:38 am

≫ Next: New tables added to SRM intelligent data type CA - BUSINESS PARTNERS

≪ Previous: Add ISU tables to the Data Echo and Client Construct frameworks

$

0

0

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



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:



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)



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)



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



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)



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)



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



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



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)



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)



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

Attached Images

             

---

New tables added to SRM intelligent data type CA - BUSINESS PARTNERS

October 25, 2017, 4:00 am

≫ Next: Enhancements for data type CA - DOCUMENT MANAGEMENT

≪ Previous: Product-relevant tables newly added

$

0

0

The standard configuration for the SRM Gold Client product has been enhanced to include tables BBPM_BUT_FRG0010, BBPM_BUT_FRG0020, BBPM_BUT_FRG0030, BBPM_BUT_FRG0060, and BBP_SUPP_MONI. If your organization has data in these tables and wants the ability to copy this data using Gold Client, follow the instructions below.

1. In the source system – typically Production – go to t-code ZGOLD and open the Data Framework function
2. Select data type CA - BUSINESS PARTNERS and choose the underlying maintenance view named ‘Tables’



3. Add a new entry where the table is BBPM_BUT_FRG0010 and the source table is BUT000 and the common field relation between the tables is PARTNER_GUID - PARTNER_GUID as seen in the screen capture below



4. Add another entry where the table is BBPM_BUT_FRG0020 and the source table is BUT000 and the common field relation between the tables is PARTNER_GUID - PARTNER_GUID as seen in the screen capture below



5. Add another entry where the table is BBPM_BUT_FRG0030 and the source table is BUT000 and the common field relation between the tables is PARTNER_GUID - PARTNER_GUID as seen in the screen capture below



6. Add another entry where the table is BBPM_BUT_FRG0060 and the source table is BUT000 and the common field relation between the tables is PARTNER_GUID - PARTNER_GUID as seen in the screen capture below



7. Lastly, add another entry where the table is BBP_SUPP_MONI and the source table is BUT000 and the common field relation between the tables is PARTNER_ID - PARTNER as seen in the screen capture below



8. Save your changes and exit the Data Framework

If some or all of these tables are missing from Refresh Alternative data type SRM - BUSINESS PARTNERS, you may wish to add them. To do so, follow the instructions below.
A. In the source system – typically Production – go to t-code ZGOLD and open the Table Framework function
B. Select data type SRM - BUSINESS PARTNERS and then open the Master Data Tables folder



C. Click on 'New Entries' located on the toolbar and add the tables as needed
D. Save your changes and exit the Table Framework

Attached Images

       

Enhancements for data type CA - DOCUMENT MANAGEMENT

October 25, 2017, 4:44 am

≫ Next: Adding Configuration for Object Status and Costing off of Order Line Items (AFPO)

≪ Previous: New tables added to SRM intelligent data type CA - BUSINESS PARTNERS

$

0

0

If your organization uses the Document Management System (DMS), the following configuration enhancements may be relevant. These enhancements will allow Gold Client to copy the following objects in relation to a given Document: Change Docs, Document Authorizations, Engineering Changes, and links to the file attachment.

Use the steps below to deploy the relevant changes to your system to mimic the enhancements that have been applied to our standard configuration. Note: these details are organized and separated by enhancement in this sequence: Change Docs, Authorizations, Engineering Changes, and links to files.

Step 0: In your primary Source client (typically Production) go to ZGOLD > Configuration > Framework > Data Echo

CHANGE DOCUMENTS

Step 1: Open data type CA - DOCUMENT MANAGEMENT and select the 'Linkages' maintenance view

Step 2: Add a link to data type CA - CHANGE DOCUMENTS using the details in the screen capture below. Note that the second row of the linkage details uses an asterisk in the 'Prv Field' column which informs Gold Client that concatenation is being used and so be sure to apply the concatenation details as well (DOKAR+DOKNR).



DOCUMENT AUTHORIZATIONS

Step 1: Create a new data type named CA - DOC MGMT AUTHORIZATIONS using the details in the screen capture below; note: the FILE ID value is CADMAU



Step 2: Open this new data type and select the 'Tables' maintenance view

Step 3: Add to data type CA - DOC MGMT AUTHORIZATIONS the table relations in the screen capture below; be sure to set table DMS_GUID as the header



Step 4: For each table relation, add the respective field joins (common fields) listed below

Tip: Add the common fields for the header table (DMS_GUID) first



Step 5: Open data type CA - DOCUMENT MANAGEMENT and select the 'Linkages' maintenance view

Step 6: Add a link to data type CA - DOC MGMT AUTHORIZATIONS using the details in the screen capture below



ENGINEERING CHANGES

Step 1: Open data type CA - DOCUMENT MANAGEMENT and select the 'Linkages' maintenance view

Step 2: Add a link to data type CA - ENGINEERING CHANGE MGMT using the details in the screen capture below. Note that the second row of the linkage details uses an asterisk in the 'Prv Field' column which informs Gold Client that concatenation is being used and so be sure to apply the concatenation details as well (DOKAR+DOKNR).



LINKS to FILE ATTACHMENTS

Step 1: Create a new data type named CA - DOC MGMT LOGISTICAL FILES using the details in the screen capture below; note: the FILE ID value is CADMLO



Step 2: Open this new data type and select the 'Tables' maintenance view

Step 3: Add to data type CA - DOC MGMT LOGISTICAL FILES the table relations in the screen capture below; be sure to set table DMS_DOC2LOIO as the header



Step 4: For each table relation, add the respective field joins (common fields) listed below



Step 5: Create a new data type named CA - DOC MGMT PHYSICAL FILES using the details in the screen capture below; note: the FILE ID value is CADMPH



Step 6: Open this new data type and select the 'Tables' maintenance view

Step 7: Add to data type CA - DOC MGMT PHYSICAL FILES the table relations in the screen capture below; be sure to set table DMS_PH_CD1 as the header



Step 8: For each table relation, add the respective field joins (common fields) listed below

Tip: Add the common fields for the header table (DMS_PH_CD1) first



Step 9: Create a new data type named CA - DOCUMENT MGMT CONTENTS using the details in the screen capture below; note: the FILE ID value is CADMSC



Step 10: Open this new data type and select the 'Tables' maintenance view

Step 11: Add to data type CA - DOCUMENT MGMT CONTENTS the lone table relation and common fields in the screen capture below



Step 12: Open data type CA - DOCUMENT MANAGEMENT and select the 'Linkages' maintenance view

Step 13: Add a link to data type CA - DOC MGMT LOGISTICAL FILES using the details in the screen capture below



Step 14: Open data type CA - DOC MGMT LOGISTICAL FILES and select the 'Linkages' maintenance view

Step 15: Add a link to data type CA - DOC MGMT PHYSICAL FILES using the details in the screen capture below



Step 16: Open data type CA - DOC MGMT PHYSICAL FILES and select the 'Linkages' maintenance view

Step 17: Add a link to data type CA - DOCUMENT MGMT CONTENTS using the details in the screen capture below



Changes complete; exit the Data Echo framework.

Attached Images

                 

Adding Configuration for Object Status and Costing off of Order Line Items (AFPO)

October 25, 2017, 6:05 am

≫ Next: New Configuration for Dispute Management Cases

≪ Previous: Enhancements for data type CA - DOCUMENT MANAGEMENT

$

0

0

If your organization has object status and costing on Orders (table AFPO for Production Orders, Work Orders, Cost Collectors and Network Orders), then this change may be relevant. Our Gold Client "golden" configuration has been enhanced so that the Object Status and Costing related to the above line items on orders can be exported. If you want to deploy these enhancements in your system's Gold Client Configuration, follow the instructions listed below.

Step 1: In your primary Source client (typically Production) go to ZGOLD --> Configuration --> Framework --> Data Echo
Step 2: Create a new data type named LINK - ORDER TO LINE ITEMS
Note: The recommended File ID is AFPOLI



Step 3: Locate the new data type at the end of the Data Type list. Open this new data type and select the Tables maintenance view.
Step 4: Add table relation AFPO-AFPO and common fields



Step 5: Within this same data type, select the Linkages maintenance view

Step 6: Add a link to data type CA - OBJECT STATUS using these linkage details



Step 7: Add a link to data type CO - COSTING (COES) using these linkage details



Step 8: Add a link to data type CO - COSTING (COFP) using these linkage details



Step 9: Add a link to data type CO - COSTING (COKA) using these linkage details



Step 10: Add a link to data type CO - COSTING (COKP) using these linkage details



Step 11: Add a link to data type CO - COSTING (COKR) using these linkage details



Step 12: Add a link to data type CO - COSTING (COKS) using these linkage details



Step 13: Add a link to data type CO - COSTING (COSB) using these linkage details



Step 14: Add a link to data type CO - COSTING (COSBD) using these linkage details



Step 15: Add a link to data type CO - COSTING (COSL) using these linkage details



Step 16: Add a link to data type CO - COSTING (COSLD) using these linkage details



Step 17: Add a link to data type CO - COSTING (COSP) using these linkage details



Step 18: Add a link to data type CO - COSTING (COSPD) using these linkage details



Step 19: Add a link to data type CO - COSTING (COSPP) using these linkage details



Step 20: Add a link to data type CO - COSTING (COSPR) using these linkage details



Step 21: Add a link to data type CO - COSTING (COSR) using these linkage details



Step 22: Add a link to data type CO - COSTING (COSS) using these linkage details



Step 23: Add a link to data type CO - COSTING (COSSD) using these linkage details



Step 24: Add a link to data type CO - COSTING (COSSP) using these linkage details



Step 25: Open data type CO - COST COLLECTOR ORDERS and select the Linkages maintenance view

Step 26: Add a link to LINK - ORDER TO LINE ITEMS using these linkage details



Step 27: Open data type PM - WORK ORDERS and select the Linkages maintenance view

Step 28: Add a link to LINK - ORDER TO LINE ITEMS using these linkage details



Step 29: Open data type PM - WORK ORDERS FROM PO and select the Linkages maintenance view

Step 30: Add a link to LINK - ORDER TO LINE ITEMS using these linkage details



Step 31: Open data type PP - ORDER MASTERS and select the Linkages maintenance view

Step 32: Add a link to LINK - ORDER TO LINE ITEMS using these linkage details



Step 33: Open data type PP - PRODUCTION ORDERS and select the Linkages maintenance view

Step 34: Add a link to LINK - ORDER TO LINE ITEMS using these linkage details



Step 35: Open data type PS - NETWORK ORDERS and select the Linkages maintenance view

Step 36: Add a link to LINK - ORDER TO LINE ITEMS using these linkage details



Save all changes as you work through these steps and then exit the framework when done.

Attached Images

                           

New Configuration for Dispute Management Cases

October 25, 2017, 7:18 am

≫ Next: Enhancements to data type CA - INVESTMENT PROGRAMS

≪ Previous: Adding Configuration for Object Status and Costing off of Order Line Items (AFPO)

$

0

0

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

• 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.

Attached Images

                 

Enhancements to data type CA - INVESTMENT PROGRAMS

October 31, 2017, 2:16 am

≫ Next: New configuration for Agency Business (LO-AB) module

≪ Previous: New Configuration for Dispute Management Cases

$

0

0

If your organization creates Investment Programs and needs to copy this data using Gold Client, you may want to check your existing configuration against our standard as we have enhanced this data type from time to time. If you wish to align this data type in your config with our current standard, follow the steps below.

Step 1: In your primary Source client (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Open data type CA - INVESTMENT PROGRAMS and select the 'Tables' maintenance view
Step 3: Add any of the table relations from the screen capture below that are missing in your system, and be sure to add the common fields for each. Additionally, consider removing any tables that are not in this screen capture.

If you are concerned about removing tables to align with our config, freely submit a support ticket so that we can discuss specifics with you.



Step 4: Open data type CA - INVESTMENT PROGRAMS and select the 'Tables' maintenance view (create this data type if it does not yet exist using the details below)
Data Type: CA - INVESTMENT PROGRAMS
Datatype Kind: T (transactional)
File ID: CAIMPR
Data Snap Rec Limit: 1000

Step 5: Add any of the table relations from the screen capture below that are missing in your system, and be sure to add the common fields for each. Additionally, consider removing any tables that are not in this screen capture.




Step 6: Open data type CA - INVESTMENT PROGRAMS and select the 'Linkages' maintenance view
Step 7: Add a data type link from CA - INVESTMENT PROGRAMS to CA - INVESTMENT PROG POSITIONS using the details in this screen capture



Step 8: Optionally, add a data type link from CA - INVESTMENT PROG POSITIONS to CA - CHANGE DOCUMENTS using the details in the screen capture below



Step 9: Optionally, add a data type link from CA - INVESTMENT PROG POSITIONS to FI - BUDGETING HIERARCHY using the details in the screen capture below
Note that an asterisk (*) exists in the Prv Field column which means that concatenation is being used. Double-click this row to open the last sub-screen and to input the necessary values.

Attached Images

      

New configuration for Agency Business (LO-AB) module

October 31, 2017, 3:41 am

≫ Next: Optimizing configuration for Payroll Clusters PCL2 and PCL4

≪ Previous: Enhancements to data type CA - INVESTMENT PROGRAMS

$

0

0

If your organization is using the Agency Business module and has the need to copy data in this space, our standard configuration was recently enhanced with the integration of data types that support this module. To deploy these changes within your own system, follow the steps detailed below. If you require support deploying these config changes, submit a ticket and our team will connect and provide assistance.

(1) In your Source system (typically Production), go to ZGOLD > Configuration > Framework > Data Echo

(2) Create the following (8) new data types using the comments and screen captures listed below



All four table relations within AB - AGENCY BUSINESS DOCUMENTS use the same common field of just WBELN-WBELN




All four table relations within AB - REMUNERATION LISTS use the same common field of just WBELN-WBELN





All four table relations within AB - SETTLEMENT DOCUMENTS use the same common field of just WBELN-WBELN



(3) Create the following data type linkages using the comments and screen captures listed below
7 links from AB - AGENCY BUSINESS DOCUMENTS

Attached Images

             

Optimizing configuration for Payroll Clusters PCL2 and PCL4

October 31, 2017, 3:54 am

≫ Next: New data type for Cost Collector orders

≪ Previous: New configuration for Agency Business (LO-AB) module

$

0

0

If your organization uses Gold Client to copy HR Payroll Cluster data - specifically tables PCL2 and PCL4 - then the enhancements we have recently deployed to our standard are relevant to you. The benefit of making these changes is that it should provide improved efficiency when exporting data from these tables. There are too many variables (data volumes, types of hardware, network activity) for our team to suggest how much efficiency could be gained by deploying these changes but the potential could be significant.
The config changes being performed here are primarily a segregation of the linkage details that exist from data type HR - EMP MAST WITH PAY POSTING to HR - PAYROLL CLUSTER (PCL4) and from HR - PAYROLL DIRECTORY to HR - PAYROLL CLUSTER (PCL2). Separating the logic into distinct database calls should lead to a degree of improved efficiency. To make these same changes in your system, follow the steps below.

Step 1: In your primary Source client (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Select data type HR - PAYROLL CLUSTER (PCL4) and select the 'Copy' function located on the toolbar; name the new data type HR - PAYROLL CLUSTER (PCL4 - F1) and set the File ID as HPC4F1


Step 3: Repeat step 2 five more times naming the new data types and File IDs as follows:
(Note: If your organization has no interest in copying some of these (RELID) types of data that are stored in PCL4, then they can be skipped. Your HR experts should be able to provide necessary insight. A more ideal solution might be to deploy these changes and then set any links that are not needed to be inactive.)
HR - PAYROLL CLUSTER (PCL4 - F2) HPC4F2
HR - PAYROLL CLUSTER (PCL4 - LA) HPC4LA
HR - PAYROLL CLUSTER (PCL4 - SA) HPC4SA
HR - PAYROLL CLUSTER (PCL4 - ST) HPC4ST
HR - PAYROLL CLUSTER (PCL4 - U1) HPC4U1

Step 4: Open data type HR - EMP MAST WITH PAY POSTING and select 'Linkages'
Step 5: Add these six new data types as links from HR - EMP MAST WITH PAY POSTING using the details displayed in the following screen captures




Please note the asterisk (*) in the following screen capture which indicates that concatenation is being used; in this case the concatenation that should be added is a value of 'A' on the first line and a provider field of 'PERNR' on the second line. Add the details to your config exactly as you see them in these screen captures so that positive results are received when exporting data.





Step 6: Remaining within data type HR - EMP MAST WITH PAY POSTING and 'Linkages', delete the link to data type HR - PAYROLL CLUSTER (PCL4) as it is no longer needed
Step 7: Select data type HR - PAYROLL CLUSTER (PCL2) and select the 'Copy' function located on the toolbar; name the new data type HR - PAYROLL CLUSTER (PCL2 - B2) and set the File ID as HPC2B2



Step 8: Open data type HR - PAYROLL DIRECTORY and select 'Linkages'
Step 9: Add a new data type link from HR - PAYROLL DIRECTORY to HR - PAYROLL CLUSTER (PCL2 - B2) using the details displayed in the following screen capture



Step 10: Remaining within data type HR - PAYROLL DIRECTORY and 'Linkages', select the link to data type HR - PAYROLL CLUSTER (PCL2)
Step 11: Remove the linkage detail where RELID = 'B2' and the line below it so that the remaining linkage details appear as they do in this screen capture



Step 12: Exit the Data Echo framework

Attached Images

         

---

New data type for Cost Collector orders

October 31, 2017, 4:03 am

≫ Next: New data types and other enhancements for Dangerous Goods and Hazardous Substances

≪ Previous: Optimizing configuration for Payroll Clusters PCL2 and PCL4

$

0

0

If your organization creates an order type known as 'Cost Collectors', then the configuration details outlined below may be relevant. Follow the steps to deploy this new data type within your team's respective Gold Client config.
Note: this topic updated on May 20, 2016 with three new linkage details and a correction for the link to CA - TEXT

Step 1: In your primary Source system (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Create a new data type named CO - COST COLLECTOR ORDERS and input these header details:

• Datatype Kind: M (master data)
• File ID: COCOLL
• Data Snap Rec Limit: 1000

Step 3: Open the new data type and select the 'Tables' view. Apply the 14 table relations as visible in the following screen capture.



Step 4: Apply the common fields for each table relation. There are only two sets of common fields used among these table relations: AUFNR-AUFNR or OBJNR-OBJNR as visible in the following screen capture examples..



The table relations below use AUFNR-AUFNR:

• AFBP AFKO
• AFKO AFKO
• AFPO AFKO
• AUFK AFKO
• CKMLMV013 AFKO

The table relations below use OBJNR-OBJNR:

• CHZP AUFK
  
• COBRA AUFK
• COBRB AUFK
• CPZP AUFK
• IHPA AUFK
• JEST AUFK
• JSTO AUFK
• ONR00 AUFK
• ONROR AUFK

Step 5: Within data type CO - COST COLLECTOR ORDERS, select the 'Linkages' view. Apply the 19 linkages as visible in the following screen capture.
Important note: Some Cost Collector orders could potentially have years and years of related Costing data. If your organization does not want to copy all Costing data in relation to these orders, set the respective data type links to be inactive (checkmark in the box means it is inactive). It is possible to customize the configuration to limit the amount of Costing data to be copied; if your team wants to pursue this option, submit a ticket on the HUB so that we can discuss specifics with you.



Step 6: Apply the linkage details for each Recipient data type as visible in the following screen capturesNote: A number of these linkage details requires the entry of an asterisk (*) in the 'Prv. Field' column which indicates that concatenation is being used. Double-click on this row to make visible the bottom sub-screen so that it is possible to input the concatenation details.

Attached Images

            

New data types and other enhancements for Dangerous Goods and Hazardous Substances

October 31, 2017, 4:14 am

≫ Next: New data types for (HR) Leave Requests

≪ Previous: New data type for Cost Collector orders

$

0

0

If your organization is using the Dangerous Goods Management and/or Hazardous Substances Management parts of the Environment, Health and Safety module, we have recently created new data types and enhanced some existing data types in this space. If you are interested in deploying these changes into your Gold Client configuration, follow the steps below.

Changes to the Client Construct framework
Step 1: In your Source system (typically Production), go to ZGOLD > Configuration > Framework > Client Construct
Step 2: Select data type EHS: DANGEROUS GOODS MANAGEMENT and then open the 'Master Data Tables' folder; then add tables:
DGTCPD
DGTEXCCHKMETH
DGTEXCCNTRIES
DGTEXCEPT
DGTEXCTEXTS
DGTEXCUNNO
If creating this data type for the first time, add the six tables above plus these eight tables:
CCDUTCARR, CCDUTDGREL, CCDUTPACK, CCDUTSPROV, CCDUTTRAPPR, DGTM2, DGTMD, DGTPK



Step 3: Create new data type EHS: HAZARDOUS SUBSTANCE MGMT and then open the 'Master Data Tables' folder; add tables:
HSMT_DN
HSMT_DT
HSMT_MD



Step 4: Select data type EHS: PRODUCT SAFETY and then open the 'Master Data Tables' folder; add tables:
CCGLT_AUDH
CCGLT_AUDI
CCGLT_AUDS
CCGLT_CLBL
If creating this data type for the first time, add the four tables above plus these 34 tables:
CCGLT_LSDE, CCGLT_LSHD, CCGLT_LSLT, CCGLT_LSRV, CCGLT_LSTG, CCGLT_MTLD, CCGLT_MTLS, CCGLT_MTLV, CVDDH, CVDDP, EST07,
EST0B, EST0D, EST0F, ESTDF, ESTDH, ESTDJ, ESTDO, ESTDR, ESTDS, ESTDU, ESTLP, ESTLR, ESTLS, ESTLS_COND, ESTLU, ESTLV, ESTMJ,
TGTPLH, TCGTPLHD, TCGTPLI, TCGTPLP, TCGTPLREL, TCGTPLU



Changes to the Data Echo framework
Phase 1: Align data types to match our updates
Step 1: In your Source system (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Select data type EHS - DANGEROUS GOODS MGMT and open the 'Tables' view
Step 3: Input the table relations and common fields visible in the following screen captures




Step 4: Select data type SD - SALES DOCUMENTS and open the 'Tables' view
Step 5: Add table relation VBEPDGAP - VBAK and then add common fields VBELN - VBELN as visible in the following screen capture
Repeat steps 4 and 5 for other Sales Order-related data types, for example, SD - CONTRACTS, SD - SALES DOCS TO CREDIT MEMO, SD - SALES DOCS TO DEBIT MEMO, SD - SALES DOCS TO DEBIT MEMO, SD - SALES DOCUMENTS FROM PO, and SD - SALES DOCUMENTS FROM PO



Step 6: Select data type SD - DELIVERIES and open the 'Tables' view
Step 7: Add table relation LIPSDGAP - LIKP and then add common fields VBELN - VBELN as visible in the following screen capture
Repeat steps 6 and 7 for other Delivery-related data types, for example, SD - DELIVERIES FROM PO, and SD - DELIVERIES TO ORDERS



Step 8: Select data type SD - CUSTOMER MASTER and open the 'Tables' view
Step 9: Add table relation CCGLT_CLBL - KNA1 and then add common fields KUNNR - KUNNR as visible in the following screen capture



Phase 2: Create new data types
Step 1: Create a new data type named EHS: HAZARDOUS SUBSTANCE MGMT and open the 'Tables' view
Step 2: Input the table relations and common fields visible in the following screen captures



Step 3: Create a new data type named EHS - DGM REGULATION EXCEPTIONS and open the 'Tables' view
Step 4: Input the table relations and common fields visible in the following screen captures



Step 5: Create a new data type named EHS - AUDIT DATA (LABEL MGMT) and open the 'Tables' view
Step 6: Input the table relations and common fields visible in the following screen captures



Phase 3: Create new data type links or change existing data type links
Step 1: Open data type EHS - DANGEROUS GOODS MGMT and select the 'Linkages' view
Step 2: Input data types EHS - DGM REGULATION EXCEPTIONS, EHS - SPEC-MATERIAL ASSIGNMENT, and MM - MATERIAL MASTER; be sure to include the linkage details as visible in the following screen captures



It's possible that your existing configuration may already some have data type linkages in place; with the previous step complete, these are no longer needed
Step 3: Open data type EHS - SPEC-MATERIAL ASSIGNMENT and select the 'Linkages' view; select data type MM - MATERIAL MASTER and delete it
Step 4: Open data type EHS - SPECIFICATION HEADER and select the 'Linkages' view; select data type EHS - SPEC-MATERIAL ASSIGNMENT and delete it

Attached Images

            

New data types for (HR) Leave Requests

October 31, 2017, 4:24 am

≫ Next: Enhancements to PS data types to collect related Costing data and Planned Orders

≪ Previous: New data types and other enhancements for Dangerous Goods and Hazardous Substances

$

0

0

If your organization creates Leave Requests (you can check by executing t-code PTARQ and the 'Display Documents' function, or simply by querying table PTREQ_HEADER), you may want to deploy the configuration enhancements outlined below which have been added to our baseline configuration.

Step 1: In your primary Source system (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Create three new data types named HR - LEAVE REQUEST ACTORS, HR - LEAVE REQUEST BY PERNR, and HR - LEAVE REQUESTS. Use the details in the screen captures below to add the relevant table relations and common fields.
Data types HR - LEAVE REQUEST ACTORS and HR - LEAVE REQUEST BY PERNR are identical to each other but this is done deliberately so that PERNRs can be used as the selection criteria for determining which Leave Requests to copy, and to help ensure that all of the various Actors/Roles associated to the Leave Requests are copied successfully.



For data type HR - LEAVE REQUESTS, use these details to add the common fields:

• For those table relations where PTREQ_ITEMS is the 'Source Table' (8 in all), the common fields should be ITEM_ID = ITEM_INS as seen in this screen capture

• For table relation PTARQ_DEDUCTION - PTREQ_HEADER, use REQUEST_ID = REQUEST_ID as seen in this screen capture

• For table relation PTREQ_HEADER - PTREQ_HEADER, use REQUEST_ID = REQUEST_ID and VERSION_NO = VERSION_NO as seen in this screen capture

• For table relation PTARQ_ITEMS - PTREQ_HEADER, use ITEM_LIST_ID = ITEM_LIST_ID as seen in this screen capture

Step 3: Create the following data type linkages between the newly created data types
HR - LEAVE REQUEST BY PERNR to HR - LEAVE REQUESTS



HR - LEAVE REQUESTS to CA - BUSINESS WORKFLOW



HR - LEAVE REQUESTS to HR - LEAVE REQUEST ACTORS

Attached Images

         

Enhancements to PS data types to collect related Costing data and Planned Orders

October 31, 2017, 4:36 am

≫ Next: Oracle Home Not Found

≪ Previous: New data types for (HR) Leave Requests

$

0

0

If your organization uses the PS (Project System) module then chances are the configuration changes documented below should be applied to your Gold Client configuration. The improvements made will help Gold Client exports include Settlement documents, Controlling documents, and Timesheets. We have also added the ability to include Planned Orders. See the instructions and screen captures below for deploying these same changes to your configuration that have been added to our standard.

UPDATE: this topic was updated as of April 20, 2016; the specific changes involved these two data type links: PP - OPERATIONS to LINK - OBJECT TO CONTROLLING DOC, and PS - WBS ELEMENTS to LINK - OBJECT TO CONTROLLING DOC. The reason for the change was to improve optimization when exporting data from these data types. The screen capture below shows that an index is readily available for table COEP which uses fields LEDNR and OBJNR. Our previous configuration only contained OBJNR but now includes LEDNR as well. See the relevant screen captures below to see how our config appears now.


Step 1: In your primary Source system (typically Prod), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Create the four new data types per the details in the screen captures below

• CO - LINE ITEMS FROM PS OBJECTS (this data type can be easily created by copying existing data type CO - LINE ITEMS)
• HR - TIMESHEET FROM PS OBJECTS
  
• LINK - OBJECT TO CONTROLLING DOC
• LINK - WBS TO PLANNED ORDERS

Step 3: Create the eight new data type links per the details in the screen captures below

• PP - OPERATIONS to CO - SETTLEMENT DOCUMENTS
• PS - NETWORK ORDERS to CO - SETTLEMENT DOCUMENTS; note that this link requires concatenation details
• PP - OPERATIONS to LINK - OBJECT TO CONTROLLING DOC
• PS - WBS ELEMENTS to LINK - OBJECT TO CONTROLLING DOC
• LINK - OBJECT TO CONTROLLING DOC to CO - LINE ITEMS FROM PS OBJECTS
• CO - LINE ITEMS FROM PS OBJECTS to HR - TIMESHEET FROM PS OBJECTS
• PS - WBS ELEMENTS to LINK - WBS TO PLANNED ORDERS
• LINK - WBS TO PLANNED ORDERS to PP - PLANNED ORDERS

This data type link has been enhanced by adding the row where COEP LEDNR = '00'


This data type link has been enhanced by adding the row where COEP LEDNR = '00'

Attached Images

          

Oracle Home Not Found

October 31, 2017, 6:28 am

≫ Next: Moving Billing Plan tables to their own data type

≪ Previous: Enhancements to PS data types to collect related Costing data and Planned Orders

$

0

0

Hello,

I am not sure if this is the correct forum but I have created a SSIS package connecting to an Oracle Source and I keep getting the error "Oracle Home Not Found". See attachment. I have both 32 and 64 Oracle Clients installed. Any feedback would be appreciated. Andy

Attached Images

 

Moving Billing Plan tables to their own data type

October 31, 2017, 6:44 am

≫ Next: New data type: PP - REPETITIVE MANUFACTURING

≪ Previous: Oracle Home Not Found

$

0

0

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.




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



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.



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.



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.



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.



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.

Attached Images

      

New data type: PP - REPETITIVE MANUFACTURING

October 31, 2017, 7:16 am

≫ Next: Add Linkages from CO - COST PLANNING to Other Costing Data Types

≪ Previous: Moving Billing Plan tables to their own data type

$

0

0

If your organization create Repetitive Manufacturing documents and would like to be able to use Gold Client to copy these data objects then apply the configuration changes outlined below.

1. Open the Data Echo framework (ZGOLD > Configuration > Framework > Data Echo)
2. Create new data type PP - REPETITIVE MANUFACTURING using the details visible below. Please note that the common fields for all table relations are the same in that they should used PRTNR-PRTNR.



3. Create new data type PP - REPETITIVE MANUFACTURNG ITM using the details visible below.



4. Add a data type link from PP - REPETITIVE MANUFACTURING to MM - MATERIAL MASTER using the details visible below.



5. Add a data type link from PP - REPETITIVE MANUFACTURING to PP - REPETITIVE MANUFACTURNG ITM using the details visible below.



6. Add a data type link from PP - REPETITIVE MANUFACTURNG ITM to MM - MATERIAL DOCUMENTS using the details visible below. Note: in our configuration we have inactivated this data type so that material documents are not included; if your organization requires this data in relation to Repetitive Manufacturing documents, leave this setting unchecked (thus making it active).



7. Add a data type link from PP - REPETITIVE MANUFACTURING to PP - REPETITIVE MANUFACTURNG ITM using the details visible below. Note: in our configuration we have inactivated this data type so that confirmation documents are not included; if your organization requires this data in relation to Repetitive Manufacturing documents, leave this setting unchecked (thus making it active).

Attached Images

      

---

Add Linkages from CO - COST PLANNING to Other Costing Data Types

October 31, 2017, 7:33 am

≫ Next: Optimizing data type FI - FINANCE DOCUMENTS

≪ Previous: New data type: PP - REPETITIVE MANUFACTURING

$

0

0

If you export data using data type CO - COST PLANNING, you may want to add downstream linkages to other CO* data types. There are ten costing tables that may have data in them related to header table ONRKL. Please see the linkage screenshots below & add them to your source system if desired. They can be added by going to ZGOLD - Configuration - Framework - Data Echo. Scroll to data type CO - COST PLANNING & open it. Double-click on Linkages.

Linkage to data type CO - COSTING (COKA)



Linkage to data type CO - COSTING (COKP)



Linkage to data type CO - COSTING (COSB)



Linkage to data type CO - COSTING (COSBD)



Linkage to data type CO - COSTING (COSL)



Linkage to data type CO - COSTING (COSLD)



Linkage to data type CO - COSTING (COSP)



Linkage to data type CO - COSTING (COSPD)



Linkage to data type CO - COSTING (COSS)



Linkage to data type CO - COSTING (COSSD)

Attached Images

          

Optimizing data type FI - FINANCE DOCUMENTS

October 31, 2017, 7:51 am

≫ Next: Various Business Partner tables have been added

≪ Previous: Add Linkages from CO - COST PLANNING to Other Costing Data Types

$

0

0

This forum topic was updated on March 24, 2015
To help optimize performance when exporting data via the FI - FINANCE DOCUMENTS data type, we recommend that customers deploy the various changes listed below. There are two sets of updates included here: (1) the table and field relations within FI - FINANCE DOCUMENTS itself, and (2) the links to recipient data types LINK - ACCT TO CLEARING DOC, LINK - FI DOC TO CUSTOMER MASTER, and LINK - FI TO OPERATING CONCERN.
Regarding the first set of updates, because this change simply involves replacing table BSEG with table BKPF as the source (parent), there is no risk to the data integrity when copying data (so as long as the directions in this forum are specifically followed). Additionally, we recommend removing table BKORM from FI - FINANCE DOCUMENTS and add it to its own data type; for step-by-step instructions for making this specific change, visit this forum topic:
https://hayes.zendesk.com/entries/24...ce-table-BKORM
Regarding the second set of updates, additional logic is being applied which means that the data being collected is more relevant and thus more optimal. The end result is that only those BSEG records which are relevant are being exported versus all BSEG records.
If you feel that support is needed to help make these changes, submit a support ticket and our team will respond accordingly.

Set 1: Update the table and field relations for FI - FINANCE DOCUMENTS
1. Within data type FI - FINANCE DOCUMENTS select the 'Tables' view


2. There will be a number of table relations in your config where the Source table is BSEG as is visible in the screen capture below (your system may not completely match these results). Several of these table relations (but not all) should be changed to BKPF.
The entries where BSEG is highlighted in yellow and bordered in blue are those records being changed; the entries where BSEG is highlighted in red should not be changed.



3. Below is a screen capture after having changed the respective BSEG values to BKPF; this screen capture represents our standard Gold Client config currently. The result is that a number of table relations that previously used BSEG as the Source table should now be BKPF.



4. After changing the Source table to be BKPF, it is absolutely vital that you apply common fields for each table relation that was changed; the common fields to use are: BELNR-BELNR, BUKRS-BUKRS, and GJAHR-GJAHR (as seen in the screen capture below)


5. Consider repeating steps 1-4 for other FI data types such as FI - CLEARING DOCUMENTS or any custom Finance data types unique to your configuration

Set 2: Update the recipient data types
1. Within data type FI - FINANCE DOCUMENTS select the 'Linkages' view. The linkages that should be updated are LINK - ACCT TO CLEARING DOC, LINK - FI DOC TO CUSTOMER MASTER, and LINK - FI TO OPERATING CONCERN.
Some of the links may be set as inactive within your Gold Client configuration and as such these are skipped during the export process; however it may be possible that they will be made active in the future and therefore would benefit from this update. In the end, the decision is yours to update only active links or all links.


2. Double-click the link to LINK - ACCT TO CLEARING DOC and add the new entry highlighted below (AND BSEG AUGBL not equal to ' ')


3. Double-click the link to LINK - FI DOC TO CUSTOMER MASTER and add the new entry highlighted below (AND BSEG KUNNR not equal to ' ')



4. Double-click the link to LINK - FI TO OPERATING CONCERN and add the new entry highlighted below (AND BSEG PAOBJNR not equal to ' ')


5. Consider repeating steps 1-4 for other FI data types such as FI - CLEARING DOCUMENTS or any custom Finance data types unique to your configuration

If your organization is using the HR module and creating Payroll data in your SAP system, then the change below is also relevant
6. Open data type HR - FI DOCUMENTS and select the 'Linkages' view; the linkage that should be updated is LINK - SETTLEMENTS (BSEG). Add a new line to the linkage details (as highlighted) consisting of AND BSEG PROJK NE ' '

Attached Images

         

Various Business Partner tables have been added

October 31, 2017, 7:59 am

≫ Next: Updates to data type FI - NOTA FISCAL DOCUMENTS

≪ Previous: Optimizing data type FI - FINANCE DOCUMENTS

$

0

0

If your organization stores any data in the list of Business Partner-related tables below, and you want to be able to copy this data via Gold Client, then deploy the configuration changes detailed in this forum topic.
BC001
BD001
CRMKUNNR
CRMPARNR
CRMLIFNR
CVI_CUST_CT_LINK
CVI_CUST_LINK
CVI_VEND_LINK

Changes to the Client Construct framework
Add tables CRMKUNNR and CRMPARNR to data type CUSTOMER MASTER



Add table CRMLIFNR to data type VENDOR MASTER



Add tables BC001, BD001, CVI_CUST_CT_LINK, CVI_CUST_LINK, and CVI_VEND_LINK to data type BUSINESS PARTNERS



Changes to the Data Echo frameworkAdd the table relation CRMKUNNR - KNA1 to data type SD - CUSTOMER MASTER, and be sure to add the common fields CUSTOME_NO - KUNNR



Add the table relation CRMPARNR - KNVK to data type SD - CUSTOMER MASTER, and be sure to add the common fields CONTACT_NO - PARNR



Add the table relation CRMLIFNR - LFA1 to data type CA - VENDOR MASTER, and be sure to add the common fields VENDOR_NO - LIFNR



Add table relations BC001 - BUT000 and BD001 - BUT000 to data type CA - BUSINESS PARTNERS, and be sure to add common fields PARTNER - PARTNER to each


Add the three table relations listed below to data type CA - BUSINESS PARTNERS, and be sure to add common fields PARTNER_GUID - PARTNER_GUID to each
CVI_CUST_CT_LINK - BUT000
CVI_CUST_LINK - BUT000
CVI_VEND_LINK - BUT000

Attached Images

        

Updates to data type FI - NOTA FISCAL DOCUMENTS

October 31, 2017, 8:11 am

≫ Next: Archived Redo Logs deletion

≪ Previous: Various Business Partner tables have been added

$

0

0

If your organization creates Nota Fiscal documents and has a need to be able to copy these objects using Gold Client, then deploy the changes outlined below.
Updated content (as of June 13, 2017) consists of: (A) newly added tables to data type FI - NOTA FISCAL DOCUMENTS, and (B) data types links so that Nota Fiscal documents can be included in the data copy in relation to MM Invoices, Material Docs, and SD Billing Docs.

Step 1: In your primary Source client (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Create a new data type using the details that follow
Note: If your configuration already contains a data type named FI - NOTA FISCAL DOCUMENTS, skip ahead to step 4
Data Type: FI - NOTA FISCAL DOCUMENTS
Datatype Kind: 'T' (transactional)
File ID: FINOTA
Data Snap Rec Limit: 1,000
Step 3: Locate the data type at the end of the list of data types
Step 4: Open the data type and select the 'Tables' maintenance view
Step 5: Add the table relations visible in the following screen capture



Step 6: Add common fields for each table relation; all table relations use common fields DOCNUM - DOCNUM (screen capture below-left) with the exception of J_1BNFSTX - J_1BNFLIN as it uses common fields DOCNUM - DOCNUM and ITMNUM - ITMNUM (screen capture below-right)



Step 7: Create a new data type using the details in this screen capture



Step 8: Locate the data type at the end of the list of data typesStep 9: Open the data type and select the 'Tables' maintenance view
Step 10: Add the table relation and common fields visible in the following screen capture



Step 11: Within this same data type select the 'Linkages' maintenance viewStep 12: Add a link to FI - NOTA FISCAL DOCUMENTS and then add the linkage details consisting of the following: J_1BNFDOC DOCNUM = DOCNUM


Step 13: Open data type MM - INVOICE RECEIPTS and select the 'Linkages' maintenance view
Step 14: Add a link to LINK - DOCUMENT TO NOTA FISCAL and then add the linkage details consisting of the following: J_1BNFLIN REFTYP = 'LI' AND J_1BNFLIN REFKEY = *. Using an asterisk on this line informs Gold Client that concatenation is used. Double-click this line and then input two rows consisting of BELNR and GJAHR. For this data to be copied successfully, ensure that your configuration matches identically the details in this screen capture.



Step 15: Open data type MM - MATERIAL DOCUMENTS and select the 'Linkages' maintenance viewStep 16: Add a link to LINK - DOCUMENT TO NOTA FISCAL and then add the linkage details consisting of the following: J_1BNFLIN REFTYP = 'MD' AND J_1BNFLIN REFKEY = *. Using an asterisk on this line informs Gold Client that concatenation is used. Double-click this line and then input two rows consisting of MBLNR and MJAHR. For this data to be copied successfully, ensure that your configuration matches identically the details in this screen capture.



Step 17: Open data type SD - BILLING DOCUMENTS and select the 'Linkages' maintenance viewStep 18: Add a link to LINK - DOCUMENT TO NOTA FISCAL and then add the linkage details consisting of the following: J_1BNFLIN REFTYP = 'BI' AND J_1BNFLIN REFKEY = VBELN.

Attached Images

        

Archived Redo Logs deletion

November 5, 2017, 8:01 pm

≫ Next: Kafka Support

≪ Previous: Updates to data type FI - NOTA FISCAL DOCUMENTS

$

0

0

We are on version 4.0.9.132. I have configured a data source to copy archived redo logs to a temporary folder, and for replicate to access the files from this folder.
Once I configured permissions correctly on the NFS mount point, it seems to be working OK.
However I am noticing that archived redo logs are not getting deleted from this temporary folder, even though I have checked this option in the datasource configuration.
Is there anything I have missed? Or are there any bugs in this area that we may need a fix for?