Other types of payments processing.

I know Paypal don't support e-check payments unless the customer have an account with them to transfer funds.
There is any way ACH Direct will be supported? They do process payments via Credit Cards or E-check.
Also i tried to setup the form to do Mail payment instead of going thru paypal and it doesnt work. The form still goes thru Paypal because the field of the payment is greater than $0.
The help setting ths is very vague ad not very helpful. It would be nice if a tutorial is created.
Thank you,
Jose

Hi Randy;
Thanks for your reply. I did the steps you mentioned but is not helpful at all. In order to avoid to go tru Paypal my amounts needs to be $0.
Also, the Notification email to the customer don't have the description of what they bought, the total amount that needs to be paid etc.
So is kinda useless to do a pay by check this way if none of that info is provided to the customer inside the notification email neither stored in the all response table within the form.
I even looked at the All Response table in the form and the amount is blank. If we change the pricing doing the option this way, is a call for disaster, because of different pricing.
Also, small business/ coorporate companies etc. mostly pay with check and most of them avoid the use of paypal at all costs even tho is secured. ACH do both Credit Cards and Checks and is a very popular and less expensive option.

Similar Messages

IBY - Payment Process Request in status Formatting

I have a problem with the payment process for a payment with processing type = PRINTED:
Steps:
I submit a Set Request, this contains the next requests
Payment Process Request Program
Scheduled Payment Selection Report
Format Payment Instructions (this will create payment instructions)
Payment Instruction Register --> but this output showed Formatted - Ready for Recording
How do I confirm a payment, only process running?
Thanks!
Carlos

Hi
Please review the note R12: Payment Process Request (PPR) Stuck In Status Formatting [ID 561048.1]
Hope this helps.
Thanks
Manish Jain.

How to automatically confirm check pay run (payment process request) in R12

Payment Method = check
The payment process profile (ppp) settings are as follows:
Processing Type=Printed
Payment Completion Point = When the Payment Instruction is Formatted
Default Payment Document= blank/null
Payment File=Send to File
My question is this. Is it possible or how do you configure oracle payments (PAYMENT PROCESS PROFILE [PPP] and/or PAYMENT PROCESS REQUEST [PPR])for check payments created as a file output like you have in 'EFT' instead of printing the checks and CONFIRM the PPR/payments AUTOMATICALLY after the checks/payments have been formatted.
The reason we are doing this is because we want an external agency to print the checks for my organisation.
What is happening at the moment is that the PPR runs and the payments file is created successfully. At this point, the PPR is in 'FORMATTED - READY FOR RECORDING' status. The PPR then remain in this status until it is manually confirmed by clicking the 'Take Action' icon in the 'payment instruction' tab and then clicking on 'CONFIRM'.
If the PPR is left in the above status, then the next submitted check pay run errors because the payment document(s) are still locked by the pay run that is in the 'Formatted - Ready for Recording' state.
If it is not possible to configure Oracle payments to auto confirm the check pay run of this type, is an API available that can be called to confirm check payments - once they are in the formatted status.
I've looked at the following notes in 'My Oracle Support', but they are not much use.
Note 1097547.1 is related to bug 8781032 which talks about "Automatic Initiate when Payment Process Request is Complete".
and then Note 1215392.1 relates to enhancement request.
Bug 10142423: GIVE AN OPTION IN PAYMENT PROCESS PROFILE TO SUBMIT POSITIVE PAY FILE AUTOMATIC
Thanks.

Try running this SQL
SELECT
r.calling_app_id,
r.created_by,
r.payment_service_request_id,
r.creation_date,
r.call_app_pay_service_req_code,
fa.application_name,
fu.user_name,
r.payment_service_request_status
FROM
iby_pay_service_requests r,
fnd_application_vl fa,
fnd_user fu
WHERE r.payment_service_request_id = <<your concurrent request ID>>
AND r.calling_app_id = fa.application_id(+)
AND r.created_by = fu.user_id(+)

Automatic Payment Process through IDOC and Receive Message Acknowledgement and BANST file format

Hi Experts,
We are implementing payment process to our client through Idoc.
Normally the process will go like below. Once Payment Initiated --> IDoc will generate --> This Idoc process through PI system and send to Bank.--> Once payment data received bank --> it will generate acknowledgement receipt and Bansta file and send it PI system --> This PI system system again send it --> SAP system. Here I want to know the required configuration from PI system to SAP system while receiving acknowledgement and Bansta file. And let me know if u guys have steps...
Thanks,
Raviram

