SAP FI Open Item Management Flag in Account Settings

Friends, earlier I discussed about Line item display flagin G/L account customizing. There is another flag called Open item management just above Line item display in the customizing of G/L accounts. At times, this flag can be a a source of confusion in terms of what will happen if this flag is checked or unchecked. Transaction to display G/L accounts customizing FS03 is the transaction through which we can view the customizing settings of a G/L account. The Control tab in FS03 will display the status of Open item management flag. The screen shot is shot is shown below :

Transaction to display Customers and Vendors accounts customizing Similarly, transactions FD03 and FK03 are used to display the customizing of customer and vendor accounts. You can yourself try to find Open item management flag in these in transactions. Well, you will not be able to find the flag. Even I cannot find it. In fact no once can!!! Because the flag doesnt exists for customers and vendors accounts . The catch is, customer and vendor accounts are Open item managed by default. Obviously because customers are your receivables and vendors are payables i.e you either have to pay (in case of customers) or receive(in case of vendors) and then perform clearing. Effect of checking Line item display flag If Open item management flag is checked for a particular G/L account then the line item containing that G/L account can be cleared. Remember that customer and vendor accounts are open item managed by default therefore customer and vendors line items are clearable by default. Please share your thoughts through comments. The easiest way to stay informed about everything on Tech2know is to go for at lease one of below options : Subscribe to my RSS feed / Subscribe by E Mail / Follow me on twitter /Become a fan on Facebook. Stay tuned for more.

SAP FI Line Item Display Flag in Account Settings

Friends, anyone who have ever worked or read SAP FI must be aware of Line item display flag. In this post I would be discussing about the affect of checking this flag. Transaction to display G/L accounts customizing FS03 is the transaction through which we can view the customizing settings of a G/L account. The Control tab in FS03 will display the status of Line item display; flag. The screen shot is shot is shown below :

Transaction to display Customers and Vendors accounts customizing Similarly, transactions FD03 and FK03 are used to display the customizing of customer and vendor accounts. You can yourself try to find Line item display flag in these in transactions. Well, you will not be able to find the flag. Even I cannot find it. In fact no once can!!! Because the flag doesnt exists for customers and vendors accounts . The catch is, customer and vendor accounts are Line item display enabled by default. You dont have the check any flag explicitly to make then Line item display. Effect of checking Line item display flag Its very simple. If Line item display flag is checked for a G/L account then during posting of an FI document, secondary index tables are also populated with the line item in which the account exists. Below are the secondary index tables which are populated during posting if the FI document have a G/L account which is manage as Line item display. Remember that customer and vendor accounts are line item display by default therefore secondary index tables are always populated with customer and vendor line items.

BSIS BSAS

Accounting: Secondary Index for G/L Accounts Accounting: Secondary Index for G/L Accounts (Cleared Items)

BSIK BSAK BSID BSAD

Accounting: Secondary Index for Vendors Accounting: Secondary Index for Vendors (Cleared Items) Accounting: Secondary Index for Customers Accounting: Secondary Index for Customers (Cleared Items)

So, if we post an FI document with 2 line items in which 1st one is customer item and 2nd is G/L account item. Assuming that the G/L account is Line item display enabled, items will be updated in below tables BSEG : Both line items will be populated. Obviously BSID : 1st line i.e customer line BSIS : 2nd line i.e G/L line. If we had vendor line instead of customer line then it would have populated in BSIK in place of BSID. The other tables, namely BSAS, BSAK and BSAD, are relevant when an FI documents are cleared and the process is called as clearing.

SAP Archiving Effect of selecting Retain account display balance in Post processing program for FI_DOCUMNT
Friends, those of you who are familiar with SAP archiving object FI_DOCUMNT, must have seen a flag Retain account display balance on the selection screen of post processing program SAPF048I. We have a small documentation available for this flag in F1 help. But, this flag causes a lot of confusion in terms of how the program will behave if we select this flag. The big question. One of the main confusion is, many a times you see in debugging that when you check this flag then program internally selects a secondary indexes pertaining to a fiscal year which you have not mentioned in selection criteria. For example, if you have given fiscal year as 2007 then also the post processing program SPF048I selects some records which pertains to fiscal year 2006 or even 2005.

