In the PR scenario, you need to open the object structure in the Object Structures application, click Inbound Setting Restrictions to open the dialog, and make the PRNUM field restricted (clicking the override checkbox and then checking the Restricted checkbox). This tells the integration framework to ignore values you provide for this column in the integration and when the field is set to autonumber, will trigger the autonumber. It's also common to do this for fields like STATUS because there is a proper way that the change status needs to be invoked. 

Hello Steven, 

Thank you for your inputs. Actually, PR and PRLINE OS is working after overriding PRNUM. we have a custom main object and child object. We have created an OS with parent and child having support Flat File. 

Here is our configuration.  I gave exclude parent key attribute in Advanced Configuration but not sure why it is pulling columns rulenum/orgid and siteID in Include/Exclude Fields. I have excluded manually and imported via Application Import. getting mandatory keys are missing. 

How can we import multiple records ?

In the PR scenario, you need to open the object structure in the Object Structures application, click Inbound Setting Restrictions to open the dialog, and make the PRNUM field restricted (clicking the override checkbox and then checking the Restricted checkbox). This tells the integration framework to ignore values you provide for this column in the integration and when the field is set to autonumber, will trigger the autonumber. It's also common to do this for fields like STATUS because there is a proper way that the change status needs to be invoked. 

Can you share how you have defined this custom object from a primary key column perspective? In Database Configuration, open your object and sort based on the primary key column sequence descending. Most customers leave this as the unique ID on the table (IE workorderid) rather than the keys from the parent plus whatever makes it unique on the child. For example, PRLINE is set to PRLINEID rather than the more appropriate SITEID, PRNUM, PRLINENUM that you would think (with SITEID & PRNUM coming from the PR header and the PRLINENUM making each line unique). The MIF was built to support this, either by defining an alternate index on the object in Database Configuration (what Maximo does for PRLINE & POLINE) or an alternate key on the object structure in the Object Structures application. This allows you to specify a different index that you say makes the record unique from an integration perspective and will override what Maximo treats as the parent keys. 

Once you establish what you expect the parent to set, along with what makes each child object unique, create an index on your custom table with those columns. And then the parent key can be excluded on the messages. 

Hello Steven, 

Thank you for your inputs. Actually, PR and PRLINE OS is working after overriding PRNUM. we have a custom main object and child object. We have created an OS with parent and child having support Flat File. 

Here is our configuration.  I gave exclude parent key attribute in Advanced Configuration but not sure why it is pulling columns rulenum/orgid and siteID in Include/Exclude Fields. I have excluded manually and imported via Application Import. getting mandatory keys are missing. 

How can we import multiple records ?

In the PR scenario, you need to open the object structure in the Object Structures application, click Inbound Setting Restrictions to open the dialog, and make the PRNUM field restricted (clicking the override checkbox and then checking the Restricted checkbox). This tells the integration framework to ignore values you provide for this column in the integration and when the field is set to autonumber, will trigger the autonumber. It's also common to do this for fields like STATUS because there is a proper way that the change status needs to be invoked. 

@Steven Shull Here we go! 

Import File:

Can you share how you have defined this custom object from a primary key column perspective? In Database Configuration, open your object and sort based on the primary key column sequence descending. Most customers leave this as the unique ID on the table (IE workorderid) rather than the keys from the parent plus whatever makes it unique on the child. For example, PRLINE is set to PRLINEID rather than the more appropriate SITEID, PRNUM, PRLINENUM that you would think (with SITEID & PRNUM coming from the PR header and the PRLINENUM making each line unique). The MIF was built to support this, either by defining an alternate index on the object in Database Configuration (what Maximo does for PRLINE & POLINE) or an alternate key on the object structure in the Object Structures application. This allows you to specify a different index that you say makes the record unique from an integration perspective and will override what Maximo treats as the parent keys. 

Once you establish what you expect the parent to set, along with what makes each child object unique, create an index on your custom table with those columns. And then the parent key can be excluded on the messages. 

Hello Steven, 

Thank you for your inputs. Actually, PR and PRLINE OS is working after overriding PRNUM. we have a custom main object and child object. We have created an OS with parent and child having support Flat File. 

Here is our configuration.  I gave exclude parent key attribute in Advanced Configuration but not sure why it is pulling columns rulenum/orgid and siteID in Include/Exclude Fields. I have excluded manually and imported via Application Import. getting mandatory keys are missing. 

How can we import multiple records ?

In the PR scenario, you need to open the object structure in the Object Structures application, click Inbound Setting Restrictions to open the dialog, and make the PRNUM field restricted (clicking the override checkbox and then checking the Restricted checkbox). This tells the integration framework to ignore values you provide for this column in the integration and when the field is set to autonumber, will trigger the autonumber. It's also common to do this for fields like STATUS because there is a proper way that the change status needs to be invoked. 

When you want something to autonumber, you do not provide the column in your file. Since you want odm_rulenum to autonumber (and I assume have autonumber configured in database configuration for it), you would leave it as restricted and not provide it in the file. Similar for IDs like ASSETTYPESID. These should be restricted (as it is in the screenshot) and not provided in the file.

You mentioned that you excluded the columns like rulenum, orgid, siteid on your child object yet you have an alternate index on the main object and a relationship that depends upon those. The exclude parent key feature doesn't mean the same thing as excluding the column on the object structure. Anything that is used to make up the primary key must exist in the object structure. Maximo should prevent you from excluding them when you reference an alternate key that contains those columns for this reason.

