Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
FS (Application Component) Financial Services⤷
FS_PSJ_CORE (Package) Core Functionality for Process Step Journal
Basic Data
| Data Element | PSJ_TRANSMISSION_STATE |
| Short Description | Aggregated Process Step Status |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PSJ_TRANSMISSION_STATE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | AggrStatus |
| Medium | 15 | AggPrcStepStat |
| Long | 20 | Agg.Proc.Step Status |
| Heading | 20 | Agg.Proc.Step Status |
Documentation
Definition
Specifies in the process activity overview which processing status of a message that is transferred from one process component to another during asynchronous communication. This corresponds with the aggregated process step status and includes the values: Being Processed, Received, Error in Content , and Obsolete .
Use
The Process Step Journal derives the aggregated process step status for each process step from the log entry for a message or process step ID that was chronologically the last to be generated. To do so, it uses the following entries for all existing process activity logs for each process step:
Dependencies
The following describes which aggregated process step status the Process Step Journal can derive from the specification for the log entries that were the last to be created (seen chronologically) :
System Activity Category Activity Status Aggregated Process Step
1) Sender Service Call started Being Processed
2) Service Call unsuccessful Error in Content
3) Error processing started Being Processed
4) Error processing unsuccessful Error in Content
5) Error processing completed Obsolete
6) Event started Being Processed
7) Event completed Obsolete
8) Recipient Service Call unsuccessful Error in Content
9) Service Call completed Recipient
10) Error processing started Being Processed
11) Error processing unsuccessful Error in Content
Explanation of the Table Entries
For 1) The sending system has sent the service message to the receiving system or to Process Integration (PI).
For 2) The sending system could not send the service message.
For 3) Errors occurred during sending of the service message. Therefore, the sending system first transferred the service message to the Error and Conflict Handler.
For 4) Error handling failed on the sender side. The sending system could not send the service message.
For 5) The sending system encountered an error while attempting to send the service message. The message could not be sent. A processor has completed error handling manually.
For 6) Events (change pointers) that did not lead to a service message being sent exist.
For 7) Events (change pointers) that did not lead to a service message being sent were processed.
For 8) The receiving system cannot process the service message it has received due to an error in content.
For 9) The receiving system has processed the service message.
For 10) The receiving system transferred the service message to the Error and Conflict Handler.
For 11) Error handling failed on the receiver side. The receiving system cannot process the service message it has received due to an error in content.
For more information, see the SAP Library for SAP for Banking on the SAP Help Portal under http://help.sap.com -> SAP for Industries -> Banking Services from SAP -> Foundation (FS-FND) -> Process Step Journal.
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 300 |
