Error in posting payment document

While posting outgoing payments through T-code F-53, the client received the error message ‘The entry 1210 is missing in table T043G’ and the system did not allow the posting payment document.
Please anybody can give me solution for this.

Hi,
       even if we are facing similiar kind of problems , I will give you some info hope this helps.
    for technial perspective print character will be determined from table J_1ACHRDET  in the FM   J_1A_DET_CHARACTER, code is here
               SELECT SINGLE * FROM J_1ACHRDET
              WHERE J_1AFITPI = X_FITYPI
              AND   J_1AFFLAG = X_FFLAG
              AND   J_1AFITPR = X_FITYPR
              AND   J_1ATTYPE = LV_TTYPE.
               X_FITYPI = T001Z-PAVAL(2)    
               X_FFLAG = blank
               X_FITYPR = I_FITYP.             " I_FITYP is from internal table VBRK-J_1AFITP ( tax type)
                LV_TTYPE  is from  J_1ACHRDET-J_1ATTYPE.  " type of transaction based on land and  region values are D or  E or  I
          branch will be determined from TVTA table
          SAP will apend   character branch and sequence number and gives official numbering
    for functional perspective you need to do configuration based on your requirements
here is the path is SPRO -> Cross-Application Components -> General Application Functions -> Cross-Application Document Numbering -> Argentina
please add point if this is useful

