Storing Specific data on DB Table(s)
In my mind when you start using a "DB" I'm assuming that you mean a relational/SQL database, and then the design of how the information is stored might change entirely.

It seems like you're using this Excel file to track a master production schedule for some kind of parts manufacturing, so it's how many parts you need, and when you need them by.

I'm not sure it makes sense to have multiple time scales in the same table for that purpose. So my reflex would be to say, we should create a table that stores information about, the date, how many parts need to be produced on that date, and which part needs to be produced.

CREATE TABLE production_schedule (
    prod_date date,
    part_no   int,
    part_qty  int
);


Then if you need to build reporting or gather the information about how much in a week, a month, six months, or a year. You could do that with queries when you need that information or you could create views that are based on such queries.

For example, a query like the following would return the total amount of parts to be created in January 2018.

SELECT SUM(part_qty) FROM production_schedule WHERE prod_date BETWEEN '01/01/2018' AND '31/01/2018';


Hopefully, this helps you understand the way you should think about creating a database to solve your problems, and perhaps a verbatim transfer of the information isn't the best solution.

It can help when getting started to think of databases as spreadsheets because they store information in a way that can be thought of as "column and row". The fact that you can store information in them and also ask sometimes simple and sometimes complicated questions of them can throw off people who are new to working with databases.