Current Record Header/SVMX.CURRENTRECORDHEADER
It refers to the ‘HEADER’ of the ‘CURRENT’ (i.e. child) ‘RECORD’. ‘HEADER’ refers to the ‘Header’ object in SFM, which is not always a ‘Master’ object in a ‘Master/Detail’ relationship, as the example provided later in this section illustrates.
It applies as a prefix, with the suffix being ‘.’ followed by API Name of a field in the ‘HEADER’ object. An example is SVMX.CURRENTRECORDHEADER. SVMXC__Service_Order__c.
This literal is used in the following scenarios:
• When a child section field must be mapped to the value of a header section field, when creating new child records. This applies to both field and value maps.
• When for a lookup field in a child section, lookup object’s attribute must be compared with the value of a header section field, in lookup search basic filter (pre-filter).
 |
This literal is not valid when used for a field in the header section of an SFM transaction page layout.2. This literal does not work in value maps for Source To Target All and Standalone Create type of SFM transactions, where the header record is also newly created.3. For this literal to work, both the source and the target fields must be included in the page layout.
|
OOTB usage of this literal can be seen in the standard SFM transaction 'Manage Work Details for Products Serviced' (LinkedProcess_WD_001) transaction, where header object is Work Detail (Record Type: Products Serviced) and child is also Work Detail (Record Type: Usage/Consumption).
In the value map for creating new Usage/Consumption lines in this SFM transaction, 'Work Order' field in child Work Detail is set to 'SVMX.CURRENTRECORDHEADER.SVMXC__Service_Order__c'. This will map the Work Order field in the newly created child object records to the value of Work Order field in the header object.