Payment Processing Tab function in PO

Dear Friends,
In Purchase order at header payment processing tab is there.
Cab any one explain me how it works.??
can i make its use to make retention money of vendor , how we can do it??
Regards,
Mahesh.

Hi,
This is ECC 6.0 EHP4 Functionality.
Refer Following Links;
[MM, Integration Materials Management and Financial Accounting|http://help.sap.com/erp2005_ehp_04/helpdata/en/42/fbded750e61febe10000000a422035/frameset.htm]
[Down Payment and Down Payment Request|http://help.sap.com/erp2005_ehp_04/helpdata/en/fa/f6b132c23146918babf211677ac6b1/frameset.htm]
[Down Payment Clearing|http://help.sap.com/erp2005_ehp_04/helpdata/en/48/b42c22e8603095e10000000a421937/frameset.htm]
[Retention|http://help.sap.com/erp2005_ehp_04/helpdata/en/6d/5e74d1cfbb4513bb13d566bd70a15a/frameset.htmhttp://help.sap.com/erp2005_ehp_04/helpdata/en/6d/5e74d1cfbb4513bb13d566bd70a15a/frameset.htm]
[Retention Processing|http://help.sap.com/erp2005_ehp_04/helpdata/en/01/df47a55d34401c84e10923ed2b4adb/frameset.htm]

Similar Messages

Payment Processing tab in Purchase Order

Hi
can anybody help me, How do we get the Payment Processing tab which is used for Retention purpose ? Which SAP Note or package is involved in this as i am unable to find that tab? We have just installed SAP ERP ECC 6.0 EHP4. Kindly guide me.
Regards
Samuel
Edited by: samuel mendis on Sep 23, 2010 2:20 PM

un-answered

Retention field is missing on Payment Processing Tab - Purchase order

Dear Experts,
I have configured retention and also activated the switch LOG_MMFI_P2P ..Payment processing tab is now appeared in PO but Retention field is missing. Please check below screen shot.
There are many posts related to Retention config, i have already checked and but none is suitable for my problem. PLease help.
Regards,
rohit

there is a differences in Dev & QA as follows
In dev field is Retentions
In QA field is Payment retention
M i missing somethin in config?
Plz help

TAB functionality(next page) in BDC recording process?

Hi,
I am trying to record a transaction using SHDB for BDC,
in recording process I am selecting records in popup screen and that screen will be having 9 records all the time and after selecting 9 records when I press tab(for going into second page) that TAB functionality is not recording.
Can any one please let me know how I can implement TAB(going to next page in recording process)
Thanks for ur time...(waiting for valuable answers)

Hi Rich,
sorry i forgot to answer .,.
I am using BP transaction and selecting business partner and ship to address tab i am trying to add address records to ship to address tab.
P+ did not work .. its not going to next page.
thanks..

EHP 6.0 PO Vendor Down payment process

Hi All ,
our client updated , EHP 6.0 , i have one query , one function updated "LOG_ MMFI _P2P" added new tab po header level payment processing , i want to how we can do po down payment process, how we can create vendor down payment header level or item level , what is uses of TCODE me2dp. Please explain me all this process above function updated "LOG_ MMFI _P2P". previous they are using Normal process now they want to use new process which is updated in EHP6.0 . Let me new process. & how create dp po item level or header level.????
previous they are using below process .
1) ME21N PO create
2) f-47 dp request
3) f-48 dp pay
4)f-54 dp clr
5)f-53 final pay
6) F-44 vendor clear
Thanks & Regards
Jay

Hello Jay,
Kindly follow the below link
http://www.slideshare.net/subhrajyotibhattacharjee7/vendor-downpayment-process-mapping-with-new-ehp4-enhanced-functionality
I think the above will clear your requirement.
Regards,
Vinayak

Looking to configure a Late payment process within Collections

