on 2025 Apr 10 6:45 AM
Hi Experts,
We are looking for best practices & standard approach in SAP S/4HANA Public Cloud to handle a real-time business scenario involving Parent-Child mapping for both Customers and Vendors, where centralized payment receipt & liability management is required.
Business Requirement:
Customers:
Parent BP: 1234
Child BPs: 4567, 7890, 2345
Invoices are raised from Child BPs based on POs received from the customer (GST-wise creation done for each location).
Requirement:
→ Payments are collected centrally in Parent BP (1234) via Bank API e-Collection.
→ Payment received in Parent BP should get reconciled & cleared against invoices lying in Child BPs.
→ Credit Management is to be maintained at Parent BP level.
Vendors:
Parent BP: 9876
Child BPs: 6543, 3210, 5678
Procurements & invoices are processed at the Child BP level.
Requirement:
→ Payments to vendors are processed centrally from Parent BP (9876).
→ Liability for all Child BP invoices should be paid from Parent BP account.
→ Vendor evaluation & liability monitoring at Parent BP level.
Clarifications Required:
What is the recommended Relationship Category to be used in BP Master Data for both Customers & Vendors in Public Cloud?
(e.g., BUR001 - Has Subsidiary, BUR017 - Is Invoiced By, BUR018 - Is Paid By, or any other specific for Vendor?)
For Customer Receipts via Bank API e-Collection — how to configure payments received in Parent BP to automatically clear Child BP invoices?
For Vendor Payments — how to process payment from Parent BP and clear Child BP liabilities?
For Customer Credit Management, is assigning Credit Segment only at Parent BP sufficient for controlling exposure of all Child BPs?
For Vendor Liability Monitoring, is there any standard feature to track consolidated liability at Parent BP level?
Is Alternative Payee or Alternative Payer mapping applicable and supported in SAP S/4HANA Public Cloud for these scenarios?
(For both Customer Receipts and Vendor Payments)
Are there any standard apps or best practice guides available for managing this Parent-Child BP structure for centralized payment and reconciliation?
Would appreciate your guidance, configuration steps, or SAP Help documentation references for handling this scenario in SAP S/4HANA Public Cloud.
Thanks in advance!
Request clarification before answering.
Dear Customer,
Multiple customer master records representing the same legal entity can be consolidated into a single, unified record known as the Golden Record.
Consolidating Customer Master Data
Business Partner Relationships
BP Relationship for Credit and Lability
The list of all relationship categories in SAP S/4HANA Public Cloud :-
RelCat | Description | Description | Title |
BBP002 | Has the Invoicing Party | Is the Invoicing Party Of | Invoicing Party Rel. |
BUR001 | Has Contact Person | Is Contact Person for | Contact Person Rel.ship |
BUR002 | Has Activity Partner | Is Activity Partner for | Act. Partner Relationship |
BUR003 | Has Shared Living Arrangement Member | Belongs to Shared Living Arrangement | Shared Living Arrangement |
BUR004 | Is Married to | Marriage | |
BUR006 | Is identical to | Alias (Identity) | |
BUR010 | Has the Employee | Is Employee of | Employee Relationship |
BUR011 | Has the Employee Responsible | Is the Employee Responsible for | Responsible Employee |
BUR013 | Is Replaced by | Replaces | Replacement Relationship |
BUR020 | Has Department | Is Department of | Department |
BUR021 | Has Child | Is Child of | Parent-Child Relationship |
BUR022 | Is Guardian | Has Guardian | Guardian Relationship |
BUR023 | Is Related to | Relationship | |
BUR024 | Has Partner in Marriage Partnership | Belongs to Marriage Partnership | Marriage Partnership |
BUR025 | Has Service Performer | Is Service Performer For | Service Performer |
BUR028 | Has Collaboration User | Is Collaboration User for | Collaboration User |
BUR030 | Is Legal Entity For | Belongs to Legal Entity | Legal Entity Relationship |
BUR101 | Has Ordering Address | Is Ordering Address For | Ordering Address |
BUR102 | Has Invoicing Party | Is Invoicing Party For | Invoicing Party |
BUR103 | Has Goods Supplier | Is Goods Supplier For | Goods supplier |
BUR104 | Has Manufacturing Site | Is Manufacturing Site For | Manufacturing Site |
BUR105 | Has Warehouse Location | Is Warehouse Location For | Warehouse Location |
BUR106 | Has Alternative Payee | Is Alternative Payee For | Alternative Payee |
BUR998 | Is Partner of | Is Partner of | Partner Relationship |
BURC01 | Is Shareholder of | Has Shareholder | Shareholder Relationship |
CHM001 | Responsible for Channel Partner | Responsible Channel Manager Unit | CHM - Relationship |
CHM002 | Has the Ship-To Party/Recipient | Is the Ship-To Party/Recipient Of | Ship-To Party Relship |
CHM003 | Corporate Family Has the Member | Is Member of Corporate Family | Company Group |
CHM004 | Has Third Party | Is Third Party Of | Third Party |
CHM005 | Has the Responsible Partner Contact | Is Responsible Partner Contact For | Resp. Partner Contact |
CPG001 | Has the Sold-To Party | Is the Sold-To Party Of | Sold-To Party Relationshp |
CRMD01 | Is Sales Partner Of | Has Sales Partner | Sales Partn. Relationship |
CRME01 | Is Trader For | Has Trader | Trader Relationship |
CRME02 | Has End Customer | Is End Customer Of | Trader - End Customer |
CRME03 | Is Service Center | Has Service Center | Service Center Relship |
CRMH00 | Has an Undefined Relationship With | Is the Undefined Partner Of | Undefined Relationship |
CRMH02 | Has the Ship-To Party/Recipient | Is the Ship-To Party/Recipient Of | Ship-To Party Relship |
CRMH03 | Has the Payer | Is the Payer Of | Payer Relationship |
CRMH04 | Has the Bill-To Party | Is the Bill-To Party Of | Bill-To Party Relship |
CRMH06 | Has the Responsible Business Partner | Is Responsible Business Partner For | Person Responsible |
CRMH07 | Has the Wholesaler | Is Wholesaler For | Wholesaler |
CRMI01 | Has the Personal Contact | Is Personal Contact Of | Personal Contact |
CRMM01 | Has the Alternative Payer | Is Alternative Payer For | Alternative Payer Relship |
CRMM02 | Has the Payee | Is Payee For | Payee Relationship |
CRMM03 | Has Correspondence Recipient | Is Correspondence Recipient For | Corr.Recipient Relship |
CRMM04 | Has Dunning Recipient | Is Dunning Recipient For | Dunning Recipient Relship |
CRMS01 | Has the Carrier | Is the Carrier For | Carrier |
CRMS02 | Manages Entitlements From | Entitlements Are Managed By | Manager for Entitlements |
CRMS03 | Is the Responsible Scrapper For | Has the Responsible Scrapper | Responsible Scrapper |
CRMS09 | Is the Remanufacturer For | Has the Remanufacturer | Remanufacturer |
EDO001 | Singapore: Has Peppol Endpoint ID | Singapore: Is Peppol Endpoint ID of | SG: Peppol Endpoint ID |
EWM001 | Has the Dock Appointment Scheduling Planner | Is the Dock Appointment Scheduling Planner Of | Dock App. Sched. Planner |
FI0200 | Has the alternative payer | Is an alternative payer for | Alternative payer |
FI0210 | Has the authorized payers | Is an authorized payer for | Authorized payers |
FI0300 | Has the alternative dunning recipient | Is alternative dunning recipient for | Altern. dunning recipient |
FS0030 | Borrower Entity Member | Has the Member | Borrower Entity Member |
FSB001 | is a shareholder of | has the shareholder | Privat Co. with partners |
FSB002 | Is subsidiary of | Is parent company of | Parent company/subsidiary |
HCM001 | Has Employment | Is Employment For | Employment |
HCM002 | Has External Employment | Is External Employment For | External Employment |
HCM003 | Has Service Performer Contract | Is Service Performer Contract For | Service Perform. Contract |
HEA010 | Has Hospital Employee | Is employed in | Hospital Employee |
HEA020 | Has Hospital Employee | Is employed in | Hospital Employee |
ICM001 | Has the Responsible Organization | Is the Responsible Organization For | Organization Responsible |
ICM002 | Has the External Organization | Is the External Organization For | External Organization |
ICM003 | Has External Person | Is the External Person For | External Person |
IHS001 | Has medical address | Is medical address | Medical Address |
ISHAPH | Has Attending Physician | Is Attending Physician For | Attending Physician |
ISHINS | Has Health Insurance Provider | Is Health Insurance Provider For | Health Insurance |
JIT001 | Has Contact Person for Just-In-Time Processes | Is Contact Person for Just-In-Time Processes | Contact Person for JIT |
LM0001 | Has the Processor | Is a Processor Of | Processor Relationship |
LM0002 | Has Responsible for Group | Is Responsible for Group | Group Responsibility Rel. |
LM0003 | Has a Subgroup | Is a Subgroup Of | Executing Subgroup |
SCM001 | Has the SNC User | Is the SNC User Of | SNC Partner User |
TM0001 | Has Sales Representative | Is Sales Representative | Sales Representative |
UDM001 | has Collection contact person | is Collection contact person for | Collections Relationship |
UKM001 | Superordinate Credit Account From | Subordinate Credit Account To | CM Account Hierarchy |
UKMSB0 | managed in Credit Management | in Credit Management is managed by | CM Processor |
UKMSBG | has Employees | is in credit analyist group | Credit Analyist Group |
If you need more help for any of the relationships categories mentioned above please a support ticket.
Kind regards,
Bhawesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
9 | |
2 | |
2 | |
2 | |
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.