Vous êtes sur la page 1sur 40

JNJ_CH_ Posting to finance implementation

HOW TO

JNJ CH

September 2012
Posting to finance implementation
06/09/2011

Version management
Version Date Author Comment
v1.0 06/09/2012 Melisa Titos Document Creation

Document distribution
Name Role Organization

Reference documents
Version Date Name

Confidentiality/Disclaimer:
This document and all information contained within is the property of NORTHGATEARINSO
International (hereafter referred to as NORTHGATEARINSO). It is issued in confidence and must not
be reproduced in whole or in part or used or given or communicated to any third party without the prior
written consent of NORTHGATEARINSO.
This document does not form or constitute part of a contractual agreement, and its submission does
not imply acceptance of any commercial terms.
Any statements and recommendations made or advice given shall not in any circumstances be
deemed to constitute a warranty by NORTHGATEARINSO as to the accuracy of such statements,
recommendations or advice. NORTHGATEARINSO shall not be liable for any loss, expense, damage
or claim arising from the statements made or omitted to be made, or advice given or not given in this
document.

Proprietary and Confidential to NorthgateArinso Page 1


Posting to finance implementation
06/09/2011

Copyright NorthgateArinso International 2008


Table of Contents

1 GENERAL INFORMATION................................................................................................................... 3
2 TECHNICAL SPECIFICATION OVERVIEW.............................................................................................. 4
2.1 Solution description................................................................................................................ 4
2.1.1 Definition of feature PPMOD..........................................................................................4
2.1.2 Parameter Modifier for Chart of accounts.......................................................................8
2.1.3 Assign WT to Main Symbolic Accounts........................................................................10
2.1.4 Additional Symbolic Account Definition.........................................................................11
2.1.5 Assignment of WTs to Additional Symbolic Accounts.................................................12
2.1.5 GL Account Definition................................................................................................... 14
2.1.6 Assign Additional Symbolic account to GL Accounts....................................................15
2.1.7 Posting Run.................................................................................................................. 17
3. FI Account Definition (SAP)...................................................................................................... 19
3.1 T030........................................................................................................................................... 19
3.2. G/L account master record maintenance (FS00).................................................................25
3.3. Cost Element....................................................................................................................... 29
3.4. Accounting Document Number Ranges...............................................................................31
3.5. Maintain Number Ranges for CO Documents......................................................................32
4. To take in account.................................................................................................................... 33
4.2. Delete Cost element............................................................................................................. 33
4.3. Technical Account................................................................................................................ 34
4.4. PCP0.................................................................................................................................... 36

Proprietary and Confidential to NorthgateArinso Page 2


Posting to finance implementation
06/09/2011

1 Ge ner al i nfor mati o n


Aspect Description
Customer JNJ
euHReka Yes
Dedicated No
ERP release 700
HR release 600
Client ED5

Proprietary and Confidential to NorthgateArinso Page 3


Posting to finance implementation
06/09/2011

2 Te c hni c al spec i fi c at i on
ove r vie w
The goal of this document is to describe the technical implementation related to Posting
Configuration for the JNJ customer CH.
The document will describe the specific components and other operations performed in the system.
This includes creation of several entries in several tables.

Requirement:

Copy of Functional
Specifications Payroll v01 00 Appendix 2b (3).xlsx

Above, there are the specifications to map WT to symbolic accounts and these to global accounts for
the Financial Posting (is just an example).

2.1 Solution description


2.1.1 Defi nition of feature PPMOD

Y00BA_PE03_CUSTOMER Create Feature PPMOD and insert just one node with the report
ZCHPY_PRO_RE_JNJ_PPMOD.

This feature returns the value which is used as modifier to map the euHReka symbolic accounts to the
euHReka GL accounts.

The report return the modifier value asking first for the payrollarea and then for the businessarea
reading from the table ZCHPY_TAB_JNJ_PM.

Proprietary and Confidential to NorthgateArinso Page 4


Posting to finance implementation
06/09/2011

Report ZCHPY_PRO_RE_JNJ_PPMOD:

The program get the personnel number fixing it from a program RPCIPE00 (table PERSON-
ALL_PERNRS) so its able to select the business area and payroll area from IT0001.

