Configure payment program to generate idoc

Hi,
I have a requirement to generate a idoc file when the payment is make. Can someone guide me how to trigger the idoc when the payment is make. I am new in FI.
thanks

Found a document from sdn.

Similar Messages

Program that generates idoc in ale/edi

friends can you please tell which program creates an idoc or how are idocs generated while customizing ale and edi ., in which step?

Hi
The following code is used to create and populate IDOC
REPORT ZALE_USR.
CONSTANTS: C_DOCTYP TYPE EDIDC-IDOCTP VALUE 'ZUSRDET01',Idoctype
C_SEGNAM TYPE EDIDD-SEGNAM VALUE 'Z1USRDET01', segmenttype
C_MESTYP TYPE EDIDC-MESTYP VALUE 'ZUSRDET'. message type
DATA: IT_ZUSR02 TYPE USR02 OCCURS 10,
IT_EDIDC TYPE EDIDC OCCURS 0,
IT_EDIDD TYPE EDIDD OCCURS 0,
WA_ZUSR02 TYPE USR02,
WA_EDIDC TYPE EDIDC,
WA_EDIDD TYPE EDIDD,
WA_Z1USRDET01 TYPE Z1USRDET01,
V_OCCMAX TYPE IDOCSYN-OCCMAX,
V_NBSEG TYPE I.
CLEAR WA_ZUSR02.
CLEAR WA_EDIDC.
Save the message type and the basic IDoc type in the control segment.
MOVE C_MESTYP TO WA_EDIDC-MESTYP.
MOVE C_DOCTYP TO WA_EDIDC-IDOCTP.
Retrieve the maximum number of segments in the basic IDoc type.
SELECT MIN( OCCMAX ) FROM IDOCSYN INTO V_OCCMAX WHERE IDOCTYP EQ C_DOCTYP AND SEGTYP EQ C_SEGNAM.
Save the whole USR02 table content in the IT_ZUSR02 internal table.
SELECT * FROM USR02 INTO CORRESPONDING FIELDS OF TABLE IT_ZUSR02.
Create a data segment for each line of IT_ZUSR02.
LOOP AT IT_ZUSR02 INTO WA_ZUSR02 .
MOVE-CORRESPONDING WA_ZUSR02 TO WA_Z1USRDET01.
CLEAR WA_EDIDD.
MOVE C_SEGNAM TO WA_EDIDD-SEGNAM.
MOVE WA_Z1USRDET01 TO WA_EDIDD-SDATA.
APPEND WA_EDIDD TO IT_EDIDD.
CLEAR WA_ZUSR02.
CLEAR WA_Z1USRDET01.
ENDLOOP.
Count the number of data segments.
DESCRIBE TABLE IT_EDIDD LINES V_NBSEG.
If the number of data segments exceeds the maximum allowed number,then display an error message.
IF V_NBSEG GT V_OCCMAX.
WRITE:/ 'ERROR'.
ENDIF.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
master_idoc_control = WA_EDIDC
OBJ_TYPE = ''
CHNUM = ''
tables
communication_idoc_control = IT_EDIDC
master_idoc_data = IT_EDIDD
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Reward points for helpful ans
Regards
Aarti

GEnerating IDOC from ABAP Program

Hello all,
we have a business scenario where we are usng XI.
We are generating SO IDocs for the scenario. here are my Questions:
1. the SO may be a create/modify/reject
2. they have to pass several checlks like ATP, Flag check etc..(Validation) which we are handling it by a user exit, once the checks are passed we have to generate idocs..i am aware that we do output determination to generte the IDOC but we are opting that.we are trung to generate the idoc thru a z-program. can anybody guide me whether we can generate an idoc thru a z-program, if so can someone provide with a sample code/steps to be followed.
Also can a BAPI generate an IDOC?

hi aarthi,
not only in your below scenario,for anycase we need a program to generate IDOC for eg MASTER_IDOC_DISTRIBUTE..
the best advice is to copy an existing inbound/outbound programs and modify it to your need.this what SAP is also suggesting...
Cheeers,
Abdul Hakim

Payment program (RFFOAU_T)

Hi,
Can any one please let me know the functionality of payment program and use of this program.
Thanks in advance.

