on 01-18-2007 3:29 AM
For BP role "Port of Entry" we source it from the Ship-to relationship.
In the partner access sequence we have source CRM_PARTNER_C Business Partner Relationships that looks to the ship-to partner function.
If the ship-to has a "Port of Entry" relationship then this works great.
If the ship-to has no "Port of Entry" relationship, then the Ship-to is coming into the order as the Port of Entry.
My goal is to have no Port of Entry partner in the order if the relationship does not exist. This should be easy but i don't see what I am missing.
The answer is to block the port of entry in defining partner functions in the IMG
Block Partner from Performing Function for Himself
Defines whether the source partner is added during partner determination for the resulting quantity. If the source does not provide a standard partner, the source partner himself becomes the standard partner.
Use
If you leave this field unmarked, the source partner is copied with the resulting quantity during partner determination.
If you mark this field, the source partner is not copied with the resulting quantity.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i think you have to first remove the second access responsible for getting ship-to party, then in the partner determination procedure you can make use of maximum and minimum entries for making it optional. it is similar to the partners like Contact persons.
let me know if this helped you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is only one step in the access sequence.
I have been playing with the Mapping/Definition in the access
- Partner function in source
- Func cat in source
But that isn't limiting the access to only pull in the port of entry when one exist on the ship-to. I'm still sure there is a configuration answer but running out of time before coding an enhancement.
User | Count |
---|---|
2 | |
1 | |
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.