REPORT zchpy_pro_re_jnj_ppmod.

*&---------------------------------------------------------------------*
*& Form ext_call_f
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* -->NAMEN text
* -->BACK text
* -->STATUS text
* -->STRUC text
*----------------------------------------------------------------------*
FORM ext_call_f USING namen back status struc STRUCTURE pc205.

DATA: lv_pernr TYPE hrp1001-sobid,


lv_pernr2 TYPE pa0001-pernr.
DATA: it_pa0001 TYPE TABLE OF p0001 WITH HEADER LINE.
DATA: l_modifier TYPE p_momag40.
data: LT_PERNR type table of PCCE_PNP_PERSON_PERNR,
wa_pernr type PCCE_PNP_PERSON_PERNR.

FIELD-SYMBOLS <ALL_PERNR>.
DATA external_var TYPE STRING value '(RPCIPE00)PERSON-ALL_PERNRS[]'.

*- Obtaining employe PERNR from position

ASSIGN (external_var) TO <ALL_PERNR>.


LT_PERNR[] = <ALL_PERNR>.

* SELECT sobid FROM hrp1001 INTO lv_pernr


* WHERE otype EQ 'S'
* AND objid EQ struc-plans
* AND rsign EQ 'A'
* AND relat EQ '008'
* AND sclas EQ 'P'
* AND begda LE struc-endda

Proprietary and Confidential to NorthgateArinso Page 5


Posting to finance implementation
06/09/2011

* AND endda GE struc-endda.


* ENDSELECT.
read table lt_pernr into wa_pernr index 1.
if sy-subrc eq 0.
lv_pernr = wa_pernr-pernr.
endif.
IF NOT lv_pernr IS INITIAL.

REFRESH it_pa0001.
lv_pernr2 = lv_pernr.
CALL FUNCTION 'HR_READ_INFOTYPE'
EXPORTING
** TCLAS = 'A'
pernr = lv_pernr2
infty = '0001'
begda = struc-begda
endda = struc-endda
** BYPASS_BUFFER = ' '
** LEGACY_MODE = ' '
** IMPORTING
** SUBRC =
TABLES
infty_tab = it_pa0001
** EXCEPTIONS
** INFTY_NOT_FOUND = 1
** OTHERS = 2
.
* IF sy-subrc <> 0.
** MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
** WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
* ENDIF.

SORT it_pa0001 BY endda DESCENDING.

READ TABLE it_pa0001 INDEX 1.


IF sy-subrc EQ 0.

SELECT SINGLE momag INTO l_modifier FROM zchpy_tab_jnj_pm


WHERE abkrs EQ it_pa0001-abkrs AND gsber EQ it_pa0001-gsber.

IF sy-subrc EQ 0.
back = l_modifier.
ELSE.
SELECT SINGLE momag INTO l_modifier FROM zchpy_tab_jnj_pm
WHERE abkrs EQ it_pa0001-abkrs AND gsber EQ '*'.

IF sy-subrc EQ 0.

back = l_modifier.
ELSE.

status = '2'.

ENDIF.

ENDIF.
ELSE.

status = '2'.

Proprietary and Confidential to NorthgateArinso Page 6


Posting to finance implementation
06/09/2011

ENDIF.
ENDIF.

ENDFORM. "ext_call_f

PY BUSINESS
FEATURE MODIFIER GL ACCOUNT
AREA AREA
PPMOD A5 AAA
C0
* AAA
A5 AAB
C1
* AAB
A5 AAC
C3
* AAC
A1 AAD
A4 AAE
C6
A5 AAF
* AAD
A4 AAG
A5 AAH
C9
A6 AAI
* AAG

A5 AAJ
CA

* AAJ
A1 AAK
A2 AAL
A3 AAM
CD
A4 AAN
A5 AAO
* AAK
A1 AAK
A2 AAL
A3 AAM
CE
A4 AAN
A5 AAO
* AAK
A1 AAK
A2 AAL
A3 AAM
CF
A4 AAN
A5 AAO
* AAK
CG A1 AAK
A2 AAL
A3 AAM
A4 AAN
A5 AAO