Short text
Payment Medium for Australia - Bank Transfers/Debit Memo BECS
Description
The program issues data medium exchange in BECS, the disk format used by Australian banks.
As well as the payment media, the accompanying payment advice notes, data medium accompanying sheets and payment summaries can also be printed in one program run.
Requirements
Payment Program Configuration
The parameters that control the way in which the payment medium programs function are configured in Customizing. For more information on configuring the payment program, refer to the Implementation Guide.
Configure payment program
1. Here you need to make specifications for the paying company code. To do this, select the relevant paying company code by choosing Paying Company Codes ->.
If payment advices are to be printed, define a SAPscript payment advice form for use with all company code payment methods. You will find the form F110_IN_AVIS as an example in the standard system.
You need to create and enter text modules in which the texts for the header, footer, signature and sender are stored. These modules can be included in the forms when they are used. To do this, choose Sender Details, from where you can also branch into text maintenance by selecting the modules. The names of the text can be defined by the user, for example F_0001_HEADER for the letter header in company code 0001.
Proceed
2. Here you need to allocate the name of the payment medium program RFFOAU_T to the payment method to avoid incorrect payment media being issued with another program by mistake.
To do this, first choose Payment methods in country, then select the country of your paying company code and the payment method you require, and then maintain the data necessary for printing the form.
Proceed
3. Here you need to make company code specifications for the payment method. To do this, choose Payment Methods In Company Code, then select the paying company code and the payment method. In this menu maintain the following data by choosing Form data or Payment Advice Control:
The SAPscript form for accompanying sheets (F110_AU_BECS in the standard system) as the next form (for DME).
The issuer data.
Sorting the correspondence.
Sorting the line items.
Proceed
Note: You should fill out the issuer specifications as follows:
Line 1 Issuer's name (26 characters long)
Line 4 Issuer's city
4. You need to make further specifications for creating the payment medium in Customizing of the house banks. Select the relevant paying company code by choosing House Banks. In the maintenance of the house banks select your house bank and then maintain the required data via the button Data Medium Exchange. For more details refer to the online documentation for the relevant fields.
Proceed
Notes:
a) Common BSB numbers, which give a bank a unique identification, must be maintained for Australian banks. This three-character abbreviation is defined in the publication 'BSB Numbers in Australia', and is entered in the SAP system as part of the DME data maintenance in the field Altern. bank ID.
b) You need to maintain the lead days. The processing date (batch due date) is calculated from the posting date plus the lead days.
c) The company number (user identification number) is also transferred from the house bank's DME data.
Setting up and changing the SAPscript forms (layout sets)
The following describes the layout of the SAPscript forms in brief. If the forms available in the standard system are sufficient for your requirements, you can skip this part of the documentation.
You can find further information on forms and the SAPscript editor in the guides on styles and form maintenance and word-processing in the SAPscript editor: Select the menu path Help -> SAP Library.
1. When setting up SAPscript forms (layout sets), symbols are included in the text; these are then replaced by actual values when the payment medium programs are run. The fields which can be used for this are defined in the Repository and contained in the following structures:
REGUH Settlement data from the payment program
REGUP Edited invoice items from the payment program
REGUD Formatted data for printing the forms
SPELL Amounts and digits in words.
FSABE Data on accounting clerk.
2. If you want the document long text for an accounting invoice document to be printed on the payment advice form, you must make the following enhancement in element "Long text for invoice document" (specially designed for this purpose):
/: DEFINE &TXT& := '&REGUP-BUKRS()&&REGUP-BELNR(RF0)&&REGUP-GJAHR&'
/: INCLUDE &TXT& OBJECT BELEG ID xyz
The text ID that you must enter for this text (xyz) is defined in the configuration menu and can be read from there. In the standard system, text ID 0003 is predefined for the payment advice information.
Proceed
3. Layout of the payment advice form (F110_IN_AVIS in the standard system)
Pages
FIRST First page per payment advice
NEXT Subsequent pages if page overflow
EDI List of payment advice notes sent per EDI
LAST Form summary section per house bank
Windows and elements
HEADER Letter header
ADDRESS Sender and address of the payee
PAGE Page counter
INFODate, payment document number, etc.
INFO      605Account number of the sender at the recipient
INFO2 Information on the next pages
REPEAT Information for the test print or proposal run
MAIN Form of address before the letter
MAIN      610-x Short text for payment method x
MAIN      610 Letter when 610-x is missing
MAIN      612Alternative payee
MAIN      613 Notification takes place in order
MAIN      614 Signature
MAIN      615 Heading of the invoice item information
MAIN      620 Carryforward at page top after page overflow
MAIN      625Invoice item information
MAIN      625-TXLong text for invoice
MAIN      625-HRInformation line for Payroll Accounting
MAIN      630Sum total
MAIN      631 User-defined text after invoice items
MAIN      675 Header for EDI advices
MAIN      676List of EDI advices
TOTAL     630 Sum total of fixed items
CARRYFWD 635 Carryforward at page bottom for page overflow
FOOTER Letter footer
SUMMARY Form summary section
4. Layout of the data medium accompanying sheet (F110_AU_BECS in the standard system)
Pages
DME Accompanying sheet
LAST Form summary section for each house bank
Windows and elements
DOMESTIC 535 Accompanying sheet
Check that the SAPscript forms (layout sets) which you use have the layout described and, in addition, check that the forms are active (both in the original language as well as in all languages into which the forms were translated).
Proceed
Periodic processing
Before the payment medium programs can be started, the payment program run must have been successfully completed. Check the status of the payment run, or schedule the payment medium programs by specifying one or more variants.
Proceed
Note: If you want to use th 'Payment document update' option, the payment documents must be updated between the time of the payment program run and the time of the payment medium program run.
Output
Forms and lists
Printout files are created per company code and house bank. These can either be printed via the print manager or immediately. Depending on the parameter you select, you can print out one or more of the following:
Accompanying sheet for the payment medium
Payment advice notes (if the information cannot be sent via EDI)
Payment summary
Error log
The number of output files is specified in the flow trace; this makes finding and allocating them within the print manager easier.
Proceed
Note: If the program was started online, then you reach the print manager from the list by selecting one of the output files displayed.
Payment Advice Notes
In addition to being able to print payment advice notes, you can also send these via EDI, fax or email.
1. To send a business partner a payment advice note via EDI, you need to select the indicator Payment advice note per EDI and maintain the partner agreement on screen "Payment Transactions Accounting" in the master record.
Proceed
Using an external converter, the IDoc created by the program can be converted into the EDI format you require (REMADV for example) and then sent.
2. To send a business partner a payment advice note by fax or email, you must use the process interface 00002040 (Business Transaction Events) to define the selection of the message type (printout, fax or email). Before you can do this, however, you must have carried out the necessary technical (Basis) settings for faxing or sending emails.
Process interface 00002050 can also be used to change or configure the print parameters and the parameters for optical archiving for payment advice notes.
DME
Data medium exchange in this case involves the creation of a file which corresponds to the rules of the credit institution in question for automatic payment transactions and which contains all the necessary payment information.
The information relevant for the payment medium (file format, creation data, payment amount in local currency, payment documents involved etc.) are stored in the system and can be called up via the DME manager.
Other functions of the DME manager are:
Downloading the file into your local (PC) file system
Displaying and printing the file contents
Generating a payment summary for the data medium
Proceed
You will find further information about the structure of the data medium in the technical description.
Output in the file system
If required, the file can be written into the file system. The file created can be copied onto a PC via the DME manager. When doing this, you should search for files by download since the data medium is not managed within the SAP System but has already been stored in the file system by means of the payment medium program.
Proceed
If the file name is not to be specified by parameter, then it is generated by the program. It then consists of the disk format, date and time of creation as well as a consecutive number so that the file name in the file system is unique.
If the file name is specified by the user, then a consecutive number is likewise added for each program run. From an organizational point of view, however, you should make sure that already existing files are not overwritten.
Note: If you cannot find the file via the DME manager, then this can be due to the following reason: the directory which was written to when the payment medium program was started (for example, in background processing), cannot be read online. Therefore you should choose a directory which can be written to and read by different machines.
Due to the above-mentioned problems and the affect this has an data security, it is advisable not to write data to the file system. It may be advisable to use this method in cases where the data medium file is 'picked up' from the file system by an external program to be passed on to the bank.
Output in the TemSe
If required, the file created can be stored within the SAP System (stored in the TemSe and not in the file system), thus protecting it from unauthorized external access. You can download the file into the user's file system via DME management.
The name of the file to be created during the download can be determined when running the payment medium program; the contents of the file name parameter are stored in the management data and defaulted when running the download.
Proceed
User exit
You can modify the dataset for data medium exchange by using the user exit interface defined. You can, however, only change the fields of the DTAMAU0 structure.
Creating a user exit
The print program calls up the EXIT_RFFOEXIT_210 function module. Please take the input and output parameters for the user exit from the function module interface.
Proceed
Create an include file with the name ZXFORU32 to program the modifications required.
Proceed
The file is included in the EXIT_RFFOEXIT_210 function module. Use the Enhancements transaction for activating or deactivating your user exits by activating or deactivating the RFFOX210 project affected.
Proceed
Error messages and error log
Termination of processing
You can find out the reason why processing was terminated (for example, production run not yet carried out, form does not exist or is not active) by looking at the error message or the related long text.
Internal SAPscript error
Check the layout of the forms. It must fulfil the above-mentioned conditions. You cannot, for example, create a bank transfer with the check print program, since bank transfers and checks have a completely different layout structure.
Error log
If errors which do not terminate the payment medium program occur when creating the output, the system lists them in the error log. If such a log is created, you must look it over because only you can decide whether the payment medium or payment advices are useless due to the errors the system finds, and decide whether they must be recreated after the errors have been rectified.
During background processing, the system outputs the error log twice, in the flow trace for the job and in a printout file. The flow trace contains information on how to rectify the errors (from the error message long texts).
You can display the long text online by choosing the error log from the list of generated output files and then the error message in question.
plz reward points if dis helps

