The way in which profitability segments are stored and numbered in the system has been modified. A separate type of profitability segment is now stored in table CE4XXXX_ACCT  (XXXX denotes the operating concern). Just as with the profitability segments in table CE4XXXX , those in table CE4XXXX_ACCT assign a unique number to each combination of characteristic values. However, in table CE4XXXX_ACCT  a new number is assigned for each new business process. Furthermore, characteristic summarization is not applied to this table

Up to and including SAP S/4HANA 1610, the profitability segment numbers are reused. That is, if two business processes are assigned to the same combination of characteristic values, only one entry is created in table CE4XXXX  and the same profitability segment number is used by both processes

One drawback of this solution is that it can degrade performance in systems containing large amounts of data because each new business process attempting to assign a profitability segment number for its characteristic values has to read table CE4XXXX  to determine if this combination already exists or if a new profitability segment number needs to be assigned. Another drawback is that characteristic summarization (transaction KEQ7) is applied to table CE4XXXX such that information sometimes gets lost unexpectedly in a business process if a characteristic is summarized

Therefore, starting with SAP S/4HANA 1709, an additional type of profitability segment is (re-)introduced (see SAP Note 199467). These profitability segments are stored in table CE4XXXX_ACCT. Just as with the profitability segments in table CE4XXXX, those in table CE4XXXX_ACCT assign a unique number to each combination of characteristic values. The difference is as follows:
● In table CE4XXXX_ACCT, a new number is assigned for each new business process instead of reusing the existing numbers.
● Characteristic summarization is not applied to table CE4XXXX_ACCT.

Note that there are three cases in account-based profitability analysis where profitability segments are created only in table CE4XXXX:
● Cost center assessment to profitability analysis
● Top-down-distribution
● Classical planning functionality like transaction KEPM

 

SAP S4HANA Customers & Vendors Integration (CVI)

 

Customers & Vendors Integration (CVI) are considered one of the top items in SAP S4HANA simplification list

BP transaction code which is know for Business Partners is the single point of entry to create, edit, and display master data for business partners, customers, and vendors as well

In S/4HANA all the previous ECC transactions, reports, conditions records, forms, etc. which use customer or vendor number will continue using the customer or vendor number. Even a new BP number is assigned to customer or vendor, the ECC customer or vendor number still has to be used.

 

ECC transactions that are no longer available or redirected (where possible) to transaction BP:

FD01, FD02, FD03, FD05, FD06, FD08FK01, FK02, FK03, FK05, FK06, FK08MAP1, MAP2, MAP3MK01, MK02, MK03, MK05, MK06, MK12, MK18, MK19V-03, V-04, V-05, V-06, V-07, V-08, V-09, V-11, V+21, V+22, V+23VAP1, VAP2, VAP3VD01, VD02, VD03, VD05, VD06XD01, XD02, XD03, XD05, XD06, XD07XK01, XK02, XK03, XK05, XK06, XK07

 

Simplification List Item Description:

• The (mandatory) target approach in SAP S/4HANA is the Business Partner approach (Customer-Vendor Integration [CVI]).
• Business Partner is now capable of centrally managing master data for business partners, customers, and vendors. With current development, BP is the single point of entry to create, edit, and display master data for business partners, customers, and vendors.
• The specific tables for customer data (KNA1) and vendor data (LFA1) remain available and are not impacted.

Note: It´s recommended but not mandatory that Business Partner ID and Customer-ID / Vendor ID are the same.

 

S/4HANA future-oriented Business Partner

- A legal entity is represented with one Business Partner, one unique Business Partner for different roles e.g. Customer, Supplier, Contact…

- Different Business Partner Categories –Organization, Person, Group

- Maximal data sharing and reuse of data which leads to an easier data consolidation

- General Data available for all different business partner roles, specific data is stored for each role

- Several Addresses possible with a default Address

- Time dependency on different sub entities e.g. roles, address, relationship, bank data etc.

 

Main Configuration Steps:

1- Activate the PPO Request for the synchronization object Business Partner

2- Check that Active Synchronization between Customer/Vendor and BP is active

3- Create Business Partner number range and grouping

4- Assign number ranges to BP Grouping

5- Assign BP Role to Customer/Vendor Account Group

6- Assign Grouping to Customer/Vendors Account groups

7- Activate Postprocessing Office

8- Run Report MDS_LOAD_COCKPIT, It creates a corresponding SAP business partner for the customer, vendor and contact data for general data, addresses, role data, bank details.

 

 

New SAP S4HANA SE16H - Forget about SE16N, SE11, SQVI

 

Hello SAP Consultants

Today we have one of the great innovation that SAP made since 2012 and fully available on SAP S4HANA

Transaction SE16H provides an advance development as part of the SAP HANA development.

You can use this transaction to access data from the SAP HANA database directly from the ERP system and to display this data in the ERP system.

We used to use the transactions code SE11/SE16/SE16N/SQVI to check table’s value and extract data.

 

Solution in brief

In addition to the functions of transaction SE16N, transaction SE16H also provides the following options:

*  New field "Database Connection":

                                   ·          In the "Database Connection" field, you can display and select the available database connections using the input help.

                                   ·          The accesses are then executed using the relevant database connection selected.

                                   ·          If a database connection was selected, the input help for the "Table" field displays the tables and views that are available in SAP HANA.

                                   ·          The number of rows in your current system/client may therefore be lower than the number displayed.

                                   ·          Note that transaction SE16H is able to check only the physical connection to the database. The table created in SAP HANA must correspond exactly to the definition in the SAP ERP Dictionary.

Database Connection

 

 

