To view the properties of this process, select the process in the navigator tree, then choose Properties from the Edit menu. This process has a result type of Flexfield Result, indicating that when the process completes, it has a result of Failure or Success. These results correspond to the lookup codes in the Flexfield Result lookup type in the Standard Flexfield Workflow item type.
This process activity is not runnable, indicating that it cannot be initiated as a top-level process to run, but rather can be run only as a subprocess when called by a higher-level process.
The subprocess begins at node 1.
Node 2 checks if the destination type for the item is Shop Floor, Inventory, or Expense.
For shop floor items, node 3 builds the shop floor charge account. See: Summary of the Build Shop Floor Charge Account Subprocess. For inventory items, node 5 builds the inventory charge account. See: Summary of the Build Inventory Charge Account Subprocess. For expense items, node 9 builds the expense charge account. See: Summary of the Build Expense Charge Account Subprocess.
If node 9 successfully builds the charge account for expense items, the workflow does not validate the code combination right away. Instead, since you can enter your own charge account on the document for expense items, node 10 first checks if all segments were provided:
If so, node 12 uses the function attribute Generate Code Combination ID to generate the complete code combination identifier (CCID).
If not, node 11 uses the function attribute Validate Segment With Values Only to validate just those segments that were provided.
Nodes 6, 10, 11, and 12 are standard flexfield workflow activities. See: Standard Flexfield Workflow.