Defining Check void reasons (for manual checks)

Hi
I am voiding manual checks in FCH9 and FCH8. The check void reasons appearing in drop down are not sufficient. Hence i need to define more check reversal reasons.
I went through SPRO node for bank transactions (in FI). But i am not getting it.
Please help me how to define check reversal reason. Please provide for SPRO path or TCode

If you do not find the required path in customisation, always Ctrl+F (Find) and type the search text.
Alternatively, searching the forum with "Void Cheques" would have given the answer.
Anyway, you may also reach FCHV by the following path:
IMG ==> Financial Accounting ==> Accounts Receivable and Payables ==> Business Transactions ==> Outgoing Payments ==> Automatic Outgoing Payments ==> Payment Media ==> Check Management ==> Define Void Reason Codes.
Please read F1 help on the configuration screen.

Similar Messages

  • Payment advise for manual check payment

    Hi,
    Client wants payment advise for manual check payment.
    He wants:
    Reference field, Invoice date, Invoice amount, TDS deduction, Service tax deduction,WCT deduction, Amount paid
    The above fields should be appeared in layout
    So Could anybody please provide the logic.
    Thanks,
    Sai

    Hi Sai,
    You wil need the help of ABAP programmer to write the program for this.
    Reference field, Invoice date, Invoice amount, TDS deduction, Service tax deduction,WCT deduction, Amount paid,  All these  fields can be picked up from BSIK,BKPF & BSEG Tables.
    The Logic is to develop a Z program which will pick up for each document posted, based on Document Number and Date the data for each of the above mentioned fields from the given tables and create a Payment Advice Form on whch he will print the data.
    Thank You.

  • FCH6-allow user to chng.check info for manual check-n not for auto chekf110

    Hi Gurus....
    T'Code FCH6 will allow user to change check info if the check is created manually. But it will not allow check info to be changed if the check is generated from F110. Is there  any mean to protect check info from being changed no matter it is manual or auto check (F110)?
    FCH6 is used for bank reconcilation. user need to key in encashment date but not to allow to modify other details e.g. amount, name,....but found for manual check, it allows users to do it so...
    Is there any way to restrict the above....
    Thanks n Regards
    N Sathish Kumar

    HI,
    The way to restrict the users from changeing the data or restricted access to certain screens or fields or t-codes can be done through Authorization Objects.  Approach your Basis guy to create one for you and you assign this Auth. Object in the user roles. Provide the Basis guy with the fields that you want to restrict. I think this is the only way to restrict the access to certain fields in a screen.
    uset this link to understand more on Aurth. Objects
    http://help.sap.com/erp2005_ehp_02/helpdata/en/95/1632e5ba9511d29e310000e839cd96/frameset.htm
    Thanks
    VK

  • AP Check printing setups for printing checks on your own

    HI
    I am wondering if there a good document which deals with AP check printing with MICR and signature on your own check stock
    thanks

    Recently we started to deal with AP check printing in our organizatin. It was a daunting task with the information and resources scattered all over and missing critical pieces of information to make sense out of the whole process flow. We attempted to go through the AP check printing internally and succeded.
    I decided to post the information for the benefit of people about the our experience
    Check Printing Basics and Beyond for Printing Checks on Your Own
    by
    Sarma Chilukuri
    This article deals with what is needed to get your own checks printed. It is a first attempt to uncover all the hidden rules that one should be aware to get your own checks printed. The first section deals with the basic AP check printing setup, while the 2nd half explores some of the flow of events that make it possible to print the check.
    Part I – Basic Setup
    AP Setup for check printing
    There are multiple steps in the AP check printing. First set of steps deal with the AP side setups. The second step is to get the System side setups. The system side setup deals with printer setup and program options setups. The last step would be to make the print format files configured with the vendor provided escape sequences in the laser print format file.
    Step 1: login as Payable Manager
    Step 2: Bank Setup: Navigate to Setup: Payments > Banks
    1.     Make sure the Bank # etc are present
    2.     Tab to “Bank Accounts”, and make sure your account # has been setup
    3.     On the Bank Accounts screen, tab to the “Payables Documents” and verify that Payment format (E.g., COK Laser Format) has been entered. This “Payment format links to next section where we associate it to the right payment program.
    Fig 1. AP Payment Bank Setup Screen
    Step 3: Program Setup (Setup: Payments > Programs)
    As we know there are only 5 formats 3 of which are “Ever Green Laser” (APXPBFE G|L|F) which are explained in the AP Users Guide. For your own form printing, you have to associate the format to APXPFEL (laser format) program. Also, the APXPBFEL or APXPBFEF call the APXPBFEG, which is the base program that pulls the data from oracle base tables. APXPBFEL is the one which allows us to print the checks with MICR and signature on a plain paper not on a pre printed stationery.
    Fig. 2 AP Payment Format Setup Screen
    Printer Styles, Drivers setup
    The above process summarizes the AP Setup. As a DBA, the printer setup needs to be validated. The base install provides the right setup to some extent. But the differences in printers and print queues may add some complexity to the final configuration. The following section discusses the set up the base install provides and changes as needed.
    Step 1. Login as system Administrator
    Step 2: Style (Install : Printer > Style)
    Look for the “PORTRAITHPLJ4LASCHECK”. This one is associated with the SRW Driver Called, “APLASP” (AP Laser printer format).
    Step 3: Driver (Install : Printer > Driver).
         1. The “PORTRAITHPLJ4LASCHECK” is associated with a “User Driver” of PORTRAIT for HPLJ4 and and a SRW driver of “APLASP”
         2. Also notice that there is an Initialization string at the bottom of it. This initialization string gets called as pre-report trigger for the APXPBFEG program (APXPBFEG.rdf) file. It sets the kind of format it should be. Please see the Appendix A for details on these printer pcl code translations. The Initialization string was as follows:
    Initialization: /eE/e&l0o2a7C/e(s0P/e(8U
    Step 4: Printer type (Install : Printer > Register)
    Each printer type is associated with a set of styles. Make sure the printer that was selected has the above style and its associated driver listed against that.
    Fig. 3 System Administrator Printer Seups
    Step 5: Program Setup (Concurrent > Program > Define)
    This step holds the key for check printing. It is necessary to define whether you need the check on top followed by the Stub or the other way around. The way it is controlled is based on the APXPBFEG.rdf, the report definition file and the APLASP.prt (Printer Style associate with the Portrait laser check format SRW driver). The APLASP.prt file ($FND_TOP/reports) has two identical setups called the 100 series and the 200 series. Those identical sets of setups define where the MICR and signature print on the check. The following table lists the some of the codes in the 100 series. Please refer to Doc ID #146452.1 for complete details.
    Fig. 4 System Administrator Concurrent Program Definitions
    CODE #     Code Definition
    100     Electronic check activation string
    101     1st Check #
    102     2nd Check #
    104     Deactivate check number mode string
    111     Activate MICR line
    112     MICR Deactivation / reset the printer head position
    121     1st Signature
    122     2nd Signature
    141     Address font activation string
    199     Return to default state string
    Table 1. APLASP.prt -- MICR Activation Codes
    The above code block repeats itself the same way in the 200 series. The decision to activate one way or the other controls the Check printing.
    Step 2: Setting up the Option block
    In the concurrent program definition for the APXPBFEL, there is an Options block in the middle. You need to list the codes that you want to activate. Please refer to Doc ID # 186640.1 for some explanation on these.
    E.g.,
    p_printer_code_mask="201,211,221,241" p_sig2_amount="" p_sig3_amount="" p_sig1_vendnum="" p_sig2_vendnum="" p_sig3_vendnum="" p_country_to_ignore="US" p_continuous_stationery="N"
    Step 3: Output format is Text
    Text format is sufficient, as the printer will pick up these escape sequences anyway.
    Fig. 5 System Administrator Concurrent Program APXPBFEL Options Definition
    UIPRINT.TXT, UIFONTS.ALI
    One needs to be aware of a few more pieces in this puzzle. The UIPRINT.TXT identifies to the Oracle Applications the print queues that were setup. This file is needed to set your PCL / Post Script printer definitions. I did not have to really tinker with these files other than identifying the PCL and Post Script Q’s that were setup on the UNIX box.
    Part II: Integrating all the pieces
    The above setups are all documented in various articles. We need to understand a few more steps to see how all these pieces come together.
    What you need to know about APXPBFEG.rdf
    APXPBFEG (.rdf) is the report file which when called pulls the data from Oracle. If you open the APXPBFEG.rdf in the Oracle reports, there is initialization to the report called, SRW.Init. This will bring in the initialization string associated with the PORTRAITHPLJ4LASCHECK driver definition file. Also, please be very careful with this report format file. When you open it, there is small tiny empty block. in the first block which calls the printer initialization code 100/200 under the Format Mask (from APLASP.prt). If this portion gets changed or messed up, one can end up with some unexpected results. Each of those blocks like MICR, CHECK etc… have associated format triggers and printer codes.
    Please make sure that the printer mask is properly handled. I noticed that the 200 series MICR (211) and Signature (221) printer masks were tied to 111 and 121 respectively. These should have been 211 and 221. The other place you need to be careful was the printer code before and after is proper.
    For E.g.,
    For the MICR, the ”printer code before and after columns “ should be 111 and 112 (or 211 / 212) respectively while Format Trigger should reference to 111 (211).
    Fig. 6 APXPBFEG rdf file printer mask and Format Triggers
    The escape sequences in the APLASP.prt file for these codes will play the crucial role in getting our format around the report output that gets generated from the APXPBFEG program. Please refer to the explanation of these escape sequence codes in the APPENDIX A.
    At this point when you run the program, you will see that the formatted output report file will have all the initialization strings and the output associated with that. You can compare the fields and verify the results. Let us closely examine the parts of the 111 and 121 where the micr and signature prints. The key to this to code the escape sequences the right way to get the associate MICR and signature print out correctly.
    Fig. 7 APXPBFEG rdf file MICR printer mask and Format Triggers
    Code 111 and Code 112 from the APLASP.prt file.
    I broke the line into pieces to illustrate the exact escape sequence code.
    Code "211"
    Part 1: esc "&f0S" esc "&f0y0X" esc "&l0E" esc "&a0L"
    Part 2: esc "(8M" esc "(s0p8.00h8.0v0s0b80T" --- This will be provided by the ROM
    Cartridge provider
    Part 3: esc "&k15H" esc "*p3215Y" esc "&a13.8C"
    code "212"
    Part 1 : esc "&f1x3x8X"
    Part 2 : esc "&f1S"
    Let us go over these 2 sets of codes carefully.
    Escape Code     Meaning     Comment
    esc "&f0S"      Push Cursor Position     
    esc "&f0y0X"     Define Macro ID 0 and Start Macro Definition     
    esc "&l0E"      Define Top Margin at 0 Lines     
    esc "&a0L"      Define Left Margin at Column 0     
    esc "(8M"     8M Symbol SetNote : As per pcl codes this happens to be Font Primary JIS Math 8 symbol     MICR Part 1 : Provided by the Vendor from where you the ROM cartridge
    esc "(s0p8.00h8.40s0b0T"     {Fixed Pitch}{pitch 8.00 cpi}{Font Style 8.40}{Medium Weight}{Typeface 0}     MICR Part 2 : Provided by the Vendor
    esc "&k15H" esc "*p907Y"     Set HMI = 15/120" Vert position = 907 Dots     
    esc "&a13.8C"     Move to Column 13.8     
         CODE 112     
    esc "&f1x3x8X"     {End Macro Definition}{Call Macro}{Delete Macro ID}     
    esc "&f1S"     {Pop Cursor Position}     At this point, the MICR gets printed
    Table 2. Escape Sequences in APLAP.prt file Explanation
    Fig. 8 APXPBFEG rdf file Signature printer mask and Format Triggers
    The signature piece (221) has also similar meaning.
    Escape Code     Meaning     Comment
    esc "&f0S"     Push Cursor Position     
    esc "*t300R"     300 DPI Graphics resolution     
    esc "*p1500X"     Horiz position = 1500 Dots     
    esc "*p650Y"     Vert position = 470 Dots     
    esc "(4B" esc "(s1p53v0s0b102T"esc "&f0S!"     Symbol SetProportionalPoint Size 53UprightMedium WeightTypeface 102Push Cursor Position!     Vendor gave the us esc "(4B"esc"(s1p53v0s0b102T!"Note: the ! when the it pushes the ! and that is where it prints the signature piece. The first part forms the symbol set , say (4B and the later part forms the signature font and ! is the piece. I took the ! from the above and let it stay with the 3rd part of it so that signature does not print twice.
    esc "&f1S"      Pop Cursor Position     
    esc "*p+121Y"     Move down 121 Dots     
    esc "&f1S"     Pop Cursor Position     
    Table 3. Escape Sequences for Signature in APLAP.prt file and Explanation
    Summary
    One can print their own checks using the above steps. This can work as a cost effective solution for small organizations where the budgetary constraints are tighter. We are successful in getting the AP Checks printed using the above method.
    References
    Metalink Doc ID # 186640.1, Different Payment Formats …
    Metalink Doc ID # 60936.1, Step by Step Guide to Setup a Printer in Oracle Applications
    Metalink Doc ID # 250543.1, How to Create An Initialization String for a Payable Check Format
    Metalink Doc ID # 48680.1, Accounts Payable FAQ – Payment Batch, Check
    Metalink Doc ID # 1074792.6, Exclamation Point (!) Prints On Check When Using APXPBFEL And Cartridge
    Metalink Doc ID # 158486.1, APXPBFEL Evergreen (Long Laser)
    Metalink Doc ID # 146452.1, Listing of p_printer_code_mask Default Values for APXPBFEL
    Chapter 2, Oracle Payables user guide
    Appendix A
    APLASP.prt printer codes explanation
    code "200" esc "&l0o2a6d66p8.000c2e1x0l63f1H" esc "&k12.00H" esc "(8U"
    esc "(s0p10.00h12.00v0s0b3T" esc "&k11.75H" esc "&a1l0R" control(M) esc"&f3005y4X"
    {Portrait}
    {Letter}
    {6 LPI}
    {Define Page Length to 66 Lines}
    {Set VMI = 8.000/48"}
    {Define Top Margin at 2 Lines}
    {Select 1 Copies}
    {Disable Perf Skip}
    {Define Text Length as 63 Lines}
    {Feed from Tray 1 (upper)}
    0.1 esc "&k12.00H"
    {Set HMI = 12.00/120"}
    0.2 esc "(8U"
    {Roman-8 Symbol Set}
    0.3 esc "(s0p10.00h12.00v0s0b3T"
    {Fixed Pitch}
    {pitch 10.00 cpi}
    {Point Size 12.00}
    {Upright}
    {Medium Weight}
    {Typeface 3}
    0.4 esc "&k11.75H"
    {Set HMI = 11.75/120"}
    0.5 esc "&a1l0R"
    {Define Left Margin at Column 1}
    {Move to Row 0}
    control(M)
    0.6 esc"&f3005y4X"
    {Define Macro ID 3005}
    {Enable Overlay}
    code "201" esc "&f0S" esc "&a1.25r70C" esc "(8U" esc "(s1p14v0s3b4148T"
    {Push Cursor Position} esc "&f0S"
    1.1 esc "&a1.25r70C"
    {Move to Row 1.25}
    {Move to Column 70}
    1.2 esc "(8U"
    {Roman-8 Symbol Set}
    1.3 esc "(s1p14v0s3b4148T"
    {Proportional}
    {Point Size 14}
    {Upright}
    {Bold}
    {Typeface 4148}
    code "202" esc "&f0S" esc "&a20.25r70C" esc "(8U" esc "(s1p14v0s3b4148T"
    {Push Cursor Position}
    2.1 esc "&a20.25r70C"
    {Move to Row 20.25}
    {Move to Column 70}
    2.2 esc "(8U"
    {Roman-8 Symbol Set}
    2.3 esc "(s1p14v0s3b4148T"
    {Proportional}
    {Point Size 14}
    {Upright}
    {Bold}
    {Typeface 4148}
    code "211" esc "&f0S" esc "&f0y0X" esc "&l0E" esc "&a0L"
    esc "(0Q" esc "(s0p8.00h8.40s0b0T" esc "&k15H" esc "*p907Y" esc "&a13.8C"
    {Push Cursor Position}
    11.1 esc "&f0y0X"
    {Define Macro ID 0}
    {Start Macro Definition}
    11.2 esc "&l0E"
    {Define Top Margin at 0 Lines}
    11.3 esc "&a0L"
    {Define Left Margin at Column 0}
    11.4 esc "(0Q"
    {0Q Symbol Set}
    11.5 esc "(s0p8.00h8.40s0b0T"
    {Fixed Pitch}
    {pitch 8.00 cpi}
    {Font Style 8.40}
    {Medium Weight}
    {Typeface 0}
    11.6 esc "&k15H" esc "*p907Y"
    {Set HMI = 15/120"}
    {Vert position = 907 Dots}
    11.7 esc "&a13.8C"
    {Move to Column 13.8}
    code "212" esc "&f1x3x8X" esc "&f1S"
    {End Macro Definition}
    {Call Macro}
    {Delete Macro ID}
    12.1 esc "&f1S"
    {Pop Cursor Position}
    code "221" esc "&f0S" esc "*t300R" esc "*p1500X" esc "*p470Y"
    esc "(30C" esc "(4B" esc "(s1p53v0s0b102T!"
    esc "&f0S!" esc "&f1S" esc "*p+121Y" esc "&f1S"
    esc "&f0S"
    {Push Cursor Position}
    21.1 esc "*t300R"
    {300 DPI Graphics resolution}
    21.2 esc "*p1500X"
    {Horiz position = 1500 Dots}
    21.3 esc "*p470Y"
    {Vert position = 470 Dots}
    21.4 esc "(30C"
    {30C Symbol Set}
    21.5 esc "(4B"
    {4B Symbol Set}
    21.6 esc "(s1p53v0s0b102T!"
    {Proportional}
    {Point Size 53}
    {Upright}
    {Medium Weight}
    {Typeface 102}
    21.7 esc "&f0S!"
    {Push Cursor Position}
    21.8 esc "&f1S"
    {Pop Cursor Position}
    21.9 esc "*p+141Y"
    {Move down 121 Dots}
    21.10 esc "&f1S"
    {Pop Cursor Position}
    code "222" esc "&f0S" esc "*t300R" esc "*p1500X" esc "*p650Y"
    esc "(30A" esc "(s0p.426h35.25v0s0b128T" esc "&f0S!"
    esc "&f1S" esc "*p+141Y" esc "&f1S"
    {Push Cursor Position}
    22.1 esc "*t300R"
    {300 DPI Graphics resolution}
    22.2 esc "*p1500X"
    {Horiz position = 1500 Dots}
    22.3 esc "*p650Y"
    {Vert position = 650 Dots}
    22.4 esc "(30A
    {30A Symbol Set}
    22.5 esc "(s0p.426h35.25v0s0b128T"
    {Fixed Pitch}
    {pitch .426 cpi}
    {Point Size 35.25}
    {Upright}
    {Medium Weight}
    {Typeface 128}
    22.6 esc "&f0S!"
    {Push Cursor Position}
    22.7 esc "&f1S"
    {Pop Cursor Position}
    22.8 esc "*p+141Y"
    {Move down 141 Dots}
    22.9 esc "&f1S"
    {Pop Cursor Position}
    code "241" esc "&a-100V" esc "&l5.8C" esc "(8U" esc "(s0p12.00h10.00v0s3b3T" esc "&k11.75H"
    41.0 esc "&a-100V"
    {Move up 100 Decipoints}
    41.1 esc "&l5.8C"
    {Set VMI = 5.8/48"}
    41.2 esc "(8U"
    {Roman-8 Symbol Set}
    41.3 esc "(s0p12.00h10.00v0s3b3T"
    {Fixed Pitch}
    {pitch 12.00 cpi}
    {Point Size 10.00}
    {Upright}
    {Bold}
    {Typeface 3}
    41.4 esc "&k11.75H"
    {Set HMI = 11.75/120"}
    code "299" esc "(8U" esc "(s0p10.00h12.00v0s0b3T" esc "&k11.75H" esc "&l6D"
    {Roman-8 Symbol Set}
    99.1 esc "(s0p10.00h12.00v0s0b3T"
    {Fixed Pitch}
    {pitch 10.00 cpi}
    {Point Size 12.00}
    {Upright}
    {Medium Weight}
    {Typeface 3}
    99.2 esc "&k11.75H"
    {Set HMI = 11.75/120"}
    99.3 esc "&l6D"
    {6 LPI}

  • Cheque format for manual check assignment document

    Friends,
    I have made a manual cheque assignment for a payment document(through F-53) through FCH5.  I have alloted a non-sequencial check lot for the document.
    Now i want to see the cheque format.  How it is possible.  I have tried in FBZ5. But i am not able to see the check view.

    Hi,
    You cant view manual cheque creation, it will just update the check number in PAYR table. It is just for record purpose.
    regards
    srikanth.

  • Mail set for manual checking but checks automatically

    I am getting very annoyed with Mail since 'upgrading' to Lion and iCloud back in February
    I have Mail General Preferences set to "Check for new messages manually", yet it checks my .Mac address automatically.
    I have all my email accounts unticked for including "when automatically checking for new mail", yet it checks  just my .Mac address automatically. This points to the problem being something to do with iCloud rather than with the new version of Mail that comes with Lion.
    Not so annoying when I have the sound switched off but very annoying when I have the speakers on and it interrupts what I'm listning to. Sometimes it even makes the noise when there doesn't appear to be any new email.
    Has anyone else had this problem? And if so, have you found a way to stop it?

    Same problem here after migrating from Snow Leopard to Lion & MobileMe to iCloud. I haven't found any answers online.

  • Request to check the reason for the following error

    Iam trying to execute the following code that is intended to show interdependency between procedures, but Iam not sure why iam getting the following error.? could any one kindly guide me . THANKs
    declare
    X varchar2(4000);
    begin
    for i in 1..5 loop
    execute immediate
    'create or replace procedure prc_'||to_char(i,'fm0000')
    || ' is begin null; end;' ;
    X:='prc_'||to_char(i,'fm0000');
    end loop;
    for i in 5..10 loop
    execute immediate
    'create or replace procedure prc_'||to_char(i,'fm0000')
    || 'is begin null; end;' ;
    end loop;
    end;
    ERROR:
    ORA-24344: success with compilation error
    ORA-06512: at line 11

    Iam trying to modified the code but it is again giving that vague error. Can any one resolve this issue.THANKS
    declare
    X varchar2(8000);
    begin
    for i in 1..5 loop
    execute immediate
    'create or replace procedure prc_'||to_char(i,'fm0000')
    || ' is begin null; end;' ;
    X:='prc_'||to_char(i,'fm0000')||';';
    end loop;
    for i in 5..10 loop
    execute immediate
    'create or replace procedure prc_'||to_char(i,'fm0000')
    || ' is begin'||X|| 'end;' ;
    end loop;
    end;
    ORA-24344: success with compilation error
    ORA-06512: at line 11

  • Auto software update won't check automatically-have to manually check

    I have a brand new macbook pro and the auto update for software updates doesn't work properly. With my old imac, all I had to ever do was to log in and it would check and find the updates. I constantly have to check for these updates myself, manually. I even changed my setting to check 'daily' and that doesn't work either. If anyone has a fix, please let me know too.

    Hi Kappy... just wanted to give you an update. I was working with Apple (by phone) to correct this update problem. While going back and forth, I ran into a problem whereby my 3 month old macbook died. Wouldn't turn on at all. Went to the Apple Store Genius Bar and they ended up replacing the Logic Board. Anyways, it fixed this auto-update problem. Seems to be updating now without a problem. Thanx for all your help here.
    One question for you, if you know... Apple had me move a '[email protected]' file onto my desktop as it didn't belong where it was. Can I just delete this file or do I need to put it somewhere else? Have no idea where it goes. fyi... I don't have mobile-me.

  • Reuse voided manual check

    Dear,
    I have a problem about the manual check.
    At first I used FCH5 to assign a manual check number to a payment document. But later on I used FCH8 to cancel the payment together with voiding the check number.
    Under such circumstances, I would like to know whether this check number can be re-used to assign to other payment document number, as physically this check doesn't have any problem.
    BR,
    Ivy

    Hello
    Check if this helps:
    Deleting Check Information for Payment Run
    If the print program crashes, the print management file will be incomplete in respect of the following information: The information stored in the check information file up to the time of the crash. The check forms generated by the print program. Since there is also no way of verifying whether the data so far generated is consistent, you have no option but to delete the check information on the payment run.
    To do this, choose Environment ® Check information ® Delete ® For payment run. On the next screen, enter the data for the payment run in question and choose Execute.
    In addition to this, you must also delete from the print management files the print jobs that were generated. After this you can rerun the print program.
    Deleting Information on Manually Created Checks
    You can delete information about a manually created check in the following cases: If you specified an incorrect check number when entering the check number. If a check payment was unexpectedly not made.
    To do this, choose Environment ® Check information ® Delete ® Manual checks.
    Deleting Information on Unused Voided Checks
    If an unused check was incorrectly voided, you must also delete the information stored for this check as follows:
    Choose Environment ® Check information ® Delete ® Voided checks. On the next screen, enter the paying company code and the relevant check numbers.
    Resetting Void Check Data
    If an issued check was mistakenly voided, you can reset the data (void reason code, user, and so on) contained in the check information so that the check is designated as a valid check again and can be cashed by the recipient.
    Choose Environment ® Check information ® Delete ® Reset data.
    Resetting Data on Cashed Checks/Extracts
    If the wrong checks were selected for manual cashing or if an update was carried out when creating an extract, although the file should only be created for test purposes, the incorrect check information can be corrected as follows:
    Choose Environment ® Check information ® Delete ® Reset data.
    Reg
    *assign points if useful

  • Check management : void reason form closing

    Dear All,
    When I want to print check using check management
    Why the system void the check with reason code number 3 (form closing) ?
    What is the meaning of void reason form closing ?
    Thank You
    -tweety-

    Check void reason code
        Checks which are voided are allocated an explanation as to why they are
        not used as a means of payment (this is called the void reason code).
    Hi,
    THese are just the reason codes for voiding checks,explanation is as below..
        In the following situations, checks are voided:
        by the form printing programs:
            -   test print
            -   page overflow
            -   form summary section
        by the user with one of the following transactions:
            -   "Void checks"
            -   "Cancel check payment"
    -   "Reverse document", provided the document in question is an
        accounting document for a check payment
    -   "Renumber checks" or "Reprint check". In this case all checks
        which were released by the action are marked as void.
    regards
    deepa

  • Manual Check issue

    HI,
    I had to reverse a payment for manual check 200018, cancel the invoice and the GR then reissue the GR and IR and now I want to pay with the same manual check the balance for vendor 477 but I can no longer find check 200018 in the system, not even as a void. Please let me know what happened as I'm lost.
    Please help me on this
    Thanks
    Supriya

    Hi,
    Check entry for your company code house bank in table PAYR for the check number and in check Register transaction FCHN for the check.
    Through which transaction did you reverse this check.
    Regards
    K.R

  • Number range of manual check

    Hello Experts,
    I have ordered new manual checks. The new manual check range should be 10000 to 11000. I want to know whether I can change check number range in FCHI if there is setting before, or is there another transaction to set the number range of manual check in SAP? Could anyone help me?
    Thank you in advance!
    Maria

    Hello Reg,
    Thanks for your reply, you mentioned "define check number ranges" that it seems to be FCHI. My problem is the check number ranges have been defined in FCHI before, if I can change them to another ranges.
    For example:
    Now the setting is:
         Lot number:1
         Check no from:0000001
         Check no to:9999999
    So, can I change them to Check from: 10000 and Check to 11000 in FCHI. If I can not change, is there any another configuration for the Manul check number in SAP?
    Thank you,
    Maria

  • Need to enter invoice and payment in the system after a manual check issued

    Client Need to enter invoice and payment in the system after a manual check is issued for some urgent transactions.
    Please suggest few ways to do this .

    Hi,
    If client can maintain a separate check book sequence for manual issue, we can configure a separate payment document with the same sequence and later record the invoice and generate payment ....
    Regards,
    Ivruksha

  • Manual Check deposite Config

    Dear SAP Experts,
    Can any body send me the configuration steps for manual check deposite (FF68)
    thanks
    balwan

    Hi,
    Please check the following link[Manual Check Deposit|http://help.sap.com/saphelp_46c/helpdata/en/32/a9ad1cebd311d1ac1f0000e8a5eb64/frameset.htm]
    Regards,
    jigar

  • PI/XI: "HTTP client. Code 110 reason" for XML PO transmission

    PI gurus,
    We use XI to convert PO IDOC to XML message and send the XML message to our vendors.
    We got the error message "HTTP client. Code 110 reason" for two POs while other POs went to the same vendor successfully.
    We also have no problem for sending XML POs to other vendors.
    Is this error caused from the sender or the receiver and how can I fix the problem?
    Thanks in advance!
    Fisher

    Hi,
    Below link will help
    HTTP client code 110 reason
    For reference check the below links too
    Message not reaching Integration server
    HTTPS Receiver Adapter with POST and query String

Maybe you are looking for