*  New column "Group":

                                   ·          In this column, you can enter any group or set that corresponds to the relevant field (selection using F4 help is possible).

                                   ·          This is particularly useful if groups are used, for example, account groups, order groups, and so on.

                                   ·          In case we want to have a quick view of the number of accounting entries by company code, we have to tick the field group and execute.

Group Column

 

*  New column "Total":

                                   ·          If you select this field, all rows found that correspond to the grouping rule (see the new column "Group") are accumulated. As a result, you can generate aggregated views for a large amount of data that, for example, displays a value for each account for each period.

 

Total Column

 

*  New column "Sort":

                                   ·          If you select this column, the system sorts the number of hits using this field.

                                   ·          You can also do this using a default layout in the SAP List Viewer. However, the data is subsequently sorted, whereas the "Sort" column sorts the data directly from the database.

Sort Column

 

*  New column "Highest/Lowest":

                                   ·          After executing this, the system returns the largest postings in the object together with their frequency based on the number of hits you requested

 

*  New column "Sequence":

                                   ·          If you use the functions mentioned above (sorting with highest/lowest), the sequence in which the fields are sorted is relevant. If you enter something in this column (values from 01 to 99), the fields are sorted in the sequence from 1 to 99. If you do not enter anything in this column, the fields are sorted according to their occurrence in the table.

                                   ·          If you mix fields that have explicit values from 01 to 99 with fields that do not have a value in this column, the fields without values are added according to their occurrence after the fields with a value.

Seq Column

 

*  New column "Aggregate":

                                   ·          In this column, you can choose between the aggregations "Maximum", "Minimum" and "Average". Depending on the data type, not all aggregation functions are available. You can either aggregate or group/total a field.

Aggregate Column

 

*  New field "Outer Join Definition":

                                   ·          This function corresponds to a basic view definition for tables that contain only additional information about the selected table (for example, to read texts).

                                   ·          You cannot map any inner joins - that is, you cannot define restrictions that must be met for more than one table. The outer join definition is used only to read additional attributes from a user-selected database connection for the selected table. This means that, for example, postings can be read from a SAP HANA database and the texts for the resulting quantity can subsequently be read from the normal ERP database.

 Outer Join

 

 

 

Example:

1- This is the New Selection Scree for SE16H rather than the old SE16N interface

SE16H

 

2- Now we will prepare an Outer Join Query using SE16H instead of SQVI or SQ01-02-03

First Select The Primary Table for example LFB1

Second Select "Outer Join Definition"

 

3- Select Secondary Table for example LFA1 then Press Save

 

4- Choose Output yellow arrow to select required columns for display in the report

 

 

5- If you want to restrict the output based on a specific value on a specific field as a predefined filter you can use the second part of the screen

 

6- Then Press Save

 

 

7- Select Which fields you want from the Primary table as well then press Execute

 

 

Finally After executing SE16H with the outer joint you have created you will find exactly the data required from the two tables in one ALV grid with a button click in seconds

 

Hope you try it in you systems, Good Luck :)

 

 

 

Financial Close

Closing operations are periodic tasks and can be subdivided in FI as follows:

  • Day-end closing
  • Month-end closing
  • Year-end closing

The closing operations component helps you prepare and carry out the activities required for day-end, month-end, and year-end closing. For this purpose, the system provides a series of standard reports that you can use to generate evaluations and analyses directly from all of the posted account balances.

The reporting tools and existing reports can be used to satisfy reporting requirements in most cases. In the area of Accounting, various reports can be used to obtain information about all fields of Financial Accounting.

Closing Activities

G/L Accounting

  • Postings incl. (new posting, displaying single documents, changes in documents (what is allowed))
  • Post Parked Documents
  • Display GL documents, values and balances.
  • Document reversals (single, mass)
  • Recurring entries – maintenance
  • Period End (Day End, Period End, Year-End)
  • Update exchange rates
  • Enter Accrural/Deferral Journal Entries
  • Reverse Accrual/Deferral Document
  • Account maintenance – clearing
  • Controlling of integrity:
    •        Gaps in document numbers
    •        Invoice numbers allocated
  • Recurring entries
  • Automatic Clearing of GR/IR Account special process
  • Manual Clearing
  • Assets Depreciation Run
  • Settlement Of Assets Under Construction - AIBU
  • Closing the Asset Year and Change the New Year - AJAB
  • Post Adjustment Entries
  • Update Exchange Rates
  • Foreign Currency Revaluation
  • Run interest Calculation
  • Run Dunning for customers
  • Bank Statement Reconciliation
  • Post Saved transaction in Cash Journal
  • Post Tax Payable
  • Record of Sales and Use Taxes Report
  • Controlling:
    • Run Assessment and Distribution
    • Run Overhead Costing sheet
    • Calculate WIP
    • Order Settlement
  • Close Previous Accounting Period
  • Carry Forward for Balances
  • Create Factory Calendar for New Year
  • Carry Forward for Fixed Assets – Reference
  • Carry Forward AP/AR Balances
  • Final Close and Release Financial Reporting
  • Close Previous Accounting Period FI & CO
  • Carry Forward for Balances
  • Create Factory Calendar for New Year

 

Roles:

Assign the following business roles to your individual test users.

 

Business Role Name

Business Role ID as Delivered by SAP

General Ledger Accountant

SAP_BR_GL_ACCOUNTANT

Accounts Receivable Accountant

SAP_BR_AR_ACCOUNTANT

Controller

SAP_BR_CONTROLLER

Accounts Payable Manager

SAP_BR_AP_MANAGER

 

 

 

 

 

 

 

 

 

Reference: Accounting and Financial Close (J58_US)