Quantcast
Channel: Attunity Integration Technology Forum
Viewing all articles
Browse latest Browse all 411

New data type for Cost Collector orders

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

Name:  Capture28.PNG
Views: 1
Size:  80.1 KB

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

Name:  Capture29.PNG
Views: 1
Size:  26.3 KB

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.

Name:  Capture30.PNG
Views: 1
Size:  131.1 KB

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.

Name:  Capture31.PNG
Views: 1
Size:  103.1 KB
Name:  Capture32.PNG
Views: 1
Size:  116.3 KB
Name:  Capture33.PNG
Views: 1
Size:  126.7 KB
Name:  Capture34.PNG
Views: 1
Size:  127.8 KB
Name:  Capture35.PNG
Views: 1
Size:  129.4 KB
Name:  Capture36.PNG
Views: 1
Size:  130.2 KB
Name:  Capture37.PNG
Views: 1
Size:  115.5 KB
Name:  Capture38.PNG
Views: 1
Size:  140.9 KB
Name:  Capture39.PNG
Views: 1
Size:  26.5 KB
Attached Images
            

Viewing all articles
Browse latest Browse all 411

Trending Articles