I am getting an error with epmautomate runintegration using the {Month#Year} nomenclature.

Summary:

When running an integration with epmautomate runintegration using the {Month#Year} nomenclature I am getting an error if I use the corresponding DM period name the integration will run as expected. I

Content (please ensure you mask any confidential information):

In this example we have a custom period dimension with 24 periods. P18 is the member name for the period and FY23 is the member name for the Year. P18-23 is the DM Period name.

C:\Oracle\EPM Automate\bin>epmautomate runIntegration "Retail Budget Load to ASO" importmode=Replace exportmode=check periodname={P18#FY23}

Processing...

EPMAT-1:EPMFDM-ERROR: Start Period does not correspond to any period in the target Application Period Mapping / Global Period Mapping.