Status distribution incorrect in GOA

[Former Member]

Hi,

i've created a shopping cart, then bid invitation followed by Bid submission to bid acceptance. Then i created a contract from this bid response successfully. But the problem is when i distribute this contract to R/3, distribution fail with status "Distribution incorrect" I don't understand the missing link. Am using SRM server 5.5 (SRM 5.0) with ECC 6.0.

Kind Regards,

Maggie

[Former Member]

Hi Gigi,

We are experiencing the same problem, could you explain what the problem was and how you managed to solve it please?

Thanks

tugrul

[Former Member]

Good day,

Status has now changed as the problem was in R/3.

Regards,

Gigi

[Former Member]

Hi

That's Great.

Problem resolved anyhow.

Good Day !!

Regards

- Atul

[Former Member]

Hi Gigi,

I am working on GOA in classic scenario, SRM 5.0, with backend ECC 6.0 and SRM support package SAPKIBKT09. I am facing the same problem.Can you suggest me how did you resolve your problem? No idoc is being created right now in SRM and ECC.

Error is GOA distribution incorrect. SMQ1 Queue name- B46B_CTR_TRANSFER- Function parameter "IV_BE_OBJTYPE" is unknown. When I double click on the function module, it says- Function module does not exist.

Regards

Kapil

[former_member195032]

Hi Goithoma,

I faced exactly same problem and coded a BADI to solve this issue.

Actually Condition type in SRM and ERP is different and that is the reason for this.

BADI Name: bbp_ctr_be_create

Sample Code is

METHOD if_ex_bbp_ctr_be_create~contract_interface_fill.

TYPES : BEGIN OF ls_mapping,

cond_type_old TYPE kscha,

cond_type_new TYPE kscha,

END OF ls_mapping.

DATA : lw_ct_be_text TYPE bbps_ctr_text.

DATA: ls_be_items TYPE bbps_ctr_item,

ls_be_cnd_ct TYPE bbpbapicondct,

ls_cnd_hd TYPE bbpbapicondhd,

ls_cnd_it TYPE bbpbapicondit,

ls_cnd_qs TYPE bbpbapicondqs,

ls_cnd_vs TYPE bbpbapicondvs,

ls_mapping TYPE ls_mapping,

lt_mapping TYPE TABLE OF ls_mapping,

lv_tabix_ct TYPE sy-tabix,

lv_tabix_hd TYPE sy-tabix,

lv_tabix_it TYPE sy-tabix.

• Condition Type mapping from SRM to ERP system.

ls_mapping-cond_type_old = '01CT'.

ls_mapping-cond_type_new = 'PB00'.

APPEND ls_mapping TO lt_mapping.

ls_mapping-cond_type_old = '01RA'.

ls_mapping-cond_type_new = 'RB00'.

APPEND ls_mapping TO lt_mapping.

ls_mapping-cond_type_old = '01RH'.

ls_mapping-cond_type_new = 'RA01'.

APPEND ls_mapping TO lt_mapping.

ls_mapping-cond_type_old = '01RP'.

ls_mapping-cond_type_new = 'RA00'.

APPEND ls_mapping TO lt_mapping.

• go through all service items (product_type 01 = normal material,

• product_type 02 = service)

LOOP AT ct_be_items INTO ls_be_items.

• additional loop on local condition table if product_type = 02

• if 02 --> change SRM condition 01CT to PRS

• only valid with services !

IF ls_be_items-product_type = 02.

LOOP AT lt_mapping INTO ls_mapping

WHERE cond_type_old = '01CT'.

ls_mapping-cond_type_new = 'PRS'.

MODIFY lt_mapping FROM ls_mapping.

ENDLOOP.

ENDIF.

LOOP AT ct_be_cnd_ct INTO ls_be_cnd_ct.

lv_tabix_ct = sy-tabix.

LOOP AT lt_mapping INTO ls_mapping

WHERE cond_type_old = ls_be_cnd_ct-cond_type.

CLEAR ls_be_cnd_ct-cond_type.

MOVE ls_mapping-cond_type_new TO ls_be_cnd_ct-cond_type.

ENDLOOP.

MODIFY ct_be_cnd_ct FROM ls_be_cnd_ct.

ENDLOOP.

LOOP AT ct_be_cnd_hd INTO ls_cnd_hd.