Proprietary and Confidential to NorthgateArinso Page 7


Posting to finance implementation
06/09/2011

* AAK
A1 AAK
A2 AAL
A3 AAM
CH
A4 AAN
A5 AAO
* AAK
A1 AAK
A2 AAL
A3 AAM
CI
A4 AAN
A5 AAO
* AAK
A1 AAK
A2 AAL
A3 AAM
CJ
A4 AAN
A5 AAO
* AAK
A1 AAK
A2 AAL
A3 AAM
CK
A4 AAN
A5 AAO
* AAK

If you can see in the table above that the PPMOD will return a modifier dependent of EEs Payroll area
and Business area. This Modifier will be used to choose the correspondent Gl-accounts.

If you ever create or need a new payroll area / business area combination you have just change or
add entries in table ZCHPY_TAB_JNJ_PM.

2.1.2 Parameter Modifi er for Chart of accounts


The customer has to decide how the posting will be organized and how the wage types will be
grouped to form the posting document and define the Chart of Accounts.

Each chart of account will have an identifier (Modifier) and will be assign to the parameter modifier
99KOM and 99ACC in Feature YCOMP.

99KOM Used to set Modifier for Symbolic Account Defn/Mapping


99ACC Used to set Modifier for euHReka GL Account Defn/Mapping

First the different Chart of accounts IDs have to be defined in table Y00BA_VIE_COMPN1.

Proprietary and Confidential to NorthgateArinso Page 8


Posting to finance implementation
06/09/2011

Note that in case of JNJ they defined a Chart of account per country site.

JNJBA Baar
JNJNE Neuchatel
JNJSH Schaffhausen
JNJSP Spreitenbach
JNJZG Zug

And then assign them to Feature YCOMP for Parameter Modifier 99KOM and 99ACC filtered by
Payroll area.
You can find in specification document the mapping between Payroll area end Country Site.

Proprietary and Confidential to NorthgateArinso Page 9


Posting to finance implementation
06/09/2011

Proprietary and Confidential to NorthgateArinso Page 10


Posting to finance implementation
06/09/2011

2.1.3 Assign WT to Main Symbolic Accounts


SM34 -> V_T52EL

All Wage types posted to FI/CO are assigned to one of the Main Symbolic Accounts ZZZC and ZZZA
with negative and positive sign like in the requirement document specified.

Proprietary and Confidential to NorthgateArinso Page 11


Posting to finance implementation
06/09/2011

2.1.4 Additional Symbolic Account Defi nition

Table Y00BA_VIE_FISADF or SPRO

This table is used to define the euHReka Additional Symbolic Accounts. This table assigns Text (or
"meaning") to each of the Additional Symbolic Accounts which you want to use (dependent on molga
and FI Parameter Modifier).

Proprietary and Confidential to NorthgateArinso Page 12


Posting to finance implementation
06/09/2011

This FI modifier are the chart of accound Ids defined by Parameter 99KOM maintained in feature
YCOMP and table Y00BA_TAB_COMP (see point 2.1.2.).

2.1.5 Assignment of WTs to Additional


Symbolic Accounts.

Table Y00BA_VIE_FIWTSA or spro

Proprietary and Confidential to NorthgateArinso Page 13


Posting to finance implementation
06/09/2011

This table re-maps wage types from Main Symbolic Accounts to Additional Symbolic Accounts
(dependent on molga and FI Modifier).

Proprietary and Confidential to NorthgateArinso Page 14


Posting to finance implementation
06/09/2011

This FI modifier are the chart of accound Ids defined by Parameter 99KOM maintained in feature
YCOMP and table Y00BA_TAB_COMP (see point 2.1.2.).

Proprietary and Confidential to NorthgateArinso Page 15


Posting to finance implementation
06/09/2011

2.1.5 GL Account Defi nition

Table Y00BA_VIE_FIACNT or SPRO.

Definition of euHReka GL Account Codes (dependent on molga and FI Modifier)

Proprietary and Confidential to NorthgateArinso Page 16


Posting to finance implementation
06/09/2011

