ECC PO not created for direct material

[Former Member]

Dear experts,

SRM 7.0, ECC 6.0 Classic scenario

Trying to order a direct material from SRM (internal goods/services)...I am assigning a vendor via an info record and a local SRM PO has been created but the PO has not been replicated to ECC.

My number range settings are as shown

In SRM: 03 660000000 669999999 (ECDP has internal number range as 03, so gave 03 here)

In ECC: 66 660000000 669999999 check box on external

and defined transaction type as ECDP with following setting

ECDP Direct PO from SRM 10 45(int) 66(ext)

Is this correct? If Yes what could be the issue as no ECC PO is created from the direct material SC?

Thanks

[ricardo_cavedini · Accepted solution]

Hello,

You mentioned that you are using direct material with classic scenario.

Technically, Classic scenario can not be adopted for Direct Materials.

One of the reasons is because only local sources of supply can be used for direct materials. Driving document will be local as standard design.

This is also explained at the following Consulting Note:

495484: Direct material: Sources of supply from the back end

This note is valid as of BBPCRM 300 and the system behaviour didn't change.

Regards,

Ricardo

[Former Member · Accepted solution]

Hey Ricardo,

Thanks for the reply.

I went through the note. But it says if you choose "Procurement as direct material" for the item, the sources of supply previously determined from the back end system disappear.

Nothing of this sort happens in my case...the info record very much stays as the SoS and a local SRM PO has been created which ought to have been replicated to ECC.

Can you verify my number ranges described above?

Also my SRM PO has the following status in BBP_PD

HEADER I1009 Held

HEADER I1021 Created

HEADER I1039 Incomplete

Thanks

Edited by: sivakumar lakshminarayanan on Jun 27, 2011 3:34 PM

[velayutham_augustheesan2 · Accepted solution]

have a look at this thread. . This is similar to your issue.

For direct material, the standard config will create a PO in SRM and to change this behavior you have to find a BADI as discussed in the thread.

regards

velu

[Former Member · Accepted solution]

Thanks for your reply.

I am aware of BADI you mentioned and that std config will create a local SRM PO. I am not want to change this behaviour but only to replicate the SRM PO to ECC. The BADI mentioned by you will create a leading ECC PO whereas I am fine with a leading SRM PO which is copied to ECC.

Thanks

[velayutham_augustheesan2 · Accepted solution]

in that case, i think you may have to configure extended classic.

regds

velu

[Former Member · Accepted solution]

I dont think so,

I have read posts by people on forums where they have said that this is std system behaviour and in case of direct procurement, classic system automatically behaves as if extended classic.

Do read Ramkakrishna Potluri's reply on this forum.

Thanks

Edited by: sivakumar lakshminarayanan on Jun 28, 2011 12:31 PM

[velayutham_augustheesan2 · Accepted solution]

refer to this link: and can u check the PO in SRM has account assignment details.

regards

velu

[Former Member]

As I explained in your other thread, it seems your SC does not have Fixed vendor and hence a PR is getting created instead of PO. Try sending this SC to sourcing and create a Po from SOCO by assigning a vendor.

Regards,

Jagadish

[Former Member]

Jagdish,

I mentioned it in that thread also and I have mentioned it here as well: "I am assigning a vendor via an info record and a local SRM PO has been created but the PO has not been replicated to ECC. " which means it is a fixed vendor and the price is also picked from the info record.

Are there issues with number range settings?

[Former Member]

Do you see any error in RZ20? Try activating Sourcing for this material and create PO from SOCO. Check if PO creates from there and update.

Regards,

Jagadish