It should be possible to have a Macro service creation create a VNF without having to create the vfModule.

However while the building blocks do seem to allow for this it is blocked because a validation in the ApiHandler required the vfModules even though the json doesn't require it.

See  

org.onap.so.apihandlerinfra.validation.UserParamsValidation

...

if(vnf.getVfModules().isEmpty())

{ throw new ValidationException ("vfModules in userParams vnf resources", true);  }

...

This stops the following been used in the Macro request to 

soip:30277/onap/so/infra/serviceInstantiation/v7/serviceInstances

with the attached request.

key part is 

"vnfs": [
{
"modelInfo":

{ "modelCustomizationName": "MARCOSINGLEVF/SIMPLE 0", "modelCustomizationId": "b4990b18-6468-4a7b-808b-d3bead021996", "modelInvariantId": "181ba261-0820-442e-aa5c-06300d760330", "modelVersionId": "cf84c49b-3104-4e5b-96dc-c2215441c117", "modelName": "MARCOSINGLEVF/SIMPLE 0", "modelType": "vnf", "modelVersion": "1" }

,
"cloudConfiguration":

{ "tenantId": "3b368b5d42f94fe3ada6fb5abaf25455", "cloudOwner": "CloudOwner", "lcpCloudRegionId": "regionOne" }

,
"platform":

{ "platformName": "demoPlatform" }

,
"lineOfBusiness": {},
"productFamilyId": "vCPE",
"instanceParams": [],
"vfModules": []
}
],