Migration of Account Receivable Transactions

Dear All,
I am new in Account Receivable, i just want to know the API or interface table for invoice migration from legacy system to oracle.
If possible to give script or API it will benefit for me to complete my task.
Regards

Key tables are
RA_INTERFACE_LINES_ALL
RA_INTERFACE_DISTRIBUTIONS_ALL
ra_customer_trx_all
ra_customer_trx_lines_all
ra_cust_trx_line_gl_dist_all
ar_payment_schedules_all
Please go through the below link to understand the AR invoice interface.
http://bhaskarreddyapps.blogspot.in/2011/10/ar-invoice-interface.html

Similar Messages

Contract Accounts (Receivable/Payable)

Guys,
what is the big advantage of using the contract accounts module over the classic accounts receivable and accounts payable module?
Kind regards,
Rudolf

Hello,
SAP Financial Accounting (FI) delivers the standard Accounts Receivable (FIAR) module to track accounts receivable transactions. This module is tightly integrated with the Sales and Distribution (SD) module to enter and process customer master data, shipping, billing, and receivables.
As requirements became more complex and the data volume increased substantially over the last couple of years, SAP developed a module in FI for tracking A/R data. This application component is known as Contract Accounts Receivable and Payable (FI-CA). SAP promotes FICA as a subledger application alternative for the FI-AR module and Accounts Payables module (FI-AP).
FI-CA was developed to deal with a large number of different customers and different types of receivables. FI-CA is mainly used in industry-specific SAP components,
which by nature have many customers and many different receivable types. Examples industries are the public
sector, utilities, insurance, and telecommunications.
Even if you do not fall into one of these industry groups, you can still use contract accounting. The industry solutions for FI-CA have been available since
1999. An industry-neutral version was introduced in 2002.
FI-CA is not only tightly integrated with the core SAP components like FI,Controlling (CO), Customer Relationship Management (CRM), and SD, it also has
the capability to deal with customers and payments over the Internet by using SAP Biller Direct, which allows your company to use electronic bill presentment and
payment (EBPP).
One of the weak points of FI-CA is its limited reporting functionality. SAP expects that customers who use the FI-CA module also have Business Information Warehouse (BW) installed. The FIAR module has better and more standard reports available and it will take considerable time and effort to develop these reports in FI-CA without using BW. SAP has recognized these shortcomings and promised improved reporting capabilities in future releases.
FI-CA incorporates more A/R functions than just processing invoices and payments and maintaining master data. These functions are necessary if you deal with a large customer base and a high volume of invoices and payments. This is the case with a utility, insurance, or
telecommunications company or in the public sector. My description of FI-CA functionality can be a starting point for your decision process. If you determine that the described functions are necessary for your business, than FI-CA could be a valuable alternative to the standard FI-AR component.
<b>REWARD POINTS IF HELPFUL</b>
Regards
Sai

Hi , We are in 11.5.10.2, recently, one of our OU was sold but still we have given the option to use our system for 6 months inorder to support their business. Now, we dont want those receivables transactions to be posted to out company accounts.

Hi , We are in 11.5.10.2, recently, one of our OU was sold but still we have given the option to use our system for 6 months inorder to support their business. Now, we dont want those receivables transactions to be posted to out company accounts.
How to handle this situation in oracle now.

How To: Direct Message and ArnettH_VZW

Unable to view Purchase order in Receiving Transactions

I am unable to view Purchase Orders in OPM (Recieving transactions- when i query up my Receipt transactions)
I want to be able to View the PO by going to Tools -> View Purchase Orders

Hi,
I believe you are missing a sub-menu which facilitates to open the purchase order on the the responsibility menu you are working with. This is the cause for the issue I guess.
Please refer the below note:
Receiving Transactions Summary - View Accounting - Function Not Available To This Responsibility (Doc ID 865884.1)
Note: In the above note, when trying tools > View accounting in the same form the user get the same issue. Similarly as solution proposed by the note, adding the missing sub menu to the menu will allow you to view the purchase order.
Please add the purchase order view sub menu on the responsibility menu you are working with and check if the issue is solved.
Please try this in your test Server and migrate the solution to the PROD.
Hope this helps!
Best Regards

