on 07-24-2009 12:55 PM
Hi,
SRM 3.0 /EBP 4.0 R/3 4.6C
As we are on Extended classic scenario, we are not utilizing the functionality of Purchase requsition in R/3
Can this functionality be used for some other purpose now?
Like , I want to populate some requirement (coming from out side R/3 via interface) as a Purchase requistion. and then I will post these requirement as an IDOC to EBP/SRM which will create a shopping cart in EBP/SRM (rest of the process is normal)
Now can I use this Purchase requisition funcitonality in R/3 as it is, or is it better to copy and customize.
If I can use as it is, what are the precautions i must take?
your inputs highly appreciated,
regards,
Mahesh
Hello Mahesh,
You mean to say that an external system generates a PR and through Interface/Idocs it is posted in R/3 as Purchase Requisition?
Yes,this is always possible...and many cutomers use this,who still want to continue with their legacy systems to generate requirement.
ofcourse these PR's can be tarnsfrred to EBP for generating a SC and the follown on process.
But my sggestion is use a seperate tracking No: to tarck the requirement coming from external system and those generated in EBP.(Good for differentating)
hope this helps
Arshad
Edited by: arshad ahmed on Jul 24, 2009 4:50 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.