Similar Messages

  • Possible to clear vendor open item against already posted payment document?

    Hi
    Can you advise if it is possible to clear an open item against already posted payment/clearing doc? Here is the background to the scenario:
    An invoice was posted with transaction FB60. This was subsequently picked up in the payment run F110 and cleared by payment document number 200005678. The item went to the bank on the paymnet file and was paid out to the vendor. The transaction reference, which appeared on the incoming bank statemnet was the payment document number 200005678.
    Subsequently it was discovered that the original invoice should have been posted with reference to a PO using MIRO. The requirement now is to reverse the paymnet documnet 200005678 in SAP, then reverse the document that was posted using FB60. After this the invoice will be posted using MIRO. This will create an open item on the vendor account.
    This item will not be piad out again. Therefore the requirement is to try clear that open item against the previously posted payment document 200005678.
    Is there any way to clear this vendor open item against the originally posted payment document 200005678?? Or any other advice on how this scenario can be handled in SAP?
    Thank for your help.
    Mike

    Hi,
    I tried that option in our test system. I ran FBRA and entered Paymnet Documnet Number (+Clearing Doc Number), Company Code, Fiscal Year.
    Then chose menu option Clearing -> Reset Cleared Items.
    The system pops up a window asking for a reversal reason and reversal date.  I use 01 and posting date of today.
    The system now posts another cleared document. That document places the invoice as an open item on the vendor account. It does not place the Payment Document as an open item on the account.
    When I go to F-44 only the open vendor invoice is showing there. There is no open paymnet document.
    Is there perhaps some configuration setting that stops the placement of the paymnet document as an open item when reset?
    Thanks for your help again.

  • Runtime error while posting a document (FB70/FBS1)

    Hi
    I am getting a runtime error while posting a document through FB70 or FBS1 .
    The erro description tells The type "CL_BCS_OBJHEAD" is unknown.
    And the program dumps in Function module SO_KPRO_DECIDE.
    Has any one faced this problem?

    Hi,
    Please check the psoting date and also the reversal  date in FBS1. Please check when you have posted the document and when you want ot reverse the same.
    Thank you,
    Shilpa.

  • FA Retirement- 21151: error while posting asset document: '100000039'

    Hello Experts,
    I have a client who encountered this error during fixed asset retirement - scrapping.
    After selecting the asset to be retired, sap did not assign an account in the account column, but the user
    was able to save the document.  After saving it, the user needs to retire again another asset - scrapping, but the document would not be saved because of this error: 21151: error while posting asset document '100000039'.  The document number the systems is referring to is the last document saved but sap did not assign an account code.
    Please help. My client is using sap b1 8.81 patch5.
    Regards,
    Luz

    Hi Too Mui Hwee,
    What we did is to put letters on the number so the series will continue example there is already 100333, 100334, 100335 since the error is encountered from 100333. We add 100333A, 100334A, 100335A.
    Thanks

  • Error while posting billing document to Accounting

    Hi,
    We are getting an error when posting Billing document to Accounting .Eror "The document type is relevant for VAT.Please inset a VAT code in postings.
    Thanks in advance.

    Dear Ravinder
    Go to VF02, input the billing document and execute.  Now from the top menubar, click on Goto <> Header <> Header.   There check what pricing procedure is flowing.
    Now go to V/08, select that pricing procedure and check whether you have maintained the condition type for VAT.  I believe you have not maintained and hence, the error. Include the VAT condition type and create a fresh sale order.
    Meanwhile, you have to reverse the billing document via VF11, reverse PGI via VL09 and delete the delivery document. 
    thanks
    G. Lakshmipathi

  • IDOC for F-53 Posting Payment Document ?

    Dear All,
    Please advise which IDOC i can use for Posting Payment Document ? I have scenario to send the IDOC payment document to others SAP system.
    Thank You and Best Regards
    Fernand

    I guess you can use the same messagetype for outgoing payments:
    report  zzinbound_idoc.
    data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
    data: g_edidd like edi_dd40 occurs 0 with header line.
    data: g_e1bpache09 like e1bpache09.
    data: g_e1bpacar09 like e1bpacar09.
    data: g_e1bpaccr09 like e1bpaccr09.
    data: g_e1bpacgl09 like e1bpacgl09.
    parameter: mode type c default 'A'.
    refresh: g_idoc_control_record, g_edidd.
    clear:   g_idoc_control_record, g_edidd.
    *-Build Control Record -*
    g_idoc_control_record-mestyp  = 'ACC_DOCUMENT'.   "Message type
    g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
    g_idoc_control_record-direct  = '2'.              "Direction
    * Receiver
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
        g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-rcvprt = 'LS'.             "Partner type
    g_idoc_control_record-rcvpfc = ''.               "Partner function
    * Sender
    g_idoc_control_record-sndpor = 'FILE_PORT'.      "Port
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-sndprt = 'LS'.             "Partner type
    g_idoc_control_record-sndpfc = ''.               "Partner function
    g_idoc_control_record-refmes = 'Customer clearing'.
    append g_idoc_control_record.
    *-Build Idoc Segments -*
    *-------E1BPACHE09 (HEADER)
    clear g_edidd.
    g_edidd-segnam = 'E1BPACHE09'.
    g_edidd-segnum = 1.
    clear g_e1bpache09.
    g_e1bpache09-bus_act    = 'RFBU'.
    g_e1bpache09-doc_date   = sy-datum.
    g_e1bpache09-doc_type   = 'DZ'.
    g_e1bpache09-comp_code  = 'BP01'.
    g_e1bpache09-pstng_date = sy-datum.
    g_e1bpache09-username   = sy-uname.
    g_e1bpache09-ref_doc_no = '0090000025'.
    move g_e1bpache09 to g_edidd-sdata.
    append g_edidd.
    *-------E1BPACGL09 (ACCOUNT GL) (Debit) (Factoring Partner)
    clear g_edidd.
    g_edidd-segnam = 'E1BPACGL09'.
    g_edidd-segnum = 2.
    clear g_e1bpacgl09.
    g_e1bpacgl09-itemno_acc = 0000000002.
    g_e1bpacgl09-gl_account = '0000157000'.
    g_e1bpacgl09-customer   = 'C6130'.
    g_e1bpacgl09-acct_type  = 'S'.
    g_e1bpacgl09-comp_code  = 'BP01'.
    *g_e1bpacgl09-costcenter = '0000001602'.
    move g_e1bpacgl09 to g_edidd-sdata.
    append g_edidd.
    *-------E1BPACAR09 (ACCOUNT RECIEVABLE) (Credit) (Customer)
    clear g_edidd.
    g_edidd-segnam = 'E1BPACAR09'.
    g_edidd-segnum = 3.
    clear g_e1bpacar09.
    g_e1bpacar09-itemno_acc = 0000000001.
    g_e1bpacar09-customer  = 'C6110'.
    g_e1bpacar09-comp_code  = 'BP01'.
    g_e1bpacar09-alloc_nmbr = '0090000025'. "BSEG-ZUONR ?
    move g_e1bpacar09 to g_edidd-sdata.
    append g_edidd.
    *-------E1BPACCR09 (CURRENCY AMOUNT)
    clear g_edidd.
    g_edidd-segnam = 'E1BPACCR09'.
    g_edidd-segnum = 4.
    clear g_e1bpaccr09.
    g_e1bpaccr09-itemno_acc = 0000000001.
    g_e1bpaccr09-curr_type  = '00'.
    g_e1bpaccr09-currency   = 'NOK'.
    g_e1bpaccr09-amt_doccur = -111.
    move g_e1bpaccr09 to g_edidd-sdata.
    append g_edidd.
    g_e1bpaccr09-itemno_acc = 0000000002.
    g_e1bpaccr09-curr_type  = '00'.
    g_e1bpaccr09-currency   = 'NOK'.
    g_e1bpaccr09-amt_doccur = 111.
    move g_e1bpaccr09 to g_edidd-sdata.
    append g_edidd.
    *-Create idoc -*
    *-Syncronous
    if mode = 'S'.
      call function 'IDOC_INBOUND_SINGLE'
        exporting
          pi_idoc_control_rec_40              = g_idoc_control_record
    *     PI_DO_COMMIT                        = 'X'
    *   IMPORTING
    *     PE_IDOC_NUMBER                      =
    *     PE_ERROR_PRIOR_TO_APPLICATION       =
        tables
          pt_idoc_data_records_40             = g_edidd
        exceptions
          idoc_not_saved                      = 1
          others                              = 2.
      if sy-subrc  0.
        message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      endif.
    *-Asynchronus
    else.
      call function 'IDOC_INBOUND_ASYNCHRONOUS'
        in background task as separate unit
        tables
          idoc_control_rec_40 = g_idoc_control_record
          idoc_data_rec_40    = g_edidd.
      commit work.
    endif.
    write: / 'Goto transaction F.13'.
    Edited by: Erik Hoven on Feb 24, 2009 12:55 PM

  • Error in posting Inventory documents for a serialized material

    hi.,
    Can someone update me the reason for:
    1. Error in posting inventory documents for a serialized material
    What are the steps to be followed during the
    1. Creation of Serialized material
    2. Creating a Purchase document for a serialized material
    3. Generating a G/R for a serialized material.
    4. Generating an inventory document for a serialized material.
    Any update is much appreciated.
    Tx.
    Mahesh

    Hello Mahesh,
    Let me try to answer your queries.
    <b>1. Generally, how does the flow of Cycle counting go w.r.t to the Indicators A.B.C and D which has been configured in OMCO.
    Would that be as per the Consumption/usage of the materials?</b>
    The following link will help to understand the cycle count process
    http://help.sap.com/saphelp_46c/helpdata/en/4d/2b8e3d43ad11d189410000e829fbbd/frameset.htm
    <b>2. How are the indicators of A,B,C,D to be set up for the other materials in the particular plant which have not been fixed as CC.</b>
    If you run the MIBC (Set ABC indicator) report, it will automatically set the ABC indicator based on your selection parameter.
    <b>3. How does the system take up the inventory count for materials that have not been flagged as CC Fixed.</b>
    Cycle counting inventory will be carried out only for the material with ABC indicator for cycle count, if you exclude the material from MIBC report or manual ABC setting then that material will not be considered under cycle count when you execute MICN report to create cycle count inventory doc.
    <b>4. How does the sytem take up the inventory count for materials for materials which have been flagged as Fixed.</b>
    Material with CC fix indicator means when MIBC report will not change CC indicator for that material with fix indicator, so when you run MICN report at that time system will take last inventory date from MARD table for that material and calculate the next due date based on ABC indicator in material.
    Hope this helps.
    Regards
    Arif Mansuri
    Frankly speaking I also dont know the process for rewarding the points, I put only one question so far but with no reply, so never got a chance to assign rewards.
    But there is a way always, this link will help you..
    https://www.sdn.sap.com/irj/sdn/crphelp#posted

  • Error while posting downpayment documents in transaction f-53

    Hi,
    I am sending this mail once again as my earlier two messages was blocked by moderators. I don't know the reason for the same. I didn't used any mocky languages or abusing words.  Normally the questions are blocked if the total no of postings are unmarked as 'answered' exceeds 10. But in my case it is not exceeded the limit.  Any way I am posting the question once again,  and I hope I will get  some helpful support from  SAP community network.
    We have different company in our configurations and in some cases we were using same document types in different company codes. For easy tracking from this fiscal year onwards we assigned separate document types for individual company codes. When we use tcode f-53 or 5.58  in the initial screen after specifying company code and  document type and the bank account , business area and vendor account in the next screen normally the open items for the given vendor should appear. but in our case it is giving error  message f-5150 ' number range for the document type xx is not maintained for company code 'xxx' for this fiscal year 2009' and we are not albe to proceed. Please give any valid solutions for the same. I hope I didn't used any abusing words in this. I will explain the problem with an example given below.
    doc type : xx in company code com1 ( number range defined)
    doc type : zz in company code com2 ( number range defined)
    suppose we are using these document types for the outgoing payments in two diffent company codes and we have common vendor v0001 for both.
    now in tcode f-53 or f-58 if you are posting for the first company with doctype 'xx' and company com1 and if we specify vendor account, normally as per sap all the open items pertaining to the vendor / compnay code will display, but in our case it is displaying the next screen with an error stating that ' number range not defined for document type xx in company code COM2'
    which is not correctl. In this screen we cannot change the company code to 'COM1' which is correct.
    This is same in the case of customer and GL account.
    How to solve this issue?
    Regards
    SK

    Hi Dinesh,
    Since you have same Vendor for your both the company codes and you have different document types for both company codes and you are posting payment for company code com1 for this number range you have maintained as per document type number object, but you are using same vendor for both company codes so if maintain number range for same number object for company code com2, system will pick company code com1 number range at the time of postings through company code com1, so maintain same number range objects number range against company code com2 to avoid inconsistency.
    As per your given example you can check by posting through company code com2 with document type ZZ.

  • Error while posting parked documents

    HI ALL,
    After upgrade when we try to post the parked documents ,It calls FM :POSTING_INTERFACE_DOCUMENT"
    Inside it a call transaction is done using FBVB which throws error while posting for more than 4 withholding tax types.
    Error : Field WITH_DIALG-WT_BASE(5) does not exist in the screen SAPLFWTD 0100.
    On running BDC in foreground mode ,Error is happening when the withholding dialog opens and screen seems to be small to input all the tax codes.
    But in 4.6 c a bigger screen pops up and no error is thrwon.
    We have checked lots of thread and notes ,But nothing seems to be relevant or helpful in our case.
    Please check it.
    Thanks!

    Hi,
    Please follow as given below:
    1. Use T.Code KO31 and enter order and deactivate the control
    2. Then try to post the parked document
    3. And use T.Code KO30 and enter the order to activate the control
    Some times system will check budget availability which already commited for parked documents.
    Hope it will work.
    Chandu

  • Error while posting parked document

    Hi  all,
      We are in ECC 5.0.  While posting a parked invoice document, (created
    through MIRO), the system is giving an error saying, 'Account XXXXXX
    requires an assignment to a CO object . Msg. No. KI235) for Rounding off
    account. 
      This G/L account has a cost center assigned in OKB9 and there is no
    problem in the validity of the cost center and it is being displayed
    when the document is simulated.
      We are facing this problem only when posting a parked document. 
    While directly posting a document, there is no problem.
      Any suggestions?
    Regards,
    Sundar Rao

    Hi Paul,
    The error is occuring when I am posting a parked invoice document.  When I try and post it directly through MIRO, there is no problem.
    I am unable to understand your reply.  Can you please elaborate?
    Regards,
    Sundar Rao

  • Error while posting 561 Document

    Dear All
                Error while posting document with movement 561. "Account Determination for entry 999 BSA 6000 not possible."
    Even OBYC setting for that valuation class already assigned.
    please advice.
    Regards
    Kumar.

    Hello Anandhakumar ,
    please check whether you have assigned the Company code which you are using to controlling area with same chart of accounts and check the OMWD settings..
    and check the FS02 tCode in that the see the control data for currency and chart of accounts settings.
    it could solve your query.
    regards,
    Ninad Kshirsagar

  • TDS Challan error - while creating payment document

    Hi,
    I was trying to create With holding tax Challan through J1INCHLN.
    Following error occurred after simulating payment document - "Withholding tax lines are being cleared along with other line items"
    Please help in above matter.
    Thanks
    Deepak

    Dear,
    Please check with business users that are these manual reversal valid? See the username for these documents and also check which transaction was used whether it is FB08 or manual JV. If it was manual then reset these documents through FBRA and reverse it through FB08 because manual is not recommended.
    If reversal are not required then after resetting through FBRA run J1INCHLN, which must bring data and you will be able to create challan.
    Respective period means the period which you enter into J1INCHLN screen.
    Regards,
    Chintan Joshi

  • FBV0 - Error while posting prked document..

    Hi Team,
    I am getting the below error while trying to post a Parked Document in FBV0*
    Field BSEG-SECCO. does not exist in the screen SAPMF05A 0302
    Message no. 00349
    Diagnosis
    The specified field does not exist on the screen.
    Procedure
    Check your batch input data.
    Kindly assist on this...
    Thanks in Advance !!!!!!

    Hi,
    If you park a document using transaction FB01 or a relevant ENJOY transaction, all substitutions are run - in contrast to transaction FBV1, which is a parking transaction only. It is possible in this case to use substitution to fill fields that are not ready for input in the line item or that are not available.
    When you post the parked document using transaction FBV0, FBV0 with a list, or FIPP.POST, the posting is executed using CALL TRANSACTION. The system collects all data from the parked document and reprocesses the data for CALL TRANSACTION. A batch input runs in the background. This transfers all field contents from the parked document to the relevant screen fields. If a field that does not exist on the screen is to be filled, the system issues error message 00349.  You cannot post the document.
    Check your substitutions. Make sure that you never substitute fields in the parking that are not ready for input.
    Regards,
    Jigar

  • Error in Posting Accounting Document from invoice

    Hi,
    When i create invoice, the system gives error while creating accounting document as,
    "Tax code Y1 does not appear in any G/L account item".
    In my pricing procedure. i have two tax condition types. MWST and ZSED (copy of mwst). when i delete ZSED from my pricing procedure and then i create a sales order/delivery & finally invoice...then it works fine (Accuonting document is created successfully).
    i have assigned the gl accounts in vkoa. and MWST & ZSED goes to same gl account via MWS accounting key.
    although i have searched the forum for this issue, but that didnt resolved my issue.
    seeking your guidance.

    Dear Robert,
    I'm having same issue as yours.
    The requirement for us is if return sales in some order reason codes, then tax should be posted to different G/L other than the G/L defined in OB40(transaction MWS).
    After several test, found the system only recognize the G/L in OB40, won't touch setting in VKOA. As if I delete the GL in table T030R, SAP will issue an error requesting GL assignment.
    Please let me know if you have solved your issue! If yes, please share your solution! 
    Thanks in advance!

  • FI error while posting one document

    While posting the document(501 - gr w/o PO), i'm getting the error:
    "Account determination requires an CO object"
    I've maintained the material master with costing view and also assigned profit center.
    I Belive in  Obyc t-code, -- in GBB -- in general modification column.. key needs to be enabled with g/l account.
    Pls explain what is the general modification and what is the key for 501 - gr w/o po
    Thankyou

    hi
    Go to FS00
    enter GL account no & Comp Code.
    Click Change button
    You might have to seek help of an FI consultant to do so.
    Also in KA01 create this G/L account as a cost element against your controlling area assigned to your Chart of Accounts, you can do so by clicking on Extra's tab in transaction KA01
    Regards

