Liquidity forecast - purchase order payment terms

Dear Experts, I have the following issue,
We are using liquidity forecast, but we are having a problem because the system does not take into account when a Purchase Order is created with Installment Payment Conditions. The Liquidity Forecast shows the Planning Date equal to Delivery Date of the Purchase Order, not taking into account the division of the payment term and the days of delay of every partial payment. I would like to know if there is workaround for this issue.
Best regards.

Hi Cristobal,
The splitting of payment commitmentment accrding to the instalment dates are not possible. However it is possible to have the first instalment payment date instead of delivery date. But for this the Payment Term definition should take the baseline date as any of the 3 defaults possible ( Doc date/Posting date/Entry date). That means it should not be "No Default".
Below reproduction from note 497381:
"In the installment payment terms, you can enter 'Fixed day' and 'Additional months' for the calculation of a baseline date. In this case, the system updates the entire payment commitment as at the calculated baseline date (fixed day and additional months)."
Please try this and also share your results with us
Shony

Similar Messages

Liquidity Forecast not considering payment term / due date

I have configured liquidity forecast and it is picking up values just fine (ECC 6.0).
My problem is that in FF7B it is not taking "Payment Term" and "Due Date" in to consideration at all. Thus as a result not showing what is due on which date.
What do I need to do to ensure that FF7B (liquidity forecast report) show balances considering "Payment Term" and "Due Date"?
Or is here some functionality missing, or I am facing a program error?
Regards

Hi,
You do not have to give the Days there.
Their functionality is different.
Assign 15 in Payment terms Tab in No of Days, Percentage should be blank.
Then the system will calculate the net due date 15 days from Document Date.

Purchase Order Payment terms

Hi all,
I have a requirement of adding description of Payment terms in the sapscript . Earlier the script only prints terms without description. It use to get the value from , &'Terms of payment: 'PEKKO-ZBTXT& in the sap script MEDRUCK.
Now i added table T052u in the print program to get the description of payment term, the field is T052U-TEXT1.
While creating payment term from tcode OBB8,Eg: Payment term is Z001 and we enter No of days and percentage . Suppose i enter 10 days , how is the script printing as "Within 10 days due net ".
I want to know where this field is stored, Pekko is a structure so iam not able to see this.
Please do tell me which table do i get to see this payment term w.r.t to PO
Waiting for ur Reply's
Regards,
Shuja

Check table :T052U
Hope thisll give you idea
P.S award the points.
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

Need a BADI for Manipulating Purchase Order Payment Terms?

Anybody know of one? We are on 4.6C....Thank-You.

Hello Sudheer,
This would be great only I do not see "Call method cl_exithandler=>get_class_name_by_interface " to put a break point in the GET_INSTANCE Code....below. Also, I only see one Method in cl_exithandler and it is GET_INSTANCE. I would really like to do what you say but can't figure out where to pit the breakpoint........Thank-You
METHOD get_instance.
CLASS cl_abap_typedescr DEFINITION LOAD.
DATA: exit TYPE REF TO object,
        temp TYPE abap_abstypename,
        int_ref TYPE REF TO cl_abap_refdescr,
        type_ref TYPE REF TO cl_abap_typedescr,
        interface TYPE seoitfname,
        exit_name TYPE exit_def,
        clskey TYPE seoclskey,
        mult TYPE seex_boolean,
        subrc LIKE sy-subrc,
        abs_type_classname TYPE string.
The absolte type name of the changing parameter instance
is got via dynamic describe
CALL METHOD cl_abap_typedescr=>describe_by_data
         EXPORTING
                   p_data       = instance
         RECEIVING
                   p_descr_ref = type_ref.
IF type_ref->type_kind NE type_ref->typekind_oref.
    RAISE no_reference.
ENDIF.
CATCH SYSTEM-EXCEPTIONS others = 1.
    int_ref ?= type_ref.
ENDCATCH.
IF sy-subrc = 1.
    RAISE no_reference.
ENDIF.
CALL METHOD int_ref->get_referenced_type
        RECEIVING
            p_descr_ref = type_ref.
IF type_ref->type_kind NE type_ref->typekind_intf OR
     type_ref->absolute_name NS '\INTERFACE='.
    RAISE no_interface_reference.
