(S4)PACG 200 SP04
Background
In certain business scenarios (e.g. ISU) special partner roles set on Business Partners can be treated similarly to customer/vendor roles. It should be possible to send to SAP FSM Business Partners who are not assigned customer/vendor partner roles but any, customer-specific one.
Until FSM Cloud Connector add-on 200 SP03 version (included), only if a BP was assigned customer-/vendor-related partner functions (e.g. FLCU01, FLVN01, see tables KNA1, LFA1) could it be sent to FSM as a Business Partner of type Customer/Supplier.
New solution
Business Partner can now be sent to SAP FSM as a customer or vendor based on any partner role.
If a Business Partner is assigned a partner role entered in transaction /PACG/ECM_BPASGN - BP role assignment and checked as customer/vendor, it can be sent to SAP FSM as such.
For partner roles which do not have customer/vendor data (cannot be reached with transactions XD03, XK03; no entries in tables KNA1/LFA1), Business Partner master data will be used instead (see transaction BP, tables BUT00). This data will be sent to FSM as customer/supplier properties. The BP’s ID will be used as well.
Prerequisites and remarks
Please keep in mind that customer/vendor may need badi implementation to fill relevant, yet missing data on client side.
The ‘BP used’ field in transaction /PACG/ECM_CPROP is a prerequisite for this functionality. On S4 systems it is set by default and cannot be disabled.
The setup program (/PACG/ECM_SETUP) should be executed before usage
If the field above is enabled, Business Partners exist in SAP and one of their (non-customer/non-vendor) roles is maintained in transaction /PACG/ECM_BPASGN - BP role assignment as customers/vendors, then object assignment check (sales area/company code/no object) is not performed. These BPs will be sent to FSM regardless of sales area/company code assignment. However, at least one ‘sales area’, 'company code' or ‘no object assignment’ (recommended) entry must exist for the company to which a customer should be sent. See transaction /PACG/ECM_EOAS - Object Assignment.
Attachment handling is not yet supported for this solution.
The logic is outbound-oriented, customer creation/update in FSM are not supported.
BP ID used as customer ID should be adjusted in outbound service call idocs by a badi, if needed to used there
Example
The following Business Partner has the role ‘MKK’ assigned.
Such a BP does not have customer master data, no entry can be found in the customer table (KNA1).
It won’t be transferred to FSM unless its role is added in transaction /PACG/ECM_BPASGN and checked as ‘Customer’.
The BP would be sent after saving or manually with transaction /PACG/ECM_CUSTMASTER:
The BPs address is also sent.
The final result in FSM master data:
