Follow-on contract from Bid Invitation

[Former Member]

Hello,

SRM 5.0SP11 ECC 6.0

CLASSIC

Sourcing with Bid Invitation

PO as a follow-on for BI is working fine

Now the task is to create contract as a follow-on.

So we use the BI trans type RFCR with internal no range matching to external no range of MK in ECC contract type.

For transaction type of follow-on doc types for RFCR

our entries are

Trans cat=BUS 2200

Trans type=RFCR

Sub obj type=BUS2000113

follow-up=PCTR

Distribution model is distributed from SRM to ECC with message type BLAREL

Partner profiles are set in SRM & ECC in WE20.

outbound and inbound parameters for SRM & ECC are maintained with message type BLAREL as per config guide.

Ports are correctly defined in WE21

BADI BBP_DETERMINE_LOGSYS points to our backend

but when "create contract" button is clicked for accepted bid

error message "Backend data could not be read"

ECC receives no IDOC.

If we run FM B46B_CTR_CREATE in SRM

for msg ID BBP_BD

we get

Transaction type for backend system not maintained.

But we have mapped ECC contract type "MK" with same no range.

Any thought?

BR

Dinesh

[imthiaz_ahmed · Accepted solution]

You need to maintain the same document types in both the systems.

Regards, IA

[Former Member · Accepted solution]

Thanks, Imthiaz.

As per yr suggestion

have created a doc type for contract PCTR in ECC

but still ECC is not receiving any IDOC.

If I run FM BBPV_CONTRACT_CREATE in ECC

and give my SRM system as IV_CALLING_LOGSYS

I am getting message

IDOC (BLAORD03) could not be saved

Also, with this suggestion do you mean to say that

we can create ECC contract only of one doc type

though in SRM we can set multiple in attribute CT_PROC_TY.

Update is that now I am able to create local contract after

the purchaser accepts the bid and clicks on "Create contract".

It is created in "Held" status.

Since we have auto approval workflow for contract no approval is required.

But when the strategic purchaser release the contract, SRM should puch the IDOC (BLAREL) to ECC

it is not happening.

We are not using BADI BBP_CTR_BE_CREATE.

and code in CONTRACT_LOGSYS_DETERMINE

under BADI BBP_DETERMINE_LOGSYS

is

method IF_EX_BBP_DETERMINE_LOGSYS~CONTRACT_LOGSYS_DETERMINE.

DATA: wa_items TYPE bbp_pds_transfer_item.

READ TABLE it_items INTO wa_items INDEX 1.

IF sy-subrc = 0.

cv_logsys = wa_items-be_log_system.

ENDIF.

endmethod.

Can you throw some more light?

BR

Dinesh

[imthiaz_ahmed · Accepted solution]

I think Dinesh, the error is here:

cv_logsys = wa_items-be_log_system

Verify what wa_items-be_log_system is pointing to. I think it is pointing to the local SRM system.

Regards, IA

[Former Member · Accepted solution]

Thanks, Imthiaz and all,

We tested with hardcoding

cv_logsys = 'R3DCLNT200'.

(R3DCLNT200 is our backend)

But we are getting error

Backend data could not be read

Summarising the scanario and the revised settings once again:

The business scenario in brief is as follows:

PR will be created in ECC.

It will be transferred in SRM for sourcing.

When the PR is of high value OP purchaser will choose BI type=contract

negotiation.

OP purchaser will fill the required details and publish the BI.

Interested bidders will submit the respone i.e. bid.

Op pur will accept the winning bid.

Out of this accepted BID he wants to create a CONTARCT in ECC ONLY

directly.

The settings we have done:

• Number ranges for SRM server purchase contracts have been maintained

as

C4 3400000000 3499999999

C5 3500000000 3599999999

• New trans types

ZLQT &

ZLVA

have been created for SRM purchase contract (copying PCTR)

made active and assigned the no ranges C5 & C4 respectively.

• Under ECC config->MM->purchasing->contrac->no ranges

this no ranges are available

and marked as external.

• In ECC define doc types for contracts

Doc types

ZLQT &

ZLVA

are available and assigned no ranges C5 & C4 as external respectively.

• Under trans types config in SRM

Bid invitation trans type

RFCR is made active

assigned internal no range

in the follow-on trans type for this type

entries are

BUS2200 RFCR BUS2000113 ZLQT

BUS2200 RFCR BUS2000113 ZLVA

• In the attribute CT_PROC_TY we have NOT maintained the doc type of

ECC contract

SINCE THIS ATTRIBUTE ALLOWS ONE VALUE ONLY.

This is standard or a bug?

• BADIs for contract management in SRM & ECC

SRM -

BADI BBP_DETERMINE_LOGSYS (activated)

in method CONTRACT_LOGSYS_DETERMINE

coding:

method IF_EX_BBP_DETERMINE_LOGSYS~CONTRACT_LOGSYS_DETERMINE.

