F-28 Incoming payment BSEG-XREF1/2 & BSEG-XREF3 grayed out on clearing line

We apply payment Using SAP standard transaction code F-28 - post incoming payment.
Business requirement is to capture Reference Key 1/2 & Reference Key 3 are on cleared as well as partial line items. Populating these fields will help reconciliation.
I have opened up these fields for data entry via
SPRO - Financial Accounting - Accounts Receivable and Accounts Payable
- Business Transactions - Incoming Payments - Make and Check Document
Settings- Define Posting Keys.
These fields are available only for partial or payment on account. For clearing lines its grayed out completely.
Appreciate your help.
Thanks
Uday Malghan

I would like to share workaround. As mentioned in my prior mail these fields were open for entry, however SAP prevents any changes. Opening up OSS message with SAP was not helpful. To get around I decided to create substitution rule to populate these fields. It works fine. I thought sharing with this forum. Thanks for for your time.

Similar Messages

How to import Incoming Payments via DTW

Hello all,
I am importing opening balances for Customers via DTW. My client wants to import all the open Invoices at their original amount, and then import the incoming payments against them to have them net out to the correct remaining balance. I already know how to import the invoices. I'm looking at using the PaymentDrafts template in DTW for the Incoming payments but I could use some guidance. Can anyone provide and example of the data required to both import the incoming payments and apply them to the appropriate AR Invoice?
Thanks,
don shields

hi donald,
Check this link to resolve ur doubts.
Import Incoming Payments with DTW
Import Incoming Payments with DTW
also check this SAP Note
Note 1162513 - How to link an Incoming Payment to an Invoice via the DTW
Jeyakanthan
Edited by: Jeyakanthan A on Apr 30, 2009 10:31 PM

Clear incoming payment for two company codes

dear all
i received an incoming payment but it concerns two company codes how to clear it

hi
what do you mean by concerning two company codes?
1. the payment is made by one company code to another company code, both of which are in your system?
2. same payment, part of which for one company code, remaining for another one?
3. centre ar collection, one company code collects money for another compay code?
please clarify
best regards, Lawrence

Bseg-XREF1 missing in F-03

Hi
The Reference Key 1,2 and 3 is missing in fb03. The document i posted is a downpayment request to a vendor, The document posted while viewing in FB03, the additional data tab is not showing the Reference Key filelds1, 2 and 3. Do somebody knows how to enable these fields in SAP.
The additional fields required are BSEG-XREF1 (Reference key 1), BSEG-XREF2 (Reference key 2), BSEG-XREF3 (Reference key 2) .
i have alredy checked the field status checkings in t code OB41 and OB32 but not found any configurations missing there,
Please let me know if somebody knows how to fix this.
Regards
Raghu

Hi
How to enable this for layouts.
regards
Raghu

Mass update BSEG-XREF1

Hi,
Can anyone suggest FM or BAPI to mass update in BSEG-XREF1, BSEG-XREF2 and BSEG-XREF3 besides using BDC and FM FI_ITEMS_MASS_CHANG?
I tried to avoid using tcode FB02 and that is the reason i don't want to use BDC and FM FI_ITEMS_MASS_CHANG.
Thanks.
Juli.

I guess only BDC via transaction FB02 is the only way..

FB05 - How to display fields BSEG-XREF1-XREF2?

Hi all,
We need to execute a FB05 ( Trasfer posting with clearing) on a GL
account: our GL documents have BSEG-XREF1/2/3 valued (with Agreement data) but BSIS-XREF1/2 are
not available on our DB (only BSIS-XREF3 exists). When we "Choose open item' for that GL account,
XREF1/2 are displayed as empty because data are selected from BSIS ( we have created a custom layout variant for line item display
with XREF fields without problem). Is it possible to retrieve data from
BSEG without changing abap standard program but only working on
customizing?
Thanks in advance.
Marco

