Yes this can be done .
Isn't it logically wrong? to insert a child whose parent is already deleted.
HI Gaurav ,
Yes logically it is wrong , but it depends upon business use case may be the same child is point to other parents .
It is logically wrong but MDM does supports it so that the parent and child records can be deleted/reactivated asynchronously i.e. in 2 different batch jobs or API calls. If you are looking to promote/delete parent/child and multiple records at the same time, you may want to understand the concept of interaction_id, where any parent/child records linked to the same interaction_id are promoted/deleted in the same API call.
Yeah it is possible, but it will lead to orphan child records in your system which do not have any parent associated, so if it is any unique business use-case where you want to have these active data in child then you can go ahead with it.
If you execute a load job on the child with hub_state_ind=1 whose parent is already soft-deleted, the load job will fail as "SIP-23014: ERROR: Cannot find lookup value x for column y".
However, if you run a real-time call (eg. SIF PUT) to insert a child record with a soft-deleted parent, the call will go thorugh successfully and will create an active child record in the BO.