Payment Programe Foreign Exchange Gain/Loss

Hi,
Our Co. Code Currency is CAD. I Configured Payment Programe with Two Different Currency i.e. in CAD & in USD. I posted the Invoices in two different currency.
Now, while i was running payment programe, it clears the payment in appropriate currency. but if payment runs in USD then it's not showing me Foreign Gain/ Loss?
Can anybody please let me know why it's happened or How i can over come with this problem.
Your help will be really appreciate.
Thanks,
Niki Shah.

Please help me,
When i run the payment program the system does not calculate the gain/ loss.
My company runs in USD when i make the payment in AUD it doe dont do the gain/loss.
What settings should i do or what am i missing, because it generating the payment but at the invoice date rate not payment date rate.
Then when i get to send the file to the bank, how do i reconcile the bank rate and the payment rate or how does the EBS know how to reconcile the two.
I will really appreciate it.
Thank you.

Generating IDOCs

Hi,
I am working on SAP Retail implementation. As a part of point of sale (POS) integration, I need to work on following messages:
- purchase orders
- Goods receipt
- Physical inventory
please let me know how to generate these idocs in SAP. We have WPMA/WPMU for generating idocs for other message types.

Hi,
For generating IDOCs you have to configure your ALE settings and you can use Tcode WE19 for testing(Generating) IDOCs. You have to use the appropriate message type to trigger the IDOC.
For creating purchase order you can use Tcode ME21.
Also if you know ABAP then you can create a program to generate an IDOC based on your requirements. Follow this program to generate IDOCs.
http://www.sap-img.com/abap/program-to-generate-idoc.htm
Regards
Sumit Bhutani

