每次在UI上修改并儲存order進而 trigger 了action framework的某個具體的action處理之後（以Action profile ORDER_MESSAGES_WEC的action ORDER_STATUS_CHANGE為例），都會在table PPFTTRIGG裡生成一條對應的entry:
OS_GUID: 唯一辨別每次處理的guid
APPLKEY: 在此例子下為order ID
APPL_OID: 和APPLKEY是1:1關系
APPL_CLS: 5C01EBDE73C0AA4EA0C9B99A85BC49DF，對應APPLCTN的value CRM_ORDER
APPLCTN: application name, 在one order framework裡為常量CRM_ORDER
CONTEXT: action profile name
TTYPE: trigger type, 即action name
STATUS: 表明該action處理狀态: 0 - not processed 1 - successfully processed 2 - incorrectly processed
MEDIUM_OID: 唯一辨別每一次email sending process
MEDIUM_CLS: 37AE970776694BC4E10000009B38F9B7，代表email sending
TIMECREATE: action處理的timestamp
USERCREATE: trigger action處理的user
DISPATCH: action 處理方式. 1 - processing using selection report 3 - immediate processing 4 - Processing when saving document
PARTINDEP: 是否和partner相關
如果想debug 該table的update，可以打開debugger的update debugging:
在class CA_SF_MAIL_PPF~MAP_SAVE_TO_DATABASE裡設斷點:
在SM13裡能看到所有待處理的updating module: