cancel
Showing results for 
Search instead for 
Did you mean: 

BBP_EXTREQ_TRANSFER - Error Message

Former Member
0 Kudos

Hello SRM Experts,

we are working on a SRM 5.0 classic scenario system. We like to move the PRs from ERP 2005 backend to the SRM system via the report "BBP_EXTREQ_TRANSFER". In transaction SMQ1 in backend we got the error message "ANORETRY" and in transaction SLG1 in SRM we got two messages:

1. No address found for partner function type Anlieferadresse (Message no. BBP_PD051)

2. System status UVOL is active (Shoping Cart 100045405) (Message no. BS013)

Tables T160EX and T160PR are maintained also table EPRTRANS.

The input canal, RFC user, local Purch. Group and the responsibility are maintained in SRM.

Do we need a local Purch Group in classic scenario for the transfer?

Has anybody an idea about this issue?

Thank you very much for your answers.

Kind regards

Axel

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Axel,

I assume you try to move reqs without any account assignment, like coming from

MRP. For these reqs a local POrg as well PGroup is needed. With the local

settings in place the transfer should work. Additionally these reqs can only be sourced by standard when using the extended classic.

Cheers,

Claudia

Former Member
0 Kudos

Hi Claudia,

If I understood you correct is it not possible to transfer reqs from Backend to SRM in classic scenario or just the sourcing? Because I have already created a local POrg and PGroup and I´m not able to transfer the PRs.

Thanks.

Regards

Axel

Former Member
0 Kudos

Hi Axel,

it is possible to transfer, the sourcing is restricted by standard.

The error seems to be related to missing information for the RFC User in the

Org Model. Check the attributes and give the user the same like your purchasers

in SRM. Also check if the local POrg / PGroup is only ticked at function, but has

no entry in fields corresponds to.

Cheers,

Claudia

Former Member
0 Kudos

Hi Claudia,

I have checked all seetings your mentioned. The RFC User is assigned to the Org. Structure "Channel Backend" (Entry Channel). The user has the same attributes and roles like the other purchasers. Also has the user an "Purchaser Assignment" to the local PGroup. The local POrg / PGroup is only ticked at function and has no entry in fields corresponds.

Do you have an idea about the error message in SLG1?

"No address found for partner function type Delivery Address"

regards

Axel

Former Member
0 Kudos

Hi,

Firstly you need to create Ship-to-Address in SRM using BBMAININT Transaction (not using BP Transaction).

Here are the related links to this issue ->

Please refer this links as well.

BR,

Disha.

Pls reward points for useful answers.

Former Member
0 Kudos

Hi Axel,

check the settting Disha suggests creating a Ship-to-Address in SRM using

BBMAININT. At least there needs to be one.

Parallel, make a PGroup responsible for the "Channel Backend" in the extended

attributes of the PGroup. The "Purchaser Assignment" is not enough.

Cheers,

Claudia

Former Member
0 Kudos

Hi,

I think I found the issue, I was using the "LUW Debugging" in TX SMQ1. The partner parameter "IT_BUT" of RFC-Function Module "BBP_BC_EXTREQ_INB" will not be filled correctly. The fields "EXT_BU_ID" and "PARTNER_SRC_SYS" of structure "BBPS_ER_BUP_C" (IT_BUT) are empty and therefore I was receiving the error message. I was changing this values manually in debug mode and the ext. req. was created in SOCO.

<b>But I have still two problems:</b>

1. The ext. req. is not changeable in SOCO

2. The Table EPRTRANS will not be filled automatically. Is there any customizing settings necessary?

Kind regards

Axel

Former Member
0 Kudos

Hi

<b>Please go through the follwoing SAP OSS Notes as well -></b>

Note 648074 - Extended transfer of purchase requisitions to SRM

Note 656597 - External requirements not transferred to SRM

Note 948716 - External requirements reappear in the Sourcing Cockpit

Note 780420 - BBP_DOCUMENT_TAB: Core key entries not correct in SoCo

<b>Related links -></b>

<u>Other related links -></u>

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