Payment program F110 not generating IDoc

Hi All
while running payment program F110 I get a sucess message IDocs generated for company code and payment method, In the payment log i see this infomation.
when i check these IDoc's in WE02 I can't find any of these IDoc's. It looks to me the program RFFOEDI1 with the variant I created is not getting executed in spite of the check box "Generate IDoc" being checked.
can any one suggest what would be wrong?
Thanks
Pranav

Hi All,
Thanks for the quick response. Following are the config made with forms;
In Paying company code setup:
    Form for payment adivce: F110_US_AVIS
    EDI accompanying sheet form: F110_EDI_01
In Payment method in company code:
    Form for payment medium : F110_EDI_01
    Next form : F110_US_DTA
I have checked with all other configuration and seems to be in place. Please let me know if these config regarding forms are correct.
When I run the program REFFOEDI1 with the variant I created these IDocs are getting generated. These are not getting generated when I run the payment program F110. I am missing some thing which is not triggering this program from payment program. Please let me know if you have any suggestion.
Thanks
Pranav

Not generating IDOC for payment Advice to Vendors

Hi,
IDOC was getting generated before one month but now SAP system has stopped generating IDOC for vendor Payment advice. This problem is with all the vendors.
After execution of t-c-ode F110, payment document is successfully created, but IDOC is not geenerated. There is no log about "IDOC not getting generated"
Checked Table REGUH, IDOC number is displayed as 0000000000000.
This was happening perfectly one month back.
There is no change in Vendor master data, IDOC number range is available.
There is no posting of IDOC in table DFKKTHP and checked Report REREMITADV for which there is no data.
Waiting for your valuable responses.
Regards
veleyudham