Hi Andreas,
thank you for your answer.
We have already tried this solution but without results. In FB05 we can see XREF1-XREF2 columns, but they contain no value in case of G/L Open Items.
However in case of Customer/Vendor Open Items XREF1-XREF2 are valued because they are taken from BSID/BSIK tables where XREF1-2-3 exist.
In table BSIS (used for GL Open Items) we have only XREF3, that in FB05 is therefore correctly valued.
Any other idea?
Thanks.
Marco

How to see fields BSEG-XREF1, BSEG-XREF2 and BSEG-XREF3 in FB60

Hi,
We need to make visible fields BSEG-XREF1, BSEG-XREF2 and BSEG-XREF3 in transaction FB60 for data entry.
Please advise .
Regards,
Saeed

Dear Saeed,
First Make Field Status group this fields mandatory or Optional.
Then after entering all the data in fb60 screen goto to environment and then press Complex Posting.
Then double click on the line Expense line item and press more data.
There you will find this fields for entry.

Search help in bseg-xref1

Hello,
I pretend to assign a seach-help to the field bseg-xref1, how can i do it?
regards
JLeal

Close your eyes, click your heels together three times and say:
"The search help is there"
Rob

Post Incoming Payments - Transaction F-28

Hello all,
I need to post Incoming payments from a certain flat file.
Is there any standard BAPI or FM which does post the Incoming payments in F-28.
Thanks in advance.
Regards,
Arun

Hi Amit,
I was searching on SDN for my problem and got your thread,
I want to post incoming payment for customers using BAPI BAPI_ACC_DOCUMENT_POST.
But i am missing some paramenters that need to pass.
When i am executing my program FI document is getting created but with posting key 40 & 50.(BSEG)
I want document to be created with posting keys 40 & 15 (i.e. Incoming payment document).
can you just give me any sample code or import values that need to pass & may be i am missing.
Also my issue is interface between Non-SAP & SAP systems via BAPI for posting & Clearing.
I know using above BAPI we can only post document but can not clear invoice.
So is there any alternative to this bapi so that i can post & clear documents?
Please reply.
I tried with BDC for f-28 inside zbapi but through f-28 also we can only post documents which are partial payments.
So is there any way to post via bdc or zbapi and then clear with some other transaction?

BDC / Bapi For Post Incoming Payment (F-28)

Hi
Im creating BDC for F-28. But it got error coming out.
>> It says DB05B-PSZAH(02) is not an input field.
What I do is: First, I search for Line Item then Document Number. Then It return to basic list. Then I loop again for the second Line Item Number and Document Number.
I can activate the first amount but cannot for the next amount and so on.
Anybody could help me on this??
Is there any BAPI for Post Incoming Payment (F-28)?
Thank you.
Regards.

i dont think there is a BAPI for this Transaction...
i have done a BDC on F-28 myself....pasting the code....hope it helps you....
*******NOTE********
the parameter in the subroutine is to see if there is a single document or multiple documents being posted.
FORM fill_bdc_data_f-28_9005 USING p_i_mult_doc TYPE c.
**BDC from screen 9005
DATA : l_amt_bdc(13), l_amt_bdc_remain(13), l_amt_bdc_mult(13),
         l_amt_bdc_mult_remain(13), l_assignment(14), l_period(2),
         l_amount(13).
CLEAR t_bdcdata.
REFRESH t_bdcdata.
PERFORM bdc_dynpro USING 'SAPMF05A' '0103'.
PERFORM bdc_field USING 'BDC_OKCODE' '=AB'.   "OK CODE - doc overview
**get user default date format and pass date in that format
PERFORM convert_date_to_user_format USING bkpf-bldat.
PERFORM bdc_field USING 'BKPF-BLDAT' w_date. "cheque date
CLEAR w_date.
PERFORM bdc_field USING 'BKPF-BLART' i_blart. "doc type
PERFORM bdc_field USING 'BKPF-BUKRS' i_bukrs. "comp code
**get user default date format and pass date in that format
PERFORM convert_date_to_user_format USING bkpf-budat.
PERFORM bdc_field USING 'BKPF-BUDAT' w_date. "posting date
CLEAR w_date.
l_period = sy-datum+4(2).
PERFORM bdc_field USING 'BKPF-MONAT' l_period. "period
PERFORM bdc_field USING 'BKPF-WAERS' 'INR'.    "currency
PERFORM bdc_field USING 'BKPF-BKTXT' i_bankl. "doc. hdr. text
PERFORM bdc_field USING 'BKPF-XBLNR' i_xblnr. "Ref. Document No.
PERFORM bdc_field USING 'BSEG-ZUONR' i_zuonr. "Assignment(Depot Code)
PERFORM bdc_field USING 'RF05A-KONTO' i_bank_gl. "Bank GL acc
PERFORM bdc_field USING 'BSEG-GSBER' i_gsber. "Business Area
l_amount = bseg-wrbtr.
PERFORM bdc_field USING 'BSEG-WRBTR' l_amount. "Amount
PERFORM bdc_field USING 'BSEG-PRCTR' ''. "Profit Center
**open items data
PERFORM bdc_field USING 'RF05A-AGKOA' 'D'.     "Acc type (D=customers)
PERFORM bdc_field USING 'RF05A-XNOPS' 'X'.     "Std OIs check box
**end of first screen
**document overview screen
PERFORM bdc_dynpro USING 'SAPMF05A' '0700'.    "Overview Screen
PERFORM bdc_field USING 'BDC_CURSOR' 'RF05A-AZEI1(01)'.     "cursor
PERFORM bdc_field USING 'BDC_OKCODE' '/00'.     "OK CODE
PERFORM bdc_field USING 'RF05A-NEWBS' '19'.    "posting key
PERFORM bdc_field USING 'RF05A-NEWKO' i_kunnr. "customer
PERFORM bdc_field USING 'RF05A-NEWUM' 'B'.     "Spl GL Indicator
**for single document selected
CLEAR l_amt_bdc.
IF p_i_mult_doc = ''.
***new screen - next line item
    PERFORM bdc_dynpro USING 'SAPMF05A' '0303'.
    PERFORM bdc_field USING 'BDC_OKCODE' '=BU'.    "OK CODE
**for single document, use the bouncing amount calculated earlier
    l_amt_bdc = w_amt_ant_bouncing.
    PERFORM bdc_field USING 'BSEG-WRBTR' l_amt_bdc. "amount
**due date - same as posting date on screen
**get user default date format and pass date in that format
    PERFORM convert_date_to_user_format USING bkpf-budat.
    PERFORM bdc_field USING 'BSEG-ZFBDT' w_date. "due date
    CLEAR w_date.
**assignment
    CLEAR l_assignment.
    CONCATENATE t_seldoc_ant_bouncing-belnr
                t_seldoc_ant_bouncing-gjahr INTO l_assignment.
    PERFORM bdc_field USING 'BSEG-ZUONR' l_assignment. "assignment
    PERFORM bdc_field USING 'BSEG-GSBER' i_gsber.
**if there is some remaining amount, then go for another line item
    IF w_rem_amt_ant_bouncing > 0.
      PERFORM bdc_field USING 'RF05A-NEWBS' '15'.    "posting key
      PERFORM bdc_field USING 'RF05A-NEWKO' i_kunnr. "customer
**new screen
      PERFORM bdc_dynpro USING 'SAPMF05A' '0301'.
      PERFORM bdc_field USING 'BDC_CURSOR' 'BSEG-ZTERM'. "CURSOR
      PERFORM bdc_field USING 'BDC_OKCODE' '=BU'.    "OK CODE-ENTER
      l_amt_bdc_remain = w_rem_amt_ant_bouncing.
      PERFORM bdc_field USING 'BSEG-WRBTR' l_amt_bdc_remain.
      PERFORM bdc_field USING 'BSEG-ZTERM' '0001'.
**AGAIN
      PERFORM bdc_dynpro USING 'SAPMF05A' '0301'.
      PERFORM bdc_field USING 'BDC_CURSOR' 'BSEG-WRBTR'. "CURSOR
      PERFORM bdc_field USING 'BDC_OKCODE' '=BU'.    "OK CODE-SAVE
      PERFORM bdc_field USING 'BSEG-WRBTR' l_amt_bdc_remain.
      PERFORM bdc_field USING 'BSEG-ZTERM' '0001'. "pmt term -hardcoded
      PERFORM bdc_field USING 'BSEG-SKFBT' l_amt_bdc_remain.
    ENDIF.
**multiple documents
ELSE.
**initialize remaining amount to amt entered on screen
    l_amt_bdc_mult_remain = bseg-wrbtr.
    LOOP AT t_seldoc_ant_bouncing.
      IF l_amt_bdc_mult_remain > 0.
        IF bseg-wrbtr > t_seldoc_ant_bouncing-rem_amt.
          l_amt_bdc_mult = t_seldoc_ant_bouncing-rem_amt.
        ELSE.
          l_amt_bdc_mult = bseg-wrbtr.
        ENDIF.
**remaining amt = screen amt - amt calculated above.
        l_amt_bdc_mult_remain = l_amt_bdc_mult_remain - l_amt_bdc_mult.
        PERFORM bdc_dynpro USING 'SAPMF05A' '0303'.
        PERFORM bdc_field USING 'BDC_OKCODE' '=BU'.    "OK CODE
        PERFORM bdc_field USING 'BSEG-WRBTR' l_amt_bdc_mult. "amount
        PERFORM bdc_field USING 'BSEG-GSBER' i_gsber. "Business Area
**due date - same as posting date on screen
**get user default date format and pass date in that format
        PERFORM convert_date_to_user_format USING bkpf-budat.
        PERFORM bdc_field USING 'BSEG-ZFBDT' w_date. "due date
        CLEAR w_date.
**assignment
        CLEAR l_assignment.
        CONCATENATE t_seldoc_ant_bouncing-belnr
                    t_seldoc_ant_bouncing-gjahr INTO l_assignment.
        PERFORM bdc_field USING 'BSEG-ZUONR' l_assignment. "assignment
**posting key 19 for all but last document
        PERFORM bdc_field USING 'RF05A-NEWBS' '19'.    "posting key
        PERFORM bdc_field USING 'RF05A-NEWKO' i_kunnr. "customer
        PERFORM bdc_field USING 'RF05A-NEWUM' 'B'.     "Spl GL
      ENDIF.
    ENDLOOP.
ENDIF.
**post remaining amount
IF p_i_mult_doc = 'X'.
**new screen if there is some amount left
    IF l_amt_bdc_mult_remain > 0.
**posting key 15 with remaining amount
      PERFORM bdc_field USING 'RF05A-NEWBS' '15'.    "posting key
      PERFORM bdc_field USING 'RF05A-NEWKO' i_kunnr. "customer
      PERFORM bdc_field USING 'RF05A-NEWUM' ''.     "Spl GL
**new screen
      PERFORM bdc_dynpro USING 'SAPMF05A' '0301'.
      PERFORM bdc_field USING 'BDC_OKCODE' '=BU'.    "OK CODE
      PERFORM bdc_field USING 'BSEG-WRBTR' l_amt_bdc_mult_remain.
      PERFORM bdc_field USING 'BSEG-ZTERM' '0001'. "pmt term - hardcoded
    ELSE.
**if no amount is left, no need for a further line item
      PERFORM bdc_field USING 'RF05A-NEWBS' ''.    "posting key
      PERFORM bdc_field USING 'RF05A-NEWKO' ''. "customer
      PERFORM bdc_field USING 'RF05A-NEWUM' ''.     "Spl GL
    ENDIF.
ENDIF.
**clear variables
CLEAR : l_amount, l_assignment, l_amt_bdc,
          l_amt_bdc_remain,l_amt_bdc_mult, l_amt_bdc_mult_remain.
ENDFORM.                    " fill_bdc_data_F-28_9005

BAPI on Post Incoming Payment (F-28) Enquiry