Maybe you are looking for

  • How to use BAPI_HELPVALUES_GET with functional location

    I try to create an RFC connection searchhelp for my ECC system to the functional location table. I thought of using the bapi_helpvalues_get but I get stuck in determing the right input data I have found the right objectype in SWOI BUS0010 now I found

  • Can I use Remote app on iPad to control RENTED (read Rented) movies on Apple TV?

    I use the Remote App on my iPad to control movies on my Apple TV, but those are movies that I own and are resident on my home network. What about controlling a rented movie that is aquired through iTunes Store? I would like to be able to control rent

  • MBP 2012 - connecting to Imac 27" 2011

    Hi, Planning on buying the new MBP 2012 with Retina.  Wondering if I can connect it to my Imac 27" via thunderbolt and access the USB 3.0 of the Macbook?  In other words, I would connect a USB 3.0 card reader (Compact Flash, XQD etc.)  on the MBP  bu

  • Getting the error column not allowed here in jdbc

    i have got an error when using jdbc. i have inserted the data from taking java textfields. The error is:column not allowed here. how to rectify this? iam eagerly waiting for ur reply.

  • Need to add Polish option to character set menu in SAP Gui

    Basis Gurus, We have installed the Polish language on our unicode R/3 system and now need to add it as a character set option in the Gui menu. Menu Path: Customize Local Layout --> Character Set --> (Missing Option for Polish) I have searched OSS and