I am looking to implement a follow-on late payment process within the Collections Management process for past due invoices. Has anyone done this before and if so any considerations or challenges to the process? Basically as invoices fall in arrears the specialist would have the ability to create a debit memo request in reference to the late invoice for a percentage of the open amount. This would be within the Process Receivables tab. It would go through an approval process and as approved would become a debit memo for the "late payment" with reference to the debit memo request.
Any thoughts?

I would look at what you can achieve in the standard FI-AR Interest process.
I dont believe there is functionality in Collections Management for this. One of the main processes is to not update FI-AR from Collections Management.
You do have the ability to add function buttons into Collections Management (Process receivables) after Enhancement Package 5

Open item management_part payment with partial clearing_post outgoing payment process open items

In this scenario of post outgoing payment process open items , i' m facing a error titled as below
The difference is too large for clearing
Message no. F5263
Diagnosis
A non-assigned difference exists for the specified clearing amount.
The difference for an automatic difference posting must not be greater than the difference permitted for the user, nor greater than the difference permitted for the tolerance group that is contained in the customer/vendor master record.
System Response
It is not possible to automatically charge off the difference.
Procedure
You can charge off the difference manually using the function "Clear differences". You define the upper limits for automatically clearing differences in the tolerance group assigned to the user.
Change tolerance groups for user
I gave the specifications in (OBA4 screen) i.e., change tolerance groups for users/employees are as follows
Amount per document : 9999999999
Amount per open item account item : 9999999999
Cash discount per line item : 10%
Permitted payment differences left blank
What else do i need to execute ?
Please aid me in resolving the error....
Thanks in advance,
Heamanthkkumar.

Hi,
it seems you want to make a partial payment of 15000, select the line item against which you want to make the payment. On the payment amount field put -15000 and then simulate. It will credit the bank account and debit you expense account. Pls refer the screen shot.
best regds
Subha

R12 Payment Process Request only picking up 1 Credit Note per supplier

I am using R12 v 12.1 and have found an issue when I create a Payment Process Request that includes multiple credit notes for a supplier. When I create the batch only 1 credit note is selected. When I attempt to manuallly add another credit note it adds it to the batch however when I confirm the payment batch only 1 credit note is applied The nett amount for the supplier is still positive so I am unable to determine why this issue is occuring. Can anyone tell me if there is a setting to allow multiple credit notes within a payment process batch for a supplier?
I have found something but am not sure if this is the solution. Under the 'Process Automation' tab when I create a PPR template I have noticed an option called 'Maximize Credits'. If this check box is selected will it allow multiple credit notes for 1 supplier to be added to a payment batch or is this option used for something different?
Can someone please help with my issue.
Thanks

Yes, you are correct.
You have to select the option "Maximize Credits" that will select all the available credit notes for the supplier while processing the PPR.
Thanks
Manish

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(+)

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 for Sales orders using Milestone Billing Plan

Hi,
The business scenario is as follows.
The delivery for the sales orders are to be created only after the pre payment( a percentage of the total sales order value) is made by the customer.
Hence the sales orders while creation are blocked for delivery creation using credit block by means of a userexit.
The credit manager checks the blocked sales orders using VKM1 transaction and verify if there are any payments made by the customer to cover this pre payment to be made.
If it is enough to cover then he releases the sales order manually for delivery creation.This is a complex process since there are too many sales orders and the payments made by the customer may not match the amount to be paid(it can be greater or lesser).The customer just pays a huge amount which is to be distributed among the sales orders for pre payments.
Later, when the invoice is created, the customer account is cleared manually using F-32 transaction for the oldest open invoices.
Here again there is a huge manual effort involved since he need to distribute the amount against the invoices using oldest open item principle.
As a solution we are planning to implement "Down Payment processing for Sales orders using Milestone Billing Plan".
Is this the right solution?
Can you please give the steps in detail to implement this functionality for above scenario?
We are using SAP 4.7 version without Project Systems.
Thanks in advance.
Regards,
Ragesh

Hi Ragesh
Check the links where you will get the entire down-payment configuration
[https://forums.sdn.sap.com/post!replydownpayments ]
Regards
Srinath

Payment Processing Tab function in PO

Similar Messages

Maybe you are looking for