@Kristene Vaughn
That's a very wrong and dangerous way to do it. If you do this in a generic service, it will update EVERY time the "check" event or operation is fired/triggered/called. To make matters worse....if the user does a "check" then goes back to change something and does "check" again, it will update yet again!!! It is better to do this via an Advanced/Enhanced Generic Service. The update will not actually occur until the "flush"....much like a regular LUW. Past that though, you should REALLY make use of the decoupled infotype framework.
In your example above, I see what you are trying to do. I would guess you are leaving off some important parts there from the config. Your operation above isn't actually doing anything by itself.
@Vijay
If you want to control "when" the updates are actually done, this is set through workflow binding on that task/step. You can have your form "pretend" to do an update without doing it at all for the purposes of checking/validating data or you can set workflow to say "when the form is done, save the data". It's all up to your workflow config (except with the NO_WORKFLOW undocumented option which ALWAYS saves)
@ All
This is very possible and well documented in the HCM P&F docs. For custom infotypes, you simply need to make sure they have been defined for the decoupled infotype framework (ie, have a "screen structure" associated and have been config'd in the decoupled IF section). This is VERY easy. Once done, you can simply add your infotype(s) into the HCM P&F config for operations (SAP_PA for example). I have done this a LOT and this is probably your safest/best way to do it. Again, if this is not possible or not meeting your needs, then (and only then) would I look at doing this in an Advanced Generic Service.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.