E Appendix: MFPCS Specific Custom Functions, Procedures, and Special Expressions

MFP Cloud Service uses the RPAS Batch Framework to set up the batch process. For more details about understanding batch_control files and its uses in the batch process, see the Oracle Retail Predictive Application Server Cloud Edition Implementation Guide. Any application-specific custom functions are packaged in RASL libraries and those are available to use in the batch_exec_list.txt control file with the service name as ra_custom to trigger to those functions and parameter as the function name. The following list of predefined custom functions are available RASL libraries installed as part of RPAS that are used by MFP.

Custom Function: rms_clnd_label

During the file-based integration, RMFCS interfaces the calendar hierarchy file (rms_clnd.csv.dat), but does not include any calendar labels. This function formats the file, filters the required columns for the MFP GA calendar hierarchy, and adds the calendar labels. This function requires the RMFCS calendar file to be present in the cloud share location with the name rms_clnd.csv.dat. After the call, this function creates the calendar hierarchy file clnd.csv.dat in the domain input directory for the subsequent hierarchy load process.

This function takes an additional optional parameter, Calendar Start Month, for generating the calendar month labels. If none is provided, it will use Feb as the start month for the 4-5-4 calendar. For example, if the customer financial start month is October (the tenth month of the year), they can pass the optional parameter as 10 (use ~ as the separator to provide the additional parameter) to generate the start month as Oct.

Example:

batch_rms_xform | ra_custom | rms_clnd_label

Special Expressions and Procedures Used in MFPCS Configuration

This section contains details about the special expressions that are not standard RPAS expressions/procedures but are used in the MFPCS configuration.

AttributesPickListExpr - Attribute Picklist Expression

This procedure is used to determine a picklist of values from a base string measure along the positions of the specified hierarchy. It also takes in a Filter Boolean as input to control which intersections are to be used to pick data for the picklist.

Syntax:

OUTMEAS <- AttributesPickListExpr(FILTERMEAS, INPUTMEAS, HIER, OUTFORMAT)

Example:

ADHDLikePoCT <- AttributesPickListExpr(ADHDLikePoCB,ADHDLikePoCL, "LOC", "0")

Expression Parameters:

The following table shows the parameter details for the expression.

Parameter Name	Parameter Type	Data Type	Description
OUTMEAS	Output	String	Output Picklist Measure which will be a string value.
INPUTMEAS	Input	String	Input String Measure containing the picklist values stored along a hierarchy.
FILTERMEAS	Input	Boolean	Boolean measure with the same intersection of OUTMEAS. It should be set to true for the intersections picklist that needs to be created.
HIER	Input	String	Hierarchy Name specified as a String constant along which the picklist values need to be used. This hierarchy should be present in INPUTMEAS.
OUTFORMAT	Input	String	Output format with valid values "0" or "1". Using "0" will create a picklist using position names as picklist internal names and labels as attribute values. "1" will create a picklist using position values as name and labels for the picklist.