How to do advance payment against PO for this is there any T.code

[Former Member]

Hello,

Lt's say for ex: Once Po is created how to pay the advance payment against PO to the vendor, for that is there any transaction code.

Once advance payment is made against PO, again system should not allow for ammendement

So like this to control the system what are the configuration settings need to be done please explain

Early action in this matter will be highly appreciated.

[Former Member · Accepted solution]

hi,

Just follow the below mention link for the complete process in details.

http://help.sap.com/saphelp_ides/helpdata/en/6e/12180a9f0411d189b80000e829fbbd/content.htm

now for the amendment part you can easily check with the use a user exit and check EKBE Po history table

and check if VGABE= 4 ( transaction event type =down payment) not modifiable

[Former Member]

Hi SAPMM69,

Below are the prerequisites for prepayment:

- In customizing, the prepayment must be allowed for each company code.

IMG->MM->LIV->Incoming Invoice->Prepayments->Configure Control of Prepayment at Co. Code Level.

- Prepayment must be permitted in the vendor master record with the prepayment indicator.

- There must be general ledger account defined for transaction PPX (prepayment) in customizing for the account determination.

To create an invoice with prepayments, you must enter the invoice with transaction MIR7 or MIRA.

Before you introduce prepayments, you must read the extra information from:

http://help.sap.com/saphelp_erp60_sp/helpdata/en/a8/b99f58452b11d189430000e829fbbd/frameset.htm

Also, read SAP Note# 937129 and 958136.

Hope this helps!!

Reetesh

[Former Member]

For advance payment against vendor use T Code F-47 (Down Payment Request)

Fill details Like : Document Type, Currency ,Account (Vendor Code) ,Trg.sp.G/L ind. (A)

Enter

Amount

put PO Number in Pur Doc field

Save

given payment by T code f-48 with refernce to F-47 document number

Regards,

Dishant

[Former Member]

Post these data by Tcode F-48 and Purch. Doc. Field in the Post Vendor Down Payment Add Vendor Item Screen You can Enter PO no. along with Item. If Po No. is not showing then You have Add Purch. Doc. Field in Screen layout.. it required some config changes.

[Former Member]

Now what I want to protect the system is once advance payment made against PO, system should not allow to ammend the PO.

At present in my system though there was an advance payment system has been allowed for ammendment of PO, what could be the reasion for this system to allow for ammendment?

So please explain the configuration settings need to be done.

Edited by: sapmm99 on Nov 24, 2011 8:34 AM

[BijayKumarBarik]

Hi,

You are paying advance payment to vendor but not mentioned how you are paying!

You need to explain details process for advance payment.

If you are following:

PO creation> PO release > advance payment, then you can use Changeability Indicator 1 in Release Indicator in designing of Release Procedure for PO, so once PO released, you can can not do any changes to that PO.

If you are following:

PO creation--> advance payment, then you can think of going for enhancement.

But you can 1st establish the process advance payment

Regards,

Biju K

[Former Member]

Hello Biju,

If you have any idea,can you please tell me the suitable user exit for PO.

Actually in my process there is no release strategy for PO,only we are having release strategy for PR.

So once PO is created and saved it should not allow for change or ammendement.

Thanks in advance.

[Former Member]

Hi,

Apply the user exit : EXIT_SAPMM06E_016

Following Logic can be use:

1. Validate the company code (BUKRS ) & Purchasing document type (BSTYP = F) from EKKO table for the Purchase order number (EBELN).

2. Check the entries for the Purchase order and the item number in the Purchase order history table ( EKBE) and also Validate if there is any down payment document exists (VGABE = 4)

3. If we find down payment doc in EKBE table then display the warning or error message as POP - UP by using functional module POPUP_TO_CONFIRM.

Step 1: Validate Company code and Purchasing Document type from EKKO table

Step 2: Check the Purchasing document history from EKBE table

Step 3: Check whether any down payment exists.

Step 4: Display popup message to user:

Use the function module u201CPOPUP_TO_CONFIRMu201D to display the below message u201CPo cannot be changed, Down payment already exists for this PO item u201D.

Edited by: redriver on Nov 27, 2011 10:06 AM