FPM Processes and Forms workflow import task error

[Former Member]

We are using HCM FPM Processes and Forms. With out workflow approval process linkage it's working fine all action infotypes get updated.

But, when we link with approval Workflow, workflow is triggering fine but during the step import task TS17900110 it's giving error.

when I check the class CL_HRASR00_WF_COMPONENTS method DATAMAPPING by passing test data from workflow container it's unable to find the entry in table T5ASRSCENARIOS and end up with error.

Is this task TS17900110 will work for FPM Processes and Forms? is there any new wd task for import form fields also instead of this old task TS17900110 ?

since for this FPM processes and forms there are new WD tasks for approval TS33700022 , Edit TS33700023 and save TS33700034.

And also I check some threads which described about CASE Customizing missing etc.

Cross checked with OSS Note 1829705 - P&F-Case Record Model POBJ_MODEL is missing in client 000

All entries are exists as per this note.

We are at latest version of EHP

SAP_HR 608 SP15

EA_HR 608 SP15

[ChrisSolomon]

You are referring to the "import fields from form" task? Yes, that works fine for FPM forms too. What does your binding look like on that task?

[Former Member]

Hi Christopher Solomon,

That task issue is fixed, there is some entry missed as I mentioned case management, re-generated.

And when I initiate workflow all values are imported properly. And the task Is showing as pending for approval. But when I check in PA30, the action has been updated directly with out approval.

I have bind the attributes as per same like what we use with old task for approval.

mapped the Form attributes

FORM do not save contains the value X for no to update the data. But still it updates directly when I initiated the process and workflow triggers and sent for approval.

[ChrisSolomon]

You mean your "FORM" workflow container value has "SUPRESS_SAVE" set as "X"? Ok....you need to be careful doing that as it overrides "SEND_VARIATION"....which may be ok depending on how you bind when you come to your actual "save" step/task.

What is set in config for your "process start"? If you have workflow doing your "save", you need to make sure "send variant" in the config of you process start is not set to "write data to application database" (else it will "save" as soon as you submit the form and THEN it will also kick off workflow).

Check that and report back.....that is about the only way I can think of that your process might be saving right now without going to your "approval".

[Former Member]

Yes, that SUPRESS_SAVE I set it as X in FORM i.e in container level. Even though I just checked by hardcoding the value in binding parameters.

ZHR_IN_TEST           00000X      &FORM&

Finally solved the issue changing the send variant value to Do Not Tolerant Error Messages in process level.

In debug, i observed that before workflow triggers that process Send Variant will trigger and save to database if option is selected Write Data to Application Database. And then it will trigger the workflow which will be sending for approval process as per workflow design.

[ChrisSolomon]

haha that's what I said above.....send variant in your process "start" config. Glad you got it worked out.