Problems : Payment conditions replication

Hi,
I have problem in business agreement and account contract replication between SAP CRM and SAP ISU.
When I replicate a business agreement from CRM to ISU, it's (almost) OK, but terms of payment is not the same between CRM and ISU.
When replicate a account contract from ISU to CRM, I obtain the following error (with transaction code SMW01 in SAP CRM) : "Enter the payment conditions" (Message no. CRM_BUPA_FRG0130222).
Thanks for your help !
Best regards,
Rémi

Hi Denis,
Thanks for your help !
I applicate the note 1420329 but problems persist.
I don't have any ideas to resolve my problem.
Best regards,
Rémi

Similar Messages

Vendor payment terms replication

Hi,
Vendor payment terms are not getting replicated to SRM 4.0 from ECC 5.0.We have batch jobs running for vendor replication ( new and update).When i change the payment terms in ECC , it is not coming to SRM.I checked in Manage BPs.
Thanks for suggesting any report / tables where i can find number of vendors that are different in both the systems and replication process. ( As i am unable to use the t code BBPGETVD, BBPUPDVD in easyaccess)
Thanks a lot.

Hi pramod,
OK. I got it.
SAP Note 1104581 -No logical system in customizing view
BBPV_PTERM_LOCAL
Symptom
You have transported local payment term Customizing (view BBPV_PTERM_LOCAL)
from your SRM development system to a productive system.
The transported payment terms cannot be selected for local purchase orders
and are not visible in Customizing step "Supplier Relationship Management >
SRM Server > Cross-Application Basic Settings > Create Payment Conditions".
More TermsZTERM, pay, BBP_POC, payment tab, terms of payment
Cause and Prerequisites
Local payment terms must have the local logical system ID in the
corresponding fields of tables BBP_PAYTERM and BBP_PAYTERM_TEXT.
Solution
Please implement this note or the relevant Support Package.
You can then use report BBPCU_PAYTERM_CONV to change the logical system of
the transported entries to the local SRM logical system.
In the single selection parameter, enter the logical system of the
transported entries.
An error will be generated if the entered logical system exists in table
BBP_BACKEND_DEST.
If an entry already exists with the same key (apart from logical system
name) as the tranported entry, no conversion will take place.
The keys of the converted payment terms and their texts will be listed
after executing the program.
The keys of the payment terms that cannot be converted will also be lsited.
table BBP_PAYTERM or BBP_PAYTERM_TEXT.
BBPM_BUT_FRG0061
Payment conditions
i will also check and come back to you.
regards
muthu

Problem in Material replications

Hi friends,
I am having a problem on Material replication from R/3 to EBP. I had configured all the required settings in EBP as well as in R/3. Whenever we are starting initial loading R3AS I am getting outbound queues in EBP instead of R/3. I am getting the error like 'The current application triggered a termination'. I could able to replicate Vendor and Locations from R/3 to EBP. If anybody can solve this problem.
Thanx in advance.
SAIRAM.ALLU

Hi,
If u define your condition type is manual and if you do any changes in quantity of order in change mode then manual condition will not be determined automatically. Again u have to enter it manually and then save it in change mode itself..
Regards
sankar

Business agreement - Edit payment conditions in Customizing

Hi Guys,
I am getting below error when i am trying to create business agreement from CRM IC.
Error - Edit payment conditions in Customizing
I have completed all the required setting in CRM as well as in ISU for business agreement creation as well as replication.
Can someone suggest some solution
Thanks,
Nitin

Hello,
If you create a business agreement in IC WC you have to maintain the
customizing "Creation of Business Agreement"
But it may be the case that you maintained only payment relevant
parameters for customizing node
"Allocate Payment-Relevant Parameters to New Business Agreements"
for payment type "By Automatic Debit". In your case payment type
"By Invoice" may be needed and may not be maintained.
Please add this in customizing via the path: Master Data ->
Business Partner -> Business Agreement -> Creation of Business
Agreement.
Please also make sure you use a BP with role "Sold to Party" when
creating business agreements, as this is needed.
OR
See
Master Data -> Business Partner -> Business Agreement -> Creation of
Business Agreement -> Allocate Payment-Relevant Parameters to New
Business Agreement
In this customizing table check the country is maintained
I hope this information is helpful.
Regards
Olivia

Transaction F110 and Payment Conditions

Hello
I´ve a problem when i´m executing transaction F110.
I´ve one vendor that in master data has the payment condition ( LFB1-ZTERM) = Z022
Z022 = 2% discount at 30 Days.
I´ve two invoices that i want to pay using transaction F110.
These invoices has the document date 26.04.2009.
In transaction F110 the post date is 06.06.2009. (More than 30 days )
When i will see the payment proposal the system gave me the information that will made the discount of 2%.
I don´t understand why this happened because the 30 days of the payment conditions has gone and the system should not take into account the discount.
Does anyone know why this happen???
Thanks and regards
João Simões