Hi all,
I try to look for BAPI on F-28 and I had search for many info. However, I found that 1 thread saying that we can have 'BAPI_ACC_GL_POSTING_POST' to do.
Refer to this site:
bapi is used to 'post incoming payments (t-code F-28)'
However, I found that the BAPI is used for transaction FB50. Generally, I use the F-28 to post incoming payment for AR. So I am not so sure that the BAPI can work.
Besides that, I found another thread claim that no BAPI for the F-28. Refer to this site:
https://www.sdn.sap.com/irj/sdn/profile?userid=677412
As my research, I cant find the appropriate BAPI. Please give me some idea on how the BAPI work, and any correct BAPI can be used? Frankly, I a bit confused now.
Thanks and regards.
Cheers,
Isaac

Kindly go through this. I thjink it will clear you.
Pattern in which function modules are called
The function module fi_document_process is called 4 times and finally document_post is called once which updates the tables.
Step 1. Call FI_DOCUMENT_PROCESS
Import Parameters
I_GJAHR     LIKE     TRWCA- YEAR
I_PROCESS     LIKE     TRWPR-PROCESS
I_EVENT     LIKE     TRWPR-EVENT
Tables
T_BKPF          LIKE     BKPF
T_BSEG          LIKE     BSEG
T_BSEGZ     LIKE     BSEGZ
T_ACCIT_EXT     LIKE     ACCIT_EXTENSION
Values to populate import parameters
      i_gjahr                 = '2007'     Fiscal year from the screen
      i_process              = 'BELEG'    Constant, can be hard coded
      i_event                  = 'CRBSEGZ'   Constant, can be hard coded
              xbkpf-bukrs '1000'.            Company code from the screen
              xbkpf-belnr '$1'.               constant , can be hard coded
              xbkpf-gjahr '2007'.            Fiscal Year , from the screen
              xbkpf-blart 'DZ'.               Can be obtained from the invoice document
              xbkpf-bldat '20070116'.       Document Date, from the screen
              xbkpf-budat 20070118'.      Posting Date , from the screen
              xbkpf-monat '01'.                   constant , can be hard coded
              xbkpf-wwert '20070118'.       posting Date
              xbkpf-usnam 'SAPUSER'.       user name
              xbkpf-tcode 'FBZ1'.                Constant, can be hard coded
              xbkpf-waers 'EUR'.                 currency, from the screen
              xbkpf-glvor 'RFBU'.                constant can be hard coded
              xbkpf-awtyp 'BKPF'.                constant, can be hard coded
              xbkpf-fikrs 1000'.               customer account number, from the screen
              xbkpf-hwaer 'EUR'.              Currency, from the screen
              xbkpf-awsys 'ECCCLNT800'.    can be hard coded
xbseg Record 1
      xbseg-bukrs '1000'.           Company code from the screen
      xbseg-belnr '$1' .           constant , can be hard coded
      xbseg-gjahr '2007'.             Fiscal Year, from the screen
      xbseg-buzei 001'.            constant , can be hard coded
      xbseg-bschl '40'.           constant , can be hard coded
      xbseg-koart 'S'.           constant , can be hard coded
      xbseg-shkzg 'S' .            constant , can be hard coded
      xbseg-dmbtr '10'.            Amount, from the screen
      xbseg-wrbtr '10'.            Amount, from the screen
      xbseg-pswbt 10'.            Amount, from the screen
      xbseg-pswsl 'EUR'.            Currency, from the screen
      xbseg-valut 20070118'.         Posting date, from the screen
      xbseg-altkt '0000110100'.
      xbseg-vorgn 'RFBU'.       constant , can be hard coded
      xbseg-fdlev 'B9'.            constant , can be hard coded
      xbseg-fdwbt '10'.            Amount, from the screen
      xbseg-fdtag '20070118'.       Posting date, from the screen
      xbseg-kokrs 1000'.             Customer account
      xbseg-xkres 'X'.           constant , can be hard coded
      xbseg-xopvw 'X'.            constant , can be hard coded
      xbseg-hkont '0000110009'. Bank Account number
      xbseg-xbilk 'X'.           constant , can be hard coded
      xbseg-fipos '9620'.            constant , can be hard coded
      xbseg-lokkt '0000110009'. Bank Account number