Contract Account Receivables/Payables

Hi,
While posting the receivable for a day (T Code FP25 / FP50), multiple receipts/payments can be posted with one reconciliation key. When the data is getting posted to GL, it is getting posted as summary entry per Reconciliation Key. If I activate the line item while performing the transaction FP25 to FP50, system doesn't post the same. Can anybody will guide in this case?

These are the transactions used in Student Accounting in the Campus Management component implemented with Contract Accounts Receivable / Payables.This is a add on package in the version 4.70
FP25 - Contract Account Receivables
FP50 - Contract Account Payables

Dunning Letter Set in Accounts Receivable

Please explan how can i create dunning letter sets for customized customer environment, where can i find funciton to create dunning letter set and how cna i attach with specific customer
i can not find any function link in the accounts receivable responsibility or nor in vision operations
Please reply me as soon as possible

hi,
There is a functionality available in the Oracle Receivables Module.
For Creating the Dunning Letter for the specific customer or for all the customers we need to do some preliminary setups to the profile of the customer,.
Steps:
1) Create a Dunning Letter format. -
Navigate to Receivables->Setup->Dunning Letter->
2) Create a Dunning Set Letter format.
Navigate to Receivables->Setup->Dunning Letter Set-
3) Attach the same to the profile of the customer.
Navigate to Receivables->Customers-> Profile-> by updating here the system will asks you the update all the profiles / Existing profile/ Not to update the profile.
If you want to update to all the profiles then you can choose the appropirate option, otherwise choose the existing profile only.
4) Customers->Query the Customer-> Go to Bill to Site -> Menu Profile-Transaction-> choose the dunning letter over there then it only apply to this customer.
If you need any clarification Please feel free to update in this forum.
Srikanth

Posting to Accounts Receivable using WPUBON, when WPUBON contains tenders

Hi all!
My client has some special requirements when invoicing specific customers in SAP ERP using WPUBON from POS DM.
They want accounts receivable to be involved, even though the WPUBON idoc have all tenders/means of payment that is required to pay for the sales in same POS transaction. (Balanced invoice with as much tenders as sales).
What seems to be SAP standard, is that a WPUBON without tenders, will post to accounts receivable.
If the WPUBON idoc includes some tenders, but not sufficiently to pay for all sales in same idoc, the tender amount will post to a balance account, while the remaining sales amount (after deducting the available tenders) are posted to the accounts receivable.
If the WPUBON idoc includes all tenders sufficient to pay for all sales in same idoc, the tender amount will post to balance accounts, and NO postings are done to the accounts receivable.
This might be logical, but for my client and its vendors it prevents them from printing the account receivable statement periodically to check it against the vendors own accounting. (The account receivable postings will be missing for sales that are paid in full in store).
For comparison: When using Payment Card processing in SAP ERP, we create sales orders that are invoiced, and when the credit cards amounts are captured, we get a financial document that posts the invoice just as we want it for WPUBON. First the invoice is posted against accounts receivable (AR), and then we get a "counter-posting" against same AR account when credit card amount is captured and clearing account/balance account for credit card company is posted.
When involving credit card as tender in WPUBON, we get postings to clearing account/balance account for credit card company , but not to AR account as we do for the sales order/invoice in SAP.
Are there customzing settings that can be done in SAP ERP to make it similar for WPUBON idocs as for sales order/invoice in SAP ERP?
Are there user exits that can "force" SAP ERP to post to AR?
Thankful for any advice!
Regards,
Oeystein Emhjellen
tlf +4795 29 25 58

Hello ,
We are also struggling with the similar problem of reconciling the AR and i would seek your help here.
I believe you have figured out all the SQL queries used to get the AR recon done so i would request if you can share the SQL queries with me as it will help us to do our piece of activity in reconciling the AR.

Changing account receivable in accounting tab