Hi,
First check certain customization:-
(1) FBZP setup for payment method at country level. Whether IDOC generation program is assigned or not.
(2) Then check the variant of RFFOEDI1 in the printout tab of F110. Is the selection creteria OK?
(3) Check the partner profile in WE20 for the bank.
Then run the program RFFOEDI1 in SE38 for your payment run and check the output.
You can also get this program debugged from you ABAPer to have root cause analysis.
Regards,
Gaurav

Payment Program - Generate additional clearing documents

Hi.
When executing an FPY1 payment run, say for a contract account. All open items that fall on the same due date are grouped into one payment document.
Due to restrictions set by our reserve bank no direct debit may exceed R50000.00. For this reason we need generate payment documents not exceeding R50000.00 but equalling the payment amount.
Eg:
3 open items all due on the same day: R200000.00, R600000.00 & R50000 = R850000.00
Instead of one payment document of R850000.00 we need 2 payment documents of R500000.00 and R350000.00 respectively.
Does any one know how this can be achieved?
Using the events provided is seems you can manipulate the document generated but not the amount of documents generated.
Any help will be appreciated. Thanks
FPY1 - IS-U - FICA - Automatic Payment Program - Direct Debit

Hi.
I think that you should look into event 0610. It should be possible there to change amounts of payable units. Check documentation of the event for name of structure holding changeable items.
Best,
Jean-Marie

Automatic payment program configuration process

Dear All,
My client is useing Automatic payment program with pyment methode "cheque" in 4.6c version. Now my client wants to go for other payment methodes... i.e,.....
1. NEFT payments - online Transfer to vendor account
2. RTGS payment Methode
3. Book Transfer.
can anybody let me know the configuration process of the above methodes. Early replies with configuration process are highly appreciated.
Thanks & Regards,
swathi

Hi
Output format and required fields of file format have already taken from bank. But SAP configuration point of view i need help.
Thanks & Regards,
Swathi
Edited by: swathi fico on Sep 21, 2009 2:44 PM
Inputs from anybody please
Edited by: swathi fico on Sep 22, 2009 3:57 PM

Configuration of Check printing in Automatic Payment Program

Hi
I am able to run the automatic payment program. But I am not sure how to configure check lots and check printing. Could any one please help me with step by step instruction regarding the configuration required after running the program.
Thanks
Hariharan G

Hi
For the program RFFOUS_C give Variant(X).
select maintain Variants button and select continue button.
give program run date , Identification feature , paying company code , sending company code , payment method , House Bank , Account ID , Check Lot NO..
Under Print Control
select Print checks checkbox , give printer name and select print immediately checkbox.
select Print Payment Advice Notes checkbox , give printer name and select print immediately checkbox.
select Print Payment Summary checkbox , give printer name and select print immediately checkbox.
No. of sample printouts (0) and select do not Void any checks checkbox.
select Attributes button and give description and save.select back arrow.
select Printout button and select Start Immediately checkbox.
In the job name for the ? give variant name(X) and enter.
To see the printed checks from the menu select System -
>Services -
>Jobs -
>Job Overview(SM37) and execute.
Also go to SP01 and execute.
we will get the list of spool requests.
Regards
Venkat
Edited by: Venkat Dara on Feb 4, 2009 12:55 PM

Payment program configuration

Hi,
We have a payment program config issue. We have around 14 company codes. For all the company codes we have only one paying company code 2000. Now for a company code 1000, we want to pay some project related expenses by the particular company code only (ie1000). But all the other usual expenses to 1000 would be paid by the company code 2000 itself. So, technically, we need to pay the expeses incurring in company code 1000 part by 1000 and part by 2000. How can we achieve this? What might be the work around for this?
Thank you in advance.
Regards,
Avin

