Algorithms Used in C1-WriteOffUploadRequest
The following table lists the algorithms which are used in the lifecycle of the C1-WriteOffUploadRequest business object:
Status | System Event | Algorithm | Algorithm Type | Description |
---|---|---|---|---|
Draft | Enter | C1-WO-DERIV | C1-WO-DERIV | This algorithm reads the BO_DATA_AREA in the request's primary table, derives additional data that is required for creating write off requests and inserts the records in C1_UPLOAD_REQ_DTLS table. |
Submitted | Enter | C1-UPLSUBENT | C1-UPLSUBENT | This algorithm is invoked when the user clicks the Submit button. It checks whether the approval is required for the upload request. If the approval is required for an upload request, the status of the upload request is changed to Approval In Progress. However, if the approval is not required for an upload request, the status of the upload request remains in the Submitted status. |
Submitted | Enter | C1-DEFERUPLD | C1-DEFERUPLD | This algorithm is invoked when the status of the upload request
is changed to Submitted or Approved. It checks whether the upload request must be processed in the real
time (i.e. immediately) or in the deferred mode (i.e. in the background).
If the number of valid records in the upload request does not exceed
the online record process limit, the system changes the status of
the upload request to Processing. However,
if the number of valid records in the upload request exceeds the online
record process limit, the system changes the status of the upload
request to Deferred Processing. It contains the following parameter:
|
Submitted | Monitor | F1-AT-RQJ | F1-GEN-BOMNJ | This algorithm transitions the current status to the specified
status. You can specify the status to which you want the business
object to transition in the following parameters:
At a time, you can specify value for either the Next Status or Next Transition Condition parameter. If you don’t specify any value for these parameters, the system will transition the business object to the default next status specified in its lifecycle. |
Approval In Progress | Enter | C1-UPLAPPENT | C1-UPLAPPENT | This algorithm creates a To Do using the To Do type specified in the upload request type. The To Do is sent to the appropriate users with the To Do role which is specified in the upload request type. In addition, a log entry is added when a To Do is created using the To Do type. |
Approval In Progress | Exit | C1-UPLAPPEXT | C1-UPLAPPEXT | This algorithm checks whether the approver is associated with the approval To Do role specified in the upload request type. If not, it does not allow the approver to approve or reject the upload request. In addition, it does not allow the submitter to approve or reject the upload request. |
Approval In Progress | Exit | F1-TODOCOMPL | F1-TODOCOMPL | This algorithm completes To Do entries that are created for the business object when the business object exits the given status. It finds and completes all open To Do entries where the business object’s primary key is defined as a drill key. However, if the Exclude To Do Entries From Auto Completion characteristic is defined for the business object, then the system does not automatically complete the respective To Do entry. |
Approved | Enter | C1-DEFERUPLD | C1-DEFERUPLD | This algorithm is invoked when the status of the upload request
is changed to Submitted or Approved. It checks whether the upload request must be processed in the real
time (i.e. immediately) or in the deferred mode (i.e. in the background).
If the number of valid records in the upload request does not exceed
the online record process limit, the system changes the status of
the upload request to Processing. However,
if the number of valid records in the upload request exceeds the online
record process limit, the system changes the status of the upload
request to Deferred Processing. It contains the following parameter:
|
Approved | Monitor | F1-AT-RQJ | F1-GEN-BOMNJ | This algorithm transitions the current status to the specified
status. You can specify the status to which you want the business
object to transition in the following parameters:
At a time, you can specify value for either the Next Status or Next Transition Condition parameter. If you don’t specify any value for these parameters, the system will transition the business object to the default next status specified in its lifecycle. |
Deferred Processing | Monitor | F1-AT-RQJ | F1-GEN-BOMNJ | This algorithm transitions the current status to the specified
status. You can specify the status to which you want the business
object to transition in the following parameters:
At a time, you can specify value for either the Next Status or Next Transition Condition parameter. If you don’t specify any value for these parameters, the system will transition the business object to the default next status specified in its lifecycle. |
Processing | Enter | C1-WO-PROC | C1-WO-PROC | This algorithm fetches the list of records that are in Validstatus for a given request ID and invokes the entity business object for creating the write off requests. If successfully processed, then the record status will be updated to Processed, otherwise the record status will be updated to Error and error details will be logged in the exception table. |
Processing | Monitor | F1-AT-RQJ | F1-GEN-BOMNJ | This algorithm transitions the current status to the specified
status. You can specify the status to which you want the business
object to transition in the following parameters:
At a time, you can specify value for either the Next Status or Next Transition Condition parameter. If you don’t specify any value for these parameters, the system will transition the business object to the default next status specified in its lifecycle. |