F.62, Correspondence Type - Accounts Receivable

Hi SAP Gurus,
When I try to print an invoice using the correspondence transaction code F.62, I get the following error.
"Correspondence type SAP19 is not permitted since no date required
Message no. FB461
Diagnosis
You entered correspondence type SAP19 which, according to default settings, requires no date specification.
System Response
Abnormal termination of processing, since in the context of the report you want to currently start, only correspondence types which require a date specification are allowed.
Procedure
Please check your entry. If necessary, first change the default settings for the entered correspondence type by means of customizing. However, make sure that no inconsistent entries exist in the trigger table. If necessary, you must first process the entries or set them to completed so that these can be deleted."
Can anyone let me know how to fix this issue.
Thanks,
Ram

Hi,
I entered the document number only with no date in F.62. Still getting the same error.
Ram

Similar Messages

Correspondence types (transaction FB12): How to print a document?

Hi,
I am using transaction FB12 to test correspondence type "account statement" in quality.
When I enter the correspondence type, customer number posting dates, it get the message that the account statement was requested.
When I go to the spool (SP01), I cannot find it.
What do I need to do to see/print the account statement?
Thank you for your support.
Kind regards,
Linda

T-code FB12, F.64
Accounting/ Financial Accounting/ Accounts Receivable/ Account/Correspondence/Request fb12
Accounting/ Financial Accounting/ Accounts Receivable/ Account/Correspondence/Maintain -f.64
Note: Prior to executing this test, ensure that you have updated the print program variants to print to a test printer
Input the following:
1) Correspondence : Corrrespondence type (the same correspondence type you used when you requested correspondence)
2) Enter company code
3) Enter Document Number
4) Hit Execute
Double click on the line item you wanted to print.
Using steps 1-3, create and print a Customer Invoice & Debit Memo.
Check the Customer Address printed below the 'Remit To' address in the Debit Memo.& Original Invoice
Menu Path:
Accounting>Financial Accounting>Accounts Receivable>Periodic Processing>Print Correspondence>Periodic Account Statement
OR enter Transaction code: F.27
Fill in the following values:
1) Company Code
2) Account type = D (for customer)
3) Account = Customer account number. Enter the range of customer accounts ((Note: Customers with no open items will not be printed.
Canadian customers will get a dual language ( English/French ) Statement and all others will get an English Statement.)
4) Indicator in master record: 2 - for monthly. The indicator here has to match the indicator set up in the customer master record.
5) Key dates for acct statement = This is an open item statement. Enter the starting date as always 01/01/1990 adn the ending date should be the last day of every month.
6) Correspondence:
7) Delete if finished = defaults to 8. Do not leave blank. If you leave blank the completed correspondence requested aren't deleted.
8) Log to printer = Provide the name of the output device in the SAP system.
Hit Execute
To view details in the spooler and status of the printing process or if the previous two steps do not produce a printed account statement, use
1) Transaction code: SP01
Click Execute.
2) Select the spool number (this is displayed in the Periodic Account Statements Log produced in step 2) you wanted to print by entering it. Click Print directly (the printer icon beside the refresh button)
T-code F.61
Select the following path
Accounting/ Financial Accounting / Accounts Receivable / Periodic Processing/Print Correspondence/As Per Request
Input the correspondence type you want to print and company code. Execute

Correspondence Type

I have defined my own correspondence type for sending a letter to the customer and assigned the Z Program created for it. Even the report variant is created.
I have listed the customer line items in FBL5N screen and placed the cursor on the required document. I am not able to view the correspondence type which I have created when I make a correspondence request from the environment menu.
Please let me know whether I have missed out any steps in creation and activation of my own correspondence type.
Thanks
Ravi
Mobile 9849393564

Hello,
Your configuration is incomplete.
Please complete the configuration.
Please follow the following steps:
IMG ==> Financial Accounting ==> Accounts Receivables and Accounts Payables ==> Customer Accounts ==> Line Items ==> Correspondence ==> Make and Check Settings for Correspondence
Define Correspondence Types
Create Report Variants for Correspondence
Assign Programs for Correspondence Types
Define Form Names for Correspondence Print (even you assign your form to blank company code also)
If you complete these steps you will get the spool request get generated.
You go to FB12 - request for the statement
then go to F.61
Then go to SP02 - Take print out.
Regards,
Ravi

AR Correspondence - Linking Form ID to Correspondence type

