SRM - Transport Payment Terms

[Former Member]

Hello,

we are implementing SRM 4.0 in standalone scenario.

We would like to know how payment terms could be transpored from a dev system to a validation system and to a production system.

Indeed, payment terms which are created through SPRO dedicated transaction are put into a transport request with the logical system related to the dev system. Therefore, after transport to val, the logical system is not correct ...

We have noticed that the tables BBP_PAYTERM and BBP_PAYTERM_TEXT which handle the payment terms could be maintained directly through SE16.

We then thought to maintain all our records directly into dev system with SE16 for logical systems val & pro and to put them manually into a transport request.

Do you know a better solution ?

Thank you for your help.

Regards.

Fabrice

[Former Member]

Hi Fabrice,

Payment terms can be replicated from backends with report BBP_UPLOAD_PAYMENT_TERMS (in that case they have the backend Logical System as key) or maintained locally (in that case the LS is the local one).

For backend values, you can replicate them between each val/val, prod/prod server.

But for local ones, you are right, the source LS is transported with the values. So we have to adapt the LS of those tables in the target system.

You should run transaction BDLS, limited on this table, to adapt the LS.

Rgds

Christophe

PS: please reward points for helpful answers

[Former Member]

Hi Christophe,

BDLS is critical and it is not intendeded for production system.

Do you agree ?

Fabrice

[Former Member]

I Agree that this is a critical transaction, and can be very risky in production system.

Otherwise, don't transport them and open the customizing in your production system (if required because SE16 is enable for BBP_PAYTERM table) to create the payment terms.

Rgds

Christophe

[Former Member]

Thanks Christophe, you confirm what we would like to do.