Why archving work itmes?

[Former Member]

Hello,

archiving messages (BC_XMB)makes sence, but for archiving workitems (BPM) I can't see an business case.

Any ideas or comments.

Regards,

Geert

[Former Member]

Hi,

After the Enron's problem in USA, in some countries, you need <u>to keep legally ALL steps</u> used by a software to transforma data during a sending of financial and accounting data. This is the <b>Sarbanes-Oxley law.</b>

http://www.sarbanes-oxley.com/

http://news.com.com/HiddenfraudriskinSarbanes-Oxley/2100-1002_3-5602776.html

And as inside a BPM, you transform, split, merge data in several steps (for instance by using three Interface Mapping), you need to keep/archive them! Not all your BPM (work item), but only ones which are under this law.

Here's the only one reason I see...

Regards.

Mickael

[Former Member]

Hello Mickael,

in fact we have to archive all steps because of SOX requirements. But all transforming/mapping is done outside of the BPM (abstarct interfaces), which is covered by BC_XMB

Archiving. So I can't see an BPM step which as impact to the data which is not covered by the BC_XMB.

Regards Geert

[Former Member]

Hello All,

I heard that sending an Idoc within a BPM will not cause a persistance (as BC_XMB) entry. Is this true? Because all of the other adapter/message types do this.

Regards,

Geert Engelhardt