Dear All,
I would like to change GL account in the account receivable field on accounting tab of a customer business partner master data. The customer has had some transactions booked in general ledger, is it possible to replace it with other AR account ? I have actually created GL account per customer group. I use UDF and FMS so that each time when select a certain customer group, the GL account automatically filled in the field. Please help. Thanks
Rgds,

Once the Business Partner (BP) is posted with entries you cant change.
But You can create another BP and you can transfer the amount by passing the journal. You should link the new BP to Old BP thru Payments Consolidation. So that only, we can get the pending invoices at the time of Incoming/Outgoing payments.

PRA - Process Improvement for Accounts Receivable and Taxes Payable

SAP PRA introduces process improvements to Accounts Receivable and Taxes Payable write off processes for small dollar line items. When small dollar line item amounts are within the user defined tolerances, these line items can be written off using a batch job, Auto Write Off.

Thank you Wolfrad-
It's a good start. I think the best method in creating roles is to create the name myself and add the t-codes pertaining to that function such as cash application and credit.
I have a list of t-codes (it says all FI transactions) but I don't see credit management t-codes like FD32. Does anyone have a list of credit management t-codes?
Thanks!
POINTS AWARDED

Accounts Receivable Report: Customer Wise Ageing Analysis report -FI module

Hi Gurus,
             Can anyone help me in providing standard report(source code) or already done sample report(source code) for Accounts Receivable Report: Customer Wise Ageing AnalysisThis is in FI Module. Though it is FI Module we need to fetch details related to Sales Module, and the days should be <0     30     60     90     120     180     365     >365
It is urgent I need to deliver this report by this week end.
Please help me . Waiting for your reply.
Points Rewarded for help rendered and I would personally send a good gift if you can help me
Yours Truly,
Rajiv Christopher.
Edited by: Rajiv Christopher on Apr 2, 2008 11:33 AM

Hi,
i am attaching aging report.
see if this is useful to you.
REPORT ZFUS0102 MESSAGE-ID OA
                LINE-SIZE 270.
Title:      GR/IR AGING REPORT
Date:       January 2001
TABLES: DISVARIANT, EKPO.
TYPE-POOLS: SLIS.
Tables
TABLES:
BSIS,
EKKO.
working table
DATA: BEGIN OF RTAB OCCURS 0,
         HKONT   LIKE BSIS-HKONT,
         ZUONR   LIKE BSIS-ZUONR,
         BUDAT   LIKE BSIS-BUDAT,
         SHKZG   LIKE BSIS-SHKZG,
         DMBTR   LIKE BSIS-DMBTR,
         PRCTR   LIKE BSIS-PRCTR,
      END OF RTAB.
DATA: BEGIN OF WTAB OCCURS 0,
         ZUONR(2) TYPE N,
         PRCTR   LIKE BSIS-PRCTR,
         DAYS(4) TYPE P,
         DMBTR   LIKE BSIS-DMBTR,
      END OF WTAB.
DATA: BEGIN OF PTAB OCCURS 0,
         ZUONR(2),
         PRCTR   LIKE BSIS-PRCTR,
         AMT30   LIKE BSIS-WRBTR,
         AMT60   LIKE BSIS-WRBTR,
         AMTPL   LIKE BSIS-WRBTR,
         TOTAL   LIKE BSIS-WRBTR,
      END OF PTAB.
PARAMETERS: COMPANY LIKE BSIS-BUKRS OBLIGATORY,
             ACCT    LIKE BSIS-HKONT OBLIGATORY,
             DATE    LIKE SY-DATUM OBLIGATORY.
SELECT-OPTIONS: S_EKORG FOR EKKO-EKORG.
PARAMETERS: P_VARI LIKE DISVARIANT-REPORT.
DATA: WS-AMT30 LIKE BSIS-WRBTR.
DATA: WS-AMT60 LIKE BSIS-WRBTR.
DATA: WS-AMTPL LIKE BSIS-WRBTR.
DATA: TITLE(21) VALUE 'GR/IR Aging Report'.
DATA: LIN TYPE I.
DATA: GX_VARIANT LIKE DISVARIANT,
      G_VARIANT LIKE DISVARIANT.
