Hierarchy
⤷ BC-SRV-GBT-PPF (Application Component) Post Processing Framework
⤷ SPPF_CUST (Package) PPF: Customizing
Basic Data
Data Element | PPFDMRGTXT |
Short Description | PPF: Description of Summarization Technology |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | AS4TEXT | |
Data Type | CHAR | Character String |
Length | 60 | |
Decimal Places | 0 | |
Output Length | 60 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Summariztn |
Medium | 20 | Summarization Logic |
Long | 30 | Summarization Logic of Action |
Heading | 20 | Summarization Logic |
Documentation
Summarization logic
The summarization logic is the assigned logic that summarizes the found actions with existing actions. If a document is created, specific actions are found. These actions are assigned to the document and have been found because of the condition evaluation of the determination technology. If you change the document, the same actions (with unchanged data) are found again. The summarization logic is responsible for merging the existing actions with the newly found actions.
Until now, 3 standard logics have been delivered:
1. max. 1 action for each action definition
A maximum of one action of this type is generated in the document for each action definition. If an action of the same type has already been found, the system ensures that no further actions of this type are found.
2. Max. 1 unprocessed action for each action definition
There may be one unprocessed action of the relevant action type in the document. Therefore, if the action is unprocessed, it is not found again. If the action is processed, it can be found again and executed.
3. max. 1 unprocessed action for each processing type
Here there can additionally be an unprocessed action for each processing type of the action. If an action is in the condition configuration, for example the processing print or mail (order acknowledgment should be printed and sent by mail), there can be an unprocessed action for print and an unprocessed action for mail for this action type.
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in | 50A |