ENDIF.
Get the interface name by the absolute type name
SPLIT type_ref->absolute_name AT '=' INTO temp interface.
Get the exit_name for the interface name
SELECT exit_name FROM sxs_inter INTO exit_name
           WHERE inter_name = interface.
    EXIT.
ENDSELECT.
IF sy-subrc = 4.
    RAISE data_incons_in_exit_managem.
ENDIF.
Get the name of the exit class
CALL FUNCTION 'SXV_GET_CLIF_BY_NAME'
       EXPORTING
            name   = exit_name
            prefix = seex_exit_class_prefix
       IMPORTING
            clif   = clskey-clsname.
CONCATENATE '\CLASS=' clskey-clsname INTO abs_type_classname.
Is the given instance initial?
IF NOT instance IS INITIAL.
    CALL METHOD cl_abap_typedescr=>describe_by_object_ref
           EXPORTING
                     p_object_ref = instance
           RECEIVING
                     p_descr_ref = type_ref.
    CHECK type_ref->absolute_name NE abs_type_classname.
ENDIF.
check how many implementations exist for an exit
CALL FUNCTION 'SXC_ACT_IMPS_PER_FLT_VAL'
       EXPORTING
            exit_name                = exit_name
       EXCEPTIONS
            multiply_active          = 1
            no_active_implementation = 2
            OTHERS                   = 3.
subrc = sy-subrc.
IF subrc = 1.
there are more than one active implementations
read the properties of the exit
    SELECT SINGLE mltp_use FROM sxs_attr INTO mult
                  WHERE exit_name = exit_name.
    IF sy-subrc = 4.
      RAISE data_incons_in_exit_managem.
    ELSEIF mult = seex_false.          " singular exit
      RAISE single_exit_multiply_active.
    ENDIF.
ENDIF.
act_imp_existing
IF subrc = 2.
    act_imp_existing = seex_false.
ELSE.
    act_imp_existing = seex_true.
ENDIF.
ok, then do your job
CREATE OBJECT exit TYPE (abs_type_classname).
CATCH SYSTEM-EXCEPTIONS move_cast_error = 1.
    instance ?= exit.
ENDCATCH.
IF sy-subrc = 1.
    RAISE cast_error.
ENDIF.

Purchase organization - Payment terms

Hi,
In our earlier system, there were separate purchasing organization (for a country) for each company code so if the same vendor is used for both the purchase organization; we were able to define different payment terms and accordingly default in Purchase order.
Now in the new system, there is only one purchasing organization (for a country) for each company code. We can define separate payment terms in company code data for the same vendor but only one payment terms in purchasing view.
Now the issue is how to default payment terms in purchase order, one option is to use BADI ME_PROCESS_PO_CUST so that the payment terms in purchase order will come from the accounting view of the vendor.
Please let me know if anybody has faced the same issue and how to resolve it.
Regards,
AG

in Vendor subrange a different payment term is possible. If you have 2 payment terms, pl see whether the issue can be solved using 2 different subranges and calling the relavent subrange in the PO

Purchase Order Payment Details.

Please tell from where i can get the Purchase Order wise Payment Details.
I tried using FBL1N but PO Number is not coming.
Further after simulating the Payment Document the reference is coming of original Financial Document in "Payment For field".
posted during the MIRO.
Please tell the required tables to join for getting the same or if standard is there then please tell the T-Code

Hi,
You can do the following.
Process : 1
Maintain sort key 014 for your reconciliation account. So this key will capture the purchase order number and throws the value to assignment field. You can add assignment field for a layout in fb1n and can see the p.o. details.
Process : 2
Check for special fields in FBL1N report using the following way.
Inside of the report Settings--->Special Fields. There you have tables and fields, you can add those however you want.
Rgds
Murali. N

Sales Order 'Payment Terms' conversion error after 8.8 Upgrade

Hello All,
We recently upgraded from 2007A PL49 to 8.8.
The Installation went smooth, until we opened up our first new Sales Order. We are getting the SQL error listed below each time we open up the sales order module. This doesnt prevent us from adding a new Sales Order, but the fact that it throws the error each time we open the module is scary.
Any ideas as to what might have changed from PL49 to cause this?
Error:
1). [Microsoft][SQL Native Client][SQL Server]Error converting data type nvarchar to numeric.
'Payment Terms' (OCTG)
Thanks,
Matt