DATA: LAYOUT   TYPE SLIS_LAYOUT_ALV,
       L_F      TYPE SLIS_T_FIELDCAT_ALV   WITH HEADER LINE,
       GROUP    TYPE SLIS_T_SP_GROUP_ALV   WITH HEADER LINE,
       COLOR    TYPE SLIS_T_SPECIALCOL_ALV WITH HEADER LINE.
DATA: LT_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER,
       LS_LINE TYPE SLIS_LISTHEADER,
       T_EVENTS   TYPE SLIS_T_EVENT.
CONSTANTS: FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE'.
INITIALIZATION.
PERFORM EVENTTAB_AUFBAUEN USING T_EVENTS[].
PERFORM VARIANT_INIT.
Get default variant
GX_VARIANT = G_VARIANT.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
       EXPORTING
            I_SAVE     = 'A'
       CHANGING
            CS_VARIANT = GX_VARIANT
       EXCEPTIONS
            NOT_FOUND = 2.
IF SY-SUBRC = 0.
    P_VARI = GX_VARIANT-VARIANT.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
PERFORM VARIANT_INPUTHELP_F14.
START-OF-SELECTION.
LS_LINE-TYP = 'S'.
WRITE SY-DATUM TO LS_LINE-INFO DD/MM/YY.
WRITE SY-UZEIT TO LS_LINE-INFO+10.
WRITE SY-UNAME TO LS_LINE-INFO+20.
WRITE TITLE    TO LS_LINE-INFO+30.
APPEND LS_LINE TO LT_TOP_OF_PAGE.
PERFORM FIELDS.
IF NOT P_VARI IS INITIAL.
    PERFORM PAI_OF_SELECTION_SCREEN.
ELSE.
    CALL FUNCTION 'REUSE_ALV_VARIANT_SELECT'
         EXPORTING
              I_DIALOG            = ' '
              I_USER_SPECIFIC     = 'A'
              I_DEFAULT           = ' '
        I_TABNAME_HEADER    =
        I_TABNAME_ITEM      =
              IT_DEFAULT_FIELDCAT = L_F[]
              I_LAYOUT            = LAYOUT
         IMPORTING
        E_EXIT              =
              ET_FIELDCAT         = L_F[]
        ET_SORT             =
        ET_FILTER           =
         CHANGING
              CS_VARIANT          = DISVARIANT
         EXCEPTIONS
              WRONG_INPUT         = 1
              FC_NOT_COMPLETE     = 2
              NOT_FOUND           = 3
              PROGRAM_ERROR       = 4
              OTHERS              = 5.
ENDIF.
Decide which tables to access.
PERFORM MAIN_SELECT.
MOVE TITLE TO LAYOUT-WINDOW_TITLEBAR.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
       EXPORTING
            I_CALLBACK_PROGRAM      = 'ZFUS0102'
            I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
            IS_LAYOUT               = LAYOUT
            IT_FIELDCAT             = L_F[]
            IT_SPECIAL_GROUPS       = GROUP[]
            I_SAVE                  = 'A'
            IS_VARIANT              = G_VARIANT
            IT_EVENTS               = T_EVENTS
       TABLES
            T_OUTTAB                = PTAB
       EXCEPTIONS
            PROGRAM_ERROR           = 1
            OTHERS                  = 2.
      FORM FIELDS                                                   *
