Data Migration of FI-CA Cleared Items

Hi,
Currently I am working on a Data Migration project to migrate data from our FI-CA module on ERP 4.7 to ECC 6.0.
THere has been a request from the business to migrate historical data (e.g. Cleared items).
Is there a SAP recommended approach or tools to load this data into the target environment?
Currently all documentation around SAP data migrations talks about stategies for open item data migration however I have seen nothing arouund migrating historical financial data.
Is this because it is not recommended or technically impossible?
Regards
Adam Gunn

That BAPI is used typically for straight out vanilla GL, AR, AP postings, however you still have to create the other side of the entry and then clear it.
I need to be able to migrate full history, which means from an FI-CA viewpoint:
1. Migrate FI-CA posting of liability against BP/contract account.
2. Migrate associated payments.
3. And then clearing documents.
Basically the requirement is to represent the historical data in the new system as if it was posted and matched off.
Is there a technical way to do this?
OR,
Do you migrate the FI-CA liabilties, then the associated payments and then run clearing on the target system?
I suspect this is almost an impossible data migration requirement as development of the extraction and load process would be extremely complex and testing would take months to cover all posting scenarios in FI-CA. However, I would be interested if anyone has attempted to do this before.
Adam

Similar Messages

Uploading of Vendor Cleared items from Legacy

Hi
We have a requirement for uploading of vendor/Customer Cleared Items I would like to know if vendor/Customer Cleared Items can be uploaded from the legacy to SAP.
I have tried my level best and ended up with no ways.
Can any one suggest if there is a way for doing it.
Thanks and Best Regards
Hari Krishnan.K

Hi,
Usually open items are uploaded for the cut off date.
You cannot upload cleared items straight away. what you have to do is that you have to upload vendor balance and transactions. Then you have to clear when you make payments
So upload the balance on the cut off date
after that ask the users to do all the transactions in system
So users will get all these details
But if you can convince the user with good reasons then that would be better.
One more option is that you can put these details in text(document texts ) there you can enter anything. also you can load these details in Vendor master 'text' .
but it will not be available in standard reports
Assign points if useful
Sunoj
Edited by: Sunoj Joseph on Apr 23, 2008 5:19 PM
Edited by: Sunoj Joseph on Apr 23, 2008 5:26 PM

Legacy Data Migration - GL Open Items

Source : SAP R/3
Target : SAP ECC
Data to be moved : GL Open Items
We need to migrate our Legacy data into SAP ECC.
Tel me the efficient way to do data transfer.
Any standard programs available for this ?
Or any technique should I have to follow for this upload.
Guide me please !
RJ

Hi,
Standard SAP tools for the upload are LSMW or BDC. Search this forum, you will find a lot of threads regarding this theme.
Regards,
Eli

Data migration

Dear all my friends,
please help to share me about data migration before go-live FI system.
i plan to migrate GL acct balance, AP/AR open item and last 3 months historical data.
please help to show me : how should i do ?
thanks !

1. Normal GL Accounts: In this case line items are not required and totals are to be updated in SAP. This can be done using GL fast entry if the number is not too high.
2. Open Item Managed GL Accounts: All the open line items are required to be uploaded in SAP from Legacy in order to clear them. Hence, a LSMW / BDC program has to be developed to upload the line items.
BAPI_ACC_DOCUMENT_POST - for GL/AP/AR
BAPI_ACC_INVOICE_RECEIPT_POST - for AP
BAPI_ACC_GL_POSTING_POST - for GL
GL Balance
F-02 or RFBIBL00 or BAPI
Dr GL a/c Credit Data migration Account or Clearing Account
3. Customer & Vendor Open Items: All open line items in Customer and Vendor Accounts have to be brought in into SAP. For this also a LSMW / BDC program needs to be developed and upload the line items.
Vendor Balances
F-02 or RFBIBL00 or BAPI
Credit Vendor a/c (individually) and Dr Data migration Account or Clearing Account
Customer balances
F-02 or RFBIBL00 or BAPI
Dr Customers a/c (individually) and Dr Data migration Account or Clearing Account
4. Asset Accounting: In case asset accounting is implemented the individual balances of each asset (Gross Value and Accumulated Depreciation) have to be uploaded using transaction AS91. For this also you need to develop a LSMW / BDC program. Further, you also need to update the GL Accounts related to Asset Accounts with totals for each asset class T.Code OASV.
For uploading the Assets
AS91 -> for uploading assets in AA
OSAV --> for uploading assets in GL entry Dr Asset (individually) Cr Data migration Account or Clearing Account
You can use LSMW for uploading all these things
After uploading all, your data migration account will become zero

