Vendor payment terms replication

[Former Member]

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.

[Former Member]

Thanks Muthu.Please update me if you know any other information.I will go through the note and simulate with my problem.

Regards,

[former_member183819]

Hi

Report BBP_UPLOAD_PAYMENT_TERMS is used to replicate the terms of

payment from the backend system into EBP.

I belive these data are stored in BBP_PAYMENT_MAP and some payment text table ...

regards

Muthu

[Former Member]

Hi Muthu,

Thanks for you reply.When i use BBP_UPLOAD_PAYMENT_TERMS ( BY giving the logical system name of the source), I am getting an error message in slg1, stating 'Error determining Purchasing date start vendor update manually.

Is there any way to update a single vendor / Not mass maintainance.

Thanks

[former_member183819]

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

--

i will also check and come back to you.

regards

muthu