FORM FIELDS.
L_F-FIELDNAME     = 'ZUONR'.
L_F-OUTPUTLEN     = 6.
L_F-SELTEXT_L     = 'SERIES'.
L_F-REPTEXT_DDIC = 'SERIES'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'PRCTR'.
L_F-OUTPUTLEN     = 10.
L_F-SELTEXT_L     = 'PROFIT CTR.'.
L_F-REPTEXT_DDIC = 'PROFIT CTR.'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'AMT30'.
L_F-SELTEXT_L     = '30 DAYS'.
L_F-REPTEXT_DDIC = '30 DAYS'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'AMT60'.
L_F-SELTEXT_L     = '60 DAYS'.
L_F-REPTEXT_DDIC = '60 DAYS'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'AMTPL'.
L_F-SELTEXT_L     = '60+ DAYS'.
L_F-REPTEXT_DDIC = '60+ DAYS'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'TOTAL'.
L_F-SELTEXT_L     = 'TOTAL'.
L_F-REPTEXT_DDIC = 'TOTAL'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
ENDFORM.
      FORM MAIN_SELECT                                              *
FORM MAIN_SELECT.
SELECT HKONT ZUONR BUDAT SHKZG DMBTR PRCTR
       INTO TABLE RTAB
       FROM BSIS
       WHERE BUKRS = COMPANY
       AND   HKONT = ACCT.
IF SY-SUBRC = 0.
    SORT RTAB.
    PERFORM PROCESS_RTAB.
    PERFORM PROCESS_WTAB.
ENDIF.
ENDFORM.                    " MAIN SELECT
      FORM VARIANT_INPUTHELP_F14                                    *
FORM VARIANT_INPUTHELP_F14.
DATA: G_EXIT(1) TYPE C.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
       EXPORTING
            IS_VARIANT          = G_VARIANT
            I_SAVE              = 'A' " g_save
          it_default_fieldcat =
       IMPORTING
            E_EXIT              = G_EXIT
            ES_VARIANT          = GX_VARIANT
       EXCEPTIONS
            NOT_FOUND = 2.
IF SY-SUBRC = 2.
    MESSAGE ID SY-MSGID TYPE 'S'      NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
    IF G_EXIT = SPACE.
      P_VARI = GX_VARIANT-VARIANT.
    ENDIF.
ENDIF.
ENDFORM.
      FORM USER_COMMAND                                             *
--> UCOMM                                                         *
--> SELFIELD                                                      *
FORM USER_COMMAND USING UCOMM LIKE SY-UCOMM SELFIELD TYPE
SLIS_SELFIELD.
IF UCOMM EQ '&IC1'.
    IF SELFIELD-TABINDEX <= 0.
      MESSAGE S108.
      EXIT.
    ENDIF.
IF SELFIELD-SEL_TAB_FIELD CS 'LIFNR'.
    SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
    CALL TRANSACTION 'XK02'.
ELSE.
    IF SELFIELD-SEL_TAB_FIELD CS 'VEND'.
      SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
      CALL TRANSACTION 'FBL1'.
    ENDIF.
ENDIF.
    CLEAR SY-UCOMM. CLEAR UCOMM.
ENDIF.
ENDFORM.
      FORM TOP_OF_PAGE                                              *
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
       EXPORTING
            IT_LIST_COMMENTARY = LT_TOP_OF_PAGE.
ENDFORM.
      FORM EVENTTAB_AUFBAUEN                                        *
--> P_T_EVENTS                                                    *
FORM EVENTTAB_AUFBAUEN USING P_T_EVENTS TYPE SLIS_T_EVENT.
DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
       EXPORTING
            I_LIST_TYPE = 0
       IMPORTING
            ET_EVENTS   = P_T_EVENTS.
READ TABLE P_T_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                                                 INTO LS_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_TOP_OF_PAGE TO LS_EVENT-FORM.
    APPEND LS_EVENT TO P_T_EVENTS.
ENDIF.
ENDFORM.                               " EVENTTAB_AUFBAUEN
      FORM PAI_OF_SELECTION_SCREEN                                  *
FORM PAI_OF_SELECTION_SCREEN.
IF NOT P_VARI IS INITIAL.
    MOVE G_VARIANT TO GX_VARIANT.
    MOVE P_VARI TO GX_VARIANT-VARIANT.
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
         EXPORTING
              I_SAVE     = 'A' " g_save
         CHANGING
              CS_VARIANT = GX_VARIANT.
    G_VARIANT = GX_VARIANT.