Note 1027506 BBP_EXTREQ_TRANSFER: ANORETRY for PR with different vendors

Note 935457 EPRTRANS entry is written, even requisition has no release

Note 742682 Entry in EPRTRANS despite item w/o account assignment

Note 799253 Transferred ext. reqmnts cannot be transferred after change

Note 765348 Selection when transferring external requirements

Note 534419 Transfer of purchase requisitions into the procuremnt system

Note 447516 Composite SAP note PlugIn Correction for External Requiremts

Do let me know.

Regards

- Atul

Former Member
0 Kudos

Hi

For (1)

<b>See this SAP OSS Note</b>

<u>Note 756991 - Cannot change External Requirement in SOCO</u>

Note 505030 - Restrictions for the integration of external requirements

(2)

Note 792985 - No update of closed flag in BE-PR at complete in SOCO

Note 905894 - Performance improvement in Sourcing

Note 1004384 - Note 905894; 925151 - Correction

Note 813845 - Items are completed incorrectly

<i>Also go through this links -></i>

<b>Hope this will definitely help.</b>

Regards

- Atul

Former Member
0 Kudos

Hi,

the automatically transfer of data in table eprtrans after creating a PR is working fine now. The note 656597 was the key for fixing this issue.

But I have still one problem:

When the ext. req. are transfered into soco and I´m moving this to the workarea of purchaser, the sc is not changeable. There is a flag (GS_SOCO_DATA-GROUPAREA-ITEM_LIST-SC_ATLERABLE) which handles the maintain mode.

Has anybody an idea to get the sc changeable?

Thanks in advance.

Regards

Axel

Former Member
0 Kudos

Hi,

Pls see the foll note;

Note 978123 - Shopping cart not editable in sourcing cockpit

BR,

Disha.

Pls reward points for useful answers.

Former Member
0 Kudos

Hi Disha,

thanks for replying. I have the not 978123 already implemented.

Any other ideas?

regards

Axel

Former Member
0 Kudos

Hi,

I found in subroutine "CHECK_SC_ITEM_ALTERABLE" of function group "BBP_SOCO_APP" following standard coding statement:

<i>* Shopping Cart item can only be changed, in case Shopping Cart

  • is not an External Requirement and if no Purchase Order for the

  • was created.

  • External Requirements are not changeable!

if not is_item-ext_demid is initial.

move c_off to cv_alterable.

else.

........</i>

I was deleting the field "EXT_DEMID" in methode "BBP_SC_CHANGE" of BADI "BBP_DOC_CHANGE_BADI" and it works. The shopping cart is now changeable in SOCO.

Is that a proper solution, or can it be critical to delete the backend req. no.? Is there maybe no relationship between SRM and Backend req. anymore?

Or has anybody an other idea to solve the issue.

Regards

Axel

Answers (2)

Answers (2)

former_member222613
Participant
0 Kudos

Axel.

I have the same original issue in my system: No address found for partner function type address delivery (Message no. BBP_PD051).

Do you have a solution?.

Former Member
0 Kudos

Hi

Did you by any chance referred to SAP OSS Note ?

Note 1103966 - Error BBP_PD 051 in SRM documents

This is a Program Error.. SRM bug...

If an employee is delimited from HR system, when the employee is replicated to SRM system the corresponding business partner's BP relations will be deleted. The documents (PO, SC and etc.,) refers

this relation for address validation.

During the change of an SRM document error BBP_PD 051 " No address found for partner function type & "occurs. This error occurs for the partners "Requestor" or "Recipient" if the employee assigned to this partner is not valid anymore in SRM. This can happen if in SRM HR replication is active and in HR this employee was delimited because he left the company.

Do let me know.

Regards

- Atul

Former Member
0 Kudos

Hi

<b>Please go through the SAP OSS Notes below -></b>

Note 1027506 BBP_EXTREQ_TRANSFER: ANORETRY for PR with different vendors

Note 1038484 External requirement transfer fails when PM order changed

Do let me know.

Regards

- Atul

Former Member
0 Kudos

Hi Atul,

Thanks for your help.