DATA: wa_items TYPE bbp_pds_transfer_item.

READ TABLE it_items INTO wa_items INDEX 1.

IF sy-subrc = 0.

cv_logsys = wa_items-be_log_system.

ENDIF.

endmethod.

BADI BBP_CTR_BE_CREATE (Deactivated-Not reqd)

ECC-

BADI BBP_CTR (Not implemented)

• Created a distribution model from SRD200 to R3D200

with message type BLAREL

created partner profile

outbound parameter for SRD200

Message type - BLAREL (Idoc type BLAREL02)

Inbound parameter for R3D200

Message type - BLAORD (Idoc type BLAO)

Message type - BLAREL (Idoc type BLAR)

Message type - COND_A (Idoc type COND)

• In inbound process code in ECC WE42

Process code BLAO is assigned to message type BLAORD

Process code cond is assigned to message type COND_A

• Ports are available in WE20

• WF WS14000086 is active with simple creation date criteria.

After all these settings it is expected that

a contract of selected doc type in accepted bid

should be created

directly in ECC R3D200

But SRM is creating a held contract locally only i.e. in SRD200

Evenafter the strategic purchaser releases this contract

no IDOC is starting from SRM and entering in ECC.

We see that our settings are correct as per config guide.

Then why SRM is not creating contract directly in ECC?

Any new thoughts?

BR

Dinesh

Edited by: Dinesh Powale on May 22, 2008 4:10 AM

[Former Member]

Hi Dinesh,

Pls check the foll settings:

1. Business Add-In BBP_DETERMINE_LOGSYS and implement the method

CONTRACT_LOGSYS_DETERMINE for R/3 backend system.

Enter value field of the parameter CV_LOGSYS correctly in the method CONTRACT_LOGSYS_DETERMINE.

2.Determining the Transaction Type for Backend Contracts

In the organizational plan, assign the CT_PROC_TY attribute, for example,

PCTR to the responsible purchasing group.

3. Setting up Organizational Data and Mapping (Master) Data

1. Using transaction PPOMA_BBP, make sure the Purchasing Organization and

Purchasing Group of the backend system exist in the organizational plan.

a. Make sure to link the SRM purchasing organization to the purchasing

organization you use for contracts in the backend system: On the Function tab

under section Local

Select the Purch. Organization indicator

Enter the key of the backend purchasing organization

Enter the key of the logical system (backend)

b. Make sure to link the SRM purchasing organization to the purchasing group you use for contracts in the backend system: On the Function tab under section Local

Select the Purch. Group indicator

Enter the key of the backend purchasing group

Enter the key of the logical system (backend)

Make sure table VENMAP contains vendor data with identical GUID, backend vendor number and logical system.

4. Specifying Number Ranges for Backend Contracts

Maintain an internal number range for backend contracts

Procedure in the R/3 Backend System

1. Setting up the IDoc Inbound Processing

R/3 inbound processing uses different IDocs for creating contracts and conditions.

Transaction Code WE42

Menu Path Tools ® ALE ® ALE Development ® IDoc ®

Inbound Processing ® Define Process Code

...

1. Assign the inbound processing code BLAO for purchasing contracts to message type

BLAORD.

2. Assign the inbound processing code COND for conditions to message type COND_A

2. Creating the ALE Partner Settings

Transaction Code WE20

Menu Path Tools ® Business Communication ® IDoc Basis

® Administration ® Partner Profile

...

1. Create a partner profile for partner type LS (logical system of sending SRM system)

with the following entries and settings under Inbound parameters:

a. Message type BLAORD (for purchasing contracts), Process Code BLAO and

Transfer IDoc immediately activated.

b. Message type COND_A (master conditions, for price determination), Process

Code COND and Transfer IDoc immediately activated

3. Specifying the Document Types for Backend Contracts

Transaction Code OMEF

IMG Path Materials Management ® Purchasing ®

Contract ® Define Document Types

...

1. Choose the transaction type for backend contracts.

2. Enter a number range for external number assignment that is identical to the internal

number range you specified in the SRM system for backend contracts.

BR,

Disha.

[Former Member]

Hi Disha,

Thanks for revising the settings from config guide.

But if you had seen my earlier post.

I have done all these settings.

I would like to talk about yr Pt. No.2

If we define contract trans types/Doc types in org attribute CT_PROC_TY

I have observed that we can not specify multiple values.

Have you observed this?

So Alternate is just define the required contract trans type/doc type

under SRM IMG : cross applns :define trans type

and make them active

they will be available for follow-on contract for an accepted Bid

I am doubting my coding in

BBP_DETERMINE_LOGSYS : CONTRACT_LOGSYS_DETERMINE

think SRM is not able to get the backend PORG correctly

which is mandatory for direct backend follow-on contract creation from bidding.

Will keep updated.

BR

Dinesh

[Former Member]

hello,

i am having simmilar kind of error... can you plz help me out to resolve the same

vivek