on 05-24-2009 1:07 PM
Hi Experts,
We are implementing SRM 5.0 classic deployment PDP scenario with Backend ECC 5.0. In the backend ECC there are three types of Purchase Requisition and Purchase Order document types - NB, ABC and XYZ; all with different number ranges
The requirement is as given below:
In the PDP scenario, when we create a PR in the backend ECC, transfer it to SRM and after sourcing create a PO in backend ECC (Classic Scenario). The document type of the PO in ECC should be same as the PR (which was created in ECC and transferred to SRM). All the document types should have different number ranges in the ECC system.
For e.g.
If we create a PR in backend ECC u201CType NBu201D and transfer it to SRM. After sourcing in SRM when we create a backend PO, the PO type should be picked up as u201CNBu201D with number range u2013 56XXXXXX.
Or if we create a PR in backend ECC u201CType ABCu201D and transfer it to SRM. After sourcing in SRM when we create a backend PO, the PO type should be picked up as u201CABCu201D with number range u2013 57XXXXXX
We approached this scenario the following way:
1. Created the different document types in ECC and SRM for PO and PR. Assigned a single document type to attribute BSA in each Purchasing Group. The PR was then processed by the buyer in Purchasing Group with the same backend document type as PR.
2.In ECC, PR document types were mapped with respective PO document types as follow-on documents.
However, we still find that PO gets created in ECC with document type that does not match the requirement. Please let me know if I am missing out something or is there another way to approach this issue.
Regards,
SKKN
1.Define Number Ranges for Shopping Carts and Follow-on Docume
2.Determine Number Ranges and Grouping in Backend Documents
3.The Business Add-In BBP_BS_GROUP_BE offers the following options
You can, independent of the standard, use the method GROUP_RQ to create a separate grouping for purchase requisitions.
In the standard, the system creates only one purchase requisition in the backend for all purchase requisitions with the same backend document type . If the document types are different, the standard creates a separate purchase requisition for each document type.
In the case of purchase orders , the grouping is made by the following fields in this order:
Vendor
Purchasing organization
Purchasing group
Contract
Document type
Item
Company code
In the second step, you can use the method GROUP_PO to create further groupings of the grouped items according criteria you have selected yourself and that are not on header level.
sc converted into po with help of organisation structure and you must check what document type you maintained in your organisation structure. i believe you can write a custome logic which document type should pick ..while create a PO since your your PR converted into external requirement i.e SC and this sc can be converted into PO if it has appropriate document type.
br
muthu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Muthu,
Thanks for your suggestion and the link. Out technical guys are analyzing the feasibility of that solution for our scenario. In the meanwhile can you tell me, if BAPI_PO_CREATE1 in ECC can be used for this issue to create a PO with documents type corresponding to PR documents type?
Thanks
SKKN
Hi
You can use the badi BBP_CREATE_BE_PO in SRM to modify the documnet type as per you requirement.
Assign correct number ranges in the SRM and ECC for the documnet type intended and that should work for you.
Also good to have all the backend documnet type defined in the org structure.
Cheers
Iftekhar Alam
Hi guys,
Any thoughts on this issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.