Ok. Based on your new statement, you do not need to use the SOAP with Attachments API since your do not want to create a web service that includes a file.
You want to create a data-oriented web service that will enable client applications to send data to your application. This is relatively basic and a good approach. In order to create this web service, you will also need to develop an internal client application to simulate the service's users and to
test the web service during development.
The first task then is to clearly identify the data that will be transmitted. This includes data type, how many values, and size. Here
you should also be thinking about security requirements such as how will you identify authorized applications. The details of what your application does once it receives the data are irrelevant in terms of developing the web service component.
The purpose of this web service is to simply allow client applications to send data to your application. The web service does not create CSV files or do any processing of the information sent. "Web Services" is a Integration technology not an Implementation technology.
You can surely find a variety of examples of web services. There are many different flavors of implementations as well as multiple styles, e.g. RESTful, SOAP.
I suggest that you visit the Apache Axis site and go through their documentation. Once you have a good understanding of what is required to develop a web service using the Axis SOAP Engine, roll yor sleeves up and give it a try. Good luck!