SAP Legacy data Migration Starategy/Process

Hi Friends
I would request you, if anybody let me knwo the process of legacy data migration into sap. What are steps I have to follow while doing legacy data migration. My questions are:
1) How to upload GL balances from legacy to SAP
2) How to upload Vendor and Customer open items into sap
3) Asset balances How to upload
4) what is the use of Migration clearing accounts.
Kindly provide if any documents for legacy data migration into sap.
Thanks in advance
Rao

Dear Rao,
Just check the bwlow link you can understand easly to upload the balances.
http://www.saptechies.com/sap-pdf-books-download/SAP_Go_live_strategy11248141773.pdf
Check the bwlow procedure for the same way do it.
First create 5 Dummy GL codes. These GL code should be zero at the end of uploading balances.
1     GL Offset Account               Dr
          Asset Offset Account          Cr
          AP Offset Account          Cr
          Sales          Cr
          Other GL's          Cr
2     Cash               Dr
     Consumption               Dr
     Asset Offset Account               Dr
     AR Offset Account               Dr
     Material Offset Account               Dr
     Other GL's               Dr
          GL Offset Account     x     Cr
3     AP Offset Account               Dr
          Vendor 1          Cr
          Vendor 2          Cr
          Vendor 3          Cr
4     Customer 1               Dr
     Customer 2               Dr
     Customer 3               Dr
          AR Offset Account          Cr
5     Fixed Asset 1               Dr
     Fixed Asset 2               Dr
          Asset Offset Account          Cr
          Acc. Depreciation Account          Cr
6     Stock Inventory Account               Dr
          Material Offset Account          Cr
Regards,

SAP Accelarated Data migration

Hi All,
Could someone kindly provide more info about SAP ADM. I am uanble to get any info about the same. I would like to understand as to how exactly the tool works. I have the 4 page PDF that is posted on the site but its not clear on the actual tool. Can someone kindly provide me with some document or screen shots or any more info about it. My mail id is [email protected] Could someone kindly reply at the earliest.
Thanks
Prahlad

Hi Prahlad,
Go through this hope u can understand.
With SAP Accelerated Data Migration, you can reduce migration
costs by as much as 50% and avoid interruption of business
processes. Moreover, shutting down the source system after
migration reduces system administration costs and total cost
of operations. In short, you realize the following benefits:
Significantly reduced cost and time to complete migration
projects
Accurate, cost-effective data transfer applicable for any kind
of source system
Better data quality because of preconfigured business objects
that ensure data consistency
Improved end-user productivity and acceptance thanks to
migration of historical data
Effective migration that avoids interruption of business
processes
Full support services to avoid risks and ensure the optimum
performance of your new business applications
Faster return on investment
In short, a smoother, more cost-effective migration to a new
technology solution ultimately positions your organization
to lower your total cost of ownership, maintain competitive
advantage, and pursue new business opportunities.
Expertise in Action
SAP Accelerated Data Migration applies a business objectoriented,
two-step approach that uses a neutral interface as a staging area
and predefined migration content for the conversion and upload
of data. The neutral interface enables the SAP tool to generate
predefined migration content and prevents all potential legal
issues regarding the intellectual property of any source-system
vendor. The whole data migration process from the source to
the target system consists of just two steps, as follows:
1. Data is extracted from the source system into the standard
interface as XML files.
2. Data migrates from the interface into the mySAP Business
Suite database. The migration is based on a new migration
workbench engine developed by SAP based on the SAP
NetWeaver® platform. All requirements for mapping structures
and fields and developing complex conversion rules are solved
within this engine (see Figure 1).
Once the migration is complete, business-unit end users have
access to all the legacy data in the new applications as if it had
originated there. They can continue to work on the existing
business process items in the new applications and benefit from
improved functionality.
Lifting the Limitations
Much of the cost and effort involved in classical data migrations
are generated by migration content development, as follows:
Identifying business objects for migration to properly support
the business
Defining the structure and field mapping for the relevant
business objects
Developing conversion rules for all necessary value mapping
Readily available migration content can simplify this effort.
SAP Accelerated Data Migration provides preconfigured business
content, helping you migrate it to your new system more efficiently
and rapidly. The tool allows the migration of all types of
data, independent of its current state within a business process.
This includes master and dynamic data, as well as partially
processed and historical data, to minimize data loss. Business
processes are uninterrupted and normal operation procedures
can be retained.
By providing a standard, neutral interface and reading data as an
XML file, SAP Accelerated Data Migration is applicable for any
kind of source system. Preconfigured data migration objects built
specifically for SAP applications significantly simplify the conversion
from non-SAP software data into SAP software data objects,
yielding far-reaching benefits. Besides reducing related IT costs,
you can be certain of consistency across business-object boundaries.
Through a direct insert into the database, you avoid the
performance limitations of classical data migration.
Reward points if helpful.
Thanks