You are right (you are NOT missing anything)! I just didn't think from that angle. In FBZP 'All company codes', you can have only one entry per company code; and currently 2000 is assigned as paying company code for company code 1000. Why don't you leave this configuration (All company codes) at it is in your system currently, configure the rest and test it?
Alternatively, why not let CoCd 2000 make these payments also (I have a feeling that the above solution is not going to work**&!^%) - you anyway have interco posting between 1000 & 2000 right? Also, read the sections 'Company code specifications' and 'Cross-Company Code Payments' in the following link. I read it a couple of times, but not getting any solution for your problem there - may be you will see something that I am not able to!!!
http://help.sap.com/saphelp_erp60_sp/helpdata/en/47/8bf634b576bc4ee10000009b38f83b/frameset.htm
Good luck!!! And please post in the forum if you find a solution - it is a really good problem that you have come up with!

How to generate checks when executing Automatic Payment Program (F110)

Is it possible to generate checks automatically when I execute the automatic payment program? Will reward points to any suggestion. Thanks!

hi patrick
try this.....ur problem may solve.....
Create Automatic Payment Transactions (F110)
Purpose
Use this procedure to generate checks proposals or ACH proposals and then subsequently issue checks or set up ACH files to be transmitted to the bank.
Trigger
Perform this procedure when through either an ACH or a check, a creditor of the University needs to be paid.
Prerequisites
Open invoices with reached due dates have to be present in the SAP system.
Menu Path
Use the following menu path to begin this transaction:
·         Select Accounting Financial Accounting Accounts Payable Periodic processing Payments to go to the Automatic Payment Transactions: Status screen.
Transaction Code
F110
Business Process Information
The automatic payment process will be centrally managed in the Accounts Payable Office. The automatic payment program will be executed each day for all open invoices (across vendors) in the system. There will be separate payment run execution corresponding to each payment method category:
Check payments: clears the open invoices and issues a check output
ACH payments: clears the open invoices and issues an ACH file output
Foreign currency payments: clears open invoices but no output is issued
State/Grant payments: clears open invoices but no output is issued
The process steps executed during the automatic payment program are:
Enter Payment Parameters
Edit/review Payment Proposal
Post Payments
Generate Payment Medium (print checks or create ACH payment file)
Generate Positive Payment File
The payment parameters are entered in order to limit the open invoices and credits selected for payment. It is important to note that the payment terms that are defined on the invoice will drive whether a invoice is due for payment during the current payment run. During the payment program execution, the invoices that are due for payment will be presented to the user on a payment proposal list.
The payment proposal is a list of expected payments grouped by vendor account. Invoices that are due for payment but cannot be paid due to some kind of accounting or system error are listed as exceptions. Examples of typical exceptions are missing banking information (for ACH payments) and blocked invoices. Some payment exceptions will be resolved at the Accounts Payable Office. However the Department must resolve some exceptions. When these types of exceptions appear on the payment proposals, the Accounts Payable Office will inform the Department of the blocked payment in order to get a resolution. Key personnel in the Accounts Payable Office will be the only resources to have access to the editing function of the payment proposal processing. Typically, there is no business reason the edit or change a payment proposal. Editing options for a payment proposal includes: changing the default disbursing bank account information or changing the payment method.
After the payment proposals have been reviewed and edited, the proposals are posted as payments. It is important to note that any open credit on the vendor's account is also taken in consideration when creating the vendor's payment. The payment method supplement defined on the invoice will drive the check sorting.
In addition to the printed check output, the payment program run produces an ACH file and a Positive Pay file. Both files are sent to the bank for further processing. The ACH file contains the vendor's payment and banking data. The Positive Pay file contains the check data (check processed, voided, etc) and is used for confirmation of payments.
Helpful Hints
·         The R/O/C column in the field description tables below defines whether the field is required (R), optional (O), or conditional (C).
·         On certain screens you may have to scroll to view some data entry fields.
·         Click the tab to view the current overall status of the payment process by viewing the informational messages.
Procedure
1. Start the transaction using the menu path or transaction code.
    Automatic Payment Transactions: Status
2. As required, complete the following fields:
·         Run date
·         Identification
3. Click the tab.
The payment program parameters are used to limit the program's selection of open invoices and credits.
    Automatic Payment Transactions: Parameters
4. As required, complete/review the following fields:
·         Posting date
·         Docs entered up to
·         Company codes
·         Pmt meths
·         Next p/date
·         Vendor
5. Click the tab.
Free selection criteria are extended parameter selection criteria used to limit the open invoices and credits selected in the payment run.
    Automatic Payment Transactions: Free Selection
