Payment Program Output

I am in asupport prj.I am aware about the payment program and its functionalities and configuration.
I am am unaware of how the checks or other payment methods are transffered to outbound interface and their relevant functionality or configuration.Actually I am unable to follow in SAP the output of payment program.
It would be helpful if any document is available.

Hi
Please have a look at the thread
[Re: Issue in Payment run]
Let me know if you require any further info.
Thanks
Kalyan

Similar Messages

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

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

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

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

Add fields to payment program

Hi Gurus,
I have a question regarding the rffo* classic payment program. I wanted to add more fields in the file that is going to be generated. However i am not able to find out how to do it like should i extend the reguh and regup tables or i should use a exit where in i call add the new fields. please help required ..
rgds
Edited by: SAPgopi on Apr 21, 2011 11:15 PM

Hi Amir,
The program documentation for the report RFZALI20 contains technical instructions for enhancing the output options.
As mentioned in the same, the ABAP dictionary structures REGUH_LST (header information) and REGUP_LST (line item information) contain the output fields provided by program RFZALI20. You can modify these fields to suit your requirements using the CI_INCLUDES CI_REGUH_LST and CI_REGUP_LST.
Also you can refer to consulting note 895843, which discusses on listing the payment request and the ordered payment amount in report RFZALI20. You can use this note as your guide and take hints from this to achieve your Business requirement.
Hope this helps.
Kind Regards
Soumya

Payment Program Document not automatically Cleared

Hi,
We created payments through F110 payment program and the vendor invoices were paid on 14th October.
We then ran the program again on 31st October and the same invoices were paid again.
We use the payment list to manually pay the telegraph transfer.
On investigation I can see the the payment document for the one on the 14th didnt automatically create a clearing document and is still open.
Can anyone tell me how this would not clear down and how to check for such errors if they seem to go through the payment program ok.
Thanks

Hi,
I could look into Tolerance Groups are proper set for the Company Codees. If the Tolerance Groups are not set properly, it would stop from clearing the documents.
I also hope you have set the config. steps proper in FBZP.
Regards,
Ravi

Questions on the SAP payment program

Hi everyone,
Here are general questions the SAP payment program. Even partial answers would be greatly appreciated. Thanks in advance!
Questions:
What are the type of accounts involved in a payment transaction? In which case a customer account could be involved?
What could "payment proposal run" mean and imply?
What could be done as "editing a proposal run"?
In the "print payment media" step, what does DME stands for?
And in general, what are the diffenrences between a posting and an FI document?
Is the payment run launched automatically?
Thanks again
SB

What are the type of accounts involved in a payment transaction? In which case a customer account could be involved?
You will make the payments to vendors and customers accounts. Customer accounts may involve where you would like to make payment for the advance that you have received from customers.
What could "payment proposal run" mean and imply?
Payment proposal is nothing but SAP will give you a simulation showing what are the invoices going to be paid, what are the invoice not going to be paid (exception) due to various reasons.
What could be done as "editing a proposal run"?
In Editing the Payament proposal, you can block a invoice, which you would not like to make the payment. You have to create the payment block specially for the purpose of payment proposal.
In the "print payment media" step, what does DME stands for?
DME - Data Medium Exchange
And in general, what are the diffenrences between a posting and an FI document?
Posting is posting a document into the system.
FI document is a document having debit and credit totalled. To post a document both and debit and credit must be tallied.
Is the payment run launched automatically?
There is no automatic launching of Automatic Payment Program. You can schedule the job in background, but I would not recommend this. I would recommend the user to enter the parameters, run proposal, execute payment run and print the media.
Regards,
Ravi

Getting Error While Attaching Concurrent Program Output PDF file for POAPPRV Workflow

