cancel
Showing results for 
Search instead for 
Did you mean: 

conditions for PO approvals in R/3 system

Former Member
0 Kudos

Hi

We are on SRM 4.0 classic scenario and backend as ECC5.0

We have a requirement where PO approval is to be done in backend R/3 system, only for POs which are created from SRM sourcing cockpit and R/3 manual POs. POs that are created from catalog based shopping carts need not undergo PO approval in backend system.

Note : All shopping carts will be approved in SRM workflow approval process before creating follow-on doc in backend system.

My questions

1. How the workflow will recognise the PO from sourcing (SRM) and manual PO created in backend R/3(not through SRM). Because we want PO workflow to be triggered only in R/3 system for these POs.

2.Is the workflow development same for SRM and R/3 system or any difference is there. I mean in R/3 also do we have n step approval BADI?

Please give me your suggestions on how to proceed on the above.

Thanks

Jagdish

Accepted Solutions (1)

Accepted Solutions (1)

yann_bouillut
Active Contributor
0 Kudos

Hi Jagdish,

1- You can use document type to distinguish SRM PO from R/3 PO.

Kind regards

Yann

Former Member
0 Kudos

Hi Yann

Thanks a lot for your quick response.

As you said we can distinguish SRM PO and R/3 PO.

But If I want to distinguish PO from SRM sourcing and PO from SRM catalog(without going to sourcing, how to distinguish them.

Thanks

Jagdish

yann_bouillut
Active Contributor
0 Kudos

Hi Jagdish,

You can transfer the catalogue ID in the R/3 PO so that you can distinguish them.

Kind regards,

Yann

Former Member
0 Kudos

Hi Yann

That is interesting....

Can you tell me how to transfer the catalog ID to R/3 PO.

I am not a technical person. So please explain me in detail steps. That would help me a lot.

Thanks

Jagdish

yann_bouillut
Active Contributor
0 Kudos

Hi Jagdish

I took the hypothesis that you use extended classic scenario :

Implement BBP_ECS_PO_OUT_BADI. This BADI is active when the Extended Classic Scenario is switched on, while PO data is transferred from EBP to R3.

Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field (that's an example) can be used to store this information. In this BADI all items are identified and their tracking number field is populated with your catalogue ID.

You can take this a starting point.

Hope this helps,

Kind regards,

Yann

PS : Please do not forget to reward )

Former Member
0 Kudos

Hi Yann

We are using Classic scenario.

Is this solution works for classic scenario too?

What is the BADI that is used for classic scenario?

Full points are rewarded....!!!!

Thanks

Jagdish

yann_bouillut
Active Contributor
0 Kudos

Hi Jagdish,

Yes : use BBP_CREATE_PO_BACK badi for classic scenario.

Thanks

Regards,

Yann

Former Member
0 Kudos

Hi Yann

Thanks a lot

Do we need to change any config if we use BADI for classic scenario.

Because currently we are not using BADI for creating POs in backend.

Regards

Jagdish

yann_bouillut
Active Contributor
0 Kudos

Hi Jagdish,

No.

Just activate and code the badi to meet your requirement.

Kind regards,

Yann

Answers (0)