Interface: PROJ - Activity element Version 2022.00

For surcharges/deductions, AnsatzInt and AnsatzExt is always 0

SplittingNumber exists when a cost centre distribution is defined for a Project/Service. For the main entry the SplittingNumber is always 0. For the corresponding cost centre distribution entries the value is > 0. The field can never be manually filled out. Split entries can also not be edited. The SplittingNumber must always be filled out with 0. The exception being if someone wants to query exactly this cost centre distribution.

For a new entry the RecordNumber may/should be entered with 0 and for a modification of an existing entry with the corresponding number.

Please enter the project number.

Until version 2003
                  For non-approved entries, the field is 0. For approved entries, it is the number of the user who approved the entry.

                  From version 2004
                  Values greater than 0: User who approved the entry.
                  Value equal to 0: Entry not approved
                  Values less than 0:
                  0 = Not approved by instance 1
                  -1 = Approved by instance 1
                  -2 = Visa refused by instance 1

                  0 = Not approved by instance 2
                  -10 = Approved by instance 2
                  -20 = Visa refused by instance 2

                  0 = Not approved by instance 2
                  -100 = Approved by instance 2
                  -200 = Visa refused by instance 2

Number of the ABACUS user who last modified the record.

If the entry is invoiced (AbrTyp=3), PeriodeNr is the relation to the invoice table.

                  Invoice header:
                  NAB.DataSet = 2, NAB.AbrNr = PeriodeNr

                  Invoice item:
                  NAB.DataSet = 3, NAB.AbrNr = PeriodeNr, NAB.ProjNr = ProjNr, NAB.AbrCode = AbrCode, NAB.BuchArt = ...., NAB.RefNr = RefNr and NAB.SplitNr = SplitNr

Field for reference in external application

Entries from Project management:
See radiovalues
0 = Standard entry
1 = Revenue entry from invoice program
2 = Surcharges/deductions from invoice program
3 = Automatic entry from deadline control
5 = Entry from activity
10 = Holiday carry-forward from prev. year
11 = Holiday credit for current year
12 = Holiday correction
14 = Budget entry from payment plan. In this case, ProjNo = NPM.ProjNo, SeqNo = NPM.Budget and SamNo = NPM.ID
15 = Budget entry from rough planning
16 = Budget entry from detailed planning
17 = Entry generated with report proposal
18 = Entry generated by task. In this case, [Reference3] = Task ID
20 = Entries generated from project contract
21 = Entries generated by activity from project contract
22 = Booking entered on AbaClik 3 or higher
23 = Booking entered on MyAbacus with DeepBox recognition
24 = Flat-rate expense
25 = Manual flat-rate
30 = Entries generated by archiving program. In this case, [Reference1] = Archiving run number
31 = Flextime carry-forward
32 = Difference entry for time control
33 = Entry recorded in iPad
34 = Entry recorded in AbaClik
35 = Entry recorded in work report app
36 = Absence entry from the service schedule
37 = In&Out entry from the service schedule
38 = Entry from AbaPoint
39 = Entry from AbaUnit
40 = Contract link to contract with periodic invoicing
41 = Contract link to contract with invoicing at execution
42 = Correction entry from fee invoice. In this case [Reference1] = NAB.AbrNr and [Reference3] = NIV.VertragId
43 = Entry generated by E-Business
44 = Booking a time surcharge
45 = Booking a monetary surcharge
46 = Contract booking for a periodical. In this case, the [Reference1] = the periodical number.
47 = Booking created from a periodical. In this case, the [Reference1] = the periodical number.
48 = Booking a paid break
49 = Booking of an NCA surcharge
50 = Incident booking from the home administration. In this case [Reference1] = NHW.event [Reference3] = Resident entry no. and BelPosNr = NES.SetNr
51 = Precalculated incident booking from the home administration. In this case [Reference1] = NHW.event [Reference3] = Resident entry no. and BelPosNr = NES.SetNr
60 = Entry generated by allocations. In this case [Reference3] = NES.SetNr and [Reference1] = NES.EntryNr
70 = Entry generated by travel costs
80 = Entry generated by absence
90 = Holiday balance carried forward from the previous year
91 = Public holiday credit for current year
92 = Rest day balance carried forward WHA
93 = Rest day credit WHA for current year
94 = Time supplement carryforward
95 = Rest day carried forward
96 = AbaClock booking
97 = Booking an on-call lump sum from the AbaPlan
98 = Booking of an on-call flat rate from the difference booking
99 = Booking from Outlook integration


Entries from ORDE:
1 = Debit entry from ORDE purchase. In this case, BelegNr = BPO.LeiErfVerdNum (version 2001 or older)
2 = Debit entry from ORDE sales. In this case, BelegNr = DPO.LeiErfVerdNum
3 = Revenue entry from ORDE sales.  In this case, BelegNr = DPO.LeiErfVerdNum
4 = Debit entry from ORDE purchase. In this case, BelegNr = BPO.LeiErfVerdNum (from version 2002)
5 = Debit entry from ORDE purchase procurement costs. In this case, BelegNr = BPO.LeiErfVerdNum (from version 2002)

Entries from Account Payable
[Reference1] = KPS.FVbLfNr
[Reference2] = KPS.FVbLfDat
[Reference3] = KPS.FVbTrNr
Until version 2000:
  [Reference1] = GIK.SAMNRSL
  [Reference2] = GIK.BU_SEQGR
  [Reference3] = GIK.BU_SEQNR

Entries from Account Receivable
  [Reference1] = Digits 3 - 10 of document no. (Trunc(BelegNr / 100))
  [Reference2] = Digits 1 + 2 of document number (BelegNr - (Trunc(BelegNr / 100) * 100.0))
  [Reference3] = BelPosNr;
  For reposted entries, the fields [Reference1], [Reference2] and [Reference3] = 0

Entries from General Ledger
  [Reference1] = Journal reference, digits 1+2 letter, digits 3+4 year or 00, e.g. E04 is 0504 
  [Reference2] = Division
  [Reference3] = Entry number (REC)

Field for reference in external application

User who entered the booking

The comments are saved in table NTB.
                  Reference:
                  NTB.Prg = 11
                  NTB.Bez = RefNr

Warnings

Reference to ORDE order
                  Reference to SCM contract

Reference to ORDE order
                  Reference to SCM contract

Reference to ORDE order
                  Reference to SCM contract

Reference to ORDE order
                  Reference to SCM contract

Reference to ORDE order
                  Reference to SCM contract

Jobdetail von AbaBau

If an entry is rebooked, the reference number for the resulting entry/original entry is saved in the field.

Terms of employment of employee

If this date is filled in, the date is passed to the payroll.
                  This can be used when the date per the current month must be included in the G/L but per the older date in the payroll settlement.

Project Management stock entries trigger cross-divisional entries, the stock accounting creates the stock outgoing entry.

Time, when the record was last edited

User, who added the record