I am in a situation where I have to perform a transaction master detail record (Drop prev details, insert new details, Update Master status)
I guess you mean exposing those 4 fields, instead of inheriting them since you cannot really inherit fields, only a class.
You could make a smaller, simpler 'update object', but I would only do so if this smaller object also exists logically in your model. Ideally, you really don't want to create special objects for updating only parts of your business objects. Instead, it's the task of your persistence layer to be smart enough to know which fields have changed and act accordingly (ie only update those fields).
So in summary:
Create DTO with those 4 fields. UI will send this DTO to business layer which will use new values to modify business object. Than you persist that modified business object.