Backend contract

[Former Member]

Hi all,

We created Purchase Requisition in Backend. Then in Enterprise Buyer we

proceeded with Bid Invitation and created the backend Purchase

Contract. But it created without reference to Purchase Requisition. (Item 00010 does not contain a purchase requisition). Is this situation correct? If not please help to solve the problem.

We are using SRM 4.0 in Extended classic scenario.

Regards,

Vlad

[Former Member · Accepted solution]

Hi Vlad,

as far as I know and tested, the behaviour you described it the standard. You need

to complete the initial Req manually.

The scenario of moved reqs from ECC to SRM has already some restrictions;

the reference to the initial req is only valid in certain situations. Have a look into

Notes 505030. Additionally, the contract scenario is 4.0 is quite basic and not yet

fully blown. That is a bit different in 5.0, but also not solved in 6.0.

Cheers,

Claudia

[Former Member · Accepted solution]

Hi,

Kindly do the following settings,

1) Maintain the IDOC settings in the BD64 for the Contract.

2) Maintain the Transaction Types of contract like GCTR or PCTR in the Org Structure Attributes tab.

3) Activate the following Badis.

BBP_DETERMINE_LOGSYS

BBP_CTR

BBP_CTR_BE_CREATE

4) Maintain the Document type and no. rangs in both the systems.

5) META_CTE_CHECK.

6) BBP_PDBE1 (Table)

7)BBP_CONTRACT_CTEATE.

😎 BLAORD - Contract Idoc.

9) Check in WE05 and BD87 T.code.

I hope it will helps.

Award the points for the help.

BR,

Vijay Mittal

[Former Member]

Hi all,

Thanks for your answers!

2 Atul: I'm using R/3 version 4.7

SAP_BASIS (SAPKB62057)

SAP_APPL (SAPKH47025)

2 Claudia: Yes, it's already clear for me, but maybe there is a not standart way to resolve the problem.

2 Vijay Mittal: I have made the following:

Maintained attributes in org. structure, activated 3 BAdIs you mentioned, Maintained the Doc type and no. rangs, made settings for BLAORD and COND_A IDOCs. Could you tell me more about the other steps?

Regards,

Vlad

[Former Member]

Hi

As I told you in my earlier reply, please go through this Note.

<u>Note 576584 - PReq references in the ECS with bid invitation process</u>

<b>This deals with the same symptoms.</b>

<b>Please raise a Customer OSS Message with SAP incase it does not suits you.</b>

Regards

- Atul

[Former Member]

Hi Atul,

The note you suggested is already implemented in our system. And for my OSS message I've resieved replay: "After check, I am afraid that this is the standard behavior of the system..." i e the problem has no solution.

But anyway thanks for your replays.

Regards,

Vlad

[Former Member]

Hi,

See if the foll notes are helpful:

Note 1047512 - Contracts: Duplicate Messages

Note 817949 - No warning message at completion of contract

Note 1036725 - Contract Management: message BBP_CTR 079

Note 643551 - Contract: customizable messages

Note 920114 - Disable 'DELETE' while creating a new Contract

Note 902043 - Contract item created with line 0

Also see this related thread:

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

Hi Disha,

It seems that there is no solution for my question in this notes. In my case the contract is created in backend, but when in tc me33k i go through menu: Environment - Purchase requisition i have an error 'Item 00010 does not contain a purchase requisition'. In tc me52n i can fill manually the Source of supply. So the question is has the contract to contain the link to the Requisition or not?

Regards,

Vlad

[Former Member]

Hi

<b>Which R/3 backend version are you using ?</b>

<u>Please go through the follwoing SAP OSS Note, which discusses the same issue ->></u>

Note 30038 - Requisition reference not updated in outline agreement

<u>Note 576584 - PReq references in the ECS with bid invitation process</u>

<u>Other related OSS Notes -></u>

Note 453888 - FAQ: Reporting in the purchasing

Note 458384 - FAQ: Consulting for the changeover to the euro in purchasing

Do let me know.

Regards

- Atul