create table temporal (campo1 number(12) not null,
                       campo2 varchar2(10) not null);

alter table temporal add (campo3 number(12) invisible not null);


insert into temporal values(1, 'ROW 1');

ORA-01400: cannot insert NULL into (squema.TEMPORAL.CAMPO3);


insert into temporal values(1, 'ROW 1', 1);

ORA-00913: too many values 

The objective behind an invisible column is typically to add or remove a column from a table without impacting existing (or perhaps new) application code.

Obviously if that new column is NOT NULL, then by definition, you are demanding that *all* application code be aware of it. Typically, this would not be the case, because only *new* application that knows about the existence of the new column would be populating it.

If you needed to ensure that the new application was not making a mistake an inserting nulls, you could temporarily have a constraint that implements a nullness check for *just* the new application. For example, the new application could set a context variable and the constraint would be:

alter table T
  add constraint chk check ( new_col is not null or sys_context('MY_CONTEXT','APP_VERSION') = '[old version]' );

When all of the application code has been migrated over *and* historical data has been updated, then you could then change the constraint to be a standard not null constraint.