Hi,
>is possible using the fileadapter to read this file and with pass it throug PI to IDOC receiver adapter without any mapping?
yes
>In that case what should the Message Type we are using in the file-sender adapter look like?
If you have no mapping it doesnt matter, the message type will not be validated during runtime. You can take the IDoc type imported from the SAP system
Regards,
Udo

Automatic Payment Process through Schedule Manager

Dear Experts,
I am an infant in SAP..just started my foot steps by formally taking up a sap course from siemens. I would like to get a complete configuration details for the scheduling automatic payment process. The scenario I could think of is a weekly payment run for a company code at 7.30 pm..Please help.
Thanks,
Aspirant

Hi,
In FBZP you need to do the config. for the automatic payment.
1All co codes:fill the paying co code.
2)Paying co codes :give Min and Max amount for payment and form payment advise.
3)Payment methods in country :In country creat the p.method
eg: for cheque :pay method 'c',select outgoing payments,check and give document type for paymentand under apyment medium program 'rffous_c'
4)payment methods in co code:give the same pay method (c)in your co code here and amt lmt and form for payment medium
5)bank determination:give the bank details i.e crcy,paymethod,house bank,account id,bank sub account,available amts etc.
6)house banks:give the detials of your bank account.
there will be no schedule job for f110.
Further you need to configure check lot,house banks for this.
regards

Down Payment Process in SD

Hi All,
We want to implement a down payment progress in our system. I did all of the customizing requirements in SD according to OSS Note 213526.
Furthermore, when I placed an sales order in VA01 and then invoiced in VF01(only invoiced the value in billing plan) -in other words down payment request in SD, I also used F-29 for down payment and the order number appears in that screen and then payed. But the condition AZWR did not change or update.
What is the problem in process or in configuration? In addition to this, I have also checked the configuration steps many times which are in OSS Note.
Regards.

Dear ,
I am doing the downpaymet with in milestone billing plan. i have 3 legs in the billing plan . the first one is acting as down payment
the remaining as normal which can be billed with normal billing plan right?
Billing plan Milestone
Item category TAO
billing document FAZ
Normal billing document F2
Item category group is 0005
Condition type is AZWR
This is all about my config could you please help me to do so..
With Regards
Aswin Nair

Down payment process

Hi guru's,
I am working on a downpayment process, where i created a material as per down payment process and changed required custom settings as per milestone billing process. as of business requirement 40% percent need to get advance from customer otherwise billing will not happened,
How can i enter this 40% amount in my sandbox where am creating dummy sales order cycle to test how the plan will work,
I finished till deliver , but i need bill that document , i have to show the amount where it received as advance , how can post that money received.
Please advice me.
thanks & regards
chandra sheker c

hi,
http://help.sap.com/saphelp_470/helpdata/en/14/c8af5ad21411d2acc70000e8a5bd28/frameset.htm
http://help.sap.com/saphelp_470/helpdata/en/01/a9c74e455711d182b40000e829fbfe/frameset.htm
The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
KAPIL

Down payment process for Poland, new business process or not ?

Hello,
I'm a little bit confused about implementation down payment process for Poland.
The OSS-notes 818079 and 1007635 describe a solution for this.
How do I have to implement the correct down payment process for Poland ? Do I have to create an extra business process with new sales order type, new billing type, separate calculation procedure, new output type and so on ?
Or is it possible to use existing business processes in sales and distribution for down payment processes ?
Thanks in advance
Holger

hi,
Check the process for down payment processing
The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
chandu

Down Payment Processing on the Basis: Document Condition

Hi all,
since Enhancement Pack 2 there is a new possibility of down payment process. The new process is not depending on billing plan instead depending on Document conditions.
With this you can also have the the final invoice delivery related. In the order you have just a new header condition AZWA (debit down payments).
Is there also a possibility to create for this new downpayment process a down payment request with financal bookings (similar to billing type FAZ) ?? The documentation doesn't give any information about this in the new downpayment process.?
Any experience would be nice??
Regards,
Norbert
Documentation for new downpayment process depending on document condition
http://help.sap.com/erp2005_ehp_03/helpdata/EN/ce/b7790d32554ae2abb5d2c4aa4e45d1/frameset.htm

Dear All,
Can anybody write me detailed customizing values for AZWA and AZWB condition types?
Online help is incomplete (e.g. condition class is missing, etc.) and system didn't add automatically these new condition types after business function activation.
Thanks.
Ferenc

Down Payment Processing in Milestone billing