Hi SAP Gurus,
Can anyone let me know how to link a Form ID to a correpondence type in Accounts Receivable. Is it through report variant?
This is what I have done so far,
Under SPRO>Accounts Receivable and Accounts Payable>Customer Accounts>Line Items>Correspondence>Make and Check Settings for Correspondence
1. Defined three custom correspondence types.
2. Assigned the same program "RFKORD11" for the three correspondence types. However I assigned three different variants for them.
3. Assigned three different custom forms for the same program RFKORD1, with three Form IDs.
The question I have is how to link form IDs to the correspondence types. Is it through report variant? if yes, where do I assign the Form ID in the variant. I tried the program RFKORD11 under SE38; but could not find the field to assign the form ID.
Thank you,
Ram

Hello,
You can find the Customizing path to the correspondence under:
Financial Accounting -> Financial Accounting Global Settings ->
Correspondence.
The creation of correspondences is controlled via the correspondence
type. Each correspondence type is assigned a print report as well as
a variant of this report (caution: correspondence type and variant
often have the same name but are completely different things). The
forms are then assigned to the individual print reports. The balance
confirmation uses no correspondence types.
o Customizing: Assign Programs for Correspondence Types (V_T048B,
    transaction OB78)
In this table, you can assign a print report and the
    corresponding variant to each correspondence type. If a
    correspondence type has been assigned to a company code, this
    correspondence type has priority.
    The following correspondence types are delivered in the standard
    system: SAP01 - SAP18, SAP50 - SAP58, SAP60 and other
    country-specific correspondence types such as SAPQ1, SAPJ1 and so
    on.
o Customizing: Define Form Names for Correspondence Print
    (V_001F_B)
In this table, you can assign a form to each print report. You
    can make a division per print report ID according to a form ID.
    The ID form corresponds to the form set specified in the variant.
If a form is assigned to a print report for a certain company
    code, this has priority.
CoCd   Corr.type   Print report Variant F-ID    Form
SAP06       RFKORD10      SAP06            F140_ACC_STAT_01
        SAP08       RFKORD10      SAP08            F140_ACC_STAT_01
        ZABC        RFKORD10      ABC08     AB     Z140_ACC_ABC
1000   SAP08       ZFKORD10      ZAP08            Z140_ACC_D3
Alternatively, you can find out the print report by calling the ABAP
   debugger. The alternative for finding out the used form is calling
   the SAPscript debugger. You can activate the SAPscript debugger in
   transaction SE71 under 'Utilities -> Activate debugger'.
Standard formats for RFKORD11 are:
SAP13 Customer statement (single statement)   RFKORD11 F140_CUS_STAT_02
SAP14 Open item list with pmt advice (single) RFKORD11 F140_CUS_STAT_02
SAP16 Open item list with pmt advice (assoc.) RFKORD11 F140_CUS_STAT_04
You can select the form on the variant in the option "Form set".
REgards,
REnan

Creation of new Print Program & Variant for new Correspondence Type created

Dear Friends,
I have created 2 new Correspondence Types in SAP as SAP61 (Vendor Debit Note) & SAP62 (Vendor Credit Note) by copying SAP09 (Internal Document) properties like itu2019s Name of the print program - RFKORD30 & Name of variant - SAP09.
We are facing problem when we execute print program in F.64 for SAP09 it is coming same like SAP61 or SAP62. Actual script & print values of SAP09 are replaced by SAP61 or SAP62.
Please suggest us how we can differentiate both SAP09 & SAP61/62. Because we use these correspondences for different purposes like SAP09 gives the information for the Line items in the Document whereas SAP61/62 gives the information of vendor line item weather it is debit or credit entry.
Your kind co-operation in this matter is highly appreciated.
Thanks & Regards,
Naveen Kumar.P

"Assigned the from to the company code - progam in V_001F_B"
Check 'Form ID' field in this IMG transaction against the program and form that you have created.
I am assuming there are 2 lines with same entries but different form IDs.
Or there are 2 lines with the same entries but different CoCodes (seem to remember that the CoCode is not taken into account as a key in certain programs - not logical i know but remembered a previous issue I had many moons ago - could be to do with the blank entry for CoCode field if there is one being picked up by the program before the entry that has your CoCode).
Now check the variant attached and Form ID in step 'Created new program variants in SA38'
Ensure the correct program and variant are attached in step OB78.
My assumption is Form ID is the key.
Hope this helps

