SAP Functionals

SAP Delivery (Introduction)

noreply@blogger.com (Asoka Varadhana) — Fri, 21 Mar 2014 13:52:00 +0000

The creation of the delivery note in SAP is the starting point of the delivery process in warehouse.Delivery actually is the term used to define the process in which the sales order information is passed to warehouse in SAP and the quantities are mentioned in the delivery note.

There are some salient features that needs to be noted for delivery:

1. Changes to the sales order are generally avoided once the delivery is created.

2. The delivery/deliveries are passed to warehouse in fixed intervals in form of batches. The only exception being rush orders.

3. In SAP,it is very much possible to combine multiple sales orders into a single delivery provided the shipping is to same destination with same timeline and other factors like address.

4. Manual or automatic process using the delivery due list is responsible for creation of deliveries using sales documents.

5. In SAP outbound delivery can be created after fulfilling certain criteria with reference to either

(i) Sales order

(ii) Stock transport order

(iii) subcontract order

(iv) project

(v) No reference

6. SAP has provided default delivery types for most of the scenarios. For example,outbound standard delivery has delivery type LF, returns delivery has type LR etc.The details can be checked in the SAP system using the delivery tcode(VL03n).

7. Based on customer agreements, complete and partial deliveries are permitted in SAP system. Combining of outbound deliveries into a single group of delivery is also permitted.

8. A delivery output is expected to have the following:

Billing of lading

Certificate of Analysis(CoA)

9. The delivery output can be passed to the customer either in printed paper or electronically.

10. Delivery due list is a generated list containing information on all sales documents which are due for delivery to customer with special emphasis on time and shipping point. Deliveries for sales orders and purchase orders can be taken care in delivery due list.

11.The overviews tab in delivery helps the users to monitor the outbound deliveries.

12.Picking and Post goods issue are part of the delivery process.

How to create Sales Area in R/3 System

noreply@blogger.com (Asoka Varadhana) — Thu, 12 Dec 2013 09:57:00 +0000

Sales Area is nothing but the combination of sales organization, division and distribution channel.Allthe document generated in SAP R/3 like the sales documents, delivery documents are assigned to sales area. For example, billing document cannot be created if the sales area is not provided for customer or material. Validation and restrictions can also be done with the help of Sales area. Creation of sales area allows business to structure their business operations and also help in excluding confusing combination of different organizational units.It also helps in identifying the customers indirectly . Business processes and organizational units can be streamlined as needed and thus sales area provides much help in this regards. In SAP Retail, divisions are less used, and as such sales area does not have much significance.

Each business process is unique and specified to a sales area.

For creating the sales are, one can use transaction OVXG or navigate to same using the SPRO path as below:

SAP IMG- Enterprise Structure –Assignment – Sales & Distribution – Setup sales area.

Before setting up the sales area, its important to first create the sales organization, division and distribution channel in the R/3 environment. Following the completion of same, one can proceed for creating sales area.

For creation of sales area, proceed with the following steps:

1. Navigate to the path or use transaction OVXG to enter the below screen.

2. Click on new entries and provide the values for sales organization, division and channel. In case, the values are not created, one would get the error as shown below.

1. Save the entry.

2. The configuration can be transported to other systems in landscape using the transport request.

Modification to sales area is permitted and can be done through the same transaction or SPRO path.

One can also assign sales office to sales area .This will be covered in a later article.

Assigning Sales document type to sales area –Transaction OVAZ

noreply@blogger.com (Asoka Varadhana) — Thu, 05 Dec 2013 14:18:00 +0000

In SAP, for every sales area, we need to assign the permitted sales document type. This is one of the mandatory configuration settings needed before creation of sales order document. In fact, it would error out before we enter the sales order document creation itself. Any alteration to the configuration will impact the modification of any sales document. From business perspective, it allows in separating the different business documents that can be generated from different sales units/sales areas. And this helps in proper accounting, auditing and separation of roles and responsibilities with respect to different business scenarios as far as business is concerned.

Like most configuration settings found in SAP R/3, the assignment of the sales document type to the sales area is stored in a table format. In a way, this is one of the best ways, to store such information as it helps in easy viewing and navigation for key users and consultants. Again, like other configuration navigation, searching based on the contents or field values, deletion/modification are also possible in the OVAZ transaction.

The transaction for assigning the sales document type to sales area is OVAZ and the corresponding SPRO path is as follows:

SAP IMG Path– SPRO - SAP Reference IMG - Sales and Distribution - Sales - Sales Documents - Sales Document Header- Assign Sales Area to Sales Document Types

Please note that sales area configuration has to be maintained in transaction ‘OVXG’ as transaction ‘OVAZ’ is dependent on the sales area declared and would error out in case if this is not maintained.

To assign the sales document type to sales area, follow the steps as mentioned below:

1. Goto OVAZ or the SPRO path as mentioned above.

2. Click on new entries and add the sales organization, distribution channel and division and sales order type.

3. In case after entering the sales area, an error is generated which states, its not maintained, please maintain the sales area in tcode OVXG or enter the correct sales area details in OVAZ.This would help in rectifying the error as shown in screen. Again, this all depends on the business and their needs.

4. Save the entry which results in assignment of sales order type to sales area.

The entry could be transported to other systems in landscape, like most other configuration settings. Once the setting is saved, one is free to start creating/modifying the sales document adhering to the new settings.

Maintaining sales Order types- transaction VOV8

noreply@blogger.com (Asoka Varadhana) — Tue, 29 Oct 2013 08:42:00 +0000

In the sales and distribution module, we would make use of different sales order types. Its important component of the sales order, which is perhaps the backbone of sales and order module. Sometimes, the types could be standard ones available in system and sometimes, its customer specific. Common sales order types used are for order, credit memo, debit memo etc. For creating and viewing the available sales order types, we use the transaction VOV8.

Alternatively, you can use the following path in SPRO to reach the same point:

IMG Menu Path - SPRO > IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Document Type

Once you enter the transaction, you will reach the following screen:

Here you should be able to see all the details of the maintained sales order type and along with related details.

In order to create a new sales order type, click on new entries and enter all the mandatory fields as shown below.

Please note you should add just not the order type name and the category but also all other related information like scheduling agreement, delivery details, general control etc.

Once entered and all are fine, you can save the details and the new order type should be available for use. Its always important to check the entered details before saving as this would be reflected on the configuration available in the system.

Distribution Channel

noreply@blogger.com (Asoka Varadhana) — Thu, 29 Aug 2013 17:23:00 +0000

For delivering the end products and services to the customers, a sales organization will make use of what is called “distribution channel”. A sales organization or a company can have multiple distribution channels. Different products and services might be rendered through distribution channels. In many organizations, they do have a specific strategy to align their business distribution with different distribution channels. A distribution needs to be assigned to a sales organization before its put into use.
Some examples of distribution channels are retail distribution channel, customer specific distribution channel,B2B(business to Business) distribution channel etc.Another point to remember here is that the material master data belonging to plants and prices could actually differ when it comes to specific sales organization and distribution channel. In other words, minimum quanitiy, minimum price, maximum price, delivering plants, receiving plants etc could differ. Unlike what most think, its not mandatory to create or use the distribution channel in one’s enterprise. It all depends on the enterprise setup plan and key business.

To Create/Define Distribution channel

We can reach the path for creating distribution channel by using the following path in SPRO:

IMG- > Enterprise Structure -> Definition- > Sales and Distribution-> Define/copy, delete, check, distribution channel

One can also access the above path using the transaction OVXI

For Creating new distribution channel, choose the option “Define distribution channel” and add entries to the table content.

Assigning the distribution channel to sales organization

This can be done using the below path or using the transaction OVXKN/OVXK.

IMG- > Enterprise Structure- > Assignment -> Sales and Distribution -> Assign distribution channel to sales organization

Add the entries and save it as needed and relationship would be then established.

Sales Organization in Enterprise structure

noreply@blogger.com (Asoka Varadhana) — Fri, 23 Aug 2013 02:50:00 +0000

In the Enterprise structure provided in SAP, sales organization is an important component as it’s the main unit handling the logistics.

Sales organization does the following:

1. Any action related to products sold

2. Customer deliveries

3. Maintaining business partners and contacts

4. Main force behind the selling of the products within the legal entity

5. Have an independent master and customer data, conditions and pricing policy.

The Sales organization is also attached to different distribution channels and division for providing the services and distributing the products.

A company code can have more than a sales organization. One of the main reasons for having more than a sales organization is to treat each legal responsibility as a different one, especially in a big enterprise. It helps in maintaining the transparency in different sales activities of the enterprise.

