Payment term key with limit days in Extended Classic Scenario

[Former Member]

Hello,

We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package

9) using the Extended Classic Scenario.

When a shopping cart is created, it must be approved, and then a

purchase order is generated (first locally at SRM, and then is

replicated to the backend).

The problem is that the payment term key (field at header level EKKO-

ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the

field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).

Example:

ZTERM ZTAGG

K180 09

K180 19

K180 31

If the payment term key selected has no several values for the field "limit

days" (one single entry), the payment term key arrives correctly at the backend purchase order.

Example:

ZTERM ZTAGG

E000 00

In SRM table BBP_PAYTERM we have upload the backend payment terms

(using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.

We have already implemented note 846009, in order to use always the backend payment term, but the error didn’t get resolved.

We have our vendor business partners mapped to the local and backend

purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.

Regards

[Former Member · Accepted solution]

hi,

Pls see the foll notes:

Note 576349 - Terms of payment in the ECS

Note 541934 - Modification note: Copying base date from T052

Note 953999 - ECS: Terms of Payment values not in PO header

<b>Note 940453 - Backend payment term data not updated in the extended PO

Note 945018 - Incoterms data not transferred to the back end</b>

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

Thanks for the reply, but none of those notes apply to the SRM Server 5.0 (SRM 4.0).

Regards

[yann_bouillut]

Hi,

First of all, i would recommend to apply OSS note 946201 so that you do not maintain local purchasing organization/group anymore !

Kind regards,

Yann

[Former Member]

First, thanks for the reply.

With the implementation of note 846009, we have more or less the same as you propose (we have only a payment term key only for the mapped backend purchasing organization, and when the payment key doesn´t have several entries for different "limit days", it works well).

Regards.

[Former Member]

The problem is solved.

Actually, the problem wasn´t in SRM, but in the BAPI BAPI_PO_CREATE1, which didn´t manage well the values of the payment terms.

[yann_bouillut]

Hi,

Did you solve it by implementing an OSS note or did you solve it by specific developement ?

Kind regards,

Yann

[Former Member]

Hello,

We first resolve the problem by specific development.

Later SAP reply the OSS note recommending us to implement note 927398 - Payment conditions not transf. to R/3.

We implemented the note and the problem get resolved, so we eliminated the specific development.