Enable multiple PO numberranges to support SRM Classic implementation.

[former_member533535]

Hi Experts,

We have implemented SRM 7.0 Classic Implimentation.

We currently have one PO number range which is assigned to one PO document type to support North America and Canada region.

We are planning to go for roll-out for Latin America, Europe and Asia pacific.

Here the client requirement is that they need to have one PO numberrange per Company.

Can any one suggest what ios the BADI that can be used to achieve this. Backend ECC we can have as many PO document type but how can this be managed in SRM.

Thanks in advance please help me with BADI or any other means this can be achieved.

Regards,

B.N.Karthikeyan

[laurent_burtaire · Accepted solution]

Hello,

A SRM document type has one number range (internal or external, depending on technical sceanrio).

So, if you have several number ranges, you must have several document types.

Make corresponding customizing in R/3 and SRM for PO document type, then for each organizational unit being a company ( 'Responsability' tab), assign correct value for attribute 'BSA' (Backend document type).

Regards.

Laurent.

[former_member533535 · Accepted solution]

Hi,

We are in Classic scenario implementation and hence the standard SRM does not have capability to manage multiple number ranges for PO.

My question can this be possible to have multiple PO number ranges in Classic scenario based on the company code of the user given in the user attribute.

SAP MM side I dont have any problem. Only thing is during transfer process how do we achieve selecting different number ranges if I maintain multiple numer ranges in SRM in the maintain intervals.

Do we have any BADI to achive this expectation. As the customising does not allow us to maintain differnt Number ranges for same logical backend ECC system.

Regards,

B.N.Karthikeyan

Edited by: B.N. Karthikeyan on May 17, 2011 9:25 AM

[laurent_burtaire · Accepted solution]

Hello,

Sorry, i did not check SRM customizing for number range per backend system for follow-on documents...

As it is not possible (and don't know if any BAdI could answer to your requirement), you could use same number range for PO and make difference between company codes PO using a specific document type for each one instead of number range...

Regards.

Laurent.

[former_member206968 · Accepted solution]

Hi Karthik,

Hope you are doing well.

You can try using badi - bbp_doc_change. In shopping cart, you can change the fields be_doc_type and be_object_id to change the backend po document type and number based on your criteria.

Regards,

Sanjeev

[former_member533535 · Accepted solution]

Hi Sanjeev,

Thanks for the reply.

Will try to test the BADI "BBP_DOC_CHANGE" and update you if we can achieve if we can able to change the Number range for PO that would get created in ECC backend.

Regards,

B.N.Karthikeyan.

[former_member533535]

Hi Sanjeev,

We have tested by updating the code in the BADI "BBP_DOC_CHANGE". We still could not able to achieve this the reason is on Approval of the SC the BADI is getting called and the information such as backend object id is empty and we could not see what is the PO number bean proposed on approval of catalog SC.

The fields be_doc_type and be_object_id to change is empty when the BADI is called on complete approval of the SC and hence we could not able to use this BADI. Can you propose any other option or when this information such as fields be_doc_type and be_object_id to change will be proposed by SRM.

Regards,

B.N.Karthikeyan.

[former_member206968]

Hi Karthik,

This could have been simpler solution if it worked.

Another suggestion: Try creating a dummy logical system and create an RFC to the same backend system. Using badi bbp_determine_logsys you can change the target logical system to this dummy logical system. Based on this dummy logical system, you can determine new number ranges through customizing. Also you can maintain new document type in attribute BSA for this logical system.

You would also need to point the plant, vendor, company code, purchasing groups etc. point to this logical system so that system can take all the values. Then it should work.

Regards,

Sanjeev

[Former Member]

Karthik,

Try BADI BBP_BS_GROUP_BE and in that use method GET_NUMBER_OR_RANGE to determine separate number ranges for PO. bBasically you need to first group POs ,for each co. code or what ever logic you have, and then assign number ranges for each group.

Hope this will help you.

Regards,

Jagadish