Submission Package
This manual is in pilot operation.
|
Participants involved in a process submit the requested data. The data submitted at one time is called a "submission package". When there is no ambiguity, it may simply be referred to as a "package".
What kind of submission package a participant needs to submit is determined by the "Submission Package Definition" included in the process definition. In other words, the participant at the end of the submission route specified in each submission package definition is responsible for submitting the package defined in that package definition.
While the Submission Package Definition represents the type of package, a submission package represents the actual individual package data that has been submitted. Therefore, the relationship between a submission package definition and submission packages is one-to-many. For example, if there is a submission package definition called "Annual Expense Budget," a submission package would be "Annual Expense Budget for Department A for FY20xx, First Submission."
Submitting a Package
A submission package is generated by "submitting" it. The generated submission package retains the data that is displayed when the parameter values of the submission package specified in the submission package are applied to all forms included in the form list specified by the submission package[1]. Please note the following points:
-
A package cannot be submitted unless the status of the process is "In Progress".
-
If a package of the same type, that is, a package based on the same submission package definition, has already been submitted, please withdraw it or request the recipient to return it before submitting.
-
Columns and rows suppressed from display by the settings in Form Column Specification and Row Specification are considered displayed for the purpose of determining retained data.
-
Data that is not displayed due to access permission types of the participant is also considered displayed for the purpose of determining retained data.
-
All-period and all-display format data is retained for keys excluding the period and display format from the displayed data keys.
-
Actions on a Package
Once a package has been submitted, you cannot delete or change its contents, but the following actions can be performed.
To perform actions, the status of the process must be "In Progress".
Actions a Submitting Participant Can Perform
Withdrawal
Participants can withdraw their submission package before final approval by the recipient[2]. The withdrawn package itself is not deleted but remains as a history. By withdrawing, the same type of package can be submitted again. After final approval by the recipient, withdrawal is not possible, so please request the responsible person at the recipient to "return" it.
Actions a Receiving Participant Can Perform
Reception
The submission package is accepted. "Reception" has the following effects:
-
The accepted data is reflected in the ledger version of the workspace of the receiving participant. Therefore, the participant can freely query and analyze the data, such as comparing it with submission package data from other submitters.
Reception can be performed under the following conditions:
-
The previous recipient on the submission route has already approved the submission package.
-
The submitter has not withdrawn the submission package, and none of the recipients have returned the submission package.
Participants cannot query the contents of submission packages that are not receivable (i.e., not arrived yet).
⚠ The data reflected by reception is the data included in the writable ledger cell range in the submission package form by the submitting participant. For details on the determination of "writable," the following conditions apply.
-
Not only ledger cells that can be directly entered using the forms specified in the Submission Package Definition, but also ledger cells where the calculation results on the form are reflected are considered "writable."
-
For the application of various access restrictions, refer to "Process Management Functions and Access Control".
Approval
The submission package is approved. By approving, the submission package becomes receivable by the next recipient on the submission route (except when the approving participant is the final recipient).
Approval can be performed under the following conditions:
-
The participant has already received but not yet approved the submission package.
-
The submitter has not withdrawn the submission package.
Return
The submission package is returned. By returning, the submission package is returned to the submitter. In other words, the submitter can submit the same type of package again, that is, a package based on the same submission package definition. Note that the returned package itself is not deleted but remains as a history.
Return can be performed under the following conditions:
-
The participant can receive or has already received but not yet approved the submission package (however, the final recipient can return it even after approval).
-
The submitter has not withdrawn the submission package.
Reflection
The contents of the received submission package are reflected in the ledger version of the workspace of the receiving participant. This is the same content as the reflection process performed at the time of reception (described above). As a result of the withdrawal and return of the submission package, there may be cases where multiple submission packages are received. In such cases, reflection always reflects the contents of the previous submission package in the ledger version of the workspace.
Querying the Contents of a Package
The contents of a submitted package can be queried in one of the following ways:
-
Query from the workspace screen of the [Contributor].
-
Query using [Excel-Link]. To access the data of the submission package with [Excel-Link], a special "ledger version key" is used. Refer to Ledger Data Edition Management for details.
In either case, only the submitting participant and the participant who can receive or has received the relevant package can query it.