Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

mapping rules !!!.......unable to understand

Former Member
0 Likes
566

Hi All

can someone help me understand the mapping rules, and also how to implement them???

Following is one example::

(sorry for the format but could not help maintain the table format)

SAP Field	Technical Name	Type	Length	Field ID	BenAdvan Field	Mapping
SSN	PA0002-PERID	CHAR	20	01	SSN	
				10	Employer ID	Blank
Adjustment Reason	PA0378-EVENT			15	Qualification Code	Mapping Rule 1
Last Name	PA0002-NACHN	CHAR	40	02	Last Name	
First Name	PA0002-VORNA	CHAR	40	03	First Name	
Address 1	PA0006-STRAS	CHAR	60	04	Street	
Address 2	PA0006-LOCAT	CHAR	60	05	Suite	
City	PA0006-ORT01	CHAR	40 	06	City	
State	PA0006-STATE	CHAR	3	07	State	
Zip	PA0006-PSTLZ	CHAR	10	08	Zip	
				11	Division	Mapping Rule 2
Gender	PA0002-GESC	CHAR	1	12	Sex	1=”M”;2=”F”
Date of Birth	PA0002-GBDAT	DATS	8	13	Date of Birth	
Marital Stat	PA0002-FAMST	CHAR	1	14	Marital Status	Mapping Rule 3
Adjustment Reason Date	PA0378-BEGDA			16	Qualification Date	
				17	Notification Date	Blank
					End of Eligibility Date 	Blank
					Print Certificate	Blank

Mapping Rule 1: Qualification Code (use adjustment reason in infotype 0377 – see note below)

DC – Loss of Dependent Status

DI – Disability

DP – Dependent Separation

LO – Lay Off

MD – Medicare Entitlement

ME – Cobra Event, Prior Medicare

RH – Reduced Hours

TE – Termination

WW- Death of Employee

RE – Retiree

Note: For the adjustment reasons and dates (qualification reasons and dates) you will need to check for the event FIRST, and then check for the associated date. An employee can have several adjustment reasons in a date range.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
394

Hi ,

Can clearly send the requirement. By seeing this, i understood , you should deal with idoc. By preparing the idoc type based on this mapping or else use the standard idoc for this mapping logic.

Thanks

Manju.

Hi All

can someone help me understand the mapping rules, and also how to implement them???

Following is one example::

(sorry for the format but could not help maintain the table format)

SAP Field	Technical Name	Type	Length	Field ID	BenAdvan Field	Mapping
SSN	PA0002-PERID	CHAR	20	01	SSN	
				10	Employer ID	Blank
Adjustment Reason	PA0378-EVENT			15	Qualification Code	Mapping Rule 1
Last Name	PA0002-NACHN	CHAR	40	02	Last Name	
First Name	PA0002-VORNA	CHAR	40	03	First Name	
Address 1	PA0006-STRAS	CHAR	60	04	Street	
Address 2	PA0006-LOCAT	CHAR	60	05	Suite	
City	PA0006-ORT01	CHAR	40 	06	City	
State	PA0006-STATE	CHAR	3	07	State	
Zip	PA0006-PSTLZ	CHAR	10	08	Zip	
				11	Division	Mapping Rule 2
Gender	PA0002-GESC	CHAR	1	12	Sex	1=”M”;2=”F”
Date of Birth	PA0002-GBDAT	DATS	8	13	Date of Birth	
Marital Stat	PA0002-FAMST	CHAR	1	14	Marital Status	Mapping Rule 3
Adjustment Reason Date	PA0378-BEGDA			16	Qualification Date	
				17	Notification Date	Blank
					End of Eligibility Date 	Blank
					Print Certificate	Blank

Mapping Rule 1: Qualification Code (use adjustment reason in infotype 0377 – see note below)

DC – Loss of Dependent Status

DI – Disability

DP – Dependent Separation

LO – Lay Off

MD – Medicare Entitlement

ME – Cobra Event, Prior Medicare

RH – Reduced Hours

TE – Termination

WW- Death of Employee

RE – Retiree

Note: For the adjustment reasons and dates (qualification reasons and dates) you will need to check for the event FIRST, and then check for the associated date. An employee can have several adjustment reasons in a date range.

1 REPLY 1
Read only

Former Member
0 Likes
395

Hi ,

Can clearly send the requirement. By seeing this, i understood , you should deal with idoc. By preparing the idoc type based on this mapping or else use the standard idoc for this mapping logic.

Thanks

Manju.