The Organizational Structure (left) can be linked to Logistical Structure (right) for each Force Element.
The Organizational Structure - Logistics Integration MRP Areas are as follows:
- MRP Areas were originally created for differentiation of Logistical Planning (MRP). The MRP area represents an organizational level for which material requirements planning is carried out independently.
- MRP Areas consist of Storage Locations.
- All Plants are referred to as MRP Areas as well.
A Storage Location is as follows:
- May be part of an MRP Area or belong directly to a plant.
- May be also be excluded from MRP Planning.
DFPS/D&S Promotes the usage of MRP Areas:
MRP Areas are the integration points between Organizational and Logistical Structure. They are assigned to Force Elements.
MRP Areas differentiate between Stocks, Provisions and Infrastructures:
- Assignment of Plant and MRP Area and Stock Storage Location in table /ISDFPS/FORCE.
- Technical Links in database tables: Storage Location <MDLG> MRP Area.
Business Partner as leading object; integrator between different data models across SAP solutions/modules.
Mandatory for SAP S/4HANA (->Simplification Item).
There are three business partner categories. You can enter the following data:
- Organization
- Form of address, name, legal form, industry, legal entity
- Person
- Form of address, first and last name, other name components (such as name prefixes and affixes and academic title), gender
- Groups
- Form of address, two names, partner group type (marriage, shared living arrangement)
The advantages are as follows:
- Multiple roles can be associated to the same Business Partner.
- Maximal data sharing and reuse of data is enabled, which leads to easier data consolidation.
- The general data is available for all different Business Partner roles; specific data is stored for each role.
- It maintains multiple relationships to the same Business Partner.
- It maintains the Time Dependency for different sub-entities roles, address, relationship, bank data, and so on.
Overview - details on the following figures:
1. Key Points:
- Delivery Address of Force Element (FE - OrgStructure) can be synchronized with address of Storage Location (Logistics)
- Minimized redundancy of address usage
Top Left (Organizational Structure):
- One FE can only have one delivery address at the same time (Infotype 1952)
- Several Storage Locations can have different addresses
- Activate FE address
- Activation of FE address triggers creation of Business Partner
Top Right (Business Partner):
- Business Partner does the Integration between data D&S and Logistics data models
- Address is copied from Force Element to Business Partner
2. CVI- Customer Vendor Integration:
- Creation of Business Partner in Roles: Customer/Vendor automatically synchronizes into Customer/Vendor objects (CVI)
- Customer/Vendor hold their own address information
3. Assign Customer/Vendor:
- Customer/Vendor object can be assigned to different Storage Locations. Address information stays at Customer/Vendor object.
- Conclusion: Delivery Address of Force Element is synchronized with the address assigned for storage locations.
The starting point is a Force Element with a delivery address:
- Different Sub Type(s) for addresses can be assigned to a FE: delivery, postal, geo location, next harbor.
- The Sub Typedelivery address is used for integration with Business Partner (BP).
- SAP D&S uses the address of FE in Infotype 1952 to sync to BP. Infotype 1952 contains an address number of global address table ADRC.
- In Comparison: HCM-Standard (without SAP D&S) uses HCM-address in Infotype 1028 for sync to BP.
- Button: Add Address - Create From Existing Address or Copy From Existing Address or Inherit Address.
- Button: Transfer Address: Allows to transfer selected address to child FE.
Technical:
Follow-up action can be set up for different status changes or measure areas.
Role: Business Partner (Gen): Is the standard role for each BP.
Role: Organizational Unit: Name and abbreviation are transferred:
- Shows delivery address
- Shows attributes of Business Partner
Link between Organizational Unit (O) and Business Partner (BP): HRP1001 O - BP (B 207).
This figure highlights the role of the business partner, in this case:
Uses Roles Customer (and/or Vendor)
Uses BAdI for automatic role creation when BP is created from FE
The transaction code BP or SAP Fiori App Maintain Business Partner are used for manual role creation:
- Show Customer/Vendor is synchronized by CVI - Display Role: Customer/Vendor
- Number of BP and Customer/Vendor can be set to same number ranges - usage of identical numbers (example shows internal number ranges, so not identical)
Left Side: SAP Fiori app Manage MRP Areas and its Storage Location:
- You can create/edit the MRP Area for the Force Element.
- You can add 1-n Storage Locations.
- Note: Link from Force Element […] Three-Dot-Menu ->'Create Stock MRP Area' is possible. FE ID is overtaken.
Right Side: Fiori App: Manage Force Elements- Logistics Section.
Assign the Logistics Data.
SAP Fiori app Manage MRP Areas and its Storage Location:
- Search MRP area
- Search for Customer/Vendor
Additional Customer/Vendors can be created for different addresses of storage locations, without connection to Force Elements. This is directly possible from the Manage MRP Areas and its Storage Location app.
Linkage of Objects in database table: Force Element ↔ Business Partner ↔ Customer/Vendor ↔ Storage Location ↔ MRP Area ↔ Force Element.
Force Element <HRP1001> Business Partner <CVI_CUST_LINK/CVI_VEND_LINK> Customer/Vendor <T001L> Storage Location <MDLG> MRP Area </ISDFPS/FORCE> Force Element.