However, a sales organization is recommended to be mapped to one and only one company code. This is to avoid the confusion that can be caused with sales area with respect to the company code.Again,it could also complete the responsibilities and functionalities of different sales organizations , even if its own the system.

How to view existing Sales organization/organizations in the enterprise

Using Transaction SPRO, navigate to the following path

SAP IMG →Enterprise Structure →Definition →Sales and Distribution →Define, Copy Delete, Check Sales Organization

Here we choose whether to create a new sales organization or copy/modify the existing sales organization details. In case, we need to create a new sales organization but is similar in many ways to existing sales organization, then its highly recommended (in fact it’s a best practice) to use the copy option and copy details from existing sales organization to the proposed sales organization. After the copy is completed, the necessary changes can be made.

The same path can be traversed using the transactions OVX4 & OVX5 respectively.

In case you are going for creation of sales organization, after entering the value of the sales organization, one would need to update the address and other related details of the organization as shown in the screenshots

Sales Organization – a four character identifier is expected to be provided here. There is no predefined ways to define the sales organization and field provided is alphanumeric. So according to project coding conventions, one can provide the sales org value.

Statistics Currency –The default currency value can be provided here for the sales organization..

Content for form text modules Address Text Name, Letter Header Text, Footer Lines Text, Greeting Text Name, and Text SDS Sender are whose contents are for text modules. The values provided here, needs to be first defined in transaction SO10 and then be assigned over here. These values are used while printing in the invoices, order confirmations or other related documents.

RefSorg SalesDoc Type –This field acts as reference type, between sales organizations when they shares a similar document type assignment. The field is automatically populated when we copy one sales organization from another.

Cust. Inter-co. Bill. –The inter company customer number needs to be provided here.

Sales Org. Calendar-In case a specific factory calendar needs to be followed, the value can be provided here.

Rebate Proc. Active –This field is relevant to rebate processing in sales and distribution. Activating the field would mean that rebate processing is live for the sales organization.

RV16ACHD-Program for finding the changes to condtion records

noreply@blogger.com (Asoka Varadhana) — Tue, 26 Jun 2012 13:04:00 +0000

RV16ACHD is a useful utility program which is incorporated to report the change log for changes to condition records.

The documentation for RV16ACHD is provided in SAP R/3 system as shown in screen and it is self explanatory. According to the documentation, it states it shows change log for price condition records. However, the program also shows for rebate changes as well .The rebate parameters are available when we try to execute the program.

The program makes use of two important function modules “SD_CONDITION_CHANGE_DOCS_LOAD” and “SD_CONDITION_CHANGE_DOCS_DISPL”. The first function module gets in the details of changes recorded in tables CDHDR and CDPOS.CDHDR and CDPOS are main tables on which the function module is based on.

The important fields in CDHDR for this report are objectclas,object id,username,udate and Tcode.The condition record numbers(knumh) is recorded in the objected.The second function module makes use of data retrieved and displays on the output screen.

The physically deleted can also be provided using this report as shown in selection screenshot.

The sample output screen of the same is as shown below. It also reports the table associated with the condition record and the reflected changes,

Discussion Forum

noreply@blogger.com (Asoka Varadhana) — Thu, 12 Jan 2012 20:25:00 +0000

Stock Transfer Order/Stock Transfer Posting

noreply@blogger.com (Asoka Varadhana) — Thu, 05 Jan 2012 15:26:00 +0000

The transfer of stocks between two places is stock transfer order in layman language. In SAP, it’s a bit more than that.The places refer to plants in company codes and they could be same or different.

Now Stock transfer order is different from Stock transport order. Key differences are:

1)Stock Transfer Order is only for inventory management. The Shipping and Purchasing modules or areas are not involved,i.e. Shipping in the issuing plant or Purchasing in the receiving plant are involved.

2) Delivery costs are not involved here.

3) Movement types involved are different.

4) No plant specific configurations are needed for transfer posting.

5)Less number of transactions invoiced incase of stock transfer order.

Usually Stock transfer order can be done in 1-2 steps.

1 Step method- Simple one in fact-Use of MB1B tcode with movement type 301.Wecan use MIGO as well.

Simplest way of transferring the stocks

The stock transfer is entered as a transfer posting in Inventory Management.
The transfer posting can be planned by creating a reservation.
The quantity of the stock transferred is posted immediately from the unrestricted-use stock of the issuing plant to the unrestricted-use stock of the receiving plant
The transfer posting is valuated at the valuation price of the material in the issuing plant.
If the plants involved belong to different company codes, the transfer between plants is also a transfer between company codes. In this case, the system creates two accounting documents for the transfer posting. The stock posting is offset against a company code clearing account.