Data migration ALE or idocs and bapis

hi ,
thank you guys for the support.
i am into a data migration project.
i need the initial setup for the idocs and bapis.
i dont know anything about these so can u send me the process for the setup and the data migration process too with idocs and bapis.
i didnt understand when they asked me if we can data migrate with a ALE, is that the same as using idocs and bapis or is it a different approach.
u can send me at any inofrmation connected to my eamil addr.
i would really appreciate that.
thank you.

Hi,
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
for VA01 use BAPI_SALESORDER_CREATEFROMDAT2
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
Thanks and regards,
Sarada

Validation rules applied to data migration templates at import

Hi everyone!
First post here for me, so please bear with me if I missed something.
My company has just started the initial implementation of ByDesign. We come from a set of disparate and partially home-grown systems that we outgrew a few years ago.
As part of this initial phase, we are basically re-creating the data on customers, suppliers, etc. since none of our existing systems makes a good source, unfortunately. We will be using the XML templates provided by ByDesign itself to import the relevant data.
It has become clear that ByDesign applies validation rules on fields like postal codes (zip codes), states (for some countries), and other fields.
It would be really helpful if we could get access to the rules that are applied at import time, so that we can format the data correctly in advance, rather than having to play "trial and error" at import time. For example, if you import address data, the first time it finds a postal code in the Netherlands which is formatted as "1234AB", it will tell you that "there needs to a space in the 5th position, because it expects the format to be "1234 AB". At that point, you stop the import, go back to the template to fix all the Dutch postal codes, and try the import again, only to run into the next validation issue.
We work with a couple of very experienced German consultants to help us implement ByDesign, and I have put this question to them, but they are unaware of a documented set of validation rules for ByDesign. Which is why I ask the question here.
So just to be very celar on what we are looking for: the data validation/formatting rules that ByDesign enforces at the time the XML data migration templates are imported.
Any help would be appreciated!
Best regards,
Eelco

Hello Eelco,
welcome to the SAP ByDesign Community Network!
The checks performed on postal codes are country specific, and represent pretty much the information that you would find in places like e.g. the "Postal Codes" page in Wikipedia.
I recommend to start with small files of 50-100 records that are assembled of a representative set of different records, in order to collect the validation rules that need reactions based on your data in an efficient way. Only once you have caught these generic data issues, I would proceed to larger files.
Personnaly I prefer to capture such generic work items on my list, then fix the small sample file immediately by editing, and do an immediate resimulation of the entire file, so that I can drill deeper and collect more generic issues of my data sample. Only after a while when I have harvested all learnings that were in my sample file, I would then apply the collected learnings to my actual data and create a new file - still not too large, in order to use my time efficiently.
Best regards
Michael

Open and Cleared Items

