Show TOC

 Example: Merging of Account Assignment Rows

The following graphic illustrates how the system merges account assignment rows:

Note Note

The example illustrates the weekly data entry period from October 14 through October 20. It is assumed that October 19 and 20 (Saturday and Sunday) are days off. Therefore, they are not shown in the example.

End of the note.
Scenario 1: Rows can be merged

  1. You enter three account assignment rows for the data entry period October 14 through 20. The account assignment information is identical in the first and third rows.

  2. In the first account assignment row, you enter three hours for October 14 and five hours for October 16.

  3. In the third account assignment row, you enter four hours for October 15.

  4. You exit time recording and call up the data entry period again.

  5. The system sorts the account assignment rows in ascending order according to the date and time for which they were entered.

  6. The system checks whether the account assignment rows can be merged:

    a. It determines that the account assignment information is identical in the first and third rows.

    b. It checks whether the fields that are filled with working times in the first account assignment row are blank in the third row. This is the case.

    c. It checks whether the fields that are filled with working times in the third account assignment row are blank in the first row. This is the case.

    The system merges the first and third account assignment rows into one.

Scenario 2: Rows cannot be merged

  1. You enter three account assignment rows for the data entry period October 14 through 20. The account assignment information is identical in the first and third rows.

  2. In the first account assignment row, you enter three hours for October 14, two hours for October 15, and five hours for October 16.

  3. In the third account assignment row, you enter four hours for October 15.

  4. You exit time recording and call up the data entry period again.

  5. The system sorts the account assignment rows in ascending order according to the date and time for which they were entered.

  6. The system checks whether the account assignment rows can be merged:

    a. It determines that the account assignment information is identical in the first and third rows.

    b. It checks whether the fields that are filled with working times in the first account assignment row are blank in the third row. This is not the case.

    You have entered working times for October 15 in both account assignment rows. The system does not add the two values because there may be different cell information (such as the processing status or follow-on documents) linked to them, which would be lost if the rows were merged. For more information, see Follow-On Documents and Outstanding Postings .

    The system cannot merge the account assignment rows.