2 Step method-This is preferred when the following conditions are needed-

Long time span between leaving Plant A and arriving at Plant B
Need to control when goods leave plant A but not received at plant B

The stock transfer includes the following processes:

A goods issue in the issuing plant
A goods receipt in the receiving plant

Transferring stock in two steps has the following characteristics:

The transfer posting cannot be planned by creating a reservation, which makes it different from 1 step transfer
The quantity posted from stock is first of all managed as stock in transfer in the receiving plant. Only once the goods receipt has been posted is the quantity posted to the unrestricted-use stock of the receiving plant.

This enables the quantity "on the road" to be monitored.

The transfer posting is valuated at the valuation price of the material in the issuing plant.

If the plants involved belong to different company codes, the transfer between plants is also a transfer between company codes. In this case, the system creates two accounting documents when the goods issue is posted. The stock posting is offset against a company code clearing account.

Inquiry Creation in SAP

noreply@blogger.com (Asoka Varadhana) — Tue, 24 May 2011 17:03:00 +0000

One of the first things involved in Sales and Distribution cycle is in creation of inquiry.

We can do this with help of the transaction VA11 or by following the path: Sales and distribution -> Sales -> Inquiry ->Create

An inquiry document can be considered more or less like an internal document.It is not a legal document , but a document to capture information about the details fo the request from prospective customer and to internally circulate within the company. Most of the times, the information captured is about the material and quantity but the rest of the information are not essential. One of the benefits of have an inquiry created is in the reduction of any business overhead needed while replying to the customers.

In many cases, we do not create inquiry, especially when we have all the necessary inputs/information for the subsequent documents,i.e sales documents. But in case, these are not available, it is considered to be a best practice to create an inquiry document.This would help in future to determine the terms and conditions, price and quantities offered to the customer and mostly to help create the quotation document.

In the Create Inquiry screen, give Quotation type, Sales organization, Distribution channel, Division, Sales office and sales group.

Pass Material, quantity, sold-to party, ship-to party. Rests of the fields are optional. Again, the unit of measurement for the material could be checked with F4 after populating it.

Bill of Lading

noreply@blogger.com (Asoka Varadhana) — Sat, 07 May 2011 12:11:00 +0000

One of the most vital documents, especially in the shipping industry is the Bill of Lading.Bill of Lading is usually created by the carrier or the responsible agent from the supplier side.It ensure all the legal proceedings as per the understanding is undertaken.The supplier or carrier is supposed to send the buyer the Bill of lading through any communication channel.The buyer has to produce this bill of lading to claim the goods that needs to be delivered.

The Bill of Lading should contain the following information:

1)Name of the Transporting company

2)Flag of the nationality

3)Shipper's name

4)Order and notify party

5)Description and weight of goods

6) Freight or other rates and taxes as applicable

There are different types of Bill of lading.We shall look at two of them.

1) Non-negotiable Bill of lading/Straight BOL- In this case, the buyer has to fulfill all the legal contract obligations(E.g Payments), to get the goods released from the port.This bill states that the goods are consigned to a specified person and it is not negotiable free from existing equities, i.e. any endorse acquires no better rights than those held by the endorser. So, for example, if the carrier or another holds a lien over the goods as security for unpaid debts, the endorse is bound by the lien although, if the endorsor wrongfully failed to disclose the charge, the endorsee will have a right to claim damages for failing to transfer an unencumbered title.

2)Bearer Bill of Lading-This document allows the goods to be delivered to the holder of it. The name of the consignee, to whom the goods have been sent, perhaps the buyer, may be stated as "bearer". It may also be an "Order bill of lading" without stating to whose specific order the bill, and delivery of cargo under it, are subject or it could be an "Order bill of lading" endorsed in blank, that is without identifying to whom the cargo should be delivered.

Assigning Purchasing Organization to Company code & Plant

noreply@blogger.com (Asoka Varadhana) — Sun, 01 May 2011 09:22:00 +0000

To assign a Purchasing Organization to Company code:
You can either use the Transaction Ox01 or goto IMG and select the option as shown(This is done after going to transaction SPRO and selecting IMG).

You will See the Purchasing Organization that is reated or which exists in the system(OX08).Assign the same to the neccessary company code.And save the entry.

