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

New data type for Funds Management

$
0
0
If your organization uses Funds Management then you may be interested in deploying the configuration changes outlined below into your own system.

Step 1: In your primary Source system (typically Production), go to ZGOLD > Configuration > Framework > Client Construct
Step 2: Add a new data type named FUNDS MANAGEMENT MASTER DATA
Step 3: Add the list of tables found in the screen capture below; there is a total of 28 tables
This same list of tables has been added below for easy copying/pasting, but be aware that you can only paste as many entries into this table as there are rows which are visible in the GUI. You can either add more rows by increasing the size of the GUI session with which you are working, or perform multiple copy/paste functions to add all of the tables.

Name:  Capture65.PNG
Views: 1
Size:  93.8 KB

FM01S
FMACTPOS
FMBUDGETPD
FMBUDGETPDT
FMCI
FMCIT
FMFCTR
FMFCTRT
FMFINCODE
FMFINT
FMFREEPOS
FMFUNDBPD
FMFUSE
FMFUSET
FMFXPO
FMHICI
FMHIPG
FMHIPOS
FMHIPP
FMHISV
FMPG
FMPOSIT
FMPP
FMPPT
FMSTATUS
FMZUBSP
TBP2A
TBP2B
Attached Images
 

Tables added to data type PROFITABILITY ANALYSIS

$
0
0
If your organization uses CO-PA, this change may be relevant. We have updated our standard configuration by incorporating into Client Construct data type PROFITABILITY ANALYSIS another 28 tables. All of these tables begin with the name T22*. Since CO-PA can be uniquely constructed in each SAP system it is possible for your system to have more or less tables, or different tables altogether than what we have added. To easily deploy this change into your Gold Client configuration follow the steps below.


  1. Go to ZGOLD > Configuration > Framework > Client Construct
  2. Select the data type PROFITABILITY ANALYSIS and then open the sub-folder named 'Master Data Tables'
  3. Convert the screen from display mode into change mode and then select the 'Insert by Pattern' icon located on the toolbar
  4. In the child window that appears, input the value T22* into the Table Name field and then 'Execute'

The end result of the above process will be the inclusion of whatever T22* tables exist in your particular system; however be aware that only Application tables (Delivery Class 'A') are intentionally targeted via this process while leaving out tables with any other delivery class. Your result should look similar to the screen capture below.

Name:  Capture66.PNG
Views: 1
Size:  58.7 KB
Attached Images
 

Add Tables T401A & T401T (MRP Profiles) to Configuration

$
0
0
Tables T401A (Material: MRP profiles (definition)) & T401T (MRP Profile Descriptions)

If you use MRP profiles, you may want to add tables T401A & T401T to your Gold Client configuration. To confirm that your system uses them, in your source system, go to transaction SE16 or SE16N & execute for table T401A. Check to see if there are records in the table. Even though these table names begin with the letter 'T', they are assigned by SAP to delivery class 'A' which represents Application Data (master and transactional) so these tables would not be included in a copy of the SAP configuration.

If you want to add them, we need to modify both the Client Construct & Data Echo configuration:
Client Construct
1) Go to ZGOLD - Configuration - Framework - Client Construct.
2) Switch to change mode.
3) Scroll to data type MATERIAL MASTER & MRP. Click the box to the left of the name to highlight it & double-click on the Master Data Tables folder.
4) Click the New Entries button & add tables T401A & T401T. Save it.

Data Echo
1) Go to ZGOLD - Configuration - Framework - Data Echo.
2) Click Create. Enter the information below in the Create Datatype window & click Enter.

3) Scroll down to the bottom of the list to find the new data type. Click on it to open it. It will prompt you to save it.
4) Double-click on the Tables option. In the Tables window that is displayed on the right side of the screen, switch to change mode.
5) Click the Add button to add two rows as shown. T401A is the header table for the new data type.

6) Double-click on the first row. We need to configure common fields between the tables. In the fields window, add the following fields relationship manually or use the Common Fields button to select the fields for you. Save it.

Add Tables T441A & T441T (Forecast Profiles) to Configuration

$
0
0
Tables T441A (Forecast Profiles) & T441T (Texts for Material Forecasting Profiles)

