The contract condition in the ECC affect the replicated PO from SRM

[Former Member]

Dear ,My expert :

I work in SRM 7.0 SP03,ECS .

In the ESC , the PR is transfered from ECC system and generate one Shopping Cart in SRM syetem.The purchaser carry out sourcing ,and convert the Shopping Cart to PO(according to the contract ) .The PO will be replicated into the ECC system .

In my scenario ,the contract is created in SRM ,and transferd into the ECC system .

I am confused that the PO will calculate the net price according the contract in the ECC system .eg,Contract in SRM net price 100$ and the discount 10% ,so the PO net price is 90$ .But the replicated PO in ECC net price is 81$.

Is it the grogram error ?

BR!

Alex!

Edited by: Alex on Apr 16, 2010 12:25 PM

Edited by: Alex on Apr 16, 2010 12:55 PM

[Former Member]

Hi Alex,

We have exact similar issue with contract conditions (e.g. discount) double counting when PO it replicated to ECC6. This happens specifically for PO item with Service Master. We have previously logged this to OSS and were only told this is standard ECC6 system limitation with no resolution provided from SAP.

Appreciate if you can share with us on your findings to resolve this issue.

Many thanks.

Cheers,

Tom

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

i am sorry, SDN went a loop for a while.

[Former Member]

Hi;

Wow , I received 21 emails from SDN forums.:)

Muthu ,In my case the follow on document is "PO"or "contract ".So I defined the contract as the RFx 's follow-on document .

Only the PO transaction type ?

Or I take a mistake?

BR!

Alex!

[former_member183819]

PO or Contract

Then you can decide before you publish the bid invitation.

I don t remeber the tab

but try in Bid Invitation

document type as select as Purchase order rathe rthan Contract and you will get Purchase order. so now control is your side.

Send me a web screen .basic data of Bid Invitation. long back worked and i forgotten.

it was SDN error you got more mails due to this thread.

Good luck

Muthu

[Former Member]

HI,Muthu :

I create the PO follow the SC in the "Carry out sourcing ".So I do not think the Bid Invitation will affect it .

And then ,the material type PO is work well ,and the Service type PO price calculate again in the ECC system .

BR!

Alex!

[former_member183819]

Eventually Purchaser only determine the follow on docuement either PO or COntract

Are you creating Purchase Order only? for that accepted Bid? but are you geting as Contract if it so DP_PROC_TY = GCTR as default?

Muthu

[Former Member]

Hello Alex,

I do not make use of GOA, contract replication, so couldn't tell you from our system. Take a look at the following notes or search for your self service.sap.com/notes. If there is nothing i think you should start thinking of posting a customer message.

Note 1446993 - Contract discount pricing condition applied twice on SHP

1404246 Deleted contract conditions reloaded in PO change version

Note 1332076 - Multiple base price conditions results in error in contract

Note 1357383 - Duplicate conditions appear in PO created from SC

Kind regards,

Tim

Edited by: T. Schuffelen on Apr 20, 2010 9:39 AM

[Former Member]

Hi Alex,

We have exact similar issue with contract conditions (e.g. discount) double counting when PO it replicated to ECC6. This happens specifically for PO item with Service Master. We have previously logged this to OSS and were only told this is standard ECC6 system limitation with no resolution provided from SAP.

Appreciate if you can share with us on your findings to resolve this issue.

Many thanks.

Cheers,

Tom

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[Former Member]

Hello Alex,

Seems strange to me aswell. Seems as if the discount/condition is applied twice, first in SRM and then again in ECC. -> issue

What kind of contract are you using: local srm contract (PCTR)? global outline agreement (GCTR)? central contract (CCTR)? You should be able to look this up via BBP_PD or maybe even via viewing the 'define transaction type' transaction, to see wich one is active.

Kind regards,

Tim

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[former_member183819]

alex. in your transaction type of Bid invitation

process control

check as Purchase order

not Contract. now contract must have pointed.

Muthu

[Former Member]

HI,Tim :

I used the "Global Contract "in my SRM system .It means the contract is created in the SRM system ,and then transferd into the ECC system .The purchaer can user it in the SRM OR ECC .

BR!

Alex!