0% found this document useful (0 votes)
79 views3 pages

BP Concept

Business partners in S/4 HANA consolidate various entity types like customers, vendors, agents, etc. into a single data model for improved data consistency and simplified transactions. Key steps to set up a business partner include: 1) defining number ranges and groups for BPs, vendors, and customers; 2) assigning these ranges and creating synchronization between entities; 3) defining the BP role and adopting relevant master data into the BP. This centralized approach streamlines entity management from a single source.

Uploaded by

sapeins
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
79 views3 pages

BP Concept

Business partners in S/4 HANA consolidate various entity types like customers, vendors, agents, etc. into a single data model for improved data consistency and simplified transactions. Key steps to set up a business partner include: 1) defining number ranges and groups for BPs, vendors, and customers; 2) assigning these ranges and creating synchronization between entities; 3) defining the BP role and adopting relevant master data into the BP. This centralized approach streamlines entity management from a single source.

Uploaded by

sapeins
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Business Partner :

XK01 , mk01, fk01, xd01, fd01, vd01 == obsolete ( no more exist in s4 hana ) ???

Reason Why ??? data redundancy , lot of t codes , role specific data , no consistency in data ..

Business partner ????

Individual , org , group ???? with whole we do business like legal entities , banks , agents , supplier ,
customers ……….. diff roles ..

Business roles !!

Advantage – single source – single transaction code (BP)

- Centralized data
- Simplified data model
- Roles specific screens

Steps we followed in ECC :=

1. Vendor group
2. No ranges for group ( there must be same no. ranges with business partner also ) – RECACUST’
3. Define grouping and assign number ranges.
4. Define BP roles == > RECACUST ( u can copy from standards ) or U can carry on with standards ..
5. Define BP role customer / vendor to business partner
6. Define no. range assignment for direction BP to vendor ( u r making a relation of both no. ranges
Vendor & BP )
7. Define BP
8. Tolerance group
9. Reconciliation ac ( s.cr)
10. Doc type ( Follow GL for doc type n number ranges )
11. Pur invoice ( same )
12. Outgoing payment (same)
13. Analysis of vendor reports ( FBL1H)

BP points to be considered to save one BP along with vendor & customer

1. BP Role ( Standard / u can customize – copy )


2. Define no. range ( BP number range)
3. Define grouping and number range ( BP Group ) – SYSK
4. Define vendor group ( ECC) - SYRM
5. Create number ranges ( Vendor group )
6. Assign number ranges to vendor group
7. Synchronization ( BP --- >> Vendor ) – define BP role direction vendor to BP
8. Define number assignment BP to vendor
9. Define BP ( Tocode – BP )

Customer ????

1. Define number ranges (BP) --- no need


2. Define grouping and number ranges ( BP group ) – no need ..
3. Define customer ac group – ecc SYDC
4. Create no. ranges “SE” - external.
5. Assign no. ranges to customer group .
6. Synchronization ( BP---- > customer ) -- > define BP role direction customer to BP
7. Define number assignment BP to vendor
8. Go to BP and select BP role ( customer (Fin. Accounting)
Pres enter – click on company code button and follow the steps to adopt customer into same BP

You might also like