I have implemented both notes but the error is still the same.

Any other ideas?

The RFC User, which is implemented in input canal (PPOMA), has the SAP_ALL rights. Do the user needs further rights (e.g Purchaser role) or special attributes in PPOMA?

Regards

Axel

Former Member
0 Kudos

Hi

Make sure you convert your RFC user as a dialog user and then integrate him into the entry channel. Once you are done with that you can convert that user back into a system user. Make sure this user has highest authorities and then you will see all you requisitions flow from R/3 to SRM. Please make sure that the RFC user-password in SU01 (SRM) is same as the password in SM59 for the SRM RFC destination in R/3. Looks like the passwords are not synchronized to enable the transfer from EPRTRANS table. Manually it doesnot get pushed either because your user ID might not have the required authorizations. Please check for password synchronizations and this should hopefully solve your problem.

<b>Related links -></b>

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

Note 891797 - Vendor/invoicing party that is not replicated

Hope this will definitely help.

Do let me know.

Regards

- Atul

Former Member
0 Kudos

Hi Atul,

I was checking all your recommendations and also the links but the problem is still there. Do you have an idea what the error message in SLG1 stands for?

"No address found for partner function type Delivery Address".

In one of the links are the transaction ME56 mentioned. With this TX it should be possible to create an entry in table EPRTRANS. I was trying this by using the TX and assigning a source of supply and save the PR but no entry has been created in table EPRTRANS. Do you now why this not happend? Or have I to do same customizing setting in backend?

Kind regards

Axel

Former Member
0 Kudos

Hi

Have you replicated the Plant to SRM that is being used in the Purch Req of R3??

Please check...

Also look at the <b>OSS Note 444941 - No address found for partner function type</b>, which talks about this error (but valid for older version of SRM)...But see whether this will help if the correction instructions in this note can be manually inserted...

Rgds

Reddy.

Former Member
0 Kudos

Hi

I am not sure.. but this can be a bug in the system.

<b>Also, Please make the follwing settings -></b>

<u>R/3</u>

Maintain Table entries for V_T160EX & V_T160PR

for logical connection of material group purchasing group

& RFC destination of SRM

Assign the proper RFC destination which you have created for SRM system

Check table CRMRFCPAR that teh RFC transfer for PR is active

<u>SRM EBP</u>

create a inbound channel

assign the proper RFC user of R/3 RFC destination beow this

Assign the responsibility of this channel to local purchasing group & category responsibility

then try to run the program BBP_EXTREQ_TRANSFER

<b>Anyways, please go through the following SAP OSS Notes as well -></b>

Note 927536 - Problems w/ plants during EBP3.0/3.5 upgrade to SRM server

Note 577398 - Enjoy PO BAPIs in SAP R/3 Release 4.6B

Note 803061 - Ordering address for the vendor cannot be selected

Note 493256 - 'No address found for partner function type goods recipient'

Note 824906 - Partner detail: "Other addresses" button

<b>Other related links -></b>

Do let me know.

Regards

- Atul

Former Member
0 Kudos

Hi,

thanks for your reply.

@Reddy:

The plants are replicated from R/3 by report "BBP_LOCATIONS_GET_ALL ".

@Atul

I have checked all settings and entries again, but I can´t find any issue. Here are the entries of tables V_T160EX and V_T160PR.

V_T160EX:

Mat. Group = empty

Purch.Group = empty

Profil = 01

Manuel = X

V_T160PR:

Profil = 01

Log. Sys. = B72100 (SRM)

Any other ideas?

Regards

Axel

Former Member
0 Kudos

Hi Axel

I have a problem when transfer extternal requirement from R/3 to, please

In _T160PR:

Profil = 01

Log. Sys. = B72100 (SRM) you used a logical system used in define logical system ou here we can use a RFC created for plan driven?

Thanks

Nilson

Former Member
0 Kudos

Hi Nilson,

could you please explain your problem more in detail, because I´m not sure if I understood your question correctly.

The value "B72100" in View V_T160PR is the RFC-Destination of the SRM System, maintained in TX SM59.

Regards

Axel