assignment to a co object sap

Blog about all things SAP

ERProof » SAP CO » SAP CO Training » SAP CO Account Assignment

SAP CO Account Assignment

Normally, when a financial document is entered in SAP FI module , user has the option of entering the cost center in the financial document. However, when documents are entered from different modules or a cross-module financial transaction occurs, such as from MM or SD , there is no option of entering the cost center in the document. In this situation, the SAP system will derive the cost center through automatic SAP CO account assignment, substitutions, or through default settings made in the primary cost element.

Automatic SAP CO Account Assignment

The automatic account assignment has to be configured in the transaction code OKB9 . For posting made in external accounting, such as for price differences, exchange rate differences, etc., the SAP system automatically checks entries in the OKB9 settings and derives the cost center.

If you do not enter a CO object (order, cost center, or project) in external accounting postings made in FI, MM or SD modules and the posting is cost relevant, then the automatic account assignment checks the relevant cost center and makes the posting.

Here are examples of automatic account assignments:

• Banking fees, exchange rate differences and discounts in FI
• Minor differences and price differences in MM

The account assignment objects that can be maintained in the transaction OKB9 are:

• Cost center
• Profit center (profitability segment)

Normally, the automatic account assignment runs on the company code level along with the CO object. However, if the user wants to make the posting on the business area level, valuation area level or profit center level, it is also available in OKB9 settings. So basically it includes the following levels:

• Company code level
• Business area level
• Valuation area level
• Profit center level

The above 3 excluding the company code level are used in cases when the account assignment is needed below the company code level.

Prerequisites

Here are the prerequisites of activating automatic SAP CO account assignment:

• Activation of the cost center accounting
• Creation of cost centers
• Maintenance of cost elements

Additionally, you can also create orders and profit centers as per the business requirements.

Settings in Transaction OKB9

Let’s discuss settings that are possible for automatic SAP CO account assignment in OKB9 transaction.

Start SPRO transaction and navigate to the following path:

Controlling – Cost Center Accounting – Actual Postings – Manual Actual Postings – Edit Automatic Account Assignment (OKB9)

Alternatively, you can start OKB9 transaction directly from the command bar.

• If you want to have the setting on the company code level only, then enter the company code and the cost element along with the corresponding CO object, i.e. a cost center, an order or a profit center.
• If you want to have the settings on the valuation area level, then enter the company code and the cost element and chose the ‘valuation area’ option in the account assignment detail as ‘1’.
• Similarly, if you want to have the settings on the business area or profit center level, then choose the option ‘2’ or ‘3’ respectively.

If you have chosen account assignment detail ‘1’ or ‘2’, then click on ‘Detail per business area/valuation area’ on the left sidebar.

Default SAP CO Account Assignment

In order to determine the correct CO account assignment, the SAP system performs several checks in the following sequence. First it checks the document which a user is posting. If the cost center is empty in the document, then the system checks if any substitutions are maintained for the particular G/L account . Next, if the substitution is also missing, then the system moves on to the OKB9 settings for automatic SAP CO account assignments. Finally, if these settings are also missing, the SAP system checks master data of the primary cost element (G/L Account) under the tab of Default Account Assignment . You can display this master data using the transaction KA03 .

You can maintain the cost center and the order in the master data of the primary cost element.

So, basically the order of checks the system makes is:

• Financial document – Cost center
• Substitutions – transaction OKC9
• Automatic account assignments – transaction OKB9
• Default account assignments – transaction KA03 / KA02

Lastly, if any of the above is not maintained, then the SAP system throws an error ‘Account X requires an assignment to a CO Object’ and doesn’t allow posting of a document.

SAP CO Account Assignment using Substitution

In cases where you don’t need OKB9 or default account assignment, the user can go for user exits where a specific G/L account is mentioned under the company and the value in the cost center is substituted by the cost center given in the substitution.

The transaction for maintaining the substitution is GGB1 .

Usage of substitutions for SAP CO account assignment is justified by the business requirement and usually SAP CO account assignment requirements are fulfilled by OKB9 or default account assignments.

Did you like this tutorial? Have any questions or comments? We would love to hear your feedback in the comments section below. It’d be a big help for us, and hopefully it’s something we can address for you in improvement of our free SAP CO tutorials.

Navigation Links

Go to next lesson:  SAP Adjustment Postings

Go to previous lesson:  SAP Profit Center

Go to overview of the course: Free SAP CO Training

4 thoughts on “SAP CO Account Assignment”

it is helpful material i ask for more clear details for using substitution method for Account Assignment. thanks in advance

