Planning Operator Configuration

[former_member222291]

Hello Experts,

I have two questions regarding the planning operator configuration:

- First, we recently upgraded to IBP 4.0.1.3 and I'm trying to create a GROUP type planning operator in order to explore this new functionnality.

Can anybody provide more information on the proper configuration for this type of operator, especially on the Schedule Procedure name to use.

- Is there any parameter that we can use to limitate the scope of an Operator to a specific set of master data. I know about Planning Units, but I would like to insert a limitation parameter directly at the Planning operator level...

Thanks again for your help. Always appreciated!

Philippe

[former_member222291 · Accepted solution]

Second try... Would there be any expert down here that could provide more info on this?

[former_member217157 · Accepted solution]

Hi Philippe,

The documentation of Group Operator will be coming out in 4.0 FP1  Patch 4 that is planned for this month. The reason being the setting of Group Planning Operator needs Operator ID and the UI does not display the Operator IDs in Patch 3. This is addressed in Patch 4

Here are the settings..

ID: GROUP

Name: e.g. Group Operator

Description: e.g. Group Operator

Add Job Procedure: SAP_SFND."sap.sop.sopfnd.catalogue::SOPAPI_OPERATOR_SCHEDULER_JOB_ADD"

Schedule Procedure:

SAP_SFND."sap.sop.sopfnd.catalogue::SOPAPI_EXECUTE_SCHEDULER_GROUP_JOB"

Mode:

Interactive Mode	No
Batch Mode	Yes
Filter Mode	Yes or No, depending on whether the user may use filters when running or scheduling the Operators in the IBP add-in for Microsoft Excel

Parameters:

OPERATOR_TYPEn (Mandatory) – Operator type like COPY, SCM etc. n is a number starting from 1.

OPERATOR_IDn (Mandatory) – Technical Operator ID (not the operator name). n is a number starting from 1.

Operator type and ID need to be defined in pairs.

DI_KFIDn (Optional) – Key figure ID. n is a number starting from 1. This group will be triggered when specified key figure values are uploaded using data import. Multiple key figures can be specified.

example:

Parameter Name	Parameter Value
OPERATOR_TYPE1	COPY
OPERATOR_ID1	10002
OPERATOR_TYPE2	COPY
OPERATOR_ID2	10003
DI_KFID1	TARGETREV

Assign this operator to planning area. All the other operators used in this operator should also be assigned to the planning view.

Note: To know the Operator ID associated with the Operator, you can open a Customer ticket for your project. (or wait till Patch 4)

To Limit the scope you can run the operator from Excel with Filters like any other Operator

Hope this helps.

Thanks,

Raghav

[former_member222291 · Accepted solution]

Raghav, thanks for the precision!

One more question about the operator scope (and this question is not specific to group operator) : Apart from Excel filters, is there any other way to limit the scope of a planning operator run?

Best Regards

[former_member217157 · Accepted solution]

Hi Philippe,

It depends on the Operator:

Example

Copy Operator has parameter <Attribute>_VALUEn for filters

Stat Forecast Operator has Filter that can be setup during Forecast Profile Definition

Thanks,

Raghav

[Former Member · Accepted solution]

Hi Rahgav,

Is this feature available for on-premise version?

Copy Operator has parameter <Attribute>_VALUEn for filter

Does the <Attribute> have a be a root or non-root attributes also work?

Regards,

Aditya G

[former_member222291 · Accepted solution]

Does any similar parameter exist for SCM operators?

Thanks again!