This FI modifier are the chart of accound Ids defined by Parameter 99KOM maintained in feature
YCOMP and table Y00BA_TAB_COMP (see point 2.1.2.).

1.1.6 Assign Additional Symbolic account to GL


Accounts.

Table Y00BA_VIE_FISAAC or SPRO

Proprietary and Confidential to NorthgateArinso Page 17


Posting to finance implementation
06/09/2011

Mapping of Additional Symbolic Account to euHReka GL Account Codes.

Proprietary and Confidential to NorthgateArinso Page 18


Posting to finance implementation
06/09/2011

2.1.6 Posting Run

After this entire configuration before you will be able to run Posting for EEs (RPCIPE00) and see if
they are balanced or not.

Proprietary and Confidential to NorthgateArinso Page 19


Posting to finance implementation
06/09/2011

If there any EE that is not balanced (red one) it could be due to some reasons.
It could be due to wrong master data, and then you have to check ITs and payroll cluster and at last
option remove payroll clusters, run payroll and posting again.
The other reason could be a wrong configuration or mapping in euHReka tables so you have the
check it.

This entire configuration is enough to be able to run posting but just to see EEs balances.
To create also right posting documents some more step have to be done. These steps are not
euHReka dependent, is a standard SAP process.

Proprietary and Confidential to NorthgateArinso Page 20


Posting to finance implementation
06/09/2011

All these error above (in PCP0) could be solved with following steps in detailed in thie document

3. FI A CCOUNT D EFINITION (SAP)


In order to obtain clean Postings (documents) within RPCIPE00, point each euHReka Additional
Symbolic to one of GL-accounts within T030 to avoid posting errors.

3.1 T030
Access to T030 SPRO Payroll Payroll: Switzerland

Proprietary and Confidential to NorthgateArinso Page 21


Posting to finance implementation
06/09/2011

Transations OBYG (Balance Sheet) and OBYE (Expense).

To access to both tables you will set Chart of account CHCA.

Assign Balance Sheet accounts (HRF):


Here you have assign all the Balance sheet accounts (Symbolic account thats start by A )

Proprietary and Confidential to NorthgateArinso Page 22


Posting to finance implementation
06/09/2011

Assign Expense accounts (HRC):


Here you have asign all the Expense accounts (Symbolic account thats start by C )

Proprietary and Confidential to NorthgateArinso Page 23


Posting to finance implementation
06/09/2011

Before we create and maintain the general ledger accounts we have to follow some more steps

Proprietary and Confidential to NorthgateArinso Page 24


Posting to finance implementation
06/09/2011

1. Assign to all Company codes Field Status Variant 0001.

2. Assign all company code to chart of account CACH

Proprietary and Confidential to NorthgateArinso Page 25


Posting to finance implementation
06/09/2011

3. Define Account group.

Proprietary and Confidential to NorthgateArinso Page 26


Posting to finance implementation
06/09/2011

Important: expand SAKO range to maximum 9999999999.

3.2. G/L account master record


maintenance (FS00)
Now we continue with de gl-account master record maintenance. All this is necessary to get a clean
posting run.

Transaction FS00 Spro

Proprietary and Confidential to NorthgateArinso Page 27


Posting to finance implementation
06/09/2011

Here you have to implement all GL/Account for each Company Code with its text description.
This process has to be maintained in each system.

Steps:
A) Enter Gl-account and Company Code.

Proprietary and Confidential to NorthgateArinso Page 28


Posting to finance implementation
06/09/2011

B) In tab Type/Description enter Account Group G/L accounts (general), Short Text, long text
and choose radio button P&L statement acct for Expense accounts and Balance Sheet
Account for Balance Sheet accounts.

C) In tab Control Data enter Account currency CHF and just if you are registering a Balance
Sheet account you have also picked Only balances in local crcy.

Proprietary and Confidential to NorthgateArinso Page 29


Posting to finance implementation
06/09/2011

D) In tab Create/bank/interest just enter Field Status group G001.

E) Enter all descriptions for the language you want

Proprietary and Confidential to NorthgateArinso Page 30


Posting to finance implementation
06/09/2011

After these steps you will solve these errors of incorrect created documents(PCP0):

