FBCJ Posting Error

Hi All,
When i am posting a cash journal ,i am facing following error.
' try again' and wheni click on the long text , there is a msg no F5A244. What is this message.? Its urgent.
Thanks a lot.
With Regards
SAPUSER5

Hi,
Please refer to SAP note 547837.
The object number range is not dependant on the year. I mean, with the
new year the number range will not be resetting, but the following
document number will be used. Therefore, to find the last number, you
just check in table TCJ_DOCUMENTS the higher document number independant
on the year. You should update in the number range status the last
number assigned + 1.
Also please check following
Please maintain it in IMG - Define Number Ranges for Numbering Groups.
Please refer to help document for it:
Define Number Ranges for Numbering Groups
Use
In this Customizing activity, you define number ranges for the cash
document numbering groups that you have created.
Mauri

Similar Messages

  • FBCJ posting error ABAP prg

    hai friends
         i have created on BAPI to FBCJ
         it is used to RECEIPT FROM BANK & PAYMENT TO BANK and its working fine
         i have created one RFC to posting the data.
          it posted only one record but i want to post all records. please rectified the error in the following conding
    *& Report  ZFBCJ_TEST_POSTING                                          *
    Report  ZFBCJ_TEST_POSTING  .
    DATA: it_advance TYPE TABLE OF ZFI_IBSADVANCE WITH HEADER LINE.
    DATA: NODATA_CHARACTER VALUE '/'.
    DATA: BDCDATA   LIKE TABLE OF BDCDATA     WITH HEADER LINE.
    data: BDCDATA1  LIKE TABLE OF BDCDATA     WITH HEADER LINE.
    DATA: MESSTAB   LIKE TABLE OF BDCMSGCOLL  WITH HEADER LINE.
    data:      MESSTAB1  LIKE TABLE OF BDCMSGCOLL  WITH HEADER LINE.
    DATA: IT_TEMP LIKE TABLE OF ZTEMPFBCJ WITH HEADER LINE.
    data: IT_TEMP type ZTEMPFBCJ.
    data: docu_dat like bkpf-bldat.
    data: docu_num like bkpf-xblnr.
    select single * into it_temp from ZTEMPFBCJ where comp = 'X'.
    *Capture whether a 'receipt' or 'payment' has been made in txn FBCJ
    SELECT single xblnr bldat  INtO (DOCU_NUM, DOCU_DAT) FROM bkpf
                      where xblnr = it_temp-REF_DOC_NO.
    IF DOCU_NUM <> it_temp-ref_doc_no.
    *LOOP AT IT_TEMP." WHERE COMP = 'X'.
    IF NOT IT_TEMP-PAYMENTS IS INITIAL.  "If a cash entry has been made
    perform bdc_dynpro      using 'SAPMFCJ0'                    '0100'.
    perform bdc_field       using 'BDC_OKCODE'                  '=CHCJ'.
    perform bdc_field       using 'BDC_CURSOR'              'ISCJ_E_POSTINGS-TRANSACT_NAME(01)'.
    perform bdc_field       using 'F_DISPLAY_PERIOD_LO'      IT_TEMP-DOCUMENT_DATE.
    perform bdc_field       using 'F_DISPLAY_PERIOD_HI'      IT_TEMP-DOCUMENT_DATE.
    perform bdc_dynpro      using 'SAPMFCJ0' '0050'.
    perform bdc_field       using 'BDC_CURSOR'               'TCJ_C_JOURNALS-CAJO_NUMBER'.
    perform bdc_field       using 'BDC_OKCODE'                  '=OK50'.
    perform bdc_field       using 'TCJ_C_JOURNALS-COMP_CODE'    '1000'.
    perform bdc_field       using 'TCJ_C_JOURNALS-CAJO_NUMBER'   IT_TEMP-CJ_NUMBER.
    perform bdc_dynpro      using 'SAPMFCJ0' '0100'.
    perform bdc_field       using 'BDC_CURSOR'             'ISCJ_E_POSTINGS-TRANSACT_NAME(01)'.
    perform bdc_field       using 'BDC_OKCODE'                  '=TODA'.
    perform bdc_dynpro      using 'SAPMFCJ0' '0100'.
    perform bdc_field       using 'BDC_OKCODE'                  '=SELE'.
    perform bdc_field       using 'BDC_CURSOR'                 'ISCJ_E_POSTINGS-TRANSACT_NAME(01)'.
    perform bdc_dynpro      using 'SAPMFCJ0' '0100'.
    perform bdc_field       using 'BDC_OKCODE'                   '=POST_ALL'.
    perform bdc_field       using 'BDC_CURSOR'                  'ISCJ_E_POSTINGS-TRANSACT_NAME(01)'.
    *perform bdc_field       using 'F_LINE_SEL'
    CALL TRANSACTION 'FBCJ' USING BDCDATA
                     MODE   'A'
                     UPDATE 'A'
                     MESSAGES INTO MESSTAB.
    *Values for 'MODE'
                "A: show all dynpros
                "E: show dynpro on error only
                "N: do not display dynpro
    *Values for 'UPDATE'
                "S: synchronously
                "A: asynchronously
                "L: local
    *UPDATE ZIBSCASHPAYMENTS SET PAYMT = ' '
    WHERE CJ_NO = IT_TEMP-CJ_NUMBER.
    ENDIF.
    IF NOT IT_TEMP-RECEIPTS IS INITIAL.  "If a cash entry has been made
    perform bdc_dynpro1      using 'SAPMFCJ0'                    '0100'.
    perform bdc_field1       using 'BDC_OKCODE'                  '=CHCJ'.
    perform bdc_field1       using 'BDC_CURSOR'                 'ISCJ_E_POSTINGS-TRANSACT_NAME(01)'.
    perform bdc_field       using 'F_DISPLAY_PERIOD_LO'          IT_TEMP-DOCUMENT_DATE.
    perform bdc_field       using 'F_DISPLAY_PERIOD_HI'           IT_TEMP-DOCUMENT_DATE.
    perform bdc_dynpro1      using 'SAPMFCJ0' '0050'.
    perform bdc_field1       using 'BDC_CURSOR'                    'TCJ_C_JOURNALS-CAJO_NUMBER'.
    perform bdc_field1       using 'BDC_OKCODE'                    '=OK50'.
    perform bdc_field1       using 'TCJ_C_JOURNALS-COMP_CODE'      '1000'.
    perform bdc_field1       using 'TCJ_C_JOURNALS-CAJO_NUMBER'        IT_TEMP-CJ_NUMBER.
    perform bdc_dynpro1      using 'SAPMFCJ0' '0100'.
    perform bdc_field1       using 'BDC_CURSOR'                          'ISCJ_E_POSTINGS-TRANSACT_NAME(04)'.
    perform bdc_field1       using 'BDC_OKCODE'                  '=TODA'.
    perform bdc_field       using 'F_DISPLAY_PERIOD_LO'          IT_TEMP-DOCUMENT_DATE.
    perform bdc_field       using 'F_DISPLAY_PERIOD_HI'           IT_TEMP-DOCUMENT_DATE.
    perform bdc_dynpro1      using 'SAPMFCJ0'                    '0100'.
    perform bdc_field1       using 'BDC_OKCODE'                  '=TAB2'.
    perform bdc_field       using 'F_DISPLAY_PERIOD_LO'          IT_TEMP-DOCUMENT_DATE.
    perform bdc_field       using 'F_DISPLAY_PERIOD_HI'           IT_TEMP-DOCUMENT_DATE.
    perform bdc_field1       using 'BDC_CURSOR'                'ISCJ_E_POSTINGS-TRANSACT_NAME(04)'.
    perform bdc_dynpro1      using 'SAPMFCJ0' '0100'.
    perform bdc_field1       using 'BDC_OKCODE'                  '=SELE'.
    perform bdc_field       using 'F_DISPLAY_PERIOD_LO'          IT_TEMP-DOCUMENT_DATE.
    perform bdc_field       using 'F_DISPLAY_PERIOD_HI'           IT_TEMP-DOCUMENT_DATE.
    perform bdc_field1       using 'BDC_CURSOR'                'ISCJ_E_POSTINGS-TRANSACT_NAME(06)'.
    perform bdc_dynpro1      using 'SAPMFCJ0'                      '0100'.
    perform bdc_field1       using 'BDC_OKCODE'                 '=POST'."   '=POST_ALL'.
    perform bdc_field       using 'F_DISPLAY_PERIOD_LO'             IT_TEMP-DOCUMENT_DATE.
    perform bdc_field       using 'F_DISPLAY_PERIOD_HI'             IT_TEMP-DOCUMENT_DATE.
    perform bdc_field1       using 'BDC_CURSOR'               'ISCJ_E_POSTINGS-TRANSACT_NAME(06)'.
    CALL TRANSACTION 'FBCJ' USING BDCDATA1
                     MODE   'A'
                     UPDATE 'A'
                     MESSAGES INTO MESSTAB1.
    *UPDATE ZIBSCASHPAYMENTS SET RECPT = ' '
    WHERE CJ_NO = IT_TEMP-CJ_NUMBER.
    ENDIF.
    *UPDATE ZTEMPFBCJ SET COMP = ' ' WHERE REF_DOC_NO = IT_TEMP-REF_DOC_NO .
    *ENDLOOP.     "END OF LOOP AT IT_TEMP
    ENDIF.
    endselect.
           Start new screen                                              *
    FORM BDC_DYNPRO USING PROGRAM DYNPRO.
      CLEAR BDCDATA.
      BDCDATA-PROGRAM  = PROGRAM.
      BDCDATA-DYNPRO   = DYNPRO.
      BDCDATA-DYNBEGIN = 'X'.
      APPEND BDCDATA.
    ENDFORM.
           Insert field                                                  *
    FORM BDC_FIELD USING FNAM FVAL.
      IF fval <> NODATA_CHARACTER.
        CLEAR BDCDATA.
        BDCDATA-FNAM = FNAM.
        BDCDATA-FVAL = FVAL.
        APPEND BDCDATA.
      ENDIF.
    ENDFORM.
           Insert field                                                  *
    FORM BDC_NODATA USING P_NODATA.
      NODATA_CHARACTER = P_NODATA.
    ENDFORM.
           Start new screen                                              *
    FORM BDC_DYNPRO1 USING PROGRAM DYNPRO.
      CLEAR BDCDATA1.
      BDCDATA1-PROGRAM  = PROGRAM.
      BDCDATA1-DYNPRO   = DYNPRO.
      BDCDATA1-DYNBEGIN = 'X'.
      APPEND BDCDATA1.
    ENDFORM.
           Insert field                                                  *
    FORM BDC_FIELD1 USING FNAM FVAL.
      IF fval <> NODATA_CHARACTER.
        CLEAR BDCDATA1.
        BDCDATA1-FNAM = FNAM.
        BDCDATA1-FVAL = FVAL.
        APPEND BDCDATA1.
      ENDIF.
    ENDFORM.
    thanks & regards
    vallamuthu

    Loop at IT_TEMP for all records to populate the bdcdata and then call the CALL TRANSACTION statement <b>outside</b> of the loop (at present I see it coded within the loop).
    Doing this will call the FBCJ just once, to post all data, instead of posting once for each loop.
    Hope this helps.
    Sudha

  • FBCJ Receipt Error

    Hi
    Please advise on how to overcome the following error and to post the transaction in FBCJ.
    FBCJ Receipt error:
    Date of transaction: 19.04.2009
    In FBCJ, under cash receipts a  split transaction is posted by user
    1) First Transaction:
    Business Transaction: Sundry Receipts (here I can change the GL Account)
    Amount: 1,000.00
    Tax Code: kept blank since it is not mandatory in respect of the above business transaction.
    2) Second Transaction:
    Business Transaction: Sale of Tender Forms
    Amount : 125.00
    Tax Code: Made Tax Code Mandatory as F1 in the GL Account under Control Data tab in Tax Category.
    User has not put Tax Code in the second transaction since in the first transaction tax code is not mandatory system allowed to save the split transaction even though for the second transaction tax code is mandatory.
    Now the tax code field is greyed out. 
    Requirement:
    Somehow or other I have to post the document (with or without tax) and my cash book balance should tally with my GL balance. 
    The following is the error message:
    Balance in transaction currency
    Message no. F5702
    Diagnosis
    A balance has occurred in transaction currency 'INR' with the following details:
    Exchange rate '00', amount '           125.00' and currency key 'INR'.
    The data in the transaction currency were transferred from the calling application.
    System Response
    Your data cannot be processed in FI.
    Procedure
    The error is probably in the calling application
    Kindly advise.  Your valuable inputs are highly solicited.
    Aravind Boddupalli

    Hi
    check in business transaction if tax code is allowed for that business transaction.

  • How to catch Posting error in File to IDoc Scenario?

    I have successfully completed File to IDoc Scenario. Now I am interested in catching posting error. i.e., if mapping goes well and when IDoc is being sent to Recipient system then if any posting error is encountered, then a mail should go to a recipient.
    Can anybody suggest the solution.
    Regards,
    Suraj Kumar

    Hi Suraj,
    this can be done by triggerring an alert to the recipient.chk out these links to trigger a alert
    /people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
    /people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
    regards
    jithesh

  • GR/IR Posting Error CKMLGRIR025 - Purchase Order History Inconsistent

    Hi Everyone.
    We currently have a posting in our GRIR for a Feright Condition Value against a Purchase Order which gets the above error when trying to post in MR11.
    The Diagnosis of the error reads:
    "The purchase order history contains differences between the goods receipt and invoice receipts/Account maintenance for the order item in the field Difference Quantitiy (= 43.804 TO) and Difference Value (= -342.77)
    The purchase order history for this tiem is inconsistent"
    When looking at this Freight Condition information in the Purchase Order I can not see why this item has resulted in this error in MR11.
    Has anyone else seen this error come through in their system, and do you have any ideas on how to fix this.
    Thanks
    Hayley

    We are experiencing the same issue with the GRIR Posting Error CKMLGRIR025 - puchase order history inconsistent.  The actual message that we receive is Puchase Order history already inconsistent -->Quantity 1.00 EA Value 0.65-USD.
    We reviewed SAP Note 708649 which also recommends using transaction MIRO with the corresponding default quantity and value o.  However, we are not able to enter an Invoice for the "default qty & value 0", as SAP gives me error message M8278 "You are not allowed to have zero lines" (just like Haley commented).  In reviewing this thread, I did not find the solution to the error message M8278 "You are not allowed to have zero lines" .  Could someone help me understand?
    Thank you!

  • Fi posting error

    Hi SAP gurus,
                        I am facing posting error fi_tax_chk_pricing_data
                       error code 13 builder tax2.
                     plz help me

    hi
    u get this error when u have not specified the county while creating the company code go to  OX02 and give country for the company code. this solves your problem
    rgds
    sree

  • MR11 GR/IR Posting Error - PO History Inconsistent - error message M8278

    Dear experts,
    We have the problem as described in SAP note 708649. Error CKMLGRIR025 - Purchase Order History Inconsistent  
    This has also been described in this thread
    Re: GR/IR Posting Error CKMLGRIR025 - Purchase Order History Inconsistent
    We also have the issue on posting an invoice "default qty & value 0" in MIRO, receiving error M8278 "You are not allowed to have zero lines".
    However, so far we are not able to correct this eg do not know how to continue to clear the GR/IR
    Any help or hints on this matter would be appreciated

    Hi,
    please note that the error message M8 278 is only issued if there is                            
    zero amount in ALL document lines.                                                                               
    This means that you can post MM-documents with zero lines. But only if                          
    there are other lines with amount > 0. The reason for this system                               
    behaviour is, that every time a MM-Invoice is posted, an FI-Document is                         
    created. In FI-Documents it isn't allowed to have zero lines.                                   
    So if you have an MM-Document with only zero lines, the Fi-document                             
    can't be created and the error message is issued.                                               
    I hope I could help you further
    Best regards
    Erika

  • PO posting error

    guys,
    i get this posting error when i try to create a purchase order.... please some one help on this??
    tnx
    wiz
    Posting only possible in periods 2009/09 and 2009/08 in company code 2000
    Message no. M7053
    Diagnosis
    The posting date entered is not within one of the permitted posting periods (current period/previous period).
    This can be due to one of two reasons:
    The correct current period has not been set in the system.
    For the system, the first of the entered periods is the current period. At the beginning of a new period, your systems administrator must change the current period in the material master record, using the function "Shift periods". This has not yet been done.
    You have entered a wrong date in the field "Posting date".
    Procedure
    Check the posting date and correct it if necessary. If your input is correct, inform your systems administrator that the "period shifting" (period-end closing) process has not yet been completed. Copied from M8022

    Hi,
    The problem was due to posting period is not open for posting yet.
    I believe you are trying to create PO for Oct 2009. But your posting period was open for Sept 2009 and Aug 2009.
    Go to tcode MMRV to check for company code 2000, current period  09 2009, previous period 08 2009.
    Go to tcode MMPV, enter the company code 2000, period 10 and fiscal year 2009, select "Check and close period" and execute.
    Go to tcode MMRV to check again for company code 2000, current period should be 10 2009, previous period 09 2009.
    You should be able to create a PO by now. If you still fail to do so, please contact your FI to open FI period via tcode OB52.
    Hope it helps.
    Regards,
    JT

  • General Ledger Posting Error (GLT2 051) No accounting transaction variant

    Hello SAP Gurus-
    When testing lockbox in FLB2, I received the following error message:
    General Ledger Posting Error (GLT2 051) No accounting transaction variant assigned to FB01/  /LB
    We are on ECC 6.0
    I created a new Document Type LB
    I created a new G/L account for Lockbox clearing and AR
    How do I fix this?
    Thank you!

    Hi,
    Assign a transaction variant for the document type you created in  Transaction code GSP_VZ3. Also, make sure that the GL accounts affected are assigned with item categories in GSP_LZ2.
    Thanks
    Aravind

  • POST errors need help

    Can any one tell me what the POST error of 2 beeps pause 1 beep is realted to? The system begins to boot flashes video, video shuts off, cmos info flashes shuts off and give post error.

    Use just one stick of RAM in a green slot. Reset the Bios and be sure the machine is not pluged in when you do those things.
    Remove all unneeded hardware so that you don't have stuff in the box when you try to boot that is not needed to post.
    Find out which Bios you have when the screen first comes up.
    You need to know which CPU core you have. If it is a Clwhammer, Newcastle or Winchester then you need Bios version 3.3 If it is a San Diego, Venice or X2 then you need Bios version 9.1.
    Now that you have a system with the correct Bios you can then install your RAM in slots 2 and 4. You should then get a post into dual channel mode.
    Set in Bios first - Optimized Defaults. Make sure that you do not skip this step.
    Now setup the Bios to match the gear in the box. No overclockinmg as yet.
    Now get Windows cleanly installed with any drivers you may need.
    Now you are ready to install those other items you have in your hot little hands. One at a time.

  • (C1) Initialize POST Error Manager (PEM)

    Hello,
    My hardware diagnostic card gives the following error: (C1) Initialize POST Error Manager (PEM). My bios just starts well and gives no error messages.
    I can go to the bios as usually and my computer works normally (at the moment), but QuickTech also gives some error messages:
    - BIOS Buffer overrun check
    - SMBus Host detection
    Maybe that these errors also have to do with it?
    When I try to search with Google I only get some manuals where these error codes are listed, but no more explanations and possible solutions.
    Can somebody please tell me what this problem is all about and how to fix it?
    I have a MSI 6533 bord.

    Hi,
    No, unfortunately not. I posted this question in a lot of different forums, but no one seems to know what's exactly wrong and how to fix it.
    I keep searching, and when I find some answers / solutions, I'll post it here. Can you also please keep me informed if you know some more?

  • Fi posting error due to fiscal period error 1

    HI SAP GURUS,
    I am trying to post TR6 Challan in todays date & getting following message-
    Fi posting error due to fiscal period error 1
    Message no. 8I216
    Diagnosis
    Attempt to post the document in a period outside the current Fiscal
    period  setup.
    Procedure
    Change the posting date  or  Change the fiscal  period prior to posting
    the  transaction under consideration.
    please help me to resolve the issue.
    CHEERS

    HI
    This error is due to Posting period is not open in FI check the posting period is opened for all the accounts in OB52 then post the entries
    hope it will be usefull

  • MSI X79-GD65(8D) gives a posting error 63 Late CPU Initialize

    Hey Guys.
    I have recently purchased new hardware.
    MSI X79-GD65(8D) Motherboard
    Intel i7 3820 CPU
    4 X Corsair Vengeance 4GB DDR3-1600 RAM
    MSI GTX660Ti Power edition GPU
    Corsair 750W Professional series PSU
    Corsair H80 CPU Cooler
    I haven't overclocked ht e mobo, but on cold boot, the mobo doesn't initialize, gives a post error 63, refered to the mobo manual, it says it means late CPU initialize. Checked the BIOS, running version 1.7 and according to MSI download site for the CPU support list.
    The memory is in quad channel as it shows in a diagram in the mobo manual. If I switch the pc off, and back on, it initializes and boots, the pc runs stable, it can run 48 hours no hassle, passes burn in tests to, just the first cold boot doesn't initialize.
    Any ideas for what to look at would be great.
    Thank you.

    A little hint for you: Don't try any of the .1B betas as they run horrible. I had to remove the latest .1B3 as it bricked the board and had to be recovered.
    1.18 B7 is still the best bios to use:
    Quote from: flobelix on 17-November-12, 00:49:07
    I'd suggest the later Bios 1.18 B7 which I'm also using with the i7-3820 (https://forum-en.msi.com/index.php?topic=154186.msg1192427#msg1192427)

  • Thru Collective conf goods posting error neds to be avoided going to COGI

    Dear,
    While doing collective confirmation along with Goods posting, If the stock is deficit then error posting generating in COGI. We need to stop error posting in IW42 itself not allowing to post error in COGI. Customisation is already done for Termination for Incorrect Goods Movement.

    Dear,
    When you post via the collective entry as well as when updating dependent goods movements of the collective order processing, no error handling is provided in Standard SAP. If you do this with IW41 it will work for you. If you set In Customizing of the confirmation (Transaction OPK4), I set error handling in case there are any incorrect goods movements.
    Transactions IW41 and IW42 are both considered to be completely separate transactions. In the individual completion confirmation, a linkage occurs between goods movement and completion confirmation that you cannot find in the overall completion confirmation.
    For this reason, the function  "Incorrect good movement"' leads to a termination in Transaction IW41 and not in Transaction IW42.
    Work around for it schedule the program CORUAFFW in background  using SM36 on hourly basis so it will clear the COGI post processing error.
    Hope it will help you.
    Regards,
    R.Brahmankar

  • Post error: Primary IDE 80 No Conductor cable

    I need to know what this error message means and how it is corrected:
    During the Post, the BIOS recognizes my hard drive then I see this message
    Primary IDE 80 No Conductor Cable
    I have just finished installing a Maxtor Diamond 7200 40GB hard drive.  I have also updated my BIOS to 3.50.
    I can't find this message in any trouble-shooting manuals.
    Any help is appreciated.

    i have a KT4 Ultra (plain) and i'm getting the same post error, i did as said by purchasing cables that specifically said they were 80 conductor and i am still receiving the message. on to of this i am also getting a post beep saying that there is a memory refresh error. also, i'm not sure if any of this is related, but i am also getting bluescreen errors during the installation of windows xp. the two errors i have received thus far are, IRQ_NOT_LESS_OR_EQUAL 0X0000000A (0X00000060, 0X00000002, 0X00000000, 0X807CE5EA) and CDFS_FILE_SYSTEM 0X00000026 (0X000401F4, 0XF80CB900, 0XF80CB600, 0XF8696021O).
    my sys config is as follows:
    420 watt psu
    amd athlon xp 2000+ @ 133
    512 ddr pc2700 @ 333
    ibm  deskstar 40gb hd primary master
    creative 12x dvd rom primary slave
    sony dru-500a dvd ±r/±rw secondary master
    seagate 2gb hd secondary slave
    3d prophet 3 video card
    sound blaster live 5.1 platinum sound card
    as of now my only conclusion is a faulty main board.

Maybe you are looking for