Hi,
Please see the config in TCode OBVU. Check if you have this setting.
Vendor Payments Always with Maximum Cash Discount
    Means that the maximum cash discount is always to be deducted when
    automatically paying vendor invoices.
Use
    Cash discount is also deducted if the payment is made after the
    predefined period.
Regards,
Sanjay

F110 Auto. payment program ..Problem payment method not found

Hi,
I done the configuration for automatic payment program.with payment method c.
when i am running the program the proposal is created but it is with a error saying no valid payment method found.
Please guide me.
Thanks
Micheal

I had given the payment method C in vendor master,Payment methods in country and payment methods in company code,Bank determination in FBZP.
I am getting the same problem.Payment method not found.Please find the error list
Information re. vendor 1900107 / customer / paying company code 100 ...
Payment with currency USD, payment method C: No valid payment procedure
Information re. vendor 1900107 / paying company code 100 ...
... payment not possible because of reported error
End of log
Job finished
Thanks and best regads
Micheal

Advance payment Condition in PO

Dear all,
Could any body say,is there any provision to mention Advance payment condition in Purchase Order.Please advise at the earliest possible.For suitable answer points would be assigned.
Regards,
NSB

Hello NSB,
The invoicing plan is a facility that allows you to schedule desired invoicing dates for planned procurements independently of the receipt of the relevant goods or performance of the relevant services. It lists the dates on which you wish to create and then pay the invoices in question.
You do not wait each time for the vendor to submit an invoice for goods supplied or services performed, but can have invoices created automatically by the system on the basis of the data available in the purchase order and then release them for payment to the vendor.
Integration: When you save the invoicing plan, data is passed on to purchase order commitments, and to Cash Management and Forecast.
Prerequisites: To be able to work with invoicing plans:
You must maintain certain settings in Customizing for Purchasing under Purchase Order à Invoicing Plan, such as the following:
Invoicing plan type
Date categories
Date descriptions
Date proposals
The PO item must have account assignment
You must use Logistics Invoice Verification
If you wish to use automatic settlement for periodic invoicing plans, automatic invoice creation must be agreed with your vendor. Eval. receipt sett. delivery must be selected in the vendor master record.
SAP recommends working with the order type FO (framework order).
An extended validity period and a "reason for cancellation" are defined in the header of this type of purchase order. The specified validity period is adopted for the invoicing plan.
If you work with standard purchase orders, you must maintain the date determination rules accordingly in Customizing, since there is no predefined validity period that can be adopted in the invoicing plan.
Features: The following two types of invoicing plan are available:
Periodic invoicing plan
Partial invoicing plan
Periodic Invoicing Plan
The periodic invoicing plan can be used for regularly recurring procurement transactions (e.g. rental, leasing, or subscriptions).
It facilitates the largely automatic creation and payment of invoices within the framework of the invoice verification process. The periodic invoicing plan uses evaluated receipt settlement (ERS) program functionality.
In the case of the periodic invoicing plan, the total value of the PO item is invoiced on each due date.
Example- A monthly sum of $600 is charged for a leased car (represented by an item of a PO). This sum is invoiced and paid on the last day but one of each month.
In Customizing for Purchasing, you can define whether the dates are to be maintained manually or whether the system is to suggest invoicing dates according to the specified rules.
Partial Invoicing Plan: The partial invoicing plan can be used for the invoicing of high-cost material or projects involving the procurement of external services that are to be subject to stage payments (such as plant construction projects, or the invoicing of individual stages of a building project following completion in each case).You can also flag due dates in a partial invoicing plan as dates for advance payments.
The amounts corresponding to these dates are then not taken into account in the sum total of the invoice items because advance payments are set off against later invoices. In the case of the partial invoicing plan, the total value of the PO item is broken down and spread over the individual dates of the invoicing plan.
A purchase order item relates to building project no. 1 with a total value of $900,000. 33.3% ($300,000) of the total value is due to be invoiced and paid on completion of the first phase of construction, a further 33.3% ($300,000) on completion of the second phase, and the rest ($300,000) following completion and acceptance of the 3rd and final phase.
In the partial invoicing plan, you wish to maintain the invoicing dates agreed with the vendor yourself. Therefore there is no system support in the form of date proposals.
However, if you wish to have due dates suggested by the system as an entry aid, you can reference an existing plan when creating a new invoicing plan. Date proposals can then be adopted from the former.
Hope this helps. pelase assign points...
Rgds
manish

Problem on Material Replication from R/3 to EBP

Hi friends,
I am having a problem on Material replication from R/3 to EBP. I had configured all the required settings in EBP as well as in R/3. Whenever we are starting initial loading R3AS I am getting outbound queues in EBP instead of R/3. I am getting the error like 'The current application triggered a termination'. I could able to replicate Vendor and Locations from R/3 to EBP. If anybody can solve this problem.
Thanx in advance.
Raj

