Is it that i will switch the flag no_messaging = c_on to Space when makes call to "CALL FUNCTION 'BBP_PO_INBOUND' DESTINATION lv_destination". Once i do this it will pick the config from R/3 for Output or does it require more config explicitly in R/3 and SRM.
If yes, Is there any negative effect downside.
Because, i read OSS Note that says to prevent Output from R/3, OSS Solution is to "no_messaging = c_on". It means SAP does not allow Output from R/3 for ECS POs. If we change this, SAP will not support I assume for any side effects.
Would appreciate if you have any doc that outlines in brief how you did. My email ID is rjayasankar@yahoo.com.
I am in design stage on a proposal. I certainly reward points when close this thread.
For many clients implementing SRM in extended classic scenario, the point is that they'll keep some PO created directly in R/3, so the question is: How and where to manage the PO outputs ?
For this point my advice is to manage the PO output in R/3, with no local output in SRM. This way all POs will be outputed in R/3 with the same form.
Now, if your need is to have your SRM POs edited only in SRM, and not in R/3, you then just have to customize your R/3 output, not to output the POs coming from SRM (based on the document type).
I am repeating my understanding based on your reply.
1. Some PO created directly in R/3. Using ECS BADI, You mean there is no leading PO. This works like Classic. I will manage the output from R/3. I am ok here.
2. My Questions is on the other case.
My leading PO is in SRM typical ECS scenario. But, still i want the output from R/3, this is my requirement.
Is it supported out of the box.
If it not, is it possible by Custom.
If it is custom, is that the place i identified in my earlier reply or any more developments/configs required both in SRM and R/3.
I read a OSS Note 793786 solution to prevent the Output from R/3 for ECS PO. This means SAP is not allowing. Even after, i try to do by custom, want to foresee what other i will have.
Based on your replies 2, 2.1 and 2.2, I should not be having any problem to output from R/3 for ECS PO. I had understood as This is out of the box function with bit of configurations both SRM and R/3, does not require any developments.
I have created a consulting note 883693 on this issue. And released it as a Pilot Release for one customer for his specific requirement. This note gives you clear information about the output determination in R/3 in case of extended classic scenario.
Not sure if you're still around but I'll give it a try anyway.
OSS note 883693 describes how to activate the printing from ECC in a way how we have also implemented it. However, the PO in ECC is obviously still closed for changes which makes it impossible to manually create output messages for the copy PO.
Is there a way to activate that posibility without having the whole PO open for change in ECC?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.