ELSE.
    PERFORM VARIANT_INIT.
ENDIF.
ENDFORM.                               " PAI_OF_SELECTION_SCREEN
      FORM VARIANT_INIT                                             *
FORM VARIANT_INIT.
CLEAR G_VARIANT.
G_VARIANT-REPORT = 'ZFUS0102'.
ENDFORM.                               " VARIANT_INIT
*&      Form PROCESS_RTAB
      text
--> p1        text
<-- p2        text
FORM PROCESS_RTAB.
DATA TLNS TYPE I.
DESCRIBE TABLE S_EKORG LINES TLNS.
LOOP AT RTAB.
    IF TLNS GT 0.
      SELECT SINGLE EKORG FROM EKKO INTO EKKO-EKORG
        WHERE EBELN = RTAB-ZUONR(10).
      CHECK EKKO-EKORG IN S_EKORG.
    ENDIF.
    IF NOT RTAB-BUDAT > DATE.
      MOVE RTAB-ZUONR(2) TO WTAB-ZUONR.
      COMPUTE WTAB-DAYS = DATE - RTAB-BUDAT.
      IF RTAB-SHKZG = 'H'.
        WTAB-DMBTR = RTAB-DMBTR * -1.
      ELSE.
        WTAB-DMBTR = RTAB-DMBTR * 1.
      ENDIF.
      MOVE RTAB-PRCTR TO WTAB-PRCTR.
      APPEND WTAB.
    ENDIF.
ENDLOOP.
FREE RTAB.
ENDFORM.                    " PROCESS_RTAB
*&      Form PROCESS_WTAB
      text
--> p1        text
<-- p2        text
FORM PROCESS_WTAB.
SORT WTAB BY ZUONR PRCTR DAYS.
LOOP AT WTAB.
    PTAB-ZUONR = WTAB-ZUONR.
    PTAB-PRCTR = WTAB-PRCTR.
    AT END OF DAYS.
      SUM.
      IF WTAB-DAYS > 60.
        WS-AMTPL = WS-AMTPL + WTAB-DMBTR.
      ELSE.
        IF WTAB-DAYS > 30.
          WS-AMT60 = WS-AMT60 + WTAB-DMBTR.
        ELSE.
          WS-AMT30 = WS-AMT30 + WTAB-DMBTR.
        ENDIF.
      ENDIF.
    ENDAT.
    AT END OF PRCTR.
      PTAB-AMTPL = WS-AMTPL.
      PTAB-AMT30 = WS-AMT30.
      PTAB-AMT60 = WS-AMT60.
      COMPUTE PTAB-TOTAL = PTAB-AMTPL + PTAB-AMT30 + PTAB-AMT60.
      APPEND PTAB.
      WS-AMTPL = 0.
      WS-AMT30 = 0.
      WS-AMT60 = 0.
    ENDAT.
ENDLOOP.
SORT PTAB BY ZUONR PRCTR.
ENDFORM.                    " PROCESS_WTAB
regards,
Sindhu

BAPI / LSMW for Accounts Receivable open items and G/L Accounts balance

I want to transport legacy data to SAP.
Please provide me with a BAPI or LSMW for creating entries for
Accounts Receivable open items
General Ledger Accounts balances

Thomas,
Program RFBIBL00 is traditionally used for converting FI transactions. In LSMW, it's object 0100, sub object 0000.
-nathan

FICO-Accounts Receivable / Payable.

Hello every one...i am totally new to FICO abap...to say i dont no anything abt FICO...but i have a develop below said requirement....can anyone please help me with the procedure( the code, if possible, to understand better)and the related transaction codes for FICO..
Here is the requirement...
'To develop a program to read open transactions posted to Accounts Receivable / Payable and to derive the correct PRofit centre from the line item master records (WBS, cost Centres etc.). Then to produce a report analysing the spend by derived profit centre'.