If you use forecast profiles, you may want to add tables T441A & T441T to your Gold Client configuration. To confirm that your system uses them, in your source system, go to transaction SE16 or SE16N & execute for table T441A. Check to see if there are records in the table. Even though these table names begin with the letter 'T', they are assigned by SAP to delivery class 'A' which represents Application Data (master and transactional) so these tables would not be included in a copy of the SAP configuration.

If you want to add them, we need to modify both the Client Construct & Data Echo configuration:
Client Construct
1) Go to ZGOLD - Configuration - Framework - Client Construct.
2) Switch to change mode.
3) Scroll to data type MATERIAL MASTER & MRP. Click the box to the left of the name to highlight it and double-click on the Master Data Tables folder.
4) Click the New Entries button & add tables T441A & T441T. Save it.

Name:  Capture67.PNG
Views: 1
Size:  53.8 KB


Data Echo
1) Go to ZGOLD - Configuration - Framework - Data Echo.
2) Create a new data type using the information below.
Data Type: MM - FORECAST PROFILE
Datatype Kind: 'M' (master data)
File ID: MMFRPR
Data Snap Rec Limit: 1,000

3) Scroll down to the bottom of the list to find the new data type. Click on it to open it. It will prompt you to save it.
4) Double-click on the Tables option. In the Tables window that is displayed on the right side of the screen, switch to change mode.
5) Click the Add button to add two the two table relations as shown in the screen capture below. T441A is the header table for the new data type.

Name:  Capture68.PNG
Views: 1
Size:  74.1 KB

6) Add the common fields for each table relation; the fields for T441A-T441A is visible in the screen capture above while the fields for T441T-T441A are below.

Name:  Capture69.PNG
Views: 1
Size:  8.5 KB

7) Save changes one last time and exit the framework
Attached Images
   

Config changes for including Material Ledger (CKML) data

$
0
0
If your organization uses Material Ledger functionality in SAP, then this forum topic may be relevant to you; if unsure about this, query table CKMLHD to see if data exists, or ask your FI team about it.
The Attunity team has updated their standard/baseline configuration so that Material Ledger data types are included (active) during data exports. Being sure to include Material Ledger data will help avoid the potential "material is inconsistent" error as is detailed here:
https://hayes.zendesk.com/entries/46...consistent-FAQ

If you are interested in making these same changes within your Gold Client configuration, follow the instructions below.

1. Go to ZGOLD > Configuration > Framework > Client Construct
2. Select data type MATERIAL LEDGER (CKML) and then open the 'Master Data Tables' folder
3. A list of nine tables will likely be present; chances are that the 'Exclusion Flag' is set for all of them and an 'Exclusion Reason' is populated
4. Update this table by removing the flag and comments (reason) so that the end result matches what is visible in the screen capture below

Name:  Capture70.PNG
Views: 2
Size:  53.5 KB

5. Go to ZGOLD > Configuration > Framework > Data Echo
6. Open data type MM - MATERIAL VALUATION and then select 'Linkages'
7. Set the link to recipient data type FI - MATERIAL LEDGER (CKMLHD) as active by removing the 'Inactive' checkbox indicator as is visible in the following screen capture
If your organization is also using Material Ledger Cost Component Split, activating this data type would also be recommended. You can query table CKMLPRKEKO if unsure about this.

Name:  Capture71.PNG
Views: 2
Size:  61.2 KB
Attached Images
  

Add table RFDT to the Data Echo framework

$
0
0
The Attunity team has supported some customers recently who required that data which is stored in table RFDT be included in their data copies. In these particular cases it was because Payment Runs had been copied but some of the associated parameters were missing in the target client. We have subsequently enhanced our baseline configuration by including in the Data Echo framework a data type for table RFDT and then linked it accordingly.
A couple of notes regarding table RFDT:
(1) SAP has defined the delivery class as 'C' (Customizing). and typically our team does not promote adding customizing tables to Gold Client but based on our work with customers, we feel that an exception could be made here; however it may be in your team's best interests to ensure that moving records stored within this table is not going to cause any unforeseen issues for your organization.
(2) The data which is stored in table RFDT is going to appear pretty useless to an end-user and that is because the "real" data is stored within a cluster field which is read via SAP programs a/o function modules. So the chances are you're probably unsure whether or not you need to copy data stored in this table and that's okay. Our team can always try and support you if unsure; just submit a ticket and we will respond.
If you're interested in the changes we have made to our standard, you can replicate these within your own system by following the steps below.