LOOP AT lt_mapping INTO ls_mapping

WHERE cond_type_old = ls_cnd_hd-cond_type.

CLEAR ls_cnd_hd-cond_type.

MOVE ls_mapping-cond_type_new TO ls_cnd_hd-cond_type.

MODIFY ct_be_cnd_hd FROM ls_cnd_hd.

ENDLOOP.

ENDLOOP.

LOOP AT ct_be_cnd_it INTO ls_cnd_it.

LOOP AT lt_mapping INTO ls_mapping

WHERE cond_type_old = ls_cnd_it-cond_type.

CLEAR ls_cnd_it-cond_type.

MOVE ls_mapping-cond_type_new TO ls_cnd_it-cond_type.

MODIFY ct_be_cnd_it FROM ls_cnd_it.

ENDLOOP.

ENDLOOP.

ENDLOOP.

ENDMETHOD.

Regards,Nishant

Please reward points if this helps.

[Former Member]

Hi Nishant,

I've implemented the BADI, it doesn't solve my problem.The worse part is am not even getting message to alert what is actually missing.

Rgs,

Maggie

Message was edited by:

Goithoma Magdeline Maletsoa

[Ramki]

Hi Goithoma

1) Do you see any thing in the Contract Monitor ( BBP_CTR_MON) ? This will be in SAP_EC_BBP_ADMINISTRATOR role.

2) Check WE05 in R/3. What are the error messages in IDOC ?

Best regards

Ramki

[Former Member]

Hi Ramki,

Now am heading somewhere.In smq1(SRM) amd getting error message "FUNCTION PARAMETER "IV_BE_OBJTYPE" is unknown. And when i click on the FM : BBPV_CONTRACT_TRANSFER i get error message " FUNCTION MODULE DOES NOT EXIST"

Rgs,

Maggie

Message was edited by:

Goithoma Magdeline Maletsoa

[Former Member]

Hi

<u>There is a BASIS Support pack missing in this case. Please ask the BASIS Team to download the Support pack in the system and the problem will get resolved.</u>

I will tell you the support package to downloaded in this case.

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Hi

Please refer to OSS Note as well.

Note 923227 - Attachments transfer not working in Background

Which SRM version you are using ? Which support package ?

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Hi Atul,

Am using SRM Server 5.5, support package SAPKIBKT07.

Rgs,

Maggie

[Former Member]

Hi

<u>Please implement this OSS Note in the system.</u>

<b>OSS Note - 945029 Distribution of Target Quantity to QW8 failed</b>

I hope this will solve the issue.

Please reward suitable points.

Regards

- Atul

[Ramki]

Hi Maggie

Check if you have a backend contract with document type same as that of SRM.

e.g. if you are using GCTR as the document type in SRM, then GCTR should exist in R/3 also. Ensure that the internal no range in SRM and external no range in R.3 or this doc type are same.

Best regards

Ramki

[Former Member]

Hi Ramakrishna,

Document type and number ranges exist correctly.

Regards,

Maggie

[Former Member]

Hi

Have you checked the OSS note -- 945029, I mentioned you earlier ?

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Atul,

Not yet, because the contract is stuck in WE05 in R/3 because of the short dump i've send to you. DYNPRO_NOT_FOUND. Am trying to solve that before i can conclude that my problem is solved.

Rgs,

Maggie

[Former Member]

Hi

<b>Incase you want to archive this IDOC, which is in Error in WE05 Transaction.</b>

<b>Goto Transaction - SARA and put the object as IDOC.</b>

<u>See this links for further help.</u>

<b>http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b81ed43d711d1893e0000e8323c4f/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/8d/3e5110462a11d189000000e8323d3a/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/8d/3e4bb1462a11d189000000e8323d3a/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/0b/5d193ad0337142e10000000a11402f/frameset.htm</b>;

Keep me posted.

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Hi Ramki and everybody,

which Idoc-type do you use?

In Configuration Guide (strategic sourcing from 12.11.2004) page 66 it only saies "setting up he idoc inbound processing of contract release order data" in SRM system.

Thus the way ERP -> SRM you should use BLAREL.

Now which idoc type do you use in distribution model for the direction SRM -> ERP? Which message-type did you check in WE05??

Thank's a lot for hints in advance.

Best regards,

Felix