xbseg Record 2.
        bseg-bukrs '1000'.       Company code from the screen
      bseg-belnr. '$1'       constant , can be hard coded
      bseg-gjahr. '2007'      Fiscal year from the screen
      bseg-augbl. '*'      constant , can be hard coded
      bseg-buzei'002'.      constant , can be hard coded
      bseg-bschl. '15'      constant , can be hard coded
      bseg-koart. 'D'      constant , can be hard coded
      bseg-shkzg. 'H'      constant , can be hard coded
      bseg-dmbtr. '10'      Amount, from the screen
      bseg-wrbtr. '10'     Amount, from the screen
      bseg-pswbt. '10'     Amount, from the screen
      bseg-pswsl. 'EUR'      currency, from the screen
      bseg-altkt. '0000120100'
      bseg-vorgn. 'RFBU'      constant , can be hard coded
      bseg-kokrs. '1000'       Customer account number
      bseg-xkres. 'X'      constant , can be hard coded
      bseg-xopvw. 'X'      constant , can be hard coded
      bseg-hkont. '0000140000'
      bseg-xbilk. 'X'      constant , can be hard coded
      bseg-fipos. '9620'      constant , can be hard coded
      bseg-lokkt. '0000140000'
      bseg-nebtr. '10'       Amount, from the screen
      bseg-xauto. 'X'      constant , can be hard coded
      bseg-xzahl. 'X'      constant , can be hard coded
      bseg-saknr. '0000140000'
      bseg-zfbdt. '20070116' Invoice document date
      bseg-hwmet. 'A'      constant , can be hard coded
      bseg-kkber. '1000'      Customer account number
      bseg-agzei. '1'      constant , can be hard coded
Step 2. Call FI_DOCUMENT_PROCESS
Import Parameters
I_GJAHR     LIKE     TRWCA- YEAR
I_PROCESS     LIKE     TRWPR-PROCESS
I_EVENT     LIKE     TRWPR-EVENT
Tables
T_BKPF          LIKE     BKPF
T_BSEG          LIKE     BSEG
T_BSEGZ     LIKE     BSEGZ
T_AUSZ3     LIKE     AUSZ_CLR
T_AUSZ4     LIKE     AUSZ_CLR_ASGMT
T_ACCIT_EXT     LIKE     ACCIT_EXTENSION
Values to populate import parameters
      i_gjahr                 = '2007'     Fiscal year from the screen
      i_process              = 'BELEG'    Constant, can be hard coded
      i_event                  = 'CLOSE'   Constant, can be hard coded
Table xausz3.
          ausz3-agzei. '1'       Constant, can be hard coded
       ausz3-waers. 'EUR'     Currency from the screen
       ausz3-bukrs. '1000'     Company Code
       ausz3-belnr. '1800000076' Document number from the screen
       ausz3-gjahr. '2007'        Fiscal Year
       ausz3-buzei. '001'
       ausz3-shkzg. 'S'          Constant, can be hard coded
       ausz3-dmbtr. '10'         Amount, from the screen
       ausz3-wrbtr. '10'           Amount, from the screen
       ausz3-koart. 'D'             Constant, can be hard coded
Step 3. Call FI_DOCUMENT_PROCESS
Import Parameters
I_GJAHR     LIKE     TRWCA- YEAR
I_PROCESS     LIKE     TRWPR-PROCESS
I_EVENT     LIKE     TRWPR-EVENT
Tables
T_BKPF          LIKE     BKPF
T_BSEG          LIKE     BSEG
T_BSEGZ     LIKE     BSEGZ
T_AUSZ3     LIKE     AUSZ_CLR
T_AUSZ4     LIKE     AUSZ_CLR_ASGMT
T_ACCIT_EXT     LIKE     ACCIT_EXTENSION
Values to populate import parameters
      i_gjahr                 = '2007'          Fiscal year from the screen
      i_process              = 'BELEG'         Constant, can be hard coded
      i_event                  = 'PROJECT'       Constant, can be hard coded
   I_AUGLV           = 'EINGZAHL' Constant, can be hard coded
Step 4. Call POST_DOCUMENT
Import Parameters
I_BKDF     LIKE     BKDF
I_UF05A     LIKE     UF05A
I_GENER     LIKE     T020-GENER
I_AUGLV     LIKE     T041A-AUGLV
Tables
T_AUSZ1     LIKE     AUSZ1
T_AUSZ2     LIKE     AUSZ2
T_AUSZ3     LIKE     AUSZ_CLR
T_AUSZ4     LIKE     AUSZ_CLR_ASGMT
T_BKP1          LIKE     BKP1
T_BKPF          LIKE     BKPF
T_BSEC          LIKE     BSEC
T_BSED          LIKE     BSED
T_BSEG          LIKE     BSEG
T_BSET          LIKE     BSET
T_BSEU          LIKE     BSEU
Values to populate import parameters
Table xausz1
    xausz1-belnr. '1800000076'    Document number from the screen
    xausz1-bukrs. '1000'            Company code from the screen
    xausz1-gjahr. '2007'            Fiscal year from the screen
    xausz1-buzei. '001'            Constant , can be hard coded
Table xausz2
        ausz2-bukrs. '1000'             Company code from the screen
        ausz2-aktio. 'A'                Constant , can be hard coded
        ausz2-augbl. '1400000054'      Posted document number..from the function NUMBER_GET_NEXT(Dynamically generated unique number)
        ausz2-augdt. '20070118'           Posting Date from the screen
        ausz2-auggj. '2007'           Fiscal Year from the screen
Table xbkpf
First record of the internal table zbkpf has to be modified with the dynamically generated document number.
Xbkpf-belnr. 1400000054
Table xbkp1
xbkp1-currj     '2007'   Fiscal year, from the screen
Table xbseg
Following fields in the table xbseg has to be modified before passing to this function module.
Record 1
   TO wa_bseg1-belnr. '1400000054' Dynamically generated number
   TO wa_bseg1-zuonr. '20070116'   Document Date from the screen
Record 2
   bseg1-belnr. '1400000054' Dynamically generated number
   bseg1-augdt. '20070118'   Posting date from the screen
   bseg1-augcp. '20070118'   Posting date from the screen
   bseg1-augbl. '1400000054' Dynamically generated number
bseg1-zuonr. '14000000542007' Concatenating dynamically generated number                                   and fiscal year
   bseg1-kunnr. '1000'        Customer number from the screen
Table Xbseu
Record 1
bseu-waers     'EUR'      Currency from the screen
Record 2
bseu-waers.      'EUR'            Currency from the screen
bseu-xzver.      'X'            Constant Hard coded
Step 5. Call FI_DOCUMENT_PROCESS
Import parameters
I_GJAHR     LIKE     TRWCA-TOYEAR
I_PROCESS     LIKE     TRWPR-PROCESS
I_EVENT     LIKE     TRWPR-EVENT
I_AWTYP     LIKE     ACCHD-AWTYP
I_AWREF     LIKE     ACCHD-AWREF
I_AWORG     LIKE     ACCHD-AWORG
I_AWSYS     LIKE     ACCHD-AWSYS
Tables
T_BKPF     LIKE     BKPF
Values to populate import parameters
i_gjahr           = '2007'      Fiscal Year from the screen
i_process         = 'BELEG'      Constant
i_event           = 'POST'      Constant
i_awtyp           = 'BKPF'      Constant
i_awref           = '1400000054'Dynamically generated posting doc number
i_aworg           = '10002007'      Concatenate comp code and Fiscal Year
i_awsys           = 'ECCCLNT800' Constant.

Post Incoming Payments:Distribute Differences

When Accounts Receivable applies incoming payments, if a customer does not pay an invoice in fullt, they will distribute the difference . . . we will assign our own identifier and assign a reason code. A document is created with Posting Key 06. However, there are no terms assigned to that document. Our Accounts Receivable group would like the terms to always default a certain terms code. Is there a way to set this up in configuration . . . We know how to manually add it, but that is alot of work.
BSEG-ZTERM
Thanks,
Diane

