Configure Multi-source Process for Child Records
A combination of field / value maps and lookup form-fill can be used to achieve this. For example, consider a Source To Target type transaction which creates Parts Order Line records from Work Detail records:
Field Map is used for mapping from Work Detail to Parts Order Line for existing Work Detail records. If some of the Parts Order Line fields need to be defaulted from Parts Order (Source To Target Child type transaction only), use SVMX.CURRENTRECORDHEADER literal in the field map. If Product and Location are the other source child objects:
1. Define field map from these objects to Parts Order Line.
2. Include lookups to these objects in Parts Order Line and add these fields in the SFM page layout.
3. Configure lookup form-fill for these lookup fields using the field maps created above.
4. For new child records, define value map for Parts Order Line with SVMX.CURRENTRECORDHEADER literal to map from Parts Order.
Lookup form-fill defined above will apply for new child records also.
Value map and lookup form-fill are applied in that order even when doing a multi-add for child records.
Keep the following in mind:
If multiple sources are of the same type (lookup object), define mutually exclusive field maps for each lookup field.
• Otherwise, the map associated with the last lookup value selected by the user will overwrite the mappings from the other lookup fields.
• An example of this is if you have Installed Product and Parent Installed Product lookup fields, and define form-fill from both these to Parts Order Line. If lookup fields are mapped, include them in the list of display fields in lookup configuration. Include all the mapped target fields in the page layout.
The above method can be used for header object record also. It has the advantage that mobile applications too support this, unlike multi-source configuration which is supported only in online.
Another advantage is that the target field values can be edited by the end user using the same SFM transaction, if required. Use multi-source configuration only when the requirement is to have multiple sources for header AND new child records have to be created from the source child records associated with the secondary source header record.