I have created sales order that does milestone billing. The down payment is 10 % of amount - Billing type FAZ and condition type AZWR is included in Pricing Procedure and ERL is asigned.
I also have done all the required settings from the help file at:
http://help.sap.com/saphelp_47x200/helpdata/en/4a/ac853478616434e10000009b38f83b/frameset.htm.
But the sales order still says G/L account not found and not saving. Is the G/L account need to found at sales order itself ? If so, where in sales oredr type I have to assigne account determination like KOFI00 etc ? Can any explain this ?
Does the down payment in sales order do the account determination to find G/L account as in case of regeualr billing docs ?

The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
By useing tcode---> VKOA assing the G/L accounts for account deteramination

Down payment processing

Hi Friends,
Could somebody throw light on as how Down payment process is carried out in general. Provide flow for the same.
Thanks

The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)

Down payment processing error

Hi,
I am facing problems in down payment processing (ECC6.0) with and without billing plan.
What I understand about the normal flow of down payment, once order is saved then down payment request FAZ is billed with reference to the order & it should reflect on the next invoices. Is it the correct flow?
In case of down payment without billing plan, while create billing type FAZ , it gives me message item category TAD can not be billed with billing type FAZ. i am using a dien material.
Even in case of mile stone billing I am getting message only billin rule 4 or 5 can be used. So where do we assign billing rule to billing plan?
I need your valuable input. I am working on ides ecc6.0.
Regards
Suman

Hi,
the message you get is quite easy to explain: you are using doc.type DZ (should be the default doc type for transaction F-29), but you are entering a vendor line item. This is definitely a problem as doc. type DZ usually does not allow vendor lines in the document, you can check it in transaction OBA7.
Another funny thing is you are saying that you want to enter a down payment received from a customer - so why do you have a vendor line in your document? I think this is the main problem, you are just using a wrong account type. Use the customer account you have entered for the down payment request earlier.
If for seom very strange reasons, you still want to use a vendor line in the customer down payment document, then you have to use another document type that allows customer, vendor and also G/L accounts (check OBA7). However, if you are working with document splitting, you should be careful when picking a document type.
Hope that helps, points welcome
Csaba

Down payment process on basis of document conditions

I am trying to setup the down payment process that uses document conditions (available since EH2) and I'm struggling with it. I can't get any values to show in condition type AZWB. I'm wondering if anyone has any experience with this process and can suggest what I might be doing wrong. I found a link to a SAP best practice guide and setup the condition types and pricing procedure per the guide
[http://help.sap.com/bp_retail603/BBLibrary/Documentation/732_BB_ConfigGuide_EN_US.doc]
I entered a value for condition AZWA in the sales order (tried both a header value and a line item value). I then made a down payment for that amount using t-code (F-29). In F-29 I entered the special G/L indicator = A and I referenced the sales order (tried with and without a line item). When I tried to create the invoice for this item I was expecting AZWB to be populated, but instead it has zero in it. I tried working through the debugger for calc routine 49, but got lost halfway through it. However, it did look like it found a value in BSEG for the down payment amount at some point. Can anyone suggest what I might be doing wrong or what else I can look at to help analyze what's going on.
Thanks

Hi,
We are also in process to implement condition-based down paymnet but when we try to enter a down payment with F-29 and referenced the sales order number, the system gave error message u201CMessage no. V1125 - Enter the item numberu201D so we were forced to enter the payment at the line item level.
How did you able to do F-29 at the header level ?
Is there special config we are missing ?
Thanks,
Avishay

Sd down payment process

hi,
sap gurus,
Downpayment/Advance Payment Process:
an order to cash mangement is made to the customer and think he has paid some advance and that billing value is 10,000 and advance paid by him is 1,00,000/- how to configure that the customer balance with the company should be shown by deducting the 10,000/- billed amount and it should show 90,000/-.
in other words...........
Advance/Down Payment Treatment Will It Get Deducted
Automatically From The Respective Advance/Downpaymnet
Paid By The Customer.
my id is [email protected]
regards,
balaji.t
09990019711.

Dear ,
I am doing the downpaymet with in milestone billing plan. i have 3 legs in the billing plan . the first one is acting as down payment
the remaining as normal which can be billed with normal billing plan right?
Billing plan Milestone
Item category TAO
billing document FAZ
Normal billing document F2
Item category group is 0005
Condition type is AZWR
This is all about my config could you please help me to do so..
With Regards
Aswin Nair

HT5622 Pls why do I keep getting this message "Payment processing is temporarily unavailable. Please try again later.... Every time I try to purchase something ????

Payment processing is temporarily unavailable. Please try again later..... That's all I've received all day, can't even change my payment type to none

Payment processing is temporarily unavailable. Please try again later..... That's all I've received all day, can't even change my payment type to none

Other types of payments processing.

Similar Messages

Maybe you are looking for