6. Perform any of the following:
If You Want To
Then
Select data by a particular field value; use the match code on the Field Name field to obtain the required field
Enter the required field value to be considered in the payment program selection of open items. The field value is entered in the Values field
Payment selection can be based on fields on the invoice or credit memo document or fields on the vendor master.
Example: A (AP payment block)
Exclude the open items that match your field value
Select to the left of Exclude values.
Include only those open items that match your field value
Deselect to the left of Exclude values.
7. Click the tab.
This information is used to expand the information that is automatically recorded in the payment run log. The payment run log is used to diagnose any program errors during the payment run.
    Automatic Payment Transactions: Additional Log
8. Perform the following:
If You Want the Payment Program Log to Record
Then
Information on due date check
Select to the left of Due date check.
Activate this option.
Any payment method selection data
Select to the left of Payment method selection in all cases.
Activate this option.
Line item information the payment documents generated upon posting the payment proposal
Select to the left of Line items of the payment documents.
Activate this option.
9. As required, complete/review the following fields:
·         Vendors (from)
·         Vendors (to)
Enter the same vendor account number range for Accounts required section of the transaction.
10. Click the tab.
The specifications defined in this section of the transaction inform the payment program the correct form to use for check printing and the correct payment file format to use for ACH payments.
    Automatic Payment Transactions: Printout and DME
11. As required, complete the following fields:
·         RFFOAVIS
·         RFFOUS_C
12. Click the tab.
    Exit editing
13. Click to save the data.
If you want to delete the payment program parameters entered, select Edit Parameters Delete.
    Automatic Payment Transactions: Status (2)
The system displays the message, "Details have been saved for the run on XX/XX/XX XXXX."
14. Click .
If you want to refresh the screen in order to view the current status (processing step) of the payment program click at any time.
    Schedule Proposal
15. Perform one of the following:
If You Want To
Then
Execute the payment program (i.e. process the payment parameters entered and create a payment proposal) immediately
Select to the left of Start immediately.
Activate this option.
Designate a target computer
Enter the name in the Target computer field.
16. Click to process the payment parameters and create a payment proposal.
While the payment program is selecting and processing data, the status will display the message, "Proposal is running." When the payment proposal has completed and is ready for review/edit, the system will display the message, "Payment proposal has been created."
    Automatic Payment Transactions: Status (3)
The system displays the message, "Proposal run has been scheduled."
17. Click .
    Automatic Payment Transactions: Status (4)
The system updates the status, "Payment proposal has been created."
18. Perform one of the following:
If You Want To
Then
Go To
Execute the payment run
Click .
Step 19
Edit the payment proposal
Click .
Step 43
Display the payment proposal
Click .
Step 54
Display the payment proposal run log
Click .
Step 57
Delete the proposal
Select Edit Proposal Delete.
Step 60
Display the proposal list in a printer friendly format
Select Edit Proposal Proposal List....
Step 62
Display only the exception (error) invoices or credits
Select Edit Proposal Exception List....
Step 67
Exit this transaction
Step 72
    Schedule Payment
19. Perform the following:
If You Want To
Then
Execute the payment program (i.e. process the payment parameters entered and create a payment proposal) immediately
Select to the left of Start immediately.
Activate this option.
Designate a target computer
Enter the name in the Target computer field.
20. Click to process the payment proposal and post the payment documents.
While the payment program is selecting and processing data, the status will display 'Payment is running'. When the payment proposal posted the status will display 'Payment run has been carried out. Posting orders X generated, X completed. (X will represent the total number of checks produced).
    Automatic Payment Transactions: Status (5)
The system displays the message, "Payment run has been scheduled."
21. Click .
    Automatic Payment Transactions: Status (6)
The system updates the status, "Payment run has been carried out." If you click after seeing the status update, "Payment run has been carried out", the system will display an update to the status, "Posting orders: XXXX generated, XXXX completed."
22. Perform one of the following:
If You Want To
Then
Go To
Review the payments posted
Click .
Step 23
Display the payment proposal
Click .
Step 26
Display the payment proposal run log
Click .
Step 29
Display the payment list in a printer friendly format
Select Edit Payments Payment List.
Step 32
Display only the exception (error) invoices or credits
Select Edit Payments Exception List.
Step 36
Print the payment run information
Click .
Step 40
Exit this transaction
Step 72
    Job Log Entries for F110-XXXX-XXXX / XXXX
