SRM Contract condition type not passed to backend contract

[Former Member]

Hello All,

We are using SRM 7.0 central contract and for pricing we created identical condition types in SRM system and maaped it in calculation schema.

Contract with a base price PB00 works absolutely fine and a backend contract is created witht the same condition type.

This issue arises if I use Z-condition type for e.g. Z123 (here Z123 is defined as a discound condition)

Now when a central contract is created with two condition including discount then two behaviour are observed

Case 1:

In SRM central contract, two condition are being used

PB00 - 1000 USd

R003 - 10% (standard condition)

In backend , the contract has both the condition PB00 as 100 USD and Z123 as 10% . In WE02 this idoc has status 53 ie. processed successfully.(COND_A02 basic type and COND_A message type)

Case 2:

Creaet second central contract two condition are being used

PB00 - 1000 USd

Z123 - 10% (here Z123 is a replica of condition type R003)

In this case, In backend system , the contract is created with only one condition type PB00 as 100 USD the other condition type Z123 is missing although the idoc (COND_A02 basic type and COND_A message type) has status 53 ie. processed successfully.

Please let me know why the system behaves in different manner for both the condition type Z123 an R003, and alsowhy the IDOC status is 53 successfully posted when one of the condition type is not copied to the backend contract.

Has anyone encounter this type of issue, then pelase let me know.

Thanks,

Yatin

[Former Member]

Hi Ravat

Keep it SRM condition type as it is and map them via BADI BBP_CTR_BE_CREATE rather than create new condition type in SRM

01CT = PB00

01RP = RA00

Muthu

---

SOA - Enterprise services

You may not use XI and ECC EHP4 technolgy due to your landscape

Note 1324759 - Behavior of condition records in central contracts

IMG> Integration with mySAP.com Components-> Supplier Relationship management> Central Contracts> Assign conditions.

[laurent_burtaire]

Hello Yatendra,

Does your specific contract condition type exist in SRM IDoc generated ?

Regards.

Laurent.

[Former Member]

Hello Laurent.

As I mentioned earlier in both the scenraio, the idoc is getting posted successfully and the relevant conditon type Z123 can be seen in segment E1KONP

E1KONP KSCHL PB00 this combination not working

E1KONP KSCHL Z123

E1KONP KSCHL PB00 this combination not working.

E1KONP KSCHL R003

I am not able to understand why it works for one and it doestnt work for another, any idea?

Thanks,

Yatin

[Former Member]

A lot of corrections for contract pricing have already been fixed in the SAP standard code with the below mentioned notes.

1493011;1491183;1484754;1488324;1503418;1495230;1484754;1456679;1488056;

1505272;1456679;1506053.

Pls check the validity and implement them.

Regards,

Neeraj

[Former Member]

Hi Yatendra,

Just for clarity, you have maintained the condition type Z123 in both SRM and ECC. Am I right? Do you find the condition type Z123 in the IDOC in ECC? If it is there in the IDOC then it should be posted. Try to create a contract in ECC manually with Z123 just to check if it works fine.

Ideally, if you have the condition type Z123 in SRM and ECC then it should be fine. However, if you have implemented the BADI then please check the code if Z123 gets left out in the logic.

Regards

Saravanan.

[Former Member]

Hello All,

As I have already mentioned the condition types in SRM are identically matched to ERP condition type hence the data is flowing correctly and even the idoc has the z-condition type Z123.The IDOC in backend ERP has status 53.

On trial and error method we did unchecked the manual indicator check in the pricing schema for the relevant condition type and because of that now the Z-condiiton type can be seen in the backend ERP contract.

If the indicator was checked, this means that this condition can be maintained only manually (directly in the transaction

ME32K in ECC) and nothing can be transfer from other source.

Note: If the same condition type is being used in more than one pricing procedure then ensure that the check bok is unchecked for agianst the relevant condition type.

Thanks,

Yatin

[Former Member]

Thanks Yatin,

your suggestion helped us, We have been trying to figure for few days for updating multiple condition in contract from srm to backedn. esp the Note is very helpful making us to change in all the condition with manual entry flag unchecked.

Bravo!!!

Thanks,

Prakash