Missing accounts descriptions.

3.3. Cost Element


For all expense accounts you have to create a cost element.

Go to transaction FS00 enter gl-account, Company code and select Edit cost element.

Proprietary and Confidential to NorthgateArinso Page 31


Posting to finance implementation
06/09/2011

Enter now date period (01.01.1900 31.12.9999) and push enter.

Then just enter value 1 in field CElem Category and save.

With this step you will solve the error

that appear in incorrect created documents in tcode PCP0.

Proprietary and Confidential to NorthgateArinso Page 32


Posting to finance implementation
06/09/2011

3.4. Accounting Document Number


Ranges
Transaction FBN1

In this activity you create number ranges for documents. For each number range you specify:
A number interval from which document numbers are selected
The type of number assignment (internal or external)

You assign one or more document types to each number range.


Number ranges for documents are company code dependent. You must therefore create your number
ranges for each company code in which the document types is used.

The number intervals must not overlap. If you use year-dependent number ranges, you can specify
the same interval with the same key severaltimes for different fiscal years(the limit up to which a
number range is still valid). If you want to define number ranges which are independent of the fiscal
year, enter 9999 in the fiscal year field.

After this step you solved the following issue from incorrect created posting documents.

Proprietary and Confidential to NorthgateArinso Page 33


Posting to finance implementation
06/09/2011

3.5. Maintain Number Ranges for CO


Documents
The document number assigned in transaction KANK is dependent upon a couple of factors like the
activity used to update the CO file and the number assigned within the controlling area.

Which number range to use will depend on the group which you have assigned by their CO activity.

For FI you have to assign it to COIN group.

Proprietary and Confidential to NorthgateArinso Page 34


Posting to finance implementation
06/09/2011

With this step you solve the issue :

4. T O TAKE IN ACCOUNT

4.2. Delete Cost element


If you need to remove the cost elements from a gl-account go to transaction KA04 set the controlling
area and gl-account number and press execute.

Proprietary and Confidential to NorthgateArinso Page 35


Posting to finance implementation
06/09/2011

4.3. Technical Account


In this step, you assign a document split account to an account key. This is a clearing account
(Transaction HRA) in Accounting.

For various reasons, payroll data that is formatted for posting to accounting must be split into several
documents per posting run. In Human Resources (HR), key 1001 is used for the breakdown of documents.
A breakdown occurs if:

There are several company codes

There are different posting dates

Proprietary and Confidential to NorthgateArinso Page 36


Posting to finance implementation
06/09/2011

There are postings to G/L accounts, customer accounts, vendor accounts

This is specified in the step Create Posting Variants (for example, document breakdown for
expenses and payables)

The document split account that is stored under the key 1001 is also used to clear the balance within a G/L
account document for each business area.

An additional split may be required depending on the size of the document in Financial Accounting. In this
case, the clearing account specified under account key 1002 in transaction HRA, is used as the document
split account.

To see the technical accounts definition goes to SPRO Payroll Payroll: Switzerland

When you run posting and look at the created documents or goes to Tcode PCP0 and see an error
related to account 22128 usually it should be due two thinks:

1. A split in cost centre where the Business area is not displayed


In this case search for the wrong EE, go to IT27 and update cost centre split.
A user exit should be executed to insert the business area for this split.

Proprietary and Confidential to NorthgateArinso Page 37


Posting to finance implementation
06/09/2011

2. A document split due to huge size. More than 999 records.

4.4. PCP0
If you want to see as search the posting documents that were create properly o with error go to
transaction PCP0.
There you can choose the documents and check errors that could appear for their corrections.

After you open an incorrect document you see the following error message.

That means that there are some EEs which have an unvalid cost center or have no cost center.

To correct this you have to fix EEs master data.

Related Docuemens

Proprietary and Confidential to NorthgateArinso Page 38


Posting to finance implementation
06/09/2011

Hereby attached two documents that could be helpful.

GL-euHReka-PY-FI_P Posting to FICO


osting.doc Workinstructions.doc

Proprietary and Confidential to NorthgateArinso Page 39

Vous aimerez peut-être aussi