Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MR (Package) Incoming Invoices
IMG Activity
ID | OLMR_T169BP | Define Partner Role as Allowed Payee |
Transaction Code | S_XDE_56000010 | (empty) |
Created on | 20070227 | |
Customizing Attributes | OLMR_T169BP | Define Partner Role as Allowed Payee |
Customizing Activity | OLMR_T169BP | Define Partner Role as Allowed Payee |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OLMR_T169BP |
Use
In this IMG activity, you can define the partner roles that are allowed payees for each client.
During invoice verification, you can use Business Add-In (BAdI) BAdI: Check Partner Data from Purchase Order to check on the basis of these entries whether the invoicing party is authorized to receive payment. If the partner role that is saved with the invoicing party in the purchase order is not an allowed payee, you can get the system to issue a message, depending on the settings in IMG activity Define Attributes of System Messages.
If you do not use customer-specific logic for checking the partner data with the above BAdI, the system checks the invoicing party according to the following logic:
- First, the system checks whether the invoicing party exists in the header data of the referenced purchase order. If the partner role is not entered on the Partners tab page in the purchase order header, you can get the system to issue a warning or error message.
- If the invoicing party is entered in the partner data of the purchase order, the system checks whether one of the roles defined for the invoicing party in this IMG activity is defined such that it authorizes to receive payment. If none of the roles assigned to the invoicing party is authorized to receive payment, you can get the system to issue a warning or error message.
Requirements
Standard settings
The vendor is predefined as an allowed payee. You cannot change or delete this entry.
Activities
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OLMR_T169BP | 0 | HLA0001544 | Logistics Invoice Verification |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
T169BP | S - Table (with text table) | SM30 |
History
Last changed by/on | SAP | 20080319 |
SAP Release Created in | 600 |