ECC - SRM - External Procurement Scenario

[Former Member]

Hi SRM Gurus,

I have to transfer Purchase requisitions from SAP ECC 6.0 to SAP SRM 5.0

the account assignment of these Purchase requisitions is "U", but it makes the purchase requisitions not to be written in the table EPRTRANS, in addiction there are no BAdIs or custome exit available in which I can insert some code to resolve the problem, the only one Customer Exit (BBPK0001) is not called if account assigment category on PR is Unknown.

Do you have any ideas to help us?

TX in advance.

Bye

[Former Member · Accepted solution]

Hi

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

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

Note 799253 Transferred ext. reqmnts cannot be transferred after change

Do let me know.

Regards

- Atul

[Former Member · Accepted solution]

Hi Atul,

I saw SAP OSS notes.

The first one is exactly the opposite I was looking for.

I want to transfer to SRM also PRs w/o account assignment. This is tha case that user asks to the buyer to create a contract.

Tx

Marco

[Former Member · Accepted solution]

Hi Marco,

you can transfer Requirement w/o Account Assignment to SRM.

From the Sourcing Cockpit it is possible to create a contract as follow on

document. Issue will be, that w/o Account Assignment the SC cannot be

closed. For this extended classic scenario is pre requisite. Maybe it is suitable

to work with a specific ECC doc type to separate the cases you are looking for.

Cheers,

Claudia

[Former Member · Accepted solution]

Hi Claudia,

my problem is that is impossible to transfer Requirement w/o Account Assignment to SRM. I debugged the standard code and is uccount assignment is <i>Unknown</i> the PR is not insert into table EPRTRANS. Moreover the only one customer exit is not called if uccount assignment is <i>Unknown</i>, so I cannot transfer PR w/o account.

You typed <i>"you can transfer Requirement w/o Account Assignment to SRM."</i> how is it possible?

TX

Marco

[Former Member · Accepted solution]

Hi Marco,

it is working, as I implemented several systems using reqs without account

assignment. There is a difference between "unknown" and "no" account

assignment. A usual req from MRP does not have any account assignment.

It is empty. This is the case I am talking about. The case for "U" = unknown

is not supported by standard, like Yann answered. Sorry, but that's the case.

There are several restrictions for the PDP scenario - have a look into 505030.

Cheers,

Claudia

[Former Member · Accepted solution]

Hi Claudia,

thanks for your replies.

I understand that I would to do is not a sap standard scenario, but I think I found the right way to do it, when I'll finish to implement this scenario I explain you how.

Do you know if for PDS is mandatory extended classic scenario?

TX for all.

Bye

Marco

[Former Member · Accepted solution]

Hi

PDS (plan Driven scenario ) is not mandatory.. It depends on the requirements.

Plan-Driven Procurement

http://help.sap.com/saphelp_srm50/helpdata/en/76/bd004261e1da6fe10000000a1550b0/frameset.htm

Plan-Driven Procurement with Plant Maintenance

http://help.sap.com/saphelp_srm50/helpdata/en/99/8afc524b07574fa215b32f1da9ddd4/frameset.htm

Plan-Driven Procurement (standalone)

http://help.sap.com/saphelp_srm50/helpdata/en/29/5f8f41a04aa809e10000000a155106/frameset.htm

Plan-Driven Procurement with Supplier Integration

http://help.sap.com/saphelp_srm50/helpdata/en/23/63b2e2f1814fe29f6674eba1a9ee9e/frameset.htm

Hope this will help.

Regards

- Atul

[Former Member · Accepted solution]

Hi Marco,

if you want to implement the full cycle - transfer REQ and Source it in SRM -

extended classic scenario is prerequisite by standard, also mentioned in docu.

Of course you can influence the standard, by adding your one logic and modi-

fication into the process.

Cheers,

Claudia

[Former Member]

Hi,

Did you manage to transfer the PR wit account assignment Unknown to SRM?

Please can you explain how?

Thanks

Ezequiel

[yann_bouillut]

Hi,

This is standard behaviour.

Kind regards,

Yann

[Former Member]

Hi,

I know that it's a standard behaviour, but is a bug because if I want to convert the SC (created automatically on SRM from the PR created on ECC) into a contract, i don't know yet the account assignment that I will use for PO referring to the contract.

So the process flow was:

1) user create a PR in ECC with Unknown account assignment

2) PR is transfered to SRM in sourcing cockpit as a SC

3) buyer convert SC into a Contract with Unknown account assignment

4) Contract was distributed to ECC

5) User create PO with reference to the contract with or without account assignment (no Unknown)

I hope I explain better what is my problem and someone could help me.

Thank you in advance.

Bye

[Former Member]

Hi Marco,

4) Contract was distributed to ECC

<i> Can you please explain that, Can we distrbute purchase contracts of SRM to ECC other than GOA.......</i>

3) buyer convert SC into a Contract with Unknown account assignment

<i>Can we create GOA as a follow on document of external requirement</i>

.