Lockbox error while posting customer payments

Hello,
I am testing the lockbox file upload and the system was able to locate the Customer number but while clearing customer, I am getting an error saying
No payment advices were found
Message no. F5664
I am trying to edit payment advice and I am getting the error as below
Payment advice 01 10000000 does not exist for account 110006 C850
Message no. FA006
Please let me know why this error is coming.
Thank You.
Edited by: Raghavaa on Dec 26, 2011 8:17 PM

I have found the cause and solution to this problem.
This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
This was resolved by splitting the IDOC into 2.
The solution is to First post only the KNA1 segment and create the customer.
In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”:  you would have got the KUNNR after the first step.
Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC. 
I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
Cheers
Venkat

Similar Messages

  • Error while posting Incoming Payment.

    Hi
    I Got this error while posting Incoming Payment. What do this Error Mean. How to solve it.
    Error:
    SBO_Application_ItemEventAP Object reference not set to an instance of an object
    Thank You

    Hi Gayathri,
    Try to disconnect the add-ons if any and then add the incoming payment.
    Regards,
    Vijay kumar

  • Error while posting Down Payment

    Hi,
    I got error while posting down payment in F-48. the error was "Special G/L Indicator P is not defined for down payment".
    Thanks,

    Hello,
    "Special G/L Indicator P is not defined for down payment" because you have not maintained this indicator in your system. For maintain this you go to TC: OBYR, dbl down payment indicator P, , give your chart of accounts and press enter. Here you have to give normal Recon A/c and Alternative Recon A/c and save it. Now, go to TC: F-48 and you will able to post it now.
    Thanks
    Para

  • Error while posting Incoming payments from customers

    Hi Experts,
                      when i am trying to post Incoming payments from customers in F-28,The payment difference amount is Rs 5.
    while simulating the following error 
    "TAX CODE C2 FOR COUNTRY IN HAS BEEN DELETED OR INCORRECTLY CHANGED"
    MESSAGE NO.FS201

    Hi,
    OBZT just controls the display of the various tax codes in the drop down list if MIRO/ FB60 etc.
    You need to maintain the atx coe correctly in FBZP. Go to FBZP and in this tax code and check whether the tax rates etc. have been defined correctly for it.
    Regards,
    SDNer

  • Error while posting Customer with Multiple sales areas using DEBMAS05.

    Dear experts,
    We are generating IDOCS vis SAP DS for posting Customer master. The message type used is DEBMAS and basic type is DEBMAS05.  we have a requirement to create 1 customer with multiple sales areas. However, we are ending up with a strange error:  "Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1". Despite the IDOC going into status 51, the customer gets created and the 1st sales area too. the 2nd sales area however is not created!  The IDOC data definitely contains Name1, otherwise the customer would not have been created in the first place.
    As the error message is related to the Address data, I also explored upon exploring this erorr further on the lines of Central Address management where in the ADRMAS and DEBMAS have to be passed together(IDOC Serialiization).  OSS Note (384462)  provides further details about this. One Important point from the note is: 
    "As you have to specify the logical name of the sending system among other things, SAP is not able to make any default settings in the standard systems. When you use the serialization groups delivered as a standard by SAP, the address objects are imported before the master objects.Thus the sequence address data before master objects must only be adhered to if one of the following points applies to your application:
    Such fields are set as required entry fields that are only provided by the BAS in the Customizing of the customer or vendor master.
    For your customers, contact persons exist to which a private address or a different business address is assigned.".
    This is not the case in our situation, as we do not have required entry fields in customizing that are only provided by the BAS, so the error is all the more confusing and I am not too sure what the cause is.
    If someone have experienced the same issue before and have found a solution to it, kindly help out.

    I have found the cause and solution to this problem.
    This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
    This was resolved by splitting the IDOC into 2.
    The solution is to First post only the KNA1 segment and create the customer.
    In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”:  you would have got the KUNNR after the first step.
    Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC. 
    I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
    Cheers
    Venkat

  • CO Object Assignment Error while posting Down Payment Request

    User is raising a Down Payment Request for the purchase of an Asset  through a Purchasing Document. This Asset Master has got the cost center and WBS Element assigned in it.
    System while saving the DP Request is throwing an error that “CO Account Assignments has different Profit Centers”
    I have also checked the cost center master but the profit center assigned there is correct only. Should I check the OKB9 settings ? If yes, for which GL Account do I need to check ? Where else can I check the CO Object Assignments for profit centers ?
    Requirement is critical. Please help.
    Thank you
    Ravi
    9849393564

    Hi,
    Good evening and greetings,
    Please have a look in GGB1 (Profit Centre Substitution), there may be some rule which is overriding the OKB9.
    Please reward points if found useful.
    Thanking you,
    With kindest regards,
    Ramesh Padmanabhan

  • Error while posting Incoming payment Cancellation entry in Current date

    Hi Experts
    Scenario
    Incoming payenet created on 31-05-2009
    Cancellation to be done on current date - 02-06-2009
    Current period selected as 010609 to 300609 in general settings
    When Incoming payment is cancelled - The system shows message ' The selected period is locked, Posting will be created in Current period', Continue - ?
    When YES is clicked - 'Date deviates from permissible range - (Journal Entry - posting date) Msg - (173-11)
    Document Numbering Journal entry is for Current period. (All the Journal entries are getting posted in current date, hence Document numbering is correct for Journal entry)
    PLEASE NOTE - The cancellation entry is needed to be passed on system date (02-06-2009) and NOT original document date of incoming payment (31-05-2009)

    Hi Sundaraja
    In 2007 B this issue does not arise, working FINE
    In 2005 B, there is option to set period as Current which I have done. and Active 'YES' & Locked 'NO'. Infact I have done this for all the periods of yr 2009-10.
    Still getting the error.
    Regards,
    Sid

  • Tax Error while posting Customer Invoice

    Hello Everyone,
    When I try to post a customer invoice using one of the default tax code (eg. 1O - output tax 10%), during simulation the system gives following error message with the item list as below: "Error message still exist - see error log". The error log shows following description -  Msg Type E : Item 003 must be corrected. 
    Itm PK Account    Account short text            Assignment         Tx           Amount
      1 01 100253     DDS SERVICES                                              1O          8.000,00
      2 50 800000     Sales revenues - dom                                    1O         7.272,73-
      3 50 175000     Output tax                                                      1O          727,27-
    Can anyone plz help me out as to why am I getting this error and what is the solution to it?
    Thanks,
    AMD

    Dear AMD008
    were you maintain properly in OB40 MWS (out put tax) relevant GL Account
    Note: are you using NEW GL please conform me
    Regards
    shankar

  • Error  while posting customer and vendor documents

    Hi
         Iam trying to post the entries in f-22 and f-43,its displaying that *No values for this selection* at account filed,
    I reconcile the customer and vendor accounts in fs00
    I assigns the account no's to customer and vendor master records
    Thank you.

    Hi Shilpa,
    Create Reconciliation account for customer using
    T-code: FS00
    in control data select as Reconciliation as customers
    and Field status group as G067
    and assign the same reconciliation in customer mater data
    Best Regards
    Ashish Jain

  • Error While Posting Outgoing Payment

    I am trying to post a test document using FBZ2 in a new company code. I am getting an error message " The entry XXXX (the new company code that I have configured) is missing in table T043G.
    Please let me know what does that mean and how I can resolve it.

    Hi,
    It menas you forgot the define Tolerances for Groups of Customers/Vendors
    T043G = Tolerances for Groups of Customers/Vendors
    Please follow the <b>T-code "OBA3"</b> and assign here Tolerance group with company code.
    If any doubt please let me know .
    if usefull assign points.
    Rgd
    Amit

  • 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

  • Tax code error while posting Planned delivery costs in Import Scenario

    Hi!!!!!
    I am getting on error while posting Planned delivery costs in MIRO for Import Purchase Order with zero value tax code v0. The error is
    "Tax code V0 country IN does not exist in procedure ZAXINN"
    For Import I defined a pricing procedure which contains all condition types for CVD, Ecess, SEcess, Additional Customs Duty and Others.
    While making Import PO im putting V0 tax code. I assigned the Tax Codes to the Company code.
    Please let me know what config is missing.
    Regards,
    Durga

    Is you ZAXINN assigned to the country India
    and is your taxcode (created in FTXP) created for country India?
    kr
    hakan

  • Error while creating customer account sites from backend

    I am creating Customer Account Sites using the TCA API from Toad.
    I am getting the following error
    The operating unit is either invalid or it cannot be derived. Please verify your Multi-Org profile options.
    The Operating unit has been defined.
    I am using the following code:
    DECLARE
    p_cust_acct_site_rec hz_cust_account_site_v2pub.cust_acct_site_rec_type;
    x_return_status VARCHAR2(2000);
    x_msg_count NUMBER;
    x_msg_data VARCHAR2(2000);
    x_cust_acct_site_id NUMBER;
    BEGIN
    p_cust_acct_site_rec.cust_account_id := 9462;
    p_cust_acct_site_rec.party_site_id := 5473;
    --p_cust_acct_site_rec.language := 'US';
    p_cust_acct_site_rec.org_id := 126;
    p_cust_acct_site_rec.created_by_module := 'TCA-EXAMPLE';
    hz_cust_account_site_v2pub.create_cust_acct_site(
    'T',
    p_cust_acct_site_rec,
    x_cust_acct_site_id,
    x_return_status,
    x_msg_count,
    x_msg_data);
    dbms_output.put_line(SubStr('x_return_status =
    '||x_return_status,1,255));
    dbms_output.put_line('x_msg_count = '||TO_CHAR(x_msg_count));
    dbms_output.put_line(SubStr('x_msg_data = '||x_msg_data,1,255));
    IF x_msg_count >1 THEN
    FOR I IN 1..x_msg_count
    LOOP
    dbms_output.put_line(I||'. '||SubStr(FND_MSG_PUB.Get(p_encoded =>
    FND_API.G_FALSE ), 1, 255));
    END LOOP;
    END IF;
    END;
    Thanks and Regards,
    K tanna

    Duplicate post.
    Error while creating customer account sites
    Error while creating customer account sites

  • Error while posting GR

    Hi
    We are facing a error while posting GR for a PO, error we are getting is "Account determination for entry 1000 FR3 0002 not possible".
    now we have checked that for the mentioned plant(val area) and co code val. grp code is 0002 only, and FR3 is picked by the system because of the condition type used (which is a Z020 and manual one).
    please help.
    regrds
    Yogesh

    Hi Yogesh,
    Maintain the GL account as mentioned by Ramki that will solve your problem. Or else u must not give an customs duty charges in PO then it will not hit that particular GL and you can post the GR
    Hope this helps.
    regards
    Anand.C

  • Error while posting FBS1 via BAPI

    Hi Experts,
    getting below error  while posting FBS1 via BAPI_ACC_DOCUMENT_POST
    TYPE ID                   NUMBER MESSAGE
    E   |RW                  |609   Error in document:  BKPF 10000022440GF3032010 TERCLNT303
    E   |RW                  |609   Error in document:  100000224 AC_DOC_NO
    FB03 Header values --
    Document Number 100000250        Company Code    40GF         Fiscal Year     2010
    Document Date   30.11.2010       Posting Date    30.11.2010   Period          11
    Currency  EUR
    FB03 Line item 1 ( posting key  40 )
    G/L Account     711014
    Company Code    40GF
    Amount          100,00  EUR
    Cost Center     40GF219001
    Quantity        0,000
    FB03 Line item 2 ( posting key  50 )
    G/L Account     167005
    Company Code    40GF
    Amount          100,00 EUR
    Assignment      20101130
    Text            ITEM TEXT 7
    Please tell me what i am missing in below code because of which i am getting  error  in return table
    FORM fill_header.
      CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
        IMPORTING
          own_logical_system = gd_documentheader-obj_sys.
      gd_documentheader-obj_type   = 'BKPF'.
      gd_documentheader-obj_key    = '10000022440GF3032010'.
      gd_documentheader-username   = sy-uname.
      gd_documentheader-header_txt = 'BAPI Test'.               "#EC NOTEXT
    gd_documentheader-obj_key_r  =
    GD_DOCUMENTHEADER-reason_rev =  '05' .
      gd_documentheader-comp_code  = '40GF'.
    GD_DOCUMENTHEADER-AC_DOC_NO  =  '100000224' .
      gd_documentheader-fisc_year  = '2010'.
      gd_documentheader-doc_date   = sy-datum.
      gd_documentheader-pstng_date = sy-datum.
    GD_DOCUMENTHEADER-TRANS_DATE =
    GD_DOCUMENTHEADER-VALUE_DATE =
    GD_DOCUMENTHEADER-FIS_PERIOD = '11' .
    GD_DOCUMENTHEADER-DOC_TYPE   = 'SA' .
    GD_DOCUMENTHEADER-REF_DOC_NO =
    GD_DOCUMENTHEADER-COMPO_ACC  =
      gd_documentheader-bus_act    = 'RFBU'.
    ENDFORM.                    "fill_header
    FORM fill_currencyamount.
      CLEAR T_currencyamount.
      T_currencyamount-itemno_acc   = 1.
      T_currencyamount-curr_type    = '00'.
      T_currencyamount-currency     = 'EUR'.
      T_currencyamount-amt_doccur   = -100.
      APPEND T_currencyamount.
      CLEAR T_currencyamount.
      T_currencyamount-itemno_acc   = 2.
      T_currencyamount-curr_type    = '00'.
      T_currencyamount-currency     = 'EUR'.
      T_currencyamount-amt_doccur   = '100'.
      APPEND T_currencyamount.
      CLEAR T_currencyamount.
    ENDFORM.                    "fill_currencyamount
    FORM fill_accountgl.
      CLEAR T_accountgl.
      T_accountgl-itemno_acc     = 1.
      T_accountgl-gl_account     =  '0000711014'.
      T_ACCOUNTGL-ACCT_TYPE      =  'S' .
      T_ACCOUNTGL-DOC_TYPE       =  'SA' .
    T_accountgl-DE_CRE_IND     =  'S' .
    T_accountgl-tax_code       = 'V1'.
    T_ACCOUNTGL-ACCT_KEY       =
      T_accountgl-item_text      = 'BAPI Test G/L line item'.  "#EC NOTEXT
    T_ACCOUNTGL-BUS_AREA       =
    T_accountgl-costcenter     = '40GF219001' .
    T_ACCOUNTGL-ORDERID        =
    T_ACCOUNTGL-MATERIAL       =
    T_ACCOUNTGL-QUANTITY       =
    T_ACCOUNTGL-BASE_UOM       =
    T_ACCOUNTGL-BASE_UOM_ISO   =
    T_ACCOUNTGL-PLANT          =
      T_accountgl-profIT_ctr     =  'S001'  .
    T_ACCOUNTGL-WBS_ELEMENT    =
    T_ACCOUNTGL-BILL_TYPE      =
    T_ACCOUNTGL-DISTR_CHAN     =
    T_accountgl-ac_doc_no      =
    T_accountgl-acct_type      =
    T_accountgl-doc_type       =
    T_accountgl-comp_code      =  '40GF' .
    T_accountgl-func_area      =
    T_accountgl-plant          =
    T_accountgl-fis_period     = '11' .
    T_accountgl-fisc_year      = '2010' .
    T_accountgl-pstng_date     =
    T_accountgl-value_date     =
    T_accountgl-customer       =
    T_accountgl-vendor_no      =
    T_accountgl-costobject     =
    T_accountgl-acttype        =
    T_accountgl-val_area       =
    T_accountgl-po_number      =
    T_accountgl-po_item        =
      APPEND T_accountgl  to t_accountg2 .
      CLEAR T_accountgl.
      T_accountgl-itemno_acc     = 2.
      T_accountgl-gl_account     =  '0000167005'.
    T_ACCOUNTGL-STAT_CON       =
    T_ACCOUNTGL-REF_KEY_1      =
    T_ACCOUNTGL-REF_KEY_2      =
    T_ACCOUNTGL-REF_KEY_3      =
      T_ACCOUNTGL-ACCT_TYPE      =  'S' .
      T_ACCOUNTGL-DOC_TYPE       =  'SA' .
    T_accountgl-DE_CRE_IND     =  'H' .
    T_accountgl-tax_code       = 'V1'.
    T_ACCOUNTGL-ACCT_KEY       =
      T_accountgl-item_text      = 'ITEM TEXT 7'.  "#EC NOTEXT
    T_ACCOUNTGL-BUS_AREA       =
    T_accountgl-costcenter     = '40GF219001' .
    T_ACCOUNTGL-ORDERID        =
    T_ACCOUNTGL-MATERIAL       =
    T_ACCOUNTGL-QUANTITY       =
    T_ACCOUNTGL-BASE_UOM       =
    T_ACCOUNTGL-BASE_UOM_ISO   =
    T_ACCOUNTGL-PLANT          =
    T_accountgl-profIT_ctr     =  'S001'  .
    T_ACCOUNTGL-WBS_ELEMENT    =
    T_accountgl-ac_doc_no      =
    T_accountgl-acct_type      =
    T_accountgl-doc_type       =
    T_accountgl-comp_code      =  '40GF' .
    T_accountgl-func_area      =
    T_accountgl-plant          =
    T_accountgl-fis_period     = '11' .
    T_accountgl-fisc_year      = '2010' .
    T_accountgl-pstng_date     =
    T_accountgl-value_date     =
    T_accountgl-customer       =
    T_accountgl-vendor_no      =
    T_accountgl-costobject     =
    T_accountgl-acttype        =
    T_accountgl-val_area       =
    T_accountgl-po_number      =
    T_accountgl-po_item        =
      APPEND T_accountgl  to t_accountg2 .
    ENDFORM.                    "fill_accountgl

    Hi Experts,
    getting below error  while posting FBS1 via BAPI_ACC_DOCUMENT_POST
    TYPE ID                   NUMBER MESSAGE
    E   |RW                  |609   Error in document:  BKPF 10000022440GF3032010 TERCLNT303
    E   |RW                  |609   Error in document:  100000224 AC_DOC_NO
    FB03 Header values --
    Document Number 100000250          Company Code    40GF         Fiscal Year     2010
    Document Date   30.11.2010           Posting Date    30.11.2010   Period          11
    Currency  EUR
    FB03 Line item 1 ( posting key  40 )
    G/L Account     711014
    Company Code    40GF
    Amount          100,00  EUR
    Cost Center     40GF219001
    Quantity        0,000
    FB03 Line item 2 ( posting key  50 )
    G/L Account     167005
    Company Code    40GF
    Amount          100,00 EUR
    Assignment      20101130
    Text            ITEM TEXT 7
    Please tell me what i am missing in below code because of which i am getting  error  in return table
    FORM fill_header.
      CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
        IMPORTING
          own_logical_system = gd_documentheader-obj_sys.
      gd_documentheader-obj_type   = 'BKPF'.
      gd_documentheader-obj_key    = '10000022440GF3032010'.
      gd_documentheader-username   = sy-uname
    gd_documentheader-obj_key_r  =
    GD_DOCUMENTHEADER-reason_rev =  '05' .
      gd_documentheader-comp_code  = '40GF'.
    GD_DOCUMENTHEADER-AC_DOC_NO  =  '100000224' .
      gd_documentheader-fisc_year  = '2010'.
      gd_documentheader-doc_date   = sy-datum.
      gd_documentheader-pstng_date = sy-datum.
    GD_DOCUMENTHEADER-FIS_PERIOD = '11' .
    GD_DOCUMENTHEADER-DOC_TYPE   = 'SA' .
      gd_documentheader-bus_act    = 'RFBU'.
    ENDFORM.                    "fill_header
    FORM fill_currencyamount.
      CLEAR T_currencyamount.
      T_currencyamount-itemno_acc   = 1.
      T_currencyamount-curr_type    = '00'.
      T_currencyamount-currency     = 'EUR'.
      T_currencyamount-amt_doccur   = -100.
      APPEND T_currencyamount.
      CLEAR T_currencyamount.
      T_currencyamount-itemno_acc   = 2.
      T_currencyamount-curr_type    = '00'.
      T_currencyamount-currency     = 'EUR'.
      T_currencyamount-amt_doccur   = '100'.
      APPEND T_currencyamount.
      CLEAR T_currencyamount.
    ENDFORM.                    "fill_currencyamount
    FORM fill_accountgl.
      CLEAR T_accountgl.
      T_accountgl-itemno_acc     = 1.
      T_accountgl-gl_account     =  '0000711014'.
      T_ACCOUNTGL-ACCT_TYPE      =  'S' .
      T_ACCOUNTGL-DOC_TYPE       =  'SA' .
      T_accountgl-item_text      = 'BAPI Test 1'.
    T_accountgl-costcenter     = '40GF219001' .
      T_accountgl-profIT_ctr     =  'S001'  .
    T_accountgl-fis_period     = '11' .
    T_accountgl-fisc_year      = '2010' .
      APPEND T_accountgl  to t_accountg2 .
      CLEAR T_accountgl.
      T_accountgl-itemno_acc     = 2.
      T_accountgl-gl_account     =  '0000167005'.
      T_ACCOUNTGL-ACCT_TYPE      =  'S' .
      T_ACCOUNTGL-DOC_TYPE       =  'SA' .
      T_accountgl-item_text      = 'ITEM TEXT 7'.
    T_accountgl-comp_code      =  '40GF' .
    T_accountgl-fis_period     = '11' .
    T_accountgl-fisc_year      = '2010' .
      APPEND T_accountgl  to t_accountg2 .
    ENDFORM.                    "fill_accountgl

Maybe you are looking for