1. Create a new data type named FI - ACCOUNTING DATA (RFDT)

Name:  Capture78.PNG
Views: 1
Size:  29.1 KB

2. Add table relation RFDT-RFDT and add the relevant common fields

Name:  Capture79.PNG
Views: 1
Size:  81.4 KB


3. Create links to FI - ACCOUNTING DATA (RFDT) as required by your organization; in our standard, we have done this from FI - PAYMENT RUNS and FI - DUNNING DATA; the linkage details for these two data types follow below.
Note: our standard config has the links set to be 'Inactive' by default; if you want the RFDT data to be included in the export, it should not be set as inactive

Name:  Capture80.PNG
Views: 1
Size:  102.4 KB

Name:  Capture81.PNG
Views: 1
Size:  133.0 KB
Attached Images
    

New Data Type CO - COST PLANNING

$
0
0
To include cost planning reporting (data from transaction KSBT) in your Gold Client configuration, please make the following changes.
New data type CO - COST PLANNING:
Table - Source Table
ONRKL - ONRKL (header)
ONR00 - ONRKL (link on common field OBJNR)
ONRKS - ONRKL (link on common fields OBJNR, KOKRS, & KOSTL)
ONRAO - ONRKL (link on common fields OBJNR & KOKRS)
ONRBP - ONRKL (link on common fields OBJNR & KOKRS)
ONRHP - ONRKL (link on common field OBJNR)
Add a linkage to CA - COST CENTERS to get the master data associated with these costs.
CSKS-KOKRS EQ ONRKL-KOKRS
AND CSKS-KOSTL EQ ONRKL-KOSTL
See attached screenshots.

Name:  Capture65.PNG
Views: 1
Size:  191.5 KB
Name:  Capture66.PNG
Views: 1
Size:  156.3 KB
Name:  Capture67.PNG
Views: 1
Size:  79.2 KB
Name:  Capture68.PNG
Views: 1
Size:  77.9 KB
Name:  Capture69.PNG
Views: 1
Size:  98.0 KB
Attached Images
     

Add Table ANLBZA to CA - ASSET MASTER & CA - ASSET MASTER (ORIGIN)

$
0
0
If your company uses table ANLBZA (Time-Dependent Depreciation Terms) it should be added to data types CA - ASSET MASTER & CA - ASSET MASTER (ORIGIN) in your Gold Client configuration. To verify you are using it, execute SE16 or SE16N in your source system & check the number of entries for ANLBZA. If you have entries, please add it to those data types. It should be added with source table ANLA with common fields ANLN1, ANLN2, & BUKRS.
Table Name - Source
ANLBZA - ANLA
Common Fields:
ANLBZA-ANLN1 = ANLA-ANLN1
ANLBZA-ANLN2 = ANLA-ANLN2
ANLBZA-BUKRS = ANLA-BUKRS
See the attached screenshot.

Name:  Capture.PNG
Views: 1
Size:  94.1 KB
Attached Images
 

Planning Profile tables

$
0
0
If your organization creates Planning Profile records and wants to be able to copy this data using Gold Client, follow the steps below to enhance your Gold Client configuration.

Enhancements to the Client Construct framework can be made by adding tables TPHVP, TPLVP, and TPSVP to existing data type MATERIAL MASTER & MRP.

Name:  Capture1.PNG
Views: 1
Size:  66.6 KB


If you want to be able to copy subsets of Planning Profile records, then enhancements to the Data Echo framework can be made as follows:
1) Create new data type CA – PLANNING PROFILES using the details displayed here:

Name:  Capture2.PNG
Views: 1
Size:  63.2 KB

2) Be sure to add the field joins (common fields) for each table relation as shown in the screen captures here:

Name:  Capture3.PNG
Views: 1
Size:  67.5 KB
Attached Images
   

Add Master Warranty tables

$
0
0
If your organization creates Master Warranty records and wants to be able to copy this data using Gold Client, follow the steps below to enhance your Gold Client configuration.

Enhancements to the Client Construct framework should be made as follows:

