Reverse Postings

Information

• A reverse posting is a posting which cancels out another posting. I.e. a reverse posting is identical with the original posting in all parameters (project, task, date, cost type), actual load is equally high but negative.
  • In PLANTA, postings or posting records are load records with actual data (actual hours, actual costs, and actual revenues).
    • Load records are records on the lowest planning level of the project. In these records, planned (Remaining) or recorded (Actual) hours worked/costs of the task resource are deipslayed per time unit, e.g. day or month etc. For more information see the Schedulemodule.
• In particular cases, reverse postings must be recorded in PLANTA project since the deletion/correction of already recorded actual dates is prevented by the PLANTA software (standard). This is the case if the following or one of the following parameters are set:
  • Approval
  • SAP status
  • Imported on or Imported by

Reason

• In the above mentioned cases, the prevention of deletion is necessary, e.g. to
  • avoid the differences between target and source system after transfer to or import from an external system.

Details

• In PLANTA Standard, automatic reverse postings are used. This means that reverse postings are created invisibly in the background upon deletion/correction of actual postings the deletion/adjustment of which is technically forbidden.
  • The new function now also offers an option to create reverse postings for postings before or on the key date, which virtually softens up the fixed key dates but with the advantage that incorrect postings can now generally be corrected. Whether these options should be used is an individual decision which brings about both advantages and disadvantages.
• If automatic reverse postings are not to be used for particular reasons, reverse postings can also be created manually. PLANTA, however, expressly advises you to use automatic reverse postings to minimize possible error sources.

Caution

• The above mentioned cases deal with the deletion of values in load records.
• This is to be differentiated from the deletion of entire posting records. Although it is technically possible, PLANTA expressly advises against it (with a few exceptions)
  • since it is not intercepted by automatic reverse postings
  • since the mechanism of prevention, as described above, does not take effect here and the deletion of load records thus leads to inconsistencies upon transfer to external systems
  • since it furthermore influences the calculation of the Remaining values. For details, see here

Principle

How do reverse postings work?

• Regardless of how reverse postings are created (manually or automatically), they are based on the same principle.
• Depending on whether the load value of the posting is deleted or whether the load value, the cost type, or the date is changed, there are 2 or 3 records (in the case of automatic reverse postings they are in the background):

• Deletion of the Actual load value of the posting

• Adjust the Actual load value of the posting, e.g. from 5 to 4

• Adjustment of the cost type or of the date of the posting
  • For automatic automatic reverse postings, this case is only supported from DB 39.5.14.

Automatic Reverse Postings

Information

• From version DB 39.5.13, it is possible to set the recording of reverse postings (negative postings) to "automatically" and to define in which case automatic reverse postings are to be created. This is controlled via the global Reverse posting variant parameter.
  • If the automatic creation of reverse postings is activated, the respective reversal values are displayed in the background when deleting/changing actual values (if the condition defined in the global parameter is applicable) and do not have to be recorded manually.
  • If the automatic creation of reverse postings is deactivated, reverse postings must be created manually as in previous versions.
  • Automatic reverse postings only take effect when you delete/change actual load values, however, they do not take effect when you delete all posting records.

Procedure for activated automatic reverse postings

• Actual hours in the Time Recording module
  • depending on the time recording variant used, either delete/change the required value directly below the time scale or in the respective load record in the Actual field
• Actual costs in the Post Costs module
  • delete/change the value in the required record in the Actual costs field.
• Actual revenues in the Post Revenues module
  • delete/change the value in the Actual revenues field in the required record.

Details on Automatic Reverse Postings

When are automatic reverse postings created?

• Via the Reverse posting variant global parameter you can control when automatic reverse postings are to be created (Bitflag):
  • 0: deactivate automatic reverse postings
  • 1: automatic reverse posting for exported loads ( SAP status = set)
  • 2: automatic reverse posting for approved loads ( Approval = set)
  • 4: automatic reverse postings for loads before the key date (if load date <= key date )
  • 8: automatic reverse postings for imported postings (Imported on or Imported by set or if there is a record in the pulse table in which PLANTA ID = UUID from DT472)
  • 15: Automatic reverse postings for all above mentioned cases.
• The parameter is a bitflag.
  Show overview of possible combinations

  value	Export	Approval	Key date	Import
  0	-	-	-	-
  1	x	-	-	-
  2	-	x	-	-
  3	x	x	-	-
  4	-	-	x	-
  5	x	-	x	-
  6	-	x	x	-
  7	x	x	x	-
  8	-	-	-	x
  9	x	-	-	x
  10	-	x	-	x
  11	x	x	-	x
  12	-	-	x	x
  13	x	-	x	x
  14	-	x	x	x
  15	x	x	x	x

  
  

Caution

• When you use the 4, 5, 6, 7, 12, 13, 14, 15 setting, the effect of the Key date performance parameter will be canceled out. Data can be created manually before or on the key date and already existing postings can be corrected or deleted (e.g. incorrect ones). Reverse postings are then automatically created for them, so that the changes can also be traced before the key date.

Traceability of Reverse Postings

• In the following modules, the project or department manager can view the reverse postings as well as the canceled records for analysis purposes.
  • Project manager
    • Progress
    • Check Reported Hours
  • Department manager
    • ICA
    • Actual hours
• Both reverse posting records (canceled postings and reverse postings) are differentiated from other records by a traffic light (the same as for completed tasks in the schedule).

Details

• Since reverse postings are saved in DT472 Load just like regular postings, you can filter them out in individual modules via the Reverse Postings parameter if you do not want to have them displayed.

Manual Reverse Postings

Information

• Manual reverse postings are recorded for deactivated or non-existing (up to DB 39.5.13) automatic reverse postings (for examples, see the "Principle" chapter).

Procedure in the Time Recording, Post Costs, and Post Revenues modules.

• Actual value is to be deleted
  • Insert a new record below the load record to be canceled and set all values except Actual load/Actual costs/Actual revenues as in the original record.
    • Enter the same value as in the original record with a minus symbol in the Actual load/Actual load/Actual revenues field.
• Actual value is to be deleted
  • Insert a new record below the load record to be canceled and set all values except Actual load/Actual costs/Actual revenues as in the original record.
    • Enter the same value as in the original record with a minus symbol in the Actual load/Actual load/Actual revenues field.
  • Insert another record and set Actual load/Actual costs/Actual revenues like in the original record.
    • Enter the new cost value in the Actual load/Actual costs/Actual revenues field.
• Cost type or date is to be changed
  • Insert a new record below the load record to be canceled and set all values except Actual load/Actual costs/Actual revenues as in the original record.
    • Enter the same value as in the original record with a minus symbol in the Actual load/Actual load/Actual revenues field.
  • Insert another record and set Actual load/Actual costs/Actual revenues like in the original record.
  • Enter the required new cost type or date value.
    • If a new parameter is only entered for one of the two parameters, the other value will remain the same as in the original record.