Understanding Building Transaction Master Business Functions
These flowcharts illustrate how transaction master business functions are built.
First, you create the individual business functions using several basic components:
![Building transaction master business functions](images/build_trans_mbsfn.gif)
Next, you combine the business functions into a DLL:
![Combining business functions into a .DLL](images/comb_bsfn_dll.gif)
You typically use these basic components to create a master business function as described by this table:
Component |
Purpose |
---|---|
Begin Document |
Called when all header information has been entered. Creates initial header if it has not already been created. Can also include default values, editing, and processing options (POs). |
Edit Line |
Called when all line information has been entered. Creates cache for detail information if it has not already been created. |
Edit Document |
Called when ready to commit the transaction. Processes any remaining document edits and verifies that all records are valid to commit. |
End Document |
Called when you need to commit the transaction. Processes all records in the header and detail cache, performs I/O, and deletes caches. |
Clear Cache |
Called when you are ready to delete all cache records. Deletes header and detail cache records. |