fico Clarifications Regarding Holding, Parking, Recurring, Documents

Parking Doc:

You can use document parking to enter and store (park) incomplete documents in the SAP System without carrying out extensive entry checks. Parked documents can be completed, checked, and then posted at a later date - if necessary by a different accounting clerk.

When documents are parked, data (for example, transaction figures) is not updated. The only exception to this is in Cash Management (TR-CM).

Holding Doc:

When you are entering data, you may be interrupted, or you may not have all the data you need for entering a document, for example bank charges or the appropriate cost center.

In this case, you can temporarily save the data you have entered, and then continue with the document entry at a later time. If you want the system to hold a document, it does not have to be complete. Account balances are not updated and the document data is not available for evaluation. A document number is not assigned.

Recurring are those which fall frequently e.g rent, insurance. While creating recurring document you need to mention whether it will fall monthly and so on.

Tips by: Vaibhav

Add on to what Mr Vaibhav has said:
Recurring Document is created when the date is fixed and the amount is fixed. Example rent, Hire purchase instaments etc.
Assigning batch input session name. When you process, say 1st of every month then all these entries will be posted automatically. To say each time you need not have to post it filling all the fields.

Parking of Document: If a junior accountant has been given the task of posting. He may make few mistakes and therefore to plug this pitfall,parking is required. The senior level manager can make the changes, correct it and then release it. Once the senior manager approves the updation takes place and untill then the records are not updated.

Hold Document: Temporary document.
Deletion is possible.
No record after deletion.

sap Configuration For Cash Journal

What are the configuration for Cash Journal?

by Mohammed Ziauddin

Cash Journal:
IMG/FA/BANK A/C / BUS TRANS/ CASH JOURNAL

- Create GL a/c for Cash Journal – Ensure post automatically is on, so that posting can take place automatically. [ 100000 Petty Cash A/c ]

- Define doc types for Cash Journal Docs - SK [other doc types SA GL, DZ Customer Receipt, KZ Vendor Payment] [ OBA7 ]

- Define No range & interval for Cash Journal documents [ FBCJC1 ] - copy from 0001.

- Setup cash journal : [ FBCJC0 ]
Give a Cash Journal Code
Various code for GL A/c’s, Customers, Vendors.

- Create, Change, Delete Business Transactions [ FBCJC2 ] : These tran types can be copied, but as they are linked to GL a/c’s, change as reqd. These can be accessed at FBCJ.
C receipts from bank GL a/c -------
B payment ot bank GL a/c --------
R Sales

For vendors & Customers, GL a/c’s need not be given, as they will be different for A/P, A/R.

- Setup Print params [ FBCJC3 ]– copy from 0001, output device – LP01.
- Posting - SAP/A/c/FA/GL/Doc Entry - Cash Journal Posting FBCJ

Integration FI with MM

Integration of SAPFI with MM is done at OBYC.

Let me elaborate... In MM you purchase goods and to which you pay, the purchasing process has the following steps:

Step1: First you send a Purchase Order to the Vendor.

Here there won't be any accounting entry as this is simply like telling the Vendor what goods you want, its quantity and the date of delivery etc.,

Step 2: You will receive the Goods to the Purchase Order.

When you receive Goods you CAN NOT make the following entry

Inventry A/c Dr

To Vendor A/c

because, some of the goods you have received may be damaged or may not be upto the mark or for any other reason goods may reject, so befor posting it to Vendor A/c we keep it in separate place till we verify the goods. And the actual entry will be

Inventry A/c Dr (Transaction Key
BSX @ OBYC)

To GR/IR A/c (Transaction
Key WRX @ OBYC)

Here the goods received is Debited to inventry and Credited to a temperary A/c i.e., GR/IR a/c

Step 3: You will post a Invoice to the Goods received.

Here you will post the invoice after you are satisfied with the goods received, the entry will be

GR/IR A/c Dr

To Vendor A/c

Now the goods are moved from GR/IR A/c and Vendor is Credited. Now you got the final entry of Goods to Vendor Account i.e,

Inventry A/c Dr

To Vendor A/c

i.e, Inventry A/c was Debited and Vendor A/c was Credit and GR/IR A/c is Dr and also Credited henced its balance became 'Zero', and it has to be Zero always.

Step 4: And make Payment to Vendor.

Vendor A/c Dr

To Bank Clearing A/c

What is "Real Time" Integration?

What is "real time integration" advantage of SAP?

What is the Config for Integration entry? How these entries get formulated in backend?

Real time integration is nothing but the data posting to all the affected areas instantly when an activity is performed. For E.g. When you do a FI-SD integration, when a PGI is posted, the following entry is affected :

1. Cost of Goods Sold Dr 100
To Inventory Account Cr 100

Here the Cost of Goods Sold is an FI entry and Inventory Account related to MM but both of them gets affected immediately when you post a PGI in SD.

The updation of these entries when PGI is done is called Real Time Integration. The affect is shown in all FI, MM and SD modules once you save the entry.

The configuration for the below entry is done in OBYC

1. Cost of Goods Sold Dr 100 (T-Key GBB)
To Inventory Account Cr 100 (T-Key BSX)

The automatic entries are posted to inventory accounts through T-keys to which GL accounts are assigned. These T-keys are assigned to movement types in MM. Please refer to T-code OMWN and OMWB for proper understanding.