1) Create new data type MASTER WARRANTY

Name:  Capture4.PNG
Views: 2
Size:  80.4 KB

If you want to be able to copy subsets of Master Warranties, then enhancements to the Data Echo framework should be made as follows:
1) Create new data type PM – MASTER WARRANTY using the details displayed here:

Name:  Capture5.PNG
Views: 2
Size:  113.3 KB

2) Be sure to add the field joins (common fields) for each table relation as shown in the screen captures here:

Name:  Capture6.PNG
Views: 2
Size:  91.6 KB

3) Add a link from any equipment data types, such as CA – EQUIPMENT DATA, to the new data type PM – MASTER WARRANTY; set the linkage details as seen in this screen capture:

Name:  Capture7.PNG
Views: 2
Size:  120.2 KB

4) For any other objects that have master warranties, add a link (as needed) to PM – MASTER WARRANTY using similar linkage details as performed in the previous step
Attached Images
    

Add DFKKTAXEX to ISU Contract Account DTs

$
0
0
If your company uses table DFKKTAXEX (Table of FI-CA Tax Exemptions) you may want to add it to your Gold Client configuration. To verify that it is used, go to transaction SE16 or SE16N & execute it for table DFKKTAXEX. Select the Number of Entries option to see if there is a record count. If there is & you want this data included in Gold Client exports, add table DFKKTAXEX to the following data types in your source system:
IS-U: COLLECTIVE CONTRACT ACCT
IS-U: CONT ACCT FROM CONTRACT
IS-U: CONTRACT ACCOUNT
IS-U: CONTRACT ACCOUNT FROM REQ
IS-U: CONTRACT ACCOUNT W BP
IS-U: CONTRACT ACCT W/ COLLECT
Add table DFKKTAXEX with source table FKKVKP. The common field relationship is DFKKTAXEX-VKONT = FKKVKP-VKONT. Please see the attached screenshot for an example.

Name:  Capture8.PNG
Views: 1
Size:  183.4 KB
Attached Images
 

FI control/object tables

$
0
0
A new data type has been created for the “Client Construct” part of Gold Client. This new data type is a collection of FI-CO control tables relevant to Profit Center Accounting (GLPCC, GLPCO), Cost of Sales Accounting (GLFUNCC, GLFUNCO), Consolidations (ECMCC, ECMCO), and Reconciliation Ledger (COFIO1, COFIO2). It’s important to copy the control data stored within these tables so that the data in the “Actuals” tables (e.g. GLPCA) can be tied to the data in the “Totals” tables (e.g. GLPCT).

Name:  Capture9.PNG
Views: 1
Size:  67.4 KB
Attached Images
 

Enhancements to CA – CONFIGURATION OBJECTS

$
0
0
If your organization uses Variant Configuration, it’s possible that the enhancements to the Gold Client configuration listed here are relevant to you. If unsure, you can use t-code SE16 or SE16N to determine if your system contains any data in these various tables.
This first set of changes is relevant to the Data Echo framework.

1. Add table relation CECUSD - CUCO using common fields CE_DESIGN – DESIGN as detailed here:

Name:  Capture10.PNG
Views: 1
Size:  111.1 KB

2. Add the table relations below where the common fields used are DSINT – DSINT as detailed below:

CECUFM – CECUSD
CECUSDT – CECUSD
CECUSF – CECUSD
CECUSFT – CECUSD

Name:  Capture11.PNG
Views: 1
Size:  44.1 KB

3. Save entries and exit

This next set of changes is relevant to the Client Construct framework.
1. Add table entries CECUSF, CECUSFT, and BCST to Master Data Type VARIANT CONFIGURATOR

Name:  Capture12.PNG
Views: 1
Size:  76.0 KB

2. Save entries and exit
Attached Images
   

Config changes to help export text in relation to Orders and Operations data

$
0
0
If your organization needs to export text that is related to various types of orders (Production, Work, Internal, Cost Collector, etc.) and/or operations data, then you may need to update your Gold Client configuration as per the details that follow.
The primary reason for this config change is due to how SAP stores this data in the STXL table. In the screen capture below you can see how the value stored in the TDNAME field is a concatenation of the MANDT (Client) value that is bordered in green and the AUFNR (Order) value that is bordered in purple. The config changes recommended below takes this detail into account so that the data can be exported successfully.