To assign the Purchasing Organization to Plant:
First goto to the same path in IMG(as shown earlier) and take the next option after the assignment to company code.This can also be done through transaction Ox17.Again, this is to be saved as a table entry.

Purchasing Organization

noreply@blogger.com (Asoka Varadhana) — Sat, 30 Apr 2011 13:20:00 +0000

A normal Enterprise would look like this from a MM perspective

A purchasing organization is an entity or organizational level that negotiates conditions of purchase with vendors for one or more plants. It is legally responsible for completing purchasing contracts. In other words, a purchasing organization is the entity that procures materials and its related services, negotiates conditions of purchase with vendors, and bears responsibility for such operations or transactions.

The form of procurement is specified through the assignment of purchasing organizations to company codes and plants or either one of them.

The form of procurement is possible in following ways:
1)Enterprise-wide: One purchasing organization procures for all the company codes of a certain client (that is, for all the individual companies of a certain corporate group) .

2)Company-specific: One purchasing organization procures for just one company code .

3)Plant-specific: One purchasing organization procures for one plant .

Mixed forms are possible, which are replicated in the system with the aid of reference purchasing organizations. This could be more specific ones.

A purchasing organization can exist without being assigned to a company code. Since each plant must be assigned to a company code, the company code can be determined via the plant.One plant can have one or more Purchasing Organizations.Each purchasing organization has its own info records and conditions for pricing.Each purchasing organization has its own vendor master data.Each purchasing organization evaluates its own vendors using MM Vendor Evaluation.

To create a Purchasing Organisation in SAP:

This is possible through SPRO or directly through the transaction Ox08.

The path that needs to be followed in IMG is as shown below(IMG->Enterprise->Definition->Materials Management->Maintain purchasing organization).The entry is maintained in a table format.

Table to get the details of creation,modification and deletion through a tcode-CDHDR

noreply@blogger.com (Asoka Varadhana) — Fri, 29 Apr 2011 03:19:00 +0000

This is a very useful table for all document details created through a transaction.This could be any tcode like Su01,Vao1, mm01 etc.Any object which is created, edited or deleted is logged in this table.Suppose you do not know the document number which was created in your system a few minutes ago.By giving the necessary time, date and transaction code, one could retrieve that information.One could also get the information when the object gets edited through transaction through this table.The username also gets logged in alongwith the information.For more details on line items, get the information of the document number from here.And then check the same in CDPOS.

Cost centre

noreply@blogger.com (Asoka Varadhana) — Sun, 20 Mar 2011 11:10:00 +0000

Cost center is that part/parts of an organization/company that indirectly contributes to profit, but has no direct involvement. In addition it adds to the cost of running a company in various ways.. Research and development centers are typical example of cost centre.

Although in facts and figures, cost center may not show any demonstrable profit.However, it can add to revenue in various ways. Innovations or fulfillment of things can help for organization.

Because of the cost factors involved compared to profit, Cost centre is seen to have a negative impact on profit. Financial investments on the infrastructure and resources are at times, not quantified to facts and figures or for that put into statistics to justify decisions. As such Organizational decisions (like cutoff and things) are mostly for Cost centers.

Cost centre in SAP

Cost centres are based on controlling areas in SAP
To see the different categories of cost centres available and to add, we use tcode OKA2

To see the cost centre heierachy as it is KSH2.

The below screenshot is KSH2 view of CO area CO01.

VKM3

noreply@blogger.com (Asoka Varadhana) — Sat, 19 Mar 2011 12:04:00 +0000

This tcode is used to release the credit block at sales order level. The most important difference between VKM1 and VKM3 is that VKM1 will show both sale order and delivery and you can block even the delivery if it is not PGId. On the other hand, VKM3 will list only sales orders.

In fact, both VKM3 and VKM1 use VKM4 programmatically to release the blocks. If you check with help of SE93, the program for VKM3 is RVKRED04 and VKM1 is RVKRED02.And the program associated with VKM4 is RVKRED01.If you check in the codes of both programs, you would see that there is usage of RVKRED01 in same, which is nothing but VKM4.The screen of VKM3 after execution looks like this.

The first button at top helps us to check the document as such.
The Green flag button helps us in releasing the document
The third button is for reassigning the document
The fourth button is for rejecting the document. You would also need to specify the reasons.
The fifth button helps the analyst to check the order and forward it to a credit manager. One can also do this by Ctrl + Shift + F8
The 'Forward to authorization' button is used for payment cards.

