Projekt

Allgemein

Profil

« Zurück | Weiter » 

Revision 6418adee

Von Kivitendo Admin vor fast 9 Jahren hinzugefügt

  • ID 6418adee39dc8d7331df12b716096f0a8611ef5d
  • Vorgänger bce4bcf8
  • Nachfolger 4f43ec85

Typos und in SL/DB/Invoice.pm

Unterschiede anzeigen:

SL/DB/Invoice.pm
229 229
    my $chart = SL::DB::Manager::Chart->get_all(query   => [ SL::DB::Manager::Chart->link_filter('AR') ],
230 230
                                                sort_by => 'id ASC',
231 231
                                                limit   => 1)->[0];
232
    croak("No AR chart found and no parameter `ar_id' given") unless $chart;
232
    croak("No AR chart found and no parameter 'ar_id' given") unless $chart;
233 233
    $params{ar_id} = $chart->id;
234 234
  }
235 235

  
......
387 387

  
388 388
=pod
389 389

  
390
=encoding UTF-8
391

  
390 392
=head1 NAME
391 393

  
392 394
SL::DB::Invoice: Rose model for invoices (table "ar")
......
458 460

  
459 461
=item * C<ar_id>
460 462

  
461
The ID of the accounds receivable chart the invoices amounts are
463
The ID of the accounts receivable chart the invoice's amounts are
462 464
posted to. If it is not set then the first chart configured for
463 465
accounts receivables is used.
464 466

  
......
484 486
and recorded in C<acc_trans>.
485 487

  
486 488
=item 6. Items in C<invoice> are updated according to their allocation
487
status (regarding for costs of goold sold). Will only be done if
489
status (regarding costs of goods sold). Will only be done if
488 490
kivitendo is not configured to use Einnahmenüberschussrechnungen.
489 491

  
490 492
=item 7. The invoice and its items are saved.
......
493 495

  
494 496
Returns C<$self> on success and C<undef> on failure. The whole process
495 497
is run inside a transaction. If it fails then nothing is saved to or
496
changed in the database. A new transaction is only started if none is
498
changed in the database. A new transaction is only started if none are
497 499
active.
498 500

  
499 501
=item C<basic_info $field>
......
503 505
=back
504 506

  
505 507
=head1 TODO
508

  
506 509
 As explained in the new_from example, it is possible to set transdate to a new value.
507 510
 From a user / programm point of view transdate is more than holy and there should be
508 511
 some validity checker available for controller code. At least the same logic like in

Auch abrufbar als: Unified diff