23. Review the displayed information.
24. Click .
25. Return to Step 22.
    Display Payment Proposal: Payments
26. Review the displayed information.
27. Click .
28. Return to Step 22.
    Job Log Entries for F110-XXXX-XXXX-X / XXXX (2)
29. Review the displayed information.
30. Click .
31. Return to Step 22.
    List Variant
32. Click .
    Payment list
33. Review the displayed information.
34. Click .
35. Return to Step 22.
    List Variant (2)
36. Click .
    Payment list (2)
37. Review the displayed information.
38. Click .
39. Return to Step 22.
    Schedule Print
40. As required, complete/review the following fields:
·         Start date
·         Start immediately
·         Start time
·         Target computer
·         Job name
41. Click .
42. Return to Step 22.
    Accounting clerk
43. Click .
    Edit Payment Proposal: Payments
44. Review the displayed information.
45. Perform one of the following:
If You Want To
Then
Go To
Continue with the payment process
Click .
Step 18
Review/edit invoice information for the payment (invoice numbers, discounts, payment amounts, etc).
1. Click on the line you want to select.
2. Click .
Step 46
Change the key payment information (payment method, house bank, payee name and address, etc.)
1. Click on the line you want to select.
2. Click .
This option does not work for lines that have exceptions.
Step 51
    Edit Payment Proposal: Open Items
46. Double-click on the line you want to choose.
    Change Line Items
47. As required, complete/review the following fields:
·         Payment block
·         Discount amount
·         Cash discount %
48. Click .
49. Click .
50. Return to Step 45.
    Change Payment
51. As required, complete/review the following fields:
·         Payment method
·         Pmt meth.supl.
·         Due date
52. Click .
53. Return to Step 45.
    Display Payment Proposal: Payments
54. Review the displayed information.
55. Click .
56. Return to Step 18.
    Job Log Entries for F110-XXXX-XXXX-X / XXXX (3)
57. Review the displayed information.
58. Click .
59. Return to Step 18.
    Delete proposal
60. Click .
    Automatic Payment Transactions: Status (7)
The system displays the message, "Data and log deleted."
61. Go to Step 72.
    List Variant (3)
62. As required, complete the following field:
·         Variant
63. Click .
    Payment list (3)
64. Review the displayed information.
65. Click .
66. Return to Step 18.
    List Variant (4)
67. As required, complete the following field:
·         Variant
68. Click .
    Payment list (4)
69. Review the displayed information.
70. Click .
71. Return to Step 18.
72. Click until you return to the SAP Easy Access screen.
73. You have completed this transaction.
Result
You have executed a payment proposal, executed and posted a payment run and printed checks.
reward me points.......dont forget

Transaction F110: Payment program: RFFOUS_D

Hi,
I have copied the standard payment program RFFOUS_D for check printing into a Z program and included the code to create the Idoc.
Further I have done all the configurations like assigning the program to company code and house bank for the country and it is visible in transaction F110.
The problem is when i run a payment run and select this Z-program nothing happens in the payment run log there is a message which says <b>'no record found'</b> and there is no creation of Idoc. I have tried debugging but no output.
Please suggest what can be the problem.
/Manik

Hi Srinivas,
The intresting thing is that payment is getting posted and a document is also generated as a result which can be seen via transaction FB03.
We want user to select the check lot number manually and then send that check number in the idoc. The standard SAP program does not support this requirement.
/Manik

Automatic payment program - urgent

Dear all,
i configured automatic payment program. when i run the automatic payment program using f110, accounting documents to Vendor account and house bank account are not generated. In the status bar, only the following messages appear:
"Parameters have been entered"
"Payment proposal has been created"
"Payment run has been carried out"
The following message is not appearing:
"Posting orders: X generated, X completed."
Can anyone guide me to solve this issue?
Will award maximum points.
Thanks in advance,
Regards,
ar

Hi,
You get the message Posting orders X(Ususally no. of documents) generated and X completed, it means that your proposal was successful. You will not get the document number in the status. Click on the Payment proposal log to view the document number generated.
Regards
Sridhar

Configure payment program to generate idoc

Similar Messages

Maybe you are looking for