on 11-02-2011 5:32 PM
Hi All,
We have an issue where in we have maintained a condition record with the access as "Purchase Doc type (NB) and Purchase Organization(XXXX):" pointing towards a "LS" partner function (ALE) and "4"
We have also maintained Partner configuration correctly. The issue which happens only in Production and not in TEst systems which is " only for ONE VENDOR the output is not getting proposed and for the other vendors it is getting proposed correctly. We also have a requirement attached to the Output and we do not have any vendor specific logic.
We also checked /Compared both the test and production system on Output Configuration as well as master data for VEndor and Info records and they seem to be ok.
Does any one faced a similar situation why an Output would not propose just for one specific vendor?
Would appreciate if any one can reply asap.
Thanks,
Within the PO. Goto messages, then Goto determination analysis. Here you can determine why your output is not initiated. This should show the procedure determined and all output condition types within procedure. When clicking on the output condition, you can navigate to the key used to look up the condition, or this will tell you if the requirement failed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
have you checked the partner profile?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then check with the requirement you are using bd64 is distribution model.
Check with ur output type, requirement and output determination. ale service comes only in picture partner profile with outbound parameters.
have u done the correct entries under message control in outbound parameters.
thanks
Aman
User | Count |
---|---|
100 | |
11 | |
11 | |
6 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.