Own Condition - Badi CONTAINER_PPF

[Private_Member_19084]

Hi experts,

I would like to use an own condition.

Therefore I already appended the field to the conditions and I also implemented the badi CONTAINER_PPF.

The badi is also called.

However, the parameter CI_PARAMETER is always not bound / initial.

So I can't maintain my field.

What is the reason, that the CI_PARAMETER is unbound?

Thx for any help

[Former Member · Accepted solution]

Hi Christian,

Have you defined the filter for your BADI implementation. Normally it should be the business object type value .

Regards,

Nithish

[Private_Member_19084 · Accepted solution]

Hello Nithish,

yes I've defined the filter.

And as written, the badi is called, but the CI_PARAMETER is unbound.

thx

[Former Member · Accepted solution]

Hi Christian,

It should have filled CI_PARAMETER with the start condition parameters. Does CI_CONTAINER is bound??

Regards,

Nithish

[Private_Member_19084 · Accepted solution]

Hi Nithish,

first thx for help.

Yes, CI_CONTAINER is filled and bound.

thx in advance

[Former Member · Accepted solution]

It really look strange  , what is the start condition which you have used??

[Private_Member_19084 · Accepted solution]

It is an own (new) condition.

I only check there the Z-Field which I would like to fill with the badi.

Thx

[Former Member · Accepted solution]

Hi,

I understand you created a start condition for your action definition.

I think you should also define a parameter name along with the condition, so that you can set the value of it in the badi impl.

in transaction CRMC_ACTION_CONF, under the start condition tab you have an option 'define parameter'.

I believe only when this is defined does the ci_parameter gets initialized in the badi.

Thanks,

Rajini A.

[Private_Member_19084 · Accepted solution]

Hi Rajini,

but I already maintained a parameter name.

Exactly the same which I would like to set via the badi.

But it is not bound.

Thx for help

[VishnAndr · Accepted solution]

Hello, Christian.

Could you please clarify the following: are you trying to add an own attribute to the container to check it in a workflow condition in actions? Only one and only for this purpose?

If yes, have you considered  to use BAdIs EVAL_STARTCOND_PPF or EVAL_SCHEDCOND_PPF for start or schedule conditions yet? You can refer to Note 1007346 - Scheduling of actions only after resetting a status

Regarding your direct question. Have you maintained business object type when you defined an action profile? Is it correct one?

[Former Member · Accepted solution]

Hi Christian,

I guess you need to have some other combination for start condition like status or date along with your z field , then you can use the BADI implementation to overwrite or set the value in the z field.

Regards,

Nithish

[Former Member]

Hi Christian,

there are three SAP standard solutions to enhance PPF Action conditions. Using BADI CONTAINER PPF is one of them. Using BADI EVAL_SCHEDCOND_PPF or EVAL_STARTCOND_PPF is another solution.

However, the most simplest solution is to enhance the BOR object providing context sensitive attributes which can be combined and evalutated. In most cases the enhancement can be done without development. In my opinion this solution is the most consultant friendly one.

Because I could not find any guide explaining this solution in a good  and development free manner, I created an own one. Please be free to use it too.

http://www.hybrid-eichhoernchen.de/ppf-action-condition-enhancement/

Kind regards,
Peter

[Former Member]

Hi Peter,

Thanks for the detailed info.It was very useful.

[Private_Member_19084]

Thx to all for help.

It was a stupid mistake, sorry for stealing your time.

The action was only active at saving, and I always debugged every submit.

At saving it worked fine.

thx to all for help