Hi All,
I am getting the below error when I am trying to attach concurrent program output to the PO Approval Notification.
An Error occurred in the following Workflow.
Item Type = POAPPRV
Item Key = 1040589-528378
User Key =945871
Error Name = WF_ERROR
Error Message = [WF_ERROR] ERROR_MESSAGE=3835: Error '-20002 - ORA-20002: [WFMLR_DOCUMENT_ERROR]' encountered during execution of Generate function 'WF_XML.Generate' for event 'oracle.apps.wf.notification.send'. ERROR_STACK=
Wf_Notification.GetAttrblob(3604701, ZZ_PREVIOUS_PO_COMPARE, text/html)
WF_XML.GetAttachment(3604701, text/html)
WF_XML.GetAttachments(3604701, http://oraerp.am.corp.xxxx.com:8099/pls/DEV, 11283)
WF_XML.GenerateDoc(oracle.apps.wf.notification.send, 3604701)
WF_XML.Generate(oracle.apps.wf.notification.send, 3604701)
WF_XML.Generate(oracle.apps.wf.notification.send, 3604701)
Wf_Event.setMessage(oracle.apps.wf.notification.send, 3604701, WF_XML.Generate)
Wf_Event.dispatch_internal()
Error Stack =
Activity ID = 190844
Activity Label = AL_NOTIFY_APPROVER_PROCESS:ZZ_PO_PO_APPROVE_ATTCH
Result Code = #MAIL
Notification ID = 3604701
There are several threads for this error however I cannot find any specific solution to the problem.
Please find the code below -
    wf_engine.setitemattrdocument(itemtype=>itemtype,
                                  itemkey=> itemkey,
                                  aname=>'ZZ_PREVIOUS_PO_COMPARE',
                                  documentid =>'PLSQLBLOB:zz_po_reqapproval_init1.xx_notif_attachments/' || to_char(l_request_id_prev_po)||':'||to_char(l_document_num));
-- here l_request_id_q_and_s is the request id of the program and l_document_num is the PO document number
PROCEDURE xx_notif_attachments(p_request_id    IN VARCHAR2,
                               p_document_num IN VARCHAR2,
                               p_document      IN OUT BLOB,
                               p_document_type IN OUT VARCHAR2) IS
v_lob_id          NUMBER;
v_document_num    VARCHAR2(15);
v_document_prefix VARCHAR2(100);
v_file_name       VARCHAR2(500);
v_file_on_os      BFILE;
v_temp_lob        BLOB;
v_dest_offset     NUMBER := 1;
v_src_offset      NUMBER := 1;
v_out_file_name   VARCHAR2(2000);
v_conc_prog_name VARCHAR2(500);
v_conc_req_id     NUMBER;
CURSOR get_output_file(p_concurrent_request_id NUMBER) IS
    SELECT cr.outfile_name, cp.concurrent_program_name
      FROM fnd_concurrent_requests cr, fnd_concurrent_programs_vl cp
     WHERE request_id = p_concurrent_request_id
       AND cp.concurrent_program_id = cr.concurrent_program_id;
BEGIN
--    set_debug_context('xx_notif_attach_procedure');
v_conc_req_id := to_number(substr(p_request_id,
                                     1,
                                     instr(p_request_id, ':') - 1));
v_document_num := substr(p_request_id,
                           instr(p_request_id, ':') + 1,
                           length(p_request_id) - 2);
OPEN get_output_file(v_conc_req_id);
FETCH get_output_file
    INTO v_out_file_name, v_conc_prog_name;
CLOSE get_output_file;
v_out_file_name := substr(v_out_file_name,
                            instr(v_out_file_name, '/', -1) + 1);
v_file_name     := to_char(v_document_num) || '-Previous_PO_Rev.pdf';
utl_file.fcopy(src_location => 'APPS_OUT_DIR',
                 src_filename => v_out_file_name,
                 dest_location => 'PO_DATA_DIR',
                 dest_filename => v_file_name);
-- v_lob_id := to_number(v_document_id);
v_file_on_os := bfilename('PO_DATA_DIR', v_file_name);
dbms_lob.createtemporary(v_temp_lob, cache => FALSE);
dbms_lob.fileopen(v_file_on_os, dbms_lob.file_readonly);
dbms_lob.loadblobfromfile(dest_lob    => v_temp_lob,
                            src_bfile   => v_file_on_os,
                            amount      => dbms_lob.getlength(v_file_on_os),
                            dest_offset => v_dest_offset,
                            src_offset => v_src_offset);
dbms_lob.fileclose(v_file_on_os);
p_document_type := 'application/pdf;name=' || v_file_name;
dbms_lob.copy(p_document, v_temp_lob, dbms_lob.getlength(v_temp_lob));
EXCEPTION
WHEN OTHERS THEN
    wf_core.CONTEXT('ZZ_PO_REQAPPROVAL_INIT1',
                    'xx_notif_attachments',
                    v_document_num,
                    p_request_id);
    RAISE;
END xx_notif_attachments;
Please help me find a to the above mentioned error.
Thanks,
Suvigya

There are two ways to look at what error the PLSQLBLOB API is throwing.
1) Call your PLSQLBLOB API GNE_PO_CREATE_FILE_ATTACHMENT.Gne_Create_File_Attachment directly from a PLSQL block and verify that it returns the BLOB data successfully.
You could also call another WF API that in turn executes the PLSQLBLOB API internally. For example,
<pre>
declare
l_document blob;
l_doctype varchar2(240);
l_aname varchar2(90);
begin
dbms_lob.CreateTemporary(l_document, true, dbms_lob.Session);
-- 207046 - This is the notification id of your failed workflow
-- PO_REPORT - Document type attribute
-- 'text/html' - Content Type being generated for
Wf_Notification.GetAttrBLOB(207046, 'PO_REPORT', 'text/html', l_document, l_doctype, l_aname);
-- Print the size of the document here to verify it was fetched correctly
end;
</pre>
2) Turn on log for SYSADMIN user with following attributes.
Log Enabled = TRUE
Log Level = ERROR
Log Module = wf.plsql%
Restart the Workflow Deferred Agent Listener and Workflow Notification Deferred Agent Listener and run your workflow process. Search for log messages written for above context and you can identify the error at wf.plsql.WF_XML.GetAttachment module with message starting as "Error when getting BLOB attachment ->"
Hope this helps.
Vijay

BI Publisher Charts not getting displayed in concurrent program output