Sir, I am not receiving the training mails from yesterday 7/1/2019. I have completed my training till here(SAP CO Account Assignment) please do send the rest of the training emails for SAP CO. Hope you will do the needful.

I am getting the same error “Account 500911 requires an assignment to a CO object”. In OKB9, we have given company code, Cost element and ticked the check box ‘Indicator: Find profitability segment using substitution’ (V_TKA3A-BSSUBST) and not filled anything like cost center, order and profit center. in OKC9 we have created substitution. All the process happening through Idoc Message Type SINGLESETTRQS_CREATE and inside BAPI BAPI_SINGLESETTREQS_CREATEMULT triggering and raising this error. Cost center is not maintained in 1. Financial document – Cost center 2. Automatic account assignments – transaction OKB9 and 3. Default account assignments – transaction KA03/KA02 But we have substitution in transaction OKC9 to determine cost centre.

Where woulbe be the issue?

good explanation

Leave a Reply Cancel reply

Do you have a question and want it to be answered ASAP? Post it on our FORUM here --> SAP FORUM !

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

3475182 - Post revenue from sales order to cost center

• Cost center is not available at Sales Orders cost assignment options.
• When using Project Revenues as sales orders accounting objects the only settlement option available is to settle the project to a Profitability segment and no option to settle the project to cost center is available.

Environment

SAP S/4HANA Cloud

SD invoice, cost center assignment, sales order cost assignment, S4_PC, S4_1C, post revenue , KBA , CO-OM-CEL , Cost Element Accounting , How To

About this page

Search for additional results.

Visit SAP Support Portal's SAP Notes and KBA Search .

Privacy | Terms of use | Legal Disclosure | Copyright | Trademark

Analyzing Key Aspects of Technical Master Data

After completing this lesson, you will be able to:

• Analyze the structure and components of technical master data
• Synthesize usage of connection object and connection
• Analyze the functionality and significance of the device location and premise
• Apply principles of installation

Technical Master Data Overview

In the SAP S/4HANA Asset Management system, the utilities' technical master data follows a predefined structure. Here, the utilities' connection object equates to an upper-level functional location, while the utilities' device location matches a functional location on a level below. Further, any utilities device corresponds to an equipment aspect that is technically installed into a device location.

Both functional locations and equipment fall under the broad term "Technical Objects." They serve as technical reference points for service and maintenance orders.

Without integration into other SAP components, premises and installations stand as pure utilities objects.

Consider the connection object as a building, a parcel of property, or a facility such as a fountain or construction site. It has a single address that links it to the regional structure and can include connections for several divisions. Moreover, the connection object is assigned to a maintenance plant for operational purposes.

The creation of premises and device locations hinge on the presence of a connection object. A single connection object can house several device locations, such as a basement and ground floor, or numerous premises, like a multifamily house with multiple apartments.

The device location specifies the exact place in a connection object where devices of any division are physically installed. This location borrows the connection object's address and can be further elaborated by extra location data.

A premise is a supplied and enclosed unit such as an apartment or a factory, and it can encompass several installations, depending on the divisions supplying it. A premise inherits the address from the connection object, transfers it to the installation, and can be elaborated further with more premise data.

Contrary to other technical master data, the installation is a logical rather than a physical object. It is the product of billing-related installations of devices and registers and their allocation to rate types. The installation maintains all related rate data such as rate category and rate type, in addition to managing all related meter reading and billing orders, along with billing and even invoicing documents. The installation inherits the connection object address from the premise, and if needed, can adopt regional default values such as the meter reading unit. Apart from being division-dependent, the installation is also linked to contracts and devices, and is assigned to the contract during the Move-In process. In essence, it connects the technical and business master data efficiently.

Connection Object and the Connection

Manifesting as a building, property, or even a facility such as a fountain or construction site, the connection object is a versatile entity. It possesses a unique address, linking it firmly to the regional structure. In this scenario, the technical address of the connection object assumes greater importance over the business partner address, which can differ. This technical address can contain default values for meter reading and billing, which can be referred to during installation creation.

Tying the connection object to the landscape of the regional structure, the regional structure group can be derived from the technical address. This group carves out its role by associating with, and grouping together, several cities. Meanwhile, the regional structure area amalgamates several regional structure groups, as defined in Customizing. This area can be derived from any connection object address when determining the plant during service order creation.

Catering to field services, both the connection object and the lower-level device location can incorporate notes. Serving as a pool of customizable texts with placeholders (&), these notes can generate individual messages. As a practical application, these notes can relay vital information to field service employees on meter reading orders or service orders. A message for a connection object could, for example, be a simple 'Beware of the Dog', 'Ring at &', or 'Key Number &'.

