Central Finance 1709 Features and Limitations
Central Finance 1709 Features and Limitations
Limitations
Central Finance (CFIN) is a solution where we can enable in S/4 HANA system itself (with a
Separate License) to facilitates and connect to Replicate the Finance (only) real time data from
any SAP Or Non- SAP (any ERP) system into S/4 HANA system.
First CFIN introduced in SAP S/4H 1503(Simple Finance 1.0) on premise edition as Central
Journal. Central Finance has undergone significant changes over past couple of years. As of now
on premise 1709, Central Finance is further enhanced to support Central
Payment, Central Tax Reporting and 3rd party system process integration
Central Finance system is not a standard lone system. It can be enabled in S4H Finance system
through Business function FINS_CFIN activation, So that, system will provide necessary
configuration, process and error handling nodes in S/4HANA system.
· Central Tax Reporting – 1709 version onwards, tax reporting can be performed
from CFIN; Sales tax calculations are still not possible for source system sales and purchases.
However, GL line items carry tax information for reporting purposes. This reporting is still
evolving as part of 1709, But restrictions apply
· Central Payments - 1709 version Central Payment system is enabled and open items
can be applied in Central System. This brings considerable value to the Business. & also It gives
the option of enabling Single Euro Payment Area (SEPA)
Limitations of Central Finance
· Fixed Assets – Fixed Assets lines in source system are not replicated into Fixed Assets
in CFIN. Asset and Depreciation journals in source system do replicate in CFIN, but as General
Ledger entries only
· Special Purpose Ledger – If source system has SPL part of their process landscape
and having special ledger reporting, these postings are not replicated in CFIN.
· CO-PA – All COPA Characters and Filed will replicate along with Finance Document
only. But if CO-PA is implemented in source system and if there are internal postings for stock
movements in profit center valuation, they are not replicated in CFIN system.
· Sales Orders as Cost Objects – If source system line items are posted with Sales
Orders (generally in COPA with Make to Order scenario), Sales Orders are not replicated into
CFIN. A unique set of Internal Orders may be mapped to this scenario
· Settlement Rules – Settlement rules in source system are not replicated in CFIN
· Tax Reporting – Even though tax reporting is available as of on premise 1709, many
restrictions exist and this process cannot be used for productive purpose as of now
· Document Reversals – Some restrictions apply for reversing the documents in
central system
· Functional Area – Functional Area derivation is not supported in CFIN system. But
still you can Map & derive it through Cost Center Master.
· Parking Documents – Documents parked in source system are not replicated into
Central System
TAG: MIGO
MM TRA NSACTION CODES
Posted on May 18, 2013 by Jayanth Maydipalle
SOURCE LIST:
PROCUREMENT
Create,Change, Print Purch Requisition w/ & w/o Mat’l Mastr; Assign Sources ME51/ ME56/ME57
INVOICE VERIFICATION
Source List:
Purchase Requisition:
Quotations :
ME47 – Create Quotation
ME48 – Change Quotation
ME49 – Price Comparison
Purchase Order:
Reservation:
Inventory Count:
Still all the functions and procedures remain same and the post below can teach a user of EHP7 environment
also about Number ranges, when he identifies the icons and correlates the to the corresponding activity..
Let’s start
A Number range is a Group of numbers to which the unique-Id created for an SAP Object belongs. In each
module we have masterdata having SAP objects such as Equipment, Notification, Order, Measuring Point,
Maintenance Plans etc in PM, Material number, Material Document, Purchase Requisition, Purchase Order in
MM, Sales Order, Sold-to-party etc in SD, Production Order in PP, Inspection lots in QM and the list is long.
This document is intended to give basic concepts of Number Ranges we need to create during the
Configuration of various modules in the implementation time and after. In this document we try to understand
these things through a Plant Maintenance object , namely Equipment .
Before starting our job related to Equipment, let’s understand few generic things about Number Ranges.
Types of Number Ranges
There are 2 categories of number ranges:
Internal numbers: These are purely numbers. System generates the number (within the range you’ve specified)
next to the immediate previous allotted number.
External numbers: This is where the person creating the SAP object (e.g., Equipment) is required to enter his
choice of number. This will be as per the alpha-numeric pattern he has already declared while creating the
number range.
T-Codes
There are configuration paths in each module for respective objects to Define respective number ranges. Also
many objects have Tcodes. Here we see the Tcodes for Defining number ranges in PM module.
SAP-PM Object Tcode
Equipments OIEN
Notification IW20
PM Order OION
Revision DIWPS_REVNRS
Few examples:
SAP Object Category
In the number ranges configuration-screen you get these Categories, where you need to assign this
category/type to a particular number range group. Where from these Groups come? These Groups are nothing
but the Number ranges we need to create. One Number range group for one or more Categories of SAP Object,
(i.e., Equipment in present case). See this picture:
Here Groups are Test, Standard Number range, Mechanical Equipment, Electrical Equipment,
Instrumentation. Under each group different categories of Equipments are seen.
Now let’s start how to create a new internal number range for an Equipment and assign few categories to it .
Tcode OIEN
Click on the Groups icon. to arrive at the picture referred in the beginning. Here you use the menu GoTo –>
Insert OR
hit F6 function key to get this pop-up.
Now, Give a title to the Group (Say Demo), give some number range say 000000000010000000 to
000000000019999999 to the Group and upon clicking the Add icon, system might give you the following
error messages, telling that this range is interfering with some other Group already existing. i.e., some overlap
between.
(In case no such overlap is there, then the Group will be created)
Assuming that overlapping is there, identify the overlapping Group, tick-in the checkbox and go to
the maintain screen like below .
See here upper range 000000000019999999 has been modified as 000000000014999999.
Means we have freed numbers from 000000000015000000 to 000000000019999999. Now again GoTo –>
Insert and repeat the New Group (Demo) creation. Now it will be accepted.
Thus,we have created a Group named Demo. See this is visible in the list of Groups.
Now we will try to assign one Equipment category to our new Group.Let’s suppose, we want to shift
Category G Equipments to this new Number Range. For this follow this procedure.
1.Mouse click on the Category G in the present position where it is .
2.Tick the check box of the target Group, here it is Demo like this
Everything has been done. Now the Category G Equipments when created through IE01 will be given the
numbers specified here.
Let’s learn about Few clicking sequences for Assigning and Not Assigning the Categories to Groups.
Case1: Unassigning a Category from any Group.
Let’s suppose I want to unassign Category H . Means I want to bring it to the Not assigned list at the bottom.
Follow this mouse click sequence.
Means
1.Click on letter H (Remember the checkbox of this Group should not be ticked-in)
2.Then click on the icon at the top.
3. Then on Not Assigned at the bottom
Means
Important:
For alphanumeric external number ranges in Equipments you need to have the following setting in the SPRO
of Equipment Categorisation.
Path:
Setting
See, for Alpha numeric number Ranges the Checkbox under column a should not be ticked-in.
Note:
Though concepts were explained with Equipment number as example, there is an identical dealing
with all other number ranges, irrespective of which module does it belong to.
And most importantly Number ranges are not recommended to be transported from Dev client to
PRD. They should be locally created in PRD client.
For many standard number range objects (like QMEL_NR for Notification and AUFTRAG for Order) a
Buffer value is maintained. This is ’10’ for Notification and ’20’ for Order. For present case
of EQUIP_NR there is no buffer is maintained.
Very often you notice skipping of numbers while creating Notifications or Orders in PRD client. This is
due to the buffer value.
The buffer is important in multiple server scenario where one client has several like in PRD client.
This Buffer value helps in quicken the process of allotting a number to the Object by the system.
Had this Buffer not been there, system takes too long to Save an Object while creating due to
contacting all servers and deciding the next consecutive number in the series.
We can create our own Number range object in SNRO and use it in developments in combination
with a function module ‘NUMBER_GET_NEXT’ , during the situations where we need to have an auto-
number generation for custom objects..
The SAP transaction code SNRO allows you to create and maintain number
ranges for use with you ABAP programs. Below shows you the simple steps
required to create a number range. In-order to access the next number in the
range from within your ABAP code simply call function
module NUMBER_GET_NEXT with the relevant details.
Fill in the appropriate details such as the from and to number, then Press the
insert button (+) to add the interval to the number range object.
Also please note the id(No) will except 01 or 1 and when you execute FM
NUMBER_GET_NEXT you will need to pass the exact id you enter here, also
make sure you create them the same on each system (i.e. DEV, QAS, PRD etc)
otherwise it will work on some and not the others.
Use function module NUMBER_GET_NEXT in your ABAP code to get next number
in your number range
Also just for information the Number range details are stored in the following
tables:
TNRO - Numnber ranges
NRIV - Number range intervals