Substitution:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/27/06e23954d9035de10000000a114084/frameset.htm

Error posting incoming payments (f-28)

Hello SAP Gurus,
When trying to post a customer payment I keep getting the following error message " The trading partner entered in account xxxxx cocdxx is not valid.
Any ideas?
Many Thanks

Hi Rup,
Field trading partner (-> BSEG-VBUND) of the company code clearing line items is filled
with the company (-> T001-RCOMP / Tr. OBY6) of the other company code, and if the account master data of the company code clearing account contain a trading partner which is different from this company,
error message F5 583 ('Business transaction cannot be processed
by consolidation') is raised as the trading partner customizing
is inconsistent.
Also for FI postings an error message is raised if the account
master data of the company code clearing account contain a
trading partner which is different from the company (-> T001-RCOMP)
of the other company code, and the posting is not possible. This
is the default system behavior. Such a FI posting is only possible
if the corresponding error message F5 636 ('The trading partner
entered in account & & is not valid') is switched off in transaction
OBA5.
Please have a look at the long text of error message F5 636:
Diagnosis
You have entered a cross-company code transaction. The system
should now automatically generate a clearing posting for account &
in company code &. The system determines the trading partner for
this line item from the company code to which the clearing posting
is made. This trading partner must be the same as that in the
account master record.
Please also check OBYA if any incosistency.
Regars,
Reka

Incoming payment by F-28: Reason code error while posting

Hello everyone,
I want to post Incoing Payment using F-28 net of TDS. I want the separate GL account to be picked up automatically for the difference when I enter the Reason Code 003.
I did the following customization for the same.
1. Financial Accounting> Accounts Receivable and Accounts Payable> Business Transactions>Incoimng Payments> Incoming Payments Global Settings>Overpayment/Underpayment> Define Reason Codes:- Here I selected the Indicator 'C' for reason code 003 which is for "Indicator: Charge off difference via separate account". The reason code 003 is for TDS Netted
2. Below the Define Reason Code node, I selected the node 'Define Accounts for Payment Differences' . Selected the key ' Rules' and selected the checkbox 'Reason Code'. Then clicked on 'Accounts' and enetered the desired GL account against the reason code '003'.
After doing the above customization I posted the Incoming payment using T code F-28. I entered the difference in the field 'Difference Posting'. Then entered reason code '003' which is for 'TDS netted' in the field 'Reason Code'. Now, I am getting the follwoing error.
Reason codes with automatic charge-off are not permitted here
Message no. F5605
Diagnosis
The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose. Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
System Response
The reason code entered is not accepted.
Procedure
You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.
How can I proceed ahead?
Thanks and Regards,
Pradnya

Hi Saulo,
Thanks for ur reply.
I had alreay done the config in OBXL and OBBE. Only thing I wanted to know is while posting Incoming Payment by F-28, how to use this reason code.
Ur reply was a gr8 help for me.
Regards,
Pradnya

Background Journal entry for Incoming payment

Dear Experts,
Would you please help me in how to get the journal entry for an incoming payment entered as "payment on account".
The relationship map does not show this, but I can see the credit entry for the customer is passed.
same happens for incoming payment made for specific AR invoices.
SAP Doc says...
Result
An incoming payment document is created.
A journal entry that credits the customer and the tax accounts (if tax is involved), and debits the receivable account, is created.
The journal entries of the incoming payments and the paid invoices are reconciled.
The paid invoices are closed; they no longer appear in the Open Items list and in the Incoming Paymentswindow as documents for payment.
So how to check the journal entries for incoming payments.
Regards
Message was edited by: Suman Roy

Hi,
To see journal entry, drill down arrow at transaction no of incoming payment window.
Thanks & Regards,
Nagarajan

F-28 Incoming payment BSEG-XREF1/2 & BSEG-XREF3 grayed out on clearing line

Similar Messages

Maybe you are looking for