First step is to include those columns again in the child object.

Then your child object should have an alternate index as well with those 3 columns from the parent + whatever else makes it unique. I'm not sure if ASSETTYPE in your example is enough or if you need to use the ID like ASSETTYPESID. If you need the ID, then that means every import will automatically create new entries unless you provide the ID since it's set to autogenerate and thus will be unique. You would not need to provide the 3 columns (rulenum, orgid, & siteid) for the child object. That's what the exclude parent key does. 

@Steven Shull Here we go! 

Import File:

Can you share how you have defined this custom object from a primary key column perspective? In Database Configuration, open your object and sort based on the primary key column sequence descending. Most customers leave this as the unique ID on the table (IE workorderid) rather than the keys from the parent plus whatever makes it unique on the child. For example, PRLINE is set to PRLINEID rather than the more appropriate SITEID, PRNUM, PRLINENUM that you would think (with SITEID & PRNUM coming from the PR header and the PRLINENUM making each line unique). The MIF was built to support this, either by defining an alternate index on the object in Database Configuration (what Maximo does for PRLINE & POLINE) or an alternate key on the object structure in the Object Structures application. This allows you to specify a different index that you say makes the record unique from an integration perspective and will override what Maximo treats as the parent keys. 

Once you establish what you expect the parent to set, along with what makes each child object unique, create an index on your custom table with those columns. And then the parent key can be excluded on the messages. 

Hello Steven, 

Thank you for your inputs. Actually, PR and PRLINE OS is working after overriding PRNUM. we have a custom main object and child object. We have created an OS with parent and child having support Flat File. 

Here is our configuration.  I gave exclude parent key attribute in Advanced Configuration but not sure why it is pulling columns rulenum/orgid and siteID in Include/Exclude Fields. I have excluded manually and imported via Application Import. getting mandatory keys are missing. 

How can we import multiple records ?

In the PR scenario, you need to open the object structure in the Object Structures application, click Inbound Setting Restrictions to open the dialog, and make the PRNUM field restricted (clicking the override checkbox and then checking the Restricted checkbox). This tells the integration framework to ignore values you provide for this column in the integration and when the field is set to autonumber, will trigger the autonumber. It's also common to do this for fields like STATUS because there is a proper way that the change status needs to be invoked. 

When you want something to autonumber, you do not provide the column in your file. Since you want odm_rulenum to autonumber (and I assume have autonumber configured in database configuration for it), you would leave it as restricted and not provide it in the file. Similar for IDs like ASSETTYPESID. These should be restricted (as it is in the screenshot) and not provided in the file.

You mentioned that you excluded the columns like rulenum, orgid, siteid on your child object yet you have an alternate index on the main object and a relationship that depends upon those. The exclude parent key feature doesn't mean the same thing as excluding the column on the object structure. Anything that is used to make up the primary key must exist in the object structure. Maximo should prevent you from excluding them when you reference an alternate key that contains those columns for this reason.

First step is to include those columns again in the child object.

Then your child object should have an alternate index as well with those 3 columns from the parent + whatever else makes it unique. I'm not sure if ASSETTYPE in your example is enough or if you need to use the ID like ASSETTYPESID. If you need the ID, then that means every import will automatically create new entries unless you provide the ID since it's set to autogenerate and thus will be unique. You would not need to provide the 3 columns (rulenum, orgid, & siteid) for the child object. That's what the exclude parent key does. 

@Steven Shull Here we go! 

Import File:

Can you share how you have defined this custom object from a primary key column perspective? In Database Configuration, open your object and sort based on the primary key column sequence descending. Most customers leave this as the unique ID on the table (IE workorderid) rather than the keys from the parent plus whatever makes it unique on the child. For example, PRLINE is set to PRLINEID rather than the more appropriate SITEID, PRNUM, PRLINENUM that you would think (with SITEID & PRNUM coming from the PR header and the PRLINENUM making each line unique). The MIF was built to support this, either by defining an alternate index on the object in Database Configuration (what Maximo does for PRLINE & POLINE) or an alternate key on the object structure in the Object Structures application. This allows you to specify a different index that you say makes the record unique from an integration perspective and will override what Maximo treats as the parent keys. 

Once you establish what you expect the parent to set, along with what makes each child object unique, create an index on your custom table with those columns. And then the parent key can be excluded on the messages. 

Hello Steven, 

Thank you for your inputs. Actually, PR and PRLINE OS is working after overriding PRNUM. we have a custom main object and child object. We have created an OS with parent and child having support Flat File. 

Here is our configuration.  I gave exclude parent key attribute in Advanced Configuration but not sure why it is pulling columns rulenum/orgid and siteID in Include/Exclude Fields. I have excluded manually and imported via Application Import. getting mandatory keys are missing. 

How can we import multiple records ?

In the PR scenario, you need to open the object structure in the Object Structures application, click Inbound Setting Restrictions to open the dialog, and make the PRNUM field restricted (clicking the override checkbox and then checking the Restricted checkbox). This tells the integration framework to ignore values you provide for this column in the integration and when the field is set to autonumber, will trigger the autonumber. It's also common to do this for fields like STATUS because there is a proper way that the change status needs to be invoked.