Product Hierarchy

noreply@blogger.com (Asoka Varadhana) — Wed, 23 Feb 2011 16:33:00 +0000

Product hierarchy is a relationship model for better analysis on objects and pricing.
The product hierarchy Structure is maintained in the structure PRODHS. In the standard system, the product hierarchy consists of up to 3 levels. The first and second levels have 5 digits and the third level has 8. The maximum number of digits is 18 and the maximum number of levels is 9.
You can define hierarchy nodes at the individual levels of the product hierarchy.

In the standard system, the product hierarchy consists of up to 3 levels. The first and second levels have 5 digits and the third level has 8. The maximum number of digits is 18 and the maximum number of levels is 9.
You can define hierarchy nodes at the individual levels of the product hierarchy.
If you want to change the standard setting of PRODHS, e.g. you want to change the number of levels, proceed as follows:
1. Create an appropriate domain in the Data Dictionary (type CHAR with the required length).
2. Assign these domains to the standard data elements PRODH1, PRODH2, ..., PRODH9.
Please note that you should use these standard data elements.
3. Change the structure PRODHS by creating or deleting fields with reference to the data elements.
Choose ZZPRODHN as field name, where n is the position of the field in the structure PRODHS.

Also for the maintaining the product hierarchies, most use the transaction OVSV

PositivePay Service(Check Extraction)

noreply@blogger.com (Asoka Varadhana) — Wed, 23 Jun 2010 13:24:00 +0000

Positive Pay Service:

This is a service in which the company would be sharing their cash register (The master data for all account transactions) of all written checks with bank. The Bank would verify all the data with respect to specifics like payee, serial number, date, amount etc and would only pay for the checks listed in the cash register. This drastically reduces the check fraud.

How it is implemented in SAP:

This is associated with transaction FCHX with program name as RFCHKE00.

The Title of the program is Check extract creation.

Attached is the functional overview of the program(You can get this from program documentation also).

Short text : Check Extract Creation

Description : This program creates a file of all check information belonging to a paying company code,providing this fulfills the specified selection criteria. The data in the file is sorted according to account number and check number and its format corresponds to the internal format of the DTACHKH and DTACHKP structures.You can generate a log of the created extract using program RFCHKN00. Specify the extract creation date and time.

Requirements: The user must be authorized to display check information in the company code requested.

Output : Here are some examples of the possible selections:

1. Selection of all not yet extracted checks

All not yet extracted checks with the specified currency and house bank are output, provided you enter no further selections. With additional selections however, you can define the output in detail by specifying individual payment methods, amounts and void reason codes.

Note: A check is categorized as not yet extracted (and is selected).

if it-

- is new in the system

- was extracted in a previous run but has since been changed,(voided, for example). In this instance too, the bank must be informed about the new status of the check.

2. Selection of checks in a payment run

By specifying the payment run date and identification, you can limit the number of checks to be selected. The program can also be scheduled as a list via the payment program.

3. List of checks in an extract

If you want to make a further copy of an extract, enter the extract date and time. If an extract is copied, the database is not updated. If none of the three selections is chosen, the output will cover the whole database.

If you enter the initial value "00" in the "Void reason code" field, only valid checks are selected. A so-called positive payment file is created. To select all checks you should delete this entry.

What is Company Code in SAP?

noreply@blogger.com (Asoka Varadhana) — Sat, 26 Dec 2009 12:02:00 +0000

A company is an organizational unit in accounting that represents a business organization in a particular country. Company code represents an independent accounting unit. In other words, it is a legal entity responsible for statutory reporting. For example,IBM is a company, but IBM consulting services is a company code.

The information that a company code can provide us include:

1)Company address
2)Chart of accounts
3)Balance Sheet currency
4)Fiscal year variant
5)Controlling area
6)Business area

SAP recommends that one use EC01 to copy an existing company code to a new one. This has the advantage that you also copy the existing company code-specific parameters. If necessary, you can then change certain data in the relevant application. This is much less time-consuming than creating a new company code.

Other transactions that could come handy in case of company code creation are:

OKKP - Assign company code to the controlling area

OBY6 - Define company code global parameters

OB62 - Assign company code to chart of accounts

OBA4 - FI Tolerance Group for Users

FBZP - Maintain Payment program

OBYA - Inter Company code clearing if being used