S4 HANA MASTER DATA Enterprise structure and Master data Flashcards
Client
3 digit alphanumeric code that models a corporate / regional group with separate set of tables and data in the application
Can have any number of company codes
Company code
helps mapping the legal entities in the application there by enabling generation of tax reports, balance sheet and P/L statements
Can have any number of plants, sales organizations and purchase organizations
Controlling area
Management oriented org unit that helps in tracking the cost flows and costing in the organization
Manages the cost accounting for one company code or multiple company codes
Sales Organization
Responsible for sale of products and services, pricing, negotiation with the customers and returns, complaints processing.
Plant
Logitics unit reponsible for tracking the inventory by value. Multiple storage locations are assigned to the same plant at which level quantity tracking is done.
Purchasing organization
Responsible for purhasing and negotiation with supplies, purchase contracts and prices in any organization
Shipping point
Responsible for delivery processing activities like picking, packing, loading and goods movements in a plant
Related to plants in a many-to-many relationship
Transportation planning point
It is responsible for shipment processing and transportation planning enabling combining multiple deliveries in a shipment and selection of optimal routes during transportation
Division
Defines the product or service division in a business unit
Distribution Channel
Identifies the chanlle through which the product or services are distributed to the customers
Mappings
Done by standardizing, simplifying the structures in the application with enough room for scalability and flexibility
Business partner data
S/4 allows to map business organizations, departments and consumers who are customers of the company as business partners in the application
- Any stake holder of the company is mapped as a business partner with corresponding role
- Both customers and vendors are modeled as business partners
- Field status and screen configurations are governed by business partner roles
- Allows to capture multiple addresses for the same partner
Sample business partners
- Contact person
- Sold-to
- Business organizations
- Sales agents
- Business organization departments
- Employees
Business partner – General data
- Address data
- Company name
- Telephone number
- Bank details
- Transportation zone
Business partner – Company code data
- Insurance data
- Reconciliation account number
- Payment terms
- Data is maintained at business partner and company code level
Business Partner – Sales area data
- Pricing data
- Shipping conditions
- Delivery priority
- Data is maintained at business partner and sales area [sales org, distribution channel, division]
Business Partner – Number ranges
- Customer
- Vendor
- Credit management
- Employee
BP CVI: Business need
hIt is mandatory to use only business partner to model any stake holder – vendor, customer, forwarding agent, employee etc. This new BP approach is defined because of some issues
BP CVI – Customer Vendor Integration
S/4 HANA supports only business partners, however the existing sales transactions would work as usual. This is acheieved using customer-vendor integration functionality
- Business partner records trigger creation of table entries in old customer tables – KNA1 & LFA1 along with entries in new table BUT000
- This enables the older transactions like VA01 - sales order creation to work properly
- Old transactions for maintaining customer, vendors are obselete in S/4 HANA
- Only transaction BP is available to manage the BP data
BP CVI – moving to S/4 HANA
Existing customers and vendors need to be synchronized to business partners before moving to S/4 HANA system as only BP is supported
S/4 HANA material master
Material master length is 40 characters
Material type ‘SERV’ introduced to model services
Different stages of a material like finished goods, sem-finished etc are modeled as material types
Material types control the fields and screen configurations in the material master
- Define number ranges
- Defines procurement type – in-house / procured
Material master views
Basic data
Sales org views
Purchasing views
Accounting views
Costing views
Production planning views
Material master – Sales area data
sales area data captured in the material master
- Availability check views
- Sales tax information
- Item category group
- Default Delivery plant
- Division