Hi,
Can you check wether there is any formatted search involved in the Sales Order?
You can also check Note No. : 1402855. Check if it helps.
Kind Regards,
Jitin
SAP Business One Forum Team

Different field mode(display/change) in sales order payment terms (VA02)

Hello All,
In the VA02 transaction, when we are changing the sales orders, in the billing document of that material shows different modes for different fields.
VA02->DOUBLE CLICK ON THE MATERIAL->BILLING DOCUMENT->FIELD PAYMENT TERMS.
For some orders, field is in display mode and for some orders, it is in changeable mode.
Could anyone please let me know about this..?
thanks and regards,
MERVIN

Dear Jignesh
As you would be aware Payment Terms will flow in SO both at header level and at item level.
So in order to control the item level changes, go to VOV7, select the item category and untick the box [Business Item] By doing so, whatever header level datas flows into SO, that will be copied to item level also and you will be controlling the changes at item level and end users cannot make changes at item level.
Now you have to control at header level for which you have to apply User exits in the program MV45AFZZ - USEREXIT_MOVE_FIELD_TO_VBAK
thanks
G. Lakshmipathi

Block sales order - payment terms

Hi Experts,
have a scenario, where we have to block the sales order if the payment terms has exceeded w.r.t to individual division. say for eg: customer "A" sales area 1000/10/01 - payment term - immediate
sales area 1000/10/02 - payment term - within 30 days. have maintained diff payment terms sales area wise in customer master. but still sales order is created without block. have defined credit limit as well and clicked on "blocked" as well. Pls help this on priority.
Rgds,
Anitha J

Hi friends,
got the answer after lot of R&D. in the configuration, automatic credit control, if critical fields is checkd, then it allows to create the sales order and delivery, but doesn't allow to do PGI, which is what is required. so customer cannot receive goods in future, once its blocked.
thanks everybody and spl thanks to hans as he is the only person to respond. Thanks a lot!!!!!!!!!!
Rgds,
Anitha J
closing the thread

Sales order Payment term modify Userexit

Hi Experts,
I am working on sales order VBKD modify userexit, in this based on customer, customer group & one maintained z field from MARA they created Ztable to pick Payment term.
For line item which doesn't have payment term (KONP-ZTERM) at condition record (XKOMV), I have to pick from Ztable & update header payment term (line item 000000).
This was working fine but problem arise for couple of material, inside userexit when line item is coming XKOMV is not filled inside userexit. when this should possible?
Points will be rewarded.
Thanks,

When the payment term is changed in the Sales Order level it DOES NOT change the BP's default payment terms.
Ans 2: only for the present Order
Ans 4: The payment term setting at the order level is only for exception where someone authorized can change it at the order level. If you prefer not to let the user change the payment term at the Sales Order level then you can manage this through Authorizations
Nothing at the document level will change the MASTER. Only changes made at the Master level are permanent from that point on.

Sales Order - Payment Terms

Hi All:
When the Sales Order is created with reference to the quote, the payment terms should be determined and defaulted from the Customer master and not from the quote.
They have changed the Customer Master Payment terms in the mean time.If i create a Sale Order w.r.t Quotation the older Payment terms comes from the Quote. But they need to take a new payment terms from the customer master(KNVV-ZTERM).
i have found that one BADI: BADI_SD_V46H0001
Package: VA
But it did not work.since it is not checked as " Multiple Use " and it has already an implementation .
And the I have also found a Enhancement: V46H0001
Package: VA
We have also verified this Enhancement which contains two Exitu2019s 1. EXIT_SAPLV46H_001
2. EXIT_SAPLV46H_002
These Exits are not triggering when we create the sales document with respect to Quotation.
Please throw some light on it...
Thanks,
Venky

Hi,
When the Sales Order is created with reference to the quote, the payment terms should be determined and defaulted from the Customer master and not from the quote.
I guess the Customer numbers on the Quotation and the Sales order would be the same while creating the SO with ref to Quotation ? So the data will be picked up appropriately.
regards,
Advait

Payment terms in Vendor Master data and purchasing info record

Hi, all, I met one trouble. While I create Purchase Order. In the header item, payment terms is automatically pop up from the data maintaining the vendor master data or purchasing info record if there is difference payment terms between in vendor master data and in purchasing info record. What happend?
Sometimes, When you create purchase order, payment terms is not automatically pop up even you maintained in the vendor master data or purchasing info record. Why? Is it meaning that I can manually to input payment terms while create each purchase order which can be difference data with vendor master data or purchase info record?
Thank you very much in advance,