Name:  Capture13.jpg
Views: 1
Size:  75.6 KB

(1) In your Source system (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
(2) Add a link from data type PP - OPERATIONS to data type CA - TEXT using the details in the screen capture below
The third linkage detail line that reads “AND STXL TDNAME LIKE *” uses a concatenation of values stored in fields MANDT and AUFPL. To add these two values simply double-click the line that contains the asterisk (*) and input these values. Note: the MANDT value is not available via the search (look up) function so it must be added manually.

Name:  Capture14.PNG
Views: 1
Size:  126.1 KB
(3) A link to data type CA - TEXT from one or more the following list of Order-based data types likely exists in your configuration already (if not, you can freely add a new data type link): CO - COST COLLECTOR ORDERS, PM - WORK ORDERS, PM - WORK ORDERS FROM PO, PP - ORDER MASTERS, and PP - PRODUCTION ORDERS.
Assuming the config already exists, you will need to change it so that the third linkage detail line that reads “AND STXL TDNAME LIKE *” which uses a concatenation of values stored in fields MANDT and AUFNR. To add these two values simply double-click the line that contains the asterisk (*) and input these values. Note: the MANDT value is not available via the search (look up) function so it must be added manually.
The screen capture below shows how our standard config has been updated in respect to data type CO - COST COLLECTOR ORDERS; however this is just an example since the update is the same for all of the Order-based data types (those noted above).

Name:  Capture15.PNG
Views: 1
Size:  128.2 KB
Attached Images
   

Standard Config Change - Add Linkage on CO - INTERNAL ORDERS

$
0
0
If your organization settles internal orders, you may want to add this new linkage to your existing Gold Client configuration.

In the Data Echo Framework, open data type CO - INTERNAL ORDERS and select the 'Linkages' maintenance view
Add a link to CO - SETTLEMENT DOCUMENTS using the linkage details in the screen capture below.

Name:  Capture16.PNG
Views: 1
Size:  102.1 KB
Attached Images
 

Adding table AMPL to both Gold Client frameworks

$
0
0
If your organization generates data in the AMPL table (Table of Approved Manufacturer Parts) and you want to copy this data using Gold Client, follow the steps below to add this table to your configuration.

Add table AMPL to the Client Construct framework

Step 1: In your primary Source client (typically Production), go to ZGOLD > Configuration > Framework > Client Construct
Step 2: Select data type MATERIAL MASTER & MRP and then open the 'Master Data Tables' subfolder
Step 3: Add table AMPL using the screen capture below for guidance
Step 4: Save your changes and exit the framework

Name:  Capture17.PNG
Views: 1
Size:  19.5 KB

Add table AMPL to the Data Echo framework

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 below
Data Type: MM - APPROVED MFG PARTS LISTS
Datatype Kind: M (master data)
File ID: MMAMPL
Data Snap Rec Limit: 1000
Step 3: Open data type MM - APPROVED MFG PARTS LISTS and select the 'Tables' maintenance view
Step 4: Add table relation AMPL-AMPL, and be sure to add the common fields using the screen capture below for guidance

Name:  Capture18.PNG
Views: 1
Size:  75.3 KB

Step 5 (Optional): Open data type MM - APPROVED MFG PARTS LISTS and select the 'Linkages' maintenance view. Add a new data type link to CA - TEXT, and be sure to apply the linkage details using the screen capture below for guidance

Name:  Capture19.PNG
Views: 1
Size:  96.5 KB

Step 6: Open data type MM - MATERIAL MASTER and select the 'Linkages' maintenance view. Add a new data type link to MM - APPROVED MFG PARTS LISTS, and be sure to apply the linkage details using the screen capture below for guidance

Name:  Capture20.PNG
Views: 1
Size:  84.3 KB

Step 7: Save changes one final time and exit the framework
Attached Images
    

Add Table ADRU to Address DTs

$
0
0
If your organization generates data in table ADRU, you should consider adding this table to the Gold Client configuration. To verify if you use it, execute SE16 or SE16N for table ADRU and check the number of entries for the table. If entries exist, please complete the steps below.

CLIENT CONSTRUCT Framework
Step 1: In your primary Source client (typically Production), go to ZGOLD > Configuration > Framework > Client Construct
Step 2: Select data type CENTRAL ADDRESS MASTER and open the 'Master Data Tables' folder
Step 3: Add table ADRU; save your changes and exit the framework

Name:  Capture21.PNG
Views: 2
Size:  42.6 KB

DATA ECHO Framework
Step 1: In your primary Source client (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Open data type CA - CENTRAL ADDRESS MANAGEMENT and select the 'Tables' maintenance view
Step 3: Add a new entry for table relation ADRU - ADRC, and be sure to add common fields ADDRNUMBER - ADDRNUMBER
Step 4: Save your changes and exit the framework

Name:  Capture22.PNG
Views: 2
Size:  70.3 KB
Attached Images
  

Add tables to the MATERIAL MASTER & MRP data type in Client Construct

$
0
0
Material-related reports and stock levels can be erroneous if the tables in the list below are not included in the export when material master data is refreshed (assuming your organization has data in these tables). It does not hurt to add the tables even if you do not use them in your system because it will simply skip them on export if they are empty. If you want to deploy these changes in your system, follow the instructions below.
MCSD
MCSDH
MSIS
MCSS
MCSSH
MSCD
MSCDH
MSCS
MSID
MSIDH

Step 1: In your primary Source client (typically Production), go to ZGOLD > Configuration > Framework > Client Construct
Step 2: Select data type MATERIAL MASTER & MRP and then open the 'Master Data Tables' subfolder
Step 3: Add the tables from the list above using the screen capture below for guidance
Step 4: Save your changes and exit the framework

Name:  Capture23.PNG
Views: 1
Size:  35.1 KB
Attached Images
 

Add Tables to MM - MATERIAL MASTER

$
0
0
You may want to add tables to the material master configuration in Gold Client so that the data in the list of 13 tables below is included in your export. To verify if you use these tables you can execute record counts via transaction SE16 or SE16N in your Production system or a recent copy of Production.
DBPR
DBVM
DVER
MCSD
MCSDH
MCSS
MCSSH
MSCD
MSCDH
MSCS
MSID
MSIDH
MSIS

Step 1: In your primary source system (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Open data MM - MATERIAL MASTER and select the 'Tables' maintenance view
Step 3: Add the three table relations below and be sure to add the common fields for each as displayed in the following screen captures
DBPR - MDMA
DBVM - MARA

DVER - MARA

Name:  Capture24.PNG
Views: 1
Size:  105.4 KB

Step 4: Add the four table relations below and be sure to add the common fields for each as displayed in the following screen captures
MCSD - MARA
MCSDH - MARA
MCSS - MARA
MCSSH - MARA

Name:  Capture25.PNG
Views: 1
Size:  119.3 KB

Step 5: Add the six table relations below and be sure to add the common fields for each as displayed in the following screen captures
MSCD - MARA
MSCDH - MARA
MSCS - MARA
MSID - MARA
MSIDH - MARA
MSIS - MARA

Name:  Capture26.PNG
Views: 1
Size:  145.7 KB

If you have other variations of MM - MATERIAL MASTER in your configuration such as MM - MATERIAL BOM COMPONENTS, MM - MATERIAL MASTER W/ VC DATA, or MM - MATERIALS WITH BOMS, you should add the same tables there also for consistency.
Attached Images
   

Add Table LL06 to WM – WAREHOUSE MANAGEMENT

$
0
0
If your organization uses the Warehouse Activity Monitor in your SAP system, you may want to add this change to your Gold Client configuration so that you can include this data in your export. To verify if you use it, in your Production system (or a recent copy of Production), use transaction SE16 or SE16N to query table LL06 to see if data exists. If you want to deploy this change to your config, follow the instructions below.

Step 1: In your primary Source client (typically Production), go to ZGOLD > Configuration > Framework > Data Echo
Step 2: Open data type WM - WAREHOUSE MANAGEMENT and select the 'Tables' maintenance view
Step 3: Add table relation LL06 - LAPG, and be sure to add the common fields using the screen capture below as guidance
Step 4: Save changes and exit the framework

Name:  Capture27.PNG
Views: 2
Size:  93.5 KB
Attached Images
 
Viewing all 411 articles
Browse latest View live