Professional Documents
Culture Documents
03 0 TRM PSCD Trans and Acct Determ
03 0 TRM PSCD Trans and Acct Determ
Introduction Interests
Documents Correspondence
Specific Posting Processes Integration Accounting
Payments and Clarification Invoicing
Dunning
SAP AG 2008, Public Sector Collections and Disbursements / Transactions / 1
1
Transactions and Account Determination
2
Transaction and Account Determination: Unit Objectives
3
Transactions and Account Determination
Structure of Transactions
4
Document Structure
Doc.Header
Document number
Reconciliation key
Document type
Currency
Document date
BP-Item(s) Posting date GL-Item(s)
Company code … Company code
Business partner Classification key GL-Account
Contract account Amount
Reconciliation account Main & sub transaction
Amount ...
Due date
Main & sub transaction
Contract Object
FM-Accounts
...
Documents consist of header data, items for contract accounts, and items for G/L
accounts. In addition to the unique document number, the header data also
contains the document type as the classifying attribute, the currency key, and
various date specifications.
When posting manually, event 1119 can be used to create error messages prior to
‘posting’ the document. This allows the user to correct the document prior to
posting.
The attribute Classification Key can been added to the PSCD document and the
request (see chapter: Specific Posting Processes). The classification key provides
a similar function to the reference number, but allows keys with a length of up to
35 characters.
The classification key is an enhancement supported in the system. This means
that the attribute is not initially active in the system delivered; you have to activate
it explicitly in your installation.
5
Clearing open items
FI - GL Account FI - GL-Account
Property
Property Tax
Tax Contract Account Bank
Bank
100,-- (1) (2) 100,--
C.
C. Lear
Lear
(1)100,-- 100,-- (2)
Doc. Header
DFKKKO
Invoice 123 Doc. Header
BP-Item DFKKKO
DFKKOP Payment 456
100,-
For the payment, all the fields that are redundant or can be reconstructed another way are
omitted from the data of the payment.
The result is a physical record that only contains a few more attributes than the original
business partner line item (DFKKOP).
This physically stored record with its data represents both an item in the invoice
document and an item in the payment document.
6
Clearing open items (partial clearing)
FI - GL Account FI - GL-Account
Contract Account
Property
Property Tax
Tax Bank
Bank
100,-- (1) C.
C. Lear
Lear (2) 60,--
(1)100,-- 60,-- (2) (3) 10,--
10,-- (3)
The posted documents do not retain their status. Under certain circumstances, document
changes and clearing of open items sometimes require that the document is saved in a
different physical form.
The split is required if a partial amount of the open item is cleared. An entry in Business
Partner table is split into two entries; the open portion and the cleared portion.
For the new sub-items, you also want to be able to recognize later that they arose from
one original item. In order to achieve this, an additional key field is introduced into the
Business Partner table: the sub-item number (OPUPZ).
7
Determining GL Accounts I
Header
BP-Item 1 GL-Item 1
BP-Item 2 GL-Item 2
... ...
BP-Item n GL-Item n
Customizing
Account
Customizing determination
Account
determination
8
Posting Areas
1
2
3
Perform:
Simulation
SAP AG 2008, Public Sector Collections and Disbursements / Transactions / 9
In many contexts the system has to derive accounts or other data. The derivation
is maintained in a so-called posting area. For all derivations you use the same
technical tool. You can see and maintain all posting areas with transaction FQC0
or the relevant menu path in the IMG.
You can always enter several derivation rules. If you do not see the list view at
first choose the menu path GOTO SELECT KEYS.
Access Sequence: As standard, the system first attempts to impart an entry with
recourse to all used key fields. If this does not work, the last key field excluded at
the next attempt. At the last attempt, only the first key field value is used. You can
change this standard procedure with user-defined access sequences. To do this,
you define:
Which of the possible key fields are relevant for the determination of the G/L account
In which order the system uses your key field definitions for the determination of the G/L
accounts
Test your customizing by clicking on „simulation“. There is also an error analysis if
the derivation was not possible.
9
GL Account Determination II
* * * 140099
10
Assigning External Main and Sub Transactions
Internal transactions are those transactions which take place within PSCD. The
main examples of these transactions are charges, interest, payments on account,
clarification postings, etc. These main and sub transactions thus serve to provide
parameters needed for the posting of these ‘internal’ transactions.
NOTE: Each entry delivered in this table must be assigned to an ‘ID’ by the
customer, regardless if the customer chooses not to rename the transactions (i.e if
the customer wishes not to rename the entry for main transaction 0010 sub
transaction 0100, then he must place identical entries in the space for external
assignment).
These internal transactions are hard-coded. Do NOT delete them.
Parameters are set for the main and sub transactions (due date to be used when
posting with these main and sub, withholding tax rule, and any additional
receivable rule).
Main and sub transactions are used to identify items based on their type (I.e.
interest, charge, etc) as well as the business process from which they originated
(payments, account statements, etc.). This controls account determination and
the flow of application-specific processing programs. This function links each item
with a main transaction to which several sub-transactions are assigned. For
example, there is a main transaction ‘charges’ and associated sub-transactions
‘dunning charge’, ‘return charge 1’, ‘return charge 2’, ‘correspondence charge’,
‘installment plan charge’, etc…
11
Maintain Main and Sub Transactions
A user is free to define new entries in this table for use for transactions not defined
as ‘internal’ to PSCD. These additional main and sub entries can be used in
general ledger account determination.
+/- sign: You choose between “not specified”, “negative amount”, “positive
amount”.
Additional receivable: This is for identifying a process as an additional
receivable. An additional receivable is one which refers back to another
receivable, for example, dunning charges and interest. In many cases, additional
receivables should not be dunned/have interest calculated on them on their own.
An item (main receivable) that is not indicated as being an additional receivable,
can have interest calculated on it and can trigger a dunning letter if no lock has
been set for it. You can set the exact characteristics of the additional receivable
depending on the operational company code. In the simplest case, it is enough to
define one rule for additional receivables.
All postings in PSCD contain information on the business transaction in the main
and sub transactions. You can assign additional attributes to the transactions in
Customizing. These attributes are copied in the business partner item when the
posting is made and can influence the following business transactions (dunning
procedure etc.).
12
Transactions and Account Determination
Structure of Transactions
13
Posting Areas: Definition
The posing areas are broken down into the following areas:
Posting areas for all application areas (for example, posting area used to identify a tax account
based on the tax code)
Posting areas for more than one application area (for example, posting area used to determine
the default values for incoming payments). You can make a number of different specifications
for each application area.
Application-Specific posting areas -> prefixed by the letter from the application area
The active application area is defined in the user parameters and/or by selecting
the application area.
Transaction FQCR: Select and output data from account determination.
You can use this report to select and display account determination data from any
posting area. In the list, you can use functions such as find, sort and total. If you
select the entry, the system branches to display screen. You can maintain the
entry by selecting display -> change.
If you enter a search value, you can use the report, for example, to find what
Customizing entry an automatically posted general ledger account was
determined from.
14
Account Determination: Receivables Account
(Receivables)
Contract account/
Contract
Account
Company code 0001
Division - Determination
Account
determination ID 01
The system determines the main transaction during business partner processing
based on the internal transaction and its allocation to a defined transaction.
The account determination ID controls determination of the receivables account in
FI-CA (together with the main transaction that resulted from the business
transaction). The company code and, potentially, the division are further criteria.
The same receivables account is determined when identical business transactions
occur for contract accounts that have the same account determination IDs.
You can use different account determination IDs to access different receivables
accounts in general ledger accounting.
15
Account Determination: Revenue Account
The account determination ID is determined from the contract account for cross-
contract business transactions, or from the contract for contract-related business
transactions.
The subtransaction is also required for the revenue account determination
This enables you to allocate different revenue accounts to one business
transaction (main transaction) by defining special subtransactions. It is also
possible to allocate different revenue accounts for each company code and
division.
16
Transactions
Allocation to internal
transactions
SAP
Main Internal
transactions Main
transactions
Allocation
SAP
Internal
Sub- Sub-
transactions Transactions
transactions
Attributes Default setting
Account Determination
- Debit/credit by SAP
Additional account
- Interest key
assignment
- Statistical/non-statistical
17