Lawson Insight Technical Documentation

Generated by:
Documentation generated by Decision Analytics

ERDs Tables Conditions Elements Libraries APIs Forms

AC190


AC190 - Activity Posting



Run Activity Posting (AC190) to post transactions to Project Accounting.


**Processing Effect

The program posts released journal entries created in Project Accounting (on
AC40.1, AC41.1, and AC42.1), imported from a non-Lawson application (using
AC540), or transferred from other Lawson software applications. AC190 updates
activity balances and calculates billable and revenue amounts based on the
billing and contract setup.
The program changes journal entries to a posted status. The date you
enter in the Post Thru Date field is the date through which activity
transactions
are posted. The Update field determines whether AC190 is run for update or
edit.
Use the Post Acct Unit Balances option to update accounting unit and
resource balances if necessary. Selecting Y in this field has the same impact
as running Accounting Unit Balance Post (AC191).


**More Information

You can choose from a variety of selection options or filters. You can
select transactions for posting by activity group or activity group list,
activity, activity list, system code, or source code. You can also select
by system code together with source code. Or you can combine an activity
group,
an activity, or an activity list with a system code, a source code, or both
a system and a source code.
When you run AC190, the currency routines are used to calculate the
two report currency amounts from the transaction amount.
You can inquire on released (unposted) and posted transactions using
AC96.1 (Transaction Analysis). You can edit transactions in error using AC45.1
(Activity Transaction Edit).
If AC190 receives transaction from Received, Not Invoiced Report (PO135),
and those transactions are related to a contract with Exclude Unpaid AP set
to Yes (on BR10.1), AC190 will set those transactions' related billable flags
and fields to non-billable. Those transactions are then not available for
billing in Billing and Revenue Management (BR). The same logic is applied
to any burden transactions created from the PO135 transactions. This
functionality
is used primarily by Grant Management users who cannot bill a grant
organization
for expenses for which they have not yet paid.



Updated Files

    ACACTIVITY -

    ACBRDNADTR -

    ACBRDNTRAN -

    ACCOMMIT   -

    ACCOMMITX  -

    ACMONITOR  -

    ACTRANS    -

    ACTRANSEG  -

    ACTRANSGL  -

    ADDRDATA   -

    CKPOINT    -

    IFMONITOR  -

    MXELEMENT  -

    MXLISTHDR  -

    MXLISTMBR  -

    SUBCKPOINT -

    SYSTEMCODE -


Referenced Files

    ACACCTCAT  -

    ACACCTCATX -

    ACACRESRT  -

    ACACRESRTX -

    ACACTGRP   -

    ACACTMXVAL -

    ACACTSEG   -

    ACADDLCNTR -

    ACAMCODE   -

    ACASNROLE  -

    ACASSIGN   -

    ACBILL     -

    ACBILLX    -

    ACBLRATE   -

    ACBLRATEX  -

    ACBRDNBLRX -

    ACBRDNDTL  -

    ACBRDNHDR  -

    ACBRDNPLX  -

    ACBRDNPRRX -

    ACBRDNTYPE -

    ACCAL      -

    ACCALX     -

    ACCATGRP   -

    ACCATGRPX  -

    ACCATMXVAL -

    ACCATSUM   -

    ACCATSUMX  -

    ACCNTRACT  -

    ACCTRCATGX -

    ACCUAMT    -

    ACCUSTOMER -

    ACGLCODE   -

    ACGRPMXVAL -

    ACIFACTV   -

    ACMASTER   -

    ACMXVAL    -

    ACRESRT    -

    ACRESRTX   -

    ACROLE     -

    ACSTATUS   -

    ACUOM      -

    CUCONV     -

    CURELAT    -

    EMPLOYEE   -

    GLADDRESS  -

    GLCHART    -

    GLINTCO    -

    GLNAMES    -

    GLSCCAT    -

    GLSRCCODE  -

    GLSYSTEM   -

    GMAWARD    -

    INSTCTRYCD -

    MXCATDEF   -

    MXLISTDTL  -

    MXOBJCAT   -

    PGEMPLOYEE -

    STRUCTURE  -

    WFSETUP    -


INVOKED Programs

    ACAC
    ACTA
    API4
    IFAC
    IFCU
    IFOB
    IFSG
    SLSE
    SLSU
    IFLU
    IFUP
    ACDR
    ACSR
    IFFC
    IFGT
    GLCC
    IFAU
    IFRS
    IFSC
    SLSB
    SLSS
    IFIM
    IFJR
    SLFD