Hi all
We are currently busy finalising our FI-CA BW Data Modeling exercise - and in process to complete Dataflow documentation.
We will make use of the standard open and cleared item extractors with enhancements on different levels. Some background on the requirements:
- We will have to extract document types, divisions, dates, clearing reasons, contract account, Business Partner etc.. information to meet the requirements.
- We will have to keep history for at least 26 months to produce the required management reports (very high number of data), and 'partition' the cubes on date level for both Cleared and Open Items.
- Most of the reports display 13 months worth of billing/ payment figures. I.e. the report for the end of October show billings vs. payments for October 2006, September, August, July, ... to October 2005.
- The requirement is that the report figures will not change from one month to the next (i.e. if I run the report for end of October - all figures from October 2006 to Oct 2005 will remain the same when I run the report for end of November). I.e. if reversals, transfers, returns etc. occur - these will be picked up in later months.
- For the above requirement, we are looking at extracting open (end of month) and cleared items (for the specific monthly interval) on a monthly basis, and appending the data in the cubes. We will then always base the June figure in the report on the June month extraction (LAUFD/ LAUFI fields) and we will pick up any movement in the next month/s - i.e. July.
Has anyone had these types of requirements before - to report on billings vs. payments, and report on history as described above. We would appreciate it if you could share your report requirements, and also design documents, especially the DataFlow documentation that we can look at as input to our design.

We had a requirement to retrieve "aging of receiveables" by customer. Basically, it goes thru each record and depending on the due date places the amounts in the following buckets (example). 0-30 day Overdue, 31-60 days Overdue, 61-90 days overdue, 30+ days overdue, 60+ days overdue) etc all the way to 6+ years overdue.
There are also cooresponding buckets for coming due analysis. For example, what is: 0-30 days coming due, 31-60 days coming due, 30+ days coming due, etc...
To do this, first I needed to be able be able to produce an open items statement at any given time in the past. Now, this seems impossible because of how the items go from open to cleared all the time. And an item that was open one month ago, may not be open anymore.
What I did was first remove any selections on item status. Then compare the posting date with teh key date in the past, if the posting date is less than or equal to the key date, keep the record.
Then compare the clearing date with the key date. First, keep all that are #. (This keeps all records still open from that posting date/key date)
Then, add another check for all items that were cleared after the key date (GT Key Date). This gives you the open items on that date.
Hope that makes sense. Let me know if you want clarification.
/smw

AP cleared Item Report

Hi,
I am use SAP query to build a AP cleared Item report. The report is similar as we can get from FBL1n, but I need a column as group key, which can not be found in FBL1n report.
My questions is:
1. When using SAP query, I use table LFA1 and BSAK, everything is ok, except I could only get the uncleared Item in the table. Like for one item have both Credit and Debit, I could find them in my report. What shall I do?
The field used in the report:
Company Code: BSAK-BUKRS
Vendor Code: BSAK-LIFNR
Vendor Name: LFA1-NAME1
Payment Type(Group Key):
Posting Date: BSAK-BUDAT
Clearing Date: BSAK-AUGDT
Document Type: BSAK-BLART
Fiscal Period: BSAK-MONAT
Fiscal Year: BSAK-GJAHR
2. Or if I just need to have a report like FBL1n, but have group key on the report, any other report I could use?

Hi
Sorry for my unclear question...
What I need is: We need a report on Vendor cleared items, which have a column is Payment Type, to refer to what kind of payment to the vendor, like it's a Adv. fee. Our solution is to use GROUP KEY field in the vendor master data to maintain the payment type information, as it's vendor specified. So for common understanding, we could use FBL1n report, use GROUP KEY as a selection and run out the report. Unfortuntely, we could select by GROUP KEY, but we can not have it shown on the report, from the layout.
So we decided to use SAP Query, which is not a very difficult one. But I found from Query, and the table/ field I refered in my previous message, I could only see some of the records. If one item is cleared in BSAK, I could not find them in my query report made by me. So hope this time my question is cleared, thanks very much.
Or, if our need is to find a proper field to maintain a information in master data, and also can be shown in the FBL1n report, may u suggest?

Difference between cleared items,open items and all postings (FI).

Hi experts,
Can anybody tell me the difference between cleared items,open items and all postings for an account.
While running corresponding bapis and transaction FAGLL03 (for GL) or FBL1N (for accounts payable) i found that in some cases all postings is less than cleared items or open items for a time period. How could it happen.According to my knowledge all postings should contain cleared items and open items.
Please correct me..
Thanks and Regards
Arjun

