cancel
Showing results for 
Search instead for 
Did you mean: 

Sap Hcm Payroll For Bahrain

Former Member
0 Kudos

Hi All,

AI am new to this forum but I know I will get answer of all queries here..Thanks in advance..

My query is : What Payroll Driver and tax details/infotype we use for Bahrain Client .What specification we need to care for bahrain ?How it is different from Indian Payroll?

If anyone answer it ,I would be really grateful.

Regards

No Bold Letters

Edited by: Sikindar on Aug 8, 2011 11:45 AM

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member110706
Participant
0 Kudos

Dear All,

I have read all your comments above. Thanks, I could get some information.

I am in the process of IMPLEMENTING EMPLOYEE CENTRAL PAYROLL for our Bahrain customers. Even though I create Molga99 in ECP system, which country setting should I select on the Employee central side.

The countries that we select in ECP and EC side should ideally match, isn't.?

I thought of choosing Saudi Arabia, SAU, as it is closest to Bahrain in terms of Payroll processing, but I am receving the below error in Check tools.

Authorised SP Assertion Consumer Service SettingCountry/RegionThe logout URL error does not match the Payroll URL and Client ID for the country/region.Saudi Arabia

The Assertion Consumer Service URL does not match the Payroll URL and Client ID for the country/region.Saudi Arabia

Kindly advise, do we have any article that explains this behavior and its solution, please advise.

Thanks

ShaikFareedM
Participant
0 Kudos

Hi Swapnil

Thanks for your detailed reply.

What we need to maintain MOL in SU3 (AE / IQ)

Thanks.

Shaik

0 Kudos

Hi Anusuiya,

There is no SAP localization for Bahrain country. In my earlier project I have implemented SAP localization for UAE and the same client asking the same thing to Bahrain location. So I have extended the UAE localization to Bahrain instead of international payroll. You have to take care of currency with 3 digit for Bahrain and you have to do small correction in UAE schema. Trust everything is working properly. Last 2 yrs client is using this and there is no issue.

Regards,

Swapnilkumar P. Lakade

ShaikFareedM
Participant
0 Kudos

Hi Swapnil Kumar,

We are planning to use UAE localization for Iraq location. Can you please help how to manage the Iraq currency in UAE localization and what all the corrections we need to do in UAE schema.

Please guide me

Thanks,

Shaik

0 Kudos

Hi Shaik,

You can follow the below steps:

1. Assign pay scale currency as IQD.

2. Maintain Infotype 0008- Basic pay with IQD.

3. Now with the help of ABAP consultant, you can modified the payroll driver program "HAECALC0" with "ZHAECALC0", where you can find function module RP_GET_CURRENCY, which is reading only molga (country grouping) and pay scale type & payscale area is optional, so you can pass those two.

4. During payroll (ZHAECALC0) initialization it will read the same correctly for IQD and will calculates the payroll in IQD.

5. Now after salary process, all the records in the cluster (PC00_MAE_CLSTR) will be in IQD.

Try this, hope this help you.

Regards,

Swapnilkumar P. Lakade

former_member193652
Active Contributor
0 Kudos

Hi,

If there is no country version you have to use international version. Use 99 as your country.

You have to develop your own function for TAX and any special requirements you have.

For TAX you can develop a function thru ABAP and use it in you payroll schema or maybe develop a PCR.

Regards,

Omid

nishantbansal91
Active Contributor
0 Kudos

Hi,

We have got the same requirement for BD.

Can u please provide us some more information.

I had already raised the question.

Thanks and Regards,

Nishant Bansal

Former Member
0 Kudos

Hi,

There are no versions for Bahrain available in the standard. For the country, that no payroll driver exists, they use the international payroll driver RPCALCX0. You can also use RPCACLX0 as a template for your country. Please check the note 212246 for more details. When working with countries which do not have a standard localization, you can choose to use molga 99 (International) or the specific molga for the country.

> By choosing molga 99, you have the advantage that the payroll driver

and cluster is already created for this molga, but you have the

disadvantage that just one country can be assigned to molga 99.

> By choosing the specific molga for the country, you have to create

the payroll driver and the cluster structure, and set the right

customizing.

In this case, beside attached SAP Note 212246, for further and detailed information please check also the website:

service.sap.com/localization

The country payroll for UAE has already been released. Please check the marketplace which contains lots information:

http://service.sap.com/globalization

Country Information ->Middle East - Africa -> United Arab Emirates

Regards,

Nishtha

Former Member
0 Kudos

Hi,

Thanks for response,Its really helpful.

Can u pls send me snote 212246 as I am unable to view it .and pls provide specific payroll infotypes and statutory deductions/taxes used for this country.

Thanks

Edited by: Anusuiya on Aug 9, 2011 6:56 AM

Edited by: Anusuiya on Aug 9, 2011 7:19 AM

Former Member
0 Kudos

Hi Nishtha,

Which other Programs/Reports, apart from RPCALCX0, we have to do the same for a succesfull payroll run and finance posting? (we've already read the SAP Note)

We have the same situation for Panamá.

Thanks in advance,

Matías

Former Member
0 Kudos

Hi Anusuiya

here we go oss-212246

Summary

Symptom

You want to implement a customer-specific payroll for a country. For this, you require a country grouping and a cluster ID for saving the payroll results.

Other terms

Payroll, T500L, country groupings, molga, T500L_CUST, T52RELID, cluster

Reason and Prerequisites

The list of ISO codes is available at http://www.iso.org/iso/country_codes.

Solution

Use the country grouping and cluster ID that is specified for your country in the table T500L.  This prevents complications in case cluster IDs that are not listed in it are used for other applications.
However, if SAP later decides to provide a standard delivery for your country, you may have to perform additional actions.
Therefore, you should create as much of your own source code as possible in customer-specific includes and in the customer namespace.  (For example, the payroll program, own wage types, functions, operations, and so on.)
To save the payroll results, always also use the international structure.  Adhere as much as possible to the example of the standard countries.  (That is, make your additions as you would for a standard country, but without the NATIO substructure; see structure PAY99_RESULT.)

In particular for older implementations, you can also use the international structure for Molga 99 and cluster RX for the countries. However, due to the better evaluation options, we recommend that you use T500L as the starting point for each (new) individual country version.


In Release 4.6C, country groupings and cluster IDs were defined for numerous countries in the T500L table. These definitions are also the basis for projects implemented in lower releases. Use these definitions, if you want to develop customer-specific payrolls. The non-numeric country groupings can be used as of Release 4.0 only.

If you require customer-specific clusters for data other than payroll results, use the name ranges reserved in the TRESC table.

To create an entry in the T500L view, as of Release 4.6C, you must use transaction PECLUSTER to enter the relevant cluster ID in the T52RELID table beforehand. In lower releases, you must define the cluster ID as a domain fixed value for the RELID_PCL2 domain.

The T500L table was enhanced with Note 540898. The additions were also added to the list below. You can use the additional T500L_CUST Customizing table to restrict your view of the T500L table.

With Note 608912, new cluster IDs were created and entered in the T500L table, the 'IS' molga was deleted, and the cluster ID for the 'TM' molga was corrected.

With Note 748954, the VG and VI country groupings were added to the T500L table.

With Note 1000674, the ME country grouping was added to the T500L table and the ISO code of the YU country grouping was changed to RS.

With Note 1022651 the RO country grouping was deleted and 61 was created instead.

With Note 1159850, the EH country grouping was added to the T500L table.

With Note 1052406 the GG, IM and JE country groupings were created.

When you implemented Note 1439023, the cluster ID was created and entered in T500L for MOLGA 57.

When you implemented Note 1485037, the cluster ID "MO" was created and entered in T500L for MOLGA MO.

When you implemented Note 1636283, the cluster ID SS was created and entered in T500L for MOLGA SS.

With SAP Note 1673076, the cluster ID PQ was created and entered in T500L for MOLGA PS.

Below, you find the table T500L with all 217 entries:


Country groupingCountryISOCluster


01GermanyDERD

02SwitzerlandCHRC

03AustriaATRA

04SpainESRE

05The NetherlandsNLRN

06FranceFRRF

07CanadaCARK

08Great BritainGBRG

09DenmarkDKRM

10USAUSRU

11IrelandIEIE

12BelgiumBERB

13AustraliaAURQ

14MalaysiaMYRL

15ItalyITRI

16South AfricaZARW

17VenezuelaVEVE

18Czech RepublicCZCZ

19PortugalPTRP

20NorwayNORV

21HungaryHURH

22JapanJPRJ

23SwedenSERS

24Saudi ArabiaSAAA

25SingaporeSGRR

26ThailandTHTH

27Hong KongHKHK

28ChinaCNCN

29ArgentinaARAR

30LuxembourgLULU

31SlovakiaSKSK

32MexicoMXMX

33RussiaRUUR

34IndonesiaIDIS

35Brunei DarussalamBNBN

36UkraineUAUA

37BrazilBRBR

38ColumbiaCOCO

39ChileCLCL

40IndiaININ

41South KoreaKRKR

42TaiwanTWTN

43New ZealandNZNZ

44FinlandFIFI

45GreeceGRGR

46PolandPLPL

47TurkeyTRTR

48PhilippinesPHPH

49NamibiaNANA

50LesothoLSLS

51BotswanaBWBW

52SwazilandSZSZ

53MozambiqueMZMZ

54KenyaKEKE

55AngolaAOAO

56ZimbabweZWZW

57Netherlands AntillesANAT

58CroatiaHRHR

60IcelandISIC

61RomaniaRORO

62SloveniaSISI

99Other Countries99RX

ADAndorraADAD

AEUnited Arab EmiratesAEEM

AFAfghanistanAFAH

AGAntigua/BarbudaAGAG

ALAlbaniaALAB

AMArmeniaAMAM

AWArubaAWAW

AZAzerbaijanAZAZ

BABosnia-HerzegovinaBABA

BBBarbadosBBBB

BDBangladeshBDBD

BFBurkina FasoBFBF

BGBulgariaBGBG

BHBahrainBHBH

BIBurundiBIBI

BJBeninBJBJ

BMBermudaBMBM

BOBoliviaBOBO

BSBahamasBSBS

BTBhutanBTBT

BYBelarusBYBY

BZBelizeBZBZ

CDDemocratic Republic of the CongoCDKO

CFCentral African RepublicCFCF

CGCongoCGCG

CIIvory CoastCICI

CKCook IslandsCKCK

CMCameroonCMCM

CRCosta RicaCRCR

CUCubaCUKU

CVCape VerdeCVCV

CYCyprusCYZY

DJDjiboutiDJDJ

DMDominicaDMDM

DODominican RepublicDODO

DZAlgeriaDZDY

ECEcuadorECEC

EEEstoniaEEEE

EGEgyptEGEG

EHWestern SaharaEHEH

EREritreaERER

ETEthiopiaETEI

FJFijiFJFJ

FMMicronesiaFMFM

FOFaroe IslandsFOFO

GAGabonGAGA

GDGrenadaGDGD

GEGeorgiaGEGE

GFFrench GuyanaGFGF

GGGuernseyGGGG

GHGhanaGHGH

GLGreenlandGLGL

GMthe GambiaGMGM

GNGuineaGNGN

GQEquatorial GuineaGQGQ

GTGuatemalaGTGT

GUGuamGUGU

GWGuinea-BissauGWGW

GYGuyanaGYGY

HNHondurasHNHN

HTHaitiHTHT

ILIsraelILIL

IMIsle of ManIMIM

IQIraqIQIQ

IRIranIRIR

JEJerseyJEJE

JMJamaicaJMJM

JOJordanJOJO

KGKyrgyzstanKGKG

KHCambodiaKHKH

KIKiribatiKIKI

KMComorosKMKM

KNSt Kitts and NevisKNKT

KPNorth KoreaKPKP

KWKuwaitKWKW

KZKazakhstanKZKZ

LALaosLALO

LBLebanonLBLE

LCSt LuciaLCLC

LILiechtensteinLILI

LKSri LankaLKLK

LRLiberiaLRLR

LTLithuaniaLTLT

LVLatviaLVLV

LYLibyaLYLY

MAMoroccoMAMA

MCMonacoMCMC

MDMoldovaMDMD

MEMontenegroMEME

MGMadagascarMGMG

MHMarshall IslandsMHMH

MKMacedoniaMKMK

MLMaliMLML

MMMyanmarMMMM

MNMongoliaMNMN

MOMacaoMOMO

MPNorth Mariana IslandsMPMP

MRMauritaniaMRMR

MTMaltaMTMT

MUMauritiusMUMU

MVThe MaldivesMVMV

MWMalawiMWMW

NCNew CaledoniaNCNC

NENigerNENE

NGNigeriaNGNG

NINicaraguaNINI

NPNepalNPNP

NRNauruNRNR

OMOmanOMOM

PAPanamaPAPA

PEPeruPEPE

PFFrench PolynesiaPFPF

PGPapua New GuineaPGPG

PKPakistanPKPK

PRPuerto RicoPRPO

PSPalestinePSPQ

PWPalauPWPW

PYParaguayPYPU

QAQatarQAQA

RWRwandaRWWA

SBSolomon IslandsSBYS

SCSeychellesSCSC

SDSudanSDSD

SLSierra LeoneSLSL

SMSan MarinoSMSM

SNSenegalSNSN

SOSomaliaSOSO

SRSurinameSRSR

SSSouth SudanSSSS

STSao Tome and PrincipeSTYT

SVEl SalvadorSVSV

SYSyriaSYSY

TDChadTDTD

TGTogoTGTG

TJTajikistanTJTJ

TMTurkmenistanTMTU

TNTunesiaTNTM

TOTongaTOTO

TPEast TimorTPTP

TTTrinidad and TobagoTTTT

TVTuvaluTVTV

TZTanzaniaTZTZ

UGUgandaUGUG

UNNon-profit organizationsUNUN

UYUruguayUYUY

UZUzbekistanUZUZ

VAVatican CityVAVA

VCSt. VincentVCVC

VGBritish Virgin IslandsVGVG

VIAmerican Virgin IslandsVIVI

VNVietnamVNVN

VUVanuatuVUVU

WSWestern SamoaWSWS

YEYemenYEYE

YURepublic of SerbiaRSYU

ZMZambiaZMZM

Sharing the notes as suggested by Nishtha.doubt if this is relevant to ur context. I ud imagine there is not a localised payroll solution for Bahrain,experts correct me if im wrong pl.You may have to cusotmised the schema -X000(international payroll schema) if necessary.Gross to net calculation need to be customized to meet  your client requirements.

no worries

kg

Former Member
0 Kudos

Hi Matias

i reckon the above holds good for your aswell.if there is not a localised payroll solution x000 schema can be used and customised(gross to net) to meet ur client needs.u may write to SAP and enquire if they have plans to build a localised solution

no worries

kg

JSteyn
Explorer
0 Kudos

Hi Matias,

There are some partner solutions available.

Just Google "SAP Payroll Panama".

Kind regards,

Former Member
0 Kudos

Hi Jans Steyn,

Currently we are implementing payroll driver for Cambodia and user has the requirement that they do not want system to trigger any retro activities in their payroll. For any retro payment, they want the tax, contribution etc to be considered as part of current month tax and contribution calculation. Is there such a mothed to cater for it? as we know so far, standard SAP unable to cater for such scenario...

Best Regards,

Vickee

JSteyn
Explorer
0 Kudos

Hi Vickee,

Since there is no standard SAP solution available for Cambodia, I presume that you are configuring the International country version (Molga '99').

From your request, it looks like the requirement is what we normally call "Tax when Paid", i.e. if there is a retro-active change in salary, the tax / SS calculated in the previous month should remain as is, only the difference in Gross should be brought forward to the current month to be taxed.

The International country version will not do this automatically, because it will perform what we normally call "Tax when Earned", i.e. if there is a retro-active change in salary, the tax / SS is recalculated in the previous month, and the difference in tax is brought forward to the current month (you do not see it in the actual results but IN-view payroll reporting will pick up the difference).

You can change the payroll schema to reset the tax calculated during a retro calculation and to "flux forward" the gross difference to the current payroll period. It is a bit tricky at best and you need to configure influx and outflux wagetypes, but it can be done in standard SAP with creative schema and rule processing.

Best regards,

Jans

Former Member
0 Kudos

Hi Jans,


Your understanding is correct. I believe the standard SAP system does not meet the our user's requirement therefore we have to customize and the schema and rules. There are many scenarios to take into consideration, example when there is a back dated update into Master Data (PA30) which will trigger a payroll retro ( unless we remove the Master Data change date in IT3). Thank you for your suggestions and replied.

Best Regards,

Vickee

Former Member
0 Kudos

Hi Vickee

you may also look at 

Retroactive accounting relevance for payroll and time per IT

View:   V_582A_D for retro controls,if my understanding of ur req is correct

no worries

kg