Matching a top-level functional location, the connection object finds its association with a maintenance plant. The maintenance plant holds all the technical objects installed for a company. The link with the maintenance plant is the maintenance planning plant, which determines planning responsibility. By assigning the regional structure groups of the connection object to regional structure areas, which are then mapped to service objects in Work Management Customizing, the maintenance planning plant can be derived.

The connection object can house connections across several divisions. Interestingly, a connection isn't a required master data object and can be considered as equipment devoid of utilities data. It acts as a bridge, linking the technical objects of the supply grid, such as lines, pylons, and transformers, to the utilities connection object. The connection can be modeled as a service connection using SAP S/4HANA Service functions via Work Management. Through the service connection workflow template, the connection is created in the final step and assigned to the connection object.

Device Location and the Premise

Existing as a precise location within a connection object, a device location is where devices from any division are technically installed. A device location comes into existence with a connection object and obtains its address from this object. You can elaborate on the exact place of a device location using extra location data, the values for which can be predefined in Customizing-even the location addition can be expanded upon with free text.

Both the device location and its counterpart, the connection object one level above, carry the potential to house notes for field services. In the form of a pool of customizable texts with placeholders, these notes serve as individual messages, printed on meter reading or service orders for field service employees. Messages for device locations include warnings or information, such as "Meter hard to access!" or "Dangerous stairs!"

In the scheme of function locations, the device location parallels a function location one level below the connection object and thereby, inherits the maintenance plant from the connection object. While the device location is the specific spot in the connection object where numerous devices are installed, it is only of significance to the distributor, who performs field service activities, such as meter reading or device replacement. The supplier, who uses the so-called device info records instead of real devices with technical equipment data, does not need the device location.

Conceptualize the premise as an enclosed unit - an apartment or a factory, for example - that is supplied by different divisions. Just like a device location, the creation of a premise requires a connection object and the address is inherited from this very object. It then transfers the address to the installation. This premise, described by more premise data, can have predefined values for the Premise Type field in Customizing, and free text descriptions for the floor and room number, as well as the location supplement.

The premise can be assigned to an owner (business partner) in one out of three types in Customizing. In the premise type, the owner information is entered directly in the premise transaction and not stored historically. In the case of the owner allocation type, the owner's details are historically noted in the Owner Allocation transaction, and here, one can also activate the Automatic Owner Move-In function.

While a technical installation is not required as a master data object, it is a pure equipment without utilities data. However, it is allocated to the premise, which is a pure utilities object. A technical installation encompasses all installed and nonmetering devices of the same division, such as a fuse box or distributor box. This installation is employed in various processes, such as House Installation Monitoring (HIK) and Outage Notifications.

Installation

In contrast to most technical master data, an installation is not a physical entity but a logical object. It manages crucial control data essential for meter reading and billing of the same division within one premise, and depends upon the division, contract, and device. Its creation calls for the existence of a premise, from which it inherits a connection object address and can adopt regional default values, like the meter reading unit.

During the Move-In process, the installation is assigned to the contract in a one-to-one relationship, linking technical and business master data. Moreover, in the process of New Installation, the installation establishes a one-to-one or many-to-one relationship with the point-of-delivery to connect technical and deregulation master data.

The Time-Dependent Data table contains significant historical data that remains immutable for a period that has been billed. The installation, along with all allocated rate data, is classified for billing and sales statistics by the billing class and division. The billing class prevents misconfigurations, for example, assignment of an industrial rate category to a residential installation. The rate category aligns with the utilities product corresponding to a particular division and billing class, and carries control data for aspects like the billing scheme, period-end billing parameters, and options for backbilling.

The meter reading unit, potentially adopted from the regional structure, and the underlying portion control the frequency and timing of reading and billing installations. Its permissibility must conform to the installation's billing class. The franchise contract specifies the franchise fee arrangement between a utilities company and the municipality, which allows the distributor to use public traffic routes for laying and operating lines.

Venturing into the Installation Structure area, accessible through the 'Devices' button, the billing-related installation of devices and registers and their allocation to rate types result in the installation structure. Since the installation is logical and not physical, a device can be assigned to multiple installations simultaneously. Here, the 'Device Data' table contain all device-related rate data, while the 'Register Data' table comprises all register-related rate data and technical data. The rate types, used along with the rate category, determine the rates.

The 'Billing Periods' button leads you to the 'Billing Overview' area, with 'Documents', 'Billing Order', and 'Rate Types' tab pages. They display the history of all billing and invoicing documents related to the installation, show the billing order and the underlying meter reading orders until billed, as well as the determined rates of the installation based on the combination of rate category and rate types, respectively.