Hi Ahmed,
Could you please elaborate. I am getting runtime error as 'Message_Type_X' (The current application triggered as termination with a short dump).
Thanks
Raj

Payment condition table for vendor

Hi,
where I can find payment condition tables for vendors ?
Regards

hi
There is no such thing as you have asked, but if it is terms of payment related just check the below
link.[Re: Table for Payment Terms]
Regards
Edited by: samuel mendis on Jun 8, 2010 3:11 PM

Recording of the payment condition in the table RBKP

They would know how to say because in the moment in that are making IV (invoice verification) the payment condition is not recorded in the table RBKP. In the table we have the field even so nothing is not recorded.
Tanks
Joubert Carvalho

Please check the following NOTEs.
NOTE 432332 MIR4 - Field ZTERM is not filled
NOTE 613761 MIR4:Payment conditions are not displayed
NOTE 322430 MIRO: Proposal logic for terms of payment
Best regards,
Makoto

Down payment condition type (azwr)

Hi guys,
Can you please help me how to configure AZWR (down payment) condition types. how we can raise milestone billing. please let me know.

Hi,
Pls go through the following path:
SPRO>Sales and Distribution>Pricing-->Define and assign pricing procedures.
Assign document pricing procedures to billing types.Check the document pricing procedure assigned for your document type.
Next goto "Define Pricing Procedure Determination".
Check the pricing procedure.
Goto "Maintain pricing procedures".
Select that pricing procedure.
Click on "Control data".
Before this make sure that this condiiton type is defined using "V/06" T.Code.
Add your condition type here in this pricing procedure.
Save the entry.
If you check this in your document,it will be appeared.
Coming to billing of "milestone billing" of billing paln item,just bill each item one by one in the billing plan item.
Goto Order item details.Goto Billing plan.
Maintain the billing block for other items except the one for which you want to bill.
Bill that item using VF01 T.Code.
Regards,
Krishna.

FI: Payment condition calculating 2 due-dates depending on document-date

Hello community!
I'm searching for a definiton of a FI-payment-condition which is calculating two different due-dates depending on document-date.
E.g.:
Invoices dated from 01.03.08 till 09.03.08 should be paid on 10.04.08.
Invoices dated from 10.03.08 till 31.03.08 should be paid on 10.05.08.
Or must this be realized by a FI-substitution???
Thanks for an answer.
Kind regards,
Bernd

Hello,
You didnot mention if u need posting date as base or document date. However your scenario, below is
the answer for your query is
1. Create one customised payment term only eg. XXX
    for first scenario,
   Day limit is 9 ;
   under payment terms tab , fixed date 10, Addl month 1
   for second scenario
   in the same payment term XXX
   Day limit is 31,
   under payment terms tab , fixed date 10, addl month 2.
Explanation.
as day limit is 9, what ever the dates of transaction between 1-9 it picks first setting
and after 9th until 31st it picks second setting.
I hope this clarifies you.
Thanks
G.Bharathi

Pick and pack with different payment condition in orders

Hello,
we have different orders for a customer with different payment condition.
Pick and pack joins the two orders into one single delivery, the result is an invoice with wrong payment condition applied.
Is there any way to generate two delivery documents as it happen when shipping address is different?
Thanks for your help
Stefano

Hi Stefano,
within the P&P it is not possible to distinguish between the payment terms of the sales order. The only way to guarantee that a separate delivery is automatically created for a particular sales order is to modify the ship-to address. You might consider this as a workaround.
Alternatively, you could use the 'Priority' to indicate a non-standard payment term & thus alert the P&P operator. This would however depend on the judgement of the operator to execute.
All the best,
Kerstin

Change the vendor payment condition in mass upload

hi
i need to change the vendor payment condition in mass upload
how to change (mass uplaod)
plz give your early reply
K.Raghuram

Hi,
Ask your abaper to write one BDC program to chnage payment condition.
With Regards,
Jaheer.

Problems in Contract Replication SRM

Hi Experts,
I need your help....i'm trying to make the contract replication from backend system by the program BBP_CONTRACT_INITIAL_UPLOAD.
But there is a message erro in coditions as down
''End of discount condition validity > end of price condition validity''
The replicate will work but all the contract cames in SRM with memorize status and i have to edit all the contracts...
if i change the date of condition in r/3 contract, i can make the replicate without problem. But this is not a correct solution.
there is a way to solve this?
I saw the notes in SAP but my Support Package is the last one (SAPKIBKT11)
Thanks all
gustavo

Hello Gustavo,
We are facing the same problem and are trying to figure out the solution from you inputs.You have suggested 2 options
1. BADI : BBP_CTR_BE_CREATE
But this BADI will be called when a contract is to be created in the backend and how will this BADI be helpful when we are replication/uploading contracts from backend R3 to SRM
2. Maintain same pricing conditions in both R3 and SRM: could you explain in details what you are trying to say.
Thanks
Raghu

Problems : Payment conditions replication

Similar Messages

Maybe you are looking for