Hi,
The payment terms is usually defaulted from either vendor master or purchasing master data record such as contract/outline agreement. Unless it is set through configuration that the payment terms be set as mandatory, any failure to maintain payment terms won't stop you from posting your PO as this information will only be useful during invoice receipt maintenance. Having said that if you are setting up your system with discount condition type as part of your PO pricing schema then it is necessary that the payment terms shall be maintained during PO creation.
Cheers,
HT

How to get PO and vendor payment term number of days??

Hi Experts,
I want to have a) Purchase order payment term number of days as well as
b) vendor Payment term number of days.
For a) For Purchase order payment term number of days I am using table EKKO and taking ZBD1T field which is giving payment
           term number of days.
          Is it correct??
      b) vendor Payment term number of days I am using table LFB1 field Zterm to take payment term key not number of days.
           Based on this key i will go to table T052 and find corresponding number of days as told MM consultants .
           But this is not BW work. We need one single table from which we can take the field or enhance the current extractor
          with that field.
So is there any other option for (b)
and Whether steps for (a) is correct???
Please confirm this.
Thanks in Advance,
Uday Shankar.

For a) For Purchase order payment term number of days I am using table EKKO and taking ZBD1T field which is giving payment
term number of days.
Is it correct??
Payment terms for purchasing doesn't come delivered as part of the R3/ECC tables and is usually is added as a custom field to EKKO and populated via a User Exit. That looks to be the instance in your case because the field that you show as being the payment terms begins with a Z (custom fields begin with Y or Z). That appears, without being able to actually validate in your R3/ECC environment, to be the correct field to use. You would have to validate, however, with the end customer or your MM function consultant to be 100% certain. If this is the correct one to use, you're going to have to enhance the 2LIS_02_HDR extractor by enhancing the extraction structure and creating the User Exit to read it from EKKO and populate into the DataSource.
b) vendor Payment term number of days I am using table LFB1 field Zterm to take payment term key not number of days.
Based on this key i will go to table T052 and find corresponding number of days as told MM consultants .
But this is not BW work. We need one single table from which we can take the field or enhance the current extractor
with that field.
You can enhance the 2LIS_02_HDR extractor with the Vendor Payment Terms by joining the following in your User Exit:
EKKO-LIFNR = LFB1-LIFNR
EKKO-BUKRS = LFB1-BUKRS
LFB1-ZTERM = T052-ZTERM
This could either be done in a SELECT statement in the User Exit to do this equi join, or you could create a view on your R3/ECC environment and SELECT from that view.

Payment terms of the credit memo

Hi
When I create a normal credit memo, the credit memo payment terms are derived while when I create a credit memo against an MIRO document, the purchase order payment terms are derived. But even for the credit memo created via MIRO we want the credit memo payment terms to be derived. Is there any way we can set this up.
Request your help please.
Thanks
Lavanya

Dear Lavanya,
the system design reports the following two cases::
-With reference to purchase order
The system always proposes the terms of payment from the first purchase
order so that they can be changed in case of goods/service
With only delivery cost items, the terms of payment key is automatically
copied from the vendor master record.
-Without reference to purchase order
If the terms of payment key does not contain any value, this is copied
from the accounting view of the vendor master record.
Depending on whether you first create a purchase order with order
reference or first create an item without order reference, the terms of
payment are determined either from the purchase order or from the vendor
master record in accordance with logic described above.
I am afraid there is no other functionality avalible for defaulting the
terms of payment.
Can you please review SAP Note 322430 with regards to the payment
terms.
I hope this helps.
mauri

Payment Terms in sales order - urgent

Hi all,
while creating a sales order, payment term 'z204' is not appearing in payment terms drop down but this payment term has been defined in SPRO . Also finance ppl has created FD document in vx11n with this payment term.
Kindly tell me that why this payment term is not appearing in sales order.
Regards,
Aisha Ishrat
ICI Pakistan Ltd.

Hi,
please check wether you maintained the payment terms in cust master company code and sales area data sections, if you maintain there properly system copies it into the sales order.
please reward the points if its helped you
Ganesh

Liquidity forecast - purchase order payment terms

Similar Messages

Maybe you are looking for