The 'Load Profile' button directs you to the synthetic load profile and usage factors used for Energy Quantity Settlement of residential customers. Moreover, the 'Facts' button takes you to individual installation facts, which control the general rate facts. These can include individual input values such as prices, discounts, or factors, and rate types specifically used to determine fact rates.

Installation Is the Central Master Data Object

In the elaborate architecture of SAP S/4HANA Utilities, the installation stands as the central and most significant master data object. Crucial to linking technical master data with business master data, the installation serves as an essential component in the Move-In process. Equally vital, it connects the technical master data with the deregulation master data via the New Installation process.

Influencing the regional structure, the installation inherits the connection object address to adopt default values. This approach bolsters the management of important time-dependent control data for both meter reading and billing. Further, the installation structure, which emerges from the billing-related installation of devices and registers and their allocation to rate types, can be maintained through the utilities Rate Maintenance function.

Adding an extra layer of specificity, individual installation facts could manifest either as rate types or individual rate step input values. These could include prices, discounts, or factors, ensuring the installation not only serves as a nexus for essential data but also as a modulator for crucial utility functions.

Installation and Rate Determination

In the robust framework of SAP S/4HANA Utilities, an installation reigns as the key and most vital master data object. Playing an integral role in managing rate data, it encapsulates a 'Rate Types' tab page. This tab displays all established rates of the installation, representing them as combinations of rate categories and rate types. This structured display streamlines the complex landscape of rates, enhancing the utility function and overall system proficiency.

Installation and Document Flow

Indeed, the installation operates as a pivotal and paramount master data object within the realm of SAP S/4HANA Utilities.

Serving as a historical archive, the 'Documents' tab page presents a comprehensive record of all past billing and invoicing documents associated with a given installation. This transparency of document history aids in tracking previous transactions, enhancing record-keeping practices, and makes for efficient data retrieval in the utilities domain.

Log in to track your progress & complete quizzes

• About AstraZeneca

Life at AstraZeneca

• Our Locations
• Information Technology
• BioPharmaceuticals
• BioPharmaceuticals R&D
• International
• Enabling functions
• Oncology R&D
• Early Talent

Inclusion & Diversity

• Application Hints & Tips

Keyword Search

City, State, or ZIP

Sr S/4HANA Consultant – SAP FI/CO

ABOUT ASTRAZENECA

AstraZeneca is a global, science-led, patient-focused biopharmaceutical company that focuses on the discovery, development and commercialisation of prescription medicines for some of the world’s most serious disease. But we’re more than one of the world’s leading pharmaceutical companies. At AstraZeneca we’re dedicated to being a Great Place to Work.

ABOUT THE ROLE:

S/4 HANA Consultant - FICO for a world leading pharmaceutical company which operates in over 100 countries and is head quartered in the United Kingdom. The candidate is expected to be a part of a functional team for a large S/4 Hana Program.

The candidate should possess broad functional knowledge in his/her domain and good technical knowledge in the FI and CO modules in both S4 and ECC. The candidate should have work experience in Product costing, WBS, APP, P2P/OTC integration, Bank Master & Business Partners

Key Accountabilities and Responsibilities of Role

• As SAP FI/CO consultant, to cover from design to deployment across the project phases. 
• Facilitate workshops to collect business requirements and map business requirements & processes. Identify, interpret, validate and document business requirements. 
• Work with stakeholders to ensure agreement with the design and support the passage of the solution design through the appropriate governance forums.
• Perform detailed analysis of business processes and Implement the Business solutions. 

Skills and Experience

• Full life cycle S/4HANA Implementation experience is mandatory and should be certified in S/4HANA Finance and / or Controlling.
• In-depth functional understanding of their respective work stream.
• Good understanding of business processes in the life sciences / pharmaceutical domain.
• Ability to understand business requirements from business users, prepare functional specifications, perform configuration changes, assist technical teams (e.g. ABAP) in their work, perform system and integration testing
• Exposure is essential to highly customized SAP environments and working on interfaces with Non SAP systems.
• Very good understanding of integration of SAP modules and end to end business processes
• Experience in New Asset accounting, Material Ledger, Accrual Engine, COGS splitting & Margin Analysis, Month end Closing Cockpit, Account and Costing based COPA
• Data Migration with SAP S/4HANA Migration Cockpit or other tools
• Ability to work in large and globally diverse / distributed teams
• Exposure to Run SAP (Solution Manager) methodologies. 
• Experience of various Estimation Techniques will be an added advantage
• Excellent communication and interpersonal skills.
• Well versed in English. Excellent spoken and written skills.
• Willingness to work in shifts and Working from Office.
• Proactive approach to problem solving. 
• Experience working in a Globally distributed team
• Awareness about SAP Activate, EML, Agile, JIRA, SAP Solution Manager, BPML & Testing Tools
• Exposure to SAP Project Systems
• Good presentation skills

