contract transfer to backend

[Former Member]

HI :

I have activiated the BADI BBP_DETERMINE_LOGSYS and set the cv_logsys with logical system name of the backend,But no contracts can be transferred to backend.does anyone could give me any suggestions.TKS.

[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.

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

BBP_DETERMINE_LOGSYS

BBP_CTR

BBP_CTR_BE_CREATE

Award the points if it helps.

BR,

Vijay Mittal

Award the point

[Former Member]

We have the same issue, could somebody give us some advices any more?

[Former Member]

HI:

have maintained condition type in R/3.test again.Nothing happened.I am going mad.

[Former Member]

Hi,

Check the following things.

1) In the Org Structure, check the GCTR/PCTR in place in the attributes field.

2) Activate the following badis.

BBP_DETERMINE_LOGSYS

BBP_CTR

BBP_CTR_BE_CREATE

3) META_CTE_CHECK.

4) BBP_PDBE1 (Table)

5)BBP_CONTRACT_CTEATE.

6) BLAORD - Contract Idoc.

7) Check in WE05 and BD87 T.code.

I hope it will helps.

Award the points for the help.

BR,

Vijay Mittal

[Former Member]

If its not triggering anything, then its a pricing condition mapping problem. SRM uses O1CT by default, but this does not exist in R3, create O1CT condition type in R3 and make sure its correct and try again. If nothing happens, its pricing condition problem.. If your conditions are correct then you will get a successful distribution or an error message.

If nothing happens; no idocs generated, nothing in outbound queue, no error message at all = conditions are messed up.

If your number ranges, doc types, etc. are messed up = error message

[Former Member]

HI:

have created the model view and added the message type what you said to it.unfortunately there is no contract exit in R/3.and I still can't find any error message.anyway thank you.

[Former Member]

HI:

the settings what you said 2 3 4 are ok,but for the settings for BD64 in both R/3 and SRM.Which message type do I need to choose?

[Former Member]

U need to do teh BD64 settings on SRM system and for the Contract the message type would be BLARL.

Award the points for the help.

Vijay Mittal

[Former Member]

NO,I can not find any error message.so strange.

[Former Member]

Which scenario are you trying to accomplish? I assume you try to use GOAs in

SRM and distribute into R/3.

What settings did you do besides the Badi you mentioned?

Thanks,

Claudia

[Former Member]

Hi hong pan,

do you have any messages in the application monitor?

Does the system give any feedback for the document creation?

In order to create a backend contract also the settings for the IDoc

communication and the condition mapping needs to be done.

Thanks,

Claudia

[Former Member]

Thank you for your reply.Our version is ECC 5.0 and SRM 5.0

[Former Member]

Hi

Which SRM and R/3 versions are you using ?

<u>Please go through the follwoing pointers, which deal with the same issue -></u>

Hope this will definitely help.

Regards

- Atul