on 04-05-2016 4:58 PM
We have a very unusual case, which we are having trouble fixing. Our stock transfer orders are using a FI payment partner function (FIDEB - customer) as the ship-to customer. Here are the steps we went through and when the issue started happening.
Has anyone run up against such a case for the implementation of OSS Note 676301 where the wrong partner function is used for the ship-to customer on the STO?
False alarm. There is a corrupt configuration table in the integration environment. We are not sure how it happened, but we were able to fix it. We don't think it is an issue with the OSS Note.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike,
One immediate thought - and perhaps too obvious - is that you mapped the partner function at both Logical System and LSG levels, and then only "de-mapped" one of them. Could that be the reason?
Regards,
Dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
3 | |
1 | |
1 | |
1 | |
1 | |
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.