External requirement not transfered to SRM

[Former Member]

Hi Friends,

I am working with SRM5.0 SP10 in integration with SAP R/3 4.6B in backend. I am working with extended classic scenario. When I execute report BBP_EXTREQ_TRANSFER, I find PR getting stucked in R/3 outbound with status "ANORETRY".

When I check aplication log in SLG1 in SRM, there is no message i.e. application log is not captured.

I have done following settings in SRM:

1. created an entry channel in PPOMA_BBP

2. assigned RFC user (R/3 to SRM) to entry channel with SAP_ALL and purchaser role

3. have given procurement responsibility for this entry channel to purchasing group (corresponding to

backend Pgrp)

4. maintained attribute BSA: NB and DP_PROC_TYPE: ECDP

5. assigned NB transaction type to shopping cast

6. maintained external number range for NB, corresponding to internal number range of doc type NB of

purchase requisition in back end system

Can anybody suggest, if I am missing something or gone wrong with any configuration setting?

Thanks & regards,

Prashant

[Former Member]

Hi Prashant,

integrate a local POrg and PGroup into the Org Model as well.

All transfered Req are automatically assigned to the local Org Elements.

Cheers,

Claudia

[Former Member]

Dear Claudia,

Thanks for immediate reply. I missed this point. I have created local Purch org unit and Local Purch Grp.

The structure is like this-

Root Node

---Company

-

---

Purchasing Org

-

---

Purchasing grp correspoding to baknd (responsible to entry channel)

-

---

Entry channel

---Local Purchasing Org

Regards,

Prashant

Edited by: Kamat Shankar on Feb 6, 2008 10:21 AM

[Former Member]

Hi Prashant,

1.Please check whether the RFC / ALE user assigned to the channel in the root org. is the same as that defined in the SM59 txn.

Also check the RFC / ALE user for any inconsistencies using BBP_BP_OM_INTEGRATE and rectify if any.

2. Also define channel at plant level instead of Co. code level. Some time this error comes because the company code could not be recognized for external requirement transfer.

3. Once again check whether the entry channel is maintained in the Responsibility of the concerned P.Grp or not.

Hope this will definitely help you in resolving the issue. Clarifications are welcome.

Award points for helpful answers.

Rgds,

Teja

[Former Member]

Hi Prashant,

you need both like this:

Local Purchasing Org

Local Purchasing Group

Cheers,

Claudia

[Former Member]

Dear Teja,

Thanks for your inputs. i have reconfirmed settings. Checked It is as you suggested. Unfortunately, no luck.

Regards,

Prashant

[Former Member]

Dear Claudia,

I did it that way. No luck. My Org structure looks like this now:

Root Node

---Company

-

---

Purchasing Org

-

---

Purchasing grp correspoding to baknd (responsible for proc of entry channel)

-

---

Entry channel (RFC user assigend to it)

-

---

Local Purchasing Org

-

---

Local Purchasing grp (responsible for proc of entry channel)

Regards,

Prashant

Edited by: Kamat Shankar on Feb 6, 2008 10:44 AM

[Former Member]

Hi

did you maintain the tables TBE11 and TBE31 as mentioned in Note 656597?

1. In table TBE11

Application ID Active Text

PM X Plant maintenance

2. Make an entry in table TBE31 for event 01000710 with the following fields:

Event Country Application Function module

01000710 PM BBP_EPRTRANS_MAINTAIN

Also check if you maintained table T160EX and T160PR in R/3 to define with Reqs

are supposed to be moved to SRM.

Cheers,

Claudia

[Former Member]

Dear Claudia,

Thanks for the reply. I have already maintained these settings in R/3. Still its the same problem.

Regards,

Prashant

Edited by: Kamat Shankar on Feb 12, 2008 7:09 AM

[Former Member]

Hi,

Pls check whether the logical system name is properly maintained in R/3 system.

See these notes /links for more pointers:

*Note 656597 - External requirements not transferred to SRM

Note 648074 - Extended transfer of purchase requisitions to SRM

Note 1027506 BBP_EXTREQ_TRANSFER: ANORETRY for PR with different vendors

Note 534419 Transfer of purchase requisitions into the procuremnt system

Note 447516 Composite SAP note PlugIn Correction for External Requiremts

Note 1038484 External requirement transfer fails when PM order changed

Note 909722 - XML inbox: Vendor/invoicing party not replicated

BR,

Disha.

Do reward points for useful answers.