Education Background

• Engineering Graduate or Postgraduate

When we put unexpected teams in the same room, we ignite ambitious thinking with the power to inspire life-changing medicines. In-person working give us the platform we need to connect, work at pace and challenge perceptions. That’s why we work, on average, a minimum of three days per week from the office. But that doesn’t mean we’re not flexible. We balance the expectation of being in the office while respecting individual flexibility. Join us in our outstanding and bold world. AstraZeneca is an equal opportunity employer. AstraZeneca will consider all qualified applicants for employment without discrimination on grounds of disability, sex or sexual orientation, pregnancy or maternity leave status, race or national or ethnic origin, age, religion or belief, gender identity or re-assignment, marital or civil partnership status, protected veteran status (if applicable) or any other characteristic protected by law.

AstraZeneca embraces diversity and equality of opportunity. We are committed to building an inclusive and diverse team representing all backgrounds, with as wide a range of perspectives as possible, and harnessing industry-leading skills. We believe that the more inclusive we are, the better our work will be. We welcome and consider applications to join our team from all qualified candidates, regardless of their characteristics. We comply with all applicable laws and regulations on non-discrimination in employment (and recruitment), as well as work authorization and employment eligibility verification requirements.

We’ll keep you up-to-date

Sign up to be the first to receive job updates.

Email Address

Confirm Email

We are AstraZeneca, one of the world’s most forward-thinking and connected BioPharmaceutical companies. Explore our world.

At AstraZeneca, our purpose is to help patients all over the world by delivering life-changing medicines as one collaborative team.

The success of AstraZeneca is founded on innovation, creativity and diversity. Discover what this means for you.

Great culture, great work assignments, supportive management. Rotation opportunity within the company. They value inclusion and diversity.

• Business IT
• Channelwise

SAP ABAP Developer (Advanced) 2628 TT

May 30, 2024

Understand the business requirements, preparing AS-IS, and TO-BE documents and get sign-off from users for Business Blueprint document

ABAP debugging beneficial (Workbench related knowledge of new development/enhancements)

Setting up the organization structure of Materials Management and perform all relevant configuration for example Purchase Organisation, Valuation Area Plants, Storage Location and Warehouse structure, etc

Preparation of testing documents and perform internal testing

Preparation of Master Data templates for various objects like Material Master, Vendor Master, Excise Master, Info-records, Source List and Purchase Orders

Integration testing with other modules

Understand interfaces, IDOC and RFC’s processing

Preparing the cut over strategy for MM objects

Preparing User manuals and conducting training to business process owners

Go-live preparation and post Go-live support

Interaction with clients through meetings, calls and emails

Handling Tickets and Tasks with the responsibility for closing the same within defined SLA’s (Service Level Agreements)

Responsible for troubleshooting issues for the system and providing support

Executing the required changes through configuration

Executing the analysis and resolution of Production Support calls

Raising Change Requests (CR’s) and writing Functional Specifications for them

Preparing test data for testing of CR’s (Change Requests)

Testing CR’s (Change Requests) and preparing test results

Carrying out regression testing

Interact with consultants of other modules

User interface transactional solutions

Proactively propose solutions to improve the support of (new) business processes

Support the functional team with issues and provide a solutions-based approach

Minimum Requirements:

Qualifications/Experience:

IT Degree and/or relevant qualifications / 7 years of SAP ABAP experience

Essential Skills Requirements:

• SAP Module Configuration
• Development documentation
• Analyse and solve SAP Module issues

Conduct SAP Module process configuration

Update and maintain all SAP Module functional documentation

Analyse and scope End-user authorisation roles

Conduct Unit tests, Integration tests and System Integration security tests

SAP ABAP Development on ECC and S/4HANA

Data services

Eclipse IDE

SAP Web IDE

SAP UI5 (simple lists) via Web IDE wizard

SAP Cloud Platform

SAP Solution Manager ChaRM

SAP Business Workflow

SAP MM-Purchasing

SAP Ariba network

SAP Ariba Guided Buying

SAP Fiori Lauchpad configuration

SAP-HCM-Personnel Administration

Any additional responsibilities assigned in the Agile Working Model (AWM) Charter

Advantageous Skills Requirements:

Formal qualification in IT (Diploma / Degree) or relevant SAP Certification

Delivery Management

Project Solution Planning, Estimation and Costing

Application Architecture

Integration Architecture

Desired Skills:

Learn more/Apply for this position