Why this happens. Well, the answer is a bit tricky but simple. If you select this flag then post processing program will delete complete clearing transactions only. Well, whats the big deal in above line. This can be found in the documentation also Table BSAS : CoCd G/L Doc No. Year 0001 0234321 5100000080 0001 0234321 5100000082 0001 0234321 5100000090 2008 100001492 25.01.2010 . So, here is the explanation :

First of all, the most important point which one need to understand is that clearing can happen across fiscal years. Below is a simple example : Clrng 2005 2005 50 200Doc Clrng 100001492 100001492 date PK 25.01.2010 25.01.2010 Amt. 40 40 in LC 100 100

Quite simple. Document 100001492 which belongs to 2010 is clearing 3 documents pertaining to years 2005 and 2008. Now, if you run post processing program for company code 0001 and year 2008 with Retain account display balance then the program selects secondary indexes on the basis of company code and account and then group them on account, clearing document number and clearing date. The grouping will result in a complete clearing transaction i.e selection of all the secondary indexes with same clearing document. So, above set of 3 documents makes a complete clearing transaction for post processing program. And this is the reason because of which you may find that post processing program selects a secondary index pertaining to a fiscal year which is different from what you have specified on the selection screen. The above procedure is true for all BSA* secondary index tables. Thats it for now. I hope I was able to explain clearly, the effect of flag Retain account display balance on the selection procedure of post processing program. Last but not the least, either complete clearing chain gets deleted or none i.e if post processing program SAPF048I finds even one record that doesnt meet the deletion criteria then none of the record is deleted. Please share your thoughts in comments. The easiest way to stay informed about everything on Tech2know is to go for at lease one of below options

SAP Archiving Important Customizing for Archiving Object FI_DOCUMNT

Friends, some time ago I discussed SAP Archiving Procedure wherein one question remained unanswered regarding whether is it mandatory to perform Delete phase and then Storage. Is it possible to perform Storage first and then Delete phase? I am taking this opportunity to explain in brief the answer of above question and some other customizing settings of archiving objectFI_DOCUMNT. You can navigate to customizing settings of archiving object FI_DOCUMNT(any archiving object) by following below steps : 1) Transaction AOBJ. 2) Search for archiving object FI_DOCUMNT and double click on it. 3) Select Customizing settings from the options on left hand side of the screen. Following is the screen shot of customizing setting for FI_DOCUMNT.

Sequence Delete Before Storing : With this setting, delete phase is performed before an archive file is stored in storage system. Store before deleting : With this setting, first the archive file is stored in connected storage system and then delete program deleted data from database. For this, deleted program have to read archive file from storage system therefore flag Delete Program Reads from Storage System must be selected. Archive File Size Maximum Size in MB and Maximum Number of Data Objects These options pertains to archive write program. The write program reads data from database and write the same in archive file till one of these conditions is satisfied i.e either size of archive file reaches 25 MB or the number of data objects reaches 30000. Settings for Delete Program As the name suggest, these settings pertains to delete program Commit counter : This defines the number of data objects which delete program deletes in one single shot i.e delete program deletes data objects in the packages of 10 in current settings. Test mode variant : This is default variant for running delete program/phase in test mode. Production mode variant : This is default variant for running delete program/phase in production mode. Delete Jobs Not Scheduled : You have to run delete program/phase manually.

Start automatically : The delete program/phase will start automatically as soon as the write phase is finished. After event : You can set delete program/phase to run as soon as a particular even is triggered. Settings for Post processing program Production mode variant : This is default variant for running post processing program/phase in production mode. Start Automatically : Post processing program will start automatically as soon as delete phase completes. Place file in Storage System Automatically : If this flag is checked then the created archive file will be stored automatically in the connected storage system defined by Content Repository. Thats it for now friends. Please share your thoughts through comments. The easiest way to stay informed about everything on Tech2know is to go for at lease one of below options :