cancel
Showing results for 
Search instead for 
Did you mean: 

How to Map Parent-Child Relationship for Both Customers & Vendors in SAP S/4HANA Public Cloud

Praveen06
Explorer
0 Kudos
292

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:

  1. Relationship Mapping:

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?)

 

  1. Centralized Payment Processing:

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?

 

  1. Credit & Liability Management:

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?

 

  1. Master Data Setup:

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)

 

  1. Standard Apps / Best Practices:

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!

Accepted Solutions (0)

Answers (1)

Answers (1)

Bhawesh
Product and Topic Expert
Product and Topic Expert
0 Kudos

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 :-

RelCatDescriptionDescriptionTitle
BBP002Has the Invoicing PartyIs the Invoicing Party OfInvoicing Party Rel.
BUR001Has Contact PersonIs Contact Person forContact Person Rel.ship
BUR002Has Activity PartnerIs Activity Partner forAct. Partner Relationship
BUR003Has Shared Living Arrangement MemberBelongs to Shared Living ArrangementShared Living Arrangement
BUR004Is Married to Marriage
BUR006Is identical to Alias (Identity)
BUR010Has the EmployeeIs Employee ofEmployee Relationship
BUR011Has the Employee ResponsibleIs the Employee Responsible forResponsible Employee
BUR013Is Replaced byReplacesReplacement Relationship
BUR020Has DepartmentIs Department ofDepartment
BUR021Has ChildIs Child ofParent-Child Relationship
BUR022Is GuardianHas GuardianGuardian Relationship
BUR023Is Related to Relationship
BUR024Has Partner in Marriage PartnershipBelongs to Marriage PartnershipMarriage Partnership
BUR025Has Service PerformerIs Service Performer ForService Performer
BUR028Has Collaboration UserIs Collaboration User forCollaboration User
BUR030Is Legal Entity ForBelongs to Legal EntityLegal Entity Relationship
BUR101Has Ordering AddressIs Ordering Address ForOrdering Address
BUR102Has Invoicing PartyIs Invoicing Party ForInvoicing Party
BUR103Has Goods SupplierIs Goods Supplier ForGoods supplier
BUR104Has Manufacturing SiteIs Manufacturing Site ForManufacturing Site
BUR105Has Warehouse LocationIs Warehouse Location ForWarehouse Location
BUR106Has Alternative PayeeIs Alternative Payee ForAlternative Payee
BUR998Is Partner ofIs Partner ofPartner Relationship
BURC01Is Shareholder ofHas ShareholderShareholder Relationship
CHM001Responsible for Channel PartnerResponsible Channel Manager UnitCHM - Relationship
CHM002Has the Ship-To Party/RecipientIs the Ship-To Party/Recipient OfShip-To Party Relship
CHM003Corporate Family Has the MemberIs Member of Corporate FamilyCompany Group
CHM004Has Third PartyIs Third Party OfThird Party
CHM005Has the Responsible Partner ContactIs Responsible Partner Contact ForResp. Partner Contact
CPG001Has the Sold-To PartyIs the Sold-To Party OfSold-To Party Relationshp
CRMD01Is Sales Partner OfHas Sales PartnerSales Partn. Relationship
CRME01Is Trader ForHas TraderTrader Relationship
CRME02Has End CustomerIs End Customer OfTrader - End Customer
CRME03Is Service CenterHas Service CenterService Center Relship
CRMH00Has an Undefined Relationship WithIs the Undefined Partner OfUndefined Relationship
CRMH02Has the Ship-To Party/RecipientIs the Ship-To Party/Recipient OfShip-To Party Relship
CRMH03Has the PayerIs the Payer OfPayer Relationship
CRMH04Has the Bill-To PartyIs the Bill-To Party OfBill-To Party Relship
CRMH06Has the Responsible Business PartnerIs Responsible Business Partner ForPerson Responsible
CRMH07Has the WholesalerIs Wholesaler ForWholesaler
CRMI01Has the Personal ContactIs Personal Contact OfPersonal Contact
CRMM01Has the Alternative PayerIs Alternative Payer ForAlternative Payer Relship
CRMM02Has the PayeeIs Payee ForPayee Relationship
CRMM03Has Correspondence RecipientIs Correspondence Recipient ForCorr.Recipient Relship
CRMM04Has Dunning RecipientIs Dunning Recipient ForDunning Recipient Relship
CRMS01Has the CarrierIs the Carrier ForCarrier
CRMS02Manages Entitlements FromEntitlements Are Managed ByManager for Entitlements
CRMS03Is the Responsible Scrapper ForHas the Responsible ScrapperResponsible Scrapper
CRMS09Is the Remanufacturer ForHas the RemanufacturerRemanufacturer
EDO001Singapore: Has Peppol Endpoint IDSingapore: Is Peppol Endpoint ID ofSG: Peppol Endpoint ID
EWM001Has the Dock Appointment Scheduling PlannerIs the Dock Appointment Scheduling Planner OfDock App. Sched. Planner
FI0200Has the alternative payerIs an alternative payer forAlternative payer
FI0210Has the authorized payersIs an authorized payer forAuthorized payers
FI0300Has the alternative dunning recipientIs alternative dunning recipient forAltern. dunning recipient
FS0030Borrower Entity MemberHas the MemberBorrower Entity Member
FSB001is a shareholder ofhas the shareholderPrivat Co. with partners
FSB002Is subsidiary ofIs parent company ofParent company/subsidiary
HCM001Has EmploymentIs Employment ForEmployment
HCM002Has External EmploymentIs External Employment ForExternal Employment
HCM003Has Service Performer ContractIs Service Performer Contract ForService Perform. Contract
HEA010Has Hospital EmployeeIs employed inHospital Employee
HEA020Has Hospital EmployeeIs employed inHospital Employee
ICM001Has the Responsible OrganizationIs the Responsible Organization ForOrganization Responsible
ICM002Has the External OrganizationIs the External Organization ForExternal Organization
ICM003Has External PersonIs the External Person ForExternal Person
IHS001Has medical addressIs medical addressMedical Address
ISHAPHHas Attending PhysicianIs Attending Physician ForAttending Physician
ISHINSHas Health Insurance ProviderIs Health Insurance Provider ForHealth Insurance
JIT001Has Contact Person for Just-In-Time ProcessesIs Contact Person for Just-In-Time ProcessesContact Person for JIT
LM0001Has the ProcessorIs a Processor OfProcessor Relationship
LM0002Has Responsible for GroupIs Responsible for GroupGroup Responsibility Rel.
LM0003Has a SubgroupIs a Subgroup OfExecuting Subgroup
SCM001Has the SNC UserIs the SNC User OfSNC Partner User
TM0001Has Sales RepresentativeIs Sales RepresentativeSales Representative
UDM001has Collection contact personis Collection contact person forCollections Relationship
UKM001Superordinate Credit Account FromSubordinate Credit Account ToCM Account Hierarchy
UKMSB0managed in Credit Managementin Credit Management is managed byCM Processor
UKMSBGhas  Employeesis in credit analyist groupCredit Analyist Group

If you need more help for any of the relationships categories mentioned above please a support ticket.

Kind regards,
Bhawesh