Hi everybody,
you should perform a query similar to this:
data: begin of t_data occurs 0 with header line,
        lifnr like bsik-lifnr,
        kunnr like bsid-kunnr,
        prctr like bseg-prctr,
        wrbtr like bseg-wrbtr,
        waers like bseg-waers,
      end of t_data.
select * from bsik...
select *
    from bseg
    where bukrs = bsik-bukrs
      and belnr = bsik-belnr
      and gjahr = bsik-gjahr
      and koart = 'S'.
    t_data-lifnr = bsik-lifnr.
    t_data-prctr = bseg-prctr.
    t_data-wrbtr = bseg-wrbtr.
    t_data-waers = bseg-waers.
    collect t_data.
endselect.
endselect.
...this could be a start.
I hope it helps. BR,
Alvaro

Table for accounts receivable

Hi experts,
Which table stores accounts receivable and accounts payable data mainly?
prasad

Dear,
It all depends upon what kind of data you look at, because if you want to know the data pertains to masters or transactions for account receivable and accounts payable.
Master data tables:
Vendor Master : LFA1, LFB1, LFBK, LFBW,ADRC, LFC1 etc
Customer Master : KNA1, KNB1, KNBK, KNC1etc.
Transaction data:
Customer
BSID - Customer Open Items
BSAD- Customer cleared items.
Vendor
BSIK - Vendor Open Items
BSAK- Vendor cleared items.

Currency problem in accounts receivables ageing report

when i generated accounts receivables ageing report i got ageing in UAE DIRHAMS only and i have receivables in two different currencies in UAE DIRHAMS AND IN EURO , i want to get all receivables in the ageing report in euro only but i couldn't please how to solve this currency problem
thanks in advance

Hi
Please refer this transaction code for account receivable ageing report
S_ALR_87012168 - Due Date Analysis for Open Items
Regards
Praveen

Accounts Receivable - Report which includes Volumetrics i.e. Material/Volume/Price

Hello,
What report can be used to obtain the following for Accounts Receivable (all in one report would be preferred):
     AR Aging
     Material Code
     Volume
     Price of material
For example, AR has $1M due from a customer (its current/within 30 days)
     What material(s) does that cover? It covers x,y,z materials
     At what price per material? x price is $90.81 per bbl, y price is $100.79 per bbl and z price is $65.84 per bbl
     What is the volume of each? x volume is 5,000 bbls, y volume is 3,000 bbls and z volume is 3,700
We need to be able to run a report that includes all the above data.
Any help is greatly appreciated.
Thanks!

Please check report under Financial-> Financial report->Accounting->Aging- > Choose customer aging receivables.
Also here is a list of other usual reports available:
Accounting - Financial Accounting - Customers - Information System - Reports for Accounts Receivable Accounting
Customer Balances
S_ALR_87012167 - Accounts Receivable Information System
S_ALR_87012172 - Customer Balances in Local Currency
S_ALR_87012186 - Customer Sales
S_ALR_87012169 - Transaction Figures: Account Balance
S_ALR_87012170 - Transaction Figures: Special Sales
S_ALR_87012171 - Transaction Figures: Sales
Customers: Items
S_ALR_87012168 - Due Date Analysis for Open Items
S_ALR_87012197 - List of Customer Line Items
S_ALR_87012173 - List of Customer Open Items for Printing
S_ALR_87012174 - List of Customer Open Items
S_ALR_87012175 - Open Items - Customer Due Date Forecast
S_ALR_87012176 - Customer Evaluation with OI Sorted List
S_ALR_87012177 - Customer Payment History
S_ALR_87012178 - Customer Open Item Analysis by Balance of Overdue Items
S_ALR_87012198 - List of Cleared Customer Items for Printing
S_ALR_87012199 - List Of Down Payments Open On Key Date - Customers
Master Data
S_ALR_87012179 - Customer List
S_ALR_87012180 - Address List
S_ALR_87012182 - Display Changes to Customers
S_ALR_87012183 - Display/Confirm Critical Customer Changes
S_ALR_87012195 - Customer Master Data Comparison

Migration of Account Receivable Transactions

Similar Messages

Maybe you are looking for