Hi Arjun,
For every Billing Documnet created(VBRK/VBRP-VBELN) there will be an accounting document created in BSID/BSAD tables.
OPEN ITEMS means the Billed/Invoice Amounts that are pending from Customers, i.e which we have to receive from Customers.
CLOSED ITEMS means the AMOUNTS received from that customer.
OPEN ITEMS : fetch data from BSID table Only
CLOSED ITEMS : fetch data from BSAD only.
ALL POSTINGS : fetch data from both BSID and BSAD.
Hope this will help.
Regards,
Nitin.

Doubt about report FBL5N of screen field:Open items and Cleared items

hi
i know the report FBL5N is use DDF LDB and the report work flow is BSID->BKFP->BSEG
but i don't know to differentiate Open Items and Cleared items in this report.
Open items and Cleared items stand for a field flag in these table (BSID,BKFP,BSEG )? if true the field is?
or they must be calc in program ? if true what about calc rules?
waiting for help! thank you!

Hi,
Here is the difference in Open Items and Cleared Items.
In FI first the document is Open (when it is posted) so the entry is made in table BSID. Once the document is cleared, it will move from BSID to BSAD. And for Cleared item you will see Clearing Document no and Clearing date values updated (these are blank when the item is open).
The only difference in Open and Cleared is via Clearing Document and Clearing Date. If the values are present, it means document is cleared.
Hope this helps.
ashish
Message was edited by:
Ashish Gundawar

Display between open items and cleared items in FS10N

hello all,
I have the following problem.
When I go with FS10N with double click on the initial balance of an G/L account I get the message:
"A large number of line items were selected
Recommendation: Only display open items
Do you want to display open items only?
Yes or NO?"
If I click yes, I get the open items only and if I click no, I get the cleared items. The strange thing is that I get same line items in both reports. For example, I can see same line item, one time as cleared (when I click no) and one time as open (when I click yes).
Do you know the reason for this? For both reports I click on initial balance, so key date should be 01.01.2009, if I run FS10N for fiscal year 2009. Right?
The user is confused in this situation because he is not sure if the item is cleared or not.
thanks for quick reply!
Daniel Nicula.

If you click yes, you get the open items only , but if I click no, you don't get the cleared items only. With NO, you get ALL items.

Open and cleared items FBL3n

Hi Guys,
I have a query.
In FBL3n for G/L line item display , we select open items or cleared items on a particular date.
What is the meaning of this? open in what sense? cleared in what sense?
thanks..
srikanth

Hi,
You can set up accounts with open item management if offsetting entries are to be assigned to the postings made to these accounts. Postings to these accounts represent incomplete transactions.
Example:
A goods receipt/invoice receipt (GR/IR) clearing account should be managed on an open item basis so that you can check at any time whether invoices have been received for the goods received for an order.
Items posted to accounts managed on an open item basis are marked as open or cleared. The balance of these accounts is always equal to the balance of the open items.
You can say that open items means vendor or customers needs to be paid.
Regards,
Jigar

Cleared item swowing as a Open item

Hi All,
I posted a document in f-02 for bank charges the entry was bank charges a/c debit and bank a/c is credit. and i posted the same data into ff67. and for reconsilation i upload the same data into FEBA for bank statement. now this document is cleared.
but the problem is when i see this document in FBL3N this document numbe showing in Open items but i cleared allready.
Please give me the solution for this.

Hi....
Those are items we cannot delete first we have to reverse those items using the FB08 for open items ..other wise use T.code FBRA for clearing items
once done the all activites after that you have dleted the statment number number useing program Goto SE38 and execute the following report: RFEBKA96.
On application put 0001. Here you will find all the statements. Mark the ones you want to delete... and press Delete Statements. This will permanently delete the load from your system.
HINT: to search the statement you want to delete (Short Key), query it using table FEBKO.
After delete the Bank Statement, the following steps can be solved. Please try:
T.Code: FEBP
The following parameters to be entered:
Statement date: The same statement date
Statement number: The same statement number
Select u201CPost immed.u201D Select
Execute
Note:
Please note that statement date is very important and same to be entered to process all the data for posting.
Finally check the statement file debit and credit balance it must be Zero
Than try to post once again ..it will allows you post
I hope it will helps you
Regards
vamsi

Data Migration of FI-CA Cleared Items

Similar Messages

Maybe you are looking for