Foreign Account Receivable in GL a/c determination

Hi all
my client does not have any foreign customers. is it necessary to assign GL code to Foreign Account Receivable in GL Account Determination.
I have assigned Debitors GL Code to Domestic Account Receivable(Type of account)
I left blanck in Foreign Account Receivable.
When i post AP invoice, system post red error"necessary sales account is missing"
Then i assigned Debitors GL code to Foreigh Account receivable too.
Then problem is resolved.
PLEASE GIVE ME SOME COMMENT ON THIS
Prasad

Hii Prasad
           Was that an AP invoice or AR invoice...there is a gap between AP invoice and foreign receavables A/C
          You must have solved the issue with some other solution
                                                           thanks
                                                                     RIYAZ

How to activate New Correspondence Type

Hi,
I have created a new correspondence type in the following manner:
1)Define Correspondence Types
2)Create Report Variants for Correspondence
3) Assigned programs to correspondence types
4) Defined Forms for Correspondence Print.
I have posted a document through FB70.
When I go to FB03 and display the document so posted and select Environment and Correspondence I am unable to see the New Correspondence that I created.
Please let me know if I am missing any configuration.
Regards,
Raj/

There is requirement where in I need to generate an invoice through FB70 as we won't be using SD billing.
In this process I am trying to activate the Correspondence. I have a particular format of the invoice. These are the steps I followed.
1) IMG-Financial Accounting-****-Correspondence-Define Correspondence Types
Here I checked the the Doc.necessary option. Should I also select the Acct required?
Please let me know what other fields do I have to select here.
2) IMG-Financial Accounting-****-Correspondence-Create Report Variants for Correspondence Types
Not sure what Config needs to be done here.
3) IMG-Financial Accounting-****-Correspondence-Assign Programs for Correspondence Types.
I have assigned the Print Program name here.(Driver program as my Abaper calls it or is it different?)
4) IMG-Financial Accounting-****-Correspondence-SAPscript-Based Forms
I have assigned the Print Program name/Drive Program name and the Form to my company code.
After this I posted FB70 Invoice. Went to FB03 display and selected Correspondence from the Environment. But I cannot see the correspondence that I have created.
Please let me know what else needs to be done.
Immediate help is very much appreciated.

Correspondence type for a/c statements- for Intercompany vendors

Hi all,
can anyone tell me the configuration for correspondence type for A/P statements for intercompany vendors. I tried using SAP08(standard correspondence type) and print program RFKORD10 and layout F140_ACC_STAT_01. I used F.27 with master data indicator '2'(which I maintained in vendor master), correspondence SAP08 for a particular intercompany vendor, I get the balance as on date, but open items are no listed in the statement. I do see the open items in FBL1N, moreover when I used the same correspondence and print program for customer I got the line items in the layout. Can anyone tell me how to accomplish the same with vendor account.
Thanks in advance
Kumar

in OB52
+ Valid for all account types
your all account will be opened. otherwise check OMSY for your company code
NHID NCC Housing and Infrastru 2009 6 2009 5 2008 12
change your settings to the above till it is working
Thanks
Rajakumar.K

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

Report on Account Receivable

hi,
can any one help regarding report on account receivable. the senario is ....
i want to generate report on accounts receivable, that to based on aging
so wht is aging n how to display it and is offset variable n how to create offset variable