Hi,
I am using BI Publisher version 11.1.1.3.0 on Windows 7 with word 2007. After creating the Bar chart in RTF template of BI publisher when I load sample XML data and check it in "Preview" is displays the output correctly.
My requirement is to print the charts in concurrent program's output on EBS version 12.1.1. (preferably HTML but PDF will also do) However when I run the concurrent program which processes the data definition and the RTF template registered for this report, the output is just an image of the chart. The XML output generated by the program is not reflected in the chart display at all. (I have verified that XML is generated properly)
Can someone please let me know if there is some setup required to make the charts display properly in concurrent program output?
I have also tried BI publisher version 10.1.3.2.1 for this. With this the concurrent program output is just blank. Not even an image is displayed.
p.s. The program uses standard executable XDODTEXE (which is normally used to run BI publisher reports)
Thanks,
Archana

Hi,
I have finally found solution to this issue....
Two setups are required to display the charts in the concurrent program's PDF output:
1. We need to edit the variables CLASSPATH and AF_CLASSPATH. These variables should have the complete path added for the xdoparser.zip file on the server.
2. The DISPLAY variable should be correctly setup to direct the server output.
Also as per my findings so far, the BI (XML) publisher version 11.1.1.3.0 (or any 11g) does not work with EBS (at least for charts). We need to use BI publisher version which is XML 5.6.3 compatible for EBS. This version is 10.1.3.2.1. (patch 12395372) Now this 10g version does not work on Windows 7 so you need to use Windows XP!
With this... finally... your charts should be getting displayed in EBS output...
Cheers!! :-)
Archana

Clear Down payment against Vendor Invoice through Automatic Payment Program

Hi
We have to adjust vendor invoice against down payment (Advance) made through automatic payment program (F110)
Please guide us is there any configuration require to consider Down payment transactions during F110 to clear against Vendor Invoice
Ex :1. Advance payment made through special GL indicator 50K.
2. Invoice document 75K posted in vendor.
3. Now we have to clear down payment made (50K) against 75K through F110.
Regards
Sreenivasulu

Hi srinivasulu,
First u create down payment request through F-47 and define the spl gl indicator for down payment and assign the gl account for down payment gl code..
Regards,
Nivas

Payment program F110 for Vendor Open Item in Foreign currency

Dear sap Guru
Is it possible to Ensures that no exchange rate differences are posted by the payment
Program? I mean: The amount in the bank posting in local currency does not result from translating the foreign currency amount at the current rate but from the total of the local currency amounts from the settled items.
Best regards
marco

Dear PAtel,
I checked and the ther eis the check box 'No exchange rate differences' anyway during the payment program execution the system is making some recalculation for open item in fc.
Someone knows what is the coloumn "Valuation Difference" in the Dysplay Payment Proposal Open Item list?
regards
marco

Automatic payment program - error No permitted payment method exists

Hi All,
I am doing the automatic payment run and done all the necessary config in FBZP.
1) Created the payment program at country level and assigned payment program
2) Created the payment method at company code level for check and assign the Check Form
3) Coming to Bank determination:
   a) Ranking order : given the payment method(A -> Check) ,currency(MYR), ranking order (1) and assigned to house bank (CIMB)
   b) Bank accounts : given house bank , payment method ,currency, account ID and clearing account number.
4) assigned the payment method (A) in vendor master.
when i run the payment run for the vendor in F110 for company code system hitting below errors:
> -
Payment method selection additional log----
> Payment method selection for items due now to the amount of MYR      112,909.38-
> Payment via payee/payer 0550000008
> Payment method "A" is being checked
> Payment with 28 print items, only 16 are allowed
> No permitted payment method exists
Information re. vendor 500000598 / paying company code 0546 ...
......payment not possible because of reported error
End of log
Job finished
please can any body help me on this. I done the same config in DEV and QAS. there working fine with out any issue.   but coming to PRD its giving problem. i double confirm the config in DEV to pRD every thing fine and same.
thanks.
Sandhya.

Hi...
I did check the 1) vendor address -> No gaps
2) My one is check printing not bank transfer
3) I did check all the vendor line items no payment blocks. user already unblock the relevent item to make payment.
Here weird thing is system hitting the same above mentioned error even I updated the payment method(C) and house bank (CIMB) in each and every line item of vendor invoice.
Thanks,
Sandhya.

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

Payment not clearing for Vendor through Automatic Payment Program

Hi
I had setup automatic payment program for my vendor to take $ from my GL account. When I run the payment program, it ran without any error, however, the vendor account was not cleared. The balance in GL and Vendor account remains the original amounts.
The log shows the following.
Job started
Step 001 started ( program SAPF110S, variant &0000000001081, user ID XXXXXXX)
Log for payment run for payment on 01/12/2008, identification XXXX
End of log
Job finished
Can anyone help ?
Thanks
Shalini

I have not proposed a solution. Now go to F110 and go to the table additional tab and press proposal log button on the lower right hand side. this will give a detailed log. Either analyse this error set right error or send the error log for analysis.
First run the proposal run and if it is successful, run the payment run and then to print run.
It should be run in the above sequence.
Edited by: Sivakumar Gopalakrishnan on Jan 12, 2008 7:54 PM

Payment Program Output

Similar Messages

Maybe you are looking for