direct material and ECS

[Former Member]

Hi all,

This relates to <b>direct procurement</b>(classic scen).

I have created local Porgs and PGrps and also backend Porgs and PGrps.Proper categories have been assigned and PO is also created.

My question is:PO is created in SRM system with the local POrg and PGrp.When PO is replicating to back end.....

..

a.]how will the system know which POrg and PGrp is to be picked for back end?

b.]Say,we have 2 POrgs and 5 PGrps....and PO created belongs to one POrg and a PGrp.Do we have to create all POrgs and PGrps in the organization and link it to backend in function tab?

c.]Is there a BADI to be used for mapping?Which one?

d.]Any changes that are to be made in PO should be made in SRM PO.Now how will those changes reflect to the already replicated PO in R/3?Any background job that does the changes?

<b>Extended classic scenario</b>

Once PO is created and when it has to be replicated to back-end(SAME QUESTIONS)

a.]how will the system know which POrg and PGrp is to be picked for back end?

b.]Say,we have 2 POrgs and 5 PGrps...do we have to create all POrgs and PGrps in the organization and link it to backend in function tab?

c.]Is there a BADI to be used for mapping?which one?

d.]Any changes that are to be made in PO should be made in SRM PO.Now how will those changes reflect to the already replicated PO in R/3?Any background job that does the changes?

Please share your views.Points will be awarded.

Many thanks

Trey

[Former Member]

Hi

Which sRM version have you implemented ? Which Scenario are you using ?

Here are the possible answers

<u>Classic Scenario -></u>

a) Purchasing organi-zation is determined based on the plant.

b) Maintain the same POrg as well as the PGrps data using configuartion, both in SRM as well as the R/3 system in order to miantian consistency.

c) I guess, BADI is not required here.

d) Execute reports - BBP_GET_STATUS_2 AND CLEAN_REQREQ_UP. Schedule these report as Jobs using SM36 transaction, to need to be scheduled in background for classic / extended classic scenario.

<u>Extended Classic Scenario -></u>

a) The Leading PO created in SRM will contain all the Porg / Pgrp details, which will be replicated to R/3 PO.

b) Maintain the same POrg as well as the PGrps data using configuartion, both in SRM as well as the R/3 system in order to miantian consistency.

c) Try the following BADIs using Se18 Transaction.

BBP_PGRP_ASSIGN_BADI                 EBP Purchasing Documents: Assign Purchasing Group(s)    

BBP_PGRP_FIND                                        Shopping Cart: Determine Responsible Purchasing Group(s)

d) Execute reports - BBP_GET_STATUS_2 AND CLEAN_REQREQ_UP. Schedule these report as Jobs using SM36 transaction, to need to be scheduled in background for classic / extended classic scenario.

<u>Please understand the details of direct procurment as well by referring to the following links -></u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/d9/12f33901fe874ce10000000a114084/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/b7/15d4396898042fe10000000a114084/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/6a/4b9e3b891da20ee10000000a114084/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/38/39d03bcf36d137e10000000a114084/frameset.htm</b>;

Hope this will help.

Please reward suitable points, incase it suits your requirements.

Regards

- Atul

[Former Member]

Hi,

Thanks for all your inputs,but i am confused.I may not have explained the situation properly or my concept is unclear.

In direct procurement,classic scneario(SRM 4.0,R/3 4.);

My understanding:

For SRM PO creation, it has to have a local POrg/Grp assigned to it.(function tab...just select the check box...but no value).I also have back end POrg/PGrp linked in the organization plan.

Now when this PO is to be copied to R/3:

-Does local POrg/Grp transfer to R/3 in the PO?

OR

-Do you change the local POrg/Grp to a back-end POrg/Grp? How?

Ramki:how can we use back-end POrg and Pgrp while creating SRM PO?SRM PO needs local POrg and Grp,right?Help...

Trey

[Former Member]

Hi

<u>That's why it's recommeded to maintain the same Configuration data both at R/3 side and SRM side.

The same data will be used (validated from SRM) where the R/3 PO will get ultimately created. There it's recommended to replicate atleast the required R/3 configuration data in SRM standard tables.</u>

<i><b>Q ->How can we use back-end POrg and Pgrp while creating SRM PO?SRM PO needs local POrg and Grp,right?</b></i>

<u>Answer -> Use <b>BBP_CREATE_PO_BACK / BBP_CREATE_PO_BACK_NEW </b> BADI and using SE19 Transaction, create a customer implementation of the same and you can over-write the Local Porg / Local PGrp (SRM data -> to the required R/3 configuration P Org/ P Grp data inside the BADI call, before the R/3 back-end document gets created after calling the BAPI - BAPI_PO_CREATE1 / BAPI_PO_CREATE depending on your System version.</u>

<b>PO data is copied over from this BADI call.</b>

<u>For Local P Org / Local P Grp data, we can overwrite the values in BBP_DOC_CHANGE_BADI (in SRM), where we have all the document data avaiable with us.</u>

Let me know incase you face any issues.

Hope this will help.

Please reward suitable points, incase it suits your requirements.

Regards

- Atul

[Ramki]

Hi Try

You can use Backend p-org and P-grp also in SRM POs.

If you use local p.org and P.grp, then they need to be changed to backend p.grp as mentioned in my previous post.

Best regards

Ramki

[Ramki]

Hi

a) Backend Purch.grp/org is determined by number of ways:

- Maintain a purchasing group for parameter EKG in backend RFC user parameters in transaction SU01. Purchasing organi-zation is determined based on the plant.

- Use backend purch.grp/org while creating SRM PO

- Use User Exits in BAPI in R/3. Set the purchasing group in the user exit in BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003) and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004).

b) If you want the SRM POs in the backend to be created with different purchasing groups and purchasing organizations, suggest you to create them in SRM also and use them while creating PO.

c) see (a) above

Best regards

Ramki

[Former Member]

Hi,

c.]Is there a BADI to be used for mapping?Which one?

Try BADI "BBP_PGRP_ASSIGN_BADI".

d.]Any changes that are to be made in PO should be made in SRM PO.Now how will those changes reflect to the already replicated PO in R/3?Any background job that does the changes?

Jobs BBP_GET_STATUS_2 AND CLEAN_REQREQ_UP need to be scheduled in background for classic scenario in addition to your distribution model.

HTH.

BR,

Disha.

Pls reward points for useful answers.