Partner Ship-to address not found.

[Former Member]

Hi all,

We are using the plan driven procurement to push our requirements using the RFC user.

When running the prgm its getting stuck in the ques with a log on SRM saying

PARTNER SHIP_TO ADDRESS NOT FOUND..

Shopping Cart INCM (Incomplete)..

We have assigned the Del-addr attribute for all the users including the RFC user in the entry channel..

Any inputs..

Regards

Manoj A.

[Former Member]

Hi all,

We were configuring Standard PDP scenario, which doesn't need any BADI to be coded. The Partner is determined in the SRM based on the Plant.

SAP have made changes in the SRM 5.0 for partner determination for PDP.

OSS note 801133 resolves the problem from backend system.

Warm regards, Ajay

[Former Member]

Hi Manoj,

Have you replicated R/3 plants with job BBP_LOCATIONS_GET_FROM_SYSTEM or BBP_LOCATIONS_GET_ALL or BBP_LOCATIONS_GET_SELECTED?

The PR item delivery address is sent by R/3 in the form of the Ship To partner function.

R/3 will determine the PR item delivery address in the followinfg priority sequence:

- take the item individual address number (EBAN-ADRNR)

- take the item assigned address number (EBAN-ADRN2)

- take storage location address (EBAN-LGORT)

You can debug R/3 PR transfer (BBP_EXTREQ_TRANSFER) to check what is sending your R/3 system.

Rgds

Christophe

PS: please reward points for helpfull answers

[Former Member]

Yes we have replicated the plants. But still the error persits. We are using ECC 5.0 (Basis 640) and SRM 5.0

[Former Member]

Hi Chris,

In the plan driven procurement we observed that the line item 'deilivery address' is not being propagated to the SC item level out of the box.

We were looking at the Plan driven badi BBP_BADI_EXTREQ_OUT on R/3 to see if we could pass this but did not help. looked like it needed a considerable amount of development. but we were more interested on a out of the box solution.

The EBAN_ADRNR has no value for this line item.

This is a similar problem while trnasfering the "Ship to" from the bidding over to the PO delivery addr.

Looks like the PO delivery address is only pulled out by the Plant which is a default valued from R/3.

i would really appreciate if you could throw some more inputs at this.

Regards

Manoj A.

[Former Member]

Hi Harish,

When we ran into this problem as far as i remember we tried repairing the RFC users using Users_gen. (repair 2)/ or delete the EBP user and BP and recreate him again.

try this out and see if it works.

then we got out of this using the trusted connection from R/3 to SRM and this will not create the SC using the RFC user anymore .. and for this the sy-unam is the user running the prog. to push the req from R/3.. but hten u have to make sure that this user is available in the org structure.

Rgds

Manoj A.

[Former Member]

Manoj,

The PR item delivery address is sent by R/3 in the form of the Ship To partner function.

R/3 will determine the PR item delivery address in the following priority sequence:

- take the item individual address number (EBAN-ADRNR)

- take the item assigned address number (EBAN-ADRN2)

- take storage location address (EBAN-LGORT)

In your case, as you said EBAN-ADRNR is empty, then it could use the storage location address.

But if you don't have any storage loc assigned as well, then R/3 has no ship to partner to send to SRM.

I don't think populating ship to party in BBP_BADI_EXTREQ_OUT will require this considerable amount of work.

Look at BBP_EXTREQ_TRANSFER: you will see how PR partners are sent to SRM. For delivery address, this is quite simple.

Rgds

Christophe

PS: please reward points for helpfull answers

[Former Member]

I forgot to propose another option:

you can use BADI CHANGE in SRM to complete the incoming SC, and take the RFC channel user's default delivery address.

Of course, if you don't maintain any delivery address in R/3 PR.

Rgds

Christophe

[Former Member]

Hi Manoj,

How did you resolve your problem ? We are having same problem for PDP

Rgds, Ajay