Hi,
of the differences between account based CO-PA and costing-based CO-PA that there is no delta extraction. There is also 1 other rule. You can only select 1 fiscal-period. The set-up is similar to costing based CO-PA.
The big difference between Account Based CO-AP and Costing Based CO-PA is of course the data is stored in the CO Modules.
Account based CO-PA is part of the CO concept. This means when you post to a cost element the data is posted to a CO-module (CCA, OPA, PA, PS etc). The way the data is stored is also different from costing based PA.
The CO tables like COEP, COBK (for the individual item are used and the COSS and COSP are used for the totals.
The object where the posting are related to they are stored in the CE4... table. So if you want to analyse the data there is 1 keyfigure and the cost-element is a characteristic (account model).
COsting Based CO-PA data is statistical data. This means that the update of CO-PA is not always equal to what is stored in the CO modules or in finance. The cost element is also not always updated and there are also more key-figures used to store info about the type of costs or revenues. Tables as CE1, CE2 , CE3 and CE4 are used.
Extraction for Account Based CO-PA is only based on the total records (full loads are only possible). For costing based CO-PA there it is possible work with init and delta packages and also to select data from the individual postings databases (CE1, CE2).
The way you generate the extractor is similar.
Hopelfully this gives you a bit more background of the CO-PA module.
CE1 *** , CE *** = Line Item Tables
CE2 *** = Plan Line Item
CE3 *** = Value Fields , Key Fig
CE4 *** = Segment Table
look at htis OSS Note to have more info (with example) about KF vs Account Mode: 407563
The question of whether to have key fig mode or characterstic model come when you have a requirement to report on multiple key figures like plan commitment, actual, etc. In such a scenerio, you have the option of either having so many key figures in the cube ( and in the report) or just have one key fig and distinguish them with a characterisic. The first one if called key fig model and the second one is called characteristic model.
If you have characteristic model you need to either have that may charactristic of that many values with in a characteristic , for example multiple values in version or value type
Regards,
Hareesh

Tutor Material for Account Receivable

Please help with Tutor Material ( study material) for account Receivable. I preparing to study this module but i do not have a study material. If someone has this material or know were i can download please share.

Hi,
It depends what type of information you are after. You can download the Oracle E-Business suite documentation CD from Metalink (or view the library online). In there you will find the Receivables User Guide, Tax manual and API reference guides amongst others (eg. Vertex Integration Guide).
Outside of the standard product docs, there are several books out there, such as the Financials Handbook (McGraw-Hill) that contain good sources of information for the core financials modules.

Interst calculation of Accounts receivable.

Hi,
Kindly provide the configuration stepsl for the Interst calculation of Accounts receivable.
Points will be assigned.

Hello,
Interest calculation :-
Define Interest Calculation Types:-
In this step, you create your interest indicators and determine whether they are to be used for the item interest calculation or account balance interest calculation.
Activities:-
1. Create the required interest indicators.
2. Make sure an interest indicator is entered in the master records of the required accounts.
Interest Calculation Type:-
Decides whether the interest indicator participates in the calculation of interest on arrears (per item) or in the account balance interest calculation (interest scale).
Define Number Ranges for Interest Forms:-
In this activity you create number ranges for interest forms by:
u2022     Specifying an interval of numbers to assign to the interest forms.
u2022     Selecting the type of number assignment (internal).
The system assigns a unique number from the number range interval.
Once you post an interest document, the number of the form is stored in the "Reference" field.
Activities:-
Create a separate number range with internal number assignment for interest calculation.
Prepare Interest on Arrears Calculation:-
In this step you make general specifications for each interest indicator for the calculation of interest on arrears. To do this, you make specifications for the selection of items as well as for calculating interest. You can make further specifications as to the subsequent processing of interest, output control and for posting.
Activities:-
Make your specifications for each interest indicator and make the required specifications.
Calendar type
The calendar type determines how many interest days per month and year are used as a basis for calculating interest on financial investments. The number of days in the year is used as the divisor for the interest rate to calculate the daily interest rate from the annual interest rate.
u2022     B - 30/360
(1 year = 360 days, 1 month = 30 days)
u2022     F - 28,..,31/360
Prepare Item Interest Calculation
In this activity you make the general settings for the individual interest indicators for the item interest calculation (report RFINTITAR). These include settings for selecting the items and for calculating the interest. You can also enter specifications for interest post processing, output control, and for posting.
In this activity, you generally make the same settings as in the previous activity, Prepare Calculation of Interest on Arrears. Changes that you make there have an effect here, and vice versa.
An exception to this is the specification that in the item interest calculation, cleared items are not to be considered in the interest run. If you make this specification here, in Prepare Calculation of Interest on Arrears, you will see that interest is calculated on either all items cleared or only items cleared with payment; these conflicting specifications have no effect on the settings you make here.
Activities:-
Here you define all of the settings relevant for the require interest indicator.
Define Reference Interest Rates:-
You define your reference interest rates by entering a key and a mnemonic name. All other fields are purely informative.
Activities
1. Define your reference interest rates.
2. Specify the interest rates for the reference interest rates in the "Enter interest values" step.
Define Time-Based Terms
You specify how the system determines an interest rate for each interest indicator. You can make these settings based on the currency and a validity date. Each entry is assigned a term that determines the type of interest that is calculated (debit or credit interest).
You also specify the interest rates that you want to use. You can:
u2022     Specify a reference interest rate for which the interest rate is defined.
u2022     Specify the required interest rate directly in the Premium field without specifying a reference interest rate.
u2022     Specify a reference interest rate and an interest rate in the Premium field. The interest premium is added to the reference interest rate during interest calculation.
u2022     You can graduate interest rates by specifying an amount in the Amount from field.
Activities
1. Make the required specifications for each interest indicator.
2. After having specified a reference interest rate, ensure that it is defined in the following steps.
Sequential number
The sequential number is required to define staggered, amount-dependent interest rates. Keep in mind that the same "Valid from" date is used for staggered interest rates. In addition, an entry with an "Amount from" of 0 is required.
Examples
Int.ind.     Currency         Valid from   Seq.no. ... Amount from
01           USD              01/01/1996   1                        0
01           USD              01/01/1996   2                     1000
01           USD              01/01/1996   3                   50000
Enter Interest Values
You specify the required interest rates dependent on the date for the reference interest rates.
Activities
Specify the interest rates for your reference interest rates.
A/R: Calculation of Interest on Arrears
The account determination is carried out via the posting interface of application 0002 (interest on arrears). The following specifications are necessary:
u2022     Account determination keys and posting details:-
First you determine which account determination keys are used. For the business transaction account determination key, 1000 (interest earned) and 2000(interest paid) should be entered. The other account determination keys (company code, interest indicator, business area) are optional. You use them if you want to define interest posting in more detail.
For every combination of the account determination keys, you specify a debit posting key, a credit posting key and account symbols (posting details). You use the account symbol 1000 for the customer posting. It is not necessary to specify an account since the posting is made to the customer account. You do, however, have to specify the posting keys.
u2022     G/L accounts:-
For each G/L account symbol, you specify the account allocation for interest earned and interest paid in full. You can differentiate the account specifications according to currencies.
Activities:-
Make the necessary specifications for posting the interest.
Regards
Ravi

Doubt On Fm FI_OPT_ARCHIVE_CORRESPONDENCE on Additional correspondence types

I had copied the function module FI_OPT_ARCHIVE_CORRESPONDENCE to a custom function module and that is placed in the BTE 2310 and this function module has contains the correspondence types SAP01 (payment notificiation) and SAP08 (account statement) and i am planning to add new one i.e SAPP01 and what will be the Document type.
And SAP01 and SAP08 has the document type FIOPAYCONF,FIOACCSTAT
My question is could you please let me know where i can see the document type for the additional correspondence types where i need to pass ARCHIVE_INDEX in the function module .

I had copied the function module FI_OPT_ARCHIVE_CORRESPONDENCE to a custom function module and that is placed in the BTE 2310 and this function module has contains the correspondence types SAP01 (payment notificiation) and SAP08 (account statement) and i am planning to add new one i.e SAPP01 and what will be the Document type.
And SAP01 and SAP08 has the document type FIOPAYCONF,FIOACCSTAT
My question is could you please let me know where i can see the document type for the additional correspondence types where i need to pass ARCHIVE_INDEX in the function module .

Additional correspondence types

I had copied the function module FI_OPT_ARCHIVE_CORRESPONDENCE to a custom function module and that is placed in the BTE and this function module has contains the correspondence types SAP01 (payment notificiation) and SAP08 (account statement) and i am planning to add new one i.e SAPP01 and what will be the Document type.
and SAP01 and SAP08 has the document type FIOPAYCONF,FIOACCSTAT
My question is could you please let me know where i can see the document type for the additional correspondence types so that i need to pass in that function module

Hi,
>>>>But, I'm not able to see the above mapping types in the drop-down list in Intf Mapping in IR.
just type in the ABAP mapping class name from SE24
and it will work
Regards,
michal

Good Issue to Account Receivable

Dear Expert,
My client has requirement to create good issue with output accounting document as below:
Dr Account Receivable
Cr Material
Do you have any idea, if this requirement can be accommodated in MM via automatic posting?
Is there any movement type that can be used to accommodate this requirement?
If it's not, do you have any idea to perform this transaction?
FYI, current accounting document for good issue is:
Dr Expense
Cr Material
Thank you in advance for your assistance.

Hi,
The accounting document of goods issue will have:
debit GBB
credit BSX
And the posting key is determined by the value string for certain movement type, so it's not changeable for automatic posting.
Thanks and regards,
Polly

F.62, Correspondence Type - Accounts Receivable

Similar Messages

Maybe you are looking for